Default to Desktop

Question:

I ran into an issue with changing out my graphics driver to the factory Nvidia drivers and ended up not being able to get back into the -Desktop profile. To work around this I went in as safety and copied the -Default profile files and renamed them -Desktop. I’ve been running just fine over the last few weeks, but now I’m noticing things like issues with my wireless keyboard and my HTC Droid doesn’t show up automatically when I plug it in. What settings do I need to reconfigure so the copied files are built the way the original files were set? Either this or where can I snag a set of the original -Desktop files pre-configured so I can put those settings back in place?

Thank you,

Here’s a thought, and someone back me if you think this will work or not before I try it. What if I load 12.1 into my VirtualBox and copy the original boot files from there over to the host 12.1? Would this work or would there be some sort of conflicts that couldn’t be solved through updating?

While waiting for someone to give some insight I managed to figure out what the issue was with my HTC not showing up. Seems there was a “short” between the phone and the computer (me). I had the phone settings set to default PC interface on “sync media” rather than “Disk Drive”. Once I changed this setting it showed up as soon as I plugged it in. Good to know in the future. To temporarily solve some of the issues with the wireless keyboard I have moved the receiver from the back of my tower to the base of my monitor right in front of the keyboard. I’ve changed out the batteries (of course, first thought) but I still keep getting this lag that started when I changed to boot settings.

On 02/24/2012 06:16 PM, roguehorse wrote:
>
> Question:

first: i read your post two days ago and could not understand what you
telling

and, then i read both you first and second post yesterday and still
wondered what was going on…so, now on day three i have some questions
(which may or may not lead to an answer)

> I ran into an issue with changing out my graphics driver to the
> factory Nvidia drivers and ended up not being able to get back into the
> -Desktop profile.

does that mean you could not boot to KDE, and instead it stopped short
of the GUI with a blank screen? with what, a log in prompt and a
blinking cursor?

or was it just a pure blank screen?

or just what does not able to get back into “the -Desktop profile” mean,
exactly?

> To work around this I went in as safety

what does it mean to go “in as safety”?
does that mean at the first green screen you selected “failsafe”?
and, then it booted all the way to KDE?

> and copied the -Default profile

see,i have no idea what you mean by “-Default profile files” !
where are they? are they the default skeleton files in where, /etc/skel
or what? ok, so please give us a list of the including their full path

> files and renamed them -Desktop.

you renamed a bunch of files that had been named -Default to -Desktop ?

> I’ve been running just fine over the last few weeks

and the system now runs fine? even with the newly installed “factory
Nvidia drivers”?

instead of messing with the “-Default profile files” why didn’t you just
uninstall the newly troublesome “factory Nvidia drivers”???

and, while we are here:

  • how many driverS did you install?

  • by “factory” driver are you saying you changed from a released driver
    to a beta or experimental driver? please tell us the driverS you were
    running before you installed, and the driverS you are now running with
    few problems (after renaming the “-Default profile files”)

> but now I’m noticing things like issues with my wireless keyboard
> and my HTC Droid doesn’t show up automatically when I plug it in.

so while waiting for help, you learned those problems were not
associated with the installation of the new driverS and fixed those
problems --GOOD for you-- contratulations!

> What settings do I need to reconfigure so the copied
> files are built the way the original files were set?

did you make a backup copy of the files before you copied files–WAIT,
earlier you said you “copied the -Default profile files and renamed them
-Desktop” so, you do have a backup of all the original files…they are
there somewhere and now named “-Desktop”, right?

but since the original files didn’t let you boot to the “-Desktop
profile” why would you want to go back to using them?

> Either this or
> where can I snag a set of the original -Desktop files pre-configured so
> I can put those settings back in place?

but, you said you made a copy of the original, pre-configured and
working before you installed the apparently troublesome “factory
Nvidia drivers”

now, i admit i don’t really know (yet) what you did, how you did it, or
why you did it…but it sounds like

-you installed a beta/experimental nVidia driver
-it broke your system
-instead of back leveling the driver, you renamed some files somewhere
and suddenly everything ran fine for a “few weeks”
-(but you had two unrelated problems which you fixed)

so, everything was running fine for two weeks–but, what is the problem
now that causes you to want to revert to the original “-Default profile
files”

color me: Confused.


DD http://tinyurl.com/DD-Caveat
What does DistroWatch write about YOU?: http://tinyurl.com/SUSEonDW

On 2012-02-26 13:01, DenverD wrote:
> On 02/24/2012 06:16 PM, roguehorse wrote:
>>
>> Question:
>
> first: i read your post two days ago and could not understand what you telling

I have read the three posts and I understand very little. Desktop profile?
What’s that? I know of the desktop directory. Maybe a power profile? Nvidia
factory drivers? Drivers of the factory version of openSUSE? Proprietary
drivers? Original opensource drivers?

I read the rest, but I can not comment, I understood nothing and got lost.

roguehorse, please start again and explain yourself better if you want us
to respond.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

Ok, Denver and Robin,

First let me say thank you for taking the time to at least try and follow along with what I am experiencing here. I’m sorry that my posts seem obscure and a little hard to follow. I will try to provide more detail and clarify what I did and how it has led to where I am now.

  1. While trying to run some WebGL graphics online I would get error codes that my drivers were not to par and possibly needed updating. Check and double check for latest drivers for NVidia GeForce 9800 GT. Using “sysinfo” I find that the driver listed there as being used is called “nouveau” where I would expect NVidia and some release number. I search online again and find instructions to replace the nouveau driver with an official driver from NVidia. I download and install 3D driver from NVIDIA 290.10. The final atep in the installation process to replace nouveau driver with NVidia driver is to log out and log back in. I log out and cannot log back in.

  2. When I log out I am presented with a terminal looking screen and a prompt that says login> and I type in my log in name. Then password> and I do that too. Some processes scroll by and I get a final “Happy Computing” or something like that and a blinking terminal prompt. That’s it. From here, I hit Ctrl+Alt+Del. This reboots the machine and brings me to my original boot selection screen.

  3. The boot selection screen on my machine gives me 5 options.
    A. openSUSE (kernel number) -Desktop
    B. (Desktop)openSUSE-kernel number - Failsafe Mode
    C. openSUSE (kernel number) -Default
    D. (Default)openSUSE-kernel number - Failsafe Mode
    E. Windows

From this screen I let a little round timer graphic run out that boots me into the “A” openSUSE -Desktop. KDE never opens and I am presented with the same screen I got when I logged out the first time as following the instructions. I repeat this action again to see if I get the same results and I do.

  1. From this point, I log into option “B”, the Failsafe Mode of “A” the -Desktop configuration.and I get a working KDE desktop. Ok, I figure I have a working computer still and will not have to re-install. I have a hard time navigating a 640 x 480 failsafe resolution on a 1920 x 1080 monitor and manage to restart the machine again.

  2. ** Forgive me as I forgot to mention this action in the original posting ** When the machine restarts and I am presented with my 5 boot selections, this time I select “C” openSUSE (kernel number) -Default. Everything loads as normal into KDE and it “seems” I have everything exactly the same as it was before the trouble. From here I determine “C” to be very = to “A” at the boot loader screen. With this logic in mind I go to YaST and into Boot Loader.

  3. In Boot Loader I copy all the data for -Default and place them into the -Desktop boot load profile. From my understanding, I am making a copy of the -Default boot load profile and renaming it -Desktop. Now, in case I get this problem again, I still have a fall back to go to that is easier to use than failsafe mode. I also understand that using either boot load profile is going to utilize the same set of files in the /boot file. So I need to copy these files as well and rename them.

  4. Still working in the “C” option profile (openSUSE -Default), I log in to Dolphin as root and go to the /boot folder. I delete all files with the -Desktop in the file name. I then copy all similar files with -Default in the file name and rename them changing -Default in the file name to -Desktop. Now I understand that I have only copied and renamed files and not re-configured them to be exact as the original files. Still make sense?

  5. I reboot the machine and allow option “A” the copied -Default profile now named -Desktop to load. Everything goes as expected and I have a working desktop again WITH the NVidia drivers that I loaded instead of the nouveau drivers.

  6. I do some searching on line and try to find a good explanation of what the difference is between the two boot load profiles. All I can find is that -Default is configured optimized for openSUSE used primarily for server operations and -Desktop for daily UI operations. This leads me to believe that I need to change some settings in the “A” -Desktop boot load profile to be optimized for daily activity.

  7. This was my original question " I need to change some settings in the “A” -Desktop boot load profile to be optimized for daily activity "

  8. After doing all this I monitor my machine very closely looking for any signs of “out of ordinary” behavior. The phone and the keyboard started behaving odd and this is when I wrote the original question. However, I’m not one to just sit and wait for others to solve my problems for me, so I continue to try and try again to attempt to solve the issue myself while waiting for someone FAR MORE knowledgeable than I to lend a bit of wisdom.

  9. While waiting for my “ray of sunshine” I figured out the phone and the work around for the keyboard for now. However, I’m still very sure that the files I deleted in /boot really should be replaced with the exact same files. My current kernel number is 12.1 - 3.1.9 - 1.4.

I hope this step by step explains things a little bit better. Sorry for any confusion.

On 02/27/2012 06:16 AM, roguehorse wrote:
>
> 1. While trying to run some WebGL graphics online I would get error
> codes that my drivers were not to par and possibly needed updating.
> Check and double check for latest drivers for NVidia GeForce 9800 GT.
> Using “sysinfo” I find that the driver listed there as being used is
> called “nouveau” where I would expect NVidia and some release number. I
> search online again and find instructions to replace the nouveau driver
> with an official driver from NVidia.

where did you find these instructions?

if you did not find them here: http://tinyurl.com/37v9y7m then you most
likely found and followed the wrong instructions and that is probably
the root cause of your problems…

it is very important to recognize that the internet remembers for a
LONG time…and, you can easily find instructions on how to do things
that worked great two years ago, on Debian or Red Hat and never worked
and never will work on openSUSE…(and what works here may or may not
work on Arch or Mint)

> I download and install 3D driver
> from NVIDIA 290.10. The final atep in the installation process to
> replace nouveau driver with NVidia driver is to log out and log back in.
> I log out and cannot log back in.

ok, THAT is the point you should have asked here: What do i do now?

> <big snip>
> 5. With this logic in mind I go to YaST and into Boot Loader.

the YaST boot loader is only a way to edit one file in the system, the
/boot/grub/menu.lst file

>
> 6. In Boot Loader I copy all the data for -Default and place them into
> the -Desktop boot load profile.

AH! that is what that meant…hahahaha (not laughing at you, laughing at
me being unable to figure out what the heck you were talking about)

> From my understanding, I am making a
> copy of the -Default boot load profile and renaming it -Desktop.

ok, but those are not a “profile” they are “boot options” or “kernel
command line parameters”

> Now, in
> case I get this problem again, I still have a fall back to go to that is
> easier to use than failsafe mode. I also understand that using either
> boot load profile is going to utilize the same set of files in the /boot
> file.

no, those boot options do not make up a “boot profile” and nothing on
the Boot Options line represents a “file” in “/boot” or “/boot file”

> So I need to copy these files as well and rename them.

those are NOT files, they are words.

>
> 7. Still working in the “C” option profile (openSUSE -Default), I log
> in to Dolphin as root and go to the /boot folder. I delete all files
> with the -Desktop in the file name. I then copy all similar files with
> -Default in the file name and rename them changing -Default in the file
> name to -Desktop. Now I understand that I have only copied and renamed
> files and not re-configured them to be exact as the original files.
> Still make sense?

no! are you saying you deleted all files like these (with different numbers)

System.map-2.6.37.6-0.9-desktop
config-2.6.37.6-0.9-desktop
initrd-2.6.37.6-0.9-desktop
vmlinuz-2.6.37.6-0.9-desktop

and, they you renamed those files like those ending with -default to now
end with -desktop, right??

if so: congratulations: you are very lucky your machine will boot at all…

and may get the award for the machine with the most screwed up /boot
which still does…

>
> 8. I reboot the machine and allow option “A” the copied -Default
> profile now named -Desktop to load. Everything goes as expected and I
> have a working desktop again WITH the NVidia drivers that I loaded
> instead of the nouveau drivers.

another amazing feat!!

>
> 9. I do some searching on line and try to find a good explanation of
> what the difference is between the two boot load profiles. All I can
> find is that -Default

those are not “load profiles”! you have two kernels installed one named
Desktop and one named Default

the vmlinuz-2.6.37.6-0.9-desktop (with different numbers) you deleted
was not a profile but was a kernel…

it is the basic ‘thing’ that is Linux…the heart of the system…

then you took a different kernel named (like)
vmlinuz-2.6.37.6-0.9-default and renamed it to vmlinuz-2.6.37.6-0.9-desktop

> 10. This was my original question " I need to change some settings in
> the “A” -Desktop boot load profile to be optimized for daily activity "

no you do not…you need instead to go back to where the trouble first
started and follow some ‘rules’

  1. if using Red Hat 9, look for Red Hat 9 answers (and etc!)

  2. if it ain’t broke, don’t fix it (unless you are capable of and
    willing to fix it yourself)

  3. if you do not know what you are doing do NOT fiddle with it until
    after you have followed Rule One and learned what to do…AND asked
    questions here if you need to

  4. if everything is going ok and you read on some web site somewhere
    that your system possibly needs upgrading: follow Rule Two. (on the
    other hand if an openSUSE website, or openSUSE application recommends an
    upgrade the follow Rule One and Three)

  5. but if everything is NOT going ok and some web site says your system
    possibly needs upgrading, follow Rule One and Three

  6. if after following Rules One, Two, Three and Four you change
    something (like install a new video driver) and the system is broken
    then undo what you did (replace the nvidia driver with the previous
    working nouveau driver)…that is do NOT leave the non-working driver in
    the system and ignore Rule Three and start deleting and renaming
    files…and then ask what to do.

> 11. <snip>
> However, I’m not one to just sit and wait for others to solve my
> problems for me, so I continue to try and try again to attempt to solve
> the issue myself while waiting for someone FAR MORE knowledgeable than I
> to lend a bit of wisdom.

ok, i DO understand that attitude and i acknowledge that it ain’t a bad
way to learn a lot…and it IS your machine…you are most welcome to
delete and rename files all day long, as long as you wish…no problem
with me…

but, if you break it, you need to fix it…

so, here is the wisdom based on my experience and knowledge: read and
follow Rules One through Ten

>
> 12. While waiting for my “ray of sunshine” I figured out the phone and
> the work around for the keyboard for now.

as said, congrats on fixing those…

> However, I’m still very sure
> that the files I deleted in /boot really should be replaced with the
> exact same files. My current kernel number is 12.1 - 3.1.9 - 1.4.
>
> I hope this step by step explains things a little bit better. Sorry for
> any confusion.

yes it does, but truth is i’m not sure how to get from ‘here’ back to
‘where you should be’…

because as far as i can see you are now operating with a default kernel
renamed desktop…the original (actual) desktop kernel having not
worked with the nvidia driver–but seems to be working fine with the
default driver (renamed to desktop)–and, i don’t know how to explain
that because if the nvidia driver wouldn’t work with the original
desktop kernel it should not work with the default kernel renamed desktop…

see?

