OESF Portables Forum
Everything Else => Sharp Zaurus => Model Specific Forums => Distros, Development, and Model Specific Forums => Archived Forums => 5x00 General discussions => Topic started by: Ethereal on March 01, 2004, 10:46:17 pm
-
Hi all.
Tumnus\' new special kernel, which opens up the possibility of overclocking, leaves off the pre-emptive patch (with its module compatibility woes), and frees us from the chains of PXA250 cache erata, is now available (http://www.zaurususergroup.com/modules.php?op=modload&name=UpDownload&file=index&req=viewsdownload&sid=53). (It\'s version 1.3)
My Dhrystone results are around 230 VAX MIPS, up from 195 with the stock 1.32 ROM...and that\'s with no overclock! (And BlueZ, including the high-speed drivers--70 kbps with Sprint PCS Vision!--works perfectly!)
Thanks tumnus...and ced...and Maslovsky...and everyone!
-
Where is everyone getting the Dhrystone binary (or even better source) from?
Si
-
http://laurent.lieben.free.fr/zaurus_kernel/dhry21 (http://laurent.lieben.free.fr/zaurus_kernel/dhry21)
-
From what i read in the description it does not \"leave off\" the pre-emp patch but has it included. Am i reading this wrong? How else could you get it to run at 400? Using the pre-emp w/o overclock i get vax mips 231.598
-
The pre-emptive patch does very little for the performance. Only v1.3 of the Special Kernel should be used now, which does NOT include the pre-emptive patch. The speed increase is due to a workaround for a bug in the PXA250 CPU being turned off. The workaround that is in the default Sharp ROMs effectively halves the speed of the CPU.
-
Greetings. Once again, thanks for working on these patches. In another thread I reported my problem with the pre-emptive standard kernel (v1.2) and disruption of battery charging. I thought I\'d share my observations with the latest special kernel patch (v1.3) since my Z seems to be an outlier. The good news: 1) it appears that the pre-emptive patch was the cause of my battery charging situation as it is no longer a problem with the special kernel, and 2) FB VNC Server (as well as VNC Viewer) works fine. The bad news: when bringing it out of suspend, the CF card is dropped from the Files tab (although the CF card icon is still visible in the system tray).
Dhrystone Benchmark, VAX MIPS rating (no overclocking):
147.045 (v1.32 ROM w/o patch and not running VNC server)
184.311 (v1.32 ROM w/ patch and running VNC server)
226.141 (v1.32 ROM w/ patch and not running VNC server)
Unfortunately, I have decided to return to the basic standard kernel since my Z behaves out of the norm and, more importantly, I perceived no speed increase of the applications I use most.
-
Hi,
using zynergy which is basically sharp rom kernel with some extra packages thrown in.
Im trying to use the new kernel 1.3 from tumnus for wireless and overclocking etc
1) I put zImage.bin and updater.sh on my cf card.
2) I shutdown, and do the battery stuff, and go to maint mode
3) Option 4 for update from cf.
4) It starts to boot, then says cannot loc devinfo
5) i get cf updater, with reset
6) I go back to battery and reboot .
7) System restarts
8) I am sure it doesnt have new kernel , cat /proc/cpuinfo, go to systeminfo etc
9) Also , tried using dhry21 (to check speeds)
before it was
500000 iterations
145.103 with ssh
147.832 without ssh
146.xxx with new kernel (nowhere near the higher #s)
Im assuming you dont have to do a format after the update, just an update, right? Format is if you replace the entire filesystem with initrd.
What might I be doing wrong?
Thank you
-
Did you see a progress indicator for zImage.bin when it was doing the update? If not then you must have either got the filename wrong (I think capitalisation may be important) or your CF card is not FAT16 (msdos FAT) formatted. Other than that you are using the correct procedure.
BTW, to tell if you have the special kernel from the ZUG downloads, do \'cat /proc/version\'. In the output from that you should see colin@paravel compiled it, which is me on my home PC.
-
Hi Tumnus,
Thanks for the reply. There was definitely no progress indicator. Cat /prov/version didnt have that, nor were there wireless extensions and the speed test failed too, so Im sure it didnt update.
In my /mnt/cf I have:
zImage.bin
updater.sh
dhrv.res
Documents and qtpalmtop directories.
cf card definitely fat16 as I flashed the zynergy rom with this. I did an update and format then, but just the update here, as format would initialize the entire filesystem
So, either I am missing something or else you can\'t do the kernel patch on this rom, but that wouldn\'t make sense as it is a sharp rom, and one would expect that it would do the update, and then have errors on bootup right?
Thank you.
-
1) I put zImage.bin and updater.sh on my cf card.
Guest
If you use the Sharp updater.sh you have to name it zImage.bin
If you use the Zynergy updater.sh you have to name it zImage
Greg
-
Greg,
This is interesting.. I will try this out and report back to you.
Thank you and Tumnus for your quick replies.
-
So ... whats the best pre-emptive kernel to run on a 5500 these days? Does someone have 2.6 up and running yet?
-
Hmmm not able to get to maint mode now. I shutdown then try to reset battery but while its booting it wont allow me to. Strange.. does it have to be on ac if the battery is near 100%?
How do you do the shutdown ? Go to gui shutdown and then when it starts back up do both buttons?
-
How do you do the shutdown ? Go to gui shutdown and then when it starts back up do both buttons?
Follow Sharps instructions except only use the 2 files needed for kernel update (no initrd.bin). You must hard reset first.
Instructions:
http://www.myzaurus.com/ROMupdate6.asp (http://www.myzaurus.com/ROMupdate6.asp)
Greg
-
Hi,
Yes i understood that. I usually just did a shutdown, and when it started to boot , hit the replace battery and took off cover, this time it didnt take.
So, easiest way is console, then halt.. When it shuts off, do what you need to do. I know only the 2 files, and also not to do a format, just an update......
-
I usually just did a shutdown, and when it started to boot , hit the replace battery and took off cover, this time it didnt take.
I\'m not sure what you are doing here?
Just do a hard reset, then bring up maint. menu. Can you bring up maint. menu after hard reset?
Greg
-
not to get off subject, but where do you find a sprint pcs bluetooth phone. I\'m about to leave sprint due to a lack of such a device.
thanks
-
How about adding CONFIG_FS_SYNC fix to the special kernel. Will it make this
kernel more useable?
-
The Z needs to be OFF, not rebooted, then do the battery/reset thing, and then hold down the OK key while turning it on. I was confused by this at first as well. Also, pay attention to the previous post about the name of the zImage and updater files, this definetly matters, i made the same mistake.
-
I shut it off with halt.. Then update. Had zImage and updater.sh on cf card. Same situation. Kernel shows yamade@yampc but speed with dhry21 is 147.296 so im very sure it didnt apply the kernel. I may look for a sharp updater , and rename back to zImage.bin, but it didnt work this way...
-
The pre-emptive patch does very little for the performance. Only v1.3 of the Special Kernel should be used now, which does NOT include the pre-emptive patch. The speed increase is due to a workaround for a bug in the PXA250 CPU being turned off. The workaround that is in the default Sharp ROMs effectively halves the speed of the CPU.
Thanks... this kernel works for me and the touch screen still works though it did need recalibrating. Even Kismet seems to be working in some fashion now.
-
Hey...
Bravo.. it worked. User stupidity (mine) , well hard to read screen and when I had copied zImage to this name , it must have gotten some unreadable character in there, did a mv zI* zImage and it worked.
Did need to recalibrate, no biggie.
Now.. the kernel says colin@paravel I think that is what Tumnus had posted. Good. This time when doing kernel flash it said success afterwards never got that before.
Ran dhry21 and speed now 229.497 instead of 147.296. Is this the appx mips speed? If so, UGH. The unit is supposed to be 400, and it is still only a bit more than 1/2 of that. Or maybe cat/cpuinfo says 397 bogus mips is more accurate?
I think I recall the program to change clock speed and I will try that, dont make it higher than 487 though , right. Is above all true?
Great job on kernel, Tumnus!!!
-
It didnt have wireless extensions i have wpc12 wireless card. Anyone gotten wireless extensions to work?
-
It didnt have wireless extensions i have wpc12 wireless card. Anyone gotten wireless extensions to work?
It works for me with a Symbol card. I didn\'t find many references to the wpc12 card with Google, but I did find this quote about the chipset it uses:
{
FCCID PKW-WPC11-V29 (approved 11/7/2002) uses ISL3873B or Prism2.5
FCCID PKW-WPC11-V31 (approved 7/23/2002) uses ISL3871xxx or Prism3
FCCID PKW-WPC11-V3 (approved 2/1/2002) uses \"
The PKW-WPC12 uses the TI ACX100 and to my knowledge never saw the light
of day.
}
If it\'s not based on the Prism chipset, you may have a hard time finding support for it...
-
So, how did you get wireless extensions to work with sharp kernel?
The linksys card is a prism based card.
-
So, how did you get wireless extensions to work with sharp kernel?
The linksys card is a prism based card.
\"It just works!\"
Sharp ROM, Special kernel V1.3.
Wireless worked with stock Sharp ROM, but Kismet did not.
Kismet works with the special kernel.
The only other problem that I had is making sure all of the
associated configuration files were present in /etc/pcmcia ,
i.e.:
spectrum
spectrum.conf
wireless
wireless.opts
wlan-ng
wlan-ng.conf
wlan-ng.opts
-
Hi,
Not wireless, wireless extensions which is a prereq for wellenreiter.
Wireless worked from beginning, and I didnt have much trouble with kismet. Trying to get wellenreiter to work with tumnus sharp kernel.
From what I read, wellenreiter needs wireless extensions to run.
If this is not the case, I\'d love to know how to do it. Otherwise, I need to either find a kernel with wireless extensions and the errata fix, or recompile a kernel and add it.
Thanks
-
Wellenreiter didn\'t work? I think it should work if you made kismet work.
I believe that sharp/special kernels have wireless extension. kismet/wellenreiter
is another story because it requires monitor mode. But once you have kismet
work, wellenreiter should work.
-
I\'m going to look at the post about wellenreiter on qtopia. However, from previous posts it was mentioned that you needed to get wireless extensions to work to get Wellenreiter going.
Wireless extensions iwconfig is not enabled on sharp roms, or on tumnus rom. I will post my success or failure after I try offroadgeeks post about this.
Much thanks
-
Yes, Wellenreiter needs wireless extension. So does Kismet.
Type \'iwpriv eth0\' from comman line. When you see \"monitor\" in the list,
Kismet/Wellenreiter is highly likely to work fine.
-
For those that were able to flash the newer kernerl, can you list what updater file you used? I\'ve downloaded the zynergy version and tried to flash the kernel as both zImage and zImage.bin. Another thing I noticed, when I download the kernel windows saves it as a bin file. So I name it zImage, thinking that the full name is zImage.bin. But the flash does not recognize the file. Interestingly, when I unpack the zynergy file, the zImage has no extension. Windows recognizes it as a file, vice a .bin.
Any help?
-
For those that were able to flash the newer kernerl, can you list what updater file you used? I\'ve downloaded the zynergy version and tried to flash the kernel as both zImage and zImage.bin. Another thing I noticed, when I download the kernel windows saves it as a bin file. So I name it zImage, thinking that the full name is zImage.bin. But the flash does not recognize the file. Interestingly, when I unpack the zynergy file, the zImage has no extension. Windows recognizes it as a file, vice a .bin.
I used update.sh from the Sharp 1.32 ROM update. Tried Zynergy some time ago and while it looked good, a number of things didn\'t seem to work quite right.
-
Well, that seemed to do the trick, sorta. I got the thing to appear to update (no progress dots, but it said it was updated and showed the Success! words).
However, now when I cat /proc/version it still says the old kernel info and yamade@yampc. Thoughts?
Thanks
-
Well, that seemed to do the trick, sorta. I got the thing to appear to update (no progress dots, but it said it was updated and showed the Success! words).
However, now when I cat /proc/version it still says the old kernel info and yamade@yampc.
That\'s not the right kernel then. Make sure the kernel is named zImage.bin (case-sensitive!) and try again. You should see progress dots too.
-
This is the one I downloaded from the download section, said it was ver 1.3: zImage_Special5600_No_Preemptive_No_Overclock-c860ROMv1.10. Rename to zImage.bin and put on CF with Sharp\'s updater.sh. Same result as before. Curiously, when I unzipped Sharp\'s package there was a file called mversion.bin. Do I need to mess with this? Nerver had to in the past.
-
This is the one I downloaded from the download section, said it was ver 1.3: zImage_Special5600_No_Preemptive_No_Overclock-c860ROMv1.10. Rename to zImage.bin and put on CF with Sharp\'s updater.sh. Same result as before. Curiously, when I unzipped Sharp\'s package there was a file called mversion.bin. Do I need to mess with this? Nerver had to in the past.
Dunno... that worked for me, but I\'m using the base Sharp ROM too, where you are still using Zynergy?
I haven\'t needed any files other than update.sh and zImage.bin
-
Well, I fixed the root problem. It seems that with the Zynergy ROM the updated kernel just wouldn\'t be recognized. I had to reflash/ reformat Sharp v1.32 and then update the kernel. Too bad, now I remember why I didn\'t like Sharp all that much in the first place. Man, is it ugly! Know of any good appearance changes? I\'m going to need to start another post for that!
-
Does anyone know if the tkc roms have the workaround?
-
OK, that was a STUPID question. Nevermind.