Package: udev Version: 161-1 Severity: normal
My Huawei E169 GSM modem has a built-in micro-sd card reader. On a current squeeze installation, the reader is detected and the corresponding device file (/dev/sdb) is created. However, no device is created for the partition of the card, which is apparently never read. Trying to force a "mount /dev/sdb /mnt" results in a "mount: no medium found on /dev/sdb", although the card is inserted. I have tried the modem on different debian machines, and the card is reliably detected on a 32-bit, mostly lenny installation with a current squeeze kernel and udev 154-1, as well as on pure lenny installation. Unfortunately, I cannot find the 154-1 version of the amd64 udev package on the internet anymore, or I would have tried downgrading. Regards, Carlos -- System Information: Debian Release: squeeze/sid APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pt_PT (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages udev depends on: ii debconf [debconf-2.0] 1.5.35 Debian configuration management sy ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libselinux1 2.0.96-1 SELinux runtime shared libraries ii libudev0 161-1 libudev shared library ii libusb-0.1-4 2:0.1.12-15 userspace USB programming library ii lsb-base 3.2-23.1 Linux Standard Base 3.2 init scrip ii util-linux 2.17.2-3.1 Miscellaneous system utilities Versions of packages udev recommends: ii pciutils 1:3.1.7-4 Linux PCI Utilities ii usbutils 0.87-5 Linux USB utilities udev suggests no packages. -- Configuration Files: /etc/modprobe.d/blacklist.conf changed: blacklist evbug blacklist usbmouse blacklist usbkbd blacklist eepro100 blacklist de4x5 blacklist am53c974 blacklist iTCO_wdt blacklist pcspkr -- debconf information: udev/new_kernel_needed: false udev/title/upgrade: udev/reboot_needed: -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
