Re: [gentoo-user] Framebuffer issue in 2.6.1
Downloaded right from www.kernel.org . - Original Message - From: Alan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, January 10, 2004 2:03 AM Subject: Re: [gentoo-user] Framebuffer issue in 2.6.1 On Fri, Jan 09, 2004 at 02:39:01PM -0800, Mark Knecht wrote: Hello everybody! I decided to give a try to the new 2.6.1 kernel. It was released as stable just a few days ago. emerge what-exactly? I was going to try this out this weekend. Kernel 2.6.1 can probably be grabbed via emerge development-sources -- Alan [EMAIL PROTECTED] - http://arcterex.net There are only 3 real sports: bull-fighting, car racing and mountain climbing. All the others are mere games.-- Hemingway -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Framebuffer issue in 2.6.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 10 January 2004 01:03, Alan wrote: Kernel 2.6.1 can probably be grabbed via emerge development-sources 2.6.1 is still, annoyingly, marked as ~x86 - -- Mike Williams -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE//9LvInuLMrk7bIwRAolsAJ4hdw4Htt0EVOTzIXDF+D1N/dCj6wCggeKp 2fcn/plpyVhPnLP2c4WZh/M= =i58Q -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Framebuffer issue in 2.6.1
Thank your very much!! The console is now colorful and properly sized. JZidar - Original Message - From: Bill Roberts [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, January 10, 2004 12:39 AM Subject: Re: [gentoo-user] Framebuffer issue in 2.6.1 On 23:27 Fri 09 Jan , Jernej Zidar wrote: In 2.4.22 I used a framebuffer (I hope this is the right term) console (no X Co.) the size 1024*768 with 32 bpp colors. In 2.6.1 I'm not able to get it. I use this setting in lilo: vga=792. If I boot 2.6.1 with this options nothing shows on the screen, although the system boots normally. If I set the line to vga=normal the new kernel boots normally. The system log shows that there's a difference in mapping the memory. The old kernel maps it to address 0xf880b000, while the new one maps it to 0xf880. Framebuffer works nicely for me in 2.6.1. The key is using getting the kernel settings right in menuconfig, in particular, use the vesa setting, not the specialized ones. See http://forums.gentoo.org/viewtopic.php?t=49036highlight=framebuffer+howto+2+6 for complete details. -- Bill Roberts -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
[gentoo-user] Re: [normal] Re: [gentoo-user] Framebuffer issue in 2.6.1
Hi Mike, 2.6.1 is still, annoyingly, marked as ~x86 you can emerge gentoo-dev-sources to get 2.6.1 brgds, Marc -- [EMAIL PROTECTED] mailing list
[gentoo-user] Framebuffer issue in 2.6.1
Hello everybody! I decided to give a try to the new 2.6.1 kernel. It was released as stable just a few days ago. As far as I have tried it so far it feels much more faster than the 2.4.22 I was using before, however there's an issue I'm not able to overcome. In 2.4.22 I used a framebuffer (I hope this is the right term) console (no X Co.) the size 1024*768 with 32 bpp colors. In 2.6.1 I'm not able to get it. I use this setting in lilo: vga=792. If I boot 2.6.1 with this options nothing shows on the screen, although the system boots normally. If I set the line to vga=normal the new kernel boots normally. The system log shows that there's a difference in mapping the memory. The old kernel maps it to address 0xf880b000, while the new one maps it to 0xf880. Is this a kernel issue or a specific setting to be passed to lilo at boot time? thanks for any advice, JZidar -- [EMAIL PROTECTED] mailing list
RE: [gentoo-user] Framebuffer issue in 2.6.1
Hello everybody! I decided to give a try to the new 2.6.1 kernel. It was released as stable just a few days ago. emerge what-exactly? I was going to try this out this weekend. Thanks, Mark -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Framebuffer issue in 2.6.1
On 23:27 Fri 09 Jan , Jernej Zidar wrote: In 2.4.22 I used a framebuffer (I hope this is the right term) console (no X Co.) the size 1024*768 with 32 bpp colors. In 2.6.1 I'm not able to get it. I use this setting in lilo: vga=792. If I boot 2.6.1 with this options nothing shows on the screen, although the system boots normally. If I set the line to vga=normal the new kernel boots normally. The system log shows that there's a difference in mapping the memory. The old kernel maps it to address 0xf880b000, while the new one maps it to 0xf880. Framebuffer works nicely for me in 2.6.1. The key is using getting the kernel settings right in menuconfig, in particular, use the vesa setting, not the specialized ones. See http://forums.gentoo.org/viewtopic.php?t=49036highlight=framebuffer+howto+2+6 for complete details. -- Bill Roberts -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Framebuffer issue in 2.6.1
On Fri, Jan 09, 2004 at 02:39:01PM -0800, Mark Knecht wrote: Hello everybody! I decided to give a try to the new 2.6.1 kernel. It was released as stable just a few days ago. emerge what-exactly? I was going to try this out this weekend. Kernel 2.6.1 can probably be grabbed via emerge development-sources -- Alan [EMAIL PROTECTED] - http://arcterex.net There are only 3 real sports: bull-fighting, car racing and mountain climbing. All the others are mere games.-- Hemingway -- [EMAIL PROTECTED] mailing list