Hi Penthux,

Thanks for the advice. That could be a factor or that the USB drive I first used was wobbly.. Anyway, I am up and running, with my installation now also copied to the usb drive (which was reformatted to ext4 for this) so that I now can switch between the SD-card installation and the one on USB by editing the root= parameter in the cmdline.txt (from /dev/mmcblk0p3 for SD to /dev/sda1 for USB). My home folder lives on the USB (referred to from the SD and USB /etc/fstab files).

Only problem is that after rebooting I often see the fsck error for the fat32 (/boot) partition (and I also see that on my laptop for the /boot/efi.... after accessing these one always seem to get this... I wonder whether the shutdown process completes; I interact via SSH (ethernet) or screen (usb-serial cable) with the pi2 and I do not always see the whole process complete (because the connections get killed before the rest)

Now I have to figure out how to get my display to work a waveshare-spotpear-4-inch-lcd. I just managed to get rpi-update installed (needed to set the correct time with ntp in order to pass a ca-certificate error https://github.com/Hexxeh/rpi-update, downloaded the driver/firmware via "REPO_URI=https://github.com/notro/rpi-firmware rpi-update" and need now to reboot to see whether any progress has been made.....

I'm migrating my web server over tonight, so far the RP2 has taken everything I've thrown at it.

I'm having the same issue as brobr (install from mounted directory (on USB)) and tried Penthux's suggestions.

Same thing. 5 or 10 seconds after starting the install setup says the install is done. A handfull of messages flash by too quickly to read (replaced by the blue setup screen) and I'm not sure where to pull them out of.

Ok, I have managed to get the a waveshare-spotpear-4-inch-lcd touchscreen to work and even kept some cryptic notes. For whoever is interested.. see attached file; referenced websites are mentioned and how it was set up according to some rasbian users. With Slackware it can be done a bit more elegant ;-)

Only problem is my wireless dongle, after I tried to get it going with Networkmanager from a commandline it got stuck (The info for nmcli is absolutely confusing to say the least. So some of my mis-commands must have triggered something..) I have now wicd doing the job but still no wireless; I noticed this in dmesg:
Cheers,

Rob

PS attachment of things to raspi2 can be a bit flimsy (especially when itself is in a nice box) and this screen is quickly upset (it does not really fit within the box-opening) when using touch input... have to get a cable or something for it... or sand down some bits away from the box-edges....

Attached Files

ChngesFor4inchTouchScreen.txt (4.9 KB, 25 views)

Are you using a USB flash drive right from the store? I found I had to reformat mine as ext2 due to symlinks and filenames in the arm source that vfat can't support.


Ohh, and don't do like me and forget to setup ntp afterward, I now have a bunch of files I created in 1970

I have experienced this issue only when my mounted USB stick was not detected, or if I'd made a mess of the partitions. So make sure when you create partitions you save the new settings. I've forgotten to do that a few times when rushing through the install process. Also, instead of mounting your USB stick, during setup (source media selection) choose option [2] to "Install from a Slackware USB stick" and see if the system scans and detects it successfully. Failing that, you have the option to install from a FTP/HTTP server, if you have access to the Internet.

As enine says, correct date/time is also a factor to consider. If you enable the network prior to running setup, you can easily set the date/time with 'ntpdate pool.ntp.org' - you can also add this to your rc.local to set the correct time during boot.

More often than not, in my experience, when setup quits as soon as it begins it's due to some small error I've created or overlooked.

I was able to reformat a USB stick to ext2 and it seemed to work for the install. Thanks enine. It took about 90 minutes.

But I'm not out of the woods. On reboot I got a root prompt and logged in. Still following the guide at "fatdog" I went to set the time. Error, ntpdate not found. So I set the time with the date command. Then I went to update as the guide says. I edited the file with nano successfully. But when running slackpkg update I got the error that wget was not found.

So enough for today. I'll revisit those errors later.

Some of you seem to be having problems. This troubles me because I had tested the SARPi2 installer thoroughly over a period of approx. 10 days before releasing it to the public. I believed it was working flawlessly. The only issues I have experienced is with some newly discovered problematic hardware.

I´m using Samsung EVO microSD cards (8GB, 16GB, and 32GB). I find these cards to be extremely reliable and compatible, and FAST! That´s not to say other microSD cards aren´t. You may find some cards work better than others. I´ve introduced my SanDisk microSD card to a pair of hungry scissors and did what I believe was the only humane thing left to do with it. ;-)

I use a Kingston DTSE9 (8GB) USB stick to store the Slackware source media. I was using an Imation Nano (16GB) USB stick, but I found that when I used this to store the source media while it was plugged into the USB ports farthest from the Ethernet port there were certain issues after rebooting, if it even booted at all. Using the Kingston USB stick in the same ports, containing the same source data, there were no such issues.

I just bricked my Slackware-arm install on my Pi2 by some usb-mishap. I plugged in a USB-serial cable, but obviously something went wrong as my computer from which I was going to login crashed, something fizzed and I think that cable can only give power now (the Pi2 was powered from the mains at the time of this accident). Dunno whether plugging into a USB3 port caused the damage or attaching the ground of the cable to a 3V pin on the GPIO board or both....Major worry is that the gpio-bridge on the pi has gone as well. Anyway, we will find out.

The USB drive I used to provide the installation (64 G intergral) gave a pertinent I/O error and all my work of the last weekend had to be zeroed over (dd if=/dev/zero of=/dev/sdc bs=1M) to be able to make it reusable and accessible for a new partition etc. (done with Gparted). Anyway, I have now copied all the newly updated slackarm stuff over and use that drive at the moment to upgrade my original slackware install on the SD drive

[sounds cryptic maybe, but for trying stuff out, I had one partition on the USB drive set up as / (root; /dev/sda1) after copying over the whole slackware-installation from the SD (apart from /boot) to the USB stick and editing the /boot/cmdline.text on the SD card to direct the booting to / on the USB drive ('root=/dev/sda1') combined with editing /etc/fstab that was copied to the USB (i.e. in (/dev/sda1/etc/)), making / point to /dev/sda1. Luckily I had left the original install on the SD card intact (incl. swap) and therefore could now boot into the Pi2 after editing the /boot/cmdline.txt back to look for / on the SD (/dev/mm....p1)]

After this has been done and all new links will be set to 1970 (forgot to set the clock before doing the upgrade), I can copy the upgraded installation to my USB /-partition again and introduce all the changes to get my 4"screen going, if the GPIO it gets attached to has not been fried. (If so, game over with Pi-play and then will hook it via a hdmi-connection to a televison and use it as a computer for guests or something). Anyway, after the copying (I do this on my laptop, that is faster) I'll try the USB in another port on the Pi2

EDIT: Changing the USB stick to another port did not make a difference. But that stick has now been completely formatted as ext4.
My gpio-plugged-in screen does not communicate with the Pi2 anymore. It glares, that's it, but won't exchange info required for the flexfb to keep going. I see an error 22 in the dmesg and /dev/fb1 is not generated... game over it seems.

I'm using Microcenter branded microsd cards and an older version of this http://www.iogear.com/product/GFR204SD/ which is a USB microSD adapter. That let me write the bootable card and then swap in another card to make the source.
My original Pi (not a 2) reboots when I plug it in though.

I used 2 different Lexar USB drives for the Slack-current files and a Kingston 16 GB micro SD for the Pi.

The difference in filesystems would seem to have made the difference that allowed me to install from the USB, although I tried FAT on one and ext2 on the other.

I looked through the N set of Slack-current and sure enough, there was no ntp or wget files. I ran a second rsync and there were NOT huge amounts of missing files. Some kernel and library updates along with a few other programs. Both ntp and wget were downloaded. I installed ntp and wget manually then updated the time and ran slackpkg update. The packages updated seemed to generally match what I remembered as being updated with rsync.

Slack now boots on my Pi 2. I just opened up a few different programs and it seemed fairly snappy. The KDE web browser and office writer failed to open. There were locale and QT errors in the terminal.

Also, it seems that I cannot immediately reboot a Pi 2 after doing a cold shutdown. It happened yesterday when I shut down after the initial install and I moved the micro SD to a second Pi 2. Same today, although the first Pi 2 booted, I shut down after installing ntp and wget as the networking did not seem to work, and that Pi would not reboot. I moved the micro SD card to the second Pi and networking worked fine.

It arrived yesterday and 14.1 installed without issue.

Nice job all, thank you

Mine has been running production for two weeks now with no problems. I shut down in the middle to swap the single power supply for a $7 powered USB hub so I can power my old Pi B from the same source.
Not as exciting as others with nothing interfaced, its simply my web server but I have 3 androids and 4 laptop/desktops using Owncloud's webdav/caldav/carddav interface to sync our data off of it. Running Apache, MariaDB, Owncloud, phpMyGPX and Drupal.

I just found last night that you need to update Exaga's packages if your running -current. I did a fresh install of current after a power issue corrupted my microsd and current didn't work with the older February packages, mainly it didn't setup eth0.

I thought I read somewhere that -current is needed for the rp2 but maybe I misread as looking at your page this morning I see its just using -current as an example.

since I'm running "production" I probably should be on 14.1 if its fine to use.