Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - ThC

Pages: [1] 2 3 ... 18
Zaurus - pdaXrom / Pdaxrom Beta4 For C3000
« on: July 14, 2006, 11:21:18 am »
status update : I've made a few trys using altboot but OZ and pdaXrom's are not buildt the same way (no init.sysvinit nor chroot in pdaXrom's /sbin dir), beside OZ and pdaXrom not using the same glibc makes altboot unusable as any pdaXrom's binary used will segfault (maybe we'd be able to use it once it will be able to kexec by itself, or is there a way to configure it so it can do it ?)
Else I'm currently working on having uboot working on my c3000 ... more news soon

Zaurus - pdaXrom / Pdaxrom Beta4 For C3000
« on: July 12, 2006, 05:33:42 pm »

Just a little word to let you know that I'm still alive and starting to work on porting beta4 and uboot to our beloved c3000 ...

Sorry it took me so long to give some news but I had too much work ... btw i'm now in holydays so you can expect more news from me really soon

Don't hesitate to post your thoughts/ideas/tryouts which could help me doing it faster

C1000/3x00 Hardware / Initialize Hdd Error
« on: July 02, 2006, 05:53:53 pm »
did you try renaming the hdd1.tar file from trisoft to hdd1.tar.gz (without re-gzipping it, just renaming) ?
Else I'll try to get my hand on my own hdd1 backup or make you a new one  (try PMing me to ask if I don't answer here)

UK / Has Anybody Used Http://
« on: April 18, 2006, 11:02:17 am »
I've had my 860 from them ... but had to pay duties for it :/
btw they are cool, first time I burned my charging circuitry they repaired it for free (just had to send it back to them ...)

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2
« on: March 16, 2006, 03:25:16 am »
it's still 1.1.0b1 at the moment ... currently working on porting 1.1.0b2  (next beta ... will probably be named "1.1.0b2 for c3000 beta 1" then lol (sorry for such confusing names btw ... )

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2
« on: March 13, 2006, 07:19:11 am »
@Danboid : well , it seems that 2.6 kernel doesn't support bvdd yet which would be a showstopper for us (btw, the pdaXrom buildsystem is nearby ready to include 2.6 kernel once it will support everything ) (if I could live without video acceleration I would already have switched to OpenBSD )

@Meanie :
Not very security. I have ever corrupted my jffs2 root file system on nand flash with this. Turn off the MTD support on booted kernel.
this one is a little scaring, seems a little too risky to include it by default in a rom (even beta) (and, it would force me to build various kernels for various roms to be able to test dual boot in any way ... remember I'm a lazy guy sometimes )

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2
« on: March 12, 2006, 05:38:17 pm »
@Danboid : I don't think 2.6 kernel is mature enough for Cxxxx models (no sound support yet etc ...) I'm only planning to use it as a bootloader so we would be able to load pdaXrom's 2.4.20 kernel (and possibly cacko's one or whatever kernel we want to use with any rom we want to use )
Unfortunately, I'm not able to help in kernel development so we must wait for OE team to finish it (or join them to help them )
Some improvement I may bring to this beta may be an Xorg server by default (if I can get my dev env. ready and compile it well for Cxxxx)

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2
« on: March 09, 2006, 04:16:18 am »
unfortunately, sashz helped me a lot indeed, but mainly in working out the build system to be able to build the whole thing, so I didn't sent him much things while I was working ... btw I have a bakup of the files I had edited in the builder so I hope it won't be too long to have another dev environement up and running again (now need to make some room on my laptop to set it up, as I won't be using a pdax86 image located on an external hard drive anymore ...that's how I did lose everything ... having all my dev environment on a REV cartridge and VMware f***ing everything :/)
BTW, i really hope to have it up and running again very soon so i'd be able to produce a few more betas and send all my work to sashz (I must admit I didn't sent him anything before my crash because, knowing he's very busy with the pdaXrom dev, I wanted to give him something polished which wouldn't need any further work from him)

edit : as of programmers using pdaXrom, 2 of them helped a little bit but one of them don't have a c3000, while the other one finally switched to openBSD after giving me the pivot_root idea.

edit2 : (status update ) i'll try to work my next beta with a 2.6 kernel based bootstrap using kexec to load pdaXrom, which could allow us to have some real multi-boot as being able to load any kernel at boot time  (still have to make some tests though ...)

