what change of vesa...

what change of vesa...

[Kenji Okamoto]

[-- Attachment #1: Type: text/plain, Size: 567 bytes --]

I crushed my 9front file server several months ago.
I got fortunately motivation to reconstruct the system
again these days, and got a recent CDROM (May 24, 2015).

Now I have strange problem on my nvidia card, which say
somethin strange handling..., which leads me to non rio.
Then, I tried vesa mode with 1024x768x8 which runs fine.

What were the changes on this vesa related timing things
cinap reported before.   Can I see the difference of old and
new codes.   As I mentioned above, I crushed my file server,
and cannot see them by myself.

Kenji

[-- Attachment #2: Type: text/html, Size: 830 bytes --]

Re: [9front] what change of vesa...

[Kurt H Maier]

Quoting Kenji Okamoto <kokamoto@hera.eonet.ne.jp>:

> I crushed my 9front file server several months ago.
> I got fortunately motivation to reconstruct the system
> again these days, and got a recent CDROM (May 24, 2015).
>
> Now I have strange problem on my nvidia card, which say
> somethin strange handling..., which leads me to non rio.
> Then, I tried vesa mode with 1024x768x8 which runs fine.
>
> What were the changes on this vesa related timing things
> cinap reported before.   Can I see the difference of old and
> new codes.   As I mentioned above, I crushed my file server,
> and cannot see them by myself.
>
> Kenji

aux/vga: remove vbs/vbe from mode, use shs/ehs when sync is ment,  
prefer detailed timing in edid
http://code.9front.org/hg/plan9front/rev/d16d837b898c

aux/vga: use optional edid information to determine mode when vgadb fails
http://code.9front.org/hg/plan9front/rev/69d00d22733b

and you might want to look at aux/vga: cleanup vesa code
http://code.9front.org/hg/plan9front/rev/7ccbd823958c

wherein cinap talks about nvidiascale() -- not sure if it's related.

khm

Re: [9front] what change of vesa...

[cinap_lenrek]

> What were the changes on this vesa related timing things
> cinap reported before.   Can I see the difference of old and
> new codes.   As I mentioned above, I crushed my file server,
> and cannot see them by myself.

vesa shouldnt be affected by that at all. the timings are required
for native drivers. what went in new is that nvidiascale stuff,
maybe that screws up on your card. have you tried commenting it
out?

--
cinap

Re: [9front] what change of vesa...

[Kenji Okamoto]

Thanks cinap.
Yes, it solved the problem.

Sorry my delay of response.
I was out of email these two days.

Kenji
-----Original Message----- 
From: cinap_lenrek@felloff.net 
Sent: Monday, June 08, 2015 5:49 AM 
To: 9front@9front.org 
Subject: Re: [9front] what change of vesa... 

> What were the changes on this vesa related timing things
> cinap reported before.   Can I see the difference of old and
> new codes.   As I mentioned above, I crushed my file server,
> and cannot see them by myself.

vesa shouldnt be affected by that at all. the timings are required
for native drivers. what went in new is that nvidiascale stuff,
maybe that screws up on your card. have you tried commenting it
out?

--
cinap

Re: [9front] what change of vesa...

[kokamoto]

> Thanks cinap.
> Yes, it solved the problem.

My nvidia card is as follows:
1.0.0:	vid  03.00.00 10de/0392  10 0:fa000000 16777216 1:d000000c 268435456 3:fb000004 16777216 5:0000df01 128
	NVIDIA Corporation G73 [GeForce 7600 GS]

Kenji

Re: [9front] what change of vesa...

[cinap_lenrek]

thanks.

--
cinap

Re: [9front] what change of vesa...

[cinap_lenrek]

i dont have any nvidia cards to test this. i think the best
way forward would be to back out the nvidiascale stuff and just
enable it on the cards that are known to work.

i'll write ftrvxmtrx who added the stuff to provide vid/did's
on the cards known to work with this.

can you tell me the vid/did of your card in case these turn
out to be the same as ftrvxmtrx's cards? if that would be the
case then it might depend on the specific vesa bios version and we
need some other way to identify the cards.

thanks in advance.

--
cinap