[prev in list] [next in list] [prev in thread] [next in thread] 

List:       suse-linux-e
Subject:    Re: [SLE] Kernel
From:       Curtis Rey <crrey () charter ! net>
Date:       2003-01-17 22:28:45
[Download RAW message or body]

One of the things you might try is to look at the "change log" for these 
respective kernels, I take it they are the Mantel kernels.  Also compare 
these to the ones at kernel.org to see what the vanilla kernels have.  

You could email Mantel about this as well, you'ld be surprised, I have done 
this with a couple of the developers for Linus' team and they have replied.  
This might get you some direction about what to do and it may also give them 
a heads up to issue they may or may not have been aware of.

Finally you could write down how every thing in fstab is layed out as far was 
what device has what partitions, e.g. /dev/hdb10 = / (root) and /dev/hdbx , 
or hdy etc.. = /home or /usr/ and so forth.  This way if you find that your 
completely stumped and want to start from scratch you can re-install with out 
formatting or just format the root drive, providing the you lay out won't 
hose your user account directory and/or other directories like /usr or what 
ever has programs or data you don't want to lose.  This would be a last 
resort.  I have had to do this on a few occasions and It's not really good 
insofar as Linux is designed to be recoverable - but doing so may take a 
certain amount of skill - the more I use and learn the less this option is 
considered because I have figure out how to fix things.  Or, you could try to 
reinstall the old kernel or do an "update where in you will probably need to 
update some core packages (or it won't think your actually updating) and then 
repatch/patch update whatever needs to be brought up to current.  

You should copy the messages from files such as ".xsession-errors", 
"/var/log/kdm.log", " /var/log/XFree86.log" "/var/log/warn" or anything else 
that you find pertinent in the "/var/log" directory and repost.  This way I 
or others on the list can get a better idea about whats going.  

It would look something like this:

(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/X11R6/lib/modules/libxaa.a
(II) Module xaa: vendor="The XFree86 Project"
	compiled for 4.2.0, module version = 1.0.0
	ABI class: XFree86 Video Driver, version 0.5
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Loading /usr/X11R6/lib/modules/libramdac.a
(II) Module ramdac: vendor="The XFree86 Project"
	compiled for 4.2.0, module version = 0.1.0
	ABI class: XFree86 Video Driver, version 0.5
(II) do I need RAC?  No, I don't.
(II) resource ranges after preInit:
	[0] 0	0xddc80000 - 0xddcfffff (0x80000) MX[B]
	[1] 0	0xd8000000 - 0xdbffffff (0x4000000) MX[B]
	[2] 0	0xde000000 - 0xdeffffff (0x1000000) MX[B]
	[3] -1	0xffe00000 - 0xffffffff (0x200000) MX[B](B)
	[4] -1	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[5] -1	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[6] -1	0x000c0000 - 0x000effff (0x30000) MX[B]
	[7] -1	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[8] -1	0xdfff7e00 - 0xdfff7eff (0x100) MX[B]
	[9] -1	0xdfff7f00 - 0xdfff7fff (0x100) MX[B]
	[10] -1	0xdfffc000 - 0xdfffffff (0x4000) MX[B]
	[11] -1	0xe0000000 - 0xe7ffffff (0x8000000) MX[B]
	[12] -1	0xdfef0000 - 0xdfefffff (0x10000) MX[B](B)
	[13] -1	0xddc80000 - 0xddcfffff (0x80000) MX[B](B)
	[14] -1	0xd8000000 - 0xdbffffff (0x4000000) MX[B](B)
	[15] -1	0xde000000 - 0xdeffffff (0x1000000) MX[B](B)
	[16] 0	0x000a0000 - 0x000affff (0x10000) MS[B](OprD)
	[17] 0	0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD)
	[18] 0	0x000b8000 - 0x000bffff (0x8000) MS[B](OprD)
	[19] -1	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[20] -1	0x00000000 - 0x000000ff (0x100) IX[B]
	[21] -1	0x0000bc00 - 0x0000bc1f (0x20) IX[B]
	[22] -1	0x0000c000 - 0x0000c01f (0x20) IX[B]
	[23] -1	0x0000c400 - 0x0000c4ff (0x100) IX[B]
	[24] -1	0x0000c800 - 0x0000c81f (0x20) IX[B]
	[25] -1	0x0000cc00 - 0x0000cc1f (0x20) IX[B]
	[26] -1	0x0000fc00 - 0x0000fc0f (0x10) IX[B]
	[27] -1	0x0000d800 - 0x0000d80f (0x10) IX[B]
	[28] -1	0x0000dc00 - 0x0000dc03 (0x4) IX[B]
	[29] -1	0x0000e000 - 0x0000e007 (0x8) IX[B]
	[30] -1	0x0000e400 - 0x0000e403 (0x4) IX[B]
	[31] -1	0x0000e800 - 0x0000e807 (0x8) IX[B]
	[32] -1	0x0000d000 - 0x0000d007 (0x8) IX[B]
	[33] -1	0x0000d400 - 0x0000d41f (0x20) IX[B]
	[34] 0	0x000003b0 - 0x000003bb (0xc) IS[B](OprU)
	[35] 0	0x000003c0 - 0x000003df (0x20) IS[B](OprU)
(II) NVIDIA(0): AGP 4X successfully initialized
(II) NVIDIA(0): Setting mode "1280x1024"
(II) NVIDIA(0): Using XFree86 Acceleration Architecture (XAA)
	Screen to screen bit blits
	Solid filled rectangles
	Solid filled trapezoids
	8x8 mono pattern filled rectangles
	8x8 mono pattern filled trapezoids
	Indirect CPU to Screen color expansion
	Solid Lines
	Scanline Image Writes
	Offscreen Pixmaps
	Driver provided FillSolidRects replacement
	Driver provided FillSolidSpans replacement
	Driver provided FillMono8x8PatternRects replacement
	Driver provided WritePixmap replacement
	Driver provided ReadPixmap replacement
	Setting up tile and stipple cache:
		20 128x128 slots
		5 256x256 slots
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-GLX
(II) Loading extension NV-CONTROL
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) [GLX]: Calling GlxExtensionInit
(II) Keyboard "Keyboard[0]" handled by legacy driver
(**) Option "Protocol" "imps/2"
(**) Mouse[1]: Protocol: "imps/2"
(**) Option "CorePointer"
(**) Mouse[1]: Core Pointer
(**) Option "Device" "/dev/input/mice"
(**) Option "Buttons" "8"
(**) Mouse[1]: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Mouse[1]: ZAxisMapping: buttons 4 and 5
(**) Mouse[1]: Buttons: 8
(II) XINPUT: Adding extended input device "Mouse[1]" (type: MOUSE)

or something like this: 

Jan 17 05:28:33 linux kernel: ip_tables: (C) 2000-2002 Netfilter core team
Jan 17 05:28:33 linux kernel: ip_conntrack (4095 buckets, 32760 max)
Jan 17 05:28:33 linux kernel: usb-uhci.c: Detected 2 ports
Jan 17 05:28:33 linux last message repeated 3 times
Jan 17 05:28:33 linux kernel: usb.c: USB device 2 (vend/prod 0x46d/0xc207) is 
not claimed by any active driver.
Jan 17 05:28:33 linux kernel: usb.c: USB device 3 (vend/prod 0x46d/0xc025) is 
not claimed by any active driver.
Jan 17 05:28:33 linux kernel: sg_attach: dev0=(21:0)
Jan 17 05:28:33 linux kernel: Attached scsi CD-ROM sr0 at scsi0, channel 0, id 
0, lun 0
Jan 17 05:28:33 linux kernel: sr0: scsi3-mmc drive: 8x/32x writer cd/rw 
xa/form2 cdda tray
Jan 17 05:28:40 linux kernel: usb_control/bulk_msg: timeout
Jan 17 05:28:41 linux kernel: usb-uhci.c: ENXIO 84000280, flags 0, urb 
c52750c0, burb c5275240
Jan 17 05:28:41 linux last message repeated 3 times
Jan 17 05:28:44 linux kernel: ide-scsi: hdd: unsupported command in request 
queue (0)
Jan 17 05:28:44 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 
64
Jan 17 05:28:44 linux kernel: ide-scsi: hdd: unsupported command in request 
queue (0)
Jan 17 05:28:44 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 
66
Jan 17 05:28:44 linux kernel: ide-scsi: hdd: unsupported command in request 
queue (0)
Jan 17 05:28:44 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 
68
Jan 17 05:28:44 linux kernel: ide-scsi: hdd: unsupported command in request 
queue (0)
Jan 17 05:28:44 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 
70
Jan 17 05:28:44 linux kernel: ide-scsi: hdd: unsupported command in request 
queue (0)
Jan 17 05:28:44 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 
72
Jan 17 05:28:44 linux kernel: ide-scsi: hdd: unsupported command in request 
queue (0)
Jan 17 05:28:44 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 
74
Jan 17 05:28:44 linux kernel: ide-scsi: hdd: unsupported command in request 
queue (0)
Jan 17 05:28:44 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 
76
Jan 17 05:28:44 linux kernel: ide-scsi: hdd: unsupported command in request 
queue (0)
Jan 17 05:28:44 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 
78
Jan 17 05:28:52 linux kernel: nvidia: loading NVIDIA Linux x86 NVdriver Kernel 
Module  1.0-3123  Tue Aug 27 15:56:48 PDT 2002
Jan 17 15:52:09 linux kernel: ip_tables: (C) 2000-2002 Netfilter core team
Jan 17 15:52:09 linux kernel: ip_conntrack (4095 buckets, 32760 max)
Jan 17 15:52:09 linux kernel: usb-uhci.c: Detected 2 ports
Jan 17 15:52:09 linux last message repeated 3 times
Jan 17 15:52:09 linux kernel: usb.c: USB device 2 (vend/prod 0x46d/0xc207) is 
not claimed by any active driver.
Jan 17 15:52:09 linux kernel: usb.c: USB device 3 (vend/prod 0x46d/0xc025) is 
not claimed by any active driver.
Jan 17 15:52:09 linux kernel: sg_attach: dev0=(21:0)
Jan 17 15:52:09 linux kernel: Attached scsi CD-ROM sr0 at scsi0, channel 0, id 
0, lun 0
Jan 17 15:52:09 linux kernel: sr0: scsi3-mmc drive: 8x/32x writer cd/rw 
xa/form2 cdda tray
Jan 17 15:52:16 linux kernel: usb_control/bulk_msg: timeout
Jan 17 15:52:17 linux kernel: usb-uhci.c: ENXIO 84000280, flags 0, urb 
c523a140, burb c523a240
Jan 17 15:52:17 linux last message repeated 3 times
Jan 17 15:52:20 linux kernel: ide-scsi: hdd: unsupported command in request 
queue (0)
Jan 17 15:52:20 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 
64
Jan 17 15:52:20 linux kernel: ide-scsi: hdd: unsupported command in request 
queue (0)
Jan 17 15:52:20 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 
66
Jan 17 15:52:20 linux kernel: ide-scsi: hdd: unsupported command in request 
queue (0)
Jan 17 15:52:20 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 
68
Jan 17 15:52:20 linux kernel: ide-scsi: hdd: unsupported command in request 
queue (0)
Jan 17 15:52:20 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 
70
Jan 17 15:52:20 linux kernel: ide-scsi: hdd: unsupported command in request 
queue (0)
Jan 17 15:52:20 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 
72
Jan 17 15:52:20 linux kernel: ide-scsi: hdd: unsupported command in request 
queue (0)
Jan 17 15:52:20 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 
74
Jan 17 15:52:20 linux kernel: ide-scsi: hdd: unsupported command in request 
queue (0)
Jan 17 15:52:20 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 
76
Jan 17 15:52:20 linux kernel: ide-scsi: hdd: unsupported command in request 
queue (0)
Jan 17 15:52:20 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 
78
Jan 17 15:52:27 linux kernel: nvidia: loading NVIDIA Linux x86 NVdriver Kernel 
Module  1.0-3123  Tue Aug 27 15:56:48 PDT 2002

This is what most of the real propeller heads here need to get a real idea 
about whats happening (bless them all).  They really can't help you if they 
don't know whats going on.  They rely on these things to service and tweak 
their own systems so up 'till now you post have probably been a little to 
vague for them to help.  These logs are from the /var/log directory and tell 
about whats happening with both your Xserver and the general manner in which 
devices are being utilized or failing.  You will notice some like the (EE) or 
(WW) for Error or Warn revolving aroung the nvidia drivers and the external 
USB device that's having problems will mostly like be fairly obvious in the 
file output, it might looks similar to this:
 
"Jan 17 05:28:44 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 
64
Jan 17 05:28:44 linux kernel: ide-scsi: hdd: unsupported command in request ." 

You could cut/paste these outputs into a post of if you have a good Idea you 
can cut it down and say something like "the nvidia drivers fail to load in X 
with this message" and just post the couple of lines of output (rather then a 
long list of repeating or redundant lines)

Take a look at the error output and the changelogs for the kernel and see what 
you can find and then repost.

Cheers and HTH, Curtis.



On Friday 17 January 2003 06:11, Linux World 999 wrote:
> ----- Original Message -----
> From: "Linux World 999" <linuxworld999@yahoo.co.uk>
> Sent: Thursday, January 16, 2003 5:11 PM
>
> > ----- Original Message -----
> > From: "Curtis Rey" <crrey@charter.net>
> > Sent: Thursday, January 16, 2003 2:38 PM
> >
> > On Thursday 16 January 2003 06:39, Linux World 999 wrote:
> > > SuSE 8.1 is running on a PC.  The software was installed from scratch
>
> and
>
> > > has been running without problems.  On SuSe's update site, there is a
>
> new
>
> > > Kernel for Athlon processors.  Yast2 installed K_Athalon kernel as the
> > > default kernel.
>
> <snip>
>
> > >Let me guess!  You have an Nvidia card with the nvidia drivers
> > > installed?
> >
> > If
> >
> > >this is the case you'll most likely have to reinstall the preveious
>
> kernel
>
> > >and then remove all pieces of the nvidia kernel and glx drivers.
> >
> > You are right about the nvidia drivers.
> >
> > >If this is indeed the case then go to:
> > >
> > >http://tldp.org/HOWTO/mini/Nvidia-OpenGL-Configuration/instnvidia.html
> > >
> > >and focus on the part about removing the libGL* and the libglx parts
> > > from
> >
> > the
> >
> > >various.  I had a similar problem and had a hard time getting the system
>
> to
>
> > >setup the nvidia 3D packages.  In fact I backdated the drivers to the
>
> 3123
>
> > >version offered by YOU using YaST to install them.
> >
> > Will try this tonight and let you know how the result.
> >
> > >HTH, let us know if this is or isn't the problem.  Curtis.
>
> <snip>
>
> Using the "nv" drivers, the kernel update installed correctly.  However,
> the new kernel does not recognise the external USB2 & firewire drives.  In
> light of this, the old kernel was "restored".
>
> Any other ideas?
>
> __________________________________________________
> Do You Yahoo!?
> Everything you'll ever need on one web page
> from News and Sport to Email and Music Charts
> http://uk.my.yahoo.com

-- 
The reasons behind the DMCA, TCPA, and Palladium that are presented to the 
public are only secondary to their real purpose.  That is to lock in markets, 
stiffle competition and pidgeon hole consumers from any viable alternatives 
that the sponsers see as competitive and a threat to their market shares and 
business models.

-- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic