Messages

16

Zaurus - pdaXrom / Can Someone Compile The Last Aircrack?

« on: February 06, 2006, 07:46:16 am »

they seem to work ... didn't have time to test them all btw ...

17

Zaurus - pdaXrom / Gp2x Psone Emulator Running Realy Fast

« on: February 01, 2006, 12:02:23 pm »

Hi,

I'd firstly want to thank you for your work ... I tryed once to compile fpcse for zaurus and only that was a real pain so I can imagine you're into a very hard work

I'd also want to tell all c3000 users out there that it works perfectly using my pdaXrom beta on c3000

I've tryed bloody roar 2 (only game I had with me .. will try other @home this weekend) and it works ... very slowly but it works ... btw I've been unable to try with HLE as it don't seems to work (I tryed pressing h, shift-h, capslock before launching then pressing h while selecting game ...) ... is it disabled in latest build ?

18

C1000/3x00 General discussions / C3100 And Windows Mobile 5.0

« on: January 30, 2006, 11:43:35 am »

I guess it will be useless for what you're trying to do ... it was running over a x86 emulator (bochs) and was too slow to be really useable (imagine running w98 on a old 386  .. beside I don't know if it would be able to handle any device connected to the zaurus such as a gps receiver)

19

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2

« on: January 28, 2006, 08:57:56 am »

then you don't have to do anything, the hdd resize utility won't check for original partitions (that's why it's only compatible with standard internal hdd at the moment) so you just have to follow the instructions at start of the post and then to apply meanies instructions to patch all files that need to be patched and you're done

20

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2

« on: January 28, 2006, 07:10:16 am »

I dont exactly understand what you are trying to achieve ... are you still trying to dual boot ? if so, maybe you could PM me and tell me what problems you had the first time

21

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2

« on: January 28, 2006, 06:51:09 am »

the installer won't restore the original content of HD ... btw I have the project of producing an updater script which will be able to restore a c3000 to factory state (would just be a matter of producing another hdimage.tgz with original hdd content) ... btw, such a file can be found using the search feature for a topic about c3000 restore from scratch, with instructions on how to use it

btw, after resizing the partitions to default, you could also use directly the cacko installer which will restore hdd content with it's own , or, if you wanted to install my pdaxrom beta, just continue with my installer, extracting only the first tgz file to your CF root

22

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2

« on: January 25, 2006, 06:18:35 am »

Thx meanie for all these fixes ... I'm going to try and take some time to get all these fixed in my install image and make a new one without all these bugs ... I hope to have it done by the end of the week but, once again, don't want to make false hope to you all so I can't promise anything but I'll really try to get time to do that

23

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2

« on: January 24, 2006, 03:55:30 am »

@pyknite : using usb network and samba ... btw sorry but I don't have time to document it right now (but you should find some docs on how to do it searching on the forum )

24

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2

« on: January 19, 2006, 03:28:47 am »

Yes, the scripts should just work on a 3100  (3000 and 3100 are not that different )

25

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2

« on: January 19, 2006, 03:17:21 am »

the "few" problems you experimented are all normal with actual dual boot methods as diferent Zaurus OSes use different kernels/libs as I was telling in my precedent posts...
Beside, this install simply won't work to create a dual boot as installer in canging initrd image with a pivot_root only image so you won't be able to boot cacko anymore.
I suggest you take a look at my topic about dual booting pdaXrom on a c3000 and try to apply it using a more recent snapshot. (the hdimage.tgz included in the actual installer for c3000 is more or less a 1.1.0beta1 snapshot so you may use it if you want  )

the dual bot I'm now trying to achieve will be a little more evolved as t would allow us to  keep multiple OSes on HD partitions, choosing the one to boot during boot time, like any other comp.  (btw, I must admit that most of my ideas toward realizing a true multi boot management are scaring me so I don't have guts to test half of these ... too afraid of bricking my Z dd'ing a new kernel to /dev/mtdblock1 during boot process for example lol)

26

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2

« on: January 19, 2006, 02:43:35 am »

@anonuk : there is still no "dual boot" available as I'm still only dreaming about it and will have to recompile a whole OZ dist against pdaXrom kernel/libs so they can be dual booted well (well ... I guess I could use an actual snapshot but there would be a lot of non-working things then I guess) ...

btw, the actual pivot_root image *should* work on a 3100 with minor mods in the updater script... so if it's the pivot_root you want to test, let me know and I'll send you an updated updater script (keep in mind I won't be able to test it to any extent as I don't have any 3100 to test with)

ps : I'm also thinking of (and talking with iamasmith about this) makeing a pdaXrom/OpenBSD dualboot if enough people gets some interrest into it ...

27

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2

« on: January 18, 2006, 07:44:22 am »

Hi,
I'm taking some rest right now and working a very little bit on remaking my builder environment as I lost everything recently ... beside, some personal problems I did put aside for a while have to be resolved so it'll take a while untill next release...

btw, this rom is ready to be used out of the box, you'll just have to modify the network.py file as described above as it seem to be the only really annoying bug so far (there are a few others bug which one can live with untill a next release, depending on his needings/capacities) and most of the bugs have been fixed in this topic so you may be able to reproduce fixes on your install

I think the better thing would be to backup your datas and try it by yourself so you can see if you can live with its bugs or if you prefer going back  

Btw I may consider making a fixed image, based on fixes provided in these lines if I get some time to do so, but don't want to make any promise as I'm not sure to have time

28

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2

« on: January 13, 2006, 04:14:24 am »

/usr/bin/usbfunction.py line 21:

Code: [Select]

STORAGE_OPTS = ["/dec/mmdca1", "/dev/hda1"]I guess what the second item of array have wrong value. The right string is "/dec/hdc1" (for CF).

/usb/bin/looknfeel.py lines from 1014 to 1018:

Code: [Select]

 if self.PANEL_LEFT_MARGIN != "" and int(self.PANEL_LEFT_MARGIN) >= 1 and int(self.PANEL_LEFT_MARGIN) <= 600:
    write_str = write_str + " --margin-start \"" + str(self.PANEL_LEFT_MARGIN)+ "\""

  if self.PANEL_RIGHT_MARGIN != "" and int(self.PANEL_RIGHT_MARGIN) >= 1 and int(self.PANEL_RIGHT_MARGIN) <= 600:
    write_str = write_str + " --margin-end \"" + str(self.PANEL_RIGHT_MARGIN)+ "\""If you try to ask the matchbox-panel for help ("matchbox-panel --help") you can see what it havn't "--margin-start" or "--margin-end" options.  So when you set panel margins in "Look-n-Feel" dialog you will be confused with startx script result.   

/etc/fstab line 1:

Code: [Select]

/dev/hda1    /mnt/cf  auto    noauto,owner    0  0It's the same problem as in 'usbfunction.py'. /dev/hda1 is not a compact flash device. I have replaced "hda1" to "hdc1".

That's all, folks! 
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110719\"][{POST_SNAPBACK}][/a][/div]

actually, it depends. the external cf can be either /dev/hda or /dev/hdc. this is dynamically mapped depending on how you booted, ie with the cf inserted or not.
the first disk detected is always hda and the second disk hdc
when u boot without a cf inserted, the internal microdrive will be hda and your cf will be hdc
if you boot with the cf inserted, your removable cf will be hda and the internal disk will be hdc
thus hardcoding hda or hdc is not a good idea. the script should check which one is the internal drive dynamically, thus adding an entry in fstab is a bad idea unless you also write a script to dynamically update fstab during bootup.
given that the pivot boot pivots to the internal disk and in order for it to be booted, the cf card has to be removed during boot, but this feature might and probably will change.
i personally think that it is a good idea to allow the pivot to either boot from the internal disk and ignore the inserted cf, or boot off the cf instead for dual booting. this should be a configurable parameter.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110781\"][{POST_SNAPBACK}][/a][/div]

Actually, as pivot_root init script is not managing external CF slot, CF will be hdc in all cases so he's right and it's my fault forgetting this one

I may do a multi-boot script but I'm not sure of it's utility as sharp/cacko, pdaXrom and OZ uses different libc/kernels, we'll have problems dual-booting to any of these.
A soluion would be to build a "special" OZ version against pdaXrom libc and kernel so we would be able to have a pdaXrom/OZ dual boot but I have to finish my work on the pdaXrom builder before starting to learn using BitBake.
If someone is interrested in helping me and allready know how to use a different libc / kernel in BitBake and have time to do so, please contact me and we'll talk about the possibility of makeing a dual-boot install (and, why not, haveing both on the internal MD, each one having its own 2Gb partition) or a dual-boot image and a special OZ cramfs to put on a CF ...

@Jondalar : Edit /usr/bin/network.py
line 1071 : replace "/usr/sbin/cardctl eject " by "/usr/sbin/cardctl eject 0"
line 1075 : replace "/usr/sbin/cardctl insert " by "/usr/sbin/cardctl insert 0"

29

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2

« on: January 12, 2006, 04:11:11 am »

Could someone with a C3100 give me the output of "sfdisk -l /dev/hdc" with a standard partitionning please ?
(sfdisk should not be disponible booting on pdaXrom or cacko/sharp rom so you may need to do it while booting in with D+B or using pdaXrom's installer

30

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2

« on: January 12, 2006, 02:46:57 am »

@desertrat : choosing a partition would add to much complexity too (need to change some config files in the pivot_root image dynamically to do such a thing...), btw, it will automatically install on the first partition of the hard drive, which only need to be > 128Mo ...so you can partition it as you want as long as you let a first partition greater than 128Mb ... after it will just be a matter of editing your fstab after first reboot.

As for the cf in slot while booting problem : this one is a bug encountered by openembedded too ... I'm going to make some tests to see if I can get rid of this one, using some HD detection scripts as I did in the installer but I'm not sure whether the pivot_root image I borrowed from openemdded will support these scripts .

@C3100 users : I'll try to produce a testing pivot_root install soon ( will just be an update in updater.sh btw) so you can test if pivot_root is more efficient than this "symlink nightmare" some of you seem to have