Arend van Spriel <arend@...> writes:
>
> On 03/14/15 23:13, Ochal Christophe wrote:
> > All,
> >
> > On 03/14/2015 09:39 PM, Stefan Lippers-Hollmann wrote:
> >> You don't need to run windows for that, the nvram (calibration data,
> >> probably the MAC address and related device specific data) is stored
> >> in your mainboard's firmware - and exposed to userspace (under linux)
> >> via /sys/firmware/efi/efivars/. You just need to identify the correct
> >> file and copy it to a place where linux expects to find it
> >> (/lib/firmware/brcm/brcmfmac43340-sdio.txt). Regards Stefan
> >> Lippers-Hollmann
> >
> > Thanks for the hint, that did it, I'm online!
>
> Apparently my hint was not clear enough. Good to hear it works for you.
>
Dear Arend,
would be nice, if you could make it clear.
I am in the exact some position (asus x205 with linux 4.0 rc3) but my
/sys/firmware/efi/efivars/ is empty. I am running debian jessie with a
kernel taken from ubuntu. Am I missing something? Even loading efivars via
modprobe doesnt change a thing.
Juergen
On 03/15/15 21:38, J?rgen Bausa wrote:
> Arend van Spriel<arend@...> writes:
>
>>
>> On 03/14/15 23:13, Ochal Christophe wrote:
>>> All,
>>>
>>> On 03/14/2015 09:39 PM, Stefan Lippers-Hollmann wrote:
>>>> You don't need to run windows for that, the nvram (calibration data,
>>>> probably the MAC address and related device specific data) is stored
>>>> in your mainboard's firmware - and exposed to userspace (under linux)
>>>> via /sys/firmware/efi/efivars/. You just need to identify the correct
>>>> file and copy it to a place where linux expects to find it
>>>> (/lib/firmware/brcm/brcmfmac43340-sdio.txt). Regards Stefan
>>>> Lippers-Hollmann
>>>
>>> Thanks for the hint, that did it, I'm online!
>>
>> Apparently my hint was not clear enough. Good to hear it works for you.
>>
>
> Dear Arend,
>
> would be nice, if you could make it clear.
>
> I am in the exact some position (asus x205 with linux 4.0 rc3) but my
> /sys/firmware/efi/efivars/ is empty. I am running debian jessie with a
> kernel taken from ubuntu. Am I missing something? Even loading efivars via
> modprobe doesnt change a thing.
Maybe you need to mount it. This is what I found [1]:
$ sudo mount -t efivarfs none /sys/firmware/efi/efivars
Regards,
Arend
[1] http://firmware.intel.com/blog/accessing-uefi-variables-linux
> Juergen
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi
On 2015-03-15, Jürgen Bausa wrote:
> Arend van Spriel <arend@...> writes:
> > On 03/14/15 23:13, Ochal Christophe wrote:
[...]
> would be nice, if you could make it clear.
>
> I am in the exact some position (asus x205 with linux 4.0 rc3) but my
> /sys/firmware/efi/efivars/ is empty. I am running debian jessie with a
> kernel taken from ubuntu. Am I missing something? Even loading efivars via
> modprobe doesnt change a thing.
You need to have efivarfs mounted, which Debian/jessie and systemd
should do by default (it certainly does, at least when booted in UEFI
mode - you probably won't have access to it in BIOS CSM mode):
$ grep efivarfs /proc/mounts
efivarfs /sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0
If it isn't for some weird reason, you'll have to mount it by hand.
# mount -t efivarfs -o rw,nosuid,nodev,noexec,relatime efivarfs /sys/firmware/efi/efivars
Regards
Stefan Lippers-Hollmann