Please don't give up on this, Brian. So far, everyone I've asked for help on this has just given up on me, and I haven't been able to find enough information to figure it out myself. It has to have something to do with the way Dapper assigns drivers to the hardware during loading. My modem activates right after 'Loading Hardware Drivers' during the boot sequence. I just don't know how to recreate what it does manually while Edgy or Feisty are running. I want to be able to upgrade to Feisty when it is ready, but this modem issue will prevent that.
I appreciate you time very much. Thank you, Steve On 3/15/07, Steven Dilworth <[EMAIL PROTECTED]> wrote: > > I did that, and got the module to load, but couldn't get my modem to 'use' > it. > > On 3/15/07, Brian Murray <[EMAIL PROTECTED]> wrote: > > > > You could try 'sudo modprobe rndis_host', if you haven't already, as the > > module is still available with the 2.6.17 kernel. > > > > -- > > Lost USB Cable Modem Detection After Dapper > > https://launchpad.net/bugs/92488 > > > > -- Lost USB Cable Modem Detection After Dapper https://launchpad.net/bugs/92488 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
