From owner-freebsd-current@FreeBSD.ORG Mon Apr 12 20:24:12 2004 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 450FD16A4CE for ; Mon, 12 Apr 2004 20:24:12 -0700 (PDT) Received: from net.nigsch.com (194-208-143-121.TELE.NET [194.208.143.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id C474143D48 for ; Mon, 12 Apr 2004 20:24:10 -0700 (PDT) (envelope-from flo@nigsch.com) Received: from net.nigsch.com (flo@localhost.nigsch.com [127.0.0.1]) by net.nigsch.com (8.12.9p1/8.12.9) with ESMTP id i3D3O9rs087570 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 13 Apr 2004 05:24:09 +0200 (CEST) (envelope-from flo@net.nigsch.com) Received: (from flo@localhost) by net.nigsch.com (8.12.9p1/8.12.9/Submit) id i3D3O9Bh087569 for freebsd-current@freebsd.org; Tue, 13 Apr 2004 05:24:09 +0200 (CEST) (envelope-from flo) Date: Tue, 13 Apr 2004 05:24:09 +0200 From: Florian Nigsch To: freebsd-current@freebsd.org Message-ID: <20040413032409.GB87463@net.nigsch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4.1i Subject: Dell Insp. 8200 doesn't find ata disks 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: Tue, 13 Apr 2004 03:24:12 -0000 Hi people! I have a Dell Inspiron 8200, BIOS rev. A10, with an installed FreeBSD, 5.2.1-RELEASE from the CD iso images. I recompiled the kernel under this system, which worked fine. Then I cvsup'ed the new sources (at the time of this writing I am using the sources of about 12/04/2003 21:00 from cvsup2.freebsd.org) recompiled the world following the process indicated in the proper documentation. Everything works without any errors. When I try to boot with the new kernel of the now -CURRENT system, it hangs when it is about to mount the root partition. I don't know everything by heart, but it is the stuff: setrootbyname failed, unable to find root device, and then it gives the mountroot> prompt. When I type "?" there, there are NO bootable devices listed, which is quite uncool. My kernel finds the atapci0 driver/device, but then it doesn't find the ata0 driver and so the ad0 device never get's initialized. I already tried to turn off ACPI, which results in a kernel panic in an earlier step. hw.pci.allow_unsupported_pci_range="1" doesn't help either. Extracts from the booting kernel: ãtãþci0: <Ïntel Ï©H³ ÛàMù00 cøntrøller> þørt 0xbfã0-0xbfãfž0x³74-0x³77ž0x¹70-0x ¹77ž0x³f4-0x³f7ž0x¹f0-0x¹f7 ãt ðevice ³¹.¹ øn þci0 ãtã0: ãt 0x¹f0 irq ¹4 øn ãtãþci0 ãtã0: [MÞSÃFË] ãtã¹: ãt 0x¹70 irq ¹5 øn ãtãþci0 ãtã¹: [MÞSÃFË] ... GËØM: creãte ðisk ãð0 ðþ=0xc2e³2c60 ãð0: 286¹5MB [58¹40/¹6/6³] ãt ãtã0-mãster ÛàMù00 ãcð0: ©à®W ãt ãtã0-slãve ÞÏØ4 Møunting røøt frøm ufs:/ðev/ãð0s³ã ... These last lines never occur with the -CURRENT kernel. I looked everywhere for a solution to this problem, tried to cvsup the newest sources two times, recompiled everything, included the ROOTDEVICE option in the kernelconfig file, tried to hardcode the rootdisk in /boot/loader.conf . But of course, this all can't work, if there just simply are no /dev/ad0 devices. How can I make my system recognize the ad0 device? The bootloader in the beginning recognizes them, I can do an "ls" and see all the contents of the harddrive. The -CURRENT kernel just forgets about the ad0 devices in some way. Any help will be greatly appreciated! Thank you very much, Florian -- --- Florian Nigsch | http://flo.nigsch.com/ PGP key: http://flo.nigsch.com/fnigsch.asc Mail automatically filtered for spam by spambayes ______________________________________________________________