In Linux, How Come Video Will Work, But Not Boot Up?

happydog500 · 10-29-2016, 06:37 PM

Please!! This is NOT a how to fix it question. (I'm kind of giving up on that) I have a different question wondering about it.

I can use dual video in Mint 17.3, but have blank screens in Mint 18, because of the loss of flgrx video driver.

In Mint 18, I can boot up with one monitor, then when running, I can hook up the second monitor (HDTV), and they will work fine.

After getting it working, if I shut off the computer, when I boot back up, I get blank screens. I have to unhook the TV, then boot back up, then hook up the TV.

I am wondering, if you don't have the right drivers, you'd think that it wouldn't work, but it does work. It just doesn't boot up working.

Not sure if I can ask the question in a way that a person can understand what I'm asking.

1. What makes it so it will not boot up properly, but after it's up and running, it will work?
2. Why can't they take the reason it works after boot up, and put that during boot up?

Thank you,
Chris.

business_kid · 10-30-2016, 05:28 AM

You can't 'lose the fglrx driver' and get away with it, because fglrx overwrites Mesa libs. You uninstall fglrx, and install latest versions of OSS & Mesa if necessary, or install fglrx. Try this

Code:

ls -l /usr/lib64/libGL*

and check for symlinks pointing at nothing.

Then get all of your video equipment described in /etc/X11/xorg.conf.d/. Write up a video.conf file and get it all down in sections like xorg.conf. Google this stuff if you have issues.

happydog500 · 10-30-2016, 09:31 PM

Sorry I was not able to write a question in such a way you would understand. My fault.

1. Linux Mint 18 did "lose flgrx." You can't install it because of xorg 1.18. The open source driver doesn't work after boot.
2. "Googled it" for a year. "no way no how" is the answer I get. It's all over the internet that a lot of amd gpu's don't work (after 14.04) with open source, and nobody can fix it.

One reason it "works" but doesn't boot is, Linux doesn't apply the video until after you log in. I went to "log in window preferences" in 17.3. When I plug in the second monitor, it shows up in "primary monitor" as DVI-0 and VGA0. In 18, it shows up blank.

When I install 18, I can't use my computer for a lot of things. I am wrecking my hardware by unplugging and plugging back in 5 times a day when I need to use it. I have to wipe it out and install 17.3. I keep hoping to get 18 to work, going back to it, but nothing ever does.

Here is the command:

Code:

mint@mint ~ $ ls -l /usr/lib64/libGL*
ls: cannot access '/usr/lib64/libGL*': No such file or directory
mint@mint ~ $

Chris.

business_kid · 10-31-2016, 05:30 AM

Here's my output showing the Mesa libGL* libraries (Intel video card)

Code:

bash-4.3$ ls -l /usr/lib64/libGL*
-rwxr-xr-x 1 root root   1457 Aug 25  2014 /usr/lib64/libGL.la
lrwxrwxrwx 1 root root     14 Oct 25  2014 /usr/lib64/libGL.so -> libGL.so.1.2.0
lrwxrwxrwx 1 root root     14 Oct 25  2014 /usr/lib64/libGL.so.1 -> libGL.so.1.2.0
-rwxr-xr-x 1 root root 414152 Aug 25  2014 /usr/lib64/libGL.so.1.2.0
-rwxr-xr-x 1 root root   1023 Aug 25  2014 /usr/lib64/libGLESv1_CM.la
lrwxrwxrwx 1 root root     21 Oct 25  2014 /usr/lib64/libGLESv1_CM.so -> libGLESv1_CM.so.1.1.0
lrwxrwxrwx 1 root root     21 Oct 25  2014 /usr/lib64/libGLESv1_CM.so.1 -> libGLESv1_CM.so.1.1.0
-rwxr-xr-x 1 root root  15848 Aug 25  2014 /usr/lib64/libGLESv1_CM.so.1.1.0
-rwxr-xr-x 1 root root   1005 Aug 25  2014 /usr/lib64/libGLESv2.la
lrwxrwxrwx 1 root root     18 Oct 25  2014 /usr/lib64/libGLESv2.so -> libGLESv2.so.2.0.0
lrwxrwxrwx 1 root root     18 Oct 25  2014 /usr/lib64/libGLESv2.so.2 -> libGLESv2.so.2.0.0
-rwxr-xr-x 1 root root  24680 Aug 25  2014 /usr/lib64/libGLESv2.so.2.0.0
lrwxrwxrwx 1 root root     17 Oct  9  2014 /usr/lib64/libGLEW.so -> libGLEW.so.1.10.0
lrwxrwxrwx 1 root root     17 Oct  9  2014 /usr/lib64/libGLEW.so.1.10 -> libGLEW.so.1.10.0
-rwxr-xr-x 1 root root 551512 Jul 15  2014 /usr/lib64/libGLEW.so.1.10.0
-rwxr-xr-x 1 root root   1254 Feb 21  2013 /usr/lib64/libGLU.la
lrwxrwxrwx 1 root root     15 Oct  9  2014 /usr/lib64/libGLU.so -> libGLU.so.1.3.1
lrwxrwxrwx 1 root root     15 Oct  9  2014 /usr/lib64/libGLU.so.1 -> libGLU.so.1.3.1
-rwxr-xr-x 1 root root 516416 Feb 21  2013 /usr/lib64/libGLU.so.1.3.1

If you have fglrx installed, libGL.so.1 will be a symlink to libGL.so.(fglrx_version_number), and so on. The .la files are static libs, iirc. You should have those files, and symlinks; not having them makes me wonder what video drivers are installed? In case Mint buries them in some subdir, try this

Code:

cd /usr/lib64
find -name 'libGL*'

If you find them in a sub directory, post the output of 'ls -l libGL*' in that directory.

happydog500 · 10-31-2016, 05:37 PM

I see you use slackware. I tried to get Salix (because I'm lazy) to work, but it has xorg. 1.18 also. After months of trying, had to go back to Mint 17.3. It was disappointing because I really wanted to use salix as my main disro.

Chris.

corbis_demon · 11-02-2016, 04:42 AM

Quote:

Originally Posted by business_kid

The .la files are static libs, iirc. You should have those files, and symlinks

The .la files are not archives with object code, but contain only meta-data. They are used by libtool to track dependencies, file names, revisions etc. Their absence shouldn't be too alarming on modern systems with pkg-config, though.