Mark Vojkovich wrote:
>
>
>
> On Thu, 15 May 2003, Kevin Brosius wrote:
>
> > Basz wrote:
> > >
> > >
> > > I've been trying to get a generic no-name laptop up using Debian. The
> > > video
> > > chip is a S3 Virge /
Basz wrote:
>
>
> I've been trying to get a generic no-name laptop up using Debian. The video
> chip is a S3 Virge / MX.
>
> I started on Woody, then Sarge and now I'm on Sid. The problem is the
> same. (I've also tried RH7.2-RH8, I haven't yet tried RH9).
>
> After "startx", the screen clear
Kevin Brosius wrote:
>
> Drew Parsons wrote:
> >
> >
> > On Mon, May 07, 2001 at 09:35:30PM -0500, Kevin Brosius wrote:
> > >
> > > I've run through a quick backdate of a few changes and thrown a 4.0.99.3
> > > module up (http://www.user1
Drew Parsons wrote:
>
>
> On Mon, May 07, 2001 at 09:35:30PM -0500, Kevin Brosius wrote:
> >
> > I've run through a quick backdate of a few changes and thrown a 4.0.99.3
> > module up (http://www.user1.netcarrier.com/~kbrosius/virge.html as
> > usual). I ha
Kevin Brosius wrote:
>
> Drew Parsons wrote:
> >
> >
> > On Mon, May 07, 2001 at 09:35:30PM -0500, Kevin Brosius wrote:
> > >
> > > I've run through a quick backdate of a few changes and thrown a 4.0.99.3
> > > module up (http://www.user1
Drew Parsons wrote:
>
>
> On Mon, May 07, 2001 at 09:35:30PM -0500, Kevin Brosius wrote:
> >
> > I've run through a quick backdate of a few changes and thrown a 4.0.99.3
> > module up (http://www.user1.netcarrier.com/~kbrosius/virge.html as
> > usual). I
Drew Parsons wrote:
>
>
> Hello Kevin,
>
> back in February we were trying to pin down the problems the ViRGE/MX card was
> having with the s3virge driver in X v4.
>
> Version 4.0.3 has since been released, and the release notes indicate
> something about the virge mx card was fixed.
>
> Howev
Drew Parsons wrote:
>
>
> Hello Kevin,
>
> back in February we were trying to pin down the problems the ViRGE/MX card was
> having with the s3virge driver in X v4.
>
> Version 4.0.3 has since been released, and the release notes indicate
> something about the virge mx card was fixed.
>
> Howe
Drew Parsons wrote:
>
>
> Hello Kevin,
>
> back in February we were trying to pin down the problems the ViRGE/MX card was
> having with the s3virge driver in X v4.
>
> Version 4.0.3 has since been released, and the release notes indicate
> something about the virge mx card was fixed.
>
Hmm, I
Drew Parsons wrote:
>
>
> Hello Kevin,
>
> back in February we were trying to pin down the problems the ViRGE/MX card was
> having with the s3virge driver in X v4.
>
> Version 4.0.3 has since been released, and the release notes indicate
> something about the virge mx card was fixed.
>
Hmm,
Robert Norris wrote:
>
>
> Kevin, all,
>
> > I've put another test version of the driver up on the page above.
> > Robert, Drew, if one of you would run this and post the log I'd
> > appreciate it. I doubt it will work any better than the 1.6.4 version
> > (you don't need to test with any deb
Robert Norris wrote:
>
>
> Kevin, all,
>
> > I've put another test version of the driver up on the page above.
> > Robert, Drew, if one of you would run this and post the log I'd
> > appreciate it. I doubt it will work any better than the 1.6.4 version
> > (you don't need to test with any de
>
> On Sat, Feb 10, 2001 at 01:30:30PM -0500, Kevin Brosius wrote:
> > Hi all,
> > I've but up another version of the MX test driver. It's at
> > http://www.user1.netcarrier.com/~kbrosius/virge.html as usual. Let me
> > know if this improves things.
>
> On Sat, Feb 10, 2001 at 01:30:30PM -0500, Kevin Brosius wrote:
> > Hi all,
> > I've but up another version of the MX test driver. It's at
> > http://www.user1.netcarrier.com/~kbrosius/virge.html as usual. Let me
> > know if this improves things.
Hi all,
I've but up another version of the MX test driver. It's at
http://www.user1.netcarrier.com/~kbrosius/virge.html as usual. Let me
know if this improves things. I've removed some initialization added
for GX2 and Xv which may be causing the screen corruption you saw with
the last test cas
Hi all,
I've but up another version of the MX test driver. It's at
http://www.user1.netcarrier.com/~kbrosius/virge.html as usual. Let me
know if this improves things. I've removed some initialization added
for GX2 and Xv which may be causing the screen corruption you saw with
the last test ca
Iain Thomas wrote:
>
>
> On Tue, 6 Feb 2001, Kevin Brosius wrote:
> > Iain Thomas wrote:
> > > On Tue, 6 Feb 2001, Drew Parsons wrote:
> > > > Dear Kevin and XFree86 developers,
> > > > The system runs perfectly fine using the vesa driver (log he
Iain Thomas wrote:
>
>
> On Tue, 6 Feb 2001, Kevin Brosius wrote:
> > Iain Thomas wrote:
> > > On Tue, 6 Feb 2001, Drew Parsons wrote:
> > > > Dear Kevin and XFree86 developers,
> > > > The system runs perfectly fine using the vesa driver (log
Iain Thomas wrote:
>
>
> On Tue, 6 Feb 2001, Drew Parsons wrote:
> > Dear Kevin and XFree86 developers,
> > The system runs perfectly fine using the vesa driver (log here ), but when I
> > try to use the proper s3virge, the computer completely freezes up, not even
> > responding to kernel magic S
Robert Norris wrote:
>
>
> > Okay, that rules out a couple obvious possibilities. I've put up a
> > purely test version on my page (ver 1.6.2) which does incremental
> > startup, pausing for a couple seconds at various points in the init.
> > sequence. Would you give it a try and post or mail m
Iain Thomas wrote:
>
>
> On Tue, 6 Feb 2001, Drew Parsons wrote:
> > Dear Kevin and XFree86 developers,
> > The system runs perfectly fine using the vesa driver (log here ), but when I
> > try to use the proper s3virge, the computer completely freezes up, not even
> > responding to kernel magic
Robert Norris wrote:
>
>
> > Okay, that rules out a couple obvious possibilities. I've put up a
> > purely test version on my page (ver 1.6.2) which does incremental
> > startup, pausing for a couple seconds at various points in the init.
> > sequence. Would you give it a try and post or mail
Robert Norris wrote:
>
>
> > Great! What kind of console are you running? Is it a text or graphical
> > console (vesafb or other)?
>
> vesafb mostly, but I've been running all the tests in both, just to see
> if it makes a difference. It hasn't.
>
> > Option "pci_burst"
> >
> > Does that help
Robert Norris wrote:
>
>
> > Great! What kind of console are you running? Is it a text or graphical
> > console (vesafb or other)?
>
> vesafb mostly, but I've been running all the tests in both, just to see
> if it makes a difference. It hasn't.
>
> > Option "pci_burst"
> >
> > Does that hel
Robert Norris wrote:
>
>
...
>
> I appreciate your efforts on this. If can help in any way (logfiles,
> test programs, whatever) please let me know - I'm happy to try anything.
>
> Regards,
> Rob.
>
Great! What kind of console are you running? Is it a text or graphical
console (vesafb or
Robert Norris wrote:
>
>
...
>
> I appreciate your efforts on this. If can help in any way (logfiles,
> test programs, whatever) please let me know - I'm happy to try anything.
>
> Regards,
> Rob.
>
Great! What kind of console are you running? Is it a text or graphical
console (vesafb or
Robert Norris wrote:
>
>
> Hi all,
>
> Until recently, I've had XFree86 from potato installed on my Toshiba
> Satellite Pro 490XCDT, without issue. This laptop has a S3 ViRGE/MX
> video chip, so I was using xserver-svga 3.3.6-11.
>
> Today I upgraded the system to woody. xserver-xfree86 4.0.2-1
Robert Norris wrote:
>
>
> Hi all,
>
> Until recently, I've had XFree86 from potato installed on my Toshiba
> Satellite Pro 490XCDT, without issue. This laptop has a S3 ViRGE/MX
> video chip, so I was using xserver-svga 3.3.6-11.
>
> Today I upgraded the system to woody. xserver-xfree86 4.0.2-
28 matches
Mail list logo
