Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-11-01 Thread Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 1 Nov 2005 07:14:45 +0100 Erik van Konijnenburg [EMAIL PROTECTED] wrote: On Mon, Oct 31, 2005 at 10:42:13AM +0100, Jonas Smedegaard wrote: On Mon, 31 Oct 2005 00:08:24 + Richard Burton [EMAIL PROTECTED] wrote: So, I have a

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-11-01 Thread Erik van Konijnenburg
On Tue, Nov 01, 2005 at 12:39:13PM +0100, Jonas Smedegaard wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 1 Nov 2005 07:14:45 +0100 Erik van Konijnenburg [EMAIL PROTECTED] wrote: On Mon, Oct 31, 2005 at 10:42:13AM +0100, Jonas Smedegaard wrote: On Mon, 31 Oct 2005

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-31 Thread Richard Burton
As Sven said vesafb isn't a module at 2.6.14. So for =2.6.14 you need both, for 2.6.14 you only need to add fbcon to the conf file. I'm sure you all spotted it - there is a slight error in the above statement, so for the record it should read: As Sven said vesafb isn't a module at 2.6.14. So

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-31 Thread Horms
On Mon, Oct 31, 2005 at 07:57:18AM +0100, Sven Luther wrote: On Mon, Oct 31, 2005 at 10:57:54AM +0900, Horms wrote: Vesafb is no more modular now, and should either have been dropped fully or builtin, please check the config file. As the driver is no longer modular it is now built

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-31 Thread Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 31 Oct 2005 00:08:24 + Richard Burton [EMAIL PROTECTED] wrote: So, I have a workaround. Not sure how this should be fixed permanently though? Easiest way would seem to be to change the yaird Default.conf, but I don't know if that's the

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-31 Thread Sven Luther
On Mon, Oct 31, 2005 at 04:43:57PM +0900, Horms wrote: On Mon, Oct 31, 2005 at 07:57:18AM +0100, Sven Luther wrote: On Mon, Oct 31, 2005 at 10:57:54AM +0900, Horms wrote: Vesafb is no more modular now, and should either have been dropped fully or builtin, please check the config

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-31 Thread Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 31 Oct 2005 16:43:57 +0900 Horms [EMAIL PROTECTED] wrote: The reason that it has been changed from modular to builtin, is that making it modular was a somewhat problematic patch. I hope we can find a solution that doesn't lead us

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-31 Thread Horms
On Mon, Oct 31, 2005 at 07:44:42AM +, Richard Burton wrote: As Sven said vesafb isn't a module at 2.6.14. So for =2.6.14 you need both, for 2.6.14 you only need to add fbcon to the conf file. I'm sure you all spotted it - there is a slight error in the above statement, so for the

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-31 Thread Horms
On Mon, Oct 31, 2005 at 05:31:03PM +0100, Jonas Smedegaard wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 31 Oct 2005 16:43:57 +0900 Horms [EMAIL PROTECTED] wrote: The reason that it has been changed from modular to builtin, is that making it modular was a somewhat

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-31 Thread Erik van Konijnenburg
On Mon, Oct 31, 2005 at 10:42:13AM +0100, Jonas Smedegaard wrote: On Mon, 31 Oct 2005 00:08:24 + Richard Burton [EMAIL PROTECTED] wrote: So, I have a workaround. Not sure how this should be fixed permanently though? Easiest way would seem to be to change the yaird Default.conf, but I

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-30 Thread Richard Burton
This could be changes to video drivers in the kernel. Please describe your graphics card used. Oops, I did intened to mention that. It's an Nvidia GeForce 6600GT 128MB (generic unbranded reference board). Please try the following: 1) add ramdisk = /usr/sbin/mkinitrd.yaird to

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-30 Thread Richard Burton
Nvidia. Ok (or ok is perhaps an exageration: problems with this specific hardware vendor is not really a surprise to me...) Yeah, but it plays native Linux Quake 4 very nicely! You did remember to uninstall yaird before regenerating the ramdisk? Yep, and to confirm it I checked the size of

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-30 Thread Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 30 Oct 2005 22:22:44 + Richard Burton [EMAIL PROTECTED] wrote: Richard: Are you ready for some more geeky tests? Always ;-) :-) So if you could boot an old kernel with initrd ramdisk and kernel options init=/bin/sh rw, and run

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-30 Thread Sven Luther
On Mon, Oct 31, 2005 at 12:13:30AM +0100, Jonas Smedegaard wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 30 Oct 2005 22:22:44 + Richard Burton [EMAIL PROTECTED] wrote: Richard: Are you ready for some more geeky tests? Always ;-) :-) So if you could boot

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-30 Thread Richard Burton
Try editing /etc/yaird/Default.cfg and add the following: MODULE vesafb Ok, that got the vesafb loaded, but that didn't give me video. Added MODULE fbcon as well and that did the job. This testing was all on the 2.6.12. As Sven said vesafb isn't a module at 2.6.14. So for =2.6.14 you need

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-30 Thread Erik van Konijnenburg
On Sun, Oct 30, 2005 at 10:21:39PM +0100, Jonas Smedegaard wrote: On Sun, 30 Oct 2005 15:25:33 + Richard Burton [EMAIL PROTECTED] wrote: This could be changes to video drivers in the kernel. Please describe your graphics card used. Oops, I did intened to mention that. It's an

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-30 Thread Aurelien Jarno
Jonas Smedegaard a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 30 Oct 2005 15:25:33 + Richard Burton [EMAIL PROTECTED] wrote: This could be changes to video drivers in the kernel. Please describe your graphics card used. Oops, I did intened to mention that. It's an

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-30 Thread Aurelien Jarno
Richard Burton a écrit : Try editing /etc/yaird/Default.cfg and add the following: MODULE vesafb Ok, that got the vesafb loaded, but that didn't give me video. Added MODULE fbcon as well and that did the job. This testing was all on the 2.6.12. As Sven said vesafb isn't a module at

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-30 Thread Horms
On Mon, Oct 31, 2005 at 12:45:54AM +0100, Sven Luther wrote: On Mon, Oct 31, 2005 at 12:13:30AM +0100, Jonas Smedegaard wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 30 Oct 2005 22:22:44 + Richard Burton [EMAIL PROTECTED] wrote: Richard: Are you ready for some

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-30 Thread Sven Luther
On Mon, Oct 31, 2005 at 10:57:54AM +0900, Horms wrote: Vesafb is no more modular now, and should either have been dropped fully or builtin, please check the config file. As the driver is no longer modular it is now built into the kernel on all i386 and amd64 architectures. It is not

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-30 Thread Sven Luther
On Mon, Oct 31, 2005 at 01:34:49AM +0100, Erik van Konijnenburg wrote: Just a quick note that there's nothing in yaird 0.0.11 tarball to support vga=... This will probably require an extra module in the config file, vesafb or so, plus an equivalence to a kernel define (I seem to remember