Ok. If I can't seem to get this PCI modem working what serial modems are supported? I really need to get net access for this machine.. Thanks, Phil ----- Forwarded Message ---- From: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> To: Fyl Beall <fylbeall@xxxxxxxxx> Cc: Robert Thornburrow <robert.thornburrow@xxxxxxxxxxxxxxxx> Sent: Wednesday, January 31, 2007 5:27:25 PM Subject: Re: Phil USA pclinuxos Linux release 2006 (Texstar) for i586 Kernel 2.6.16.27.tex1.lve on an i686 / kernel 2.6.16.27.tex1.lve Fyl, Re: ttyS_PCTEL0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. -------------- Means that the driver is NOT supporting interrogation of the hardware. This is the core problem, and I cannot assess why. Automation can be done, what there is no use fusing with it until a postive response is acquired by: # wvdialconf /etc/wvdial.conf Try that if you haven't as yet. Is the modem working under Microsoft. Copy responses to Robert, our Pctel expert MarvS On 1/31/07, Fyl Beall <fylbeall@xxxxxxxxx> wrote: > Marvin, > Modprobe seems to help some. KPPP now finds the modem but it does not seem to get any response back from the modem when it is queried. /dev/ttyS_PCTEL0 is created but it only seems to last for the current session. When I reboot I have to again do a modprobe to at least get KPPP to even see it. Is there a way to make it show up permanently and what do you think the cause is of the modem not talking to me? Here's the modprobe output: > > > Scanning your serial ports for a modem. > > Port Scan<*1>: Scanning ttyS_PCTEL0 first, /dev/modem is a link to it. > ttyS_PCTEL0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 4800 baud > ttyS_PCTEL0<*1>: ATQ0 V1 E1 -- failed with 4800 baud, next try: 9600 baud > ttyS_PCTEL0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 19200 baud > ttyS_PCTEL0<*1>: ATQ0 V1 E1 -- failed with 19200 baud, next try: 115200 baud > ttyS_PCTEL0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. > ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 4800 baud > ttyS0<*1>: ATQ0 V1 E1 -- failed with 4800 baud, next try: 9600 baud > ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 19200 baud > ttyS0<*1>: ATQ0 V1 E1 -- failed with 19200 baud, next try: 115200 baud > ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. > ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 4800 baud > ttyS1<*1>: ATQ0 V1 E1 -- failed with 4800 baud, next try: 9600 baud > ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 19200 baud > ttyS1<*1>: ATQ0 V1 E1 -- failed with 19200 baud, next try: 115200 baud > ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. > Port Scan<*1>: S2 S3 > > Sorry, no modem was detected! Is it in use by another program? > Did you configure it properly with setserial? > > Please read the FAQ at http://open.nit.ca/wvdial/ > > If you still have problems, send mail to wvdial-list@xxxxxxxxxxxxx > > [root@localhost ~]# > > > > > ----- Original Message ---- > From: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> > To: Fyl Beall <fylbeall@xxxxxxxxx> > Sent: Tuesday, January 30, 2007 7:56:56 PM > Subject: Re: Phil USA pclinuxos Linux release 2006 (Texstar) for i586 Kernel 2.6.16.27.tex1.lve on an i686 / kernel 2.6.16.27.tex1.lve > > Fyl, > > RE The base of the UDEV device file system is: /dev/.udevdb > The devices have to be created a new after each bootup, for UDEV using systems. > So do > $ su root > # modprobe Driver (I don't remember what your PCtel Driver name is). > This should also create the /dev/ttyS_PCTEL0 > which should then be found by: > # wvdialconf /etc/wvdial.conf > > Try it > > Marv > > > > > On 1/30/07, Fyl Beall <fylbeall@xxxxxxxxx> wrote: > > Syed and Marvin, > > Also, when I try to configure KPPP it cannot find the modem and fails with a "unable to open modem" error when I use /dev/modem. > > > > Phil > > > > ----- Original Message ---- > > From: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> > > To: Fyl Beall <fylbeall@xxxxxxxxx> > > Cc: discuss@xxxxxxxxxxxxx > > Sent: Tuesday, January 30, 2007 5:53:01 AM > > Subject: Re: Phil USA pclinuxos Linux release 2006 (Texstar) for i586 Kernel 2.6.16.27.tex1.lve on an i686 / kernel 2.6.16.27.tex1.lve > > > > RE: > The modem symbolic link is /dev/modem -> ttyS_PCTEL0 > > Run > > # wvdialconf /etc/wvdial.conf > > is the modem detected? > > > > If so: > > # gedit /etc/wvdial.conf > > entering your personal info and deleting the < > > > Then dialout with' > > # wvdial > > > > MarvS > > > > On 1/30/07, Fyl Beall <fylbeall@xxxxxxxxx> wrote: > > > > > > Hi, > > > > > > This installation looks like it's installing the drivers and finding the modem ok but when I try to configure an internet connection it only gives me serial port options. It does not seem to find the PCI modem. > > > > > > > > > Thanks for being willing to help! > > > > > > Phil > > > > > > > > > -------------------------- System information ---------------------------- > > > > > > pclinuxos Linux release 2006 (Texstar) for i586 > > > > > > Kernel 2.6.16.27.tex1.lve on an i686 / > > > > > > Linux version 2.6.16.27.tex1.lve (ocilent1@xpc) (gcc version 3.3.1 (Mandrake Linux 9.2 3.3.1-2mdk)) #1 Mon Jul 31 15:59:12 WST 2006 > > > > > > scanModem update of: 2006_December_25 > > > > > > The modem symbolic link is /dev/modem -> ttyS_PCTEL0 > > > > > > > > > > > > USB modem not detected by lsusb > > > > > > > > > > > > Modem or host audio card candidates have firmware information: > > > > > > > > > > > > PCI slot PCI ID SubsystemID Name > > > > > > ---------- --------- --------- -------------- > > > > > > 02:09.0 134d:7897 134d:0001 Modem: PCTel Inc HSP MicroModem 56 > > > > > > > > > > > > Modem interrupt assignment and sharing: > > > > > > > > > > > > --- Bootup diagnositcs for card in PCI slot 02:09.0 ---- > > > > > > ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 18 (level, low) -> IRQ 16 > > > > > > ACPI: PCI interrupt for device 0000:02:09.0 disabled > > > > > > ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 18 (level, low) -> IRQ 16 > > > > > > pctel_pci(232): PCTel device[0000:02:09.0](0x48) found 134d:7897 (rev 02), iobase=0x1040, irq=16. > > > > > > > > > > > > The PCI slot 02:09.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 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 === > > > > > > > > > > > > For candidate modem in PCI bus: 02:09.0 > > > > > > Class 0703: 134d:7897 Modem: PCTel Inc HSP MicroModem 56 > > > > > > Primary PCI_id 134d:7897 > > > > > > Support type needed or chipset: PCTEL > > > > > > > > > > > > > > > > > > At http://linmodems.technion.ac.il/pctel-linux > > > > > > Get the pctel-0.9.7-9-rht-6.tar.gz > > > > > > Unpack under Linux with: > > > > > > tar zxf pctel*.tar.gz > > > > > > and read instuctions therein. > > > > > > Read Pctel.txt and Modem/YourSystem.txt for follow through guidance. > > > > > > > > > > > > Writing Pctel.txt > > > > > > > > > > > > Completed candidate modem analyses. > > > > > > > > > > > > The base of the UDEV device file system is: /dev/.udevdb > > > > > > > > > > > > Versions adequately match for the compiler installed: 3.3.1 > > > > > > and the compiler used in kernel assembly: 3.3.1 > > > > > > > > > > > > > > > > > > > > > > > > Compiling resources appear complete: > > > > > > make utility - /usr/bin/make > > > > > > Compiler version 3.3 > > > > > > kernel_headers base folder /lib/modules/2.6.16.27.tex1.lve/build > > > > > > Compressed files at: /usr/src/acx-20070101.tar.bz2 > > > > > > > > > > > > > > > > > > Checking pppd properties: > > > > > > -rwsr-xr-t 1 root root 300248 Jul 23 16:10 /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 > > > > > > noauth > > > > > > noipdefault > > > > > > usepeerdns > > > > > > > > > > > > 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. > > > > > > ========================================================== > > > > > > > > > > > > # > > > > > > # UDEV rule for modems > > > > > > # creates symlink /dev/modem and takes care of permissions > > > > > > KERNEL="ttyLTM[0-9]", NAME="%k", MODE="0660", GROUP="uucp", SYMLINK="modem" > > > > > > KERNEL="slusb[0-9]", NAME="%k", MODE="0660", GROUP="uucp", SYMLINK="modem" > > > > > > KERNEL="ttySL[0-9]", NAME="%k", MODE="0660", GROUP="uucp", SYMLINK="modem" > > > > > > KERNEL="ttySHCF[0-9]", NAME="%k", MODE="0660", GROUP="uucp", SYMLINK="modem" > > > > > > Checking for modem support lines: > > > > > > -------------------------------------- > > > > > > /device/modem symbolic link: lrwxrwxrwx 1 root root 11 Jan 8 08:34 /dev/modem -> ttyS_PCTEL0 > > > > > > slmodemd created symbolic link /dev/ttySL0: > > > > > > Within /etc/udev/ files: > > > > > > /etc/udev/rules.d/pctel.rules:KERNEL="ttyS_PCTEL0", SYMLINK="modem" > > > > > > /etc/udev/rules.d/modem.rules:# UDEV rule for modems > > > > > > /etc/udev/rules.d/modem.rules:# creates symlink /dev/modem and takes care of permissions > > > > > > /etc/udev/rules.d/modem.rules:KERNEL="ttyLTM[0-9]", NAME="%k", MODE="0660", GROUP="uucp", SYMLINK="modem" > > > > > > /etc/udev/rules.d/modem.rules:KERNEL="slusb[0-9]", NAME="%k", MODE="0660", GROUP="uucp", SYMLINK="modem" > > > > > > /etc/udev/rules.d/modem.rules:KERNEL="ttySL[0-9]", NAME="%k", MODE="0660", GROUP="uucp", SYMLINK="modem" > > > > > > /etc/udev/rules.d/modem.rules:KERNEL="ttySHCF[0-9]", NAME="%k", MODE="0660", GROUP="uucp", SYMLINK="modem" > > > > > > 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 -------- > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > __________________________________________________ > > > Do You Yahoo!? > > > Tired of spam? Yahoo! Mail has the best spam protection around > > > http://mail.yahoo.com > > > > > > > > > > > > > > > > > > > > > ____________________________________________________________________________________ > > > Sucker-punch spam with award-winning protection. > > > Try the free Yahoo! Mail Beta. > > > http://advision.webevents.yahoo.com/mailbeta/features_spam.html > > > > > > > > > > > > > > > > > ____________________________________________________________________________________ > > Any questions? Get answers on any topic at www.Answers.yahoo.com. Try it now. > > > > > > > > > ____________________________________________________________________________________ > Now that's room service! Choose from over 150,000 hotels > in 45,000 destinations on Yahoo! Travel to find your fit. > http://farechase.yahoo.com/promo-generic-14795097 > ____________________________________________________________________________________ It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. http://tools.search.yahoo.com/toolbar/features/mail/ ____________________________________________________________________________________ Looking for earth-friendly autos? Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center. http://autos.yahoo.com/green_center/
