Re: Framebuffer on 2.6.3
On Thu, Mar 18, 2004 at 08:32:24PM +0200, Mugurel Tudor wrote: > I have a Debian Sid installed on my laptop, and dramebuffer is kinda > vital for me (nice console in native resolution). All worked fine in > 2.6.0, but when I installed 2.6.3, the framebuffer is not functioning > anymore (I can not see anything when it's booting). From what I've > discovered, vesafb wasn't included in initrd. So I recreated initrd with > vesafb, checked with a "strings initrd.img | grep vesafb" that my vesafb > driver is indeed in the initrd, but the problem still persist. > > Have anyone experienced something similar ? Yes, I've seen the same thing recently. I changed out my graphics card recently (It's now an Matrox g400) and I thought it was THAT, but now that you mention it, that card worked fine with 2.6.2. I don't know how to fix it (I don't use the console much on that box), I wish I had more help for you.
Re: Framebuffer on 2.6.3
On Thu, Mar 18, 2004 at 08:32:24PM +0200, Mugurel Tudor wrote: > I have a Debian Sid installed on my laptop, and dramebuffer is kinda > vital for me (nice console in native resolution). All worked fine in > 2.6.0, but when I installed 2.6.3, the framebuffer is not functioning > anymore (I can not see anything when it's booting). From what I've > discovered, vesafb wasn't included in initrd. So I recreated initrd with > vesafb, checked with a "strings initrd.img | grep vesafb" that my vesafb > driver is indeed in the initrd, but the problem still persist. > > Have anyone experienced something similar ? Yes, I've seen the same thing recently. I changed out my graphics card recently (It's now an Matrox g400) and I thought it was THAT, but now that you mention it, that card worked fine with 2.6.2. I don't know how to fix it (I don't use the console much on that box), I wish I had more help for you. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Framebuffer on 2.6.3
On Jo, 2004-03-18 at 21:04, Anders Ellenshøj Andersen wrote: > If you just switched from 2.4 you need to enable the new framebuffer in 2.6 > as > the config has changed. > No, I've used 2.6.0 before. > You need to enable framebuffer. Then select the appropriate driver and > finally > you must also enable CONFIG_FRAMEBUFFER_CONSOLE in the console display driver > support section. > I didn' t compile 2.6.3 myself, i've installed it allready compiled from sid repository, and vesafb is compiled as a module by debian (and it's not in the intrd.img by default, like in 2.6.0). > Anders E. Andersen > > -- > This email was generated using KMail from KDE 3.1.5 on Debian GNU/Linux -- Mugurel Tudor ([EMAIL PROTECTED]) Linux Registered User: 212231 In God we Trust. All others must have valid md5 checksums. signature.asc Description: This is a digitally signed message part
Re: Framebuffer on 2.6.3
On Thursday 18 March 2004 19:32, Mugurel Tudor wrote: > 2.6.0, but when I installed 2.6.3, the framebuffer is not functioning > anymore (I can not see anything when it's booting). From what I've > Have anyone experienced something similar ? If you just switched from 2.4 you need to enable the new framebuffer in 2.6 as the config has changed. You need to enable framebuffer. Then select the appropriate driver and finally you must also enable CONFIG_FRAMEBUFFER_CONSOLE in the console display driver support section. Anders E. Andersen -- This email was generated using KMail from KDE 3.1.5 on Debian GNU/Linux
Re: Framebuffer on 2.6.3
On Jo, 2004-03-18 at 21:04, Anders EllenshÃj Andersen wrote: > If you just switched from 2.4 you need to enable the new framebuffer in 2.6 as > the config has changed. > No, I've used 2.6.0 before. > You need to enable framebuffer. Then select the appropriate driver and finally > you must also enable CONFIG_FRAMEBUFFER_CONSOLE in the console display driver > support section. > I didn' t compile 2.6.3 myself, i've installed it allready compiled from sid repository, and vesafb is compiled as a module by debian (and it's not in the intrd.img by default, like in 2.6.0). > Anders E. Andersen > > -- > This email was generated using KMail from KDE 3.1.5 on Debian GNU/Linux -- Mugurel Tudor ([EMAIL PROTECTED]) Linux Registered User: 212231 In God we Trust. All others must have valid md5 checksums. signature.asc Description: This is a digitally signed message part
Framebuffer on 2.6.3
I have a Debian Sid installed on my laptop, and dramebuffer is kinda vital for me (nice console in native resolution). All worked fine in 2.6.0, but when I installed 2.6.3, the framebuffer is not functioning anymore (I can not see anything when it's booting). From what I've discovered, vesafb wasn't included in initrd. So I recreated initrd with vesafb, checked with a "strings initrd.img | grep vesafb" that my vesafb driver is indeed in the initrd, but the problem still persist. Have anyone experienced something similar ? -- Mugurel Tudor ([EMAIL PROTECTED]) Linux Registered User: 212231 In God we Trust. All others must have valid md5 checksums. signature.asc Description: This is a digitally signed message part
Re: Framebuffer on 2.6.3
On Thursday 18 March 2004 19:32, Mugurel Tudor wrote: > 2.6.0, but when I installed 2.6.3, the framebuffer is not functioning > anymore (I can not see anything when it's booting). From what I've > Have anyone experienced something similar ? If you just switched from 2.4 you need to enable the new framebuffer in 2.6 as the config has changed. You need to enable framebuffer. Then select the appropriate driver and finally you must also enable CONFIG_FRAMEBUFFER_CONSOLE in the console display driver support section. Anders E. Andersen -- This email was generated using KMail from KDE 3.1.5 on Debian GNU/Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Framebuffer on 2.6.3
I have a Debian Sid installed on my laptop, and dramebuffer is kinda vital for me (nice console in native resolution). All worked fine in 2.6.0, but when I installed 2.6.3, the framebuffer is not functioning anymore (I can not see anything when it's booting). From what I've discovered, vesafb wasn't included in initrd. So I recreated initrd with vesafb, checked with a "strings initrd.img | grep vesafb" that my vesafb driver is indeed in the initrd, but the problem still persist. Have anyone experienced something similar ? -- Mugurel Tudor ([EMAIL PROTECTED]) Linux Registered User: 212231 In God we Trust. All others must have valid md5 checksums. signature.asc Description: This is a digitally signed message part
