OZ stops at console (OPIE not launched)

[Anonymous]

I\'ve been running OpenZaurus 3.5 for a couple weeks.  I went to put my compact flash card in and it didn\'t see it (although it usually does) so I said hay...reboot. in the shutdown/reboot screen I hit reboot and it stuck there, so I flipped the Replace battery switch down to hard shut it off. (done it many times before in lock ups) and now it boots to a Login: prompt, where I can login and launch console tools.
a) how do I launch OPIE from here?
if I can just get my cf and sd card mounted I can reflash. I have the TK rom/kernel on the sd, which needs to be moved to the CF to reflash. I wan to try TK over OZ anyway.


thank you

[Greg2]

Start Opie with:

# /etc/init.d/opie start

Greg

[Anonymous]

Code: [Select]

# /etc/init.d/opie start

Starting Opie-login....

#
it just exits without launching anything.

[Greg2]

When you installed oz did you set a passcode?

If so, use that for login

Greg

[Mickeyl]

To get debug output, start Opie with /opt/QtPalmtop/bin/qpe

[Anonymous]

I didn\'t set a passcode...but I did login as both root and user (only two users available) neither worked.

[Greg2]

Use the command Mickey gave you and post output

Greg

[lardman]

I\'d do one of these:

Start syslogd - you\'ll have to look at the --help output to see how to start it with a circular memory buffer (as opposed to writing to /var/log/), then try \'/etc/init.d/opie start\', then see what happened by reading the syslog output with logread (or something like that).

or

Look in the /etc/init.d/opie script and try running each bit one by one and see which one is causing the problem.


Si

[Anonymous]

Code: [Select]

# /opt/QtPalmtop/bin/qpe

Could not open for writing `/root/Settings/locale.conf.new\'

Could not open for writing `/root/Settings/qpe.conf.new\'

Cannot create Qt/Embedded data directory: /tmp/qtembedded-root

Code: [Select]

# touch /root/Settings/testfile

touch: testfile: Read-only file system

Hmm...how\'d this happen...

[Anonymous]

Is there some way to alter the boot method (i.e mount as rw) or something?
Essentially...my zaurus is dead until I find out how...last resort is to buy a CF reader/writer and write a new rom to that...

[lardman]

What does \'mount\' show out of interest?

I would suggest that you do a mount -o rw,remount or similar but I don\'t think this will work with jffs2.


Si

[Anonymous]

Code: [Select]

# mount

warning: can\'t open/etc/mtab: No such file or directory
which is because it\'s a RO FS...

when I try to remount /dev/mtdblock4 (according to /etc/fstab the root partition) it says device or resource busy, but I can\'t unmount it (not mounted)

[Greg2]

I don\'t know how to fix that, but try to...

# su
# cd /mnt/card
# ls

if you can see your files to flash with now,  you can move them to cf card

Greg

[Anonymous]

nope, /mnt/card and cf don\'t work.
My wifi card doesn\'t either.

[lardman]

Work out what the mount point is for the flashROM and try running fsck on it?

Si