A new beta of the fast kernel is on :externe.net/zaurus/kernel/binaries/beta

If everything is ok it will be released tomorrow. Please flash it and report any potential problem.

To install it, carefully follow the instructions in externe.net/zaurus/kernel, especially if you are using a sharp rom. You **MUST** replace your modules by modules.tar.gz and you **MUST** unpack keyboard.tar.gz. If you don't, the keyboard will not be usable.

What's new: - finer battery report (1% by 1% instead of 100/75/25/0) - faster NWFPE backported from 2.4.30 - usb keyboard AND internal keyboard AND bluetooth keyboard now work fine all at the same time, including all the keys (keypad etc.) without requiring any external binary. F1 to F12 are mapped to the Zaurus buttons (ex: press on f1 for the calendar, F6 for the userdef key, f7 for light etc)

This hopefully marks the end of keyboard problems. keyboard.tar.gz will be improved in the future to make shift+fn give 8 bit chars (ex: shift+fn+e could give é (e acute) while shift+numlock would give control codes (ex: ctrl-c, ctrl-a)

Many thanks to nilch (http://www.oesf.org/forums/index.php?showuser=1034) whose generous donation of a USB mini A/A cable made the finer test/fixes of the USB keyboard possible. [the best way to have some specific hardware problem fixed is to get me the same hardware :-)]

The bugs are due to the guylhem "rom" (distribution). if you install the kernel on the 0.9, you will still experience them. On a sharp rom no problem however, but you'll miss the many nifty features...

The bugs are due to the guylhem "rom" (distribution). if you install the kernel on the 0.9, you will still experience them. On a sharp rom no problem however, but you'll miss the many nifty features...

ok, so if I get you, this is not the guylhem rom, but the "fast kernel" one instead.

I wasn't sure if you had dropped the fast kernel thing in lieu of having the guylhem rom instead.

While you're at it, what's the differences between the ffpe vs no-ffpe mean to the user?

This is my initial experience loading and running the new kernel under the Guylhem 0.9 distribution. The process described in the README worked well. The method used to update the keyboard drivers differs from the document, but you have to know about these things when you're a king ..er.. beta tester.

The system came up with no problem, or indeed any change that I could see watching the boot messages scroll by. The internal keyboard works, though I haven't exhaustively tested it. (I don't have a supported external keyboard. Will IRK + Think Outside work some time?) The WiFi came up with no difficulty using the configuration from before the kernel upgrade.

hrw:subjectively... I haven't done any formal tests, but the fwpe patch does seem a bit faster. It would definitelly be worth testing in OE--especially since oe stuff should take better advantage of it.

---------------------- If you are using Guylhem ROM, you are done. Else, you need to reset the SL6000 using the reset button on the back. Press and hold the OK button while turn on the zaurus, then select "3. Format" in the menu in order to format the system, then yes (Y).

The zaurus will then reboot on the new kernel.

- If you are not using Guylhem ROM, you must restore your backup---------------------

Essentially, if you're using the Sharp ROM:

reset the SL6000 using the reset button on the back. Press and hold the OK button while turn on the zaurus, then select "3. Format" in the menu in order to format the system, then yes (Y). The zaurus will then reboot on the new kernel.

Restore from your backup.

---------------------

... backup from which step? What kind of backup? "Format" - what's it formatting? The main memory ... ?

should be keysymbols.tbl (either that or the filename needs to change)

-- after rebooting --

INIT: version 2.78 bootingdepmod: Can't open /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep for writingmodprobe: Can't open dependencies file /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep (No such file or directory)mount: Mounting usbdevfs on /proc/bus/usb failed: No such file or directoryinsmod: vtty: no module by that name found

-- observation --

sd card not recognizedkeys all messed up <= fixed, when extracting from /