Jump to content

Quantum

Members
  • Posts

    22
  • Joined

  • Last visited

Everything posted by Quantum

  1. Unfortunately I am not a coder. I will depend on this method for the foreseeable future. I like the idea of the blue light showing disk activity. I did set aside /extlinux but then it fails the same old way.
  2. Ok, I don't understand this but it works for me, I'd like to help others but don't know how this works.
  3. YES!! Boots just fine, resizes the partition, asks all the questions and I can log in and get root. No failed systemd services and top is the top process in top. Did an update and upgrade, rebooted, and it's fine. Only thing is no blue light, at all. Do I have to do all of this forever?
  4. sda 8:0 1 116.5G 0 disk └─sda1 8:1 1 1.9G 0 part 9e5054cd-01
  5. I had hope, but same old problem. # dd if=/home/bill/dl/Armbian_22.02.2_Odroidn2_bullseye_current_5.10.103.img of=/dev/sda bs=4M status=progress # tar -xzf u-boot-meson.tgz # dd bs=512 seek=1 conv=notrunc,fsync if=u-boot-meson.bin of=/dev/sda Put in the card, plug it in, and it drops to (initramfs).
  6. file-upload.net got a big red warning page on Firefox as hosting harmful files. And your file is only 600kB?
  7. Igor just takes the saveset straight from Debian's ARM port and builds it their way: So you go for this, compile your own and settle for CLI. Nah, (initramfs) again. Well having something is better than nothing, right? You settle for Armbian_21.08.1_Odroidn2_bullseye_current_5.10.60.img . Yay, it boots! But think you're going to be a smartazz and do an apt full-upgrade? Sure, it works. But reboot... and now you are at (initramfs) again, and dead in the water. Fail.
  8. So for those who have the Odroid N2+, Armbian is not maintained. I've tested most releases and found that they stopped working at Armbian_21.08.9_Odroidn2 If you choose an Ubu image 21.08.1 or older, it works but you can't get updates because they're no longer on Ubu's site. It may be that the N2 still works, but the N2+ certainly doesn't. I don't know any more about what to do about this.
  9. Yes the Mate image works fine. Also does one from c0rnelius in IRC. It is definitely an Armbian problem, but it seems that Igor has better things to do.
  10. Nobody else has an n2 or n2+. No current Armbian image works.
  11. Unfortunately console does not work. I have to power down the N2+ and put the SD card in my laptop to pull logs. How is it that this log is not informative? What else can I do? No Armbian image works on the N2+.
  12. Armbian_22.05.4_Odroidn2_jammy_current_5.10.123_xfce_desktop.img ... comes up with the Armbian logo and circling dots... But the dots go on for an hour and a half. Here's what /var/log/bootstrap.log looks like.
  13. I think it can't work because I have a TB S. And none of the rest of you has an S. So Armbian is busted with the TB S. Yes, and manual setup was what I fell back to after NetworkManager, connman, and nmtui failed. eth0 worked fine, but no matter how I set up wpa and wlan0 it would not associate. It would try, but fail with Reason 11. (regulatory not met) I manually copied regulatory.db and regulatory.db.t4k into /lib/firmware but boot still couldn't find it. With a clean install and then nmtui, eth0 gets the right static IP, but it is incommunicado with the rest of the network, even after reboot. This is a lost cause. I've wasted over a week on a fool's errand. I should have known better than to mess with Debian again, and just learned how to compile u-boot for Fed.
  14. Most current Armbian Armbian_5.75_Tinkerboard_Debian_stretch_next_4.19.20, sha256sum verified. Plug USB cable between TB and laptop, and /dev/sdb appears in dmesg. # dd if=Armbian_5.75_Tinkerboard_Debian_stretch_next_4.19.20.img of=/dev/sdb bs=4M status=progress Take to testbed, plug into eth0 and USB power, it boots to command-line with no fluctuation of red light or power-sag messaged. (3A wall wart) Boots. Set wlan0 up like the attached, save, but it is NOT in Activate. Reboot and wlan0 has no static IP and in nmtui it is NOT in activate. I am confident now that this is because I have a TB S. And none of the rest of you has an S. So Armbian is busted with the TB S. Can I help with a lshw? I'd love to, but after the clean install and nmtui, eth0 gets the right IP but is incommunicado. That is enough.
  15. I always work as root for config. I've run Linux exclusively for 22 years. I ran Debian for 15 of those years, but packages weren't updated so I went to CentOS. Now it looks to me like Debian has descended into chaos. Thanks, but wpa_cli has 156 commands. I've already lost a week full-time tryin to set up this wifi interface using every other method that exists, each one failing in one way of another. Are you saying that nmtui will add a wifi WPA2 interface for you successfully? Have you tried this with the current Armbian saveset?
  16. I now remember discovering nmtui in the past two weeks and trying that too. I can add and set up the wifi interface just fine. But when I go to Activate it... it's not there. Stop/restart nmtui and the interface is still in Add... but only eth0 is in Activate. Maybe this Armbian is impractical/impossible. Why does everyone say that nmtui works for wifi when it doesn't? Or is it that it doesn't work on the current release?
  17. I now remember discovering nmtui in the past two weeks and trying that too. I can add and set up the wifi interface just fine. But when I go to Activate it... it's not there. Stop/restart nmtui and the interface is still in Add... but only eth0 is in Activate. Maybe this Armbian is impractical/impossible. Why does everyone say that nmtui works for wifi when it doesn't? Or is it that it doesn't work on the current release?
  18. Trying to reach a headless TinkerBoard with X2Go so I can set up wifi. SELinux is disabled. I can SSH in as my user just fine, with and without -i, but when setting the Pyhoca session to "Discover SSH Keys", I get "Not a valid EC private key file!" Ok, apparently it wants an elliptic curve key. It never used to accept anything but DSA and RSA. So I made an ecdsa keypair and ssh-copy-id to the TB. Same failure. I know that X2Go can't handle ed25519 unfortunately, so I don't even have that key for my user. When setting the Pyhoca session SSH key manually to /home/bill/.ssh/id_rsa or /home/bill/.ssh/id_ecdsa, I get, "Not a valid EC private key file!" When not setting the Pyhoca session SSH key either way, and password is allowed on the TB server, it comes up with a dialog box asking for password, and when I enter the correct one I get, "Authentication failed!" Needless to say, all three methods work on the commandline. Showstopper because I can't configure wifi without NetworkManager and NetworkManager requires a GUI, and this machine is headless. Researched this to the ends of the Earth, but the issues were X2Go from a Windows client (I'm CentOS), a permissions problem on keys or .ssh, or ssh_config forwarding was disabled. None apply here. #x2go irc is moribund, and the dev left to do the dishes.
  19. No idea what forums are available here. Going to https://forum.armbian.com/forum/ I get, "The page you requested does not exist". My only other option is Active Threads, and I feature there already.
  20. Yup your system is running, looks like about 10 times armbianmonitor got run. But it doesn't say anything about wifi setup. I can't get into LXQt using X2Go due to an auth failure which only happens in X2Go, no matter with SSH key automatic, manual, or password. With command-line no problem. SSH is set to accept either, but X2Go won't have it. This TB is headless.
  21. I tried first the armbian-setup, but it has no provision for WPA2 so it can't connect. WPA2 is the hard part. Also, being in Washington and after setting my timezone to L.A., I try to change my repository from Estonia, but my only other choices are China and Bulgaria. Then I tried NetworkManager, but apparently it's GUI only and there doesn't seem to be an app for LXQt. Then I stopped/disabled NM and installed ConnMan. I couldn't make that work and I can't remember why, I believe it was because it would not allow me to set a static IP, which is necessary. So I was left with trying to do it manually, which I've now failed with. I'm installing the Armbian image into eMMC, and then updating with the Armbian cli/ascii system, and then installing LXQt. I was aware of armbianmonitor -u, but: # armbianmonitor -u Network/firewall problem detected. Not able to upload debug info. Please fix this or use "-U" instead and upload whole output manually System diagnosis information will now be uploaded to gzip: /var/log/armbian-hardware-monitor.log.1.gz: No such file or directory curl: (6) Could not resolve host: ix.io Please post the URL in the forum where you've been asked for. (For some reason the forum software would not allow me to put the above two into the same code block) I'm coming in on eth0 which does not have gateway set, as wlan0 is supposed to be doing that. I can no longer bring up wlan0 with the current manual config, as above. I can't imagine why this is so difficult.
  22. Tinker Board S, Armbian 5.75, 4.19.20 I've spent a week now full-time trying to make this busted thing work. The closest I've come is setting everything for roaming. /etc/network/interfaces.d/wlan0 iface wlan0 inet manual wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf wpa-driver wext iface mercury inet dhcp iface home inet static address 10.2.1.22 netmask 255.255.255.0 network 10.2.1.0 gateway 10.2.1.1 #post-up #Schnittstelle automatisch aktivieren auto wlan0 /etc/wpa_supplicant/wpa_supplicant.conf # Will automatically select the best network based on the order of network blocks, # network security level (WPA/WPA2 is preferred), and signal strength. ctrl_interface=/run/wpa_supplicant ap_scan=2 # Go directly to the hidden SSID network={ ssid="mercury" id_str="mercury" psk={ ... } } network={ ssid="sirius24" id_str="home" scan_ssid=1 proto=RSN key_mgmt=WPA-PSK pairwise=CCMP group=TKIP CCMP psk="{ ... }" #psk={ ... } } # dmesg ... [Tue Feb 12 14:49:18 2019] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [Tue Feb 12 14:49:18 2019] cfg80211: failed to load regulatory.db ... even though I've put regulatory.db, regulatory.db.5, and regulatory.db.p7s into /lib/firmware.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines