Professional Linux Help and Support Thread

henderson

Active member
  • Nov 24, 2007
    3,150
    2
    38
    Senior Executive, Goldman Sachs
    I tried it, still no luck. I think main issue is NIC is not detected properly. Bcoz if the NIC is active there are 2 indicators on NIC those should active and LAN light on the router should lit despite the default gateways, IPs and stuff.
     

    dineitdark

    Member
    Jan 25, 2007
    642
    1
    0
    henderson said:
    I tried it, still no luck. I think main issue is NIC is not detected properly. Bcoz if the NIC is active there are 2 indicators on NIC those should active and LAN light on the router should lit despite the default gateways, IPs and stuff.
    yes i think you are correct. what is your NIC?
     

    dineitdark

    Member
    Jan 25, 2007
    642
    1
    0
    henderson said:
    RealTek RTL8139/810x Family Fast Ethernet NIC

    thats how it displays on device manager
    after some googling i came accros this page please take a look at it. some guy/girl managed to get it to work in suse(where it didn't work out of the box)

    http://www.linuxquestions.org/hcl/showproduct.php/product/2533

    Distribution: SuSE 10.1, Fedora6, Slackware 11, Ubuntu 6.06.1


    r1000 was only supported by Ubuntu from the distros I tried (mentioned above).

    (By the way, thought windows says RTL8139/R810x, it is most likely not an RTL8139, or it would use the RTL8139 specific driver, and linux detects that well.)

    I downloaded the latest source for the R1000 drivers from Realtek, which required some editing before getting to work, here is how:

    These are the steps I followed for r1000 v1.04

    I copied the r1000 files into /root/r1000
    such that I had /root/r1000/src/..... files
    and /root/r1000/Makefile

    I edited /root/src/Makefile_linux26x
    and changed
    include $(PWD)/src/Makefile_linux26x
    to
    include /root/r1000/src/Makefile_linux26x

    then I edited /root/r1000/src/r1000_n.c (thanks to dotato)
    and changed the 3 lines startting with MODULE_PARM to MODULE_PARM_DESC

    as root I wrote
    make clean modules
    make install
    depmod -a (no idea what it does but it was in the readme)

    then I ran r1000.
    Started up SuSE's YaST, went to 'view hardware'
    Closed it.
    Opened up Netword Devices (still in YaST) and there was my NIC ready for configuration!!!

    Joy oh joy!
    It finally works.

    Once you get the driver installed, it works well, Don't know why r1000 was not included with any of those Distros except Ubuntu

    seems like he had to download the drivers from RealTek's web site and the compile it as a kernel module. so i suggest you to go to realtek's site and get the drivers(source code...) from there. and follow the instruction in there Readme.

    if you get any problems while compiling please post em here.
     

    ICE

    Active member
  • Mar 26, 2007
    6,152
    1
    38
    41
    henderson said:
    there was some issues,

    first one is there was no such directory called /root/src/
    second one is there was no such command named 'make'

    I think these are not available in live cd

    install 'make' then

    apt-get install make
     

    nagaya

    Member
    Mar 18, 2007
    12,671
    194
    0
    guys just installed Mandriva 2008.0 and my tvout on Nvidia Geforce is bit wierd;
    i wanna change format to PAL but how to do it'?
     

    nagaya

    Member
    Mar 18, 2007
    12,671
    194
    0
    heshan123 said:
    huh? modem drivers in your driver CD? thats very rare. When did u buy ur modem machan? Whats the brand?
    i had Intel 537 modem and successed in many linux destros;just downloaded and compiled driver and configured wvdial to dial and ....

    what's ur modem's chipset?
     

    nagaya

    Member
    Mar 18, 2007
    12,671
    194
    0
    ICE said:
    :D some old 1 mate. conexant soft 56k HSF
    yeah cool it has good linux supoort HCF also;there was a driver called linmodem or something with good results;i've used this modem for dial-in server in mandrake 9 and had great success
     

    nagaya

    Member
    Mar 18, 2007
    12,671
    194
    0
    henderson said:
    I have a problem with Suse 10.3, i tried to boot this from the live CD, I use a router and its working properly. My NIC is Realtek RTL8139/810X onboard LAN, and the LEDs on that card does not lit when I boot from Suse, while it lits when I boot from XP. means my Ethernet card is the culprit. Can you give me some advice on this matter to setup my stupid Ethernet card.
    no machan RTL8139 is good 100Mbps card and RTL 8029 is 10Mbps i have used many of them and it's card that usually shipped with any old pc and yet so

    the prob is on config ;have u tried to config with "ifconfig" ?:nerd:
     

    henderson

    Active member
  • Nov 24, 2007
    3,150
    2
    38
    Senior Executive, Goldman Sachs
    nagaya said:
    no machan RTL8139 is good 100Mbps card and RTL 8029 is 10Mbps i have used many of them and it's card that usually shipped with any old pc and yet so

    the prob is on config ;have u tried to config with "ifconfig" ?:nerd:

    this is ifconfig output

    linux:/home/linux # ifconfig
    eth0 Link encap:Ethernet HWaddr 00:15:58:44:65:6F
    inet addr:169.254.63.97 Bcast:169.254.255.255 Mask:255.255.0.0
    inet6 addr: fe80::215:58ff:fe44:656f/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    Interrupt:17 Base address:0x2000

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:45 errors:0 dropped:0 overruns:0 frame:0
    TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:2860 (2.7 Kb) TX bytes:2860 (2.7 Kb)
     

    ICE

    Active member
  • Mar 26, 2007
    6,152
    1
    38
    41
    henderson said:
    this is ifconfig output

    linux:/home/linux # ifconfig
    eth0 Link encap:Ethernet HWaddr 00:15:58:44:65:6F
    inet addr:169.254.63.97 Bcast:169.254.255.255 Mask:255.255.0.0
    inet6 addr: fe80::215:58ff:fe44:656f/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    Interrupt:17 Base address:0x2000

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:45 errors:0 dropped:0 overruns:0 frame:0
    TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:2860 (2.7 Kb) TX bytes:2860 (2.7 Kb)

    hmm i dont see a default GW :S
     

    nagaya

    Member
    Mar 18, 2007
    12,671
    194
    0
    henderson said:
    still it should indicate ethernet card is active or not, adsl router and NIC indicators are not indicating ethernet card is not active. No point of setting default GW if your card is not active
    here's the prob

    inet addr:169.254.63.97 Bcast:169.254.255.255 Mask:255.255.0.0

    ur ip is not assigned and card assiged default one 169.254.63.97

    first run ifconfig eth0 down
    then use ifconfig to config it

    then u hav to add dns severs, the path will differ according to destro
     

    dineitdark

    Member
    Jan 25, 2007
    642
    1
    0
    @henderson
    hi, sorry i couldn't keep up with the thread. the command make might not be installed as you said on the live CD. and for you to install it would need your n/w to work in the first place :P so its a bit tricky situation that you have over there.

    you have some choices here,

    1. stay with suse and get the needed packages from the net and store them in your windows partition and boot from live cd and install them on the live env. and compile your drivers.

    2. choose some other distro that supports your NIC out of the box.

    notes:
    in order to build the NIC driver you will some packages
    "You will need the kernel source and compiling software - gcc, make etc.".

    that missing /root/src is the kernel source(kernel headers to be more specific) that drivers build script was trying to find.

    there are others who is having the same problem as you do.
    here is a pointer to a another thread about installing this driver from source on suse
    http://forums.suselinuxsupport.de/index.php?showtopic=36365
     

    dineitdark

    Member
    Jan 25, 2007
    642
    1
    0
    ICE said:
    install 'make' then

    apt-get install make
    machan ASFAIK apt-get is debian (and debian biased distro) specific. so its not there in suse. he will have to use rpm to install the stuff and not apt.