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

Bug#276768: marked as done ([i386][netinst][20040921] success: Dell Latitude C400)

Your message dated Wed, 08 Sep 2010 03:57:43 +0000
with message-id <E1OtBn5-0004BJ-TB@ravel.debian.org>
and subject line Closing old installation report #276768
has caused the Debian Bug report #276768,
regarding [i386][netinst][20040921] success: Dell Latitude C400
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

276768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=276768
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports


(md5sum 09697510e1123190e78e103fd61b413f)

uname -a:
Linux version 2.6.7-1-686 (dilinger@toaster.hq.voxel.net) (gcc version 3.3.4 (De
bian 1:3.3.4-2)) #1 Thu Jul 8 05:36:53 EDT 2004

Date: 2004-10-01T19_16_39+1000
  How did you install? boot "linux" from netinst cdrom
  What did you boot off? netinst cdrom
  If network install, from where? n/a
  Proxied? no

Machine: Dell Latitude C400
Processor: Intel(R) Pentium(R) III Mobile CPU       866MHz
Memory: 256100 kB
Root Device: IDE, /dev/hda

Root Size/partition table:
(fdisk -l /dev/hda)

Disk /dev/hda: 30.0 GB, 30005821440 bytes
255 heads, 63 sectors/track, 3648 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1               1         191     1534176    7  HPFS/NTFS
/dev/hda2   *         192         829     5124735    7  HPFS/NTFS
/dev/hda3             830         862      265072+  83  Linux
/dev/hda4             863        3648    22378545    f  W95 Ext'd (LBA)
/dev/hda5             863        1227     2931831   83  Linux
/dev/hda6            1228        1289      497983+  83  Linux
/dev/hda7            1290        1532     1951866   83  Linux
/dev/hda8            1533        3492    15743668+  83  Linux
/dev/hda9            3493        3554      497983+  83  Linux
/dev/hda10           3555        3648      755023+  82  Linux swap

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/hda3       /               ext3    defaults,errors=remount-ro 0 1
/dev/hda8       /home           ext3    defaults        0       2
/dev/hda7       /opt            ext3    defaults        0       2
/dev/hda9       /tmp            ext3    defaults,nosuid,nodev        0 2
/dev/hda5       /usr            ext3    defaults        0       2
/dev/hda6       /var            ext3    defaults        0       2
/dev/hda10      none            swap    sw              0       0
/dev/hda2       /c              ntfs    ro,uid=1000,gid=1000      0  0
/dev/hdc        /media/cdrom0   iso9660 ro,user,noauto  0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0
none            /proc/bus/usb   usbdevfs

Output of lspci and lspci -n:
0000:00:00.0 0600: 8086:3575 (rev 04)
0000:00:00.0 Host bridge: Intel Corp. 82830 830 Chipset Host Bridge (rev 04)
0000:00:02.0 0300: 8086:3577 (rev 04)
0000:00:02.0 VGA compatible controller: Intel Corp. 82830 CGC [Chipset Graphics Controller] (rev 04)
0000:00:02.1 0380: 8086:3577
0000:00:02.1 Display controller: Intel Corp. 82830 CGC [Chipset Graphics Controller]
0000:00:1d.0 0c03: 8086:2482 (rev 02)
0000:00:1d.0 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 02)
0000:00:1e.0 0604: 8086:2448 (rev 42)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 42)
0000:00:1f.0 0601: 8086:248c (rev 02)
0000:00:1f.0 ISA bridge: Intel Corp. 82801CAM ISA Bridge (LPC) (rev 02)
0000:00:1f.1 0101: 8086:248a (rev 02)
0000:00:1f.1 IDE interface: Intel Corp. 82801CAM IDE U100 (rev 02)
0000:00:1f.5 0401: 8086:2485 (rev 02)
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801CA/CAM AC'97 Audio Controller (rev 02)
0000:00:1f.6 0703: 8086:2486 (rev 02)
0000:00:1f.6 Modem: Intel Corp. 82801CA/CAM AC'97 Modem Controller (rev 02)
0000:02:00.0 0200: 10b7:9200 (rev 78)
0000:02:00.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
0000:02:01.0 0607: 104c:ac50 (rev 02)
0000:02:01.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 02)

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

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


Dual-boot with WinXP.
Resized NT partitions with Partition Magic 8.0
Created linux partitions with partman.
Initial install with "linux" (ie 2.4.27), then installed 2.6.7.

[minor bug] (kernel framebuffer size miscalculated on Dell c400)
  The framebuffer driver appears to stop drawing one character cell short
  of the full width of the screen. This leads to a strongly "stepped"
  output which looks like hell but is (just) readable.
  I am uncertain if this is a problem in the framebuffer support or a
  buggy, lying BIOS.

  I am uncertain but from memory I think that this occurs in both the
  "linux" and "linux26" flavours of the installer.

  The same problem appears with the Ubuntu linux preview
  (warty warthog, 20040915,

  workaround: (again from memory)
  linux debian-installer/framebuffer=false

[usability bug]
  On the first attempt at installation, I filled up /var and had to
  go all the way back to the start. This is just silly.

  First, let me describe what happened when /var filled.
  1. The install step failed, but I was stuck inside the step.
     I think the name is "copying packages"?
  2. My notes are unclear but I think it was telling me that I'd
     run out of space. It is good that I'm told this.
  3. The problem was that there was no obvious next step -
        no advice to hit <ESC>,
        no [Go Back] button,
        only an [OK] button which took me into the next stage
          "Configuring the Base System", which I feel was the
          wrong thing to do in this case.
     I had to hit ^c to escape and get back to the main menu.
  Perhaps this bug should be titled
    "cdrom-retriever(??) doesn't handle /var filling up correctly"
  I'm not sure where the fault lies, I'm guessing cdrom-retriever.
  I think the answer is to provide a [Go Back] button that takes
  you to the main menu.

[wishlist bug]
  Now, to addressing the silliness:
  d-i knows that it is going to copy a bunch of .debs to /var and
  it can work out how much space it is going to take to do that
  (just sum the space taken on the cd). So it should be able to
  notice there is not enough space and do something about it.
  Note that I'm not talking about the space required to _extract_
  the .debs (eg into /usr), I realise that is very hard to compute.

  A small complication is differences in inode size between the
  source and target filesystems. I think 90% of cases could be
  covered by a fudge factor. This could be estimated to sufficient
  accuracy by copying a handful of packages across and comparing
  the .debs' sizes.

  The install manual could have a note added suggesting that /var
  should be _at least_ 512Mbyte, or at least make it more obvious
  that you need to compare the number of Mb in the packages to be
  downloaded and the free space in /var. A brief look at the manual
  (http://d-i.alioth.debian.org/manual/en.i386/) doesn't show any
  really clear statement that you need a big /var during installation.
  There are hints, but I don't think it says
   "/var too small => install fails".
  I suggest it be added to section 3.4 and/or 6.3; I will try to put
  a patch together.

  Copy _some_ of the packages and install them,
    then delete the .debs and copy another batch. repeat.

  apt-get can work out the correct ordering so that installing in
  batches is possible. I think the following shell code does this,
  but I'm not sure if it is suitable for the d-i environment.
  This code does a fixed number of packages at a time. Ideally one
  would make an automated check of the free space and ensure that
  the number is set low enough that /var never fills.

  # PKGLIST must be in the environment and contain the list of
  # packages you want to install.
  [ "unset" = "${PKGLIST:-unset}" ] && exit
  apt-get --no-act --assume-yes install $PKGLIST 2>/dev/null | \
      grep -E '^Inst ' 2>/dev/null | awk '{print $2}' > $sortedlist

  npkg=`cat $sortedlist |wc -l`
  jpkg=`expr $ipkg + $chunk`
  while [ $ipkg -lt $npkg ] ; do
      list=`awk 'NR >= '$ipkg' && NR < '$jpkg'{printf "%s ", $0}'`
      [ "X " = "X${list}" ] && break

      if apt-get install $list ; then
          apt-get --assume-yes clean 1>/dev/null 2>/dev/null
          jpkg=`expr $ipkg + $chunk`
          exit 1
  /bin/rm -f $sortedlist
  exit 0

lsmod produces the following output: (2.6.7)

Module                  Size  Used by
i830                   78724  3
ds                     18532  2
af_packet              22376  2
snd_intel8x0m          20264  0
snd_intel8x0           36460  0
snd_ac97_codec         70020  2 snd_intel8x0m,snd_intel8x0
snd_pcm                98756  2 snd_intel8x0m,snd_intel8x0
snd_timer              25668  1 snd_pcm
snd_page_alloc         11752  3 snd_intel8x0m,snd_intel8x0,snd_pcm
gameport                4704  1 snd_intel8x0
snd_mpu401_uart         7968  1 snd_intel8x0
snd_rawmidi            25184  1 snd_mpu401_uart
snd_seq_device          8200  1 snd_rawmidi
snd                    56644  8 snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
pci_hotplug            34640  0
uhci_hcd               32880  0
usbcore               114784  3 uhci_hcd
intel_agp              19836  1
floppy                 61204  0
parport_pc             35008  0
parport                41832  1 parport_pc
rtc                    12760  0
pcspkr                  3592  0
tsdev                   7328  0
mousedev               10444  2
joydev                  9888  0
psmouse                20360  0
evdev                   9568  0
i810_audio             33972  0
ac97_codec             18956  1 i810_audio
soundcore              10336  2 snd,i810_audio
3c59x                  38952  0
yenta_socket           21440  0
pcmcia_core            68132  2 ds,yenta_socket
agpgart                34152  4 intel_agp
nls_cp437               5696  1
capability              4520  0
commoncap               7200  1 capability
ide_cd                 43332  0
cdrom                  40352  1 ide_cd
ntfs                   93292  1
ext2                   72392  0
ext3                  127144  6
jbd                    62264  1 ext3
mbcache                 9348  2 ext2,ext3
ide_disk               19264  9
ide_generic             1408  0
piix                   13440  1
ide_core              142808  4 ide_cd,ide_disk,ide_generic,piix
sd_mod                 21728  0
ata_piix                8004  0
libata                 41700  1 ata_piix
scsi_mod              125004  2 sd_mod,libata
unix                   28624  46
font                    8320  0
vesafb                  6656  0
cfbcopyarea             3840  1 vesafb
cfbimgblt               3040  1 vesafb
cfbfillrect             3776  1 vesafb

Install logs and other status info is available in /var/log/debian-installer/.
Once you have filled out this report, mail it to submit@bugs.debian.org.

I seem to have deleted the installer logs...

--- End Message ---
--- Begin Message ---
We are closing this installation report for one of the following
- it was reported with a pre-lenny version of Debian
- indications in the installation report give the feeling that
  the reported problem waslying in another software, unrelated to
  D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
  fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful

The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet. 

In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.

You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.

If some problems are found, please report them with a new bug sent
against installation-reports.

Many thanks for your understanding and your help improving Debian,
past and present.

--- End Message ---

Reply to: