Right, I'm having trouble sorting my real MAC address out. I'm sure all of the information is out there but a combination of scattered info and being a Linux newbie means I'm struggling. (N40L running DSM 5.0-4418 update 1)
So, I began by using WinSCP to log in to the server, then opening a putty window I type "dmesg | grep "eth"" and I get the following:
[ 5.860379] jme: JMicron JMC2XX ethernet driver version 1.0.8
[ 7.218268] pcieport 0000:00:06.0: eth0: Tigon3 [partno(BCM95723) rev 5784100 ] (PCI Express) MAC address xx:xx:xx:xx:xx:xx
[ 7.218389] pcieport 0000:00:06.0: eth0: attached PHY is 5784 (10/100/1000Bas e-T Ethernet) (WireSpeed[1], EEE[0])
[ 7.218436] pcieport 0000:00:06.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] AS F[0] TSOcap[1]
[ 7.218481] pcieport 0000:00:06.0: eth0: dma_rwctrl[76180000] dma_mask[64-bit ]
[ 13.693107] usbcore: registered new interface driver ethub
[ 16.493917] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 18.952665] pcieport 0000:00:06.0: eth0: Link is up at 1000 Mbps, full duplex
[ 18.952665] pcieport 0000:00:06.0: eth0: Flow control is on for TX and on for RX
[ 18.952665] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 29.538110] eth0: no IPv6 routers present
Now I think I use the vender file patcher from http://raving.at/ on the USB that the server boots from which is fine but then I'm confused as to where I go from there. What are the randomize options for? Should I not be putting in my real MAC address in one or all of the fields? Also, where do I get my real serial from?
Presumably, once I have filled these fields in, I click the patch vender file button, and then re-boot from the USB and the info centre should show the correct MAC address?
If anyone can help me out I'll do my best to put together a step-by-step (similar to the update one that sk82jack did)
Right, I'm having trouble sorting my real MAC address out. I'm sure all of the information is out there but a combination of scattered info and being a Linux newbie means I'm struggling. (N40L running DSM 5.0-4418 update 1)
So, I began by using WinSCP to log in to the server, then opening a putty window I type "dmesg | grep "eth"" and I get the following:
[ 5.860379] jme: JMicron JMC2XX ethernet driver version 1.0.8
[ 7.218268] pcieport 0000:00:06.0: eth0: Tigon3 [partno(BCM95723) rev 5784100 ] (PCI Express) MAC address xx:xx:xx:xx:xx:xx
[ 7.218389] pcieport 0000:00:06.0: eth0: attached PHY is 5784 (10/100/1000Bas e-T Ethernet) (WireSpeed[1], EEE[0])
[ 7.218436] pcieport 0000:00:06.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] AS F[0] TSOcap[1]
[ 7.218481] pcieport 0000:00:06.0: eth0: dma_rwctrl[76180000] dma_mask[64-bit ]
[ 13.693107] usbcore: registered new interface driver ethub
[ 16.493917] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 18.952665] pcieport 0000:00:06.0: eth0: Link is up at 1000 Mbps, full duplex
[ 18.952665] pcieport 0000:00:06.0: eth0: Flow control is on for TX and on for RX
[ 18.952665] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 29.538110] eth0: no IPv6 routers present
Now I think I use the vender file patcher from http://raving.at/ on the USB that the server boots from which is fine but then I'm confused as to where I go from there. What are the randomize options for? Should I not be putting in my real MAC address in one or all of the fields? Also, where do I get my real serial from?
Presumably, once I have filled these fields in, I click the patch vender file button, and then re-boot from the USB and the info centre should show the correct MAC address?
If anyone can help me out I'll do my best to put together a step-by-step (similar to the update one that sk82jack did)
Did anyone ever experienced a kernel panic on the N54L. I recently installed XPEnology DSM 5 beta on my N54L and it has never been stable. I noticed that it crashed with high CPU load, like whenever it is scanning the plex library or postprocessingwith couchpotato or sickbeard. Sometimes it only stops the packages that are responsible of the high CPU load.
I have tried to reinstall, but the same problem accrued.
Does anyone have a suggestion? Did I do something wrong? And how can I track the problem of a kernel panic?
While I'm writing this, I tried to restart my NAS and now I wont boot anymore. I have a monitor connected to it and it writes a lot of "failed to write to log file /var/log/upstart/dsm-services.log
My data is not that important, I just want a "stable" XPEnology installation on my machine, so should I do a re-installation?
So I plan on getting MS Number 2 setup tonight with a direct install of XPenology rather than use ESXi.
I plan on installing two intel dual port nics next week after pay day, can I simply drop these in and the XPenology OS will detect them? I'm confident that ESXi can handle the install easily enough and then I just assign the cards, but the direct install im not sure on.
So I plan on getting MS Number 2 setup tonight with a direct install of XPenology rather than use ESXi.
I plan on installing two intel dual port nics next week after pay day, can I simply drop these in and the XPenology OS will detect them? I'm confident that ESXi can handle the install easily enough and then I just assign the cards, but the direct install im not sure on.
Yes this forum is a mess, but I'm not the main admin, I can't optimize it.
During one day I set up a paypal account for donation, it was hacked the same day...
I only do it for fun and sharing, not for money.
Before working on DSM 5.0:
- I just finished my updated ESXi build (DSM 4.3-3827) this week-end.
- Done some download server maintenance.
- I'm currently finalizing beta 8 which add support for sound, bluetooth, wifi and maybe dvb.
Yes DSM 5.0 is a "big" update, but it doesn't add amazing new features, "just" refresh the UI.
I know you guys out there like the Up to Date way but in IT this is more If It Works, Don't Touch It ^^
So YES I will of course work on DSM 5.0, but when I will found time for it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.