I need to compile Kernel in order to run Docker.io (Docker.io says: “You are running Linux kernel version 3.4.39-BPI-M3-Kernel, which is unsupported for running Docker. Please upgrade your kernel to 3.8+”). Is there a How To? Is cross compile an option in order to compile it faster?
1 Like
I have the same question.
You could try armbian to install docker, here is the image: https://dl.armbian.com/bananapim3/Debian_stretch_dev.7z (Here Thanks for the armbian community)
Download this image to your ubuntu PC (I am using ubuntu PC), then decompress it
- 7z x Armbian_5.59_Bananapim3_Debian_stretch_dev_4.18.8.7z
- fdisk -l to check your sd card drive letter, my sd card is 32 GB, and you could see the drive letter is /dev/sdf
- bpi-copy xxx.img to your sd card
username: root, password: 1234
Here are steps to install docker:
-
vim /etc/apt/sources.list
-
add this source：“deb http://http.debian.net/debian jessie-backports main”
-
apt-get update
-
apt-get install docker.io
To have a test, if docker has installed in your image.
- sudo docker run --rm hello-world
Thank you for your reply.
After I follow this steps I wasn’t able to boot from card. With other images I am able to boot , but with this one… I can’t.
can you try this tool？
I try Etcher on Ubuntu desktop and dd command. I also try Rufus on windows 10. The same result in all the cases. No boot for this image.
How did you manage to boot with this image ? I try different sd cards.
hello, Did you try Etcher on windows?
and M3 we are trying to update kernel to 4.19.
Yes, I try also that. The same result. No booting .
that’s strange, could you show me the log?
Sure. What is the path for the logs that you want to see ? I mean where I can find them ?
Checking for Rufus updates...
Checking release channel...
Updates: Unable to access version data
Found USB 2.0 device 'Generic- SD/MMC USB Device' (0BDA:0109)
1 device found
No volume information for drive 0x83
Disk type: Removable, Disk size: 32 GB, Sector size: 512 bytes
Cylinders: 3781, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0xD9C918FE
Drive has an unknown Master Boot Record
Partition 1:
Type: GNU/Linux (0x83)
Size: 28.7 GB (30789713920 bytes)
Start Sector: 8192, Boot: No
Closed Windows format prompt
Scanning image...
ISO analysis:
E:\Armbian_5.59_Bananapim3_Debian_stretch_dev_4.18.8\Armbian_5.59_Bananapim3_Debian_stretch_dev_4.18.8.img' doesn't look like an ISO image
Disk image analysis:
Image has an unknown Master Boot Record
Image is a bootable disk image
Using image: Armbian_5.59_Bananapim3_Debian_stretch_dev_4.18.8.img (1000 MB)
Format operation started
Requesting disk access...
Opened \\.\PHYSICALDRIVE3 for exclusive write access
Requesting lock...
Will use 'G:' as volume mountpoint
Requesting lock...
Writing Image...
Drive has an unknown Master Boot Record
Found USB 2.0 device 'Generic- SD/MMC USB Device' (0BDA:0109)
1 device found
No volume information for drive 0x83
Disk type: Removable, Disk size: 32 GB, Sector size: 512 bytes
Cylinders: 3781, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0xD9C918FE
Drive has an unknown Master Boot Record
Partition 1:
Type: GNU/Linux (0x83)
Size: 996 MB (1044381696 bytes)
Start Sector: 8192, Boot: No
>Hello, I format my sd card, and install image again, it could boot.
could you please try these commands to install image?
bpi-copy xxx.img /dev/sd< drive letter >
it should work.
cazacu@cazacu-Lenovo-ideapad-110-15IBR:~/Downloads/Armbian_5.59_Bananapim3_Debian_stretch_dev_4.18.8$ sudo bpi-copy Armbian_5.59_Bananapim3_Debian_stretch_dev_4.18.8.img /dev/mmcblk0p1
SRC=Armbian_5.59_Bananapim3_Debian_stretch_dev_4.18.8.img
DST=/dev/mmcblk0p1
COPYMODE=imagetodisk
imagetodisk
bpi-copy(v1.3.3(github)), bananapi image & disk tools
Usage: bpi-copy [OPTIONS]...
bpi-copy [ --help | -v | --version ]
bpi-copy IMGFILE
bpi-copy IMGDIR
bpi-copy IMGFILE DEVICE
bpi-copy DEVICE IMGFILE
Warning: Try to write Armbian_5.59_Bananapim3_Debian_stretch_dev_4.18.8.img to BOOTDISK /dev/mmcblk0p1
==============================================================
vineri 19 octombrie 2018, 13:37:11 +0300
*** start COPY (blue led on ) .....
INFO: /dev/mmcblk0p1 : SD/eMMC !!
umount device: /dev/mmcblk0p1
==============================================================
IMGFILE=Armbian_5.59_Bananapim3_Debian_stretch_dev_4.18.8.img
==============================================================
img
1000MiB 0:01:08 [14,7MiB/s] [ <=> ]
100+0 records in
100+0 records out
1048576000 bytes (1,0 GB, 1000 MiB) copied, 68,2079 s, 15,4 MB/s
22+5361 records in
22+5361 records out
*** end COPY (blue led off) .....
vineri 19 octombrie 2018, 13:38:42 +0300
==============================================================
RUNTIME 1:31
OK!! You can remove the BOOTDISK /dev/mmcblk0p1 now!!
cazacu@cazacu-Lenovo-ideapad-110-15IBR:~/Downloads/Armbian_5.59_Bananapim3_Debian_stretch_dev_4.18.8$
It’s not booting. I am not sure what i am doing wrong.
I also try with with Disk Image Write native application from Ubuntu. Same result.
It said image is not bootable.
Can you please show me the full log ?
Hello, I add more details here, please check it.
- I will repeat this steps and I will come with more logs.
- I do not know where can be the difference.
- I have Banana Pi M3 v 1.2. Sandisk card 32 Gb. ext4 partion format.
- I can boot from other images.
Do you have other suggestions ?
Thank you
I manage to boot somehow… I mean was the same behavior. But this time I pressed multiple time reset button, and he mange to enter in boot mode.
But at end of boot load , I received fail on CPU … And he said will reboot in 10 seconds. I think was a temperature problem , because the board was very hot.
I don’t have a log and I didn’t manage to enter again in that mode.
Thank you for your time with me.
I salute you with respect.
I manage to boot.
I install image with etcher-electron. And what was the difference from other images , was the blue led. For this image was not lighting up. There was no logs during the system loading…
So I just wait some minutes with the cursor in left corner… And after that I was able to login.
Thank you again !
P.S. I did not try to install docker, but from now I don’t think will be a problem.
For me this topic is closed.
1 Like