* Stephen Frost [EMAIL PROTECTED] [2004-01-20 15:58]:
Package: installation-reports
Version: Beta2; Downloaded: 18-Jan-2004
Stephen, can you look at this bug report, try beta4 and tell us which
issues are still left?
--
Martin Michlmayr
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL
FYI I cloned this bug and assigned it to discover. The new bug number
for the discover issue is #229736.
Thanks Gaudenz
Stephen Frost schrieb:
* Gaudenz Steinlin ([EMAIL PROTECTED]) wrote:
This looks like discover is hanging when detecting the hardware not when
loading modules.
Playing with
* 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
Stephen Frost wrote:
Couple of other points:
All known:
No progress meter on mke2fs/mounting of filesystems, it just goes to a
blank screen until that's all done.
Bug in partconf, fixed by the new partman in unstable.
When installing the 'base packages' it stops at '75%' and then waits
On Wed, Jan 21, 2004 at 09:41:24PM -0500, Stephen Frost wrote:
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
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, if not earlier...
The all does not mean all modules but all
* 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, if not
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 on another console.
Isn't there an option to spawn a
* 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 on
On Thu, Jan 22, 2004 at 02:06:33PM -0500, Stephen Frost wrote:
* 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
* 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),
Am Die, den 20.01.2004 schrieb Stephen Frost um 21:58:
Comments/Problems:
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), though it did
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 it log which module it's trying to load something? It
* 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 it
clone 228772 -1
reassign -1 busybox-cvs
severity -1 normal
tags -1 upstream confirmed
retitle -1 busybox - ash stops respoding after alt-1
thanks
On Wed, Jan 21, 2004 at 11:08:36AM -0500, Stephen Frost wrote:
- bash on con2, for whatever reason, stops responding if you hit
'alt-1' by
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 Stephen Frost um 21:58:
I tend to agree, but
* 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
Am Mit, den 21.01.2004 schrieb Stephen Frost um 18:16:
* 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
* 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.
Processing commands for [EMAIL PROTECTED]:
clone 228772 -1
Bug#228772: Install Report - discover locked, boot hung
Bug 228772 cloned as bug 228915.
reassign -1 busybox-cvs
Bug#228915: Install Report - discover locked, boot hung
Bug reassigned from package `installation-reports' to `busybox-cvs
* 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:
24 matches
Mail list logo
