Stan Goodman pecked at the keyboard and wrote:

At 14:13:09 on Thursday Thursday 08 October 2009, Constantinos Galilei wrote:

...

On Thursday October 8 2009 6:19:45 am Stan Goodman wrote:

...

SUBDIRS=/home/stan/NIC/r8168-8.014.00/src modules make[2]: Entering directory `/usr/src/linux-2.6.27.7-9-obj/x86_64/default' make[2]: *** No rule to make target `modules'. Stop. make[2]: Leaving directory `/usr/src/linux-2.6.27.7-9-obj/x86_64/default' make[1]: *** [modules] Error 2 make[1]: Leaving directory `/home/stan/NIC/r8168-8.014.00/src' make: *** [modules] Error 2 # This is *kind of* a 'make' error. It can't find some makefile dealing with your kernel.

First of all, do `uname -r` and make sure the result is linux-2.6.27.7-9-obj. If it's not, you will need to specify the kernel

I did before I wrote, to be sure I knew what kernel version is here. The response is <2.6.27.29-0.1-default>. I do not see in the list that YaST has anything about a version like "-obj".

I have kernel-source and kernel-syms.

...

(hopefully when you run ./configure, otherwise you'll have to edit the makefile itself).

Perhaps that will become clearer to me later. Right now, I do not find a way to edit makefile, nor a way to avoid doing so.

...

And if you're not sure you have the kernel headers installed, check.

I didn't see "kernel-headers" in YaST. A more fundamental search brings them up as "linux-kernel heades"

Te Error 2 is now as follows, containing several errors, including an unfound command:

# make clean modules make -C src/ clean make[1]: Entering directory `/home/stan/NIC/r8168-8.014.00/src' rm -rf *.o *.ko *~ core* .dep* .*.d .*.cmd *.mod.c *.a *.s .*.flags .tmp_versions Module.symvers Modules.symvers Module.markers *.order make[1]: Leaving directory `/home/stan/NIC/r8168-8.014.00/src' make -C src/ modules make[1]: Entering directory `/home/stan/NIC/r8168-8.014.00/src' make -C /lib/modules/2.6.27.7-9-default/build SUBDIRS=/home/stan/NIC/r8168-8.014.00/src modules make[2]: Entering directory `/usr/src/linux-2.6.27.7-9-obj/x86_64/default' make -C ../../../linux-2.6.27.7-9 O=/usr/src/linux-2.6.27.7-9-obj/x86_64/default/. modules make[4]: gcc: Command not found CC [M] /home/stan/NIC/r8168-8.014.00/src/r8168_n.o

/bin/sh: gcc: command not found

Is a powerful hint at the problem. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Stan Goodman wrote:

That's true. It doesn't help to choose among the many gcc compilers on the DVD. Can I assume that gcc-c++ is the way to go? Or is gcc43-c++ the one with the brass ring? Or gcc43? Or what?

I suspect "zypper in gcc" will get you what you need. /Per -- Per Jessen, Zürich (16.4°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Stan Goodman pecked at the keyboard and wrote:

At 17:53:55 on Thursday Thursday 08 October 2009, Per Jessen wrote:

...

Stan Goodman wrote:

...

That's true. It doesn't help to choose among the many gcc compilers on the DVD. Can I assume that gcc-c++ is the way to go? Or is gcc43-c++ the one with the brass ring? Or gcc43? Or what? I suspect "zypper in gcc" will get you what you need.

That caused the system to try to access the non-oss repository, because it complained that it couldn't resolve download.opensuse.org. The problem is that I am trying to get the Ethernet card to work, and there is no other way to reach the outside world. It stands to reason that the necessary compiler has to be on the DVD. But there are many likely looking gcc compilers on the DVD; so far I know that gcc43 and gcc43-c++ don't help. Which one does it want?

Disable all repo's except for the *dvd* or add it if it isn't in the list, then zypper ref and zypper in gcc. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

At 20:15:49 on Thursday Thursday 08 October 2009, Stan Goodman wrote:

At 18:34:56 on Thursday Thursday 08 October 2009, "Ken Schneider -

openSUSE" wrote:

...

Stan Goodman pecked at the keyboard and wrote:

...

At 17:53:55 on Thursday Thursday 08 October 2009, Per Jessen

wrote:

...

Stan Goodman wrote:

...

That's true. It doesn't help to choose among the many gcc compilers on the DVD. Can I assume that gcc-c++ is the way to go? Or is gcc43-c++ the one with the brass ring? Or gcc43? Or what?

I suspect "zypper in gcc" will get you what you need.

That caused the system to try to access the non-oss repository, because it complained that it couldn't resolve download.opensuse.org. The problem is that I am trying to get the Ethernet card to work, and there is no other way to reach the outside world. It stands to reason that the necessary compiler has to be on the DVD. But there are many likely looking gcc compilers on the DVD; so far I know that gcc43 and gcc43-c++ don't help. Which one does it want?

Disable all repo's except for the *dvd* or add it if it isn't in the list, then zypper ref and zypper in gcc.

That made the modules without errors. There are two warning messages that I assume are expected, indicating that some facility is not supported by the driver:

r8168_n.c.:526: warning: 'rtl8168_ocp_gphy_read' defined but not used r8168_n.c.5292: warning: 'rtl8168_reinit_task' defined but not used

The rest of the compilation finished, apparently in good order. seems to have found the installed driver.

But , according to the instructions, was expected to include in its response a line about eth0, but there is no such thing in its two paragraph, which seem otherwise to be in order.

Also worrying is that I now notice in Network Settings/Overview that in the lower window the name of the Ethernet card is followed by "(no hwinfo)"

And the upshot is that the network is unreachable. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

At 20:59:11 on Thursday Thursday 08 October 2009, kanenas@hawaii.rr.com wrote:

On Thursday 08 October 2009 08:35:03 am Stan Goodman wrote:

...

At 20:15:49 on Thursday Thursday 08 October 2009, Stan Goodman

wrote:

...

At 18:34:56 on Thursday Thursday 08 October 2009, "Ken Schneider -

openSUSE" wrote:

...

Stan Goodman pecked at the keyboard and wrote:

...

At 17:53:55 on Thursday Thursday 08 October 2009, Per Jessen

wrote:

...

Stan Goodman wrote: > That's true. It doesn't help to choose among the many gcc > compilers on the DVD. Can I assume that gcc-c++ is the way to > go? Or is gcc43-c++ the one with the brass ring? Or gcc43? Or > what?

I suspect "zypper in gcc" will get you what you need.

That caused the system to try to access the non-oss repository, because it complained that it couldn't resolve download.opensuse.org. The problem is that I am trying to get the Ethernet card to work, and there is no other way to reach the outside world. It stands to reason that the necessary compiler has to be on the DVD. But there are many likely looking gcc compilers on the DVD; so far I know that gcc43 and gcc43-c++ don't help. Which one does it want?

Disable all repo's except for the *dvd* or add it if it isn't in the list, then zypper ref and zypper in gcc.

That made the modules without errors. There are two warning messages that I assume are expected, indicating that some facility is not supported by the driver:

r8168_n.c.:526: warning: 'rtl8168_ocp_gphy_read' defined but not used r8168_n.c.5292: warning: 'rtl8168_reinit_task' defined but not used

The rest of the compilation finished, apparently in good order.

| grep r8186> seems to have found the installed driver.

But , according to the instructions, was expected to include in its response a line about eth0, but there is no such thing in its two paragraph, which seem otherwise to be in order.

Also worrying is that I now notice in Network Settings/Overview that in the lower window the name of the Ethernet card is followed by "(no hwinfo)"

And the upshot is that the network is unreachable.

-- Stan Goodman Qiryat Tiv'on Israel

There should be no need to manually install drivers for an rt8168. you might want to consider removing what you have installed and see where that takes you. fyi, my vostro shows r8169 as the driver found / installed by yast for the rt nic. if the card is seen by yast and editing it completes (and the module is shown / typed in in the hardware tab), then you might want to verify your cable connection, just as a sanity check.

I'll have to google to find out how to remove a driver, and go through the whole process again. oS did identify the controller correctly, but didn't find a driver for it. What repository is it in? I d/l the driver from RealTek The only hardware I see in Network Settings is on the Overview tab. If there is a "hardware tab", I don't see it. Nor do I see a place where the driver is shown. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thursday 08 October 2009 19:59:11 kanenas@hawaii.rr.com wrote:

There should be no need to manually install drivers for an rt8168.

Well, not if you don't have an rt8168 based NIC you won't.

you might want to consider removing what you have installed and see where that takes you.

Or not. It all depends on whether the NIC has been configured and the correct module selected for it.

fyi, my vostro shows r8169 as the driver found / installed by yast for the rt nic.

That's all well and good, but do you have an rt8169 or 8168 based NIC? I have an rt8168 based NIC on one of my systems. It's built onto a M/B that's replaced one that failed. The one it replaced didn't have an onboard NIC, so when it failed to work with 11.1, I just put the old rt8139 based NIC back in and continued as before. The funny part about this is that that system didn't have a DVD drive and so I needed to use PXE booting to reconfigure it for the new hardware. To do this I needed to have both NICs connected to a switch. The onboard NIC started the network boot process and would load the kernel and initrd. After that, once the installation had sent the DHCP requests to the NICs, the onboard one failed and the older one took over. The installation completed just fine like this and, after everything had finished, I disabled the onboard NIC until I saw this thread. Now I've compiled and installed the rt8168 module, and now have to remember to rebuild and reinstall it with every kernel update. As for whether it works, that I can't say as yet. That NIC doesn't have a cable plugged into it, and the system is also headless so I'd need to move it to be able to plug it into a keyboard and monitor just in case doing a cable swap broke its networking.

if the card is seen by yast and editing it completes (and the module is shown / typed in in the hardware tab), then you might want to verify your cable connection, just as a sanity check.

That's a good thing to check, but YaST doesn't always pick the correct module for hardware. It didn't for my hardware, and it's not the first time I've had to compile a module to get a working onboard network card. Admittedly, the last time was many years ago with an nForce2 motherboard. As for this time, here's the output of lspci for my cards: donnas:~ # lspci|grep -i ethernet 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03) 03:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) and here's the hwinfo for the 8168: 30: PCI 200.0: 0200 Ethernet controller [Created at pci.318] UDI: /org/freedesktop/Hal/devices/pci_10ec_8168 Unique ID: mY_N.SNc65Gva3GC Parent ID: M71A.yjEgnYhrx38 SysFS ID: /devices/pci0000:00/0000:00:07.0/0000:02:00.0 SysFS BusID: 0000:02:00.0 Hardware Class: network Model: "Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller" Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd." Device: pci 0x8168 "RTL8111/8168B PCI Express Gigabit Ethernet controller" SubVendor: pci 0x1565 "Biostar Microtech Int'l Corp" SubDevice: pci 0x2309 Revision: 0x03 Driver: "r8168" Driver Modules: "r8168" Device File: eth2 I/O Ports: 0xd800-0xd8ff (rw) Memory Range: 0xf8fff000-0xf8ffffff (rw,prefetchable) Memory Range: 0xf8ff8000-0xf8ffbfff (rw,prefetchable) Memory Range: 0xfeae0000-0xfeafffff (ro,prefetchable,disabled) IRQ: 4348 (no events) HW Address: 00:30:67:22:0c:d2 Link detected: no Module Alias: "pci:v000010ECd00008168sv00001565sd00002309bc02sc00i00" Driver Info #0: Driver Status: r8169 is not active Driver Activation Cmd: "modprobe r8169" Driver Info #1: Driver Status: r8168 is active Driver Activation Cmd: "modprobe r8168" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #10 (PCI bridge) Regards, David Bolt -- Team Acorn: www.distributed.net OGR-NG @ ~100Mnodes RC5-72 @ ~1Mkeys/s openSUSE 10.3 32b | openSUSE 11.0 32b | | openSUSE 10.3 64b | openSUSE 11.0 64b | openSUSE 11.1 64b | openSUSE 11.2m8 RISC OS 3.6 | RISC OS 3.11 | openSUSE 11.1 PPC | TOS 4.02 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

At 20:35:06 on Thursday Thursday 08 October 2009, "Ken Schneider - openSUSE" wrote:

Stan Goodman pecked at the keyboard and wrote:

...

At 18:34:56 on Thursday Thursday 08 October 2009, "Ken Schneider - openSUSE" wrote:

That made the modules without errors. There are two warning messages that I assume are expected, indicating that some facility is not supported by the driver:

r8168_n.c.:526: warning: 'rtl8168_ocp_gphy_read' defined but not used r8168_n.c.5292: warning: 'rtl8168_reinit_task' defined but not used

The rest of the compilation finished, apparently in good order. seems to have found the installed driver.

But , according to the instructions, was expected to include in its response a line about eth0, but there is no such thing in its two paragraph, which seem otherwise to be in order.

Also worrying is that I now notice in Network Settings/Overview that in the lower window the name of the Ethernet card is followed by "(no hwinfo)"

I've configured the Network Settings in YaST.

In the network card settings under the hardware tab, which driver does it show? If not the rtl8168 then change it to be so. After saving your changes you might have to run (as root) rcnetwork restart. Past that if you still have problems it will be beyond my help. Good luck.

I am certainly grateful for your help thus far. Where exactly are you asking me to look for the network card settings? Running rcnetwork restart tells me that "No configuration found for pan0". That's a new one. What I get from Google is that this is something to do with Bluetooth. I do not have Blueteeth, so there must be some confution somewhere.

-- Ken Schneider SuSe since Version 5.2, June 1998

-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

At 22:01:31 on Thursday Thursday 08 October 2009, "Ken Schneider - openSUSE" wrote:

Stan Goodman pecked at the keyboard and wrote:

...

At 20:35:06 on Thursday Thursday 08 October 2009, "Ken Schneider -

openSUSE" wrote:

...

Stan Goodman pecked at the keyboard and wrote: In the network card settings under the hardware tab, which driver does it show? If not the rtl8168 then change it to be so. After saving your changes you might have to run (as root) rcnetwork restart. Past that if you still have problems it will be beyond my help. Good luck.

I am certainly grateful for your help thus far.

Where exactly are you asking me to look for the network card settings?

In YaST-->Network Device-->Network Settings

...

Running rcnetwork restart tells me that "No configuration found for pan0". That's a new one. What I get from Google is that this is something to do with Bluetooth. I do not have Bluetooth, so there must be some confusion somewhere.

I recall that at an early stage there was a response to an instruction in a terminal window with two paragraphs, one headed "lo" and the other "pan0". The latter was unfamiliar to me, and anyway I was not asked about it, so I shrugged it off.

-- Ken Schneider SuSe since Version 5.2, June 1998

-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Friday 09 October 2009 03:01:01 am Stan Goodman wrote:

The Module Name field must be the one you suggested I fill with rtl8169; it was empty, and I filled it. When I closed the window (Next > OK) and opened again, both fields were again empty.

are you sure that driver is installed on your system? -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Friday 09 October 2009 03:43:19 am Stan Goodman wrote:

I am sure of nothing at this point, including my name.

what surprises me is that your system didn't recognize the rt8169 network card without installing a separate driver. i think i remember that the card on my other machine uses the same one, and detected it automatically. don't have access to that machine now and can't confirm this for sure, though. somewhere in the process of uninstalling the old and installing the new driver something must have gone wrong; but what exactly i can't figure out from this thread; certainly hope that somebody else will, but the whole thing appears pretty confused. if you boot from a live CD, does your network work? -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thursday 08 October 2009 23:42:42 phanisvara das wrote:

On Friday 09 October 2009 03:43:19 am Stan Goodman wrote:

...

I am sure of nothing at this point, including my name.

what surprises me is that your system didn't recognize the rt8169

He doesn't have an rt8169 network card. The first post in this thread shows he has an rt8168 card, and the rt8169 driver doesn't work with it. <quote> The NIC in this Vostro 1510 notebook is shown by Network Devices as: . </quote> Regards, David Bolt -- Team Acorn: www.distributed.net OGR-NG @ ~100Mnodes RC5-72 @ ~1Mkeys/s openSUSE 10.3 32b | openSUSE 11.0 32b | | openSUSE 10.3 64b | openSUSE 11.0 64b | openSUSE 11.1 64b | openSUSE 11.2m8 RISC OS 3.6 | RISC OS 3.11 | openSUSE 11.1 PPC | TOS 4.02 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On October 12, 2009 9:15:01 am Roman B. wrote:

On October 10, 2009 7:23:27 pm David Bolt wrote:

...

On Thursday 08 October 2009 23:42:42 phanisvara das wrote:

...

On Friday 09 October 2009 03:43:19 am Stan Goodman wrote:

...

I am sure of nothing at this point, including my name.

what surprises me is that your system didn't recognize the rt8169

He doesn't have an rt8169 network card. The first post in this thread shows he has an rt8168 card, and the rt8169 driver doesn't work with it.

<quote> The NIC in this Vostro 1510 notebook is shown by Network Devices as: .

</quote>

Regards, David Bolt

Check out the following link:

http://www.opendrivers.com/driver/252272/realtek-rtl8169-driver-6.006.00- linux-kernel-2.6.x-2.4.x-free-download.html

Roman

Hi all, I found the RTL8168 UNIX/Linux driver vers.8.014.00 on the Realtek.com.tw website. Read the readme file for install instructions. Good Luck! Roman -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Monday 12 October 2009 15:11:59 David Bolt wrote:

On Monday 12 October 2009 14:38:52 Roman B. wrote:

...

Hi all,

I found the RTL8168 UNIX/Linux driver vers.8.014.00 on the Realtek.com.tw website. Read the readme file for install instructions.

That's the one I have downloaded, built, installed, configured but not yet tested. With luck I'll be able to test it out under 11.1 this evening to see if it actually works. At the same time, I'll try out 11.2 milestone 8 on the same system to see if it loads up the right driver. I'm guessing that it'll load up the rt8169 module and that it probably won't work, although it will be a nice surprise if it does.

Well, I was pleasantly surprised. Milestone 8 did indeed load up the r8169 module, and it did work. Even more curious was that after rebooting back into 11.1 I was able to get it working with the r8169 module. It did require using YaST to remove the network card and reconfigure it completely, but it did start working properly afterwards. It is slightly puzzling as to why it didn't work before and, as for it failing when used to do a network installation, my guess about that is that either the DHCP request was possibly timing out, or the driver took too long to configure the network card . At some point I'll have to look and see if the DHCP server received the request and sent a response, Regards, David Bolt -- Team Acorn: www.distributed.net OGR-NG @ ~100Mnodes RC5-72 @ ~1Mkeys/s openSUSE 10.3 32b | openSUSE 11.0 32b | | openSUSE 10.3 64b | openSUSE 11.0 64b | openSUSE 11.1 64b | openSUSE 11.2m8 RISC OS 3.6 | RISC OS 3.11 | openSUSE 11.1 PPC | TOS 4.02 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Friday 09 October 2009 10:40:34 am Andreas Jaeger wrote:

Btw. why do you need this at all? Doesn't the rt8169 driver support this card? I just looked at the 2.6.31 kernel and there it does support it as far as I can see,

i suspect he didn't configure the network card, which was probably detected ok by yast, and therefore the network wasn't working. he concluded that he needed another driver... is that perhaps how it happened, stan? -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Andreas Jaeger wrote:

On Thursday 08 October 2009 13:19:45 Stan Goodman wrote:

...

The NIC in this Vostro 1510 notebook is shown by Network Devices as: .

The kernel is v2.6.27-9-default.

Having found the PCI ID of the card (10ec:8168), and acquired the appropriate driver file from the RealTek site, I attempted to install it, following precisely the instructions given in its readme file, which says that the driver is intended for v2.6 kernel..

Btw. why do you need this at all? Doesn't the rt8169 driver support this card? I just looked at the 2.6.31 kernel and there it does support it as far as I can see,

Yes and no. We have the same chipsets here in PCI-Express cards. They *do* run with the standard kernel driver r8169. However, we had some weird lockups under heavy network load. So we're also using the realtek supplied drivers (r8168-8.014.00) (They'll probably need proper module parameters on load to set the card to the right mode) Cheers, Pit -- Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit Institute for Solar Physics Tel.: +34 922 405 590 (Spain) P.Suetterlin@royac.iac.es +46 8 5537 8534 (Sweden) Peter.Suetterlin@astro.su.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org