DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD General

OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 3rd June 2008
leonardz leonardz is offline
New User
 
Join Date: Jun 2008
Posts: 1
Thanked 0 Times in 0 Posts
Default iwi not loaded by OS

I have an AMD64 laptop with an Intel PRO/Wireless 2200BG wireless card. It works under linux but I cannot get it to work under OpenBSD (using -current).

Config sees the device driver but dmesg.boot shows it cannot load the driver (see below). So there are is no iwi0 device. What do I need to do to have OpenBSD see the device.

As an asside: I could not get iwi-firmware-3.0.tgz to load as aq package (it complained that it only will load on 1386. So I untarred it into /etc/firmware and rebooted..

grep iwi dmesg.boot
iwi0 at pci0 dev 5 function 0 "Intel PRO/Wireless 2200BG" rev 0x05: could not map memory space
root@genetraveller run 503>>config -e /bsd
OpenBSD 4.3-current (GENERIC) #1448: Sat May 31 12:18:34 MDT 2008
deraadt@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
warning: no output file specified
Enter 'help' for information
ukc> find iwi
131 iwi* at pci* dev -1 function -1 flags 0x0
ukc> quit
Reply With Quote
  #2   (View Single Post)  
Old 3rd June 2008
jggimi's Avatar
jggimi jggimi is online now
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 3,435
Thanked 214 Times in 189 Posts
Default

Make sure your firmware was unpacked correctly. In the tarball is a +CONTENTS file, a +DESC file, and an etc/ folder containing the firmware and related files. If you untarred directly into /etc, the firmware will be in /etc/etc/firmware, which would be in error.

Your dmesg fragment status, "could not map memory space" is disconcerting. If you have confirmed the firmware is in the right spot, then this error should be reported to the OpenBSD project. Use sendbug if you have a working NIC. I recommend this because the HCL lists the iwi driver and the 2200 BG as supported on the amd64 architecture.

Yeah, I note that the +CONTENTS say "@arch i386" -- but the man page for amd64 and i386 point to the same package.

As a circumvention, you could install i386 and see if the NIC works there.
Reply With Quote
  #3   (View Single Post)  
Old 3rd June 2008
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 2,834
Thanked 190 Times in 160 Posts
Default

Quote:
Originally Posted by jggimi View Post
MUse sendbug if you have a working NIC.
For more information on submitting PR's, see the following:

http://openbsd.org/report.html
Reply With Quote
  #4   (View Single Post)  
Old 4th June 2008
BSDfan666 BSDfan666 is offline
Real Name: N/A, this is the interweb.
Helpful companion
 
Join Date: Apr 2008
Location: Ontario, Canada
Posts: 2,223
Thanked 193 Times in 184 Posts
Default

There are some config flags for pcibios(4) that can fix possible PCI configuration problems... another option is to disable pcibios and enable acpi for acpiprt(4) support.

Note: A message was sent into @tech that may fix some systems, http://marc.info/?t=121235482300003&r=1&w=2

If this doesn't work, try using GENERIC.MP, even on non-MP systems the introduction of ioapic(4) may be beneficial.

Good luck & Take care.
Reply With Quote
Reply

Tags
intel, wireless

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
ATH not loaded during boot time?? disappearedng FreeBSD General 4 14th July 2008 06:57 AM


All times are GMT. The time now is 04:51 PM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick