Messages

1

6000 - Tosa / 2.6.x Kernel?

« on: July 31, 2006, 11:06:41 pm »

I've been seeing sporadic mentions of 2.6.x kernels in development for the 6000 (Tosa).

Can anyone comment on how close we are to having a stable *modern* kernel?

Thanks,
Randall
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

Check out these two threads...
[a href=\"https://www.oesf.org/forums/index.php?showtopic=18471&st=105]https://www.oesf.org/forums/index.php?showtopic=18471&st=105[/url]
and
https://www.oesf.org/forums/index.php?showtopic=20632&st=15

You'll find images in the first one.  Download, flash, and see for yourself!  

I'm running the latest test image on my tosa and it's rockin'.  I wouldn't say it's release-ready, but definitely coming along.  But like I said, see for yourself.

2

Angstrom & OpenZaurus / 3.5.4.1 Kernel 2.6 Testing On Tosa/6000

« on: July 21, 2006, 08:25:46 pm »

I need help on describing the alarm's when suspended. 

What application is the alarms from?
Is this still and issue in the 2.6 kernel?

I do not have this problem since I do not have alarms on my Z so I am not the best person to descibe it but I can put the bug in if I can get more information.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136026\"][{POST_SNAPBACK}][/a][/div]

I'm assuming you're talking about alarms not resuming the unit when they occur while the unit is suspended.  I'm pretty sure that's fixed unless there's some other issue I don't know about.  In the other thread, dirk siad it's fixed, and they work for me (I just tested it) on the latest image.

EDIT: By "latest image" I really mean, "latest GPE image."  I don't know about Opie.

3

Angstrom & OpenZaurus / Fixes For 3.5.4 / Tosa (6000 Models)

« on: July 17, 2006, 08:07:00 pm »

As a side note: are the names "ohci_hcd" and "ohci-hcd" interchangeable?  Doing a "modprobe -l | grep ohci" shows "ohci-hcd" but when it's loaded, lsmod shows it as "ohci_hcd".  Both seem to work when loading/unloading it via modprobe and rmmod.  What's up with that?

This thread explains the naming translation: Name of kernel modules
[div align=\"right\"][a href=\"index.php?act=findpost&pid=135356\"][{POST_SNAPBACK}][/a][/div]

Ah, that makes perfect sense.  Thanks!

4

Angstrom & OpenZaurus / Fixes For 3.5.4 / Tosa (6000 Models)

« on: July 15, 2006, 05:05:46 pm »

Alrighty, here's the script I whipped up to unload/load ohci on suspend/resume.

Code: [Select]

#!/bin/sh

# Unloads/loads the ohci driver on suspend/resume due to
# it's lack of power management support.  This is a temporary
# hack until the ohci driver is improved.

case "$1" in
        suspend)
                rm /var/run/ohci-was-loaded
                if [ "`/sbin/lsmod | grep ohci_hcd`" != "" ]; then
                        rmmod ohci_hcd
                        echo true > /var/run/ohci-was-loaded
                fi
               ;;
        resume)
                if [ "`cat /var/run/ohci-was-loaded`" = "true" ]; then
                        modprobe ohci_hcd
                        rm /var/run/ohci-was-loaded
                fi
               ;;
esac
I placed that at /etc/apm/scripts.d/ohci-apm-hack and simlinked it to /etc/apm/suspend.d/06ohci-apm-hack (so it will run right after 05ifupdown) and to /etc/apm/resume.d/31ohci-apm-hack (again, so it will run right after 30fiupdown).  I figured it'd be a good idea to run it *after* ifupdown because if wlan is up, ohci will be loaded.   Since ifupdown will unload/load modules according to the rmmod/modprobe commands in the post-down/pre-up lines of /etc/network/interfaces, it will handle the unloading/loading of ohci.  So this script only really does anything if ohci is loaded, but the wlan interface isn't considered up by ifupdown.  

Anyway, this does the trick for me.  While I highly doubt anyone's tosa will burst into flames when this runs, I warn: Use at own risk.    

As a side note: are the names "ohci_hcd" and "ohci-hcd" interchangeable?  Doing a "modprobe -l | grep ohci" shows "ohci-hcd" but when it's loaded, lsmod shows it as "ohci_hcd".  Both seem to work when loading/unloading it via modprobe and rmmod.  What's up with that?

5

Angstrom & OpenZaurus / Fixes For 3.5.4 / Tosa (6000 Models)

« on: July 13, 2006, 07:37:39 pm »

Thanks, dirk.  I'll try this when I get home.  Would I be correct in assuming I can add a line to my apm scripts to unload/load the ohci driver on suspend/resume as a workaround, or would it be more involved than that?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=135053\"][{POST_SNAPBACK}][/a][/div]

That should solve about 90% of the suspend/resume issues
[div align=\"right\"][a href=\"index.php?act=findpost&pid=135067\"][{POST_SNAPBACK}][/a][/div]

dirk: My WiFi is up and running now.    Thanks.

koen:    Good to know.  I took a look at the apm scripts earlier, but just at a glance.  I'll dig into it next chance I get.  Is there a good reason why nobody has come up with a workaround like this already?  Is it just that nobody has cared enough to try, or is it more difficult that I think it is?  I'll be glad to give it a shot, and if I come up with anything that doesn't suck too bad, I'll share.  

6

Angstrom & OpenZaurus / Fixes For 3.5.4 / Tosa (6000 Models)

« on: July 13, 2006, 03:56:48 pm »

Hmm, I tried commenting those lines out on my unit, but on "ifup wlan0" I get:
wlanctl-ng: No shcuh device
Failed to enable the device, exitcode=1 .
run-parts: /etc/network/if-pre-up.d/wlan-ng exited with return code 1: Success

Upon inspection of /proc/modules, the prism2_usb, p80211, and usbcore modules are all loaded, but there's no wlan0 in the output of ifconfig or /dev/.

Am I missing something? (A module?  A brain?     )

You need to load the ohci driver. modprobe ohci-hcd should do the trick
There is a reason why this isn't loaded automatically: The ohci driver lacks powermanagement. With loaded ohci module the device will crash on suspend. So you need to unload the module before suspend.

Thanks, dirk.  I'll try this when I get home.  Would I be correct in assuming I can add a line to my apm scripts to unload/load the ohci driver on suspend/resume as a workaround, or would it be more involved than that?

7

Angstrom & OpenZaurus / Fixes For 3.5.4 / Tosa (6000 Models)

« on: July 12, 2006, 10:14:53 pm »

comment out lines with 'usbctl' in /etc/network/interfaces to get wifi working[div align=\"right\"][a href=\"index.php?act=findpost&pid=134823\"][{POST_SNAPBACK}][/a][/div]

Hmm, I tried commenting those lines out on my unit, but on "ifup wlan0" I get:
wlanctl-ng: No shcuh device
Failed to enable the device, exitcode=1 .
run-parts: /etc/network/if-pre-up.d/wlan-ng exited with return code 1: Success

Upon inspection of /proc/modules, the prism2_usb, p80211, and usbcore modules are all loaded, but there's no wlan0 in the output of ifconfig or /dev/.

Am I missing something? (A module?  A brain?     )

It is good to see that the backlight issue is something that can be explained.  It is kinda cool to have it do that so that i know i need to charge or turn down the brightness of the screen.  Now the question is if this is a feature or a bug.[div align=\"right\"][a href=\"index.php?act=findpost&pid=134904\"][{POST_SNAPBACK}][/a][/div]

I don't know about "bug."  I suppose "feature behaving badly" would be apt. :-P

8

Angstrom & OpenZaurus / Fixes For 3.5.4 / Tosa (6000 Models)

« on: July 02, 2006, 08:05:35 pm »

Thanks koen, duly noted.

dirk, I loaded the 2.6 image back up.  

You're correct about the alarms: testing it this time works just fine.  The problem must have been between the keyboard and chair last time.  :-P Somewhat relatedly, I noticed that the system date and time don't survive a reboot (resets to about 4:48AM, May 8th, 2006 every time), which may have been what threw my test of the alarm off before.   (At least that's my excuse.)
I've spent some time trying to reproduce the hang on suspend/resume while on the dock with no luck.  All I remember doing was setting it in the dock, suspending it, resuming it, then it hangs part way into the resume (the screen was kind of half-drawn, much like what it looks like part way through rotating the screen).  I've tried to reproduce it with all sorts of combinations of things running/not running, SD card in/out, and with varied lengths of time spent in suspend.  Still no love.  If I can get it to do it again, I'll post anything new here.

BTW, I want to thank all the folks working on this (and other Zaurus related stuff too), I greatly appreciate your volunteered time and effort.  So Z devs: Hoorah!

9

Angstrom & OpenZaurus / Fixes For 3.5.4 / Tosa (6000 Models)

« on: June 29, 2006, 11:04:35 pm »

dirk, I had to take it out of town with me to use for IM/email since the time I tested the 2.6 image and I flashed back to the latest OZ release.  I'll load up the 2.6 image again this weekend and see if I can put together something helpful.  

dirk and/or hrw: Is there a bugtracker around for the 2.6 image testers can consult/post to?  I'd hate to clutter up this thread with stuff that's redundant/already fixed/etc'.

10

Angstrom & OpenZaurus / Fixes For 3.5.4 / Tosa (6000 Models)

« on: June 25, 2006, 09:49:31 pm »

Hi all.

I gave the 2.6 image a go today, and I must say, very nice.

The increase in performance is stunning to say the least.  It feels nearly like a new machine.  Applications seem to load and run much more quickly than OZ 3.4.5.  Screen rotation also takes far less time.  I also like the added granularity in the back light brightness.

I may be missing something, but suspend and resume is worse with this image than the latest OZ release.  It seems to resume when putting it back on the dock after suspending it while on battery.  It also hung on resume after suspending/resuming while on the dock, but I can't seem reproduce it.

The old blue and yellow artifacting is still there (which I seem to remember reading was a bug in X and not the kernel), and resume on alarm still doesn't work.

Over all, the 2.6 image isn't ready for day to day use (for me anyway) but very, very promising.


Anyway, just my $0.02.  

11

Angstrom & OpenZaurus / Fixes For 3.5.4 / Tosa (6000 Models)

« on: April 26, 2006, 08:35:34 pm »

vorondil28: Dirk Opfer is Tosa/2.6 maintainer and iirc he know about that thread.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

Ah, I gotcha.  Good to know.  So he's the guy in charge of this ([a href=\"http://www.do13.de/openzaurus/]http://www.do13.de/openzaurus/[/url]) page, right?

12

Angstrom & OpenZaurus / Fixes For 3.5.4 / Tosa (6000 Models)

« on: April 25, 2006, 11:21:30 pm »

Haven't heard anything out of this topic for a while.  What's the status of the bounty?  Any takers?  Nine hundred bucks is a good chunk of change.  

***BUMP***  

13

Angstrom & OpenZaurus / Fixes For 3.5.4 / Tosa (6000 Models)

« on: March 30, 2006, 11:12:23 pm »

Also, it would be very nice if we can have an icon to manage the wifi connection.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=121145\"][{POST_SNAPBACK}][/a][/div]

I most certainly second that.  Of all the things that bug me about OZ/GPE on tosa, it's the management of wifi that frustrates me the most.  Ideally, nobody should have to drop into a terminal for something as common as bringing up/down an interface.  I'd be great to have an icon in the matchbox dock/panel/whatchamacallit that lets you enable/disable, view available networks, connect/disconnect, etc'.  GPE-Aerial seems to be designed to do at least some of this, but it's still a long way from usable (unless I'm doing something wrong).  Is anybody using aerial on any of the other Zaurii?  I don't know if it just needs 6000-specific fixes, or if it's inherently broken.

Anyway, like I said, I'll hop all over a test-release of this stuff and I'll do what I can in the way of bug-hunting.

14

Angstrom & OpenZaurus / Fixes For 3.5.4 / Tosa (6000 Models)

« on: March 30, 2006, 05:01:05 pm »

I guess we need to find out who has teh sl6k that are willing to test and work on the creating the list of issues and making sure they are in bugtrackers they need to be in.  Since I am not awear of a bugtracker for openzaurus do we need a keep the list here with links to the bug in its respective bugtracking system?[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

I've got a 6000L and I'm all for improvements.  I'm a broke student so I don't have much to give in the way of cash (maybe buy a hacker lunch?    ),  but I'd be willing to test things in the name of science.  

The OZ-related bugtrackers are linked to from here:
 [a href=\"http://openzaurus.org/wordpress/links/]http://openzaurus.org/wordpress/links/[/url]

And in case nobody has seen this, this page describes the current state of 2.6 on tosa:
http://www.do13.de/openzaurus/

15

Angstrom & OpenZaurus / 3.5.4 Internal Wifi On 6000?

« on: March 23, 2006, 05:48:42 pm »

There's probably an esay way to add a launcher to the OZ/GPE desktop, but I'll defer to the GPE experts for guidance on how to do that.

I've been wanting to do that for a while but haven't bothered to try it yet.  If nobody posts how to do it, I'll take a crack at it this weekend and post the results.  I've poked around the GPE docs a little but didn't see anything about it.  It might be a matchbox thing though, I'm not sure.

Maybe someone well-versed in GPE can write a little applet that fixes the 6000 Tosa wifi config and interface start/stop issues once and for all. That would be a big plus.

Indeed.  Maybe someone could start a bounty for it.  :-p  I'd certainly drop a few bucks in if it ment having the internal wireless on the 6000L/W's working 100% without having to drop into rxvt.