<p dir="ltr">Well, crud. A programmable serial interface would be perfect but it sounds like the hardware combo doesn't support it.</p>
<div class="gmail_quote">On Nov 10, 2013 2:24 PM, "Alex Carver" <<a href="mailto:agcarver%2Bale@acarver.net">agcarver+ale@acarver.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'll do my best but given that this has apparently been an ongoing<br>
problem since 2007 across multiple distros it seems that no one has<br>
quite figured out how to resolve it. It appears I can have IrDA -or-<br>
serial but not both in some systems. In this case some digging suggests<br>
an IO memory mapping issue. The IrDA port tries to grab two addresses<br>
(0x2f8 and 0x2e8) but there's already two ports in use by the serial<br>
module (0x3f8-physport and 0x2f8-modem). So the IrDA modules does a<br>
power grab, shuffles addresses and IRQs around and poof, no more serial<br>
ports. The toshsat1800-irdasetup program identifies the IrDA chip and<br>
sees three serial ports. I'm not sure why it sees three though but it<br>
doesn't appear that I can change the IO port addresses.<br>
<br>
On 11/10/2013 09:57, Jim Kinney wrote:<br>
> Cool! If you find out why the IrDA causes a conflict be sure to add to this<br>
> thread, please. Oddball kernel issues are weird.<br>
> On Nov 10, 2013 12:25 PM, "Alex Carver" <<a href="mailto:agcarver%2Bale@acarver.net">agcarver+ale@acarver.net</a>> wrote:<br>
><br>
>> Nope, it was completely clean and so was the cardbus socket (the wifi<br>
>> card works in both cardbus sockets). Three hours of google searching<br>
>> led me to blacklist the smsc_ircc2 module which woke up the serial ports<br>
>> (both the on-board and the modem) and everything started working.<br>
>> Somehow that module (used by the IrDA module) causes issues with serial<br>
>> ports on many laptops. I don't know why, that's probably more google<br>
>> searching. I don't need IrDA support (though it would be fun to play<br>
>> with since I have several IrDA enabled devices) but it would be nice to<br>
>> find out why smsc_ircc2 messes things up.<br>
>><br>
>> On 11/10/2013 05:33, Jim Kinney wrote:<br>
>>> Sounds like the modem is dead or maybe has some crud on the board. Try an<br>
>>> electric cleaner spray.<br>
>>> On Nov 9, 2013 3:47 PM, "Alex Carver" <<a href="mailto:agcarver%2Bale@acarver.net">agcarver+ale@acarver.net</a>> wrote:<br>
>>><br>
>>>> I'm tinkering with a cardbus modem I found in one of my hardware piles<br>
>>>> (I'm still missing the actual cable but I know I have it here<br>
>>>> somewhere). Anyway, I'm trying to figure out the best way to see if<br>
>>>> it's working (eg, responding to AT commands) but I can't quite seem to<br>
>>>> get minicom to talk to it. It's not a winmodem as far as I know.<br>
>>>> According to dmesg, the pcmcia system sees the card, then serial_cs sees<br>
>>>> the card and identifies it as a 16550A sittign on IRQ 3 0x3e8. It<br>
>>>> eventually gets assigned to /dev/ttyS2.<br>
>>>><br>
>>>> So far nothing seems out of the ordinary but I just can't seem to get it<br>
>>>> to respond to any basic commands (not even plain AT for which I should<br>
>>>> see OK). I know the cardbus system is working because I also have a<br>
>>>> wireless network card in there and that's working fine.<br>
>>>><br>
>>>> Ideas for probing and testing the modem?<br>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</blockquote></div>