problems with RH8.0 & kernel 2.4.20

dfiguero · 12-12-02, 11:13 AM

Hi,

I seem to have a very weird problem. I downloaded and installed RH8.0, I then upgraded the kernel to 2.4.20 and finally I installed the NVIDIA drivers (rebuilt from the RPM source).

Everything works fine the first time I run 'startx' after rebooting the machine. But if I log out and try 'startx' again then I get stuck with the RH/gnome splash screen. I've checked with 'lspci' and /proc/iomem and there are no conflicts there. I've also loaded X withouth gnome and everything seems fine. /var/log/XFree86.0.log doesn't report any errors.

The only difference I see when running 'startx' after rebooting and any other time after that is a line in the log which points to a PCI address (oldVal1):

II) PCI: stages = 0x03, oldVal1 = 0x8000003c, mode1Res1 = 0x80000000

is what I get when I run startx after rebooting.

(II) PCI: stages = 0x03, oldVal1 = 0x800000b0, mode1Res1 = 0x80000000

and this is what I get every other time.

Any clues as to why it decides to change address or why it will only work on that particular address (0x8000003c)?

Thanks,

Diego

bwkaz · 12-12-02, 11:31 AM

When it fails, is there anything possibly relevant in either the X log (/var/log/XFree86.0.log) or the kernel error / warning log (/var/log/messages and/or the output of dmesg)?

I don't have any idea what that oldVal1 even is, so, err, yeah.

dfiguero · 12-12-02, 12:55 PM

No, unfortunately there is no error msg in either the X log or the output of dmesg.

I've gone as far as knowing that the problem is somewhere after gnome-session is called by startx -> /etc/X11/xinit/xinitrc.

But I am almost sure the problem has to do with the oldVal1 value since it always contains the same value after reboot and it changes the second time 'startx' is executed.

12-12-02, 11:13 AM	#1
dfiguero Registered User Join Date: Dec 2002 Posts: 2	problems with RH8.0 & kernel 2.4.20 Hi, I seem to have a very weird problem. I downloaded and installed RH8.0, I then upgraded the kernel to 2.4.20 and finally I installed the NVIDIA drivers (rebuilt from the RPM source). Everything works fine the first time I run 'startx' after rebooting the machine. But if I log out and try 'startx' again then I get stuck with the RH/gnome splash screen. I've checked with 'lspci' and /proc/iomem and there are no conflicts there. I've also loaded X withouth gnome and everything seems fine. /var/log/XFree86.0.log doesn't report any errors. The only difference I see when running 'startx' after rebooting and any other time after that is a line in the log which points to a PCI address (oldVal1): II) PCI: stages = 0x03, oldVal1 = 0x8000003c, mode1Res1 = 0x80000000 is what I get when I run startx after rebooting. (II) PCI: stages = 0x03, oldVal1 = 0x800000b0, mode1Res1 = 0x80000000 and this is what I get every other time. Any clues as to why it decides to change address or why it will only work on that particular address (0x8000003c)? Thanks, Diego

12-12-02, 11:31 AM	#2
bwkaz Registered User Join Date: Sep 2002 Posts: 2,262	When it fails, is there anything possibly relevant in either the X log (/var/log/XFree86.0.log) or the kernel error / warning log (/var/log/messages and/or the output of dmesg)? I don't have any idea what that oldVal1 even is, so, err, yeah. __________________ Registered Linux User #219692

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[BUG] nvidia crashes kernel with 'Xid 13' and attempted to yield the CPU while atomic	rockob	NVIDIA Linux	36	09-26-12 07:48 AM
upgrade to xorg server 1.13 damaged Geforce 7300 GT	KDE	NVIDIA Linux	2	09-07-12 08:04 AM
Fatal upgrade: from bad (8800 GTS) to worse 9GTX 560 Ti)	ssnyder	NVIDIA Linux	1	07-01-12 08:14 PM
UEFI+Nvidia - NVRM: Your system is not currently configured to drive a VGA console...	interzoneuk	NVIDIA Linux	0	06-26-12 04:51 AM
xorg locks-up with newest nvidia drivers w/ vdpau.	theroot	NVIDIA Linux	1	06-24-12 11:04 AM

12-12-02, 12:55 PM	#3
dfiguero Registered User Join Date: Dec 2002 Posts: 2	No, unfortunately there is no error msg in either the X log or the output of dmesg. I've gone as far as knowing that the problem is somewhere after gnome-session is called by startx -> /etc/X11/xinit/xinitrc. But I am almost sure the problem has to do with the oldVal1 value since it always contains the same value after reboot and it changes the second time 'startx' is executed.