Great news indeed, but "updated the MINI from the DELL Hardy repos"?
Plain english please - does that mean choosing software update from
within the OS?  Thanks

-- 
Wireless WPA2 consistantly crashes the laptop
https://bugs.launchpad.net/bugs/300784
You received this bug notification because you are a member of OEM
Services QA, which is subscribed to The Dell Mini Project.

Status in Dell Inspiron Mini with Custom Dell UI: Fix Released

Bug description:
Connecting to my workplace internal wireless locks up the Dell Mini 9. Most of 
this I already documented on the Ubuntu forums 
(http://ubuntuforums.org/showthread.php?t=910487&page=72) and I'm just going to 
copy and paste them over. I have access to the access points, and the 
authentication servers and I'm happy to reproduce this as needed to isolate the 
problem.

------------------------------------
First Post:
Finally, and most seriously I can't get onto the wireless at work. It's running 
WPA2 Enterprise, PEAP authentication, EAP-MSCHAP v2 for secondary 
authentication. It locks the Mini hard with on green dot on the network 
manager. The bugger is that I can look at the wireless authentication server 
and I'm logging in successfully according to it but every time I do it hangs my 
mini. I also tried installing 8.10 to see if the network manager was updated 
and could get around this with no love. I reverted back to the Dell remix 
because I like all of my keys to do what their labeled to do. WPA wireless 
works like a champ both at home and on the work guest wireless. Any ideas?

------------------------------------
Second Post:
Quote:
Originally Posted by yakker.yak View Post
Hmmm, no experience myself, but it sounds like a wireless driver issue.
Have you tried with another network manager, such as WCID?

No dice on the WICD idea but I do like it better. Due to the lpia kernel issue 
I reinstalled 8.10 rather than repackage the WICD .deb and risk dependency 
problems. Still hangs in the same place. Mac and Windows notebooks on the same 
network are working fine but this just won't connect. It hangs on "Validating 
authentication" in WICD. Protocol is "PEAP with GTC".

------------------------------------
Third Post:
Quote:
Originally Posted by yakker.yak View Post
That's too bad. This suggests that it's not a network manager issue but more 
likely the wireless driver.

Have you checked Launchpad to see if something related has been filed as a bug? 
Perhaps worthwhile to file as a bug, although if you need your Mini 9 working 
now I realize this is not going to help your immediate problem
I'm leaning towards the wireless drive problem as well. Three more symptoms 
that I identified yesterday for what their worth.
1. The last line in the wicd.log file while I had it in debug mode was "wpa_cli 
result is associated" after which the desktop locked.
2. The keyboard still responds to the brightness controls so something is still 
working under there even if it may only be the hardware and not the OS.
3. Another staff member here has an Asus Eee loaded with Ubuntu and he can 
connect to the secured work wireless so that would suggest that the operating 
system is okay leaving the Dell wireless driver as a likely culprit.

Today's chore is to see if I can get a text only console running and then try 
to associate to the access point that way. That will isolate out X Windows. 
I'll also post something on Launchpad and see what sticks. Any advice is still 
very much appreciated.

------------------------------------
Fourth Post:
 Re: Inspiron Mini 9
My wireless skills are not quite what they should be but after looking into it 
EAP-MSCHAP v2 is different than GTC but they both produce similar results.

I wasn't able to connect to the wireless via the command line but I was able to 
see all sorts of terrible error messages on tty1. I tested with WICD using PEAP 
and GTC, I also tested with Network-Manager using PEAP and EAP-MSCHAP v2, both 
tests produced the same results on tty1.

First there was a huge string of Out of memory, kill process xxxxx messages. 
I'm assuming that these killed all of my active processes on the box. After 
that there was a pause between 30 and 90 seconds and then the screen filled 
again with what I'm assuming is a core dump ending in [224.456542] ---[end 
trace 7ac017cba2be4fca ]---

Does anyone know of a good way to capture this data? I checked the logs after I 
rebooted and found nothing. I suspect that the syslog service is in that first 
batch of processes to get whacked.

_______________________________________________
Mailing list: https://launchpad.net/~oem-qa
Post to     : oem-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~oem-qa
More help   : https://help.launchpad.net/ListHelp

Reply via email to