12/31/2022 0 Comments Making gx works 2 run on linuxI then started with a fresh venus 2.7 install and copied the kernel image and dtb file into /boot. Then back in bitbake terminal ran bitbake linux-sunxiĪnd it compiled happily (not on my first try, see below for how I prepared the modified kernel tar ball). :).Īfter following your guidance to set up and as suggested I modified the bitbake recipe, just the SRC_URI line SRC_URI = "file:///path/to/custom/tarball/v$.tar.gz" Could also be that you're already close going your route and as usual there are tons of different ways to achieve the same. The manual for what you're then working in is here. venus/sources/meta-victronenergy/meta-bsp/recipes-kernel/linux/ linux-sunxi_4.19.123-sunxi5.bb, to have your repo on disk as the src-uri, rather than the repo online. The best I can think of is to clone our linux repo (which you've already done), make the change you need and thereafter change the kernel recipe in. Once that first build is succeeded, next you need to figure out how to change that config file. The OE (=OpenEmbedded) way is to build everything from source, including cross compilers and so forth. Now in that shell, you need to run: bitbake linux-sunxiĪt least, thats what I think you should run :). But that should't matter anyway and lets keep it as simple as possible first time around Now you're in a new shell, ready to build the kernel according to v2.70~5, ie not venus os large, and thus not version 5.10. Now, I don't know if it works, I'm just pasting here what I'd try first if I were you: Hey, if I was doing what you are, I would try and build the kernel the exact same way we do, but then with that flag enabled. I wonder if multiple might be enabled, but this seems unlikely and there is no mention of the others in the boot log on the original 2.66. I might try the other network drivers but doubt that these are the issue here since the 8723bu is running in the original installation. I haven't enabled the video driver but doubt this is a concern here. Managed to unblock but not sure why it is raised in the first place. Need to understand rfkill as that was raised as blocking the device when activating using connmanctl. Maybe I should revisit this now that the driver is installed. I was able to power on the wifi but tethering didn't work. I had tried with connmanctl before I found the missing wifi driver. Is this just failing because of some dhcp issue? Why is this failing on my system? I read something about the access point configuration using dnsmasq and hostapd (after abandoning connmanctl) so might have to dig into the dnsmasq configuration to understand what is going on. Where is the ap0 configuration, ssid, password coming from? I found hostapd-run that seems to set up the access point, but it depends on ap0 already being configured. Where are the wifi drivers and video driver coming from in the image install? I wonder if I need to compile the 8723bu driver in the context of the bridge module somehow. I will have to try to get some logs to see why the connection is failing. So I went onto vrm online and set the password (ethernet connection to internet is still up), but I still can't connect to the wireless access point. Now ap0 is up and I can see the wifi, but the ssid has changed. rtl8723bu 5-1.1:1.2 disabled-wlan0: renamed from wlan0 usbcore: registered new interface driver rtl8723bu 8723bu: loading out-of-tree module taints kernel. So I enabled this one and rebooted depmod Rtl8723bu 5-1.1:1.2 disabled-wlan0: renamed from wlan0So I copied these over, and looking at the boot log of the original 4.19.123 i noticed that 8723bu.ko is being used rtl8723bu 5-1.1:1.2 ap0: renamed from wlan1 On a diff of find in these directories we now have the bridge module as expected but are missing a few wifi drivers and a video driver. I also replaced the modules folder /lib/modules/4.19.123 with the newly built folder. I then copied over the kernel into /boot (renamed 4.19.123.custom) and replaced the kernel symlink in /boot to link to the modified kernel. I moved over to venus OS 2.66 to work this out and recompiled 4.19.123 as above, although this time I needed to install more gcc compilation stuff sudo apt-get install gcc-arm*
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |