> Alexey E. Suslikov writes:
> > Tuesday, October 21, 2003, 5:07:59 PM, you wrote:
> >
> > int 10 type
> > generic emulator
> >
> > 4.3.0/OpenBSD 3.4 no generic "bad cksm"
> > 4.3.0/Linux 2.4.23 "bad cksm" "bad cksm"
> > 4.3.99.14/OpenBSD 3.4 no generic "bad cksm"
> > 4.3.99.14/Linux 2.4.23 n/a n/a
> >
> > haven't tried 4.3.99.14 under Linux. tests was made via linux
> > livecd.
> >
> > think there are lot of people running 4.3.99.14 under Linux, so
> > we can just ask...
> >
> generic uses an emulator while the linux-specific version uses vm86.
> Therefore I suppose the first column is the linux specific one while
> the second is the 'generic' one.
> Since both show the bad checksum this may not be the cause of the
> problem.
> Do you see the same probems under linux as on BSD when you use the
> generic one? Do you also see them with the linux-specific int10
> module under Linux?
> Sorry for pestering you so much. I just want to make sure it's not
> an emulator but a BIOS problem.
i am sorry :) this mistake was made in hurrying. table must looks like
int 10 type
native generic
4.3.0/OpenBSD 3.4 no native "bad cksm"
4.3.0/Linux 2.4.23 "bad cksm" "bad cksm"
4.3.99.14/OpenBSD 3.4 no native "bad cksm"
4.3.99.14/Linux 2.4.23 n/a n/a
here, "native" means OS-specific int10 module (like vm86 on linux) and
"generic" means emulator. BSDs always use an emulator.
maybe this is a BIOS problem, but lot of people see this independently.
i don't think what they all have corrupted firmwares.
_______________________________________________
XFree86 mailing list
XFree86@xxxxxxxxxxx
http://XFree86.Org/mailman/listinfo/xfree86
