Bug#233007: Install report: Toshiba A100
Package: installation-reports
INSTALL REPORT
Debian-installer-version: 2004-02-12 http://gluck.debian.org/cdimage/testing/daily/i386/current/sarge-i386-netinst.iso
uname -a: Linux comp-14 2.4.24-1-386 #1 Tue Jan 6 19:18:04 EST 2004 i686 GNU/Linux
Date: 2004-02-14 15:00 EST
Method: CD (sarge-i386-netinst.iso), boot from CD. Could not complete net
install: NTLM (Microsoft ISA) proxy not supported :(
Machine: Toshiba Portege A100
Processor: Intel Pentium-M 1.4 GHz
Memory: 256 MB
Root Device: IDE Toshiba MK4025GAS
Root Size/partition table: <Feel free to paste the full partition
table, with notes on which partitions are mounted where.>
Output of lspci:
00:00.0 Host bridge: Intel Corp. 82852/855GM Host Bridge (rev 02)
00:00.1 System peripheral: Intel Corp.: Unknown device 3584 (rev 02)
00:00.3 System peripheral: Intel Corp.: Unknown device 3585 (rev 02)
00:02.0 VGA compatible controller: Intel Corp. 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corp. 82852/855GM Integrated Graphics Device (rev 02)
00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 03)
00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 03)
00:1d.7 USB Controller: Intel Corp. 82801DB USB2 (rev 03)
00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 83)
00:1f.0 ISA bridge: Intel Corp. 82801DBM LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corp. 82801DBM Ultra ATA Storage Controller (rev 03)
00:1f.5 Multimedia audio controller: Intel Corp. 82801DB AC'97 Audio Controller (rev 03)
00:1f.6 Modem: Intel Corp. 82801DB AC'97 Modem Controller (rev 03)
01:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)
01:08.0 Ethernet controller: Intel Corp. 82801BD PRO/100 VE (MOB) Ethernet Controller (rev 83)
01:0a.0 Ethernet controller: Unknown device 168c:0013 (rev 01)
01:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to Cardbus Bridge with ZV Support (rev 32)
01:0b.1 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to Cardbus Bridge with ZV Support (rev 32)
01:0d.0 System peripheral: Toshiba America Info Systems SD TypA Controller (rev 03)
Base System Installation Checklist:
Initial boot worked: [O ]
Configure network HW: [E ] ([B])
Config network: [O ]
Detect CD: [O ]
Load installer modules: [O ]
Detect hard drives: [O ]
Partition hard drives: [E ] ([B])
Create file systems: [O ] ([B])
Mount partitions: [O ] ([B])
Install base system: [O ]
Install boot loader: [E ]
Reboot: [O ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
^^ Should be another option, e.g. [B] or [P] mean it works (not an "error"),
but works badly or poorly.
Comments/Problems:
Choose language:
ar - miscoded (rendered with ?????)
ru - words cutoff (po-russ instead of po-russki)
Network:
DHCP fails on built-in wireless (works OK on built-in ethernet port).
Presumably the wireless port is PCI device 01:0a.0. It's an Atheros AR5001X+
Wireless Network Adapter (Ethernet 802.3).
Partitioning:
Only cfdisk offered standard for partitioning??? Seems inferior to the
alternatives. Was not able to create more logical partitions, after
creating two primary ones (the original NTFS and the new bootable linux
partition).
Exiting from there into the full menu, there are then three partitioning
options, which is confusing. I need to partition the drive three times???
This ought to be organised more clearly, so I'm not tempted to think I need
three partitionings.
Partition the Storage Devices: resize partition does not support ntfs,
which pretty much rules out any easy dual-boot set up from any modern
MS Windows system. I had to use Partition Magic to do it.
Cannot select the FREE SPACE after the windows partitions (15.7GB primary
ntfs, 8.9 GB logical fat32): "Partition the
storage devices" simply jumps straight back to the menu of partitions
instead of the menu of partitioning actions (I can get to the action menu when
I select the windows partitions). So this option (is it parted or partman?)
is useless.
"Automatically partition hard drives" is no good - it says it will destroy
all data on all disks. I can't wipe the windows partitions here! It would
make more sense if this automatically partitioned available free space,
rather than the entire drive.
So it's back the the ugly default cfdisk, which could not create more
logical partitions after making 2 primary ones. So I make the linux
partitions all logical using cfdisk. This is too complicated!
Configure and mount partitions:
When choosing the mount point (/, /usr, /boot, etc), the full choice of
mount points is always in the list, even if some of them have already been
selected. The list should be updated to only show unassigned mount points -
you can't mount two partitions to the same directory (not in Linux anyway,
maybe Hurd can).
Screen goes blank while configuring mounts, which takes a good 30 seconds.
A message should be displayed describing what is happening and "please wait".
Install boot loader (GRUB):
I wanted to install grub to (hd0,2), to place it on the first linux
partition rather than the first partition on the drive, in order to test boot
compatibility with the pre-installed Windows systems. But d-i failed,
saying "Executing 'grub-install (hd0,2)' failed. This is a fatal error."\
Later, installing to (hd0), the installer freezes at "20%--- Determining
GRUB boot device". Had to force a reboot.
After reboot, I had to configure and mount partitions again. But the
filesystems on them had to be recreated again. It should be possible to
simply mount them without recreating them. This wastes time reinstalling
the base system all over again, when I should be able to go straight to
"install GRUB" again. But some corruption from the previous broken GRUB
install seems to have messed data up (the second base install failed
anyway), so in fact I needed to recreate the filesystems anyway.
Install the base system:
Naturally, a 2.6 kernel would be nice (why wasn't this question asked the
first time?) Only 2.4.24-1 is currently available. Installing it, I get an
error message, saying:
/usr/sbin/mkinitrd: Cannot determine root device. Failed to creat
initrd image.
Fairly serious, wouldn't agree. (why didn't this error appear the first time?)
Reboot again, proceed again in cfdisk by deleting partitions and writing the
new table (with deletions) before renewing. Only reset / and /usr.
This time, after reinstalling base again, I install grub onto (hd0) and all
is working.
Grub is pretty darn ugly don't you think? Can I have graphical lilo back
again...?? ;)
I notice that after reboot, there are still some memory disks (cramfs or
tmpfs), but they aren't listed in /etc/fstab. Should they really be there?
How do I get rid of them?
=======================
Debian base system configuration:
my computer name (similar to "COMP-14") was rejected, even though it
conforms to the instructions on the page (the '-' is in the middle, not
beginning or ending).
Timezone configuration is done twice.
My computer is asked for again, I learn that the capital letters are what
was rejected: "comp-14" is accepted. Is this really appropriate behaviour?
Configuring apt: configuring proxies is not supported in interface. Anyway,
apt does not support NTLM (Microsoft ISA) proxies anyway, which should be
fixed now that NTLM support for free software is available (see mozilla 1.6,
samba3).
Base config keeps looping - I'm back to timezone again. Why? This happened
after asking me if I want to use tasksel or aptitude or dselect to choose
more packages (I chose "nothing", after which it returned to timezone). Is
it because testing apt sources failed (I have not yet configured the proxy
server - should this be another debconf question?).
Choosing "aptitude" instead of "nothing" I loop back to timezone again. This
is getting boring. I kill the installation with "shutdown" from another
virtual console. I have more control after this - base-config now lets me
get to a menu where I can choose what to do next. It still jumps to timezone
after "select packages" within that menu list, but I can choose to go
straight to "install packages" (which also jumps to timezone) or to
"configure MTA" (which continues to "finish configuring base system").
I can edit /boot/grub/menu.lst to add the windows partition, and the Windows
environment is able to boot (the IT staff will be happy).
In the new system, I can't mount windows shares (smbfs), I get the error
smbfs: mount_data version 1684370019 is not supported
which does not sound good. (Mounting the shares works on my old sid machine).
Let me know if you the files from /var/log/debian-installer.
Drew
Reply to: