Search the Community

Showing results for tags 'mainline'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues
    • Peer to peer technical support
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner H5 & A64
    • Armada A388, A3700
    • Amlogic S905(x)
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Other supported boards
  • Development
    • Allwinner H6
    • Rockchip 3399
    • Development

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 888 results

  1. Hi, I have a couple of these boards which I have been using with Armbian and the old, 3.10 kernel. Ideally I would really like to go mainline as later kernels have some functionality that would be useful for my use of the board. The only remaining reason (apart from cpu freq.) for sticking to the 3.10 kernel has been the lack of MIPI DSI support in mainline, but now I see that, despite the Matrix at http://linux-sunxi.org/Linux_mainlining_effort still being red for A64 mipi, some work is being/has been done by Maxime Ripard. I'm just wondering if anyone here knows if a working mainline kernel with DSI for the Pine 64 is starting to look like a possibility and if it might be possible to include in an armbian build. I might be able to do some testing of anyone can guide me in making a build with the necessary patches.
  2. Hi, I have two OrangePi Lite running side by side. After working fine for about 8 months both started to experience same issue with wireless: The board works randomly for few hours or few days and then looses wireless connection. When this happens reboot does not help as then issue occurs immediately after the boot. Unplugging and replugging power source resolves that for a while and then happens again I suspect it may not be related to a hardware issue or wireless hotspot, as I have at least 3 other clients that continue to work fine. Searching for it on the internet brought this issue with Raspberry Pi: https://github.com/raspberrypi/linux/issues/1988. Raspberry uses different wireless chipset either. All that makes me think this may be an issue in the kernel itself Any ideas or thoughts? Workaround also appreciated Thanks
  3. Has anybody seen this message at boot: [ 5.352826] CPU4: failed to come online [ 5.352835] CPU4: failed in unknown state : 0x0 [ 10.481328] CPU5: failed to come online [ 10.481336] CPU5: failed in unknown state : 0x0 Then, the A72 cores don't show up (unsurprisingly since these are the two cores that somehow did not come online). On top of that, the kernel throws a backtrace (related to sound if I understand correctly): ------------[ cut here ]------------ [ 13.014782] WARNING: CPU: 3 PID: 1 at kernel/irq/manage.c:1990 request_threaded_irq+0x144/0x180 [ 13.014784] Modules linked in: [ 13.014793] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.4.26-rockchip64 #20.02.5 [ 13.014795] Hardware name: Pine64 RockPro64 (DT) [ 13.014799] pstate: a0000005 (NzCv daif -PAN -UAO) [ 13.014804] pc : request_threaded_irq+0x144/0x180 [ 13.014808] lr : request_threaded_irq+0x6c/0x180 [ 13.014810] sp : ffff80001004b9b0 [ 13.014813] x29: ffff80001004b9b0 x28: 0000000000000000 [ 13.014817] x27: ffff0000ef78c0c0 x26: ffff8000111c8d98 [ 13.014822] x25: 0000000000000000 x24: 0000000000000007 [ 13.014826] x23: ffff0000f0914870 x22: ffff800010b2dce0 [ 13.014830] x21: ffff0000f142a000 x20: 0000000000000000 [ 13.014834] x19: ffff80001141bee0 x18: 0000000000000001 [ 13.014838] x17: ffff800011188d00 x16: ffff800011188d08 [ 13.014843] x15: ffffffffffffffff x14: ffff80001137b508 [ 13.014847] x13: ffff00016f1e14b7 x12: ffff0000ef1e14c3 [ 13.014851] x11: ffff0000f67ac268 x10: 0000000000000040 [ 13.014855] x9 : ffff80001139f028 x8 : ffff80001139f020 [ 13.014859] x7 : ffff0000f10002a8 x6 : 0000000000000000 [ 13.014863] x5 : ffff0000f1000248 x4 : 0000000000000000 [ 13.014867] x3 : 0000000000000000 x2 : 0000000000000000 [ 13.014871] x1 : 0000000000000007 x0 : 0000000000031600 [ 13.014875] Call trace: [ 13.014880] request_threaded_irq+0x144/0x180 [ 13.014887] snd_mtpav_probe+0x15c/0x3d8 [ 13.014893] platform_drv_probe+0x50/0xa0 [ 13.014899] really_probe+0xd8/0x300 [ 13.014902] driver_probe_device+0x54/0xe8 [ 13.014906] __device_attach_driver+0x80/0xb8 [ 13.014910] bus_for_each_drv+0x78/0xc8 [ 13.014915] __device_attach+0xd4/0x130 [ 13.014918] device_initial_probe+0x10/0x18 [ 13.014922] bus_probe_device+0x90/0x98 [ 13.014927] device_add+0x3c4/0x5f0 [ 13.014930] platform_device_add+0x10c/0x230 [ 13.014934] platform_device_register_full+0xc8/0x140 [ 13.014940] alsa_card_mtpav_init+0x74/0xd0 [ 13.014945] do_one_initcall+0x74/0x1b0 [ 13.014950] kernel_init_freeable+0x194/0x22c [ 13.014957] kernel_init+0x10/0xfc [ 13.014961] ret_from_fork+0x10/0x18 [ 13.014969] ---[ end trace 34ce35f0c45c0a90 ]--- Mathias
  4. Hi! Now that the camera interface has been merged in mainline Kernel, I would like to try to use the OrangePi OV5640 camera module on my OrangePi One. So with the latest Armbian Bionic (20.02.1, kernel 5.4.20), I have been trying to get a device tree overlay. But for now, it fails to compile with: $ sudo armbian-add-overlay sun8i-h3-csi.dts Compiling the overlay Error: sun8i-h3-csi.dts:27.23-24 syntax error FATAL ERROR: Unable to parse input tree Error compiling the overlay My current overlay looks like this: /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&pio>; __overlay__ { csi_mclk_pin: csi-mclk-pin { pins = "PE1"; function = "csi"; }; }; }; fragment@1 { target = <&i2c2>; __overlay__ { status = "okay"; ov5640: camera@3c { compatible = "ovti,ov5640"; reg = <0x3c>; pinctrl-names = "default"; pinctrl-0 = <&csi_mclk_pin>; clocks = <&ccu CLK_CSI_MCLK>; clock-names = "xclk"; AVDD-supply = <&reg_aldo1>; DOVDD-supply = <&reg_dldo3>; DVDD-supply = <&reg_eldo3>; reset-gpios = <&pio 4 14 GPIO_ACTIVE_LOW>; /* CSI-RST-R: PE14 */ powerdown-gpios = <&pio 4 15 GPIO_ACTIVE_HIGH>; /* CSI-STBY-R: PE15 */ port { ov5640_ep: endpoint { remote-endpoint = <&csi_ep>; bus-width = <8>; data-shift = <2>; /* lines 9:2 are used */ hsync-active = <1>; /* Active high */ vsync-active = <0>; /* Active low */ data-active = <1>; /* Active high */ pclk-sample = <1>; /* Rising */ }; }; }; }; }; fragment@2 { target = <&csi>; __overlay__ { status = "okay"; port { csi_ep: endpoint { remote-endpoint = <&ov5640_ep>; bus-width = <8>; hsync-active = <1>; /* Active high */ vsync-active = <0>; /* Active low */ data-active = <1>; /* Active high */ pclk-sample = <1>; /* Rising */ }; }; }; }; }; So the line 27, which seem to trigger the error is: `clocks = <&ccu CLK_CSI_MCLK>;` Also, according to the documentation, the regulator fields are required but this board does not have much regulators (like AXP209), so I have no idea what to write here. But this is my first time writing a device-tree overlay so I am not sure what is wrong with this line. Could someone guide me to get my overlay right? And, does anyone already got the CSI interface working with OV5460 sensor on a H3 based board? Thank you.
  5. Hello, I have a massive problem as the time/date on my Pine64 keep changing randomly to the year 2113. In my project, I use several Pine64s and the problem now occurs on many of these Pine64s. Unfortunately I need the correct time for my project. I am using the following system: ARMBIAN 5.32.170911 nightly Ubuntu 16.04.3 LTS 4.13.0-sun50iw1 (with additional overlays = uart3 and console = ttyS3) Could this be due to the error described in the post and is the bug fixed in kernel version 4.14? Could I install this kernel version 4.14 via armbian-config (next-kernel)? Thanks a lot for help.
  6. Hello guys. After a long time unsuccesfully trying to use a NanoPi Neo to record I2S data, I wonder if is there some NanoPi board that is capable of such thing. Can you suggest one? Thank you very much!
  7. Hello, I have installed Armbian Debian Stretch Next (mainline kernel) on my Odroid C2 and updated to newest version(apt update & apt upgrade). Everything works fine except USB ports. I have USB LTE modem which is not recognized. I have tried "lsusb -v" but with this modem not works. But when I connect USB keyboard first then "lsusb -v" and next I connect LTE modem and type "lsusb -v" then it's works. I also tried connecting USB LTE modem before Odroid C2 boot but this workaround not working. Is there any workaround which not involving connecting more than one USB device? Maybe usb kernel modules (usbcore, ehci_hcd, ...) compiled as external modules will help find workaround?
  8. I'am running the latest Stretch server version on a PiOne (Linux 4.14.65-sunxi). I think that something is going wrong with the logrotate. The rotation is done in /var/log.hdd directory (see also the scripts in /etc/logrotate.d/). But the original file of each is in /var/log directory and is not "cleared" after the rename, because it is not renamed. So, if Zram copies /var/log directory to the /var/log.hdd directory, the original file in /var/log with old logging and included new logging is written to the /var/log.hdd directory. In the next logrotate this growing file is compressed. In this situation/in my case the compressed files contains all the loggings and not only the loggings of the last day or week or month, depending which file is compressed. And the file is still growing and growing. Is my conclusion right or is something wrong in my Stretch installation. In the latest case, I could not find it. Please give me a hint.
  9. Hello, I have two Banana Pi Pro boards with current Armbian 20.02.1_Bananapipro_buster_current_5.4.20_minimal, kernel 5.4.20-sunxi and both have small SSD connected (WD 120GB and Goodram 120GB). fdisk -l doesn't show any drive's except sdcard (and ram drives). Is there any way I can get it working?
  10. Just wanted to note this - target NanoPi NEO2 - task at hand is Byte-UnixBench.... https://github.com/sfx2000/byte-unixbench more to follow...
  11. I recently purchased a number of Orange Pi and Nano Pi boards, and discovered the awesome work of the Armbian team :-) The Orange Pi Plus2 H5 is a rather nice board - built in eMMC, H5, etc. (I wish it had 1GB of RAM but that's a different subject.) I'd love to use these boards for a number of projects. As a test, I modified the DTS for the board (mainline kernel) to enable support for the 1.1v/1.3v switch for VDD-CPUX using the SY8113B on the board. I also enabled the allowed clock changes to 1.2GHz for cpufreq. All of this worked great, but the board was very unstable at anything over 1GHz, which seemed strange, given that the CPU voltage should be switching to 1.3v. I found that when measuring the voltage of the "1V2C" testpoint on the board that VDD-CPUX was always at 1.1v - it never switched to 1.3v. I did some further examination of the board, and I was surprised to find that the "Q5" BSN20 MOSFET was not populated on the board! I checked all of the other passives and they are present - it is like Xunlong simply decided not to stuff this part when they built the board. So, as a test, I desoldered this part from my Orange Pi Zero rev 1.4 board and soldered it in the missing "Q5" spot on my Orange Pi Zero Plus2 board. And now it works great! VDD-CPUX properly switches between 1.1v/1.3v (measured at the "1V2C" TP), and I can clock the board to 1.296GHz without any problems. Would anyone have an idea why Xunlong doesn't solder this part on the board by default? They include all the other parts in this part of the power circuit, just not this MOSFET. I was going to buy a few more of these boards, and I'd like to be able to clock them up. Perhaps I should just order a set of these BSN20 MOSFETs and solder them on myself when I receive the boards...? Or perhaps I should just forget Xunlong/Orange Pi and use Nano Pis? My Nano Pi Neo Plus2 has been working perfectly since I powered it up (I enabled clocking to 1.296GHz by default as well in the DTS). By the way, I did some extensive tests and it looks like with both of these boards DVFS and thermal throttling works fine - the clock throttles back properly at the different temperature thresholds. Thank you!
  12. Hi, can anyone let me know if we can enable a UART port from a DTB file? Means like compile DTB to DTS, make changes and then again recompile it to a DTB like we do in the script.bin file of legacy kernel. Earlier I have used to mention "overlays=uart1 uart2" in the armbianEnv.txt file but, this didn't work for me .
  13. as described in: https://gitlab.freedesktop.org/mesa/mesa/issues/2377 it's possible to use meson HW video codec now, but in the URL, not very clear, does any one know how to use it?
  14. There's this: Anybody knows about the status of PWM on the H5 (OPi PC 2 in my case) with mainline kernel? BTW am I off-topic asking about H5 in this forum? Thanks.
  15. I'm trying to disable the HDMI output on my A20-OlinuXino LIME. I have tried to disable the HDMI from the u-boot console using this commands : -setenv video-mode sunxi:1024x768-24@60,monitor=none -saveenv I have also tried to recompile the boot.cmd but even in this way nothing. Corrently i'm using : Linux lime 4.19.62-sunxi #5.92 Where is my mistake? Thanks in advance.
  16. Good day! Tell me if there is support for hardware acceleration Orange PI WIN PLUS Cortex-A64 ?? I try to run a video (vlc,mpv) but it is very slow =(
  17. Hello,Respected Developers: I'm an Orange Pi user.In the process of using the armbian, I encountered serious problems. My Control Board is Orange Pi PC Plus.Armbian is "ARMBIAN 5.59 stable Ubuntu 18.04.1 LTS 4.14.65-sunxi" I installed jdk and mysql.And run a JAVA program.I set a time zone for Asia-Chongqing,The system language is Chinese,I use three serial ports. When running for a period of time,There will be bugs.About one to three days. The specific phenomena are as follows: 1.Run "date",the time is 1978. 2.Mysql occupy cpu 195%, occupy mem 27%,systemd occupy cpu 34%,Another systemd occupy cpu 14% ,systemd-jo+ occupy cpu 39%. 3.eth0‘s ip disappear,Unable to connect remotely from the network for ssh.I only use serial port to connect. 4.I can't use the reboot command to restart,I input "reboot",It didn't respond. Time automatically changed to 1978. I hope you can help me solve this problem,Thanks very much.
  18. Hi everyone, I have a problem when work on OPi zero wifi which is running Armbian linux sunxi 4.19.62. I used nmtui to configure wifi connection with static ip. It works fine even rebooting or re-powering up however I tried to power off the router and the result is it has never reconnected again. Next, I plugged in the ethernet cable into RJ45 port, the connection is established. I use sudo ifconfig to show the information, I saw that both the wifi (static) and ethernet are correctly then I can access via ssh or scanning the ip. One again, I continued plugging out the ethernet cable, all connections were disappeared even wifi and connection via ssh is failed. Is there anyone face on this issue? Giving me some help, please.
  19. Dear all, Starting from NAND memory used to work fine on the nanopi neo plus2, however with the new boards (both v1.2 and v2.0 revision) we just obtained it frequently doesn't want to reboot, while a cold boot works fine (I tried also earlier u-boot versions (2019.04, 2018.11) without much success for the reboot from NAND). The re-boot process stops at this point (from the serial console): [ OK ] Reached target Shutdown. [ 152.452083] reboot: Restarting system U-Boot SPL 2019.10-armbian (Jan 25 2020 - 19:56:27 +0100) DRAM: 1024 MiB Trying to boot from MMC2 I suspected the problem to be in the u-boot, since the friendlyarm on NAND reboots without a hitch. I found a work-around for the latest stretch image (Armbian_20.02.0-rc1_Nanopineoplus2_stretch_current_5.4.14.7z), by doing the following: boot friendlyarm image from NAND and copy the sunxi-spl.bin: sudo dd if=/dev/mmcblk2 of=sunxi-spl-friendlyarm.bin count=4 bs=8k skip=1 boot armbian from NAND and update u-boot: switched to linux-image-next-sunxi64=5.90 kernel via armbian-config / System / Other / switch dd if=sunxi-spl-friendlyarm.bin of=/dev/mmcblk2 count=4 bs=8k seek=1 conv=fsync The atached armbianmonitor -u upload is from after a fresh reboot with the working configuration. Kind regards, Dennis
  20. Well, no fancy introduction here, because this doesn't pretend to be a script for the general use, only for testers who want to try the current *very early* status of the media capabilities in the Armbian meson mainline kernel. Warning: It will replace your current kernel with a pre-compiled nightly 4.19.20. Instructions: Download, untar and run. If you need further instructions, then you are not ready for this script (again, it is very unpolished, not for general use). Download link: https://mega.nz/#!YvYUhayC!CI1fl52V4tV0G4oqUib4W-NlMpVSpLDp8kmo74g-V08 Things that you can try with this script, on a X session: Use a 1080p@30fps h264 video, and play it with "mpv -hwdec <filename>". You'll see in the logs that it is decoding through v4l-m2mcopy Install and run glmark2-es2 Use Chromium WebGL Play a 1080p@30fps video in YouTube in full-screen smoothly. I'm pretty sure it is not really using HW decoding as it claims (there is no initialization message in dmesg), but it's smooth for sure. Gstreamer is tested not to work, in some other forum I was told that Bionic version is not enough and I need to compile a newer one. Performance is not in any way good, but it is a starting point. Anyway, the first TO-DO is getting the mali module integrated into the kernel, so there is no need to compile it separately.
  21. I want to drive 2 SPI devices on my orangepi zero. I enabled `spi-spidev` and `spi-add-cs1` overlays and set `param_spidev_spi_bus` to 1. But by I still get only `/dev/spi1.0` available. When I add `param_spidev_spi_cs=1`, I get `/dev/spi1.1` but `/dev/spi1.0` disappears. Do I see it correctly that I can choose *either* `/dev/spi1.0` *or* `/dev/spi1.1` but not both with that overlay? How can I activate both cs pins? There are a bunch of example custom files out there, but none are meant specifically for the setup where I need spi1 (instead of spi0) and need to use a GPIO pin for cs1. And I can't really find any docs on how to write my own overlay. So any help is appreciated.
  22. Using Armbian_20.02.1 with 5.4 kernel on NEO2 board, I'm running into an issue trying to get the USB OTG working with the g_ether module. When I run modprobe g_ether I see the following in dmesg: [ 490.490582] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers I've also tried compiling my own img using the Armbian builder but it looks like all the correct OTG options are already selected by default. Any ideas what I'm doing wrong?
  23. Is there a way to boot the Pine-A64 LTS with Armbian via eMMC? I can use the SD card to boot the armian-Sopine image, but the eMMC memory is not recognized. With the Ayufan image (jessie-minimal) on SD card (https://github.com/ayufan-pine64/linux-build/releases), I can at least recognize the eMMC memory and using sudo dd bs = 30M if = Image / jessie-minimal-sopine-0.7.19-118.img of =/dev/ mmcblk1 copy to the eMMC memory. I removed the SD card and booted with eMMC. I did the same steps with the Armbian image and write the Armbian image on the eMMC (with the Ayufan image on SD card) sudo dd bs=30M if=Image/Armbian_5.38_Pine64so_Ubuntu_xenial_default_3.10.107.img of=/dev/mmcblk1 and nothings happens after the reboot. There are further steps that I have to carry out?
  24. Hello, I am using up to date Armbian Buster. TP-Link TL-WN722N V1 USB WiFi dongle causes system crashes after kernel upgrade to 5.4.12-meson64 #19.11.8 SMP PREEMPT Thu Jan 16 20:12:23 CET 2020 aarch64 GNU/Linux. Before updating the kernel, I had no such problem. Feb 12 20:17:15 xxx systemd[1]: Found device AR9271 802.11n. Feb 12 20:17:15 xxx systemd[1]: Started ifup for wlx54e6fc8d208e. Feb 12 20:17:15 xxx wpa_supplicant[2360]: Successfully initialized wpa_supplicant Feb 12 20:17:15 xxx sh[2344]: wlx54e6fc8d208e=wlx54e6fc8d208e Feb 12 20:17:17 xxx wpa_supplicant[2361]: Using interface wlx54e6fc8d208e with hwaddr 54:e6:fc:8d:20:8e and ssid "mynetwork" Feb 12 20:17:17 xxx wpa_supplicant[2361]: wlx54e6fc8d208e: interface state UNINITIALIZED->ENABLED Feb 12 20:17:17 xxx wpa_supplicant[2361]: wlx54e6fc8d208e: AP-ENABLED Feb 12 20:17:17 xxx wpa_supplicant[2361]: wlx54e6fc8d208e: CTRL-EVENT-CONNECTED - Connection to 54:e6:fc:8d:20:8e completed [id=0 id_str=] Feb 12 20:17:20 xxx systemd[1]: systemd-rfkill.service: Succeeded. Feb 12 20:17:41 xxx wpa_supplicant[2361]: wlx54e6fc8d208e: AP-STA-CONNECTED 2c:d0:5a:38:bd:3b Feb 12 20:18:00 xxx sshd[2403]: Accepted password for myuser from 10.0.0.5 port 22 ssh2 Feb 12 20:18:00 xxx sshd[2403]: pam_unix(sshd:session): session opened for user myuser by (uid=0) Feb 12 20:18:00 xxx systemd[1]: Created slice User Slice of UID 1001. Feb 12 20:18:00 xxx systemd[1]: Starting User Runtime Directory /run/user/1001... Feb 12 20:18:00 xxx systemd-logind[1584]: New session 7 of user myuser. Feb 12 20:18:00 xxx systemd[1]: Started User Runtime Directory /run/user/1001. Feb 12 20:18:00 xxx systemd[1]: Starting User Manager for UID 1001... Feb 12 20:18:00 xxx systemd[2406]: pam_unix(systemd-user:session): session opened for user myuser by (uid=0) Feb 12 20:18:00 xxx systemd[2406]: Reached target Paths. Feb 12 20:18:00 xxx systemd[2406]: Reached target Sockets. Feb 12 20:18:00 xxx systemd[2406]: Reached target Timers. Feb 12 20:18:00 xxx systemd[2406]: Reached target Basic System. Feb 12 20:18:00 xxx systemd[2406]: Reached target Default. Feb 12 20:18:00 xxx systemd[2406]: Startup finished in 123ms. Feb 12 20:18:00 xxx systemd[1]: Started User Manager for UID 1001. Feb 12 20:18:00 xxx systemd[1]: Started Session 7 of user myuser. Feb 12 20:18:48 xxx sshd[2505]: Received disconnect from 10.0.0.5 port 22:11: disconnected by user Feb 12 20:18:48 xxx sshd[2505]: Disconnected from user myuser 10.0.0.5 port 22 Feb 12 20:18:48 xxx sshd[2403]: pam_unix(sshd:session): session closed for user myuser Feb 12 20:18:48 xxx systemd[1]: session-7.scope: Succeeded. Feb 12 20:18:48 xxx systemd-logind[1584]: Session 7 logged out. Waiting for processes to exit. Feb 12 20:18:48 xxx systemd-logind[1584]: Removed session 7. Feb 12 20:18:54 xxx wpa_supplicant[2361]: wlx54e6fc8d208e: AP-STA-DISCONNECTED 2c:d0:5a:38:bd:3b Feb 12 20:18:56 xxx kernel: ath: phy0: Unable to remove station entry for: 2c:d0:5a:38:bd:3b Message from syslogd@localhost at Feb 12 20:18:59 ... kernel:[ 571.404886] Internal error: Oops: 96000004 [#1] PREEMPT SMP Message from syslogd@localhost at Feb 12 20:18:59 ... kernel:[ 571.612865] Code: d5384101 b9402262 b9401020 11000400 (f8626a99) Message from syslogd@localhost at Feb 12 20:18:59 ... kernel:[ 571.623551] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b Second one: Feb 12 20:23:08 xxx wpa_supplicant[2125]: Using interface wlx54e6fc8d208e with hwaddr 54:e6:fc:8d:20:8e and ssid "mynetwork" Feb 12 20:23:08 xxx wpa_supplicant[2125]: wlx54e6fc8d208e: interface state UNINITIALIZED->ENABLED Feb 12 20:23:08 xxx wpa_supplicant[2125]: wlx54e6fc8d208e: AP-ENABLED Feb 12 20:23:08 xxx wpa_supplicant[2125]: wlx54e6fc8d208e: CTRL-EVENT-CONNECTED - Connection to 54:e6:fc:8d:20:8e completed [id=0 id_str=] Feb 12 20:23:11 xxx systemd[1]: systemd-rfkill.service: Succeeded. Message from syslogd@localhost at Feb 12 20:23:25 ... kernel:[ 77.921372] Internal error: Oops: 96000004 [#1] PREEMPT SMP Message from syslogd@localhost at Feb 12 20:23:25 ... kernel:[ 78.152254] Code: d5384101 b9402262 b9401020 11000400 (f8626a99) Feb 12 20:23:25 xxx kernel: Unable to handle kernel paging request at virtual address 0005001700000048 Feb 12 20:23:25 xxx kernel: Mem abort info: Feb 12 20:23:25 xxx kernel: ESR = 0x96000004 Feb 12 20:23:25 xxx kernel: EC = 0x25: DABT (current EL), IL = 32 bits Feb 12 20:23:25 xxx kernel: SET = 0, FnV = 0 Feb 12 20:23:25 xxx kernel: EA = 0, S1PTW = 0 Feb 12 20:23:25 xxx kernel: Data abort info: Feb 12 20:23:25 xxx kernel: ISV = 0, ISS = 0x00000004 Feb 12 20:23:25 xxx kernel: CM = 0, WnR = 0 Feb 12 20:23:25 xxx kernel: [0005001700000048] address between user and kernel address ranges Feb 12 20:23:25 xxx kernel: Internal error: Oops: 96000004 [#1] PREEMPT SMP Feb 12 20:23:25 xxx kernel: Modules linked in: ath9k_htc ath9k_common ath9k_hw mac80211 ath cfg80211 rfkill libarc4 cdc_ether usbnet uas nf_log_ipv4 nf_log_common nft_limit cpufreq_powersave cpufreq_conservative xt_tcpudp xt_multiport xt_LOG xt_limit xt_conntrack nft_counter nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables nfnetlink meson_rng rng_core meson_gxbb_wdt scpi_hwmon ip_tables x_tables dwmac_generic realtek dwmac_meson8b Feb 12 20:23:25 xxx kernel: CPU: 1 PID: 2125 Comm: wpa_supplicant Not tainted 5.4.12-meson64 #19.11.8 Feb 12 20:23:25 xxx kernel: Hardware name: Hardkernel ODROID-C2 (DT) Feb 12 20:23:25 xxx kernel: pstate: 60000005 (nZCv daif -PAN -UAO) Feb 12 20:23:25 xxx kernel: pc : __kmalloc_node_track_caller+0x150/0x288 Feb 12 20:23:25 xxx kernel: lr : __kmalloc_node_track_caller+0x4c/0x288 Feb 12 20:23:25 xxx kernel: sp : ffff800010603710 Feb 12 20:23:25 xxx kernel: x29: ffff800010603710 x28: 0000000000000014 Feb 12 20:23:25 xxx kernel: x27: ffff80001249d3c0 x26: ffff000042d90d00 Feb 12 20:23:25 xxx kernel: x25: 00000000ffffffff x24: 0000000000159801 Feb 12 20:23:25 xxx kernel: x23: ffff800011c67510 x22: 00000000ffffffff Feb 12 20:23:25 xxx kernel: x21: 00000000000928c0 x20: 0005001700000048 Feb 12 20:23:25 xxx kernel: x19: ffff000007303800 x18: 0000000000000000 Feb 12 20:23:25 xxx kernel: x17: 0000000000000000 x16: 0000000000000000 Feb 12 20:23:25 xxx kernel: x15: 0000000000000000 x14: 85a901e7583f6960 Feb 12 20:23:25 xxx kernel: x13: 3c82001b6c5b05ca x12: 32d0f6c2e6c1b305 Feb 12 20:23:25 xxx kernel: x11: ed25b09923fa1d1c x10: 32b5a2a8b0fc50fa Feb 12 20:23:25 xxx kernel: x9 : 0000000000000000 x8 : ffff00003c5a1020 Feb 12 20:23:25 xxx kernel: x7 : 0000000000000000 x6 : ffff00003c5a1020 Feb 12 20:23:25 xxx kernel: x5 : 0000000000000020 x4 : 0000000000000000 Feb 12 20:23:25 xxx kernel: x3 : 0000000000159801 x2 : 0000000000000000 Feb 12 20:23:25 xxx kernel: x1 : ffff00003c56aac0 x0 : 0000000000000001 Feb 12 20:23:25 xxx kernel: Call trace: Feb 12 20:23:25 xxx kernel: __kmalloc_node_track_caller+0x150/0x288 Feb 12 20:23:25 xxx kernel: __kmalloc_reserve.isra.56+0x44/0xa0 Feb 12 20:23:25 xxx kernel: pskb_expand_head+0x70/0x2d0 Feb 12 20:23:25 xxx kernel: netlink_trim+0xa0/0xe0 Feb 12 20:23:25 xxx kernel: netlink_unicast+0x54/0x1f8 Feb 12 20:23:25 xxx kernel: nl80211_tx_mgmt+0x32c/0x370 [cfg80211] Feb 12 20:23:25 xxx kernel: genl_family_rcv_msg+0x1dc/0x3b0 Feb 12 20:23:25 xxx kernel: genl_rcv_msg+0x58/0xd0 Feb 12 20:23:25 xxx kernel: netlink_rcv_skb+0x58/0x118 Feb 12 20:23:25 xxx kernel: genl_rcv+0x34/0x48 Feb 12 20:23:25 xxx kernel: netlink_unicast+0x180/0x1f8 Feb 12 20:23:25 xxx kernel: netlink_sendmsg+0x198/0x338 Feb 12 20:23:25 xxx kernel: sock_sendmsg+0x44/0x50 Feb 12 20:23:25 xxx kernel: ____sys_sendmsg+0x250/0x290 Feb 12 20:23:25 xxx kernel: ___sys_sendmsg+0x80/0xc0 Feb 12 20:23:25 xxx kernel: __sys_sendmsg+0x68/0xb8 Feb 12 20:23:25 xxx kernel: __arm64_sys_sendmsg+0x20/0x28 Feb 12 20:23:25 xxx kernel: el0_svc_common.constprop.2+0x88/0x150 Feb 12 20:23:25 xxx kernel: el0_svc_handler+0x20/0x80 Feb 12 20:23:25 xxx kernel: el0_svc+0x8/0xc Feb 12 20:23:25 xxx kernel: Code: d5384101 b9402262 b9401020 11000400 (f8626a99) Feb 12 20:23:25 xxx kernel: ---[ end trace 7b6592514db85574 ]--- Message from syslogd@localhost at Feb 12 20:23:26 ... kernel:[ 78.799696] Internal error: Oops: 96000004 [#2] PREEMPT SMP Message from syslogd@localhost at Feb 12 20:23:26 ... kernel:[ 79.010560] Code: d5384101 b9402262 b9401020 11000400 (f8626a99) Feb 12 20:23:26 xxx kernel: Unable to handle kernel paging request at virtual address 0005001700000048 Feb 12 20:23:26 xxx kernel: Mem abort info: Feb 12 20:23:26 xxx kernel: ESR = 0x96000004 Feb 12 20:23:26 xxx kernel: EC = 0x25: DABT (current EL), IL = 32 bits Feb 12 20:23:26 xxx kernel: SET = 0, FnV = 0 Feb 12 20:23:26 xxx kernel: EA = 0, S1PTW = 0 Feb 12 20:23:26 xxx kernel: Data abort info: Feb 12 20:23:26 xxx kernel: ISV = 0, ISS = 0x00000004 Feb 12 20:23:26 xxx kernel: CM = 0, WnR = 0 Feb 12 20:23:26 xxx kernel: [0005001700000048] address between user and kernel address ranges Feb 12 20:23:26 xxx kernel: Internal error: Oops: 96000004 [#2] PREEMPT SMP Feb 12 20:23:26 xxx kernel: Modules linked in: ath9k_htc ath9k_common ath9k_hw mac80211 ath cfg80211 rfkill libarc4 cdc_ether usbnet uas nf_log_ipv4 nf_log_common nft_limit cpufreq_powersave cpufreq_conservative xt_tcpudp xt_multiport xt_LOG xt_limit xt_conntrack nft_counter nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables nfnetlink meson_rng rng_core meson_gxbb_wdt scpi_hwmon ip_tables x_tables dwmac_generic realtek dwmac_meson8b Feb 12 20:23:26 xxx kernel: CPU: 1 PID: 7 Comm: kworker/u8:0 Tainted: G D 5.4.12-meson64 #19.11.8 Feb 12 20:23:26 xxx kernel: Hardware name: Hardkernel ODROID-C2 (DT) Feb 12 20:23:26 xxx kernel: Workqueue: phy0 ath9k_led_work [ath9k_htc] Feb 12 20:23:26 xxx kernel: pstate: 60000005 (nZCv daif -PAN -UAO) Feb 12 20:23:26 xxx kernel: pc : __kmalloc_node_track_caller+0x150/0x288 Feb 12 20:23:26 xxx kernel: lr : __kmalloc_node_track_caller+0x4c/0x288 Feb 12 20:23:26 xxx kernel: sp : ffff80001005bbe0 Feb 12 20:23:26 xxx kernel: x29: ffff80001005bbe0 x28: 0000000000000000 Feb 12 20:23:26 xxx kernel: x27: ffff00000735a0b8 x26: ffff80001005bd70 Feb 12 20:23:26 xxx kernel: x25: 00000000ffffffff x24: 0000000000159801 Feb 12 20:23:26 xxx kernel: x23: ffff800011c62c54 x22: 00000000ffffffff Feb 12 20:23:26 xxx kernel: x21: 0000000000082a20 x20: 0005001700000048 Feb 12 20:23:26 xxx kernel: x19: ffff000007303800 x18: 0000000000000010 Feb 12 20:23:26 xxx kernel: x17: 0000000000000000 x16: 0000000000000000 Feb 12 20:23:26 xxx kernel: x15: 0000000000000000 x14: 3239353662372065 Feb 12 20:23:26 xxx kernel: x13: 0000000000000000 x12: 0000000000000001 Feb 12 20:23:26 xxx kernel: x11: 0000000000000000 x10: 00000000000009f0 Feb 12 20:23:26 xxx kernel: x9 : ffff80001005bd60 x8 : fefefefefefefeff Feb 12 20:23:26 xxx kernel: x7 : 0000000000000001 x6 : 0000000000000064 Feb 12 20:23:26 xxx kernel: x5 : 000000000000000c x4 : 0000000000000000 Feb 12 20:23:26 xxx kernel: x3 : 0000000000159801 x2 : 0000000000000000 Feb 12 20:23:26 xxx kernel: x1 : ffff000007395580 x0 : 0000000000000001 Feb 12 20:23:26 xxx kernel: Call trace: Feb 12 20:23:26 xxx kernel: __kmalloc_node_track_caller+0x150/0x288 Feb 12 20:23:26 xxx kernel: __kmalloc_reserve.isra.56+0x44/0xa0 Feb 12 20:23:26 xxx kernel: __alloc_skb+0x84/0x198 Feb 12 20:23:26 xxx kernel: ath9k_wmi_cmd+0x6c/0x1c8 [ath9k_htc] Feb 12 20:23:26 xxx kernel: ath9k_reg_rmw+0x7c/0x170 [ath9k_htc] Feb 12 20:23:26 xxx kernel: ath9k_hw_set_gpio+0xa8/0xf0 [ath9k_hw] Feb 12 20:23:26 xxx kernel: ath9k_led_work+0x28/0x30 [ath9k_htc] Feb 12 20:23:26 xxx kernel: process_one_work+0x1e0/0x338 Feb 12 20:23:26 xxx kernel: worker_thread+0x40/0x440 Feb 12 20:23:26 xxx kernel: kthread+0x120/0x128 Feb 12 20:23:26 xxx kernel: ret_from_fork+0x10/0x18 Feb 12 20:23:26 xxx kernel: Code: d5384101 b9402262 b9401020 11000400 (f8626a99) Feb 12 20:23:26 xxx kernel: ---[ end trace 7b6592514db85575 ]--- Message from syslogd@localhost at Feb 12 20:23:47 ... kernel:[ 99.419758] Internal error: Oops: 96000004 [#3] PREEMPT SMP Message from syslogd@localhost at Feb 12 20:23:47 ... kernel:[ 99.642872] Code: d5384101 b9402262 b9401020 11000400 (f8626a99) Feb 12 20:23:46 xxx kernel: Unable to handle kernel paging request at virtual address 0005001700000048 Feb 12 20:23:46 xxx kernel: Mem abort info: Feb 12 20:23:46 xxx kernel: ESR = 0x96000004 Feb 12 20:23:46 xxx kernel: EC = 0x25: DABT (current EL), IL = 32 bits Feb 12 20:23:46 xxx kernel: SET = 0, FnV = 0 Feb 12 20:23:46 xxx kernel: EA = 0, S1PTW = 0 Feb 12 20:23:46 xxx kernel: Data abort info: Feb 12 20:23:46 xxx kernel: ISV = 0, ISS = 0x00000004 Feb 12 20:23:46 xxx kernel: CM = 0, WnR = 0 Feb 12 20:23:46 xxx kernel: [0005001700000048] address between user and kernel address ranges Feb 12 20:23:47 xxx kernel: Internal error: Oops: 96000004 [#3] PREEMPT SMP Feb 12 20:23:47 xxx kernel: Modules linked in: ath9k_htc ath9k_common ath9k_hw mac80211 ath cfg80211 rfkill libarc4 cdc_ether usbnet uas nf_log_ipv4 nf_log_common nft_limit cpufreq_powersave cpufreq_conservative xt_tcpudp xt_multiport xt_LOG xt_limit xt_conntrack nft_counter nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables nfnetlink meson_rng rng_core meson_gxbb_wdt scpi_hwmon ip_tables x_tables dwmac_generic realtek dwmac_meson8b Feb 12 20:23:47 xxx kernel: CPU: 1 PID: 1557 Comm: systemd-timesyn Tainted: G D 5.4.12-meson64 #19.11.8 Feb 12 20:23:47 xxx kernel: Hardware name: Hardkernel ODROID-C2 (DT) Feb 12 20:23:47 xxx kernel: pstate: 60000005 (nZCv daif -PAN -UAO) Feb 12 20:23:47 xxx kernel: pc : __kmalloc_node_track_caller+0x150/0x288 Feb 12 20:23:47 xxx kernel: lr : __kmalloc_node_track_caller+0x4c/0x288 Feb 12 20:23:47 xxx kernel: sp : ffff8000105f37c0 Feb 12 20:23:47 xxx kernel: x29: ffff8000105f37c0 x28: 0000000000000000 Feb 12 20:23:47 xxx kernel: x27: 0000000000000cc0 x26: 0000000000000000 Feb 12 20:23:47 xxx kernel: x25: 00000000ffffffff x24: 0000000000159801 Feb 12 20:23:47 xxx kernel: x23: ffff800011c62c54 x22: 00000000ffffffff Feb 12 20:23:47 xxx kernel: x21: 0000000000082cc0 x20: 0005001700000048 Feb 12 20:23:47 xxx kernel: x19: ffff000007303800 x18: 0000000000000000 Feb 12 20:23:47 xxx kernel: x17: 0000000000000000 x16: 0000000000000000 Feb 12 20:23:47 xxx kernel: x15: 0000000000000000 x14: 0000000000000000 Feb 12 20:23:47 xxx kernel: x13: 0000000000000001 x12: 0000000000000000 Feb 12 20:23:47 xxx kernel: x11: 0000000000000000 x10: 0000000000000000 Feb 12 20:23:47 xxx kernel: x9 : 0000000000000000 x8 : 00000000000005c8 Feb 12 20:23:47 xxx kernel: x7 : 0000000000000014 x6 : 0000000000000000 Feb 12 20:23:47 xxx kernel: x5 : ffff000042d90e00 x4 : ffff00007fbb42f0 Feb 12 20:23:47 xxx kernel: x3 : 0000000000159801 x2 : 0000000000000000 Feb 12 20:23:47 xxx kernel: x1 : ffff00007ef4e3c0 x0 : 0000000000000001 Feb 12 20:23:47 xxx kernel: Call trace: Feb 12 20:23:47 xxx kernel: __kmalloc_node_track_caller+0x150/0x288 Feb 12 20:23:47 xxx kernel: __kmalloc_reserve.isra.56+0x44/0xa0 Feb 12 20:23:47 xxx kernel: __alloc_skb+0x84/0x198 Feb 12 20:23:47 xxx kernel: alloc_skb_with_frags+0x50/0x1e0 Feb 12 20:23:47 xxx kernel: sock_alloc_send_pskb+0x200/0x238 Feb 12 20:23:47 xxx kernel: sock_alloc_send_skb+0x1c/0x28 Feb 12 20:23:47 xxx kernel: __ip_append_data.isra.59+0x770/0xc10 Feb 12 20:23:47 xxx kernel: ip_make_skb+0xe8/0x140 Feb 12 20:23:47 xxx kernel: udp_sendmsg+0x794/0xa10 Feb 12 20:23:47 xxx kernel: inet_sendmsg+0x40/0x68 Feb 12 20:23:47 xxx kernel: sock_sendmsg+0x44/0x50 Feb 12 20:23:47 xxx kernel: __sys_sendto+0xcc/0x130 Feb 12 20:23:47 xxx kernel: __arm64_sys_sendto+0x24/0x30 Feb 12 20:23:47 xxx kernel: el0_svc_common.constprop.2+0x88/0x150 Feb 12 20:23:47 xxx kernel: el0_svc_handler+0x20/0x80 Feb 12 20:23:47 xxx kernel: el0_svc+0x8/0xc Feb 12 20:23:47 xxx kernel: Code: d5384101 b9402262 b9401020 11000400 (f8626a99) Feb 12 20:23:47 xxx kernel: ---[ end trace 7b6592514db85576 ]---
  25. Hi, Are there any news on if Armbian will be on the new H5 64bit board? Orange released an Android SDK and an Android image but I guess everyone is waiting for a decent 64bit Debian. Since took the plunge and got into the H5 wagon ordering one, I looked at the released info and obviously there was nothing I could use myself.. So the question goes to the Armbian gurus, guys do you think that there could be an Armbian release for H5 this year? Christos