OESF Portables Forum
Everything Else => Sharp Zaurus => Model Specific Forums => Distros, Development, and Model Specific Forums => Archived Forums => C1000/3x00 General discussions => Topic started by: steliosx on July 02, 2005, 06:26:15 pm
-
EDIT: current problem:
trying again for about 10 times, and Im really pissed. here is what I get, no matter if I use an empty Dane-Elec CF 512Mb or an empty Kingston SD 1Gb.
After following the instructions I quoted above, here is how it goes:
1. Sharp Logo
2. "INIT - Booting version 2.78"<4-5 seconds pass>
"sl_time nand_read_time"
[b]touch: /home/sharp/etc/rts_reset: no such file or directory[/b]
INIT - Entering runlevel 4<1 second passes>
--- Zaurus CF updater ---
Please Reset|
Please, somebody, help me or I'll through this thing out of the window... been trying for a couple of hours already..
Old post:
hello all
I dloaded tetsu's special kernel for my c1k - files updater.sh and zImage on to my CF card, rebooted while holding down OK button, selected option 4 at the flash menu and confirmed by pressing Y,
waited for the process to finish, removed the battery when asked to reboot after process finished - and here I am
mplayer-iwmmxt 1.5 installed OK and so did bvdd 0.4
however in Zplayer frontend it wont let me select the "enable iwmmxt extensions" button..
I was wondering if the Kernel installed OK. can anybody provide a way for me to check that v18a kernel is indeed installed in my C1000? is there a way to see it?
thanks!
-
The easist way to be sure is to run "uname -a" from the console.
The info is also kept in /proc/version (or somewhere similair), when you rebooted the Z did you see the standard sharp "please wait" screen or did you have a lot of text scrolling by? If you had the text then you have installed the new kernel.
The problem with Zplayer and not being able to select iwmmxt is that Zplayer doesn't recognise the C1k properly yet so it doesn't konw to turn on iwmmxt or to use bvdd.
Stu
-
hello Stubear and thanks, im getting:
bash-2.05$ uname -a
Linux zaurus 2.4.20 #1 Mon, 28 Feb 2005 19:44:25 +0900 armv5tel unknown
and then im getting:
bash-2.05$ su # more /proc/version
Linux version 2.4.20 (namikosi@mascaras) (gcc version 2.95.2 19) #1 Mon, 28 Feb 2005 19:44:25 +0900
any ideas?
by the way if it isn't installed, can somebody provide the instructions again?
here is what i did:
This is how you update your kernel (you'll find the files at the end of this page)
Put your Z on the charger (it will not work otherwise)
Put zImage and updater.sh on an empty CF-card. There should be no other files on the card
Open your C's Terminal, become root (su -) and type reboot.
Press and hold the OK button during the complete re-booting process.
The following menus are most likely in Japanese. From the service menue, select option 4 (four). Select CF and acknowledge the upcoming warning by moving to the left button and press OK.
The new kernel will now be transferred on to your system. If the Z asks you to reset, disconnect the charger, open the battery compartment and remove the battery. Wait 10 seconds or so, put the battery back in, close the compartment and slide the little switch back to lock.
Turn you Z on and let it boot.
-
hello Stubear and thanks, im getting:
bash-2.05$ uname -a
Linux zaurus 2.4.20 #1 Mon, 28 Feb 2005 19:44:25 +0900 armv5tel unknown
and then im getting:
bash-2.05$ su # more /proc/version
Linux version 2.4.20 (namikosi@mascaras) (gcc version 2.95.2 19) #1 Mon, 28 Feb 2005 19:44:25 +0900
any ideas?
It looks like the original Sharp kernel
by the way if it isn't installed, can somebody provide the instructions again?
here is what i did:
This is how you update your kernel (you'll find the files at the end of this page)
Put your Z on the charger (it will not work otherwise)
Put zImage and updater.sh on an empty CF-card. There should be no other files on the card
Open your C's Terminal, become root (su -) and type reboot.
Press and hold the OK button during the complete re-booting process.
The following menus are most likely in Japanese. From the service menue, select option 4 (four). Select CF and acknowledge the upcoming warning by moving to the left button and press OK.
The new kernel will now be transferred on to your system. If the Z asks you to reset, disconnect the charger, open the battery compartment and remove the battery. Wait 10 seconds or so, put the battery back in, close the compartment and slide the little switch back to lock.
Turn you Z on and let it boot.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86845\"][{POST_SNAPBACK}][/a][/div]
Yep, that's what I do except
1. I don't worry about the card being empty
2. I use the "reboot" option on the Menu (Q -> reboot) and hold down OK after clicking "yes" to reboot message
3. After the new kernel is copied you should see a message
--- Zaurus SD Updater ---
zImage: 1235792bytes
Successfully Completed.
Please reset
And as I mentioned previously you will see lots of scrolling text rather than the white Sharp welcome screen.
I'm unable to flash tetsu's special kernel at the moment but the testsu site says The version is displayed like v18a@tetsu.homelinux.org.
which isn't what your /proc/version states.
You should also have a /proc/tpressure or /proc/zaurus/tpressure if the correct version has been installed properly.
Hope this helps
Stu
-
Also, just in case: don't forget to install the modules ipk which come along Tetsu's kernel... bvdd, for instance, comes as a module with this kernel.
On my C3000 with Tetsu's v.18a kernel, uname -a gives:
Linux zaurus 2.4.20 #1 Tue, 03 May 2005 23:36:41 +0900 armv5tel unnknown,
and cat /proc/version reports:
Linux version 2.4.20 (v18a@tetsu.homelinux.org) (gcc version 2.95.2 19991024 (release)) #1 Tue, 03 May 2005 23:36:41 +0900.
-
thanks for the feedback guys
seems that the kernel was not updated.
could someone care to provide the steps of this upgrade again? translating tetsu.homelinux.org didn't help
thanks in advance
EDIT: trying again for about 10 times, and Im really pissed. here is what I get, no matter if I use an empty Dane-Elec CF 512Mb or an empty Kingston SD 1Gb.
After following the instructions I quoted above, here is how it goes:
Sharp Logo
INIT - Booting version 2.78
<4-5 seconds pass>
sl_time nand_read_time
touch: /home/sharp/etc/rts_reset: no such file or directory
INIT - Entering runlevel 4<1 second passes>
--- Zaurus CF updater ---
Please Reset|
help me or I'll through this thing out of the window... been trying for a couple of hours already..
-
--- Zaurus CF updater ---
Please Reset|
help me or I'll through this thing out of the window... been trying for a couple of hours already..
Can't test right now to confirm, but I remember that I had the same problem once before. In my case, reformatting the SD card with a FAT16 partition seemed to solve the problem, as far as I can remember, the Zaurus appeared not to be able to read the file during my first attempt. Here is a picture of what was displayed on the screen when I reflashed the ROM (during my first Cacko ROM install):
[ You are not allowed to view attachments ]
Hope this helps...
In case you want to investigate the issue, here's what fdisk -l /dev/mmcda reports:
Disk /dev/mmcda: 255 MB, 255852544 bytes
16 heads, 32 sectors/tracks, 976 cylinders
Units = cylinders of 512 * 512 = 262144 bytes
Device Boot Start End Blocks Id System
/dev/mmcda1 1 976 249805+ 6 FAT16
Also, I'm sure you already checked this again and again, but you have to make sure that 1) the card is empty and contains only the required files, and 2) the file names are set appropriately (in a nutshell, there should be only the updater.sh script and the zImage.bin file). If you didn't rename the files you downloaded to those names (and the upper/lower case matters, of course), then this would be a good start. If you did all this already, then I've got no idea what you did wrong!
-
Which updater.sh file are you using?
Also what is the name of the zImage file?
If you are using the updater.sh from testsu's site then the zImage must be called zImage (not zImage.bin)
If you are using the updater.sh from the Sharp site then it should be zImage.bin but might not work with the tetsu kernel.
Also as euroclie mentioned make sure the cards are formatted FAT16 not FAT32, if you format them under windows you will get the option of FAT and FAT32, FAT is what you want.
Good luck
Stu
-
where's Tetsu's special c1k ROM?
-
Which updater.sh file are you using?
Also what is the name of the zImage file?
If you are using the updater.sh from testsu's site then the zImage must be called zImage (not zImage.bin)
im using updater.sh.C1000 renamed to updater.sh from tetsu's site
f*ck, thats what I couldn't make out - i was used to using zImage.bin always!
anyways! hope that renaming it to zImage alone will do the trick
thanks for the feedback guys!
samxiao, check http://tetsu.homelinux.org/zaurus/kernel/index.html (http://tetsu.homelinux.org/zaurus/kernel/index.html)
-
samxiao, check http://tetsu.homelinux.org/zaurus/kernel/index.html (http://tetsu.homelinux.org/zaurus/kernel/index.html)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=87212\"][{POST_SNAPBACK}][/a][/div]
thanks for your help
which ROM i should download?
all Japanese
can't read
i try Excite! translation
still couldn't understand
thanks for any help
-
what about initrd.bin?
where should i find it?
-
If you have a C1k then you want to download "SL-C1000 special kernel (v18a)", the link is about 1/4 down the page and downloads the file zImage-v18a-C1000.bin. Renmae this to zImage when you ocpy it to the zaurus.
There is no initrd.bin, this is a kernel only so no rom file
Stu
-
If you have a C1k then you want to download "SL-C1000 special kernel (v18a)", the link is about 1/4 down the page and downloads the file zImage-v18a-C1000.bin. Renmae this to zImage when you ocpy it to the zaurus.
There is no initrd.bin, this is a kernel only so no rom file
Stu
[div align=\"right\"][a href=\"index.php?act=findpost&pid=87265\"][{POST_SNAPBACK}][/a][/div]
but i already erase the original content on my Zaurus
therefore i need a initrd.bin to get my stuff back
not just the kernel
do you guys have an English Cacko NAND share with me?
thanks
i'm screwed
-
trisoft.de has a nand backup of the sharp rom for c1000.
-
what about initrd.bin?
where should i find it?
(Note: by the time I finished to type this post, the thread had already moved on, and it is probably not very relevant / needed anymore, but I'll post this nonetheless as it may be usefull to other users later...)
Let's try to see if I'm better at understanding online translation engines! (no warranty, though... there are big disclaimers everywhere when you try playing with that kernel update stuff, and I didn't spend time to translate them, but I suppose that you already know that bad things can potentially happen to your Zaurus! )
Warning: it seems that I didn't get it right, Ragnorok used these translated instructions to reflash his C1000, and couldn't switch it on again after a seemingly successful reflash, so there is obviously a problem here. I'd advise against using this post to reflash your Zaurus until the cause of the problem has been found. This post will then be re-edited and I'll remove this warning...
Here's what I understand from Tetsu's instructions (automated translation edited for clarity and to remove stuff that doesn't apply to the C1000. Warning, the links (kernel image and modules) are valid only with the v18a version, the latest at the time I write this):
Kernel update procedure:
(1) Download updater.sh.c1000 from Sharp's developer website (http://developer.ezaurus.com/sl_j/source/c1000/kernel_update_c1000.htm). This page contains a big disclaimer, and a tiny line with the link to the file. Here is the direct link to updater.sh.c1000 (http://developer.ezaurus.com/sl_j/source/c1000/20050228/updater.sh.c1000). Once you have this file, rename it to updater.sh and copy it at the root of an empty CF or SD card.
(2) Download the c1000 kernel image from Tetsu's website (http://tetsu.homelinux.org/zaurus/kernel/v14e/zImage-v18a-C1000.bin) and rename it to zImage, then copy it as well on the CF or SD card. (no .bin extension, and mind the case, as usual!)
(3) Check that there is no other file on your memory card except updater.sh and zImage. (in particular, you must NOT have a initrd.bin file on your card!)
(4) Follow Sharp's website instructions for kernel updating. (see below)
(5) Install the C1000/3000 Special Kernel's associated modules (http://tetsu.homelinux.org/zaurus/kernel/v14e/kernel-modules_v18a_arm.ipk) (.ipk file) after the next boot.
And here are the instructions on Sharp's website (that's the page where you get the updater.sh.c1000 file):
Sharp's Linux kernel update procedure
This is the procedures to update the SL-C1000 Linux kernel to the latest one. Please follow every step one by one in the following order.
1) Prepare your SD or CF memory card (which must have at least 16MB empty space or more) in order to update the Linux kernel.
Do not format with FAT16 (or FAT), or do not reformat the memory card after purchasing it. The first partition on the memory card must be a vfat partition.
Make sure that the SL-C1000 can recognize the card by inserting it in the Zaurus and checking that the SD or CF card icon appears in the taskbar before updating the Linux kernel.
2) Copy the updater.sh and zImage files on the memory card's root directory, and make sure that there is no other file in that directory. The zImage file must be at most 1260KB, and the updater.sh (for the C1000) file size is 2560 bytes.
3) Back up your personal data to PC before updating the Linux kernel.
4) Turn off your SL-C1000.
5) Insert the memory card in the SL-C1000. Do not insert any other card during the kernel update.
6) Make sure that the AC adapter is connected to the SL-C1000 and operating (charge LED must be illuminated). Make sure that the battery is charged enough before updating the kernel. You won't be able to proceed with the update if the orange battery LED doesn't illuminate.
7) Set the battery compartment switch to "release" and remove the battery cover. Wait for 30 seconds, then push the reset switch (inside the battery compartement) with a pen tip, then reinstall the battery cover and set the switch to "lock" again.
8) Check that the orange battery LED is illuminated, then press the "Power" button while keeping the "OK" key pressed until you see the maintenance menu (in Japanese).
9) In the maintenance menu, select the fourth entry (4.アップデート).
10) Depending on the type of card you copied the files to, select either the first (1.CF) or second (2.SD) menu on the next screen, then select "はい(Y)" to confirm your choice and proceed to the update.
11) The Zaurus will display "Successfully Completed. Please reset" after the kernel update, so at that point perform again the step #7, then switch on your Zaurus normally.
Do not interrupt the update process and do not remove the AC adapter during the update, unless you turn your Zaurus into an expensive paperweight!
I hope that I didn't make any big mistake when editing the text, and that the few users on the board that do read Japanese will help me correct these instructions if there's anything wrong... One word about the memory card format: it seems that Sharp recommends using a vfat partition (or the online translation engine got it wrong), but I've had some success with a FAT16 partition nonetheless... Go figure! Any input on this subject is welcome!
-
I was able to update to the 18a kernel just fine, however, it appears Tetsu's kernel modules are no longer where he has them linked. I get
/zaurus/kernel/v14e/kernel-modules_v18_arm.ipk was not found on this server
Anyone have a copy of it to share?
shane
-
I was able to update to the 18a kernel just fine, however, it appears Tetsu's kernel modules are no longer where he has them linked. I get
/zaurus/kernel/v14e/kernel-modules_v18_arm.ipk was not found on this server
Anyone have a copy of it to share?
shane
[div align=\"right\"][a href=\"index.php?act=findpost&pid=87289\"][{POST_SNAPBACK}][/a][/div]
does this have support of ext2 like Cacko did?
-
it appears Tetsu's kernel modules are no longer where he has them linked. I get
/zaurus/kernel/v14e/kernel-modules_v18_arm.ipk was not found on this server
Anyone have a copy of it to share?
Can't get the file, the link is broken on Tetsu's page, you're right.
But if you edit the url and replace "kernel-modules_v18_arm.ipk" by "kernel-modules_v18a_arm.ipk" (follow the link) (http://tetsu.homelinux.org/zaurus/kernel/v14e/kernel-modules_v18a_arm.ipk) you can get the latest module. Thanks for the pointer, I'll update my post right now!
-
it appears Tetsu's kernel modules are no longer where he has them linked. I get
/zaurus/kernel/v14e/kernel-modules_v18_arm.ipk was not found on this server
Anyone have a copy of it to share?
Can't get the file, the link is broken on Tetsu's page, you're right.
But if you edit the url and replace "kernel-modules_v18_arm.ipk" by "kernel-modules_v18a_arm.ipk" (follow the link) (http://tetsu.homelinux.org/zaurus/kernel/v14e/kernel-modules_v18a_arm.ipk) you can get the latest module. Thanks for the pointer, I'll update my post right now!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=87293\"][{POST_SNAPBACK}][/a][/div]
why you need to install this module?
isn't the zImage already using v18 kernel?
-
why you need to install this module?
isn't the zImage already using v18 kernel?
Some things have been compiled as modules and not included in the kernel, that's why you probably want to install the associated modules.
It's mostly bluetooth and USB stuff, but there are some other things you might need (bvdd for mplayer, for instance).
-
why you need to install this module?
isn't the zImage already using v18 kernel?
Some things have been compiled as modules and not included in the kernel, that's why you probably want to install the associated modules.
It's mostly bluetooth and USB stuff, but there are some other things you might need (bvdd for mplayer, for instance).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=87297\"][{POST_SNAPBACK}][/a][/div]
do you know if this one supports mounting of ext2?
i know the original JP SharpROM doesn't
-
does this have support of ext2 like Cacko did?
If you check Tetsu's website (http://tetsu.homelinux.org/zaurus/kernel/index.html), there's a link at the bottom to the kernel config file (http://tetsu.homelinux.org/zaurus/kernel/v14e/v18a-C1000) used to compile the C1000 special kernel, you'll know which options are configured as a module (CONFIG_xxx=m) and which are built-in into the kernel (CONFIG_yyy=y).
There's a line which reads:CONFIG_EXT2_FS=y
So I think it's safe to assume that ext2 support is included in the special kernel!
-
does this have support of ext2 like Cacko did?
If you check Tetsu's website (http://tetsu.homelinux.org/zaurus/kernel/index.html), there's a link at the bottom to the kernel config file (http://tetsu.homelinux.org/zaurus/kernel/v14e/v18a-C1000) used to compile the C1000 special kernel, you'll know which options are configured as a module (CONFIG_xxx=m) and which are built-in into the kernel (CONFIG_yyy=y).
There's a line which reads:CONFIG_EXT2_FS=y
So I think it's safe to assume that ext2 support is included in the special kernel!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=87301\"][{POST_SNAPBACK}][/a][/div]
thanks
since i erase my orig JP ROM
and they don't provide initrd.bin
so i need to reflash back the NAND from TriSoft right?
-
since i erase my orig JP ROM
and they don't provide initrd.bin
so i need to reflash back the NAND from TriSoft right?
That seems your only solution right now, I think. But then, I only have a C3000, which is different (because the OS is basically on the hard drive, not in Flash), so don't trust my word only on such an important subject!
-
what about initrd.bin?
where should i find it?
...[snip]...
Kernel update procedure:
...[snip]...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=87282\"][{POST_SNAPBACK}][/a][/div]
- Just followed euroclie's procedure to the letter. All went swimmingly until I got to the bit about turning on the Zaurus normally. Somehow that didn't go quite as planned. (little boy pout)
- The power LED goes out, the screen flashes power for a split-second ... then dead as a door nail. Resetting (hard reset under battery cover) brings the power LED back, and I can still enter the maint menu. I reflashed tetsu's 18a kernel again, just for kicks, and got the same result. I did get to Successfully completed. Please reset both times I flashed.
- Fortunately I also snagged the "original" kernel. I'm going to try flashing back to see if it doesn't revive the system. Most unfortunate ... this is the first time I've tried flashing anything on Hiro, and it's not a good foot to start on. (bemused grin)
- If that fails, I have a NAND backup of the system as shipped to me that aught to force the issue, at the expense of tons of time to rebuild it the way it was now. I should have done a NAND backup of the system as it was!! (smirk) Good ol' hindsight.
- None-the-less, if anyone has any perls of wisdom to impart, I'd be happy to read them. Maybe I'll give it another go after some reconnoiter...
P.S. - The "original" kernel flash did fail. It does the same thing, but the power LED pops back on all by itself, and it will repeat this dog and pony show. It just won't turn on. Most unsatisfying. (frown)
P.P.S - Z*A*T*C*H
- Wound up doing a NAND restore ... it's in progress now ... hope it works!! (fretful hand-wringing)
P.P.P.S - It did. Now I get to try to get my backup of PIM/PI's data to work when it's no longer in the ROM area! (drool) Beats a brick any day!...
-
- Just followed euroclie's procedure to the letter. All went swimmingly until I got to the bit about turning on the Zaurus normally. Somehow that didn't go quite as planned. (little boy pout)
- The power LED goes out, the screen flashes power for a split-second ... then dead as a door nail. Resetting (hard reset under battery cover) brings the power LED back, and I can still enter the maint menu. I reflashed tetsu's 18a kernel again, just for kicks, and got the same result. I did get to Successfully completed. Please reset both times I flashed.
Ouch! That's bad news... I'll try to reflash Sharp original kernel this week-end, then reflash Tetsu's kernel again to see if the translation I made works at least on my C3000.
I'm sorry that it didn't work as expected, I must have missed something. That's strange because as far as I can remember I did follow the same procedure when flashing my 3000, but then that was a few weeks/months ago, back when Cacko beta1 was released for the 3k...
I'm glad that a NAND restore did unbrick your Zaurus, though!
I'll modify my post to prevent anyone else from using these translated instructions until we've tracked the problem.