Can't run laptop (HP ProBook 455 G1 (F7X54EA)) with fglrx64

English Hardware
1

Hi all,
recently I installed LEAP 42.1, and try to install/run fglrx64 drivers from their repo with result:

Summary report:

Kernel => 4.1.12-1-default
Detected => RPM package
Build => FAILURE ]
Install => FAILURE ]

Kernel => 4.1.20-11-default
Detected => RPM package
Build => OK ]
Install => OK ]

Building/installation of fglrx kernel module failed! Try again
by calling “/usr/bin/fglrx-kernel-build.sh” manually.

Unfortunately, after rebooting in multiuser with graphics - I see grey screen (gdm ?), and no login screen.

Can you help me please get fglrx running ?
Where I can find more information - what’s wrong with drivers/X/etc ?

2

Hi
I have a ProBook 455 G1, normally I build the rpm manually from the script at https://en.opensuse.org/SDB:AMD_fglrx#Building_the_rpm_yourself

Then once built/installed run the ./makerpm-amd-15.12.sh -igf to add the gdm fix…

3

Ok, understood, will try today later.
Thank you.

4

Unfortunately, not yet good result.
I tried as you suggested - driver compiled from source, installed and fix applied “-igf” without any issues.
However, still - can’t see Login screen (only grey screen, seems backlight is on).
Symptoms are the same as I install fglrx from repo.

Here is the Xorg log what I have right after system started (after compilation/installation and apply “-igf”) - http://cutpi.com/tvw
I really don’t know - Where to look at now ?

5

Hi
Hmm, not sure then, didn’t see any (EE) entries in your log. Is autologin set? If so disable that and install lightdm and set the displaymanager to use that instead of GDM. You can do both of the displaymanager changes via YaST /etc/sysconfig editor, press ctrl+alt+F1 to get to a tty and use the ncurses version of YaST to install and configure.

6

Hi
Autologin - is off.

I got small progress: installed lightdm, switched to it (vi /etc/sysconfig/displaymanager), rebooted, and I able to see login screen, however Gnome session didn’t run.
IceWM session - run succesfully.

When I try to run Gnome session (I need gnome), it shows on white background error like - “Oh, no. Something went wrong.” and “Logout” button.

In what log file I can find what went wrong with gnome-session ?

7

On Thu 12 May 2016 11:56:01 AM CDT, khilov wrote:

Hi
Autologin - is off.

I got small progress: installed lightdm, switched to it (vi
/etc/sysconfig/displaymanager), rebooted, and I able to see login
screen, however Gnome session didn’t run.
IceWM session - run succesfully.

When I try to run Gnome session (I need gnome), it shows on white
background error like - “Oh, no. Something went wrong.” and “Logout”
button.

In what log file I can find what went wrong with gnome-session ?

Hi
And your sure the system is all up to date?


zypper ref -f
zypper -t patch
zypper up

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.20-11-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

8

On Thu 12 May 2016 08:21:19 PM CDT, malcolmlewis wrote:

[QUOTE]
On Thu 12 May 2016 11:56:01 AM CDT, khilov wrote:

Hi
Autologin - is off.

I got small progress: installed lightdm, switched to it (vi
/etc/sysconfig/displaymanager), rebooted, and I able to see login
screen, however Gnome session didn’t run.
IceWM session - run succesfully.

When I try to run Gnome session (I need gnome), it shows on white
background error like - “Oh, no. Something went wrong.” and “Logout”
button.

In what log file I can find what went wrong with gnome-session ?

Hi
And your sure the system is all up to date?


zypper ref -f
zypper -t patch
zypper up

[/QUOTE]
Hi
Here is the related bug report;
https://bugzilla.opensuse.org/show_bug.cgi?id=955167

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.20-11-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

9

Hi
thank you for your answers.
Yes, system is up-to-date, this is first what I do after new OS installed.

Interesting bug report.
After reading it I checked gdm processes in the system (when gdm shows grey greeting screen to me).
Here they are:

root 977 1 0 01:23 ? 00:00:00 /usr/sbin/gdm
root 1003 977 1 01:23 tty7 00:00:06 /usr/bin/Xorg :0 -background none -noreset -verbose -logverbose 7 -core -auth /run/gdm/auth-for-gdm-bR7bsD/database -seat seat0 -nolisten tcp vt7
root 1098 977 0 01:23 ? 00:00:00 gdm-session-worker [pam/gdm-launch-environment]
gdm 1106 1098 0 01:23 ? 00:00:00 /usr/bin/gnome-session --autostart /usr/share/gdm/greeter/autostart --debug
gdm 1126 1106 0 01:23 ? 00:00:00 /usr/lib/gnome-settings-daemon-3.0/gnome-settings-daemon

Thus, Xorg in my system is not failed at all (especially with a stacktrace), and keep running, I believe I experience different problem.
As you can see, I enable gdm debug.

When I try to run Gnome session, I constantly see next error message in the log:

gnome-session[1077]: DEBUG(+): GsmManager: Client added: /org/gnome/SessionManager/Client2
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 141 (RANDR)
Minor opcode of failed request: 13 (RRChangeOutputProperty)
Value in failed request: 0x77
Serial number of failed request: 329
Current serial number in output stream: 331
gnome-session[1077]: DEBUG(+): GsmAutostartApp: (pid:1146) done (status:1)
gnome-session[1077]: DEBUG(+): emitting SessionIsActive

Could this be root of the problem ?

I put logs here: http://cutpi.com/fdm
BTW, /etc/X11/xorg.cong - is removed for the moment.

PS: xfce works good also.

10

Hi
What I need to do is re-install openSUSE Leap 42.1 on my HP, I may not be able to get around to that until the weekend.

11

Hi
OK, confirmed and created a bug https://bugzilla.opensuse.org/show_bug.cgi?id=980195 feel free to add yourself and own comments as well (give some more priority the more folks speak up on it :wink: )

12

Hi
Thank you for confirming issue, will continue in Bugzilla.