I think, I'll give regular FW 1.76 a try, but I don't think this should make a difference, right?
Advertising
When I try this, bash logs out or terminal crashes. Using with sudo returns an ERROR: file exists.OsirisX wrote:You can also try running insmod command directly after Fedora has booted without the sdhci.modules script.
I don't think it matters but haven't tested with recovery fw.wsxps wrote:Yes, that works. I'm loading the payload via wifi. Maybe it makes a difference that I'm currently on 1.76 recovery FW?
I think, I'll give regular FW 1.76 a try, but I don't think this should make a difference, right?
Module has probably loaded but wifi firmware most likely failed. Can you post your dmesg log for mmc?wsxps wrote:When I try this, bash logs out or terminal crashes. Using with sudo returns an ERROR: file exists. I assume, that loading this module is not the main problem...
Code: Select all
sudo dmesg | grep mmc
Thanks for posting your output. Seems you have the same issue as D-ecks. Network device is found but doesn't respond to any commands. I'll try investigating more and see if I can resolve this issue.wsxps wrote: Looks like it finds the device, but cannot load the driver correctly, right? ip addr still doen't show mmc0. I'm now booting from regular FW 1.76.
Working or device available only? That is a good question.VitaGenic wrote:audio output working.
To quote the original post:D-ecks wrote:Working or device available only? That is a good question.VitaGenic wrote:audio output working.
I'm interested in this thing too.