Jump to content

jock

Members
  • Posts

    2154
  • Joined

  • Last visited

Posts posted by jock

  1. 8 hours ago, Obmor said:

    Do I understand correctly that when changing/updating the kernel version, the driver will not load and you will need to rebuild the module?

    Yes, it is correct. But I will enable the rtl8189es module in the armbian mainline so forthcoming kernels will have the module compiled in. Just not update the kernel in the meantime.

  2. 2 hours ago, Obmor said:

    It worked! thank you very much! There are already 2 WLANs: WLAN0 and WLAN1 hmm..

    That's because usually these drivers are suited for Android and they expose by default a "regular" interface and a "P2P" interface for direct connection.

    Just use wlan0, or there should be a module option to disable the p2p interface.

  3. @Obmor

    here it is a module for kernel 6.6.67 and rtl8189es. Put this module in /lib/modules/6.6.41-current-rockchip/kernel/drivers/net/wireless directory, then run sudo depmod -a and reboot.

    If everything went ok, you should get 8189es driver loaded after boot; perhaps you may need a firmware to put somewhere in /lib/firmware. In case, the driver should complain about in dmesg that something is missing or wrong, and that may serve as hint to proceed further.

     

     

    8189es.ko.gz

  4. @Obmor I see several issues within dmesg, but nothing about the wifi chip.

    First, you should remove rk322x-wlan-alt-wiring from the overlays, which seems not suitable for your board.

     

    With the current configuration of overlays, the SDIO chip (ie: the wifi chip) on mmc1 is detected, but no drivers are loaded as long as I see; are you sure you have an ssv6051?

    If you run rk322x-config, you should have a line Wifi device: .... Device ID: .... if your board really has a ssv6051, you should get 3030:3030 as device ID

  5. 9 hours ago, Obmor said:

    I checked, this module is not loaded in Armbian does it make sense in modprobe ssv6051?

    Hello! No, it has no sense to modprobe the module because the kernel should autodetect the chip and load the module automatically.

    The module is not loaded automatically because the chip is turned off and the kernel could not autodetect it.

     

    Try to put this file: rk322x-led-conf9.dtbo
    in /boot/dtb/overlay directory, then append led-conf9 to overlays line in /boot/armbianEnv.txt and see from dmesg if your wifi device gets detected.

    Send the dmesg log anyway, it is the first step to understand what is wrong.

     

     

  6. @zzc @galenzhao @Obmor tvboxes have a huge amount of wireless chip on board and supporting all of them is very difficult and time consuming taks which I can't afford anymore; the APxxxx series is usually supported because they are basically broadcom chips and the driver is there, but their functionality also depends upon the board wiring, the firmware, the nvram, etc... as you see there are several pieces in the puzzle and it is not easy to fit them without some effort.

     

    The best advice I could give you if you need basic wireless connectivity, is to buy a mediatek-based (mt7601) USB dongle; the next best advice is to buy SBCs with standard or premium support (not CSC) by armbian

  7. @haven just had the chance to check with Debian Bookworm with no DE at all, bare terminal.

    In my case, on my IIyama monitor, I have no issues at all with HDMI sound. It works on kernel 6.6.60 (latest 6.6 release so far), double checked on older 5.19 kernel and it works the same way.

     

    Perhaps the issue is more software related with pulseaudio/xfce rather than related to bare hardware?

     

    As a side note, I only have a very loud default volume, since there is no volume control and so I get 100% volume.

    Turning down volume configuring alsa with "softvol" plugin (following this) fixes the loud volume and HDMI audio works fine in bare terminal for me.

  8. On 11/12/2024 at 1:26 AM, remlei said:

    I wish this was the case but as soon as armbian is installed on emmc, any image in the community repo from github do not boot the SD card first, for it to boot to sd card, I need to short that maskrom to ground.

    It could be that it is not working anymore since I upgraded to 2024.04 u-boot and had to practically rebuild the configuration from scratch.

    This is indeed not intended and has to be considered as a regression.

  9. 8 hours ago, Ioan Bogdan Veringioiu said:

    Do you know something about the patch above ?

    I vaguely remember that it was inherited from somewhere when I merged rockchip 32 bit families (there was a separate family for rk322x).

    It is actually an adaptation from a kernel submitted patch from a rockchip person: https://patchwork.kernel.org/project/linux-rockchip/patch/1569553244-3165-2-git-send-email-zhangqing@rock-chips.com/, but it actually never went into the mainline kernel.

  10. 14 hours ago, Ioan Bogdan Veringioiu said:
    [   17.456578] rockchip_rk3066_pll_set_rate: Invalid rate : 32690000 for pll clk pll_npll

    Weird that 800x480@65Hz works despite the invalid rate warning, and 800x480@66Hz does not produce any warning but does not work at all.

    By the way, the only "major" difference is the negative VSync for the native 800x480 mode.

     

    You may want to compare those modelines against the kernel 4.4 to look for differences.

    Perhaps there are some "restrictions" in the modeline on armbian kernel 6.6 that force the display with a vertical refresh rate (65.7 Hz) that is not supported by the display.

     

    Did you try also to force display vertical refresh rate to 60Hz and 66Hz via kernel command line?

     

  11. 15 hours ago, remlei said:

    this is expected specially for eMMC models unfortunately.

    No, this is not expected at all. Unless there is a problem that may freeze the board at boot (like the optee issue that is coming up recently), when armbian is installed, boot priority is given to sdcard, then eMMC.

     

      @Mr-TNT I guess you did not follow the instructions to first erase eMMC and test armbian on sdcard and later install into eMMC.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines