jock Posted January 24, 2022 Author Posted January 24, 2022 2 hours ago, MarcoFdN said: I found the issue with rk3318-config! My wifi device dev path is /sys/bus/sdio/devices/mmc4:0001:1 instead of mmc1 or mmc3. After modifying the rk3318-config script, it now detects my WiFi card and configure Bluetooth! (maybe another lookup path should be added in rk3318-config?) Yes, you're right! rk3318-config should check for mmc4 and not mmc3, I will fix in the next release. Thanks for spotting this! The error messages are from brcmfmac driver are expected and a bit misleading: it tries to load those firmware files, can't find them and goes further, but then it leave you with no success message, so the user thinks that some firmware is missing, but it is not. It was confusing for me as well. Everything seems in the right place to me, both wifi and bluetooth, and everything should work right fine, but looking better I missed to copy a patch from 5.10 tree into 5.15: https://github.com/paolosabatino/armbian-build/blob/rk3318/patch/kernel/archive/rockchip64-5.10/general-workaround-broadcom-bt-serdev.patch this issue was one of the most bastard things ever, and it still keeps biting the ass I'll fix this other thing and rebuild kernel soon! 0 Quote
jock Posted January 24, 2022 Author Posted January 24, 2022 @lucky62 unfortunately the openvfd driver does not comply at all with the standard linux led framework, so you can't use the triggers like what you would do straight away as like as other leds. Openvfd driver forces the need for the userspace process to control the leds. You may also want to write your own userspace code to control the leds the way you like, but triggers are provided by linux kernel and what you can do is just "simulate" the same behaviour in userspace. In practice, the openvfd driver needs quite a bit of refactoring to be more standard compliant. 0 Quote
lucky62 Posted January 24, 2022 Posted January 24, 2022 15 minutes ago, paradigman said: Hello, could you share a few details on how you were able to display the clock? I don't know what was the problem... Currently I have installed latest kernel 5.15.16. You must have the kernel headers of the running kernel installed. Also you must have the correct configuration file vfd.conf. Steps how the driver was build and installed: # download the sources: https://github.com/arthur-liberman/linux_openvfd # change the directory cd linux_openvfd/driver # edit the Makefile # change the line KERNELDIR = ../../../ # to this: KERNELDIR = /lib/modules/$(shell uname -r)/build # create a symlink to correct System.map in this KERNELDIR - in my case: # /lib/modules/5.15.16-rockchip64/build/System.map -> /boot/System.map-5.15.16-rockchip64 # compile the driver: make -j4 # install module make modules_install # try to load module modprobe openvfd Thats all. 0 Quote
lucky62 Posted January 24, 2022 Posted January 24, 2022 posted twice by mistake.. this second post removed. 0 Quote
paradigman Posted January 24, 2022 Posted January 24, 2022 1 hour ago, lucky62 said: .. # install module make modules_install # try to load module modprobe openvfd Thats all. Thanks for your description, imerging with Jock's previous description like this and now I've been able to compile the driver so that it loads correctly. I do not use the config file because the jock dts overlay in principle contains the configurations required for FD6551. Ok, how to proceed after the module loads? What will show the current time on the display? 0 Quote
MarcoFdN Posted January 24, 2022 Posted January 24, 2022 @jock Thanks! I will try it as soon as you have a new kernel to test! 0 Quote
lucky62 Posted January 25, 2022 Posted January 25, 2022 10 hours ago, paradigman said: Ok, how to proceed after the module loads? What will show the current time on the display? you need to compile and run the OpenVFDService. It can be started in various ways but I copied compiled binary file into /sbin (/usr/sbin link). And the following service file into /lib/systemd/system (grabbed somewhere from web and modified). then I can use: systemctl enable openvfd systemctl disable openvfd systemctl start openvfd systemctl stop openvfd openvfd.service 0 Quote
jock Posted January 25, 2022 Author Posted January 25, 2022 @MarcoFdN I updated the debian bullseye image and the upgrade packages to include the fix for bluetooth and rk3318-config script. 1 Quote
MarcoFdN Posted January 25, 2022 Posted January 25, 2022 @jock 1,000 thanks! rk3318-config script and bluetooth are working now! 0 Quote
paradigman Posted January 25, 2022 Posted January 25, 2022 @lucky62: thanks for your descriptons. Unfortunately for me, not a single digit is still lit, even though I did everything as described. I can't run the OpenVFDService compile, so I used Jock's pre-compiled version. My configuration is in dts. don't know if it's important, but here's a relevant detail about dmesg's output. Please look at it, does it look good? Spoiler OpenVFD: Version: V1.4.0 OpenVFD: vfd_gpio_clk: Empty. OpenVFD: vfd_gpio_dat: Empty. OpenVFD: vfd_gpio_stb: Empty. OpenVFD: vfd_gpio0: #0 = 0x00; #1 = 0x00; #2 = 0xFF; OpenVFD: vfd_gpio1: #0 = 0x00; #1 = 0x00; #2 = 0xFF; OpenVFD: vfd_gpio2: #0 = 0x00; #1 = 0x00; #2 = 0xFF; OpenVFD: vfd_gpio3: #0 = 0x00; #1 = 0x00; #2 = 0xFF; OpenVFD: vfd_gpio_protocol: #0 = 0x00; #1 = 0x00; OpenVFD: vfd_chars: Empty. OpenVFD: vfd_dot_bits: Empty. OpenVFD: vfd_display_type: Empty. OpenVFD: Detected gpio chips: gpio0, gpio1, gpio2, gpio3, ff100000.syscon:gpio. OpenVFD: Failed to verify VFD configuration file, attempt using device tree as fallback. OpenVFD: openvfd_gpio_clk: pin = 68, flags = 0x10 OpenVFD: openvfd_gpio_dat: pin = 69, flags = 0x10 OpenVFD: openvfd_gpio_stb: pin = 64, flags = 0xFF OpenVFD: openvfd_gpio0 pin entry not found OpenVFD: openvfd_gpio1 pin entry not found OpenVFD: openvfd_gpio2 pin entry not found OpenVFD: openvfd_gpio3 pin entry not found OpenVFD: chars_prop = 00000000347bd94e OpenVFD: chars_prop->length = 5 OpenVFD: char #0: 0 OpenVFD: char #1: 1 OpenVFD: char #2: 2 OpenVFD: char #3: 3 OpenVFD: char #4: 4 OpenVFD: dot_bits_prop = 00000000e9600422 OpenVFD: dot_bits_prop->length = 7 OpenVFD: dot_bit #0: 0 OpenVFD: dot_bit #1: 1 OpenVFD: dot_bit #2: 2 OpenVFD: dot_bit #3: 3 OpenVFD: dot_bit #4: 4 OpenVFD: dot_bit #5: 5 OpenVFD: dot_bit #6: 6 OpenVFD: display.type = 0, display.controller = 6, pdata->dev->dtb_active.display.flags = 0x00 OpenVFD: Select FD6551 controller OpenVFD: SW I2C interface intialized (address = 0x0000 (N/A), MSB mode, pull-ups on) brightness = 0 0 Quote
lucky62 Posted January 26, 2022 Posted January 26, 2022 @paradigmanbelow are messages from my box. Looks very similar but I have a different controller. I cannot help more... From your messages - maybe this is the problem: Quote OpenVFD: SW I2C interface intialized (address = 0x0000 (N/A), MSB mode, pull-ups on) # dmesg | grep -i openvfd [ 351.437611] openvfd: loading out-of-tree module taints kernel. [ 351.438416] openvfd: module verification failed: signature and/or required key missing - tainting kernel [ 351.440096] OpenVFD: Version: V1.4.0 [ 351.440121] OpenVFD: vfd_gpio_clk: Empty. [ 351.440127] OpenVFD: vfd_gpio_dat: Empty. [ 351.440132] OpenVFD: vfd_gpio_stb: Empty. [ 351.440144] OpenVFD: vfd_gpio0: #0 = 0x00; #1 = 0x00; #2 = 0xFF; [ 351.440152] OpenVFD: vfd_gpio1: #0 = 0x00; #1 = 0x00; #2 = 0xFF; [ 351.440162] OpenVFD: vfd_gpio2: #0 = 0x00; #1 = 0x00; #2 = 0xFF; [ 351.440171] OpenVFD: vfd_gpio3: #0 = 0x00; #1 = 0x00; #2 = 0xFF; [ 351.440180] OpenVFD: vfd_gpio_protocol: #0 = 0x00; #1 = 0x00; [ 351.440188] OpenVFD: vfd_chars: Empty. [ 351.440193] OpenVFD: vfd_dot_bits: Empty. [ 351.440200] OpenVFD: vfd_display_type: Empty. [ 351.440216] OpenVFD: Detected gpio chips: gpio0, gpio1, gpio2, gpio3, ff100000.syscon:gpio. [ 351.440222] OpenVFD: Failed to verify VFD configuration file, attempt using device tree as fallback. [ 351.441087] OpenVFD: openvfd_gpio_clk: pin = 83, flags = 0x00 [ 351.441111] OpenVFD: openvfd_gpio_dat: pin = 86, flags = 0x00 [ 351.441138] OpenVFD: openvfd_gpio_stb: pin = 82, flags = 0x00 [ 351.441150] OpenVFD: openvfd_gpio0 pin entry not found [ 351.441156] OpenVFD: openvfd_gpio1 pin entry not found [ 351.441162] OpenVFD: openvfd_gpio2 pin entry not found [ 351.441171] OpenVFD: openvfd_gpio3 pin entry not found [ 351.441176] OpenVFD: chars_prop = 00000000c43836d4 [ 351.441185] OpenVFD: chars_prop->length = 5 [ 351.441189] OpenVFD: char #0: 4 [ 351.441195] OpenVFD: char #1: 0 [ 351.441202] OpenVFD: char #2: 1 [ 351.441208] OpenVFD: char #3: 2 [ 351.441213] OpenVFD: char #4: 3 [ 351.441222] OpenVFD: dot_bits_prop = 000000001c63f005 [ 351.441227] OpenVFD: dot_bits_prop->length = 7 [ 351.441233] OpenVFD: dot_bit #0: 0 [ 351.441240] OpenVFD: dot_bit #1: 1 [ 351.441246] OpenVFD: dot_bit #2: 2 [ 351.441251] OpenVFD: dot_bit #3: 3 [ 351.441258] OpenVFD: dot_bit #4: 4 [ 351.441262] OpenVFD: dot_bit #5: 5 [ 351.441269] OpenVFD: dot_bit #6: 6 [ 351.441277] OpenVFD: display.type = 3, display.controller = 0, pdata->dev->dtb_active.display.flags = 0x00 [ 351.442023] OpenVFD: Select FD628 controller [ 351.442217] OpenVFD: SW SPI 3-wire interface intialized (LSB mode) 1 Quote
jock Posted January 26, 2022 Author Posted January 26, 2022 9 hours ago, paradigman said: @lucky62: thanks for your descriptons. Unfortunately for me, not a single digit is still lit, even though I did everything as described. I can't run the OpenVFDService compile, so I used Jock's pre-compiled version. My configuration is in dts. don't know if it's important, but here's a relevant detail about dmesg's output. Please look at it, does it look good? Reveal hidden contents OpenVFD: Version: V1.4.0 OpenVFD: vfd_gpio_clk: Empty. OpenVFD: vfd_gpio_dat: Empty. OpenVFD: vfd_gpio_stb: Empty. OpenVFD: vfd_gpio0: #0 = 0x00; #1 = 0x00; #2 = 0xFF; OpenVFD: vfd_gpio1: #0 = 0x00; #1 = 0x00; #2 = 0xFF; OpenVFD: vfd_gpio2: #0 = 0x00; #1 = 0x00; #2 = 0xFF; OpenVFD: vfd_gpio3: #0 = 0x00; #1 = 0x00; #2 = 0xFF; OpenVFD: vfd_gpio_protocol: #0 = 0x00; #1 = 0x00; OpenVFD: vfd_chars: Empty. OpenVFD: vfd_dot_bits: Empty. OpenVFD: vfd_display_type: Empty. OpenVFD: Detected gpio chips: gpio0, gpio1, gpio2, gpio3, ff100000.syscon:gpio. OpenVFD: Failed to verify VFD configuration file, attempt using device tree as fallback. OpenVFD: openvfd_gpio_clk: pin = 68, flags = 0x10 OpenVFD: openvfd_gpio_dat: pin = 69, flags = 0x10 OpenVFD: openvfd_gpio_stb: pin = 64, flags = 0xFF OpenVFD: openvfd_gpio0 pin entry not found OpenVFD: openvfd_gpio1 pin entry not found OpenVFD: openvfd_gpio2 pin entry not found OpenVFD: openvfd_gpio3 pin entry not found OpenVFD: chars_prop = 00000000347bd94e OpenVFD: chars_prop->length = 5 OpenVFD: char #0: 0 OpenVFD: char #1: 1 OpenVFD: char #2: 2 OpenVFD: char #3: 3 OpenVFD: char #4: 4 OpenVFD: dot_bits_prop = 00000000e9600422 OpenVFD: dot_bits_prop->length = 7 OpenVFD: dot_bit #0: 0 OpenVFD: dot_bit #1: 1 OpenVFD: dot_bit #2: 2 OpenVFD: dot_bit #3: 3 OpenVFD: dot_bit #4: 4 OpenVFD: dot_bit #5: 5 OpenVFD: dot_bit #6: 6 OpenVFD: display.type = 0, display.controller = 6, pdata->dev->dtb_active.display.flags = 0x00 OpenVFD: Select FD6551 controller OpenVFD: SW I2C interface intialized (address = 0x0000 (N/A), MSB mode, pull-ups on) brightness = 0 Don't use my driver, it is half-baked and for testing only. Use the original one. 0 Quote
paradigman Posted January 26, 2022 Posted January 26, 2022 44 minutes ago, jock said: Don't use my driver, it is half-baked and for testing only. Use the original one. I understand it's half-finished, but as long as the display is blank, it's suitable for testing. 0 Quote
paradigman Posted January 26, 2022 Posted January 26, 2022 6 hours ago, lucky62 said: @paradigmanbelow are messages from my box. Looks very similar but I have a different controller. I cannot help more... From your messages - maybe this is the problem: OpenVFD: SW I2C interface intialized (address = 0x0000 (N/A), MSB mode, pull-ups on) Thanks for checking the log. In fact, you confirmed my guess that there was a fault around the I2C bus. I find it strange that if I activate I2C-7 or I2C-8 (or even both at the same time) in the armbian-config, no new bus is detected in the system. In this case, if I run: ls -l /dev/i2*, it still shows the same I2C-4 that was previously available due to HDMI. 0 Quote
Zippy Posted January 26, 2022 Posted January 26, 2022 6 minutes ago, paradigman said: Thanks for checking the log. In fact, you confirmed my guess that there was a fault around the I2C bus. I find it strange that if I activate I2C-7 or I2C-8 (or even both at the same time) in the armbian-config, no new bus is detected in the system. In this case, if I run: ls -l /dev/i2*, it still shows the same I2C-4 that was previously available due to HDMI. i have a FD655S controller i was able to compile the driver module and the service i will have some test. where did you put your vfd.conf ? and what in it ? 0 Quote
paradigman Posted January 26, 2022 Posted January 26, 2022 1 minute ago, Zippy said: i have a FD655S controller i was able to compile the driver module and the service i will have some test. where did you put your vfd.conf ? and what in it ? Hi, I'm so glad you're dealing with this. I didn't put the vfd.conf file anywhere because if it was, it ignored every line of it. Instead, I define the configuration in DTS like this: Spoiler /dts-v1/; /plugin/; / { fragment@0 { target-path = "/"; __overlay__ { openvfd { compatible = "open,vfd"; dev_name = "openvfd"; openvfd_gpio_clk = <&gpio2 0x04 0x10>; openvfd_gpio_dat = <&gpio2 0x05 0x10>; openvfd_gpio_stb = <&gpio2 0x00 0xFF>; openvfd_chars = [00 01 02 03 04]; openvfd_dot_bits = [00 01 02 03 04 05 06]; openvfd_display_type = [06 00 00 00]; status = "okay"; }; }; }; }; 0 Quote
Zippy Posted January 26, 2022 Posted January 26, 2022 did not focus on vfd yet since i am using this box as low power server utility in case of power outage, so really not need the led but if i can help by doing some test why not will let you know 1 Quote
vitaliy.burkut Posted January 27, 2022 Posted January 27, 2022 Hi all!I was finally able to extract DTB file from android boot.ing. And I see that configuration for wifi device is absolutistly different. The pice from @jock img for rk3318 (rk3318-box.dtb): sdio-pwrseq { wifi-enable-h { rockchip,pins = <0x01 0x12 0x00 0x6d>; phandle = <0x7d>; }; }; From Android: sdio-pwrseq { wifi-enable-h { rockchip,pins = <0x01 0x12 0x00 0x7e>; phandle = <0x8b>; }; }; And device description use a different method to solving: From android: wireless-wlan { compatible = "wlan-platdata"; rockchip,grf = <0x1c>; wifi_chip_type = "ap6330"; sdio_vref = <0x708>; WIFI,host_wake_irq = <0x71 0x13 0x00>; status = "okay"; }; How I see on https://titanwolf.org/Network/Articles/Article?AID=0f861e3c-2b51-4e69-b924-a1d6a208f2bd compatible = "wlan-platdata" means that will be use power control rfkill-wlan wifi_chip_type = "ap6330"; says what driver should be use But I not understand why node wireless-wlan is described in root (how it linked with sdio bus?) @jock may by you can ask me: if I move wireless-wlan node from android dtb to my own dto and try to run it on your img, will it work?01_dtbdump_rockchip,rk3328-box-avb.dtb 01_dtbdump_rockchip,rk3328-box-avb.dts 0 Quote
vitaliy.burkut Posted January 27, 2022 Posted January 27, 2022 24.01.2022 в 22:10, MarcoFdN сказал: My wifi device dev path is /sys/bus/sdio/devices/mmc4:0001:1 instead of mmc1 or mmc3. @MarcoFdNcan you explain me how you find the path? I looked your dts file. The description of wifi node looks like in my dts, but I can not see relations between wifi node and sdio bus. Thank you in advance 0 Quote
jock Posted January 27, 2022 Author Posted January 27, 2022 @vitaliy.burkut those pinctrl configurations are not different, in fact despite the different numbers, they are right the same thing. I assume you're using mainline kernel, as long as you didn't specify and didn't provide any log. The wireless-wlan node is a proprietary rockchip thing that, thanks God, is not present in mainline kernel and will never be. You don't need it. It is a very bad practice to put such node in that position describing the hardware such way, and copying it into any other dtb won't work. I checked into your dtb and your board is a pretty standard board which does not need any particular dtb tricks. ap6330 should work out of the board, you may want to add rk3318-box-wlan-ap6330 device tree overlay and be sure rk3318-box-ext-wlan overlay is not set in armbianEnv.txt . rk3318-config does by itself though. If your device gets detected and you see wlan0 device but cannot scan APs, probably you should seek a more suitable nvram file for your board. PS: - You should post whatever is described in the first post to get suitable help. - From a previous post, rk3318-config detects an AP6334 and not AP6330. Why you want to force ap6330 is a mistery to me, but if the answer is "the device tree says that", now you understand how shitty and misleading the wireless-wlan node is. 0 Quote
paradigman Posted January 30, 2022 Posted January 30, 2022 @kruzer I think we have a very similar board, yet my LCD screen is still dark. I will list all the relevant sections here, would you see if you see any relevant differences from what you are experiencing? Many thanks. Edit: The problem was solved. There was an authorization problem accessing the service file and I discovered this using the systemctl status openvfd command. 0 Quote
intikallpa Posted February 1, 2022 Posted February 1, 2022 On 11/23/2021 at 2:11 PM, Huafu said: I finally got some time to come back on my X88PRO 10 boards. The first one had wrong RAM and ROM size, the seller sent me a new one which appears (looking at the onboard chips) to have the real RAM/ROM. (first board was 2G RAM/32G ROM, 2nd is 4G ram/64G ROM). Any file attached to this post is related to the second board, but both are called X88PRO 10. I've tried your new image Armbian 21.11 - Debian Bullseye desktop [xfce] - mainline kernel 5.15.2 on my old board (the one with only 2G of RAM), but running rk3318-config and rebooting keeps telling me that it'll switch to another bus. Then I've tried the hirsute image and that one did work after switching to the other bus and rebooting. One thing tho, I can't figure out how to enable/disable overscan. Various options tested (disable_overscan=1 or 0, disp_mode=, ... didn't change anything). In brief, something like 20 pixels are out of the screen on each side. Then I've switched to the new board (the 4G RAM one). Using multitool (even before the first boot without sdcard), I've done a backup and I've extracted the dtb from each partition (not only the first one had some dtb, but also the 4th, 6th and 8th partitions had some). I then used dtc tool to get the dts out of each file which I attached here if it can be useful for anyone. All pictures, dtb, kernels and dts can be found here (as well as the original eMMC image). Now comes the failing part: I was expecting the board to just be the same as the other one (the 2G one) with just augmented RAM and ROM, and once my backup has been created, I've burn to flash the Armbian 21.11 - Debian Bullseye desktop [xfce] - mainline kernel 5.15.2 image directly without testing it . Removed power, sdcard, rebooted, ....and nothing. No signal on HDMI even after 10 minutes (I was hoping it was just the partition resize taking a long time). I've tried to boot again from sdcard but nothing more was happening. I then tried to boot with male/male USB while keeping the pin inside the jack plug, but on both USB ports I had no output in dmesg of my laptop. Tho the red led turns on as well as the light in the coaxial audio plug. At that point I don't know what else I can do, as you can see on the picture without the heatsink, the pins of the eMMC aren't accessible at all so I cannot try the screwdriver trick. Any idea on what I can try/do? Thanks in advance for any help even if it's a "drop it to the bin" message , and lemme know if you want me to send anything else from those boards. p1-01_dtbdump_rockchip,rk3328-evb.dts p1-02_dtbdump_rockchip,rk3328-evb.dts p1-03_dtbdump_rockchip,rk3328-evb.dts p1-04_dtbdump_rockchip,rk3328-evb.dts p4-01_dtbdump_fragment@0.dts p6-01_dtbdump_rockchip,rk3328-box-liantong-avb.dts p6-02_dtbdump_rockchip,rk3328-box-liantong-avb.dts p6-03_dtbdump_rockchip,rk3328-box-liantong-avb.dts p8-01_dtbdump_rockchip,rk3328-box-liantong-avb.dts p8-02_dtbdump_fragment@0.dts p8-03_dtbdump_rockchip,rk3328-box-liantong-avb.dts p8-04_dtbdump_rockchip,rk3328-box-liantong-avb.dts Update: thanks to @enigmasphinx's post, I looked right under the board where the eMMC is in the other side, and I found not 2 but 3 pins (see 2 new attached pics)! I will try to connect some of them, I hope a wrong combination won't do some more damage Maskrom mode: shortcircuit between points B and C. This works perfect for My X88Pro 10. 1 Quote
paradigman Posted February 6, 2022 Posted February 6, 2022 I have a working openvfd configuration, the box displays the exact time after boot. Now the question is, is it possible to display "boot" during boot, as shown during boot of the factory Android firmware? Do I think this can be set in the openvfd overlay? That would be the goal: 0 Quote
Wester_Minsk Posted February 7, 2022 Posted February 7, 2022 @jock Hi! In the thread about CSC Armbian for RK322X TV Boxes, good news about Multitool with SSH, This Multitool is suitable for rk3318 ?? What version of drrbin is there? 0 Quote
jock Posted February 7, 2022 Author Posted February 7, 2022 7 minutes ago, Wester_Minsk said: @jock Hi! In the thread about CSC Armbian for RK322X TV Boxes, good news about Multitool with SSH, This Multitool is suitable for rk3318 ?? What version of drrbin is there? Not that one, but multitool for rk3318 has been updated as well with the same enhancements. You can download it from the first page of this thread. (I didn't had the chance to test the rk3318 version, but if you feel confident you can try it and report ) 0 Quote
Zippy Posted February 7, 2022 Posted February 7, 2022 22 hours ago, paradigman said: I have a working openvfd configuration, the box displays the exact time after boot. Now the question is, is it possible to display "boot" during boot, as shown during boot of the factory Android firmware? Do I think this can be set in the openvfd overlay? That would be the goal: nice , i still have no luck with mine, but like i said , not that important to me so... can you share your config ? again congrats 0 Quote
Wester_Minsk Posted February 7, 2022 Posted February 7, 2022 12 минут назад, jock сказал: Not that one, but multitool for rk3318 has been updated as well with the same enhancements. You can download it from the first page of this thread. (I didn't had the chance to test the rk3318 version, but if you feel confident you can try it and report ) Multitool over SSH worked great!! It took me 5 minutes to install in emmc. Thank you very much! 1 Quote
paradigman Posted February 7, 2022 Posted February 7, 2022 1 minute ago, Zippy said: nice , i still have no luck with mine, but like i said , not that important to me so... can you share your config ? again congrats Of course. I wrote a little script for it that shortens the process a bit. It is important to know that I am not working as a root user within armbian. The necessary steps: copy openvfd-fd6551.dts to /home/<username> copy install_kernel_debs.sh to /home/<username> copy OpenVFDService file to /usr/sbin, AND set permission to 777 ! copy openvfd.service file to /lib/systemd/system sudo armbian-add-overlay openvfd-fd6551.dts sudo /bin/bash install_kernel_debs.sh After reboot: cd linux_openvfd/driver edit MAKE -> KERNELDIR = /lib/modules/$(shell uname -r)/build sudo make -j4 sudo make modules_install sudo modprobe openvfd sudo usermod -a -G i2c <username> Start the Service: sudo systemctl enable openvfd sudo systemctl start openvfd openvfd-fd6551.dts openvfd.service OpenVFDService install_kernel_debs.sh 2 Quote
markst Posted February 7, 2022 Posted February 7, 2022 I need help with WIFI. I have a few X88 PRO 10 (4GB RAM 64GB ROM RK3318) that I purchased from the same Amazon seller. Unfortunately the seller must source from different suppliers as they are not all the same. Some have a SP6330 WIFI chip and this works fine. But others have a LG642 WIFI chip that is NOT working. The LG642 WIFI chip looks to have the same manufacturer marking on it as the Sp6330 (a sun). When using the rk3318-config (running it 2 times with reboot) I get the following. But WIFI will not connect. Wifi device: Broadcom BCM4334/AmPak AP6334 - Device ID: 02d0:4334 In armbianEnv.txt I have the following: verbosity=1 bootlogo=false overlay_prefix=rockchip fdtfile=rockchip/rk3318-box.dtb rootdev=UUID=xxxxxxxxxxxxxxxxxxxxxxxx rootfstype=ext4 console=both overlays=rk3318-box-wlan-ext rk3318-box-led-conf2 rk3318-box-wlan-ap6330 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u I started with Armbian 22.02 - Ubuntu Jammy (beta) desktop [xfce] - mainline kernel 5.15.17 - 2022-01-29 0 Quote
markst Posted February 7, 2022 Posted February 7, 2022 This is the other WIFI chip. It is working correctly. In rk3318-config it is NOT recognized but is working in nmtui. I can connect successfully to WIFI. "No WIFI chip has been detected" 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.