OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: Meanie on February 24, 2007, 01:45:43 am
-
since pdaXii13 is based on beta1/beta3 and build directly on a Zaurus installed with pdaXrom beta1/beta3, it is possible to upgrade those system to pdaXii13 base without reflashing them.
in order to upgrade to pdaXii13 you will need to be running either beta1 or beta3 already and have about 10MB of free space left on your NAND (the exact space needed is not known and may be less).
make sure you do a NAND backup before attempting this. this is a generic upgrade method and may not work as expected on some systems with fancy setups. make sure you have a backup before upgrading to pdaXii13...
What you need to do is download and extract http://www.tyrannozaurus.com/feed/pdaXii13...ii13-custom.tgz (http://www.tyrannozaurus.com/feed/pdaXii13/build/pdaXii13-custom.tgz) to your Z somewhere (preferably CF card rather than SD card)
Shut down X and any unneeded services including SD service
Then from the extracted directory run
./install-fix-beta3 / upgrade
reboot and your system is patched to the same level as pdaXii13 base.
running version will tell you which edition and version of pdaXii13 you have.
The full pdaXii13 is available for the C3000 model as a complete install since there is no beta1/beta3 for it in the first place, however, you can use this method to upgrade an older pdaXii13 to the latest patch level as well...
C1000, C3100, C3200 can be upgraded this way without requiring you to reflash, but of course you can use the pdaXii13 Akita installer to flash if you want to.
The installer (both for Alice and Sally) have an upgrade option which basically does the extraction the update file for you and also installs the files.
C7x0, C8x0 can use this method to update their setup.
pdaXii13 base edition is a collection of bug fixes and patches rolled together to fix quite a lot of bugs in pdaXrom beta1/beta3. pdaXii13 full adds a lot of pre-installed and customised applicatons which requires a lot of space and only available to C3x00 models...
-
Nice! I'll give it a shot on my C860 before plunging into the new test builds next week. Thanks!
-
definitely interesting. I'd kinda put off the change because beta3 is working ok. this is tempting
-
Yes it sounds very tempting, although being a beta3 / 3200 user I have few complaints - mainly interested in the speed benefits of the new kernel releases.
Is there a list of what is improved/fixed that we might see to help us decide if we -need- this upgrade? Or maybe it's possible to pick and choose the updated files without running the updater....
-
Just look the "readme.txt" in Meanie's custom package tarball.
Maybe this can also be useful:
http://www.tyrannozaurus.com/?q=node/210 (http://www.tyrannozaurus.com/?q=node/210)
-
this is what I was looking for!
I have an extremely prductive and stable beta1 setup on my 860, and this upgrade sounds lik the best I can achieve without introducing r121 (enormous on 860) glitches. Gonna try soon, after a complete backup.
When you speak about NAND backup, do you mean using Louigi600 backup script (Louigi is working on extremely usfull scripts at the moment)?
-
this is what I was looking for!
I have an extremely prductive and stable beta1 setup on my 860, and this upgrade sounds lik the best I can achieve without introducing r121 (enormous on 860) glitches. Gonna try soon, after a complete backup.
When you speak about NAND backup, do you mean using Louigi600 backup script (Louigi is working on extremely usfull scripts at the moment)?
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=155141\")
no, NAND backup as in D+M thingy to get into the service menu and do a complete backup of the NAND/flash memory...
also see the first post of this thread which lists some of the enhancements/bug fixes in pdaXii13. note that changes are specific to some models only, ie the SD module to support >1GB SD cards won't be available to c7x0/c8x0 models. just like keymappings, however, other things like the matchbox panel applies to all models...
[a href=\"https://www.oesf.org/forums/index.php?showtopic=22798]https://www.oesf.org/forums/index.php?showtopic=22798[/url]
-
this is what I was looking for![div align=\"right\"][a href=\"index.php?act=findpost&pid=155141\"][{POST_SNAPBACK}][/a][/div]
the SD module to support >1GB SD cards won't be available to c7x0/c8x0 models.[div align=\"right\"][a href=\"index.php?act=findpost&pid=155144\"][{POST_SNAPBACK}][/a][/div]
I was starting to get really interested too, until I read this post of course . I guess the issue is that the c7x0 models still use the 2.6.18 kernel instead of the 2.6.20, right? There's no way to get that working for us poor older clampshells?
-
this is what I was looking for![div align=\"right\"][a href=\"index.php?act=findpost&pid=155141\"][{POST_SNAPBACK}][/a][/div]
the SD module to support >1GB SD cards won't be available to c7x0/c8x0 models.[div align=\"right\"][a href=\"index.php?act=findpost&pid=155144\"][{POST_SNAPBACK}][/a][/div]
I was starting to get really interested too, until I read this post of course . I guess the issue is that the c7x0 models still use the 2.6.18 kernel instead of the 2.6.20, right? There's no way to get that working for us poor older clampshells?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=155146\"][{POST_SNAPBACK}][/a][/div]
actually, there is a driver for 2.4.18 that works on Sharp ROM and can in theory be copied to pdaXrom with modified sd scripts but I am unable to test this without having one of those models...
-
Ok-- I did it. I've only had it going a few minutes, but at the very least it seems to have done no harm (which I expect is the 1st question that those considering the upgrade want answered).
I had been using openbox, and this defaulted to ROX, which is fine, I like ROX.
it is pdax 3.5.1--I thought it was going to be 3.5.2....
On reboot, my ide wasn't mounted. again, not a biggie. Possibly the fact that I have /home/root linked to its real folder in /mnt/ide/home/root ? (got tired of nand space issues)
I mounted manually, ran ipkg-link just to be sure--though it seems like the links are all there already.
works fine after i did the manual stuff just mentioned.--and that seems likely due to some linking and tweaking I did
-
I had been using openbox, and this defaulted to ROX, which is fine, I like ROX.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=155182\")
You can use pdaxii13.config to select between openbox or rox upon startup of X
If pdaxii13.config isn't on your menu (or desktop in openbox) you can create a .desktop file.
This is what I did, look at this thread for more details.
[a href=\"https://www.oesf.org/forums/index.php?showtopic=23195]https://www.oesf.org/forums/index.php?showtopic=23195[/url]
-
I had been using openbox, and this defaulted to ROX, which is fine, I like ROX.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=155182\")
You can use pdaxii13.config to select between openbox or rox upon startup of X
If pdaxii13.config isn't on your menu (or desktop in openbox) you can create a .desktop file.
This is what I did, look at this thread for more details.
[a href=\"https://www.oesf.org/forums/index.php?showtopic=23195]https://www.oesf.org/forums/index.php?showtopic=23195[/url]
[div align=\"right\"][a href=\"index.php?act=findpost&pid=155183\"][{POST_SNAPBACK}][/a][/div]
Thanks. actually I read the post on the configs and it cleared up something for me--
I had been running openbox for fear that rox would be running on top of openbox--wasting a lot of power and memory. since it isn't I, think I might like ROX a little better...
We'll see, I suppose
-
this is what I was looking for![div align=\"right\"][a href=\"index.php?act=findpost&pid=155141\"][{POST_SNAPBACK}][/a][/div]
the SD module to support >1GB SD cards won't be available to c7x0/c8x0 models.[div align=\"right\"][a href=\"index.php?act=findpost&pid=155144\"][{POST_SNAPBACK}][/a][/div]
I was starting to get really interested too, until I read this post of course . I guess the issue is that the c7x0 models still use the 2.6.18 kernel instead of the 2.6.20, right? There's no way to get that working for us poor older clampshells?[div align=\"right\"][a href=\"index.php?act=findpost&pid=155146\"][{POST_SNAPBACK}][/a][/div]
actually, there is a driver for 2.4.18 that works on Sharp ROM and can in theory be copied to pdaXrom with modified sd scripts but I am unable to test this without having one of those models...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=155147\"][{POST_SNAPBACK}][/a][/div]
There's an eager tester right here! I've got the driver (installed & working under Cacko). If you can walk me through what I'd need to do, I'll be your guinea pig.
-
the older method is described on loji's page (just llok up the user loji it has the address on the profile)
the directions are for the unmodified 2.4.29, but I bet it is really similar.
-
C860 user here with the first problem . The upgrade (from beta1) went without error, and the reboot went fine & X starts ok. But the display comes up rotated 90 degrees clockwise, so it's sitting sideways pointed the wrong way when the unit is in clampshell mode (i.e. the keyboard is visible), and rotates upside down when the unit screen is rotated to portrait mode.
Any idea how I can fix this? thks
-
do a xrandr -o 1 or 2 or 3 or 4 until it is correct and add it the bottom of your .xinitrc under your home dir...
Late
PS. Sorry I'm so vague... I didnt develop for pdaXii..
-
C860 user here with the first problem . The upgrade (from beta1) went without error, and the reboot went fine & X starts ok. But the display comes up rotated 90 degrees clockwise, so it's sitting sideways pointed the wrong way when the unit is in clampshell mode (i.e. the keyboard is visible), and rotates upside down when the unit screen is rotated to portrait mode.
Any idea how I can fix this? thks
[div align=\"right\"][a href=\"index.php?act=findpost&pid=155197\"][{POST_SNAPBACK}][/a][/div]
if I had a tarball of a beta1 system (prior to upgrading) then it would help me out as a guide in general. in order to fix the upside down rotation problem, i need the startx script under /usr/X11R6/bin
to create the tarball, please do the following:
tar czf /mnt/card/corgi.tgz /bin /etc /home /lib /root /sbin /usr
-
this is what I was looking for![div align=\"right\"][a href=\"index.php?act=findpost&pid=155141\"][{POST_SNAPBACK}][/a][/div]
the SD module to support >1GB SD cards won't be available to c7x0/c8x0 models.[div align=\"right\"][a href=\"index.php?act=findpost&pid=155144\"][{POST_SNAPBACK}][/a][/div]
I was starting to get really interested too, until I read this post of course . I guess the issue is that the c7x0 models still use the 2.6.18 kernel instead of the 2.6.20, right? There's no way to get that working for us poor older clampshells?[div align=\"right\"][a href=\"index.php?act=findpost&pid=155146\"][{POST_SNAPBACK}][/a][/div]
actually, there is a driver for 2.4.18 that works on Sharp ROM and can in theory be copied to pdaXrom with modified sd scripts but I am unable to test this without having one of those models...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=155147\"][{POST_SNAPBACK}][/a][/div]
There's an eager tester right here! I've got the driver (installed & working under Cacko). If you can walk me through what I'd need to do, I'll be your guinea pig.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=155193\"][{POST_SNAPBACK}][/a][/div]
install this package on beta1 and see what happens with the SD card (of course don't install this package from a SD card directly
-
do a xrandr -o 1 or 2 or 3 or 4 until it is correct and add it the bottom of your .xinitrc under your home dir...[div align=\"right\"][a href=\"index.php?act=findpost&pid=155198\"][{POST_SNAPBACK}][/a][/div]
'xrandr -o 1' did the trick for landscape mode, but then rotating the screen flips it wrong again both in that & portrait, so I have to run it again (I assume the rotate script is hard coded for this value). No problem though, this gets me running properly in the mean time. thanks
-
C860 user here with the first problem . The upgrade (from beta1) went without error, and the reboot went fine & X starts ok. But the display comes up rotated 90 degrees clockwise, so it's sitting sideways pointed the wrong way when the unit is in clampshell mode (i.e. the keyboard is visible), and rotates upside down when the unit screen is rotated to portrait mode.
Any idea how I can fix this? thks[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=155197\")
if I had a tarball of a beta1 system (prior to upgrading) then it would help me out as a guide in general. in order to fix the upside down rotation problem, i need the startx script under /usr/X11R6/bin
to create the tarball, please do the following:
tar czf /mnt/card/corgi.tgz /bin /etc /home /lib /root /sbin /usr[div align=\"right\"][a href=\"index.php?act=findpost&pid=155200\"][{POST_SNAPBACK}][/a][/div]
It seems I can't upload a 32mb file to the board , so you can grab it [a href=\"http://grogsworld.dyndns.org/zaurus/corgi-beta1.tgz]here[/url].
Thanks for all of your help & hard work (past, present & future ). It's MUCH appreciated.
-
any chance we can see pdaxii13 format big SD cards to FAT?
-
any chance we can see pdaxii13 format big SD cards to FAT?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=155269\"][{POST_SNAPBACK}][/a][/div]
what are you asking? FAT16 has a 2GB limit, that's one of the reason FAT32 was created...
-
this is what I was looking for![div align=\"right\"][a href=\"index.php?act=findpost&pid=155141\"][{POST_SNAPBACK}][/a][/div]
the SD module to support >1GB SD cards won't be available to c7x0/c8x0 models.[div align=\"right\"][a href=\"index.php?act=findpost&pid=155144\"][{POST_SNAPBACK}][/a][/div]
I was starting to get really interested too, until I read this post of course . I guess the issue is that the c7x0 models still use the 2.6.18 kernel instead of the 2.6.20, right? There's no way to get that working for us poor older clampshells?[div align=\"right\"][a href=\"index.php?act=findpost&pid=155146\"][{POST_SNAPBACK}][/a][/div]
actually, there is a driver for 2.4.18 that works on Sharp ROM and can in theory be copied to pdaXrom with modified sd scripts but I am unable to test this without having one of those models...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=155147\"][{POST_SNAPBACK}][/a][/div]
There's an eager tester right here! I've got the driver (installed & working under Cacko). If you can walk me through what I'd need to do, I'll be your guinea pig.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=155193\"][{POST_SNAPBACK}][/a][/div]
install this package on beta1 and see what happens with the SD card (of course don't install this package from a SD card directly
[div align=\"right\"][a href=\"index.php?act=findpost&pid=155210\"][{POST_SNAPBACK}][/a][/div]
so who tried it? does it work?
-
do a xrandr -o 1 or 2 or 3 or 4 until it is correct and add it the bottom of your .xinitrc under your home dir...[div align=\"right\"][a href=\"index.php?act=findpost&pid=155198\"][{POST_SNAPBACK}][/a][/div]
'xrandr -o 1' did the trick for landscape mode, but then rotating the screen flips it wrong again both in that & portrait, so I have to run it again (I assume the rotate script is hard coded for this value). No problem though, this gets me running properly in the mean time. thanks
[div align=\"right\"][a href=\"index.php?act=findpost&pid=155216\"][{POST_SNAPBACK}][/a][/div]
edit /usr/X11R6/bin/startx and remove
-screen 480x640@270
-
Beta # only sees 4gig FAT 32 as 1 gig. I thought you knew--formatting at 4 gig to FAT32 yeilds a 1 gig FAT32 sd in beta3. Thought I'd ask if there was hope for a fix in PDaxii13. I'm guessing there won't be--seems like some fundamental sort of problem with the way the module handles FAT32--but I thought I'd ask. 4 gigs that would pop into pretty much any box would be handy.
kernel 2.6 doesn't seem to have this problem which I why I suspect it isn't going to be fixed
-
Beta # only sees 4gig FAT 32 as 1 gig. I thought you knew--formatting at 4 gig to FAT32 yeilds a 1 gig FAT32 sd in beta3. Thought I'd ask if there was hope for a fix in PDaxii13. I'm guessing there won't be--seems like some fundamental sort of problem with the way the module handles FAT32--but I thought I'd ask. 4 gigs that would pop into pretty much any box would be handy.
kernel 2.6 doesn't seem to have this problem which I why I suspect it isn't going to be fixed
[div align=\"right\"][a href=\"index.php?act=findpost&pid=155278\"][{POST_SNAPBACK}][/a][/div]
erm... i've been using a 4GB SD card in pdaXii13 for like since build1....
-
I have also been using a 4 gig for about as long as we've known the module could be imported. I might hve been among the first to try it, in fact. that isn't the point.
try this:
backup your 4 gig sd
fdisk it to type 6 (windows FAT32..or was it type b--I always have to check)
format it vfat -F 32
check the size
I bet it will say 1 gig
type 82/ext2 works just fine.
this is actually a known issue.
I had originally been mildly curious as to whether anyone knew a fix, not intending to inform you of a defect. I think the problem maybe has something to do with the module, since the kernel can see >4 gig FAT32 on other media, and since the issue doesnt exist in 2.6 based roms. I seem to remember hrw saying it had something to do with block sizes.
Have you really never run into this? there was a thread running about it last fall.
-
I have also been using a 4 gig for about as long as we've known the module could be imported. I might hve been among the first to try it, in fact. that isn't the point.
try this:
backup your 4 gig sd
fdisk it to type 6 (windows FAT32..or was it type b--I always have to check)
format it vfat -F 32
check the size
I bet it will say 1 gig
type 82/ext2 works just fine.
this is actually a known issue.
I had originally been mildly curious as to whether anyone knew a fix, not intending to inform you of a defect. I think the problem maybe has something to do with the module, since the kernel can see >4 gig FAT32 on other media, and since the issue doesnt exist in 2.6 based roms. I seem to remember hrw saying it had something to do with block sizes.
Have you really never run into this? there was a thread running about it last fall.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=155285\"][{POST_SNAPBACK}][/a][/div]
I had this issue and found it seems to be a buggy mkfs version under beta3.
When you use the D+B boot emergency system and format the card's partition there with
mkfs.vfat -F 32 /dev/mmcda1it will have 4GB again, with Fat32 FS (I tried this only with a 2GB card, though).
I have copied the mkfs versions from there to the main system now, so I can format cards without booting into D+B.
daniel
-
install this package on beta1 and see what happens with the SD card (of course don't install this package from a SD card directly [div align=\"right\"][a href=\"index.php?act=findpost&pid=155210\"][{POST_SNAPBACK}][/a][/div]
so who tried it? does it work?[div align=\"right\"][a href=\"index.php?act=findpost&pid=155276\"][{POST_SNAPBACK}][/a][/div]
Busy with family stuff most of the weekend, so not much time. Tried it now, modules seem to be loaded
root-:) lsmod
Module Size Used by Tainted: P
sharp_mmcsd_m 25888 0 (unused)
sdmmc_linux 12680 1 (initializing)
sd_memory 4680 0 [sdmmc_linux]
sd_core 17908 0 [sdmmc_linux sd_memory]
sd_linux 11496 0 [sdmmc_linux sd_memory sd_core]
mousedev 4496 1
pxa_bi 21388 0 (unused)
net_fd 25000 0 (unused)
usbdcore 34456 0 [pxa_bi net_fd]
usbdmonitor 5216 0but lots of errors from dmesg
edc
r10: c15b4000 r9 : 00034cd8 r8 : c5b00da8
r7 : 00000010 r6 : 00000000 r5 : c5b01258 r4 : 00000010
r3 : c5ac5ff8 r2 : 00000010 r1 : 0000000f r0 : c5b01258
Flags: Nzcv IRQs on FIQs on Mode SVC_32 Segment user
Control: 197F Table: A16B4000 DAC: 00000015 PID: 0
Process insmod (pid: 707, stackpage=c15b5000)
Stack: (0xc15b5ec0 to 0xc15b6000)
5ec0: c5b00c14 c011f66c 80000013 ffffffff c15b5f04 c15b5ee0 c5b00c14 c011f654
5ee0: 00000000 c5b011b0 c5b00000 c159d000 00000060 ffffffea c15b5fa4 c15b5f08
5f00: c0044088 c5b00aa8 c159d000 c15b5f1c c159e000 0000000b c3e0cd00 00000060
5f20: c5af0000 c5b00060 00003188 00000000 00000000 00000000 00000000 00000000
5f40: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
5f60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000005
5f80: c5b00000 00000000 00000080 c002f9e4 c15b4000 00000000 00000000 c15b5fa8
5fa0: c002f840 c0043974 00000005 c003f934 00021ad0 00034cd8 ffffffff 40016000
5fc0: 00000005 c5b00000 00000000 0002eb28 00003188 00000000 00000000 0000000b
5fe0: 400e8aa0 bfffba80 0000c938 400e8aac 60000010 00021ad0 00000000 00000000
Backtrace:
Function entered at [] from []
Function entered at [] from []
r8 = FFFFFFEA r7 = 00000060 r6 = C159D000 r5 = C5B00000
r4 = C5B011B0
Function entered at [] from []
Code: e3530000 0a000004 e1530000 0a000008 (e5933020)
SD: RCA=0xb368
SD: SD memory is detected
Unable to handle kernel NULL pointer dereference at virtual address 00000063
pgd = c0004000
*pgd = a0002001, *pmd = a0002001, *pte = a000108f, *ppte = a000100f
Internal error: Oops: ffffffff
CPU: 0
pc : [] lr : [] Tainted: P
sp : c16bdf74 ip : c16bdf98 fp : c16bdf94
r10: c0282fe4 r9 : c5ac0bb8 r8 : 20000013
r7 : c5ac2128 r6 : 00000000 r5 : c16bc000 r4 : 00000000
r3 : 00000001 r2 : c16bc000 r1 : c16bc0e8 r0 : 00000063
Flags: nzCv IRQs off FIQs on Mode SVC_32 Segment kernel
Control: 197F Table: A35F4000 DAC: 0000001D PID: 0
Process ttach (pid: 710, stackpage=c16bd000)
Stack: (0xc16bdf64 to 0xc16be000)
df60: c0041240 c003ff2c 20000093 ffffffff 00000000 c16bc000 00000000
df80: c5ac2128 c2d1cb10 c16bdfa4 c16bdf98 c0041240 c003ff18 c16bdfb4 c16bdfa8
dfa0: c0045fbc c0041220 c16bdfc4 c16bdfb8 c0046264 c0045f50 c16bdff4 c16bdfc8
dfc0: c5ac023c c004624c c2d1cb50 00000000 c03c4000 c03c4000 c03c4348 c03c4338
dfe0: 00000001 c03c5fbc 00000000 c16bdff8 c0030c04 c5ac00b0 00000000 00000000
Backtrace:
Function entered at [] from []
r8 = C2D1CB10 r7 = C5AC2128 r6 = 00000000 r5 = C16BC000
r4 = 00000000
Function entered at [] from []
Function entered at [] from []
Function entered at [] from []
Function entered at [] from []
Code: e3883080 e121f003 e5903000 e2833001 (e4803004)
Unable to handle kernel paging request at virtual address ffffffff
pgd = c0004000
*pgd = 00000000, *pmd = 00000000
Internal error: Oops: 0
CPU: 0
pc : [] lr : [] Tainted: P
sp : c16bde4c ip : c16bde60 fp : c16bde5c
r10: ffffffff r9 : ffffffff r8 : c003ff2c
r7 : ffffffff r6 : 0000000b r5 : c16bc000 r4 : c16bc000
r3 : a0000093 r2 : a0000093 r1 : ffffffff r0 : c16bc000
Flags: NzCv IRQs off FIQs on Mode SVC_32 Segment kernel
Control: 197F Table: A35F4000 DAC: 0000001D PID: 0
Process ttach (pid: 710, stackpage=c16bd000)
Stack: (0xc16bde3c to 0xc16be000)
de20: c0046168
de40: c004bb20 a0000093 ffffffff c3c8fae0 c16bde6c c16bde60 c0046168 c004baf0
de60: c16bde88 c16bde70 c00341a8 c0045f50 00000063 c16bdf2c 00000000 c16bdea8
de80: c16bde8c c0034ee4 c00340ac c16bc000 e4803004 c16bdf2c 00000063 c16bdec0
dea0: c16bdeac c0034f98 c0034e88 ffffffff 00000004 c16bdef8 c16bdec4 c0036b60
dec0: c0034f50 c16bdf2c c3190000 00000000 00000063 c16bc000 00000024 00000003
dee0: c02111e4 c02111c0 ffffffff c16bdf28 c16bdefc c0035694 c00369c4 c16bdf2c
df00: ffffffff c16bdf60 00000000 c5ac2128 20000013 20000093 c0282fe4 c16bdf94
df20: c16bdf2c c002f480 c003562c 00000063 c16bc0e8 c16bc000 00000001 00000000
df40: c16bc000 00000000 c5ac2128 20000013 c5ac0bb8 c0282fe4 c16bdf94 c16bdf98
df60: c16bdf74 c0041240 c003ff2c 20000093 ffffffff 00000000 c16bc000 00000000
df80: c5ac2128 c2d1cb10 c16bdfa4 c16bdf98 c0041240 c003ff18 c16bdfb4 c16bdfa8
dfa0: c0045fbc c0041220 c16bdfc4 c16bdfb8 c0046264 c0045f50 c16bdff4 c16bdfc8
dfc0: c5ac023c c004624c c2d1cb50 00000000 c03c4000 c03c4000 c03c4348 c03c4338
dfe0: 00000001 c03c5fbc 00000000 c16bdff8 c0030c04 c5ac00b0 00000000 00000000
Backtrace:
Function entered at [] from []
r4 = C3C8FAE0
Function entered at [] from []
Function entered at [] from []
r6 = 00000000 r5 = C16BDF2C r4 = 00000063
Function entered at [] from []
r7 = 00000063 r6 = C16BDF2C r5 = E4803004 r4 = C16BC000
Function entered at [] from []
r4 = 00000004
Function entered at [] from []
Function entered at [] from []
Function entered at [] from []
r8 = C2D1CB10 r7 = C5AC2128 r6 = 00000000 r5 = C16BC000
r4 = 00000000
Function entered at [] from []
Function entered at [] from []
Function entered at [] from []
Function entered at [] from []
Code: e5843334 e10f2000 e3823080 e121f003 (e5913000)
SD: bus 0 is unregistered.
Unable to handle kernel paging request at virtual address c5ac603c
pgd = c1770000
*pgd = a3f47021, *pmd = a3f47021, *pte = 00000000, *ppte = 00000000
Internal error: Oops: 0
CPU: 0
pc : [] lr : [<00000000>] Tainted: P
sp : c1851ec0 ip : a0000013 fp : c1851ee8
r10: c3a6f060 r9 : c3f1b73c r8 : 00003c00
r7 : c1fedd20 r6 : fffffffa r5 : 3c000000 r4 : c3f1b720
r3 : c5ac6028 r2 : c1fedd20 r1 : c3a6f060 r0 : c3f1b720
Flags: NzCv IRQs on FIQs on Mode SVC_32 Segment user
Control: 197F Table: A1770000 DAC: 00000015 PID: 0
Process mount (pid: 885, stackpage=c1851000)
Stack: (0xc1851eb0 to 0xc1852000)
1ea0: 00000000 c006b430 a0000013 ffffffff
1ec0: c3a6f060 c1fedd20 c1fedd20 c32d9268 c02541d4 c1850000 0001e89c c1851f00
1ee0: c1851eec c006b638 c006b3c8 c3a6f060 c32d9260 c1851f30 c1851f04 c00b2dd8
1f00: c006b610 c1851f20 c1851f14 c006ed30 c1fedd20 c3a6f060 00000000 c03be360
1f20: c3b1c6c0 c1851f54 c1851f34 c006390c c00b2d08 00020000 00020000 00000000
1f40: c3f1c000 c002f9e4 c1851f84 c1851f58 c0063804 c0063814 c3b1c6c0 c03be360
1f60: c006eab8 c005b128 c3f1c000 00000001 00000001 00000003 c1851fa4 c1851f88
1f80: c0063b60 c00637c4 bfffdff8 00020210 00000000 00000005 00000000 c1851fa8
1fa0: c002f840 c0063b28 bfffdff8 c00356f4 00020210 00020000 00000000 00006000
1fc0: bfffdff8 00020210 00000000 00020210 bffff658 bffff668 0001e89c 00020230
1fe0: 40137e7c bfff57e8 400db290 400db264 60000010 00020210 4021c26c 401ef29c
Backtrace:
Function entered at [] from []
Function entered at [] from []
r5 = C32D9260 r4 = C3A6F060
Function entered at [] from []
r8 = C3B1C6C0 r7 = C03BE360 r6 = 00000000 r5 = C3A6F060
r4 = C1FEDD20
Function entered at [] from []
r8 = C002F9E4 r7 = C3F1C000 r6 = 00000000 r5 = 00020000
r4 = 00020000
Function entered at [] from []
r4 = 00000003
Function entered at [] from []
r7 = 00000005 r6 = 00000000 r5 = 00020210 r4 = BFFFDFF8
Code: e5840018 e5943018 e3530000 0a000048 (e5931014)
no /dev/mmcd/disc0/part devices created, just a /dev/mmcd/disc0/disc, which fails to mount
root-:) mount /dev/mmcd/disc0/disc /mnt/card
Segmentation fault
-
do a xrandr -o 1 or 2 or 3 or 4 until it is correct and add it the bottom of your .xinitrc under your home dir...[div align=\"right\"][a href=\"index.php?act=findpost&pid=155198\"][{POST_SNAPBACK}][/a][/div]
'xrandr -o 1' did the trick for landscape mode, but then rotating the screen flips it wrong again both in that & portrait, so I have to run it again (I assume the rotate script is hard coded for this value). No problem though, this gets me running properly in the mean time. thanks
[div align=\"right\"][a href=\"index.php?act=findpost&pid=155216\"][{POST_SNAPBACK}][/a][/div]
edit /usr/X11R6/bin/startx and remove
-screen 480x640@270[div align=\"right\"][a href=\"index.php?act=findpost&pid=155277\"][{POST_SNAPBACK}][/a][/div]
That did the trick. thks
-
install this package on beta1 and see what happens with the SD card (of course don't install this package from a SD card directly [div align=\"right\"][a href=\"index.php?act=findpost&pid=155210\"][{POST_SNAPBACK}][/a][/div]
so who tried it? does it work?[div align=\"right\"][a href=\"index.php?act=findpost&pid=155276\"][{POST_SNAPBACK}][/a][/div]
Busy with family stuff most of the weekend, so not much time. Tried it now, modules seem to be loaded
root-:) lsmod
Module Size Used by Tainted: P
sharp_mmcsd_m 25888 0 (unused)
sdmmc_linux 12680 1 (initializing)
sd_memory 4680 0 [sdmmc_linux]
sd_core 17908 0 [sdmmc_linux sd_memory]
sd_linux 11496 0 [sdmmc_linux sd_memory sd_core]
mousedev 4496 1
pxa_bi 21388 0 (unused)
net_fd 25000 0 (unused)
usbdcore 34456 0 [pxa_bi net_fd]
usbdmonitor 5216 0but lots of errors from dmesg
edc
r10: c15b4000 r9 : 00034cd8 r8 : c5b00da8
r7 : 00000010 r6 : 00000000 r5 : c5b01258 r4 : 00000010
r3 : c5ac5ff8 r2 : 00000010 r1 : 0000000f r0 : c5b01258
Flags: Nzcv IRQs on FIQs on Mode SVC_32 Segment user
Control: 197F Table: A16B4000 DAC: 00000015 PID: 0
Process insmod (pid: 707, stackpage=c15b5000)
Stack: (0xc15b5ec0 to 0xc15b6000)
5ec0: c5b00c14 c011f66c 80000013 ffffffff c15b5f04 c15b5ee0 c5b00c14 c011f654
5ee0: 00000000 c5b011b0 c5b00000 c159d000 00000060 ffffffea c15b5fa4 c15b5f08
5f00: c0044088 c5b00aa8 c159d000 c15b5f1c c159e000 0000000b c3e0cd00 00000060
5f20: c5af0000 c5b00060 00003188 00000000 00000000 00000000 00000000 00000000
5f40: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
5f60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000005
5f80: c5b00000 00000000 00000080 c002f9e4 c15b4000 00000000 00000000 c15b5fa8
5fa0: c002f840 c0043974 00000005 c003f934 00021ad0 00034cd8 ffffffff 40016000
5fc0: 00000005 c5b00000 00000000 0002eb28 00003188 00000000 00000000 0000000b
5fe0: 400e8aa0 bfffba80 0000c938 400e8aac 60000010 00021ad0 00000000 00000000
Backtrace:
Function entered at [] from []
Function entered at [] from []
r8 = FFFFFFEA r7 = 00000060 r6 = C159D000 r5 = C5B00000
r4 = C5B011B0
Function entered at [] from []
Code: e3530000 0a000004 e1530000 0a000008 (e5933020)
SD: RCA=0xb368
SD: SD memory is detected
Unable to handle kernel NULL pointer dereference at virtual address 00000063
pgd = c0004000
*pgd = a0002001, *pmd = a0002001, *pte = a000108f, *ppte = a000100f
Internal error: Oops: ffffffff
CPU: 0
pc : [] lr : [] Tainted: P
sp : c16bdf74 ip : c16bdf98 fp : c16bdf94
r10: c0282fe4 r9 : c5ac0bb8 r8 : 20000013
r7 : c5ac2128 r6 : 00000000 r5 : c16bc000 r4 : 00000000
r3 : 00000001 r2 : c16bc000 r1 : c16bc0e8 r0 : 00000063
Flags: nzCv IRQs off FIQs on Mode SVC_32 Segment kernel
Control: 197F Table: A35F4000 DAC: 0000001D PID: 0
Process ttach (pid: 710, stackpage=c16bd000)
Stack: (0xc16bdf64 to 0xc16be000)
df60: c0041240 c003ff2c 20000093 ffffffff 00000000 c16bc000 00000000
df80: c5ac2128 c2d1cb10 c16bdfa4 c16bdf98 c0041240 c003ff18 c16bdfb4 c16bdfa8
dfa0: c0045fbc c0041220 c16bdfc4 c16bdfb8 c0046264 c0045f50 c16bdff4 c16bdfc8
dfc0: c5ac023c c004624c c2d1cb50 00000000 c03c4000 c03c4000 c03c4348 c03c4338
dfe0: 00000001 c03c5fbc 00000000 c16bdff8 c0030c04 c5ac00b0 00000000 00000000
Backtrace:
Function entered at [] from []
r8 = C2D1CB10 r7 = C5AC2128 r6 = 00000000 r5 = C16BC000
r4 = 00000000
Function entered at [] from []
Function entered at [] from []
Function entered at [] from []
Function entered at [] from []
Code: e3883080 e121f003 e5903000 e2833001 (e4803004)
Unable to handle kernel paging request at virtual address ffffffff
pgd = c0004000
*pgd = 00000000, *pmd = 00000000
Internal error: Oops: 0
CPU: 0
pc : [] lr : [] Tainted: P
sp : c16bde4c ip : c16bde60 fp : c16bde5c
r10: ffffffff r9 : ffffffff r8 : c003ff2c
r7 : ffffffff r6 : 0000000b r5 : c16bc000 r4 : c16bc000
r3 : a0000093 r2 : a0000093 r1 : ffffffff r0 : c16bc000
Flags: NzCv IRQs off FIQs on Mode SVC_32 Segment kernel
Control: 197F Table: A35F4000 DAC: 0000001D PID: 0
Process ttach (pid: 710, stackpage=c16bd000)
Stack: (0xc16bde3c to 0xc16be000)
de20: c0046168
de40: c004bb20 a0000093 ffffffff c3c8fae0 c16bde6c c16bde60 c0046168 c004baf0
de60: c16bde88 c16bde70 c00341a8 c0045f50 00000063 c16bdf2c 00000000 c16bdea8
de80: c16bde8c c0034ee4 c00340ac c16bc000 e4803004 c16bdf2c 00000063 c16bdec0
dea0: c16bdeac c0034f98 c0034e88 ffffffff 00000004 c16bdef8 c16bdec4 c0036b60
dec0: c0034f50 c16bdf2c c3190000 00000000 00000063 c16bc000 00000024 00000003
dee0: c02111e4 c02111c0 ffffffff c16bdf28 c16bdefc c0035694 c00369c4 c16bdf2c
df00: ffffffff c16bdf60 00000000 c5ac2128 20000013 20000093 c0282fe4 c16bdf94
df20: c16bdf2c c002f480 c003562c 00000063 c16bc0e8 c16bc000 00000001 00000000
df40: c16bc000 00000000 c5ac2128 20000013 c5ac0bb8 c0282fe4 c16bdf94 c16bdf98
df60: c16bdf74 c0041240 c003ff2c 20000093 ffffffff 00000000 c16bc000 00000000
df80: c5ac2128 c2d1cb10 c16bdfa4 c16bdf98 c0041240 c003ff18 c16bdfb4 c16bdfa8
dfa0: c0045fbc c0041220 c16bdfc4 c16bdfb8 c0046264 c0045f50 c16bdff4 c16bdfc8
dfc0: c5ac023c c004624c c2d1cb50 00000000 c03c4000 c03c4000 c03c4348 c03c4338
dfe0: 00000001 c03c5fbc 00000000 c16bdff8 c0030c04 c5ac00b0 00000000 00000000
Backtrace:
Function entered at [] from []
r4 = C3C8FAE0
Function entered at [] from []
Function entered at [] from []
r6 = 00000000 r5 = C16BDF2C r4 = 00000063
Function entered at [] from []
r7 = 00000063 r6 = C16BDF2C r5 = E4803004 r4 = C16BC000
Function entered at [] from []
r4 = 00000004
Function entered at [] from []
Function entered at [] from []
Function entered at [] from []
r8 = C2D1CB10 r7 = C5AC2128 r6 = 00000000 r5 = C16BC000
r4 = 00000000
Function entered at [] from []
Function entered at [] from []
Function entered at [] from []
Function entered at [] from []
Code: e5843334 e10f2000 e3823080 e121f003 (e5913000)
SD: bus 0 is unregistered.
Unable to handle kernel paging request at virtual address c5ac603c
pgd = c1770000
*pgd = a3f47021, *pmd = a3f47021, *pte = 00000000, *ppte = 00000000
Internal error: Oops: 0
CPU: 0
pc : [] lr : [<00000000>] Tainted: P
sp : c1851ec0 ip : a0000013 fp : c1851ee8
r10: c3a6f060 r9 : c3f1b73c r8 : 00003c00
r7 : c1fedd20 r6 : fffffffa r5 : 3c000000 r4 : c3f1b720
r3 : c5ac6028 r2 : c1fedd20 r1 : c3a6f060 r0 : c3f1b720
Flags: NzCv IRQs on FIQs on Mode SVC_32 Segment user
Control: 197F Table: A1770000 DAC: 00000015 PID: 0
Process mount (pid: 885, stackpage=c1851000)
Stack: (0xc1851eb0 to 0xc1852000)
1ea0: 00000000 c006b430 a0000013 ffffffff
1ec0: c3a6f060 c1fedd20 c1fedd20 c32d9268 c02541d4 c1850000 0001e89c c1851f00
1ee0: c1851eec c006b638 c006b3c8 c3a6f060 c32d9260 c1851f30 c1851f04 c00b2dd8
1f00: c006b610 c1851f20 c1851f14 c006ed30 c1fedd20 c3a6f060 00000000 c03be360
1f20: c3b1c6c0 c1851f54 c1851f34 c006390c c00b2d08 00020000 00020000 00000000
1f40: c3f1c000 c002f9e4 c1851f84 c1851f58 c0063804 c0063814 c3b1c6c0 c03be360
1f60: c006eab8 c005b128 c3f1c000 00000001 00000001 00000003 c1851fa4 c1851f88
1f80: c0063b60 c00637c4 bfffdff8 00020210 00000000 00000005 00000000 c1851fa8
1fa0: c002f840 c0063b28 bfffdff8 c00356f4 00020210 00020000 00000000 00006000
1fc0: bfffdff8 00020210 00000000 00020210 bffff658 bffff668 0001e89c 00020230
1fe0: 40137e7c bfff57e8 400db290 400db264 60000010 00020210 4021c26c 401ef29c
Backtrace:
Function entered at [] from []
Function entered at [] from []
r5 = C32D9260 r4 = C3A6F060
Function entered at [] from []
r8 = C3B1C6C0 r7 = C03BE360 r6 = 00000000 r5 = C3A6F060
r4 = C1FEDD20
Function entered at [] from []
r8 = C002F9E4 r7 = C3F1C000 r6 = 00000000 r5 = 00020000
r4 = 00020000
Function entered at [] from []
r4 = 00000003
Function entered at [] from []
r7 = 00000005 r6 = 00000000 r5 = 00020210 r4 = BFFFDFF8
Code: e5840018 e5943018 e3530000 0a000048 (e5931014)
no /dev/mmcd/disc0/part devices created, just a /dev/mmcd/disc0/disc, which fails to mount
root-:) mount /dev/mmcd/disc0/disc /mnt/card
Segmentation fault[div align=\"right\"][a href=\"index.php?act=findpost&pid=155301\"][{POST_SNAPBACK}][/a][/div]
that's too bad then. no big SD support in that case...
-
Hi. I got the upgrade to pdaxii13 working on my 860 model from a clean install of beta1. I am having trouble with it not recognizing any SD card after the upgrade. Any ideas?
Also if I quit X, the cli is scrambled and rotated. I have no problem with X being rotated though.
Apart from that I am eager to see what this distro can do.
Thanks for any help...
-
Hi. I got the upgrade to pdaxii13 working on my 860 model from a clean install of beta1. I am having trouble with it not recognizing any SD card after the upgrade. Any ideas?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=158720\"][{POST_SNAPBACK}][/a][/div]
Sort of solved my first query. I had tried mounting from the command line, but clearly I was doing that wrong. Then I installed rox, which took a while because of a missing library, and then from rox filer just clicking on the card icon when in the /mnt folder did the trick.
Still got the problem I had on exiting X.
-
Hi. I got the upgrade to pdaxii13 working on my 860 model from a clean install of beta1. I am having trouble with it not recognizing any SD card after the upgrade. Any ideas?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=158720\"][{POST_SNAPBACK}][/a][/div]
Sort of solved my first query. I had tried mounting from the command line, but clearly I was doing that wrong. Then I installed rox, which took a while because of a missing library, and then from rox filer just clicking on the card icon when in the /mnt folder did the trick.
Still got the problem I had on exiting X.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=158742\"][{POST_SNAPBACK}][/a][/div]
sorry, I have no idea why it is rotated, but just don't exit X
actually, can you rotate the screen before you exit X. will the display then be correct?
-
sorry, I have no idea why it is rotated, but just don't exit X
actually, can you rotate the screen before you exit X. will the display then be correct?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=158814\"][{POST_SNAPBACK}][/a][/div]
That was fun. Simple rotation and back again works fine. Rotate the screen and quit X leads to an interlaced screen with the text repeated in 3 columns. Looks very odd/ but you can just make out the login prompt. So I relogin and startx, and it is completely confused. Not only does the cursor move independently (mirrored and rotated I think) of the stylus, but it is the wrong way round and the applet icons are stretched.
So I wont be doing that too often.
Incidentally the keymapping is not quite right. I fixed the mouse buttons with the input panel, and found a fix for the brightness and screen magnification fn buttons above 1 2 3 4. But the magnifying has similar effects to the screen with it being rotated.
I guess I'd like to fix it if it needs it so I can play games like quake... going to try it now.
I'd also like to get my old corgi keymapping back from beta1. I saved the xmodmap, but am not sure what to with it.
However, I am still thrilled to get pdaxii13 on my c860... looking forward to getting it working.
Thanks
John
-
sorry, I have no idea why it is rotated, but just don't exit X
actually, can you rotate the screen before you exit X. will the display then be correct?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=158814\"][{POST_SNAPBACK}][/a][/div]
That was fun. Simple rotation and back again works fine. Rotate the screen and quit X leads to an interlaced screen with the text repeated in 3 columns. Looks very odd/ but you can just make out the login prompt. So I relogin and startx, and it is completely confused. Not only does the cursor move independently (mirrored and rotated I think) of the stylus, but it is the wrong way round and the applet icons are stretched.
So I wont be doing that too often.
Incidentally the keymapping is not quite right. I fixed the mouse buttons with the input panel, and found a fix for the brightness and screen magnification fn buttons above 1 2 3 4. But the magnifying has similar effects to the screen with it being rotated.
I guess I'd like to fix it if it needs it so I can play games like quake... going to try it now.
I'd also like to get my old corgi keymapping back from beta1. I saved the xmodmap, but am not sure what to with it.
However, I am still thrilled to get pdaxii13 on my c860... looking forward to getting it working.
Thanks
John
[div align=\"right\"][a href=\"index.php?act=findpost&pid=158958\"][{POST_SNAPBACK}][/a][/div]
since i dont have a c8x0, i never touched the keymap file. if you have a better working one, send it my way and i will include it in pdaXii13...
in fact, send any useful modifications my way for inclusion...
-
in fact, send any useful modifications my way for inclusion...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=158959\"][{POST_SNAPBACK}][/a][/div]
Sure... if I get anything useful done I will send config files for you to ponder.
Quake started tiny and rotated. Returning to desktop and all screwed. Reboot fixes tho.
-
If I run xrandr in aterm it returns:
0 640x480
1 480x640
2 240x320
I guess that last line should be 320x240. Where does xrandr pick up these values from and can I change the last one?
-
If I run xrandr in aterm it returns:
0 640x480
1 480x640
2 240x320
I guess that last line should be 320x240. Where does xrandr pick up these values from and can I change the last one?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=158964\"][{POST_SNAPBACK}][/a][/div]
try editing /usr/X11R6/bin/startx
and add the following value for RES
-screen 240x320@270
or
-screen 640x480@270
make sure you add it to the section for SL-C860, there is a similar entry for SL-C1000....
-
If I run xrandr in aterm it returns:
0 640x480
1 480x640
2 240x320
I guess that last line should be 320x240. Where does xrandr pick up these values from and can I change the last one?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=158964\"][{POST_SNAPBACK}][/a][/div]
try editing /usr/X11R6/bin/startx
and add the following value for RES
-screen 240x320@270
or
-screen 640x480@270
make sure you add it to the section for SL-C860, there is a similar entry for SL-C1000....
[div align=\"right\"][a href=\"index.php?act=findpost&pid=158965\"][{POST_SNAPBACK}][/a][/div]
I have actually got Quake running full screen. I'll have to write a little script to automate it.
xrandr -s 240x320
xrandr -o 3
/usr/apps/Games/Quake/AppRun
I didn't find editing startx made any difference.
When I quit Quake it returns to full res landscape screen the right way up. But unfortunately the cursor isn't where I press the stylus, so I press the menu button, then arrow keys to aterm and type reboot to reset the Z.
It's not that I am desperate to run quake, I just want to know that if I come across apps/games that want the lower resolution screen I can get around the problem.
If you ave any other suggestions for startx I am game.
Thanks
John
-
Hi. I got the upgrade to pdaxii13 working on my 860 model from a clean install of beta1. I am having trouble with it not recognizing any SD card after the upgrade. Any ideas?
Also if I quit X, the cli is scrambled and rotated. I have no problem with X being rotated though.[div align=\"right\"][a href=\"index.php?act=findpost&pid=158720\"][{POST_SNAPBACK}][/a][/div]
Sort of solved my first query. I had tried mounting from the command line, but clearly I was doing that wrong. Then I installed rox, which took a while because of a missing library, and then from rox filer just clicking on the card icon when in the /mnt folder did the trick.[div align=\"right\"][a href=\"index.php?act=findpost&pid=158742\"][{POST_SNAPBACK}][/a][/div]
Hi macwiz. I've just applied the pdaxii13 upgrade to my beta2 install, and I'm experiencing the same two problems as you. Cards won't mount (neither sd nor cf) and I get the funky sideways screen when I quit X. I know you said the former problem was solved by installing rox, but any idea of what the 'behind the scenes' issue was? According to my earlier findings, pdax1113's updated modules weren't compatible with the C860's kernel, but see below.
And did you ever get the screen rotation fixed? thks
[regarding failed tests of the 2.4.18 sd module]
that's too bad then. no big SD support in that case...[div align=\"right\"][a href=\"index.php?act=findpost&pid=155309\"][{POST_SNAPBACK}][/a][/div]
Hi again, Meanie. I've tried grappling with pdaxii13 again & I stumbled on something interesting. Previously my testing was from a beta1 base install. This time I tried it from my last beta2 working image (which was the last beta that really worked well on the C860). It was with my flipping back & forth that I noticed that the two use different kernels!
beta1:
# uname -a
Linux zaurus 2.4.18-rmk7-pxa3-embedix #1 Mon, 14 Nov 2005 20:35:45 +0000 armv5tel unknownbeta2:
root@zaurus# uname -a
Linux zaurus 2.4.20 #1 Tue, 07 Mar 2006 01:09:26 +0000 armv5tel unknownDoes this mean that there might be hope for me yet? i.e. is there another module for the 2.4.20 kernel I can try?
-
....
beta1:
# uname -a
Linux zaurus 2.4.18-rmk7-pxa3-embedix #1 Mon, 14 Nov 2005 20:35:45 +0000 armv5tel unknownbeta2:
root@zaurus# uname -a
Linux zaurus 2.4.20 #1 Tue, 07 Mar 2006 01:09:26 +0000 armv5tel unknownDoes this mean that there might be hope for me yet? i.e. is there another module for the 2.4.20 kernel I can try?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=164388\"][{POST_SNAPBACK}][/a][/div]
sashz ported the 2.4.20 kernel to the c7x0 series!? Is this uname from before or after doing a pdaXii13 patching? If it really is running 2.4.20 then maybe the enhanced SD driver from the 3200 will work.
-
sashz ported the 2.4.20 kernel to the c7x0 series!? Is this uname from before or after doing a pdaXii13 patching? If it really is running 2.4.20 then maybe the enhanced SD driver from the 3200 will work.[div align=\"right\"][a href=\"index.php?act=findpost&pid=164399\"][{POST_SNAPBACK}][/a][/div]
I'm pretty sure both of these were pre-upgrade, but I'll reflash & double check. And if by the 3200 sd driver you mean the one included in the pdaxii13 upgrade tarball, then no, it seems to cause problems. I'll double check that too & report back.
-
sashz ported the 2.4.20 kernel to the c7x0 series!? Is this uname from before or after doing a pdaXii13 patching? If it really is running 2.4.20 then maybe the enhanced SD driver from the 3200 will work.[div align=\"right\"][a href=\"index.php?act=findpost&pid=164399\"][{POST_SNAPBACK}][/a][/div]
I'm pretty sure both of these were pre-upgrade, but I'll reflash & double check. And if by the 3200 sd driver you mean the one included in the pdaxii13 upgrade tarball, then no, it seems to cause problems. I'll double check that too & report back.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=164442\"][{POST_SNAPBACK}][/a][/div]
Well that is potentially good and bad news. Yes, I was referring to the one included in the tarball. Meanie repackaged the 3200 enhanced sd driver that shipped with the SharpROM so that it could be used under pdaX. I'm surprised that it didn't work. I hope it isn't due to hardware differences between the xx0 and xx00.
-
I'm pretty sure both of these were pre-upgrade, but I'll reflash & double check.
Confirmed. pre-upgrade beta1 = 2.4.18, beta2 (& presumably beta3) = 2.4.20. Which is what I expected, since AFAIK pdaxii13 doesn't touch the kernel itself.
And if by the 3200 sd driver you mean the one included in the pdaxii13 upgrade tarball, then no, it seems to cause problems. I'll double check that too & report back.[div align=\"right\"][a href=\"index.php?act=findpost&pid=164442\"][{POST_SNAPBACK}][/a][/div]
Well that is potentially good and bad news. Yes, I was referring to the one included in the tarball. Meanie repackaged the 3200 enhanced sd driver that shipped with the SharpROM so that it could be used under pdaX. I'm surprised that it didn't work. I hope it isn't due to hardware differences between the xx0 and xx00.[div align=\"right\"][a href=\"index.php?act=findpost&pid=164449\"][{POST_SNAPBACK}][/a][/div]
No good news I'm afraid. After upgrade & reboot, NO cards are mounting properly, sd or cf. Using a 1GB sd & a 512MB cf for testing. Neither /dev/mm* nor /dev/hd* exist. Lots of errors from dmesg, most notably for sd:
pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)and for hd:
hda: LEXAR ATA FLASH, ATA DISK drive
hda: ERROR, PORTS ALREADY IN USE
And now one of the best things from beta2 (over beta1) is gone; the fn-brigthness & fn-zoom keys are broken (sigh).
The main reason I was trying to get pdaxii13 working is that I'm wanting to try other rom's, but there currently isn't an easy restore back to R197/8 like the NAND utilities provide. I also tried Angstrom again, but no joy there yet (yes, I did send a help message to the mailing list). From this state, I'm willing/forced to play around a bit .
-
I'm pretty sure both of these were pre-upgrade, but I'll reflash & double check.
Confirmed. pre-upgrade beta1 = 2.4.18, beta2 (& presumably beta3) = 2.4.20. Which is what I expected, since AFAIK pdaxii13 doesn't touch the kernel itself.
And if by the 3200 sd driver you mean the one included in the pdaxii13 upgrade tarball, then no, it seems to cause problems. I'll double check that too & report back.[div align=\"right\"][a href=\"index.php?act=findpost&pid=164442\"][{POST_SNAPBACK}][/a][/div]
Well that is potentially good and bad news. Yes, I was referring to the one included in the tarball. Meanie repackaged the 3200 enhanced sd driver that shipped with the SharpROM so that it could be used under pdaX. I'm surprised that it didn't work. I hope it isn't due to hardware differences between the xx0 and xx00.[div align=\"right\"][a href=\"index.php?act=findpost&pid=164449\"][{POST_SNAPBACK}][/a][/div]
No good news I'm afraid. After upgrade & reboot, NO cards are mounting properly, sd or cf. Using a 1GB sd & a 512MB cf for testing. Neither /dev/mm* nor /dev/hd* exist. Lots of errors from dmesg, most notably for sd:
pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)and for hd:
hda: LEXAR ATA FLASH, ATA DISK drive
hda: ERROR, PORTS ALREADY IN USE
And now one of the best things from beta2 (over beta1) is gone; the fn-brigthness & fn-zoom keys are broken (sigh).
The main reason I was trying to get pdaxii13 working is that I'm wanting to try other rom's, but there currently isn't an easy restore back to R197/8 like the NAND utilities provide. I also tried Angstrom again, but no joy there yet (yes, I did send a help message to the mailing list). From this state, I'm willing/forced to play around a bit .
[div align=\"right\"][a href=\"index.php?act=findpost&pid=164455\"][{POST_SNAPBACK}][/a][/div]
Very interesting about the 2.4.20 kernel under beta 2.
I used see that SD error all the time when I restarted Cacko so, even if we can get your SD slot working with the beta2 kernel I wouldn't be surprised if you still see the error. Is the package in the pdaXii13 sdcard_2.4.20_armv5tel.ipk?
The ROX depends are share-mime-info and gtk2. I doubt either of those would have the goodies to kick start your CF slot so it must be ROX itself.
I seem to remember that at one point that the accessx (sticky keys) in pdaXii13 was conflicting with keymapping. Meanie has since fixed that issue. Perhaps that might be related to your issue. On the other hand does either Ctrl-4 or japanese key to the left of the - key-4 increase your brightness? Wait does the 860 have a Ctrl key?
I hope some of this helps.
-
Okay, how about beta3 for the 860? Image and Feed are here. (http://distro.ibiblio.org/pub/linux/distributions/pdaxrom/download/contrib/1.1.0beta3/Zaurus-7x0-860/)
In the 7x0/860 feed is this.
Package: sdcard
Source: http://www.pdaXrom.org/src/sdcard-0.1.0.tar.bz2 (http://www.pdaXrom.org/src/sdcard-0.1.0.tar.bz2)
Priority: optional
Section: Utilities
Maintainer: Alexander Chukov <sash@pdaXrom.org>
Architecture: armv5tel
Version: 0.1.0-1
Depends:
Description: SD card drivers and utils
Size: 17.5k
I don't know if it gives greater than 1GB support though.
-
Okay, how about beta3 for the 860? Image and Feed are here. (http://distro.ibiblio.org/pub/linux/distributions/pdaxrom/download/contrib/1.1.0beta3/Zaurus-7x0-860/)
Already had that one too, tried with same results.
In the 7x0/860 feed is this.
[...snip...]
I don't know if it gives greater than 1GB support though.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=164462\")
I tried the one from the [a href=\"http://www.tyrannozaurus.com/feed/beta3/feed/sdcard_2.4.20_armv5tel.ipk]TY feed[/url], no change. it seems there's no difference from which of the 3 beta's you start, cards no longer mount after the upgrade. At least for me that's the case, although we haven't heard back from macwiz yet.
Looks like I'm going back to Cacko until I have time to reinstall r197.
Thanks for the all help, Holovector.
-
Okay, how about beta3 for the 860? Image and Feed are here. (http://distro.ibiblio.org/pub/linux/distributions/pdaxrom/download/contrib/1.1.0beta3/Zaurus-7x0-860/)
Already had that one too, tried with same results.
In the 7x0/860 feed is this.
[...snip...]
I don't know if it gives greater than 1GB support though.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=164462\")
I tried the one from the [a href=\"http://www.tyrannozaurus.com/feed/beta3/feed/sdcard_2.4.20_armv5tel.ipk]TY feed[/url], no change. it seems there's no difference from which of the 3 beta's you start, cards no longer mount after the upgrade. At least for me that's the case, although we haven't heard back from macwiz yet.
Looks like I'm going back to Cacko until I have time to reinstall r197.
Thanks for the all help, Holovector.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=164465\"][{POST_SNAPBACK}][/a][/div]
You're welcome. I just wish I could have been more help to you.
-
Hi macwiz. I've just applied the pdaxii13 upgrade to my beta2 install, and I'm experiencing the same two problems as you. Cards won't mount (neither sd nor cf) and I get the funky sideways screen when I quit X. I know you said the former problem was solved by installing rox, but any idea of what the 'behind the scenes' issue was? According to my earlier findings, pdax1113's updated modules weren't compatible with the C860's kernel, but see below.
And did you ever get the screen rotation fixed? thks
Hi grog.
Er, I'm not really very technical so I don't know why I dabble with these things.
I did have fun with pdaxii13 on my c860, but found that installing things from various beta3 feeds would break it regularly, so I kind of gave up. I never did solve the rotation problem on exiting X, and really I was never likely to.
Right now I'm trying Angstrom - glutton for punishment - and I suspect strongly that this will be a wasted effort for me. However, finding that my 1 GB SD was mounted automatically by it I popped in my 2 GB card and it was mounted OK too! This card I originally bought for my Z, but finding it didn't work, it has languished in my loox 720 (yuk). I haven't got anything bigger to try, but perhaps there is something in it for you if you need larger SD support.
Good luck
John
-
Er, I'm not really very technical so I don't know why I dabble with these things.
'cause it's fun?
I did have fun with pdaxii13 on my c860, but found that installing things from various beta3 feeds would break it regularly, so I kind of gave up. I never did solve the rotation problem on exiting X, and really I was never likely to.
Right now I'm trying Angstrom - glutton for punishment - and I suspect strongly that this will be a wasted effort for me. However, finding that my 1 GB SD was mounted automatically by it I popped in my 2 GB card and it was mounted OK too! This card I originally bought for my Z, but finding it didn't work, it has languished in my loox 720 (yuk). I haven't got anything bigger to try, but perhaps there is something in it for you if you need larger SD support.[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=164470\")
Actually you now have me curious about Angstrom support for the C860. I just sent a note to the devel list yesterday 'cause the latest console image won't run at all for me (see [a href=\"http://lists.linuxtogo.org/pipermail/angstrom-distro-devel/2007-July/000449.html]here[/url] for details, no answer yet). But you say you're running it? How did you get it installed, if you don't mind me asking?
On second thought, maybe the reply should be in a different thread so we don't get this one off track. Post here (https://www.oesf.org/forums/index.php?showtopic=24335). thks
-
I have added pelrun's hacked sd module so SD cards > 1GB should now also work on 7x0/8x0 models...
-
I have added pelrun's hacked sd module so SD cards > 1GB should now also work on 7x0/8x0 models...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=166126\"][{POST_SNAPBACK}][/a][/div]
I'm trying it tonight on a C760, I'll report the SD 2go test
OK, here is some feedback.
The version is 5.4.9 Charlie.
The first things I notice that don't work: the light cannot be changed with fn+3 or 4
The zoom cannot be changed with fn+1 or 2
If I'm on a terminal I can see that fn+4 inputs a 4 as if I didn't press fn
The CF card that is mounted doesn't want to unmount with the applet at least (eject failed message)
My 2go SD card doesn't mount. A 1go doesn't either.
A USB entry is in this mounting applet although I don't have one on the C760.
I'm going to try beta1 without pdaxii13 and tell you the difference.
-
I have added pelrun's hacked sd module so SD cards > 1GB should now also work on 7x0/8x0 models...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=166126\"][{POST_SNAPBACK}][/a][/div]
I'm trying it tonight on a C760, I'll report the SD 2go test
OK, here is some feedback.
The version is 5.4.9 Charlie.
The first things I notice that don't work: the light cannot be changed with fn+3 or 4
The zoom cannot be changed with fn+1 or 2
If I'm on a terminal I can see that fn+4 inputs a 4 as if I didn't press fn
The CF card that is mounted doesn't want to unmount with the applet at least (eject failed message)
My 2go SD card doesn't mount. A 1go doesn't either.
A USB entry is in this mounting applet although I don't have one on the C760.
I'm going to try beta1 without pdaxii13 and tell you the difference.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167665\"][{POST_SNAPBACK}][/a][/div]
Try the "super_L" key (second one after control) + 1 or 2 or 3 or 4 instead of "Fn"
For "F4" input I changed the keymap to got it with "Fn" + number. It's set to "Fn" + "Shift" + number by default.
-
Back to beta1: the CF and sd cards mount and unmount correctly but not my 2gigs SD.
-
Just trying build 5.4.9 on C700:
- 2G SD works
- no automounting of SD, have to mount it manually
- CF mounts automatically
- Fn+3,4 (backlight) did not work. the keyboard behaviour was strange (Tab did tab + CAPSLOCk alltogether etc)
after disabling everything in pdaXii13config - config it started to work, so something is harming the keymap.
- Fn +1,2 (zoom) is broken, it Fn+2 rotates the screen and it stays so, also touch screen is unusable then
- when exiting X the console is messed up and rotated (almost invisible), after going back to X, the screen is rotated 90°
and touch screen is unusable.
to the unusable touch screen: it seems like that the cursor is rotated 90° to the real image if you understand (you touch the screen, but the touch
appears somewhere else)
also last problem, which may be something completely unrelated: after waking up from suspend, sometimes the backlight stays off a keyboard
does not react, I can barely see that the display is showing something, no reaction to Fn+4 or other keys, have to hardreset then
-
Just trying build 5.4.9 on C700:
- 2G SD works
- no automounting of SD, have to mount it manually
- CF mounts automatically
- Fn+3,4 (backlight) did not work. the keyboard behaviour was strange (Tab did tab + CAPSLOCk alltogether etc)
after disabling everything in pdaXii13config - config it started to work, so something is harming the keymap.
- Fn +1,2 (zoom) is broken, it Fn+2 rotates the screen and it stays so, also touch screen is unusable then
- when exiting X the console is messed up and rotated (almost invisible), after going back to X, the screen is rotated 90°
and touch screen is unusable.
to the unusable touch screen: it seems like that the cursor is rotated 90° to the real image if you understand (you touch the screen, but the touch
appears somewhere else)
also last problem, which may be something completely unrelated: after waking up from suspend, sometimes the backlight stays off a keyboard
does not react, I can barely see that the display is showing something, no reaction to Fn+4 or other keys, have to hardreset then
yes, 2GB SD is working now thanks to pelrun
automounting for SD can be fixed, but need testing
all the keys will need customisation/fixing since the keycodes are different to those of akita/spitz
you probably turned off sticky keys using pdaXcfg. it works with the akita/spitz models but probably causes other things due to keycode differences
i need someone to build a custom keymap for those models...
and finally, probably the biggest problem is screen rotation and zooming. seems to be misbehaving badly but unfortunately, I cannot test nor fix it...