Fwd: How to recover boot floppy in Lenny

2010-04-17 Thread Mauricio Contreras
-- Forwarded message --
From: Mauricio Contreras mauricio.contre...@gmail.com
Date: Sat, Apr 17, 2010 at 11:25 AM
Subject: Re: How to recover boot floppy in Lenny
To: Camaleón noela...@gmail.com


On Fri, Apr 16, 2010 at 11:44 AM, Camaleón noela...@gmail.com wrote:
 On Fri, 16 Apr 2010 10:48:10 -0300, Mauricio Contreras wrote:

 On Fri, Apr 16, 2010 at 8:04 AM, Camaleón wrote:

 You mean there is no sound after you login?

 I fail to see any relation with that fact (no sound) and the bootloader
 being located in a floppy disk or SuperGrubDisk so I would investigate
 first why the sound stopped from working.

 (...)

 I recovered sound in Lenny after booting with SuperGrub and running
 alsaconf as root. I picked up my old SoundBlaster Live card and the
 emu10k1 module with alsaconf and set it up as the main sound card
 (there's also an integrated AC'97 in the motherboard) card with index=0.
 Then sound came back.

 Ah, that makes more sense to me :-)

 (...)

 My disks are set up as follows:

 IDE 80 GB hda: 2 partitions
 hd0, 40 GB --- windows xp boot;
 hd1, 40 GB --- windows xp data files

 SATA 80 GB sda 1 partition
 sda 80 GB -- windows data files

 SATA 500 GB
 sdb 1 partition sdb (??) 500 GB ---lenny

 I haven't been able to configure Grub 0.94 to boot in this setup so I
 have used SuperGrub or a bootable floppy with Lenny. Could you point me
 to an appropiate grub setup?

 Well, it seems you have 3 physical hard disks, with windows installed in
 the first partition of the IDE hdd and Lenny in the second SATA (500 GiB).

 First you have to do is *to know* what hard disk is being booted in first
 place by the BIOS (IDE 80 -windows- or SATA 500 -lenny-). After that,
 put here the results of your findings and we will see what could be the
 better setup for installing GRUB :-)

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


I'm enclosing results from fdisk -l and the current grub setup from menu.lst

debian:/home/mferminco# /sbin/fdisk -l

Disco /dev/hda: 81.9 GB, 81964302336 bytes
255 heads, 63 sectors/track, 9964 cylinders
Units = cilindros of 16065 * 512 = 8225280 bytes
Disk identifier: 0xeba8eba8

Disposit. Inicio    Comienzo      Fin      Bloques  Id  Sistema
/dev/hda1   *           1        9964    80035798+   7  HPFS/NTFS

Disco /dev/sda: 82.3 GB, 82348277760 bytes
255 heads, 63 sectors/track, 10011 cylinders
Units = cilindros of 16065 * 512 = 8225280 bytes
Disk identifier: 0x353e353d

Disposit. Inicio    Comienzo      Fin      Bloques  Id  Sistema
/dev/sda1   *           1        3636    29206138+   7  HPFS/NTFS
/dev/sda2            3637       10011    51207187+   f  W95 Ext'd (LBA)
/dev/sda5            3637       10011    51207156    7  HPFS/NTFS

Disco /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cilindros of 16065 * 512 = 8225280 bytes
Disk identifier: 0x869150ed

Disposit. Inicio    Comienzo      Fin      Bloques  Id  Sistema
/dev/sdb1   *           1       60471   485733276   83  Linux
/dev/sdb2           60472       60801     2650725    5  Extendida
/dev/sdb5           60472       60801     2650693+  82  Linux swap / Solaris

THIS COMES FROM /boot/grub/menu.lst. It doesn't boot linux!

title           Debian GNU/Linux, kernel 2.6.26-2-686
root            (hd2,0)
kernel          /boot/vmlinuz-2.6.26-2-686 root=/dev/sdb1 ro quiet
initrd          /boot/initrd.img-2.6.26-2-686

title           Debian GNU/Linux, kernel 2.6.26-2-686 (single-user mode)
root            (hd2,0)
kernel          /boot/vmlinuz-2.6.26-2-686 root=/dev/sdb1 ro single
initrd          /boot/initrd.img-2.6.26-2-686

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title           Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title           Microsoft Windows XP Professional
root            (hd1,0)
savedefault
map             (hd0) (hd1)
map             (hd1) (hd0)
chainloader     +1

Right now the system boots Windows XP directly.

Mauricio Contreras
Buenos Aires, Argentina


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



Re: Fwd: How to recover boot floppy in Lenny

2010-04-17 Thread Camaleón
2010/4/17 Mauricio Contreras:

 On Fri, Apr 16, 2010 at 11:44 AM, Camaleón wrote:

(...)

 First you have to do is *to know* what hard disk is being booted in 
first
 place by the BIOS (IDE 80 -windows- or SATA 500 -lenny-). After 
that,
 put here the results of your findings and we will see what could be the
 better setup for installing GRUB :-)

 I'm enclosing results from fdisk -l and the current grub setup from 
menu.lst

(...)


 THIS COMES FROM /boot/grub/menu.lst. It doesn't boot linux!

(...)

 Right now the system boots Windows XP directly.


O.k. So now you are *not getting* the GRUB menu, right?

By reading the data you provided, I'd say your BIOS is setup to boot at 
first the disk that holds windows OS and so windows loads directly.

If that is true, I will make you some suggestions/ways to solve/bypass 
this. 

(Disclaimer: all of these options are risky -as so is any action that 
involve the bootloader- so please, if in doubt, *ask someone in the know* 
to make the job and before taking any step keep your invaluable data in 
a safe place)

1/ Install GRUB into the MBR of the first disk.

Caution! this will cause the current bootloader of the disk (that is, 
windows bootloader) will be *lost* and GRUB will take control of the 
booting process... it should be no problem but when windows comes into 
play, one never knows.


2/ Create a new partition into the hard disk holding windows OS to 
install GRUB there. Then, you can mark that partition with the bootable 
flag. In theory, this will pass the boot control to GRUB and you could 
boot any OS from there.


3/ Change the BIOS order of the hard disk booting devices.

Caution! This can mess a bit the current setup of your debian lenny 
install, I am not sure what will be the results.

By selecting as hard disk first boot device the disk where you have 
installed Debian lenny, this will make you boot directly into Debian. 
Then you can:

a) Install GRUB into the hard disk MBR
b) Install GRUB into the first sector of a partition

(note: probably you already have GRUB installed somewhere in the hard 
drive)


And... I think I have no more advices to handle this situation, if 
someone wants to add another one, I'm sure the OP will thank any idea O:-)

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