Ack, Now Opie Won't Start!

[vputz]

OK, no ideas here.

I have a 6000 running OZ 3.5.2.  I was playing around a little bit with it, trying to upgrade Kopi (which was on quickload)...

Well, my main partition ran out of space during the upgrade, so I tried removing Kopi and supporting libraries to install them to SD.  Good plan, but since Kopi was on quickload I decided to reboot with the reset button...

...and Opie is no more.  I can boot and press a button at the "press a key within 5 seconds" prompt, and all works as well as it can in text mode.  I can even activate wlan0 and ssh in to play around.  But starting Opie always blanks the screen and does nothing on the main unit (ssh is still responsive and I can pretend to "/etc/init.d/opie stop" and "/etc/init.d/opie start" to my heart's content).

How can I diagnose what's going on?  I have to admit to being a little panicked; I'm about to move in 2 days and the Z was going to be my wireless link to the outside world, so this is Very Unfortunate.

-->VPutz

[lardman]

Start syslogd; then try 'opie start'; then use logread (I think) to see what the error messages were.

Alternatively make a copy of the /etc/init.d/opie script and edit it so that the errors are spat out to the console rather than to /dev/null


Si

[Pyrates]

Hey, I have the same problem!

I have an 5500, though, but the symptoms are exactly the same. When I /etc/init.d/opie start from the commandline, then theres just quicklauncher in the process list, not qpe nor opie-login (not sure if they have to...).

Heres the relevant excerpt from logread:

Code: [Select]

Jan  1 16:59:51 collie syslog.info -- MARK --
Jan  1 17:10:30 collie user.warn qpe: qt_init() [1383] - successfully entered daemon mode
Seems ok to me.

Here's how it came: I incidentally switched to the text console. Not remembering how to change back, I looked for a command like "switch" or whatnot, using completion by pressing tab. The only possibilities were "swapon" and "swapoff", so I tried using <- to enter something new. I dont know what else I pressed, but then the screen went blank, power went off (I dont have any swap partition, and surely didnt press 5 buttons at once, so I think it doesnt have anything to do with the possible commands). Thats it, I had to hard-reset, and now I have the same symptoms as vputz. I could just reflash (I have backups ), but I'd surely like to know whats going on...

Here's the output of dmesg:

Code: [Select]

root@collie:/etc/init.d# dmesg
Linux version 2.4.18-rmk7-pxa3-embedix-021129 (mickey@r2d2) () #1 Sun, 28 Nov 2004 17:21:11 +0100
CPU: Intel StrongARM-1110 revision 8
Machine: Sharp-Collie
Security risk: creating user accessible mapping for 0x00000000 at 0xe8000000
Security risk: creating user accessible mapping for 0x08000000 at 0xea000000
Security risk: creating user accessible mapping for 0xc2000000 at 0xf2000000
Security risk: creating user accessible mapping for 0x40000000 at 0xf0000000
On node 0 totalpages: 10240
zone(0): 10240 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: console=tty1 root=/dev/mtdblock4 rootfstype=jffs2 jffs2_orphaned_inodes=delete mem=40M
Relocating machine vectors to 0xffff0000
Console: colour dummy device 80x30
Calibrating delay loop... 137.21 BogoMIPS
Memory: 40MB = 40MB total
Memory: 38144KB available (1688K code, 361K data, 80K init)
Dentry-cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode-cache hash table entries: 4096 (order: 3, 32768 bytes)
Mount-cache hash table entries: 1024 (order: 1, 8192 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
GA Chip: L1
UCB1200 generic module installed
RCSR = 2
suspend main adc = 591(591)
fatal chk = 380
apm: BIOS version 1.2 Flags 0x02 (Driver version 1.14)
apm: Current AC Status : 0
batok installed
Starting kswapd
JFFS2 version 2.1. (C) 2001 Red Hat, Inc., designed by Axis Communications AB.
comadj = 147,44414d43,44414d43
Console: switching to colour frame buffer device 60x53
Collie frame buffer driver initialized.
keyboard initilaized.
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with no serial options enabled
COLLIE serial driver version 1.3
ttyS0 on SA1100 UART3 (irq 17)
ttyS1 on SA1100 UART1 (irq 15)ttyS2 on SA1100 UART2 (irq 16), using IRDA
touch adj= 18225,25378,-1441792,-3014656
ucb1200 touch screen driver initialized
sharpled_init: done.
SA1100 Real Time Clock driver v1.00
block: 128 slots per queue, batch=32
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
loop: loaded (max 8 devices)
PPP generic driver version 2.4.1
PPP BSD Compression module registered
ide-cs.c 1.26 1999/11/16 02:10:49 (David Hinds)
Collie Sound Driver Installed
TC35143F audio driver initialized
MTD Sharp chip driver
SA1100 flash: probing 32-bit flash bus
Using static partition definition
Creating 6 MTD partitions on "SA1100 flash":
0x00000000-0x00020000 : "Angel Monitor"
0x00020000-0x00040000 : "CF Updater"
0x00040000-0x000c0000 : "Diagnostics"
0x000c0000-0x001c0000 : "kernel"
0x001c0000-0x00fe0000 : "jffs2"
0x00fe0000-0x01000000 : "angel stuff"
Linux Kernel Card Services 3.1.22
  options:  [pm]
SA-1100 PCMCIA (CS release 3.1.22)
sa1100_pcmcia_init(0)
sa1100_pcmcia_init(1)
Frontlight Driver Initialized.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NetWinder Floating Point Emulator V0.95 (c) 1998-1999 Rebel.com
IrCOMM protocol (Dag Brattli)
VFS: Mounted root (jffs2 filesystem) readonly.
Freeing init memory: 80K
Warning: unable to open an initial console.
klips_info:ipsec_init: KLIPS startup, Openswan KLIPS IPsec stack version: 2.2.0
klips_info:ipsec_alg_init: KLIPS alg v=0.8.1-0 (EALG_MAX=255, AALG_MAX=251)
klips_info:ipsec_alg_init: calling ipsec_alg_static_init()
IPv6 v0.8 for NET4.0
IPv6 over IPv4 tunneling driver
usbdcore: usbdcore 0.1 035 2002-06-12 20:00 (dbg="")
net_fd 0.1 035 2002-06-12 20:00 (dbg="",alwaysup=0,OUT=64,IN=64)
vendorID: 4dd productID: 8004
sa1100_bi 0.2 035 2002-06-12 20:00 (dbg="")
bi_modinit: call udc_startup_events
bi_device_event: call udc_enable
bi_device_event: call udc_all_interrupts
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
SD Driver Initialized.
sharp_mmcsd 0.21 27 Sep 2002
usbdm: usbd_monitor 0.3 035 2002-06-12 20:00
monitor_request_irq: 23 44
monitor_request_irq: failed: -16
usbdm: request irq failed
monitor_connected: 1
monitor_load:
monitor_hotplug: agent: usbd interface: monitor action: load
monitor_modinit: finished
BlueZ Core ver 2.4 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky
BlueZ L2CAP ver 2.3 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky
BlueZ RFCOMM ver 1.1
Copyright (C) 2002 Maxim Krasnyansky
Copyright (C) 2002 Marcel Holtmann
IrDA: Registered device irda1
eth0: NE2000 Compatible: io 0xc4860300, irq 35, hw_addr 00:10:60:F1:CA:11
eth0: no IPv6 routers present
VFS: Disk change detected on device mmcd(60,1)
Partition check:
 mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
VFS: Can't find a Minix or Minix V2 filesystem on device 3c:01.
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
MSDOS FS: IO charset utf8
check backup battery !
usbdcore: usbdcore 0.1 035 2002-06-12 20:00 exiting
usbdcore: usbdcore 0.1 035 2002-06-12 20:00 (dbg="")
net_fd 0.1 035 2002-06-12 20:00 (dbg="",alwaysup=0,OUT=64,IN=64)
vendorID: 4dd productID: 8004
sa1100_bi 0.2 035 2002-06-12 20:00 (dbg="")
bi_modinit: call udc_startup_events
bi_device_event: call udc_enable
bi_device_event: call udc_all_interrupts
I'd really appreciate any comments...

Cheers
Philipp

[vputz]

syslogd/logread, eh?


OK, lemme try...

Code: [Select]

root@tosa:~# /etc/init.d/opie start
Starting Opie in 5 seconds... press key to interrupt.
You seem to already have a /root/Applications directory.
Assuming it is the Opie Applications directory. Exiting.
Starting Opie....
ODevice() - found 'Hardware     : SHARP Tosa'
qt_init() - starting in daemon mode...
root@tosa:~#
Hmm, got my blank screen running.  Let's try that logread.

Woops.  Logread showed no new entries.

However...

Code: [Select]

root@tosa:~# cat /var/log/messages
Jan  1 08:08:02 tosa syslog.info syslogd started: BusyBox v1.00 (2004.11.30-07:04+0000)
Jan  1 08:08:50 tosa user.warn qpe: qt_init() [3779] - successfully entered daemon mode
dmesg wasn't any help.  Is anything running in daemon mode?

Code: [Select]

root@tosa:~# ps -aux
  PID  Uid     VmSize Stat Command
    1 root        532 S   ini  
    2 root            SW  [keventd]
    3 root            RWN [kapm-idled]
    4 root            SW  [off_thread]
    5 root            SW  [battchrgon]
    6 root            SW  [battchrgoff]
    7 root            SW  [sharpsl_bat]
    8 root            SW  [fatalchk]
    9 root            SW  [jacketchk]
   10 root            SWN [ksoftirqd_CPU0]
   11 root            SW  [kswapd]
   12 root            SW  [bdflush]
   13 root            SW  [kupdated]
   14 root            SW  [buzzer]
   15 root            SW  [swapper]
   16 root            SW  [swapper]
   17 root            SW  [mtdblockd]
   19 root            SW  [krfcommd]
   95 root            SWN [jffs2_gcd_mtd2]
  234 root            SWN [jffs2_gcd_mtd3]
  291 root        308 S   /sbin/sdmgr
  345 root            SW  [khubd]
  440 daemon      444 S   /sbin/portmap
  988 root        632 S   /usr/sbin/dropbear -r /etc/dropbear/dropbear_rsa_host
 1010 root        552 S   /usr/sbin/apmd -P /etc/apm/apmd_proxy --proxy-timeout
 1044 root        544 S   /sbin/sdpd
 1071 root        484 S   irattach /dev/ttyS1
 1153 root        768 S   /sbin/cardmgr
 1161 root        584 S   /sbin/syslogd -n -C
 1163 root        564 S   /sbin/klogd -n
 1190 root        524 S   /sbin/getty 115200 ttyS0
 1191 root        900 S   -sh
 3036 root        480 S   /sbin/wland
 3246 root        644 S   udhcpc -b -p /var/run/udhcpc.wlan0.pid -i wlan0
 3738 root       1072 R   /usr/sbin/dropbear -r /etc/dropbear/dropbear_rsa_host
 3739 root        888 S   -sh
 3746 root        592 S   syslogd
 3787 root        716 R   ps -aux
...hmm, don't see anything that looks like QPE.

I tried editing /etc/init.d/opie to redirect anything from /dev/null and, well, I don't see "null" anywhere in there.

I'm absolutely flummoxed!  Any clues would be helpful, but I'm out of ideas.

Thanks!

-->VPutz

[lardman]

I tried editing /etc/init.d/opie to redirect anything from /dev/null

Okay, so perhaps it's directed elsewhere. there must be some output going somewhere.


Si

[vputz]

I tried editing /etc/init.d/opie to redirect anything from /dev/null

Okay, so perhaps it's directed elsewhere. there must be some output going somewhere.

[div align=\"right\"][a href=\"index.php?act=findpost&pid=69901\"][{POST_SNAPBACK}][/a][/div]

One would think.  I wasn't trying to be sarcastic--just couldn't see any redirection.  And I'm not sure there is any!

The plot thickens...

I played with /etc/init.d/opie a bit.  It basically comes down to setting the environment and then calling

Code: [Select]

/opt/QtPalmtop/bin/qpe -terminal 2
Hmm, sounds good.  I try that from the command line... and Opie tries to come up!  Frabjous day!  Unfortunately, it comes up with ONLY the documents tab and the O-menu doesn't work, and it takes a little bit with the hourglass cursor in the bottom-right corner to do it.

Here's the kicker... if I set the OPIEDIR, QPEDIR, LD_LIBRARY_PATH, and PATH as the init.d/opie script does... that very same command line does nothing except say "starting in daemon mode" and quitting (without leaving anything running):

Code: [Select]

root@tosa:~# export OPIEDIR=/opt/QtPalmtop
root@tosa:~# export QPEDIR=/opt/QtPalmtop
root@tosa:~# export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$OPIEDIR/lib
root@tosa:~# export PATH=$PATH:$OPIEDIR/bin
root@tosa:~# /opt/QtPalmtop/bin/q
/opt/QtPalmtop/bin/qcop            /opt/QtPalmtop/bin/qpe
/opt/QtPalmtop/bin/qeserver        /opt/QtPalmtop/bin/quickexec
/opt/QtPalmtop/bin/qpdf            /opt/QtPalmtop/bin/quicklauncher
root@tosa:~# /opt/QtPalmtop/bin/qpe -terminal 2
qt_init() - starting in daemon mode...
root@tosa:~# ps ax | grep qpe
 5575 root        456 S   grep qpe
root@tosa:~#
The mystery deepens.  New shell, new window.  If I set OPIEDIR=/opt/QtPalmtop in the shell, qpe won't start.  If I set it to nothing (clear the variable) it starts but not correctly:

Code: [Select]

root@tosa:~#
root@tosa:~# export OPIEDIR=              
root@tosa:~# /opt/QtPalmtop/bin/qpe -terminal 2
qt_init() - starting in daemon mode...
root@tosa:~# ps ax | grep qpe
 5636 root       5156 S   /opt/QtPalmtop/bin/qpe -terminal 2
 5642 root        456 S   grep qpe
root@tosa:~# kill -9 5636
root@tosa:~# ps ax | grep qpe
 5644 root        456 S   grep qpe
root@tosa:~# export OPIEDIR=/opt/QtPalmtop
root@tosa:~# /opt/QtPalmtop/bin/qpe -terminal 2
qt_init() - starting in daemon mode...
root@tosa:~# ps ax | grep qpe
 5651 root        456 S   grep qpe
root@tosa:~#
(blink, blink)

My flummoxing knows no bounds.  But the mystery gets better, from my point of view...

I have an SD card.  If I set OPIEDIR=/mnt/card/opt/QtPalmtop, QPE actually STARTS, but here's something interesting, only the apps installed to sd actually show up in the menus.  HOWEVER, if the hotkeys are set to launch applications, they will launch them even if they are installed on the main device.

ALSO, the O-menu is still empty and my style settings are lost.

So it sounds like some part of the root-side opie configuration is farkled.  But how can I figure out which part?

(I know, I should probably just reflash at this point, but now my curiosity is piqued, and I really don't want to go through the trouble of reflashing if I can avoid it).

-->VPutz

[Hrw]

try:

Code: [Select]

/opt/QtPalmtop/bin/qpe -nodaemon -terminal 2and look when it fail

[vputz]

try:

Code: [Select]

/opt/QtPalmtop/bin/qpe -nodaemon -terminal 2and look when it fail
[div align=\"right\"][a href=\"index.php?act=findpost&pid=70019\"][{POST_SNAPBACK}][/a][/div]

Thanks!  Didn't know about the -nodaemon switch.  Progress!  I think in my case it's the Kopi alarm applet maybe...

Code: [Select]

root@tosa:~# export OPIEDIR=/opt/QtPalmtop
root@tosa:~# /opt/QtPalmtop/bin/qpe -nodaemon -terminal 2
qt_init() - terminal specification is '2'.
qt_init() - active vt is #1, switching to #2 as requested...
: VTApplet::popup
: WARNING: preferred keyboard is Multikey
: WARNING: Found Applet: libbatteryapplet.so
: OTaskbarAppletWrapper::queryInterface()
: OTaskbarAppletWrapper::queryInterface()
: OTaskbarAppletWrapper::queryInterface()
: WARNING: Found Applet: libbrightnessapplet.so
: OTaskbarAppletWrapper::queryInterface()
: OTaskbarAppletWrapper::queryInterface()
: OTaskbarAppletWrapper::queryInterface()
: WARNING: Found Applet: libcardmonapplet.so
: OTaskbarAppletWrapper::queryInterface()
: OTaskbarAppletWrapper::queryInterface()
: OTaskbarAppletWrapper::queryInterface()
 : WARNING: Found Applet: libclipboardapplet.so
: OTaskbarAppletWrapper::queryInterface()
: OTaskbarAppletWrapper::queryInterface()
: OTaskbarAppletWrapper::queryInterface()
: WARNING: Found Applet: libclockapplet.so
: OTaskbarAppletWrapper::queryInterface()
: OTaskbarAppletWrapper::queryInterface()
: OTaskbarAppletWrapper::queryInterface()
: WARNING: Found Applet: libirdaapplet.so
: OTaskbarAppletWrapper::queryInterface()
: OTaskbarAppletWrapper::queryInterface()
: OTaskbarAppletWrapper::queryInterface()
: WARNING: Found Applet: libkopialarmapplet.so
Bus error
root@tosa:~#
Aha, so it was the kopi-applet program.  Curse it!  Somehow it must have been corrupted during an ipkg operation where I ran out of space; that explains much, I think.  I ipkg-removed it and Opie starts again.

Hurrah!  Thanks for the -nodaemon hint; once I got log information, the rest was pretty easy.

-->VPutz

[Pyrates]

Yeah, that helped. I had the line "Adding SMTP account" and then segmentation fault, so I figured it was the mailapplet. And, behold, as I removed it, everything went back to normal  Thanks !!!

Cheers
Philipp