PDA

View Full Version : Strange UMTS modem lockups


billlagr
2008-03-30, 08:53 PM CDT
Hi All
This is a bit of a strange one... I have had, and up until now, my mobile broadband connection working perfectly on both a Huawei E220 USB and a Novatel Merlin U660 PCMCIA modems. I use ither Vodafone Mobile Card Connect or UMTSMON to 'dial in' with. As stated previously, until very recently, the connection worked perfectly using any combination of the above hardware and diallers.
Now when I 'dial' in, the connection comes up and after between 10-15 seconds, the Gnome toolbars become unresponsive, including the menus, however the desktop items still work and any terminals open still work, as do menus brought up by right clicking. Moving and resizing windows still works as well. About 10-15 seconds after that, everything remaining goes unresponsive - desktop icons don't work, terminals become unresponsive, right menu no longer comes up, however the mouse pointer still moves fine.
This happens regardless of the modem, or choice of dialler, and happens when I am a normal user or logged in as root. Because of this I suspect the problem may be related to pppd (same problems with a USB or PCMCIA modem). The problem also occurs regardless of the kernel I boot with. (Can't remember specific versions ATM, but its the latest and the previous one, as I have had to boot into Winblows to post this :/)
System is F8 with all latest updates, and no exotic/3rd party modules. I did have the slmodem package for the inbuilt modem installed and the ATI proprietry drivers, but I have removed both of them and the problem still happens.
Anyone have any suggestions??

Thanks
Bill

joekrahn
2008-04-30, 01:55 PM CDT
Did any system software get updated at the time the problems started, especially the kernel? Sometimes a kernel module change can cause problems for certain hardware, and it may be an unrelated device due to IRQ sharing. My first guess would be to boot to a previous kernel, and also check if the kernel module drivers have options that might provide a work-around.

Also, I would try running top in a VT console, and switch to it before the X hang occurs.