Login configure problem, perhaps?

[wedgetail]

as
Thanks you have given me a lead to think broader.  I will be happy for hours.
I just went to the C-Programming KDE-mini and checked, there is a kderc, so I should have had one I think.   

[Old-Polack]

as
Thanks you have given me a lead to think broader.  I will be happy for hours.
I just went to the C-Programming KDE-mini and checked, there is a kderc, so I should have had one I think.   

Did you try copying it to the system that does not have one?

[wedgetail]

old-polack
Yes, having looked at the 'new KDE-mini' kdedrc  file I thought it was not too intimidating. Thought I recognised half the items so I copied it to the old system.

I am in the process of doing the binary cut on the file, think I have two keyboard items left. The systems fail/hangs just after the login and the hard drive picture shows up. I loose my patience after 30 seconds and at the moement go for alt-F2 to get a terminal.  Trying to avoid a complete restart.  Actually this time I came in via failsafe, but startx crashes.  I can't quite see the connection as I thought I had X running when "tools" wonder across the screen.  

Here I get stuck trying run "Video" or "drakfx" just an interesting little side track.  

Have logged onto forum via another system to search.

Turns out it is XFdrake that is needed after logging on via a text terminal. Funny that I think it was the same last time I had to go through this exercise.  

I started up using Vesa, and I have just reset to my normal Nvidia 9600.  I have also checked with only one item in the kdedrc it seems my system has an aversion for the kdedrc.

When I did the recommend re-start to get Vesa "embedded" the system hung with the one item in the kdedrc  so I deleted the file (using the new bare bones KDE-mini) and I have actually re-started normally with the Vesa setting, first re-start with successful login after the use of XFdrake. What do you know absolutely no crash messages.   but  

Now I will re-start again with the correct Nvidia settings.

[wedgetail]

Nvidia--??
When starting up with the Nvidia settings the problem is back.  Two crash files kded and kmcinit
The crash reports a very similar to the very first ones I got.

Edit:
Removed a number of commit logs, I think this is unnedded

Then got interested in the nvidia settings when I ran this from menu, merry dance in panel but nothing??

Had trouble trying to find the command line statement for nvidia settings, via edit menu route. Something about khotkey, when acknowledging message I got the command line statement:

[gert@localhost config]$ /usr/bin/nvidia-settings
Segmentation fault
[gert@localhost config]$

Remembering that vesa driver seemed OK, I installed nouvo driver, for something different, and crash messages gone, but much worth when I tried to run nvidia settings from command line, I was informed that "two partitions were located, which one was to be formatted ??". Well I was no longer half asleep at that stage.  

There is a degree of exitement sometimes when working Linux    I decided it was time to look closer at the nvidia.  I have had a good run but remember several nvidia problem posts, so I have done a bit of searching and I think there is something going on here.

01:00.0 VGA compatible controller: nVidia Corporation G94 [GeForce 9600 GT] (rev a1)


[root@localhost gert]# lspci -v -s 01:00.0
01:00.0 VGA compatible controller: nVidia Corporation G94 [GeForce 9600 GT] (rev a1) (prog-if 00 [VGA controller])
        Subsystem: Elitegroup Computer Systems Device 10a9
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Memory at fa000000 (64-bit, non-prefetchable) [size=32M]
        I/O ports at dc00 [size=128]
        Expansion ROM at fe880000 [disabled] [size=512K]
        Capabilities: [60] Power Management version 3
        Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [78] Express Endpoint, MSI 00
        Capabilities: [b4] Vendor Specific Information: Len=14 <?>
        Capabilities: [100] Virtual Channel
        Capabilities: [128] Power Budgeting <?>
        Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
       Kernel driver in use: nouveau
        Kernel modules: nvidiafb, nvidia96xx, nvidia-current, nvidia173, nouveau

[root@localhost gert]#

When running nuoveau I got this.  Some education for me please.  The result marked in red above, does that mean kernel now has nuoveau compiled in and in addition another five modules installed?? (Getting a bit crowded??)

I seem to have lost my lsmod |grep nvid associated with above, it revealed that there was nothing nvidia so I am assuming that only nouvea available.

Having met the question about formatting partitions while working with display, I felt a bit uncomfortable and decided to install the nvidia via pcc again, followed by re-start and obligatory two crash messages.  

Nvidia 9600 closer look
Uses the nvidia 6100 to GT xxxx in pcc.

[root@localhost gert]# lspci -nnv -s 01:00.0
01:00.0 VGA compatible controller [0300]: nVidia Corporation G94 [GeForce 9600 GT] [10de:0622] (rev a1) (prog-if 00 [VGA controller])
        Subsystem: Elitegroup Computer Systems Device [1019:10a9]
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Memory at fa000000 (64-bit, non-prefetchable) [size=32M]
        I/O ports at dc00 [size=128]
        [virtual] Expansion ROM at fe880000 [disabled] [size=512K]
        Capabilities: [60] Power Management version 3
        Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [78] Express Endpoint, MSI 00
        Capabilities: [b4] Vendor Specific Information: Len=14 <?>
        Capabilities: [100] Virtual Channel
        Capabilities: [128] Power Budgeting <?>
        Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
       Kernel driver in use: nvidia
        Kernel modules: nvidiafb, nvidia96xx, nvidia-current, nvidia173, nouveau

[root@localhost gert]#

Any nvidia modules installed?

[root@localhost gert]# lsmod |grep nvid
nvidia              10736981  40
i2c_core               16500  11 nvidia,tda1004x,saa7134_dvb,tuner_simple,tda9887,tda8290,tuner,saa7134,v4l2_common,videodev,tveeprom
[root@localhost gert]#


[root@localhost gert]# lsmod |grep nou
[root@localhost gert]#

The last bit indicates to me that nouveau is not linked to kernel?

Have I got enough nvidia modules installed  


I am just leaving the next two for my own record when I copy the thread

[root@localhost gert]# dmesg |grep nvid
nvidia: module license 'NVIDIA' taints kernel.
nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
nvidia 0000:01:00.0: setting latency timer to 64
nvidia-settings[3113]: segfault at 74f91315 ip 49c68be4 sp bfef5194 error 6 in ld-2.13.so[49c5e000+1a000]
nvidia-settings[3195]: segfault at 750ec315 ip 49c68be4 sp bfe640f4 error 6 in ld-2.13.so[49c5e000+1a000]
[root@localhost gert]#

[root@localhost gert]# dmesg |grep vga
Kernel command line: BOOT_IMAGE=MniMe2010.10 root=LABEL=minime2010 resume=LABEL=swap4000 splash=silent vga=788   console=tty0  console=ttyS0,38400n8 nokmsboot
vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[root@localhost gert]#

I really need some enlightenment on sorting the driver situation out, not sure where to start? I have just kept running the updates and had no problems catching my attention until yesterday approximately

[wedgetail]

Prelink

What does Prelink do?  Could that be a "sleeper" yet to be awakened to a system?  My barrel of ideas have been miserably low, really needing a torch to see if anything was there. When I decided to uninstall prelink.

When I got stuck into the nvidia setup on this system and searched forum I noticed several topics with prelink.  As a last easy item to try before letting go I have uninstalled via Synaptic. Re-started the system, and sat an stared for 58 seconds, waited for the crash messages, then lost my patience and started using the system. They have not arrived yet.   10 minutes later.

Klipper is back in action, it has even saved many of my mouse copy/paste actions. So Klipper seems to have been in a funny mode, perhaps showing a frozen image.


Nvidia settings
Now this also runs perfectly, can be called from menu and will run from command line.

[gert@localhost ~]$ /usr/bin/nvidia-settings
^C
[gert@localhost ~]$

Only a few days ago Baldbrick kindly educated me a bit on the desktop option: Folder View or Desktop View since then I have run in aaahh ummm Desktop, ie I have change over from the previous many month. Prelink gone unhappy?

Now what about the nvidia driver? Do I have a problem? I am taking a brake.