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

Re: Missing network interface after installing using 2.2.23



Hello again, please see below...

----- Original Message -----
From: "Ray Knight" <audilvr@speakeasy.org>
To: "George Bingham" <gbingham@us.ibm.com>
Cc: "Debian 68k Mailing List" <debian-68k@lists.debian.org>
Sent: Friday, January 17, 2003 10:18 PM
Subject: Re: Missing network interface after installing using 2.2.23


> On Fri, 2003-01-17 at 15:42, George Bingham wrote:
> >
> >
> >
> >
> > Hello,
> >
> >     I am installing Debian onto my Quadra 660AV.
> >     I am using the network to do the installation. My network is a
little
> > home network where I have DSL, a router and my quadra is hanging off
that.
> > The router is using DHCP for internal clients. All is well when the
install
> > program gets it's stuff from debian.org during the install procedure,
but
> > then at first boot, the final setup steps it asks me to setup a PPP
client
> > for connecting to the network.
> >
> >    In other words, I think that although the install kernel sees my
built
> > in ethernet, the regular kernel (2.2.23) doesn't see it. What do I do to
> > get the regular kernel to see my ethernet? I'm thinking I'm missing
> > parameters on the kernel command line??
> >
>
> That question is just part of the standard post-install configuration.
> Just answer no.  If you switch to another console, log in and run
> ifconfig you should see the connection you configured during
> installation.
>
> Ray
>
>
>
>
> --
> To UNSUBSCRIBE, email to debian-68k-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
>

    This time while installing, I made sure to install the net module called
'nbd' - Not sure
if it's the right one (This is on a Quadra 660 AV).

    Now after it's first boot, when it gets to the part where it's going to
use APT to install
stuff, I tell it I want to use the network to install, either ftp or http,
and go through the screens to pick which servers and all, and when it tests
the apt sources I always get:

"Failed to fetch <url> Something wicked happened resolving
<hostname><protocol> (-3)"

When I go into another terminal, if I type 'ifconfig' it shows eth0's
hardware address, "UP BROADCAST RUNNING MULTICAST ...."  and after some TX
and RX stats, it shows 'interrupt: 24 base address:0xc000

Then it shows 'lo' and another set of stats for that which is Link encap:
Local Loopback' (I'm not sure if I'll always have that or if it's falling
back to the local loopback cause it can't see beyond the machine?)

Then it shows 'tunl0' which shows IPIP Tunnel UP RUNNING NOARP ....

But with this all setup, I still can't get APT to see any other machines....

I've tried running 'dhclient' but nothing happens, not sure what I need to
put into a dhclient.conf file for the simple DSL modem to router to machines
network I have.

Any help would be appreciated.

Thanks,

George



Reply to: