On Sunday, March 11, 2012 07:08 PM Michael Fischer wrote:
FWIW, this is all persuant to my threads "12.1 installation failure" and "Video cards and 12.1" of the past few days.
Card is Radeon HD 6450
Got the darn thing to install.
At the initial reboot, it gave up on graphics saying something like (sorry I didn't copy it down) "couldn't find a graphical interface". I proceeded as follows:
1) chmod +s /usr/X11/bin/Xorg 2) cp xorg.conf.install xorg.conf 3) startx (this got me started into LXDE - specified during install)
hwinfo (the graphical'd version in yast) suggests that I've got a display of "ATI VGA compatible controller" whose driver is "Radeon". Indeed lsmod(8) shows the radeon driver loaded. It certainly is not mentioned in the xorg.conf. And fbdev (nor indeed 'fb' anything) is shown by lsmod.
Xorg.0.log speaks repeatedly of vesa, but no module with 'vesa' in it is currently loaded by the kernel. (perhaps that's not the right place to look?)
I notice something about a SAX3, but the repo is not displayed in the yast2 repository list. How to add it?
Suggestions more than welcomed about all this.
I'm off to experiment with things like specifying "Radeon" in xorg.conf but... *sigh*
Michael, you may already have this resolved, but if not just to clarify a couple details which may help . . . * radeon is a driver and a kernel module; it is the open source version for ATI and you need to check whether your card's chipset (the "rv") is supported by this driver * the proprietary ATI driver is fglrx; it is also a kernel module. I haven't used an ATI card in a long while, I don't know its status. IIRC it's no longer supported. I would think there's an wiki page on it. But if you have an old card, it might be worth checking whether you can still compile it * vesafb (the vesa framebuffer) is what is used by the kernel for graphical display at boot, it is compiled into the kernel so you won't see it as a module. It only supports the resolutions specified in the vesa standard, as specified in your kernel boot line "vga=". It is not used by X. * vesa is an X server vesa driver. It's resolutions also are limited to the vesa standard. * fbdev is the X server framebuffer driver. It supports an even narrower range of resolutions than vesa * the X server determines the resolution by querying the monitor's EDID. Older monitors, and in particular laptops, often do not even have an EDID or what they have is broken. Even some newer ones, typically the cheapos. This is just plain negligence by the manufacturer. When X cannot find an EDID, it guesses. When X finds an EDID but it's bad, X may quite possibly use the wrong resolution. Consequently, you may need to tell X which resolution to use, and it needs to be one supported by the driver that X has selected or you have told X to use. Start with find a driver that works with you card, forcing an 800x600 resolution just to get the graphical display working. Then work on forcing your monitor's native resolution and refresh rate (both together!), making sure that the driver you're using supports that. Hope that helps a bit. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org