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.html > >> 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.php > >> 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.html > >> > >> 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.html > >> > >> 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 --------
