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

Bug#631157: marked as done (base: pcmcia card xircom (REM56G-100) won't work at boot, but will work after ejecting and reinstering)

Your message dated Tue, 25 Jun 2013 20:00:55 +0200
with message-id <20130625180055.GA4890@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #631157,
regarding base: pcmcia card xircom (REM56G-100) won't work at boot, but will work after ejecting and reinstering
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.)


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

I have a XIRCOM Realport REM65G-100, pluged into Dell Inspiron 3700.

I tried to install the card, drivers where present, the card is detected, but
won't work. I found this:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/45295

In this bugreport people are advising to eject the card and insert it while the
laptop is on. It works!

Quote:

"BTW, the Xircom card is a multi-device card (LAN and modem device) and the
modem is detected and configured during boot, but not the LAN.
The kernel module 'serial_cs' is loaded and bound to the device
The kernel module 'xirc2ps_cs' is loaded but not bound !?

Might the problem be related to udev ?"
- Patrick Frey

'lsmod' shows some lines that may be inetresting:

xirc2ps_cs     10343  0
serial_cs       13924  1
pcmcia          16194  2 xir2c2ps_cs,serial_cs
pcmcia_core  20150  5 xir2c2ps_cs,serial_cs,pcmcia,yenta_socket,rsrc_nonstatic

'dmesg' has some interesting lines too:

[13.877155] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into
slot 0
[14.409329] pcmcia 0.0: pcmcia: registered new device pcmcia0.0

maybe 'find / -name xir*' can be interesting:

/lib/modules/2.6.32-5-686/kernel/drivers/net/tulip/xircom_cb.ko
/lib/modules/2.6.32-5-686/kernel/drivers/net/pcmcia/xirc2ps_cs.ko
/sys/bus/pcmcia/drivers/xirc2ps_cs
/sys/module/pcmcia_core/holders/xirc2ps_cs
/sys/module/pcmcia/holders/xirc2ps_cs
/sys/module/xirc2ps_cs

Hopfully I can help resolving this bug.



-- System Information:
Debian Release: 6.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=nl_BE.utf8, LC_CTYPE=nl_BE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz

--- End Message ---
Reply to: