Boot method: SD-Card
Image version: zcat firmware.BananaPiM2Berry.img.gz partition.img.gz >
/dev/sdb
https://deb.debian.org/debian/dists/stable/main/installer-armhf/current/images/netboot/SD-card-images/firmware.BananaPiM2Berry.img.gz
https://deb.debian.org/debian/dists/stable/main/installer-armhf/current/images/netboot/SD-card-images/partition.img.gz
Date: 05 Jan 2025
Machine: Banana Pi BPI-M2 Berry /
https://docs.banana-pi.org/en/BPI-M2_Berry/BananaPi_BPI-M2_Berry
Processor: Allwinner R40i
Memory: 1GB DDR3
Partitions: <df -Tl will do; the raw partition table is preferred>
=== Output "df -Tl" of Variant "SD-Card 32GB" ===
Filesystem Type 1K-blocks Used Available Use% Mounted on
udev devtmpfs 488980 0 488980 0% /dev
tmpfs tmpfs 101968 776 101192 1% /run
/dev/mmcblk0p3 ext4 28692516 1221796 25987868 5% /
tmpfs tmpfs 509820 0 509820 0% /dev/shm
tmpfs tmpfs 5120 0 5120 0% /run/lock
/dev/mmcblk0p2 ext2 466026 57754 383287 14% /boot
tmpfs tmpfs 101964 0 101964 0% /run/user/1000
=== Output "df -Tl" of Variant "SD-Card 4GB & SATA 2TB" ===
Filesystem Type 1K-blocks Used Available Use% Mounted on
udev devtmpfs 489152 0 489152 0% /dev
tmpfs tmpfs 101968 500 101468 1% /run
/dev/sda2 ext4 1919803704 1113292 1821095944 1% /
tmpfs tmpfs 509820 0 509820 0% /dev/shm
tmpfs tmpfs 5120 0 5120 0% /run/lock
/dev/mmcblk1p2 ext2 466026 57408 383633 14% /boot
tmpfs tmpfs 101964 0 101964 0% /run/user/1000
Output of lspci -knn (or lspci -nn): n/a However I am going to attach
the output of hwinfo for Variant "SD-Card 4GB & SATA 2TB"
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [O]
Detect network card: [O]
Configure network: [O]*
Detect media: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Install base system: [P]
Clock/timezone setup: [O]
User/password setup: [O]
Install tasks: [O]
Install boot loader: [O]
Overall install: [O]
*LAN
Comments/Problems:
Summary: Works great, of all those who helped to get working smoothly.
Even the "Power Key" is working as expected. Thanks a million for your work!
To understand my perspective ...
My goal is to setup a Banana Pi M2 Berry as a kind of remote backup
unit. LAN and SATA connection are important to me.
I had followed the instruction of
https://wiki.debian.org/InstallingDebianOn/Allwinner#Installing_from_an_SD_card_image
Later I recognized that comment at the end on "Banana PI M2 Berry" by
LucasNussbaum
From my experience of one day working with BPI and installing it twice
... those work-around seems to be outdated, as everything worked as
expected.
Installation worked like on a PC, except that I could not use HDMI output.
I had installed two variants
- Variant "SD-Card 32GB" (my first attempt)
- Variant "SD-Card 4GB & SATA 2TB"
For both variants I used "guided partitioning", whereas for the one
with SATA I changed something before teh new partitions got writing.
1. deleted partition "/" from SD-Card
2. deleted swap partition from SD-Card
3. created swap partition on SATA drive
4. created partition "/" pm SATA drive
That were the only changes I made. From there I continued with the
installation and no further adjustments were required.
What I liked about the comment from LucasNussbaum ...
The line "You will need a UART (console) cable."
Ah ha ... got it ... I had some trouble with establishing the serial
connection and even went so far to test UART2.
Banana Pi M2 Berry <--> Linux PC
The only quick and easy option I had was using a CH340G - ESP01 UART
Adapter, the one which is usually used for programming the ESP8266-01 board.
My Linux system supports the UART Adapter (by "lsusb" identified as
"QinHeng Electronics CH340 serial converter").
The pins on the ESP01 UART Adapter and ESP8266-01 board were
identical!!! So I simply connected the RXD-RXD and TXD-TXD.
With a regular USB-Serial-TTL Adapter you would have to cross the lines
... RXD-TXD and TXD-RXD.
[E] Broadcom BCM43430A1
It looks to me like Broadcom chip cannot be used (WiFi & Bluetooth).
[E] sun4i-pinctrl & dw-apb-uart
In the boolog are lots of error messages.
My comment on Banana PI M2 Berry and the setup of the installation ...
to make it crisp clear ...
The installer does not support HDMI.
The communication use the boards Debug UART (TTL 3.3V). The UART0 is the
only 3-Pin header on the board.
See https://docs.banana-pi.org/en/BPI-M2_Berry/BananaPi_BPI-M2_Berry
My comment on Serial-Telnet software ... as the baud rate is not
mentioned ...
Settings for the serial port (USB) on the PC have to be (in PuTTY
"Category: Connection > Serial")
- Serial line to connect to: /dev/ttyUSB0
- Speed (baud): 115200
- Data bits: 8
- Stop bits: 1
- Parity: None
- Flow control: XON/XOFF
Further more information on using PuTTY
Category: Terminal
- enable option "Implicit CR in every LF"
Category: Window > Translation
- enable option "Enable VT100 line drawing even in UTF-8 mode"
Linux specific - Category: Windows > Selection
- select "CLIPBOARD" as "Mouse paste action"
- select "CLIPBOARD" as "{Ctrl,Shift} + Ins"
With the above changed (compared to "Default Settings"), the loook &
feel is very pleasant.
And the exchange with other application had been possible as well
(CTRL+INS for Copy & SHIFT+INS for Paste).
On System of variant "SD-Card 4GB & SATA 2TB", I executed the following
command to provide further information as attachments.
hwinfo > hwinfo.out
gzip --to-stdout hwinfo.out > hwinfo.out.gz
tar --create --gzip --file=var_log_installer.tar.gz
--directory=var/log/installer .
=== Boot log of Variant "SD-Card 4GB & SATA 2TB" ===
U-Boot SPL 2023.01+dfsg-2+deb12u1 (Apr 18 2024 - 22:00:21 +0000)
DRAM: 1024 MiB
Trying to boot from MMC1
U-Boot 2023.01+dfsg-2+deb12u1 (Apr 18 2024 - 22:00:21 +0000) Allwinner
Technology
CPU: Allwinner R40 (SUN8I 1701)
Model: Banana Pi M2 Berry
DRAM: 1 GiB
Core: 59 devices, 22 uclasses, devicetree: separate
WDT: Not starting watchdog@1c20c90
MMC: mmc@1c0f000: 0, mmc@1c10000: 1
Loading Environment from FAT... Unable to use mmc 0:2...
In: serial@1c28000
Out: serial@1c28000
Err: serial@1c28000
Net: eth0: ethernet@1c50000
starting USB...
Bus usb@1c19000: USB EHCI 1.00
scanning bus usb@1c19000 for devices... 2 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:2...
Found U-Boot script /boot.scr
2627 bytes read in 1 ms (2.5 MiB/s)
## Executing script at 43100000
Mainline u-boot / new-style environment detected.
5513728 bytes read in 239 ms (22 MiB/s)
25138 bytes read in 4 ms (6 MiB/s)
23450642 bytes read in 1002 ms (22.3 MiB/s)
Booting Debian 6.1.0-28-armmp-lpae from mmc 0:2...
Kernel image @ 0x42000000 [ 0x000000 - 0x542200 ]
## Flattened Device Tree blob at 43000000
Booting using the fdt blob at 0x43000000
Working FDT set to 43000000
Loading Ramdisk to 489a2000, end 49fff412 ... OK
Loading Device Tree to 48998000, end 489a1231 ... OK
Working FDT set to 48998000
Starting kernel ...
[ 0.003844] /cpus/cpu@0 missing clock-frequency property
[ 0.003881] /cpus/cpu@1 missing clock-frequency property
[ 0.003965] /cpus/cpu@2 missing clock-frequency property
[ 0.003986] /cpus/cpu@3 missing clock-frequency property
[ 4.856069] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 198
[ 4.862733] sun4i-pinctrl 1c20800.pinctrl: pin-198 (1c28c00.serial)
status -517
[ 4.870059] sun4i-pinctrl 1c20800.pinctrl: could not request pin 198
(PG6) from group PG6 on device 1c20800.pinctrl
[ 4.880587] dw-apb-uart 1c28c00.serial: Error applying setting,
reverse things back
[ 4.888975] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 202
[ 4.895632] sun4i-pinctrl 1c20800.pinctrl: pin-202
(1c20800.pinctrl:202) status -517
[ 4.904807] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 198
[ 4.911480] sun4i-pinctrl 1c20800.pinctrl: pin-198 (1c28c00.serial)
status -517
[ 4.918802] sun4i-pinctrl 1c20800.pinctrl: could not request pin 198
(PG6) from group PG6 on device 1c20800.pinctrl
[ 4.929334] dw-apb-uart 1c28c00.serial: Error applying setting,
reverse things back
[ 4.937604] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 202
[ 4.944249] sun4i-pinctrl 1c20800.pinctrl: pin-202
(1c20800.pinctrl:202) status -517
[ 4.952585] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 198
[ 4.959260] sun4i-pinctrl 1c20800.pinctrl: pin-198 (1c28c00.serial)
status -517
[ 4.966598] sun4i-pinctrl 1c20800.pinctrl: could not request pin 198
(PG6) from group PG6 on device 1c20800.pinctrl
[ 4.977125] dw-apb-uart 1c28c00.serial: Error applying setting,
reverse things back
[ 4.985331] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 202
[ 4.991967] sun4i-pinctrl 1c20800.pinctrl: pin-202
(1c20800.pinctrl:202) status -517
[ 5.774088] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 198
[ 5.780847] sun4i-pinctrl 1c20800.pinctrl: pin-198 (1c28c00.serial)
status -517
[ 5.788231] sun4i-pinctrl 1c20800.pinctrl: could not request pin 198
(PG6) from group PG6 on device 1c20800.pinctrl
[ 5.798841] dw-apb-uart 1c28c00.serial: Error applying setting,
reverse things back
[ 5.807679] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 202
[ 5.814369] sun4i-pinctrl 1c20800.pinctrl: pin-202
(1c20800.pinctrl:202) status -517
[ 5.880200] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 198
[ 5.886944] sun4i-pinctrl 1c20800.pinctrl: pin-198 (1c28c00.serial)
status -517
[ 5.894334] sun4i-pinctrl 1c20800.pinctrl: could not request pin 198
(PG6) from group PG6 on device 1c20800.pinctrl
[ 5.904921] dw-apb-uart 1c28c00.serial: Error applying setting,
reverse things back
[ 5.914073] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 202
[ 5.920784] sun4i-pinctrl 1c20800.pinctrl: pin-202
(1c20800.pinctrl:202) status -517
[ 5.933241] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 198
[ 5.939930] sun4i-pinctrl 1c20800.pinctrl: pin-198 (1c28c00.serial)
status -517
[ 5.947309] sun4i-pinctrl 1c20800.pinctrl: could not request pin 198
(PG6) from group PG6 on device 1c20800.pinctrl
[ 5.957880] dw-apb-uart 1c28c00.serial: Error applying setting,
reverse things back
[ 5.959062] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 202
[ 5.972365] sun4i-pinctrl 1c20800.pinctrl: pin-202
(1c20800.pinctrl:202) status -517
[ 5.984998] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 198
[ 5.991771] sun4i-pinctrl 1c20800.pinctrl: pin-198 (1c28c00.serial)
status -517
[ 5.999168] sun4i-pinctrl 1c20800.pinctrl: could not request pin 198
(PG6) from group PG6 on device 1c20800.pinctrl
[ 6.009746] dw-apb-uart 1c28c00.serial: Error applying setting,
reverse things back
[ 6.026182] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 0
[ 6.032728] sun4i-pinctrl 1c20800.pinctrl: pin-0 (1c50000.ethernet)
status -517
[ 6.040160] sun4i-pinctrl 1c20800.pinctrl: could not request pin 0
(PA0) from group PA0 on device 1c20800.pinctrl
[ 6.050584] dwmac-sun8i 1c50000.ethernet: Error applying setting,
reverse things back
[ 6.059757] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 202
[ 6.066526] sun4i-pinctrl 1c20800.pinctrl: pin-202
(1c20800.pinctrl:202) status -517
[ 6.077065] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 160
[ 6.079318] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 198
[ 6.079470] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 192
[ 6.079480] sun4i-pinctrl 1c20800.pinctrl: pin-192 (1c10000.mmc)
status -517
[ 6.079491] sun4i-pinctrl 1c20800.pinctrl: could not request pin 192
(PG0) from group PG0 on device 1c20800.pinctrl
[ 6.079502] sunxi-mmc 1c10000.mmc: Error applying setting, reverse
things back
[ 6.083798] sun4i-pinctrl 1c20800.pinctrl: pin-160 (1c0f000.mmc)
status -517
[ 6.090448] sun4i-pinctrl 1c20800.pinctrl: pin-198 (1c28c00.serial)
status -517
[ 6.097073] sun4i-pinctrl 1c20800.pinctrl: could not request pin 160
(PF0) from group PF0 on device 1c20800.pinctrl
[ 6.104137] sun4i-pinctrl 1c20800.pinctrl: could not request pin 198
(PG6) from group PG6 on device 1c20800.pinctrl
[ 6.114643] sunxi-mmc 1c0f000.mmc: Error applying setting, reverse
things back
[ 6.121863] dw-apb-uart 1c28c00.serial: Error applying setting,
reverse things back
/dev/sda2: clean, 35466/121978880 files, 8225925/487890432 blocks
[ 25.384176] brcmfmac mmc0:0001:1: firmware: failed to load
brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-berry.bin (-2)
[ 25.394551] firmware_class: See https://wiki.debian.org/Firmware for
information about missing firmware
[ 25.404312] brcmfmac mmc0:0001:1: firmware: failed to load
brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-berry.bin (-2)
[ 25.414850] brcmfmac mmc0:0001:1: firmware: failed to load
brcm/brcmfmac43430-sdio.bin (-2)
[ 25.423435] brcmfmac mmc0:0001:1: firmware: failed to load
brcm/brcmfmac43430-sdio.bin (-2)
[ 26.433265] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000):
clkctl 0x50
[ 27.092057] bluetooth hci0: firmware: failed to load
brcm/BCM43430A1.sinovoip,bpi-m2-berry.hcd (-2)
[ 27.101347] bluetooth hci0: firmware: failed to load
brcm/BCM43430A1.sinovoip,bpi-m2-berry.hcd (-2)
[ 27.113380] bluetooth hci0: firmware: failed to load
brcm/BCM43430A1.hcd (-2)
[ 27.120748] bluetooth hci0: firmware: failed to load
brcm/BCM43430A1.hcd (-2)
[ 27.128135] bluetooth hci0: firmware: failed to load
brcm/BCM.sinovoip,bpi-m2-berry.hcd (-2)
[ 27.137536] bluetooth hci0: firmware: failed to load
brcm/BCM.sinovoip,bpi-m2-berry.hcd (-2)
[ 27.146314] bluetooth hci0: firmware: failed to load brcm/BCM.hcd (-2)
[ 27.153036] bluetooth hci0: firmware: failed to load brcm/BCM.hcd (-2)
[ 27.159700] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[ 27.166403] Bluetooth: hci0: BCM:
'brcm/BCM43430A1.sinovoip,bpi-m2-berry.hcd'
[ 27.173614] Bluetooth: hci0: BCM: 'brcm/BCM43430A1.hcd'
[ 27.178924] Bluetooth: hci0: BCM: 'brcm/BCM.sinovoip,bpi-m2-berry.hcd'
[ 27.185528] Bluetooth: hci0: BCM: 'brcm/BCM.hcd'
Debian GNU/Linux 12 Sino1 ttyS0
Sino1 login: