R8168.ko issues / Diskless MD issues

[purps]

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.

[Steakboy]

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

[Steakboy]

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!

[purps]

What kind of NICs have you got on the core? Please indicate which you are using for the internal network.

Cheers,
Matt.

[Steakboy]

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.

[magner]

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

[Steakboy]

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.