Jump to content

Search the Community

Showing results for tags 'solved'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Product Groups

  • Misc
  • Support

Categories

  • Armbian
  • Armbian releases

Categories

  • Volunteering opportunities

Calendars

  • Community Calendar

Categories

  • Members

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

  1. Hi, there are invalid references inside sun50i-h5-fixup.scr, I think. I use NANOPINEO2, myself compiled linux-*-current-sunxi64_20.05.0-trunk_arm64.deb, kernel 5.4.28-sunxi64 #trunk SMP PREEMPT. amrbianEnv.txt (reduced): overlay_prefix=sun50i-h5 overlays=i2c0 uart1 uart2 usbhost1 usbhost2 usbhost3 param_uart1_rtscts=1 param_uart2_rtscts=1 For example, the row param_uart2_rtscts=1 leads to use following rows of sun50i-h5-fixup.scr: fdt get value tmp_phandle1 /soc/pinctrl@1c20800/uart2 phandle fdt get value tmp_phandle2 /soc/pinctrl@1c20800/uart2_rts_cts phandle fdt set /soc/serial@1c28800 pinctrl-names "default" "default" fdt set /soc/serial@1c28800 pinctrl-0 "<${tmp_phandle1}>" fdt set /soc/serial@1c28800 pinctrl-1 "<${tmp_phandle2}>" env delete tmp_phandle1 tmp_phandle2 There are some error messages during boot: Applying kernel provided DT fixup script (sun50i-h5-fixup.scr) ## Executing script at 44000000 tmp_bank=A tmp_pin=21 libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND 10046717 bytes read in 505 ms (19 MiB/s) As a result, the RTS/CTS handshaking for UART2 is unfunctional. May be for UART1 and UART3 is the same? I think the reason is that there are no paths /soc/pinctrl@1c20800/uart2 and /soc/pinctrl@1c20800/uart2_rts_cts inside the device tree specified by sun50i-h5-nanopi-neo2-v1.1.dtb file. The right paths are /soc/pinctrl@1c20800/uart2-pins and /soc/pinctrl@1c20800/uart2-rts-cts-pins, I think. Am I right? I've tried easy modification of SCR script - handshaking is now functional, but CRC is bad. If I am right, what is the right way to correct this? Script change (how properly?), DTB change, DTBO creation, ...? Moreover, look at this reduced listing of /sys/firmware/devicetree/base/soc/pinctrl@1c20800: csi-pins emac-rgmii-pins i2c0-pins i2c1-pins i2c2-pins i2s0-pins i2s1-pins mmc0-pins mmc1-pins mmc2-8bit-pins spi0-pins spi1-pins uart0-pa-pins uart1-pins uart1-rts-cts-pins uart2-pins uart2_rts_cts uart2-rts-cts-pins uart3-pins uart3-rts-cts-pins w1_pins Why are somewhere dashes "-" and somewhere underscores "_" ? Thank you.
  2. I am building my own armbian image using the armbian build environment. A substantial part of the image creation time is occupied by over-and-over recompiling the kernel. Sure, it does go faster the 2nd time, but it still takes a lot of time. The goal for me is not to make a custom kernel. I am totally happy with the kernel. The goal for me is to modify the rest of the image. They installed software, config, etc. Is there a way to reuse an existing kernel for this, instead of rebuilding a new one each time? Cheers, Dolf.
  3. Since - in my eyes - at least - there is a likelihood of confusion regarding the "Supporter" tag of members that actually (recurring) donating to the project. People could think "Supporter" means staff member that actually support people with their issues. The real staff rank, Moderator and Administrator to say, is "hidden" in their individual profiles. Since I like the idea of flat hierarchy I do not suggest to make the actual staff visible in forum postings but simply rename the Supporter to something like "Donator" to make it clear that these people donated to the project but are not necessarly involved into it. Tell me what you think,
  4. Hi to all, I've a problem with my installation of Armbian. Currently i'm using Armbian Bionic on my pine A64 kernel version: Linux pine64 5.4.20-sunxi64 #20.02.1 SMP Mon Feb 17 02:37:37 CET 2020 aarch64 aarch64 aarch64 GNU/Linux When i attach my external hdd it doesn't show in /dev neither i can find it in the logs; daniele@pine64:~$ lsusb Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub daniele@pine64:~$ dmesg | grep usb [ 1.254270] usbcore: registered new interface driver usbfs [ 1.254306] usbcore: registered new interface driver hub [ 1.254366] usbcore: registered new device driver usb [ 2.035099] sun4i-usb-phy 1c19400.phy: failed to get clock usb0_phy [ 2.057968] ehci-platform 1c1a000.usb: EHCI Host Controller [ 2.057989] ehci-platform 1c1a000.usb: new USB bus registered, assigned bus number 1 [ 2.058095] ehci-platform 1c1a000.usb: irq 19, io mem 0x01c1a000 [ 2.071979] ehci-platform 1c1a000.usb: USB 2.0 started, EHCI 1.00 [ 2.072211] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04 [ 2.072219] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.072225] usb usb1: Product: EHCI Host Controller [ 2.072231] usb usb1: Manufacturer: Linux 5.4.20-sunxi64 ehci_hcd [ 2.072237] usb usb1: SerialNumber: 1c1a000.usb [ 2.073450] ohci-platform 1c1a400.usb: Generic Platform OHCI controller [ 2.073468] ohci-platform 1c1a400.usb: new USB bus registered, assigned bus number 2 [ 2.073558] ohci-platform 1c1a400.usb: irq 20, io mem 0x01c1a400 [ 2.136249] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.04 [ 2.136257] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.136263] usb usb2: Product: Generic Platform OHCI controller [ 2.136269] usb usb2: Manufacturer: Linux 5.4.20-sunxi64 ohci_hcd [ 2.136275] usb usb2: SerialNumber: 1c1a400.usb [ 2.137581] usbcore: registered new interface driver usb-storage [ 2.142711] usbcore: registered new interface driver usbhid [ 2.142713] usbhid: USB HID core driver [ 2.280060] ehci-platform 1c1b000.usb: EHCI Host Controller [ 2.280082] ehci-platform 1c1b000.usb: new USB bus registered, assigned bus number 3 [ 2.280183] ehci-platform 1c1b000.usb: irq 21, io mem 0x01c1b000 [ 2.295979] ehci-platform 1c1b000.usb: USB 2.0 started, EHCI 1.00 [ 2.296153] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04 [ 2.296161] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.296167] usb usb3: Product: EHCI Host Controller [ 2.296173] usb usb3: Manufacturer: Linux 5.4.20-sunxi64 ehci_hcd [ 2.296178] usb usb3: SerialNumber: 1c1b000.usb [ 2.297275] ohci-platform 1c1b400.usb: Generic Platform OHCI controller [ 2.297293] ohci-platform 1c1b400.usb: new USB bus registered, assigned bus number 4 [ 2.297386] ohci-platform 1c1b400.usb: irq 22, io mem 0x01c1b400 [ 2.360140] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.04 [ 2.360147] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.360154] usb usb4: Product: Generic Platform OHCI controller [ 2.360160] usb usb4: Manufacturer: Linux 5.4.20-sunxi64 ohci_hcd [ 2.360165] usb usb4: SerialNumber: 1c1b400.usb [ 2.361268] usb_phy_generic usb_phy_generic.0.auto: usb_phy_generic.0.auto supply vcc not found, using dummy regulator [ 2.361648] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver [ 2.361665] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 5 [ 2.361876] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04 [ 2.361884] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.361890] usb usb5: Product: MUSB HDRC host driver [ 2.361896] usb usb5: Manufacturer: Linux 5.4.20-sunxi64 musb-hcd [ 2.361901] usb usb5: SerialNumber: musb-hdrc.1.auto [ 5.366107] axp20x-usb-power-supply axp20x-usb-power-supply: DMA mask not set daniele@pine64:~$ ls -l /dev/sd* ls: cannot access '/dev/sd*': No such file or directory The same hdd is recognized correctly in my laptop: Bus 001 Device 013: ID 1bcf:0c31 Sunplus Innovation Technology Inc. SPIF30x Serial-ATA bridge I've installed the full firmware package from the armbian-config tools, other usb dongles are recognized correctly. What can i do now? Thanks, Daniele.
  5. I have two NanoPi R1s, both with Armbian Buster. I want to use both as wireless access points, however the wifi seems to be problematic. It always works at first, but not anymore after updating, changing the config and rebooting. My hostapd config is the following: # # armbian hostapd configuration example # # nl80211 mode # ssid=[myssid, contains some numbers] interface=wlan0 hw_mode=g channel=6 [11 on the other one] #bridge=br0 driver=nl80211 logger_syslog=0 logger_syslog_level=0 wmm_enabled=1 wpa=2 preamble=1 wpa_psk=[random thing armbian-config generated] wpa_passphrase=[secret] wpa_key_mgmt=WPA-PSK wpa_pairwise=CCMP rsn_pairwise=CCMP wpa_strict_rekey=1 wpa_disable_eapol_key_retries=1 ieee80211w=2 auth_algs=1 macaddr_acl=0 noscan=1 ## IEEE 802.11n ieee80211n=1 ht_capab=[DSSS_CK-40][HT20+] country_code=DE ieee80211d=1 ## IEEE 802.11n ### IEEE 802.11a #hw_mode=a ### IEEE 802.11a ### IEEE 802.11ac #ieee80211ac=1 #vht_capab=[MAX-MPDU-11454][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1][MAX-A-MPDU-LEN-EXP3] #vht_oper_chwidth=1 #vht_oper_centr_freq_seg0_idx=42 ### IEEE 802.11ac # controlling enabled ctrl_interface=/var/run/hostapd ctrl_interface_group=0 Systemd says hostapd is loaded, active and exited. The wifi is not detectable by any of my devices. If I try to start hostapd manually via hostapd /etc/resolv.conf , it says Configuration file: /etc/hostapd.conf wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE wlan0: Could not connect to kernel driver Using interface wlan0 with hwaddr 18:93:7f:73:4a:ec and ssid "[SSID from config file]" random: Only 18/20 bytes of strong random data available from /dev/random random: Not enough entropy pool available for secure operations WPA: Not enough entropy in random pool for secure operations - update keys later when the first station connects wlan0: Could not connect to kernel driver Interface initialization failed wlan0: interface state COUNTRY_UPDATE->DISABLED wlan0: AP-DISABLED wlan0: Unable to setup interface. wlan0: interface state DISABLED->DISABLED wlan0: AP-DISABLED wlan0: CTRL-EVENT-TERMINATING hostapd_free_hapd_data: Interface wlan0 wasn't started nl80211: deinit ifname=wlan0 disabled_11b_rates=0 Not sure whether this is a bug or an error on my side. It used to work with OpenWrt, however the problem there is the only images for it are provided by FriendlyArm (there are no official images by the OpenWrt team), and that image is still on version 18.01, which doesn't get any security updates anymore. EDIT: I maybe also should have mentioned the WiFi and hotspot options disappear in `armbian-config`. `ip addr` or `ip link` still show the wlan0 interface however. Maybe a recent update broke the driver or so? Still not sure whether I should move this to H3 bug reports. EDIT 2: I now tried to connect to a different WiFi with `wpa_supplicant`. Works with both `wext` and `nl80211` drivers (the former returns some `IOCTL` errors, but isn't used by hostapd anyway, and it still seems to work nevertheless). So the issue is probably more related to hostapd than to the driver. EDIT 3: `iw list` said it only supported CMAC-128 ciphers, so I removed any config that would use 256 bit ciphers. Also various sources suggested this was an old bug, and I needed to run `nmcli radio wifi off` and `rfkill unblock wlan` before starting hostapd, however that didn't change anything.
  6. I recently updated from very old Armbian image. The update was not smooth so I had to re-image my device with the newest version. After that USB devices cannot be detected at all. I tried USB keyboard and 3D printer (is should looks like generic serial device). Keyboard works perfectly during u-boot but stops working as soon as kernel starts. lsusb doesn't show any devices: $ lsusb -t /: Bus 09.Port 1: Dev 1, Class=root_hub, Driver=musb-hdrc/1p, 480M /: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M So it seems like some generic issue with USB support. Now I'm using kernel 5.4.20-sunxi, also tried 4.19.104-sunxi and some other available in armbian-config - all give the same result. Any help with making it work again is very appreciated.
  7. I also like to keep things in order, but forum and this project is too big for me since a long time ago. Keeping this thing organised can only be done together. I appreciate your willingness to do your share! #armbian channel is unofficial for one very banal reason It doesn't have a recording device -> irclogs.armbian.com I tried to fix this once - by reaching out to IRC server staff to acquire OP status which is needed to install a bot, now its years ago, but failed. Then this task simply faded off the radar. It has been more than 25 years since I was installing IRC bots so I also feel a bit rusted doing that ... if you can fix this, #armbian can become official at once and I will also be there more often. Herzlich willkommen!
  8. Hi, After building a DEV Pine64 image successfully, I wanted to build a Dev BananaPI image to update 2 banana pis. Unfortunately I have this error (using this commit id : e7aeffb1) : Setting up nplan (0.36.3) ... Setting up networkd-dispatcher (1.7-0ubuntu3.3) ... Installing new version of config file /etc/default/networkd-dispatcher ... Setting up gnupg (2.2.4-1ubuntu1.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for initramfs-tools (0.130ubuntu3.5) ... [ o.k. ] Installing packages for [ Armbian ] Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package armbian-firmware [ error ] ERROR in function create_rootfs_cache [ debootstrap-ng.sh:216 ] [ error ] Installation of Armbian packages failed [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ image-helpers.sh:60 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated I'm trying to generate a new image. It's only the second image I'm trying to build, so maybe I forgot some cleanup somewhere. Thanks in advance.
  9. In the TV boxes section, it is quite calm and there is enough of the standard option. If the user has the first message on the forum, all messages are put in the moderation queue. If there is at least one approved message, the user can write directly to existing topics. If I see that his messages are spam or violate the rules, I delete them. As far as I understand, for those who have few messages (3-5- ?)- creating a new theme is put in the moderation queue. So far, there have been no problems. I read all messages in the " my " section and can see where there are hidden ads and delete such messages. If you have any suggestions or comments about my work, I am ready to listen to them.
  10. Thanks for creating a new topic! I am having problems accessing it:
  11. Armbianmonitor for 5.4.6: http://ix.io/260C From switching between 4.19.x and 5.4.x kernels I noticed that the lower cpu frequencies got missing. It should start at 120MHz like this: root@horangepione:~# uname -a Linux honeypot2 4.19.84-sunxi #19.11.3 SMP Mon Nov 18 18:39:42 CET 2019 armv7l GNU/Linux root@horangepione:~# cpufreq-info -o minimum CPU frequency - maximum CPU frequency - governor CPU 0 120000 kHz ( 11 %) - 1008000 kHz (100 %) - ondemand CPU 1 120000 kHz ( 11 %) - 1008000 kHz (100 %) - ondemand CPU 2 120000 kHz ( 11 %) - 1008000 kHz (100 %) - ondemand CPU 3 120000 kHz ( 11 %) - 1008000 kHz (100 %) - ondemand Though on 5.4.x the minimum frequency is 480MHz. Since the default cpufrequtils file was not there I created one: cat /etc/default/cpufrequtils # WARNING: this file will be replaced on board support package (linux-root-...) upgrade ENABLE=true MIN_SPEED=120000 MAX_SPEED=1200000 GOVERNOR=ondemand It seems to have an effect because when changing the minimum frequency it clocks up as it should. Frequencies beyond 1.01GHz missing as well but that is a different story...I guess. Cheers Werner
  12. Espressobin V7 1G 800MHz DDR4 RAM 1GHz cpu purchased last week. The board starts up reliably and gets to the boot prompt ok (using minicom). I downloaded and unpacked Armbian_5.91_Espressobin_Debian_buster_next_4.19.59.img. Ran shasum and got "Ok". I dd'd it to a new Samsung SD card, dd'd it back, and ran shasum again, getting "Ok". I put the card in the board and powered it up. It finds the card and tries to boot but fails, saying: Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Bad Linux ARM64 Image magic! I'm guessing that the problem is that I did not update uboot. I copied flash-image-ddr4-1g-1cs-1000_800.bin to a FAT formatted USB key, but this: Updated u-boot needs new default boot environment and new boot script (overwrite the one on your /boot media – needed only if you upgrade from < v5.59). This is what you need to copy/paste into u-boot prompt: is unclear. This: Copy this flash-image-ddr4-1g-1cs-1000_800.bin to your FAT formatted USB key, plug it into USB3.0 port and execute from u-boot prompt: bubt flash-image-ddr4-1g-1cs-1000_800.bin spi usb Seems clear enough. I assume that I am then to paste the list of commands that follows in at the boot prompt but the part about the "new boot script" is unclear. [Edit] I updated uboot and inserted the setenv commands (but ignored the unclear part about the "new boot script"). I'm getting U-Boot 2018.03-devel-18.12.3-gc9aa92c-armbian (Feb 20 2019 - 09:45:04 +0100) so that evidently worked. However, when it tries to boot from the SD card I get Marvell>> run bootcmd_mmc0 / ** Unrecognized filesystem type ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ ** Unrecognized filesystem type ** ## Executing script at 06d00000 Wrong image format for "source" command Marvell>> [Edit] The SD card is the same one that I used to flash the Uboot update. Is it necessary to prepare the card in any way other than to dd the image to it? [Edit] I loop mounted the image and found that it has an ext4 filesystem with an 8192 block offset. Used dd to make a copy with no offset. That copy boots. -- John Hasler
  13. first i was able to boot my nanopi from SD card and i was able to access it through SSH. then i was trying to boot my nanopi from EMMC but it was not booting. I already installed a different OS which is specialized for Eflasher (nanopi-neo-core_eflasher_friendlycore-xenial_4.14_armhf_20190522 ) . then i followed the steps carefully: http://wiki.friendlyarm.com/wiki/index. ... i_NEO_Core note : i was using commands since there is no HDMI. I typed : eflasher then i choose 1 and typed yes and waited until the OS was installed successfully and finally i powered off the nanopi, removed the SD card as mentioned, tried to power it on but i could not access it again through SSH anymore. I would if someone could help find the problem. or if someone would post the detailed steps to boot the nanopi NEO CORE from emmc using commands lines not HDMI. thanks in advance
  14. Hi, I can't make usb otg works on orange pi pc armbian stretch. Linux orangepipc 4.19.38-sunxi #5.83 SMP Fri May 3 23:33:25 CEST 2019 armv7l GNU/Linux At boot there is the following message in dmesg: [ 2.252841] usb0-vbus: disabling I tried to enable usbhost0 with armbianconfig overlays, but it doesn't make a difference. Any suggestions ? thanks
  15. TRYING TO create an ad-hoc network using wireless adapter( lb-link model: wn155a) on NANOPI NEO (Linux nanopim1 3.4.113-sun8i #28 SMP PREEMPT Thu Feb 2 02:01:28 CET 2017 armv7l GNU/Linux). we used this link https://citricks.net/create-access-point-linux/ BUT ad-hoc WAS NOT CREATED. running iwconfig looks like: lo no wireless extensions. tunl0 no wireless extensions. ra0 Ralink STA ESSID:"11n-AP" Nickname:"MT7601STA" Mode:Auto Frequency=2.412 GHz Access Point: Not-Associated Bit Rate:1 Mb/s RTS thr:off Fragment thr:off Encryption key:off Link Quality=10/100 Signal level:0 dBm Noise level:0 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 eth0 no wireless extensions. running ifconfig looks like : eth0 .....(not important) lo ... (not important) ra0 Link encap:Ethernet HWaddr 0c:8c:24:b7:d7:dc UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:17365 errors:0 dropped:0 overruns:0 frame:0 TX packets:156 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3718930 (3.5 MiB) TX bytes:16224 (15.8 KiB) Can I use the steps of creating an Access Point to create an ad-hoc mode network? or I am in the wrong way?
  16. Hello, I want to read data from UART3 on OrangePi One. I want to use UART3 (pin 8 & 10), so I enabled uart3 overlay at /boot/armbianEnv.txt. Now I expect to read data via minicom -b 115200 -D /dev/ttyS3 but I read nothing unfortunately. What am I missing? Any help is appreciated. I'm using Linux orangepione 4.19.38-sunxi (sorry, armbianmonitor doesn't generate link) Thank you, Regards
  17. I am having problems with the NanoPi R1. I loaded the latest Armbian for R1 on flash. All works good. I went to armbian-config to load into eMMC. The last step of the process had weird text on the dialog, I clicked "OK" anyway, and the process seemed to be working. But after removing uSD card and rebooting, the board does not work. The red led stays on solid. Did anyone successfully burn the image from uSD to eMMC using the tool in armbian-config?
  18. I use the Armbian_5.45_Orangepizeroplus2-h5_Debian_stretch_next_4.14.44.img. I want to use a sensor based on the spi protocol. In armbian-config i enable the spi ,the armbianEnv.txt like this: verbosity=1 console=both overlay_prefix=sun50i-h5 overlays=i2c0 i2c1 spdif-out spi-add-cs1 spi-jedec-nor spi-spidev uart1 uart2 usbhost2 usbhost3 rootdev=UUID=bb48b498-7bd1-4018-b77d-ba00fa61a33d rootfstype=ext4 param_uart1_rtscts=1 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u But in /dev on spi-dev root@H5:~# ls /dev/s shm/ snd/ stderr stdin stdout Is it because there is no code adaptation spi-dev? if not ,I want to try to transplant the spi-dev code,Can give me some guiding advice?
  19. Hello, I'm running a OPI Lite with debian jessie, All works fine until i have to reboot, and that happens quiet often while testing software. AFTER the boot i'm not able to reach the OPI via SSH, because the eth0 is activated ...and has a 169.x.x.x ip adress... On the OPI Lite i can ONLY discover WIFI and no eth0 connector...So i go into the "nmtui" tool and "disactivate" the eth0... Than i have access again via the wifi to my OPI lite. How can i completely disable the eth0, that only WIFI connects to my network? I didn't find about this behavior on the web, anyone else have that problem? Kind regards from Hans F4VSJ
  20. Requirements: https://github.com/lthiery/SPI-Py https://github.com/mxgxw/MFRC522-python (for Raspberry Pi) https://github.com/kwanxian/OrangePiPC/tree/master/SPI/RC522 (for Orange Pi PC) sudo armbian-config System --> Hardware --> select "spi-spidev" --> Confirm --> reboot when reboot finish: sudo vim /boot/armbianEnv.txt under "overlays=spi-spidev",add this: "param_spidev_spi_bus=0" save & reboot again. then you can see spi enable in "/dev/spidev0.0". cd ./SPI_Python sudo python3 setup.py install cd ../RC522 sudo python3 Read.py you can test IC card like this: Welcome to the MFRC522 data read example Press Ctrl-C to stop. Card detected Card read UID: 53,101,232,169 Size: 8 Sector 8 [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Card detected Card read UID: 53,101,232,169 Size: 8 Sector 8 [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
  21. Hello, I'm new to the Pi computers and all that, and I'm planning on doing a project, so I was wondering if the Opi One H3 would support packet injection and monitor mode on Armbian with the onboard wifi? Thanks in advance.
  22. Hello everyone. I'm new to Armbian. If I do not restart or turn off by command (correctly) all the files generated or transferred since it was turned on are deleted immediately. Why? Is it normal in Armbian? I use Orange Pi Win Plus 2, how do I deactivate that functionality? I use it as a remote server.
  23. Hi! Periodically, time in two-three days, sharply increases CPU utilization, the system becomes disfunctional. SD card and power supply maybe not the best, but they working fine in other systems and I'm tried others. SSH hangs on login while this problem is actual, but i have a serial connection, so can investigate in real time. Please, advise, what to look when this situation came again? top - 03:02:15 up 24855 days, 3:14, 1 user, load average: 1.75, 1.77, 1.93 Tasks: 125 total, 3 running, 70 sleeping, 0 stopped, 8 zombie %Cpu(s): 17.4 us, 26.6 sy, 0.0 ni, 56.1 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 505152 total, 9724 free, 144028 used, 351400 buff/cache KiB Swap: 1301132 total, 1299340 free, 1792 used. 343236 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 26012 3040 1304 R 100.0 0.6 46:55.28 systemd 851 root 20 0 6128 1368 948 R 75.2 0.3 34:13.74 systemd-lo+ 8668 root 20 0 7044 2608 2136 R 1.3 0.5 0:00.15 top 7 root 20 0 0 0 0 S 0.3 0.0 14:28.83 ksoftirqd/0 8 root 20 0 0 0 0 I 0.3 0.0 1:21.03 rcu_sched 2 root 20 0 0 0 0 S 0.0 0.0 0:00.05 kthreadd root@pione:/media/data/log# systemctl reboot Failed to set wall message, ignoring: Connection timed out Failed to reboot system via logind: Connection timed out Failed to start reboot.target: Connection timed out See system logs and 'systemctl status reboot.target' for details. root@pione:/media/data/log# root@pione:/media/data/log# systemctl status reboot.target Failed to get properties: Connection timed out root@pione:/media/data/log# root@pione:/media/data/log# reboot root@pione:/media/data/log# root@pione:/media/data/log# reboot -f Failed to read reboot parameter file: No such file or directory Rebooting. [141846.733884] reboot: Restarting system ▒▒▒▒▒▒ U-Boot SPL 2018.05-armbian (Aug 19 2018 - 17:07:52 +0200) DRAM: 512 MiB Trying to boot from MMC1 System log:
  24. Hellow, I would like to report an issue with Orange Pi PC+ I tried to run the board with a manually built image (with kernel version 'next' and 5.71). While in the past I was able to create Wifi hotspots without any issues, with a new image I encountered weird issues where the hotspot was listed from Wifi clients, but trying to connect triggered some scarry traceback such as this one : Having no idea what I was doing, after trying a few other things, I tried downgrading the kernel to 5.70 (using apt.armbian.org) - this did not solve the issue - and then to 5.67 for which it was working as expected ! I don't know if this is something that can be solved upstream somehow ... Naively it sounds related to the 8189fs module (driver for the Wifi chip ?) but not really sure as I don't understand so much all the driver and kernel stuffs
  25. I just got a Nanopi NEO2 512MB, installed Armbian Ubuntu Bionic. It works fine, except for the DVB-T/C stick. It is affected by Kernel 4.10+ problems. I wonder if I can downgrade to an older kernel, like 4.4.0 for example, where everything works perfectly? If yes, how? There is a patch that perhaps would resolve the problem, how could I apply this patch to an of the available releases of Armbian? This patch Please, help me with this. Many thanks!
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines