Author Topic: Beta 3 Fixes, Customs, Contrib  (Read 18200 times)

adf

  • Hero Member
  • *****
  • Posts: 2807
    • View Profile
    • http://
Beta 3 Fixes, Customs, Contrib
« Reply #30 on: October 02, 2006, 03:58:39 pm »
Quote
I added the info about the pointer for 7X0-860 series. Beta 3 isn't really the best release for those machines though. Beta1 is much more stable on them, but beta3 is best for C1000 and higher.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=142857\"][{POST_SNAPBACK}][/a][/div]
maybe we should consider some way of labelling an updated, remixed beta as '2.4 final " for the various 2.4 based versions?
**3100 Zubuntu Jaunty,(working on Cacko dualboot), 16G A-Data internal CF, 4G SD, Ambicom WL-1100C Cf, linksys usb ethernet,  BelkinF8T020 BT card, Belkin F8U1500-E Ir kbd, mini targus usb mouse, rechargeble AC/DC powered USB hub, psp cables and battery extenders.

**6000l  Tetsuized Sharprom, installed on internal flash only 1G sd, 2G cf

loji

  • Full Member
  • ***
  • Posts: 130
    • View Profile
    • http://
Beta 3 Fixes, Customs, Contrib
« Reply #31 on: October 02, 2006, 04:07:42 pm »
I would love ot .. but firstly we need to build a new stable system.  I've made a persistant home from the pdaXrom CD (which didn't work when i ran setup like the instructions say ... I had to extract the rootfs.bin and place it in the root of a FAT directory) I also found the Dl for IMageBuilder which allows you to slipstream ipks into an installable image. (ie: add rox, etc...) but I don't know enough, I tried to run qmake like the instructions say, and it errored saying something about not being set-up correctly.

If someone wants to help with compiling or giving info: I'd much welcome it.
-> pdaXrom beta 3 fixes & feeds
C-1000 + pdaXrom beta3
linksys wifi + expansions

adf

  • Hero Member
  • *****
  • Posts: 2807
    • View Profile
    • http://
Beta 3 Fixes, Customs, Contrib
« Reply #32 on: October 03, 2006, 02:41:25 am »
Huh... I had assumed it would be pretty straightforward.  Well.. I can setup an older machine for the purpose of experimenting, I suppose- but it sounds like I'll get pretty much the same results you did.

ps.  If we do get it to work, maybe r0x + a different wm-like fvwm, or ede if we can get the applets working right?
« Last Edit: October 03, 2006, 02:42:29 am by adf »
**3100 Zubuntu Jaunty,(working on Cacko dualboot), 16G A-Data internal CF, 4G SD, Ambicom WL-1100C Cf, linksys usb ethernet,  BelkinF8T020 BT card, Belkin F8U1500-E Ir kbd, mini targus usb mouse, rechargeble AC/DC powered USB hub, psp cables and battery extenders.

**6000l  Tetsuized Sharprom, installed on internal flash only 1G sd, 2G cf

loji

  • Full Member
  • ***
  • Posts: 130
    • View Profile
    • http://
Beta 3 Fixes, Customs, Contrib
« Reply #33 on: October 04, 2006, 01:12:34 am »
Well I was trying to get ImageBuilder-0.0.2 to work. It allows slipstreaming ipks into the initrd and rootfs of the installable image. (ie: don't have to compile it all from scratch ... just have to get image builder up and running to at least add / remove packages.  ie: update abiword, and everything -- possibly add rox : however I'm not sure if it allows editing files within the image, or only installing ipks straightforward.

I was on IRC last night and pgas was helping me out, but still no go. Got further than I did before tho. I'm running into troubles with qmake and make with paths and enviroments not being set. I did:

Code: [Select]
#export QMAKESPEC /usr/lib/qt/
and that allowed qmake to build the ImageBuilder-0.0.2.pro (i think) but even after playing with the Makefile I couldn't get 'make' to work. It kept giving me problems saying that it couldn't find the needed .ui and .moc files in /usr/lib/qt/bin :: however they are in the ImageBuilder directory themselves .. so it was still looking in the wrong place from the export option I had to pass to make qmake work ::: not sure how to move it back, I tried defining absolute paths in the Makefile, but that didn't work either.  I never compiled before, so there are probably steps I'm missing .... the tutorials on pdaXrom site don't help much .. since they are for using svn and the newest versions.

we'll keep tinkering away, and see what happens :: anyone with experience get in touch with me.
-> pdaXrom beta 3 fixes & feeds
C-1000 + pdaXrom beta3
linksys wifi + expansions

loji

  • Full Member
  • ***
  • Posts: 130
    • View Profile
    • http://
Beta 3 Fixes, Customs, Contrib
« Reply #34 on: October 05, 2006, 01:26:35 pm »
small update ... Just added the inf about the Input Settings dialog bug . It rewrites the kernel.map which changes the keybaord layout outside of X (basic shell) so that the [>?.] buttons doesn`t work .. You need to edit the filw if you`ve ever run Input Setup and delete the null keys.

Apparently the correct kernel.map lives in the ipk vender-tweaks .... I`m thinking it ma be possible to combine many fixes into this vender-tweak package and use that for `stablizing` our installs. It would allow a correct image to be made once I get ImageBuilder to work ..and also let peiople apply the patches without re-flashing. .. hmm...interesting though. Most the the vender tweaks package seems to be symlinked .. so I`ll have to do it in a *nix enviroment.

does anyone know if I can untar and edit ..then re-tar and change the extension? or do I need to completly rebuild the ipk?
-> pdaXrom beta 3 fixes & feeds
C-1000 + pdaXrom beta3
linksys wifi + expansions

loji

  • Full Member
  • ***
  • Posts: 130
    • View Profile
    • http://
Beta 3 Fixes, Customs, Contrib
« Reply #35 on: October 31, 2006, 01:20:35 am »
Just added an update ::: Instructions for partitioning SD cards as well as chaning ipkg.conf + fstab  to reconize the new partitions.
-> pdaXrom beta 3 fixes & feeds
C-1000 + pdaXrom beta3
linksys wifi + expansions

zi99y

  • Sr. Member
  • ****
  • Posts: 282
    • View Profile
Beta 3 Fixes, Customs, Contrib
« Reply #36 on: October 31, 2006, 04:15:45 pm »
Hi loji, good to see a few updates - your page is becoming a veritable goldmine!

It might be useful to include this nugget:


If you get errors during bootup relating to libiconv or libstdc++, you can fix it by ensuring that the following packages are installed to the root of your filesystem with the command "ipkg -d root install <packagename>"

libstdcxx5-compat_5.0.7_armv5tel.ipk
libstdcxx_5.0.5_arm.ipk
libiconv_1.9.2_arm.ipk

The problem is that if they are installed in another location, it will not be linked until after bootup by the ipkg-link process.

cheers!

Meanie

  • Hero Member
  • *****
  • Posts: 2803
    • View Profile
    • http://www.users.on.net/~hluc/myZaurus/
Beta 3 Fixes, Customs, Contrib
« Reply #37 on: June 22, 2007, 08:54:24 pm »
just FYI, pdaXii13 is beta3 with all the mentioned fixes/patches and many more pre-applied.
the pdaXii13 installer also has an upgrade/patch option to apply all those fixes to an already installed beta1/beta3 installation.
« Last Edit: June 22, 2007, 08:55:43 pm by Meanie »
SL-C3000 - pdaXii13 build5.4.9 (based on pdaXrom beta3) / SL-C3100 - Sharp ROM 1.02 JP (heavily customised)
Netgear MA701 CF, SanDisk ConnectPlus CF, Socket Bluetooth CF, 4GB Kingston CF,  4GB pqi SD, 4GB ChoiceOnly SD, 2GB SanDisk SD USB Plus, 1GB SanDisk USB Plus, 1GB Transcend SD, 2GB SanDisk MicroSD with SD adaptor, Piel Frama Leather Case, GoldX 5-in-1 USB cable, USB hub, USB mouse, USB keyboard, USB ethernet, USB HDD, many other USB accessories...
(Zaurus SL-C3000 owner since March 14. 2005, Zaurus SL-C3100 owner since September 21. 2005)
http://members.iinet.net.au/~wyso/myZaurus - zBook3K