OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: CoreDump on May 21, 2006, 11:27:20 am
-
Hey all,
At http://hentges.net/tmp/Poodle-Kernel-2.6/ (http://hentges.net/tmp/Poodle-Kernel-2.6/) you'll find an experimental Opie image for Poodle with kernel 2.6.
Be advised that a few kernel related things are still broken (sound, SD/MMC and probably USB) but this preview should give you a good understanding of what is to come
If you find problems with Opie that are related to the switch from kernel 2.4 to 2.6 please let me know but check the Kernel 2.6 Status Page (http://hentges.net/tmp/Poodle-Kernel-2.6/) before posting.
Have fun
-
Hi CoreDump,
I just wanted to say I'm really impressed and happy with the progress I am reading about, and very happy that I donated money towards the 5600 you now have. Since the 5600 is my primary PDA I am not able to help test currently since certain bugs that are listed are too critical for me not to be able to use, but am looking forward to trying this out once things get a little more stable.
Best of luck and bravo on your speedy work!
steven
Hey all,
At http://hentges.net/tmp/Poodle-Kernel-2.6/ (http://hentges.net/tmp/Poodle-Kernel-2.6/) you'll find an experimental Opie image for Poodle with kernel 2.6.
Be advised that a few kernel related things are still broken (sound, SD/MMC and probably USB) but this preview should give you a good understanding of what is to come
If you find problems with Opie that are related to the switch from kernel 2.4 to 2.6 please let me know but check the Kernel 2.6 Status Page (http://hentges.net/tmp/Poodle-Kernel-2.6/) before posting.
Have fun
[div align=\"right\"][a href=\"index.php?act=findpost&pid=127967\"][{POST_SNAPBACK}][/a][/div]
-
@CoreDump -> SD works for me... card: 256M Vikings
for example Calendar+Address+Backspace doesn't work on GPE from .dev
I don't know if you notice this but if you put the device in suspend/resume mode or change the backlight settings then the screen flicker for few seconds with horizontal lines...
Something I've played this weekend is creating a swap file via NBD (http://nbd.sourceforge.net/), I need to post the .bb file... so far it works great with 2.6.
-
@CoreDump -> SD works for me... card: 256M Vikings
for example Calendar+Address+Backspace doesn't work on GPE from .dev
GPE in .dev + .oz is missing a few changesets, that's why I only uploaded Opie so far
I don't know if you notice this but if you put the device in suspend/resume mode or change the backlight settings then the screen flicker for few seconds with horizontal lines...
Yep, getting that here as well.
Something I've played this weekend is creating a swap file via NBD (http://nbd.sourceforge.net/), I need to post the .bb file... so far it works great with 2.6.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=128016\"][{POST_SNAPBACK}][/a][/div]
Sound nifty but also dog slow
-
In what does that image differ from the normal 2.4 image?
I thought you can use a normal image with the right modules in /lib/modules
-
Jinidog: there was some fixes done in OPIE recently to get poodle support fixed. Also some changes to rootfs content.
-
Any specific place to look for current dated updates by the 2 developers doing Poodle work? The status page on OZ gets changed but no dated information to tell when things are getting fixed. Maybe a blog with just little notes regarding what got fixed when and by whom and if other bugs are found where to report them to and where the latest test releases can be downloaded.
Thanks
-
In short: CoreDump cleaned most of userspace problems and some of kernel part. Now we need to go into kernel work where we do not have too many people.
-
I'm going to paste CoreDump's post from the 5x00 General discussions here so the OZ users can see it:
It took a bit longer than expected but here it is:
http://hentges.net/tmp/Poodle-Kernel-2.6/17-JUL-06/ (http://hentges.net/tmp/Poodle-Kernel-2.6/17-JUL-06/)
The GPE version needs hotkey bindings (edit /etc/keylaunchrc for that)
Sound drivers are installed but currently you'll get nasty distortions after any sound is played.
There is a alsa-mixer configuration which enables perfect sound (after rebooting) since RP's sound worked just fine. After he installed my asound.state he got caught by the distortions, too. Sadly he overwrote his working asound.state.
Soo....if you manage to find the working settings (using alsamixer) let me know =)
from here:
https://www.oesf.org/forums/index.php?showt...ndpost&p=135461 (https://www.oesf.org/forums/index.php?showtopic=19157&view=findpost&p=135461)
I'm listening to mp3s with xmms on my poodle and they sound very good.
I've installed: alsa-conf, alsa-settings, alsa-utils-alsactl, alsa-utils-alsamixer, alsa-utils-aplay... opened alsamixer and turned the volumn down.
Thanks CoreDump
Greg
-
I'm going to paste CoreDump's post from the 5x00 General discussions here so the OZ users can see it:It took a bit longer than expected but here it is:
http://hentges.net/tmp/Poodle-Kernel-2.6/17-JUL-06/ (http://hentges.net/tmp/Poodle-Kernel-2.6/17-JUL-06/)
The GPE version needs hotkey bindings (edit /etc/keylaunchrc for that)
Sound drivers are installed but currently you'll get nasty distortions after any sound is played.
There is a alsa-mixer configuration which enables perfect sound (after rebooting) since RP's sound worked just fine. After he installed my asound.state he got caught by the distortions, too. Sadly he overwrote his working asound.state.
Soo....if you manage to find the working settings (using alsamixer) let me know =)
from here:
https://www.oesf.org/forums/index.php?showt...ndpost&p=135461 (https://www.oesf.org/forums/index.php?showtopic=19157&view=findpost&p=135461)
I'm listening to mp3s with xmms on my poodle and they sound very good.
I've installed: alsa-conf, alsa-settings, alsa-utils-alsactl, alsa-utils-alsamixer, alsa-utils-aplay... opened alsamixer and turned the volumn down.
Thanks CoreDump
Greg
[div align=\"right\"][a href=\"index.php?act=findpost&pid=135606\"][{POST_SNAPBACK}][/a][/div]
You're welcome RP is the true hero as he reworked poodles sound driver.
You're not getting static noise at the end of the song / file?
Do me a favor and do a "cat /usr/share/sounds/beep.raw > /dev/dsp" and tell me if you hear a sound w/ distortions after the sound has finished playing.
If not, a copy of your /etc/asound.state would be appreciated
-
You're not getting static noise at the end of the song / file?
no
Do me a favor and do a "cat /usr/share/sounds/beep.raw > /dev/dsp" and tell me if you hear a sound w/ distortions after the sound has finished playing.
root@poodle:/# cat /usr/share/sounds/beep.raw > /dev/dsp
-sh: cannot create /dev/dsp: Device
or resource busy
root@poodle:/# cat /usr/share/sounds/beep.raw > /dev/dsp
root@poodle:/#
The first test I had the screen taps and key clicks on, they work also
The second worked fine with no static or distortions after the beep.
Here's a copy of my asound.state:
-
In both the opie and gpe versions, the g_ether kernel modules were missing after the initial install. After I added it in, USB works great.
-
In both the opie and gpe versions, the g_ether kernel modules were missing after the initial install. After I added it in, USB works great.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=135620\"][{POST_SNAPBACK}][/a][/div]
Once OE is writeable again, I'll have a look at poodle-2.6.conf. There are quite a few differences between the .dev and .oz version (.dev installs more modules etc).
Thanks for letting me know
-
You're not getting static noise at the end of the song / file?
no
Do me a favor and do a "cat /usr/share/sounds/beep.raw > /dev/dsp" and tell me if you hear a sound w/ distortions after the sound has finished playing.
root@poodle:/# cat /usr/share/sounds/beep.raw > /dev/dsp
-sh: cannot create /dev/dsp: Device
or resource busy
root@poodle:/# cat /usr/share/sounds/beep.raw > /dev/dsp
root@poodle:/#
The first test I had the screen taps and key clicks on, they work also
The second worked fine with no static or distortions after the beep.
Here's a copy of my asound.state:
[div align=\"right\"][a href=\"index.php?act=findpost&pid=135615\"][{POST_SNAPBACK}][/a][/div]
Thanks for your config, I'll test it once I get poodle to compile correctly again.
-
Hi,
I wanted to provide a bit of feedback regarding the poodle 2.6 kernel. I hope this is the best place to put it:
After I installed cardfs for Opie, SDL applications didn't work anymore. They gave me this error:
Unable to init SDL: No available video device
So I removed the libsdl-1.2-0 that came with cardfs and installed the one from the 3.5.4.1 feed and then it worked again.
Also, prboom-opie in the 3.5.4.1 feed seems to be a duplicate of the prboom.ipk. prboom-opie from the 3.5.4 feed is the same version so I installed it and it works OK.
-
I noticed that with both opie and gpe the fn-levt/right-arrow combination does not switch VT's. If I switch to VT 1 I can use it to switch back however.
-
Thanks for your config, I'll test it once I get poodle to compile correctly again.
I was just looking for you on irc, but you weren't around. So I will leave you a note here:
I was listening to some of my blues today and it 'was' a good sounding system, but I thought I would test some other things for us poodle users... and I had to do a hard reset. After a reboot, there where 'your' distortions... I wish you had kept them
I copied the asound.state to my desktop and it was not changed from the working one, so I don't think that is the problem... or the fix.
Maybe a module not loading? I'll test some more tomorrow.
Greg
-
Hi,
I wanted to provide a bit of feedback regarding the poodle 2.6 kernel. I hope this is the best place to put it:
After I installed cardfs for Opie, SDL applications didn't work anymore. They gave me this error:
Unable to init SDL: No available video device
So I removed the libsdl-1.2-0 that came with cardfs and installed the one from the 3.5.4.1 feed and then it worked again.
Yes, that's one of the more annoying bugs of OE. It doesn't differentiate between libsdl-x11 and libsdl-qpe. So, depending on which sdl was compiled, either the Opie image or the GPE image will get the wrong version.
The only way around at this time is to rebuild the correct SDL before building any sort of image. It is something very easy to overlook
Also, prboom-opie in the 3.5.4.1 feed seems to be a duplicate of the prboom.ipk. prboom-opie from the 3.5.4 feed is the same version so I installed it and it works OK.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=135767\"][{POST_SNAPBACK}][/a][/div]
It's been some time since I did the prboom-opie hack. IIRC the only difference between the two are opie-specific "desktop" icons and a device-specific configuration of prboom.
Apart from that, prboom-opie and prboom are indeed identical.
-
I noticed that with both opie and gpe the fn-levt/right-arrow combination does not switch VT's. If I switch to VT 1 I can use it to switch back however.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=135770\"][{POST_SNAPBACK}][/a][/div]
VT switching should work just fine in GPE but is IIRC known not to work in Opie.
There may mor may not be some key-bindings missing from keylauncher which would explain the GPE issue.
Opie never had support for it in the first place
I'll have a look.
-
Thanks for your config, I'll test it once I get poodle to compile correctly again.
I was just looking for you on irc, but you weren't around. So I will leave you a note here:
I was listening to some of my blues today and it 'was' a good sounding system, but I thought I would test some other things for us poodle users... and I had to do a hard reset. After a reboot, there where 'your' distortions... I wish you had kept them
I copied the asound.state to my desktop and it was not changed from the working one, so I don't think that is the problem... or the fix.
Maybe a module not loading? I'll test some more tomorrow.
Greg
[div align=\"right\"][a href=\"index.php?act=findpost&pid=135795\"][{POST_SNAPBACK}][/a][/div]
Well, would have been too easy anyway RP only got the distrotions after a reboot, too. Interesting indeed. There are still some things to be fixed / reworked in the sound driver so a driver bug is indeed possible. At least RP can now reproduce the problem (which is required to be able to fix something like that).
Regarding IRC: /msg's or normal messages w/ my nick will usually appear in my backlog
-
Well, would have been too easy anyway RP only got the distrotions after a reboot, too. Interesting indeed.
To fix the poodle sound after a reboot-> you simply suspend from the menu for about 30 seconds
Maybe this info will help you or RP with the problem.
Greg
-
Well, would have been too easy anyway RP only got the distrotions after a reboot, too. Interesting indeed.
To fix the poodle sound after a reboot-> you simply suspend from the menu for about 30 seconds
Maybe this info will help you or RP with the problem.
Greg
[div align=\"right\"][a href=\"index.php?act=findpost&pid=135891\"][{POST_SNAPBACK}][/a][/div]
Excellent, thanks!
-
So, I finally tried the new images.
Couldn't test much of it until now, but looks good (and fast).
Is there anything special I have to care of when getting usb networking to work?
Is the kernel module missing?
ifconfig -a reports no usbd0 device.
-
So, I finally tried the new images.
Couldn't test much of it until now, but looks good (and fast).
Is there anything special I have to care of when getting usb networking to work?
Is the kernel module missing?
ifconfig -a reports no usbd0 device.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136174\"][{POST_SNAPBACK}][/a][/div]
and it will never do, usbd0 is some kernel 2.4 invention. Modprobe g_ether and ifup usb0
-
You will have to install the g_ether module from the feed first.
-
I feared that.
It's difficult without connection to the internet.
Where can I get the module so that I can copy it via card and insmod it?
-
Well, despite of that. With the hentges Opie image I had the problem, that the screen turns black when launching Opie.
Was unusable.
With GPE the backlight control doesn't work correctly and disables the screen normally.
You have to tap around on the black screen and move somehow the slider again until it turns on again.
Suspend does not work either.
-
The next release will have a lot more modules installed by default, g_ether being on of them.
-
Okay, I have that stuff working now.
Had to build my own kernel out of OE (and flash it since the modules where compiled with gcc-4.1.1 and your kernel is built with gcc-3.4) and it works now.
So far so good.
Don't want to give my new 2.6 kernel away
I'm just building some apps for testing them.
Strangly mounting nfs-drives does not work (protocol unsupported) although I have the nfs-module loaded.
Is anyone interested in my reports?
-
Okay, I have that stuff working now.
Had to build my own kernel out of OE (and flash it since the modules where compiled with gcc-4.1.1 and your kernel is built with gcc-3.4) and it works now.
So far so good.
I take it you've built the kernel from .dev? Th correct branch for OZ is .oz354x
Don't want to give my new 2.6 kernel away
I'm just building some apps for testing them.
Strangly mounting nfs-drives does not work (protocol unsupported) although I have the nfs-module loaded.
NFS shares mount fine. Please retry with a kernel from the .oz354x branch.
Is anyone interested in my reports?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136253\"][{POST_SNAPBACK}][/a][/div]
Of course, that's what this thread is there for
-
By the way, does the current poodle 2.6.17 kernel have the cache errata fix enabled or disabled? I get about 400 BogoMIPS but I can't tell what the actual CPU speed is running at. Would it be possible to test a "fast" kernel if the cache errata fix is currently enabled and the CPU is slowed down?
Thanks.
Okay, I have that stuff working now.
Had to build my own kernel out of OE (and flash it since the modules where compiled with gcc-4.1.1 and your kernel is built with gcc-3.4) and it works now.
So far so good.
I take it you've built the kernel from .dev? Th correct branch for OZ is .oz354x
Don't want to give my new 2.6 kernel away
I'm just building some apps for testing them.
Strangly mounting nfs-drives does not work (protocol unsupported) although I have the nfs-module loaded.
NFS shares mount fine. Please retry with a kernel from the .oz354x branch.
Is anyone interested in my reports?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136253\"][{POST_SNAPBACK}][/a][/div]
Of course, that's what this thread is there for
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136277\"][{POST_SNAPBACK}][/a][/div]
-
By the way, does the current poodle 2.6.17 kernel have the cache errata fix enabled or disabled? I get about 400 BogoMIPS but I can't tell what the actual CPU speed is running at. Would it be possible to test a "fast" kernel if the cache errata fix is currently enabled and the CPU is slowed down?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136285\"][{POST_SNAPBACK}][/a][/div]
kernel 2.6 handles that on-the-fly, no need for two kernels.
-
A new image is online (http://hentges.net/tmp/Poodle-Kernel-2.6/26-JUL-06/),
happy flashing
-
Do you know if it's possible to disable the cache errata fix in the 2.6 kernel even if I have a PXA250? I'm assuming that the kernel automatically enables it if it autodetects the PXA250 but I'd like to disable it and see if it causes any instability.
By the way, does the current poodle 2.6.17 kernel have the cache errata fix enabled or disabled? I get about 400 BogoMIPS but I can't tell what the actual CPU speed is running at. Would it be possible to test a "fast" kernel if the cache errata fix is currently enabled and the CPU is slowed down?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136285\"][{POST_SNAPBACK}][/a][/div]
kernel 2.6 handles that on-the-fly, no need for two kernels.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136286\"][{POST_SNAPBACK}][/a][/div]
-
Do you know if it's possible to disable the cache errata fix in the 2.6 kernel even if I have a PXA250? I'm assuming that the kernel automatically enables it if it autodetects the PXA250 but I'd like to disable it and see if it causes any instability.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136469\"][{POST_SNAPBACK}][/a][/div]
Yes, it will cause instability and data-corruption, that's why the check is there. Note that 2.6 handles it more intelligently (==faster) than 2.4, so there's no gain in disabling the check. Unless you like data corruption, of course.
-
Hi,
Can I ask a quick newbie question about the difference between the files in the ext2/ and tarballs/ directories? I've read through all of the altboot docs but I just want to make sure.
I think you use a file from the tarballs directory to install the rootfs either on to the SD card directly or on to a loop image on the SD card. If you install on to a loop image then you need to create the image and specify the size (which is fixed). Then you can use altboot to boot from the loop image.
I'm not so clear about the rootfs.ext2 files - I believe they are precreated loop images that you can use altboot to boot from. I'm assuming that these images are also fixed in size? What's the main purpose of using such an image, because it seems like you can boot from it but you can't install any new applications on it due to the fixed size.
Does this seem right? Altboot seems like a great idea and I like the idea of a bootable filesystem on an SD card so I can switch back and forth between GPE and Opie.
Thanks for all of your work on this!
A new image is online (http://hentges.net/tmp/Poodle-Kernel-2.6/26-JUL-06/),
happy flashing
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136462\"][{POST_SNAPBACK}][/a][/div]
-
Hi,
Can I ask a quick newbie question about the difference between the files in the ext2/ and tarballs/ directories? I've read through all of the altboot docs but I just want to make sure.
I think you use a file from the tarballs directory to install the rootfs either on to the SD card directly or on to a loop image on the SD card. If you install on to a loop image then you need to create the image and specify the size (which is fixed). Then you can use altboot to boot from the loop image.
Correct, the tar.gz installer of altboot creates the loop-image for you however.
I'm not so clear about the rootfs.ext2 files - I believe they are precreated loop images that you can use altboot to boot from.
Correct.
I'm assuming that these images are also fixed in size? What's the main purpose of using such an image, because it seems like you can boot from it but you can't install any new applications on it due to the fixed size.
The size is fixed yeah, but that doesn't mean there is no free space in /
The ext2 files are ~100Mb in size which leaves you _a_lot_ of free room to play with
Does this seem right? Altboot seems like a great idea and I like the idea of a bootable filesystem on an SD card so I can switch back and forth between GPE and Opie.
Thanks for all of your work on this!
A new image is online (http://hentges.net/tmp/Poodle-Kernel-2.6/26-JUL-06/),
happy flashing
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136462\"][{POST_SNAPBACK}][/a][/div]
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136478\"][{POST_SNAPBACK}][/a][/div]
-
Cool. I'd like to share my experiences with the brand new poodle 2.6 kernel. I installed the new Hentges bootstrap ROM and then the GPE and Opie Hentges premade ext2 rootfs files on an SD card in the /boot-images directory. The SD card is formatted as FAT.
As soon as the poodle booted up, it showed that it was loading some kernel modules. It complained about a few, saying that they already existed. I can get the exact list if you would like. Then it made a strange sound, almost like a telephone ring, and then static immediately after that.
I went into altboot and specified that I wanted to boot off of the GPE rootfs bin file. The static sound stopped as soon as altboot started. Altboot then started booting up with the GPE rootfs file but then it got to the point where it says "Waiting for /dev to be populated" and then hung indefinitely. I probably waited about 5-10 minutes and nothing happened.
Then I did a hard reset and tried to boot off of the Opie rootfs bin file. I got the same result.
Does it make a difference if the rootfs files are located on a FAT-formatted SD card? I tried formatting the SD card as ext2 a while back but gave up because fsck gave too many errors on bootup. Do you know if OZ supports the concept of nested ext2 loopfiles, where I could create a big loopfile and then put smaller ones inside of it? I might try this next.
Hi,
Can I ask a quick newbie question about the difference between the files in the ext2/ and tarballs/ directories? I've read through all of the altboot docs but I just want to make sure.
I think you use a file from the tarballs directory to install the rootfs either on to the SD card directly or on to a loop image on the SD card. If you install on to a loop image then you need to create the image and specify the size (which is fixed). Then you can use altboot to boot from the loop image.
Correct, the tar.gz installer of altboot creates the loop-image for you however.
I'm not so clear about the rootfs.ext2 files - I believe they are precreated loop images that you can use altboot to boot from.
Correct.
I'm assuming that these images are also fixed in size? What's the main purpose of using such an image, because it seems like you can boot from it but you can't install any new applications on it due to the fixed size.
The size is fixed yeah, but that doesn't mean there is no free space in /
The ext2 files are ~100Mb in size which leaves you _a_lot_ of free room to play with
Does this seem right? Altboot seems like a great idea and I like the idea of a bootable filesystem on an SD card so I can switch back and forth between GPE and Opie.
Thanks for all of your work on this!
A new image is online (http://hentges.net/tmp/Poodle-Kernel-2.6/26-JUL-06/),
happy flashing
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136462\"][{POST_SNAPBACK}][/a][/div]
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136478\"][{POST_SNAPBACK}][/a][/div]
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136482\"][{POST_SNAPBACK}][/a][/div]
-
Cool. I'd like to share my experiences with the brand new poodle 2.6 kernel. I installed the new Hentges bootstrap ROM and then the GPE and Opie Hentges premade ext2 rootfs files on an SD card in the /boot-images directory. The SD card is formatted as FAT.
As soon as the poodle booted up, it showed that it was loading some kernel modules. It complained about a few, saying that they already existed. I can get the exact list if you would like. Then it made a strange sound, almost like a telephone ring, and then static immediately after that.
I went into altboot and specified that I wanted to boot off of the GPE rootfs bin file. The static sound stopped as soon as altboot started. Altboot then started booting up with the GPE rootfs file but then it got to the point where it says "Waiting for /dev to be populated" and then hung indefinitely. I probably waited about 5-10 minutes and nothing happened.
Then I did a hard reset and tried to boot off of the Opie rootfs bin file. I got the same result.
Does it make a difference if the rootfs files are located on a FAT-formatted SD card? I tried formatting the SD card as ext2 a while back but gave up because fsck gave too many errors on bootup. Do you know if OZ supports the concept of nested ext2 loopfiles, where I could create a big loopfile and then put smaller ones inside of it? I might try this next.
I had similar problems with my 1 gig SD card (Kingston Elite pro) formated as ext2.. I have not had a chance to try my old 256 MB Kingston card that I used to use. I was able to split my 1GB card into 4 partitions and altboot from a real rootfs.
Hope this helps,
-
Is it possible to overclock the poodle with the 2.6 kernel?
(is it possible at all?)
-
Hmmm. So you were able to split your 1 GB card into 4 ext2 partitions and haven't experienced any problems? I may have to consider this if I run into a dead end.
My current approach is to format the SD card as FAT and create a 980 MB loop ext2 filesystem. I then put the rootfs filesystems in here. So it's a loop filesystem within a loop filesystem.
The problem is, altboot doesn't like this. It doesn't know how to mount the SD card to /mnt/sd and then do a mount -o loop /mnt/sd/filesys /media/card, and then boot off of the GPE rootfs image that it finds in /media/card/boot-images.
Any suggestions in how to hack altboot.func to do this? I was thinking about hardcoding the "mount -o loop" somewhere but there must be a more elegant way to autodetect the nested loop filesystems.
Cool. I'd like to share my experiences with the brand new poodle 2.6 kernel. I installed the new Hentges bootstrap ROM and then the GPE and Opie Hentges premade ext2 rootfs files on an SD card in the /boot-images directory. The SD card is formatted as FAT.
As soon as the poodle booted up, it showed that it was loading some kernel modules. It complained about a few, saying that they already existed. I can get the exact list if you would like. Then it made a strange sound, almost like a telephone ring, and then static immediately after that.
I went into altboot and specified that I wanted to boot off of the GPE rootfs bin file. The static sound stopped as soon as altboot started. Altboot then started booting up with the GPE rootfs file but then it got to the point where it says "Waiting for /dev to be populated" and then hung indefinitely. I probably waited about 5-10 minutes and nothing happened.
Then I did a hard reset and tried to boot off of the Opie rootfs bin file. I got the same result.
Does it make a difference if the rootfs files are located on a FAT-formatted SD card? I tried formatting the SD card as ext2 a while back but gave up because fsck gave too many errors on bootup. Do you know if OZ supports the concept of nested ext2 loopfiles, where I could create a big loopfile and then put smaller ones inside of it? I might try this next.
I had similar problems with my 1 gig SD card (Kingston Elite pro) formated as ext2.. I have not had a chance to try my old 256 MB Kingston card that I used to use. I was able to split my 1GB card into 4 partitions and altboot from a real rootfs.
Hope this helps,
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136617\"][{POST_SNAPBACK}][/a][/div]
-
I'm having trouble using ipkg. It works once, e.g on 'ipkg update', and then when I go to do 'ipkg upgrade' or 'ipkg update' again, I get this:
root@poodle:/var/tmp# ipkg upgrade
Upgrading gpe-bluetooth on root from 0.51-r0 to 0.53-r0...
Downloading http://ewi546.ewi.utwente.nl/mirror/www.openzaurus.org/official/unstable/3.5.4.1/feed/x11/gpe-bluetooth_0.53-r0_arm.ipk
xsystem: ERROR: fork failed before execution: `wget --passive-ftp -q -P /tmp/ipkg-zCmREl http://ewi546.ewi.utwente.nl/mirror/www.openzaurus.org/official/unstable/3.5.4.1/feed/x11/gpe-bluetooth_0.53-r0_arm.ipk'
Upgrading libcontactsdb0 on root from 0.3-r0 to 0.4-r0...
Downloading http://ewi546.ewi.utwente.nl/mirror/www.openzaurus.org/official/unstable/3.5.4.1/feed/x11/libcontactsdb0_0.4-r0_arm.ipk
xsystem: ERROR: fork failed before execution: `wget --passive-ftp -q -P /tmp/ipkg-zCmREl http://ewi546.ewi.utwente.nl/mirror/www.openzaurus.org/official/unstable/3.5.4.1/feed/x11/libcontactsdb0_0.4-r0_arm.ipk'
Package libusb is already installed in root.
Nothing to be done
Collected errors:
Failed to download gpe-bluetooth. Perhaps you need to run 'ipkg update'?
Failed to download libcontactsdb0. Perhaps you need to run 'ipkg update'?
Only way to fix it is to reboot or 'rm -rf /var/ipkg'
The PDA is connected via USB to my laptop and NAT is working properly; resolv.conf is also properly set up.
-
xsystem: ERROR: fork failed before execution: `wget --passive-ftp -q -P /tmp/ipkg-zCmREl
That means "Help, I'm out of memory", try adding some (more) swap
-
That means "Help, I'm out of memory", try adding some (more) swap
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136882\"][{POST_SNAPBACK}][/a][/div]
Is swap possible on the inbuilt (jffs2) flash? Creating a swap file works, but activating it fails with 'invalid argument', and the kernel says 'swapfile has holes'.
-
That means "Help, I'm out of memory", try adding some (more) swap
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136882\"][{POST_SNAPBACK}][/a][/div]
Is swap possible on the inbuilt (jffs2) flash? Creating a swap file works, but activating it fails with 'invalid argument', and the kernel says 'swapfile has holes'.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136886\"][{POST_SNAPBACK}][/a][/div]
It's possible, but will kill the flash. Try creating a swapfile on SD or CF
-
Just a thought. . . What are the BMIPs of a. . . say. . 3100?
Just thinking about zPSX. . .
-
I played around with this new image but experienced some problems. I started by installing the 26-July Hentges bootstrap image. I was able to modify altboot.func to work with nested filesystems, so I mounted my FAT SD card on /media/sd, then mounted an ext2 image called /media/sd/filesys on /media/card, then mounted the rootfs binary on /media/image. Both /dev/loop0 and /dev/loop1 are used.
But GPE wasn't functional - I got a segmentation fault when I tried to install the bash package. And when I altboot'd into the Opie rootfs binary, it hung at boot when it got to the "populating /dev" message.
So I kept the 26-July kernel but now tried installing the 26-July Hentges Opie image directly into flash. I then installed cardfs. Unfortunately, Opie would hang after I ran certain programs (such as scummvm) that used to worked before.
I even tried downgrading just the kernel, back to 17-July and keeping the 26-July image. But scummvm still didn't work right so I gave up. I've moved back to the 17-July Hentges kernel and image.
Do you know how many changes there are between the 17-July and 26-July kernel and image?
A new image is online (http://hentges.net/tmp/Poodle-Kernel-2.6/26-JUL-06/),
happy flashing
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136462\"][{POST_SNAPBACK}][/a][/div]
-
Can I put in a request to get WPA crypto modules added to the kernel image? I'm talking about ieee80211_crypt_tkip (which I need) and ieee80211_crypt_ccmp. I connect to two wireless networks about 99% of the time and they both use WPA/TKIP Enterprise.
-
Can I put in a request to get WPA crypto modules added to the kernel image? I'm talking about ieee80211_crypt_tkip (which I need) and ieee80211_crypt_ccmp. I connect to two wireless networks about 99% of the time and they both use WPA/TKIP Enterprise.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136898\"][{POST_SNAPBACK}][/a][/div]
Those should be in the feeds if they were built as modules
-
Those should be in the feeds if they were built as modules
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136900\"][{POST_SNAPBACK}][/a][/div]
Well, I couldn't find a feed for the test images, so I built the linux-openzaurus-2.6.17 kernel for poodle myself, and that gave me all the modules I needed (and then some) as .ipk files. The whole batch of module packages is only 3.7MB so if anyone wants any of them I can post them my server.
-
Could you please post these modules? Also, how did you build the kernel? Just "bitbake virtual/kernel"?
Thanks.
Those should be in the feeds if they were built as modules
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136900\"][{POST_SNAPBACK}][/a][/div]
Well, I couldn't find a feed for the test images, so I built the linux-openzaurus-2.6.17 kernel for poodle myself, and that gave me all the modules I needed (and then some) as .ipk files. The whole batch of module packages is only 3.7MB so if anyone wants any of them I can post them my server.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136934\"][{POST_SNAPBACK}][/a][/div]
-
Could you please post these modules? Also, how did you build the kernel? Just "bitbake virtual/kernel"?
Thanks.
The modules are attached to this message. All the kernel-module-*.ipk files built by bitbake are in a single .tar.gz file. Beware, some of them are already provided by the test image and will not install. Also, you can fetch individual .ipks from this address:
http://www.oakcourt.dyndns.org/~andrew/lin...ules-2.6.17-r9/ (http://www.oakcourt.dyndns.org/~andrew/linux/zaurus/kernel-modules-2.6.17-r9/)
It is not a feed, though. I haven't figured out how to generate those.
I created them by building 'linux-openzaurus-2.6.17' out of the .oz354x branch. I had hengtes CVS in my BBPATH, but I don't think that was necessary. See 'GettingStarted' on the OpenEmbedded wiki if you need more help.
-
It is not a feed, though. I haven't figured out how to generate those.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136945\"][{POST_SNAPBACK}][/a][/div]
ipkg-make-index -p Packages .
-
ipkg-make-index -p Packages .
[/code]
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136947\"][{POST_SNAPBACK}][/a][/div]
Alright, thanks. It should be a feed now:
src kernel-modules-test http://www.oakcourt.dyndns.org/~andrew/linux/zaurus/kernel-modules-2.6.17-r9/
Any problems, let me know.
-
Speaking of the kernel, hotplug seems to not be working, at least for PCMCIA. I have to 'modprobe hostap_cs' or whatever to activate my CF cards (wifi and bluetooth). It works on my laptop (also 2.6.17), but I am out of date on how hotplug/udev operates these days (/proc/sys/kernel/hotplug is empty) so I've been poking around /proc and /sys on the Z and on my laptop, comparing them to figure out what's missing.
Incidentally, udev seems out-of-date (084). My laptop has 093. Is there a reason for this or could this be the reason that hotplugging CF cards isn't working?
-
Thanks. I wound up just compiling the kernel on my own and was able to get to the modules. I noticed that kernel-module-ip-tables and kernel-module-ipsec were not included. Do you know how we can get these compiled too? The usual way is to go into the configuration file and specify the options but I don't know how it's done via OE.
Also, this is slightly unrelated but when I tried to bitbake fbvncserver-kmodule, OE assumed that I wanted to use the poodle 2.4.18-embedix kernel instead and tried to download the source code for that. When I did a bitbake -D -D -D fbvncserver-kmodule, I couldn't see poodle-2.6 as one of the options for a kernel. Any ideas?
Could you please post these modules? Also, how did you build the kernel? Just "bitbake virtual/kernel"?
Thanks.
The modules are attached to this message. All the kernel-module-*.ipk files built by bitbake are in a single .tar.gz file. Beware, some of them are already provided by the test image and will not install. Also, you can fetch individual .ipks from this address:
http://www.oakcourt.dyndns.org/~andrew/lin...ules-2.6.17-r9/ (http://www.oakcourt.dyndns.org/~andrew/linux/zaurus/kernel-modules-2.6.17-r9/)
It is not a feed, though. I haven't figured out how to generate those.
I created them by building 'linux-openzaurus-2.6.17' out of the .oz354x branch. I had hengtes CVS in my BBPATH, but I don't think that was necessary. See 'GettingStarted' on the OpenEmbedded wiki if you need more help.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136945\"][{POST_SNAPBACK}][/a][/div]
-
To build a kernel 2.6 for poodle, you should specify what kernel version you want in your local.conf file. There is a variable (the name of which escapes me ATM) for specifying the kernel series (2.4 or 2.6) on machines that support it (like poodle). You can also set PREFERRED_PROVIDER and PREFERRED_VERSION variables for the kernel there. See the OpenEmbedded wiki and other .conf files for examples and more information.
The configuration file for the kernel is located in packages/linux/linux-openzaurus-2.6.17/defconfig-poodle (I think). You can just modify that file if you want to change some options.
-
Thanks. I wound up just compiling the kernel on my own and was able to get to the modules. I noticed that kernel-module-ip-tables and kernel-module-ipsec were not included. Do you know how we can get these compiled too? The usual way is to go into the configuration file and specify the options but I don't know how it's done via OE.
Also, this is slightly unrelated but when I tried to bitbake fbvncserver-kmodule, OE assumed that I wanted to use the poodle 2.4.18-embedix kernel instead and tried to download the source code for that. When I did a bitbake -D -D -D fbvncserver-kmodule, I couldn't see poodle-2.6 as one of the options for a kernel. Any ideas?
Unfortunately, fbvncserver-kmodule needs some TLC... It is a 2.4 style module and does not know how to compile for a 2.6 kernel. If you have some experience at porting linux drivers from 2.4 to 2.6, you should be able to get it working. I have looked at it, but I am still a wee noob when it comes to both module code and bitbake..
-
Thanks. I wound up just compiling the kernel on my own and was able to get to the modules. I noticed that kernel-module-ip-tables and kernel-module-ipsec were not included. Do you know how we can get these compiled too? The usual way is to go into the configuration file and specify the options but I don't know how it's done via OE.
Also, this is slightly unrelated but when I tried to bitbake fbvncserver-kmodule, OE assumed that I wanted to use the poodle 2.4.18-embedix kernel instead and tried to download the source code for that. When I did a bitbake -D -D -D fbvncserver-kmodule, I couldn't see poodle-2.6 as one of the options for a kernel. Any ideas?
Unfortunately, fbvncserver-kmodule needs some TLC... It is a 2.4 style module and does not know how to compile for a 2.6 kernel. If you have some experience at porting linux drivers from 2.4 to 2.6, you should be able to get it working. I have looked at it, but I am still a wee noob when it comes to both module code and bitbake..
[div align=\"right\"][a href=\"index.php?act=findpost&pid=137181\"][{POST_SNAPBACK}][/a][/div]
why not use x11vnc or xdamagevnc?
-
Thanks. I wound up just compiling the kernel on my own and was able to get to the modules. I noticed that kernel-module-ip-tables and kernel-module-ipsec were not included. Do you know how we can get these compiled too? The usual way is to go into the configuration file and specify the options but I don't know how it's done via OE.
Also, this is slightly unrelated but when I tried to bitbake fbvncserver-kmodule, OE assumed that I wanted to use the poodle 2.4.18-embedix kernel instead and tried to download the source code for that. When I did a bitbake -D -D -D fbvncserver-kmodule, I couldn't see poodle-2.6 as one of the options for a kernel. Any ideas?
Unfortunately, fbvncserver-kmodule needs some TLC... It is a 2.4 style module and does not know how to compile for a 2.6 kernel. If you have some experience at porting linux drivers from 2.4 to 2.6, you should be able to get it working. I have looked at it, but I am still a wee noob when it comes to both module code and bitbake..
[div align=\"right\"][a href=\"index.php?act=findpost&pid=137181\"][{POST_SNAPBACK}][/a][/div]
why not use x11vnc or xdamagevnc?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=137182\"][{POST_SNAPBACK}][/a][/div]
With Opie ?????
-
Do x11vnc or xdamagevnc work with Opie? Also, do you know how to compile kernel-module-ip-tables or kernel-module-ipsec? I noticed that there is a .config in /stuff/build/tmp/work/linux-openzaurus-2.6.17. If I modify it to include these kernel modules and do a bitbake linux-openzaurus-2.6.17, will the modules be compiled or do I need to specify them somewhere else?
The second question is unrelated to the first but I figured you may know the answer.
Thanks.
Thanks. I wound up just compiling the kernel on my own and was able to get to the modules. I noticed that kernel-module-ip-tables and kernel-module-ipsec were not included. Do you know how we can get these compiled too? The usual way is to go into the configuration file and specify the options but I don't know how it's done via OE.
Also, this is slightly unrelated but when I tried to bitbake fbvncserver-kmodule, OE assumed that I wanted to use the poodle 2.4.18-embedix kernel instead and tried to download the source code for that. When I did a bitbake -D -D -D fbvncserver-kmodule, I couldn't see poodle-2.6 as one of the options for a kernel. Any ideas?
Unfortunately, fbvncserver-kmodule needs some TLC... It is a 2.4 style module and does not know how to compile for a 2.6 kernel. If you have some experience at porting linux drivers from 2.4 to 2.6, you should be able to get it working. I have looked at it, but I am still a wee noob when it comes to both module code and bitbake..
[div align=\"right\"][a href=\"index.php?act=findpost&pid=137181\"][{POST_SNAPBACK}][/a][/div]
why not use x11vnc or xdamagevnc?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=137182\"][{POST_SNAPBACK}][/a][/div]
-
I was wondering where the latest poodle kernel is? I've been watching this thread and tried to download the july 26 and I get a 404 error...
Any ideas?
-
I was wondering where the latest poodle kernel is? I've been watching this thread and tried to download the july 26 and I get a 404 error...
Any ideas?
Here:
http://hentges.net/tmp/do_not_use/poodle/ (http://hentges.net/tmp/do_not_use/poodle/)
-
Thanks for the link, but where is the NAND images. I thought they were there previously. I need a 250 NAND that goes back to Sharp image. Right now I only have the one from galacticslacker that is a TheKompany ROM.
Any ideas???