Intel wifi ipw showing up but not working
Hello I just installed OpenBSD 6.8 on a Toshiba Tecra S1. It is a fresh install, so i can't say if it worked on previous OpenBSD versions (I have seen something in the mailing list about that). the BIOS has no special options regarding the wireless card. The laptop has this network card: ipw0 at pci2 dev 4 function 0 "Intel PRO/Wireless 2100" rev 0x04: irq 11, address 00:0c:f1:1f:b2:a0 I installed the firmware with fw_update. I try to bring the interface up, I can set the nwid, but it never connects. I set the WEP password and it does not get saved if I check back with ifconfig. If I try to scan, nothing is shown, I get no errors on the console/dmesg. Also I notice the LED does never blink, there is no activity on the card I tried enabling debug and I see: ifconfig debug ipw0 list ifconfig: SIOCDIFADDR: Device not configured what am I missing? some magic sysctl? Thank you, Riccardo
Re: Intel wifi ipw showing up but not working
On 2021-02-12, Riccardo Mottola wrote: > The laptop has this network card: > > ipw0 at pci2 dev 4 function 0 "Intel PRO/Wireless 2100" rev 0x04: irq > 11, address 00:0c:f1:1f:b2:a0 Please send full dmesg, not an excerpt. > I installed the firmware with fw_update. I try to bring the interface > up, I can set the nwid, but it never connects. What do you type to bring the interface up? If you are using /etc/hostname.ipw0 and "sh /etc/netstart ipw0", what are the contents of the file? > I set the WEP password and it does not get saved if I check back with > ifconfig. WEP password definitely won't get displayed back if you check as non-root. I don't recall if it is displayed for root or not. What does "ifconfig ipw0" say? Is there an "RF kill" (wifi on/off) switch on the laptop, if so did you try toggling it? > If I try to scan, nothing is shown, I get no errors on the console/dmesg. > > Also I notice the LED does never blink, there is no activity on the card > > > I tried enabling debug and I see: > > ifconfig debug ipw0 list > ifconfig: SIOCDIFADDR: Device not configured Syntax for that is "ifconfig ipw0 debug", if you get any messages they'll appear in dmesg and/or /var/log/messages (preemptive: please reply on-list not to me personally).
Re: Intel wifi ipw showing up but not working
Riccardo, Have you created the file in /etc/hostname.interface ? in your case it would be /etc/hostname.ipw0 if your interface is ipw0 and the WEP Key or WPA KEY should be added, also remember to add dhcp. After you created the file with the content I added below, you should be able to execute netstart as root with: # sh /etc/netstart -- example of hostname file -- join "Network-WIFI" wpakey password dhcp -- end of example -- On Fri, Feb 12, 2021 at 10:10:32PM +0100, Riccardo Mottola wrote: > Hello > > > I just installed OpenBSD 6.8 on a Toshiba Tecra S1. It is a fresh install, > so i can't say if it worked on previous OpenBSD versions (I have seen > something in the mailing list about that). the BIOS has no special options > regarding the wireless card. > > The laptop has this network card: > > ipw0 at pci2 dev 4 function 0 "Intel PRO/Wireless 2100" rev 0x04: irq 11, > address 00:0c:f1:1f:b2:a0 > > I installed the firmware with fw_update. I try to bring the interface up, I > can set the nwid, but it never connects. > > I set the WEP password and it does not get saved if I check back with > ifconfig. > > If I try to scan, nothing is shown, I get no errors on the console/dmesg. > > Also I notice the LED does never blink, there is no activity on the card > > > I tried enabling debug and I see: > > ifconfig debug ipw0 list > ifconfig: SIOCDIFADDR: Device not configured > > > what am I missing? some magic sysctl? > > > Thank you, > > Riccardo > -- Jose Figueroa
Re: pkg_add and an authenticating proxy
that is what I get for not keeping up to date. I have been using FETCH_CMD for a number of years to get through authenticating proxy, never bothered to see if support was added to fetch.c On Thu, Feb 11, 2021 at 3:18 PM Stuart Henderson wrote: > > On 2021-02-11, Stephan Mending wrote: > > I'm a dork. I actually tried that but forgot to set "keepenv" in doas.conf. > > :| > > This is fairly recent, jca fixed ftp to do http over an authenticated proxy > last year >
Re: amdgpu unstable atm
On Wed, Feb 10, 2021 at 06:46:55PM +0900, rgc wrote: > > sysupgraded this morning > logged in xenodm, running stterm, tmux, spyder3, firefox-esr > left it as-is ... went to work. > checked it later in the day, saw the console login prompt, pressing a key > shutdown the system. hmmn. this is probably a user error because i had the same thing happen today thinking i had the machine suspended (via zzz) i pressed the power button and the machine powered off. but i can't remember if i pressed the power button on that day. kern.version=OpenBSD 6.9-beta (GENERIC.MP) #323: Tue Feb 9 10:19:03 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP kern.version=OpenBSD 6.9-beta (GENERIC.MP) #328: Wed Feb 10 18:08:26 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP #323 was used over the weekend (2 days) no issues #328 is running now. playing with vowpal_wabbit (a one-off compile) ~ rgc
Re: .forward file with 6.8 and smtpd -- should that still work?
On Fri, 22 Jan 2021, Gabriel Garcia wrote: > > Used to be able to put .forward files in the home > > directory of certain users and re-send their mail to a gmail or other > > address. > > > > Doesn't seem to work now. Is that feature available somehow with smtpd? > > This should still work, I believe it's related to local mail delivery, rather > than smtpd itself. > > Perhaps you should share the relevant configuration, the .forward file you > wish processed and the use case that isn't working for folks to assist. Hi Gabriel, thanks for the encouragement. Thought I answered you but don't see it in the archive. Just for the record, I wanted to confirm what apparently fixed the problem for me... seems it was a name server problem. >From my postponed messages folder later on 22 Jan 2021: Simple .forward is working fine, and automatically, for me now. Might have had something to do with a new MX record propagation delay. Austin
