Im trying to get to the debian install through ubuntu through windows 7. I used wubi to install ubuntu and partition the hard drive for a debian install later. But now that Ive installed ubuntu theres no selection to boot Windows 7 in the grub menu that wubi set up. I never touched the windows partition during install but used C:/ for the install components. how can i add windows to the grub selection?
View 6 Replies
Ubuntu 10.04 I am dual-booting along with Windows. I need to change the order of boot options so that Windows is the automatic selection rather than Ubuntu. I cannot find the file to make the change and not sure what changes I should make when I do find it .
View 2 Replies View RelatedI have been trying for a couple days now to install 10.04 on a 250G hard drive that was a USB boot with 9.1. I want the hard drive in the case. The bios has been changed and does see the new drive. Boot selection has been changed to CD Rom. Everything starts out fine until step 4 of the install, Prepare partitions. There is no hard drive available on this step. The HDD is not seen by the disk utility either.
View 6 Replies View RelatedI have the issue of getting the Kubuntu getting booted first if I do not select manually in 7 sec. how to make that auto selection to XP so that, I can leave the computer and let it select Windows.
View 4 Replies View RelatedI just attempted to install ubuntu for the 4th and 5th time and have yet again had a fail. This time it actually completed the installation, which is a first. however upon reboot it takes me directly to Vista - I don't see grub or a o/s selection choice.
View 9 Replies View RelatedI'd like to install Fedora 14 64bit as a dual boot on an existing win 7 32bit system. When I boot with the Live CD, after selecting "boot" in the Fedora boot selection menu, I get a grey screen with a white cursor, and the system freezes. I checked the Live CD on my laptop and it worked perfectly.
My System:
MotherboardASUS P5Q DELUXE
CPUIntel Core 2 Duo E6750, 2,66 GHz, Sockel 775
[code]...
I have installed Debian a few times now (and other distro's), so I'm fairly used to installing linux. I'm not used to installing it on Apple hardware (back in 2009 on my laptop I had some issues that were solved rather quickly, but that's about it). Now I'm installing Debian Squeeze on a new (well, bought today, but it is the previous model: iMac 11,2) desktop iMac.
Installing goes well (resizing partition, rEFIt, booting Debian 6.0.1a netinstall CD, installing packages etc.) I followed a tutorial [URL] to install grub explicitly with force after installing and running gptsync. Everything went according to the tutorial and I rebooted to be welcomed by rEFIt and then grub: perfect!
BUT when I chose Debian in the grub-selection list, I only see a few lines of starting the kernel, and then my screen goes all black. A few seconds later I hear a sound, and iirc it's the sound of gdm prompting to select a user. I cannot switch to a TTY and I have to use the power-button to shut the system down.
I've finished the installation of Debian Squeeze using Installer loader from Windows. But the Installer menu is still appear on Windows Boot Manager.
I've try to uninstall the "Installer Loader" from Windows and I got an error message about BCDEDIT (if I'm not wrong), during uninstallation process.
I ignore it, and continue the uninstallation process until complete. But, After I reboot my computer, the Installer menu is still appear on Windows Boot Manager.
I'm using Windows Vista Business SP2.
got a lenovo B50-30 (no touchscreen) that came preeinstalled with windows 8. after installing debian im unable to boot windows , im not too great with grub configuration.this is what i suspect is the menu entry for windows in the grub boot menu .
Code: Select all### BEGIN /etc/grub.d/30_otheros ###
# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda3
menuentry "Windows Vista (loader)" {
set root=(hostdisk//dev/sda,gpt3)
search --no-floppy --fs-uuid --set=root 8CA2-D25B
chainloader +1
}
here is info about the partition table (ive alocated / and swap part for debian nothing else. )
Code: Select allDisk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
[code]....
i would like to know how to configure windows to boot from the grub2 menu.
I installed Debian 5 hours ago, and I am fighting with it since then. I'll pass on the tons of issues I am encountering (wrong desktop environment (I asked for debian's, I got Gnome), shitload of various errors when doing basic things, resolution of a minitel).
The biggest issue I am having is that Grub is not listing Windows and I can't boot into it. I've tried os-prober and update-grub, the boot info script detects Windows 7 (it's windows 10 but, whatever), I've tried to boot into a windows repair USB stick and fix the mbr and boot through the cmd (which both returned success). I am currently trying to create boot-repair USB stick, but I keep getting errors about file systems not handling symbolic links...
How can I repair Windows boot (which seems to have been messed up by Debian's setup)..
Also, I am quite used to linux and unix systems, as I am dev and use Mac OS at work and used Ubuntu/Fedora for years, and I never had such a bad and messy experience with any of those OS...
Here is the boot-info generated with Boot-Repair-Disk [URL] .....
How can I change the behavior of the selection buffer or a program that uses it ( I have xclip) to not send me text until the mouse button is released while clicking and dragging? This causes havok in the software I'm developing that tries to make use of the selection buffer. I need the full selection, not bits more bits more bits and then the full selection.EDIT: I cannot listen for mouse events such as button release outside of the GUI of my program.
View 2 Replies View RelatedI am having dual boot system(windows 7 and Fedora 12).When i switch on my system.It show the the timer 3 sec in order to get boot selection window(means window which asks that what to start fedora 12 or windows 7).I want to increase this time from 3 to 10 sec.
[URL]
I'll start off with stating my problem and summarize how I got to it.
I installed Windows 10 on an SSD. I installed Debian 8.2 after it. The SSD was/is a GPT disk. I installed both installations from a UEFI booted device (DVD for Windows, and USB drive with Live CD for Debian).
I tested it after each installation making sure I could boot via UEFI into Windows, then Debian, then Windows, to make sure nothing broke.
I rebooted the machine. Suddenly, no more UEFI. Nothing. I didn't change any BIOS/UEFI setup menu settings. Not even my USB drive with Live CD will boot through UEFI anymore. Even when nothing else is plugged into the system.
My situation is actually a bit more complicated than that, but I think that will suffice for now. I can still boot into the Live CD on the USB drive, just in Legacy mode only. I mounted the EFI partition on /mnt/boot after I mounted the file system for Debian on /mnt. It is identical, as far as I can tell, to as it was before when it was working.
My motherboard has CSM and Secure Boot, both have been set up how they need to be to boot UEFI into Debian. Tinkering with them further after things broke did not fix it. I tried all variations of options/settings.
The GRUB Reinstall guide says to be in EFI mode before starting it, so I can't do that.
My motherboard is an ASUS X99 Deluxe, and I've heard ASUS has special "features" (read: bugs) that come with their boards. Searching hasn't brought up any other people with this issue. I believe the firmware is updated to it's most current one.
I've tried dd-ing my backup of my old system, from before trying to migrate to a Dual Boot system, to the SSD (after backing up the dual boot setup with dd -> <name>.img via the Live CD USB). However, that won't boot either as it is a UEFI install as well.
The layout of my EFI partition is as such:
/boot/EFI/Boot/bootx64.efi
/boot/EFI/Microsoft/<Microsoft-naming>.efi
/boot/EFI/debian/grubx64.efi
I've heard that the standards on how that's supposed to be set up isn't a standard. However, since it worked booting into the OS' the first time, I don't see how that could be the issue (a bad hierarchy layout leading to the UEFI not being able to see the OS installs).
I've seen that I can boot to an EFI shell (called Shell.efi, apparently) via an option in my UEFI BIOS setup menu on my motherboard. Is that an option here to somehow bypass this strange issue?
All I can think to try is burn it all and start over. But not knowing what caused it means I could just make it happen again. Plus, I can't boot into UEFI install media, so I can't install UEFI boot OS'. :/
I installed lenny and now my windows 7 won't boot. When I select it in Grub the machine just restarts the bios after a few seconds of black screen. The machine I'm using is a very vanilla intel p4.
I'll paste my /boot/grub/menu.lst below. All of the drive options look correct. I properly shutdown Windows 7 before installing lenny. I'm sure I can reinstall the mbr and get my windows back, but I would like to dual boot with grub.
I've recently bought a new computer and installed Windows 7 on it, but left 100GB of space on a separate partition so I could put Debian next to it in dual boot. I have the new Intel i7 950 processor and I run Windows 7 Proffesional 64 bit, so I assumed I had to pick the ia64 debian image. However the CD I burned from the ia64 image didn't boot. (a black screen started and an underscore kept flashing, but nothing else happened)[URL]
I've managed to install i386 Debian on a older intel pentium 4 computer before and that worked fine. I believe I used another application to burn the CD then. This time I've burned the CD with the default Windows CD burn application. I can try burn more CD's but I don't have much left so I want to make sure this is the problem before attempting again. (the burned files on the ia64 CD look exactly the same as the files on the i386 CD, when browsing through the cd files in windows) "If your PC has a 64-bit AMD or Intel processor, you will most likely need the "amd64" images (though "i386" is also fine), the "ia64" images will not work."This seems a bit strange, they recommend me to use the amd64 image if you have a "64-bit AMD or intel processor". I dunno if this is a typo, but it seems weird to me that the AMD-64 Debian version would also work on my Intel machine
I recently installed Debian 7 on a dual boot with Windows Vista. Thus, when I boot the computer, I am prompted by a GRUB screen to select Windows Vista loader, Debian, and Debian (recovery mode). I would like to upgrade Windows Vista to Windows 7. Will this cause an issue with GRUB? Will a Windows 7 loader be added to the list or will a Windows 7 loader replace the Windows Vista loader? Will there have to be a setting change within Debian? Within Windows?
View 6 Replies View RelatedI have a Dell laptop (inspiron 1150) which was dual booting Windows XP and Ubuntu 9.04. I have successfully installed Debian Jessie Standard over the Ubuntu. I pre-partitioned using gparted-live to make a separate single partition for the Debian install. Guided partitioning was then carried out by the installer producing separate /, /home, and swap partitions. After installation, the grub menu shows an entry for Debian and Windows XP. I can boot Debian, but not Windows XP. The symptoms are the same as reported in other forums: A terminal is displayed, vanishes and the system reboots defaulting to the Debian boot.
The grub.cfg file for the Jessie system has an other-os entry:
Code: Select allmenuentry "Microsoft Windows XP Home Edition (on /dev/sda2)" {
set root=(hostdisk//dev/sda, msdos2)
search --no-floppy --fs-uuid --set=root cc0ce0ab0ce091ae
drivemap -s (hd0) ${root}
chainloader +1
}
The original Windows entry for the Ubuntu install was:
Code: Select allmenuentry "Microsoft Windows XP Home Edition (on /dev/sda2)" {
insmod ntfs
set root=(hd0,2)
search --no-floppy --fs-uuid --set cc0ce0ab0ce091ae
drivemap -s (hd0) ${root}
chainloader +1
}
The partitions produced by partman look OK (during the pre-partitioning I did not touch sda1, sda2, or sda3):
Code: Select all~ # fdisk -l
Disk /dev/sda: 37.3 GiB, 40007761920 bytes, 78140160 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
[Code] .....
Partition table entries are not in disk order.
The os-prober found XP:
Code: Select all~ # os-prober
/dev/sda2:Microsoft Windows XP Home Edition:Windows:chain
So it seems that everything is in place, but there are perhaps important differences in the grub.cfg files. Are the two "set root" commands equivalent for example?
I have Windows 10 and Deb 8 dual boot, and I need to re-install Windows but want to avoid (or at least plan for) losing Grub/Linux boot.
Last time I re-installed Windows after Linux I ended up having to re-install Linux again afterwards as well, because I couldn't recover it (seemingly due to complications from encryption). So this time I'm wanting to plan and avoid that.
CURRENT DISK PARTITIONS:
Code: Select allsda1 | 550M | EFI System
sda2 | 128M | Microsoft reserved
sda3 | 175.8G | Microsoft basic data
sda4 | 286M | Linux filesystem (Boot)
sda5 | 28.2G | Linux filesystem (Root)
sda6 | 91.3G | Linux filesystem (Home)
sda7 | 1.9G | Linux swap
[Code] ....
As there is a "Microsoft Reserved" partition and a separate Microsoft directory within the EFI partition, if I just go ahead and reinstall Windows will it install it's boot loader/image to one of it's own partitions? And NOT affect anything else like Grub and other Linux things?
Logic tells me yes, but there seems to be many issues on the internet about installing Windows after Linux.
My primary concern is whatever happens with Windows or anything to do with dual loading etc, is that Linux will still just boot, or I can get it working again without much hassle.
Why is there a reserved Microsoft partition AND a Microsoft directory in the EFI partition? Which one boots Windows?
Why is there a separate Linux Boot partition AND a Linux directory in the EFI partition? Which one boots Linux? Where is Grub invoked from, is one redundant, etc?
How these work. It is possible I've set them up wrong, or with redundant partitions, but both systems have been booting ok for months.
I've been using Debian for a few years but always on dedicated boxes and/or VMs.
Finally decided to dual boot Debian and Windows on my main Desktop PC.
Installed as I normally would using, however this time using a seperate drive (one for the existing Windows 10 install and the other for Debian), Debian install detects that windows has an EFI partition and sticks an entry in there, which is fair enough, and everything working fine. Then I spent some time configuring all my software and set it all up just the way I like it. I've rebooted Debian a few times to check it's working correctly and it is.
The issue arrives when I reboot and load into Windows 10. It boots fine.
However after a further reboot GRUB no longer loads... and the machine just boots directly into Windows 10.
After doing some further digging into my EFI partition (and reinstalling various times) it would appear that after a reboot Windows 10 deletes the entry GRUB creates in my EFI partition after EVERY reboot.
Done some googling and most people advise turning off 'fast boot' in Windows as it locks certain partitions to facilitate the machine going into hibernation, only to find that it's always been turned off on my machine (I recall due to a driver issue with my graphics card this had to be turned off when I installed Windows 10).
I've found this article on the Ubuntu forums : [URL] .... however I've tried their steps and windows is still doing a hostile takeover of my EFI partion after a reboot!
Any way to stop Windows 10 from interfering with my EFI files after a reboot? (without doing the obvious thing and kill Windows off).
I have used dual boot systems using various versions of windows and Debian for many years and have encountered no problems. However, I have a problem with installing Debian on a EeePC (ASUS PC1201) which uses Winows 7. I can not even get started because I can not understand the information that I have on my hard drive partitions. Windows 7 says that I have the following :
Local Disk(C:) 78.1 GB free of 99.9GB
Local Disk(D:) 49.8 GB free of 83.8.GB
NewVolume(G:) 948 KB of 0.99 GB
Local Disk(F:) 37.9 GB free of 38..0 GB
(Originally the ASUS only had two partitions C: and D: I used Gparted to genetate F: and G:)
gparted-live-0.7.1.5 says that I have the following :-
/dev/sda1 ntfs 992.5 KB
/devf/sda2 ntfs 100.00 GB with 66.09GB unused
/dev/sda3 ntfs 132.88GB with 129.88 GB unused
unallocated 1.00 GB
Debian Squeeze (the net install version) will not install. G was the result of trying to provide some swap space. How do I prepare the hard drive so that Squeeze it will install on F: ?
how to install Debian after Windows is already installed. Could someone give me a brief guide to begin the process of installing Windows? When I installed Debian I already made a partition for windows (in the same hard disk), I hope I did it right.
View 3 Replies View Relatedis it safe to install a dual boot windows 32bit and a linux 64bit on the same pc?
View 14 Replies View RelatedEverything was going great earlier today when suddenly, my PC on a fresh boot, gave me a message that said something like "Ubuntu is running on low graphics mode ..". It was running a low res, i think it was 640x480, and gave me some repair options like a. Boot in low res mode for just one session b. Trouble shoot this error etc..There were 3 more options but i don't remember what they were.
i chose "boot in low res just for this one session", but it gave me the same error the next boot. Then i tried troubleshooting, which didn't work (restoring to a backup config was no use). Then finally i rebooted and started Ubuntu in Recovery mode, and i did something like "Fix broken packages" because , from the list of options it seemed like the only one which would help at that time.
But now, whenever i choose the Ubuntu option after starting my PC, it just restarts my computer. My other OS is Windows 7 which boots just fine. Hope someone can help me with this . In the meanwhile i'll try making a new MBR or something.
i'm new to ubuntu and i've got a nubby question: is there any shortcut for word selection like Ctrl+Shift+(right/left)Arrow in Windows?
View 2 Replies View Relatedi install ubuntu though wubi and it worked kind of. It asked me to restart at the end so i did and when it was startaing up it didnt show the option to boot into ubuntu.
View 9 Replies View RelatedI have several RHEL 5.0 servers in a secure network. We have identified around 200 rpms from 5.4 that we would like to upgrade. These servers have no connection to the internet, and very limited connection to the corporate network.
The application guys will not approve a full 5.4 upgrade as the app is reliant on certain rpms from 5.0.
So how can I create a boot disk that will install just the selected 200 rpm's. I have been trying to modify (remove rpms) from the downloaded 5.4 dvd, but with no luck. I have also had a look at anaconda, but seem to be going round in circles.
I have a Ubuntu - windows 7 dual boot (in two partitions of the same HDD) desktop PC for a few months. I was learning terminal commands and, although I don't think I made such a big mistake, but the fact is that the a very strange thing happenned: "Preferences" and "Administration" from System disappeared as it did also "Applications". After rebooting the same it remained the same. No big deal, I thought, because I haven't yet saved any important work on Ubuntu. So I reinstalled Ubuntu. Done that everything was nice until I booted Windows... Since then I counldn't start windows after GRUB due to:
Status: 0xc000000f
Info: The boot selection failed because a required device is inaccessible."
Windows Live DVD Repair is useless. I've tried CHKDSK utilities, no result. Windows partition in Ubuntu's Disk Utility is OK but I can't access the files (all "broken links"), just can explore a few directories after which I find myself entering the same folder endlessly. I wanted to repair windows boot or at least recover some important files in Documents and I thought I had backup (but turns out that, for some reason that I'm still trying to understand, they aren't...).
I locked the screen, came back, typed the password, screen remained black, though cursor was visible and moving. Nothing I could do to rejuvenate the screen. Had to switch to tty6, sudo shutdown -r now. Then, on reboot obtained kernel selection, it proceeded to displaying kernel messages, but froze on sdb, after 3 secs. I figured it was the usb, so turned off, removed usb cables to external hard drives, but again it froze saying something about firewire mouse, the mouse is also usb. I tried several times, but no matter what kernel I chose, I couldn't get it to boot. So I loaded puppy live cd, but now it can't access some parts of the disk. I was running utorrent and the folder with partially downloaded files can be accessed but there's nothing there (there was), and some folders can't be accessed at all.
View 2 Replies View RelatedI installed 11.04 after Windows 7. when the GRUB boot menu starts up there is an option for Win 7 boot but it will not boot windows. When that option is selected the screen changes colour for 2 seconds and then reverts to the GRUB menu. Ubuntu boots fine.I downloaded the Boot Info Script and ran it, the results are
Code:
Boot Info Script 0.55 dated February 15th, 2010
============================= Boot Info Summary: ==============================[code].....
I had a dual boot machine with fedora 12 and windows vista and I could use grub boot-loader to switch between two. Few days ago windows got corrupt and I have to reinstall it. I put windows 7 now and as usual it erased grub. So to reinstall I put the fedora 12 installation CD on and followed some usual setup steps. When I got the command line I issued the command "grub-install /dev/sda" (sda not hda because It showed bunch of sda, sda1..) but surprisingly it said grub command not found. I remember doing it before while it worked fine.
View 4 Replies View Related
