Your message dated Sun, 30 Jul 2006 23:55:17 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380543: Package: installation-reports
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
Boot method: tftp network boot , etch daily build (and beta2 too)
Image version: 2006-07-30 daily build
Date: 2006-07-30
Machine: Hand built machine
Processor: Sempron64 2800 (in 32bit mode)
Memory: 512MB
Partitions:
df -T
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/md1 ext3 74999320 789968 70399544 2% /
tmpfs tmpfs 250372 0 250372 0% /dev/shm
tmpfs tmpfs 10240 76 10164 1% /dev
sfdisk -d /dev/sda
# partition table of /dev/sda
unit: sectors
/dev/sda1 : start= 63, size= 3903732, Id=fd
/dev/sda2 : start= 3903795, size=152392590, Id=fd, bootable
/dev/sda3 : start= 0, size= 0, Id= 0
/dev/sda4 : start= 0, size= 0, Id= 0
sfdisk -d /dev/sdb
# partition table of /dev/sdb
unit: sectors
/dev/sdb1 : start= 63, size= 3903732, Id=fd
/dev/sdb2 : start= 3903795, size=152392590, Id=fd, bootable
/dev/sdb3 : start= 0, size= 0, Id= 0
/dev/sdb4 : start= 0, size= 0, Id= 0
flix:~#
<df -Tl will do; the raw partition table is preferred>
Output of lspci and lspci -n:
00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:05.0 VGA compatible controller: nVidia Corporation C51G [GeForce
6100] (rev a2)
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3)
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller
(rev a1)
00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller
(rev a1)
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio
(rev a2)
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Miscellaneous Control
01:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23
IEEE-1394a-2000 Controller (PHY/Link)
00:00.0 0500: 10de:02f1 (rev a2)
00:00.1 0500: 10de:02fa (rev a2)
00:00.2 0500: 10de:02fe (rev a2)
00:00.3 0500: 10de:02f8 (rev a2)
00:00.4 0500: 10de:02f9 (rev a2)
00:00.5 0500: 10de:02ff (rev a2)
00:00.6 0500: 10de:027f (rev a2)
00:00.7 0500: 10de:027e (rev a2)
00:02.0 0604: 10de:02fc (rev a1)
00:03.0 0604: 10de:02fd (rev a1)
00:04.0 0604: 10de:02fb (rev a1)
00:05.0 0300: 10de:0242 (rev a2)
00:09.0 0500: 10de:0270 (rev a2)
00:0a.0 0601: 10de:0260 (rev a3)
00:0a.1 0c05: 10de:0264 (rev a3)
00:0a.2 0500: 10de:0272 (rev a3)
00:0b.0 0c03: 10de:026d (rev a3)
00:0b.1 0c03: 10de:026e (rev a3)
00:0d.0 0101: 10de:0265 (rev a1)
00:0e.0 0101: 10de:0266 (rev a1)
00:0f.0 0101: 10de:0267 (rev a1)
00:10.0 0604: 10de:026f (rev a2)
00:10.1 0403: 10de:026c (rev a2)
00:14.0 0680: 10de:0269 (rev a3)
00:18.0 0600: 1022:1100
00:18.1 0600: 1022:1101
00:18.2 0600: 1022:1102
00:18.3 0600: 1022:1103
01:0e.0 0c00: 104c:8024
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: []
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: [E]
Reboot: [O]
Comments/Problems:
The machine was installed remotely over the serial line, and
though it mostly works when you try and install lilo from the menu it
has a syntax error in the serial line that it sticks in the lilo.conf
file which causes the installation stage to fail.
It currently puts in
serial=0,115200n8--
but should only put in
serial=0,115200n8
Apart from that the installer works fine!
Cheers,
--
Peter Taphouse
Bytemark Hosting
http://www.bytemark.co.uk
+44 (0)845 004 3 004
--- End Message ---
--- Begin Message ---
On Sunday 30 July 2006 23:03, Pete Taphouse wrote:
> Oops, Sorry about that. We use our own pxe config file and I'd made a
> typo on the prompt line (no space between console=ttyS0,115200 and the
> --) . Feeling a little foolish now :-)
No problem. That does make the installation successful and thus allows me
to close your report.
Thanks for submitting it.
Cheers,
FJP
--- End Message ---
