11-01-2023, 09:05 AM
Hey all! First post here.
I'll keep it quick, but before I start I want to say that I have a workaround and I'm OK with it, although I'd like to have a "cleaner" solution in place if possible.
Long and short of it: Just received my Pinebook Pro a few days ago with Manjaro ARM. All was well until I found out that the version Manjaro I had didn't support external monitors at all, due to patch not being in mainline. Tried different monitors, different cables, rotating cables, etc. No dice.
So I switched to a custom kernel to fix that problem, however that knocked out my WiFi. OS wouldn't even acknowledge that hardware was there. I thought it may have been hardware failure until I starting finding errors about loading Broadcom firmware in dmesg.
I tried the usual suspects such as ensuring /boot was properly mounted, cold booting, privacy switch, etc. Nothing. Reverting back to the original kernel made no difference either.
After many hours of trial & error and searching for answers, I found a set of firmware files which worked when placed in the proper location, but it wasn't "plug-and-play" so to speak. Every time now when I want to use WiFi after booting, I have to use that "(un)bind" trick:
I never touched the Broadcom firmware files before my kernel update and later before my reversion. Thought maybe something was compiled into the stock kernel to enable WiFi, so I can't explain why WiFi still didn't work when I reverted. So I could be missing something there.
I can have that command line above automatically run on boot, no problem.
Wanted to share my experience, help others out if they run into this, and also ask if there is anything I can do to not have to run that command on every boot.
I'm in a Good Place now, and still enjoying PBPro. Look forward to testing as my daily driver!
I'll keep it quick, but before I start I want to say that I have a workaround and I'm OK with it, although I'd like to have a "cleaner" solution in place if possible.
Long and short of it: Just received my Pinebook Pro a few days ago with Manjaro ARM. All was well until I found out that the version Manjaro I had didn't support external monitors at all, due to patch not being in mainline. Tried different monitors, different cables, rotating cables, etc. No dice.
So I switched to a custom kernel to fix that problem, however that knocked out my WiFi. OS wouldn't even acknowledge that hardware was there. I thought it may have been hardware failure until I starting finding errors about loading Broadcom firmware in dmesg.
I tried the usual suspects such as ensuring /boot was properly mounted, cold booting, privacy switch, etc. Nothing. Reverting back to the original kernel made no difference either.
After many hours of trial & error and searching for answers, I found a set of firmware files which worked when placed in the proper location, but it wasn't "plug-and-play" so to speak. Every time now when I want to use WiFi after booting, I have to use that "(un)bind" trick:
Code:
sudo tee /sys/bus/platform/drivers/dwmmc_rockchip/{un,}bind <<< 'fe310000.mmc'I never touched the Broadcom firmware files before my kernel update and later before my reversion. Thought maybe something was compiled into the stock kernel to enable WiFi, so I can't explain why WiFi still didn't work when I reverted. So I could be missing something there.
I can have that command line above automatically run on boot, no problem.
Wanted to share my experience, help others out if they run into this, and also ask if there is anything I can do to not have to run that command on every boot.
I'm in a Good Place now, and still enjoying PBPro. Look forward to testing as my daily driver!
