Greetings to all!
I installed 12.1 from a dvd on an external hard drive, using this guide here :SDB:Installation on external hard drive - openSUSE
It is a guide for 11.4, but it went just fine, untill the phase of automatic configuration, when i got the message that the system couldn´t find the appropriate driver for my graphic card. After the installation was over, i could only boot into terminal.
Then i tried another way by upgrading newly installed 11.4, and the same happened at the end, i.e. no graphical environment, just this time i didn´t get a message about the missing driver for the g.card.
In failsafe i just didn´t know how to install that “appropriate graphic card driver”, because installing ati proprietary driver, with my old ati radeon 9600/RV350AR, was out of question, but installing ati legacy too, since i have read that after opensuse 11.1 that was impossible ( and i had no idea how to do it anyway).
In failsafe konqueror told me that i had fbdev as 2D driver, and swrast-driver (7.11) for 3D, but without hardware acceleration, if i remember well.
So i had to reinstall 11.4.
Just to add that i had a similar (or the same) problem with KDE Live-CD (12.1 RC1 and 2): this time the message was something like “found a not supported hardware” and then, again, booting into terminal mode.
Here is the PC´s config:
AMD Athlon Palomino Processor, 1250MHz
MSI MS-638OE motherboard, chipset VIA KT 266/333
ATI Radeon 9600, 128 MB
1,5 GB RAM
Is just a simple installation of good old opens source radeon driver solution to the problem? Then again, being in failsafe, i couldn´t find the driver in YaST´s “add and remove software”.
By the way, would it be feasible, or better to say wise to update to 12.1 via Thumbleweed? I am afraid that it would come again to the same problem of the missing “appropriate” driver.
And another “by the way”: how is it possible that such an installation problem could have happened to opensuse? Which is clearly better than ubuntu, mint, fedora…and then again, i didn´t have a single problem installing them, not to mention opensuse´s 4,7 GB big installation DVD and around 500 MB big CD of fedora, for example.
Thanks in advance.
Hi,
Your Radeon card is supported by the “radeon” driver
This driver is included in the default package xorg-x11-driver-video
You can verify this with cmd,
info radeon
As you have no gui, suggest you de-install the fglrx driver as follows,
cd /usr/share/ati/
sh fglrx-uninstall.sh
The above two cmds should put you back to the original install configuration
Next check that you do not have a file
/etc/X11/xorg.conf
If you do, rename it. eg. /etc/X11/xorg.conf-111122 or to something else you will remember later
Next check in file /etc/X11/xorg.conf.d/50-device.conf, you have at least the following statements
Section "Device"
Identifier "Default Device"
Driver "radeon"
EndSection
Then power down.
If alls gone well you should now be able to boot into a gui.
If not come back.
Installed, this time on PC´s hd instead of the external h.drive.
It went smooth, but at the end no graphic card driver installed, just like before.
- tried these 2 commands-
cd /usr/share/ati/
sh fglrx-uninstall.sh (even thought i did not see that a proprietary ati driver was installed),
what gave me the same answer:" no data or folder found".
2)/etc/X11/xorg.conf- the file does not exist. - /etc/X11/xorg.conf.d/50-device.conf- yes, there is what you wrote, actually, here is what is written there:
"Section “Device”
Identifier “Default Device”
#Driver “radeon”
## Required magic for radeon/radeonhd drivers; output name
## (here: “DVI-0”) can be figured out via ‘xrandr -q’
#Option “monitor-DVI-0” “Default Monitor”
#EndSection"
If the “radeon” driver is already installed, what then- reinstall it? Better yet- how to do it, if it isn´t too much to ask?
Thanks, all the best!
You might benefit by reading some practical theory here on openSUSE GNU/Linux graphics: openSUSE Graphic Card Practical Theory Guide for Users (in particular post#2 there)
That’s nominal.
You do understand that a # at the front of a line means the line is a comment and it is not to be treated as code ? Yes ?
If you want that file to be used, you need to remove the comments so that it looks like:
"Section "Device"
Identifier "Default Device"
#
Driver "radeon"
#
# ## Required magic for radeon/radeonhd drivers; output name
# ## (here: "DVI-0") can be figured out via 'xrandr -q'
# #Option "monitor-DVI-0" "Default Monitor"
#
EndSection"
Having typed that, I do not recommend that by itself as an approach.
It reads to me, that kernel mode setting (KMS), which is the automatic configuration of your graphics, did not work. … So as a user you could try to configure it (ie User Mode Setting, or UMS ).
Reboot your PC (you can do so from a terminal log in by typing with root permissions “shutdown -r now” (no quotes)) … and then when the grub boot menu appears, in the options line type “nomodeset” and boot nominally That should disable kernel mode setting, and instead, openSUSE will fall back to trying either the ‘radeonhd’ graphic driver, or the ‘fbdev’ graphic driver. If that fails, then try a ‘failsafe’ boot (which is a grub boot menu option).
Once you get a GUI, you can try to use a superior driver to the ‘radeonhd’ or ‘fbdev’ by applying the above edit noted to the /etc/X11/xorg.conf.d/50-device.conf AND also boot with the “nomodeset” boot code. Its also possibly you may need to disable KMS in init.rd … This is documented in the openSUSE-12.1 release notes.
Well no, i did not know what a # at the front of a line meant- i am just a regular user, or even less than that, who find out a few moths ago that it whas possible to install and try ubuntu on my old pc, and after mint and fedora i tried opensuse 11.4.
I edited the file and removed a # , rebooted with “nomodeset”, but nothing changed, there i was in the console mode again.
Then i tried it with failsafe mode, 5 minutes ago it worked fine, now the cursor was just standing there in the middle of the screen, blincking.
What is left? To disable KMS in init.rd…
I am tired right now-it´s night here- and i´m sorry, i do not think i will give it a try, probably i will delete 12.1 tomorow. It is just a waste of your and mine time, it would be better to wait for 12.2… and stay with 11.4 on my external hd.
Thanks for help, guys, and all the best, again!
I guess you did not read the guide I pointed you to. Thats unfortunate.
Or maybe you did but did not try the radeonhd driver? vesa driver ? The fbdev driver ? Did you try in the /etc/X11/xorg.conf.d/50-device.conf
"Section "Device"
Identifier "Default Device"
#
#Driver "radeon"
Driver "vesa"
#
# ## Required magic for radeon/radeonhd drivers; output name
# ## (here: "DVI-0") can be figured out via 'xrandr -q'
# #Option "monitor-DVI-0" "Default Monitor"
#
EndSection"
restart and boot with ‘nomodeset’ boot code.
Or
"Section "Device"
Identifier "Default Device"
#
#Driver "radeon"
Driver "radeonhd"
#
# ## Required magic for radeon/radeonhd drivers; output name
# ## (here: "DVI-0") can be figured out via 'xrandr -q'
# #Option "monitor-DVI-0" "Default Monitor"
#
EndSection"
restart and boot with ‘nomodeset’ boot code.
Or
"Section "Device"
Identifier "Default Device"
#
#Driver "radeon"
Driver "fbdev"
#
# ## Required magic for radeon/radeonhd drivers; output name
# ## (here: "DVI-0") can be figured out via 'xrandr -q'
# #Option "monitor-DVI-0" "Default Monitor"
#
EndSection"
and restart with ‘nomodeset’ boot code and test.
Please, what is it in the practical theory guide that made you not attempt any of its recommendations ?
Note it is EASY to edit in a text full screen mode. Assuming you have a wired internet connection, with root permissions install midnight commander (mc) with:
zypper in mc
and then after it is installed, you can run it with the command ‘mc’ as both a regular user and root permissions. It has function keys for the menu which makes it easy to use for editing files in a full screen text mode.
Never give up but some care is needed!
If you got to the gui in safemode once, you must be almost there.
Try the safemode once more.
If sucessful run the cmd as a user (not root),
krandrtray
and then try setting up the screen from the icon that should appear in the system tray.
Note: (to the best of my knowledge)
The chipset RV350 on the Radeon 9600PRO/9600SE/9600 cards is supported by the radeon driver.
The radeonhd driver does not support your graphics card. So stay with the radeon driver.
The info is in the cmds,
info radeon
info radeonhd
If that does not work try,
from my PC, the cmd gives the following info (as root),
<2011Nov24><23:43></home/michael> lspci |grep Radeon
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon HD 3200 Graphics
<2011Nov24><23:44></home/michael>
This info translates in the /etc/X11/xorg.conf.d/50-devices as follows,
note the format change for the BusID, so that file should now look like,
"Section "Device"
Identifier "Default Device"
Driver "radeon"
BusID "PCI:1:5:0"
## Required magic for radeon/radeonhd drivers; output name
## (here: "DVI-0") can be figured out via 'xrandr -q'
#Option "monitor-DVI-0" "Default Monitor"
EndSection"
If you get into the gui again and cannot setup the graphics via krandrtray post the output of,
xrandr |grep connected
If all still fails try:-
Quote from “File: manpages, Node: radeon, Up: (dir) RADEON(4) NAME radeon - ATI RADEON video driver”
" Option “ReverseDDC” “boolean”
When BIOS connector information isn’t available, use this option
to reverse the mapping of the two main DDC ports. Use this if
the X server obviously detects the wrong display for each con-
nector. This is typically needed on the Radeon 9600 cards bun-
dled with Apple G5s. The default is off."
This indicates there should be a the statement in the file /etc/X11/xorg.conf.d/50-device.conf,
Option “ReverseDDC” “on”
making it look at least as follows,
"Section "Device"
Identifier "Default Device"
Driver "radeon"
BusID "PCI:A:B:C"
Option "ReverseDDC" "on"
## Required magic for radeon/radeonhd drivers; output name
## (here: "DVI-0") can be figured out via 'xrandr -q'
#Option "monitor-DVI-0" "Default Monitor"
EndSection"
where ‘A:B:C’ are the values from your machine from,
lspci |grep Radeon
"‘0A:0B.C’ VGA compatible controller: … "
Best of luck.
@oldcpu:
“Please, what is it in the practical theory guide that made you not attempt any of its recommendations ?”
Fatigue! Being tired, i briefly read about a half of it, with a half of my head, and i couldn´t see that simple answer for a simple “windows user´s” question: how to install an ati driver? So, i looked for the package which had “radeon” driver i needed. Didn´t see it in the guide, or how to install it (exe.-2 clicks-go), then i left reading and i tried to install the xorg-x11-driver-video package via terminal. But it was, to my surprise, already installed. So: i couldn´t install “radeonhd” (not supported g.card), tried “fbdev” on failsafe, too slow, and opensuse couldn´t install “radeon” at the beginning. And i couldn´t figure out how to install it by myself, or “install” it = where to click twice!
Well, here we are now: i “installed” “vesa” driver as you suggested me. It works, finally i have GUI, but it is pretty slow, just like the “fbdev”.
@keellambert:
The attempt to activate/install “radeon” driver failed.
Here is the otput from “lspci |grep Radeon” :
"dhcppc0:/home/sladjo # lspci |grep Radeon
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AR [Radeon 9600]
01:00.1 Display controller: ATI Technologies Inc RV350 AR [Radeon 9600] (Secondary) "
I tried, following your example, both with "BusID “PCI:1:0:0"”, and with “BusID “PCI:1:0:1” ( correct me if i didn´t understood you well-i would be glad if i didn´t)- but nothing, no GUI.
Adding " Option “ReverseDDC” “on” to it didn´t help.
The screen resolution is 1280x1024, (0,0 Hz) and i can not change it, “Krandrtray” could not allso.
And here is the output from “xrandr |grep connected”:
sladjo@dhcppc0:~> xrandr |grep connected
xrandr: Failed to get size of gamma for output default
default connected 1280x1024+0+0 0mm x 0mm”
All right, i got “vesa” now, but not yet “radeon”- how to inst…active it, that is the question, it seems to me.
Because, staying on “vesa” wouldn´t have much of sense, i think you will agree upon that.
I hope opensuse/novell will reealise some patch to remedy that.
Anyway, i would like to thank both of you guys for your help.
some points,
-
what’s your monitor and does it support DDC?
-
have you tried using another monitor cable?
-
check the files in /etc/X11/xorg.conf.d/ and make sure none are blacklisting ‘radeon’
-
Also can you list the output of cmds,
– xrandr
– less messages |grep ‘Nov 27’ |grep kernel
Note: The previous output of xrandr is correct for your graphics card.
They are for the vga and dvi card outputs.
Here we are:
1)- The monitor is Samsung SyncMaster 765MB and, as far as i could find it on google it does support DDC (DDC1 and DDC-2B+ “…Dieser Monitor entspricht dem internationalen Standard VESA DDC für die Plug & Play-Funktion”)
2)- No, i have not tried another monitor cable. I should point out here that it works with 11.4 and Windows XP, in all of the resolutions that are specified by Samsung.
3)- i did not see that in any of the files in /etc/X11/xorg.conf.d the “radeon” driver is blacklisted.
However, i did noticed some other thing about 2 of those files, namely “50-monitor.conf” and “50-screen.conf”. Here is how they are written.
“50-monitor.conf”:
#Section “Monitor”
Identifier “Default Monitor”
## If your monitor doesn’t support DDC you may override the
## defaults here
#HorizSync 28-85
#VertRefresh 50-100
## Add your mode lines here, use e.g the cvt tool
#EndSection
“50-sreen.conf”:
#Section “Screen”
Identifier “Default Screen”
Device “Default Device”
## Doesn’t help for radeon/radeonhd drivers; use magic in
## 50-device.conf instead
Monitor “Default Monitor”
#EndSection
Notice that they both beggin and finish whit a “#” ("#Section…"and “#EndSection”), which should means that “they are not treated like a code”, as oldcpu pointed out. Should i delete those 4 “#”?
4)- Here is the otput of “xrandr”:
sladjo@dhcppc0:~> xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1280 x 1024, maximum 1280 x 1024
default connected 1280x1024+0+0 0mm x 0mm
1280x1024 0.0*
1024x768 0.0
800x600 0.0
640x480 0.0
and the output from “less messages |grep ‘Nov 27’ |grep kernel”
sladjo@dhcppc0:~> less messages |grep ‘Nov 27’ |grep kernel
messages: Datei oder Verzeichnis nicht gefunden
(No such file or directory)
The file ‘messages’ is in the directory /var/log and it requires root permissions to view.
The symbol ’ | ’ is a pipe, where there is an explanation here Pipeline (Unix) - Wikipedia, the free encyclopedia … where a pipe takes the output of a process (stdout) and feeds it directly as input (stdin) to the next one.
And note the ‘command’ grep is a filter.
The command ‘less’ is the opposite of the command ‘more’ and it allows one to view a file (or an output) and scroll through it, where i the case of ‘less’ it allows backward movement in the file as well as forward movement.
Hence by specifying (with root permissions in order to view the file messages):
less /var/log/messages | grep 'Nov 27' | grep kernel
you see all lines with both ‘27-Nov’ and ‘kernel’ in the line (if any) . You may see nothing in return.
ie you run the ‘less’ command against the file ‘messages’ and you send its output to the grep-filter and keep only lines with ‘27 Nov’ and you in turn send that to another grep-filter and keep only lines with ‘kernel’. Its fairly common/basic GNU/Linux stuff once you get used to it, and it is incredibly powerful and quick for searching (IF one can get the syntax correct).
If it were me with this problem, I would change ‘vesa’ to ‘radeon’ in the /etc/X11/xorg.conf.d/50-device.conf and boot with the boot code ‘nomodeset’. That as you noted will fail, and possibly leave you at a text prompt? If so login, and switch to root permissions and with the program ‘mc’ change ‘radeon’ back to ‘vesa’ in the 50-device.conf, and then type ‘shutdown -r now’ and then reboot with the boot code ‘nomodeset’ which will give you your low GUI with vesa driver.
BUT you will have two interesting log files in /var/log/ … You will have /var/log/Xorg.0.log.old (which will have information from the initial failed radeon boot) and /var/log/Xorg.0.log (which will have information from the most recent successful vesa boot). [ie last 2 boots are in those files].
Compare the two, and see what errors are given when radeon driver fails. If you wish to share the file contents, do NOT post the contents here !! Instead post on SUSE Paste (each on a different paste page) and post the address/URL here.
I suspect this will be beyond my ability to troubleshoot, but I also suspect that information from those log files is necessary for anyone to figure out why the ‘radeon’ boot is failing.
@oldpcu
thanks for correcting my slip with cmd ‘less messages |grep ‘Nov 27’ |grep kernel’
here are some possible reason for the output of xrandr not recognising your monitor,
- damaged monitor cable,
- BIOS needs updating on your motherboard and/or video card, (but only as a last resort!)
- xrandr or a dependancy is not correctly installed
To manually construct the files,
- 50-device.conf
- 50-monitor.conf
- 50-screen.conf
the only information is good outputs from cmds, - lspci which we have
- xrandr which we need
Hence the first priority is to sort out xrandr operation.
BTW when modifying script files from the cmd line prompt, my preferred program is vim.
I would add broken EDID or buggy driver, unable to read the EDID info correctly. If it’s the case, it might help to use a custom EDID with the radeon driver. But I haven’t read the whole thread (sorry).
@oldpcu
(Just to mention, trying “su” + “less messages |grep ‘Nov 27’ |grep kernel” i got the same message- No such file or directory. Trying “less /var/log/messages | grep ‘Nov 27’ | grep kernel” i got an output too big to be shown here.)
Anyway, i have posted content of the 2 files as you suggested, here is where they could be found:
-for Xorg.0.log: SUSE Paste
-for Xorg.0.log.old : SUSE Paste
Hence the first priority is to sort out xrandr operation.
I don´t know how i´m supposed to do that. Isn´t the output of xrandr command, which is at the bottom of my latest post (good) enough? Or i achieved it through an irregular procedure?
(sladjo@dhcppc0:~> xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1280 x 1024, maximum 1280 x 1024
default connected 1280x1024+0+0 0mm x 0mm
1280x1024 0.0*
1024x768 0.0
800x600 0.0
640x480 0.0 )
I am writing this from windows xp , so i can´t repeat the procedure right now.
And monitor cable is not damaged, which leaves us the 2 other above mentioned reasons. (Better leave BIOS update out of this 
Just to emphasize one thing- 12.1´s installer did not recognized my graphic card as supported when I tried to install 2 RC´s Live CDs, giving me a black screen which meant the end of the show and, for the 3rd time with live CDs, 12.1 Gnome Live CD just jumped immediately to the console mode.
Whit 12.1 KDE DVD, when it tried automatically to configure the installation the installer gave me the message that it couldn´t find/load ( don´t rember exactly now) an appropriate driver for my graphic card. (And i have tried also 3 time to install 12.1 from the DVD, on 2 difrent HDD.)
IMHO, there must be some bug in the 12.1´s installer which prevents it from corectly installing, or loading “radeon” driver for my graphic card, once the installation is finished. The problem very likely could lie in that part of the 12.1´s software which is responsible for the driver´s installation or for the graphic card´s recognition.
Then- maybe- skiping the automatic configuration during the installation process could be of help?
In Windows, when there is a problem with a badly installed driver, deleting and reistaling the driver also helps.
You could put that on SUSE Paste
ok, on the radeon card in its /var/log/Xorg.0.log.old file, I note:
20.397] (II) AIGLX: Screen 0 is not DRI2 capable
20.398] drmOpenDevice: node name is /dev/dri/card0
20.398] drmOpenDevice: open result is 12, (OK)
20.398] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
20.398] drmOpenDevice: node name is /dev/dri/card0
20.398] drmOpenDevice: open result is 12, (OK)
20.398] drmOpenByBusid: drmOpenMinor returns 12
20.398] drmOpenByBusid: Interface 1.4 failed, trying 1.1
20.398] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
20.860]
Backtrace:
20.883] 0: /usr/bin/Xorg (xorg_backtrace+0x37) [0x80a86b7]
20.883] 1: /usr/bin/Xorg (0x8048000+0x64a0a) [0x80aca0a]
20.883] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe410]
20.884] 3: /usr/lib/dri/r300_dri.so (0xac10e000+0x3b8720) [0xac4c6720]
20.884] 4: /usr/lib/dri/r300_dri.so (0xac10e000+0xa1bf7d) [0xacb29f7d]
20.884] 5: /usr/lib/dri/r300_dri.so (0xac10e000+0x134629) [0xac242629]
20.885] Illegal instruction at address 0xac4c6720
20.885]
Fatal server error:
20.885] Caught signal 4 (Illegal instruction). Server aborting
20.885]
20.885]
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
20.885] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
20.885]
20.885] disable primary dac
20.885] (II) RADEON(0): RADEONRestoreMemMapRegisters() :
20.885] (II) RADEON(0): MC_FB_LOCATION : 0x1fff0000 0xd7ffd000
20.885] (II) RADEON(0): MC_AGP_LOCATION : 0x27ff2000
I will be the 1st to admit that is away above my head. I assume this ATI AMD 9600 is an AGP card ? If so, I assume there is only one AGP slot. The errors suggest it struggled when doing something with dri.
I recall for the 9600/9800 there was a bug in 11.4 : Screen corruption on Radeon 9800 Pro 128MB with a fix (likely also used in conjunction with the ‘nomodeset’ boot code):
Workaround for R3xx/R4xx users (Radeon 9600/X300/Xxxx)
------------------------------------------------------
- disabled KMS by adding 'nomodeset' to boot options.
- add the following section to your /etc/X11/xorg.conf.d/50-device.conf
Section "Module"
Disable "dri"
Disable "dri2"
EndSection
but that was to have been fixed in 12.1 so I do not think that applicable to you (ie you could try it with the ‘radeon’ driver, but I would bet that it won’t help).
I recall an old PC of my wife had an old AMD 9200 PRO and for me to get that PC to work (back in the openSUSE-11.3 days) I needed to edit the 50-device.conf files (and it HAD to be used in conjunction with the boot code ‘nomodeset’):
Section "Device"
Identifier "Default Device"
Driver "radeon"
## Required magic for radeon/radeonhd drivers; output name
## (here: "DVI-0") can be figured out via 'xrandr -q'
#Option "monitor-DVI-0" "Default Monitor"
#oldcpu added following 2 lines
Option "BusType" "PCI"
Option "AGPSize" "64"
EndSection
but again, I woudl bet that will also NOT work for you (although you could try it).
Basically, I don’t have any good suggestions. I suspect you are in bug writing territory here.
From lines 933 onwards in file Xorg.0.log.old it looks as though the radeon
driver is loaded.
Did you mix-up the files?
Anyway, when you boot-up and the Xorg.0.log file looks like the one posted as
Xorg.0.log.old, do you end up in a gui or cmd line prompt?
If you end-up at the cmd line prompt, what happens if the following cmd is given,
startx
if the gui fails please post output
The worry about the output of the xrandr cmd is that its specifying a screen dimension of zero. However the correct dimensions can be retrieved now we know your monitor type.
I’ll come back to you later on that, if the suggestion from oldcpu and startx fails.
- As stated before the output labelled Xorg.0.log.old looks as though you have ended up with
the radeon module installed, also ati & vesa. The same applies to the file Xorg.0.log (diffent timing though)
17.614] (II) LoadModule: "extmod"
17.637] (II) LoadModule: "dbe"
17.644] (II) LoadModule: "glx"
17.647] (II) LoadModule: "record"
17.652] (II) LoadModule: "dri"
17.661] (II) LoadModule: "dri2"
17.664] (II) LoadModule: "fglrx" 17.675] (II) UnloadModule: "fglrx"
17.675] (II) LoadModule: "radeonhd" 18.047] (II) UnloadModule: "radeonhd"
17.684] (II) LoadModule: "ati"
17.687] (II) LoadModule: "radeon"
17.689] (II) LoadModule: "fbdev" 18.047] (II) UnloadModule: "fbdev"
17.692] (II) LoadModule: "vesa"
17.726] (II) LoadModule: "fbdevhw" 18.047] (II) UnloadModule: "fbdevhw"
17.735] (II) LoadModule: "vgahw" 18.047] (II) UnloadModule: "vesa"
17.746] (II) LoadModule: "int10"
17.773] (II) LoadModule: "ddc"
17.773] (II) LoadModule: "i2c"
18.027] (II) LoadModule: "fb"
18.041] (II) LoadModule: "ramdac"
18.041] (II) LoadModule: "exa"
18.686] (II) LoadModule: "theatre_detect"
This can be verified with cmd,
lsmod |grep radeon
- If you feel lucky try the following, in directory /etc/X11/xorg.conf.d/
rename the following files,
50-device.conf to 50-device.conf-9600
50-monitor.conf to 50-monitor.conf-9600
50-screen.conf to 50-screen.conf-9600
make new file 50-device.conf
Section "Device"
Identifier "aticonfig-Device[1]-0"
Driver "radeon"
Option "Monitor-VGA-0" "VGA-0"
Option "Monitor-DVI-0" "DVI-0"
BusID "PCI:1:0:0"
EndSection
make new file 50-device.conf
Section "Monitor"
Identifier "VGA-0"
Option "VendorName" "ATI openSource Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
Option "PreferredMode" "1280x1024"
Option "TargetRefresh" "60"
Option "Position" "0 0"
Option "Rotate" "normal"
Option "Disable" "false"
EndSection
Section "Monitor"
Identifier "DVI-0"
Option "VendorName" "ATI openSource Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
Option "PreferredMode" "1280x1024"
Option "TargetRefresh" "60"
Option "Position" "1280 0"
Option "Rotate" "normal"
Option "Disable" "true"
EndSection
make new file 50-device.conf
Section "ServerLayout"
Identifier "aticonfig Layout"
Screen 0 "aticonfig-Screen[1]-0" 0 0
EndSection
Section "Screen"
Identifier "aticonfig-Screen[1]-0"
Device "aticonfig-Device[1]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Virtual 2048 1024
Depth 24
EndSubSection
EndSection
and then do a cold boot.
If it boots into a gui try again with xrandrtray to set the screen as you require.
This should sort out any failures in the above files. Note, again must be run as root.
If the result is mayhem just rename the files to there previous state.
- As stated before the output labelled Xorg.0.log.old looks as though you have ended up with
the radeon module installed, also ati & vesa. The same applies to the file Xorg.0.log (diffent timing though)
17.614] (II) LoadModule: "extmod"
17.637] (II) LoadModule: "dbe"
17.644] (II) LoadModule: "glx"
17.647] (II) LoadModule: "record"
17.652] (II) LoadModule: "dri"
17.661] (II) LoadModule: "dri2"
17.664] (II) LoadModule: "fglrx" 17.675] (II) UnloadModule: "fglrx"
17.675] (II) LoadModule: "radeonhd" 18.047] (II) UnloadModule: "radeonhd"
17.684] (II) LoadModule: "ati"
17.687] (II) LoadModule: "radeon"
17.689] (II) LoadModule: "fbdev" 18.047] (II) UnloadModule: "fbdev"
17.692] (II) LoadModule: "vesa"
17.726] (II) LoadModule: "fbdevhw" 18.047] (II) UnloadModule: "fbdevhw"
17.735] (II) LoadModule: "vgahw" 18.047] (II) UnloadModule: "vesa"
17.746] (II) LoadModule: "int10"
17.773] (II) LoadModule: "ddc"
17.773] (II) LoadModule: "i2c"
18.027] (II) LoadModule: "fb"
18.041] (II) LoadModule: "ramdac"
18.041] (II) LoadModule: "exa"
18.686] (II) LoadModule: "theatre_detect"
This can be verified with cmd,
lsmod |grep radeon
- If you feel lucky try the following, in directory /etc/X11/xorg.conf.d/
rename the following files,
50-device.conf to 50-device.conf-9600
50-monitor.conf to 50-monitor.conf-9600
50-screen.conf to 50-screen.conf-9600
make new file 50-device.conf
Section "Device"
Identifier "aticonfig-Device[1]-0"
Driver "radeon"
Option "Monitor-VGA-0" "VGA-0"
Option "Monitor-DVI-0" "DVI-0"
BusID "PCI:1:0:0"
EndSection
make new file 50-device.conf
Section "Monitor"
Identifier "VGA-0"
Option "VendorName" "ATI openSource Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
Option "PreferredMode" "1280x1024"
Option "TargetRefresh" "60"
Option "Position" "0 0"
Option "Rotate" "normal"
Option "Disable" "false"
EndSection
Section "Monitor"
Identifier "DVI-0"
Option "VendorName" "ATI openSource Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
Option "PreferredMode" "1280x1024"
Option "TargetRefresh" "60"
Option "Position" "1280 0"
Option "Rotate" "normal"
Option "Disable" "true"
EndSection
make new file 50-device.conf
Section "ServerLayout"
Identifier "aticonfig Layout"
Screen 0 "aticonfig-Screen[1]-0" 0 0
EndSection
Section "Screen"
Identifier "aticonfig-Screen[1]-0"
Device "aticonfig-Device[1]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Virtual 1280 1024
Depth 24
EndSubSection
EndSection
and then do a cold boot.
If it boots into a gui try again with xrandrtray to set the screen as you require.
This should sort out any failures in the above files. Note, again must be run as root.
If the result is mayhem just rename the files to there previous state.