[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#370520: marked as done (udev doesn't get a UEVENT when plugging in PCMCIA-Card (16bit))

Your message dated Fri, 24 Jul 2009 23:37:23 +0200
with message-id <20090724213723.GA19471@galadriel.inutil.org>
and subject line Re: udev doesn't get a UEVENT when plugging in PCMCIA-Card (16bit)
has caused the Debian Bug report #370520,
regarding udev doesn't get a UEVENT when plugging in PCMCIA-Card (16bit)
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
370520: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=370520
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: udev
Version: 0.093-1
Severity: normal

Hi there.

When plugging in my 16-bit orinoco wireless lan pcard, according to
udevmonitor udev doesn't get a UEVENT from the kernel.

The kernel itself says the following when plugging in/out the card,
respectively:

pccard: PCMCIA card inserted into slot 1
pccard: card ejected from slot 1

Then i read the udev-rulefile "pcmcia.rules" and "executed it by hand".
The strange thing is that when running "pcmcia-check-broken-cis -r 1" (or
0, depends on the socket in which the card is plugged in) the kernel says:

cs: unable to map card memory!
cs: unable to map card memory!

The problems appeared after upgrading from pcmcia-cs to pcmciautils,
before this everything worked fine. Oh, btw: when plugging in other
devices, usb sticks for example, I get a UEVENT and everything works.

I hope this problem is udev-related.

bye bye
Johannes

-- Package-specific info:
-- /etc/udev/rules.d/:
/etc/udev/rules.d/:
insgesamt 8
lrwxrwxrwx 1 root root  20 2006-06-03 14:58 020_permissions.rules -> ../permissions.rules
lrwxrwxrwx 1 root root  12 2006-06-05 16:52 050_hal-plugdev.rules -> ../hal.rules
lrwxrwxrwx 1 root root  15 2006-05-28 18:30 85-pcmcia.rules -> ../pcmcia.rules
lrwxrwxrwx 1 root root  13 2006-06-03 14:58 udev.rules -> ../udev.rules
lrwxrwxrwx 1 root root  25 2006-06-03 14:58 z20_persistent-input.rules -> ../persistent-input.rules
lrwxrwxrwx 1 root root  19 2006-06-03 14:58 z20_persistent.rules -> ../persistent.rules
-rw-r--r-- 1 root root 462 2006-06-03 14:58 z25_persistent-cd.rules
-rw-r--r-- 1 root root 444 2006-06-03 14:58 z25_persistent-net.rules
lrwxrwxrwx 1 root root  33 2006-06-03 14:58 z45_persistent-net-generator.rules -> ../persistent-net-generator.rules
lrwxrwxrwx 1 root root  12 2006-06-03 14:58 z50_run.rules -> ../run.rules
lrwxrwxrwx 1 root root  16 2006-06-03 14:58 z55_hotplug.rules -> ../hotplug.rules
lrwxrwxrwx 1 root root  19 2005-11-30 22:41 z60_alsa-utils.rules -> ../alsa-utils.rules
lrwxrwxrwx 1 root root  15 2005-11-30 19:28 z60_hdparm.rules -> ../hdparm.rules
lrwxrwxrwx 1 root root  33 2006-06-05 16:39 z60_xserver-xorg-input-wacom.rules -> ../xserver-xorg-input-wacom.rules
lrwxrwxrwx 1 root root  29 2006-06-03 14:58 z75_cd-aliases-generator.rules -> ../cd-aliases-generator.rules

-- /sys/:
/sys/block/hda/dev
/sys/block/hda/hda1/dev
/sys/block/hda/hda2/dev
/sys/block/hda/hda3/dev
/sys/block/hda/hda4/dev
/sys/block/hdc/dev
/sys/class/graphics/fb0/dev
/sys/class/input/input0/event0/dev
/sys/class/input/input1/event1/dev
/sys/class/input/input1/mouse0/dev
/sys/class/input/input2/event2/dev
/sys/class/input/input2/mouse1/dev
/sys/class/input/mice/dev
/sys/class/misc/fuse/dev
/sys/class/misc/psaux/dev
/sys/class/ppdev/parport0/dev
/sys/class/sound/audio/dev
/sys/class/sound/controlC0/dev
/sys/class/sound/dsp/dev
/sys/class/sound/mixer/dev
/sys/class/sound/pcmC0D0c/dev
/sys/class/sound/pcmC0D0p/dev
/sys/class/sound/timer/dev
/sys/class/usb_device/usbdev1.1/dev

-- Kernel configuration:
 isapnp_init not present.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16.19
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)

Versions of packages udev depends on:
ii  initscripts                2.86.ds1-14.1 Scripts for initializing and shutt
ii  libc6                      2.3.6-13      GNU C Library: Shared libraries
ii  libselinux1                1.30-1        SELinux shared libraries
ii  libvolume-id0              0.093-1       libvolume_id shared library
ii  lsb-base                   3.1-9         Linux Standard Base 3.1 init scrip

udev recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Sun, Dec 21, 2008 at 11:20:35AM +0100, Moritz Muehlenhoff wrote:
> On Mon, Jun 05, 2006 at 06:23:32PM +0200, Johannes Bittner wrote:
> > Package: udev
> > Version: 0.093-1
> > Severity: normal
> > 
> > Hi there.
> > 
> > When plugging in my 16-bit orinoco wireless lan pcard, according to
> > udevmonitor udev doesn't get a UEVENT from the kernel.
> > 
> > The kernel itself says the following when plugging in/out the card,
> > respectively:
> > 
> > pccard: PCMCIA card inserted into slot 1
> > pccard: card ejected from slot 1
> > 
> > Then i read the udev-rulefile "pcmcia.rules" and "executed it by hand".
> > The strange thing is that when running "pcmcia-check-broken-cis -r 1" (or
> > 0, depends on the socket in which the card is plugged in) the kernel says:
> > 
> > cs: unable to map card memory!
> > cs: unable to map card memory!
> > 
> > The problems appeared after upgrading from pcmcia-cs to pcmciautils,
> > before this everything worked fine. Oh, btw: when plugging in other
> > devices, usb sticks for example, I get a UEVENT and everything works.
> 
> Does this error still occur with more recent kernel versions?

No further feedback, closing the bug.

If anyone reencounters the problem, please reopen this bug.

Cheers,
        Moritz

--- End Message ---
Reply to: