Re: No text mode display after grub
On 2007-03-21 @ 19:12:39 (week 12) Florian Kulzer wrote: > Let me just quickly correct my earlier statement: I think the Debian > Linux source packages have the "modular vesafb" option removed anyway > because it caused trouble in the past. I half remembered this and then I > mixed things up a bit when I wrote the previous mail. You probably got a > "module not found" error. I don't think I saw "module not found" in the log. I did see another one though: Uhhuh. NMI received for unknown reason a0 on CPU 0 That's what I got when X slowed down to a sloth's pace. I haven't got the faintest idea what it means. I'll look it up this weekend. > If you still want to try out features of the 2.6.20 kernel without much > hassle then you can use one of the Debian Linux images which are > available if you add this to your /etc/apt/sources.list: > > deb http://kernel-archive.buildserver.net/debian-kernel trunk main That's great. I didn't know about that one. Thanks for the heads-up. Grx HdV -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: No text mode display after grub
On Wed, Mar 21, 2007 at 17:10:56 +, J.A. de Vries wrote: > On 2007-03-04 @ 19:43:57 (week 09) Florian Kulzer wrote: > > > I think this might be related to the framebuffer driver. > > Agreed. > > > You can try to "modprobe vesafb" (or whatever fb module is suitable > > for your graphics card) from an X root console and see if this helps. > > I am sorry to say it didn't. Let me just quickly correct my earlier statement: I think the Debian Linux source packages have the "modular vesafb" option removed anyway because it caused trouble in the past. I half remembered this and then I mixed things up a bit when I wrote the previous mail. You probably got a "module not found" error. > > It might be necessary to compile vesafb (or ...fb) statically into the > > kernel. > > Tried that after you suggested it, but to no avail. > > Meanwhile I've given up. I am now using the pre-build 2.6.18-4 kernel, > which works like a charm. If you still want to try out features of the 2.6.20 kernel without much hassle then you can use one of the Debian Linux images which are available if you add this to your /etc/apt/sources.list: deb http://kernel-archive.buildserver.net/debian-kernel trunk main I use the 2.6.20-1-amd64 image from that source to have 3D acceleration for my Intel 82Q963/Q965 graphics controller, and this kernel works for me without problems. The 2.6.20 source package with Debian patches are also available, of course, if you want to compile yourself from Debian sources. More info about these kernel snapshots (and the archive signing key) can be found here: http://wiki.debian.org/DebianKernel > Thanks for trying to help. It is appreciated. > > Grx HdV -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: No text mode display after grub
On 2007-03-04 @ 19:43:57 (week 09) Florian Kulzer wrote: > I think this might be related to the framebuffer driver. Agreed. > You can try to "modprobe vesafb" (or whatever fb module is suitable > for your graphics card) from an X root console and see if this helps. I am sorry to say it didn't. > It might be necessary to compile vesafb (or ...fb) statically into the > kernel. Tried that after you suggested it, but to no avail. Meanwhile I've given up. I am now using the pre-build 2.6.18-4 kernel, which works like a charm. Thanks for trying to help. It is appreciated. Grx HdV -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: No text mode display after grub
On 2007-03-05 @ 01:48:40 (week 10) Chris Bannister wrote: Sorry to get back only now. Haven't been keeping up with my mail due to an overly full agenda and todo list. > Is there any particular reason you need a later kernel? Other than wanting to try out a couple of new features no, not really. > You could compare the kernel configs. If they are *too* different then > does compiling say a 2.6.18 kernel with the same/similar configs work? Nothing too different between them. I am probably overlooking something. Up til now I've never had any problems with my home-made kernels. However, I do tend to strip them down quite aggressively. Changes are I did something that causes problems only for this particular setup. Meanwhile I have tried a couple of things. First I noticed I hadn't enabled the framebuffer. After I did that I did get back the console and after some tweaking I even managed to get X running too, but only in VESA mode and only for a very short time. After it starts up it gets progressively slower until it grinds down to a full stop. I tried to enable the radeon driver, but the same happened. Weirder still, if I try to install the ati driver from the console the slowing down starts as soon as the installer begins showing the (text-mode) dialogs (not before). Ah well, I've given up and returned to the comfort of the pre-compiled Debian GNU/Linux kernel (2.6.18-4). Everything is fine now. Though it still bugs me I didn't find out what I did wrong... Thanks for trying to help! Grx HdV -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: No text mode display after grub
On 2007-02-28 @ 12:49:05 (week 09) Andrew Sackville-West wrote: Sorry to get back only now. Haven't been keeping up with my mail due to an overly full agenda and todo list. > did you try vga=normal? that should at least get you a readable > screen. won't be the best res. I did, but still no console. Meanwhile I have found a workaround, but not a solution to the problem. See my other message in this thread. Thanks for taking the time. Grx HdV -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: No text mode display after grub
On Mon, Mar 05, 2007 at 01:48:40 +1300, Chris Bannister wrote: > On Wed, Feb 28, 2007 at 08:11:36PM +, J.A. de Vries wrote: > > Hi, > > > > My boss gave me a Dell Latitude D810 to use for work so I didn't have to > > use my privately owned Acer Ferrari 4000 anymore. First thing I did was > > install testing on it, which was no problem at all. Next I built a > > 2.6.20.1 kernel (vanilla from kernel.org) and now I have a bit of a > > Is there any particular reason you need a later kernel? > > > strange problem: after I make a selection in the grub menu I see about 2 > > lines printed to the console (they flash by too fast to read, but they > > do not seem to be error messages). After that the screen stays dark > > until kdm starts. Everything else is working like a charm. After logging > > in to X I tried to change to a virtual console and noticed text mode > > won't work there either. Does anyone have an idea what I could do to get > > the text console back? I use it regularly. I tried using the vga=xxx > > option [1] as a boot parameter, but either I can't find the correct > > value for it, or that is not the solution to this problem. > > You could compare the kernel configs. If they are *too* different then > does compiling say a 2.6.18 kernel with the same/similar configs work? I think this might be related to the framebuffer driver. You can try to "modprobe vesafb" (or whatever fb module is suitable for your graphics card) from an X root console and see if this helps. It might be necessary to compile vesafb (or ...fb) statically into the kernel. -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: No text mode display after grub
On Wed, Feb 28, 2007 at 08:11:36PM +, J.A. de Vries wrote: > Hi, > > My boss gave me a Dell Latitude D810 to use for work so I didn't have to > use my privately owned Acer Ferrari 4000 anymore. First thing I did was > install testing on it, which was no problem at all. Next I built a > 2.6.20.1 kernel (vanilla from kernel.org) and now I have a bit of a Is there any particular reason you need a later kernel? > strange problem: after I make a selection in the grub menu I see about 2 > lines printed to the console (they flash by too fast to read, but they > do not seem to be error messages). After that the screen stays dark > until kdm starts. Everything else is working like a charm. After logging > in to X I tried to change to a virtual console and noticed text mode > won't work there either. Does anyone have an idea what I could do to get > the text console back? I use it regularly. I tried using the vga=xxx > option [1] as a boot parameter, but either I can't find the correct > value for it, or that is not the solution to this problem. You could compare the kernel configs. If they are *too* different then does compiling say a 2.6.18 kernel with the same/similar configs work? -- Chris. == Don't forget to check that your /etc/apt/sources.lst entries point to etch and not testing, otherwise you may end up with a broken system once etch goes stable. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: No text mode display after grub
On Wed, Feb 28, 2007 at 08:11:36PM +, J.A. de Vries wrote: > Hi, > > My boss gave me a Dell Latitude D810 to use for work so I didn't have to > use my privately owned Acer Ferrari 4000 anymore. First thing I did was > install testing on it, which was no problem at all. Next I built a > 2.6.20.1 kernel (vanilla from kernel.org) and now I have a bit of a > strange problem: after I make a selection in the grub menu I see about 2 > lines printed to the console (they flash by too fast to read, but they > do not seem to be error messages). After that the screen stays dark > until kdm starts. Everything else is working like a charm. After logging > in to X I tried to change to a virtual console and noticed text mode > won't work there either. Does anyone have an idea what I could do to get > the text console back? I use it regularly. I tried using the vga=xxx > option [1] as a boot parameter, but either I can't find the correct > value for it, or that is not the solution to this problem. did you try vga=normal? that should at least get you a readable screen. won't be the best res. A signature.asc Description: Digital signature
