Messages

1

Zaurus - pdaXrom / Pdaxrom For C3000 (based On Beta1/beta3)

« on: November 26, 2006, 03:11:20 am »

I thought I'd give a quick rundown of my experience with pdaXii13. I started out with the base image and Tetsu kernel. It worked rather well for me, including my Socket CF Wifi card, meaning that the problems with mounting a CF card are purely module based in terms of loading the ide driver. BVDD in Mplayer worked fine for me out of the box. Unfortunately, I started getting the FS errors again. Basically when it happens, I can't do anything anymore. If by chance I have a console open when it happens, I can try to do things like "reboot" but I just get "bus error" or "I/O error." Since it seems like most other people aren't getting it, I'm now suspecting that it's a problem with my Ebook reader, Justreader. I just flashed with hdimage-custom so I'll see if I get the problem without installing Justreader.

For those that are giving suggestions for what default programs / settings to have in the hdimage, keep in mind that this hdimage-custom is Meanie's specific style / programs that he only posted so that we could see what he's got so far. Once you get things exactly as you like for a default installation, you can run his zbackup program and get a tgz of your specific default programs, which I think is awesome.

2

Zaurus - pdaXrom / Pdaxrom For C3000 (based On Beta1/beta3)

« on: November 24, 2006, 04:04:51 am »

Will try it ASAP! Thank you so much!
BTW, what does the name pdaXii31 mean?
daniel
[div align=\"right\"][a href=\"index.php?act=findpost&pid=147149\"][{POST_SNAPBACK}][/a][/div]

I would venture a guess at pdaXrom based on the Beta ii produced earlier for the 3k and the pdaXrom Beta 1/Beta 3 versions. hehe. Currently, I was able to get all the files except hdimage-custom.tgz, so I'm guessing it's still uploading.

3

Zaurus - pdaXrom / Pdaxrom B3 For C3000

« on: November 16, 2006, 02:40:26 am »

ok, I got it working. pdaXrom 1.1.0 beta3 on C3000 using Tetsu special kernel 18h, ie 2.4.20

I am going to polish up the installer a bit more. Then I am going to apply all the customisations and create the base hdimage.tgz file

The installer allows you to repartition the MicroDrive, either one partition of 4GB, my custom paritioning which is 1.5GB root, 512MB swap,  2.0GB data
it also allows you to restore the default Sharp partition layout

what I want to do is make this the universal installer for C3000 and allow it to flash pdaXrom beta3, r121 and OZ

anyway,  there's still a lot of work to be done...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=146402\"][{POST_SNAPBACK}][/a][/div]

Sounds good. What exactly did you have to do to get it work? Mainly, how did you build a working initrd? I think some good documentation would be good so that everyone could benefit. Unfortunately, I've been pretty busy so I haven't gotten to play with it any since my last post.

Do you need any help working through any of it?

4

Zaurus - pdaXrom / Pdaxrom B3 For C3000

« on: November 11, 2006, 11:27:32 pm »

Another way you can run whatever distro you want on your 3k i described in my post here:

https://www.oesf.org/forums/index.php?showtopic=21540&hl=

The nice thing about just using the Oz kernel and installer to install pdaxrom is you can run any version of pdaxrom, because the oz kernel boots from the c3k hard drive, so its transparent to pdaxrom. there is a SMALL probability that because the modules and kernel could have been compiled with different options of a problem coming up, but i use the hostap driver, hid for a usb kb, and usb-storage for a hd and never had any stability issues.

Using the oz kernel to boot a standard pdaxrom install also helps keep us from making a c3k fork of pdaxrom, more effort can then be focused on pdaxrom itself, and not workaround hacks. the only thing that should be put in place for pdaxrom in reguards to the 3k is change the kernel option on the 3k distro to boot from (names here may be wrong, i'm going from memory) /dev/hda1 instead of /dev/mtblock1.

on the suspend issue i always suspend with apm --suspend, and never have any problems, the button just seems to give me issues, so i don't use it.

I hope this helps some ppl, enjoy
[div align=\"right\"][a href=\"index.php?act=findpost&pid=146079\"][{POST_SNAPBACK}][/a][/div]

Well, I think using the OZ kernel works just fine for maybe Beta 4 and 1.10r121 because they run on a 2.6 kernel. Beta 3 runs on a 2.4 kernel, so I don't think it'd work. Out of curiosity, I just tried it and it wouldn't boot up with the Beta 3 hdimage1.tgz at all (froze after displaying the OpenZaurus logo).

One of the main reasons I'd like to use a pdaXrom-based kernel is for the BVDD support, which OZ doesn't support. They're working on their own method of acceleration, but that will take some time to get out. Being able to have an accelerated Mplayer and to use psx4zaurus is a major plus for me.

5

Zaurus - pdaXrom / Pdaxrom B3 For C3000

« on: November 10, 2006, 09:28:10 pm »

not sure about the initrd.bin bit, but if you send me a tarball of its content, then I could give it a go also.

as for the modules, did you replace the existing lib directory with the lib directory of tetsu's modules? it does not contain everything, but rather is a set of updatede modules so you would need the existing module files and just copy the tetsu ones on top to overwrite and replace some of them.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=146022\"][{POST_SNAPBACK}][/a][/div]

Oh, I thought Tetsu's ipk provided all the necessary modules. I'll try that again. I've attached a tar.gz of the modified initrd I tried. It's got the two fixes you have on your website applied (to provide fsck and to boot even with an external CF card inserted), but it didn't work for me.

Well, I just tried it with Tetsu's module ipk overlaying the original beta 3 hdimage.tgz's modules and I still get the same error. Sure enough, even after not replacing, but overlaying Tetsu's modules, there is still no ide-cs.o module. Maybe ThC's compiled kernel had that built in (so that he wouldn't need the module in the initrd), but Tetsu's kernel does not. I'm not sure.

6

Zaurus - pdaXrom / Pdaxrom B3 For C3000

« on: November 10, 2006, 10:52:07 am »

Just for fun, I played around with the initrd and tried to build my own with the beta2 initrd and applying your fixes. I used the instructions here:

https://www.oesf.org/index.php?title=C3000_Device_Specifics

to extract, modify, and rebuild the initrd, including the SHARP header. Unfortunately, when I tried to boot with this initrd, I got these errors:

Code: [Select]

CLEANMARKER node found at 0x00280000 has totlen 0xc != normal 0x0
VFS: Mounted root (jffs2 filesystem) readonly.
Freeing init memory: 80K
and then it just hung, so I'm assuming there's something I don't know about building an initrd file (quite likely). I also tried to use a new tools.tar file with Tetsu's kernel and new hdimage.tgz with the beta3 files and also the /lib/modules/2.4.20 folder replaced with the one provided with Tetsu's modules ipk then tried to boot with ThC's original initrd, but this also gave me problems. It said that it couldn't parse the modules.dep file (which has a file length of 0) and also it couldn't find the pcmcia/ide-cs.o file, which doesn't exist. I've never used Tetsu's kernel before... are these modules possibly built into the kernel and we need to modify the initrd to not require that module?

7

Zaurus - pdaXrom / Pdaxrom B3 For C3000

« on: November 10, 2006, 08:57:32 am »

Sounds good. For the fixes, do you basically mean the fixes you have here:

http://www.users.on.net/~hluc/myZaurus/custom-pdaxrom.html

or are there other fixes that need to be applied? Customizing hdimage.tgz is probably the last thing we need to do, as it's simply a matter of providing the root fs that will be booted (like you said, changing default programs and such).

Your kernel idea sounds good. I didn't think about using the Tetsu kernel as I've never used it before.

In terms of initrd, couldn't we just modify the initrd provided in beta2 with the fixes listed on your site to provide the fsck, and the external CF card fixes? We can work on improving the initrd with a boot menu and such after we get a booting system, I think, with the improved kernel and updated root fs.

Why do you need to rip the initrd.bin from a Zaurus file? If we're just applying fixes to an existing initrd, couldn't we just mount it, fix it, unmount it, and re-rip it from the /dev/mtdblock0? I'm not terribly familiar with the whole process yet, so I'm not exactly sure.

8

Zaurus - pdaXrom / Pdaxrom B3 For C3000

« on: November 10, 2006, 08:15:33 am »

Well, I had a little bit of time today, so I took a look at the kathrin-1.1.0beta3-akita zip file and started comparing it to ThC's pdaXrom-c3000beta2 release to see what would need to be done to get a nice stable version of pdaXrom running on the c3000. Personally, pdaXrom did exactly what I needed to, but I couldn't stand the instability of it (when I used beta2, I would have to reboot my zaurus constantly due to FS errors), which got me to switch to OpenZaurus, where I had no stability problems except if I didn't touch my zaurus for a while.

Looking through the initrd files, we should be able to use the same root structure without too much hassle. We'd just have to figure out the bare minimum we'd want flashed onto the ROM in order to pivot to the hard drive and go from there. We could also probably use the same initrd file, if I'm not mistaken, as all it does is pivot the root to the hard drive. I may have a go at flashing the pdaXrom-c3000beta2 with only replacing the hdimage1.tgz with the beta3 ripped root directory.

The main problem is that we'd still be using the same kernel that ThC compiled for beta2, in the tools.tar file. I've compiled kernels before, but never for the zaurus, so I don't really have an environment setup to do it, nor do I know anything about the pdaXrom build tools or where the proper patches are to patch the kernel with what is necessary. Is anyone still even interested in this at all? I guess I got kind of tired of no one really taking any initiative in getting proper C3000 support. I'm really rather busy though, so I'll help when I can, but we need as much help as we can. Let's also document everything we do as much as possible so future people can take over as necessary.

9

Zaurus - pdaXrom / Pdaxrom B3 For C3000

« on: October 26, 2006, 04:39:14 am »

The problem is that this thread is specifically about the C3000. The last time I checked, the best that we had for the C3000 was the 1.1.0beta1-based Beta 2 version. When I ran this, I essentially had to restart the zaurus every day due to file system problems. I thought that my microdrive may have been going out, but I switched to OZ and it's been very stable ever since.

The responses to the stability were referring to the 1.1.0beta3, which, as far as I know, isn't really running on the C3000 yet, which is the original purpose of this thread. I am aware of the people trying to get the newest version of Pdaxrom up on the C3000, but this version is based on the 2.6 kernel and has its own set of problems.

I'd like to return to Pdaxrom sometime, but I don't think I have the time/experience to get it up and running without a how-to, which is why I've been following this thread in the hopes that someone gets it working.

10

Zaurus - pdaXrom / Japanese Dictionnary

« on: February 11, 2006, 02:08:29 pm »

Hello !

I found XJDICT but don't know if anybody has tried to port it to the zaurus...
It seems to be quite light yet powerful...

http://www.csse.monash.edu.au/~jwb/xjdic/
[div align=\"right\"][a href=\"index.php?act=findpost&pid=114323\"][{POST_SNAPBACK}][/a][/div]

I got it compiled, but the terminal doesn't know how to display the Japanese Encodings. I'd like to see Kiten for the PdaXrom; it's what I use on my desktop and I really like it. I don't know how to compile Kiten without KDE though.

11

Zaurus - pdaXrom / Gp2x Psone Emulator Running Realy Fast

« on: February 06, 2006, 12:40:26 am »

How are people getting FF7 to work? With the latest version, when I try to run FF7, I see the Sony Computer Entertainment America Presents text flicker, then flicker again, then it just freezes. I'm using an uncompressed BIN I created in Linux. Epsxe runs the BIN fine.

12

Zaurus - pdaXrom / Gp2x Psone Emulator Running Realy Fast

« on: February 04, 2006, 05:32:15 pm »

I have one quick question. Does it make any speed difference in running a compressed file as opposed to an uncompressed. I don't mind the space taken up by an uncompressed BIN file.

13

Zaurus - pdaXrom / Gweled Compiled

« on: January 24, 2006, 04:57:11 pm »

I finally got Gweled working for PdaXrom. Some of the animations slow down when a lot of stuff happens, but it's definitely playable.

I'm not sure what dependencies it needs.

14

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2

« on: January 11, 2006, 11:28:51 pm »

So far it works pretty well. The only issue I'm having is that when I turn off/suspend the Zaurus, the hard drive light stays lit. Is this normal behavior? Can we stop it from lighting? I don't think that the hard drive is actually active.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110520\"][{POST_SNAPBACK}][/a][/div]

Remove the SD card, and they are no problem ... hard drive stop light.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110531\"][{POST_SNAPBACK}][/a][/div]

I've turned off the Zaurus without any cards in at all (SD or CF) and the hard drive light still stays lit. It's been that way for several hours and hasn't really lost any battery power, so I'm assuming that the hard drive isn't being used, but the light is still rather annoying. Any ideas?

15

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2

« on: January 11, 2006, 02:44:40 pm »

So far it works pretty well. The only issue I'm having is that when I turn off/suspend the Zaurus, the hard drive light stays lit. Is this normal behavior? Can we stop it from lighting? I don't think that the hard drive is actually active.