LinuxMCE Forums

General => Installation issues => Topic started by: Steakboy on September 12, 2011, 08:57:45 pm

Title: R8168.ko issues / Diskless MD issues
Post by: Steakboy on September 12, 2011, 08:57:45 pm
Hi All,

I am trying to install a diskless MD, which has an on board NIC that needs the R8168 driver.

There are loads of forum posts I've seen and followed to get this running, but after a few minutes, I get the error 'line 1: can't open /tmp/net-eth0.conf' and the kernel panic attempting to kill message. '

The mother board is an A74ML-K with a gigabit Realtek NIC.

A lot of the posts on the forum refer to a folder - '/usr/pluto/diskless/', but there is no folder called diskless in /usr/pluto.

I added a new NIC to the mb, but this didn't allow me to boot over the LAN.

I'm close to tears...

Russell
Title: Re: R8168.ko issues / Diskless MD issues
Post by: Steakboy on September 12, 2011, 09:13:46 pm
I forgot to include - the onboard Realtek NIC on the mb for the hybrid is also not live. NetworkManager seems to be disabled, however the 2nd NIC works no problem.
Title: Re: R8168.ko issues / Diskless MD issues
Post by: kyfalcon on September 12, 2011, 09:45:11 pm
Is your onboard nic possibly turned off in bios? Also you may have to swap eth0 and eth1. This can be a problem. There should be a post concerning this in the forum.
Title: Re: R8168.ko issues / Diskless MD issues
Post by: seth on September 12, 2011, 09:57:47 pm
 :)
Hi. I have 2 MD's with the dreaded 8168 NIC driver issue.

You will find the relevant data to get your new driver complied here:

http://wiki.linuxmce.org/index.php/Realtek_8168 (http://wiki.linuxmce.org/index.php/Realtek_8168)

Please do not use the driver I have listed for the 7.10 version. Build a new one using the instructions at the top of the page.

Best Regards,

Seth


Perhaps if I have time this evening, I will post up my 8.10 version of the 8168 driver. Save you some compile time, not that it takes long.

Title: Re: R8168.ko issues / Diskless MD issues
Post by: purps on September 12, 2011, 10:02:33 pm
seth's advice here is also very useful http://forum.linuxmce.org/index.php?topic=6806.0

Cheers,
Matt.
Title: Re: R8168.ko issues / Diskless MD issues
Post by: Steakboy on September 13, 2011, 07:40:32 pm
OK, I ended up messing about with too much, so I wiped and started again today.

The problem I have now, with trying to get a network boot, is in the webadmin page, I have the external NIC as eth0 and the internal as eth0:1.

When I try a /etc/init.d/networking restart, the eth0:1 device doesnt get recognised.

Also, in the web admin networking page, eth0 and eth0:1 both have the same mac address.

I am guessing there's an mce file I need to amend somewhere?

Currently, I recieve a DHGCP address on the diskless MD, but then follows a few PXE errors (E11 ARP timeout, E38 TFTP can't open a connection).
Title: Re: R8168.ko issues / Diskless MD issues
Post by: Steakboy on September 13, 2011, 08:23:19 pm
SO I have made a couple of changes, and now I tftp boot again, before getting the same error as before -

"IP-Config: no response after 60 secs - giving up
/init: .:line 1: can't open /tmp/net-eth0.conf
[ 63.267760] kernel panic - not syncing: Attemped to kill init!"
Title: Re: R8168.ko issues / Diskless MD issues
Post by: kyfalcon on September 13, 2011, 08:45:12 pm
try swapping the lines going into your nic cards. Worth a try
Title: Re: R8168.ko issues / Diskless MD issues
Post by: Steakboy on September 13, 2011, 08:57:36 pm
I've switched the patch leads into the NICs, and I get no DHCP packets back, so I don't get anywhere with a PXE boot.

The 2nd (external) NIC is playing up, and from another thread on the net, I've seen a reference to a /etc/dhcp3/dhcpd.conf file, which references fugue.com, so I don't knwo if the 2nd NIC needs to be working fully?

I'm from the networking side of life, so linux isn't a strong (or even weak) point. Big learning curve since starting this!

Edit: I have perhaps jumped the gun with this, and it's not an R8169 issue? I'm not sure at all...
Title: Re: R8168.ko issues / Diskless MD issues
Post by: Steakboy on September 13, 2011, 09:23:29 pm
So, it does seem that I need to r8169/8111 driver for this card, however I can see in the verbose during the tftpboot that there's mention of the rtl8139 driver.

The rtl8139 is for 10/100 only, and this is definately a gigabit NIC.

How would I go about forcing the 8169/8111 driver onto the MD during boot?
Title: Re: R8168.ko issues / Diskless MD issues
Post by: ardirtbiker on September 14, 2011, 12:25:56 am
You can grab the latest Realtek driver for that NIC from the RealTek website.   You'll have to follow the instructions in http://wiki.linuxmce.org/index.php/Unrecognized_NIC (http://wiki.linuxmce.org/index.php/Unrecognized_NIC)   and this http://wiki.linuxmce.org/index.php/Realtek_8168 (http://wiki.linuxmce.org/index.php/Realtek_8168)..
This all gets done from your CORE/Hybrid machine... you'll have to create the initial MD via the admin web page > Media Directors..  once the directory under /usr/pluto/diskless/xx   (xx is the MD number) is created, you'll have to follow the instructions on the Unrecognized NIC link  and/or  the Realtek link

Dennis
Title: Re: R8168.ko issues / Diskless MD issues
Post by: Steakboy on September 14, 2011, 05:39:17 pm
I've created the MD as a diskless MD in the web admin page, but when I look in /usr/pluto/ there is no folder called diskless?

I've rebooted and the MD is definitely there, and set up as diskless. It has the device number of #34, but still does not show in dolphin.  ???
Title: Re: R8168.ko issues / Diskless MD issues
Post by: purps on September 14, 2011, 11:25:19 pm
Don't do anything in web admin, that's not necessary.

Did you do something simliar to this as per the link I posted earlier...

Code: [Select]
cp r8168.ko /lib/modules/2.6.22-14-generic/kernel/drivers/net/
mv /lib/modules/2.6.22-14-generic/kernel/drivers/net/r8169.ko /lib/modules/2.6.22-14-generic/kernel/drivers/net/r8169.bak
depmod -a
/usr/pluto/bin/Diskless_BuildDefaultImage.sh

...before trying to reboot the MD again?
Title: Re: R8168.ko issues / Diskless MD issues
Post by: Steakboy on September 21, 2011, 06:07:58 pm
Hi, sorry for the delay - I had a short break away from London.

I did run what you suggested. Everything ran OK, but again I have a line telling me 'etho: link down' on the MD after it has loaded some things from the core.
Title: Re: R8168.ko issues / Diskless MD issues
Post by: Steakboy on September 21, 2011, 08:02:05 pm
I'm wondering if it would be easier to have this running with a HDD and kubuntu installed... Would I be right?
Title: Re: R8168.ko issues / Diskless MD issues
Post by: purps on September 21, 2011, 08:32:30 pm
Hi, sorry for the delay - I had a short break away from London.

I did run what you suggested. Everything ran OK, but again I have a line telling me 'etho: link down' on the MD after it has loaded some things from the core.

So you've got a r8168.ko in /lib/modules/2.6.22-14-generic/kernel/drivers/net/ ?

Also don't forget to add r8168 to /etc/initramfs-tools-interactor/modules.

And do a "modprobe r8168" after the depmod -a, sorry, should have said that. Then run /usr/pluto/bin/Diskless_BuildDefaultImage.sh again.

I'm wondering if it would be easier to have this running with a HDD and kubuntu installed... Would I be right?

That won't be possible, netboot only,

Cheers,
Matt.
Title: Re: R8168.ko issues / Diskless MD issues
Post by: Steakboy on September 21, 2011, 09:39:39 pm
Hi Matt,

I've done all of that again, triple checked all the files are correct, r8168 was in the modules file (shoudl it be r8168.ko maybe). I've ran depmode - a and then modprobe, but it's still failing after about 90 seconds of the boot process.

The actual NIC is an RTL8139, which Foxconn (manufacturer of the motherboard) have given me a link to the r8168-8.025.tar.bz2 download - the one I've installed. 

Russell
Title: Re: R8168.ko issues / Diskless MD issues
Post by: Steakboy on September 22, 2011, 08:41:40 pm
OK, tonight I've tried to create a USB drive with GRUB and the correct details, copied from http://wiki.linuxmce.org/index.php/GRUB_PXE , but I'm having no luck!

Incidentally, my Windows laptop wont boot from the USB key, although it seems to have all of the correct files on it.

Am I best to source a new motherboard, without a Realtek NIC? I'm going grey because of this!
Title: Re: R8168.ko issues / Diskless MD issues
Post by: purps on September 22, 2011, 11:32:27 pm
What kind of NICs have you got on the core? Please indicate which you are using for the internal network.

Cheers,
Matt.
Title: Re: R8168.ko issues / Diskless MD issues
Post by: Steakboy on September 22, 2011, 11:37:37 pm
I have 1 additional NIC that isn't working fully (I think it's to do with the eth:0 and eth:01 settings), but the on board NIC, which I am using for the internal network, is a Realtek RTL8111E (M4A88T-M mb).

Edit: The other is branded as RoHS PCIeGLAN, which doesnt throw up a lot online.
Title: Re: R8168.ko issues / Diskless MD issues
Post by: magner on September 26, 2011, 10:39:01 pm
Hey how you doing mate,

Follow these steps inside terminal and you should get the 8168 NIC working. my 2nd NIC runs on the 8111 driver and works out of the box.

Setting up the 8168 NIC

   19  cd /etc/                                                         
   18  cd modprobe.d                                                     
   19  nano blacklist 

add a line “blacklist r8169”     
                                           
   20  update-initramfs -k all -u                                       
   21  rmmod r8169                                                       
   22  cp r8168.ko /lib/modules/2.6.27-17-generic/kernel/drivers/net/
   23  depmod                                                                           
   24  modprobe r8168                                                                   
   25  lshw -C Network          (this should show r8168 now to be the driver)

Cheers
Dan
Title: Re: R8168.ko issues / Diskless MD issues
Post by: Steakboy on October 07, 2011, 06:42:43 pm
I tried everything down in the thread, but it simply wouldn't work.

In the end, I decided to put the HDD into the client machine, and did a fresh installation, made the changes for the R8168 driver, and now both are happily talking to each other.

It seems really strange that it wouldn't work the other way around.

Thanks for the advice offered on the thread.