Well, here it goes again:
Issue with my onboard
mskc0: Marvell Yukon 88E8053 Marvell Yukon-2
With the newest i386 (quite old btw.) snapshot, I can use msk0 without
any troubles UNTIL I start X on the machine.
As soon as I do that interrupts go to 99% and everything starts to crawl
until I
On 2006/09/14 11:03, Andreas Bihlmaier wrote:
With the newest i386 (quite old btw.) snapshot, I can use msk0 without
any troubles UNTIL I start X on the machine.
As soon as I do that interrupts go to 99% and everything starts to crawl
until I reboot. Pretty much same issue I had before with
* Stuart Henderson [EMAIL PROTECTED] [2006-09-14 11:27]:
On 2006/09/14 11:03, Andreas Bihlmaier wrote:
With the newest i386 (quite old btw.) snapshot, I can use msk0 without
any troubles UNTIL I start X on the machine.
As soon as I do that interrupts go to 99% and everything starts to crawl
On Thu, Sep 14, 2006 at 11:03:59AM +0200, Andreas Bihlmaier wrote:
Well, here it goes again:
Issue with my onboard
mskc0: Marvell Yukon 88E8053 Marvell Yukon-2
With the newest i386 (quite old btw.) snapshot, I can use msk0 without
any troubles UNTIL I start X on the machine.
As soon as I
On Thu, Sep 14, 2006 at 10:22:03AM +0100, Stuart Henderson wrote:
On 2006/09/14 11:03, Andreas Bihlmaier wrote:
With the newest i386 (quite old btw.) snapshot, I can use msk0 without
any troubles UNTIL I start X on the machine.
As soon as I do that interrupts go to 99% and everything starts
On Thu, Sep 14, 2006 at 11:03:59AM +0200, Andreas Bihlmaier wrote:
Well, here it goes again:
Issue with my onboard
mskc0: Marvell Yukon 88E8053 Marvell Yukon-2
With the newest i386 (quite old btw.) snapshot, I can use msk0 without
any troubles UNTIL I start X on the machine.
As soon as I
On Thu, Sep 14, 2006 at 07:44:44PM +1000, Jonathan Gray wrote:
On Thu, Sep 14, 2006 at 11:03:59AM +0200, Andreas Bihlmaier wrote:
Well, here it goes again:
Issue with my onboard
mskc0: Marvell Yukon 88E8053 Marvell Yukon-2
With the newest i386 (quite old btw.) snapshot, I can use
On Fri, Aug 18, 2006 at 01:02:13PM +0200, Andreas Bihlmaier wrote:
On Thu, Aug 17, 2006 at 09:04:05PM +0200, Mark Kettenis wrote:
Last night I checked in a driver, msk(4), for the previously
unsupported Marvell and SysKonnect Gigabit NICs. The driver works
pretty well for me on the new Mac
Date: Thu, 17 Aug 2006 20:58:08 -0400
From: Mike Erdely [EMAIL PROTECTED]
Mark Kettenis wrote:
Last night I checked in a driver, msk(4), for the previously
unsupported Marvell and SysKonnect Gigabit NICs.
I couldn't wait to get home! I downloaded the latest snapshot (today's
from
On Thu, Aug 17, 2006 at 09:04:05PM +0200, Mark Kettenis wrote:
Last night I checked in a driver, msk(4), for the previously
unsupported Marvell and SysKonnect Gigabit NICs. The driver works
pretty well for me on the new Mac mini, but could really use some more
testing, especially on different
Mark Kettenis wrote:
Oops, sorry to have made you go through the hoops again. I discovered
today that the BIOS on the mini is somewhat busted and reports the
wrong interrupt for msk(4). I've got some patches to get the
interrupt routing info from ACPI, but they're not quite ready yet to
go in.
Last night I checked in a driver, msk(4), for the previously
unsupported Marvell and SysKonnect Gigabit NICs. The driver works
pretty well for me on the new Mac mini, but could really use some more
testing, especially on different hardware. If you have such hardware
please compile yourself a
Mark Kettenis wrote:
Last night I checked in a driver, msk(4), for the previously
unsupported Marvell and SysKonnect Gigabit NICs.
I couldn't wait to get home! I downloaded the latest snapshot (today's
from ftp.openbsd.org) and burned cd40.iso to a CD-RW.
I rebooted my Mac Mini (purchased
13 matches
Mail list logo
