On Tue, 12 Mar 2013, Martin Mokrejs wrote:
> Hi Greg,
>
> Greg KH wrote:
> > On Tue, Mar 12, 2013 at 11:45:39AM +0100, Martin Mokrejs wrote:
> >> Hi,
> >> while testing how my computer behaves with USB disabled I see this line
> >> still
> >> in dmesg output:
> >>
> >> Initializing USB Mass S
On Tuesday 12 March 2013 17:58:30 Martin Mokrejs wrote:
> No, I just wondered why 'nousb' disables on the runtime ehci/xhci (also
> included
> statically in the kernbel binary) while not other USB-related modules. Maybe
> it
> was thought that no downstream modules will load because of unmet depe
Hi Greg,
Greg KH wrote:
> On Tue, Mar 12, 2013 at 11:45:39AM +0100, Martin Mokrejs wrote:
>> Hi,
>> while testing how my computer behaves with USB disabled I see this line
>> still
>> in dmesg output:
>>
>> Initializing USB Mass Storage driver...
>
> Did you build the driver into the kernel?
On Tue, Mar 12, 2013 at 11:45:39AM +0100, Martin Mokrejs wrote:
> Hi,
> while testing how my computer behaves with USB disabled I see this line
> still
> in dmesg output:
>
> Initializing USB Mass Storage driver...
Did you build the driver into the kernel? Or is it being automatically
loaded
Hi,
while testing how my computer behaves with USB disabled I see this line still
in dmesg output:
Initializing USB Mass Storage driver...
Is there any driver able to use it under 'nousb' situation at all? Shouldn't it
be prevented from loading as well? This was tested on 3.9-rc1.
Thank you,
