From carlo.caione at gmail.com Sun Dec 5 21:37:26 2010 From: carlo.caione at gmail.com (Carlo Caione) Date: Sun, 05 Dec 2010 22:37:26 +0100 Subject: [ARMedslack] Unable to login (armedslack 13.1 + beagleboard) Message-ID: <1291585046.26059.9.camel@belfagor> Hi, This is pretty strange (for me). The problem is that my armedslack on beagleboard xM rev.A doesn't allow me to login (using pass: root, password: password). Even more strange is that I cannot access even after I modified the /etc/shadow or /etc/passwd files (resetting the root password). Here the full log: http://pastebin.com/gFfXfrTT Any idea? Thank you, -- Carlo Caione From unixjohn1969 at gmail.com Sun Dec 5 22:37:01 2010 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Sun, 5 Dec 2010 17:37:01 -0500 Subject: [ARMedslack] Unable to login (armedslack 13.1 + beagleboard) In-Reply-To: References: <1291585046.26059.9.camel@belfagor> Message-ID: /etc/securetty ? ** This message has been delivered via a Google Android ** On Dec 5, 2010 4:36 PM, "Carlo Caione" wrote: Hi, This is pretty strange (for me). The problem is that my armedslack on beagleboard xM rev.A doesn't allow me to login (using pass: root, password: password). Even more strange is that I cannot access even after I modified the /etc/shadow or /etc/passwd files (resetting the root password). Here the full log: http://pastebin.com/gFfXfrTT Any idea? Thank you, -- Carlo Caione _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlo.caione at gmail.com Sun Dec 5 22:54:55 2010 From: carlo.caione at gmail.com (Carlo Caione) Date: Sun, 5 Dec 2010 23:54:55 +0100 Subject: [ARMedslack] Unable to login (armedslack 13.1 + beagleboard) In-Reply-To: References: <1291585046.26059.9.camel@belfagor> Message-ID: On Dec 5, 2010, at 11:37 PM, John O'Donnell wrote: > /etc/securetty ? What a shame, yes, thank you... I would suggest to insert this in the README file for minirootfs. -- Carlo Caione From m-lists at biscuit.org.uk Tue Dec 7 10:01:50 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 7 Dec 2010 10:01:50 +0000 (GMT) Subject: [ARMedslack] Unable to login (armedslack 13.1 + beagleboard) In-Reply-To: References: <1291585046.26059.9.camel@belfagor> Message-ID: > What a shame, yes, thank you... > I would suggest to insert this in the README file for minirootfs. Thanks. I've added it in. From jawkins at armedslack.org Tue Dec 7 10:53:22 2010 From: jawkins at armedslack.org (Jim Hawkins) Date: Tue, 7 Dec 2010 10:53:22 +0000 (GMT) Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: References: <20101128094331.506cdab1@liberty> Message-ID: On Mon, 29 Nov 2010, Stuart Winter wrote: > On Sun, 28 Nov 2010, John O'Donnell wrote: > > > You are booting from ext. It is HIDEOUSLY slow. I make a small FAT partition > > and boot from that on the guru usb. > > This must be something to do with the Guruplug. I boot from an ext2 > partition on my sheevaplugs and openrd (which has an eSATA drive) and it > takes a couple of seconds to load both the kernel & initrd. There seems to be something wrong with SATA in the latest u-boot. As others have reported, I couldn't get it to detect the eSATA drive on my guruplug. If I revert the last commit to the Marvell ATA stuff it seems happier, although it sometimes fails to detect the drive and when it does, it shows the drive twice as two devices. I've just booted my kernel from an ext2 formatted partition on an eSATA drive on my guruplug. It's not slow. When I've got some time I'll look into making it work more reliably. Cheers, Jim From christophe.lyon at gmail.com Tue Dec 7 20:44:20 2010 From: christophe.lyon at gmail.com (Christophe Lyon) Date: Tue, 7 Dec 2010 21:44:20 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar Message-ID: Hi all, I have recently purchased a Dockstar, and I have some trouble making it boot on ARMedSlack installed on a memory stick, despite reading messages on this mailing list. I have replaced the original uboot by the one described on http://jeff.doozan.com/debian/uboot/ which is configured to boot from /dev/sda1. After several attempts with Slackware, I have successfully booted Debian on my memory stick using the procedure/script from http://jeff.doozan.com/debian/, so the stick is OK :-) I must mention that I don't have a serial cable; I have actived uboot's netconsole, which is helpful... but not enough. To install Slackware, I have installed the minirootfs from ftp://ftp.armedslack.org/armedslack/armedslack-devtools/minirootfs/roots/slack-13.1-miniroot_14Jun10.tar.xz and followed the instructions (mainly declare /dev/sda1 as '/' in etc/fstab) When trying to boot Slackware, here are the messages I can read: (Re)start USB... USB: ? Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 3 USB Device(s) found ? ? ?scanning bus for storage devices... 1 Storage Device(s) found Loading file "/rescueme" from usb device 0:1 (usbda1) ** File not found /rescueme reading /rescueme.txt ** Unable to read "/rescueme.txt" from usb 0:1 ** Creating 1 MTD partitions on "nand0": 0x000002500000-0x000010000000 : "mtd=3" UBI: attaching mtd1 to ubi0 UBI: physical eraseblock size: ? 131072 bytes (128 KiB) UBI: logical eraseblock size: ? ?129024 bytes UBI: smallest flash I/O unit: ? ?2048 UBI: sub-page size: ? ? ? ? ? ? ?512 UBI: VID header offset: ? ? ? ? ?512 (aligned 512) UBI: data offset: ? ? ? ? ? ? ? ?2048 UBI: attached mtd1 to ubi0 UBI: MTD device name: ? ? ? ? ? ?"mtd=3" UBI: MTD device size: ? ? ? ? ? ?219 MiB UBI: number of good PEBs: ? ? ? ?1752 UBI: number of bad PEBs: ? ? ? ? 0 UBI: max. allowed volumes: ? ? ? 128 UBI: wear-leveling threshold: ? ?4096 UBI: number of internal volumes: 1 UBI: number of user volumes: ? ? 0 UBI: available PEBs: ? ? ? ? ? ? 1731 UBI: total number of reserved PEBs: 21 UBI: number of PEBs reserved for bad PEB handling: 17 UBI: max/mean erase counter: 1/1 UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19 Error reading superblock on volume 'ubi:rootfs'! Loading file "/boot/uImage" from usb device 0:1 (usbda1) 1 bytes read Found bootable drive on usb 0:1 Loading file "/boot/uImage" from usb device 0:1 (usbda1) 2096780 bytes read Loading file "/boot/uInitrd" from usb device 0:1 (usbda1) 7706248 bytes read ## Booting kernel from Legacy Image at 00800000 ... ?Image Name: ? Linux-2.6.33.5-kirkwood ?Image Type: ? ARM Linux Kernel Image (uncompressed) ?Data Size: ? ?2096716 Bytes = 2 MiB ?Load Address: 00008000 ?Entry Point: ?00008000 ?Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 01100000 ... ?Image Name: ? Slackware ARM Initial RAM disk f ?Image Type: ? ARM Linux RAMDisk Image (gzip compressed) ?Data Size: ? ?7706184 Bytes = 7.3 MiB ?Load Address: 00000000 ?Entry Point: ?00000000 ?Verifying Checksum ... OK ?Loading Kernel Image ... OK OK Starting kernel ... And nothing more. Then I have tried nmap, but no service answers, so I don't know if the kernel as booted OK or not. I have tried to add netconsole=@192.168.0.3 to bootargs, but it looks like the supplied kernel does not support netconsole. Any hint? Thanks! From claudio.cavalera at gmail.com Thu Dec 9 11:58:26 2010 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Thu, 9 Dec 2010 12:58:26 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: Message-ID: On Tue, Dec 7, 2010 at 21:44, Christophe Lyon wrote: > I must mention that I don't have a serial cable; I have actived > uboot's netconsole, which is helpful... but not enough. > You are stuck at the same point as me. If you read my emails you could find some parameters to pass at the kernel command line in order to have DHCP and network and therefore avoid serial cable. Not wokring for me though. :-( Please let us know if you succeed. Thanks, Claudio From m-lists at biscuit.org.uk Thu Dec 9 12:02:15 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 9 Dec 2010 12:02:15 +0000 (GMT) Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: Message-ID: > kernel command line in order to have DHCP and network and therefore > avoid serial cable. Not wokring for me though. :-( > Please let us know if you succeed. Did you check your DHCP logs? does the device request an IP? /me suggests getting a serial cable :) At least then we can figure out where the boot process is failing - it might be a simple fix. From claudio.cavalera at gmail.com Thu Dec 9 13:30:11 2010 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Thu, 9 Dec 2010 14:30:11 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: Message-ID: On Thu, Dec 9, 2010 at 13:02, Stuart Winter wrote: > >> kernel command line in order to have DHCP and network and therefore >> avoid serial cable. Not wokring for me though. :-( >> Please let us know if you succeed. > > Did you check your DHCP logs? ?does the device request an IP? My DHCP server is the ADSL router. It is a switch. :-/ > /me suggests getting a serial cable :) > At least then we can figure out where the boot process is failing - it > might be a simple fix. I have a serial cable but I can't bear debian works without it. :-) Ciao, Claudio From m-lists at biscuit.org.uk Thu Dec 9 13:48:25 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 9 Dec 2010 13:48:25 +0000 (GMT) Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: Message-ID: > I have a serial cable but I can't bear debian works without it. :-) Hang on a minute. So you've got a serial cable... use it, figure out where the boot process stops (if at all). Then once we know what the problem is, it can most likely be fixed or worked around. Then, once it's fixed, you can forget that you ever used it and pretend like everything worked first time. http://www.hypnosis101.com/amnesia.htm Easy. Let's get to it! :-) From thenktor at gmx.de Thu Dec 9 14:14:36 2010 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Thu, 9 Dec 2010 15:14:36 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: Message-ID: <201012091514.36900.thenktor@gmx.de> Am Thursday 09 December 2010 14:48:25 schrieb Stuart Winter: > > I have a serial cable but I can't bear debian works without it. :-) > > Hang on a minute. So you've got a serial cable... > use it, figure out where the boot process stops (if at all). > Then once we know what the problem is, it can most likely be fixed or > worked around. Within 90 % a serial cable to RS232 connector won't work with the Dockstar. You need a TTL to RS232 level converter. Search for it on ebay and you'll find some cheap TTL to USB interfaces from China. From claudio.cavalera at gmail.com Thu Dec 9 15:04:53 2010 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Thu, 9 Dec 2010 16:04:53 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: <201012091514.36900.thenktor@gmx.de> References: <201012091514.36900.thenktor@gmx.de> Message-ID: 2010/12/9 Thorsten M?hlfelder : > Am Thursday 09 December 2010 14:48:25 schrieb Stuart Winter: >> > I have a serial cable but I can't bear debian works without it. :-) >> >> Hang on a minute. ?So you've got a serial cable... >> use it, figure out where the boot process stops (if at all). >> Then once we know what the problem is, it can most likely be fixed or >> worked around. > > Within 90 % a serial cable to RS232 connector won't work with the Dockstar. > You need a TTL to RS232 level converter. > Search for it on ebay and you'll find some cheap TTL to USB interfaces from > China. I already have the right serial cable with the right connector. But I'm too lazy to open the dockstar. :-) From christophe.lyon at gmail.com Thu Dec 9 20:02:00 2010 From: christophe.lyon at gmail.com (Christophe Lyon) Date: Thu, 9 Dec 2010 21:02:00 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <201012091514.36900.thenktor@gmx.de> Message-ID: > > I already have the right serial cable with the right connector. But > I'm too lazy to open the dockstar. :-) Too bad! I misread your initial post and thought you actually succeeded in booting Slackware.... :-( From claudio.cavalera at gmail.com Thu Dec 9 23:30:00 2010 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Fri, 10 Dec 2010 00:30:00 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <201012091514.36900.thenktor@gmx.de> Message-ID: On Thu, Dec 9, 2010 at 21:02, Christophe Lyon wrote: >> >> I already have the right serial cable with the right connector. But >> I'm too lazy to open the dockstar. :-) > > Too bad! > I misread your initial post and thought you actually succeeded in > booting Slackware.... :-( Maybe I've booted it but it did not get an IP Address. Serial cable is for whimps. :-) Which parameters do you use at bootm= ? From christophe.lyon at gmail.com Fri Dec 10 12:09:10 2010 From: christophe.lyon at gmail.com (Christophe Lyon) Date: Fri, 10 Dec 2010 13:09:10 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <201012091514.36900.thenktor@gmx.de> Message-ID: On Fri, Dec 10, 2010 at 12:30 AM, Claudio Cavalera wrote: > On Thu, Dec 9, 2010 at 21:02, Christophe Lyon wrote: >>> >>> I already have the right serial cable with the right connector. But >>> I'm too lazy to open the dockstar. :-) >> >> Too bad! >> I misread your initial post and thought you actually succeeded in >> booting Slackware.... :-( > > Maybe I've booted it but it did not get an IP Address. Serial cable is > for whimps. :-) > Which parameters do you use at bootm= ? As I said, I used Jeff Doozan's script to update my uboot, which also sets to boot parameters. I have: usb_root=/dev/sda1 usb_rootfstype=ext2 usb_rootdelay=10 usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi (usb_device is set to 0:1 by usb_scan) bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset (I copied only the usb_bootcmd part, as it is the only relevant one here) I have tried to add netconsole parameters to usb_set_bootargs, with no effect. Christophe. From claudio.cavalera at gmail.com Fri Dec 10 13:12:10 2010 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Fri, 10 Dec 2010 14:12:10 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <201012091514.36900.thenktor@gmx.de> Message-ID: On Fri, Dec 10, 2010 at 13:09, Christophe Lyon wrote: >> Maybe I've booted it but it did not get an IP Address. Serial cable is >> for whimps. :-) >> Which parameters do you use at bootm= ? > > As I said, I used Jeff Doozan's script to update my uboot, which also > sets to boot parameters. I have also used that script to update/patch my uboot but just for that. I then activated the netconsole and used uboot interactively with a couple of nc sessions. You should be able to do this if you read well within my old emails at this list. I think we are using completely different approaches. I was using a tftp server with tftpboot commands at uboot prompt. Regards, Claudio From christophe.lyon at gmail.com Fri Dec 10 14:48:58 2010 From: christophe.lyon at gmail.com (Christophe Lyon) Date: Fri, 10 Dec 2010 15:48:58 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <201012091514.36900.thenktor@gmx.de> Message-ID: >> As I said, I used Jeff Doozan's script to update my uboot, which also >> sets to boot parameters. > > I have also used that script to update/patch my uboot but just for that. > I then activated the netconsole and used uboot interactively with a > couple of nc sessions. You should be able to do this if you read well > within my old emails at this list. > I think we are using completely different approaches. > I was using a tftp server with tftpboot commands at uboot prompt. > Indeed, I'd like to avoid tftp if it's not absolutely necessary... and I don't see why it would be. Does anyone know if the pre-compiled ARMedslackware kernel support netconsole? (If so, then it looks like the kernel boot crashes before netconsole is operational). Christophe. From m-lists at biscuit.org.uk Fri Dec 10 15:58:29 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 10 Dec 2010 15:58:29 +0000 (GMT) Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <201012091514.36900.thenktor@gmx.de> Message-ID: > Does anyone know if the pre-compiled ARMedslackware kernel support > netconsole? (If so, then it looks like the kernel boot crashes before > netconsole is operational). It's compiled as a module, so you'd have to include it in the initrd. I've taken the latest code from kernel.SlackBuild (where the initrd's are made) and made this script: http://stash.armedslack.org/scripts/make-new-initrd.sh (This is useful for people in general, btw). This will make a new initrd for the *Operating system*, however, not the installer. There's no point in adding netconsole to the installer initrd because the installer's initrd is quite a different beast and if it's not making it as far as running the /etc/rc.d/rc.modules-arm script, then you're buggered. Actually - what driver does the dockstar use for its ethernet? I assume it's mv643xx_eth -- if not, then that's your problem ;-) I can't imagine it'd be anything other than that though. In order to use netconsole with the installer you'd have to recompile the kernel to include netconsole and the ethernet driver into the kernel itself. From claudio.cavalera at gmail.com Fri Dec 10 16:06:26 2010 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Fri, 10 Dec 2010 17:06:26 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <201012091514.36900.thenktor@gmx.de> Message-ID: On Fri, Dec 10, 2010 at 16:58, Stuart Winter wrote: > Actually - what driver does the dockstar use for its ethernet? > I assume it's mv643xx_eth -- if not, then that's your problem ;-) > I can't imagine it'd be anything other than that though. I have it when I run lsmod in the debian mv643xx_eth Ciao, Claudio From cedric.vincent at gmail.com Sat Dec 11 10:08:34 2010 From: cedric.vincent at gmail.com (=?UTF-8?Q?C=C3=A9dric_VINCENT?=) Date: Sat, 11 Dec 2010 11:08:34 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <201012091514.36900.thenktor@gmx.de> Message-ID: On Fri, Dec 10, 2010 at 4:58 PM, Stuart Winter wrote: > > It's compiled as a module, so you'd have to include it in the initrd. Maybe the netconsole feature would be more useful as a builtin instead of as a module in this specific case (i.e. don't get ARMedSlack booting on Dockstar and don't use a serial console), since the kernel may run into troubles before the load of the module. Christophe, I should be able to provide you a kernel with the netconsole as a builtin on Monday if you wish. Will you give it a try with ARMedSlack mini-rootfs and investigate what's going on? Regards, C?dric. From m-lists at biscuit.org.uk Sat Dec 11 10:28:38 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 11 Dec 2010 10:28:38 +0000 (GMT) Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <201012091514.36900.thenktor@gmx.de> Message-ID: > Maybe the netconsole feature would be more useful as a builtin instead > of as a module in this specific case (i.e. don't get ARMedSlack > booting on Dockstar and don't use a serial console), since the kernel > may run into troubles before the load of the module. This means you also need to compile the network driver into the kernel. In the kernel I only want to include drivers that really cannot be modules, so I'll keep the NIC drivers as modules. From cedric.vincent at gmail.com Sat Dec 11 10:34:46 2010 From: cedric.vincent at gmail.com (=?UTF-8?Q?C=C3=A9dric_VINCENT?=) Date: Sat, 11 Dec 2010 11:34:46 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <201012091514.36900.thenktor@gmx.de> Message-ID: On Sat, Dec 11, 2010 at 11:28 AM, Stuart Winter wrote: > > This means you also need to compile the network driver into the kernel. Thanks for the advice. > In the kernel I only want to include drivers that really cannot be > modules, so I'll keep the NIC drivers as modules. I do agree with you, that was just a suggestion for debug purpose in this specific case. Does someone know if there is a reliable support for in-memory kernel core dump on ARM? It could be useful too. From christophe.lyon at gmail.com Sat Dec 11 21:28:29 2010 From: christophe.lyon at gmail.com (Christophe Lyon) Date: Sat, 11 Dec 2010 22:28:29 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <201012091514.36900.thenktor@gmx.de> Message-ID: 2010/12/11 C?dric VINCENT : > Christophe, I should be able to provide you a kernel with the > netconsole as a builtin on Monday if you wish. ?Will you give it a try > with ARMedSlack mini-rootfs and investigate what's going on? > Yes, it could be useful, thanks! From christophe.lyon at gmail.com Wed Dec 15 12:35:35 2010 From: christophe.lyon at gmail.com (Christophe Lyon) Date: Wed, 15 Dec 2010 13:35:35 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <201012091514.36900.thenktor@gmx.de> Message-ID: On Fri, Dec 10, 2010 at 5:06 PM, Claudio Cavalera wrote: > I have it when I run lsmod in the debian > mv643xx_eth > For the record, I have also noticed that under Debian the kernel version is a bit older: root at debian:~# uname -a Linux debian 2.6.32-5-kirkwood #1 Fri Nov 26 07:01:06 UTC 2010 armv5tel GNU/Linux The modules loaded are: root at debian:~# lsmod Module Size Used by ipv6 253826 10 hmac 2475 0 sha1_generic 1717 0 mv_cesa 9262 0 aes_generic 32820 1 mv_cesa ext2 55411 1 mbcache 4860 1 ext2 sd_mod 31312 3 crc_t10dif 1106 1 sd_mod usb_storage 34879 2 scsi_mod 119252 2 sd_mod,usb_storage ehci_hcd 35579 0 usbcore 122203 3 usb_storage,ehci_hcd mvsdio 5318 0 nls_base 5367 1 usbcore mv643xx_eth 22562 0 mmc_core 50206 1 mvsdio libphy 14836 1 mv643xx_eth inet_lro 5060 1 mv643xx_eth configfs 20841 0 # cat /proc/cpuinfo Processor : Feroceon 88FR131 rev 1 (v5l) BogoMIPS : 1192.75 Features : swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant : 0x2 CPU part : 0x131 CPU revision : 1 Hardware : Marvell SheevaPlug Reference Board Revision : 0000 Serial : 0000000000000000 Christophe. From unixjohn1969 at gmail.com Fri Dec 17 05:21:28 2010 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Fri, 17 Dec 2010 00:21:28 -0500 Subject: [ARMedslack] KDE fails in -current Message-ID: <4D0AF358.5010907@gmail.com> I just upgraded my guruplug to -current from a previous -current root at guruslack:/var/adm/packages# lm kde* kdeaccessibility-4.5.4-arm-1 kdenetwork-4.5.4-arm-1 kdeadmin-4.5.4-arm-1 kdepim-4.4.7-arm-1 kdeartwork-4.5.4-arm-1 kdepim-runtime-4.4.7-arm-6 kdebase-4.5.4-arm-1 kdepimlibs-4.5.4-arm-1 kdebase-runtime-4.5.4-arm-1 kdeplasma-addons-4.5.4-arm-1 kdebase-workspace-4.5.4-arm-1 kdesdk-4.5.4-arm-1 kdebindings-4.5.4-arm-1 kdetoys-4.5.4-arm-1 kdeedu-4.5.4-arm-1 kdeutils-4.5.4-arm-1 kdegames-4.5.4-arm-1 kdevelop-4.1.1-arm-1 kdegraphics-4.5.4-arm-1 kdevplatform-1.1.1-arm-1 kdelibs-4.5.4-arm-1 kdewebdev-4.5.4-arm-1 kdemultimedia-4.5.4-arm-1 I cannot start KDE nor any KDE apps now. startkde: Starting up... kdeinit4: Shutting down running client. Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance() kbuildsycoca4 running... kbuildsycoca4(26397) KBuildSycoca::checkTimestamps: checking file timestamps kbuildsycoca4(26397) KBuildSycoca::checkTimestamps: timestamps check ok kbuildsycoca4(26397) kdemain: Emitting notifyDatabaseChanged () Fetched layout groups from X server: layouts: ("us") variants: ("") X Error: BadValue (integer parameter out of range for operation) 2 Major opcode: 102 (X_ChangeKeyboardControl) Resource id: 0xffffffe0 Fetched layout groups from X server: layouts: ("us") variants: ("") QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance() QDBusObjectPath: invalid path "" kded(26396)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.5' kwin(26411) Kephal::DesktopWidgetScreens::DesktopWidgetScreens: foo kwin(26411) KDecorationPlugins::loadPlugin: kwin : path "/usr/lib/kde4/kwin3_plastik.so" for "kwin3_plastik" Application::crashHandler() called with signal 11; recent crashes: 1 KCrash: Application 'kwin' crashing... kwin(26413) Kephal::DesktopWidgetScreens::DesktopWidgetScreens: foo kwin(26413) KDecorationPlugins::loadPlugin: kwin : path "/usr/lib/kde4/kwin3_plastik.so" for "kwin3_plastik" Application::crashHandler() called with signal 11; recent crashes: 2 KCrash: Application 'kwin' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit KCrash: Application 'drkonqi' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit kwin(26416) KWin::Application::Application: Too many crashes recently, disabling compositing kwin(26416) Kephal::DesktopWidgetScreens::DesktopWidgetScreens: foo kwin(26416) KDecorationPlugins::loadPlugin: kwin : path "/usr/lib/kde4/kwin3_plastik.so" for "kwin3_plastik" Application::crashHandler() called with signal 11; recent crashes: 3 KCrash: Application 'drkonqi' crashing... KCrash: Application 'kwin' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit KCrash: Application 'drkonqi' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit QDBusObjectPath: invalid path "" kwin(26420) KWin::Application::Application: Too many crashes recently, disabling compositing kwin(26420) Kephal::DesktopWidgetScreens::DesktopWidgetScreens: foo kwin(26420) KDecorationPlugins::loadPlugin: kwin : path "/usr/lib/kde4/kwin3_plastik.so" for "kwin3_plastik" Application::crashHandler() called with signal 11; recent crashes: 4 KCrash: Application 'kwin' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit KCrash: Application 'plasma-desktop' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit (26422)/: Communication problem with "plasma-desktop" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.ServiceUnknown" : " "The name org.kde.plasma-desktop was not provided by any .service files" " QDBusObjectPath: invalid path "" KCrash: Application 'drkonqi' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit KCrash: Application 'drkonqi' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit (26427)/: Communication problem with "plasma-desktop" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.ServiceUnknown" : " "The name org.kde.plasma-desktop was not provided by any .service files" " Application::crashHandler() called with signal 11; recent crashes: 5 KCrash: Application 'kwin' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit kcminit(26403)/kdecore (KLibrary) findLibraryInternal: plugins should not have a 'lib' prefix: "libkcm_hotkeys.so" kcminit(26403)/kdecore (KLibrary) findLibraryInternal: plugins should not have a 'lib' prefix: "libkcm_keys.so" KCrash: Application 'drkonqi' crashing... KCrash: Application 'drkonqi' crashing... kcminit(26403)/kdecore (KLibrary) findLibraryInternal: plugins should not have a 'lib' prefix: "libkcminit_nsplugins.so" kcminit(26403)/kdecore (KLibrary) findLibraryInternal: plugins should not have a 'lib' prefix: "libkcm_emoticons.so" KCrash: Application 'drkonqi' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit QMetaObject::invokeMethod: No such method KAccessApp::loadCommandLineOptionsForNewInstance() Application::crashHandler() called with signal 11; recent crashes: 6 KCrash: Application 'kwin' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit Qt: Session management error: Could not open network socket ICE default IO error handler doing an exit(), pid = 26438, errno = 11 KCrash: Attempting to start /usr/bin/krunner from kdeinit kdeinit4: (krunner /usr/bin/krunner) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: Resource temporarily unavailable KCrash: Attempting to start /usr/bin/krunner directly KCrash: Application 'krunner' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit kdeinit4: (drkonqi /usr/lib/kde4/libexec/drkonqi) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: No such file or directory KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly If I try to launch just one app I get this: root at guruslack:/usr/adm/packages# export DISPLAY=mrlinux:0 root at guruslack:/usr/adm/packages# cd root at guruslack:~# ktorrent QMetaObject::invokeMethod: No such method kt::App::loadCommandLineOptionsForNewInstance() Warning: QSocketNotifier: Invalid socket 15 and type 'Read', disabling... KCrash: Application 'ktorrent' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/root/.kde/socket-guruslack/kdeinit4_mrlinux_0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly root at guruslack:~# KCrash: Application 'drkonqi' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/root/.kde/socket-guruslack/kdeinit4_mrlinux_0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly KCrash: Application 'drkonqi' crashing... -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From m-lists at biscuit.org.uk Fri Dec 17 18:12:23 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 17 Dec 2010 18:12:23 +0000 (GMT) Subject: [ARMedslack] KDE fails in -current In-Reply-To: <4D0AF358.5010907@gmail.com> References: <4D0AF358.5010907@gmail.com> Message-ID: > I just upgraded my guruplug to -current from a previous -current Have you tried mving your .kde directory out of the way and trying again? To be honest I can't remember if I tried this KDE version or not. I don't have local access to my ARM kit until mid-februrary, so I can't do the usual testing I would. I tried one KDE startup over XVNC but I don't recall if this was this version or the rebuild I did a few weeks ago. As an aside, I think that Slackware 13.2 will be released in the next couple of months (just a hunch!), but given that armedslack-current hasn't had anywhere *near* the amount of testing I'd usually be able to do, I am thinking of skipping the 13.2 release. Also, maintaining too many versions consumes too much time. From m-lists at biscuit.org.uk Sun Dec 19 12:15:40 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 19 Dec 2010 12:15:40 +0000 (GMT) Subject: [ARMedslack] KDE fails in -current In-Reply-To: <4D0AF358.5010907@gmail.com> References: <4D0AF358.5010907@gmail.com> Message-ID: > I just upgraded my guruplug to -current from a previous -current I've tried this with x11vnc - yep, it's pretty broken isn't it! I think it might be because of the new "mesa", so I'm going to have a play around with that now. From unixjohn1969 at gmail.com Sun Dec 19 12:29:07 2010 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Sun, 19 Dec 2010 07:29:07 -0500 Subject: [ARMedslack] KDE fails in -current In-Reply-To: References: <4D0AF358.5010907@gmail.com> Message-ID: <4D0DFA93.7010302@gmail.com> On 12/19/2010 07:15 AM, Stuart Winter wrote: > >> I just upgraded my guruplug to -current from a previous -current > > I've tried this with x11vnc - yep, it's pretty broken isn't it! > > I think it might be because of the new "mesa", so I'm going to have a play > around with that now. Let me know when you have a new version to test, I'll be at the top! Reverted back to 13.1 last night (QT, XZ, All KDE, etc, etc). Thanks O -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From m-lists at biscuit.org.uk Sun Dec 19 14:12:15 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 19 Dec 2010 14:12:15 +0000 (GMT) Subject: [ARMedslack] KDE fails in -current In-Reply-To: <4D0DFA93.7010302@gmail.com> References: <4D0AF358.5010907@gmail.com> <4D0DFA93.7010302@gmail.com> Message-ID: > > I think it might be because of the new "mesa", so I'm going to have a play > > around with that now. > > Let me know when you have a new version to test, I'll be at the top! > Reverted back to 13.1 last night (QT, XZ, All KDE, etc, etc). I don't think it's Mesa now, although I've rebuilt it to make "xlib" the default driver, as it should be on ARM. WindowMaker works fine through x11vnc - I think it's a KDE problem. There's a 4.4.5 KDE release available which looks like it'll fix at least a few of those errors. I might try upgrading kdebase and seeing if that works, but hopefully KDE will be upgraded in Slackware. -- Stuart Winter Slackware ARM: www.armedslack.org From m-lists at biscuit.org.uk Sun Dec 19 14:47:06 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 19 Dec 2010 14:47:06 +0000 (GMT) Subject: [ARMedslack] KDE fails in -current In-Reply-To: References: <4D0AF358.5010907@gmail.com> <4D0DFA93.7010302@gmail.com> Message-ID: > There's a 4.4.5 KDE release available which looks like it'll fix at least > a few of those errors. I got confused by Debian's numbering scheme - there isn't one. Ubuntu has a beta release, but you cannot cherry pick bits of KDE to build. There are a number of posts which have the same errors in as you posted, so there might be commits that can be pulled out and patched in the current version of KDE. Other than that, it'll stay broken! -- Stuart Winter Slackware ARM: www.armedslack.org From richard.lapointe at gmail.com Tue Dec 21 02:37:12 2010 From: richard.lapointe at gmail.com (Rich) Date: Mon, 20 Dec 2010 21:37:12 -0500 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <201012091514.36900.thenktor@gmx.de> Message-ID: <4D1012D8.4070109@laprjns.com> My testing indicates that it not getting an ip assign during initialization because the rc.inet1.conf file isn't configured I'm a wimp, so I've been using serial cable to observe what is happening. Using a desktop with Linux (Salix OS) I partitioned a Memorex 2G USB Stick into two partitions, one (sda1) for the root file system and a second for a swap partitions. I untar'ed the mini file system on to sda1, edited fstab to have sda1 mounted / and sda2 as swap. I then added sym links for the kernel and initrd ln -s uImage-kirkwood-2.3.33.5 uImage ln -s unitrd-kirkwood02.6.33.5 uInitrd Then I plug the stick into my dockstar (using doozan uboot along with his rescue system) and booted it. I monitored the boot up process with a netconsole terminal and a serial terminal connection to the dockstar. The two file attached are the output of each of these terminals during the boot process. On the initial boot, it did boot the kernel and started the system initialization scripts but then fdisk the sda1 and rebooted. The second boot did complete and I got a login prompt on the serial terminal. The netconole terminal stop at Starting kernel...... , but did show the reboot into the second boot up and then again stop at starting kernel. Although it did boot to the login prompt, my router did not indicate that the dockstar was connected. Using the serial console, i looked in and checked ifconfig and fond that there was no ip Linux 2.6.33.5-kirkwood. Last login: Thu Jan 1 01:00:52 +0100 1970 on /dev/ttyS0. You have mail. root at slackware:~# ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:560 (560.0 B) TX bytes:560 (560.0 B) I then checked /etc/rc.d/rc.inet1.conf file and noticed that it wasn't configured. I edited to use dhcp USE_DHCP[0]="yes" rebooted and was able to ssh into the dockstar Rich Lapointe On 12/10/2010 10:58 AM, Stuart Winter wrote: > >> Does anyone know if the pre-compiled ARMedslackware kernel support >> netconsole? (If so, then it looks like the kernel boot crashes before >> netconsole is operational). >> > It's compiled as a module, so you'd have to include it in the initrd. > > I've taken the latest code from kernel.SlackBuild (where the initrd's are > made) and made this script: > > http://stash.armedslack.org/scripts/make-new-initrd.sh > > (This is useful for people in general, btw). > > This will make a new initrd for the *Operating system*, however, not the > installer. > > There's no point in adding netconsole to the installer initrd because the > installer's initrd is quite a different beast and if it's not making it as > far as running the /etc/rc.d/rc.modules-arm script, then you're buggered. > > Actually - what driver does the dockstar use for its ethernet? > I assume it's mv643xx_eth -- if not, then that's your problem ;-) > I can't imagine it'd be anything other than that though. > > In order to use netconsole with the installer you'd have to recompile the > kernel to include netconsole and the ethernet driver into the kernel > itself. > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > > -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: test-1_serial.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: test-1_netconsole.txt URL: From m-lists at biscuit.org.uk Tue Dec 21 10:13:41 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 21 Dec 2010 10:13:41 +0000 (GMT) Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: <4D1012D8.4070109@laprjns.com> References: <201012091514.36900.thenktor@gmx.de> <4D1012D8.4070109@laprjns.com> Message-ID: On Mon, 20 Dec 2010, Rich wrote: > My testing indicates that it not getting an ip assign during initialization > because the rc.inet1.conf file isn't configured I'm a wimp, so I've been > using serial cable to observe what is happening. Since you have a serial cable, can you also try booting the installer? This is what the others have been struggling with -- why doesn't the installer get an IP? If you boot using the config lines found here: ftp://ftp.armedslack.org/armedslack/armedslack-devtools/sheevaplug/quickboot.txt Take the line below this heading: "-current (automatically starting DHCP and SSHd)" The system should boot and get an IP from DHCP. Can you see what is happening? -- Stuart Winter Slackware ARM: www.armedslack.org From richard.lapointe at gmail.com Tue Dec 28 21:12:10 2010 From: richard.lapointe at gmail.com (Rich) Date: Tue, 28 Dec 2010 16:12:10 -0500 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <201012091514.36900.thenktor@gmx.de> <4D1012D8.4070109@laprjns.com> Message-ID: <4D1A52AA.8010102@laprjns.com> I wasn't to sure how you got the installer running over ssh, so here's what I did. First, my dockstar is running Jeff Doozan latest uboot and Rescue System, so when I boot without any usb drives plugged in it boots into the Rescue System (http://forum.doozan.com/read.php?4,831). I connect to the dockstar via ssh (the rescue system starts dhcp). Although I do have the serial line running, I just use it to monitor what going on since I'm trying to figure out how to install armedslack without a serial line. (I've got two other dockstars waiting in the wings). Once I'm connected I do the following: Prepare a directory for change root file system 1) mkdir /tmp/armedslack 2) cd /tmp/armedslack Download the armedslack uinitrd (has the installer) and decompress it # wget ftp://ftp.armedslack.org/armedslack/armedslack-13.1/isolinux/uinitrd-kirkwood.img # dd if=uinitrd-kirkwood.img bs=64 skip=1 | gzip -dc | cpio -div Now thing get a little fuzzy for me, since I really don't have a deep knowledge of what I'm doing. I found through googling that I had to do the following mounts before I changed rooted into the installer fs. It seems to br needed to mount a usb stick and its the only way to get nano running; i don't know how to use vim . #mount /proc/ /tmp/armedslack/proc # mount /dev/ /tmp/armedslack/proc # chroot /tmp/armedslack /bin/bash #TERM=linux Now plug in a usb drive, run fdisk or cfdisk and partition the drive. Since I using Doozan uboot / needs to be on sda1. I partitioned my 4G usb stick with 3.75G sda1 for \ and sda2 as a 250M swap. OK, now run the armedslack installer. #./usr/lib/setup/setup This will resulted in running the armedslack installer. The only thing of note here is that I selected a ftp install and connect to the ftp.armedslack.org using its ip address (83.170.96.167). After successfully connecting to the repos, I then select the packages and the installer proceeds to install the packages. With my usb stick and depending on the packages selected this can take a few hours to install. I found that using my Seagate Freeagent 500GM disk loads much faster. Once everything is installed and the setup is complete (network, root password, services etc) I exit out of the installer and then add the following sym links since Doozan uboot looks for uImange and uInitrd to boot. #cd /boot # ln -s uinitrd-kickwood-2.6.35.5 uInitrd # ln -s uImage-kirkwood-2.6.35.5 uImage Then I exist out of the changed root environment and reboot the dockstar. After all this and with using the serial output to monitor the process, the kernel does boot but gets a fdisk error and stalls for 60 second and then reboots, repeating the sequence over and over. See the attached file for the boot output and fdisk error from the serial link. It seems to have something to do with the dockstar not having a real time clock and getting time stamp errors. I am able to fix this by doing the following. 1) Add the following line in rc.S right at the beginning /bin/mount -n -o remount,ro / 2) add an e2fsck,config file to /etc/. The file that i use can be found here. ftp://laprjns.com/in/e2fsck.conf Once I added these, rebooting results in going through a successful fdisk on the / fs. After completing the fdisk, it successfully reboots to the armedslack prompt. Since it's fdisk'ing and rebooting it does take a little while to come up . Also found that once I successfully booted, I then can remove both the mount line in rc.S and the e2fsck.con file and boot the system there after. I sure that there is a better way to get the installer running, but as I said my linux knowledge is limited. Regards Rich Lapointe (laprjns) On 12/21/2010 05:13 AM, Stuart Winter wrote: > On Mon, 20 Dec 2010, Rich wrote: > > >> My testing indicates that it not getting an ip assign during initialization >> because the rc.inet1.conf file isn't configured I'm a wimp, so I've been >> using serial cable to observe what is happening. >> > Since you have a serial cable, can you also try booting the installer? > > This is what the others have been struggling with -- why doesn't the > installer get an IP? If you boot using the config lines found here: > ftp://ftp.armedslack.org/armedslack/armedslack-devtools/sheevaplug/quickboot.txt > > Take the line below this heading: > "-current (automatically starting DHCP and SSHd)" > > The system should boot and get an IP from DHCP. > > Can you see what is happening? > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: test A 12-28-20 URL: