Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I think it works fine, except for one thing. The driver complains about not being able to find the WLAN card, until I eject it, and insert it again.
Then it prompts:
PCI: Enabling device 03:00.0 (0000 -> 0003)
and then the driver loads fine..
So.. in short. I think that the device doesn't get initialized until I explicitly insert it. Anything I should modify/configure in order to have it 'detected' during startup?
Its pcmcia doinking up and not loading the cardbus module correctly... it might be cardmgr being slow to start so it doesn't recognize an insertion event. Hmm, its not a real pcmcia card, its a cardbus card, and the kernel dealing with these is a rather new thing, not to mention that userspace binaries are still pcmcia-cs, so development is slow and split in half.
I guess the best thing I can think to do is cheat. Call a reload of pcmcia with the card in there. If this is redhat, Suse, mandrake:
/etc/rc.d/init.d/pcmcia restart
If that loads the module correctly, just put that line in:
/etc/rc.d/rc.local or if its SuSe, boot.local, or really, post back with your distro.
The other ideas I can think of are all unfortunately voodoo, hand compile a newer version of pcmcia-cs against your existing kernel... the bug is probably with cardmgr not probing the socket right and only catching it on stab events, possibly yenta_socket, the in-kernel driver, but I doubt it, that thing is usually quite good at what it does, is there anything odd in dmesg on startup?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.