[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#253033: FWD: Re: Bug#253033: installation-reports



----- Forwarded message from Peter Yellman <peter.yellman@cox.net> -----

From: Peter Yellman <peter.yellman@cox.net>
Date: Mon, 07 Jun 2004 10:04:07 -0400
To: Joey Hess <joeyh@debian.org>
Subject: Re: Bug#253033: installation-reports
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007

Joey,

Thanks for the reply.  Your information about the absence of netcfg udeb 
qualifies as a complete explanation for me.  That is surprising, to say 
the least.  The install was for a server system, so the lack of X 
packages never occured to me.

As for paraphrasing the error message, I didn't like having to do it, 
but I would have to do another install to get the exact message!  I 
looked through the install logs before sending the report, but could not 
locate the message. At least here's a little more info. It occured (more 
than once) in expert mode. After being given the opportunity to select 
which modules to load, the installer then goes through giving the 
opportunity to add parameters to each module; it was after selecting 
"Continue" on the selected network module that the error occured.

FYI -- Before this experience, I'd never done anything but netinstall 
(with the new installer).  However, on this occasion I just couldn't get 
the base system installed over the network, despite about 5 tries -- 
always had problems downloading (tried 4 or 5 mirrors), which I'd rarely 
had before.  Of course I was using b3, I should probably burn a b4 disk 
and give it another try.

Finally, I discovered something a litle more serious about this last 
install from the full CD, which I thought had been successful; the 
binutils package had not been fully installed - a number of the binaries 
were missing.  This probably had nothing to do with my original problem 
(no network setup), but I have to wonder if having to step back through 
the install process a number of times while applying my workaround 
(activating the network card in an alt term) contributed to this glitch. 
 Although my system is stable, I now am left wondering what other key 
packages may not be correctly or fully installed.  I would like to add 
my voice to those calling for adding netcfg to the full CD set.

Thanks,
Peter Yellman

Joey Hess wrote:
>Peter Yellman wrote:
>
>>http://cdimage.debian.org/pub/cdimage-testing/cd/jigdo-area/i386/sarge-i386-1.jigdo 
>>
>>Multiple attempts -- at least 5.  Tried linux, expert, linux26, 
>>expert26. Never offered the opportunity to configure network.  Tried 
>>with 2 different NICs - a common Macronix, and an Intel e100.  Installer 
>>seemed to see NIC -- module was loaded in alt console, but never started 
>>network configuration.
>
>
>This is a known problem with the full CDs, depsite numerous requests to
>the debian-cd guys to fix this, they do not include the netcfg udeb
>necessary to get the network configured. They also don't include a
>usable set of packages to get X working, or some hardware working
>post-install, so I cannot recommend you use them if you want a working
>system -- use the netinst CDs.
>
>
>>Selecting network module in expert mode resulted 
>>in message to the effect "requested module not available".
>
>
>Please don't paraphrase error messages. What exactly did you select from
>the menu, and what was the exact error message you received?
>


----- End forwarded message -----

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature


Reply to: