Thanks for the input. The errors I pointed out should be available in the /var/log/messages or messages.1 .2 .3 etc...or in dmesg each time you reboot the machine. At least that is the case with mine. If you don't have it then it's I guess very specific to this atom board. I know someone else added something along the lines "irq=fixconflict" to get rid of the issue with a wireless USB mouse showing same symptoms and CentOS. IRQ conflicts is also one of my thoughts as well but I can't play at BIOS level at this time as the server is thousands miles away from me.<div>
<br></div><div>Regards,<br><br><div class="gmail_quote">On Sun, Jan 2, 2011 at 8:18 PM, Sebastian <span dir="ltr"><<a href="mailto:shop@open-t.co.uk">shop@open-t.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<div class="im"><br>
<br>
On 01/02/2011 08:08 PM, Bruce B wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks for the input. I have the latest drivers but it seems that there<br>
is some serious incompatibility issue with the kernel as when the<br>
FLASHING happens even if the system is restarted it's still not<br>
detected. One has to re-plug it in and then it shows in "wanrouter hwprobe".<br>
<br>
It could also be that the atom board is not compatible with the driver<br>
in my case. It your /var/log/messages upon restart do you any line that<br>
might match this:<br>
*<br>
*<br>
*cd /var/log/*<br>
*grep -o "device not accepting address" **<br>
*grep -o "USB device is disconnected" **<br>
*dmesg | egrep "device not accepting address" *<br>
*dmesg | egrep "USB device is disconnected" *<br>
<br>
If not then you are not experiencing the same issue. If you have then<br>
it's a universal issue and not hardware specific.<br>
<br>
I would really appreciate it if you look into your logs and let me know.<br>
</blockquote>
<br></div>
If you are asking me to look into the logs when the U100 is not recognised and it is flashing - I'm afraid I can't help much - as this problem went away and haven't had issues any more for at least 6-8 months now. Considering the U100 persist in giving problems even after computer restarts somehow sounds to me like a hardware issue. I wouldn't be surprised if the Acer Aspire motherboard is not coping very well with both of them being plugged in - although, obviously, it should.<br>
<br>
This linux-usb FAQ seems to also suggest that the problem is hardware (based on the "device is not accepting address" error message):<br>
<br>
<a href="http://www.linux-usb.org/FAQ.html#ts6" target="_blank">http://www.linux-usb.org/FAQ.html#ts6</a><br>
<br>
Have you tried disabling in bios everything you don't use - maybe sound card, wifi etc. to free some IRQ's?<br>
<br>
I run kernel 2.6.33.4-smp - just in case it helps.<br>
<br>
Let me know if you need any other info. If you find a final solution - I would be curious to know - just in case I will stumble over this problem.<br>
<br>
It wouldn't be a bad idea to build a script which grep's lsusb output - and run it through cron maybe every 10 minutes - to try and determine more precisely when does the U100 stop being recognised. Then you can look through the logs to see if there is anything else happening in the system around the same time.<br>
<br>
Sebastian<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
<br>
Regards,<br>
Bruce<br>
<br>
<br>
On Sat, Jan 1, 2011 at 6:57 PM, Sebastian <<a href="mailto:shop@open-t.co.uk" target="_blank">shop@open-t.co.uk</a><br></div><div><div></div><div class="h5">
<mailto:<a href="mailto:shop@open-t.co.uk" target="_blank">shop@open-t.co.uk</a>>> wrote:<br>
<br>
Hi Bruce,<br>
<br>
<br>
On 12/28/2010 10:51 PM, Bruce B wrote:<br>
<br>
Thanks for the input. I can not replicate the situation as it<br>
happens<br>
randomely or maybe over the weekend. However I have sent you all the<br>
requested command and logs in a separate e-mail for your<br>
analyzes. The<br>
only thing that stood out at me was the output of "lsusb -v" at<br>
the very<br>
end where it timed out.<br>
<br>
Since all lines didn't work I am to assume that both module went<br>
down<br>
but per my diagnoses with "hwprobe" I could see one unit<br>
connected and<br>
the other was not when the problem happened. Simply<br>
connecting/disconnecting that unit or connecting it to another port<br>
solved the problem and it showed up in "hwprobe"<br>
<br>
This is an Acer Aspire Revo mini PC. I am wondering if the U100s<br>
draw<br>
too much power? The only other USB connected device is the thumb<br>
size<br>
wireless connector for the keyboard.<br>
<br>
Acer computer:<br>
<a href="http://reviews.cnet.com/desktops/acer-aspire-revo-ar1600/4505-3118_7-33777218.html" target="_blank">http://reviews.cnet.com/desktops/acer-aspire-revo-ar1600/4505-3118_7-33777218.html</a><br>
<br>
<br>
Don't know if this will help - but I will butt in with what I have :-)<br>
<br>
I've been using a Sangoma U100 adapter for about 2 years now. It is<br>
connected to a Compaq V2120 laptop (Celeron M 1.4GHz processor)<br>
which serves as my home server. It is actually the main reason I<br>
went for the U100 - as I couldn't add a PCI or PCIe card to a laptop<br>
to get the FXO ports I needed. I have to say I really like the U100<br>
- I believe it is the only low(ish) cost USB based FXO interface on<br>
the market.<br>
<br>
I have had occasional problems with it. I remember it used to just<br>
stop working - and the lights would start flashing. If I remember<br>
correctly - I went to Sangoma's website and downloaded the latest<br>
wanpipe drivers, compiled and installed them - and everything was ok<br>
after that. At the moment I'm running Asterisk 1.6.2.9 and wanpipe<br>
3.5.11. I can't remember what version of wanpipe was giving<br>
problems, I'm afraid.<br>
<br>
I also found that mine doesn't really like to be hot-plugged - it<br>
just freezes the system with strange characters on the screen. But<br>
that was a while ago. Since I've learned it's foibles - it must be<br>
at least one year since I had to look at it.<br>
<br>
Sebastian<br>
<br>
<br>
<br>
Looking forward to your analysis.<br>
<br>
Regards,<br>
Bruce<br>
<br>
On Tue, Dec 28, 2010 at 3:58 PM, Moises Silva<br>
<<a href="mailto:moises.silva@gmail.com" target="_blank">moises.silva@gmail.com</a> <mailto:<a href="mailto:moises.silva@gmail.com" target="_blank">moises.silva@gmail.com</a>><br></div></div>
<mailto:<a href="mailto:moises.silva@gmail.com" target="_blank">moises.silva@gmail.com</a> <mailto:<a href="mailto:moises.silva@gmail.com" target="_blank">moises.silva@gmail.com</a>>>><div class="im">
<br>
wrote:<br>
<br>
On Tue, Dec 28, 2010 at 11:33 AM, Bruce B<br>
<<a href="mailto:bruceb444@gmail.com" target="_blank">bruceb444@gmail.com</a> <mailto:<a href="mailto:bruceb444@gmail.com" target="_blank">bruceb444@gmail.com</a>><br></div><div class="im">
<mailto:<a href="mailto:bruceb444@gmail.com" target="_blank">bruceb444@gmail.com</a> <mailto:<a href="mailto:bruceb444@gmail.com" target="_blank">bruceb444@gmail.com</a>>>> wrote:<br>
<br>
<br>
I appreciate your feedback and let me know what info I<br>
can post<br>
here that may help resolve the issue (such as output<br>
from dmesg<br>
or lspci?).<br>
<br>
<br>
Hi Bruce,<br>
<br>
The following would be useful for starters:<br>
<br>
1. cat /etc/wanpipe/*.conf<br>
<br>
2. ifconfig -a (from a working and non-working situation)<br>
<br>
3. lspci -v and lsusb -v (from a working and non-working<br>
situation)<br>
<br>
4. wanrouter hwprobe verbose (from a working and non-working<br>
situation)<br>
<br>
5. /var/log/messages (near the date the problem happened)<br>
<br>
Moises Silva<br>
Senior Software Engineer<br>
Sangoma Technologies Inc. | 100 Renfrew Drive, Suite 100,<br>
Markham ON<br>
L3R 9R6 Canada<br>
t. 1 905 474 1990 x128 | e. <a href="mailto:moy@sangoma.com" target="_blank">moy@sangoma.com</a><br></div>
<mailto:<a href="mailto:moy@sangoma.com" target="_blank">moy@sangoma.com</a>> <mailto:<a href="mailto:moy@sangoma.com" target="_blank">moy@sangoma.com</a><div><div></div><div class="h5"><br>
<mailto:<a href="mailto:moy@sangoma.com" target="_blank">moy@sangoma.com</a>>><br>
<br>
<br>
--<br>
<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by<br>
<a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar<br>
every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
<br>
<br>
<br>
<br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by<br>
<a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar every<br>
Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
<br>
<br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
<br>
<br>
<br>
<br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</div></div></blockquote><div><div></div><div class="h5">
<br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</div></div></blockquote></div><br></div>