On a fresh install, including a drive reformat, of openSUSE 13.2, the root desktop is jumbled and disorganized. Some elements do not appear until the mouse passes over them, others show inappropriate font sizes or squashed text. Mouse response is sluggish, although I do not see inappropriate hard drive activity.
The wallpaper displays correctly, as do some of the windows that pop up during logon. The logon screen itself is OK.
On previous installs, this has only affected root, but this last attempt, the user’s desktop is also corrupt.
I’m hoping there’s some config file I can delete and have the system rebuild, or some such.
Keep in mind, please, that fixes have to go through the console; the desktop is almost useless.
I’ve downloaded the install package several times, and verified the checksum. I’m installing via a USB flash drive.
I’m using the default install, except for forcing the reformat. I’ve got swap, root(ext4), and home(XFS) partitions.
My motherboard is an ABIT NF8-V2 with 1.5 GB.
Video is a PNY GeForce 6200AGP.
CPU is a AMD Sempron 2600+ running at 1.6 GHz.
Yes, I’m using KDE, because that’s the default. Shoulda said.
And the “root desktop” is the one created for the “root” admin account, as opposed to the desktop created for the ordinary user account. As I understand it, these two accounts are also part of the default.
I restarted the machine, but this time I took the “advanced options” at the boot splash screen (the one with the chameleon logo across the top), and chose “openSUSE…(recovery mode)”.
This brought me up in the automatically logged in user account, which is now perfectly fine, even after reboot.
The root admin account is still bargled.
I’ve done this before, which is why I thought the user account was OK–it’s not, but it can be fixed.
As a matter of ordinary practice, yes, absolutely–and yet it seems that the root desktop should display correctly, especially since the problem occurs in other accounts as well.
Also, while I am configuring this small, standalone, personal machine with no corporate or government security issues at stake, and which as yet has no personal stuff on it either, it would be convenient to log in as root, do the desired configurations, then log out and thereafter always use an ordinary user account.
I hope it is not SUSE’s policy to discourage the use of the root account by presenting an unusable desktop.
> As a matter of ordinary practice, yes, absolutely–and yet it seems that
> the root desktop should display correctly, especially since the problem
> occurs in other accounts as well.
Yes, it should work.
> Also, while I am configuring this small, standalone, personal machine
> with no corporate or government security issues at stake, and which as
> yet has no personal stuff on it either, it would be convenient to log in
> as root, do the desired configurations, then log out and thereafter
> always use an ordinary user account.
I do the same thing
> I hope it is not SUSE’s policy to discourage the use of the root account
> by presenting an unusable desktop.
No. Not more that not recommend it. I remember a release on which root
got a background paper in reds, with dozens of bombs
Very nice, I liked it. People asked how to remove it, but I let it stay.
never log into a GUI as root!!! never ever for any reason.>:(
If it works ok in recovery mode then it is probably a video driver problem. Have you installed the proprietary driver?? The 6200 chip set is getting long in the tooth. I’m not certain that the current drivers support it. Maybe check on the NVIDIA site.
Ok I looked 6200 is still supported with the GO2 flavour driver (304.125)
I recommend you add the NVIDIA repo in Yast and install the GO2 flavour driver.
it is best to NOT to have auto login on since it allows more option in trouble shooting if it is off. If you need instruction on turn it off please ask.
I turned off auto-login, rebooted, took the recover option, and logged in as root. OK! Problem worked around on both accounts.
then it is probably a video driver problem. Have you installed the proprietary driver?? The 6200 chip set is getting long in the tooth. I’m not certain that the current drivers support it. Maybe check on the NVIDIA site.
Ok I looked 6200 is still supported with the GO2 flavour driver (304.125)
I recommend you add the NVIDIA repo in Yast and install the GO2 flavour driver.
It seems I’m running the “noveau” driver; I don’t know if that’s what I had from the start, or if that’s what got used after the recovery mode boot.
Nvidia’s site recommends using the driver distributed with the package, rather than their generic driver–but I might fall back to one of the earlier drivers, such as nv.
Now that the mosquitoes are out for the evening, I need to go do yardwork so that they don’t starve.
Current plan of action, once I’ve feed the arthropods, is to reinstall, including the Nvidia community repository, and see what comes of that.
Something else I want to try: creating another user both before and after the recovery boot.
Thanks to everyone for assistance so far.
===
Off topic comments:
never log into a GUI as root!!! never ever for any reason.>:(
Yes, I’m trying to discipline myself to use the console, sudo, even vi.
However, my attitude towards such things may be summed up in the suggestion that the best car safety device would be six inch spikes in the middle of our steering wheels; I think logging into the GUI as root would be a close approximation.
heck, my password on both accounts (admin and user) while climbing the learning cliff is “letmein”, since I have to use it over and over and over and over and…
And let’s face it:
When I figure out how get everything set the way I want it, I’m going to do a final format and reinstall, and use Best Practices, including good passwords, when I do it.
So: My machine, my needs, my rules thankyouveddymuchyes.
it is best to NOT to have auto login on since it allows more option in trouble shooting if it is off. If you need instruction on turn it off please ask.
This we agree on; it’s the default, it took me awhile to figure out how to make it stop happening on install, and I missed that step last time.
On 2015-06-20 01:06, tenthumbs wrote:
>
> gogalthorp;2715963 Wrote:
>> 2) If it works ok in recovery mode
>>
>
> ?Why does it work in recovery mode? What changes?
Well, the kernel boots with may options that disable many features. It
even disables all cpu cores but one. Then, graphics mode runs with a
different configuration that should always work, even if at a lower
resolution and speed.
> It seems I’m running the “noveau” driver; I don’t know if that’s what I
> had from the start, or if that’s what got used after the recovery mode
> boot.
Nouveau is the default, opensource driver.
nvidia is the proprietary driver, and you have to take extra steps to
install it. Basically, there are two ways: the hard and easy way. I
recommend the later.
I’m using the Nvidia 6150LE, which is probably similar. It actually works okay with nouveau if you disable desktop effects in KDE. However, I usually install the nvidia driver (from the nvidia repo), for better results – and desktop effects are okay with that driver.
Hm, well, that was interesting. A useful learning experience I shall long contemplate in my eternal quest for enlightenment. Oooommmm…
I told the installer to use four repositories. Yast tells me they all run at priority 99.
[local]
USB Flash drive
[default] /* Then, somewhere, I picked up the idea you should also use these, or possibly that they were, as noted, the defaults that are always check. /
Main Repository (OSS)
Main Repository (NON-OSS)
[nVidia] / Recommended by gogalthorp. I don’t know why this was entered twice; I think I only entered it once.
13.2 /* http://download.nvidia.com/opensuse/13.2/
NIVIDIA Graphics Drivers /http://download.nvidia.com/opensuse/13.2 */
[whatthehell]
Main Update Repository
And, wow, installation took a long, long time, over an hour. i think because all repositories ran at the same priority.
next round, I think I’ll just go with NVIDIA and Main Update (Advice solicited–or should I start a separate thread for that?
Nevertheless, whatever got installed runs much better than the “nouveau” driver.
If I install with the DVD installer and using online repos, then I usually go with the main update repo. I sometimes use also the main OSS repo.
For fastest install, don’t use any online repos with the DVD installer, though of course you will need them with the NET installer.
There have been major updates to Gnome and KDE since 13.2 was released, and those will be in the update repo. If you are using KDE, then there are some large packages such as the wallpaper packages that will be installed from the main OSS repo. Install will be faster without those. But eventually they will get installed when you install something from the repo or run online updates. So you are trading install time with later update time. If your internet connection is slow, then better to do at a later update, perhaps overnight when you are not using the computer for anything important.
As for Nvidia – on my Nvidia box, I usually go with nouveau for the initial install. Then I login with “icewm” which works pretty well with nouveau. And there I add the nvidia repo and add the nvidia driver. I don’t login to KDE until after I have it working with the nvidia driver.
[way too much information here; not only am I saving notes for myself, but for the Next Guy that stumbles on this post with similar problems. A lot of what I’ve found in my own searches refers to openSUSE 11, way obsolete and sometimes very different.
[Is it appropriate for me to put up an installation report here of what I’ve found, the problems and fixes I came up with?]
As it happened, this time I took the two default repositories:
Main (OSS)
Main (NON-OSS)
…and the nVidia Graphics driver, because nouveau seems not to play well on my graphics hardware. I ended up with nVidia G02-304.125-36, whatever that means, and I seem to have a good desktop now.
So noted. I’ll do one more install, i want to try saving my browser configuration and a few other bits and pieces between installs.
But yeah, next time, I’ll just go with the update repositories, which I assume forces all the normal stuff to come out of my thumb drives.
There have been major updates to Gnome and KDE since 13.2 was released, and those will be in the update repo. If you are using KDE, then there are some large packages such as the wallpaper packages that will be installed from the main OSS repo. Install will be faster without those. But eventually they will get installed when you install something from the repo or run online updates. So you are trading install time with later update time. If your internet connection is slow, then better to do at a later update, perhaps overnight when you are not using the computer for anything important.
Interesting. This is giving me good insight into how to manage the installation and update process. Because I’m not doing anything on this machine right now EXCEPT playing with installation and update, I’m going to try to get a completely updated system right out of install.
nVidia installation notes for the Next Guy who stumbles across this post on a keyword search:
At the very start of the install, right after the installer boots up, you must check both
Add Online Repositories
Include Add-on products
“Add online” gets you access to the Main and Update repositories, and “Include Add-on products” will later allow you to enter the nividia link.
But that doesn’t happen until much later in the install sequence, after partitioning the hard drives and setting the time zone.
If you type in the nVidia link, be sure to spell “opensuse” in all lower case; nvidia’s server is case sensitive.
I don’t know if there’s a way to browse to that repository.
As for Nvidia – on my Nvidia box, I usually go with nouveau for the initial install. Then I login with “icewm” which works pretty well with nouveau. And there I add the nvidia repo and add the nvidia driver. I don’t login to KDE until after I have it working with the nvidia driver.
Unfortunately, nouveau works so badly for me that the desktop is almost unusable; it’s even hard to start a console session. I have to take the “recover” option at boot. I’d much rather get the correct driver right from the very start.
The “correct” driver for me seems to be, again, the “nVidia G02-304.125-36” Both the G02 and the 304 designation seem to turn up in conversation a lot.
OK, off to other things.
Next hassle: install Pale Moon instead of Firefox. Couldn’t get it to play last time.
Ooh, one other thing: I tried to Export the installation settings to an XML file in the root directory, but it didn’t stick. Maybe it’s in my thumb drive? Huh, can’t get Dolphin to recognize it. Ah well.
If you could use nouveau with the install, you can probably login to Icewm (one of the available desktops). The installer is using that.
If the graphics are bad even for the install, then add “nomodeset” to the end of the kernel command line while booting into the installer or into your system. You will get lower resolution graphics, but it will then work. You can use that to install the nvidia drivers.
The G02 driver is for older cards. My computer with nvidia was purchased in 2007, so that makes it 8 years old. Support for that card will eventually go away, so I’ll either have to buy a newer graphics card, put up with nouveau or use “nomodeset” always. The “304.125” is the nvidia driver number. I think it is version 125 for the 304 driver. Newer nvidia cards use a different driver.
The details you have provided in your last post are pretty good, and I hope others do find them helpful.
All your personal setting like browser configs etc are saved in your home directory (short hand ~/ always is your personal home) If you install and NOT format the home partition then your personal stuff is saved if you have taken the defaults and have a separate home partition. So If you simply reuse the partitions rather then blow them away and mark the home parturition to mount as /home and NOT format it your personal settings are preserved.
You should limit the number of active repositories to the defaults, packman and nvidia, until you get a feel for it since it is possible to install stuff from any random repo that may break your system. Not all repos are “official” Priorities are no longer the main way to determine where a package comes from. Now downloaded packages have a vendor (repo) property that essential only allows updates from the vendor that you originally used even if newer are in some other repo even if the priority number of that repo is lower. You can of course force a vendor change if you want. You can install stuff from any random repo but either remove or disable the repos so only updates can come from the official community ones +packman
The first update after an install is huge at this point so it will take a while depending on your download speed.
On the jumbled desktop front, I see from logs in /var/log/YaST2 that the nouveau driver is apparently still being installed, but works now, so maybe running the updates is enough to make it play? hm.
===
Other installation and learning stuff.
I probably need to start making separate threads for some of this stuff, or at least start a “Hitting ten thumbs with a thousand hammers” thread to log my learning experience.
On the machine of discourse, which I am using exclusively as a learning platform for installing and configuring openSUSE, I pretty much want to wipe it clean each time as part of the installation exercise. But I wanted to save some logging and hardware/software manifests, and was using a separate, persistent partition for that.
Except not really, because as I played with the Expert Partitioner, I ended up deleting that partition between installs because I’d allocated way too much space for it.
And I’ve discovered that my mail dot com accounts offer free cloud space, which would serve my purposes just fine.
And I’m now seeing references to things like /var/log/YaST2 and even the option of sending installation logs to a “remote” NSF server. (Actually, my desktop machine right over ----> there, but I need to setup the NSF server on it. And it’s Win7.)
You should limit the number of active repositories to the defaults, packman and nvidia, until you get a feel for it since it is possible to install stuff from any random repo that may break your system. Not all repos are “official” Priorities are no longer the main way to determine where a package comes from. Now downloaded packages have a vendor (repo) property that essential only allows updates from the vendor that you originally used even if newer are in some other repo even if the priority number of that repo is lower. You can of course force a vendor change if you want. You can install stuff from any random repo but either remove or disable the repos so only updates can come from the official community ones +packman
The first update after an install is huge at this point so it will take a while depending on your download speed.
Ah, good info there. Last install I unchecked the default OSS and NON-OSS repos, checked the Update repos, and added the nVidia repo. Now in YaST, I see I still have a bunch of updates to perform. Le sigh. Also, I’m still not taking enough notes to remember exactly how things are going and what difference they make.
===
Now I need to work in atom-space, doing some carpentry: I’m installing Pal-ruf panels UNDER the elevated deck over my carport. Recently replaced the old decking, because it was laid on half-inch sleepers over plywood, which trapped pine tree trash, which held moisture against the underside of the decking boards and the top of the plywood, which caused everything to warp and rot. Le sigh.
This stuff is on hangers underneath the joists; plenty of room to let the trash wash away.
===
Gosh, larval stage is fun. I’ve been here before, several times, but it never really took. Feels different this time, though. You folks help a lot.
In home is all personal settings ie email credentials/documents/music/browser settings/ settings for any and all programs you run.
Linux is multi user in the true sense not in a MS sense. Any and all things that are your personal choices are in your home as is the same for each and every user. Most system settings are in /etc (like 99.9%) You do not want /etc too be on a different partition since there are files needed that must be available at boot before any other partition is mounted. Most notably /etc/fstab which has the info on what to mount at boot. So take care about that. There are other directories also needed so having them on another partition can cause problems. Also there are virtual directories that in essence contain process. Remember in Unix all things are files. Look in /proc /sys /dev all these are virtual and do not exist on the hardware drive.
The install image does not change from the day it is released so now there are a ton of updates as I said.
Have no idea if you can setup a true NSF on Windows but there is samba which allows you to do Network sharing with MS stuff. Actually Windows Networking is just a very bastardized version of NFS but it is not (surprise surprise) interoperable.
