Topic: SME Server 7.5 modprobe.conf, network card driver disappears on reboot

[jaysen]

I am having an issue with our SME Server 7.5 installation.  Our server has an on-board Intel gigabit ethernet adapter that uses the e1000e driver.  I see this driver is installed but the alias eth0 e1000e line was missing from modprobe.conf but instead it has alias eth0 tg3 which does not work for this adapter.  When I replace the tg3 with e1000e I am able to bring up the eth0 interface and all works fine until I have to reboot the server after updates.  I notice my changes are gone and it's back to the tg3 driver.

Why does it erase my settings and how can I get the e1000e driver to permanently load even after reboots and updates?  This is a big problem because if something happens when I am not in the office and the driver doesn't load, my entire office can't do their work.  Can someone tell me how to fix this problem?

Thank You,

Jaysen

[cactus]

Don't report problems here - Please report bugs and potential bugs in the bug tracker

[jaysen]

Don't report problems here - Please report bugs and potential bugs in the bug tracker

That doesn't quite solve my issue, but thanks. 

[Stefano]

filling a bug will do

please report here the reference, thank you

[janet]

jaysen

That doesn't quite solve my issue, but thanks.

Your issue will only get solved if you lodge a bug report, what is difficult about doing that ?

[Igi2003]

Hello,
open with vi or mcedit "/home/e-smith/db/configuration" and search for String "EthernetDriver1=xxxx". Replace "tg3" with "e1000" and save.
"signal-event post-upgrade" and "signal-event reboot" should fix your problem.
modprobe.conf is build with templates and setting in configuration database.

Igi

[CharlieBrady]

open with vi or mcedit "/home/e-smith/db/configuration" and search for String "EthernetDriver1=xxxx". Replace "tg3" with "e1000" and save.
"signal-event post-upgrade" and "signal-event reboot" should fix your problem.

Please don't give bad advice. The configuration database should not be edited with a text editor.

[jaysen]

Hello,
open with vi or mcedit "/home/e-smith/db/configuration" and search for String "EthernetDriver1=xxxx". Replace "tg3" with "e1000" and save.
"signal-event post-upgrade" and "signal-event reboot" should fix your problem.
modprobe.conf is build with templates and setting in configuration database.

Igi

Igi,

Finally someone that cares enough to understand and actually give me an answer rather than tell me to go submit a bug when it's not a bug.  Thank You!

You probably already know this but pay no attention to those who simply are here to attack those who seek help.  They do that because they let the power of being a moderator get to their tiny little heads. 

Thanks Again,

Jaysen

[jaysen]

Please don't give bad advice. The configuration database should not be edited with a text editor.

CharlieBrady,

I don't see Igi's advice as bad.  The nice thing about Linux is that it's "Open Source" and things can be changed especially if the configuration database is wrong which in my case it is.  My ethernet card does not use the tg3 driver and if the database is overwriting my configuration with that driver then it is wrong so I will change it to make it work for my hardware.  Please do not attack others if they have the answer and you don't. 

Have a nice day!

Jaysen

[Stefano]

jaysen: editing configuration db directly is a bad idea.. and such a suggestion is bad because you could break your server..

please, change your attitude, thank you

[CharlieBrady]

My ethernet card does not use the tg3 driver ...

You don't seem to be asking yourself (or anyone else) why your configuration database contains the wrong information. Did you change your hardware, and not then change the configuration by running option 2 from the admin console menu?

[CharlieBrady]

I don't see Igi's advice as bad.

That is because you are new here, and inexperienced with this software.

Please do not attack others if they have the answer and you don't.

I didn't attack anyone. I asked someone not to provide bad advice.

You seem to have a very combative and unco-operative attitude. If you had followed the advice first given to you, your problem would have been amicably resolved long ago.

Anyway, goodbye, good luck and good riddance.

[Igi2003]

jaysen: editing configuration db directly is a bad idea.. and such a suggestion is bad because you could break your server..

please, change your attitude, thank you

If you don´t know what you do, you can break the server, if you know what you do, you don´t break the server!
I´ve explizit write what to do to. My D-Link USB Ethernet Adapter will not work. Admin console menu doesn´t recognize this Ethernet Adapter.
SME 8.0beta5 does not recognize my Marvell Yokon Onboard. The Server select e1000 driver for this card. Only if I change manually in configuration db, the Ethernet Card will work.

Sorry, but when a User needs help for his productive server, and I have an answer, I will tell this. If an productive server in an Company breaks after update, then the Problem must be solved quickly. The server cannot be powered down for few days till the problem is solved in the Bug Tracker.

Sorry, but I don´t understand this attitude.

This post is the last post of me in this forum. Bye Bye and good luck for the future with your SME!! I don´t feel like it.

[cactus]

If you don´t know what you do, you can break the server, if you know what you do, you don´t break the server!

You clearly seem to lack some, the db file expilictly reads to not manually edit it:

Code: [Select]

# DO NOT MODIFY THIS FILE.
# This file is automatically maintained by the Mitel Networks SME Server
# configuration software.  Manually editing this file may put your
# system in an unknown state.
Still you advice to edit that file, to a user from which you can hardly judge the experience...

You had better advice to use the db commands:

Code: [Select]

db configuration set EthernetDriver1 e1000

Sorry, but when a User needs help for his productive server, and I have an answer, I will tell this. If an productive server in an Company breaks after update, then the Problem must be solved quickly. The server cannot be powered down for few days till the problem is solved in the Bug Tracker.

You can still report a bug as this might affect more users. Using a free product as SME Server comes with some drawbacks and obligations, one is to behave in a manor the community can benefit from and that is to report issues when you see them in order to improve this product for all users.

Sorry, but I don´t understand this attitude.

Although I see your point, I fail to understand your attitude too. You could have at least reported a bug and documented your workaround in there. It might have helped us focus on a issue and find a proper resolution.
It is not the first time I have to say this to you or other users in the German forums, I am disappointed that you all are so reluctant.

This post is the last post of me in this forum. Bye Bye and good luck for the future with your SME!! I don´t feel like it.

Opting-out is one way to resolve your frustration, I doubt however it will solve your issues with SME Server in the future. Good luck!

[Stefano]

igi2003: first of all I was answering to jaysen, not to you.

then.. you, and I and maybe many users here know hot to edit db files directly (and, I repeat, this is a bad idea), but when you give such an advice here you'd think that next month, or maybe next year, someone could find it without knowing anything about SME..

do you still think your suggestion is a good one?

anyway, I really don't understand why you want to leave the forum and the community.. stay here, and keep helping people, thank you