She's dead Jim..

[sm0kew0n]

Well, not really.

I stupidly let the battery go flat while it (1Ghz) was on standby, after charging and turning on it segfaulted and dropped to the console, after which I rebooted and it loaded SZ fine. But, now wifi can't be turned on from the gui.

I can get wifi from the terminal with -

/etc/init.d/wl1251-init start

Here is pndrun_op_wifi.out -

=======================================================================================
PND             : /usr/pandora/apps/op_wifi.pnd
PND_FSTYPE      : Squashfs
APPDATADIR      : //pandora/appdata/op_wifi
APPDD_FSTYPE    : rootfs
PND_CPUSPEED    : <unset>
EXENAME         : op_wifi.sh
ARGUMENTS       : <unset>
=======================================================================================
[ START ]--- Mount the PND ----------
Mounting : mount -t squashfs -o ro "/dev/loop0" "/mnt/utmp/op_wifi"
Mounting the Union FS : mount -t aufs -o exec,dirs="//pandora/appdata/op_wifi=rw+nolwh":"/mnt/pnd/op_wifi=rr" none "/mnt/utmp/op_wifi"
mount: wrong fs type, bad option, bad superblock on none,
       missing codepage or helper program, or other error
       (for several filesystems (e.g. nfs, cifs) you might
       need a /sbin/mount.<type> helper program)
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

WARNING : mount faild, re-tring
mount: wrong fs type, bad option, bad superblock on none,
       missing codepage or helper program, or other error
       (for several filesystems (e.g. nfs, cifs) you might
       need a /sbin/mount.<type> helper program)
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

ERROR: The Union File-system is not mounted !
+++++++
Loopback devices :
/dev/loop0: [000e]:16985 (/usr/pandora/apps/op_wifi.pnd)
Are mounted on :
/dev/loop0 on /mnt/utmp/op_wifi type squashfs (ro,relatime)
For these Union :
ERROR: The Union File-system is not mounted !
+++++++
Loopback devices :
/dev/loop0: [000e]:16985 (/usr/pandora/apps/op_wifi.pnd)
Are mounted on :
/dev/loop0 on /mnt/utmp/op_wifi type squashfs (ro,relatime)
For these Union :
[ FAILED]--- Mount the PND ----------
=======================================================================================
Return code is : 8

So I checked the mounts -

rootfs on / type rootfs (rw)
ubi0:rootfs on / type ubifs (rw,relatime,bulk_read)
devtmpfs on /dev type devtmpfs (rw,relatime,size=222052k,nr_inodes=55513,mode=755)
proc on /proc type proc (rw,relatime)
tmpfs on /mnt/.splash type tmpfs (rw,relatime,size=40k)
sysfs on /sys type sysfs (rw,relatime)
none on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
gvfs-fuse-daemon on /home/admin/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=1000,group_id=1001)
/dev/loop0 on /mnt/utmp/op_wifi type squashfs (ro,relatime)
/dev/mmcblk1p1 on /media/32 type vfat (rw,dirsync,noatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/mmcblk0p2 on /media/apps type vfat (rw,dirsync,noatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/mmcblk0p1 on /media/system type ext2 (rw,dirsync,noatime,errors=continue)

and op_wifi appears to be mounted at /dev/loop0 so here is dmesg -

[ 3946.581329] EXT3-fs (mmcblk0): error: can't find ext3 filesystem on dev mmcblk0.
[ 3946.582489] EXT2-fs (mmcblk0): error: can't find an ext2 filesystem on dev mmcblk0.
[ 3946.583679] FAT-fs (mmcblk0): bogus number of reserved sectors
[ 3946.583831] FAT-fs (mmcblk0): Can't find a valid FAT filesystem
[ 3946.584655] SQUASHFS error: Can't find a SQUASHFS superblock on mmcblk0
[ 3947.899749] EXT2-fs (mmcblk0p1): warning: mounting unchecked fs, running e2fsck is recommended
[ 3960.438842] aufs test_add:294:mount[2806]: uid/gid/perm /mnt/pnd/op_wifi 1000/1000/0755, 0/0/0777
[ 3960.439025] aufs au_xino_create:769:mount[2806]: xino doesn't support /tmp/.aufs.xino(ubifs)
[ 3962.470672] aufs test_add:294:mount[2813]: uid/gid/perm /mnt/pnd/op_wifi 1000/1000/0755, 0/0/0777
[ 3962.471343] aufs au_xino_create:769:mount[2813]: xino doesn't support /tmp/.aufs.xino(ubifs)

So those last 4 lines appear to point to the problem, what is the problem???? (aside from user error )

Cheers.

 

[alxm]

The last log block seems to hint at SD card issues (mmcblk0), what happens if you boot with no cards inserted?

Or maybe something else was corrupted in the OS when the unit lost power, I'd try reflashing to rule out anything like that. Good luck!

 

[FBnil]

Very rarely, a /tmp/directory suddenly becomes a /tmp/file after corruption. Deleting the /tmp/file solves it. In that line, move /pandora/appdata/op_wifi/ out of the way.

What happens when you bootstrap it?

# become root
sudo su
# start wifi
/etc/init.d/wl1251-init start

and to stop it(also as root):

ifconfig wlan0 down
rmmod board_omap3pandora_wifi

 

[levi]

Very rarely, a /tmp/directory suddenly becomes a /tmp/file after corruption.

IIRC the /tmp folder is mounted as tmpfs (which is a RAM FS) and not union mounted, so a /tmp/file should just disappear when the system mounts that tmpfs over the top of it. Thinking it through, you could actually lose quite a lot of space on your root partition, especially if you've landed up with big stuff under /dev/shm or /sys/kernel/debug somehow, which would actually be quite hard to debug from a live mounted system - you'd probably need to boot from live media to figure out it's even there, eating up your disc space.

 

[sm0kew0n]

..what happens if you boot with no cards inserted?

I noticed that too, popped the cards out and the behaviour is the same.

move /pandora/appdata/op_wifi/ out of the way

Nope, changes nothing, a bit different if I become root (sudo su) and start wifi, in this case it appears to start but the led fails to come on but sudo as user starts wifi, led an all....?

One other thing I noticed was that op_wifi in /mnt/utmp has different ownership than all the other directories, i.e. admin wheel instead of root root. Probably nothing...

I don't want to reflash but feel it looming.

[edit] I won't go into sleep/standby either.

 

[levi]

IIRC all files in /usr/pandora/scripts should be owned root:root and have the suid bit set. May be worth checking that.

I wouldn't worry about the ownership of anything in /mnt/utmp. That depends on your user when you pnd_ran things, and won't survive a reboot anyway.

 

[sm0kew0n]

Okay I got fed up and downloaded SZ 1.76 and the trouble continues...

reading boot.scr

5190852 bytes read
## Executing script at 82000000
Wrong image format for "source" command
script failed

This is what I get after extracting to an SD card, I checked md5 and it's all good.

I don't want to post in 1.76 release thread until I know the problem is not related to the original debacle.

 

[levi]

After extracting? You mean after extracting, ejecting the card, plugging it into your pandora and rebooting (possibly holding down the R button) ? It's an error from the pandora, not the machine you're extracting on (although I dare say you could do it on Pandora, I've just never done that yet).

This is sounding more like a hardware issue than a software issue to me, although I guess we still need to exclude the possibility of user error. FWIW, I've let the battery run out on my Pandora by accident many times, and it's never done anything like this to me.

How did you unpack it out of interest? I suppose a line ending issue could cause something like this.

 

[sm0kew0n]

I guess we still need to exclude the possibility of user error

err, never exclude that. I just tried another SD card and it went through, I'll see myself out...

thanks levi.