cancel
Showing results for 
Search instead for 
Did you mean: 
ArchivedThis topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.
mostlyharmless
New member
3 2 0 0
Message 1 of 4
2,371
Flag Post

Authorization fails on Linux after kernel 4.5, rgsmbiosreader error

HP Recommended
RGS Receiver
Linux

Lately I noticed that both older versions of RGS Receiver eg 7.2.3, as well as newer eg 7.3.2 no longer can authenticate advanced features for Linux kernels 4.5 and over.  I've only managed to narrow it down between a change in kernel 4.5.0rc1 and 4.5.0, but, sadly I don't have the source or patches around this release in order to bisect it further.  

 

The failiure occurs because the HP binary rgsmbiosreader fails to run under the newer kernels.  The error is

Exception Caught. Failed to initialize WSTL. Are you running with administrator privlidges? Error mapping memory! Address: ac3fb000 size: 4096

Note that the binary has to be run as root to get this message.  Not running as root gets the usual error of "Must be administrator/root to run"  This is NOT a permissions error.  Running the binary, as root, under kernels <4.5 provides the system uuid.  Apparently the system ID is placed in the file opt/hpremote/registration/H264. 

 

There is a workaround.  Executing the following code

sudo dmidecode -t 1 | grep UUID | tr A-z a-z | tr -d - | cut -c8-80 > opt/hpremote/registration/H264

duplicates the output of "#rgsmbiosreader -u""  Then one can replace the binary rgsmbiosreader with a simple script that simply echoes this file, ie

#!/bin/sh
cat /opt/hpremote/registration/H264

Name the script rgsmbiosreader (you can save the original binary under some other name) and make it executable with chmod +x rgsmbiosreader

 

Now authenticating works again.  Needless to say, it'd be nice to have HP fix their binary, or better yet, use dmidecode to get the system uuid if they want instead of their (broken) binary.

0 Kudos
3 REPLIES 3
KellyRGS
Level 7
Level 7
541 534 41 51
Message 2 of 4
Flag Post
HP Recommended

Thank you for the information.  I have copied your question and looking into this.  What version of Linux are you using, and what kernel?

 

I work on the behalf of HP.

I am an HP employee.
0 Kudos
mostlyharmless
Author
New member
3 2 0 0
Message 3 of 4
Flag Post
HP Recommended
Client side, I'm using Arch, but have duplicated this issue with Ubuntu and a few others. As I mentioned, the change occurred during the kernel 4.5.0 development, and should be distro independent. Arch is rolling release, and is currently on kernel 4.9 or 4.10. The server is Windows 7.

The same problem occurs in a virtual machine under KVM with any Linux version I've tested.
0 Kudos
KellyRGS
Level 7
Level 7
541 534 41 51
Message 4 of 4
Flag Post
HP Recommended

Thank you for the additional information.  Will look into this.

I work on the behalf of HP.

I am an HP employee.
0 Kudos
ArchivedThis topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation