Package: installation-reports Version: Beta2; Downloaded: 18-Jan-2004 Severity: important INSTALL REPORT Debian-installer-version: Beta2; 18-Jan-2004; http://people.debian.org/cdimage/testing/netinst/i386/beta2/sarge-i386-netinst.iso uname -a: N/A, didn't get that far Date: 19-Jan-2004 Method: Booted off the netinst ISO and installed from it. Machine: Sony Vaio PCG-FRV28 Processor: Intel Pentium 4 - 2.8Ghz Memory: 512MB Root Device: IDE, single disk on primary controller (/dev/hda) Root Size/partition table: (From memory): /dev/hda1 - 5G 'recovery' /dev/hda2 - 10G NTFS (WinXP) /dev/hda3 - 128MB root /dev/hda4 - Extended /dev/hda5 - 10G NTFS (WinXP) /dev/hda6 - 3G /usr /dev/hda7 - 1G /var /dev/hda8 - 5G /home Output of lspci: Unfortunately I havn't got it, the install didn't make it far enough to where I could get it off using the network. If I can run it from the install CD I could hand copy it, if necessary. Base System Installation Checklist: Initial boot worked: [O] Configure network HW: [O] Config network: [O] - only eth0 :( 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: [E] Install boot loader: [O] Reboot: [E] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: Alright, first a few bitches: - Waiting for DHCP to time out sucked, I know it won't work, eth0 isn't even connected to anything - Couldn't configure my wireless card (eth1), though it did appear to be detected and looked operational - bash on con2, for whatever reason, stops responding if you hit 'alt-1' by accident (like when going for alt-f1 to get back to the installation), this is *very* annoying since you have to restart the install to get a shell to work in, it'd be nice to have a way to forcibly reset the shell or bring up another one or something - Every other step it appears to 'detect hardware' or whatever, what's with that? I don't have a floppy on the machine but every time it takes a few seconds to try and load it. Now, the big problems: - discover just hung for a *long* time (>30 minutes), it was called with 'modules-detect all', iirc. This was in the postinst of discover after the 'base system' had been installed and it was installing 'extra components', iirc. I didn't see any kernel oops or anything abnormal, and I was able to kill discover off (though it just restarted and got stuck at the same place). Eventually I just hacked up the postinst to act like it didn't find anything (MODULES=""). This got me through the rest of the install and to reboot. - On boot, everything looked alright except after saying something like 'lp0: detected blah blah' nothing else showed up. It looked to have just hung at that point. Maybe it was trying to load up some framebuffer or maybe X is supposted to start at that point? I dunno, but I couldn't do anything, none of the other consoles appeared to be up or anything. I recall being warned that there might be a problem with the current X in Debian and the graphics card in my laptop (ATI Radeon IGP 345M 64MB (shared)), though 4.3 (released *how* long ago?) supports it. Don't know if that's a problem here or not. Hope this helps, I'm thinking about trying a daily-build or something. If anyone has any comments/suggestions on things I could try, I'm all ears. I'd really like to get Debian on the box, and heard d-i was starting to get pretty decent... Thanks, Stephen
Attachment:
signature.asc
Description: Digital signature