From owner-freebsd-current@FreeBSD.ORG Fri Dec 26 12:58:13 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA8F516A4CE for ; Fri, 26 Dec 2003 12:58:13 -0800 (PST) Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61A4B43D46 for ; Fri, 26 Dec 2003 12:58:12 -0800 (PST) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (localhost [127.0.0.1]) hBQKwCLr019072 for ; Fri, 26 Dec 2003 12:58:12 -0800 (PST) (envelope-from david@bunrab.catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.12.10/8.12.10/Submit) id hBQKwC5Y019071 for current@freebsd.org; Fri, 26 Dec 2003 12:58:12 -0800 (PST) (envelope-from david) Date: Fri, 26 Dec 2003 12:58:12 -0800 (PST) From: David Wolfskill Message-Id: <200312262058.hBQKwC5Y019071@bunrab.catwhisker.org> To: current@freebsd.org In-Reply-To: <200312262045.hBQKjERj019044@bunrab.catwhisker.org> Subject: Re: "no driver attached" for Realtek 8129-based NIC X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Dec 2003 20:58:14 -0000 Ugh. Looks as if my cut/paste of the console output ran across a lone '.' and somewhat truncated the output; worse, the next stuff was interpreted as Cc: addresses. Sorry about that.... :-( The console output that was dropped was not relevant to the problem, so I'll not bother with it further. I will point out that the kernel does still have the "rl" device; it also has the "re" device defined. A copy of the kernel configuration may be found at http://www.catwhisker.org/~david/FreeBSD/current/FREEBEAST if you'd like to take a look. One other thing: when running -STABLE, it seems that irq 2 is assigned to the 8129 NIC in question, while under -CURRENT, irq 16 is assigned. Bit when -CURRENT boots, the console output shows: ioapic0: intpin 2 -> irq 2 (edge, activehi) ... ioapic0: intpin 16 -> irq 16 (level, activelo) I'll freely admit that I don't know much about hardware generally (and PC hardware specifically), but given that we're talking about running the same hardware with the same BIOS settings (unless FreeBSD has some mechanism to change them), the difference between using irq 2 vs. irq 16 would appear to be fairly significant. But then, seeing: pcib0: matched entry for 0.9.INTA (source ) pcib0: device is hardwired to IRQ 16 found-> vendor=0x10ec, dev=0x8129, revid=0x00 bus=0, slot=9, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x20 (8000 ns), maxlat=0x40 (16000 ns) intpin=a, irq=16 map[10]: type 4, range 32, base 0100c400, size 7, enabled map[14]: type 1, range 32, base d9000000, size 7, enabled map[18]: type 1, range 32, base 01000000, size 24, enabled map[1c]: type 1, range 32, base 01000000, size 24, enabled map[20]: type 1, range 32, base 01000000, size 24, enabled map[24]: type 1, range 32, base 01000000, size 24, enabled followed a bit later by pci_describe_device(): no vendor data for c0c21af4 pci0: at device 9.0 (no driver attached) is something I have trouble understanding. Thanks for any clues, david -- David H. Wolfskill david@catwhisker.org If you want true virus-protection for your PC, install a non-Microsoft OS on it. Plausible candidates include FreeBSD, Linux, NetBSD, OpenBSD, and Solaris (in alphabetical order).