Longtime Fedora user going rawhide (i915.modeset, keyboard layouts, xorg.conf/synaptics, bluetooth)

MartinG gronslet at gmail.com
Mon Sep 22 11:53:04 UTC 2008


Hi list, this is my first post here.

Having used (stable) Fedora since the very beginning, and also the
testing branch for some months now, I decided to go rawhide.
My setup is a pure install of Fedora 9 from the live-kde image (using
crypted partitions), later updated by "yum --enablerepo=rawhide update".

I have a Dell Latitude X1 (Intel mobile 915GM/GMS/910GML graphics
card, synaptics touchpad, smolt profile in [1])

I am a KDE 4 user, and I have searched this list [2].

Now for the questions:

1. The modesetting driver for the intel card doesn't seem to be
included in the latest kernel (2.6.27-0.329.rc6.git2.fc10.i686) --
adding "i915.modeset=1" as a kernel parameter in /etc/grub.conf gives
an error "unknown boot option, ignoring". This is also mentioned by
Rex Dieter in airlied's blog [3]. Also, if I try to boot with that
option, I am able to log in to X, but then X freezes and fills my
/var/log/Xorg.0.log with *many* lines like

...
exaCopyDirty: Pending damage region empty!
[mi] EQ overflowing. The server is probably stuck in an infinite loop.
[mi] mieqEnequeue: out-of-order valuator event; dropping.
[mi] EQ overflowing. The server is probably stuck in an infinite loop.
[mi] mieqEnequeue: out-of-order valuator event; dropping.
...

Is there any plan to include the modesetting driver for intel again?
Should I file a bug, if so -- where (what product)?


2. Bluetooth. I used bluetooth with "great" success in F9 testing, but
in rawhide the service doesn't seem to start: Doing "service bluetooth
restart" gives neither "[  OK  ]" nor "[FAIL]". But, hm, just now, I
started "bluetoothd" manually, and was able to do a "hcitool scan" and
find my phone. The "kdebluetooth" tray icon is still reporting "No
bluetooth adapter", though. The update to rawhide also removed
/etc/bluetooth/hcid.conf and left /etc/sysconfig/bluetooth with all
lines commented out (not sure what I had before).

I know bluetooth support in KDE 4 is a bit broken at the moment, but I
just wanted to report on the possible issue in the bluetooth rc
scripts.

3. What is the grand plan for configuration replacement for the
xorg.conf file? I've read that eg. options for the synaptics touchpad
driver can be put in /etc/hal/fdi/policy/10-synaptics.fdi, and I have
fiddled a bit around with it. Are we all supposed to hardcode xml
files now, or are all windows managers meant to provide GUIs for
these? (not a rant, just an honest question)

4. Possibly related to the non-existent xorg.conf file, I had some
serious issues with the keyboard when enabling keyboard layouts in KDE
systemsettings. Specifically, some keys where mapped wrong, some
didn't work at all (eg. the arrow keys). Disabling keyboard layouts in
KDE 4, and restarting X "solves" the problem, but how do I enable the
"nodeadkeys" variant of my Norwegian keyboard? Making a .fdi file? Any
hints appreciated.

Thanks for all the great work so far, I hope I can contribute by
sending in bug reports. Any feedback appreciated.

-MartinG

[1] http://www.smolts.org/client/show/pub_01507560-2bed-4c14-94a5-c72964bb4b84
[2] http://search.gmane.org/?query=stuff&author=&group=gmane.linux.redhat.fedora.testers
[3] http://airlied.livejournal.com/58778.html?thread=240794#t240794




More information about the fedora-test-list mailing list