- Apr 17, 2015
The problem very well may be in a new kernel. I for example have problem specifically with newer kernel. That is why I suggested OP tries older setup.
Yes, is surely worth a try, never said anything against thatThe problem very well may be in a new kernel. I for example have problem specifically with newer kernel. That is why I suggested OP tries older setup.
Interesting - the daily latest netinst boots with no issues. I progressed to the first graphical install screen no problem but stopped there as that's not really what I want to install.Hmm, after a bit of research, there seems more people to have problems on this PC/board with Debian (and Proxmox VE's root is Debian).
Out of interest, could you try a newer Debian Testing (Buster) netinst image? A daily generated one could be found at: https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/
It has a newer kernel and bootloader version than Debian stable (Stretch), possibly including more workarounds for certain hardware, so maybe worth a shot.
I wonder if there's a way to replace grub on the proxmox install CD/USB for this later version? or to port the version from the latest debian netinst which I just confirmed also works fine. I'm hoping we have a helpful grub expert watching!!!Hello,
I'm getting the same issue trying to install Proxmox (or Debian) on a beelink x55 and vbook A1.
On the other end, Ubuntu server and Centos are installing themselves without issue.
To install proxmox, I had to use 2 usb dongle at the same time
a) one with a usb bootable dongle created from scratch
b) one with a rufus/etcher/dd copy of the proxmox install iso
The PC will boot on the a) and mount b) during init step. The install will work but at the first reboot, it will hang like when trying to boot from the usb install dongle b).
I probably need now to boot from an ubuntu live cd and do a grub-install on /dev/sda
To create a), I followed https://github.com/ndeineko/grub2-bios-uefi-usb and copied the boot folder from the proxmox install iso onto the usb dongle.
It's far from being solved yet.
EDIT: I also tried to install Debian 8.11 and 9.5 without success. (same behavior with a black screen and white cursor, before the grub menu)
already done. I tried rufus/UltraISO/dd/unetbootin/etcher/win32image/... . The partition table and flags are the same.Try imageUSB to make bootable USB and change your CSM parameters in BIOS to legacy
I can second that. I've also tried many writers, several USB sticks, and a CD-ROM drive. They all boot fine on another pc, and other installers boot fine on the x55. The new testing version of Debian has the problem fixed.already done. I tried rufus/UltraISO/dd/unetbootin/etcher/win32image/... . The partition table and flags are the same.
The issue is not with the usb dongle. It's with the bootloader used by Debian that's doesn't support as many platforms as the one used by Ubuntu 18.04 or Centos 7.
While installing Proxmox VE on Debian is totally valid and supported, you're right here, installing PVE on the daily testing images won't work for now.Suggestions of what to do next appreciated. I guess I could install this daily debian, and then install proxmox - would that work? I would prefer not to be running a daily debian though!
Ugh!!! I've definitely not done that before!While installing Proxmox VE on Debian is totally valid and supported, you're right here, installing PVE on the daily testing images won't work for now.
Those are based on what will become the next Debian and Proxmox VE 6.X release sometimes in the middle of 2019, and currently we have no repo online (which makes sense, as it's still before the next Debian release freeze and we may still get some incompatibilities).
What you could do is installing the testing image, with only small disk space and Debootrap a Debian 9 "Jessie" from there, and just use the Debian daily testing as "glorified" bootloader...
PVE can then be installed if you boot the PVE Jessie the first time.
That's quite hacky and not really ideal, I know, looking at how much work you put already in it seems that you're do not fear such things
Did not found a possible cause after a quick look at the differneces between our and unstables GRUB, yet...
You could just install Debian 9 stretch on a disk on another PC, like you tried before, but manually install the newer grub .deb package with dpkg -i before switching back to the problematic PC?If anyone knows an easy way to backport it, please let me know!!
Yes - that's sort of what I'm thinking, or the same on the proxmox install. In the briefest few seconds I had to look at the grub packages I got the impression the main package is a dummy that creates a set of dependencies of several other packages. I could be completely wrong but it looked like I would need to do more than dpkg -i grub2 - perhaps a few more packages.You could just install Debian 9 stretch on a disk on another PC, like you tried before, but manually install the newer grub .deb package with dpkg -i before switching back to the problematic PC?
If it then boots we know it was just the different GRUB and you can install PVE on top of that.
I've already done that - unplug, remove battery connector, BIOS resets. Seems to work ok, but you're right, there's no cmos reset jumper, or automatic reset after x failed boots - not that I can tell.Looking forward to your step-by-step recipe.
FYI: Be careful with BIOS settings... It is possible to brick the X55 purely through the settings... (Maybe the result of setting the OS in BIOS to "linux') AND big and BOLD "THERE IS NO NVRAM / BIOS REST SWITCH" which most systems and motherboards have!