NEW: CACkO Zaurus Qtopia ROM 1.21 HotFix B

[mcamou]

I wonder if maybe the orange light goes out when the battery is FULLY charged. In previous ROM\'s, it just stayed on as long as the power cord was plugged in. I\'ll have to drain the battery good and see if the orange light stays on longer. Either way, it works fine, and maybe it is just a feature. It will keep my orange light from burning out prematurely.

I do appreciate this ROM and it is great!

That\'s exactly it, the orange light stays on only until the battery is fully charged. That way you know when you can unplug  it (if, like me, you like to \"top it off\" each time you plug it in)

[clofland]

Ok, an update on the USB storage \"issue\":

Every time you reboot, /etc/hotplug/usbd.ftype reverts to containing \"net\" instead of \"storage\"

To make it more confusing, the PC Link application still shows the last state that IT set the file to. So if you reboot, it will THINK you are in storage mode, but only by switching to \"PC Link Setting\" and back to \"Storage\" can you get it to set /etc/hotplug/usbd.ftype back to \"storage.\"

Does anyone know why /etc/hotplug/usbd.ftype goes back to \"net\" every time we reboot? It is a minor problem, so hoping for an easy fix.

ON a side note, I also found that /home/zaurus/Settings/route.conf was set to \"Network\" this morning, instead of USB, even though, again, the \"PC Link\" application said it was set to \"USB I/O\" for PC sync. That seems to be staying put once I fixed it, but just another case of the PC Link app not being in sync with reality.

[maslovsky]

To make it more confusing, the PC Link application still shows the last state that IT set the file to. So if you reboot, it will THINK you are in storage mode, but only by switching to \"PC Link Setting\" and back to \"Storage\" can you get it to set /etc/hotplug/usbd.ftype back to \"storage.\"  

Does anyone know why /etc/hotplug/usbd.ftype goes back to \"net\" every time we reboot? It is a minor problem, so hoping for an easy fix.

I will take a look, though it\'s strange that only some people expirience problems with the Net/Storage settings...

[Stubear]

You need to change the perms on /etc/hotplug/usbd.ftype to something less restrictive than it currently is. Sorry I can\'t remember exactly what it was originally, but setting it to 666 will let everyone write to it (and save the value betweeen boots)

EDIT: You also need to check that /etc/hotplug/usbdstorage.conf has perms of at least 664 - I think that they were set to 644

Stu

[ant]

Can confirm the same NEt/Storage quirks.
BTW I experienced this before with other Roms, I dare to say with all included Sharp\'s stock one.

Stubear is probably right: could be a permissions issue.

Ant

[maslovsky]

You need to change the perms on /etc/hotplug/usbd.ftype to something less restrictive than it currently is. Sorry I can\'t remember exactly what it was originally, but setting it to 666 will let everyone write to it (and save the value betweeen boots)

EDIT: You also need to check that /etc/hotplug/usbdstorage.conf has perms of at least 664 - I think that they were set to 644

Stu

This should have been fixed by the hotfix B, but looks like not it was not nailed down completely...

Try to update permissions manualy:

su
cd /etc/hotplug
chmod 666 usbdstorage.conf
chmod 666 usbd.ftype

[clofland]

Still doesn\'t fix the problem.
I did the above, so that /etc/hotplug/usbd.ftype is -rw-rw-rw- and it still goes back to containing \"net\" after every reboot.

I also tried:

chown zaurus:qpe /etc/hotplug/usbd.ftype

but that did not help either. It always goes back to \"net\" after a reboot.

PC Link is quite able to set it to what it wants, it just won\'t stay that way through a reboot. As if it is being overwritten during a reboot by some script or process in the boot up process. The time stamp on /etc/hotplug/usbd.ftype also indicates that it is being modified during my last reboot (more recently than usbdstorage.conf or route.conf which both have the same stamp, that being when I ran PC Link before the reboot).

On a side note: How much of a donation do I need to make to you to have you take the white \"SHARP\" screen out of your kernel? I really like your kernel (saves me a ton of work rolling my own), but I\'d much rather see the cool penguin and the linux boot up text scroll by. (Would be even cooler without the penguin so we can see all of the text, but I\'ve researched that and it sounded like even more work to try to change that picture to a smaller/nill one.) What do you think? Taking out the SHARP screen is just one \"X\" in the config, it can\'t cost too much?

Now if I had a nice \"diff\" file based on the kernel source from Sharp that I could use to build a kernel just like yours, then I could just re-roll it with my own options too.

Oh, and the ROM is COOL, these are minor irritations I am bringing up. I just love to make it all \"perfect,\" but overall, I am loving it!

[clofland]

