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 genericbad cksm
4.3.0/Linux 2.4.23bad cksmbad cksm
I haven't been following this too closely, but was this happening only
on BSDs? The VBE thing stuck out in my mind, as there was just an issue
in DRI (the radeon mergedfb changes) where using the generic int10
emulation caused the driver to crash, while the linux-specific one
didn't. I
Eric Anholt writes:
I haven't been following this too closely, but was this happening only
on BSDs? The VBE thing stuck out in my mind, as there was just an issue
in DRI (the radeon mergedfb changes) where using the generic int10
emulation caused the driver to crash, while the
Eric Anholt writes:
I haven't been following this too closely, but was this happening only
on BSDs? The VBE thing stuck out in my mind, as there was just an issue
in DRI (the radeon mergedfb changes) where using the generic int10
emulation caused the driver to crash, while the
On Tue, 21 Oct 2003, Alexey E. Suslikov wrote:
I haven't been following this too closely, but was this happening only
on BSDs? The VBE thing stuck out in my mind, as there was just an issue
in DRI (the radeon mergedfb changes) where using the generic int10
emulation caused the driver to
On Tue, Oct 21, 2003 at 08:07:59AM -0600, Marc Aurele La France wrote:
On Tue, 21 Oct 2003, Alexey E. Suslikov wrote:
I haven't been following this too closely, but was this happening only
on BSDs? The VBE thing stuck out in my mind, as there was just an issue
in DRI (the radeon
Tuesday, October 21, 2003, 5:07:59 PM, you wrote:
On Tue, 21 Oct 2003, Alexey E. Suslikov wrote:
I haven't been following this too closely, but was this happening only
on BSDs? The VBE thing stuck out in my mind, as there was just an issue
in DRI (the radeon mergedfb changes) where using
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 genericbad cksm
4.3.0/Linux 2.4.23bad cksmbad cksm
keywords: openbsd, x11, i830, ring buffer, lockup
It just occurred to me where I had seen this type of black screen problem
before. It happens when using the vesa driver with an 845G. We work
around this in the i810 driver by remembering the initial video mode
and simply re-initialising it
On Mon, Oct 20, 2003 at 11:13:12AM +0300, Alexey E. Suslikov wrote:
keywords: openbsd, x11, i830, ring buffer, lockup
It just occurred to me where I had seen this type of black screen problem
before. It happens when using the vesa driver with an 845G. We work
around this in the i810
On Mon, Oct 20, 2003 at 11:13:12AM +0300, Alexey E. Suslikov wrote:
keywords: openbsd, x11, i830, ring buffer, lockup
It just occurred to me where I had seen this type of black screen problem
before. It happens when using the vesa driver with an 845G. We work
around this in the i810 driver
On Mon, 2003-10-20 at 18:40, David Dawes wrote:
On Mon, Oct 20, 2003 at 11:13:12AM +0300, Alexey E. Suslikov wrote:
keywords: openbsd, x11, i830, ring buffer, lockup
It just occurred to me where I had seen this type of black screen problem
before. It happens when using the vesa driver
12 matches
Mail list logo
