Re: Bootloader error grub minimal bash "load the kernel first" after installing my live image via calamares installer

[Thomas Schmitt]

Hi,

please reply to the list in order to keep all readers informed.
(It would be ok to Cc my mail address, but it is not necessary.)

- Forwarded message from Sakkra Billa  -
Date: Mon, 14 Aug 2023 09:32:37 +0530
From: Sakkra Billa 
To: Thomas Schmitt 
Subject: Re: Bootloader error grub minimal bash "load the kernel first"
after installing my live image via calamares installer

Thanks for the reply. I tried debian di too but wasn't successful in that
either it said that the kernel version for live and installer were not the
same.

- End forwarded message -

The problem is out of my range of experience and probably out of the
experience of the other participants here.

So you will have to ask the Debian Installer experts what goes wrong.

  https://wiki.debian.org/DebianInstaller
proposes
  Email: debian-b...@lists.debian.org
  IRC: #debian-boot

To improve your chances for helpful replies you should give them tangible
information. At least:
- The possibile configuration of the installer,
- the commands used to bring it into the directory tree which later
  becomes the ISO content,
- the exact error messages you get from the attempt to use the installer.
  (Even if this means that you have to manually toggle them into your
   mail.)


Have a nice day :)

Thomas

[sakkrabi...@gmail.com: Re: Bootloader error grub minimal bash "load the kernel first" after installing my live image via calamares installer]

[Andrew M.A. Cater]

- Forwarded message from Sakkra Billa  -

Date: Sun, 13 Aug 2023 21:35:33 +0530
From: Sakkra Billa 
To: "Andrew M.A. Cater" 
Subject: Re: Bootloader error grub minimal bash "load the kernel first" after
installing my live image via calamares installer

Thanks for the reply,
Actually i am not using debian live-build (as it wont work for 512mb ram)
rather i am using debootstrap

On Sun, Aug 13, 2023 at 8:43 PM Andrew M.A. Cater 
wrote:

> On Sun, Aug 13, 2023 at 06:56:08PM +0530, Sakkra Billa wrote:
> > I followed the tutorial from:
> > https://www.willhaley.com/blog/custom-debian-live-environment/ to make a
> > live custom debian 12 image. In order to install it on my VM I installed
> > calamares, calamares-settings-debian and rsync . The live image works
> > perfectly and the installation also finishes without errors but when i
> > reboot my VM into the installed environment, it boots into grub minimal
> > bash line editing mode. On typing boot it says "load the kernel first". I
> > did not change any of the calamares settings everything is default.
> Please
> > guide me that where did i go wrong.
>
> I don't know the tutorial. I'd suggest asking on IRC channel debian-live on
> OFTC or on the debian-live Debian mailing list.
>
> I think this is sufficiently niche that those two sources of advice may
> prove to be better.
>
> All the very best, as ever,
>
> Andy Cater
>
>

- End forwarded message -

Re: Bootloader error grub minimal bash "load the kernel first" after installing my live image via calamares installer

[Thomas Schmitt]

Hi,

Sakkra Billa wrote:
> I followed the tutorial
> from: https://www.willhaley.com/blog/custom-debian-live-environment/
> [www.willhaley.com] to make a live custom debian 12 image.

(The xorriso run looks ok.)


> In order to
> install it on my VM I installed calamares, calamares-settings-debian and
.rsync . The live image works perfectly

So the aim of the tutorial was achieved.


> and the installation also finishes
> without errors but when i reboot my VM into the installed environment, it
> boots into grub minimal bash line editing mode. On typing boot it says "load
> the kernel first".

I assume you used calamares for the installation.
Obviously it did not give GRUB the right configuration to load the
installed Linux kernel.


> I did not change any of the calamares settings everything
> is default.

You will have to look for instructions about calamares.


Have a nice day :)

Thomas

Re: Bootloader error grub minimal bash "load the kernel first" after installing my live image via calamares installer

[Andy Smith]

Hi,

On Sun, Aug 13, 2023 at 06:56:08PM +0530, Sakkra Billa wrote:
>when i reboot my VM into the installed environment, it boots into
>grub minimal On typing boot it says "load the kernel first".

What kind of VM is this? Which provider, if you are unsure.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: Bootloader error grub minimal bash "load the kernel first" after installing my live image via calamares installer

[Michael Kjörling]

On 13 Aug 2023 18:56 +0530, from sakkrabi...@gmail.com (Sakkra Billa):
> but when i
> reboot my VM into the installed environment, it boots into grub minimal
> bash line editing mode. On typing boot it says "load the kernel first".

Sounds to me like GRUB can't find grub.cfg, or it is somehow corrupt.

-- 
Michael Kjörling  https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Re: Bootloader error grub minimal bash "load the kernel first" after installing my live image via calamares installer

[Andrew M.A. Cater]

On Sun, Aug 13, 2023 at 06:56:08PM +0530, Sakkra Billa wrote:
> I followed the tutorial from:
> https://www.willhaley.com/blog/custom-debian-live-environment/ to make a
> live custom debian 12 image. In order to install it on my VM I installed
> calamares, calamares-settings-debian and rsync . The live image works
> perfectly and the installation also finishes without errors but when i
> reboot my VM into the installed environment, it boots into grub minimal
> bash line editing mode. On typing boot it says "load the kernel first". I
> did not change any of the calamares settings everything is default. Please
> guide me that where did i go wrong.

I don't know the tutorial. I'd suggest asking on IRC channel debian-live on
OFTC or on the debian-live Debian mailing list.

I think this is sufficiently niche that those two sources of advice may
prove to be better.

All the very best, as ever,

Andy Cater

Bootloader error grub minimal bash "load the kernel first" after installing my live image via calamares installer

[Sakkra Billa]

I followed the tutorial from:
https://www.willhaley.com/blog/custom-debian-live-environment/ to make a
live custom debian 12 image. In order to install it on my VM I installed
calamares, calamares-settings-debian and rsync . The live image works
perfectly and the installation also finishes without errors but when i
reboot my VM into the installed environment, it boots into grub minimal
bash line editing mode. On typing boot it says "load the kernel first". I
did not change any of the calamares settings everything is default. Please
guide me that where did i go wrong.

Re: Debian netinstall systemd-boot (bootloader) support

[Kenneth Parker]

On Wed, Jan 29, 2020, 11:04 AM Fun Society  wrote:

> I'm using it on debian (replacing the grub) but it was frustrating using
> netinstall ISO, you can't boot live to install the systemd-boot easily, so
> I find a way to boot my Debian using grub rescue then install the
> systemd-boot. That's why I suggest systemd-boot must be added as bootloader
> options on the installer
>

Thanks!  Grub-Rescue (on cd) is an awesome suggestion, for if something
goes wrong, when installing systemd-boot after the fact.

Kenneth Parker

>
> On Wed, Jan 29, 2020, 22:51 Kenneth Parker  wrote:
>
>>
>>
>> On Wed, Jan 29, 2020, 2:27 AM Fun Society  wrote:
>>
>>> Hi, can you guys add/provide systemd-boot option on the Debian
>>> installer? Because some of the UEFI laptop not supported grub bootloader,
>>> The bios automatically delete boot entry if the name of the grub boot entry
>>> not "Linux" and grub installation by Debian installer is named Debian so
>>> the machine won't detect the os.
>>>
>>> The machine will boot if the grub is installed with this specific
>>> command:
>>> grub-install --target=x86_64-efi --boot-directory=esp
>>> --bootloader-id="Linux"
>>>
>>> Which is not the command provided by the Debian installer.
>>>
>>> So I suggest systemd-boot should be added as options for bootloader
>>> installation on the Debian installer. The BIOS can automatically detect OS
>>> by systemd-boot.
>>>
>>
>> I would like to learn more about systemd-boot.  Has anyone used it with
>> Debian?  (The rather informative article I am reading is for Arch Linux,
>> and was at the top of a Google Search).
>>
>>>
>>> This probably happened on windows only supported os.
>>>
>>
>> It *does* say that it only works with uefi, meaning "recent Windows".
>>
>> Kenneth Parker
>>
>

Re: Re: Debian netinstall systemd-boot (bootloader) support

[Fun Society]

I'm using it on debian (replacing the grub) but it was frustrating using
netinstall ISO, you can't boot live to install the systemd-boot easily, so
I find a way to boot my Debian using grub rescue then install the
systemd-boot. That's why I suggest systemd-boot must be added as bootloader
options on the installer.

Re: Debian netinstall systemd-boot (bootloader) support

[Kenneth Parker]

On Wed, Jan 29, 2020, 2:27 AM Fun Society  wrote:

> Hi, can you guys add/provide systemd-boot option on the Debian installer?
> Because some of the UEFI laptop not supported grub bootloader, The bios
> automatically delete boot entry if the name of the grub boot entry not
> "Linux" and grub installation by Debian installer is named Debian so the
> machine won't detect the os.
>
> The machine will boot if the grub is installed with this specific command:
> grub-install --target=x86_64-efi --boot-directory=esp
> --bootloader-id="Linux"
>
> Which is not the command provided by the Debian installer.
>
> So I suggest systemd-boot should be added as options for bootloader
> installation on the Debian installer. The BIOS can automatically detect OS
> by systemd-boot.
>

I would like to learn more about systemd-boot.  Has anyone used it with
Debian?  (The rather informative article I am reading is for Arch Linux,
and was at the top of a Google Search).

>
> This probably happened on windows only supported os.
>

It *does* say that it only works with uefi, meaning "recent Windows".

Kenneth Parker

Debian netinstall systemd-boot (bootloader) support

[Fun Society]

Hi, can you guys add/provide systemd-boot option on the Debian installer?
Because some of the UEFI laptop not supported grub bootloader, The bios
automatically delete boot entry if the name of the grub boot entry not
"Linux" and grub installation by Debian installer is named Debian so the
machine won't detect the os.

The machine will boot if the grub is installed with this specific command:
grub-install --target=x86_64-efi --boot-directory=esp
--bootloader-id="Linux"

Which is not the command provided by the Debian installer.

So I suggest systemd-boot should be added as options for bootloader
installation on the Debian installer. The BIOS can automatically detect OS
by systemd-boot.

This probably happened on windows only supported os.

Sincerely

Windows bootloader (was Re: using a Windows 7 disk image with KVM?)

[Chris]

On Fri, 21 Sep 2018 18:49:43 +0500
Alexander V. Makartsev wrote:

> I always prefer to do the job with the tools that are native to OS.

Me too. Unfortunately, I wasn't able to repair the bootloader when
moving a windows 10 partition with gparted (to resize it later).
Reinstalling Windows was faster.

Chris

Re: bootloader customization (was: System Dorked -- Help...)

[moxalt]

On Sun, 25 Oct 2015 13:52:06 -0400, Felix Miata  wrote:

> David Baron composed on 2015-10-25 14:53 (UTC+0200):
> 
> > I started with wheezy 64 bit install and grub2. Did not have any clue how
> > it worked but it did. When upgraded to Sid, added a kernel and wanted to
> > keep the older on around just-in-case, I had no idea how to do this with
> > Grub2 so I went back to Lilo. Lilo also makes it easy of have a systemd and
> > older-style init choice, the latter saved me recently.  
> 
> > Running afoul of having two 1 terra disks around could have been the
> > problem. I have no understanding of this business. I had no problem reading
> > and writing the partition I wanted to make root. Just could not do anything
> > in it, either chroot or on boot into the system which malfunctioned.  
> 
> > How do I make custom boot menus, kernel, init choices and such using the
> > Grub?  
> 
> There are numerous www howtos for customizing Grub2.
> http://ubuntuforums.org/showthread.php?t=1296225 amounts to one such.
> 
> Customizing Grub Legacy is much simpler.
> http://www.gnu.org/software/grub/manual/legacy/grub.html#Installing-GRUB-natively
> explains setting it up simply.
> 
> http://fm.no-ip.com/Share/Linux/menu.lst can serve as a menu.lst template
> based on how things work here. Note in its lower section there are special
> stanzas used only for network installations. I don't download many iso files.
> It's wasteful of bandwidth to download so much that will only be used at most
> once. There are no hard dependencies on configs elsewhere located when using
> Grub Legacy, but do note that Debian's Grub Legacy still cannot read EXT4
> filesystems at least as of Jessie, so its use should be limited accordingly
> either to systems on which EXT4 isn't present, or to needing access only to
> EXT3 or EXT2 or older supported filesystems. Grub Legacy in Mageia, Fedora
> and openSUSE have no such limitation. I use openSUSE's, as it has a nice
> gfxboot configuration that's simple enough to use and customize, and
> extremely friendly at boot time.
> 
> Should you wish to try Grub Legacy, I'll be more than happy to assist.

I used GRUB Legacy (one of the 0.99~ releases) under Debian 7, and it worked
fine reading from ext4.

Re: bootloader customization (was: System Dorked -- Help...)

[Felix Miata]

David Baron composed on 2015-10-25 14:53 (UTC+0200):

> I started with wheezy 64 bit install and grub2. Did not have any clue how it 
> worked but it did. 
> When upgraded to Sid, added a kernel and wanted to keep the older on around 
> just-in-case, I 
> had no idea how to do this with Grub2 so I went back to Lilo. Lilo also makes 
> it easy of have a 
> systemd and older-style init choice, the latter saved me recently.

> Running afoul of having two 1 terra disks around could have been the problem. 
> I have no 
> understanding of this business. I had no problem reading and writing the 
> partition I wanted to 
> make root. Just could not do anything in it, either chroot or on boot into 
> the system which 
> malfunctioned.

> How do I make custom boot menus, kernel, init choices and such using the Grub?

There are numerous www howtos for customizing Grub2.
http://ubuntuforums.org/showthread.php?t=1296225 amounts to one such.

Customizing Grub Legacy is much simpler.
http://www.gnu.org/software/grub/manual/legacy/grub.html#Installing-GRUB-natively
explains setting it up simply.

http://fm.no-ip.com/Share/Linux/menu.lst can serve as a menu.lst template
based on how things work here. Note in its lower section there are special
stanzas used only for network installations. I don't download many iso files.
It's wasteful of bandwidth to download so much that will only be used at most
once. There are no hard dependencies on configs elsewhere located when using
Grub Legacy, but do note that Debian's Grub Legacy still cannot read EXT4
filesystems at least as of Jessie, so its use should be limited accordingly
either to systems on which EXT4 isn't present, or to needing access only to
EXT3 or EXT2 or older supported filesystems. Grub Legacy in Mageia, Fedora
and openSUSE have no such limitation. I use openSUSE's, as it has a nice
gfxboot configuration that's simple enough to use and customize, and
extremely friendly at boot time.

Should you wish to try Grub Legacy, I'll be more than happy to assist.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Bootloader + tftp

[Marco A]

Salve Lista

Prezados , tenho algumas maquinas diskless( build on bootstrap) onde rodo
algumas aplicações em sistema de arquivos ramdisk . Para facilitar futuras
configurações e atualizações nos respectivos rootfs, pretendo quando
necessário que estas maquinas no processo de boot busquem a imagem via rede.

Porem  a imagem rootfs  que as  maquinas cliente devem  carregar não estão
na mesma rede do servidor dhcp/tftp e tambem a referida rede não existe
possibilidade de um servidor para tal finalidade(dhcp/pxelinux.0) ,assim o
tradicional boot pxe creio que não funcionaria.

Para este cénario  será necessário  um bootloader nas maquinas cliente,
porem este terá que reconhecer  placa de rede e subir com as devidas
configurações para então buscar a imagem no servidor ip-mask-gw
ip-servidor-tftp

Pesquisando  a respeito creio que apenas com o Grub  daria conta ,bootando
a maquina cliente e subindo a rede.  Nas opções do Grub Legacy e Grub2 tem
suporte a boot de rede mas tem que recompilar com o respectivo driver para
placa , porem fica a duvida se atenderia ao que preciso.


Ou quem sabe um outro bootloader ,similar a U-boot  ou Super Grub




Sds.

Marcos

Re: Debian 7 and Debian 8 and bootloader

[Pascal Hambourg]

Bret Busby a écrit :
 
 It would be on a UEFI/GPT system, so the primary partitions are redundant.
 
 With Linux, I generally have a / partition, a /swap partition, a /home
 partition, and data partitions, with the swap partition being shared
 between the Linux installations; as they are not running concurrently,
 I do not see a problem with the /swap partition being shared between
 them.

You will see the problem if you hibernate (suspend to disk) one
installation and reboot to another installation.

 On a UEFI system that does not allow the Dual system, and, does not
 allow for the Secure Boot option to be turned off within UEFI, I have
 to choose either UEFI or Legacy, and the Win 8 is booted via UEFI, and
 the Linux systems are booted via the Legacy option.

Yet another broken UEFI implementation. According to Microsoft
requirements, secure boot can be disabled on non-ARM platforms certified
for Windows 8.

However it may be possible to boot Debian with secure boot, see for
example http://www.rodsbooks.com/efi-bootloaders/secureboot.html.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/551f92ca.5080...@plouf.fr.eu.org

Debian 7 and Debian 8 and bootloader

[Bret Busby]

Hello.

Do Debian 7 and Debian 8 (when it is to be released), and a bootloader
such as GRUB, allow yet, for more than one version of Debian, to be
installed on a system, and, to be selectable options for the
bootloader?

-- 
Bret Busby
Armadale
West Australia
..

So once you do know what the question actually is,
 you'll know what the answer means.
- Deep Thought,
 Chapter 28 of Book 1 of
 The Hitchhiker's Guide to the Galaxy:
 A Trilogy In Four Parts,
 written by Douglas Adams,
 published by Pan Books, 1992




-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CACX6j8N1bw=1GmKs9HKGw=ycfnhunr3q5tgy5h9w9f8qp+j...@mail.gmail.com

Re: Debian 7 and Debian 8 and bootloader

[Andrew M.A. Cater]

On Sat, Apr 04, 2015 at 01:51:15AM +0800, Bret Busby wrote:
 Hello.
 
 Do Debian 7 and Debian 8 (when it is to be released), and a bootloader
 such as GRUB, allow yet, for more than one version of Debian, to be
 installed on a system, and, to be selectable options for the
 bootloader?
 
 -- 
 Bret Busby
 Armadale
 West Australia
 ..
 

Should do: it would probably be a good idea to install Debian 7 first on 
the first half of the disk, using the expert install, and then to install
Debian 8 separately on the second half of the disk.

I'd be happy to attempt to do this to check for you, if requested.

All the best,

Andy





 So once you do know what the question actually is,
  you'll know what the answer means.
 - Deep Thought,
  Chapter 28 of Book 1 of
  The Hitchhiker's Guide to the Galaxy:
  A Trilogy In Four Parts,
  written by Douglas Adams,
  published by Pan Books, 1992
 
 
 
 
 -- 
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 https://lists.debian.org/CACX6j8N1bw=1GmKs9HKGw=ycfnhunr3q5tgy5h9w9f8qp+j...@mail.gmail.com


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150403211204.ga1...@galactic.demon.co.uk

Re: Debian 7 and Debian 8 and bootloader

[David Wright]

Quoting Andrew M.A. Cater (amaca...@galactic.demon.co.uk):
 On Sat, Apr 04, 2015 at 01:51:15AM +0800, Bret Busby wrote:
  Do Debian 7 and Debian 8 (when it is to be released), and a bootloader
  such as GRUB, allow yet, for more than one version of Debian, to be
  installed on a system, and, to be selectable options for the
  bootloader?
 
 Should do: it would probably be a good idea to install Debian 7 first on 
 the first half of the disk, using the expert install, and then to install
 Debian 8 separately on the second half of the disk.
 
 I'd be happy to attempt to do this to check for you, if requested.

No need to check; yes, this is routine. But I would refine that
suggestion slightly. On my own disks I create four primary partitions,
for two versions of Debian (each in between 20 and 32GB), a swap and
the rest as /home. (Many other people are now using logical volume
managers and suchlike.)

Typically I will have a stable and a testing, partly for new features
of important (to me) software (like lilypond), but also so that I can
learn about the new features while early adopters are interested in/
discussing them.

Grub also manages the (almost unused) windows disks that a couple of
my computers contain.

Cheers,
David.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150404000809.gc13...@alum.home

Re: Debian 7 and Debian 8 and bootloader

[Bret Busby]

On 04/04/2015, David Wright deb...@lionunicorn.co.uk wrote:
 Quoting Andrew M.A. Cater (amaca...@galactic.demon.co.uk):
 On Sat, Apr 04, 2015 at 01:51:15AM +0800, Bret Busby wrote:
  Do Debian 7 and Debian 8 (when it is to be released), and a bootloader
  such as GRUB, allow yet, for more than one version of Debian, to be
  installed on a system, and, to be selectable options for the
  bootloader?

 Should do: it would probably be a good idea to install Debian 7 first on
 the first half of the disk, using the expert install, and then to install
 Debian 8 separately on the second half of the disk.

 I'd be happy to attempt to do this to check for you, if requested.

 No need to check; yes, this is routine. But I would refine that
 suggestion slightly. On my own disks I create four primary partitions,
 for two versions of Debian (each in between 20 and 32GB), a swap and
 the rest as /home. (Many other people are now using logical volume
 managers and suchlike.)

 Typically I will have a stable and a testing, partly for new features
 of important (to me) software (like lilypond), but also so that I can
 learn about the new features while early adopters are interested in/
 discussing them.

 Grub also manages the (almost unused) windows disks that a couple of
 my computers contain.

 Cheers,
 David.


It would be on a UEFI/GPT system, so the primary partitions are redundant.

With Linux, I generally have a / partition, a /swap partition, a /home
partition, and data partitions, with the swap partition being shared
between the Linux installations; as they are not running concurrently,
I do not see a problem with the /swap partition being shared between
them.

On a UEFI system that does not allow the Dual system, and, does not
allow for the Secure Boot option to be turned off within UEFI, I have
to choose either UEFI or Legacy, and the Win 8 is booted via UEFI, and
the Linux systems are booted via the Legacy option.

-- 
Bret Busby
Armadale
West Australia
..

So once you do know what the question actually is,
 you'll know what the answer means.
- Deep Thought,
 Chapter 28 of Book 1 of
 The Hitchhiker's Guide to the Galaxy:
 A Trilogy In Four Parts,
 written by Douglas Adams,
 published by Pan Books, 1992




-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cacx6j8mndlubdnpnufiqqfndmafmjejq+dgdakvugegi22+...@mail.gmail.com

Re: Compilar U-boot(Bootloader) para ARMv5

[Camaleón]

El Mon, 15 Dec 2014 20:03:45 +0100, TheMrRafus a escribió:

 Hola

Ese html...

 No se si sera aqui el sitio idoneo, pero dado que quiero compilarlo en
 un pc de 32 bits supongo qu ira aqui.
 
 El caso es que quiero compilar el bootloader U-Boot para el chipset
 Conexant CX 94610-11Z
 
 
 Supongo que necesito el Toolchain Linaro, hasta instalarlo se, lo que me
 falta son los comandos necesarios para compilarlo.

(..)

Mira a ver si esto te puede servir:

https://wiki.linaro.org/Resources/HowTo/BootloaderDeploy

Saludos,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/pan.2014.12.16.15.28...@gmail.com

Compilar U-boot(Bootloader) para ARMv5

[TheMrRafus a]

Hola

No se si sera aqui el sitio idoneo, pero dado que quiero compilarlo en un
pc de 32 bits supongo qu ira aqui.

El caso es que quiero compilar el bootloader U-Boot para el chipset
Conexant CX 94610-11Z


Supongo que necesito el Toolchain Linaro, hasta instalarlo se, lo que me
falta son los comandos necesarios para compilarlo.

U-boot es compatible con ese chipset.

Uso Debian Wheezy con xfce 32 bits por si es de ayuda

El uboot que quiero compilar es de linaro:

https://git.linaro.org/?p=boot/u-boot-linaro-stable.git;a=summary


Saludos

Re: Unable to install bootloader on software raid

[Darac Marjal]

On Sat, Dec 13, 2014 at 11:36:58AM +0200, Johann Spies wrote:
After two of my hard disks failed, I decided to use a software raid in
future and tried to install Debian Testing on the raid.  The configuration
of the raid and software installation went well until I tried to install
the bootloader.  Both Grub and Lilo refused to install.
 
If it is not possible to install Grub or Lilo onto a software raid, why is
the option available in Grub?
 
I have seen several efforts to solve this problem on the internet, but
none of them worked for me.
 
What is the way to install Debian onto a software raid?

I think the problem is that, depending on the RAID level, the BIOS won't
be able to read the disks in order to load GRUB. If you're running
RAID0, then you're in luck; both drives appear as normal disks and all
that RAID does is ensure they are kept identical. If you're running
RAID1, though, then each disk is a chopped-up mess of data and you NEED
the RAID to provide the hint that half the data is on another device.

Now, once grub is loaded, it CAN assemble the RAID to a sufficient point
to load all the pieces of the kernel, but if the BIOS can't make enough
sense out of the disk to load GRUB then you have a problem. In that
case, you would normally leave a portion of the disk unRAIDed and
install GRUB onto that.

 
Regards
Johann
--
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)


signature.asc
Description: Digital signature

Re: Unable to install bootloader on software raid

[Sven Hartge]

Darac Marjal mailingl...@darac.org.uk wrote:

 I think the problem is that, depending on the RAID level, the BIOS won't
 be able to read the disks in order to load GRUB. If you're running
 RAID0, then you're in luck; both drives appear as normal disks and all
 that RAID does is ensure they are kept identical. If you're running
 RAID1, though, then each disk is a chopped-up mess of data and you NEED
 the RAID to provide the hint that half the data is on another device.

It's the other way round: RAID0 is striped, aka chopped up mess and
RAID1 are mirrored disks.

S°

-- 
Sigmentation fault. Core dumped.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/7b7phlg9v...@mids.svenhartge.de

Re: Unable to install bootloader on software raid

[Pascal Hambourg]

Sven Hartge a écrit :
 Darac Marjal mailingl...@darac.org.uk wrote:
 
 I think the problem is that, depending on the RAID level, the BIOS won't
 be able to read the disks in order to load GRUB. If you're running
 RAID0, then you're in luck; both drives appear as normal disks and all
 that RAID does is ensure they are kept identical. If you're running
 RAID1, though, then each disk is a chopped-up mess of data and you NEED
 the RAID to provide the hint that half the data is on another device.
 
 It's the other way round: RAID0 is striped, aka chopped up mess and
 RAID1 are mirrored disks.

Besides, the Linux RAID arrays usually do no reside on whole raw disks
but on RAID partitions. GRUB's boot image and core image are usually
installed on each disk outside these partitions. This way all the
sectors needed to load GRUB's core image can be found on each single
disk, regardless of the RAID level.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/548f5683.6010...@plouf.fr.eu.org

Unable to install bootloader on software raid

[Johann Spies]

After two of my hard disks failed, I decided to use a software raid in
future and tried to install Debian Testing on the raid.  The configuration
of the raid and software installation went well until I tried to install
the bootloader.  Both Grub and Lilo refused to install.

If it is not possible to install Grub or Lilo onto a software raid, why is
the option available in Grub?

I have seen several efforts to solve this problem on the internet, but none
of them worked for me.

What is the way to install Debian onto a software raid?

Regards
Johann

-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)

Re: Unable to install bootloader on software raid

[Ron]

On Sat, 13 Dec 2014 11:36:58 +0200
Johann Spies johann.sp...@gmail.com wrote:

 What is the way to install Debian onto a software raid?

I have installed 7.7.0-64 from the DVD without any problem.

So it might be something in Testing ?

Did you try to install from a Live-CD/DVD ? ISTR that in that case you must add 
dmraid=true at the end of the GRUB boot line.
 
Cheers,
 
Ron.
-- 
  Distrust all those who love you extremely
   upon a very slight acquaintance
   and without any visible reason.
   -- Lord Chesterfield

   -- http://www.olgiati-in-paraguay.org --
 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141213065435.7230a...@ron.cerrocora.org

Re: Unable to install bootloader on software raid

[Johann Spies]

Thanks for your reply, Ron.

In the end I configured my partions to exclude the first 250Mb (/boot) from
the raid and I could install Grub just to have a working system.

It is not the best solution.  The installer should work as expected.

Regards
Johann

-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)

Re: Unable to install bootloader on software raid

[Pascal Hambourg]

Johann Spies a écrit :
 
 In the end I configured my partions to exclude the first 250Mb (/boot) from
 the raid and I could install Grub just to have a working system.
 
 It is not the best solution.

Obviously it's not. /boot should be on a RAID (and the bootloader
installed on all disks, which the installer won't do automatically) in
order for the system to be able to boot after any disk failure.

How did you prepare the disks the first time ?

PS : dm-raid is needed only if you want to use software BIOS RAID (aka
fakeRAID, not recommended), not Linux native RAID.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/548cb11f.5060...@plouf.fr.eu.org

Re: Installing a bootloader on a Mac Mini without OSX

[Stefan Monnier]

  I've tried the i386 install (v7.7) CD multiple times and I've tried having
  it put GRUB on the MBR and on the partition and neither way resulted
  in a bootable install.
 I think this can be made to work with a bit of twiddling (e.g. using
 lilo or grub-legacy, or maybe tweaking of the partition table).
 But without knowing any more details than (not) resulted in a bootable
 install, it's hard to tell.
 The only further details I have is that I didn't see any sign of GRUB on any
 of the times I rebooted after an install.  The word GRUB never appeared on
 the screen, just the folder-with-a-question-mark icon.

When you're in Debian (probably via the install CD), what do

fdisk -l /dev/sda
and
parted /dev/sda print

return?

 I suspect I had grub v1 on there for a minute or two, the one time I tried
 the Lenny amd64 disc.

Try

grub-install /dev/sda

tell us what it said (there are many ways it can fail).  And tell us what

mount

says as well right before/after the above grub-install command.


Stefan


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/jwvtx13h66k.fsf-monnier+gmane.linux.debian.u...@gnu.org

Re: Installing a bootloader on a Mac Mini without OSX

[Brian Sammon]

On Thu, 4 Dec 2014 13:25:37 -0500
Brian Sammon debian-users-l...@brisammon.fastmail.fm wrote:

 Is there a way to install Debian/Linux on this machine that doesn't involve  
 buying or borrowing (or borrowing) a copy of OSX?  Is it easier to install 
  linux on a USB disk and run it off of that?

Status report:
I've tried the i386 install (v7.7) CD multiple times and I've tried having it 
put GRUB on the MBR and on the partition and neither way resulted in a bootable 
install.
The Wheezy 7.7 amd64 install CD doesn't boot at all.  Appears to be the same 
issue as bug #744959:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744959
I found a Lenny amd64 install CD, and it boots, but with no better results than 
the Wheezy i386 install CD.
Ubuntu has IntelMac-specific ISOs, I'll probably try one of those soon.

 Two particular subtasks that I may need to do that seem to require OSX:
 1) Blessing a partition

Still learning about this, but it appears that there are non-OSX options

 2) Checking what version of firmware it has (some versions have BIOS
compatibility)

I've been playing with a rEFInd (http://www.rodsbooks.com/refind/) boot CD and 
it has a function for reporting your firmware version.
Also, Apple's website doesn't list any firmware updates for my 2007 Mac Mini, 
so this is a moot point in my case.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20141207140942.810e188560016296c78f1...@brisammon.fastmail.fm

Re: Installing a bootloader on a Mac Mini without OSX

[Stefan Monnier]

 I've tried the i386 install (v7.7) CD multiple times and I've tried having
 it put GRUB on the MBR and on the partition and neither way resulted
 in a bootable install.

I think this can be made to work with a bit of twiddling (e.g. using
lilo or grub-legacy, or maybe tweaking of the partition table).
But without knowing any more details than (not) resulted in a bootable
install, it's hard to tell.


Stefan


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/jwv388rqjpe.fsf-monnier+gmane.linux.debian.u...@gnu.org

Re: Installing a bootloader on a Mac Mini without OSX

[Brian Sammon]

On Sun, 07 Dec 2014 15:40:33 -0500
Stefan Monnier monn...@iro.umontreal.ca wrote:

  I've tried the i386 install (v7.7) CD multiple times and I've tried having
  it put GRUB on the MBR and on the partition and neither way resulted
  in a bootable install.
 
 I think this can be made to work with a bit of twiddling (e.g. using
 lilo or grub-legacy, or maybe tweaking of the partition table).
 But without knowing any more details than (not) resulted in a bootable
 install, it's hard to tell.

The only further details I have is that I didn't see any sign of GRUB on any of 
the times I rebooted after an install.  The word GRUB never appeared on the 
screen, just the folder-with-a-question-mark icon.

I suspect I had grub v1 on there for a minute or two, the one time I tried the 
Lenny amd64 disc.  I had the same results there, as well.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20141207200604.968df1e672c12c3f1e1ce...@brisammon.fastmail.fm

debian 6.0.7 amd64 raid0 lvm crypt - bootloader issue

[shmick]

Hi all,

Having installed debian onto a hardware raid pc setup, using dmraid=true
switch, I attempt to repair the failed grub/lilo bootlader install after
rebooting into rescue, again with dmraid=true

How can I get grub installed?  

Background info:

Partitioning setup according to guided lvm crypt defaults with all installed
onto same partition

Using this setup /boot was created as primary partition under raid stripe
Ie /dev/mapper/long-sata-raid-name1

All else is located in logical encrypted volume
Ie /dev/mapper/long-sata-raid-name5

Start rescue mode and select /dev/my-volume-group/root to start shell

update-grub
-/usr/sbin/grub-probe: error: no such disk

Do I need to edit /boot/grub/device.map and if so what should I add
?

Current device.map includes

(hd0) /dev/disk/by-id/1st-sata-disk
(hd1) /dev/disk/by-id/2nd-sata-disk
(hd2) /dev/mapper/long-sata-raid-name

grub-install /dev/mapper/long-sata-raid-name
-/usr/sbin/grub-probe: error: no such disk

?


-- 
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/001101ce351b$71db2720$55917560$@riseup.net

Re: Bootloader

[Andrei Popescu]

On Lu, 28 mar 11, 11:04:01, Roman Gelfand wrote:
 Is it possible for syslinux to load another syslinux with it's own
 configuration file found in another directory?  If so, where can I
 find sample?

If you don't get useful answers in a few days you might want to look for 
some syslinux mailing lists/forums/...

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Bootloader

[Roman Gelfand]

Is it possible for syslinux to load another syslinux with it's own
configuration file found in another directory?  If so, where can I
find sample?

Thanks in advance


-- 
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/AANLkTi=hpyfnttswkwpvaeax94-lzfg7qffnabv-9...@mail.gmail.com

What's not cross-posting... (was Re: Adding a bootloader to a Windows partition image)

[Ron Johnson]

On 03/06/2011 01:38 AM, Doug wrote:
[snip]

A message I wrote in reply to a question on the Kubuntu list may be
of some help.
The message is called Install Win98 on /dev/sda4 and does not
actually install
Windows to /dev/sda4, but to /sdb1. And it's XP, not 98. Anyway,
since it is frowned
on to cross-post, I will tell you that the message was posted
03/06/2011 at 12:28 AM,
so you can look for it there. (The earlier post was by Jerry Lapham
at 03/05/2011
at 8:14 PM. He decided to use XP, which is what I had done.)



Adding a link to the body of the email is actually considered good 
practice, since Google will bump up the solution link.


--
I prefer banana-flavored energy bars made from tofu.


--
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/4d7340ad.3060...@cox.net

Re: What's not cross-posting... (was Re: Adding a bootloader to a Windows partition image)

[Doug]

On 03/06/2011 03:07 AM, Ron Johnson wrote:

On 03/06/2011 01:38 AM, Doug wrote:
[snip]

A message I wrote in reply to a question on the Kubuntu list may be
of some help.
The message is called Install Win98 on /dev/sda4 and does not
actually install
Windows to /dev/sda4, but to /sdb1. And it's XP, not 98. Anyway,
since it is frowned
on to cross-post, I will tell you that the message was posted
03/06/2011 at 12:28 AM,
so you can look for it there. (The earlier post was by Jerry Lapham
at 03/05/2011
at 8:14 PM. He decided to use XP, which is what I had done.)



Adding a link to the body of the email is actually considered good 
practice, since Google will bump up the solution link.



That sounds like a good idea.  How would I do that?
Thanx--doug

--
Blessed are the peacemakers...for they shall be shot at from both sides. --A. 
M. Greeley


--
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/4d7343f8.9050...@optonline.net

Re: What's not cross-posting... (was Re: Adding a bootloader to a Windows partition image)

[Ron Johnson]

On 03/06/2011 02:21 AM, Doug wrote:

On 03/06/2011 03:07 AM, Ron Johnson wrote:

On 03/06/2011 01:38 AM, Doug wrote:
[snip]

A message I wrote in reply to a question on the Kubuntu list may be
of some help.
The message is called Install Win98 on /dev/sda4 and does not
actually install
Windows to /dev/sda4, but to /sdb1. And it's XP, not 98. Anyway,
since it is frowned
on to cross-post, I will tell you that the message was posted
03/06/2011 at 12:28 AM,
so you can look for it there. (The earlier post was by Jerry Lapham
at 03/05/2011
at 8:14 PM. He decided to use XP, which is what I had done.)



Adding a link to the body of the email is actually considered good
practice, since Google will bump up the solution link.


That sounds like a good idea. How would I do that?


Like this:
https://lists.ubuntu.com/archives/kubuntu-users/2011-March/053651.html

--
I prefer banana-flavored energy bars made from tofu.


--
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/4d735df9.7060...@cox.net

Re: What's not cross-posting... (was Re: Adding a bootloader to a Windows partition image)

[Doug]

On 03/06/2011 05:12 AM, Ron Johnson wrote:

On 03/06/2011 02:21 AM, Doug wrote:

/snip/

since it is frowned
on to cross-post, I will tell you that the message was posted
03/06/2011 at 12:28 AM,
so you can look for it there. (The earlier post was by Jerry Lapham
at 03/05/2011
at 8:14 PM. He decided to use XP, which is what I had done.)



Adding a link to the body of the email is actually considered good
practice, since Google will bump up the solution link.


/snip/. Anyway,
That sounds like a good idea. How would I do that?


Like this:
https://lists.ubuntu.com/archives/kubuntu-users/2011-March/053651.html


You have illustrated the results of doing what you suggest, but not how
to go about doing it.  I see, for instance, ubuntu which is not part 
of the

story at all--debian and kubuntu are the lists involved. Also, the 3651
after the basic date?  Where does that come from?  I'm afraid that I'm
not getting it.

--doug

--
Blessed are the peacemakers...for they shall be shot at from both sides. --A. 
M. Greeley


--
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/4d73f457.7000...@optonline.net

Re: Adding a bootloader to a Windows partition image

[Joel Roth]

On Sun, Mar 06, 2011 at 02:38:54AM -0500, Doug wrote:
 On 03/06/2011 01:05 AM, Joel Roth wrote:
 Hi,
 
 I installed kvm-qemu and enabled virtualization in BIOS.
 
 Now, I have a Windows partition I'd like to fiddle.
 It was produced thusly:
 
  dd if=/dev/sdb1 of=windows_partition
 
 Entering this command
 
  qemu --enable-kvm windows_partition
 
 opens a black window with the booting message.
 
 Of course, it needs a boot loader. I tried this:
 
  grub-install windows_partition
 
 But this fails with:
 
  Format of install_device not recognized.
 
  INSTALL_DEVICE can be a GRUB device name or a system device filename.
 
 Can someone suggest or point a reference to help me
 create a bootable partition?
 
 A LILO solution would be okay, too.
 
 Thanks!
 
 A message I wrote in reply to a question on the Kubuntu list may be
 of some help.
 The message is called Install Win98 on /dev/sda4 and does not
 actually install
 Windows to /dev/sda4, but to /sdb1. And it's XP, not 98.  Anyway,
 since it is frowned
 on to cross-post, I will tell you that the message was posted
 03/06/2011 at 12:28 AM,
 so you can look for it there.  (The earlier post was by Jerry Lapham
 at 03/05/2011
 at 8:14 PM.  He decided to use XP, which is what I had done.)

Ron Johnson added:

 https://lists.ubuntu.com/archives/kubuntu-users/2011-March/053651.html 

What I want really, is to copy GRUB to the boot record
to the **partition image**, so I can say.

qemu --enable-kvm windows_partition_image

What I just thought of would be to use grub-install
with the correct parameters to a real partition, 
then dd it to the partition image.

Regards,

 --doug
 
 -- 
 Blessed are the peacemakers...for they shall be shot at from both sides. 
 --A. M. Greeley

Yow!  For a contemporary flavor I could add:

...by guns sold to drug cartels under the watchful eyes of ATF
 
-- 
Joel Roth


-- 
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/20110306211806.GA28447@sprite

Re: What's not cross-posting... (was Re: Adding a bootloader to a Windows partition image)

[Ron Johnson]

On 03/06/2011 02:53 PM, Doug wrote:

On 03/06/2011 05:12 AM, Ron Johnson wrote:

On 03/06/2011 02:21 AM, Doug wrote:

/snip/

since it is frowned
on to cross-post, I will tell you that the message was posted
03/06/2011 at 12:28 AM,
so you can look for it there. (The earlier post was by Jerry
Lapham
at 03/05/2011
at 8:14 PM. He decided to use XP, which is what I had done.)



Adding a link to the body of the email is actually considered good
practice, since Google will bump up the solution link.


/snip/. Anyway,
That sounds like a good idea. How would I do that?


Like this:
https://lists.ubuntu.com/archives/kubuntu-users/2011-March/053651.html



You have illustrated the results of doing what you suggest, but not how
to go about doing it. I see, for instance, ubuntu which is not
part of the
story at all--debian and kubuntu are the lists involved. Also, the
3651
after the basic date? Where does that come from? I'm afraid that I'm
not getting it.



I googled for the quote, and pasted the link into the email.

You seem to think that this is more than just pasting text (in this 
case a url) into an email window, but it's not.


--
I prefer banana-flavored energy bars made from tofu.


--
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/4d73fcb5.4000...@cox.net

Adding a bootloader to a Windows partition image

[Joel Roth]

Hi,

I installed kvm-qemu and enabled virtualization in BIOS.

Now, I have a Windows partition I'd like to fiddle.
It was produced thusly:

dd if=/dev/sdb1 of=windows_partition

Entering this command

qemu --enable-kvm windows_partition 

opens a black window with the booting message.

Of course, it needs a boot loader. I tried this:

grub-install windows_partition

But this fails with:

Format of install_device not recognized.

INSTALL_DEVICE can be a GRUB device name or a system device filename.

Can someone suggest or point a reference to help me
create a bootable partition?

A LILO solution would be okay, too.

Thanks!

-- 
Joel Roth


-- 
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/20110306060552.GA3645@sprite

Re: Adding a bootloader to a Windows partition image

[Doug]

On 03/06/2011 01:05 AM, Joel Roth wrote:

Hi,

I installed kvm-qemu and enabled virtualization in BIOS.

Now, I have a Windows partition I'd like to fiddle.
It was produced thusly:

 dd if=/dev/sdb1 of=windows_partition

Entering this command

 qemu --enable-kvm windows_partition

opens a black window with the booting message.

Of course, it needs a boot loader. I tried this:

 grub-install windows_partition

But this fails with:

 Format of install_device not recognized.

 INSTALL_DEVICE can be a GRUB device name or a system device filename.

Can someone suggest or point a reference to help me
create a bootable partition?

A LILO solution would be okay, too.

Thanks!

A message I wrote in reply to a question on the Kubuntu list may be of 
some help.
The message is called Install Win98 on /dev/sda4 and does not actually 
install
Windows to /dev/sda4, but to /sdb1. And it's XP, not 98.  Anyway, since 
it is frowned
on to cross-post, I will tell you that the message was posted 03/06/2011 
at 12:28 AM,
so you can look for it there.  (The earlier post was by Jerry Lapham at 
03/05/2011

at 8:14 PM.  He decided to use XP, which is what I had done.)

--doug


--
Blessed are the peacemakers...for they shall be shot at from both sides. --A. 
M. Greeley


--
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/4d733a0e.3070...@optonline.net

Squeeze. Failed to install bootloader in VirtualBox

[Mark Goldshtein]

Hello, list!

Here is a try to install Squeeze into Oracle VirtualBox 3.2.6. Virtual
drive is 8.0 GB persistent, RAM 768 Mb, a virtual drive was
partitioned by Squeeze installer with default settings (/, swap;
ext3). Everything is fine, except for bootloader. There is a failure
during GRUB (GRUB2, lilo) installation process: GRUB installation
failed. The 'grub-pc' package failed to install
into /target/.

Also tried to partition a virtual hdd before Squeeze installation. No
effect, bootloader installation failed also.

Please, help to install a bootloader.

Thanks for your time!

-- 

Sincerely Yours'
Mark Goldshtein


-- 
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/aanlktik_0oyrvma7fzjl4npynk0sbikxcyqybx_wj...@mail.gmail.com

Re: Squeeze. Failed to install bootloader in VirtualBox

[Camaleón]

On Wed, 15 Sep 2010 18:32:19 +0400, Mark Goldshtein wrote:

 Here is a try to install Squeeze into Oracle VirtualBox 3.2.6. Virtual
 drive is 8.0 GB persistent, RAM 768 Mb, a virtual drive was partitioned
 by Squeeze installer with default settings (/, swap; ext3). Everything
 is fine, except for bootloader. There is a failure during GRUB (GRUB2,
 lilo) installation process: GRUB installation failed. The 'grub-pc'
 package failed to install into /target/.
 
 Also tried to partition a virtual hdd before Squeeze installation. No
 effect, bootloader installation failed also.
 
 Please, help to install a bootloader.

I also had problems for installing GRUB (legacy) into VM using d-i 
(squeeze). I had to use SuperGrubDisk and proceed from there.

Indeed, installing GRUB in lenny was also problematic, IIRC. The first 
time always failed (red screen with error message: GRUB installation 
failed), and had to retry to get it properly installed :-?

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.2010.09.15.14.51...@gmail.com

Re: Squeeze. Failed to install bootloader in VirtualBox

[Mark Goldshtein]

On Wed, Sep 15, 2010 at 6:51 PM, Camaleón noela...@gmail.com wrote:
 On Wed, 15 Sep 2010 18:32:19 +0400, Mark Goldshtein wrote:

 Here is a try to install Squeeze into Oracle VirtualBox 3.2.6. Virtual
 drive is 8.0 GB persistent, RAM 768 Mb, a virtual drive was partitioned
 by Squeeze installer with default settings (/, swap; ext3). Everything
 is fine, except for bootloader. There is a failure during GRUB (GRUB2,
 lilo) installation process: GRUB installation failed. The 'grub-pc'
 package failed to install into /target/.

 Also tried to partition a virtual hdd before Squeeze installation. No
 effect, bootloader installation failed also.

 Please, help to install a bootloader.

 I also had problems for installing GRUB (legacy) into VM using d-i
 (squeeze). I had to use SuperGrubDisk and proceed from there.

Thanks for an idea. Tried both SGD and Debian Squeeze weekly build
DVD-1 'Rescue Mode' with no success: apt-get reported there are no
such files on the media. Actually they are in a proper place and
sources.list is in order and contains that DVD as a valid repository.

 Indeed, installing GRUB in lenny was also problematic, IIRC. The first
 time always failed (red screen with error message: GRUB installation
 failed), and had to retry to get it properly installed :-?

Yes, I confirm that. Another way to won was to pre-partition a target
drive by LiveCD before an actual install.

Have no clue on next step anyway. Tried Squeeze netinstall image on
the same VirtualBox, it is not booting even.
How to install Squeeze??
-- 

Sincerely Yours'
Mark Goldshtein


--
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/aanlktikw6k8jy12cdxvq0zmexws9uqdqnnvcdw+h4...@mail.gmail.com

Re: Squeeze. Failed to install bootloader in VirtualBox

[Camaleón]

On Wed, 15 Sep 2010 20:05:58 +0400, Mark Goldshtein wrote:

 On Wed, Sep 15, 2010 at 6:51 PM, Camaleón wrote:

 I also had problems for installing GRUB (legacy) into VM using d-i
 (squeeze). I had to use SuperGrubDisk and proceed from there.
 
 Thanks for an idea. Tried both SGD and Debian Squeeze weekly build DVD-1
 'Rescue Mode' with no success: apt-get reported there are no such files
 on the media. Actually they are in a proper place and sources.list is in
 order and contains that DVD as a valid repository.

Mmm, SDG does not works for you? That's weird :-?

What I made was downloading the ISO image from SDG site and configured 
Virtualbox squeeze vm machine to boot from there. That way GRUB installed 
just fine.

 Indeed, installing GRUB in lenny was also problematic, IIRC. The first
 time always failed (red screen with error message: GRUB installation
 failed), and had to retry to get it properly installed :-?
 
 Yes, I confirm that. Another way to won was to pre-partition a target
 drive by LiveCD before an actual install.
 
 Have no clue on next step anyway. Tried Squeeze netinstall image on the
 same VirtualBox, it is not booting even. How to install Squeeze??

Well, I think you can always install squeeze without a bootloader and 
install it later (from SDG or from squeeze itself).

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.2010.09.15.16.22...@gmail.com

Re: Squeeze. Failed to install bootloader in VirtualBox

[Greg Madden]

On Wednesday 15 September 2010 08:05:58 Mark Goldshtein wrote:
 On Wed, Sep 15, 2010 at 6:51 PM, Camaleón noela...@gmail.com wrote:
  On Wed, 15 Sep 2010 18:32:19 +0400, Mark Goldshtein wrote:
  Here is a try to install Squeeze into Oracle VirtualBox 3.2.6. Virtual
  drive is 8.0 GB persistent, RAM 768 Mb, a virtual drive was partitioned
  by Squeeze installer with default settings (/, swap; ext3). Everything
  is fine, except for bootloader. There is a failure during GRUB (GRUB2,
  lilo) installation process: GRUB installation failed. The 'grub-pc'
  package failed to install into /target/.
 
  Also tried to partition a virtual hdd before Squeeze installation. No
  effect, bootloader installation failed also.
 
  Please, help to install a bootloader.
 
  I also had problems for installing GRUB (legacy) into VM using d-i
  (squeeze). I had to use SuperGrubDisk and proceed from there.

 Thanks for an idea. Tried both SGD and Debian Squeeze weekly build
 DVD-1 'Rescue Mode' with no success: apt-get reported there are no
 such files on the media. Actually they are in a proper place and
 sources.list is in order and contains that DVD as a valid repository.

  Indeed, installing GRUB in lenny was also problematic, IIRC. The first
  time always failed (red screen with error message: GRUB installation
  failed), and had to retry to get it properly installed :-?

 Yes, I confirm that. Another way to won was to pre-partition a target
 drive by LiveCD before an actual install.

 Have no clue on next step anyway. Tried Squeeze netinstall image on
 the same VirtualBox, it is not booting even.
 How to install Squeeze??
 --

 Sincerely Yours'
 Mark Goldshtein

I have had the same error in using Vbox  Squeeze. Since my goal was to have a 
single os vm I just installed lilo instead. Lilo was given as a choice when I 
said no to installing grub.

-- 
Peace,

Greg


--
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/201009151014.11817.gomadtr...@gci.net

Re: Squeeze. Failed to install bootloader in VirtualBox

[Mark Goldshtein]

On Wed, Sep 15, 2010 at 10:14 PM, Greg Madden gomadtr...@gci.net wrote:
 On Wednesday 15 September 2010 08:05:58 Mark Goldshtein wrote:
 On Wed, Sep 15, 2010 at 6:51 PM, Camaleón noela...@gmail.com wrote:
  On Wed, 15 Sep 2010 18:32:19 +0400, Mark Goldshtein wrote:
  Here is a try to install Squeeze into Oracle VirtualBox 3.2.6. Virtual
  drive is 8.0 GB persistent, RAM 768 Mb, a virtual drive was partitioned
  by Squeeze installer with default settings (/, swap; ext3). Everything
  is fine, except for bootloader. There is a failure during GRUB (GRUB2,
  lilo) installation process: GRUB installation failed. The 'grub-pc'
  package failed to install into /target/.
 
  Also tried to partition a virtual hdd before Squeeze installation. No
  effect, bootloader installation failed also.
 
  Please, help to install a bootloader.
 
  I also had problems for installing GRUB (legacy) into VM using d-i
  (squeeze). I had to use SuperGrubDisk and proceed from there.

 Thanks for an idea. Tried both SGD and Debian Squeeze weekly build
 DVD-1 'Rescue Mode' with no success: apt-get reported there are no
 such files on the media. Actually they are in a proper place and
 sources.list is in order and contains that DVD as a valid repository.

  Indeed, installing GRUB in lenny was also problematic, IIRC. The first
  time always failed (red screen with error message: GRUB installation
  failed), and had to retry to get it properly installed :-?

 Yes, I confirm that. Another way to won was to pre-partition a target
 drive by LiveCD before an actual install.

 Have no clue on next step anyway. Tried Squeeze netinstall image on
 the same VirtualBox, it is not booting even.
 How to install Squeeze??
 --

 Sincerely Yours'
 Mark Goldshtein

 I have had the same error in using Vbox  Squeeze. Since my goal was to have a
 single os vm I just installed lilo instead. Lilo was given as a choice when I
 said no to installing grub.


Just finished a fresh install. This time went through 'expert text
install' and have chosen a network mirror with possibly more actual
packages. Install process was smooth and clean, GRUB is in MBR now and
booting well.

Thanks to all for your help and support!


-- 

Sincerely Yours'
Mark Goldshtein


--
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/aanlktim4yyeumzkvceom2gz+kg5v_nfjejwx8-ani...@mail.gmail.com

why does a minimal lenny install want to use LILO as the bootloader?

[Robert P. J. Day]

  since i saved the output from dpkg --get-selections from the
previous install before reformatting the hard drive, i understood that
i could do a bare-bones install, then use dpkg --set-selections to
reproduce the package selection and install.

  so, just for fun, i deselected every selection in the package groups
list, and now i'm being asked about where i want to install LILO.
why?  if you choose to do a minimal install, is grub somehow
considered too fancy or optional?  that's just weird.  would selecting
one of those choices give me the grub option back again?

rday
--


Robert P. J. Day   Waterloo, Ontario, CANADA

Linux Consulting, Training and Annoying Kernel Pedantry.

Web page:  http://crashcourse.ca
Twitter:   http://twitter.com/rpjday



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: why does a minimal lenny install want to use LILO as the bootloader?

[Robert P. J. Day]

On Wed, 9 Sep 2009, Robert P. J. Day wrote:

   since i saved the output from dpkg --get-selections from the
 previous install before reformatting the hard drive, i understood
 that i could do a bare-bones install, then use dpkg
 --set-selections to reproduce the package selection and install.

   so, just for fun, i deselected every selection in the package
 groups list, and now i'm being asked about where i want to install
 LILO. why?  if you choose to do a minimal install, is grub somehow
 considered too fancy or optional?  that's just weird.  would
 selecting one of those choices give me the grub option back again?

  wait, i might have the answer, here:

http://linux.derkeiler.com/Mailing-Lists/Debian/2008-08/msg02319.html

except that i *did* make a separate, primary partition for /boot --
/dev/hda1, right at the front of the hard drive.  does it have to be
bootable?  is that what i might have forgotten?

rday
--


Robert P. J. Day   Waterloo, Ontario, CANADA

Linux Consulting, Training and Annoying Kernel Pedantry.

Web page:  http://crashcourse.ca
Twitter:   http://twitter.com/rpjday



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

bootloader

[mattias]

Kör dualboot med redhat enterprise på en disk med windows
Har olika vpser på en annan disk
Ihop med vpserna ligger en debian instalation
Som använder lilo som loader
Redhat kör grub
Går det att få grub att boota debian fast debian använder lilo
Hur skulle den raden i menu.lst se ut?



--
To UNSUBSCRIBE, email to debian-user-swedish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: bootloader

[Martin Bagge / brother]

On Tue, 1 Sep 2009, mattias wrote:


Kör dualboot med redhat enterprise på en disk med windows
Har olika vpser på en annan disk
Ihop med vpserna ligger en debian instalation
Som använder lilo som loader
Redhat kör grub
Går det att få grub att boota debian fast debian använder lilo
Hur skulle den raden i menu.lst se ut?


Antingen så kör du grub eller så kör du lilo. Du kan inte blanda då de 
genomför samma typ av funktion.


Baserat på att du vill köra grub så ska installationen av densamma i de 
allra flesta fall kunna hitta alla dina operativsystem automatiskt.


För att kunna ge dig rätt inställningar för menu.lst behöver vi veta 
diskstrukturen, vilket os som ligger på vilken partition osv alltså.

--
/brother
http://martin.bagge.nu
Bruce Schneier doesn't use a keylogger.  He's standing right behind you.


--
To UNSUBSCRIBE, email to debian-user-swedish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

SV: bootloader

[mattias]

Det va inte direkt så att ja valde lilo vid installationen av debian
Redhat ligger  på /dev/hda
Och debian på /dev/mj/debian

-Ursprungligt meddelande-
Från: Martin Bagge / brother [mailto:mar...@bagge.nu] 
Skickat: den 1 september 2009 21:43
Till: mattias
Kopia: debian-user-swedish@lists.debian.org
Ämne: Re: bootloader


On Tue, 1 Sep 2009, mattias wrote:

 Kör dualboot med redhat enterprise på en disk med windows
 Har olika vpser på en annan disk
 Ihop med vpserna ligger en debian instalation
 Som använder lilo som loader
 Redhat kör grub
 Går det att få grub att boota debian fast debian använder lilo Hur 
 skulle den raden i menu.lst se ut?

Antingen så kör du grub eller så kör du lilo. Du kan inte blanda då de 
genomför samma typ av funktion.

Baserat på att du vill köra grub så ska installationen av densamma i de 
allra flesta fall kunna hitta alla dina operativsystem automatiskt.

För att kunna ge dig rätt inställningar för menu.lst behöver vi veta 
diskstrukturen, vilket os som ligger på vilken partition osv alltså.
-- 
/brother
http://martin.bagge.nu
Bruce Schneier doesn't use a keylogger.  He's standing right behind you.



--
To UNSUBSCRIBE, email to debian-user-swedish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: bootloader

[Mats Klingberg]

Hej,

2009-09-01 21.29.12 skrev mattias:
 Kör dualboot med redhat enterprise på en disk med windows
 Har olika vpser på en annan disk
 Ihop med vpserna ligger en debian instalation
 Som använder lilo som loader
 Redhat kör grub
 Går det att få grub att boota debian fast debian använder lilo
 Hur skulle den raden i menu.lst se ut?

Det borde gå att ladda LILO från GRUB genom att använda chainloader, p.s.s. 
som när man vill boota windows:

rootnoverify (hd0,0)  # Byt ut till rätt disk/partition
makeactive  # Behövs eventuellt inte
chainloader +1

Å andra sidan borde GRUB kunna boota ditt debian direkt, t.ex:

root (hd0,0)
kernel sökväg-till-kernel root=/dev/xxx
initrd sökväg-till-initrd

Hälsningar,
Mats Klingberg




--
To UNSUBSCRIBE, email to debian-user-swedish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Installing an EFI bootloader on a non-bootable Lenny install (Intel Mac)?

[Kevin Ponds]

Hi,


I have an Intel Mac that was previously running Ubuntu in a singleboot
configuration (no rEFIt installed -- booting with whatever Ubuntu's default
boot method is, which appears to be grub with EFI support).

I attempted to migrate over to Lenny over the weekend, not even thinking
about whether or not it had stock EFI support.  I tried my standard install
method which is to use the netinst CD, tasksel nothing except for the base
system, and then pull in what I need with apt when the system boots.

Short version of the story is that after the install and load of grub, it
doesn't boot.  I'm under the impression that the stock Lenny install has a
version of grub that doesn't support EFI.  Unfortunately, all of the
documentation that I can find on how to install Debian on intel macs is
written from the perspective of having OSX already installed (and thus being
able to set up rEFIt from there).

So what I would like to do now is get this system booting, as it already has
Lenny installed on it, I think that getting a bootloader that supports EFI
installed and imaged into the MBR (or GUID? don't know a whole lot about
EFI, I assume the bootloader will sort this out for me.) will get me there.
I notice that there is a package in Lenny called grub-efi.

My question is: If I boot from a live CD, chroot into my Lenny install,
install grub-efi, and then run grub-update, will I be good?  Will grub.conf
or menu.lst changes be required? Is there anything else I have to watch out
for?

Is there already any supporting documentation for EFI systems which do not
have a bootable OS on them?  If not, maybe I could contribute something to
the wiki once I get this ironed out.


Thanks,

Kevin

Re: debootstrap and GRUB bootloader

[Osamu Aoki]

I may be wrong but ...

On Fri, Aug 15, 2008 at 04:28:03PM +0200, Urs Thuermann wrote:
 I want to build a Debian system using debootstrap and install that on
 a Compact Flash card for an x86 embedded system.
 
 I have created and mounted a fresh file system on a logical volume
 which I install the new Debian system into using debootstrap.  That
 works fine and I can chroot into the new system and install some more
 package using aptitude.  This is done by a simple shell script:
 
 #!/bin/sh
 mkfs  /dev/vg0/cu

So it is flat ext3 across flash.  Usualy, you parttion them like
harddisk and make filesystem on the first and only partition /dev/sda1.

Osamu


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

debootstrap and GRUB bootloader

[Urs Thuermann]

I want to build a Debian system using debootstrap and install that on
a Compact Flash card for an x86 embedded system.

I have created and mounted a fresh file system on a logical volume
which I install the new Debian system into using debootstrap.  That
works fine and I can chroot into the new system and install some more
package using aptitude.  This is done by a simple shell script:

#!/bin/sh
mkfs  /dev/vg0/cu
mount /dev/vg0/cu cu
debootstrap lenny cu
cp config/etc/hostname cu/etc
cp config/etc/fstabcu/etc
...
chroot cu EOF
mount /proc
mount /dev/pts
mount -t sysfs sysfs /sys
aptitude update
aptitude install -y -R iproute less wpasupplicant ferm tcpdump ppp \
pciutils openssh-{client,server} telnet ftp hdparm bridge-utils \
bzip2 file dnsutils dhcp3-server bind9 ntp ntpdate grub
umount /sys
umount /dev/pts
umount /proc
EOF

I then copy the file system image onto the Compact Flash card using dd

# umount /dev/vg0/cu
# dd if=/dev/vg0/cu of=/dev/sdb1

But then, installing the GRUB bootloader fails:

# mount /dev/sdb1 /mnt
# chroot /mnt
# mknod /dev/sdb  b 8 16
# mknod /dev/sdb1 b 8 17
# ls -A /boot
# grub-install /dev/sdb
Searching for GRUB installation directory ... found: /boot/grub
The file /boot/grub/stage1 not read correctly.
# ls -AF /boot
grub/
# ls -lAF /boot/grub 
total 212
-rw-r--r-- 1 root root197 Aug 15 14:15 default
-rw-r--r-- 1 root root 15 Aug 15 14:15 device.map
-rw-r--r-- 1 root root   8704 Aug 15 14:15 e2fs_stage1_5
-rw-r--r-- 1 root root   8544 Aug 15 14:15 fat_stage1_5
-rw-r--r-- 1 root root   9568 Aug 15 14:15 jfs_stage1_5
-rw-r--r-- 1 root root   7904 Aug 15 14:15 minix_stage1_5
-rw-r--r-- 1 root root  10720 Aug 15 14:15 reiserfs_stage1_5
-rw-r--r-- 1 root root512 Aug 15 14:15 stage1
-rw-r--r-- 1 root root 128616 Aug 15 14:15 stage2
-rw-r--r-- 1 root root  10280 Aug 15 14:15 xfs_stage1_5
# cat /boot/grub/device.map 
(hd0)   /dev/sdb
# 

So grub-install copies all stage* to /boot/grub and correctly creates
the devices.map file, but seems to have some problem with the stage1
bootloader.  I have also strace(1)ed the call to grub-install but
couldn't find out the problem.

I have also checked the MBR of /dev/sdb an there is no GRUB bootloader
installed.

So what can I do to complete the bootloader install?  What does the
error message

The file /boot/grub/stage1 not read correctly.

mean?  I think simply copying stage1 to /dev/sdb manually, i.e.

# dd if=/dev/stage1 of=/dev/sdb bs=446

won't work since, AFAIK, the MBR must contain the references (block
numbers) to the stage1_5 loaders.

urs


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Can not build Grub bootloader

[Carlos Bergero]

There is a problem with the files time and date, as the error message 
says. Check the directory files time and date with the command 'ls -l'
and the system time with 'date'. Then ensure to set times correctly use 
date to reset system time if necessary, 'man date' if you dont know how, 
and 'touch file-name' change the files times, also 'man touch' to know 
how to use it.
In any case u might wont to consider using grub packager 'apt-get 
install grub' or if u wont to build it grub-src, for which u have to 
change your /etc/apt/sources.list to add the src directorys.


Cheers,
rak

rocky escribió:

Hey,

I'm following the Pocket Linux Guide from www.tldp.org. I'm on the
section of build the GRUB bootloader

I downloaded the grup 0.95. export CC=gcc -mcpu=i386 does not give
any warning. But running configure stopped me from going on.

$-code begin--$
ronie:/usr/src/grub-0.95# ./configure --host=i386-pc-linux-gnu --
without-curses
configure: WARNING: If you wanted to set the --build type, don't use --
host.
If a cross compiler is detected then cross compile mode will be
used.
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... configure: error: newly
created file is older than distributed files!
Check your system clock
$-code end--$

I'm using Debian Etch which is the latest stable version. Can any of
you help me please?

Blessings,
Rocky





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Can not build Grub bootloader

[rocky]

Hey,

I'm following the Pocket Linux Guide from www.tldp.org. I'm on the
section of build the GRUB bootloader

I downloaded the grup 0.95. export CC=gcc -mcpu=i386 does not give
any warning. But running configure stopped me from going on.

$-code begin--$
ronie:/usr/src/grub-0.95# ./configure --host=i386-pc-linux-gnu --
without-curses
configure: WARNING: If you wanted to set the --build type, don't use --
host.
If a cross compiler is detected then cross compile mode will be
used.
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... configure: error: newly
created file is older than distributed files!
Check your system clock
$-code end--$

I'm using Debian Etch which is the latest stable version. Can any of
you help me please?

Blessings,
Rocky


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Möglichkeit Bootloader auf DOS Partion installieren?

[frank-gerhard]

Sehr geehrte Damen und Herren,

ich habe ein altes Petium II Notebook mit 300Mhz, 128MB Arbeitsspeicher und 
drei Festplattenpartionen. Eine 2GB (FAT32 formatiert) Festplattenpartion und 
log. Laufwerke mit je 1GB (ebenfalls FAT32 formatiert) auf der erweiteren 
Partition. Ich habe zwar die Möglichkeit eine Linuxvariante auf das zweite 
Logische Laufwerk zu installieren, jedoch kann ich mit meinem Notebook weder 
von dem Diskettenlaufwerk booten (Diskettenlaufwerk ist kaputt), noch kann ich 
von CD booten. Die bootfähigen CD's werden als solche nicht erkannt. Es bliebe 
mir nur die Möglichkeit ein Bootloader auf die erste Partion zu installieren 
und  so die Möglichkeit zu haben, neben dem Windows 98 Betriebssystem eine 
Linux-Variante über das CD-Laufwerk zu installieren. Natürlich erst wenn ich 
die entsprechenden CD's mit meinem noch älteren Pentium I mit 200 Mhz 
heruntergeladen hätte und auf dem seinen DVD-Brenner zu brennen. Kennen Sie 
eine Möglchkeit einen Bootloader für Linux auf eine Fat32 formatierte Partion 
zu installieren um so ein Linux-Betriebssystem über das CD Laufwerk zu 
installieren?

mfg
[EMAIL PROTECTED]

Re: Möglichkei t Bootloader auf DOS Partion installieren?

[Wolf Wiegand]

Hallo,

[EMAIL PROTECTED] wrote:

 Sehr geehrte Damen und Herren,
 
Du darfst ruhig 'Du' zu uns sagen :-)

 Kennen Sie eine Möglchkeit einen Bootloader für Linux auf eine Fat32 
 formatierte Partion zu installieren um so ein Linux-Betriebssystem 
 über das CD Laufwerk zu installieren?

Es gibt loadlin, damit kann man von DOS aus ein Linux booten. Wie man
allerdings damit eine Installation ausführt, kann ich auch nicht sagen.

Alternative Möglichkeiten:

- Festplatte ausbauen, in einen anderen Rechner hängen und dort die
  Installation durchführen.

- Falls der Rechner über das Netzwerk booten kann, auf einem anderen
  Rechner einen PXE-Server starten (bei Knoppix ist so weit ich weiß,
  alles dabei), und damit ein Linux starten.

Ohne ein bisschen Bastelei wird es wohl leider nicht gehen.

Viele Grüße,

  Wolf
-- 
Wenn Kinder ein Jahr alt sind, ist es, als würde man seine Zeit mit einem 
Betrunkenen im Mini-Format verbringen. Du musst sie festhalten. Sie lachen und 
weinen. Sie pinkeln. Sie kotzen. [Johnny Depp]


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Debian installieren, bootloader dabei auf USB-Stick installieren

[Christian Biermann]

Hallo,

ich möchte Debian auf einem Rechner installieren auf dem auch Windows XP läuft. 
Dabei will ich den Boot-loader (egal welchen) auf einen USB-Stick installieren, 
so dass der Rechner ohne eingesteckten USB-Stick ganz normal in XP bootet und 
mit eingestecktem USB Stick mir Windows oder Linux anbietet.

Ist das möglich und wenn ja wie? Bisherige Informationen im Internet verlangten 
immer einen bereits installierten bootloader (n dem fall Grub).

Vielen Dank,

Christian
-- 


Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: Debian installieren, bootloader dabei auf USB-Stick installieren

[Tobias Krais]

Hi Christian

 ich möchte Debian auf einem Rechner installieren auf dem auch Windows XP 
 läuft. Dabei will ich den Boot-loader (egal welchen) auf einen USB-Stick 
 installieren, so dass der Rechner ohne eingesteckten USB-Stick ganz normal in 
 XP bootet und mit eingestecktem USB Stick mir Windows oder Linux anbietet.
 
 Ist das möglich und wenn ja wie? Bisherige Informationen im Internet 
 verlangten immer einen bereits installierten bootloader (n dem fall Grub).

habs noch nicht ausprobiert, aber versuch mal bei der Installation den
USB-Stick schon eingesteckt zu haben und dann bei der GRUB-Installation
nicht /dev/hda anzugeben, sondern /dev/sda.

Grüßle, Tobias


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: Debian installieren, bootloader dabei auf USB-Stick installieren

[Christian Biermann]

Hallo Tobias,

vielen Dank für Deinen Vorschlag. Ich hatte es auf diese Art und Weise schon 
ausprobiert. Der USB Stick wird erkannt und lässt sich z.B. auch formatieren, 
jedoch gelang die Installation von Grub oder Lilo nicht. An die Fehlermeldung 
kann ich mich nicht mehr erinnern. Dazu müsste ich die Installation erneut 
durchführen. Wenn es Sinn macht, kann ich es wiederholen?

Viele Grüße,

Christian


 Original-Nachricht 
Datum: Thu, 17 Aug 2006 09:19:41 +0200
Von: Tobias Krais [EMAIL PROTECTED]
An: Debian Mailingliste debian-user-german@lists.debian.org
Betreff: Re: Debian installieren, bootloader dabei auf USB-Stick installieren

 Hi Christian
 
  ich möchte Debian auf einem Rechner installieren auf dem auch Windows
 XP läuft. Dabei will ich den Boot-loader (egal welchen) auf einen USB-Stick
 installieren, so dass der Rechner ohne eingesteckten USB-Stick ganz normal
 in XP bootet und mit eingestecktem USB Stick mir Windows oder Linux
 anbietet.
  
  Ist das möglich und wenn ja wie? Bisherige Informationen im Internet
 verlangten immer einen bereits installierten bootloader (n dem fall Grub).
 
 habs noch nicht ausprobiert, aber versuch mal bei der Installation den
 USB-Stick schon eingesteckt zu haben und dann bei der GRUB-Installation
 nicht /dev/hda anzugeben, sondern /dev/sda.
 
 Grüßle, Tobias
 
 
 -- 
 Haeufig gestellte Fragen und Antworten (FAQ): 
 http://www.de.debian.org/debian-user-german-FAQ/
 
 Zum AUSTRAGEN schicken Sie eine Mail an
 [EMAIL PROTECTED]
 mit dem Subject unsubscribe. Probleme? Mail an
 [EMAIL PROTECTED] (engl)

-- 


Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: GRUB bootloader issue

[Alvin Oga]

On Wed, 28 Sep 2005, H.S. wrote:

 Mike S wrote:
  Did you mount /boot first?
 
 umm, no, I don't recall so. I jotted down the steps I took and mounting
 /boot doesn't appear in those. My method worked properly on a laptop

*you* do NOT ( manually ) mount /boot or / or /usr or /var or /tmp or 
any other partition or directories

*the boot kernel* will mount what it needs when its ready to do
so by looking at the entries in /etc/fstab

/boot as a partition is NOT required on most machines if its
bios can handle booting from above 1024 cylinders
- or boot from floppy or cdrom or usb or network to avoid the
problem

if /boot is NOT defined in /etc/fstab, and you put your vmlinuz-2.6.x
kernel in /boot/vmlinuz-2.6.x, than your system will not boot properly

 trick question  for more thinking about how it boots 

if /boot/vmlinuz-2.6.x is what you want to boot, but /boot needs
to be mounted by vmlinuz-2.6.x, trick is which comes first ??

- the boot loader ( lilo, grub, loadlin, .. ) and boot sequence
magically figures it out for you before it turns control over
to avoid this silly catch-22

- this silly catch-22 is part of why grub needs to have its silly
stage-1.5 filesystem dependent files for ext3 or xfs or reiserfs

c ya
alvin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: GRUB bootloader issue

[Jay Zach]

Jeremy Merritt wrote:

I need help figuring out what is going on with my
Debian / GRUB bootloader. Because of some Windoze
issues, I had to re-install XP on my machine. It
discarded the grub loader and now you can only boot to
XP from hda1. I consulted with another Debian user who
said to simply run 'grub-install /dev/hda1' off of a
live CD. I tried that with hda, hda1, and hdb2 (debian
partition) just to be sure, and it gave the same error
every time. Here is an example of the error it gave.



[EMAIL PROTECTED]:/mnt/hdb2/sbin # grub-install /dev/hda1
Probing devices to guess BIOS drives. This may take
a long time.
Could not find device for /boot: Not found or not a
block device.



fdisk -l returns the following when run from the live
CD:

Disk /dev/hda: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 2433 19543041 7 HPFS/NTFS
/dev/hda2 2434 4865 19535040 5 Extended
/dev/hda5 2434 3197 6136798+ 83 Linux
/dev/hda6 3198 3337 1124518+ 82 Linux swap
/dev/hda7 3338 4865 12273628+ 83 Linux

Disk /dev/hdb: 61.4 GB, 61492838400 bytes
255 heads, 63 sectors/track, 7476 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdb1 1 3188 25607578+ c W95 FAT32 (LBA)
/dev/hdb2 * 3189 7298 33013575 83 Linux
/dev/hdb3 7299 7476 1429785 5 Extended
/dev/hdb5 7299 7476 1429753+ 82 Linux swap

Disk /dev/hdd: 30.0 GB, 30020272128 bytes
255 heads, 63 sectors/track, 3649 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdd1 * 1 3649 29310561 83 Linux

Any help is appreciated.



__ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com






There are some nice bootloaders on http://www.ultimatebootcd.com/ that I've used 
to boot up into my real linux system before to do rescue work.  It's easier 
than ch'rooting and all that ;)



--


BOFH excuse #158:

Defunct processes

Wednesday Sep 28, 2005




begin:vcard
fn:Jay Zach
n:Zach;Jay
org:CBI;IS
adr;dom:;;1500 N. Ritter;Indianapolis;IN
email;internet:[EMAIL PROTECTED]
title:NT Administrator
tel;work:(317) 355
tel;cell:(317) 339-3525
x-mozilla-html:FALSE
url:http://www.ecommunity.com
version:2.1
end:vcard

Re: GRUB bootloader issue

[H.S.]

Mike S wrote:
 Did you mount /boot first?

umm, no, I don't recall so. I jotted down the steps I took and mounting
/boot doesn't appear in those. My method worked properly on a laptop
which had Ubuntu and WinXP and my friend has lost Grub after installing
Windows. Got grub after following the steps I listed below. In his case
however, IIRC there was no separate partition for /boot -- so this may
be necessary after all.

-HS


 
 On 9/26/05, *H.S.* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
 
 Jeremy Merritt wrote:
  I need help figuring out what is going on with my
  Debian / GRUB bootloader. Because of some Windoze
  issues, I had to re-install XP on my machine. It
  discarded the grub loader and now you can only boot to
  XP from hda1. I consulted with another Debian user who
 
 
 Try this:
 Booted with a Live CD and have the desktop GUI on the screen
 
   1. Open a terminal or a command prompt window.
   2. Make a temporary directory somewhere where you will mount the root
 filesystem of Linux OS you have installed on your hard disk. For
 example,:
  $ mkdir /tmp/rootdir
   3. Mount the root filesystem (/) of your installed Linux OS. If your
 root filesystem was installed in /dev/hdaX, where X is the numer of
 partition of your hard disk, you will mount it as:
  $ sudo mount /dev/hdaX
  You may need to change the drive letter(hda or hdb or hdc ...)
 depending where you had installed the original Linux system.
   4. Change the root environment to your hard disk Linux system:
  $ chroot /tmp/rootdir
   5. Reinstall grub to the hard disk which is your first boot device.
 Assuming /dev/hda is your first boot device, you will give the following
 command:
  # grub-install /dev/hda
   6. After the command finished and shows no errors, reboot your
 machine (take care it does not reboot into your live CD again!).
 
 
 regards,
 -HS
 
 
 --
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 mailto:[EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact
 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
 
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: GRUB bootloader issue

[Roby]

Jeremy Merritt wrote:

 I tried that and it seemed to work. When I ran
 'grub-install /dev/hda5' it reported 'no errors' and
 seemed to execute successfully. However, upon reboot,
 I am back to XP bootup. Is there another step that I
 need to include?
 
 Steps so far:
 
 1. Boot up with live CD (Knoppix)
 2. Activate shell and go root
 3. Mount /dev/hda5 as /mnt/hda5
 4. chroot /mnt/hda5 /bin/bash
 5. grub-install /dev/hda5
 
(snip)

The MBR did not get updated: still points to XP.  I wonder whether live
Knoppix allows write access to the MBR.

I prefer to re-install MBR by booting grub from a floppy.  My Linux boot
partition is hda3, so:

grub root (hd0,2)
 Filesystem type is reiserfs, partition type 0x93
grub setup (hda)
grub reboot

This doesn't install grub, it just writes the MBR.  You could use 
grub root (hd1,x)
grub setup (hda)
if your grub boot files are in hdb(x+1).
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: GRUB bootloader issue

[Andy]

On Monday 26 September 2005 2:02, Roby wrote:
 Jeremy Merritt wrote:
  I tried that and it seemed to work. When I ran
  'grub-install /dev/hda5' it reported 'no errors' and
  seemed to execute successfully. However, upon reboot,
  I am back to XP bootup. Is there another step that I
  need to include?
 
  Steps so far:
 
  1. Boot up with live CD (Knoppix)
  2. Activate shell and go root
  3. Mount /dev/hda5 as /mnt/hda5
  4. chroot /mnt/hda5 /bin/bash
  5. grub-install /dev/hda5

almost.
1) Boot Knoppix
2) mount /dev/hdg2 to /mnt/hdg2 (this is /)
3) chroot ./hdg2
4) mount all linux partitions from the /etc/fstab from the chroot
5) make backup of /boot/grub
6) grub-install /dev/hda1

 (snip)

 The MBR did not get updated: still points to XP.  I wonder whether live
 Knoppix allows write access to the MBR.

Sorry if I'm being an idiot here but, if it didn't install the MBR, then how 
is it I'm now getting the grub menu on boot rather than the Windows boot 
loader list of OSs?

Just want to get things correct in my head before trying any of this. I don't 
want to lose the 1 working OS I have atm :)

Thanks,
Andy


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: GRUB bootloader issue

[Andy]

On Monday 26 September 2005 2:02, Roby wrote:
 Jeremy Merritt wrote:
  I tried that and it seemed to work. When I ran
  'grub-install /dev/hda5' it reported 'no errors' and
  seemed to execute successfully. However, upon reboot,
  I am back to XP bootup. Is there another step that I
  need to include?
 
  Steps so far:
 
  1. Boot up with live CD (Knoppix)
  2. Activate shell and go root
  3. Mount /dev/hda5 as /mnt/hda5
  4. chroot /mnt/hda5 /bin/bash
  5. grub-install /dev/hda5

 (snip)

Oops, looks like I posted to the wrong thread, ignore me. Sorry guys :(

Andy


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: GRUB bootloader issue

[H.S.]

Jeremy Merritt wrote:
 I need help figuring out what is going on with my
 Debian / GRUB bootloader. Because of some Windoze
 issues, I had to re-install XP on my machine. It
 discarded the grub loader and now you can only boot to
 XP from hda1. I consulted with another Debian user who


Try this:
Booted with a Live CD and have the desktop GUI on the screen

   1. Open a terminal or a command prompt window.
   2. Make a temporary directory somewhere where you will mount the root
filesystem of Linux OS you have installed on your hard disk. For example,:
  $ mkdir /tmp/rootdir
   3. Mount the root filesystem (/) of your installed Linux OS. If your
root filesystem was installed in /dev/hdaX, where X is the numer of
partition of your hard disk, you will mount it as:
  $ sudo mount /dev/hdaX
  You may need to change the drive letter(hda or hdb or hdc ...)
depending where you had installed the original Linux system.
   4. Change the root environment to your hard disk Linux system:
  $ chroot /tmp/rootdir
   5. Reinstall grub to the hard disk which is your first boot device.
Assuming /dev/hda is your first boot device, you will give the following
command:
  # grub-install /dev/hda
   6. After the command finished and shows no errors, reboot your
machine (take care it does not reboot into your live CD again!).


regards,
-HS


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: GRUB bootloader issue

[Mike S]

Did you mount /boot first?
On 9/26/05, H.S. [EMAIL PROTECTED] wrote:
Jeremy Merritt wrote: I need help figuring out what is going on with my Debian / GRUB bootloader. Because of some Windoze
 issues, I had to re-install XP on my machine. It discarded the grub loader and now you can only boot to XP from hda1. I consulted with another Debian user whoTry this:Booted with a Live CD and have the desktop GUI on the screen
1. Open a terminal or a command prompt window.2. Make a temporary directory somewhere where you will mount the rootfilesystem of Linux OS you have installed on your hard disk. For example,: $ mkdir /tmp/rootdir
3. Mount the root filesystem (/) of your installed Linux OS. If yourroot filesystem was installed in /dev/hdaX, where X is the numer ofpartition of your hard disk, you will mount it as: $ sudo mount /dev/hdaX
 You may need to change the drive letter(hda or hdb or hdc ...)depending where you had installed the original Linux system.4. Change the root environment to your hard disk Linux system: $ chroot /tmp/rootdir
5. Reinstall grub to the hard disk which is your first boot device.Assuming /dev/hda is your first boot device, you will give the followingcommand: # grub-install /dev/hda6. After the command finished and shows no errors, reboot your
machine (take care it does not reboot into your live CD again!).regards,-HS--To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

GRUB bootloader issue

[Jeremy Merritt]

I need help figuring out what is going on with my
Debian / GRUB bootloader. Because of some Windoze
issues, I had to re-install XP on my machine. It
discarded the grub loader and now you can only boot to
XP from hda1. I consulted with another Debian user who
said to simply run 'grub-install /dev/hda1' off of a
live CD. I tried that with hda, hda1, and hdb2 (debian
partition) just to be sure, and it gave the same error
every time. Here is an example of the error it gave.

 [EMAIL PROTECTED]:/mnt/hdb2/sbin # grub-install /dev/hda1
 Probing devices to guess BIOS drives. This may take
 a long time.
 Could not find device for /boot: Not found or not a
 block device.

fdisk -l returns the following when run from the live
CD:

Disk /dev/hda: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 2433 19543041 7 HPFS/NTFS
/dev/hda2 2434 4865 19535040 5 Extended
/dev/hda5 2434 3197 6136798+ 83 Linux
/dev/hda6 3198 3337 1124518+ 82 Linux swap
/dev/hda7 3338 4865 12273628+ 83 Linux

Disk /dev/hdb: 61.4 GB, 61492838400 bytes
255 heads, 63 sectors/track, 7476 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdb1 1 3188 25607578+ c W95 FAT32 (LBA)
/dev/hdb2 * 3189 7298 33013575 83 Linux
/dev/hdb3 7299 7476 1429785 5 Extended
/dev/hdb5 7299 7476 1429753+ 82 Linux swap

Disk /dev/hdd: 30.0 GB, 30020272128 bytes
255 heads, 63 sectors/track, 3649 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdd1 * 1 3649 29310561 83 Linux

Any help is appreciated.



__ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: GRUB bootloader issue

[Malcolm Lalkaka]

/dev/hda1 seems to be an NTFS filesystem (at least that's what fdisk
says). I'm not sure about this, but may it have to be a Linux
filesystem (e.g. ext3) in order for grub to work with it. I may be
wrong about this, so take it with a grain of salt.

Also, it seems that all of your hard drives, (hda, hdb, and hdd) have
a partition that is marked as a boot partition. I believe that you can
have only one boot partition, even if you have multiple drives. At
least that is how it is on my system.

Hope this helps,
Malcolm
 mlalkaka [at] gmail.com 
-

On 9/25/05, Jeremy Merritt [EMAIL PROTECTED] wrote:
 I need help figuring out what is going on with my
 Debian / GRUB bootloader. Because of some Windoze
 issues, I had to re-install XP on my machine. It
 discarded the grub loader and now you can only boot to
 XP from hda1. I consulted with another Debian user who
 said to simply run 'grub-install /dev/hda1' off of a
 live CD. I tried that with hda, hda1, and hdb2 (debian
 partition) just to be sure, and it gave the same error
 every time. Here is an example of the error it gave.

  [EMAIL PROTECTED]:/mnt/hdb2/sbin # grub-install /dev/hda1
  Probing devices to guess BIOS drives. This may take
  a long time.
  Could not find device for /boot: Not found or not a
  block device.

 fdisk -l returns the following when run from the live
 CD:

 Disk /dev/hda: 40.0 GB, 40020664320 bytes
 255 heads, 63 sectors/track, 4865 cylinders
 Units = cylinders of 16065 * 512 = 8225280 bytes

 Device Boot Start End Blocks Id System
 /dev/hda1 * 1 2433 19543041 7 HPFS/NTFS
 /dev/hda2 2434 4865 19535040 5 Extended
 /dev/hda5 2434 3197 6136798+ 83 Linux
 /dev/hda6 3198 3337 1124518+ 82 Linux swap
 /dev/hda7 3338 4865 12273628+ 83 Linux

 Disk /dev/hdb: 61.4 GB, 61492838400 bytes
 255 heads, 63 sectors/track, 7476 cylinders
 Units = cylinders of 16065 * 512 = 8225280 bytes

 Device Boot Start End Blocks Id System
 /dev/hdb1 1 3188 25607578+ c W95 FAT32 (LBA)
 /dev/hdb2 * 3189 7298 33013575 83 Linux
 /dev/hdb3 7299 7476 1429785 5 Extended
 /dev/hdb5 7299 7476 1429753+ 82 Linux swap

 Disk /dev/hdd: 30.0 GB, 30020272128 bytes
 255 heads, 63 sectors/track, 3649 cylinders
 Units = cylinders of 16065 * 512 = 8225280 bytes

 Device Boot Start End Blocks Id System
 /dev/hdd1 * 1 3649 29310561 83 Linux

 Any help is appreciated.

Re: GRUB bootloader issue

[Roby]

Jeremy Merritt wrote:

 I need help figuring out what is going on with my
 Debian / GRUB bootloader. Because of some Windoze
 issues, I had to re-install XP on my machine. It
 discarded the grub loader and now you can only boot to
 XP from hda1. I consulted with another Debian user who
 said to simply run 'grub-install /dev/hda1' off of a
 live CD. I tried that with hda, hda1, and hdb2 (debian
 partition) just to be sure, and it gave the same error
 every time. Here is an example of the error it gave.
 
 [EMAIL PROTECTED]:/mnt/hdb2/sbin # grub-install /dev/hda1
 Probing devices to guess BIOS drives. This may take
 a long time.
 Could not find device for /boot: Not found or not a
 block device.
 
 fdisk -l returns the following when run from the live
 CD:
 
 Disk /dev/hda: 40.0 GB, 40020664320 bytes
 255 heads, 63 sectors/track, 4865 cylinders
 Units = cylinders of 16065 * 512 = 8225280 bytes
 
 Device Boot Start End Blocks Id System
 /dev/hda1 * 1 2433 19543041 7 HPFS/NTFS
 /dev/hda2 2434 4865 19535040 5 Extended
 /dev/hda5 2434 3197 6136798+ 83 Linux
 /dev/hda6 3198 3337 1124518+ 82 Linux swap
 /dev/hda7 3338 4865 12273628+ 83 Linux
 
 Disk /dev/hdb: 61.4 GB, 61492838400 bytes
 255 heads, 63 sectors/track, 7476 cylinders
 Units = cylinders of 16065 * 512 = 8225280 bytes
 
 Device Boot Start End Blocks Id System
 /dev/hdb1 1 3188 25607578+ c W95 FAT32 (LBA)
 /dev/hdb2 * 3189 7298 33013575 83 Linux
 /dev/hdb3 7299 7476 1429785 5 Extended
 /dev/hdb5 7299 7476 1429753+ 82 Linux swap
 
 Disk /dev/hdd: 30.0 GB, 30020272128 bytes
 255 heads, 63 sectors/track, 3649 cylinders
 Units = cylinders of 16065 * 512 = 8225280 bytes
 
 Device Boot Start End Blocks Id System
 /dev/hdd1 * 1 3649 29310561 83 Linux
 
 Any help is appreciated.
 
Hi Jeremy!

fdisk says hda2 is an extended partition that contains three Linux
partitions.  My *guess* is that your boot partition is hda5 and that's
probably where grub is hiding.

Roby


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: GRUB bootloader issue

[Alan Ianson]

On Sun September 25 2005 04:32 pm, Jeremy Merritt wrote:
 I need help figuring out what is going on with my
 Debian / GRUB bootloader. Because of some Windoze
 issues, I had to re-install XP on my machine. It
 discarded the grub loader and now you can only boot to
 XP from hda1. I consulted with another Debian user who
 said to simply run 'grub-install /dev/hda1' off of a
 live CD. I tried that with hda, hda1, and hdb2 (debian
 partition) just to be sure, and it gave the same error
 every time. Here is an example of the error it gave.

That happened to me before too. I had to boot a live cd and chroot into the 
partition that contains the /boot directory and then grub-install /dev/hda.
I think something along the lines of chroot /dev/hda5 /bin/bash will get you 
where you need to be.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: GRUB bootloader issue

[Jeremy Merritt]

I tried that and it seemed to work. When I ran
'grub-install /dev/hda5' it reported 'no errors' and
seemed to execute successfully. However, upon reboot,
I am back to XP bootup. Is there another step that I
need to include?

Steps so far:

1. Boot up with live CD (Knoppix)
2. Activate shell and go root
3. Mount /dev/hda5 as /mnt/hda5
4. chroot /mnt/hda5 /bin/bash
5. grub-install /dev/hda5

Thanks for any input.

Note: hda5 is actually a Mandrake partition. hdb2 and
other hdb(x) Linux is Debian. But I realize, to get
this to work, it will somehow involve grub-install
hda(x).

--- Alan Ianson [EMAIL PROTECTED] wrote:

 On Sun September 25 2005 04:32 pm, Jeremy Merritt
 wrote:
  I need help figuring out what is going on with my
  Debian / GRUB bootloader. Because of some Windoze
  issues, I had to re-install XP on my machine. It
  discarded the grub loader and now you can only
 boot to
  XP from hda1. I consulted with another Debian user
 who
  said to simply run 'grub-install /dev/hda1' off of
 a
  live CD. I tried that with hda, hda1, and hdb2
 (debian
  partition) just to be sure, and it gave the same
 error
  every time. Here is an example of the error it
 gave.
 
 That happened to me before too. I had to boot a live
 cd and chroot into the 
 partition that contains the /boot directory and then
 grub-install /dev/hda.
 I think something along the lines of chroot
 /dev/hda5 /bin/bash will get you 
 where you need to be.
 
 
 -- 
 To UNSUBSCRIBE, email to
 [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact
 [EMAIL PROTECTED]
 
 




__ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bootloader produces garbage - reconstructing MBR

[Haines Brown]

[Sorry if some of you are reading this message a second time. I was
not gated to the list properly, and this is a resend to the list
itself rather than newsgroup.]

Booting a scsi hd results in garbage after the scsi adapter's device
scan.

I have three scsi hard disks: sda, sdb, and sdc. My grub bootloader is
in sda MBR, and it is used to boot sda (disk not otherwise used), sdc
(my running system) or sdb (an emergency/utility disk).

It happened that I could no longer mount my ide cdrom or my scsi cdrom
drives, and in investigating this (no ide1 reported in dmesg) I found
that I could no longer boot using the bootloader in sda MBR:
Immediately after my Adaptec adapter scans the scsi devices, the boot
process hangs with the display of garbage characters.

If I boot each disk by itself with all other scsi devices
disconnected, I boot to garbage with sda, but sdb and sdc boot to a
blinking cursor after the scsi device scan. My sdb lilo loader has not
been used for a couple years, and my sdc grub loader has never been
tested, and I assume the blinking cursor is only a boot loader
configuration issue of lesser concern right now and unrelated to
difficulty getting the sda bootloader to work.

I can boot all three disks from a grub boot floppy, which I assume
narrows things down to what's in the sda MBR rather than a hardware
problem.

My current return for dmesg does not show a hardware problem either as
far as I can make out. I have put it on line at:
http//www.hartford-hwp.com/sandbox/dmesg.html

I copied (dd) the MBR on sda and sdc to img files. Being binary files,
I could not get diff to tell me anything more than that they differed,
but they are the same size (is any of this meaningful?). I couldn't
see any difference between when viewing them with beav. Although the
two hard disks are very similar (both are Hitachi/IBM, 36Gb, U160, but
sda is 10k rpm and sdc is 15k rpm). The operating systems are both
sarge, but use different kernels. I worry that I was not booting the
system I thought I was, and it is possible the two img files are the
same sdc file. But as I've described the situation, are not the two
files likely to be identical?

I need to do a MBR check, repair or restoration. Is there any
alternative (for a person of limited expertise) but to wipe it out and
start afresh? If there's evidence of corruption, which I assume the
gargage implies, is a wipe-out the only way to proceed?

To wipe the MBR clean, I read of doing # fdisk /MBR. However, there's
no reference to that option in man fdisk. Is it a good way to wipe out
the MBR so that it can be reconstructed? Other than making the disk
unbootable from its bootloader, which is already the case, are there
any particular dangers doing this?

Or should I simply overwrite the MBR with a new install of grub, which
I assume simply means doing grub root and grub setup.

-- 
 
   Haines Brown
   KB1GRM   


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Bootloader produces garbage - reconstructing MBR

[Alvin Oga]

On Sun, 3 Jul 2005, Haines Brown wrote:

 It happened that I could no longer mount my ide cdrom or my scsi cdrom
 drives

that is a simple kernel option problem
- fix lilo/grub config files
- manually installt he modules manuall

 I can boot all three disks from a grub boot floppy, which I assume
 narrows things down to what's in the sda MBR rather than a hardware
 problem.

good.. says grub's MBR on the floppy is correct
 
 I copied (dd) the MBR on sda and sdc to img files. Being binary files,

how exactly was the dd command ??

dd if=/dev/fd0 of=/dev/sda bs=448 count=1

any other dd command is WRONG

- NEVER copy binary files from xx to yy versions

 I could not get diff to tell me anything more than that they differed,

duh... why should it be the same

-- use the latest grub via cvs from gnu.org

 I need to do a MBR check, repair or restoration.
..
 To wipe the MBR clean, I read of doing # fdisk /MBR.

wipe it ( fdisk /mbr or dd if=/dev/null of=/dev/sda bs=448 count=1 )
and rerun lilo or grub

 Other than making the disk
 unbootable from its bootloader, which is already the case, are there
 any particular dangers doing this?

you dont need to worry.. you ahve a working boot floppy...
save it as it.. forever

 I assume simply means doing grub root and grub setup.

grub-install /dev/sda
or
grub-install /des/db
...

c ya
alvin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [OT]: co to ten tudzież (Było: Re: Graficzny Bootloader)

[Lech Karol Pawłaszek]

Dnia poniedziaek, 31 stycznia 2005 10:46, Marek Zakowicz napisa:
[...]
 Wg wspomnianego przez Ciebie sownika, onegdaj znaczy przedwczoraj
 (http://sjp.pwn.pl/haslo.php?id=40266).  Nie zauwayem by w cigu
 ostatniego tygodnia porusza na tej grupie czy to kwesti tudzie, czy
 te innych zabytkw naszego jzyka...
[...]

Tak. Dokadnie chodzio mi o przedwczoraj. Tylko nigdzie nie wspomniaem, 
e 
zauwayem ten bd na d-u-p. To mia by przykad tego geometrycznego 
wzrostu.

Hm. Wtek jest cakowicie OT, wic przenosi si w czeluci rozmw 
prywatnych... 

Pozdrawiam.

-- 
Lech Karol Pawaszek ike
You will never see me fall from grace... [KoRn]

Re: Graficzny Bootloader

[Lech Karol Pawłaszek]

Dnia pitek, 28 stycznia 2005 20:32, Robert Moka napisa:
 Dnia 28-01-2005, pi o godzinie 20:16 +0100, Wojciech Ziniewicz
[..]
  debian logo ? tudzie wanie bootsplash ? :| nie wiemm :|

Mam nadziej, e wiesz znaczenie sowa tudzie (czyli spjnik oznaczajcy 
dokadnie to samo co i ;-)

 Cakowicie graficzne menu gruba. Wiksze litery, dodatkowe menu na dole
 z moliwoci wyboru np. konkretnej wersji jzykowej. Wszystko
 dziaajce z mysz. Jasny gwint... niech kto mi pomoe i podrzuci linka
 do screena.

screen'a nie mam, ale moe chodzi Ci o PUPA ? ;]

http://www.nongnu.org/pupa/
http://gnu.open-mirror.com/software/grub/grub.html#GRUB2

-- 
Lech Karol Pawaszek ike
You will never see me fall from grace... [KoRn]

Re: Graficzny Bootloader

[Wojciech Ziniewicz]

On Sat, 29 Jan 2005 17:15:56 +0100, Lech Karol Pawaszek
[EMAIL PROTECTED] wrote:
 Dnia pitek, 28 stycznia 2005 20:32, Robert Moka napisa:
  Dnia 28-01-2005, pi o godzinie 20:16 +0100, Wojciech Ziniewicz
 [..]
   debian logo ? tudzie wanie bootsplash ? :| nie wiemm :|
 
 Mam nadziej, e wiesz znaczenie sowa tudzie (czyli spjnik 
 oznaczajcy
 dokadnie to samo co i ;-)
maso malane. ale tudzie nie oznacza dokdnie tego samego co i
:) nie kmy si jednak o spjniki aczkolwiek , jednak, co wicej
,eby nie popa w niepotrzebne spory :PPP

-- 
Pozdrawiam, Wojciech Ziniewicz
Powered by google.com 
[EMAIL PROTECTED]
#gg 6583979

[OT]: co to ten tudzież (Było: Re: Graficzny Bootloader)

[Lech Karol Pawłaszek]

Dnia sobota, 29 stycznia 2005 22:21, Wojciech Ziniewicz napisa:
[...]
debian logo ? tudzie wanie bootsplash ? :| nie wiemm :|
 
  Mam nadziej, e wiesz znaczenie sowa tudzie (czyli spjnik 
  oznaczajcy
  dokadnie to samo co i ;-)

 maso malane. ale tudzie nie oznacza dokdnie tego samego co i

 :) nie kmy si jednak o spjniki aczkolwiek , jednak, co wicej

 ,eby nie popa w niepotrzebne spory :PPP

No to jeszcze raz.
http://sjp.pwn.pl/haslo.php?id=63334

Nie mczybym listy takimi problemami, gdyby nie to, e ostatnio zauwaam 
geometrycznie rosnc tendencj do uywania tego sowa.

Onegdaj ju zwracaem uwag jednej osobie.

Ja lubi nowe sowa i zawdy chtnie sigaem po nowe sowa, lecz lepiej 
wiedzie co si mwi, prawda?

C. Lec na wieczorne ablucje.

Pozdrawiam. ;-)

-- 
Lech Karol Pawaszek ike
You will never see me fall from grace... [KoRn]

Re: Graficzny Bootloader

[Wojciech Ziniewicz]

On Fri, 28 Jan 2005 11:50:47 +0100, Bartosz Gogel [EMAIL PROTECTED] wrote:
 
 
 
  Moe chodzi o co takiego ?
  http://www.debianusers.pl/article.php?aid=67
 
 
 wanie, nawet nie wiedziaem czego szukac, dziki za pomoc

http://www.bootsplash.de 

-- 
Pozdrawiam, Wojciech Ziniewicz
Powered by google.com 
[EMAIL PROTECTED]
#gg 6583979

Re: Graficzny Bootloader

[Paweł Tęcza]

On Fri, Jan 28, 2005 at 01:06:30PM +0100, Wojciech Ziniewicz wrote:
 On Fri, 28 Jan 2005 11:50:47 +0100, Bartosz Gogel [EMAIL PROTECTED] wrote:
[...]
  wanie, nawet nie wiedziaem czego szukac, dziki za pomoc
 
 http://www.bootsplash.de 

To ja jeszcze zarzuce jednym linkiem, a co :)

http://debblue.debian.net/

P.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Graficzny Bootloader

[Krzysztof Zubik]

Robert Moka napisa.
 Dnia 28-01-2005, pi o godzinie 13:10 +0100, Pawe Tcza napisa(a):
  On Fri, Jan 28, 2005 at 01:06:30PM +0100, Wojciech Ziniewicz wrote:
   On Fri, 28 Jan 2005 11:50:47 +0100, Bartosz Gogel [EMAIL PROTECTED] 
   wrote:
wanie, nawet nie wiedziaem czego szukac, dziki za pomoc
   http://www.bootsplash.de
  To ja jeszcze zarzuce jednym linkiem, a co :)
  http://debblue.debian.net/
 A moe wiecie jak uzyska cakowicie graficznego gruba. Nie chodzi mi o
 wstawienie bitmapy tak jak http://debblue.debian.net/, tylko o co
 takiego jak pojawia si przy starcie choby nowego Suse LiveCD albo
 Gnoppixa? Nie znalazem nigdzie screena.
Witam.
Juz myslalem, ze pomylka, a jednak juz po konsultacji z niejakimi
googlami przekonalem sie,ze od niedawna mamy kolejne distro.
http://www.google.pl/linux?hl=plq=GnoppixbtnG=Szukaj+z+Googlelr=
Linux w wyniku bardzo dynamicznego rozwoju wyglada coraz ciekawiej.
-- 
Konczac Pozdrawiam. Krzysztof.

Registered Linux User: 253243 | Powered by Aurox 9.0
Krzysztof Zubik. | [EMAIL PROTECTED] | [EMAIL PROTECTED]
http://www.idn.org.pl/users/kzubik
GaduGadu. 1208376 | Jabber. [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Grub-Bootloader wiederherstellen

[Peter Schtt]

Hallo,

 ich habe auf einem System, wo Win98 und Debian, Kernel 2.4, parallel
 installiert wurde, Win98 neu installiert.

Win98 ist jetzt nicht mehr in c:\win98 sondern in c:\windows.

 Jetzt ist natürlich der BootLoader weg, was ich vorher leider vergaß.
 
 Wie kann ich den am einfachsten wieder herstellen?
 
[..]
 Solltest du nicht reinkommen, dann empfehle ich dir Knoppix o.ä. zu
 booten, die partition zu mounten
 mkdir /tmp/chroot
 mount /dev/[hs]da /tmp/chroot -o rw
 chroot /tmp/chroot
 grub-install /dev/hda

habe ich so gemacht:
/dev/hda1 ist Windows
/dev/hda2 ist Linux-Root

mount /dev/hda1 /mnt/hda1 -o rw
mount /dev/hda2 /mnt/hda2 -o rw
chroot /mnt/hda2
grub-install /dev/hda1

Nun erscheint das alte Boot-Menü wieder und ich kann auch von Linux auf
die Windows-Partition (via fstab gemounted) zugreifen.

Wenn ich aber boote, dann erscheint im grub-Menu Windows, aber er startet
kein Windows.
Er zeigt nur die Daten aus der menu.lst an:

title  Windows 98
root  (hd0,0)
makeactive
chainloader +1

und kehrt dann zum Boot-Menü zurück.

Bevor ich mittels grub-install den MBR wieder hergestellt habe,
bootete Windows ganz normal.

Hat jemand eine Idee?

TIA

Ciao
  Peter Schütt

-- 
www.pstt.de


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: Grub-Bootloader wiederherstellen

[Andreas Pakulat]

On 07.Jan 2005 - 16:59:09, Peter Schütt wrote:
 Hallo,
  Solltest du nicht reinkommen, dann empfehle ich dir Knoppix o.ä. zu
  booten, die partition zu mounten
  mkdir /tmp/chroot
  mount /dev/[hs]da /tmp/chroot -o rw
  chroot /tmp/chroot
  grub-install /dev/hda
 
 habe ich so gemacht:
 /dev/hda1 ist Windows
 /dev/hda2 ist Linux-Root
 
 mount /dev/hda1 /mnt/hda1 -o rw

Das ist unnötig.

 mount /dev/hda2 /mnt/hda2 -o rw
 chroot /mnt/hda2
 grub-install /dev/hda1
  ^^

Das war ein Fehler, damit hast du Windows Bootsektor zerstört. Ich
weiss nicht ob Windows98 da Tools mitgebracht hat um den
wiederherzustellen... 

 Wenn ich aber boote, dann erscheint im grub-Menu Windows, aber er startet
 kein Windows.

Weil es keinen Bootsektor mehr für Windows gibt. Installiere den Grub
in /dev/hda nachdem du mit Windows-Tools dessen Bootsektor repariert
hast.

IIRC geht reparieren durch: Booten von Windows-CD und anschliessendes
sys a: c:

Danach musst du die Knoppix wieder reinschieben und grub installieren
(aber diesmal in hda und nicht hda1)

Andreas

-- 
Your temporary financial embarrassment will be relieved in a surprising manner.


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: Grub-Bootloader wiederherstellen

[Christian Brehm]

Ich hab den Anfang des Problems leider nicht mitgekriegt, aber wenn ich 
recht weiß kannst Du den Win Bootloader wiederherstellen, indem Du mit 
der Installations CD bootest und dann fixmbr eingibst, falls Dir das 
weiterhilft. Ohne Garantie, ist lange her, daß ich sowas gemacht habe.

Gruß
Christian
Andreas Pakulat schrieb:
On 07.Jan 2005 - 16:59:09, Peter Schütt wrote:
Hallo,
Solltest du nicht reinkommen, dann empfehle ich dir Knoppix o.ä. zu
booten, die partition zu mounten
mkdir /tmp/chroot
mount /dev/[hs]da /tmp/chroot -o rw
chroot /tmp/chroot
grub-install /dev/hda
habe ich so gemacht:
/dev/hda1 ist Windows
/dev/hda2 ist Linux-Root
mount /dev/hda1 /mnt/hda1 -o rw

Das ist unnötig.

mount /dev/hda2 /mnt/hda2 -o rw
chroot /mnt/hda2
grub-install /dev/hda1
  ^^
Das war ein Fehler, damit hast du Windows Bootsektor zerstört. Ich
weiss nicht ob Windows98 da Tools mitgebracht hat um den
wiederherzustellen... 


Wenn ich aber boote, dann erscheint im grub-Menu Windows, aber er startet
kein Windows.

Weil es keinen Bootsektor mehr für Windows gibt. Installiere den Grub
in /dev/hda nachdem du mit Windows-Tools dessen Bootsektor repariert
hast.
IIRC geht reparieren durch: Booten von Windows-CD und anschliessendes
sys a: c:
Danach musst du die Knoppix wieder reinschieben und grub installieren
(aber diesmal in hda und nicht hda1)
Andreas

--
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: Grub-Bootloader wiederherstellen

[Andreas Pakulat]

On 07.Jan 2005 - 18:58:02, Christian Brehm wrote:
 Ich hab den Anfang des Problems leider nicht mitgekriegt,

Nicht nur den:

1. Bitte kein CC an mich ich lese die Liste mit

2. Bitte ToFu abstellen, das ist schlecht lesbar und erhöht das
Datenaufkommen (http://learn.to/quote)

 aber wenn ich 
 recht weiß kannst Du den Win Bootloader wiederherstellen, indem Du mit 
 der Installations CD bootest und dann fixmbr eingibst, falls Dir das 
 weiterhilft. Ohne Garantie, ist lange her, daß ich sowas gemacht habe.

Also Win98 ist auch schon ne Weile her, aber IIRC hatte es kein fixmbr
oder fixboot. Das gabs nur bei Win2K und XP (vielleicht auch ME ode
NT aber die kenn ich nun gar nicht)

Andreas

-- 
Increased knowledge will help you now.  Have mate's phone bugged.


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: Grub-Bootloader wiederherstellen

[Hans-Martin Flesch]

Andreas Pakulat schrieb:
On 07.Jan 2005 - 18:58:02, Christian Brehm wrote:
aber wenn ich 
recht weiß kannst Du den Win Bootloader wiederherstellen, indem Du mit 
der Installations CD bootest und dann fixmbr eingibst, falls Dir das 
weiterhilft. Ohne Garantie, ist lange her, daß ich sowas gemacht habe.

Also Win98 ist auch schon ne Weile her, aber IIRC hatte es kein fixmbr
oder fixboot. Das gabs nur bei Win2K und XP (vielleicht auch ME ode
NT aber die kenn ich nun gar nicht)
Bei WIN98 hilft ein fdisk /mbr um den Masterbootrecord wieder herzustellen..
Martin
--
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Grub-Bootloader wiederherstellen

[Peter Schtt]

Hallo,
ich habe auf einem System, wo Win98 und Debian, Kernel 2.4, parallel
installiert wurde, Win98 neu installiert.
Jetzt ist natürlich der BootLoader weg, was ich vorher leider vergaß.

Wie kann ich den am einfachsten wieder herstellen?

TIA

Ciao
  Peter Schütt

-- 
www.pstt.de


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: Grub-Bootloader wiederherstellen

[Martin Theiss]

Hi Peter Schütt, *,

Peter Schütt wrote:

 Hallo,
 ich habe auf einem System, wo Win98 und Debian, Kernel 2.4, parallel
 installiert wurde, Win98 neu installiert.
 Jetzt ist natürlich der BootLoader weg, was ich vorher leider vergaß.
 
 Wie kann ich den am einfachsten wieder herstellen?

Wenn du in dein Linux wieder rein kommst, dann reicht als root
grub-install /dev/hda
bzw.
grub-install /dev/sda

Solltest du nicht reinkommen, dann empfehle ich dir Knoppix o.ä. zu booten,
die partition zu mounten
mkdir /tmp/chroot
mount /dev/[hs]da /tmp/chroot -o rw
chroot /tmp/chroot
grub-install /dev/hda

Gruss
Martin

-- 
Martin Theiss [EMAIL PROTECTED]
Primary key fingerprint: EC80 53A2 F0A2 6E6C 74D2  CB6E 002A F6D3 E78B 7F45

The box said 'Requires Windows 95 or better', so I installed Linux - TKK 5


signature.asc
Description: Digital signature

Re: Grub-Bootloader wiederherstellen

[Andreas Pakulat]

On 05.Jan 2005 - 18:00:21, Peter Schütt wrote:
 Hallo,
 ich habe auf einem System, wo Win98 und Debian, Kernel 2.4, parallel
 installiert wurde, Win98 neu installiert.
 Jetzt ist natürlich der BootLoader weg, was ich vorher leider vergaß.
 
 Wie kann ich den am einfachsten wieder herstellen?

Knoppix rein, grub-install aufrufen (man grub-install lesen)

Andreas

-- 
Cold hands, no gloves.


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: Grub-Bootloader wiederherstellen

[gebhard dettmar]

On Wednesday 05 January 2005 18:00, Peter Schütt wrote:
 Hallo,
 ich habe auf einem System, wo Win98 und Debian, Kernel 2.4, parallel
 installiert wurde, Win98 neu installiert.
 Jetzt ist natürlich der BootLoader weg, was ich vorher leider vergaß.

 Wie kann ich den am einfachsten wieder herstellen?
Mit Bootdiskette / -CD
 TIA

 Ciao
   Peter Schütt
dito
gebhard

Re: Grub-Bootloader wiederherstellen

[Martin Röhricht]

Am Mittwoch, den 05.01.2005, 18:00 +0100 schrieb Peter Schütt:
 Hallo,
 ich habe auf einem System, wo Win98 und Debian, Kernel 2.4, parallel
 installiert wurde, Win98 neu installiert.
 Jetzt ist natürlich der BootLoader weg, was ich vorher leider vergaß.
 
 Wie kann ich den am einfachsten wieder herstellen?

Ich habe mir mal in einem Dokument festgehalten, wie es bei mir immer
funktioniert hat mit Windows XP:
Mit einer Installations-CD der Linux Distribution die Linux Installation
booten. 

1. SuSE bringt im Startmenü der CDs einen entsprechenden Punkt mit. 
   Unter Debian kann man linuxbf26 o.ä. booten.
2. Grub als root starten mit dem Kommando »grub«
3. Die Linux Partition ausfindig machen (find /boot/grub/stage1)
   und Grub wieder in den MBR schreiben:

---8
GNU GRUB version 0.95 (640K lower / 3072K upper memory)

[ Minimal BASH-like line editing is supported. For the first
word, TABblists possible command completions. Anywhere else TAB
lists the possible completions of a device/filename. ]

grub find /boot/grub/stage1

(hd0,5)

grub root (hd0,5)

Filesystem type is ext2fs, partition type 0x83

grub setup (hd0)

Checking if /boot/grub/stage1 exists... yes

Checking if /boot/grub/stage2 exists... yes

Checking if /boot/grub/e2fs_stage1_5 exists... yes

Running embed /boot/grub/e2fs_stage1_5 (hd0)... 16 sectors are
embedded.

succeeded

Running install /boot/grub/stage1 (hd0) (hd0)1+16 p
(hd0,5)/boot/grub/stage2 /boot/grub/menu.lst... succeeded

Done.
---8

HTH,
Martin

Re: Bootloader for Sarge - partitions

[Micha Feigin]

On Sat, Sep 18, 2004 at 03:29:59PM -0700, Alvin Oga wrote:
 
 
 On Sat, 18 Sep 2004, Robert Epprecht wrote:
 
  Alvin Oga [EMAIL PROTECTED] writes:
  
 - /boot should NOT be a separate partition
  

That NOT true. The right line today is

/boot no longer needs to be a separate partition.

It used to be required due to bios limitations on the location of the
system on the disk, but that requirement was removed so ...
Its sometimes a problem to have lilo/grub on the second HD or the
second/third/... controllers, but thats less and less true also.

  Why? Please elaborate.
 
 even if you can boot, you do NOT have a root fs ..
 ( /etc /bin /sbin /lib /dev ... )
 
 you can always use a fd or cd or network to boot
 the system if the rootfs /etc /bin /sbin is working
 without /boot
 
 without a rootfs ... it is pointless to boot unless
 the boot fd or boot cd has its own rootfs 
 ( like an installer or standalone system like knoppix )
 
 gazillion ways to boot a box
 
 only one way to fix a dead linux install 
   - to get into single user mode
   or boot a standalone system w/o needing the 
   dead/suspect hard disk
 
   - a bad partition scheme will prevent you
   from fixing your disk gone bad due to
   corruptions in ext2/ext3/reiserfs/etc
 
 partition scheme is important if you dont want to lose
 your user data in say /home
   - user configs in /etc is easy to save onto floppy
 

I have to admit I can't follow your reasoning here. Whats the relation
between a separate boot partition and the ability to boot in single
user mode or access the partition from a live-cd and relatives?

 c ya
 alvin
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
  
  +++
  This Mail Was Scanned By Mail-seCure System
  at the Tel-Aviv University CC.
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Bootloader for Sarge - partitions

[Alvin Oga]

hi ya micha

On Sun, 19 Sep 2004, Micha Feigin wrote:

- /boot should NOT be a separate partition
   
 
 That NOT true. The right line today is 
 /boot no longer needs to be a separate partition.

okay ... i'll bite ...

 It used to be required due to bios limitations on the location of the
 system on the disk, but that requirement was removed so ...
 Its sometimes a problem to have lilo/grub on the second HD or the
 second/third/... controllers, but thats less and less true also.

but if one still has a klunky old pc that one keeps using
instead of buying the latest greates p4-3.8G ... or dual0opteroons
to be a dns server or mail server.. one will still run into the 
bios problems ... having /boot a separate partion or not will
depend on where the rootfs is loaded due to that bios limiation

having /boot in /dev/hda1 or under 1024 won't help you ... 
since the rest of the the /bin /dev /lib is in /dev/hda1000 
well above 1024 cylinder ... with windoze stuck inbetween ..
( its unlikely to have /boot vastly different that a mere 64MB or
( 128MB for themain rootfs that you care about

 I have to admit I can't follow your reasoning here. Whats the relation
 between a separate boot partition and the ability to boot in single
 user mode or access the partition from a live-cd and relatives?

one learns the hardway ... single use is important to some and not to
others ... 

in my book .. any machine that does not support single user mode
or init 2 or init 3 or init 5  or init 0 or init 6 is a throw away machine
- and even worst if one has to sit there and wait for e2fsck
to finish checking the whole silly 300GB before youc an wiggle
the keys at 3AM

having /boot in a different partition will NOT help you any

you can always boot from floppy or cd w/o having /boot on the hd

c ya
akvin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]