Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm using Ubuntu - have used the stock kernel, recompiled 2.28, 2.29 and tried Interpid and even Karmic Alpha, but always the same result:
The card will scan (i.e. iwlist eth1 scan), but will not set - I always get 'SET Failed: Device or resource busy'. Have attempted to determine in as many ways possible what has got hold of the device, but am failing miserably.
I've tried blacklisting bcm43xx b43legacy, ssb and b44 but with no luck.
Incidently it turns up as a eth card, and I can't get udev to recognise it otherwise.
Um, I hate to be the one to break this to you, but if you read the Broadcom site, you'll see the that driver is for the 4311, 4312, 4321 and 4322 chipsets. With a 4310 you will likely have better luck with b43/ssb or ndiswrapper.
Yeah - did actually notice that and try to keep my fingers crossed it would work as HP claim the 4510s Wifi is supported as a driver is available - tried both b43 and ndiswrapper and ndiswrapper crashed the kernel..... anyone know why that might be? I got the correct driver and ndis loaded the device but on modprobe the kernel went into meltdown..... (modprobe worked fine without the driver installed so it sounds like a driver issue....)
ndiswrapper crashed the kernel..... anyone know why that might be?
Did you compile ndiswrapper yourself or did you use a pre-compiled package? That said there are a couple of possible explanations. The most likely is that the Windows driver is one that doesn't work with ndiswrapper. Usually an XP driver works. Vista drivers have been, well, unpredictable as have 64 bit drivers. Try the latest XP driver and if that doesn't work, try some older ones if you can find them.
as HP claim the 4510s Wifi is supported as a driver is available
If HP put Ubuntu on this, you might want to call and yell. I've seen a few threads around here about really poor wireless drivers on HP installed Ubuntu.
Okay - thanks. Definitely shouting at HP as having put Suse Enterprise on not only is the wifi not recognised but the graphics won't go above 800x600 - yet they advertise as Linux supported on Suse.....
Given up on the Broadcom driver for now - its clearly doesn't work on these units. Am trying to get NDISWrapper working as per the standard config. Have tried on a very similar laptop, 2.29 kernel, ndiswrapper rebuilt, Broadcom 4312 and it works. Tried exactly the same config on this HP unit and as soon as I modprobe ndiswrapper the system hangs dead. Any idea what might cause this?
as soon as I modprobe ndiswrapper the system hangs dead. Any idea what might cause this?
It is likely the Windows driver, at least in the past that has usually been the main culprit. What I would do would be to grab the latest stable ndiswrapper and compile it by hand (you need your kernel sources installed for this) and then grab the driver suggested by the ndiswrapper site on Sourceforge. Hopefully that combination will work.
That's what I thought it might be, but I've tried the following with no success:
I have two laptops I've tried, one with a Broadcom 4310 and one a 4312. I've installed the linux 2.29 kernel on both and compiled ndiswrapper from source. Using NDIS wrapper, both use the same driver. The laptop with the 4312 works, the one with the 4310 hangs, despite both using the same ndiswrapper module and the same driver (the only driver that ndiswrapper recognises the device with).
On the one that hangs, I rolled back to 2.24 (Hardy) and used the stock ndiswrapper - same result, just hangs crashing the system....
Don't know if there could be some kind of weird conflict going on in the system internals? All the posts I've read seem to indicate it would be the driver, but then the same driver works on the other system....
The problem is likely a combination of driver and hardware. In other words, the same driver may behave differently when faced with different hardware. If it is any consolation the 4310 has long been a pain in the posterior.
If ndiswrapper isn't going to go, there is still the b43 option. It does require that firmware be installed, but I'm pretty sure there are Ubuntu packages for that.