Jump to content

Search the Community

Showing results for tags 'odroidc2'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Khadas VIM4
    • Radxa Zero 2
    • Odroid M1
    • NanoPi R5S
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Old bug tracker - read only
    • Old bug tracker - read only
  • TV Boxes's General Chat
  • TV Boxes's Reviews/Tutorials
  • TV Boxes's FAQ
  • TV Boxes's TV Boxes running Armbian
  • TV Boxes's Rockchip CPU Boxes
  • TV Boxes's Amlogic CPU Boxes
  • TV Boxes's Allwinner CPU Boxes
  • Android's Forums
  • Gaming on ARM's Reviews
  • Gaming on ARM's Issues

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


Skype


Github


Location


Interests

  1. I would like to permanently change at start up the UART permissions of /dev/ttyAML0 to give user, read write permissions always. I can do this with the usual "chmod" command but this gets reset after every boot and sometimes also during normal operations. Can somebody direct me to how this can be done please? xuraax
  2. I use DietPi on my Odroid C2. I post here because the developer mentioned that the DietPi image is based on the Armbian kernel and he suggested posting here. When I attach the R5 to a USB port of my Odroid C2 it is not recognized. lsusb and dmesg do not show it. On my Ubuntu 22.04 PC it does show up. Looked around and finally found an old post on this forum that mentions a bug with the C2 in recognizing USB devices. The mentioned workaround is to add a second USB device and reboot the device. I added an USB drive and both are now recognized, initialized and working after a reboot. (When removing one of the devices it again doesn’t stick after a reboot.) I can not find more information on this. It seems this problem isn't solved? Regards, Joost
  3. I have an C2 and an old VU7 (800x480p60hz) https://wiki.odroid.com/accessory/display/vu_series/vu7/vu7#tab__odroid-c2 that I was hoping to use for a mini kiosk. Was able to run the older Hard Kernel supplied images with the uboot boot.ini updates suggested above to change disable auto detect, fix the resolution, and set to DVI rather than HDMI mode. When I loaded the latest Focal image from Armbian when I have the screen switched on then the kernel faults and reboots. ## Flattened Device Tree blob at 04080000 Booting using the fdt blob at 0x4080000 Loading Ramdisk to 7b06a000, end 7bf49d63 ... OK Loading Device Tree to 000000007aff8000, end 000000007b069fff ... OK Starting kernel ... GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0; TE: 59543 no sdio debug board detected BL2 Built : 11:44:26, Nov 25 2015. gxb gfb13a3b-c2 - jcao@wonton I assume all I should need to do is update the /boot/boot.cmd, run `mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr` and the boot.scr should be updated. Also set: setenv disable_vu7 "false" But that variable isn't being used anywhere in the boot.cmd so I don't think it is being applied.
  4. Odroid C2 never starting after a soft reboot (reboot command). I have the same problem which other user is having with the Odroid C4 With the last kernel I have 5.10.102-meson64 the Odroid C2 never boots again after the "reboot" command, I need to unplug and plug again the power suply. Thanks and best regards, David
  5. This week we discontinued the default 3.x kernel for the Odroid C2, and are working on the 4.18/4.19 kernels. A few odds and ends have come up, the biggest one appears to be the gpio-hog in the C2 device tree somehow not working, causing the USB hub on the board to never be powered on. root@odroidc2:/sys/class/gpio# cat /sys/kernel/debug/gpio gpiochip1: GPIOs 378-496, parent: platform/c8834000.periphs:pinctrl@4b0, periphs-banks: gpio-392 ( |mdio-reset ) out hi gpio-407 ( |reset ) out hi gpio-422 ( |cd ) in lo gpio-465 ( |TFLASH_VDD ) out hi gpiochip0: GPIOs 497-511, parent: platform/c8100000.bus:pinctrl@14, aobus-banks: gpio-500 ( |TF_IO ) out lo gpio-501 ( |usb-hub-reset ) out hi gpio-502 ( |USB_OTG_PWR ) out hi gpio-510 ( |c2:blue:alive ) out lo The hog claims it is there, but I get no power to the port. The other is the HDMI output becoming extremely fussy about the sort of monitor it's been given. [update] On the NanoPi K2 I actually get a crash on boot with my HDMI --> DVI adapter monitor. With both monitors, if plugged in after boot, desktop displays (on C2 only the pure HDMI monitor will display at all), but a fault occurs: FYI @Neil Armstrong
  6. Hi there, I've an odroid C2 device used for home automation and running armbian (uname -a) : Linux odroidc2 4.19.69-meson64 which is running stable with no problem. Yesterday, I've downloaded a fresh image of latest armbian for odroid C2, named Armbian_21.02.1_Odroidc2_buster_current_5.10.12.img.xz. Put it on a new SD card and booted. It booted correctly but I've NO network. The LAN chip doesnt work at all, altough it appear in the device list I've theses entries in dmesg: [ 2.217600] meson8b-dwmac c9410000.ethernet: IRQ eth_wake_irq not found [ 2.217611] meson8b-dwmac c9410000.ethernet: IRQ eth_lpi not found [ 2.217694] meson8b-dwmac c9410000.ethernet: PTP uses main clock [ 2.218292] random: fast init done [ 2.218418] meson8b-dwmac c9410000.ethernet: User ID: 0x11, Synopsys ID: 0x37 [ 2.218426] meson8b-dwmac c9410000.ethernet: DWMAC1000 [ 2.218431] meson8b-dwmac c9410000.ethernet: DMA HW capability register supported [ 2.218435] meson8b-dwmac c9410000.ethernet: RX Checksum Offload Engine supported [ 2.218439] meson8b-dwmac c9410000.ethernet: COE Type 2 [ 2.218443] meson8b-dwmac c9410000.ethernet: TX Checksum insertion supported [ 2.218446] meson8b-dwmac c9410000.ethernet: Wake-Up On Lan supported [ 2.218538] meson8b-dwmac c9410000.ethernet: Normal descriptors [ 2.218543] meson8b-dwmac c9410000.ethernet: Ring mode enabled [ 2.218547] meson8b-dwmac c9410000.ethernet: Enable RX Mitigation via HW Watchdog Timer ... [ 10.568311] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1 [ 10.568329] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 10.615619] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1 [ 10.615634] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 10.716190] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1 [ 10.716207] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 10.735509] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1 [ 10.735535] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) the first message I see when I boot (while plug in the power) is: Net: Could not get PHY for ethernet@c9410000: addr -1 No ethernet found The device is working with older armbian version but not the latest ? Could anyone look at it because the image available for download seem's broken and should not be distributed like this. I've reverted back to my old image (that's why I don't have the full log) and lost my week end on it, trying to sort it out without success. Could this be related to the .dtb ?? Thanks you
  7. according to here 5.13 is latest kernel https://www.armbian.com/odroid-c2/ but when I issue: sudo apt-get update && sudo apt-get dist-upgrade -y I'm still on 5.10....
  8. Hi , i buiild a SPDIF connector like shown here: https://forum.odroid.com/viewtopic.php?t=21477 it uses the J7 SPDIF output which is connected to HDMI. On coreelec i can clearly see a HDMI soundcard output with aplay -L , i dont see that on armbian.... Is odroid c2 spdif output on armbian working ? why do i not see this soundcard that f.e. libreelec is showing ( i have 2 odroid c2s , one is running coreelec in my living room with HDMI connector working) im using a little older armbian distro since the latest has ethernet issues on C2 (im using 20.11 , kernel 5.9.10 debian edition ) regards, Simon
  9. Hello all! I have an ODROID-C2 that I am trying to use with a GPS connected over UART for timing purposes, which requires the use of pps. Based on my searching and reading in this forum, I have determined that for my OS and kernel (Focal, 5.9.14) I should be able to do so by adding overlay=pps-gpio to armbianEnv.txt. What is not clear to me, however, is how to specify which pin to use! In this thread I see windysea said: But I don't know how to use this information! I have found no documentation on param_pps_*, and my attempts at guessing based on information from other threads and resources have failed to work so far. I have been fiddling with this for a few days to no avail now, so any assistance would be greatly appreciated. Regards, John
  10. 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?
  11. Hi, I'm getting a random packet loss on the ethernet connection. When pinging, about 6-8% pings are lost, the ssh connection sometimes freezes for a moment. Things I've tried so far: Disabled NetworkManager, added eth0 in /etc/network/interfaces with a static ip4 address Disabled EEE for eth0 Replaced ethernet cable Plugged into different switch None of them made something better. My C1 & C4 with the same Armbian Buster version/release don't have this issue. How to investigate deeper in this issue?
  12. I recently bought a 64 GB eMMC module (chip on orange board) from Ordoid/Hardkernel but u-boot does not recognize the eMMC. What I did: installed the official Armbian_20.11.10_Odroidc2_focal_current_5.9.14.img.xz with Etcher on SD card booted successfully from SD card, eMMC is accessible from within Armbian/Ubuntu executed nand-sata-install to transfer the system to eMMC, which completed without error messages shutdown the system, removed SDcard and restarted it The serial console displayed the following: U-Boot 2020.10-armbian (Jan 05 2021 - 01:40:47 +0100) odroid-c2 Model: Hardkernel ODROID-C2 SoC: Amlogic Meson GXBB (S905) Revision 1f:c (0:1) DRAM: 2 GiB MMC: mmc@72000: 0, mmc@74000: 1 In: serial Out: serial Err: serial Net: eth0: ethernet@c9410000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! Card did not respond to voltage select! MMC Device 2 not found no mmc device at slot 2 starting USB... Bus usb@c9100000: USB DWC2 scanning bus usb@c9100000 for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found and then tried to boot via network. I then flashed the eMMC with the official Odroid image ubuntu-20.04-3.16-minimal-odroid-c2-20200617.img.xz and the system booted up successfully, so the eMMC module is working fine. Next step was to try the nightly build (Armbian_21.02.0-trunk.80_Odroidc2_focal_current_5.10.10_gnome_desktop.img.xz, with Etcher flashed on SD, then nand-sata-install) and again the eMMC as not visible in u-boot so the system did not come up. Therefore I set up an Armbian build environment and first tried to use this promising patch for u-boot https://gitlab.denx.de/u-boot/custodians/u-boot-amlogic/-/commit/5ccd5d2cc98224108ae9fb09593a862c9caa5e80 but it seemed not to be suficient. I then replaced the provided u-boot v2020.10 with the new v2021.01 version and after replacing the kernel and uboot packages with the self compiled ones the eMMC was recognised by u-boot and the system boots from the orange 64GB eMMC module. U-Boot 2021.01-armbian (Feb 01 2021 - 11:57:23 +0100) odroid-c2 Model: Hardkernel ODROID-C2 SoC: Amlogic Meson GXBB (S905) Revision 1f:c (0:1) DRAM: 2 GiB MMC: mmc@72000: 0, mmc@74000: 1 In: serial Out: serial Err: serial Net: eth0: ethernet@c9410000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! : -110 switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 7136 bytes read in 1 ms (6.8 MiB/s) ## Executing script at 08000000 161 bytes read in 1 ms (157.2 KiB/s) 15703885 bytes read in 342 ms (43.8 MiB/s) 25461248 bytes read in 556 ms (43.7 MiB/s) 38868 bytes read in 2 ms (18.5 MiB/s) 232 bytes read in 1 ms (226.6 KiB/s) Applying kernel provided DT fixup script (meson-fixup.scr) The "Card did not respond to voltage select" message is from the missing SD card Therefore I kindly ask to upgrade the u-boot of Odroid C2 to version 2021.01 in the next release.
  13. A few weeks ago, after a firmware-upgrade my C2 bricked. It's blue led didn't flash any more and no serial console was available. Since I had everything setup just right I wanted to recover it using these steps here: https://docs.armbian.com/User-Guide_Recovery/#replacing-boot Off course I replaced the packages with the ones for the C2. Specifically: https://mirrors.dotsrc.org/armbian-apt/pool/main/l/linux-5.9.14-meson64/linux-dtb-current-meson64_20.11.3_arm64.deb https://mirrors.dotsrc.org/armbian-apt/pool/main/l/linux-5.9.14-meson64/linux-image-current-meson64_20.11.3_arm64.deb https://mirrors.dotsrc.org/armbian-apt/pool/main/l/linux-buster-root-current-odroidc2/linux-buster-root-current-odroidc2_20.11.6_arm64.deb https://mirrors.dotsrc.org/armbian-apt/pool/main/a/armbian-firmware/armbian-firmware_20.11.3_all.deb After following all the steps, I don't seem to have an uInitrd. I don't know if that would help booting up again, but from the symlinks section it's the only file missing after following all the steps: Does anybody know what went wrong or guide me towards the right steps to recover my C2?
  14. I started to play with lima(mesa mali drivers) on Odroid C2 with ubuntu 19.04 with kernel 5.3. rc6 with lima enabled I add latest mesa drivers from https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers there are only arm64 packages But there is problem on amlogic platform with order of dri/card* as dri/card0 point to lima and dri/card1 point to mesa drm driver but most software don't have options to set it up and they expect drm driver on card0 so there is problem in weston 5 for example https://lists.freedesktop.org/archives/wayland-devel/2018-September/039446.html but weston 4 and 6(https://packages.debian.org/sid/weston) is working fine so what is working in my case I was able to start weston4 like weston --drm-device=card1 then weston-simple-egl then glmark2-wayland so good luck with lima and panfrost it will be nice to test panfrost on odroid xu4 It will be nice to have simple options to enable lima/panfrost on armbian what do you think? It should be metter of enabling LIMA in kernel configs and add install mesa from oibaf ppa I asked him about armhf build be he talk about small amount of users lima gitlab issues https://gitlab.freedesktop.org/lima/mesa/issues
  15. I tried Armbian_20.11.0-trunk.32_Odroidc2_focal_current_5.9.8.img and Armbian_20.11.0-trunk.32_Odroidc2_buster_current_5.9.8.img and both will not boot after apt upgrade. Armbian_20.08.22_Odroidc2_focal_current_5.9.6.img will not come up after sudo reboot and has to be power cycled. I believe the latter has been a persistent issue.
  16. With my OPi Zero, I noticed that at random times the ethernet connection somehow gets disabled. The only way to recover is by power cycling. I use the device as Pi-Hole (so when ethernet gets disconnected, I don't have internet anymore), print server and UniFi controller. I decided to swap it for my Odroid C2. Odd enough the C2 has the same issue. Maybe someone can help me with this? When powercycled, the Odroid with the latest Armbian (installed two days ago) is all up and running fine. It can connect to the internet, I can SSH into it. The ethernet led is flashing orange, so the gigabit connection is available. However, at rondom times the ethernet leds are both disabled. At this point, the C2 is still alive, but there's no way to access it without power cycling. I've tried removing the ethernet cable and connecting it again, hoping Armbian would recognize the connection - what happens in this case is that the green led will flash a few times (100Mbit) but the device is still offline. I've added some information from the log here before rebooting. This information keeps repeating in the log files... Hopefully someone can guide my as how to get the connection stable.
  17. Dear community, unfortunately, "armbianmonitor -u" doesn't give me a link anymore, and I'm not sure if uploading works at all. So I cant provide the information As our deployment date approaches, we try to finalize our Armbian system for North Pacific seafloor... and found some unexpected problems (problems seem alwas to be unexpected): The TigerVNC has two problems on Armbian, and it would be great if you could verify that issues and maybe problem some helpful ideas: (1) TigerVNC (tigervnc-common/stable,now 1.9.0) needs the following workaround to start at all: LD_PRELOAD=/lib/aarch64-linux-gnu/libgcc_s.so.1 vncserver :1 -localhost no Seems to be libunwind8 related, and is ugly, but not the main problem. (2) TigerVNC can be started by crontab "@reboot", but fails to open a desktop. There are messages about dbus problems, the display closes afterwards. I use Armbian NEXT, with Debian Buster, and kernel is locked to 4.19.90 (due to the various troubles with the new kernel, which seems to be optimzed for video playback but not stable operation). Any help is appreciated, and if you need more information, please let me know. So far, Michael
  18. Hi all, as a small status update on the seafloor business, here are some pictures of the new Odroid C2 based instruments which will be deployed in September/October in the northers Pacific. Ten modules with different functionality will be deployed, all based on a standard setup of Odroid C2, TRB3sc FPGA based TDC DAQ system, one PADIWA preamp, and a modded mdedia converter serving as a fully configurable mini switch. One of the modules carries several Hamamatsu mini spectrometers, as well as a camera, to observe bioluminescence. Another module is targeting at muon tracking with SiPM based readout: I have some more picture of the more "fancy" PMT based modules, but don't want to flood this forum now with too many pictures. To all of you: thanks for the support you gave us over the last year, and the discussions on specific topics! Deployment pictures will follow once the modules are in place on the seafloor, 2600m deep in the Pacific (and operational, hopefully, this time we just have a GbE fiber, no serial port...) See you, Michael
  19. With our Current moving to 5.7, anyone building it themselves should report anything missing/new/different/wanted here. Le Potato La Frite NanoPi K2 ODROID C2 VIM 1 USB OK OK OK OK OK REBOOT NOK OK OK NOK NOK SOUND OK OK OK OK OK HDMI OK OK OK OK OK Onboard WiFi NA NA OK NA OK
  20. I have an application that depends on the Linux HID USB gadget via configfs on the USB OTG port. It works under Raspberry Pi OS (2020-05-27-buster-lite), but I'm having trouble getting it to work under Armbian (Armbian_20.05.2_Odroidc2_buster_current_5.6.15). Specifically, I'm having trouble getting the configfs module to run. What I've done so far: Removed the J1 jumper as described on the ODROID wiki. Recompiled /boot/dtbs/amlogic/meson-gxbb-odroidc2.dtb to set dr_mode = "peripheral"; as described in this ODROID magazine article. When I run this script with sudo: #!/usr/bin/env bash modprobe libcomposite cd /sys/kernel/config/usb_gadget/ mkdir -p g1 cd g1 echo 0x1d6b > idVendor # Linux Foundation echo 0x0104 > idProduct # Multifunction Composite Gadget echo 0x0100 > bcdDevice # v1.0.0 echo 0x0200 > bcdUSB # USB2 STRINGS_DIR="strings/0x409" mkdir -p "$STRINGS_DIR" echo "6b65796d696d6570690" > "${STRINGS_DIR}/serialnumber" echo "Linux Foundation" > "${STRINGS_DIR}/manufacturer" echo "Generic USB Keyboard" > "${STRINGS_DIR}/product" FUNCTIONS_DIR="functions/hid.usb0" mkdir -p "$FUNCTIONS_DIR" echo 1 > "${FUNCTIONS_DIR}/protocol" # Keyboard echo 1 > "${FUNCTIONS_DIR}/subclass" # Boot interface subclass echo 8 > "${FUNCTIONS_DIR}/report_length" # Write the report descriptor # Source: https://www.kernel.org/doc/html/latest/usb/gadget_hid.html echo -ne \\x05\\x01\\x09\\x06\\xa1\\x01\\x05\\x07\\x19\\xe0\\x29\\xe7\\x15\\x00\\x25\\x01\\x75\\x01\\x95\\x08\\x81\\x02\\x95\\x01\\x75\\x08\\x81\\x03\\x95\\x05\\x75\\x01\\x05\\x08\\x19\\x01\\x29\\x05\\x91\\x02\\x95\\x01\\x75\\x03\\x91\\x03\\x95\\x06\\x75\\x08\\x15\\x00\\x25\\x65\\x05\\x07\\x19\\x00\\x29\\x65\\x81\\x00\\xc0 > "${FUNCTIONS_DIR}/report_desc" CONFIG_INDEX=1 CONFIGS_DIR="configs/c.${CONFIG_INDEX}" mkdir -p "$CONFIGS_DIR" echo 250 > "${CONFIGS_DIR}/MaxPower" CONFIGS_STRINGS_DIR="${CONFIGS_DIR}/strings/0x409" mkdir -p "$CONFIGS_STRINGS_DIR" echo "Config ${CONFIG_INDEX}: ECM network" > "${CONFIGS_STRINGS_DIR}/configuration" ln -s "$FUNCTIONS_DIR" "${CONFIGS_DIR}/" ls /sys/class/udc > UDC chmod 777 /dev/hidg0 It fails with on the last line with: chmod: cannot access '/dev/hidg0': No such file or directory And /sys/class/udc is not a symlink, as it's expected to be: $ ls /sys/class/udc -l total 0 Also, when I run dmesg | grep configfs, I get nothing, whereas on RasPiOS I see a message about dwc2 loading the configfs-gadget. It there anything else I can do to enable the USB HID gadget on Armbian?
  21. Hi, I have question about ports /dev/ttyAML1 and /dev/ttyAML2 (device Odroid C2, Image Buster) I dont see in dmesg the ports /dev/ttyAML1 and /dev/ttyAML2 [ 0.000256] printk: console [tty1] enabled [ 1.877506] c81004c0.serial: ttyAML0 at MMIO 0xc81004c0 (irq = 13, base_baud = 1500000) is a meson_uart [ 1.877549] printk: console [ttyAML0] enabled [ 3.452296] systemd[1]: Created slice system-serial\x2dgetty.slice. [ 3.455230] systemd[1]: Created slice system-getty.slice. [ 4.257715] cdc_acm 1-1.4:1.0: ttyACM0: USB ACM device overlays=i2cA i2cB uartA uartB uartC w1-gpio How should i chnage the meson-gxbb-odroidc2.dtb to working configuration with kernel 5.4.27-meson64 This is actual configuration: serial@84c0 { compatible = "amlogic,meson-gx-uart"; reg = < 0x00 0x84c0 0x00 0x18 >; interrupts = < 0x00 0x1a 0x01 >; status = "disabled"; clocks = < 0x0e 0x03 0x1a 0x0e >; clock-names = "xtal\0pclk\0baud"; pinctrl-0 = < 0x0f >; pinctrl-names = "default"; phandle = < 0x47 >; }; With kernel 4.19.69 was working with following change in meson-gxbb-odroidc2.dtb serial@84c0 { compatible = "amlogic,meson-gx-uart"; reg = < 0x00 0x84c0 0x00 0x18 >; interrupts = < 0x00 0x1a 0x01 >; status = "disabled"; clocks = < 0x0d 0x0b 0x1a 0x0d >; clock-names = "xtal\0pclk\0baud"; pinctrl-names = "default"; pinctrl-0 = < 0x72 >; phandle = < 0x43 >; }; Thanks for help
  22. Today I installed packages (apt-get upgrade): armbian-config armbian-firmware linux-buster-root-current-odroidc2 linux-dtb-current-meson64 linux-image-current-meson64 linux-u-boot-odroidc2-current and rebooted the system. Afterwards no more USB devices were found: Active USB Hub, USB Hd, USB mouse, USB memorystick Regardless if connected via USB Hub or directly. lsusb doesn't show any devices. Any hints? Thanks in advance
  23. Hello, So I have ODROID C2 running latest Armbian bionic with kernel 5.6.11-meson64 #trunk.130. I have a Quectel E25 4G LTE modem connected via USB port. Everything works like a charm - BUT - whenever I try to download (or upload) even small amounts of data, I get kernel panic and the process hangs. Sometimes, the whole device crashes. It happens only when I try to download or upload data. Even trying to paste large amount of text into a terminal text editor causes kernel panic. This does NOT happen if I'm connected via ethernet. Here's the dmesg (while I was trying to wget a file) - [ 1552.786535] dwc2 c9100000.usb: dwc2_hc_chhltd_intr_dma: Channel 5 - ChHltd set, but reason is unknown [ 1552.790108] dwc2 c9100000.usb: hcint 0x00000002, intsts 0x04200009 [ 1552.796227] dwc2 c9100000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 1552.803673] dwc2 c9100000.usb: dwc2_update_urb_state(): trimming xfer length [ 1552.812182] Unable to handle kernel paging request at virtual address 00565416857379cc [ 1552.818442] Mem abort info: [ 1552.821242] ESR = 0x96000004 [ 1552.824238] EC = 0x25: DABT (current EL), IL = 32 bits [ 1552.829533] SET = 0, FnV = 0 [ 1552.832519] EA = 0, S1PTW = 0 [ 1552.835603] Data abort info: [ 1552.838398] ISV = 0, ISS = 0x00000004 [ 1552.842254] CM = 0, WnR = 0 [ 1552.845185] [00565416857379cc] address between user and kernel address ranges [ 1552.852299] Internal error: Oops: 96000004 [#7] PREEMPT SMP [ 1552.857720] Modules linked in: fuse rfkill cpufreq_powersave cpufreq_conservative snd_soc_hdmi_codec snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer snd soundcore ac97_bus dw_hdmi_i2s_audio qmi_wwan cdc_wdm usbnet option usb_wwan usbserial zstd lima meson_dw_hdmi meson_vdec(C) gpu_sched dw_hdmi v4l2_mem2mem meson_drm videobuf2_dma_contig videobuf2_v4l2 videobuf2_memops drm_kms_helper videobuf2_common videodev meson_rng rng_core drm meson_gxbb_wdt meson_ir ao_cec mc drm_panel_orientation_quirks meson_canvas cec scpi_hwmon zram sch_fq_codel ip_tables x_tables uas dwmac_generic realtek dwmac_meson8b [ 1552.910249] CPU: 1 PID: 5010 Comm: wget Tainted: G D C 5.6.11-meson64 #trunk.130 [ 1552.918693] Hardware name: Hardkernel ODROID-C2 (DT) [ 1552.923612] pstate: 40000005 (nZcv daif -PAN -UAO) [ 1552.928365] pc : skb_release_data+0xd0/0x128 [ 1552.932583] lr : skb_release_all+0x24/0x30 [ 1552.936633] sp : ffff800012cebaa0 [ 1552.939911] x29: ffff800012cebaa0 x28: ffff000038bd5300 [ 1552.945172] x27: 0000000000000000 x26: 0000000000000000 [ 1552.950432] x25: ffff0000329c2dd0 x24: 0000000000003e99 [ 1552.955694] x23: 0000000000000001 x22: ffff000035a086c0 [ 1552.960955] x21: ffff000038bd5300 x20: ffff000035a086f0 [ 1552.966216] x19: 0000000000000000 x18: 0000000000000000 [ 1552.971477] x17: 0000000000000000 x16: 0000000000000000 [ 1552.976739] x15: 0000000000000000 x14: 9f572ea8481e2814 [ 1552.982000] x13: 335fbd453f89511e x12: 9db6920c2442ac6a [ 1552.987261] x11: 47c53f91911e5b7b x10: 00000000000003cd [ 1552.992522] x9 : 0000000000000001 x8 : 9a25c697375866e4 [ 1552.997783] x7 : baf054b7c521bef4 x6 : 00000008b3a2c9ef [ 1553.003045] x5 : ffff0000329c3274 x4 : ffff0000329c2de8 [ 1553.008306] x3 : 0000000000000780 x2 : 0000000000000640 [ 1553.013567] x1 : 0000000000000020 x0 : c7565416857379cc [ 1553.018830] Call trace: [ 1553.021247] skb_release_data+0xd0/0x128 [ 1553.025126] skb_release_all+0x24/0x30 [ 1553.028835] __kfree_skb+0x14/0x28 [ 1553.032200] tcp_recvmsg+0x670/0xa30 [ 1553.035737] inet_recvmsg+0x50/0x120 [ 1553.039275] sock_recvmsg+0x48/0x58 [ 1553.042723] sock_read_iter+0x84/0xd8 [ 1553.046347] new_sync_read+0x164/0x178 [ 1553.050053] __vfs_read+0x2c/0x40 [ 1553.053330] vfs_read+0x9c/0x188 [ 1553.056522] ksys_read+0xd0/0xe8 [ 1553.059713] __arm64_sys_read+0x18/0x20 [ 1553.063512] el0_svc_common.constprop.2+0x88/0x150 [ 1553.068251] do_el0_svc+0x20/0x80 [ 1553.071530] el0_sync_handler+0x118/0x188 [ 1553.075496] el0_sync+0x140/0x180 [ 1553.078778] Code: 6b13001f 54fffdcc f94006c0 b40000a0 (f9400013) [ 1553.084814] ---[ end trace 49bbe6bc41c38aaa ]--- I tried to downgrade the kernel to an older version and this does not seem to solve the issue. Any ideas?
  24. Hi. Running Armbian Buster on Odroid C-2, Linux odroidc2 5.4.35-meson64 #trunk SMP PREEMPT Thu Apr 23 18:16:56 CEST 2020 aarch64 GNU/Linux With "armbian-config" I'm triyng to switch to another Kernel without success, error on "switch_kernel.log" file is: linux-image-dev-meson64=20.05.0-trunk.130 linux-dtb-dev-meson64=20.05.0-trunk.130 linux-u-boot-odroidc2-dev Any idea?
  25. Hi. Running (installed from img file on SD Card) Armbian "Armbian_20.02.8_Odroidc2_buster_current_5.4.28". If I try to reboot (reboot command) the Odroid-C2 does not startup again (so it does not reboot)..... Only way to startup it again is to electric poweroff and then poweron. uname -a: Linux odroidc2 5.4.28-meson64 #20.02.8 SMP PREEMPT Mon Mar 30 09:12:52 CEST 2020 aarch64 GNU/Linux How to solve? Thank you.
×
×
  • Create New...