[GUTSY]Computer freeze when machine boot up with 8180L wireless plugged in

[Eddy]

After upgrading from feisty to gutsy, with ndiswrapper and driver for 8180L driver already installed, the machine booting process freezes as soon as it reaches the point where it tries to connect to the wireless router (i.e. after it asks the key ring password).

This consistently happens. When it happens, the CAP LOCK light is blinking and everything stops working. Have to force the machine down.

ProblemType: Bug
Architecture: i386
Date: Sun Oct 28 16:52:55 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/yelp
Package: yelp 2.20.0-0ubuntu3
PackageArchitecture: i386
ProcCmdline: yelp
ProcCwd: /home/eddy
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: yelp
Uname: Linux eddy-laptop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

[Andres Mujica (andres.mujica)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in ndiswrapper.

But it would be nice if you can give us some additional info as is described here:

https://wiki.ubuntu.com/DebuggingHardwareDetection

[Andres Mujica (andres.mujica)]

Also try this suggestions

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/16247/comments/1

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/16247/comments/4

and this

https://wiki.ubuntu.com/DebuggingSystemCrash

Please help us recollecting this info so we can address this issue.

[Andres Mujica (andres.mujica)]

this could be a duplicate from

https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/132657

waiting for additional info to decide this.

Thanks

[Eddy (tretriluxana-s)]

Here are the log files as suggested. Let me know if anything else are needed.

[Andres Mujica (andres.mujica)]

Ok that's great thanks,

please help us with this info

WITHOUT THE CARD PLUGGED

sudo lsmod

WITH THE CARD PLUGGED

sudo lsmod

sudo dpkg -l | grep ndis

Also if you cand add the DebuggingsystemCrash info page would be good.

Thanks

[Eddy (tretriluxana-s)]

Here are the requested info.

[Andres Mujica (andres.mujica)]

Hi Eddy , thanks for your info.

I believe there's some things going on here, so i need your help in order to testing this.

Also this seems to be a duplicate of bug #132657

Can you provide me with this info?

sudo modinfo rtl8180
sudo find /lib/modules/`uname -r` | grep rtl8180

Also, -and probably you wouldn't like this-, can you uninstall ndiswrapper in order to check if you can put your rtl8180 to work without using ndiswrapper??

I believe there's some kind of conflict there.

And a last favor, can you check the bug i've mentioned before in order to determine if is a duplicate bug??

Thanks

[Eddy (tretriluxana-s)]

Attached is the output log for the command you suggested. It also contains my current modprobe's blacklist.

This RTL8180 has never worked out of the box with Ubuntu (Feisty). I always had to use ndiswrapper. It appears that the native module that comes with it doesn't like it or something. In fact I had to blacklist it in order to get the ndiswrapper thing to work. Note that the card I have is the ver 4.0 which is one of those problematic one.

I think the funny thing about this is that the problem happens only when I leave the card plugged and boot up the machine. If I don't have the card plugged, the machine boots just fine. And when the boot is complete and I plugged in the card, everything works just fine as before. Something seems to be going on during the machine boot up. Also note that it happens only happen when all the X graphic things are already up and running. It's right after I supply the password to the key ring thing so the driver can get the passcode to connect to the network.

I don't think the bug 132657 is a duplicate of this. In that one the card doesn't work at all. For this one, it works fine but only that boot time that has problem.

[Ben James (something-for-the-pain)]

I have experienced the same kernel panic as many others when using the rtl8180 driver and ndiswrapper on Ubuntu 7.10.

After some searching I have found a number of duplicate bugs, so I thought it wise to add a comment to each with references to the others, such that once the bug is fixed all bug reports can be updated and/or consolidated.

Here are the open bugs I could find:

#164937 - new, undecided importance, unassigned
#158176 - incomplete, undecided importance, SEAQ - Andres Mujica
#132657 - incomplete, medium importance, unassigned

[Andres Mujica (andres.mujica)]

I'm not marking this as a dupe of the ben's list as explained by Eddy, but this must be relates somehow, so thanks Ben for pointing those out.

[Barak (barak-naveh)]

Started happening after upgrading from 9.04 to 9.10. I have an ancient Sharp AR10 running Xubuntu with Edimax Wireless LAN cardbus model EW-7108PCg.

any ideas? workarounds?

[Barak (barak-naveh)]

btw, it happens sporadically, took me a bit to realize it's the wireless card. when i take out the card, the system usually recovers. then i can plug it back and continue to use it for some time, unti l the next hang.

[Przemek K. (azrael)]

Barak:
which driver are you using?
ndiswrapper? rtl8180?
or are you using the official driver from Edimax?
http://www.edimax.co.uk/en/support_detail.php?pd_id=5&pl1_id=1&pl2_id=44

Please test the latest Ubuntu 10.04, especially with the rtl8180 driver as ndiswrapper is not recommended.

[Barak (barak-naveh)]

Thanks.
Already gave that computer away to someone, but will suggest her to upgrade to 10.04.
She is not tech, so she will wait for 10.04 to come out of beta.

[Przemek K. (azrael)]

Ubuntu 10.04 has been released some time ago. Did you managed to test it?

[Barak (barak-naveh)]

No, the computer died, but thanks much for following up on this.

[Przemek K. (azrael)]

In that case I'm closing this bug. Feel free to reopen it if you encounter this problem again, and feel free to report more bugs in the future.
https://help.ubuntu.com/community/ReportingBugs