On Tue, Feb 06, 2001 at 11:10:35AM -0500, Kevin Brosius wrote:
>
> There's a new version up on my web page (ver 1.6.3). It's another
> incremental start version which _will_ show a difference in the log. (I
> promise!) Would you try it out? It takes a little longer to start
> fully, ~4 seconds
On Tue, Feb 06, 2001 at 11:10:35AM -0500, Kevin Brosius wrote:
>
> There's a new version up on my web page (ver 1.6.3). It's another
> incremental start version which _will_ show a difference in the log. (I
> promise!) Would you try it out? It takes a little longer to start
> fully, ~4 second
> There's a new version up on my web page (ver 1.6.3). It's another
> incremental start version which _will_ show a difference in the log. (I
> promise!) Would you try it out? It takes a little longer to start
> fully, ~4 seconds, so allow 30-35 total.
Log files are up, I've included log files
> There's a new version up on my web page (ver 1.6.3). It's another
> incremental start version which _will_ show a difference in the log. (I
> promise!) Would you try it out? It takes a little longer to start
> fully, ~4 seconds, so allow 30-35 total.
Log files are up, I've included log file
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
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
On Sat, Feb 03, 2001 at 02:16:23PM +1100, Robert Norris wrote:
>
> I found bug #78406, which seems to describe this exact same problem, but
> it also states that it has been fixed.
That bug report was mine, by the way, so I'm following this thread with
interest. The new version did not in fact f
On Sat, Feb 03, 2001 at 02:16:23PM +1100, Robert Norris wrote:
>
> I found bug #78406, which seems to describe this exact same problem, but
> it also states that it has been fixed.
That bug report was mine, by the way, so I'm following this thread with
interest. The new version did not in fact
> 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 me the log? Wait
> about 30 seconds
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
> 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 me the log? Wait
> about 30 second
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
On Sat, Feb 03, 2001 at 11:49:49AM -0500, Kevin Brosius wrote:
> I've also put up another test version at
> http://www.user1.netcarrier.com/~kbrosius/virge.html. Try it without
> the pci_burst option if you still have trouble. Let me know if anything
> changes.
I've been following this thread wi
On Sat, Feb 03, 2001 at 11:49:49AM -0500, Kevin Brosius wrote:
> I've also put up another test version at
> http://www.user1.netcarrier.com/~kbrosius/virge.html. Try it without
> the pci_burst option if you still have trouble. Let me know if anything
> changes.
I've been following this thread w
> 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?
No change.
> I've also put up another te
> 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?
No change.
> I've also put up another t
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
On Sat, Feb 03, 2001 at 10:45:13PM +1100, Robert Norris wrote:
>
> > Have you tried 'XFree86 -configure' yet? That will generate a generic
> > XF86Config file. Let me know if you see any difference. It can't be
> > any worse...
>
> No change, unfortunately.
>
I've had what may well be exactly
Kevin,
> As far as XFree86 is concerned, you don't need to submit any more than
> this. I've forwarded your message to the private ViRGE mailing list,
> we'll see if anyone with a ViRGE MX can take a look. Will you be taking
> the log files down soon?
Thanks for your attention. The log files wi
On Sat, Feb 03, 2001 at 10:45:13PM +1100, Robert Norris wrote:
>
> > Have you tried 'XFree86 -configure' yet? That will generate a generic
> > XF86Config file. Let me know if you see any difference. It can't be
> > any worse...
>
> No change, unfortunately.
>
I've had what may well be exactl
Kevin,
> As far as XFree86 is concerned, you don't need to submit any more than
> this. I've forwarded your message to the private ViRGE mailing list,
> we'll see if anyone with a ViRGE MX can take a look. Will you be taking
> the log files down soon?
Thanks for your attention. The log files w
I had something quite similar when starting XFree4.0.1 after a boot sequence in
frame buffer mode (the machine was completly frozen).
After booting in a normal text mode X started without any problem.
My card is an S3 virge dx.
bye
Quoting Kevin Brosius <[EMAIL PROTECTED]>:
> Robert Norris wro
I had something quite similar when starting XFree4.0.1 after a boot sequence in
frame buffer mode (the machine was completly frozen).
After booting in a normal text mode X started without any problem.
My card is an S3 virge dx.
bye
Quoting Kevin Brosius <[EMAIL PROTECTED]>:
> Robert Norris wr
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
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 was
installed.
After configuring and st
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-
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 was
installed.
After configuring and s
28 matches
Mail list logo
