WiFi stopped working after about one day

[voytas]

This is my first post here, I've been patiently waiting for my Pandora and I have finally received it last Saturday, and this is great, all seemed to be working fine, including WiFi. But suddenly, on the next day WiFi is not working anymore. Below is dmesg log. I have no idea what is wrong, but basically, when I switch WiFi on, led indicator stays off, under Wireless Networks it shows "disconnected". I tried reflashing using the HF5 Beta 4 firmware, no joy, same issue. Could it be possibly hardware issue? Is there any diagnostic I can run? Thanks.


[ 317.735626] Pandora WiFi: Probe started


[ 317.766693] Sending insert event for MMC3...


[ 317.770996] Pandora WiFi: Probe done


[ 317.822052] mmc2: card claims to support voltages below the defined range. These will be ignored.


[ 317.831024] mmc2: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.


[ 317.842803] mmc2: new SDIO card at address 0001


[ 317.938903] wl1251: using dedicated interrupt line


[ 317.939239] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 317.939270] wl1251: ERROR sdio read failed (-84)


[ 317.954254] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 317.954315] wl1251: ERROR sdio read failed (-84)


[ 317.959014] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 317.959045] wl1251: ERROR sdio read failed (-84)


[ 317.963897] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 317.963928] wl1251: ERROR sdio read failed (-84)


[ 317.977661] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 317.977691] wl1251: ERROR sdio read failed (-84)


[ 317.982391] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 317.990692] wl1251: ERROR sdio read failed (-84)


[ 318.009124] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 318.009185] wl1251: ERROR sdio read failed (-84)


[ 318.024536] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 318.024597] wl1251: ERROR sdio read failed (-84)


[ 318.029296] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 318.029327] wl1251: ERROR sdio read failed (-84)


[ 318.034179] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 318.034210] wl1251: ERROR sdio read failed (-84)


[ 318.048004] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 318.048034] wl1251: ERROR sdio read failed (-84)


[ 318.052734] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 318.063629] wl1251: ERROR sdio read failed (-84)


[ 318.068511] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 318.068572] wl1251: ERROR sdio read failed (-84)


[ 318.087036] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 318.087066] wl1251: ERROR sdio read failed (-84)


[ 318.091766] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 318.091796] wl1251: ERROR sdio read failed (-84)


[ 318.096649] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 318.096679] wl1251: ERROR sdio read failed (-84)


[ 318.110473] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 318.110534] wl1251: ERROR sdio read failed (-84)


[ 318.115203] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 318.126037] wl1251: ERROR sdio read failed (-84)


[ 318.274627] phy0: Selected rate control algorithm 'minstrel'


[ 318.275573] wl1251: loaded


[ 318.278320] wl1251: initialized


[ 319.844818] sdio_reset_comm():


[ 319.868560] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 319.868621] wl1251: ERROR sdio read failed (-84)


[ 319.873260] wl1251: ERROR unsupported chip id: 0x3020101


[ 335.337005] sdio_reset_comm():


[ 335.360748] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 335.360778] wl1251: ERROR sdio read failed (-84)


[ 335.365417] wl1251: ERROR unsupported chip id: 0x3020101


[ 335.432189] sdio_reset_comm():


[ 335.442687] mmci-omap mmci-omap.2: MMC IRQ 0x408003 : CC TC ERRI DEB


[ 335.442749] wl1251: ERROR sdio read failed (-84)


[ 335.447479] wl1251: ERROR unsupported chip id: 0x3020101


[ 353.592193] keyboard.c: can't emulate rawmode for keycode 191


[ 353.765869] keyboard.c: can't emulate rawmode for keycode 191

 

[WizardStan]

It does have the feeling of a hardware problem, based on those outputs. Perhaps a loose wire or something.


But maybe it's not, there's some things we can try first. Try pulling the battery out and waiting 10 minutes, give the Pandora time to reset all states to default.

 

[voytas]

It does have the feeling of a hardware problem, based on those outputs. Perhaps a loose wire or something.


But maybe it's not, there's some things we can try first. Try pulling the battery out and waiting 10 minutes, give the Pandora time to reset all states to default.

I have just tried that (removed battery for about 20 mins), but now I cannot find wlan0 device at all (toggling WiFi seems to be doing nothing). It disappeared completely. Like no WiFi at all. Any other ideas?

 

[WizardStan]

I have just tried that (removed battery for about 20 mins), but now I cannot find wlan0 device at all (toggling WiFi seems to be doing nothing). It disappeared completely. Like no WiFi at all. Any other ideas?

Huh. Well, at this point I've got nothing then. If no wlan device is appearing at all that usually means it physically cannot find the device. Unless someone else has an idea, my only suggestion could possibly be to RMA. Sorry.


I believe you may be the first person for whom their wifi is physically broken in this way, so... lucky you?

 

[lordbobjones]

My understanding is that when they test the system, the wifi has to work in order for the unit to flash. I might be wrong. Since it was working and then stopped indicates some other issues.


Let's check a few simple things:


Please forgive the first one... Did you toggle WIFI on after the battery drop? Remember it resets everything.


Second, did you try logging into your router and changing the channel the router is broadcasting on? It took me several tries before I found one that made my Pandora happy. And some channels would work one day and then not the next.


Third, try connecting to another router. Some routers do not play well with the Pandora.

 

[voytas]

My understanding is that when they test the system, the wifi has to work in order for the unit to flash. I might be wrong. Since it was working and then stopped indicates some other issues.


Let's check a few simple things:


Please forgive the first one... Did you toggle WIFI on after the battery drop? Remember it resets everything.


Second, did you try logging into your router and changing the channel the router is broadcasting on? It took me several tries before I found one that made my Pandora happy. And some channels would work one day and then not the next.


Third, try connecting to another router. Some routers do not play well with the Pandora.

I am aware that I have to toggle WiFi, tried that several times (including rebooting, etc), no luck .


In terms of connecting to another router, it is rather difficult if there are no network devices available on my Pandora anymore, it cannot connect to any router as network manager simply shows that there are no networking devices available (and toggling WiFi doesn't change that state). To try another router I would simply need working WiFi device first...


I will try reflashing it later today again as the last resort, but I think it is hardware issue, these errors it reported rather indicate that, and now no wlan0 device at all, it should exists as far as I know.

 

[WizardStan]

There is one other thing to try. Open a terminal and on the command line type

sudo /usr/pandora/scripts/op_wifi.sh

Copy that output into a post here for us to go over. If everything is fine, it should simply say "Starting WL1251 yadda yadda something", but I suspect you will see a lot of errors.

 

[voytas]

There is one other thing to try. Open a terminal and on the command line type

sudo /usr/pandora/scripts/op_wifi.sh

Copy that output into a post here for us to go over. If everything is fine, it should simply say "Starting WL1251 yadda yadda something", but I suspect you will see a lot of errors.

There is just one line it outputs:


Starting WL1251 MAC80211 Wireless LAN driver: wl1251.


And that's it.


and when executed again:


wlan0: unknown interface: No such device

 

[WizardStan]

hmmm. Run that same script one more time, wait a couple of seconds, and then type "dmesg"


That should dump a bunch of information about what it tried to do with the wifi drivers. See if anything especially looks like an error. The last line should be "ADDRCONF(NETDEV_UP):wlan0: link is not ready"

 

[voytas]

Below is dmesg output after running the script. No errors as far as I can tell. And still no WiFi. I think basically WiFi device is not working at all, e.g. not being detected.


] musb_hdrc: hw_ep 2rx, max 512


[ 9.643798] musb_hdrc: hw_ep 3tx, max 512


[ 9.643829] musb_hdrc: hw_ep 3rx, max 512


[ 9.643829] musb_hdrc: hw_ep 4tx, max 512


[ 9.643829] musb_hdrc: hw_ep 4rx, max 512


[ 9.643859] musb_hdrc: hw_ep 5tx, max 512


[ 9.643859] musb_hdrc: hw_ep 5rx, max 512


[ 9.643890] musb_hdrc: hw_ep 6tx, max 512


[ 9.643890] musb_hdrc: hw_ep 6rx, max 512


[ 9.643890] musb_hdrc: hw_ep 7tx, max 512


[ 9.643920] musb_hdrc: hw_ep 7rx, max 512


[ 9.643920] musb_hdrc: hw_ep 8tx, max 512


[ 9.643951] musb_hdrc: hw_ep 8rx, max 512


[ 9.643951] musb_hdrc: hw_ep 9tx, max 512


[ 9.643981] musb_hdrc: hw_ep 9rx, max 512


[ 9.643981] musb_hdrc: hw_ep 10tx, max 512


[ 9.643981] musb_hdrc: hw_ep 10rx, max 512


[ 9.644012] musb_hdrc: hw_ep 11tx, max 512


[ 9.644012] musb_hdrc: hw_ep 11rx, max 512


[ 9.644042] musb_hdrc: hw_ep 12tx, max 512


[ 9.644042] musb_hdrc: hw_ep 12rx, max 512


[ 9.644073] musb_hdrc: hw_ep 13tx, max 512


[ 9.644073] musb_hdrc: hw_ep 13rx, max 512


[ 9.644073] musb_hdrc: hw_ep 14shared, max 1024


[ 9.644104] musb_hdrc: hw_ep 15shared, max 1024


[ 9.644134] musb_hdrc: USB OTG mode controller at d80ab000 using PIO, IRQ 92


[ 9.666442] Bluetooth: Core ver 2.13


[ 9.666870] NET: Registered protocol family 31


[ 9.666870] Bluetooth: HCI device and connection manager initialized


[ 9.666900] Bluetooth: HCI socket layer initialized


[ 9.669982] NET: Registered protocol family 2


[ 9.674102] Switched to high resolution mode on CPU 0


[ 9.736724] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)


[ 9.737274] TCP established hash table entries: 8192 (order: 4, 65536 bytes)


[ 9.737518] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)


[ 9.737640] TCP: Hash tables configured (established 8192 bind 8192)


[ 9.737670] TCP reno registered


[ 9.760162] NET: Registered protocol family 1


[ 9.761474] NetWinder Floating Point Emulator V0.97 (double precision)


[ 9.763702] VFS: Disk quotas dquot_6.5.1


[ 9.763793] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)


[ 9.764343] squashfs: version 4.0 (2009/01/31) Phillip Lougher


[ 9.766448] aufs 2-27


[ 9.766510] msgmni has been set to 485


[ 9.766571] io scheduler noop registered


[ 9.766601] io scheduler anticipatory registered (default)


[ 9.766601] io scheduler deadline registered


[ 9.766754] io scheduler cfq registered


[ 9.788635] Serial: 8250/16550 driver4 ports, IRQ sharing enabled


[ 9.811950] serial8250.0: ttyS0 at MMIO 0x49020000 (irq = 74) is a ST16654


[ 9.811981] console [ttyS0] enabled


[ 10.254974] brd: module loaded


[ 10.262756] loop: module loaded


[ 10.265960] pndctrl loaded.


[ 10.269378] usbcore: registered new interface driver asix


[ 10.275054] usbcore: registered new interface driver cdc_ether


[ 10.281188] usbcore: registered new interface driver rndis_host


[ 10.287231] i2c /dev entries driver


[ 10.292663] input: power-button as /devices/virtual/input/input0


[ 10.322631] triton2 power button driver initialized


[ 10.329162] Driver 'sd' needs updating - please use bus_type methods


[ 10.336120] omap2-nand driver initializing


[ 10.341400] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xbc (Micron NAND 512MiB 1,8V 16-bit)


[ 10.350585] cmdlinepart partition parsing not available


[ 10.355865] Creating 5 MTD partitions on "omap2-nand":


[ 10.361053] 0x00000000-0x00080000 : "xloader"


[ 10.366302] 0x00080000-0x00260000 : "uboot"


[ 10.371826] 0x00260000-0x00280000 : "uboot-env"


[ 10.376953] 0x00280000-0x00c80000 : "boot"


[ 10.385864] 0x00c80000-0x20000000 : "rootfs"


[ 10.604095] UBI: attaching mtd4 to ubi0


[ 10.607971] UBI: physical eraseblock size: 131072 bytes (128 KiB)


[ 10.614318] UBI: logical eraseblock size: 129024 bytes


[ 10.619781] UBI: smallest flash I/O unit: 2048


[ 10.624511] UBI: sub-page size: 512


[ 10.629180] UBI: VID header offset: 512 (aligned 512)


[ 10.635070] UBI: data offset: 2048


[ 11.904937] UBI: attached mtd4 to ubi0


[ 11.908782] UBI: MTD device name: "rootfs"


[ 11.913879] UBI: MTD device size: 499 MiB


[ 11.918884] UBI: number of good PEBs: 3996


[ 11.923614] UBI: number of bad PEBs: 0


[ 11.928131] UBI: max. allowed volumes: 128


[ 11.932800] UBI: wear-leveling threshold: 4096


[ 11.937530] UBI: number of internal volumes: 1


[ 11.942016] UBI: number of user volumes: 1


[ 11.946472] UBI: available PEBs: 0


[ 11.950958] UBI: total number of reserved PEBs: 3996


[ 11.955993] UBI: number of PEBs reserved for bad PEB handling: 39


[ 11.962097] UBI: max/mean erase counter: 20/6


[ 11.966522] UBI: image sequence number: 1978485972


[ 11.971405] UBI: attaching mtd3 to ubi1


[ 11.975250] UBI: physical eraseblock size: 131072 bytes (128 KiB)


[ 11.981597] UBI: logical eraseblock size: 129024 bytes


[ 11.987030] UBI: smallest flash I/O unit: 2048


[ 11.991760] UBI: sub-page size: 512


[ 11.996429] UBI: VID header offset: 512 (aligned 512)


[ 12.002319] UBI: data offset: 2048


[ 12.009155] UBI: background thread "ubi_bgt0d" started, PID 355


[ 12.052246] UBI: attached mtd3 to ubi1


[ 12.056030] UBI: MTD device name: "boot"


[ 12.061004] UBI: MTD device size: 10 MiB


[ 12.065948] UBI: number of good PEBs: 79


[ 12.070495] UBI: number of bad PEBs: 1


[ 12.074981] UBI: max. allowed volumes: 128


[ 12.079620] UBI: wear-leveling threshold: 4096


[ 12.084381] UBI: number of internal volumes: 1


[ 12.088867] UBI: number of user volumes: 1


[ 12.093353] UBI: available PEBs: 0


[ 12.097839] UBI: total number of reserved PEBs: 79


[ 12.102661] UBI: number of PEBs reserved for bad PEB handling: 2


[ 12.108703] UBI: max/mean erase counter: 10/6


[ 12.113128] UBI: image sequence number: 1390175686


[ 12.117950] usbmon: debugfs is not available


[ 12.122650] ehci-omap ehci-omap.0: OMAP-EHCI Host Controller


[ 12.128540] UBI: background thread "ubi_bgt1d" started, PID 358


[ 12.134765] ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1


[ 12.142608] ehci-omap ehci-omap.0: irq 77, io mem 0x48064800


[ 12.158386] ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004


[ 12.166564] usb usb1: configuration #1 chosen from 1 choice


[ 12.172485] hub 1-0:1.0: USB hub found


[ 12.176361] hub 1-0:1.0: 3 ports detected


[ 12.284637] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002


[ 12.291534] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1


[ 12.298797] usb usb1: Product: OMAP-EHCI Host Controller


[ 12.304168] usb usb1: Manufacturer: Linux 2.6.27.46-omap1 ehci_hcd


[ 12.310394] usb usb1: SerialNumber: ehci-omap.0


[ 12.315277] Initializing USB Mass Storage driver...


[ 12.320434] usbcore: registered new interface driver usb-storage


[ 12.326538] USB Mass Storage support registered.


[ 12.331481] usbcore: registered new interface driver libusual


[ 12.337799] mice: PS/2 mouse device common for all mice


[ 12.362518] input: gpio-keys as /devices/platform/gpio-keys/input/input1


[ 12.432830] input: keypad as /devices/platform/i2c_omap.1/i2c-adapter/i2c-1/1-004a/twl4030_keypad/input/input2


[ 12.496429] input: nub0 as /devices/platform/i2c_omap.3/i2c-adapter/i2c-3/3-0066/input/input3


[ 12.557647] input: nub1 as /devices/platform/i2c_omap.3/i2c-adapter/i2c-3/3-0067/input/input4


[ 12.620330] twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0


[ 12.631408] bq27x00-battery 3-0055: support ver. 1.1.0 enabled


[ 12.637664] Bluetooth: HCI UART driver ver 2.2


[ 12.642150] Bluetooth: HCI H4 protocol initialized


[ 12.647033] Bluetooth: HCILL protocol initialized


[ 12.651855] hci_h4p hci_h4p: Registering HCI H4P device


[ 12.807800] mmci-omap mmci-omap.0: Failed to get debounce clock


[ 12.916351] mmci-omap mmci-omap.1: Failed to get debounce clock


[ 12.917358] mmci-omap mmci-omap.2: Failed to get debounce clock


[ 12.918212] Registered led device: pandora::sd1


[ 12.923065] Registered led device: pandora::sd2


[ 12.927947] Registered led device: pandora::bluetooth


[ 12.933349] Registered led device: pandora::wifi


[ 12.938781] Registered led device: pandora::keypad_bl


[ 12.944244] Registered led device: pandora:ower


[ 12.949493] Registered led device: pandora::charger


[ 12.954956] usbcore: registered new interface driver usbhid


[ 12.960632] usbhid: v2.6:USB HID core driver


[ 12.965454] Advanced Linux Sound Architecture Driver Version 1.0.17.


[ 12.972320] ASoC version 0.13.2


[ 12.975799] OMAP3 Pandora SoC init


[ 12.979614] TWL4030 Audio Codec init


[ 12.984802] asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok


[ 12.991760] asoc: twl4030 <-> omap-mcbsp-dai-1 mapping ok


[ 13.006011] ALSA device list:


[ 13.009002] #0: omap3pandora (twl4030)


[ 13.013275] TCP cubic registered


[ 13.016540] NET: Registered protocol family 17


[ 13.021087] NET: Registered protocol family 15


[ 13.025634] Bluetooth: L2CAP ver 2.11


[ 13.029296] Bluetooth: L2CAP socket layer initialized


[ 13.034423] Bluetooth: SCO (Voice Link) ver 0.6


[ 13.039001] Bluetooth: SCO socket layer initialized


[ 13.044067] Bluetooth: RFCOMM socket layer initialized


[ 13.049316] Bluetooth: RFCOMM TTY layer initialized


[ 13.054229] Bluetooth: RFCOMM ver 1.10


[ 13.058074] Bluetooth: BNEP (Ethernet Emulation) ver 1.3


[ 13.063415] Bluetooth: HIDP (Human Interface Emulation) ver 1.2


[ 13.069915] RPC: Registered udp transport module.


[ 13.074707] RPC: Registered tcp transport module.


[ 13.079467] ThumbEE CPU extension supported.


[ 13.083831] Disabling unused clock "sr2_fck"


[ 13.083831] Disabling unused clock "sr1_fck"


[ 13.083862] Disabling unused clock "mcbsp_fck"


[ 13.083862] Disabling unused clock "mcbsp_fck"


[ 13.083892] Disabling unused clock "mcbsp_fck"


[ 13.083892] Disabling unused clock "mcbsp_ick"


[ 13.083892] Disabling unused clock "mcbsp_ick"


[ 13.083923] Disabling unused clock "mcbsp_ick"


[ 13.083923] Disabling unused clock "gpt2_ick"


[ 13.083953] Disabling unused clock "gpt3_ick"


[ 13.083953] Disabling unused clock "gpt4_ick"


[ 13.083984] Disabling unused clock "gpt5_ick"


[ 13.083984] Disabling unused clock "gpt6_ick"


[ 13.084014] Disabling unused clock "gpt7_ick"


[ 13.084014] Disabling unused clock "gpt8_ick"


[ 13.084014] Disabling unused clock "gpt9_ick"


[ 13.084045] Disabling unused clock "wdt3_ick"


[ 13.084045] Disabling unused clock "wdt3_fck"


[ 13.084075] Disabling unused clock "gpio2_dbck"


[ 13.084075] Disabling unused clock "gpio3_dbck"


[ 13.084106] Disabling unused clock "gpio5_dbck"


[ 13.084106] Disabling unused clock "gpt9_fck"


[ 13.084136] Disabling unused clock "gpt8_fck"


[ 13.084136] Disabling unused clock "gpt7_fck"


[ 13.084167] Disabling unused clock "gpt6_fck"


[ 13.084167] Disabling unused clock "gpt5_fck"


[ 13.084167] Disabling unused clock "gpt4_fck"


[ 13.084197] Disabling unused clock "gpt3_fck"


[ 13.084197] Disabling unused clock "gpt2_fck"


[ 13.084228] Disabling unused clock "gpt1_ick"


[ 13.084228] Disabling unused clock "wdt1_ick"


[ 13.084259] Disabling unused clock "wdt2_ick"


[ 13.084259] Disabling unused clock "wdt2_fck"


[ 13.084289] Disabling unused clock "gpio1_dbck"


[ 13.084289] Disabling unused clock "gpt1_fck"


[ 13.084320] Disabling unused clock "cam_ick"


[ 13.084320] Disabling unused clock "cam_mclk"


[ 13.084320] Disabling unused clock "des1_ick"


[ 13.084350] Disabling unused clock "sha11_ick"


[ 13.084350] Disabling unused clock "rng_ick"


[ 13.084381] Disabling unused clock "aes1_ick"


[ 13.084381] Disabling unused clock "ssi_ick"


[ 13.084411] Disabling unused clock "mailboxes_ick"


[ 13.084411] Disabling unused clock "mcbsp_ick"


[ 13.084411] Disabling unused clock "mcbsp_ick"


[ 13.084442] Disabling unused clock "gpt10_ick"


[ 13.084442] Disabling unused clock "gpt11_ick"


[ 13.084472] Disabling unused clock "uart2_ick"


[ 13.084472] Disabling unused clock "i2c_ick"


[ 13.084503] Disabling unused clock "hdq_ick"


[ 13.084503] Disabling unused clock "mspro_ick"


[ 13.084503] Disabling unused clock "des2_ick"


[ 13.084533] Disabling unused clock "sha12_ick"


[ 13.084533] Disabling unused clock "aes2_ick"


[ 13.084564] Disabling unused clock "icr_ick"


[ 13.084564] Disabling unused clock "pka_ick"


[ 13.084594] Disabling unused clock "ssi_ssr_fck"


[ 13.084594] Disabling unused clock "hdq_fck"


[ 13.084594] Disabling unused clock "uart2_fck"


[ 13.084625] Disabling unused clock "mcbsp_fck"


[ 13.084625] Disabling unused clock "mcbsp_fck"


[ 13.084655] Disabling unused clock "i2c_fck"


[ 13.084655] Disabling unused clock "mspro_fck"


[ 13.084686] Disabling unused clock "gpt11_fck"


[ 13.084686] Disabling unused clock "gpt10_fck"


[ 13.084716] Disabling unused clock "iva2_ck"


[ 13.084716] Disabling unused clock "dpll4_m6x2_ck"


[ 13.084747] Disabling unused clock "dpll4_m5x2_ck"


[ 13.084747] Disabling unused clock "dpll3_m3x2_ck"


[ 13.084777] Disabling unused clock "sys_clkout1"


[ 13.084808] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1


[ 13.124603] Console: switching to colour frame buffer device 100x30


[ 13.309234] twl4030_rtc twl4030_rtc: setting system clock to 2011-02-09 18:54:18 UTC (1297277658)


[ 13.411407] UBIFS: mounted UBI device 0, volume 0, name "rootfs"


[ 13.417541] UBIFS: file system size: 508612608 bytes (496692 KiB, 485 MiB, 3942 LEBs)


[ 13.425598] UBIFS: journal size: 9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)


[ 13.432983] UBIFS: media format: w4/r0 (latest is w4/r0)


[ 13.438842] UBIFS: default compressor: lzo


[ 13.442993] UBIFS: reserved for root: 0 bytes (0 KiB)


[ 13.449340] VFS: Mounted root (ubifs filesystem).


[ 13.454193] Freeing init memory: 148K


[ 20.396881] ads7846 spi1.0: touchscreen, irq 254


[ 20.402252] input: touchscreen as /devices/platform/omap2_mcspi.1/spi1.0/input/input5


[ 24.975341] UBIFS: mounted UBI device 1, volume 0, name "boot"


[ 24.981292] UBIFS: file system size: 8257536 bytes (8064 KiB, 7 MiB, 64 LEBs)


[ 24.988677] UBIFS: journal size: 1032193 bytes (1008 KiB, 0 MiB, 6 LEBs)


[ 24.995971] UBIFS: media format: w4/r0 (latest is w4/r0)


[ 25.001831] UBIFS: default compressor: lzo


[ 25.005981] UBIFS: reserved for root: 390023 bytes (380 KiB)


[ 26.362213] input: nub0 as /devices/platform/i2c_omap.3/i2c-adapter/i2c-3/3-0066/input/input6


[ 26.604431] input: nub1 as /devices/platform/i2c_omap.3/i2c-adapter/i2c-3/3-0067/input/input7


[ 160.519165] NET: Registered protocol family 10


[ 329.589324] keyboard.c: can't emulate rawmode for keycode 185


[ 329.653839] keyboard.c: can't emulate rawmode for keycode 185


[ 340.032043] Generic kernel compatibility enabled based on linux-next next-20100113


[ 340.283630] cfg80211: Calling CRDA to update world regulatory domain


[ 340.923004] lib80211: common routines for IEEE802.11 drivers


[ 340.928863] lib80211_crypt: registered algorithm 'NULL'


[ 340.961791] lib80211_crypt: registered algorithm 'TKIP'


[ 340.992370] lib80211_crypt: registered algorithm 'WEP'


[ 341.023193] lib80211_crypt: registered algorithm 'CCMP'


[ 341.156005] Pandora WiFi: Probe started


[ 341.181854] Sending insert event for MMC3...


[ 341.186157] Pandora WiFi: Probe done

 

[WizardStan]

[ 341.156005] Pandora WiFi: Probe started


[ 341.181854] Sending insert event for MMC3...


[ 341.186157] Pandora WiFi: Probe done

If it were working at all (even incorrectly) there would be more after that. It installs the wifi driver, and triggers an "insert" event which should force the wifi to start connecting, but as we can see there is nothing, not even an error. That probably means it didn't detect any device on MMC3. I'm out of ideas again.

 

[notaz]

Yeah the module doesn't respond at all, as if it wasn't there.

 

[moxie]

This sounds a bit similar to my problem, actually...

 

[voytas]

Ok, since it really looks like hardware issue and there are no more ideas, I have requested RMA. And thanks for your help anyway, I simply must be unlucky .

 

[manutdnsubi]

Have you found anything out about your wifi issue? I am having the same problem. My wifi was spotty for a few days and now nothing happens when I switch it on. I tried to activate using the script above and got the same results. I tried taking the battery out for 20 minutes and I have tried flashing HF5 RC1 but I still get the same problem. Any help would be much appreciated!


ps I have not opened the pandora to do any hardware changes nor have I messed with the software other than to play roms.

 

[voytas]

Have you found anything out about your wifi issue? I am having the same problem. My wifi was spotty for a few days and now nothing happens when I switch it on. I tried to activate using the script above and got the same results. I tried taking the battery out for 20 minutes and I have tried flashing HF5 RC1 but I still get the same problem. Any help would be much appreciated!


ps I have not opened the pandora to do any hardware changes nor have I messed with the software other than to play roms.

No, it is still not working at all. Initially it was working fine, then I switched it off and next day it was not working, I haven't started using it before it failed, just browsing web, basic stuff. So I will be sending it back...

 

[Trip]

Sorry for digging up an old thread but I've got this same problem.

Did ED ever find out what the matter was when you R.M.A'd your device?