Re: sysctl(3) interface
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). DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: unique hardware identification
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 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 to 'dmidump' in this thread. If you're referring to getting smbios data reported in kenv - that is up to your system/BIOS vendor: If they don't embed the information in the BIOS, FreeBSD can't report it. The response on my laptop is complete. My older whitebox desktops either don't have the data populated or don't report it at all. kenv appeared in 4.1, the smbios. stuff only appeared midway in 6.1 danny That would explain it then. I'm running 6.1 release with the security updates, not stable. -- Daniel Rudy ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: unique hardware identification
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 to 'dmidump' in this thread. For retrieving DMI information, please see sysutils/dmidecode in the ports collection. It works fine on the HP Proliant machines here, it even reports the exact population of the RAM slots and other things, which makes remote administration easier. Of course, it only works on machines with DMI-compliant BIOS interface. If you don't get SMBIOS information, I very much doubt that it'll provide DMI information either. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, USt-Id: DE204219783 Any opinions expressed in this message are personal to the author and may not necessarily reflect the opinions of secnetix GmbH Co KG in any way. FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd I have stopped reading Stephen King novels. Now I just read C code instead. -- Richard A. O'Keefe ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Fast SCSI RAID controller
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 signature
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
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 still does not work for me. Even worse the computer is flooded with error messages to the point it is hard to reboot. These are like so: Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=92 flags=0 type=131 len=20 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=93 flags=0 type=157 len=244 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=94 flags=0 type=130 len=24 Feb 3 00:11:31 rose kernel: scanning channel 14 status 1 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=95 flags=0 type=131 len=20 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=96 flags=0 type=132 len=16 Feb 3 00:11:31 rose kernel: scan finished nchan=14 status=1 chan=14 Feb 3 00:11:31 rose kernel: rx notification qid=4 idx=136 flags=0 type=128 len=8 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=97 flags=0 type=157 len=244 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=98 flags=0 type=130 len=24 Feb 3 00:11:31 rose kernel: scanning channel 36 status 1 continually repeating and the WLAN light never lights up. For me the driver 0070121-wpi-freebsd.tar.gz as mentioned in the postof Gilbert Cao is the only one that works, and works very well. I am just using it now. My computer is a Sony Vaio VGN C1 in 32 bits mode. -- Michel Talon ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
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-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 still does not work for me. Even worse the computer is flooded with error messages to the point it is hard to reboot. These are like so: Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=92 flags=0 type=131 len=20 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=93 flags=0 type=157 len=244 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=94 flags=0 type=130 len=24 Feb 3 00:11:31 rose kernel: scanning channel 14 status 1 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=95 flags=0 type=131 len=20 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=96 flags=0 type=132 len=16 Feb 3 00:11:31 rose kernel: scan finished nchan=14 status=1 chan=14 Feb 3 00:11:31 rose kernel: rx notification qid=4 idx=136 flags=0 type=128 len=8 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=97 flags=0 type=157 len=244 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=98 flags=0 type=130 len=24 Feb 3 00:11:31 rose kernel: scanning channel 36 status 1 continually repeating and the WLAN light never lights up. For me the driver 0070121-wpi-freebsd.tar.gz as mentioned in the postof Gilbert Cao is the only one that works, and works very well. I am just using it now. My computer is a Sony Vaio VGN C1 in 32 bits mode. -- Michel Talon ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
