I have a dell inspiron 5559 and i used to have a dual boot windows 10 and ubuntu 16.0.4.
After an update of windows 10 i got many problems like my graphic card driver didnt get auto-update and my cpu fan got some problem
After changing my fan windows would enter an automatic repair and before even starting it... it would jump into blue screen and enter a restart loop while my linux would work just fine
I tried installing or repairing windows but before the page for chosing language blue screen apears again and system jumps out of installation
I started a system diagnose and ram memmory test but there wasnt any error.
So i thought maybe its grub menu or linux's problem and i used rm rf root in ubuntu (that was a foolish mistake im really sad about this now) after that still i cant install or repair windows. and when i turn on my pc an error apears
//
Error: file '/boot/grub/i386-pc/normal.mod' not found.
Entering rescue mod...
Grub rescue>
//
I tried different windows dvd's for installation all had same problem. And i tried installing or trying ubuntu or kali live using an usb but various errors show up like bootmgr is missing or....
Can anyone help?
Sorry if my text had some english problems :)))
May be formatting the entire hard drive then install Windows or Ubuntu would work for you.
Related
Newest PhpStorm terminal is not functional on Windows 10. Using legacy console setting for CMD does not help to solve the issue. Cannot type anything inside terminal.
Meaning this old 2015 year fix: WebStorm/PhpStorm, issue with terminal on Windows 10
does not solve the issue.
This issue happens on a specific Dell laptop only. Meaning it's not common on other computers I've tried to install it. Maybe could be related to some BIOS setting?
Happened because of the Lithuanian letters of the user folder in the system which came from Microsoft account of the computer.
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
Hoping this is the right place to ask this. I'm trying to learn React Native and I'm using Expo as my medium for deployment, but I'm finding that I'm literally getting 20 minutes at a time before my browser fails to connect with the error code ERR_CONNECTION_FAILED. I've tried the following:
netsh winsock reset, then the related ipconfig commands for flushing DNS settings
Clearing browser caches
Updating drivers
I'm at my wits end as the only thing that completely solves it is restarting my laptop, which for obvious reasons isn't feasible every 20 minutes, so I'm hoping somebody can help.
I'm experiencing the same issue with Expo in this environment:
Windows 10, version 1909 (OS build 18363.476)
using WSL (Windows Subsystem for Linux) with Ubuntu 18.04 LTS
These links were useful to learn why this is happening:
https://github.com/expo/expo-cli/issues/99
https://github.com/microsoft/WSL/issues/2913
https://github.com/microsoft/WSL/issues/3951
In essence, this issue seems to be due to a problem with WSL. Per a post in the first link, I tried the alternative to restarting the computer and it worked - it made the ERR_CONNECTION_FAILED problems disappear...for 20 minutes. That alternative is as follows:
WIN+R -> services.msc
Find LxssManager
Right-click -> Restart
This restarts the WSL service which also means that the WSL instance that was running gets terminated. This is less than ideal, but at least a computer restart is avoided. The third link says this WSL problem is fixed in Windows Insider Build 18890.
I am now considering spinning up a VM to run Ubuntu instead of trying to use WSL for Expo projects.
I uninstalled the latest Windows updates, and the problem has not surfaced since.
I have VMware and windows 10 installed on a virtual machine on my Macbook Pro. I have an ISO file of windows 10 mounted and sometimes when I restart windows and expect it to restart I'm prompted with the "install windows screen" instead.
It scares the shit out of me. Why is this happening? There seem to be some kind of delay as it seems to auto-magically open windows when I try again.
This morning I thought I had to restart windows all over again and go through 3 days of headache (setting up / installing programs etc), but then I went on a meeting and then it worked. Any thoughts?
Changing the BIOS boot order to ignore the CD-ROM should fix the issue.
However, is there any reason you have the ISO mounted still?
I think it was the iso file on the host, it is mounted. And delete your snapshots.