Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
02-15-2004, 09:02 PM
|
#1
|
Member
Registered: Sep 2002
Distribution: Fedora Core 3
Posts: 247
Rep:
|
Xfree86 update has bugs?
I doubt this is a coincidence... I ran swaret and updated everything like I usually do. There is an updated XFree86 package according to the changelog (x/xfree86-4.3.0-i486-6.tgz) for Feb. 12. Well after I updated everything, for the first time ever my X Server crashed out of nowhere when I was away from my computer. Then I noticed I get the following from dmesg:
Code:
request_module: failed /sbin/modprobe -- agpgart. error = 256
0: NVRM: AGPGART: unable to retrieve symbol table
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
Thoughts?
|
|
|
02-16-2004, 04:49 AM
|
#2
|
Member
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 770
Rep:
|
I get similar error messages to the last 4 lines, ie
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
My guess is that you are running a 2.6.1 or later kernel. I got these messages since the 2.6.1 kernel update. Are you sure that dmesg didn't show these messages before the XFree86 package upgrade?
Anyhow I have been trying to find the reason for the messages, and it appears to be a bug in X, probably there all along, but not reported by the 2.4 series kernels. There is reference to the problem in kernel developer mailing lists, so I am guessing that there is some chatter going on between the kernel developers and the XFree86 developers, and a fix will come along eventually...
I reckon your X server problems are very likely related to the first bit though:
request_module: failed /sbin/modprobe -- agpgart. error = 256
0: NVRM: AGPGART: unable to retrieve symbol table
and I believe this IS related to the XFree86 package update. I am guessing that XFree86 wants to use its own video driver, and has overwritten something that was previously handled by a 3rd party (Nvidia?) driver. In my case I had to re-run the Nvidia driver install script. (The GLX part was no longer loading, and I was down to 2D, this is consistent with the basic 2d level of support provided by the XFree86 driver)
Hope this makes a bit of sense.
tobyl
|
|
|
02-16-2004, 11:46 AM
|
#3
|
Member
Registered: Sep 2002
Distribution: Fedora Core 3
Posts: 247
Original Poster
Rep:
|
Well I noticed my X crashes when my screensaver kicks in, so I disabled that and it hasn't crashed since. And yes I am running 2.6.2. And I may have had those messages prior; I didn't really check then. I will try to reinstall the NVIDIA drivers and see it that helps any.
|
|
|
02-16-2004, 12:14 PM
|
#4
|
Member
Registered: Nov 2003
Location: Texas
Distribution: Slackware 9.1, Fedora Core 1 & Mandrake 9.2
Posts: 31
Rep:
|
I have the same problem with an ATI 9000 after updating XFree86. I almost said no to it, but I just can't resist an update. You know the old saying "If it ain't broke, break it".
I guess I will try to go back to previous XFree86. I tried reinstalling the VID drivers and that did me no good.
Good Luck,
|
|
|
02-16-2004, 12:18 PM
|
#5
|
Member
Registered: Sep 2002
Distribution: Fedora Core 3
Posts: 247
Original Poster
Rep:
|
I guess I will be fine if I don't run a screensaver, at least until a fix comes out.
|
|
|
All times are GMT -5. The time now is 03:27 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|