wpi firmware Intel eula

[plouk]

Hi there,

Does anyone know what to do to accept the eula Intel Licence in order to use the firmware for the wpi driver ?

I've read "man ifconfig, sysctl,sysctl.conf and wpi", the whole directory "/libdata/firmware/if_wpi/*" but I couldn't find any clues !.
It is said that we must agree with the eula from Intel but nothing about how to do it.

first, I tried with "eula=1" and "intel.eula=1" in my "/etc/sysctl.conf"; but It's not working !
Then I also tried "hw.wpi.accept_eula=1" just to mimic what is noticed in the man page related to "ipw", but unfortunately that didn't work, as well !

Any suggestions are welcome...

[BSDfan666]

The wpi(4) driver in NetBSD is based on the same one that's in OpenBSD, written by Damien Bergamini.

In OpenBSD, users must acquire the firmware from Damien's own website in a format installable using the native package management tools, i.e: pkg_add(1).

NetBSD 5.0 appears to distribute the firmware from Intel, unfortunately users must agree to the terms of the Intel EULA prior using it.

Blindly trying sysctl(1) commands isn't very productive, you can see a list of all elements using no arguments at all.. or by using -a, it is however very inconsiderate of them to not include it in the man page, I agree.

The sysctl MIB should be hw.wpi.accept_eula, are you sure it is not?

I myself don't like this EULA stuff either, so feel free to use OpenBSD and avoid this mess.

Good luck, and I hope that helps.

[plouk]

hi BSDfan666,

thank you for your help.

I did put in my "/etc/sysctl.conf" "hw.wpi.accept_eula=1" but It doesn't work.
During the boot process, the system is complaining with
- second level name wpi in hw.wpi.eula_accept=1 is invalid...

So what's next ???

About OpenBSD, I had some troubles with the 4.5 release, either with the acpi(acpitz) either with the network.

- acpi isn't working with 2 cpus(one is ok), the system reboots due to overheat(115°c), actually this value is false but anyway the system reboots.
I had to disable acpitz with "config"; when recompiling the kernel without "smp" or "acpitz" the system was unstable.
I've installed the 4.6 beta for testing purpose and the acpi issue seems to be resolved( I like the new installer, by the way ).

- I have to log in a wireless network at home(I'm not the administrator) where the password is made with the character "&", unexpectedly during the boot process I get "/etc/rc: &XXXX not found..." consequently, the wireless doesn't work. It appears that the system interprets the characters after "&" as a new command; therefore either with "ifconfig" or "/etc/hostname.XX0" I wasn't able to settle the network.

[jggimi]

"Escape" special characters from the shell with backslash. e.g.:

Penn \& Teller

[plouk]

Originally Posted by jggimi

"Escape" special characters from the shell with backslash. e.g.:

Penn \& Teller

I can't program but I though about it.
Have you tried it ?
At the moment this laptop is running netbsd 5.0, so I wouldn't reinstall OpenBSD again if that doesn't work !

[BSDfan666]

Where is your sense of adventure?

Anyway, can you post a dmesg and the output of sysctl as attachments or inline using the [code][/code] blocks?

Perhaps we can find the problem..

[jggimi]

Originally Posted by plouk

Have you tried it ?

Of course, from interactive shells (sh, ksh, tcsh) and within embedded "here documents" within bourne shell scripts.

And while I've never mucked about with escaped characters inside a hostname.<if> file, the file is parsed by /etc/netstart, a bourne shell script.

I wouldn't reinstall OpenBSD again if that doesn't work !

Test it yourself, from any *nix shell, like so:

$ echo Command A in background & echo Command B in foreground
[1] 24715
Command B in foreground
$ Command A in background

[1] + Done		   echo Command A in background
$ echo Penn \& Teller
Penn & Teller
$

No need to install the OS. See my .sig for live media.

[plouk]

Originally Posted by BSDfan666

Where is your sense of adventure?

oh gosh!
It's cheating
ok, I may reinstall OpenBSD tomorrow just to be sure about the escape character !

I'll also see for dmesg..., but later,(I could log in the wireless network with a live CD, puppylinux actually)

thank you guys, I'll be back tomorrow with some news.