Re: shim boot-loader problem
On 25/03/2023 04:48, KCB Leigh wrote: > Through about May of 2022 I was able to also boot with Ubuntu, with no problems... but some time in the last half of 2022, I updated Debian, & now, although the Ubuntu option exists in the GRUB boot loader menu, when I select it, I get the error message: 'bad shim signature' & I cannot boot with Ubuntu any more. Perhaps old key that was used to sign shim in ubuntu has been revoked since that time due to a vulnerability in grub. If so then you need to update the shim-signed package. /EFI/debian/ fbx64.efi, grubx64.efi, mmx64.efi, shimx64.efi BOOTX64.CSV & grub.cfg I think the relevant file is the shimx64.efi file. On the The relevant file can be found in output of (it does not matter if Debian or Ubuntu is booted) efibootmgr -v Likely you are right. Ubuntu volume, the /boot/efi/ directory is completely empty & I've not been able to find any files with names containing shim. Perhaps a wrong partition is mounted to /boot/efi. Usually the same partition should be mounted in Debian and Ubuntu. Compare fdisk -l findmnt /boot/efi My QUESTION: can I simply copy the /EFI/debian/... directory & files to the UBUNTU volume to enable the machine to boot when secure boot is enabled? No. Files are signed with distribution-specific keys and have different compiled in paths (/EFI/debian, /EFI/ubuntu) Ensure that the proper partition is mounted to /boot/efi and run update-grub. I do not remember if it is enough or shim package has its own script. I suggest to look into EFI/BOOT directory on the EFI System Partition. It may contain fallback from some OS. This directory is intended for removable media, but firmware may prefer it even for built-in drives. Signed shim .efi file may be installed as EFI/BOOT/BOOTX64.EFI. Several years ago buggy EFI was not uncommon. Notice that os-probber was disabled by default some time ago, so alternative OS entries disappeared from *grub* menu unless it is explicitly enabled. It should not affect the firmware (BIOS) boot menu. You may get some impression of expected file layout for EFI system partition from https://wiki.debian.org/UEFI
shim boot-loader problem
I have an ACER ASPIRE 5.14 laptop with an internal hard disk, with both Windows 10, & Ubuntu v.20.04 on separate partitions (which I use only occasionally), but have been running the machine primarily from a USB stick with Debian 11.6: Linux cpe-67-241-65-193 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64 GNU/Linux The problem: > I can boot with Debian with no problems; > I can boot with Windows with no problems; > Through about May of 2022 I was able to also boot with Ubuntu, with no problems... but some time in the last half of 2022, I updated Debian, & now, although the Ubuntu option exists in the GRUB boot loader menu, when I select it, I get the error message: 'bad shim signature' & I cannot boot with Ubuntu any more. > To boot with Ubuntu, I have to disable secure boot in the BIOS/UEFI setup (F2 on my computer). With earlier versions of the kernel, I think one had to disable secure boot to boot with debian, but after kernel 5.10, one could boot with secure boot enabled, as my experiences through the middle of 2022 showed. > The APPARENT reason is that on the Debian boot volume, the /boot/efi/ directory contains: /EFI/debian/ fbx64.efi, grubx64.efi, mmx64.efi, shimx64.efi BOOTX64.CSV & grub.cfg I think the relevant file is the shimx64.efi file. On the Ubuntu volume, the /boot/efi/ directory is completely empty & I've not been able to find any files with names containing shim. My QUESTION: can I simply copy the /EFI/debian/... directory & files to the UBUNTU volume to enable the machine to boot when secure boot is enabled? My worry is that the Ubuntu OS uses a different version of kernel: the 2 most recent versions of kernel on each volume are: DEBIAN 11.6 | UBUNTU 5.10.0-20-amd64 | 5.15.0-67-generic 5.10.0-21-amd64 | 5.19.0-35-generic so the shimx64.efi may work for the debian OS but not the UBUNTU, though this shim 'boot-loader' is 'used' before the kernel, I think. I would be most appreciative of any advice, or suggestions for a better place to submit this question, if this forum's not appropriate. With many thanks, Ken (I have not subscribed to the list, but will try to check it; I would be very grateful if replies could be cc to my e-mail address: kcbl2...@yahoo.co.uk.)
Re: Bullseye installation failure because boot loader not installed
On Sun 15 Aug 2021 at 10:48:58 (-0400), Greg Wooledge wrote: > On Sun, Aug 15, 2021 at 08:19:35PM +0700, Ken Heard wrote: > > Having noted that the release of Bullseye is imminent I decided to > > use the RC2 iteration of Bullseye rather than Buster. > > I consequently downloaded file 'Debian-bullseye-DI-rc2-amd4-netinst.iso' > > I don't know where you're getting your information from, but you > appear to be out of date in a few respects. > > Bullseye was officially released yesterday. You should be using an > installer image labeled "11.0", not one labelled "rc2" (release > candidate 2). In fact, I don't even think that was the final release > candidate. I thought there were at least 3 of them, possibly more. > > It's quite possible that the issues you encountered were fixed after > that release candidate image was created. I assumed this account started, say, a number of weeks ago, and the OP stuck with the original media for continuity's sake. But if the full account is posted in due course, I hope it's more informative than would be suggested by statements like: "The installer however did not like the answer" "Once again I did not really have much choice in the matter" "the installer did not seem to like that answer either" (Personally, I only tested rc2 on a BIOS-booting machine. As expected, I still got the "seems that this computer is configured to boot via EFI" screen that's entirely inappropriate for this class of PC.) Cheers, David.
Re: Bullseye installation failure because boot loader not installed
On Sun, Aug 15, 2021 at 08:19:35PM +0700, Ken Heard wrote: > Having noted that the release of Bullseye is imminent I decided to > use the RC2 iteration of Bullseye rather than Buster. > I consequently downloaded file 'Debian-bullseye-DI-rc2-amd4-netinst.iso' I don't know where you're getting your information from, but you appear to be out of date in a few respects. Bullseye was officially released yesterday. You should be using an installer image labeled "11.0", not one labelled "rc2" (release candidate 2). In fact, I don't even think that was the final release candidate. I thought there were at least 3 of them, possibly more. It's quite possible that the issues you encountered were fixed after that release candidate image was created.
Re: Bullseye installation failure because boot loader not installed
On Sun 15 Aug 2021 at 20:19:35 +0700, Ken Heard wrote: [Extensive information snipped] >From Knoppix live check that the Debian installation is on /dev/sda. Then 'grub-install /dev/sda' and boot. -- Brian.
Bullseye installation failure because boot loader not installed
I recently upgraded a desktop computer by replacing major parts in it including the mainboard and CPU. I now want to install in it a more up to date operating system than Wheezy which was the one used before the upgrade. Having noted that the release of Bullseye is imminent I decided to use the RC2 iteration of Bullseye rather than Buster. I consequently downloaded file 'Debian-bullseye-DI-rc2-amd4-netinst.iso' and also the 2021-07-18 version of the 'Debian GNU/Linux Installation Guide". I had considerable difficulties with the installer, to the effect that it took me about 27 hours off and on over 10 days with nine false starts. I managed to complete the installation but with one crucial exception. In due course I want to impart to you my complete installation experience -- but not before that exception is rectified. I refer to the last item on the installation menu, 'Install the boot loader' -- it was never installed. The verbatim transcript of the messages received from the installer at this point and my answers thereto follow. ---- Install the GRUB boot loader. First message from the installer: It seems that this new installation is the only operating system on this computer. If so, it should be safe to install the GRUB boot loader to your primary drive (UEFI partition/boot record). I gave my consent to have the GRUB boot loader to my primary drive. Second message: You need to make the newly installed system bootable, by installing the GRUB boot loader on a bootable device. The usual way to do this is to install GRUB to your primary drive (UEFI partition/boot record). You may instead install GRUB to a different drive (or partition), or to removable media, Device for boot loader installation: Enter device manually /dev/sda (ata-ST2000DM008-2FR102_ZFL3PHLG /dev/sdb (ata-ST2000DM001-1CH164_Z340HH9V I chose to install it on /dev/sda. The installer however did not like the answer and sent me a third message: It seems that this computer is configured to boot via EFI, but maybe that configuration will not work for booting from the hard drive. Some EFI firmware implementations do not meet the EFI specification (i.e. they are buggy!) and do not support proper configuration of boot options from system hard drives. A workaround for this problem is to install an extra copy of the EFI version of the GRUB boot loader to a fall back location, the “removable media path”. Almost all EFI systems, no matter how buggy, will boot GRUB that way. Force GRUB installation to the EFI removable path? or Once again I did not really have much choice in the matter; so I chose and pressed 'Enter', but the installer did not seem to like that answer either. Next a series of messages crossed the screen too quickly for me to read them, and then the screen went blank. Not only was the ‘Install the boot loader’ aborted but also was aborted whatever would follow – if anything. I would consequently be very grateful if someone could tell me what needs to be done to provide the boot loader and how to do it. I am quite eager to start using this computer as soon as possible. By the way I was able to find a way into the computer by doing a Knoppix live installation. I examined the files in /boot/grub, the one belonging to the computer, not to Knoppix. I discovered that in directory /boot/grub there is no grub.cfg file. Also there is no directory /boot/efi. Finally I noted that from the installer start page grub commands are accessible. On 2021-08-12 I sent this message to sub...@bug.debian.org; but I was told that my message will be ignored unless I identify the package to which it relates and its version. My situation is such that i don't think i can provide such information. For the record the mainboard is a Gigabyte B450 I Aorus pro wifi. The CPU is a 4 core AMD RyZen3 3200G with Radeon Vega 8 Graphics. I will not be using a separate GPU. There are two 2 tb hard drives for a RAID1, with LVM. Regards, Ken
Re: [OT] CentOS 6 [Was: Re: how to quickly recover buster boot loader]
On Wed 05 Aug 2020 at 17:51:36 (+), Long Wind wrote: > no, i try centos for fun and fedora and opensuse > my hardware is old and old software usually require less memory/disk > these old software are new to me, i might discover interesting app > http://archive.debian.org/ > http://archives.fedoraproject.org/ > i don't think update is important Bear in mind that when you install some distribution "just for fun", then unless you take precautions, it will naturally take control of the boot process. So you probably want to have a well-practised method standing by for restoring your preferred distribution's. Cheers, David.
Re: how to quickly recover buster boot loader
On Wed 05 Aug 2020 at 15:14:33 +, Andrew Cater wrote: > Boot from Debian install media. Use rescue mode. Mount Debian partition > when prompted. Run os-prober and update-grub then exit. Machine should > reboot into Debian. No need to run os-prober; update-grub does it. -- Brian.
[OT] CentOS 6 [Was: Re: how to quickly recover buster boot loader]
On Wed, 05 Aug, 2020 at 00:04:48 +, Long Wind wrote: >i have win7 at sda1 and buster at sda2 >i install centos 6 at sda3, it can boot win7, can't see buster >i mean i can't boot buster now >is there some rescue image that can be written to bootable usb disk? >or do you know how to config centos 6 boot loader? >is buster's boot code installed at sda2 by default? An off-topic question: do you have a particular need for CentOS 6? It reaches its end of life in November.
Re: how to quickly recover buster boot loader
Boot from Debian install media. Use rescue mode. Mount Debian partition when prompted. Run os-prober and update-grub then exit. Machine should reboot into Debian. On Wed, Aug 5, 2020 at 1:28 PM Long Wind wrote: > Thank Greg! > but chroot dance is new to me, it doesn't seem easy > it involves many steps (commands) > a small error will lead to failure > > i install centos just for fun > i can install lubuntu at sda3 and it can boot buster > > > > > On Wednesday, August 5, 2020, 8:15:14 PM GMT+8, Greg Wooledge < > wool...@eeg.ccf.org> wrote: > > > On Wed, Aug 05, 2020 at 12:04:48AM +, Long Wind wrote: > > > i have win7 at sda1 and buster at sda2i install centos 6 at sda3, it can > boot win7, can't see busteri mean i can't boot buster now > > is there some rescue image that can be written to bootable usb disk? > > or do you know how to config centos 6 boot loader?is buster's boot code > installed at sda2 by default? > > > I'm going to assume you're using Legacy/MBR booting, because I don't know > enough about UEFI to answer this question in that universe. > > If you're trying to multi-boot several different Linuxes from one > hard drive, the first thing you have to do is make a decision. You > must choose which Linux will be in control of the boot loader. > > Let's say you choose Debian. (If you choose something else, stop > reading now, and go ask the other OS's mailing list for help.) > > First step, then, will be to boot into Debian successfully. For this, > you'll probably need to boot into whatever Linux you *can* boot, whether > that's the CentOS on the hard drive, or a rescue CD, or whatever. > > Once you're booted into *a* Linux, then you can do the chroot dance > to mount the Debian file system(s) underneath that. > > According to the IRC bot factoid, that dance goes something like > this: > > Mount your root filesystem with "mount -t ext2 /dev/whatever /target" > and make /dev, /proc and /sys usable with "mount --rbind --make-rslave > /dev /target/dev ; mount -t proc none /target/proc ; mount -t sysfs none > /target/sys". You can then chroot into the system with "chroot /target". > > There may be other dances that will also work. > > Once you're chrooted into Debian running under some sort of Linux > kernel, first make sure the os-prober package is installed. Then you can > write Debian's GRUB into the master boot recor, by running grub-install. > > After doing grub-install, you should have GRUB in the hard drive's > master boot record and it should be configured to read the menu in > Debian's version of the /boot directory. > > In order to make the Debian GRUB menu point to all of the operating > systems on your hard drive, make sure os-prober is installed (yes, I > know, I already said it; I'm saying it again). Then run update-grub. > > Exit out of the chroot, unmount it, and reboot. You should get Debian's > GRUB menu, and you should be able to boot into Debian, at the very > least. > > If the Debian GRUB menu doesn't contain all of the operating systems > that you think it should contain, then you'll have to poke around in > the update-grub and os-prober internals and figure out what's wrong. > > Once you get everything working, you'll need to remember that you have > chosen to make Debian the controller of the boot loader. Every time > you make a kernel change to any of the *other* Linuxes on your hard > drive, you'll need to boot into Debian, and run update-grub, to pick > up the changes in the other Linuxes. > > >
Re: how to quickly recover buster boot loader
On Wed, Aug 05, 2020 at 12:04:48AM +, Long Wind wrote: > i have win7 at sda1 and buster at sda2i install centos 6 at sda3, it can boot > win7, can't see busteri mean i can't boot buster now > is there some rescue image that can be written to bootable usb disk? > or do you know how to config centos 6 boot loader?is buster's boot code > installed at sda2 by default? I'm going to assume you're using Legacy/MBR booting, because I don't know enough about UEFI to answer this question in that universe. If you're trying to multi-boot several different Linuxes from one hard drive, the first thing you have to do is make a decision. You must choose which Linux will be in control of the boot loader. Let's say you choose Debian. (If you choose something else, stop reading now, and go ask the other OS's mailing list for help.) First step, then, will be to boot into Debian successfully. For this, you'll probably need to boot into whatever Linux you *can* boot, whether that's the CentOS on the hard drive, or a rescue CD, or whatever. Once you're booted into *a* Linux, then you can do the chroot dance to mount the Debian file system(s) underneath that. According to the IRC bot factoid, that dance goes something like this: Mount your root filesystem with "mount -t ext2 /dev/whatever /target" and make /dev, /proc and /sys usable with "mount --rbind --make-rslave /dev /target/dev ; mount -t proc none /target/proc ; mount -t sysfs none /target/sys". You can then chroot into the system with "chroot /target". There may be other dances that will also work. Once you're chrooted into Debian running under some sort of Linux kernel, first make sure the os-prober package is installed. Then you can write Debian's GRUB into the master boot recor, by running grub-install. After doing grub-install, you should have GRUB in the hard drive's master boot record and it should be configured to read the menu in Debian's version of the /boot directory. In order to make the Debian GRUB menu point to all of the operating systems on your hard drive, make sure os-prober is installed (yes, I know, I already said it; I'm saying it again). Then run update-grub. Exit out of the chroot, unmount it, and reboot. You should get Debian's GRUB menu, and you should be able to boot into Debian, at the very least. If the Debian GRUB menu doesn't contain all of the operating systems that you think it should contain, then you'll have to poke around in the update-grub and os-prober internals and figure out what's wrong. Once you get everything working, you'll need to remember that you have chosen to make Debian the controller of the boot loader. Every time you make a kernel change to any of the *other* Linuxes on your hard drive, you'll need to boot into Debian, and run update-grub, to pick up the changes in the other Linuxes.
Re: No Boot Loader -- Debian Latest Edition
On Fri, 29 Nov 2019 15:42:44 -0500 J B Martin wrote: > I have it booting now. > > I need to study how to use the GUI at this point. Thanks, Good, glad to hear it. In the future, please reply to the list so that archive readers will know how things worked out. Thanks -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: No Boot Loader -- Debian Latest Edition
On Fri, 29 Nov 2019 12:52:00 -0500 J B Martin wrote: > I am using the install CD and the install runs fine, > but after removing CD, the OS won't load the > boot sector. It isn't the OS that loads the boot sector, it's the firmware (BIOS' boot code). Have you had an OS on this computer before? Is this an UEFI boot or traditional? What's the exact text of the error message? -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
No Boot Loader -- Debian Latest Edition
Hello, I am using the install CD and the install runs fine, but after removing CD, the OS won't load the boot sector. It's an Intel i5 with 8gb RAM. I've changed all my power and CMOS setting and nothing works. Is this a common problem installing Debian? Thanks, Bryant -- Joseph Bryant Martin USA 804 223-0325 Info Voice 804 719-1705
Fwd: Loading OS into software model of SPARC(without BIOS and boot loader)
-- Forwarded message -- From: Renju Boben Date: Mon, Sep 29, 2014 at 3:54 AM Subject: Loading OS into software model of SPARC(without BIOS and boot loader) To: sparcli...@vger.rutgers.edu Hi, I have the software model of a SPARC v8 processor and its Memory management unit. The model accepts input (instructions) in the form . I am trying to load stripped down Linux 3.1.4 into it (without BIOS and boot loader). I have the kernel in the required format. But i don,t know from which address to start executing. Also, what should be the condition of the registers when the OS is about to load. I have read that in x86 architecture after 640KB there are special jump instructions (because original 8086 only had 640 KB of memory). Are there any similar jumps in SPARC. if so how does if affect loading OS. Has this jumping any dependence on Boot loader Regards, Renju Boben
Re: gdm3 issue [boot loader digression]
On Mon, Dec 9, 2013 at 5:04 PM, Neal Murphy wrote: > > Grub 2 is, as far as I know, still broken. This is the kind of statement that makes me laugh, this case or NM's or... 1) The silent majority of grub2 users have no problems. 2) File a bug report if grub2 (or any other package) fails for you. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=sxyxrboqmphsgaohwgvs6u8g-ja7oz6+g8rinzzy-q...@mail.gmail.com
Re: gdm3 issue [boot loader digression]
On Monday, December 09, 2013 06:06:24 AM Ralf Mardorf wrote: > On Mon, 2013-12-09 at 15:15 +0530, Kailash Kalyani wrote: > > The issue started when I removed old linux images from Ubuntu which is > > on another partition. That resulted in a grub update from ubuntu and > > since then I've had this issue. > > So the answer already seems to be there. Ubuntu did likely automatically > write a broken grub.cfg with what ever obscure boot option that does > break to log in your Debian. > > If possible you should use a good boot loader instead of GRUB, e.g. > Syslinux. I use GRUB 2 just for fun too, but edit grub.cfg manually. > > Use GRUB 2 from Debian, hopefully it's defaults are more sane than those > of *buntus and automatically generate a saner grub.cfg. Syslinux is nice, but it has its own problems and limitations. I couldn't get it to work on ISO installer, ISO converted-to-flash install and the system runtime. Grub 2 is, as far as I know, still broken. I once spent 2-3 weeks trying to change my firewall system from isolinux/lilo/grub to grub2 for all booting. I couldn't get it to work on ISO and it simply refused to install on the disk I told it to (it always used the first disk it found that had some form of grub2 on it). I finally quit and went back to grub legacy with all of redhat's patches. I had it re-integrated and running in about a half hour: booting the ISO and the ISO equivalent on flash/rotating drives--which entails copying the tree from the ISO, changing '(cd)' to '(hd0,0)' in the config file(s), and installing grub in the boot loader--and booting the runtime system. The firewall system now has a consistent boot presentation. Since then, I've fixed a few bugs in it; it now displays background images very nicely, handles multiple linked config files, works very well on serial consoles, and the 'hit a key to continue' works reliably to select the serial or VESA console when it finds both. My tuppence. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201312091204.21162.neal.p.mur...@alum.wpi.edu
Re: Error: Boot loader didn't return any data!
On Tue, 19 Feb 2013 14:22:28 +0100 Denis Witt wrote: > Any ideas? Got it solved. turns out that there was an apt-proxy pointing to a non existing machine, so the packages could not be loaded. Maybe xen-create-image should print an error about this. ;) Anyway, the logfile did. Best regards Denis -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130219145633.54436123@X200
Boot-loader flag during /boot partition setup 'on' or 'off'?
Hi Debian users, I noticed in the very beginning of the Debian Squeeze installer (under ‘help’) that it said: -begin- In order to start your new system, a so called boot-loader is used. It can be installed either in the master boot record of the first hard disk, or in a partition. When the boot-loader is installed in a partition, you must 'set' the boot-loader flag for it. Such a partition will be marked with ‘B’ in the main partion menu. -end- I am installing Debian Squeeze 'netinst' on a 2nd hard disk and will dual-boot with windows. In the partition setup during installation, I created my first partition on the 2nd drive as /boot. Do I need to ‘set’ the boot-loader flag in this /boot partition configuration to 'on'? When they mention the phrase, 'set the boot-loader flag', I assume they are instructing me to 'turn the flag ‘on’ in the partition menu for /boot. I see the default is set to ‘off’. Thank you -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CALDXikoFwc6q3kqzP SxkQ5b_nJfm=7pf-umeebtj4vj4...@mail.gmail.com
Re: restoring GRUB boot loader for Debian after reinstalling Windows 7
On 12/12/2011 01:05 PM, Colin Reinhardt wrote: Hi, I reinstalled a new (parallel) installation of Win7 on my primary (boot) drive, and the Win7 boot loader overwrote Debian GRUB which was previously installed. How can I restore GRUB so I can boot into either Debian or Win7 at system start up? Thanks! Colin I've done this on my Ubuntu laptop but it uses Grub2. My debian server still uses Grub Legacy and the procedures are different. I Googled and got this site. the instructions look right. good luck http://wiki.debian.org/GrubRecover Marcus. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ee645ab.5000...@kermitplace.us
restoring GRUB boot loader for Debian after reinstalling Windows 7
Hi, I reinstalled a new (parallel) installation of Win7 on my primary (boot) drive, and the Win7 boot loader overwrote Debian GRUB which was previously installed. How can I restore GRUB so I can boot into either Debian or Win7 at system start up? Thanks! Colin -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOJ5kvtc=mVcGs6nAZT-N00kK=MV=gpnqmmfqym1oqttonw...@mail.gmail.com
Re: Boot loader installation failed.
Hi. On Saturday 24 September 2011 18:11:33 Eneko Gotzon Ares wrote: > I'm a humble Mac user trying to start using Debian (Squeeze) on a 2.1 > GHz PowerPC G5. I did a Squeeze installation on my PowerMac G5 some weeks ago - no problem. Yaboot works fine - I have a dual boot installation Squeeze / Mac OS X using yaboot here on my machine. > The processor is a PowerPC 970fx "G5" with 64-bit data paths and > registers, with native support for 32-bit application code. > > I have download powerpc netinst image and run install64 command. I used the debian-6.0.1a-powerpc-CD1, not the netinstall one. > The installation progress well until the yaboot boot loader (last step > before finish): it always fails at its 83% progression rate. I have > unsuccessfully tried all options proposed by the installer. > > There is advice about installing the Debian Lenny's yaboot intead. > What you think? > Any help will welcome. You may try to ask on the debian powerpc mailing list as well: debian-powe...@lists.debian.org > Thank you very much. > -- > Eneko Gotzon Ares Good luck. Hartwig -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201109242115.55239.hartwig.atr...@arcor.de
Re: Boot loader installation failed.
> > > Forwarded Message > > From: Eneko Gotzon Ares > > To: debian-user@lists.debian.org > > Subject: Boot loader installation failed. > > Date: Sat, 24 Sep 2011 18:11:33 +0200 > > yaboot Since I'm not using Apple, I googled and it seems to be possible to use GRUB, http://sowerbutts.com/linux-mac-mini/ Hth, Ralf > > > > > > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1316889239.4078.31.camel@debian
Re: Boot loader installation failed.
On Sat, 24 Sep 2011 18:11:33 +0200, Eneko Gotzon Ares wrote: > I'm a humble Mac user trying to start using Debian (Squeeze) on a 2.1 > GHz PowerPC G5. (...) There is a dedicated mailing list for the ppc arch, just in case you still have not done it I would also post this question there: http://lists.debian.org/debian-powerpc/ Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.09.24.17.06...@gmail.com
Boot loader installation failed.
I'm a humble Mac user trying to start using Debian (Squeeze) on a 2.1 GHz PowerPC G5. The processor is a PowerPC 970fx "G5" with 64-bit data paths and registers, with native support for 32-bit application code. I have download powerpc netinst image and run install64 command. The installation progress well until the yaboot boot loader (last step before finish): it always fails at its 83% progression rate. I have unsuccessfully tried all options proposed by the installer. There is advice about installing the Debian Lenny's yaboot intead. What you think? Any help will welcome. Thank you very much. -- Eneko Gotzon Ares
Re: boot loader
On Sb, 26 mar 11, 14:30:13, shawn wilson wrote: > > > > You can fix it with ms-sys[1] from System Rescue CD[2] > > > > [1] http://ms-sys.sourceforge.net/ > > i'll have to try this. the sourceforge page says that it works on > fat32. however, freshmeat has a changelog that seems to indicate it > works on vista/7 which (i hope) also means it works with xp (or any > other ntfs based system). Worked for me on Windows XP. > > [2] http://www.sysresccd.org/ > > heh, still haven't gone to the store to get media (which is why i > haven't tried anything else yet). i'm sorta hoping that #1 will make > it so that i don't have to go to the store :) You can put it on a USB stick. Just loop-mount the iso somewhere (but not on /mnt) and run the script in the root directory. HTH, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: boot loader
On Sat, Mar 26, 2011 at 5:26 AM, Andrei Popescu wrote: > On Jo, 24 mar 11, 12:30:39, shawn wilson wrote: >> not sure of the topicality of this here but... >> >> i've got a computer with ntldr messing up. since i don't have a windows xp >> disk, i have no way of fixing this (besides torrent). so, i was hoping to >> find some sort of quick install that just shoved grup on the system and made >> a minimal partition for /boot (and whatever else is required for grub). > > You can fix it with ms-sys[1] from System Rescue CD[2] > > [1] http://ms-sys.sourceforge.net/ i'll have to try this. the sourceforge page says that it works on fat32. however, freshmeat has a changelog that seems to indicate it works on vista/7 which (i hope) also means it works with xp (or any other ntfs based system). > [2] http://www.sysresccd.org/ heh, still haven't gone to the store to get media (which is why i haven't tried anything else yet). i'm sorta hoping that #1 will make it so that i don't have to go to the store :) i have a kubuntu boot cd, so either an apt-get for this or get headers and libraries and compile and run. i'm just hoping that there's enough ram on this thing to handle this -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTimBEfM9Qm3i4O=nHMPJkWQoye=Z8kQ=-au2g...@mail.gmail.com
Re: boot loader
On Jo, 24 mar 11, 12:30:39, shawn wilson wrote: > not sure of the topicality of this here but... > > i've got a computer with ntldr messing up. since i don't have a windows xp > disk, i have no way of fixing this (besides torrent). so, i was hoping to > find some sort of quick install that just shoved grup on the system and made > a minimal partition for /boot (and whatever else is required for grub). You can fix it with ms-sys[1] from System Rescue CD[2] [1] http://ms-sys.sourceforge.net/ [2] http://www.sysresccd.org/ Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: boot loader
On Mar 24, 2011 5:26 PM, "Mark" wrote: > > On Thu, Mar 24, 2011 at 2:22 PM, shawn wilson wrote: >> >> >> now, that's pretty cool. bad part is now i have to go to the store and >> get more cds (or probably better, a thumb drive). however, at least i >> have an easy way to get this system up and probably use one of the >> boot loaders Bob's suggested or figure out if windows can revive its >> own mbr (probably not). >> > for windows, booting into rescue mode (pending you get your hands on a CD), it's just 2 commands: > > fixmbr > fixboot c: > > and you will be booting windows again. Yeah, hence why I said I didn't have a windows xp cd (have win7 but I didn't want to chance messing this up). See, dude has a 250G disk and I don't have that space to spare for him, so no going back :)
Re: boot loader
On Thu, Mar 24, 2011 at 02:25:44PM -0700, Mark wrote: > On Thu, Mar 24, 2011 at 2:22 PM, shawn wilson wrote: > > > > > now, that's pretty cool. bad part is now i have to go to the store and > > get more cds (or probably better, a thumb drive). however, at least i > > have an easy way to get this system up and probably use one of the > > boot loaders Bob's suggested or figure out if windows can revive its > > own mbr (probably not). > > > > for windows, booting into rescue mode (pending you get your hands on a CD), > it's just 2 commands: > > fixmbr > fixboot c: > > and you will be booting windows again. > Brings back numerous memories. Super grub disk is nice to have on hand for general booting issues. It does that windows fix also. -- Regards, Freeman "Microsoft is not the answer. Microsoft is the question. NO (or Linux) is the answer." --Somebody -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110324213255.GA22932@Europa.office
Re: boot loader
On Thu, Mar 24, 2011 at 2:22 PM, shawn wilson wrote: > > now, that's pretty cool. bad part is now i have to go to the store and > get more cds (or probably better, a thumb drive). however, at least i > have an easy way to get this system up and probably use one of the > boot loaders Bob's suggested or figure out if windows can revive its > own mbr (probably not). > > for windows, booting into rescue mode (pending you get your hands on a CD), it's just 2 commands: fixmbr fixboot c: and you will be booting windows again. HTH.
Re: boot loader
On Thu, Mar 24, 2011 at 4:54 PM, Freeman wrote: > On Thu, Mar 24, 2011 at 12:30:39PM -0400, shawn wilson wrote: >> not sure of the topicality of this here but... >> >> i've got a computer with ntldr messing up. since i don't have a windows xp >> disk, i have no way of fixing this (besides torrent). so, i was hoping to >> find some sort of quick install that just shoved grup on the system and made >> a minimal partition for /boot (and whatever else is required for grub). >> >> as it is, i can't find anything that does this. so i'm curious of everything >> that grub depends on? just /boot or do i need some config files in /etc and >> do i need any binaries for it? i'm not interested in maintaining grub from >> the system (it would just be maintained from a boot cd if at all). i just >> need it to boot and work. i'm going to use gparted to make a ~10 meg >> partition (i think that's all i should need). >> >> ... unless anyone knows of a system that does all of this for me, then i'll >> just let it ride and not worry about anything? > > I've always used super grub disk . I don't think it will make partitions, > maybe subdirectories. It can probably install grub without new partitions. > But it might also restore a windows boot. > now, that's pretty cool. bad part is now i have to go to the store and get more cds (or probably better, a thumb drive). however, at least i have an easy way to get this system up and probably use one of the boot loaders Bob's suggested or figure out if windows can revive its own mbr (probably not). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTim4NMFCtXqBYe1E-q56zVpVfD-52g-9GQ2Xgq=i...@mail.gmail.com
Re: boot loader
On Thu, Mar 24, 2011 at 12:30:39PM -0400, shawn wilson wrote: > not sure of the topicality of this here but... > > i've got a computer with ntldr messing up. since i don't have a windows xp > disk, i have no way of fixing this (besides torrent). so, i was hoping to > find some sort of quick install that just shoved grup on the system and made > a minimal partition for /boot (and whatever else is required for grub). > > as it is, i can't find anything that does this. so i'm curious of everything > that grub depends on? just /boot or do i need some config files in /etc and > do i need any binaries for it? i'm not interested in maintaining grub from > the system (it would just be maintained from a boot cd if at all). i just > need it to boot and work. i'm going to use gparted to make a ~10 meg > partition (i think that's all i should need). > > ... unless anyone knows of a system that does all of this for me, then i'll > just let it ride and not worry about anything? I've always used super grub disk . I don't think it will make partitions, maybe subdirectories. It can probably install grub without new partitions. But it might also restore a windows boot. -- Regards, Freeman "Microsoft is not the answer. Microsoft is the question. NO (or Linux) is the answer." --Somebody -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110324205405.GA12889@Europa.office
Re: boot loader
On 03/24/2011 09:30 AM, shawn wilson wrote: > not sure of the topicality of this here but... > > i've got a computer with ntldr messing up. since i don't have a windows > xp disk, i have no way of fixing this (besides torrent). so, i was > hoping to find some sort of quick install that just shoved grup on the > system and made a minimal partition for /boot (and whatever else is > required for grub). > > as it is, i can't find anything that does this. so i'm curious of > everything that grub depends on? just /boot or do i need some config > files in /etc and do i need any binaries for it? i'm not interested in > maintaining grub from the system (it would just be maintained from a > boot cd if at all). i just need it to boot and work. i'm going to use > gparted to make a ~10 meg partition (i think that's all i should need). > > ... unless anyone knows of a system that does all of this for me, then > i'll just let it ride and not worry about anything? Check out "Smart Boot Loader" (http://btmgr.sourceforge.net/) or "Master Boot Loader" (http://mbldr.sourceforge.net/) instead. -- Bob McGowan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d8b88db@symantec.com
boot loader
not sure of the topicality of this here but... i've got a computer with ntldr messing up. since i don't have a windows xp disk, i have no way of fixing this (besides torrent). so, i was hoping to find some sort of quick install that just shoved grup on the system and made a minimal partition for /boot (and whatever else is required for grub). as it is, i can't find anything that does this. so i'm curious of everything that grub depends on? just /boot or do i need some config files in /etc and do i need any binaries for it? i'm not interested in maintaining grub from the system (it would just be maintained from a boot cd if at all). i just need it to boot and work. i'm going to use gparted to make a ~10 meg partition (i think that's all i should need). ... unless anyone knows of a system that does all of this for me, then i'll just let it ride and not worry about anything?
RE: Grub boot loader?
> Date: Thu, 4 Feb 2010 12:44:01 +1300 > From: mockingb...@earthlight.co.nz > To: debian-user@lists.debian.org > Subject: Re: Grub boot loader? > > On Wed, Feb 03, 2010 at 11:09:16AM +, Hadi Motamedi wrote: > > > Yes , I am running Sarge . I got the point . Thank you very much . > > So is your "problem" sorted? > > Sarge is unsupported now and any advice you recieve may not be correct > as there have been quite a few changes between Sarge -> Lenny. > > Is there a special reason you are not running Lenny? > > P.S. Please don't split threads. That is, don't create a new message > when replying to a post. Use list reply if you can, or if Gmail can't > cope with that then do a reply and arrange the headers to suit. > (That's if even Gmail will do that! :) ) > > > -- > Chris. > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Thanks for your message . The fact that I am using Sarge comes from the applications installed on my server . It is actually running Asterisk pbx 1.4 and DECT application software . For the Asterisk part , I want to upgrade it to Asterisk 1.6 (to make use of the new features) . But for the DECT application software , I am not sure if upgrading to Lenny can cause any software incompatibilities . Sorry that I am sending the reply to you from here , as the Gmail is not accessible from yesterday in my zone till now. _ Hotmail: Trusted email with Microsoft’s powerful SPAM protection. https://signup.live.com/signup.aspx?id=60969
Re: Grub boot loader?
On Wed, Feb 3, 2010 at 2:08 AM, Chris Bannister < mockingb...@earthlight.co.nz> wrote: > On Tue, Feb 02, 2010 at 06:15:12AM +, hadi motamedi wrote: > > The answer is easier to read and follow if you type it directly under > the question. Also, removing old text helps as well. > > > On Mon, Feb 1, 2010 at 2:24 PM, Chris Bannister < > > mockingb...@earthlight.co.nz> wrote: > > [snip] > > > - How can I check if it is running splashy ? > > I don't know - I've never run it or even looked at it, but apt-cache > policy splashy might help. > > > - No , I don't want to make these changes permanent . I want to change > them > > for that one reboot . So I want to touch grub edit menu. > > OK. > > > - Please find below the output of grep -v '^#' /boot/grub/menu.lst : > > title Debian GNU/Linux,kernel 2.4.27-2-386 > > That is a really old kernel. Are you running Sarge? > > > root (hd0,0) > > kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hda1 ro > > initrd /boot/initrd.img-2.4.27-2-386 > > savedefault > > boot > > titleDebian GNU/Linux , kernel 2.4.27-2-386 (recovery mode) > > root(hd0,0) > > kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hda1 ro single > > Look! You already have a single user mode. > > > initrd /boot/initrd.img-2.4.27-2-386 > > savedefault > > boot > > -- > Chris. > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > > Yes , I am running Sarge . I got the point . Thank you very much .
Re: Grub boot loader?
On Wed, Feb 03, 2010 at 11:09:16AM +, Hadi Motamedi wrote: > Yes , I am running Sarge . I got the point . Thank you very much . So is your "problem" sorted? Sarge is unsupported now and any advice you recieve may not be correct as there have been quite a few changes between Sarge -> Lenny. Is there a special reason you are not running Lenny? P.S. Please don't split threads. That is, don't create a new message when replying to a post. Use list reply if you can, or if Gmail can't cope with that then do a reply and arrange the headers to suit. (That's if even Gmail will do that! :) ) -- Chris. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Grub boot loader?
From: motamed...@hotmail.com To: debian-user@lists.debian.org Subject: Date: Wed, 3 Feb 2010 11:05:40 + On Wed, Feb 3, 2010 at 2:08 AM, Chris Bannister wrote: On Tue, Feb 02, 2010 at 06:15:12AM +, hadi motamedi wrote: The answer is easier to read and follow if you type it directly under the question. Also, removing old text helps as well. > On Mon, Feb 1, 2010 at 2:24 PM, Chris Bannister < > mockingb...@earthlight.co.nz> wrote: [snip] > - How can I check if it is running splashy ? I don't know - I've never run it or even looked at it, but apt-cache policy splashy might help. > - No , I don't want to make these changes permanent . I want to change them > for that one reboot . So I want to touch grub edit menu. OK. > - Please find below the output of grep -v '^#' /boot/grub/menu.lst : > title Debian GNU/Linux,kernel 2.4.27-2-386 That is a really old kernel. Are you running Sarge? > root (hd0,0) > kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hda1 ro > initrd /boot/initrd.img-2.4.27-2-386 > savedefault > boot > titleDebian GNU/Linux , kernel 2.4.27-2-386 (recovery mode) > root(hd0,0) > kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hda1 ro single Look! You already have a single user mode. > initrd /boot/initrd.img-2.4.27-2-386 > savedefault > boot -- Chris. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Yes , I am running Sarge . I got the point . Thank you very much . Hotmail: Powerful Free email with security by Microsoft. Get it now. _ Hotmail: Trusted email with powerful SPAM protection. https://signup.live.com/signup.aspx?id=60969
Re: Grub boot loader?
On Tue, Feb 02, 2010 at 06:15:12AM +, hadi motamedi wrote: The answer is easier to read and follow if you type it directly under the question. Also, removing old text helps as well. > On Mon, Feb 1, 2010 at 2:24 PM, Chris Bannister < > mockingb...@earthlight.co.nz> wrote: [snip] > - How can I check if it is running splashy ? I don't know - I've never run it or even looked at it, but apt-cache policy splashy might help. > - No , I don't want to make these changes permanent . I want to change them > for that one reboot . So I want to touch grub edit menu. OK. > - Please find below the output of grep -v '^#' /boot/grub/menu.lst : > title Debian GNU/Linux,kernel 2.4.27-2-386 That is a really old kernel. Are you running Sarge? > root (hd0,0) > kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hda1 ro > initrd /boot/initrd.img-2.4.27-2-386 > savedefault > boot > titleDebian GNU/Linux , kernel 2.4.27-2-386 (recovery mode) > root(hd0,0) > kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hda1 ro single Look! You already have a single user mode. > initrd /boot/initrd.img-2.4.27-2-386 > savedefault > boot -- Chris. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Grub boot loader?
On Mon, Feb 1, 2010 at 2:24 PM, Chris Bannister < mockingb...@earthlight.co.nz> wrote: > On Mon, Feb 01, 2010 at 12:46:36PM +, hadi motamedi wrote: > > Thank you for your reply . > > - Yes , my computer boots to a login prompt . > > Good. Then DON"T mess with grub-install. > > > - When I press the 'e' key , nothing happens and after the timer expiry > the > > boot process will begin automatically . So I don't have chance to edit my > > boot kernel . > > - I don't see the grub menu . I just see the Debian logo and a timer that > > counts down automatically . > > Ahhh, that might be the reason. You running splashy? > > > - I want to be able to edit the menu say putting it into single user mode > by > > adding 'single' at the end of the line , etc. > > I presume you want to make this change permanent. The only way to do > that is by editing /boot/grub/menu.lst and running update-grub. > > You did run 'update-grub', didn't you? > > Editing the menu by pressing the 'e' key does not write any thing to > menu.lst - it only allows you to change 'things' for that one boot. The > changes are lost after that. > > But if you can't see the menu when you boot, how can you select "single > user" mode anyway? > > But you should already have a single user mode if you ran update-grub. > > What is output of: > > grep -v '^#' /boot/grub/menu.lst > > -- > Chris. > -- > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > > Thank you for your message . - So I won't try for 'grub-install' . - How can I check if it is running splashy ? - No , I don't want to make these changes permanent . I want to change them for that one reboot . So I want to touch grub edit menu. - Please find below the output of grep -v '^#' /boot/grub/menu.lst : title Debian GNU/Linux,kernel 2.4.27-2-386 root (hd0,0) kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hda1 ro initrd /boot/initrd.img-2.4.27-2-386 savedefault boot titleDebian GNU/Linux , kernel 2.4.27-2-386 (recovery mode) root(hd0,0) kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hda1 ro single initrd /boot/initrd.img-2.4.27-2-386 savedefault boot Thank you
Re: Grub boot loader?
On Tue, 2 Feb 2010 02:22:11 +1300 Chris Bannister wrote: > On Mon, Feb 01, 2010 at 08:27:54AM +, hadi motamedi wrote: > > Thank you for your message . So you mean I can make use of it to activate my > > grub edit w/o any problem? > > That all depends on what your problem is that you are trying to solve. > > Is your computer booting to a login prompt? > > Pressing the 'e' key *should* alow you to edit the menu entry. What > happens when you press 'e'? > > Are you seeing the menu? If not what are you seeing? I have no idea if this is relevant to the OP's problem, but in any event, for the archives: I once was terribly frustrated by the failure of the grub keys (b, e, p) to do what they were supposed to do. I eventually realized the problem: I use a dvorak keymap, both in the console and in X, but grub was using qwerty ... [A quick Google^WYahoo finds this way to get grub to use dvorak: http://bobbens.dyndns.org/files/grub-dvorak.lst] Celejar -- foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Grub boot loader?
On Mon, Feb 01, 2010 at 12:46:36PM +, hadi motamedi wrote: > Thank you for your reply . > - Yes , my computer boots to a login prompt . Good. Then DON"T mess with grub-install. > - When I press the 'e' key , nothing happens and after the timer expiry the > boot process will begin automatically . So I don't have chance to edit my > boot kernel . > - I don't see the grub menu . I just see the Debian logo and a timer that > counts down automatically . Ahhh, that might be the reason. You running splashy? > - I want to be able to edit the menu say putting it into single user mode by > adding 'single' at the end of the line , etc. I presume you want to make this change permanent. The only way to do that is by editing /boot/grub/menu.lst and running update-grub. You did run 'update-grub', didn't you? Editing the menu by pressing the 'e' key does not write any thing to menu.lst - it only allows you to change 'things' for that one boot. The changes are lost after that. But if you can't see the menu when you boot, how can you select "single user" mode anyway? But you should already have a single user mode if you ran update-grub. What is output of: grep -v '^#' /boot/grub/menu.lst -- Chris. -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Grub boot loader?
On Mon, Feb 1, 2010 at 1:22 PM, Chris Bannister < mockingb...@earthlight.co.nz> wrote: > On Mon, Feb 01, 2010 at 08:27:54AM +, hadi motamedi wrote: > > Thank you for your message . So you mean I can make use of it to activate > my > > grub edit w/o any problem? > > That all depends on what your problem is that you are trying to solve. > > Is your computer booting to a login prompt? > > Pressing the 'e' key *should* alow you to edit the menu entry. What > happens when you press 'e'? > > Are you seeing the menu? If not what are you seeing? > > Why do you want to edit the menu? > > You'll need to provide more information if you want help. > > Please, respond only to the list. I don't need two copies. > > -- > Chris. > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > > Thank you for your reply . - Yes , my computer boots to a login prompt . - When I press the 'e' key , nothing happens and after the timer expiry the boot process will begin automatically . So I don't have chance to edit my boot kernel . - I don't see the grub menu . I just see the Debian logo and a timer that counts down automatically . - I want to be able to edit the menu say putting it into single user mode by adding 'single' at the end of the line , etc.
Re: Grub boot loader?
On Mon, Feb 01, 2010 at 08:27:54AM +, hadi motamedi wrote: > Thank you for your message . So you mean I can make use of it to activate my > grub edit w/o any problem? That all depends on what your problem is that you are trying to solve. Is your computer booting to a login prompt? Pressing the 'e' key *should* alow you to edit the menu entry. What happens when you press 'e'? Are you seeing the menu? If not what are you seeing? Why do you want to edit the menu? You'll need to provide more information if you want help. Please, respond only to the list. I don't need two copies. -- Chris. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Grub boot loader?
On Mon, Feb 1, 2010 at 8:09 AM, Rico Secada wrote: > On Mon, 1 Feb 2010 07:59:44 + > hadi motamedi wrote: > > > Dear All > > On my Debian server , the '/boot/grub/menu.lst' has the right > > configuration but when I reboot my Debian server I cannot enter to > > grub edit menu to edit my boot kernel by pressing the 'e' key . Can > > you please confirm if I can activate it through issuing the > > followings : > > #grub-install /dev/hdax > > Is it a safe procedure to try with? Please confirm. > > Than you > > "grub-install copies GRUB images into the DIR/boot directory specfied > by --root-directory, and uses the grub shell to install grub into the > boot sector." > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > > Thank you for your message . So you mean I can make use of it to activate my grub edit w/o any problem?
Re: Grub boot loader?
On Mon, 1 Feb 2010 07:59:44 + hadi motamedi wrote: > Dear All > On my Debian server , the '/boot/grub/menu.lst' has the right > configuration but when I reboot my Debian server I cannot enter to > grub edit menu to edit my boot kernel by pressing the 'e' key . Can > you please confirm if I can activate it through issuing the > followings : > #grub-install /dev/hdax > Is it a safe procedure to try with? Please confirm. > Than you "grub-install copies GRUB images into the DIR/boot directory specfied by --root-directory, and uses the grub shell to install grub into the boot sector." -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Grub boot loader?
Dear All On my Debian server , the '/boot/grub/menu.lst' has the right configuration but when I reboot my Debian server I cannot enter to grub edit menu to edit my boot kernel by pressing the 'e' key . Can you please confirm if I can activate it through issuing the followings : #grub-install /dev/hdax Is it a safe procedure to try with? Please confirm. Than you
Re: Booting into Lenny from Etch (was: Problems installing Lenny's Grub boot loader to a partition)
On Mon,01.Jun.09, 22:19:55, Rodolfo Medina wrote: > To say it more simply, the problem is that I can't boot into my Lenny > partition > from my Etch partition, whose Grub boot loader is installed to the mbr. Did you add an entry for Lenny in the menu.lst of Etch? If you have grub installed on the Lenny partition you can chainload grub from the grub in MBR. Maybe you should post the relevant snippets of both menu.lst, your partition layout and where grub is installed. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: Booting into Lenny from Etch (was: Problems installing Lenny's Grub boot loader to a partition)
Rodolfo Medina writes: > On my PC I have many different partitions. With Etch, I've never had > problems installing the Grub boot loader to a partition at my pleasure and > not to the master boot record. > > Today I installed Lenny for the first time, from a DVD set bought from an > official Debian vendor, and: if I install the Grub boot loader to the mbr, > everything seems all right; instead, if I install the Grub boot loader to a > partition, then I can't boot into the system and get an > > Error 2: Bad file or directory type > > Did anyone experience the same problem, why does it occur and how to solve > it? To say it more simply, the problem is that I can't boot into my Lenny partition from my Etch partition, whose Grub boot loader is installed to the mbr. Rodolfo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Problems installing Lenny's Grub boot loader to a partition
On my PC I have many different partitions. With Etch, I've never had problems installing the Grub boot loader to a partition at my pleasure and not to the master boot record. Today I installed Lenny for the first time, from a DVD set bought from an official Debian vendor, and: if I install the Grub boot loader to the mbr, everything seems all right; instead, if I install the Grub boot loader to a partition, then I can't boot into the system and get an Error 2: Bad file or directory type Did anyone experience the same problem, why does it occur and how to solve it? Thanks for any help Rodolfo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
D-Installer: GRUB fails to install boot loader
Hello, i am trying to perform a network install with Debian Installer, which is failing when installing the GRUB loader with "Unable to install GRUB in (hd0)" Executing 'grub-install (hd0)' failed. and in the console i see: Cannot find a GRUB drive for /dev/sdq2. Check our device.map. error: Running 'grub-install --no-floppy --recheck "(hd0)"' failed. The problematic system: IBM woodcrest blade with Intel 5000P chipset, "LSI Logic/Sym bios Logic SAS1064ET PCI-Express-MPT SAS" SCSI controller, Qlogic ISP2422-based 4Gb FC adapter with several SAN Luns attached (that why the local disk appears as /dev/sdq...) The partition table: cat /proc/partitions major minor #blocks name (... ram0 to ram15 here...) 65 0 71687000 sdq 65 1 8474256 sdq1 (swap) 65 2 6000277 sdq2 (/ ) 65 3 57207465 sdq3 (unmounted) I also tried to run grub-install by hand from the rescue/debug shell, # grub-installer '(hd0)' Wrong number of args: mapdevfs The same error happens when trying with any other hd number (including (hd15), (hd16) etc) and with the --recheck options. I tried to intercept and log into a file the parameters mapdevfs is getting but i also don't get any. Lilo DID install without problems on the MBR. Where could be the problem? I couldn't find anything relevant after a lot of searching in google and in the debian lists. Thanks for any tip! (PS: Please CC me directly as i am currently not subscribed.) Ariel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot loader/ installer
On Tue, Oct 23, 2007 at 11:17:46AM -0700, Andrew Sackville-West wrote:
> On Tue, Oct 23, 2007 at 01:27:08PM -0400, Ryan Jones wrote:
> > I recently tried to install Debian on my system but while i was installing
> > it I ran across some problems unrelated to your program and had to do a
> > system restore before i was able to install Linux.
>
> what method were you using to install? It sounds like you were using
> www.goodbye-microsoft.{org,com}
>
> > Now when i start up i am
> > given the option to start windows or the installer. But I am unable to
> > use the installer because system restore has gotten rid of the file nor have
> > i found a way to get rid of it. I am using Windows Vista on a HP pavilion
> > tx1000 tablet notebook with an amd64 processor.
>
> so do you want to install debian or not? if you do, then you need to
> re-download the installer file. If not, you merely need to clean up
> your boot loader. I can't remember exactly what the file is called,
> but there is a file windows uses for booting multiple OS's and you
> merely have to delete the entries for the debian installer.
>
> A
boot.ini and it's located in the root of the first partition.
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
signature.asc
Description: Digital signature
Re: boot loader/ installer
On Tue, Oct 23, 2007 at 01:27:08PM -0400, Ryan Jones wrote:
> I recently tried to install Debian on my system but while i was installing
> it I ran across some problems unrelated to your program and had to do a
> system restore before i was able to install Linux.
what method were you using to install? It sounds like you were using
www.goodbye-microsoft.{org,com}
> Now when i start up i am
> given the option to start windows or the installer. But I am unable to
> use the installer because system restore has gotten rid of the file nor have
> i found a way to get rid of it. I am using Windows Vista on a HP pavilion
> tx1000 tablet notebook with an amd64 processor.
so do you want to install debian or not? if you do, then you need to
re-download the installer file. If not, you merely need to clean up
your boot loader. I can't remember exactly what the file is called,
but there is a file windows uses for booting multiple OS's and you
merely have to delete the entries for the debian installer.
A
signature.asc
Description: Digital signature
boot loader/ installer
I recently tried to install Debian on my system but while i was installing it I ran across some problems unrelated to your program and had to do a system restore before i was able to install Linux. Now when i start up i am given the option to start windows or the installer. But I am unable to use the installer because system restore has gotten rid of the file nor have i found a way to get rid of it. I am using Windows Vista on a HP pavilion tx1000 tablet notebook with an amd64 processor. Thank you for your help, -Ryan Jones-
Re: Boot loader option
在 2005-10-31一的 05:03 +0200，Mark Panen写道： > Hi > > I have installed sarge before but i forget now, is there an option to > choose between installing grub to the MBR and to the /root ? I would > not like to install to MBR. Try install sarge in expert mode. See help after boot from CD. Press F1~F12.
Boot loader option
Hi I have installed sarge before but i forget now, is there an option to choose between installing grub to the MBR and to the /root ? I would not like to install to MBR.
Re: irq redundancies in boot loader message
On Wed, Sep 01, 2004 at 11:55:27AM -0700, God bless us all, everyone. wrote: > Please CC me as I am unsubscribed. > The boot loader reports: > ttyS00 at 0x03f8 irq=4 is at 16550A > ttyS01 at 0x02f8 irq=3 is at 16550A > ttyS02 at 0x03e8 irq=4 is at 16550A > The modem (which has failed all attempts to dial) USR Sportster, ?56K, > WAS indeed on COM3 (ttyS2) and irq4 before I observed this message and > set irq2 with the physical jumper. Rebooting did not avail, and > rescue.bin made the identical report, in fact, and preempted my full > reinstallation. ttyS02 remains irq4. Is there an idea I may try? > setserial /dev/ttyS2 irq4 -- If quizzes are quizzical, what are tests? (Think about it) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
irq redundancies in boot loader message
Please CC me as I am unsubscribed. The boot loader reports:ttyS00 at 0x03f8 irq=4 is at 16550AttyS01 at 0x02f8 irq=3 is at 16550AttyS02 at 0x03e8 irq=4 is at 16550A The modem (which has failed all attempts to dial) USR Sportster, ?56K, WAS indeed on COM3 (ttyS2) and irq4 before I observed this message and set irq2 with the physical jumper. Rebooting did not avail, and rescue.bin made the identical report,in fact, and preempted my full reinstallation. ttyS02 remains irq4. Is there an idea I may try? Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! Enter now.
Re: Is Grub going to be official Sarge boot loader?
On Wed, 17 Mar 2004 14:30:15 +0100, Roberto Sanchez wrote: > Raiz-mpx wrote: >> After reading Debian Weekly News for March 16th, it mentions that; >> "This release features the new partitioner that supports automatic >> partitioning and LVM and uses [43]grub as boot-loader on i386." >> >> So does this means that my favorite boot loader will be the official >> Debian boot loader instead of Lilo? >> >> I know its not really that big of deal, as anyone can apt-get Lilo, >> but might save users a little bit of headache due to the boot loader >> issues. >> >> Rthoreau >> >> > > What I want to know is when dpkg/apt will support grub. I > roll my own kernels, and (naturally) use dpkg to install them. > I like how dpkg automatically updates the symlinks and runs lilo. > One of the reasons I have resisted installing grub is the lack > of automated support. Does anyone know for sure? > > -Roberto [EMAIL PROTECTED] ~]% cat /etc/kernel-img.conf # Do not create symbolic links in / postinst_hook = /sbin/update-grub postrm_hook = /sbin/update-grub do_bootloader = no do_symlinks = no do_initrd = Yes There. Now dpkg/apt supports grub (and not Lilo). -- I usually have a GPG digital signature included as an attachment. See http://www.gnupg.org/ for info about these digital signatures. My key was last signed 10/14/2003. If you use GPG *please* see me about signing the key. * My computer can't give you viruses by email. *** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Is Grub going to be official Sarge boot loader?
On Wed, Mar 17, 2004 at 11:27:19AM -0500, H. S. wrote: > Gokul Poduval wrote: > > Looks like grub is going to be the default. The beta 3 releast notes > >of the debian installer says > > > >The Debian Installer team is once again ready to announce a beta release > >of the Debian sarge installer. New features in beta 3 include: > > > > - new easy to use partitioner that supports automatic partitioning and > >LVM > > - *grub as the default boot loader on i386* > >and so on... > > > er ... it is too hard to ask the installer "Which bootloader would you > like to user: > " > > ? Boot with DEBCONF_PRIORITY=medium (or drop the priority with the menu item, if you see it), and I believe you can then choose. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Is Grub going to be official Sarge boot loader?
Gokul Poduval wrote: Hello, Looks like grub is going to be the default. The beta 3 releast notes of the debian installer says The Debian Installer team is once again ready to announce a beta release of the Debian sarge installer. New features in beta 3 include: - new easy to use partitioner that supports automatic partitioning and LVM - *grub as the default boot loader on i386* and so on... er ... it is too hard to ask the installer "Which bootloader would you like to user: " ? This way both camps will be happy. I am happy with grub though, I use Grub in Fedora, and whenever I reinstall Debian (for whatever reason) and if it is also using Grub I face no problems at all. ->HS -- (Remove all underscores from my email address to get the correct one. Apologies for the inconvenience, but this is to reduce spam.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Is Grub going to be official Sarge boot loader?
Sridhar M.A. wrote: On Wed, Mar 17, 2004 at 08:41:33AM -0500, Richard Hoskins wrote: > Roberto Sanchez <[EMAIL PROTECTED]> writes: > > > What I want to know is when dpkg/apt will support grub. I roll my > > own kernels, and (naturally) use dpkg to install them. I like how > > dpkg automatically updates the symlinks and runs lilo. One of the > > reasons I have resisted installing grub is the lack of automated > > support. Does anyone know for sure? > > With grub there are no symlinks to update and such. The menu file has > to be updated, but that is done with update-grub, so there is not a > lot left to automate. Just run update-grub after installing your new > kernel, and you should be all right. (Check the menu file before > rebooting, of course.) > If the menu entry points to /vmlinuz, you do not have to check anything. Everytime a kernel image is installed via dpkg, /vmlinuz is linked to the latest kernel image in /boot. So, with grub one does not have to do anything. Regards, Yup. I just figured that out. GRUB is actually much simpler than I thought. -Roberto signature.asc Description: OpenPGP digital signature
Re: Is Grub going to be official Sarge boot loader?
On Wed, Mar 17, 2004 at 08:41:33AM -0500, Richard Hoskins wrote: > Roberto Sanchez <[EMAIL PROTECTED]> writes: > > > What I want to know is when dpkg/apt will support grub. I roll my > > own kernels, and (naturally) use dpkg to install them. I like how > > dpkg automatically updates the symlinks and runs lilo. One of the > > reasons I have resisted installing grub is the lack of automated > > support. Does anyone know for sure? > > With grub there are no symlinks to update and such. The menu file has > to be updated, but that is done with update-grub, so there is not a > lot left to automate. Just run update-grub after installing your new > kernel, and you should be all right. (Check the menu file before > rebooting, of course.) > If the menu entry points to /vmlinuz, you do not have to check anything. Everytime a kernel image is installed via dpkg, /vmlinuz is linked to the latest kernel image in /boot. So, with grub one does not have to do anything. Regards, -- Sridhar M.A. GPG KeyID : F6A35935 Fingerprint: D172 22C4 7CDC D9CD 62B5 55C1 2A69 D5D8 F6A3 5935 Things fall apart; the centre cannot hold. signature.asc Description: Digital signature
Re: Is Grub going to be official Sarge boot loader?
Roberto Sanchez <[EMAIL PROTECTED]> writes: > What I want to know is when dpkg/apt will support grub. I roll my > own kernels, and (naturally) use dpkg to install them. I like how > dpkg automatically updates the symlinks and runs lilo. One of the > reasons I have resisted installing grub is the lack of automated > support. Does anyone know for sure? With grub there are no symlinks to update and such. The menu file has to be updated, but that is done with update-grub, so there is not a lot left to automate. Just run update-grub after installing your new kernel, and you should be all right. (Check the menu file before rebooting, of course.) -- Lift me down, so I can make the Earth tremble. --Bucky Katt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Is Grub going to be official Sarge boot loader?
Hello Roberto! On Wed, Mar 17, 2004 at 08:27:50AM -0500, Roberto Sanchez wrote: > What I want to know is when dpkg/apt will support grub. I > roll my own kernels, and (naturally) use dpkg to install them. > I like how dpkg automatically updates the symlinks and runs lilo. > One of the reasons I have resisted installing grub is the lack > of automated support. Does anyone know for sure? Grub is well supported, the same way as lilo. This is my /etc/kernel-img.conf: |do_symlinks = no |postinst_hook = /sbin/update-grub |postrm_hook = /sbin/update-grub |do_bootloader = no |do_bootfloppy = no Additionally see /usr/share/doc/grub/README.Debian.gz Cheers, Flo signature.asc Description: Digital signature
Re: Is Grub going to be official Sarge boot loader?
Raiz-mpx wrote: After reading Debian Weekly News for March 16th, it mentions that; "This release features the new partitioner that supports automatic partitioning and LVM and uses [43]grub as boot-loader on i386." So does this means that my favorite boot loader will be the official Debian boot loader instead of Lilo? I know its not really that big of deal, as anyone can apt-get Lilo, but might save users a little bit of headache due to the boot loader issues. Rthoreau What I want to know is when dpkg/apt will support grub. I roll my own kernels, and (naturally) use dpkg to install them. I like how dpkg automatically updates the symlinks and runs lilo. One of the reasons I have resisted installing grub is the lack of automated support. Does anyone know for sure? -Roberto signature.asc Description: OpenPGP digital signature
Re: Is Grub going to be official Sarge boot loader?
Hello, Looks like grub is going to be the default. The beta 3 releast notes of the debian installer says The Debian Installer team is once again ready to announce a beta release of the Debian sarge installer. New features in beta 3 include: - new easy to use partitioner that supports automatic partitioning and LVM - *grub as the default boot loader on i386* and so on... gokul Raiz-mpx wrote: After reading Debian Weekly News for March 16th, it mentions that; "This release features the new partitioner that supports automatic partitioning and LVM and uses [43]grub as boot-loader on i386." So does this means that my favorite boot loader will be the official Debian boot loader instead of Lilo? I know its not really that big of deal, as anyone can apt-get Lilo, but might save users a little bit of headache due to the boot loader issues. Rthoreau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Is Grub going to be official Sarge boot loader?
After reading Debian Weekly News for March 16th, it mentions that; "This release features the new partitioner that supports automatic partitioning and LVM and uses [43]grub as boot-loader on i386." So does this means that my favorite boot loader will be the official Debian boot loader instead of Lilo? I know its not really that big of deal, as anyone can apt-get Lilo, but might save users a little bit of headache due to the boot loader issues. Rthoreau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot loader question
On Sat, 2003-10-04 at 02:05, Jason Housewright wrote: > Greetings all. > > I am looking at possibly moving to Debian; I have a > question about the boot loader. I have used grub for > quite a while now. What is the default bl for Debian, > and if one is preferred over the other, is it > difficult to switch? Thanks in advance for any help > and/or for directing me to helpful sources. It will by default install Lilo. No bother. apt-get install grub Then "grub-install /dev/) Write a good /boot/grub/menu.lst Reboot. And after a successful boot" apt-get remove --purge lilo All done. -- greg, [EMAIL PROTECTED] REMEMBER ED CURRY! http://www.iwethey.org/ed_curry BUY WAR BONDS signature.asc Description: This is a digitally signed message part
Re: boot loader question
On Sat, 04 Oct 2003 08:30:15 +0200, Jason Housewright <[EMAIL PROTECTED]> wrote: > Greetings all. > > I am looking at possibly moving to Debian; I have a > question about the boot loader. I have used grub for > quite a while now. What is the default bl for Debian, > and if one is preferred over the other, is it > difficult to switch? Thanks in advance for any help > and/or for directing me to helpful sources. > As of 3.0r1 I believe it was still LILO, the key thing to remember is to run lilo after editing /etc/lilo.conf or modifying the partition table. Documention is extensive, but if the install doesn't set up windows, there is a fairly self explanatory example of how to set it up in the config file. I haven't gotten a handle on grub, but I've been using lilo for several years longer than grub has been around. Debian's lilo.conf contains more comments than you'll need to tweak it however you want. I don't recall if grub is available when installing, if not, installing it after the fact is trivial anyway. Michael C. -- [EMAIL PROTECTED] http://mcsuper5.freeshell.org/ Registered Linux User #303915 http://counter.li.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot loader question
On (03/10/03 23:05), Jason Housewright wrote: > Greetings all. > > I am looking at possibly moving to Debian; I have a > question about the boot loader. I have used grub for > quite a while now. What is the default bl for Debian, > and if one is preferred over the other, is it > difficult to switch? Thanks in advance for any help > and/or for directing me to helpful sources. > Lilo is the default boot loader but Grub is preferred by many. We use Lilo for servers that only use Debian and Grub for multiboot Pc's. For my Mac G4 I use Yaboot. HTH Clive -- http://www.clivemenzies.co.uk strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot loader question
Debian doesn't lock you to any one boot loader. You can apt-get lilo or apt-get grub and you'll have the one of your choice! Naitik. On Fri, 3 Oct 2003 23:05:10 -0700 (PDT) Jason Housewright <[EMAIL PROTECTED]> wrote: > Greetings all. > > I am looking at possibly moving to Debian; I have a > question about the boot loader. I have used grub for > quite a while now. What is the default bl for Debian, > and if one is preferred over the other, is it > difficult to switch? Thanks in advance for any help > and/or for directing me to helpful sources. > > J. Brad > > __ > Do you Yahoo!? > The New Yahoo! Shopping - with improved product search > http://shopping.yahoo.com > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
boot loader question
Greetings all. I am looking at possibly moving to Debian; I have a question about the boot loader. I have used grub for quite a while now. What is the default bl for Debian, and if one is preferred over the other, is it difficult to switch? Thanks in advance for any help and/or for directing me to helpful sources. J. Brad __ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: minimal boot loader?
Jason Pepas wrote: > > hello, > > I have been reading through a bunch of howto's on creating floppy based linux > systems. The process of creating the floppy images strikes me as being way > too complicated. > > In short, is there a program which behaves like this? > > mkbootdisk --append="" kernel.img rootfs.img > > I haven't been able to find anything which takes a kernel image, a root > filesystem image, and a boot paramter string, and creates a 1 or 2 floppy > set, all in one command. > > This seems like it would be such a nice thing to have, I just can't beleive no > one has done this yet, so I though I'd ask here before I go off and write a > script which accomplishes the same thing. > > thanks, > jason pepas The Debian package of grub has something like that called 'mkbimage' (I haven't tried it). It uses grub as the bootloader, which you may or may not want to use Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
minimal boot loader?
hello, I have been reading through a bunch of howto's on creating floppy based linux systems. The process of creating the floppy images strikes me as being way too complicated. In short, is there a program which behaves like this? mkbootdisk --append="" kernel.img rootfs.img I haven't been able to find anything which takes a kernel image, a root filesystem image, and a boot paramter string, and creates a 1 or 2 floppy set, all in one command. This seems like it would be such a nice thing to have, I just can't beleive no one has done this yet, so I though I'd ask here before I go off and write a script which accomplishes the same thing. thanks, jason pepas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installing a New Boot Loader on a Software RAID
On Tue, 2003-03-04 at 12:13, Robert James Kaes wrote: > Hi, > Is it possible to change the boot loader on a software RAID system while > the system is running in multiuser mode? Currently the machine has LILO > installed, but I would like to switch it to grub. I believe that grub cannot boot software RAID devices. You'll have to put /boot on a non-RAID partition for grub to find it ... it's possible since I last looked grub can do this, if I'm wrong then I'd love to be corrected. -- Fraser Campbell <[EMAIL PROTECTED]>http://wehave.net/ Brampton, Ontario, CanadaDebian GNU/Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installing a New Boot Loader on a Software RAID
Robert James Kaes said: > Hi, > Is it possible to change the boot loader on a software RAID system while > the system is running in multiuser mode? Currently the machine has LILO > installed, but I would like to switch it to grub. I can't imagine why not, but you won't be able to test it without rebooting .. nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Installing a New Boot Loader on a Software RAID
Hi, Is it possible to change the boot loader on a software RAID system while the system is running in multiuser mode? Currently the machine has LILO installed, but I would like to switch it to grub. -- Robert -- -- Robert James Kaes--- Flarenet Inc. ---(519) 426-3782 http://www.flarenet.com/ * Putting the Service Back in Internet Service Provider * -- pgp0.pgp Description: PGP signature
Re: nature of a boot loader
Dai, Grub and LILO can both chainload to each other just like they can to a windows boot loader. You can have the other boot loader on another drive or at the beginning of a partition. I did just this to make things a little more pleasant to my wife, who is not hip to windows and finds some of the hackerish things I do to our computers confusing. I installed grub on my PC that initially gave a choice of "Windows" or "Linux", with Windows being the default. So that way she didn't have to touch the keyboard to get into the OS she's presently most comfortable with, and even if she does monkey with the menu, it's easy for her to deal with. Selecting "Linux" from the first grub menu would chain-load to a second copy of grub that was installed in the first sector of my linux root partition, which would then allow me to select the kernel to use. I would often experiment with different kernels, some of which wouldn't work out all that well, but I could leave them in the second Grub menu without disturbing my wife, thus achieving complete matrimonial harmony. The same basic setup would apply to LILO, and should you desire to for some reason, you could chain load from LILO to Grub, or Grub to LILO. You can also have the NT boot menu load Grub or LILO by installing first to a partition, and then copying the bootsector to a file in your Windows partition. Suppose /dev/hda2 is where you've installed Grub: dd if=/dev/hda2 of=grubboot.dat bs=512 count=1 then copy grubboot.dat to your Windows partition and add it to your NT or Win2k boot menu. This probably works on XP too, but I don't have XP. Yours, Michael D. Crawford GoingWare Inc. - Expert Software Development and Consulting. http://www.goingware.com/ [EMAIL PROTECTED] Tilting at Windmills for a Better Tomorrow. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nature of a boot loader
Bruce Park wrote: Dai, My understanding with booting an OS works like this. The BIOS must first be set to detect something. In my computer, I have it boot in this order. 1. floppy 2. cdrom 3. primary hard disk This is pretty much self explanatory. Now once floppy and cdrom fail, it'll load whatever is in the MBR. In my case, it's GRUB. GRUB has two loading stages 1 and 2. Stage 1 is nothing much and just loads stage 2 which is usually the GRUB menu. One a choice is made, the kernel and the root file system is mounted. By now, your OS should start loading appropriate things. Because of the nature of a boot loader, I don't think it can load another boot loader such as lilo or even GRUB thats a part of another disk. I'm only beginning to understand how all these things work. I could be totally wrong but this my understanding after reading documents online. But GRUB can chainload another boot loader on the same disk like this: titile DOS rootnoverify (hd0, 0) chainloader +1 My question is can GRUB load another boot loader on another disk? Now we can use GRUB to boot everything in both hard drives. The ONLY problem I can see with this is by showing you an example. Let's say I have two hard drivers, hd0 and hd1. GRUB will boot from MBR of the first hard drive. The original grub.conf or menu.lst lies in the hd0. If I go into hd1 and need to edit grub, now I have to mount hd0 then write the GRUB configuration. As far as I can see, it's really not much trouble at all but that's the ONLY thing that I can see where this becomes a problem. Yes. It's very easy to use GRUB. In fact I also have GRUB work this way. Let me know if this helps at all. I'm always happy to help linux users. bp Thank you very much. Dai yuwen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot loader problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 22 November 2002 11:23 pm, Rebecca Riall & Jeff Melton wrote: > > Thanks for writing. The documentation for Debian 2.2 actually does say > there's an "mbr" boot loader, although I'd never heard of it until I got > Debian. Nor had I, but I suspect that is what is causing your existing prompts. There is confusing terminology because MBR normally refers to the first block on a disk - in this case it is refering to the code that is loaded into the first block on the disk ... > Right now that line from lilo.conf says boot=/dev/hda. Maybe that's the > problem, since hda isn't the name of a partition? Should it say > boot=/dev/hda5, my root partition for Linux? NO - remember the terminology for lilo is confusing because the same name is used for two things. 1) The set of programs that load up during boot before handing control over to the operatating system just loaded. 2) The program that writes 1) to the hard disk based on the parameters in /etc/lilo.conf. what boot does is tell 2) where to install 1). In this case /dev/hda is the mbr of the first ide drive. Actually - you can tell lilo several different images to load once it is past the mbr stage. The following shows most of my lilo.conf (I get prompted with a menu of 4 operating systems (Linux, Linux in single user mode, and older version of linux as a backup in case of problems and Windows) to boot from and 5 secs to choose before the default (Linux) is loaded. I reckon if you set something like this (particularly the "other" stanza at the end) in to your /etc/lilo and run lilo you will get it dual boot. (You can make Windows the default if you would prefer. # Support LBA for large hard disks. # lba32 # Specifies the device that should be mounted as root. (`/') # root=/dev/hda3 # Installs the specified file as the new boot sector # You have the choice between: bmp, compat, menu and text # Look in /boot/ and in lilo.conf(5) manpage for details # install=/boot/boot-menu.b # Specifies the location of the map file # map=/boot/map # Specifies the number of deciseconds (0.1 seconds) LILO should # wait before booting the first image. # delay=20 #prompt with menu prompts from above with 5 sec timeout prompt timeout=50 # Specifies the VGA text mode at boot time. (normal, extended, ask, ) vga=normal default=Linux image=/vmlinuz label=Linux initrd=/initrd.img read-only image=/vmlinuz label=single initrd=/initrd.img read-only append=single image=/vmlinuz.old initrd=/initrd.img.old label=old read-only optional # If you have another OS on this machine to boot, you can uncomment the # following lines, changing the device name on the `other' line to # where your other OS' partition is. other=/dev/hda1 label="Windows" - -- Alan Chandler [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE93smruFHxcV2FFoIRAg86AKCDTRv4GxBmdYeCT/Ae/IS7a9O0GACff+xh WdQX+2OBausJbVW28KBPbh0= =JMcQ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot loader problem
On Fri, 22 Nov 2002, Seneca wrote: > On Fri, Nov 22, 2002 at 10:52:06AM -0500, Rebecca Riall & Jeff Melton wrote: > > Recently I tried to install Debian 2.2 on a system with Win98 (recently I > > had Red Hat 7.2 but got tired of some of the glitches). Never was able to > > get it successfully up and running, and decided to go with Mandrake 9.0 > > for the time being. For now, Mandrake is there and Debian is gone. > > > > My problem is that ever since the Debian installation attempt, during > > which I installed the "mbr" boot loader, I have been unable to boot > > properly into Windows or my now successfully installed Mandrake OS without > > using the Win98 CD. If I don't do this, I get a prompt that says > > "MBR1234FA:" or more recently "MBR1FA:" and the computer stalls at that > > point. > > Your computer stalls because it is waiting for your input. An exerpt > from /usr/share/doc/mbr/README: > 4.1 The boot prompt > ~~~ > The boot prompt looks something like this: > 14FA: > > This is the list of valid keys which may be pressed. This means that > partitions 1, and 4 can be booted, also the first floppy drive > (F). The A means that 'advanced' mode may be entered, in which any > partition may be booted. The prompt for this mode looks like this: > 1234F: > The only other valid key which may be pressed is RETURN, which > continues booting with the default partition Thanks for writing. The documentation for Debian 2.2 actually does say there's an "mbr" boot loader, although I'd never heard of it until I got Debian. Anyway, the problem I'm having is that neither pressing enter nor pressing any of the other listed keys results in the system booting. This prompt is a leftover from when I had Debian (sort of) installed, apparently. > > Something seems to be stuck in my boot sector from the Debian > > install attempt that won't go away. I tried various things to fix the > > situation, including using fdisk/mbr from DOS to install the default > > Windows boot record. Nothing has worked so far. I tried re-installing > > Debian in hopes of changing the boot loader, but it seemed to want to > > install on top of my Mandrake partitions and didn't give me the option of > > installing it elsewhere. Am I stuck with starting boots from the CD > > forever, or is there a solution? > > Back in January, the MBR prompt kept coming up every time I booted the > system (logical partitions can be fun to boot from) and I got rid of it > by changing one line of my lilo.conf (I think it was the "boot=" line), > then rerunning LILO. Even if the prompt never stops coming up, you don't > need to use the CD. Instead, enter in the partition that you want to > boot from. There is also an article about clearing out the MBR in issue > 63 of the Linux Gazette. Right now that line from lilo.conf says boot=/dev/hda. Maybe that's the problem, since hda isn't the name of a partition? Should it say boot=/dev/hda5, my root partition for Linux? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot loader problem
On Fri, Nov 22, 2002 at 10:52:06AM -0500, Rebecca Riall & Jeff Melton wrote: > Recently I tried to install Debian 2.2 on a system with Win98 (recently I > had Red Hat 7.2 but got tired of some of the glitches). Never was able to > get it successfully up and running, and decided to go with Mandrake 9.0 > for the time being. For now, Mandrake is there and Debian is gone. > > My problem is that ever since the Debian installation attempt, during > which I installed the "mbr" boot loader, I have been unable to boot mbr is _not_ a boot loader. It is a MBR (Master Boot Record) to replace the non-free MS-DOS MBR. LILO is a boot loader. > properly into Windows or my now successfully installed Mandrake OS without > using the Win98 CD. If I don't do this, I get a prompt that says > "MBR1234FA:" or more recently "MBR1FA:" and the computer stalls at that > point. Your computer stalls because it is waiting for your input. An exerpt from /usr/share/doc/mbr/README: 4.1 The boot prompt ~~~ The boot prompt looks something like this: 14FA: This is the list of valid keys which may be pressed. This means that partitions 1, and 4 can be booted, also the first floppy drive (F). The A means that 'advanced' mode may be entered, in which any partition may be booted. The prompt for this mode looks like this: 1234F: The only other valid key which may be pressed is RETURN, which continues booting with the default partition > Something seems to be stuck in my boot sector from the Debian > install attempt that won't go away. I tried various things to fix the > situation, including using fdisk/mbr from DOS to install the default > Windows boot record. Nothing has worked so far. I tried re-installing > Debian in hopes of changing the boot loader, but it seemed to want to > install on top of my Mandrake partitions and didn't give me the option of > installing it elsewhere. Am I stuck with starting boots from the CD > forever, or is there a solution? Back in January, the MBR prompt kept coming up every time I booted the system (logical partitions can be fun to boot from) and I got rid of it by changing one line of my lilo.conf (I think it was the "boot=" line), then rerunning LILO. Even if the prompt never stops coming up, you don't need to use the CD. Instead, enter in the partition that you want to boot from. There is also an article about clearing out the MBR in issue 63 of the Linux Gazette. > P.S. I'm not quite a newbie, but close (have been using Linux for about a > year), so please keep it simple! About a year? I started with Linux (Debian is my first, and currently only, distro) on December 2 last year. -- Seneca [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
boot loader problem
Recently I tried to install Debian 2.2 on a system with Win98 (recently I had Red Hat 7.2 but got tired of some of the glitches). Never was able to get it successfully up and running, and decided to go with Mandrake 9.0 for the time being. For now, Mandrake is there and Debian is gone. My problem is that ever since the Debian installation attempt, during which I installed the "mbr" boot loader, I have been unable to boot properly into Windows or my now successfully installed Mandrake OS without using the Win98 CD. If I don't do this, I get a prompt that says "MBR1234FA:" or more recently "MBR1FA:" and the computer stalls at that point. Something seems to be stuck in my boot sector from the Debian install attempt that won't go away. I tried various things to fix the situation, including using fdisk/mbr from DOS to install the default Windows boot record. Nothing has worked so far. I tried re-installing Debian in hopes of changing the boot loader, but it seemed to want to install on top of my Mandrake partitions and didn't give me the option of installing it elsewhere. Am I stuck with starting boots from the CD forever, or is there a solution? Thanks! Jeff Melton P.S. I'm not quite a newbie, but close (have been using Linux for about a year), so please keep it simple! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dual boot win2k as boot loader
Well the problem ended up being that the hard disk had a bad sector right in the area of the /boot partition (before the 1024K) point. So there for lilo was spitting out all those 01 01 01 01. Using Loadlin from with in win2k sounds also like a pretty good idea once the HD gets replaced. Leave it to MS to make a rule that says you can't use their boot loader to load non MS software. Donald R. Spoon wrote: > Barney Wrightson wrote: > >> Quenten Griffith wrote: >> >>> Well that is good to know that lilo can and backs up the org. MBR, >>> but basically there seems no way to boot Debian with the WIN2k Boot >>> loader. I don't have a problem with that but my friend may be leary. >>> >> >> I believe it is actually possible to get the W2K boot loader to boot >> other OSs like linux and solaris x86, but I haven't done it myself. >> You would probably need lilo installed on the linux boot partition >> rather than in MBR and then modify the c:\boot.ini in W2K to point to >> your linux install. You will need to google for the details though. >> >> Be warned though, I believe it contravenes the MS EULA to boot any >> non-MS OS using their boot loader. (as if that would stop people dual >> booting, actually it seems more like a challenge to me :)) >> >> HTH >> Barney. >> >> > > I don't have Win2K here, so this is speculation at best, BUT I recall > a very nice "Mini HOWTO" on using the WinNT bootloader to boot linux. > Maybe M$ hasn't changed how their boot-loader works since NT?? The > mini-HOWTO can be found at the LDP at: > http://www.tldp.org/HOWTO/mini/Linux+NT-Loader.html#toc6. Maybe you > can get some ideas there. > > Incidently, I have an old DEC Alpha XLT-300 that was primarily made to > run WinNT. I have Debian Woody running on it, and the boot-up schema > is quite unique. Basically it uses the boot-loader to call > loadlin.exe which then runs the kernel. (It is a little more > complicated than that ). If you can boot Linux from within > Win2K using loadlin.exe, then you "should" be able to automate this > with the bootloader. > > As a last resort, booting from within Win2K using loadlin.exe seems to > also "fit the bill" for your friend. It might be a bit tedious to > first boot into Win2k then run the linload script, but he would have > the comfort of knowing Win2K still boots!! > > Cheers, > -Don Spoon- > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dual boot win2k as boot loader
Hi No, that's right. Lilo won't owerwrite win2k's mbr. I'm not sure exacly how this works, but it's working:) I'm workin dayly with several pc's with dualboot win2k/debian, and I have done this several times, last time today on my own ibm-x20 laptop. I'm working with support on both windoze and debian and need to keep both system's on all my pc's, even if Debian is my primary OS:) I can see from the list that there is several way's to to this, but I think this method is the easyest, and it has never faild. It's not nessesary to use win98 startupdisk either, as long as there is fdisk on the floppy(or bootable cd), your ok. /ernst On Wed, 4 Sep 2002, Quenten Griffith wrote: > So lilo won't overwrite Win2k's mbr and just doing an fdisk/ mbr will > restore the orginal boot loader? Hmmm I was always told that once lilo > took control of that machine then thats it you can't get win2k boot > loader back with our reinstalling, but I have nevr tired it. This may > work then. > > ernst wrote: > > >Hi > >I would just install debian, and configure lilo in MBR on hda. That would > >not destroy windoze bootloader, just take controll over it:) > > > >If you later want's to remove debian and lilo, you can just boot up with a > >win98 boot/startupdisk and run "fdisk /mbr". > >That's it. > > > >Good Luck > > > >/ernst > > > > > >On Wed, 4 Sep 2002, Quenten Griffith wrote: > > > > > > > >>Hello all I am setting up a dual boot machine for a friend of mine who > >>wants to give Linux a go, he has to 20 gig hard drives hda being where > >>win2k resides, and hdb is broken up to two 10 gig partions. hdb1 being > >>swap hdb3 being / on the first 9gig. The other 10gig is fat32 for > >>storage space in windows. He does not want to lose the win2k boot > >>loader just in case he doesn't like linux, that way he can remove linux > >>with out messing up his MBR on hda. So I installed Debian and told Lilo > >>to go on hdb3 and to write a MBR to hdb then I boot into it with the > >>boot floppy and do a dd if=/devhdb of=/tmp/debian.bin bs=512 count=1 and > >>then I take the .bin file and boot into windows and place it in the c:\ > >>and edit boot.ini accordinly. After that I boot up and select debian > >>and I get a black screen with MBR=FA3 or something along that lines and > >>I can't do anything. So I then tried the same dd statement but used > >>/dev/hdb3 and I get a screen full of 0 and 1's when I try to boot of > >>that bin. Do I need to make a sepreate boot partition on /dev/hdb for > >>Debian and then do the dd statment with the boot partion? I want ot > >>make sure I get it right next time so that he won't give up on Linux. > >> Thanks all. > >> > >> > >>-- > >>To UNSUBSCRIBE, email to [EMAIL PROTECTED] > >>with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >> > >> > >> > > > > > > > > > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dual boot win2k as boot loader
Barney Wrightson wrote: > Quenten Griffith wrote: > >> Well that is good to know that lilo can and backs up the org. MBR, but >> basically there seems no way to boot Debian with the WIN2k Boot >> loader. I don't have a problem with that but my friend may be leary. >> > > I believe it is actually possible to get the W2K boot loader to boot > other OSs like linux and solaris x86, but I haven't done it myself. You > would probably need lilo installed on the linux boot partition rather > than in MBR and then modify the c:\boot.ini in W2K to point to your > linux install. You will need to google for the details though. > > Be warned though, I believe it contravenes the MS EULA to boot any > non-MS OS using their boot loader. (as if that would stop people dual > booting, actually it seems more like a challenge to me :)) > > HTH > Barney. > > I don't have Win2K here, so this is speculation at best, BUT I recall a very nice "Mini HOWTO" on using the WinNT bootloader to boot linux. Maybe M$ hasn't changed how their boot-loader works since NT?? The mini-HOWTO can be found at the LDP at: http://www.tldp.org/HOWTO/mini/Linux+NT-Loader.html#toc6. Maybe you can get some ideas there. Incidently, I have an old DEC Alpha XLT-300 that was primarily made to run WinNT. I have Debian Woody running on it, and the boot-up schema is quite unique. Basically it uses the boot-loader to call loadlin.exe which then runs the kernel. (It is a little more complicated than that ). If you can boot Linux from within Win2K using loadlin.exe, then you "should" be able to automate this with the bootloader. As a last resort, booting from within Win2K using loadlin.exe seems to also "fit the bill" for your friend. It might be a bit tedious to first boot into Win2k then run the linload script, but he would have the comfort of knowing Win2K still boots!! Cheers, -Don Spoon- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dual boot win2k as boot loader
Quenten Griffith wrote: > Well that is good to know that lilo can and backs up the org. MBR, but > basically there seems no way to boot Debian with the WIN2k Boot loader. > I don't have a problem with that but my friend may be leary. > I believe it is actually possible to get the W2K boot loader to boot other OSs like linux and solaris x86, but I haven't done it myself. You would probably need lilo installed on the linux boot partition rather than in MBR and then modify the c:\boot.ini in W2K to point to your linux install. You will need to google for the details though. Be warned though, I believe it contravenes the MS EULA to boot any non-MS OS using their boot loader. (as if that would stop people dual booting, actually it seems more like a challenge to me :)) HTH Barney. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dual boot win2k as boot loader
Ok I will try that tonight and see what happens tonight and report back and see if its just a funcationality that grub has. I like your other idea though of setting up a small boot partion on /dev/hda as well. That should work for sure as you said. Elimar Riesebieter wrote: >On Wed, 04 Sep 2002 the mental interface of Quenten Griffith told: > > > >>Is this a Lilo thing? I installed Gentoo on the same computer and it >>uses Grub, with the same exact setup, but it had a seprate /boot on the >>second drive. >> >> >Use grub for trial boot! > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dual boot win2k as boot loader
Hi, - Original Message - From: "Quenten Griffith" <[EMAIL PROTECTED]> To: "Søren Rydlund" <[EMAIL PROTECTED]> Sent: Wednesday, September 04, 2002 4:21 PM Subject: Re: dual boot win2k as boot loader > *This message was transferred with a trial version of CommuniGate(tm) Pro* > > What do you mean by save the mbr? I got a program called boot.exe, that can load and save mbr. Best Regards Soren Rydlund -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dual boot win2k as boot loader
On Wed, 04 Sep 2002 the mental interface of Quenten Griffith told: > Is this a Lilo thing? I installed Gentoo on the same computer and it > uses Grub, with the same exact setup, but it had a seprate /boot on the > second drive. Use grub for trial boot! -- The way to source is always uphill! -unknown- msg00674/pgp0.pgp Description: PGP signature
Re: dual boot win2k as boot loader
Is this a Lilo thing? I installed Gentoo on the same computer and it uses Grub, with the same exact setup, but it had a seprate /boot on the second drive. Elimar Riesebieter wrote: >On Wed, 04 Sep 2002 the mental interface of Quenten Griffith told: > > > >>Well that is good to know that lilo can and backs up the org. MBR, >>but basically there seems no way to boot Debian with the WIN2k >>Boot loader. I don't have a problem with that but my friend may >>be leary. >> >> >> >[...] > >Then you have to boot from the primary disk (hda)! Do a small >patition (i.e. 10 Mb) for /boot on hda. Install lilo in that and do >your dd stuff again. It'll work for shure! > >Ciao > >Elimar > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dual boot win2k as boot loader
On Wed, 04 Sep 2002 the mental interface of Quenten Griffith told: > Well that is good to know that lilo can and backs up the org. MBR, > but basically there seems no way to boot Debian with the WIN2k > Boot loader. I don't have a problem with that but my friend may > be leary. > [...] Then you have to boot from the primary disk (hda)! Do a small patition (i.e. 10 Mb) for /boot on hda. Install lilo in that and do your dd stuff again. It'll work for shure! Ciao Elimar -- Obviously the human brain works like a computer. Since there are no stupid computers humans can't be stupid. There are just a few running with Windows or even CE ;-) msg00668/pgp0.pgp Description: PGP signature
Re: dual boot win2k as boot loader
Well that is good to know that lilo can and backs up the org. MBR, but basically there seems no way to boot Debian with the WIN2k Boot loader. I don't have a problem with that but my friend may be leary. Elimar Riesebieter wrote: >Hi Gents, > >On Wed, 04 Sep 2002 the mental interface of ernst told: > > > >>Hi >>I would just install debian, and configure lilo in MBR on hda. That would >>not destroy windoze bootloader, just take controll over it:) >> >>If you later want's to remove debian and lilo, you can just boot up with a >>win98 boot/startupdisk and run "fdisk /mbr". >>That's it. >> >> > >Quenten is using W2K. There you have to boot the W2K CD in repair >modus and run fixmbr! > >A better way is to restore the mbr within debian. In /etc/boot there >is a boot.0300. This is the backup mbr written by lilo the first >time installing lilo in /dev/hda. Running lilo -u /dev/hda (in that >case) will restore the mbr of w2k. After that linux can only be >booted via fd or cd and w2k is using the the internal bootloader! > >[...] > >HTH > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dual boot win2k as boot loader
So lilo won't overwrite Win2k's mbr and just doing an fdisk/ mbr will restore the orginal boot loader? Hmmm I was always told that once lilo took control of that machine then thats it you can't get win2k boot loader back with our reinstalling, but I have nevr tired it. This may work then. ernst wrote: >Hi >I would just install debian, and configure lilo in MBR on hda. That would >not destroy windoze bootloader, just take controll over it:) > >If you later want's to remove debian and lilo, you can just boot up with a >win98 boot/startupdisk and run "fdisk /mbr". >That's it. > >Good Luck > >/ernst > > >On Wed, 4 Sep 2002, Quenten Griffith wrote: > > > >>Hello all I am setting up a dual boot machine for a friend of mine who >>wants to give Linux a go, he has to 20 gig hard drives hda being where >>win2k resides, and hdb is broken up to two 10 gig partions. hdb1 being >>swap hdb3 being / on the first 9gig. The other 10gig is fat32 for >>storage space in windows. He does not want to lose the win2k boot >>loader just in case he doesn't like linux, that way he can remove linux >>with out messing up his MBR on hda. So I installed Debian and told Lilo >>to go on hdb3 and to write a MBR to hdb then I boot into it with the >>boot floppy and do a dd if=/devhdb of=/tmp/debian.bin bs=512 count=1 and >>then I take the .bin file and boot into windows and place it in the c:\ >>and edit boot.ini accordinly. After that I boot up and select debian >>and I get a black screen with MBR=FA3 or something along that lines and >>I can't do anything. So I then tried the same dd statement but used >>/dev/hdb3 and I get a screen full of 0 and 1's when I try to boot of >>that bin. Do I need to make a sepreate boot partition on /dev/hdb for >>Debian and then do the dd statment with the boot partion? I want ot >>make sure I get it right next time so that he won't give up on Linux. >> Thanks all. >> >> >>-- >>To UNSUBSCRIBE, email to [EMAIL PROTECTED] >>with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >> >> >> > > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dual boot win2k as boot loader
Hi Gents, On Wed, 04 Sep 2002 the mental interface of ernst told: > Hi > I would just install debian, and configure lilo in MBR on hda. That would > not destroy windoze bootloader, just take controll over it:) > > If you later want's to remove debian and lilo, you can just boot up with a > win98 boot/startupdisk and run "fdisk /mbr". > That's it. Quenten is using W2K. There you have to boot the W2K CD in repair modus and run fixmbr! A better way is to restore the mbr within debian. In /etc/boot there is a boot.0300. This is the backup mbr written by lilo the first time installing lilo in /dev/hda. Running lilo -u /dev/hda (in that case) will restore the mbr of w2k. After that linux can only be booted via fd or cd and w2k is using the the internal bootloader! [...] HTH -- Alles was viel bedacht wird ist bedenklich!;-) Friedrich Nietzsche msg00660/pgp0.pgp Description: PGP signature
Re: dual boot win2k as boot loader
Hi, You could also save the mbr and there after install debian in the mbr. Then you load the saved win2k mbr in mbr and then change the boot.ini file. Best Regards Soren Rydlund - Original Message - From: "ernst" <[EMAIL PROTECTED]> To: "debian-user" <[EMAIL PROTECTED]> Sent: Wednesday, September 04, 2002 4:03 PM Subject: Re: dual boot win2k as boot loader > *This message was transferred with a trial version of CommuniGate(tm) Pro* > Hi > I would just install debian, and configure lilo in MBR on hda. That would > not destroy windoze bootloader, just take controll over it:) > > If you later want's to remove debian and lilo, you can just boot up with a > win98 boot/startupdisk and run "fdisk /mbr". > That's it. > > Good Luck > > /ernst > > > On Wed, 4 Sep 2002, Quenten Griffith wrote: > > > Hello all I am setting up a dual boot machine for a friend of mine who > > wants to give Linux a go, he has to 20 gig hard drives hda being where > > win2k resides, and hdb is broken up to two 10 gig partions. hdb1 being > > swap hdb3 being / on the first 9gig. The other 10gig is fat32 for > > storage space in windows. He does not want to lose the win2k boot > > loader just in case he doesn't like linux, that way he can remove linux > > with out messing up his MBR on hda. So I installed Debian and told Lilo > > to go on hdb3 and to write a MBR to hdb then I boot into it with the > > boot floppy and do a dd if=/devhdb of=/tmp/debian.bin bs=512 count=1 and > > then I take the .bin file and boot into windows and place it in the c:\ > > and edit boot.ini accordinly. After that I boot up and select debian > > and I get a black screen with MBR=FA3 or something along that lines and > > I can't do anything. So I then tried the same dd statement but used > > /dev/hdb3 and I get a screen full of 0 and 1's when I try to boot of > > that bin. Do I need to make a sepreate boot partition on /dev/hdb for > > Debian and then do the dd statment with the boot partion? I want ot > > make sure I get it right next time so that he won't give up on Linux. > > Thanks all. > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dual boot win2k as boot loader
Hi I would just install debian, and configure lilo in MBR on hda. That would not destroy windoze bootloader, just take controll over it:) If you later want's to remove debian and lilo, you can just boot up with a win98 boot/startupdisk and run "fdisk /mbr". That's it. Good Luck /ernst On Wed, 4 Sep 2002, Quenten Griffith wrote: > Hello all I am setting up a dual boot machine for a friend of mine who > wants to give Linux a go, he has to 20 gig hard drives hda being where > win2k resides, and hdb is broken up to two 10 gig partions. hdb1 being > swap hdb3 being / on the first 9gig. The other 10gig is fat32 for > storage space in windows. He does not want to lose the win2k boot > loader just in case he doesn't like linux, that way he can remove linux > with out messing up his MBR on hda. So I installed Debian and told Lilo > to go on hdb3 and to write a MBR to hdb then I boot into it with the > boot floppy and do a dd if=/devhdb of=/tmp/debian.bin bs=512 count=1 and > then I take the .bin file and boot into windows and place it in the c:\ > and edit boot.ini accordinly. After that I boot up and select debian > and I get a black screen with MBR=FA3 or something along that lines and > I can't do anything. So I then tried the same dd statement but used > /dev/hdb3 and I get a screen full of 0 and 1's when I try to boot of > that bin. Do I need to make a sepreate boot partition on /dev/hdb for > Debian and then do the dd statment with the boot partion? I want ot > make sure I get it right next time so that he won't give up on Linux. > Thanks all. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
dual boot win2k as boot loader
Hello all I am setting up a dual boot machine for a friend of mine who wants to give Linux a go, he has to 20 gig hard drives hda being where win2k resides, and hdb is broken up to two 10 gig partions. hdb1 being swap hdb3 being / on the first 9gig. The other 10gig is fat32 for storage space in windows. He does not want to lose the win2k boot loader just in case he doesn't like linux, that way he can remove linux with out messing up his MBR on hda. So I installed Debian and told Lilo to go on hdb3 and to write a MBR to hdb then I boot into it with the boot floppy and do a dd if=/devhdb of=/tmp/debian.bin bs=512 count=1 and then I take the .bin file and boot into windows and place it in the c:\ and edit boot.ini accordinly. After that I boot up and select debian and I get a black screen with MBR=FA3 or something along that lines and I can't do anything. So I then tried the same dd statement but used /dev/hdb3 and I get a screen full of 0 and 1's when I try to boot of that bin. Do I need to make a sepreate boot partition on /dev/hdb for Debian and then do the dd statment with the boot partion? I want ot make sure I get it right next time so that he won't give up on Linux. Thanks all. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
