Messages

1

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

« on: July 19, 2006, 10:40:41 am »

I can't get WEP to work using Tosa's builtin wireless lan.

Code: [Select]

iface wlan0 inet dhcp
 Â wireless_type wlan-ng
 Â       wireless_mode managed
 Â       wireless_key1 11111111111111111
 Â       wireless_essid MYWORKPLACEI don't recall seeing anything about this in this thread?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=135734\"][{POST_SNAPBACK}][/a][/div]

This format won't work with the wlan-ng driver. Use this instead:

Code: [Select]

       wireless_enc on
       wlan_ng_authtype opensystem
       wlan_ng_key0 aa:aa:aa:aa:aa:aa:aa:aa:aa:aa:aa:aa:aa
The tosa internal usb wlan can only be used wit the wlan-ng driver which support a different syntax.
Did you modified your file with the gpe gui? If yes this won't work, because these gpe doesn't know the wlan-ng syntax.
Gpe needs patches to switch the format if "wireless_type wlan-ng" is selected. I did this a few month ago for opie, but this needs to be redone for gpe.

Please do not blame me or the oz team about the driver. Sharp made the decision and there is no other linux driver available.  
I'm not happy with this driver, but there is no choice.
A long term solution might be to integrate the usb part into the kernel hostap driver, but this needs a lot of work.

Btw. Another point, wireless tools (iwconfig, iwlist,..) aren't fully supported by wlan-ng. You have to use their own tools (wlan-ng-ctl...)

Dirk

2

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

« on: July 19, 2006, 10:24:06 am »

when I flashed to the latest GPE install yesterday, and then yesterday evening did an IPKG upgrade, after rebooting I got an error that the kernel was mismatched to its modules' versions, and there was a long wait inviting me to abandon booting - presumably to reflash.

however, I threw caution to the wind and let it carry on, and everything seems OK still. However, you probably want to ensure that your tosa kernel build version matches the module builds in the feed to avoid this error.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=135722\"][{POST_SNAPBACK}][/a][/div]

right, there is a mismatch between the installed kernel and the modules into the feed.
You can ignore these message or supress it by removing /etc/init.d/checkversion

Dirk

3

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

« on: July 18, 2006, 05:16:06 am »

Is there a way to check if the Z is on the dock instead of external power since this woudl be when to load the g_ether and activate the usb0(also woudl be a good place to kick off unison)?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=135419\"][{POST_SNAPBACK}][/a][/div]

IRC. tosa is the only device which is able to detect the usb connection.
I haven't looked in detail into the udc implementation how the implement automatic activation of usb0.
I'll put this into my todo list.

Dirk

4

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

« on: July 17, 2006, 04:04:11 am »

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

Thanks, looks good as a workaround

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

5

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

« on: July 17, 2006, 03:48:43 am »

Some of the issues observations I have had since I flashed back are:

1.  usb0 stops sending and recieving traffic after a while.  I believe this is still an issue with writing to the cf card at the same time as using the usb bus.  This is a pain in the ass since I like to put my Z on its dock when I am at work and ssh into it, uses synergy or x11vnc on it while I am at my desk.  Is there no way around this issue?  Will I see this same problem if I use a usb hub on the usb host port and plug in a usb network adapter(along with other usb devices like usb cd-rw and usb keyboard) to have network access and being able to uses my cf card, since I do not have access to wifi at my desk(or at work all together but that is a different issue)?

I do not use the usb interface. I haven't heard about such problems on the clamshell devices with 2.6 kernel, because they are using the same drivers.

2.  When I plug the Z into the dock it turns the power on.  This is really not a problem other then I would like to have the g_ether loaded when this happens.  Is this possable?

I think this is possible with the apm scripts. Create a script which is called on resume. This script checks if the device is externally powered, then load g_ether module.

3.  Volumn control in GPE is not working.  I am guessing this is due to the sound not being fully supported in the kernel, but I though I would point it out since I plan to put it on the list of things that need to still be fixed on my website(One of the things I test with new images/kernels)

Sound in the kernel is fully working (at least playback checked). I don't know if GPE uses ALSA or the OSS emulation layer. At least alsamixer can control the volume. I am guessing this problem is somewhere between GPE - OSS emu - ALSA

Dirk

6

6000 - Tosa / 6000 Dismantled.

« on: July 17, 2006, 03:12:31 am »

Can anyone suggested ANYTHING? I checked the keyboard, and the two LCD connectors, and they seem fine.

Sorry to hear about your tosa.
Please re-check the lcd connector and the battery switches.

Dirk

