RTL8168/8111 on Puppy 2.13 Not recognised

Post Reply
Message
Author
reis
Posts: 6
Joined: Tue 13 Feb 2007, 11:03

RTL8168/8111 on Puppy 2.13 Not recognised

#1 Post by reis »

I have a shiny new E6400 on a Gigabyte GA-945P-S3 MB with 1 Gig RAM, 250 Gig SATA HD, and an X300 Video card.

Puppy 2.13 works great except that it won't recognize the on-board NIC, which is a Realtek RTL8168/8111.

The NIC works fine in Windoze XP (using the driver on the MB CD). It also worked in Xubuntu 6.10 from a recent APC cover disk. I downloaded the driver (not using Puppy), r1000 v1.05 and tried to build it in puppy 2.13 but I get compile errors, due to conflicting declarations.

Any suggestions? Looking at the code, there seems to be a duplicate declarations of some routines, some have a FASTCALL attribute, some have a fastcall attribute, and some have neither.

Any chance of this driver appearing in zdrv_2xx any time soon?
Alternatively, I read somewhere that the 8168 is supported in the 2.6.19 kernel. What is the frequency of kernel updates in puppy os?

Please be gentle with me, I'm new around here. Its the first time I've tried doing any kernel type stuff in Linux...

For what its worth, I found Xubuntu to be very unhelpful when it came to doing things like mounting my Windoze partitions - Puppy's MUT was miles ahead.

TIA.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#2 Post by tempestuous »

Realtek has a proprietary Linux driver for the RTL8101/8168/8169 chipsets.
The latest version 1.05 failed to compile, but I was able to compile the earlier v1.04, which I now attach.
After installing the dotpup, load the driver like this -

modprobe r1000

Then you should be able to use the network wizard.
Attachments
Realtek-r1000-1.04-k2.6.18.1.pup
for Puppy 2.12 onwards
(16.66 KiB) Downloaded 2498 times

reis
Posts: 6
Joined: Tue 13 Feb 2007, 11:03

Yes it works now

#3 Post by reis »

The v1.04 driver above works fine, as is proven by the fact that I'm posting this reply from Puppy 2.13 with the RTL8168/8111 on board NIC. :)
Thanks!

zaw
Posts: 4
Joined: Sat 26 May 2007, 00:58

Help what do I do now?

#4 Post by zaw »

hi

I have the same problem with the SAME NIC on my ASUS P5B mobo.

can you tell me what exactly is the procedure you guys used to get the NIC working.

I got to the point where I used the consol window to run modprobe r1000
The command did not generate any errors so I presume it worked.

but now how do I install it using the network wizzard.

I cannot see the NIC listed.
Do I have to restart puppy?

regards
pzaw

reis
Posts: 6
Joined: Tue 13 Feb 2007, 11:03

#5 Post by reis »

Use the network wizard. Even though r1000 does not appear in the list of drivers, you select "specify SPECIFY A CUSTOM DRIVER" and then enter the module name.

I hope this helps

klivekaiser
Posts: 1
Joined: Sun 09 Dec 2012, 04:06

help

#6 Post by klivekaiser »

I double click on the .pup and it goes all the way through to where it asks me if I want to remove the .pup and I say no. Then I type modprobe r1000 into the sakura terminal and it says that Module r1000 not found. I also come up with nothing when I type lsmod | grep r1000. The default r8169 isn't working for me and I even did rmmod to get rid of it but I can't get the above .pup to give me the r1000 module to install. Please help. Thank you

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#7 Post by tempestuous »

klivekaiser wrote:... into the sakura terminal ...
klivekaiser, have a look at the date that I posted this r1000 module. And have a look at the kernel version it was compiled for.

You would be best to post your question for help in the Sakura forum thread ...
... and give them as much information about your hardware as possible.
Your dmesg results would be useful.
The PCI ID would be good, too.

Post Reply