Display is not loaded after SP3 update

SUSE Linux Enterprise Desktop SLED Updates
21

Hi
Interesting, the repo appears to be present?

Use;

zypper -R qrm x11-video-fglrxG02-HP

Can you post the output from;

uname -a

You can use the if(info) switch;

zypper if kernel-default

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.1 Kernel 3.11.10-21-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

22

[QUOTE=malcolmlewis;24098]Hi
Interesting, the repo appears to be present?[/QUOTE]

Seems so. Here you’re the output of zypper lr, nothing unusual, right?

zypper lr
#  | Alias                                     | Name                                                  | Enabled | Refresh
---+-------------------------------------------+-------------------------------------------------------+---------+--------
 1 | /home:DarkPlayer:Pipelight.repo           | /home:DarkPlayer:Pipelight.repo                       | Yes     | Yes    
 2 | ATI-Driver-SLE11-SP3                      | ATI-Driver-SLE11-SP3                                  | Yes     | Yes    
 3 | HP-BNB-Dedicated-Update-Channel           | HP-BNB-Dedicated-Update-Channel                       | Yes     | Yes    
 4 | SLED11-SP3-SDK                            | SUSE Linux Enterprise Software Development Kit 11 SP3 | Yes     | No     
 5 | nVidia-Driver-SLE11-SP3                   | nVidia-Driver-SLE11-SP3                               | Yes     | Yes    
 6 | nu_novell_com:SLE11-SDK-SP1-Pool          | SLE11-SDK-SP1-Pool                                    | No      | Yes    
 7 | nu_novell_com:SLE11-SDK-SP1-Updates       | SLE11-SDK-SP1-Updates                                 | No      | Yes    
 8 | nu_novell_com:SLE11-SDK-SP2-Core          | SLE11-SDK-SP2-Core                                    | No      | Yes    
 9 | nu_novell_com:SLE11-SDK-SP2-Updates       | SLE11-SDK-SP2-Updates                                 | No      | Yes    
10 | nu_novell_com:SLE11-SDK-SP3-Pool          | SLE11-SDK-SP3-Pool                                    | Yes     | Yes    
11 | nu_novell_com:SLE11-SDK-SP3-Updates       | SLE11-SDK-SP3-Updates                                 | Yes     | Yes    
12 | nu_novell_com:SLE11-SP1-Debuginfo-Pool    | SLE11-SP1-Debuginfo-Pool                              | No      | Yes    
13 | nu_novell_com:SLE11-SP1-Debuginfo-Updates | SLE11-SP1-Debuginfo-Updates                           | No      | Yes    
14 | nu_novell_com:SLE11-SP2-Debuginfo-Core    | SLE11-SP2-Debuginfo-Core                              | No      | Yes    
15 | nu_novell_com:SLE11-SP2-Debuginfo-Updates | SLE11-SP2-Debuginfo-Updates                           | No      | Yes    
16 | nu_novell_com:SLED11-Extras               | SLED11-Extras                                         | Yes     | Yes    
17 | nu_novell_com:SLED11-SP1-Pool             | SLED11-SP1-Pool                                       | No      | Yes    
18 | nu_novell_com:SLED11-SP1-Updates          | SLED11-SP1-Updates                                    | No      | Yes    
19 | nu_novell_com:SLED11-SP2-Core             | SLED11-SP2-Core                                       | No      | Yes    
20 | nu_novell_com:SLED11-SP2-HP-BNB-Updates   | SLED11-SP2-HP-BNB-Updates                             | No      | Yes    
21 | nu_novell_com:SLED11-SP2-Updates          | SLED11-SP2-Updates                                    | No      | Yes    
22 | nu_novell_com:SLED11-SP3-Pool             | SLED11-SP3-Pool                                       | Yes     | Yes    
23 | nu_novell_com:SLED11-SP3-Updates          | SLED11-SP3-Updates                                    | Yes     | Yes

[QUOTE]Use;

zypper -R qrm x11-video-fglrxG02-HP [/QUOTE]
That one didn’t work

zypper -R qrm x11-video-fglrxG02-HP
The path specified in the --root option must be absolute.

[QUOTE]
Can you post the output from;

uname -a [/QUOTE]
Here it is

uname -a
Linux linux-moati 3.0.101-0.7.17-default #1 SMP Tue Feb 4 13:24:49 UTC 2014 (90aac76) x86_64 x86_64 x86_64 GNU/Linux

No info on why it is not installed, is there?

Information for package kernel-default:

Repository: SLED11-SP3-Updates
Name: kernel-default
Version: 3.0.101-0.35.1
Arch: x86_64
Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany
Support Level: Level 3
Installed: Yes
Status: out-of-date (version 3.0.101-0.7.17.1 installed)
Installed Size: 82.2 MiB
Summary: The Standard Kernel
Description: 
The standard kernel for both uniprocessor and multiprocessor systems.


Source Timestamp: 2014-07-09 13:43:04 +0200
GIT Revision: c36987dc9f1f1f7fc8b2be8cc756cadf4b52002e
GIT Branch: SLE11-SP3

Thanks,
Ahmed

23

Hi
Oops there was a q there;

zypper -R rm x11-video-fglrxG02-HP

After it’s gone, fire up YaST software repositories and disable 2 and 5.

Or via zypper;

zypper mr -d 2
zypper mr -d 5
zypper ref

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.1 Kernel 3.11.10-21-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

24

[QUOTE=malcolmlewis;24100]Hi
Oops there was a q there;

zypper -R rm x11-video-fglrxG02-HP [/QUOTE]

Same thing, I got the same error.

zypper -R rm x11-video-fglrxG02-HP
The path specified in the --root option must be absolute.

Thanks,
Ahmed

25

Hi
Hmmm, what if you use YaST Software Management, search for it and
uncheck the box.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.1 Kernel 3.11.10-21-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

26

[QUOTE=malcolmlewis;24215]Hi
Hmmm, what if you use YaST Software Management, search for it and
uncheck the box.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.1 Kernel 3.11.10-21-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks![/QUOTE]

It is not there either! As if it disappeared!

But are we sure that the zypper update problem is related to the fglrx driver?

Thanks,
Ahmed

27

Hi
Apologize for the delay, hmmm maybe clean the zypper database and see

zypper cc -a
zypper ref -bd
zypper patch
zypper up

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-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!

28

[QUOTE=malcolmlewis;24564]Hi
Apologize for the delay, hmmm maybe clean the zypper database and see

zypper cc -a
zypper ref -bd
zypper patch
zypper up

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-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![/QUOTE]

Got the below error when I ran zypper patch

 zypper cc -a
All repositories have been cleaned up.
linux-moati:/home/aabdelkhalek # zypper ref -bd
Forcing raw metadata refresh
Retrieving repository '/home:DarkPlayer:Pipelight.repo' metadata [done]
Forcing building of repository cache
Building repository '/home:DarkPlayer:Pipelight.repo' cache [done]
Forcing raw metadata refresh
Retrieving repository 'ATI-Driver-SLE11-SP3' metadata [done]
Forcing building of repository cache
Building repository 'ATI-Driver-SLE11-SP3' cache [done]
Forcing raw metadata refresh
Retrieving repository 'HP-BNB-Dedicated-Update-Channel' metadata [done]
Forcing building of repository cache
Building repository 'HP-BNB-Dedicated-Update-Channel' cache [done]
Forcing raw metadata refresh
Retrieving repository 'SUSE Linux Enterprise Software Development Kit 11 SP3' metadata [done]
Forcing building of repository cache
Building repository 'SUSE Linux Enterprise Software Development Kit 11 SP3' cache [done]
Forcing raw metadata refresh
Retrieving repository 'nVidia-Driver-SLE11-SP3' metadata [done]
Forcing building of repository cache
Building repository 'nVidia-Driver-SLE11-SP3' cache [done]
Forcing raw metadata refresh
Retrieving repository 'SLE11-SDK-SP3-Pool' metadata [done]
Forcing building of repository cache
Building repository 'SLE11-SDK-SP3-Pool' cache [done]
Forcing raw metadata refresh
Retrieving repository 'SLE11-SDK-SP3-Updates' metadata [done]
Forcing building of repository cache
Building repository 'SLE11-SDK-SP3-Updates' cache [done]
Forcing raw metadata refresh
Retrieving repository 'SLED11-Extras' metadata [done]
Forcing building of repository cache
Building repository 'SLED11-Extras' cache [done]
Forcing raw metadata refresh
Retrieving repository 'SLED11-SP3-Pool' metadata [done]
Forcing building of repository cache
Building repository 'SLED11-SP3-Pool' cache [done]
Forcing raw metadata refresh
Retrieving repository 'SLED11-SP3-Updates' metadata [done]
Forcing building of repository cache
Building repository 'SLED11-SP3-Updates' cache [done]
All repositories have been refreshed.
linux-moati:/home/aabdelkhalek # zypper patch
Refreshing service 'nu_novell_com'.
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: rt3290-kmp-default-3.9.2_3.0.13_0.27-0.1.1.x86_64 requires kernel(default:kernel_printk) = 9cc1b39ddf89e9f5, but this requirement cannot be provided
  deleted providers: kernel-default-base-3.0.101-0.7.17.1.x86_64
 Solution 1: deinstallation of rt3290-kmp-default-3.9.2_3.0.13_0.27-0.1.1.x86_64
 Solution 2: do not install patch:sledsp3-kernel-9751.noarch
 Solution 3: break rt3290-kmp-default-3.9.2_3.0.13_0.27-0.1.1.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c] (c): 
linux-moati:/home/aabdelkhalek #

What do you think?

Thanks for your cooperation
Ahmed

29

Hi
Dang, so which repo is the rt3290-kmp coming from (I suspect the HP
repo);

zypper if rt3290-kmp-default

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-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!

30

[QUOTE=malcolmlewis;24566]Hi
Dang, so which repo is the rt3290-kmp coming from (I suspect the HP
repo);

zypper if rt3290-kmp-default

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-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![/QUOTE]

it is related to the bluetooth driver. I recall doing similar update before and afterwards the bluetooth didn’t work!

Information for package rt3290-kmp-default:

Repository: @System
Name: rt3290-kmp-default
Version: 3.9.2_3.0.13_0.27-0.1.1
Arch: x86_64
Vendor: openSUSE Build Service
Support Level: unknown
Installed: Yes
Status: up-to-date
Installed Size: 131.0 KiB
Summary: Kernel modules for Ralink RT3290 Bluetooth
Description: 
This package contains the kernel module driver for Ralink RT3290 Bluetooth

Authors: Kevin (kevin.chou@mediatek.com)
31

Hi
OK, so lets remove it temporarily, then can find a src rpm you can
rebuild for the updated kernel.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-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!

32

[QUOTE=malcolmlewis;24568]Hi
OK, so lets remove it temporarily, then can find a src rpm you can
rebuild for the updated kernel.[/QUOTE]

So what I did was the following:

In the zypper update options, I choose option 1 to uninstall the rt3290 package and proceeded with the update. After the update was finished, I rebooted and faced the same problem with the display which I solved as in post #4. Now, the blue tooth does not work and it says:

“Your computer does not any have Bluetooth adapters plugged in”

What do you recommend?

Thanks a lot for your help and cooperation,
Ahmed

33

Hi
So the system all updated, just don’t have bluetooth now. Your wireless
works ok?

Can you post the output from;

/sbin/lspci -nnk|grep -A2 Network
and

lsusb

My understanding is the driver was for wireless, not bluetooth. Have
you tried the wireless Fn key, sometime you have to cycle through
pressing it to enable wireless and bluetooth.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-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!

34

[QUOTE=malcolmlewis;24725]Hi
So the system all updated, just don’t have bluetooth now. Your wireless
works ok?[/QUOTE]

The system is updated. Below is the output of zypper patch and zypper update. And yes my wireless works fine and this is how I’m connected to the internet (not wired)

# zypper patch
Refreshing service 'nu_novell_com'.
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Nothing to do.

 # zypper update
Refreshing service 'nu_novell_com'.
Loading repository data...
Reading installed packages...

Nothing to do.

[QUOTE]
Can you post the output from;

[CODE]
/sbin/lspci -nnk|grep -A2 Network
and

lsusb
[/CODE][/Quote]
Here you’re

 # /sbin/lspci -nnk|grep -A2 Network
04:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290]
	Subsystem: Hewlett-Packard Company Device [103c:18ec]
	Kernel driver in use: rt2800pci

 # lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 003: ID 138a:003d Validity Sensors, Inc. 
Bus 003 Device 004: ID 1bcf:2c2a Sunplus Innovation Technology Inc.

[QUOTE]
My understanding is the driver was for wireless, not bluetooth. Have
you tried the wireless Fn key, sometime you have to cycle through
pressing it to enable wireless and bluetooth.[/QUOTE]
I tried that but nothing happens.

Thanks,
Ahmed

35

Hi
OK, so that shows the kmp that was causing the issue is not needed
anymore :wink:

OK, can you install rfkill from here and can check whether it’s
softblocked or not;

As root user;

zypper in http://download.opensuse.org/repositories/home:/draht/SLE_11_SP3_Update/x86_64/rfkill-0.5-1.11.x86_64.rpm
rfkill list

If you can post the output from the above command, hopefully the
bluetooth is present.

Another question it’s all on (as in bluetooth) in the BIOS?

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-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!

36

[QUOTE=malcolmlewis;24735]
OK, can you install rfkill from here and can check whether it’s
softblocked or not;

As root user;

zypper in http://download.opensuse.org/repositories/home:/draht/SLE_11_SP3_Update/x86_64/rfkill-0.5-1.11.x86_64.rpm
rfkill list

If you can post the output from the above command, hopefully the
bluetooth is present.

Another question it’s all on (as in bluetooth) in the BIOS?

–[/QUOTE]

Here you’re the output of rfkill list.

rfkill list
0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

I believe it is a driver problem.

Thanks,
Ahmed

37

Hi
Yes, it would appear so, I have found the source and will build a src
rpm for you to rebuild locally (to match your running kernel), it will
also blacklist your existing driver (rt2800pci) then hopefully your
bluetooth will work again.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-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!

38

Hi
OK, so I have the kmp built for the original kernel, you will need to
rebuild locally and install the resulting kmp and also blacklist the
existing driver it’s using.

We need to install some prerequisites first (open a terminal);

su -
zypper in make gcc kernel-source linux-kernel-headers kernel-syms
module-init-tools
exit

Lets grab the src rpm and rebuild the kmp (as your user, not root!)

wget -c http://download.opensuse.org/repositories/home:/malcolmlewis:/SLE_11_SPn_General/SLE_11_SP3/src/rt3290sta-2.6.0.0-2.1.src.rpm
rpmbuild --rebuild rt3290sta-2.6.0.0-2.1.src.rpm

This should produce a file;

Wrote: /usr/src/packages/RPMS/x86_64/rt3290sta-kmp-default-2.6.0.0_3.0.101_0.40-2.1.x86_64.rpm

If all is ok, we can install this, but also have to blacklist the
existing driver;

Create a text file and save as rt3290sta-blacklist;

#Wireless drivers conflicting with rt3290sta
blacklist rt2800pci
blacklist rt2x00pci

So now switch to root user and copy the blacklist file;

su -
cp <wherever_you_created_the_file>/rt3290sta-blacklist /etc/modprobe.d/
zypper in /usr/src/packages/RPMS/x86_64/rt3290sta-kmp-default*
shutdown -r now

So on reboot, hopefully your wireless is up and running as well as your
bluetooth, you can check the output from rfkill as well.

If your wireless doesn’t come back, just delete the blacklist file and
reboot to enable the old driver.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-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!

39

[QUOTE=malcolmlewis;24774]Hi
OK, so I have the kmp built for the original kernel, you will need to
rebuild locally and install the resulting kmp and also blacklist the
existing driver it’s using.

We need to install some prerequisites first (open a terminal);

su -
zypper in make gcc kernel-source linux-kernel-headers kernel-syms
module-init-tools
exit

Lets grab the src rpm and rebuild the kmp (as your user, not root!)

wget -c http://download.opensuse.org/repositories/home:/malcolmlewis:/SLE_11_SPn_General/SLE_11_SP3/src/rt3290sta-2.6.0.0-2.1.src.rpm
rpmbuild --rebuild rt3290sta-2.6.0.0-2.1.src.rpm

This should produce a file;

Wrote: /usr/src/packages/RPMS/x86_64/rt3290sta-kmp-default-2.6.0.0_3.0.101_0.40-2.1.x86_64.rpm

If all is ok, we can install this, but also have to blacklist the
existing driver;

Create a text file and save as rt3290sta-blacklist;

#Wireless drivers conflicting with rt3290sta
blacklist rt2800pci
blacklist rt2x00pci

So now switch to root user and copy the blacklist file;

su -
cp <wherever_you_created_the_file>/rt3290sta-blacklist /etc/modprobe.d/
zypper in /usr/src/packages/RPMS/x86_64/rt3290sta-kmp-default*
shutdown -r now

So on reboot, hopefully your wireless is up and running as well as your
bluetooth, you can check the output from rfkill as well.

If your wireless doesn’t come back, just delete the blacklist file and
reboot to enable the old driver.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-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![/QUOTE]

I tried following this procedure and unfortunately the wireless driver stopped working and of course the bluetooth didn’t work.

I deleted the blacklist file and restarted but I don’t know why but the old driver was not restored and I had to look for a cable to connect to the internet.

Here’s the output of the rfkill list. There was no response so I suspected that I ran the correct command!

# rfkill list
# 
# 
# rfkill 
Usage:	rfkill [options] command
Options:
	--version	show version (0.5)
Commands:
	help
	event
	list [IDENTIFIER]
	block IDENTIFIER
	unblock IDENTIFIER
where IDENTIFIER is the index no. of an rfkill switch or one of:
	<idx> all wifi wlan bluetooth uwb ultrawideband wimax wwan gps fm nfc
# rfkill list
#

While following the procedure, the command module-init-tools was not found and I ignored that, thinking that if it was not found, the build would not be successful

I checked that package and it is there

zypper if module-init-tools
Refreshing service 'nu_novell_com'.
Loading repository data...
Reading installed packages...


Information for package module-init-tools:

Repository: SLED11-SP3-Pool
Name: module-init-tools
Version: 3.11.1-1.28.5
Arch: x86_64
Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany
Support Level: Level 3
Installed: Yes
Status: up-to-date
Installed Size: 488.0 KiB
Summary: Utilities to Load Modules into the Kernel
Description: 
Utilities for loading kernel modules. Included are 'insmod', 'lsmod',
'rmmod', 'depmod', and 'modprobe'. The configuration file
/etc/modprobe.* can be used to pass parameters to the modules. 'depmod'
should be used after compiling a new kernel to generate the dependency
information. 'insmod' does not use the dependency nor the options file.
Therefore, 'modprobe' is normally used to load a module.

Thanks,
Ahmed

40

Hi
Can you post the output from;

zypper se kmp
ls /etc/modprobe.d/

At what point in the process did it not find the module-init-tools?

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-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!