Bug#420631: Frohes Neues Jahr
Achtung! - Wichtiger Hinweis für das Neue Jahr! Fahren Sie nicht betrunken! Autofahren ist gefährlich, wenn man einen Tropfen Alkohol getrunken hat. Da fragt man sich doch gleich: Bestehe ich die Fahrprüfung heute noch? Wie gut, daß ich mich online testen kann: http://Pruefung-beginnen.net/[EMAIL PROTECTED] Sie werden gebeten, die Prüfung sofort durchzuführen und abzuschließen. Bitte benutzen Sie folgenden Link: http://Pruefung-beginnen.net/[EMAIL PROTECTED] Mit freundlichen Grüßen Sabrina Schneider - Sie haben sich mit der E-Mail-Adresse [EMAIL PROTECTED] für den Informationsdienst angemeldet.
Re: d-i support for running in a Xen guest domain
On Wed, Jan 09, 2008 at 09:58:45PM +, Ian Campbell wrote: I'm interested in getting d-i to work seamlessly inside a Xen guest domain using the paravirt_ops kernel support for Xen in 2.6.24+ (currently only available in the kernel svn trunk snapshots builds I think). 2.6.23 already have the same amount of support than .24. It would be reasonably easy to create -xen-686 udebs (in fact I did for my testing) and tweak d-i to select a -xen kernel package image as appropriate during install, however I think I have a better idea ;-)... The explicit Xen images will disappear in the future, it just lacks infrastructure. Bastian -- Yes, it is written. Good shall always destroy evil. -- Sirah the Yang, The Omega Glory, stardate unknown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#455923: Info received (Bug#455923: Acknowledgement (Failt to mount the root filesystem of sata hard disc on amd64 kernel))
well, strangely, if i add ahci to /etc/modprobe.d/blacklist the system still dont boots, and then i need, on busybox, to remove the module from /etc/modprobe.d/balcklist and load it again. so i can boot. :( in resume, my pc almost never boot alone, at first time.
Bug#455923: Failt to mount the root filesystem of sata hard disc on amd64 kernel
On Wed, Dec 12, 2007 at 02:35:51PM -0200, Paulo Diovani wrote: my kernel does not create /dev/sda1 (root) on boot. grub loads from the same hd and, sometimes, the system works fine, but in most of'em i fall into busybox and have only /dev/hda (cdrom). What is the content of /sys/block at this time? debian-laptop:~# uname -a Linux debian-laptop 2.6.23-1-amd64 #1 SMP Fri Nov 30 12:19:15 UTC 2007 x86_64 GNU/Linux Please recheck with 2.6.24-rc7, see http://wiki.debian.org/DebianKernel for further informations. Bastian -- Hailing frequencies open, Captain. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#455923: Failt to mount the root filesystem of sata hard disc on amd64 kernel
debian-laptop:~# ls /sys/block/ hdaloop2 loop5 ram0 ram11 ram14 ram3 ram6 ram9 loop0 loop3 loop6 ram1 ram12 ram15 ram4 ram7 sda loop1 loop4 loop7 ram10 ram13 ram2 ram5 ram8 debian-laptop:~# ls /sys/block/sda/ capability device queue removable sda2 sizestat uevent dev holders range sda1 sda3 slaves subsystem
Processed: notfound 421325 in 2.6.22-1
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.11 notfound 421325 2.6.22-1 Bug#421325: boot fsck cooked nearly the cpu Bug no longer marked as found in version 2.6.22-1. (By the way, this Bug is currently marked as done.) End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with nfs and initramfs-tools
Hi,
thank you for your reply. I discovered, that there is no easy way to
solve the problem just by adding some configuration. I had to hack the
nfs-script to get the work done.
Here is the result of my work, just to let you know that there is no
direct problem with the package ;)
Am Montag, den 07.01.2008, 18:28 +0100 schrieb maximilian attems:
you could checkout initramfs-tools togethere with newer klibc from Lenny
and see if you can still reproduce with those your trouble?
Thank you for pointing me to klibc, there is one of the problems in this
case.
When u use the parameter ip=::dhcp on the commandline, the following
command will be executed by the
nfs-script /usr/share/initramfs-tools/scripts/nfs:
ipconfig -d ::dhcp
This loops forever because one interface will not come up due to a
missing network-cable.
Adding -t 10 kills ipconfig after 10 tries.
ipconfig -t 10 -d ::dhcp
I dont't know if the loop is a desired behaviour or if it is a bug, I
think there are good reasons for both possibilities.
After that sourceing /tmp/net-${DEVICE}.conf will overwrite the nfs
setting from the kernel-commandline with the setting gathered from the
dhcp-server. And again, this could be desired or not ;)
Our DHCP-Server does not know anything about the nfs-root because it is
needed exclusively by the rescuesystem.
In addition ${DEVICE} seemes to be hardcoded in the initramfs.conf. If
initramfs.conf says eth0 and the interface is eth1 it will not be
sourced.
I have put it like this:
for i in `ls /tmp/net-*.conf`; do . $i; done
as I know that there is only one nic which will be configured.
--
Mit freundlichen Gruessen
Andre Timmermann
Nine Internet Solutions AG, nine.ch, Letzigraben 77, CH-8003 Zuerich
Tel +41 44 637 40 00 | Direkt +41 44 637 40 06 | Fax +41 44 481 16 43
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#460131: mkvmlinuz: [INTL:it] Italian debconf templates translation
Package: mkvmlinuz Severity: wishlist Tags: patch l10n Please add the italian debconf templates translation (attached). Thanks, Luca it.po Description: Binary data
Bug#460132: Nikon D40 DSLR doesn't mount over USB
Package: linux-image-2.6.22-3-686 Version: 2.6.22-6 Severity: normal Tags: patch --- Please enter the report below this line. --- Note: This same bug was found on the AMD64 kernel When a Nikon D40 Digital Single Lens Reflex (DSLR) camera is connected if fails to the device and thus does not import the pictures. The following is reported in /var/log/syslog --- System information. ---Jan 10 21:04:45 wiley kernel: Initializing USB Mass Storage driver... Jan 10 21:04:45 wiley kernel: scsi0 : SCSI emulation for USB Mass Storage devices Jan 10 21:04:45 wiley kernel: usbcore: registered new interface driver usb-storage Jan 10 21:04:45 wiley kernel: USB Mass Storage support registered. Jan 10 21:04:45 wiley kernel: usb-storage: device found at 2 Jan 10 21:04:45 wiley kernel: usb-storage: waiting for device to settle before scanning Jan 10 21:04:45 wiley NetworkManager: debug [119085.267573] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_4b0_413_6286775_if0'). Jan 10 21:04:45 wiley NetworkManager: debug [119085.335633] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_4b0_413_6286775_usbraw'). Jan 10 21:04:50 wiley kernel: usb-storage: device scan complete Jan 10 21:04:50 wiley kernel: scsi 0:0:0:0: Direct-Access NIKOND40 1.10 PQ: 0 ANSI: 2 Jan 10 21:04:50 wiley kernel: sd 0:0:0:0: [sda] 3970049 512-byte hardware sectors (2033 MB) Jan 10 21:04:50 wiley kernel: sd 0:0:0:0: [sda] Write Protect is off Jan 10 21:04:50 wiley kernel: sd 0:0:0:0: [sda] Mode Sense: 0f 00 00 00 Jan 10 21:04:50 wiley kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through Jan 10 21:04:50 wiley kernel: sd 0:0:0:0: [sda] 3970049 512-byte hardware sectors (2033 MB) Jan 10 21:04:50 wiley kernel: sd 0:0:0:0: [sda] Write Protect is off Jan 10 21:04:50 wiley kernel: sd 0:0:0:0: [sda] Mode Sense: 0f 00 00 00 Jan 10 21:04:50 wiley kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through Jan 10 21:04:50 wiley kernel: sda: sda1 Jan 10 21:04:50 wiley kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk Jan 10 21:04:50 wiley NetworkManager: debug [119090.419093] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_4b0_413_6286775_if0_scsi_host'). Jan 10 21:04:50 wiley NetworkManager: debug [119090.427267] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_4b0_413_6286775_if0_scsi_host_scsi_device_lun0'). Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 3970048 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 3970048 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 3970048 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 3970048 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 3970048 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 3970048 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 3970048 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 3970048 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 3970048 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 3970048 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 3970048 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 3970048 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 3970048 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 3970048 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 40 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 40 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 41 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 42 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 40 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 41 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 40 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 41 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 40 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 41 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 40 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 41 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 0 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 0 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 1 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 0 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 1 Jan 10 21:04:50 wiley NetworkManager: debug
Bug#460132: marked as done (Nikon D40 DSLR doesn't mount over USB)
Your message dated Thu, 10 Jan 2008 23:04:39 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#460132: Nikon D40 DSLR doesn't mount over USB has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: linux-image-2.6.22-3-686 Version: 2.6.22-6 Severity: normal Tags: patch --- Please enter the report below this line. --- Note: This same bug was found on the AMD64 kernel When a Nikon D40 Digital Single Lens Reflex (DSLR) camera is connected if fails to the device and thus does not import the pictures. The following is reported in /var/log/syslog --- System information. ---Jan 10 21:04:45 wiley kernel: Initializing USB Mass Storage driver... Jan 10 21:04:45 wiley kernel: scsi0 : SCSI emulation for USB Mass Storage devices Jan 10 21:04:45 wiley kernel: usbcore: registered new interface driver usb-storage Jan 10 21:04:45 wiley kernel: USB Mass Storage support registered. Jan 10 21:04:45 wiley kernel: usb-storage: device found at 2 Jan 10 21:04:45 wiley kernel: usb-storage: waiting for device to settle before scanning Jan 10 21:04:45 wiley NetworkManager: debug [119085.267573] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_4b0_413_6286775_if0'). Jan 10 21:04:45 wiley NetworkManager: debug [119085.335633] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_4b0_413_6286775_usbraw'). Jan 10 21:04:50 wiley kernel: usb-storage: device scan complete Jan 10 21:04:50 wiley kernel: scsi 0:0:0:0: Direct-Access NIKOND40 1.10 PQ: 0 ANSI: 2 Jan 10 21:04:50 wiley kernel: sd 0:0:0:0: [sda] 3970049 512-byte hardware sectors (2033 MB) Jan 10 21:04:50 wiley kernel: sd 0:0:0:0: [sda] Write Protect is off Jan 10 21:04:50 wiley kernel: sd 0:0:0:0: [sda] Mode Sense: 0f 00 00 00 Jan 10 21:04:50 wiley kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through Jan 10 21:04:50 wiley kernel: sd 0:0:0:0: [sda] 3970049 512-byte hardware sectors (2033 MB) Jan 10 21:04:50 wiley kernel: sd 0:0:0:0: [sda] Write Protect is off Jan 10 21:04:50 wiley kernel: sd 0:0:0:0: [sda] Mode Sense: 0f 00 00 00 Jan 10 21:04:50 wiley kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through Jan 10 21:04:50 wiley kernel: sda: sda1 Jan 10 21:04:50 wiley kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk Jan 10 21:04:50 wiley NetworkManager: debug [119090.419093] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_4b0_413_6286775_if0_scsi_host'). Jan 10 21:04:50 wiley NetworkManager: debug [119090.427267] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_4b0_413_6286775_if0_scsi_host_scsi_device_lun0'). Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 3970048 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 3970048 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 3970048 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 3970048 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 3970048 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 3970048 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 3970048 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 3970048 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 3970048 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 3970048 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 3970048 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 3970048 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 3970048 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 3970048 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 40 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 40 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 41 Jan 10 21:04:50 wiley kernel: Buffer I/O error on device sda, logical block 42 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 40 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 41 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 40 Jan 10 21:04:50 wiley kernel: end_request: I/O error, dev sda, sector 41 Jan 10 21:04:50 wiley
Bug#459546: linux-image-2.6.18-5-xen-686: bnx2 fails to work with xen bridging
On Mon, Jan 07, 2008 at 09:59:10AM +0100, Xavier Poinsard wrote: Package: linux-image-2.6.18-5-xen-686 Version: 2.6.18.dfsg.1-17 Severity: important The shipped version of the bnx2 driver fails to work with xen bridging. With an updated version like this one : http://linux.dell.com/files/bnx2/xen-fix/ the network driver is working. This bug fix is detailled in the driver changelog. Updating this driver would save many users of xen having this broadcom network card. hey Xavier, This seems like a reasonable bug to fix in a stable update. However an important part of accepting something into a stable release (possibly the most important part) is demonstrating a high confidence that this will not break things for other users. Since this patch requires a firmware blob update, its not possible for us to do that with this patch alone. Michael: Do you know (and can you share) what the changes were to the fw in this changeset? http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=af3ee519c5d6bebbda9bf0ca3b81bc50b4dd2163 -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#459546: linux-image-2.6.18-5-xen-686: bnx2 fails to work with xen bridging
On Thu, 2008-01-10 at 17:08 -0700, dann frazier wrote: On Mon, Jan 07, 2008 at 09:59:10AM +0100, Xavier Poinsard wrote: Package: linux-image-2.6.18-5-xen-686 Version: 2.6.18.dfsg.1-17 Severity: important The shipped version of the bnx2 driver fails to work with xen bridging. With an updated version like this one : http://linux.dell.com/files/bnx2/xen-fix/ the network driver is working. This bug fix is detailled in the driver changelog. Updating this driver would save many users of xen having this broadcom network card. hey Xavier, This seems like a reasonable bug to fix in a stable update. However an important part of accepting something into a stable release (possibly the most important part) is demonstrating a high confidence that this will not break things for other users. Since this patch requires a firmware blob update, its not possible for us to do that with this patch alone. Michael: Do you know (and can you share) what the changes were to the fw in this changeset? http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=af3ee519c5d6bebbda9bf0ca3b81bc50b4dd2163 This is the actual firmware patch that fixed the problem: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7510873d8659f4192cb5b3327f748e401d216399 Xen puts the networking device in promiscuous mode and programs the MAC address to fe:ff:ff:ff:ff:ff. The network stack continues to use the factory programmed MAC address of the NIC. This should normally be OK since we are in promiscuous mode and should be able to receive all packets. There was however a flaw in the firmware when the NIC was configured like this with management firmware also running. Management firmware also uses the same factory programmed MAC address. In such a configuration, packets addressed to the NIC's factory address would be delivered to management firmware only but not to the Linux driver. This was clearly a bug as promiscuous mode should include reception of all packets. I think the firmware programmer did not foresee such a scenario and our test cases did not include something like this. So the change in the firmware was to correct this bug. It has been lab and field tested for over a year. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#459546: linux-image-2.6.18-5-xen-686: bnx2 fails to work with xen bridging
On Thu, Jan 10, 2008 at 05:22:49PM -0800, Michael Chan wrote: Michael: Do you know (and can you share) what the changes were to the fw in this changeset? http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=af3ee519c5d6bebbda9bf0ca3b81bc50b4dd2163 This is the actual firmware patch that fixed the problem: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7510873d8659f4192cb5b3327f748e401d216399 Xen puts the networking device in promiscuous mode and programs the MAC address to fe:ff:ff:ff:ff:ff. The network stack continues to use the factory programmed MAC address of the NIC. This should normally be OK since we are in promiscuous mode and should be able to receive all packets. There was however a flaw in the firmware when the NIC was configured like this with management firmware also running. Management firmware also uses the same factory programmed MAC address. In such a configuration, packets addressed to the NIC's factory address would be delivered to management firmware only but not to the Linux driver. This was clearly a bug as promiscuous mode should include reception of all packets. I think the firmware programmer did not foresee such a scenario and our test cases did not include something like this. So the change in the firmware was to correct this bug. It has been lab and field tested for over a year. Thanks Michael. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419950: NETDEV WATCHDOG problems return
On Tue, 8 Jan 2008, maximilian attems wrote: On Tue, Jan 08, 2008 at 03:44:11PM -0500, Lou Poppler wrote: Is it possible to find version 2.6.18.dfsg.1-13etch5 somewhere ? snapshot.debian.net Thanks Maks, I re-installed 1-13etch5 and it also fails for me now. With any more than light load, the network card becomes unusable under 1-13etch5, 1-13etch6, and 1-17. Apparently something else besides the kernel has changed here to bring back the problem. I guess I better re-install 1-17, and experiment with changing kernel options; but I don't really have any good ideas at this point. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
2.6.23 upload to p-u
I plan to upload the first linux-2.6.23 for etchnahalf this coming Sunday. The changes I have in mind before then are: * Merge in 2.6.23.13 (one changeset) * Revert to the older Firewire stack (for compatability w/ etch) Anything else? -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#460190: linux-image-686: USB detection problem
Package: linux-image-686 Version: 2.6.22+11 Severity: important Kernel only detect USB devices conected at system boot. If i conect a USB device when the system is booted, 'lsusb' command does not list it, but some devices work when they are not listed in 'lsusb' while other does not work. Same for 2.6.23 image on Sid. I think this is a Kernel bug becouse i have made the test in a Linux Kernel installed from .debs from Ubuntu repositories (linux-image-2.6.24-4-generic) and all usb devices are listed and working on 'lsusb' using it on Debian. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-686 depends on: ii linux-image-2.6-686 2.6.22+11 Linux 2.6 image on PPro/Celeron/PI linux-image-686 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#460192: linux-image-2.6.23-1-686: USB detection problem
Package: linux-image-2.6.23-1-686 Version: 2.6.23-2 Severity: important Kernel only detect USB devices conected at system boot. If i conect a USB device when the system is booted, 'lsusb' command does not list it, but some devices work when they are not listed in 'lsusb' while other does not work. I think this is a bug of Debian kernel, becouse if I install a Ubuntu kernel in Debian, everything work well. -- Package-specific info: ** Version: Linux version 2.6.23-1-686 (Debian 2.6.23-2) ([EMAIL PROTECTED]) (gcc version 4.1.3 20071209 (prerelease) (Debian 4.1.2-18)) #1 SMP Fri Dec 21 13:57:07 UTC 2007 ** cmdline: root=/dev/sda1 ro vga=788 ** Not tainted ** Kernel log: sd 0:0:1:0: Attached scsi generic sg1 type 0 sr 1:0:0:0: Attached scsi generic sg2 type 5 usb 3-2: configuration #1 chosen from 1 choice kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Real Time Clock Driver v1.12ac input: PC Speaker as /class/input/input2 pci_hotplug: PCI Hot Plug PCI Core version: 0.5 shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Linux agpgart interface v0.102 Linux video capture interface: v2.00 sis96x_smbus :00:02.1: SiS96x SMBus base address: 0xe600 agpgart: Detected SiS chipset - id:1606 agpgart: AGP aperture is 64M @ 0xd800 parport_pc 00:0a: reported by Plug and Play ACPI parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA] input: Power Button (FF) as /class/input/input3 ACPI: Power Button (FF) [PWRF] input: Power Button (CM) as /class/input/input4 ACPI: Power Button (CM) [PWRB] bttv: driver version 0.9.17 loaded bttv: using 8 buffers with 2080k (520 pages) each for capture bttv: Bt8xx card found (0). ACPI: PCI Interrupt :00:0a.0[A] - GSI 18 (level, low) - IRQ 22 bttv0: Bt878 (rev 2) at :00:0a.0, irq: 22, latency: 32, mmio: 0xdf00 parport0: Printer, HEWLETT-PACKARD DESKJET 710C bttv0: detected: AVermedia TVCapture 98 [card=13], PCI subsystem ID is 1461:0002 bttv0: using: AVerMedia TVCapture 98 [card=13,autodetected] bttv0: gpio: en=, out= in=000477c3 [init] bttv0: Hauppauge/Voodoo msp34xx: reset line init [11] bttv0: Avermedia eeprom[0x4011]: tuner=5 radio:no remote control:yes bttv0: tuner type=5 bttv0: i2c: checking for MSP34xx @ 0x80... not found bttv0: i2c: checking for MSP34xx (alternate address) @ 0x88... not found bttv0: i2c: checking for TDA9875 @ 0xb0... not found bttv0: i2c: checking for TDA7432 @ 0x8a... not found tuner 1-0061: chip found @ 0xc2 (bt878 #0 [sw]) tuner 1-0061: type set to 5 (Philips PAL_BG (FI1216 and compatibles)) tuner 1-0061: type set to 5 (Philips PAL_BG (FI1216 and compatibles)) bttv0: registered device video0 bttv0: registered device vbi0 bttv0: PLL: 28636363 = 35468950 .. ok input: bttv IR (card=13) as /class/input/input5 bt878: AUDIO driver version 0.0.0 loaded bt878: Bt878 AUDIO function found (0). ACPI: PCI Interrupt :00:0a.1[A] - GSI 18 (level, low) - IRQ 22 bt878_probe: card id=[0x21461], Unknown card. Exiting.. ACPI: PCI interrupt for device :00:0a.1 disabled bt878: probe of :00:0a.1 failed with error -22 ACPI: PCI Interrupt :00:08.0[A] - GSI 16 (level, low) - IRQ 19 Adding 2546260k swap on /dev/sda9. Priority:-1 extents:1 across:2546260k EXT3 FS on sda1, internal journal loop: module loaded device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [EMAIL PROTECTED] fuse init (API version 7.8) eth1: link up, 100Mbps, full-duplex, lpa 0x45E1 eth0: setting half-duplex. lp0: using parport0 (interrupt-driven). ppdev: user-space parallel port driver Netfilter messages via NETLINK v0.30. nf_conntrack version 0.5.0 (16384 buckets, 65536 max) ip_tables: (C) 2000-2006 Netfilter Core Team [drm] Initialized drm 1.1.0 20060810 ACPI: PCI Interrupt :01:00.0[A] - GSI 16 (level, low) - IRQ 19 [drm] Initialized radeon 1.28.0 20060524 on minor 0 agpgart: Found an AGP 2.0 compliant device at :00:00.0. agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode [drm] Setting GART location based on new memory map [drm] Loading R200 Microcode [drm] writeback test succeeded in 1 usecs NET: Registered protocol family 10 lo: Disabled Privacy Extensions ADDRCONF(NETDEV_UP): eth0: link is not ready NET: Registered protocol family 4 NET: Registered protocol family 3 NET: Registered protocol family 5 usb 4-5: new high speed USB device using ehci_hcd and address 4 usb 4-5: configuration #1 chosen from 1 choice Initializing USB Mass Storage driver... scsi2 : SCSI emulation for USB Mass Storage devices usbcore: registered new interface driver usb-storage USB Mass Storage support registered. usb-storage: device found at 4 usb-storage: waiting for device to settle before scanning usb-storage: device scan complete scsi 2:0:0:0: Direct-Access VBTM Store 'n' Go 1.02 PQ: 0 ANSI: 0 CCS sd 2:0:0:0: [sdc] 2013184 512-byte hardware sectors (1031 MB) sd 2:0:0:0: [sdc] Write Protect is
