Proxmox 7.1.2 installation fail on Huawei RH2288H V3

A

aactis

New Member
Jan 19, 2022
2
0
1
Turin, Italy
Hi,
i am new to the forum and also a beginner on Proxmox VE.
At the moment i am trying to install it on a Huawei RH2288H V3 server with 2 Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz, 256 GB RAM and a 1TB Raid1 HDD but the installer ISO fail after the DHCP request at the moment of display the Splash screen.
I have found the Xorg.0.log and seem it can't start the framebuffer.

Any suggestion for solve the problem ?

Sorry for my poor english, but i don't use it often and it become a bit rusty :)

Thanks in advance and good day to all.

PS i have already tried a new media, and with this media i installed proxmox on a old portable without problem.
I also tried the memory on server and seems ok with Memtest86 v4.3.7.
I tried to boot with a Debian 11 media and the graphical installation interface work without problem with it.

Here are the content of my Xorg.0.log file:
------
[ 65.284]
X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
[ 65.284] Build Operating System: linux Debian
[ 65.284] Current Operating System: Linux proxmox 5.13.19-2-pve #1 SMP PVE 5.13.19-4 (Mon, 29 Nov 2021 12:10:09 +0100) x86_64
[ 65.284] Kernel command line: BOOT_IMAGE=/boot/linux26 ro ramdisk_size=16777216 rw quiet splash=verbose proxdebug
[ 65.284] Build Date: 13 April 2021 04:07:31PM
[ 65.284] xorg-server 2:1.20.11-1 (https://www.debian.org/support)
[ 65.284] Current version of pixman: 0.40.0
[ 65.284] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 65.284] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 65.284] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jan 20 15:27:05 2022
[ 65.287] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 65.377] (==) No Layout section. Using the first Screen section.
[ 65.377] (==) No screen section available. Using defaults.
[ 65.377] (**) |-->Screen "Default Screen Section" (0)
[ 65.377] (**) | |-->Monitor "<default monitor>"
[ 65.377] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 65.377] (==) Automatically adding devices
[ 65.377] (==) Automatically enabling devices
[ 65.377] (==) Automatically adding GPU devices
[ 65.426] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 65.426] (WW) The directory "/usr/share/fonts/X11/misc" does not exist.
[ 65.426] Entry deleted from font path.
[ 65.426] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 65.426] Entry deleted from font path.
[ 65.426] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[ 65.426] Entry deleted from font path.
[ 65.426] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[ 65.426] Entry deleted from font path.
[ 65.426] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[ 65.426] Entry deleted from font path.
[ 65.426] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[ 65.426] Entry deleted from font path.
[ 65.426] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[ 65.426] Entry deleted from font path.
[ 65.426] (==) FontPath set to:
built-ins
[ 65.426] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 65.426] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 65.426] (II) Loader magic: 0x55d9f5dd2e40
[ 65.426] (II) Module ABI versions:
[ 65.426] X.Org ANSI C Emulation: 0.4
[ 65.426] X.Org Video Driver: 24.1
[ 65.426] X.Org XInput driver : 24.1
[ 65.426] X.Org Server Extension : 10.0
[ 65.427] (--) using VT number 4

[ 65.427] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 65.446] (--) PCI:*(7@0:0:0) 19e5:1711:0000:0000 rev 1, Mem @ 0x90000000/33554432, 0x92000000/2097152, BIOS @ 0x????????/131072
[ 65.446] (II) LoadModule: "glx"
[ 65.446] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 65.823] (II) Module glx: vendor="X.Org Foundation"
[ 65.823] compiled for 1.20.11, module version = 1.0.0
[ 65.823] ABI class: X.Org Server Extension, version 10.0
[ 65.823] (==) Matched modesetting as autoconfigured driver 0
[ 65.823] (==) Matched fbdev as autoconfigured driver 1
[ 65.823] (==) Matched vesa as autoconfigured driver 2
[ 65.823] (==) Assigned the driver to the xf86ConfigLayout
[ 65.823] (II) LoadModule: "modesetting"
[ 65.823] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 65.896] (II) Module modesetting: vendor="X.Org Foundation"
[ 65.896] compiled for 1.20.11, module version = 1.20.11
[ 65.896] Module class: X.Org Video Driver
[ 65.896] ABI class: X.Org Video Driver, version 24.1
[ 65.896] (II) LoadModule: "fbdev"
[ 65.896] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 66.016] (II) Module fbdev: vendor="X.Org Foundation"
[ 66.016] compiled for 1.20.0, module version = 0.5.0
[ 66.016] Module class: X.Org Video Driver
[ 66.016] ABI class: X.Org Video Driver, version 24.0
[ 66.016] (II) LoadModule: "vesa"
[ 66.016] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 66.098] (II) Module vesa: vendor="X.Org Foundation"
[ 66.098] compiled for 1.20.9, module version = 2.5.0
[ 66.098] Module class: X.Org Video Driver
[ 66.098] ABI class: X.Org Video Driver, version 24.1
[ 66.098] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 66.098] (II) FBDEV: driver for framebuffer: fbdev
[ 66.098] (II) VESA: driver for VESA chipsets: vesa
[ 66.249] (EE) open /dev/dri/card0: No such file or directory
[ 66.249] (WW) Falling back to old probe method for modesetting
[ 66.249] (EE) open /dev/dri/card0: No such file or directory
[ 66.249] (II) Loading sub module "fbdevhw"
[ 66.249] (II) LoadModule: "fbdevhw"
[ 66.249] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 66.266] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 66.266] compiled for 1.20.11, module version = 0.0.2
[ 66.266] ABI class: X.Org Video Driver, version 24.1
[ 66.266] (EE) Unable to find a valid framebuffer device
[ 66.266] (WW) Falling back to old probe method for fbdev
[ 66.266] (II) Loading sub module "fbdevhw"
[ 66.266] (II) LoadModule: "fbdevhw"
[ 66.266] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 66.266] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 66.266] compiled for 1.20.11, module version = 0.0.2
[ 66.266] ABI class: X.Org Video Driver, version 24.1
[ 66.266] (II) FBDEV(2): using default device
[ 66.266] (EE) Screen 0 deleted because of no matching config section.
[ 66.266] (II) UnloadModule: "modesetting"
[ 66.266] (EE) Screen 0 deleted because of no matching config section.
[ 66.266] (II) UnloadModule: "fbdev"
[ 66.266] (II) UnloadSubModule: "fbdevhw"
[ 66.266] (EE)
Fatal server error:
[ 66.266] (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
[ 66.266] (EE)
[ 66.266] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 66.266] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 66.266] (EE)
[ 66.566] (EE) Server terminated with error (1). Closing log file.
 
Last edited:
NO-CARRIER indicates either no cable connected or an issue with the cable or module.
Have you checked that the cable is connected on the right port?

Is it an Intel NIC with a 3rd party SFP module?
 
mira said:
NO-CARRIER indicates either no cable connected or an issue with the cable or module.
Have you checked that the cable is connected on the right port?

Is it an Intel NIC with a 3rd party SFP module?
Click to expand...
Thank you very much, I did choose the wrong NIC at the beginning, but now there are more strange errors,
Now the network can be connected, but after the IP addresses of the two nics are set, they point to the same MAC address in the Intranet. That is to say, the GUI displays different IP addresses set by the two nics, but the traffic actually goes to the same NIC. If one NIC is disconnected, the two IP addresses cannot be accessed
 
Please provide the output of ip -details a
 
mira said:
Please provide the output of ip -details a
Click to expand...
I just installed Centos7.9 2009 on the server, the problem is the same, I think it may not be PVE or Debian problem, it is Linux problem, command output details as shown in the picture
1659350717826.png
 
Check if there's a firmware update available for the NIC.
Also check if there's a BIOS update available for your mainboard.
 
mira said:
Check if there's a firmware update available for the NIC.
Also check if there's a BIOS update available for your mainboard.
Click to expand...
https://forum.proxmox.com/threads/t...-addresses-on-the-intranet-correspond-to-one- nic.113034/#post-488125
================================================ ==============================
This link is a detailed description of the problem. After I changed the two nics to different IP segments, the problem was solved. For example: It was 192.168.1.117/24 and 192.168.1.118/24 before, but changed to 192.168.1.117 and 192.168.3.118. Thank you very much for your reply and help. However, my skills are not enough for me to update NIC firmware or BIOS firmware, I am a novice in IT ~~
 
Yes the Same for the entire MultiBlade E9000 for High Density. This is really a must for the next version, all big data-centers are now migrating from Dell and HP to Huawei and IBM because of the cost and shipping from China being the best.


CH121
CH 222
And al the blades compatible with the E9000 have been tested.
Non worked. Gonna test the workarround altought if it is a well known issue recomend inserting it into the documentation
 
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