You are not logged in.
Pages: 1
Before coming to Arch, I was a long time Slackware user. As an ex-Slackee, I was used to doing the whole monolithic kernel thing. When Arch decided to switch to a more modular initrd based kernel, I wasn't impressed so I relied on custom compiling as much as possible. So over the last few days I've been testing the stock Arch kernel and CK patched version and I'm very impressed. Needless to say, they've won me over in terms of using modular as opposed to monolithic. Awesome work guys.
Offline
Nice post, johnisevil. Your appreciation is appreciated - glad you like the kernels. ![]()
Offline
Hooray! Feel free to add Feature Requests to the bug tracker if there's anything you feel we could improved.
Offline
Hooray! Feel free to add Feature Requests to the bug tracker if there's anything you feel we could improved.
So far everything is running nicely. Only issue I'm having is with the beta nvidia driver. When I go to start X it hangs then I need to reset my system. I think this is to do with the eeprom module since I've read a lot about this being a problem with the new nvidia driver.
Offline
I just installed the nvidia driver a couple of days ago and it works fine for me.
Mind you I have an NVidia card that is about 3 years old and that may have an influence.
Did you check the wiki for installation procedures? Just type "nvidia" in the wiki's search and you will find it.
Offline
phrakture wrote:Hooray! Feel free to add Feature Requests to the bug tracker if there's anything you feel we could improved.
So far everything is running nicely. Only issue I'm having is with the beta nvidia driver. When I go to start X it hangs then I need to reset my system. I think this is to do with the eeprom module since I've read a lot about this being a problem with the new nvidia driver.
Blacklist eeprom in your /etc/rc.conf.
James
Offline
Adding eeprom to MOD_BLACKLIST in /etc/rc.conf seemed to solve the issue with it causing X to hang when starting it but now I've got a new problem. I get the following error:
[john@metatron ~]$ startx
xauth: creating new authority file /home/john/.serverauth.3937
X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: UNKNOWN
Current Operating System: Linux metatron 2.6.18-ck #1 SMP PREEMPT Sun Nov 5 18:5
4:10 GMT 2006 i686
Build Date: 19 September 2006
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Nov 9 20:14:46 2006
(==) Using config file: "/etc/X11/xorg.conf"
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x84) [0x80c4724]
1: [0xb7fcc420]
2: /usr/bin/X(main+0x2aa) [0x806ea5a]
3: /lib/libc.so.6(__libc_start_main+0xd8) [0xb7def808]
4: /usr/bin/X(FontFileCompleteXLFD+0xa5) [0x806df61]
Fatal server error:
Caught signal 11. Server aborting
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.I only get this when using the nvidia-beta driver.
Offline
IMHO it will be better if you discuss problems of nvidia-beta in its thread, 'cause there are much more people who use nvidia-beta reading it.
to live is to die
Offline
IMHO it will be better if you discuss problems of nvidia-beta in its thread, 'cause there are much more people who use nvidia-beta reading it.
Also there's the non-beta 1.0.9629 nvidia driver in testing already. I've no idea if this will solve your issue but I think it's generally a good idea to use that instead of the (older) beta driver from unstable.
Offline
Romashka wrote:IMHO it will be better if you discuss problems of nvidia-beta in its thread, 'cause there are much more people who use nvidia-beta reading it.
Also there's the non-beta 1.0.9629 nvidia driver in testing already. I've no idea if this will solve your issue but I think it's generally a good idea to use that instead of the (older) beta driver from unstable.
I'll give that a try when I'm at home again. Thanks for the tip.
Offline
If I recall correctly, the similar problem was caused by orphaned files lying somewhere in /usr/lib. If you still get that error, uninstall nvidia-utils, remove all the leftovers and reinstall.
Offline
If I recall correctly, the similar problem was caused by orphaned files lying somewhere in /usr/lib. If you still get that error, uninstall nvidia-utils, remove all the leftovers and reinstall.
That kind of helps and kind of doesn't. The idea of orphaned files makes sense for something not working, but unless I know what they are I'm not about the start deleting files from /usr/lib.
Offline
Just purge all nvidia packages from your system and if you still see some *NVIDIA*/*nvidia* files in /usr/lib/, you can be pretty sure they're from outer space and thus can be safely removed. If that doesn't convince you - well, it's you who won't be able to use X with 3d acceleration ;-)
Offline
I guess you could move the "nvidia" files you're considering for deletion elsewhere, like to your home directory. I do this when I'm not 100% comfortable that removing a file will fix or break something.
Offline
Just purge all nvidia packages from your system and if you still see some *NVIDIA*/*nvidia* files in /usr/lib/, you can be pretty sure they're from outer space and thus can be safely removed. If that doesn't convince you - well, it's you who won't be able to use X with 3d acceleration ;-)
Well, I do get 3D acceleration just fine, but not with the beta drivers.
Offline
Still trying to figure out files that may be left over from a previous manual install of nvidia but a good tip for finding them shows the wonders of pacman and grep.
pacman -Qo /usr/lib/*.{a,la,so*} | grep "No package owns"Offline
Pages: 1