Find the answer to your Linux question:
Results 1 to 6 of 6
Hi all...yup, I'm a complete and total noob to this wacky thang called Linux. Anyhow, I just partitioned the hard drive on my Dell Inspiron 8000 (I know, it's rockin'!!), ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Apr 2006
    Posts
    3

    Total Noob to Linux, Networking Issues


    Hi all...yup, I'm a complete and total noob to this wacky thang called Linux.
    Anyhow, I just partitioned the hard drive on my Dell Inspiron 8000 (I know, it's rockin'!!), running WindowsMe, and installed Suse 9.1
    I've got a wired ethernet card (MS MN120, to be exact) which works just peachy happy under Windows to connect to my LAN via a sweet hub.
    Now, upon installation, Susa recognized the network card just fine. I configured it with a static IP addy (192.168.10.2 I believe), and everything seemed to work just fine. However, when I go into a terminal to try to ping the damn card, I get 'network is unreachable'. No idea what's causing this, as I've got an older 'puter I wiped windows off completey, installed Suse and did the same thing to be greeting with total success..computer pinging itself just fine...and able to connect to another 'puter I have that dual boots windows/suse.
    The darn laptop however is giving me grief, and I've got no idea why.
    Network card was detected fine. Static IP addy. Same thing I did on my other two comps, and it's not working.
    Ah, the laptop also has a modem that when I try to configure it, it says it needs the package 'Itmodem'. Where would I get such a thing?

  2. #2
    Linux Guru AlexK's Avatar
    Join Date
    Feb 2005
    Location
    Earth
    Posts
    3,379
    as root, can you post the results of these commands:
    Code:
    ifconfig
    route
    as for the ltmodem package, I guess, you could download it from SUSE's ftp site, or via a yast repository once the internet is up and running on the laptop.
    Life is complex, it has a real part and an imaginary part.

  3. #3
    Just Joined!
    Join Date
    Apr 2006
    Posts
    3
    Okay, so it detects my wired Microsoft MN120 Network Adapter just fine.
    I go in and set it up to a static IP addy: 192.168.10.2
    I give it host name: humphrey
    site: home

    I try to ping, with no results.
    I can however ping 127.0.0.1 just fine.

    Anyhow, here are the results of the said commands, run as root:
    ifconfig
    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask: 255.0.0.0
    inet6 addr: ::1/28 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:74 errors:0 dropped:0 overruns:0 frame:0
    TX packets:74 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:4710 (4.5kb) TX bytes:4710 (4.5kb)


    route
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    (The actual table appears to be totally empty, there's nothing after the above line)

  4. #4
    Linux Guru AlexK's Avatar
    Join Date
    Feb 2005
    Location
    Earth
    Posts
    3,379
    Ok, after a bit of searching, I found that your card uses the "Ethernet Pro 100" chipset. So, what you'll have to do is load the driver for the card with this command (do it as root):

    Code:
    modprobe eepro100
    Now, look at the output from ifconfig and an entry for eth0 should show up. If it doesn't post back the result from this command:
    Code:
    dmesg | tail
    Life is complex, it has a real part and an imaginary part.

  5. #5
    Just Joined!
    Join Date
    Apr 2006
    Posts
    3
    modprobe eepro100 command executed as root didn't give any sort of feedback, seemed to work just fine. However, no enry for eth0 in the ifconfig afterwards.

    So here is the result of dmesg | tail
    hdb: ATAPI 24X CD-ROM drive, 128kB Cache
    Uniform CD-ROM driver Revision: 3.20
    SCSI subsystem initialized
    st: Version 20040318, fixed bufsize 32768, s/g segs 256
    BIOS EDD facility v0.13 2004-Mar-09, 1 devices found
    drivers/usb/input/hid-input.c: event field not found
    drivers/usb/input/hid-input.c: event field not found
    spurious 8259A interrupt: IRQ7.
    eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html
    eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others

  6. #6
    Linux Guru AlexK's Avatar
    Join Date
    Feb 2005
    Location
    Earth
    Posts
    3,379
    hmm,
    can you post back what these commands return:
    Code:
    dmesg | grep eth
    dmesg | grep eepro
    lspci | grep net
    run the last command as root, if it returns nothing, post back what lspci returns.

    Do these commands after modprobing the driver. A successful modprobe should return nothing onto your screen. (i.e. it should just goto the next line of command prompt).
    Life is complex, it has a real part and an imaginary part.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •