Difference between revisions of "Talk:ATI Mobility Radeon X1400"
(→framebuffer at 1680x1050?) |
(→framebuffer at 1680x1050?) |
||
| Line 13: | Line 13: | ||
:Hm, which vga-mode is it -- what vga=XXX did you append to your boot-params? --[[User:Zhenech|Zhenech]] 14:39, 15 May 2007 (CEST) | :Hm, which vga-mode is it -- what vga=XXX did you append to your boot-params? --[[User:Zhenech|Zhenech]] 14:39, 15 May 2007 (CEST) | ||
::Well, after googling I found 0x13b, 0x142, 0x145 and 0x148, adding 0x200 and booting -> only 0x145 works and fglrx isn't able to initialize the display afterwards, also tested 0x144 and 0x143 with same results. :( --[[User:Zhenech|Zhenech]] 15:44, 15 May 2007 (CEST) | ::Well, after googling I found 0x13b, 0x142, 0x145 and 0x148, adding 0x200 and booting -> only 0x145 works and fglrx isn't able to initialize the display afterwards, also tested 0x144 and 0x143 with same results. :( --[[User:Zhenech|Zhenech]] 15:44, 15 May 2007 (CEST) | ||
| + | |||
| + | ---- | ||
| + | Sorry, my ignorance. I was talking about the X vesa driver, not the vesafb kernel framebuffer. Better do better reading from now on. :-( I removed the entry from the article. | ||
Revision as of 12:11, 18 May 2007
framebuffer at 1680x1050?
hey guys - did anyone of you get the framebuffer to 1680x1050? vesafb works well with 1280x1024, but not more. maybe with vesafb-tng from dev.gentoo.org/~spock? the patch fails here with 2.6.16 and 2.6.17 :( (yes, I posted this question already to Category_talk:Z61m, but never got a reply there)
I've not been able to get vesafb above 1280x1024 either, and didn't see any screen output from vesafb-tng when I tried it. --Jescombe 15:40, 28 August 2006 (CEST)
Use lower color depth -- just added an entry into main article i use 1400x1050 and highcolor (16bit)
- Hm, which vga-mode is it -- what vga=XXX did you append to your boot-params? --Zhenech 14:39, 15 May 2007 (CEST)
- Well, after googling I found 0x13b, 0x142, 0x145 and 0x148, adding 0x200 and booting -> only 0x145 works and fglrx isn't able to initialize the display afterwards, also tested 0x144 and 0x143 with same results. :( --Zhenech 15:44, 15 May 2007 (CEST)
Sorry, my ignorance. I was talking about the X vesa driver, not the vesafb kernel framebuffer. Better do better reading from now on. :-( I removed the entry from the article.
