OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: adf on June 02, 2006, 03:20:04 pm
-
I didn't become an initial tester. As a consequence, despite reading the threads, I've gotten confused about what the 2.6 based pdax can and can't do. Would it be too much trouble to run this or another thread that details the status of the system?
Right now, I'm immedialtely interested in largeer than 1 gig sd support, video overly/performance, and the the overall useablilty-- keymappng, etc.
Anyone who is running beta4/2.6 care to fill me in? maybe keep a running report?
edit: I realize much of this is on the initial thread, but so is a lot of discussion about fixing things that are now fixed.
-
I didn't become an initial tester. As a consequence, despite reading the threads, I've gotten confused about what the 2.6 based pdax can and can't do. Would it be too much trouble to run this or another thread that details the status of the system?
Right now, I'm immedialtely interested in largeer than 1 gig sd support, video overly/performance, and the the overall useablilty-- keymappng, etc.
Anyone who is running beta4/2.6 care to fill me in? maybe keep a running report?
edit: I realize much of this is on the initial thread, but so is a lot of discussion about fixing things that are now fixed.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=129505\"][{POST_SNAPBACK}][/a][/div]
I asked a similar question on the new site some weeks ago and am still waiting for an answer, the status of the present system would definitely be good to know .
cycle_55
-
I'd also like to know if the next version is going to be a stable version of what's come before or add yet more features to debug.
-
Oh and I am under the impression that the beta 4 rom requires a custom bootloader bin? Yes?
-
Oh and I am under the impression that the beta 4 rom requires a custom bootloader bin? Yes?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=129586\"][{POST_SNAPBACK}][/a][/div]
Right as i was thinking to open a thread like that, in these days i'm doing a deep test about it.
This is what i worked out. Other people sure had other impressions.
1) Suspend works better now, suspending and then opening again my Zauri result in a immediate resuming.
2) The .py utilities are to be completely rewritten, because they do only damages to the configurations file.
3) Keyboard maps are wrong, but you have only to load the right one with the xmodmap command in X.
The right keyboard map is in the /etc/X11/kb/Akita/xmodmap_us, only do a script that loads the right file when launching X and that' s it.
4) Partitions in the internal hd are recognizied correctly at the start, but i f you have more than 1 patition after the 1rst load you have to change the /etc/fstab file with the right scheme.
5) I worked out why my partition table was delete the last time.
Now command to eject and insert cards is pccardctl as pcmciautils package and if you eject your slot 0 that is the internal HD, if you insert it again the Filesystem do not resume.
And if you insert the HD again and try to reboot it will delete your partition table.
So if you have more than 1 partition it' s dangerous doing this. Because rebooting your table will be not recognized.
So if you eject inadvertitely your internal HD, leave it ejected and reboot not with the command from the shell but with your reset button.
I suggest you to make only one partition and if you want swap make a swapfile to have no risk of table corruption, as if your table is inadvertitely deleted you will redo it with fstab and the old files will be magically resumed.
Now, what i think about this Beta4 is that we are near to a stable solution, builder it' s more usable and kernel compilation do not bring to errors like the precessors.
The Zauri with the Kernel 2.6 it' s more usable, suspend works better, the drivers load perfectly and partitions at boot up are recnognized and not forced to the Zauri scheme as the older Betas.
Glibc iconv integration makes you compile nearly everything without problems now.
Good work Sashz.
Byez!!
-
Right now, I'm immedialtely interested in largeer than 1 gig sd support, video overly/performance, and the the overall useablilty-- keymappng, etc.
I've tried to write some files (around 200MB) to 2GB SD Card (Kingston, 160x) - it works. But I only tried it once (I haven't got any SD Cards myself)
-
So does this new bootloader work with other rom or does it mean we got to return to the SHARP bootloader to load other roms? hmmm
-
So does this new bootloader work with other rom or does it mean we got to return to the SHARP bootloader to load other roms? hmmm
You are correct... but for me,,, pdaxrom is what im going to stick with.... but for those who like to "Rom Hop"... it might be a problem unless others file suit with the boot loader... but i dont see that happening...
Late
-
to answer some of my quetions:
4 gig sd works
it seems pretty stable
i will try some previous firefox plugins: java, gplflash,and mplayerplugin to see what happens.
-
Got terribly busy with work and schedule since January and no free time to "play with" my beloved Z or even browing the forum until now. It's time to try out the new pdaX stuff.
Just flashed my C1000 to Beta4. Much more responsive. Nice thing. Great job. Thankz sashz!!
And I'm more than happy to help updating and (re)compiling the stuff from my contrib feed.
But at the same time I'm a bit concerned about the compatility between Beta4 and the older apps. Here are a couple of questions about compiling:
1) Learned that the new Betas no longer uses libiconv, but instead new glibc and locales. The result is I can no longer use the old compiled stuff (less, mrxvt, and especially the GTK2 apps). Seem no big problem got them compiled again. Actually I tried out Beta3 just for one evening and got some apps recompiled (which no longer need the older libiconv) using the zgcc 3.4.6 . But just a very general (and dummy) question: to what extent the apps from the old feeds and the contrib feeds (most were compiled for old pdaX versions) need to be recompiled?
And more importantly ...
2) It seems the very much needed multi language inputmethods (such as scim) just disappear from the new feeds altogether. I tried compiling the latest versions of SCIM and GCIN under Beta3 last night, assuming that the recompiled apps will need recompiled inputmethods (also not depending on libiconv) too. I could make SCIM, but encountered make install errors and got kicked out unexpectedly. GCIN complained about missing /usr/lib/qt3/plugins/inputmethods and /usr/lib/qt4/plugins/inputmethods . Any guidance is much appreciated.
3) Is it okay anyhow to use the zgcc 3.4.6 image from http://mail.pdaxrom.org/contrib/1.1.0beta3/Zaurus-7x0-860/ (http://mail.pdaxrom.org/contrib/1.1.0beta3/Zaurus-7x0-860/) to recompile stuff?
4) One more questions: I'm a bit confused by the tons fo locales in the Beta3 and Beta4 feeds. What should we do with them actually? Let say, for inputmethods, do we need the glibc locales for specific languages or something like that? Sorry for asking in such a vague way as I know virtually nothing about locales and encodings.
Thanks!
-
might be an idea to recompile everything when a release candidate or final version comes out, saves you recompiling over and over again. no?
-
Yeah, but I still need some working apps to do the "real" work. And it is not a bad idea for ppl to try some recompiled apps on the new Beta4, right?
-
dunno, what if beta 5 or RC1 is literally around the corner?
-
3) Is it okay anyhow to use the zgcc 3.4.6 image from http://mail.pdaxrom.org/contrib/1.1.0beta3/Zaurus-7x0-860/ (http://mail.pdaxrom.org/contrib/1.1.0beta3/Zaurus-7x0-860/) to recompile stuff?
Yep... it still works...
-
3) Keyboard maps are wrong, but you have only to load the right one with the xmodmap command in X.
The right keyboard map is in the /etc/X11/kb/Akita/xmodmap_us, only do a script that loads the right file when launching X and that' s it.
But I find xmodmap already linked to xmodmap_us. Still after exiting to the login shell, "A" and Up arrow keys (while the jog switch is working) won't function and need reboot. How do you fix that precisely? Thanks!
-
to answer some of my quetions:
4 gig sd works
it seems pretty stable
i will try some previous firefox plugins: java, gplflash,and mplayerplugin to see what happens.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=129699\"][{POST_SNAPBACK}][/a][/div]
Would you mind telling us which brand is your 4 gig SD?
-
it has a pink label on blue plastic that says MyFlash and 150x
I bought it for about $90 US at zipzoomfly.com
They listed it a a Patriot 4 gig 150x. It has been recently available at newegg, too.
right now the 4gig patriot at zzf is a 133x (for a good price, too). I wasn't able to find any on a quick search, but I bet if you poke around a bit you'll find one.
edit: while searching I found descriptions that match this card as as an "A-Data" brand.
-
Many thanks. Pity that both zzf and newegg ship within US only. Gotta find a friend to help me get one.
-
no luck with the firefox java plugin -- it wants libiconv.
Since cortez has posted java updates, maybe updating the plugin was about due anyway. I haven't got a 1.4 builder setup. Anyone who already has stuff compiling for 1.4 care to give it a whirl?
-
3) Keyboard maps are wrong, but you have only to load the right one with the xmodmap command in X.
The right keyboard map is in the /etc/X11/kb/Akita/xmodmap_us, only do a script that loads the right file when launching X and that' s it.
But I find xmodmap already linked to xmodmap_us. Still after exiting to the login shell, "A" and Up arrow keys (while the jog switch is working) won't function and need reboot. How do you fix that precisely? Thanks!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=129764\"][{POST_SNAPBACK}][/a][/div]
Right, there are 2 separated commands to load the map in the shell and X.
For the shell is loadkeys and you have to load the /etc/sysconfig/keyboard/Spitz/keymap.map
To have the a key functioning only press the fn key with it and then load the map with loadkeys.
I don' t really know now what' s the corresponding keycodes of the bare terminal environment as they are different from the X one.
In X i use xev, do you know there' s a corresponding command for the shell?
Byez!
-
Right, there are 2 separated commands to load the map in the shell and X.
For the shell is loadkeys and you have to load the /etc/sysconfig/keyboard/Spitz/keymap.map
To have the a key functioning only press the fn key with it and then load the map with loadkeys.
I don' t really know now what' s the corresponding keycodes of the bare terminal environment as they are different from the X one.
In X i use xev, do you know there' s a corresponding command for the shell?
Byez!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=129820\"][{POST_SNAPBACK}][/a][/div]
Thanks. I used loadkeys /etc/sysconfig/keyboard/Akita/keymap.map (instead of Spitz) and it seems to work. But the hassle is I need to do it every time X is loaded.
Still fiddling with xev. Hope can work it out soon.
-
Thanks. I used loadkeys /etc/sysconfig/keyboard/Akita/keymap.map (instead of Spitz) and it seems to work. But the hassle is I need to do it every time X is loaded.
Still fiddling with xev. Hope can work it out soon.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=129829\"][{POST_SNAPBACK}][/a][/div]
HEHHEHEH!! Yes i know, but it' s only a symlink to the /etc/sysconfig/keyboard/Spitz/keymap.map
Now, if you check the /etc/rc.d/init.d/x11 you will see the line
test -f /etc/sysconfig/keyboard/kernel.map -a -f /usr/bin/loadkeys && /usr/bin/loadkeys /etc/sysconfig/keyboard/kernel.map
The kernel.map file is the one edited by the inputconfig.py utility to change the map of the keyboard in X.
Just delete it and the problem will be fixed with it. As inputconfig.py for the 2.6 kernel doesn' t work.
BYEZ!
-
Thanks again for your quick tip and explanation, Xromer! I just renamed /etc/sysconfig/keyboard/kernel.map and now the keys come back. There are still a few things to tackle, such as the menu key is not mapped (pressing it won't bring out the X menu) and brightness is not mapped to any key (need to find a way to got setfl mapped somehow). Meanie has a modified keymap on his site. Will take a look soon and see how it fits.
By the way really thanks for your efforts to compile GPE pim stuff. Actually I have been trying them on my 860 (running Beta1). What I love most is the speed and lightweight, and most importantly I can use SCIM to input multilanguage characters in them!! But still have yet to get atd and alarm to work despite using your latest cvs. Will read thru that thread and ask later. Really looking forward to your Beta4 packages I am very happy to test them out.