Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
  • Location

Recent Profile Visitors

11042 profile views
  1. Normally when you have installed a XFCE-Desktop image for the Pinebook A64 you could set the display brigthness with the following pkexec command to a readable higher level - like I did in the past (possible brightness values are 1-10 - on startup this is only set to 2): pkexec /usr/sbin/xfpm-power-backlight-helper --set-brightness 8 read-out command for the current value: pkexec /usr/sbin/xfpm-power-backlight-helper --get-brightness but on standard CLI-install pkexec and xfpm-power-backlight-helper are missing, so to use this command-line (in /etc/rc.local) you have to install these 2 packages: sudo apt install xfce4-power-manager pkexec
  2. Couldnt get the USB-Gigabit-Ethernet to work after/in a passive USB-Hub The Kernel (3.1.x) seem to have no support for a CIFS/Samba-Mount I had problem after update to bookworm with the openssh-server (only connection reset) and so I installed dropbear and vsftpd (because openssh-sftp was also deinstalled with openssh-server) lsusb Bus 001 Device 003: ID 2001:f103 D-Link Corp. DUB-H7 7-port USB 2.0 hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 302.008300] usb 1-1: new high-speed USB device number 4 using musb-hdrc [ 302.152099] hub 1-1:1.0: ignoring external hub [ 388.976745] usb 1-1: new high-speed USB device number 18 using musb-hdrc [ 389.124877] hub 1-1:1.0: ignoring external hub
  3. @whitefeather Its a long time ago - but did read this read today again and found a debian bulleye image (v1.37) on his page from March 2023 ; Debian Bullseye Image v1.37 So maybe that will give a "new life" for my i96 more /proc/cpuinfo Processor : ARMv7 Processor rev 1 (v7l) processor : 0 model name : ARMv7 Processor rev 1 (v7l) BogoMIPS : 370.93 Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc05 CPU revision : 1 Hardware : rda8810 Revision : 0000 Serial : 0000000000000000
  4. @Vidor armbian may see/use the RTL8188CUS as RTL8192CUS like on my Logilink WL0084A (which should have a RTL8188CUS): TP-LINK TL-WN725N Rev V1 - RTL8188EU [247548.026879] usb 1-1: new high-speed USB device number 3 using ehci-platform [247548.186436] usb 1-1: New USB device found, idVendor=0bda, idProduct=8179, bcdDevice= 0.00 [247548.187113] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [247548.187144] usb 1-1: Product: 802.11n NIC [247548.187170] usb 1-1: Manufacturer: Realtek [247548.388942] r8188eu: module is from the staging directory, the quality is unknown, you have been warned. [247548.498252] usbcore: registered new interface driver r8188eu [247549.167691] r8188eu 1-1:1.0: Firmware Version 11, SubVersion 1, Signature 0x88e1 Logilink WL0084A - RTL8188CUS - like TP-LINK TL-WN725N Rev V2/V3 [247297.741636] usb 1-1: Product: 802.11n WLAN Adapter [247297.741675] usb 1-1: Manufacturer: 802.11n WLAN Adapter [247298.168480] rtl8192cu: Chip version 0x10 [247298.465056] rtl8192cu: Board Type 0 [247298.466340] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1 [247298.467873] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin [247298.470442] ieee80211 phy1: Selected rate control algorithm 'rtl_rc' [247298.479578] usbcore: registered new interface driver rtl8192cu So there are good chances that you adapter will work
  5. @Vidor this may depend on the hardware-revision do you get at this time the are 3 versions V1 has the Realtek RTL8188CUS as chipset http://en.techinfodepot.shoutwiki.com/wiki/TP-LINK_TL-WN725N_v1 and the V2 and V3 seems to have the Realtek RTL8188EUS as chipset http://en.techinfodepot.shoutwiki.com/wiki/TP-LINK_TL-WN725N_v2
  6. normally the font and font-size can be reconfigured from the hdmi-console via dpkg-reconfigure console-setup
  7. I also had this issue the last time I reinstalled the build-system. I have a 18MBit line, but do not get from all servers >= 500Kb sec. It depends on the country. As Iam in turkey - most servers are very slow and if I have the chance (like on debian install) I choose the servers in Germany which are much faster for me (up to 1800Kb/sec), but armbian didnt let choose me
  8. I also use a Orange Pi One as PiHole without problems. As Backup a NanoPi A64 is also running here PiHole if the Orange Pi One is down
  9. At the page https://myr2d2build.com/build/issues-91-100/issue-99/ we could see thats the R2D2 Board (which was in Issue 99) is a board from the company named "Orange Pi" named ROBOT v1.2 , but the pictures arent sharp enough to read more. If the Board contains a SDCard and not only emmc then it could be more easy to replace the sounds.
  10. The Kernel 6.0.10 is working for me here. Only got the problems with the not installed DTBs/Overlays - the Neo2 DTBs/Overlays I copied out of the NanoPi A64 install with Kernel 6.0.10 With 6.0.10 I can wait for 6.1 to come Linux npi-neo2-24 6.0.10-sunxi64 #22.11.1 SMP Wed Nov 30 11:26:36 UTC 2022 aarch64 GNU/Linux
  11. Today I had the same problem with my two Neo2 v1.0 After Update/Reboot the director /boot/dtb/allwinner/overlay was completly missing for dtb-6.0.10-sunxi64 (and the directory /boot/dtb-6.0.10-sunxi64/allwinner/ has only -dtb files from the end of Noveber (maybe they are right)) But Iam was in the lucky case that my NanoPi A64 had upgraded successfully to 6.0.10 and all the dtb-files including the overlay-folde for 6.0.10 was there. So I copied these files over to /boot/dtb/allwinner (symbolic link dtb => dtb-6.0.10-sunxi64) and by restarting the Neo2 v1.0 did boot again, because of the missing overlays .dtbo/.scr the Neo2 V1.0 wasnt booting only to emergency mode If anyone need the dtb-directory for sunxi64 and Kernel 6.0.10 I will attach they here at this thread. I dont know whats the difference between the Neo2 and the NanoPi A64 (both sunxi64). The upgrade to 6.0.10 did also work fine on a Orange Pi Zero (sunxi only) allwinner60.zip
  12. @Nefedorov Sorry - I have no clue about it. For the 5102 I corrected the .DTBs with some other user to make it work. I have no idea abot TDM and how to use 4 soundcards at once
  13. Because I didnt want a end0: as eth0: device on my NanoPi A64 I added extraargs=net.ifnames=0 to my /boot/armbianEnv.txt But on bootup the armbian-motd told me RX today: Error: No interface matching "eth0" found in database. The armbian-motd in /etc/default has the line PRIMARY_INTERFACE="$(ls -1 /sys/class/net/ | grep -E "en|eth|wl" -m 1)" On the commandline I do get a clear etho with this command: root@npi-a64-116:~# ls -1 /sys/class/net/ | grep -E "en|eth|wl" -m 1 eth0 Where is "the database"? and why have we an end0: device (and not and enx?) [EDIT] found how to add the eth0 to the database (on my other SBCs is was already there). The command is: vnstat --add -i eth0 in the thread System diagnosis information has been uploaded to https://paste.armbian.com/etodezihuf
  14. As Caution-Information: Today I updated a NanoPi Neo 2 v1.1 with armbian bullseye bleeding edge-kernel-setting via apt update/upgrade from Kernel 5.19.16 to 6.0.10 (also from armbian 22.08 to armbian 22.11.1) and had a no-boot after restart serial-TTL-Log after reboot: The problem was (the system did work fine before incl. restart etc), that the file /boot/dtb/allwinner/sun50i-h5-nanopi-neo2-v1.1.dtb was missing - and also the complete directory /boot/dtb/allwinner/overlay/ including /boot/dtb/allwinner/overlay/sun50i-h5-usbhost1.dtbo /boot/dtb/allwinner/overlay/sun50i-h5-usbhost2.dtbo /boot/dtb/allwinner/overlay/sun50i-h5-fixup.scr was also mising I had to open my silver-Neo2-NAS-case, extract the SDCard and copy this file and directory from ym other Neo2 (under kernel 5.19.16) over to the SDcard from ym Neo 2 v1.1 So I dont know if I get the same problem, when I try to update my 2 Neo 2 v1.0 Anyone else had bootup-lockup(s) after the 22.11 update?
  15. I can recommend the USB Image Tool: Info-Page: https://www.alexpage.de/usb-image-tool/ Download at: https://www.alexpage.de/usb-image-tool/download/
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines