From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mta01.eonet.ne.jp ([203.140.81.45]) by pp; Fri Jun 5 01:43:12 EDT 2015 Received: from neptune (101-140-104-248f1.osk3.eonet.ne.jp [101.140.104.248]) by mailmsa12.mozu.eo.k-opti.ad.jp with ESMTP id t555h8pv019099 for <9front@9front.org>; Fri, 5 Jun 2015 14:43:08 +0900 Message-ID: <59CBA0461FDA4C33A403BE5428B85959@jitaku.localdomain> List-ID: <9front.9front.org> X-Glyph: ➈ X-Bullshit: scripting framework From: "Kenji Okamoto" To: <9front@9front.org> Subject: what change of vesa... Date: Fri, 5 Jun 2015 14:43:07 +0900 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0009_01D09F9D.EF7D1BE0" X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 16.4.3528.331 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331 This is a multi-part message in MIME format. ------=_NextPart_000_0009_01D09F9D.EF7D1BE0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable 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 ------=_NextPart_000_0009_01D09F9D.EF7D1BE0 Content-Type: text/html; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable

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

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

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

Kenji

------=_NextPart_000_0009_01D09F9D.EF7D1BE0-- From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from owm.eumx.net ([91.82.101.43]) by pp; Fri Jun 5 01:48:01 EDT 2015 Date: Fri, 05 Jun 2015 05:47:54 +0000 Message-ID: <20150605054754.Horde.4Y3PRthjsf82m18ff_jAZbs@ssl.eumx.net> List-ID: <9front.9front.org> X-Glyph: ➈ X-Bullshit: virtual base ACPI component-aware template From: Kurt H Maier To: 9front@9front.org Subject: Re: [9front] what change of vesa... In-Reply-To: <59CBA0461FDA4C33A403BE5428B85959@jitaku.localdomain> User-Agent: Horde Application Framework 5 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline Quoting Kenji Okamoto : > 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mta01.eonet.ne.jp ([203.140.81.44]) by pp; Sun Jun 7 20:34:23 EDT 2015 Received: from mars.jitaku.localdomain (101-140-104-248f1.osk3.eonet.ne.jp [101.140.104.248]) by mailmsa11.mozu.eo.k-opti.ad.jp with ESMTP id t580YKF3012560 for <9front@9front.org>; Mon, 8 Jun 2015 09:34:20 +0900 To: 9front@9front.org Subject: Re: [9front] what change of vesa... Date: Mon, 8 Jun 2015 00:34:05 +0900 From: kokamoto@hera.eonet.ne.jp Message-ID: <152693ba0c43a33aef1369f5c34dc1ed@mars.jitaku.localdomain> List-ID: <9front.9front.org> X-Glyph: ➈ X-Bullshit: out-scaling-aware lifecycle layer In-Reply-To: <697F978772C44FA3B3A604D896E44F3D@jitaku.localdomain> References: <90445d4090491ca8ef71805b109ea8d4@felloff.net> <697F978772C44FA3B3A604D896E44F3D@jitaku.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit > 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from felloff.net ([199.191.58.38]) by pp; Sun Jun 7 16:49:41 EDT 2015 Message-ID: <90445d4090491ca8ef71805b109ea8d4@felloff.net> List-ID: <9front.9front.org> X-Glyph: ➈ X-Bullshit: advanced XML interface pipelining cloud realtime-java backend Date: Sun, 7 Jun 2015 22:49:23 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org Subject: Re: [9front] what change of vesa... In-Reply-To: <59CBA0461FDA4C33A403BE5428B85959@jitaku.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit > 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mta01.eonet.ne.jp ([203.140.81.47]) by pp; Sun Jun 7 20:21:18 EDT 2015 Received: from neptune (101-140-104-248f1.osk3.eonet.ne.jp [101.140.104.248]) by mailmsa12.mozu.eo.k-opti.ad.jp with ESMTP id t580LCiN027248 for <9front@9front.org>; Mon, 8 Jun 2015 09:21:12 +0900 Message-ID: <697F978772C44FA3B3A604D896E44F3D@jitaku.localdomain> List-ID: <9front.9front.org> X-Glyph: ➈ X-Bullshit: generic strategy From: "Kenji Okamoto" To: <9front@9front.org> References: <90445d4090491ca8ef71805b109ea8d4@felloff.net> In-Reply-To: <90445d4090491ca8ef71805b109ea8d4@felloff.net> Subject: Re: [9front] what change of vesa... Date: Mon, 8 Jun 2015 09:21:12 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 16.4.3528.331 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from felloff.net ([199.191.58.38]) by pp; Sun Jun 7 20:30:53 EDT 2015 Message-ID: <4249b7ac26891451b85d5a77da4a500e@felloff.net> List-ID: <9front.9front.org> X-Glyph: ➈ X-Bullshit: proven scripting DOM software Date: Mon, 8 Jun 2015 02:30:41 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org Subject: Re: [9front] what change of vesa... In-Reply-To: <697F978772C44FA3B3A604D896E44F3D@jitaku.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from felloff.net ([199.191.58.38]) by pp; Sun Jun 7 20:43:47 EDT 2015 Message-ID: <57624226abe1167c068aa13ab6fd444f@felloff.net> List-ID: <9front.9front.org> X-Glyph: ➈ X-Bullshit: mobile extended SQL over WEB2.0 module-scale hosting module-aware optimizer Date: Mon, 8 Jun 2015 02:43:39 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org Subject: Re: [9front] what change of vesa... In-Reply-To: <152693ba0c43a33aef1369f5c34dc1ed@mars.jitaku.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit thanks. -- cinap