Your message dated Mon, 20 Aug 2012 06:04:24 +0200
with message-id <[email protected]>
and subject line Re: Bug#681656: Detect Network Hardware stops Wheezy install
has caused the Debian Bug report #681656,
regarding Detect Network Hardware stops Wheezy install
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.)


-- 
681656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681656
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debian-installer
Version: 20120508

Just grabbed this ISO image:

debian-wheezy-DI-b1-i386-kde-CD-1.jigdo
<http://cdimage.debian.org/cdimage/weekly-builds/i386/jigdo-cd/debian-wheezy-DI-b1-i386-kde-CD-1.jigdo>

Which is dated 15-JUL-2012 via Jigdo (verified Checksum as ok)

System is currently running Lenny (oldstable) and I'm planning on wiping it
and installing Wheezy...

However, the Wheezy installer stops at Detecting Network Hardware.. The
mouse cursor can freely move around the screen and it looks like the
installer doesn't try to detect any network hardware (no progress bar!).

Here are 3 screenshots..
http://imgur.com/a/3Fp0T

Not sure what to do from here as there doesn't seem to be any way to
continue the install.

--- End Message ---
--- Begin Message ---
Quoting [email protected] ([email protected]):
> Sorry for my bad english...
> I've the same problem, which DIDN'T appear in the ALPHA release. This bug is 
> shown only in the BETA WHEEZY release.
> If there is a non-free firmware, the installer stopped the installation.
> A solution can be insert a USB pendrive with the firmwares, it works for me.
> 
> Please, solve this bug, it's very important in my opinion. 


This is a known problem that has been identified in the kernel and
currently worked around in mountmedia. To go  around it, you need to
use daily built images.


Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to