RE: making a floppy for essential modules
Here is how I set up my Dell
Set up Debian 3.0r1 on Dell Poweredge 2400
1. Insert Debian disk and boot from it.
2. At boot: prompt type bf24 and press enter.
3. Complete rest of install normally. Make sure to install the c
compiler.
4. Download most current kernel. For this example it was 2.4.20
5. Copy kernel to /usr/src
6. tar xzvf linux-2.4.20.tar.gz
7. rm linux
8. ln -s linux-2.4.20 linux
9. ls -al (verify symbolic link you just created)
10. cd /usr/src/linux
11. make menuconfig
12. Select your options in the menu
13. Store configuration to file. This is your backup.
14. make dep
15. make clean
16. make bzImage (ignore warning message)
17. make modules
18. make modules_install
19. make install
20. vi /etc/lilo.conf
21. Verify settings are correct.
lilo.conf
Samba:/etc# more lilo.conf
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# --------------- `install-mbr(8)', `/usr/share/doc/lilo/',
# and `/usr/share/doc/mbr/'.
# +---------------------------------------------------------------+
# | !! Reminder !! |
# | |
# | Don't forget to run `lilo' after you make changes to this |
# | conffile, `/boot/bootmess.txt', or install a new kernel. The |
# | computer will most likely fail to boot if a kernel-image |
# | post-install script or you don't remember to run `lilo'. |
# | |
# +---------------------------------------------------------------+
# Support LBA for large hard disks.
#
lba32
# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
# bios=0x81
#disk=/dev/sda
# bios=0x80
# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/sda
# Specifies the device that should be mounted as root. (`/')
#
root=/dev/sda1
# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using `compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
#
# compact
# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
install=/boot/boot.b
# Specifies the location of the map file
#
map=/boot/map
# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000
# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=100
# You can put a customized boot message up if you like. If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress. `single-key' goes with the `alias' lines in the
# `image' configurations below. eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
prompt
# single-key
# single-key
# delay=100
# timeout=100
# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
#
# vga=ask
# vga=9
#
vga=normal
# Kernel command line options that apply to all installed images go
# here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append="ide2=0xd400,0xd002 ide3=0xcc00,0xc802 hdb=ide-scsi hdc=ide-scsi"
# Boot up Linux by default.
#
default=Linux
image=/boot/vmlinuz-2.4.20-x
label=Linux
read-only
# restricted
# alias=1
image=/vmlinuz
label=OldLinux
read-only
# restricted
# alias=2
# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
# label=HURD
# restricted
# alias=3
22. /sbin/lilo
23. shutdown -r now
24. cd /etc/network
25. vi interfaces
26. Verify the following. Make changes as required.
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
auto eth0
iface eth0 inet static
address 192.168.0.25
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.71
auto eth1
iface eth1 inet static
address 192.168.0.26
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.71
27. shutdown -r now
28.
-----Original Message-----
From: New Disorder Records [mailto:ernst@hblindustries.com]
Sent: Tuesday, December 09, 2003 1:09 PM
To: debian-user@lists.debian.org
Subject: making a floppy for essential modules
Hi,
I am trying to install debian on a dell poweredge, but I need drivers
for the hard drives and ethernet card. I have found the drivers, but I
have no idea how to put them on a floppy disk so that debian will see them
when I put the floppy in. I don't have other debian machines in the
office, so I have to make the floppies on a windows machine. Any advice
about how to put the drivers on a floppy so that debian will see them
would be greatly appreciated.
Ernst Schoen-Rene,
HBL Industries.
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
Reply to: