Package: installation-report Using a Daily netinst i386 .iso, 2006-10-18 13:26 according to the HTTP server
(Reporting manually, reportbug keeps dying on something -_-)
Boot method: CD-netinst
Image version: i386 Daily 2006-10-18
Date: Repeatedly over the weekend of 2006-10-21 and 2006-10-22
Machine: Whitebox w/HPT370 controller (ABit SA6-R motherboard)
Processor: PIII 1gHz
Memory: 512 MB
Partitions:
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/mapper/all-root
ext3 20642428 698220 18895632 4% /
tmpfs tmpfs 258444 0 258444 0% /lib/init/rw
udev tmpfs 10240 44 10196 1% /dev
tmpfs tmpfs 258444 8 258436 1% /dev/shm
/dev/hde1 ext3 93307 24764 63726 28% /boot
/dev/mapper/all-home
ext3 51606140 18966864 30017836 39% /home
/dev/mapper/all-video
xfs 168517228 46627880 121889348 28% /video
/dev/hdf5 ext3 76932488 8679640 64345316 12% /oldhome
(/dev/mapper/all also contains a swap partition, and is /dev/hde2)
Output of lspci and lspci -n:
00:00.0 Host bridge: Intel Corporation 82815 815 Chipset Host Bridge and Memory
Controller Hub (rev 04)
00:01.0 PCI bridge: Intel Corporation 82815 815 Chipset AGP Bridge (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 11)
00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 11)
00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 (rev 11)
00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB (Hub #1) (rev 11)
00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus (rev 11)
00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB (Hub #2) (rev 11)
00:1f.5 Multimedia audio controller: Intel Corporation 82801BA/BAM AC'97 Audio
(rev 11)
01:00.0 VGA compatible controller: ATI Technologies Inc R350 AH [Radeon 9800]
01:00.1 Display controller: ATI Technologies Inc Radeon R350 [Radeon 9800]
(Secondary)
02:01.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100]
(rev 08)
02:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
02:06.0 Mass storage controller: Triones Technologies, Inc.
HPT366/368/370/370A/372/372N (rev 04)
00:00.0 0600: 8086:1130 (rev 04)
00:01.0 0604: 8086:1131 (rev 04)
00:1e.0 0604: 8086:244e (rev 11)
00:1f.0 0601: 8086:2440 (rev 11)
00:1f.1 0101: 8086:244b (rev 11)
00:1f.2 0c03: 8086:2442 (rev 11)
00:1f.3 0c05: 8086:2443 (rev 11)
00:1f.4 0c03: 8086:2444 (rev 11)
00:1f.5 0401: 8086:2445 (rev 11)
01:00.0 0300: 1002:4148
01:00.1 0380: 1002:4168
02:01.0 0200: 8086:1229 (rev 08)
02:02.0 0200: 10ec:8139 (rev 10)
02:06.0 0180: 1103:0004 (rev 04)
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: [E]
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: [E]
Comments/Problems:
I hit the following problems:
As well as #392858, the ppp-udeb.postinst script has a number of
other bugs. (ppp-udeb 2.4.4rel-2)
On line 34, the $P needs to be somewhere other than directly between
the -I and the $1, as when $P has the value -U, pppoe-discovery
tries to use the ethernet device -U, which fails.
Also on line 34, the file stderr is redirected to is /tmp/ppp-errors
but for the rest of the file this is referred to as /tmp/ppp-error,
causing detection of the timeouts to fail.
I suspect the rm -f /tmp/probe-finished on line 31 probably should be
a rm -f /tmp/probe-finished /tmp/ppp-error and moved to before line 34
so the script doesn't detect timeouts from a previous loop iteration.
There's a typo on line 39 "Timout".
Line 51 (log probe-finished) prolly should be outside the while [ ! -f
/tmp/probe-finished ]
It'd be nice if pppoe-discovery returned immediately on detection of
any PPPoE Access Concentrator, rather than continuing to listen for
further reponses, as it is being used only to determine if any access
concentrators are out there.
This'd reduce false timeout logs.
Anyway, with these fixes, it seems to work OK, although the resolv.conf test on
line 196 also seemed to fail for me after the pppoe detection had succeeded but
ppp failed to dial up, so I suspect that -e is the wrong test. (I'm guessing
it's returning false for a dangling symlink) or the ln -s should be ln -sf.
Even though the script returned failure, the link came up and things worked.
==
The HPT370 problem comes up because GRUB uses a hard disk sector which the
HPT370 BIOS uses for its own purposes.
The hard solution is to have the stage1_5 file (or the equivalent under grub2,
both suffer this problem) write to a later sector.
The easy solution would be to detect if we're installing grub onto a HPT370
disk, and use the Debian MBR with grub installed onto the /boot partition as
when doing multiboot.
Details of the grub/HPT370 conflict at [1], and the hard fix at [2]. I couldn't
see an obvious way to do the hard fix using the install-grub scripts, nor how
it all works under grub2.
There's also a relevant thread at [3]... Apparently RedHat has patched their
grub to detect and work around this... I haven't confirmed this, and I think
the "easy solution" above is prolly a cleaner fix in this case.
This bug manifests as an Error 17 (for me) or error 21 (seen on google) on
rebooting, after everything appears to be working fine. If someone has a RAID
array set up, it'll prolly manifest as the array losing it's 'nana. ^_^
[1] http://savannah.gnu.org/bugs/?2394
[2] http://lists.gnu.org/archive/html/bug-grub/2004-07/msg00113.html
[3] http://www.mail-archive.com/bug-grub@gnu.org/msg09759.html
Yes, this bug has been open but uncommented on since 2003... -_-
==
I didn't format the xfs partition with d-i, as the wiki
suggested that was broken, and I'd already had to reinstall
once due to changing from another board to the HPT370 board.
--
Paul "TBBle" Hampson, [EMAIL PROTECTED]
Shorter .sig for a more eco-friendly paperless office.
pgp4zdSzlhUZY.pgp
Description: PGP signature
