Robert, When I get home, I will try to play with it a bit. I have a slax module and a script that generates the module for Slax 6.1.2 with kernel 2.6.27.27 http://www.slax.org/modules.php?action=detail&id=2487 But I will run this against slax-remix-v06 or next-remix-v07 which have 2.6.33.2 and 2.6.34 kernels respectively. If I encounter any failures/success, I will report back. If anyone can download Slax remix(es), and get the script you can beat me to it and report back, just change the line: From: # run ./configure -auto for the type of modem you have # you can have pct789,,,cm8738, i8xx, sis, via686a ./configure -auto # otherwise change this to your modem type :) to # run ./configure -auto for the type of modem you have # you can have pct789,,,cm8738, i8xx, sis, via686a ./configure -pct789 # otherwise change this to your modem type :) like Robert is instructing us to do. Regards, Antonio On Tue, Jun 1, 2010 at 6:39 AM, Robert Thornburrow <robert.thornburrow@xxxxxxxxxxxxxxxx> wrote: > Antonio, > > If I read the script right, it should always prompt for the modem type if > the autodetection fails, but you can always run it manually by following > what the setup script does and substitute -manual for -auto when running > configure. Choose the "pct789" HAL as it is the most common. > > Steps are: > > cd src/ > ./configure -manual > make > > Optionally you can also do: > > make install > make insmod > > But these are not necessary to test for compile failures. Of course you > would still need the modem installed to test that the driver actually works! > > Best regards, > > Robert > > On 01/06/2010 12:08, Antonio Olivares wrote: >> >> Robert, >> >> On 6/1/10, Robert Thornburrow <robert.thornburrow@xxxxxxxxxxxxxxxx> wrote: >>> Antonio, >>> >>> What kernel changes are there for 2.6.34? >> >> http://kernelnewbies.org/Linux_2_6_34 >> >>> Anything significant that >>> affects modem drivers? >>> >> >> I don't know about this one, will have to test some more. I know that >> martian_modem does not work on it, get some error message. The >> martian_dev.ko file can get created, but the martian_modem helper is >> not created :( Don't know about other drivers i.e, intel 537 and >> slmodemd, will test when I have a chance this afternoon/tonight. >> >>> >>> Owing to work commitments, I'm afraid I only do patches when someone >>> reports a compilation failure against a new kernel. If there are definite >>> errors (other than the include/asm/mach-default one), could you please >>> forward them to me and I will fix. >>> >> I'll try my best to let you know. Need to plug out PCTEL modem and >> take it with me and put into test computer, otherwise configure script >> will bomb out since there is no PCTEL modem :( >>> >>> Best regards, >>> >>> Robert >>> >> Regards, >> >> Antonio >> >>> On 01/06/2010 03:29, Antonio Olivares wrote: >>>> >>>> Carlos, >>>> >>>> Thanks for forwarding the ModemData.txt >>>> >>>> I can see the statement: >>>> >>>> Versions adequately match for the compiler installed: 4.4.3 >>>> and the compiler used in kernel assembly: 4.4.3 >>>> >>>> linux-headers-2.6.32-21-generic resources needed for compiling are >>>> not manifestly ready! >>>> The patch utility is needed for compiling ALSA drivers, and possibly >>>> others. >>>> >>>> If compiling is necessary packages must be installed, providing: >>>> linux-headers-2.6.32-21-generic >>>> >>>> and what you tried to do to remedy it >>>> >>>>>>> carlos@carlos-desktop:~$ sudo apt-get install linux-headers-$(uname -r) >>>>>>> Reading package lists... Done >>>>>>> Building dependency tree >>>>>>> Reading state information... Done >>>>>>> linux-headers-2.6.32-21-generic is already the newest version. >>>>>>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. >>>>>>> carlos@carlos-desktop:~$ >>>> >>>> Your machine is i686 and not x86_64. The drivers are not working, or >>>> the kernel devel/sources are not present and will fail to build. I >>>> hope that Marv can test the drivers? >>>> I don't have 2.6.32 kernel now, but on 2.6.34 to test. I do believe >>>> pctel code has not been updated to accomodate new kernel changes :( >>>> >>>> Hope we can find something to help figure this out. >>>> >>>> >>>> Regards, >>>> >>>> Antonio >>>> >>>> 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.32-21-generic >>>> 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=i686, Ubuntu , ALSA_version=1.0.21 >>>> Linux version 2.6.32-21-generic (buildd@rothera) (gcc version 4.4.3 >>>> (Ubuntu 4.4.3-4ubuntu5) ) #32-Ubuntu SMP Fri Apr 16 08:10:02 UTC 2010 >>>> scanModem update of: 2010_05_29 >>>> >>>> Distrib_ID=Ubuntu >>>> DistribCodeName=lucid >>>> AptRepositoryStem=http://us.archive.ubuntu.com/ubuntu/ >>>> >>>> >>>> Presently install your Linux Distributions dkms package. It provides >>>> for automated driver updates, >>>> following upgrade of your kernel. For details see >>>> http://linux.dell.com/projects.shtml#dkms >>>> >>>> There are no blacklisted modem drivers in /etc/modprobe* files >>>> >>>> Potentially useful modem drivers now loaded are: >>>> >>>> >>>> Attached USB devices are: >>>> ID 05dc:a400 Lexar Media, Inc. JumpDrive trade; Pro 40-501 >>>> If a cellphone is not detected, see >>>> http://ubuntuforums.org/archive/index.php/t-878554.html >>>> A sample report is: >>>> http://linmodems.technion.ac.il/bigarch/archive-nineth/msg00578.html >>>> >>>> If a USB modem or cellphone is attached and was not detected, please >>>> provide available information in your request to discuss@xxxxxxxxxxxxx >>>> >>>> Candidate PCI devices with modem chips are: >>>> 05:06.0 Modem: PCTel Inc HSP MicroModem 56 (rev 02) >>>> High Definition Audio cards can host modem chips. >>>> >>>> For candidate card in slot 05:06.0, firmware information and bootup >>>> diagnostics are: >>>> PCI slot PCI ID SubsystemID Name >>>> ---------- --------- --------- -------------- >>>> 05:06.0 134d:7890 13e1:5089 Modem: PCTel Inc HSP MicroModem 56 >>>> >>>> Modem interrupt assignment and sharing: >>>> --- Bootup diagnostics for card in PCI slot 05:06.0 ---- >>>> [ 0.100569] pci 0000:05:06.0: reg 10 io port: [0xb000-0xb03f] >>>> [ 0.100599] pci 0000:05:06.0: supports D2 >>>> [ 0.100601] pci 0000:05:06.0: PME# supported from D0 D2 D3hot >>>> [ 0.100605] pci 0000:05:06.0: PME# disabled >>>> [ 0.263884] serial 0000:05:06.0: PCI INT A -> Link[APC1] -> GSI 16 >>>> (level, low) -> IRQ 16 >>>> >>>> The PCI slot 05:06.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. >>>> >>>> >>>> === Finished firmware and bootup diagnostics, next deducing cogent >>>> software. === >>>> >>>> Predictive diagnostics for card in bus 05:06.0: >>>> Modem chipset detected on >>>> NAME="Modem: PCTel Inc HSP MicroModem 56 " >>>> CLASS=0703 >>>> PCIDEV=134d:7890 >>>> SUBSYS=13e1:5089 >>>> IRQ=16 >>>> IDENT=PCTEL >>>> >>>> For candidate modem in: 05:06.0 >>>> 0703 Modem: PCTel Inc HSP MicroModem 56 >>>> Primary device ID: 134d:7890 >>>> Support type needed or chipset: PCTEL >>>> >>>> >>>> At http://linmodems.technion.ac.il/pctel-linux >>>> Get the pctel-0.9.7-9-rht-10.tar.gz >>>> Unpack under Linux with: >>>> tar zxf pctel*.tar.gz >>>> and read instuctions therein. >>>> Read DOCs/Pctel.txt and Modem/DOCs/YourSystem.txt for follow through >>>> guidance. >>>> >>>> Writing DOCs/Pctel.txt >>>> >>>> Completed candidate modem analyses. >>>> >>>> The base of the UDEV device file system is: /dev/.udev >>>> >>>> Versions adequately match for the compiler installed: 4.4.3 >>>> and the compiler used in kernel assembly: 4.4.3 >>>> >>>> linux-headers-2.6.32-21-generic resources needed for compiling are >>>> not manifestly ready! >>>> The patch utility is needed for compiling ALSA drivers, and possibly >>>> others. >>>> >>>> If compiling is necessary packages must be installed, providing: >>>> linux-headers-2.6.32-21-generic >>>> >>>> >>>> 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: >>>> -rwsr-xr-- 1 root dip 273312 2010-03-06 19:59 /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) >>>> 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 >>>> >>>> For guidance on FAX usage, get from >>>> http://linmodems.technion.ac.il/packages/ get faxing.tar.gz >>>> It has samples for a modem using port /dev/ttySL0, which must be >>>> changed to match your modem's port. >>>> >>>> Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 >>>> 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: >>>> /etc/udev/rules.d/70-pctel.rules:KERNEL=="ttyS_PCTEL0", SYMLINK="modem" >>>> Within /etc/modprobe.conf files: >>>> /etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2 >>>> /etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2 >>>> /etc/modprobe.d/blacklist-modem.conf:# Uncomment these entries in >>>> order to blacklist unwanted modem drivers >>>> /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-atiixp-modem >>>> /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-via82xx-modem >>>> Within any ancient /etc/devfs files: >>>> >>>> Within ancient kernel 2.4.n /etc/module.conf files: >>>> >>>> --------- end modem support lines -------- >>>> >>>> >>>> >>>> On 5/31/10, carlos ramos <caramosc@xxxxxxxxx> wrote: >>>>> On 5/31/10, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: >>>>>> Carlos, >>>>>> >>>>>> Sorry to ask you, but you point out that you have PcTEL HSP Modem, >>>>>> You did run scanModem, can you attach/send us ModemData.txt? >>>>>> >>>>>> http://linmodems.technion.ac.il/packages/scanModem.gz >>>>>> >>>>>> Why do I ask, we need to know exactly the architecture, the modem >>>>>> driver might be correct, but you might be running on an x86_64 machine >>>>>> which will produce errors and not work. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Antonio >>>>>> >>>>>> On 5/31/10, carlos ramos <caramosc@xxxxxxxxx> wrote: >>>>>>> Hi, first thanks for taking the time to read about my situation. >>>>>>> >>>>>>> Well i have an internal dial up modem that i cant install in my pc. >>>>>>> This is my first try with a linux distro, moving from XP, but having a >>>>>>> pc with out an internet connection is like having a car with out >>>>>>> wheels. So im really hoping to get the modem install to completely >>>>>>> move from windows. >>>>>>> >>>>>>> System: Ubuntu 10.04 >>>>>>> Modem: PCTel HSP Micromodem 56 134d:7890 >>>>>>> >>>>>>> I already ran the scanmodem tool, thats why im sure about the model of >>>>>>> the modem, i downloaded the recommended pctel-0.9.7-9-rht-10.tar.gz >>>>>>> file but when i do: >>>>>>> >>>>>>> carlos@carlos-desktop:~/Desktop/pctel-0.9.7-9-rht-10$ sudo ./setup >>>>>>> checking for running kernel version...2.6.32 >>>>>>> checking for ptserial...ptserial-2.6.c >>>>>>> checking for gcc...4.4.3 >>>>>>> checking for kernel gcc version...4.4.3 >>>>>>> searching for kernel includes...found at >>>>>>> /lib/modules/2.6.32-21-generic/build/include >>>>>>> checking for >>>>>>> autoconf.h.../lib/modules/2.6.32-21-generic/build/include/linux/autoconf.h >>>>>>> checking for asm/mach-default...** error >>>>>>> include/asm/mach-default directory could not be found >>>>>>> you probably need to configure your kernel, please read the FAQ >>>>>>> about no include/asm/mach-default directory. >>>>>>> ** compilation error >>>>>>> please read the FAQ about reporting compilation problems >>>>>>> and report this problem. A transcript of the build process >>>>>>> has been saved in src/make.log. When reporting problems to >>>>>>> the development team, please send us this file. >>>>>>> >>>>>>> thats what i get, the make.log file really doesnt tell my anything, its >>>>>>> content: >>>>>>> >>>>>>> make: *** No targets specified and no makefile found. Stop. >>>>>>> >>>>>>> I've been trying to install the modem for a couple of days now but no >>>>>>> luck, I've been googgling and going through forum threads rebooting to >>>>>>> ubuntu and trying, then rebooting to windows to search for more tips >>>>>>> but nothing. I read in a thread that i must have the linux headers >>>>>>> install but i think i do because when i do: >>>>>>> >>>>>>> carlos@carlos-desktop:~$ sudo apt-get install linux-headers-$(uname -r) >>>>>>> Reading package lists... Done >>>>>>> Building dependency tree >>>>>>> Reading state information... Done >>>>>>> linux-headers-2.6.32-21-generic is already the newest version. >>>>>>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. >>>>>>> carlos@carlos-desktop:~$ >>>>>>> >>>>>>> any help will be appreciated !!! >>>>>>> >>>>>> >>>>> Yes i did run the scanmodem tool. >>>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> > > >
