* Steve McIntyre ([EMAIL PROTECTED]) wrote:
At the moment the regular CD builds for amd64 are still using the
separate amd64 archive from ftbfs.debian.net. As amd64 is about to hit
testing in the mainr archive Real Soon Now, I'm planning on moving the
CD builds over to use the normal archive
* Debian Bug Tracking System ([EMAIL PROTECTED]) wrote:
This was not an NMU, but a real upload from the maintainers CVS.
Uh, this bug doesn't appear to actually be fixed by the upload which was
done. Somehow this bug got merged with a bug about ignoring the
disable/enable stuff. This bug was
* Gaudenz Steinlin ([EMAIL PROTECTED]) wrote:
This looks like discover is hanging when detecting the hardware not when
loading modules.
Playing with it some more I discovered that if I attach an strace to an
already running discover that's hung trying to close (or talk to, or
something) the
* Gaudenz Steinlin ([EMAIL PROTECTED]) wrote:
Am Don, den 22.01.2004 schrieb Stephen Frost um 03:35:
* Gaudenz Steinlin ([EMAIL PROTECTED]) wrote:
This looks like discover is hanging when detecting the hardware not when
loading modules.
Yup, looks like that's it somehow
* Matt Kraai ([EMAIL PROTECTED]) wrote:
On Wed, Jan 21, 2004 at 11:08:36AM -0500, Stephen Frost wrote:
It's really annoying. :) I'm working around it though. It's still be
nice if there was a way to kill/restart the shell on that console
somehow though, or start up another shell
* Gaudenz Steinlin ([EMAIL PROTECTED]) wrote:
Am Die, den 20.01.2004 schrieb Stephen Frost um 21:58:
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
* Gaudenz Steinlin ([EMAIL PROTECTED]) wrote:
Am Mit, den 21.01.2004 schrieb Stephen Frost um 17:08:
* Gaudenz Steinlin ([EMAIL PROTECTED]) wrote:
Am Die, den 20.01.2004 schrieb Stephen Frost um 21:58:
I tend to agree, but I have no idea which module it was trying to load..
Does
* Gaudenz Steinlin ([EMAIL PROTECTED]) wrote:
Am Mit, den 21.01.2004 schrieb Stephen Frost um 17:38:
* Gaudenz Steinlin ([EMAIL PROTECTED]) wrote:
Am Mit, den 21.01.2004 schrieb Stephen Frost um 17:08:
* Gaudenz Steinlin ([EMAIL PROTECTED]) wrote:
Am Die, den 20.01.2004 schrieb
* Gaudenz Steinlin ([EMAIL PROTECTED]) wrote:
This looks like discover is hanging when detecting the hardware not when
loading modules.
Ok.
And that's where it hung, didn't say anything after that. Over on the
console I did a ps auwx and saw 'discover --module all' in the process
list.
* Gaudenz Steinlin ([EMAIL PROTECTED]) wrote:
Am Die, den 20.01.2004 schrieb Stephen Frost um 21:58:
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
* Gaudenz Steinlin ([EMAIL PROTECTED]) wrote:
This looks like discover is hanging when detecting the hardware not when
loading modules.
Yup, looks like that's it somehow, if not earlier...
The all does not mean all modules but all types of devices. You can
modify /etc/discover.conf to see
Hey all,
Couple of other points:
No progress meter on mke2fs/mounting of filesystems, it just goes to a
blank screen until that's all done.
When installing the 'base packages' it stops at '75%' and then waits
there for quite a while, I suspect it's a DNS problem (since the network
isn't up
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:
13 matches
Mail list logo
