Hello Marvin Stodolsky. PCLInuxOS is based on Mandriva. If there is a solution for Mandriva, maybe I can try that. As for Jacques' solution about the unistd.h, I did find the file in my install, but unfortunately I could not figure out where to put the line "#include <asm/unistd.h>". His file is just a few lines while mine is quite a few... Thanks. On Thursday 04 January 2007 23:15, you wrote: > Syed, > > I'm not familiar with pclinuxos > You may have to update kernel-developement files to install the > unistd.h Jacques refers to. In Debian related distros this package is > called libuclibc-dev > pclinuxos should have some tool for searching the package lists for > unistd.h > > The modem should definintely be supported. > > MarvS > > On 1/4/07, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote: > > Syed, > > > > The compilation error is due to missing definition of system calls > > __NT_timer_create and __NT_timer_timeset available in the system sources > > include file named asm/unistd.h > > > > To find this file in your computer, use the find command AS ROOT (or you > > get thousands of errors for files which a general user is not allowed to > > see): > > find /usr/src -name unistd.h > > > > In my different Linux distribution and kernel version, this file > > asm/unistd.h is loaded by command #include <asm/unistd.h> which is part > > of the file linux/unistd.h > > > > I have attached my own linux/unistd.h > > I suggest that: > > 1-you verify with the find command that you do have a file asm/unistd.h > > in your machine. > > 2-compare your file linux/unistd.h with mine. > > 3-IF and ONLY IF there is no other difference than the line > > #include <asm/unistd.h> probably missing in your linux/unistd.h, then > > just add this line and try to compile. > > 4-if the file linux/unistd.h is NOT found in your machine, add mine in > > the relevant directory ..../include/linux/ > > If you cannot identify this directory, use find /usr/src -name linux > > 5-YOU DO NOT PLAY WITH THE FILE ../include/asm/unistd.h > > 6-YOU MAKE A COPY of your ../include/linux/unistd.h BEFORE MAKING ANY > > CHANGE IN IT. No need to write why. > > > > Jacques > > > > Syed Karim wrote: > > > Here is an updated ModemData.txt, Jacques Goldberg. Let me know if its > > > possible to make this modem work. > > > > > > > > > Only plain text email is forwarded by the DISCUSS@xxxxxxxxxxxxx List > > > Server. Do use the following as the email Subject Line: > > > SomeName, YourCountry pclinuxos Linux release 2006 (Texstar) > > > for i586 > > > Kernel 2.6.16.27.tex1.lve on an i686 / kernel 2.6.16.27.tex1.lve > > > 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 > > > ---------------------------- 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 > > > > > > > > > USB modem not detected by lsusb > > > > > > Modem or host audio card candidates have firmware information: > > > > > > PCI slot PCI ID SubsystemID Name > > > ---------- --------- --------- -------------- > > > 00:03.1 115d:000c 8086:2408 Serial controller: Xircom > > > Mini-PCI V.90 56k Modem > > > > > > Modem interrupt assignment and sharing: > > > 11: 1045 XT-PIC uhci_hcd:usb1, yenta, yenta, eth0, > > > CS46XX > > > > > > --- Bootup diagnositcs for card in PCI slot 00:03.1 ---- > > > ACPI: PCI Interrupt 0000:00:03.1[A] -> Link [LNKC] -> GSI 11 (level, > > > low) -> IRQ 11 > > > > > > === Finished modem firmware and bootup diagnostics section. === > > > === Next deducing cogent software === > > > > > > For candidate modem in PCI bus: 00:03.1 > > > Class 0700: 115d:000c Serial controller: Xircom Mini-PCI V.90 56k > > > Modem Primary PCI_id 115d:000c > > > Support type needed or chipset: Agere.DSP > > > > > > > > > > > > The modem has a supported Lucent/Agere Mars or Apollo DSP (digital > > > signal processing) chipset. Support packages for 2.6.n kernels are at: > > > http://phep2.technion.ac.il/linmodems/packages/ltmodem/kernel-2.6/marti > > >an/ For a temporary fix for 2.6.18 kernels see > > > > > > See AgereDSP.txt for Details. > > > DSP=1 > > > > > > Vendor 115d is XIRCOM, which was purchased by Intel > > > The following devices have Lucent/AgereSystems DSP chipsets supported > > > by the Martian variant of the AgereSystems ltmodem software. > > > > > > XIRCOM 0x115d 0x0000-0x000F > > > XIRCOM 0x115d 0x0440-0x045c > > > XIRCOM 0x115d 0x0010-0x03ff > > > > > > > > > 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 > > > > > > > > > Checking pppd properties: > > > -rwsr-xr-t 1 root root 300248 Jul 23 18: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: > > > slmodemd created symbolic link /dev/ttySL0: > > > Within /etc/udev/ files: > > > /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 -------- -- Syed
