Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
My virtual Linux guest has stopped using correct screenresol
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
thurnax
Tux's lil' helper
Tux's lil' helper


Joined: 17 Apr 2014
Posts: 90

PostPosted: Sat Nov 04, 2017 2:08 pm    Post subject: My virtual Linux guest has stopped using correct screenresol Reply with quote

I used to have a properly working Linux guest under VMWare workstation/Player until recently. By 'properly working' I mean that the GRUB boot menu and the ensuing boot process through OpenRC are shown in a 1680x1050 resolution screen. Once it is booted up, drivers (possibly kernel drivers) convey the available screen resolution from the size of the window that the guest is running in and dynamically adjusts the screen resolution as I resize the window or entering/leaving full screen mode on my host machine.

Now, none of that works. The GRUB and the OpnNRC is now in some 640x480 resolution and the KDE Plasma 5 desktop is using some strange default low-res VESA screen.

The event that led to this faulty state of the machine was when I accidentally unmerged bintools as an attempt to remove the old version of binutils. That broke the toolchain so I had to boot from a Gentoo LiveCD/DVD and recompile the bintools from there. I managed to clean out the old version of bintools in the end. However, since the rebuild from the LiveCD, the screen resolution is now broken.

The drivers for handling the KDE screen are provided through a virtual CDROM containing vmware-tools or from an overlay repository named 'vmware' that I reached via the Layman tool. The problem with these tools start when running the vmware-config-tools perl script as it doesn't accept neither '/usr/bin/gcc' as a proper binary for the gcc compiler nor '/usr/src/linux' as proper kernel headers even though I have built them. The perl scipt can be accessed here or through the command 'curl http://termbin.com/xs8p' in the Bash shell for use in favourite text editor of choice.
Back to top
View user's profile Send private message
nokilli
Apprentice
Apprentice


Joined: 25 Feb 2004
Posts: 195

PostPosted: Sat Nov 04, 2017 2:57 pm    Post subject: Reply with quote

Gentoo has ebuilds for vmware stuff including vmware-tools. You're saying that you're getting vmware-tools from virtual CD-ROM or via layman, why complicate this? Why not just emerge vmware-tools from within the guest?

Also, the Gentoo LiveCD is ancient by ebuild standards, we're all supposed to use sysrescuecd for drydocking like this. No doubt a whole ton of issues creeped into your system as a result.

In your situation I would emerge -e @world at this point. Or at least make sure that vmware-tools, et al, are in your world file and do a emerge -uDNav @world.
_________________
Today is the first day of the rest of your Gentoo installation.
Back to top
View user's profile Send private message
thurnax
Tux's lil' helper
Tux's lil' helper


Joined: 17 Apr 2014
Posts: 90

PostPosted: Sun Nov 05, 2017 1:36 am    Post subject: Reply with quote

The vmware packages aren't maintained within the main repositories of Gentoo as far as I understand. As for vmware-tools, older packages are available through the main repository but they have been masked due to alleged security issues. According to instructions, it was suggested to get the packages through the so called overlay. After conducting some research about overlay I found the tool called 'layman' and I found a repository named 'vmware' which I assume is the repository that these instructions referred to. I have added the vmware repository and emerge the latest package through 'emerge -a vmware-tools::vmware'.

Irregardless of source and versioning, that 'vmware-config-tools' perl script I pasted in my prior post probably must be run, it appears. This perl script apparently compiles the required drivers for the virtual hardware to be properly initialized in the guest environment into the kernels. I cannot understand how a re-emerge of the binutils packages has managed to corrupt the linux kernel and the grub boot menu prior to that kernel.

I did another update using -avuND world. The pyflakes / flake8 package conflict has come up once again and pycharm fails to install but I guess they are not essential for the drivers and the screen resolution. Now KDE doesn't even start, I have a black screen.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum