Messages

1

Zaurus - pdaXrom / Zaurus Cannot Boot Anymore

« on: August 26, 2007, 11:35:44 am »

I need to re-flash soon. I keep forgetting stuff. Any other ideas before I do?

dq

2

Zaurus - pdaXrom / Zaurus Cannot Boot Anymore

« on: August 12, 2007, 05:58:12 pm »

Makes no difference.

dq

3

Zaurus - pdaXrom / Zaurus Cannot Boot Anymore

« on: August 10, 2007, 09:50:19 pm »

No problem, I do want to re-flash sometime soon though. Having this out of service for too long is killing me.

dq

4

Zaurus - pdaXrom / Zaurus Cannot Boot Anymore

« on: August 09, 2007, 11:34:18 pm »

Maybe there's something else that's shown during the start-up that's causing problems. Here's some of the other messages during the start-up:

Code: [Select]

sa1100-rtc sa1100-rtc: setting system clock to 1970-01-01 00:00:08 (9)
mmcblk0: mmc0:e624 SD01G 992000KiB
 mmcblk0: p1
jffo2_scan_inode(): CRC failed on node at 0X073a7df4: Read 0xffffffff, calculated 0x1490a44b
VFS: Mounted root (jffs2 filesystem)
Freeing init memory: 76K
sharpsl-pm sharpsl-pm: Charging Error!
JFFS2 notice: (1) read_dnode: header CRC failed on node at 0x49a57d8: read 0xffffffff, calculated 0x91771dd9
INIT version 2.86 booting
JFFS2 notice: (1) read_dnode: header CRC failed on node at 0x49a41e8: read 0xffffffff, calculated 0x57071eab
JFFS2 notice: (1) read_dnode: header CRC failed on node at 0x4112fe4: read 0xffffffff, calculated 0xb3dcdeb6
INIT: cannot execute "/etc/rc.d/rc.sysinit"
JFFS2 notice: (1) check_node_data: wrong data CRC in data node at 0x04172000: read 0x779fcb82, calculated 0xf50f6549.
INIT: Entering runlevel: 5
Starting sshd:PRNG is not seeded         [FAILED]
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
switchevd: No such file or directory
Starting switchevd:                              [   OK   ]
JFFS2 warning: (1) jffs2_sum_write_sumnode: Not enough space for summary, padsize = -74
INIT: Id "ln" respawning too fast: disabled for 5 minutes
INIT: no more processes left in this runlevel
NB: I had the battery taken out for this boot.

I may have some typos in there since I typed it all by hand.

Here's my rc flie:

Code: [Select]

#!/bin/sh
#
# rc            This file is responsible for starting/stopping
#               services when the runlevel changes.
#
# Original Author:      
#               Miquel van Smoorenburg,
# Modified:
#    2001.12.11    SHARP, for SHARP SL series
#


# Now find out what the current and what the previous runlevel are.
#argv1="$1"
#set `/sbin/runlevel`
#runlevel=$2
#previous=$1
#export runlevel previous
runlevel=$1

