Hentges 3.5.4.1 For Collie

[kellyharding]

Seem to be having some odd problems with my Socket LP CF wifi card using this rom and OPIE.

Seems to work fine under GPE. But I've found GPE is a bit too unstable for me, the console and packagemanager for example seem to die randomly on me.

Anyway, back to the wifi.

getting:

Code: [Select]

eth0: Error -5 writing Tx descriptor to BAP
(repeats a number of times)
eth0: New Link Status: Disconnected (0002)
I don't get this behaviour when I've flashed with the GPE image, are there different kernel modules or something like that with the OPIE image?

Kelly

[Hrw]

http://openzaurus.org/wordpress/2006/04/12...with-wifi-card/

[telemetric_au]

i really like the download progress read outs during package management ! is there anyway that can happen in standard 3.5.4 ??

[telemetric_au]

i really like the download progress read outs during package management ! is there anyway that can happen in standard 3.5.4 ??
[div align=\"right\"][a href=\"index.php?act=findpost&pid=123887\"][{POST_SNAPBACK}][/a][/div]

i found that the "apkg" package when the "troubleshooting output" option is selected  does this, as may the standard pkg manager when in the "information level" selection but im finding apkg work better.

[kellyharding]

http://openzaurus.org/wordpress/2006/04/12...with-wifi-card/
[div align=\"right\"][a href=\"index.php?act=findpost&pid=123884\"][{POST_SNAPBACK}][/a][/div]

Have posted relelvent information to bugs.openembedded.org

Hope it proves helpful, if you need any more information on it just ask.

Kelly

[Snappy]

Flashed happily and rebooted happily ... and am now using the new hentges rom happily!

Thanks CoreDump!

...

Still trying to figure out how to get the Belkin ir keyboard to work ...

[Storm]

Just finished flashing. Excellent job, Coredump!

Noticed something strange though. I installed bash, and changed root's prompt to /bin/bash. When I log in, it gives me the command prompt normally. However, after the first command completes (e.g. ls -l or anything else), the prompt does not return. Control-C has no effect, though ssh commands (like ~.) do work.

I had the same configuration on 3.5.4, and it worked fine.

Ideas?
--Storm

[Storm]

After some testing/use of 3.5.4.1alpha2, I am seeing some hard lockups on my Zaurus that didn't happen in 3.5.4rc. It appears to happen whenever I have it on for more than a minute. I reflashed it last night, and after configuring it, was reading an e-book. When I tried to suspend (with the power switch), it was locked. No response from the touchscreen or autoscrolling. I reset (flipping battery cover switch) it and put it on the cradle to charge overnight. When I got up this morning and pulled it off the cradle, again it was locked up. I couldn't tap the icons on the desktop, nothing. I reset it again, and left it sitting while I packed up my laptop, and in that short amount of time, It locked hard again.

I reset it, and as soon as it came up, I suspended it, and thats where I am now. One other thing I noticed is that whenever it boots, there is a message, "stty: standard input: bad file descriptor" or something to that effect. Possibly unrelated, but I figured I would throw it out there.

Has anyone else seen this type of behavior?

Thanks.
--Storm

[arniel]

After some testing/use of 3.5.4.1alpha2, I am seeing some hard lockups on my Zaurus that didn't happen in 3.5.4rc. It appears to happen whenever I have it on for more than a minute. I reflashed it last night, and after configuring it, was reading an e-book. When I tried to suspend (with the power switch), it was locked. No response from the touchscreen or autoscrolling. I reset (flipping battery cover switch) it and put it on the cradle to charge overnight. When I got up this morning and pulled it off the cradle, again it was locked up. I couldn't tap the icons on the desktop, nothing. I reset it again, and left it sitting while I packed up my laptop, and in that short amount of time, It locked hard again.

I reset it, and as soon as it came up, I suspended it, and thats where I am now. One other thing I noticed is that whenever it boots, there is a message, "stty: bad file descriptor" or something to that effect. Possibly unrelated, but I figured I would throw it out there.

Has anyone else seen this type of behavior?

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

Yup, I've noticed both problems on my SL5500.  The suspend issue seems to occur every other suspension, I think.
Also, after flashing the ROM and installing cardfs, I had to do an ipkg-link to get most of the packages on SD working.
lastly, have not had any luck getting my wired ethernet PCMCIA card working, even after installing axnet package and checking the conf file.  Although it's detecred as a Linksys PCM100 v3 (correct), the taskbar icon to eject lists it as a completely different device and the axnet library remains unused.
Apart from that, it feels excellent.  Indeed the responsiveness is much improved over 3.5.3.

[CoreDump]

Re: Lockups

I'm using my Collie daily with the exact same image as found in do_not_use and I can't reproduce any lockups so far.

[Storm]

Re: Lockups

I'm using my Collie daily with the exact same image as found in do_not_use and I can't reproduce any lockups so far.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=124383\"][{POST_SNAPBACK}][/a][/div]

Hmmm...Lest I missed something important, let me run through my steps.

My hardware config is an SL-5500 with a 1GB Sandisk SD card. I flashed from a 32MB Sandisk CF. I untarred hentges-opie-image-collie_T1-RC4.tar.gz onto the CF card, verified the md5sum of initrd.bin,  zImage-collie-64-0-20060409201626.bin (renamed to zImage) and cardfs-opie-collie-openzaurus_oz3.5.4.1-alpha2-opie1.2.1-T1-RC4.bin. I also copied the cardfs image to the SD card.

I flashed the unit as I always have (C-D and reset, when the lights went out after about 3 minutes, reset and replaced the battery cover). I pulled the CF card and let it boot up. Going through the prompts, I set up cardfs on the SD card (which remained inserted the entire time), and it came up to opie.

That is all I did. I haven't even tried to install any additional software. I can provide specific answers to the questions during the install if that helps. I was wondering if it was my SD card, but it is less than 8 months old, and since arniel is having the same issues, unless it was a bad run of them, I tend to doubt it.

I thought it was just a suspend issue myself, until I found that it had locked up on the cradle last night. By default, the Zaurus is set to never suspend on power. *shrug*

Do you see any step I might have missed? I may try reflashing with the gpe image to see if I get the same symptoms.

--Storm

[CoreDump]

Well, I don't see anything wrong there. Did you install any additional software beside what's inside the base install + cardfs?

Could you check if these lockups happen if you use the Opie menu to suspend and not the Cancel button?

BTW: The "bad filedescriptor" massage is harmless and is fixed in recent altboot versions.

I'll pred an upgrade feed in the next few days which will pull in all changed to upgrade the OZ version from 3.5.4.1-alpha* to 3.5.4.1-rc1, I just hope Collies' on-board flash won't fill up like its known to do...

[herbieach]

Hey Coredump,

Really appreciate your efforts on this ROM release.

I just reflashed again to get a clean system (just like Storm above) and then got my USB networking up. Did a suspend on the cradle and it locked up hard.

One thing I noticed in /etc/ipkg.conf is that one of the machine specific feeds pointed to the akita directory (can't remember which one but I changed it to collie as it should be). Not sure if this could have had a potential impact on when these images were built.

Also I take it the opie feed is not included in the config file to make it generic and therefore needs to be added manually.

[Storm]

Well, I don't see anything wrong there. Did you install any additional software beside what's inside the base install + cardfs?

No. It is the base flash. I did it a total of 3 times over this weekend, and this last time, after I noticed the lockup issue, I did not install anything additional.

Could you check if these lockups happen if you use the Opie menu to suspend and not the Cancel button?

They do not. Its behaving like the early days of OZ3.5.3.

BTW: The "bad filedescriptor" massage is harmless and is fixed in recent altboot versions.

I suspected this, but I figured it might be another piece of the puzzle, so I reported it just in case.

I'll pred an upgrade feed in the next few days which will pull in all changed to upgrade the OZ version from 3.5.4.1-alpha* to 3.5.4.1-rc1, I just hope Collies' on-board flash won't fill up like its known to do...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=124411\"][{POST_SNAPBACK}][/a][/div]

Could the kernel have somehow gotten rolled back to an early 3.5.3 one? This appears to be (now that you pointed it out) the same suspend problem that we were having before.

I'm going to hold off on installing any more software until we pin this down. BTW, is there any reason why installing bash and changing root's shell to it would cause it to hang after the first command? It didn't do this in 3.5.4rc.

--Storm

[Snappy]

Now that you mentioned, I'm also getting the lockups.  ... It would hang when I try to shut it down. Screen stays on with backlight but system is hanged. hmmm

I also get the "stty: standard input: bad file descriptor" error