On Mon, May 4, 2009 at 9:30 AM, Kumar Appaiah <[email protected]> wrote: > I hope you didn't reboot after doing the modprobe, since that may undo > the modprobe... But assuming that the module is loaded every reboot, > the problem would be there... >
I did reboot after doing a modprobe.. Still no use.. > > I would suggest comparing the lspci output on your computer with the > ones given at the bottom of the page: > > http://wiki.debian.org/ipw2200 > lspci does not output a wireless device at all even after installing the firmware / manually placing it in /lib/firmware and adding it to the boot image.. >It would be nice if you could describe part of the dmesg >output which appears when you insert the module using modprobe, since >that could help track down where the problem might be. I don't understand this part.. You want me to paste the dmesg output as a whole (that'd be too long)? Or should i pipe grep -i <something> and display the output? On Mon, May 4, 2009 at 10:16 AM, Kapil Hari Paranjape <[email protected]> wrote: > Hello, > > Are you booting using a Debian linux-image-2.6.26-2-... kernel? > If so you may want to should run (as root). > update-initramfs -u > This ensures that all needed modules are in the initrd.img image. > > Other than that your problem appears to be mysterious since the > ipw2200 driver works fine with the R51 that we have. > I'm booting using a Debian linux-image-2.6.26-1-... kernel.. I forgot to mention updating the image.. I'd done it once i added the ipw2200 module to the kernel using modprobe.. May the source be with you. Bhargav Prasanna _______________________________________________ To unsubscribe, email [email protected] with "unsubscribe <password> <address>" in the subject or body of the message. http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
