Help - Search - Members - Calendar
Full Version: Fast Kernel - 20050521
OESF Forums > Distros, Development, and Model Specific Forums > Model Specific Forums > 6000 - Tosa
guylhem
Hello

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 :-)]

Guylhem
ken
QUOTE(guylhem @ May 20 2005, 10:10 AM)
Hello

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

*


have some of the bugs from the previous versions been resolved? ie, unable to install apps other than main memory, etc
guylhem
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...
ken
QUOTE(guylhem @ May 20 2005, 11:55 AM)
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?
hbo
This is a documentation bug report. In the instructions at http://www.externe.net/zaurus/kernel/READM...mk7-pxa3-common , at step six, we have:

CODE
- To flash a kernel, put these files at the root of the CF card (or SD card) :

    scp consolescroll updater.sh root@zaurus_ip:/mnt/cf
    scp zImage root@zaurus_ip:/mnt/cf/updater.sh


I believe the last line should be

CODE
    scp zImage root@zaurus_ip:/mnt/cf/zImage.bin
hbo
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.

That's all I had time for tonight. More tomorrow.
Hrw
can you publish NWFPE patch? Does it give something noticable in speed?
BarryW
Okay, this may seem kinda dumb, but how can you tell if it's using the new kernel or not??
adf
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.
ken
Guylhem:

This step bothers me a little. Please elaborate ...

---------------------
- 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 ... ?

Thanks
guylhem
On sharp rom, /home should be formatted after a kernel update to make clean place for the new modules. You can skip this step if you know what to do.

Hrw, this is simply the 2.4.30 kernel nwfpe being backported. all the src will be published as usual
ken
QUOTE(guylhem @ May 21 2005, 04:26 PM)
On sharp rom, /home should be formatted after a kernel update to make clean place for the new modules. You can skip this step if you know what to do.

*


So selecting "format" will *only* remove stuff in /home?

Also, when you said restore ... can you provide more details as to where the restore info is from and how one does it?

I don't have a clue on this -- thanks!
guylhem
use the backup/restore application on sharp rom
ken
QUOTE(guylhem @ May 22 2005, 04:06 AM)
use the backup/restore application on sharp rom
*


ah. I was overthinking this. ok
ken
note: scp not available

note: wget http://externe.net/zaurus/flash/kernel/keyboard/keysyms.tbl incorrect.

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


-- after rebooting --

INIT: version 2.78 booting
depmod: Can't open /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep for writing
modprobe: 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 directory
insmod: vtty: no module by that name found

-- observation --

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

my renamed nand backup disappeared. *sigh*
hbo
QUOTE(ken @ May 22 2005, 05:15 PM)
note: scp not available

note: wget http://externe.net/zaurus/flash/kernel/keyboard/keysyms.tbl incorrect.

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


No, for the beta, you needed to unpack keyboard.tar.gz (available at the same place the beta kernel was) in the root directory. (The location wasn't clear in the instructions, but looking at the tarball contents showed the way.)

QUOTE
-- after rebooting --

lots of problems


It sounds like you didn't correctly unpack the modules or the keyboard stuff, either one.

QUOTE
my renamed nand backup disappeared.  *sigh*
*


This is not good. NAND restore is probably the only way out at this point.
ken
QUOTE(hbo @ May 22 2005, 04:32 PM)
No, for the beta, you needed to unpack keyboard.tar.gz (available at the same place the beta kernel was) in the root directory. (The location wasn't clear in the instructions, but looking at the tarball contents showed the way.)


bleh, my error I guess. I used the files from the beta, but followed the instructions that was from the fast-kernel (as per his original message)

note: this is using the Sharp ROM

ok, found the source of the problems. the keyboard and modules files needs to be extracted from / rather than the directories as listed in the instructions.

I think after that is when things go awry. Mostly missing things.

I should note that I had to put the "find ..." and "for ..." instructions in a .sh file, otherwise I wouldn't be able to type certain characters.

----- during boot -----

depmod: Can't open /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep for writing
modprobe: 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 directory
insmod: vtty: no module by that name found
INIT: Entering runlevel: 5

----- after boot -----
observation: sd card not recognized.

of course, this meant that all the programs I installed was not being found.

booting into console mode, and trying to manually mount /mnt/card resulted in:

modprobe: modprobe: Can't open dependencies file /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep (No such file or directory) (repeats 6 times)
mount: Mounting /dev/mmcda1 on /mnt/card failed: No such device or address

The entry in /etc/fstab showed:

/dev/mmcda1 /mnt/card auto noauto, owner 0 0

(everything points to the module not being found)

I tried to copy everything from modules.rom to modules, chmod 777 to modules.dep, but still the same results. oh well, nothing else I can try. Hope this info helps
guylhem
Tried depmod -ae ?
ken
QUOTE(guylhem @ May 24 2005, 09:11 AM)
Tried depmod -ae  ?
*


#depmod -ae
depmod: Can't open /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep for writing

(I would have assumed this because of the mv modules modules.rom instruction)

#mount -n -o remount,rw /
#copy -R modules.rom modules
#depmod -ae (no error messages)
#mount /mnt/card
modprobe: modprobe: Can't locate modules block-major-60 (repeats 6 times)
mount: Mounting /dev/mmcda1 on /mnt/card failed: No such device or address

-----

A point of interest. I'm not sure what I did, but I do know I didn't do the 'format' and 'restore' options. I mucked around, and at some point when I rebooted, the SD card was recognized. No clue.
malik
hello,

i have the same problems like ken and a mysterious one: the "f" key turns the
light on and off? i guess this is a bad joke:-) other keys seem to be okay.

i avoided the last step in the instructions: format/backup. backuping will overwrite
/home/root and therefore the settings of the find-for commands or not?

malik
gab74
I've the same problems like ken; i'm using sharp roms...

I follow the README by guylhem...

Can't open /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep for writing

Infact /lib/modules doesent exist !

Is "mv modules modules.rom" instruction for Sharp Rom too ?

#depmod -ae
#depmod: Can't open /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep for writing

Any helps for installing new kernel on Sharp Rom ?
xjqian
Didn't know a new version was up last october. Anyboy tried this yet or everybody lost interest in the fast kernel?

Version 20051020
- definitely fixed remaining keyboard issues with a new compatibility
mode
- boot in only 1 minute : removed DMESG.
Most of the remaining delay is due to jffs2 checks
- added other axim keyboard fixes
ken
QUOTE(xjqian @ Feb 3 2006, 01:05 AM)
Didn't know a new version was up last october. Anyboy tried this yet or everybody lost interest in the fast kernel?


I'm awaiting his return from his busy schedule and side interests.
robyinno
I'm interested if in pdaxrom...

Roberto

QUOTE(xjqian @ Feb 3 2006, 12:05 PM)
Didn't know a new version was up last october. Anyboy tried this yet or everybody lost interest in the fast kernel?

Version 20051020
- definitely fixed remaining keyboard issues with a new compatibility
  mode
- boot in only 1 minute : removed DMESG.
  Most of the remaining delay is due to jffs2 checks
- added other axim keyboard fixes
*
DrWowe
QUOTE(xjqian @ Feb 3 2006, 05:05 AM)
Didn't know a new version was up last october. Anyboy tried this yet or everybody lost interest in the fast kernel?


I've been using the October version for a while. It works great, although I changed a few config options to revert the new keyboard stuff, and recompiled it myself.
adf
it would be the logical choice for your project. are you also planning to include the fast sdl stuff?
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.