I installed that, and did sudo modprobe ungrab-winmodem. Should I have to do other stuff before to unload the 537 driver first and then reload ungrab-winmodem, and then reload the 537 driver? Now when I do wvdial it says "cannot open /dev/ttyS40: Nosuch file or directory." -----Original Message----- From: Antonio Olivares [mailto:olivares14031@xxxxxxxxx] Sent: Wednesday, July 04, 2012 11:51 AM To: Philippe Vouters Cc: Andrew Merczynski-Hait; Linmodems; Marvin Stodolsky Subject: Re: I am bothered by the serial driver - Can't SSH to your Ubuntu computer Dear Phillipe and/or Andrew, Have you installed ungrab-winmodem? If you need to clear the serial driver from interfering, install it and check again http://linmodems.technion.ac.il/packages/smartlink/ungrab-winmodem-20090716. tar.gz Regards, Antonio On Wed, Jul 4, 2012 at 10:46 AM, Philippe Vouters <philippe.vouters@xxxxxxxxxxx> wrote: > Andrew, > > The problem with the "serial" driver is that it is included into the > kernel and automicatically scans the PCI bus. It can't be blacklisted > unless rebuilding a kernel. This driver interferes with the 537ep > modem hence it likely displaying a NO DIALTONE. > > By the way did you boot the Ubuntu Rescue CD and could delete > /etc/init.d/537_boot ???? > > Yours truly, > > Philippe Vouters (Fontainebleau/France) > URL: http://vouters.dyndns.org/ > SIP: sip:Vouters@xxxxxxxxxxxxxxxx > > Le 04/07/2012 04:41, Andrew Merczynski-Hait a écrit : >> >> I'm really sorry for all this trouble. >> >> My computer went off a few times today, did you reboot it? Right now >> though it's on, but even though I appear to be connected to the >> internet, web pages are not displaying---Therefore you probably >> wouldn't be able to SSH. I will have to deal with this my tomorrow... >> I really don't know what this problem is. I already tried rebooting. >> (actually I came to the computer and it was prompting for the BIOS >> password, making me think you rebooted.) >> >> >> Update: As I am typing this my system halted, and displayed a long, long >> error message. The first line says: BUG: Unable to handle kernel NULL >> pointer dereference at 00000004. >> >> Later I see: Modules linked in intel537................... >> >> So the reboots were probably this error, not you. >> >> Summary: Now I have a kernel error message, causing the computer to crash >> repeatedly. I assume the modem is not working. You can't SSH anymore and >> it >> seems the internet isn't working. <sarcasm> Hoorah! </sarcasm>. >> >> I realize you are doing your best and appreciate your help/recommendations >> regarding the modem, and this issue, presumably caused by the modem. >> Thanks, >> >> Happy American Independence day! :) >> >> ~Andrew >> >> >
