Kasnoa Posted December 20, 2024 Posted December 20, 2024 Because i need a more recent kernel than 5.10 on my odroid m2, i tried armbian. i searched for the nearest model and i manage to find Radxa Rock 5C (rocky 3588s2) i flash emmc with Bleeding edge images with Armbian Linux v6.11/ Debian 12 (Bookworm)Minimal / IOT for the rock 5c in /boot/armbianEnv.txt i changed just one line after installation : fdtfile=rockchip/rk3588s-odroid-m2.dtb and after a final apt upgrade i can run version 6.12.1-edge-rockchip-rk3588 of the kernel. for now it seems fine to me. 0 Quote
Solskogen Posted January 3 Posted January 3 I'm not sure if you're Jidea on the odroid forums, but I'll reply here as well. Changing the ftdfile line does not work on my M2. If I change the default, I'm only getting a black screen. I can still access the machine on ssh to revert it. 0 Quote
Nicola Zilio Posted January 17 Posted January 17 I would also be interested in, maybe official :), support for this board. What would the procedure be for that? 0 Quote
Werner Posted January 17 Posted January 17 https://docs.armbian.com/Process_Contribute/ https://docs.armbian.com/User-Guide_Board-Support-Rules/ 0 Quote
Walter Zambotti Posted February 9 Posted February 9 @Solskogen You didn't mention whether you also did the final apt upgrade after changing the line /boot/armbianEnv.txt. Did you? 0 Quote
Solskogen Posted February 14 Posted February 14 I did, but someone on the odroid forum have created a own odroid m2 config file, so I'm using that for now. Everything seem to work just fine except hdmi sound 0 Quote
ysfm Posted March 27 Posted March 27 (edited) Hello. Is it possible to add Type C display alt mode support? https://lore.kernel.org/linux-rockchip/20250223113036.74252-1-andyshrk@163.com/ https://patchwork.kernel.org/project/linux-arm-kernel/patch/20250312104214.525242-7-andyshrk@163.com/ ****The Display Port driver is not included in 6.14. So we will have to wait now. Edited March 28 by ysfm I edited the message because I could not delete it. 0 Quote
Walter Zambotti Posted June 2 Posted June 2 (edited) Testing the M2 16G with trunk 90 (Kernel 6.15) & trunk 38 (Kern 6.14.8) and the USB-C OTG port isn't working. [ +0.245948] usb 7-1: new full-speed USB device number 2 using xhci-hcd [ +0.124258] usb 7-1: device descriptor read/64, error -71 [ +0.227984] usb 7-1: device descriptor read/64, error -71 [ +0.223715] usb 7-1: new full-speed USB device number 3 using xhci-hcd [ +0.124295] usb 7-1: device descriptor read/64, error -71 [ +0.223803] usb 7-1: device descriptor read/64, error -71 [ +0.104107] usb usb7-port1: attempt power cycle [ +0.395844] usb 7-1: new full-speed USB device number 4 using xhci-hcd [ +0.000112] usb 7-1: Device not responding to setup address. [ +0.203891] usb 7-1: Device not responding to setup address. [ +0.203946] usb 7-1: device not accepting address 4, error -71 [ +0.000609] usb 7-1: WARN: invalid context state for evaluate context command. [ +0.119353] usb 7-1: new full-speed USB device number 5 using xhci-hcd [ +0.000118] usb 7-1: Device not responding to setup address. [ +0.204373] usb 7-1: Device not responding to setup address. [ +0.207473] usb 7-1: device not accepting address 5, error -71 [ +0.000613] usb 7-1: WARN: invalid context state for evaluate context command. [ +0.000109] usb usb7-port1: unable to enumerate USB device [ +30.217458] usb 7-1: new full-speed USB device number 6 using xhci-hcd [ +0.123993] usb 7-1: device descriptor read/64, error -71 [ +0.231951] usb 7-1: device descriptor read/64, error -71 [ +0.223935] usb 7-1: new full-speed USB device number 7 using xhci-hcd [ +0.120028] usb 7-1: device descriptor read/64, error -71 [ +0.224108] usb 7-1: device descriptor read/64, error -71 [ +0.103939] usb usb7-port1: attempt power cycle [ +0.396008] usb 7-1: new full-speed USB device number 8 using xhci-hcd [ +0.000139] usb 7-1: Device not responding to setup address. [ +0.203807] usb 7-1: Device not responding to setup address. [ +0.207853] usb 7-1: device not accepting address 8, error -71 [ +0.000608] usb 7-1: WARN: invalid context state for evaluate context command. [ +0.119394] usb 7-1: new full-speed USB device number 9 using xhci-hcd [ +0.000140] usb 7-1: Device not responding to setup address. [ +0.204031] usb 7-1: Device not responding to setup address. [ +0.203926] usb 7-1: device not accepting address 9, error -71 [ +0.000796] usb 7-1: WARN: invalid context state for evaluate context command. [ +0.000293] usb usb7-port1: unable to enumerate USB device [Jun 2 19:50] usb 7-1: new full-speed USB device number 10 using xhci-hcd [ +0.123926] usb 7-1: device descriptor read/64, error -71 [ +0.116517] xhci-hcd xhci-hcd.7.auto: remove, state 4 [ +0.000011] usb usb8: USB disconnect, device number 1 [ +0.000280] xhci-hcd xhci-hcd.7.auto: USB bus 8 deregistered [ +0.000009] xhci-hcd xhci-hcd.7.auto: remove, state 1 [ +0.000004] usb usb7: USB disconnect, device number 1 [ +0.055430] usb usb7-port1: attempt power cycle Same USB-C device (CCD camera) tested and working in the USB-3 port. Edited June 4 by Walter Zambotti 0 Quote
Walter Zambotti Posted June 4 Posted June 4 (edited) After the last update/upgrade USB BUS 7 has completely disappeared! So no life at all on the USB-C port. The following packages were upgraded : linux-dtb-edge-rockchip64, armbian-bsp-cli-odroidm2-edge, linux-image-edge-rockchip64, linux-u-boot-odroidm2-edge, armbian-firmware I suspect linux-dtb-edge-rockchip64 is not the M2 specific package and it has over written the dtb. Also I can't seem to install the kernel headers from armbian-config. It appears to go through the motions but nothing is installed. Also where can I find a documentation on what each device overlay (in armbian-config) is for? Edited June 4 by Walter Zambotti 0 Quote
Walter Zambotti Posted June 11 Posted June 11 Just plugged a M.2 M key to E key adapter with an Intel AX200 iwlwifi (installed the firmware) booted up and Wifi 6 is going without using a USB port. My project is one step closer!!! Just have to get that last USB-C port working. 0 Quote
Walter Zambotti Posted Friday at 03:39 AM Posted Friday at 03:39 AM The latest 6.16.RC3 kernel breaks the Intel PCI Wifi drivers. Was working in 6.15 without issue: [ 5.321789] iwlwifi 0004:41:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz [ 5.329839] iwlwifi 0004:41:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37 [ 5.330430] iwlwifi 0004:41:00.0: loaded firmware version 77.864baa2e.0 cc-a0-77.ucode op_mode iwlmvm [ 5.587350] iwlwifi 0004:41:00.0: Detected RF HR B3, rfid=0x10a100 [ 5.653139] iwlwifi 0004:41:00.0: base HW address: 04:ed:33:54:7e:d2 [ 5.716280] iwlwifi 0004:41:00.0 wlP4p65s0: renamed from wlan0 [ 8.890717] iwlwifi 0004:41:00.0: Registered PHC clock: iwlwifi-PTP, with index: 1 [ 8.890759] WARNING: CPU: 6 PID: 1203 at drivers/net/wireless/intel/iwlwifi/mvm/mld-mac.c:37 iwl_mvm_mld_mac_ctxt_cmd_common+0x158/0x1e4 [iwlmvm] [ 8.890778] Modules linked in: sunrpc iwlmvm pwm_fan display_connector mac80211 rk805_pwrkey libarc4 snd_soc_hdmi_codec snd_soc_core hantro_vpu snd_compress rockchip_vdec2(C) snd_pcm_dmaengine v4l2_vp9 rk_crypto2 iwlwifi v4l2_jpeg rockchip_rga snd_pcm sm3_generic v4l2_h264 libsm3 videobuf2_dma_contig v4l2_mem2mem videobuf2_dma_sg snd_timer videobuf2_memops videobuf2_v4l2 snd videodev joydev panthor soundcore cfg80211 videobuf2_common drm_gpuvm drm_exec mc rfkill gpu_sched drm_shmem_helper cpufreq_dt zram binfmt_misc sch_fq_codel dm_mod autofs4 realtek phy_rockchip_samsung_hdptx phy_rockchip_usbdp fusb302 tcpm typec rtc_pcf8563 dwmac_rk nvmem_rockchip_otp stmmac_platform stmmac rockchip_rng rng_core pcs_xpcs rockchipdrm dw_hdmi_qp dw_hdmi cec dw_mipi_dsi analogix_dp drm_display_helper drm_dp_aux_bus [ 8.891251] iwlwifi 0004:41:00.0: Microcode SW error detected. Restarting 0x0. [ 8.891978] iwlwifi 0004:41:00.0: Start IWL Error Log Dump: [ 8.892489] iwlwifi 0004:41:00.0: Transport status: 0x0000004B, valid: 6 [ 8.892494] iwlwifi 0004:41:00.0: Loaded firmware version: 77.864baa2e.0 cc-a0-77.ucode [ 8.892499] iwlwifi 0004:41:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.