> With 3.7 released, I figured this would be a great time to add wifi
> ability to my firewall.  Being a good boy, I checked the HCL at
> http://www.openbsd.org/i386.html to see which cards I should look for at
> my local retailers.  Several were in stock, so I grabbed one and
> installed, only to find that it wouldn't boot.  Grumble, look at the
> box, and see nothing amiss.  Head back to store, swap for another card,
> only to have the same story repeated.  At this point, I'm beginning to
> suspect something wrong with my system, but I have no clue what.  The
> only lead I have is that some of the cards I didn't pick were marked
> "PCI 2.2 slot", and my system is PCI 2.1.  The boxes I did try didn't
> have a PCI rev listed.  So I suppose the best question to ask is, has
> anyone encountered a 2.1 friendly card, or am I up a creek?
>
> dmesg:
> [ using 465076 bytes of bsd ELF symbol table ]
> Copyright (c) 1982, 1986, 1989, 1991, 1993
>         The Regents of the University of California.  All rights reserved.
> Copyright (c) 1995-2005 OpenBSD. All rights reserved.
> http://www.OpenBSD.org
>
> OpenBSD 3.7 (GENERIC) #50: Sun Mar 20 00:01:57 MST 2005
>     [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Intel Pentium (P54C) ("GenuineIntel" 586-class) 171 MHz
> cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8
> cpu0: F00F bug workaround installed
> real mem  = 100245504 (97896K)
> avail mem = 84451328 (82472K)
> using 1249 buffers containing 5115904 bytes (4996K) of memory
> mainbus0 (root)
> bios0 at mainbus0: AT/286+(c8) BIOS, date 02/26/97, BIOS32 rev.  @
> 0xfb340
> apm0 at bios0: Power Management spec V1.2
> apm0: APM engage (device 1): power management disabled (1)
> apm0: AC on, battery charge unknown
> pcibios0 at bios0: rev 2.1 @ 0xf0000/0xb804
> pcibios0: PCI BIOS has 6 Interrupt Routing table entries
> pcibios0: PCI Interrupt Router at 000:07:0 ("Intel 82371SB ISA" rev 0x00)
> pcibios0: PCI bus #0 is the last bus
> bios0: ROM list: 0xc0000/0x8000
> cpu0 at mainbus0
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev  function  "Intel 82437VX" rev 0x02
> pcib0 at pci0 dev 7 function  "Intel 82371SB ISA" rev 0x01
> pciide0 at pci0 dev 7 function 1 "Intel 82371SB IDE" rev 0x00: DMA,
> channel  wired to compatibility, channel 1 wired to compatibility
> wd0 at pciide0 channel  drive 0: <QUANTUM FIREBALL EX13.6A>
> wd0: 16-sector PIO, LBA, 12970MB, 26563824 sectors
> wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
> pciide0: channel 1 disabled (no drives)
> vga1 at pci0 dev 9 function  "S3 ViRGE DX/GX" rev 0x01
> wsdisplay0 at vga1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> fxp0 at pci0 dev 10 function  "Intel 82557" rev 0x02: irq 10, address
> 00:a0:c9:77:80:0d
> inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 0
> isa0 at pcib0
> isadma0 at isa0
> pckbc0 at isa0 port 0x60/5
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0 (mux 1 ignored for console): console keyboard, using
> wsdisplay0
> pcppi0 at isa0 port 0x61
> midi0 at pcppi0: <PC speaker>
> sysbeep0 at pcppi0
> npx0 at isa0 port 0xf0/16: using exception 16
> pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> pccom0: console
> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
> biomask fbed netmask ffed ttymask ffef
> pctr: 586-class performance counters and user-level cycle counter enabled
> dkcsum: wd0 matched BIOS disk 80
> root on wd0a
> rootdev=0x0 rrootdev=0x300 rawdev=0x302
> Automatic boot in progress: starting file system checks.
> /dev/rwd0a: file system is clean; not checking
> /dev/rwd0g: file system is clean; not checking
> /dev/rwd0d: file system is clean; not checking
> /dev/rwd0f: file system is clean; not checking
> /dev/rwd0e: file system is clean; not checking
> /dev/rwd0h: file system is clean; not checking
> setting tty flags
> starting network
> starting system logger
> starting rpc daemons: ntpd.
> savecore: no core dump
> checking quotas: done.
> building ps databases: kvm dev.
> clearing /tmp
> starting pre-securelevel daemons:.
> setting kernel security level: kern.securelevel:  -> 1
> creating runtime link editor directory cache.
> preserving editor files
> starting network daemons: sendmail inetd sshd.
> starting local daemons:.
> standard daemons: cron.
> Fri May 20 20:38:22 EDT 2005

A DLINK DWL-G520 (Rev 2) seams to work fine (at an ASUS K8V with a Duron
1800Mhz). =)
And I hope the drivers will be ported to other archs too! (like AMD64.. :-( )

Btw: Some boards have problems if you include some PCI-Cards to some
PCI-Slots. Mostly the card work in another PCI-Slot (then it depends to
the damn sharings) but sometimes some Cards wont work at some motherboards
(some greets to the old VIA Chipsets and others..).

Kind regards,
Sebastian

Reply via email to