Re: i give up



Andrew Reilly wrote:
On Sun, Nov 30, 2008 at 10:37:39AM -0800, Tim Kientzle wrote:

I wonder if there's some way to partially automate
collecting some of this information.

There is. Just install ports/sysutils/bsdstats, set the
appropriate frobs in /etc/rc.conf and be happy. Look at the
http://bsdstats.org/ page from time to time.

This is a start towards what I had in mind, but
still has a ways to go. Here are a few questions
I would like to ask of such a database:

"What ethernet cards have people used with FreeBSD 7.0?"

This would require being able to start from
a particular OS (and version?).

"I have a Broadcom card, what driver do I need with FreeBSD 7?"

This requires being able to navigate from OS/version
to device type, manufacturer, then driver. This
should also have callouts for any driver that's not
part of the GENERIC kernel.

"pciconf just gave me an ID xyz123; what chip is that?"

I see device names but not hardware-level IDs.

"Any suggestions for a good network card to buy?"

This information seems to stop at the chipset level.
When I go to the store, very few boxes have chipset
names on them. It would be good to give users the
option to provide a manufacturer (and product name?)
for the card or motherboard in use. Such information
would necessarily be more sporadic than the automatically
collected information, but it would build up over time.

Based on the numbers here, I'm going to guess that
PC-BSD has this service turned on by default. You
should talk to folks maintaining installers for other
systems about possibly getting it integrated there.
(With clearly-worded notices about data being anonymous,
etc.)

It would also be interesting to use this from the installer
to look up missing drivers (enumerate PCI IDs for any
device that didn't attach a driver and query the bsdstats
service for information about that device); this would
make it a lot easier for users to find drivers supported
out-of-tree.

Such a database could provide very useful information to the
development community ("most popular unsupported ethernet
cards") and to users ("most popular supported ethernet
cards").

Tim
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Problems with r8168 on AMD64
    ... I'm using the r8168 driver (the latest one available ... card is still up, ... output of dmesg when I've loaded the module. ... r8168 Gigabit Ethernet driver 8.010.00-NAPI loaded ...
    (comp.os.linux.hardware)
  • Re: RTL8139 Card and forcedeth : Network Card all confused ..Help !
    ... Ethernet card. ... This MAC address is allocated to Asustek, so I guess it belongs to the built-in nVidia ethernet interface on the motherboard. ... When I ckeched on their website, the manufacturer provided only a driver source code for 2.4 kernel. ... I tried to hack the 2.6 kernel 8139too code to adapt it to the non standard PCI ID and PCI I/O and memory regions, ...
    (comp.os.linux.networking)
  • Re: i give up
    ... collecting some of this information. ... Just install ports/sysutils/bsdstats, set the ... "I have a Broadcom card, what driver do I need with FreeBSD 7?" ...
    (freebsd-current)
  • Wired LAN Compact Flash on PPC2003
    ... I need help setting a wired 10/100 MB Ethernet card on pocket pc 2003. ... The driver in the Cd ... Out of desperation I even tried to set it up under the Wireless Network ...
    (microsoft.public.pocketpc.developer.networking)
  • PCI ethernet card from ebay doesnt work at all. Possibly fake, but which?
    ... I needed a PCI ethernet card for an old P3 system and so I did some ... but doing ifup eth0 gives ... Silan cards and the correct driver is sc92031. ... does anyone know what card I really have? ...
    (Debian-User)