[SOLVED] manual installation on the Raspberry Pi: unable to boot

YuGiOhJCJ · 04-06-2015, 06:44 AM

Hello,

I try to install Slackware on my Raspberry Pi Model B.
I follow the instructions here:
http://docs.slackware.com/howtos:har...rm:raspberrypi

This is exactly what I am doing after inserting my Kingston SD4/8GB SD Card:

Code:

# Get the slack-14.1-miniroot_04Nov13.tar.xz archive
cd /tmp
wget -c ftp://ftp.arm.slackware.com/slackwarearm/slackwarearm-devtools/minirootfs/roots/slack-14.1-miniroot_04Nov13.tar.xz
# Get the raspbian_boot_stuff.tgz archive
wget -c http://downloads.raspberrypi.org/raspbian/images/raspbian-2013-09-16/2013-09-10-wheezy-raspbian.zip
unzip -o 2013-09-10-wheezy-raspbian.zip
sudo losetup -o $((8192 * 512)) /dev/loop0 2013-09-10-wheezy-raspbian.img
sudo losetup -o $((122880 * 512)) /dev/loop1 2013-09-10-wheezy-raspbian.img
sudo mount -o ro /dev/loop1 /mnt/floppy
sudo mount -o ro /dev/loop0 /mnt/floppy/boot
cd /mnt/floppy
tar vcpzf /tmp/raspbian_boot_stuff.tgz boot lib/modules/ lib/firmware opt/vc
cd -
sudo umount /mnt/floppy/boot
sudo umount /mnt/floppy
sudo losetup -D
rm 2013-09-10-wheezy-raspbian.img
# Install on the SD card
sudo mkdosfs -F 32 /dev/mmcblk0p1
sudo mke2fs -t ext4 -b 4096 -i 16384 -m 0  -L root /dev/mmcblk0p2
sudo mount -o noatime /dev/mmcblk0p2 /mnt/hd
sudo mkdir -vp /mnt/hd/boot
sudo mount -o noatime /dev/mmcblk0p1 /mnt/hd/boot
cd /mnt/hd
sudo tar xvf /tmp/slack-14.1-miniroot_04Nov13.tar.xz
sudo tar xvf /tmp/raspbian_boot_stuff.tgz
sudo vim boot/cmdline.txt
sudo vim etc/fstab
cd -
sudo umount /mnt/hd/boot
sudo umount /mnt/hd

This is how my SD card is partitioned:

Code:

sudo fdisk -l /dev/mmcblk0

Disk /dev/mmcblk0: 7822 MB, 7822376960 bytes
4 heads, 16 sectors/track, 238720 cylinders, total 15278080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000d8d91

        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1            2048      133119       65536    c  W95 FAT32 (LBA)
/dev/mmcblk0p2          133120     7995391     3931136   83  Linux

This is the content of the boot/cmdline.txt file:

Code:

dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait ro

This is the content of the etc/fstab file:

Code:

proc            /proc           proc    defaults          0       0
/dev/mmcblk0p1  /boot           vfat    errors=remount-ro          0       2
/dev/mmcblk0p2  /               ext4    errors=remount-ro,noatime  0       1

When I insert the SD card to my Raspberry Pi then I connect the power cable, I only got a "red" LED.
This is not a hardware problem because it works with the NOOB installer.
The first installation of Slackware on my Raspberry Pi I have done in July 2014 was a success.
But today, I am unable to do it again.
Probably I forgot a step somewhere but I do not see what is missing.

Any idea why I cannot boot after installing Slackware on my Raspberry Pi?

Thank you.
Best regards.

the3dfxdude · 04-06-2015, 09:52 AM

Seeing those "manual" instructions, I wouldn't trust it too much, since it appears to be using raspian images to bootstrap the thing that are way old now. I do not know if this board you are setting up is the same as your last one, but boards at different times came from different fab spins, or have had minor revisions. The firmware has to be updated to the latest, or it won't boot. I wouldn't run anything except the most recent reasonable image to rule that out. Go to http://rpi.fatdog.eu/ as his installer image is only a few days old, and I just went through his instructions successfully 2 days ago.

louigi600 · 04-06-2015, 12:23 PM

I wrote the manual installation myself (well it was edited to that text by someone else).
I added the notes below the community modified installer links because none of the worked on my board at the time my unit was shipped to me.

the3dfxdude: I point to the image download section not to a specific image ... so chances are that raspbian has the updated kernel and firmware ... I then show how to extract the stuff you need to boot Slackware (or any other distro if you like ... possibly even one of the installation images provided by community).

YuGiOhJCJ: I'm not sure why your SD is not booting ... but it's not really an installation ... it's just a miniroot system that then needs to be extended with the rest.
I suggest you try booting the raspbian image ... if it boots then the firmware in the raspbian image is good for your board ... you just need to figure our what went wrong ... or possibly what was incorrectly documented in docs slackware.

It might be helpful if you cut and paste the entire procedure including the command's output.
I don't remember off hand what the led status on the PI mean but I suggest you also look at that to see if it can help figure out what went wrong.
If it's a firmware issue the leds should indicate that something more then just the red led ... if only the red led gets lit I think the firmware file is not even found on the SD.

the3dfxdude · 04-06-2015, 01:21 PM

Quote:

Originally Posted by louigi600

the3dfxdude: I point to the image download section not to a specific image ... so chances are that raspbian has the updated kernel and firmware ... I then show how to extract the stuff you need to boot Slackware (or any other distro if you like ... possibly even one of the installation images provided by community).

I understand. I might have used the wrong word: 'trust'. I mean that they should extrapolate to what they need to actually be doing and not run it literally.

slacker1337 · 04-06-2015, 06:14 PM

This is how my SD card is partitioned:

Code:

sudo fdisk -l /dev/mmcblk0

Disk /dev/mmcblk0: 7822 MB, 7822376960 bytes
4 heads, 16 sectors/track, 238720 cylinders, total 15278080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000d8d91

        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1            2048      133119       65536    c  W95 FAT32 (LBA)
/dev/mmcblk0p2          133120     7995391     3931136   83  Linux

I noticed that your /dev/mmcblk0p1 partition is not marked as bootable, couldn't that be part of your problem?

louigi600 · 04-07-2015, 01:28 AM

I don't remember if I had-to make my dos partition bootable ... chances are that it's not required as it's not dos that's booting.
I'll check when I get back home ... or if anyone else that has a Pi handy they're welcome.

YuGiOhJCJ · 04-07-2015, 10:52 AM

the3dfxdude> I prefer a manual installation than an installation that requires an installer.
That is why I chose this solution.
Anyway, I have followed these instructions using an old version of raspbian from 2013 but I have also tested with a version from 2014.
Same results.
On the link you give, I only see an installer image.
That is not what I am looking for as I would like a manual installation.

louigi600> OK I give you the full output later, I am busy now.
How exactly I can try booting the raspbian image like you said?

slacker1337> Indeed, I have already tested with the boot flag activated and: same results.

louigi600 · 04-08-2015, 04:36 AM

I only went as far as extracting the bits and pieces to boot Slackware ARM miniroot, I never actually installed Raspbian but if I remember correctly it should not be much more then just writing the image to a SD.

I would advise to use the newer firmware in the latest raspbian image release notes:

Code:

2015-02-16:
  * Newer firmware with various fixes

YuGiOhJCJ · 04-08-2015, 10:23 AM

This is the full output:

Code:

$ cd /tmp
$ wget -c ftp://ftp.arm.slackware.com/slackwarearm/slackwarearm-devtools/minirootfs/roots/slack-14.1-miniroot_04Nov13.tar.xz
--2015-04-08 16:50:45--  ftp://ftp.arm.slackware.com/slackwarearm/slackwarearm-devtools/minirootfs/roots/slack-14.1-miniroot_04Nov13.tar.xz
           => slack-14.1-miniroot_04Nov13.tar.xz
Resolving ftp.arm.slackware.com (ftp.arm.slackware.com)... 91.109.244.240
Connecting to ftp.arm.slackware.com (ftp.arm.slackware.com)|91.109.244.240|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done.    ==> PWD ... done.
==> TYPE I ... done.  ==> CWD (1) /slackwarearm/slackwarearm-devtools/minirootfs/roots ... done.
==> SIZE slack-14.1-miniroot_04Nov13.tar.xz ... 30165556
File has already been retrieved.
2015-04-08 16:50:46 (0.00 B/s) - slack-14.1-miniroot_04Nov13.tar.xz saved [30165556]

$ wget -c http://downloads.raspberrypi.org/raspbian/images/raspbian-2013-09-16/2013-09-10-wheezy-raspbian.zip
--2015-04-08 16:51:24--  http://downloads.raspberrypi.org/raspbian/images/raspbian-2013-09-16/2013-09-10-wheezy-raspbian.zip
Resolving downloads.raspberrypi.org (downloads.raspberrypi.org)... 93.93.130.214, 93.93.130.39, 93.93.128.211, ...
Connecting to downloads.raspberrypi.org (downloads.raspberrypi.org)|93.93.130.214|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://director.downloads.raspberrypi.org/raspbian/images/raspbian-2013-09-16/2013-09-10-wheezy-raspbian.zip [following]
--2015-04-08 16:51:24--  http://director.downloads.raspberrypi.org/raspbian/images/raspbian-2013-09-16/2013-09-10-wheezy-raspbian.zip
Resolving director.downloads.raspberrypi.org (director.downloads.raspberrypi.org)... 93.93.128.211, 93.93.128.230, 93.93.130.214, ...
Reusing existing connection to downloads.raspberrypi.org:80.
HTTP request sent, awaiting response... 416 Requested Range Not Satisfiable

    The file is already fully retrieved; nothing to do.

$ unzip -o 2013-09-10-wheezy-raspbian.zip
Archive:  2013-09-10-wheezy-raspbian.zip
  inflating: 2013-09-10-wheezy-raspbian.img  
$ sudo losetup -o $((8192 * 512)) /dev/loop0 2013-09-10-wheezy-raspbian.img
$ sudo losetup -o $((122880 * 512)) /dev/loop1 2013-09-10-wheezy-raspbian.img
$ sudo mount -o ro /dev/loop1 /mnt/floppy
$ sudo mount -o ro /dev/loop0 /mnt/floppy/boot
$ cd /mnt/floppy
$ tar vcpzf /tmp/raspbian_boot_stuff.tgz boot lib/modules/ lib/firmware opt/vc
boot/
boot/bootcode.bin
boot/cmdline.txt
boot/config.txt
boot/fixup.dat
boot/fixup_cd.dat
boot/fixup_x.dat
boot/kernel.img
boot/kernel_emergency.img
boot/start.elf
boot/start_cd.elf
boot/start_x.elf
boot/issue.txt
lib/modules/
[...] I cut here because it is too much characters for this forum :)
$ cd -
/tmp
$ sudo umount /mnt/floppy/boot
$ sudo umount /mnt/floppy
$ sudo losetup -D
$ rm 2013-09-10-wheezy-raspbian.img
$ sudo mkdosfs -F 32 /dev/mmcblk0p1
mkfs.fat 3.0.22 (2013-07-19)
WARNING: Not enough clusters for a 32 bit FAT!
$ sudo mke2fs -t ext4 -b 4096 -i 16384 -m 0  -L root /dev/mmcblk0p2
mke2fs 1.42.8 (20-Jun-2013)
Discarding device blocks: failed - Input/output error
Filesystem label=root
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
245760 inodes, 982784 blocks
0 blocks (0.00) reserved for the super user
First data block=0
Maximum filesystem blocks=1006632960
30 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done 

$ sudo mount -o noatime /dev/mmcblk0p2 /mnt/hd
$ sudo mkdir -vp /mnt/hd/boot
mkdir: created directory /mnt/hd/boot
$ sudo mount -o noatime /dev/mmcblk0p1 /mnt/hd/boot
$ cd /mnt/hd
$ sudo tar xvf /tmp/slack-14.1-miniroot_04Nov13.tar.xz
./
./var/
./var/rwho
./var/adm
./var/spool/
./var/spool/cron/
./var/spool/cron/crontabs/
./var/spool/cron/crontabs/root
./var/spool/cron/cronstamps/
./var/spool/mail/
./var/spool/mail/root
./var/lock/
./var/lock/subsys/
./var/lib/
./var/lib/dhcpcd/
./var/lib/dbus/
./var/lib/nfs/
./var/lib/nfs/rmtab
./var/lib/nfs/etab
./var/lib/nfs/state
./var/lib/nfs/sm.bak/
./var/lib/nfs/xtab
./var/lib/nfs/sm/
./var/lib/arpd/
./var/log/
./var/log/scripts/
[...] I cut here because it is too much characters for this forum :)
$ sudo tar xvf /tmp/raspbian_boot_stuff.tgz
boot/
boot/bootcode.bin
boot/cmdline.txt
boot/config.txt
boot/fixup.dat
boot/fixup_cd.dat
boot/fixup_x.dat
boot/kernel.img
boot/kernel_emergency.img
boot/start.elf
boot/start_cd.elf
boot/start_x.elf
boot/issue.txt
lib/modules/
[...] I cut here because it is too much characters for this forum :)
$ sudo vim boot/cmdline.txt
$ sudo vim etc/fstab
$ cd -
/tmp
$ sudo umount /mnt/hd/boot
$ sudo umount /mnt/hd

Anything strange here?

louigi600 · 04-08-2015, 12:09 PM

Probabbly not ... but I noticed that you did

Code:

$ sudo losetup -o $((8192 * 512)) /dev/loop0 2013-09-10-wheezy-raspbian.img
$ sudo losetup -o $((122880 * 512)) /dev/loop1 2013-09-10-wheezy-raspbian.img

without having checked first if the image partitioning patches that, it probably has not changed since I wrote the guide, or you might even be using the same image that I used, but a check would not hurt.

Then I noticed this:

Code:

$ sudo mkdosfs -F 32 /dev/mmcblk0p1
mkfs.fat 3.0.22 (2013-07-19)
WARNING: Not enough clusters for a 32 bit FAT!
$ sudo mke2fs -t ext4 -b 4096 -i 16384 -m 0  -L root /dev/mmcblk0p2
mke2fs 1.42.8 (20-Jun-2013)
Discarding device blocks: failed - Input/output error

You formatted the SD but did you partition it first ? (or you didn't show it) ... you got errors while formatting maybe there's something wrong in the SD partitions or partition table ? are you sure the SD you are targeting is in /dev/mmcblk0 on the computer where you're doing this ?

YuGiOhJCJ · 04-09-2015, 10:13 AM

louigi600>I am using the same image that you used so the values 8192, 122880 and 512 are good.
See here:

Code:

$ fdisk -l 2013-09-10-wheezy-raspbian.img 

Disk 2013-09-10-wheezy-raspbian.img: 1939 MB, 1939865600 bytes
255 heads, 63 sectors/track, 235 cylinders, total 3788800 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000b03b7

                         Device Boot      Start         End      Blocks   Id  System
2013-09-10-wheezy-raspbian.img1            8192      122879       57344    c  W95 FAT32 (LBA)
2013-09-10-wheezy-raspbian.img2          122880     3788799     1832960   83  Linux

Anyway, the other version I have also used for an other test seems to keep the same values :

Code:

$ fdisk -l 2014-06-20-wheezy-raspbian.img 

Disk 2014-06-20-wheezy-raspbian.img: 2962 MB, 2962227200 bytes
255 heads, 63 sectors/track, 360 cylinders, total 5785600 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000b5098

                         Device Boot      Start         End      Blocks   Id  System
2014-06-20-wheezy-raspbian.img1            8192      122879       57344    c  W95 FAT32 (LBA)
2014-06-20-wheezy-raspbian.img2          122880     5785599     2831360   83  Linux

So, I think there is no problem here.

For the warning message from the "mkdosfs" command, I have seen it.
In fact, this is because the partition size is not enough large to be formatted correctly.
In order to remove this warning I have increased the size of my first FAT32 partition.
But this does not solve the problem: When I insert the SD card to my Raspberry Pi then I connect the power cable, I only got a "red" LED.

For answering all you questions:

"You formatted the SD but did you partition it first ?"
Yes, I am using fdisk first to partition and I have only shown the result of "fdisk -l".
As you can see, it is exactly the partitions of your instructions.

"Maybe there's something wrong in the SD partitions or partition table ?"
Yes, there is one error for the first partition but that is just because of the size that is not enough large.
If I increase the size of this partition, I have zero error while I am formatting.
Anyway, that is not an error but a warning.
I think it is formatted because the "mount" command is working and I can copy files on this partition so it seems to be good.

"Are you sure the SD you are targeting is in /dev/mmcblk0 on the computer where you're doing this ?"
Yes, /dev/mmcblk0 is corresponding exactly to my SD card because when I insert the card, this device automatically appears.
I remind you that I am able to install an other operating system on this card (using NOOB) so it should be fine.

Any other idea why I cannot boot?

YuGiOhJCJ · 04-09-2015, 10:21 AM

Yes, in fact you have right there was an error while formatting the second partition.
But this not happen in a normal case.
I have done a copy/paste of my commands so it is maybe too quick but as you can see, when I do it manually, I got no error:

Code:

$ sudo mke2fs -t ext4 -b 4096 -i 16384 -m 0  -L root /dev/mmcblk0p2
mke2fs 1.42.8 (20-Jun-2013)
Discarding device blocks: done                            
Filesystem label=root
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
245760 inodes, 982784 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1006632960
30 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done

So the problem is not here... But where?

louigi600 · 04-10-2015, 01:28 AM

You said you've done this on another board previously and it worked, does the SD you are making now boot on the older board ?
If it does that the new board requires the newer firmware, if it doesn't something else is wrong.
If you don't have the old board anymore put the image (dd of the whole SD possibly xz compressed) somewhere so I can get it and test it on my PI.

YuGiOhJCJ · 04-10-2015, 02:41 AM

In fact, I have maybe not explained the things correctly.
I have only one board.
I have successfully installed Slackware following your instructions in July 2014.
But today, on the same board with the same SD card, I am unable to do it again.

louigi600 · 04-10-2015, 02:50 AM

Today when I get back home I'll try go trough all the steps again to see if something is wrong.
Have you got another SD to play with ? just incase something is starting to go wrong with the SD itself.