Talk:ATI Mobility Radeon X1400 - Revision history

Vyrtualx: /* framebuffer at 1680x1050? */

2008-03-25T06:35:24Z

‎framebuffer at 1680x1050?

Jescombe: /* framebuffer at 1680x1050? */

2007-07-19T16:14:33Z

‎framebuffer at 1680x1050?

Mar: /* framebuffer at 1680x1050? */

2007-05-18T11:11:39Z

‎framebuffer at 1680x1050?

Zhenech: /* framebuffer at 1680x1050? */

2007-05-15T13:44:53Z

‎framebuffer at 1680x1050?

Zhenech: /* framebuffer at 1680x1050? */

2007-05-15T12:39:02Z

‎framebuffer at 1680x1050?

Mar: /* framebuffer at 1680x1050? */

2007-05-15T10:57:37Z

‎framebuffer at 1680x1050?

Jescombe: /* framebuffer at 1680x1050? */

2006-08-28T13:40:07Z

‎framebuffer at 1680x1050?

Zhenech at 07:58, 28 August 2006

2006-08-28T07:58:39Z

New page

== 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 [http://dev.gentoo.org/~spock/projects/vesafb-tng/ 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)

← Older revision		Revision as of 06:35, 25 March 2008
Line 1:		Line 1:
		+	Hi -
		+	I'm having major trouble installing linux on my T60 intel core 2 duo with ati mob. radeon x1400. Here are the issues i encountered:
		+	1. Failure to partition my hard drive (either from text installation nor with partition magic 7)
		+	2. Installation freezes with screen/resolution error, stating it will restart within 2 minutes - same with Ubuntu 7.1 and Fedora 8
		+	3. Installation with Alternate installation of ubuntu 7.10 stopped at partition b/c it cannot follow through with the partition (error)
		+	4. Fedora 8 installation DVD does not work but Live CD does load into the Fedora Live desktop. Though when I tried to install it from here, I still ge the error with partition.
		+
		+	Please give me any kind of input/suggestions or point me to the right forum where I can read more into it. Thank you so much!
		+	===========================================================================
		+
		+
	== framebuffer at 1680x1050? ==		== framebuffer at 1680x1050? ==
	hey guys - did anyone of you get the framebuffer to 1680x1050?		hey guys - did anyone of you get the framebuffer to 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)
 ::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.

← Older revision		Revision as of 11:11, 18 May 2007
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.

← Older revision		Revision as of 13:44, 15 May 2007
Line 12:		Line 12:
	Use lower color depth -- just added an entry into main article i use 1400x1050 and highcolor (16bit)		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? --[[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)

← Older revision		Revision as of 12:39, 15 May 2007
Line 11:		Line 11:
	----		----
	Use lower color depth -- just added an entry into main article i use 1400x1050 and highcolor (16bit)		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? --[[User:Zhenech\|Zhenech]] 14:39, 15 May 2007 (CEST)

← Older revision		Revision as of 10:57, 15 May 2007
Line 8:		Line 8:
	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.		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.
	--[[User:Jescombe\|Jescombe]] 15:40, 28 August 2006 (CEST)		--[[User:Jescombe\|Jescombe]] 15:40, 28 August 2006 (CEST)
		+
		+	----
		+	Use lower color depth -- just added an entry into main article i use 1400x1050 and highcolor (16bit)

← Older revision		Revision as of 13:40, 28 August 2006
Line 4:		Line 4:
	maybe with vesafb-tng from [http://dev.gentoo.org/~spock/projects/vesafb-tng/ dev.gentoo.org/~spock]? the patch fails here with 2.6.16 and 2.6.17 :(		maybe with vesafb-tng from [http://dev.gentoo.org/~spock/projects/vesafb-tng/ 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)		(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.
		+	--[[User:Jescombe\|Jescombe]] 15:40, 28 August 2006 (CEST)