BTW. How did you get the half broken tosa? I'am interessed in such a device to do some measurement in order to optimize the 2.6 kernel.

7

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

« on: July 14, 2006, 06:59:18 am »

I press power button on my Zaurus, and just after screen is turned black, I press power button again. Some times this leads to system hang up.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=135109\"][{POST_SNAPBACK}][/a][/div]

Does the screen is turned on(but no backlight)? Does the green led blinks twice?

I think I have identified a race condition. I'll look into this.

Dirk

8

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

« on: July 14, 2006, 02:47:45 am »

I had wifi (using the ohci_hcd module) working for a while till I ran ipkg upgrade from http://ewi546.ewi.utwente.nl/mirror/www.op...e/3.5.4.1/feed/ since I was that machine had tosa(I was willing to take the risk).  Since the kernel modules are newer it broke a few things, at least it is not working as well as it did before I ran upgrade.  I am reflashing now to start over without running upgrade.

Should I be able to uses packages from that feed?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=135064\"][{POST_SNAPBACK}][/a][/div]

My image is build from the oz354x tree, so the packages should be identical (except zaurusd which has a newer config file).
Can you post your error messages?

Dirk

9

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

« on: July 14, 2006, 02:38:36 am »

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? 

A script as a workaround should work. The best solution is to improve the driver.

Dirk

10

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

« on: July 13, 2006, 02:26:07 am »

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.

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

Right this feature has a bug.
The backlight driver limits the intensity when the battery level is low. There is a bug if batterylevel is around the threshhold.

I had tested kernel 2.6.17 with OPIE image.

System hangs up if it turned off and quickly turned on.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=134817\"][{POST_SNAPBACK}][/a][/div]

Can't reproduce this, can you provide more details?

Dirk

11

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

« on: July 12, 2006, 03:10:11 am »

All Z-- The *(*&&!! package manager gui. Multiple network profiles in network applet.

6000 the network applet needs to work. really. If I have to screw around with manual settings everytime I go for a walk, Im never gonna use this..

Are you talking about the gpe applet?
The gpe network applet can't handle the wlan-ng driver. For Opie I added support a couple of months ago.

Dirk

12

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

« on: July 03, 2006, 05:12:20 pm »

Its been a few months since the last image was posted, has there been any progress that would warrent posting a new alpha image?

I found time to improve the tosa kernel (small changes).
The new Image is online Tosa 2.6 Image

Changes:
- Kernel 2.6.17
- No automatic resume during charging
- Headphone detection works

Dirk

13

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

« on: June 28, 2006, 06:10:03 am »

Hi all.

....

It seems to resume when putting it back on the dock after suspending it while on battery.

This is a known bug. I'll fix this soon.

It also hung on resume after suspending/resuming while on the dock, but I can't seem reproduce it.

I saw this one time, can you provide more details?

The old blue and yellow artifacting is still there (which I seem to remember reading was a bug in X and not the kernel),

This has a low priority, I'll look into this later.

and resume on alarm still doesn't work.

This should be working. I checked this some time ago. Can you provide the dmesg output?

Dirk

14

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

« on: May 08, 2006, 09:09:04 am »

hello,

i only tested the image because of the present "drawing bug" (blue/yellow lines)
of the official oz images for tosa. i was a little bit dissapointed as this bug also
appears in the 2.6 kernel. i think this is what dirk calls "noisy". but it is interesting
that it does not appear in rotated mode!

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

hello malik,

yes the "drawing bug" isn't fixed yet. Sorry I hadn't enough time to look into this.
The touchscreen is noisy, because the lcd disturbs the touchcontroller. Sharps 2.4 solution is a quick fix, but I'am working on a better one.

btw. I put a new snapshot on my website. These images are based on the current 3.5.4.1-rc2 version. The gpe-image starts touch calibration on first startup.
Please note these images are no official openzaurus releases, just development snapshots.

Dirk

15

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

« on: May 03, 2006, 06:24:03 pm »

Any chance someone with oe setup can build and post a test image of the 2.6 kernel?  I would but i dont have a machine to build on at the moment.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

Hey,

I put an actual development snapshot on my website. [a href=\"http://www.do13.de/oz/temp/image/]Image[/url]

This experimental image has some issues:
- The gpe touch calibration on the first startup won't work. So you have to use the keyboad to exit gpe and call ts_calibrate manually
- suspend / resume with loaded ohci-hcd module will crash on suspend
- expansion jacket isn't supported yet
- lot of small issues (keymap need some tweaks, touch is noisy, ...)
- one user reported usb client won't work. I haven't checked this

Dirk