edit3 : if anyone want to speed up the process to a next beta, please someone try to compile a 1.1.0beta2 kernel for c3000 as I still have everything I need to work on making an image, but won't have time to set up a new dev environment (freeing space etc ...) before my next holidays, while I could work during my little free times in the meanwhile on a new beta image if I had a working 1.1.0beta2 kernel

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2
« on: March 07, 2006, 08:12:28 am »
Sorry for not giving much support recently but I don't have much time to work on this project right now as I got back to my studies which I have to pay so I need to work on my free time  (I didn't even had time to restore my build system since I lost all my work ... :/ )
btw I still have some of the things I did on another comp and I'll try to make another test release based on this beta2.
For the partitioning concern, the problem is that the partitioning is handled by sfdisk actually, which needs to know precisely the disk parameters. So I don't really know right now how to handle partitions for all the people out there who changed their microdrive with a 1Gb CF card or whatever ... (that's why partitioning is under a different menu and the install will work even if you don't do it or repartition by yourself)
@Danboid : I'd also need someone who knows Python better than me to fix this one, not ime to learn python right now to fix it for next release

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2
« on: February 27, 2006, 08:30:13 am »

You'll need to use pdaXrom's 1.1beta1 feeds (general and c1000-3100 specifics) ... that's probably why firefox doesn't work for you  You should find whatever you need there (else it's probably in the forums... )

Zaurus - pdaXrom / Call For Discussion: Dual Boot
« on: February 19, 2006, 11:30:50 am »
well, I dont think there's a real need to interfere in init-v process to dual-boot, the kernel swithing can be implemented either before or during the sbin/init scripts loading ... the glibc concerns are about being able to use the same kernel for the 2 used distribs which would be easyer (I'm a little bit lazy sometimes )...

Zaurus - pdaXrom / Call For Discussion: Dual Boot
« on: February 19, 2006, 11:11:13 am »
@jgardia : I guess this one is to be asked to sashz as he's the main developper of pdaXrom main branch ... i'm not even an "official" pdaXrom developper and I'm only working on the c3000 port on my free time (not as frequently as I would like to btw) ... beside, every package would have to be recompiled for a new release of pdaXrom that would use a newer libc (or we may be able to have some compat packages as we have for running some rc8 packages on rc10+).
Btw I don't know if sashz have time to work on this as it would probably require a lot of patches to be remade for everything to compile well .
I may try by myself to compile a pdaXrom version against glibc2.3.3 but I can't guarantee that I'll be able to achieve anything ...

I were proposing to compile an OZ distrib with downgraded glibc because OZ claims to be compatible with any glibc , which pdaXrom doesn't

EDIT : I'm not asking OZ team to downgrade their main branch to an older glibc, but am talking about haveing an other OZ-based distrib dedicated to multi-boot

EDIT2 : after 5 minutes of reflexion, i think kernel swapping is definitely the way to go as either we'll lose the advantage of one of the worlds as not being able to have their software library useable "out of the box"  (or move pdaXrom's main dev branch to a newer glibc which doesn't depend on me ^^)

Zaurus - pdaXrom / Kernel - Zimage
« on: February 18, 2006, 08:45:37 pm »
your kernel is under a partition of your flash memory called "smf" (/dev/mtdblock1 if I remember well ... don't have my zaurus with me to check but you can see it during boot time)

as far as I know there's no lilo/grub replacement yet, but there's boot scripts to load init scripts from different partitions ... nothing for different kernels though

it *may* be possible to reflash dynamicaly the kernel at boot time (using dd for example) but it seems a bit risky to me and I don't want to fry my zaurus trying this one

Zaurus - pdaXrom / Call For Discussion: Dual Boot
« on: February 18, 2006, 08:40:00 pm »
the problem is not about booting scripts as we already have some (like the one I'm using taken from oz booting scripts wich could permit us to dual boot with minor mods)... the problem is about libc used in different distrib ...
It would require either compile a pdaXrom with same libc as oz or sharp rom (only way to have a realy useable dual boot with sharp rom) or recompile an oz rom using same libc as pdaXrom ...
I already asked for people able to recompile oe using pdaXrom's libc but noone answered ... btw I don't have time for now to discover oz build system as I have to finish my work on pdaXrom one before ...

Zaurus - pdaXrom / Gemrb
« on: February 12, 2006, 06:36:53 am »
on the screenshots section of the site, there's a gkrellm launched and one can notice that 70% of cpu is used and it don't seem to have any other program open ... I guess this would be a little heavy for our poor little Zs :s

Pages: [1] 2 3 ... 18