Your message dated Wed, 08 Sep 2010 03:58:22 +0000
with message-id <[email protected]>
and subject line Closing old installation report #401962
has caused the Debian Bug report #401962,
regarding installation-reports Sun v100 / Etch RC1 Installer
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
401962: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401962
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: installation-reports
Boot method: < network rarpd/tftpd >
Image version: <
http://ftp.nl.debian.org/debian/dists/testing/main/installer-sparc/rc1/image
s/sparc64/netboot/2.6/boot.img >
Date: < 12/06/2006 >
Machine: < Sun SunFire v100>
Processor: 650mhz
Memory: 2048mb
Partitions: < n/a >
Output of lspci -nn and lspci -vnn:
[r...@v100-1 ~] lspci
zsh: command not found: lspci
[r...@v100-1 ~] apt-get install lspci
Reading package lists... Done
Building dependency tree... Done
E: Couldn't find package lspci
[r...@v100-1 ~]
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [O]
Detect network card: [E]
Configure network: [E]
Detect CD: [E]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Install base system: [O]
Clock/timezone setup: [O]
User/password setup: [O]
Install tasks: [O]
Install boot loader: [O]
Overall install: [O]
Comments/Problems:
CD Installation: Boots into installer from CD, but fails to detect CD-ROM
drive. Using built-in Sun v100 CD-ROM Drive.
Network Installation: (via rarpd/tftp) using Etch RC1 boot.img file, system
boots, network is mis-detected as "dmfe". Network won't work via DHCP,
manual configuaration, etc. Had to get to shell, and then ran following
commands:
Modprobe -r dmfe
Modprobe -r tulip
Modprobe tulip
Ifconfig eth0 x.x.x.x netmask y.y.y.y
Route add default gw z.z.z.z
Echo 'nameserver n.n.n.n" > /etc/resolve.conf
Then network-based install works properly.
After reboot, system still prefers DMFE for networking and does not work at
all, must do the same modprobe -r dmfe/tulip, then modprobe tulip, and then
bring the interface up. Can't blacklist DMFE in udev, it still loads
somehow *shrug*. I am now rebuilding the kernel without DMFE support to see
if I can just make it run with tulip.
Thanks,
Jared Valentine
[email protected]
--- End Message ---
--- Begin Message ---
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
Installer.
- indications in the installation report give the feeling that
the reported problem waslying in another software, unrelated to
D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful
The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet.
In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.
You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.
If some problems are found, please report them with a new bug sent
against installation-reports.
Many thanks for your understanding and your help improving Debian,
past and present.
--- End Message ---
