Re: 2.6.15-1-sparc64 issues on blade 100

2006-02-21 Thread Dave Love
Luis F. Ortiz [EMAIL PROTECTED] writes: So I took a peek at the reference clock chip (X7) and it is a 29.4 Mhz clock. The same with mine, I think, though it's rather indistinct. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: 2.6.15-1-sparc64 issues on blade 100

2006-02-18 Thread Luis F. Ortiz
On Feb 14, 2006, at 11:42 AM, Dave Love wrote: My XF86Config-4 does still have the old Option reference_clock 28.636 Mhz though. Presumably that should be irrelevant now, should it? Dave: I've been dragging that line around in my X config file for quite awhile. So

Re: 2.6.15-1-sparc64 issues on blade 100

2006-02-15 Thread Admar Schoonen
Dear Luis, On Mon, Feb 13, 2006 at 07:18:02PM -0500, Luis F. Ortiz wrote: I'm running OBP 4.5.9 (2002/02/07), which I think is the latest that can run on a Sparc Blade 100. I have just upgraded to OBP 4.17.1 2005/04/11 14:31. This solved the issue of 'flickering' and red dots in Xorg.

Re: 2.6.15-1-sparc64 issues on blade 100

2006-02-14 Thread Dave Love
Luis F. Ortiz [EMAIL PROTECTED] writes: I'm running OBP 4.5.9 (2002/02/07), which I think is the latest that can run on a Sparc Blade 100. Mine has cpu : TI UltraSparc IIe (Hummingbird) fpu : UltraSparc IIe integrated FPU promlib : Version 3

Re: 2.6.15-1-sparc64 issues on blade 100

2006-02-13 Thread Luis F. Ortiz
On Feb 12, 2006, at 1:40 PM, Admar Schoonen wrote: ... Louis: which open boot firmware are you using? According to /proc/openprom/openprom/version, I'm still at OBP 4.0.45 2001/02/08 14:33, could this be an issue for the framebuffer code? If not, then is it possible that my Ati chip is a

Re: 2.6.15-1-sparc64 issues on blade 100

2006-02-12 Thread Admar Schoonen
On Fri, Feb 10, 2006 at 08:46:40PM -0800, Jurij Smakov wrote: On Wed, 8 Feb 2006, Luis F. Ortiz wrote: With regard to the video problems, you are welcome to try my fix to the problem. There were two problems I found, a missing flag (M64F_SDRAM_MAGIC_PLL) and a bad clock rate (230

Re: 2.6.15-1-sparc64 issues on blade 100

2006-02-12 Thread Jurij Smakov
On Sun, 12 Feb 2006, Admar Schoonen wrote: I just tried http://www.wooyd.org/debian/kernels/linux-image-2.6.16-rc2-sparc64_2.6.15+2.6.16-rc2-0experimental.1_sparc.deb (time stamp is 11 Feb 2006, 09:17), and there is still some flickering in the console when text is scrolling by, and there are

Re: 2.6.15-1-sparc64 issues on blade 100

2006-02-10 Thread Jurij Smakov
On Wed, 8 Feb 2006, Luis F. Ortiz wrote: With regard to the video problems, you are welcome to try my fix to the problem. There were two problems I found, a missing flag (M64F_SDRAM_MAGIC_PLL) and a bad clock rate (230 instead of 235). Try applying some variation of the following patch.

Re: 2.6.15-1-sparc64 issues on blade 100

2006-02-09 Thread Admar Schoonen
Dear Luis Ortiz and Jurij Smakov, On Wed, Feb 08, 2006 at 08:02:54AM -0500, Luis F. Ortiz wrote: With regard to the video problems, you are welcome to try my fix to the problem. Thanks Luis! I will try your patch next weekend. In mean time, Jurij posted new kernel images at

Re: 2.6.15-1-sparc64 issues on blade 100

2006-02-08 Thread Luis F. Ortiz
On Feb 2, 2006, at 6:37 PM, Admar Schoonen wrote: Dear Debian people, I recently tried linux-image-2.6.15-1-sparc64 with an up to date unstable on my blade 100. I noticed a few issues: 1. Framebuffer is still a bit distorted. This is (or at least was) a known issue for recent kernels

2.6.15-1-sparc64 issues on blade 100

2006-02-02 Thread Admar Schoonen
Dear Debian people, I recently tried linux-image-2.6.15-1-sparc64 with an up to date unstable on my blade 100. I noticed a few issues: 1. Framebuffer is still a bit distorted. This is (or at least was) a known issue for recent kernels (bug id 317756). However, this bug is closed, but