On Fri, Sep 5, 2008 at 3:35 PM, Salva Ferrer <email address hidden> wrote:
> Same for me, Intrepid uses the new uvesafb for the same function so vesafb
> can be blacklisted again. I disabled my vesafb and let uvesafb do the job
> and everything went fine.
> Just make sure that v86d package is installed, in my case it was not and
> had to do it manually.
>
>
> On Fri, Sep 5, 2008 at 12:39 PM, Shriramana Sharma <email address hidden>wrote:
>
>> Trying the latest Intrepid kernel with the following packages:
>>
>> linux_2.6.27.2.2_i386.deb
>> linux-generic_2.6.27.2.2_i386.deb
>> linux-image_2.6.27.2.2_i386.deb
>> linux-image-2.6.27-2-generic_2.6.27-2.3_i386.deb
>> linux-image-generic_2.6.27.2.2_i386.deb
>> linux-restricted-modules_2.6.27.2.2_i386.deb
>> linux-restricted-modules-2.6.27-2-generic_2.6.27-2.2_i386.deb
>> linux-restricted-modules-common_2.6.27-2.2_all.deb
>> linux-restricted-modules-generic_2.6.27.2.2_i386.deb
>>
>> and I am not getting my tty-s when using vesafb. Is there a regression
>> and should this bug be reopened?
>>
>> --
>> Blank ttys when using vesafb (vga=xxx)
>> https://bugs.launchpad.net/bugs/129910
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>
I am attaching another bug with uvesafb that may apear for those switching /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/246269
to intrepid, just a reference:
https:/
On Fri, Sep 5, 2008 at 3:35 PM, Salva Ferrer <email address hidden> wrote:
> Same for me, Intrepid uses the new uvesafb for the same function so vesafb 6.27.2. 2_i386. deb 2.6.27. 2.2_i386. deb 2.6.27. 2.2_i386. deb 2.6.27- 2-generic_ 2.6.27- 2.3_i386. deb generic_ 2.6.27. 2.2_i386. deb d-modules_ 2.6.27. 2.2_i386. deb d-modules- 2.6.27- 2-generic_ 2.6.27- 2.2_i386. deb d-modules- common_ 2.6.27- 2.2_all. deb d-modules- generic_ 2.6.27. 2.2_i386. deb /bugs.launchpad .net/bugs/ 129910
> can be blacklisted again. I disabled my vesafb and let uvesafb do the job
> and everything went fine.
> Just make sure that v86d package is installed, in my case it was not and
> had to do it manually.
>
>
> On Fri, Sep 5, 2008 at 12:39 PM, Shriramana Sharma <email address hidden>wrote:
>
>> Trying the latest Intrepid kernel with the following packages:
>>
>> linux_2.
>> linux-generic_
>> linux-image_
>> linux-image-
>> linux-image-
>> linux-restricte
>> linux-restricte
>> linux-restricte
>> linux-restricte
>>
>> and I am not getting my tty-s when using vesafb. Is there a regression
>> and should this bug be reopened?
>>
>> --
>> Blank ttys when using vesafb (vga=xxx)
>> https:/
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>