From owner-freebsd-mobile Mon Apr 30 14: 0:51 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from pogo.caustic.org (pogo.caustic.org [208.44.193.69]) by hub.freebsd.org (Postfix) with ESMTP id 2213137B422 for ; Mon, 30 Apr 2001 14:00:49 -0700 (PDT) (envelope-from johan.beisser@caustic.org) Received: from localhost (jan@localhost) by pogo.caustic.org (8.11.0/ignatz) with ESMTP id f3UL0mQ02503 for ; Mon, 30 Apr 2001 14:00:48 -0700 (PDT) X-Authentication-Warning: pogo.caustic.org: jan owned process doing -bs Date: Mon, 30 Apr 2001 14:00:48 -0700 (PDT) From: "F. Johan Beisser" X-Sender: jan@pogo.caustic.org To: mobile@freebsd.org Subject: Toshiba Satellite Pro 4600 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hola, i've recently come in to the posession of a Toshiba Satellite Pro 4600. after some work, i've installed FreeBSD 4.3-RELEASE on a partition of the disk. so far, there've been a few problems. First, the built in fxp ethernet card times out. it seems to be related with the sharing of IRQs between many of the onboard PCI devices. The real trick is that it seems i can't move any of these devices around at all. currently, i'm running a slightly customised version of the GENERIC kernel (i removed the USB devices, and stopped running the usbd to clear up some clutter in the output from dmesg). any ideas? according to win2k, and freebsds dmesg, most devices on this machine are set to use irq 11. i've not found an easy way to move irqs (win2k does let you do this, but it seems that the laptops BIOS doesn't want to listen). any thoughts or experiences with Toshiba laptops and making them work with FreeBSD 4 would be appreciated. thanks much, -- johan +------/ f. johan beisser /-----------------------------------+ Web: http://caustic.org/~jan email: johan.beisser@caustic.org "knowledge is power, power corrupts. study hard, be evil" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message