| View previous topic :: View next topic |
| Author |
Message |
Ziquet
n00b
Joined: 16 Apr 2004
Posts: 14
Location: Switzerland
|
 Posted: Sun Nov 21, 2004 3:35 pm Post subject: Problem with framebuffer (vesafb-tng) |
 |
|
Hello,
I'm facing a problem with the framebuffer of the latest gentoo-dev-sources series (2.6.9-*). Here is an image that shows my problem:
[img:741debca0e]http://www.borer.name/vesafb-bug-small.png[/img:741debca0e]
This is happening only with the 2.6.9 kernel, with 2.6.8, that I'm currently using, no problem at all. For information, the computer is not locked, it boots correctly and I can access it through ssh, but the display is borked.
My computer is a Compaq evo n800v notebook, and the graphic card is an Ati Radeon mobility M6.
Any help would be greatly appreciated.
Ziq. |
|
| Back to top |
|
 |
Wampas
n00b
Joined: 16 Nov 2004
Posts: 48
|
| Posted: Sun Nov 21, 2004 4:09 pm Post subject: |
|
|
Please can you report the results of these commands (only the line that concerns your radeon card or fglx lines :
and :
About your issue, where did you setup resolution of the screen and load the driver? In the boot loader? Did you setup a default resolution in the kernel next to vesa-tng?
_________________
Fujitsu Amilo 1425 | P-M725 dothan @1.60Ghz | Intel i855PM | 80GB ATA8MB | Radeon Mobility 9700 128M | Intel AC'97 | 512MB
XP1800+ | MSI KT3 Ultra | Leadtek GF4 TI4200 64MB @ 300/550 | AC'97 | 40GB | 1GB DDR
Duron 1100 GF2MX 32MB | 2x40GB| 512MB |
|
| Back to top |
|
|
Ziquet
n00b
Joined: 16 Apr 2004
Posts: 14
Location: Switzerland
|
| Posted: Sun Nov 21, 2004 5:29 pm Post subject: |
|
|
| Code: | icare ~ # lspci -v
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] (prog-if 00 [VGA])
Subsystem: Compaq Computer Corporation: Unknown device 004a
Flags: stepping, 66Mhz, medium devsel, IRQ 11
Memory at 88000000 (32-bit, prefetchable)
I/O ports at 3000 [size=256]
Memory at 80380000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [58] AGP version 2.0
Capabilities: [50] Power Management version 2
|
Concerning fglx I'm not using Ati binary driver, but the one shipped with Xorg.
| Code: | icare ~ # cat /proc/mtrr
reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1
reg01: base=0x88000000 (2176MB), size= 16MB: write-combining, count=1
|
The resolution is selected in the bootloader (video=vesafb:ywrap,mtrr,1400x1050-32@60 splash=silent,theme:craft), but I also setup the default resolution in the kernel (the same as the command line). I've also tried without the mtrr parameter, still the same problem...
Ziq.
--edit--
Here is the output of dmesg, don't know if it might be usefull
| Code: | tux@icare % dmesg | grep vesafb ~
Kernel command line: root=/dev/hda3 hdc=ide-cd video=vesafb:ywrap,1400x1050-32@60 splash=silent,theme:craft
vesafb: ATI Technologies Inc., P7 , 01.00 (OEM: ATI MOBILITY RADEON 7500)
vesafb: VBE version: 2.0
vesafb: protected mode interface info at c000:5687
vesafb: pmi: set display start = c00c571b, set palette = c00c5767
vesafb: pmi: ports = 3010 3016 3054 3038 303c 305c 3000 3004 30b0 30b2 30b4
vesafb: monitor limits: vf = 0 Hz, hf = 0 kHz, clk = 0 MHz
vesafb: mode 1792x1344-32@0 not found
vesafb: mode 1792x1344-32@0 not found
vesafb: mode 1856x1392-32@0 not found
vesafb: mode 1856x1392-32@0 not found
vesafb: mode 1920x1440-32@0 not found
vesafb: mode 1920x1440-32@0 not found
vesafb: scrolling: ywrap using protected mode interface, yres_virtual=2621
vesafb: mode switch failed (eax: 0x14f)
vesafb: framebuffer at 0x88000000, mapped to 0xe0900000, size 16384k
|
|
|
| Back to top |
|
|
Wampas
n00b
Joined: 16 Nov 2004
Posts: 48
|
| Posted: Sun Nov 21, 2004 9:55 pm Post subject: |
|
|
Yes it is useful :
| Code: | icare ~ # cat /proc/mtrr
reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1
reg01: base=0x88000000 (2176MB), size= 16MB: write-combining, count=1 |
First line is your RAM, second one is your video card.
It shows well that when you log on X and switch to xorg drivers, your video RAM isnt initialized properly...
It is a problem with vesa drivers apparently : it needs 16MB video memory and allocate em then when you enter X it doesnt work and your video memory stays low, however i have no clue what RAM your video card has (maybe it is shared memory ?).
But it doesnt solve your issue though... I used tried to use vesa but had some troubles so i gave up and removed vesa (it seemed to be giving more troubles than anything for ati drivers after X loaded.
_________________
Fujitsu Amilo 1425 | P-M725 dothan @1.60Ghz | Intel i855PM | 80GB ATA8MB | Radeon Mobility 9700 128M | Intel AC'97 | 512MB
XP1800+ | MSI KT3 Ultra | Leadtek GF4 TI4200 64MB @ 300/550 | AC'97 | 40GB | 1GB DDR
Duron 1100 GF2MX 32MB | 2x40GB| 512MB |
|
| Back to top |
|
|
Ziquet
n00b
Joined: 16 Apr 2004
Posts: 14
Location: Switzerland
|
| Posted: Mon Nov 22, 2004 9:15 pm Post subject: |
|
|
I believe you on the RAM problem, but the fact is that I event don't have time to start X. I choose my kernel in grub, and then when it activates the framebuffer the whole display is borked, and nothing changes, as it is shown on the photo I have taken.
What is even more interesting is that it works well with 2.6.8 kernel... anyway, I'll stick with this kernel and wait for 2.6.10, perhaps it'll solve my problem...
Thanks for your help. |
|
| Back to top |
|
|
daff
Apprentice
Joined: 02 Jul 2003
Posts: 232
Location: Vienna, Austria
|
| Posted: Sun Jan 09, 2005 4:13 pm Post subject: |
|
|
Just for the record, I have the same problem on my Thinkpad T41p with 2.6.9-gentoo-r13. All resolutions are fine, just 1400x1050 isn't. Everything works with a 2.6.8 kernel, but going back to that is not an option for me. And as for 2.6.10... it seems to introduce more problems than it solves, doesn't it?
_________________
Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
