Re: [Angstrom-distro-users] Support for Sharp SL-C3100 (spitz)
On Fri, Jun 7, 2013 at 12:27 AM, Yan Seiner y...@seiner.com wrote: Hi Eric: My needs are (fairly) simple I am trying to get an image with a browser that runs javascript, supports sound output, and has minicom, picocom, or some similar serial communications app. the 2007.12 image which boots fine does not have a browser nor minicom. The later images that hang on the pxa... line do - but they don't boot. I also found zubuntu, which is based on hardy heron, and boots fine, runs firefox, but does not have minicom available and the repositories no longer exist. :( http://www.omegamoon.com/blog/static.php?page=ZaurusUbuntu I don't mind building my own images; I do a lot of work with OpenWRT so I am used to building embedded stuff, as long as it is somewhat user friendly :) So yes, I'd be willing to build it if I can get a recipe. The pxa2xx-udc pxa2xx-udc: UDC connecting message is apparently due to a race condition in the boot scripts somewhere. I have not tried to track that down. --Yan Eric Edwin wrote: Hi Yan, I have a Zaurus Spitz (SL-C3000) Terrier (SL-C3200). The most recent Angstrom image I managed to get to boot OK was from; http://www.angstrom-distribution.org/releases/2007.12/images/ The last narcissus image I built in February 2012 failed to proceed past the message; 'pxa2xx-udc pxa2xx-udc: UDC connecting' I have managed to build a working Open Embedded Core image with 3.2.18 kernel (core-image-minimal core-image-sato). You also have the option of; Zgrom For the past ~3months the OpenEmbedded built image (~3.2.32 kernel) has errors therefore please take this into account if you decide to build your own image. If you require any more info please contact me. Best regards, Eric Date: Wed, 5 Jun 2013 10:25:20 -0700 From: y...@seiner.com To: angstrom-distro-users@linuxtogo.org Subject: [Angstrom-distro-users] Support for Sharp SL-C3100 (spitz) I have tried building 2011.03 on narcissus for a Sharp SL-C3100. I badly need WPA-PSK support, and I need a newer kernel than the 2007.11 release offers. I can't get the image to boot. It hangs at Can't open /dev/misc/rtc: no such file or directory. It never starts the GUI. Does anyone have a newer image with a newer kernel that supports WPA-PSK? Thanks. -- Project Management Consulting and Training http://www.ridgelineconsultingllc.com ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users !DSPAM:51b10295236781804284693! -- Project Management Consulting and Training http://www.ridgelineconsultingllc.com ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users Hi, unfortunately the images built by the old Narcissus have issues with udev and don't have any maintainance. However there is today a new Narcissus based on oe-core: it just needs to be expanded with configuration for Zaurus. I plan to send the setup as soon as possible, atm I'm still working about reducing 3.8 kernel size. Cheers Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Support for Sharp SL-C3100 (spitz)
On Thu, Jun 6, 2013 at 11:28 PM, Eric Edwin eric_ed...@hotmail.com wrote: Hi Yan, I have a Zaurus Spitz (SL-C3000) Terrier (SL-C3200). The most recent Angstrom image I managed to get to boot OK was from; http://www.angstrom-distribution.org/releases/2007.12/images/ The last narcissus image I built in February 2012 failed to proceed past the message; 'pxa2xx-udc pxa2xx-udc: UDC connecting' I have managed to build a working Open Embedded Core image with 3.2.18 kernel (core-image-minimal core-image-sato). You also have the option of; Zgrom For the past ~3months the OpenEmbedded built image (~3.2.32 kernel) has errors therefore please take this into account if you decide to build your own image. If you require any more info please contact me. Best regards, Eric No idea about those errors... Are you referring to Angstrom images or images built with the simpler [oe-core + meta-initramfs + meta-handheld] setup? Cheers Andrea Date: Wed, 5 Jun 2013 10:25:20 -0700 From: y...@seiner.com To: angstrom-distro-users@linuxtogo.org Subject: [Angstrom-distro-users] Support for Sharp SL-C3100 (spitz) I have tried building 2011.03 on narcissus for a Sharp SL-C3100. I badly need WPA-PSK support, and I need a newer kernel than the 2007.11 release offers. I can't get the image to boot. It hangs at Can't open /dev/misc/rtc: no such file or directory. It never starts the GUI. Does anyone have a newer image with a newer kernel that supports WPA-PSK? Thanks. -- Project Management Consulting and Training http://www.ridgelineconsultingllc.com ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] booting hangs at UDC connecting
On Fri, Jun 8, 2012 at 10:01 AM, Morgan Gangwere indr...@earfolds.com wrote: Its a long known problem. I've never gotten the Akita booting right ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users I suspect it is the old issue of udev cache vs. root RO at boot. You can try to disable it in /etc/default/udev # Comment this out to disable device cache -DEVCACHE=/etc/dev.tar +#DEVCACHE=/etc/dev.tar Cheers Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] unable to mount root fs with kernel 3.0.1 on hx4700
On Tue, May 29, 2012 at 1:39 PM, Paul Parsons lost.dista...@yahoo.com wrote: Hello, --- On Tue, 29/5/12, wiselynx.na...@fastwebnet.it wiselynx.na...@fastwebnet.it wrote: hello everybody, I'm trying to build a working and updated Angstrom image for my hx4700. I follow ed these instructions: http://www.angstrom-distribution.org/building-angstrom and with a bit of struggle I was able to produce both a kernel zImage and some r oot filesystems file in jffs2 format. I'm using SDG bootloader 1.2.4, only slightly hexedited to write kernel output o n framebuffer instead of serial. After flashing both the kernel and the root fs, the kernel hangs with the following message: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) There is also I googled around searching for a solution, but the only things I found is http:/ /comments.gmane.org/gmane.linux.distributions.angstrom.devel/3837 which seems to describe exactly the same problem. Someone said that solded with a hack, but th ere is no mention of the hack itself I think I know what the problem is. The SDG bootloader provides, and the Linux kernel expects, a command line which includes the MTD partition information. The format of the MTD partition information is defined in drivers/mtd/cmdlinepart.c in the kernel source: mtdparts=mtddef[;mtddef] mtddef := mtd-id:partdef[,partdef] etc... The mtd-id provided by the SDG bootloader is ipaq. The mtd-id expected by the Linux kernel is physmap-flash. Thus the Linux kernel does not recognize the MTD partition information provided by the SDG bootloader. There are two fixes: 1. Modify the SDG bootloader to provide physmap-flash. This is what I do; the SDG bootloader 1.2.5 source is available. 2. Modify the Linux kernel to expect ipaq. This is probably the easier option. For example this patch might work (I haven't tested it and it was derived from the linux-3.4.0 sources): No exact idea of ipaq's kernels but couldn't you just use CONFIG_MTD_CMDLINE_PARTS=y as we do on Zaurus? Cheers Andrea diff --git a/drivers/mtd/cmdlinepart.c b/drivers/mtd/cmdlinepart.c index ddf9ec6..707eaf5 100644 --- a/drivers/mtd/cmdlinepart.c +++ b/drivers/mtd/cmdlinepart.c @@ -320,7 +320,7 @@ static int parse_cmdline_partitions(struct mtd_info *master, unsigned long offset; int i; struct cmdline_mtd_partition *part; - const char *mtd_id = master-name; + const char *mtd_id = ipaq; /* parse command line */ if (!cmdline_parsed) Regards, Paul ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] unable to mount root fs with kernel 3.0.1 on hx4700
On Tue, May 29, 2012 at 4:01 PM, Paul Parsons lost.dista...@yahoo.com wrote: --- On Tue, 29/5/12, wiseLYNX wiselynx.na...@fastwebnet.it wrote: 1. Modify the SDG bootloader to provide physmap-flash. This is what I do; the SDG bootloader 1.2.5 source is available. where? I found only links to the sdgsystems site and to the site of someone called kmeaw, but it is not available anymore on both sites. http://sdgsystems.net/pub/ipaq/hx4700/src/ 2. Modify the Linux kernel to expect ipaq. This is probably the easier option. For example this patch might work (I haven't tested it and it was derived from the linux-3.4.0 sources): diff --git a/drivers/mtd/cmdlinepart.c b/drivers/mtd/cmdlinepart.c index ddf9ec6..707eaf5 100644 --- a/drivers/mtd/cmdlinepart.c +++ b/drivers/mtd/cmdlinepart.c @@ -320,7 +320,7 @@ static int parse_cmdline_partitions(struct mtd_info *master, unsigned long offset; int i; struct cmdline_mtd_partition *part; - const char *mtd_id = master-name; + const char *mtd_id = ipaq; /* parse command line */ if (!cmdline_parsed) I tried the latter, and it didn't work: same exact result :-( I may have got it wrong then. But the mismatched mtd-id is an issue that needs to be addressed before the CONFIG_MTD_CMDLINE_PARTS (cmdlinepart.c) driver will work with the SDG bootloader. An alternative might be to override the command line with the CONFIG_CMDLINE config option. ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users About bad commandline/broken/obsolete bootloaders: I was thinking you could use a first kernel booting an initramfs with kexecboot, then the commandline for the kexec'ed kernel could be read from a file (or mangled in the code as done for Zaurus). BTW it seems the issue is very old, as mentioned in the old bootmenu-images in oe-classic http://cgit.openembedded.org/openembedded/tree/recipes/initrdscripts/files/01-bootldr-buster.sh?h=org.openembedded.dev Cheers Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] NAND boot on akita not possible?
On Sat, Aug 20, 2011 at 6:52 AM, Morgan Gangwere mgangw...@cnm.edu wrote: On Fri, Aug 12, 2011 at 11:22:39AM +0200, Andrea Adami wrote: On Sat, Aug 6, 2011 at 11:22 PM, Morgan Gangwere mgangw...@cnm.edu wrote: hi folks, ive been trying to get my new akita to boot from the NAND for some time through the kexecboot posted on theite but to no avail. heres what ive tried so far... - extracting the old initrds and adding the requisite kernel-cmdline and friends [kexecboot flails and cant find it] - getting a jffs2 frm narcissus and flashing that as initrd.bin w/ kexecboot as zImage [again kexecboot wont see it...] - running the whole show from an sd card [gets somewhere but fails along the way] - making my own initrd.bin with mjfs.jffs2 -r rootfs/ -o initrd.bin what magic am i missing here? Just to rule out all doubts, please do restore an original Sharp image as prerequisite (original partitioning). Way ahead of you there. I flashed Cacko on it just to make sure it was all OK. It was running pdaXrom when I got it. The original owner assured me that he had not dinked with the partitioning. So... Original partitioning (50/50 mix / and /home) is still all there. The fact you used Cacko and or pdaxrom does not exclude you have custom partitioning. In fact, I always repartitioned using those. First two methods are ok, not error-prone.You seem to know what you are doing, maybe one thing: kexecboot looks for /boot/boot.cfg and not for kernel-cmdline anymore. See the And Friends -- I included boot.cfg and kernel-cmdline just because I'm too used to dealing with the Collie still. Painful sidenote: the Just Busybox build is really *JUST* BusyBox -- no kernel at all. This bummed me heavily when I was unable to find /boot/boot.cfg and such. Second Painful Sidenote: Narcissus won't generate a JFFS2 image anymore. Or an ext2. We test on other clamshells regularly. FWIW akita has just a different eraseblock size, nothing more. I figured as much :) I'm happily Running on the old 2007.12 release on NAND -- but its just so painful to not have an up-to-date version of GPE or Opie. My dmesg output shows a lot of Bad Eraseblock Size notes -- I'd assume (naiively) that this is benign? I don't know...long ago I've heard about some akita having 0x04000 erasesize like other clamshells. Would be rare. Please post the output of cat proc/mtd. We'd expect dev:sizeerasesize name mtd0: 006b 0002 Filesystem mtd1: 0070 0002 smf mtd2: 003a 0002 root mtd3: 003f 0002 home You can also try using console for flashing: Kernel: nandlogical /dev/mtd1 WRITE 0x0E 0x14 zImage.bin Rootfs: flash_eraseall -j /dev/mtd2 nandwrite /dev/mtd2 rootfsA.jffs2 Optionally: flash_eraseall -j /dev/mtd3 nandwrite /dev/mtd3 rootfsB.jffs2 (using updater.sh rootfsA - initrd.bin rootfsB - home.bin) Regards Andrea I've tried running from Altboot on the SD card and I get a Kernel Not Syncing panic so I've just been Living With What I Have. -- Morgan Gangwere -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
[Angstrom-distro-users] Linux-kexecboot 2.6.39
Hello, there are fresh installkits for Zaurus, built using oe-core and meta-zaurus layers at http://projects.linuxtogo.org/frs/?group_id=55 - linux-kexecboot 2.6.39.3 kernels from OpenEmbedded (and pending patches) - containing kexecboot v. 0.5.9 - compiled with gcc version 4.6.1 20110627 (prerelease) a.k.a. (gcc-cross-4.6.1+svnr175454-r7) I have successfully tested on following machines (NAND, CF, SD): - c7x0 - poodle - spitz Please report about collie and akita (possibly on real device, not qemu-arm) Thanks Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Linux-kexecboot 2.6.39
On Wed, Aug 17, 2011 at 9:53 AM, Koen Kooi k...@dominion.thruhere.netwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Op 17-08-11 09:35, Andrea Adami schreef: Hello, there are fresh installkits for Zaurus, built using oe-core and meta-zaurus layers at http://projects.linuxtogo.org/frs/?group_id=55 - linux-kexecboot 2.6.39.3 kernels from OpenEmbedded (and pending patches) - containing kexecboot v. 0.5.9 - compiled with gcc version 4.6.1 20110627 (prerelease) a.k.a. (gcc-cross-4.6.1+svnr175454-r7) Why not use the stock angstrom 4.5.4? We were plagued by a mysterious kexecboot bug happening since long time. The bug was present in openembedded-classic as well as building with Angstrom setup-scripts. Surprisingly enough compiling with gcc4.6 seems to solve the issue. The issue is rather strange and is still under observation. I'll follow-up in the other thread about toolchain for Angstrom-next. Regards Andrea -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFOS3OLMkyGM64RGpERAuXaAKCndsVnw9IoJBSOpTg/8djdcRCAjgCgnhfi SWtjrZoZHGVpNjqR65AfogY= =9rcy -END PGP SIGNATURE- ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] NAND boot on akita not possible?
On Sat, Aug 6, 2011 at 11:22 PM, Morgan Gangwere mgangw...@cnm.edu wrote: hi folks, ive been trying to get my new akita to boot from the NAND for some time through the kexecboot posted on theite but to no avail. heres what ive tried so far... - extracting the old initrds and adding the requisite kernel-cmdline and friends [kexecboot flails and cant find it] - getting a jffs2 frm narcissus and flashing that as initrd.bin w/ kexecboot as zImage [again kexecboot wont see it...] - running the whole show from an sd card [gets somewhere but fails along the way] - making my own initrd.bin with mjfs.jffs2 -r rootfs/ -o initrd.bin what magic am i missing here? Just to rule out all doubts, please do restore an original Sharp image as prerequisite (original partitioning). First two methods are ok, not error-prone.You seem to know what you are doing, maybe one thing: kexecboot looks for /boot/boot.cfg and not for kernel-cmdline anymore. We test on other clamshells regularly. FWIW akita has just a different eraseblock size, nothing more. Regards Andrea -- morgan gangwere -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Getting my collie to boot
iirc one of the old kexecboot kernels for collie was missing ATA/CF boot ability. Sorry, cannot remember which version. I started to unify features after 2.6.32. (I have any collie so cannot test personally, can just build) Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Collie (Sharp Zaurus SL-5500) back working properly
Hi, here a log of vanilla 2.6.38-c3 booting: http://pastebin.com/se3BMrmU This kernel was still lacking the [PATCH] collie: do actually pass locomo_info to locomo driver http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.38.y.git;a=commit;h=34cd2d38db423a991a36d14e9f79e98993addd07 2.6.39 and 3.0-rc4 are under testing. Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Collie (Sharp Zaurus SL-5500) back working properly
On Sat, Jun 25, 2011 at 9:25 PM, J.A. Bezemer j.a.bezemer-angst...@opensourcepartners.nl wrote: cut The fact that recently all Collie kernel patches were removed from OE git Master as being obsolete, makes me fear the worst... Don't worry ;) 2.6.2x-rp kernels have been removed, yes, in favour of more modern kernels (2.6.39+). Support for Collie is supposedly integrated although I have no idea of its current status. I see you have found one of the prebuilt 2.6.3x kernels to be non-functioning, that's unfortunate. The way forward however IMHO is to try to get any bugs in newer kernels fixed. 2.6.2x kernels were almost working but only with now obsoleted userspace. There is no viable alternative, we have to aim at linux 3.0. From the 'family' point of view, the situation of 2.6.39 is very promising: vanilla kernel seems having only minor keymap issues (well, and touchscreen). Outstanding thing is power management: in that regard clamshell devices have more upstream support (basically only spitz). 2.6.31 has been removed too, including all of the Collie patches. 2.6.38 only has a defconfig that pretends to be for Collie, but I'd wager that nobody has ever built and tested it. AFAIK at least USB networking is not in mainline kernels at all, let alone the collie-specific details. So it is not just _bugs_ in newer kernels, there is actually missing functionality that has never been pushed upstream (or has never been accepted). The defconfig state has been 'normalized' in order to be coherent for all zaurus models. Surely more features/modules have to be enabled now. We are open to any suggestion/patch. I can personally test only corgi, spitz and poodle, so pxa devices. Regarding collie, last confirmation I have is that it boots fine 2.6.37 (keyboard was not registered before). I've been taught to never throw away my old trousers until I'm sure the new pair actually fits. Unfortunately OE seems to have another opinion... Keeping userspace compiling/working for 2.6.2x is imho today a waste of time. Think about udev, hal (deprecated),... cut Please note the latest kernels deprecated the old ATA driver thus CF is now /dev/sd*. We'll upload asap 2.6.39.1 kexecboot-kernels for the 'new' userland. Finally, the future of zaurus support depends on the support the meta-handhelds layer (for oe-core) will have. Anne Bezemer Thanks for your time Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] bitbake quilt-native unifdef failures
... FATAL: quilt-native-0.48: http://download.savannah.gnu.org/releases/quilt/quilt-0.48.tar.gz cannot check archive integrity ... Hi, please delete quilt-0.48.tar.gz and its .md5. It looks your download was bad. The recipes expects following hashes: SRC_URI[md5sum] = f77adda60039ffa753f3c584a286f12b SRC_URI[sha256sum] = 73fd760d3b5cbf06417576591dc37d67380d189392db9000c21b7cbebee49ffc Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Kexecboot on ipaqs
On Tue, Nov 23, 2010 at 4:59 AM, Collin Rickford shredfore...@gmx.com wrote: I used kexecboot on my hx4700 to boot some narcissus builds I made, and it seemed to work alright. At the time, I had SDG bootloader installed and the kexecboot kernel flashed to boot from sd. For some reason, It only worked for Angstrom builds and not Familiar builds, and it couldn't boot from internal memory (rom). This was awhile ago, has there been any new development on kexecboot? Hello, kexecboot expects a /boot/zImage or a /zImage (zImage.bin is also ok). You can add a configuration file (/boot/boot.cfg) to set your commandline. Please check the /boot of the Narcissus image. The latest version just adds a new GUI and some minor fixes. Regards Andrea. P.S. We'll add a README asap ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] ipaq H2200 : need the lab bootloader
Hello, while you're experimenting, why not test linux-kexecboot as bootloader? There are old versions for h2200 and hx4700: http://www.angstrom-distribution.org/demo/kexecboot/ Linux-kexecboot is full maintained in OpenEmbedded, just lacking ipaq testers... Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] ipaq H2200 : need the lab bootloader
For r26, you can build yourself the latest version in the repository just remember to set DEFAULT_PREFERENCE = -1 in the OpenEmbedded recipe http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux-handhelds-2.6_2.6.21-hh20.bb Obviously I meant to 'unset' that -1 preference, setting it to 1. Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] [zaurus] linux-kexecboot-2.6.36-r24-new-GUI
On Thu, Nov 4, 2010 at 1:49 AM, Marty tux2...@gmail.com wrote: ok, I have the Zaurus SL-5600 Poodle. I just got this handheld and am learning about how to flash the ROM. I've been messing with Angstrom for about 2 weeks now and have gotten all the installable 2007.12 images to boot that are here: http://www.angstrom-distribution.org/releases/2007.12/images/poodle these all contain 3 files: updater.sh, zImage.bin, initrd.bin your compressed file only contained 2 files: updater.sh and zImage.bin I also downloaded and uncompressed a narcissus file for poodle that uncompressed to reveal an entire Linux system. I'm thinking these are the same as the initrd.bin file that's not in kexecboot. See http://wiki.openembedded.org/index.php/Zaurus You need to flash a special zImage, afterward no more kernel flashing. However, when I flash my Zaurus with only your 2 files it's very quick and then the unit will not start after pressing the reset button. Everything (your 2 files and the narcissus Linux system) are on my SD card. What am I doing wrong? Nothing... poodle doesn't boot with vanilla kernel. Marty Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Angstrom FAQ
Other recent info are here: http://wiki.openembedded.org/index.php/Zaurus That said, collie and especially poodle are the *least* maintained Zaurus devices (not enough devs-testers). Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
[Angstrom-distro-users] [zaurus] linux-kexecboot-2.6.36-r24-new-GUI
Hello, I've uploaded Zaurus 2.6.36 kexecboot kernels with the new gui: http://projects.linuxtogo.org/projects/zaurus/ Please test and report, mostly interested on collie, poodle, tosa. Regards Andrea P.S. Tested on: c7x0 : boots, kexecboot is ok (power button has no effect ?) spitz: boots, kexecboot is ok, (some strange freezes, power button dims the screen) ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] c7x0 Narcissus status
As for akita, I can say that we have big hopes for 2.6.36: last news are Subject: Re: 2.6.36-rc1 on zaurus: bluetooth regression Good news is that it boots, suspends and resumes. Bad news is that bluetooth broke for me. I'm using CF bluetooth card. Well' update asap. Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Latest Akita kernel?
On Tue, Sep 21, 2010 at 9:24 PM, Kelly Price strredw...@gmail.com wrote: What's the latest precompiled kernel for the Sharp Akita series? 2.6.20 is unsupported by any distro now. At the moment still 2.6.26. We have big hopes for 2.6.36: last news are Subject: Re: 2.6.36-rc1 on zaurus: bluetooth regression Good news is that it boots, suspends and resumes. Bad news is that bluetooth broke for me. I'm using CF bluetooth card. Well' update asap. Regards Andrea On Tue, Sep 21, 2010 at 9:24 PM, Kelly Price strredw...@gmail.com wrote: What's the latest precompiled kernel for the Sharp Akita series? 2.6.20 is unsupported by any distro now. Sent from my iPhone ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] minimal-image as a ramdisk
On Sat, Sep 18, 2010 at 9:52 PM, Pablo Vasquez pevasq...@gmail.com wrote: Greetings. I have been following cbrake's instructions (which are also in oe/conf/machine/cm-x270.conf) to build an angstrom-minimal-image with uclibc for use as a ramdisk. But the resulting image is always too big to fit in the NOR. Is there a tidy way of generating a minimal-image for use as a ramdisk which does not have a kernel image in it? This looks like it would decrease the image's size quite enough to get it into the NOR. Would this result in any broken stuff? thanks. Pablo. ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users Hi Pablo, there are two knobs to reduce the size of minimal-image: change DISTRO and use minimal or even micro * and/or * instead of minimal-image use an initramfs-* image (uclibc or even klibc). This kind of rootfs seems more suited to your purpose. Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] [zaurus] please test actual Narcissus images
FWIW the autobuilder did not yet rebuild for our machines...so please wait. Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
[Angstrom-distro-users] [zaurus] please test actual Narcissus images
Hello, the udev vs.old kernels problem should be solved: please test actual Narcissus images based on .dev on your Zaurus and report issues here [1]. Thanks in advance Andrea [1] On my C860 I see a strange issue: OOM during udev init script, only booting jffs2 images from nand. Same unpacked rootfs can boot from SD/CF. Time for serial cable... ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] c860 kexecboot working, narcissus rootfs on SD almost...
On Mon, Jul 12, 2010 at 3:44 PM, John Walker johnwal...@mac.com wrote: Any update on this Andrea? On 16 Jun 2010, at 11:10, Andrea Adami wrote: Hi, kernel 2.6.34 is needing more work than expected : fast recharge is practically broken :/ In the meantime Stanislav provided a patch for udev-141 and we are testing it. Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Update to Collie install page proposition.
Felipe, I fixed some imprecisions, mostly due to my bad copy and paste... Thanks Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Update to Collie install page proposition.
* rootfs.tar.gz -- Attain from narcissus and unpack it to SD card or CF card (formatted with ext2 filesystem). For kexecboot (not for flashing) there is no need to have it ext2, could be ext3, ext4, even fat if it's just a kernel w/out rootfs. Also! Now that you have kexecboot installed you can boot other images/OSes(Like Openzaurus) without having to flash the collie(unless you want it in nand). For kexecboot on collie *only* : you should be able to boot your 'OpenZaurus' image resident in nand once you follow this steps: 1 create a partition on a MMC/SD card [2] 2 create an empty /boot directory 3 create/copy boot.cfg 1) install cacko and repartition e.g. mtd2 to 19mb as suggested 2) flash kexecboot kernel 3) create a small (few mb) /boot partition on SD/CF 4) copy the OpenZaurus (or a 2.4 kernel) in /boot and rename it zImage 5) create /boot/boot.cfg: DEFAULT=OpenZaurus LABEL=OpenZaurus KERNEL=/boot/zImage APPEND=console=ttySA0,115200n8 console=tty1 noinitrd rw root=/dev/mtdblock2 rootfstype=jffs2 debug This is the same trick we used trying to boot older (2.4 Cacko) images on Zaurus: unfortunately on models with resizable partitions there is an BIG problem being the target 2.4. kernel cannot correctly get the atag/cmdline mtdparts passed by kexec. Result: mtdparts misdetection. Old kernels had patches to be able to receive the bootparams from the bootloader. Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Installing on a collie.
Interesting. Well maybe we are on to something because I believe narcissus is using 2.6.31 for the collie. At least thats what Ive discovered when I look in the /boot folder. I can give specifics when I get home later. yes, collie kernel was even pushed to 2.6.31! Same applies to this one...should be sane. Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] kexecboot test new version c7x0
John, the online image builder (Narcissus) doesn't let you choose the version. I meant *self-built* images, sorry if it was too cryptic. Andrea On Thu, May 13, 2010 at 1:14 AM, John Walker johnwal...@mac.com wrote: Thanks Andrea Will look at online builder to see what you mean by prefer_124 Sounds promising. John So, for today, if you build your image you can simply prefer udev_124. Otherwise, be advised Angstrom online builder gives udev_151, so try to avoid udev. ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] kexecboot test new version c7x0
And for all the whining about udev, I have received exactly *zero* feedback on the udev static patch I posted. One person offered to test. Koen, I applied the patch with the hammer and it seems to work (at least console-image came to login) BUT the patch as it is cannot be packaged. How should the fle magically become packaged with udev_151? A brief chat with XorA did not clear my doubts... I also asked (weeks ago!) for newer kexecboot images to be uploaded to the angstrom site and that also hasn't happened. Well, there is anything new since dec 2009, just new testing kernel versions. Latest stable images (2.6.2x) are in linuxtogo / zaurus-devel Kexecboot completion is expected in June (at least this is what Yuri said to me last time). We all have been really busy last months, and the little time was spent fighting with bitbake changes or with new unexpected kernel regressions :/ Andrea P.S. I sent a couple of patch months ago to sync a bit stable with dev wrt Zaurus. These got ignored too... If you mean I can rediff and finally sync the two distros (now would be good moment to pin 2.6.2x kernels in stable as soon as we move to 2.6.3x) ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] kexecboot test new version c7x0
Sorry for the lack of updates, thi sis the situation: 1) we are testing the 2.6.34 kernels. There are big hopes these will be default for Zaurus (very probable for spitz and c7x0, outstanding issue being power mgmt) 2) if we jump on 2.6.34 the issues with udev (and klibc, etc, etc) will disappear alltogether, without strange hacks 3) development on some machines has slowed a bit. Some progress is expected in June (for tosa and collie) So, for today, if you build your image you can simply prefer udev_124. Otherwise, be advised Angstrom online builder gives udev_151, so try to avoid udev. Finally, no, unfortunately there are anymore updated Zaurus images to download from the Angstrom site, just 2007 stuff (bad idea, imho). Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] kexecboot test new version c7x0
The culprit is udev_151: the old 124 version works perfectly. We are testing a workaround...stay tuned! Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Testing linux-kexecboot_2.6.34-rc4
Files have been uploaded here: http://projects.linuxtogo.org/frs/?group_id=55 Thx for testing! Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
[Angstrom-distro-users] Fwd: Testing linux-kexecboot_2.6.34-rc3
-- Forwarded message -- From: Andrea Adami andrea.ad...@gmail.com Date: Sat, Apr 10, 2010 at 1:56 AM Subject: Testing linux-kexecboot_2.6.34-rc3 To: Zaurus PDA developers list zaurus-de...@lists.linuxtogo.org Hello, I've uploaded some fresh kexecboot kernels here: http://projects.linuxtogo.org/frs/?group_id=55 These are built with the current (April, 10th) kernel configuration, taken from http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/kexecboot Please test them: I tried to uniform the config used by Zaurus machines but tosa and collie are very different... Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Udev issues on c7x0, was Re: Collie ?install
We are moving from linux-rp to linux for all zaurus machines but at the moment only collie and tosa have newer kernels.Unfortunately we lack feedback about those new kernels on these devices... I'm sorry to disagree see [1] and [2] and [3]. People are ready to give feedback but unfortunately most people do not have enough time/skills to set up a dev environment. But if people provide testing bzimage you will get feedback. You see, we discovered that since some time the rootfs generated by Narcissus is not compatible anymore with old linux-rp-2.6.2x kernels (udev). I had to downgrade udev to 124 for testing: I successfully booted the images on c7x0 and others did on spitz. Tosa and colie are using kernels 2.6.27 thus these machines should not have been affected by the udev issue...so basically we'd have to devine whether the culprit is the kernel or the rootfsI personally guess the rootfs is almost sane. I'd be happy to upload some testing 2.6.34-rc3 linux-kexecboot kernels for all Zaurus models, even though 2.6.3x is not yet 100% on Zaurus. But remember: within linux-kexecboot, sound, usb, networking will be absolutely disregarded (only framebuffer and block devices are tested). If the machine boots it's just a matter of extending the kernel config and build the modules, etc.., possibly armonizing the features between machines: eventual failures booting a Narcissus or self-created rootfs.tar.gz will probably depend on broken kernel-driver or modules renaming. About x11-image, forget about it for the moment. There is still a lot of indecision with regard to xserver: some machines are using xserver-kdrive (tosa and collie use the latest xserver-kdrive-fbdev) while akita uses xserver-kdrive-1.300 which seems to be the last working one. Add to this that spitz is testing xorg-xserverI'd be not surprised to hear 'hey...the screen is frozen, all black...' or similar nice stories... Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Udev issues on c7x0, was Re: Collie install
Ok, there is no more doubt: http://git.kernel.org/?p=linux/hotplug/udev.git;a=blob;hb=HEAD;f=README -The requirements: Version =2.6.27 of the Linux kernel -CONFIG_SYSFS_DEPRECATED=y (in our defconfigs) BTW it llooks 141 too is needing CONFIG_SYSFS_DEPRECATED=n. Opinions? Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Udev issues on c7x0, was Re: Collie install
All the zaurus kernels are later than this version so not really an issue. I thought most models were mainline now so we can update to 2.6.33 anyway? We are still on 2.6.26 for clamshells (poodle is near, but still 2.6.24). angstrom. If your kernel recipe isn't using linux.inc, fix that! Ditto. Including linux-rp.inc and not linux.inc. We are moving from linux-rp to linux for all zaurus machines but at the moment only collie and tosa have newer kernels.Unfortunately we lack feedback about those new kernels on these devices... On clamshells, the power management issues are not yet solved in mainline (read no suspend/resume, no recharge in standby...) I'd sincerely hope we can move to 2.6.34 but realistic could be the 2.6.36 time frame. Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Collie install
I could verify that downgrading udev to 141 from 151 makes Zaurus c7x0 boot... There are apparently still issues with device nodes. Being that pastebin.ca is down I temporarly posted the logs here: http://projects.linuxtogo.org/frs/shownotes.php?release_id=133 I'll do more tests this evening Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Collie install
But still no joy with the collie images, I have tried stable, unstable, opie, console, udev, etc. but can get nothing to completely bo I suspect a new kexecboot kernel would help. I can't seem to build one for collie, maybe Andrea can hook you up with one. If I'm not wrong we agreed that the issue is in the rootfs, *after* kexec'ing to the new kernel. Isn't there any collie-image known to boot around? I'm sorry but really never gave too much attention to pre-clamshells. Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] narcissus spitz unstable image hangs at boot
Same on corgi (c7x0) hangs when the last lines are: usb0: Ethernet Gadget, version May Day 2005 usb0: using pxa2xx_udc, OUT ep2out-bulk IN ep1in-bulk STATUS ep6in-init usb0: MAC [deleted by me] usb0: HOST MAC [I won't reveal this either] usb0: RNDIS ready This happens with auto-built opie-image. Console image boots fine. Investigating... Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] narcissus spitz unstable image hangs at boot
FWIW x11-image fails on first boot at Configuring avahi-autoipd. and on second boot with hwclock: can't open '/dev/misc/rtc' I smell an old issue here..let see.. Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Collie install using Narcisus.
What I get when trying to boot the last image is Note: No boot-images found in (/media/card/boot-images) Pivoting root . Illegal instructi hmm...this doesn't seem kexecboot to me... Please retry flashing http://www.angstrom-distribution.org/demo/kexecboot/zImage-kexecboot-2.6.26-r12-collie.bin Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Updating zImage for narcissus snapshots
Done with a kexecboot kernel picked from http://www.angstrom-distribution.org/demo/kexecboot/ Old but 'should just work' Actually, SL-C700 seems having problems with some kernel options (cpufreq). But the reported failure was an immediate lock after flashing kernel, a.k.a 'did not reboot' In the NAND I installed the console only image. The kexecboot menu shows only the SD card entry. Why NAND install not shown? In fact, updater.sh requires legacy jffs2 images. The one provided by Narcissus cannot be flashed by updater.sh (initrd.bin needs 16bytes cruft at the beginning, removed by updater.sh). We are working on this legacy... Finally, remember c700 only has 32mb space on mtd2 partition. In my SD card (formatted as ext2) I installed the opie image. When selecting the SD card entry, nothing happens, zaurus just freezes Ah, did not try stable since long time. Please try with .dev image. Furthermore, I do not understand how the selected Linux knows its root partition. Is it automagically provided by kexecboot or should I write a file (boot.cfg?)? Kexecboot passes the root= and rootfstype= parameter to the launched kernel and in fstab of the images you see rootfs / auto defaults1 1 Plus, for each bootable partition you can configure boot.cfg in order to have rootfs elsewhere. Furthermore, how to ensure coherent kernel version between kexecboot installation and (future) test image? Well, really you shouldn't care too much. You can boot any 2.6 (recent) kernel with old 2.6.26 or 2.6.3x kexecboot (actually in testing-phase).. Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Updating zImage for narcissus snapshots
Furthermore, how to ensure coherent kernel version between kexecboot installation and (future) test image? Well, really you shouldn't care too much. You can boot any 2.6 (recent) kernel with old 2.6.26 or 2.6.3x kexecboot (actually in testing-phase).. The initial matter was to have a fresh kernel. The matter is running a 2.6.24 kernel with 2.6.26 system: loadable modules are not found. Kexecboot kernel has own initramfs userspace and does not need any module. The kernel you launch resides in a rootfs which expectedly contains the corresponding modules. A question I suggest to add to FAQ (I will do it): with narcissus, how can I prepare a zImage.bin for updater.sh? Narcissus provides a single file. Is there an associated repository somewhere? At the moment Narcissus creates *standard* jffs2 images. The 16bytes header/signature is requested by the legacy updater.sh used by Sharp Zaurus only. We are thinking about a modern updater.sh for flashing standard jffs2 images. For the moment you can edit the initrd.bin with an hexeditor and add 16 bytes at the beginning (or do it with simple shell commands). Then updater.sh will strip these again and will flash the image properly (aligned). Personally, I naively renamed a /boot/zImage.2.6.26 from an image generated by narcissus to zImage.bin and tried to flash it. The updater complaints about too huge file (16M instead of 13M, as I remember). That wouldn't work. We expect only the linux-kexecboot kernel in nand, now. Other (production) kernels are just too big to fit in the mtd partition (needing to be able to boot from CF/SD/MTD, ...) Thx for your testing Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Updating zImage for narcissus snapshots
A question I suggest to add to FAQ (I will do it): with narcissus, how can I prepare a zImage.bin for updater.sh? Ah, sorry, if you meant just zImage, well...Narcissus images do not provide linux-kexecboot, just the normal kernel in /boot of the rootfs. Unfortunately atm we have only old versions in http://www.angstrom-distribution.org/demo/kexecboot/ We'll update and add an external repository at linuxtogo, probably soon. I could think about a cpu-freq disabled version for linux-kexecboot_2.6.26 if it sorts out this blocks the SL-C700. Just let me know, pls. Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Updating zImage for narcissus snapshots
My last install was an altboot + console image. Probably this is an old console-image, lacking /boot/zImage So, my question is now: how to install kexecboot image + a console only image on the NAND? Copy on the SD/CF the 3 files: 1 zImage.bin (kexecboot kernel) 2 initrd.bin (valid jffs2 console image, produced by openembedded, with 16 bytes Sharp header) 3 updater.sh Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Struggling with a collie install.
On Wed, Dec 2, 2009 at 2:22 AM, Roland Hughes roland.hug...@gmail.com wrote: I have tried various builds of narcissus builds including opie, gpe, and x11 console. All of them come up with the hwclock error. Same on other Zaurus models. See here logs of Narcissus image booting on c7x0: http://fr.pastebin.ca/1699259 FYI this is log of a successful boot of a console-image built by myself: http://fr.pastebin.ca/1699268 It seems problems arise after 'Starting udev' ... We are working on this. Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Struggling with a collie install.
Perhaps starting from #101 ? /etc/rcS.d/S03udev: line 50: can't create /tmp/uname: Read-only file system Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] xserver-kdrive and klibc couldn't be compiled (qemux86 target)
As Khem pointed out , unfortunately at the moment klibc is broken for x86 x86-64 http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=6f36bd6e28bce49b72e5a3cff77e0c74b8f65e41 BTW see http://www.zytor.com/pipermail/klibc/2009-September/thread.html Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Important information for Angström users (*not* spam)
but why cannot we use a kexecboot kernel with standard files Because linux-kexecboot a.k.a. the kexecboot kernel embeds a very limited initramfs:, containing just a couple of static binaries (kexec and kexecboot). Kexec is the tool (see kexec-tools), kexecboot is the 'init', a custom-purposed binary launching kexec with appropriate args. The name 'kexecboot' was given by the author of the project. So, if you want to create a standard 'liveramdisk' image, just enable kexec during the config of the kernel and deploy kexec-tools in your image. See in recipe/images for more examples. Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Help installing angstom on a collie.
Roland, the online image builder creates a complete rootfs, kernel included. You just need to unpack this on a SD or CF card. To boot this new rootfs you need to flash a special kernel from here http://www.angstrom-distribution.org/demo/kexecboot/ (this is the old 2.6.26) If you want a rootfs in nand, this must be in the .jffs2 format. Just rename your-image-rootfs.jffs2 to initrd.bin and copy it on the card whith the kexecboot zImage. Some info there: http://linuxtogo.org/gowiki/AngstromManual Regards Andrea P.S. unfortunately collie develpment has slowed down. I can't find any recent image in the angstrom downloads. ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Build Anstrom/Opie 2009.x for C7x0 fails
# On branch stable/2009 I see you checked out the stable branch, which unfortunately lacks lot of zaurus-specific commits. How can I fix this error? I suggest you to checkout the org.openembedded.dev branch. Regards Andrea $ du -hs /oe/build/tmp/deploy/glibc/images/c7x0/* 272K /oe/build/tmp/deploy/glibc/images/c7x0/Angstrom-console-image-glibc-ipk-2009.X-test-20090718-c7x0-testlab 12M /oe/build/tmp/deploy/glibc/images/c7x0/Angstrom-console-image-glibc-ipk-2009.X-test-20090718-c7x0.rootfs.jffs2 16M /oe/build/tmp/deploy/glibc/images/c7x0/Angstrom-console-image-glibc-ipk-2009.X-test-20090718-c7x0.rootfs.summary.jffs2 9.2M /oe/build/tmp/deploy/glibc/images/c7x0/Angstrom-console-image-glibc-ipk-2009.X-test-20090718-c7x0.rootfs.tar.gz 88K /oe/build/tmp/deploy/glibc/images/c7x0/Angstrom-initramfs-kexecboot-image-glibc-ipk-2009.X-test-20090718-c7x0.rootfs.cpio.gz 428K /oe/build/tmp/deploy/glibc/images/c7x0/Angstrom-opie-image-glibc-ipk-2009.X-test-20090718-c7x0-testlab 23M /oe/build/tmp/deploy/glibc/images/c7x0/Angstrom-opie-image-glibc-ipk-2009.X-test-20090718-c7x0.rootfs.jffs2 30M /oe/build/tmp/deploy/glibc/images/c7x0/Angstrom-opie-image-glibc-ipk-2009.X-test-20090718-c7x0.rootfs.summary.jffs2 19M /oe/build/tmp/deploy/glibc/images/c7x0/Angstrom-opie-image-glibc-ipk-2009.X-test-20090718-c7x0.rootfs.tar.gz 596K /oe/build/tmp/deploy/glibc/images/c7x0/Angstrom-x11-image-glibc-ipk-2009.X-test-20090718-c7x0-testlab 24M /oe/build/tmp/deploy/glibc/images/c7x0/Angstrom-x11-image-glibc-ipk-2009.X-test-20090718-c7x0.rootfs.jffs2 31M /oe/build/tmp/deploy/glibc/images/c7x0/Angstrom-x11-image-glibc-ipk-2009.X-test-20090718-c7x0.rootfs.summary.jffs2 20M /oe/build/tmp/deploy/glibc/images/c7x0/Angstrom-x11-image-glibc-ipk-2009.X-test-20090718-c7x0.rootfs.tar.gz 4.0K/oe/build/tmp/deploy/glibc/images/c7x0/console-image-c7x0.jffs2 4.0K/oe/build/tmp/deploy/glibc/images/c7x0/console-image-c7x0.tar.gz 4.0K /oe/build/tmp/deploy/glibc/images/c7x0/initramfs-kexecboot-image-c7x0.cpio.gz 1.1M/oe/build/tmp/deploy/glibc/images/c7x0/installkit-c7x0.tar.gz 4.0K /oe/build/tmp/deploy/glibc/images/c7x0/installkit-c7x0.tar.gz.md5 3.1M/oe/build/tmp/deploy/glibc/images/c7x0/modules-2.6.26-r11-c7x0.tgz 4.0K/oe/build/tmp/deploy/glibc/images/c7x0/opie-image-c7x0.jffs2 4.0K/oe/build/tmp/deploy/glibc/images/c7x0/opie-image-c7x0.tar.gz 16K /oe/build/tmp/deploy/glibc/images/c7x0/updater.sh.c7x0 4.0K/oe/build/tmp/deploy/glibc/images/c7x0/x11-image-c7x0.jffs2 4.0K/oe/build/tmp/deploy/glibc/images/c7x0/x11-image-c7x0.tar.gz 1.3M/oe/build/tmp/deploy/glibc/images/c7x0/zImage-2.6.26-r11-c7x0.bin 0 /oe/build/tmp/deploy/glibc/images/c7x0/zImage-c7x0.bin 1.1M /oe/build/tmp/deploy/glibc/images/c7x0/zImage-kexecboot-2.6.26-r13-c7x0.bin 0 /oe/build/tmp/deploy/glibc/images/c7x0/zImage-kexecboot-c7x0.bin ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Latest Akita build?
I generated a file from the website and downloaded {name}.tar.bz2, and
renamed it to hdimage1.tgz. The I put it onto an SD card with the
zimage.bin, gnu-tar and updater.sh files from my most recent download of the
installkit, 2007.12.R13 and flashed the ROM as usual. When it tried to
boot, I get
I'm afraid I have no idea what to do now. Please help?
The Narcissus images does not pair with the old kernels.
You need the latest zImage-kexecboot kernel for your machine.
http://www.angstrom-distribution.org/unstable/autobuild/akita/
Cheers
Ant
___
Angstrom-distro-users mailing list
Angstrom-distro-users@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Latest Akita build?
During the first boot, I got screen after screen of messages... Well, not only you...it seems it happens building images from packages, like Narcissus does. These images need more test. Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Latest Akita build?
In dev branch, Akita is boasted since long time by linux-rp-2.6.26. It is not perfect, we are working on 2.6.28 but we have still some issues with power management for all kernels 2.6.24. Changelog: http://cgit.openembedded.net/cgit.cgi?url=openembedded/log/packages/linux/linux-rp-2.6.26 Which modules are missing? I don't remember having disabled any modules. Regards Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Kexecboot kernels for testing available
FWIW the kernel works fine on C860 for booting from nand. About mount time, jffs2.summary images are a bit faster but waste more nand space... Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] [ANN] Opie 1.2.3 n ow supported in Ångström
ehm...my post was a lure to fish koen...probably the only one who remembers about opie/w100 around. The question is: how bad is the w100 driver in opie/qte..? Which bugs spits it out? Actually pfalcon disabled in two steps the w100 framework. I have no idea why..I was not using opie in the last 2years. 1) opie-init: Remove hacky and stale overrides for opie init script. http://gitweb.openembedded.net/?p=org.openembedded.dev.git;a=commit;h=9d5fb61646141bed1a7897c990f41c4e5c42b41c 2) qte-mt 2.3.10: Drop application of w100 accel patch for c7x0. http://gitweb.openembedded.net/?p=org.openembedded.dev.git;a=commit;h=7b909ad3a15370184a8fb6ab8ff16db7479109bc pfalcon probably forgot to enable the 'Transformed' override in opie-init, because libopie is defaulting w100 (which let me suppose the driver got main acceptance). I'll try to re-enable the patches and see the errors (already found one blocker...) I stlii hope old maintainers of OpenZaurus sort out and shed lights on the matter. Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] ncurses-native broken, breaks dev build of console-image, x11-image, ...
Another fresh report
[20080917 04:11:23] aum one little weird thing in the angstrom
build howto page cost me a full day's processing time:
[20080917 04:11:36] aum the howto says:
[20080917 04:11:43] aum TMPDIR =
/home/david/work/sw/pocketpc/openembedded/OE/${DISTRO}-tmp/
[20080917 04:12:02] aum but that causes some package builds to
break at QA sanity check stage
[20080917 04:12:06] aum changing it to:
[20080917 04:12:16] aum TMPDIR =
/home/david/work/sw/pocketpc/openembedded/OE/build/${DISTRO}/tmp/
[20080917 04:12:19] aum seems to work
[20080917 04:18:55] Tartarus hmmm
[20080917 04:19:04] Tartarus I wonder if not having 'tmp' in the
name upsets something
[20080917 04:19:13] Tartarus I've got a bunch of QA errors I always ignore
[20080917 04:19:36] Tartarus and I set TMPDIR to
${my_workdir}/build_$arch_$machine
[20080917 04:19:51] aum Tartarus: in the dev branch, having 'tmp'
in the name breaks ncurses-native, for one
___
Angstrom-distro-users mailing list
Angstrom-distro-users@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Continued QA issues
I'd say, wipe your TMPDIR and retry.
If it's there, wipe the old /home/bon/OE/${DISTRO}-tmp/ too.
Just my 2 cents
Andrea
___
Angstrom-distro-users mailing list
Angstrom-distro-users@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Spitz Status
I did only notice now the bug it looks exactly like the (ignored) issue I reported here: http://lists.linuxtogo.org/pipermail/angstrom-distro-devel/2008-July/002416.html My solution is *not* to follow the 'building-angstrom' instructions Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] Akita, c7x0, simpad, spitz and tosa kernel 2.6.24 images available from the angstrom stable branch
Koen, Angstrom-x11-image-glibc-ipk-2007.12-r9-c7x0-installkit.tgz (running linux-rp-2.6.24) doesn't suffer for evident bugs at first sight. No issues with suspend an resume. The altboot image seems ok (mounted the opie rootfs as loopback on SD) but shows to much debugging messages for a release version. Great work! Andrea On Fri, Mar 7, 2008 at 7:29 PM, Koen Kooi [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, If you want to help out your machine mentors by testing kernel 2.6.24 for akita, c7x0, simpad, spitz or tosa, grab a 2007.12-r9 image from http://www.angstrom-distribution.org/unstable/autobuild/ , install it and tell us all about it. Zaurus users should download the 'installkit' tarballs and will find the updater.sh, zImage.bin and rootfs file ready for flashing inside, the simpad users will need the jffs2 file and flash it according to the instructions on opensimpad.org. happy testing, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFH0YmCMkyGM64RGpERAtCtAJ9YQO64H4wQvb/yw/n/GG6mz93BHQCfZiNp Ustsb1iBf7LHFFvrVWqaSmY= =eNmd -END PGP SIGNATURE- ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] reconfigure locales?
On 2/28/08, Harmon Seaver [EMAIL PROTECTED] wrote: I've been trying to reset my timezone to CST, but although the page in settings *says* Americas/Chicago, the actual time, set from the network, continual resets to UTC, no matter what I do. I've tried Thanks for reminding us the issue. There is an open bug related to gpe-conf: http://bugs.openembedded.net/show_bug.cgi?id=3315. I also noticed in /etc/profile that there is a reference to /etc/localtime, which doesn't exiest. if [ ! -e /etc/localtime ]; then TZ=UTC# Time Zone. Look at http://theory.uwinnipeg.ca # for an explanation of how to set this to yourexport TZ fi The question is: should we have a postinstall script creating /etc/localtime from standard GB locale? Ant ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] How to build custom kernel?
On 2/29/08, Yan Seiner [EMAIL PROTECTED] wrote: I'm trying to do the same thing, except that I am working with a 2.6.24 kernel. I've spliced that kernel into stable, and built it in its default config, and now I need to configure it to build the libertas_cs driver. I have the same questions as you. If you find out how to do it 'the bitbake way' please share. The first option being from the bitbake shell, $ bitbake -c menuconfig linux-xy-2.6.24 should do the trick. Then you'll find in $WORKDIR the fresh defconfig. Ant ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
Re: [Angstrom-distro-users] How to build custom kernel?
To unmask the 2.6.24 kernel all you need is commenting out DEFAULT_PREFERENCE = -1 in /org.openembedded.dev/packages/linux/linux-rp_2.6.24.bb Andrea ___ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
