From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <94fcb271ea827fa3d297aef77ef9b6a9@granite.cias.osakafu-u.ac.jp> To: 9fans@cse.psu.edu Subject: Re: [9fans] South bridge not found From: okamoto@granite.cias.osakafu-u.ac.jp MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-vjdtsmzqtxfqkkkqdkjjwhujpm" Date: Tue, 22 Oct 2002 17:09:08 +0900 Topicbox-Message-UUID: 09a59588-eacb-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-vjdtsmzqtxfqkkkqdkjjwhujpm Content-Disposition: inline Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Hi Russ, Yes, you are right. The problem was fixed. So, I have to recognize the card identity before /sys/src/9/pc/vganvidia.c:/^nvidiacurload will be called... My another nvidia card (GeForce 2 MX) does right order of left and right. Kenji --upas-vjdtsmzqtxfqkkkqdkjjwhujpm Content-Type: message/rfc822 Content-Disposition: inline Received: from granite.cias.osakafu-u.ac.jp ([192.168.1.3]) by diabase; Tue Oct 22 16:02:33 JST 2002 Received: from elmo.cias.osakafu-u.ac.jp (elmo.cias.osakafu-u.ac.jp [157.16.103.2]) by granite.cias.osakafu-u.ac.jp (8.9.3/8.9.3) with ESMTP id PAA12002 for ; Tue, 22 Oct 2002 15:35:55 +0900 Received: from mail.cse.psu.edu (psuvax1.cse.psu.edu [130.203.4.6]) by elmo.cias.osakafu-u.ac.jp (8.9.3/3.7W-02040219) with ESMTP id PAA07025 for ; Tue, 22 Oct 2002 15:59:20 +0900 (JST) Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.16.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 702AE19A93; Tue, 22 Oct 2002 02:59:11 -0400 (EDT) Delivered-To: 9fans@cse.psu.edu Received: from granite.cias.osakafu-u.ac.jp (granite.cias.osakafu-u.ac.jp [157.16.101.69]) by mail.cse.psu.edu (CSE Mail Server) with SMTP id 3A54319A8C for <9fans@cse.psu.edu>; Tue, 22 Oct 2002 02:58:52 -0400 (EDT) Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] South bridge not found From: okamoto@granite.cias.osakafu-u.ac.jp MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-btwxjbdstokltoanejhsjkgdqu" Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Tue, 22 Oct 2002 15:59:32 +0900 This is a multi-part message in MIME format. --upas-btwxjbdstokltoanejhsjkgdqu Content-Disposition: inline Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit It is vid=0x10DE did=0x0171. I tried Russ's patch, and recompiled kernel, and got panic. :-) Please wait for a while, I have not updated source tree for a while. settime() is the problem (only one, I don't knwo). After solving this problem, I'll try Russ's suggestion. Kenji --upas-btwxjbdstokltoanejhsjkgdqu Content-Type: message/rfc822 Content-Disposition: inline Received: from granite.cias.osakafu-u.ac.jp ([192.168.1.3]) by diabase; Tue Oct 22 15:55:32 JST 2002 Received: from elmo.cias.osakafu-u.ac.jp (elmo.cias.osakafu-u.ac.jp [157.16.103.2]) by granite.cias.osakafu-u.ac.jp (8.9.3/8.9.3) with ESMTP id PAA11991 for ; Tue, 22 Oct 2002 15:28:54 +0900 Received: from mail.cse.psu.edu (psuvax1.cse.psu.edu [130.203.4.6]) by elmo.cias.osakafu-u.ac.jp (8.9.3/3.7W-02040219) with ESMTP id PAA06922 for ; Tue, 22 Oct 2002 15:52:19 +0900 (JST) Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.16.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 772DB19A8D; Tue, 22 Oct 2002 02:52:11 -0400 (EDT) Delivered-To: 9fans@cse.psu.edu Received: from fbsd.acl.lanl.gov (fbsd.acl.lanl.gov [128.165.147.119]) by mail.cse.psu.edu (CSE Mail Server) with SMTP id 4D88219A78 for <9fans@cse.psu.edu>; Tue, 22 Oct 2002 02:51:28 -0400 (EDT) Received: (qmail 33207 invoked by uid 18927); 22 Oct 2002 06:46:13 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 22 Oct 2002 06:46:13 -0000 From: andrey mirtchovski X-X-Sender: andrey@fbsd.acl.lanl.gov To: 9fans@cse.psu.edu Subject: Re: [9fans] South bridge not found In-Reply-To: <069e379061d75fb2d08fbb1be54e4542@plan9.bell-labs.com> Message-ID: <20021022004039.F30430-100000@fbsd.acl.lanl.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Tue, 22 Oct 2002 00:46:13 -0600 (MDT) On Tue, 22 Oct 2002, Russ Cox wrote: > That makes the problem a lot easier. > [snip] As usual, you have the correct solution. What is the vendor ID for this card? It should be in the current P9 driver already, but that means somebody actually had a card with the same device ID and did not report a problem? I definitely have had no such experience with the Ti4600... andrey --upas-btwxjbdstokltoanejhsjkgdqu-- --upas-vjdtsmzqtxfqkkkqdkjjwhujpm--