OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: mozz on November 06, 2005, 04:57:38 am
-
Hello,
I've test OZ 3.5.4RC with GPE on my poodle (5600) and I've seen a "little" bug.
When I click on the screen, the pointer goes to another part of the screen. If I click down then the pointer goes up to the screen, like a mirror. I've tried to re-calibrate and nothing, :-(
Thanks.
-
You have had more luck than me with it I decided to give it a whirl on my Collie and it hangs at "Starting GPE display manager : gpe-dm
Oh well it is an RC
-
I've test OZ 3.5.4RC with GPE on my poodle (5600) and I've seen a "little" bug.
When I click on the screen, the pointer goes to another part of the screen. If I click down then the pointer goes up to the screen, like a mirror. I've tried to re-calibrate and nothing, :-(
Can you add this to the bug tracker please (if you haven't already).
Si
-
I've test OZ 3.5.4RC with GPE on my poodle (5600) and I've seen a "little" bug.
When I click on the screen, the pointer goes to another part of the screen. If I click down then the pointer goes up to the screen, like a mirror. I've tried to re-calibrate and nothing, :-(
Can you add this to the bug tracker please (if you haven't already).
Si
[div align=\"right\"][a href=\"index.php?act=findpost&pid=102557\"][{POST_SNAPBACK}][/a][/div]
Hi,
I just do it, bug #443
-
I found that my calibration is way off. I have to touch the bottom of the screen to activate the close window ('x') at the top of an application, for instance. When I try to run xtscal to rcalibrate, I get the error that can't write to /etc/, disk full. I noticed that / is indeed full. Could this be similar to what was discussed in this thread (https://www.oesf.org/forums/index.php?showtopic=13204&hl=)?
I also can't find the bug that you reference above. Is this (http://handhelds.org/~bugzilla/) the right place to look?
thks
-
The bugtracker in question is here: http://bugs.openembedded.org/ (http://bugs.openembedded.org/)
I'm not sure why / is full for you. Have you installed any stuff? Perhaps the flash size has been set wrongly in OE (so the rootfs image is too large).
Si
-
The bugtracker in question is here: http://bugs.openembedded.org/ (http://bugs.openembedded.org/)
Thanks. Found it.
I'm not sure why / is full for you. Have you installed any stuff?
For me it was like that from a fresh flash. Since I couldn't work with it properly, I didn't try to do anything (else) with it.
Perhaps the flash size has been set wrongly in OE (so the rootfs image is too large).[div align=\"right\"][a href=\"index.php?act=findpost&pid=109511\"][{POST_SNAPBACK}][/a][/div]
That sounds like a reasonable explanation to me. I've added my comments to the bug. Who do we talk to about adjusting the flash size?
-
How large is the flash on the poodle then?
In org.openembedded.dev/conf/machines/poodle.conf it's set as:
ROOT_FLASH_SIZE = "32"
(Note that this is a couple of weeks old, so changes may have been made, plus the image you're running comes from the 3.5.4 branch rather than the development branch so it may be different there anyway)
Is this correct? I thought the 32MB was split between the /home and / mounts?
In any case, if you think this is an issue I'd ask on #oe or #openzaurus and then create a new bug about it.
Si
-
How large is the flash on the poodle then?
I thought it was 32mb, but when I look at the output of df on my current install of opie 3.5.4 (stuff installed on home & symlinked since the flash):
Filesystem Size Used Available Use% Mounted on
/dev/mtdblock2 22.0M 21.6M 400.0k 98% /
/dev/mtdblock3 35.0M 11.8M 23.2M 34% /home
tmpfs 14.6M 52.0k 14.6M 0% /var
tmpfs 14.6M 0 14.6M 0% /media/ram
the total of the first partition & the two tmpfs's is only about 51mb & the home fs only 35mb. So where's the total 96mb that the unit supposed to have? I must be reading it wrong somehow.
In any case, the opie image seems to be ok, so does that have a different setting?
In any case, if you think this is an issue I'd ask on #oe or #openzaurus and then create a new bug about it.[div align=\"right\"][a href=\"index.php?act=findpost&pid=109526\"][{POST_SNAPBACK}][/a][/div]
As soon as we get this straightened out I will. thks
-
You could try http://ewi546.ewi.utwente.nl/tmp/hrw/oz-3.5.4-rc-poodle/ (http://ewi546.ewi.utwente.nl/tmp/hrw/oz-3.5.4-rc-poodle/) which is my image for poodle (opie-image only)
-
You could try http://ewi546.ewi.utwente.nl/tmp/hrw/oz-3.5.4-rc-poodle/ (http://ewi546.ewi.utwente.nl/tmp/hrw/oz-3.5.4-rc-poodle/) which is my image for poodle (opie-image only)[div align=\"right\"][a href=\"index.php?act=findpost&pid=109550\"][{POST_SNAPBACK}][/a][/div]
The problem seems to be only with the gpe image; the opie image works fine. But thanks for the offer
-
I can provide gpe-image too.
-
I can provide gpe-image too.[div align=\"right\"][a href=\"index.php?act=findpost&pid=109662\"][{POST_SNAPBACK}][/a][/div]
Ok. cool. So what's the difference between yours & the 'official' ones? Do you know what the flash size is for your opie image compared to the gpe one? Are they different?
thks
-
official 3.5.4-rc1 is quite old - we fixed some bugs later.
due to one problem I cannot now provide working gpe-image (build problem)
-
official 3.5.4-rc1 is quite old - we fixed some bugs later.
due to one problem I cannot now provide working gpe-image (build problem)[div align=\"right\"][a href=\"index.php?act=findpost&pid=110235\"][{POST_SNAPBACK}][/a][/div]
So sad . Thanks for trying. As I'm settling in on OPIE right now anyway, I'll take you up on your offer & try the your newer image anyway. At least it's OZ .
EDIT: were you able to confirm the build size of GPE vs OPIE? Are they different?
Thanks
-
My opie-image for poodle is 20M in size. If it's too big then propose something to remove - I'm open for discussion.
-
My opie-image for poodle is 20M in size. If it's too big then propose something to remove - I'm open for discussion.[div align=\"right\"][a href=\"index.php?act=findpost&pid=110259\"][{POST_SNAPBACK}][/a][/div]
I haven't had a chance to try your neweer OPIE image, but I know the 'official' OPIE one works ok. It's the GPE image that we seem to be having problems with. Do you know what the default flash size it set for GPE?
-
How large is the flash on the poodle then?
I thought it was 32mb, but when I look at the output of df on my current install of opie 3.5.4 (stuff installed on home & symlinked since the flash):
Filesystem Size Used Available Use% Mounted on
/dev/mtdblock2 22.0M 21.6M 400.0k 98% /
/dev/mtdblock3 35.0M 11.8M 23.2M 34% /home
tmpfs 14.6M 52.0k 14.6M 0% /var
tmpfs 14.6M 0 14.6M 0% /media/ram
the total of the first partition & the two tmpfs's is only about 51mb & the home fs only 35mb. So where's the total 96mb that the unit supposed to have? I must be reading it wrong somehow.
I believe the 96 Mb is 32MB flash (mtdblock1 + mtdblock2) +32Mb flash (mtblock3) and 32 Mb RAM. The first ~10Mb (mtdblock1) is where the kernel sits.
Aren't Marketeers great ...
Hope this helps..