On Wed, 23 Feb 2011 07:27:18 -0500 (EST), Dererk <der...@debian.org> wrote:
>
> This can be easily solved through some udev's rules, unfortunately I
> lack the hardware for this test from time to time, so I would need you
> to send me the corresponding lspci -v from this device.
> As soon as you provide me with that information I'll be able to go on
> and upload a fix for this.
Pertinent output of "lspci -vv -nn":
00:06.0 Communications controller [0780]: Agere Systems L56xM+S [Mars-2]
WinModem 56k [11c1:0449] (rev 01)
Subsystem: AMBIT Microsystem Corp. Lucent Win Modem [1468:0440]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 11
Region 0: Memory at fedffc00 (32-bit, non-prefetchable) [size=256]
Region 1: I/O ports at fc88 [size=8]
Region 2: I/O ports at f800 [size=256]
Capabilities: [f8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=0mA
PME(D0-,D1-,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: martian
I hope this contains the information that you need.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
