Great; something has changed!
The modem is not yet recognised, but the error you showed me is no more there:
Scanning your serial ports for a modem.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S2 S3
Sorry, no modem was detected! Is it in use by another program?
Then I put the ethernet off and report as follows:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
So nothing more about the eth0!
Unfortunately the wvdialconf is not making my modem work anyway...
I tried with GNOME PPP as well... and I report a strange thing: when I
go to the panel to choose the port number, the program allows me to
"authomatically scan" for a modem. It tries for a dozen of seconds and
then report that no modem was found. The curious thing is that -
during the scan time - the red lights on the modem start to move and
light on and off... so I believe that the datas are reaching the
modem, but the system is in any way not able to "recognise" it...
It is quite strange, because if the PC or the modem had not worked, we
wouldn't have seen the red lights moving...
I hope that it could help you in any way...
Thank you,
Matteo
2007/12/15, Matteo Mambretti <teo2257@xxxxxxxxx>:
> Marvin,
> when I make
> $ sudo ifconfig eth0 down
> the ethernet connection goes down and then authomatically reconnects. But the
> $ ifconfig
> always gives the same results.
> (of course NOW I have an ethernet connection, but I'm trying to set
> this modem running because this PC needs to be placed in a town where
> the ADSL is not working)
>
> The$ sudo wvdialconf /etc/wvdial.conf
> always tells me that no modem is found:
>
> Scanning your serial ports for a modem.
>
> Modem Port Scan<*1>: Scanning ttySHSF0 first, /dev/modem is a link to it.
> Modem Port Scan<*1>: SHSF0
> ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
> ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
> ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
> ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
> ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
> ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
> Modem Port Scan<*1>: S2 S3 SHSF1 SHSF2 SHSF3 SHSF4 SHSF5
> Modem Port Scan<*1>: SHSF6 SHSF7
> Sorry, no modem was detected! Is it in use by another program?
> Did you configure it properly with setserial?
>
> I installed setserial, but I do not know how to use it, and if it
> could be helpful for me...
> Thank I made
> $ grep SERIAL /boot/config*
> and the following is the result:
>
> /boot/config-2.6.20-16-generic:CONFIG_PARPORT_SERIAL=m
> /boot/config-2.6.20-16-generic:CONFIG_MOUSE_SERIAL=m
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_NONSTANDARD=y
> /boot/config-2.6.20-16-generic:# CONFIG_ESPSERIAL is not set
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_8250=y
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_8250_CONSOLE=y
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_8250_PCI=y
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_8250_PNP=y
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_8250_CS=m
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_8250_NR_UARTS=48
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_8250_RUNTIME_UARTS=4
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_8250_EXTENDED=y
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_8250_MANY_PORTS=y
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_8250_FOURPORT=m
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_8250_ACCENT=m
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_8250_BOCA=m
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_8250_EXAR_ST16C554=m
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_8250_HUB6=m
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_8250_SHARE_IRQ=y
> /boot/config-2.6.20-16-generic:# CONFIG_SERIAL_8250_DETECT_IRQ is not set
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_8250_RSA=y
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_8250_MCA=m
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_CORE=y
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_CORE_CONSOLE=y
> /boot/config-2.6.20-16-generic:CONFIG_SERIAL_JSM=m
> /boot/config-2.6.20-16-generic:CONFIG_SND_SERIAL_U16550=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_GENERIC=y
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_AIRCABLE=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_AIRPRIME=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_ARK3116=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_BELKIN=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_WHITEHEAT=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_CP2101=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_CYPRESS_M8=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_EMPEG=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_FTDI_SIO=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_FUNSOFT=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_VISOR=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_IPAQ=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_IR=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_EDGEPORT=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_EDGEPORT_TI=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_GARMIN=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_IPW=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_KEYSPAN_PDA=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_KEYSPAN=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_KEYSPAN_MPR=y
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_KEYSPAN_USA28=y
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_KEYSPAN_USA28X=y
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_KEYSPAN_USA19=y
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_KEYSPAN_USA18X=y
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_KEYSPAN_USA19W=y
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_KEYSPAN_USA49W=y
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_KEYSPAN_USA49WLC=y
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_KLSI=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_KOBIL_SCT=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_MCT_U232=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_MOS7720=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_MOS7840=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_NAVMAN=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_PL2303=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_HP4X=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_SAFE=m
> /boot/config-2.6.20-16-generic:# CONFIG_USB_SERIAL_SAFE_PADDED is not set
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_SIERRAWIRELESS=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_TI=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_CYBERJACK=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_XIRCOM=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_OPTION=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_OMNINET=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_SERIAL_DEBUG=m
> /boot/config-2.6.20-16-generic:CONFIG_USB_G_SERIAL=m
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_8250=y
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_8250_CONSOLE=y
> /boot/config-2.6.22-14-generic:# CONFIG_SERIAL_8250_DETECT_IRQ is not set
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_8250_EXTENDED=y
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_8250_MANY_PORTS=y
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_8250_NR_UARTS=48
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_8250_PCI=y
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_8250_PNP=y
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_8250_RSA=y
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_8250_RUNTIME_UARTS=4
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_8250_SHARE_IRQ=y
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_CORE=y
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_CORE_CONSOLE=y
> /boot/config-2.6.22-14-generic:# CONFIG_ESPSERIAL is not set
> /boot/config-2.6.22-14-generic:CONFIG_MOUSE_SERIAL=m
> /boot/config-2.6.22-14-generic:CONFIG_PARPORT_SERIAL=m
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_8250_ACCENT=m
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_8250_BOCA=m
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_8250_CS=m
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_8250_EXAR_ST16C554=m
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_8250_FOURPORT=m
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_8250_HUB6=m
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_8250_MCA=m
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_JSM=m
> /boot/config-2.6.22-14-generic:CONFIG_SERIAL_NONSTANDARD=y
> /boot/config-2.6.22-14-generic:CONFIG_SND_SERIAL_U16550=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_G_SERIAL=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_AIRCABLE=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_AIRPRIME=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_ARK3116=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_BELKIN=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_CP2101=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_CYBERJACK=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_CYPRESS_M8=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_DEBUG=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_EDGEPORT=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_EDGEPORT_TI=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_EMPEG=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_FTDI_SIO=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_FUNSOFT=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_GARMIN=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_GENERIC=y
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_HP4X=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_IPAQ=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_IPW=m
> /boot/config-2.6.22-14-generic:# CONFIG_USB_SERIAL_IR is not set
> /boot/config-2.6.22-14-generic:# CONFIG_USB_SERIAL_KEYSPAN is not set
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_KEYSPAN_PDA=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_KLSI=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_KOBIL_SCT=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_MCT_U232=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_MOS7720=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_MOS7840=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_NAVMAN=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_OMNINET=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_OPTION=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_PL2303=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_SAFE=m
> /boot/config-2.6.22-14-generic:# CONFIG_USB_SERIAL_SAFE_PADDED is not set
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_SIERRAWIRELESS=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_TI=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_VISOR=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_WHITEHEAT=m
> /boot/config-2.6.22-14-generic:CONFIG_USB_SERIAL_XIRCOM=m
>
>
> Thank you for your patience and for your always so nice help...
> Matteo
>
>
>
>
> 2007/12/15, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>:
> > Matteo,
> >
> > The lo represents a standard loop back channel, supoprting all other
> > COMM channels, and
> > the eth0 an automated setup for ethernet usage.
> >
> > The ppp0 absense relates that nothing automated has setup/grabbed the
> > ppp0 channel,
> > which would have accounted for a failure of
> > $ sudo wvdialconf /etc/wvdial.conf
> >
> > On the chance that the eth0 channel may in some way be competing, try
> > $ sudo ifconfig eth0 down
> > To see the result
> > $ ifconfig
> > Then try again
> > $ sudo wvdialconf /etc/wvdial.conf
> >
> > Also what is the output from
> > $ grep SERIAL /boot/config*
> > which I expect will show that the serial driver support is compiled
> > into the boot kernel.
> >
> > MarvS
> >
> >
> > On Dec 15, 2007 4:16 AM, Matteo Mambretti <teo2257@xxxxxxxxx> wrote:
> > > The very strange thing is that... it neither seems to consider ppp0...
> > >
> > > eth0 Link encap:Ethernet HWaddr 00:0D:60:26:07:D9
> > > inet addr:192.168.0.8 Bcast:255.255.255.255 Mask:255.255.255.0
> > > inet6 addr: fe80::20d:60ff:fe26:7d9/64 Scope:Link
> > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > > RX packets:852 errors:0 dropped:0 overruns:0 frame:0
> > > TX packets:721 errors:0 dropped:0 overruns:0 carrier:0
> > > collisions:0 txqueuelen:100
> > > RX bytes:446000 (435.5 KB) TX bytes:282045 (275.4 KB)
> > > Base address:0x2000 Memory:e8100000-e8120000
> > >
> > > lo Link encap:Local Loopback
> > > inet addr:127.0.0.1 Mask:255.0.0.0
> > > inet6 addr: ::1/128 Scope:Host
> > > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > > collisions:0 txqueuelen:0
> > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> > >
> > > Isn't it quite strange...?
> > >
> > > Thank you,
> > > Matteo
> > >
> > > 2007/12/15, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>:
> > >
> > > > Matteo,
> > > >
> > > > Try
> > > > $ ifconfig
> > > > is there displayed an information block, with ppp0 on its left?
> > > >
> > > > If so, the device port may be blocked b some other program/utiliy. Do
> > > > $ sudo ifconfig ppp0 down
> > > > Check for the removal of the block with:
> > > > $ ifconfig
> > > >
> > > > Then try
> > > > $ sudo wvdialconf /etc/wvdial.conf
> > > >
> > > > MarvS
> > > >
> > > >
> > > > On Dec 14, 2007 3:28 PM, Matteo Mambretti <teo2257@xxxxxxxxx> wrote:
> > > > > Just to puntualize... when I made these commands the modem was
> > > > > plugged-in and switched on. So, theoretically speaking, the PC should
> > > > > have "seen" it.
> > > > > I can tell you something more: the device is for sure "working", as
> > > > > when I switch the modem on, the computer itself switches
> > > > > authomatically on... it is curious, but it is anyway a confirmation
> > > > > that the serial port is working and, in any way, receives the modem
> > > > > signals...
> > > > >
> > > > > Thank you again for an help...
> > > > > Matteo
> > > > >
> > > > > 2007/12/13, Matteo Mambretti <teo2257@xxxxxxxxx>:
> > > > >
> > > > > > Hi Marvin,
> > > > > > thank you as usual for your always very kind help.
> > > > > > Please find below the result of my queries:
> > > > > >
> > > > > > $ cat /proc/interrupts
> > > > > > CPU0
> > > > > > 0: 130 IO-APIC-edge timer
> > > > > > 1: 143 IO-APIC-edge i8042
> > > > > > 6: 5 IO-APIC-edge floppy
> > > > > > 7: 0 IO-APIC-edge parport0
> > > > > > 8: 3 IO-APIC-edge rtc
> > > > > > 9: 1 IO-APIC-fasteoi acpi
> > > > > > 12: 3518 IO-APIC-edge i8042
> > > > > > 14: 9174 IO-APIC-edge libata
> > > > > > 15: 0 IO-APIC-edge libata
> > > > > > 16: 9573 IO-APIC-fasteoi uhci_hcd:usb1, uhci_hcd:usb4,
> > > > > > eth0, i915@pci:0000:00:02.0
> > > > > > 17: 0 IO-APIC-fasteoi uhci_hcd:usb2
> > > > > > 18: 0 IO-APIC-fasteoi uhci_hcd:usb3
> > > > > > 19: 0 IO-APIC-fasteoi ehci_hcd:usb5
> > > > > > 20: 389 IO-APIC-fasteoi Intel ICH5
> > > > > > NMI: 0
> > > > > > LOC: 18720
> > > > > > ERR: 0
> > > > > > MIS: 0
> > > > > >
> > > > > > $ ls /
> > > > > > bin dev initrd lib mnt root sys var
> > > > > > boot etc initrd.img lost+found opt sbin tmp vmlinuz
> > > > > > cdrom home initrd.img.old media proc srv usr vmlinuz.old
> > > > > >
> > > > > > $ sudo modprobe 8250
> > > > > > FATAL: Module 8250 not found.
> > > > > >
> > > > > > I tried $ sudo modprobe 9573 as well, but with no result (always
> > > > > > module not found).
> > > > > >
> > > > > > I hope this will help you understanding what the problem can be...
> > > > > >
> > > > > > Thank you very much!!!
> > > > > > Matteo
> > > > > >
> > > > > > 2007/12/13, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>:
> > > > > > > Folks,
> > > > > > >
> > > > > > > Would someone check what the name of the serial port driver is?
> > > > > > > I thing it is simple 8250.ko , but I'm traveling with a MAC this week
> > > > > > >
> > > > > > > Matteo
> > > > > > >
> > > > > > > [ 16.474893] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports,
> > > > > > > IRQ sharing enabled
> > > > > > > [ 16.474992] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> > > > > > > [ 16.475205] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> > > > > > > [ 16.475958] 00:0c: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> > > > > > > [ 16.476269] 00:0d: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> > > > > > > -----
> > > > > > > The boot up testing of the serial ports seems OK
> > > > > > > Try again
> > > > > > > $ cat /proc/interrupts
> > > > > > > and be sure to include the / in the indicated places. you should
> > > > > > > also see proc in the output of
> > > > > > > $ ls /
> > > > > > > as it is a BASIC Linux virtual file system, relating ongoing processes
> > > > > > >
> > > > > > > Also try
> > > > > > > $ sudo modprobe 8250
> > > > > > > or whatever the driver name is reported to be. THen again
> > > > > > > $ sudo wvdialconf /etc/wvdial.conf
> > > > > > >
> > > > > > > MarvS
> > > > > > >
> > > > > > > On Dec 12, 2007 3:29 PM, Matteo Mambretti <teo2257@xxxxxxxxx> wrote:
> > > > > > > > Thank you!
> > > > > > > > Here you have the details, in the attached file!
> > > > > > > >
> > > > > > > > Best regards,
> > > > > > > > Matteo
> > > > > > > >
> > > > > > > > 2007/12/12, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>:
> > > > > > > >
> > > > > > > > > Matteo,
> > > > > > > > >
> > > > > > > > > It is unlikely that it is a Ubuntu problem perse,
> > > > > > > > > but rather some hardware resource conflict.
> > > > > > > > > Do
> > > > > > > > > $ dmesg > dmesg.txt
> > > > > > > > > and send us the dmesg.txt
> > > > > > > > >
> > > > > > > > > MarvS
> > > > > > > > >
> > > > > > > > > On Dec 12, 2007 6:50 AM, Matteo Mambretti <teo2257@xxxxxxxxx> wrote:
> > > > > > > > > > Dear all
> > > > > > > > > > it is a very strange situation... the Ubuntu system seems not able at
> > > > > > > > > > all to see the serial modem, and so it is not possible to work with
> > > > > > > > > > it. Can anybody of you help me please?
> > > > > > > > > >
> > > > > > > > > > Thank you,
> > > > > > > > > > Matteo
> > > > > > > > > >
> > > > > > > > > > 2007/12/10, Matteo Mambretti <teo2257@xxxxxxxxx>:
> > > > > > > > > >
> > > > > > > > > > > Dear all,
> > > > > > > > > > > I tried to do what was suggested, but at the command
> > > > > > > > > > > $ cat /proc/interrupts
> > > > > > > > > > > the reply was: "no such file or directory"...
> > > > > > > > > > >
> > > > > > > > > > > Thank you for a precious help!
> > > > > > > > > > > Matteo
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > 2007/12/10, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>:
> > > > > > > > > > > > Matteo,
> > > > > > > > > > > >
> > > > > > > > > > > > There may be interference between, the unnecessary hsf* drivers and
> > > > > > > > > > > > serial modem requirements.
> > > > > > > > > > > > Please do a complete uninstall. For your imput package:
> > > > > > > > > > > > hsfmodem_7.68.00.04full_k2.6.22_14_generic_ubuntu_i386.deb
> > > > > > > > > > > > get the installed name with
> > > > > > > > > > > > $ sudo apt-cache search hsfmodem
> > > > > > > > > > > > which will output the hsfmodem-installed-Name
> > > > > > > > > > > > Then do the uninstall with:
> > > > > > > > > > > > $ sudo apt-get remove hsfmodem-installed-Name
> > > > > > > > > > > > or just use the ADMIN tool "aptitude" to do the uninstall
> > > > > > > > > > > >
> > > > > > > > > > > > Afterwards reboot, and try again the
> > > > > > > > > > > > $ sudo wvdialconf /etc/wvdial.conf
> > > > > > > > > > > >
> > > > > > > > > > > > If the modem is not found,
> > > > > > > > > > > > send us the output of:
> > > > > > > > > > > > $ cat /proc/interrupts
> > > > > > > > > > > >
> > > > > > > > > > > > Please send to the List, Not me directly
> > > > > > > > > > > >
> > > > > > > > > > > > MarvS
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > $ sudo hsfmodem --help
> > > > > > > > > > > > to get the command syntax shown. Then the uninstall command. Something like:
> > > > > > > > > > > > $ sudo hsfmodem --
> > > > > > > > > > > >
> > > > > > > > > > > > On Dec 9, 2007 1:51 PM, Matteo Mambretti <teo2257@xxxxxxxxx> wrote:
> > > > > > > > > > > > > Marvin,
> > > > > > > > > > > > > unfortunately this seems to be the hardest problem... it isn't finding
> > > > > > > > > > > > > the serial modem!
> > > > > > > > > > > > >
> > > > > > > > > > > > > You can find below the error:
> > > > > > > > > > > > >
> > > > > > > > > > > > > Scanning your serial ports for a modem.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Modem Port Scan<*1>: Scanning ttySHSF0 first, /dev/modem is a link to it.
> > > > > > > > > > > > > Modem Port Scan<*1>: SHSF0
> > > > > > > > > > > > > ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
> > > > > > > > > > > > > ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
> > > > > > > > > > > > > ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
> > > > > > > > > > > > > ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
> > > > > > > > > > > > > ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
> > > > > > > > > > > > > ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
> > > > > > > > > > > > > Modem Port Scan<*1>: S2 S3 SHSF1 SHSF2 SHSF3 SHSF4 SHSF5
> > > > > > > > > > > > > Modem Port Scan<*1>: SHSF6 SHSF7
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Sorry, no modem was detected! Is it in use by another program?
> > > > > > > > > > > > > Did you configure it properly with setserial?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Please read the FAQ at http://open.nit.ca/wiki/?WvDial
> > > > > > > > > > > > >
> > > > > > > > > > > > > If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>.
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thank you!
> > > > > > > > > > > > > Matteo
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > 2007/12/9, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Matteo
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > For a serial port modem, just run
> > > > > > > > > > > > > > $ sudo wvdialconf /etc/wvdial.conf
> > > > > > > > > > > > > > which should report finding the modem.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Then
> > > > > > > > > > > > > > $ sudo gedit /etc/wvdial.conf
> > > > > > > > > > > > > > deleting the symbols ; < > and putting in your dialout info.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Then dialout with
> > > > > > > > > > > > > > $ sudo wvdial
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Dec 8, 2007 1:23 PM, Matteo Mambretti <teo2257@xxxxxxxxx> wrote:
> > > > > > > > > > > > > > > Hi Marvin,
> > > > > > > > > > > > > > > thank you very much for your very kind help!
> > > > > > > > > > > > > > > Unfortunately something seems still not ok... the Modem is connected
> > > > > > > > > > > > > > > to the serial port (I do not know if it is the 0 or the 1) and the
> > > > > > > > > > > > > > > power is on, but the PC seems not to recognise it.
> > > > > > > > > > > > > > > I am anyway attaching the report to the 3 suggested commands... I hope
> > > > > > > > > > > > > > > this would help you (as honestly it sounds quite ununderstandable for
> > > > > > > > > > > > > > > me...)
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Thank you in advance,
> > > > > > > > > > > > > > > Matteo
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > 2007/12/8, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Matteo,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Modem not detected though HDA card diagnostics, though not excluding
> > > > > > > > > > > > > > > > a possible Conexant modem chip impervious to ALSA diagnostics.
> > > > > > > > > > > > > > > > -----
> > > > > > > > > > > > > > > > is likely our case. From
> > > > > > > > > > > > > > > > http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
> > > > > > > > > > > > > > > > get the hsfmodem_7.68.00.04full_k2.6.22_14_generic_ubuntu_i386.deb.zip
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Under Linux unpack wth
> > > > > > > > > > > > > > > > $ unzip hsf*.zip
> > > > > > > > > > > > > > > > Start the install with:
> > > > > > > > > > > > > > > > $ sudo dpkg -i hsf*.deb
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > A reboot may be necessary for the modem can be detected with:
> > > > > > > > > > > > > > > > $ sudo wvdialconf /etc/wvdial.conf
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > If thus detected:
> > > > > > > > > > > > > > > > $ sudo gedit /etc/wvdial.conf
> > > > > > > > > > > > > > > > to delete the ; < > symbols and replace with you dialout info. The
> > > > > > > > > > > > > > > > dialout with:
> > > > > > > > > > > > > > > > $ sudo wvdial
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Please report back at this point.
> > > > > > > > > > > > > > > > Also we will need the ouputs of
> > > > > > > > > > > > > > > > $ lspci
> > > > > > > > > > > > > > > > $ lspci -nv
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > MarvS
> > > > > > > > > > > > > > > > scanModem maintainer
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > On Dec 8, 2007 5:32 AM, Matteo Mambretti <teo2257@xxxxxxxxx> wrote:
> > > > > > > > > > > > > > > > > Hi,
> > > > > > > > > > > > > > > > > can you help me?
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > I am a pretty new (Italian) Ubuntu user, and I have got no idea about
> > > > > > > > > > > > > > > > > what to do to install and make my 3Com/US Robotics modem run...
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Thank you!
> > > > > > > > > > > > > > > > > Matteo
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
