Nubs And Date/time Settings Shortcuts Don't Work


Eniko

Eniko

Raving Python fangirl
Joined
Sep 29, 2008
Messages
641
Age
41
Location
Netherlands
Website
purplepirates.darksiren.net
When I boot my Pandora from having shut it off, the Nubs and Date and time settings shortcuts don't work. If I restart they work again. Doubt it's a problem with my firmware since I reflashed it after getting this problem and I still have it.
 
Eniko said:
When I boot my Pandora from having shut it off, the Nubs and Date and time settings shortcuts don't work. If I restart they work again. Doubt it's a problem with my firmware since I reflashed it after getting this problem and I still have it.
Click to expand...

That's strange. o_O What hotfixes have you installed?

-God Ginrai
 
Last edited by a moderator:
Managed to get it to fail again and this is what pndrunop_nubmode.out contains:
in fork!
PND ++ /usr/pandora/apps//pandorascripts.pnd
mountpoint:
Basename: op_nubmode
mkdir -p /mnt/pnd/op_nubmode
/mnt/utmp/op_nubmode
/usr/pandora/scripts/pnd_run.sh: line 124: [: !: integer expression expected
not mounted on loop yet, doing so
Usage: grep [OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.
Usage: grep [OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.
LoopMountedon:
/dev/loop0
Filetype is Squashfs
sudo mount -t squashfs /dev/loop0
mounting union!
Filesystem is
/usr/pandora/scripts/pnd_run.sh: line 179: [: =: unary operator expected
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
​
/usr/pandora/scripts/pnd_run.sh: line 200: ./op_nubmode.sh: No such file or directory
app exited
rm: cannot remove `/mnt/utmp/op_nubmode': No such file or directory
umount: /mnt/utmp/op_nubmode: not found
umount failed, didnt clean up
Click to expand...
Hope someone can make some sense of this.
 
Bump again.

Far as I can tell every other boot when "the loop is mounted" (and god knows what that means since I'm not schooled in Linux) the "sudo mount -t squashfs /dev/loopn" command fails to mount for some reason. I have no idea why. I did as it told me and used the command "dmesg | tail" at the terminal, which produces this when it fails:

aufs test_add:243:mount[1910]: uid/gid/perm /mnt/pnd/op_wifi 1000/1000/0755, 0/0/0777
aufs au_xino_create:656:mount[1910]: xino doesn't support /tmp/.aufs.xino(ubifs)

Anyone?
 
Eniko said:
Far as I can tell every other boot when "the loop is mounted" (and god knows what that means since I'm not schooled in Linux)
Click to expand...
Devices are files, but files are not devices. You can mount a device (ie, a disk drive), but in order to mount a file (ie, a PND file) it needs to be treated as a disk drive device. That's where loop backs come in. It lets you create a device that other things (ie, the file system) can use.
I've also seen loop backs for a webcam, so you could play a video file, or share your desktop, or whatever, and your system picks up this loop device as if it were a webcam.
None of this helps, of course. I have no idea from looking at the errors why it would be failing. Sorry :(
 
Last edited by a moderator:
Try booting with no cards in, just from the nand
Does this make the mounting errors go away?
It shouldn't need to mount anything to set nubs, that already isn't mounted
Look at the line #s referenced and try to puzzle it out? What about grep?
Two months

dave
 
I get a different failure, but it might be because i was messing with my pnd_run.sh script :eek:


Code: 
op-tsh:~$ cat /tmp/pndrunop_nubmode.out 
in fork!
/usr/pandora/scripts/pnd_run.sh: line 100: [: too many arguments
mountpoint: Mounted on
/usr/pandora/scripts/pnd_run.sh: line 117: [: Mounted: binary operator expected
/usr/pandora/scripts/pnd_run.sh: line 120: [: !: integer expression expected
not mounted on loop yet, doing so
Usage: grep [OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.
Usage: grep [OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.
Filetype is Squashfs
sudo mount -t squashfs  /dev/loop0 /mnt/pnd/op_nubmode
mounting union!
Filesystem is 
/usr/pandora/scripts/pnd_run.sh: line 173: [: =: unary operator expected
Usage: mount -V                 : print version
       mount -h                 : print this help
       mount                    : list mounted filesystems
       mount -l                 : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
       mount -a [-t|-O] ...     : mount all stuff from /etc/fstab
       mount device             : mount device at the known place
       mount directory          : mount known device here
       mount -t type dev dir    : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
       mount --bind olddir newdir
or move a subtree:
       mount --move olddir newdir
One can change the type of mount containing the directory dir:
       mount --make-shared dir
       mount --make-slave dir
       mount --make-private dir
       mount --make-unbindable dir
One can change the type of all the mounts in a mount subtree
containing the directory dir:
       mount --make-rshared dir
       mount --make-rslave dir
       mount --make-rprivate dir
       mount --make-runbindable dir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using  -L label  or by uuid, using  -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say  man 8 mount .
/usr/pandora/scripts/pnd_run.sh: line 194: ./op_nubmode.sh: No such file or directory
app exited
rm: cannot remove `/mnt/utmp/op_nubmode': No such file or directory
umount: /mnt/utmp/op_nubmode: not found
umount failed, didnt clean up

I'll investigate this myself, and report back - but it's nice outside now...
 
Eniko said:
Bump. I'm the only one who gets this?
Click to expand...
In your case, I wonder if you have a corrupted pnd file. check by typing this first line into the terminal, and comparing the result
Code: 
 md5sum /usr/pandora/apps/pandorascripts.pnd 
e8f7287d793aaf5c0e1f2d32284b8705  /usr/pandora/apps/pandorascripts.pnd

BTW, I identified one of my problems, some time in the past, run_pnd.sh has created in my home directory a directory called 'Mounted on', which is the value returned from df into MOUNTPOINT when the pnd is on the root filesystem.
 
Last edited by a moderator:
Booting without SD cards doesn't help. And the checksum is identical to the one posted above. Maybe I should reflash a second time in the hopes it'll be fixed but considering this problem's persisted across the flash that came on the Pandora and the one I reflashed later, I'm not too hopeful for that...
 
sorry, I missed the part about it working when your re-booted. Let me try and check my updated script, and we can see if that helps.
 
Try downloading this file to a temporary directory, http://bugs.openpandora.org/index.php?getfile=40
then in the same directory,
Code: 
chmod u+x
./pnd_run /usr/pandora/apps/pandorascripts.pnd -3

which will let you test my slightly more robust script without replacing the real one. Not much chance it will show the problem, but it is an improvement.
 
I did this and I'm not sure what was supposed to happen, but it looked like it worked. However, it doesn't fix the problem.

EDIT: When I hard reset my Pandora when I have this problem (using Pandora button + power slider) the problem isn't fixed, as opposed to restarting. When I hard reset my Pandora when everything is working the problem does occur after it restarts.

EDIT2: MiniMenu has the same problem.

EDIT3: Finally got sick of fiddling with this. I reflashed and things seem to be working now.
 
Eniko said:
However, it doesn't fix the problem.
Click to expand...

Just to be clear, the instructions I gave were not a permanent fix, just a way of running my version of the script without replacing the built-in one. You'd need to copy that script to /usr/pandora/scripts to make it permanent.
 
Last edited by a moderator:
Yeah, I meant that when I set up your script (without replacing the built-in) the OP PNDs would still fail to start, so it didn't make a difference. I'm still not sure what caused this really, the only odd thing I did on my Pandora was

sudo opkg update
sudo opkg install cifs​
and I highly doubt that could've messed everything up. Still not doing that this go around just in case. :p
 
You must log in or register to reply here.

Similar threads

hmc
Keyboard shortcuts don't work
Replies
8
Views
3K
hmc
hmc
pmprog
XFCE not processing Keyboard Shortcuts
Replies
3
Views
815
MarioPandio
MarioPandio
P
My Pandora freezes every time when I try to change date and time
Replies
16
Views
2K
Mr_Loon
Mr_Loon
E
Please Select The Date.
2 3
Replies
42
Views
7K
EvilDragon
EvilDragon
MarioPandio
Keyboard Shortcuts
Replies
13
Views
4K
MarioPandio
MarioPandio
Back
Top