I’ve got a laptop (ACER Aspire 8935G) with two graphic cards, one is an ATI Mobility Radeon HD 4670 (no entry in the wiki page about compatibility with openSUSE for the Mobility version…) and the other is a low-power Intel graphic card (for low power). I’ve installed Fedora on the laptop, but it sticks to the Intel card, and I didn’t manage to change it, nor did I get an answer on Fedora forums.
Is there any general option to do that under SUSE? I understand that it might not work with this configuration of hardware, but is it even possible to choose the graphic card to be used? If yes, could you provide some link to/name of the feature, so I can look further into it?
So , now that you know some graphic card theory for openSUSE, you could download an openSUSE liveCD, and then see what you can do with that. That way you do NOT need to install anything to test. Software.openSUSE.org Note I stated a liveCD and NOT a DVD. You can not test from a DVD like you can from a liveCD.
Also try an openSUSE-11.2 liveCD and not an 11.3 miletone liveCD (as 11.2 has the tool sax2 on the liveCD, where 11.3 milestone releases do not). Download the liveCD, do the md5sum check of downloaded iso vs md5sum on download website and if that passes then burn iso to a +R or -R CD (not an RW) at slowest speed your burner allows.
Then boot to that liveCD. At first splash/boot menu, select F3 and selected TEXT ! Then boot the liveCD and it should boot to a full screen text mode. When greeted with a text login prompt, login as user “linux” and use <enter> as password. Then type “su” (no quotes) to switch users to root (administrator) using <enter> as password.
Then use the openSUSE tool “sax2”.
Then type:
sax2 -p
to see what graphic cards sax2 recognizes. Hopefully you will see a chip-0 and a chip-1, where one of these two is your Intel and the other your Radeon.
If that is the case, you can test both (one at a time) with the basic vesa driver.
For chip-0:
sax2 -r -m 0=vesa
and if that works, exit sax2, type “exit” to get rid of root permissions (that is VERY important) and then type “startx” to boot to X.
Alternatively, for chip-1 (instead of chip-0 above):
sax2 -r -m 1=vesa
and if that works, exit sax2, type “exit” to get rid of root permissions (that is VERY important) and then type “startx” to boot to X.
Now lets say you know chip-0 to be Intel. Then you could instead of vesa try:
sax2 -r -m 0=intel
and if that works, exit sax2, type “exit” to get rid of root permissions (that is VERY important) and then type “startx” to boot to X.
Of course if the intel was chip-1 then it would be “sax2 -r -m 1=intel”.
Now lets say you know chip-1 to be the Radeon. Then you could instead of vesa try the radeonhd driver:
sax2 -r -m 1=radeonhd
and if that works, exit sax2, type “exit” to get rid of root permissions (that is VERY important) and then type “startx” to boot to X.
… but its possible the ‘radeonhd’ did not work, in which case you could try ‘radeon’ driver. So to try chip-1 as the radeon driver you could try:
sax2 -r -m 1=radeon
and if that works, exit sax2, type “exit” to get rid of root permissions (that is VERY important) and then type “startx” to boot to X.
Note both the radeon and radeonhd driver as packaged in openSUSE-11.2 are buggy, … but there are updates available. So if you have at least some functionality with one of those two (necessary to prove there is some chance of this working), then there is a further chance you can get it working better after installation by updating to a more cutting edge (less buggy) version of the driver.
Note those sax2 commands should be run from run level 3 (a full screen text mode with NO X running anywhere on the PC) and not from run level 5.
The only configuration that worked was the intel for the intel chip, even vesa drivers wouldn’t start up the ATI card. Is it possible to download the newest realese of radeon or radeonhd packages into my hard drive and use them from the liveCD?
Also SUSE wouldn’t detect my network hardware. Neither the wireless, nor the cable.
I got myself into quite some trouble with this laptop it seems.
Sorry to read that. Is it possible for you to provide more technical information? Did you get any errors? What was in the /var/log/Xorg.0.log when you tried the various drivers? (you can post it on PasteBin.be).
What was the output of
sax2 -p
when run as root. I know you can see that but those trying to help can not.
I recommend you keep a digital camera handy, so you can take pix of errors, and not have to write them down all the time.
Yes, but you need a PC with lots of RAM (at least 4GB IMHO) and as soon as you switch OFF the power, all the work one does to set it up (and there is a lot because one is doing this from a LiveCD as opposed to a regular install) is lost.
Again, more technical information to confirm this would be helpful.
I’m no expert in wireless, and I mess up things quite often, but I am rather skeptical here: re your statements without any more detail. I confess I have acquired a healthy skeptism over the years, and as long as I can improve my ability to be tactful, then asking questions can sometimes help point one in the right direction.
I’m no expert neither. I only said it didn’t use them on it’s own. With some searching I’m sure I would be able to make it work, but that’s only if I manage to get the graphic cards working how I want them to (otherwise I’m just sticking to my Fedora and being a lame Linux user untill I have more time to learn how to properly use it )
Ok, I’ve managed to copy the config files to my hard drive and >> the outputs too
sax2 -p:
Chip: 0 is -> Intel Mobile Intel® GM45 Express Chipset 00:02:0 0x8086 0x2a42 PCI intel
Chip: 1 is -> ATI ATI MOBILITY RADEON HD 4670 01:00:0 0x1002 0x9488 AGP radeonhd
outputs of both
sax2 -r -m 1=radeon
sax2 -r -m 1=radeonhd
are the same:
SaX: initializing please wait...
SaX: no X-Server is running
SaX: will start own server if needed
ISaX: could not import file: /var/cache/sax/files/config at /usr/sbin/isax line 199. //(repeated about 6 times)
SPP: prepare device [0] profile: Depth24
SPP: prepare device [0] profile: Intel
SPP: calling device [0] profile script: Intel
SPP: prepare device [0] profile: AIGLX
SPP: prepare device [0] profile: Composite
SPP: prepare device [0] profile: Virtual2k
SPP: prepare device [0] profile: Virtual
SPP: including prepared profile(s)...
SaX: startup
xc: sorry could not start configuration server
xc: for details refer to the log file:
/var/log/SaX.log
xc: abort...
the line with “//(repeated about 6 times)” added to it didn’t get into the file, but went to the console output. and it appeared there about 6 times
See if you can disable the Intel onboard from the BIOS, remove xorg.conf and retry to configure the card as oldcpu suggested. This way the ATI would become device0
It appears the radeon and radeonhd driver as packaged in openSUSE-11.2 does not work well with the radeonhd 4670. One needs the updates to the driver on the Xorg : x11 repository per post #11 here: openSUSE Forums - View Single Post - openSUSE Graphic Card Practical Theory Guide for Users unfortunately there is no real way to test that with a liveCD as it requires a reboot.
Hence that likely viable approach is not available to you.
You could (if your PC has sufficient RAM) now try the proprietary ATI graphic driver. I think you need at least 4GB of ram to try that. You need to boot to the liveCD run level 3, and then from zypper (not from yast as it will install to much) install kernel-source and kernel-syms (of the same version as the 2.6.31.5 kernel to match the 2.6.31.5 on the liveCD) and also linux kernel headers, gcc, make, automake. Do not go to yast to install this as it will try to install something like 400MB worth of rpms which one does not have the space to waste in a liveCD boot.
Then make the driver per the guidance here: ATI/The Hard Way - openSUSE while it states that wiki is out of date, frankly the one it refers to is IMHO worse, and I recommend the wiki I quote … ie from a text mode (you need a wired connection to the internet)
login as a regular user (not root)
download the ATI driver .run file
su #switch to user root
install the rpms I noted with zypper:
zypper install kernel-source kernel-syms linux-kernel-headers gcc make automake
run sh ati*.run --buildpkg SuSE/SUSE112-AMD64
rpm -Uvh fgl*.rpm
ldconfig
aticonfig --initial
type: exit #to get rid of root permission
startx
You may need to play with aticonfig input arguments to get it to see and configure your graphic card.
I have an Acer 8935g laptop, openSUSE 11.2, 4GB ram and two cards:
Chip 0: Intel GM45
Chip 1: ATI HD4670
I am able to get radeonhd working ok, but I want the full functionality of the card (extra speakers, mic etc) so tried to install the proprietary driver.
I have worked through all the various links that you suggest, but to no avail. I have tried ‘one-click’, the easy way, the hard way, been in and out of init 3 like a yo-yo, but the system will only recognise the first card (Intel) which has much reduced functionality.
Both the ATI driver executable and the rpm option appear to work, and subsequently aticonfig appears to work. But after installation various sax2 attempts all hang and when I reboot the systems starts ok but X hangs with a blank screen (I am able to go to a command prompt ok).
Unfortunately the Acer has a very restricted bios, there is no option to disable the intel card in the hardware.
Do you have any further suggestions? Do you know any way in SUSE that I can programmatically disable (hide) the Intel?
I understand this was likely painful, but in truth its too general a statement in order to not provide advice that may duplicate what you tried. You really DO have to be more specific. Heck, I can’t even tell if you were using a 32-bit or a 64-bit openSUSE, nor can I tell what desktop (KDE ? Gnome ? LXDE ? Xfce ? ) … it should not matter but …
Also when you tried the radeon/radeonhd driver, what rpms were you using? Did you try the cutting edge driver/rpms from the X11 : Xorg repository? And if you did, what commands did you use to try to configure the /etc/X11/xorg.conf file? What did the file look like (PasteBin.be is a good place to put such a file. Do NOT post it here).
when you tried the proprietary driver, what version did you try? What comamnds did you use to try to configure the /etc/X11/xorg.conf file. What did the file look like (PasteBin.be is a good place to put such a file. Do NOT post it here).
(Just tried to register with PasteBin but registration not available now therefore xorg.conf extract at end of message.)
First, I followed the instructions with the proprietary driver, using the automatic option:
sh ./ati-driver-installer-10-3–x86.x86_64.run
aticonfig --initial
reboot, the screen hung so I repeated this time with:
aticonfig --initial -f.
screen hung.
Second, I generated a distribution specific package (fglrx64_7_4_0_SUSE112-8.712-1.x86_64.rpm) and installed with rmp Uvh …
aticonfig --initial -f.
Screen hung.
I tried aticonfig --initial --input=/etc/X11/xorg.conf.
Screen hung.
Found your various (excellent) posts and made sure all the packages were installed from Xorg : x11 repository (as per post #11).
Screen hung.
Next I found this link and carefully followed the instructions as listed.
Screen hung.
Various attempts to use sax2 -r -m 0 (or 1) =fglrx (or redeonhd) all failed: ‘(ww) fglrx no matching device section for instance (Bus ID PCI:0@1:0:1) found’.
Of course that did not work. You forgot to install the rpm fglrx.
Similar problem. You forgot to un-install the fglrx rpm (from before) , before you installed the new rpm.
Sorry, thats too general. What rpms did you install ? What version numbers? Did you do a quality check to ensure you actually did install the rpms? Many users think they installed them and they did not. And finally, after rpms were successfully installed, did you reboot to run level 3 and configure an /etc/X11/xorg.conf file with the appropriate sax2 arguments. My guess is you did not.
… well, … apologies, I’m from Missouri, but all the above approcahes were not accurate, and the approach you quoted requires an edit to a command to work in openSUSE-11.2, so I’m not convinced you were able to implement that edit correctly.
None of those will work if the 1st 4 example you quoted were not followed correctly. As far as I can read, every one of examples 1 to 4 were not followed correctly.
I confess I don’t know where to start. :\ As far as I can read, you were not able to follow the directions in any of the cases above. Hence I’m reluctant to provide any specific recommendations as I am afraid they will not be followed exactly.
Help me understand this:
You say “(1) Of course that did not work. You forgot to install the rpm fglrx.” then you say " (2) You forgot to un-install the fglrx rpm (from before) , before you installed the new rpm."
At no point did I knowingly install fglrx separately. The first installation (1) and the rpm file (2) were both generated using the ati installer script. Are you saying that the fglrx should be installed before using the script? If so where from?
No, I am saying in (1) that the “fglrx” rpm is created by the script. After that it MUST be manually installed by yourself. That instruction is written in every guide that I have seen about using the ATI .run file.
For (2) , in case you already had the “fglrx” rpm installed, then it must be removed before you try to install a new version of the “fglrx” rpm.
You say: " None of those will work if the 1st 4 example you quoted were not followed correctly. As far as I can read, every one of examples 1 to 4 were not followed correctly." It is not clear to me what you base this statement on.
I followed the ATI installation instructions in (1) and (2) very carefully. They did not require installation of fglrx first. If they do - show me where please, and I will start again.
As for the rpms, I did as one of your posts suggested:
zypper install kernel-source kernel-syms linux-kernel-headers gcc make automake
rpm -Uvh fgl*.rpm
ldconfig
aticonfig --initial
type: exit #to get rid of root permission
startx
Unfortunately your interpretation of (1) and (2) seems to have hindered your acceptance that I did indeed follow (4) as required.
I know how easy it is to make mistakes when you are tired so I have attempted to get this working over a period of days, each time returning and following the various guidance as carefully as I can.
It may be that a new code release is required and that no-one can resolve it right now.
Of course I could be wrong. I based my assessment on your description of the activities you performed.
Typically, with a propietary ATI graphic driver, if installing it via what is called “the hardway” (which is not hard), one will first ensure one has the kernel-source and kernel-syms of the EXACT same version as one’s kernel installed, and also have linux-kernel-headers and the openSUSE “base development” pattern installed. Then in run level 3 one will do ALL of the activities from a full screen run level 3 (and not from run level 5).
delete any old fglrx rpm that may be installed.
then run the ATI*.run file with the appropriate syntax/arguments;
then install the new fglrx rpm created by the ATI *.run file;
then run the ATI ati-config executeable with the appropriate syntax and arguments to create an xorg.conf file.
reboot to test (or run startx as a regular user to test)
I definitely did NOT get the impression you did that. Just the contrary. I was left with the impression you skipped steps.
Yes, most definitely it has. I don’t see how I can assume anything else.
Good luck with your efforts.
Also, you may try take a look at “man sax2”. Even though depreciated, if I recall correctly, sax2 has arguments that can be run to specifically setup 2 graphic devices on a PC. Also, I do not have 2 graphic devices on any of my PCs, so this sax2 capability is not something I can help you with.
Just to be clear, I worked through exactly the steps that you describe, more than once.
I have come across a reference to agpgart and the question whether config_agp was enabled when the kernel was built. I do not have agpgart loaded (only intel_agp) so will check this out and let you know if it is fruitful.
Using the -c option in sax2 made no difference and the agp issue seems irrelevant.
Having worked carefully through all the various approaches, each time returning the machine to a clean state, the solution still evades me.
Either I get a blank screen, sax2 returns an error or the Intel card is used. I have not found a non-bios way of disabling or by-passing the on-board Intel card so that sax will use the ATI card.
It seems that I will have to settle with the radeonhd driver for now and hope a new release of a proprietary driver addresses the problem.
it seems.