Re: [gentoo-user] Networking problems on new install?

2008-04-07 Thread Mick
On Sunday 06 April 2008, Volker Armin Hemmann wrote:
> On Sonntag, 6. April 2008, Les Henderson wrote:
> > I recently bought a laptop that has an onboard Realtek RTL8101E NIC. I
> > installed a system to dual boot with Windows Vista (which was
> > preinstalled, which I'd really like to be able to get away from
> > eventually) using the amd64 2007.0 liveDVD to do a networkless
> > install. The LiveDVD would load the r8169 module, but networking still
> > would not work (dhcpcd eth0 times out). I used the LiveDVD to emerge
> > the 2.6.19-r5 kernel. I installed the r8101 module from the RealTek
> > site, and while this finally would allow me to see eth0 under my own
> > environment (I could see it booting from the LiveDVD as well),
> > networking still would not work (dhcpcd eth0 times out). Looking
> > around the gentoo forums I've seen suggestions to use either the r8169
> > or r8101 modules (depending on which post I read) using a kernel
> >
> > >2.6.19 and <2.6.22, that finally the module may work. I don't have a
> >
> > spare gentoo box on which I can grab this using emerge. Any
> > suggestions on how I can do this? My windows system has network
> > access, and I can mount my windows partition. Is there a better way to
> > get this NIC working?
>
> install a recent kernel like 2.6.23 or 2.6.24 (just download the sources,
> unpack them in /usr/src, create the linux symlink). And use the in kernel
> r8169 drivers.
>
> Don't use 'vendor' drivers if you don't have to!
>
> > Actually my ultimate goal is to get my Marvell TOPDOG wireless NIC
> > working, but it appears to me that I will need to get ndiswrapper and
> > perhaps wine for this to happen, neither of which are on the LiveDVD.
> > I'm hoping to get a network connection so I can get enough packages to
> > update the system enough to get this working and solve other hardware
> > issues resulting from me having a new laptop designed to work with
> > Vista.
>
> you might want to use the 2008-beta livecd for this - this way you don't
> have with a lot of very messy stuff (like expat). And wine is.. evil. Every
> release breaks something. If your stuff works at all.

Another thing to consider if your card is seen by ifconfig (i.e. you probably 
have found the right driver for the card) but dhcpcd still times out:  you 
may need to recompile the dhcpcd client with the vram USE flag.  Some dhcp 
server implementations won't play nicely without it.
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Networking problems on new install?

2008-04-06 Thread Volker Armin Hemmann
On Sonntag, 6. April 2008, Les Henderson wrote:
> I recently bought a laptop that has an onboard Realtek RTL8101E NIC. I
> installed a system to dual boot with Windows Vista (which was
> preinstalled, which I'd really like to be able to get away from
> eventually) using the amd64 2007.0 liveDVD to do a networkless
> install. The LiveDVD would load the r8169 module, but networking still
> would not work (dhcpcd eth0 times out). I used the LiveDVD to emerge
> the 2.6.19-r5 kernel. I installed the r8101 module from the RealTek
> site, and while this finally would allow me to see eth0 under my own
> environment (I could see it booting from the LiveDVD as well),
> networking still would not work (dhcpcd eth0 times out). Looking
> around the gentoo forums I've seen suggestions to use either the r8169
> or r8101 modules (depending on which post I read) using a kernel
>
> >2.6.19 and <2.6.22, that finally the module may work. I don't have a
>
> spare gentoo box on which I can grab this using emerge. Any
> suggestions on how I can do this? My windows system has network
> access, and I can mount my windows partition. Is there a better way to
> get this NIC working?

install a recent kernel like 2.6.23 or 2.6.24 (just download the sources, 
unpack them in /usr/src, create the linux symlink). And use the in kernel 
r8169 drivers.

Don't use 'vendor' drivers if you don't have to!

>
> Actually my ultimate goal is to get my Marvell TOPDOG wireless NIC
> working, but it appears to me that I will need to get ndiswrapper and
> perhaps wine for this to happen, neither of which are on the LiveDVD.
> I'm hoping to get a network connection so I can get enough packages to
> update the system enough to get this working and solve other hardware
> issues resulting from me having a new laptop designed to work with
> Vista.

