Does your kernel module load correctly? I get complaints about an
unsupported memory range [see my previous post for more details]. I'm
building a kernel with 'option PCI_ALLOW_UNSUPPORTED_IO_RANGE' now to
see if that helps.
And about __sF, could an LD_PRELOAD with a __sF 'stub' be a workaround?
-
Hmm, not for me (yet?). Part of dmesg:
VESA: v3.0, 16384k memory, flags:0x1, mode table:0xc03bb322 (122)
VESA: NVidia
VESA: NVidia Riva TNT A0
agp0: mem 0xe000-0xe3ff at
device 0.0 on pci0
agp0: allocating GATT for aperture of size 256M
nvidia0: mem 0xe600-0xe6ff
dn't try since asleep and
await have been removed. Furthermore, I changed the 10*hz sleep timeout to 100*hz,
no luck. I don't really know what to try next.
- Willem van Engen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, 27 Jun 2002 12:21:19 +0900
"Takanori Watanabe" <[EMAIL PROTECTED]> wrote:
> In message <[EMAIL PROTECTED]>, Willem van Engen wrote:
>
> >Hello,
> >
> >there already is some code for smbalert# handling on intpm
> >(ENABLE_ALART), but
I just installed cvsupped and installed a new world&kernel at 3feb2000.
Everything works fine, but reading /dev/dsp (cat /dev/dsp e.g.) gives
some thousands of bytes output, but then totally crashes the system;
it doesn't even break to the debugger when pressing Ctrl-Alt-Esc.
It worked fine on my
