On Jan 08, M Jared Finder [EMAIL PROTECTED] wrote:
With kernel 2.6.14, the nvidiafb was loaded, which screwed up on my
GeForce 4 MX. nvidiafb should be blacklisted by default.
It is supposed to be. Feel free to investigate why it's being loaded
(I do not own any nvidia hardware).
Also, please
Marco d'Itri wrote:
On Jan 08, M Jared Finder [EMAIL PROTECTED] wrote:
With kernel 2.6.14, the nvidiafb was loaded, which screwed up on my
GeForce 4 MX. nvidiafb should be blacklisted by default.
It is supposed to be. Feel free to investigate why it's being loaded
(I do not own any nvidia
On Jan 08, M Jared Finder [EMAIL PROTECTED] wrote:
Shouldn't the effects of having an empty modprobe.conf be documented
*somewhere*?
Like in the man page and in the warning you get at every boot from the
init script?
--
ciao,
Marco
signature.asc
Description: Digital signature
Marco d'Itri wrote:
On Jan 08, M Jared Finder [EMAIL PROTECTED] wrote:
Shouldn't the effects of having an empty modprobe.conf be documented
*somewhere*?
Like in the man page and in the warning you get at every boot from the
init script?
Boy, am I embaressed.
Yeah, that seems like a good
Package: udev
Version: 0.079-1
Followup-For: Bug #80
With kernel 2.6.14, the nvidiafb was loaded, which screwed up on my
GeForce 4 MX. nvidiafb should be blacklisted by default.
-- MJF
-- Package-specific info:
-- /etc/udev/rules.d/:
/etc/udev/rules.d/:
total 0
lrwxrwxrwx 1 root root 20
5 matches
Mail list logo
