by falcon40 » Aug 27th, '12, 09:08
Hello Ken-Bergen,
Thank you for the reply. I have edited the subject to remove the "closed" moniker. I did not want to trouble the whole for one unique occurence. Thanks for correcting me and allowing me to proceed further.
I reinstalled with KDE only and wireless connectivity initiates and holds after each boot. What I have done in the past is use the "task-XXX" packages to add desktops. I used to use the DVD (free) version and did not seem to have too many problems. This time I used the Live CD to install Mageia 2 and, in KDE, everything is much more consistent and predictable. I noticed that if I tried to install from boot, I experienced random dropouts. However, if I ran the Live CD and installed from within the test environment I ended with a rock solid implementation that initiates wireless connectivity every time. (This may be one reason there is such a divide in opinion on whether the wireless scripts, commands and programs are sufficient.) Before I try to reinstall other desktops, is there a particular process which should be followed?
One thing I am wondering about is whether removing "mono" instances can break the network connectivity of all the other desktops. I did try to remove any "mono" instances (no particular agenda, necessarily--just trying different implementations). Other than that I did not do anything I have not done in the past.
I will await a reply in the event you or others have any insight before I try again. I am not averse to additional trial and error as it helps me learn but the process is time consuming. I am a little wary as once I tried to access other environments, that is when all my issues started.
falcon40