From dowelld at netscape.net Wed May 1 15:28:55 2013 From: dowelld at netscape.net (dowelld at netscape.net) Date: Wed, 1 May 2013 11:28:55 -0400 (EDT) Subject: [ARMedslack] Slackware ARM on Raspberry Pi In-Reply-To: References: <8D01405829E8E32-DA4-CEC3@webmail-m134.sysops.aol.com> Message-ID: <8D01497BA3AFCEE-DA4-11117@webmail-m134.sysops.aol.com> -----Original Message----- From: Gregg Levine To: Slackware ARM port Sent: Wed, May 1, 2013 4:03 pm Subject: Re: [ARMedslack] Slackware ARM on Raspberry Pi On Tue, Apr 30, 2013 at 6:02 PM, wrote: > Hi, > > The packages from Dave's Collective (Kernel 3.1.9) don't seem to support the > extra memory on the revised Raspberry Pi Model B board. I think this is > because the firmware package used is downlevel. > > So I've made some new firmware, kernel (3.6.11) and module packages. They > can be found here http://www.dowelld.net/?p=43. > > Thanks > Dave > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > Hello! Dave how did you get Slackware for ARM running on yours? I didn't have much luck originally with my setup and decided to put it aside. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack Hi Gregg, I modified the Dave's Collective installer ramdisk image, so that I can do headless installs. I write that (plus the other required files) to a (50MB) (v)fat partition on an SD card, then boot the Pi on that card. Then I follow the standard install path to NFS install Slackware, except I use a set of custom tagfiles to only install the packages I want. I'm currently installing a modified version of 13.37, I've added the raspi- packages to the y directory, and added them into the tagfile. Would you like me to upload the files I'm using? So you can try them. Regards Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregg.drwho8 at gmail.com Wed May 1 15:32:33 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Wed, 1 May 2013 11:32:33 -0400 Subject: [ARMedslack] Slackware ARM on Raspberry Pi In-Reply-To: <8D01497BA3AFCEE-DA4-11117@webmail-m134.sysops.aol.com> References: <8D01405829E8E32-DA4-CEC3@webmail-m134.sysops.aol.com> <8D01497BA3AFCEE-DA4-11117@webmail-m134.sysops.aol.com> Message-ID: On Wed, May 1, 2013 at 11:28 AM, wrote: > -----Original Message----- > From: Gregg Levine > To: Slackware ARM port > Sent: Wed, May 1, 2013 4:03 pm > Subject: Re: [ARMedslack] Slackware ARM on Raspberry Pi > > > On Tue, Apr 30, 2013 at 6:02 PM, wrote: >> Hi, >> >> The packages from Dave's Collective (Kernel 3.1.9) don't seem to support >> the >> extra memory on the revised Raspberry Pi Model B board. I think this is >> because the firmware package used is downlevel. >> >> So I've made some new firmware, kernel (3.6.11) and module packages. They >> can be found here http://www.dowelld.net/?p=43. >> >> Thanks >> Dave > > Hello! > Dave how did you get Slackware for ARM running on yours? I didn't have > much luck originally with my setup and decided to put it aside. > > ----- > Gregg C Levine gregg.drwho8 at gmail.com > "This signature fought the Time Wars, time and again." > > Hi Gregg, > > > > I modified the Dave's Collective installer ramdisk image, so that I can do > headless installs. > > I write that (plus the other required files) to a (50MB) (v)fat partition on > an SD card, then boot the Pi on that card. > > Then I follow the standard install path to NFS install Slackware, except I > use a set of custom tagfiles to only install the packages I want. > > I'm currently installing a modified version of 13.37, I've added the raspi- > packages to the y directory, and added them into the tagfile. > > > > Would you like me to upload the files I'm using? So you can try them. > > > > > Regards > > Dave Hello! Yes please. Along with complete instructions on how to install them. An NFS delivered install? Interesting. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From dowelld at netscape.net Wed May 1 20:20:41 2013 From: dowelld at netscape.net (dowelld at netscape.net) Date: Wed, 1 May 2013 16:20:41 -0400 (EDT) Subject: [ARMedslack] Slackware ARM on Raspberry Pi In-Reply-To: References: <8D01405829E8E32-DA4-CEC3@webmail-m134.sysops.aol.com> <8D01497BA3AFCEE-DA4-11117@webmail-m134.sysops.aol.com> Message-ID: <8D014C07C295C94-DA4-13A47@webmail-m134.sysops.aol.com> On Wed, May 1, 2013 at 11:28 AM, wrote: > -----Original Message----- > From: Gregg Levine > To: Slackware ARM port > Sent: Wed, May 1, 2013 4:03 pm > Subject: Re: [ARMedslack] Slackware ARM on Raspberry Pi > > > On Tue, Apr 30, 2013 at 6:02 PM, wrote: >> Hi, >> >> The packages from Dave's Collective (Kernel 3.1.9) don't seem to support >> the >> extra memory on the revised Raspberry Pi Model B board. I think this is >> because the firmware package used is downlevel. >> >> So I've made some new firmware, kernel (3.6.11) and module packages. They >> can be found here http://www.dowelld.net/?p=43. >> >> Thanks >> Dave > > Hello! > Dave how did you get Slackware for ARM running on yours? I didn't have > much luck originally with my setup and decided to put it aside. > > ----- > Gregg C Levine gregg.drwho8 at gmail.com > "This signature fought the Time Wars, time and again." > > Hi Gregg, > > > > I modified the Dave's Collective installer ramdisk image, so that I can do > headless installs. > > I write that (plus the other required files) to a (50MB) (v)fat partition on > an SD card, then boot the Pi on that card. > > Then I follow the standard install path to NFS install Slackware, except I > use a set of custom tagfiles to only install the packages I want. > > I'm currently installing a modified version of 13.37, I've added the raspi- > packages to the y directory, and added them into the tagfile. > > > > Would you like me to upload the files I'm using? So you can try them. > > > > > Regards > > Dave Hello! Yes please. Along with complete instructions on how to install them. An NFS delivered install? Interesting. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack Hi Gregg I've uploaded them here http://www.dowelld.net/?p=49 I hope that helps. Let me know how you get on Thanks Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.lapointe at gmail.com Thu May 2 00:58:44 2013 From: richard.lapointe at gmail.com (Richard Lapointe) Date: Wed, 01 May 2013 20:58:44 -0400 Subject: [ARMedslack] Slackware ARM on Raspberry Pi In-Reply-To: References: <8D01405829E8E32-DA4-CEC3@webmail-m134.sysops.aol.com> Message-ID: <5181BA44.6030901@laprjns.com> On 04/30/2013 06:35 PM, Gregg Levine wrote: > On Tue, Apr 30, 2013 at 6:02 PM, wrote: >> Hi, >> >> The packages from Dave's Collective (Kernel 3.1.9) don't seem to support the >> extra memory on the revised Raspberry Pi Model B board. I think this is >> because the firmware package used is downlevel. >> >> So I've made some new firmware, kernel (3.6.11) and module packages. They >> can be found here http://www.dowelld.net/?p=43. >> >> Thanks >> Dave >> >> _______________________________________________ >> ARMedslack mailing list >> ARMedslack at lists.armedslack.org >> http://lists.armedslack.org/mailman/listinfo/armedslack >> > Hello! > Dave how did you get Slackware for ARM running on yours? I didn't have > much luck originally with my setup and decided to put it aside. I got my running by following these directions: http://rpi.fatdog.eu/ Basically it get the Slackwarearm installer going. I didn't bother with downloading the Slackwarearm repo to a usb drive like it suggest in the beginning. I just got the installer going and used the ftp install method. rich at rpi-17:~$ uname -a Linux rpi-17 3.6.11+ #408 PREEMPT Wed Apr 10 20:33:39 BST 2013 armv6l ARMv6-compatible processor rev 7 (v6l) BCM2708 GNU/Linux also see http://imageshack.us/a/img849/863/screenshot0316201309191.png Rich Lapointe (laprjns) From thenktor at salixos.org Thu May 2 12:27:18 2013 From: thenktor at salixos.org (=?utf-8?Q?Thorsten_M=C3=BChlfelder?=) Date: Thu, 2 May 2013 14:27:18 +0200 Subject: [ARMedslack] Slackware ARM on Raspberry Pi In-Reply-To: <5181BA44.6030901@laprjns.com> References: <5181BA44.6030901@laprjns.com> Message-ID: > rich at rpi-17:~$ uname -a > Linux rpi-17 3.6.11+ #408 PREEMPT Wed Apr 10 20:33:39 BST 2013 armv6l > ARMv6-compatible processor rev 7 (v6l) BCM2708 GNU/Linux > > also see http://imageshack.us/a/img849/863/screenshot0316201309191.png Looks nice, but it is damn slow when used as desktop, isn't it? -- Thorsten M?hlfelder Salix OS: www.salixos.org From stanley at stanleygarvey.com Thu May 2 21:31:49 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Thu, 02 May 2013 22:31:49 +0100 Subject: [ARMedslack] Slackware ARM on Raspberry Pi In-Reply-To: References: <5181BA44.6030901@laprjns.com> Message-ID: <20130502213149.93A1CCD05B3BE@bmail03.one.com> On May 2, 2013 13:27 "Thorsten M?hlfelder" wrote: > > rich at rpi-17:~$ uname -a > > Linux rpi-17 3.6.11+ #408 PREEMPT Wed Apr 10 20:33:39 BST 2013 > > armv6l > > ARMv6-compatible processor rev 7 (v6l) BCM2708 GNU/Linux > > > > also see > > > > Looks nice, but it is damn slow when used as desktop, isn't it? > > That's a moot point. The Raspberry pi was never intended to be a > desktop machine it is a toy computer for children to learn programming > and electronic interfacing on. It also depends on what you mean by > desktop, if you mean desktop environment, the there are many to chose > from. I would not recommend running KDE on a Raspberry pi but xfce is > pretty nippy once it has loaded (on start up things like gpg-agent run > in the background soaking up 100 cpu., This can be turned off if you > wish). Speed is also affected by the raspberry pi's use of SD card > storage, you may find you have periods of high iowait caused by kswapd > and mmcd, This can be addressed by turning off journaling and access > time writes to SDcard etc. > All in all the Raspberry pi is a neat bit of 'off the shelf' kit that > has great potential for use in not only in education but also home > automation and building cool gadgets like media centers, wifi internet > radios etc, etc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dowelld at netscape.net Thu May 2 23:14:43 2013 From: dowelld at netscape.net (dowelld at netscape.net) Date: Thu, 2 May 2013 19:14:43 -0400 (EDT) Subject: [ARMedslack] Slackware ARM on Raspberry Pi In-Reply-To: <20130502213149.93A1CCD05B3BE@bmail03.one.com> References: <5181BA44.6030901@laprjns.com> <20130502213149.93A1CCD05B3BE@bmail03.one.com> Message-ID: <8D015A1F6BEB384-22F8-28D4F@webmail-vd017.sysops.aol.com> On May 2, 2013 13:27 "Thorsten M?hlfelder" wrote: rich at rpi-17:~$ uname -a Linux rpi-17 3.6.11+ #408 PREEMPT Wed Apr 10 20:33:39 BST 2013 armv6l ARMv6-compatible processor rev 7 (v6l) BCM2708 GNU/Linux also see http://imageshack.us/a/img849/863/screenshot0316201309191.png Looks nice, but it is damn slow when used as desktop, isn't it? That's a moot point. The Raspberry pi was never intended to be a desktop machine it is a toy computer for children to learn programming and electronic interfacing on. It also depends on what you mean by desktop, if you mean desktop environment, the there are many to chose from. I would not recommend running KDE on a Raspberry pi but xfce is pretty nippy once it has loaded (on start up things like gpg-agent run in the background soaking up 100 cpu., This can be turned off if you wish). Speed is also affected by the raspberry pi's use of SD card storage, you may find you have periods of high iowait caused by kswapd and mmcd, This can be addressed by turning off journaling and access time writes to SDcard etc. All in all the Raspberry pi is a neat bit of 'off the shelf' kit that has great potential for use in not only in education but also home automation and building cool gadgets like media centers, wifi internet radios etc, etc. _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack I'm using it as an headless appliance to provide remote support to customers, so I'm not using it in any kind of desktop role. For what I'm using it as it's a great little cheap box, doing sterling work as a protocol bridge. Our customers love that it basically extends our support structure right inside of their infrastructure, making passing stuff to us as easy as anything they do on their own systems. Looking at it from the declared aims of the foundation, I'm not sure their project is ontrack to deliver anything like what they set about it delivering. Which is why I stopped bothering to contribute to their site. It seems to have been taken over by hobbyists who all know how to make it be a media server, or a home automation device. The community has become filled with those people who have already done the work for the targeted audience. But then I think people are inherently lazy, if a pre-existing solution exists, which does what that person wants, then they'll use that solution rather than go and write one themselves. FOSS pretty much proves that beyond any doubt. Slackware undoubtedly proves it beyond any doubt, many slackers could build from scratch but we all like what Pat (@ team (not excluding any of the rest of you Stuart)) did, so we don't bother doing it ourselves. I can't help feeling the hobbyist community which has grown up around the Pi has pretty much ruled out kids bothering to learn with it, they'll just use the hobbyists stuff on their Pis. Now if the hobbyist community had been about "here's how you could make it into a ..." instead of "here's an image which makes it a ..." then they might have had something. If you can accept (and work around) its limitations (like 22 hours for a full build on a single Pi (distcc is a wonderful bit of kit :-) ), then it's a very capable little box, well worth the money. Thanks Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From wktintemann at online.de Wed May 8 10:22:53 2013 From: wktintemann at online.de (Wolfgang Tintemann auf Desktop PC unter Linux Mint Maya mit Evolution) Date: Wed, 08 May 2013 12:22:53 +0200 Subject: [ARMedslack] Slackware minirootfs on unsupported device wm8850 Message-ID: <1368008573.3833.8.camel@VLC-PC> I successfully booted the minirootfs on my wm8850 7 inch netbook ( Wondermedia SoC, device produced in China ). I could login as root/passwd from console tty1. Since I am a complete beginner with Slackware I would like to have some help how I get in a 1st step the network running on the minirootfs system. My ( sel-cross-compiled ) kernel ( 3.9.0-rc7 ) detects detects successfully a plugged in Logilink USB ALAN stick : ifconfig and iwconfig show wlan0 eth0 is not supported at the moment by my kernel - maybe in the near future. I tried wpa_supplicant call with a wpa_supplicant.conf which runs fine under Debian but I got no connection. Have you any recommendation what I could/must do now to get WiFi running ? From ottavio2006-usenet2012 at yahoo.com Wed May 8 14:31:29 2013 From: ottavio2006-usenet2012 at yahoo.com (Ottavio Caruso) Date: Wed, 8 May 2013 15:31:29 +0100 Subject: [ARMedslack] slackware-arm on chromebook In-Reply-To: <20130131015910.2E9FC20AE9B@rs.cname.com> References: <20130131015910.2E9FC20AE9B@rs.cname.com> Message-ID: On 31 January 2013 01:59, james_ozone wrote: > Greetings. Some google searching tells me you're the only one who has > installed slackware on a chromebook, and now that I've finally seen the > hardware, I want one too. > > Do you have something more current than the "interim" (now missing) docs? > Would you like some help? I've managed to recover my very first template for the installation of Slackware onto the Samsung Chromeboook. It contains many errors and originally it was meant for a USB flash drive, then I installed it on a SD card. Unfortunately the final document has gone lost forever. Attached in case anybody finds it useful -- Ottavio -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- ?Stimulated by Olof Johansson?s post: https://plus.google.com/u/0/109993695638569781190/posts/b2fazijJppZ I have decided to venture in the epic task of running the Slackwarearm (formerly known as Armedslack) on my new little shiny Samsung Chromebook. Don?t get me wrong: I really love Chrome OS. I love it so much that now it has become my main operating system, but I have used Slackware on Intel for a few years and I wanted to replicate my happy experience on the ARM architecture. Limitations: 1. This is not a proper port of Slackware for the Chromebook. It?s a cheap hack made by a non IT professional with too much time on his hands. A proper port would only happen if and when native kernel, module and firmware packages are available in the Slackwarearm tree. It might happen, it might not happen and it won?t be me to do the job. 2. The whole process is not very user-friendly, actually it was a massive pain for me with my limited skills. At the moment the system is barely usable but it does work. It boots all right, can acquire a proper and decent wireless connection and can be expanded downloading more packages from the Slackwarearm tree. I haven?t tested sound and video but I plan to do so once I have a proper graphical environment. 3. At the moment I haven?t replicated the installation on a SD card. Some commands might differ and you have to be extra careful when you mess with creating and deleting partitions and you might get rid of important data. 4. This document assumes that you are familiar with running the Chromebook in developer mode, that you have some experience with Slackware and the command line and have an understanding of the Slackware philosophy (What? No dependency resolution?) If the bullet points above don?t ring any bell, please don?t mess with your Chromebook as you risk to make it unusable and invalidate the warranty (yes, you could always reflash the device, but...) Before you start, familiarize yourself with these documents: http://www.chromebook-linux.com/2011/11/booting-gnulinux-distribution-from-usb.html https://plus.google.com/u/0/109993695638569781190/posts/b2fazijJppZ https://plus.google.com/u/0/109993695638569781190/posts/34PYU79eUqP http://www.armedslack.org/introduction/ Still awake and willing to take risks? Let?s go! Insert a flash drive at the back of your Chromebook. It?s a safe option to plug it into the standard USB2 port. Once plugged in, the Chrome file manager will appear and will automatically mount the USB device on the left pane, just under the Downloads and the Google Drive folder. Right click on USB drive and select ?Eject device?. Press CTRL+ALT+T and type: shell sudo su Don?t use ?sudo bash?, you are going to have problems when chrooting to the slackware partition. Type: dmesg|tail You will see an output similar to this: [10730.135107] sd 1:0:0:0: [sda] Asking for cache data failed [10730.135120] sd 1:0:0:0: [sda] Assuming drive cache: write through [10730.135130] sd 1:0:0:0: [sda] Attached SCSI removable disk Your flash drive will be identified as /dev/sda You can?t use fdisk on this device as you need a GUID Partition Table (GPT), therefore you need ?parted?. Strictly speaking you could use the Chrome OS native tool ?cgpt? but I find parted a bit more user-friendly (I?m not joking). [TODO: expand the alignment and ext4 options, ref: http://www.styryx.com/en/computers/operating-systems/unix-linux/linux-installation-to-usb-flash http://www.raspberrypi.org/phpBB3/viewtopic.php?f=9&t=850 http://www.ibm.com/developerworks/linux/library/l-4kb-sector-disks/ ] [libparted library The libparted library powers many Linux partitioning tools that support file system manipulation. Through version 2.1, the text-mode GNU Parted program (command name parted) provides little support for aligning on anything but cylinder boundaries. The best approach may be to type unit s to change the default unit to sectors. You can then manually enter partition start points in sectors and verify partition start points precisely. Version 2.2 has begun a transition toward a policy that's more useful for disks with 4096-byte physical sectors. With this version, you can specify a starting value of 1M and the sector will be properly aligned. This version also warns you when your partitions are not properly aligned. ] A little breakdown of the commands: [TODO: replace parted with cgpt] parted -a optimal /dev/sda Then at the parted prompt (parted) mktable gpt Warning: The existing disk label on /dev/sda will be destroyed and all data on this disk will be lost. Do you want to continue?Yes/No? Yes [TODO: this needs to be redone completely] (parted) unit MiB http://en.wikipedia.org/wiki/Mebibyte Create a small 17 MiB partition for the kernel starting at 1 MiB (melibytes, not megabytes) (parted) mkpart primary ext4 1 16 Then reuse all the remaining space for the root partition: (parted) mkpart primary ext4 16 -1 ?-1? means until the last sector. (parted) unit s (parted) print Number Start End Size File system Name Flags 1 4096s 30719s 26624s KERN-A 2 32768s 1998847s 1966080s ext4 ROOT-A make sure it starts at 4096s ??????? Umount the drive again as the Chromebook has this annoying habit of mounting drives when a new filesystem has been added. Duh! ??????? Don?t worry about the labels given to the partition, they will be overridden later. As ?mkpart? does not really create a filesystem, you?ll have to do it manually only on the root partition: mkfs.ext4 /dev/sda2 Don?t worry creating a filesystem on /dev/sda1. Now it?s time to install the Slackware ARM mini root filesystem. Point your Chrome browser to: http://www.armedslack.org/getslack/ Scroll down to the end of the page and select a mirror. I have selected http://ftp.slackware.org.uk/slackwarearm/ which will form the base url of the Slackware tree. Navigate into the slackwarearm-devtools/minirootfs/ directory. Make sure that you bookmark or save the README.txt file. Now change into roots/ and download the latest minirootfs, which at the moment of writing is slack-14.0-miniroot_27Sep12.tar.xz Bookmark or save also the slack-14.0-miniroot_details.txt file. Go back to slackwarearm-current/slackware/ap/ and download the latest slackpkg package, at the moment: slackpkg-2.82.0-arm-3.tgz.re Mount the second partition: mount /dev/sda2 /media/removable/ As per the README.txt file that you have previously bookmarked or saved, unpack the mini root into /mnt/removable: tar -xf /home/chronos/user/Downloads/slack-14.0-miniroot_27Sep12.tar.xz -C /media/removable/ Mount /tmp, /proc, /sys and /dev, copy some files over and chroot: mount --bind /tmp/ /media/removable/tmp/ mount --bind /proc/ /media/removable/proc/ mount --bind /sys/ /media/removable/sys/ mount --bind /dev/ /media/removable/dev/ cp /etc/resolv.conf /media/removable/etc/resolv.conf cp /home/chronos/user/Downloads/slackpkg-2.82.0-arm-3.tgz /tmp chroot /media/removable/ Switch off syslog: chmod -x /etc/rc.d/rc.syslog nano /etc/inittab and comment the first line beginning with "s0": # Local serial lines: s0:12345:respawn:/sbin/agetty 115200 ttyS0 vt100 nano /etc/securetty and comment the first line starting with ttyS0 Change the root password and add a local user with adduser. Don?t forget to add yourself to the additional users or you won?t be able to have sound, print, add devices and so on. Wipe out all kernel related packages: removepkg /var/log/packages/kernel* mkdir /lib/modules Temporarily exit from chroot and copy over the contents from /lib/modules and /lib/firmware cp -pr /lib/modules/* /media/removable/lib/modules/ cp -pr /lib/firmware/* /media/removable/lib/firmware/ Re-enter chroot and: installpkg /tmp/slackpkg-2.82.0-arm-3.tgz Edit /etc/slackpkg/slackpkg.conf and /etc/slackpkg/mirrors to your taste. Run: slackpkg update Ignore the errors and: slackpkg install gnupg ncurses Don?t worry about the frames not displaying properly. Try to live with it, the problem will be fixed once you boot into the real system. Update the gpg key: slackpkg update gpg Install a minimal set of packages, just enough to give you a wireless connection: slackpkg install wireless-tools wpa_supplicant libnl3 I assume you are using WPA authentication on your router, otherwise please refer to the Slackware wiki: http://docs.slackware.com/slackbook:wifi nano /etc/wpa_supplicant.conf You will have to add this snippet of code if you use WPA-PSK: network={ ssid="my-router-ssid" key_mgmt=WPA-PSK psk="my-router-passphrase" } [TODO: change mount points] nano /etc/fstab This is my recommended file system table: proc /proc proc defaults 0 0 tmpfs /dev/shm tmpfs defaults 0 0 tmpfs /tmp tmpfs defaults 0 0 /dev/sda2 / ext4 errors=remount-ro 0 1 Exit the chroot and copy the Chromebook mount points in case we are going to mount some partitions from within Slackware: exit cp /etc/fstab /media/removable/root/chromeos-fstab mount > /media/removable/root/chromeos-mount-points unmount everything: umount /media/removable/proc/ umount /media/removable/tmp/ umount /media/removable/sys/ umount /media/removable/dev/ umount /dev/sda2 Now we are going to pack a kernel that will be flashed over the first partition. This command will generate the kernel command line: echo "console=tty1 debug verbose \ root=/dev/sda2 rootwait ro" > /tmp/config Now I suggest to make a second config file with the read-write flag on the kernel echo "console=tty1 debug verbose \ root=/dev/sda2 rootwait rw" > /tmp/config.rw The reason for this as I had problems booting the first time with the ?ro? flg. More on this later. This command will create newkern as the binary image and sign it with the verified boot tools: vbutil_kernel --pack /home/chronos/user/Downloads/newkern \ --keyblock /usr/share/vboot/devkeys/kernel.keyblock \ --version 1 \ --signprivate /usr/share/vboot/devkeys/kernel_data_key.vbprivk \ --config=/tmp/config \ --vmlinuz /boot/vmlinuz-3.4.0 --arch arm Also create a second kernel image with the ?rw? flag so that you can use this if you have problems booting the first kernel: vbutil_kernel --pack /home/chronos/user/Downloads/newkern.rw \ --keyblock /usr/share/vboot/devkeys/kernel.keyblock \ --version 1 \ --signprivate /usr/share/vboot/devkeys/kernel_data_key.vbprivk \ --config=/tmp/config.rw \ --vmlinuz /boot/vmlinuz-3.4.0 --arch arm In my experience I had to write out the kernel with the ?rw? flag to the first partition first in order to make it work: dd if=/home/chronos/user/Downloads/newkern.rw of=/dev/sda1 Output: 7240+0 records in 7240+0 records out 3706880 bytes (3.7 MB) copied, 3.7376 s, 992 kB/s Verify the current kernel on the disk: vbutil_kernel --verify /dev/sda1 Key block: Size: 0x4b8 Flags: 7 !DEV DEV !REC Data key algorithm: 4 RSA2048 SHA256 Data key version: 1 Data key sha1sum: d6170aa480136f1f29cf339a5ab1b960585fa444 Preamble: Size: 0xfb48 Header version: 2.0 Kernel version: 1 Body load address: 0x100000 Body size: 0x379000 Bootloader address: 0x479000 Bootloader size: 0x0 Body verification succeeded. The final step is to mark the partition on the USB stick as known good so that the firmware will try to boot it. I have tried many different permutations and this is the one that worked for me: cgpt add -i 2 -S 1 -T 5 -P 5 -t kernel -l KERN-A /dev/sda A breakdown of this command: for partition index 1 (/dev/sda1), mark it as successful, priority to 5 and tries to 5. Typing: cgpt show /dev/sda should give ?Type: ChromeOS kernel? for partition 1, otherwise you have done something wrong. Now, enable booting from "USB": crossystem dev_boot_usb=1 You only perform this command once. You?ll more than most likely get this error: Unable to open FDT property nonvolatile-context-storage Just ignore it. Then reboot. At the developer mode screen press CTRL+U to load the kernel and boot from the USB stick. Fingers crossed, now you should have a familiar boot sequence and a login prompt. What I have done at this point is to reboot the Chromebook into Chrome OS and rewrite out the kernel with the ?ro? flag to the first partition and reboot again: dd if=/home/chronos/user/Downloads/newkern of=/dev/sda1 But you might be luckier at skipping this part. So let?s go back to the login prompt. As root run: ifconfig mlan0 up wpa_supplicant -c /etc/wpa_supplicant.conf -i mlan0 -d Test if it works, you should see a long stream of data and a reference to ?CONNECTED? Press CTRL+C to kill the process and restart it in the background: wpa_supplicant -c /etc/wpa_supplicant.conf -i mlan0 -B dhcpcd mlan0 Where to go from here? Now that you have a proper internet connection you should at least install the a, ap, f and n series: slackpkg install a ap f n But you probably want a full graphical environment, in which case you need the l, x and xap series. I advise against installing the Kde environment but you might well need some individual packages from the kde and kdei series. If you need to build packages from sources you also need all the D (development) package series. I plan to write a second tutorial once I have a full graphical system and am able to test how audio and video perform on this system. For now, happy hacking! From m-lists at biscuit.org.uk Wed May 8 14:50:06 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 8 May 2013 15:50:06 +0100 (BST) Subject: [ARMedslack] slackware-arm on chromebook In-Reply-To: References: <20130131015910.2E9FC20AE9B@rs.cname.com> Message-ID: > I've managed to recover my very first template for the installation of > Slackware onto the Samsung Chromeboook. It contains many errors and > originally it was meant for a USB flash drive, then I installed it on a SD > card. Unfortunately the final document has gone lost forever. I put together a semi-structured doc when I got Slackware on to my Chromebook ftp://ftp.arm.slackware.com/slackwarearm/slackwarearm-devtools/chromebook/INSTALL.txt It's not really for public consumption yet (but if I have some time in a month or so, I'll continue work on the Chromebook), but might be useful. -- Stuart Winter Slackware ARM: http://arm.slackware.com From slackware at langfinger.org Thu May 9 17:33:57 2013 From: slackware at langfinger.org (Michael Langfinger) Date: Thu, 09 May 2013 19:33:57 +0200 Subject: [ARMedslack] Strange problem installing Slackware 14.0 on the Raspberry Pi Message-ID: Hi, I tried to install Slackware 14.0 for ARM on my Raspberry Pi (Model B, 512 MB RAM). I used the installer image from http://rpi.fatdog.eu/, the package repository is on a USB flash drive. The installer boots just fine, I can configure my keyboard and set the current date without problems. I can also configure the partitions (swap, root and so on) in the setup, set the package source and select the packages. The installation process starts but quits after a few seconds, telling me that the installation was successful (which of course is wrong). Shortly before this message, two error messages pop up in the background: "Error retrieving current directory - getcwd cannot access parent directories: no such file or directory" and "/mnt/etc/fstab - no such file or directory". I made sure that the SD card is writable and mounted to /mnt. I don't think that this is a hardware issue, because the same SD card was used in this RPi with OpenELEC. And this is not the only strange behaviour - when i quit the installer, the system date is set to the next day (e.g. May,10 instead of May,9). I have no clue what might cause this and how to solve it. I installed Slackware on another RPi a while ago, without any problems (using the image from Dave's Collective and with a NFS server for the packages). I will try the image from Dave, but I don't think that this will solve the problem. Any ideas? Kind regards, Michael Langfinger From stanley at stanleygarvey.com Thu May 9 21:46:12 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Thu, 09 May 2013 22:46:12 +0100 Subject: [ARMedslack] Strange problem installing Slackware 14.0 on the Raspberry Pi In-Reply-To: References: Message-ID: <20130509214612.A54B5A5F20724@bmail-n01.one.com> On May 9, 2013 18:33 "Michael Langfinger" wrote: > Hi, > > I tried to install Slackware 14.0 for ARM on my Raspberry Pi (Model B, > 512 MB RAM). I used the installer image from > the > package repository is on a USB flash drive. The installer boots just > fine, I can configure my keyboard and set the current date without > problems. I can also configure the partitions (swap, root and so on) > in > the setup, set the package source and select the packages. The > installation process starts but quits after a few seconds, telling me > that the installation was successful (which of course is wrong). > Shortly > before this message, two error messages pop up in the background: > > "Error retrieving current directory - getcwd cannot access parent > directories: no such file or directory" and "/mnt/etc/fstab - no such > file or directory". I made sure that the SD card is writable and > mounted > to /mnt. I don't think that this is a hardware issue, because the same > SD card was used in this RPi with OpenELEC. > > And this is not the only strange behaviour - when i quit the > installer, > the system date is set to the next day (e.g. May,10 instead of May,9). > I > have no clue what might cause this and how to solve it. I installed 88 > key velocity sensiti > Slackware on another RPi a while ago, without any problems (using the > image from Dave's Collective and with a NFS server for the packages). > I > will try the image from Dave, but I don't think that this will solve > the > problem. > > Any ideas? > > Kind regards, > > Michael Langfinger > > Hi, it sounds like your mount points are incorrect, I dont know about > the date though? I tried looking up rpi.fatdog.eu. but cant connect to > the site as it seems to be down at the moment. where are you mounting > the usb package repository? You also say you have mounted the SD card > to /mnt, the slackware installer should mount the rootFS at /mnt for > you. > _______________________________________________ > ARMedslack mailing list > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackware at langfinger.org Fri May 10 07:36:15 2013 From: slackware at langfinger.org (Michael Langfinger) Date: Fri, 10 May 2013 09:36:15 +0200 Subject: [ARMedslack] Strange problem installing Slackware 14.0 on the Raspberry Pi In-Reply-To: <20130509214612.A54B5A5F20724@bmail-n01.one.com> References: <20130509214612.A54B5A5F20724@bmail-n01.one.com> Message-ID: <38ee69e0c83c5a28e6e7ea16f11ad0a0-EhVcX1hHQARfWkQdAQYAWQoDGQlVS19cWF9EAVxEXEI3UlEWXV5/H1dWQ15eRyoDXFxRQV9UWw9a-webmailer2@server06.webmailer.hosteurope.de> Hi Stanley, the USB flash drive was mounted to /floppy and the repository was available at /floppy/slackwarearm-14.0/slackware. The installer did find the package files there, and I was able to select the packages from the menu. I didn't mount the SD card manually, i was referring to where the installer mounted the RootFS partition of the SD card (in this case, mmcblk0p3 was mounted to /mnt). Anyway, I was able to install Slackware in the meantime, using a FTP server as package source. So I think that the problem is related either to a hardware incompability with the USB flash drive or a simple hardware defect of the flash drive. I didn't consider this possibility at first, because the error message pointed me to a problem with the SD card and because the installer was able to retrieve the package list from the drive without a problem. Speaking of the installer, I don't know if the behaviour in this case is useful. The installer quits telling the user that the installation was successful, although it wasn't; additionally, the important error messages that might help the user to find the cause for the problem just pop up for less than a second and then disappear; they don't get logged anywhere (neither in the syslog nor in one of the temporary files of the installer, which are created in /mnt during the installation process). I had to run the installer several times just to be able to puzzle together the error message(s). Regarding the date problem: Unfortunately I forgot to check if this also happened after the successful installation (in this case it wouldn't be related to the installation problem). Maybe I will be able to test that later this day. Kind regards, Michael Langfinger Am Donnerstag, den 09.05.2013, 23:46 +0200 schrieb "stanley garvey" : > On May 9, 2013 18:33 "Michael Langfinger" [1] wrote: > Hi, > > I tried to install Slackware 14.0 for ARM on my Raspberry Pi (Model > B, > > 512 MB RAM). I used the installer image from http://rpi.fatdog.eu/, > [2] the > package repository is on a USB flash drive. The installer boots just > fine, I can configure my keyboard and set the current date without > problems. I can also configure the partitions (swap, root and so on) > in > the setup, set the package source and select the packages. The > installation process starts but quits after a few seconds, telling me > that the installation was successful (which of course is wrong). > Shortly > before this message, two error messages pop up in the background: > > "Error retrieving current directory - getcwd cannot access parent > directories: no such file or directory" and "/mnt/etc/fstab - no such > file or directory". I made sure that the SD card is writable and > mounted > to /mnt. I don't think that this is a hardware issue, because the > same > > SD card was used in this RPi with OpenELEC. > > And this is not the only strange behaviour - when i quit the > installer, > the system date is set to the next day (e.g. May,10 instead of > May,9). > I > have no clue what might cause this and how to solve it. I installed > 88 > key velocity sensiti > Slackware on another RPi a while ago, without any problems (using the > image from Dave's Collective and with a NFS server for the packages). > I > will try the image from Dave, but I don't think that this will solve > the > problem. > > Any ideas? > > Kind regards, > > Michael Langfinger > > Hi, it sounds like your mount points are incorrect, I dont know about > the date though? I tried looking up rpi.fatdog.eu. but cant connect > to > the site as it seems to be down at the moment. where are you mounting > the usb package repository? You also say you have mounted the SD card > to /mnt, the slackware installer should mount the rootFS at /mnt for > you. > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org [3] > http://lists.armedslack.org/mailman/listinfo/armedslack [4] > > > Links: > ------ > [1] mailto:slackware at langfinger.org > [2] http://rpi.fatdog.eu/, > [3] mailto:ARMedslack at lists.armedslack.org > [4] http://lists.armedslack.org/mailman/listinfo/armedslack From m-lists at biscuit.org.uk Sat May 11 08:42:54 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 11 May 2013 09:42:54 +0100 (BST) Subject: [ARMedslack] Slackware minirootfs on unsupported device wm8850 In-Reply-To: <1368008573.3833.8.camel@VLC-PC> References: <1368008573.3833.8.camel@VLC-PC> Message-ID: > Since I am a complete beginner with Slackware I would like to have > some help how I get in a 1st step the network running on the minirootfs > system. I have had the latest available miniroot working with WiFi on the Chromebook, so I know that the tools included in the miniroot are sufficient. > My ( sel-cross-compiled ) kernel ( 3.9.0-rc7 ) detects detects > successfully a plugged in Logilink USB ALAN stick : ifconfig > and iwconfig show wlan0 [..] > > I tried wpa_supplicant call with a wpa_supplicant.conf which runs > fine under Debian but I got no connection. > > Have you any recommendation what I could/must do now to get WiFi > running ? Assuming that you've got the firmware available and loaded (which should be the case if the interface shows up in 'ifconfig'), all I did was: # cat << EOF > /etc/wpa_supplicant.conf ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=0 eapol_version=1 ap_scan=1 fast_reauth=1 EOF Then add the network ESSID and password to the wpa supplicant config: # wpa_passphrase ESSID_of_access_point YourWPApass >> /etc/wpa_supplicant.conf In /etc/rc.d/rc.inet1.conf, find the section beginning with this: ## Example config information for wlan0. Uncomment the lines you need and fill ## in your data. (You may not need all of these for your wireless network) IFNAME[4]="mlan0" ### this will change depending on your device's nic name IPADDR[4]="" NETMASK[4]="" USE_DHCP[4]="yes" DHCP_HOSTNAME[4]="icculus-wireless" DHCP_KEEPRESOLV[4]="no" DHCP_KEEPNTP[4]="no" DHCP_KEEPGW[4]="no" DHCP_IPADDR[4]="" WLAN_ESSID[4]=YOURESSID WLAN_MODE[4]=Managed WLAN_RATE[4]="54M auto" WLAN_CHANNEL[4]="auto" WLAN_KEY[4]="YOURWLANKEY" #WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=YOURWLAKEY" WLAN_WPA[4]="wpa_supplicant" WLAN_WPADRIVER[4]="wext" WLAN_WPAWAIT[4]=10 ------------------------------ You'll need to look through that to make sure you have the correct settings, then you can run /etc/rc.d/rc.inet1 and it should bring up your WLAN NIC. -- Stuart Winter Slackware ARM: http://arm.slackware.com From louigi600 at yahoo.it Fri May 17 17:53:59 2013 From: louigi600 at yahoo.it (Davide) Date: Fri, 17 May 2013 18:53:59 +0100 (BST) Subject: [ARMedslack] tigervnc for slackware arm In-Reply-To: <1366701453.22435.YahooMailNeo@web28806.mail.ir2.yahoo.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> <516F4D26.8070509@laprjns.com> <1366267726.66275.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366274242.70229.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366278467.500.YahooMailNeo@web28805.mail.ir2.yahoo.com> <516FCD68.7040903@laprjns.com> <1366285376.44148.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366634953.80971.YahooMailNeo@web28803.mail.ir2.yahoo.com> <5175BCB9.7000904@laprjns.com> <1366701453.22435.YahooMailNeo@web28806.mail.ir2.yahoo.com> Message-ID: <1368813239.15904.YahooMailNeo@web28804.mail.ir2.yahoo.com> Can't seem to get tightvnc client to interoperate with the x0vncserver running on my desktop. I can find tigervnc package for x86 slackware ... anyone have an idea if there's an ARM tigervnc package ? Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.lapointe at gmail.com Sat May 18 12:26:13 2013 From: richard.lapointe at gmail.com (Richard Lapointe) Date: Sat, 18 May 2013 08:26:13 -0400 Subject: [ARMedslack] tigervnc for slackware arm In-Reply-To: <1368813239.15904.YahooMailNeo@web28804.mail.ir2.yahoo.com> References: <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> <516F4D26.8070509@laprjns.com> <1366267726.66275.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366274242.70229.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366278467.500.YahooMailNeo@web28805.mail.ir2.yahoo.com> <516FCD68.7040903@laprjns.com> <1366285376.44148.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366634953.80971.YahooMailNeo@web28803.mail.ir2.yahoo.com> <5175BCB9.7000904@laprjns.com> <1366701453.22435.YahooMailNeo@web28806.mail.ir2.yahoo.com> <1368813239.15904.YahooMailNeo@web28804.mail.ir2.yahoo.com> Message-ID: <51977365.5010403@laprjns.com> Here one that I built but never tested. http://dl.dropboxusercontent.com/u/90881870/tightvnc-1.3.10-arm-1rl.txz It was built on a d\Dockstar running slackwarearm 14.0 I have close to five hundred arm (armv5tel) packages that were built natively on a Dockstar / Pogoplug using Salix slkbuild packaging system (http://slkbuild.sourceforge.net/) and Salix's source repo ( http://salix.enialis.net/x86_64/14.0/source/). Rich Lapointe (laprjns) On 05/17/2013 01:53 PM, Davide wrote: > Can't seem to get tightvnc client to interoperate with the x0vncserver > running on my desktop. > I can find tigervnc package for x86 slackware ... anyone have an idea > if there's an ARM tigervnc package ? > > Regards > David ar > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Mon May 20 05:30:27 2013 From: louigi600 at yahoo.it (Davide) Date: Mon, 20 May 2013 06:30:27 +0100 (BST) Subject: [ARMedslack] tigervnc for slackware arm In-Reply-To: <51977365.5010403@laprjns.com> References: <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> <516F4D26.8070509@laprjns.com> <1366267726.66275.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366274242.70229.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366278467.500.YahooMailNeo@web28805.mail.ir2.yahoo.com> <516FCD68.7040903@laprjns.com> <1366285376.44148.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366634953.80971.YahooMailNeo@web28803.mail.ir2.yahoo.com> <5175BCB9.7000904@laprjns.com> <1366701453.22435.YahooMailNeo@web28806.mail.ir2.yahoo.com> <1368813239.15904.YahooMailNeo@web28804.mail.ir2.yahoo.com> <51977365.5010403@laprjns.com> Message-ID: <1369027827.57180.YahooMailNeo@web28805.mail.ir2.yahoo.com> It's not a typo .... I'm looking for TIGERvnc client not tightvnc client. I run a desktop across 2 screens on my work pc (tigervnc x0vncserver shares?your live desktop) and the tightvnc client seems to crash when I try to connect to it, this does not happen if I use the tigervnc client. ? Regards David ________________________________ Da: Richard Lapointe A: Davide ; Slackware ARM port Inviato: Sabato 18 Maggio 2013 14:26 Oggetto: Re: [ARMedslack] tigervnc for slackware arm Here one that I built but never tested.? http://dl.dropboxusercontent.com/u/90881870/tightvnc-1.3.10-arm-1rl.txz It was built on a d\Dockstar running slackwarearm 14.0 I have close to five hundred arm (armv5tel) packages that were built natively on a Dockstar / Pogoplug? using Salix slkbuild packaging system (http://slkbuild.sourceforge.net/) and Salix's source repo ( http://salix.enialis.net/x86_64/14.0/source/). Rich Lapointe (laprjns) On 05/17/2013 01:53 PM, Davide wrote: Can't seem to get tightvnc client to interoperate with the x0vncserver running on my desktop. >I can find tigervnc package for x86 slackware ... anyone have an idea if there's an ARM tigervnc package ? > >Regards >David ar > > > >_______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From mozes at slackware.com Tue May 28 21:13:16 2013 From: mozes at slackware.com (Stuart Winter) Date: Tue, 28 May 2013 14:13:16 -0700 (PDT) Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 Message-ID: Hi Since Slackware 14.1 is coming together, could all of you who plan on preparing and distributing support for Slackware ARM 14.1 for the RaspberryPi please reply to this message (on-list) with the following information. I will collate it and put it into the /INSTALL_RASPBERRYPI.TXT document within the release. Note that this is *only* for those of you who are supplying images/installers that contain the _official_ Slackware ARM packages which will be taken from ftp.arm.slackware.com/slackwarearm/slackwarearm-14.1. 1. The URL of the web site containing information about your distribution. 2. Installation method: regular installer / pre-supplied image(s) If it's a pre-supplied image, what categories of software are included: Don't list every package, but a high level brief description such as: dev tools ('d') - Compilers and toolchain tools - Python, Perl X11 ('x') - X packages relevant to the Rpi KDE ('kde') - All of KDE - Base components of KDE 3. RPi boards / versions of boards that your distribution has been tested with and confirmed operational. 4. The particular reason for choosing yours over another. Some of the reasons that some people have created their own image is because Dave Spencer's work stopped at 13.37, or theirs addressed particular problems on certain boards. Please note that this shouldn't be a reason for the 14.1 release - you should treat this as new rather than a patch to someone else's work (even if that's what it started out as). Deadline: --------- I'll stop taking submissions at the release of RC1 of Slackware 14.1 x86. Any questions - please ask! Cheers Stuart. -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: http://arm.slackware.com From stanley at stanleygarvey.com Thu May 30 07:34:11 2013 From: stanley at stanleygarvey.com (stanley at stanleygarvey.com) Date: Thu, 30 May 2013 09:34:11 +0200 Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: References: Message-ID: <4c3f9baec30c1edd25e84fb27bb198de.squirrel@webmail01.one.com> > > Hi > > > Since Slackware 14.1 is coming together, could all of you who > plan on preparing and distributing support for Slackware ARM > 14.1 for the RaspberryPi please reply to this message (on-list) with the > following information. I will collate it and put it into the > /INSTALL_RASPBERRYPI.TXT document within the release. > > Note that this is *only* for those of you who are supplying > images/installers that contain the _official_ Slackware ARM packages which > will be taken from ftp.arm.slackware.com/slackwarearm/slackwarearm-14.1. > > 1. The URL of the web site containing information about your > distribution. > > 2. Installation method: regular installer / pre-supplied image(s) > > If it's a pre-supplied image, what categories of software are > included: > > Don't list every package, but a high level brief description such as: > > dev tools ('d') > > - Compilers and toolchain tools > - Python, Perl > > X11 ('x') > > - X packages relevant to the Rpi > > KDE ('kde') > - All of KDE > - Base components of KDE > > > 3. RPi boards / versions of boards that your distribution has been > tested with and confirmed operational. > > 4. The particular reason for choosing yours over another. Some of the > reasons that some people have created their own image is because Dave > Spencer's work stopped at 13.37, or theirs addressed particular > problems on certain boards. > > Please note that this shouldn't be a reason for the 14.1 release - > you should treat this as new rather than a patch to someone else's > work (even > if that's what it started out as). > > > Deadline: > --------- > > I'll stop taking submissions at the release of RC1 of Slackware 14.1 x86. > > Any questions - please ask! > > Cheers > Stuart. > > > -- > Stuart Winter > www.slackware.com/~mozes > Slackware for ARM: http://arm.slackware.com > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > Hi Stuart I would be happy to provide both an installer and some pre-installed images for 14.1 for the Raspberry Pi. Installer: 1) stanleygarvey.com/Slackberry/index.php 2)regular installer, after install drop to shell and execute raspberrypi/finalise.sh (a simple bash script to remove non rpi kernels, source and stuff). 3) Version 14.0 tested on model B boards revision A 256MB and B 512MB and confirmed operational, however the file '70-persistent-net.rules' may require tweeking to bring eth0 up. 4) No particular reason for choosing my installer over another. It is a modified version of your versatile-initrd placed on David Spenser's partition scheme. Pre-supplied images: 1) stanleygarvey.com/Slackberry/index.php 2)full install of all packages excluding KDE KDEI and kernel source. 3) Version 14.0 tested on model B boards revision A 256MB and B 512MB and confirmed operational, however the file '70-persistent-net.rules' may require tweeking to bring eth0 up. 4) No particular reason for choosing my pre-installed images over another. Kernels are now built using a modified slackwarearm build script and do not occupy the kernel.bin namespace. Also a plea for help. Since 14.0 eth0 is renamed to eth1 on first boot (but not always), I did not see this in version 13.37 and attributed this to an error on my part then to rc.wireless. since It also occurs when using the installer I think it may be a race condition some were. If anyone can help with this please drop a line to me on the list. From louigi600 at yahoo.it Thu May 30 08:31:20 2013 From: louigi600 at yahoo.it (Davide) Date: Thu, 30 May 2013 09:31:20 +0100 (BST) Subject: [ARMedslack] Toshiba AC100 In-Reply-To: References: Message-ID: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> I noticed that the whole http://tosh-ac100.wetpaint.com/ thing has been taken down thus braking the link for the information on how to get slackware arme on the AC100. I'm trying to get the info from the wetpaint crew (at least the text I wrote) to see if I can have it hosted somewhere else. Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregg.drwho8 at gmail.com Thu May 30 14:26:23 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Thu, 30 May 2013 10:26:23 -0400 Subject: [ARMedslack] Toshiba AC100 In-Reply-To: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> References: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> Message-ID: On Thu, May 30, 2013 at 4:31 AM, Davide wrote: > I noticed that the whole http://tosh-ac100.wetpaint.com/ thing has been > taken down thus braking the link for the information on how to get slackware > arme on the AC100. > I'm trying to get the info from the wetpaint crew (at least the text I > wrote) to see if I can have it hosted somewhere else. > > Regards > David > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > Hello! Yes it says "Site blocked" and offers an apology from the hosting entity. Please keep us up to date. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From gregg.drwho8 at gmail.com Thu May 30 14:30:34 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Thu, 30 May 2013 10:30:34 -0400 Subject: [ARMedslack] Toshiba AC100 In-Reply-To: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> References: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> Message-ID: On Thu, May 30, 2013 at 4:31 AM, Davide wrote: > I noticed that the whole http://tosh-ac100.wetpaint.com/ thing has been > taken down thus braking the link for the information on how to get slackware > arme on the AC100. > I'm trying to get the info from the wetpaint crew (at least the text I > wrote) to see if I can have it hosted somewhere else. > > Regards > David Hello! I just asked Google about our interested problem and as it happens Google told me about the Wikipedia entries on it. That location has at its bottom of page an external link, that link is here: http://ac100.grandou.net/ that Wiki has a surprise there. It contains your text carefully collected from the mistake that Wetpaint claims they blocked. (The mistake was theirs, not yours.) I believe it is the text you were thinking of. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From louigi600 at yahoo.it Fri May 31 07:00:32 2013 From: louigi600 at yahoo.it (Davide) Date: Fri, 31 May 2013 08:00:32 +0100 (BST) Subject: [ARMedslack] Toshiba AC100 In-Reply-To: References: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> Message-ID: <1369983632.36172.YahooMailNeo@web28805.mail.ir2.yahoo.com> >> I noticed that the whole http://tosh-ac100.wetpaint.com/ thing has been >> taken down thus braking the link for the information on how to get slackware >> arme on the AC100. >> I'm trying to get the info from the wetpaint crew (at least the text I >> wrote) to see if I can have it hosted somewhere else. >> >> Regards >> David >Hello! >I just asked Google about our interested problem and as it happens >Google told me about the Wikipedia entries on it. That location has at >its bottom of page an external link, that link is here: >http://ac100.grandou.net/ that Wiki has a surprise there. > >It contains your text carefully collected from the mistake that >Wetpaint claims they blocked. (The mistake was theirs, not yours.) I >believe it is the text you were thinking of. Intresting but I can't see to find my text .... I probabbly need to have a better look? but even the search form over there is not helping me. Have you a link directly to the text ? Stuart: if thext is where Greg says maybe the link in the supported platforms should be updated (as it's currently broken). Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregg.drwho8 at gmail.com Fri May 31 14:23:11 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Fri, 31 May 2013 10:23:11 -0400 Subject: [ARMedslack] Toshiba AC100 In-Reply-To: <1369983632.36172.YahooMailNeo@web28805.mail.ir2.yahoo.com> References: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1369983632.36172.YahooMailNeo@web28805.mail.ir2.yahoo.com> Message-ID: On Fri, May 31, 2013 at 3:00 AM, Davide wrote: > > >>> I noticed that the whole http://tosh-ac100.wetpaint.com/ thing has been >>> taken down thus braking the link for the information on how to get >>> slackware >>> arme on the AC100. >>> I'm trying to get the info from the wetpaint crew (at least the text I >>> wrote) to see if I can have it hosted somewhere else. >>> >>> Regards >>> David > >>Hello! >>I just asked Google about our interested problem and as it happens >>Google told me about the Wikipedia entries on it. That location has at >>its bottom of page an external link, that link is here: >>http://ac100.grandou.net/ that Wiki has a surprise there. >> >>It contains your text carefully collected from the mistake that >>Wetpaint claims they blocked. (The mistake was theirs, not yours.) I >>believe it is the text you were thinking of. > > Intresting but I can't see to find my text .... > I probabbly need to have a better look but even the search form over there > is not helping me. > Have you a link directly to the text ? > > Stuart: if thext is where Greg says maybe the link in the supported > platforms should be updated (as it's currently broken). > > Regards > David Hello! It's down at the bottom of the pages on the new site. I promptly selected the link and brought it up, and shoehorned it into the Tiny URL maker. Here: http://tinyurl.com/m3qffon and that's yours. They state that after importing the (possibly) obsolete information it will be deleted. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From louigi600 at yahoo.it Fri May 31 19:34:35 2013 From: louigi600 at yahoo.it (Davide) Date: Fri, 31 May 2013 20:34:35 +0100 (BST) Subject: [ARMedslack] Toshiba AC100 In-Reply-To: References: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1369983632.36172.YahooMailNeo@web28805.mail.ir2.yahoo.com> Message-ID: <1370028875.41867.YahooMailNeo@web28805.mail.ir2.yahoo.com> >>>> I noticed that the whole http://tosh-ac100.wetpaint.com/ thing has been >>>> taken down thus braking the link for the information on how to get >>>> slackware >>>> arme on the AC100. >>>> I'm trying to get the info from the wetpaint crew (at least the text I >>>> wrote) to see if I can have it hosted somewhere else. >>>> >>>> Regards >>>> David >> >>>Hello! >>>I just asked Google about our interested problem and as it happens >>>Google told me about the Wikipedia entries on it. That location has at >>>its bottom of page an external link, that link is here: >>>http://ac100.grandou.net/ that Wiki has a surprise there. >>> >>>It contains your text carefully collected from the mistake that >>>Wetpaint claims they blocked. (The mistake was theirs, not yours.) I >>>believe it is the text you were thinking of. >> >> Intresting but I can't see to find my text .... >> I probabbly need to have a better look? but even the search form over there >> is not helping me. >> Have you a link directly to the text ? >> >> Stuart: if thext is where Greg says maybe the link in the supported >> platforms should be updated (as it's currently broken). >> >> Regards >> David >Hello! >It's down at the bottom of the pages on the new site. I promptly >selected the link and brought it up, and shoehorned it into the Tiny >URL maker. Here: http://tinyurl.com/m3qffon and that's yours. They >state that after importing the (possibly) obsolete information it will >be deleted. There's probably something wrong with me or with my browser or some other dumb thing? ... but I recognize a menu that's resembles remotely what used to be on tosh-ac100 ... but I looked on every element of the menu and could not recognise my armedslack (it was not slackware arm at the time) howto ... well if you can see the text save it somewhere. I'm not interested in the layout ... just the text. I'll fix it up and find another place to host it. Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From ottavio2006-usenet2012 at yahoo.com Fri May 31 21:42:39 2013 From: ottavio2006-usenet2012 at yahoo.com (Ottavio Caruso) Date: Fri, 31 May 2013 22:42:39 +0100 Subject: [ARMedslack] Toshiba AC100 In-Reply-To: <1370028875.41867.YahooMailNeo@web28805.mail.ir2.yahoo.com> References: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1369983632.36172.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370028875.41867.YahooMailNeo@web28805.mail.ir2.yahoo.com> Message-ID: On May 31, 2013 8:34 PM, "Davide" wrote: > > > >>>> I noticed that the whole http://tosh-ac100.wetpaint.com/ thing has been > >>>> taken down thus braking the link for the information on how to get > >>>> slackware > >>>> arme on the AC100. > >>>> I'm trying to get the info from the wetpaint crew (at least the text I > >>>> wrote) to see if I can have it hosted somewhere else. > >>>> > >>>> Regards > >>>> David > >> > >>>Hello! > >>>I just asked Google about our interested problem and as it happens > >>>Google told me about the Wikipedia entries on it. That location has at > >>>its bottom of page an external link, that link is here: > >>>http://ac100.grandou.net/ that Wiki has a surprise there. > >>> > >>>It contains your text carefully collected from the mistake that > >>>Wetpaint claims they blocked. (The mistake was theirs, not yours.) I > >>>believe it is the text you were thinking of. > >> > >> Intresting but I can't see to find my text .... > >> I probabbly need to have a better look but even the search form over there > >> is not helping me. > >> Have you a link directly to the text ? > >> > >> Stuart: if thext is where Greg says maybe the link in the supported > >> platforms should be updated (as it's currently broken). > >> > >> Regards > >> David > > >Hello! > >It's down at the bottom of the pages on the new site. I promptly > >selected the link and brought it up, and shoehorned it into the Tiny > >URL maker. Here: http://tinyurl.com/m3qffon and that's yours. They > >state that after importing the (possibly) obsolete information it will > >be deleted. > > There's probably something wrong with me or with my browser or some other dumb thing ... but I recognize a menu that's resembles remotely what used to be on tosh-ac100 ... but I looked on every element of the menu and could not recognise my armedslack (it was not slackware arm at the time) howto ... well if you can see the text save it somewhere. > I'm not interested in the layout ... just the text. I'll fix it up and find another place to host it. > > Regards > David > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > Have you tried on the web archive? http://web.archive.org -------------- next part -------------- An HTML attachment was scrubbed... URL: