I am new to linux and I am attempting to establish a dual boot with Windows Vista 32 Bit and Linux Debian 503 i386-netinst. When I place the install cd into the cd drive and boot from the cd a problem occurs at "Booting the kernel."
A message appears:
[0.116007] ..MP-BIOS bug: 8524 timer not connected to IO-APIC
Then the installation just "stalls" and never moves past this point.
I've installed Linux Ubuntu 10.04 LTS on my computer, and the Dual-booting shows after starting the computer
But what I need to know is how do you set the timer so that if I don't press "Enter"...that it choses my preferred operating system in a certain period of time (seconds or minutes...etc) by itself?
I'm trying to reinstall Debian on one of my machines after an unsuccessful install of FreeBSD (it didn't jive with my ssd). Debian installations have never been a problem before on this particular setup before but now for some reason it won't get past the "Debian GNU/linux installer boot menu". The USB goes into idle mode and the menu does not respond to keyboard strokes. I've tried several debian images to no avail. Ubuntu seems to work just fine though but I don't want to install Ubuntu just because Debians having some problems. I booted ubuntu live and reformated the SSD I had tried to install FreeBSD on because there were no partition tables on it but that didn't work either. I'd like some expert input before I go do another `dd`.
View 2 Replies View RelatedI have just installed Squeeze on my laptap with a radeon mobility equipped laptop. When it boots, I see the following message:r600_cp: Failed to load firmware "radeon/RV635_pfp.bin".and some others, too, but it stalls at that point, and I cannot use CTRL-ALT-F2 to get a text-based prompt - in fact, I can only seem to get it back with a ALT-SYSRQ (R-E-I-S-V-B) sequence to force a reboot. It is a multi-boot system, with a windows partition, Ubuntu partition, and the new Debian partition. The Ubuntu and Windows partitions will still boot, only the Debian stalls.
When I boot into Ubuntu, I can see the Debian partition, and can see (for instance) the /var/boot/dmesg file, but it only says:"(Nothing has been logged yet.)"So, being new to debian itself (even though, I know, that Ubuntu has a debian base), how can I make it boot without X, which is I presume, the center of the difficulty? Can I change some file on the debian partition using Ubuntu to get the debian partition to boot in text only mode, and then try to fix the radeon driver?
Alternatively, can I put the proper files for the radeon driver *from* the Ubuntu partition *to* the debian partition and expect it to load and boot correctly? I did, at one point, download and install the proprietary ATI driver files on Ubuntu, so can I put them in a proper place on the debian install?
I was able to copy the iso file and tried the installation however I stubbled upon the same problem I had when I tried installing Fedora 11. The message I received was "(1) (0.048001) MP-BIOS bug:8254 timer not connected to IO-APIC (2) (0.064001) Kernel panic-not syncing:IO-APIC + timer doesn't work Book with apic debug and send a report. Then try booting with the 'no apic-option'.
View 4 Replies View RelatedI installed Windows, then Ubuntu, but I don't know how to set the timer for the Dual-boot menu to start at Windows firstOn my Laptop, Ubuntu is set to run first and it's set to start after 10 secondsBut I wasn't the one who installed Ubuntu on my Laptop, it was someone else...etc. So I don't really know how to do the thingI want to set the Dual-boot so that Windows bee's the first one to start loading, at a timer of 1 minute
View 9 Replies View RelatedThe "MP-BIOS bug: 8254 timer not connected to IO-APIC" error message shows up on boot on at least one of my RHEL servers, and I'm not quite sure what to make of it. My understanding of the situation is that the timer is located elsewhere on the motherboard than where the kernel looks for it. Is this correct?
I've come across people suggestin one should disable APIC by adding "noapic" to the kernel boot options, but which consequences does this imply - in SNP setups only one CPU will be used by the kernel?
I have installed splashy from sid. Rest of the system is squeeze, and put the parameter "vga=791 splash quiet" in the kernel parameter...
Unfortunately this is not working properly. It does load the splash image as intended, but it then just hangs here, and does not load the OS unless I press enter. (I asume that something is hangning, but I cannot see the shell from here, and ctrl+f2-f6 is not working so I cannot get to any tty).
Then after boot, I can only see the / partition. But not /home. Duing a fdisk -l shows up the partitions, so they are there, just not mounted at boot?
If I press F2 at boot, before the image shows up, it does actually boot without any issues at all. It must be something with the image loading that is causing this.
I have some virtual machines running with CentOS 5.3 (32 bit) and everything works as expected. To test a possible upgrade I took one of then and did yum clean all yum update after rebooting I get a kernel panic with the following message:
MP BIOS BUG : 8254 timer not connected to APIC IO I know that I can change the boot command not to use APIC and after that the machine boots again but I doubt that there has been any change to the virtual APIC implementation during the upgrade of the OS. Is there anything that iI should exclude from upgrading while working in a vm? I use VMWare Player 2.5.3 build-185404 on a 64 bit Ubuntu 9.04 as host.
This is what is happening I downloaded the Ubuntu 10.04.1 LTS MD5 check and everything good for burning
Burned the image and restarted my laptop for installation.
Well I get the Ubuntu logo with the little points down and looks like loading but it stalls and does nothing after some time.
Don't know what to do I'm on Fedora now but I want ubuntu.
I've been using Linux (Fedora) since 2005 (when I happily abandoned Windows) and loved every minute of it. No installation or other unresolvable problems. But now, I am totally stuck. A month ago, they just gave me a new desktop in the office: Dell Optiplex 960 with the Intel Core 2 Duo vPro chip. So I waited for Fedora 11 to come out, burned the x86-64 Install Media on a DVD, repartitioned the hard drive like I always do on new Windoze machines, and began installing. The install process gets to this announcement and stops:
mounting /tmp as tmpfs... done Then, after a 5-minute wait, if I push the power button on the computer for a hard reboot, then it says:
running install running /sbin/loader and then stalls for good. Then all I can do is hard-reboot again.
So, out of curiosity (and for other reasons), I tried booting the machine from other linux disks: Knoppix, and SystemRescue (www.sysresccd.org). They all stall at different points. The funny thing is that both Fedora 11 x86-64 and SystemRescue happily boot on my personal one-year-old Lenovo T61 Intel Centrino Duo VPro laptop.
I get a feeling that somehow the Intel Core 2 Duo vPro is causing the problem. I also think that there is got to be someone else out there who either had this problem, or was able to install F11 on similar Dell box. Google search did not produce actionalbe answers for me.
I am trying to install the PPC kernel on an iBook G3. The CDs boot up, however both the net-install and the regular install cd both freeze up after it looks for harddisks. The screen is blue. The box title says
"Loading additional components"
"0%"
"Retrieving lvm2-udeb"
I have no clue what to do. I am trying to get an error readout, but nothing but the power button works. It shuts it off. I check the system clock and it was wrong, but I got it set to the correct time. I don't have and OSX disks. I am wanting a full Linux HD. Please let me know how to trouble shoot. (I have seen that many people have no problem installing this on there macs. The os is still working on the os side, but I want to switch it to Linux.)
Before the installation, I had triple boot of WinXP, Win 7, Ubuntu 10.10. As you can guess, the main boot-loader was grub. The second is Win 7 boot loader, and there it gives the option what to choose, load XP or Win 7.I made a decision to remove Ubuntu and install Debian(you know better than me why I did). So first, I searched a guide how to un-dual-boot. It told me to delete the two partition that Ubuntu use(swap and ext4) and write to MBR the win 7 boot-loader(using EasyBCD), so I delete them and use EeasyBCD. At this stage, I had 2 partitions: NTFS for XP and NTFS for Win 7, and the Win 7 boot-loader(and XP) worked pretty well.I install the latest testing of Debian(6 RC2) from DVD1 using this guide, except I choose to use the graphical installer, ext4(not ext3 as there), install the desktop environment, and choose to install grub(even know it didn't asked me). The swap partition I set is 3 GB because my RAM is 2 GB, even know that ubuntu set it in the past to 2 GB.The installation went pretty well, just when come to grub package, it says that there was an error with installing grub package(it didn't told me what), I had no choice, so I choose to skip over grub/lilo and finish with no boot manager. I was thinking to myself: "So I couldn't install grub, at least I have the Win 7 boot-loader(which contain XP loader), and maybe Win 7 boot-loader will recognize Debian too.". But I end up with no boot at all.It told me than when choose not to install boot-manager that I need to load /vmlinuz and give it the parameter root=/dev/sda4(my deb partition).I think that if I could install grub, I could load all my boots("sudo grub update" right?).How can I fix it?
View 3 Replies View RelatedI recently bought a new Samsung netbook N310 and want to install dual-boot Debian lenny along with windows xp home edition. My CPU is like this: Intel Atom CPU N270 1.6GHz which architectures and kernels I should download from the cd installation? there are so many:alpha, amd64, armel, hppa, i386, ia64, mips, mipsel, powerpc, s390, and sparc.
View 4 Replies View RelatedIs it possible to install Windows XP on a machine that already has Debian 7.8? I find lots of articles on installing Debian after but not before XP.
I would like to get a prompt at startup to select Windows XP or Debian 7.8 and then choose which one I want. The reason I want to do that is because I have Guitar Pro on XP and cant find anything as good and also I want to watch Netflix and cant seem to be able to find a way to do that on Debian 7.8 except windows emulator which defeats the point of Debian anyway. Also my Epson V500 will not work on Debian 7.1 and I have tried everything, been to Epson, installed drivers etc..
I have Lenny installed & it works fine, in a few days will add Windows 7 (want to dual boot - 1 250 GB hard disk) used gparted to free up lots of room for Win 7
- My question is this, Debian then Win or Win then Debian (I want GRUB to manage both so hope since Lenny is installed Win 7 will use the free space no problem) ?
I have Debian installed but I need to dual boot with distribution based on Ubuntu 14.04. This is my first UEFI dual boot install attempt. And I must do it right. I must not lose my Debian !
Code: Select allDisk /dev/sdb: 232,9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
[Code] ....
Ubuntu will go to /dev/sdb5 but I don`t no for sure what to do when installing Ubuntu. How to select during install existing UEFI partition(/dev/sdb1) so Debian and Ubuntu can use it. Can I select existing UEFI partition like I would do for /home or /swap ? Will this work ?
And what will happen with Grub if I select install grub ? I want to manage grub from Debian, it is my main OS. Can I skip Grub install and just update grub on my debian after ubuntu install ? Or I just install grub, then after completed Ubuntu install I install it again from Debian. Will this work ?
Is procedure of installing dual boot trivial like before or UEFI hide`s some unpleasant surprise.
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'. :/
Initially had windows xp in my system. Picked up on free partition (*it was not a primary partition*) and installed Debian from CD. The installation went fine. Towards end of installation the grub install ran detected windows xp presence and I continued with the install. End of install, prompted that the system would reboot.
However on reboot, I wasnt presented when boot option ( windows xp vs debian) but my windows xp directly got booted. How to get this boot option.
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 RelatedMy Toshiba Satellite C870-198 has Debian 7.7 installed in UEFI mode alongside Windows 8.1. The GRUB menu no longer displays, but the machine boots straight into Windows.
I can boot into Debian or Windows from rEFInd installed on a USB stick. The rEFInd menu has the following entries:
The Debian entry actually launches the GRUB menu which was installed with Debian.
Code: Select allBoot Microsoft EFI boot (Boot Repair backup) from Basic data partition.
Boot supposed Microsoft EFI boot (probably GRUB) from Basic data partition.
Boot EFIubuntugrubx64.efi from Basic data partition.
Boot EFIdebiangrubx64.efi from Basic data partition.
Boot bootootx64.efi from Basic data partition.
Boot vmlinuz-3.2.0-4-amd64 from boot.
In an attempt to fix GRUB I executed the commands in the 'Reinstalling grub-efi on your hard drive' section of: [URL] ....
Code: Select allmount /dev/sda1 /boot/efi
... surprisingly returned:
Code: Select all$LogFile version 2.0 is not supported. (This driver supports version 1.1 only.)
$LogFile version 2.0 is not supported. (This driver supports version 1.1 only.)
Did not find any restart pages in $LogFile and it was not empty.
The file system wasn't safely closed on Windows. Fixing.
Code: Select all[ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD"
... returned "EFI boot on HDD".
[Code] ....
... Where is Debian?
FULL HISTORY ....
=============================
The laptop came with Windows 8 preinstalled. I switched off Secure Boot and installed Ubuntu for UEFI dual boot. I recall having to use Boot Repair to get the GRUB boot manager working properly for both systems.
Recently I decided to replace Ubuntu with Debian 7.7 and first cloned the entire hard drive to a USB drive (The Clone Drive). This drive successfully boots into Ubuntu in UEFI mode.
Following this I took the opportunity to update Windows to 8.1, which broke GRUB as expected, so that the machine would only boot straight into Windows.
I installed Debian from a live USB stick in the mistaken belief that it would be bootable in UEFI mode. It did boot OK in legacy mode.
I then burned the full Debian 'DVD' image to a USB stick, booted it in UEFI mode and reinstalled Debian. In UEFI mode GRUB allowed me to boot into both Debian and Windows.
At this point I tested The Clone Drive. It was still able to boot into Ubuntu as previously, but after powering down, unplugging The Clone Drive and rebooting, the GRUB menu failed to appear and the machine booted straight into Windows. This is its current state.
I'm inexperienced in Debian. I have a dual-boot machine (64-bit, Debian 7.3, Windows 7, legacy boot) and encouter a problem at boot ever since I completed the installation of Debian 7.3 alongside the exising Windows 7. This machine has six hard drives: two are intended for ntfs storage of general data (raided together by RAID1); two more are intended for ext4 storage of general data (also raided together by RAID1); the fifth contains the Windows OS files and the sixth contains the Debian OS files. The problem is that I arrive to the grub_rescue each time at boot, seeing the message:
GRUB loading.
Welcome to GRUB!
error: no such device: e081517b-3399-4067-9294-8f0686f753ca.
Entering rescue mode...
grub_rescue>
I 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 RelatedI've set up a dual boot system with Debian and Windows 8, both installed on their own drive, with their own boot partition. I installed eveything in UEFI-Mode with fast- and secure boot turned off. Both installations are working, as I can access them by changing the boot priority in the Bios. What I cannot achieve is to let grub boot my windows installation.
This is the output of parted -l:
Code: Select allModel: ATA Samsung SSD 840 (scsi)
Disk /dev/sda: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 512MB 511MB fat32 boot
2 512MB 111GB 111GB ext4
3 111GB 128GB 17,0GB linux-swap(v1)
[Code] ....
As you can see, my linux install is on sda, my windows install on sdc (sdb beeing a data disk). This is the entry I made in the 40_custom file in etc/grub.d:
Code: Select allmenuentry "Windows 8.1" {
insmod part_gpt
insmod chain
set root='(hd2,gpt2)'
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
boot
}
I think this should be fine, but if I choose the windows entry wehen grub is booting, it says: error: no such partition. It's my first debian installation, and I am stuck here. Not too much of Linux experience in general.
My laptop setup is:
sda1: W7
sda2: FAT16
sda3: /boot
sda4: encrypted LVM with debian (everything besides /boot)
now I've re-installed W7 so grub was overwritten. I've tried the procedure which worked for me previously:booting with the netinst usb in rescue mode, choosing a root partition to mount, using grub-install to reinstall the grub:
Code: Select allmount /dev/sda3 /boot
grub-install /dev/sda
Now I'm on Jessie (stable), and this time this fails, and I am able to mount only sda3.grub-install doesn't exit so I'm assuming it has been replaced by `grub-installer'. also '/boot' doesnt exist so I created it manually.
Code: Select allmount /dev/sda3 /boot
grub-installer /dev/sda
The latter fails with
Code: Select all/dev/sda/proc not a directory