Testing KLV-vmHost, Designed for Hosting VM's

[rockedge]

@JusGellin Can you set the computer up for legacy boot (BIOS)? I saw this problem with the HDD device/partition names before recently. Trouble with solid state hard drives and the naming convention.

Surprised we can't get KLV to boot. Perhaps experiment with turning off the EFI boot if it is at all possible. I will have to look at the problem and the machine your using for this a bit closer.

I think the problem is with the 512GB M.2 PCIe NVMe Solid State Drive and recognizing it. Somewhere on this forum this was discussed recently........

I am leaning towards the kernel modules are not loading or the kernel is not configured for NVMe usage as being a cause. More research is ongoing.....

UPDATE: some research led me to some info coming from some guys experiencing the same issues:

For anybody else who comes across this thread trying to solve Dell NVMe SSD issues as I did, I just wanted to add that I was able to solve the issue by switching the SATA Operation from "RAID" to "AHCI" in the BIOS. I did not want to disable the SATA bus altogether, as I have a couple non-RAIDed SATA drives plugged in.

I should also note this was on an Optiplex 7040 desktop tower, and also that I only ran into this issue when using UEFI boot mode. I did not have any issues with the BIOS in "Legacy boot" configuration.

Original post -> https://bbs.archlinux.org/viewtopic.php?id=204629

Another piece of info:

The fix for me was as follow:

Enable VDM in the bios
Enable CSM and allow legacy boot devices
Completely wipe the driver
Boot off the 21.1.5 image and then the drive was detected and allowed installation of manjaro.

[JusGellin]

Changing from RAID to AHCI made it work!
Thanks so much!

@JusGellin Can you set the computer up for legacy boot (BIOS)? I saw this problem with the HDD device/partition names before recently. Trouble with solid state hard drives and the naming convention.

JusGellin wrote - (The laptop has a note in its bios: NOTE: Legacy Boot mode is not supported on this platform)

Surprised we can't get KLV to boot. Perhaps experiment with turning off the EFI boot if it is at all possible. I will have to look at the problem and the machine your using for this a bit closer.

I think the problem is with the 512GB M.2 PCIe NVMe Solid State Drive and recognizing it. Somewhere on this forum this was discussed recently........

I am leaning towards the kernel modules are not loading or the kernel is not configured for NVMe usage as being a cause. More research is ongoing.....

UPDATE: some research led me to some info coming from some guys experiencing the same issues:

For anybody else who comes across this thread trying to solve Dell NVMe SSD issues as I did, I just wanted to add that I was able to solve the issue by switching the SATA Operation from "RAID" to "AHCI" in the BIOS. I did not want to disable the SATA bus altogether, as I have a couple non-RAIDed SATA drives plugged in.

JusGellin wrote - (This made it work by changing from RAID to AHCI)

I should also note this was on an Optiplex 7040 desktop tower, and also that I only ran into this issue when using UEFI boot mode. I did not have any issues with the BIOS in "Legacy boot" configuration.

Original post -> https://bbs.archlinux.org/viewtopic.php?id=204629

[rockedge]

@JusGellin keep us in the loop on your progress

[JusGellin]

I want to understand how to use this better now that it works on my new laptop.

Should I be able to install software if I want?
I tried to install lshw since it wasn't found.
But the install gave an error

bash-5.2# xbps-install -S lshw
[*] Updating repository `https://mirror.clarkson.edu/voidlinux/c ... 4-repodata' ...
ERROR: [reposync] failed to fetch file `https://mirror.clarkson.edu/voidlinux/c ... 4-repodata': Transient resolver failure
[*] Updating repository `https://mirror.clarkson.edu/voidlinux/c ... 4-repodata' ...
ERROR: [reposync] failed to fetch file `https://mirror.clarkson.edu/voidlinux/c ... 4-repodata': Transient resolver failure

Name Action Version New version Download size
lshw install - B.02.19.2_2 2026KB

Size to download: 2026KB
Size required on disk: 7719KB
Space available on disk: 15GB

Do you want to continue? [Y/n]

[*] Downloading packages
ERROR: [trans] failed to download `lshw-B.02.19.2_2' signature from `https://mirror.clarkson.edu/voidlinux/current': Transient resolver failure
Transaction failed! see above for errors.
bash-5.2#

How can I do this?

Thanks

[rockedge]

@JusGellin There has been some change to the Void Linux repo URL's.

Also possible is the entire Void Linux repo's are being updated and building upgraded packages......wait a while and try again.

open /etc/xbps.d/00-repository-main.conf
change the URL to this:

Code: Select all

repository=https://repo-default.voidlinux.org/current

open /etc/xbps.d/10-repository-nonfree.conf
change the URL to this:

Code: Select all

repository=https://repo-default.voidlinux.org/current/nonfree

open a terminal and:

Code: Select all

xbps-install -S

Now try to install the package.

[JusGellin]

Can you see the egg on my face?
When this was able to boot up, I forgot about the wifi connection!
Would it be possible to have the network connection show up right away in the bottom right bar?

But I haven't been able to get the wifi to work yet - at least for KLV-vmHost.
When I realized this, one of the things I did to verify that it would work was to boot into BookwormPup.
I was able to get wifi connected doing that.

For the booting to KLV-vmHost:
I selected the Advanced Network Configuration from the Settings menu
(I've successfully done this for KLV-vmHost on another laptop and re-verified I still could do it on that laptop - it works)
It has the default Bridge connection to virb0 - I delete that and it tells me that the network connection has been disconnected.
Next I add wifi and set SSID and security to WPA/WPA2/WPA3 Personal - enter password.
But it doesn't connect like my other laptop did.
If I right click on the network icon on the bottom right bar, the Connection Information is greyed out.
The network connection check box is checked.

If I reboot and save the session, when it comes up it once again gets the Bridge connection along with my wifi connection - but is connected to Bridge connection not the wifi
It seems to want to connect to Bridge - virbr0 again on the reboot.
I can't make it connect it to wifi.

So wifi definately works if I use BookwormPup
KLV-vmHost seems to insist on connecting to Bridge - virbr0 instead of my added wifi connection.

How can I troubleshoot further?
Thanks

[JusGellin]

When I rebooted the next time and both the wifi and again bridge-virbr0 came up,
from the terminal ran ip addr
It only showed vibr0 connecected (besides the loopback)

When I deleted vibr0 in Network Connections,
It still showed up in ip addr.

For some reason it won't let go of the Bridge-vibr0 connection.

Thanks

[rcrsn51]

@JusGellin Is this the same machine as the one in the other thread with the vesa video problem? Does this mean that you have at least found a platform that supports your modern graphics hardware?

[JusGellin]

@JusGellin Is this the same machine as the one in the other thread with the vesa video problem? Does this mean that you have at least found a platform that supports your modern graphics hardware?

Yes, it is.
I wasn't even able to boot this laptop up with it until @rockedge found information that made it boot up.

Then, when it came up it has the many display resolutiion settings including the max settting.
So this one works right for display resolutions on that machine.

Now I need to get the wifi working.

[rockedge]

@JusGellin Let's try a trick...
open a terminal and type:

Code: Select all

nmtui

use the keyboard to navigate to make the selections and add the passphrase

[JusGellin]

@rockedge
That's the same as what I put into Advanced Network Configuration for wifi
But every time I reboot, Bridge - virbr0 comes up also.

I tried to activate the wifi with that command, but it only allows the virb0 to be activated.

Even if I delete that connection
If I try to activate wifi, it doesn't show up there.

But still BW connects to wifi and the virb0 doesn't show up.

[JusGellin]

I booted up BW from usb.
It connects to wifi

I tried running nmtui.
It says "NetworkManager is not running"

So is it doing wifi differently?

[rockedge]

Yes, I think Bookwormpup uses ConnMan.

KLV uses Networkmanager. nmtui is for KLV variants.

[JusGellin]

@rockedge
Is there anything else I could look at or try?

It seems like Debian types are able to connect to wifi, like BookwormPup and LinuxMintLMDE
Also AlpineLinux is able to connect.

I tried a few KLA that wouldn't come up or the mouse cursor would freeze.
Most of these were done using Ventoy.

My laptop isn't doing very well for how powerful it is.
It must need that power to run Win11.

[JusGellin]

@rockedge
It seems that there might be something not working when I use the Settings -> Advanced Network Configuration
When I add Wi-FI to it, it takes the settings but doesn't connect.
I can't get it to turn it on.

Then when I reboot and go back to it, it defaults to ethernet again.
It's like the ethernet connection is stuck to it.

Could you look at it? That should make this work properly.

Thanks

[JusGellin]

@rockedge
I tested with newer kernels.
One was Linux Mint which has 6.8 - that worked well on my laptop for both display resolutions and wifi.
That beats Alpine Linux which has kernel 6.6. I can't change the resolutions.

So that is the minimum kernel that I've found so far that works for me which is 6.8.

This KLV is 6.10 so it's wifi should work also.

Thanks

[fredx181]

@rockedge
It seems that there might be something not working when I use the Settings -> Advanced Network Configuration
When I add Wi-FI to it, it takes the settings but doesn't connect.
I can't get it to turn it on.

Then when I reboot and go back to it, it defaults to ethernet again.
It's like the ethernet connection is stuck to it.

Could you look at it? That should make this work properly.

Thanks

Not sure if I understand your problem, how I connect to Wi-Fi is left click on the small empty space on the left to the speaker icon.
(unfortunately, for me, the icon is missing, may be because I have no ethernet on my laptop )
edit: but as soon as I get connection the wifi icon shows there.

Screenshot_2024-11-10_14-44-17.png (188.36 KiB) Viewed 437 times

[JusGellin]

Not sure if I understand your problem, how I connect to Wi-Fi is left click on the small empty space on the left to the speaker icon (unfortunately the icon is missing, may be because I have no ethernet on my laptop )
edit: but as soon as I get connection the wifi icon shows there.

Screenshot_2024-11-10_14-44-17.png

When I right click there it has:
greyed out No network devices available and
VPN Connections

I'm able to do what you said on other ones like BookwormPup ok, so I know it works. Just not with KLV-vmHost
When I run ip addr on the KLV, no wifi shows up.

Thanks

[fredx181]

Not sure if I understand your problem, how I connect to Wi-Fi is left click on the small empty space on the left to the speaker icon (unfortunately the icon is missing, may be because I have no ethernet on my laptop )
edit: but as soon as I get connection the wifi icon shows there.
Screenshot_2024-11-10_14-44-17.png

When I right click there it has:
greyed out No network devices available and
VPN Connections

I'm able to do what you said on other ones like BookwormPup ok, so I know it works. Just not with KLV-vmHost
When I run ip addr on the KLV, no wifi shows up.

Thanks

Ah, ok, then probably the firmware that you need for wifi is not included in KLV-vmHost .

[JusGellin]

@fredx181
It works on another model laptop I have.
Just not on my new laptop.

Thanks

[fredx181]

@fredx181
It works on another model laptop I have.
Just not on my new laptop.

Thanks

Try to find what's the wifi adapter on your new laptop: lspci | grep -i net or perhaps lspci | grep -i wireless and post the outcome here.
I'm no good with these things, perhaps @rockedge knows then what firmware needed for it (edit: or it may be a kernel module).

[rockedge]

I will look at this in a few moments.....I must feed my 2 cats...they are staging a coup........

[fredx181]

I will look at this in a few moments.....I must feed my 2 cats...they are staging a coup........

Your cats will probably know the solution, after they're fed of course ...

[JusGellin]

Running this from this KLV gives:

Code: Select all

bash-5.2# lspci
00:08.0 Class 0880: 8086:a74f
00:15.1 Class 0c80: 8086:51e9
00:1f.0 Class 0601: 8086:519d
00:04.0 Class 1180: 8086:a71d
00:14.3 Class 0280: 8086:51f1
00:16.0 Class 0780: 8086:51e0
01:00.0 Class 0108: 144d:a80f
00:1f.5 Class 0c80: 8086:51a4
00:1f.3 Class 0403: 8086:51ca
00:00.0 Class 0600: 8086:a708
00:12.0 Class 0700: 8086:51fc
00:15.0 Class 0c80: 8086:51e8
00:06.0 Class 0604: 8086:a74d
00:14.2 Class 0500: 8086:51ef
00:02.0 Class 0300: 8086:a7ac
00:14.0 Class 0c03: 8086:51ed
00:1f.4 Class 0c05: 8086:51a3
bash-5.2# 

So I did it from BookwormPup:

Code: Select all

lspci | grep -i net
00:14.3 Network controller: Intel Corporation Raptor Lake PCH CNVi wifi (rev 01)

[fredx181]

Running this from this KLV gives:
...

Strange IMHO that lspci gives only that and no clear info , e.g. network controller, graphics etc.. (edit: see EDIT below)

So I did it from BookwormPup:

Code: Select all

lspci | grep -i net
00:14.3 Network controller: Intel Corporation Raptor Lake PCH CNVi wifi (rev 01)

That's much better !

EDIT: I see now that the lspci version in KLV-vmHost is link to busybox, to get better (verbose) output, the "full" lspci is required, install pciutils

[JusGellin]

EDIT: I see now that the lspci version in KLV-vmHost is link to busybox, to get better (verbose) output, the "full" lspci is required, install pciutils

It doesn't have that command.

[fredx181]

@JusGellin
I meant the package pciutils.

[JusGellin]

Finally! I got this to work on my new laptop.

Here's the story:
I studied and compared different installs on this and on another laptop that everything seems to work on.
I looked at all the settings I could from the terminal commands.

The problem I had was that this new laptop which has an Intel Core 7 processor and Raptor Lake Graphics and Network.
I compared this KLV-vmHost install with BookwormPup64_10.0.8 on this.

The KLV would work ok with the graphic resolutions but the network wouldn't work. I could set it up for wifi, but the the Advanced Network Configuraton wouldn't do anything to connect.
So I wasn't able to even install anything because it couldn't get on the internet.
The BW would not work with the graphic resolutions but the network would work.

I went through a lot to at least try to understand these better and came down to the suggestions I received to try changing the firmware
first directly at /lib/firmware, which I couldn't get to work right and even would lose the network on BW.

Also, I tried the suggestion to change the fdrv to another one from a link. This also would make BW loose any ability to connect to wifi.

So I thought, since BW had its wifi connection why not try using its fdrv and copy it over to the KLV, rename it for the KLV.
When I did that, the display resolutions still worked and when I set the wifi up, that worked well!

I'm not sure what else may or may not work on this.
What I now have is for this KLV-vmHost is a kernel 6.10.10 and firmware from Bookworm for its kernel of 6.1.106.

I kind of think this really isn't the right way to accomplish this, but so far this is best I can do.

[rockedge]

My answer to that! -> viewtopic.php?p=135660#p135660

[JusGellin]

The real solution to solve the no wifi problem on my Dell laptop:
Looking at dmesg the error shows the wifi failed not due to iwlwifi-so-a0-gf-a0-89.ucode.
Another line specifically indicates the problem:
iwlwifi 0000:00:14.3: PNVM data is missing, please install iwlwifi-so-a0-gf-a0.pnvm

Since Bookworm wifi worked, I used its iwlwifi-so-a0-gf-a0.pnvm, which made it work.

So, I'm thinking the problem is that the 01firmware...sfs needs to have the one that comes with iwlwifi-so-a0-gf-a0-89.ucode.
That would make the firmware sfs work if iwlwifi-so-a0-gf-a0-89.ucode is used for any computer.

Could that be included in the firmware?
Also does it matter that the firmware used here inidicates it's for 6.9.1 -> 01firmware-6.9.1_1.sfs?
Yet, uname -r is indicating 6.10.10_1 for the kernel.

Thanks