Search results

Could you elaborate on how to do this in the config file? thanks, Matt

I don't remember exactly, but would have been to change the named interface in the network configuration file. /etc/network/interfaces I probably ran ifconfig to find the correct interface name, and just substituted in the network interface file. The problem comes about I think sure to the dummy...

Hi - the first line is the name of the file, the second the contents of the file. You'll need to use an text editor like vi or nano to put the contents into the file - the same for other instructions further down. I use vi, only because I have for years. If you're not familiar nano might be a...

Hi goenjamin - I added that file, it won't exist. Debian will parse all files in that folder for release names, so you're effectively telling it that buster exists in the repos, and then setting the default release back to stretch / stable so that it doesn't use those repos by default. Then...

I can confirm it works on the SSD. I had to make some changes to the network config after moving from my pc back to the beelink but otherwise it worked fine...

Random smiley annoying! Should read colon and D so APT followed by :: and then Default

OK, here goes, the great reveal!!! I have tested this on a USB flash disk, but I think it will work on the SSD. You'll need a way to attach the X55 SSD to a PC that will boot the proxmox install, do the install (from a normal USB install media), then boot into proxmox on a working PC. The...

I 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.

at the risk of causing wild excitement, I managed to get proxmox to boot. Whilst I did install the testing version of grub2 this alone did not fix it. I just wanted to mention in case others are trying this. I then changed quite a few other things, so I'm now going to try and work out exactly...

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...

Ugh!!! I've definitely not done that before! I was trying to work out if there's a way to backport grub from testing onto the installed proxmox booted on another machine. I haven't had chance to try yet. There have been a number of minor version updates to grub going on the package name /...

great idea! tried it - rEFInd boots of course, can see proxmox. will it boot it? No :( same black screen with static white underscore.

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. Possibly the proxmox Devs might be able to back port the installer...

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!!!

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. So whatever issue is on the current proxmox, it does look like it has been resolved in this later debian...

I tried 2 older versions, no luck...

I don't get that far unfortunately. Before any menu options at all, I just go straight to a black screen and static cursor. Whatever mechanism starts and presents the usual menu, it just doesn't get that far. I should have mentioned, I already tried an older install, same problem!

So I ran the install on another computer onto a USB stick. Insert that working installation into the Beelink Gemini X55 I'm trying to run it on and exactly the same - black screen with white underscore. So it looks like the installer and installed OS do the same thing at boot time. So I'm still...

Hmm, maybe, but I wouldn't be surprised if the same thing happens post install. I don't think I have a convenient way of doing it elsewhere either. Although I might be able to install to a usb flash drive elsewhere and move that and see if it boots... Something for me to think about!

can't find that post either. so unfortunately I'm a bit stuck. really frustrating...