--- On Wed, 6/24/09, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: > From: Antonio Olivares <olivares14031@xxxxxxxxx> > Subject: Re: using a phone modem on F10 on a Thinkpad T61 > To: " encouragement and advice for using Fedora.Community assistance" <fedora-list@xxxxxxxxxx> > Date: Wednesday, June 24, 2009, 4:52 PM > > --- On Wed, 6/24/09, Globe Trotter <itsme_410@xxxxxxxxx> > wrote: > > > From: Globe Trotter <itsme_410@xxxxxxxxx> > > Subject: using a phone modem on F10 on a Thinkpad T61 > > To: fedora-list@xxxxxxxxxx > > Date: Wednesday, June 24, 2009, 1:21 PM > > > > So, I know this is kind of ancient, but I am behind a > phone > > line on a IBM Thinkpad T61 and was wondering if anyone > could > > please help me with how to set it up for Fedora 10. > > > > Best, > > T > > > > > > > > > > -- > > Trotter, > > Please visit LinModems.org page: > > http://linmodems.technion.ac.il/ > > Download scanModem.gz > > http://linmodems.technion.ac.il/packages/scanModem.gz > > copy it to your home folder/directory > > $ gunzip scanModem.gz > $ chmod +x scanModem > $ su - > passwd: > # ./scanModem > > will run and write folder Modem/ with ModemData.txt please > send it to me not list here(you can register at > linmodems.org site and send to discuss@xxxxxxxxxxxxx > at your discretion), but I think I can help so please send > it to me if you want. I hope that the modem is not a > difficult one and that we can help get you online with > Fedora. If it is a cell phone that you will use as a > modem, then you may safely run from a terminal > > $ su - > passwd: > # wvdialconf /etc/wvdial.conf > > and it will scan for modem ports and may find one like at > /dev/ttyUSB0, or /dev/ttyACM0 or something related. > Then you may edit the /etc/wvdial.conf file as root add your > username, password and ISP's phone number and get > connected. > > Hope this helps, > > Antonio > > > > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > hi antonio, here is the ModemData attached. Thanks very much for all your help! T PS: I attach as text in case the attachment file does not make it through... Only plain text email is forwarded by the Discuss@xxxxxxxxxxxxx List Server, as HTML can contain viruses. Use as the email Subject Line: YourName, YourCountry kernel 2.6.27.24-170.2.68.fc10.x86_64 With this Subject Line cogent experts will be alerted, and useful case names left in the Archive. YourCountry will enable Country specific guidance. Linux experts in YourCountry can be found through: http://www.linux.org/groups/index.html. They will know your Country's modem code, which may be essential for dialup service. Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an Internet Provider mail filters. So in a day, also check the Archived responses at http://www.linmodems.org -------------------------- System information ---------------------------- CPU=x86_64, Linux version 2.6.27.24-170.2.68.fc10.x86_64 (mockbuild@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.3.2 20081105 (Red Hat 4.3.2-7) (GCC) ) #1 SMP Wed May 20 22:47:23 EDT 2009 scanModem update of: 2009_05_31 Some modem drivers can only be used in 32 bit modem on x86_64 systems, while some others are competent on x86_64 Systems. Cases are: 1) http://linmodems.technion.ac.il/bigarch/archive-seventh/msg03119.html for the snd-hda-intel audio+modem driver. Also applicable to AC97 modem controllers. In both cases, 32 bit libraries must be installed to support the slmodemd helper having a precompiled 32 bit component. 2) For USB modems using the slusb.ko driver. 32 bit libraries must be installed to support the slmodemd helper having a precompiled 32 bit component 3) The hsfmodem and hcfpcimodem drivers for Conexant chipsest modes are x86_64 competent. There are no blacklisted modem drivers in /etc/modprobe* files Potentially useful modem drivers now loaded are: snd_hda_intel Attached USB devices are: ID 0781:5151 SanDisk Corp. Cruzer Micro 256/512MB Flash Drive ID 045e:0040 Microsoft Corp. Wheel Mouse Optical ID 0a5c:2110 Broadcom Corp. Bluetooth Controller If a cellphone is not detected, see http://ubuntuforums.org/archive/index.php/t-878554.html If a USB modem or cellphone is attached and was not detected, please provide available information in your request to discuss@xxxxxxxxxxxxx For candidate card in slot 00:1b.0, firmware information and bootup diagnostics are: PCI slot PCI ID SubsystemID Name ---------- --------- --------- -------------- 00:1b.0 8086:284b 17aa:20ac Audio device: Intel Corporation 82801H Modem interrupt assignment and sharing: 17: 181 618 IO-APIC-fasteoi uhci_hcd:usb6, HDA Intel, firewire_ohci, iwlagn --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- PCI: 0000:00:1b.0 reg 10 64bit mmio: [fe020000, fe023fff] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold pci 0000:00:1b.0: PME# disabled HDA Intel 0000:00:1b.0: PCI INT B -> GSI 17 (level, low) -> IRQ 17 HDA Intel 0000:00:1b.0: setting latency timer to 64 The PCI slot 00:1b.0 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 DOCs/Bootup.txt about possible fixes. Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx if help is needed. ===== Advanced Linux Sound Architecture (ALSA) diagnostics ===== The ALSA packages provide audio support and also drivers for some modems. ALSA diagnostics are written during bootup to /proc/asound/ folders. The /proc/asound/pcm file reports: ----------------------- 00-01: AD198x Digital : AD198x Digital : playback 1 00-00: AD198x Analog : AD198x Analog : playback 1 : capture 2 about /proc/asound/cards: ------------------------ 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xfe020000 irq 17 PCI slot 00:1b.0 has a High Definition Audio Card The drivers are in the kernel modules tree at: /lib/modules/2.6.27.24-170.2.68.fc10.x86_64/kernel/sound/pci/hda/snd-hda-intel.ko /lib/modules/2.6.27.5-117.fc10.x86_64/kernel/sound/pci/hda/snd-hda-intel.ko UNEXPECTED HDA diagnostic outcome. === Finished firmware and bootup diagnostics, next deducing cogent software. === Predictive diagnostics for card in bus 00:1b.0: Modem chipset detected on NAME="Audio device: Intel Corporation 82801H " CLASS=0403 PCIDEV=8086:284b SUBSYS=17aa:20ac IRQ=17 HDA=8086:284b SOFT=8086:284b.HDA ArchivedChip=0x14f12bfa CodecClass=14f1 IDENT=hsfmodem Driver=hsfmodem-drivers For candidate modem in: 00:1b.0 0403 Audio device: Intel Corporation 82801H Primary device ID: 8086:284b Subsystem PCI_id 17aa:20ac Softmodem codec or chipset from diagnostics: from Archives: 0x14f12bfa Support type needed or chipset: hsfmodem Writing DOCs/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 DOCs/Conexant.txt Start at http://www.linuxant.com/drivers/hsf/downloads-license.php to find the hsfmodem package matching your System. For several Linux distros, there are precompiled drivers matched to specific kernels. These have within the FileName, your KernelVersion: 2.6.27.24_170.2.68.fc10.x86_64 They can be found through http://www.linuxant.com/drivers/hsf/full/downloads.php A more precise location may be given a few paragraphs below. If an EXACT Match with your your KernelVersion is not found, one of the "Generic packages with source" near the bottom of the page must be used. Downloaded packages must be moved into the Linux partition (home folder is OK) and unzipped with: unzip hsf*.zip The installation command for a .deb suffic packages is, with root/adm permission: dpkg -i hsf*.deb while for .rpm suffix it is, with: rpm -i hsf*.rpm Support for Conexant chips hosted on High Definition Audio cards may require installation of additional packages, one of the alsa-driver-linuxant packages on http://www.linuxant.com/alsa-driver/ At the same time download the alsa-driver-1.0.17-1.patch , in case it prove to be later needed. During the hsfmodem install, there will be a message if there is necessary installation of alsa-driver-linuxant The installation command for a .deb suffic packages is, with root/adm permission: dpkg -i hsf*.deb while for .rpm suffix it is, with: rpm -i hsf*.rpm There may a message that "Dependencies" are not satisfied. In this case the Ubuntu/Debian packages to be installed are linux-libc-dev & libc6-dev. Package names may be different for other Linuxes. If not on your install CD, these packages can be searched for at http://packages.ubuntu.com. After download, they can be coinstalled with: dpkg -i li*.deb Again try the alsa-driver-linuxant There may be a message that the patch must be applied. In this case get the ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.17.tar.bz2 Under Linux, this package is unpacked with: $ tar jxf alsa*.tar.bz2 Next the patch is applied with: $ patch -p0 < alsa-driver-1.0.17-1.patch See http://linmodems.technion.ac.il/bigarch/archive-eighth/msg00838.html for details on compiling and installing replacement snd-hda-intel + its dependent drivers. After the installation is completed, rerun the hsfmodem installation. Reboot and try to detect the modem with Root permission: wvdialconf /etc/wvdial.conf Start at http://www.linuxant.com/drivers/hsf/full for eventually download of a hsfmodem-7.68.00.12full_k.???.zip package with ??? the package type (deb, rpm, tar etc) These packages have compiled drivers but will also compile a driver, if there is a mismatch between the resident kernel and provided driver. The generic hsfmodem-7.68.00.12full.tar.gz package only provides compiling support Read DOCs/Conexant.txt Writing DOCs/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.3.2 and the compiler used in kernel assembly: 4.3.2 linux-headers-2.6.27.24-170.2.68.fc10.x86_64 resources needed for compiling are not manifestly ready! If compiling is necessary packages must be installed, providing: If a driver compilation fails, with message including some lack of some FileName.h (stdio.h for example), then Some additional kernel-header files need installation to /usr/include. The minimal additional packages are libc6-dev and any of its dependents, under Ubuntu linux-libc-dev If an alternate ethernet connection is available, $ apt-get update $ apt-get -s install linux-kernel-devel will install needed packages. For Debian/Ubuntu related distributions, run the following command to display the needed package list: Otherwise packages have to be found through http://packages.ubuntu.com Once downloaded and transferred into a Linux partition, they can be installed alltogether with: $ sudo dpkg -i *.deb Checking pppd properties: -r-xr-xr-x 1 root root 349480 2008-08-28 16:49 /usr/sbin/pppd In case of an "error 17" "serial loopback" problem, see: http://linmodems.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/DOCs/YourSystem.txt concerning other COMM channels: eth0 wlan0 wmaster0 Which can interfere with Browser naviagation. Don't worry about the following, it is for 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: 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 -------- -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
