diff --git a/2006-01-23-how-to-install-debian-sarge-on-an-ibm-blade.html b/2006-01-23-how-to-install-debian-sarge-on-an-ibm-blade.html new file mode 100644 index 0000000..d55f9c7 --- /dev/null +++ b/2006-01-23-how-to-install-debian-sarge-on-an-ibm-blade.html @@ -0,0 +1,55 @@ + + + + + +

This is, unfortunately, complicated. You’ll need:

+ + + +

Steps:

+ +
    +
  1. Attach the USB drive
    2. +
  2. Boot the blade from the DVD
    3. +
  3. At the boot prompt, type: linux26 vga=771
    4. +
  4. Go through the install as normal. Note that the drives are out of order (USB drive is first).
    5. +
  5. When asked “Do you want to install the GRUB bootloader to the master boot record?”, say No.
    6. +
  6. Enter /dev/sdb to install to.
    7. +
  7. The install will reboot.
    8. +
  8. Let the disc eject or, if remote, change the boot order to boot from HD first.
    9. +
  9. GRUB will error when trying to boot; dismiss the error message.
    10. +
  10. Press “e” to edit the boot commands. Change “(hd1,0)” to “(hd0,0)” and “/dev/sdb1″ to “/dev/sda1″.
    11. +
  11. Press “b” to boot.
    12. +
  12. Use the “cdrom” access method for apt.
    13. +
  13. Go through the install as normal.
    14. +
  14. Log in as root.
    15. +
  15. Edit /etc/fstab, correcting the drive lettering for any partitions that are messed up.
    16. +
  16. Run: mount /boot
    17. +
  17. Edit /boot/grub/menu.lst, changing the lines starting with “# kopt=” and “# groot=” to reflect the changes made during boot.
    18. +
  18. Run: update-grub
    19. +
  19. If you configured RAID during installation, edit /etc/mdadm/mdadm.conf to reflect drive letter changes.
    20. +
  20. Mount the USB drive on /mnt.
    21. +
  21. Run: apt-get install module-assistant kernel-kbuild-2.6-3 debhelper kernel-image-2.6.8-2-686-smp build-essential +(the non-SMP image will also work, if you want this off)
    22. +
  22. Run: dpkg -i /mnt/bcm5700-source_7.3.5-4_all.deb /mnt/kernel-headers-2.6.8-2_2.6.8-16_i386.deb /mnt/kernel-headers-2.6.8-2-686_2.6.8-16_i386.deb /mnt/kernel-headers-2.6.8-2-686-smp_2.6.8-16_i386.deb
    23. +
  23. Run: cp /mnt/fixup-network.sh /etc/init.d/
    24. +
  24. Run: reboot
    25. +
  25. When the machine reboots, run: module-assistant prepare
    26. +
  26. Run: module-assistant auto-install bcm5700
    27. +
  27. Run: update-rc.d fixup-network.sh start 34 0 6 S .
    28. +
  28. Run: reboot
    29. +
  29. The machine should now be usable. If you’ve got the BladeCenter internal Cisco switch, the install has probably triggerred flap suppression. telnet to the switch and shutdown/noshutdown the port (hints: show int status, conf t, int interfacename, shutdown, no shutdown).
    30. +
+ + diff --git a/files/bcm5700-source_7.3.5-4_all.deb b/files/bcm5700-source_7.3.5-4_all.deb new file mode 100644 index 0000000..a88c137 Binary files /dev/null and b/files/bcm5700-source_7.3.5-4_all.deb differ diff --git a/files/fixup-network.sh b/files/fixup-network.sh new file mode 100644 index 0000000..34f243e --- /dev/null +++ b/files/fixup-network.sh @@ -0,0 +1,9 @@ +#!/bin/sh + +case "$1" in + start) + rmmod tg3 + rmmod bcm5700 + modprobe bcm5700 + ;; +esac diff --git a/files/kernel-headers-2.6.8-2-686-smp_2.6.8-16_i386.deb b/files/kernel-headers-2.6.8-2-686-smp_2.6.8-16_i386.deb new file mode 100644 index 0000000..ef55545 Binary files /dev/null and b/files/kernel-headers-2.6.8-2-686-smp_2.6.8-16_i386.deb differ diff --git a/files/kernel-headers-2.6.8-2-686_2.6.8-16_i386.deb b/files/kernel-headers-2.6.8-2-686_2.6.8-16_i386.deb new file mode 100644 index 0000000..09b8679 Binary files /dev/null and b/files/kernel-headers-2.6.8-2-686_2.6.8-16_i386.deb differ diff --git a/include/style.css b/include/style.css index 2992c29..5c47189 100644 --- a/include/style.css +++ b/include/style.css @@ -85,8 +85,9 @@ h4 { font-weight: bold; } -ul li { - margin-bottom: 10px; +ul li, ol li { + margin-top: 5px; + margin-bottom: 5px; } code { diff --git a/index.html b/index.html index 47e7f6c..b03b676 100644 --- a/index.html +++ b/index.html @@ -40,6 +40,7 @@
  • 2009-Sep-11: Confusing BIND with CNAMEs
  • 2009-Feb-19: The odd case of my mugging
  • 2009-Feb-03: 5-packet TCP connection?
    • +
  • 2006-Jan-23: How to install Debian Sarge on an IBM Blade
  • 2006-Jan-22: Why does my machine think its name is localhost...
  • 2006-Jan-22: Flashing without Microsoft or floppy drives
    • diff --git a/markdown/2006-01-23-how-to-install-debian-sarge-on-an-ibm-blade.md b/markdown/2006-01-23-how-to-install-debian-sarge-on-an-ibm-blade.md new file mode 100644 index 0000000..dca5ba9 --- /dev/null +++ b/markdown/2006-01-23-how-to-install-debian-sarge-on-an-ibm-blade.md @@ -0,0 +1,49 @@ + + + + + +This is, unfortunately, complicated. You’ll need: + +* [The full DVD #1 of Sarge](http://mirror.cs.wisc.edu/pub/mirrors/linux/debian-cd/3.1_r1/i386/bt-dvd/debian-31r1-i386-binary-1.iso.torrent) +* A USB drive containing: + * [fixup-network.sh](files/fixup-network.sh) + * [bcm5700-source\_7.3.5-4\_all.deb](files/bcm5700-source_7.3.5-4_all.deb) + * kernel-headers-2.6.8-2\_2.6.8-16\_i386.deb [link broken in platform transfer] + * [kernel-headers-2.6.8-2-686\_2.6.8-16\_i386.deb](files/kernel-headers-2.6.8-2-686_2.6.8-16_i386.deb) + * [kernel-headers-2.6.8-2-686-smp\_2.6.8-16\_i386.deb](files/kernel-headers-2.6.8-2-686-smp_2.6.8-16_i386.deb) + +Steps: + +1. Attach the USB drive +1. Boot the blade from the DVD +1. At the boot prompt, type: `linux26 vga=771` +1. Go through the install as normal. Note that the drives are out of order (USB drive is first). +1. When asked “Do you want to install the GRUB bootloader to the master boot record?”, say No. +1. Enter _/dev/sdb_ to install to. +1. The install will reboot. +1. Let the disc eject or, if remote, change the boot order to boot from HD first. +1. GRUB will error when trying to boot; dismiss the error message. +1. Press “e” to edit the boot commands. Change “(hd1,0)” to “(hd0,0)” and “/dev/sdb1″ to “/dev/sda1″. +1. Press “b” to boot. +1. Use the “cdrom” access method for apt. +1. Go through the install as normal. +1. Log in as root. +1. Edit /etc/fstab, correcting the drive lettering for any partitions that are messed up. +1. Run: `mount /boot` +1. Edit /boot/grub/menu.lst, changing the lines starting with “# kopt=” and “# groot=” to reflect the changes made during boot. +1. Run: `update-grub` +1. If you configured RAID during installation, edit /etc/mdadm/mdadm.conf to reflect drive letter changes. +1. Mount the USB drive on /mnt. +1. Run: `apt-get install module-assistant kernel-kbuild-2.6-3 debhelper kernel-image-2.6.8-2-686-smp build-essential` + (the non-SMP image will also work, if you want this off) +1. Run: `dpkg -i /mnt/bcm5700-source_7.3.5-4_all.deb /mnt/kernel-headers-2.6.8-2_2.6.8-16_i386.deb /mnt/kernel-headers-2.6.8-2-686_2.6.8-16_i386.deb /mnt/kernel-headers-2.6.8-2-686-smp_2.6.8-16_i386.deb` +1. Run: `cp /mnt/fixup-network.sh /etc/init.d/` +1. Run: `reboot` +1. When the machine reboots, run: `module-assistant prepare` +1. Run: `module-assistant auto-install bcm5700` +1. Run: `update-rc.d fixup-network.sh start 34 0 6 S .` +1. Run: `reboot` +1. The machine should now be usable. If you’ve got the BladeCenter internal Cisco switch, the install has probably triggerred flap suppression. telnet to the switch and shutdown/noshutdown the port (hints: show int status, conf t, int _interfacename_, shutdown, no shutdown). + + diff --git a/markdown/index.md b/markdown/index.md index 4ded5a8..6fef878 100644 --- a/markdown/index.md +++ b/markdown/index.md @@ -39,6 +39,7 @@ 1. 2009-Sep-11: [Confusing BIND with CNAMEs](2009-09-11-confusing-bind-with-cnames.html) 1. 2009-Feb-19: [The odd case of my mugging](2019-02-19-the-odd-case-of-my-mugging.html) 1. 2009-Feb-03: [5-packet TCP connection?](2009-02-03-5-packet-tcp-connection.html) +1. 2006-Jan-23: [How to install Debian Sarge on an IBM Blade](2006-01-23-how-to-install-debian-sarge-on-an-ibm-blade.html) 1. 2006-Jan-22: [Why does my machine think its name is localhost...](2006-01-22-why-does-my-machine-think-its-name-is-localhost-even-though-i-changed-it.html) 1. 2006-Jan-22: [Flashing without Microsoft or floppy drives](2006-01-22-flashing-without-microsoft-or-floppy-drives.html)