[Voyage-linux] Mubox: Success for a B Rev 2.1, but not for a Raspberry pi 2 B
Glenn McK
(spam-protected)
Thu Apr 14 12:26:57 HKT 2016
Hi,
Using these versions...
voyage-mubox-rpi-current.tar.xz 06-Feb-2015 08:42 44217224
with https://api.github.com/repos/Hexxeh/rpi-firmware/git/refs/heads/master
as revision...
1e84c2891c1853a3628aed59c06de0315d13c4f1 Apr 14 11:20 52708050
First the success
I've managed to get mubox installed on a B Rev 2.1 (UK)
pi at voyage-mubox:~$ cat /proc/cpuinfo
processor : 0
model name : ARMv6-compatible processor rev 7 (v6l)
BogoMIPS : 697.95
Features : half thumb fastmult vfp edsp java tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xb76
CPU revision : 7
Hardware : BCM2708
Revision : 000e
Serial : 00000000fd19ddc8
pi at voyage-mubox:/etc$ uname -a
Linux voyage-mubox 4.4.7+ #876 Tue Apr 12 22:24:32 BST 2016 armv6l GNU/Linux
It required a couple of edits to the install script...
>······cp "${mntpt}/boot/"*.img "${mntpt1}/"
>······cp "${mntpt}/boot/"*.dtb "${mntpt1}/"
>······mkdir -p ${mntpt1}/overlays
->······cp "${mntpt}/boot/overlays/"*.dtb "${mntpt1}/overlays"
+>······cp "${mntpt}/boot/overlays/"*.dtbo "${mntpt1}/overlays"
·
>······if [ -f "${mntpt}/boot/"Module.symvers ]; then
>······>·······cp "${mntpt}/boot/"Module.symvers "${mntpt1}/"
>······fi
+>······if [ -f "${mntpt}/boot/"Module7.symvers ]; then
+>······>·······cp "${mntpt}/boot/"Module7.symvers "${mntpt1}/"
+>······fi
>······if [ -f "${mntpt}/boot/"git_hash ]; then
>······>·······cp "${mntpt}/boot/"git_hash "${mntpt1}/"
>······fi
as it was failing to transfer the overlay.dtb files ; they are now .dtbo
files
They are installed on the 1st Pi, the successful B Rev (2.1), as dtbo's
dtb or dtbo? https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=140835
It also wasn't moving over the Module7.symvers, where I believe (7) is
specific to the Raspberry pi 2
The failure comes when I install to the SD, and then try to boot from the
micro SD card.
I get one blink from the green (ack?) LED on the Pi and that's it - no more
blinks, no hdmi display, no Led lights. It just sits there.
I've modified the install script (install-mubox-rpi.sh) to keep the large
files locally, it checks on the rpi-firmware file to make sure it's current
but otherwise fetches the files and plonks them in my LAN's webserver. I've
tried a few times to install and figured the polite thing to do was stop
hammering the servers for a start:-)
I also configured the script to do a dry run so that I could check on what
it was doing at each stage.
The boot partion appear as so...
01:40 PM $ ls -al /tmp/cf1
total 21318
drwxr-xr-x 3 root root 16384 Jan 1 1970 .
drwxrwxrwt 37 root root 4096 Apr 14 13:40 ..
-rwxr-xr-x 1 root root 12814 Apr 14 12:58 bcm2708-rpi-b.dtb
-rwxr-xr-x 1 root root 13153 Apr 14 12:58 bcm2708-rpi-b-plus.dtb
-rwxr-xr-x 1 root root 12802 Apr 14 12:58 bcm2708-rpi-cm.dtb
-rwxr-xr-x 1 root root 14420 Apr 14 12:58 bcm2709-rpi-2-b.dtb
-rwxr-xr-x 1 root root 15102 Apr 14 12:58 bcm2710-rpi-3-b.dtb
-rwxr-xr-x 1 root root 17924 Apr 14 12:58 bootcode.bin
-rwxr-xr-x 1 root root 138 Apr 14 12:58 cmdline.txt
-rwxr-xr-x 1 root root 1718 Apr 14 12:59 config.txt
-rwxr-xr-x 1 root root 2512 Apr 14 12:58 fixup_cd.dat
-rwxr-xr-x 1 root root 6484 Apr 14 12:58 fixup.dat
-rwxr-xr-x 1 root root 9725 Apr 14 12:58 fixup_db.dat
-rwxr-xr-x 1 root root 9727 Apr 14 12:58 fixup_x.dat
-rwxr-xr-x 1 root root 41 Apr 14 12:58 git_hash
-rwxr-xr-x 1 root root 4182296 Apr 14 12:58 kernel7.img
-rwxr-xr-x 1 root root 4080280 Apr 14 12:58 kernel.img
-rwxr-xr-x 1 root root 649339 Apr 14 12:58 Module7.symvers
-rwxr-xr-x 1 root root 654486 Apr 14 12:58 Module.symvers
drwxr-xr-x 2 root root 6144 Apr 14 12:58 overlays
-rwxr-xr-x 1 root root 615896 Apr 14 12:58 start_cd.elf
-rwxr-xr-x 1 root root 4891656 Apr 14 12:58 start_db.elf
-rwxr-xr-x 1 root root 2743032 Apr 14 12:58 start.elf
-rwxr-xr-x 1 root root 3843912 Apr 14 12:58 start_x.elf
I get the odd error from the depmod process, the following shows just a
few, I've had more on previous runs
This is from start to finish with the new script (that's why the odd
messages and ultra fast speeds!)
12:54 PM $ ./install-mubox-rpi.sh /dev/sdd write
Commiting write to /dev/sdd, no turning back now!
mntpt_no_write=/tmp/cf #/dev/sdd2
mntpt1_no_write=/tmp/cf1 #/dev/sdd1
fdisk & Formatting is done
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 42.1M 100 42.1M 0 0 2313k 0 0:00:18 0:00:18 --:--:--
1425k
install of root is done
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 50.2M 100 50.2M 0 0 5368k 0 0:00:09 0:00:09 --:--:--
3075k
install Boot
mount /dev/sdd1 /tmp/cf1
mount /dev/sdd2 /tmp/cf
*** depmod 4.4.7+
*** depmod 4.4.7-v7+
depmod: ERROR: failed to load symbols from
/tmp/cf/lib/modules/4.4.7-v7+/kernel/drivers/media/dvb-frontends/tda8083.ko:
Exec format error
depmod: ERROR: failed to load symbols from
/tmp/cf/lib/modules/4.4.7-v7+/kernel/drivers/media/dvb-frontends/tda18271c2dd.ko:
Invalid argument
depmod: ERROR: failed to load symbols from
/tmp/cf/lib/modules/4.4.7-v7+/kernel/net/ipv6/ipv6.ko: Invalid argument
Here!!!
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
0 0 0 0 0 0 0 0 --:--:-- 0:00:01
--:--:-- 0
100 10670 100 10670 0 0 3172 0 0:00:03 0:00:03 --:--:--
8966
[...]
Voyage MuBox for RaspBerry Pi installed!
xterm root at whitebeard:~/PebbleLinux/VoyageLinux
12:59 PM $
Hoping this side of the project is still active, and hoping you can help.
It would be really nice to get an embedded version running on the Pi 2 -
with more memory, a faster processor, and more USB ports to name a few
pluses.
I was a real fan of pebble linux back in 2004-6, this appears to be a great
replacement for that now defunct but excellent effort. Its debian roots
made it easy to maintain, and I see this as being the same, once installed.
:-)
Ah, ps
I almost ?? fragged 2 cards in the process of installing this.
mount /dev/sdd2 on /tmp/cf failed: Structure needs cleaning ext4
A google search returns a lot of XFS results. The first SD I repartitioned
as WFat 32 and put it in the phone as I couldn't get rid of the error no
matter how I tried to repartion it (moving partion 1/2 boundary around did
nothing.)
The second one was fixed (so far so good anyway) with e2fsck -y /dev/sdd2
The -y option was needed!
Hope that helps someone else with their google-fu ?
--
Cheers
Glenn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20160414/fe9bb025/attachment.html>
More information about the Voyage-linux
mailing list