Установив пакунок kernel-source, після чого система почала виконувати команду make без помилок.
The kernel was compiled with gcc version 4.2.1 and a compiler is not installedlinux-headers-2.6.22.5-31-default resources needed for compiling are not manifestly ready!If compiling is necessary packages must be installed, providing: gcc-4.2 kernel-source-2.6.22.5-31-default
# Blacklist of modules without the supported flag.blacklist slusb unsupportedblacklist slamr unsupportedblacklist ungrab_winmodem unsupported
# Blacklist of modules without the supported flag.#blacklist slusb unsupported#blacklist slamr unsupported#blacklist ungrab_winmodem unsupported
First complete compiling report by installing packagelinux-headers-2.6.22.5-31-default or equivalent.Next from http://linmodems.technion.ac.il/packages/smartlink/ download theungrab-winmodem-20080126.tar.gzslmodem-2.9.11-20080401.tar.gzUnder linux, unpack with:$ tar zxf *.tar.gzRead the directions, compile and install.Be careful that the device /dev/slamr0 has to be recreated upon each bootup:# mknod -m 660 /dev/slamr0 c 242 0 2until automation is establishedThen setup the modem with:# modprobe ungrab-winmodem# modprobe slamr# slmodemd -c RUSSIA /dev/slamr0For# lspci -s 02:0c.0 -n02:0c.0 Class 0703: 1057:3052get explaining documentation by running:$ ./scanModem fake 1057:3052Meanwhile I'll deduce why my automation in scanModem failed.
UPDATE=2008_04_16 Continuing as this update is a only 1 weeks old, but the current Update is always at: http://linmodems.technion.ac.ilALSA sound/drivers/opl3/opl3_lib.c:125: OPL3: stat2 = 0x0ALSA sound/drivers/opl3/opl3_lib.c:442: OPL2/3 chip not detected at 0xc050/0xc052Identifying PCI bus slots with candidate modems.Running PCIbus casesAnalysing card in PCI bus 02:0c.0, writing to scanout.02:0c.0Using scanout.02:0c.0 data, and writing guidance to ModemData.txtRead Smartlink.txtWriting Smartlink.txt Writing residual guidance customized to your System. A subfolder Modem/ has been written, containing these files with more detailed Information: ------------------------------------------------------------------------------------------ 1stRead.txt DriverCompiling.txt InfoGeneral.txt ModemData.txtRational.txt scanout.02:0c.0 Smartlink.txt SoftModem.txtTesting.txt UNSUBSCRIBE.txt wvdial.txt YourSystem.txt------------------------------------------------------------------------------------------- Please read 1stRead.txt first for Guidance.
Only plain text email is forwarded by the Discuss@Linmodems.org List Server, as HTML can contain viruses. Use as the email Subject Line: YourName, YourCountry Welcome to openSUSE 10.3 (i586) - Kernel kernel 2.6.22.5-31-default With this Subject Line cogent experts will be alerted, and useful case names left in the Archive. YourCountry will enable Country specific guidance. Your contry's local Linux experts 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@Linmodems.org 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, Welcome to openSUSE 10.3 (i586) - Kernel Linux version 2.6.22.5-31-default (geeko@buildhost) (gcc version 4.2.1 (SUSE Linux)) #1 SMP 2007/09/21 22:29:00 UTC scanModem update of: 2008_04_16 There are no blacklisted modem drivers in /etc/modprobe* files USB modem not detected by lsusbFor candidate card in slot 02:0c.0, firmware information and bootup diagnostics are: PCI slot PCI ID SubsystemID Name ---------- --------- --------- -------------- 02:0c.0 1057:3052 1057:3020 Modem: Motorola SM56 Data Fax Modem Modem interrupt assignment and sharing: --- Bootup diagnostics for card in PCI slot 02:0c.0 ----ACPI: PCI Interrupt 0000:02:0c.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 100000:02:0c.0: ttyS2 at I/O 0xc808 (irq = 10) is a 164500000:02:0c.0: ttyS3 at I/O 0xc810 (irq = 10) is a 8250Couldn't register serial port 0000:02:0c.0: -28=== Finished firmware and bootup diagnostics, next deducing cogent software. ===Predictive diagnostics for card in bus 02:0c.0: Modem chipset detected onCLASS="Class 0703: 1057:3052"NAME="Modem: Motorola SM56 Data Fax Modem "PCIDEV=1057:3052SUBSYS=1057:3020IRQ=10IDENT=slamr For candidate modem in: 02:0c.0 Class 0703: 1057:3052 Modem: Motorola SM56 Data Fax Modem Primary PCI_id 1057:3052 Support type needed or chipset: slamr ----------------end Softmodem section -------------- 1057:3052 has a Motorola chipset, poorly supported by Motorola itself However Zello discovered that drivers written to support Smartlink modems do support the 1057:3052 chipset!! It sufficed to add 1057:3052 to the list of modem cards recognized by the Smartlink slamr driver. There is a ungrab-winmodem driver used in conjunction with slamr, which must have 1057:3052 similarly added. See messages from Zello: http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00846.html http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00848.html and Alvaro Aguirre about the ungrab-winmodem fix: http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00990.html For general guidance on ungrab-winmodem + slamr usage, read the Smartlink.txtThe modem is supported by the Smartlink slamr driverplus the slmodemd helper utility. Read theSmartlink.txt and Modem/YourSystem.txt for follow through guidance.For 2.6.22.5-31-default compiling drivers is necessary. As of October 2007 the current packages athttp://linmodems.technion.ac.il/packages/smartlink/ are theungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20080126.tar.gzWriting Smartlink.txt============ end Smartlink section ===================== Completed candidate modem analyses. The base of the UDEV device file system is: /dev/.udev Versions adequately match for the compiler installed: 4.2.1 and the compiler used in kernel assembly: 4.2.1 Minimal compiling resources appear complete: make utility - /usr/bin/make Compiler version 4.2 linuc_headers base folder /lib/modules/2.6.22.5-31-default/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. If a driver compilation fails, with message including some lack of some FileName.h (stdio.h for example), thenSome additional kernel-header files need installation to /usr/include. The minimal additional packages are libc6-devand any of its dependents, under Ubuntu linux-libc-devIf an alternate ethernet connection is available,$ apt-get update$ apt-get -s install linux-kernel-develwill install needed packageFor Debian/Ubuntu related distributions, run the following command to display the needed package list:Otherwise packages have to be found through http://packages.ubuntu.comOnce downloaded and transferred into a Linux partition,they can be installed alltogether with:$ sudo dpkg -i *.debChecking pppd properties: -rwxr-xr-x 1 root dialout 298784 2007-09-22 02:41 /usr/sbin/pppdIn case of an "error 17" "serial loopback" problem, see: http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.htmlTo enable dialout without Root permission do: $ su - root (not for Ubuntu) chmod a+x /usr/sbin/pppdor under Ubuntu related Linuxes chmod a+x /usr/sbin/pppdChecking settings of: /etc/ppp/optionsnoipdefaultnoauthcrtsctslockmodemasyncmap 0nodetachlcp-echo-interval 30lcp-echo-failure 4lcp-max-configure 60lcp-restart 2idle 600noipxfile /etc/ppp/filtersIn case of a message like: Warning: Could not modify /etc/ppp/pap-secrets: Permission deniedsee http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.htmlRead Modem/YourSystem.txt concerning other COMM channels: eth0 modem1Which can interfere with Browser naviagation. Don't worry about the following, it is for the 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/50-udev-default.rules:KERNEL=="mwave", NAME="modems/%k", GROUP="uucp"/etc/udev/rules.d/77-network.rules:SUBSYSTEM=="net", ENV{INTERFACE}=="ppp*|ippp*|isdn*|plip*|lo*|irda*|dummy*|ipsec*|tun*|tap*|bond*|vlan*|modem*|dsl*", GOTO="skip_ifup" Within /etc/modprobe.conf files:/etc/modprobe.conf:# Linux ACP modem (Mwave) Within any ancient /etc/devfs files: Within ancient kernel 2.4.n /etc/module.conf files:--------- end modem support lines --------
When 'slmodemd' is running this creates PTY (pseudo-terminal) to emulate modem port device, also this creates symbolic link like '/dev/ttySL0' (shown at startup).