Hello,
I've noticed in several versions of 2.6.15 that VESA fb console seems
completely broken : it draws screen in several very slow steps, making
the whole display almos unusable. And it crashes *very* often, for
example when switching to X. The computer is complety locked, and
doesn't even respond to SysRQ.
I guess it is quite trivial to reproduce, the difference with 2.6.14 is
immediately visible.
I use vga=0x31B as boot param.
Attached is .config.
Thanks in advance for any info on this...
--
DW
Damien Wyart wrote:
> Hello,
>
> I've noticed in several versions of 2.6.15 that VESA fb console seems
> completely broken : it draws screen in several very slow steps, making
> the whole display almos unusable. And it crashes *very* often, for
> example when switching to X. The computer is complety locked, and
> doesn't even respond to SysRQ.
>
> I guess it is quite trivial to reproduce, the difference with 2.6.14 is
> immediately visible.
>
> I use vga=0x31B as boot param.
>
Try booting with:
vga=0x31b video=vesafb:mtrr:3
or
vga=0x31b video=vesafb:ypan,mtrr:3
Tony
> > I've noticed in several versions of 2.6.15 that VESA fb console
> > seems completely broken : it draws screen in several very slow
> > steps, making the whole display almos unusable. And it crashes
> > *very* often, for example when switching to X. The computer is
> > complety locked, and doesn't even respond to SysRQ.
> > I use vga=0x31B as boot param.
* "Antonino A. Daplas" <[email protected]> [051122 01:28]:
> Try booting with:
> vga=0x31b video=vesafb:mtrr:3
Thanks, this works fine with this param and also without any video=
param. I had a default video=vesafb:mtrr:2 in my grub conf file because
of mtrr problems a few kernel versions earlier (had been discussed
extensively on this list). This setting doesn't work well in 2.6.15.
--
Damien
Damien Wyart <[email protected]> wrote:
>
> > > I've noticed in several versions of 2.6.15 that VESA fb console
> > > seems completely broken : it draws screen in several very slow
> > > steps, making the whole display almos unusable. And it crashes
> > > *very* often, for example when switching to X. The computer is
> > > complety locked, and doesn't even respond to SysRQ.
>
> > > I use vga=0x31B as boot param.
>
> * "Antonino A. Daplas" <[email protected]> [051122 01:28]:
>
> > Try booting with:
> > vga=0x31b video=vesafb:mtrr:3
>
> Thanks, this works fine with this param and also without any video=
> param. I had a default video=vesafb:mtrr:2 in my grub conf file because
> of mtrr problems a few kernel versions earlier (had been discussed
> extensively on this list). This setting doesn't work well in 2.6.15.
>
Does 2.6.15-rc? work OK without any special boot options? (We want it to..)
Andrew Morton wrote:
> Damien Wyart <[email protected]> wrote:
>>>> I've noticed in several versions of 2.6.15 that VESA fb console
>>>> seems completely broken : it draws screen in several very slow
>>>> steps, making the whole display almos unusable. And it crashes
>>>> *very* often, for example when switching to X. The computer is
>>>> complety locked, and doesn't even respond to SysRQ.
>>>> I use vga=0x31B as boot param.
>> * "Antonino A. Daplas" <[email protected]> [051122 01:28]:
>>
>>> Try booting with:
>>> vga=0x31b video=vesafb:mtrr:3
>> Thanks, this works fine with this param and also without any video=
>> param. I had a default video=vesafb:mtrr:2 in my grub conf file because
>> of mtrr problems a few kernel versions earlier (had been discussed
>> extensively on this list). This setting doesn't work well in 2.6.15.
>>
>
> Does 2.6.15-rc? work OK without any special boot options? (We want it to..)
>
>From what I understand, before this, he needs video=vesafb:mtrr:2. (Because
his machine defaults to write-back mtrr instead of write-combining). Now it
works without any special boot options because I made vesafb default to
nomtrr because of problems like this and conflicts with X/DRI.
Tony
> > > > Try booting with: vga=0x31b video=vesafb:mtrr:3
> > > Thanks, this works fine with this param and also without any
> > > video= param. I had a default video=vesafb:mtrr:2 in my grub conf
> > > file because of mtrr problems a few kernel versions earlier (had
> > > been discussed extensively on this list). This setting doesn't
> > > work well in 2.6.15.
> > Does 2.6.15-rc? work OK without any special boot options? (We want it to..)
* Antonino A. Daplas <[email protected]> [2005-11-23 08:32]:
> From what I understand, before this, he needs video=vesafb:mtrr:2.
> (Because his machine defaults to write-back mtrr instead of
> write-combining). Now it works without any special boot options
> because I made vesafb default to nomtrr because of problems like this
> and conflicts with X/DRI.
Exactly, I confirm that boot is ok without any special boot option.
--
Damien
Antonino A. Daplas wrote:
> Andrew Morton wrote:
>
>>Damien Wyart <[email protected]> wrote:
>>
>>>>>I've noticed in several versions of 2.6.15 that VESA fb console
>>>>>seems completely broken : it draws screen in several very slow
>>>>>steps, making the whole display almos unusable. And it crashes
>>>>>*very* often, for example when switching to X. The computer is
>>>>>complety locked, and doesn't even respond to SysRQ.
>>>>>I use vga=0x31B as boot param.
>>>
>>>* "Antonino A. Daplas" <[email protected]> [051122 01:28]:
>>>
>>>
>>>>Try booting with:
>>>>vga=0x31b video=vesafb:mtrr:3
>>>
>>>Thanks, this works fine with this param and also without any video=
>>>param. I had a default video=vesafb:mtrr:2 in my grub conf file because
>>>of mtrr problems a few kernel versions earlier (had been discussed
>>>extensively on this list). This setting doesn't work well in 2.6.15.
>>>
>>
>>Does 2.6.15-rc? work OK without any special boot options? (We want it to..)
>>
>
>
> From what I understand, before this, he needs video=vesafb:mtrr:2. (Because
> his machine defaults to write-back mtrr instead of write-combining). Now it
> works without any special boot options because I made vesafb default to
> nomtrr because of problems like this and conflicts with X/DRI.
>
Thank you, I bet this fixes a problem I was having with a system which
sometimes came up with video problems unless I used an mtrr parameter.
--
-bill davidsen ([email protected])
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me