I go and setup the network and reboot, when i get logged back in the network isnt working. If i restart the network service it works again - until the next reboot. Also, i have a dual monitor setup,each time i reboot it forgets the monitor settings. This is a fresh install on x86_64 system.
Any ideas?
What is the Desktop Environment you are using? Did you make any adjustments in YaST to how the network is managed?
Thanks,
-Nathan
Hi, I’m using KDE and no i didnt change the network manager, its set to ‘wicked’ which was the default i guess. but I do get a message when i run Network Settings: ‘More than one interface asks to control the hostname via dhcp. If you keep the current settings the behavior is non-deterministic. Involved configuration files ifcfg-eth0 dhcp.’
so i see a conflict but i dont know how to resolve it
I just tried deleting /etc/sysconfig/network/ifcfg-eth0 and the error message doesnt show up any more so thats good, but i dont think it affects my network failing to start on reboot or my monitor settings going away. I’ll try rebooting to be sure, but i dont hold out much hope there.
Well knock me over with a feather! Both the Network and Monitor issues are now resolved. I would really like to understand what was going on there.
-
You may have multiple network adapters enabled.
You should open up your Network Settings in YaST, and make sure only one device is recognized and enabled (likely a wired ethernet connection). If you have Wireless also, disable your wireless adapter, either by hardware or software (You can use rfkill for a software solution to switch wireless on and off). -
While in YaST Network Settings, verify how your adapter is identified, it’s likely something other than eth0. There is no need to change anything if things are working fine.
-
Is this a system upgrade from another version of openSUSE? By default, a new LEAP install does not use legacy device naming(eg etho, eth1, wlan0), each device name is an abbreviation of the NIC manufacturer.
TSU
Hi, I have 2 wired ethernet and 1 wireless, in yast they are shown as eth0, eth1 and wlan0. I had originally tried upgrading from 13.1 to leap 42.2 but that didn’t work so i did a complete fresh install including re-partitioning and formatting during the install. So really this is a fresh install. I only run static IP’s so I did have all 3 enabled and each was configured for static IP 192.168.0.x’s, when i ran into trouble the first thing i did was de-configure eth1 and wlan0 but the issue was still there. Its baffling to me that having this conflict with wicked and ifcfg-eth0 would cause the dual monitor setup to be lost on reboot - but ha6t is certainly what happened. BTW I was pleasantly surprised to see my network interfaces given rational names again. I really despised the naming convention of basically a long series of random numbers and letters - what a cluster-f&^k that was. I upgraded from 13.1 which I dearly loved to 42.2 because I wanted to have more recent libraries. I looked at 13.2 and 42.1 awhile back but rejected them for a number of reasons, but after trying 42.2 on Virtualbox it looked pretty good, I didn’t see any obvious issues on Virtualbox, at least none that were concerning, it was only on my full system that I ran into this. On 42.2 there are a few minor issues, but I can live with them (for instance - how come no button on ‘look and feel’ to get more themes there? Same with splash screens. but as i said those are minor issues, just wish they would address it, there are more but i wont bring it up here. Anyway - thanks for the help
This is a bit off topic but what really bugs me about Linux in general is not the actual system as a whole but the lack of a coherent help system. Man pages are great (they should ditch the info pages - no-one uses them as they suck), that’s not the issue, its in the GUI desktops, especially obvious in KDE where the help system is virtually non-existant - it reminds me of Borland in the 90’s - great software and **** poor help system. Help buttons either don’t do anything at all or bring up a dialog ‘Documentation not Found’. In other cases it brings you to the top of the Documentation tree and since there is no ‘find’ function (there is but it only searches the visible page - useless!). In the cases where the Help button or F1 actually brings up a context sensitive help window the Help text isn’t very good, in Bluetooth for example the Help buttons are actually disabled altogether (whats nap - had to google it but still don’t know why the nap button is there - a working help button that brings up good informative text, would of been nice) Anyway, that’s my really big issue with Linux and KDE in general - i would bet the same is true under Gnome and others - its always the case that help text is back-burner’d and a low priority
Hi
It is… 
We have a specific forum for rants and such, please refrain from this type of rhetoric in the technical help forums. Also note our sponsor is the Borland developer/owner…
A general comment on documentation in general…
First,
It has always been my personal Dev slogan that truly well written software does not require documentation. Documentation only exists when software is not intuitive.
Also,
IMO the general lack of documentation has existed for a long time and will get worse…
Because today the Internet is the documentation and there is willingness for just about anybody to write about anything when a need is recognized. Like everything else about the Internet, there is no guarantee that any “documentation” is accurate or well written, but there is hope that better articles will float to the top of any Internet searches.
This also means that each and every User will need to develop Internet savvy, and skills to find what is needed…
Since documentation is and will become more ad hoc, don’t expect that companies will want to devote resources to provide it.
IMO,
TSU
AFAIK no “fresh” LEAP install has reverted to legacy network device names, so I strongly suspect that you may have thought that you re-formatted, but didn’t.
If you simply re-partitioned without also re-formatting, but the new partitions are <exactly> the same as the old partitions, your old files will re-appear and you would have completed your upgrade from your original openSUSE. An interrupted upgrade could also have created new network devices, creating duplicates and conflicts.
Speculating,
TSU
Sorry, I will do as you say in the future. I did not intend to down Borland, they made a really super-great product in C++Builder (for Windows), i only wish they would still make the Linux version (what was it called, Kylix?) , I’d buy it in a heartbeat! The C++Builder IDE/RAD was the best (and easiest to learn) their ever was for developing GUI software.