Closed alistair23 closed 3 years ago
@larsim @schultzern @steinarbakkemo
@alistair23 hello and thanks for the interest in the reMarkable kernel. Are you rebuilding the modules and installing them as well when you are testing?
make modules_install INSTALL_MOD_PATH=<desired_path>
Thanks for getting back to me.
I just realised that in the above log the brcmfmac
driver doesn't appear to even load, so good point. I just assumed that the modules would be loaded from the rootFS (I'm using the default rM2 rootFS).
I haven't actually spent much time getting the 4.14. kernel working. Most of my effort has been spent trying to get WiFi working with the 5.4 kernel and the 5.11. In that case I do see lots of brcmfmac
logs and the device appears to start (it goes in and out of sleep) but I never get a wlan0
device. I guess that isn't up to you to help debug though (unless you want to :P )
I managed to get WiFi working the with 5.4 kernel. It seems like the firmware version the kernel expects has changed, combined with some timing issues. All working now though. Thanks for the help.
I am experience same issue wifi wlan0 interface doesn't appear in ifconfig . if you can share more detail , how you fix.
If I build the zero-sugar kernel d4e7e07a390f8b2544ca09d69142d18114149004 using the
zero-sugar.dts
device tree andzero-sugar_defconfig
config I can successfully boot my own kernel on the rM2. However the WiFi doesn't work.I have attached the kernel log below.
I have a single change in the device tree to get UART on the pogo pins, which causes OTG errors in the log below. I can use the same device tree with the pre-built kernel on the rM2 to get UART and the WiFi still works. So I know it isn't my DTS change.
Is there any chance you haven't pushed some WiFi patches to this repo?
I'm using the same config (checked against the pre-built kernel) and using the same rootFS so the same binary blobs are supplied. The only differences I can think of is the actual kernel source or the version of GCC being used.