[SOLVED] HP Z440 Workstation

M

mst80

Member
Apr 28, 2020
14
2
8
44
Hi

I got hp Z440 and i cant make it running. During installation (Proxmox VE 6.1) process i get this error messages:

(not sure if it is correctly visible but it says at the beginning:
ACPI error: Needed [Buffer/String/Package], found [Integer])
IMG_1676.png

Any help very very appreciated.

Thanks.
 

Attachments

  • IMG_1676.png
    IMG_1676.png
    113.1 KB · Views: 33
Hi,

you could try to edit the installers GRUB boot entry and add module_blacklist=nvidiafb to the linux line, then continue with booting (CTRL+X).

This reads like an issue with the HP firmware,
https://h30434.www3.hp.com/t5/Noteb...with-linux/td-p/6021489/highlight/true/page/2

There should be a Bugfix in the 5.4 Kernel (which we will ship with the next release):
https://bugzilla.kernel.org/show_bug.cgi?id=201981

Some poster had luck with adding pci=nommconf to the kernel commandline on boot.
 
I cant boot it, the initial message I posted is while installing.

t.lamprecht said:
you could try to edit the installers GRUB boot entry and add module_blacklist=nvidiafb to the linux line, then continue with booting (CTRL+X).
Click to expand...
how can i do this?
 
Boot the ISO until you get the initial graphical screen where you can select "Install Proxmox VE", memtest, ...
Keep the first entry selected and hit the e key, you will see a screen like:
Screenshot_2020-04-28 nina - Proxmox Virtual Environment.png
Go to the end of the line starting with linux (arrow keys), there you can enter the parameters. Once done you can hit CTRL+x to continue booting with those params.
 
Also, the Proxmox Mailgateway 6.2 released today, while another project it shares most of the installer and ships already the new 5.4 Kernel, you could try to test it; just to see if the errors are gone with using the newer kernel (like the bugzilla entry suggest).
 
t.lamprecht said:
Also, the Proxmox Mailgateway 6.2 released today, while another project it shares most of the installer and ships already the new 5.4 Kernel, you could try to test it; just to see if the errors are gone with using the newer kernel (like the bugzilla entry suggest).
Click to expand...

Ok so i managed to amend GRUB installers boot entry.

Unfortunately trying with mailgate did not succeed.

I've tried with:
  • module_blacklist=nvidiafb
  • pci=nommconf
  • acpi=nommconf (not sure was it typo in above so i tried this as well)
  • pnpacpi=off
above gave same error on ACPI: `ACPI error: Needed [Buffer/String/Package], found [Integer]`
  • acpi=strict
this one gave a bit different outcome to `Needed...` just gave `ACPI Error: Aborting method...`
  • acpi=off
this resulted with different outcome, see screenshot attached.

IMG_1712.png

With all above failed, any ideas what can i do now?
 

That wont help if the pve-kernel makes problem on that HW, as the first reboot into the new kernel will make problems..

But, actually from your test of PMG it seems that the pve-kernel-5.4 makes some things quite better, the ACPI errors are all gone there, aren't they? It seems that the remaining issues stem from the NVIDIA card which fails to get up and thus the graphical installer cannot start.

So, I'd really go for https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster (if even possible, it uses the 4.19 Kernel so not sure how your HPs firmware likes that) and then before the reboot install the upcoming 5.4 Kernel:
apt install pve-kernel-5.4
 
t.lamprecht said:
apt install pve-kernel-5.4
Click to expand...
How to do it?


OK, so i tried installing debian 10. I started with graphicall installation and did not add any command modifiers for GRUB ( no fiddling with acpi)
Installation went well. I managed to get up to end.
With first reboot I can see GRUB menu and after 2sec system start booting but i get black screen and that is it. Monitor is switching off "saying" no input signal.
When I restart i can see again GRUB menu but that is it. Either normal or recovery mode takes me back to black screen and after short time monitor is switching off reporting "No signal".

Turning off monitor and on doesn't make any difference - black screen and after seconds it is reporting "No Signal".
Altering boot options and adding acpi=off result with displaying some info but stuck on below step. No Ctrl+Alt+F1-F12 make any difference

IMG_1766.jpg

Any idea?
 
At this point I'd guess that the graphic card inside the workstation (should be a NVIDIA NVS 310, 315 or 510, from the Datasheets) has some real issues with Linux, neither booting our Kernel nor Debian's stock kernel is really not the best sign.

I mean, in the screenshot it says that it wants to start the GNOME Display Manager, so you kept the graphical environment enabled for installation. You could try to reinstall without any graphical environment. Tick off "Debian desktop environment" and the print server, then tick on the SSH server. The selection screen should look like:

Screenshot_2020-05-02 QEMU (test-iso-6 0) - noVNC.png

This way it should not boot to a graphical installation, as this clearly doesn't works with your NVIDIA hardware and the kernel drivers. If you want then a graphical environment afterwards we can still go for that with the proprietary drivers, but I'd first try to get the installation working.

Does this workstation also have remote access (iLO/IPMI/...), as that could be worth a try...
 
I managed to install Debian 10 in console mode ( no graphic installer) as you suggested. I can't see anything, i am getting black screen and "no signal" message. So no idea what messages it spit out during boot. BUT, i can ssh into it.

Also i managed to install OpenMediaVault which does not require any GUI. It gave me black screen as well but i could log into it using Web GUI.
I managed to install pve 5.4 kernel and it works, I mean it boots and i can log into it using Web GUI or ssh.

So, PROXMOX fails because part of installation require GUI - i guess.

So having Debian installed, can i install somehow proxmox without need for graphic card to be used in more than console mode?
I believe that graphic card is not required when proxmox is set up and running - right?
 
I plugged in different monitor and actually i can see output:
 

Attachments

  • IMG_1848.jpg
    IMG_1848.jpg
    846.5 KB · Views: 23
Ok, i followed installation process from this link https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster
including step:
apt install proxmox-ve postfix open-iscsi

on console i get some errors (short version) ((long version below)):
Code: 
Job for pvestatd.service failed because the control process exited with error code.
See "systemctl status pvestatd.service" and "journalctl -xe" for details.
dpkg: error processing package pve-manager (--configure):
installed pve-manager package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
  Package pve-manager is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Processing triggers for mime-support (3.62) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-5.3.18-3-pve
Running hook script 'zz-pve-efiboot'..
Re-executing '/etc/kernel/postinst.d/zz-pve-efiboot' in new private mount namespace..
No /etc/kernel/pve-efiboot-uuids found, skipping ESP sync.
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for rsyslog (8.1901.0-1) ...
Processing triggers for systemd (241-7~deb10u3) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.38.1+dfsg-1) ...
Processing triggers for pve-ha-manager (3.0-9) ...
Errors were encountered while processing:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

on console i get some errors (long version):

Code: 
Loaded services file OK.
Server role: ROLE_STANDALONE

Done
Setting up libavfilter7:amd64 (7:4.1.4-1~deb10u1) ...
Setting up glusterfs-common (5.5-3) ...
Adding group `gluster' (GID 116) ...
Done.
Setting up gstreamer1.0-libav:amd64 (1.15.0.1+git20180723+db823502-2) ...
Setting up glusterfs-client (5.5-3) ...
Setting up liblvm2cmd2.03:amd64 (2.03.02-pve4) ...
Setting up ceph-common (12.2.11+dfsg1-2.1+b1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/ceph.target → /lib/systemd/system/ceph.target.
Created symlink /etc/systemd/system/multi-user.target.wants/rbdmap.service → /lib/systemd/system/rbdmap.service.
Setting up dmeventd (2:1.02.155-pve4) ...
Created symlink /etc/systemd/system/sockets.target.wants/dm-event.socket → /lib/systemd/system/dm-event.socket.
dm-event.service is a disabled or a static unit, not starting it.
Setting up python-cephfs (12.2.11+dfsg1-2.1+b1) ...
Setting up liblwp-protocol-https-perl (6.07-2) ...
Setting up libwww-perl (6.36-2) ...
Setting up pve-qemu-kvm (4.1.1-4) ...
Setting up lvm2 (2.03.02-pve4) ...
update-initramfs: deferring update (trigger activated)
Created symlink /etc/systemd/system/sysinit.target.wants/blk-availability.service → /lib/systemd/system/blk-availability.service.
Created symlink /etc/systemd/system/sysinit.target.wants/lvm2-monitor.service → /lib/systemd/system/lvm2-monitor.service.
Created symlink /etc/systemd/system/sysinit.target.wants/lvm2-lvmpolld.socket → /lib/systemd/system/lvm2-lvmpolld.socket.
Setting up libpve-apiclient-perl (3.0-3) ...
Setting up spiceterm (3.1-1) ...
Setting up libxml-parser-perl (2.44-4) ...
Setting up libxml-twig-perl (1:3.50-1.1) ...
Setting up libnet-dbus-perl (1.1.0-5+b1) ...
Setting up libpve-common-perl (6.0-17) ...
Setting up pve-cluster (6.1-4) ...
Created symlink /etc/systemd/system/multi-user.target.wants/pve-cluster.service → /lib/systemd/system/pve-cluster.service.
Job for pve-cluster.service failed because the control process exited with error code.
See "systemctl status pve-cluster.service" and "journalctl -xe" for details.
Setting up libxml-sax-expat-perl (0.51-1) ...
update-perl-sax-parsers: Registering Perl SAX parser XML::SAX::Expat with priority 50...
update-perl-sax-parsers: Updating overall Perl SAX parser modules info file...
Replacing config file /etc/perl/XML/SAX/ParserDetails.ini with new version
Setting up libpve-cluster-perl (6.1-4) ...
Setting up libpve-http-server-perl (3.0-5) ...
Setting up pve-ha-manager (3.0-9) ...
Created symlink /etc/systemd/system/multi-user.target.wants/pve-ha-crm.service → /lib/systemd/system/pve-ha-crm.service.
Created symlink /etc/systemd/system/multi-user.target.wants/pve-ha-lrm.service → /lib/systemd/system/pve-ha-lrm.service.
Job for pve-ha-lrm.service failed because the control process exited with error code.
See "systemctl status pve-ha-lrm.service" and "journalctl -xe" for details.
Job for pve-ha-crm.service failed because the control process exited with error code.
See "systemctl status pve-ha-crm.service" and "journalctl -xe" for details.
Setting up pve-xtermjs (4.3.0-1) ...
Setting up libpve-access-control (6.0-6) ...
Setting up libpve-cluster-api-perl (6.1-4) ...
Setting up librados2-perl (1.1-2) ...
Setting up libpve-storage-perl (6.1-5) ...
Setting up pve-firewall (4.0-10) ...
Created symlink /etc/systemd/system/multi-user.target.wants/pve-firewall.service → /lib/systemd/system/pve-firewall.service.
pvefw-logger.service is a disabled or a static unit, not starting it.
Job for pve-firewall.service failed because the control process exited with error code.
See "systemctl status pve-firewall.service" and "journalctl -xe" for details.
Setting up libpve-guest-common-perl (3.0-5) ...
Setting up pve-container (3.0-23) ...
system-pve\x2dcontainer.slice is a disabled or a static unit, not starting it.
Setting up qemu-server (6.1-7) ...
Created symlink /etc/systemd/system/multi-user.target.wants/qmeventd.service → /lib/systemd/system/qmeventd.service.
Setting up pve-manager (6.1-8) ...
ipcc_send_rec[1] failed: Connection refused
ipcc_send_rec[2] failed: Connection refused
ipcc_send_rec[3] failed: Connection refused
Unable to load access control list: Connection refused
Created symlink /etc/systemd/system/multi-user.target.wants/pvedaemon.service → /lib/systemd/system/pvedaemon.service.
Created symlink /etc/systemd/system/multi-user.target.wants/pveproxy.service → /lib/systemd/system/pveproxy.service.
Created symlink /etc/systemd/system/multi-user.target.wants/spiceproxy.service → /lib/systemd/system/spiceproxy.service.
Created symlink /etc/systemd/system/multi-user.target.wants/pvestatd.service → /lib/systemd/system/pvestatd.service.
Created symlink /etc/systemd/system/getty.target.wants/pvebanner.service → /lib/systemd/system/pvebanner.service.
Created symlink /etc/systemd/system/timers.target.wants/pvesr.timer → /lib/systemd/system/pvesr.timer.
Created symlink /etc/systemd/system/timers.target.wants/pve-daily-update.timer → /lib/systemd/system/pve-daily-update.timer.
Created symlink /etc/systemd/system/sysinit.target.wants/pvenetcommit.service → /lib/systemd/system/pvenetcommit.service.
Created symlink /etc/systemd/system/pve-manager.service → /lib/systemd/system/pve-guests.service.
Created symlink /etc/systemd/system/multi-user.target.wants/pve-guests.service → /lib/systemd/system/pve-guests.service.
Job for pvestatd.service failed because the control process exited with error code.
See "systemctl status pvestatd.service" and "journalctl -xe" for details.
dpkg: error processing package pve-manager (--configure):
installed pve-manager package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
  Package pve-manager is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Processing triggers for mime-support (3.62) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-5.3.18-3-pve
Running hook script 'zz-pve-efiboot'..
Re-executing '/etc/kernel/postinst.d/zz-pve-efiboot' in new private mount namespace..
No /etc/kernel/pve-efiboot-uuids found, skipping ESP sync.
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for rsyslog (8.1901.0-1) ...
Processing triggers for systemd (241-7~deb10u3) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.38.1+dfsg-1) ...
Processing triggers for pve-ha-manager (3.0-9) ...
Errors were encountered while processing:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)
 
Last edited:
pve-cluster.service seems the one having the problems, the other are probably just followup issues, what's in
journalctl -u pve-cluster.service
To see why it fails.
 
t.lamprecht said:
pve-cluster.service seems the one having the problems, the other are probably just followup issues, what's in
journalctl -u pve-cluster.service
To see why it fails.
Click to expand...
output:

Code: 
-- Logs begin at Mon 2020-05-04 12:14:12 BST, end at Mon 2020-05-04 12:17:36 BST. --
May 04 12:14:28 debian systemd[1]: Starting The Proxmox VE cluster filesystem...
May 04 12:14:30 debian systemd[1]: Started The Proxmox VE cluster filesystem.
 
  • Like
Reactions: Orfer Orduz
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom