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 -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, Mar 11, Michael Fischer wrote:
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 should say that the current situation sometimes leaves window content sort of garbled on movement. Not good for real usage, though it might get me though some debugging. Michael -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, Mar 11, Michael Fischer wrote:
On Sun, Mar 11, Michael Fischer wrote:
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.
Ok, I removed the xorg.conf and set the /etc/X11/xorg.conf.d/50-device to use 'Device: "radeon"'. Now I get (EE) RADEON(0): Chipset: "CAICOS" (ChipID = 0x6779) requires KMS off to reboot without the 'nomodeset' ... ok, now I'm back to being unable to boot: mdadm: an md device must be given in this mode ... /dev/md0: the superbblock could not be read or does not describe a correct ext2 off to try to reinstall that partition.. Michael -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/03/11 19:43 (GMT-0400) Michael Fischer composed:
Ok, I removed the xorg.conf and set the /etc/X11/xorg.conf.d/50-device to use 'Device: "radeon"'. Now I get
(EE) RADEON(0): Chipset: "CAICOS" (ChipID = 0x6779) requires KMS
off to reboot without the 'nomodeset'
1-For 50-device.conf to work you also need properly uncommented sections in 50-monitor.conf and 50-screen.conf, at least in every case I've tried to use xorg.conf.d/. 2-nomodeset on cmdline prevents the radeon driver from working at all. Radeon requires working KMS.
... ok, now I'm back to being unable to boot:
mdadm: an md device must be given in this mode ... /dev/md0: the superbblock could not be read or does not describe a correct ext2
off to try to reinstall that partition..
Boot messages are often in a misleading order as long as you're using systemd and/or "YES" for RUN_PARALLEL= in /etc/sysconfig/boot. This also may be a problem that goes away if not using systemd init. You can per boot or permanently not use it via instructions in the relnotes: http://www.suse.de/relnotes/i386/openSUSE/12.1/RELEASE-NOTES.en.html -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sunday 11 Mar 2012 19:09:39 Michael Fischer wrote:
On Sun, Mar 11, Michael Fischer wrote:
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 should say that the current situation sometimes leaves window content sort of garbled on movement. Not good for real usage, though it might get me though some debugging.
Michael I tried running 12.1 on my old laptop with a Radeon card but it never loaded to a graphics login, it always bombed out to a text login. My card is old so i'm not sure if its an issue with Radeon cards or old drivers being dropped.
It all works fine on 11.4 I've given up until 12.2 to see if that works any better. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Mar 12, ianseeks wrote:
I tried running 12.1 on my old laptop with a Radeon card but it never loaded to a graphics login, it always bombed out to a text login. My card is old so i'm not sure if its an issue with Radeon cards or old drivers being dropped.
It all works fine on 11.4
I've given up until 12.2 to see if that works any better.
Proprietary driver works fine for me now (bummer in some ways, but it works) # zypper ar -f http://geeko.ioda.net/mirror/ati/openSUSE_12.1/ fglrx # zypper in fglrx64_xpic_SUSE121 # atinconfig --initial # shutdown -r now takes a while to download, but the above got me going fine. You'll probably need 'nomodeset' on the kernel line when booting in to do the above. After that, you don't need it. Michael -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 12 Mar 2012 22:12:42 Michael Fischer wrote:
On Mon, Mar 12, ianseeks wrote:
I tried running 12.1 on my old laptop with a Radeon card but it never loaded to a graphics login, it always bombed out to a text login. My card is old so i'm not sure if its an issue with Radeon cards or old drivers being dropped.
It all works fine on 11.4
I've given up until 12.2 to see if that works any better.
Proprietary driver works fine for me now (bummer in some ways, but it works)
# zypper ar -f http://geeko.ioda.net/mirror/ati/openSUSE_12.1/ fglrx # zypper in fglrx64_xpic_SUSE121 # atinconfig --initial # shutdown -r now
takes a while to download, but the above got me going fine. You'll probably need 'nomodeset' on the kernel line when booting in to do the above. After that, you don't need it.
Michael I'll give that a try, thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Mar 13, ianseeks wrote:
On Monday 12 Mar 2012 22:12:42 Michael Fischer wrote:
On Mon, Mar 12, ianseeks wrote:
I tried running 12.1 on my old laptop with a Radeon card but it never loaded to a graphics login, it always bombed out to a text login. My card is old so i'm not sure if its an issue with Radeon cards or old drivers being dropped.
It all works fine on 11.4
I've given up until 12.2 to see if that works any better.
Proprietary driver works fine for me now (bummer in some ways, but it works)
# zypper ar -f http://geeko.ioda.net/mirror/ati/openSUSE_12.1/ fglrx # zypper in fglrx64_xpic_SUSE121 # atinconfig --initial
typo: s/atinconfig/aticonfig/ Michael -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday 13 Mar 2012 10:38:33 Michael Fischer wrote:
On Tue, Mar 13, ianseeks wrote:
On Monday 12 Mar 2012 22:12:42 Michael Fischer wrote:
On Mon, Mar 12, ianseeks wrote:
I tried running 12.1 on my old laptop with a Radeon card but it never loaded to a graphics login, it always bombed out to a text login. My card is old so i'm not sure if its an issue with Radeon cards or old drivers being dropped.
It all works fine on 11.4
I've given up until 12.2 to see if that works any better.
Proprietary driver works fine for me now (bummer in some ways, but it works)
# zypper ar -f http://geeko.ioda.net/mirror/ati/openSUSE_12.1/ fglrx # zypper in fglrx64_xpic_SUSE121 # atinconfig --initial
typo: s/atinconfig/aticonfig/
Michael
thanks.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/03/11 19:08 (GMT-0400) Michael Fischer composed:
FWIW, this is all persuant to my threads "12.1 installation failure" and "Video cards and 12.1" of the past few days.
What were you using last before 12.1 (or now?)?
Card is Radeon HD 6450
What rv is that (available from lspci output)? Is a built-in part of the motherboard?
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
I think this does little but try to specify that the native FOSS driver for your video chip will not be used.
3) startx (this got me started into LXDE - specified during install)
See also the tail of /etc/permissions.local.
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.
1-Put /var/log/Xorg.0.log where list subscribers can see it, preferable an upload that won't get wrapped to your own personal web space or http://susepaste.org/ or http://pastebin.com/ or similar. 2-Read: http://en.opensuse.org/SDB:ATI_troubleshooting http://en.opensuse.org/SDB:Radeon http://en.opensuse.org/openSUSE:Bugreport_X#How_to_test_the_latest_Xorg 3-consider other mailing lists where those with more experience with your video chip might be focusing their attention: opensuse-kernel opensuse-xorg 4-uploading y2logs might also prove helpful before this is resolved: http://en.opensuse.org/Bugs/YaST#I_reported_a_YaST2_bug.2C_and_now_I_am_aske...
I'm off to experiment with things like specifying "Radeon" in xorg.conf but... *sigh*
Managing xorg.conf by hand can be unwieldy. An alternative that's less succeptible to parse errors is using /etc/X11/xorg.conf.d/, specifically in most cases: 50-device.conf, 50-monitor.conf, 50.screen.conf. http://lists.opensuse.org/opensuse/2012-03/msg00388.html has an attachment with an example/minimal use of these three files either individually, or combined into xorg.conf. I've sometimes found that attempting use of these three files will lead to loss of keyboard and mouse if /etc/X11/xorg.conf.d/90-keytable.conf does not exist. Main thing I can tell it does is specify use of evdev input device driver. I have sometimes found, never having used a video chip even close to yours (AFAICT), that a fourth file in xorg.conf.d/ can sometimes be helpful (it disables compositing) at least for troubleshooting: #70-composite.conf Section "Extensions" Option "Composite" "Disable" EndSection
I should say that the current situation sometimes leaves window content sort of garbled on movement. Not good for real usage, though it might get me though some debugging. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, Mar 11, Felix Miata wrote:
On 2012/03/11 19:08 (GMT-0400) Michael Fischer composed:
FWIW, this is all persuant to my threads "12.1 installation failure" and "Video cards and 12.1" of the past few days.
What were you using last before 12.1 (or now?)?
Not on this machine, but 11.4 - where it happily copes with an integrated intel graphics chip. Just did a reinstall to get around an inability to reboot (tried to raid 1 that /boot partition again. Sometimes works, sometimes not) After the "initial reboot", yast comes back in curses mode with The graphical interface could not be started The required packages were not installed or the graphics card is not properly supported. Now, in between, I found out (upthread) that this card needs KMS. As I'm in a nomodeset install, that probably explains the message. Going to see if I can simply reboot - without nomodeset and 50-device.conf set to use "radeon". .......... Ok, now I've got an install with no Xorg binary.... How many times do I have to go through this? And Yast thinks xorg-11 is installed. Michael -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, Mar 11, Michael Fischer wrote:
On Sun, Mar 11, Felix Miata wrote:
Ok, the Xorg binary was simply not where I expected it. Found it and set the permissions. Nope, without nomodeset, its goofed. Screen wrapped around at the 50% mark as per an earlier post.... I guess I can run with vesafb (by cp xorg.conf.install to xorg.conf) for now. Off to order a variety of cheap Radeon and GeForce clones from newegg to try (Radeon 5450, GeForce 210, GeForce 8400GS). Felix, thanks for all the tips and effort. Appreciated. Michael -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/03/11 21:27 (GMT-0400) Michael Fischer composed:
Ok, the Xorg binary was simply not where I expected it. Found it and set the permissions.
Nope, without nomodeset, its goofed. Screen wrapped around at the 50% mark as per an earlier post....
I guess I can run with vesafb (by cp xorg.conf.install to xorg.conf) for now.
Off to order a variety of cheap Radeon and GeForce clones from newegg to try (Radeon 5450, GeForce 210, GeForce 8400GS).
Before you do that, try this on cmdline instead of nomodeset: video=1600x900@60 Substitute whatever your display's native resolution is for 1600x900. What display are you using? Could be that it is where the bug lies and only 12.1 figured out how to hit it. Could be a more complete xorg.conf WRT display characteristics is all you need. Also, there may be Xorg startup and/or config parameters to try specific to troubleshooting whatever rv chip yours is, and other suggestions if only you weren't keeping Xorg.0.log a secret. One would be disabling EDID via xorg.conf*. Believe it or not, sometimes Dell knows about stuff like this, and may have some help available if only you can figure out where to look.
Felix, thanks for all the tips and effort. Appreciated. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, Mar 11, Felix Miata wrote:
Before you do that, try this on cmdline instead of nomodeset:
video=1600x900@60
Substitute whatever your display's native resolution is for 1600x900. What display are you using? Could be that it is where the bug lies and only 12.1 figured out how to hit it. Could be a more complete xorg.conf WRT display characteristics is all you need.
Also, there may be Xorg startup and/or config parameters to try specific to troubleshooting whatever rv chip yours is, and other suggestions if only you weren't keeping Xorg.0.log a secret. One would be disabling EDID via xorg.conf*.
Sorry about not pasting Xorg.0.log. Nothing personal :-) I stumbled on the opensuse page for the fglrx driver, and as it took all of 2 zypper commands, I gave it a try and it seems to work. The Xorg.0.log definitely shows it operative, though modprobe shows nothing about it or radeon.
Believe it or not, sometimes Dell knows about stuff like this, and may have some help available if only you can figure out where to look.
Oh, I believe it. Thanks again for all the help. I'm off to see a woman about some brandy while the mountain of detected software updates install... I've been at this for 8 hours now. Been years since I had this much trouble with a SuSE install. The weekday evenings to come will be full of the fun of transfering $HOME from backup to the new machine (once found a busted integrated nic that way) and all the dancing to get multimedia, etc. working properly. All the best, Michael -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
On Mon, Mar 12, Dennis Gallien wrote:
Michael, you may already have this resolved, but if not just to clarify a couple details which may help . . .
Thank you for taking the time to explain the various types of drivers. I'll save the info for later use if/when I manage to get into this sort of muddle again. I stumbled on http://en.opensuse.org/SDB:ATI_drivers and followed the CLI instructions, followed by `aticonfig --initial`. It had its way with my xorg.conf file. Fortunately, it worked :-) I prefer to go with the FOSS drivers when possible, but for now, this gets me a useable system.
* 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.
Michael -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Dennis Gallien -
Felix Miata -
ianseeks -
Michael Fischer