problems with new ethernet card and router

From: Craig Watson (watsoncm_at_btinternet.com)
Date: 03/24/04 

Date: Wed, 24 Mar 2004 18:57:12 +0000 (UTC)

Hi -

I have recently installed SuSE Linux 9.0 Pro on my PC as a dual boot with
WinXP Home Edition. No problems with the installation; SuSE identified all
my hardware first time. Unfortunately it resolutely refused to speak to the
standard 'frog' Speedtouch USB modem, despite admitting to seeing it
connected to my machine. Requests for help to appropriate newsgroups quickly
led me to decide to ditch the frog in favour of a new ADSL Firewall Router
(a Netgear DG834) and a Netgear FA311 PCI ethernet card.

Installation of the new kit under WinXP was done and dusted in less than ten
minutes, save for a little tweaking of my proxy server settings on the
firewall.

However, (you can guess what's coming), while SuSE is happy to recognise the
ethernet card as eth0 and I can ping it at IP address 192.168.0.2 quite
happily, I can't reach the router at 192.168.0.1. Ping returns a destination
unreachable message.

One other thing. WinXP always negotiates a 100Mbps connection with the
router via the ethernet card, as indicated by the port active lamp being a
nice, green colour (I have the ethernet card connected to port 4 on the
router). When I restart my machine and boot Linux via the Grub boot handler,
the lamp on port 4 turns to amber, which, my card documentation tells me, is
a 10Mbps connection. The colour change is always evident very early in the
boot process, usually before Grub starts to echo the boot process (I have
splash=verbose as the default setting, so I can see what's happening). I am
unsure of the significance of the change in connection speed.

I have tried various combinations of settings for eth0 via YaST for default
gateway, destination, gateway, netmask, etc but I have quickly exhausted the
possibilities I can think of as a Linux noob.

PC is a P4 2.4GHz on a Chaintech mobo with 1Gb DDR RAM.

Anyone got any ideas what it is I'm doing wrong?

many thanks
Craig

Relevant Pages

  • Re: ADSL Modem Configuration
    ... You will also need an ethernet card ... > the modem using a straight lan connection with dhcp. ... networked printers/scanners. ... I was experimenting with Mepis and Winxp. ...
    (comp.os.linux.setup)
  • Re: How do I solve this boot.ini problem with WinXP?
    ... I've redone it all and I've made a bit of progress but, alas, WinXP still ... I copied those two files from the CD into the root of the 2K partition by ... Win2K didn't object. ... full boot menu in the DOS-like screen. ...
    (microsoft.public.windowsxp.newusers)
  • Re: Home Edition Startup Files
    ... I Recently used a XP boot floppy to load the PC and was told that a dll file ... As you know, the WinXP CD-ROM is bootable, and it contains a utility called the Recovery Console. ... The first physical sector of each partition and of each logical drive holds the boot sector for that volume. ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: Second hard drive causing blue screen error
    ... able to boot whilst it is connected. ... What is the make & model of your "old" HDD, ... power plug connection? ... When the Western Digital began the BSoD I disconnected ...
    (microsoft.public.windowsxp.hardware)
  • Re: in lieu of swapping out hard drives
    ... which in turn is plugged into the Expresscard port on the dv8100cto. ... Recieve screen asking which device to boot from ... drives including the CDROM with the eSATA connected. ... connection to the ExpressCard is eSATA or PATA, ...
    (microsoft.public.windowsxp.general)