Re: [ARMedslack] Raspberry-Pi sanity check
On Sep 30, 2013 19:50 Yigit Turgut y.tur...@gmail.com wrote: You post feels like installing windows xp and/thus doesn't prove that you are sane. http://en.wikipedia.org/wiki/Sane I think it would be better if you could give instructions to get slackarm-current from official source,burn to card,boot up (the whole procedure) - like fatdog. Yes I do need to document more, In this instance I just needed to prove to myself and to anyone that was listening that the files were not corrupt and booted. The Images are an easy way to skip the installation procedure, the installer is better, you get to select the packages you want. I have no wish to reinvent the wheel and there are some great texts around showing how to install a Slackware system, fatdog has done an excellent job. Personally I would install via FTP of HTTP and not from a USB stick, however not everyone has internet access, so it's horses for courses. If you wish to install current then use the installer and point it to the official source. The Installer is just the standard Slackwarearm installer I have changed very little. Regards. Stanley ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] A quick primer for the PI
On Sep 27, 2013 12:16 Tom tom...@spoko.eu.org wrote: I do not need images to test, just boot files and kernel. With these: ftp://ftp.stanleygarvey.co.uk/pub/slackwarearm_rpi/boot/ Both of mine RPis hang at colorful screen. Set of files that work for me: https://salwach.pl/img/RPi/slack14_tom.zip Tom Thanks for testing, ftp://ftp.stanleygarvey.co.uk/pub/slackwarearm_rpi/boot/ These are the new raspbian wheezy 2013-09-10 boot files and where for Davide to try. The kernel is mine, but expects swap on partition 2 and ext4 rootfs on partition 3, and the cmdline.txt is compiled into the kernel. the kernel also requires the config.txt to point to it as it is not called kernel.img. I am sure your files will work for me here but so do mine. Thanks for your help. Stanley ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] Raspberry-Pi sanity check
Okay, Just to check I am sane I will now demonstrate how to install an image to SDHC card, there will be no camera tricks or fudges: As root: bash-4.2# cd /home/stanley bash-4.2# mkdir sanity-check bash-4.2# cd sanity-check bash-4.2# wget http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623 .zip --2013-09-27 20:26:42-- http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623 .zip Resolving stanleygarvey.com (stanleygarvey.com)... 46.30.211.48 Connecting to stanleygarvey.com (stanleygarvey.com)|46.30.211.48|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1632447253 (1.5G) [application/zip] Saving to: 'slackwarearm-14.0-8GB-20130623.zip' 100%[] 1,632,447,253 7.43MB/s in 3m 36s 2013-09-27 20:30:47 (7.22 MB/s) - 'slackwarearm-14.0-8GB-20130623.zip' saved [1632447253/1632447253] bash-4.2# unzip slackwarearm-14.0-8GB-20130623.zip Archive: slackwarearm-14.0-8GB-20130623.zip inflating: slackwarearm-14.0-8GB-20130623.img - Just for good measure -- bash-4.2# md5sum slackwarearm-14.0-8GB-20130623.img b96fbb397ce028af8cc257b5b5c4f443 slackwarearm-14.0-8GB-20130623.img -- Now I insert an SDHC 8GB card, on this system. I have 1 hard drive(/dev/sda) and one USB Drive(dev/sdb) the SDHC card becomes /dev/sdc -- bash-4.2# dd if=slackwarearm-14.0-8GB-20130623.img of=/dev/sdc bs=65536 123056+0 records in 123056+0 records out 8064598016 bytes (8.1 GB) copied, 1856 s, 4.3 MB/s --- Well that took a while! Now I pop the SDHC card into a random Raspberry Pi and boot and ... Er ..it just boots up. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Generic Allwinner Slackware installer, was: Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd)
On Jul 28, 2013 09:52 Stuart Winter m-li...@biscuit.org.uk wrote: I noticed RPi patches also not making it into kernel.org. Last weekend I tried to compile a generic 3.10.1 kernel for the RPi and it failed to boot. Rather than patch kernel source for a specific ARM target, are we expected to use the generic kernel and build a device tree binary? That's the idea, yes except that you wouldn't have to build the device tree blob since if support is compiled into the kernel for that device, then the DTB would already have been built and would be provided with the kernel package. The DTBs are generated by kernel.SlackBuild for the specific architectures, so once additional support is added, the architecture name will need to be appended to the list for the specific kernel. I tried to build an armv6 and armv7 generic kernel, but since the base line is set to armv6, when armv7 code begins to build, it fails since the ARMv6 CPUs cannot execute v7 instructions. I don't understand why you can select both CPUs in this case. You need to select ARMv7 to choose the hardware that has a v7 CPU. I guess the whole thing isn't entirely complete yet, or perhaps I'm misunderstanding what you can do with it. Needless to say, I'm building a ganeric armv7 kernel now. Thanks for that, I am building a generic armv6 kernel now, using the bcm2835_defconfig. hoping it will boot later today. This is what I should have done in the first place rather than trying to make oldconfig :( then I can make any tweeks it may require. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] Kernel 2.10 and raspberry pi
Hi, just been to kernel.org to see if the raspberry pi is supported. I see no support for the device in any kernel previous to 3.10.1 which includes support for the BCM2835. I find this odd. I would have thought that patches would have been submitted and merged in the the kernel tree. We still got super H Dreamcast code in there so why no Raspberry pi? Work is still being done on 3.6.11 at raspberry pi github. Work stopped last year on 3.2.27, so why are the patches not in kernel.org? I don't get this. I could post this to Raspberry pi, however my feeling is that I will not get a definitive answer. Perhaps I am misunderstanding how the process works. Please enlighten me.___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] armedslack on android phone?
On Jul 14, 2013 10:22 Davide louigi...@yahoo.it wrote: If the phone is an A1x based SOC there's chance that you can get started really quickly by reusing info on how I got Slackware arm on my XZPAD700 tables (that is a A13 based SOC). There's still work to do like the touchscreen and figuring out what kind of X server will work (probably a frame-buffer one) but it's booting and the frambuffer console is working. The documentation has not yet made it to the non officially supported platform list but I've documented my doings on http://docs.slackware.com/howtos:hardware:arm:hacking_the_xzpad700_7_t ablet. I've also a self sufficient image builder that I've tarballed into 63Mb but have no place to put the image on. This new image builder replaces the script I've put on docs.slackware.com and feautres dialog menus for choosing things like target soc,kernel,partition sizes and root image tarball. Stuart: what do you think about adding it to the list along with the AC100, Pandora and Pi ? Ciao David Da: Brian L Gorecki gore...@fastguys.net A: 'Slackware ARM port' armedslack@lists.armedslack.org Inviato: Sabato 13 Luglio 2013 15:30 Oggetto: Re: [ARMedslack] armedslack on android phone? The most straight forward answer would be no, the arm architecture used in that phone isn’t supported ‘out of the box’. However, with some work, kernel builds and patience probably can be done. See http://arm.slackware.com/supportedplatforms/ for a starting point. I’ve had the same thoughts for an old Motorola Q I have but so far haven’t deemed it worth the effort. From:ARMedslack [mailto:armedslack-boun...@lists.armedslack.org] On Behalf OfDennis Sent: Friday, July 12, 2013 1:39 PM To: armedslack@lists.armedslack.org Subject: [ARMedslack] armedslack on android phone? Hello all I have a motorola bionic phone with android JB. With it I have a webdock, which is basically a hdmi monitor with a usb mouse and keyboard. I use this fairly often and what I really miss is running linux as android is a modified version and just doesn't have the same look, feel, and functionality as a full linux system. I run slackware 14 on my home system, and when I found out slackware had this group I joined up. So far it looks like the rasp pi and simular computers are the target. Just wondering if anyone has ventured into the android phone area? I'm not sure if a dual boot would be possible? Or if it would have to run under the android shell as other linux distro's do. I haven't done much programming for a long time, but I do continue to use and play around with my linux machine at home. Been a slackware fan since 1992 or so and after trying some of the other distro's I found I prefer slackware still. Dual boot would be prefered, and I have found that the drivers for the phone are available thru android open source so just maybe this would be workable. I'm also looking to get a small computer like one of usb sticks I've seen to put the web on the TV, and am looking for any advice as to which would be the best for slackware/android combo. thanks Dennis ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack Slackware ARM is very generic and will run on an spectacular amount of devices. How you get it on to an unsupported device is the rub. I doubt that you can dual boot in the conventional sense as ARM devices don't use LILO as your desktop will. In fact most ARM systems boot differently, some use uboot, some yaffs. (Slackware ARM uses both inird and uboot). Some will use a propitiatory procedure that can only be guessed at. You will need a custom kernel compiled against your arch, you cant just use a slackware ARM kernel and expect it to work, it won't. Your open source drivers will have been compiled for android and will use the bionic libararys, Slackware will require that you recompile the drivers for glib. You could do this if you are prepared to put in the time, and fail, stomp your feet, try again until you succeed. Good luck!___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1
On Jun 13, 2013 21:39 Stuart Winter m-li...@biscuit.org.uk wrote: Ok I've changed it and will upload the new installers once I've got Linux 3.9.6 kernels built. Actually, can you test it? I just edited it and haven't tested it. It's really just cosmetic, so it should be fine: http://armed.slackware.com/tmp/armedslack-nofscheck It Should work but does not. may I suggest this line: if [ $( egrep versatile /proc/cpuinfo || egrep BCM2708 /proc/cpuinfo ) != -a -s $FSTAB ]; then found to work on both Raspberry Pi and ARM-Versatile. Many thanks ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1
On Jun 15, 2013 15:31 stanley garvey stan...@stanleygarvey.com wrote: On Jun 13, 2013 21:39 Stuart Winter m-li...@biscuit.org.uk wrote: Ok I've changed it and will upload the new installers once I've got Linux 3.9.6 kernels built. Actually, can you test it? I just edited it and haven't tested it. It's really just cosmetic, so it should be fine: http://armed.slackware.com/tmp/armedslack-nofscheck It Should work but does not. may I suggest this line: if [ $( egrep versatile /proc/cpuinfo || egrep BCM2708 /proc/cpuinfo ) != -a -s $FSTAB ]; then found to work on both Raspberry Pi and ARM-Versatile. Many thanks Better still if [ $( grep versatile\|BCM2708 /proc/cpuinfo ) != -a -s $FSTAB ]; then Also tested on Raspberry Pi and QEMU ARM-Versatile, I don't know why the alternation is being missed in egrep. My grep is version 2.14, am I out of date? ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1
On Jun 12, 2013 19:32 Stuart Winter m-li...@biscuit.org.uk wrote: read write. The Raspberry Pi does not honor the ro flag :( The only way round this is to use a hacked rc.S, Unless somebody has a better idea? Default it into the kernel: CONFIG_CMDLINE: On some architectures (EBSA110 and CATS), there is currently no way for the boot loader to pass arguments to the kernel. For these architectures, you should supply some command-line options at build time by entering them here. As a minimum, you should specify the memory size and the root device (e.g., mem=64M root=/dev/nfs). It's in 'Boot Options () Default kernel command string' compile it in and give it a go. Solved! thanks I've updated the new sysvinit-scripts package with the inittab change and I'll push out the changes soon. Great, Thank you very much! I wa We saw the good side and the bad side of cyclists today and I also got to read a poem from the 'Black Cab poet' Tue 11th Jun 2013 @ 7:07.58 - 1h 53m 18ss wondering if something similar could be done for '/usr/lib/setup/armedslack-nofscheck ' to make it more generic? ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1
On Jun 13, 2013 21:35 Stuart Winter m-li...@biscuit.org.uk wrote: We saw the good side and the bad side of cyclists today and I also got to read a poem from the 'Black Cab poet' Cool. How'd it go?! whoops, don't ya just hate it when that happens? :) Tue 11th Jun 2013 @ 7:07.58 - 1h 53m 18ss wondering if something similar could be done for '/usr/lib/setup/armedslack-nofscheck ' to make it more generic? Ok I've changed it and will upload the new installers once I've got Linux 3.9.6 kernels built. I'll test it, Thank you! ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1
On Jun 11, 2013 21:59 Stuart Winter m-li...@biscuit.org.uk wrote: stanleygarvey.com/slackwarearm_rpi/index.php and dropped the slackberry name, also I can report that slackware-current does not OK great. Download SlackwareArm for Raspberry Pi®. You're missing the capitalisation - ARM stands for Advanced (or 'Acorn' if you go back further) Risc Machines (or at least it used to in the early 90s - it's probably too cool for that now though ;-) ). I'll Correct that ( The whole section needs some polishing and rewriting) [..] As for issues with the Raspberry Pi, I don't see many, it has no real time clock, rc.S needs hacking to remove the annoying message, and inittab requires patching and that's about it. What message? is it from hwclock? Personally I just leave those kind of messages in place -it looks a bit ugly but at least it's a reminder that there is no hardware clock. No I meant the annoying message from rc.S about the rootFS being read write. The Raspberry Pi does not honor the ro flag :( The only way round this is to use a hacked rc.S, Unless somebody has a better idea? What needs to be modified in inittab? http://ftp.arm.slackware.com/slackwarearm/slackwarearm-current/source /a/sysvinit-scripts/sources/doinst.sh.openttyS0 Could the change be added into here? The less changes you have to keep adding in the better - especially when I'm already doing it for the others! yes! The Raspberry Pi uses ttyAMA0 could i Suggest: egrep -q Versatile /proc/cpuinfo /dev/null 21 || egrep -q BCM2708 /proc/cpuinfo /dev/null 21 \ sed -i '/^# Local serial lines:/ a\s0:12345:respawn:/sbin/agetty 115200 ttyAMA0 vt100' etc/inittab.new || \ sed -i '/^# Local serial lines:/ a\s0:12345:respawn:/sbin/agetty 115200 ttyS0 vt100' etc/inittab.new ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1
On Jun 8, 2013 08:12 Stuart Winter m-li...@biscuit.org.uk wrote: I got rid of the problem of eth0 - eth1 udev renamingon the images I create by using the slackware supported standard /etc/rc.d/rc.shutdown_local script to remove the70-persistent-net.rules file whenever a shutdown is run. Iuse it for a whole load of other stuff as well, but removing it on shutdown makes theimages I create portable across boxes. Check that you do not have udevd running twice. ps wwaxu --forest | grep udev may show that there are multiple udevd running, but they should be children of a single parent. This was the cause of the renaming problem in an earlier builds of Slackware (prior to 14.0 release, I think, or maybe even post 14.0) - udevd had been started independently twice in the boot sequence. This was fixed a long time ago so I'm wondering whether the installer or some packages you have are old. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack Thanks for thar Stuart. I now have a clue where to look. root@slackberry:~# ps wwaxu --forest | grep udev root 62 0.3 0.3 4232 1636 ? Ss 00:00 0:01 /sbin/udevd --daemon root 625 0.0 0.2 4228 1240 ? S 00:00 0:00 \_ /sbin/udevd --daemon root 627 0.0 0.2 4228 1164 ? S 00:00 0:00 \_ /sbin/udevd --daemon Cheers! ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1
On Jun 8, 2013 18:54 Stuart Winter m-li...@biscuit.org.uk wrote: Hi Stuart, I could own the master' image' if you would like. I could set aside some hours a week to administer fixes and such. Q. Would I create the base image myself or do you have one in mind? If I have only ever considered what would be appropriate in the mini root (which was essentially everything needed to have a working OS + some every day tools I needed in order to bootstrap new architectures). Normally people tend to ship minimal roots (check Fedora etc.) and the people can then download the packages they require. This has some obvious benefits such as it's faster to download, faster to upload, easier to maintain and people can use slackpkg or whatever to install the packages they want. Ovbviously if I was doing it, there'd just be an installer so I would not have to consider what to supply ;-) I'll leave it for you to decide. so do you think my modified Versatile-initrd is a good starting point? or should I start back with David Spencers installer? I would value your views on this. I have not looked at your initrd and I don't have a Rpi (if I did I'd have done the support myself). My two questions are: 1. - what are you modifying and why? For example, when I add a new architecture all I edit in the installer is the /etc/rc.d/rc.modules-arm. The generic installer is then built (actually it's the versatile one but I'm going to make it generic for Linux 3.10), and my scripts unpack it, determine what modules the versatile/generic installer has and replaces them with the versions for the particular architecture, then adds any arch-specific modules and finally wraps it up again. http://armed.slackware.com/scripts/mk-tegra.sh It's pretty ugly but it's simple. That's basically what I have done, but by hand. There is also a 'raspberrypi' directory containing a simple script that should be ran before rebooting from the installer to remove non raspberry pi kenels and kernel source, modify inittab, rc.S and set the config.txt to boot from rootfs. - I'll look at your mk-tegra script, thanks 2. - can any of your changes be merged back into the original installer? This is more of a rhetorical question ;-) That is more of a rhetorical question. I have changed as little as possible! Also, what name? I have been using Slackberry as short for 'slackwarearm on a raspberry pi' is this appropriate? I could register a domain for this. If you were turning it into a different product which was based on Slackware, then it makes sense to give it a different name. The only reason Slackware ARM was called 'ARMedslack' was because since I didn't really know Patrick in 2002, the web site said unofficial stuff shouldn't use the Slackware name, and so respectfully I gave it a separate name. However, the OS has *always* been Slackware but on the ARM architecture - apart from porting it and making necessary or particularly (what I think are) appropriate changes, it's the same product as x86. So the short answer is that I personally prefer 'Slackware ARM on a Raspberry Pi' because you're actually taking the same product but making it installable and runable on the Rpi. Okay, all my page titles start with SlackwareArm for the raspberry Pi' even if pointed to by 'Slackberry' I guess an installer wouldn't need its own domain. Cheers s.___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1
On Jun 7, 2013 22:32 Stuart Winter m-li...@biscuit.org.uk wrote: Hi Rick, [..] I'm probably not the person for anything too technical but I could most likely manage the wiki side of things if the learning curve is not too steep. I've contributed on other wikis in the past and could probably do what is required or at least have a go. [..] I was referring specifically to someone owning the 'master' RPi image rather than the wiki document (since anybody can update the wiki doc). I would like to see one master image/installer that has all of the fixes in it, and then have a wiki doc on docs.slackware.com with all of the appropriate information. An ARM section has now been created and I've moved the content of the INSTALL_RASPBERRYPI.TXT file into a wiki doc (the new version of this file just has the URL to the RPi wiki doc once I push out the next updates). http://docs.slackware.com/howtos:hardware:arm Feel free to add to or modify the docs. Hi Stuart, I could own the master' image' if you would like. I could set aside some hours a week to administer fixes and such. Q. Would I create the base image myself or do you have one in mind? If so do you think my modified Versatile-initrd is a good starting point? or should I start back with David Spencers installer? I would value your views on this. Also, what name? I have been using Slackberry as short for 'slackwarearm on a raspberry pi' is this appropriate? I could register a domain for this. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1
On May 30, 2013 08:34 stan...@stanleygarvey.com wrote:
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
http://www.slackware.com/~mozes
Slackware for ARM: http://arm.slackware.com
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
Hi Stuart
Judging by the avalanche of submissions, it would look I am alone in
supporting Slackware on the RPi - ( Hello! - cue hall type reverb and
tumbleweed).
However my site gets two or three hits a day regarding slackberry, so
somebody's interested.
The issue with udev renaming eth0 to eth1 is documented on the site. I
need to fix this but given to udevs labariynthine nature I may require
a ball of string. I may be some time.
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Strange problem installing Slackware 14.0 on the Raspberry Pi
On May 9, 2013 18:33 Michael Langfinger slackw...@langfinger.org 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/, 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@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Slackware ARM on Raspberry Pi
On May 2, 2013 13:27 Thorsten Mühlfelder thenk...@salixos.org wrote: rich@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@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Avatar S701-R2A-1 Sirius 7 Tablet
On Apr 15, 2013 20:46 Ben Bauer b...@bauers.ca wrote: http://www.comtronic.ca/cci/home.php?do=ShowProductscmd=detailcid=N Bpid=017133 CPU ARM Cortex-A9 1.0GHz Single Core GPU Mali-400, with 3D Accelerator Memory1GB DDR3 Storage 4GB NAND Flash Display 7 TFT-LCD ... I/O Ports 1 x Micro USB 2.0 Port 1 x Mini HDMI Port 1 x TF Card Slot 1 x Power Port Does anyone have experience with this (or similar hardware)? I am hoping to put Slackware native on this and move over some python programs (currently prototyped on an Atom processor) that I have written for classroom use ( audience response system, multiple choice testing, flashcards etc). I am a Slacker since 1994 but ARM is new to me. Naive questions: 1) any chance I can boot from CF card ? 2) if so, is a USB keyboard likely to autodetect? 3) would X be mulitouch or single? 4) is there a better/easier sub $100 device I should consider? ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack 4) Yes, consider using a raspberry pi, it is under $100 and runs slackwarearm debian arch and more. The raspberriy pi is a neat little arm computer that runs from CF card. It's not a tablet but can connect to tv's monitors and hdtv's.it needs a 5 volt 1 amp psu has no moving parts and no fan and yes it is ARM! ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Raspberry Pi Linux kernel versions for Slackware ARM 14.0
On Apr 11, 2013 08:40 Stuart Winter m-li...@biscuit.org.uk wrote: David spencers installer uses the 3.1.9 kernel, Sorinm's image is also using 3.1.9, I am using 3.2.27, I don't know of any kernels older that these. Some people use the Rpi-update script and so will be using v3.6 even if they started using v3.1. My 3.2.27 kernels are now built using your build scripts and no longer use the default name 'kernel.bin' and would be unaffected by Rpi-update. OK thanks - I've rebuilt glibc against 3.1.0 so as to allow a live upgrade from 14.0 to 14.1. It'd be nice to see some Rpi kernel upgrades to the latest release -- is the Rpi support not yet in the upstream kernels? I will have a look at kernel.org over the weekend to see if Rpi support is included. My feeling is that Rpi support will probably be included for v3.1 and 3.2 as active development has ceased for these versions on github. This is why I stuck with 3.2.27, kernel upgrades are frequent on github and v3.6.y is in constant flux at present. David Spencers site has not been updated since august last year and although Sorinms site seems to be active I note he is still using v3.1.9, Sorinm is also not a fan of the rpi-update script as it may silently break something. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Raspberry Pi Linux kernel versions for Slackware ARM 14.0
On Apr 10, 2013 14:38 Stuart Winter mo...@slackware.com wrote: Hi When I bumped the minimum kernel version required by glibc to Linux 3.4.0, I'd checked the Raspberry Pi stuff and believed that the Raspberry Pi's had a mimimum of Linux Kernel v3.6 available. From what I can see now, it looks like some of the RPi images are using Linux 3.1. Is there anyone who's distributing anything that's older than this version? It looks like I'll need to respin glibc to change the mimimum kernel to be 3.1.0 so that RPi users can upgrade to Slackware ARM 14.0 to 14.1. Hello, David spencers installer uses the 3.1.9 kernel, Sorinm's image is also using 3.1.9, I am using 3.2.27, I don't know of any kernels older that these. Some people use the Rpi-update script and so will be using v3.6 even if they started using v3.1. My 3.2.27 kernels are now built using your build scripts and no longer use the default name 'kernel.bin' and would be unaffected by Rpi-update. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Quick question
On Mar 31, 2013 23:03 Ottavio Caruso ottavio2006-usenet2...@yahoo.com wrote: On the other hand if you release a new rootfs say every month, all that a smart user has to do is umount /home and untar the new rootfs over the old one and some post install cleanup. Alternatively they can be educated to update properly. snip 1) That would be a lot of work and .. 2) You assume the user is smart, Slackware is K.I.S.S. for a reason. 3) Education is not an exact science. 4) Installers provide a uniform experience. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Can't slackpkg update to latest jre/jdk
On Feb 20, 2013 22:11 stanley garvey stan...@stanleygarvey.com wrote: On Feb 20, 2013 21:08 openpand...@free.fr wrote: Hi ! I have both packages installed, slackpkg mirror is pointing to ftp://ftp.armedslack.org/slackwarearm/slackwarearm-14.0/ slackpkg update works, the /tmp/xxx/Changelog is ok, but the upgrade-all won't upgrade to the newer jdk/jre. They're not blacklisted. Any reason to this ? Maybe it's because they were added directly to /patches without having be in /slackware/d/ first ? ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack Try Installpkg, I don't think these packages where present on release of 14.0. My understanding is that they where added to patches after slackwarearm-14.0 was released. regards. PS is that a GP32x ? ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Install Slackware on a new Raspberry Pi
On Feb 4, 2013 21:58 rou...@mm.di.uoa.gr wrote: stanley garvey wrote: On Feb 3, 2013 19:33 stanley garvey stan...@stanleygarvey.com wrote: On Feb 3, 2013 18:51 Andrei B. andrix...@yahoo.com wrote: My experience so far , as I also have the model B (512ram) is like this: - raspbian or weezy works fine. Note that they were from october 2012, after the launch of the mode B. Dave's image (so far) for slackware is dated august 2012. Using Dave's image and start.elf from the raspbian image, I managed to start the installer (set for only 128MB ram) and do a complete installation, on my 16G image. However, I couldn't start the system after installation, with the installed kernel, following all of Dave's instructions. I'm still researching with Stanley's site. I'll probably bring up my own site, to document these experiences. I think is super cool that Slackware exists as full distro, just like the x86 version, for ARM. I still have to try (tomorrow, maybe) Stanley's already installed images. --- On Sun, 2/3/13, rou...@mm.di.uoa.gr rou...@mm.di.uoa.gr wrote: From: rou...@mm.di.uoa.gr rou...@mm.di.uoa.gr Subject: Re: [ARMedslack] Install Slackware on a new Raspberry Pi To: Philippe Tjon-A-Hen pnmtjona...@gmail.com Cc: armedslack@lists.armedslack.org Date: Sunday, February 3, 2013, 10:01 AM Philippe Tjon-A-Hen wrote: Found this site yet ? http://rpi.fatdog.eu/?p=home Yes I have already been there, thanks for the suggestion. My problem is that I cannot start the installer (rainbow screen). Is there anything particular at this site that I should be paying more attention to? -Stathis Op 3 feb. 2013 03:12 schreef rou...@mm.di.uoa.gr rou...@mm.di.uoa.gr /mc/compose?to=rou...@mm.di.uoa.gr het volgende: Hi all, first of all, thanks to everyone here for the wonderful work. Keep it up! Just got my Pi (model B, 512MB) and tried the raspian-wheezy (2012-12-16) first and it works fine. Followed instructions from Dave's Collective (http://www.daves-collective.co.uk/raspi/installing.shtml ) and prepared two SD cards, a 8GB and a 32GB. Unfortunately, with either of the cards, all I get is the rainbow screen. How does one proceed from that? -Stathis ___ ARMedslack mailing list ARMedslack@lists.armedslack.org /mc/compose?to=ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack Hi, please use the 16 GB image, it is cleaner and has an issue with networking fixed. You can use the 8GB image but read issues and workarounds on my site first! Finally I used the 16GB image and booted fine. Well done Stanley! Thanks for the port. [...snip...] -Stathis Good news Stathis, the port is Stuart winters,I only made the image. Best regards Stanley ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Install Slackware on a new Raspberry Pi
On Feb 3, 2013 19:33 stanley garvey stan...@stanleygarvey.com wrote: On Feb 3, 2013 18:51 Andrei B. andrix...@yahoo.com wrote: My experience so far , as I also have the model B (512ram) is like this: - raspbian or weezy works fine. Note that they were from october 2012, after the launch of the mode B. Dave's image (so far) for slackware is dated august 2012. Using Dave's image and start.elf from the raspbian image, I managed to start the installer (set for only 128MB ram) and do a complete installation, on my 16G image. However, I couldn't start the system after installation, with the installed kernel, following all of Dave's instructions. I'm still researching with Stanley's site. I'll probably bring up my own site, to document these experiences. I think is super cool that Slackware exists as full distro, just like the x86 version, for ARM. I still have to try (tomorrow, maybe) Stanley's already installed images. --- On Sun, 2/3/13, rou...@mm.di.uoa.gr rou...@mm.di.uoa.gr wrote: From: rou...@mm.di.uoa.gr rou...@mm.di.uoa.gr Subject: Re: [ARMedslack] Install Slackware on a new Raspberry Pi To: Philippe Tjon-A-Hen pnmtjona...@gmail.com Cc: armedslack@lists.armedslack.org Date: Sunday, February 3, 2013, 10:01 AM Philippe Tjon-A-Hen wrote: Found this site yet ? http://rpi.fatdog.eu/?p=home Yes I have already been there, thanks for the suggestion. My problem is that I cannot start the installer (rainbow screen). Is there anything particular at this site that I should be paying more attention to? -Stathis Op 3 feb. 2013 03:12 schreef rou...@mm.di.uoa.gr /mc/compose?to=rou...@mm.di.uoa.gr het volgende: Hi all, first of all, thanks to everyone here for the wonderful work. Keep it up! Just got my Pi (model B, 512MB) and tried the raspian-wheezy (2012-12-16) first and it works fine. Followed instructions from Dave's Collective (http://www.daves-collective.co.uk/raspi/installing.shtml) and prepared two SD cards, a 8GB and a 32GB. Unfortunately, with either of the cards, all I get is the rainbow screen. How does one proceed from that? -Stathis ___ ARMedslack mailing list ARMedslack@lists.armedslack.org /mc/compose?to=ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack Hi, please use the 16 GB image, it is cleaner and has an issue with networking fixed. You can use the 8GB image but read issues and workarounds on my site first! The 16GB image has a prettier boot partition and include the full config.txt file from elinux with every config parm you can think of. Both images are based upon the work of David Spencer but contain no tweeks or optimizations. You can use the image as an installer by uncommenting these lines in config.txt: ## ramfsfile (string) ## ramfs file to load ## #ramfsfile=intrd-versatile.img --uncomment (line 493) ## ramfsaddr ## Address to load ramfs file at ## #ramfsaddr=0xa0 --uncomment (line 498) If you chose to reinstall this way be mindful that you will lose the kernel modules and source, so move them some place safe first. The installation steps are the same as Davids, however no extra packages exist. I would like to write an installer but my partner says I spend to much time on this already, plus I've been working 7 days a week :( You can also find a bunch of natively rebuilt packages at ftp.stanleygarvey.co.uk most of series a has been rebuilt all of series xfce and more, take a look. If you wish to use these packages you can do so by using the command : upgradepkg --reinstall somepackage-*arm*tgz I hope that helps, comments to slackberry(at)stanleygarvey.com Best regards Stanley. P.S you will need to comment out the lines you uncommented above in the config.txt or you will reboot back into an install, I shouldn't need to tell you that, but just to be clear. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Install Slackware on a new Raspberry Pi
On Feb 3, 2013 20:17 Gregg Levine gregg.drw...@gmail.com wrote: On Sun, Feb 3, 2013 at 2:52 PM, stanley garvey stan...@stanleygarvey.com wrote: On Feb 3, 2013 19:33 stanley garvey stan...@stanleygarvey.com wrote: On Feb 3, 2013 18:51 Andrei B. andrix...@yahoo.com wrote: My experience so far , as I also have the model B (512ram) is like this: - raspbian or weezy works fine. Note that they were from october 2012, after the launch of the mode B. Dave's image (so far) for slackware is dated august 2012. Using Dave's image and start.elf from the raspbian image, I managed to start the installer (set for only 128MB ram) and do a complete installation, on my 16G image. However, I couldn't start the system after installation, with the installed kernel, following all of Dave's instructions. I'm still researching with Stanley's site. I'll probably bring up my own site, to document these experiences. I think is super cool that Slackware exists as full distro, just like the x86 version, for ARM. I still have to try (tomorrow, maybe) Stanley's already installed images. --- On Sun, 2/3/13, rou...@mm.di.uoa.gr rou...@mm.di.uoa.gr wrote: From: rou...@mm.di.uoa.gr rou...@mm.di.uoa.gr Subject: Re: [ARMedslack] Install Slackware on a new Raspberry Pi To: Philippe Tjon-A-Hen pnmtjona...@gmail.com Cc: armedslack@lists.armedslack.org Date: Sunday, February 3, 2013, 10:01 AM Philippe Tjon-A-Hen wrote: Found this site yet ? http://rpi.fatdog.eu/?p=home Yes I have already been there, thanks for the suggestion. My problem is that I cannot start the installer (rainbow screen). Is there anything particular at this site that I should be paying more attention to? -Stathis Op 3 feb. 2013 03:12 schreef rou...@mm.di.uoa.gr het volgende: Hi all, first of all, thanks to everyone here for the wonderful work. Keep it up! Just got my Pi (model B, 512MB) and tried the raspian-wheezy (2012-12-16) first and it works fine. Followed instructions from Dave's Collective (http://www.daves-collective.co.uk/raspi/installing.shtml) and prepared two SD cards, a 8GB and a 32GB. Unfortunately, with either of the cards, all I get is the rainbow screen. How does one proceed from that? -Stathis ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack Hi, please use the 16 GB image, it is cleaner and has an issue with networking fixed. You can use the 8GB image but read issues and workarounds on my site first! The 16GB image has a prettier boot partition and include the full config.txt file from elinux with every config parm you can think of. Both images are based upon the work of David Spencer but contain no tweeks or optimizations. You can use the image as an installer by uncommenting these lines in config.txt: ## ramfsfile (string) ## ramfs file to load ## #ramfsfile=intrd-versatile.img --uncomment (line 493) ## ramfsaddr ## Address to load ramfs file at ## #ramfsaddr=0xa0 --uncomment (line 498) If you chose to reinstall this way be mindful that you will lose the kernel modules and source, so move them some place safe first. The installation steps are the same as Davids, however no extra packages exist. I would like to write an installer but my partner says I spend to much time on this already, plus I've been working 7 days a week :( You can also find a bunch of natively rebuilt packages at ftp.stanleygarvey.co.uk most of series a has been rebuilt all of series xfce and more, take a look. If you wish to use these packages you can do so by using the command : upgradepkg --reinstall somepackage-*arm*tgz I hope that helps, comments to slackberry(at)stanleygarvey.com Best regards Stanley. P.S you will need to comment out the lines you uncommented above in the config.txt or you will reboot back into an install, I shouldn't need to tell you that, but just to be clear. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack Hello! Stanley you're saying to boot into a normal Slackware screen as opposed to the installer based ramdisk I need to uncomment those lines that're commented out? I had an inspired guess regarding that, but, ah, never had a chance to try it Now you've got me confused, try it it's one way or the other, if you find yourself going round in a loop then you've got it wrong. Bless g'night Stanley ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http
Re: [ARMedslack] Mystery Prefixes
On Feb 1, 2013 18:04 Stuart Winter m-li...@biscuit.org.uk wrote: Can anyone explain the mystery prefixes on Firefox and Seamonkey? Most Slackware arm packages have the usual blah-*arm*tgz, however mozilla-firefox has the mysterious armv6j prefix. The slackbuild shows only -march armv5te? ftp://ftp.arm.slackware.com/slackwarearm/unsupported/slackwarearm-curr ent/source/mozilla-firefox/mozilla-firefox.SlackBuild The -march is set to armv6j in the build script. The script you're looking at was not used to build the package .tgz you're looking at. Seamonkey has the prefix armhfp- I have not checked the slackbuild, but that would suggest hardware floating point. Could some one explain. Your confused, Yes it's named 'hfp' for that reason which is mentioned in the build script (at least in -current, but maybe not for 14.0). However, there's some confusion on my part about what actually required an HFP unit and what didn't because ISTR that during various Mozilla releases (of all of the apps), at some stages I found info that led me to conclude that the newer versions had instructions for, and only ran on systems with an FPU; and other times it was due to the NEON extensions in (I think) armv7 machines. That made sense until someone told me that the same packages I thought were armv7 only, also ran on the armv6 Raspberry Pi. To conclude, I don't really know apart from anything named 'armv6j' really was built for -march=armv6j. Anything named 'hfp' definitley needs a machine with a HFPU, but may or may not also contain the armv7 NEON instructions. Needless to say I am pleased to have dropped Mozilla. What a ball ache that thing was with every release. -- - Okay, It was me that was confused. I think you can use Hardware FP in any application so long as the application uses its own private library's, and that is what I thought was happening, as SlackwareARM supports devices without a HFPU I could not figure it out. Looks like Firefox might rebuild natively on a raspberry pi after all (day two, I kid you not!). I have put all my builds up on my ftp site if any one is interested, they can be used as overlays upgradepkg --reinstall someapplication-*tgz Best regards Stanley, ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] First boot on Raspberry PI for Slackware 14.0 for ARM
On Jan 26, 2013 01:05 Dave Dowell dowe...@netscape.net wrote: On 25/01/2013 23:34, Gregg Levine wrote: Hello! Okay group I just brought up the Slackware 14.0 for the Raspberry pi image available on Stanley Garvey's site. Aside from one nit, the device almost arbitrarily changed the eth0 setting to eth1 for reasons it did not clearly explain. Everything worked correctly from that one on. However how do I go about changing from UK keyboard to something resembling a US one? In this case Stanley I borrowed my screen from a (what else?) system running Slackware-13.37 and connected to it the HDMI cable via a HDMI-DVI adapter that I bought today. Earlier I also bought an 8 Gigabyte card on sale from Staples and used an image writing tool from that system to write things out. And then connected everything from there. It came up exactly as expected. Except for that one nit concerning the Ethernet device swap. I once saw that happen on an Intel system I was trying to revive and knew where to fix things. But here? No I don't. I have the installer based image that David Spencer made up and with that and the screen I'll probably create a more customized one. The one strange thing is why would things swap names for the Ethernet one? But otherwise it is all good. - Gregg C Levine gregg.drw...@gmail.com This signature fought the Time Wars, time and again. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack Is there a udev rule left on the image from the installation system, check in /etc/udev/rules.d and see if the 70-persistent-net.rules files has an entry for the eth0 hardware address from the install system. If there is you can just delete that file and the system will recreate it next time it boots, with your device (MAC address) listed as the eth0 device. Thanks Dave ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack Hi, Great to hear you got the image to boot! I have known about this issue for a while, I missed it when testing the images because I was swapping the cards between boards and assumed that udev was just picking up on a new mac address. I all ways remove /etc/udev/rules.d/70-persistent-net.rules and the ssh keys when making an image. The culprit here is /etc/rc.d/rc.wireless chmod -x /etc/rc.d/wireless rm /etc/udev/rules.d/70-persistent-net.rules reboot Should fix it. Sorry about that. I will make some new images with this fixed and a prettier boot partition soon. regards Stanley ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] First boot on Raspberry PI for Slackware 14.0 for ARM
On Jan 26, 2013 17:28 Gregg Levine gregg.drw...@gmail.com wrote: Hello! Thanks. As it happens I typed that out in a hurry. I bought a 16, which I did write out your image to. I'm going to leave that image on it, and work out how to reset the keyboard settings. (Even if I end up importing the keyboard management tools from 13.37 or earlier via source code files.) I'll probably pick up the same card and try again with the installer image since it also complained about space sizing. - Hi, I don't know about keyboard management tools? see http://docs.slackware.com/howtos:window_managers:keyboard_layout that might help. If you are new to Slackware you should read these great texts: http://code.google.com/p/slackbasics-i18n/ http://slackbook.org/ They where written a while ago, however Slackware does not change that much. (Thankfully). I don't understand about David Spencers installer complaining about space sizing? Do you mean the software you are using to burn the image? It's intended that you use fdisk or cfdisk to remove the last partition and recreate it using the total space remaining on the sdcard. It's a great idea, I fell into the trap of putting the swap partion at the end of the drive in the superstitious belief that the seek times are higher at the end of a hard drive. I have no empirical evidence to support this and an sdcard is solid state anyway. Good luck and best regards. Stanley ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] BCM2835 what -march to use?
On Jan 19, 2013 16:13 Stuart Winter m-li...@biscuit.org.uk wrote: btw for clarification when I say cross compiling, I mean cross compiling proper - building entirely on a machine other than the target. What I do with distcc is *building* natively, with *some* of the code being compiled on a host that happens to be an x86 with the exact same toolchain as natively. There are only prisere [slackwarearm-current] # find . -type f -name '.no*distcc*' | wc -l 26 That aren't built with distcc, as they fail for what ever reason, but build natively. Can you sort out your mail client? I'm not sure what's happened here - you have replied to a mail that you never sent? It's taxing my poor brain for moments in order to determine what you're quoting and what's fresh. [..] using -march=armv6j. I prefer to compile nativley, however mozilla-firefox compiled for 3 days the got stuck with ld in deep sleep 98%wait. so I might want to x-compile that one. Thanks for the great slackit! I don't cross compile it and it works for me - takes an hour or less to build, IIRC. Perhaps you don't have enough RAM on your machine? Sorry about The Email client, it's web based, and very poor, I run my own mail server and prefer mutt, but Sorbs have blocked me : Name: Stanley Garvey IP/Host: 81.111.128.0/17 IP: 81.111.194.105 DNS: NXDOMAIN DNS TTL: -1 DNS Info is cached: No Additional Information: My response: Remove 81.111.128.105 from your database. I run my own mail-server. You have no legal right to blacklist this address. please provide reasons for blacklisting this address. Thank you. Anyway still rebuilding your packages for armv6j -mpu=vfp -mfloat-abi=softfp -mtune=arm1176jzf-f. can't get aspell to compile, Needed to patch fuse with #define _GNU_SOURCE. Also needed to upgrade to /a/usbutils.006 as source not in slackware64 Kind regards. Stanley ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images
Snip! Hello! Interesting thought. So what did you use for both making your images? And then writing them to SD cards? OKay, I followed David Spencers suggestion for the SD-card format, see also this article https://lwn.net/Articles/428584/ I then recompiled a Raspberry-pi Kernel with initrd support as the stock kernels do not come with initrd support enabled by default, bit of a bodge, then saved the kernel modules and kernel source elsewhere as the modules will be overwritten by the install. rebooted and did a regular install over nfs. copyed back the kernel source, did make _modules_install. To recreate the modules, Put the Kernel source in /usr/src/kernel-whatever made the historic symlink to it ln -s /usr/src/kernel-whatever Removed the shh keys in /etc/ssh Both Public and Private (You dont't what my keys) Remove /etc/udev/70-persistent.net-rules dd if=/my/image of=/myfilename Does that help? Regards Stanley. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images
On Jan 7, 2013 15:03 Gregg Levine gregg.drw...@gmail.com wrote: On Mon, Jan 7, 2013 at 3:54 AM, stan...@stanleygarvey.com wrote: Hi Gregg Sounds like the image is corruped I will chk whn bck frm wrkM Did you see a krnel Panic? Can you mount the sdcard on your linux pc and see the ext4 fs? Refmt in digital camera Sent from my BlackBerry smartphone from Virgin Media -Original Message- From: Gregg Levine gregg.drw...@gmail.com __ snip - Hello! Yes to the first three. But no to the last. No camera here who uses those things. - Gregg C Levine gregg.drw...@gmail.com This signature fought the Time Wars, time and again. Gregg, I have just downloaded SlackwareArm-14.0-8GB-20121201.zip unzipped it re-flashed to a sandisk 8GB class 4 card like so: bash-4.1# dd if=SlackwareArm-14.0-8GB-20121201.img of=/dev/sdc bs=65536 123056+0 records in 123056+0 records out 8064598016 bytes (8.1 GB) copied, 1862.39 s, 4.3 MB/s (your /dev/sd?) will depend on your set up) It booted fine. I can't reproduce the error. I had suspected that I had got the /boot/cmdline.txt wrong, but it is correct Can you give me more details, what does the kernel say? Did you download it from stanleygarvey.com/Slackberry/download.php or via rsync or ftp (the files should all be identical). regards Stanley. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images
On Jan 7, 2013 20:15 Gregg Levine gregg.drw...@gmail.com wrote: On Mon, Jan 7, 2013 at 2:29 PM, stanley garvey stan...@stanleygarvey.com wrote: On Jan 7, 2013 15:58 Gregg Levine gregg.drw...@gmail.com wrote: On Mon, Jan 7, 2013 at 10:55 AM, stanley garvey stan...@stanleygarvey.com wrote: On Jan 7, 2013 15:03 Gregg Levine gregg.drw...@gmail.com wrote: On Mon, Jan 7, 2013 at 3:54 AM, stan...@stanleygarvey.com wrote: Snip Hello! I think from Rsync function. I'll retrieve it again and from your website. I'll know more later. Hi, just checked all files are identical: bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip 1dd852334977d734e5ff833ecacface9 SlackwareArm-14.0-8GB-20121201.zip (local copy) bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip 1dd852334977d734e5ff833ecacface9 SlackwareArm-14.0-8GB-20121201.zip (Danish server powered by windmills) Suggest you re-download the zip file and do: md5sum SlackwareArm-14.0-8GB-20121201.zip to check integrity. regards Stanley. Hello! Now it is getting baroque, I just ran the command against both a new file (downloaded today) and one that did cause the problems. The command returns the same hash codes. I'll try again momentarily. - Gregg C Levine gregg.drw...@gmail.com This signature fought the Time Wars, time and again. Blimey, I like baroque, somethings obviously baroque, but I cant think what it can be, if you live in Warwickshire I would cycle around and fix it for you! I Guess you don't? are you confusing a kernel panic will the annoying message from Pat regarding the file system being read/write? try pressing enter. With kind regards, Stanley. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images
On Jan 7, 2013 20:37 Gregg Levine gregg.drw...@gmail.com wrote: On Mon, Jan 7, 2013 at 3:31 PM, stanley garvey stan...@stanleygarvey.com wrote: On Jan 7, 2013 20:15 Gregg Levine gregg.drw...@gmail.com wrote: On Mon, Jan 7, 2013 at 2:29 PM, stanley garvey stan...@stanleygarvey.com wrote: On Jan 7, 2013 15:58 Gregg Levine gregg.drw...@gmail.com wrote: On Mon, Jan 7, 2013 at 10:55 AM, stanley garvey stan...@stanleygarvey.com wrote: On Jan 7, 2013 15:03 Gregg Levine gregg.drw...@gmail.com wrote: On Mon, Jan 7, 2013 at 3:54 AM, stan...@stanleygarvey.com wrote: Snip Hello! I think from Rsync function. I'll retrieve it again and from your website. I'll know more later. Hi, just checked all files are identical: bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip 1dd852334977d734e5ff833ecacface9 SlackwareArm-14.0-8GB-20121201.zip (local copy) bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip 1dd852334977d734e5ff833ecacface9 SlackwareArm-14.0-8GB-20121201.zip (Danish server powered by windmills) Suggest you re-download the zip file and do: md5sum SlackwareArm-14.0-8GB-20121201.zip to check integrity. regards Stanley. Hello! Now it is getting baroque, I just ran the command against both a new file (downloaded today) and one that did cause the problems. The command returns the same hash codes. I'll try again momentarily. - Gregg C Levine gregg.drw...@gmail.com This signature fought the Time Wars, time and again. Blimey, I like baroque, somethings obviously baroque, but I cant think what it can be, if you live in Warwickshire I would cycle around and fix it for you! I Guess you don't? are you confusing a kernel panic will the annoying message from Pat regarding the file system being read/write? try pressing enter. With kind regards, Stanley. Hello! I see your point. I really do. This is indeed a kernel panic as the system starts to panic when it can't find and mount the root file system. Not the classic one regarding the file system being read/write. But I'll try again and see what happens next. - Gregg C Levine gregg.drw...@gmail.com This signature fought the Time Wars, time and again. OK I.m going to put a cold poltice on my forehead and retire, listening to Bach's fantasia and fuge in D minor. good night and good luck ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Upset regarding raspberry pi - unsuported.-Opinion
On Dec 25, 2012 17:19 Stuart Winter m-li...@biscuit.org.uk wrote: the Raspberry Pi Foundation go and do? they create a raspberry pi store with Debian (Raspiean app store or what ever). enough already, I want my children to lean how to programme, not how to download the latest app. I don't see any issue, myself. [..] Also, it just occurred to me that an App Store isn't much different from a big 5.25 floppy disk containing loads of BASIC programs you could load in and run. The concepts are the same, just the name and the format changes. Guess I was just trolling, I was having a lack of faith, I was not sure how a 9/10 year old would take to running Slackware. I wanted the children to use Slackware because I use Slackware, but time was running short. and I did not think I had it right for a 9/10 year old child, so I thought 'hey why not just load the Rpi debian image?', checking the website I wrongly assumed they had gone commercial. This was further fueled by the conversation I had with my partner concerning lock ins and proprietary software ( iPods/kindles/android devices). My nephew is delighted with his RC helicopter, and the Boy wants only his XBox, the girl, however can't wait to write stories on the new computer . Now I have to teach her Vi. Happy Christmas and a fantastic new year. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] QEMU support - does anybody care about it?
On Sep 5, 2012 14:38 Stuart Winter m-li...@biscuit.org.uk wrote: Yeah, I'd miss it too... I still use qemu with its snapshot feature to build packages on a clean installation. My real ARM hardware has too many packages installed to consider it a clean installation. I had a look and realised that to remove all the references to Versatile, and test the packages and installer would take more effort and time than to build the kernels and test it once or twice a year, so I'll leave them there. Thank you. QEMU is a very useful tool. Without QEMU I would not have been able to get SlackwareArm up and running on a Raspberry pi before a proper installer existed. What would have been an impossible task was made trivial with the QMEU support. Thank you for all your hard work supporting Slackware on Arm. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Slackware ARM current directory name is being changed - Mon 27th August
On Aug 28, 2012 22:11 Stuart Winter m-li...@biscuit.org.uk wrote: #from : rsync -avz --delete $mirror::armedslack/slackware-$system/patches/packages/ packages-$system #to : #rsync -avz --delete $mirror::slackwarearm/slackware-$system/patches/packages/ No because this never worked ;-) For all existing releases, the dirs are named armedslack-$version not slackware-$version, so your original rsync line wouldn't have worked. The directory names for -current and -14.0 are slackwarearm-$version. Heh, Yes, the script is simple, as is the author. Its from an x86 box. I plan to use it on Slackware arm. Perhaps it will need to be more elaborate. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Slackware ARM current directory name is being changed - Mon 27th August
On Aug 27, 2012 22:15 stanley garvey stan...@stanleygarvey.com wrote: On Aug 25, 2012 23:30 Stuart Winter m-li...@biscuit.org.uk wrote: In addition, the root directory on the FTP site the rsync module name will also change as below: FTP: ftp.armedslack.org/armedslack becomes ftp.armedslack.org/slackwarearm rsync: ftp.armedslack.org::armedslack becomes ftp.armedslack.org::slackwarearm Cheers s. _ So I need to change : # For: Slackware-13.37. Should work on all previous versions # Descr: Upgrades to patched/fixed/upgraded packages via rync mirror # URL: http://www.stanleygarvey.com/ # Needs: slackware public key: http://www.slackware.com/gpg-key # Changelog: mirror=rsync.slackware.org.uk cd /root system=`cut -d -f2 /etc/slackware-version | cut -d. -f1-2` echo Found Slackware-$system, getting upgraded packages from $mirror #from : rsync -avz --delete $mirror::armedslack/slackware-$system/patches/packages/ packages-$system #to : #rsync -avz --delete $mirror::slackwarearm/slackware-$system/patches/packages/ packages-$system cd packages-$system for f in *.t*z do echo Verifying $f gpg -q --verify $f.asc $f if [ $? == 0 ]; then echo Passed upgradepkg $f else echo failed fi done ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Hello and questions about getting Slackware on the Raspberry Pi
On Jul 11, 2012 23:43 Doug Peterson galen...@gmail.com wrote: Thank you. I am rsyncing this now. Will give it a try. -Doug On Wed, Jun 20, 2012 at 6:42 PM, stanley garvey stan...@stanleygarvey.com wrote: I have an 8gb img Get it via: rsync -avz --delete rsync.stanleygarvey.co.uk::SlackBerry/Image . This is the whole armed slack for an 8 GB sd sandisk card sans KDE. Sorry it's not zipped, it is very late. instructions: dd bs=1M if=Slacberry_8GB.img of=/dev/your_sd_card (most likley sdc) check with mount! don't wipe your hard drive. see rsync -avz rsync.stanleygarvey.co.uk::SlackBerry Thanks for trying it out Doug. Please replace or edit the file /etc/fstab with : /dev/mmcblk0p3 swap swap defaults 0 0 /dev/mmcblk0p2 / ext4 defaults 1 0 /dev/mmcblk0p1 /boot vfat defaults 0 0 #/dev/cdrom /mnt/cdrom auto noauto,owner,ro 0 0 #/dev/fd0 /mnt/floppy auto noauto,owner 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 proc /proc proc defaults 0 0 tmpfs /dev/shm tmpfs defaults 0 0 I messed up and forgot to change this file in the image, oddly the pi boots with an incorrect /etc/fstab anyhow. Some Caveats. the boot will stop with an annoying message regarding the root file system being RW, just continue by hitting enter. You can hack the script /etc/rc.d/rc.S if you like, I chose not to. The Pi has no real time clock and starting the ntp daemon does not set the time, the ntpdate command will set the time example: ntpdate ntp.stanleygarvey.co.uk I have not investigated why this occurs. I did not think that there was much interest in the image and so had not updated it. I have a couple of slackbuilds that I will upload, this weekend: A script by Hexxeh to update the raspberry pi kernel and firmware also two librarys to enable the use of the hardware accelerated video player 'omxplayer'. Let me know how you get along. Regards Stanley ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] libflashplayer
On Jul 4, 2012 18:47 Thorsten Mühlfelder thenk...@gmail.com wrote: Am Wed, 4 Jul 2012 14:51:29 +0100 (BST) schrieb Davide louigi...@yahoo.it: why the hell should one use flash for authentication on a web site (on some sites if you don't have flash you cannot even see the box for typing the authentication) ! I've never seen that and actually it's kind of funny nowadays. I guess the webmaster does not want to have many users? :-D The mobile phone/tablet market is growing every day and neither iOS nor recent Android is meant to run flash. Flash is already dead. Its hulking corpse seemingly animated only by the inertia of its ubiquitous web presence. In a diverse client environment Adobe has lost their way. The Web works just fine with out flash. It's now down to content providers to provide content that does not require a proprietary plugin. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] libflashplayer
On Jul 1, 2012 13:58 Stuart Winter m-li...@biscuit.org.uk wrote: available in source code I don't see why people can assume one can just drop libflashplayer.so for Android and expect it to work and even if it did you'd open a can of worms. It is a can of worms. It is closed source and lets hope it's finished. Adobe don't fully support it and have publicly said so. It does work - I tested it. I suspect it doesn't work for Davide because the library is compiled for a CPU higher than his own. This is what I ran it on: I am a pragmatist, if it works use it. Still hoping the web goes HTML5, MP4, OGG. Steve Jobs may have had a point. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Hello and questions about getting Slackware on the Raspberry Pi
On Jun 20, 2012 09:07 Stuart Winter m-li...@biscuit.org.uk wrote: I have an 8gb img Get it via: rsync -avz --delete rsync.stanleygarvey.co.uk::SlackBerry/Image . This is the whole armed slack for an 8 GB sd sandisk card sans KDE. Sorry it's not zipped, it is very late. instructions: dd bs=1M if=Slacberry_8GB.img of=/dev/your_sd_card (most likley sdc) check with mount! don't wipe your hard drive. see rsync -avz rsync.stanleygarvey.co.uk::SlackBerry For a listing os the other files.\good night :) ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] nfs and qemu install
On Jun 14, 2012 21:59 Stuart Winter m-li...@biscuit.org.uk wrote: X will require building xf86-video-fbdev, and you will need to get an xorg.conf from a running pi. I'm not sure why people say this -- this package is in Slackware ARM and always has been. My mistake. I should have said X needs xf86-video-fbdev and requires an xorg.conf from a running pi. Reason,I was looking at source/ x/X11/build/package-blacklist on a x86 dvd. # We don't want this one, as it causes failure of X with no xorg.conf xf86-video-fbdev Off topic. Nice to see people want armed slack on a Raspberry pi, I don't use Debian, Arch is better. I don't get apt-get and I don't want my dep's solved by a pacman. The Rpi is an educational computer. The kids will be getting one each for Christmas and I want them running slackware. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] nfs and qemu install
On Jun 13, 2012 09:59 Rick Miles frmr...@aapt.net.au wrote: On Tue, 2012-06-12 at 14:40 +1000, Rick Miles wrote: Qemu-install.txt just says Choose '3 - Install from NFS (Network Filesystem)' I plan on eventually running this on a raspberrypi :) Cheers Hi, the Qemu-install.txt is quite old and you may save yourself some headaches by using VDE. see: alien.slackbook.org/dokuwiki/doku.php?id=slackware:vde This is how I Installed armed slack on qemu. compile and install vde use a script like this to set up networking: (As root) #!/bin/bash modprobe tun echo 1 /proc/sys/net/ipv4/ip_forward iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE vde_switch -tap tap0 -daemon chmod -R a+rwx /var/run/vde.ctl ifconfig tap0 192.168.2.1 broadcast 192.168.2.255 netmask 255.255.255.0 This give me a subnet 192.168.2.?? for virtual machines, My router is 192.168.0.1 and my host machine is on 192.168.0.3. here is the host routing table after executing the above script (man route) Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.2.0 * 255.255.255.0 U 0 0 0 tap0 localnet * 255.255.255.0 U 0 0 0 eth0 loopback * 255.0.0.0 U 0 0 0 lo default 192.168.0.1 0.0.0.0 UG 1 0 0 eth0 To install armedslack on qemu I do this: make a directory for your VM, and in that directory make some subdirs, HardDrive, CDROM, Images. create a raw disk image in HardDrive using dd. copy needed initrd's to images and create an iso of the armedslack distro with mkisofs (no need to be bootable). then run an install script like this one: #!/bin/bash # install armed slack qemu-system-arm -M versatilepb -m 256 -kernel Images/zImage-versatile -hda HardDrive/harddisk.img -cdrom CDROM/armedslack.iso -initrd Images/initrd-versatile.img -append root=/dev/ram rw Now sit back and install, the installer will find the cdrom and install the packages from it. to run the installed VM use a script like this one.( adjusting per your needs :)) #!/bin/bash # Start armed slack qemu-system-arm -M versatilepb -m 256 -net vde,vlan=0 -net nic,vlan=0,macaddr=52:54:41:53:13:37 -kernel Images/zImage-versatile -hda HardDrive/harddisk.img -cdrom CDROM/armedslack.iso -localtime -usb -no-reboot -initrd Images/initrd-versatile.gz -append root=/dev/sda2 rootfs=ext4 After configuring the network with netconf ( I like static ips for my VM's ) the VM's routing table looks like this: ___ Destination Gateway Genmask Flags Metric Ref Use Iface localnet * 255.255.255.0 U 0 0 0 eth0 loopback * 255.0.0.0 U 0 0 0 lo default 192.168.2.1 0.0.0.0 UG 1 0 0 eth0 Good luck getting it to work on a slackberry pi, I have done just that. you will need to compile a stock Raspberry pi kernel, (good luck on back porting 2.6.37 to broadcom chip, would be cool though, let me know if you do.) get your .config from a running kernel, arch is good. copy your /root from qemu to your sd card (boot needs to be empty) linux partion and your uncompresseed kernel to the boot vfat partion as kernel.img, don't forget to copy the kernel modules to /lib/module, edit your fstab and cmdline.txt, phew! reboot and voila! Minor niggles: ntpd wont set the clock, however ntpdate will, you go figure? rootfs always loads as rw, perhaps a quirk of the pi boot loader? if you need alpha audio modprobe snd-bbcm2835 X will require building xf86-video-fbdev, and you will need to get an xorg.conf from a running pi. all the best. Stanley I hope that helps ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
