Intel i9 9900K
32GB RAM
Radeon 380 & Nvidia 610
Installed into Hyper-V VM on windows 10 21H1
Passed through USB SSD is the only drive available to the VM
Installed from freshly downloaded netinstall Tumbleweed .iso with matching SHA256 and passed media check
openSUSE-Tumbleweed-NET-x86_64-Snapshot20211111-Media.iso
Guided setup partitions, ticked the box for LVM and separate /home (XFS), all other options left at default
Due to my <1mb internet, the install said is was going to take 4 hours, so I came back to it 6 hours later to find 3 orange dots with some sort of breathing effect animation, but they’d disappear and reappear roughly every 5 seconds. I didn’t stare too long at it, so that’s only vague memory. Task manager in windows showed a repeating pattern of heavy disk reads and light writes, repeating in time with the orange dots disappearing. I concluded that it must have crashed or be stuck on something, so I force reset the VM.
On reboot, just got a blinking cursor. Ctrl + Alt + Fkeys does bring up tty# and I can log in to a command line, so I shutdown and went to google (actually duckduckgo but whatever)
Googled around, found a lot of forum threads telling people to add nomodeset to grub boot options while starting up, so I tried that, but it didn’t help.
I noticed quiet in the boot options next to where I was putting nomodeset, so I figured I’d take that out and see what happened. Now after about a minute of blinking cursor it says " 52.489549] C0] hv_balloon: Max. dynamic memory size: 8192 MB" and the blinking cursor is on the second line. Now if I Ctrl + Alt + Fkey it very briefly shows a login prompt, but immediately (split-second) goes back to hv_balloon and the blinking cursor.
Adding nomodeset and removing quiet does the same thing as just removing quiet.
Hi and welcome to the Forum
Might have better luck with WSL2?
What about as well as nomodeset add plymouth.enable=0 (maybe even drop to text mode installer with textmode=1) but if you have such slow internet, it may be far better to find somewhere to download the full iso image very likely it can’t get the drivers for the graphics to run…
WSL2 still requires me to use windows, which I’m trying to get away from. Was hoping to set up Linux in a VM on a passed through drive so I could eventually switch to booting from it. The prevalence of Linux boot CDs led me to believe it would handle the hardware change, but since everything I’ve read online points to this being a graphics driver issue, and I have both AMD and Nvidia graphics cards, I’m starting to doubt that.
Tried adding plymouth.enable=0 as well, same result. You seem to be talking about the installer with textmode=1 but I tried that anyway, same result.
openSUSE is installed, it’s just not starting the GUI, sitting on blinking underscore instead.
Hi
Then yes, that’s a graphics card issue. Not sure how hyper-v handles passthough, no issues see the other way and qemu. Now, I have a dedicated card and screen for gpu passthrough (and SSD via dedicated sata card).
The only thing I’m passing through is the USB SSD, and that appears to be handled by the virtual SCSI controller, so passthrough possibly isn’t even the right term to use.
I believe Hyper-V can handle proper hardware passthrough, but I only skim read the tutorial, enough to know it’s quite an involved process, I think significantly moreso than under Linux and QEMU.
Is there anything I can do to make this work as-is? I can log into a command line, so I can install/uninstall packages if need be, or access log files. Most of the more advanced help I’ve found while searching around has been for Ubuntu or Arch, nothing for openSUSE, so I have no idea where to start.
Hyper-V doesn’t have graphics options, it’s just a virtual GPU, super standard VM. It’s more or less the same as a VirtualBox VM with everything left at default, the only thing I customized is to make it use a physical drive instead of a virtual disk, but the physical drive is still connected to a virtual controller in the VM, so it should all be super standard.
It’s a desktop with 2 discrete cards, neither of which are being passed through.
Tried setting it to 2GB, no change. Disabled dynamic memory entirely so it just uses 8GB from the start, no change. I’m going to leave dynamic memory turned off.
Downloading openSUSE-Tumbleweed-GNOME-Live-x86_64-Snapshot20211111-Media.iso now. Estimated time is going between 2 hours and 3 hours.
Once it’s downloaded and booted, is there anything specific I should do?
While looking at memory settings on the VM, I noticed it was only assigned 1 core, so I upped that to 4 and tried to boot with nomodeset, it now says “[FAILED] Failed to start X Display Manager.” above the blinking cursor. Went back to 1 core, blinking cursor by itself. Up to 2 cores with nomodeset, Failed. Still 2 cores but with default boot options, blinking cursor by itself.
Hi
Just add the Tumbleweed Live iso and boot as a live desktop and see what happens. What about 4 cores and don’t add nomodeset? If you also add the boot option 3 after quiet, does it boot to a console login (runlevel 3, multi-user target) on the existing install?
4 cores without nomodeset, blinking cursor by itself. Ctrl + Alt + Fkeys very briefly shows a terminal login, then immediately (split second) goes back to the blinking cursor. Exactly the same as 2 cores.
Boot option 3 brings me directly to tty1 with a login prompt.
Hi
OK, and you can login ok? If so it may just be missing desktop patterns, if you switch to root user and run yast (the ncurses version) and check under the desktop patterns and see if it’s installed…
Yes, logged in. I’ve never used YaST in text mode, and not much experience with YaST besides, so I’m having to learn as I go. It’s alright though, I know how to google
I set the filter to patterns, and looked at the ones that seemed relevant.
“GNOME Desktop Environment (Basic)” 16 of 17 packages installed
“GNOME Desktop Environment (Wayland)” 32 of 40 packages installed
“GNOME Desktop Environment (X11)” 61 of 61 packages installed
“X Window System” 24 of 26 packages installed
The packages that aren’t installed don’t look important to me, it’s things like predictive text and personal organizers. Are all the patterns marked as installed meant to have all the packages installed, or is this ok?
Also, the live CD finished downloading. Ran it first with 4 cores, then 1 core, got the same results in both cases.
Normal boot, I get green dots for a minute, then orange dots which flicker about every second. Memory demand in Hyper-V is 1146MB.
In failsafe mode, I get green dots for a minute, then drops back to tty1. Above the normal tty prompt is the text that was displayed during startup, with the last lines being “Starting Show Plymouth Boot Screen…” and “Starting Wait for udev To Complete Device Initialization…”
Tried adding nomodeset to normal boot (only tried it with 1 core), got the same result as failsafe mode.
I can’t get at the log file itself because windows 10 doesn’t like XFS or LVM, so best I got is screenshots. Those 3 cover the whole log file.
video=800x600@60 briefly brings up an error about invalid screen, ending with “:Skipped”. Goes by too quickly to read more than that, but I feel I got the important bits.
If I don’t use 3 or nomodeset, I can’t get to a tty, it just goes back to the blinking cursor after less than a second.
