Alle 19:18, lunedì 8 settembre 2003, Thomas Winischhofer ha scritto:
> Flavio wrote:
> > 1) when starting X the display "blinks" (the same way as if it
> > starts, is immediately killed, and started again) for trhee, four
> > times; then it finally works. Additionally when switching from X
> >
Alle 15:50, lunedì 8 settembre 2003, Alistair J Ross ha scritto:
> Flavio,
>
> 1) Hmm I've often had issues with similar SiS I/C's but on
> mainboards in the past. It probably has something to do with the way
> the driver or the hardware retains VRAM information. I can't help
> much there, is
Alle 19:18, lunedì 8 settembre 2003, Thomas Winischhofer ha scritto:
> Flavio wrote:
> > 1) when starting X the display "blinks" (the same way as if it
> > starts, is immediately killed, and started again) for trhee, four
> > times; then it finally works. Additionally when switching from X
> >
Alle 15:50, lunedì 8 settembre 2003, Alistair J Ross ha scritto:
> Flavio,
>
> 1) Hmm I've often had issues with similar SiS I/C's but on
> mainboards in the past. It probably has something to do with the way
> the driver or the hardware retains VRAM information. I can't help
> much there, is
Flavio wrote:
> 1) when starting X the display "blinks" (the same way as if it starts,
> is immediately killed, and started again) for trhee, four times; then
> it finally works. Additionally when switching from X to a console, the
How do you start X? xdm? kdm? ?dm? Or startx?
> screen remains "
Flavio wrote:
> 1) when starting X the display "blinks" (the same way as if it starts,
> is immediately killed, and started again) for trhee, four times; then
> it finally works. Additionally when switching from X to a console, the
How do you start X? xdm? kdm? ?dm? Or startx?
> screen remains "di
Flavio,
1) Hmm I've often had issues with similar SiS I/C's but on mainboards
in the past. It probably has something to do with the way the driver or
the hardware retains VRAM information. I can't help much there, is it a
severe issue or just an eyesore for a few se
Flavio,
1) Hmm I've often had issues with similar SiS I/C's but on mainboards
in the past. It probably has something to do with the way the driver or
the hardware retains VRAM information. I can't help much there, is it a
severe issue or just an eyesore for a few se
8 matches
Mail list logo
