Re: framebuffer broken on 712 using kernel 2.6.4
On Thu, 9 Sep 2004, Stuart Brady wrote: On Thu, Aug 19, 2004 at 09:52:32AM +0300, Martin-Éric Racine wrote: [Snip] 2) all 2.6.x since 2.6.5 The PA-RISC Tux appears. Everything within the lines it occupies is a clean pitch black. Bootup messages start on the last line of the penguin, overlaping its legs. Messages up to Gecko-style soft power switch enabled. scroll on below. Messages following that appear on the feet of the penguin again and are all printed there, without scrolling down. Once the INIT: version 2.86 message appears at that location, things magically resume a few lines below the powerswitch kernel message, starting with the Setting disc parameters: done. message and scroll down, eventually making the penguin scroll off-screen. Try it with: STI_CONSOLE=y (STI text console) DUMMY_CONSOLE_COLUMNS=c (Initial number of console screen columns) DUMMY_CONSOLE_ROWS=r (Initial number of console screen rows) Where c is the screen width (in pixels) divided by 8 (E.g. 1024/8=128) and r is the height divided by 16 (E.g. 768/16=48). (These options are under Device Drivers - Graphics support - Console display driver support.) I don't know whether you actually need sticon itself, but you need to choose in order to set the columns/rows. Perhaps that's a bug. Using 128 and 48 solved it. This being said, it wasn't needed previously. I have no choice but to call that a regression, because it forces the kernel to be built for a specific framebuffer size; there is no way to have a generic kernel that will work for everyone, e.g. with the new Debian Installer, for instance. -- Martin-Éric Racine, ICT Consultant http://www.iki.fi/q-funk/
Re: framebuffer broken on 712 using kernel 2.6.4
On Thu, Aug 19, 2004 at 09:52:32AM +0300, Martin-Éric Racine wrote: [Snip] 2) all 2.6.x since 2.6.5 The PA-RISC Tux appears. Everything within the lines it occupies is a clean pitch black. Bootup messages start on the last line of the penguin, overlaping its legs. Messages up to Gecko-style soft power switch enabled. scroll on below. Messages following that appear on the feet of the penguin again and are all printed there, without scrolling down. Once the INIT: version 2.86 message appears at that location, things magically resume a few lines below the powerswitch kernel message, starting with the Setting disc parameters: done. message and scroll down, eventually making the penguin scroll off-screen. Try it with: STI_CONSOLE=y (STI text console) DUMMY_CONSOLE_COLUMNS=c (Initial number of console screen columns) DUMMY_CONSOLE_ROWS=r (Initial number of console screen rows) Where c is the screen width (in pixels) divided by 8 (E.g. 1024/8=128) and r is the height divided by 16 (E.g. 768/16=48). (These options are under Device Drivers - Graphics support - Console display driver support.) I don't know whether you actually need sticon itself, but you need to choose in order to set the columns/rows. Perhaps that's a bug. Hope that helps, -- Stuart Brady
Re: framebuffer broken on 712 using kernel 2.6.4
On Sat, Sep 04, 2004 at 12:45:50AM +0300, Martin-?ric Racine wrote: So I tried again with the following: source 2.6.8.1-pa7 gcc 3.4.1 binutils 2.15 Same result as before: PA Tux has its legs chopped and the bootup messages are a real mess. I have the same problem on a 715/100 with: source 2.6.8.1-pa7 gcc 3.3.4-6sarge1.2 binutils 2.15-1 It goes away once init is started. -- Stuart Brady
Re: framebuffer broken on 712 using kernel 2.6.4
On Thu, 2 Sep 2004, Carlos O'Donell wrote: source 2.6.8.1-pa7 gcc 3.3.3 binutils 2.14.90.0.7 I could upgrade gcc to 3.4.1, but I doubt this would change anything. Binutils 2.15 has been reported as broken, so I cannot use that anyhow. source 2.6.8.1-pa7 gcc version 3.3.4 (Debian 1:3.3.4-5) here. binutils 2.14.90.0.7 20031029 Debian GNU/Linux. So I tried again with the following: source 2.6.8.1-pa7 gcc 3.4.1 binutils 2.15 Same result as before: PA Tux has its legs chopped and the bootup messages are a real mess. -- Martin-Éric Racine, ICT Consultant http://www.iki.fi/q-funk/
Re: framebuffer broken on 712 using kernel 2.6.4
source 2.6.8.1-pa7 gcc 3.3.3 binutils 2.14.90.0.7 I could upgrade gcc to 3.4.1, but I doubt this would change anything. Binutils 2.15 has been reported as broken, so I cannot use that anyhow. source 2.6.8.1-pa7 gcc version 3.3.4 (Debian 1:3.3.4-5) here. binutils 2.14.90.0.7 20031029 Debian GNU/Linux. c.
Re: framebuffer broken on 712 using kernel 2.6.4
On Tue, 31 Aug 2004, Carlos O'Donell wrote: On Mon, Aug 30, 2004 at 01:01:27AM +0300, Martin-?ric Racine wrote: On Thu, 19 Aug 2004, Carlos O'Donell wrote: The latest kernel framebuffer works perfectly fine here on my 712/100, that's cvs head. With the PA-RISC penguin logo or the normal Tux or no logo? PA-RISC penguin logo. Here, I tried the kernel-image-2.6-32 from Debian to compare with my 712 kernel and still get the symptoms I described before. I would build a new kernel from cvs head, with unstable gcc and binutils. If that fails I can help you more. source 2.6.8.1-pa7 gcc 3.3.3 binutils 2.14.90.0.7 I could upgrade gcc to 3.4.1, but I doubt this would change anything. Binutils 2.15 has been reported as broken, so I cannot use that anyhow. -- Martin-Éric Racine, ICT Consultant http://www.iki.fi/q-funk/
Re: framebuffer broken on 712 using kernel 2.6.4
On Mon, Aug 30, 2004 at 01:01:27AM +0300, Martin-?ric Racine wrote: On Thu, 19 Aug 2004, Carlos O'Donell wrote: The latest kernel framebuffer works perfectly fine here on my 712/100, that's cvs head. With the PA-RISC penguin logo or the normal Tux or no logo? PA-RISC penguin logo. Here, I tried the kernel-image-2.6-32 from Debian to compare with my 712 kernel and still get the symptoms I described before. I would build a new kernel from cvs head, with unstable gcc and binutils. If that fails I can help you more. c.
Re: framebuffer broken on 712 using kernel 2.6.4
On Thu, 19 Aug 2004, Carlos O'Donell wrote: The latest kernel framebuffer works perfectly fine here on my 712/100, that's cvs head. With the PA-RISC penguin logo or the normal Tux or no logo? Here, I tried the kernel-image-2.6-32 from Debian to compare with my 712 kernel and still get the symptoms I described before. -- Martin-Éric Racine, ICT Consultant http://www.iki.fi/q-funk/
framebuffer broken on 712 using kernel 2.6.4
Hello, Perhaps the parisc-linux mailing list would be a better place for this, but I'm not a kernel hacker and thus do not subscribe... Since 2.6.5 the framebuffer on my 712 no longer works correctly, if I enable any of the Tux Penguin logos in my kernel. In fact, among 2.6 kernels, 2.6.4 was the only time it worked properly. I'll describe what I saw in both cases: 1) 2.6.4 The PA-RISC Tux appears. Everything within the lines it occupies is a clean pitch black. Bootup messages start right below the penguin and scroll down from that point on. The penguin remains unaffected for as long as nothing affects framebuffer operation (until I run fonty to put ISO-8859-1 fonts on console). 2) all 2.6.x since 2.6.5 The PA-RISC Tux appears. Everything within the lines it occupies is a clean pitch black. Bootup messages start on the last line of the penguin, overlaping its legs. Messages up to Gecko-style soft power switch enabled. scroll on below. Messages following that appear on the feet of the penguin again and are all printed there, without scrolling down. Once the INIT: version 2.86 message appears at that location, things magically resume a few lines below the powerswitch kernel message, starting with the Setting disc parameters: done. message and scroll down, eventually making the penguin scroll off-screen. -- Martin-Éric Racine, ICT Consultant http://www.iki.fi/q-funk/
