I have installed debian 9.3 on HP DL20 Gen9. When Debian 9.3 start, what happen is that the screen of the system appear like on the picture after the grub goes. any help?
Try booting your computer up in safe mode from Grub. Install updates and restart.
If it happens again you probably need to configure your graphics card for your installation.
Re-install Debian 9, when in the Software selection menu,
don't enable Debian Desktop Environment. If you need a desktop environment, simply enable certain Desktop environments.
In this case, I'm using Cinnamon. Until now there are no problems.
Thanks.
I find a solution. I used "nomodeset on the boot", and the screen appear normaly. I have used another tty2 and i get connected with the shell.
nano /etc/default/grub
i find this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
and i have changed it to this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset"
Related
I'm on windows 10 and I'm encountering Docker on Windows crashing on startup.
I just installed docker on windows and have a couple of containers spinning up (last night). I've been able to use it but after reboot, or shutdown, this was the behaviour ever since. Pretty unstable.
It looks like this and terminates after a while without any prompt of an error.
More info that I have Hyper-V installed on my machine and "Use the WSL 2 based engine" option enabled on docker.
On my end, I was able to solve this by:
Going to Apps & Features
Search for Ubuntu (or any linux distro you've installed)
Click on it and navigate to Advance options
Click on Reset button.
Also, try to trial and error which docker on windows version is stable with your system.
Hope that helps.
Windows 10 N Pro, version 2004
I had a few different OS VM's setup before I decided to try Docker out.
After installing it and realizing I better stick to VM's I went on my Virtualbox, tried starting my old VM's and couldn't get past the boot screen - the issue is it goes to a black screen.
I created a few new VM's all resulting in the same issue. I tried restarting the machine, Windows Restore, trying different BIOS settings, uninstalling docker, reinstalling Virtualbox, increasing VRAM to 128MB, uninstalling subsystem for Linux, disabling the Hypervisor and sandboxing. The only thing that let me interact with the VM was enabling EFI - although after choosing "boot" option I had the same black screen.
After trying all possible solutions on SO and Google I stumbled upon a comment (which unfortunately I can't find) which pinpointed that Docker installer explicitly overwrites VM/Hypoer registries or processes. I don't know if that's the issue however it is the case.
How can I get my VM's running again without reinstalling Windows?
It sounds like the problem is: 1) You were successfully running VMs with VirtualBox on Windows 10 Pro, 2) You installed Docker, 3) Docker broke VBox. Correct?
Look here:
https://superuser.com/questions/1290051/virtualbox-no-longer-works-after-uninstalling-docker-on-windows-10.
Control Panel -> Programs and Features
On the left side choose "Turn Windows features on or off
Uncheck Hyper-V
reboot
After reboot you have to reinstall/repair your installation of VirtualBox with the original installer!
Reboot again and it should work 🙂
In general, please try posting these kinds of questions on https://serverfault.com or https://superuser.com. StackOverflow is for "programming" questions.
Centos 8 ships with Wayland as its compositor and I was forced to install centos8 due to some GLIBCXX compatability issue. Everything SEEMS to work ok but there is a curious absence of all xapps and I cant get a remote X11 session going. It seems I am in Wayland hell.
Centos 8 ships with the shiny new Wayland with rumored X11 compatibility, but all I find is articles on rumors of xwayland and a host of badly named products whose names all begin with 'W' for cute.
I cant seem to install any x11, xapps or anything that would force xwayland to install as a dependency. Its amazing how easily a decision is taken to burn thousands of hours on tens of thousands of users globally.
My best google-fu has yielded nothing.
Please help. How can I get x11 (xwayland) up and running so that I can run apps from my Windows desktop as I used to with Centos 7...?
I've already encountered this "problem" and the solution I usually apply is to disable WayLand.
To do this, just edit this file with any editor (I use VI)
/etc/gdm/custom.conf
and change the line
#WaylandEnable=false
into
WaylandEnable=false
Save and close the file and restart gdm service with
systemctl restart gdm.service
I ran into an error after installing VMware Fusion on my mac, that it couldn't find /dev/vmmon. After some digging, I've learned that there are only so many available character devices, and that other software I have has consumed them.
Since I actively use Viscosity and Virtualbox (for the time being), the only other one that I could find I had was Intel HAXM driver.
Instructions online suggest to run a script to uninstall it, however that script did not exist on my laptop.
I unloaded the driver with the command:
sudo kextunload -b com.intel.kext.intelhaxm
I wanted to determine if there is anything else I need to do, will this driver attempt to reload during boot?
Thanks!
The Intel HAXM docs show that as of 2018, there is an uninstall script:
sudo /Library/Extensions/intelhaxm.kext/Contents/Resources/uninstall.sh
I had the same issue, Tim Potter's solution fixed my issue ,
sudo kextunload -b com.intel.kext.intelhaxm
Thanks
Cannot find /dev/vmmon (VMware Fusion 8.5.1 on macOS 10.12.1)
I had the same problem.
After a lot of trial and error, and helpful support from VMware I got it to work by
Create another user on the mac
log in as that new user
start fusion
create a new virtual machine (custom, windows7, no actual OS installation)
If machine starts, then vmmon is restored correctly
switch back to your normal user, start fusion and your existing vm
I have not investigated WHY this works, and VMware-support couldn´t tell me either. For now - I do not care. It works, and I can run my vms again.
I installed RHEL 6.4 server under Parallels 7 on my Mac OS 10.8 just now from an iso file I just downloaded from RedHat. The installation seemed to proceed ok, but at the end I'm left with a screen with a gray bar followed by the text "RedHat Enterprise Linux Server 6.4" with no obvious way how to login.
If I shut down the machine I see it running the shutdown scripts. If I boot it I see the boot scripts and they all look ok. But I always end up at that same screen with no way to login.
I can enter characters in the screen, but there is no Linux prompt at all.
Anybody know what to do next? I couldn't glean anything fro the RedHat install manual.
Thanks,
doug
I had the same problem. The issue is the X-win server will not start because Parallels tools breaks the framebuffer with the RHEL 6.4 update. This is especially easy to see because a fresh install works fine until you install Parallels tools.
When you see the "select system to boot" message, hit the key that allows you to edit the boot arguments. Add a "3" to the end to force the startup to runlevel 3 (which is a console login without the GUI).
After logging in, type the command "starts" and you will see that it fails. Once you are able to fix this problem, the normal bootup into the GUI login will also work.
I had to downgrade the video driver subsystem back to 6.3 for it to start working, and you also have to add an exclusion to yum to prevent it from updating and removing the fix. This will be necessary until Parallels releases an updated tools that addresses this issue. There is a procedure I found in the CentOS forums for how to do this, sorry I don't have the link.