Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller

2007-02-02 Thread Sam Fourman Jr.
Michel, I was told a few days ago that those messages are nothing more than debug messages, and that is how it is supposed to work. Sam Fourman Jr. On 2/2/07, Michel Talon <[EMAIL PROTECTED]> wrote: > A new version of the driver is up which fixes the firmware issues. > Seems the wpi-firmwa

Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller

2007-02-02 Thread Michel Talon
> A new version of the driver is up which fixes the firmware issues. > Seems the wpi-firmware-kmod port was creating corrupt modules. > Things should work much better now. Download at the same place, file: > 20070131-wpi-freebsd.tar.gz Unfortunately, i must report that this last version stil

Fast SCSI RAID controller

2007-02-02 Thread Josef Grosch
Can anyone suggest a fast SCSI RAID controller for FreeBSD 6.2 ? Our vendor is having trouble with the latest Adaptec Josef -- Josef Grosch | Another day closer to a | FreeBSD 6.2 [EMAIL PROTECTED] | Micro$oft free world | Berkeley, Ca. pgpfQtFosRELO.pgp Description: PGP signatur

Re: unique hardware identification

2007-02-02 Thread Oliver Fromme
Peter Jeremy wrote: > Daniel Rudy wrote: > > None of this stuff appears on my system and I'm running 6.1. I can't > > even find dmidump anywhere on the system or in ports either. > > Please elaborate. kenv(8) states that it first appeared in 4.1.1 and > I don't recall seeing any reference

Re: unique hardware identification

2007-02-02 Thread Daniel Rudy
At about the time of 2/1/2007 11:33 PM, Danny Braniss stated the following: >> --ikeVEW9yuYc//A+q >> Content-Type: text/plain; charset=us-ascii >> Content-Disposition: inline >> Content-Transfer-Encoding: quoted-printable >> >> On Thu, 2007-Feb-01 21:49:43 -0800, Daniel Rudy wrote: >>> None of this

Re: sysctl(3) interface

2007-02-02 Thread Dag-Erling Smørgrav
Daniel Rudy <[EMAIL PROTECTED]> writes: > Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes: > > man 3 devinfo > A little too late since I already hacked the source for sysctl(8) and > figured out how it works. The dev sysctl tree contains only a subset of the information available through devinfo(3)