Xorg problem on Asus Aspire 7552G - Slackware

colorpurple21859 · 04-12-2015, 02:05 PM

Have you tried to use the open source radeon driver without uninstalling fglrx? To just see what happens, edit the /etc/modprobe.d/radeon_blacklist.conf and change the entries from radeon to fglrx, edit /etc/X11/xorg.conf and change driver line from fglrx to radeon in the device section. Reboot and see what happens. Another thought is have you tried setting up a new user. Something in the user config files may be causing the problem.

BearlyThere · 04-12-2015, 02:52 PM

First thing I tried was making a new user and running startx. The system threw the font error because it was running with the xorg.conf file.

Then I switched the drivers in the blacklist file to run radeon and blacklist fglrx. Xorg.conf was changed to reflect the radeon driver. Running startx on a user or root account now produces:

Code:

(II) [KMS] drm report modesetting isn't supported.
(EE)
Fatal server error:
(EE) no screens found (EE)

Note: when the system booted with the radeon configuration I saw a fglrx module loaded message zip past. Is the aforementioned blacklist switch all that is required to change from one driver to the other?

colorpurple21859 · 04-12-2015, 08:12 PM

If

Code:

lsmod

shows both radeon and fglrx loaded then

Code:

modprobe -r fglrx

then startx with the radeon driver in your xorg.conf or maybe without the xorg.conf.

BearlyThere · 04-12-2015, 11:22 PM

Ok, I unloaded my fglrx driver and loaded the radeon driver. My screen resolution at the command line changed immediately, though startx didn't work. Is it possible that even though the fglrx driver looks like its running, the system is using a fall-back vesa driver instead?

Some research indicates that the fglrx module may need to be loaded earlier in the boot process. Is that correct? If so, how should this be done? Can I call fglrx in grub or do I need to figure out how to use initrd to call it?

colorpurple21859 · 04-13-2015, 05:27 AM

I was seeing if X would start with the open source radeon driver. That would hopefully determine if it has anything to do with the fglrx driver or something else. At this point it looks like something else. May be try slackpkg install-new, or slackpkg install x, slackpkg install l, to see if something didn't get install initially. Would suggest to remove fglrx before running slackpkg, just in case something gets installed that was missing and overwrites files installed by fglrx.

BearlyThere · 04-13-2015, 11:27 AM

OK, I uninstalled fglrx and enabled radeon. I checked for packages that had been missed in the initial installation process as you suggested. None were found. Then I reinstalled all of the packages from 'l' and 'x' in the slackware 64 14.1 disk and made sure that Xorg was properly configured (Xorg -configure).

The configure option failed out because it found multiple display adapters: fglrx (which was uninstalled), vesa, and modesetting. I changed the xorg.conf to reflect the "radeon" driver only and removed the other display options.

Startx and.... same "no fonts found" problem.

What's the next step?

colorpurple21859 · 04-13-2015, 12:28 PM

Quote:

Then I reinstalled all of the packages from 'l' and 'x' in the slackware 64 14.1 disk

Have you updated the system from the internet, and reinstall from internet just in case there isn't something right with the dvd?

BearlyThere · 04-13-2015, 01:04 PM

I did the reinstall from the disk because it was local but then I did slackpkg update, slackpkg install-new, slackpkg update-all from online sources.

business_kid · 04-13-2015, 01:27 PM

I find the 'delete & reinstall' approach rarely solves anything in linux. Did you install EVERYTHING? Otherwise it could be dependencies. To check the dependencies on the programs like Xorg Try

Code:

ldd /usr/bin/Xorg |grep found

BearlyThere · 04-13-2015, 03:37 PM

Hi business_kid. AFAIK I installed everything both when the system was created initially and when I reinstalled recently. During the recent install I did

Code:

cd /slackware/slackware64/x/
installpkg ./*.txz

Your dependency check returned nothing 'found'

Code:

ldd /usr/bin/Xorg
	linux-vdso.so.1 (0x00007fffc1d73000)
	libudev.so.0 => /lib64/libudev.so.0 (0x00007f240bb48000)
	librt.so.1 => /lib64/librt.so.1 (0x00007f240b940000)
	libnettle.so.4 => /usr/lib64/libnettle.so.4 (0x00007f240b712000)
	libpciaccess.so.0 => /usr/lib64/libpciaccess.so.0 (0x00007f240b50a000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f240b2ed000)
	libdrm.so.2 => /usr/lib64/libdrm.so.2 (0x00007f240b0e0000)
	libpixman-1.so.0 => /usr/lib64/libpixman-1.so.0 (0x00007f240ae38000)
	libXfont.so.1 => /usr/lib64/libXfont.so.1 (0x00007f240acaa000)
	libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007f240aa13000)
	libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f240a803000)
	libpng14.so.14 => /usr/lib64/libpng14.so.14 (0x00007f240a5de000)
	libfontenc.so.1 => /usr/lib64/libfontenc.so.1 (0x00007f240a3d6000)
	libz.so.1 => /lib64/libz.so.1 (0x00007f240a1c1000)
	libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f2409fbe000)
	libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007f2409db8000)
	libm.so.6 => /lib64/libm.so.6 (0x00007f2409ab6000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007f24098b2000)
	libc.so.6 => /lib64/libc.so.6 (0x00007f24094e8000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f240bd94000)

When I do the command without 'grep found'.

colorpurple21859 · 04-13-2015, 05:57 PM

What happen when you do slackpkg install x, slackpkg install l, using the internet as the source and not the disk?

BearlyThere · 04-13-2015, 06:04 PM

It says there are no packages to install but that I can reinstall/uninstall. Slackpkg is not set up to look for local sources.

colorpurple21859 · 04-13-2015, 06:08 PM

I'm out of ideas. The only thing is maybe there is something in your grub.cfg that is passing something to your kernel, but I don't see how that can be.

BearlyThere · 04-13-2015, 06:20 PM

The only remaining idea I have is to try to load the fglrx module early in boot via initrd. I haven't been able to figure that out though. Some of the old articles mention something about the system not being able to unload the VGA driver and switch it with the ATI one. This theory is supported by the difference in screen resolution between booting with the radeon driver and the fglrx driver.

I don't know enough about how the process is supposed to work to be able to figure out what is going wrong. My skill level is probably "well-informed hobbyist" at best. For future reference, is the radeon driver good enough to play video games with or does that require the ATI driver?

colorpurple21859 · 04-13-2015, 06:23 PM

I did come across this worth a try at this point.

Quote:

X.Org does not usually require an /etc/X11/xorg.conf file, but in some cases (usually older cards) it is necessary to add the following line in the fglrx 'Device' section:

Option "SWCursor" "true"

got it from here http://docs.slackware.com/howtos:har...aphics_drivers