Martin the /dev/modem --> /dev/ttyS0 link is created through bootup actions of the sl-modem-daemon scripts, useless on your System $ sudo apt-get remove sl-modem-daemon and the problem should disappear. MarvS On 10/11/07, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote: > Marvin, we need your expertise here. > Martin has correctly installed the HSF driver, and it works fine. > > There still is however a problem which I never met because I am not > using Ubuntu as you know. > > Martin would like to use the network control tool in the system settings > utility supplied with KED, to establish a modem connection, > The tool does not find the modem because ttySHSF0 is not in the list of > possibly available modems (this is how things look with my Gnome based > equivalent, probably identical to his). > Things go well if he re-creates a /dev/modem link to ttySHSF0, but the > link does not persist. > Every time he boots, the link is reset to /dev/ttySL0 . > He has already checked that the slmodem driver is not loaded. > Is there any feature in Ubuntu which bluntly creates a link to > /dev/ttySL0 at boot, overwriting the existing link to /dev/ttySHSF0 ? > > Thanks in advance - Jacques > > Martin Baumann wrote: > > eh bien, effectivement, on se comprendrait aussi! Meme si je m'exprime mieux > > en Anglais et ma langue maternelle est l'Allemand. > > > > In fact, sudo lsmod | grep sl returns a blank, nothing, just the command line. > > Which, presumably, indicates that the slmodem isn't loaded. > > > > So then I tried sudo lsmod without the filter, the output of which you see > > below. Nothing in there with an sl string. > > And so, just to prove I'm not dreaming, I added a ls -l /dev/modem, which > > brought up the inevitable ttySL0. Did you say something about screaming in > > your first mail? > > > > Ah well, time to call it a day! > > Good night > > Martin > > > > rdlc23@rdlc23hp:~$ sudo lsmod > > Module Size Used by > > i915 25472 3 > > drm 81044 4 i915 > > rfcomm 40856 0 > > l2cap 25856 5 rfcomm > > bluetooth 55908 4 rfcomm,l2cap > > ppdev 10116 0 > > cpufreq_powersave 2688 0 > > cpufreq_ondemand 9228 0 > > cpufreq_conservative 8200 0 > > cpufreq_userspace 5408 0 > > cpufreq_stats 7360 0 > > freq_table 5792 2 cpufreq_ondemand,cpufreq_stats > > sony_acpi 6284 0 > > dev_acpi 12292 0 > > pcc_acpi 13184 0 > > tc1100_wmi 8068 0 > > video 16388 0 > > battery 10756 0 > > ac 6020 0 > > sbs 15652 0 > > i2c_ec 6016 1 sbs > > i2c_core 22656 1 i2c_ec > > container 5248 0 > > button 8720 0 > > asus_acpi 17308 0 > > backlight 7040 1 asus_acpi > > dock 10268 0 > > sbp2 23812 0 > > parport_pc 36388 0 > > lp 12452 0 > > parport 36936 3 ppdev,parport_pc,lp > > snd_intel8x0 34332 1 > > joydev 10816 0 > > snd_ac97_codec 98464 1 snd_intel8x0 > > ac97_bus 3200 1 snd_ac97_codec > > snd_pcm_oss 44544 0 > > snd_mixer_oss 17408 1 snd_pcm_oss > > snd_pcm 79876 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss > > snd_seq_dummy 4740 0 > > snd_seq_oss 32896 0 > > pcmcia 39212 0 > > snd_seq_midi 9600 0 > > snd_rawmidi 25472 1 snd_seq_midi > > snd_seq_midi_event 8448 2 snd_seq_oss,snd_seq_midi > > snd_seq 52592 6 > > snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event > > snd_timer 23684 2 snd_pcm,snd_seq > > snd_seq_device 9100 5 > > snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq > > hsfmc97ich 71448 0 > > hsfserial 24580 1 hsfmc97ich > > hsfengine 1295244 2 hsfmc97ich,hsfserial > > iTCO_wdt 11812 0 > > iTCO_vendor_support 4868 1 iTCO_wdt > > serio_raw 7940 0 > > snd 54020 12 > > snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device > > soundcore 8672 1 snd > > intel_agp 26140 1 > > hsfosspec 104040 6 hsfmc97ich,hsfserial,hsfengine > > psmouse 38920 0 > > yenta_socket 27532 1 > > rsrc_nonstatic 14080 1 yenta_socket > > pcmcia_core 40852 3 pcmcia,yenta_socket,rsrc_nonstatic > > snd_page_alloc 10888 2 snd_intel8x0,snd_pcm > > agpgart 35400 3 drm,intel_agp > > hsfsoar 93904 1 hsfmc97ich > > shpchp 34324 0 > > pci_hotplug 32576 1 shpchp > > evdev 11008 5 > > tsdev 8768 0 > > ext3 133128 2 > > jbd 59816 1 ext3 > > mbcache 9604 1 ext3 > > sg 36252 0 > > sr_mod 17060 0 > > cdrom 37664 1 sr_mod > > sd_mod 23428 4 > > ata_piix 15492 3 > > ata_generic 9092 0 > > libata 125720 2 ata_piix,ata_generic > > scsi_mod 142348 5 sbp2,sg,sr_mod,sd_mod,libata > > 8139too 27648 0 > > generic 5124 0 [permanent] > > ohci1394 36528 0 > > ieee1394 299448 2 sbp2,ohci1394 > > 8139cp 25088 0 > > mii 6528 2 8139too,8139cp > > ehci_hcd 34188 0 > > uhci_hcd 25360 0 > > usbcore 134280 4 hsfosspec,ehci_hcd,uhci_hcd > > thermal 14856 0 > > processor 31048 1 thermal > > fan 5636 0 > > fbcon 42656 0 > > tileblit 3584 1 fbcon > > font 9216 1 fbcon > > bitblit 6912 1 fbcon > > softcursor 3200 1 bitblit > > vesafb 9220 0 > > capability 5896 0 > > commoncap 8192 1 capability > > rdlc23@rdlc23hp:~$ ls -l /dev/modem > > lrwxrwxrwx 1 root root 6 2007-10-11 20:15 /dev/modem -> ttySL0 > > rdlc23@rdlc23hp:~$ > > > > On Thursday 11 October 2007 19:11:18 you wrote: > >> Et si j'ecrivais en francais, a Nyon, vous le parlez certainement! > >> > >> What does this show? > >> sudo lsmod | grep sl > >> > >> It could be that Ubuntu loads the slmodem driver by default, then > >> forcing the /dev/ttySL0 link to /dev/modem > >> > >> lsmod shows which modules are loaded, lsmod output is sent to grep using > >> the vertical bar | , and grep scans the lsmod output for the string ls > >> which shows a reduced lsmod output sufficient to see if Ubuntu has > >> loaded the slmodem driver. > >> > >> Note that this would be expected if you installed the slmodem driver and > >> later the HSF driver without removing the slmodem driver which of course > >> is not needed. > >> > >> Jacques > >> > >> Martin Baumann wrote: > >>> Hello Jacques, > >>> i've done my fair share of mistypes today, but l'm afraid my initial > >>> analysis was correct: > >>> on start-up, ls -l /dev/modem returns /dev/ttySL0. > >>> I can change that to /dev/ttySHSF0 (as it should be) with sudo > >>> ln -s/dev/ttySHSF0/dev/modem, which checks out with ls -l /... as well as > >>> the fact that sudo rm /dev/ttySL0 returns 'no such file'. > >>> > >>> Re-boot, and we're back to square 1, ie. /dev/modem = /dev/ttySL0. > >>> So this does get loaded during start-up. > >>> > >>> Incidentally, I did test the dial-up connection with the machine > >>> disconnected from the Network. The two connections will not be used > >>> concurrently (I have an ADSL LAN here in Nyon, the dial-up is required > >>> for our holiday home in France). > >>> > >>> Have a nice evening and best regards, > >>> Martin Baumann > >>> > >>> > >>> . > >>> > >>> On Thursday 11 October 2007 15:34:58 you wrote: > >>>> Martin, > >>>> Perhaps you mistyped the command, see inside your message > >>>> > >>>> Martin Baumann wrote: > >>>>> You are right, Jacques, in your assumption that this is a graphical > >>>>> front-end for various system functions, this part of it for creating > >>>>> and maintaining network connections. > >>>>> There is a modem on /dev/ttySHSF0, with which I dialled into sunrise > >>>>> this morning. The start-up script tells me a HSF modem is being loaded > >>>>> (and when shutting down, it is shown as being stopped). > >>>>> ls -l /dev/modem, however, returns /dev/ttySL0. > >>>>> So I used sudo ln -s/dev/ttySHSF0/dev/modem to change it. This worked, > >>>>> but didn't bring the HSF modem up in the network manager. > >>>> ln -sf /dev/modem /dev/ttySHSF0 > >>>> ln -s etc... WITHOUT the additional f does not overwrite ttySL0 > >>>> > >>>> One good thing would be to do after that ln -sf ... > >>>> sudo rm /dev/ttySL0 > >>>> once, reboot, and then > >>>> ls -l /dev/modem > >>>> and > >>>> ls -l /dev/ttySL* > >>>> > >>>> Your connections (cable, wifi) to the router may make Web browsing to > >>>> fail if the so-called DNS servers are not the same. > >>>> You will see that by typing > >>>> cat /etc/resolv.conf > >>>> once with the modem on and once with the modem off. > >>>> If your router is also connected to sunrise, as the modem, you are in > >>>> the lucky case where the Ethernet and Wifi connections can coexist, but > >>>> then, how do you know which one you actually use? > >>>> > >>>> /sbin/ifconfig > >>>> shows them all (blocks eth0 and eth1 for Ethernet and wifi, ppp0 for > >>>> modem, lo is a dummy entry for internal purposes). > >>>> > >>>> Jacques > >>>> > >>>>> Having meanwhile re-booted the machine, /dev/modem is now back at > >>>>> ttySL0, so it obviously gets written there on start-up. > >>>>> Not sure this is relevant, but normally, the machine (an old Compaq > >>>>> nx9030 laptop) is connected by cable to the network router. I also use > >>>>> an old wireless card which is activated by a modprobe ndiswrapper > >>>>> command - don't ask me why and how. > >>>>> Of course I could just dial up through the terminal as and when I need > >>>>> to, but trying to explain that (or rather how to) to my wife might be > >>>>> even more daunting than figuring the network manager out! > >>>>> Best regards, > >>>>> Martin > >>>>> > >>>>> On Thursday 11 October 2007 11:44:52 you wrote: > >>>>>> Martin, > >>>>>> > >>>>>> I essentially know nothing about KDE. We at CERN try to keep tight > >>>>>> compatibility and CERN takes responsibility to tell us to rather use > >>>>>> Gnome. Assuming that your "KDE system setting" window means the > >>>>>> graphical interface to set up a network (as in Gnome), please verify > >>>>>> of you have a (pseudo)file named /dev/modem using command ls -l > >>>>>> /dev/modem Now, when the driver is loaded, it creates a /dev file > >>>>>> which would be /dev/ttySHSF0 for example for a Conexant modem, > >>>>>> /dev/ttySL0 for a modem driver by slmodem, etc... > >>>>>> If you see no /dev/modem, make one for example as in > >>>>>> ln -s /dev/ttySL0 /dev/modem > >>>>>> which means "read ttySL0 when you see modem. > >>>>>> If you already have the wrong modem ttyS... identifier, > >>>>>> ln -sf /dev/ttySL0 /dev/modem will make /dev/modem to point to > >>>>>> /dev/ttySL0 This should be enough for your Network manager to detect > >>>>>> the modem but with the SmartLink driver (slmodemd) the command > >>>>>> slmodemd et... must be running before trying to use the manager > >>>>>> (because /dev/ttySL0 exists only while this command is running). > >>>>>> Please return to me if you slmodemd and want to know how to > >>>>>> automatically start it at boot time. > >>>>>> > >>>>>> Regards - Jacques > >>>>>> > >>>>>> Martin Baumann wrote: > >>>>>>> It's a pleasure to hear and to learn from you, Jacques. > >>>>>>> Yes, I do remember punch cards and great big rattling sorting > >>>>>>> machines for them and of course - much later - the ubiquitous > >>>>>>> IBM360's. I was at Caterpillar in Geneva then, where I think we had > >>>>>>> the first e-mail system in 1974 maybe? But most of my computer > >>>>>>> experience since then - not surprisingly in the corporate world - has > >>>>>>> been MS - dominated, so converting my home systems to run on Kubuntu > >>>>>>> is a bit of an adventure. And yes, sometimes it feels like screaming, > >>>>>>> but the satisfaction of 'getting there' - as I did with my dial-in a > >>>>>>> couple of minutes ago - make it worthwhile. > >>>>>>> My next challenge will be to figure out why this modem - which > >>>>>>> obviously exists and works - still doesn't show up in my kde system > >>>>>>> settings window. Best regards, > >>>>>>> Martin Baumann > >>>>>>> > >>>>>>> On Thursday 11 October 2007 10:50:49 you wrote: > >>>>>>>> Martin, > >>>>>>>> I am a physicist, 72 years old, started using computers at CERN, > >>>>>>>> Geneva (http://cern.ch) in 1961. There were no PC's in these days, > >>>>>>>> only mainframes serving many users, one at a time with punched > >>>>>>>> cards, later also time-sharing with dumb text-only terminals. > >>>>>>>> We mainly used IBM360 mainframes running their old (still in use) > >>>>>>>> MVS operating system. Wylbur was developped by the Stanford > >>>>>>>> University in the sixties to allow program editing using dumb > >>>>>>>> alphameric terminals in place of punched cards, in time sharing, and > >>>>>>>> to allow submission to batch (one at a time) execution and results > >>>>>>>> retrieval. > >>>>>>>> > >>>>>>>> Here is an example of what Wylbur can do. > >>>>>>>> I wish to create 567 identical line such as > >>>>>>>> Hello dear Mr. XXXX, how are you? > >>>>>>>> and then to replace XXXX by a number starting from 17 increasing by > >>>>>>>> 19. I need three Wylbur commands for that. ----> is the Wylbur > >>>>>>>> prompt for a command: > >>>>>>>> ---->collect > >>>>>>>> Hello dear Mr. XXXX, how are you? > >>>>>>>> ---->CTRL-D (used to stop collecting lines) > >>>>>>>> ---->copy first do 566 > >>>>>>>> ---->change 'XXXX' to 17 +19 > >>>>>>>> > >>>>>>>> This IS a REAL LIFE daily problem for people who want to process > >>>>>>>> selected numbered data files accumulated in the laboratory without > >>>>>>>> typing the command again and again for each file... > >>>>>>>> > >>>>>>>> Enjoy Linux, and if you ever think of screaming about command lines, > >>>>>>>> please remember that Unix and therefore Linux were primarily > >>>>>>>> intended for scientists developping software, note as an "ersatz" > >>>>>>>> for Windows. > >>>>>>>> > >>>>>>>> Jacques > >>>>>>>> > >>>>>>>> Martin Baumann wrote: > >>>>>>>>> Hello Jacques, > >>>>>>>>> thanks for that explanation. Gedit was indeed missing, I'm just > >>>>>>>>> downloading it as we "speak". If it is an excellent suggestion for > >>>>>>>>> beginners who have never seen a text editor before, it's right for > >>>>>>>>> me - sadly, though l'm classified as a very, very old (50 +++) > >>>>>>>>> user, I never heard of Wylbur either. It takes a little longer, but > >>>>>>>>> l'll get to grips with it yet! > >>>>>>>>> best regards > >>>>>>>>> MCB > >>>>>>>>> . > >>>>>>>>> > >>>>>>>>> On Thursday 11 October 2007 09:15:30 Jacques Goldberg wrote: > >>>>>>>>>> Martin, > >>>>>>>>>> > >>>>>>>>>> Actually you can use any text editor in place of gedit or nano. > >>>>>>>>>> gedit is an excellent suggestion to beginners who have not seen a > >>>>>>>>>> text editor before under any system. > >>>>>>>>>> > >>>>>>>>>> Some other widely spread editors: pico kedit vi vim gvim emacs > >>>>>>>>>> nedit joe (http://en.wikipedia.org/wiki/Joe's_Own_Editor) and many > >>>>>>>>>> more. > >>>>>>>>>> > >>>>>>>>>> Early Linux distributions used to include jove (a simple friendly > >>>>>>>>>> interface to emacs) and xjove (added X11 features) but they sadly > >>>>>>>>>> seem to have faded away. > >>>>>>>>>> > >>>>>>>>>> Nedit is often preferred by people coming from a Mac or PC Windows > >>>>>>>>>> environment. > >>>>>>>>>> > >>>>>>>>>> Very old users (50+) may even think of using Wylbur (mainly for > >>>>>>>>>> professional mass editing): youngsters never heard the name! > >>>>>>>>>> > >>>>>>>>>> Actually any text editor which you may ever have used on any > >>>>>>>>>> system has an identical or very close version under Linux. > >>>>>>>>>> > >>>>>>>>>> I have written all the above because experienced users new to > >>>>>>>>>> Linux may prefer using their past (other) familiar environment > >>>>>>>>>> than learning a randomly selected tool. > >>>>>>>>>> ******** > >>>>>>>>>> > >>>>>>>>>> The absence of gedit in your computer is strange indeed, as Marv > >>>>>>>>>> says. Could you try the command > >>>>>>>>>> sudo find / -name gedit > >>>>>>>>>> to verify that this program is really missing? > >>>>>>>>>> > >>>>>>>>>> Jacques > >>>>>>>>>> > >>>>>>>>>> Marvin Stodolsky wrote: > >>>>>>>>>>> Martin > >>>>>>>>>>> > >>>>>>>>>>>> gedit /etc/wvdial.conf returns "sudo: gedit: command not found". > >>>>>>>>>>> Strange as gedit is usually part of the standard install. > >>>>>>>>>>> But you instead use: > >>>>>>>>>>> $ sudo nano /etc/wvdial.conf > >>>>>>>>>>> > >>>>>>>>>>> MarvS > >>>>>>>>>>> > >>>>>>>>>>> On 10/10/07, Martin Baumann <mcbaumann@xxxxxxx> wrote: > >>>>>>>>>>>> downloaded the hsfmodem packages listed in ModemData.txt and > >>>>>>>>>>>> installed. Is found by $ sudo wvdial / etc/wvdial.conf. However, > >>>>>>>>>>>> $ sudo > >>>>>>>>>>>> gedit /etc/wvdial.conf returns "sudo: gedit: command not found". > >>>>>>>>>>>> Text of ModemData.txt follows. > >>>>>>>>>>>> Thanks for your help, best regards, > >>>>>>>>>>>> Martin Baumann > >>>>>>>>>>>> > >>>>>>>>>>>> Only plain text email is forwarded by the > >>>>>>>>>>>> DISCUSS@xxxxxxxxxxxxx List Server. Do use the following as the > >>>>>>>>>>>> email Subject Line: SomeName, YourCountry kernel > >>>>>>>>>>>> 2.6.20-16-generic 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=i686, > >>>>>>>>>>>> Linux version 2.6.20-16-generic (root@terranova) (gcc version > >>>>>>>>>>>> 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #2 SMP Sun Sep 23 19:50:39 UTC > >>>>>>>>>>>> 2007 scanModem update of: 2007_Oct_08 > >>>>>>>>>>>> The modem symbolic link is /dev/modem -> ttySL0 > >>>>>>>>>>>> The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/0 > >>>>>>>>>>>> > >>>>>>>>>>>> There are no blacklisted modem drivers in /etc/modprobe* files > >>>>>>>>>>>> USB modem not detected by lsusb > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> Advanced Linux Sound Architecture (ALSA) spackage providing > >>>>>>>>>>>> audio support on your System, also includes drivers for some > >>>>>>>>>>>> modems. For modems using the snd-hda-intel audio+modem driver, > >>>>>>>>>>>> upgrades to a new ALSA version are sometimes > >>>>>>>>>>>> necessary to achieve function. See for example: > >>>>>>>>>>>> > >>>>>>>>>>>> http://linmodems.technion.ac.il/bigarch/archive-seventh/msg02144 > >>>>>>>>>>>> .h tm l Copying ALSA diagnostics to Modem/ALSArdlc23.tgz > >>>>>>>>>>>> ALSAversion = 1.0.13 > >>>>>>>>>>>> > >>>>>>>>>>>> Modem or candidate host audio card have firmware information and > >>>>>>>>>>>> diagnostics: > >>>>>>>>>>>> > >>>>>>>>>>>> PCI slot PCI ID SubsystemID Name > >>>>>>>>>>>> ---------- --------- --------- -------------- > >>>>>>>>>>>> 00:1f.6 8086:24c6 103c:3084 Modem: Intel > >>>>>>>>>>>> Corporation 82801DB/DBL/DBM > >>>>>>>>>>>> > >>>>>>>>>>>> Modem interrupt assignment and sharing: > >>>>>>>>>>>> 5: 6064 XT-PIC-XT Intel 82801DB-ICH4, Intel > >>>>>>>>>>>> 82801DB-ICH4 Modem > >>>>>>>>>>>> --- Bootup diagnostics for card in PCI slot 00:1f.6 ---- > >>>>>>>>>>>> [ 11.633792] ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link > >>>>>>>>>>>> [LNKB] -> GSI 5 (level, low) -> IRQ 5 > >>>>>>>>>>>> [ 11.633803] ACPI: PCI interrupt for device 0000:00:1f.6 > >>>>>>>>>>>> disabled [ 27.532000] ACPI: PCI Interrupt 0000:00:1f.6[B] -> > >>>>>>>>>>>> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5 > >>>>>>>>>>>> [ 27.532000] PCI: Setting latency timer of device 0000:00:1f.6 > >>>>>>>>>>>> to 64 > >>>>>>>>>>>> > >>>>>>>>>>>> The PCI slot 00:1f.6 of the modem card may be disabled early in > >>>>>>>>>>>> a bootup process, but then enabled later. If modem drivers > >>>>>>>>>>>> load but the modem is not responsive, read Bootup.txt about > >>>>>>>>>>>> possible fixes. Send dmesg.txt along with ModemData.txt to > >>>>>>>>>>>> discuss@xxxxxxxxxxxxx if help is needed. > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> === Finished modem firmware and bootup diagnostics section. === > >>>>>>>>>>>> === Next deducing cogent software === > >>>>>>>>>>>> > >>>>>>>>>>>> Modem not detected though HDA card diagnostics > >>>>>>>>>>>> For candidate modem in PCI bus: 00:1f.6 > >>>>>>>>>>>> Class 0703: 8086:24c6 Modem: Intel Corporation > >>>>>>>>>>>> 82801DB/DBL/DBM Primary PCI_id 8086:24c6 > >>>>>>>>>>>> Subsystem PCI_id 103c:3084 > >>>>>>>>>>>> Softmodem codec or Vendor from diagnostics: CXT30, a > >>>>>>>>>>>> Conexant type, from Archives: CXT, a Conexant type, CXT is a > >>>>>>>>>>>> generic for all CXTnumbers, with Linuxant hsfmodem software > >>>>>>>>>>>> support. > >>>>>>>>>>>> > >>>>>>>>>>>> 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: hsfmodem > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> Writing Intel.txt > >>>>>>>>>>>> > >>>>>>>>>>>> For owners of a Dell PCs with Conexant HSF modems, a driver > >>>>>>>>>>>> source package with full speed enabled is available, but > >>>>>>>>>>>> requires driver compiling. Read Conexant.txt > >>>>>>>>>>>> > >>>>>>>>>>>> The hsfmodem package serves a great variety of Conexant chipset > >>>>>>>>>>>> modems. From > >>>>>>>>>>>> http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.ph > >>>>>>>>>>>> p download > >>>>>>>>>>>> hsfmodem_VersionSpec_k2.6.20_16_generic_ubuntu_i386.deb.zip with > >>>>>>>>>>>> 2.6.20_16_generic equivalent to 2.6.20-16-generic, your kernel > >>>>>>>>>>>> version. > >>>>>>>>>>>> Under Linux unpack with: > >>>>>>>>>>>> $ unzip hsfmodem*.zip > >>>>>>>>>>>> Then install with: > >>>>>>>>>>>> $ sudo dpkg -i hsfmodem*.deb > >>>>>>>>>>>> Subsequently, the modem should be found with > >>>>>>>>>>>> $ sudo wvdialconf /etc/wvdial.conf > >>>>>>>>>>>> Edit in your personal information with: > >>>>>>>>>>>> $ sudo gedit /etc/wvdial.conf > >>>>>>>>>>>> and try dialing out with: > >>>>>>>>>>>> $ sudo wvdial. > >>>>>>>>>>>> See Testing.txt for details. > >>>>>>>>>>>> > >>>>>>>>>>>> Read Conexant.txt > >>>>>>>>>>>> > >>>>>>>>>>>> Writing Conexant.txt > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> Completed candidate modem analyses. > >>>>>>>>>>>> > >>>>>>>>>>>> The base of the UDEV device file system is: /dev/.udev > >>>>>>>>>>>> > >>>>>>>>>>>> Versions adequately match for the compiler installed: 4.1.2 > >>>>>>>>>>>> and the compiler used in kernel assembly: 4.1.2 > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> Minimal compiling resources appear complete: > >>>>>>>>>>>> make utility - /usr/bin/make > >>>>>>>>>>>> Compiler version 4.1 > >>>>>>>>>>>> linuc_headers base folder > >>>>>>>>>>>> /lib/modules/2.6.20-16-generic/build > >>>>>>>>>>>> > >>>>>>>>>>>> However some compilations and executable functions may need > >>>>>>>>>>>> additional files, in the FileNames.h (so called kernel > >>>>>>>>>>>> "h"eaders) collection installed in /usr/include/ . > >>>>>>>>>>>> For martian_modem, additional required packages are libc6-dev > >>>>>>>>>>>> (and for Debian/Ubuntu, linux-libc-dev). The also required > >>>>>>>>>>>> headers of package libc6 are commonly installed by default. > >>>>>>>>>>>> > >>>>>>>>>>>> Compressed files at: /usr/src/sl-modem.tar.bz2 > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> If a driver compilation files with message including some lack > >>>>>>>>>>>> of some FileName.h (stdio.h for example. > >>>>>>>>>>>> Some additional kernel-header files need installation to > >>>>>>>>>>>> /usr/include. For Debian/Ubuntu related distributions, run the > >>>>>>>>>>>> following command to display the needed package list: > >>>>>>>>>>>> $ sudo apt-get -s install linux-kernel-devel > >>>>>>>>>>>> While some of the files may be on the install CD, others may > >>>>>>>>>>>> have to be found through http://packages.ubuntu.com > >>>>>>>>>>>> > >>>>>>>>>>>> For Ubuntu Feisty, additional packages required were: > >>>>>>>>>>>> libc6-dev linux-libc-dev > >>>>>>>>>>>> available through http://packages.ubuntu.com/ , if not on the > >>>>>>>>>>>> install CD. Such packages may have different names for other > >>>>>>>>>>>> Linux distributions. Try installing just the libc6-dev, then > >>>>>>>>>>>> test the compile again. > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> Checking pppd properties: > >>>>>>>>>>>> -rwsr-xr-- 1 root dip 269224 2007-04-05 05:41 > >>>>>>>>>>>> /usr/sbin/pppd > >>>>>>>>>>>> > >>>>>>>>>>>> In case of an "error 17" "serial loopback" problem, see: > >>>>>>>>>>>> > >>>>>>>>>>>> http://phep2.technion.ac.il/linmodems/archive-sixth/msg02637.htm > >>>>>>>>>>>> l > >>>>>>>>>>>> > >>>>>>>>>>>> To enable dialout without Root permission do: > >>>>>>>>>>>> $ su - root (not for Ubuntu) > >>>>>>>>>>>> sudo chmod a+x /usr/sbin/pppd > >>>>>>>>>>>> or under Ubuntu related Linuxes > >>>>>>>>>>>> sudo chmod a+x /usr/sbin/pppd > >>>>>>>>>>>> > >>>>>>>>>>>> Checking settings of: /etc/ppp/options > >>>>>>>>>>>> asyncmap 0 > >>>>>>>>>>>> noauth > >>>>>>>>>>>> crtscts > >>>>>>>>>>>> lock > >>>>>>>>>>>> hide-password > >>>>>>>>>>>> modem > >>>>>>>>>>>> proxyarp > >>>>>>>>>>>> lcp-echo-interval 30 > >>>>>>>>>>>> lcp-echo-failure 4 > >>>>>>>>>>>> noipx > >>>>>>>>>>>> > >>>>>>>>>>>> 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.h > >>>>>>>>>>>> tm l > >>>>>>>>>>>> > >>>>>>>>>>>> Read Modem/YourSystem.txt concerning other COMM channels: eth0 > >>>>>>>>>>>> Which can interfere with Browser naviagation. > >>>>>>>>>>>> > >>>>>>>>>>>> Don't worry about the following, it is for the experts > >>>>>>>>>>>> should trouble shooting be necessary. > >>>>>>>>>>>> ========================================================== > >>>>>>>>>>>> > >>>>>>>>>>>> # start/stop the daemon when the USB modem is connected > >>>>>>>>>>>> KERNEL=="slusb[0-9]*", GROUP="dialout", > >>>>>>>>>>>> RUN+="/etc/init.d/sl-modem-daemon" Checking for modem support > >>>>>>>>>>>> lines: -------------------------------------- > >>>>>>>>>>>> /device/modem symbolic link: lrwxrwxrwx 1 root root 6 > >>>>>>>>>>>> 2007-10-10 09:54 /dev/modem -> ttySL0 > >>>>>>>>>>>> slmodemd created symbolic link /dev/ttySL0: lrwxrwxrwx 1 root > >>>>>>>>>>>> root 10 2007-10-10 09:54 /dev/ttySL0 -> /dev/pts/0 > >>>>>>>>>>>> Within /etc/udev/ files: > >>>>>>>>>>>> /etc/udev/rules.d/030_sl-modem-daemon.rules:# start/stop the > >>>>>>>>>>>> daemon when the USB modem is connected > >>>>>>>>>>>> /etc/udev/rules.d/030_sl-modem-daemon.rules:KERNEL=="slusb[0-9]* > >>>>>>>>>>>> ", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon" > >>>>>>>>>>>> /etc/udev/sl-modem-daemon.rules:# start/stop the daemon when the > >>>>>>>>>>>> USB modem is connected > >>>>>>>>>>>> /etc/udev/sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", > >>>>>>>>>>>> GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon" > >>>>>>>>>>>> Within /etc/modprobe.conf files: > >>>>>>>>>>>> /etc/modprobe.d/sl-modem-daemon.modutils:install slamr > >>>>>>>>>>>> modprobe --ignore-install ungrab-winmodem ; modprobe > >>>>>>>>>>>> --ignore-install slamr; test -e /dev/slamr0 || (/bin/mknod -m > >>>>>>>>>>>> 660 /dev/slamr0 c 242 0 2>/dev/null && chgrp dialout > >>>>>>>>>>>> /dev/slamr0) /etc/modprobe.d/blacklist-modem:# Uncomment these > >>>>>>>>>>>> entries in order to blacklist unwanted modem drivers > >>>>>>>>>>>> /etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem > >>>>>>>>>>>> /etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem > >>>>>>>>>>>> /etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2 > >>>>>>>>>>>> /etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2 > >>>>>>>>>>>> Within any ancient /etc/devfs files: > >>>>>>>>>>>> > >>>>>>>>>>>> Within ancient kernel 2.4.n /etc/module.conf files: > >>>>>>>>>>>> > >>>>>>>>>>>> --------- end modem support lines -------- > > >
