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

Bug#276590: marked as done (painful alpha install)

Your message dated Sat, 24 Mar 2007 10:40:08 -0700
with message-id <20070324174008.GC5976@ryukin.fglan>
and subject line closing very old report on alpha install
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: installation-reports

INSTALL REPORT

Debian-installer-version: pre-rc2

downloaded from http://people.debian.org/~vorlon/d-i/images/2004-09-30/netboot/boot.img

uname -a: Linux lilalph 2.4.27-1-generic #1 Sat Sep 4 01:15:04 CEST 2004 alpha GNU/Linux

Date: 2004-10-12 
Method: 
How did you install? 

used netboot image

What did you boot off?

SRM bootloader, dhcp & tftp

If network install, from where?  Proxied?

ftp.us.debian.org, used a local squid proxy.

Machine: alpha, easy WebServer (similar to multia ?)
Processor: 
cpu                     : Alpha
cpu model               : LCA4
cpu variation           : 7
cpu revision            : 0
cycle frequency [Hz]    : 166626363 est.
BogoMIPS                : 323.24

Memory: 96MB
Root Device: SCSI: /dev/sda5 
Root Size/partition table:  

fdisk /dev/sda -l -u
           
Disk /dev/sda: 4293 MB, 4293632000 bytes
133 heads, 62 sectors/track, 1016 cylinders, total 8386000 sectors
Units = sectors of 1 * 512 = 512 bytes


6 partitions:
#       start       end      size     fstype   [fsize bsize   cpg]
  a:        1      1954      1954       ext2    (aboot partition ?)                  
  b:     1955    158205    156251       ext2    /boot                   
  c:   158206   5041017   4882812       ext2    (old root)                  
  d:  5041018   5373049    332032       swap    swap                  
  e:  5373050   8385999   3012950       ext2    /


Output of lspci and lspci -n:

0000:00:06.0 SCSI storage controller: LSI Logic / Symbios Logic 53c810 (rev 02)
0000:00:07.0 Non-VGA unclassified device: Intel Corp. 82378ZB/IB, 82379AB (SIO, SIO.A) PCI to ISA Bridge (rev 03)
0000:00:08.0 Ethernet controller: Digital Equipment Corporation DECchip 21040 [Tulip] (rev 23)
0000:00:0b.0 Display controller: Digital Equipment Corporation DECchip 21030 [TGA] (rev 02)
l

0000:00:06.0 0100: 1000:0001 (rev 02)
0000:00:07.0 0000: 8086:0484 (rev 03)
0000:00:08.0 0200: 1011:0002 (rev 23)
0000:00:0b.0 0380: 1011:0004 (rev 02)


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:    [E]
Configure network HW:   [E]
Config network:         [O]
Detect CD:              [ ]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [O]
Create file systems:    [E]
Mount partitions:       [O]
Install base system:    [O]
Install boot loader:    [E]
Reboot:                 [E]

Comments/Problems:

still requires using the serial console instead of TGA video hardware...  (bug
#273232).  i had to manually specify the boot flags to use a serial console.


the installer detected and loaded wrong ethernet module.  should load de4x5,
instead loads tulip.  from /usr/share/discover/pci.lst:

    10110002        ethernet        tulip   DECchip 21040 [Tulip]

this looks fixed in discover1-data 1.2004.09.25 (bug #273265)


"Change debconf priority" didn't ask what priority to change to, and dropped
back to the main menu.  didn't appear to have any effect.  (i had set
debconf/priority=low from the boot prompt, in order to manually load the
appropriate ethernet module)


specifying DEBIAN_FRONTEND=text failed with the following error messages, in a
seemingly endless loop:

/build/buildd/cdebconf-0.70/src/frontend.c:160 (frontend_new): Cannot load frontend module /usr/lib/cdebconf/frontend/text.so: /usr/lib/cdebconf/frontend/text.so: cannot open shared object file: No such file or directory                    

if it could at least attempt to fall back to an alternate frontend when the
default frontend fails... it would at least give a chance for the install to
proceed...  or at least stop trying to probe for a non-existant frontend at
some point.


when selecting a partition with an existing filesystem, it asked what type of
filesystem to use, which made me concerned, since there was data i wanted to
preserve... it might be better if it asked to format the partition first, and
only if (re)formatting the partition should it ask what type of filesystem to
use (presuming there is a valid filesystem on the partition)...


aboot failed to install, but gave no reason why.  the /boot partition had an
existing aboot installation on it already. it seems to at least boot up to
base-config ok, but with the kernel from the previous install. /boot/vmlinuz
points to the 2.4.26-1-generic kernel, though /vmlinuz points to the
2.4.27-1-generic kernel.


and still, the initrd for the generated 2.4.27 kernel fails to load the
appropriate SCSI controller driver for a 2.4 kernel (bug #273267), which causes
a kernel panic becaue it can't find the root filesystem. this may be fixed in
discover1-data 1.2004.09.25, if that's what the initrd generation uses during
install to determine what modules to load...


what fun. :)

live well,
  vagrant

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
i'm closing this old bug because i know several of the reported issues
are now addressed, and i don't really have access to the hardware to
test the remaining issues.

live well,
  vagrant

--- End Message ---
Reply to: