Am 03.06.2011 15:54, schrieb Felix Miata:
> On 2011/06/03 12:25 (GMT+0200) walter harms composed:
> 
>> i did an update to 11.4 [from 11.2] and got some strange trouble.
> 
>> the default kernel did not generate a useable system, since i had no
>> keybord etc. (under investigation)
> 
>> the desktop failsafe worked.
>> I got the desktop version working with acpi=on since the i915.ko did
>> not load without (bug ?).
> 
>> Now i am stuck with KDE. It is to smart for its own good.
>> It tries to change the GFX config and gets it wrong.
>> Changing the WM "solves" the problem but that is not what i want.
> 
>> Anyone an idea where to find the kde config data that sets the display ?
> 
> KDE isn't designed for configuring X, only limited tweaking. You could
> try YaST2 in one of the other WMs, or just boot the default kernel to
> runlevel 3, login as root, 'cd /etc/X11', 'mv xorg.conf xorg.conf-112',
> 'init 5', and see if auto config X gets you what you need.

The problem with the "default" OS11.4 is more general. I have no clue
what it may be but the kdb (USB) is not functioning, gfx is not fount etc.
I suspect it may be a problem with the modules setup, as i see much less
modules in the /lib/modules/"default" tree than in the desktop tree.

> 
> Keyboard and mouse drivers in 11.4 are different from those in 11.2, and
> your xorg.conf is probably setting use of uninstalled drivers. I don't
> know why other WMs might still work.
> 

When i go to runlevel 5 the display manager works fine, starting a kde
session causes ghost mirror images, making the system unusabele, stopping
kde resets the Gfx into a usable state. Replacing KDE with fvwm2 .. everything 
is
fine. There are no special setups for KDE of what so ever involved. even 
removing
.kde* does not help.

> Which Intel gfx chip do you have (clue: lspci)?

i915, driver is found but requieres acpi to work (took me by surprise)

I am totaly stuck where KDE stores that type of configs.

re,
 wh

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to