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

Bug#292719: (no subject)

Package: installation-reports


Debian-installer-version: rc2
uname -a: Linux trysia 2.4.27-2-586tsc #1 Thu Dec 30 18:06:49 JST 2004 i586 GNU/Linux
Date: 1/28/2005
Method:  Network install from HTTP mirror, direct connection, PCMCIA network card.
Used rc2 floppy images.

Machine: Toshiba Tecra 500CDT
Processor: 120MHz Pentium
Memory: 144MB
Root Device: 4GB IDE
Root Size/partition table:
(parted) p                                                                
Disk geometry for /dev/hda: 0.000-4645.634 megabytes
Disk label type: msdos
Minor    Start       End     Type      Filesystem  Flags
1          0.031   4196.206  primary   ext3        boot
2       4196.206   4496.132  primary               
3       4496.133   4645.634  extended              lba
5       4496.164   4645.634  logical   linux-swap  

Output of lspci and lspci -n:
0000:00:00.0 Host bridge: Toshiba America Info Systems 601 (rev 11)
0000:00:04.0 VGA compatible controller: Chips and Technologies F65550 (rev 04)

0000:00:00.0 0600: 1179:0601 (rev 11)
0000:00:04.0 0300: 102c:00e0 (rev 04)

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

Initial boot worked:    [O]
Configure network HW:   [E]
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]


The installation went very well.  Few notes for this machine.  The kernel pcmcia drivers
for 2.4 and 2.6 do not work with a 16-bit card when the slot is set to Cardbus/16-bit
mode in the BIOS.  It must be reset to PCIC Compatible for this to work, or else the 
pcmcia-cs drivers can be used instead, since they work fine.  (For some reason the 2.6
Toshiba support is _worse_ than pcmcia-cs.)  This is why I report an error in configure
network HW above, since it was impossible to get the 16-bit network card to work without
changing the BIOS setting (which the user may have no idea is the problem why his network
card doesn't work).

Also, I had to install ifplugd and waproamd/wireless-tools myself.  It seems that these
should automatically be installed if a hotplug network card (and/or a wireless card)

Crystal sound chip has fixed resources set in the BIOS (some port ranges, irq=5 and irq=9).
Unfortunately, /etc/pcmcia/config.opts must be manually edited to reflect this exclusions,
otherwise the PCMCIA card takes over that IRQ.  Perhaps this chip should be
added to discover's hardware detection - its resources can be read from its
configuration port and appropriate action automatically taken.

The rest is nitpicks:

Only 64MB of RAM is cacheable.  The optimal setup for performance is to limit mem=63M
and then mount a slram mtd device over the rest for swap (highest swap priority).
I don't think this can be detected though.

The machine needs a APM hibernate partition (type=0xa0) for APM suspend to
work.  It would be nice if this were able to be automatically setup on machines
which report APM capability.

It would seem that installing smartmontools by default would be reasonable.  You can
use smartctl to determine whether the machine supports SMART, and if so,
change /etc/default/smartmontools to Yes so that smartd is run.  Bonus points to
automatically mail root when a disk error occurs (-m option to smartd).

It is too bad that we can't use DMI for these older special-case machines, since they
have not DMI pool.

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.

Reply to: