[PlanetCCRMA] Re: 2.6.7 ccrma kernel and usb / nvidia support

[Rick B]

Fernando Lopez-Lezcano wrote:

>On Wed, 2004-11-17 at 21:32, Shayne O'Connor wrote:
>  
>
>>Rick B wrote:
>>
>>    
>>
>>>You could try booting without acpi. To do this you need to add
>>>acpi=off 
>>>to the kernel boot line in grub.conf like so:
>>>
>>>title Fedora Core (2.6.8.1-1.520.1vR9.ll.rhfc2.ccrma)
>>>    root (hd0,1)
>>>    kernel /vmlinuz-2.6.8.1-1.520.1vR9.ll.rhfc2.ccrma ro
>>>root=/dev/hda3 
>>>rhgb acpi=off apm=off
>>>
>>>Or you can just edit the line when the boot screen appears by clicking
>>>on the kernel you wan't to boot then pressing "e". When your done 
>>>editing press enter and then press "b" to boot. This only works for
>>>that 
>>>one boot, if you want to make it permanent you will have to add it to 
>>>the grub.conf file.
>>>      
>>>
>>nope - that didn't do it either :(
>>
>>unless anyone else has some ideas, looks like it's time for another
>>re-install ... dear god ...
>>    
>>
>
>I suspect a reinstall would not help. There must be something wrong with
>the kernel itself. Paying attention I have seen a message on recent
>kernels I built that said that the usbdevfs filesystem could not be
>mounted on /proc. Apparently that message is not logged, see if you can
>see it during boot (it happens during the initial rc.rcsysinit script).
>I thought I had all the options enabled for that...
>
>This is the line in /etc/rc.d/rc.sysinit that fails:
>  mount -t usbdevfs usbdevfs /proc/bus/usb
>See if that fails, or check whether you have something in /proc/bus/usb/
>
>I'll have to investigate this more....
>
>Maybe the binary driver is probing /proc/bus/usb to find whether the
>device is there or not. 
>
>-- Fernando
>
>
>_______________________________________________
>PlanetCCRMA mailing list
>PlanetCCRMA at ccrma.stanford.edu
>http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
>
>  
>
    I had problems with my scanner on FC2 because permissions were not 
set right on /proc/bus/usb/002/002 for users, and root was the only one 
that could use the scanner. Could this be a permissions problem?

                Rick B