you might want to use the 2008-beta livecd for this - this way you don't have 
with a lot of very messy stuff (like expat). And wine is.. evil. Every 
release breaks something. If your stuff works at all.
-- 
gentoo-user@lists.gentoo.org mailing list



Re: [gentoo-user] Networking problems

2006-11-06 Thread Hans-Werner Hilse
Hi,

On Sat, 4 Nov 2006 07:24:51 -0500 (GMT-05:00) Jeff Cranmer
<[EMAIL PROTECTED]> wrote:

> For the /etc/resolv.conf file, I have:
> search belkin
> nameserver 192.168.2.1
> nameserver 207.69.188.185
> nameserver 207.69.188.186
> nameserver 207.69.188.187

Given that the router runs a local DNS (caching) server, that should be
alright.

> route -n returns
> Kernel IP routing table
> Destination   Gateway  Genmask   Flags
> MetricRef Use  Iface
> 192.168.2.0  0.0.0.0  255.255.255.0  U  0  0  0   eth0
> 127.0.0.00.0.0.0  255.0.0.0  U  0  0  0   lo
> 0.0.0.0  192.168.2.1  0.0.0.0   UG  0  0  0   eth0

looks good.

> Comparing this with the equivalent working connection via my Mandriva
> Linux boot-up,  /etc/resolv.conf is the same, but route -n returns
> [...]
> The main difference is that the metric column is all 0 on my
> non-working install, and I'm missing the 169.254.0.0 row from route -n

That doesn't matter. That 169.254.0.0 subnet is the Windows
autoconfiguration range (when there's no DHCP server, but IP address
gathering is set to "automatic") and the metric doesn't matter because
you don't have concurrent routes.

> I'm not using genkernel.  Is it possible that a kernel
> misconfiguration is responsible for the problems I'm having?

Unlikely, because in that case DHCP wouldn't work at all.

Maybe the Belkin is blocking your pings? Maybe the Belkin is
misconfigured and does not have Internet access? Maybe some firewall,
either on the Belkin or on your Gentoo machine (you can check by
issuing "iptables -vnL")?

You should also try to monitor traffic with tcpdump when issuing those
test pings. BTW, you cannot ping "http://www.google.de"; since that
isn't a domain name but a URL. But you probably *did* ping the domain
name, didn't you?

-hwh
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Networking problems

2006-11-04 Thread Jeff Cranmer
Perhaps removing all the lines from the net configuration script was the key 
after all.
It didn't work on the next boot-up cycle, but on the one following that, 
without performing any extra configuration steps, the network connection was 
operational :-/

I have a network.  Now I can proceed with installing kde :-)

The results of ifconfig and route -n are unchanged.

Jeff


-Original Message-
>From: Mick <[EMAIL PROTECTED]>
>Sent: Nov 4, 2006 8:29 AM
>To: gentoo-user@lists.gentoo.org
>Subject: Re: [gentoo-user] Networking problems
>
>On Saturday 04 November 2006 12:24, Jeff Cranmer wrote:
>
>> Comparing this with the equivalent working connection via my Mandriva Linux
>> boot-up,  /etc/resolv.conf is the same, but route -n returns Kernel IP
>> routing table
>> Destination   Gateway  Genmask   FlagsMetricRef
>> Use  Iface 192.168.2.0  0.0.0.0255.255.255.0 U 
>>10 00  eth0 169.254.0.0   0.0.0.0   
>>255.0.0.0U 10 00  eth0
>> 127.0.0.0  0.0.0.0255.0.0.0U 0 
>> 00  lo 0.0.0.0 192.168.2.1  0.0.0.0
>>   UG  10 00  eth0
>
>Have you tried only entering config_eth0=( "dhcp" ) in your /etc/conf.d/net 
>and leaving all the routing and dns setting to dhcpcd to sort out?  Have you 
>a complicating LAN arrangement that requires the nodns option?
>-- 
>Regards,
>Mick

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Networking problems

2006-11-04 Thread Mick
On Saturday 04 November 2006 12:24, Jeff Cranmer wrote:

> Comparing this with the equivalent working connection via my Mandriva Linux
> boot-up,  /etc/resolv.conf is the same, but route -n returns Kernel IP
> routing table
> Destination   Gateway  Genmask   FlagsMetricRef
> Use  Iface 192.168.2.0  0.0.0.0255.255.255.0 U 
>10 00  eth0 169.254.0.0   0.0.0.0   
>255.0.0.0U 10 00  eth0
> 127.0.0.0  0.0.0.0255.0.0.0U 0 
> 00  lo 0.0.0.0 192.168.2.1  0.0.0.0
>   UG  10 00  eth0

Have you tried only entering config_eth0=( "dhcp" ) in your /etc/conf.d/net 
and leaving all the routing and dns setting to dhcpcd to sort out?  Have you 
a complicating LAN arrangement that requires the nodns option?
-- 
Regards,
Mick


pgpjZMRYQ5bKt.pgp
Description: PGP signature


Re: [gentoo-user] Networking problems

2006-11-04 Thread Jeff Cranmer
After reading the comments at the top of the /etc/conf.d/net, a blank file will 
automatically use DHCP for any net.* scripts in /etc/init.d, so I commented out 
all the parameters that I'd added.  The file then matches the one in the livecd 
boot-up that I used to install the OS.

For the /etc/resolv.conf file, I have:
search belkin
nameserver 192.168.2.1
nameserver 207.69.188.185
nameserver 207.69.188.186
nameserver 207.69.188.187

route -n returns
Kernel IP routing table
Destination   Gateway  Genmask   FlagsMetricRef 
Use  Iface
192.168.2.0  0.0.0.0255.255.255.0 U 0  0
0  eth0
127.0.0.0  0.0.0.0255.0.0.0U 0  
00  lo
0.0.0.0 192.168.2.1  0.0.0.0   UG  0 0  
  0  eth0

Comparing this with the equivalent working connection via my Mandriva Linux 
boot-up,  /etc/resolv.conf is the same, but route -n returns
Kernel IP routing table
Destination   Gateway  Genmask   FlagsMetricRef 
Use  Iface
192.168.2.0  0.0.0.0255.255.255.0 U 10 0
0  eth0
169.254.0.0   0.0.0.0   255.0.0.0U 10 0 
   0  eth0
127.0.0.0  0.0.0.0255.0.0.0U 0  
00  lo
0.0.0.0 192.168.2.1  0.0.0.0   UG  10 0 
   0  eth0

The main difference is that the metric column is all 0 on my non-working 
install, and I'm missing the 169.254.0.0 row from route -n

I'm not using genkernel.  Is it possible that a kernel misconfiguration is 
responsible for the problems I'm having?

Thanks

Jeff


-Original Message-
>From: Novensiles divi Flamen <[EMAIL PROTECTED]>
>Sent: Nov 3, 2006 10:15 PM
>To: gentoo-user@lists.gentoo.org
>Subject: Re: [gentoo-user] Networking problems
>
>On Saturday 04 November 2006 09:57, Jeff Cranmer wrote:
>> I seem to have some network issues with my gentoo install
>>
>> I have /etc/init.0/net.eth0 configured to run at the default runlevel.
>> It appears to startup ok.  No firewall has been installed yet.
>> The network appears to startup eth0 correctly, obtaining a dhcp address
>> from my cable provider via the router.
>>
>Are you getting DNS and default route settings from the DHCP server? Your 
>option 'nodns' means you'd need to have it set manually. 
>
>cat /etc/resolv.conf should show the value of your DNS server.
>
>route -n should show your default gateway. Check that both values are sane.
>
>- Noven
>-- 
>>-- Novensiles divi Flamen --<
>> Miles Militis Fons <

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Networking problems

2006-11-03 Thread Novensiles divi Flamen
On Saturday 04 November 2006 09:57, Jeff Cranmer wrote:
> I seem to have some network issues with my gentoo install
>
> I have /etc/init.0/net.eth0 configured to run at the default runlevel.
> It appears to startup ok.  No firewall has been installed yet.
> The network appears to startup eth0 correctly, obtaining a dhcp address
> from my cable provider via the router.
>
Are you getting DNS and default route settings from the DHCP server? Your 
option 'nodns' means you'd need to have it set manually. 

cat /etc/resolv.conf should show the value of your DNS server.

route -n should show your default gateway. Check that both values are sane.

- Noven
-- 
>-- Novensiles divi Flamen --<
> Miles Militis Fons <


pgp6LD8nPAOZI.pgp
Description: PGP signature