From m-lists at biscuit.org.uk Mon Aug 15 12:48:44 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 15 Aug 2011 13:48:44 +0100 (BST) Subject: [ARMedslack] Root on NFS and DHCP support built into the kernel? Message-ID: Hi I am thinking of adding DHCP support & ROOT_NFS into the kernel to support systems without local storage. These options need to be compiled into the kernel rather than as modules. Would anybody (who isn't already building their own kernels) benefit from these options? -- Stuart Winter Slackware ARM: www.armedslack.org From brennan.newman at gmail.com Mon Aug 15 15:07:11 2011 From: brennan.newman at gmail.com (Brennan Newman) Date: Mon, 15 Aug 2011 10:07:11 -0500 Subject: [ARMedslack] Root on NFS and DHCP support built into the kernel? In-Reply-To: References: Message-ID: I would like to experiment with root on NFS. On Aug 15, 2011 7:48 AM, "Stuart Winter" wrote: > > Hi > > I am thinking of adding DHCP support & ROOT_NFS into the kernel to support > systems without local storage. > These options need to be compiled into the kernel rather than as modules. > > Would anybody (who isn't already building their own kernels) benefit from > these options? > > -- > Stuart Winter > Slackware ARM: www.armedslack.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From niels.horn at gmail.com Mon Aug 15 14:15:02 2011 From: niels.horn at gmail.com (Niels Horn) Date: Mon, 15 Aug 2011 11:15:02 -0300 Subject: [ARMedslack] Root on NFS and DHCP support built into the kernel? In-Reply-To: References: Message-ID: On Mon, Aug 15, 2011 at 9:48 AM, Stuart Winter wrote: > > Hi > > I am thinking of adding DHCP support & ROOT_NFS into the kernel to support > systems without local storage. > These options need to be compiled into the kernel rather than as modules. > > Would anybody (who isn't already building their own kernels) benefit from > these options? > > -- > Stuart Winter > Slackware ARM: www.armedslack.org Hi, I can certainly imagine aplications where this could be useful. I *thought* about doing this (building my own kernel) but simply never got to do it (priorities, priorities, ...). Now, ideally, I would like to have a combination of ROOT_NFS + wireless dongle module for the SheevaPlug. But I guess that means building my own kernel anyway, to get the module for the wireless chipset in there. Well, just random ramblings and loose ideas. Like I said, never really sat back to ponder about this more. -- Niels Horn From atelszewski at gmail.com Mon Aug 15 20:24:20 2011 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 15 Aug 2011 22:24:20 +0200 Subject: [ARMedslack] Root on NFS and DHCP support built into the kernel? In-Reply-To: References: Message-ID: <4E498074.8090907@gmail.com> > I would like to experiment with root on NFS. Please see here: http://lists.armedslack.org/pipermail/armedslack/2011-April/000890.html >> >> Hi >> >> I am thinking of adding DHCP support & ROOT_NFS into the kernel to support >> systems without local storage. >> These options need to be compiled into the kernel rather than as modules. >> >> Would anybody (who isn't already building their own kernels) benefit from >> these options? I guess the problem will be what network adapters drivers to include (all or some specific), because either you need to have the network card module compiled in or use initrd for the root over NFS. Or do you only mean to support Sheeva adapter? Then I guess there is no problem with adding only one or two modules. All in all the root over NFS is a nice thing(TM). Add to it loading the kernel and initrd images over network and you have solution that can speed up development very much (e.g. you don't need to re-flash the on board memory). And probably it could be used in some emergency situations, like when the device's original rootfs is damaged - then you can boot over network and start inspecting. -- Pozdrawiam, Best regards, Andrzej Telszewski From pr0f3ss0r1492 at yahoo.com Mon Aug 15 23:35:43 2011 From: pr0f3ss0r1492 at yahoo.com (Ottavio) Date: Tue, 16 Aug 2011 00:35:43 +0100 Subject: [ARMedslack] N00b alert: "Kernel image must be specified" (Qemu - Windows host) Message-ID: Hello, first time here, please be patient. I apologise asking this question here, but the Qemu user forum is currently down and the qemu-devel list is aimed at developers only. I have converted the -Current Miniroot fs to a proper image on a Linux host, made some minor corrections to ftstab and inittab, transferred it to a flash drive and tried to boot it on a Windows host with this line: qemu-system-arm.exe -drive file=slackware-arm-root,index=0,media=disk -M versatilepb -m 256 -usb -k en-gb but I got the error: "Kernel image must be specified". So I downloaded zImage-versatile and initrd-versatile.gz and added this : -kernel zImage-versatile -initrd initrd-versatile.gz -append "root=/dev/sda1 rootfs=ext2" and It works fine. Why does qemu-system-arm need a kernel and a initrd? Is it possible to boot an ARM image directly? Is this a limitation of the ARM Architecture or of the volatile board emulation or of qemu-system-arm altogether? Then I'd have some more n00b questions but I'll ask them later. Thank you -- Ottavio A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? From dowelld at netscape.net Tue Aug 16 00:01:40 2011 From: dowelld at netscape.net (Dave Dowell) Date: Tue, 16 Aug 2011 01:01:40 +0100 Subject: [ARMedslack] N00b alert: "Kernel image must be specified" (Qemu - Windows host) In-Reply-To: References: Message-ID: <4E49B364.7090209@netscape.net> Hello Ottovio, It's a bit of all of them. On ARM systems you always need to tell it to load the kernel image. What happens then is very dependent upon how things have been built. For example it's possible to build a combined image where the kernel and the initrd are rolled into one package, or more often they're kept as seperate images. In the case of ARMedslack the kernel and the initrd are kept seperate, this makes modifying things easier. The initrd itself can do different things dependent on how it was designed. For example the initrd on the Sheevaplug uClibc Debian system is the actual root filesystem, the same is true for the iConnect Debian uClibc system. The ARMedslack initrd is only a initial ramdisk, which contains relevant modules (in your specific case the module for ext2fs) to allow the kernel to access the real root device. So the initrd is about giving the kernel the ability to access the real root device, so that it can mount the real root filesystem and continue the system bringup, read up on pivot root to find out more about this. It should be possible to compile a kernel to include the necessary drivers to directly access the real root device, although I've not tried that yet. It is possible to combine a kernel and initrd into a single image, and thus only load one file into memory and boot that, but that's not the design in play here. It is possible to use an initrd as the real rootdev, but reducing it to fit into the flash memory available onboard most ARM devices requires a lot of work yet, and isn't really in scope for the straight port of Slackware to ARM. I hope that covers your questions? Thanks Dave On 16/08/2011 00:35, Ottavio wrote: > Hello, first time here, please be patient. > > I apologise asking this question here, but the Qemu user forum is > currently down and the qemu-devel list is aimed at developers only. > > I have converted the -Current Miniroot fs to a proper image on a Linux > host, made some minor corrections to ftstab and inittab, transferred > it to a flash drive and tried to boot it on a Windows host with this > line: > > qemu-system-arm.exe -drive file=slackware-arm-root,index=0,media=disk > -M versatilepb -m 256 -usb -k en-gb > > but I got the error: "Kernel image must be specified". > > So I downloaded zImage-versatile and initrd-versatile.gz and added this : > > -kernel zImage-versatile -initrd initrd-versatile.gz -append > "root=/dev/sda1 rootfs=ext2" > > and It works fine. > > Why does qemu-system-arm need a kernel and a initrd? Is it possible to > boot an ARM image directly? Is this a limitation of the ARM > Architecture or of the volatile board emulation or of qemu-system-arm > altogether? > > Then I'd have some more n00b questions but I'll ask them later. > > Thank you > > > From pr0f3ss0r1492 at yahoo.com Tue Aug 16 08:00:28 2011 From: pr0f3ss0r1492 at yahoo.com (Ottavio) Date: Tue, 16 Aug 2011 09:00:28 +0100 Subject: [ARMedslack] N00b alert: "Kernel image must be specified" (Qemu - Windows host) In-Reply-To: <4E49B364.7090209@netscape.net> References: <4E49B364.7090209@netscape.net> Message-ID: On 16 August 2011 01:01, Dave Dowell wrote: > On ARM systems you always need to tell it to load the kernel image. What > happens then is very dependent upon how things have been built. > > For example it's possible to build a combined image where the kernel and the > initrd are rolled into one package, or more often they're kept as seperate > images. > In the case of ARMedslack the kernel and the initrd are kept seperate, this > makes modifying things easier. > > The initrd itself can do different things dependent on how it was designed. > For example the initrd on the Sheevaplug uClibc Debian system is the actual > root filesystem, the same is true for the iConnect Debian uClibc system. > > The ARMedslack initrd is only a initial ramdisk, which contains relevant > modules (in your specific case the module for ext2fs) to allow the kernel to > access the real root device. So the initrd is about giving the kernel the > ability to access the real root device, so that it can mount the real root > filesystem and continue the system bringup, read up on pivot root to find > out more about this. > > It should be possible to compile a kernel to include the necessary drivers > to directly access the real root device, although I've not tried that yet. > It is possible to combine a kernel and initrd into a single image, and thus > only load one file into memory and boot that, but that's not the design in > play here. > It is possible to use an initrd as the real rootdev, but reducing it to fit > into the flash memory available onboard most ARM devices requires a lot of > work yet, and isn't really in scope for the straight port of Slackware to > ARM. > > I hope that covers your questions? > Thanks > Dave Thanks Dave, it does answer my questions, although I still need to to find my ABC of ARM computing. Not having a real device to to play with (but I am thinking of one in particular, so watch this space) I still have to connect the bits and pieces from QEMU to the real world while in the x86/64 world it's a bit more straightforward. -- Ottavio A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? From pr0f3ss0r1492 at yahoo.com Tue Aug 16 08:05:16 2011 From: pr0f3ss0r1492 at yahoo.com (Ottavio) Date: Tue, 16 Aug 2011 09:05:16 +0100 Subject: [ARMedslack] N00b alert: "Kernel image must be specified" (Qemu - Windows host) In-Reply-To: References: <4E49B364.7090209@netscape.net> Message-ID: On 16 August 2011 09:00, Ottavio wrote: > On 16 August 2011 01:01, Dave Dowell wrote: > >> On ARM systems you always need to tell it to load the kernel image. What >> happens then is very dependent upon how things have been built. And another thing: can you point me out to a resource that explains the role of a bootloader on ARM devices as opposed to the PC? Thanks -- Ottavio A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? From dowelld at netscape.net Tue Aug 16 08:19:36 2011 From: dowelld at netscape.net (Dave Dowell) Date: Tue, 16 Aug 2011 09:19:36 +0100 Subject: [ARMedslack] N00b alert: "Kernel image must be specified" (Qemu - Windows host) In-Reply-To: References: <4E49B364.7090209@netscape.net> Message-ID: <4E4A2818.3090900@netscape.net> Hello Ottavio, The bootloader does the same job in both environments, it loads the kernel into memory, it might also load an initrd into memory, and it then hands control of theprocessor over to the kernel code it loaded, probably passing command line arguments into the kernel as it does that. It just looks and feels different to what you're used to. Thanks Dave On 16/08/2011 09:05, Ottavio wrote: > On 16 August 2011 09:00, Ottavio wrote: >> On 16 August 2011 01:01, Dave Dowell wrote: >> >>> On ARM systems you always need to tell it to load the kernel image. What >>> happens then is very dependent upon how things have been built. > > And another thing: can you point me out to a resource that explains > the role of a bootloader on ARM devices as opposed to the PC? > > Thanks > From pr0f3ss0r1492 at yahoo.com Sat Aug 20 15:42:12 2011 From: pr0f3ss0r1492 at yahoo.com (Ottavio) Date: Sat, 20 Aug 2011 16:42:12 +0100 Subject: [ARMedslack] Current: Problem with xterm and seg fault on firefox Message-ID: Hello, I am trying to build a minimal installation with X11 and Firefox, mirroring what I have already on 64 bit PC. I am running this image in qemu with command line: qemu-system-arm.exe -M versatilepb -drive file=slackware-arm-root,index=0,media=disk -kernel zImage-versatile -initrd initrd-versatile.gz -append "root=/dev/sda1 rootfs=ext2" -m 256 -usb -no-shutdown I've started from the current miniroot and added packages with slackpkg (a painful process). So I've got to the point where I thin I have all the necessary packages and all packages have been upgraded so they are all up to date. On the pc target I have no window managers and start firefox from the console with this line: $ startx firefox & but on the ARM target I get error: xterm: bad command line option "xterm". Screenshot: http://img694.imageshack.us/img694/1952/startx.png If I start xterm with this line: xinit -- :0 I can start xterm fine. I wonder if anybody has any ideas. Then I have a second and bigger problem. Once I have started xterm I launch Firefox and I get a segmentation fault: http://img840.imageshack.us/img840/9855/firefoxcrash.png I have reinstalled Firefox but I get the same error. Thank you for your attention -- Ottavio A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? From armedslack at innes.veryspeedy.net Sun Aug 21 15:12:03 2011 From: armedslack at innes.veryspeedy.net (Innes Read) Date: Sun, 21 Aug 2011 16:12:03 +0100 Subject: [ARMedslack] DreamPlug hang Message-ID: <4E512043.1020706@innes.veryspeedy.net> Hi, Newbie alert! This is my first post and first steps with the Kirkwood ARM stuff so please go easy on me. I've just obtained a Dreamplug device, basically a slightly upgraded Guruplug. Following the Armedslack install instructions I get a solidly reproducible hang on initial kernel boot. For grins I saw someone on the list had posted a 2.6.38.7 kernel and I installed the uImage for that onto a memory card and booted... with exactly the same result. My uneducated guess is that there is some module that is locking the system up (wrong/missing) and/or I've forgotten something really important! I'm happy to provide additional data and try suggestions out, in fact it would be a great learning experience on how the initial kernel stuff works. I've pasted a failing boot below, and following that is a working one using the kernel supplied with the device. Here's the failing boot from the U-Boot prompt. The uImage file is on a FAT16 partition, /dev/sdb1, and the uinitrd is the same place and also copied to the second ext2 partition, /dev/sdb2 (or in RAM if doing TFTP): run bootcmd_sdb (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 4 USB Device(s) found scanning bus for storage devices... 2 Storage Device(s) found reading uImage 2024580 bytes read ## Booting kernel from Legacy Image at 06400000 ... Image Name: Linux-2.6.38.7-kirkwood Created: 2011-05-26 7:29:53 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2024516 Bytes = 1.9 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.000000] Linux version 2.6.38.7-kirkwood (root at slackware) (gcc version 4.5.2 (GCC) ) #1 PREEMPT Thu May 26 08:29:19 BST 2011 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] Machine: Marvell GuruPlug Reference Board [ 0.000000] Memory policy: ECC disabled, Data cache writeback [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 [ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sdb2 panic=10 rootwait [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] Memory: 512MB = 512MB total [ 0.000000] Memory: 515308k/515308k available, 8980k reserved, 0K highmem [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) [ 0.000000] DMA : 0xffc00000 - 0xffe00000 ( 2 MB) [ 0.000000] vmalloc : 0xe0800000 - 0xfe800000 ( 480 MB) [ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) [ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB) [ 0.000000] .init : 0xc0008000 - 0xc0029000 ( 132 kB) [ 0.000000] .text : 0xc0029000 - 0xc03ce968 (3735 kB) [ 0.000000] .data : 0xc03d0000 - 0xc03f7af8 ( 159 kB) [ 0.000000] Preemptable hierarchical RCU implementation. [ 0.000000] RCU-based detection of stalled CPUs is disabled. [ 0.000000] Verbose stalled-CPUs detection is disabled. [ 0.000000] NR_IRQS:114 [ 0.000000] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms [ 0.000000] Console: colour dummy device 80x30 [ 3.656806] Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776) [ 3.896687] pid_max: default: 32768 minimum: 301 [ 3.896820] Security Framework initialized [ 3.896892] Mount-cache hash table entries: 512 [ 3.897193] Initializing cgroup subsys ns [ 3.897205] ns_cgroup deprecated: consider using the 'clone_children' flag without the ns_cgroup. [ 3.897218] Initializing cgroup subsys cpuacct [ 3.897233] Initializing cgroup subsys devices [ 3.897242] Initializing cgroup subsys freezer [ 3.897251] Initializing cgroup subsys net_cls [ 3.897280] CPU: Testing write buffer coherency: ok [ 3.899729] print_constraints: dummy: [ 3.899900] NET: Registered protocol family 16 [ 3.901086] Kirkwood: MV88F6281-A1, TCLK=200000000. [ 3.901099] Feroceon L2: Cache support initialised. [ 3.910270] bio: create slab at 0 [ 3.911024] vgaarb: loaded [ 3.912520] Switching to clocksource orion_clocksource [ 3.916683] Switched to NOHz mode on CPU #0 [ 3.931135] NET: Registered protocol family 2 [ 3.931348] IP route cache hash table entries: 4096 (order: 2, 16384 bytes) [ 3.932062] TCP established hash table entries: 16384 (order: 5, 131072 bytes) [ 3.932415] TCP bind hash table entries: 16384 (order: 4, 65536 bytes) [ 3.933112] TCP: Hash tables configured (established 16384 bind 16384) [ 3.933125] TCP reno registered [ 3.933138] UDP hash table entries: 256 (order: 0, 4096 bytes) [ 3.933161] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [ 3.933454] NET: Registered protocol family 1 [ 3.934652] audit: initializing netlink socket (disabled) [ 3.934688] type=2000 audit(0.270:1): initialized [ 3.993557] VFS: Disk quotas dquot_6.5.2 [ 3.993672] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 3.993781] JFFS2 version 2.2. (NAND) (SUMMARY) ? 2001-2006 Red Hat, Inc. [ 3.994168] msgmni has been set to 1006 [ 3.995000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [ 3.995015] io scheduler noop registered [ 3.995024] io scheduler deadline registered [ 3.995084] io scheduler cfq registered (default) [ 4.170023] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [ 4.191940] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A [ 4.565649] console [ttyS0] enabled [ 4.577548] brd: module loaded The system locks up absolutely solid at this point, every time, whether I boot with the 2.6.38.7 kernel as above or if I boot, via TFTP, the install kernel from Slackware 13.37. For comparison, here's the boot from the stock kernel that comes with the Dreamplug: U-Boot 2011.06-02334-g8f495d9-dirty (Mar 28 2011 - 05:21:06) Marvell-DreamPlug SoC: Kirkwood 88F6281_A0 DRAM: 512 MiB SF: Detected MX25L1606 with page size 256, total 1 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 Marvell>> printenv baudrate=115200 x_bootcmd_ethernet=ping 192.168.2.1 x_bootcmd_usb=usb start x_bootcmd_kernel=fatload usb 0 0x6400000 uImage x_bootargs=console=ttyS0,115200 x_bootargs_root=root=/dev/sda2 rootdelay=10 ethact=egiga0 ethaddr=F0:AD:4E:00:7B:4B eth1addr=F0:AD:4E:00:7B:4C ipaddr=192.168.1.14 serverip=192.168.1.13 arcNumber=2659 mainlineLinux=yes bootdelay=10 bootcmd_sdb=setenv bootargs console=ttyS0,115200 root=/dev/sdb2 panic=10 rootwait; usb start; run boot_sdb; boot_sdb=fatload usb 1 0x6400000 uImage; bootm 0x6400000; bootcmd_sda=${bootcmd_eth}; ${x_bootcmd_usb}; ${x_bootcmd_kernel}; setenv bootargs ${x_bootargs} ${x_bootargs_root}; bootm 0x6400000; bootcmd_eth=setenv ethact egiga0; ${x_bootcmd_ethernet}; setenv ethact egiga1; ${x_bootcmd_ethernet} clear_kernel_in_mem=echo Purging kernel in memory; mw 0x6400000 0x0 0x300000 bootcmd=run clear_kernel_in_mem; run bootcmd_sdb; run bootcmd_sda stdin=serial stdout=serial stderr=serial Environment size: 940/4092 bytes Marvell>> run bootcmd_sda (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 4 USB Device(s) found scanning bus for storage devices... 2 Storage Device(s) found reading uImage 2712400 bytes read ## Booting kernel from Legacy Image at 06400000 ... Image Name: Linux-2.6.33.6 Created: 2011-02-08 8:18:48 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2712336 Bytes = 2.6 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Linux version 2.6.33.6 (root at localhost.localdomain) (gcc version 4.2.1) #1 PREEMPT Tue Feb 8 03:18:41 EST 2011 CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 CPU: VIVT data cache, VIVT instruction cache Machine: Marvell GuruPlug Reference Board Memory policy: ECC disabled, Data cache writeback Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 Kernel command line: console=ttyS0,115200 root=/dev/sda2 rootdelay=10 PID hash table entries: 2048 (order: 1, 8192 bytes) Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 256MB 256MB = 512MB total Memory: 513408KB available (4832K code, 862K data, 140K init, 0K highmem) SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 Hierarchical RCU implementation. NR_IRQS:114 Console: colour dummy device 80x30 Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 Kirkwood: MV88F6281-A1, TCLK=200000000. Feroceon L2: Cache support initialised. bio: create slab at 0 vgaarb: loaded SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb cfg80211: Using static regulatory domain info cfg80211: Regulatory domain: 00 (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm) (2457000 KHz - 2482000 KHz @ 20000 KHz), (600 mBi, 2000 mBm) (2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm) (5170000 KHz - 5250000 KHz @ 40000 KHz), (600 mBi, 2000 mBm) (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 2000 mBm) cfg80211: Calling CRDA to update world regulatory domain Switching to clocksource orion_clocksource NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 5, 131072 bytes) TCP bind hash table entries: 16384 (order: 4, 65536 bytes) TCP: Hash tables configured (established 16384 bind 16384) TCP reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. JFFS2 version 2.2. (NAND) ? 2001-2006 Red Hat, Inc. JFS: nTxBlock = 4012, nTxLock = 32102 msgmni has been set to 1003 alg: No test for stdrng (krng) io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A console [ttyS0] enabled brd: module loaded loop: module loaded No NAND device found. MV-643xx 10/100/1000 ethernet driver version 1.4 mv643xx_eth smi: probed net eth0: port 0 with MAC address f0:ad:4e:00:7b:4b net eth1: port 0 with MAC address f0:ad:4e:00:7b:4c ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver orion-ehci orion-ehci.0: Marvell Orion EHCI orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1 orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000 orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. usbcore: registered new interface driver ums-datafab usbcore: registered new interface driver ums-freecom usbcore: registered new interface driver ums-jumpshot usbcore: registered new interface driver ums-sddr09 usbcore: registered new interface driver ums-sddr55 mice: PS/2 mouse device common for all mice rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0 i2c /dev entries driver cpuidle: using governor ladder cpuidle: using governor menu sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman mmc0: mvsdio driver initialized, lacking card detect (fall back to polling) Registered led device: guruplug:red:health Registered led device: guruplug:green:health Registered led device: guruplug:red:wmode Registered led device: guruplug:green:wmode mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver mv_xor mv_xor.0: Marvell XOR: ( xor cpy ) mmc0: new high speed SDIO card at address 0001 mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy ) mv_xor mv_xor.2: Marvell XOR: ( xor cpy ) mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy ) usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid usbhid: USB HID core driver oprofile: using timer interrupt. TCP cubic registered NET: Registered protocol family 17 lib80211: common routines for IEEE802.11 drivers rtc-mv rtc-mv: setting system clock to 2011-08-21 14:12:27 UTC (1313935947) Waiting 10sec before mounting root device... usb 1-1: new high speed USB device using orion-ehci and address 2 hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected usb 1-1.1: new high speed USB device using orion-ehci and address 3 scsi0 : usb-storage 1-1.1:1.0 usb 1-1.4: new full speed USB device using orion-ehci and address 4 input: C-Media USB Headphone Set as /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.3/input/input0 generic-usb 0003:0D8C:000C.0001: input: USB HID v1.00 Device [C-Media USB Headphone Set ] on usb-orion-ehci.0-1.4/input3 scsi 0:0:0:0: Direct-Access Generic STORAGE DEVICE 9910 PQ: 0 ANSI: 0 sd 0:0:0:0: Attached scsi generic sg0 type 0 scsi 0:0:0:1: Direct-Access Generic STORAGE DEVICE 9910 PQ: 0 ANSI: 0 sd 0:0:0:0: [sda] 3842048 512-byte logical blocks: (1.96 GB/1.83 GiB) sd 0:0:0:1: Attached scsi generic sg1 type 0 sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:1: [sdb] 16121856 512-byte logical blocks: (8.25 GB/7.68 GiB) sd 0:0:0:1: [sdb] Write Protect is off sd 0:0:0:1: [sdb] Assuming drive cache: write through sd 0:0:0:0: [sda] Assuming drive cache: write through sda: sda1 sda2 sda: p2 size 3653412 exceeds device capacity, limited to end of disk sd 0:0:0:1: [sdb] Assuming drive cache: write through sdb: sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] Attached SCSI removable disk sdb1 sdb2 sd 0:0:0:1: [sdb] Assuming drive cache: write through sd 0:0:0:1: [sdb] Attached SCSI removable disk EXT3-fs (sda2): warning: maximal mount count reached, running e2fsck is recommended kjournald starting. Commit interval 5 seconds EXT3-fs (sda2): using internal journal EXT3-fs (sda2): mounted filesystem with writeback data mode VFS: Mounted root (ext3 filesystem) on device 8:2. Freeing init memory: 140K * Filesystem type 'fusectl' is not supported. Skipping mount. * Setting preliminary keymap...  [ OK ] * Starting kernel event manager...  [ OK ] * Loading hardware drivers...  Bluetooth: Core ver 2.15 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized sata_mv sata_mv.0: version 1.28 sata_mv sata_mv.0: slots 32 ports 1 scsi1 : sata_mv libertas_sdio: Libertas SDIO driver ata1: SATA max UDMA/133 irq 21 libertas_sdio: Copyright Pierre Ossman libertas_sdio mmc0:0001:1: firmware: requesting sd8688_helper.bin ata1: SATA link down (SStatus 0 SControl F300) libertas: can't load helper firmware libertas: failed to load helper firmware libertas_sdio: probe of mmc0:0001:1 failed with error -2 Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2 btmrvl_sdio mmc0:0001:2: firmware: requesting sd8688_helper.bin btmrvl_sdio_download_helper: request_firmware(helper) failed, error code = -2 btmrvl_sdio_download_fw: Failed to download helper! btmrvl_sdio_probe: Downloading firmware failed! eth1: link up, 100 Mb/s, full duplex, flow control disabled uap_probe: vendor=0x02DF device=0x9104 class=0 function=1 uap_sdio mmc0:0001:1: firmware: requesting mrvl/helper_sd.bin uap_sdio mmc0:0001:1: firmware: requesting mrvl/sd8688_ap.bin UAP FW is active usbcore: registered new interface driver snd-usb-audio kjournald starting. Commit interval 5 seconds EXT3-fs (sdb2): using internal journal EXT3-fs (sdb2): mounted filesystem with writeback data mode NET: Registered protocol family 10 ADDRCONF(NETDEV_UP): eth0: link is not ready [ OK ] * Loading kernel modules...  * Loading manual drivers...  [ OK ] * Setting kernel variables (/etc/sysctl.conf)...  [ OK ] * Setting kernel variables (/etc/sysctl.d/10-console-messages.conf)...  [ OK ] * Setting kernel variables (/etc/sysctl.d/10-network-security.conf)...  [ OK ] * Activating swap...  [ OK ] * Starting early crypto disks...  [ OK ] * Starting remaining crypto disks...  [ OK ] * Checking file systems...  fsck 1.41.4 (27-Jan-2009) [ OK ] * Mounting local filesystems...  [ OK ] * Activating swapfile swap...  [ OK ] * Configuring network interfaces...  [ OK ] * Setting up console font and keymap...  [ OK ] * Starting system log daemon...  [ OK ] * Starting kernel log daemon...  [ OK ] * Starting system message bus dbus Ubuntu 9.04 DreamPlug ttyS0 Cheers, Innes. From dowelld at netscape.net Sun Aug 21 16:47:55 2011 From: dowelld at netscape.net (Dave Dowell) Date: Sun, 21 Aug 2011 17:47:55 +0100 Subject: [ARMedslack] DreamPlug hang In-Reply-To: <4E512043.1020706@innes.veryspeedy.net> References: <4E512043.1020706@innes.veryspeedy.net> Message-ID: <4E5136BB.4090202@netscape.net> Hi Innes, You need to go back over the Kirkwood install instructions, specifically the bit about setting up the uboot environment after completing the install. Your Dreamplug seems to be using a combined image (kernel+initrd rolled into one file), hence uboot is only set to load one file from sda. ARMedslack uses seperate kernel and initrd images, so uboot needs to be setup to load both images before calling the kernel to boot. Work through section 5.0 of the Kirkwood install instuctions. Specifically this bit. setenv bootcmd_slk 'usb start;ext2load usb 0:1 0x01100000 /uinitrd-kirkwood;ext2load usb 0:1 0x00800000 /uImage-kirkwood;bootm 0x00800000 0x01100000' The first ext2load command of that line loads the initrd. The second ext2load command of that line loads the kernel. The bootm command uses the load addresses of both of the loaded files. Thanks Dave On 21/08/2011 16:12, Innes Read wrote: > Hi, > > Newbie alert! This is my first post and first steps with the Kirkwood > ARM stuff so please go easy on me. > > I've just obtained a Dreamplug device, basically a slightly upgraded > Guruplug. Following the Armedslack install instructions I get a > solidly reproducible hang on initial kernel boot. For grins I saw > someone on the list had posted a 2.6.38.7 kernel and I installed the > uImage for that onto a memory card and booted... with exactly the same > result. My uneducated guess is that there is some module that is > locking the system up (wrong/missing) and/or I've forgotten something > really important! > > I'm happy to provide additional data and try suggestions out, in fact > it would be a great learning experience on how the initial kernel > stuff works. I've pasted a failing boot below, and following that is > a working one using the kernel supplied with the device. Here's the > failing boot from the U-Boot prompt. The uImage file is on a FAT16 > partition, /dev/sdb1, and the uinitrd is the same place and also > copied to the second ext2 partition, /dev/sdb2 (or in RAM if doing TFTP): > > run bootcmd_sdb > > (Re)start USB... > USB: Register 10011 NbrPorts 1 > USB EHCI 1.00 > scanning bus for devices... 4 USB Device(s) found > scanning bus for storage devices... 2 Storage Device(s) found > reading uImage > > 2024580 bytes read > ## Booting kernel from Legacy Image at 06400000 ... > Image Name: Linux-2.6.38.7-kirkwood > Created: 2011-05-26 7:29:53 UTC > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 2024516 Bytes = 1.9 MiB > Load Address: 00008000 > Entry Point: 00008000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > OK > > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > [ 0.000000] Linux version 2.6.38.7-kirkwood (root at slackware) (gcc > version 4.5.2 (GCC) ) #1 PREEMPT Thu May 26 08:29:19 BST 2011 > [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), > cr=00053977 > [ 0.000000] CPU: VIVT data cache, VIVT instruction cache > [ 0.000000] Machine: Marvell GuruPlug Reference Board > [ 0.000000] Memory policy: ECC disabled, Data cache writeback > [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. > Total pages: 130048 > [ 0.000000] Kernel command line: console=ttyS0,115200 > root=/dev/sdb2 panic=10 rootwait > [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) > [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, > 262144 bytes) > [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 > bytes) > [ 0.000000] Memory: 512MB = 512MB total > [ 0.000000] Memory: 515308k/515308k available, 8980k reserved, 0K > highmem > [ 0.000000] Virtual kernel memory layout: > [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) > [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) > [ 0.000000] DMA : 0xffc00000 - 0xffe00000 ( 2 MB) > [ 0.000000] vmalloc : 0xe0800000 - 0xfe800000 ( 480 MB) > [ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) > [ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB) > [ 0.000000] .init : 0xc0008000 - 0xc0029000 ( 132 kB) > [ 0.000000] .text : 0xc0029000 - 0xc03ce968 (3735 kB) > [ 0.000000] .data : 0xc03d0000 - 0xc03f7af8 ( 159 kB) > [ 0.000000] Preemptable hierarchical RCU implementation. > [ 0.000000] RCU-based detection of stalled CPUs is disabled. > [ 0.000000] Verbose stalled-CPUs detection is disabled. > [ 0.000000] NR_IRQS:114 > [ 0.000000] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps > every 21474ms > [ 0.000000] Console: colour dummy device 80x30 > [ 3.656806] Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776) > [ 3.896687] pid_max: default: 32768 minimum: 301 > [ 3.896820] Security Framework initialized > [ 3.896892] Mount-cache hash table entries: 512 > [ 3.897193] Initializing cgroup subsys ns > [ 3.897205] ns_cgroup deprecated: consider using the > 'clone_children' flag without the ns_cgroup. > [ 3.897218] Initializing cgroup subsys cpuacct > [ 3.897233] Initializing cgroup subsys devices > [ 3.897242] Initializing cgroup subsys freezer > [ 3.897251] Initializing cgroup subsys net_cls > [ 3.897280] CPU: Testing write buffer coherency: ok > [ 3.899729] print_constraints: dummy: > [ 3.899900] NET: Registered protocol family 16 > [ 3.901086] Kirkwood: MV88F6281-A1, TCLK=200000000. > [ 3.901099] Feroceon L2: Cache support initialised. > [ 3.910270] bio: create slab at 0 > [ 3.911024] vgaarb: loaded > [ 3.912520] Switching to clocksource orion_clocksource > [ 3.916683] Switched to NOHz mode on CPU #0 > [ 3.931135] NET: Registered protocol family 2 > [ 3.931348] IP route cache hash table entries: 4096 (order: 2, > 16384 bytes) > [ 3.932062] TCP established hash table entries: 16384 (order: 5, > 131072 bytes) > [ 3.932415] TCP bind hash table entries: 16384 (order: 4, 65536 bytes) > [ 3.933112] TCP: Hash tables configured (established 16384 bind 16384) > [ 3.933125] TCP reno registered > [ 3.933138] UDP hash table entries: 256 (order: 0, 4096 bytes) > [ 3.933161] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) > [ 3.933454] NET: Registered protocol family 1 > [ 3.934652] audit: initializing netlink socket (disabled) > [ 3.934688] type=2000 audit(0.270:1): initialized > [ 3.993557] VFS: Disk quotas dquot_6.5.2 > [ 3.993672] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) > [ 3.993781] JFFS2 version 2.2. (NAND) (SUMMARY) ? 2001-2006 Red > Hat, Inc. > [ 3.994168] msgmni has been set to 1006 > [ 3.995000] Block layer SCSI generic (bsg) driver version 0.4 > loaded (major 253) > [ 3.995015] io scheduler noop registered > [ 3.995024] io scheduler deadline registered > [ 3.995084] io scheduler cfq registered (default) > [ 4.170023] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled > [ 4.191940] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a > 16550A > [ 4.565649] console [ttyS0] enabled > [ 4.577548] brd: module loaded > > > The system locks up absolutely solid at this point, every time, > whether I boot with the 2.6.38.7 kernel as above or if I boot, via > TFTP, the install kernel from Slackware 13.37. For comparison, here's > the boot from the stock kernel that comes with the Dreamplug: > > U-Boot 2011.06-02334-g8f495d9-dirty (Mar 28 2011 - 05:21:06) > Marvell-DreamPlug > > SoC: Kirkwood 88F6281_A0 > DRAM: 512 MiB > SF: Detected MX25L1606 with page size 256, total 1 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 > Marvell>> printenv > > baudrate=115200 > x_bootcmd_ethernet=ping 192.168.2.1 > x_bootcmd_usb=usb start > x_bootcmd_kernel=fatload usb 0 0x6400000 uImage > x_bootargs=console=ttyS0,115200 > x_bootargs_root=root=/dev/sda2 rootdelay=10 > ethact=egiga0 > ethaddr=F0:AD:4E:00:7B:4B > eth1addr=F0:AD:4E:00:7B:4C > ipaddr=192.168.1.14 > serverip=192.168.1.13 > arcNumber=2659 > mainlineLinux=yes > bootdelay=10 > bootcmd_sdb=setenv bootargs console=ttyS0,115200 root=/dev/sdb2 > panic=10 rootwait; usb start; run boot_sdb; > boot_sdb=fatload usb 1 0x6400000 uImage; bootm 0x6400000; > bootcmd_sda=${bootcmd_eth}; ${x_bootcmd_usb}; ${x_bootcmd_kernel}; > setenv bootargs ${x_bootargs} ${x_bootargs_root}; bootm 0x6400000; > bootcmd_eth=setenv ethact egiga0; ${x_bootcmd_ethernet}; setenv ethact > egiga1; ${x_bootcmd_ethernet} > clear_kernel_in_mem=echo Purging kernel in memory; mw 0x6400000 0x0 > 0x300000 > bootcmd=run clear_kernel_in_mem; run bootcmd_sdb; run bootcmd_sda > stdin=serial > stdout=serial > stderr=serial > > Environment size: 940/4092 bytes > Marvell>> run bootcmd_sda > > (Re)start USB... > USB: Register 10011 NbrPorts 1 > USB EHCI 1.00 > scanning bus for devices... 4 USB Device(s) found > scanning bus for storage devices... 2 Storage Device(s) found > reading uImage > > 2712400 bytes read > ## Booting kernel from Legacy Image at 06400000 ... > Image Name: Linux-2.6.33.6 > Created: 2011-02-08 8:18:48 UTC > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 2712336 Bytes = 2.6 MiB > Load Address: 00008000 > Entry Point: 00008000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > OK > > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > Linux version 2.6.33.6 (root at localhost.localdomain) (gcc version > 4.2.1) #1 PREEMPT Tue Feb 8 03:18:41 EST 2011 > CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 > CPU: VIVT data cache, VIVT instruction cache > Machine: Marvell GuruPlug Reference Board > Memory policy: ECC disabled, Data cache writeback > Built 1 zonelists in Zone order, mobility grouping on. Total pages: > 130048 > Kernel command line: console=ttyS0,115200 root=/dev/sda2 rootdelay=10 > PID hash table entries: 2048 (order: 1, 8192 bytes) > Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) > Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) > Memory: 256MB 256MB = 512MB total > Memory: 513408KB available (4832K code, 862K data, 140K init, 0K highmem) > SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 > Hierarchical RCU implementation. > NR_IRQS:114 > Console: colour dummy device 80x30 > Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776) > Mount-cache hash table entries: 512 > CPU: Testing write buffer coherency: ok > NET: Registered protocol family 16 > Kirkwood: MV88F6281-A1, TCLK=200000000. > Feroceon L2: Cache support initialised. > bio: create slab at 0 > vgaarb: loaded > SCSI subsystem initialized > usbcore: registered new interface driver usbfs > usbcore: registered new interface driver hub > usbcore: registered new device driver usb > cfg80211: Using static regulatory domain info > cfg80211: Regulatory domain: 00 > (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) > (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm) > (2457000 KHz - 2482000 KHz @ 20000 KHz), (600 mBi, 2000 mBm) > (2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm) > (5170000 KHz - 5250000 KHz @ 40000 KHz), (600 mBi, 2000 mBm) > (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 2000 mBm) > cfg80211: Calling CRDA to update world regulatory domain > Switching to clocksource orion_clocksource > NET: Registered protocol family 2 > IP route cache hash table entries: 4096 (order: 2, 16384 bytes) > TCP established hash table entries: 16384 (order: 5, 131072 bytes) > TCP bind hash table entries: 16384 (order: 4, 65536 bytes) > TCP: Hash tables configured (established 16384 bind 16384) > TCP reno registered > UDP hash table entries: 256 (order: 0, 4096 bytes) > UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) > NET: Registered protocol family 1 > RPC: Registered udp transport module. > RPC: Registered tcp transport module. > RPC: Registered tcp NFSv4.1 backchannel transport module. > JFFS2 version 2.2. (NAND) ? 2001-2006 Red Hat, Inc. > JFS: nTxBlock = 4012, nTxLock = 32102 > msgmni has been set to 1003 > alg: No test for stdrng (krng) > io scheduler noop registered > io scheduler deadline registered > io scheduler cfq registered (default) > Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled > serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A > console [ttyS0] enabled > brd: module loaded > loop: module loaded > No NAND device found. > MV-643xx 10/100/1000 ethernet driver version 1.4 > mv643xx_eth smi: probed > net eth0: port 0 with MAC address f0:ad:4e:00:7b:4b > net eth1: port 0 with MAC address f0:ad:4e:00:7b:4c > ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver > orion-ehci orion-ehci.0: Marvell Orion EHCI > orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1 > orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000 > orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00 > hub 1-0:1.0: USB hub found > hub 1-0:1.0: 1 port detected > Initializing USB Mass Storage driver... > usbcore: registered new interface driver usb-storage > USB Mass Storage support registered. > usbcore: registered new interface driver ums-datafab > usbcore: registered new interface driver ums-freecom > usbcore: registered new interface driver ums-jumpshot > usbcore: registered new interface driver ums-sddr09 > usbcore: registered new interface driver ums-sddr55 > mice: PS/2 mouse device common for all mice > rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0 > i2c /dev entries driver > cpuidle: using governor ladder > cpuidle: using governor menu > sdhci: Secure Digital Host Controller Interface driver > sdhci: Copyright(c) Pierre Ossman > mmc0: mvsdio driver initialized, lacking card detect (fall back to > polling) > Registered led device: guruplug:red:health > Registered led device: guruplug:green:health > Registered led device: guruplug:red:wmode > Registered led device: guruplug:green:wmode > mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver > mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver > mv_xor mv_xor.0: Marvell XOR: ( xor cpy ) > mmc0: new high speed SDIO card at address 0001 > mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy ) > mv_xor mv_xor.2: Marvell XOR: ( xor cpy ) > mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy ) > usbcore: registered new interface driver hiddev > usbcore: registered new interface driver usbhid > usbhid: USB HID core driver > oprofile: using timer interrupt. > TCP cubic registered > NET: Registered protocol family 17 > lib80211: common routines for IEEE802.11 drivers > rtc-mv rtc-mv: setting system clock to 2011-08-21 14:12:27 UTC > (1313935947) > Waiting 10sec before mounting root device... > usb 1-1: new high speed USB device using orion-ehci and address 2 > hub 1-1:1.0: USB hub found > hub 1-1:1.0: 4 ports detected > usb 1-1.1: new high speed USB device using orion-ehci and address 3 > scsi0 : usb-storage 1-1.1:1.0 > usb 1-1.4: new full speed USB device using orion-ehci and address 4 > input: C-Media USB Headphone Set as > /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.3/input/input0 > generic-usb 0003:0D8C:000C.0001: input: USB HID v1.00 Device [C-Media > USB Headphone Set ] on usb-orion-ehci.0-1.4/input3 > scsi 0:0:0:0: Direct-Access Generic STORAGE DEVICE 9910 PQ: 0 > ANSI: 0 > sd 0:0:0:0: Attached scsi generic sg0 type 0 > scsi 0:0:0:1: Direct-Access Generic STORAGE DEVICE 9910 PQ: 0 > ANSI: 0 > sd 0:0:0:0: [sda] 3842048 512-byte logical blocks: (1.96 GB/1.83 GiB) > sd 0:0:0:1: Attached scsi generic sg1 type 0 > sd 0:0:0:0: [sda] Write Protect is off > sd 0:0:0:0: [sda] Assuming drive cache: write through > sd 0:0:0:1: [sdb] 16121856 512-byte logical blocks: (8.25 GB/7.68 GiB) > sd 0:0:0:1: [sdb] Write Protect is off > sd 0:0:0:1: [sdb] Assuming drive cache: write through > sd 0:0:0:0: [sda] Assuming drive cache: write through > sda: sda1 sda2 > sda: p2 size 3653412 exceeds device capacity, limited to end of disk > sd 0:0:0:1: [sdb] Assuming drive cache: write through > sdb: > sd 0:0:0:0: [sda] Assuming drive cache: write through > sd 0:0:0:0: [sda] Attached SCSI removable disk > sdb1 sdb2 > sd 0:0:0:1: [sdb] Assuming drive cache: write through > sd 0:0:0:1: [sdb] Attached SCSI removable disk > EXT3-fs (sda2): warning: maximal mount count reached, running e2fsck > is recommended > kjournald starting. Commit interval 5 seconds > EXT3-fs (sda2): using internal journal > EXT3-fs (sda2): mounted filesystem with writeback data mode > VFS: Mounted root (ext3 filesystem) on device 8:2. > Freeing init memory: 140K > * Filesystem type 'fusectl' is not supported. Skipping > mount. > * Setting preliminary keymap...  > [ OK ] > * Starting kernel event manager...  > [ OK ] > * Loading hardware drivers...  Bluetooth: Core ver 2.15 > NET: Registered protocol family 31 > Bluetooth: HCI device and connection manager initialized > Bluetooth: HCI socket layer initialized > sata_mv sata_mv.0: version 1.28 > sata_mv sata_mv.0: slots 32 ports 1 > scsi1 : sata_mv > libertas_sdio: Libertas SDIO driver > ata1: SATA max UDMA/133 irq 21 > libertas_sdio: Copyright Pierre Ossman > libertas_sdio mmc0:0001:1: firmware: requesting sd8688_helper.bin > ata1: SATA link down (SStatus 0 SControl F300) > libertas: can't load helper firmware > libertas: failed to load helper firmware > libertas_sdio: probe of mmc0:0001:1 failed with error -2 > Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2 > btmrvl_sdio mmc0:0001:2: firmware: requesting sd8688_helper.bin > btmrvl_sdio_download_helper: request_firmware(helper) failed, error > code = -2 > btmrvl_sdio_download_fw: Failed to download helper! > btmrvl_sdio_probe: Downloading firmware failed! > eth1: link up, 100 Mb/s, full duplex, flow control disabled > uap_probe: vendor=0x02DF device=0x9104 class=0 function=1 > uap_sdio mmc0:0001:1: firmware: requesting mrvl/helper_sd.bin > uap_sdio mmc0:0001:1: firmware: requesting mrvl/sd8688_ap.bin > UAP FW is active > usbcore: registered new interface driver snd-usb-audio > kjournald starting. Commit interval 5 seconds > EXT3-fs (sdb2): using internal journal > EXT3-fs (sdb2): mounted filesystem with writeback data mode > NET: Registered protocol family 10 > ADDRCONF(NETDEV_UP): eth0: link is not ready > > [ OK ] > * Loading kernel modules...  * Loading manual drivers... >  > [ OK ] > * Setting kernel variables (/etc/sysctl.conf)...  > [ OK ] > * Setting kernel variables > (/etc/sysctl.d/10-console-messages.conf)...  > [ OK ] > * Setting kernel variables > (/etc/sysctl.d/10-network-security.conf)...  > [ OK ] > * Activating swap...  > [ OK ] > * Starting early crypto disks...  > [ OK ] > * Starting remaining crypto disks...  > [ OK ] > * Checking file systems...  fsck 1.41.4 (27-Jan-2009) > > [ OK ] > * Mounting local filesystems...  > [ OK ] > * Activating swapfile swap...  > [ OK ] > * Configuring network interfaces...  > [ OK ] > * Setting up console font and keymap...  > [ OK ] > * Starting system log daemon...  > [ OK ] > * Starting kernel log daemon...  > [ OK ] > > * Starting system message bus dbus Ubuntu 9.04 DreamPlug ttyS0 > > Cheers, Innes. > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack From armedslack at innes.veryspeedy.net Sun Aug 21 17:22:03 2011 From: armedslack at innes.veryspeedy.net (Innes Read) Date: Sun, 21 Aug 2011 18:22:03 +0100 Subject: [ARMedslack] DreamPlug hang In-Reply-To: <4E5136BB.4090202@netscape.net> References: <4E512043.1020706@innes.veryspeedy.net> <4E5136BB.4090202@netscape.net> Message-ID: <4E513EBB.8000502@innes.veryspeedy.net> Dave, Thanks for the quick response. I understand your point for the current U-Boot stuff and will deal with that (ext2load is not available with the Dreamplug it seems, so I'm stuck with a FAT16 option only but hey, same difference). In the meantime, the hang occurs even when I follow the similar instructions for GA Slackware 13.37, ie. see the following output from the U-Boot prompt: tftpboot 0x01100000 armedslack-13.37/uinitrd-kirkwood.img No link on egiga0 Using egiga1 device TFTP from server 192.168.1.13; our IP address is 192.168.1.14 Filename 'armedslack-13.37/uinitrd-kirkwood.img'. Load address: 0x1100000 Loading: *################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################### done Bytes transferred = 17397761 (1097801 hex) Marvell>> tftpboot 0x00800000 armedslack-13.37/uImage-kirkwood Using egiga1 device TFTP from server 192.168.1.13; our IP address is 192.168.1.14 Filename 'armedslack-13.37/uImage-kirkwood'. Load address: 0x800000 Loading: *################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ######## done Bytes transferred = 2033192 (1f0628 hex) Marvell>> setenv bootargs console=ttyS0,115200 nodhcp kbd=uk root=/dev/ram rw Marvell>> bootm 0x00800000 0x01100000 ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-2.6.38.4-kirkwood Created: 2011-04-22 11:50:56 UTC 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 Installer Created: 2011-04-25 6:21:47 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 17397697 Bytes = 16.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.000000] Linux version 2.6.38.4-kirkwood (root at wizbit) (gcc version 4.5.2 (GCC) ) #2 PREEMPT Fri Apr 22 12:50:29 BST 2011 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] Machine: Marvell GuruPlug Reference Board [ 0.000000] Memory policy: ECC disabled, Data cache writeback [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 [ 0.000000] Kernel command line: console=ttyS0,115200 nodhcp kbd=uk root=/dev/ram rw [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] Memory: 512MB = 512MB total [ 0.000000] Memory: 498308k/498308k available, 25980k reserved, 0K highmem [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) [ 0.000000] DMA : 0xffc00000 - 0xffe00000 ( 2 MB) [ 0.000000] vmalloc : 0xe0800000 - 0xfe800000 ( 480 MB) [ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) [ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB) [ 0.000000] .init : 0xc0008000 - 0xc0029000 ( 132 kB) [ 0.000000] .text : 0xc0029000 - 0xc03d1a5c (3747 kB) [ 0.000000] .data : 0xc03d2000 - 0xc03f9c38 ( 160 kB) [ 0.000000] Preemptable hierarchical RCU implementation. [ 0.000000] RCU-based detection of stalled CPUs is disabled. [ 0.000000] Verbose stalled-CPUs detection is disabled. [ 0.000000] NR_IRQS:114 [ 0.000000] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms [ 0.000000] Console: colour dummy device 80x30 [ 12.464411] Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776) [ 12.704289] pid_max: default: 32768 minimum: 301 [ 12.704424] Security Framework initialized [ 12.704496] Mount-cache hash table entries: 512 [ 12.704793] Initializing cgroup subsys ns [ 12.704804] ns_cgroup deprecated: consider using the 'clone_children' flag without the ns_cgroup. [ 12.704818] Initializing cgroup subsys cpuacct [ 12.704833] Initializing cgroup subsys devices [ 12.704842] Initializing cgroup subsys freezer [ 12.704851] Initializing cgroup subsys net_cls [ 12.704915] CPU: Testing write buffer coherency: ok [ 12.707457] print_constraints: dummy: [ 12.707634] NET: Registered protocol family 16 [ 12.708861] Kirkwood: MV88F6281-A1, TCLK=200000000. [ 12.708875] Feroceon L2: Cache support initialised. [ 12.718412] bio: create slab at 0 [ 12.719203] vgaarb: loaded [ 12.720747] Switching to clocksource orion_clocksource [ 12.724286] Switched to NOHz mode on CPU #0 [ 12.739818] NET: Registered protocol family 2 [ 12.740028] IP route cache hash table entries: 4096 (order: 2, 16384 bytes) [ 12.740754] TCP established hash table entries: 16384 (order: 5, 131072 bytes) [ 12.741649] TCP bind hash table entries: 16384 (order: 4, 65536 bytes) [ 12.741830] TCP: Hash tables configured (established 16384 bind 16384) [ 12.741840] TCP reno registered [ 12.741851] UDP hash table entries: 256 (order: 0, 4096 bytes) [ 12.741874] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [ 12.742171] NET: Registered protocol family 1 [ 12.742381] Trying to unpack rootfs image as initramfs... [ 13.846239] Freeing initrd memory: 16988K [ 13.847383] audit: initializing netlink socket (disabled) [ 13.847434] type=2000 audit(1.370:1): initialized [ 13.906528] VFS: Disk quotas dquot_6.5.2 [ 13.906636] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 13.906750] JFFS2 version 2.2. (NAND) (SUMMARY) ? 2001-2006 Red Hat, Inc. [ 13.907145] msgmni has been set to 1006 [ 13.908019] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [ 13.908034] io scheduler noop registered [ 13.908042] io scheduler deadline registered [ 13.908105] io scheduler cfq registered (default) [ 14.082907] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [ 14.104668] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A [ 14.487504] console [ttyS0] enabled [ 14.499610] brd: module loaded And solid hang again, same place. So this is still going to be a problem even if I fix the current U-Boot commands to deal with the slightly different way of loading. Or am I missing something? Cheers, Innes. On 21/08/2011 17:47, Dave Dowell wrote: > Hi Innes, > > You need to go back over the Kirkwood install instructions, specifically > the bit about setting up the uboot environment after completing the > install. > > Your Dreamplug seems to be using a combined image (kernel+initrd rolled > into one file), hence uboot is only set to load one file from sda. > ARMedslack uses seperate kernel and initrd images, so uboot needs to be > setup to load both images before calling the kernel to boot. > > Work through section 5.0 of the Kirkwood install instuctions. > Specifically this bit. > > setenv bootcmd_slk 'usb start;ext2load usb 0:1 0x01100000 > /uinitrd-kirkwood;ext2load usb 0:1 0x00800000 /uImage-kirkwood;bootm > 0x00800000 0x01100000' > > > The first ext2load command of that line loads the initrd. > The second ext2load command of that line loads the kernel. > The bootm command uses the load addresses of both of the loaded files. > > Thanks > Dave From MLangfinger at web.de Sun Aug 21 17:43:12 2011 From: MLangfinger at web.de (Michael Langfinger) Date: Sun, 21 Aug 2011 19:43:12 +0200 (CEST) Subject: [ARMedslack] DreamPlug hang Message-ID: <1941599696.2053847.1313948592389.JavaMail.fmail@mwmweb042> 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 ___________________________________________________________ Schon geh?rt? WEB.DE hat einen genialen Phishing-Filter in die Toolbar eingebaut! http://produkte.web.de/go/toolbar From armedslack at innes.veryspeedy.net Mon Aug 22 10:50:47 2011 From: armedslack at innes.veryspeedy.net (Innes Read) Date: Mon, 22 Aug 2011 11:50:47 +0100 Subject: [ARMedslack] DreamPlug hang In-Reply-To: <1941599696.2053847.1313948592389.JavaMail.fmail@mwmweb042> References: <1941599696.2053847.1313948592389.JavaMail.fmail@mwmweb042> Message-ID: <4E523487.3060209@innes.veryspeedy.net> 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 > ___________________________________________________________ > Schon geh?rt? WEB.DE hat einen genialen Phishing-Filter in die > Toolbar eingebaut! http://produkte.web.de/go/toolbar > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack From pr0f3ss0r1492 at yahoo.com Mon Aug 22 11:40:53 2011 From: pr0f3ss0r1492 at yahoo.com (Ottavio) Date: Mon, 22 Aug 2011 12:40:53 +0100 Subject: [ARMedslack] Current - Firefox 3.6.19 segmentation fault Message-ID: On 20 August 2011 16:42, Ottavio wrote: > > Then I have a second and bigger problem. Once I have started xterm I > launch Firefox and I get a segmentation fault: > > http://img840.imageshack.us/img840/9855/firefoxcrash.png > > I have reinstalled Firefox but I get the same error. I have downgraded Firefox to 3.6.19, from the armedslack-13.37/patches/ repository. I still have the dreaded segmentation fault. Would it help if I posted the /var/log/packages ? I have tried to up the memory but it looks like qemu accepts a max of 356 M on the versatile board. Any ideas? -- Ottavio A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? From louigi600 at yahoo.it Mon Aug 22 12:53:03 2011 From: louigi600 at yahoo.it (Davide) Date: Mon, 22 Aug 2011 13:53:03 +0100 (BST) Subject: [ARMedslack] R: Current: Problem with xterm and seg fault on firefox In-Reply-To: Message-ID: <1314017583.25058.YahooMailClassic@web29709.mail.ird.yahoo.com> Installare Xorg partendo da un miniroot e' di sicuro una tortura soprattutto dato che xorg e' stato suddiviso in un botto di pacchetti. Ti consiglio di collegarti alla macchina virtuale via ssh abilitando il flag -X che ridirige la grafica nel tunnel ssh Una volta che sei dentro prova a lanciare qualcosa di grafico (tipo xclock) e dovresti vederlo apparire sul tuo desktop. Se cio non avviene comincia a debuggare il motivo. Piano piano lavora verso cose piu complicate tipo xterm e il browser in modo da scoprire i problemi gradualmente (in modo da facilitarti il debugging). Ciao Davide --- Sab 20/8/11, Ottavio ha scritto: > Da: Ottavio > Oggetto: [ARMedslack] Current: Problem with xterm and seg fault on firefox > A: ARMedslack at lists.armedslack.org > Data: Sabato 20 agosto 2011, 17:42 > Hello, > > I am trying to build a minimal installation with X11 and > Firefox, > mirroring what I have already on 64 bit PC. > > I am running this image in qemu with command line: > > qemu-system-arm.exe -M versatilepb? -drive > file=slackware-arm-root,index=0,media=disk???-kernel > zImage-versatile > -initrd initrd-versatile.gz -append "root=/dev/sda1 > rootfs=ext2"? -m > 256 -usb? -no-shutdown > > I've started from the current miniroot and added packages > with > slackpkg (a painful process). So I've got to the point > where I thin I > have all the necessary packages and all packages have been > upgraded so > they are all up to date. > > On the pc target I have no window managers and start > firefox from the > console with this line: > > $ startx firefox & > > but on the ARM target I get error:? xterm: bad command > line option "xterm". > > Screenshot: http://img694.imageshack.us/img694/1952/startx.png > > If I start xterm with this line: > > xinit -- :0 > > I can start xterm fine. I wonder if anybody has any ideas. > > Then I have a second and bigger problem. Once I have > started xterm I > launch Firefox and I get a segmentation fault: > > http://img840.imageshack.us/img840/9855/firefoxcrash.png > > I have reinstalled Firefox but I get the same error. > > Thank you for your attention > > -- > Ottavio > > > A: Because it messes up the order in which people normally > read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From pr0f3ss0r1492 at yahoo.com Tue Aug 23 11:14:40 2011 From: pr0f3ss0r1492 at yahoo.com (Ottavio) Date: Tue, 23 Aug 2011 12:14:40 +0100 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) Message-ID: Note: cc'ed to William Schaub Hello, William Schaub has stated an interest in making an Armedslack image for Efika MX board, at the moment on the Genesi Smartbook and Smartop: http://www.genesi-usa.com/products/smartbook http://www.genesi-usa.com/products/efika Has anybody on this list any interest in working on this project? I myself would like to, but I haven't got either the hardware or the necessary skills but I would be interested in purchasing a proper ARM netbook with Slackware on it. -- Ottavio A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? From louigi600 at yahoo.it Tue Aug 23 11:45:30 2011 From: louigi600 at yahoo.it (Davide) Date: Tue, 23 Aug 2011 12:45:30 +0100 (BST) Subject: [ARMedslack] R: Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: Message-ID: <1314099930.62865.YahooMailClassic@web29709.mail.ird.yahoo.com> Like the Toschiba AC100 it's a arm7 instruction set machine so it should run instruction set ARM4 with consequent performance loss. So armedslack userland should run on that hardware: all you need is means to boot custom kernel and last but not least a custom kernel that can run armedslack userland. Regards David --- Mar 23/8/11, Ottavio ha scritto: > Da: Ottavio > Oggetto: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) > A: ARMedslack at lists.armedslack.org > Cc: wschaub at steubentech.com > Data: Marted? 23 agosto 2011, 13:14 > Note: cc'ed to William Schaub > > Hello, > > William Schaub has stated an interest in making an > Armedslack image > for Efika MX board, at the moment on the Genesi Smartbook > and Smartop: > http://www.genesi-usa.com/products/smartbook > http://www.genesi-usa.com/products/efika > > Has anybody on this list any interest in working on this > project? I > myself would like to, but I haven't got either the hardware > or the > necessary skills but I would be interested in purchasing a > proper ARM > netbook with Slackware on it. > > -- > Ottavio > > > A: Because it messes up the order in which people normally > read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From m-lists at biscuit.org.uk Tue Aug 23 12:17:52 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 23 Aug 2011 13:17:52 +0100 (BST) Subject: [ARMedslack] Current - Firefox 3.6.19 segmentation fault In-Reply-To: References: Message-ID: > I have tried to up the memory but it looks like qemu accepts a max of > 356 M on the versatile board. I installed a *full* installation of -current inside QEMU and am running firefox-6.0 in 256MB RAM. It's slow, as to be expected, but it's not crashed. Does it crash only when you view certain pages? I'm just guessing, but it may be that you haven't got all of the required packages installed. The runtime packages (gathered from ldd) for firefox are: dbus alsa-lib atk cairo dbus-glib expat freetype gdk-pixbuf2 glib2 gtk+2 libnotify libpng pango startup-notification fontconfig libX11 libXau libXdmcp libXext libXrender libXt libxcb pixman -- Stuart Winter Slackware ARM: www.armedslack.org From m-lists at biscuit.org.uk Tue Aug 23 12:26:00 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 23 Aug 2011 13:26:00 +0100 (BST) Subject: [ARMedslack] Current - Firefox 3.6.19 segmentation fault In-Reply-To: References: Message-ID: Also unless you've got a patched qemu, qemu does not support >256MB RAM for the versatile board. On Tue, 23 Aug 2011, Stuart Winter wrote: > > > I have tried to up the memory but it looks like qemu accepts a max of > > 356 M on the versatile board. > > I installed a *full* installation of -current inside QEMU and am running > firefox-6.0 in 256MB RAM. It's slow, as to be expected, but it's not > crashed. > Does it crash only when you view certain pages? > > I'm just guessing, but it may be that you haven't got all of the required > packages installed. > The runtime packages (gathered from ldd) for firefox are: > dbus > alsa-lib > atk > cairo > dbus-glib > expat > freetype > gdk-pixbuf2 > glib2 > gtk+2 > libnotify > libpng > pango > startup-notification > fontconfig > libX11 > libXau > libXdmcp > libXext > libXrender > libXt > libxcb > pixman > > > -- Stuart Winter Slackware ARM: www.armedslack.org From pr0f3ss0r1492 at yahoo.com Tue Aug 23 12:47:16 2011 From: pr0f3ss0r1492 at yahoo.com (Ottavio) Date: Tue, 23 Aug 2011 13:47:16 +0100 Subject: [ARMedslack] R: Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: <1314099930.62865.YahooMailClassic@web29709.mail.ird.yahoo.com> Message-ID: On 23 August 2011 12:45, Davide wrote: > all you need is means to boot custom kernel and last but not least a custom kernel > that can run armedslack userland Well, this is exactly what I would like to verify before hand. I won't commit to buy a machine that can only run Ubuntu Maverick. -- Ottavio Caruso A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? From pr0f3ss0r1492 at yahoo.com Tue Aug 23 22:56:26 2011 From: pr0f3ss0r1492 at yahoo.com (Ottavio) Date: Tue, 23 Aug 2011 23:56:26 +0100 Subject: [ARMedslack] Current - Firefox 3.6.19 segmentation fault In-Reply-To: References: Message-ID: On 23 August 2011 13:17, Stuart Winter wrote: > >> I have tried to up the memory but it looks like qemu accepts a max of >> 356 M on the versatile board. > > I installed a *full* installation of -current inside QEMU and am running > firefox-6.0 in 256MB RAM. ?It's slow, as to be expected, but it's not > crashed. > Does it crash only when you view certain pages? > > I'm just guessing, but it may be that you haven't got all of the required > packages installed. > The runtime packages (gathered from ldd) for firefox are: > dbus > alsa-lib > atk > cairo > dbus-glib > expat > freetype > gdk-pixbuf2 > glib2 > gtk+2 > libnotify > libpng > pango > startup-notification > fontconfig > libX11 > libXau > libXdmcp > libXext > libXrender > libXt > libxcb > pixman > > I had downgraded to firefox 3.6.19 and that was the result of ldd: # ldd /usr/lib/firefox-3.6.19/firefox-bin libxul.so => not found libxpcom.so => not found libplc4.so => not found libnspr4.so => not found libpthread.so.0 => /lib/libpthread.so.0 (0x40165000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x4003e000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x4011f000) libc.so.6 => /lib/libc.so.6 (0x40186000) /lib/ld-linux.so.3 (0x40017000) libm.so.6 => /lib/libm.so.6 (0x402d1000) I believe the first 4 libraries are in the firefox directory and I shouldn't worry about them. These are the packages installed: # ls /var/log/packages/ aaa_base-13.37-arm-2 aaa_elflibs-13.37-arm-5 aaa_terminfo-5.8-arm-1 acl-2.2.50-arm-1 atk-1.32.0-arm-1 attr-2.4.45-arm-1 bash-4.1.010-arm-1 bin-11.1-arm-1 bzip2-1.0.6-arm-1 cairo-1.10.2-arm-2 coreutils-8.12-arm-1 cxxlibs-6.0.14-arm-2 dbus-1.4.1-arm-1 dcron-4.4-arm-1 devs-2.3.1-arm-1 dhcpcd-5.2.12-arm-1 dialog-1.1_20100428-arm-2 diffutils-3.0-arm-1 e2fsprogs-1.41.14-arm-1 ed-1.4-arm-1 etc-13.013-arm-1 file-5.07-arm-1 findutils-4.4.2-arm-1 fontconfig-2.8.0-arm-1 gawk-3.1.8-arm-1 gdk-pixbuf2-2.23.3-arm-1 gettext-0.18.1.1-arm-1 getty-ps-2.1.0b-arm-1 glib2-2.28.6-arm-1 glibc-solibs-2.13-arm-3 glibc-zoneinfo-2.13-noarch-3 gnupg-1.4.11-arm-1 gnutls-2.12.7-arm-1 grep-2.7-arm-1 groff-1.21-arm-1 gtk+2-2.24.4-arm-1 gzip-1.4-arm-1 inotify-tools-3.14-arm-1 iproute2-2.6.37-arm-1 iputils-s20101006-arm-1 jfsutils-1.1.15-arm-1 kbd-1.15.2-arm-1 kernel-modules-versatile-2.6.39.4_versatile-arm-1 less-443-arm-1 lftp-4.2.2-arm-1 libICE-1.0.7-arm-1 libSM-1.2.0-arm-1 libX11-1.4.3-arm-2 libXau-1.0.6-arm-1 libXaw-1.0.9-arm-1 libXcomposite-0.4.3-arm-1 libXcursor-1.1.11-arm-1 libXdamage-1.1.3-arm-1 libXdmcp-1.1.0-arm-1 libXext-1.2.0-arm-1 libXfixes-5.0-arm-1 libXfont-1.4.3-arm-1 libXft-2.2.0-arm-1 libXi-1.4.2-arm-1 libXinerama-1.1.1-arm-1 libXmu-1.1.0-arm-1 libXpm-3.5.9-arm-1 libXrandr-1.3.1-arm-1 libXrender-0.9.6-arm-1 libXt-1.1.1-arm-1 libdrm-2.4.25-arm-1 libfontenc-1.1.0-arm-1 libgcrypt-1.4.6-arm-1 libgpg-error-1.9-arm-1 libpciaccess-0.12.1-arm-1 libxcb-1.7-arm-1 libxkbfile-1.0.7-arm-1 links-2.3pre1-arm-1 lvm2-2.02.84-arm-1 lzo-2.03-arm-1 man-1.6g-arm-1 mesa-7.10.2-arm-1 module-init-tools-3.12-arm-2 mozilla-firefox-3.6.19-armv5t-1_slack13.37 mtd-utils-240411-arm-1 nano-2.3.1-arm-1 ncurses-5.9-arm-1 net-tools-1.60-arm-2 network-scripts-13.0-noarch-2 nfs-utils-1.2.3-arm-3 ntp-4.2.6p3-arm-2 openssh-5.8p1-arm-1 openssl-solibs-0.9.8r-arm-2 pango-1.28.4-arm-1 pixman-0.20.2-arm-1 pkgtools-13.37-noarch-6 portmap-6.0-arm-1 procps-3.2.8-arm-2 rsync-3.0.8-arm-1 sed-4.2.1-arm-1 shadow-4.1.4.3-arm-2 slackpkg-2.82.0-arm-2 startup-notification-0.10-arm-1 sysvinit-2.86-arm-1 sysvinit-scripts-1.2-noarch-13 tar-1.26-arm-1 telnet-0.17-arm-1 traceroute-2.0.17-arm-1 u-boot-tools-2011.03-arm-1 udev-165-arm-2 usbutils-002-arm-1 utempter-1.1.5-arm-1 util-linux-2.19-arm-1 vim-7.3.154-arm-1 wget-1.13-arm-1 which-2.20-arm-1 xauth-1.0.5-arm-1 xcb-util-0.3.6-arm-1 xf86-input-evdev-2.6.0-arm-1 xf86-video-fbdev-0.4.2-arm-2 xinit-1.3.0-arm-1 xkbcomp-1.2.1-arm-1 xkeyboard-config-2.2.1-noarch-1 xorg-server-1.9.5-arm-1 xterm-267-arm-1 xz-5.0.2-arm-1 I will install a proper window manager and see if that sorts things out -- Ottavio A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? From slothpuck at gmail.com Wed Aug 24 21:24:17 2011 From: slothpuck at gmail.com (lee jones) Date: Wed, 24 Aug 2011 21:24:17 +0000 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) Message-ID: I've just recently bought an efika mx smartbook, and I'd be intrested in getting armedslaack onto it as well. From what I've read elsewhere online, the smartbook will try to boot from sd first then the internal flash. Though I must admit I have no idea on what to set up to create some sort of bootloader. Armedslack on the efika mx could be intresting - the supplied ubuntu install works but it's not all that fast. Maybe armedslack with kde 3.5 might be faster? ljones -------------- next part -------------- An HTML attachment was scrubbed... URL: From pr0f3ss0r1492 at yahoo.com Wed Aug 24 21:56:10 2011 From: pr0f3ss0r1492 at yahoo.com (Ottavio) Date: Wed, 24 Aug 2011 22:56:10 +0100 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: On 24 August 2011 22:24, lee jones wrote: > Armedslack on the efika mx could be intresting - the supplied ubuntu install > works but it's not all that fast. Maybe armedslack with kde 3.5 might be > faster? > Thanks for your interest in the matter, although to be honest I myself am starting to lose interest in it. I have applied for an account on the Power Developer forum (for those who are not familiar: Genesi used to be a Power PC manufacturer, then they switched to ARM but retained the 'Power' so to speak) but I haven't had a contact yet. It looks like this August the whole world is on holiday. -- Ottavio A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? From slothpuck at gmail.com Wed Aug 24 23:15:07 2011 From: slothpuck at gmail.com (lee jones) Date: Wed, 24 Aug 2011 23:15:07 +0000 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: On Wed, Aug 24, 2011 at 9:56 PM, Ottavio wrote: > On 24 August 2011 22:24, lee jones wrote: > > Armedslack on the efika mx could be intresting - the supplied ubuntu > install > > works but it's not all that fast. Maybe armedslack with kde 3.5 might be > > faster? > > > > Thanks for your interest in the matter, although to be honest I myself > am starting to lose interest in it. I have applied for an account on > the Power Developer forum (for those who are not familiar: Genesi > used to be a Power PC > manufacturer, then they switched to ARM but retained the 'Power' so to > speak) but I haven't had a contact yet. It looks like this August the > whole world is on holiday. > > > > -- > Ottavio > > > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > Must admit I'd still like to try it if only to replace that s-l-o-w ubuntu install. Though I'm just not sure how to go about it but I was reading this; http://steubentech.com/~talon/Efika-MX/mavericksd/README.txt In particular the end of it as far as I can tell what is needed is a kernel, initrd and a boot.scr file. Though weather it is possible to use armedslack's kernel/initrd or the efika's ones I'm not sure. I'm no expert at this but at the least surely the kernel versions would have to tie up which might cause problems if they don't. Must admit I'm really fumbling around in the dark here x.x . -- :) SP -------------- next part -------------- An HTML attachment was scrubbed... URL: From pr0f3ss0r1492 at yahoo.com Thu Aug 25 00:46:45 2011 From: pr0f3ss0r1492 at yahoo.com (Ottavio) Date: Thu, 25 Aug 2011 01:46:45 +0100 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: On 25 August 2011 00:15, lee jones wrote: > Must admit I'd still like to try it if only to replace that s-l-o-w ubuntu > install. Though I'm just not sure how to go about it but I was reading this; > > http://steubentech.com/~talon/Efika-MX/mavericksd/README.txt > > In particular the end of it as far as I can tell what is needed is a kernel, > initrd and a boot.scr file. It looks like that the kernel is in the 'linux-image-2.6.31.14.20-efikamx' package: http://packages.efikamx.info/pool/main/l/linux-source-2.6.31.14.20-efikamx/ It's a .deb file and if you extract it in the /boot directory you'll find "vmlinuz-2.6.31.14.20-efikamx". There's no separate initrd. Whether this kernel would boot slackware root out of the box, I doubt it because armedslack-13.37 comes with the 2.6.38.4 kernel and armedslack-current with 2.6.39.4 but this is only my opinion. If you have an account on power developer you could do us a favour and ask there. About creating the boot.src and/or building the kernel from scratch: https://wiki.linaro.org/Boards/Efika The standard boot.src should be in the /boot partition of the SSD. > Though weather it is possible to use > armedslack's kernel/initrd or the > efika's ones I'm not sure. The kernels on armedslack repository are only for kirkwood and versatile. -- Ottavio A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? From slothpuck at gmail.com Thu Aug 25 20:17:09 2011 From: slothpuck at gmail.com (lee jones) Date: Thu, 25 Aug 2011 20:17:09 +0000 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: On Thu, Aug 25, 2011 at 12:46 AM, Ottavio wrote: > On 25 August 2011 00:15, lee jones wrote: > > Must admit I'd still like to try it if only to replace that s-l-o-w > ubuntu > > install. Though I'm just not sure how to go about it but I was reading > this; > > > > http://steubentech.com/~talon/Efika-MX/mavericksd/README.txt > > > > In particular the end of it as far as I can tell what is needed is a > kernel, > > initrd and a boot.scr file. > > It looks like that the kernel is in the > 'linux-image-2.6.31.14.20-efikamx' package: > http://packages.efikamx.info/pool/main/l/linux-source-2.6.31.14.20-efikamx/ > > It's a .deb file and if you extract it in the /boot directory you'll > find "vmlinuz-2.6.31.14.20-efikamx". There's no separate initrd. > > Whether this kernel would boot slackware root out of the box, I doubt > it because armedslack-13.37 comes with the 2.6.38.4 kernel and > armedslack-current with 2.6.39.4 but this is only my opinion. If you > have an account on power developer you could do us a favour and ask > there. > > About creating the boot.src and/or building the kernel from scratch: > https://wiki.linaro.org/Boards/Efika > > The standard boot.src should be in the /boot partition of the SSD. > > > Though weather it is possible to use > > armedslack's kernel/initrd or the > > efika's ones I'm not sure. > > The kernels on armedslack repository are only for kirkwood and versatile. > > > -- > Ottavio > > > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > Just been trying to make a start on this now, but so far I can't even get the mx to even attempt to boot from sd, it just ignores it and boots of the internal flash x.x . -- :) SP -------------- next part -------------- An HTML attachment was scrubbed... URL: From slothpuck at gmail.com Thu Aug 25 20:49:23 2011 From: slothpuck at gmail.com (lee jones) Date: Thu, 25 Aug 2011 20:49:23 +0000 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: > > > Just been trying to make a start on this now, but so far I can't even get > the mx to even attempt to boot from sd, it just ignores it and boots of the > internal flash x.x . > > > -- > :) > > Update: I now have the efika mx smartbook booting off sd. It appears that ext2 is needed for boot, and that files such as boot.scr need to go into the root of the 1st partiton. Some examples have this in a directory called "boot" - this dosen't seem to work. No more progress after that though. The files in the 1st partiton are; drwxr-xr-x 3 root root 1.0K Aug 25 17:35 . drwxrwxrwx 27 root root 4.0K Aug 25 17:42 .. -rwxrwxrwx 1 aaaaa users 845K Mar 1 03:26 System.map-2.6.31.14.20-efikamx drwxrwxrwx 2 root root 1.0K Aug 25 17:36 boot -rwxrwxrwx 1 aaaaa users 466 Aug 25 2011 boot.scr -rwxrwxrwx 1 aaaaa users 479 Apr 1 17:11 boot.scr.bak -rwxrwxrwx 1 aaaaa users 394 Apr 1 17:01 boot.script -rwxrwxrwx 1 aaaaa users 65K Mar 1 03:09 config-2.6.31.14.20-efikamx -rwxrwxrwx 1 aaaaa users 6.5M Apr 1 17:12 initrd.img -rwxrwxrwx 1 aaaaa users 6.5M Apr 1 17:12 initrd.img-2.6.31.14.20-efikamx -rwxrwxrwx 1 aaaaa users 281 Apr 1 16:37 kernel-prep -rwxrwxrwx 1 aaaaa users 77 Apr 1 16:40 script-prep -rwxrwxrwx 1 aaaaa users 1.9M Apr 1 17:11 uImage-2.6.31.14.20-efikamx -rwxrwxrwx 1 aaaaa users 1.9M Mar 3 01:37 uImage-2.6.31.14.20-efikamx.bak -rwxrwxrwx 1 aaaaa users 6.5M Apr 1 17:11 uInitrd-2.6.31.14.20-efikamx -rwxrwxrwx 1 aaaaa users 6.5M Mar 3 01:37 uInitrd-2.6.31.14.20-efikamx.bak -rwxrwxrwx 1 aaaaa users 1.9M Apr 1 17:12 vmlinuz -rwxrwxrwx 1 aaaaa users 1.9M Mar 1 03:26 vmlinuz-2.6.31.14.20-efikamx boot.script looks like this setenv ramdisk uInitrd-2.6.31.14.20-efikamx; setenv kernel uImage-2.6.31.14.20-efikamx; setenv bootargs console=tty1 root=/dev/mmcblk0p2 rootwait rw; ${loadcmd} ${ramdiskaddr} ${ramdisk}; if imi ${ramdiskaddr}; then; else setenv bootargs ${bootargs} noinitrd; setenv ramdiskaddr ""; fi; ${loadcmd} ${kerneladdr} ${kernel} if imi ${kerneladdr}; then bootm ${kerneladdr} ${ramdiskaddr} fi; I have two partitions on the SD card I'm using, the first ext2 the second ext3. The second partition contains this ( ftp://ftp.armedslack.org/armedslack/armedslack-devtools/minirootfs/roots/slack-13.1-miniroot_14Jun10.tar.xz) . I understand about the kernel versions being different, though at this stage I'm just aiming for something that begins to even attempt boot! :) . So far no joy though, I get this - booting begins but fails soon after; [2.128927] udev[497]: starting version 163 No init found. Try passing init= bootarg. BusyBox v1.15.3 (Ubuntu 1:1.15-3-1ubuntu5) built in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) _ The system dosen't respond to keyboard input after that point. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pr0f3ss0r1492 at yahoo.com Thu Aug 25 22:21:45 2011 From: pr0f3ss0r1492 at yahoo.com (Ottavio) Date: Thu, 25 Aug 2011 23:21:45 +0100 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: On 25 August 2011 21:49, lee jones wrote: > The second partition contains this > ( ftp://ftp.armedslack.org/armedslack/armedslack-devtools/minirootfs/roots/slack-13.1-miniroot_14Jun10.tar.xz ) Excuse the silly question, did you actually extract the image on the partition or did just copy the archive (I said it was a silly question but I had to ask!). > boot.script looks like this > setenv ramdisk uInitrd-2.6.31.14.20-efikamx; > setenv kernel uImage-2.6.31.14.20-efikamx; > setenv bootargs console=tty1 root=/dev/mmcblk0p2 rootwait rw; How is the second partition recognised on your smartbook (fdisk -l)? Did you change "root=" to point to the right partition? I'd also add ?"rootfs=ext3" . Copy the original boot.script into boot.script.orig, then edit ?boot.script and: cd /boot ./script-prep boot.script boot.scr Then, according to William Steuben's instructions: "If you want the initial first time boot setup to work you need to cd to the root filesystem of the sd card and type touch var/lib/oem-config/run" Do this only if you have a recovery image. I don't want to be responsible for the life of your smartbook. And another thing: have you tried to boot from the installed Ubuntu, mount the Slackware partition and then chroot into it? At least you know if you can run that system with that kernel and those modules. -- Ottavio A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? From slothpuck at gmail.com Fri Aug 26 18:26:22 2011 From: slothpuck at gmail.com (lee jones) Date: Fri, 26 Aug 2011 18:26:22 +0000 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: On Thu, Aug 25, 2011 at 10:21 PM, Ottavio wrote: > On 25 August 2011 21:49, lee jones wrote: > > The second partition contains this > > ( > ftp://ftp.armedslack.org/armedslack/armedslack-devtools/minirootfs/roots/slack-13.1-miniroot_14Jun10.tar.xz) > > Excuse the silly question, did you actually extract the image on the > partition or did just copy the archive (I said it was a silly question > but I had to ask!). > *thinks ... I partitioned the SD card into two partitions and formatted them; for the second partition I downloaded the slack-13.1 miniroot file and extracted its contents onto the second SD partiton. > > > boot.script looks like this > > setenv ramdisk uInitrd-2.6.31.14.20-efikamx; > > setenv kernel uImage-2.6.31.14.20-efikamx; > > setenv bootargs console=tty1 root=/dev/mmcblk0p2 rootwait rw; > > How is the second partition recognised on your smartbook (fdisk -l)? > Did you change "root=" to point to the right partition? > I'd also add "rootfs=ext3" . > root= seems to be ok pointing to the correct partition. fdisk -l shows the sd card as two partitions - /dev/mmcblk0p1 (1st sd partition) and /dev/mmcblk0p2 (2nd sd partition). In my boot.script file it says root=/dev/mmcblk0p2 .I also tried adding in rootfs=ext3 . > > Copy the original boot.script into boot.script.orig, then edit boot.script > and: > > cd /boot > ./script-prep boot.script boot.scr > > I did try that, Intrestingly if I put it all into /boot on the sd card the efika mx won't boot from the SD card at all. I have to put everything in root (of the SD card) to even get it to consider booting! Didn't succeed in booting from SD though, same problem as before. > Then, according to William Steuben's instructions: > "If you want the initial first time boot setup to work you need to cd > to the root filesystem of the sd card and type touch > var/lib/oem-config/run" > Not sure but the slack 13.1 miniroot dosen't seem to have this file. > > Do this only if you have a recovery image. I don't want to be > responsible for the life of your smartbook. > > And another thing: have you tried to boot from the installed Ubuntu, > mount the Slackware partition and then chroot into it? At least you > know if you can run that system with that kernel and those modules. > > That's an intresting idea! Just sticking with the slack 13.1 miniroot on the sd card (second partition) I tried doing sudo chroot on the second partiton (I used df -h to get the directory name where it is mounted in ubuntu) and it seemed to work (though I only tried basic bash-like commands like ls, cp etc). I also tried running pkgtool surprisingly this worked too and I was able to list all the installed packages (In the slack 13.1 miniroot) by choosing the "view" option. ljones -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Fri Aug 26 20:19:21 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 26 Aug 2011 21:19:21 +0100 (BST) Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: > > > ( > > ftp://ftp.armedslack.org/armedslack/armedslack-devtools/minirootfs/roots/slack-13.1-miniroot_14Jun10.tar.xz) > > > > Excuse the silly question, did you actually extract the image on the > > partition or did just copy the archive (I said it was a silly question > > but I had to ask!). > > > > > *thinks ... I partitioned the SD card into two partitions and formatted > them; for the second partition I downloaded the slack-13.1 miniroot file and > extracted its contents onto the second SD partiton. And configured it, as the instructions say, I assume :) From slothpuck at gmail.com Fri Aug 26 21:04:41 2011 From: slothpuck at gmail.com (lee jones) Date: Fri, 26 Aug 2011 21:04:41 +0000 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: Ok, I have an update here as I have gotten a little further. But (wait for it) there's good news and bad news. The good news? I've now gotten further with booting. It appears the efika mx kernel dosen't work with ext3! Going over the top of the second partiton (using ext3) with ext4 meant I got further with booting. The bad news? I'm now as far in as "Loading /usr/share/kbd/keymaps/i386/qwerty/uk.map.gz" . The system all but stops there, the only line it prints after some time is "INIT: Id "s0" respawning too fast: disabled for 5 minutes". I also double-checked the /etc/fstab on the slackware 13.1 mini file system (second partiton of my SD card) it looks fine (I am guessing here); ljones -------------- next part -------------- An HTML attachment was scrubbed... URL: From slothpuck at gmail.com Fri Aug 26 21:09:02 2011 From: slothpuck at gmail.com (lee jones) Date: Fri, 26 Aug 2011 21:09:02 +0000 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: On Fri, Aug 26, 2011 at 9:04 PM, lee jones wrote: > > > I also double-checked the /etc/fstab on the slackware 13.1 mini file system > (second partiton of my SD card) it looks fine (I am guessing here); > > ljones > Sorry, gmail ate my last lines on my message(!). The /etc/fstab reads; /dev/mmcblk0p2 / ext4 errors=remount-ro 0 1 ljones -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Fri Aug 26 21:18:54 2011 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Fri, 26 Aug 2011 23:18:54 +0200 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: <4E580DBE.1010808@gmail.com> On 08/26/2011 11:04 PM, lee jones wrote: > The bad news? I'm now as far in as "Loading > /usr/share/kbd/keymaps/i386/qwerty/uk.map.gz" . The system all but stops > there, the only line it prints after some time is "INIT: Id "s0" respawning > too fast: disabled for 5 minutes". For 99% it means that INIT (/etc/inittab) can't open console on serial port, but the system should be running. Maybe try to play with serial console settings (proper /dev/tty* entry in /etc/inittab, etc) or try to setup network and SSH (on the miniroot) and then try to ssh to the device. -- Pozdrawiam, Best regards, Andrzej Telszewski From slothpuck at gmail.com Fri Aug 26 21:30:13 2011 From: slothpuck at gmail.com (lee jones) Date: Fri, 26 Aug 2011 21:30:13 +0000 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: <4E580DBE.1010808@gmail.com> References: <4E580DBE.1010808@gmail.com> Message-ID: On Fri, Aug 26, 2011 at 9:18 PM, Andrzej Telszewski wrote: > On 08/26/2011 11:04 PM, lee jones wrote: > > The bad news? I'm now as far in as "Loading > > /usr/share/kbd/keymaps/i386/qwerty/uk.map.gz" . The system all but stops > > there, the only line it prints after some time is "INIT: Id "s0" > respawning > > too fast: disabled for 5 minutes". > > For 99% it means that INIT (/etc/inittab) can't open console on serial > port, but the system should be running. Maybe try to play with serial > console settings (proper /dev/tty* entry in /etc/inittab, etc) or try to > setup network and SSH (on the miniroot) and then try to ssh to the device. > > -- > Pozdrawiam, > Best regards, > Andrzej Telszewski > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > Think you're right there ... I commented out the line in /etc/inittab starting with s0:12345 and that put paid to that message :) . ljones -------------- next part -------------- An HTML attachment was scrubbed... URL: From slothpuck at gmail.com Fri Aug 26 21:33:18 2011 From: slothpuck at gmail.com (lee jones) Date: Fri, 26 Aug 2011 21:33:18 +0000 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: On Fri, Aug 26, 2011 at 9:04 PM, lee jones wrote: > > Ok, I have an update here as I have gotten a little further. But (wait for > it) there's good news and bad news. > > The good news? I've now gotten further with booting. It appears the efika > mx kernel dosen't work with ext3! Going over the top of the second partiton > (using ext3) with ext4 meant I got further with booting. > > The bad news? I'm now as far in as "Loading > /usr/share/kbd/keymaps/i386/qwerty/uk.map.gz" . The system all but stops > there, the only line it prints after some time is "INIT: Id "s0" respawning > too fast: disabled for 5 minutes". > > I also double-checked the /etc/fstab on the slackware 13.1 mini file system > (second partiton of my SD card) it looks fine (I am guessing here); > > ljones > Update : The messages about INIT: s0 respawning have gone :) (had to edit inittab) but still got the lock up after the line "/usr/share/kbd/keymaps/i386/qwerty/uk.map.gz". I tried stopping this from loading by doing this; # Load the keyboard map. More maps are in /usr/share/kbd/keymaps. #if [ -x /usr/bin/loadkeys ]; then # /usr/bin/loadkeys uk.map #fi but it now locks up on "starting system message bus: /usr/bin/dbus-uuidgen --ensure ; /usr/bin/daemon --system". Something is causing armedslack to lock up but not sure what! ljones -------------- next part -------------- An HTML attachment was scrubbed... URL: From dowelld at netscape.net Fri Aug 26 23:37:10 2011 From: dowelld at netscape.net (Dave Dowell) Date: Sat, 27 Aug 2011 00:37:10 +0100 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: <4E580DBE.1010808@gmail.com> References: <4E580DBE.1010808@gmail.com> Message-ID: <4E582E26.5060605@netscape.net> Have you checked that a getty is being spawned against a tty device in /etc/inittab? You can also comment out the getty that is being spawned against ttyS0 there which is the cause of that "INIT: Id s0 respawing to fast.... " message. Thanks Dave On 26/08/2011 22:18, Andrzej Telszewski wrote: > On 08/26/2011 11:04 PM, lee jones wrote: >> The bad news? I'm now as far in as "Loading >> /usr/share/kbd/keymaps/i386/qwerty/uk.map.gz" . The system all but stops >> there, the only line it prints after some time is "INIT: Id "s0" respawning >> too fast: disabled for 5 minutes". > For 99% it means that INIT (/etc/inittab) can't open console on serial > port, but the system should be running. Maybe try to play with serial > console settings (proper /dev/tty* entry in /etc/inittab, etc) or try to > setup network and SSH (on the miniroot) and then try to ssh to the device. > From pr0f3ss0r1492 at yahoo.com Sat Aug 27 00:04:43 2011 From: pr0f3ss0r1492 at yahoo.com (Ottavio) Date: Sat, 27 Aug 2011 01:04:43 +0100 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: On 26 August 2011 22:09, lee jones wrote: > The /etc/fstab reads; > > /dev/mmcblk0p2?? /? ext4 errors=remount-ro 0? 1 > Shouldn't that be: /dev/mmcblk0p2 / ext4 defaults 1 1 /dev/mmcblk0p1 /boot ext2 defaults 0 0 ? -- Ottavio A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? From slothpuck at gmail.com Sat Aug 27 10:49:38 2011 From: slothpuck at gmail.com (lee jones) Date: Sat, 27 Aug 2011 10:49:38 +0000 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: On Sat, Aug 27, 2011 at 12:04 AM, Ottavio wrote: > On 26 August 2011 22:09, lee jones wrote: > > The /etc/fstab reads; > > > > /dev/mmcblk0p2 / ext4 errors=remount-ro 0 1 > > > > Shouldn't that be: > > /dev/mmcblk0p2 / ext4 defaults 1 1 > /dev/mmcblk0p1 /boot ext2 defaults 0 0 > > ? > > -- > Ottavio > > > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > Good point it probably should be, oops! -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From slothpuck at gmail.com Sat Aug 27 12:52:51 2011 From: slothpuck at gmail.com (lee jones) Date: Sat, 27 Aug 2011 12:52:51 +0000 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: Ok .... I decided to note down as a list of instructions what I've tried to do, here goes. Note that it still does not boot! Attempt at getting Armedslack 13.1 onto Efika MX Smartbook Armedslack Version used = slack-13.1-miniroot_14Jun10.tar.xz Efika mx modules/kernel version = 2.6.31.14.20-efikamx 0. Notes * This dosen't work yet. Although the earlier boot error messages I had have largely gone - so far the MX smartbook locks up/hangs, it dosen't complete boot. * I changed the 1st partiton from EXT2 to EXT3 as I found that while I was doing all of this it (partiton 1) would get corrupted x.x . * The efika mx kernel used here *at boot-up* dosen't understand EXT3! * Once booting has started EXT3 seems ok but them dosen't understand EXT2... * I ended up using EXT3 for partiton 1 and EXT4 for partition 2. here's what I've tried; 1. Grab an SD card and partition it into two partitions Partition 1 - 100MB EXT3 Partition 2 - Rest of card EXT4 2. Format both partitions on a linux system. Use mkfs.ext3 for the ext3 partiton, and use mkfs.ext4 for the ext4 partition. 3. Download the slack 13.1 miniroot file from here; ftp://ftp.armedslack.org/armedslack/armedslack-devtools/minirootfs/roots/slack-13.1-miniroot_14Jun10.tar.xz 4. Download both the boot.tar.xz and root.tar.xz from here; http://steubentech.com/~talon/Efika-MX/mavericksd/ 5. Extract the files from the boot.tar.xz file onto the first partiton. Note that in the .tar.xz file the files are in a directory called "boot". These will need to be moved to the root of the 1st partition of the SD card. Also get rid of the old boot directory and lost+found. 6. Extract the files from the slack distro onto the second partition of the SD card, e.g. tar -xf slack-13.1-miniroot_14Jul10.tar.xz -C /where/you/mounted/the/second/partition 7. Extract the /lib/modules directory and files from the root.tar.xz file. Copy them onto the second SD card partition into /lib/modules. 8. Edit on the second SD partition etc/inittab and comment out the line starting "s0:1234", put a # in front to comment out. 9. Edit on the second SD partition etc/fstab and add this; /dev/mmcblk0p2 / ext4 defaults 1 1 /dev/mmcblk0p1 /boot ext3 defaults 0 0 10. Boot up the efika MX smartbook with no SD card in it (so it goes into its ubuntu distro), once it has loaded up pop in the second card. 11. On the first SD card partition, change the boot.script file to read as follows (it should be in the root of the 1st SD card partition, you'll need sudo also); ** setenv ramdisk uInitrd-2.6.31.14.20-efikamx; setenv kernel uImage-2.6.31.14.20-efikamx; setenv bootargs console=tty1 root=/dev/mmcblk0p2 rootwait ro; ${loadcmd} ${ramdiskaddr} ${ramdisk}; if imi ${ramdiskaddr}; then; else setenv bootargs ${bootargs} noinitrd; setenv ramdiskaddr ""; fi; ${loadcmd} ${kerneladdr} ${kernel} if imi ${kerneladdr}; then bootm ${kerneladdr} ${ramdiskaddr} fi; ** 11. From the first partition of the SD card run the following command; sudo ./script-prep boot.script boot.scr 12. Shut down the MX smartbook, leave the SD card in its slot and power back on. ljones -------------- next part -------------- An HTML attachment was scrubbed... URL: From slothpuck at gmail.com Sat Aug 27 12:54:15 2011 From: slothpuck at gmail.com (lee jones) Date: Sat, 27 Aug 2011 12:54:15 +0000 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: The contents of /var/log/messages if its useful :) ! Aug 27 12:40:04 slackware syslogd 1.5.0: restart. Aug 27 12:40:04 slackware klogd: klogd 1.5.0, log source = /proc/kmsg started. Aug 27 12:40:04 slackware klogd: [ 0.000000] Initializing cgroup subsys cpuset Aug 27 12:40:04 slackware klogd: [ 0.000000] Linux version 2.6.31.14.20-efikamx (root at buildbot) (gcc version 4.5.1 (Ubuntu/Linaro 4.5.1-7ubuntu2) ) #2 PREEMPT Mon Feb 28 21:18:36 CST 2011 Aug 27 12:40:04 slackware klogd: [ 0.000000] Kernel command line: console=tty1 root=/dev/mmcblk0p2 rootwait ro Aug 27 12:40:04 slackware klogd: [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Aug 27 12:40:04 slackware klogd: [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Aug 27 12:40:04 slackware klogd: [ 0.000000] Memory: 416MB = 416MB total Aug 27 12:40:04 slackware klogd: [ 0.000000] Memory: 410884KB available (3564K code, 589K data, 136K init, 0K highmem) Aug 27 12:40:04 slackware klogd: [ 0.000000] SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 Aug 27 12:40:04 slackware klogd: [ 0.000000] Hierarchical RCU implementation. Aug 27 12:40:04 slackware klogd: [ 0.000000] NR_IRQS:368 Aug 27 12:40:04 slackware klogd: [ 0.000000] MXC IRQ initialized Aug 27 12:40:04 slackware klogd: [ 0.000000] console [tty1] enabled Aug 27 12:40:04 slackware klogd: [ 0.000000] Calibrating delay loop... 799.53 BogoMIPS (lpj=3997696) Aug 27 12:40:04 slackware klogd: [ 0.000000] Initializing cgroup subsys ns Aug 27 12:40:04 slackware klogd: [ 0.000000] Initializing cgroup subsys cpuacct Aug 27 12:40:04 slackware klogd: [ 0.000000] Initializing cgroup subsys freezer Aug 27 12:40:04 slackware klogd: [ 0.000000] Initializing cgroup subsys net_cls Aug 27 12:40:04 slackware klogd: [ 0.000000] CPU: Testing write buffer coherency: ok Aug 27 12:40:04 slackware klogd: [ 0.000000] devtmpfs: initialized Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: core version 0.5 Aug 27 12:40:04 slackware klogd: [ 0.000000] NET: Registered protocol family 16 Aug 27 12:40:04 slackware klogd: [ 0.000000] i.MX IRAM pool: 128 KB at 0x9a840000 Aug 27 12:40:04 slackware klogd: [ 0.000000] IRAM READY Aug 27 12:40:04 slackware klogd: [ 0.000000] CPU is i.MX51 Revision 3.0 Aug 27 12:40:04 slackware klogd: [ 0.000000] MXC GPIO hardware Aug 27 12:40:04 slackware klogd: [ 0.000000] Efika MX: mmc0 configured as MicroSD Aug 27 12:40:04 slackware klogd: [ 0.000000] Efika MX: mmc1 configured as external SDHC Aug 27 12:40:04 slackware klogd: [ 0.000000] Efika MX: Smartbook Revision 2.0 Aug 27 12:40:04 slackware klogd: [ 0.000000] Efika MX: Memory type Hynix DDR2 Aug 27 12:40:04 slackware klogd: [ 0.000000] Using SDMA I.API Aug 27 12:40:04 slackware klogd: [ 0.000000] MXC DMA API initialized Aug 27 12:40:04 slackware klogd: [ 0.000000] SCSI subsystem initialized Aug 27 12:40:04 slackware klogd: [ 0.000000] CSPI: mxc_spi-0 probed Aug 27 12:40:04 slackware klogd: [ 0.000000] IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7) Aug 27 12:40:04 slackware klogd: [ 0.000000] NET: Registered protocol family 8 Aug 27 12:40:04 slackware klogd: [ 0.000000] NET: Registered protocol family 20 Aug 27 12:40:04 slackware klogd: [ 0.000000] mc13892 Rev 2.0 FinVer 2 detected Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: SW1: 600 <--> 1375 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: SW2: 900 <--> 1850 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: SW3: 1100 <--> 1850 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: SW4: 1100 <--> 1850 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: SWBST: 0 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: VIOHI: 0 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: VPLL: 1050 <--> 1800 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: VDIG: 1650 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: VSD: 1800 <--> 3150 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: VUSB2: 2400 <--> 2775 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: VVIDEO: 2775 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: VAUDIO: 2300 <--> 3000 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: VCAM: 2500 <--> 3000 mV fast normal Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: VGEN1: 1200 <--> 3150 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: VGEN2: 1200 <--> 3150 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: VGEN3: 1800 <--> 2900 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: VUSB: 0 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: GPO1: 0 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: GPO2: 0 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: GPO3: 0 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] regulator: GPO4: 0 mV Aug 27 12:40:04 slackware klogd: [ 0.000000] Device spi1.0 probed Aug 27 12:40:04 slackware klogd: [ 1.067933] NET: Registered protocol family 2 Aug 27 12:40:04 slackware klogd: [ 1.068321] IP route cache hash table entries: 4096 (order: 2, 16384 bytes) Aug 27 12:40:04 slackware klogd: [ 1.069353] TCP established hash table entries: 16384 (order: 5, 131072 bytes) Aug 27 12:40:04 slackware klogd: [ 1.069657] TCP bind hash table entries: 16384 (order: 4, 65536 bytes) Aug 27 12:40:04 slackware klogd: [ 1.069836] TCP: Hash tables configured (established 16384 bind 16384) Aug 27 12:40:04 slackware klogd: [ 1.069867] TCP reno registered Aug 27 12:40:04 slackware klogd: [ 1.070091] NET: Registered protocol family 1 Aug 27 12:40:04 slackware klogd: [ 1.070330] Unpacking initramfs... Aug 27 12:40:04 slackware klogd: [ 1.476889] Freeing initrd memory: 6596K Aug 27 12:40:04 slackware klogd: [ 1.477916] LPMode driver module loaded Aug 27 12:40:04 slackware klogd: [ 1.477954] Static Power Management for Freescale i.MX51 Aug 27 12:40:04 slackware klogd: [ 1.478289] PM driver module loaded Aug 27 12:40:04 slackware klogd: [ 1.478583] sdram autogating driver module loaded Aug 27 12:40:04 slackware klogd: [ 1.478963] Bus freq driver module loaded Aug 27 12:40:04 slackware klogd: [ 1.479031] mxc_dvfs_core_probe Aug 27 12:40:04 slackware klogd: [ 1.479348] DVFS driver module loaded Aug 27 12:40:04 slackware klogd: [ 1.479386] i.MXC CPU frequency driver Aug 27 12:40:04 slackware klogd: [ 1.480023] DVFS PER driver module loaded Aug 27 12:40:04 slackware klogd: [ 1.481823] squashfs: version 4.0 (2009/01/31) Phillip Lougher Aug 27 12:40:04 slackware klogd: [ 1.481896] msgmni has been set to 815 Aug 27 12:40:04 slackware klogd: [ 1.483541] alg: No test for stdrng (krng) Aug 27 12:40:04 slackware klogd: [ 1.483912] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) Aug 27 12:40:04 slackware klogd: [ 1.483963] io scheduler noop registered (default) Aug 27 12:40:04 slackware klogd: [ 1.484006] io scheduler cfq registered Aug 27 12:40:04 slackware klogd: [ 1.536711] mxc_ipu mxc_ipu: Channel already disabled 9 Aug 27 12:40:04 slackware klogd: [ 1.536722] mxc_ipu mxc_ipu: Channel already uninitialized 9 Aug 27 12:40:04 slackware klogd: [ 1.547594] IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7) Aug 27 12:40:04 slackware klogd: [ 1.578714] Serial: MXC Internal UART driver Aug 27 12:40:04 slackware klogd: [ 1.579052] mxcintuart.0: ttymxc0 at MMIO 0x73fbc000 (irq = 31) is a Freescale i.MX Aug 27 12:40:04 slackware klogd: [ 1.584451] loop: module loaded Aug 27 12:40:04 slackware klogd: [ 1.586394] mice: PS/2 mouse device common for all mice Aug 27 12:40:04 slackware klogd: [ 1.586635] mc13892 rtc probe start Aug 27 12:40:04 slackware klogd: [ 1.588038] pmic_rtc pmic_rtc.1: rtc core: registered pmic_rtc as rtc0 Aug 27 12:40:04 slackware klogd: [ 1.588202] mc13892 rtc probe succeed Aug 27 12:40:04 slackware klogd: [ 1.588484] i2c /dev entries driver Aug 27 12:40:04 slackware klogd: [ 1.589263] Linux video capture interface: v2.00 Aug 27 12:40:04 slackware klogd: [ 1.589927] mxc_v4l2_output mxc_v4l2_output.0: Registered device video0 Aug 27 12:40:04 slackware klogd: [ 1.590306] MXC WatchDog Driver 2.0 Aug 27 12:40:04 slackware klogd: [ 1.590961] MXC Watchdog # 0 Timer: initial timeout 60 sec Aug 27 12:40:04 slackware klogd: [ 1.591388] cpuidle: using governor ladder Aug 27 12:40:04 slackware klogd: [ 1.591495] cpuidle: using governor menu Aug 27 12:40:04 slackware klogd: [ 1.594333] PMIC Character device: successfully loaded Aug 27 12:40:04 slackware klogd: [ 1.597366] VPU initialized Aug 27 12:40:04 slackware klogd: [ 1.601039] Registered led device: led:capslock Aug 27 12:40:04 slackware klogd: [ 1.603912] Registered led device: led:alarm Aug 27 12:40:04 slackware klogd: [ 1.607623] Advanced Linux Sound Architecture Driver Version 1.0.20. Aug 27 12:40:04 slackware klogd: [ 1.615441] ALSA device list: Aug 27 12:40:04 slackware klogd: [ 1.618147] No soundcards found. Aug 27 12:40:04 slackware klogd: [ 1.621789] TCP cubic registered Aug 27 12:40:04 slackware klogd: [ 1.624196] NET: Registered protocol family 17 Aug 27 12:40:04 slackware klogd: [ 1.626686] ThumbEE CPU extension supported. Aug 27 12:40:04 slackware klogd: [ 1.632056] input: Efika MX Input as /devices/virtual/input/input0 Aug 27 12:40:04 slackware klogd: [ 1.635272] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2 Aug 27 12:40:04 slackware klogd: [ 1.665055] pmic_rtc pmic_rtc.1: setting system clock to 2011-08-27 12:39:51 UTC (1314448791) Aug 27 12:40:04 slackware klogd: [ 2.017637] Freeing init memory: 136K Aug 27 12:40:04 slackware klogd: [ 2.128719] udev[497]: starting version 163 Aug 27 12:40:04 slackware klogd: [ 3.105961] pata_fsl pata_fsl: rchan=29 wchan=28 Aug 27 12:40:04 slackware klogd: [ 3.106298] scsi0 : pata_fsl Aug 27 12:40:04 slackware klogd: [ 3.108489] ata1: PATA max UDMA/44 irq 70 Aug 27 12:40:04 slackware klogd: [ 3.288690] ata1.00: CFA: Flash Module, Ver2.M11, max UDMA/100 Aug 27 12:40:04 slackware klogd: [ 3.288842] ata1.00: 30146256 sectors, multi 1: LBA Aug 27 12:40:04 slackware klogd: [ 3.331825] ata1.00: configured for UDMA/44 Aug 27 12:40:04 slackware klogd: [ 3.332319] scsi 0:0:0:0: Direct-Access ATA Flash Module Ver2 PQ: 0 ANSI: 5 Aug 27 12:40:04 slackware klogd: [ 3.341668] sd 0:0:0:0: Attached scsi generic sg0 type 0 Aug 27 12:40:04 slackware klogd: [ 3.342506] sd 0:0:0:0: [sda] 30146256 512-byte logical blocks: (15.4 GB/14.3 GiB) Aug 27 12:40:04 slackware klogd: [ 3.342938] sd 0:0:0:0: [sda] Write Protect is off Aug 27 12:40:04 slackware klogd: [ 3.343184] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Aug 27 12:40:04 slackware klogd: [ 3.344130] sda: sda1 sda2 Aug 27 12:40:04 slackware klogd: [ 3.356149] sd 0:0:0:0: [sda] Attached SCSI disk Aug 27 12:40:04 slackware klogd: [ 3.483131] mxsdhci: MXC Secure Digital Host Controller Interface driver Aug 27 12:40:04 slackware klogd: [ 3.483408] mxsdhci: MXC SDHCI Controller Driver. Aug 27 12:40:04 slackware klogd: [ 3.486526] mmc0: SDHCI detect irq 187 irq 1 INTERNAL DMA Aug 27 12:40:04 slackware klogd: [ 3.486717] mxsdhci: MXC SDHCI Controller Driver. Aug 27 12:40:04 slackware klogd: [ 3.489867] mmc1: SDHCI detect irq 136 irq 2 INTERNAL DMA Aug 27 12:40:04 slackware klogd: [ 3.677256] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel at redhat.com Aug 27 12:40:04 slackware klogd: [ 4.331136] mmc1: new SD card at address f50f Aug 27 12:40:04 slackware klogd: [ 4.339225] mmcblk0: mmc1:f50f SD01G 982 MiB Aug 27 12:40:04 slackware klogd: [ 4.339625] mmcblk0: p1 p2 Aug 27 12:40:04 slackware klogd: [ 4.566126] EXT4-fs (mmcblk0p2): barriers enabled Aug 27 12:40:04 slackware klogd: [ 4.567140] kjournald2 starting: pid 630, dev mmcblk0p2:8, commit interval 5 seconds Aug 27 12:40:04 slackware klogd: [ 4.567437] EXT4-fs (mmcblk0p2): delayed allocation enabled Aug 27 12:40:04 slackware klogd: [ 4.567618] EXT4-fs: file extents enabled Aug 27 12:40:04 slackware klogd: [ 4.568000] EXT4-fs: mballoc enabled Aug 27 12:40:04 slackware klogd: [ 4.568162] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode Aug 27 12:40:04 slackware klogd: [ 5.602717] udev: starting version 153 Aug 27 12:40:04 slackware klogd: [ 5.968147] usbcore: registered new interface driver usbfs Aug 27 12:40:04 slackware klogd: [ 5.971490] usbcore: registered new interface driver hub Aug 27 12:40:04 slackware klogd: [ 6.036757] sgtl5000-i2c 1-000a: SGTL5000 revision 17 Aug 27 12:40:04 slackware klogd: [ 6.061298] usbcore: registered new device driver usb Aug 27 12:40:04 slackware klogd: [ 6.105326] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Aug 27 12:40:04 slackware klogd: [ 6.217667] fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller Aug 27 12:40:04 slackware klogd: [ 6.221323] fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1 Aug 27 12:40:04 slackware klogd: [ 6.251088] fsl-ehci fsl-ehci.0: irq 18, io base 0x73f80000 Aug 27 12:40:04 slackware klogd: [ 6.267671] fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00 Aug 27 12:40:04 slackware klogd: [ 6.271390] usb usb1: configuration #1 chosen from 1 choice Aug 27 12:40:04 slackware klogd: [ 6.274538] hub 1-0:1.0: USB hub found Aug 27 12:40:04 slackware klogd: [ 6.277648] hub 1-0:1.0: 1 port detected Aug 27 12:40:04 slackware klogd: [ 6.497840] fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller Aug 27 12:40:04 slackware klogd: [ 6.501036] fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2 Aug 27 12:40:04 slackware klogd: [ 6.527681] fsl-ehci fsl-ehci.1: irq 14, io base 0x73f80200 Aug 27 12:40:04 slackware klogd: [ 6.547653] fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00 Aug 27 12:40:04 slackware klogd: [ 6.551201] usb usb2: configuration #1 chosen from 1 choice Aug 27 12:40:04 slackware klogd: [ 6.554256] hub 2-0:1.0: USB hub found Aug 27 12:40:04 slackware klogd: [ 6.558179] hub 2-0:1.0: 1 port detected Aug 27 12:40:04 slackware klogd: [ 6.777575] usb 2-1: new high speed USB device using fsl-ehci and address 2 Aug 27 12:40:04 slackware klogd: [ 6.780581] fsl-ehci fsl-ehci.2: Freescale On-Chip EHCI Host Controller Aug 27 12:40:04 slackware klogd: [ 6.783451] fsl-ehci fsl-ehci.2: new USB bus registered, assigned bus number 3 Aug 27 12:40:04 slackware klogd: [ 6.807579] fsl-ehci fsl-ehci.2: irq 16, io base 0x73f80400 Aug 27 12:40:04 slackware klogd: [ 6.917570] fsl-ehci fsl-ehci.2: USB 2.0 started, EHCI 1.00 Aug 27 12:40:04 slackware klogd: [ 6.920978] usb usb3: configuration #1 chosen from 1 choice Aug 27 12:40:04 slackware klogd: [ 6.923971] hub 3-0:1.0: USB hub found Aug 27 12:40:04 slackware klogd: [ 6.926769] hub 3-0:1.0: 1 port detected Aug 27 12:40:04 slackware klogd: [ 6.930284] usb 2-1: configuration #1 chosen from 1 choice Aug 27 12:40:04 slackware klogd: [ 6.933450] hub 2-1:1.0: USB hub found Aug 27 12:40:04 slackware klogd: [ 6.936294] hub 2-1:1.0: 4 ports detected Aug 27 12:40:04 slackware klogd: [ 7.157616] usb 3-1: new high speed USB device using fsl-ehci and address 2 Aug 27 12:40:04 slackware klogd: [ 7.308863] usb 3-1: configuration #1 chosen from 1 choice Aug 27 12:40:04 slackware klogd: [ 7.320428] hub 3-1:1.0: USB hub found Aug 27 12:40:04 slackware klogd: [ 7.323756] hub 3-1:1.0: 3 ports detected Aug 27 12:40:04 slackware klogd: [ 7.407747] usb 2-1.1: new low speed USB device using fsl-ehci and address 3 Aug 27 12:40:04 slackware klogd: [ 7.528805] usb 2-1.1: configuration #1 chosen from 1 choice Aug 27 12:40:04 slackware klogd: [ 7.627894] usb 2-1.4: new low speed USB device using fsl-ehci and address 4 Aug 27 12:40:04 slackware klogd: [ 7.741698] usb 2-1.4: configuration #1 chosen from 1 choice Aug 27 12:40:04 slackware klogd: [ 7.774611] input: USB Keyboard as /devices/platform/fsl-ehci.1/usb2/2-1/2-1.1/2-1.1:1.0/input/input1 Aug 27 12:40:04 slackware klogd: [ 7.799839] generic-usb 0003:04D9:FF09.0001: input: USB HID v1.10 Keyboard [USB Keyboard] on usb-fsl-ehci.1-1.1/input0 Aug 27 12:40:04 slackware klogd: [ 7.837856] usb 3-1.2: new high speed USB device using fsl-ehci and address 3 Aug 27 12:40:04 slackware klogd: [ 7.870213] input: USB Keyboard as /devices/platform/fsl-ehci.1/usb2/2-1/2-1.1/2-1.1:1.1/input/input2 Aug 27 12:40:04 slackware klogd: [ 7.877402] generic-usb 0003:04D9:FF09.0002: input: USB HID v1.10 Mouse [USB Keyboard] on usb-fsl-ehci.1-1.1/input1 Aug 27 12:40:04 slackware klogd: [ 7.927924] input: USB Mouse as /devices/platform/fsl-ehci.1/usb2/2-1/2-1.4/2-1.4:1.0/input/input3 Aug 27 12:40:04 slackware klogd: [ 7.932546] generic-usb 0003:15D9:0A33.0003: input: USB HID v1.10 Mouse [USB Mouse] on usb-fsl-ehci.1-1.4/input0 Aug 27 12:40:04 slackware klogd: [ 7.969507] usbcore: registered new interface driver usbhid Aug 27 12:40:04 slackware klogd: [ 7.973652] usb 3-1.2: configuration #1 chosen from 1 choice Aug 27 12:40:04 slackware klogd: [ 7.977313] usbhid: v2.6:USB HID core driver Aug 27 12:40:04 slackware klogd: [ 8.009391] usbcore: registered new interface driver usbmouse Aug 27 12:40:04 slackware klogd: [ 8.013119] usbmouse: v1.6:USB HID Boot Protocol mouse driver Aug 27 12:40:04 slackware klogd: [ 8.097352] usbcore: registered new interface driver usbkbd Aug 27 12:40:04 slackware klogd: [ 8.101105] usbkbd: :USB HID Boot Protocol keyboard driver Aug 27 12:40:04 slackware klogd: [ 8.171465] uvcvideo: Found UVC 1.00 device Pegatron (04f2:b1b0) Aug 27 12:40:04 slackware klogd: [ 8.178801] input: Pegatron as /devices/platform/fsl-ehci.2/usb3/3-1/3-1.2/3-1.2:1.0/input/input4 Aug 27 12:40:04 slackware klogd: [ 8.184645] usbcore: registered new interface driver uvcvideo Aug 27 12:40:04 slackware klogd: [ 8.188558] USB Video Class driver (v0.1.0) Aug 27 12:40:04 slackware klogd: [ 8.427853] EXT4-fs (mmcblk0p2): internal journal on mmcblk0p2:8 Aug 27 12:40:04 slackware klogd: [ 12.913472] kjournald starting. Commit interval 15 seconds Aug 27 12:40:04 slackware klogd: [ 13.098121] EXT3 FS on mmcblk0p1, internal journal Aug 27 12:40:04 slackware klogd: [ 13.101751] EXT3-fs: mounted filesystem with writeback data mode. Aug 27 12:40:04 slackware logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Aug 27 12:40:04 slackware logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo Aug 27 12:40:06 slackware rpc.statd[965]: Version 1.2.2 starting Aug 27 12:40:06 slackware sm-notify[966]: Version 1.2.2 starting Aug 27 12:40:06 slackware klogd: [ 16.641775] NET: Registered protocol family 10 Aug 27 12:40:06 slackware klogd: [ 16.643226] lo: Disabled Privacy Extensions Aug 27 12:40:06 slackware sshd[978]: Server listening on 0.0.0.0 port 22. Aug 27 12:40:06 slackware sshd[978]: Server listening on :: port 22. ljones -------------- next part -------------- An HTML attachment was scrubbed... URL: From slothpuck at gmail.com Sat Aug 27 12:56:39 2011 From: slothpuck at gmail.com (lee jones) Date: Sat, 27 Aug 2011 12:56:39 +0000 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: Also contents of /var/log/dmesg; [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Linux version 2.6.31.14.20-efikamx (root at buildbot) (gcc version 4.5.1 (Ubuntu/Linaro 4.5.1-7ubuntu2) ) #2 PREEMPT Mon Feb 28 21:18:36 CST 2011 [ 0.000000] CPU: ARMv7 Processor [412fc085] revision 5 (ARMv7), cr=10c53c7f [ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache [ 0.000000] Machine: Genesi Efika MX (Smartbook) [ 0.000000] Memory policy: ECC disabled, Data cache writeback [ 0.000000] On node 0 totalpages: 106496 [ 0.000000] free_area_init_node: node 0, pgdat 80419a14, node_mem_map 8047e000 [ 0.000000] DMA zone: 192 pages used for memmap [ 0.000000] DMA zone: 0 pages reserved [ 0.000000] DMA zone: 24384 pages, LIFO batch:3 [ 0.000000] Normal zone: 640 pages used for memmap [ 0.000000] Normal zone: 81280 pages, LIFO batch:15 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 105664 [ 0.000000] Kernel command line: console=tty1 root=/dev/mmcblk0p2 rootwait ro [ 0.000000] PID hash table entries: 2048 (order: 11, 8192 bytes) [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] Memory: 416MB = 416MB total [ 0.000000] Memory: 410884KB available (3564K code, 589K data, 136K init, 0K highmem) [ 0.000000] SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] NR_IRQS:368 [ 0.000000] MXC IRQ initialized [ 0.000000] Console: colour dummy device 80x30 [ 0.000000] console [tty1] enabled [ 0.000000] Calibrating delay loop... 799.53 BogoMIPS (lpj=3997696) [ 0.000000] Mount-cache hash table entries: 512 [ 0.000000] Initializing cgroup subsys ns [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Initializing cgroup subsys freezer [ 0.000000] Initializing cgroup subsys net_cls [ 0.000000] CPU: Testing write buffer coherency: ok [ 0.000000] devtmpfs: initialized [ 0.000000] regulator: core version 0.5 [ 0.000000] NET: Registered protocol family 16 [ 0.000000] i.MX IRAM pool: 128 KB at 0x9a840000 [ 0.000000] IRAM READY [ 0.000000] CPU is i.MX51 Revision 3.0 [ 0.000000] MXC GPIO hardware [ 0.000000] Efika MX: mmc0 configured as MicroSD [ 0.000000] Efika MX: mmc1 configured as external SDHC [ 0.000000] Efika MX: Smartbook Revision 2.0 [ 0.000000] Efika MX: Memory type Hynix DDR2 [ 0.000000] Using SDMA I.API [ 0.000000] MXC DMA API initialized [ 0.000000] bio: create slab at 0 [ 0.000000] SCSI subsystem initialized [ 0.000000] CSPI: mxc_spi-0 probed [ 0.000000] IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7) [ 0.000000] NET: Registered protocol family 8 [ 0.000000] NET: Registered protocol family 20 [ 0.000000] mc13892 Rev 2.0 FinVer 2 detected [ 0.000000] Initializing regulators for Efika MX [ 0.000000] regulator: SW1: 600 <--> 1375 mV [ 0.000000] regulator: SW2: 900 <--> 1850 mV [ 0.000000] regulator: SW3: 1100 <--> 1850 mV [ 0.000000] regulator: SW4: 1100 <--> 1850 mV [ 0.000000] regulator: SWBST: 0 mV [ 0.000000] regulator: VIOHI: 0 mV [ 0.000000] regulator: VPLL: 1050 <--> 1800 mV [ 0.000000] regulator: VDIG: 1650 mV [ 0.000000] regulator: VSD: 1800 <--> 3150 mV [ 0.000000] regulator: VUSB2: 2400 <--> 2775 mV [ 0.000000] regulator: VVIDEO: 2775 mV [ 0.000000] regulator: VAUDIO: 2300 <--> 3000 mV [ 0.000000] regulator: VCAM: 2500 <--> 3000 mV fast normal [ 0.000000] regulator: VGEN1: 1200 <--> 3150 mV [ 0.000000] regulator: VGEN2: 1200 <--> 3150 mV [ 0.000000] regulator: VGEN3: 1800 <--> 2900 mV [ 0.000000] regulator: VUSB: 0 mV [ 0.000000] regulator: GPO1: 0 mV [ 0.000000] regulator: GPO2: 0 mV [ 0.000000] regulator: GPO3: 0 mV [ 0.000000] regulator: GPO4: 0 mV [ 0.000000] Device spi1.0 probed [ 1.067574] Switched to high resolution mode on CPU 0 [ 1.067933] NET: Registered protocol family 2 [ 1.068321] IP route cache hash table entries: 4096 (order: 2, 16384 bytes) [ 1.069353] TCP established hash table entries: 16384 (order: 5, 131072 bytes) [ 1.069657] TCP bind hash table entries: 16384 (order: 4, 65536 bytes) [ 1.069836] TCP: Hash tables configured (established 16384 bind 16384) [ 1.069867] TCP reno registered [ 1.070091] NET: Registered protocol family 1 [ 1.070330] Unpacking initramfs... [ 1.476889] Freeing initrd memory: 6596K [ 1.477916] LPMode driver module loaded [ 1.477954] Static Power Management for Freescale i.MX51 [ 1.478289] PM driver module loaded [ 1.478583] sdram autogating driver module loaded [ 1.478963] Bus freq driver module loaded [ 1.479031] mxc_dvfs_core_probe [ 1.479348] DVFS driver module loaded [ 1.479386] i.MXC CPU frequency driver [ 1.480023] DVFS PER driver module loaded [ 1.481823] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 1.481896] msgmni has been set to 815 [ 1.483541] alg: No test for stdrng (krng) [ 1.483912] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) [ 1.483963] io scheduler noop registered (default) [ 1.484006] io scheduler cfq registered [ 1.500484] Console: switching to colour frame buffer device 30x20 [ 1.518939] EDID Dump: [ 1.519591] 00ffffffffffff0006afd220000000000112010380160d780a2b699757559629 [ 1.521701] 214f5400000001010101010101010101010101010101b0130040415819201888 [ 1.523897] 3100df7d000000180000000f0000000000000000000000000020000000fe0041 [ 1.526177] 554f0a202020202020202020000000fe004231303141573032205630200a00c7 [ 1.528602] resolution: r(1024, 600), v(1024, 600) o(0, 0) [ 1.530722] bpp=0, hw(0, 0), pclk=19841 [ 1.532189] margin(160, 24, 21, 3) [ 1.533657] hv(136, 1), sync=0, vmode=0 [ 1.535163] mtl017: Probe LCD Panel: AUO B101AW02 V0 [ 1.536711] mxc_ipu mxc_ipu: Channel already disabled 9 [ 1.536722] mxc_ipu mxc_ipu: Channel already uninitialized 9 [ 1.547594] IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7) [ 1.578714] Serial: MXC Internal UART driver [ 1.579052] mxcintuart.0: ttymxc0 at MMIO 0x73fbc000 (irq = 31) is a Freescale i.MX [ 1.584451] loop: module loaded [ 1.586394] mice: PS/2 mouse device common for all mice [ 1.586635] mc13892 rtc probe start [ 1.588038] pmic_rtc pmic_rtc.1: rtc core: registered pmic_rtc as rtc0 [ 1.588202] mc13892 rtc probe succeed [ 1.588484] i2c /dev entries driver [ 1.589263] Linux video capture interface: v2.00 [ 1.589927] mxc_v4l2_output mxc_v4l2_output.0: Registered device video0 [ 1.590306] MXC WatchDog Driver 2.0 [ 1.590515] clk: Unable to get requested clock: wdog_clk [ 1.590961] MXC Watchdog # 0 Timer: initial timeout 60 sec [ 1.591388] cpuidle: using governor ladder [ 1.591495] cpuidle: using governor menu [ 1.594333] PMIC Character device: successfully loaded [ 1.597366] VPU initialized [ 1.601039] Registered led device: led:capslock [ 1.603912] Registered led device: led:alarm [ 1.607623] Advanced Linux Sound Architecture Driver Version 1.0.20. [ 1.615441] ALSA device list: [ 1.618147] No soundcards found. [ 1.621789] TCP cubic registered [ 1.624196] NET: Registered protocol family 17 [ 1.626686] ThumbEE CPU extension supported. [ 1.629343] mtl017 1-003a: Initializing MTL017 LVDS Controller [ 1.632056] input: Efika MX Input as /devices/virtual/input/input0 [ 1.635272] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2 [ 1.639473] regulator_init_complete: incomplete constraints, leaving GPO4 on [ 1.642193] regulator_init_complete: incomplete constraints, leaving GPO3 on [ 1.644774] regulator_init_complete: incomplete constraints, leaving GPO2 on [ 1.647334] regulator_init_complete: incomplete constraints, leaving GPO1 on [ 1.649953] regulator_init_complete: incomplete constraints, leaving VGEN1 on [ 1.652501] regulator_init_complete: incomplete constraints, leaving VCAM on [ 1.654999] regulator_init_complete: incomplete constraints, leaving VAUDIO on [ 1.657424] regulator_init_complete: incomplete constraints, leaving VSD on [ 1.659901] regulator_init_complete: incomplete constraints, leaving VDIG on [ 1.662279] regulator_init_complete: incomplete constraints, leaving SWBST on [ 1.665055] pmic_rtc pmic_rtc.1: setting system clock to 2011-08-27 12:39:51 UTC (1314448791) [ 2.017637] Freeing init memory: 136K [ 2.128719] udev[497]: starting version 163 [ 3.094986] libata version 3.00 loaded. [ 3.105961] pata_fsl pata_fsl: rchan=29 wchan=28 [ 3.106298] scsi0 : pata_fsl [ 3.108489] ata1: PATA max UDMA/44 irq 70 [ 3.288690] ata1.00: CFA: Flash Module, Ver2.M11, max UDMA/100 [ 3.288842] ata1.00: 30146256 sectors, multi 1: LBA [ 3.331825] ata1.00: configured for UDMA/44 [ 3.332319] scsi 0:0:0:0: Direct-Access ATA Flash Module Ver2 PQ: 0 ANSI: 5 [ 3.341668] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 3.342506] sd 0:0:0:0: [sda] 30146256 512-byte logical blocks: (15.4 GB/14.3 GiB) [ 3.342938] sd 0:0:0:0: [sda] Write Protect is off [ 3.343055] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 3.343184] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 3.344130] sda: sda1 sda2 [ 3.356149] sd 0:0:0:0: [sda] Attached SCSI disk [ 3.483131] mxsdhci: MXC Secure Digital Host Controller Interface driver [ 3.483408] mxsdhci: MXC SDHCI Controller Driver. [ 3.486526] mmc0: SDHCI detect irq 187 irq 1 INTERNAL DMA [ 3.486717] mxsdhci: MXC SDHCI Controller Driver. [ 3.489867] mmc1: SDHCI detect irq 136 irq 2 INTERNAL DMA [ 3.677256] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel at redhat.com [ 4.331136] mmc1: new SD card at address f50f [ 4.339225] mmcblk0: mmc1:f50f SD01G 982 MiB [ 4.339625] mmcblk0: p1 p2 [ 4.566126] EXT4-fs (mmcblk0p2): barriers enabled [ 4.567140] kjournald2 starting: pid 630, dev mmcblk0p2:8, commit interval 5 seconds [ 4.567437] EXT4-fs (mmcblk0p2): delayed allocation enabled [ 4.567618] EXT4-fs: file extents enabled [ 4.568000] EXT4-fs: mballoc enabled [ 4.568162] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode [ 5.602717] udev: starting version 153 [ 5.953539] SBS: Initial State: Present [ 5.953568] SBS: Battery structure 0x98e75800 [ 5.968147] usbcore: registered new interface driver usbfs [ 5.971490] usbcore: registered new interface driver hub [ 6.036757] sgtl5000-i2c 1-000a: SGTL5000 revision 17 [ 6.061298] usbcore: registered new device driver usb [ 6.105326] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 6.217667] fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller [ 6.221323] fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1 [ 6.251088] fsl-ehci fsl-ehci.0: irq 18, io base 0x73f80000 [ 6.267671] fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00 [ 6.271390] usb usb1: configuration #1 chosen from 1 choice [ 6.274538] hub 1-0:1.0: USB hub found [ 6.277648] hub 1-0:1.0: 1 port detected [ 6.497840] fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller [ 6.501036] fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2 [ 6.527681] fsl-ehci fsl-ehci.1: irq 14, io base 0x73f80200 [ 6.547653] fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00 [ 6.551201] usb usb2: configuration #1 chosen from 1 choice [ 6.554256] hub 2-0:1.0: USB hub found [ 6.558179] hub 2-0:1.0: 1 port detected [ 6.777575] usb 2-1: new high speed USB device using fsl-ehci and address 2 [ 6.780581] fsl-ehci fsl-ehci.2: Freescale On-Chip EHCI Host Controller [ 6.783451] fsl-ehci fsl-ehci.2: new USB bus registered, assigned bus number 3 [ 6.807579] fsl-ehci fsl-ehci.2: irq 16, io base 0x73f80400 [ 6.917570] fsl-ehci fsl-ehci.2: USB 2.0 started, EHCI 1.00 [ 6.920978] usb usb3: configuration #1 chosen from 1 choice [ 6.923971] hub 3-0:1.0: USB hub found [ 6.926769] hub 3-0:1.0: 1 port detected [ 6.930284] usb 2-1: configuration #1 chosen from 1 choice [ 6.933450] hub 2-1:1.0: USB hub found [ 6.936294] hub 2-1:1.0: 4 ports detected [ 7.157616] usb 3-1: new high speed USB device using fsl-ehci and address 2 [ 7.308863] usb 3-1: configuration #1 chosen from 1 choice [ 7.320428] hub 3-1:1.0: USB hub found [ 7.323756] hub 3-1:1.0: 3 ports detected [ 7.407747] usb 2-1.1: new low speed USB device using fsl-ehci and address 3 [ 7.528805] usb 2-1.1: configuration #1 chosen from 1 choice [ 7.627894] usb 2-1.4: new low speed USB device using fsl-ehci and address 4 [ 7.741698] usb 2-1.4: configuration #1 chosen from 1 choice [ 7.774611] input: USB Keyboard as /devices/platform/fsl-ehci.1/usb2/2-1/2-1.1/2-1.1:1.0/input/input1 [ 7.799839] generic-usb 0003:04D9:FF09.0001: input: USB HID v1.10 Keyboard [USB Keyboard] on usb-fsl-ehci.1-1.1/input0 [ 7.837856] usb 3-1.2: new high speed USB device using fsl-ehci and address 3 [ 7.870213] input: USB Keyboard as /devices/platform/fsl-ehci.1/usb2/2-1/2-1.1/2-1.1:1.1/input/input2 [ 7.877402] generic-usb 0003:04D9:FF09.0002: input: USB HID v1.10 Mouse [USB Keyboard] on usb-fsl-ehci.1-1.1/input1 [ 7.927924] input: USB Mouse as /devices/platform/fsl-ehci.1/usb2/2-1/2-1.4/2-1.4:1.0/input/input3 [ 7.932546] generic-usb 0003:15D9:0A33.0003: input: USB HID v1.10 Mouse [USB Mouse] on usb-fsl-ehci.1-1.4/input0 [ 7.969507] usbcore: registered new interface driver usbhid [ 7.973652] usb 3-1.2: configuration #1 chosen from 1 choice [ 7.977313] usbhid: v2.6:USB HID core driver [ 8.009391] usbcore: registered new interface driver usbmouse [ 8.013119] usbmouse: v1.6:USB HID Boot Protocol mouse driver [ 8.097352] usbcore: registered new interface driver usbkbd [ 8.101105] usbkbd: :USB HID Boot Protocol keyboard driver [ 8.171465] uvcvideo: Found UVC 1.00 device Pegatron (04f2:b1b0) [ 8.178801] input: Pegatron as /devices/platform/fsl-ehci.2/usb3/3-1/3-1.2/3-1.2:1.0/input/input4 [ 8.184645] usbcore: registered new interface driver uvcvideo [ 8.188558] USB Video Class driver (v0.1.0) [ 8.427853] EXT4-fs (mmcblk0p2): internal journal on mmcblk0p2:8 [ 12.913472] kjournald starting. Commit interval 15 seconds [ 13.098121] EXT3 FS on mmcblk0p1, internal journal [ 13.101751] EXT3-fs: mounted filesystem with writeback data mode. ljones -------------- next part -------------- An HTML attachment was scrubbed... URL: From pr0f3ss0r1492 at yahoo.com Mon Aug 29 00:35:13 2011 From: pr0f3ss0r1492 at yahoo.com (Ottavio) Date: Mon, 29 Aug 2011 01:35:13 +0100 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: On 27 August 2011 13:52, lee jones wrote: > Ok .... I decided to note down as a list of instructions what I've tried to > do, here goes. Note that it still does not boot! > Have you tried using these other boot, modules and firmware tarballs (not the rootfs, that's fedora 13): http://ausil.us/smartbook/ I have a feeling these will work and you don't need to run any scripts with this one, just unpack the boot tarball on the first partition on a sdcard formated ext3 and replace the armedslack modules and firmare and let us know. -- Ottavio A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? From slothpuck at gmail.com Mon Aug 29 16:02:48 2011 From: slothpuck at gmail.com (lee jones) Date: Mon, 29 Aug 2011 16:02:48 +0000 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: Well, good news! I'm gradually getting somewhere. Those newer boot/module/firmware files almost did the trick. I say almost as there just seems to be one tiny little problem. Ok first off. I deleted everything I had on the first SD card partition and replaced it with the ones found from here; http://ausil.us/smartbook/boot-2.6.31.14.22-efikamx.tar I also downloaded these; http://ausil.us/smartbook/modules-2.6.31.14.22-efikamx.tar http://ausil.us/smartbook/firmware.tar.bz2 I moved the contents of those (decompressed) files into /lib (that's where they decompress to in the files themselves) so that I now have a "/lib/firmware" and "/lib/modules/2.6.31.14.22-efikamx" . Note that my armed /etc/fstab and /etc/inittab are the same as earlier, i.e. >8. Edit on the second SD partition etc/initab and comment out the line starting "s0:1234", put a # in front of it to comment it out. >9. Edit on the second SD partition /etc/fstab and add this; >/dev/mmcblk0p2 / ext4 defaults 1 1 >/dev/mmcblk0p1 /boot ext3 defaults 0 0 Tried that, rebooted but no joy. I got a blue screen with an empty circle which gradually turned to white (some sort of loading graphic instead of the normal boot messages). Next job then was to kill off the loading graphics. I noticed that the boot-2.6.31.14.22-efikamx.tar file (all of its contents copied to the first partiton of the SD card) had a script called " boot.scr.in" which is used to make the boot.scr loader. This script had the following line in it; setenv bootargs root=/dev/sda2 rootwait ro rhgb quiet; So there was my first problem The SD card in my earlier attempts was always seen by the kernel as /dev/mmcblk0p1 and /dev/mmcblk0p2; sda2 would be seen as the internal flash on the efika mx. So guessing it might still be the same way (couldn't see the kernel boot messages at this stage) I changed the "sda2" to "mmcblk0p2". The boot-2.6.31.14-22-efikamax.tar file was missing a few script files like "kernel-prep" and "script-prep" so I copied these from an older boot file as per my previous attempts to boot. Ran sudo ./script-prep boot.scr.in boot.scr (from the efika mx's installed linux) ; Reboot but still nothing. Same graphic and no messages. So then I noticed a directory in that boot-2.6.31.14-22-efikamax.tar (all contents copied to the first partiton of the SD card). In it was a directory called grub and inside that a file called "splash.xpm.gz". Reasoning that this might be the graphic file, I deleted it. Reran script-prep again (as earlier) but still no joy, and still a graphic! Looked again at the boot.scr.in file . This time I tried adding in "console=tty1" and also removing "rhgb" and "quiet". So the line now looks like this; setenv bootargs console tty=1 root=/dev/mmcblk0p2 rootwait ro; Reran script-prep and rebooted. Some success! No graphic getting in the way and console messages at last. Though it still didn't complete boot and got stuck in a similar fashion to my earlier attempts. However I noticed one thing though (not sure exactly what it does!). The kernel messages spat out a message about a problem with something caleld "selinux" and mentioned setting selinux to zero in the kernel boot parameters (the message suggested using "selinux=0"). I did not know exactly what this does, but decided to try it (!), and came up with the following line for boot.scr.in; setenv bootargs console=tty1 root=/dev/mmcblk0p2 selinux=0 rootwait ro; Re-ran script-prep and rebooted again. Much better news this time :) I got to the point whereby I finally got a login prompt! However now I have some sort of bizarre keyboard problem. I can get to the point now where I'm asked for the slackware login; slackware login: but now if I type in "root" (without the " s !) and press return the system echos back the letter r followed by the cursor. So it looks like this; slackware login: root r_ Pressing return after this gives me a "Password:" prompt. Pressing return again moves the cursor down to the next line and it just waits for more keyboard input; pressing return again results in a short (one or two) second pause and "Login incorrect". I know a keymap is being loaded at boot, as I changed /etc/rc.d/rc.keymap to this; #!/bin/sh # Load the keyboard map. More maps are in /usr/share/kbd/keymaps. if [ -x /usr/bin/loadkeys ]; then echo "Loaded a keymap!" /usr/bin/loadkeys us.map fi (The efika mx smartbook I'm using has a US keyboard layout, btw). And when the system boots I can see my message "Loaded a keymap!" along with "Loading /usr/share/kbd/keymaps/i386/qwerty/us.map.gz" so I know it is loading in some sort of keymap, though it dosen't seem to be 100% quite working because of the problems above (maybe there's an arm keymap?). ljones -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Tue Aug 30 11:53:14 2011 From: louigi600 at yahoo.it (Davide) Date: Tue, 30 Aug 2011 12:53:14 +0100 (BST) Subject: [ARMedslack] Hope nobody gets upset for this Message-ID: <1314705194.39123.YahooMailClassic@web29709.mail.ird.yahoo.com> I know it's not the correct place for this but since it's ARM hardware maybe I've a little audience here. I'd sell off a Zaurus C760 and C860. Anyone intrested can email me privately about this. Sorry for disturbing. David Rao From louigi600 at yahoo.it Tue Aug 30 13:29:30 2011 From: louigi600 at yahoo.it (Davide) Date: Tue, 30 Aug 2011 14:29:30 +0100 (BST) Subject: [ARMedslack] Raspberry Pi ... keep an eye on this In-Reply-To: <1314705194.39123.YahooMailClassic@web29709.mail.ird.yahoo.com> Message-ID: <1314710970.13262.YahooMailClassic@web29713.mail.ird.yahoo.com> This might be a nice piece of hardware for running armedslack: http://www.raspberrypi.org/?page_id=2 From louigi600 at yahoo.it Tue Aug 30 13:52:48 2011 From: louigi600 at yahoo.it (Davide) Date: Tue, 30 Aug 2011 14:52:48 +0100 (BST) Subject: [ARMedslack] N00b alert: "Kernel image must be specified" (Qemu - Windows host) In-Reply-To: Message-ID: <1314712368.27968.YahooMailClassic@web29711.mail.ird.yahoo.com> Non so se ti hanno rispost a soddisfazione.... comunque lo scopo e' universalmente: inizializzare l'hardware affinche si possa caricare in ram un kernel dalle periferiche a disposizione per poi passare il controllo al kernel. Avevo scritto una cosa interessante a riguardo dello zaurus e il lavoro che fece sash per far funzionare parzialmente uboot sullo Z. Dovrei ancora averelo da qualche parte in formato txt ... ti interessa ? Era + che altro un remonder per capire io steso quello che accadeva zull Z che ai tempi mi sembrava tanto diverso da un PC ... --- Mar 16/8/11, Ottavio ha scritto: > Da: Ottavio > Oggetto: Re: [ARMedslack] N00b alert: "Kernel image must be specified" (Qemu - Windows host) > A: "Slackware ARM port" > Data: Marted? 16 agosto 2011, 10:05 > On 16 August 2011 09:00, Ottavio > > wrote: > > On 16 August 2011 01:01, Dave Dowell > wrote: > > > >> On ARM systems you always need to tell it to load > the kernel image. What > >> happens then is very dependent upon how things > have been built. > > > And another thing: can you point me out to a resource that > explains > the role of a bootloader on ARM devices as opposed to the > PC? > > Thanks > > -- > Ottavio > > > A: Because it messes up the order in which people normally > read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From pino.otto at gmail.com Tue Aug 30 13:42:40 2011 From: pino.otto at gmail.com (Giovanni) Date: Tue, 30 Aug 2011 15:42:40 +0200 Subject: [ARMedslack] Raspberry Pi ... keep an eye on this In-Reply-To: <1314710970.13262.YahooMailClassic@web29713.mail.ird.yahoo.com> References: <1314705194.39123.YahooMailClassic@web29709.mail.ird.yahoo.com> <1314710970.13262.YahooMailClassic@web29713.mail.ird.yahoo.com> Message-ID: yes, when it is available, I will buy one and try to install slack on it ciao aj On Tue, Aug 30, 2011 at 3:29 PM, Davide wrote: > This might be a nice piece of hardware for running armedslack: > http://www.raspberrypi.org/?page_id=2 > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cedric.vincent at gmail.com Tue Aug 30 14:11:54 2011 From: cedric.vincent at gmail.com (=?UTF-8?Q?C=C3=A9dric_VINCENT?=) Date: Tue, 30 Aug 2011 16:11:54 +0200 Subject: [ARMedslack] N00b alert: "Kernel image must be specified" (Qemu - Windows host) In-Reply-To: <1314712368.27968.YahooMailClassic@web29711.mail.ird.yahoo.com> References: <1314712368.27968.YahooMailClassic@web29711.mail.ird.yahoo.com> Message-ID: On Tue, Aug 30, 2011 at 3:52 PM, Davide wrote: > Non so se ti hanno rispost a soddisfazione.... comunque lo scopo e' universalmente: > inizializzare l'hardware affinche si possa caricare in ram un kernel dalle periferiche a disposizione per poi passare il controllo al kernel. > > Avevo scritto una cosa interessante a riguardo dello zaurus e il ?lavoro che fece sash per far funzionare parzialmente uboot sullo Z. > > Dovrei ancora averelo da qualche parte in formato txt ... ti interessa ? > Era + che altro un remonder per capire io steso quello che accadeva zull Z che ai tempi mi sembrava tanto diverso da un PC ... Ich habe nicht verstehen ! Please could you speak English in this mailing-list, parce que cela risque de devenir la nouvelle tour de Babel ;) Thanks, C?dric. From pr0f3ss0r1492 at yahoo.com Tue Aug 30 14:36:28 2011 From: pr0f3ss0r1492 at yahoo.com (Ottavio) Date: Tue, 30 Aug 2011 15:36:28 +0100 Subject: [ARMedslack] N00b alert: "Kernel image must be specified" (Qemu - Windows host) In-Reply-To: References: <1314712368.27968.YahooMailClassic@web29711.mail.ird.yahoo.com> Message-ID: 2011/8/30 C?dric VINCENT : > Ich habe nicht verstehen ! Please could you speak English in this > mailing-list, parce que cela risque de devenir la nouvelle tour de > Babel ;) Me and Davide are running English 0.1 (8-bit) through an emulator... -- Ottavio A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? From slothpuck at gmail.com Wed Aug 31 12:45:12 2011 From: slothpuck at gmail.com (lee jones) Date: Wed, 31 Aug 2011 12:45:12 +0000 Subject: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz) In-Reply-To: References: Message-ID: Ok here's a tidied up list of what I've tried (second attempt) at installing armedslack on the Efika MX smartbook. ---- Armedslack Version used = slack-13.1-miniroot_14Jun10.tar.xz Efika mx modules/kernel version = 2.6.31.14.22 0. Notes * This dosen't work properly yet - currently boots to a command line, but keyboard is unusable. 1. Grab an SD card and partition it into two partitons Partition 1 - 100MB EXT3 Partition 2 - Rest of card EXT4 2. Format both partitions on a linux system. Use mkfs.ext3 for the ext3 partiton, and use mkfs.ext4 for the ext4 partition. 3. Download the slack 13.1 miniroot file from here; ftp://ftp.armedslack.org/armedslack/armedslack-devtools/minirootfs/roots/slack-13.1-miniroot_14Jun10.tar.xz 4. Download the following files from here; [1] http://ausil.us/smartbook/boot-2.6.31.14.22-efikamx.tar [2] http://ausil.us/smartbook/modules-2.6.31.14.22-efikamx.tar [3] http://ausil.us/smartbook/firmware.tar.bz2 [4] http://steubentech.com/~talon/Efika-MX/mavericksd/boot.tar.xz 5. Extract two scripts from [4] - these are the files "script-prep" and "kernel-prep". 6. Extract the contents of [1] onto the first partition of the SD card. Move the files into the "boot" directory into the root of the first partition of the SD card. Delete the directories "dracut" and "grub". 7. Extract the files from the slack distro onto the second partition of the SD card, e.g. tar -xf slack-13.1-miniroot_14Jul10.tar.xz -C /where/you/mounted/the/second/partition 8. Extract the files from [2] and [3] onto the second partition of the SD card. 9. On the second SD card partition edit /etc/inittab and comment out the line starting with "s0:1234", put a # in front of that line to comment it out. 9. On the second SD card partition edit /etc/fstab and add the following; /dev/mmcblk0p2 / ext4 defaults 1 1 /dev/mmcblk0p1 /boot ext3 defaults 0 0 10. On the first partition when the files in [1] were extracted you should have a boot.scr.in file. Edit this to look as follows; setenv ramdisk uInitrd; setenv kernel uImage; setenv bootargs console=tty1 root=/dev/mmcblk0p2 selinux=0 rootwait ro; ${loadcmd} ${ramdiskaddr} ${ramdisk}; if imi ${ramdiskaddr}; then; else setenv bootargs ${bootargs} noinitrd; setenv ramdiskaddr ""; fi; ${loadcmd} ${kerneladdr} ${kernel} if imi ${kerneladdr}; then bootm ${kerneladdr} ${ramdiskaddr} fi; 11. Boot the efika MX and allow it to boot the default linux (ubuntu) install. Insert the SD card, open a command line to where the SD card (1st partition) is mounted and do the following; sudo ./script-prep boot.scr.in boot.scr 12. Reboot the efika MX smartbook, leave the SD card in the SD slot. ljones -------------- next part -------------- An HTML attachment was scrubbed... URL: