OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> Where Has Pdaxrom.org Gone?, And openzaurus and oesf...
johnsutton
post Jan 25 2007, 06:37 AM
Post #1





Group: Members
Posts: 32
Joined: 28-April 05
From: Wales
Member No.: 7,019



I can't get through to pdaxrom.org, openzaurus.org redirects to http://openzaurus.linuxtogo.org/wordpress/ which is very pretty but otherwise useless, and oesf.org gives:

Warning: _loadcachedcode(/tmp/tpl_0_7_0_766ea99e632183d2b4f45e85d9bfe9c3.php): failed to open stream: Permission denied in /public/vhost/o/oesf/html/PHPTAL-NP-0.7.0/libs/PHPTAL/Template.php on line 430
etc...

In particular, where can I go to get the lastest pdaxrom?
TIA
Go to the top of the page
 
+Quote Post
Chero
post Jan 25 2007, 07:09 AM
Post #2





Group: Members
Posts: 1,141
Joined: 22-April 04
From: Belgium
Member No.: 2,962



The team is doing a lot of work on the main site so it's going up and down quite a lot.

Depends on what you want :
pdaXii13 by meanie on http://www.tyrannozaurus.com (please read the threads about it)

r10, r11, r12, beta1, beta3, beta4 and r121 on the pdaXrom.org-download-mirror :
http://distro.ibiblio.org/pub/linux/distri...axrom/download/

Chero.
Go to the top of the page
 
+Quote Post
johnsutton
post Jan 25 2007, 09:53 AM
Post #3





Group: Members
Posts: 32
Joined: 28-April 05
From: Wales
Member No.: 7,019



Thanks for that Chero. I've downloaded:

pdaXrom-1.1.0r121-Kathrin-akita-current.zip
pdaXrom-1.1.0r121-Kathrin-u-boot-akita-current.zip

but now what? There used to be docs on pdaxrom.org to show the way, but where are they now? I don't feel very confident about installing u-boot as I understand that it is possible to brick the zaurus while so doing?
Go to the top of the page
 
+Quote Post
Capn_Fish
post Jan 25 2007, 10:47 AM
Post #4





Group: Members
Posts: 2,350
Joined: 30-July 06
Member No.: 10,575



QUOTE(johnsutton @ Jan 25 2007, 12:53 PM)
Thanks for that Chero.  I've downloaded:

pdaXrom-1.1.0r121-Kathrin-akita-current.zip
pdaXrom-1.1.0r121-Kathrin-u-boot-akita-current.zip

but now what?  There used to be docs on pdaxrom.org to show the way, but where are they now?  I don't feel very confident about installing u-boot as I understand that it is possible to brick the zaurus while so doing?
*

To install pdaXrom r121 and uBoot:

-Do a NAND backup

-Put uBoot files on root of SD/CF card and put SD/CF card in Zaurus (one or the other)

-Open the battery door, hold down C+D, then press the reset switch. Mail and Power LEDs should come on, then turn off

-Remove SD/CF and put pdaXrom install files on the root of SD/CF (I believe you relpace autoboot.sh by doing this if you didn't remove the uBoot files to begin with).

-Put SD/CF in Zaurus, hold OK, and press the power button. You should get into the Emergency System. Say "y" to the prompt.

-Enjoy

EDIT: No, it's nearly impossible to brick a Zaurus software-wise.
Go to the top of the page
 
+Quote Post
johnsutton
post Jan 29 2007, 07:36 AM
Post #5





Group: Members
Posts: 32
Joined: 28-April 05
From: Wales
Member No.: 7,019



QUOTE(Capn_Fish @ Jan 25 2007, 07:47 PM)
QUOTE(johnsutton @ Jan 25 2007, 12:53 PM)
Thanks for that Chero.  I've downloaded:

pdaXrom-1.1.0r121-Kathrin-akita-current.zip
pdaXrom-1.1.0r121-Kathrin-u-boot-akita-current.zip

but now what?  There used to be docs on pdaxrom.org to show the way, but where are they now?  I don't feel very confident about installing u-boot as I understand that it is possible to brick the zaurus while so doing?
*

To install pdaXrom r121 and uBoot:

-Do a NAND backup

-Put uBoot files on root of SD/CF card and put SD/CF card in Zaurus (one or the other)

-Open the battery door, hold down C+D, then press the reset switch. Mail and Power LEDs should come on, then turn off

-Remove SD/CF and put pdaXrom install files on the root of SD/CF (I believe you relpace autoboot.sh by doing this if you didn't remove the uBoot files to begin with).

-Put SD/CF in Zaurus, hold OK, and press the power button. You should get into the Emergency System. Say "y" to the prompt.

-Enjoy

EDIT: No, it's nearly impossible to brick a Zaurus software-wise.
*



Thanks for that Capn_Fish. As it turned out, my mileage did vary somewhat, mostly (I believe) because my CF media are formatted as ext2. But I did get there in the end, and here is how for the benefit of anyone who might run into similar problems. This all relates to a C1000.

- the C+D reset didn't work - this just resulted in both of the leds flashing continuously. The solution was to use the usual option 4 on the Japanese menu accessed using OK+On/Off. This got the uboot/emergency system installed.

- OK+powerbutton didn't work, where by powerbutton I mean On/Off or the reset switch - neither of these options worked. Rather, it was necessary to remove the battery and then plug in the power adapter while holding down OK for about 10 secs. This successfully booted the emergency system.

- the emergency system did not pick up and run the autoboot.sh on the cf holding the r121 system, presumably again because it was formatted ext2? Or maybe because it was cf rather than sd? Anyway, it was necessary to run the autoboot manually. But first I had to get round another gotcha, namely that if I booted into the emergency system with the cf _already_ inserted, then any attempt to access the cf locks up the system! And this despite the fact that df shows the cf as mounted and available. The solution was to boot the emergency system to the bash prompt and _then_ insert the cf. It automatically gets mounted and now it is properly accessible and I entered:

sh /mnt/cf/autoboot.sh /mnt/cf

Bingo. After much ado and various points at which I thought I had indeed bricked my zaurus, I got r121 installed! It only remained to run it...

Oh dear... this is bleeding edge stuff and I need my Zaurus 24/7. I reckon it would take me a minimum of several days (if not weeks) of effort to get the new system into a usable state. But I gave up after these 2 problems: USB widget fails to start up so I could not get the thing connected to my desktop machine and so get an ssh session going, and this is a starting point for getting any serious amount of configuration work done. And then the final straw was that it could not read my 1Gb sd card. Alarmingly, it correctly detected that it contained an ext2 filesystem and mounted it, but showed it as empty! For a few horrible minutes I was convinced that it had deleted the contents of my sd card altogether. In fact, once I had reflashed with my beta1 system, I could see that the sd filesystem was intact. So how r121 could see it as _empty_ is really quite bizarre.

If there were a proper list of bugs and fixes somewhere (I can't find one?) then persevering with r121 would be an option. But without this, every person who wants to test it has to trawl through hundreds of forum posts (like this one ;-) searching for the fixes. In short, as a development process, this is a complete shambles ;-( Pity, because it has great potential, but without the proper infrastructure in place, it is I fear ultimately doomed...
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 23rd October 2014 - 09:55 AM