FOLLOW UP: FIX for USB reversion problem!

Ok, I think the problem is in /home/etc/rc.d/init.d/usb

If you change it to read like so:

start)
    if [ -x $CONTROL ] ; then
        if [ -s /etc/hotplug/usbdstorage.conf ] ; then USB_DEFAULT=storage;
        fi

        action \"Loading USB modules:\" $CONTROL $USB_DEFAULT

This seems to fix the problem quite nicely. =)
Basically it was setting the USB back to a default at every boot (runlevel change), without checking first to see if we had already chosen what we wanted.

Don\'t give me too much credit. I only found the source of the problem, the actual code to fix it, as simple as it may be, I found in a USB file from another ROM I had been using that didn\'t give me this problem.  I just compared the two to see what was different, and then the problem was obvious.

[maslovsky]

On a side note: How much of a donation do I need to make to you to have you take the white \"SHARP\" screen out of your kernel? I really like your kernel (saves me a ton of work rolling my own), but I\'d much rather see the cool penguin and the linux boot up text scroll by. (Would be even cooler without the penguin so we can see all of the text, but I\'ve researched that and it sounded like even more work to try to change that picture to a smaller/nill one.) What do you think? Taking out the SHARP screen is just one \"X\" in the config, it can\'t cost too much?  

Now if I had a nice \"diff\" file based on the kernel source from Sharp that I could use to build a kernel just like yours, then I could just re-roll it with my own options too.

I left Sharp boot logo intentionaly - I personaly don\'t see any use in the scrolling boot messages other than \"coolness\"   I would have gotten rig of the init message too if I could, but I did not dig into kernel source too deep to figure out how.

Yes, removing the logo is easy, having ALL messages show up in console is easy too. Replacing or removing default penguin is doable but not as trivial as the other two options.

Anyway, I can build a kernal without Sharp logo for you. What Zaurus model do you have?

If you want to donate - it\'s up to you how much   There is a paypal link on my Zaurus page http://my-zaurus.narod.ru

[maslovsky]

FOLLOW UP: FIX for USB reversion problem!

Ok, I think the problem is in /home/etc/rc.d/init.d/usb

If you change it to read like so:

start)
    if [ -x $CONTROL ] ; then
        if [ -s /etc/hotplug/usbdstorage.conf ] ; then USB_DEFAULT=storage;  
        fi

        action \"Loading USB modules:\" $CONTROL $USB_DEFAULT

This seems to fix the problem quite nicely. =)
Basically it was setting the USB back to a default at every boot (runlevel change), without checking first to see if we had already chosen what we wanted.

Don\'t give me too much credit. I only found the source of the problem, the actual code to fix it, as simple as it may be, I found in a USB file from another ROM I had been using that didn\'t give me this problem.  I just compared the two to see what was different, and then the problem was obvious.

This is rather strange because the script is from the Sharp default root filesystem, I havn\'t changed it.  Anyway, thanks for the solution, I\'ll make sure it gets into the next hotfix (whenever it\'s out)

[clofland]

I left Sharp boot logo intentionaly - I personaly don\'t see any use in the scrolling boot messages other than \"coolness\"   I would have gotten rig of the init message too if I could, but I did not dig into kernel source too deep to figure out how.

Yes, removing the logo is easy, having ALL messages show up in console is easy too. Replacing or removing default penguin is doable but not as trivial as the other two options.

Anyway, I can build a kernal without Sharp logo for you. What Zaurus model do you have?

Well, \"coolness\" is a big part of the Z to me.

I have a 760, and if you want to do it GREAT! But don\'t waist too much time on it, I\'m sure you have better things to do.

I guess I kind of assumed that most Z users were geeks like me and get a kick out of seeing their PDA boot up just like their desktop and watching all of the messages scroll by. I also hate watching \"blank\" screens while waiting. Reminds me of Windows.  I\'d rather see what the OS is doing. Makes the wait seem less and gives a feeling like I know what is going on.

Again, though, don\'t do it just for me unless you are bored.

Also, is there still a command that will hault before loading QT and dump to console? I forget what it was.

[omega]

Here here, i would love to see all the action scrolling by as well.

[maslovsky]

OK, if there will be a few people who want such kernel I\'ll build it and package as a separate update. Next week maybe.

Also, is there still a command that will hault before loading QT and dump to console? I forget what it was.

Yes, press the \"/,\" button during Wait... prompt, you\'ll get a list of boot options.

[PowerZ]

I would prefer that as well.

[albertr]

Anton,

If you\'d like I can send you a patch to get rid of boot logo, I have it removed in my kernel. Not that looking at scrolling messages are very useful - they scroll so fast, it\'s hard to see anything...
-albertr