# Is there an rc directory for this new runlevel?
if [ -d /etc/rc.d/rc$runlevel.d ]; then
    # First, run the KILL scripts.
    for I in /etc/rc.d/rc$runlevel.d/K*; do
    # Check if the script is there.
    [ ! -f $I ] && continue
    
    # Check if the subsystem is already up.
    subsys=${I#/etc/rc.d/rc$runlevel.d/K??}
    [ ! -f /var/lock/subsys/$subsys ] && \
     [ ! -f /var/lock/subsys/${subsys}.init ] && continue

    # Bring the subsystem down.
    if [ -x $I ];then
     $I stop
    fi
    done

    # Now run the START scripts.
    for I in /etc/rc.d/rc$runlevel.d/S*; do
    # Check if the script is there.
    [ ! -f $I ] && continue

    # Check if the subsystem is already up.
    subsys=${I#/etc/rc.d/rc$runlevel.d/S??}
    [ -f /var/lock/subsys/$subsys ] || \
     [ -f /var/lock/subsys/${subsys}.init ] && continue

    # Bring the subsystem up.
    if [ -x $I ];then
     $I start
    fi
    done
fi

# Check for runlevel 0 or 6
if [ $runlevel -eq 0 -o $runlevel -eq 6 ]; then
    for I in /etc/rc.d/rc$runlevel.d/S*; do
    # Check if the script is there.
    [ ! -f $I ] && continue

    # Check if the subsystem is already up.
    subsys=${I#/etc/rc.d/rc$runlevel.d/S??}
    [ -f /var/lock/subsys/$subsys ] || \
     [ -f /var/lock/subsys/${subsys}.init ] && continue

    # Bring the subsystem up.
    if [ -x $I ]; then
     $I start
    fi
    done
fi

exit 0
It shouldn't really have changed-- I don't mess around with config files in pdaxrom.

Oh yeah, I didn't mention that I have a c760, but that should be kinda obvious from the log files I gave you.

Thanks.

dq

5

Zaurus - pdaXrom / Zaurus Cannot Boot Anymore

« on: August 08, 2007, 09:48:39 pm »

ls -l /mnt/pdaxrom/sbin/getty

Code: [Select]

lrwxrwxrwx    1 root     root           14 Jan  1 00:00 /mnt/pdaxrom/sbin/getty -> ../bin/busybox
/mnt/pdaxrom/bin/busybox | grep getty

Code: [Select]

    getty, grep, head, hwclock, kill, klogd, ln, logger, login, losetup,
Ok, the last one I was able to make a new tty2 login prompt. The only problem was that I couldn't ctrl-c out of it. I'm not even sure what the button for ctrl is in emerg. Is it the kanji key (the one next to Fn)? If so, it doesn't work. None of the other buttons work either-- they just display garbage: '^[[20~' etc.

I tried to killall busybox too, but that didn't work either.

dq

6

Zaurus - pdaXrom / Zaurus Cannot Boot Anymore

« on: August 07, 2007, 09:08:08 pm »

inittab:

Code: [Select]

#
# /etc/inittab
#

#   0 - halt (Do NOT set initdefault to this)
#   1 - Single user mode
#   2 - Multiuser, without NFS (The same as 3, if you do not have networking)
#   3 - Full multiuser mode
#   4 - JavaVM(Intent) developer mode
#   5 - JavaVM(Intent)
#   6 - reboot (Do NOT set initdefault to this)
#
id:5:initdefault:

# Specify things to do when starting
si::sysinit:/etc/rc.d/rc.sysinit

l0:0:wait:/etc/rc.d/rc 0
l1:1:wait:/etc/rc.d/rc 1
l2:2:wait:/etc/rc.d/rc 2
l3:3:wait:/etc/rc.d/rc 3
l4:4:wait:/etc/rc.d/rc 4
l5:5:wait:/etc/rc.d/rc 5
l6:6:wait:/etc/rc.d/rc 6

# Specify things to do before rebooting
um::ctrlaltdel:/bin/umount -a -r > /dev/null 2>&1
sw::ctrlaltdel:/sbin/swapoff -a > /dev/null 2>&1

# Specify program to run on ttyS0
s0:24:respawn:/sbin/getty 9600 ttyS0
pd:3:respawn:/etc/sync/serialctl

# Specify program to run on tty1
1:2:respawn:/sbin/getty 9600 tty1
ln:345:respawn:/sbin/getty 9600 tty1
#qt:5:respawn:/sbin/qt

# collie sp.
#sy::respawn:/sbin/shsync
messages:

Code: [Select]

Jan  1 00:01:41 syslogd started: BusyBox v1.01 (2007.04.11-21:57+0000)
Jan  1 00:01:48 consolechars: Format: 3
Jan  1 00:01:48 rc.sysinit: Setup console font: succeeded
Jan  1 00:01:48 init: Entering runlevel: 5
Jan  1 00:01:49 zaurushw: Starting Husky:  succeeded
Jan  1 00:01:50 sshd:
Jan  1 00:01:50 sshd:
Jan  1 00:01:51 sshd[900]: Server listening on :: port 22.
Jan  1 00:01:51 sshd[900]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Jan  1 00:01:51 ssh: sshd startup succeeded
Jan  1 00:01:53 input.agent[930]: ... no modules for INPUT product 0019/0001/0001/0100
Jan  1 00:02:05 switchev: Starting switchevd:  succeeded
Jan  1 00:21:41 -- MARK --
Jan  1 00:23:58 login[1115]: root login  on `vc/1'
Jan  1 00:24:02 sudo:     root : TTY=vc/1; PWD=/home/root; USER=root; COMMAND=/usr/bin/loadkeys /etc/sysconfig/keyboard/Husky/keymap.map
Jan  1 00:24:02 sudo:     root : TTY=vc/1; PWD=/home/root; USER=root; COMMAND=/sbin/modprobe mousedev
Jan  1 00:24:03 input.agent[1141]: ... no modules for INPUT product
Jan  1 00:24:06 switchev: switchevd shutdown succeeded
Jan  1 00:24:07 switchev: Starting switchevd:  succeeded
Jan  3 14:39:04 sudo:     root : TTY=vc/1; PWD=/home/root; USER=root; COMMAND=/sbin/pccardctl eject 0
Jan  3 14:39:10 sudo:     root : TTY=vc/1; PWD=/home/root; USER=root; COMMAND=/sbin/pccardctl insert 0
Jan  3 15:49:31 -- MARK --
Jan  5 11:53:24 -- MARK --
Jan 10 21:33:09 -- MARK --
Jan 21 14:15:33 -- MARK --
Jan 25 20:10:08 -- MARK --
Jan 27 14:54:25 sudo:     root : TTY=vc/1; PWD=/home/root; USER=root; COMMAND=/usr/bin/loadkeys /etc/sysconfig/keyboard/Husky/keymap.m
dmesg:

Code: [Select]

Linux version 2.6.16 (root@pdaX86) (gcc version 3.4.6) #1 PREEMPT Wed Apr 11 15:59:50 UTC 2007
CPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE)
Machine: SHARP Husky
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 16384
  DMA zone: 16384 pages, LIFO batch:3
  DMA32 zone: 0 pages, LIFO batch:0
  Normal zone: 0 pages, LIFO batch:0
  HighMem zone: 0 pages, LIFO batch:0
Memory clock: 99.53MHz (*27)
Run Mode clock: 199.07MHz (*2)
Turbo Mode clock: 398.13MHz (*2.0, active)
CPU0: D VIVT undefined 5 cache
CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
Built 1 zonelists
Kernel command line: console=ttyS0,115200 console=tty1 root=/dev/mtdblock2 rootfstype=jffs2
PID hash table entries: 512 (order: 9, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 64MB = 64MB total
Memory: 62220KB available (2108K code, 401K data, 76K init)
Calibrating delay loop... 397.31 BogoMIPS (lpj=1986560)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Sharp Scoop Device found at 0x10800000 -> 0xc4800000
pxa25x: CPU frequency change support initialized (powersave tables)
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) (SUMMARY)  (C) 2001-2003 Red Hat, Inc.
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
Corgi Backlight Driver Initialized.
Found w100 at 0x08000000.
Console: switching to colour frame buffer device 80x30
fb0: w100fb frame buffer device
pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 15) is a FFUART
pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 14) is a BTUART
pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 13) is a STUART
pxa2xx-uart.3: ttyS3 at MMIO 0x41600000 (irq = 0) is a HWUART
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
Sharp SL series flash device: 800000 at 0
Using static partision definition
Creating 1 MTD partitions on "sharpsl-flash":
0x00120000-0x007f0000 : "Boot PROM Filesystem"
pccard: PCMCIA card inserted into slot 0
pcmcia: registering new device pcmcia0.0
NAND device: Manufacturer ID: 0xec, Chip ID: 0x79 (Samsung NAND 128MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 32 at 0x00080000
Bad eraseblock 1445 at 0x01694000
Creating 2 MTD partitions on "sharpsl-nand":
0x00000000-0x00700000 : "Logical"
0x00700000-0x08000000 : "JFFS2"
input: Corgi Keyboard as /class/input/input0
input: Corgi Touchscreen as /class/input/input1
sa1100-rtc sa1100-rtc: rtc intf: sysfs
sa1100-rtc sa1100-rtc: rtc intf: proc
sa1100-rtc sa1100-rtc: rtc intf: dev (253:0)
sa1100-rtc sa1100-rtc: rtc core: registered sa1100-rtc as rtc0
sa1100-rtc sa1100-rtc: SA11xx/PXA2xx RTC Registered
I2C: i2c-0: PXA I2C adapter
Registered led device: corgi:amber
Registered led device: corgi:green
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 2, 16384 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Probing IDE interface ide0...
mmcblk0: mmc0:e624 SD01G 992000KiB
 mmcblk0: p1
hda: TOSHIBA THNCF1G02PG, CFA DISK drive
ide0 at 0xc4820000-0xc4820007,0xc482000e on irq 40
hda: max request size: 128KiB
hda: 2000880 sectors (1024 MB) w/2KiB Cache, CHS=1985/16/63
 hda: hda1
ide-cs: hda: Vcc = 3.3, Vpp = 0.0
sa1100-rtc sa1100-rtc: setting the system clock to 1970-01-01 00:00:10 (10)
VFS: Mounted root (jffs2 filesystem).
Freeing init memory: 76K
JFFS2 notice: (1) read_dnode: header CRC failed on node at 0x4112fe4: read 0xffffffff, calculated 0xb3dcdeb6
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
NET: Registered protocol family 23
ASoC version 0.10rc4
wm8731: WM8731 Audio Codec 0.7
soc: WM8731 <-> pxa2xx-i2s mapping ok

7

Zaurus - pdaXrom / Zaurus Cannot Boot Anymore

« on: August 07, 2007, 09:01:22 pm »

I didn't do anything unusual with the unit. The last thing I tried to do was upgrade from sp5 to sp8. Which didn't seem to successful I might add. However, that was over a month ago. I haven't done anything configuration-wise since. I'll post inittab, dmesg etc. shortly.

dq

8

Zaurus - pdaXrom / Zaurus Cannot Boot Anymore

« on: August 06, 2007, 03:18:55 pm »

I didn't do anything out of the ordinary only tried to reboot the unit by removing the battery because the unit froze-up (for the millionth time-- I've complained about this before). Anyway, now during the boot-up sequence it seems to freeze at:

Code: [Select]

Starting switchevd:                      [  OK  ]However, it's not really frozen because I eventually get an error message:

Code: [Select]

INIT: Id "ln" respawning too fast: disabled for 5 minutesThen it occurs again in 5 minutes and so on.

Previous to the switchevd message I get another error message:

Code: [Select]

Starting sshd:PRNG is not seeded         [FAILED]Does this have to do with the problem?

I'd just re-flash the ROM (v197); however, I don't want to lose any data. Is there a way I can at least back-up the data before I have to re-flash?

Thanks.

dq

9

Zaurus - pdaXrom / Fixes For R198/r197

« on: June 17, 2007, 11:19:35 pm »

Oh yeah, and sometimes the unit doesn't shut off (suspend)-- I have to reboot it to make it work again.

dq

10

Zaurus - pdaXrom / Fixes For R198/r197

« on: June 12, 2007, 10:27:18 pm »

- shutting off randomly for no reason

this is actually a power saving feature. just change the timeout to be longer.

This is not the screen shutting off but rather the whole unit shutting off. Maybe there's another timeout you're referring to, but the problem seems to go deeper than the "Light & Power Settings".

- apm issues

more details please....

Actually, I think this is related to the previous problem. It has been mentioned before that's why I didn't elaborate. Basically, after it shuts off by itself and quite unexpectedly, it takes great effort (and a little prayer) to get it turned back on. When I check the power level it has dropped to 5% when just a few minutes before the power level was good. I've given-up trusting apm and the power level indicator.

Also, I should mention, another problem. It may be related to these other two points, but sometimes (and it seems quite random) when powering up, X freezes-up, only showing a blinking cursor in the top right. I can ssh in and kill X or take out the battery and reboot the unit, but in the course of doing this the data that was in any of the programs that were running becomes corrupted.

dq

11

Zaurus - pdaXrom / Fixes For R198/r197

« on: June 12, 2007, 01:14:25 pm »

any comment about r197 stability/usability after this patch?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163041\"][{POST_SNAPBACK}][/a][/div]

Sure. First of all I have a 760. There are some neat additions to this I recommend upgrading if you already have r197 installed.

However, the debilitating issues are still present:

- shutting off randomly for no reason
- apm issues
- screen not refreshing after exiting X
- audio doesn't shut off when headphones are plugged-in
- screen fading doesn't work with Fn+3 and 4 keys

There are more, these are just off the top of my head.

All I ask for is stability (the first issue). I can live with the rest of the issues.

dq

12

Zaurus - pdaXrom / New Pdaxrom Release R197

« on: April 17, 2007, 10:28:38 am »

Thanks to the developers for releasing this.

Yeah the APM issue is still not resolved. Looks like the something (APM?) makes the Z think that it is low on battery and shuts it off.

Also, turning it on is a problem, I'm not sure if I should use the 'Home' button or the 'Power' button-- I've tried both, but I cannot figure out which one actually works since I press both until it finally turns on.

EDIT: Right after I wrote the above I realized that pdaxrom's behavior changed after installing the normal applications I used. Maybe the programs that I use interfere with the rom itself? Once I have time, I'll make a list of programs that I installed on top of the vanilla install. Please note, that I didn't notice the behavioral changes immediately after installation. They started gradually, which, I don't really understand why.

dq

13

Zaurus - pdaXrom / What Is The New Version?

« on: April 09, 2007, 02:54:35 pm »

Yeah, I know. I don't like to complain since I am getting this for free. So thanks guys for all your hard work!

dq

14

Zaurus - pdaXrom / What Is The New Version?

« on: April 09, 2007, 11:24:02 am »

Yeah, r121, that's the one I'm using. It constantly crashes and corrupts all my data, I cannot play music on it anymore, the battery charging manager doesn't work well anymore, the date resets to zero when I reboot, some of the buttons don't work properly, the screen doesn't refresh in tty-mode, the screen shuts off for no reason and doesn't turn back on... I've been able to cope with some of these issues for months now, but my patience is wearing thin, especially when all my data gets corrupted. Do others here feel the same way?

dq

15

Zaurus - pdaXrom / What Is The New Version?

« on: April 09, 2007, 10:43:45 am »

A fews ago I asked if the new version would be released. I was told it would be released in one week; however, it's now been like three weeks and there doesn't seem to be a new release. But I'm seeing talk of ii13, r189, r196, what are these? Are these the releases that were promised or something else?

dq