arox's post in r2s bridge mode eth0 lan0 was marked as the answer
As stated in the tutorial, you should assign an address to the bridge only.
The bridge forward everything on data link layer and the interface of the bridge then form/extract IP packet. Otherwise you will have a hard time to manage kernel routing tables...
arox's post in command time : missing --help and other options was marked as the answer
"time" is "built in" into the shell.
In order to use the full version described by "man", you should first install the full version in /usr/bin/time :
# apt-get install time.
And call it with the full path.
Also, when man fail to give doc because a package is missing, just google "man cmd".
arox's post in Bridged WiFi AP does not pass dhcp was marked as the answer
Check you have the same netmask on router, bridge and dhcp config.
Check router arp tables and messages to see if it receive requests.
Check if interfaces are really added to the bridge with brctl and that some nasty software has not added addresses to wlan0 and eth0 with ifconfig.
arox's post in Transferring big file crashes BananaPi M1 was marked as the answer
Perhaps you should try another PSU or check your cables : your voltage drop low at 960 MHz and you got SATA errors and reset.
Try : cat /sys/devices/platform/sunxi-i2c.0/i2c-0/0-0034/axp20-supplyer.28/power_supply/ac/voltage_now while transferring files.
arox's post in Bananapi M1 + SSD since 2018, now stuck in read-only filesystem was marked as the answer
If you are not familiar with unix/linux :
- fsck /dev/sda1
If he seems to think nothing needs to be done, don't believe it, do :
- fsck -f /dev/sda1
When he ask to confirm for inodes clear, say "y". You don't have much choice anyway.
If he start asking for removing blocs, you may become worried, but you don't have much choice than agree.
If the number of removal becomes important, you may become very upset.
If he finished and leave a number of files without name in lost+found you have a problem.
But generally you just have a pair of inodes and some pointers/counters that need to be fixed.
In theory you should do a second fsck to be sure the fs is repaired. If this one needs action, your disk or controler has a problem. (The card or the disk ?)
Before swapping sdcards and trying to boot on disk, do a mount
- mount dev/sda1 /mnt
- cat /mnt/etc/os-release (to reassure yourself)
- umount /mnt (or you risk to damage your fs another time)