[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#301461: d-i rc3 installation report

Package: installation-reports

Debian-installer-version: sarge-businesscard ISO of RC3 on i386 arch, downloaded 3/24/2005 from cdimage.debian.org
uname -a: Don't remember
Date: approximately 8:00PM Central, March 25, 2005
Method: Booted from businesscard CD.

Machine: Dell Inspiron 8200 Laptop
Processor: Pentium 4 ~ 1.6 GHz
Memory: 256M
Root Device: businesscard CD?
Root Size/partition table: Didn't get to partitioning.
Output of lspci and lspci -n: Didn't realize I'd need this ahead of time.

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:              [ ]
Load installer modules: [ ]
Detect hard drives:     [ ]
Partition hard drives:  [ ]
Create file systems:    [ ]
Mount partitions:       [ ]
Install base system:    [ ]
Install boot loader:    [ ]
Reboot:                 [ ]


I'm doing testing for my main system, for which I intend to install the sarge release (report is for another system).
The installer worked well until I got to the DHCP network configuration.  I received a message that the DHCP configuration had timed out.  I've gotten this message before on my main system when testing d-i (rc 1 or 2, not reported).  Tried again, but no luck.  I would do this manually, but I don't know how.  The installer didn't give me an option for changing the timeout.  I've used DHCP on this LAN before, but have reason to believe the router (SMC 7004VWBR) is slow to respond.
As much as I want to support Debian, I'm a bit put out about the bug reporting procedure.  Is there a good way to report bugs without sending email info?  Would it be feasible to allow the installer to prepare the above information, and allow users to just save it and annotate it before sending?
I applaud everyone's effort on Debian and d-i in
 particular.  I really want to learn Linux.  The main obstacle has always been getting Linux to a known state, and then being able to incrementally test and return the system to a known backup state.  Once the installer runs to completion and I can image my system, I feel like I'll be home free.  I am a pretty technical person, but I'm not steeped in Linux know-how, despite having run it before and following it since as far back as 1995.

Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around

Reply to: