Your message dated Wed, 08 Sep 2010 03:57:33 +0000
with message-id <e1otbmv-0003pm...@ravel.debian.org>
and subject line Closing old installation report #255369
has caused the Debian Bug report #255369,
regarding installation-reports: TC1 cannot insmod network modules -
installation cycles
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 ow...@bugs.debian.org
immediately.)
--
255369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=255369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Version: Test Candidate 1
Severity: important
On starting the installer on an old AMD-K6, the installer failed to
detect the ISA network card, which I know to work with the "ne" module.
On selecting "ne" to be used when prompted to choose a network module,
the screen blanked grey, paused, then d-i appeared to restart. The
same occured when I tried a variety of other network modules.
Switching to tty2, I found that insmodding ne showed a series of ugly
errors regarding "unresolved symbols". I do not have the exact text,
though I can fetch it if required by rerunning the installation.
While insmod failed, using `modprobe ne io=0x300` was successful and the
next time d-i cycled I was not prompted to select a network card module.
When installation finished, I was still unable to use insmod network
modules, with the same error. However, once the machine had been
rebooted, insmod worked along with modprobe.
My CPU is a 200mhz AMD K6.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i586)
Kernel: Linux 2.4.26-1-386
Locale: LANG=en_GB, LC_CTYPE=en_GB
--- 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 ---