try this: put this in a user terminal and copy paste the results back to
here between code tags (if you don’t know what a “user terminal” is or
how to open one, see Rule Three…if you don’t know what “between code
tags” means see http://goo.gl/i3wnr

while you are off digesting the above, and doing the copy paste i’m
gonna try to figure out how to get you back to the correct kernel, and a
video driver which works with it…

OH: Rule Eleven is: Read and understand the caveat in my sig before
following any of my advice.


DD http://tinyurl.com/DD-Caveat
What does DistroWatch write about YOU?: http://tinyurl.com/SUSEonDW

On 2012-02-27 06:16, roguehorse wrote:

> Using “sysinfo” I find that the driver listed there as being used is
> called “nouveau” where I would expect NVidia and some release number. I
> search online again and find instructions to replace the nouveau driver

Link to those instructions, pl?

> 6. In Boot Loader I copy all the data for -Default and place them into
> the -Desktop boot load profile. From my understanding, I am making a
> copy of the -Default boot load profile and renaming it -Desktop. Now, in
> case I get this problem again, I still have a fall back to go to that is
> easier to use than failsafe mode. I also understand that using either
> boot load profile is going to utilize the same set of files in the /boot
> file. So I need to copy these files as well and rename them.

Those are not profiles, the are the orders on how to load the kernel on
boot, and are dangerous to touch if you do not know what they are.

> 7. Still working in the “C” option profile (openSUSE -Default), I log
> in to Dolphin as root and go to the /boot folder. I delete all files
> with the -Desktop in the file name. I then copy all similar files with
> -Default in the file name and rename them changing -Default in the file
> name to -Desktop. Now I understand that I have only copied and renamed
> files and not re-configured them to be exact as the original files.
> Still make sense?

Argh!!!

I’m very surprised that your machine still boots. And don’t ask me how to
recover from that mess…


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

Guys,

I’m really sorry this is causing so much frustration. Lets just leave it at the machine is working just fine, it’s not worth fretting over. Worst case scenario is I can do a fresh install and plug in my software xml file to put it back together. What’s 15 min and a clean system?

This link is a similar set of instructions as what I followed, however, this is not the same page. 15. Graphics Drivers - Install Nvidia or ATI/AMD 3D Driver

If you care to see the write up with screenshots of what I did, you can go here How - To: Open Graphics Drivers

I’m actually intrigued that you both seem surprised that the system still boots. It was a very simple procedure and I didn’t do any black magic or anything. I think I’ll just load 12.1 fresh into a VirtualBox and do a comparative look myself.

I really appreciate you guys trying to help though.

Thank you!

On 2012-02-28 02:46, roguehorse wrote:

> I’m actually intrigued that you both seem surprised that the system
> still boots. It was a very simple procedure and I didn’t do any black
> magic or anything. I think I’ll just load 12.1 fresh into a VirtualBox
> and do a comparative look myself.

You renamed kernel image files, and you are surprised it works? :-o


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

I believe what you meant to say is that I’m “NOT” surprised that it works. It was a simple concept of duplication, nothing more or less.

What I did find out of interest however (after installing in VBox and updating), when I copied out the -Desktop extension files from kernel 3.1.9-1.4 on the fresh system and compared them to my original system are the differences in numbers of lines.

new system: -Desktop config txt file contains 5846 lines
original system: -Default config txt contains 5843 lines

new system: -Desktop system.map txt file contains 61802 lines
original system: -Default system.map txt file contains 59189 lines

so the question here is why the are the files not the same in length when they are the same kernel number? If it is a matter of the kernel is updated via updates and upgrades yet carries the same kernel number then we get back to the original question of what is the difference between -Default and -Desktop when both carry the same kernel number?

On 2012-02-28 09:46, roguehorse wrote:
>
> I believe what you meant to say is that I’m “NOT” surprised that it
> works. It was a simple concept of duplication, nothing more or less.

No, I’m very surprised.

> What I did find out of interest however (after installing in VBox and
> updating), when I copied out the -Desktop extension files from kernel
> 3.1.9-1.4 on the fresh system and compared them to my original system
> are the differences in numbers of lines.
>
> new system: -Desktop config txt file contains 5846 lines
> original system: -Default config txt contains 5843 lines

They are not text files, they are binaries, program code! You can not
compare number of lines, there is no such thing.

You are very much mistaken.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

The fresh new “binaries” or “code” for sysctl.conf-3.1.9-1.4 -desktop are:

new

Generated file - do not edit.

Disable the hung task timer by default. (bnc#552820)

kernel.hung_task_timeout = 0

Increase defaults for IPC (bnc#146656)

kernel.msgmax = 65536
kernel.msgmnb = 65536
kernel.sem = 250 256000 32 1024

Increase defaults for IPC (bnc#146656) (64-bit, 4k pages)

kernel.shmmax = 0xffffffffffffffff

SHMALL = SHMMAX/PAGE_SIZE*(SHMMNI/16)

kernel.shmall = 0x0fffffffffffff00

The desktop workload is sensitive to latency, so start writeout earlier

(bnc#552883)

sys.vm.dirty_ratio=20

The currently in use “binaries” or “code” for sysctl.conf-3.1.9-1.4 -desktop are:

using

Generated file - do not edit.

Disable the hung task timer by default. (bnc#552820)

kernel.hung_task_timeout = 0

Increase defaults for IPC (bnc#146656)

kernel.msgmax = 65536
kernel.msgmnb = 65536
kernel.sem = 250 256000 32 1024

Increase defaults for IPC (bnc#146656) (64-bit, 4k pages)

kernel.shmmax = 0xffffffffffffffff

SHMALL = SHMMAX/PAGE_SIZE*(SHMMNI/16)

kernel.shmall = 0x0fffffffffffff00

The “code” in red is not in the “code” I’m running. Why and what is it’s relevance?

To add to the previous statement are the differences between config-3.1.9-1.4 -desktop “code”

A section of the newer “code”

New

RCU Subsystem

CONFIG_TREE_PREEMPT_RCU=y
CONFIG_PREEMPT_RCU=y

CONFIG_RCU_TRACE is not set

CONFIG_RCU_FANOUT=64

CONFIG_RCU_FANOUT_EXACT is not set

CONFIG_TREE_RCU_TRACE is not set

CONFIG_RCU_BOOST=y
CONFIG_RCU_BOOST_PRIO=1
CONFIG_RCU_BOOST_DELAY=500
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=18
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
CONFIG_CGROUPS=y

CONFIG_CGROUP_DEBUG is not set

The same section from the “code” in current use:

current

RCU Subsystem

CONFIG_TREE_RCU=y

CONFIG_PREEMPT_RCU is not set

CONFIG_RCU_TRACE is not set

CONFIG_RCU_FANOUT=64

CONFIG_RCU_FANOUT_EXACT is not set

CONFIG_RCU_FAST_NO_HZ=y

CONFIG_TREE_RCU_TRACE is not set

CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=18
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
CONFIG_CGROUPS=y

CONFIG_CGROUP_DEBUG is not set

The differences are obvious. Which goes ALL THE WAY BACK to the original question. What are the differences in the “code”? Or as it seems the differences could be indefinite based on the continual changes of each individuals system and their use and maintenance of that system? Thus, as noticing the obvious differences between 3.1.9-1.4 -desktop and 3.1.9-1.4 -default the next logical step is to compare the newly installed 3.1.9-1.4 -default to the currently running 3.1.9-1.4 -default. The only problem here lies in the fact that the fresh system does not have a 3.1.9-1.4 -default to boot to?

On Wed, 29 Feb 2012 03:06:03 +0000, roguehorse wrote:

> The fresh new “binaries” or “code” for sysctl.conf-3.1.9-1.4 -desktop
> are:

That’s not what changed. You need to install the Desktop kernel package
again.

Messing around with config files for a kernel compilation isn’t going to
get you where you need to be.

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

On 2012-02-29 04:06, roguehorse wrote:
>
> The fresh new “binaries” or “code” for sysctl.conf-3.1.9-1.4 -desktop
> are:

You are altering that file only? That does nothing.

I understood you were talking of “vmlinuz-3.1.9-1.4-desktop”.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

On 2012-02-29 05:06, roguehorse wrote:
>
> To add to the previous statement are the differences between
> config-3.1.9-1.4 -desktop “code”

That file only contain a list of what was done when the kernel was
compiled, it is not the kernel. Changing that file does nothing, you have
to compile it again changing the values in the proper place. And i don’t
recommend it.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

OK,

Well it’s May now and the system is still running like clockwork so I’m not inclined to do much more on this. However, I have received many NVidia driver updates over the last few months and all is still good as far as the original changes in graphics drivers. We’ll see how things go when I do my next system upgrade.