Quote:
Originally Posted by Greenfuse
We might learn more from dmesg. Try switching the modem off for a few seconds, then back on again (or possibly even try unplugging it from the serial port). When you have done this type the following command in a terminal.
With luck we might see what node is assigned to the modem when the hotplug daemon picks it up.
Kppp can be a bit of a pig at times. Another angle that might be worth trying is using the gnome dialup utility (can't remember what it is called but you should find it somewhere in FC6.) I think it is a frontend for wvdial, which is tried and trusted linux software.
|
Greenfuse, it is internal modem, not external,I ty ScanModem from Linmodems.org, the following result shows:
-------------------------- System information ----------------------------
CPU=i686, Fedora Core release 6 (Zod)
Kernel
Linux version 2.6.18-1.2798.fc6xen (brewbuilder@hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)) #1 SMP Mon Oct 16 15:11:19 EDT 2006
scanModem update of: 2007_Jan_22
USB modem not detected by lsusb
Modem or host audio card candidates have firmware information:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
02:0d.0 12b9:1008 12b9:00ad Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610
Modem interrupt assignment and sharing:
--- Bootup diagnositcs for card in PCI slot 02:0d.0 ----
=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===
For candidate modem in PCI bus: 02:0d.0
Class 0700: 12b9:1008 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610
Primary PCI_id 12b9:1008
Support type needed or chipset: USrobotics.serial
Vendor 10b7 3COM Inc. purchased the vendor 12b9 US Robotics modem technology.
Their winmodems have no Linux support. Their controller chipset modems
are supported by the Linux serial drivers.
The PCI id 12b9:1008 modem is Supported.
PCI ID Name Support status
-------------------------------------------------------------------------------
10b7:1006 3COM 0038TA AC101 - TF Mini-PCI winmodem, not supported
10b7:1007 3COM 3C556 V.90 Mini-PCI winmodem, not supported
12b9:1006 US Robotics 3cp803598 Voice winmodem, not supported
12b9:1007 US Robotics ERL3263A-0 DF GWPCI PC99 winmodem, not supported
12b9:0062 US Robotics erk41926a-0.6 usr 56k serial driver supported
12b9:1008 US Robotics 3cp803598 serial driver supported
wvdialconf wvtest , should detect the modem. Read Testing.txt
====== end 3COM section =======
but modem still not works.