Fw: Re: disabling VESAFB no longer locks up VT (was Re: 2.4.10-r1 MTRR bug)

Are you folks aware of this lkml thread??

Thanks.

Begin forwarded message:

Date: Fri, 14 Jan 2005 16:50:42 -0800
From: Steve <redacted>
To: Daniel Drake <redacted>
Cc: Andrew Morton <redacted>, linux-kernel@vger.kernel.org
Subject: Re: disabling VESAFB no longer locks up VT (was Re: 2.4.10-r1 MTRR bug)


Daniel Drake wrote:

Hi Andrew,

Andrew Morton wrote:

quoted

Steve [off-list ref] wrote:

quoted

For the Athlon 2100, I get the following outputs and then the VGA 
console is frozen from further output (but it doesn't prevent the 
full bootup into X windows session of which I am able to resume 
normal Linux/X session, but not able to regain any virtual console 
session.)

hm.  Not sure what could have caused that.

This may be a problem in Gentoo's kernels, we offer an experimental 
version of vesafb... 

Disabling the VESAFB resulted in regaining control of the VTs (virtual 
terminals).


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

On Saturday 15 January 2005 09:04, Andrew Morton wrote:

Are you folks aware of this lkml thread??

Thanks.

His lspci shows:

0000:01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 
661/741/760 PCI/AGP VGA Display Adapter (prog-if 00 [VGA])
        Subsystem: Elitegroup Computer Systems: Unknown device 1b13
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 10
        BIST result: 00
        Region 0: Memory at d8000000 (32-bit, prefetchable) 
        Region 1: Memory at e5000000 (32-bit, non-prefetchable) [size=128K]

Does this look strange?  Usually each resource shows both the start address
and resource size. Region 0 does not show the resource size. This is probably
confusing vesafb.

Also, his /proc/iomem shows
...
f000ef6f-f100ef6e : vesafb
...

Besides it not matching the lspci output, the start address is not 4K aligned.

You can try this (no guarantees), tell vesafb the actual amount of RAM the
card has (assuming standard kernel vesafb): 

video=vesafb:vtotal:N

where N = the total amount of Video RAM in MiB

Tony




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt