[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20061208222148.u6druqastzscwgg0@69.222.0.225>
Date: Fri, 08 Dec 2006 22:21:48 -0600
From: art@...ltd.com
To: linux-kernel@...r.kernel.org
Cc: zaitcev@...hat.com, torvalds@...l.org
Subject: Re: 2.6.19-git libusual: modprobe for usb-storage succeeded, but
module is not present
to: linux-kernel@...r.kernel.org
cc: zaitcev@...hat.com, torvalds@...l.org
Re: 2.6.19-git libusual: modprobe for usb-storage succeeded, but
module is not present
> usb 2-2: new high speed USB device using ehci_hcd and address 3
> > usb 2-2: configuration #1 chosen from 1 choice
> > libusual: modprobe for usb-storage succeeded, but module is not present
> > usb 2-4: new high speed USB device using ehci_hcd and address 5
> > usb 2-4: configuration #1 chosen from 1 choice
> > libusual: modprobe for usb-storage succeeded, but module is not present
> > usb 2-5: new high speed USB device using ehci_hcd and address 6
> > usb 2-5: configuration #1 chosen from 1 choice
> > libusual: modprobe for usb-storage succeeded, but module is not present
> I don't know what you've done to accomplish it, but either your
> modules got separated (e.g. libusual built statically while usb-storage
> is dynamic), or your modprobe is toast, or 100 other reasons.
>
> Just deconfigure CONFIG_BLK_DEV_UB and CONFIG_USB_LIBUSUAL
> and forget about it all.
>
> I know, I have to think of a workaround for this, but nothing is
> readily apparent.
>
> -- Pete
was
CONFIG_BLK_DEV_UB=m
CONFIG_USB_LIBUSUAL=y
now
# CONFIG_BLK_DEV_UB is not set
# CONFIG_USB_LIBUSUAL is not set
works ok thanx
xboom
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists