Hello,
I was quite surprised today as I've just put my ssd from my 10-year-old AMD64 desktop computer into my new TS140 and clearos6.5 started and runs now... The new network-cards work out of the box, I can configure them as eth2 and eth3.
Except the LDAP sevice isn't starting and running.
I did some search around the forum, but could not find a solution - I hope the question is in the right place, I also searched the LDAP related category - would it be better placed there?
Can someone point me into the right direction for further search or did someone such a brute hardware change with success?
Better just set up everything new?
Thank you,
Bernd
I was quite surprised today as I've just put my ssd from my 10-year-old AMD64 desktop computer into my new TS140 and clearos6.5 started and runs now... The new network-cards work out of the box, I can configure them as eth2 and eth3.
Except the LDAP sevice isn't starting and running.
I did some search around the forum, but could not find a solution - I hope the question is in the right place, I also searched the LDAP related category - would it be better placed there?
Can someone point me into the right direction for further search or did someone such a brute hardware change with success?
Better just set up everything new?
Thank you,
Bernd
In Hardware
Share this post:
Responses (6)
-
Accepted Answer
-
Accepted Answer
You can generally get away with such a hardware change as long as the disk access method stays the same e.g. both use AHCI. I got away with it going from a 2009 AMD x2 to a 4th gen Core i3. If you wanted to keep the same interface names you can edit /etc/udev/rules.d/70-persistent-net.rules to manipulate the ethX - MAC address relationship as you want (reboot afterwards).
Also not relevant to your problem but can you give the output to:lspci -k | grep Eth -a 4
uname -r
With respect to the LDAP problem are you seeing any clues about why it is failing in the logs?
[edit]
Posts crossed.
[/edit] -
Accepted Answer
Thank you for answering!
I will set the renaming on my todo-list...
this the output:
[root@clearb rules.d]# lspci -k | grep Eth
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 04)
02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
[root@clearb rules.d]# uname -r
2.6.32-431.17.1.v6.x86_64
[root@clearb rules.d]#
for the 'grep Eth -a 4', there where no results. -
Accepted Answer
-
Accepted Answer
Ok, so there are more details:
lspci -k | grep Eth -A 4
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 04)
Subsystem: Lenovo Device 30a5
Kernel driver in use: e1000e
Kernel modules: e1000e
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04)
--
02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
Subsystem: Intel Corporation Gigabit CT Desktop Adapter
Kernel driver in use: e1000e
Kernel modules: e1000e
03:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8893 (rev 41)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family PCI Gigabit Ethernet NIC
Kernel driver in use: r8169
Kernel modules: r8169
(I've installed the old PCI-Card too (eth0) but I didn't add it to the ip-settings)
Thank you again for your help! -
Accepted Answer
Not so sure about the NIC issue now. It appears that the latest kernel (or one but last is now shipping with an updated e1000e driver.. The problem has bee the 82574L which used to give all sorts of trouble when the kernel was shipping with the 1.9.5. module. Still, there is a later one available. Download and install this one then restart networking or reboot.
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »