OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

11 Pages V  < 1 2 3 4 > »   
Reply to this topicStart new topic
> Cacko Kernel For Sl-5500/5000d
yzord
post Apr 15 2004, 11:07 AM
Post #16





Group: Members
Posts: 162
Joined: 11-December 03
Member No.: 1,152



QUOTE
Another thing, the link posted to the new battery applet is dead. Is there another location for this applet. The ZSI site has a protest page up so I can't get it from there either.

Richard


It's a typo. The actualy url is: http://my-zaurus.narod.ru/opie.html
Yz
Go to the top of the page
 
+Quote Post
rjedge
post Apr 15 2004, 11:42 AM
Post #17





Group: Members
Posts: 5
Joined: 14-April 04
From: Langley, BC Canada
Member No.: 2,847



QUOTE
It's a typo. The actualy url is: http://my-zaurus.narod.ru/opie.html


Thanks. Got it.
Go to the top of the page
 
+Quote Post
fatherb
post Apr 15 2004, 12:45 PM
Post #18





Group: Members
Posts: 8
Joined: 17-March 04
Member No.: 2,372



Just tried flashing the 64-0 kernel on my sl5500 with sharp 3.13. Flashes fine but after rebooting it shows the new cacko penguin logo and then hangs showing init: version 2.78 booting.

There's now 4 of us with this problem so clearly it doesn't work - will have a go with the 32-30 one and let all know the results.
Go to the top of the page
 
+Quote Post
fatherb
post Apr 15 2004, 12:58 PM
Post #19





Group: Members
Posts: 8
Joined: 17-March 04
Member No.: 2,372



Flashing with the 32-30 kernel worked, but I am unable to retrieve my backup. I tried renaming the original file (called '2004-04-15-20-35' to '2004-04-15-20-35-unknown' but it still can't find the file in the restore application.

For some reason I seem to have a different backup naming convention to the one Maslovsky mentions in his notes, 003-01-01-00-01.backup_SL5500-US-3.

I tried to put a .backup in my name but it won't accept '.' as a character.

Anyone have any ideas?
Go to the top of the page
 
+Quote Post
gregallen
post Apr 15 2004, 02:09 PM
Post #20





Group: Members
Posts: 7
Joined: 20-March 04
Member No.: 2,427



QUOTE
For some reason I seem to have a different backup naming convention to the one Maslovsky mentions in his notes, 003-01-01-00-01.backup_SL5500-US-3.  

I tried to put a .backup in my name but it won't accept '.' as a character.  

Anyone have any ideas?


create a new empty backup, and see what suffix it gets.

check the suffix from a terminal, rather than a filemanager.

likewise do the rename from a terminal ("mv <old> <new>").
Go to the top of the page
 
+Quote Post
ageiron
post Apr 15 2004, 02:31 PM
Post #21





Group: Members
Posts: 3
Joined: 15-April 04
Member No.: 2,868



Hi all,

I have the same problem posted here with the 60-0 zImage. Locks the Z very hard (must perform a hard reset to get it to turn off) after about 3 second when booting the new kernel.

I have been able to flash the 32-30 with no problem.

I am intersted in having the 60-0 work with my Zaurus since I have a couple of large custom programs that could benefit from such a configuration.

My SD card has already been formatted EXT2.

Is there anyway we can work together to resolve this? any especial procedures /configurations needed before flashing?

I will appreciate any help or guidance !

Regards, Antonio
Go to the top of the page
 
+Quote Post
Greg2
post Apr 15 2004, 02:35 PM
Post #22





Group: Members
Posts: 790
Joined: 28-October 03
From: USA
Member No.: 792



maslovsky

Works great, everything checks out ok!

Changing Backup file name works fine. Ambicom 56k ez-jack cf modem and SMC2642W ez-connect wireless cf cards work fine. Batteryapplet, overclock and usb-storage work, so far everything works and the card write speeds are up.

Thanks

Greg
Go to the top of the page
 
+Quote Post
tecknobabble
post Apr 15 2004, 02:46 PM
Post #23





Group: Members
Posts: 26
Joined: 17-March 04
From: UK
Member No.: 2,364



QUOTE
There's now 4 of us with this problem so clearly it doesn't work - will have a go with the 32-30 one and let all know the results.

Make that 5.... no joy with the 64-00, but the 32-30 is fine.... 64-00 locks up after the boot image - throws up running the rc.rofilesys script as far as I can tell. I run my own custom filesystem image that works with either sort of kernel and it looks like it blows up when its checking the /proc/cmdline to find out the memsize used....
Go to the top of the page
 
+Quote Post
Greg2
post Apr 15 2004, 02:55 PM
Post #24





Group: Members
Posts: 790
Joined: 28-October 03
From: USA
Member No.: 792



As for the 64-0 kernel...

Edit:
Please follow instructions updated by maslovsky

Greg
Go to the top of the page
 
+Quote Post
ageiron
post Apr 15 2004, 05:32 PM
Post #25





Group: Members
Posts: 3
Joined: 15-April 04
Member No.: 2,868



Hi,

Tried reflashing together with w initrd.bin from the sharp 3.13 rom (rombursted) and no joy either. Same result when starting. Pinguin logo and the INIT: version 2.7.8 booting and hard lock.

Only diference is that when the flashing process ended the two leds starting flashing together. This stopped as soon as the hard reset button was pressed. Never saw this before and I have tried almost every rom out there....

What can I try next? Does anyone have the 64-0 rom working on their Zs?

Rgds, Antonio
Go to the top of the page
 
+Quote Post
Xaser
post Apr 15 2004, 09:02 PM
Post #26





Group: Members
Posts: 35
Joined: 8-February 04
From: Costa Rica
Member No.: 1,771



Hi maslovsky!
Thank you very much for take the time to answer and the good will to help!!!... smile.gif
The simple suspend and put in the craddle put the ligth in order, now steady and normal! smile.gif

If this may help some of the other users, as a report of working, my Z5500 now appears to work fine, but I use the 30-32 rom and my Lexar SD card is formatted in VFAT (for easy access under windows and by means a card RW adapter...), and the initrd.bin of the upgrade is ProtoTKC v1.0, and the standar backup file was restored withouth rename it.

Im thinking about made a test with this new Cacko Zimage 64-0+ProtoTKC2.0+HomeOnSD script but Im not clear if there is a trouble with this combination, and I must make an effort to get the time for doing try and error work because my real work is a little charged by this days,so,if someone tried it or know see something that could make that the things dont go fine/work, well, some advice/alert will be appreciated, specially if it could save some waste of time/efforts...

best regards to everybody! smile.gif
Go to the top of the page
 
+Quote Post
maslovsky
post Apr 15 2004, 09:50 PM
Post #27





Group: Members
Posts: 1,426
Joined: 22-October 03
Member No.: 89



Important information regarding 64-0 kernel!

This kernel is only intended to be used on top of existing 64-0 Cacko/Crow ROM!!! I will not work if you flash it on top of 32-30 (default) ROM.

Also, it's not garantied to be compatible with TKC home on SD ROM, since it uses a different approach to implement it. However a 32-30 kernel may work.

If you want to use 64-0 configuration. you must flash one of the Cacko/Crow ROMs first, depending on your zaurus model (5500 or 5000D):

http://www.zaurususergroup.com/modules.php...download&sid=65

Read more info on Cacko/Crow ROM here:

http://www.schwag.org/~crow/
http://www.schwag.org/%7Ecrow/cacko/flash_...structions.html
Go to the top of the page
 
+Quote Post
fatherb
post Apr 15 2004, 10:29 PM
Post #28





Group: Members
Posts: 8
Joined: 17-March 04
Member No.: 2,372



Well, now we know what's wrong!!! It can't be used on the stock sharp rom.

Gotta say though Maslovsky, in your initial instructions it specifically states that the new kernel would work on the sharp 3.13 rom. Guess we are all lucky that we haven't turned our Z's into fancy new paperweights.

I have the 32-30 kernel flashed on my stock sharp 3.13 and it is so far working fine. Any plans to make the 64-0 work on the normal rom?
Go to the top of the page
 
+Quote Post
maslovsky
post Apr 15 2004, 10:36 PM
Post #29





Group: Members
Posts: 1,426
Joined: 22-October 03
Member No.: 89



QUOTE
Well, now we know what's wrong!!! It can't be used on the stock sharp rom.

Gotta say though Maslovsky, in your initial instructions it specifically states that the new kernel would work on the sharp 3.13 rom.  Guess we are all lucky that we haven't turned our Z's into fancy new paperweights.

I have the 32-30 kernel flashed on my stock sharp 3.13 and it is so far working fine.  Any plans to make the 64-0 work on the normal rom?


Yes, I must have been not clear enough on my instructions, sorry. I've updated them. 64-0 cannot work on normal ROM, since there is no space for /home. You have to flash Cacko/Crow ROMs to use 64-0 config.
Go to the top of the page
 
+Quote Post
tecknobabble
post Apr 16 2004, 12:17 AM
Post #30





Group: Members
Posts: 26
Joined: 17-March 04
From: UK
Member No.: 2,364



QUOTE
Yes, I must have been not clear enough on my instructions, sorry. I've updated them. 64-0 cannot work on normal ROM, since there is no space for /home. You have to flash Cacko/Crow ROMs to use 64-0 config.

I run a Crow like ROM and the 64-0 still doesn't work, maybe I didn't make that clear in my previous reply. No worries as I've gone back to my own kernel, if I can find the details of the patches I might roll them into mine and see what happens.
Go to the top of the page
 
+Quote Post

11 Pages V  < 1 2 3 4 > » 
Reply to this topicStart new topic
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 24th October 2014 - 01:34 AM