OESF Portables Forum
Everything Else => Sharp Zaurus => Model Specific Forums => Distros, Development, and Model Specific Forums => Archived Forums => 6000 - Tosa => Topic started by: xjqian on November 15, 2007, 08:11:25 am
-
Get it here: Get Angstrom Unstable Release for tosa (http://www.angstrom-distribution.org/unstable/images/tosa/) The latest tested release is r8 (kernel 2.6.23).
Working out-of-box
altboot (http://linuxtogo.org/gowiki/AngstromAltboot) with loopback image or direct fs
Kernel 2.6.23 (testing 2.6.24 for >= r9) Tosa kernel status from Dmitry (http://tosa.lumag.spb.ru/status.html)
Images: Opie 1.2.3 (core opie application feed (http://www.angstrom-distribution.org/repo/?action=section§ion=opie), other opie or qt applications not in the feed yet) and GPE 2.8 (x11-image) with match-box as default WM
Keyboard (keymap changed in 2.6.24)
Internal Wifi (wlan-ng-modules-usb 2.8 (http://ftp://ftp.linux-wlan.org/pub/linux-wlan-ng/README)) 802.11b WEP only, no WPA (http://ftp://ftp.linux-wlan.org/pub/linux-wlan-ng/FAQ)
SD: non-sdhc or sdhc (tested with 4GB card of both)
CF and 2nd CF on sled
OE Tosa Meta-Bug (http://bugs.openembedded.org/show_bug.cgi?id=2309)
Outstanding critical bugs:
1. suspend/resume OE bug 2134 (http://bugs.openembedded.org/show_bug.cgi?id=2134)
[Closed] 2. sound system OE bug 3518 (http://bugs.openembedded.org/show_bug.cgi?id=3518) Speaker/Headphone tested working. Mic/phone untested
Major bugs:
[Hacked kdrive in x11-image to overcome the problem, still an issue in opie-image] 1. frame buffer (a.k.a, screen corruption or the famous yellow vertical lines) : occurs "occasionally" with 2.6.23 kernel, much better than "often" with 2.6.17 kernel OE bug 490 (http://bugs.openembedded.org/show_bug.cgi?id=490)
Opie bugs: file Opie bug tracker (http://opie-bugs.oszine.de/login_page.php)
GPE bugs: file GPE bug tracker (http://bugs.linuxtogo.org/)
Kernel, roofs or packaging bugs: file OE bug tracker (http://bugs.openembedded.org/)
Not tested yet:
?USB host
?Speaker/Headphone/Headset/Mic (need to fix the alsa state in r9)
USB client
USB network
Mic (the one on the back of the device) / PhoneMic (2.5mm jack used with a headset)
etc.
-
thanks for that update!
p.s. what's the max SD/MMC memory card size it will support? 1GB? 2GB? 4GB non-sdhc? SDHC?
-
Ok that sounds good.
Wifi also works out of the box?
-
internal wifi out of box
sdhc should be working
-
internal wifi out of box
sdhc should be working
I don't suppose anyone's cracked the problem of getting WPA to work? Last I knew, only the wlan-ng driver worked and it didn't support anything other than WEP!
-
speculatrix: and this will rather never happen.
Wlan-ng driver is written in so ugly style that it will never get into mainline kernel, prism2 on usb is something which is not available on market and probably most of it's users moved to other solutions when wanted WPA (as bonus they got 802.11g chipsets).
-
speculatrix: and this will rather never happen.
Wlan-ng driver is written in so ugly style that it will never get into mainline kernel, prism2 on usb is something which is not available on market and probably most of it's users moved to other solutions when wanted WPA (as bonus they got 802.11g chipsets).
sadly, I came to accept long ago that tosa's wifi was never going to support any decent cryptographic standard, but I hoped that just possibly there'd be a glimmer of hope.
still there's always openvpn, which probably a better solution than rather crap idea of WPA-TKIP anyway!
-
For past 2,3 years I have been using PDAXRom 1.1 Beta2 on my lovely Tosa. It does everything I need it to do: play mp3 and avi, light browsing, abiword, dictionary, and viewing pdf.
I was so afraid to broke my perfectly tweaked ROM and I stopped doing any update at all. After all those time, I finally decided to move on and started experimenting again.
I guess I will give Angsrom a try and see what happens!!
-
For past 2,3 years I have been using PDAXRom 1.1 Beta2 on my lovely Tosa. It does everything I need it to do: play mp3 and avi, light browsing,
...
I guess I will give Angsrom a try and see what happens!!
if you take a NAND backup, you can go back to pdaXrom without any hassle.
-
For past 2,3 years I have been using PDAXRom 1.1 Beta2 on my lovely Tosa. It does everything I need it to do: play mp3 and avi, light browsing,
...
I guess I will give Angsrom a try and see what happens!!
if you take a NAND backup, you can go back to pdaXrom without any hassle.
Thanks. That's gonna be the project for this weekend. Hopefully most of things will work out of box.
-
[ANNC] Tosa Angstrom RC1.x (http://article.gmane.org/gmane.linux.distributions.angstrom.user/1144)
-
r8 release from the Angstrom stable branch has been released. No critical change from r2. The next big thing is to bump kernel to 2.6.24. That should solve or remedy a bunch of kernel related problems.
status updated.
-
r8 release from the Angstrom stable branch has been released. No critical change from r2. The next big thing is to bump kernel to 2.6.24. That should solve or remedy a bunch of kernel related problems.
status updated.
thanks, I will dig out my Tosa and see how far I get . When Angstrom is good enough and I can use my Tosa more, I will get a new battery. I'd like to use it as an in-car media player (with a wireless hard drive) and to run tomtom,!
-
thanks, I will dig out my Tosa and see how far I get . When Angstrom is good enough and I can use my Tosa more, I will get a new battery. I'd like to use it as an in-car media player (with a wireless hard drive) and to run tomtom,!
Please skip r8 and test r9 with 2.6.24 kernel.
-
thanks, I will dig out my Tosa and see how far I get . When Angstrom is good enough and I can use my Tosa more, I will get a new battery. I'd like to use it as an in-car media player (with a wireless hard drive) and to run tomtom,!
Please skip r8 and test r9 with 2.6.24 kernel.
is there a decent browser working in Angstrom on 6k?
-
thanks, I will dig out my Tosa and see how far I get . When Angstrom is good enough and I can use my Tosa more, I will get a new battery. I'd like to use it as an in-car media player (with a wireless hard drive) and to run tomtom,!
Please skip r8 and test r9 with 2.6.24 kernel.
sorry r9 with 2.6.24 kernel is not bootable right now. please test r8 instead.
-
is there a decent browser working in Angstrom on 6k?
in opie, bluelightening is working with konqueror-embedded upstream to get qt2 patches upstream.
in x11, there are couple of options: links-x11, netsurf, minimo, gpe-mini-browser and openmoko-browser2
I've used minimo which works very well on tosa (except the FN key is borken), I've heard netfurf is also a good alternative. personally, I don't like gpe-mini-browser. no experience with openmoko-browser (there is demo on youtube though.
-
I tried the r17, and got an error right at start-up. The backlight went off, and I got a line of text <something I can't remember> then ->no info.
have any info? Is this the same problem that r9 had with the 2.6.24 kernel?
-AeroSigma
-
I tried the r17, and got an error right at start-up. The backlight went off, and I got a line of text <something I can't remember> then ->no info.
have any info? Is this the same problem that r9 had with the 2.6.24 kernel?
-AeroSigma
Yeah. Still the same problem with r9. The one built from dev branch boots fine fore. I'm trying to figure out what's the difference.
-
I can't seem to get insternal WiFi to work (out of the box,) I select the "Wifi device" in the wlan0 tab under network settings, but next time I open network settings, it has unchecked itself. I also don't seem to have the tools like ifconfig ifup etc. to work with. What image are you using? I'm using the x11-image which gives me GPE.
Edit: Well I've installed the console edition and I have the networking tools. Could they have gotten overlooked in the x11-istall package? Also, do you know what are the "relevant packages" to install GPE and x11 from the base console flash?
-AeroSigma
-
I can't seem to get insternal WiFi to work (out of the box,) I select the "Wifi device" in the wlan0 tab under network settings, but next time I open network settings, it has unchecked itself. I also don't seem to have the tools like ifconfig ifup etc. to work with. What image are you using? I'm using the x11-image which gives me GPE.
Edit: Well I've installed the console edition and I have the networking tools. Could they have gotten overlooked in the x11-istall package? Also, do you know what are the "relevant packages" to install GPE and x11 from the base console flash?
-AeroSigma
The wlan0 network setting gui is known broken. Try to manually edit /etc/wlan instead. There is a nice tutorial in the openzaurus wiki which works the same for Angstrom.
The /sbin directory is not in the normal users' path. su - to get root access (just enter for password) for ifconfig, ifup etc.
-
I felt like a fish out of water without my internet config tools. I tried root
su but not su - but with the latter, I get more in my PATH. what does the - do?
I've got usb ethernet and wireless working now.
Thanks
-AeroSigma
-
but with the latter, I get more in my PATH. what does the - do?
I think it's a convention (busybox?). su is what debian/ubuntu uses for root including all PATH, while su is what Fedora uses for limited root, you need su - in Fedora for root with /sbin. I have no insight or historical knowledge about why it is so, although Angstrom is closer to debian than Fedora in lineage.
-
su makes you become root but keeps most of your existing environment, "su -" replaces your environment so is equivalent to logging in afresh as the new user.
you can also do "su fred" and "su - fred"
and you can run a command with su too
of course all this depends on what's been built into busybox.
-
I've searched around for a way to sync my Angstrom w/GPE (installed gpe-todo, gpe-calendar etc. as well) with Outlook in windows(no choice, it's used at my company) and I can't seem to be able to get it to work. This is really the only holding point for me to switch to Angstrom. Am I overlooking something? Is there a way to sync my Tosa loaded with Angstrom w/GPE to Outlook in Windows?
-AeroSigma
PS-it dosen't have to be easy to set up, I can handle the terminal and vi etc. It just has to work once it's been set up.
-
AeroSigma,
Which install of Angstrom are you using? I've tried a few and get the blank screen as well (has a bug for the latest version been filed?).
In terms of syncing, there was some activity when OpenZaurus was active...had something to do with passwordless ssh and some file conversions on the fly IIRC. I may be confusing that with sync w/ Evolution.
-
Use r8 (release 8) to get by the blank screen problem. All of the newer releases have the 2.6.24 kernel, which won't boot on the tosa yet. You can find r8 here. (http://www.angstrom-distribution.org/unstable/images/tosa/) You can find the rest of the Tosa imagese here. (http://www.angstrom-distribution.org/unstable/autobuild/tosa/)
xjgian mentioned that he got the current release (17?) booting on the Tosa when he self-complied from the dev build, so I'm trying that out. I'll let you know how it goes.
-
xjgian mentioned that he got the current release (17?) booting on the Tosa when he self-complied from the dev build, so I'm trying that out. I'll let you know how it goes.
SO how does it go you ask? Not well. I compiled r18 from the Dev build (took an entire day running on Ubuntu through VMWare) but when I flashed my Tosa, I still get the "tmio-fb: null info->mode" at the top of the screen instead of booting up, which I beileve is the 2.6.24 kernel problem.
xjgian, did you get a bootable build with the 2.6.24 kernel? Could you send my your local.conf or your x11 image?
-AeroSIgma
-
Let me also ask you; have you gotten around the suspend bug? I don't believe that's been fixed in any of the releases.
I keep forgetting about this...and it's a show stopper for me.
-
Sorry to post on a dead post but I just wanted to let you know that after lots of debugging from Dmitry he finally manage to solve the 2.6.24 bug on the tosa kernel.
It is available here : http://tosa.lumag.spb.ru/uploads/tosa-stable-images/debug/ (http://tosa.lumag.spb.ru/uploads/tosa-stable-images/debug/)
So now Angström is booting back with the r19 image. But with that image the backlight doesn't seems to work on my tosa. I haven't tried other images yet though to check.
Discussion on the topic can be found here : http://lists.linuxtogo.org/pipermail/angst...ber/002737.html (http://lists.linuxtogo.org/pipermail/angstrom-distro-devel/2008-November/002737.html)
More information on Dmitry's tosa page : http://tosa.lumag.spb.ru/news/17/55/Status-update.html (http://tosa.lumag.spb.ru/news/17/55/Status-update.html)
-
Sorry to post on a dead post but I just wanted to let you know that after lots of debugging from Dmitry he finally manage to solve the 2.6.24 bug on the tosa kernel.
It is available here : http://tosa.lumag.spb.ru/uploads/tosa-stable-images/debug/ (http://tosa.lumag.spb.ru/uploads/tosa-stable-images/debug/)
So now Angström is booting back with the r19 image. But with that image the backlight doesn't seems to work on my tosa. I haven't tried other images yet though to check.
Discussion on the topic can be found here : http://lists.linuxtogo.org/pipermail/angst...ber/002737.html (http://lists.linuxtogo.org/pipermail/angstrom-distro-devel/2008-November/002737.html)
More information on Dmitry's tosa page : http://tosa.lumag.spb.ru/news/17/55/Status-update.html (http://tosa.lumag.spb.ru/news/17/55/Status-update.html)
good news late is still good news! does that means the backlight is stuck ON or OFF?
-
good news late is still good news! does that means the backlight is stuck ON or OFF?
Hey Speculatrix,
It was always stuck off, that's why it was unusable Anyway while I was posting this, Dmitry released a new kernel with a fix at the same place (http://tosa.lumag.spb.ru/uploads/tosa-stable-images/debug/) so now you can test the latest Angstrom on the tosa.
Honestly I haven't had the time to try anything on it yet, so I can't tell you if it's good or not but it's still means a working 2.6.24 kernel on tosa !
Anyway if people could have a go with it, I bet Dmitry could do with more tosa users testings.
-
http://www.angstrom-distribution.org/relea...2007.12/images/ (http://www.angstrom-distribution.org/releases/2007.12/images/)
doesn't seem to list tosa at all! where can I find a tosa firmware image I can flash please?
-
Hey Speculatrix,
Sorry I should have specified
Tosa hasn't been a supported plateform during the latest stable release for lack of maintainers to solve the tosa specific issues. But you can find the 2007.12 r8 images here :
http://www.angstrom-distribution.org/unstable/images/tosa/ (http://www.angstrom-distribution.org/unstable/images/tosa/) which are the last know working images with 2.6.23 kernels. The 2007.12 r9 marked the switch to 2.6.24 and a massive tosa breakage that has just been solved by Dmitry.
You can find all images incudling the new OPIE images here : http://www.angstrom-distribution.org/unsta...autobuild/tosa/ (http://www.angstrom-distribution.org/unstable/autobuild/tosa/) (use the installkits)
It seems the new kernel from Dmitry hasn't been committed yet so you will find the zimage from here : http://tosa.lumag.spb.ru/uploads/tosa-stable-images/debug/ (http://tosa.lumag.spb.ru/uploads/tosa-stable-images/debug/)
I know you don't need the instructions as you are an experienced tosa users but in case somebody needs them :
1. For GPE download : http://www.angstrom-distribution.org/unsta...-installkit.tgz (http://www.angstrom-distribution.org/unstable/autobuild/tosa/Angstrom-minimalist-gpe-image-glibc-ipk-2007.12-r19-tosa-installkit.tgz)
For OPIE download : http://www.angstrom-distribution.org/unsta...-installkit.tgz (http://www.angstrom-distribution.org/unstable/autobuild/tosa/Angstrom-opie-image-glibc-ipk-2007.12-r19-tosa-installkit.tgz)
2. Download the alternative kernel from Dmitry : http://tosa.lumag.spb.ru/uploads/tosa-stab...zImage-tosa.bin (http://tosa.lumag.spb.ru/uploads/tosa-stable-images/debug/zImage-tosa.bin)
3. Rename it to zimage.bin
4. Extract the installkit
5. Replace the zimage.bin by the one from Dmitry
6. Put the files on a FAT formatted CF or SD
7. Reset with the stylus.
8. Press OK while pressing the ON button
9. Choose Update and then CF or SD
10. After the flashing it should reboot automatically
11. Test Angstrom
Let me know if you have any issues
LeTic
-
OK...I had forgotten about the autobuild directory. I tried the new kernel with the older installkits, so I'm assuming that's why things like sound and backlight are not impacted by Opie or GPE.
Aside from that, things look REALLY good! Response is very snappy, boot time is short, suspend works (though needs "Menu | Suspend" to go into suspend, button brings out of suspend). Today I'll try the autobuild rootfs's to see what the difference is.
Excellent work Dmitri!!
-
first time it booted, it stuck on the line printed before INIT, but this time looks better.
--edit-- hm, doesn't seem to suspend. is that normal?
memo to self: fix wonky LCD cable!
-
--edit-- hm, doesn't seem to suspend. is that normal?
It suspended for me using the menu (QPE, or Opie); not with the button. Comes out of suspend via the button, however.
Still no access to increasing / decreasing backlight via settings on either opie or gpe, haven't tested sound through alsa(mixer, player, etc...), but wifi is working (open network at least)!
-
thanks for that. my frankenzaurus has a loose connection somewhere and the video display has gone funny- upside down and scaled wrongly, so I will open up and have a poke!
computer hardware's been a PITA of late, my wireless NAS's wifi is bust, my sony laptop fan is failing, and my UPS has developed a death-rattle when its fans kick in.
-
--edit-- hm, doesn't seem to suspend. is that normal?
It suspended for me using the menu (QPE, or Opie); not with the button. Comes out of suspend via the button, however.
I'll have to look upon this.
Still no access to increasing / decreasing backlight via settings on either opie or gpe, haven't tested sound through alsa(mixer, player, etc...), but wifi is working (open network at least)!
I've committed the fix for the opie to .dev branch to support backlight setting. I'll have to look into GPE, but that may need time, as I'm more dedicated to opie for now. The patch should be
pretty easy though (check opie commit).
-
This may be a bit off topic but I was testing Angstrom on my Tosa but when I tried to reflash my NAND backup it turned out the the backup was bad. Unfortuantely the only NAND backups I have been able to find are Japanese and while that looks cool and all my Japanese is not really up to par. Anyone have a good NAND backup they would be willing to share? Oh yeah also my update menu is still in Japanese even after flashing Angstrom.Thanks
-
Unfortuantely the only NAND backups I have been able to find are Japanese and while that looks cool and all my Japanese is not really up to par.
There are several topics about NAND backups on this forum. Also the page about tosa on www.oesf.org should contain a link to SL-6000 NAND backup. Please take care to check.
-
I'm not sure you can ever change the update menu, there's an immutable block of flash for recovery, this is why zaurus is hard to brick.
There is a "diagnostic" menu in ROM, which can not be removed. OTOH "update" menu lies just in bare NAND and can easily be removed (e.g. by installing u-boot).
-
Unfortuantely the only NAND backups I have been able to find are Japanese and while that looks cool and all my Japanese is not really up to par.
There are several topics about NAND backups on this forum. Also the page about tosa on www.oesf.org should contain a link to SL-6000 NAND backup. Please take care to check.
Unfortuantely I have checked and all the links I have been able to find to the sl-6000L NAND backup are broken. I was hoping someone else might have squirreled one away just in case.
-
I'm not sure you can ever change the update menu, there's an immutable block of flash for recovery, this is why zaurus is hard to brick.
trisoft IIRC had downloads of various roms.
Well I have done it. My update menu was in English before but now it is Japanese.
-
--edit-- hm, doesn't seem to suspend. is that normal?
It suspended for me using the menu (QPE, or Opie); not with the button. Comes out of suspend via the button, however.
I'll have to look upon this.
Today the fix went in in the .dev branch. It was just two missed lines in defconfig-tosa. I'll still have to check the keys mappings, check GPE problems etc.
-
Speaking of keymappings; I did an
ipkg update, ipkg upgrade
which eliminated my ability to get to the Fn generated keys (numbers, punctuation, etc...)
Suspend still has the problem of freezing the prism2_usb module. Can't reload (unload or load) this module after suspend.
I've noticed some other behaviors; but they're specific to Opie or GPE.
Feeling hopeful!
-
Speaking of keymappings; I did an
ipkg update, ipkg upgrade
Angstrom 2008 uses opkg. Do you track 2008 (unstable) or 2007 (stable) branch?
which eliminated my ability to get to the Fn generated keys (numbers, punctuation, etc...)
Suspend still has the problem of freezing the prism2_usb module. Can't reload (unload or load) this module after suspend.
The workaround was pushed into 2008 branch. If you do track 2007.1, get apm-tosa-suspendfix package from 2008 feed
and install it.
I've noticed some other behaviors; but they're specific to Opie or GPE.
Tell me more, please
Most probably there should be several problems related to incorrect keymappings,
I did not test GPE at all for a long time. Currently busy with work, RL, providing upgraded kernel via OE (I plan to provide 2.6.27 or 2.6.28-rc soon) and fixing opie issues.
-
Angstrom 2008 uses opkg. Do you track 2008 (unstable) or 2007 (stable) branch?
Not sure what you mean by "track", however update specified 2007.
Tell me more, please
Most probably there should be several problems related to incorrect keymappings,
You jogged my memory. - Key repeat is still too sensitive. Very easy to do www.goooooogle.commm
- Testing the sketchpad app, I discovered I could not draw a straight line; just jagged ones (even after recalibrating)
- I'd like to be able to install Minimo or Midori, but ran into the "locale not supported" error.
- Installing to SD or CF requires linking to get libs to work.
I'm sure at least a couple of the above are kernel related.
[!--quoteo(post=0:date=:name=lumag)--][div class=\'quotetop\']QUOTE(lumag)[/div][div class=\'quotemain\'][!--quotec--]I did not test GPE at all for a long time. Currently busy with work, RL, providing upgraded kernel via OE (I plan to provide 2.6.27 or 2.6.28-rc soon) and fixing opie issues.[/quote]
Your work is appreciated.
-
Not sure what you mean by "track", however update specified 2007.
[!--quoteo(post=0:date=:name=lumag)--][div class=\'quotetop\']QUOTE(lumag)[/div][div class=\'quotemain\'][!--quotec--]The workaround was pushed into 2008 branch. If you do track 2007.1, get apm-tosa-suspendfix package from 2008 feed
and install it.
Does this mean if I use opkg, I'll be on the right track (so to speak)? Or is it editing the /etc/opkg files?
[/quote]
Hey undrwater
FYI the 2008 branch is now in the autobuild feeds here : http://www.angstrom-distribution.org/unsta...autobuild/tosa/ (http://www.angstrom-distribution.org/unstable/autobuild/tosa/) so you can test the current development version instead of the "Old" stable. It features lots of improvements (one of them being the use of opkg instead of ipkg) and all the Tosa work from Dmitry.
-
OK...I was looking in that directory before, but the images I downloaded still use ipkg.
I do notice the following:
Angstrom-x11-image-glibc-ipk-2008.1-test-20081127-tosa-installkit.tgz
which I suppose is the "2008" track you speak of. I'll try that out.
[EDIT]
Just tried it out. Show stopper is apparently the keyboard does not work. "new user details" screen is the first...but neither HW or SW keyboard are placing text in the fields. Orange lines are back too. This is with the above installkit and Dmitry's kernel.
[/EDIT]
-
I pried my eyes a bit wider and found a few other of the 2008.1 images. None of the x11 images allow me to enter info into the login screens, so I tried the console image and found opkg. Suspend did not work via hardware on this image either. What's the command?
I'm curious to try e-wm...is the one that's in the feed the same as what's showing up on the openmoko devices?
I have to say it's been fun trying new stuff with this device that had been gathering dust!
-
Just tried it out. Show stopper is apparently the keyboard does not work. "new user details" screen is the first...but neither HW or SW keyboard are placing text in the fields. Orange lines are back too. This is with the above installkit and Dmitry's kernel.
For the keyboard, etc. I'm waiting for general Angstrom decision about future of X11 images (will they contain Kdrive or Xorg and which version).
Suspend did not work via hardware on this image either. What's the command?
I generally use apm -s. However if the "power" button doesn't work, could you please post the result of
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']grep Name /proc/bus/input/devices
grep Handlers /proc/bus/input/devices[/div]
Also please check the exact version of kernel package in those images.
-
could you please post the result of
# grep Name /proc/bus/input/devices
N: Name="Tosa Keyboard"
N: Name="wm97xx touchscreen"Also please check the exact version of kernel package in those images.
Not sure what you meant specifically, but here's:
# uname -a
Linux tosa 2.6.24 #1 PREEMPT Fri Nov 21 16:46:51 MSK 2008 armv5tel unknown
and:
#opkg list | grep kernel
.
.
.
kernel - 2.6.24-r17.1 - 2.6 Linux Development Kernel for Zaurus devices and iPAQ hx2750.
kernel - 2.6.24-r16.1 -
kernel-2.6.24 - 2.6.24-r17.1 - 2.6 Linux Development Kernel for Zaurus devices and iPAQ hx2750.
kernel-2.6.24 - 2.6.24-r16.1 -
kernel-cmdline-2.6.24 - 2.6.24-r17.1 - 2.6 Linux Development Kernel for Zaurus devices and iPAQ hx2750.
kernel-cmdline-2.6.24 - 2.6.24-r16.1 -
kernel-dev - 2.6.24-r17.1 - 2.6 Linux Development Kernel for Zaurus devices and iPAQ hx2750.
kernel-image-2.6.24 - 2.6.24-r17.1 - 2.6 Linux Development Kernel for Zaurus devices and iPAQ hx2750.
.
.
.
Hope that's what you needed.
BTW: apm -s worked quite nicely. Hardware button brought Tosa back to life. I had to reset my network settings (which brought back wifi), but at least the module wasn't frozen.
-
could you please post the result of
# grep Name /proc/bus/input/devices
N: Name="Tosa Keyboard"
N: Name="wm97xx touchscreen"Also please check the exact version of kernel package in those images.
Not sure what you meant specifically, but here's:
# uname -a
Linux tosa 2.6.24 #1 PREEMPT Fri Nov 21 16:46:51 MSK 2008 armv5tel unknown
I see... please reflash the kernel with http://www.angstrom-distribution.org/unsta...24-r17-tosa.bin (http://www.angstrom-distribution.org/unstable/autobuild/tosa/zImage-2.6.24-r17-tosa.bin)
It should fix the power key problem.
BTW: apm -s worked quite nicely. Hardware button brought Tosa back to life. I had to reset my network settings (which brought back wifi), but at least the module wasn't frozen.
As assumed.
-
please reflash the kernel with http://www.angstrom-distribution.org/unsta...24-r17-tosa.bin (http://www.angstrom-distribution.org/unsta...24-r17-tosa.bin)
It should fix the power key problem.
It does. But are all of the debug options turned on? It's very noisy!
Also, I was playing around a bit and got e-wm installed and running up to the point where locale is asked for...but it doesn't seem to register the touch screen. Is that a kernel thing, or an e thing?
-
please reflash the kernel with http://www.angstrom-distribution.org/unsta...24-r17-tosa.bin (http://www.angstrom-distribution.org/unsta...24-r17-tosa.bin)
It should fix the power key problem.
It does. But are all of the debug options turned on? It's very noisy!
Most probably the debug is on as it's unstable release. At least I didn't do anything special for enabling it
Also, I was playing around a bit and got e-wm installed and running up to the point where locale is asked for...but it doesn't seem to register the touch screen. Is that a kernel thing, or an e thing?
As the ts does work in opie, I'd assume that this is the E problem.
-
I think everything looks good so fart at this point except key repeat. Once again, if I type www.google.com, I typically get wwwww.gooooogle.com. This behavior showed up in previous kernels and has a bug filed.
Thanks again...and Happy New Year!!
-
I know you don't need the instructions as you are an experienced tosa users but in case somebody needs them :
I'm almost tearing my hair out with the latest Angstrom! Hopefully someone can help me figure all this out.
I installed openembedded and tried building a couple of images, basically, helloworld-image and console-image. And I ended up with an angstrom-dev/deploy/glibc/images/tosa directory that looks like this:
Angstrom-helloworld-image-glibc-ipk-2009.X-test-20090529-tosa-installkit.tgz
Angstrom-helloworld-image-glibc-ipk-2009.X-test-20090529-tosa-installkit.tgz.md5
Angstrom-helloworld-image-glibc-ipk-2009.X-test-20090529-tosa.rootfs.jffs2
Angstrom-helloworld-image-glibc-ipk-2009.X-test-20090529-tosa.rootfs.tar.bz2
Angstrom-helloworld-image-glibc-ipk-2009.X-test-20090529-tosa.rootfs.tar.gz
Angstrom-helloworld-image-glibc-ipk-2009.X-test-20090529-tosa-testlab
Angstrom-initramfs-kexecboot-image-glibc-ipk-2009.X-test-20090529-tosa-installkit.tgz
Angstrom-initramfs-kexecboot-image-glibc-ipk-2009.X-test-20090529-tosa-installkit.tgz.md5
Angstrom-initramfs-kexecboot-image-glibc-ipk-2009.X-test-20090529-tosa.rootfs.cpio.gz
Angstrom-initramfs-kexecboot-image-glibc-ipk-2009.X-test-20090529-tosa.rootfs.jffs2
Angstrom-initramfs-kexecboot-image-glibc-ipk-2009.X-test-20090529-tosa.rootfs.tar.bz2
Angstrom-initramfs-kexecboot-image-glibc-ipk-2009.X-test-20090529-tosa.rootfs.tar.gz
Angstrom-initramfs-kexecboot-image-glibc-ipk-2009.X-test-20090529-tosa-testlab
helloworld-image-tosa.jffs2
helloworld-image-tosa.tar.bz2
helloworld-image-tosa.tar.gz
initramfs-kexecboot-image-tosa.cpio.gz
initramfs-kexecboot-image-tosa.jffs2
initramfs-kexecboot-image-tosa.tar.bz2
initramfs-kexecboot-image-tosa.tar.gz
modules-2.6.29-r0-tosa.tgz
updater.sh.tosa
zImage-2.6.29-r0-tosa.bin
zImage-kexecboot-2.6.24-r0-tosa.bin
zImage-kexecboot-tosa.bin
zImage-tosa.bin
I have no idea what all these do or how to use them. What I did try is various combinations of flashing a zImage.bin and initrd.bin using option 4 of the maintenance menu (as specified per earlier instructions). The flashing usually works alright but then when it boots, it loads a bootloader that cannot find any bootable devices. On a hunch, I tried unpacking one of the tar.gz images to an ext2 formatted SD card and tried booting with that plugged in and it was detected by the bootloader. Booting it sort of worked but it quickly exited back to the bootloader (I assume that was just a problem with the image I unpacked).
My questions are:
What is the correct usage for all of these file types, i.e. should the .jffs2 files be renamed initrd.bin and included in the flashing process? What am I supposed to do with the bz2 and gz files? Are they only for unpacking to external media?
How do I install to the internal flash? It used to work with the stable 2007-12 build and instructions.
Is there a newer version of updater.sh (that one was not built by oe and I added it myself having picked it up from elsewhere)? The reason I ask is that when trying to flash zImage-2.6.29-r0-tosa.bin it fails during the update program with the error that the file is too big. That kernel is approximately 1.3mb while the others are 1.2mb. Is this a constraint of the SL-6000 itself? I thought it has 32mb of internal memory.
* * *
Unfortunately, none of the available documentation that I could find online talks about installing these files. I did find a small entry here Angstrom Manual (http://linuxtogo.org/gowiki/AngstromManual) which talks about what they are but not how to use them as they are all device specific. Unfortunately the tosa documentation only talks about copying the files from an installkit and flashing the device from the maintenance menu.
-
Hi,
sorry for the lack of documentation, kexecboot is still in development...
Here the important bits:
Sharp Zaurus family (new method - WIP)
For every machine an installkit-${MACHINE}.tar.gz is created, containing updater.sh and zImage (the kexecboot-kernel). Unpack the installkit on a formatted card and follow the usual flashing procedure. If you want a rootfs in nand, this mus be in the .jffs2 format. Just rename your-image-rootfs.jffs2 to initrd.bin and copy it on the card whith updater.sh. On removable media, the root filesystem (your-image-rootfs.tar.gz) must be unpacked into the desired partition.
I'm pretty sure you have an outdated git tree. Please delete all the a.m. images, pull and rebuild.
Regards
Ant
-
Hi,
sorry for the lack of documentation, kexecboot is still in development...
Here the important bits:
Sharp Zaurus family (new method - WIP)
For every machine an installkit-${MACHINE}.tar.gz is created, containing updater.sh and zImage (the kexecboot-kernel). Unpack the installkit on a formatted card and follow the usual flashing procedure. If you want a rootfs in nand, this mus be in the .jffs2 format. Just rename your-image-rootfs.jffs2 to initrd.bin and copy it on the card whith updater.sh. On removable media, the root filesystem (your-image-rootfs.tar.gz) must be unpacked into the desired partition.
I'm pretty sure you have an outdated git tree. Please delete all the a.m. images, pull and rebuild.
Regards
Ant
Thank you for the explanation! After I get it all working I promise to update the wiki
I'm not sure what I'm doing wrong with the git tree. I set it up using the Building Angstrom Instructions (http://www.angstrom-distribution.org/building-ångström) literally a few days ago. Unfortunately, that didn't build correctly the first time and I made the following changes to get it to build:
I replaced my copies of:
kexec-arm-atags.patch
kexec-tools-static_1.101.bb
initramfs-kexecboot-image.bb
With copies downloaded from http://cgit.openembedded.org/ (http://cgit.openembedded.org/) in the org.openembedded.dev branch. And I added my own copy of updater.sh.tosa after an error message reported that it couldn't find it.
Doing that allowed me to compile and make the images I was asking about above but doing a "git pull" seems to have broken it and I can't figure out how to fix it so...
I've just decided to delete everything start over following the OE Getting Started Instructions (http://wiki.openembedded.net/index.php/Getting_Started) the only notable difference appears to be not checking out the stable/2009 branch.
-
>I replaced my copies of:
...
>the only notable difference appears to be not checking out the stable/2009 branch.
Yes...the fixes are only in .dev branch at the moment.
A patch for .stable branch is expected very soon.
Regards
Ant
-
Okay, two more problems have arisen...
1. Building base-image or console-image fails at the wlan-ng packages. Here is the log for wlan-ng modules.
NOTE: make CC=ccache arm-angstrom-linux-gnueabi-gcc -march=armv5te -mtune=xscale -mno-thumb-interwork -mno-thumb LD=arm-angstrom-linux-gnueabi-ld PARALLEL_MAKE= -C src all
make: Entering directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src'
set -e; for d in mkmeta shared p80211 prism2; do make WLAN_SRC=/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/ -C $d ; done
make[1]: Entering directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/mkmeta'
mkdir -p obj
make[1]: Leaving directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/mkmeta'
make[1]: Entering directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/shared'
Nothing to do...
make[1]: Leaving directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/shared'
make[1]: Entering directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/p80211'
make -C /home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/linux-2.6.29-r4/linux-2.6.29 M='/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/p80211' WLAN_SRC=/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/ modules
make: Entering an unknown directory
make: *** /home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/linux-2.6.29-r4/linux-2.6.29: No such file or directory. Stop.
make: Leaving an unknown directory
make[1]: *** [default] Error 2
make[1]: Leaving directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/p80211'
make: *** [all] Error 2
make: Leaving directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src'
FATAL: oe_runmake failed
It appears to be a file not found error but I haven't modified the tree at all and I did a "git pull" before building.
2. Two kernels were built (2.6.24-r13 and 2.6.29-r5) as well as updater.sh.tosa. Only 2.6.24-r13 can be flashed using updater.sh.tosa, 2.6.29-r5 gives the error message that the file is too big. This is a problem because as you know, the reason I am trying to get this all up and running is so I can take a shot at installing Android and I believe Android requires a 2.6.25 or higher kernel to work.
-
I asked on the mailing list, but didn't get a reply so I thought I'd ask here.
All of the 2008.x images in the autobuild dir are gone, and only kexec images are there. I have used the narcissus images in the past successfully to boot Angstrom with either Opie or x11 for Tosa (via SD w/ kexec kernel). Lately the images have not been completing the configuration of kernel modules. In particular, kernel-module-zlib-inflate gets stuck (can't get past it - Tosa requires a reset).
I'm curious if anyone is still doing kernel dev for the tosa (it was lumaq {letic?}). Is there any way to follow development if it is still going on? I love the device, and I'd love to continue using it if I can.
Thanks,
Russell Dwiggins
-
Kernel development is still actively done, and can be followed on the linux-arm-kernel mailing list.
I'll try to build 2.6.31 for Tosa tomorrow... promise made!
My Tosa has been sitting in the drawer for much too long. let's see how this works out
Cheers,
cortez
I asked on the mailing list, but didn't get a reply so I thought I'd ask here.
All of the 2008.x images in the autobuild dir are gone, and only kexec images are there. I have used the narcissus images in the past successfully to boot Angstrom with either Opie or x11 for Tosa (via SD w/ kexec kernel). Lately the images have not been completing the configuration of kernel modules. In particular, kernel-module-zlib-inflate gets stuck (can't get past it - Tosa requires a reset).
I'm curious if anyone is still doing kernel dev for the tosa (it was lumaq {letic?}). Is there any way to follow development if it is still going on? I love the device, and I'd love to continue using it if I can.
Thanks,
Russell Dwiggins
-
Thanks Cortez, you're a major asset to this community!
Does this mean Zubuntu might follow shortly?? *nudge*
-
Small update: the multiboot kernel is working, but starting the 2.6.31-rc3 kernel results in a black screen on startup. I'll check the kernel configuration again later to see if I mis-configured something, and give it another try.
-
Another small update: somehow the 2.6.31 kernel still doesn't work, so I tried 2.6.29. I now have Zubuntu working... at least partly. Fonts are displayed scrambled, and touchscreen doesn't seem to work. So a beginning is made, but there's still work to do.
-
A bigger update and a request for help to all off you can be found on my blog here (http://www.omegamoon.com/blog/index.php?entry=entry090716-153753).
-
I'm on my way to trying it, but just a quick note on extracting the rootfs onto an SD:
A lot of
Cannot create symlink to `': Operation not permittedtype errors.
More later...
-
I'm on my way to trying it, but just a quick note on extracting the rootfs onto an SD:
A lot of
Cannot create symlink to `': Operation not permittedtype errors.
More later...
Make sure you use "sudo tar -zxpf achive.tar.gz" to make sure you have the right permissions. This is important!
-
Turned out to be a bad mount. Created new topic (Zubuntu isn't angstrom, is it?)
-
Thanks Cortez, you're a major asset to this community!
Does this mean Zubuntu might follow shortly?? *nudge*
I agree 100%. I might be somewhat quiet of late due to busyness, but I still read the updates avidly. I've bought a dremel in the hope I can grind off the broken ram chip in one of my tosas and solder a fresh one on!