Messages

1

Zaurus - pdaXrom / Best Wifi?

« on: February 08, 2008, 11:55:12 pm »

i have a d-link dcf-660w that came with my collie (got it on e-bay).. it's freakin awful. somehow it permanently jacks up my SD cards. for a month or two i thought my zaurus was breaking my SD cards until i bought 2 more for dirt cheap on e-bay and started trying to diagnose the problem.

the collie uses a 2.4.18 kernel, though. i'm sure newer kernels have better support. or it could just be _my_ card that acts screwy. or it could just be that pdaxrom has a bad driver for it or something. i don't recall ruining any sd cards during the short period that i used the original sharp rom.

2

Zaurus - pdaXrom / Sl-5500 Right Arrow Shuts Off

« on: February 08, 2008, 10:50:54 pm »

woo! hell yeah! got the touchscreen to work!!!!!!!!!!!!!

mknod /dev/sharp_ts c 11 0

looks like the major/minor numbers were different for my kernel. i got the right ones out of linux/drivers/char/collie_ucb1200_ts.c

3

Zaurus - pdaXrom / Sl-5500 Right Arrow Shuts Off

« on: February 03, 2008, 08:52:04 pm »

one of those patches makes my zaurus unable to see my 256mb pcmcia card. it isn't cacko.patch or unb0rk-apm.patch or unb0rk.rightarrow.patch.

4

Zaurus - pdaXrom / Sl-5500 Right Arrow Shuts Off

« on: February 03, 2008, 05:21:07 pm »

this is a list of the patches that angstrom appears to apply to the kernel. the openswan patch didn't quite apply correctly so i chose not to apply it in my instructions below.

the touchscreen still doesn't work after applying all these patches. either i am leaving something out of the kernel config or there is some other patch that pdaxrom uses that i don't have... this fixed the right arrow bug, though

who knows what else fails to work in this kernel. i haven't done much testing.

all of these patches are in an attachment to this post along with the kernel config file i used.

cacko.patch
unb0rk-rightarrow.patch
unb0rk-apm.patch
battery.patch
bluetooth-2.4.18-mh15.patch
iw_handlers.w13-5.diff
iw_handlers.w14-5.diff
iw240_we15-6.diff
iw249_we16-6.diff
iw249_we17-13.diff
iw240_we18-5.diff
idecs.patch
logo.patch
initsh.patch
keymap-more-sane.patch
mkdep.patch
disable-pcmcia-probe.patch
linux-2.4.18-list_move.patch
openswan-2.2.0-kernel-2.4-klips.patch.gz
1764-1.patch
module_licence.patch
ir240_sys_max_tx-2.diff
ir241_qos_param-2.diff

put the contents of the cross sdk under /usr/local/arm (see my first post for a link to the sdk).

the compiler binaries should wind up in /usr/local/arm/2.95.3/bin once you uncompress the cross sdk tarball.

iirc, there are some hardwired paths in the cross compiler that require it to be in that directory.

create a directory to work in.
put the bziped kernel tarball (my first post links to it), the kernel.config file and all patches in this directory.
cd into the directory.

tar -xvjf linux-sl5500-20030509-rom3_10.tar.bz2
ln -s linux linux-2.4.18
ln -s linux linux-2.6-bkpxa

patch -p0 < cacko.patch
patch -p0 < unb0rk-rightarrow.patch
patch -p0 < unb0rk-apm.patch
patch -p0 < battery.patch
patch -p0 < bluetooth-2.4.18-mh15.patch
patch -p0 < iw_handlers.w13-5.diff
patch -p0 < iw_handlers.w14-5.diff
patch -p0 < iw240_we15-6.diff
patch -p0 < iw249_we16-6.diff
patch -p0 < iw249_we17-13.diff
patch -p0 < iw240_we18-5.diff
patch -p0 < idecs.patch
patch -p0 < logo.patch
patch -p0 < initsh.patch
patch -p0 < keymap-more-sane.patch
patch -p0 < mkdep.patch
patch -p0 < disable-pcmcia-probe.patch
patch -p0 < linux-2.4.18-list_move.patch
patch -p0 < 1764-1.patch
patch -p0 < module_licence.patch
patch -p0 < ir240_sys_max_tx-2.diff
patch -p0 < ir241_qos_param-2.diff

