ok, let do it according with your preferences. However I find better to have the whole rules.d folder. I gave you the download link and you can start the iso with the vmplayer or simply mount the iso with acetoneiso2.
71-seat.rules
This file is part of systemd.
systemd is free software; you can redistribute it and/or modify it
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation; either version 2.1 of the License, or
(at your option) any later version.
ACTION==“remove”, GOTO=“seat_end”
TAG==“uaccess”, SUBSYSTEM!=“sound”, TAG+=“seat”
SUBSYSTEM==“sound”, KERNEL==“card*”, TAG+=“seat”
SUBSYSTEM==“input”, KERNEL==“input*”, TAG+=“seat”
SUBSYSTEM==“graphics”, KERNEL==“fb[0-9]*”, TAG+=“seat”
SUBSYSTEM==“usb”, ATTR{bDeviceClass}==“09”, TAG+=“seat”
‘Plugable’ USB hub, sound, network, graphics adapter
SUBSYSTEM==“usb”, ATTR{idVendor}==“2230”, ATTR{idProduct}==“000[13]”, ENV{ID_AUTOSEAT}=“1”
Mimo 720, with integrated USB hub, displaylink graphics, and e2i
touchscreen. This device carries no proper VID/PID in the USB hub,
but it does carry good ID data in the graphics component, hence we
check it from the parent. There’s a bit of a race here however,
given that the child devices might not exist yet at the time this
rule is executed. To work around this we’ll trigger the parent from
the child if we notice that the parent wasn’t recognized yet.
Match parent
SUBSYSTEM==“usb”, ATTR{idVendor}==“058f”, ATTR{idProduct}==“6254”,
ATTR{%k.2/idVendor}==“17e9”, ATTR{%k.2/idProduct}==“401a”, ATTR{%k.2/product}==“mimo inc”,
ENV{ID_AUTOSEAT}=“1”, ENV{ID_AVOID_LOOP}=“1”
Match child, look for parent’s ID_AVOID_LOOP
SUBSYSTEM==“usb”, ATTR{idVendor}==“17e9”, ATTR{idProduct}==“401a”, ATTR{product}==“mimo inc”,
ATTR{…/idVendor}==“058f”, ATTR{…/idProduct}==“6254”,
IMPORT{parent}=“ID_AVOID_LOOP”
Match child, retrigger parent
SUBSYSTEM==“usb”, ATTR{idVendor}==“17e9”, ATTR{idProduct}==“401a”, ATTR{product}==“mimo inc”,
ATTR{…/idVendor}==“058f”, ATTR{…/idProduct}==“6254”,
ENV{ID_AVOID_LOOP}=="",
RUN+="/sbin/udevadm trigger --parent-match=%p/…"
TAG==“seat”, ENV{ID_PATH}=="", IMPORT{builtin}=“path_id”
TAG==“seat”, ENV{ID_FOR_SEAT}=="", ENV{ID_PATH_TAG}!="", ENV{ID_FOR_SEAT}="$env{SUBSYSTEM}-$env{ID_PATH_TAG}"
SUBSYSTEM==“input”, ATTR{name}==“Wiebetech LLC Wiebetech”, RUN+="/bin/loginctl lock-sessions"
LABEL=“seat_end”
73.seat-late.rules
This file is part of systemd.
systemd is free software; you can redistribute it and/or modify it
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation; either version 2.1 of the License, or
(at your option) any later version.
ACTION==“remove”, GOTO=“seat_late_end”
ENV{ID_SEAT}=="", ENV{ID_AUTOSEAT}==“1”, ENV{ID_FOR_SEAT}!="", ENV{ID_SEAT}=“seat-$env{ID_FOR_SEAT}”
ENV{ID_SEAT}=="", IMPORT{parent}=“ID_SEAT”
ENV{ID_SEAT}!="", TAG+="$env{ID_SEAT}"
TAG==“uaccess”, ENV{MAJOR}!="", RUN{builtin}+=“uaccess”
LABEL=“seat_late_end”
And now:
finally I installed also all the bluetooth files:
97-bluetooth-hid2hci.rules
97-bluetooth-serial.rules
97-bluetooth.rules
Like I wrote, I got consequently a well working bluetooth system, with working device discovery, what fixes exactely the diNovo keyboard bug and much more. BUT!!!:
later I pressed by mistake th standby button and what a catastrophe by restoring. nothing more works and everything must be resetted-rebooted-reconfigured, assuming that then it will work again. opensuse shows an absolute leak of robustness concerning autentification, possibly attempting to repair bugs with a too liberal use of password requests, see what they did with wireless. for this reason I renonced to get the bluetooth working, being content just with a working dinovo keyboard.
better injured as dead.
i am also working here for evrybody, but as old suse user I don’t belive the team will fix such bugs. if you are lucky they will put in the code a remark concerning the next distribution (don’t worry, the team is not erloud to read posts :)).
the best kind of help is to make finally a couple of well structured posts, they will be well visible in google, what I find relevant because our issues concern at least also all xbuntu distros. if ubuntu will fix a bug also opensuse will do that. they call that “mainstream”.
right now, let go ahead and use for some time the fixed system. have you a better idea?
the only option: delete the installation and goodbye opensuse 12.2