I have XP and win 7. I want to triple boot with Debian.When I install, grub finds win 7 and XP and says everything should be fine, but then when I boot, only debian appears.This was fixed by doing update-grub2 after logging in.Now, I have win 7 bootloader as an option. However, when I boot into XP, and then reboot, grub disappers. he screen just says welcome to grub and then a blinking cursor.
View 10 RepliesI installed squeeze with 2 drives, one for squeeze (2.6.32-3-amd64 using 120GB hdd), and one for my old winxp. I used LVM with ext4 on /root, /home, and ext2 for /boot. The install gave me grub 1.98.
When booted, screen says
Loading Grub
Welcome to Grub
I decided to upgrade to Squeeze from Etch.
not upgrade, but moving from etch to squeeze.
Clean new install. Format disks, re-partition...etc.
All goes perfectly well, until I reboot into my newly installed Squeeze.
After the messages from the bios motherboard, there is a black screen with a flashing cursor, and nothing else happens. Now it should have been the GRUB coming up and asking which system to boot into. But there is nothing at all on my screen.
I thought I've done something wrong during install, so I formated the disks again, and re-installed squeeze again. Just paying close attention to every message, before I went further.
And AGAIN, when rebooting into the system, there is nothing on the screen.
Last nigth I upgrade my system to squeeze and it whent well except for grub-pc and udev. If i try to upgrade now udev will not install do to problems with the kernel version and grub-pc can't seem to find the boot image.
[Code].....
yesterday I updated my squeeze amd64 on my Phenom X4 and now it is not booting anymore. Have you experienced the same problem?
After that I noticed the shutdown was not working anymore, it just restarted instead of powering down. This morning it wouldn't boot squeeze anymore, when grub starts and prints "Welcome to grub" (or something like that) the list of operating systems is not shown.
I noticed the updated also included grub and I saw it correctly detected my operating systems.
I am planning to boot knoppix soon and try to reinstall grub from chroot, but currently I am at work.
I try to install to my desktop as Squeeze/ISPConfig3 server, but GRUB does not load after several re-installations.
I have
- 6 x 500GB HDs
- ASYS A8N-SLI Bios SLI-RAID active as only then RAIDSata1-RAIDSata4 can be seen 2 x RAID1 (has to have something) and all drives can be seen by Debian-installer as individuals Same has been working with LinuxMint (both LM10 and LM Debian Edition) (with and w/o fake-RAID)
1st test: Guided partitioning (LVM) for one disk (where /boot will be separated) => Installation OK and starting.
[Code]....
I'm configuring a machine with Debian 6. I booted from the DVD, took the defaults, and it eventually came up with a Gnome desktop. Everything worked as expected.
I then installed gcc, g++, the Debian kernel source, and built a new kernel with preemptive multitasking turned on. It built clean, I ran "make install" and it put the kernel files in /boot. I rebooted and got a kernel panic error, to the effect that it couldn't find the root filesystem.
/boot/grub/grub.cfg shows
"linux /boot/vmlinuz-2.6.32-5-686 root=UUID=1890437b-5884-4b83-97cf-62d39f63c872 ro single"
for the original install, but the entry for the new kernel has
"linux /boot/vmlinuz-2.6.30DW-preempt root=/dev/sda1 ro quiet"
/etc/fstab has
# / was on /dev/sda1 during installation
"UUID=1890437b-5884-4b83-97cf-62d39f63c872 / ext3 errors=remount-ro 0 1"
I've tried changing the grub entry to UUID, but the new kernel still panics. grub-mkconfig and update-grub just rebuild the split UUID=/sda1 grub.cfg. The new kernel still seems to be looking for /dev/sda1 even after changing grub.
I just installed squeeze and at finish it asked me if it write the MBR with gurb.
I say yes, but after restarintg, squeeze doesnot appear in grub.
I also have lenny in the same PC. code...
How can I run squeeze I just installed.
I recently purchased a new Lenovo Thinkpad T420i and am having problems installing the latest version of Squeeze from CD. After receiving the laptop, I started it up, configured Windows 7, and confirmed everything is working correctly. Next I went through the Debian installer, which completed successfully. I'll be dual-booting Windows 7 and Debian, so at the partitioning stage I resized my NTFS partition, added a shared VFAT partition, then used the "Guided" install to create my root and swap partitions. My partition layout is code...
I assumed something was wrong with grub, so I booted the CD into rescue mode and chose to reinstall grub onto the Master Boot Record. But nothing changed. Just to experiment, I went into fdisk, deleted all my new partitions (leaving just the Windows ones), and tried rebooting, but the same error happened. I then went through the Debian installer again, being careful to set everything up correctly, but still, the device won't boot.
I'm not even getting to the grub boot screen, so something is wrong even before the point. Reinstalling grub to the Master Boot Record (grub-install /dev/sda) isn't changing anything. How can I troubleshoot this?
I cannot count how many times I have re-installed squeeze, and do all kinds of fixes to grub, but no joy. Every time, there is this ntoskrnl.exe error, and to re-install it. I thought my WIN XP may be corrupted, so I reinstalled it, and updated it with sp3 and all updates. Then I re-installed squeeze (reformatting all partitions). At the end, the installer ask if I want to install grub to mbr. I replied yes. After reboot, only the 2.6.32.3-amd64 and the recovery kernels show up on the grub screen, no winxp.OK, I booted into squeeze kernel and looked at the /boot/grub/grub.cfg file, and there winxp is not included in /etc/grub.d/30_os-prober section. In terminal, I typed
#os-propber and it found winxp in /dev/sda1
then I typed
#update-grub
and now /etc/grub.d/30_os-prober now show winxp.I rebooted, and winxp shows on the grub screen, and I chose winxp.It came back with "ntoskrnl.exe ...error... re-install ntoskrnl..."Here are the details:
fdisk -l
root@SHUM-AMD64:/home/shum# fdisk -l
Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
[code]....
I've installed Lenny with no problem, but I tried switching to Squeeze, and grub for some reason didn't pick up on the Windows partition this time - it just shows the two Linux options (debian and debian single-user). I check the menu.lst file (which I've edited under Lenny with no issues), but for some reason it doesn't exist at all in this install. Is it in a different location with Squeeze maybe?
why grub didn't pick up on my Windows install?
I'm trying to do is protect the computer against housemates. The standard procedure I do with Lenny:
1. Password protect BIOS.
2. In BIOS, always boot from hard drive. Disable booting from any other device such as USB or CD-ROM.
3. Password protect Grub (v1) using the "password --md5 $1$9MuaA/$5TDLgvmcEiCWNr5W9VaMK1" syntax in my menu.lst file.
With the above precautions in place, [I think] the only way to gain root access to the system is to take the case lid off and proceed to do stuff physically (like set jumpers and/or take out the hard drive). Am I correct? My reasoning for this is, the computer boots -> must boot from HD -> must load Grub -> must go to default menu item since others are protected, and cannot command prompt in Grub without password.
Anyhow, In Squeeze, I was a bit disappointed to find out, after doing a bit of Google-research, that Grub v2 (which is standard on Squeeze now) does not easily support password protecting the Grub menu. Am I correct? Will this issue perhaps be addressed in the Squeeze final release? Is this feature dumb anyways because the Grub password is of no use (i.e. my paragraph above is complete horseradish)?
Another thing I would like to do is change the console font and size back to something more "normal" or "classic", not some crazy tiny font that's only found in totally bleeding edge Linux distrubutions <gasp!>. I found that the Squeeze console font (e.g. when I type Ctrl+Alt+F1) is wicked tiny. I wanna change it to "normal". Grub v2 password and console font config?
My Squeeze installation has the horrific 80x25 line display, and I cannot stand it. I know it can do better, because the grub screen is very tiny. I ran dpkg-reconfigure console-setup, but the offerings there aren't much better. I don't know what happened to the good ol' days of grub when all you had to do was pass vga=791 to the kernel to get a decent console size... but it seems they are gone.
I don't really understand this new v2 grub... I don't know why it was necessary to change how it was configured, when it seemed to work so exquisitely. how I would accomplish the functional equivalent of passing vga=791 (1024x768@75hz) to the kernel in grub
i had windows 7 on my system and now i installed debian squeeze but grub does not show my windows 7 in menu for selecting how could repair this problem?
View 4 Replies View RelatedI have installed vmlinuz and initrd.gz (squeeze) in /boot/newinstallation and added to Grub the lines:titleNova Instalaçãoroot(hd0,0)kernel/boot/newinstall/vmlinuzinitrd/newinstall/initrd.gzNevertheless, when I choose this option at the grub, it begins to start the kernel vmlinuz and thus restart the system. The installed Debian Lenny boots in a normal way.
View 10 Replies View RelatedI just formatted the partition that contains fedora 15 using windows.. Now when I attempt to boot my PC the grub bootloader comes up and I cannot boot anything.... The error that I get|| i feel i need a boot command to boot boot win7 from grub... grub propmts me " minimal bash-like line editing is supported. for the first word tab possible list a possible commands completion anywhere else tab list
View 1 Replies View RelatedI was installing sqeeze i386 on my laptop VOSTRO 1400 and got this the 'grub-pc' package failed to install into /target/. without the GRUB boot loader, the installed system will not boot.
View 3 Replies View RelatedI tried to install Open Office following a guide in OpenOffice.org but after several attempts debian refused to boot properly. I decided to re-install Debian 5.0. When we came to the installation of the boot loader GRUB refused to be installed. I stopped the installation expecting to go back to the beginning. But now it tries to boot saying:Grub loading stage 1.5.
Grub loading, please wait...
Error 15
This is an old Toshiba 3110 with Windows 98SE installed which I have successfully customized and do not want to loose. What can I do to get back into W98SE and then re-install Debian properly?
When updating from the last Debian Live image (Squeeze) to the current Debian testing, apt announces a lot of packages being not required:
The following packages were automatically installed and are no longer required:
openoffice.org-draw libpcsclite1 libwpd8c2a usb-modeswitch gtk2-engines-smooth dnsmasq-base tomboy
libmono-security2.0-cil libgsf-1-common update-notifier-common libndesk-dbus1.0-cil libmtp8 libmono-addins-gui0.2-cil
gnome-js-common pnm2ppa libavutil49 libhal-storage1 libmono-system2.0-cil update-notifier python-mako
openoffice.org-officebean openoffice.org-emailmerge network-manager-gnome openoffice.org-impress gdebi libgpod-common
[Code]...
These include some important packages, like network-manager-gnome for example. Was it really intended to be removed? Without it, it's impossible to manage network connections from Gnome (only manual option of editing interfaces config is left). Is it a bug, or some incomplete intention? apt suggests to autoremove these packages. Should they all be retained, or only some of them, or it's supposed to be none? Removing some of them makes sense for me (like Epiphany for example), but some not at all.
I want to remove pulse and install alsa instead but I can't seem to be able to do it. I tried to search for all packages with "pulse" in their names and purging them but it didn't work because aptitude wanted to remove all of the packages that used pulse with along with pulse.
View 2 Replies View RelatedI have Debian Jessie 8.0 amd-64 installed. It is a dual boot system with Widnows 8.1 alongside. Both the systems work fine with a few glitches coming at times on jessie. But I assume it should get stabilised with time.
Problem is:
The usb keyboard is no longer detected until the GRUB stage crosses.
* This implies I am unable to press F2 to enter into BIOS
* I am unable to chose Windows 8.1 by using arrow key on the keyboard.
When the default system (first in the grub list), in this case Debian is selected after time runs out then the keyboard comes back to life and works properly thereafter.
So far I have tried the possible solution given at [URL] .... but it did not work.
Some Information
================
$ lsb_release -a
No LSB modules are available.
Distributor ID:Debian
Description:Debian GNU/Linux testing (jessie)
Release:testing
Codename:jessie
$ uname -r
3.13-1-amd64
how to replace grub2 with grub-legacy hassle-free? I mean, is there any danger in doing the following procedure: purging grub2 and installing the legacy version after that? I'm using Squeeze system with ext4.
View 1 Replies View RelatedThis passed weekend I decided to upgrade the household server. I found cheap 2 TB disks on sale, so I got 4 of them, and began the upgrade. All went well, I used dd to copy the LVM pv to a new disk, removed the old disks, setup the array in degraded mode, evacuated the copy volume, and added it into the array.... then reused the old disks in new desktops. (well all good after I turned on virtualization in the bios)... all except grub.
I setup a raid 1 array for the /boot partitions. So far so good... but I boot and it sees the grub MBR, I know this because it dumps me into the grub> shell. Now comes the weird part... I can boot it just fine by doing a cat /grub/menu.lst and then using the lines in there to boot it:
[Code]...
That works fine, but, when I reboot, no menu. I am perplexed. I copied /boot with tar (mounted the mirror on /mnt and did a "tar cf - | (cd /mnt; tar xvf -)", I ran grub-install, and update-grub, both a few times. I even dropped into the grub shell and had it setup each of the 4 disks in turn (I wanted to do that anyway, since I do really need to be able to boot from any of them... I guess I should have entries for them in menu.lst too... but one problem at a time...)
So here is my situation..i was using win 7 and ubuntu 10.10 in my dell studio 1555. and i wanted to try out debian so i installed debian in my pendrive. so the grub was modified. when the computer starts it shows debian,ubuntu and win7 no problem.. but if i remove the pendrive, nothing comes up. it shows grub rescue>..
so now i cant start up unless i plug in the pendrive. what to do now to solve this problem?? i want to restore my grub to the previos state.
When I try and boot my Debian computer I get the messages: Grub Loading stage1.5. Grub loading, please wait... Error 15 Is there any way of recovering from this - or is it simply a fresh install? I was attempting an upgrade from Lenny to Squeeze and despite a few hurdles it looked like it was all happening. Got the new kernel loading, and the new grub. It looked as though grub2 was working so I ran the grub-remove-legacy-support command (something like that) and now my computer won't boot grub or Linux.
I'm assuming the MBR on my harddrive is lost, however I don't know what state the partition is in. I'm guessing that maybe this has been lost as well. I tried a few tools from the Ultimate Boot CD but nothing here was able to re-install my grub or boot from any partition or even mount my file-system. I'm fearing the worst but would like it confirmed before I blow it all away with a new install.
I have installed Windows 7 on my laptop . Now, it directly boot from Windows 7 . I think the MBR overwrote my grub . I have found two methods by google , but still does work .
1: boot from debian install CD, Alt +F2 switch to the console. "grub " "root (hd0,0)" "setup (hd0,0)".
2:boot from CD, mount /dev/scsi/host0/bus0/target0/lun0/part1 /mnt ; chroot /mnt ; grub-install /dev/sda.
I was trying to get the Windows one working again. Here's what fdisk -l reads:
[Code]...
I'll change these or do some grub configurations, if anyone knows what ones can work.
If I recall correctly, my Squeeze desktop is working whereas my Squeeze laptop isn't.
Here are the errors: Failed to open a session for the virtual machine Ubuntu 10.04.2. The virtual machine 'Ubuntu 10.04.2' has terminated unexpectedly during startup with exit code 1.
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Machine
[Code]....
my Setup is Fedora 14 x64 + radeon hd 4830 i've downloaded .run package from ati site with latest driver for x64 systems. installed it, but didn't edited grub.conf becouse i didn't understood anything there (probably didn't spent enough time to get things understand) Now i've lost possibility to enter my Fedora system. during boot it lost it's modern blue boot screen (with filling drop), it was replaced by standard old boot screen with triple-color stripe. after this boot screen monitor start blinking going on and off. and on last step i'm getting "Fedora 14 boot bla bla bla something" on screen. nothing works except Ctrl+Alt+Delete. system reboots showing successful daemons shutting sequence. How can i edit grub menu from initial grub screen is it possible to it's own 'e' option or 'c' from grub command line?
View 4 Replies View RelatedI would like to know if there is any differences on how to install and to configure GRUB 2 in the different architectures (BIOS/IBM PC-Compatibles, EFI/MacIntel and Corebbot)? Does the Ubuntu installer automatically recognize the different architectures and install the appropriate GRUB 2 package ('grub-pc', 'grub-efi' or 'grub-coreboot' according to the arch)? Or does it just install 'grub-pc'? Is the location of GRUB 2's configuration files different depending on the arch of the computer? Or are they all located in '/boot/grub/', '/etc/grub/default' and '/etc/grub.d/', no matter the arch of the computer? Are the files' structure and options to configure GRUB 2 ('/etc/grub/default' and the scripts in '/etc/grub.d/') different depending on the arch of the computer?
View 3 Replies View Related