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

Re: Missing network interface after installing using 2.2.23

On Sat, 2003-01-18 at 00:02, George Bingham wrote:
> Hello again, please see below...
> From: "Ray Knight" 
> > 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.
> >
>     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).
This is not necessary.  You shouldn't have to load any modules to use
Ethernet as all the drivers are linked into the kernel.

>     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
This shows that your on-board Ethernet card is recognized.  Does it show
an IP address similar to the second line below?

eth0      Link encap:Ethernet  HWaddr 08:00:07:66:DD:DA  
          inet addr:  Bcast: 
          RX packets:203089 errors:0 dropped:0 overruns:0 frame:0
          TX packets:113234 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:60454274 (57.6 MiB)  TX bytes:42528154 (40.5 MiB)
          Interrupt:3 Base address:0xa000 

If not your dhclient isn't assigning an address.  I don't use dhcp, I
assign all my systems static IP addresses and run my own internal DNS
server, so I can't help with this.  You could assign a static IP address
to verify that dhcp is the problem.

> 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.

Perhaps someone else on the list more familiar with dhclient can provide
the help you require.


Reply to: