Newsgroup: it.comp.os.linux.iniziare
Titolo: [Lungo] Problema con modem Motorola

 is our expert on Motorola problems
 Achieving function with these drivers is often difficult.
 If you computer alternatively boots Linux and Microsoft OS,
 do a complete PowerOff before starting Linux.
 Otherwise there may be an error during following Motorola usage:
     SM_DisplayFatalError
 Some guidance for particular cases is:
 
http://linmodems.technion.ac.il/archive-fourth/msg01751.html
 
http://linmodems.technion.ac.il/archive-fourth/msg01749.html
 
http://linmodems.technion.ac.il/archive-fourth/msg01750.html
http://linmodems.org/cgi-bin/ezmlm-cgi?1:mss:13952:200405:enbjmmngagmdejkemacc
 
http://users.volja.net/kutulu/sm56.tar.gz
 There is a volunteer Motorola site: 
http://www.sm56.tk/
 The installation creates a driver sm56.o , the character devices
      /dev/motomem
      /dev/sm56
         with symbolic link  /dev/modem --> /dev/sm56
  the /etc/modules.conf lines:
      alias char-major-24 sm56
      options sm56 country=1
  and documentation in  usr/share/doc/HTML/en/sm56/  and "man sm56"
  An additional line in /etc/modules.conf
      alias /dev/modem /dev/sm56
  would beneficially aid driver autoloading, without which there may be
a failure of the wvdial functionality test:
  # /etc/wvdialconf /etc/wvdial.conf
 --------------------------------- End Motorola ------------------
  ======= PCI_ID checking completed ======
 Update=2005_Oct_23
A PCMCIA CardBus is not detected on this System.
For information on modem port creation under the UDEV device file
system see:
 
http://linmodems.technion.ac.il/archive-fourth/msg03299.html
  for
Conexnant modems
 
http://linmodems.technion.ac.il/archive-fifth/msg01177.html
  for
Lucent/Agere DSP modems
The following information blocks just query some ppp support items.
====================================================
   grep -rs ppp /etc/modprobe.*
-------------------------------------
/etc/modprobe.devfs:alias	/dev/ppp*		ppp_generic
-------------------------------------
  The following ppp related modules are likely unpacked during loading.
  If not they  should be unpacked by root with:
# gunzip PathTo/ModuleName.ko.gz
----------------------------------------
/lib/modules/2.6.12-12mdk/kernel/drivers/net/bsd_comp.ko.gz
/lib/modules/2.6.12-12mdk/kernel/drivers/net/ppp_async.ko.gz
/lib/modules/2.6.12-12mdk/kernel/drivers/net/ppp_generic.ko.gz
/lib/modules/2.6.12-12mdk/kernel/drivers/net/slhc.ko.gz
/lib/modules/2.6.12-12mdk/kernel/drivers/net/ppp_deflate.ko.gz
/lib/modules/2.6.12-12mdk/kernel/lib/zlib_deflate/zlib_deflate.ko.gz
 On most Systems, unpacking will driven by installing the wvdial.rpm
 and/or the package providing the KPPP graphical dialing interface.
----active COMM services are ------------
eth0      Link encap:Ethernet  HWaddr 00:0D:88:1A:01:AA
          inet6 addr: fe80::20d:88ff:fe1a:1aa/64 Scope:Link
This COMM mode should be closed before using the modem, or DNS services
may fail.
 Be sure to read the Ethernet section of Modem/YourModem.txt
A /dev/modem symbolic link is not present
 No devfsd.conf file found, indicated absense of the devfsd daemon
package
 for device file system (devfs) symbolic link support.
DEVFSD=
 ---- dmesg queries -------
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11 12 14 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11 12 14 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11 12 14 15) *0,
disabled.
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
audit: initializing netlink socket (disabled)
  Beginning with Fedora 2  kernel-2.6.6-1.427, kernel-headers needed
  for compiling drivers are provide at:
/lib/modules/kernel-version/build/
  Thus upgrading above kernel 2.6.5-1.358 to 2.6.6-* is Stongly
Recommended
  pppd version 2.4.2 may not be fully compatible with 2.6.8 kernel
releases.
  If an initial CONNECT is achieved without PPP being subsequently
established,
  drop back to a 2.4.1 version.  This has worked for PCTEL AMR modem
users,
  supported by the 
http://www.smlink.com
  slmodem software.
  Check pppd version with:
    pppd --version
  See  
http://linmodems.technion.ac.il/archive-fourth/msg03167.html
If the Mandrake installation disks do not include the dialer utility
wvdial.rpm,
then get instructions from
http://linmodems.technion.ac.il/archive-fifth/msg01480.html
-----------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------
ora...credo che la parte "succulenta" sia
<snip>
"There is a Bad IRQ=255 "
<snip>
Ora ho disabilitato la modalità PnP nel Bios, riavviato e rifatto lo
scanModem, ma non ne vuole sapere di riconoscere la scheda al suo posto
Da windozz vedo le seguenti impostazioni del modem
IRQ=19
intervallo I/O è B000-B0FF
invece in linux
#cat /proc/interrupt
           CPU0
  0:    1634172    IO-APIC-edge  timer
  1:       3422    IO-APIC-edge  i8042
  7:          2    IO-APIC-edge  parport0
  8:          1    IO-APIC-edge  rtc
  9:          0   IO-APIC-level  acpi
 12:     100536    IO-APIC-edge  i8042
 14:      43763    IO-APIC-edge  ide0
 15:      73515    IO-APIC-edge  ide1
 16:       6059   IO-APIC-level  uhci_hcd:usb2, EMU10K1
 17:          7   IO-APIC-level  ehci_hcd:usb5, bttv0, bt878
 18:          0   IO-APIC-level  eth0
 19:          0   IO-APIC-level  uhci_hcd:usb1
 21:         34   IO-APIC-level  uhci_hcd:usb3, uhci_hcd:usb4
NMI:          0
LOC:    1634044
ERR:          0
MIS:          0
è un modem interno <-> COM3 <-> ttyS2  (presumo...) e pertanto non
dovrebbe essere [fonte Modem-HowTo v0.38]
ttyS2 (COM3) indirizzo 0x3e8 IRQ 4
non ci capisco nulla...chi ha ragione???
probabilmente bisogna smanettare con setpci o le pciutils....avete
qualche idea?????????
come faccio a convertire l'I/O B000-B0FF  in un qualcosa di simile a
0x3e8 (non vorrei che fossero due modi di leggere la medesima
notazione)???
Grazie in anticipo
Max

 non ci capisco nulla...chi ha ragione???
Nessuno dei due.
E' un softmodem, ed e' il driver a decidere come viene visto dal
sistema, se come seriale numero tre o teletrasporto sul canale 2.
Hai provato a vedere qui?
http://www.motorola.com/softmodem/driver.htm
-- 
           |Save our planet!
    Ciao   |Save wildlife!
   roberto |For your E-MAIL use ONLY recycled Bytes  !!
           |roberto poggi   
rpo...@softhome.net

 
http://www.motorola.com/softmodem/driver.htm
#rpm -i sm56-06.05.02-2.mdk10_263-7.i586.rpm
poi reboooooto e non lo vedo ancora....


 poi reboooooto e non lo vedo ancora....
Beh, sicuro che si faccia cosi'?
uno straccio di documentazione su quel driver ci dovrebbe essere, come
minimo vedi con un modprobe se ottieni qualche risultato.
PS: Cosa intendi con "non lo vedo ancora"? chi dovrebbe vederlo e dove?
PS Al quadrato: togli tutto il superfluo, quando rispondi, come la firma
del post a cui stai rispondendo.
