Page 4 of 4
Re: Testing KLV-vmHost, Designed for Hosting VM's
Posted: Sun Nov 17, 2024 3:34 pm
by rockedge
Also does it matter that the firmware used here indicates it's for 6.9.1 -> 01firmware-6.9.1_1.sfs?
No not really.
I had to use the last Puppy Linux woof-CE kernel-kit produced firmware (fdrv) to assemble 01firmware-6.9.1_1.sfs. I couldn't get the kernel-kit to produce any usable fdrv after this version. The fdrv always shows up at the end around 4000 K and totally useless. Turns out this one works well with the Void Linux 6.10.10_1 kernel.
See speed was the main factor.....I was going to produce this distro in about an hour and a half and use a newer Void Linux kernel extracted during the build process.
Since there is NO reliable program/script that filters down the size of the complete firmware collection I went with the much smaller fdrv converted manually to 01firmware, and not try to manually pick out what firmware where.
You can use the 01firmware.sfs as an uncompressed (un-squashed) directory and boot the system that way. Makes it much easier to work with. Like adding firmware to it and immediately testing it without having to squash it again.
Show me what to add and I will assemble another 01firmware.sfs if in doubt.
My main dev machine is a Dell PowerEdge rack server.......horrible graphics card....since it's an industrial grade rack server which is designed to run 99% of the time headless, it doesn't need anything but 1280x1024 and ASCII so it's outfitted with MATOX graphics card.....many Puppy Linux fdrv's do not contain any firmware for it. So When I am making stuff...graphics always has to be tested on some other machine.
Re: Testing KLV-vmHost, Designed for Hosting VM's
Posted: Sun Nov 17, 2024 4:16 pm
by JusGellin
@rockedge
I like that you make it as small as you can.
I would like to give it a try.
But as far as the 01firmware is concerned, from what happened to me is in order for my new computer use so-a0-gf-a0-89.ucode,
it failed until I could copy so-a0-gf-a0.pnvm from somewhere else.
So if others will need that ucode, their wifi will fail too.
Thanks for all the work you do for many things here with all of this.
Re: Testing KLV-vmHost, Designed for Hosting VM's
Posted: Tue Nov 19, 2024 1:04 am
by JusGellin
@rockedge
Here's an update for making a virtual machine of BookwormPup_10.0.8.
It works beautifully on my new laptop.
Where install of BW10.0.8 directly on the laptop would only give one resolution for the display.
But as a virtual machine installed on this host, it work just like it should.
Here's the details for what it looked like as a virtual machine:
Code: Select all
# inxi -Fxxxz
System: Host: puppypc8351 Kernel: 6.1.106 x86_64 (64 bit) Desktop: JWM 2.4.3 dm: N/A
Distro: BookwormPup64 10.0.8
Machine: Device: qemu-or-kvm System: QEMU product: Standard PC (Q35 + ICH9 2009) v: pc-q35-9.1
Mobo: N/A model: N/A BIOS: SeaBIOS v: rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org date: 04/01/2014
Chassis: type: 1 v: pc-q35-9.1
CPU(s): 2 Single core Intel Core 7 150Us (-HT-SMP-) cache: 32768 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10444
clock speeds: max: 2611 MHz 1: 2611 MHz 2: 2611 MHz
Graphics: Card: Red Hat Virtio 1.0 GPU bus-ID: 00:01.0 chip-ID: 1af4:1050
Display Server: X.org 1.21.1.7 drivers: modesetting (unloaded: fbdev,vesa)
tty size: 131x30 Advanced Data: N/A for root
Audio: Card Intel 82801I (ICH9 Family) HD Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:293e
Sound: Advanced Linux Sound Architecture v: k6.1.106
Network: Card: Red Hat Virtio 1.0 network device driver: virtio-pci v: 1 bus-ID: 01:00.0 chip-ID: 1af4:1041
IF: eth0 state: up speed: -1 duplex: unknown mac: <filter>
Drives: HDD Total Size: 134.7GB (35.5% used)
ID-1: /dev/sda model: QEMU_HARDDISK size: 10.7GB serial: QM00003
ID-2: USB /dev/sdb model: USB_3.2.1_FD size: 124.0GB serial: 071C272F2F137A97-0:0
Partition: ID-1: / size: 2.2G used: 724M (34%) fs: overlay dev: N/A
ID-2: swap-1 size: 2.01GB used: 0.00GB (0%) fs: swap dev: /dev/zram0
Sensors: None detected - is lm-sensors installed and configured?
Info: Processes: 141 Uptime: 22 min Memory: 366.0/1958.1MB
Init: SysVinit v: N/A runlevel: 5 Gcc sys: 12.2.0
Client: Shell (bash 5.2.151 running in lxterminal) inxi: 2.3.8
Code: Select all
# xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
Virtual-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 325mm x 203mm
1280x800 74.99 +
5120x2160 50.00
4096x2160 50.00
3840x2160 60.00 50.00 59.94
1920x1440 60.00
2560x1080 50.00
1856x1392 60.00
1792x1344 60.00
2048x1152 60.00
1920x1200 59.88
1920x1080 60.00* 50.00
1600x1200 60.00
1680x1050 59.95
1400x1050 59.98
1280x1024 60.02
1440x900 59.89
1280x960 60.00
1360x768 60.02
1280x768 59.87
1024x768 60.00
800x600 60.32
640x480 60.00 59.94