Author Topic: pdaXrom on SL-6000 (Read 9741 times)

amrein · « **on:** October 27, 2004, 10:57:30 am »

Hi,

Has someone tested pdaXrom on SL-6000? If not, what are the show stoppers you found? Any info?

I guess the bigger issue at present is pdaXrom developpers not having this device in their hands (for test) but... a lot of people here in US should already have hacked this device isn't it? I mean pdaXrom users.

Anyone who can liberate all SL-6000 users wanting to test something else?

nevarrie · « **Reply #1 on:** October 27, 2004, 03:08:44 pm »

Quote

Hi,

Has someone tested pdaXrom on SL-6000? If not, what are the show stoppers you found? Any info?

I uses a modified verion of the pdaXrom updater.sh to flash OpenZaurus OPIE and GPE to my SL-6000L. I made my version of the updater.sh so it can flash the pdaXrom also. Whne I did flash the initrd.bin(Using my OpenZaurus Kernel) the fash goes just fine but then durring boot it hangs. I am guessing this is due to the 30/30 split on the flash partition and a 40+mb initrd.bin. THe resize of partitons does nto seem to work on the 6k...but I really did nto spend much time on trying to figure out the problem...if anyone is interested in testing this and makign it work you can get the tar for my flash here:

http://zaurus.thegrantclan.org/download/za...20041027.tar.gz

WARNING: that tar file is about 70mb.(Has initrd.bin files for GPE, OPIE and PdaXrom) To uses it just extract the contents to you cf or sd card and doa power|OK boot then choice update for the zaurus maintance menu...then you zaurus will boot into the menu system simular to pdaXrom. Mine has a few menus that work for me when I am flashing between OPIE and GPE...If you need to remove something to make the tools dir smaller you can remove the intrd.bin in the OPIE or GPE dir if you do not wish to flash those to your Z.

nevarrie · « **Reply #2 on:** October 27, 2004, 05:57:52 pm »

I decided to take a closer look at pdaXrom again today and using the updater.sh console I found in /var/log/dmesg this:

Code: [Select]

RAMDISK: Compressed image found at block 0
Freeing initrd memory: 8192K
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 156K
jffs2_scan_inode_node(): Data CRC failed on node at 0x000664a4: Read 0x40596715, calculated 0x7f5c2731
Child dir "gtk-2.0" (ino #2256) of dir ino #2144 appears to be a hard link
Inode #3645 was a directory with children - removing those too...
Inode #3646 was a directory with children - removing those too...
Inode #5597 was a directory with children - removing those too...
Inode #5598 was a directory with children - removing those too...
Inode #5599 was a directory with children - removing those too...
Inode #5614 was a directory with children - removing those too...
Inode #5617 was a directory with children - removing those too...
Inode #5618 was a directory with children - removing those too...
Inode #5626 was a directory with children - removing those too...
Inode #5500 was a directory with children - removing those too...
Inode #5502 was a directory with children - removing those too...

amrein · « **Reply #3 on:** October 28, 2004, 04:30:23 am »

Problems in jffs2 Inode. Your pdaXrom filesystem image is certainly corrupted or not relevant.

Questions:

_ You are using the standard SL-6000 kernel recompiled with pdaXrom gcc and glibc version?
_ Have you modified the initrd and added the corresponding generated modules. I guess your issue come from this.
_ What kind of modification have you done into the pdaXrom installer?

Can a pdaXrom maintainer prepare an initrd and a kernel so people could test this?

nevarrie · « **Reply #4 on:** October 28, 2004, 11:39:20 am »

Quote

_ You are using the standard SL-6000 kernel recompiled with pdaXrom gcc and glibc version?

No...I was using the kernel I compiled for my openzaurus installs and I also tried the kernel that has the overclocking and the libsdl enchancements...I may try to uses the pdaXrom-builder adn try to create a rom and see if that makes any difference

Quote

_ Have you modified the initrd and added the corresponding generated modules. I guess your issue come from this.

I have not modified the initrd.bin file...I used the initrd.bin from kathrin-rc5.zip.

Quote

_ What kind of modification have you done into the pdaXrom installer?

I added in the lines for the SL-6000 model. The biggest change needed to make it work for the SL-6000 is this case statement:

Code: [Select]

           SL-6000)
              MODULESIZE=0x1E00000
             ;;
           SL-5600)
              MODULESIZE=0x1600000
             ;;
           *)
              MODULESIZE=0x1900000
             ;;
           esac

The other changes where so that I could uses my tools dir on my install media along with having the option of keeping several different initrd.bin files on my sd card and choice from the menu which one I wanted to flash. My updater.sh does work for the 5600 also...I have the source for the updater.sh up on my server in http://zaurus.thegrantclan.org/download/za.../updater.sh.src.

Quote

Problems in jffs2 Inode. Your pdaXrom filesystem image is certainly corrupted or not relevant.

I get the same kind of errors with openzaurus when the initrd.bin is to large for the partition. I did do a resize to 45 before flashing..The first time I set it to 50 but had problems with the flash erroring out.

Laze · « **Reply #5 on:** October 29, 2004, 05:44:53 am »

Sash has been looking into this.. First off all the lack of a SL6000 in our hands is a big problem but that might be fixed soon :-)

Secondly the chipset used in the SL6000 is completely different from the Cxxx series so there can be now hardware accelleration right now and some other things are different..

But rest assured that we are working on making support for the SL6000 and as soon we are closer to the complete version of Kathrin we will be looking into the making other hardware work with the pdaXrom.

amrein · « **Reply #6 on:** October 29, 2004, 10:24:00 am »

It's a good news. Thank for the info Laze.

Tehas · « **Reply #7 on:** November 28, 2004, 10:42:35 pm »

*Bump* I've been toying with the idea of a 6000 and would like to try pdaXrom.

cwaig · « **Reply #8 on:** November 29, 2004, 04:49:33 am »

Quote

Secondly the chipset used in the SL6000 is completely different from the Cxxx series so there can be now hardware accelleration right now and some other things are different..

Have you looked at Sharp's kernel source patch for the SL6000? There's some hardware acceleration support in the framebuffer driver included in their code (accelerated blits, etc). It's not much, and Toshiba haven't released the specs for the chipset, so it's the only reference available for how to code it

MrZaurus · « **Reply #9 on:** November 29, 2004, 04:57:16 pm »

Hello all I was reading some forums and saw a post mentioning pdaXrom on a zaurus 6000 but it was a few months old. I was still woundering if it was being developed. Thanks for all your help!!!!

Tyris · « **Reply #10 on:** January 12, 2005, 02:39:38 am »

Quote

Sash has been looking into this.. First off all the lack of a SL6000 in our hands is a big problem but that might be fixed soon :-)

Secondly the chipset used in the SL6000 is completely different from the Cxxx series so there can be now hardware accelleration right now and some other things are different..

But rest assured that we are working on making support for the SL6000 and as soon we are closer to the complete version of Kathrin we will be looking into the making other hardware work with the pdaXrom.

As noted earlier in the sl-6000 sub-forum, we've got a fairly large base of installed owners (seeing as how Amazon and other vendors are all sold out). Many of us are would like to support development of pdaxrom for the 6000.

Can any of the pdaxrom developers comment on the upcoming road-map for future releases, and whether there are plans to support the sl-6000. Also, is there a fund setup for hardware and further research/development on the 6000?

-T

adf · « **Reply #11 on:** March 08, 2005, 01:42:59 pm »

Did the pdaXrom team ever actually get a 6000? If so, great, if not could i get a pointer to the "buy the pdaxrom team a 6000" donation link?

edit: Just got a look at pdaXrom "in the flesh". WOW. absolutely outstanding. Had a brief moment of clamshell shopping immediately afterwards.

I'm absolute sure that it would look even better on my 6k. Really.

jdmoorman · « **Reply #12 on:** March 15, 2005, 07:19:41 am »

Laze,

I have a 6000 that I could loan to the team for an indefinite period of time, if it would be help.

Laze · « **Reply #13 on:** March 15, 2005, 12:13:29 pm »

Feel free to donate using the homepage and hardware can be sent to the adress on the homepage.

jdmoorman · « **Reply #14 on:** March 15, 2005, 12:53:29 pm »

Quote

Feel free to donate using the homepage and hardware can be sent to the adress on the homepage.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=70805\"][{POST_SNAPBACK}][/a][/div]

I'll try to get it boxed up tonight and ship it out tomorrow.
I think I still have the original box, manual, cd, etc.

News:

Author Topic: pdaXrom on SL-6000 (Read 9741 times)