Jump to content

phier

Members
  • Posts

    39
  • Joined

  • Last visited

Everything posted by phier

  1. @Igor thank you, i will try to upgrade kernel firstly. Also can I found that specific model of that usb2sata converter and see if its blacklisted or not? Maybe there is some list of good working usb2sata converters... no idea ;/ wanted to upgrade to 5.4.125 but there is missing package of linux-sources of 5.4.125 ... so will not work again... linux-headers-current-odroidxu4/buster 21.05.4 armhf Linux kernel headers for 5.4.125-odroidxu4 on armhf linux-image-current-odroidxu4/buster 21.05.4 armhf Linux kernel, version 5.4.125-odroidxu4 @Werner i tried > http://ix.io/3uqK thanks
  2. Hi, running armbian debian Linux odroid-backup 4.14.222-odroidxu4 ; and having attached 2x 3.5" disks i am getting so many disconnects in dmesg log paste.debian.net/1205714/ Is that armbian / kernel / or odroid issue? So i can further investigate. thank you
  3. No idea why, but on odroid xu4 Armbian 21.05.4 Buster with Linux 4.14.222-odroidxu4 the file /boot/armbianEnv.txt is missing. boot from UART ## Executing script at 43e00000 ** File not found /boot/armbianEnv.txt ** ** Unrecognized filesystem type ** ** File not found armbianEnv.txt **
  4. the fresh install was done from image Armbian_21.05.1_Odroidxu4_buster_legacy_4.14.222.img then i upgrade via apt update; upgrade... so it moved to Armbian 21.05.6 Buster with Linux 4.14.222-odroidxu4 and the error reported above started to happen constantly. I installed again directly Armbian 21.05.6 Buster with Linux 4.14.222-odroidxu4 and it works... strange issue.
  5. hello, any idea what kind of issue it might be / how to fix it? after execution reboot cmd it got stuck > error below Welcome to Armbian 21.05.6 Buster with Linux 4.14.222-odroidxu4 root@odroid-monitor:~# reboot [ 49.378939] reboot: Rest! U-Boot 2017.05-armbian (May 06 2021 - 18:13:45 +0000) for ODROID-XU4 CPU: Exynos5422 @ 800 MHz Model: Odroid XU4 based on EXYNOS5422 Board: Odroid XU4 based on EXYNOS5422 Type: xu4 DRAM: 2 GiB Error binding driver 'gpio_exynos': -12 Error binding driver 'gpio_exynos': -12 Error binding driver 'gpio_exynos': -12 Error binding driver 'gpio_exynos': -12 Error binding driver 'gpio_exynos': -12 Some drivers failed to bind initcall sequence be9af240 failed at call 43e18010 (err=-12) ### ERROR ### Please RESET the board ###
  6. @Werner the bug I reported is related to the in-built wifi card on banana m1+ board; its not 3rd party hw. The issue which is happening also on 3rd party hw was attached onlyfor your information that it might be kernel or also user space bug.
  7. is there any plan for a fix? also i tried usb wifi but this one is constantly dropping .... [ 955.206493] usb 1-1: new high-speed USB device number 4 using ehci-platform [ 955.252439] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x2, status: 0x0, addr: 0x34, flags: 0x0 [ 955.368151] usb 1-1: New USB device found, idVendor=0bda, idProduct=8176, bcdDevice= 2.00 [ 955.368168] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 955.368174] usb 1-1: Product: 802.11n WLAN Adapter [ 955.368180] usb 1-1: Manufacturer: Realtek [ 955.368188] usb 1-1: SerialNumber: 00e04c000001 [ 955.373535] rtl8192cu: Chip version 0x10 [ 955.471500] rtl8192cu: Board Type 0 [ 955.471707] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1 [ 955.471851] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin [ 955.471984] ieee80211 phy3: Selected rate control algorithm 'rtl_rc' [ 955.486577] rtl8192cu: MAC auto ON okay! [ 955.530016] rtl8192cu: Tx queue select: 0x05 [ 958.729813] wlan1: authenticate with b0:b9:8a:4d:96:38 [ 958.759936] wlan1: send auth to b0:b9:8a:4d:96:38 (try 1/3) other usb wifi card> same behavior as internal wifi ie not connecting at all [ 176.579021] usb 1-1: New USB device found, idVendor=0bda, idProduct=8171, bcdDevice= 2.00 [ 176.579034] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 176.579041] usb 1-1: Product: RTL8188S WLAN Adapter [ 176.579047] usb 1-1: Manufacturer: Manufacturer Realtek [ 176.579054] usb 1-1: SerialNumber: 00e04c000001 [ 176.646620] r8712u: module is from the staging directory, the quality is unknown, you have been warned. [ 176.654156] r8712u: register rtl8712_netdev_ops to netdev_ops [ 176.654187] usb 1-1: r8712u: USB_SPEED_HIGH with 4 endpoints [ 176.655147] usb 1-1: r8712u: Boot from EFUSE: Autoload OK [ 177.365150] usb 1-1: r8712u: CustomerID = 0x0000 [ 177.365165] usb 1-1: r8712u: MAC Address from efuse = 00:13:33:b2:e5:08 [ 177.365173] usb 1-1: r8712u: Loading firmware from "rtlwifi/rtl8712u.bin" [ 177.365419] usbcore: registered new interface driver r8712u [ 177.429613] r8712u 1-1:1.0 wlx001333b2e508: renamed from wlan1 [ 178.360775] r8712u 1-1:1.0 wlx001333b2e508: 1 RCR=0x153f00e [ 178.361502] r8712u 1-1:1.0 wlx001333b2e508: 2 RCR=0x553f00e Basically pc is unusable at all otherwise then using ethernet. thanks
  8. root@bananapi:~# armbianmonitor -u System diagnosis information will now be uploaded to unterminated quoted string at or near "'\x0a232323204163746976617465642031206c7a6f2d726c65207a72616d20737761702064657669636573207769746820343938204d4220656163680a0a232323204163746976617465642041726d6269616e2072616d6c6f6720706172746974696f6e2077697468207a73746420636f6d7072657373696f6e0a0a53756e203133204a756e20323032312030363a31373a333220504d20555443207c2042616e616e61205069207c' 073797374656d645b315d3a204c697374656e696e6" LINE 7: '\x0a232323204163746976617465642031206c7a6f2... ^ Please post the URL in the forum where you've been asked for. broken also hah Second try > System diagnosis information will now be uploaded to http://ix.io/3qg3 And i am going to try it with kernel 5.10.
  9. this is all on 5.4.88-sunxi ; i will try 5.10, well yes, i cant use 5.10x+ as ZFS is broken there.
  10. 1769]: Failed to create interface p2p-dev-wlan0: -5 (Input/output error) 1769]: nl80211: Failed to create a P2P Device interface p2p-dev-wlan0 1769]: P2P: Failed to enable P2P Device interface 1769]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Int> 1769]: wlan0: Trying to associate with SSID 'OpenWrt' 1769]: wlan0: WPA: Failed to select authenticated key management type 1769]: wlan0: WPA: Failed to set WPA key management and encryption suites 1769]: wlan0: Trying to associate with SSID 'OpenWrt' 1769]: wlan0: WPA: Failed to select authenticated key management type 1769]: wlan0: WPA: Failed to set WPA key management and encryption suites
  11. on latest ubuntu it does > Could not activate connection: │ │ │ │ st│ Activation failed: The Wi-Fi │ │ │ │ RE│ network could not be found
  12. I dont think so, when i was running OS Bananian it worked fine and i was able connect to the same AP via WPA2
  13. yes apt update && upgrade but apparently Error: Unable to read database "/var/lib/vnstat/wlan0": No such file or directory Merge "eth0+wlan0" failed. is another bug as the one i reported ie its not connecting to the AP using WPA2
  14. Hi, after login the error> RX today: Error: Unable to read database "/var/lib/vnstat/wlan0": No such file or directory Merge "eth0+wlan0" failed. When i try to connect to WIFI network via armbain-configure -> WIFI ; network selected + password provided I got error> Passwords or encryption keys are required to access the │ │ wireless network 'OpenWrt'. second / third try> Could not activate connection: │ │ │ │ │ Activation failed: Secrets were │ │ │ │ │ required, but not provided root@bananapi:~# cat /var/lib/vnstat cat: /var/lib/vnstat: Is a directory root@bananapi:~# iwconfig wlan0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=31 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off I can connect to router1 (generic box from provider) wpa-psk but I cant connect to router2 running openwrt 2.4ghz channel 9... wpa2-psk Somone had same issue - no one cared.... journalctl -xe Jun 17 15:56:17 bananapi NetworkManager[1259]: <info> [1623945377.8507] device (wlan0): supplicant interface state: scanning -> associating Jun 17 15:56:18 bananapi wpa_supplicant[1246]: wlan0: CTRL-EVENT-ASSOC-REJECT bs sid=00:00:00:00:00:00 status_code=16 Jun 17 15:56:18 bananapi wpa_supplicant[1246]: wlan0: CTRL-EVENT-SSID-TEMP-DISAB LED id=0 ssid="OpenWrt" auth_failures=2 duration=20 reason=CONN_FAILED Jun 17 15:56:18 bananapi NetworkManager[1259]: <info> [1623945378.5012] device (wlan0): supplicant interface state: associating -> disconnected Jun 17 15:56:28 bananapi NetworkManager[1259]: <info> [1623945388.6097] device (wlan0): supplicant interface state: disconnected -> scanning Jun 17 15:56:30 bananapi NetworkManager[1259]: <warn> [1623945390.4327] device (wlan0): Activation: (wifi) association took too long Jun 17 15:56:30 bananapi NetworkManager[1259]: <info> [1623945390.4367] device (wlan0): state change: config -> failed (reason 'no-secrets', sys-iface-state: ' managed') Jun 17 15:56:30 bananapi NetworkManager[1259]: <warn> [1623945390.4442] device (wlan0): Activation: failed for connection 'OpenWrt' Jun 17 15:56:30 bananapi NetworkManager[1259]: <info> [1623945390.4482] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: ' managed') Jun 17 15:56:31 bananapi NetworkManager[1259]: <info> [1623945391.2775] device (wlan0): supplicant interface state: scanning -> disconnected systemctl status wpa_supplicant Jun 17 16:21:45 bananapi systemd[1]: Starting WPA supplicant... Jun 17 16:21:45 bananapi wpa_supplicant[3821]: Successfully initialized wpa_supplicant Jun 17 16:21:45 bananapi systemd[1]: Started WPA supplicant. Jun 17 16:21:47 bananapi wpa_supplicant[3821]: Failed to create interface p2p-dev-wlan0: -5 (Input/output error) Jun 17 16:21:47 bananapi wpa_supplicant[3821]: nl80211: Failed to create a P2P Device interface p2p-dev-wlan0 Jun 17 16:21:47 bananapi wpa_supplicant[3821]: P2P: Failed to enable P2P Device interface journalctl -xe -- The job identifier is 1102. Jun 17 16:21:45 bananapi nm-dispatcher[3823]: req:1 'down' [wlan0]: new request (3 scripts) Jun 17 16:21:45 bananapi nm-dispatcher[3823]: req:1 'down' [wlan0]: start running ordered scripts... Jun 17 16:21:47 bananapi wpa_supplicant[3821]: Failed to create interface p2p-dev-wlan0: -5 (Input/output error) Jun 17 16:21:47 bananapi kernel: ieee80211 phy0: brcmf_p2p_create_p2pdev: timeout occurred Jun 17 16:21:47 bananapi kernel: ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev-wlan0 type 10 failed: err=-5 Jun 17 16:21:47 bananapi wpa_supplicant[3821]: nl80211: Failed to create a P2P Device interface p2p-dev-wlan0 Jun 17 16:21:47 bananapi wpa_supplicant[3821]: P2P: Failed to enable P2P Device interface Jun 17 16:21:47 bananapi NetworkManager[1259]: <info> [1623946907.2591] sup-iface[0xa32608,wlan0]: supports 5 scan SSIDs Jun 17 16:21:47 bananapi NetworkManager[1259]: <info> [1623946907.2686] device (wlan0): supplicant interface state: starting -> ready Jun 17 16:21:47 bananapi NetworkManager[1259]: <info> [1623946907.2690] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface Jun 17 16:21:48 bananapi nm-dispatcher[3823]: Eth0 Eth0stat 2 2 IN-USE SSID MODE CHAN RATE SIGNAL BARS SECURITY router2 Infra 9 260 Mbit/s 97 **** WPA2 router1 Infra 2 130 Mbit/s 80 *** WPA1 WPA2
  15. uboot reads /boot/armbianEnv.txt & kernel images from the first partition marked as bootable (fdisk). Rootfs can be changed by updating armbianEnv.txt (on the first bootable partition) rootdev=UUID to boot from any partition.
  16. fixed echo "zfs-dkms zfs-dkms/stop-build-for-32bit-kernel boolean false" | debconf-set-selections
  17. it looks like the bug is in the package; as install meant to be interactive; its not and by default N is chosen as not continue ;/ Okay It has to be armbian bug. root@bananapi:~# man debconf-show root@bananapi:~# debconf-show zfs-dkms * zfs-dkms/note-incompatible-licenses: * zfs-dkms/stop-build-for-32bit-kernel: true zfs-dkms/stop-build-for-unknown-kernel: true https://github.com/openzfs/zfs/issues/12243 On armbian - ubuntu - it was interactive; on armbian debian - it just goes thru the wrong branch and no interaction by user https://salsa.debian.org/zfsonlinux-team/zfs/-/blob/master/debian/zfs-dkms.postinst#L18 thanks looks like there are headers/ img for almost all the versions.
  18. It wont help, 5.10x has a bug with alsa so plug plugin is broken (edit in debian it works, on ubuntu its broken... ) also there is another bug with zfs in ubuntu 5.10 (kernel has to be downgraded) on debian doesnt work. zfs on debian > 5.10.34-sunxi Setting up zfs-dkms (2.0.3-1~bpo10+1) ... Ok, aborting, since ZFS is not designed for 32-bit kernels. The only solution is 4.19.59 or anything <5 but apparently for all of these headers / sources are missing. Also on debian kernel headers between 5.4 < 5.10 are missing completely. linux-headers-current-sunxi/buster 21.05.1 armhf Linux kernel headers for 5.10.34-sunxi on armhf linux-headers-dev-sunxi/buster 21.02.3 armhf Linux kernel headers for 5.11.3-sunxi on armhf linux-headers-edge-sunxi/buster 21.08.0-trunk.71 armhf Linux kernel headers for 5.12.10-sunxi on armhf edge linux-headers-legacy-sunxi/buster 21.05.1 armhf Linux kernel headers for 5.4.88-sunxi on armhf Maybe the only solution is to build it using build script.
  19. Hi, its seems that maybe 80% is missing? i dont know, i downloaded latest stable debian Armbian_5.91_Bananapi_Debian_buster_next_4.19.59.img and headers are missing ... ie not much can be compiled. I assume that one is recent. Even linux source is missing. root@bananapi:~# uname -a Linux bananapi 4.19.59-sunxi #5.91 SMP Mon Jul 15 14:09:32 CEST 2019 armv7l GNU/Linux linux-image-next-sunxi - Linux kernel, version 4.19.59-sunxi So basically such a distribution is unusable... as one cant compile anything on it related to the kernel... and as someone compiled kernel 4.19.59-sunxi I assume the headers were there... So it means i have to compile kernel from scratch again ... to get headers.
  20. Hi, is there some specific reason why there is a kernel linux-source-5.8.16-sunxi as part of packages repository, but headers for such a version are missing? I saw similar post https://forum.armbian.com/topic/8347-install-linux-headers/ without any solution, but if there is a kernel package why the headers are missing? I assume headers were used during the build process... thanks
  21. hi, these is mostly about how to fully re-flash uboot; but how can one re-configure uboot ie access its env variables?
  22. is there any update regarding to that?
  23. hi, where exactly is stored uboot env storage? How can i read/modify it using fw_printenv/fw_setenv ? thanks
  24. so apparently its some armbian secret.
  25. Even i made /dev/mmcblk0p2 * bootable; edited its /etc/fstab & /boot/armbianEnv.txt with proper UUID of /dev/mmcblk0p2 it got booted from /dev/mmcblk0p1 after reboot. https://github.com/u-boot/u-boot/blob/master/doc/README.distro Distros simply need to install the boot configuration files (see next section) in an ext2/3/4 or FAT partition, mark the partition bootable (via the MBR bootable flag, or GPT legacy_bios_bootable attribute), and U-Boot (or any other bootloader) will find those boot files and execute them. This is conceptually identical to creating a grub2 configuration file on a desktop PC. Device Boot Start End Sectors Size Id Type /dev/mmcblk0p1 8192 10493951 10485760 5G 83 Linux /dev/mmcblk0p2 * 10493952 31116287 20622336 9.9G 83 Linux
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines