Unrecognized NIC - Revision history

Joerod at 23:40, 14 October 2012

2012-10-14T23:40:37Z

←Older revision		Revision as of 23:40, 14 October 2012
Line 70:		Line 70:

	One thing is certain though, once you make one stuff up, you can go back and try to fix it up but more often than not you end up in knots! It is usually better to go right back to the beginning and completely delete the MD from the device tree (and allow it to delete all the files - that's why deleting an MD is so slow) and starting again, being concious that the new MD will have a new device number, and that often it will detect it as AMD64 rather than i386, and if your core is i386 (which it should be) the chroot won't work...		One thing is certain though, once you make one stuff up, you can go back and try to fix it up but more often than not you end up in knots! It is usually better to go right back to the beginning and completely delete the MD from the device tree (and allow it to delete all the files - that's why deleting an MD is so slow) and starting again, being concious that the new MD will have a new device number, and that often it will detect it as AMD64 rather than i386, and if your core is i386 (which it should be) the chroot won't work...

			BIOS boot firmware -> PXE boot firmware -> vmlinuz RAM disk bootstrap software -> initramfs Linux micro kernel boot software -> Linux full kernel

	--colinjones		--colinjones

2012-10-14T16:26:53Z

@@ Line 50: / Line 50: @@
 Now reboot your media director. Everything should come up, the way it is meant to.
 == Caveat ==
 Whenever you click Regenerate this media director, you have to redo the step for the initial ramdisk of the media director.
 The above steps do not work, if the media director and the core utilize two different CPU architectures,ie. one is using AMD64 the other i386 (chroot won't work). Note - AMD64 does not necessarily imply an AMD CPU, it just means the CPU is in 64 bit mode. An Intel CPU can just as easily be AMD64, and vice versa for i386, it can be an AMD CPU, just in 32 bit mode. i386=32bit mode; AMD64=64bit mode, it says nothing about the CPU manufacturer.

2012-10-09T05:06:13Z

←Older revision		Revision as of 05:06, 9 October 2012
Line 1:		Line 1:
	{{versioninfo}}		{{versioninfo}}
	[[Category: Networking]]		[[Category: Networking\|NIC]]
	[[Category:Network Adapters\|*]]		[[Category:Network Adapters\|*]]
	[[Category: Troubleshooting]]		[[Category: Troubleshooting]]
	~~[[Category: Tutorials]]~~

	'''Note''' If you have a r8168 NIC, see the [[r8168]] page first.		'''Note''' If you have a r8168 NIC, see the [[r8168]] page first.

2012-10-08T11:49:01Z

2012-05-18T12:59:05Z

Modify modules on core

←Older revision		Revision as of 12:59, 18 May 2012
Line 14:		Line 14:
	Or for the Marvell Yukon 88E8055 chip for example add;		Or for the Marvell Yukon 88E8055 chip for example add;
	sky2		sky2
	Or for a foxconn nt330i / Aleutia H1 you'll need to download the linux drivers from Atheros http://partner.atheros.com/Drivers.aspx and install them, then place the module in the modules file		Or for a foxconn nt330i / Aleutia H1 you'll need to download the linux drivers from Atheros http://partner.atheros.com/Drivers.aspx (or follow instructions and download drivers from http://joefleming.net/2010/05/26/atheros-ar8131-and-linux/ if that link is dead) and install them, then place the module in the modules file
	atl1e		atl1e

2011-01-14T06:42:12Z

Modify modules on core

←Older revision		Revision as of 06:42, 14 January 2011
Line 15:		Line 15:
	sky2		sky2
	Or for a foxconn nt330i / Aleutia H1 you'll need to download the linux drivers from Atheros http://partner.atheros.com/Drivers.aspx and install them, then place the module in the modules file		Or for a foxconn nt330i / Aleutia H1 you'll need to download the linux drivers from Atheros http://partner.atheros.com/Drivers.aspx and install them, then place the module in the modules file
	~~arl1e~~		atl1e

	After adding the above line (and saving the change of course ;-) ), you have to recreate the initial ramdisk. For 0704 do;		After adding the above line (and saving the change of course ;-) ), you have to recreate the initial ramdisk. For 0704 do;

2011-01-14T05:36:14Z

Modify modules on core

←Older revision		Revision as of 05:36, 14 January 2011
Line 14:		Line 14:
	Or for the Marvell Yukon 88E8055 chip for example add;		Or for the Marvell Yukon 88E8055 chip for example add;
	sky2		sky2
			Or for a foxconn nt330i / Aleutia H1 you'll need to download the linux drivers from Atheros http://partner.atheros.com/Drivers.aspx and install them, then place the module in the modules file
			arl1e

	After adding the above line (and saving the change of course ;-) ), you have to recreate the initial ramdisk. For 0704 do;		After adding the above line (and saving the change of course ;-) ), you have to recreate the initial ramdisk. For 0704 do;
	/usr/pluto/bin/Diskless_BuildDefaultImage.sh		/usr/pluto/bin/Diskless_BuildDefaultImage.sh

2010-05-05T08:47:09Z

2009-08-10T22:04:12Z

2009-07-28T07:48:19Z

Caveat

←Older revision		Revision as of 07:48, 28 July 2009
Line 49:		Line 49:
	== Caveat ==		== Caveat ==
	Whenever you click Regenerate this media director, you have to redo the step for the initial ramdisk of the media director.		Whenever you click Regenerate this media director, you have to redo the step for the initial ramdisk of the media director.
	The above steps do not work, if the media director and the core utilize two different CPU architectures,ie. one is using AMD64 the other i386 (chroot won't work).		The above steps do not work, if the media director and the core utilize two different CPU architectures,ie. one is using AMD64 the other i386 (chroot won't work). Note - AMD64 does not necessarily imply an AMD CPU, it just means the CPU is in 64 bit mode. An Intel CPU can just as easily be AMD64, and vice versa for i386, it can be an AMD CPU, just in 32 bit mode. i386=32bit mode; AMD64=64bit mode, it says nothing about the CPU manufacturer.