From hammack at GotSlack.org Tue Feb 7 02:27:21 2012 From: hammack at GotSlack.org (Jim Hammack) Date: Mon, 06 Feb 2012 20:27:21 -0600 Subject: [ARMedslack] ARMedslack hangs during boot on Dreamplug In-Reply-To: References: Message-ID: <4F308C09.4030509@GotSlack.org> I've been trying to install ARMedslack on my Dreamplug (ser: 1148-XXXXXX) by following Stuart's excellent instructions in INSTALL_KIRKWOOD.TXT, but have been unable to get the system to boot. I believe it is due to a problem with my u-boot which I scrambled earlier. I have been able to find only one version of u-boot that will run on this machine (the guruplug version from http://www.armedslack.org/maint_kirkwooduboot loads but hangs after a 'reset'). This one works: Marvell>> version U-Boot 2011.03-00012-g1a93b51-dirty-pingtoo-v1.2 (Jun 15 2011 - 22:44:57) Marvell-DreamPlug armv5tel-softfloat-linux-gnueabi-gcc (Gentoo 4.4.4-r2 p1.3, pie-0.4.5) 4.4.4 GNU ld (GNU Binutils) 2.20.1.20100303 I am following Stuart's instructions with two exceptions: 1. I am using dream-2.6.38.4-uImage (renamed uImage-kirkwood) from with-linux instead of uImage-kirkwood from the distribution due to a known problem with uImage-kirkwood on the Dreamplug. (http://lists.armedslack.org/2011-August/000978.html) 2. I am using a fat16 boot partition rather that the ext2 partition Stuart uses in his documentation, so I have changed all references to "ext2load" to "fatload" in the bootcmd The system loads uinitrd-kirkwood okay, then loads uImage-kirkwood (which is really dream-2.6.38.4-uImage), but hangs after: "Uncompressing Linux... done, booting the kernel." I don't think this is the problem, but does anyone see any problems with my u-boot variables? Also, I've read that newer Dreamplugs (#114 and later) have some differences from the earlier version. Could this be why the majority of u-boot versions I've found do not run on this machine? Any ideas on where I can find a suitable u-boot? I tried the version referenced here: (http://www.newit.co.uk/forum/index.php?topic=1977.0) but that version hangs also. Any input is appreciated! Thanks, Jim printenv and boot details follow: Marvell>> printenv arcNumber=2659 baudrate=115200 bootargs_console=console=ttyS0,115200 bootargs_root=root=/dev/sda3 waitforroot=10 rootfs=ext4 bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_slk ; reset bootcmd_slk=usb start;fatload usb 0:1 0x01100000 /uinitrd-kirkwood;fatload usb 0:1 0x00800000 /uImage-kirkwood;bootm 0x00800000 0x01100000 bootdelay=3 eth1addr=02:50:43:ba:45:cb ethact=egiga0 ethaddr=00:DE:AD:C0:FF:EE ipaddr=192.168.2.1 mainlineLinux=yes serial_num=DS2-1148-000934 serverip=192.168.2.7 stderr=serial stdin=serial stdout=serial Environment size: 561/65532 bytes Marvell>> reset U-Boot 2011.03-00012-g1a93b51-dirty-pingtoo-v1.2 (Jun 15 2011 - 22:44:57) Marvell-DreamPlug SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB SF: Got idcodes 00000000: c2 20 15 c2 20 . .. SF: Detected MX25L1605D with page size 256, total 2 MiB In: serial Out: serial Err: serial Net: egiga0, egiga1 88E1121 Initialized on egiga0 88E1121 Initialized on egiga1 Hit any key to stop autoboot: 0 (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... EHCI timed out on TD - token=0x80008c80 4 USB Device(s) found scanning bus for storage devices... Device NOT ready Request Sense returned 02 3A 00 2 Storage Device(s) found reading /uinitrd-kirkwood 5755094 bytes read reading /uImage-kirkwood 2033192 bytes read ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-2.6.38.4-kirkwood Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2033128 Bytes = 1.9 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 01100000 ... Image Name: Slackware ARM Initial RAM disk f Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5755030 Bytes = 5.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. From brennan.newman at gmail.com Tue Feb 7 02:32:36 2012 From: brennan.newman at gmail.com (Brennan Newman) Date: Mon, 6 Feb 2012 20:32:36 -0600 Subject: [ARMedslack] ARMedslack hangs during boot on Dreamplug In-Reply-To: <4F308C09.4030509@GotSlack.org> References: <4F308C09.4030509@GotSlack.org> Message-ID: Jim, I had this same issue and it was driving me crazy, it is a simple fix (at least for me). Simply re-download the kernel images and make sure that you are transferring it over in binary. I had used Filezilla to get my install and it was set to transfer all files in ascii by default which according to many people in the world today mangles binary files pretty badly. Hope this helps. Brennan On Mon, Feb 6, 2012 at 8:27 PM, Jim Hammack wrote: > I've been trying to install ARMedslack on my Dreamplug (ser: 1148-XXXXXX) > by following Stuart's excellent instructions in INSTALL_KIRKWOOD.TXT, but > have been unable to get the system to boot. I believe it is due to a > problem with my u-boot which I scrambled earlier. I have been able to find > only one version of u-boot that will run on this machine (the guruplug > version from http://www.armedslack.org/**maint_kirkwoodubootloads but hangs after a 'reset'). This one works: > > Marvell>> version > > U-Boot 2011.03-00012-g1a93b51-dirty-**pingtoo-v1.2 (Jun 15 2011 - > 22:44:57) > Marvell-DreamPlug > armv5tel-softfloat-linux-**gnueabi-gcc (Gentoo 4.4.4-r2 p1.3, pie-0.4.5) > 4.4.4 > GNU ld (GNU Binutils) 2.20.1.20100303 > > I am following Stuart's instructions with two exceptions: > > 1. I am using dream-2.6.38.4-uImage (renamed uImage-kirkwood) from > with-linux instead of uImage-kirkwood from the distribution due to a known > problem with uImage-kirkwood on the Dreamplug. ( > http://lists.armedslack.org/**2011-August/000978.html > ) > 2. I am using a fat16 boot partition rather that the ext2 partition > Stuart uses in his documentation, so I have changed all references to > "ext2load" to "fatload" in the bootcmd > > The system loads uinitrd-kirkwood okay, then loads uImage-kirkwood (which > is really dream-2.6.38.4-uImage), but hangs after: > > "Uncompressing Linux... done, booting the kernel." > > I don't think this is the problem, but does anyone see any problems with > my u-boot variables? Also, I've read that newer Dreamplugs (#114 and > later) have some differences from the earlier version. Could this be why > the majority of u-boot versions I've found do not run on this machine? Any > ideas on where I can find a suitable u-boot? I tried the version referenced > here: > (http://www.newit.co.uk/forum/**index.php?topic=1977.0) > but that version hangs also. > > Any input is appreciated! > > Thanks, > Jim > > printenv and boot details follow: > > Marvell>> printenv > arcNumber=2659 > baudrate=115200 > bootargs_console=console=**ttyS0,115200 > bootargs_root=root=/dev/sda3 waitforroot=10 rootfs=ext4 > bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run > bootcmd_slk ; reset > bootcmd_slk=usb start;fatload usb 0:1 0x01100000 /uinitrd-kirkwood;fatload > usb 0:1 0x00800000 /uImage-kirkwood;bootm 0x00800000 0x01100000 > bootdelay=3 > eth1addr=02:50:43:ba:45:cb > ethact=egiga0 > ethaddr=00:DE:AD:C0:FF:EE > ipaddr=192.168.2.1 > mainlineLinux=yes > serial_num=DS2-1148-000934 > serverip=192.168.2.7 > stderr=serial > stdin=serial > stdout=serial > > Environment size: 561/65532 bytes > Marvell>> reset > > U-Boot 2011.03-00012-g1a93b51-dirty-**pingtoo-v1.2 (Jun 15 2011 - > 22:44:57) > Marvell-DreamPlug > > SoC: Kirkwood 88F6281_A1 > DRAM: 512 MiB > SF: Got idcodes > 00000000: c2 20 15 c2 20 . .. > SF: Detected MX25L1605D with page size 256, total 2 MiB > In: serial > Out: serial > Err: serial > Net: egiga0, egiga1 > 88E1121 Initialized on egiga0 > 88E1121 Initialized on egiga1 > Hit any key to stop autoboot: 0 > (Re)start USB... > USB: Register 10011 NbrPorts 1 > USB EHCI 1.00 > scanning bus for devices... EHCI timed out on TD - token=0x80008c80 > 4 USB Device(s) found > scanning bus for storage devices... Device NOT ready > Request Sense returned 02 3A 00 > 2 Storage Device(s) found > reading /uinitrd-kirkwood > > 5755094 bytes read > reading /uImage-kirkwood > > 2033192 bytes read > ## Booting kernel from Legacy Image at 00800000 ... > Image Name: Linux-2.6.38.4-kirkwood > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 2033128 Bytes = 1.9 MiB > Load Address: 00008000 > Entry Point: 00008000 > Verifying Checksum ... OK > ## Loading init Ramdisk from Legacy Image at 01100000 ... > Image Name: Slackware ARM Initial RAM disk f > Image Type: ARM Linux RAMDisk Image (gzip compressed) > Data Size: 5755030 Bytes = 5.5 MiB > Load Address: 00000000 > Entry Point: 00000000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > OK > > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > > > ______________________________**_________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.**org > http://lists.armedslack.org/**mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hammack at GotSlack.org Thu Feb 9 02:36:38 2012 From: hammack at GotSlack.org (Jim Hammack) Date: Wed, 08 Feb 2012 20:36:38 -0600 Subject: [ARMedslack] ARMedslack hangs during boot on Dreamplug In-Reply-To: References: <4F308C09.4030509@GotSlack.org> Message-ID: <4F333136.4080903@GotSlack.org> An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Thu Feb 9 08:38:10 2012 From: louigi600 at yahoo.it (Davide) Date: Thu, 9 Feb 2012 08:38:10 +0000 (GMT) Subject: [ARMedslack] ARMedslack hangs during boot on Dreamplug In-Reply-To: <4F333136.4080903@GotSlack.org> References: <4F308C09.4030509@GotSlack.org> <4F333136.4080903@GotSlack.org> Message-ID: <1328776690.13778.YahooMailNeo@web29705.mail.ird.yahoo.com> If you can boot the image via tftp but subsequently not from flash then maybe it war not flashed correctly. Are you erasing partition before writing kernel to it ? ________________________________ Da: Jim Hammack A: armedslack at lists.armedslack.org Inviato: Gioved? 9 Febbraio 2012 3:36 Oggetto: Re: [ARMedslack] ARMedslack hangs during boot on Dreamplug Brennan, ? Thanks for the suggestion, but I downloaded the files again and made sure they were binary transfers, and still no luck.? I also downloaded armedslack-current (I had the original armedslack-13.37 that I used on my sheevaplug) but still no change.? I'm confused because the kernel boots after the initial tftpboot and I can install software, configure the system, etc., but when I try to reboot the system hangs. ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? Jim On 02/06/2012 08:32 PM, Brennan Newman wrote: Jim, >? I had this same issue and it was driving me crazy, it is a simple fix (at least for me). ?Simply re-download the kernel images and make sure that you are transferring it over in binary. ?I had used Filezilla to get my install and it was set to transfer all files in ascii by default which according to many people in the world today mangles binary files pretty badly. ?Hope this helps. > > >Brennan > > >On Mon, Feb 6, 2012 at 8:27 PM, Jim Hammack wrote: > >I've been trying to install ARMedslack on my Dreamplug (ser: 1148-XXXXXX) by following Stuart's excellent instructions in INSTALL_KIRKWOOD.TXT, but have been unable to get the system to boot. ? I believe it is due to a problem with my u-boot which I scrambled earlier. ?I have been able to find only one version of u-boot that will run on this machine (the guruplug version from http://www.armedslack.org/maint_kirkwooduboot loads but hangs after a 'reset'). ?This one works: >> >>Marvell>> version >> >>U-Boot 2011.03-00012-g1a93b51-dirty-pingtoo-v1.2 (Jun 15 2011 - 22:44:57) >>Marvell-DreamPlug >>armv5tel-softfloat-linux-gnueabi-gcc (Gentoo 4.4.4-r2 p1.3, pie-0.4.5) 4.4.4 >>GNU ld (GNU Binutils) 2.20.1.20100303 >> >>I am following Stuart's instructions with two exceptions: >> >>1. I am using dream-2.6.38.4-uImage (renamed uImage-kirkwood) from with-linux instead of uImage-kirkwood from the distribution due to a known problem with uImage-kirkwood on the Dreamplug. ?(http://lists.armedslack.org/2011-August/000978.html) >>2. ?I am using a fat16 boot partition rather that the ext2 partition Stuart uses in his documentation, so I have changed all references to "ext2load" to "fatload" in the bootcmd >> >>The system loads uinitrd-kirkwood okay, then loads uImage-kirkwood (which is really dream-2.6.38.4-uImage), but hangs after: >> >>"Uncompressing Linux... done, booting the kernel." >> >>I don't think this is the problem, but does anyone see any problems with my u-boot variables? ?Also, I've read that newer Dreamplugs (#114 and later) have some differences from the earlier version. ?Could this be why the majority of u-boot versions I've found do not run on this machine? ?Any ideas on where I can find a suitable u-boot? I tried the version referenced here: >>(http://www.newit.co.uk/forum/index.php?topic=1977.0) but that version hangs also. >> >>Any input is appreciated! >> >>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?Thanks, >>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?Jim >> >>printenv and boot details follow: >> >>Marvell>> printenv >>arcNumber=2659 >>baudrate=115200 >>bootargs_console=console=ttyS0,115200 >>bootargs_root=root=/dev/sda3 waitforroot=10 rootfs=ext4 >>bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_slk ; reset >>bootcmd_slk=usb start;fatload usb 0:1 0x01100000 /uinitrd-kirkwood;fatload usb 0:1 0x00800000 /uImage-kirkwood;bootm 0x00800000 0x01100000 >>bootdelay=3 >>eth1addr=02:50:43:ba:45:cb >>ethact=egiga0 >>ethaddr=00:DE:AD:C0:FF:EE >>ipaddr=192.168.2.1 >>mainlineLinux=yes >>serial_num=DS2-1148-000934 >>serverip=192.168.2.7 >>stderr=serial >>stdin=serial >>stdout=serial >> >>Environment size: 561/65532 bytes >>Marvell>> reset >> >>U-Boot 2011.03-00012-g1a93b51-dirty-pingtoo-v1.2 (Jun 15 2011 - 22:44:57) >>Marvell-DreamPlug >> >>SoC: ? Kirkwood 88F6281_A1 >>DRAM: ?512 MiB >>SF: Got idcodes >>00000000: c2 20 15 c2 20 ? ?. .. >>SF: Detected MX25L1605D with page size 256, total 2 MiB >>In: ? ?serial >>Out: ? serial >>Err: ? serial >>Net: ? egiga0, egiga1 >>88E1121 Initialized on egiga0 >>88E1121 Initialized on egiga1 >>Hit any key to stop autoboot: ?0 >>(Re)start USB... >>USB: ? Register 10011 NbrPorts 1 >>USB EHCI 1.00 >>scanning bus for devices... EHCI timed out on TD - token=0x80008c80 >>4 USB Device(s) found >>? ? ? scanning bus for storage devices... Device NOT ready >>? Request Sense returned 02 3A 00 >>2 Storage Device(s) found >>reading /uinitrd-kirkwood >> >>5755094 bytes read >>reading /uImage-kirkwood >> >>2033192 bytes read >>## Booting kernel from Legacy Image at 00800000 ... >>? Image Name: ? Linux-2.6.38.4-kirkwood >>? Image Type: ? ARM Linux Kernel Image (uncompressed) >>? Data Size: ? ?2033128 Bytes = 1.9 MiB >>? Load Address: 00008000 >>? Entry Point: ?00008000 >>? Verifying Checksum ... OK >>## Loading init Ramdisk from Legacy Image at 01100000 ... >>? Image Name: ? Slackware ARM Initial RAM disk f >>? Image Type: ? ARM Linux RAMDisk Image (gzip compressed) >>? Data Size: ? ?5755030 Bytes = 5.5 MiB >>? Load Address: 00000000 >>? Entry Point: ?00000000 >>? Verifying Checksum ... OK >>? Loading Kernel Image ... OK >>OK >> >>Starting kernel ... >> >>Uncompressing Linux... done, booting the kernel. >> >> >>_______________________________________________ >>ARMedslack mailing list >>ARMedslack at lists.armedslack.org >>http://lists.armedslack.org/mailman/listinfo/armedslack >> > > > >_______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From free-choice at libero.it Thu Feb 9 09:37:13 2012 From: free-choice at libero.it (free-choice at libero.it) Date: Thu, 9 Feb 2012 10:37:13 +0100 (CET) Subject: [ARMedslack] Irssi issue on ARM Cortex A9 Message-ID: <29130019.24696971328780233835.JavaMail.defaultUser@defaultHost> Using the official irssi package on my Toshiba AC100 I get the error message: "error while loading shared libraries: libperl.so: cannot open shared object file: No such file or directory.".Libperl.so is not present on the system (I just have libperl.a in /usr/lib/perl5.../CORE). The solution is to download, compile and install irssi from source code.Maybe the official package doesn't work everywhere. Some Toshiba AC100 hardware specifications:- nVidia Tegra 250 processor (nVidia Tegra 2 serie) that has a dual-core ARM Cortex A9 CPU, 1.0 GHz frequency for core- 512 MB ram -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Thu Feb 9 09:46:24 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 9 Feb 2012 09:46:24 +0000 (GMT) Subject: [ARMedslack] Irssi issue on ARM Cortex A9 In-Reply-To: <29130019.24696971328780233835.JavaMail.defaultUser@defaultHost> References: <29130019.24696971328780233835.JavaMail.defaultUser@defaultHost> Message-ID: On Thu, 9 Feb 2012, free-choice at libero.it wrote: > Using the official irssi package on my Toshiba AC100 I get the error > message: "error while loading shared libraries: libperl.so: cannot open > shared object file: No such file or directory.".Libperl.so is not > present on the system (I just have libperl.a in /usr/lib/perl5.../CORE). > The solution is to download, compile and install irssi from source > code.Maybe the official package doesn't work everywhere. The package works everywhere - I tried it on Slackware ARM 13.37 and -current. What version of Slackware ARM are you using? I suspect for some reason your libperl.so has been wiped. On -current: root at dodot:~# grep libperl.so /var/log/packages/* /var/log/packages/perl-5.14.0-arm-2:usr/lib/perl5/CORE/libperl.so root at dodot:~# ls -la /usr/lib/perl5/CORE/libperl.so -r-xr-xr-x 1 root root 1396404 Dec 16 23:11 /usr/lib/perl5/CORE/libperl.so* root at dodot:~# -- Stuart Winter Slackware ARM: www.armedslack.org From free-choice at libero.it Thu Feb 9 10:12:52 2012 From: free-choice at libero.it (free-choice at libero.it) Date: Thu, 9 Feb 2012 11:12:52 +0100 (CET) Subject: [ARMedslack] R: Re: Irssi issue on ARM Cortex A9 Message-ID: <15071359.24720661328782372704.JavaMail.defaultUser@defaultHost> >The package works everywhere - I tried it on Slackware ARM 13.37 and >-current. > >What version of Slackware ARM are you using? >I suspect for some reason your libperl.so has been wiped. > >On -current: > >root at dodot:~# grep libperl.so /var/log/packages/* >/var/log/packages/perl-5.14.0-arm-2:usr/lib/perl5/CORE/libperl.so >root at dodot:~# ls -la /usr/lib/perl5/CORE/libperl.so >-r-xr-xr-x 1 root root 1396404 Dec 16 23:11 >/usr/lib/perl5/CORE/libperl.so* >root at dodot:~# I'm using ARMedslack 13.37 and I haven't libperl.so, but libperl.a in the path that I wrote. I just know that the package gave me that error. So, I compiled and installed from source code and it works fine. From unixjohn1969 at gmail.com Thu Feb 9 11:02:23 2012 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Thu, 9 Feb 2012 12:02:23 +0100 Subject: [ARMedslack] Irssi issue on ARM Cortex A9 In-Reply-To: <29130019.24696971328780233835.JavaMail.defaultUser@defaultHost> References: <29130019.24696971328780233835.JavaMail.defaultUser@defaultHost> Message-ID: I just logged into my plug and irssi wasn't installed. I installed it from -current and it works fine for me. I got logged into an irc server. John On Feb 9, 2012 4:40 AM, "free-choice at libero.it" wrote: > Using the official irssi package on my Toshiba AC100 I get the error > message: "error while loading shared libraries: libperl.so: cannot open > shared object file: No such file or directory.". > > Libperl.so is not present on the system (I just have libperl.a in > /usr/lib/perl5.../CORE). > > > The solution is to download, compile and install irssi from source code. > > Maybe the official package doesn't work everywhere. > > > Some Toshiba AC100 hardware specifications: > > - nVidia Tegra 250 processor (nVidia Tegra 2 serie) that has a dual-core > ARM Cortex A9 CPU, 1.0 GHz frequency for core > > - 512 MB ram > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From armedslack at innes.veryspeedy.net Thu Feb 9 13:26:07 2012 From: armedslack at innes.veryspeedy.net (Innes Read) Date: Thu, 09 Feb 2012 13:26:07 +0000 Subject: [ARMedslack] ARMedslack hangs during boot on Dreamplug In-Reply-To: <4F308C09.4030509@GotSlack.org> References: <4F308C09.4030509@GotSlack.org> Message-ID: <4F33C96F.5010807@innes.veryspeedy.net> Hi, This sounds like the exact same problem I had when I got my Dreamplug. Here's the note chain that describes the solution: ******************************************************************* Michael, Thanks for pointing me to those, that got me going (I used a combination of the with-linux kernel and the uinitrd from Slackware 13.37 to get everything installed). You made my day getting my plug all ready to go! Cheers, Innes. On 21/08/2011 18:43, Michael Langfinger wrote: > Hi Innes, > > the problem is that the kernel that is delivered with ARMedslack has MTD support compiled in. For some strange reason, this causes the Dreamplug to hang. [1] > > The workaround for this is pretty simple. Just compile a kernel without MTD support or - which i did - use the kernel from "with-linux" for the dreamplug. [2] > > You also have to ensure that the uImage is on a FAT partition, because the u-boot version on the Dreamplug doesn't support booting from ext2 (except they fixed this in newer revisions, it's been a while since i installed ARMedslack on the dreamplug). > > Of course this workaround has the disadvantage that you have to take care that a system update doesn't overwrite your custom uImage and you have to take care about kernel upgrades yourself. I circumvent the problem of an accidental upgrade (leading to an unbootable system) by mounting the partition that contains the custom uImage to /boot-vfat; /boot is just a folder. In this case a kernel upgrade will overwrite the uImage in /boot, which doesn't affect the system boot at all. Maybe not the best way, but it works. > > You also might need to set the arcNumber (in u-boot) to the correct value (should be 2659, iirc - unfortunately the dreamplug is about 50 kilometers away from my current position, so i can't look it up ;)). > > Cheers, > Michael > > > > [1] http://www.plugcomputer.org/plugforum/index.php?PHPSESSID=manimc8t872rscog9oeti7adb5&topic=5731.0 > > [2] http://archlinuxarm.org/mirror/with-linux/index.php?dir=2.6.38%2F2.6.38.8%2F On 07/02/2012 02:27, Jim Hammack wrote: > I've been trying to install ARMedslack on my Dreamplug (ser: > 1148-XXXXXX) by following Stuart's excellent instructions in > INSTALL_KIRKWOOD.TXT, but have been unable to get the system to boot. I > ... From cap.janemba at gmail.com Thu Feb 9 13:55:03 2012 From: cap.janemba at gmail.com (janemba) Date: Thu, 09 Feb 2012 14:55:03 +0100 Subject: [ARMedslack] AC100 again Message-ID: <4F33D037.3060501@gmail.com> Hello, Did someone make a HOWTO on installing armedslack on AC100 ? Regards, From hammack at GotSlack.org Thu Feb 9 15:20:11 2012 From: hammack at GotSlack.org (Jim Hammack) Date: Thu, 09 Feb 2012 09:20:11 -0600 Subject: [ARMedslack] ARMedslack hangs during boot on Dreamplug In-Reply-To: <1328776690.13778.YahooMailNeo@web29705.mail.ird.yahoo.com> References: <4F308C09.4030509@GotSlack.org> <4F333136.4080903@GotSlack.org> <1328776690.13778.YahooMailNeo@web29705.mail.ird.yahoo.com> Message-ID: <4F33E42B.7010203@GotSlack.org> An HTML attachment was scrubbed... URL: From hammack at GotSlack.org Thu Feb 9 15:24:11 2012 From: hammack at GotSlack.org (Jim Hammack) Date: Thu, 09 Feb 2012 09:24:11 -0600 Subject: [ARMedslack] ARMedslack hangs during boot on Dreamplug In-Reply-To: <4F33C96F.5010807@innes.veryspeedy.net> References: <4F308C09.4030509@GotSlack.org> <4F33C96F.5010807@innes.veryspeedy.net> Message-ID: <4F33E51B.6070905@GotSlack.org> An HTML attachment was scrubbed... URL: From unixjohn1969 at gmail.com Thu Feb 9 16:19:17 2012 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Thu, 9 Feb 2012 17:19:17 +0100 Subject: [ARMedslack] ARMedslack hangs during boot on Dreamplug In-Reply-To: <4F33E42B.7010203@GotSlack.org> References: <4F308C09.4030509@GotSlack.org> <4F333136.4080903@GotSlack.org> <1328776690.13778.YahooMailNeo@web29705.mail.ird.yahoo.com> <4F33E42B.7010203@GotSlack.org> Message-ID: http://forum.doozan.com/read.php?3,1893 On Feb 9, 2012 10:20 AM, "Jim Hammack" wrote: > Davide, > > I'm not sure what you mean by erasing the partition. I am using these > commands taken from INSTALL_KIRKWOOD.TXT: > > setenv arcNumber 2659 > setenv mainlineLinux yes > setenv ipaddr 192.168.2.1 > setenv serverip 192.168.2.7 > saveenv > reset > usb start > tftpboot 0x01100000 armedslack-13.37/uinitrd-kirkwood.img > tftpboot 0x00800000 armedslack-13.37/uImage-kirkwood > setenv bootargs console=ttyS0,115200 nodhcp kbd=us root=/dev/ram rw > bootm 0x00800000 0x01100000 > > *** install armedslack and reboot *** > > setenv bootargs_console console=ttyS0,115200 > setenv bootargs_root 'root=/dev/sda3 waitforroot=10 rootfs=ext4' > setenv bootcmd 'setenv bootargs $(bootargs_console) $(bootargs_root); run > bootcmd_slk ; reset' > setenv bootcmd_slk 'usb start;ext2load usb 0:1 0x01100000 > /uinitrd-kirkwood;ext2load usb 0:1 0x00800000 /uImage-kirkwood;bootm > 0x00800000 0x01100000' > setenv ethaddr F0:AD:4E:00:E5:BD > setenv eth1addr F0:AD:4E:00:E5:BE > saveenv > reset > > Thanks, > Jim > > On 02/09/2012 02:38 AM, Davide wrote: > > If you can boot the image via tftp but subsequently not from flash then > maybe it war not flashed correctly. > Are you erasing partition before writing kernel to it ? > > ------------------------------ > *Da:* Jim Hammack > *A:* armedslack at lists.armedslack.org > *Inviato:* Gioved? 9 Febbraio 2012 3:36 > *Oggetto:* Re: [ARMedslack] ARMedslack hangs during boot on Dreamplug > > Brennan, > > Thanks for the suggestion, but I downloaded the files again and made > sure they were binary transfers, and still no luck. I also downloaded > armedslack-current (I had the original armedslack-13.37 that I used on my > sheevaplug) but still no change. I'm confused because the kernel boots > after the initial tftpboot and I can install software, configure the > system, etc., but when I try to reboot the system hangs. > > Jim > > On 02/06/2012 08:32 PM, Brennan Newman wrote: > > Jim, > I had this same issue and it was driving me crazy, it is a simple fix > (at least for me). Simply re-download the kernel images and make sure that > you are transferring it over in binary. I had used Filezilla to get my > install and it was set to transfer all files in ascii by default which > according to many people in the world today mangles binary files pretty > badly. Hope this helps. > > Brennan > > On Mon, Feb 6, 2012 at 8:27 PM, Jim Hammack wrote: > > I've been trying to install ARMedslack on my Dreamplug (ser: 1148-XXXXXX) > by following Stuart's excellent instructions in INSTALL_KIRKWOOD.TXT, but > have been unable to get the system to boot. I believe it is due to a > problem with my u-boot which I scrambled earlier. I have been able to find > only one version of u-boot that will run on this machine (the guruplug > version from http://www.armedslack.org/maint_kirkwooduboot loads but > hangs after a 'reset'). This one works: > > Marvell>> version > > U-Boot 2011.03-00012-g1a93b51-dirty-pingtoo-v1.2 (Jun 15 2011 - 22:44:57) > Marvell-DreamPlug > armv5tel-softfloat-linux-gnueabi-gcc (Gentoo 4.4.4-r2 p1.3, pie-0.4.5) > 4.4.4 > GNU ld (GNU Binutils) 2.20.1.20100303 > > I am following Stuart's instructions with two exceptions: > > 1. I am using dream-2.6.38.4-uImage (renamed uImage-kirkwood) from > with-linux instead of uImage-kirkwood from the distribution due to a known > problem with uImage-kirkwood on the Dreamplug. ( > http://lists.armedslack.org/2011-August/000978.html) > 2. I am using a fat16 boot partition rather that the ext2 partition > Stuart uses in his documentation, so I have changed all references to > "ext2load" to "fatload" in the bootcmd > > The system loads uinitrd-kirkwood okay, then loads uImage-kirkwood (which > is really dream-2.6.38.4-uImage), but hangs after: > > "Uncompressing Linux... done, booting the kernel." > > I don't think this is the problem, but does anyone see any problems with > my u-boot variables? Also, I've read that newer Dreamplugs (#114 and > later) have some differences from the earlier version. Could this be why > the majority of u-boot versions I've found do not run on this machine? Any > ideas on where I can find a suitable u-boot? I tried the version referenced > here: > (http://www.newit.co.uk/forum/index.php?topic=1977.0) but that version > hangs also. > > Any input is appreciated! > > Thanks, > Jim > > printenv and boot details follow: > > Marvell>> printenv > arcNumber=2659 > baudrate=115200 > bootargs_console=console=ttyS0,115200 > bootargs_root=root=/dev/sda3 waitforroot=10 rootfs=ext4 > bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run > bootcmd_slk ; reset > bootcmd_slk=usb start;fatload usb 0:1 0x01100000 /uinitrd-kirkwood;fatload > usb 0:1 0x00800000 /uImage-kirkwood;bootm 0x00800000 0x01100000 > bootdelay=3 > eth1addr=02:50:43:ba:45:cb > ethact=egiga0 > ethaddr=00:DE:AD:C0:FF:EE > ipaddr=192.168.2.1 > mainlineLinux=yes > serial_num=DS2-1148-000934 > serverip=192.168.2.7 > stderr=serial > stdin=serial > stdout=serial > > Environment size: 561/65532 bytes > Marvell>> reset > > U-Boot 2011.03-00012-g1a93b51-dirty-pingtoo-v1.2 (Jun 15 2011 - 22:44:57) > Marvell-DreamPlug > > SoC: Kirkwood 88F6281_A1 > DRAM: 512 MiB > SF: Got idcodes > 00000000: c2 20 15 c2 20 . .. > SF: Detected MX25L1605D with page size 256, total 2 MiB > In: serial > Out: serial > Err: serial > Net: egiga0, egiga1 > 88E1121 Initialized on egiga0 > 88E1121 Initialized on egiga1 > Hit any key to stop autoboot: 0 > (Re)start USB... > USB: Register 10011 NbrPorts 1 > USB EHCI 1.00 > scanning bus for devices... EHCI timed out on TD - token=0x80008c80 > 4 USB Device(s) found > scanning bus for storage devices... Device NOT ready > Request Sense returned 02 3A 00 > 2 Storage Device(s) found > reading /uinitrd-kirkwood > > 5755094 bytes read > reading /uImage-kirkwood > > 2033192 bytes read > ## Booting kernel from Legacy Image at 00800000 ... > Image Name: Linux-2.6.38.4-kirkwood > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 2033128 Bytes = 1.9 MiB > Load Address: 00008000 > Entry Point: 00008000 > Verifying Checksum ... OK > ## Loading init Ramdisk from Legacy Image at 01100000 ... > Image Name: Slackware ARM Initial RAM disk f > Image Type: ARM Linux RAMDisk Image (gzip compressed) > Data Size: 5755030 Bytes = 5.5 MiB > Load Address: 00000000 > Entry Point: 00000000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > OK > > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > > > > > _______________________________________________ > ARMedslack mailing listARMedslack at lists.armedslack.orghttp://lists.armedslack.org/mailman/listinfo/armedslack > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > > > > > _______________________________________________ > ARMedslack mailing listARMedslack at lists.armedslack.orghttp://lists.armedslack.org/mailman/listinfo/armedslack > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Thu Feb 9 16:25:41 2012 From: louigi600 at yahoo.it (Davide) Date: Thu, 9 Feb 2012 16:25:41 +0000 (GMT) Subject: [ARMedslack] ARMedslack hangs during boot on Dreamplug In-Reply-To: <4F33E42B.7010203@GotSlack.org> References: <4F308C09.4030509@GotSlack.org> <4F333136.4080903@GotSlack.org> <1328776690.13778.YahooMailNeo@web29705.mail.ird.yahoo.com> <4F33E42B.7010203@GotSlack.org> Message-ID: <1328804741.15916.YahooMailNeo@web29705.mail.ird.yahoo.com> I may be mixing up memories from Zaurus and dockstar. But I remember that on one of these if one forgot to erase the flash partition where the kernel was about to be written next boot would fail. But I may be putting you of with this. Sorry for any inconvinience. ________________________________ Da: Jim Hammack A: armedslack at lists.armedslack.org Inviato: Gioved? 9 Febbraio 2012 16:20 Oggetto: Re: [ARMedslack] ARMedslack hangs during boot on Dreamplug Davide, ? I'm not sure what you mean by erasing the partition.? I am using these commands taken from INSTALL_KIRKWOOD.TXT: setenv arcNumber 2659 setenv mainlineLinux yes setenv ipaddr 192.168.2.1 setenv serverip 192.168.2.7 saveenv reset usb start tftpboot 0x01100000 armedslack-13.37/uinitrd-kirkwood.img tftpboot 0x00800000 armedslack-13.37/uImage-kirkwood setenv bootargs console=ttyS0,115200 nodhcp kbd=us root=/dev/ram rw bootm 0x00800000 0x01100000 *** install armedslack and reboot *** setenv bootargs_console console=ttyS0,115200 setenv bootargs_root 'root=/dev/sda3 waitforroot=10 rootfs=ext4' setenv bootcmd 'setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_slk ; reset' setenv bootcmd_slk 'usb start;ext2load usb 0:1 0x01100000 /uinitrd-kirkwood;ext2load usb 0:1 0x00800000 /uImage-kirkwood;bootm 0x00800000 0x01100000' setenv ethaddr F0:AD:4E:00:E5:BD setenv eth1addr F0:AD:4E:00:E5:BE saveenv reset ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? Thanks, ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ?? Jim On 02/09/2012 02:38 AM, Davide wrote: If you can boot the image via tftp but subsequently not from flash then maybe it war not flashed correctly. >Are you erasing partition before writing kernel to it ? > > > > >________________________________ > Da: Jim Hammack >A: armedslack at lists.armedslack.org >Inviato: Gioved? 9 Febbraio 2012 3:36 >Oggetto: Re: [ARMedslack] ARMedslack hangs during boot on Dreamplug > > >Brennan, > >? Thanks for the suggestion, but I downloaded the files again and made sure they were binary transfers, and still no luck.? I also downloaded armedslack-current (I had the original armedslack-13.37 that I used on my sheevaplug) but still no change.? I'm confused because the kernel boots after the initial tftpboot and I can install software, configure the system, etc., but when I try to reboot the system hangs. > >??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? Jim > >On 02/06/2012 08:32 PM, Brennan Newman wrote: >Jim, >>? I had this same issue and it was driving me crazy, it is a simple fix (at least for me). ?Simply re-download the kernel images and make sure that you are transferring it over in binary. ?I had used Filezilla to get my install and it was set to transfer all files in ascii by default which according to many people in the world today mangles binary files pretty badly. ?Hope this helps. >> >> >>Brennan >> >> >>On Mon, Feb 6, 2012 at 8:27 PM, Jim Hammack wrote: >> >>I've been trying to install ARMedslack on my Dreamplug (ser: 1148-XXXXXX) by following Stuart's excellent instructions in INSTALL_KIRKWOOD.TXT, but have been unable to get the system to boot. ? I believe it is due to a problem with my u-boot which I scrambled earlier. ?I have been able to find only one version of u-boot that will run on this machine (the guruplug version from http://www.armedslack.org/maint_kirkwooduboot loads but hangs after a 'reset'). ?This one works: >>> >>>Marvell>> version >>> >>>U-Boot 2011.03-00012-g1a93b51-dirty-pingtoo-v1.2 (Jun 15 2011 - 22:44:57) >>>Marvell-DreamPlug >>>armv5tel-softfloat-linux-gnueabi-gcc (Gentoo 4.4.4-r2 p1.3, pie-0.4.5) 4.4.4 >>>GNU ld (GNU Binutils) 2.20.1.20100303 >>> >>>I am following Stuart's instructions with two exceptions: >>> >>>1. I am using dream-2.6.38.4-uImage (renamed uImage-kirkwood) from with-linux instead of uImage-kirkwood from the distribution due to a known problem with uImage-kirkwood on the Dreamplug. ?(http://lists.armedslack.org/2011-August/000978.html) >>>2. ?I am using a fat16 boot partition rather that the ext2 partition Stuart uses in his documentation, so I have changed all references to "ext2load" to "fatload" in the bootcmd >>> >>>The system loads uinitrd-kirkwood okay, then loads uImage-kirkwood (which is really dream-2.6.38.4-uImage), but hangs after: >>> >>>"Uncompressing Linux... done, booting the kernel." >>> >>>I don't think this is the problem, but does anyone see any problems with my u-boot variables? ?Also, I've read that newer Dreamplugs (#114 and later) have some differences from the earlier version. ?Could this be why the majority of u-boot versions I've found do not run on this machine? ?Any ideas on where I can find a suitable u-boot? I tried the version referenced here: >>>(http://www.newit.co.uk/forum/index.php?topic=1977.0) but that version hangs also. >>> >>>Any input is appreciated! >>> >>>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?Thanks, >>>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?Jim >>> >>>printenv and boot details follow: >>> >>>Marvell>> printenv >>>arcNumber=2659 >>>baudrate=115200 >>>bootargs_console=console=ttyS0,115200 >>>bootargs_root=root=/dev/sda3 waitforroot=10 rootfs=ext4 >>>bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_slk ; reset >>>bootcmd_slk=usb start;fatload usb 0:1 0x01100000 /uinitrd-kirkwood;fatload usb 0:1 0x00800000 /uImage-kirkwood;bootm 0x00800000 0x01100000 >>>bootdelay=3 >>>eth1addr=02:50:43:ba:45:cb >>>ethact=egiga0 >>>ethaddr=00:DE:AD:C0:FF:EE >>>ipaddr=192.168.2.1 >>>mainlineLinux=yes >>>serial_num=DS2-1148-000934 >>>serverip=192.168.2.7 >>>stderr=serial >>>stdin=serial >>>stdout=serial >>> >>>Environment size: 561/65532 bytes >>>Marvell>> reset >>> >>>U-Boot 2011.03-00012-g1a93b51-dirty-pingtoo-v1.2 (Jun 15 2011 - 22:44:57) >>>Marvell-DreamPlug >>> >>>SoC: ? Kirkwood 88F6281_A1 >>>DRAM: ?512 MiB >>>SF: Got idcodes >>>00000000: c2 20 15 c2 20 ? ?. .. >>>SF: Detected MX25L1605D with page size 256, total 2 MiB >>>In: ? ?serial >>>Out: ? serial >>>Err: ? serial >>>Net: ? egiga0, egiga1 >>>88E1121 Initialized on egiga0 >>>88E1121 Initialized on egiga1 >>>Hit any key to stop autoboot: ?0 >>>(Re)start USB... >>>USB: ? Register 10011 NbrPorts 1 >>>USB EHCI 1.00 >>>scanning bus for devices... EHCI timed out on TD - token=0x80008c80 >>>4 USB Device(s) found >>>? ? ? scanning bus for storage devices... Device NOT ready >>>? Request Sense returned 02 3A 00 >>>2 Storage Device(s) found >>>reading /uinitrd-kirkwood >>> >>>5755094 bytes read >>>reading /uImage-kirkwood >>> >>>2033192 bytes read >>>## Booting kernel from Legacy Image at 00800000 ... >>>? Image Name: ? Linux-2.6.38.4-kirkwood >>>? Image Type: ? ARM Linux Kernel Image (uncompressed) >>>? Data Size: ? ?2033128 Bytes = 1.9 MiB >>>? Load Address: 00008000 >>>? Entry Point: ?00008000 >>>? Verifying Checksum ... OK >>>## Loading init Ramdisk from Legacy Image at 01100000 ... >>>? Image Name: ? Slackware ARM Initial RAM disk f >>>? Image Type: ? ARM Linux RAMDisk Image (gzip compressed) >>>? Data Size: ? ?5755030 Bytes = 5.5 MiB >>>? Load Address: 00000000 >>>? Entry Point: ?00000000 >>>? Verifying Checksum ... OK >>>? Loading Kernel Image ... OK >>>OK >>> >>>Starting kernel ... >>> >>>Uncompressing Linux... done, booting the kernel. >>> >>> >>>_______________________________________________ >>>ARMedslack mailing list >>>ARMedslack at lists.armedslack.org >>>http://lists.armedslack.org/mailman/listinfo/armedslack >>> >> >> >> >>_______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack >_______________________________________________ >ARMedslack mailing list >ARMedslack at lists.armedslack.org >http://lists.armedslack.org/mailman/listinfo/armedslack > > > > > >_______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From free-choice at libero.it Thu Feb 9 17:29:05 2012 From: free-choice at libero.it (freechoice) Date: Thu, 9 Feb 2012 18:29:05 +0100 (CET) Subject: [ARMedslack] R: AC100 again Message-ID: <29809.13100131328808545914.JavaMail.defaultUser@defaultHost> You can find something here: http://tosh-ac100.wetpaint.com/page/ARMedslack cap.janemba at gmail.com 9-feb-2012 14.55 >Hello, > >Did someone make a HOWTO on installing armedslack on AC100 ? > > >Regards, > >_______________________________________________ >ARMedslack mailing list >ARMedslack at lists.armedslack.org >http://lists.armedslack.org/mailman/listinfo/armedslack > From m-lists at biscuit.org.uk Thu Feb 9 18:41:00 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 9 Feb 2012 18:41:00 +0000 (GMT) Subject: [ARMedslack] R: Re: Irssi issue on ARM Cortex A9 In-Reply-To: <15071359.24720661328782372704.JavaMail.defaultUser@defaultHost> References: <15071359.24720661328782372704.JavaMail.defaultUser@defaultHost> Message-ID: > I'm using ARMedslack 13.37 and I haven't libperl.so, but libperl.a in the path > that I wrote. > I just know that the package gave me that error. So, I compiled and installed > from source code and it works fine. If you were planning on using Perl, you probably want to reinstall the perl package since it's missing one of the libraries. From m-lists at biscuit.org.uk Thu Feb 9 18:49:03 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 9 Feb 2012 18:49:03 +0000 (GMT) Subject: [ARMedslack] ARMedslack hangs during boot on Dreamplug In-Reply-To: <4F33E42B.7010203@GotSlack.org> References: <4F308C09.4030509@GotSlack.org> <4F333136.4080903@GotSlack.org> <1328776690.13778.YahooMailNeo@web29705.mail.ird.yahoo.com> <4F33E42B.7010203@GotSlack.org> Message-ID: > tftpboot 0x01100000 armedslack-13.37/uinitrd-kirkwood.img > tftpboot 0x00800000 armedslack-13.37/uImage-kirkwood > setenv bootargs console=ttyS0,115200 nodhcp kbd=us root=/dev/ram rw > bootm 0x00800000 0x01100000 > > *** install armedslack and reboot *** > > setenv bootargs_console console=ttyS0,115200 > setenv bootargs_root 'root=/dev/sda3 waitforroot=10 rootfs=ext4' > setenv bootcmd 'setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_slk ; reset' > setenv bootcmd_slk 'usb start;ext2load usb 0:1 0x01100000 /uinitrd-kirkwood;ext2load usb 0:1 0x00800000 /uImage-kirkwood;bootm 0x00800000 0x01100000' > setenv ethaddr F0:AD:4E:00:E5:BD > setenv eth1addr F0:AD:4E:00:E5:BE > saveenv > reset I found that the u-boot on my Trimslice wouldn't work with these settings as, for some reason, it failed to expand some of the variables set. Look at these instead ftp://ftp.armedslack.org/armedslack/armedslack-devtools/tegra/booting.txt You'll want to set all of the relevant settings in the single 'bootargs' variable. It'll probably work then. Try this: setenv bootargs 'console=ttyS0,115200 root=/dev/sda3 waitforroot=5 rootfs=ext4' setenv bootcmd_slk 'usb start;ext2load usb 0:1 0x01100000 /uinitrd-kirkwood;ext2load usb 0:1 0x00800000 /uImage-kirkwood;bootm 0x00800000 0x01100000' setenv bootcmd 'run bootcmd_slk ; reset' save reset From free-choice at libero.it Thu Feb 9 19:01:29 2012 From: free-choice at libero.it (freechoice) Date: Thu, 9 Feb 2012 20:01:29 +0100 (CET) Subject: [ARMedslack] R: Re: R: Re: Irssi issue on ARM Cortex A9 Message-ID: <5292961.24391911328814089882.JavaMail.defaultUser@defaultHost> Really, before I reinstalled Perl from source code, but nothing changed. So, I reinstalled Irssi from source code and I resolved. If someone could try on a Toshiba AC100... 9-feb-2012 19.41 >A: "Slackware ARM port" >Ogg: Re: [ARMedslack] R: Re: Irssi issue on ARM Cortex A9 > > >> I'm using ARMedslack 13.37 and I haven't libperl.so, but libperl.a in the path >> that I wrote. >> I just know that the package gave me that error. So, I compiled and installed >> from source code and it works fine. > >If you were planning on using Perl, you probably want to reinstall the >perl package since it's missing one of the libraries. >_______________________________________________ >ARMedslack mailing list >ARMedslack at lists.armedslack.org >http://lists.armedslack.org/mailman/listinfo/armedslack > From robby at rlworkman.net Thu Feb 9 14:50:02 2012 From: robby at rlworkman.net (Robby Workman) Date: Thu, 9 Feb 2012 08:50:02 -0600 Subject: [ARMedslack] R: Re: Irssi issue on ARM Cortex A9 In-Reply-To: <15071359.24720661328782372704.JavaMail.defaultUser@defaultHost> References: <15071359.24720661328782372704.JavaMail.defaultUser@defaultHost> Message-ID: <20120209085002.49a7d3f8@liberty.rlwhome.lan> On Thu, 9 Feb 2012 11:12:52 +0100 (CET) "free-choice at libero.it" wrote: > >The package works everywhere - I tried it on Slackware ARM 13.37 and > >-current. > > > >What version of Slackware ARM are you using? > >I suspect for some reason your libperl.so has been wiped. > > > >On -current: > > > >root at dodot:~# grep libperl.so /var/log/packages/* > >/var/log/packages/perl-5.14.0-arm-2:usr/lib/perl5/CORE/libperl.so > >root at dodot:~# ls -la /usr/lib/perl5/CORE/libperl.so > >-r-xr-xr-x 1 root root 1396404 Dec 16 23:11 > >/usr/lib/perl5/CORE/libperl.so* > >root at dodot:~# > > I'm using ARMedslack 13.37 and I haven't libperl.so, but libperl.a in > the path that I wrote. > I just know that the package gave me that error. So, I compiled and > installed from source code and it works fine. You didn't install the perl package, or else you somehow modified your system to remove the shared library needed. The point is that irssi works on a proper installation. There's no problem with the package itself or how it's built - the problem is local to your system. -RW From m-lists at biscuit.org.uk Thu Feb 9 19:09:20 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 9 Feb 2012 19:09:20 +0000 (GMT) Subject: [ARMedslack] R: Re: R: Re: Irssi issue on ARM Cortex A9 In-Reply-To: <5292961.24391911328814089882.JavaMail.defaultUser@defaultHost> References: <5292961.24391911328814089882.JavaMail.defaultUser@defaultHost> Message-ID: > Really, before I reinstalled Perl from source code, but nothing changed. So, I > reinstalled Irssi from source code and I resolved. Yes because most likely, your build of irssi hasn't built the dependency on perl since your perl piece is missing. If you were to remove your newly built irssi, upgradepkg --reinstall n/irssi*tgz d/perl*tgz you'd ought to find it works. From hammack at GotSlack.org Fri Feb 10 03:50:28 2012 From: hammack at GotSlack.org (Jim Hammack) Date: Thu, 09 Feb 2012 21:50:28 -0600 Subject: [ARMedslack] SOLVED - ARMedslack hangs during boot on Dreamplug In-Reply-To: <4F33E42B.7010203@GotSlack.org> References: <4F308C09.4030509@GotSlack.org> <4F333136.4080903@GotSlack.org> <1328776690.13778.YahooMailNeo@web29705.mail.ird.yahoo.com> <4F33E42B.7010203@GotSlack.org> Message-ID: <4F349404.9080600@GotSlack.org> All, Thanks for all of the suggestions. I was able to get the system booted by flashing the original u-boot (U-Boot 2011.06-02334-g8f495d9-dirty (Mar 28 2011 - 05:21:06) - which does not support ext2) and installing an older version of armedslack which uses kernel 2.6.38.4. I replaced uImage-kirkwood with dream-2.6.38.4-uImage to get around the problem pointed out by Innes earlier with MTD support causing the boot sequence to hang on dreamplugs. The older kernel is not really a problem for me and it matches what I'm running on my Sheevaplug anyway. So it appears that my problem was caused by the version of u-boot I was trying to use (to get ext2 support) and not by incorrect environmental variables or by corrupted files. I had one problem after following the instructions in INSTALL_KIRKWOOD.TXT. I created a FAT16 /boot partition as Stuart suggests in the documentation and specified that partition for /boot during installation, but the Slackware installation did not write /boot there for some reason. So I had to reboot via tftpboot and copy the files from my ext4 partition to the FAT partition. I'd like to use ext2 for the boot partition (FAT apparently does not support symbolic links), but at this point I'm afraid of bricking the box again by trying to use another version of u-boot that supports ext2. If anyone has been successful with that, I'd like to find out the secret! Thanks, Jim >> ------------------------------------------------------------------------ >> ** >> >> On Mon, Feb 6, 2012 at 8:27 PM, Jim Hammack > > wrote: >> >> I've been trying to install ARMedslack on my Dreamplug (ser: >> 1148-XXXXXX) by following Stuart's excellent instructions in >> INSTALL_KIRKWOOD.TXT, but have been unable to get the system to >> boot. I believe it is due to a problem with my u-boot which I >> scrambled earlier. I have been able to find only one version of >> u-boot that will run on this machine (the guruplug version from >> http://www.armedslack.org/maint_kirkwooduboot loads but hangs >> after a 'reset'). This one works: >> >> Marvell>> version >> >> U-Boot 2011.03-00012-g1a93b51-dirty-pingtoo-v1.2 (Jun 15 2011 - >> 22:44:57) >> Marvell-DreamPlug >> armv5tel-softfloat-linux-gnueabi-gcc (Gentoo 4.4.4-r2 p1.3, >> pie-0.4.5) 4.4.4 >> GNU ld (GNU Binutils) 2.20.1.20100303 >> >> I am following Stuart's instructions with two exceptions: >> >> 1. I am using dream-2.6.38.4-uImage (renamed uImage-kirkwood) >> from with-linux instead of uImage-kirkwood from the distribution >> due to a known problem with uImage-kirkwood on the Dreamplug. >> (http://lists.armedslack.org/2011-August/000978.html) >> 2. I am using a fat16 boot partition rather that the ext2 >> partition Stuart uses in his documentation, so I have changed all >> references to "ext2load" to "fatload" in the bootcmd >> >> The system loads uinitrd-kirkwood okay, then loads >> uImage-kirkwood (which is really dream-2.6.38.4-uImage), but >> hangs after: >> >> "Uncompressing Linux... done, booting the kernel." >> >> I don't think this is the problem, but does anyone see any >> problems with my u-boot variables? Also, I've read that newer >> Dreamplugs (#114 and later) have some differences from the >> earlier version. Could this be why the majority of u-boot >> versions I've found do not run on this machine? Any ideas on >> where I can find a suitable u-boot? I tried the version >> referenced here: >> (http://www.newit.co.uk/forum/index.php?topic=1977.0) but that >> version hangs also. >> >> Any input is appreciated! >> >> Thanks, >> Jim >> >> printenv and boot details follow: >> >> Marvell>> printenv >> arcNumber=2659 >> baudrate=115200 >> bootargs_console=console=ttyS0,115200 >> bootargs_root=root=/dev/sda3 waitforroot=10 rootfs=ext4 >> bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run >> bootcmd_slk ; reset >> bootcmd_slk=usb start;fatload usb 0:1 0x01100000 >> /uinitrd-kirkwood;fatload usb 0:1 0x00800000 >> /uImage-kirkwood;bootm 0x00800000 0x01100000 >> bootdelay=3 >> eth1addr=02:50:43:ba:45:cb >> ethact=egiga0 >> ethaddr=00:DE:AD:C0:FF:EE >> ipaddr=192.168.2.1 >> mainlineLinux=yes >> serial_num=DS2-1148-000934 >> serverip=192.168.2.7 >> stderr=serial >> stdin=serial >> stdout=serial >> >> Environment size: 561/65532 bytes >> Marvell>> reset >> >> U-Boot 2011.03-00012-g1a93b51-dirty-pingtoo-v1.2 (Jun 15 2011 - >> 22:44:57) >> Marvell-DreamPlug >> >> SoC: Kirkwood 88F6281_A1 >> DRAM: 512 MiB >> SF: Got idcodes >> 00000000: c2 20 15 c2 20 . .. >> SF: Detected MX25L1605D with page size 256, total 2 MiB >> In: serial >> Out: serial >> Err: serial >> Net: egiga0, egiga1 >> 88E1121 Initialized on egiga0 >> 88E1121 Initialized on egiga1 >> Hit any key to stop autoboot: 0 >> (Re)start USB... >> USB: Register 10011 NbrPorts 1 >> USB EHCI 1.00 >> scanning bus for devices... EHCI timed out on TD - token=0x80008c80 >> 4 USB Device(s) found >> scanning bus for storage devices... Device NOT ready >> Request Sense returned 02 3A 00 >> 2 Storage Device(s) found >> reading /uinitrd-kirkwood >> >> 5755094 bytes read >> reading /uImage-kirkwood >> >> 2033192 bytes read >> ## Booting kernel from Legacy Image at 00800000 ... >> Image Name: Linux-2.6.38.4-kirkwood >> Image Type: ARM Linux Kernel Image (uncompressed) >> Data Size: 2033128 Bytes = 1.9 MiB >> Load Address: 00008000 >> Entry Point: 00008000 >> Verifying Checksum ... OK >> ## Loading init Ramdisk from Legacy Image at 01100000 ... >> Image Name: Slackware ARM Initial RAM disk f >> Image Type: ARM Linux RAMDisk Image (gzip compressed) >> Data Size: 5755030 Bytes = 5.5 MiB >> Load Address: 00000000 >> Entry Point: 00000000 >> Verifying Checksum ... OK >> Loading Kernel Image ... OK >> OK >> >> Starting kernel ... >> >> Uncompressing Linux... done, booting the kernel. >> >> >> _______________________________________________ >> ARMedslack mailing list >> ARMedslack at lists.armedslack.org >> >> http://lists.armedslack.org/mailman/listinfo/armedslack >> >> >>> >>> >>> _______________________________________________ >>> ARMedslack mailing list >>> ARMedslack at lists.armedslack.org >>> http://lists.armedslack.org/mailman/listinfo/armedslack >> >> _______________________________________________ >> ARMedslack mailing list >> ARMedslack at lists.armedslack.org >> http://lists.armedslack.org/mailman/listinfo/armedslack >> >> >> >> >> _______________________________________________ >> ARMedslack mailing list >> ARMedslack at lists.armedslack.org >> http://lists.armedslack.org/mailman/listinfo/armedslack > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack From m-lists at biscuit.org.uk Fri Feb 10 10:00:54 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 10 Feb 2012 10:00:54 +0000 (GMT) Subject: [ARMedslack] SOLVED - ARMedslack hangs during boot on Dreamplug In-Reply-To: <4F349404.9080600@GotSlack.org> References: <4F308C09.4030509@GotSlack.org> <4F333136.4080903@GotSlack.org> <1328776690.13778.YahooMailNeo@web29705.mail.ird.yahoo.com> <4F33E42B.7010203@GotSlack.org> <4F349404.9080600@GotSlack.org> Message-ID: > > I had one problem after following the instructions in INSTALL_KIRKWOOD.TXT. > I created a FAT16 /boot partition as Stuart suggests in the documentation and I don't suggest FAT - I suggest ext2, for the reason you mention - FAT doesn't support symlinks, and the u-boot for the Sheevas and OpenRD client only support ext2. From unixjohn1969 at gmail.com Fri Feb 10 11:05:17 2012 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Fri, 10 Feb 2012 06:05:17 -0500 Subject: [ARMedslack] SOLVED - ARMedslack hangs during boot on Dreamplug In-Reply-To: References: <4F308C09.4030509@GotSlack.org> <4F333136.4080903@GotSlack.org> <1328776690.13778.YahooMailNeo@web29705.mail.ird.yahoo.com> <4F33E42B.7010203@GotSlack.org> <4F349404.9080600@GotSlack.org> Message-ID: <4F34F9ED.1050403@gmail.com> On 02/10/2012 05:00 AM, Stuart Winter wrote: > >> >> I had one problem after following the instructions in INSTALL_KIRKWOOD.TXT. >> I created a FAT16 /boot partition as Stuart suggests in the documentation and > > I don't suggest FAT - I suggest ext2, for the reason you mention - > FAT doesn't support symlinks, and the u-boot for the Sheevas and OpenRD > client only support ext2. Try FAT. Compare to ext2. When you see the difference, enjoy ext. Upgrade manually. Only my Sheevas work well with FAT. -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From hammack at GotSlack.org Fri Feb 10 14:54:41 2012 From: hammack at GotSlack.org (Jim Hammack) Date: Fri, 10 Feb 2012 08:54:41 -0600 Subject: [ARMedslack] SOLVED - ARMedslack hangs during boot on Dreamplug In-Reply-To: References: <4F308C09.4030509@GotSlack.org> <4F333136.4080903@GotSlack.org> <1328776690.13778.YahooMailNeo@web29705.mail.ird.yahoo.com> <4F33E42B.7010203@GotSlack.org> <4F349404.9080600@GotSlack.org> Message-ID: <4F352FB1.4090001@GotSlack.org> An HTML attachment was scrubbed... URL: From rw at rlworkman.net Sat Feb 11 07:08:13 2012 From: rw at rlworkman.net (Robby Workman) Date: Sat, 11 Feb 2012 01:08:13 -0600 Subject: [ARMedslack] Cant get -current 3.1.5 to boot In-Reply-To: <4F001964.8000803@gmail.com> References: <4F001964.8000803@gmail.com> Message-ID: <20120211010813.0c5a7e8a@liberty.rlwhome.lan> On Sun, 01 Jan 2012 03:29:24 -0500 John O'Donnell wrote: > I upgraded from 3.1.2 to the 3.1.5 packages yesterday. Before > attempting to compile the guruplug UAP drivers I tried to boot and > had no luck. Hung at: > > > -- ## Booting kernel from Legacy Image at 00800000 ... > Image Name: Linux-3.1.5-kirkwood > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 2090424 Bytes = 2 MiB > Load Address: 00008000 > Entry Point: 00008000 > Verifying Checksum ... OK > ## Loading init Ramdisk from Legacy Image at 01100000 ... > Image Name: Slackware ARM Initial RAM disk f > Image Type: ARM Linux RAMDisk Image (gzip compressed) > Data Size: 5811263 Bytes = 5.5 MiB > Load Address: 00000000 > Entry Point: 00000000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > OK > > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > > > I compiled up the modules and my own uImage with the .config that > comes with the armedslack kernel source and the same thing happens. > > I set it back to 3.1.2 and it boots fine. Oh bah, something definitely changed somewhere along the line :/ For a new project here, I need a newer kernel than the one in 13.37, so I decided to use the 3.2.2 kernel from -current. I get the same problem here (albeit under slightly different circumstances). Mine is installed to the NAND, and rootfs is on the mtd, so I don't need an initrd at all; thus, my env settings are this: Marvell>> printenv arcNumber=2659 baudrate=115200 bootargs_console=console=ttyS0,115200 bootargs_root=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs rootfs=ubifs bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_nand; run bootcmd_slack bootcmd_nand=nand read 0x800000 0x100000 0x400000 bootcmd_slack=bootm 0x800000 bootdelay=3 eth1addr=02:50:43:eb:75:43 ethact=egiga0 ethaddr=00:50:43:01:5D:EA fileaddr=800000 filesize=36D00 ipaddr=192.168.13.1 mainlineLinux=yes nand_erasesize=20000 nand_oobsize=40 nand_writesize=800 serverip=192.168.13.11 stderr=serial stdin=serial stdout=serial When I boot, here's what happens: U-Boot 2011.06 (Jul 26 2011 - 12:26:42) Marvell-GuruPlug SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB NAND: 512 MiB In: serial Out: serial Err: serial Net: egiga0, egiga1 88E1121 Initialized on egiga0 88E1121 Initialized on egiga1 Hit any key to stop autoboot: 0 NAND read: device 0 offset 0x100000, size 0x400000 4194304 bytes read: OK ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-3.2.2-kirkwood Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2082616 Bytes = 2 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. ... nothing ... I can boot the 13.37 kernel and such just fine still, but I don't have any of the old 3.1.x kernels from -current. I guess I'll have to compile my own, because I *really* need something newer than 2.6.38 :/ -RW From robby at rlworkman.net Sat Feb 11 07:32:51 2012 From: robby at rlworkman.net (Robby Workman) Date: Sat, 11 Feb 2012 01:32:51 -0600 Subject: [ARMedslack] Cant get -current 3.1.5 to boot In-Reply-To: <20120211010813.0c5a7e8a@liberty.rlwhome.lan> References: <4F001964.8000803@gmail.com> <20120211010813.0c5a7e8a@liberty.rlwhome.lan> Message-ID: <20120211013251.6811f1a3@liberty.rlwhome.lan> On Sat, 11 Feb 2012 01:08:13 -0600 Robby Workman wrote: > On Sun, 01 Jan 2012 03:29:24 -0500 > John O'Donnell wrote: > > > I upgraded from 3.1.2 to the 3.1.5 packages yesterday. Before > > attempting to compile the guruplug UAP drivers I tried to boot and > > had no luck. Hung at: > > > > > > -- ## Booting kernel from Legacy Image at 00800000 ... > > Image Name: Linux-3.1.5-kirkwood > > Image Type: ARM Linux Kernel Image (uncompressed) > > Data Size: 2090424 Bytes = 2 MiB > > Load Address: 00008000 > > Entry Point: 00008000 > > Verifying Checksum ... OK > > ## Loading init Ramdisk from Legacy Image at 01100000 ... > > Image Name: Slackware ARM Initial RAM disk f > > Image Type: ARM Linux RAMDisk Image (gzip compressed) > > Data Size: 5811263 Bytes = 5.5 MiB > > Load Address: 00000000 > > Entry Point: 00000000 > > Verifying Checksum ... OK > > Loading Kernel Image ... OK > > OK > > > > Starting kernel ... > > > > Uncompressing Linux... done, booting the kernel. > > > > > > I compiled up the modules and my own uImage with the .config that > > comes with the armedslack kernel source and the same thing happens. > > > > I set it back to 3.1.2 and it boots fine. > > > Oh bah, something definitely changed somewhere along the line :/ > > For a new project here, I need a newer kernel than the one in 13.37, > so I decided to use the 3.2.2 kernel from -current. I get the same > problem here (albeit under slightly different circumstances). > > Mine is installed to the NAND, and rootfs is on the mtd, so I don't > need an initrd at all; thus, my env settings are this: > > Marvell>> printenv > arcNumber=2659 > baudrate=115200 > bootargs_console=console=ttyS0,115200 > bootargs_root=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs rootfs=ubifs > bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run > bootcmd_nand; run bootcmd_slack bootcmd_nand=nand read 0x800000 > 0x100000 0x400000 bootcmd_slack=bootm 0x800000 > bootdelay=3 > eth1addr=02:50:43:eb:75:43 > ethact=egiga0 > ethaddr=00:50:43:01:5D:EA > fileaddr=800000 > filesize=36D00 > ipaddr=192.168.13.1 > mainlineLinux=yes > nand_erasesize=20000 > nand_oobsize=40 > nand_writesize=800 > serverip=192.168.13.11 > stderr=serial > stdin=serial > stdout=serial > > > When I boot, here's what happens: > > U-Boot 2011.06 (Jul 26 2011 - 12:26:42) > Marvell-GuruPlug > > SoC: Kirkwood 88F6281_A1 > DRAM: 512 MiB > NAND: 512 MiB > In: serial > Out: serial > Err: serial > Net: egiga0, egiga1 > 88E1121 Initialized on egiga0 > 88E1121 Initialized on egiga1 > Hit any key to stop autoboot: 0 > > NAND read: device 0 offset 0x100000, size 0x400000 > 4194304 bytes read: OK > ## Booting kernel from Legacy Image at 00800000 ... > Image Name: Linux-3.2.2-kirkwood > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 2082616 Bytes = 2 MiB > Load Address: 00008000 > Entry Point: 00008000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > OK > > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > > ... nothing ... > > > I can boot the 13.37 kernel and such just fine still, but I don't > have any of the old 3.1.x kernels from -current. I guess I'll have > to compile my own, because I *really* need something newer than > 2.6.38 :/ And just found this: http://www.mail-archive.com/debian-bugs-dist at lists.debian.org/msg986288.html http://lists.denx.de/pipermail/u-boot/2012-February/117020.html So I went here: http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade.html and grabbed this: http://people.debian.org/~tbm/u-boot/2011.12-2/guruplug/u-boot.kwb Even so, this still hangs: U-Boot 2011.12 (Jan 08 2012 - 21:46:50) Marvell-GuruPlug SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB WARNING: Caches not enabled NAND: 512 MiB In: serial Out: serial Err: serial Net: egiga0, egiga1 88E1121 Initialized on egiga0 88E1121 Initialized on egiga1 Hit any key to stop autoboot: 0 NAND read: device 0 offset 0x100000, size 0x400000 4194304 bytes read: OK ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-3.2.2-kirkwood Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2082616 Bytes = 2 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. ... bah ... From m-lists at biscuit.org.uk Sat Feb 11 09:12:41 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 11 Feb 2012 09:12:41 +0000 (GMT) Subject: [ARMedslack] Cant get -current 3.1.5 to boot In-Reply-To: <20120211013251.6811f1a3@liberty.rlwhome.lan> References: <4F001964.8000803@gmail.com> <20120211010813.0c5a7e8a@liberty.rlwhome.lan> <20120211013251.6811f1a3@liberty.rlwhome.lan> Message-ID: > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. [..] I wonder though whether the kernel is actually booting but the serial console output has stopped. Have you tried pinging the machine's IP after a few mins? I pushed out Linux 3.2.5 yesterday to -current. Does this work? The same problem is reported here though: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658759: Have a read through that - there's a link to an u-boot patch. The suggestion is that a kernel change has exposed a bug in the u-boot on the guruplugs. Although as I said, the same Kernel runs perfectly on my Sheevas and OpenRD client; but IIRC the u-boot for guruplugs was never really robust. -- Stuart Winter Slackware ARM: www.armedslack.org From hammack at GotSlack.org Sat Feb 11 19:11:50 2012 From: hammack at GotSlack.org (Jim Hammack) Date: Sat, 11 Feb 2012 13:11:50 -0600 Subject: [ARMedslack] Cant get -current 3.1.5 to boot In-Reply-To: References: <4F001964.8000803@gmail.com> <20120211010813.0c5a7e8a@liberty.rlwhome.lan> <20120211013251.6811f1a3@liberty.rlwhome.lan> Message-ID: <4F36BD76.2080601@GotSlack.org> An HTML attachment was scrubbed... URL: From robby at rlworkman.net Sat Feb 11 19:12:01 2012 From: robby at rlworkman.net (Robby Workman) Date: Sat, 11 Feb 2012 13:12:01 -0600 Subject: [ARMedslack] Cant get -current 3.1.5 to boot In-Reply-To: References: <4F001964.8000803@gmail.com> <20120211010813.0c5a7e8a@liberty.rlwhome.lan> <20120211013251.6811f1a3@liberty.rlwhome.lan> Message-ID: <20120211131201.3d9aad43@liberty.rlwhome.lan> On Sat, 11 Feb 2012 09:12:41 +0000 (GMT) Stuart Winter wrote: > > > Starting kernel ... > > > > Uncompressing Linux... done, booting the kernel. > [..] > > I wonder though whether the kernel is actually booting but the serial > console output has stopped. Have you tried pinging the machine's IP > after a few mins? > > I pushed out Linux 3.2.5 yesterday to -current. Does this work? > > The same problem is reported here though: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658759: Yes, I found that, but I *really* don't want to build my own uboot. I did that several times before, and as often as not, I had to use the openocd stuff to recover the plug :) > Have a read through that - there's a link to an u-boot patch. > The suggestion is that a kernel change has exposed a bug in the > u-boot on the guruplugs. Although as I said, the same Kernel runs > perfectly on my Sheevas and OpenRD client; but IIRC the u-boot for > guruplugs was never really robust. Yes indeed, it's fragile. I'm hoping 3.2.5 is fine, but time will tell. I've pulled the latest kernel from -current, but I was too sleepy last night at 0300 to try it. I'll get there today... :) -RW From robby at rlworkman.net Sat Feb 11 21:05:39 2012 From: robby at rlworkman.net (Robby Workman) Date: Sat, 11 Feb 2012 15:05:39 -0600 Subject: [ARMedslack] Cant get -current 3.1.5 to boot In-Reply-To: <20120211131201.3d9aad43@liberty.rlwhome.lan> References: <4F001964.8000803@gmail.com> <20120211010813.0c5a7e8a@liberty.rlwhome.lan> <20120211013251.6811f1a3@liberty.rlwhome.lan> <20120211131201.3d9aad43@liberty.rlwhome.lan> Message-ID: <20120211150539.20790bed@liberty.rlwhome.lan> On Sat, 11 Feb 2012 13:12:01 -0600 Robby Workman wrote: > On Sat, 11 Feb 2012 09:12:41 +0000 (GMT) > Stuart Winter wrote: > > > > > > Starting kernel ... > > > > > > Uncompressing Linux... done, booting the kernel. > > [..] > > > > I wonder though whether the kernel is actually booting but the > > serial console output has stopped. Have you tried pinging the > > machine's IP after a few mins? > > > > I pushed out Linux 3.2.5 yesterday to -current. Does this work? > > > > The same problem is reported here though: > > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658759: > > > Yes, I found that, but I *really* don't want to build my own uboot. > I did that several times before, and as often as not, I had to use > the openocd stuff to recover the plug :) > > > > Have a read through that - there's a link to an u-boot patch. > > The suggestion is that a kernel change has exposed a bug in the > > u-boot on the guruplugs. Although as I said, the same Kernel runs > > perfectly on my Sheevas and OpenRD client; but IIRC the u-boot for > > guruplugs was never really robust. > > > Yes indeed, it's fragile. I'm hoping 3.2.5 is fine, but time will > tell. I've pulled the latest kernel from -current, but I was too > sleepy last night at 0300 to try it. I'll get there today... :) Okay, here's the verdict: 3.2.x simply won't boot -- I just tried 3.2.5 and got the same results. You'll have to flash a new u-boot. Best I can tell, there's not one already built out there floating around on the web, so you'll have to do it yourself, and here's how. First, get a git checkout of Marvell's u-boot stuff: git clone git://git.denx.de/u-boot-marvell.git Make sure you have the 'master' branch checked out: git checkout master Now build the new u-boot.kwb image: make guruplug_config make ./tools/mkimage \ -n ./board/Marvell/guruplug/kwbimage.cfg \ -T kwbimage \ -a 0x00600000 \ -e 0x00600000 \ -d u-boot.bin \ u-boot.kwb Now reboot the plug and "hit any key" to stop booting and drop you into the u-boot environment. Set "serverip" to your tftp server and "ipaddr" to your plug ip setenv serverip 10.10.10.1 setenv ipaddr 10.10.10.2 Grab the u-boot.kwb image tftpboot 0x0800000 u-boot.kwb Erase the old u-boot image and flash the new one nand erase 0x0 0x60000 nand write 0x0800000 0x0 0x60000 For grins and giggles, do this (but note that you might have to re-setenv all of your env setttings): saveenv reset In case anyone doesn't want to build the u-boot.kwb themselves, I'm attaching my image (gpg signed) to this message: here are md5sums: 070a4e64fabf2cbeff5778f1702f7f19 u-boot.kwb 8508eba5be077fca2e446c8998780b40 u-boot.kwb.asc Enjoy! -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: u-boot.kwb Type: application/octet-stream Size: 229160 bytes Desc: not available URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: u-boot.kwb.asc URL: From m-lists at biscuit.org.uk Sat Feb 11 21:47:58 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 11 Feb 2012 21:47:58 +0000 (GMT) Subject: [ARMedslack] Cant get -current 3.1.5 to boot In-Reply-To: <20120211150539.20790bed@liberty.rlwhome.lan> References: <4F001964.8000803@gmail.com> <20120211010813.0c5a7e8a@liberty.rlwhome.lan> <20120211013251.6811f1a3@liberty.rlwhome.lan> <20120211131201.3d9aad43@liberty.rlwhome.lan> <20120211150539.20790bed@liberty.rlwhome.lan> Message-ID: > attaching my image (gpg signed) to this message: here are md5sums: [..] I'll add this to the ftp site once I push the next round of updates. -- Stuart Winter Slackware ARM: www.armedslack.org From armedslack at mersenne.com Sun Feb 12 23:54:06 2012 From: armedslack at mersenne.com (David Madden) Date: Sun, 12 Feb 2012 15:54:06 -0800 Subject: [ARMedslack] Tagfile for Minimal Install Message-ID: <4F38511E.1000703@mersenne.com> Hi, I'd like to do a minimal install of armedslack onto a GuruPlug. I tried using the tagfile listed here: http://www.linuxquestions.org/questions/slackware-14/slack-minimal-install-howto-829789/ But it's for an older version of Slackware, and for x86, so it's not quite right. In particular, it doesn't include _something_ that's needed to run pkginstaller, so it doesn't fit my definition of "minimal" (enough stuff to boot, come up on the network with ssh and download additional packages). Does anybody have a more up-to-date tagfile? Thanks, dhm. From robby at rlworkman.net Mon Feb 13 00:41:07 2012 From: robby at rlworkman.net (Robby Workman) Date: Sun, 12 Feb 2012 18:41:07 -0600 Subject: [ARMedslack] Tagfile for Minimal Install In-Reply-To: <4F38511E.1000703@mersenne.com> References: <4F38511E.1000703@mersenne.com> Message-ID: <20120212184107.6ca294db@liberty.rlwhome.lan> On Sun, 12 Feb 2012 15:54:06 -0800 David Madden wrote: > Hi, I'd like to do a minimal install of armedslack onto a GuruPlug. > I tried using the tagfile listed here: > > http://www.linuxquestions.org/questions/slackware-14/slack-minimal-install-howto-829789/ > > But it's for an older version of Slackware, and for x86, so it's not > quite right. In particular, it doesn't include _something_ that's > needed to run pkginstaller, so it doesn't fit my definition of > "minimal" (enough stuff to boot, come up on the network with ssh and > download additional packages). > > Does anybody have a more up-to-date tagfile? Nope, but here's what's installed on my guruplug: (see attachment) fw # df -h Filesystem Size Used Avail Use% Mounted on ubi0:rootfs 463M 187M 276M 41% / tmpfs 252M 0 252M 0% /dev/shm tmpfs 128M 0 128M 0% /tmp -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: guruplug_package_list Type: application/octet-stream Size: 2114 bytes Desc: not available URL: From armedslack at mersenne.com Mon Feb 13 06:59:55 2012 From: armedslack at mersenne.com (David Madden) Date: Sun, 12 Feb 2012 22:59:55 -0800 Subject: [ARMedslack] Tagfile for Minimal Install (provided!) Message-ID: <4F38B4EB.70406@mersenne.com> Following up...I made a set of tagfiles by changing all "recommended" and "optional" packages to "skip," then adding in whatever I needed to be able to load packages using slackpkg. The basic install is about 200M on my GuruPlug, which will easily fit in the Flash (as soon as I figure out all the UBIFS stuff). Hope this is of some use to you all... -------------- next part -------------- A non-text attachment was scrubbed... Name: tagfiles-min.tgz Type: application/x-gzip Size: 5873 bytes Desc: not available URL: From louigi600 at yahoo.it Mon Feb 13 07:22:07 2012 From: louigi600 at yahoo.it (Davide) Date: Mon, 13 Feb 2012 07:22:07 +0000 (GMT) Subject: [ARMedslack] Tagfile for Minimal Install In-Reply-To: <4F38511E.1000703@mersenne.com> References: <4F38511E.1000703@mersenne.com> Message-ID: <1329117727.65313.YahooMailNeo@web29702.mail.ird.yahoo.com> If you want a minimal install try starting from the miniroot and then add a few things where neaded ... it will be quicker then editing tagfiles. ________________________________ Da: David Madden A: armedslack at lists.armedslack.org Inviato: Luned? 13 Febbraio 2012 0:54 Oggetto: [ARMedslack] Tagfile for Minimal Install Hi, I'd like to do a minimal install of armedslack onto a GuruPlug.? I tried using the tagfile listed here: http://www.linuxquestions.org/questions/slackware-14/slack-minimal-install-howto-829789/ But it's for an older version of Slackware, and for x86, so it's not quite right.? In particular, it doesn't include _something_ that's needed to run pkginstaller, so it doesn't fit my definition of "minimal" (enough stuff to boot, come up on the network with ssh and download additional packages). Does anybody have a more up-to-date tagfile? Thanks, dhm. _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From dhm at mersenne.com Sun Feb 12 23:52:01 2012 From: dhm at mersenne.com (David Madden) Date: Sun, 12 Feb 2012 15:52:01 -0800 Subject: [ARMedslack] Tagfile for Minimal Install Message-ID: <4F3850A1.1040800@mersenne.com> Hi, I'd like to do a minimal install of armedslack onto a GuruPlug. I tried using the tagfile listed here: http://www.linuxquestions.org/questions/slackware-14/slack-minimal-install-howto-829789/ But it's for an older version of Slackware, and for x86, so it's not quite right. In particular, it doesn't include _something_ that's needed to run pkginstaller, so it doesn't fit my definition of "minimal" (enough stuff to boot, come up on the network with ssh and download additional packages). Does anybody have a more up-to-date tagfile? Thanks, -- Mersenne Law LLC ? www.mersenne.com ? +1-503-679-1671 - Small Business, Startup and Intellectual Property Law - 1500 SW First Ave. ? Suite 1170 ? Portland, Oregon 97201 From dhm at mersenne.com Mon Feb 13 06:59:03 2012 From: dhm at mersenne.com (David Madden) Date: Sun, 12 Feb 2012 22:59:03 -0800 Subject: [ARMedslack] Tagfile for Minimal Install (provided!) Message-ID: <4F38B4B7.40606@mersenne.com> Following up...I made a set of tagfiles by changing all "recommended" and "optional" packages to "skip," then adding in whatever I needed to be able to load packages using slackpkg. The basic install is about 200M on my GuruPlug, which will easily fit in the Flash (as soon as I figure out all the UBIFS stuff). Hope this is of some use to you all... -- Mersenne Law LLC ? www.mersenne.com ? +1-503-679-1671 - Small Business, Startup and Intellectual Property Law - 1500 SW First Ave. ? Suite 1170 ? Portland, Oregon 97201 -------------- next part -------------- A non-text attachment was scrubbed... Name: tagfiles-min.tgz Type: application/x-gzip Size: 5873 bytes Desc: not available URL: From m-lists at biscuit.org.uk Mon Feb 13 08:30:24 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 13 Feb 2012 08:30:24 +0000 (GMT) Subject: [ARMedslack] Tagfile for Minimal Install (provided!) In-Reply-To: <4F38B4B7.40606@mersenne.com> References: <4F38B4B7.40606@mersenne.com> Message-ID: > Following up...I made a set of tagfiles by changing all "recommended" and > "optional" packages to "skip," then adding in whatever I needed to be able to > load packages using slackpkg. The basic install is about 200M on my GuruPlug, > which will easily fit in the Flash (as soon as I figure out all the UBIFS > stuff). I also maintain the list for the mini root build script: ftp://ftp.armedslack.org/armedslack/armedslack-devtools/minirootfs/scripts/build_minirootfs.sh This is slightly more than minimal as I want some network tools in there - it expands to about 250MB I think. -- Stuart Winter Slackware ARM: www.armedslack.org From pino.otto at gmail.com Mon Feb 13 09:27:25 2012 From: pino.otto at gmail.com (Giovanni) Date: Mon, 13 Feb 2012 10:27:25 +0100 Subject: [ARMedslack] How to install full Slackware from mini root file system Message-ID: I have installed Slackware ARM 13.37 on a pandaboard successfully. Now I would like to install the full version (all packages), starting from the working minimal installation. I already downloaded the slackware ARM tree via rsync directly on the pandaboard. What is the suggested way to install all the packages? Best regards, giovanni -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Mon Feb 13 10:20:57 2012 From: louigi600 at yahoo.it (Davide) Date: Mon, 13 Feb 2012 10:20:57 +0000 (GMT) Subject: [ARMedslack] How to install full Slackware from mini root file system In-Reply-To: References: Message-ID: <1329128457.35046.YahooMailNeo@web29702.mail.ird.yahoo.com> Generally I do this by hand by installing what I require as I find missing functionality. But as a starting guide you might want to get networking working and slackpkg working: n/dhcpcd-5.2.11-i486-1.txz n/ethtool-2.6.36-i486-1.txz n/inetd-1.79s-i486-8.txz n/iptables-1.4.10-i486-1.txz n/iputils-s20101006-i486-1.txz n/iw-0.9.20-i486-1.txz n/links-2.3pre1-i486-1.txz n/network-scripts-13.0-noarch-3.txz n/nmap-5.51-i486-1.txz n/openssh-5.8p1-i486-1.txz n/wget-1.12-i486-1.txz n/wireless-tools-29-i486-6.txz n/wpa_supplicant-0.7.3-i486-3.txz ap/slackpkg-2.82.0-noarch-5.tgz Then setup slackpkg to point to the repository you wish, and run "slackpkg update" ... from there getting the rest will be very easy and fast when you need it: slackpkg install or even get prompted for a wole set of packages slackpkg install n Have fun Davide ________________________________ Da: Giovanni A: Slackware ARM port Inviato: Luned? 13 Febbraio 2012 10:27 Oggetto: [ARMedslack] How to install full Slackware from mini root file system I have installed Slackware ARM 13.37 on a pandaboard successfully. Now I would like to install the full version (all packages), starting from the working minimal installation. I already downloaded the slackware ARM tree via rsync directly on the pandaboard. What is the suggested way to install all the packages? Best regards, giovanni _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From pino.otto at gmail.com Mon Feb 13 10:43:42 2012 From: pino.otto at gmail.com (Giovanni) Date: Mon, 13 Feb 2012 11:43:42 +0100 Subject: [ARMedslack] How to install full Slackware from mini root file system In-Reply-To: <1329128457.35046.YahooMailNeo@web29702.mail.ird.yahoo.com> References: <1329128457.35046.YahooMailNeo@web29702.mail.ird.yahoo.com> Message-ID: Thanks Davide for your answer. I need a clarification. I already have a minimal slackware 13.37 installed and working. My question is: if I go to the directory slackware/a and I install all the packages with the command # installpkg *.t?z go I break the already installed packages or it just overwrites the existing packages? Best regards, giovanni On Mon, Feb 13, 2012 at 11:20 AM, Davide wrote: > Generally I do this by hand by installing what I require as I find missing > functionality. > But as a starting guide you might want to get networking working and > slackpkg working: > n/dhcpcd-5.2.11-i486-1.txz > n/ethtool-2.6.36-i486-1.txz > n/inetd-1.79s-i486-8.txz > n/iptables-1.4.10-i486-1.txz > n/iputils-s20101006-i486-1.txz > n/iw-0.9.20-i486-1.txz > n/links-2.3pre1-i486-1.txz > n/network-scripts-13.0-noarch-3.txz > n/nmap-5.51-i486-1.txz > n/openssh-5.8p1-i486-1.txz > n/wget-1.12-i486-1.txz > n/wireless-tools-29-i486-6.txz > n/wpa_supplicant-0.7.3-i486-3.txz > ap/slackpkg-2.82.0-noarch-5.tgz > > Then setup slackpkg to point to the repository you wish, and run "slackpkg > update" ... from there getting the rest will be very easy and fast when you > need it: > slackpkg install > or even get prompted for a wole set of packages > slackpkg install n > > Have fun > Davide > > > ------------------------------ > *Da:* Giovanni > *A:* Slackware ARM port > *Inviato:* Luned? 13 Febbraio 2012 10:27 > *Oggetto:* [ARMedslack] How to install full Slackware from mini root file > system > > I have installed Slackware ARM 13.37 on a pandaboard successfully. > > Now I would like to install the full version (all packages), starting from > the working minimal installation. > > I already downloaded the slackware ARM tree via rsync directly on the > pandaboard. > > What is the suggested way to install all the packages? > > Best regards, > giovanni > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Mon Feb 13 10:57:51 2012 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 13 Feb 2012 11:57:51 +0100 Subject: [ARMedslack] How to install full Slackware from mini root file system In-Reply-To: References: <1329128457.35046.YahooMailNeo@web29702.mail.ird.yahoo.com> Message-ID: <4F38ECAF.9020105@gmail.com> On 02/13/2012 11:43 AM, Giovanni wrote: > My question is: > if I go to the directory slackware/a and I install all the packages with > the command > # installpkg *.t?z > go I break the already installed packages or it just overwrites the > existing packages? You would be better using: installpkg --install-new *.t?z -- Best regards, Andrzej Telszewski From atelszewski at gmail.com Mon Feb 13 11:01:38 2012 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 13 Feb 2012 12:01:38 +0100 Subject: [ARMedslack] How to install full Slackware from mini root file system In-Reply-To: <4F38ECAF.9020105@gmail.com> References: <1329128457.35046.YahooMailNeo@web29702.mail.ird.yahoo.com> <4F38ECAF.9020105@gmail.com> Message-ID: <4F38ED92.2090007@gmail.com> > You would be better using: > installpkg --install-new *.t?z > Sorry, should be: upgradepkg --install-new *.t?z -- Pozdrawiam, Best regards, Andrzej Telszewski From pino.otto at gmail.com Wed Feb 15 16:22:11 2012 From: pino.otto at gmail.com (Giovanni) Date: Wed, 15 Feb 2012 17:22:11 +0100 Subject: [ARMedslack] How to install full Slackware from mini root file system In-Reply-To: <4F38ED92.2090007@gmail.com> References: <1329128457.35046.YahooMailNeo@web29702.mail.ird.yahoo.com> <4F38ECAF.9020105@gmail.com> <4F38ED92.2090007@gmail.com> Message-ID: Thanks for all the answers. At the end, I installed by using rsync to download the slackware tree locally on the pandabard and then upgradepkg --install-new *.t?z in each package series' directory. On Mon, Feb 13, 2012 at 12:01 PM, Andrzej Telszewski wrote: > You would be better using: >> installpkg --install-new *.t?z >> >> > Sorry, should be: > upgradepkg --install-new *.t?z > > -- > Pozdrawiam, > > Best regards, > Andrzej Telszewski > ______________________________**_________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.**org > http://lists.armedslack.org/**mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pino.otto at gmail.com Wed Feb 15 16:37:14 2012 From: pino.otto at gmail.com (Giovanni) Date: Wed, 15 Feb 2012 17:37:14 +0100 Subject: [ARMedslack] sendmail problem Message-ID: I installed the mini root fs of slackware ARM 13.37 on the pandaboard and then the full installation (all packages, except KDE). The installation of all the packages is OK. But I found a problem when I try to send an email, by using the sendmail. sendmail is up and running: root 15973 0.0 0.4 7912 2020 ? Ss Feb06 0:02 sendmail: accepting connections smmsp 15976 0.0 0.3 7284 1532 ? Ss Feb06 0:00 sendmail: Queue runner at 00:25:00 for /var/spool/clientmqueue if I try to send a mail with the command: echo "prova" | mail -s "test" pino.otto at gmail.com I get the following error in the file /var/log/maillog: Feb 7 06:24:43 slackware sendmail[22802]: e176OhJw022802: from=root, size=216, class=0, nrcpts=1, msgid=<200002070624.e176OhJw022802 at slackware.localdomain>, relay=root at localhost Feb 7 06:24:44 slackware sm-mta[22803]: e176OhFi022803: from=, size=467, class=0, nrcpts=1, msgid=<200002070624.e176OhJw022802 at slackware.localdomain>, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1] Feb 7 06:24:44 slackware sendmail[22802]: e176OhJw022802: to= pino.otto at gmail.com, ctladdr=root (0/0), delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=30216, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (e176OhFi022803 Message accepted for delivery) Feb 7 06:24:44 slackware sm-mta[22805]: STARTTLS=client, relay= gmail-smtp-in.l.google.com., version=TLSv1/SSLv3, verify=FAIL, cipher=RC4-SHA, bits=128/128 Feb 7 06:24:45 slackware sm-mta[22805]: e176OhFi022803: to=< pino.otto at gmail.com>, ctladdr= (0/0), delay=00:00:02, xdelay=00:00:01, mailer=esmtp, pri=120467, relay= gmail-smtp-in.l.google.com. [173.194.65.26], dsn=5.0.0, stat=Service unavailable Feb 7 06:24:45 slackware sm-mta[22805]: e176OhFi022803: e176OjFi022805: DSN: Service unavailable Feb 7 06:24:46 slackware sm-mta[22805]: e176OjFi022805: to=, delay=00:00:01, xdelay=00:00:01, mailer=local, pri=31686, dsn=2.0.0, stat=Sent Is there any special configuration to do, in order to get the sendmail working on Slackware ARM? Best regards, giovanni -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Thu Feb 16 11:06:06 2012 From: louigi600 at yahoo.it (Davide) Date: Thu, 16 Feb 2012 11:06:06 +0000 (GMT) Subject: [ARMedslack] sendmail problem In-Reply-To: References: Message-ID: <1329390366.95083.YahooMailNeo@web29701.mail.ird.yahoo.com> Looks like you've no resolver configured. Is your /etc/resolv.conf i empty ? Also google might regect mail coming directly from your host ... you might like to configure your ISP mail relay as SMART HOST in sendmail.mc ... and subsequently make clean , make all in the sendmail config directory. Regards David ________________________________ Da: Giovanni A: Slackware ARM port Inviato: Mercoled? 15 Febbraio 2012 17:37 Oggetto: [ARMedslack] sendmail problem I installed the mini root fs of slackware ARM 13.37 on the pandaboard and then the full installation (all packages, except KDE). The installation of all the packages is OK. But I found a problem when I try to send an email, by using the sendmail. sendmail is up and running: root???? 15973? 0.0? 0.4?? 7912? 2020 ???????? Ss?? Feb06?? 0:02 sendmail: accepting connections?????? smmsp??? 15976? 0.0? 0.3?? 7284? 1532 ???????? Ss?? Feb06?? 0:00 sendmail: Queue runner at 00:25:00 for /var/spool/clientmqueue if I try to send a mail with the command: echo "prova" | mail -s "test" pino.otto at gmail.com I get the following error in the file /var/log/maillog: Feb? 7 06:24:43 slackware sendmail[22802]: e176OhJw022802: from=root, size=216, class=0, nrcpts=1, msgid=<200002070624.e176OhJw022802 at slackware.localdomain>, relay=root at localhost Feb? 7 06:24:44 slackware sm-mta[22803]: e176OhFi022803: from=, size=467, class=0, nrcpts=1, msgid=<200002070624.e176OhJw022802 at slackware.localdomain>, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1] Feb? 7 06:24:44 slackware sendmail[22802]: e176OhJw022802: to=pino.otto at gmail.com, ctladdr=root (0/0), delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=30216, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (e176OhFi022803 Message accepted for delivery) Feb? 7 06:24:44 slackware sm-mta[22805]: STARTTLS=client, relay=gmail-smtp-in.l.google.com., version=TLSv1/SSLv3, verify=FAIL, cipher=RC4-SHA, bits=128/128 Feb? 7 06:24:45 slackware sm-mta[22805]: e176OhFi022803: to=, ctladdr= (0/0), delay=00:00:02, xdelay=00:00:01, mailer=esmtp, pri=120467, relay=gmail-smtp-in.l.google.com. [173.194.65.26], dsn=5.0.0, stat=Service unavailable Feb? 7 06:24:45 slackware sm-mta[22805]: e176OhFi022803: e176OjFi022805: DSN: Service unavailable Feb? 7 06:24:46 slackware sm-mta[22805]: e176OjFi022805: to=, delay=00:00:01, xdelay=00:00:01, mailer=local, pri=31686, dsn=2.0.0, stat=Sent Is there any special configuration to do, in order to get the sendmail working on Slackware ARM? Best regards, giovanni _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Thu Feb 16 11:28:22 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 16 Feb 2012 11:28:22 +0000 (GMT) Subject: [ARMedslack] sendmail problem In-Reply-To: <1329390366.95083.YahooMailNeo@web29701.mail.ird.yahoo.com> References: <1329390366.95083.YahooMailNeo@web29701.mail.ird.yahoo.com> Message-ID: On Thu, 16 Feb 2012, Davide wrote: > Looks like you've no resolver configured. Is your /etc/resolv.conf i empty ? > > Also google might regect mail coming directly from your host ... you might like to configure your ISP mail relay as SMART HOST in sendmail.mc ... and subsequently make clean , make all in the sendmail config directory. It also could be doing sender verification and your From: address is invalid. From armedslack at mersenne.com Mon Feb 20 18:49:26 2012 From: armedslack at mersenne.com (David Madden) Date: Mon, 20 Feb 2012 10:49:26 -0800 Subject: [ARMedslack] GuruPlug Wireless? Message-ID: <4F4295B6.9060407@mersenne.com> Hi, I've been working on customizing a GuruPlug to do some specific tasks on my home network. I've tried installing Slackware & Debian (both successful) but I haven't been able to build a functional kernel or get wireless running. So, I wonder: * How much of a hassle is it to get from a vanilla kernel tree to a bootable uImage? (I've gotten clean compiles using the config from /boot/config-whatever, but it hangs on boot after "Uncompressing Linux... done, booting the kernel.") * Are the Marvell wireless drivers & tools integrated into the kernel / distro, or is it still an "add external software" project? (I'm fiddling with this in the first place, rather than going with a full Slackware or Debian install, because I'd like to put together a minimal system that fits in the 512MB NAND Flash, so my USB disk can be all data.) Thanks! From geoff at ohdoughnut.com Tue Feb 21 12:34:10 2012 From: geoff at ohdoughnut.com (Geoff Walton) Date: Tue, 21 Feb 2012 07:34:10 -0500 Subject: [ARMedslack] GuruPlug Wireless? In-Reply-To: <4F4295B6.9060407@mersenne.com> References: <4F4295B6.9060407@mersenne.com> Message-ID: I had to 'borrow' to firmware files from the debian install that ships on the device in order to get AP mode to work. I never attempted to get it to run as a client. You can download the file system image from plugcomputer.org and exact them. I have good luck in general with the 2.6.33.5-kirkwood kernel from the 13.1 ArmedSlack distribution, after struggling with the wireless on the later kernels; even though I am using most of the other packages for a snapshot of current shortly before the release of 13.37 and a few later application layer ones with security updates. I can send the firmware images if you need and get them out the Debian image (not entirely sure of the license); but I would try the 2.6.33.5-kirkwood kernel image from 13.1 to get your wireless going. It seems like a number of people had wireless On Mon, Feb 20, 2012 at 1:49 PM, David Madden wrote: > Hi, I've been working on customizing a GuruPlug to do some specific tasks > on my home network. I've tried installing Slackware & Debian (both > successful) but I haven't been able to build a functional kernel or get > wireless running. So, I wonder: > > * How much of a hassle is it to get from a vanilla kernel tree to a > bootable uImage? (I've gotten clean compiles using the config from > /boot/config-whatever, but it hangs on boot after "Uncompressing Linux... > done, booting the kernel.") > > * Are the Marvell wireless drivers & tools integrated into the kernel / > distro, or is it still an "add external software" project? > > (I'm fiddling with this in the first place, rather than going with a full > Slackware or Debian install, because I'd like to put together a minimal > system that fits in the 512MB NAND Flash, so my USB disk can be all data.) > > Thanks! > ______________________________**_________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.**org > http://lists.armedslack.org/**mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From unixjohn1969 at gmail.com Thu Feb 23 07:57:49 2012 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Thu, 23 Feb 2012 02:57:49 -0500 Subject: [ARMedslack] GuruPlug Wireless? In-Reply-To: <4F4295B6.9060407@mersenne.com> References: <4F4295B6.9060407@mersenne.com> Message-ID: <4F45F17D.6010107@gmail.com> On 02/20/2012 01:49 PM, David Madden wrote: > Hi, I've been working on customizing a GuruPlug to do some specific tasks on my > home network. I've tried installing Slackware & Debian (both successful) but I > haven't been able to build a functional kernel or get wireless running. So, I > wonder: > > * How much of a hassle is it to get from a vanilla kernel tree to a bootable > uImage? (I've gotten clean compiles using the config from /boot/config-whatever, > but it hangs on boot after "Uncompressing Linux... done, booting the kernel.") > > * Are the Marvell wireless drivers & tools integrated into the kernel / distro, > or is it still an "add external software" project? It is NOT a part of armedslack. I have all the files needed (firmware / boot scripts / binaries + source) to run an access point here: http://juanisan.homeip.net/guruplug/uap-slackware/ The drivers are NOT a part of the armedslack kernel and need to be rolled in by hand. A patch for armedslack is here: http://juanisan.homeip.net/guruplug/JJO-Marvell-Libertas-8688-AP-FULLPATCH-up-to-3.1.2.patch > (I'm fiddling with this in the first place, rather than going with a full > Slackware or Debian install, because I'd like to put together a minimal system > that fits in the 512MB NAND Flash, so my USB disk can be all data.) That shouldnt be a problem but you will need to add in UBIFS or whatever your root fs is into the kernel as the guruplug MTD layout doesnt have a partition for an initrd. hope this helps John -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From m-lists at biscuit.org.uk Thu Feb 23 08:09:59 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 23 Feb 2012 08:09:59 +0000 (GMT) Subject: [ARMedslack] GuruPlug Wireless? In-Reply-To: <4F45F17D.6010107@gmail.com> References: <4F4295B6.9060407@mersenne.com> <4F45F17D.6010107@gmail.com> Message-ID: > http://juanisan.homeip.net/guruplug/JJO-Marvell-Libertas-8688-AP-FULLPATCH-up-to-3.1.2.patch I remember you mentioning this before. What would need to happen to make this patch be in the upstream kernel? -- Stuart Winter Slackware ARM: www.armedslack.org From unixjohn1969 at gmail.com Thu Feb 23 08:58:39 2012 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Thu, 23 Feb 2012 03:58:39 -0500 Subject: [ARMedslack] GuruPlug Wireless? In-Reply-To: References: <4F4295B6.9060407@mersenne.com> <4F45F17D.6010107@gmail.com> Message-ID: <4F45FFBF.6020205@gmail.com> On 02/23/2012 03:09 AM, Stuart Winter wrote: > >> http://juanisan.homeip.net/guruplug/JJO-Marvell-Libertas-8688-AP-FULLPATCH-up-to-3.1.2.patch > > I remember you mentioning this before. What would need to happen to make > this patch be in the upstream kernel? I consulted the libertas driver author. It was too custom somehow. He made it sound like it could never make it into the mainstream kernel. They are attempting to make the current driver more generic to cover more of the chipsets and bus access methods, but it will probably be a while before this chipset gets looked at. I just patch what they had to work with all the current kernel changes. Till then it remains a custom driver. I could make a package that could match the kernel_kirkwood-3.x.x-arm-1.tgz but I would have to make one every time you changed your kernel. Add a separate package for the binaries, libs, scripts that dont change. This way there would be nothing to compile for the end user, but how important is it? John -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From armedslack at mersenne.com Fri Feb 24 15:47:12 2012 From: armedslack at mersenne.com (David Madden) Date: Fri, 24 Feb 2012 07:47:12 -0800 Subject: [ARMedslack] GuruPlug Wireless? Message-ID: <4F47B100.80907@mersenne.com> Thanks for the replies & info. (For some reason, it doesn't look like I'm getting digests, so I just saw them in the web archives.) I've had luck building a 3.2.6 kernel with vanilla sources and a bit of .config file tweaking. My current config is at: http://www.mersenne.com/downloads/GuruPlug-config.gz for anybody that wants it. I found the instructions at http://wiki.beyondlogic.org/index.php/GuruPlug_Building_Kernel to be helpful. Still no WiFi, but I'll try John's files & patches tonight. Regards, dhm From unixjohn1969 at gmail.com Sat Feb 25 08:19:42 2012 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Sat, 25 Feb 2012 03:19:42 -0500 Subject: [ARMedslack] GuruPlug Wireless? In-Reply-To: <4F47B100.80907@mersenne.com> References: <4F47B100.80907@mersenne.com> Message-ID: <4F48999E.3040207@gmail.com> On 02/24/2012 10:47 AM, David Madden wrote: > Still no WiFi, but I'll try John's files & patches tonight. > Lemme know if you run into any issues, I'll fix em right up. I havent run on a 3.2 kernel yet. Just 3.1 Good Luck John -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From armedslack at mersenne.com Sat Feb 25 17:59:32 2012 From: armedslack at mersenne.com (David Madden) Date: Sat, 25 Feb 2012 09:59:32 -0800 Subject: [ARMedslack] GuruPlug Wireless? In-Reply-To: <4F48999E.3040207@gmail.com> References: <4F47B100.80907@mersenne.com> <4F48999E.3040207@gmail.com> Message-ID: <4F492184.2050702@mersenne.com> On 2/25/2012 00:19, John O'Donnell wrote: > Lemme know if you run into any issues, I'll fix em right up. I havent > run on a 3.2 kernel yet. Just 3.1 Something wrong with the uap_drv.h part of the patch (on OS_INT_RESTORE). I applied it by hand, and <...much compiling occurs...> Uh oh: CC [M] drivers/net/wireless/libertas_uap/uap_main.o drivers/net/wireless/libertas_uap/uap_main.c: In function 'uap_service_main_thread': drivers/net/wireless/libertas_uap/uap_main.c:701:13: error: 'uap_private' has no member named 'driverlock' drivers/net/wireless/libertas_uap/uap_main.c:701:13: error: 'uap_private' has no member named 'driverlock' drivers/net/wireless/libertas_uap/uap_main.c: At top level: drivers/net/wireless/libertas_uap/uap_main.c:1565:5: error: unknown field 'ndo_set_multicast_list' specified in initializer drivers/net/wireless/libertas_uap/uap_main.c:1565:5: warning: initialization from incompatible pointer type [enabled by default] drivers/net/wireless/libertas_uap/uap_main.c:1565:5: warning: (near initialization for 'uap_netdev_ops.ndo_vlan_rx_add_vid') [enabled by default] make[4]: *** [drivers/net/wireless/libertas_uap/uap_main.o] Error 1 make[3]: *** [drivers/net/wireless/libertas_uap] Error 2 make[2]: *** [drivers/net/wireless] Error 2 make[1]: *** [drivers/net] Error 2 make: *** [drivers] Error 2 root at vex:/spare/linux-3.2.6-jod# Gotta run out now; will look into this later today. Thanks! From armedslack at mersenne.com Sat Feb 25 20:26:26 2012 From: armedslack at mersenne.com (David Madden) Date: Sat, 25 Feb 2012 12:26:26 -0800 Subject: [ARMedslack] GuruPlug Wireless? In-Reply-To: <4F492184.2050702@mersenne.com> References: <4F47B100.80907@mersenne.com> <4F48999E.3040207@gmail.com> <4F492184.2050702@mersenne.com> Message-ID: <4F4943F2.3070901@mersenne.com> On 2/25/2012 09:59, David Madden wrote: > will look into this later today. OK, the first error ("no member named driverlock") was my fault: I hand-applied the patch wrong. Second error ("unknown field 'ndo_set_multicast_list'") was apparently a change in a netdevice structure. Both fixed and the patched modules build OK with a vanilla 3.2.6. However... Loading the module doesn't wake up any hardware, or do anything else that I can see. I've attached a typescript with system info and execution of rc.uap8xxx. I dunno what's supposed to happen, but I'm guessing more than what actually did happen! Thanks, dhm -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: typescript URL: From unixjohn1969 at gmail.com Sun Feb 26 07:31:17 2012 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Sun, 26 Feb 2012 02:31:17 -0500 Subject: [ARMedslack] GuruPlug Wireless? In-Reply-To: <4F4943F2.3070901@mersenne.com> References: <4F47B100.80907@mersenne.com> <4F48999E.3040207@gmail.com> <4F492184.2050702@mersenne.com> <4F4943F2.3070901@mersenne.com> Message-ID: <4F49DFC5.5010305@gmail.com> On 02/25/2012 03:26 PM, David Madden wrote: > On 2/25/2012 09:59, David Madden wrote: >> will look into this later today. I am just reading all your notes now. Good information! Thank you! Damn something must have changed in 3.2. I am just getting my development guruplug upgraded to the latest -current so I can work on this and it is taking some time since I am working on a microSD card again. I used to have a 80g attached HD but I'm trying to turn one of my sheevas into a dev platform for other things, so I am patiently waiting for the guru to catch up to -current. The last kernel I was running was 3.1.2. I had issues upgrading to 3.1.5 (-current at the time) so I havent upgraded since. I'm gonna plow into this 3.2.6 now. Compiles take a while on this setup so please be patient. Poppin' on the GCC fins, got my Makefile wetsuit, and put on the kernel source mask and snorkel and I'm GOING IN! I'll be back! Oh man that was a short trip... I still cant get the newer -current kernels to boot on my guruplug. Did you have to rebuild yours from scratch? I am going to attempt that now. This is why I stopped upgrading. reading uinitrd-kirkwood-3.2.6 5937060 bytes read reading /uImage-kirkwood-3.2.6 2083896 bytes read ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-3.2.6-kirkwood Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2083832 Bytes = 2 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 01100000 ... Image Name: Slackware ARM Initial RAM disk f Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5936996 Bytes = 5.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. (... and cue up Depeche Mode's "Enjoy the Silence" ...) Going back to 3.1.2 and try to rebuild 3.2.6 from that. Then maybe I can look at the UAP drivers. John -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From armedslack at mersenne.com Sun Feb 26 07:54:58 2012 From: armedslack at mersenne.com (David Madden) Date: Sat, 25 Feb 2012 23:54:58 -0800 Subject: [ARMedslack] GuruPlug Wireless? In-Reply-To: <4F49DFC5.5010305@gmail.com> References: <4F47B100.80907@mersenne.com> <4F48999E.3040207@gmail.com> <4F492184.2050702@mersenne.com> <4F4943F2.3070901@mersenne.com> <4F49DFC5.5010305@gmail.com> Message-ID: <4F49E552.1030303@mersenne.com> On 2/25/2012 23:31, John O'Donnell wrote: > Oh man that was a short trip... I still cant get the newer -current > kernels to boot on my guruplug. Did you have to rebuild yours from > scratch? I am going to attempt that now. This is why I stopped upgrading. I rebuilt from scratch. I had the same hang-at-booting problem, but I hadn't built a kernel for years, so I didn't know if it was me being stupid and out of date, or what. I followed the instructions at http://wiki.beyondlogic.org/index.php/GuruPlug_Building_Kernel and got my first bootable kernel. After that, things have been going pretty well: I can change config items, recompile, and be pretty confident the image will boot. I'll attach my .config, which ought to get you in the ballpark, anyway. I'm close to having my dream Plug (heh) set up. Apache, MySQL, Postgres and all that stuff, and the UBI filesystem is small enough to (probably) fit on my Dockstar, too. If I can get WiFi running in AP mode, it'll be perfect. I bet Globalscale could sell a bunch of these if they had a little more memory, more CPU speed, and a spot to plug in a 2.5" SATA drive. Or even just a spot to clip a 2.5" drive on, with a USB/SATA adapter. I'm going to have to duct-tape my SSD to the plug so it doesn't just dangle off on the floor. Regards, dhm. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: armedslack-3.2.6-config URL: From dhm at mersenne.com Sat Feb 25 16:06:51 2012 From: dhm at mersenne.com (David Madden) Date: Sat, 25 Feb 2012 08:06:51 -0800 Subject: [ARMedslack] GuruPlug Wireless? In-Reply-To: <4F48999E.3040207@gmail.com> References: <4F47B100.80907@mersenne.com> <4F48999E.3040207@gmail.com> Message-ID: <4F49071B.9010801@mersenne.com> On 2/25/2012 00:19, John O'Donnell wrote: > Lemme know if you run into any issues, I'll fix em right up. I havent > run on a 3.2 kernel yet. Just 3.1 Hi John. I was going to reply that your patch doesn't work against 3.2.6, but I (stupidly!) was running it in dry-run mode, and some of the end patches (your additions?) fail because the additions of libertas_uap haven't been done (because of dry-run mode!) Stupid! Let me copy my functional 3.2.6 tree, apply your patch, build, and see what happens. Regards, -- Mersenne Law LLC ? www.mersenne.com ? +1-503-679-1671 - Small Business, Startup and Intellectual Property Law - 1500 SW First Ave. ? Suite 1170 ? Portland, Oregon 97201 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: patch-result URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4062 bytes Desc: S/MIME Cryptographic Signature URL: From unixjohn1969 at gmail.com Mon Feb 27 19:51:52 2012 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Mon, 27 Feb 2012 14:51:52 -0500 Subject: [ARMedslack] GuruPlug Wireless? In-Reply-To: <4F47B100.80907@mersenne.com> References: <4F47B100.80907@mersenne.com> Message-ID: <4F4BDED8.2040900@gmail.com> On 02/24/2012 10:47 AM, David Madden wrote: > Thanks for the replies & info. (For some reason, it doesn't look like I'm > getting digests, so I just saw them in the web archives.) > > I've had luck building a 3.2.6 kernel with vanilla sources and a bit of .config > file tweaking. My current config is at: > > http://www.mersenne.com/downloads/GuruPlug-config.gz I am trying your config to see if I can get a booted kernel. I tried re-compiling what comes with armedslack and it failed to boot again. So re-compiling again... Maybe tomorrow I can boot 3.2.6 John -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson