Re: HDA Intel, Brazil Fedora Core release 6 (Zod)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, May 02, 2007 at 07:25:53PM +0300, Jacques Goldberg wrote:
> Fernando,
> What I wrote about not using minicom was based on about 7 years of 
> experience with winmodems.
> Ok, I am an ignorant, or at best an amateur: I never managed to start a 
> connection using minicom with such a modem.

  I'm an amateur too. ;)  My experience with minicom. just to test modem
dial out, is quite ok, even for winmodems.  My previous notebook (an HP
zv5000) had a Smart Modem too and worked without problem.

  Once I get modem dialing, and hopefully someone answering at the other
side, the connection/authentication is another step for wich I use others
tools to accomplish.


> I did not investigate why because minicom is just irrelevant for me.

  Ok, I uderstood something of this kind.   Being as neewbie as I am, I
decided to try 'wvdial', as you and others, sugested.  Who knows if there
wasn't some resource unavailable in minicom and present in wvdial ?  In
dubio pro réu ! (In doubt for defendant)  So I gave wvdial a try.
Unfortunately the result was the same as with minicom.   As I listed
in the previous message.


> 
> The messages which you quote
> 
> Fernando M. Roxo da Motta wrote:
> >On Wed, May 02, 2007 at 11:02:58AM +0300, Jacques Goldberg wrote:
> >>As Marv says, you should use wvdial to debug your connection.
> >>With minicom you cannot connect to the Internet, even not login to your 
> >>ISP, just see (perhaps) that the modem works.
> >
> >  I'm not having any problem to login to my ISP, I just can't make the the
> >modem dial out.   That is the reason to use minicom, I'm trying the modem
> >first.   I guess that all neccessary configurations, programs and the such
> >for ISP authentication should be correct, as it was working before in my
> >previous notebook.   (Yes, that was a Smart Link modem too)
> >
> >
> >>If you insist using minicom, which we strongly discourage, you MUST have 
> >>X3 added to the modem initialization string.
> >>
> >
> >  That was my fault !   You're right, and that was what I used in my
> >tests, as all texts say "do no test carrier presence", and even because
> >most of the time I just have no line connected.  No, the line connection
> >does not change anything.
> >
> >  The problem is that it doesn't matter if I use 'wvdial', 'minicom' or
> >what else we imagine, doesn't matter if I ask to check the carrier or not,
> >doesn't matter if I ask for "no wait" (X3) or not, doesn't matter if the
> >line is connected or not,  every single try gives exactly the same result:
> >
> >application: NO CARRIER
> >             ERROR
> >
> >slmodemd:    error: cannot setup hw params for playback: Invalid argument
> >
> >hda-intel:   invalid format_val, rate=9600, ch=1, format=2
> >
> >
> >   Just for the records, the error messages above came from a try with
> >'wvdial' with a config that reads :
> >
> >=====================8<------- cut here ------------------------------
> >[Dialer Defaults]
> ># lines beginning with # are Comments, not read by wvdial
> >Modem = /dev/ttySL0
> >Baud = 115200
> >Init1 = ATZ
> >Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
> >## if there is problem with dial tone acquisition, add into the above line:
> >#    X3 meaning "dial without waiting"
> >## for some Internet Provides, there may be problems with the new V92 mode 
> >codes
> ># This can be suppresses with an:
> ># Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=90
> >## Within Italy it is sometimes necessary to even force a slower mode
> ># ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=34
> ># This mode is also useful for PBX dialout lines.
> >ISDN = 0
> >Modem Type = Analog Modem
> ># edit in your IP's phone number below.
> >Phone = 9999-9999
> ># Do not use - or spaceds in the Phone = line
> ># Introducing a pause with a , is sometimes necessary with hotel/company
> ># switchb
> ># Phone = 8,3334445555 or 8,,,3334445555 for s 3 second pause
> >Username = blah
> ># for MSN.net, use instead
> >#  Username = MSN/Your_Login_Name
> >Password = bleh
> ># if not using the SmartLink slmodemd, comment out with # the following
> ># line.
> >Carrier Check = no
> >=====================8<------- cut here ------------------------------
> >
> >  And the output was :
> >
> >=====================8<------- cut here ------------------------------
> ># wvdial 
> >--> WvDial: Internet dialer version 1.54.0
> >--> Cannot get information for serial port.
> >--> Initializing modem.
> >--> Sending: ATZ
> >ATZ
> >OK
> >--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
> >ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
> >OK
> >--> Modem initialized.
> >--> Sending: ATDT9999-9999
> >--> Waiting for carrier.
> >ATDT9999-9999
> >NO CARRIER
> >ERROR
> >--> No Carrier!  Trying again.
> >--> Sending: ATDT9999-9999
> >--> Waiting for carrier.
> >ATDT9999-9999
> >NO CARRIER
> >ERROR
> >--> No Carrier!  Trying again.
> >--> Sending: ATDT9999-9999
> >--> Waiting for carrier.
> >ATDT9999-9999
> >NO CARRIER
> >ERROR
> >--> No Carrier!  Trying again.
> >
> >And so forth "ad nauseam".
> >=====================8<------- cut here ------------------------------
> >
> >  For each "NO CARRIER/ERROR" I have a corresponding message "error:
> >cannot setup hw params for playback: Invalid argument" in the 'slmodemd'
> >output and the corresponding "invalid format_val, rate=9600, ch=1,
> >format=2" in the syslog/dmesg.
> >
> >
> >  Thank you for your attention.
> >
> >
> >>Jacques
> >>
> >>Fernando M. Roxo da Motta wrote:
> >>> Hi all,
> >>>
> >>>
> >>> I'm sending attached the file 'ModemData.txt', as requested by it.
> >>>
> >>>(Note: the suggested subject "SomeName, ..." is not clear, my name ?, my
> >>>machine name?, the modem name ?;)
> >>>
> >>> This is an Acer TravelMate 8210-6597 (Intel Core 2 Duo T7200 2 GHz, 2GiB
> >>>ram).
> >>>
> >>> I've tried the package "slmodem-alsa-2.9.11-1.lvn5" (for FC5, I know,
> >>>but it loaded anyway), the "SLMODEMD.gcc4.1.tar.gz"  (as suggested by
> >>>"ModemData.txt" and "YourSystem.txt" files) and, finally, the
> >>>"slmodem-2.9.11-20070427.tar.gz".   All produced the same result.
> >>>
> >>> The daemon 'slmodemd' loaded with rhe following setup :
> >>>
> >>>====================8<------ cut here --------------------------
> >>>#/etc/sysconfig/slmodemd
> >>>#modem device, default /dev/slamr0,
> >>>#for USB take /dev/slusb0 for example 
> >>>#SLMODEMD_DEVICE=/dev/slamr0
> >>>#for Alsa support with older software should be "hw:n"
> >>>#for ATI chipset "modem:n" is mandatory
> >>>SLMODEMD_DEVICE="hw:0,6"
> >>>
> >>>#Your country, try "slmodemd --countrylist"
> >>>SLMODEMD_COUNTRY=BRAZIL
> >>>
> >>>#config Alsa support
> >>>SLMODEMD_OPTS="--alsa"
> >>>
> >>>#config Alsa support debug use (e.g.) interactively :
> >>>#slmodemd  -c BRAZIL --alsa --debug=2 --log  hw:0,6
> >>>====================8<------ cut here --------------------------
> >>>
> >>> I'm using the 'minicom' to test the modem, and the results were the
> >>>same as those with 'wvdial'.   The modem answers to ATI[0-7] giving an
> >>>error for ATI8 :
> >>>
> >>>
> >>>====================8<------ cut here --------------------------
> >>>AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0                     
> >>>OK                                                   
> >>>ati0                                                 
> >>>SmartLink Soft Modem                                 
> >>>OK
> >>>ati1
> >>>SmartLink Soft Modem, 2.9.11
> >>>Smart Link Ltd.
> >>>OK
> >>>ati2
> >>>SmartLink Soft Modem, 2.9.11
> >>>Smart Link Ltd.
> >>>OK
> >>>ati3
> >>>hw:0,6
> >>>alsa modem driver
> >>>OK
> >>>ati4
> >>>s00=000 s01=000 s02=043 s03=013 s04=010 s05=008 s06=002 s07=045 
> >>>s08=002 s09=006 s10=007 s11=100 s12=050 s13=001 s14=000 s15=001 
> >>>s16=001 s17=000 s18=000 s19=000 s20=000 s21=000 s22=000 s23=000 
> >>>
> >>>OK
> >>>ati5
> >>>Stored Profile 0:
> >>>OK
> >>>ati6
> >>>Stored Profile 1:
> >>>OK
> >>>ati7
> >>>Country: BRAZIL
> >>>OK
> >>>ati8
> >>>ERROR
> >>>====================8<------ cut here --------------------------
> >>>
> >>> When I try to dial anything it complains :
> >>>
> >>>atdt 222222222
> >>>NO CARRIER
> >>>ERROR
> >>>
> >>>
> >>> Running interactively the daemon I get :
> >>>
> >>>====================8<------ cut here --------------------------
> >>># slmodemd  -c BRAZIL --alsa --debug=2 --log  hw:0,6
> >>>SmartLink Soft Modem: version 2.9.11 Apr 30 2007 17:32:58
> >>><879.831452> SmartLink Soft Modem: version 2.9.11 Apr 30 2007 17:32:58
> >>><879.831560> hw:0,6: startup modem...
> >>><879.831688> hw:0,6: update termios...
> >>>symbolic link `/dev/ttySL0' -> `/dev/pts/1' created.
> >>>modem `hw:0,6' created. TTY is `/dev/pts/1'
> >>><879.832179> open file: /var/lib/slmodem/data.hw:0,6...
> >>><879.832909> main: rt applyed: SCHED_FIFO, pri 99
> >>>Use `/dev/ttySL0' as modem device, Ctrl+C for termination.
> >>><909.159858> main: termios changed.         <<=====  here I start minicom
> >>><909.159924> hw:0,6: update termios...
> >>><910.161112> hw:0,6: run cmd: ATS7=45S0=0L1V1X4&c1E1Q0
> >>><910.161174> main: alsa_ioctl: cmd 8, arg 0...
> >>><910.161198> hw:0,6: modem report result: 0 (OK)
> >>><972.659639> hw:0,6: run cmd: atdt2222222   <<=====  try atdt 2222222
> >>><972.659716> hw:0,6: modem dial: t2222222...
> >>><972.659736> hw:0,6: modem_dial_start...
> >>><972.660447> hw:0,6: modem_start..
> >>><972.660465> hw:0,6: modem set state: 1 --> 2...
> >>><972.660482> hw:0,6: new state: DP_ESTAB
> >>><972.660499> main: alsa_ioctl: cmd 8, arg 1...
> >>><972.660517> hw:0,6: modem set hook: 0 --> 1...
> >>><972.660535> main: alsa_ioctl: cmd 2, arg 1...
> >>><972.662356> main: alsa_ioctl: cmd 11, arg 0...
> >>><972.662438> main: alsa_ioctl: cmd 4, arg 2580...
> >>><972.662516> main: alsa_ioctl: cmd 7, arg 30...
> >>><972.662537> main: alsa_start...
> >>>error: cannot setup hw params for playback: Invalid argument
> >>><972.662736> err: hw:0,6: modem start = -22: cannot start device.
> >>><972.662758> hw:0,6: modem_stop..
> >>><972.662775> hw:0,6: modem set hook: 1 --> 0...
> >>><972.662792> main: alsa_ioctl: cmd 2, arg 0...
> >>><972.664363> main: alsa_ioctl: cmd 8, arg 0...
> >>><972.664473> hw:0,6: modem set state: 2 --> 1...
> >>><972.664491> hw:0,6: new state: MODEM_IDLE
> >>><972.664509> hw:0,6: modem report result: 3 (NO CARRIER)
> >>><972.664535> hw:0,6: modem report result: 4 (ERROR)
> >>><407.466946> hw:0,6: run cmd: atdt          <<==== just ATDT, no number
> >>><407.467071> hw:0,6: modem dial: t...
> >>><407.467093> hw:0,6: modem_dial_start...
> >>><407.467827> hw:0,6: modem_start..
> >>><407.467845> hw:0,6: modem set state: 1 --> 2...
> >>><407.467918> hw:0,6: new state: DP_ESTAB
> >>><407.467937> main: alsa_ioctl: cmd 8, arg 1...
> >>><407.467956> hw:0,6: modem set hook: 0 --> 1...
> >>><407.467974> main: alsa_ioctl: cmd 2, arg 1...
> >>><407.469912> main: alsa_ioctl: cmd 11, arg 0...
> >>><407.469996> main: alsa_ioctl: cmd 4, arg 2580...
> >>><407.470017> main: alsa_ioctl: cmd 7, arg 30...
> >>><407.470035> main: alsa_start...
> >>>error: cannot setup hw params for playback: Invalid argument
> >>><407.471978> err: hw:0,6: modem start = -22: cannot start device.
> >>><407.472005> hw:0,6: modem_stop..
> >>><407.472023> hw:0,6: modem set hook: 1 --> 0...
> >>><407.472041> main: alsa_ioctl: cmd 2, arg 0...
> >>><407.473904> main: alsa_ioctl: cmd 8, arg 0...
> >>><407.474369> hw:0,6: modem set state: 2 --> 1...
> >>><407.474387> hw:0,6: new state: MODEM_IDLE
> >>><407.474405> hw:0,6: modem report result: 3 (NO CARRIER)
> >>><407.474431> hw:0,6: modem report result: 4 (ERROR)
> >>>====================8<------ cut here --------------------------
> >>>
> >>>
> >>> All errors above generated in syslog (or dmesg if you prefer) the 
> >>> message :
> >>>
> >>>hda-intel: invalid format_val, rate=9600, ch=1, format=2
> >>>
> >>> Just as a guess, it looks like the module "snd_hda_intel" is complaining
> >>>about the format (or contents) of some information.
> >>>
> >>> By the way, the "snd_*" modules loaded are :
> >>>
> >>>====================8<------ cut here --------------------------
> >>># lsmod|grep snd
> >>>snd_hda_intel          30817  3 
> >>>snd_hda_codec         204353  1 snd_hda_intel
> >>>snd_seq_dummy          12613  0 
> >>>snd_seq_oss            41153  0 
> >>>snd_seq_midi_event     16705  1 snd_seq_oss
> >>>snd_seq                64225  5
> >>>snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
> >>>snd_seq_device         17109  3 snd_seq_dummy,snd_seq_oss,snd_seq
> >>>snd_pcm_oss            53345  0 
> >>>snd_mixer_oss          25537  1 snd_pcm_oss
> >>>snd_pcm                93641  5 snd_hda_intel,snd_hda_codec,snd_pcm_oss
> >>>snd_timer              32969  2 snd_seq,snd_pcm
> >>>snd                    72553  13
> >>>snd_hda_intel,snd_hda_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
> >>>soundcore              17505  1 snd
> >>>snd_page_alloc         18897  2 snd_hda_intel,snd_pcm
> >>>====================8<------ cut here --------------------------
> >>>
> >>>
> >>> I hope these informations can help in anyway.   If any extra test
> >>>becomes neccesary, please, tell me.
> >>>
> >>>
> >>>
> >>>
> >>> Roxo
> >>>
> >>>
> >>>
> >>>------------------------------------------------------------------------
> >>>
> >>>Only plain text email is forwarded by the  DISCUSS@xxxxxxxxxxxxx List 
> >>>Server.
> >>>Do use the following as the email Subject Line:
> >>>          SomeName, YourCountry Fedora Core release 6 (Zod)
> >>>Kernel  kernel 2.6.20-1.2944.fc6 
> >>>This will alert cogent experts, and  distinguish cases in the Archives.
> >>>YourCountry will enable Country Code guidance.
> >>>Occassionally responses are blocked by an Internet Provider mail filters.
> >>>So in a day, also check the Archived responses at 
> >>>http://www.linmodems.org .
> >>>Local Linux experts can be found through: 
> >>>http://www.linux.org/groups/index.html
> >>>--------------------------  System information 
> >>>----------------------------
> >>>CPU=x86_64,  Fedora Core release 6 (Zod)
> >>>Kernel 
> >>>Linux version 2.6.20-1.2944.fc6 
> >>>(brewbuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.1 20070105 
> >>>(Red Hat 4.1.1-51)) #1 SMP Tue Apr 10 17:46:00 EDT 2007
> >>>scanModem update of:  2007_April_23
> >>>
> >>>
> >>>USB modem not detected by lsusb
> >>>
> >>>Modem or host audio card candidates have firmware information:
> >>>
> >>>PCI slot	PCI ID		SubsystemID	Name
> >>>----------	---------	---------	--------------
> >>>00:1b.0	8086:27d8	1025:0092	Audio device: Intel 
> >>>Corporation 82801G 
> >>>Modem interrupt assignment and sharing: 
> >>>22:        250       1960   IO-APIC-fasteoi   HDA Intel
> >>>
> >>>--- Bootup diagnositcs for card in PCI slot 00:1b.0 ----
> >>>ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 22
> >>>PCI: Setting latency timer of device 0000:00:1b.0 to 64
> >>>
> >>>=== Finished modem firmware and bootup diagnostics section. ===
> >>>=== Next deducing cogent software ===
> >>>
> >>>ALSAversion 1.0.14rc1
> >>>8086:27d8 is a High Definition Audio card, possibly hosting a soft modem.
> >>>
> >>>For candidate modem in PCI bus:  00:1b.0
> >>>  Class 0403: 8086:27d8 Audio device: Intel Corporation 82801G
> >>>     Primary PCI_id  8086:27d8
> >>>   Subsystem PCI_id  1025:0092 
> >>>   Softmodem codec or Vendor from diagnostics: 11c1, an AgereSystems 
> >>>   type.
> >>>                             from    Archives: 
> >>>                       
> >>>
> >>>This is a NEW softmodem case!  Please send the output ModemData.txt 
> >>>to DISCUSS@xxxxxxxxxxxxx , even if further assistance is not needed.
> >>>It will enrich the Archive and help others!
> >>>-------------------------------------------
> >>>Lacking a dsp (digital signal processing) chip, the modem is a software 
> >>>intensive or "softmodem" type. Its primary controller manages the 
> >>>traffic with the CPU. But the software needed is specified in the 
> >>>Subsystem.
> >>>-----------------------------------------
> >>>Support type needed or chipset:	slmodemd
> >>>
> >>>An ALSA (Advanced Linux Sound Architecture) modem driver:  snd-hda-intel
> >>>provides Low Level support enabling contact with the modem hardware.
> >>>For all BUT Conexant chip soft modems (using hsfmodem software)
> >>>complementary High Level support is through a Smartlink utility:  
> >>>slmodemd
> >>>
> >>>Download from http://linmodems.technion.ac.il/packages/smartlink/ 
> >>>the package SLMODEMD.gcc4.1.tar.gz having a compiled slmodemd. Unpack 
> >>>under Linux with:
> >>>	$ tar zxf SLMODEMD.gcc4.1.tar.gz
> >>>and read instructions therein. But briefly, the modem is setup with 
> >>>command:
> >>>	 slmodemd -c YOUR_COUNTRY --alsa hw:0,6 
> >>>reporting dynamic creation of ports:
> >>>	/dev/ttySL0 --> /dev/pts/N   , with N some number
> >>>Read Smartlink.txt and Modem/YourSystem.txt for follow through guidance.
> >>>
> >>>Already loaded into the kernel is snd-hda-intel and audio drivers it 
> >>>depends on,
> >>>displayed by:	lsmod | grep snd_hda_intel
> >>>Module                  Size  Used by
> >>>-------------------------------------
> >>>snd_hda_intel          30817  0 
> >>>snd_hda_codec         204353  1 snd_hda_intel
> >>>snd_pcm                93641  3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
> >>>snd                    72553  9 
> >>>snd_hda_intel,snd_hda_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
> >>>snd_page_alloc         18897  2 snd_hda_intel,snd_pcm
> >>>
> >>>
> >>>The diagnostic outputs for this softmodem section have their raw 
> >>>information in
> >>>folders and text files under /proc/asound/ which you can browse. The 
> >>>information
> >>>is from files:
> >>>	/proc/asound/pcm
> >>>-------------------------------
> >>>00-06: Si3054 Modem : Si3054 Modem : playback 1 : capture 1
> >>>00-02: ALC883 Analog : ALC883 Analog : capture 2
> >>>00-00: ALC883 Analog : ALC883 Analog : playback 1 : capture 2
> >>>
> >>>	/proc/asound/modules
> >>>-------------------------------
> >>>0 snd_hda_intel
> >>>	/proc/asound/card0/codec#1
> >>>-------------------------------
> >>>Codec: Generic 11c1 Si3054
> >>>Address: 1
> >>>Vendor Id: 0x11c13026
> >>>Subsystem Id: 0x11c13026
> >>>Revision Id: 0x100600
> >>>-------------------------------
> >>>Current support status of HDA cards is:
> >>> Vendor IDs  Chip maker     Support type 
> >>> ----------  ----------    -------------
> >>> 0x14f12bfa  Conexant      hsfmodem , not slmodemd compatible
> >>> 0x11c13026  AgereSystems  snd-hda-intel, slmodemd supported
> >>> 0x11c11040  AgereSystems      "             "     support not yet 
> >>> available.
> >>> 0x11c13055  AgereSystems      "             "    ,      "
> >>> 0x163c3055  Smartlink         "             "    ,      "
> >>> 0x163c3155    "               "             "    ,      "
> >>> 0x10573055  Motorola          "             "    ,      "
> >>> 0x10573155     "              "             "    ,      ""
> >>>as of October 2006.
> >>>
> >>>and from the command:
> >>>	aplay -l | grep -i modem
> >>>card 0: Intel [HDA Intel], device 6: Si3054 Modem [Si3054 Modem]
> >>>
> >>>----------------end Softmodem section --------------
> >>>
> >>>Writing Intel.txt
> >>>Writing Smartlink.txt
> >>>============ end Smartlink section =====================
> >>>
> >>>Completed candidate modem analyses.
> >>>
> >>>The base of the UDEV device file system is: /dev/.udev
> >>>
> >>>Versions adequately match for the compiler installed: 4.1.1
> >>>            and the compiler used in kernel assembly: 4.1.1
> >>>
> >>>Kernel-header resources needed for compiling are not manifestly ready!
> >>>
> >>>If compiling is necessary packages must be installed, providing:
> >>>	 kernel-source-2.6.20-1.2944.fc6
> >>>
> >>>
> >>>Checking pppd properties:
> >>>	-r-xr-xr-x 1 root root 337264 Dez  1 10:51 /usr/sbin/pppd
> >>>
> >>>In case of an "error 17" "serial loopback" problem, see:
> >>>   http://phep2.technion.ac.il/linmodems/archive-sixth/msg02637.html
> >>>
> >>>To enable dialout without Root permission do:
> >>>	$ su - root  (not for Ubuntu)
> >>>        chmod a+x /usr/sbin/pppd
> >>>or under Ubuntu related Linuxes
> >>>	 chmod a+x /usr/sbin/pppd
> >>>
> >>>Checking settings of:	/etc/ppp/options
> >>>lock
> >>>
> >>>In case of a message like:
> >>>  Warning: Could not modify /etc/ppp/pap-secrets: Permission denied
> >>>see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html
> >>>
> >>>Read Modem/YourSystem.txt concerning other COMM channels: dummy0 eth0
> >>>Which can interfere with Browser naviagation.
> >>>
> >>>Don't worry about the following, it is for the experts
> >>>should trouble shooting be necessary.
> >>>==========================================================
> >>>
> >>>Checking for modem support lines:
> >>>--------------------------------------
> >>>    /device/modem symbolic link:   
> >>>slmodemd created symbolic link /dev/ttySL0:  
> >>>    Within /etc/udev/ files:
> >>>/etc/udev/rules.d/50-udev.rules:KERNEL=="modems/mwave*",        
> >>>NAME="%k", GROUP="uucp", MODE="0660"
> >>>    Within /etc/modprobe.conf files:
> >>>
> >>>    Within any ancient /etc/devfs files:
> >>>
> >>>    Within ancient kernel 2.4.n /etc/module.conf files:
> >>>
> >>>--------- end modem support lines --------
> >>>
> >
> >
> >  Roxo
> >


  Roxo

-- 
---------------- Non luctari, ludare -------------------+ WYSIWYG Editor ?
Fernando M. Roxo da Motta <roxo@xxxxxxxx>               |  VI !!
Except where explicitly stated I speak on my own behalf.| I see text,
      ( Usuário Linux registrado #39505 )               | I get text !


[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux