Wireless dead with next kernel

gene heskett gheskett at wdtv.com
Mon Aug 29 11:59:20 UTC 2011


On Monday, August 29, 2011 07:15:04 AM Nils Kassube did opine:

> gene heskett wrote:
> > This is probably the wrong list,
> 
> Why? I don't think so. Granted, you might get a wider audience on the
> ubuntu-users list because the problem isn't Kubuntu specific, but IMHO
> this list is fine.
> 
> > the machine is a lappy with 10.04
> > LTS plus all of the older KDE-4.5.4 installed.  I am going to try to
> > make kmail work for an out of state trip the end of the week.
> > 
> > The updater installed a slightly newer kernel from the Lucid LTS
> > repo's, but when I reboot to it, the wireless is dead, I assume
> > because ndiswrapper doesn't load the dongles needed bcmwlhigh5.xx
> > driver.  But if I try to reinstall it again, ndiswrapper says its
> > already installed.
> 
> Did you remove the remains from the old ndiswrapper version before you
> installed the new one like it is explained at [1]?
> 
Yes, but I did not repeat that for the newer kernel, which having slept on 
it, is probably related.

AND after doing a fresh make install from the ndiswrapper-1.56 src tree, I 
will have to move ndiswrapper.ko to the proper location in the /lib/modules 
tree also since the ndiswrapper-1.56 'make install' script puts the .ko in 
the wrong place.  It puts it in the misc/wireless path, when it apparently 
needs to be in the kernel/drivers/net/wireless subdir.
So I expect I can fix it this morning once I input enough coffee and a 
muffin & find enough clothes to legally walk around in the back yard where 
the machine shop is located.

Apparently this bit of corrective use of mc's F6 button will be needed 
everytime a kernel is updated.  I don't have that problem on the milling 
machine's LTS install as its net is wired, AND the kernel version frozen by 
its use of the RTAI engine, so this caught me a bit off guard.

So, to those who, because your hardware is too new for LTS, build 
ndiswrapper "out of tree" from the tarball, either fix the Makefile, or 
move the .ko to where the system thinks it is supposed to be once the make 
install has been done.  And I don't know enough about fixing Makefile's.

> > I can back up to the slightly older kernel, a
> > 2.6.32-22 IIRC, and it all works perfectly and as fast as my cable
> > circuit allows.
> > 
> > The newer kernel is a 2.6.32-34 IIRC.
> 
> Please check the kernel version with the command
> 
> uname -r
> 
> in a terminal (konsole). If it is really 2.6.32-34, then you probably
> have the lucid-proposed repository enabled. I'm not so sure if that is a
> 
> good idea - from [2]:

Possibly, I was trying to avoid the out of tree build.

> | "Pre-released Updates" enables the Proposed repository, which is the
> | testing area for updates. This repository is recommended only to
> | those interested in helping to test updates and provide feedback.
> 
> So if it really is the 2.6.32-34 kernel, you may consider to file a bug
> report [3]. Then I would propose to first install the 2.6.32-33 kernel
> which comes from lucid-updates or lucid-security. Finally disable the
> lucid-proposed repository and uninstall the 2.6.32-34 kernel. Of course
> I can't tell you if your wireless would work with the 2.6.32-33 kernel
> because I don't have that hardware.

It does, but ndiswrapper is too old.  IMO the real solution would be to 
allow the LTS wireless tree to track modern (read that as "available at 
Staples") hardware.  ndiswrapper-1.54 is rather hopelessly old, and to be 
complete (security crap still doesn't work), so should the iw-tools things.  

Since that radio is not in an alu sided house, it can usually find 11 to 13 
other 'cel's when a scan is done.  Being forced to run it open, not even 
wep works with the state of the iw stuff in LTS, which is to me a far 
bigger security hole than anything they may or may not have patched in the 
-34 kernel.

But I don't expect that attitude would win me any friends at cannon* 
either.  :(  To them I am just another crotchety old fart.

> > While I am here, what key combo brings up the early grub bootfile
> > selection screen?
> 
> From [4]:
> | Hold down SHIFT to display the menu during boot. In certain cases,
> | pressing the ESC key may also display the menu.

Shift key? (shakes head in wonderment)  Thanks, the ESC doesn't work, that 
is the 'normal' key for that, but of course the *buntu's just have to be 
different.  They also steal F-key strokes from mc to pop up a worthless 
menu for something completely unrelated, making you run mc with a ^%$#@& 
mouse!  What a PIMA drag that is. :(

You can tell I've been running linux a long time, since RH5.0 TBE.

Thanks, Nils.
> 
> [1]
> <https://help.ubuntu.com/community/WifiDocs/Driver/Ndiswrapper#Compiling
> %20the%20latest%20version%20of%20ndiswrapper> [2]
> <https://help.ubuntu.com/community/Repositories/Kubuntu>
> [3] <https://help.ubuntu.com/community/ReportingBugs>
> [4] <https://help.ubuntu.com/community/Grub2>


Cheers, gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://204.111.67.138:85/gene>
Just give Alice some pencils and she will stay busy for hours.



More information about the kubuntu-users mailing list