Yum Update Caused Problems

I am having problems with my Sony Vaio windows
it boots up saying (on a black screen, grey text):
==============================================
Windows Boot Manager
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1. Insert your Windows installation disc and restart your computer.
2. Choose your language settings, and then click "Next."
3. Click "Repair your computer."
If you do not have this disc, contact your system administrator or computer manufacturer for assistance.
Status: 0xc0000225
Info: The boot selection failed because a required device is inaccessible.
Enter=Continue ESC=Exit
==========================================
No matter how many times i tried to restart and even tried F10 repeatedly or Alt-F10 I can't get to any other screen other than the above screen.

So I thought ah to hell with windows on this machine. I'll just install a linux distro because it's for my uncle all he really needs is internet and watch youtube videos/movies.

I have successfully burned and installed Fedora before on other machines using LiveCDs when they had CDs.

This time I tried to burn the DVD since it's it doesn't fit on the CD (I got my ISO from http://download.fedoraproject.org/pu...86_64-21-5.iso)
But when i inserted my DVD and restarted the same black screen appears.

So i have been looking for an older version of Fedora that fits on a CD (I am thinking maybe it'll boot from a CD, not sure though) but can't find any.

Any thoughts or solution to my problem?

Thanks in advance.

Hi Guys, I installed a dual boot config. on a 160 gb hdd. The first choice in grub menu is Linux Lite (latest distro) and the second boot choice is Mint 17.1 Rebecca. I'm encountering a situation that when I boot into LL the system boots OK. Then when I try a restart and boot into Mint it seems to be doing OK until the end of the boot process at which time the screen flashes the Mint logo and then goes dark-then flashes then goes dark every second or so-endlessly. After a while I'm sometimes able to get Mint to finish booting by hitting the esc key. Any ideas how to make this screen flashing situation stop and do a normal boot?

Update: Solved the problem by changing the resolution settings to coincide with those of LL....flashing stopped!

LL and Mint IMHO are two of the best distros for a Newbie to "get their feet wet." - I know, I am that Newbie.

I have setup a dual boot system with Fedora 21 and Arch Linux. The problem is that Fedora doesn't see my encrypted Arch installation. The installations are on separate partitions and do not share anything apart from hard disk space. I have run the following commands as root in Fedora:

Code:

grub2-install /dev/sda

Code:

os-prober

Code:

grub2-mkconfig -o /boot/grub2/grub.cfg

When I rebooted, Fedora was the only OS entry showing in the GRUB menu.

There was a suggestion from one of the members of the Arch forums that I should write the entry myself into /etc/grub.d/40_custom and then re-build the grub configuration or take the Arch entry from Arch's /boot/grub/grub.cfg and just paste it into the 40_custom in Fedora and rebuild.

How do I boot from a live Arch USB stick into the installed Arch and do as stated above? How would it work? Thanks in advance for your replies.

Hi everyone.
Earlier I posted a reply on a thread about a problem with partitions while installing Elementary OS Freya as dual-boot, and yancek answered giving me a link with a tutorial (thank you!).

However, after I continue with the installation it stopped with an error saying that grub wasn't installed, something like that. But when I start my computer (with USB boot priority), pops a window with the option to 'Try Elementary..." and "Install Elementary..." and if I press Esc a grub console appears. Doesn't that mean grub is installed? What should I do to fix this?

Best regards,
a Linux amateur

After creating a bootable usb using Universal USB Installer. I booted up the sytstem (Dell Inspiron N4110) F12 boot on usb, did the install, everything went well until after copying files and then the error message that "The grub-pc package failed to install into /target.. So i continued without a boot loader and now am trying to figure out how to get it back.
Previously i did a perfect dual boot of Kali Linux wherein the Grub boot loader was present. I did however uninstall Kali, reclaim HDD space, and even use EasyBCD to remove Grub(i believe).
Also worth noting is that before this dual boot with pignuy and after uninstalling kali linux i did a complete reinstallation of my windows 7 system using the recovery HD.

Now i would like to know how i could get grub boot loader back onto my system so that i can boot up Pinguy OS. Thanks

Please Help,

I have a Windows 7 and Fedora 20 dual boot pc .
Today i deleted the fedora partition from windows disk management and then restarted my pc.
Now i am stuck in the 'grub rescue > ' screen ...... It is showing 'no such partition ' , after searching through the internet i tried these commands......

grub rescue > set boot=(hd0,msdos6)

grub rescue> set prefix=(hd0,msdos6)/*boot/grub

grub rescue> insmod normal (after this line ,i am getting the error , grub rescue > unknown filesystem)

grub rescue> normal

Don't know what to do ,but i want to get back to the windows os first ,also i don't have the windows or fedora live cd . My Windows recovery is stored in my pc hard drive....... plzz help so that i can resolve this issue

I have made a change to GRUB2 bootloader in etc/default/grub.
Now I need to run 'update grub' for the change to take effect.
However, the 'update grub' command on the terminal is giving this error message:
Code:

root@debian:/# update grub
bash: update: command not found

Can someone please explain why this command is no longer working?

I've had to make a change to grub because I tried to install a new distro which meant I had to alter grub.
The install wasn't successful so I deleted the grub file and then re-installed it.
The re-installed grub needs a change so I can get sound on my pc.
However, I can't add these changes because the 'update grub' command doesn't work.

I've checked the grub file with another debian distro and they are both the same.
So now I don't know if I need to check if a different grub file is the problem or anything else.
Can someone help?

Hi Folks,
Installed Mint-mate 17.
It gives message:You are now disconnected" after logging in.
I restart, the network connection comes.
It is not "networking restart", but system restart.

Tried five more times. The behaviour is every time the same.
After booting the system, no network connection. But from there I restart the system, then network connection is on.

Very irritating to always boot it second time to get the network connection up.

The computer is a desktop Dell Optiplex 9010.
On the same computer, Windows 7 runs without any problem.

Any idea how to fix it?

Thanks

Hi Folks,
I am a relative newbie to linux.
I am running Fedora 21 from an external USB Hard Drive and get the following message after Grub has loaded. Any help in resolving this is very much appreciated.

: [sdb] No Caching mode page found
[ 4.407772]sd 4:0:0:0 [sdb] assuming drive cache: write through
Welcome to emergency mode! After logging in, type "journalctl -xb" to view
Systems logs, "systemsctl rebboot" to reboot, "systemctl default" or ^D to Try again to boot into default mode.
Give root password for maintenance (or press Control-D to continue):
[ 26.078356] ldv: disabled by bios
[ 36.249164]system-fsck[628]: /dev/sdb3: clean, 403/128016 files, 174669/512000

Thanks

If I'm loading down the system, i.e., running transmission while playing a video, periodically network throughput drops, video stops, cpu activity jumps up, then after a few seconds to a minute suddenly cpu activity goes back to normal, networking and video resumes. In addition I have this "important" message in the log viewer:

Quote:
systemd-udevd
Error calling EVIOCSKEYCODE on device node '/dev/input/event2' (scan code 0xc0183, key code 226): Invalid argument
There are several lines with varying scan and key codes, the rest being the same.

In addition, a couple weeks ago, I had locked myself out of the system, (boot to black screen), due to a failed attempt at installing the latest AMD/ATI proprietary drivers. Thanks to the help of several people on the forum, I was able to get back in, using the native drivers.


Obviously as a newbie to Linux I don't know if any of these things are related.

I would appreciate any help anyone could give me, TIA!!