Fedora Linux Support Community & Resources Center
  #1  
Old 1st June 2012, 11:29 AM
itayshom Offline
Registered User
 
Join Date: Jun 2012
Location: Israel
Posts: 6
linuxfirefox
F17 upgrade: display driver problem (HD4200)

Hello,

Last night I upgraded from F16 to F17 via the preupgrade program.
(Not that everything went smoothly -(grub bug etc.)

Problem is that now the system doesn't detect my graphics card. I have an ATI HD4200 and was using the Gallium driver before, but now the systems falls to VESA driver, and shows maxium resolution of 1280x1024 (and slow graphics) whereas I used to have 1920x1080.

There is no xorg.conf file, nor was there before. (I have no idea what to put there anyway.)

I would appreciate any help.

Itay.
Reply With Quote
  #2  
Old 1st June 2012, 11:36 AM
SlowJet Offline
Registered User
 
Join Date: Jan 2005
Posts: 5,048
linuxfirefox
Re: F17 upgrade: display driver problem (HD4200)

Fedora does not have but a few 3d drivers, like 3, maybe.
Sounds like you need to study up on nvida driver with the dkms modules from a 3rd repo.
There are problaly a dozen how-to threads aound.

SJ
__________________
Do the Math
Reply With Quote
  #3  
Old 1st June 2012, 11:45 AM
itayshom Offline
Registered User
 
Join Date: Jun 2012
Location: Israel
Posts: 6
linuxfirefox
Re: F17 upgrade: display driver problem (HD4200)

I have an ATI card, not an nVidia card....

I just want the 'regular' Gallium driver back.

On System Settings->Displays, it says "Unknown".

Itay.
Reply With Quote
  #4  
Old 1st June 2012, 12:23 PM
SlowJet Offline
Registered User
 
Join Date: Jan 2005
Posts: 5,048
linuxfirefox
Re: F17 upgrade: display driver problem (HD4200)

There is no reverse on the Fedora Machine.

If your xorg did not select one, then alll that remains is the standard vesa drv.

Gallium drv ?

$ rpm -qa xorg-x11-drv\*
xorg-x11-drv-vmware-12.0.2-1.fc17.i686
xorg-x11-drv-synaptics-1.6.1-1.fc17.i686
xorg-x11-drv-ast-0.93.9-6.fc17.i686
xorg-x11-drv-vesa-2.3.1-1.fc17.i686
xorg-x11-drv-ati-6.14.4-5.20120417git0bda305f7.fc17.i686
xorg-x11-drv-nouveau-0.0.16-35.20120306gitf5d1cd2.fc17.i686
xorg-x11-drv-openchrome-0.2.906-1.fc17.i686
xorg-x11-drv-geode-2.11.12-3.fc17.i686
xorg-x11-drv-fbdev-0.4.2-8.fc17.i686
xorg-x11-drv-evdev-2.7.0-2.fc17.i686
xorg-x11-drv-dummy-0.3.5-4.fc17.i686
xorg-x11-drv-cirrus-1.4.0-1.fc17.i686
xorg-x11-drv-wacom-0.14.0-2.fc17.i686
xorg-x11-drv-qxl-0.0.22-0.fc17.i686
xorg-x11-drv-vmmouse-12.8.0-1.fc17.i686
xorg-x11-drv-mga-1.4.13-19.20120104git9223c44a7.fc17.i686
xorg-x11-drv-void-1.4.0-8.fc17.i686
xorg-x11-drv-intel-2.19.0-3.fc17.i686

SJ
__________________
Do the Math
Reply With Quote
  #5  
Old 1st June 2012, 03:14 PM
itayshom Offline
Registered User
 
Join Date: Jun 2012
Location: Israel
Posts: 6
linuxfirefox
Re: F17 upgrade: display driver problem (HD4200)

Gallium is the generic ATI driver, AFAIK.

II also have lots installed:

$ rpm -qa xorg-x11-drv\*
xorg-x11-drv-synaptics-1.6.0-1.fc17.x86_64
xorg-x11-drv-vmware-12.0.2-1.fc17.x86_64
xorg-x11-drv-i740-1.3.2-16.fc17.x86_64
xorg-x11-drv-v4l-0.2.0-20.fc17.x86_64
xorg-x11-drv-savage-2.3.4-1.fc17.x86_64
xorg-x11-drv-apm-1.2.3-15.fc17.x86_64
xorg-x11-drv-s3virge-1.10.4-15.fc17.x86_64
xorg-x11-drv-glint-1.2.7-1.fc17.x86_64
xorg-x11-drv-sis-0.10.4-1.fc17.x86_64
xorg-x11-drv-trident-1.3.4-14.fc17.x86_64
xorg-x11-drv-keyboard-1.6.1-4.fc17.x86_64
xorg-x11-drv-intel-2.19.0-1.fc17.x86_64
xorg-x11-drv-dummy-0.3.5-4.fc17.x86_64
xorg-x11-drv-mach64-6.9.1-1.fc17.x86_64
xorg-x11-drv-mouse-1.7.2-1.fc17.x86_64
xorg-x11-drv-rendition-4.2.4-14.fc17.x86_64
xorg-x11-drv-wacom-0.14.0-2.fc17.x86_64
xorg-x11-drv-mga-1.4.13-19.20120104git9223c44a7.fc17.x86_64
xorg-x11-drv-nv-2.1.18-15.fc17.x86_64
xorg-x11-drv-r128-6.8.2-1.fc17.x86_64
xorg-x11-drv-vesa-2.3.0-15.fc17.x86_64
xorg-x11-drv-openchrome-0.2.906-1.fc17.x86_64
xorg-x11-drv-siliconmotion-1.7.5-9.fc17.x86_64
xorg-x11-drv-i128-1.3.5-1.fc17.x86_64
xorg-x11-drv-fbdev-0.4.2-8.fc17.x86_64
xorg-x11-drv-ati-6.14.4-5.20120417git0bda305f7.fc17.x86_64
xorg-x11-drv-tdfx-1.4.3-18.20120104gitfe60f0ed2.fc17.x86_64
xorg-x11-drv-nouveau-0.0.16-34.20110720gitb806e3f.fc17.x86_64
xorg-x11-drv-void-1.4.0-8.fc17.x86_64
xorg-x11-drv-cirrus-1.3.2-19.fc17.x86_64
xorg-x11-drv-vmmouse-12.8.0-1.fc17.x86_64
xorg-x11-drv-evdev-2.7.0-2.fc17.x86_64
xorg-x11-drv-voodoo-1.2.4-14.fc17.x86_64
xorg-x11-drv-ast-0.93.9-6.fc17.x86_64
xorg-x11-drv-sisusb-0.9.4-13.fc17.x86_64
xorg-x11-drv-qxl-0.0.22-0.fc17.x86_64
xorg-x11-drv-modesetting-0.2.0-1.fc17.x86_64

How does it know which one to choose?
I have a 64bit system by the way.

Thank you .
Itay
Reply With Quote
  #6  
Old 1st June 2012, 03:53 PM
tashirosgt Offline
Registered User
 
Join Date: Aug 2004
Posts: 3,940
linuxfirefox
Re: F17 upgrade: display driver problem (HD4200)

itayshom,

It would help if you provided unambiguous information about how Fedora detects your video card and what module and driver it is using.

This method works in FC 16, so it probably works in FC 17:

Code:
lspci
and look for the line relevant to the video card.

The line probably has "VGA" in it: So you could also do

Code:
lspci | grep VGA
You get output like:

Code:
01:00.0 VGA compatible controller: nVidia Corporation GT218 [GeForce 210] (rev a2)
Use the slot number like "01:00.0" to get information on video controller by doing:

Code:
lspci -v -s 01:00.0
and get output like:

Code:
01:00.0 VGA compatible controller: nVidia Corporation GT218 [GeForce 210] (rev a2) (prog-if 00 [VGA controller])
	Subsystem: ASUSTeK Computer Inc. Device 8354
	Flags: bus master, fast devsel, latency 0, IRQ 18
	Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
	Memory at c0000000 (64-bit, prefetchable) [size=256M]
	Memory at de000000 (64-bit, prefetchable) [size=32M]
	I/O ports at bf00 [size=128]
	[virtual] Expansion ROM at d0000000 [disabled] [size=512K]
	Capabilities: [60] Power Management version 3
	Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [78] Express Endpoint, MSI 00
	Capabilities: [b4] Vendor Specific Information: Len=14 <?>
	Capabilities: [100] Virtual Channel
	Capabilities: [128] Power Budgeting <?>
	Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
	Kernel driver in use: nouveau
	Kernel modules: nouveau
(It's interesting that the output apparently makes a distinction between the terms "module" and "driver".)

If you post this information, it will at least clear up what Fedora thinks about your video.

What Xorg thinks is indicated in the log file /var/log/Xorg.0.log
__________________
"Never let the task you are trying to accomplish distract you from the study of computers."
Reply With Quote
  #7  
Old 1st June 2012, 04:15 PM
itayshom Offline
Registered User
 
Join Date: Jun 2012
Location: Israel
Posts: 6
linuxfirefox
Re: F17 upgrade: display driver problem (HD4200)

The relevant lines from lspci:

# lspci -v -s 01:05.0
01:05.0 VGA compatible controller: ATI Technologies Inc RS880 [Radeon HD 4200] (prog-if 00 [VGA controller])
Subsystem: Giga-byte Technology Device d000
Flags: bus master, fast devsel, latency 0, IRQ 10
Memory at d0000000 (32-bit, prefetchable) [size=256M]
I/O ports at ee00 [size=256]
Memory at fdfe0000 (32-bit, non-prefetchable) [size=64K]
Memory at fde00000 (32-bit, non-prefetchable) [size=1M]
Expansion ROM at <unassigned> [disabled]
Capabilities: [50] Power Management version 3
Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+

I have also attached my Xorg.0.log. Is there anything I have to look for?

Thank you,
Itay.
Attached Files
File Type: log Xorg.0.log (109.8 KB, 83 views)
Reply With Quote
  #8  
Old 2nd June 2012, 05:07 PM
itayshom Offline
Registered User
 
Join Date: Jun 2012
Location: Israel
Posts: 6
linuxfirefox
Re: F17 upgrade: display driver problem (HD4200)

Using Xorg -configure, I found this problem with monitor detection:

Code:
# Xorg -configure
X.Org X Server 1.12.0
Release Date: 2012-03-04
X Protocol Version 11, Revision 0
Build Operating System: x86-14 2.6.32-220.4.1.el6.x86_64 
Current Operating System: Linux Violator 3.3.7-1.fc17.x86_64 #1 SMP Mon May 21 22:32:19 UTC 2012 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-3.3.7-1.fc17.x86_64 root=/dev/mapper/vg_violator-lv_root ro rd.md=0 rd.dm=0 rd.lvm.lv=vg_violator/lv_root rd.lvm.lv=vg_violator/lv_swap KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8
Build Date: 14 May 2012  04:10:41AM
Build ID: xorg-x11-server 1.12.0-5.fc17 
Current version of pixman: 0.24.4
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Jun  2 18:56:48 2012
List of video drivers:
	savage
	i128
	sisusb
	siliconmotion
	v4l
	voodoo
	mga
	intel
	glint
	tdfx
	mach64
	vmware
	ati
	nouveau
	radeon
	i740
	qxl
	apm
	nv
	ast
	trident
	s3virge
	rendition
	r128
	openchrome
	cirrus
	dummy
	sis
	modesetting
	fbdev
	vesa
(++) Using config file: "/root/xorg.conf.new"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) [KMS] No DRICreatePCIBusID symbol, no kernel modesetting.
Number of created screens does not match number of detected devices.
  Configuration failed.
Server terminated with error (2). Closing log file.
Also, when asking Xorg about config using an old xorg.conf backup file, I get this error:

Code:
# Xorg -config /etc/X11/xorg.conf.backup
X.Org X Server 1.12.0
Release Date: 2012-03-04
X Protocol Version 11, Revision 0
Build Operating System: x86-14 2.6.32-220.4.1.el6.x86_64 
Current Operating System: Linux Violator 3.3.7-1.fc17.x86_64 #1 SMP Mon May 21 22:32:19 UTC 2012 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-3.3.7-1.fc17.x86_64 root=/dev/mapper/vg_violator-lv_root ro rd.md=0 rd.dm=0 rd.lvm.lv=vg_violator/lv_root rd.lvm.lv=vg_violator/lv_swap KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8
Build Date: 14 May 2012  04:10:41AM
Build ID: xorg-x11-server 1.12.0-5.fc17 
Current version of pixman: 0.24.4
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Jun  2 18:57:19 2012
(++) Using config file: "/etc/X11/xorg.conf.backup"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"

Fatal server error:
no screens found

Please consult the Fedora Project support 
	 at http://wiki.x.org
 for help. 
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

Server terminated with error (1). Closing log file.
Does anyone have an idea?

I should say that in fact the monitor works, but in a really lousy, horrible, slow fallback mode.
I have a standard LCD LG Flatron W2261V which worked just fine.

The kernel version is 3.3.7-1.fc17.x86_64

Itay.
Reply With Quote
  #9  
Old 2nd June 2012, 06:00 PM
Opanos Offline
Registered User
 
Join Date: Apr 2012
Location: Greece-Athens
Posts: 13
linuxfirefox
Re: F17 upgrade: display driver problem (HD4200)

Read this [if you dont find out]
Code:
http://forums.fedoraforum.org/showthread.php?p=1580816#post1580816
is the answer.
Reply With Quote
  #10  
Old 2nd June 2012, 06:45 PM
SlowJet Offline
Registered User
 
Join Date: Jan 2005
Posts: 5,048
linuxfirefox
Re: F17 upgrade: display driver problem (HD4200)

The xorg-x11-drivers rpm will require all the xorg-x11-drv-*
If you earse xorg-x11-drivers, then you can earse unwanted xorg-x11-drv-name.

Installed:
xorg-x11-drivers.i686 0:7.4-8.fc17

Dependency Installed:
xorg-x11-drv-apm.i686 0:1.2.3-15.fc17 xorg-x11-drv-glint.i686 0:1.2.7-1.fc17
xorg-x11-drv-i128.i686 0:1.3.5-1.fc17 xorg-x11-drv-i740.i686 0:1.3.2-16.fc17
xorg-x11-drv-keyboard.i686 0:1.6.1-4.fc17 xorg-x11-drv-mach64.i686 0:6.9.1-1.fc17
xorg-x11-drv-modesetting.i686 0:0.2.0-1.fc17 xorg-x11-drv-mouse.i686 0:1.7.2-1.fc17
xorg-x11-drv-neomagic.i686 0:1.2.6-1.fc17 xorg-x11-drv-nv.i686 0:2.1.18-15.fc17
xorg-x11-drv-r128.i686 0:6.8.2-1.fc17 xorg-x11-drv-rendition.i686 0:4.2.4-14.fc17
xorg-x11-drv-s3virge.i686 0:1.10.4-15.fc17 xorg-x11-drv-savage.i686 0:2.3.4-1.fc17
xorg-x11-drv-siliconmotion.i686 0:1.7.6-1.fc17 xorg-x11-drv-sis.i686 0:0.10.4-1.fc17
xorg-x11-drv-sisusb.i686 0:0.9.4-13.fc17 xorg-x11-drv-tdfx.i686 0:1.4.3-18.20120104gitfe60f0ed2.fc17
xorg-x11-drv-trident.i686 0:1.3.4-14.fc17 xorg-x11-drv-v4l.i686 0:0.2.0-20.fc17
xorg-x11-drv-voodoo.i686 0:1.2.4-14.fc17

SJ
__________________
Do the Math
Reply With Quote
  #11  
Old 3rd June 2012, 08:47 PM
itayshom Offline
Registered User
 
Join Date: Jun 2012
Location: Israel
Posts: 6
linuxfirefox
Re: F17 upgrade: display driver problem (HD4200)

Opanos, I read the thread. It seems that my Radeon 4xxx series is no longer supported with Catalyst.

By the way I have no idea what's the difference between Catalyst and fglrx.

I just want the FOSS driver for ATI, and not Vesa. How do I do that

Itay.
Reply With Quote
Reply

Tags
display, driver, f17, hd4200, problem, upgrade

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
ati display driver problem pradeep.rawat Hardware & Laptops 5 9th November 2009 11:55 PM
problem with ati display driver woundjuice Hardware & Laptops 0 21st February 2009 06:10 PM
Display driver problem nirrud Hardware & Laptops 1 7th January 2005 01:50 PM


Current GMT-time: 20:35 (Friday, 25-07-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat