Messages

1

Angstrom & OpenZaurus / Oz 3.5.3 Bug List

« on: August 04, 2005, 10:20:23 pm »

OZ 3.5.3
Upgrade kernel
Hentges ROM
SL5500/Collie
Opie

Issue: Hardware buttons stop working, randomnly, after turning on.

Details: After every reboot, after suspending and awakening between once and three times, the hardware buttons, including the keyboard, will not be recognised and will have no effect after turning it on. Attemping to reboot using the applet or from opie-embeddedconsole will result in a freeze, attemping to switch to a virtual terminal will fail.

Also: I have recently noticed, while looking for every other symptom I can find, that 'keventd' has become a zombie process every time this happens.

IT seems to happen less often if left to turn itself off, instead of actively telling it to suspend, but still happens.

2

Angstrom & OpenZaurus / Oz 3.5.3 Bug List

« on: June 05, 2005, 12:12:52 am »

________________________________
- SL5500
- kernel 2.4.18
- opie 1.2.0
________________________________
DESCRIPTION OF THE BUG(s) :

When holding down the 4th button(beside of "house button" on the middle) the zaurus turns off the light and also shuts down. Then "Cancel On/Off" button doesn't bring it up again.

 You will have to do a soft reset to turn the zaurus on again.




________________________________
[div align=\"right\"][a href=\"index.php?act=findpost&pid=82572\"][{POST_SNAPBACK}][/a][/div]

That would be the menu key for a short press, or turning the light off for a long press, as set in standard configuration.

I also have this problem, with the same symptoms described above.

3

Angstrom & OpenZaurus / Oz 3.5.3 Bug List

« on: May 10, 2005, 10:02:55 pm »

Interesting, but irrelevant to my case. As I stated above, I will _never_ install something as fundamental as libc6 to anything other than root, and haven't done so in this case. So I still don't know why these errors occur.

Nor have I upgraded libc6, incidentally.

Sl-5500/Collie
3.5.3
GPE

***** WARNING REFLASH REQUIRED *****
Watch out for installing libc6 onto a SD card ( CF card also affected but not confirmed )

When "ipkg-link mount /media/card/packages" is used to link from the SD card after installing a package everything goes OK until libc6 is attempted to be linked. The rug is pulled from under the system's nose and errors concerning the shared library libc.so.6 are everywhere. "ls" no longer works and the system is badly broken.

A reflash of the system fixes it. Clearly the symlinks for libc6 have badly gone wrong.


[div align=\"right\"][a href=\"index.php?act=findpost&pid=78712\"][{POST_SNAPBACK}][/a][/div]

4

Angstrom & OpenZaurus / Oz 3.5.3 Bug List

« on: May 03, 2005, 06:53:22 pm »

ln is provided by busybox iirc.

Have you tried to upgrade or installed busybox to a storage card?


Si
[div align=\"right\"][a href=\"index.php?act=findpost&pid=78001\"][{POST_SNAPBACK}][/a][/div]

You do recall correctly.

I haven't tried to upgrade busybox, not having seen a busybox upgrade. There isn't one in the feed. I haven't tried to move it, as I firmly believe in keeping all the real fundamentals (busybox, bash, libc6, that sort of thing) installed to root, where fewer things should be able to go wrong, like symlinks no longer working.

I haven't tried to install root to SD, either, just a standard 40-24 kernel, and I flashed completely with 3.5.3 instead of using updater.sh

Do you think I should try it, or are you asking if I have?

5

Angstrom & OpenZaurus / Oz 3.5.3 Bug List

« on: May 02, 2005, 08:44:08 pm »

More information! Part way to a solution!

It's opie-embeddedkonsole.

I was just, half an hour after posting the report, carefully installing a couple of packages so that my Zaurus would still be useful for the two or three tasks I absolutely have to have it for. I don't like opie-console, so I always use opie-embeddedkonsole instead.

So I installed it, and IMMEDIATELY, I lost all packges installed to /media/ram. I checked /opt/QtPalmtop/bin as the easiest confirmation, and sure enough all links to files on /media/ram had been replaced by symlinks to themselves.

I uninstalled opie-embeddedkonsole, rebooted, and presto, ipkg-link restored all packages on /media/ram again. This is the first time I have been able to restore `ln` functionality, after having to reflash 4, maybe 5, times.

[div align=\"right\"][a href=\"index.php?act=findpost&pid=77818\"][{POST_SNAPBACK}][/a][/div]

No, sorry, that's still wrong.

It was pure coincidence that it was opie-embeddedkonsole that caused the problem. I have since discovered more information, including this other symptom:

During ipkg operations, $DESTINATION/usr/lib/ipkg/status is copied to status.tmp, changes written to status.tmp, then status.tmp copied to status and deleted. When `ln` stops working properly, status.tmp remains, and status is not modified.

Doing it manually, `mv` returns a 'no such file or directory' error message, but `cp` and `rm` will still work. This suggests a file system or libc error to me.

So, at the moment, after doing a considerable amount of package removal and (re)installation, to configure things to my liking, I can uninstall multiple packages at once safely, but can only install packages individually. After each installation, I then need to check $DESTINATION/usr/lib/ipkg/status before proceeding with anything else. If there is an error, I need to cp/rm status.tmp to status, then *immediately* reboot, clean up by deleting and reinstalling the package I was working on, and check that before doing anything else. This will prevent permanent `ln`/`mv` errors.

6

Angstrom & OpenZaurus / Oz 3.5.3 Bug List

« on: May 01, 2005, 11:23:31 pm »

A mighty, showstopping, life-destroying problem:

More information! Part way to a solution!

It's opie-embeddedkonsole.

I was just, half an hour after posting the report, carefully installing a couple of packages so that my Zaurus would still be useful for the two or three tasks I absolutely have to have it for. I don't like opie-console, so I always use opie-embeddedkonsole instead.

So I installed it, and IMMEDIATELY, I lost all packges installed to /media/ram. I checked /opt/QtPalmtop/bin as the easiest confirmation, and sure enough all links to files on /media/ram had been replaced by symlinks to themselves.

I uninstalled opie-embeddedkonsole, rebooted, and presto, ipkg-link restored all packages on /media/ram again. This is the first time I have been able to restore `ln` functionality, after having to reflash 4, maybe 5, times.

I have, however, absolutely no idea why. Or why it took up to a week on previous occasions.

7

Angstrom & OpenZaurus / Oz 3.5.3 Bug List

« on: May 01, 2005, 10:18:08 pm »

A mighty, showstopping, life-destroying problem:

SL-5500/Collie
3.5.3
Opie
All upgrades as at April 27.
________________________________
DESCRIPTION OF THE BUG(s) :
(bugtracker where bug is reported and bugnumber)

I haven't reported it yet, as I can't seem to get into the OE bugtracker at the moment.

Some time after flashing with 3.5.3, between an hour or most of a week, `ln -s` will suddenly stop working properly, preventing manual commands or ipkg-link from working. If using opie-packagemanager, ipkg-link seems to be called with `mount`, thereby destroying all packages on that media, ram or SD. installations to root will also fail.

Details: `ln -s` will create a link to itself. Example (edited for legibility):
  $ ln -s /media/card/etc/rsyncd.conf /etc/rsyncd.conf
  $ ls -l /etc/rsyncd.conf
  $ /etc/rsyncd.conf -> /etc/rsyncd.conf

Also, ipkg-install -dest root <package> will result in all files in <package> being replaced with symlinks to themselves. Thereby rendering them useless.

This will start occuring with any usage of `ln` or `ipkg-link` at a random time,  without any rhyme or reason that I can determine and without ever reverting to correct behaviour.

________________________________
SOLUTION (if found) :

No idea. Help!

Suggestion: Is it possible to make opie-advancedfm show symlinks that don't point to a valid destination? At the moment, messing around with the command line (although faster and easier for me anyway) is the only way to find redundant symlinks that may be upsetting ipkg-link or explaining program failures.