From owner-freebsd-mobile Mon Sep 10 19:42: 2 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 0D3CE37B40C for ; Mon, 10 Sep 2001 19:41:59 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f8B2fu608356; Mon, 10 Sep 2001 20:41:57 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f8B2ftt29320; Mon, 10 Sep 2001 20:41:56 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109110241.f8B2ftt29320@harmony.village.org> To: Lars Eggert Subject: Re: PC-Card broken: 4.4-RC4 & Dell Latitude C600 Cc: mobile@FreeBSD.ORG In-reply-to: Your message of "Mon, 10 Sep 2001 11:45:32 PDT." <3B9D0A4C.2090203@isi.edu> References: <3B9D0A4C.2090203@isi.edu> Date: Mon, 10 Sep 2001 20:41:55 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <3B9D0A4C.2090203@isi.edu> Lars Eggert writes: : I've installed 4.4-RC4 on a new Dell Latitude C600, and PC-cards aren't : working. Following the (extensive) thread about this earlier, I'm still : confused as to which settings could fix this. The Latitude c600 fixes might not have made it into RC4, so I'd try something newer. At least I think the latitude uses the TI-1130. If it is the dmesg below, then the TI-1130 fixes are relevant. : Problem: Any card I insert is probed twice! I fixed this *AFTER* 4.4RC-4. The message should be benign, but there is anecdotal evidence that it isn't... : For example, I insert a : Linksys PCMPC100 card, it is probed correctly as ed0 ("ed0 at port : 0x300-0x31f irq 11 slot 1 on pccard1"). A few seconds later, I get a : second probe message ("ed1 at port 0x320-0x33f irq 11 slot 1 on : pccard1") for the same card, and the machine freezes up. Wow! It shouldn't do that. I'd try the latest -stable to see if it still happens. : With the new PC-card code, is listing of available interrupts in : /etc/pccard.conf still required? Only if you specifically set intr_path to 1. Otherwise, the system just deals for you. : pcic0: irq 11 at device 3.0 on pci0 : pcic0: PCI Memory allocated: 0x44000000 : pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][CSC serial isa irq] : pccard0: on pcic0 This should work with PCI interrupts. I've not seen any laptops that have an interrupt routed to the pci slot like you have that don't work. Most of the problems with PCI interrupts are with interrupt routing when the BIOS doesn't assign it on boot. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message