Cacko Kernel For Sl-5500/5000d Options

[technojunkie]

I left a file manager on before I press the cancel(on/off) buton to suspend zaurus, and after I resumed, it seems that the sd card is not properly mounted.  There seem to be fewer folders and they are mostly empty.  Anyway to fix that?

I have the same problem... It's kind of annoying that I have to reboot my z every time I suspend it. I remember reading somewhere that on another /home on sd approach, they had to tweak something in the suspend/resume scripts to make the SD mount properly. I'm looking for it now, as I have reflashed to cacko.

** edit **
I didn't find the answer, I must have seen it on devnet. But I did go buy a new SD card and that solved the problem. my lexar must have been off on the timing and couldn't resume properly.

[dougeeebear]

One solution to the annoying blink problem is to reboot your Z, it will start with the LED steady. It's not so complex. Maybe you guys can have a try. If I have time, I may look at the battery part driver for solution.

Just wondered if you have had time yet.

Thanks, Doug

[earthcoder]

i get to a screen at start that says -

Give root password for maintance

so i press OK

then type passwd
then type a 8 letter password and confirm and it says - passwd[34]: an error occurred updating the password file

anyone got any clue what i should do.. except from throw the pda out the window cause of all the trouble i have with it..

[caunt]

Hi again earthcoder,
I tried to answer you under your "Help" post, but thought I'd mention that if you still want to "throw the pda", I wouldn't mind if you threw it my way instead of out the window I'll even pay shipping!

(But I'm sure you'll get it running)

[tsuribaka]

Is it normal for System Info to show "Total Memory: 46280" on a 5500?

"free" also says Mem: 46280.

Shouldn't it be 64M?

(I am using the 64M version of the rom)

[derekwei77]

Hey Maslovsky,

First thanks for the updated kernel image for SL-5500.
This is great work.

I'm trying to write a kernel module for my Zaurus 5500 to
support wireless ad hoc networking between Zs. The kernel
module needs support of netfilter. So I have three questions
about Cacko kernel zImage-sl5500-32-30:1. Has zImage-sl5500-32-30
already supported netfilter? 2. Can I get the kernel source
or header files? 3. Can you recommend cross-compile toolchains compatible
with the kernel source? Thanks a lot,

Derek

[dougeeebear]

I'm trying to write a kernel module for my Zaurus 5500 to
support wireless ad hoc networking between Zs. The kernel
module needs support of netfilter. So I have three questions
about Cacko kernel zImage-sl5500-32-30:1. Has zImage-sl5500-32-30

Since you are working on this kernel, do you suppose you could figure out the problem with the flashing battery light?
I only have this problem with the kernel installed.

I have SL-5500 with standard sharp rom 3.13.

Any help is appreciated (no pressure).

Thanks, Doug

[maslovsky]

Hey Maslovsky,

First thanks for the updated kernel image for SL-5500.
This is great work.

I'm trying to write a kernel module for my Zaurus 5500 to
support wireless ad hoc networking between Zs. The kernel
module needs support of netfilter. So I have three questions
about Cacko kernel zImage-sl5500-32-30:1. Has zImage-sl5500-32-30
already supported netfilter? 2. Can I get the kernel source
or header files? 3. Can you recommend cross-compile toolchains compatible
with the kernel source? Thanks a lot,

Derek

No, this kernel doesn't have netfilter enabled.
Kernel source is available at ZUG downloads section as well as dveelopment tools and development HOWTOS

[revdjenk]

Hey everyone, anyone

I have been using the new Caclko 64-0 kernel with my 5500 and enjoying it, esp. the battery app.
I installed the 1.9.1.6 KDE-PIM and whoops!
I first noticed that I no longer had any ipks listed in the uninstall area. and any later installed programs never had their icons change (or show up as installed or uninstallable.)

KDE-PIM would not start either. So I re-booted.

Still had the no-show in the install-uninstall lists....so I decided to flash Cacko again.

And now, after reset, I am getting same message as earthcoder reported. along with saying that I can do normal start with Control-D.
Well, all the key combinations in the world just bring me back to the prompt; as do any further resets.

I have reflashed several more times, but the same result upon restart.

Any suggestions?

[revdjenk]

Well...

I just re-formatted my SD and reflashed.

Everything back to normal! Luckily I had recently backed up!

[revdjenk]

Just so you don't misunderstand, everything is working, the third time around, because I have NOT installed KDEPIM 1.9.16!

[craigtyson]

The Files arnt there any more. Were they droped dou to compatibility problems? Or are they still available. Im looking to get a liitle bit more out of my tkc ROM v1 on my 5500

Cheers

Craig.

[craigtyson]

Found em. The files are under kernel source not the roms section as listed.
Installed and working fine on a tkc v1 30/32 with kTrove to put the apps onto SD so I can keep the card VFAT. As advertised write access to the cards is much quicker.

Craig

[technojunkie]

Well After many months of using the 64-0 kernel(zImage) with what I thought was the correct filesystem, I have had to reflash to get my WiFi card working. This time I know I have the files correct as I downloaded them in the same zip file, and I am now experiencing the infamous blinking battery light issue.

I think based off of my experience it is pretty safe to say that there is a config/version/other problem somewhere in the file structure that is causing the blinking rather than an issue with the kernel itself.

I am relieved though, that after a month of "bangin o' the head" I finally have WiFi.

As soon as I have my linux box back up and running I will dig into this ROM as deeply as I can and try to find any clues as to what causes this.

(OR if my wife lets me I may just upgrade to the new SL-C1000 )

[dougeeebear]

and I am now experiencing the infamous blinking battery light issue. 

I guess this issue is now dead in the water, with all the focus on the newer cacko updates going on.
I was hoping it might get fixed.
Oh, well...