OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Sharp ROMs => Topic started by: dovregubb on March 06, 2004, 09:04:57 am
-
Hi
I as the header say I am using a SL5500 with TKC ROM Alpha 3 with the home on SD script found in ZUGs mirrored devnet pages.
This works extremley well (after owning a Zaurus for 2 years I finally find it usefull) However here the other day I had to perform a HARD reset.
I know this is because for some reason the ROM dosent udnerstand the SD is a /home or something. Because of the way the script mounts the SD device.
The error message is something like this: Invalid argument while trying to open /dev/mtdblock1
I am not a computer litterate, but I am quite ill-literate when it comes to Linux commands. So please help me what I need to do to get it up and running again.
Thanks
- Dovregubb
-
Hi,
I had a similar problem with my sd card 256mb sandisk. Records on my card were corrupted and then the OS did crash. I could fix it by changing the mout option in the generated rc script. There is used the async option during mount. I changed it to sync and all worked fine up to now.
Axel
-
Well, ok but I am not able to use vi as it gives error message: Can\'t create temporary file, errno=no. So how do I edit it then?
- Dovregubb
-
Ok, I have managed to get to the TKC Loading screen. However it is not able to pass this screen and keeps lookping back to the wait 5 seconds screen and restarting the TKC loading screen... again and again...
Desperatly in need of help here.
-
If you want, try the most recent prep-home-sd.sh script (uploaded here, file name \"prep-home-sd_test5.zip\"). One thing, do not use the prep-home-sd.sh that ships with the tkc alpha3 rom. This one was more betta, and after I originally sent it to Proto for inclusion we were discussing ways to make it more interesting. One of the things that was added to it was a mkswap at the end of it to turn the ramdisk into swap. The effect of this was that once the swap started being used, if you rebooted the Zaurus then an earlier part of the boot scripts would try to do an fsck on the ramdisk and end up hanging.
This newer version of the script is more elabrate, it allows you to specify the size of an optional swap file to put within the filesystem of the ramdisk, and the generated rc.card script will remember that value to recreate the swap file if you hard-reset. It also has a few other options in it that is documented within the script. I\'ve exhaustive tested this new one, with multiple soft and hard resets, even re-flashing the rom, and it appears to not have any issues (at least for me).
The options combination I end up using is:
$ prep-home-sd.sh -s 20 -t -c -f
This gives you a 20-meg swapfile (-s 20), mount /tmp as a ramfs filesystem (-t), copies your existing /home to the SD (-c) (instead of initilizing an SD with default values, which would be -i), and mounts the SD card via the loopback driver for faster speed (-f). You might want to leave off the -f flag... it makes writes to the SD card faster, but may also fail in some configurations.
If you do a smaller or no swapfile, then leave off the -t flag. (With a big swapfile there is little room left on the ramdisk for /tmp files, but with no swap file you will run low on memory by having /tmp mounted as a ramfs. And I don\'t put /tmp on the SD for speed reasons.) Also, instead of specifying the -f flag (which speeds up writes but can cause potential hanging issues for some people), you can install the async io kernel that I uploaded here the other day. It\'s in the sl-5500 kernel downloads section.
Also note that if you are having issues where your Zaurus hangs on suspend with using /home on SD, that is because some brands of SD cards are simply incompatible with surviving a suspend/resume cycle. The effect is that on resume, the card is unreadable until it is unmounted/remounted (normally handled by the sdmgr program). And it can\'t be unmounted if it is in use, which would be the case when you are running your environment off of it. My recomendation is to use Lexar cards, stay away from Sandisk and PNY cards (from various reports I\'ve had).
I\'m also about to relase a howto and some scripts that will automatically rebuild a regular Sharp 3.10 or TKC 1.0 rom (with a modified /root/etc/rc.d/rc.sysinit script) so that it will work with this /home on SD method. I\'ve got to take a bit more time to test it out to make sure I don\'t have any errors in it.
-
I did as you suggested. Downloaded the newest version of the script. Reflashed and started up from scratch. Not only is this script working on resets. But it is also seemlessy faster than before. Actually my SL5500 is now faster than it ever were. Its AMAZING to think that your script can bring so much life into a 2 years old PDA.
Thanks for all the effort!
- Dovre
-
I made the same experience! Thanks a lot!
-
Can someone lead me by the hand (or at least pointing me to a site, old Devnet location or other thread in ZUG) in the process of preparing to run this script; especially keeping these things in mind:
Does tkcrom backup do both apps and docs? (I have never tried this.) Is it better to send to pc or cf?
Then do format of sd?
Script run here, correct?
Will restore put the apps and docs back \"in place\" to run from the newly ext formatted sd?
-
derekp - I have a few questions:
I read through a few threads regarding your async kernel - out of curiosity, is there a way to upgrade the kernel that would not require a full ROM flash? Not a big prob, but I have things setup nicely on my 5500 right now If not, I\'ll just flash with the zimage that you posted on 3/5/04.
To clarify, if I go with the async kernel, I would not with the -f fast SD mount option, right?
In your description of the script, you wrote the following: \"copies your existing /home to the SD (-c)\". And in the code I see: \"-c -- copy existing ramdisk-based /home contents to the SD card\". Does this mean that the ram contents are left on the ramdisk as well? If so, won\'t they take up too much space on the ramdisk, which is the space that we\'re trying to free up via home-on-sd?
What\'s the advantage/difference of the -c option versus -i?
For the -t option, the code mentions: \"(should be used with ramdisk option)\" What option is that referring to?
Thanks in advance. Oh, and If your answer is \"wait til I freakin finish the docs$@#$!!\", I certainly understand
- Nate
-
derekp - I have a few questions:
First of all, you are using the TKC 2.0-alpha 3 rom right? (I think you mentioned that before, but I\'m to lazy to look that up right now)
If not, then the prep-home-sd script won\'t do you much good (until I release modrom script in a few days, which will modify your existing rom to support home-on-sd).
I read through a few threads regarding your async kernel - out of curiosity, is there a way to upgrade the kernel that would not require a full ROM flash? Not a big prob, but I have things setup nicely on my 5500 right now If not, I\'ll just flash with the zimage that you posted on 3/5/04.
Updating the rom requires you to hit the reset button afterwards, which will wipe out your ramdisk. However, I think that if you are just rewriting the kernel, you might not have to hit the reset button a second time.
To clarify, if I go with the async kernel, I would not with the -f fast SD mount option, right?
Yes, this is correct. In fact, the async kernel is a bit faster than using the -f flag (-f just builds the rc.card script on the SD with the \"-o loop\" option on the mount command).
In your description of the script, you wrote the following: \"copies your existing /home to the SD (-c)\". And in the code I see: \"-c -- copy existing ramdisk-based /home contents to the SD card\". Does this mean that the ram contents are left on the ramdisk as well? If so, won\'t they take up too much space on the ramdisk, which is the space that we\'re trying to free up via home-on-sd?
What\'s the advantage/difference of the -c option versus -i?
Yes, the ramdisk contents are untouched either way.
If you wanted to free up your ramdisk, then you could either do that manually, or hit the reset button which will re-initialize the ramdisk.
The general idea is that after the procedure, you could continue to boot up either with or without the SD card to switch between /home on ram, or /home on SD. So you aren\'t committed to keeping your SD slot tied up all the time.
So, for example, if you use the -i switch, then your SD card will resemble a freshly reset zaurus. If you use -c, then your existing settings and all installed apps should be preserved onto the SD. You can then feel free to wipe out your ramdisk after testing out booting off the SD.
For the -t option, the code mentions: \"(should be used with ramdisk option)\" What option is that referring to?
The way I set it up, is that the /tmp directory still points to the ramdisk. If you create a large swap file, then there won\'t be enough room on your ramdisk for /tmp. Therefore, by making /tmp a ramfs filesystem type, you end up with one pool of storage to share between virtual memory and /tmp files (it dynamically resizes itself to store the files as needed). However, if you don\'t create a swap file, or have a small one, then if you use /tmp as a ramfs filesystem, you will be eating into your application memory. I didn\'t want to commit to any cutoff values for one way or the other, so I leave it up to the individual to do what works the best.
BTW, most of these options only affect how the rc.card script is built. You can always tweek the script afterwards, i.e, if you want to switch from the loopback /home mount you modify a variable at the top of the script.
Hope this answers most of you questions.
--derek
-
Tremendous, derek! To confirm, I\'m using the TKC 2.0-alpha 3 rom on a 5500.
Last Q: So once I perform the home-on-sd, I assume that all apps that I install to internal ROM will actually be installed to the SD card, correct? Would installing to SD then become redundant, or would it somehow install packages differently if I use -dest /mnt/card?
Thanks a lot for your feedback - I\'ll be giving this a try tomorrow morning...
-
I did it, and it worked great! I applied derek\'s async zImage and flashed with tkcROM 2.0-alpha3, then ran the script:
# prep-home-sd.sh -s 20 -t -c
I really wish that I would have benchmarked writes and reads on my SD card beforehand, as they seem VERY fast now comparatively. Thanks for the excellent work, derek!
Then.... my card could not recover from a suspend (SanDisk 512MB).
For the benefit of anyone that wants to know (???), I will share my experiences:
After a hard reboot, my 5500 spewed a TON of error messages until I finally decided on a hard reset. I received a bunch of error messages during the load after the reset, but eventually QT loaded up and to my amazement, the apps that I installed were still there and functioning. The home-on-sd was still in effect.
I then reflashed from the CF card with the async zImage and tkcROM 2.0-alpha3, and I got the same results.
Finally, I took the SD out, did a hard reboot (wouldn\'t respond to suspend or reboot commands), and things seemed to work as if the SD card never existed (as derek indicated it would). I then reformatted my SD card as ext2, and I was officially back in business with the normal functionality of the async zImage and tkcROM 2.0-alpha3. For good measure, I performed another hard reset, and the tkcROM loaded normally with no errors.
Doug - I wanted to help you with some other questions, but only after I had this working fully on my end. I will try to exchange my SanDisk 512MB card tonight for a Lexar 512MB card at Circuit City (hoping that it\'s not past the return window of time), then I will try this again with that card...
Can someone lead me by the hand (or at least pointing me to a site, old Devnet location or other thread in ZUG) in the process of preparing to run this script; especially keeping these things in mind:
I\'ll try
Does tkcrom backup do both apps and docs? (I have never tried this.) Is it better to send to pc or cf?
Then do format of sd?
I have only backed up to/from my Windows XP system, so I can\'t really talk regarding backups to CF. As a note, IIRC due to a bug, the tkcROM 2.0-alpha3 will not allow you to backup to CF. In addition, when I restore from my backups on my PC with this ROM, I am never able to suspend my 5500 (another bug in this version of tkcROM). Thus, ASAIK, there is no effective backup method for tkcROM 2.0-alpha3. Brutal.
Will restore put the apps and docs back \"in place\" to run from the newly ext formatted sd?
The restore process (in general) should fully restore everything to your zaurus\' ramdisk, so since the zaurus \"thinks\" that the SD card is a part of internal ram (that\'s what it seems like to me), IMO it should backup the ramdisk and SD accordingly. Perhaps derek could add to this.
Script run here, correct?
As indicated above, I put the script from this site (hosted in ZUG downloads) on my CF card, as well as the async zimage. I then flashed my 5500 with the async zImage (let me know if you need more of an explanation for any of this), then I ran the script from the terminal (see command above) at the location of the script on my CF card. The script ran successfully, then I had to reboot to see the effects of home-on-sd in place.
I know this is LOOONG, but I hope that it\'s helpful in terms of the steps and what to expect.
God bless!
Nate
-
derekp - I went out and grabbed a Lexar 256MB SD card, and I was having the same results that I described in the last thread with my SanDisk 512MB: It will not suspend, and once I try to do so, I am forced to do a hard reset.
However, I finally figured out that if I remove the 5500 from the cradle when I perform the suspend, it suspends fine and recovers as expected! Not sure what\'s going on here, but I\'ll make a personal note NOT to suspend while it is in the cradle anymore.
I will retest my SanDisk SD card again and see if it is working all right-
Nate
EDIT: I tested this successfully with my SanDisk card and it\'s working great. I am using the asyncio zImage and the improved mmcsd.o module and things seem to be working great now! So much swap and the SD-write improvements have made my 5500 INCREDIBLY fast compared to my old configuration. Thanks again for sharing this knowledge!
On a side note, I left my 5500 on in the cradle last night, and when I woke up all that I would get is the following:
The system booted to this:
I had a shell and it complained that the file system was corrupt. It then gave me these options: Enter password to repair or press Control-D. Then:
1) reboot... after which it dies and can\'t be started unless I flash it again
2) I get a prompt that comes up like the following
(Repair FS) #
So, once again I had to flash it. Pretty unstable from my usage thus far...
-
Well, as much fun as it\'s been to use the asyncio kernel, I just encountered a dealbreaker... at least for the present. It seems that the asyncio kernel has affected the serial_cs.o, to the effect that I get the following messages when installing bluetooth (as usual on tkcROM):
# ipkg install bluez-zaurus_2[1].3-2.4.18d_arm.ipk
Unpacking bluez-zaurus...Done.
Configuring bluez-zaurus...depmod: *** Unresolved symbols in /lib/modules.rom/2.4.18-rmk7-pxa3-embedix/kernel/drivers/char/pcmcia/serial_cs.o
Starting Bluetooth... Can\'t open serial port: No such device
Can\'t initialize device: No such device
Done.
Done.
# modprobe serial_cs
/lib/modules.rom/2.4.18-rmk7-pxa3-embedix/kernel/drivers/char/pcmcia/serial_cs.o: unresolved symbol unregister_serial
/lib/modules.rom/2.4.18-rmk7-pxa3-embedix/kernel/drivers/char/pcmcia/serial_cs.o: unresolved symbol register_serial
/lib/modules.rom/2.4.18-rmk7-pxa3-embedix/kernel/drivers/char/pcmcia/serial_cs.o: insmod /lib/modules.rom/2.4.18-rmk7-pxa3-embedix/kernel/drivers/char/pcmcia/serial_cs.o failed
/lib/modules.rom/2.4.18-rmk7-pxa3-embedix/kernel/drivers/char/pcmcia/serial_cs.o: insmod serial_cs failed
#
Any ideas here, Derek? I\'d like to get this working, but replacing the existing driver with another copy of serial_cs.o that I have (then doing a depmod -a and modprobe) did not seem to work, so I\'m off to the original tkcROM zImage for now...
-
derek...
I cannot find the \"prep-home-sd_test5.zip\" file anywhere, and your \"here\" is not a link. Help!
-
Doug -
- Go to Zaurus Downloads from the Home page
- type \"prep-home\" in the search box
The first item to appear from the search should be the file.
-
Derekp, I\'ve found a bug with this new async IO kernel. With your kernel I found that I cound not get my NPC card to work correctly. It detected it fine, but the Network Connection icon in the taskbar would never come up. Going back to the old kernel this works no problem.
-
Derekp, I\'ve found a bug with this new async IO kernel. With your kernel I found that I cound not get my NPC card to work correctly. It detected it fine, but the Network Connection icon in the taskbar would never come up. Going back to the old kernel this works no problem.
As I indicated as well, when I install the Bluez driver ipk with the async kernel (as opposed to the kernel that accompanies the latest tkcROM release), I get errors with the serial_cs module. So I, too, had to abort my use of the kernel
-
Hello revdjenk!
Here is the link that you ask...
http://www.zaurususergroup.com/modules.php...wdownload&cid=5 (http://www.zaurususergroup.com/modules.php?op=modload&name=UpDownload&file=index&req=viewdownload&cid=5)
Im trying it by now, but is unsatble, after a reset, the filesystem crash, in had my Z5500 on stand by in hope that the fix for this unstable behavoir could be found.... Sadly, I cant help toomuch because Im not a programer...
Best regards and luck!
Xaser
-
Ok, coulde some please tell me what a \"NPC card\" is. Am assumeing that it is a wirless card and or blue touth. Now I have been using the async kernel since before it was posted. I have yet to have any problumes (that i did not couse). And form what I understand CONFIG_FS_SYNC forces the kernel to sync during wirites. Now how this affects a network and or blue touth card, am not sure. As for the serial_cs module I have goten errors on a 2.4.18 kernel on my laptop. By the way could someone please tell me what a Bluez driver is for.
JP
-
joshp - I can\'t answer your question regarding the NPC card, but I had the problems with my bluetooth card. Namely, with tkcROM 2.0alpha3 I have not had any problems with getting the bluetooth card Bluez drivers to work properly. However, just after installing the ASYNCIO kernel, when I tried to install the same Bluez driver I have the errors that I mentioned in a previous thread with the serial_cs module. Once I switched back to the normal tkcROM zImage and flashed, the Bluez driver install did not cause any errors again.
Again, I\'m not sure what\'s causing the problems, but since the only variable that I changed was the kernel I must guess that it is causing the issue. If anybody has any ideas on some good testing/possible resolutions to try, please let me know-
Nate
-
Joshp - Its a Network Phone Card (NPC) by Aerlink (actually Socket) the connects to cell phones and creates a serial interface similar to what a bluetooth card does.
n8a - I have a feeling our problems are one in the same as my card must be using the serial_cs module. I\'m just not sure how to validate this though. One difference is that mine installs without error. Maybe someone can find a fix in this module. Or is there another one floating around that I haven\'t yet tried?
?
-
n8a - I have a feeling our problems are one in the same as my card must be using the serial_cs module. I\'m just not sure how to validate this though. One difference is that mine installs without error. Maybe someone can find a fix in this module. Or is there another one floating around that I haven\'t yet tried?
?
This is kinda the blind leading the blind, but if you want to find out if there are errors with the module:
# modprobe serial_cs
When I do that (see my old post in this thread), it outputs a bunch of error messages. I\'m trying to learn more about the modules, testing/changing them, the custom kernels, etc., but there\'s just so much to learn!
-
thanks all!
I was searching in the wrong places!
-
Any ideas here, Derek? I\'d like to get this working, but replacing the existing driver with another copy of serial_cs.o that I have (then doing a depmod -a and modprobe) did not seem to work, so I\'m off to the original tkcROM zImage for now...
Sorry it took a while for me to get back to you on this on, I was out of town for a few days.
It looks like the serial driver is compiled into the tkc kernel. When I compiled the async io kernel, I left most of the config options set to default, which ends up putting the serial driver as a module.
I\'ve attached the serail.o module, try insmoding this one before loading up your serial_cs.o modules and let me know if it works.
Anyone else who\'s having similar errors (symbol not found), let me know, and I\'ll add those modules to my list of ones that need to be compiled into the kernel.
-
Hey Derek Would you mind sending me your .config file for you async kernel.
thanks
JP
-
derekp - Sorry, my understanding of Linux isn\'t as great as I would like, but I\'m learning. How do I use your serial.o module?
-
thanks, derek. I\'ll have to try it after my vacation, as I\'m leaving for Lake Tahoe and I have everything working as I need it now. Not a good time to start testing things out, unfortunately...
I will try it with your async-io kernel first, then with the home on SD along with that kernel.
Another thing too, Derek - I reloaded the tkcROM 2.0 alpha3 zimage and initrd.bin, and then simply tried out the home on SD without the asyncio kernel but with the -f option. For some reason, each time I would reboot, it would give a TON of error messages, which would last about 5-10 minutes. Then, finally it would boot up. I don\'t know if you\'ve encountered that, but it made reboots brutal. If you haven\'t experienced that, then perhaps it was something that I did (it was a while ago, so I dont\' fully remember unfortunately).
-
Woohoo, the serial.o fix works great! And I got it to load automatically when serial_cs.o loads by modifying the modules.dep file.
-
Hello!
Well, about the async kernel,I have the same trouble but with my modem, this is the issues:
1) My Targus Pocket Modem 56k v.90 works fine with others roms but with the async it had the same bug, I made the settings but no connections icon appears, only appears the icon if I made an IR dialup connection BUT in that case, DONT appears the modem connection and only appears the IR Dialup connection.
2) The IR dialup connection works fine, so, please maintain it working when fix the other connections issues.
But, all around the async kernel with home on sd are GREAT!... so, thanks very much to all the good people that are making it working!
Best regards!
-
Bad news on my end. My Simpletech SD does not like to be ext2 and treated as home. I get similar findings as n8a gets with his SanDisk. Oh well... just so you know, Derek, it all looks good and runs fine until you suspend!
I\'ll have to break down and get a Lexar! I want to run KO-PI!
-
Revdjenk, there\'s another thread around here on SD card speed, where they were talking about an alternate SD driver. It\'s available under the downloads section, it seems to solve a bunch of problems. Try it and let me know if it solves your problems.
-
eww.. thanks for the heads up.. was just getting ready to try this kernel myself..
Well, as much fun as it\'s been to use the asyncio kernel, I just encountered a dealbreaker... at least for the present. It seems that the asyncio kernel has affected the serial_cs.o, to the effect that I get the following messages when installing bluetooth (as usual on tkcROM):
<code snip>
Any ideas here, Derek? I\'d like to get this working, but replacing the existing driver with another copy of serial_cs.o that I have (then doing a depmod -a and modprobe) did not seem to work, so I\'m off to the original tkcROM zImage for now...
-
I am using a sandisk sd card and the tkrom a3 with the prep-home script and it has been work great for about a week now no problems at all and witht he sd mounted via loopback I cannot really tell any difference from using main memory for /home. Thanks for a great script.
Colin
-
It looks like the serial driver is compiled into the tkc kernel. When I compiled the async io kernel, I left most of the config options set to default, which ends up putting the serial driver as a module.
I\'ve attached the serail.o module, try insmoding this one before loading up your serial_cs.o modules and let me know if it works.
derek,
I have the file and finally have my 5500 back in the configuration to try this out, but I\'m not sure of how to insmod the serial.o file. I have copied the file to the following directory:
# pwd
/home/root/modules/2.4.18-rmk7-pxa3-embedix/pcmcia
# ls
memory_cs.o prism2_cs.o serial_cs.o spectrum_cs.o
orinoco_cs.o serial.o sharpzdc_cs.o
#
I then did # insmod serial.o, which just returned me to the prompt. What can I do to get this to work as you explained above? Thanks in advance for the baby steps
-
n8a - It took me a while, but I figured it out. This is what I did:
insmod serial.o
insmod serial_cs.o
Installing serial.o first loads the symbols required to load serial_cs.o. You can do a lsmod to see what modules are installed. If everything works after this let me know. I figured out how to edit the modules file so that this loads automatically.
-
Not sure if others have the same experience, but the my Netgear MA701 wasn\'t recognised by the async kernel. (cardinfo would return a result, but there was no kernel output to dmesg on card insert).
Swapped in the \'standard\' kernel that ships with TKC ROM and the card works fine.
-
Thanks a ton, agosine. However, this is what I\'m getting:
# ls
memory_cs.o prism2_cs.o serial_cs.o spectrum_cs.o
orinoco_cs.o serial.o sharpzdc_cs.o
# insmod serial.o
# insmod serial_cs.o
# /etc/rc.d/init.d/bluetooth restart
Shutting down Bluetooth... Can\'t open RFCOMM control socket: Address family not supported by protocol
Done.
Starting Bluetooth... modprobe: line 1: Invalid dependency
1à Bà 0 â Ãåõÿë
modprobe: line 1: Invalid dependency
1à Bà 0 â Ãåõÿë
Can\'t set line discipline: Invalid argument
Can\'t initialize device: Invalid argument
Can\'t open RFCOMM control socket: Address family not supported by protocol
Done.
# /etc/rc.d/init.d/pcmcia restart
# /etc/rc.d/init.d/bluetooth restart
Shutting down Bluetooth... Can\'t open RFCOMM control socket: Address family not supported by protocol
Done.
Starting Bluetooth... modprobe: line 1: Invalid dependency
1à Bà 0 â Ãåõÿë
modprobe: line 1: Invalid dependency
1à Bà 0 â Ãåõÿë
Can\'t get port settings: Input/output error
Can\'t initialize device: Input/output error
Can\'t open RFCOMM control socket: Address family not supported by protocol
Done.
# lsmod
Module Size Used by
serial_cs 4640 0 (unused)
serial 25504 0 [serial_cs]
sa1100_bi 23088 0 (unused)
net_fd 16688 1
usbdcore 22592 0 [sa1100_bi net_fd]
usbdmonitor 5488 0
devinfo 2912 0 (unused)
sharp_mmcsd_m 27408 2
# modprobe serial
modprobe: line 1: Invalid dependency
1à Bà 0 â Ãåõÿë
# modprobe serial_cs
modprobe: line 1: Invalid dependency
1à Bà 0 â Ãåõÿë
#
Obviously, I don\'t really know what I\'m doing with these modules... Time for me to try to research this more. As always, I welcome any tips!
-
OK, so I just remembered to do a \"depmod -a\", and thus I no longer have the crazy modprobe results:
# depmod -a
# modprobe serial_cs
# modprobe serial
# /etc/rc.d/init.d/bluetooth restart
Shutting down Bluetooth... Can\'t open RFCOMM control socket: Address family not supported by protocol
Done.
Starting Bluetooth... Can\'t get port settings: Input/output error
Can\'t initialize device: Input/output error
Done.
# hciconfig
#
Still ain\'t working...
-
n8a - Glad I could help a little. If I come across anything more I\'ll let you know.
-
n8a,
Here\'s a new copy of the async kernel.
What I did this time dump /proc/ksyms from both the standard tkcrom kernel, and the async kernel, then started tweeking the async kernel until the kernel symbols match between the two. What this has is CONFIG_SERIAL and CONFIG_SERIAL_COLLIE turned on, and CONFIG_SERIAL_8250 turned off. Also, the Aironet driver is turned on. At this point, the only apparent difference is the tkcrom kernel has two ksyms related to the Raylink driver, which I couldn\'t find the kernel option to turn on. I don\'t think that one is important.
Let me know if you have better luck with this kernel.
-
That did it, Derek! Very, very nice.
Well, I must say that I\'m finally very happy with the state of my 5500. Thanks MUCHO. I certainly want to do some dual-booting, but man, that zImage asyncio kernel makes a HUGE speed difference compared to running home-on-sd with the -f option and the normal tkcROM zImage.
The one MAJOR remaining issue is that I have rebooted the 5500 three times, with the following results:
First time, after installing a ton of apps, the system booted to this:
I had a shell and it complained that the file system was corrupt. It then gave me these options: Enter password to repair or press Control-D. Then:
1) reboot... after which it dies and can\'t be started unless I flash it again
2) I get a prompt that comes up like the following
(Repair FS) #
I ended up having to pop the battery out to get it to respond… I then see the “Generating SSH Keys…†Nice!
Second time, error messages for about 8 minutes before the startup message began…
Third time, same as the first time (again, I had installed a bunch of apps).
The good thing is that since *everything* seems to be on the SD card, once it loads up, everything is intact, including data that I’ve stored. If there is a way to remedy this unfortunate process, then this will become my hands-down favorite configuration for the 5500…
-
Well, I\'m glad that the new kernel is working for you. The filesystem errors you get on reboots worries me though. The only time I\'ve come accross that is with the modified prep-home-sd.sh that is included on the tkc-2.0alpha3 rom. That version creates the /mnt/card/rc.card script with a mkswap command at the end that turns the ramdisk into a swapfile. This of course causes the ramdisk to become corrupted after heavy application usage (including installing a bunch of packages), which will cause fsck to dump out a bunch of errors.
I know that you\'ve grabbed the newer prep-home-sd.sh script (test5) which doesn\'t have this issue, but just in case, double-check your rc.card file (on the root of the sd card), and if it contains a line \"mkswap /dev/iramdisk\" at the end of it, coment it out (along with the following swapon command).
If it isn\'t the mkswap issue, then I\'m out of ideas, as I haven\'t run accross this issue otherwise. I\'ll be at the user-group meeting on Sunday, so I can take a look then.
--derek
-
hmmm... this is what I found in /home/rc.card:
cd /
umount /home
fsck -y /dev/mmcda1
# Rename the devices. This is so the SD shows up
# as "Internal Storage" in Qtopia
mv /dev/mtdblock1 /dev/iramdisk
mv /dev/mmcda1 /dev/mmcsd1
ln -s /dev/mmcsd1 /dev/mtdblock1
mount -oasync,noatime /dev/mtdblock1 /home
mkswap /dev/iramdisk
swapon /dev/iramdisk
I just checked the version of your script that I downloaded, and it definitely ends in test5.zip. In addition, I tried to replace the script on my CF card with the script from that zip file and both files were identical down to the modified date.
So, I just comment out the last two lines and it should work fine, right? I\'ll give it a go. Out of curiosity, why did you turn the whole ramdisk into a swapfile, then specify a 20 MB swapfile when running the script? Or is the swapfile specification at install a new feature of the test5 version? At any rate, thanks again and I\'ll let you know if this solves it --
Nate
-
Let me back up a couple notches here :-)
I had originally put together the prep-home-sd script (and modified rc.sysinit script) without any swap file, then sent it into Proto to include in the tkcrom. Then we started going over ideas to improve it a bit. Proto thought it would be a good idea to then turn the ramdisk into a swap partition, since it was no longer being used for /home, so he added the mkswap & swapon to the end of the script and included that version in the tkcrom 2.0 alpha-3 release. However, since a fsck is run by rc.sysinit before the rc.card script is called, this would cause the fsck errors that you see.
Meanwhile, I had fallen off the face of the plannet (read: got bogged down with work). Later, I sat down a my orignial script (without the mkswap) and overhauled it (added a swap file (not a swap partition), moved some stuff around, etc). I\'ve been waiting to here back from Proto, but I take it that it\'s his turn to get over-loaded with non-Zaurus activities :-).
The version of the rc.card script you posted above, is not generated by the new script but is the one generated by the (old) prep-home-sd.sh script included in the tkcrom. So, one of two possibilities: 1) you probably ran the old version of the script (the one on the tkcrom) by mistake, or 2) you ran the old version originally, and for some reason the new version didn\'t overwrite the rc.card that was put on the sd previously. To make sure that you are running the right version, specify the whole path of where you put it. Also, the new version has better help (the help text should pop up if you don\'t specify any parameters). Or, a third posibility is that I upload the wrong script. Nah, that couldn\'t happen :-)
Good luck,
--derek
-
Hey, thanks for the lengthy explanation. It was not needed, but I certainly appreciate it! I\'ve noticed that in addition to the fact that I just really need to ramp up on unix skills, there\'s no way to know how many aps/fixes/etc work on the zaurus or to find a history without being a part of the development (or at least testing effort) yourself. This is partially due to the nature of such work (who likes to document), the stretched resources factor (so few here that are good developers), and the fact that we lost the devnet site, where I would desperately wanted to get the history on the tkcROM versions and many, many other things that I saw posted there long ago. *sigh*
On the bright side, it’s good to know that Proto’s alive
As a note, I did find it interesting that my previous run of the prep-home-on-sd script worked even though I was in the wrong directory! That struck me as a *little* odd! However, there were multiple times that I cd’d to the directory in which the script was located, but old script ran…
I reran the script, and after typing the full path, the prompts made me aware that I was running the correct script for the first time. I’m now installing some stuff, rebooting, using bluetooth, etc. with no probs! Thanks for the help again, Derek!
-
One thing on Unix, is that when you type in a command, it will search your path first, but won\'t look in the current directory at all (unless the current directory is in the path). So, if you want to run a script that is in the current directory, either specify the full path name, or put a \"./\" in front of the file name \"(the dot means current directory).
Glad you got it working.
-
Hello,
I have a SL5500 as the topic.
I run the script with 20mo of swap.
How can I change this size to set to the full size of ramdisk ?
In my system Info, I can see 28508 kb for Total memory and 20967kb forTotal swap.
Where is my 64mo of ramdisk ?
Thx
-
Hello,
I have a SL5500 as the topic.
I run the script with 20mo of swap.
How can I change this size to set to the full size of ramdisk ?
In my system Info, I can see 28508 kb for Total memory and 20967kb forTotal swap.
Where is my 64mo of ramdisk ?
Thx
The way the kernel is configured the system gets 16mb for mem 16mb for the root filesystem and 32mb for the /home filesystem. So bascliy the zaurus looks like this
16mb mem
16mb / #Mounted as cramfs
32 mb /home #Mounted as ext2(I think)
In order to use the full 32mb you would have to remake the swap file. Whan booted up into tkc rom open you console and exec the floweing:
cd /mnt/ramdisk
swapoff swapfile
rm swapfile
dd if=/dev/zero of=swapfile bs=1024k count=32768
mkswap swapfile
swapon swapfile
You should now have a 32mb swap file. Note that you may have to change around the count=32768 as that is the true count for 32mb, it may help to exec \"df /mnt/ramdisk\" to get the true size of the internel mem. Hope this helps.
JP
P.S. You should be able to delate any thing on your internel ramdisk with the expecon of the var dir. Because if you deleate it the Z will hang on suspend.
-
I have been running with the /home on SD with alpha3 for several months, but have just found a little snag on my setup.
Case 1: boot with neither SD or CF card - works fine and uses standard ROM.
Case 2: boot with both SD and CF cards in - works fine and uses /home on SD.
Case 3: boot with SD in but no CF fails. It gets as far as the Kompany splash screen, stays for a while, drops to a Wait 5,4,3,2,1 prompt and then goes back to the Kompany splash screen and then repeats ad nauseam.
I am trying to debug what may be happening. I have looked at rc.card. rc.sysinit - no clues. I tried going to a Linux prompt by pressing / at the Wait prompt and entered:
survive -l 6 /sbin/launchas per /etc/inittab; but it just drops out the a Wait prompt after showing the splash screen for a while.
Any tips on how to debug would be appreciated.
-
Could anyone point me to the async kernal for TKRom 2 alpha3, please? I have installed the one from the ROM, and have many problems.
If DerekP happens to read this, I have used your recommendation, i.e. -s 20 -t -c -f ; am I right in thinking I should just use this minus the -f with the new kernal? Also, could I just flash the kernal, and is there some way to remove the -f without re-flashing the whole ROM?
I hope that is all clear and makes sense - I have never used the terminal before, and am gleaning what I can from the forum - had a fair amount of success so far!
Many thanks to anyone that can help.
-
sirhc7,
I believe that you type prep-home-sd.sh -i to return to defaults.
Now whether that takes you back to a blank state, I do not know; but I had read that in derekp's initial explanation.
-
sirhc7,
I believe that you type prep-home-sd.sh -i to return to defaults.
Now whether that takes you back to a blank state, I do not know; but I had read that in derekp's initial explanation.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=90682\"][{POST_SNAPBACK}][/a][/div]
Thanks, Doug.
I'm afraid I've given up on tkrom 2 - couldn't get it to be stable; shame, it was excellent in every other way. I ended up using the Hybrid ROM with Qtopia 1.6.2, and it's almost perfect.
Cheers,
Chris.
-
I'm afraid I've given up on tkrom 2 - couldn't get it to be stable; shame, it was excellent in every other way. I ended up using the Hybrid ROM with Qtopia 1.6.2, and it's almost perfect.
Cheers,
Hi Chris.
Have you gotten the hancom apps to work with Hybrid ROM and Qtopia 1.6.2? I've ended up the same as you and keep coming back to the hybrid, but I'm still using Qtopia 1.5.4 because of the spreadsheet, and word programs.
Thanks
-
Hello!
Well, about the async kernel,I have the same trouble but with my modem, this is the issues:
1) My Targus Pocket Modem 56k v.90 works fine with others roms but with the async it had the same bug, I made the settings but no connections icon appears, only appears the icon if I made an IR dialup connection BUT in that case, DONT appears the modem connection and only appears the IR Dialup connection.
2) The IR dialup connection works fine, so, please maintain it working when fix the other connections issues.
But, all around the async kernel with home on sd are GREAT!... so, thanks very much to all the good people that are making it working!
Best regards!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=16229\"][{POST_SNAPBACK}][/a][/div]
Coming back to the TKompany ROM after a long time away playing with OZ. I have the 32/30 image with home on my SD and have updated the Kernel Cacko's.
Got most of what i want done but am struggling with syncing. Could someone please clarify which version of Intellisync to use. Is it the original (1.43) or the updated vrsion that shipped with the 3.13 ROM?
many thanks
-
Airwolf said:
"Got most of what i want done but am struggling with syncing. Could someone please clarify which version of Intellisync to use. Is it the original (1.43) or the updated vrsion that shipped with the 3.13 ROM?"
Hi Airwolf, you need the version of Intellisync that comes with the upgrade to 3.13 Sharp rom.
I've had very litle problem running this version of TKC and I've found that Treeexplorer works very nicely with it as does kdepimpi. The combination of home on SD and those two apps makes my 5500 a much more useful object. However, I spend much more time on my 860 these days.
I did try the Cacko kernel and the Async, but seemed to find a few problems and irritations so went back to the alpha kernel.
Cheers
-
Can I ask where you got the tkRom files from??
I have been trying to install this for about a week.
I got the files from
http://kflog.org/~axel/GPS-CF_HOW_TO-TKROM...pha3.HowTo.html (http://kflog.org/~axel/GPS-CF_HOW_TO-TKROM2.0Alpha3/TkRom-2.0-Alpha3.HowTo.html)
The site has instructions for installing and the files for the Alpha3 rom. But when I try loading these to my CF card and flashing as per the instructions the mail and power lights flash instead of staying on and the only way to stop the process is to perform a hard reset. So I'm not sure if it's the files or me
Any help or guidance would be really welcome.
-
Can I ask where you got the tkRom files from??
I have been trying to install this for about a week.
I got the files from
http://kflog.org/~axel/GPS-CF_HOW_TO-TKROM...pha3.HowTo.html (http://kflog.org/~axel/GPS-CF_HOW_TO-TKROM2.0Alpha3/TkRom-2.0-Alpha3.HowTo.html)
The site has instructions for installing and the files for the Alpha3 rom. But when I try loading these to my CF card and flashing as per the instructions the mail and power lights flash instead of staying on and the only way to stop the process is to perform a hard reset. So I'm not sure if it's the files or me
Any help or guidance would be really welcome.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=94782\")
hi JacX
got mine form here
[a href=\"http://www.zaurususergroup.org/UpDownload+index-req-viewsdownload-sid-31.phtml]http://www.zaurususergroup.org/UpDownload+...ad-sid-31.phtml[/url]
You will need the alpha initrd and a zImage file.
Make sure you CF card is formatted as windows FAT (NOT FAT32). Press the C and D buttons at the same time as the reset button at the back near the battery. Also remember to press the reset button again after the flash has completed
if you are still having problems post again
-
Many thanks for that airwolf.
I'll have a go tonight and let you know.
-
Airwolf said:
"Got most of what i want done but am struggling with syncing. Could someone please clarify which version of Intellisync to use. Is it the original (1.43) or the updated vrsion that shipped with the 3.13 ROM?"
Hi Airwolf, you need the version of Intellisync that comes with the upgrade to 3.13 Sharp rom.
I've had very litle problem running this version of TKC and I've found that Treeexplorer works very nicely with it as does kdepimpi. The combination of home on SD and those two apps makes my 5500 a much more useful object. However, I spend much more time on my 860 these days.
I did try the Cacko kernel and the Async, but seemed to find a few problems and irritations so went back to the alpha kernel.
Cheers
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=94750\")
hey Tux
forgot to ask.... I downloaded this [a href=\"http://prdownloads.sourceforge.net/kdepimpi/kdepim_2.2.3_for_SharpRom.ipk.zip?download]http://prdownloads.sourceforge.net/kdepimp...pk.zip?download[/url]
but when i try to install any of the files i get an error message "The filename of this package includes character this application can't handle. Please change the filename and retry install"
any ideas
thanks
-
I have just installed this ROM, with the home on SD, and the async kernel.
It seems to be working a treat, however, my wireless network card no longer works. It worked fine on Sharp ROM 2.86 (I think) and 3.13 without any tweaking of the /etc/pcmcia/wlan-ng.conf file, but it now refuses to work with tkrom.
The device does detect a card, and labels it as an Intersil PRISM2 11Mbps card, but when I go into the network settings, it says there is no network available.
I tried adding the card manually to the wlan-ng.conf file, but that doesn't work either.
I don't want to go back to the Sharp ROM, as this one is great...apart from this problem
All input appreciated
Ventmore
-
Well...I've just gone trhough the whole process again, and this time it is working perfectly.
This time, I installed the wireless card after the initial flash. It was working fine, so I went ahead and flashed the async kernel. I checked the card again, and again it worked. After that, as the card was working, I ran:
prep-home-sd.sh -s 20 -t -c
Success!!!
The only thing I did differently, was to run the prep script with -c instead of -i. Also, I haven't reset again to clear the RAM out, but I don't think that should make a difference...in fact...I'll try that now.
Still working, and all of my apps are still intact
Cheers
Ventmore
-
Ok...I've lost it again. The card shows that it is recognised, as usual, but no network connection is hown, and if I run opera, it pops a net connection box, but there is nothing in the list.
Also, when I insert the card now, the light comes on and stays on, whereas, when it's working properly, the light only comes on when connected.
Any help would be very welcome
Ventmore
-
I know this is an older thread, but I thought I'ld let everyone know that I took some time to mess w/ my old 5500 last night and I was successful in taking the /root/etc/rc.d/rc.sysinit script from the TKC ROM 2.0 Alpha 3 and modifying both the original TKC 1.0 ROM and the Sharp 3.13 ROM w/ the script. The process was pretty quick and easy. While doing it I went ahead and replaced the /lib/modules.rom/2.4.18-rmk7-pxa3-embedix/kernel/drivers/block/sharp_mmcsd_m.o module w/ the patched one that is also mentioned here in the thread. My reasoning for doing this is, I never had much luck w/ the Cacko ROM/Kernel being stable w/ home on my sd card. The TKC ROM 2 has always ran stable. Anyway, I was getting errors when trying to use tun.o and ipsec.o modules w/ the TKC kernel. Both worked fine w/ the Original Sharp Kernel/3.13 ROM. So, now I have the 3.13 ROM running vpnc w/ no problems and still have my /home on my SD card. Everything is stable. Besides, re-installing alot of packages, I'm pretty happy using the stock Sharp ROM for now, but I'm going to revisit this area eventually and make an new updated ROM for my 5500. If anyone is interested in the initrd.bin files, feel free to drop me an email. I usually read the site daily when I can, but hardly ever post. I haven't used my Z in awhile because of work, but I've been growing tired of my Palm PDA's again & have a re-newed interest in the Z. In fact I just bought a 5600 today & will hopefully have 6000 this week. I'm also looking forward to getting a 3200 to replace the 3000 I sold to loc4me last year along w/ my Palm LifeDrive and a TX. He just got those not too long ago and has been having fun w/ lately. :-)
-
I know this is an older thread, but I thought I'ld let everyone know that I took some time to mess w/ my old 5500 last night and I was successful in taking the /root/etc/rc.d/rc.sysinit script from the TKC ROM 2.0 Alpha 3 and modifying both the original TKC 1.0 ROM and the Sharp 3.13 ROM w/ the script. The process was pretty quick and easy. While doing it I went ahead and replaced the /lib/modules.rom/2.4.18-rmk7-pxa3-embedix/kernel/drivers/block/sharp_mmcsd_m.o module w/ the patched one that is also mentioned here in the thread. My reasoning for doing this is, I never had much luck w/ the Cacko ROM/Kernel being stable w/ home on my sd card. The TKC ROM 2 has always ran stable. Anyway, I was getting errors when trying to use tun.o and ipsec.o modules w/ the TKC kernel. Both worked fine w/ the Original Sharp Kernel/3.13 ROM. So, now I have the 3.13 ROM running vpnc w/ no problems and still have my /home on my SD card. Everything is stable. Besides, re-installing alot of packages, I'm pretty happy using the stock Sharp ROM for now, but I'm going to revisit this area eventually and make an new updated ROM for my 5500. If anyone is interested in the initrd.bin files, feel free to drop me an email. I usually read the site daily when I can, but hardly ever post. I haven't used my Z in awhile because of work, but I've been growing tired of my Palm PDA's again & have a re-newed interest in the Z. In fact I just bought a 5600 today & will hopefully have 6000 this week. I'm also looking forward to getting a 3200 to replace the 3000 I sold to loc4me last year along w/ my Palm LifeDrive and a TX. He just got those not too long ago and has been having fun w/ lately. :-)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=146754\"][{POST_SNAPBACK}][/a][/div]
I'd certainly be interested in a new ROM for the 5500, looks like things have stagnated a bit... all the alternatives to OZ are at least 2 years old. In fact, I just installed Cacko 2.4.18 w/1.6.2 yesterday as I'm looking for a more stable alternative to OZ, but of course it's not a pretty/functional and I've yet to get some useful IPKs together for pdf reading and opera.
-
Just thought I'd bump this thread up a bit.
The threads about using the tweaked Sharp and TKC roms that have home on sd with the >2gb drivers seem to have made it more topical.
(Oh and thanks very much to kb7sqi for the work and the product!)
If any admin reads this and has the time would it be possible to move this thread to the 5500 general forum?
If that happened would it be possible to make it a sticky thread?
If that happened perhaps the two other threads mentioned above could also be made sticky?
Cheers