OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: sashz on May 17, 2006, 02:30:50 am
-
http://mail.pdaxrom.org/node/82 (http://mail.pdaxrom.org/node/82)
Next 1.1.0beta4 preparing for C7x0/860
-
great! Just now I wanted to look into the sound things and so on.
Thank you sashz!
-
Sashz, as i' m finishing compiling the Beta3 completely to add the rules-ipk for the GPE-Packages, when the Beta4 Builder will be online?
I had many problems compiling the kernel with the Builder.
Now i think that could be because you need the /usr/include/linux stuff already in the PdaXrom.iso X86 env to compile the kernel.
Do you think that this could be the problem?
Now that i understood better the builder composition, i will add the rules-ipk of the GPE-PIMS directly in the builder, so that dependencies will be satisfied automatically like the ROMS one.
Very, very good work Sashz, the Builder is perfectly functional now that i understood how to fix addresses of the packages and compilation rules.
Now, do you think the Pakacges i built with the Beta3 will work with the Beta4 release or i have to wait for the Beta4 builder to build them?
Because i have to know if i can flash directly the Beta4 or wait until all the Developing packages are online.
BYEZ!
-
super!!
I'll upload builder tomorrow, also pdaXrom beta4 for x86 (host system for builder )
Sashz, as i' m finishing compiling the Beta3 completely to add the rules-ipk for the GPE-Packages, when the Beta4 Builder will be online?
I had many problems compiling the kernel with the Builder.
Now i think that could be because you need the /usr/include/linux stuff already in the PdaXrom.iso X86 env to compile the kernel.
Do you think that this could be the problem?
Now that i understood better the builder composition, i will add the rules-ipk of the GPE-PIMS directly in the builder, so that dependencies will be satisfied automatically like the ROMS one.
Very, very good work Sashz, the Builder is perfectly functional now that i understood how to fix addresses of the packages and compilation rules.
Now, do you think the Pakacges i built with the Beta3 will work with the Beta4 release or i have to wait for the Beta4 builder to build them?
Because i have to know if i can flash directly the Beta4 or wait until all the Developing packages are online.
BYEZ!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=127415\"][{POST_SNAPBACK}][/a][/div]
-
Can you make sure the stylus problem fix is included please? https://www.oesf.org/forums/index.php?showtopic=19411 (https://www.oesf.org/forums/index.php?showtopic=19411)
-
1) Does anybody else find that their settings menu in fbpanel goes off the bottom of the screen? I can't always access the lower items. Is there a way to fix this?
2) I'm working on a fix for the LAN & WIFI applet to allow multiple profiles to work again (as this was a very useful feature). Is anybody else interested in this?
3) Is it possible to get the hostap utilities put into the main ROM in future versions? It's tricky to install them without wireless networking, which is why I need them. (Should I build my own ROM for this?)
4) Does video acceleration work with a standard video overlay?
5) When I tap the screen with the stylus, sometimes it does not register that I have un-tapped and the mouse stays down (for example, if I click on a button, the button might stay down until I click somewhere else). Is this something anybody else has found, and is there a way to fix it?
6) Thank you all so much! I really appreciate your ongoing hard work.
-
1) - patch coming soon
2) - yes!
3) - yes
4) - overlay driver exists but mplayer not support it yet
5) - need fix it
-
Here are two hacks I have made to make networking on my pdaXrom 1.1.0beta4 work more smoothly.
They're not pretty and not ideal!
pdaxrom-1.1.0beta4-network-applet-hack.tar.gz
This is a hack of network.py (The LAN & WIFI configuration applett).
It allows a person to use multiple profiles again, with the following restrictions:
If a profile is wireless, then the configuration will be applied to the wlan0 interface.
If the profile is normal, then the configuration is applied to the eth0 interface.
EXCEPT: if the profile is named usb0, then it is applied to the usb0 interface.
NOTE: Do not name your profiles wlan0 or eth0 anymore!
pdaxrom_1.1.0beta4_hostap_fw_fix2.tar.gz
This fix loads firmware into prism2 CF cards automatically when they are inserted, it's been updated so it works more often. (100% in my experience)
This is helpful for cards like: Netgear MA 701, Planex GW-CF11X, Linksys WCF11, etc.
See: A list of prism2 CF cards (http://www.netstumbler.org/archive/index.php/t-13713.html)
Enjoy.
-
5) If you tap the screen a bit longer there is no problem if you release it. If you tap and release fast then the Zaurus doesnt know that you already released so it remains "tapped".
-
There are two main problems I am having with using the latest beta - I am hoping someone can help me with these so that I can continue to use it I have a 3100.
- I can not get the right click with stylus to work (works fine with mouse of course). In the Input settings applet the default for right click is 'Fn' - but that does not work. I have tried the other options with no luck, except tap and hold for right click - but after the first tap and hold every tap is then a right click!
- after exiting X I can not type the letter 'a' - so I can not restart X - my only option is to type reboot, pull the battery out, or press reset. All other keys seem to work after exiting x - except A?
The only other problem I was having was the menu being cut off - but it looks like there is a fix on the way for that
thanks for the great work on this amazing rom!
-
It seems that you dont have the latest release. In the first beta4 release I also had that problem with "A" after exiting X.... but now it is gone.
look here: http://mail.pdaxrom.org/node/82 (http://mail.pdaxrom.org/node/82)
-
wow, I'm starting to love this rom!
I almost dismissed using this rom as it seems you need to always run as root to allow things to run smoothly. However, I've now gotten used to the idea and it does infact simplify things (though Im sure Ill change my mind when I accidently rm -rf / or something ).
I'm having similar problems to the others in this thread, but sashz has identified them so I wont repeat them. I would like to second gromituk's request for the stylus fix though. Tapping and holding a scroll bar becomes an annoyance when the page you are trying to read keeps jumping about. The stylus doesnt need to be that accurate, so giving it some breathing room for tiny movements would be good.
Now the problems Ive been having:
1) one problem that i havnt seen mention is the jogwheel on the side of the Cxxxx doesnt seem to be working properly... only 'up' works on it. Also only the down key on the min keyboard has repeat keys ie. press and hold and it keeps scrolling a webpage. I have to use the jogwheels up to scroll back up in a similar fassion as the up keyboard key only pressed once when you hold it down.
2) The delay from pressing and holding a key to the key repeating seems too short. I often accidently enter 2 or 3 of the same key. Is there any way to change this delay?
3) The clock time and date keep resetting when I reboot! it keeps join back to 1970 jan 1st, so to compile anything I need to set the time again after reboot otherwise it sees my build environment is not sane
4) I cant tear myself away from the Zaurus now, and as a result I'm getting very little sleep. Can anyone recommend any good caffine products
Keep up the good work - if all this gets fixed (except number 4 ) I'll start donating on a regular basis, and I'll make it my mission to get other people to donate too - if i'm really happy I will donate a small percent of profit for every Zaurus I sell when I start selling them
Thanks,
Phill
-
3) The Z doesn't seem to have a powered RTC chip, so if you take all the power away, you lose the date and time. Install the ntpdate package and run "ntpdate pool.ntp.org" to set the time easily when connected to ethernet or wlan or something... it's not ideal, but pretty easy.
4) Live in the UK? Try Red Bull or one of the ripoffs like Blue Charge, Kick, etc... (or pro-plus if you like pills)
Live in the US? Try Mountain Dew (banned in the UK) (or vivarin if you like pills -- very strong!)
Live /anywhere/? get a caffatiere and buy some freshly ground coffee and make a nice cup of alertness
--
Has anybody found that their Z becomes unstable now when overclocked? I find in 520 I often get super-distortion on the screen and in 624 it's often to unstable to use, especially with a wifi card attached... might this be too much current being used?
Any ideas?
-
3) The Z doesn't seem to have a powered RTC chip, so if you take all the power away, you lose the date and time. Install the ntpdate package and run "ntpdate pool.ntp.org" to set the time easily when connected to ethernet or wlan or something... it's not ideal, but pretty easy.
4) Live in the UK? Try Red Bull or one of the ripoffs like Blue Charge, Kick, etc... (or pro-plus if you like pills)
Live in the US? Try Mountain Dew (banned in the UK) (or vivarin if you like pills -- very strong!)
Live /anywhere/? get a caffatiere and buy some freshly ground coffee and make a nice cup of alertness
--
Has anybody found that their Z becomes unstable now when overclocked? I find in 520 I often get super-distortion on the screen and in 624 it's often to unstable to use, especially with a wifi card attached... might this be too much current being used?
Any ideas?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=127613\"][{POST_SNAPBACK}][/a][/div]
I'll pickup some redbull ripoffs on my next shopping trip
Okay, I guess the network time will do fine, I'll mainly be around a wifi access point anyway.
I have overclocked to 624 fine. I have been running at that speed while compiling and I havnt noticed any problems yet.
-
Thats funnny... I found the overclocking potential of beta4 to be something really *special*. When I first overclocked I didnt believe that it was because the screen had no distortion or something else... just the speed and the really told me that it was OC'ed... really nice!
-
3) The Z doesn't seem to have a powered RTC chip, so if you take all the power away, you lose the date and time. Install the ntpdate package and run "ntpdate pool.ntp.org" to set the time easily when connected to ethernet or wlan or something... it's not ideal, but pretty easy.
I dont think this is the issue... Beta3 works fine with the time... I believe it is because... before shutdown the script to sync software time to hardware time doesnt run....
I ran beta4 for a week and I had the same problem... but I dont remember seeing it at shutdown...but I defiently seen the hardware clock syncing at startup....
May tonight now that I got my "PERFECT SETUP" nand with beta3... I will install beta4 and pick at it again....
-
Our 2.6 kernel was done right - not like 2.4-crapix which Sharp gave to us
-
I am running beta 4 on my 3200. My biggest problem is that my microdrive is being mounted as my cf card. I can't seem to figure out how to address this problem although, I know I could probably modify fstab somehow.
Any suggestions?
Also, fbpanel randomly crashes occasionally, leaving me with a massive white line aross the bottom.
Nice work guys. I am really impress aside from these two minor things!
--Fish
-
Just open your fstab and change the mount point of /dev/hda1 (which should be /mnt/cf) to /mnt/ide1. You can also change the "noauto" option to "auto" so that the microdrive gets mounted everytime you boot your Zaurus.
-
For beta4
I have a problem that my network cf card gets mounted as a storage device initially. So I have to unmount the phantom drive and then re insert the wlan wireless cf card to get networking working.
Is there an equivilant to bvdd in beta4?
mplayer -vo bvdd gives not such device
darmou
-
This kernel doesn't support the bvdd device driver at the moment (Is this a 2.6 thing?)
But if you do a "xrandr -s 1" before playing a video, and use "mplayer -vo sdl" I find it to be very acceptable.
On my C3100, when I overclock to 520 I find the screen gets really choppy when the Microdrive does access. I didn't have this problem with OZ or beta2. If the microdrive is really being used hard, and the screen brightness is high, and the cpu is in 624MHz, if I plug in my wifi CF, then random programs segfault the screen flickers and the whole unit then locks up hard. I'm using the latest beta4 which in every other way is lovely. Has anybody else found any problems at all with this? If not, I'll re-flash from the start, and see if it still happens.
-
Ok, my compilation of Beta3 it' s going on.
Now i have little problems understanding the dependencies management of the Buillder.
For the reason that i didn' t compile the kernel, pcmcia-cs doesn't compile and the compilation stopped.
I removed it from the compilation on the .config file, but the Builder tries to compile it the same.
When i removed the kernel compilation it worked, why now it doesn' t?
I removed the pcmcia-cs.* files in the state dir, but it still won' t go on.
Now is another packages requesting it??? And where are the files that decide the compilation priorities and dependencies?
How is the depends.out generated?
That' s the only thing i' m trying to understand, to have a better vision of the Builder and help you in compilation Sashz.
THX for the builder and the Iso beta4, i' m just downloading it and will try tomorrow.
Tomorrow i will try the 2.6.15-openmosix kernel with the make -j option for compilation i will let you know.
I think that controlled by a script that decides the depend priority like the Builder's one, the parallel compilation could work.
:-) Too many things have to try tomorrow, upgrade to Fedora5, OpenMoSiX, Builder4, new GPE-PIMS.
Hope to survive!!! Bye GUYS!!
-
I was able to get the bvdd driver installed on Beta 4, and it seems to work, though I was testing it with bvdd enhanced SDL, and not mplayer.
I got the bvdd.0.4.0 IPK, and installed it. I'll put up instructions for the latest revision to beta 4 if needed. I think it was bvdd that I needed to unpack the IPK and manually install it due to some folders not existing that it wanted to unpack to.
Either way, I have a /dev/bvdd and a working init script. So I'd imagine it's worth a try installing that IPK and seeing if it works with mplayer. If someone tries it out with mplayer, let me know if it works for you.
Thanks
-
I was able to get the bvdd driver installed on Beta 4, and it seems to work, though I was testing it with bvdd enhanced SDL, and not mplayer.
I got the bvdd.0.4.0 IPK, and installed it. I'll put up instructions for the latest revision to beta 4 if needed. I think it was bvdd that I needed to unpack the IPK and manually install it due to some folders not existing that it wanted to unpack to.
Either way, I have a /dev/bvdd and a working init script. So I'd imagine it's worth a try installing that IPK and seeing if it works with mplayer. If someone tries it out with mplayer, let me know if it works for you.
Thanks
[div align=\"right\"][a href=\"index.php?act=findpost&pid=127899\"][{POST_SNAPBACK}][/a][/div]
Awesome news. I am very new to pdaxrom and the zaurus in general (I used to only run OpenBSD and use it mainly as a server), so just the fact that I can get some kind of acceleration for SDL working in beta4 sounds great to me . I've been programming my SDL to be playable for the Zaurus with no acceleration, so this should give me some more leeway.
Can you perhaps point me in the right direction to setting up SDL to use bvdd in my programs?
I've been running beta4 since this release and its been great - I have my XFCE 4.4 beta environment setup nicely but with 1 thing missing -> Is it possible to enable XComposite? I tried looking for an XFree config file but couldnt find anything. Hey, I got it working beautifully on OpenBSD (in portrait screen mode) - everything ran incredibly smoothly - so you can't say it will be too slow. It may slow something things down, but it would brighten up my desktop when using just text editors, webbrowsers etc.
Thanks,
Phill
EDIT: zodttd! your paypal donation link in your signature doesnt seem to be working. It just takes me to a page that says: "You have entered unsupported characters for this field. Current available language character types are: European, Chinese, Korean, Japanese, and Thai. Please try again."
Also... i cant find this bvdd ipk where is it?
-
Well no such luck. I installed the newest beta 4, and got bvdd module on it by copying the /lib/modules/2.4..... contents to /lib/modules/2.6.16/ and it installed the device.
I ran the init script just in case. /dev/bvdd is installed. But it probably has to be compiled for 2.6.16 or it won't work.
I tested bvdd with mplayer_bvdd and it couldn't load /dev/bvdd
As for SDL, I'm assuming it reverts to a different renderer if bvdd isn't found.
Phill: For now, if you want bvdd you will need beta 3 and it's SDL_1.2.9_armv5tel IPK. I imagine bvdd will work soon on beta 4. It probably just needs a recompile.
-
Thanks for the heads up on the donation link Phill, it's now fixed. I was wondering why I hadn't received a donation from the Zaurus community yet. Time to get working on ZPSX so that link has some more use.
-
Thanks for the heads up on the donation link Phill, it's now fixed. I was wondering why I hadn't received a donation from the Zaurus community yet. Time to get working on ZPSX so that link has some more use.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=127909\"][{POST_SNAPBACK}][/a][/div]
Donated! And I encourage others to donate too. This is one of the most interesting projects on the Zaurus!
-
Thanks Phill! I really appreciate it!
Now that Beta 4 has overclocking capability, all it needs now is bvdd, and the PSX will be playable on the Zaurus. pdaXrom is advancing well.
sashz: Is bvdd working on your end already?
-
Guys help me, there' s something i miss.
6) Extract files to this or another CF or SD card, there must be: rootfs.img kernel.img autoboot.sh
7) Run diagnostic menu (D+M) and run NAND Flash Erase from Extra Menu. (ADDED)
Whate the hell is D+M i press D and M keys of the keyboard and On toghether but nothing happens,
it boots normally.
8) Turn OFF your zaurus. Unplug power adapter, eject battery.
9) Insert SD or CF card with extarcted files (if you insert both CF and SD, updating fails)
10) Press and hold "C" and "D" keys and plug power adapter (battery must be ejected!).
C nad D??? Normal keys??? Do i have to pull out the battery, close the cover and use the Zaurus with the cover closed and wihout the battery, pressing C and D and ON??
BOH!!!
BYEZ!
-
7) Run diagnostic menu (D+M) and run NAND Flash Erase from Extra Menu. (ADDED)
Whate the hell is D+M i press D and M keys of the keyboard and On toghether but nothing happens,
it boots normally.
You must have no battery first, then press and hold together D and M keys, while holding them plug the power cable. The diagnostic menu should appear after 1 second.
10) Press and hold "C" and "D" keys and plug power adapter (battery must be ejected!).
Same thing as above but with C and D keys. You have too wait at least 10 seconds before something happens this time.
-
I'm having problems with the tab key acting as Caps Lock without the Fn being pressed first. So every tab press toggles Caps lock, very annoying
I've tried playing with the xmodmap_us even to the point of deleting the section that controls the Caps lock to no avail.
Anyone experienced this or has a clue on how to fix?
TIA
Jerry
-
7) Run diagnostic menu (D+M) and run NAND Flash Erase from Extra Menu. (ADDED)
Whate the hell is D+M i press D and M keys of the keyboard and On toghether but nothing happens,
it boots normally.
You must have no battery first, then press and hold together D and M keys, while holding them plug the power cable. The diagnostic menu should appear after 1 second.
10) Press and hold "C" and "D" keys and plug power adapter (battery must be ejected!).
Same thing as above but with C and D keys. You have too wait at least 10 seconds before something happens this time.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=127954\"][{POST_SNAPBACK}][/a][/div]
Thanks scheck.r as always!
Flashed perfectly, now i' mporting all in Beta4.
That' s what i did until now.
1) Extracted PdaXrom4 Env for X86 and made an RPM package for FC4.
2) Made a builder.txt file for this package installation and for pdaxrom4 env cross-compilation.
3) Just compiling the new Beta4 SDK, i think a will make an RPM package as well.
If you think this stuff could be useful, i will put it on my contrib.
BYEZ!
-
I've been having a go at making beta4 as useable as beta2 and 3, I've got the right and middle click to work again properly.
(swap the numbers in /etc/sysconfig/x11mousebutts) to get default (working) beta2 behaviour.
I want to make my Z run the apm suspend and resume scripts. (To unmount samba, restart CF cards, lock the screen, pause xmms/mplayer, etc) Does anybody know how to make the power button execute "apm --suspend" rather than suspending instantly?
-
Hello, have problem on my C1000 - i think sound not working - cant add anything to xmms, also when i try make alsaconf i get:
line 102: getopt: command not found
if alsamixer i get:
error opening terminal : rxvt is it normal?
And my touchscreen working not good - when im press to close button (X) - nothing happend.
Thx in advance.
-
Hi, I've got on the boat!
So far, the problems with my C1000 are...
1. lots of jffs warning messages at boot
2. a missing application in fbpanel (the second one from the left)
3. ppp does not connect
The last one really is the problem.
I found ppp device has changed from /dev/ttyS3 of beta1 to /dev/ttyS0 now.
I did the exact same manner as I did in beta1, which was successful.
The card I use is SII MC-C450 and it is well recognized by the fbpanel applet.
Here is the output.
# authdrv ttyS0 debug call bitwarp
abort on (NO CARRIER)
abort on (NO DIALTONE)
abort on (BUSY)
send (ATZ^M)
expect (OK)
alarm
Failed
Connect script failed
Is there any Japanese user or user in Japan who uses So-net service and succeed in using it with beta4?
P.S. (this report is a repost of mine in another thread, which I deleted.)
-
So far, the problems with my C1000 are...
1. lots of jffs warning messages at boot
This is due to flash driver which Sharp used under 2.4 kernel. Akita/Borzoi/Terrier all probably got same situation.
-
er... I rebooted a couple times and it started working just fine. imagine that.
-
Found one issue with overclocking: at 624MHz screen becomes very shattered after resume. Exit matchbox and found keys like "A" missing. Everything comes back after reboot. 520 MHz seems ok. Anyone got this also?
EDIT
Strange. Every time I launch CPU Config, it always shows 416 MHz. Does that work?
EDIT 2
The keymapping thingy is just a separate issue, as was discussed here: https://www.oesf.org/forums/index.php?showt...ndpost&p=129595 (https://www.oesf.org/forums/index.php?showtopic=19724&view=findpost&p=129595) (Xromer's point 3)
Got another situation: after reboot CF card fails to mount. I need to eject and reinsert the card to get it recognized.