cp kernel.config linux/.config

cd linux
export PATH=$PATH:/usr/local/arm/2.95.3/bin/

for some reason, i need to do a make menuconfig and then immediately exit choosing to save my kernel config at this point. otherwise, the kernel will fail to compile. dunno why.

make menuconfig
   select "Exit"
   select "Yes" at the prompt

make dep && make bzImage

copy the newly created zImage from arch/arm/boot/ to your cf card along with the pdaxrom beta1 initrd.bin

reflash.

you might try leaving out the logo.patch if you don't like the openzaurus logo appearing at the top of the screen. lol.

5

Zaurus - pdaXrom / Sl-5500 Right Arrow Shuts Off

« on: February 02, 2008, 08:51:15 pm »

i've managed to get it to boot but it appears that the touch screen isn't working. i haven't patched the right arrow bug yet either.

anyway, the angstrom project has a complicated .... build system... thing ... that i borrowed configuration info from to get my kernel config to work. i'm really not sure how i managed to make it boot but heck, it works. i'll just stay the hell out of the MTD configuration screen and it should work out ok.. i hope.

OH. the angstrom build system also has like 10 or 15 patches for the 2.4 kernel on the collie. many of these patches look important for getting all the 5500s hardware to work right. the biggest one is "cacko.patch".. it looks like it contains mtd stuff so i bet it's required if you want a kernel that boots. i applied it. it also provides the tiny console font that pdaxrom uses... and a ton of other stuff too, i'm sure. i'll attach the other patches to this thread once i've decided if they are needed or not.

i've attached cacko.patch, and my kernel config.

6

Zaurus - pdaXrom / Sl-5500 Right Arrow Shuts Off

« on: January 21, 2008, 03:48:38 pm »

./Documentation/arm/SA1100/Assabet

that document in the kernel tree has instructions that look relevant. it contains instructions for configuring the kernel. i followed the instructions. it created a .config file for me. i then did a make menuconfig, copied the changes it made to the MTD section to paper, put the old kernel config back in place, and updated it's MTD settings manually via another make menuconfig.

the result is a small improvement:

TC35143F audio driver initialized
MTD Sharp chip driver <ds@lineo.com>
SA1100 flash: probing 32-bit flash bus
Probe at base[0x0](0x00000000) past the end of the map (0xffffffff)
Probe at base[0x0](0x00000000) past the end of the map (0xffffffff)
CFI: Found no SA1100 flash device at location zero
Sharp SL series flash device: 1000000 at 0
request_module[map_rom]: Root fs not mounted
Linux Kernel Card Services 3.1.22
  options:  [pm]
SA-1100 PCMCIA (CS release 3.1.22)
Kernel panic: d'oh

7

Zaurus - pdaXrom / Sl-5500 Right Arrow Shuts Off

« on: January 21, 2008, 02:03:14 pm »

TC35143F audio driver initialized
MTD Sharp chip driver <ds@lineo.com>
Linux Kernel Card Services 3.1.22
  options:  [pm]
SA-1100 PCMCIA (CS release 3.1.22)
Kernel panic: d'oh

found the sharp driver in the kernel config: mtd->ram/rom/flash chip drivers->older ... drivers..->pre CFI sharp..

8

Zaurus - pdaXrom / Sl-5500 Right Arrow Shuts Off

« on: January 21, 2008, 01:46:26 pm »

fun stuff. i made my kernel panic right after it _should_ have done this:

TC35143F audio driver initialized
MTD Sharp chip driver <ds@lineo.com>
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)

instead, it did this:

TC35143F audio driver initialized
Linux Kernel Card Services 3.1.22
  options:  [pm]
SA-1100 PCMCIA (CS release 3.1.22)
Kernel panic: d'oh

that would explain the lack of mtdblock4, i think.

9

Zaurus - pdaXrom / Sl-5500 Right Arrow Shuts Off

« on: January 21, 2008, 01:17:49 pm »

thanks for the log.

it _appears_ that the root device mtdblock4 that my kernel is failing to open is created earlier up in your log:

MTD Sharp chip driver <ds@lineo.com>
SA1100 flash: probing 32-bit flash bus
Using static partition definition
Creating 6 MTD partitions on "SA1100 flash":
0x00000000-0x00020000 : "Angel Monitor"  <- #0
0x00020000-0x00040000 : "CF Updater" <- #1
0x00040000-0x000c0000 : "Diagnostics" <- #2
0x000c0000-0x001c0000 : "kernel" <- #3
0x001c0000-0x00fe0000 : "jffs2"            <-- jffs2 and it's #4
0x00fe0000-0x01000000 : "angel stuff"

perhaps my kernel isn't configured correctly to create this device, whatever it is.
resizing my default initrd size in the kernel didn't work.

10

Zaurus - pdaXrom / Sl-5500 Right Arrow Shuts Off

« on: January 21, 2008, 03:07:52 am »

i didn't have initrd support built into the kernel. d'oh!

but it's still borked. perhaps cos i don't have the default initrd size set correctly.

RAMDISK: Couldn't find valid RAM disk image starting at 0.
Freeing initrd memory: 3072K
VFS: Cannot open root device "mtdblock4" or 1f:04
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 1f:04

bed time. i'll dink around with it later.

11

Zaurus - pdaXrom / Sl-5500 Right Arrow Shuts Off

« on: January 21, 2008, 02:24:28 am »

i used a kernel config file from pdaxrom for the sl-5500 on the kernel mentioned in the first post to get a booting kernel. it appears to point to the same ramdisk /dev/mtdblock4 (major 1f, minor 04) but it panics.

here's the panic i get:

VFS: Cannot open root device "mtdblock4" or 1f:04
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 1f:04

geez. how annoying. is it possible that i need to change something about the ramdisk too?

hopefully it's just something about the kernel that needs changing.

looks like i have a bit of reading up to do if no one has a simple solution to my problem.

12

Zaurus - pdaXrom / Sl-5500 Right Arrow Shuts Off

« on: January 21, 2008, 12:46:10 am »

well, holy cow. i managed to make a kernel that boots with the pdaxrom initrd and then panics when it's unable to mount a root fs.

more to come later if anything interesting happens.

13

Zaurus - pdaXrom / Sl-5500 Right Arrow Shuts Off

« on: January 21, 2008, 12:13:34 am »

thanks for your reply. i flashed my z with the new zImage, powered it up, and it displayed a screen that said "Sharp" in red letters.
but i reflashed with the pdaxrom kernel and it starts up again. i'll try a few more kernels.

14

Zaurus - pdaXrom / Nes Emulator With 5500 - Collie

« on: January 20, 2008, 04:47:07 pm »

i've just compiled fceu for my sl-5500 after reading the above post. it seems to slow to be playable. i'm running it in an x window. i assume it would be much faster without x. but the biggest problem is that it runs in a resolution that is 2 or 3 times the size of the sl5500's resolution. i couldn't find a way to scale the window size down.

15

Zaurus - pdaXrom / Help In Compiling?

« on: January 20, 2008, 03:41:30 pm »

i managed to compile mplayer for my sl-5500 but it's really too slow and kludgy for playing videos, imho...

anyone who wants ought to be able to find the mplayer binary and libmad here: http://static.webng.com/zaurus.html

i just signed up with webng.com for free hosting. i hope the link lasts.