Re[2]: Installation 1.3 failed, returned to 1.1 and upgraded
Recall, I ran Debian 1.1 with few problems for 7 months.
With few problems, for months, I used numerous "bo" packages,
though evidently not the "bo" dpkg_1.*.deb package.
Last month I tried installing Debian 1.3, eventually re-initializing
several partitions, but these pure Debian 1.3 installations continue to fail.
I have created two sets of installation disks on computers separated by 1 mile,
and both produce the same troubles.
I now try the boot (rescue) disk and a debian-site mirror on a
second hard disk. This mirror passes an md5sum check.
I SEEM TO GET THROUGH THE INSTALLATION, BUT CAN BOOT FROM NEITHER THE NEW FLOPPY
NOR THE NEW HARD DISK BOOT-RECORDS.
Below, I
1. Outline parts of my current installation steps.
I include a couple installation anomolies which do not cause
my installation failure, but probably should be modified in bo/disks-i386.
2. I include my floppy bootup stream and my disk bootup stream.
3. Some "fdisk" information about my /dev/sda disk drive.
4. Some final comments.
First, here is some of my interaction with install:
-----------------------------------------------------------------------------
Select Partition
Please select the partition to initialize as a linux ext2 filesystem
/dev/sda6
/dev/sda7
/dev/sda8
/dev/sda9
/dev/sda10
/dev/sda11
/dev/sda12
/dev/sda13
/dev/sdb2
[I selected /dev/sda7.
But note that MY PARTITION /dev/sda1 IS NOT LISTED.
It is "Linux native". Last week I had it as "Linux swap"
and it was not considered a possible swap partition.
Since I used /dev/sda1 as my swap partition under Debian 1.1
for 7 months, Debian 1.3 should somehow consider /dev/sda1.
]
-----------------------
|Configure the Network?|
-----------------------
Is your system connected to a network?
[WHAT SHOULD WE ppp USERS SAY? Please insert a comment for us. I said no.]
.
.
.
---------------------------------
|Configure Device Driver Modules|
---------------------------------
.
.
.
------ ------- Enter Command-Line Arguments:
|misc| --> |psaux| --> psaux
------ ------- No module parameters
. Depends on misc.o
. [I believe this is no longer true, though it
. certainly was 6 months ago. I FIND NO misc.o
in Debian 1.3 and my PS/2 mouse works without
misc.o]
-----------------------
|Configure the Network|
-----------------------
.
.
.
-------------------------
|Install the Base System|
-------------------------
Please choose the directory where the Debian archive resides
/mnt/mirrors/debian [my entry after mounting /dev/sdb2 on /mnt.
/dev/sdb2 contains by Debian mirror,
last updated June 9]
Select the Base Archive file
list Choose from a list of Base Archive Files
manually Enter the Directory ...
[This time around, there was no third entry like
default The default stable Archive
so I selected "list"]
Select Color or Monochrome
[OOPS, THE INSTALLATION HAS RETURNED TO THE BEGINNING
as if I just inserted the boot (rescue) disk.
Something went amiss --THIS SHOULD NOT HAVE HAPPENED.
Since swap space was already initialized, my installation
was muddled and I rebooted.
The next attempted installation produced three options,
and I selected "default".
The following entries/responses continue with my later install.]
---------------------------------------------
|Make Linux Bootable Directly From Hard Disk|
---------------------------------------------
Create Master Boot Record?
.
.
Install a master boot record on /dev/sda?
<yes> <no> [I responded "yes"]
[Meanwhile, /target/lilo.conf has
boot=/dev/sda2 [NOT /dev/sda; /dev/sda2 is the primary
root=/dev/sda7 partition holding /dev/sda7]
compact
install=/boot/boot.b
map=/boot/map
vga=normal
delay=10
image=/vmlinuz
label=Linux
read-only
This does not correspond to my just made response.
I gather from this and from the lack of a "lilo" executable in ram-disk that
"install" makes the boot record by a method other than lilo.
]
Make Linux the Default Boot Partition?
.
.
Boot the Debian system on /dev/sda2 as the default?
<yes> <no> [I respond "yes". HOWEVER, I said above that
I wanted /dev/sda, so this seems redundant
THIS MAY BE A KEY TO MY PROBLEM REBOOTING
FROM HARD DISK.]
--------------------
|Make a Boot Floppy|
--------------------
------------------------------------------------------------------
|Please place a blank floppy disk in the first floppy disk drive,|
|and press ENTER |
------------------------------------------------------------------
<OK>
.
.
Creating the operating system kernel
-------------------------------
|Next Reboot the System|
-------------------------------
With no installation errors, I was ready to reboot.
A floppy reboot on June 24, 1997, produced [hand copied] the following stream:
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
.
.
.
Loading Linux ...
Uncompressing Linux...done.
Now booting the kernel
Console: 16 point font, 400 scans
pcibios_init : BIOS32 Service Directory Structure at 0x000fd720
pcibios_init : BIOS32 Service Directory entry at 0xfd7301
pcibios_init : PCIBIOS revision 2.10 entry at 0xfd751
Probing PCI hardware.
Calibrating delay loop...okay - 199.07 BogoMIPS
Memory: 62756K/65536K available (984K kernel code, 384K reserved, 1412K data)
Swansea University Computer Society NET3.034 for Linux 2.0
NET3: Unix domain sockets 0.13 for Linux NET3.035.
Swansea University Computer Society TCP/IP for NET3.034
IP Protocols: ICMP, UDP, TCP
VFS: Disk quotas version dquot_5.6.0 initialized
checking 386/387 coupling...Ok, fpu using exception 16 error reporting.
Checking 'hlt' instruction...OK.
Linux version 2.0.29 (herbert@greathan)(gcc version 2.7.2.2) #1 Mon May 26
09:25:51 EST 1997
Real Time Clock Driver V1.07
tpqic02: Runtime config, $Revision: 0.4.1.5 $, $Date's 1994/10/29 02:46:113 $
tpqic02: DMA buffers: 20 blocks, at address 0x248c00 (0x248a50)
Ramdisk driver initialized: 16 ramdisks of 4096 K size
loop: registered device at major 7
ide: i82371 PIIX (Triton) on PCI bus 0 function 57
ide0: BM-DMA at 0xffa0-0xffa7
ide1: BM-DMA at 0xffa8-0xffaf
hdc: CD-ROM CDU311, ATAPI CDROM drive
ide1 at 0x170-0x177,0x376 on irq15
Floppy drive(s): fd0 is 1.44M
Started kswapd v 1.4.2.2
FDC 0 is a National Semiconductor PC87306
md driver 0.35 MAX_MD_DEV=4, MAX_REAL=8
aic7xxx: BurstLen=8 DWDs, Latency Timer= 64PCLKS
aic7xxx: AHA-2940 Ultra Rev B.
aic7xxx: devconfig = 0x1580
aix7xxx: Reading SEEPROM...done
aix7xxx: Enabling support for Ultra SCSI speed.
aix7xxx: Extended translation enabled.
aix7xxx: Memory check yields 16 SCBS, paging not enabled.
aicxxxx: Enabling the wide channel of AHA-2940 Ultra-wide.
AHA-2940 Ultra-WIDE (PCI-bus), I/O 0xfc00,Mem 0xffbef000:
irq 10
bus release time 40 bclks
data fifo threshhold 100%
SCSI CHANNEA:
scsi id 7
scsi selection timeout 256ms
scsi bus reset at power-on disabled
scsi bus parity enabled
scsi bus termination (low byte) disabled
scsi bus termination (high byte) enabled
aic7xxx: Downloading sequencer code...done.
aicxxx: Resetting the SCSI bus..done.
Failed initialization of WD-7000 SCSI card!
PPA: unable to initialize controller at 0x378, error 2
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 4.0/3.2/4.0
scsi : 1 host
scsi0: Scanning channel A for devices.
scsi0: Received MSG_WDTR, Target 1, channel A need wdtr (0xffff).
scsi0: Target 1, channel A, now synchronous at 20.0 MHz, offset 15.
Vendor: SEAGATE Model: ST32155N Rev:0176
Type: Direct-Access ANSI SCSI Revision: 02
Detected scsi disk sda at scsi0, channel 0, id 1, lun 0
scsi0: Received MSG_WDTR, Target 2, channel A need wdtr (0xfffd).
scsi0: Target 2, channel A, now synchronous at 10.0MHz, offset 15.
Vendor: SEAGATE Model: ST32550N Rev:0019
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdb at scsi0, channel 0, id 2, lun 0
scsi : detected 2 SCSI disks total.
SCSI device sda: hdwr sector=512 bytes. Sectors= 4197405 [2049MB][2.0GB]
SCSI device sdb: hdwr sector=512 bytes. Sectors=4194058 [2047MB][2.0GB]
Partition check:
sda: sda1 sda2<sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13>
sdb: sdb1 sdb2
VFS: Mounted root (ext2 filesystem) readonly.
-----------------------------------------------------------------------------
After this, the system hung. <alt-F2>, <alt-F3>, <alt-F4> had no effect.
A hard disk reboot produced the following stream:
-----------------------------------------------------------------------------
.
.
.
LILO Loading Linux
Uncompressing Linux...
crc error
--System halted
-----------------------------------------------------------------------------
Several later attempts putting the boot record on either floppy or hard disk
usually produced the same result,
LILO Loading Linux
Uncompressing Linux...
crc error
--System halted
For example, I tried
/target/sbin/lilo -C /target/etc/lilo.conf
which responded
Added Linux *
when /target/etc/lilo.conf was
boot=/dev/sda
root=/dev/sda7
compact
install=/target/boot/boot.b
map=/target/boot/map
image=/target/boot/vmlinuz-2.0.29
vga=normal
delay=50
label=Linux
read-only
And I tried the same with "boot=/dev/fd0".
But remember, I used Debian 1.1 successfully for 7 months,
used the 2.0.30 kernel successfully for some time, and
I can (indeed, amongst my troubles, did) install Debian 1.1 last week.
I am now trying lilo with some "yard" emergency disks I created.
They took me days to create, but I can put on them lilo,
vim, bash, ..., so I have all the usual tools.
The files on my "yard" emergency disks are about 6 months old.
Using my "yard" emergency disks, using the same /target/etc/lilo.conf
as just above, and mounting /dev/sda7 on /target,
I enter
lilo -C /target/etc/lilo.conf
getting
Map segment is too big.
Any clues? Does that mean that vmlinuz-2.0.29 of 623,026 is too big?
Or is my "yard" lilo just too old?
Bruce Perens asked me to run "fdisk" for information on the swap partition.
Here are my fdisk results:
Device Boot Begin Start End Blocks Id System
/dev/sda1 1 1 9 72261 83 Linux native [I changed from Linux
swap]
/dev/sda2 * 10 10 261 2024190 5 Extended
/dev/sda5 10 10 18 72261 82 Linux swap
/dev/sda6 19 19 26 64228+ 83 Linux native
/dev/sda7 27 27 30 32098+ 83 Linux native
/dev/sda8 31 31 34 32098+ 83 Linux native
/dev/sda9 35 35 136 819283+ 83 Linux native
/dev/sda10 137 137 149 104391 83 Linux native
/dev/sda11 150 150 175 208813+ 83 Linux native
/dev/sda12 176 176 195 160618+ 83 Linux native
/dev/sda13 196 196 261 530113+ 83 Linux native
>From the floppy boot stream above, you can see that I have 2 scsi disks
on an Adapted 2940UW board, an ATAPI CD [which Debian 1.3 install complains
about via <alt>F4 unless I put in a CD with a filesystem; eg, a Sun archive CD],
a Pentium Pro 200Mz chip with Natoma (Venus) motherboard,
64 MB parity memory.
For the last three weeks, my only contact with Linux has been boot disks,
rescue disks, "yard" rescue disks.
I am not slugging through this Debian 1.3 distribution as quickly
as I did the Debian 1.1 distribution and APPRECIATE ANY HELP ON INSTALLATION.
Jim Burt, jburt@nass.usda.gov
(703)235-5213, ext. 132
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: