Ticket #1939 (assigned defect)

Opened 10 years ago

Last modified 10 years ago

wifi crashes the device

Reported by: gawlitza Owned by: marek
Priority: normal Milestone: Om2008.9
Component: unknown Version: Om2008.9-dev
Severity: major Keywords:
Cc: Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: PatchReviewResult:
Reproducible: always

Description

After upgrade to last 2008.8 update from 31.08.2008: If I configure wifi with encryption key the system hangs up immediatly after setting the proper essid. System is really dead. Must remove and replace battery to get it restarted.

Change History

comment:1 Changed 10 years ago by tick

  • Owner changed from julian_chu to marek
  • Status changed from new to assigned

comment:2 Changed 10 years ago by marek

  • Component changed from Distro to unknown
  • Severity changed from critical to major

You upgraded using opkg update && opkg upgrade ? Could you try a plain install of the image and the latest kernel and try again ?

comment:3 Changed 10 years ago by emartini

I observed something similar. Each rootfs after 2008-08-29 let's authentication fail and finally leads to a frozen condition (after several auth attempts) if you won't swith of WiFi?.
Update was made via full flashing of kernel and rootfs.

comment:4 Changed 10 years ago by wendy_hung

Hi, could you please make this ticket more clear?
Like which day's kernel/root file system, can this reproducible? is that still happening?

Reread this again: https://docs.openmoko.org/trac/wiki/NewTicket

Thank you.

comment:5 Changed 10 years ago by gawlitza

Hi Marek,
answering your question via mail does not work (mail returned with not known address).
The hang occurs if you want to establish a wep-key-secured wlan-connection. It occurs NOT with unsecured wlan. If you disable wep-key security in the router and let the wep key in iwconfig empty, then wifi works and you can install packages and so on ! If you set wep-key with iwconfig and then - which is necessary - set the proper essid, then system freezes, you must remove all plugs and battery to reboot. Therefore I think this is a kernel / kernel-module / driver problem, and not a problem of applications in rootfs. This is reproducable every time I tried.
I have frerunner full-flashed with Om2008.8-gta02-20080903.uImage.bin and Om2008.8-gta02-20080904.rootfs.jffs2.
Greatings M. Gawlitza

comment:6 follow-up: ↓ 7 Changed 10 years ago by marek

Currently, we are digging into the wifi stuff to debug the driver. Om2008.8 has problems with unsecured networks as well but we could trace it down. I think we can fix that one soon. We move on to WEP networks now. We will come up with an instruction to narrow down the issue. I guess Werner will post it somewhere. We highly appreciate your help.
My mail address (marek@…) should work - others can mail me. :-)

comment:7 in reply to: ↑ 6 Changed 10 years ago by chenna

I have flashed the device with Om2008.8.uImage.bin & Om2008.8.rootfs.jffs2

available at http://downloads.openmoko.org/releases/Om2008.8/.

I could not find the file /etc/volatives.cache but I could find /etc/volatile.cache and deleted this file and rebooted. But still I see wIFI unknown.

I have seen the ticket 1734 and there I found th following info:

I could not locate openmoko-openmoko-qtopia-x11-image-glibc-ipk--20080806-om-gta02.rootfs.jffs2.

Please share the working image for WIFI, USB networking and Blue tooth.

Please let me know the path where to download the working image for WIFI, USB networking and Bluetooth.

Thankyou

Replying to mattt:

Just in the interest of completeness, I reflashed the old rootfs...

openmoko-openmoko-qtopia-x11-image-glibc-ipk--20080806-om-gta02.rootfs.jffs2
still using the 20080808 kernel.

wifi works
usb works
carrier is detected.

So I don't think it's the kernel.
And it isn't he hardware.

Replying to marek:

Currently, we are digging into the wifi stuff to debug the driver. Om2008.8 has problems with unsecured networks as well but we could trace it down. I think we can fix that one soon. We move on to WEP networks now. We will come up with an instruction to narrow down the issue. I guess Werner will post it somewhere. We highly appreciate your help.
My mail address (marek@…) should work - others can mail me. :-)

Note: See TracTickets for help on using tickets.