Package: installation-reports Boot method: CD // debian-testing-amd64-netinst.iso Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso from one, maybe 2 hours ago Date: immediately after the download / burning
Machine: homebrew, Tyan Thunder K8W board Processor: 2x Operon 240 Memory: 1GB per CPU Partitions: see below Output of lspci and lspci -n: not available 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: [E] Detect CD: [O] Load installer modules: [O] Detect hard drives: [E] Partition hard drives: [E] Create file systems: [E] Mount partitions: [ ] Install base system: [ ] Install boot loader: [ ] Reboot: [ ] Comments/Problems: expert install in German - I have on WD Raptor 74GB each on the first two SATA channels of the boards silicon image controller. On the first try the kernel printed an "ata2 is slow to respond" message and timed out the second channel after a 30 sec. Removing and re-inserting the sata_sil module did not change the outcome of the probe. (The machine has never exhibited a problem with the disks under previous Debian / Ubuntu installs.) Fearing the disk had died I tried to boot the Ubuntu kernel on it - no problem. On the next reboot it was fine. - first boot had my real nic (Broadcom gigabit) as eth0, someting else (ethernet-over-firewire maybe?) as eth1, on second boot the order was reversed. It's a known problem, I gather. If at all possible exotic interfaces should always come last. - DHCP timed out twice before succeeding. (both boots, strange) - I let the installer wipe the second disk (guided partitioning, LVM, seperate home). This gave me an error about how notifying the kernel about the partition changes failed. Despite its own warning that an immediate reboot was required the installer tried to init the partitions and failed horribly. At this point I decided to abort the install. If these are not all known issues I can try again tomorrow and get some logs.
