Author Topic: Dual Booting pdaX from SD  (Read 31152 times)

jerrybme

  • Hero Member
  • *****
  • Posts: 639
    • View Profile
    • http://
Dual Booting pdaX from SD
« Reply #45 on: April 23, 2004, 04:54:51 pm »
Update: the cardmgr error was occuring when I had an ext2 formatted Cf card in the slot during boot. Booting with vfat CF works fine & I have access to the card. Weird.
Jerry
SL-C3100
Angstrom-GPE
Lexar SD 1 GB
PQI 2GB CF
Ambicom WL1100 CF

jerrybme

  • Hero Member
  • *****
  • Posts: 639
    • View Profile
    • http://
Dual Booting pdaX from SD
« Reply #46 on: April 24, 2004, 12:46:26 am »
Ok, a few observations now that I\'ve had a chance to play around with several configurations.

First, having pdaXrom on the SD is great, especially for a C750 owner, with a 256 SD card, I can install what ever I want without worrying about space.

Using the Cacko 1.21 kernel will work as long as you use the Xfbdev file from x11zaurus that Stu posted. While it works, it doesn\'t work well. The calibration is off (I think because x11zaurus was meant for the portrait orientation of the 5x00 (the calibration screen\'s text is in portrait). Also suspend, power buttons, on the fly rotation and wireless don\'t work.

I flashed the pdaXrom kernel (while still keeping Cacko 1.21 ROM in internal memory) and the original Xfbdev works fine, calibration is spot on, rotation works, wireless and power button all work. It is however, noticibly slower than with Cacko kernel. And of course with the pdaXrom kernel, Cacko Qt is wacked. It runs but the calibration is so off it is all but unusable.

Conclusion, for this to work well the kernels of Cacko & pdaXrom need to be more compatible. Next I\'m going to try derek\'s suggestion of comparing output of ksyms, but my shallow linux skills may not be enough to make much of them.

Jerry
SL-C3100
Angstrom-GPE
Lexar SD 1 GB
PQI 2GB CF
Ambicom WL1100 CF

jerrybme

  • Hero Member
  • *****
  • Posts: 639
    • View Profile
    • http://
Dual Booting pdaX from SD
« Reply #47 on: April 24, 2004, 01:55:52 am »
Here\'s the result of the diff between the ksysm output of the pdaxrom v cacko kernels:
Code: [Select]
pdaXrom Kernel                                     Cacko Kernel



__insmod_net_fd_O/lib/modules/2.4.18-rmk7-pxa3-embedix/kernel | __insmod_kbdsim_O/home/root/usr/local/bin/kbdsim.o_M3F99D189_

                                                              > __insmod_kbdsim_S.bss_L4

                                                              > __insmod_kbdsim_S.data_L72

                                                              > __insmod_kbdsim_S.text_L300

                                                              > __insmod_net_fd_O/lib/modules.rom/2.4.18-rmk7-pxa3-embedix/ke

                                                              > __insmod_net_fd_S.bss_L120

__insmod_net_fd_S.text_L15496                                 | __insmod_net_fd_S.text_L15472

__insmod_pxa_bi_O/lib/modules/2.4.18-rmk7-pxa3-embedix/kernel | __insmod_pxa_bi_O/lib/modules.rom/2.4.18-rmk7-pxa3-embedix/ke

                                                              > __insmod_pxa_bi_S.bss_L116

__insmod_pxa_bi_S.text_L13668                                 | __insmod_pxa_bi_S.text_L13684

__insmod_usbdcore_O/lib/modules/2.4.18-rmk7-pxa3-embedix/kern | __insmod_usbdcore_O/lib/modules.rom/2.4.18-rmk7-pxa3-embedix/

                                                              > __insmod_usbdcore_S.bss_L48

__insmod_usbdcore_S.text_L22016                               | __insmod_usbdcore_S.text_L22064

__insmod_usbdmonitor_O/lib/modules/2.4.18-rmk7-pxa3-embedix/k | __insmod_usbdmonitor_O/lib/modules.rom/2.4.18-rmk7-pxa3-embed

                                                              > __insmod_usbdmonitor_S.bss_L72

baswap                                                        <

batostr                                                       <

bluez_accept_dequeue                                          <

bluez_accept_enqueue                                          <

bluez_dump                                                    <

bluez_sock_init                                               <

bluez_sock_link                                               <

bluez_sock_poll                                               <

bluez_sock_recvmsg                                            <

bluez_sock_register                                           <

bluez_sock_unlink                                             <

bluez_sock_unregister                                         <

bluez_sock_wait_state                                         <

bterr                                                         <

hci_conn_auth                                                 <

hci_conn_encrypt                                              <

hci_connect                                                   <

hci_dev_get                                                   <

hci_get_route                                                 <

hci_recv_frame                                                <

hci_register_dev                                              <

hci_register_proto                                            <

hci_resume_dev                                                <

hci_send_acl                                                  <

hci_send_cmd                                                  <

hci_send_sco                                                  <

hci_si_event                                                  <

hci_suspend_dev                                               <

hci_unregister_dev                                            <

hci_unregister_proto                                          <

                                                              > journal_enable_debug

                                                              > kbdsim_fops

                                                              > kbdsim_open

                                                              > kbdsim_release

                                                              > kbdsim_write

l2cap_load                                                    <

                                                              > nb_opens

                                                              > slc7x0_key_suspend

wireless_send_event                                           <


Is there anyway to compile a kernel that would work with both? maslovsky? A little help here
***edit***
The text is not wrapping correctly so I\'m attaching a txt file for those inquiring minds that want to see it clearer
SL-C3100
Angstrom-GPE
Lexar SD 1 GB
PQI 2GB CF
Ambicom WL1100 CF

maslovsky

  • Hero Member
  • *****
  • Posts: 1426
    • View Profile
    • http://my-zaurus.narod.ru
Dual Booting pdaX from SD
« Reply #48 on: April 24, 2004, 03:27:02 pm »
Making a kernel that would be compatibe for both ROMs is what I wanted to accimplish next after releasing Cacko ROMs 1.2x.
I hope we\'ll get to make it.

jerrybme

  • Hero Member
  • *****
  • Posts: 639
    • View Profile
    • http://
Dual Booting pdaX from SD
« Reply #49 on: April 24, 2004, 09:45:18 pm »
Quote
Making a kernel that would be compatibe for both ROMs is what I wanted to accimplish next after releasing Cacko ROMs 1.2x.
I hope we\'ll get to make it.
 That\'s great!  
 While we wait can you enlighten me on what\'s different about the pdaXrom kernel that makes the digitizer act so differently than the Cacko kernel?
Thanks,
Jerry
SL-C3100
Angstrom-GPE
Lexar SD 1 GB
PQI 2GB CF
Ambicom WL1100 CF

iyah

  • Newbie
  • *
  • Posts: 8
    • View Profile
Dual Booting pdaX from SD
« Reply #50 on: April 25, 2004, 08:36:38 pm »
Just a note to let you dude(tte?)s know that following stu\'s instructions and caveats, then pdaXrom dual booted on an sl-6 with an sd card. X pops up with the xfbdev from x11zaurus, and looks clean. Problem is it doesn\'t recognize the pen input ... should I just be able to edit the xfree86 file and change input devices ? Any ideas on this appreciated ...

Joshp

  • Sr. Member
  • ****
  • Posts: 265
    • View Profile
    • http://
Dual Booting pdaX from SD
« Reply #51 on: April 25, 2004, 08:51:14 pm »
And I might add that I tryed this on my sl-5500 it WORKS!!! The only problume I had is that it wouldint recognize pen input and or anything form the keyboard.

JP

Stubear

  • Hero Member
  • *****
  • Posts: 1164
    • View Profile
    • http://
Dual Booting pdaX from SD
« Reply #52 on: April 25, 2004, 10:52:50 pm »
iyah, Joshp,

Try running ts_calibrate prior to runngi xstart - or delete /etc/ts_calibrate then run xstart , this will recalibrate the touch screen for pdaX, I probably left the calaibration file from the C760 in the tarball.

Stu
SL-C1000, Hand converted to English with Japanese Input
Running X apps via X/Qt
iRiver USB host cable; Diatec P-Cord usb power cable (extendable); Acro's Reel Cable USB (A to A, B, Mini-B,  & Mini-B 8pin); GreenHouse 1Gb PicoDrive+; 2x256Mb Hagiwara SD cards; 128Mb Transcend CF card; 512Mb PQI CF card; AmbiCom WL1100C-CF 11B WLAN card

iyah

  • Newbie
  • *
  • Posts: 8
    • View Profile
Dual Booting pdaX from SD
« Reply #53 on: April 26, 2004, 09:25:54 am »
Found ts_calibrate in /usr/bin/ ... was nothing like that in /etc/. Anyways, ran it, and it went through the 5 point and taps ... afterwards nothing new was in /etc/ (should there be a file generated from this ?). X was the same .. I could navigate using the buttons (not so straightforward, but probably not hard to fix) a bit, but the pen still does nothing. For instance, use the keys to highlight a folder, then use the pen to tap another folder, the highlighted folder will blink, but not open. There is a hint of a pointer somewhere on the screen, but does not follow the pen. So there is also no way top get down to the menu on the bottom where the taskbar is either. When I get some more time I can hack at it some more, so any pointers appreciated. Does pdaX use a config file like xf86config-4 or something ?

Stubear

  • Hero Member
  • *****
  • Posts: 1164
    • View Profile
    • http://
Dual Booting pdaX from SD
« Reply #54 on: April 26, 2004, 06:26:51 pm »
Sorry my miss,

remove /etc/pointercal and try startx again - should run the calibration first. Otherwise I\'m at a lose, what XFbdev are you using?

Stu
SL-C1000, Hand converted to English with Japanese Input
Running X apps via X/Qt
iRiver USB host cable; Diatec P-Cord usb power cable (extendable); Acro's Reel Cable USB (A to A, B, Mini-B,  & Mini-B 8pin); GreenHouse 1Gb PicoDrive+; 2x256Mb Hagiwara SD cards; 128Mb Transcend CF card; 512Mb PQI CF card; AmbiCom WL1100C-CF 11B WLAN card

jerrybme

  • Hero Member
  • *****
  • Posts: 639
    • View Profile
    • http://
Dual Booting pdaX from SD
« Reply #55 on: April 26, 2004, 10:45:21 pm »
Quote
Sorry my miss,

remove /etc/pointercal and try startx again - should run the calibration first. Otherwise I\'m at a lose, what XFbdev are you using?

Stu
I just run ts_calibrate the first time after I boot to the SD before I run startx. This only works with X11zaurus Xfbdev that Stu posted (assuming you\'re running a Sharp compatible Kernel)

Jerry
SL-C3100
Angstrom-GPE
Lexar SD 1 GB
PQI 2GB CF
Ambicom WL1100 CF

anonuk

  • Full Member
  • ***
  • Posts: 176
    • View Profile
    • http://
Dual Booting pdaX from SD
« Reply #56 on: April 29, 2004, 06:38:06 pm »
what sort of speed does x11 run at on the SD card?
* C3100 with Cacko 1.23 and debian (pocketworkstation) - 1Gb SD / 1Gb CF / Prism Wifi
* C-860 with Cacko 1.21b/pdaXrom dualboot with 256Mb CF / 512 Mb SD / Prism Wifi
* SL-5500 with Cacko rom with 128Mb SD home on SD / 96 Mb CF

jerrybme

  • Hero Member
  • *****
  • Posts: 639
    • View Profile
    • http://
Dual Booting pdaX from SD
« Reply #57 on: April 29, 2004, 07:10:26 pm »
Quote
what sort of speed does x11 run at on the SD card?
With the cacko kernel it runs at an acceptable speed only a tad bit slower than normal. With the pdaXrom kernel it is much slower. It is very usable (but the right side of the screen is always mis-calibrated and it\'ll drive you nuts).

Let\'s hope maslovsky is able to unify the kernels so it works for both ROMs. That\'ll take care of the calibration problem (and others too)
Jerry
SL-C3100
Angstrom-GPE
Lexar SD 1 GB
PQI 2GB CF
Ambicom WL1100 CF

Stubear

  • Hero Member
  • *****
  • Posts: 1164
    • View Profile
    • http://
Dual Booting pdaX from SD
« Reply #58 on: April 29, 2004, 09:28:20 pm »
Once it7s started it\'s fine - just takes a while to get going, large apps also take a while to start but are okay after that

Stu
SL-C1000, Hand converted to English with Japanese Input
Running X apps via X/Qt
iRiver USB host cable; Diatec P-Cord usb power cable (extendable); Acro's Reel Cable USB (A to A, B, Mini-B,  & Mini-B 8pin); GreenHouse 1Gb PicoDrive+; 2x256Mb Hagiwara SD cards; 128Mb Transcend CF card; 512Mb PQI CF card; AmbiCom WL1100C-CF 11B WLAN card

jerrybme

  • Hero Member
  • *****
  • Posts: 639
    • View Profile
    • http://
Dual Booting pdaX from SD
« Reply #59 on: April 29, 2004, 11:44:47 pm »
Quote
Once it7s started it\'s fine - just takes a while to get going, large apps also take a while to start but are okay after that

Stu
Stu:
Have you been able to get the wifi or suspend to work with the Sharp kernel or is it just me?

BTW, thanks for all of your help getting this to work.
Jerry
SL-C3100
Angstrom-GPE
Lexar SD 1 GB
PQI 2GB CF
Ambicom WL1100 CF