Tested (kubuntu) Hardy Alpha 4 - the fix is _not_ included.
Behavior is Identical to Alpha 3 :-(
--
[regression] Kobil card reader doesn't work with Hardy
https://bugs.launchpad.net/bugs/183109
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact f
The first Kubuntu Hardy KDE4 Alpha
(https://wiki.kubuntu.org/HardyHeron/Alpha5/KubuntuKDE4) comes with a
completely new displayconfig module that indeed uses XRandR.
It is not fully operational yet (settings cannot be changed), but this looks
like the right approach.
Hopefully someone will backp
http://bryceharrington.org/drupal/display-config-1 describes the recent
progress of the Ubuntu display configuration.
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notification because you are a member of Kubuntu
Team, which is s
No progress with Kubuntu Hardy Alpha 6 - still the same error. Strange
that such a higly visible malfunction is not getting more attention...
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notification because you are a member of
If a re-write for Hardy is no option and the module is broken by design,
what can we do?
a) Remove it entirely and let the user deal with command-line xrandr
If "fixup" allows to port/backport
b) Backport the one from Kubuntu-Hardy-KDE4 that is prepared for XRandR
c) Port the one from Ubuntu Har
Same problem here (T23 with SuperSavage IX/C SDR) - I'm able to recover
by closing and re-opening the lid again after resume - seems to be just
an issue with screen switching. I also recognize that Fn-F7 does not
work with Gutsy while it worked with Feisty. In Feisty I sometimes had
to press Fn-F7
** Attachment added: "Difference between the (working) patched Gutsy driver and
the current Hardy code"
http://launchpadlibrarian.net/11347369/kobil_c_2.6.24-diff
--
[regression] Kobil card reader doesn't work with Hardy
https://bugs.launchpad.net/bugs/183109
You received this bug notificati
** Attachment added: "lsusb -v output"
http://launchpadlibrarian.net/11347365/lsusb.log
--
[regression] Kobil card reader doesn't work with Hardy
https://bugs.launchpad.net/bugs/183109
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubu
Public bug reported:
The USB-attached Kobil Kaan Standard Plus cardreader that worked with all
pre-Gusty releases does no longer work with Hardy - tested with Alpha 3. Note
that it only worked on Gutsy with a patch - for details see #128228.
With Hardy Alpha 3, the driver does not load with the
** Attachment added: "dmesg output"
http://launchpadlibrarian.net/11347359/dmesg-hardy.log
--
[regression] Kobil card reader doesn't work with Hardy
https://bugs.launchpad.net/bugs/183109
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Attachment added: "uname -a output"
http://launchpadlibrarian.net/11347362/uname.log
--
[regression] Kobil card reader doesn't work with Hardy
https://bugs.launchpad.net/bugs/183109
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubu
** Attachment added: "lspci -vvnn output"
http://launchpadlibrarian.net/11347363/lspci-vvnn.log
--
[regression] Kobil card reader doesn't work with Hardy
https://bugs.launchpad.net/bugs/183109
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
I was very disappoionted with the last kernel update (2.6.22-14.47) because it
did not include the fix for the broken driver.
The current driver is unusable, the fix is available - what's going wrong here?
--
[regression] Kobil card reader don't work with 2.6.22-x (now with a patch)
https://bugs
Erik,
I attached the patch that I backported from 2.6.24-rc1 to the current 2.6.22-14
gutsy kernel to my post
(https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/128228/comments/6)
above.
Applying that patch (http://launchpadlibrarian.net/10175748/kobil_sct.patch) to
the curren
There was never a question that the driver would work with hardy - as I
mentioned above, the driver _is_ going to be fixed for 2.6.24. The point is
that I'm missing the fix as part of a _gutsy_ kernel update.
The gutsy kernel introduced the regression and again, the driver was working
with feist
Ben, thanks for your investigations. I actually see one more functional
difference, the new code added setting the speed variable within the
baud rate case statement in kobil_set_termios().
- case 9600:
default:
+ speed = 9600;
+ ca
Forget my previous post, I overlooked that the speed variable is set by the
tty_get_baud_rate() function.
However, I was able to set up a build system with the Hardy live CD to test
commenting out the lines as recommended by Ben above. That _did not_ change
anything - still getting the error.
Wh
Debug level log on the same system using Gutsy:
Jan 24 08:59:57 localhost kernel: [ 583.811810]
/build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/usb-serial.c: USB
Serial support registered for KOBILUSB smart card terminal
Jan 24 08:59:57 localhost kernel: [ 583.812179
Stefan, that did the trick!
Jan 24 20:26:13 ubuntu kernel: [ 795.453861] usbcore: registered new interface
driver usbserial_generic
Jan 24 20:26:13 ubuntu kernel: [ 795.453866]
/build/buildd/linux-2.6.24/drivers/usb/serial/usb-serial.c: USB Serial Driver
core
Jan 24 20:26:30 ubuntu kernel: [
Just tested Stefan's patch with a high-level application (Moneyplex
2004) - works fine! I hope the patch will still make it into Hardy Alpha
4!
--
[regression] Kobil card reader doesn't work with Hardy
https://bugs.launchpad.net/bugs/183109
You received this bug notification because you are a mem
Problem is still present with Kubuntu Hardy Alpha 5 (i386, liveCD).
Installing python-dev as suggested in a related thread did not help.
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notification because you are a member of Ubunt
Looks like the root cause is the integration of the new 1.4.0 X server. This
server does no longer require a ServerLayout section in xorg.conf - see that
attached xorg.conf for the Alpha 5 live CD.
When starting displayconfig, the code calls
/var/lib/python-support/python2.5/displayconfigabstrac
Looks like the smart way would be to use XRandR
(http://www.x.org/wiki/Projects/XRandR) as the preferred way to set screen
size, orientation and/or reflection of the outputs for a screen for modern X
servers.
Maybe some URandR (http://www.x.org/wiki/Projects/XRandR) or Python-XRandR
(https://c
23 matches
Mail list logo
