The
-
Posts
18 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by The
-
-
I found the error. It was the mount point. Everything's working fine now for almost 7 weeks.
-
On 5/10/2020 at 9:09 PM, Igor said:
Try changing CPU governor to "performance" and report if that helps.
My uptime is 7 days. As long as never before. I guess the change to "performance" works. Thank you very much.
-
-
Armbianmonitor:
Hello,
my BananaPi M1 sometimes just stops working. The maximum uptime is 5 days. Usually the time is shorter. The system simply hangs. I can no longer access the system via SSH. When I connect a monitor to HDMI, nothing is displayed, so I can log in.
I have connected an external hard drive that is self-powered. I know the stories with the power supply. I have run ' stress -c 2 -m 1 '. The system remains stable.
Time CPU load %cpu %sys %usr %nice %io %irq CPU PMIC DC-IN C.St 19:09:19: --- 0.69 10% 5% 5% 4% 0% 0% 49.3°C 42.4°C 5.10V 0/6 19:09:49: --- 2.16 100% 33% 66% 0% 0% 0% 50.2°C 43.6°C 5.10V 0/6 19:10:16: --- 3.18 100% 33% 65% 0% 0% 1% 50.2°C 44.0°C 5.06V 0/6 19:10:47: --- 3.58 100% 33% 64% 0% 0% 1% 51.0°C 44.4°C 5.05V 0/6 19:11:17: --- 3.96 100% 33% 64% 0% 0% 1% 51.4°C 44.9°C 5.03V 0/6 19:11:47: --- 4.34 100% 33% 65% 0% 0% 1% 51.1°C 45.0°C 5.09V 0/6 19:12:17: --- 4.42 100% 33% 65% 0% 0% 1% 51.3°C 45.3°C 5.07V 0/6
I also executed 'armbianmonitor -u'.The log is here: http://ix.io/2lzX
I checked syslog, daemon.log, user.log, armbian-ramlog.log for errors. With my amateurish understanding I did not find any error entries. In which logs can I still look up to search for errors?
I have installed armbian buster minimal. Additionally I have pihole, transmission (to seed armbian torrents https://forum.armbian.com/topic/4198-seed-our-torrents/) and syncthing running. Other programs I have not installed yet.
-
1007M swap. I don't know... This is from dmesg:
[ 24.553452] Adding 1030140k swap on /var/swap. Priority:-2 extents:5 across:3536892k SSFS
20 minutes ago, Igor said:This is my torrent server on the same 8Gb SD card.
/dev/mmcblk0p1 7458672 1058648 6297556 15% //dev/sdb1 7752457508 6878909040 482830824 94% /ext
I saw with lsblk, that sda1 has no mountpoint... that could be the reason. I will check it out.
-
Yes. I stopped the service and started it again. I rebooted my BananaPi too.
-
I did that already, but forgot to mention it.
"download-dir": "/mnt/EXTUSB/Transmission/", "incomplete-dir": "/mnt/EXTUSB/Transmission/", "incomplete-dir-enabled": true,58 minutes ago, Igor said:remove currently downloaded data which is stored on SD card, probably /var/lib/transmission-daemon/
My data is stored in /mnt/EXTUSB. There is nothing to remove in this folder and its subfolders. Please see here:
/var/lib/transmission-daemon$ sudo du -cksh * | sort -hr | head -n 5 4,0K total 4,0K downloads 0 info
I checked disk usage in my other folders . Here are my top five in / and /var:
Disk usage in /: 7,3G total 4,5G mnt - This is my external USB drive 1,8G var - 826M usr 136M lib Disk usage in /var: 1,8G total 1007M swap 413M www 231M lib 141M cache
-
Hello,
I followed the instructions for installing transmission and seed the torrents. When I then download the torrents withsudo /etc/cron.daily/seed-armbian-torrent
my internal memory is used and filled up. The torrents are stored on the external hard disk.
df -h Filesystem Size Used Avail Use% Mounted on /dev/mmcblk0p1 7,4G 7,3G 0 100% /
Normally 5.6G from the internal memory card is used. What uses this memory?
I have linked the links from transmission for blocklists, resume, torrents to my external USB hard disk to save space but it didn't help.
ls -al /var/lib/transmission-daemon/.config/transmission-daemon/ lrwxrwxrwx 1 root root 64 Apr 2 22:56 blocklists -> /mnt/EXTUSB/Transmission/.config/transmission-daemon/blocklists/ lrwxrwxrwx 1 root root 60 Apr 2 22:56 resume -> /mnt/EXTUSB/Transmission/.config/transmission-daemon/resume/ lrwxrwxrwx 1 root root 38 Jan 1 2019 settings.json -> /etc/transmission-daemon/settings.json -rw------- 1 debian-transmission debian-transmission 138 Apr 3 17:39 stats.json lrwxrwxrwx 1 root root 62 Apr 2 22:55 torrents -> /mnt/EXTUSB/Transmission/.config/transmission-daemon/torrents/
-
On 3/21/2020 at 9:05 AM, Igor said:
That is something wrong on your side. HDMI 100% works.
I found the error. It was because of my HDMI cable. With a shorter cable it works. Now my Bananapi M1 runs well.
@Igor: Sorry for the inconvenience and thanks for the quick answers. Now I share all current torrents for that SBC.
-
Thank you very much. This was really fast.
I tried different images:
- Armbian_5.90_Bananapi_Ubuntu_xenial_default_3.4.113_desktop - Green heartbeat LED flashes sometimes. No HDMI output.
- Armbian_19.11.6_Bananapi_buster_current_5.4.8_desktop - No heartbeat LED. No HDMI output.
- All new Armbian_20.02.5_Bananapi_xxxx_xxxxx_5.4.26 - No heartbeat LED. No HDMI output.
Is HDMI output enabled? Is the green heartbeat LED enabled?
I want to install some things in front of the SBC. If all is configured I want to use it headless.
Do you have some hints for me?
-
Hello,
I wanted to upgrade my Bananapi M1. So I downloaded "Buster minimal" from https://www.armbian.com/bananapi/ Last modified: 2020-02-17. I flashed the image to my SD card and started the SBC. But nothing happened. I got no heartbeat LED nor HDMI output. (I know from my Tinkerboard that I have to boot without connected HDMI to start correct. I did this with the bananapi too.) So I tried different variants: Bionic server, Buster server and Buster desktop. I never had a video output. I cross checked with my old raspian lite from 2016. With this image the Bananapi works. I used dd and Etcher for SD card preparation.
What am I doing wrong? Can I use this version with the Bananapi?
Best regards.
-
Thank you. What can I do now? How may I help?
-
On 10/31/2018 at 1:30 AM, TonyMac32 said:
We added some patches from Asus to enable some of the nicer things like CEC/etc, unfortunately someone with a similar problem apparently simply decided to start cutting wires instead of finishing the software debug. Have you tried another monitor that may have different/more limited capabilities?
I've tested it with two Full HD televisions of different brands that works when it is connected at startup. Then I checked the monitor that don't work.
On 10/31/2018 at 1:30 AM, TonyMac32 said:UART adapter on the debug UART (it is either UART 2 or 3, it changed at one point and then again after the vendor kernel issues) That will show whatever output is being produced by U-boot/the kernel (assuming it gets to the kernel but dies parsing the DT)
UART 2 with 115200 baud shows me U-Boot. Here is the recording of the monitor that works.
SpoilerU-Boot SPL 2018.07-armbian (Sep 19 2018 - 13:23:29 +0200)
Returning to boot ROM...
U-Boot 2018.07-armbian (Sep 19 2018 - 13:23:29 +0200)Model: Tinker-RK3288
DRAM: 2 GiB
MMC: dwmmc@ff0c0000: 1, dwmmc@ff0f0000: 0
Loading Environment from EXT4... Card did not respond to voltage select!
** Bad device mmc 0 **
Failed (-5)
In: serial
Out: vidconsole
Err: vidconsole
Model: Tinker-RK3288
Net: eth0: ethernet@ff290000
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
1532 bytes read in 3 ms (498 KiB/s)
## Executing script at 00000000
U-boot loaded from eMMC
178 bytes read in 3 ms (57.6 KiB/s)
43206 bytes read in 8 ms (5.1 MiB/s)
3741412 bytes read in 169 ms (21.1 MiB/s)
8546016 bytes read in 380 ms (21.4 MiB/s)
## Loading init Ramdisk from Legacy Image at 21000000 ...
Image Name: uInitrd
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 3741348 Bytes = 3.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to 0fc6e000, end 0ffff6a4 ... OK
Loading Device Tree to 0fc60000, end 0fc6d8c5 ... OKStarting kernel ...
Here is the second recording of the monitor that dont works.
SpoilerU-Boot SPL 2018.07-armbian (Sep 19 2018 - 13:23:29 +0200)
Returning to boot ROM...
U-Boot 2018.07-armbian (Sep 19 2018 - 13:23:29 +0200)Model: Tinker-RK3288
DRAM: 2 GiB
MMC: dwmmc@ff0c0000: 1, dwmmc@ff0f0000: 0
Loading Environment from EXT4... Card did not respond to voltage select!
** Bad device mmc 0 **
Failed (-5)Both outputs are equal up to the line "Failed (-5). I don't get an error message.
I checked UART 3 with 115200 baud. Here is the first with the monitor that works.
SpoilerLoading, please wait...
starting version 232
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.29.2
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: recovering journal
/dev/mmcblk0p1: Superblock last mount time is in the future.
(by less than a day, probably due to the hardware clock being incorrectly set)
/dev/mmcblk0p1: clean, 77496/894912 files, 512054/3849616 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.Welcome to Debian GNU/Linux 9 (stretch)!
[ OK ] Listening on fsck to fsckd communication Socket.
[ OK ] Started Forward Password Requests to Wall Directory Watch.
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
[ OK ] Listening on Journal Socket (/dev/log).
[ OK ] Reached target Swap.
[ OK ] Listening on Journal Socket.
[ OK ] Started Dispatch Password Requests to Console Directory Watch.
[ OK ] Listening on Syslog Socket.
[ OK ] Reached target Remote File Systems.
[ OK ] Listening on udev Control Socket.
[ OK ] Reached target Paths.
[ OK ] Created slice User and Session Slice.
[ OK ] Reached target Encrypted Volumes.
[ OK ] Listening on udev Kernel Socket.
[ OK ] Created slice System Slice.
[ OK ] Created slice system-getty.slice.
Mounting POSIX Message Queue File System...
Starting Set the console keyboard layout...
Starting Remount Root and Kernel File Systems...
Starting Journal Service...
[ OK ] Created slice system-serial\x2dgetty.slice.
Starting Create list of required st…ce nodes for the current kernel...
Mounting Debug File System...
[ OK ] Reached target Slices.
Starting Nameserver information manager...
Starting Restore / save the current clock...
Starting Load Kernel Modules...
[ OK ] Mounted POSIX Message Queue File System.
[ OK ] Mounted Debug File System.
[ OK ] Started Remount Root and Kernel File Systems.
[ OK ] Started Create list of required sta…vice nodes for the current kernel.
[ OK ] Started Restore / save the current clock.
[ OK ] Started Load Kernel Modules.
[ OK ] Started Nameserver information manager.
[ OK ] Started Journal Service.
[ OK ] Started Set the console keyboard layout.
Starting Apply Kernel Variables...
Mounting Configuration File System...
Starting Create Static Device Nodes in /dev...
Starting udev Coldplug all Devices...
Starting Flush Journal to Persistent Storage...
Starting Load/Save Random Seed...
[ OK ] Mounted Configuration File System.
[ OK ] Started Apply Kernel Variables.
[ OK ] Started Create Static Device Nodes in /dev.
[ OK ] Started Load/Save Random Seed.
[ OK ] Reached target Local File Systems (Pre).
Mounting /tmp...
Starting udev Kernel Device Manager...
[ OK ] Mounted /tmp.
[ OK ] Reached target Local File Systems.
Starting Set console font and keymap...
Starting Raise network interfaces...
Starting Armbian ZRAM config...
[ OK ] Started Flush Journal to Persistent Storage.
[ OK ] Started Set console font and keymap.
[ OK ] Started udev Kernel Device Manager.
Starting Create Volatile Files and Directories...
[ OK ] Started Create Volatile Files and Directories.
[ OK ] Reached target System Time Synchronized.
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Started Entropy daemon using the HAVEGE algorithm.
[ OK ] Started udev Coldplug all Devices.
[ OK ] Started Update UTMP about System Boot/Shutdown.
[ OK ] Found device /dev/ttyS3.
[ OK ] Found device /dev/ttyS2.
[ OK ] Reached target Sound Card.
[ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Starting Load/Save RF Kill Switch Status...
[ OK ] Started Load/Save RF Kill Switch Status.
[ OK ] Started Raise network interfaces.
[ OK ] Started Armbian ZRAM config.
Starting Armbian memory supported logging...
[ OK ] Started Armbian memory supported logging.
[ OK ] Reached target System Initialization.
Starting Armbian hardware monitoring...
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Reached target Sockets.
[ OK ] Started Daily apt download activities.
Starting Armbian hardware optimization...
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Started Daily apt upgrade and clean activities.
[ OK ] Started Run certbot twice daily.
[ OK ] Reached target Timers.
[ OK ] Started Armbian hardware optimization.
[ OK ] Started Armbian hardware monitoring.
[ OK ] Reached target Basic System.
[ OK ] Started Regular background program processing daemon.
Starting Realtek H5 bluetooth support...
[ OK ] Started D-Bus System Message Bus.
Starting LSB: Start/stop sysstat's sadc...
Starting Save/Restore Sound Card State...
Starting Certbot...
Starting LSB: Load kernel modules needed to enable cpufreq scaling...
Starting Login Service...
Starting Network Manager...
Starting System Logging Service...
[ OK ] Started Realtek H5 bluetooth support.
[ OK ] Started Save/Restore Sound Card State.
[ OK ] Started LSB: Start/stop sysstat's sadc.
[ OK ] Started Login Service.
[ OK ] Started System Logging Service.
[ OK ] Started LSB: Load kernel modules needed to enable cpufreq scaling.
Starting LSB: set CPUFreq kernel parameters...
[ OK ] Started LSB: set CPUFreq kernel parameters.
Starting LSB: Set sysfs variables from /etc/sysfs.conf...
[ OK ] Started LSB: Set sysfs variables from /etc/sysfs.conf.
[ OK ] Started Network Manager.
Starting Network Manager Wait Online...
[ OK ] Reached target Network.
Starting Permit User Sessions...
Starting A high performance web server and a reverse proxy server...
Starting OpenBSD Secure Shell server...
[ OK ] Started Unattended Upgrades Shutdown.
[ OK ] Started Permit User Sessions.
Starting Network Manager Script Dispatcher Service...
[ OK ] Started Network Manager Script Dispatcher Service.
Starting Hostname Service...
[ OK ] Started OpenBSD Secure Shell server.
[ OK ] Started Hostname Service.
Starting Authorization Manager...
Starting WPA supplicant...
[ OK ] Started Authorization Manager.
[ OK ] Started A high performance web server and a reverse proxy server.
[ OK ] Started WPA supplicant.
Starting Load/Save RF Kill Switch Status...
[ OK ] Reached target Bluetooth.
[ OK ] Started Load/Save RF Kill Switch Status.
[ OK ] Started Certbot.
[ OK ] Started Network Manager Wait Online.
[ OK ] Reached target Network is Online.
Starting LSB: Start NTP daemon...
Starting /etc/rc.local Compatibility...
Starting LSB: Advanced IEEE 802.11 management daemon...
[ OK ] Started /etc/rc.local Compatibility.
[ OK ] Started LSB: Advanced IEEE 802.11 management daemon.
[ OK ] Started Getty on tty1.
[ OK ] Started Serial Getty on ttyS3.
[ OK ] Started Serial Getty on ttyS2.
[ OK ] Reached target Login Prompts.
[ OK ] Started LSB: Start NTP daemon.
[ OK ] Reached target Multi-User System.
[ OK ] Reached target Graphical Interface.
Starting Update UTMP about System Runlevel Changes...
[ OK ] Started Update UTMP about System Runlevel Changes.Debian GNU/Linux 9 tinkerboard ttyS3
All works fine. No error messages. With the second monitor that dont works I don't get an output.
Bottom line: I can start the tinkerboard with a Full HD TV. When I connect the board to the monitor (resolution 1920 x 1200) via HDMI it does not start. I started the tinkerboard with the unplugged HDMI cable. The Tinkerboard starts normal. When the yellow and green LEDs lights up I connect the HDMI monitor. The monitor works an has the correct resolution. The board works fine.
Appendix:
I searched the internet for the message "Card did not respond to voltage select!". It seems to be a common problem with U-Boot but nobody is concerned. So I guess in my case, it's not the problem.
On 10/31/2018 at 1:30 AM, TonyMac32 said:See BayLibre's comments about the Amlogic clock system and their undocumented system supervisor core
I don't know the comment. Do you have a link?
-
Hello,
I'm observing a strange behavior. If I connect the Tinkerboard to HDMI, it won't start. Only the red led LED lights up. Yellow and green did not light up. The Tinkerboard ist connected to a NorthPada 5V 3A Micro USB Charger power supply. I measured the supply voltage with 5.3V and checked with an oscilloscope if there are voltage dips. But the voltage was stable.
I did a cross test. I unplugged the HDMI cable and started the Tinkerboard. The Tinkerboard starts and the yellow and green LEDs lights up. I measured the supply voltage with 5.3V and checked with an oscilloscope if there a voltage dips. The voltage was stable and dropped to roughly 5.1V for a short time when the green LED flashed. I can connect the HDMI monitor and work with it. The board works fine.
I use Armbian_5.59_Tinkerboard_Debian_stretch_next_4.14.67
How can I check what's going wrong and where the Tinkerboard stucks in the boot process.
Whats wrong with the HDMI? -
Banana Pi M1 is in that range. It depends on your application. Do you want a cheap SBC or do you have an application where you need more power?
-
5 hours ago, martinayotte said:
Check if this file has corruption too : /etc/resolvconf/resolv.conf.d/original
I found /etc/resolvconf/resolv.conf.d/head. I fixed it there, rebooted and it works. Thanks a lot!
-
I use "Armbian_5.59_Tinkerboard_Debian_stretch_next_4.14.67". After every reboot the line for the nameserver in resolv.conf looks like this:
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@nameserver 192.168.3.1
When I delete all ^@ chars my networks works fine. After reboot the characters are inserted again. I tried "chmod 444 resolv.conf" but after reboot resolv.conf has 644 again. How can I correct this? What is the problem with my installation?
Best regards.
Why shows inxi -i the backbone of my provider?
in Software, Applications, Userspace
Posted
I use my Banana Pi with pihole. There I see different IF-IDs.
1) What are IF-IDs? I assume Interface IDs. On my Laptop I don't see that. There are only IFs.
2) The speed of IF-ID-1 and -3 are 10000 Mbps. My Banana Pi M1 has only 100 Mbps. What is the sense of this?
3) The WAN IP of IF-ID-3 shows with whois that this is a Backbone of Vodafone. How could this be, that I see this?
inxi -i Network: Device-1: sun7i-a20-gmac driver: sun7i_dwmac IF: eth0 state: up speed: 100 Mbps duplex: full mac: 02:cd:02:41:f1:17 IP v4: 192.168.178.5/24 type: dynamic noprefixroute scope: global IP v6: fe80::a8fc:3ac5:236d:9a08/64 type: noprefixroute scope: link Device-2: sun4i-a10-emac driver: N/A IF: eth0 state: up speed: 100 Mbps duplex: full mac: 02:cd:02:41:f1:17 IP v4: 192.168.178.5/24 type: dynamic noprefixroute scope: global IP v6: fe80::a8fc:3ac5:236d:9a08/64 type: noprefixroute scope: link IF-ID-1: br-c5313994639f state: up speed: 10000 Mbps duplex: unknown mac: 02:42:5e:a7:db:07 IP v4: 172.18.0.1/16 scope: global IP v4: 169.254.26.87/16 type: noprefixroute scope: global IP v6: fe80::dcd1:baf2:cbe0:ee55/64 scope: link IF-ID-2: docker0 state: down mac: 02:42:b7:ad:fd:8e IP v4: 172.17.0.1/16 scope: global IF-ID-3: veth7c401b9 state: up speed: 10000 Mbps duplex: full mac: 82:f2:6e:c4:3a:5c WAN IP: 178.11.164.65