Help - Search - Members - Calendar
Full Version: Beta1 Vs Rc121
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > pdaXrom
Darth_Sith
Finally I'm be able to install u-boot and then rc121.
Kernel 2.6 is very very fast!
Suspend/resume are istantaneous, very good!

It's a beautiful rom, but there are may problem (bt, wifi, ipk ecc).
So I came back to beta1, that is the best for me.
But my question is: it's possible to swap 2.6 kernel in beta1?
With my old beta for example, Z can't read sd 4gb, and with driver works, but I can't unmount and the remaining size is wrong.
With rc121 it's perfect, but I have too problem.

So it's possible make what I'm saying?
ULhume
QUOTE(Darth_Sith @ Nov 23 2006, 05:19 PM)
But my question is: it's possible to swap 2.6 kernel in beta1?

As far as I know the "problems" with b4/b121 come from kernel 2.6 smile.gif so the real difference between b3 and b4 is this very swap... In kernel 2.6 there is no "original" binary drivers from Sharp, so that's a reason why there is some problems (ex. SD speed, usb as storage) and an other reason is driver developpement level (ex. Wifi drivers for my Symbol don't handle scanning in 2.6).
InSearchOf
Bt works... wifi works... ipk works (gui doesnt)... well the gui does... just it the refresh button...

I'm lookin for alternate means of managing ipkgs...


But no there really is no way... the reason alot of things aren't working correctly is because we had to change alot of things in the rom due to changeing to 2.6 kernel... alot of the thinging that worked with 2.4 dont work that same with 2.6 and changes needed to made... we are working out all the bugs as I type and we are hope to have another stable release in the near future...

Late
Late
ULhume
QUOTE(InSearchOf @ Nov 23 2006, 06:00 PM)
Bt works... wifi works... ipk works (gui doesnt)... well the gui does... just it the refresh button...

I'm lookin for alternate means of managing ipkgs...


But no there really is no way... the reason alot of things aren't working correctly is because we had to change alot of things in the rom due to changeing to 2.6 kernel... alot of the thinging that worked with 2.4 dont work that same with 2.6 and changes needed to made... we are working out all the bugs as I type and we are hope to have another stable release in the near future...

Late
Late
*

Just a question InSearchOf, is there any comprehensive document explaining how to build from scratch b121 ? And by the way, I didn't find b121 builder on the website... I'd like to fix this **** usb driver but if I follow the documentation I just end up with an explosion ;-)
InSearchOf
QUOTE(ULhume @ Nov 23 2006, 01:32 PM)
QUOTE(InSearchOf @ Nov 23 2006, 06:00 PM)
Bt works... wifi works... ipk works (gui doesnt)... well the gui does... just it the refresh button...

I'm lookin for alternate means of managing ipkgs...


But no there really is no way... the reason alot of things aren't working correctly is because we had to change alot of things in the rom due to changeing to 2.6 kernel... alot of the thinging that worked with 2.4 dont work that same with 2.6 and changes needed to made... we are working out all the bugs as I type and we are hope to have another stable release in the near future...

Late
Late
*

Just a question InSearchOf, is there any comprehensive document explaining how to build from scratch b121 ? And by the way, I didn't find b121 builder on the website... I'd like to fix this **** usb driver but if I follow the documentation I just end up with an explosion ;-)
*



Build from scratch? like from scratch scratch?

or just build the baseline ROM... but with your own apps?

Late

PS. use pdax86 liveCD to build with baserom but customized with your own apps from pdaxrom.org
Meanie
QUOTE(ULhume @ Nov 24 2006, 04:32 AM)
QUOTE(InSearchOf @ Nov 23 2006, 06:00 PM)
Bt works... wifi works... ipk works (gui doesnt)... well the gui does... just it the refresh button...

I'm lookin for alternate means of managing ipkgs...


But no there really is no way... the reason alot of things aren't working correctly is because we had to change alot of things in the rom due to changeing to 2.6 kernel... alot of the thinging that worked with 2.4 dont work that same with 2.6 and changes needed to made... we are working out all the bugs as I type and we are hope to have another stable release in the near future...

Late
Late
*

Just a question InSearchOf, is there any comprehensive document explaining how to build from scratch b121 ? And by the way, I didn't find b121 builder on the website... I'd like to fix this **** usb driver but if I follow the documentation I just end up with an explosion ;-)
*



you won't be able to fix the usb driver problem by rebuilding r121 but rather than that you will need to subscribe to msdn and get a development license for the new usb gadget driver for linux devices and also visual studio, fix up the driver and pay m$ to be allowed to distribute your fixed device driver smile.gif
InSearchOf
ULhume, are you talkin about the usb module on the Z... or the USB driver for XP? if for xp you would have to follow what Meanie posted above...

Late
ULhume
QUOTE(InSearchOf @ Nov 23 2006, 11:11 PM)
ULhume, are you talkin about the usb module on the Z... or the USB driver for XP? if for xp you would have to follow what Meanie posted above...

Late
*

No smile.gif) No XP for me, far too toxic for my organism... I just wanted to build some patch to the kernel 2.6 pxa usb driver.
InSearchOf
pdax86 LiveCD

It contains the building software...

Developement Write Up

Theres the documentation...

Late
ULhume
QUOTE(InSearchOf @ Nov 24 2006, 12:39 AM)
pdax86 LiveCD

It contains the building software...

Developement Write Up

Theres the documentation...

Late
*

Oh well, I see. To be honnest I *already* read this and if I just follow the process I end up with a bunch of compilation errors at the very middle of the chaintool building.

Don't take it the wrong way, I know that writting clear documentation is kind of a real work. But here, for us (at least for me) it is a real guess game... choosing the right configuration at the first place, fighting with wrong url for sources to finally end up with strange double-symlink errors in my case after hours is kind of a frustration... So when I was asking for a documentation, it was more a *real* experience of someone who built b121 from scratch, step by step.

No offence here, but anyone can observe that we can have very quickly a lot of missing softwares for pxr in just no time. Thank's to the cross-compiling package. But when it is about the "underground" stuff (wifi problems, usb problems, etc...), we have to follow Sashz pace. It is very difficult to contribute and I think the lack of solid documentation is part of the problem.

While we are in the subject, an other part of this problem is the lack of information/commucation. As an example, leaving messages in pxr bug tracking is point less when everything deseapear overnight. An other example, with b3 there was two chaintools, in b4/121, I didn't find any information about hard float/soft float chains, is it still needed ? Is the "soft" one can do the job now ? Mysterie... There is a beautiful shiny website where the last news is 2 months ago...

Well, it's late and perhaps did I spent to much time trying to figure out how to build this stuff. By the way, is there any serious reason for the need of this pdaXrom image ? It's kind of amazing to cross-compile in this psoedo-i386 distribution using vmplayer (because noone have a spare PC dedicated to this..).
InSearchOf
I will try to answer your questions as soon as possible... but if you want to use vmplayer, under a seperate OS to do compiling because you dont want to spare a pc... why can't you just just use vmplayer an boot off the cd?

I'm not sash or laze but I believe this was done to elimated a lot of questions being asked prior about things not working... it is was all due to files the user was missing... and or operating system incompatibilities... Yes, I did ask the question before about it, and I believe that is what the dev's were trying to accomplish...

But as I said earlier, Myself, Sash and Laze (and others willing to help) are working on getting all the bugs out of the system and also updating the documentation...

Give us a little bit and we will try and step it up a little bit...

Late
adf
All the hard work is appreciated.
It seems like the 2.6 stuff is getting pretty close. How's progress on the efltk config applets? ...and if those work out, would it not make a great deal of sense to base as much of the new rom's basic stuff on efltk/ede as possible? apps included where possible (realizing that gtk is inevitable, and QT will likely be needed as well) ? just a passing thought, but it might make things even snappier ...

EDIT: It appears that dillo is or will be able to be compiled on efltk...even more reason to at least give this a thought
ULhume
QUOTE(InSearchOf @ Nov 24 2006, 02:17 AM)
I will try to answer your questions as soon as possible... but if you want to use vmplayer, under a seperate OS to do compiling because you dont want to spare a pc... why can't you just just use vmplayer an boot off the cd?

I'm not sash or laze but I believe this was done to elimated a lot of questions being asked prior about things not working... it is was all due to files the user was missing... and or operating system incompatibilities... Yes, I did ask the question before about it, and I believe that is what the dev's were trying to accomplish...

But as I said earlier, Myself, Sash and Laze (and others willing to help) are working on getting all the bugs out of the system and also updating the documentation...

Give us a little bit and we will try and step it up a little bit...

Late
*

First my apologize, I was really tired tonight and my post was more bitter than what I felt in reallity. I know you are not laze or sash and this was not against you as you was the only one how dare answering my b121 bugs questions in the bugtracker (by the way, the host cable trick works perfectly).

About VMWare, openZaurus, as far as I know do the same job as pdaX86 but in a "simple" linux env. Using vmware eat resources whatever you do, at least memory. And that's in my opinion a waste of time dealing with wrong keyboard layout, installing missing softwares, etc... But why not if it was just working ou of the box (if this this the target of this so special distribution), but it is not...

Has I tried to explain (but my english is far from perfect and lack nuances) I really appreciate the work on pdaXrom, I'm using it for 2 years now on an everyday base. I seen work and evolution from the first RC I tried. But as a user that don't want to step back (kind of free software philosphy I think), I'm just getting frustrated not knowing what's going on. I made a lot documentation for Zaurus (in french, sorry smile.gif and 2/3 of it is only for pdaXrom. But I'm at a point that I just can go further with so few documentation, and most important, more informations and news, etc... And I think what really upseted me is to discover that all posts sent in bugtracker just deseapered overnight with no explanation (I leaved a message asking why but no answer). That is feedback illusion.

Just an other example, you say you are working on bugs, and improving this or that. But do you imagine the double work done by users if they don't know exactly what is in the pipe ? We try to add whatever application, having hard time to compile it and discover that, finally, it is now included in the next beta, waste of time. I wanted to fix the usb module trying to make usb storage gadjet working (at least try ;-) but perhaps I'll discover tomorrow that the new beta is already solving this issue, waste of time again.

So my post was too bitter but my frustration, is real even if I really appreciate all the work to make this distrib. Perphaps it is more frustration just because of that ;-)
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2015 Invision Power Services, Inc.