Just to say that it still exists in -22 (but it's quite normal because
it was just a security update).
--
usb devices not recognized automatically when plugged in a hub
https://bugs.launchpad.net/bugs/287576
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I just tried to backport the hub_reset() and persistent_device()
functions from hub.c in 2.6.26, but it didn't help. (So the patch I
attach to this comment DOESN'T WORK).
I guess there are also modifications in the ehci driver but I'm not fit
enought to look in it.
I searched throught the diff fi
Public bug reported:
Binary package hint: linux-image-2.6.24-21-generic
1) Hardy 8.04.1 with hardy-updates
2) linux-image-2.6.24-21-generic: Installed: 2.6.24-21.42
Since the kernel upgrade from 2.6.24-19 to 2.6.24-21, devices plugged in
our internal usbhub are not automatically reconized. Runn
** Attachment added: "dmesg output. No message while plugging in usbdevice in a
hub."
http://launchpadlibrarian.net/18797906/dmesg.log
--
usb devices not recognized automatically when plugged in a hub
https://bugs.launchpad.net/bugs/287576
You received this bug notification because you are a
** Attachment added: "output of uname -a"
http://launchpadlibrarian.net/18797961/uname-a.log
--
usb devices not recognized automatically when plugged in a hub
https://bugs.launchpad.net/bugs/287576
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "output of lspci -vvnn"
http://launchpadlibrarian.net/18798379/lspci-vvnn.log
--
usb devices not recognized automatically when plugged in a hub
https://bugs.launchpad.net/bugs/287576
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Attachment added: "/proc/version_signature"
http://launchpadlibrarian.net/18798371/version.log
--
usb devices not recognized automatically when plugged in a hub
https://bugs.launchpad.net/bugs/287576
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Attachment added: "output of lsusb -v"
http://launchpadlibrarian.net/18798402/lsusb-v.log
--
usb devices not recognized automatically when plugged in a hub
https://bugs.launchpad.net/bugs/287576
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I tried to recompile the kernel and remove the ubuntu modification from
drivers/usb/core/hub.c (see attached patch), and the usb hubs are
working back. I guess the bug is somewhere in this modification.
How I did :
apt-get source linux-image-2.6.24-21-generic
patch -p1 -R < hub.patch
cd linux-2.6
I had a look in hub.c and I propose this patch which works for me. I'm
not quite sure if it has side effects since it's the first time I'm
looking in the usbcore code.
I noticed that when I'm plugging a memory stick in my hub, the hub makes
a soft reset first. I guess it can be one of this "side e
Some infos which could be usefull.
This computer is sold from transtec with a SuSE Enteprise Desktop 10. I
downloaded a trial version to see how the graphic chip worked and I took
some infos.
First of all, it works properly :). 3D works fine.
I made a rpm -qa to get the installed versions of the
I thought it did the same with the newest driver, but it was actually my
xorg.conf which wasn't OK. I just tried with the xorg.conf of comment
#10 and it works better.
For the moment, I don't get any GLX extensions but I hope I can fix it
by myself with a little work.
I attach my Xorg.0.log file
I removed all packages related to nvidia (but I guess just nvidia-glx
was usefull to remove). And I can get some 3D now.
But DRI is not activated using libgl1-mesa-glx and I still didn't found
why. I'll try the diverses variants and if none works, I'll try to
compile the last mesa revision. Is the
I found on this page : http://ubuntuforums.org/showthread.php?t=843052
that I had to remove libglitz1 to get dri activated.
It works now pretty well (enought for the 3D features I needed). I still
have some times problems to switch from X to console (screen stays
black, but Ctrl+Alt+F7 give it bac
I applied the patch on the default 2.2.1 driver and built the package
with it. It works well without the xorg.conf workaround.
I still need the Modeline for my monitor but I have to test further.
It's already an improvement.
--
"Output LVDS is connected to pipe B" on a Mini-PC without LFP
https:
Public bug reported:
Binary package hint: cryptsetup
lsb_release -rd :
Description:Ubuntu 8.04.2
Release:8.04
apt-cache policy cryptsetup :
cryptsetup:
Installed: 2:1.0.5-2ubuntu12
Candidate: 2:1.0.5-2ubuntu12
Version table:
*** 2:1.0.5-2ubuntu12 0
500 http://archive.u
** Attachment added: "Patch to allow cryptsetup to suicide a keyslot"
http://launchpadlibrarian.net/21946428/cryptsetup-hardy-suicide.patch
--
cryptsetup: Cannot delete a Keyslot from itselfs
https://bugs.launchpad.net/bugs/324871
You received this bug notification because you are a member of
I just checked and it was corrected upstream in revision 41 of trunk
http://code.google.com/p/cryptsetup/source/diff?spec=svn47&r=41&format=side&path=/trunk/lib/setup.c&old_path=/trunk/lib/setup.c&old=38
--
cryptsetup: Cannot delete a Keyslot from itselfs
https://bugs.launchpad.net/bugs/324871
Y
** Bug watch added: Debian Bug tracker #513596
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513596
** Also affects: cryptsetup via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513596
Importance: Unknown
Status: Unknown
** Also affects: cryptsetup (Debian) via
http://bug
Still exists in 2.6.24-23.
--
usb devices not recognized automatically when plugged in a hub
https://bugs.launchpad.net/bugs/287576
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
I was working with the workaround "don't update the kernel with any
version > 2.6.24-19" for a while.
I just retested with 2.6.24-24 and 2.6.24-25, and this issue seems to be fixed.
With the 2.6.31 from 9.10 it also works fine.
I checked the linux_2.6.24-25.63.diff.gz (got with apt-get source
li
Public bug reported:
I installed the 10.04 beta1 using PXE network boot from here :
http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-
amd64/beta-1/images/netboot/netboot.tar.gz
If HPET is activated in the BIOS (either 32 bits or 64 bits), the kernel
ouputs a warning at "hpet.c:392".
** Attachment added: "uname -a"
http://launchpadlibrarian.net/42066055/uname-a.log
--
HPET warning on P55 based mainboard (GA-P55A-UD5)
https://bugs.launchpad.net/bugs/548914
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
** Attachment added: "lspci -vnvn"
http://launchpadlibrarian.net/42066139/lspci-vnvn.log
--
HPET warning on P55 based mainboard (GA-P55A-UD5)
https://bugs.launchpad.net/bugs/548914
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "/proc/version_signature"
http://launchpadlibrarian.net/42066171/version.log
--
HPET warning on P55 based mainboard (GA-P55A-UD5)
https://bugs.launchpad.net/bugs/548914
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Attachment added: "dmesg"
http://launchpadlibrarian.net/42066193/dmesg.log
--
HPET warning on P55 based mainboard (GA-P55A-UD5)
https://bugs.launchpad.net/bugs/548914
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I'm experiencing a similar problem with 10.04 beta1 on a GA-P55A-UD5
Mainboard.
When the disk is plugged in eSata, it is reconized from kernel, and
appears in gnome under "computer".
But a password is asked when I double-click on the drive.
The permissions of the block devices are the same if th
27 matches
Mail list logo
