Hello Michael,
Am 1/12/2013 1:24 PM, Michael Tokarev wrote:
Peter, are you able to run git bisect or something like that, to try to
pinpoint either the commit which introduced this issue or which fixed
it?
Well, i'm no expert at git, but i made some progress, see below.
Besides, what are
Hi,
well - it's probably only for historic interest, but if i made no bisecting
mistake, this commit has fixed it (note that
the meaning of 'good' and 'bad' is swapped due to how git bisect works):
root@debian:~/qemu_git/qemu-kvm# git bisect good
Bisecting: 87 revisions left to test after this
Hello Michael,
Am 1/12/2013 1:24 PM, Michael Tokarev wrote:
Peter, are you able to run git bisect or something like that, to try to
pinpoint either the commit which introduced this issue or which fixed
it?
Well, i'm no expert at git, but i made some progress, see below.
Besides, what are
Hi,
well - it's probably only for historic interest, but if i made no bisecting
mistake, this commit has fixed it (note that
the meaning of 'good' and 'bad' is swapped due to how git bisect works):
root@debian:~/qemu_git/qemu-kvm# git bisect good
Bisecting: 87 revisions left to test after this
Hi again!
The good news: 1.3.0 works (at least with my setup). The bad news is
that this might lower the motivation to fix 1.1.2 ;-) ...
Attached is the USB trace file from the non-working case with V 1.1.2.
If decompressed, it's an 185 MB text file and - honestly - i cannot make
any sense of
Hi again!
The good news: 1.3.0 works (at least with my setup). The bad news is
that this might lower the motivation to fix 1.1.2 ;-) ...
Attached is the USB trace file from the non-working case with V 1.1.2.
If decompressed, it's an 185 MB text file and - honestly - i cannot make
any sense of
Am 1/8/2013 6:08 PM, Serge Hallyn wrote:
(replying to comment #12) could you please follow up on comments #6 and
#7?
It also would be worthwhile, at this point, checking whether latest
upstream (1.3) is still broken.
Just a short note: I somehow produced a backported *.deb for 1.3.0 and
i
Am 1/8/2013 6:08 PM, Serge Hallyn wrote:
(replying to comment #12) could you please follow up on comments #6 and
#7?
It also would be worthwhile, at this point, checking whether latest
upstream (1.3) is still broken.
Just a short note: I somehow produced a backported *.deb for 1.3.0 and
i
Just confirming the bug. I'm having the same issues with the same USB
smart card reader as the submitter (Kobil mIDentity) on Debian Squeeze
using the qemu-kvm version 1.2.0 from debian-backports. Going back to
1.0 fixes the problem (http://snapshot.debian.org/package/qemu-
Referring to my last comment: The URL does only work if you add a
backslash at the end, sorry about that.
One last note: In Germany, the Kobil USB Reader is/was supplied by DATEV
(see http://www.datev.com/) to their members/partners. So, anybody who's
running DATEV software on kvm-virtualized
Just confirming the bug. I'm having the same issues with the same USB
smart card reader as the submitter (Kobil mIDentity) on Debian Squeeze
using the qemu-kvm version 1.2.0 from debian-backports. Going back to
1.0 fixes the problem (http://snapshot.debian.org/package/qemu-
Referring to my last comment: The URL does only work if you add a
backslash at the end, sorry about that.
One last note: In Germany, the Kobil USB Reader is/was supplied by DATEV
(see http://www.datev.com/) to their members/partners. So, anybody who's
running DATEV software on kvm-virtualized
Just tested rhythmbox from lucid-proposed. Well, rhythmbox still doesn't
honour my playlist_format=audio/x-mpegurl line in the .is_audio_player
file and keeps creating *.pls instead *.m3u playlists, but:
The crasher is gone. Verified fixed.
However, dropping files directly from playlists or the
Public bug reported:
Binary package hint: rhythmbox
Steps to reproduce:
1) Insert a SD-memory card containing the magic file .is_audio_player
into the pc's card reader.
2) Wait till the removable device comes up in rhythmbox.
3) Create a playlist on the device.
4) Drag-and-drop an entry from
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/44912943/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/44912944/Disassembly.txt
** Attachment added: GConfNonDefault.txt
http://launchpadlibrarian.net/44912945/GConfNonDefault.txt
Seeing this still on Karmic Beta:
Linux version 2.6.31-11-generic (bui...@yellow) (gcc version 4.4.1 (Ubuntu
4.4.1-4ubuntu4) ) #38-Ubuntu SMP Fri Oct 2 11:06:40 UTC 2009
It's a 1TB Toshiba USB drive and it also needs the afm. max_sectors
trick. However, i'm under the expression that the drive
Bug seems to be fixed in Jaunty and can be closed.
--
Nokia 6233 usb-storage won't work
https://bugs.launchpad.net/bugs/222153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
One last feedback from me: At least on my motherboard (Asrock
A770Crossfire) the reason for the missing _PSS tables is solved:
The BIOS disables C'n'Q *silently* (even when the setting is set to
Enabled) if memory modules from a certain vendor are used. In my case
it were those:
A-Data
Well, i've entered the following bug in the kernel bug tracker:
http://bugzilla.kernel.org/show_bug.cgi?id=12948
It was confirmed that the Asrock BIOS doesn't contained the required
_PSS tables - which is an error on their part - nothing Linux can do
about. The _PSS tables are needed for
I'm seeing the same on Jaunty Kernel version 2.6.28-11-generic since i
swapped my Asus M2A-VM Mobo with an Asrock A770Crossfire Mobo (newest
BIOS P1.20, C'n'Q enabled in the BIOS).
Attaching the output of dmidecode and my dmesg.
** Attachment added: dbg.tgz
And seems we have the same on another Asrock Mobo:
https://bugs.launchpad.net/ubuntu/+bug/347002
--
Error on Boot: [Firmware Bug]:Powernow-k8: Your BIOS does not provide ACPI_PSS
objects in a way that Linux understands.
https://bugs.launchpad.net/bugs/331691
You received this bug notification
Public bug reported:
Binary package hint: linux-image-2.6.24-16-generic
Usb-storage in the Hardy Heron kernel image doesn't work for the Nokia 6233.
This is IMHO a re-apperance of bug #102965.
I tracked down the issue to the following entry in
drivers/usb/storage/unusual_devs.h:
/* Reported by
22 matches
Mail list logo
