[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Re[2]: Installation 1.3 failed, returned to 1.1 and upgraded



On Thu, 26 Jun 1997 JIM_BURT_at_nass-fx@nass.usda.gov wrote:

: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.
[stuff cut]
:
:   [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.
:   ]

A guess:  you either have a screwed up fdisk or partition table.  I've
had bad experiences with cfdisk.  fdisk on the other hand has no trouble
with two ST34371W drives attached to an Adaptec 2940UW.

:
:  -----------------------
:  |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.]
:        .

PPP users should indeed say no.  I think it did include this comment ...
I may be mistaken.

:        .
:   ---------------------------------
:   |Configure Device Driver Modules|
:   ---------------------------------
[snip]
:   ---------------------------------------------
:   |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 

so /dev/sda2 is the name of the extended partition?  This seems wrong
...

:        root=/dev/sda7                             partition holding /dev/sda7]
:        compact
:        install=/boot/boot.b
[snip]
: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

I have yet to get a system with both IDE and SCSI interfaces active to
boot off the SCSI disk.  Perhaps there is a workaround for this, but
it's my understanding that the Adaptec BIOS will not hook the boot
sequence if IDE drives are present.

: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>

This is a lot of partitions ... at one point Linux came with a default
maximum of 8 partitions/drive (for SCSI)  Has this (obviously) changed?

:   sdb: sdb1 sdb2
:VFS: Mounted root (ext2 filesystem) readonly.
:-----------------------------------------------------------------------------
:After this, the system hung.  <alt-F2>, <alt-F3>, <alt-F4> had no effect.
[snip]
:
: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

The extended partition being active still bugs me :)  Any LILO gurus out
there?  Also, have you *deleted* partition 1, or did you just change the
OS type?  Of course, if you delete it now, you'll renumber the
partitions.  Gotta love partition tables ...

:>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],

Sure, cos it's looking for readable CDs to install from.  I suppose they
could disable the message about not finding a valid filesystem, but
others might not like that?

: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
:

Well, good luck.  I installed Debian on a system very similar to yours
(a Gateway G6, also uses the Venus MB I believe) with very few
difficulties.  Doesn't help you, I know, but it is possible, at any
rate.

--
  Nathan Norman    :    Hostmaster CFNI    :    nnorman@cfni.com
    finger nnorman@cfni.com for PGP public key and other stuff
Key fingerprint = CE 03 10 AF 32 81 18 58  9D 32 C2 AB 93 6D C4 72
--



--
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: