Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Mar 2005 16:26:32 -0500 (EST)
From:      "Matthew N. Dodd" <winter@jurai.net>
To:        Karel Miklav <karel.miklav@siol.net>
Cc:        freebsd-mobile@freebsd.org
Subject:   Re: Thinkpad 600e interrupt storm
Message-ID:  <20050310162340.Q63068@sasami.jurai.net>
In-Reply-To: <4230B9DE.6040908@siol.net>
References:  <20050219040357.47106754@spadger.best.vwh.net> <42197CA3.7050709@understudy.net> <421E331C.10804@siol.net> <20050224181142.B60128@sasami.jurai.net> <421E7780.6050800@understudy.net> <20050224202147.A60128@sasami.jurai.net> <421EAAA5.3090304@understudy.net> <20050225095658.D60128@sasami.jurai.net> <4226996D.3020402@understudy.net> <20050303004752.V16908@sasami.jurai.net> <422B9A6B.6050109@understudy.net> <4230B9DE.6040908@siol.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 10 Mar 2005, Karel Miklav wrote:
> tp# kldload smapi

Right, and the kernel will display something like this if it finds it.

smapi0: <SMAPI BIOS> at iomem 0xfe9a0-0xfe9bf on motherboard
smapi0: Version: 0.83, Length: 32, Checksum: 0x43
smapi0: Information=0x7<REAL_VM86,PROTECTED_16,PROTECTED_32>

> smapi: open(/dev/smapi0, ...): No such file or directory
> tp# mknod smapi c 0 0   <-- a wild guess

Nope, not with DEVFS.

I'm guessing that the orm(4) driver has claimed that BIOS region.  You'll 
have to load the module from the loader.

Add 'smapi_load="YES"' to /boot/loader.conf

-- 
10 40 80 C0 00 FF FF FF FF C0 00 00 00 00 10 AA AA 03 00 00 00 08 00



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050310162340.Q63068>