It doesn't work (yet) on the 2.6.3* kernels. As an alternative, you can downgrade just the kernel back to 2.6.27 or 2.6.28 (whatever you had in your previous Ubuntu 9.04 install) and use the old drivers that you mention on http://forum.ubuntu.ru/index.php?topic=56349.0 Otherwise, you will have to wait till the driver code is hacked some more to be in-sync with the current kernel developments. -- Nick Zhuravlev www.auriga.com On Sat, Dec 05, 2009 at 03:08:16PM +0300, Плашинов Дмитрий <bulldog1972@xxxxxxx> wrote: > Добрый день пожалуйста помогите разобраться с этим модемом (чип > 11с11040) в ubuntu 9.04 все прекрасно работало а в 9.10 никак завести не > могу, в 9.04 устанавливал так > http://forum.ubuntu.ru/index.php?topic=56349.0 и все прекрасно работало > а в 9.10 по всякому пробовал > (http://forum.ubuntu.ru/index.php?topic=74024.msg579263#msg579263) ну > никак не хочет. > Заранее признателен Плашинов Дмитрий > ACER Aspire 4720Z - ноутбук > CLASS=0403 > NAME="Audio device: Intel Corporation 82801H " > PCIDEV=8086:284b > SUBSYS=1025:011d > IRQ=22 > HDA=8086:284b > SOFT=8086:284b.HDA > CodecDiagnosed= > slamrTest= > HDAchipVendorID=11c1 > CHIP=0x11c11040 > CodecClass= > IDENT=agrsm > Driver=agrsm > DRIVER=agrsm > 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.31-15-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, > Linux version 2.6.31-15-generic (buildd@rothera) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #50-Ubuntu SMP Tue Nov 10 14:54:29 UTC 2009 > scanModem update of: 2009_11_26 > > > The dkms driver upgrade utilities are installed, > > 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 0458:0046 KYE Systems Corp. (Mouse Systems) > ID 064e:a101 Suyin Corp. Acer CrystalEye Webcam > 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 > > 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 1025:011d Audio device: Intel Corporation 82801H > > Modem interrupt assignment and sharing: > 22: 4616 517 IO-APIC-fasteoi HDA Intel > --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- > [ 1.155359] pci 0000:00:1b.0: reg 10 64bit mmio: [0xf0500000-0xf0503fff] > [ 1.155433] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold > [ 1.155439] pci 0000:00:1b.0: PME# disabled > [ 20.411354] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 > [ 20.411416] HDA Intel 0000:00:1b.0: setting latency timer to 64 > [ 20.489509] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input9 > > 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 ALSA verion is 1.0.20 > The modem cards detected by "aplay -l" are: None > > > The /proc/asound/pcm file reports: > ----------------------- > 00-00: ALC268 Analog : ALC268 Analog : playback 1 : capture 1 > 00-01: ALC268 Digital : ALC268 Digital : playback 1 > 00-02: ALC268 Analog : ALC268 Analog : capture 1 > > about /proc/asound/cards: > ------------------------ > 0 [Intel ]: HDA-Intel - HDA Intel > HDA Intel at 0xf0500000 irq 22 > > PCI slot 00:1b.0 has a High Definition Audio Card > The drivers are in the kernel modules tree at: > /lib/modules/2.6.31-15-generic/kernel/sound/pci/hda/snd-hda-intel.ko > /lib/modules/2.6.31-14-generic/kernel/sound/pci/hda/snd-hda-intel.ko > The modem codec file for the HDA card is: /proc/asound/card0/codec#1 > -------------------------------------------------------- > Codec: LSI ID 1040 > Address: 1 > Function Id: 0x2 > Vendor Id: 0x11c11040 > Subsystem Id: 0x1025011d > Revision Id: 0x100200 > Modem Function Group: 0x1 > > The audio card hosts a softmodem chip: 0x11c11040 > If not a Conexant modem, the driver agrsm with its dependent drivers: > > ---------- > provide audio + modem support with the modem chip residing on the subsystem. > Any particular card can host any one of several soft modem chips. > > === 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=1025:011d > IRQ=22 > HDA=8086:284b > SOFT=8086:284b.HDA > HDAchipVendorID=11c1 > CHIP=0x11c11040 > IDENT=agrsm > Driver=agrsm > > For candidate modem in: 00:1b.0 > 0403 Audio device: Intel Corporation 82801H > Primary device ID: 8086:284b > Subsystem PCI_id 1025:011d > Softmodem codec or chipset from diagnostics: 0x11c11040 > from Archives: > The HDA card softmodem chip is 0x11c11040 > > > Support type needed or chipset: agrsm > > > Writing DOCs/Intel.txt > > The AgereSystems/LSI agrsm code supports compiling of a agrmodem + agrserial driver pair. > There are a few different chipsets which use this driver pair, but they use different code resources: > Chipsets KV* PackageNames (most current as of November 2009) > ---------------------------------------------------------------------------------------------- > 11c1:048c and 11c1:048f 2.6.29 agrsm048pci-2.1.60_20091022_i386.deb or agrsm048pci-2.1.60_20091022.tar.gz > 11c1:0620 2.6.28 agrsm06pci_2.1.80~20090825_i386.deb or agrsm06pci_2.1.80~20090825_i386.tar.gz > 11c11040 (on HDA audio cards) 2.6.27 dkms-agrsm_2.1.80-9mdv2009.0_i386.deb or agrsm-2.1.80-10mdv2009.0.tar.gz > All available at: http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ , whereat additionally > automation & testing agrsm-tools_0.0.1_all.deb or agrsm-tools-0.0.1-2.noarch.rpm > General background agrsm_howto.txt > for rpm variants of dkms-agrsm , see http://linux.zsolttech.com/linmodem/agrsm/ > ------------------------------------------------------------------------------------------------ > * KV == latest kernel release with a reported success > > All of the above packages are dkms competent. This means that if your Linux distros dkms package > is previously installed, if provides for future updates matching forthcoming kernels. > > -------------- end Agere Systems section ------------------- > > Completed candidate modem analyses. > > The base of the UDEV device file system is: /dev/.udev > > Versions adequately match for the compiler installed: 4.4.1 > and the compiler used in kernel assembly: 4.4.1 > > > > Minimal compiling resources appear complete: > make utility - /usr/bin/make > Compiler version 4.4 > linuc_headers base folder /lib/modules/2.6.31-15-generic/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 needed. The also required headers of package libc6 are commonly installed by default. > Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev packages, for kernels 2.6.24 and later versions. > In not included on your install CD, search for them at http://packages.ubuntu.com > or comparable Repository for other Linux distros. > When compiling ALSA drivers, the utility "patch" will also be needed. > > > > > 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 277352 2009-02-20 20:25 /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 > > 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: > /etc/modprobe.d/agrsm.conf:## setup agrsm modem with only: "sudo modprobe agrserial" > /etc/modprobe.d/agrsm.conf:install agrserial /sbin/modprobe --ignore-install agrmodem ; /sbin/modprobe --ignore-install agrserial && \ > /etc/modprobe.d/agrsm.conf:remove agrserial /sbin/modprobe -r --ignore-remove agrserial ; /sbin/modprobe -r --ignore-remove agrmodem && { if test -L /dev/ttySAGR; then rm /dev/ttySAGR; fi } ; true > /etc/modprobe.d/agrsm.conf:# to automate bootup "sudo modprobe agrmodem" > /etc/modprobe.d/agrsm.conf:## to setup agrsm modem with only: "sudo modprobe agrmodem" > /etc/modprobe.d/agrsm.conf:# install agrmodem /sbin/modprobe --ignore-install agrmodem && \ > /etc/modprobe.d/agrsm.conf:## of effects of agrmodem and agrserial loading > /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 -------- > > CPU0 CPU1 > 0: 639151 7054 IO-APIC-edge timer > 1: 1928 14 IO-APIC-edge i8042 > 8: 1 0 IO-APIC-edge rtc0 > 9: 10137 229 IO-APIC-fasteoi acpi > 12: 5869 0 IO-APIC-edge i8042 > 14: 29772 384 IO-APIC-edge ata_piix > 15: 0 0 IO-APIC-edge ata_piix > 16: 2 0 IO-APIC-fasteoi uhci_hcd:usb3, ohci1394 > 17: 1314 22 IO-APIC-fasteoi mmc0, ath > 18: 0 0 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb7 > 19: 67930 154 IO-APIC-fasteoi uhci_hcd:usb6 > 21: 0 0 IO-APIC-fasteoi uhci_hcd:usb4 > 22: 4616 517 IO-APIC-fasteoi HDA Intel > 23: 20 0 IO-APIC-fasteoi ehci_hcd:usb2, uhci_hcd:usb5 > 27: 25491 1517 PCI-MSI-edge ahci > 28: 93087 627 PCI-MSI-edge i915 > 29: 27792 17 PCI-MSI-edge eth0 > NMI: 0 0 Non-maskable interrupts > LOC: 200097 424786 Local timer interrupts > SPU: 0 0 Spurious interrupts > CNT: 0 0 Performance counter interrupts > PND: 0 0 Performance pending work > RES: 185257 210909 Rescheduling interrupts > CAL: 114 200 Function call interrupts > TLB: 612 2441 TLB shootdowns > TRM: 0 0 Thermal event interrupts > THR: 0 0 Threshold APIC interrupts > MCE: 0 0 Machine check exceptions > MCP: 12 12 Machine check polls > ERR: 0 > MIS: 0 > > [ 0.000000] Initializing cgroup subsys cpuset > [ 0.000000] Initializing cgroup subsys cpu > [ 0.000000] Linux version 2.6.31-15-generic (buildd@rothera) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #50-Ubuntu SMP Tue Nov 10 14:54:29 UTC 2009 (Ubuntu 2.6.31-15.50-generic) > [ 0.000000] KERNEL supported cpus: > [ 0.000000] Intel GenuineIntel > [ 0.000000] AMD AuthenticAMD > [ 0.000000] NSC Geode by NSC > [ 0.000000] Cyrix CyrixInstead > [ 0.000000] Centaur CentaurHauls > [ 0.000000] Transmeta GenuineTMx86 > [ 0.000000] Transmeta TransmetaCPU > [ 0.000000] UMC UMC UMC UMC > [ 0.000000] BIOS-provided physical RAM map: > [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable) > [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) > [ 0.000000] BIOS-e820: 00000000000d2000 - 00000000000d4000 (reserved) > [ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) > [ 0.000000] BIOS-e820: 0000000000100000 - 000000007f6d0000 (usable) > [ 0.000000] BIOS-e820: 000000007f6d0000 - 000000007f6e1000 (ACPI NVS) > [ 0.000000] BIOS-e820: 000000007f6e1000 - 0000000080000000 (reserved) > [ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved) > [ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved) > [ 0.000000] BIOS-e820: 00000000fed00000 - 00000000fed00400 (reserved) > [ 0.000000] BIOS-e820: 00000000fed14000 - 00000000fed1a000 (reserved) > [ 0.000000] BIOS-e820: 00000000fed1c000 - 00000000fed90000 (reserved) > [ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) > [ 0.000000] BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved) > [ 0.000000] DMI present. > [ 0.000000] last_pfn = 0x7f6d0 max_arch_pfn = 0x100000 > [ 0.000000] MTRR default type: uncachable > [ 0.000000] MTRR fixed ranges enabled: > [ 0.000000] 00000-9FFFF write-back > [ 0.000000] A0000-BFFFF uncachable > [ 0.000000] C0000-D3FFF write-protect > [ 0.000000] D4000-DFFFF uncachable > [ 0.000000] E0000-FFFFF write-protect > [ 0.000000] MTRR variable ranges enabled: > [ 0.000000] 0 base 000000000 mask F80000000 write-back > [ 0.000000] 1 base 07F700000 mask FFFF00000 uncachable > [ 0.000000] 2 base 07F800000 mask FFF800000 uncachable > [ 0.000000] 3 disabled > [ 0.000000] 4 disabled > [ 0.000000] 5 disabled > [ 0.000000] 6 disabled > [ 0.000000] 7 disabled > [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 > [ 0.000000] e820 update range: 0000000000002000 - 0000000000006000 (usable) ==> (reserved) > [ 0.000000] Scanning 1 areas for low memory corruption > [ 0.000000] modified physical RAM map: > [ 0.000000] modified: 0000000000000000 - 0000000000002000 (usable) > [ 0.000000] modified: 0000000000002000 - 0000000000006000 (reserved) > [ 0.000000] modified: 0000000000006000 - 000000000009f800 (usable) > [ 0.000000] modified: 000000000009f800 - 00000000000a0000 (reserved) > [ 0.000000] modified: 00000000000d2000 - 00000000000d4000 (reserved) > [ 0.000000] modified: 00000000000e0000 - 0000000000100000 (reserved) > [ 0.000000] modified: 0000000000100000 - 000000007f6d0000 (usable) > [ 0.000000] modified: 000000007f6d0000 - 000000007f6e1000 (ACPI NVS) > [ 0.000000] modified: 000000007f6e1000 - 0000000080000000 (reserved) > [ 0.000000] modified: 00000000e0000000 - 00000000f0000000 (reserved) > [ 0.000000] modified: 00000000fec00000 - 00000000fec10000 (reserved) > [ 0.000000] modified: 00000000fed00000 - 00000000fed00400 (reserved) > [ 0.000000] modified: 00000000fed14000 - 00000000fed1a000 (reserved) > [ 0.000000] modified: 00000000fed1c000 - 00000000fed90000 (reserved) > [ 0.000000] modified: 00000000fee00000 - 00000000fee01000 (reserved) > [ 0.000000] modified: 00000000ff000000 - 0000000100000000 (reserved) > [ 0.000000] initial memory mapped : 0 - 00c00000 > [ 0.000000] init_memory_mapping: 0000000000000000-00000000377fe000 > [ 0.000000] Using x86 segment limits to approximate NX protection > [ 0.000000] 0000000000 - 0000400000 page 4k > [ 0.000000] 0000400000 - 0037400000 page 2M > [ 0.000000] 0037400000 - 00377fe000 page 4k > [ 0.000000] kernel direct mapping tables up to 377fe000 @ 7000-c000 > [ 0.000000] RAMDISK: 378a4000 - 37fef9cb > [ 0.000000] Allocated new RAMDISK: 008ad000 - 00ff89cb > [ 0.000000] Move RAMDISK from 00000000378a4000 - 0000000037fef9ca to 008ad000 - 00ff89ca > [ 0.000000] ACPI: RSDP 000f7ae0 00024 (v02 PTLTD ) > [ 0.000000] ACPI: XSDT 7f6d38f1 0007C (v01 ACRSYS ACRPRDCT 06040000 LTP 00000000) > [ 0.000000] ACPI: FACP 7f6ddc2a 000F4 (v03 INTEL CRESTLNE 06040000 ALAN 00000001) > [ 0.000000] ACPI: DSDT 7f6d4de1 08DD5 (v02 INTEL CRESTLNE 06040000 MSFT 03000001) > [ 0.000000] ACPI: FACS 7f6e0fc0 00040 > [ 0.000000] ACPI: APIC 7f6ddd1e 00068 (v01 INTEL CRESTLNE 06040000 LOHR 0000005A) > [ 0.000000] ACPI: HPET 7f6ddd86 00038 (v01 INTEL CRESTLNE 06040000 LOHR 0000005A) > [ 0.000000] ACPI: MCFG 7f6dddbe 0003C (v01 INTEL CRESTLNE 06040000 LOHR 0000005A) > [ 0.000000] ACPI: APIC 7f6dddfa 00068 (v01 PTLTD APIC 06040000 LTP 00000000) > [ 0.000000] ACPI: BOOT 7f6dde62 00028 (v01 PTLTD $SBFTBL$ 06040000 LTP 00000001) > [ 0.000000] ACPI: SLIC 7f6dde8a 00176 (v01 ACRSYS ACRPRDCT 06040000 acer 00000000) > [ 0.000000] ACPI: SSDT 7f6d4b04 002DD (v01 SataRe SataAhci 00001000 INTL 20050624) > [ 0.000000] ACPI: SSDT 7f6d3f29 0025F (v01 PmRef Cpu0Tst 00003000 INTL 20050624) > [ 0.000000] ACPI: SSDT 7f6d3e83 000A6 (v01 PmRef Cpu1Tst 00003000 INTL 20050624) > [ 0.000000] ACPI: SSDT 7f6d396d 00516 (v01 PmRef CpuPm 00003000 INTL 20050624) > [ 0.000000] ACPI: BIOS bug: multiple APIC/MADT found, using 0 > [ 0.000000] ACPI: If "acpi_apic_instance=2" works better, notify linux-acpi@xxxxxxxxxxxxxxx > [ 0.000000] ACPI: Local APIC address 0xfee00000 > [ 0.000000] 1150MB HIGHMEM available. > [ 0.000000] 887MB LOWMEM available. > [ 0.000000] mapped low ram: 0 - 377fe000 > [ 0.000000] low ram: 0 - 377fe000 > [ 0.000000] node 0 low ram: 00000000 - 377fe000 > [ 0.000000] node 0 bootmap 00008000 - 0000ef00 > [ 0.000000] (9 early reservations) ==> bootmem [0000000000 - 00377fe000] > [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] > [ 0.000000] #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000] > [ 0.000000] #2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000] > [ 0.000000] #3 [0000100000 - 00008a80a0] TEXT DATA BSS ==> [0000100000 - 00008a80a0] > [ 0.000000] #4 [000009f800 - 0000100000] BIOS reserved ==> [000009f800 - 0000100000] > [ 0.000000] #5 [00008a9000 - 00008ac150] BRK ==> [00008a9000 - 00008ac150] > [ 0.000000] #6 [0000007000 - 0000008000] PGTABLE ==> [0000007000 - 0000008000] > [ 0.000000] #7 [00008ad000 - 0000ff89cb] NEW RAMDISK ==> [00008ad000 - 0000ff89cb] > [ 0.000000] #8 [0000008000 - 000000f000] BOOTMAP ==> [0000008000 - 000000f000] > [ 0.000000] found SMP MP-table at [c00f7b10] f7b10 > [ 0.000000] Zone PFN ranges: > [ 0.000000] DMA 0x00000000 -> 0x00001000 > [ 0.000000] Normal 0x00001000 -> 0x000377fe > [ 0.000000] HighMem 0x000377fe -> 0x0007f6d0 > [ 0.000000] Movable zone start PFN for each node > [ 0.000000] early_node_map[3] active PFN ranges > [ 0.000000] 0: 0x00000000 -> 0x00000002 > [ 0.000000] 0: 0x00000006 -> 0x0000009f > [ 0.000000] 0: 0x00000100 -> 0x0007f6d0 > [ 0.000000] On node 0 totalpages: 521835 > [ 0.000000] free_area_init_node: node 0, pgdat c0784940, node_mem_map c1000000 > [ 0.000000] DMA zone: 32 pages used for memmap > [ 0.000000] DMA zone: 0 pages reserved > [ 0.000000] DMA zone: 3963 pages, LIFO batch:0 > [ 0.000000] Normal zone: 1744 pages used for memmap > [ 0.000000] Normal zone: 221486 pages, LIFO batch:31 > [ 0.000000] HighMem zone: 2302 pages used for memmap > [ 0.000000] HighMem zone: 292308 pages, LIFO batch:31 > [ 0.000000] Using APIC driver default > [ 0.000000] ACPI: PM-Timer IO Port: 0x1008 > [ 0.000000] ACPI: Local APIC address 0xfee00000 > [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) > [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) > [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) > [ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) > [ 0.000000] IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23 > [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) > [ 0.000000] ACPI: IRQ0 used by override. > [ 0.000000] ACPI: IRQ2 used by override. > [ 0.000000] ACPI: IRQ9 used by override. > [ 0.000000] Enabling APIC mode: Flat. Using 1 I/O APICs > [ 0.000000] Using ACPI (MADT) for SMP configuration information > [ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000 > [ 0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs > [ 0.000000] nr_irqs_gsi: 24 > [ 0.000000] PM: Registered nosave memory: 0000000000002000 - 0000000000006000 > [ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000 > [ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000d2000 > [ 0.000000] PM: Registered nosave memory: 00000000000d2000 - 00000000000d4000 > [ 0.000000] PM: Registered nosave memory: 00000000000d4000 - 00000000000e0000 > [ 0.000000] PM: Registered nosave memory: 00000000000e0000 - 0000000000100000 > [ 0.000000] Allocating PCI resources starting at 80000000 (gap: 80000000:60000000) > [ 0.000000] NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1 > [ 0.000000] PERCPU: Embedded 14 pages at c1ffa000, static data 35612 bytes > [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 517757 > [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-15-generic root=UUID=7f47cf18-8540-4f91-9d5c-03bafb9c91dc ro quiet splash > [ 0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes) > [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) > [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) > [ 0.000000] Enabling fast FPU save and restore... done. > [ 0.000000] Enabling unmasked SIMD FPU exception support... done. > [ 0.000000] Initializing CPU#0 > [ 0.000000] allocated 10438720 bytes of page_cgroup > [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups > [ 0.000000] Initializing HighMem for node 0 (000377fe:0007f6d0) > [ 0.000000] Memory: 2043644k/2087744k available (4566k kernel code, 42820k reserved, 2142k data, 540k init, 1178440k highmem) > [ 0.000000] virtual kernel memory layout: > [ 0.000000] fixmap : 0xfff1d000 - 0xfffff000 ( 904 kB) > [ 0.000000] pkmap : 0xff800000 - 0xffc00000 (4096 kB) > [ 0.000000] vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB) > [ 0.000000] lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB) > [ 0.000000] .init : 0xc078e000 - 0xc0815000 ( 540 kB) > [ 0.000000] .data : 0xc0575b44 - 0xc078d3c8 (2142 kB) > [ 0.000000] .text : 0xc0100000 - 0xc0575b44 (4566 kB) > [ 0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok. > [ 0.000000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 > [ 0.000000] NR_IRQS:2304 nr_irqs:424 > [ 0.000000] Extended CMOS year: 2000 > [ 0.000000] Fast TSC calibration using PIT > [ 0.000000] Detected 1733.237 MHz processor. > [ 0.001487] Console: colour VGA+ 80x25 > [ 0.001490] console [tty0] enabled > [ 0.001682] hpet clockevent registered > [ 0.001687] HPET: 3 timers in total, 0 timers will be used for per-cpu timer > [ 0.001694] Calibrating delay loop (skipped), value calculated using timer frequency.. 3466.47 BogoMIPS (lpj=6932948) > [ 0.001716] Security Framework initialized > [ 0.001740] AppArmor: AppArmor initialized > [ 0.001748] Mount-cache hash table entries: 512 > [ 0.001898] Initializing cgroup subsys ns > [ 0.001904] Initializing cgroup subsys cpuacct > [ 0.001909] Initializing cgroup subsys memory > [ 0.001917] Initializing cgroup subsys freezer > [ 0.001920] Initializing cgroup subsys net_cls > [ 0.001935] CPU: L1 I cache: 32K, L1 D cache: 32K > [ 0.001938] CPU: L2 cache: 1024K > [ 0.001942] CPU: Physical Processor ID: 0 > [ 0.001943] CPU: Processor Core ID: 0 > [ 0.001948] mce: CPU supports 6 MCE banks > [ 0.001956] CPU0: Thermal monitoring handled by SMI > [ 0.001960] using mwait in idle threads. > [ 0.001968] Performance Counters: Core2 events, Intel PMU driver. > [ 0.001979] ... version: 2 > [ 0.001980] ... bit width: 40 > [ 0.001982] ... generic counters: 2 > [ 0.001984] ... value mask: 000000ffffffffff > [ 0.001986] ... max period: 000000007fffffff > [ 0.001988] ... fixed-purpose counters: 3 > [ 0.001990] ... counter mask: 0000000700000003 > [ 0.001995] Checking 'hlt' instruction... OK. > [ 0.018924] ACPI: Core revision 20090521 > [ 0.036452] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 > [ 0.077181] CPU0: Intel(R) Pentium(R) Dual CPU T2370 @ 1.73GHz stepping 0d > [ 0.080001] Booting processor 1 APIC 0x1 ip 0x6000 > [ 0.004000] Initializing CPU#1 > [ 0.004000] Calibrating delay using timer specific routine.. 3466.57 BogoMIPS (lpj=6933141) > [ 0.004000] CPU: L1 I cache: 32K, L1 D cache: 32K > [ 0.004000] CPU: L2 cache: 1024K > [ 0.004000] CPU: Physical Processor ID: 0 > [ 0.004000] CPU: Processor Core ID: 1 > [ 0.004000] mce: CPU supports 6 MCE banks > [ 0.004000] CPU1: Thermal monitoring handled by SMI > [ 0.004000] x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106 > [ 0.165551] CPU1: Intel(R) Pentium(R) Dual CPU T2370 @ 1.73GHz stepping 0d > [ 0.165569] checking TSC synchronization [CPU#0 -> CPU#1]: passed. > [ 0.168026] Brought up 2 CPUs > [ 0.168029] Total of 2 processors activated (6933.04 BogoMIPS). > [ 0.168085] CPU0 attaching sched-domain: > [ 0.168089] domain 0: span 0-1 level MC > [ 0.168092] groups: 0 1 > [ 0.168098] CPU1 attaching sched-domain: > [ 0.168100] domain 0: span 0-1 level MC > [ 0.168103] groups: 1 0 > [ 0.168192] Booting paravirtualized kernel on bare hardware > [ 0.168871] regulator: core version 0.5 > [ 0.168871] Time: 18:20:36 Date: 12/03/09 > [ 0.168871] NET: Registered protocol family 16 > [ 0.168871] EISA bus registered > [ 0.168871] ACPI: bus type pci registered > [ 0.168871] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255 > [ 0.168871] PCI: MCFG area at e0000000 reserved in E820 > [ 0.168871] PCI: Using MMCONFIG for extended config space > [ 0.168871] PCI: Using configuration type 1 for base access > [ 0.172385] bio: create slab <bio-0> at 0 > [ 0.173252] ACPI: EC: Look up EC in DSDT > [ 0.178472] ACPI: BIOS _OSI(Linux) query ignored > [ 0.180024] ACPI: EC: non-query interrupt received, switching to interrupt mode > [ 0.692007] ACPI: EC: missing confirmations, switch off interrupt mode. > [ 1.148092] ACPI: Interpreter enabled > [ 1.148099] ACPI: (supports S0 S3 S4 S5) > [ 1.148123] ACPI: Using IOAPIC for interrupt routing > [ 1.153583] ACPI: EC: GPE = 0x18, I/O: command/status = 0x66, data = 0x62 > [ 1.153586] ACPI: EC: driver started in poll mode > [ 1.153981] ACPI: No dock devices found. > [ 1.154670] ACPI Error (psargs-0359): [CDW1] Namespace lookup failure, AE_NOT_FOUND > [ 1.154678] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0._OSC] (Node f7012270), AE_NOT_FOUND > [ 1.154712] ACPI: PCI Root Bridge [PCI0] (0000:00) > [ 1.154834] pci 0000:00:02.0: reg 10 64bit mmio: [0xf0000000-0xf00fffff] > [ 1.154844] pci 0000:00:02.0: reg 18 64bit mmio: [0xd0000000-0xdfffffff] > [ 1.154850] pci 0000:00:02.0: reg 20 io port: [0x1800-0x1807] > [ 1.154906] pci 0000:00:02.1: reg 10 64bit mmio: [0xf0100000-0xf01fffff] > [ 1.155046] pci 0000:00:1a.0: reg 20 io port: [0x1820-0x183f] > [ 1.155123] pci 0000:00:1a.1: reg 20 io port: [0x1840-0x185f] > [ 1.155210] pci 0000:00:1a.7: reg 10 32bit mmio: [0xf0704800-0xf0704bff] > [ 1.155287] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold > [ 1.155294] pci 0000:00:1a.7: PME# disabled > [ 1.155359] pci 0000:00:1b.0: reg 10 64bit mmio: [0xf0500000-0xf0503fff] > [ 1.155433] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold > [ 1.155439] pci 0000:00:1b.0: PME# disabled > [ 1.155543] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold > [ 1.155549] pci 0000:00:1c.0: PME# disabled > [ 1.155656] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold > [ 1.155662] pci 0000:00:1c.1: PME# disabled > [ 1.155769] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold > [ 1.155775] pci 0000:00:1c.2: PME# disabled > [ 1.155856] pci 0000:00:1d.0: reg 20 io port: [0x1860-0x187f] > [ 1.155934] pci 0000:00:1d.1: reg 20 io port: [0x1880-0x189f] > [ 1.156023] pci 0000:00:1d.2: reg 20 io port: [0x18a0-0x18bf] > [ 1.156110] pci 0000:00:1d.7: reg 10 32bit mmio: [0xf0704c00-0xf0704fff] > [ 1.156186] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold > [ 1.156193] pci 0000:00:1d.7: PME# disabled > [ 1.156391] pci 0000:00:1f.0: quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO > [ 1.156396] pci 0000:00:1f.0: quirk: region 1180-11bf claimed by ICH6 GPIO > [ 1.156401] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0680 (mask 007f) > [ 1.156406] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 0600 (mask 003f) > [ 1.156413] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 4 PIO at 0068 (mask 0007) > [ 1.156475] pci 0000:00:1f.1: reg 10 io port: [0x00-0x07] > [ 1.156485] pci 0000:00:1f.1: reg 14 io port: [0x00-0x03] > [ 1.156494] pci 0000:00:1f.1: reg 18 io port: [0x00-0x07] > [ 1.156504] pci 0000:00:1f.1: reg 1c io port: [0x00-0x03] > [ 1.156514] pci 0000:00:1f.1: reg 20 io port: [0x1810-0x181f] > [ 1.156602] pci 0000:00:1f.2: reg 10 io port: [0x1c00-0x1c07] > [ 1.156612] pci 0000:00:1f.2: reg 14 io port: [0x18d4-0x18d7] > [ 1.156621] pci 0000:00:1f.2: reg 18 io port: [0x18d8-0x18df] > [ 1.156631] pci 0000:00:1f.2: reg 1c io port: [0x18d0-0x18d3] > [ 1.156641] pci 0000:00:1f.2: reg 20 io port: [0x18e0-0x18ff] > [ 1.156651] pci 0000:00:1f.2: reg 24 32bit mmio: [0xf0704000-0xf07047ff] > [ 1.156702] pci 0000:00:1f.2: PME# supported from D3hot > [ 1.156707] pci 0000:00:1f.2: PME# disabled > [ 1.156747] pci 0000:00:1f.3: reg 10 32bit mmio: [0x000000-0x0000ff] > [ 1.156778] pci 0000:00:1f.3: reg 20 io port: [0x1c20-0x1c3f] > [ 1.156884] pci 0000:00:1c.0: bridge io port: [0x00-0xfff] > [ 1.156891] pci 0000:00:1c.0: bridge 32bit mmio: [0x000000-0x0fffff] > [ 1.156900] pci 0000:00:1c.0: bridge 64bit mmio pref: [0x000000-0x0fffff] > [ 1.156984] pci 0000:04:00.0: reg 10 64bit mmio: [0x000000-0x00ffff] > [ 1.157182] pci 0000:00:1c.1: bridge io port: [0x00-0xfff] > [ 1.157188] pci 0000:00:1c.1: bridge 32bit mmio: [0x000000-0x0fffff] > [ 1.157197] pci 0000:00:1c.1: bridge 64bit mmio pref: [0x000000-0x0fffff] > [ 1.157432] pci 0000:05:00.0: reg 10 64bit mmio: [0x000000-0x00ffff] > [ 1.157686] pci 0000:05:00.0: PME# supported from D3hot D3cold > [ 1.157699] pci 0000:05:00.0: PME# disabled > [ 1.157825] pci 0000:00:1c.2: bridge io port: [0x00-0xfff] > [ 1.157831] pci 0000:00:1c.2: bridge 32bit mmio: [0x000000-0x0fffff] > [ 1.157841] pci 0000:00:1c.2: bridge 64bit mmio pref: [0x000000-0x0fffff] > [ 1.157914] pci 0000:0a:09.0: reg 10 32bit mmio: [0xf0400000-0xf04007ff] > [ 1.157987] pci 0000:0a:09.0: supports D1 D2 > [ 1.157990] pci 0000:0a:09.0: PME# supported from D0 D1 D2 D3hot D3cold > [ 1.157996] pci 0000:0a:09.0: PME# disabled > [ 1.158046] pci 0000:0a:09.1: reg 10 32bit mmio: [0xf0400800-0xf04008ff] > [ 1.158117] pci 0000:0a:09.1: supports D1 D2 > [ 1.158119] pci 0000:0a:09.1: PME# supported from D0 D1 D2 D3hot D3cold > [ 1.158125] pci 0000:0a:09.1: PME# disabled > [ 1.158176] pci 0000:0a:09.2: reg 10 32bit mmio: [0xf0400c00-0xf0400cff] > [ 1.158248] pci 0000:0a:09.2: supports D1 D2 > [ 1.158250] pci 0000:0a:09.2: PME# supported from D0 D1 D2 D3hot D3cold > [ 1.158256] pci 0000:0a:09.2: PME# disabled > [ 1.158308] pci 0000:0a:09.3: reg 10 32bit mmio: [0xf0401000-0xf04010ff] > [ 1.158380] pci 0000:0a:09.3: supports D1 D2 > [ 1.158382] pci 0000:0a:09.3: PME# supported from D0 D1 D2 D3hot D3cold > [ 1.158388] pci 0000:0a:09.3: PME# disabled > [ 1.158439] pci 0000:0a:09.4: reg 10 32bit mmio: [0xf0401400-0xf04014ff] > [ 1.158511] pci 0000:0a:09.4: supports D1 D2 > [ 1.158513] pci 0000:0a:09.4: PME# supported from D0 D1 D2 D3hot D3cold > [ 1.158519] pci 0000:0a:09.4: PME# disabled > [ 1.158583] pci 0000:00:1e.0: transparent bridge > [ 1.158593] pci 0000:00:1e.0: bridge 32bit mmio: [0xf0400000-0xf04fffff] > [ 1.158632] pci_bus 0000:00: on NUMA node 0 > [ 1.158638] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] > [ 1.158921] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT] > [ 1.159010] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT] > [ 1.159090] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP03._PRT] > [ 1.159219] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT] > [ 1.159324] ACPI Error (psargs-0359): [CDW1] Namespace lookup failure, AE_NOT_FOUND > [ 1.159331] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0._OSC] (Node f7012270), AE_NOT_FOUND > [ 1.172412] ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 *5 6 7 10 12 14 15) > [ 1.172535] ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 11 12 14 15) *10 > [ 1.172655] ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 *10 12 14 15) > [ 1.172774] ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 11 12 14 15) *10 > [ 1.172893] ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled. > [ 1.173012] ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 *11 12 14 15) > [ 1.173130] ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12 14 15) *11 > [ 1.173248] ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 *7 11 12 14 15) > [ 1.173471] SCSI subsystem initialized > [ 1.173509] libata version 3.00 loaded. > [ 1.173509] usbcore: registered new interface driver usbfs > [ 1.173509] usbcore: registered new interface driver hub > [ 1.173509] usbcore: registered new device driver usb > [ 1.173509] ACPI: WMI: Mapper loaded > [ 1.173509] PCI: Using ACPI for IRQ routing > [ 1.173509] pci 0000:00:1c.0: BAR 13: can't allocate resource > [ 1.173509] pci 0000:00:1c.0: BAR 14: can't allocate resource > [ 1.173509] pci 0000:00:1c.0: BAR 15: can't allocate resource > [ 1.173509] pci 0000:00:1c.1: BAR 13: can't allocate resource > [ 1.173509] pci 0000:00:1c.1: BAR 14: can't allocate resource > [ 1.173509] pci 0000:00:1c.1: BAR 15: can't allocate resource > [ 1.173509] pci 0000:00:1c.2: BAR 13: can't allocate resource > [ 1.173509] pci 0000:00:1c.2: BAR 14: can't allocate resource > [ 1.173509] pci 0000:00:1c.2: BAR 15: can't allocate resource > [ 1.184011] Bluetooth: Core ver 2.15 > [ 1.184029] NET: Registered protocol family 31 > [ 1.184029] Bluetooth: HCI device and connection manager initialized > [ 1.184029] Bluetooth: HCI socket layer initialized > [ 1.184029] NetLabel: Initializing > [ 1.184029] NetLabel: domain hash size = 128 > [ 1.184029] NetLabel: protocols = UNLABELED CIPSOv4 > [ 1.184041] NetLabel: unlabeled traffic allowed by default > [ 1.184077] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0 > [ 1.184084] hpet0: 3 comparators, 64-bit 14.318180 MHz counter > [ 1.192028] Switched to high resolution mode on CPU 0 > [ 1.193591] Switched to high resolution mode on CPU 1 > [ 1.200022] pnp: PnP ACPI init > [ 1.200046] ACPI: bus type pnp registered > [ 1.203249] pnp: PnP ACPI: found 11 devices > [ 1.203252] ACPI: ACPI bus type pnp unregistered > [ 1.203256] PnPBIOS: Disabled by ACPI PNP > [ 1.203270] system 00:01: iomem range 0xfed1c000-0xfed1ffff has been reserved > [ 1.203274] system 00:01: iomem range 0xfed14000-0xfed17fff has been reserved > [ 1.203278] system 00:01: iomem range 0xfed18000-0xfed18fff has been reserved > [ 1.203281] system 00:01: iomem range 0xfed19000-0xfed19fff has been reserved > [ 1.203285] system 00:01: iomem range 0xe0000000-0xefffffff has been reserved > [ 1.203288] system 00:01: iomem range 0xfed20000-0xfed3ffff has been reserved > [ 1.203291] system 00:01: iomem range 0xfed40000-0xfed44fff has been reserved > [ 1.203295] system 00:01: iomem range 0xfed45000-0xfed8ffff has been reserved > [ 1.203302] system 00:04: iomem range 0xfed00000-0xfed003ff has been reserved > [ 1.203311] system 00:06: ioport range 0x680-0x69f has been reserved > [ 1.203314] system 00:06: ioport range 0x800-0x80f has been reserved > [ 1.203317] system 00:06: ioport range 0x1000-0x107f has been reserved > [ 1.203321] system 00:06: ioport range 0x1180-0x11bf has been reserved > [ 1.203328] system 00:06: ioport range 0x1640-0x164f has been reserved > [ 1.203331] system 00:06: ioport range 0xfe00-0xfe00 has been reserved > [ 1.238041] AppArmor: AppArmor Filesystem Enabled > [ 1.238138] pci 0000:00:1c.0: PCI bridge, secondary bus 0000:02 > [ 1.238141] pci 0000:00:1c.0: IO window: disabled > [ 1.238148] pci 0000:00:1c.0: MEM window: disabled > [ 1.238154] pci 0000:00:1c.0: PREFETCH window: disabled > [ 1.238170] pci 0000:00:1c.1: PCI bridge, secondary bus 0000:04 > [ 1.238173] pci 0000:00:1c.1: IO window: disabled > [ 1.238181] pci 0000:00:1c.1: MEM window: 0x80000000-0x800fffff > [ 1.238186] pci 0000:00:1c.1: PREFETCH window: disabled > [ 1.238248] pci 0000:00:1c.2: PCI bridge, secondary bus 0000:05 > [ 1.238250] pci 0000:00:1c.2: IO window: disabled > [ 1.238258] pci 0000:00:1c.2: MEM window: 0x80100000-0x801fffff > [ 1.238263] pci 0000:00:1c.2: PREFETCH window: disabled > [ 1.238269] pci 0000:00:1e.0: PCI bridge, secondary bus 0000:0a > [ 1.238272] pci 0000:00:1e.0: IO window: disabled > [ 1.238279] pci 0000:00:1e.0: MEM window: 0xf0400000-0xf04fffff > [ 1.238285] pci 0000:00:1e.0: PREFETCH window: disabled > [ 1.238303] alloc irq_desc for 17 on node -1 > [ 1.238305] alloc kstat_irqs on node -1 > [ 1.238312] pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > [ 1.238321] pci 0000:00:1c.0: setting latency timer to 64 > [ 1.238331] pci 0000:00:1c.1: enabling device (0000 -> 0002) > [ 1.238336] alloc irq_desc for 16 on node -1 > [ 1.238338] alloc kstat_irqs on node -1 > [ 1.238342] pci 0000:00:1c.1: PCI INT B -> GSI 16 (level, low) -> IRQ 16 > [ 1.238350] pci 0000:00:1c.1: setting latency timer to 64 > [ 1.238360] pci 0000:00:1c.2: enabling device (0000 -> 0002) > [ 1.238364] alloc irq_desc for 18 on node -1 > [ 1.238366] alloc kstat_irqs on node -1 > [ 1.238370] pci 0000:00:1c.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 > [ 1.238378] pci 0000:00:1c.2: setting latency timer to 64 > [ 1.238388] pci 0000:00:1e.0: setting latency timer to 64 > [ 1.238394] pci_bus 0000:00: resource 0 io: [0x00-0xffff] > [ 1.238397] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff] > [ 1.238400] pci_bus 0000:02: resource 0 mem: [0x0-0xfff] > [ 1.238403] pci_bus 0000:02: resource 1 mem: [0x0-0xfffff] > [ 1.238406] pci_bus 0000:02: resource 2 mem: [0x0-0xfffff] > [ 1.238409] pci_bus 0000:04: resource 0 mem: [0x0-0xfff] > [ 1.238412] pci_bus 0000:04: resource 1 mem: [0x80000000-0x800fffff] > [ 1.238415] pci_bus 0000:04: resource 2 mem: [0x0-0xfffff] > [ 1.238417] pci_bus 0000:05: resource 0 mem: [0x0-0xfff] > [ 1.238420] pci_bus 0000:05: resource 1 mem: [0x80100000-0x801fffff] > [ 1.238423] pci_bus 0000:05: resource 2 mem: [0x0-0xfffff] > [ 1.238426] pci_bus 0000:0a: resource 1 mem: [0xf0400000-0xf04fffff] > [ 1.238429] pci_bus 0000:0a: resource 3 io: [0x00-0xffff] > [ 1.238432] pci_bus 0000:0a: resource 4 mem: [0x000000-0xffffffff] > [ 1.238476] NET: Registered protocol family 2 > [ 1.238590] IP route cache hash table entries: 32768 (order: 5, 131072 bytes) > [ 1.238977] TCP established hash table entries: 131072 (order: 8, 1048576 bytes) > [ 1.239504] TCP bind hash table entries: 65536 (order: 7, 524288 bytes) > [ 1.239898] TCP: Hash tables configured (established 131072 bind 65536) > [ 1.239901] TCP reno registered > [ 1.240071] NET: Registered protocol family 1 > [ 1.240159] Trying to unpack rootfs image as initramfs... > [ 1.457452] Freeing initrd memory: 7470k freed > [ 1.463550] Simple Boot Flag at 0x35 set to 0x1 > [ 1.463768] cpufreq-nforce2: No nForce2 chipset. > [ 1.463800] Scanning for low memory corruption every 60 seconds > [ 1.463929] audit: initializing netlink socket (disabled) > [ 1.463951] type=2000 audit(1259864437.460:1): initialized > [ 1.473810] highmem bounce pool size: 64 pages > [ 1.473817] HugeTLB registered 4 MB page size, pre-allocated 0 pages > [ 1.475527] VFS: Disk quotas dquot_6.5.2 > [ 1.475596] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) > [ 1.476245] fuse init (API version 7.12) > [ 1.476342] msgmni has been set to 1706 > [ 1.476581] alg: No test for stdrng (krng) > [ 1.476598] io scheduler noop registered > [ 1.476601] io scheduler anticipatory registered > [ 1.476603] io scheduler deadline registered > [ 1.476651] io scheduler cfq registered (default) > [ 1.476666] pci 0000:00:02.0: Boot video device > [ 1.476989] alloc irq_desc for 24 on node -1 > [ 1.476991] alloc kstat_irqs on node -1 > [ 1.477006] pcieport-driver 0000:00:1c.0: irq 24 for MSI/MSI-X > [ 1.477020] pcieport-driver 0000:00:1c.0: setting latency timer to 64 > [ 1.477206] alloc irq_desc for 25 on node -1 > [ 1.477208] alloc kstat_irqs on node -1 > [ 1.477219] pcieport-driver 0000:00:1c.1: irq 25 for MSI/MSI-X > [ 1.477232] pcieport-driver 0000:00:1c.1: setting latency timer to 64 > [ 1.477412] alloc irq_desc for 26 on node -1 > [ 1.477414] alloc kstat_irqs on node -1 > [ 1.477424] pcieport-driver 0000:00:1c.2: irq 26 for MSI/MSI-X > [ 1.477437] pcieport-driver 0000:00:1c.2: setting latency timer to 64 > [ 1.477559] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > [ 1.477631] ACPI Error (psargs-0359): [CDW1] Namespace lookup failure, AE_NOT_FOUND > [ 1.477639] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0._OSC] (Node f7012270), AE_NOT_FOUND > [ 1.477722] ACPI Error (psargs-0359): [CDW1] Namespace lookup failure, AE_NOT_FOUND > [ 1.477728] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0._OSC] (Node f7012270), AE_NOT_FOUND > [ 1.477800] ACPI Error (psargs-0359): [CDW1] Namespace lookup failure, AE_NOT_FOUND > [ 1.477806] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0._OSC] (Node f7012270), AE_NOT_FOUND > [ 1.477897] ACPI Error (psargs-0359): [CDW1] Namespace lookup failure, AE_NOT_FOUND > [ 1.477903] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0._OSC] (Node f7012270), AE_NOT_FOUND > [ 1.477974] ACPI Error (psargs-0359): [CDW1] Namespace lookup failure, AE_NOT_FOUND > [ 1.477980] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0._OSC] (Node f7012270), AE_NOT_FOUND > [ 1.478051] ACPI Error (psargs-0359): [CDW1] Namespace lookup failure, AE_NOT_FOUND > [ 1.478057] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0._OSC] (Node f7012270), AE_NOT_FOUND > [ 1.478106] pciehp: PCI Express Hot Plug Controller Driver version: 0.4 > [ 1.532114] ACPI: AC Adapter [ACAD] (on-line) > [ 1.532185] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0 > [ 1.532189] ACPI: Power Button [PWRF] > [ 1.532265] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input1 > [ 1.532333] ACPI: Lid Switch [LID] > [ 1.532384] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2 > [ 1.532387] ACPI: Power Button [PWRB] > [ 1.532438] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3 > [ 1.532441] ACPI: Sleep Button [SLPB] > [ 1.533192] ACPI: SSDT 7f6d4804 00238 (v01 PmRef Cpu0Ist 00003000 INTL 20050624) > [ 1.533849] ACPI: SSDT 7f6d4188 005F7 (v01 PmRef Cpu0Cst 00003001 INTL 20050624) > [ 1.536525] Monitor-Mwait will be used to enter C-1 state > [ 1.536560] Monitor-Mwait will be used to enter C-2 state > [ 1.536586] Monitor-Mwait will be used to enter C-3 state > [ 1.536596] Marking TSC unstable due to TSC halts in idle > [ 1.536619] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3]) > [ 1.536650] processor LNXCPU:00: registered as cooling_device0 > [ 1.536655] ACPI: Processor [CPU0] (supports 8 throttling states) > [ 1.537078] ACPI: SSDT 7f6d4a3c 000C8 (v01 PmRef Cpu1Ist 00003000 INTL 20050624) > [ 1.537530] ACPI: SSDT 7f6d477f 00085 (v01 PmRef Cpu1Cst 00003000 INTL 20050624) > [ 1.538709] ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3]) > [ 1.538740] processor LNXCPU:01: registered as cooling_device1 > [ 1.538745] ACPI: Processor [CPU1] (supports 8 throttling states) > [ 1.764070] thermal LNXTHERM:01: registered as thermal_zone0 > [ 1.764082] ACPI: Thermal Zone [THRM] (86 C) > [ 1.764152] isapnp: Scanning for PnP cards... > [ 1.776102] ACPI: Battery Slot [BAT1] (battery absent) > [ 2.118364] isapnp: No Plug & Play device found > [ 2.119750] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled > [ 2.121334] brd: module loaded > [ 2.121853] loop: module loaded > [ 2.121938] input: Macintosh mouse button emulation as /devices/virtual/input/input4 > [ 2.122032] ahci 0000:00:1f.2: version 3.0 > [ 2.122052] alloc irq_desc for 19 on node -1 > [ 2.122055] alloc kstat_irqs on node -1 > [ 2.122063] ahci 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19 > [ 2.122108] alloc irq_desc for 27 on node -1 > [ 2.122110] alloc kstat_irqs on node -1 > [ 2.122121] ahci 0000:00:1f.2: irq 27 for MSI/MSI-X > [ 2.122203] ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 3 ports 3 Gbps 0x7 impl SATA mode > [ 2.122207] ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pio slum part > [ 2.122214] ahci 0000:00:1f.2: setting latency timer to 64 > [ 2.122513] scsi0 : ahci > [ 2.122637] scsi1 : ahci > [ 2.122706] scsi2 : ahci > [ 2.122838] ata1: SATA max UDMA/133 abar m2048@0xf0704000 port 0xf0704100 irq 27 > [ 2.122843] ata2: SATA max UDMA/133 abar m2048@0xf0704000 port 0xf0704180 irq 27 > [ 2.122847] ata3: SATA max UDMA/133 abar m2048@0xf0704000 port 0xf0704200 irq 27 > [ 2.122921] ata_piix 0000:00:1f.1: version 2.13 > [ 2.122934] ata_piix 0000:00:1f.1: PCI INT A -> GSI 19 (level, low) -> IRQ 19 > [ 2.122985] ata_piix 0000:00:1f.1: setting latency timer to 64 > [ 2.123071] scsi3 : ata_piix > [ 2.123143] scsi4 : ata_piix > [ 2.123844] ata4: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x1810 irq 14 > [ 2.123848] ata5: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x1818 irq 15 > [ 2.124938] Fixed MDIO Bus: probed > [ 2.124981] PPP generic driver version 2.4.2 > [ 2.125118] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver > [ 2.125142] ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18 > [ 2.125163] ehci_hcd 0000:00:1a.7: setting latency timer to 64 > [ 2.125167] ehci_hcd 0000:00:1a.7: EHCI Host Controller > [ 2.125224] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1 > [ 2.129136] ehci_hcd 0000:00:1a.7: debug port 1 > [ 2.129144] ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported > [ 2.129162] ehci_hcd 0000:00:1a.7: irq 18, io mem 0xf0704800 > [ 2.144020] ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00 > [ 2.144104] usb usb1: configuration #1 chosen from 1 choice > [ 2.144138] hub 1-0:1.0: USB hub found > [ 2.144147] hub 1-0:1.0: 4 ports detected > [ 2.144212] alloc irq_desc for 23 on node -1 > [ 2.144215] alloc kstat_irqs on node -1 > [ 2.144222] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23 > [ 2.144234] ehci_hcd 0000:00:1d.7: setting latency timer to 64 > [ 2.144238] ehci_hcd 0000:00:1d.7: EHCI Host Controller > [ 2.144275] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2 > [ 2.148176] ehci_hcd 0000:00:1d.7: debug port 1 > [ 2.148183] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported > [ 2.148199] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xf0704c00 > [ 2.160019] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00 > [ 2.160092] usb usb2: configuration #1 chosen from 1 choice > [ 2.160123] hub 2-0:1.0: USB hub found > [ 2.160130] hub 2-0:1.0: 6 ports detected > [ 2.160203] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver > [ 2.160226] uhci_hcd: USB Universal Host Controller Interface driver > [ 2.160264] uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > [ 2.160273] uhci_hcd 0000:00:1a.0: setting latency timer to 64 > [ 2.160277] uhci_hcd 0000:00:1a.0: UHCI Host Controller > [ 2.160317] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3 > [ 2.160358] uhci_hcd 0000:00:1a.0: irq 16, io base 0x00001820 > [ 2.160452] usb usb3: configuration #1 chosen from 1 choice > [ 2.160482] hub 3-0:1.0: USB hub found > [ 2.160490] hub 3-0:1.0: 2 ports detected > [ 2.160545] alloc irq_desc for 21 on node -1 > [ 2.160548] alloc kstat_irqs on node -1 > [ 2.160554] uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21 > [ 2.160562] uhci_hcd 0000:00:1a.1: setting latency timer to 64 > [ 2.160566] uhci_hcd 0000:00:1a.1: UHCI Host Controller > [ 2.160603] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4 > [ 2.160641] uhci_hcd 0000:00:1a.1: irq 21, io base 0x00001840 > [ 2.160728] usb usb4: configuration #1 chosen from 1 choice > [ 2.160758] hub 4-0:1.0: USB hub found > [ 2.160765] hub 4-0:1.0: 2 ports detected > [ 2.160824] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23 > [ 2.160832] uhci_hcd 0000:00:1d.0: setting latency timer to 64 > [ 2.160836] uhci_hcd 0000:00:1d.0: UHCI Host Controller > [ 2.160869] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 5 > [ 2.160900] uhci_hcd 0000:00:1d.0: irq 23, io base 0x00001860 > [ 2.160988] usb usb5: configuration #1 chosen from 1 choice > [ 2.161032] hub 5-0:1.0: USB hub found > [ 2.161039] hub 5-0:1.0: 2 ports detected > [ 2.161097] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 > [ 2.161104] uhci_hcd 0000:00:1d.1: setting latency timer to 64 > [ 2.161108] uhci_hcd 0000:00:1d.1: UHCI Host Controller > [ 2.161145] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 6 > [ 2.161187] uhci_hcd 0000:00:1d.1: irq 19, io base 0x00001880 > [ 2.161277] usb usb6: configuration #1 chosen from 1 choice > [ 2.161306] hub 6-0:1.0: USB hub found > [ 2.161314] hub 6-0:1.0: 2 ports detected > [ 2.161369] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 > [ 2.161377] uhci_hcd 0000:00:1d.2: setting latency timer to 64 > [ 2.161381] uhci_hcd 0000:00:1d.2: UHCI Host Controller > [ 2.161415] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 7 > [ 2.161444] uhci_hcd 0000:00:1d.2: irq 18, io base 0x000018a0 > [ 2.161535] usb usb7: configuration #1 chosen from 1 choice > [ 2.161564] hub 7-0:1.0: USB hub found > [ 2.161572] hub 7-0:1.0: 2 ports detected > [ 2.161696] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 > [ 2.165164] i8042.c: Detected active multiplexing controller, rev 1.1. > [ 2.166134] serio: i8042 KBD port at 0x60,0x64 irq 1 > [ 2.166140] serio: i8042 AUX0 port at 0x60,0x64 irq 12 > [ 2.166144] serio: i8042 AUX1 port at 0x60,0x64 irq 12 > [ 2.166147] serio: i8042 AUX2 port at 0x60,0x64 irq 12 > [ 2.166151] serio: i8042 AUX3 port at 0x60,0x64 irq 12 > [ 2.166235] mice: PS/2 mouse device common for all mice > [ 2.166388] rtc_cmos 00:07: RTC can wake from S4 > [ 2.166428] rtc_cmos 00:07: rtc core: registered rtc_cmos as rtc0 > [ 2.166464] rtc0: alarms up to one month, y3k, 242 bytes nvram, hpet irqs > [ 2.166582] device-mapper: uevent: version 1.0.3 > [ 2.166703] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@xxxxxxxxxx > [ 2.166809] device-mapper: multipath: version 1.1.0 loaded > [ 2.166812] device-mapper: multipath round-robin: version 1.0.0 loaded > [ 2.166956] EISA: Probing bus 0 at eisa.0 > [ 2.166963] Cannot allocate resource for EISA slot 1 > [ 2.166997] EISA: Detected 0 cards. > [ 2.167210] cpuidle: using governor ladder > [ 2.167353] cpuidle: using governor menu > [ 2.167932] TCP cubic registered > [ 2.168123] NET: Registered protocol family 10 > [ 2.168649] lo: Disabled Privacy Extensions > [ 2.169042] NET: Registered protocol family 17 > [ 2.169064] Bluetooth: L2CAP ver 2.13 > [ 2.169066] Bluetooth: L2CAP socket layer initialized > [ 2.169069] Bluetooth: SCO (Voice Link) ver 0.6 > [ 2.169071] Bluetooth: SCO socket layer initialized > [ 2.169120] Bluetooth: RFCOMM TTY layer initialized > [ 2.169124] Bluetooth: RFCOMM socket layer initialized > [ 2.169126] Bluetooth: RFCOMM ver 1.11 > [ 2.169836] Using IPI No-Shortcut mode > [ 2.169912] PM: Resume from disk failed. > [ 2.169927] registered taskstats version 1 > [ 2.170079] Magic number: 5:442:341 > [ 2.170189] rtc_cmos 00:07: setting system clock to 2009-12-03 18:20:38 UTC (1259864438) > [ 2.170193] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found > [ 2.170194] EDD information not available. > [ 2.195309] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input5 > [ 2.292785] ata4.00: ATAPI: HL-DT-ST DVDRAM GSA-T40N, JP01, max UDMA/33 > [ 2.308351] ata4.00: configured for UDMA/33 > [ 2.440076] ata3: SATA link down (SStatus 0 SControl 300) > [ 2.440101] ata2: SATA link down (SStatus 0 SControl 300) > [ 2.440128] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > [ 2.441143] ACPI Warning: \_SB_.PCI0.SATA.PRT0._GTF: Return type mismatch - found Integer, expected Buffer 20090521 nspredef-940 > [ 2.441152] ata1.00: _GTF unexpected object type 0x1 > [ 2.441234] ata1.00: ATA-7: ST9160821AS, 3.ALD, max UDMA/133 > [ 2.441237] ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32) > [ 2.442433] ata1.00: _GTF unexpected object type 0x1 > [ 2.442550] ata1.00: configured for UDMA/133 > [ 2.456200] scsi 0:0:0:0: Direct-Access ATA ST9160821AS 3.AL PQ: 0 ANSI: 5 > [ 2.456347] sd 0:0:0:0: Attached scsi generic sg0 type 0 > [ 2.456390] sd 0:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB) > [ 2.456442] sd 0:0:0:0: [sda] Write Protect is off > [ 2.456445] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 > [ 2.456472] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > [ 2.456613] sda: > [ 2.460293] scsi 3:0:0:0: CD-ROM HL-DT-ST DVDRAM GSA-T40N JP01 PQ: 0 ANSI: 5 > [ 2.471582] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray > [ 2.471585] Uniform CD-ROM driver Revision: 3.20 > [ 2.471681] sr 3:0:0:0: Attached scsi CD-ROM sr0 > [ 2.471729] sr 3:0:0:0: Attached scsi generic sg1 type 5 > [ 2.472064] usb 2-3: new high speed USB device using ehci_hcd and address 2 > [ 2.484283] sda1 sda2 sda3 sda4 < > [ 2.500035] Clocksource tsc unstable (delta = -251450909 ns) > [ 2.509180] sda5 sda6 > > [ 2.528606] sd 0:0:0:0: [sda] Attached SCSI disk > [ 2.528640] Freeing unused kernel memory: 540k freed > [ 2.529048] Write protecting the kernel text: 4568k > [ 2.529113] Write protecting the kernel read-only data: 1836k > [ 2.633749] usb 2-3: configuration #1 chosen from 1 choice > [ 2.696347] Linux agpgart interface v0.103 > [ 2.720773] agpgart-intel 0000:00:00.0: Intel 965GM Chipset > [ 2.721196] agpgart-intel 0000:00:00.0: detected 7676K stolen memory > [ 2.724605] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000 > [ 2.738684] ohci1394 0000:0a:09.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > [ 2.756482] tg3.c:v3.99 (April 20, 2009) > [ 2.756547] tg3 0000:05:00.0: enabling device (0000 -> 0002) > [ 2.756561] tg3 0000:05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 > [ 2.756584] tg3 0000:05:00.0: setting latency timer to 64 > [ 2.775834] tg3 0000:05:00.0: wake-up capability disabled by ACPI > [ 2.775850] tg3 0000:05:00.0: PME# disabled > [ 2.795233] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[16] MMIO=[f0400000-f04007ff] Max Packet=[2048] IR/IT contexts=[4/4] > [ 2.806797] [drm] Initialized drm 1.1.0 20060810 > [ 2.824830] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > [ 2.824837] i915 0000:00:02.0: setting latency timer to 64 > [ 2.827493] alloc irq_desc for 28 on node -1 > [ 2.827497] alloc kstat_irqs on node -1 > [ 2.827509] i915 0000:00:02.0: irq 28 for MSI/MSI-X > [ 2.830420] eth0: Tigon3 [partno(BCM95787m) rev b002] (PCI Express) MAC address 00:1e:68:30:fa:d0 > [ 2.830426] eth0: attached PHY is 5787 (10/100/1000Base-T Ethernet) (WireSpeed[1]) > [ 2.830429] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] > [ 2.830432] eth0: dma_rwctrl[76180000] dma_mask[64-bit] > [ 3.121041] usb 6-2: new low speed USB device using uhci_hcd and address 2 > [ 3.294339] usb 6-2: configuration #1 chosen from 1 choice > [ 3.313160] usbcore: registered new interface driver hiddev > [ 3.329525] input: Genius Wireless Mouse as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/input/input6 > [ 3.329619] generic-usb 0003:0458:0046.0001: input,hidraw0: USB HID v1.00 Mouse [Genius Wireless Mouse] on usb-0000:00:1d.1-2/input0 > [ 3.329637] usbcore: registered new interface driver usbhid > [ 3.329640] usbhid: v2.6:USB HID core driver > [ 3.332566] [drm] TV-14: set mode NTSC 480i 0 > [ 3.459250] [drm] fb0: inteldrmfb frame buffer device > [ 3.697215] acpi device:05: registered as cooling_device2 > [ 3.936187] acpi device:06: registered as cooling_device3 > [ 3.936410] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/input/input7 > [ 3.936460] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) > [ 3.936505] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 > [ 4.004922] [drm] LVDS-8: set mode 1280x800 17 > [ 4.029445] Console: switching to colour frame buffer device 160x50 > [ 4.147471] ieee1394: Host added: ID:BUS[0-00:1023] GUID[00241b00e8f0c800] > [ 4.411701] PM: Starting manual resume from disk > [ 4.411706] PM: Resume from partition 8:6 > [ 4.411708] PM: Checking hibernation image. > [ 4.411911] PM: Resume from disk failed. > [ 4.442528] EXT4-fs (sda5): barriers enabled > [ 4.455671] kjournald2 starting: pid 419, dev sda5:8, commit interval 5 seconds > [ 4.455684] EXT4-fs (sda5): delayed allocation enabled > [ 4.455688] EXT4-fs: file extents enabled > [ 4.457178] EXT4-fs: mballoc enabled > [ 4.457195] EXT4-fs (sda5): mounted filesystem with ordered data mode > [ 5.307468] type=1505 audit(1259864441.633:2): operation="profile_load" pid=442 name=/usr/share/gdm/guest-session/Xsession > [ 5.310472] type=1505 audit(1259864441.637:3): operation="profile_load" pid=443 name=/sbin/dhclient3 > [ 5.311318] type=1505 audit(1259864441.637:4): operation="profile_load" pid=443 name=/usr/lib/NetworkManager/nm-dhcp-client.action > [ 5.311775] type=1505 audit(1259864441.637:5): operation="profile_load" pid=443 name=/usr/lib/connman/scripts/dhclient-script > [ 5.400636] type=1505 audit(1259864441.729:6): operation="profile_load" pid=444 name=/usr/bin/evince > [ 5.414465] type=1505 audit(1259864441.741:7): operation="profile_load" pid=444 name=/usr/bin/evince-previewer > [ 5.422568] type=1505 audit(1259864441.749:8): operation="profile_load" pid=444 name=/usr/bin/evince-thumbnailer > [ 5.445436] type=1505 audit(1259864441.773:9): operation="profile_load" pid=446 name=/usr/lib/cups/backend/cups-pdf > [ 5.446424] type=1505 audit(1259864441.773:10): operation="profile_load" pid=446 name=/usr/sbin/cupsd > [ 5.458186] type=1505 audit(1259864441.785:11): operation="profile_load" pid=447 name=/usr/sbin/tcpdump > [ 19.381398] Adding 2008084k swap on /dev/sda6. Priority:-1 extents:1 across:2008084k > [ 19.413094] udev: starting version 147 > [ 19.453284] lp: driver loaded but no devices found > [ 20.102188] sdhci: Secure Digital Host Controller Interface driver > [ 20.102192] sdhci: Copyright(c) Pierre Ossman > [ 20.103784] sdhci-pci 0000:0a:09.1: SDHCI controller found [1180:0822] (rev 22) > [ 20.103806] sdhci-pci 0000:0a:09.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17 > [ 20.104841] sdhci-pci 0000:0a:09.1: Will use DMA mode even though HW doesn't fully claim to support it. > [ 20.105916] Registered led device: mmc0:: > [ 20.106968] mmc0: SDHCI controller on PCI [0000:0a:09.1] using DMA > [ 20.108967] ricoh-mmc: Ricoh MMC Controller disabling driver > [ 20.108971] ricoh-mmc: Copyright(c) Philip Langdale > [ 20.109020] ricoh-mmc: Ricoh MMC controller found at 0000:0a:09.2 [1180:0843] (rev 12) > [ 20.109041] ricoh-mmc: Controller is now disabled. > [ 20.155621] EXT4-fs (sda5): internal journal on sda5:8 > [ 20.196674] Linux video capture interface: v2.00 > [ 20.216429] uvcvideo: Found UVC 1.00 device Acer CrystalEye webcam (064e:a101) > [ 20.226580] acer-wmi: Acer Laptop ACPI-WMI Extras > [ 20.227092] acer-wmi: Brightness must be controlled by generic video driver > [ 20.230263] input: Acer CrystalEye webcam as /devices/pci0000:00/0000:00:1d.7/usb2/2-3/2-3:1.0/input/input8 > [ 20.230324] usbcore: registered new interface driver uvcvideo > [ 20.230328] USB Video Class driver (v0.1.0) > [ 20.266323] cfg80211: Calling CRDA to update world regulatory domain > [ 20.294163] ath5k 0000:04:00.0: enabling device (0000 -> 0002) > [ 20.294174] ath5k 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > [ 20.294190] ath5k 0000:04:00.0: setting latency timer to 64 > [ 20.294240] ath5k 0000:04:00.0: registered as 'phy0' > [ 20.347772] cfg80211: World regulatory domain updated: > [ 20.347777] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) > [ 20.347781] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) > [ 20.347784] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) > [ 20.347787] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) > [ 20.347790] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) > [ 20.347793] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) > [ 20.358753] ip_tables: (C) 2000-2006 Netfilter Core Team > [ 20.390943] ath: EEPROM regdomain: 0x65 > [ 20.390946] ath: EEPROM indicates we should expect a direct regpair map > [ 20.390950] ath: Country alpha2 being used: 00 > [ 20.390952] ath: Regpair used: 0x65 > [ 20.411341] alloc irq_desc for 22 on node -1 > [ 20.411345] alloc kstat_irqs on node -1 > [ 20.411354] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 > [ 20.411416] HDA Intel 0000:00:1b.0: setting latency timer to 64 > [ 20.419120] phy0: Selected rate control algorithm 'minstrel' > [ 20.419990] Registered led device: ath5k-phy0::rx > [ 20.420042] Registered led device: ath5k-phy0::tx > [ 20.420046] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70) > [ 20.489413] hda_codec: Unknown model for ALC268, trying auto-probe from BIOS... > [ 20.489509] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input9 > [ 20.681780] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) > [ 20.682012] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use > [ 20.682015] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or > [ 20.682018] sysctl net.netfilter.nf_conntrack_acct=1 to enable it. > [ 21.166285] type=1505 audit(1259853657.493:12): operation="profile_replace" pid=977 name=/usr/share/gdm/guest-session/Xsession > [ 21.182135] type=1505 audit(1259853657.509:13): operation="profile_replace" pid=1043 name=/sbin/dhclient3 > [ 21.183031] type=1505 audit(1259853657.509:14): operation="profile_replace" pid=1043 name=/usr/lib/NetworkManager/nm-dhcp-client.action > [ 21.183509] type=1505 audit(1259853657.509:15): operation="profile_replace" pid=1043 name=/usr/lib/connman/scripts/dhclient-script > [ 21.197333] type=1505 audit(1259853657.525:16): operation="profile_replace" pid=1044 name=/usr/bin/evince > [ 21.243892] type=1505 audit(1259853657.569:17): operation="profile_replace" pid=1044 name=/usr/bin/evince-previewer > [ 21.289176] type=1505 audit(1259853657.617:18): operation="profile_replace" pid=1044 name=/usr/bin/evince-thumbnailer > [ 21.329706] type=1505 audit(1259853657.657:19): operation="profile_replace" pid=1059 name=/usr/lib/cups/backend/cups-pdf > [ 21.330693] type=1505 audit(1259853657.657:20): operation="profile_replace" pid=1059 name=/usr/sbin/cupsd > [ 21.357632] type=1505 audit(1259853657.685:21): operation="profile_replace" pid=1060 name=/usr/sbin/tcpdump > [ 21.372331] ADDRCONF(NETDEV_UP): wlan0: link is not ready > [ 21.372660] Synaptics Touchpad, model: 1, fw: 6.5, id: 0x81a0b1, caps: 0xa04711/0xa04000 > [ 21.374004] tg3 0000:05:00.0: wake-up capability disabled by ACPI > [ 21.374020] tg3 0000:05:00.0: PME# disabled > [ 21.374257] alloc irq_desc for 29 on node -1 > [ 21.374260] alloc kstat_irqs on node -1 > [ 21.374293] tg3 0000:05:00.0: irq 29 for MSI/MSI-X > [ 21.415409] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input10 > [ 21.587526] ADDRCONF(NETDEV_UP): eth0: link is not ready > [ 21.600007] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x024ba000 > [ 22.400193] ppdev: user-space parallel port driver > [ 22.996711] [drm] TV-14: set mode NTSC 480i 0 > [ 23.193895] [drm] TV-14: set mode NTSC 480i 0 > [ 23.456669] [drm] TV-14: set mode NTSC 480i 0 > [ 23.597273] [drm] TV-14: set mode NTSC 480i 0 > [ 23.810047] tg3: eth0: Link is up at 10 Mbps, half duplex. > [ 23.810051] tg3: eth0: Flow control is off for TX and off for RX. > [ 23.811554] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready > [ 26.183469] [drm] TV-14: set mode NTSC 480i 0 > [ 26.323844] [drm] TV-14: set mode NTSC 480i 0 > [ 26.591158] [drm] TV-14: set mode NTSC 480i 0 > [ 26.731173] [drm] TV-14: set mode NTSC 480i 0 > [ 27.011177] [drm] TV-14: set mode NTSC 480i 0 > [ 27.151211] [drm] TV-14: set mode NTSC 480i 0 > [ 33.932050] eth0: no IPv6 routers present > [ 39.443943] [drm] TV-14: set mode NTSC 480i 0 > [ 39.585239] [drm] TV-14: set mode NTSC 480i 0 > [ 39.858172] [drm] TV-14: set mode NTSC 480i 0 > [ 39.999376] [drm] TV-14: set mode NTSC 480i 0 > [ 40.268197] [drm] TV-14: set mode NTSC 480i 0 > [ 40.408356] [drm] TV-14: set mode NTSC 480i 0 > [ 41.492229] [drm] TV-14: set mode NTSC 480i 0 > [ 41.632258] [drm] TV-14: set mode NTSC 480i 0 > [ 192.351368] [drm] TV-14: set mode NTSC 480i 0 > [ 345.090571] [drm] TV-14: set mode NTSC 480i 0 > [ 345.231418] [drm] TV-14: set mode NTSC 480i 0 > [ 494.351644] tg3: eth0: Link is down. > [ 496.742543] tg3: eth0: Link is up at 10 Mbps, half duplex. > [ 496.742551] tg3: eth0: Flow control is off for TX and off for RX. > [ 542.676483] tg3: eth0: Link is down. > [ 544.935633] tg3: eth0: Link is up at 10 Mbps, half duplex. > [ 544.935641] tg3: eth0: Flow control is off for TX and off for RX. > [ 554.437090] [drm] TV-14: set mode NTSC 480i 0 > [ 554.577467] [drm] TV-14: set mode NTSC 480i 0 > [ 554.837233] [drm] TV-14: set mode NTSC 480i 0 > [ 554.977243] [drm] TV-14: set mode NTSC 480i 0 > [ 557.341344] [drm] TV-14: set mode NTSC 480i 0 > [ 557.481383] [drm] TV-14: set mode NTSC 480i 0 > [ 557.753334] [drm] TV-14: set mode NTSC 480i 0 > [ 557.893386] [drm] TV-14: set mode NTSC 480i 0 > [ 558.167537] [drm] TV-14: set mode NTSC 480i 0 > [ 558.308592] [drm] TV-14: set mode NTSC 480i 0 > [ 566.045866] [drm] TV-14: set mode NTSC 480i 0 > [ 566.190499] [drm] TV-14: set mode NTSC 480i 0 > [ 566.464503] [drm] TV-14: set mode NTSC 480i 0 > [ 566.610810] [drm] TV-14: set mode NTSC 480i 0 > [ 566.883813] [drm] TV-14: set mode NTSC 480i 0 > [ 567.028546] [drm] TV-14: set mode NTSC 480i 0 > [ 568.058807] [drm] TV-14: set mode NTSC 480i 0 > [ 568.200153] [drm] TV-14: set mode NTSC 480i 0 > [ 1030.962269] CE: hpet increasing min_delta_ns to 15000 nsec > [ 1481.527806] sr 3:0:0:0: [sr0] unaligned transfer > [ 1481.527901] sr 3:0:0:0: [sr0] unaligned transfer > [ 1481.527971] sr 3:0:0:0: [sr0] unaligned transfer > [ 1481.527994] sr 3:0:0:0: [sr0] unaligned transfer > [ 1484.963522] UDF-fs: No VRS found > [ 1484.963530] UDF-fs: No partition found (1) > [ 1484.982370] ISO 9660 Extensions: Microsoft Joliet Level 3 > [ 1485.019686] ISO 9660 Extensions: RRIP_1991A > [ 1799.938282] UDF-fs: No VRS found > [ 1799.938292] UDF-fs: No partition found (1) > [ 1799.954115] ISO 9660 Extensions: Microsoft Joliet Level 3 > [ 1800.013822] ISO 9660 Extensions: RRIP_1991A > > Module Size Used by > isofs 31620 0 > udf 80900 0 > crc_itu_t 1852 1 udf > binfmt_misc 8356 1 > ppdev 6688 0 > joydev 10272 0 > iptable_nat 5500 0 > nf_nat 17808 1 iptable_nat > nf_conntrack_ipv4 13352 3 iptable_nat,nf_nat > nf_conntrack 67608 3 iptable_nat,nf_nat,nf_conntrack_ipv4 > nf_defrag_ipv4 1756 1 nf_conntrack_ipv4 > iptable_mangle 3452 0 > snd_hda_codec_realtek 203328 1 > arc4 1660 2 > ecb 2524 2 > snd_hda_intel 26920 2 > snd_hda_codec 75708 2 snd_hda_codec_realtek,snd_hda_intel > snd_hwdep 7200 1 snd_hda_codec > iptable_filter 3100 0 > snd_pcm_oss 37920 0 > snd_mixer_oss 16028 1 snd_pcm_oss > snd_pcm 75296 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss > ip_tables 11692 3 iptable_nat,iptable_mangle,iptable_filter > x_tables 16544 2 iptable_nat,ip_tables > snd_seq_dummy 2656 0 > ath5k 124260 0 > mac80211 181236 1 ath5k > ath 8060 1 ath5k > snd_seq_oss 28576 0 > snd_seq_midi 6432 0 > snd_rawmidi 22208 1 snd_seq_midi > snd_seq_midi_event 6940 2 snd_seq_oss,snd_seq_midi > snd_seq 50224 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event > snd_timer 22276 2 snd_pcm,snd_seq > snd_seq_device 6920 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq > acer_wmi 15936 0 > psmouse 56500 0 > serio_raw 5280 0 > uvcvideo 59080 0 > videodev 36736 1 uvcvideo > v4l1_compat 14496 2 uvcvideo,videodev > cfg80211 93052 3 ath5k,mac80211,ath > ricoh_mmc 3676 0 > sdhci_pci 7100 0 > sdhci 17472 1 sdhci_pci > led_class 4096 3 ath5k,acer_wmi,sdhci > snd 59204 16 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device > soundcore 7264 1 snd > snd_page_alloc 9156 2 snd_hda_intel,snd_pcm > lp 8964 0 > parport 35340 2 ppdev,lp > fbcon 36640 72 > tileblit 2460 1 fbcon > font 8124 1 fbcon > bitblit 5372 1 fbcon > softcursor 1756 1 bitblit > usbhid 38208 0 > i915 221064 3 > drm 159584 3 i915 > i2c_algo_bit 5760 1 i915 > tg3 109600 0 > ohci1394 29900 0 > ieee1394 86596 1 ohci1394 > intel_agp 27484 2 i915 > agpgart 34988 2 drm,intel_agp > video 19380 1 i915 > output 2780 1 video > > A modem device/card may be disabled at bootup, due to a variety of causes. > Look at the bootup diagnostics record dmesg.txt and try to garner some > understanding from it. Attach it to your query to discuss@xxxxxxxxxxxxx > Possibilities therein are too diverse to be automagically processed by > scanModem. A line including the PCI > bus slot 00:1b.0 of your modem, and "disable" or "disabling" predicts problems, > though sometimes corrected later in the bootup. Similarly a line with "@" > in the interrupt (IRQ) for your 00:1b.0 slot is predictive of problems. > > Possible corrections are: > 1) Within the boot up BIOS, change from a Windows to a non-PNP/Other Operating System type. > Instructions for accessing BIOS are at: > http://linmodems.technion.ac.il/resources.html within: Additional Resourcces. > 2a) Add an option "pci=routeirq" to the kernel boot up line. > Here is an example paragraph from /boot/grub/menu.lst : > title Ubuntu, kernel 2.6.15-26-686 > root (hd0,6) > kernel /boot/vmlinuz-2.6.15-26-686 root=/dev/hda7 ro pci=routeirq > initrd /boot/initrd.img-2.6.15-26-686 > savedefault > 2b) Same as above, but use "pollirq" instead of "pci=routeirq". > 3) Within some BIOS setups, IRQ assignments can be changed. > 4) On non-laptop systems, moving the modem card to another slot has helped. > 5) Blacklist as many drivers as possible. See > http://linmodems.technion.ac.il/bigarch/archive-eighth/msg01593.html > 6) Sometimes upgrading the kernel solves the problem. > 7) Sometimes downgrading the kernel solves the problem. > 8) Sometimes changing the Linux distribution solves the problem. > 9) Get unloading.gz from http://linmodems.technion.ac.il/linmodems/ > This script unloads excess drivers which may be competing for resources. > Before trying to set up the modem, do: > $ gunzip unloading.gz > $ chmod +x unloading > $ su - root > # ./unloading > Or for Ubuntu related Distros > $ sudo ./unloading > > > If you want help from the email group Discuss@xxxxxxxxxxxxx, PLEASE join the List > at http://www.linmodems.org . Otherwise your messages will be delayed until the evening, > waiting for someone to verify it is not junk mail, before forwarding through the List server. > > The files in this Modem/ folder have the following roles: > > ModemData.txt - Diagnostics and accumulated information cogent to your modem and host system. > This is the ONLY file which should be sent to the List DISCUSS@xxxxxxxxxxxxx , > if further help is needed. Send your email and attachments as plain text as > other formats are rejected by the List Server, to avoid virus transmission. > Always send the ENTIRE ModemData.txt, as It includes subtle diagnostic ouputs needed > to best guide you. Please in the covering email mention your Country, to enable Country > specific advice. > Always use the most recent update of scanModem accessed ONLY at > http://linmodems.technion.ac.il/packages/scanModem.gz > to produce ModemData.txt > URLs to cogent advice are regularly updated, so your problem may be solved therein. > Please Do NOT send Do NOT send other files in this folder Modem/ > > Several informative files without diagnostics are in the DOCs subfolder. > A file(s) specific to your modem chipset will be written, such as: > Smartlink.txt, Conexant.txt, Intel.txt , etc > > YourModem.txt - Guidance about operating your particular System, for your benefit > It should NOT be sent to Discuss@xxxxxxxxxxxxx > > Rational.txt - Motivations of this scanModem package. > > DriverCompiling.txt - Explains the roles of additional files which may have to be installed > to support compiling of modem drivers, and the steps to take. > > SoftModem.txt - Information and instructions about "soft modems". > For these modems, additional steps may be necessary for choice of supporting software. > The primary PCI ID is that of the host audio or modem controller, which can support diverse Subsystems. It is the chipset of the Subsystem which determines the software needed. > > ModemTesting.txt SHOULD be read, but after drivers have been installed. > > InfoGeneral.txt has general information about the status of winmodem support under Linux, > Do read it if ModemData.txt reports that your current modem is not supported under Linux. > > Unsubscribe.txt - Howto terminate email tranmissions from the List. > > If you are Linux newcomer, please do locate your local Linux group through: > http://www.linux.org/groups/index.html . If you are not comfortable with English, > a local Linux user can often be of substantial assistance in getting you on to the Internet. > > > This file should NOT be sent to Discuss@xxxxxxxxxxxxx > It has common guidance for modem usage after setup. > > > Interfererce with browser naviagation: > ------------------------------------- > Other COMM channels can interfere with browsing under dialout. > Suspect channels set during your scanModem run were shown by: ifconfig > eth0 Link encap:Ethernet HWaddr 00:1e:68:30:fa:d0 > inet addr:212.67.29.173 Bcast:212.67.31.255 Mask:255.255.252.0 > inet6 addr: fe80::21e:68ff:fe30:fad0/64 Диапазон:СÑылка > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:15513 errors:131 dropped:0 overruns:0 frame:0 > TX packets:13186 errors:0 dropped:0 overruns:0 carrier:0 > коллизии:131 txqueuelen:1000 > RX bytes:16130035 (16.1 MB) TX bytes:1601883 (1.6 MB) > Прервано:18 > > lo Link encap:Ð›Ð¾ÐºÐ°Ð»ÑŒÐ½Ð°Ñ Ð¿ÐµÑ‚Ð»Ñ (Loopback) > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Диапазон:Узел > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:15039 errors:0 dropped:0 overruns:0 frame:0 > TX packets:15039 errors:0 dropped:0 overruns:0 carrier:0 > коллизии:0 txqueuelen:0 > RX bytes:444793 (444.7 KB) TX bytes:444793 (444.7 KB) > > wlan0 Link encap:Ethernet HWaddr 00:1f:3a:97:1f:7d > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > коллизии:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > wmaster0 Link encap:UNSPEC HWaddr 00-1F-3A-97-1F-7D-00-00-00-00-00-00-00-00-00-00 > UP RUNNING MTU:0 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > коллизии:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > A block with "lo" is an internal loopback test and harmless. > > However, other COMM channels such as ethernet "eth0" will block browser function > through dialout connections. Domain Name Services (DNS) needed for browsing > will be blocked by an ineffective default usage of the eth0 assigned DNS. > > If is wisest to disable bootup establishment of alternate channels in your Control Center. > Depending on your Linux distribution, > one of the following root/admin commands may alternatively be effective: > # ifdown eth0 > # ifconfig eth0 down > # /etc/init.d/network stop > # /etc/init.d/networking stop > Be wary that some Systems will periodically try to re-establish internet. > So if browsing should suspiciously fail, recheck with > ifconfig > ---------------------------- end COMM Channels -------------------------- > Ubuntu is not yet providing pre-compiled drivers for WinModems > > The Modem/DOCs/DriverCompiling.txt is a MUST READ, > if you are not experienced in configuring kernel-source/ > or get "unresolved symbols" upon driver insertion. > > Most recent WinModem fixes are in: http://linmodems.technion.ac.il/FAQ.html > > (4) For guidance on automation see http://linmodems.technion.ac.il/archive-fourth/msg03734.html > and the scripts in the slmodem-2.9.n/scripts folder/ > > > Modem usage is accomplished through drivers, sometimes some helper software, > and the core communication work horse "pppd". Usually it will be found at > /usr/sbin/pppd with permissions shown on my Ubuntu system by: > $ ls -l /usr/sbin/pppd > -rwsr-xr-- 1 root dip 257720 2006-07-05 08:58 /usr/sbin/pppd > The s means "sticky" meaning only one person can use pppd at a time. > As installed, it requires Root/Adm permissions to use pppd, directly or > through front end dialer tools. This is a security precaution common to > all COMM channels. But if you want to enable a simple User to dialout, > as is basically OK for a single user PC, do: > $ su - root > # chmod a+x /usr/sbin/pppd > or for Ubuntu: > $ sudo chmod a+x /usr/sbin/pppd > after which there will be seen: > $ ls -l /usr/sbin/pppd > -rwsr-xr-x 1 root dip 257720 2006-07-05 08:58 /usr/sbin/pppd > with the last x meaning any one can execute pppd, either directly or > much more commonly through a front end dialer such as wvdial of KPPP. > > The preferred dialer utility for modem testing is wvdial, having a configuration utility: conf > wvdialconf is called during testing of some modem drivers. Particularly if your > modem uses the driver martian_dev of helper utility slmodemd, please install the > wvdial package!! For other drivers, dialers such as gnomeppp or kppp may be adequate. > but wvdial is still preferred for testing. > > Configuration file for wvdial > ------------------------------- > There is a very smart dialer utility "wvdial" > which can be used once basic modem setup is accomplished. A configuration file > is needed, which begins below with [Dialer defaults]. This file can be accessed > any where by: > $ wvdial --config Path_to/configuration_file > Most commonly the configuration file is saved as: > /etc/wvdial.conf > whereat it will serve all Users of the computer. If saved as: > /home/LoginName/.wvdial.rc > it will be found and used before /etc/wvdial.conf. Note that "." beginning > a file name means "do not show it", except through usage of: > $ ls -a > Many local configuration files are thus "hidden" in your /home/LoginName/ folder > > Some Linux installations have dialup tools like Kinternet, GnomePPP, and the > Redhat/Fedora Internet Connection Wizard which are front ends for wvdial and > will write /etc/wvdial.conf files. For this reason, it is advisable to test > your configuration file first, before copying it to /etc/wvdial.conf. Typically > a first test is run with: > $ sudo wvdialconf wvtest > which will search ports with names: /dev/modem /dev/ttyS* /dev/rfcomm*. > A successful ouput include a section like: > WvModem<*1>: Cannot get information for serial port. > ttySL0<*1>: ATQ0 V1 E1 -- OK > ttySL0<*1>: ATQ0 V1 E1 Z -- OK > ttySL0<*1>: ATQ0 V1 E1 S0=0 -- OK > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK > Note: above lines are testing the driver, modem firmware is then first read by ATI > ttySL0<*1>: Modem Identifier: ATI -- SmartLink Soft Modem > ttySL0<*1>: Speed 4800: AT -- OK > ttySL0<*1>: Speed 9600: AT -- OK > ttySL0<*1>: Speed 19200: AT -- OK > ttySL0<*1>: Speed 38400: AT -- OK > ttySL0<*1>: Speed 57600: AT -- OK > ttySL0<*1>: Speed 115200: AT -- OK > ttySL0<*1>: Speed 230400: AT -- OK > ttySL0<*1>: Speed 460800: AT -- OK > ttySL0<*1>: Max speed is 460800; that should be safe. > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK > > Found a modem on /dev/ttySL0. > Modem configuration written to wvtest. > ttySL0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0" > ------ > will be included in a successful run, where in this case /dev/ttySL0 > is the responding device port. The generated wvtest file is: > [Dialer Defaults] > Modem = /dev/ttySL0 > Baud = 460800 > Init1 = ATZ > Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > ISDN = 0 > Modem Type = Analog Modem > ; Phone = <Target Phone Number> > ; Username = <Your Login Name> > ; Password = <Your Password> > > which at a minimim must be edited to a form like: > [Dialer Defaults] > Modem = /dev/ttySL0 > Baud = 115200 > Init1 = ATZ > Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > ISDN = 0 > Modem Type = Analog Modem > Phone = 3334445555 > Username = Your_Login_Name > Password = Your_Password > > Additional if your modem port is of the type /dev/pts/N , with N a number, > then there MUST be added a line: > Carrier Check = no > This requirement currently applies to dialups using the helper utility: slmodemd > together with slamr, slusb or ALSA modem drivers, OR the " " : martian_helper > used with the martian_dev for Lucent/Agere modems with DSP chipsets. > > Then a test dialput can be done with: > $ sudo wvdial --config wvtest > > There are some Systems for which the wvdialconf test will stall at rfcomm ports. > This is a wvdialconf bug and can be bypassed by just using wvdial with a trial > wvtest, but you need to specify the port appropriate to your modem. > > If the configuration file below, lines beginning with # are comments. > Removing a # will activate a line with wvdial instructions appropriate to > special circumstances. > > > [Dialer defaults] > # Lines begining with # are comments. > # wvdial will look for this file at /etc/wvdial.conf or /home/LoginName/.wvdial.rc > > # Redhat/Fedora have an Internet Connection Wizard in the popup menus > # ICW will write a two part /etc/wvdial.conf supporting multiple modem usage. > > Modem = ModemPort > # typically a symbolic link to the true port is used, /dev/modem or /dev/ttyS* > # wvdialconf will test all port names /dev/modem and /dev/ttyS* > > Init1 = ATZ > Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > # Lack of dialtone acquisition can be due to low line voltage, > # a common problem in Italy. > # Try inserting a "dial without waiting": X3 > # Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +FCLASS=0 > # In case of connection instabilities, specify a lower frequency: > # Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=34 > # a MS=90 option is sometimes necessary for Internet Providers with buggy V92 protocols: > # Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 > ISDN = 0 > Modem Type = Analog Modem > # Dial Command = ATDP > ## replaces Touch Tone prefix ATDT to Dialout_phone_number, with older Pulse prefix ATDP > > Phone = Dialout_phone_number > # if going through a switch board, a perhaps necessary pause can produced with a comma: > # Phone = 1,Dialout_phone_number > Username = LoginName > # if Internet Provider is MSN.net or uses CHAP authentication, use under Linux: > #Username = MSN/LoginName > > Password = YourPassWord > > # the following lines is NEEDED only for usage with slmodemd or martian_helper > Carrier check = no > # Kinternet appears to add it automatically. > > ## If CONNECT is achieved but browsing fails, try activating the following line > # Auto DNS = yes > ## To make a logfile wvdial.out > # wvdial 2>&1 | tee wvdial.out > # # For some Internet providers, the following line is necessary > # Stupid Mode = yes > ## for other wvdial options, do "man wvdial" or see the documentation in > ## /usr/share/doc/wvdial/ > > # to dial an alternate provide use "wvdial 2nd" which will preferentially read: > [Dialer 2nd] > Phone = 2nd_phone_number > Username = 2nd_LoginName > Password = 2nd_PassWord > > gnome-ppp is a graphical front end to wvdial. Its setup writes itss configuration file to > the users home folder as .wvdial.conf . The leading "." means Hide. But the file can be displayed with: > $ ls -a wv* > and edited with: > $ gedit ./wvdial.conf > > > ## End wvdial config file > > For instructions to UNSUBSCRIBE from discuss@xxxxxxxxxxxxx, > send an email to: discuss-help@xxxxxxxxxxxxx > MODEM TESTING > > This text is complemented by the Post-Install at http://linmodems.technion.ac.il > Please so consult it if the following does not suffice. > > The wvdial package provides for an automated hardware+driver test. > This utility searches through ports with syntax: /dev/ttyS* (i.e. S0, S1, SL0 etc.) > and also follows a symbolic link: > /dev/modem --> /dev/ModemPort > If your modem port name does not satisfy these requirements already, > do a console login as: > su - root > Make the symbolic links as: > ln -sf /dev/ModemPort /dev/modem > ln -sf /dev/ModemPort /dev/ttyS15 > wherein /dev/ttyS15 is reserved for experimental usage. > Should there be problems with wvdial version 1.54.1-1 , drop back to 1.54.0-1 > > For recent RedHat and Fedora releases, wvdialconf is used by the Internet Wizard. > Within the pop-up menus find the Wizard. Its actions will write a configuration file: > /etc/wvdial.conf > For other Linux distros, open a console and login with > su - root > If necessary load the modem drivers: > sudo modprobe DriverNames > Then run the test: > wvdialconf /etc/wvdial.conf > Checks /dev/modem and ports /dev/ttyS*, a success at port /dev/ttySLT0 would be: > ttySLT0<*1>: ATQ0 V1 E1 -- OK > ttySLT0<*1>: ATQ0 V1 E1 Z -- OK > ttySLT0<*1>: ATQ0 V1 E1 S0=0 -- OK > ttySLT0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK > ttySLT0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK > ttySLT0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK > etc. > The /etc/wvdial.conf written looks like: > > [Dialer Defaults] > Modem = /dev/ttySLT0 > Baud = 115200 > Init1 = ATZ > Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > ISDN = 0 > Modem Type = Analog Modem > ; Phone = <Target Phone Number> > ; Username = <Your Login Name> > ; Password = <Your Password> > > For systems using the SmartLink slmodem drivers, > the following line should be added to its /etc/wvdial.conf > Carrier Check = no > So after editing in your personal information a functional file is like: > > [Dialer Defaults] > # lines beginning with # are Comments, not read by wvdial > Modem = /dev/ttySLT0 > Baud = 115200 > Init1 = ATZ > Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > ## if there is problem with dial tone acquisition, add into the above line: > # X3 > # meaning "dial without waiting" > ## for some Internet Provides, there may be problems with the new V92 mode codes. > # This can be suppresses with an: > # Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=90 > ## Within Italy it is sometimes necessary to even force a slower mode > # ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=34 > # This mode is also useful for PBX dialout lines. > ISDN = 0 > Modem Type = Analog Modem > # edit in your IP's phone number below. > Phone = 3334445555 > # Do not use - or spaceds in the Phone = line > # Introducing a pause with a , is sometimes necessary with hotel/company switchboards > # Phone = 8,3334445555 or 8,,,3334445555 for s 3 second pause > Username = Your_Login_Name > # for MSN.net, use instead > # Username = MSN/Your_Login_Name > Password = Your_Password > # if not using the SmartLink slmodemd, comment out with # the following line. > Carrier Check = no > [ Dialer 2nd_home ] > Phone = 7778889999 > > Then dialout with > $ sudo wvdial > or use the 2nd dialup number with: > $ sudo wvdial 2nd_home > > > The /etc/wvdial.conf generated by the RedHat/Fedora Internet Wizard > has a different format, adapted to its own dialer. This includes a line > Stupid Mode = yes > More informative dialup feedback May be obtained if it is commented out: > # Stupid Mode = yes > > A dialout with wvdial will then display like: > # wvdial & > --> WvDial: Internet dialer version 1.53 > --> Initializing modem. > --> Sending: ATZ > ATZ > OK > --> Sending: ATQ0 V1 E1 M1 S0=0 &C1 &D2 +FCLASS=0 > ATQ0 V1 E1 M1 S0=0 &C1 &D2 +FCLASS=0 > OK > --> Modem initialized. > --> Sending: ATDT3019178111 > --> Waiting for carrier. > ATDT3019178111 > CONNECT 53333 V42bis > --> Carrier detected. Waiting for prompt. > ** APX1.LNH.MD.RCN.NET Terminal Server ** > Login: > --> Looks like a login prompt. > --> Sending: LoginName > LoginName > Password: > --> Looks like a password prompt. > --> Sending: (password) > Entering PPP Session. > IP address is 66.44.1.6 > MTU is 1006. > --> Looks like a welcome message. > --> Starting pppd at Sat Jul 26 13:59:03 2003 > --> pid of pppd: 2404 > : pppd 2.4.1 started by root, uid 0 > : Using interface ppp0 > : Connect: ppp0 <--> /dev/tts/LT0 > Jul 26 13:59:08 stodolsklap kernel: PPP BSD Compression module registered > Jul 26 13:59:08 stodolsklap kernel: PPP Deflate Compression module registered > : local IP address 66.44.1.6 > : remote IP address 208.59.89.132 > : primary DNS address 207.172.3.8 > > The & in "wvdial &" puts the process into the background, > allowing further usage of the command prompt. To stop a backgrounded process: > # fg wvdial > # Ctrl -C > > TROUBLE SHOOTING > > Check for modem driver loading. > Do FIRST read INSTRUCTIONS files provided with the modem driver resource. > Some may have installed to /usr/share/doc/Modem_or_Driver_Name/ > For RPM using distros, documentation files will be listed through > rpm -q -d packageName (less the version part, sometimes) > and all directly installed files can be listed by > rpm -q -l packageName > Depending upon your installation, the modem drivers may/may_not be autoloaded. > Login as Root in a console with: > # su - root > # lsmod > If the modem drivers are not already loaded onto the kernel, insert them with command > # sudo modprobe ModuleDriver > If there are multiple drivers such as the lt_modem.o and lt_serial.o pair, > commanding the serial like driver: > # sudo modprobe lt_serial > should autoload all modules it depends on. Check with: > # lsmod > This proceeds through a reading of dependency files > written to /lib/modules/2.6.31-15-generic/ during boot up through the "depmod -a" command. > In constrast > # insmod lt_serial > would only attempt loading of that single driver and will FAIL, if its dependency on > lt_modem.o has been satisfied by prior lt_modem.o insertion. > > Do read "man wvdial" and /usr/share/doc/vwdial documentation > sometime browse the documentation that is written to /usr/share/doc/wvdial/ > Therein are instructions for setting up alternative dialouts. > > %%% This wvdialconf action if successful generates the files: > /etc/ppp/peers/wvdial > /etc/ppp/peers/wvdial-pipe > in addition to the /etc/wvdial.conf > > Many Users prefer to use the dialout utility KPPP. This is fine. > But each User MUST run the configuration process separately. > In principle, different Users on the same Linux System could > have different Internet providers and/or use different modems. > The configuration process generates a file: /home/UserFolder/.kde/share/config/kppprc > Therein, non-standard modem port names can be entered, such as: > [Modem] > Device=/dev/ttySHSF0 > for the Conexant hsfmodem port. > > > Preparation for dialout if other COMM modes are active. > --------------------------------------------------------------------------- > Concurrent ethernet capability will compete for > the Domain Name Service (DNS) needed for browser naviagation. So as root: > # /sbin/ifconfig eth0 down > before starting a dialout! > With a Mandrake installation, it will be necessary to: > # /etc/init.d/network stop > > Internet clients such as Netscape, Mozilla, Explorer etc. > should be CLOSED during your first dial out trials. > Should a URL on the Internet be specifed as the default URL/connect, > then the Client may compete with ppp for connectivity functions. > After PPP functionality has been verified, the effects of opened > or launched browsers can be checked > > If you have installed the DIALD (dial on demand) package, stop it for initial tests: > # /etc/init.d/diald stop > Otherwise diald function will be initiated with modem usage, > and could compilate issues. Test diald only after ppp by itself is fine. > > If your internet provider assigns DNS dynamically then add to /etc/ppp/options: > usepeerdns > > To analyze a dialout attempt, it is useful to display kernel messages with: > # tail -f /var/log/messages & > The & puts the commanded process in the "background" allowing recovery of the command prompt. > > Some dialer packages (kppp etc) may automate the above steps. > > > Note that for some Linux distributions (Mandrake for one), > maintain modules in compressed module.gz format, if modem service was not specified > during the Linux installation. A subsequent installation of any dialer package: > wvdial - PPP dialer with built-in intelligence. > kppp - PPP dialer for KDE > dtmfdial - A DTMF Tone Dialer > gkdial - Gtk-based PPP dial-up configuration tool. > gkdial-gnome - GNOME-based PPP dial-up configuration tool. > masqdialer - daemon for remote control of masqueraded dialup links > pppconfig - Debian configuration toolset with command: pppconf > will stimulate unpacking of ppp related modules during bootup. > > The cogent ppp related modules loaded during such a CONNECT are displayed within the output from: > # lsmod > ppp_deflate 3512 1 (autoclean) > zlib_inflate 18980 0 (autoclean) [ppp_deflate] > zlib_deflate 18648 0 (autoclean) [ppp_deflate] > bsd_comp 4440 0 (autoclean) > ppp_async 7744 1 (autoclean) > ppp_generic 16380 3 (autoclean) [ppp_deflate bsd_comp ppp_async] > slhc 5264 1 (autoclean) [ppp_generic > > For ealier 2.4.nn kernels, loading of these modules may require the following lines within > /etc/module.conf : > ### automate ppp modules loading ### > alias /dev/ppp ppp_generic > alias char-major-108 ppp_generic > alias tty-ldisc-3 ppp_async > alias tty-ldisc-14 ppp_synctty > alias ppp-compress-21 bsd_comp > alias ppp-compress-24 ppp_deflate > alias ppp-compress-26 ppp_deflate > ### end ppp block #### > For more recent kernels with their modutils, > these lines are no longer needed. > > For potential causes of a NO DIALTONE failure, read the Post-install.html > at http://linmodems.technion.ac.il/ Not setting the Country Code may be > and additional problem. > > COUNTRY CODE Issues > ==================== > The modem which you purchase locally or abroad may not be preset > with the proper Country Code setting. An incorrect setting can > hinder acquisition of dial tone. > Inclusion of an X3 (dial without wainting) in the modem Init string > of under wvdial, including in /etc/wvdial.conf a line > Stupid Mode = yes > > Dialtone recognition depends on the setting of country > and/or local phone line equipment. > > To properly get dialtone for your country phone experiment use > AT+GCI=xx where xx is country code in hexidecimal format. > Theoretically there could be 256 different countries but > not all are valid. Tables in manuals are way off date, > you have to write a small script to try all combinations > for yourself if you can't guess by chance. > > After country select you can check textual name of the country it represents. > For example: > at+gci=00 > OK > ati9 > Japan > > If you can't find exact country, choose the nearest one available. > Nearby countries tend to have similar equipment and compatible dialtones. > > If a message like: > Sep 20 09:32:42 localhost pppd[7355]: The remote system is required to authenticate itself > is generated during an abort of a login, > Then try adding a line to /etc/ppp/options > no auth > > 8) After a successful CONNECT, the Domain Name Service (DNS) needed > for Browser navigation can be checked with: > # ping corel.com > PING comcast.net (63.240.76.72): 56 data bytes > 64 bytes from 63.240.76.72: icmp_seq=0 ttl=52 time=209.1 ms > 64 bytes from 63.240.76.72: icmp_seq=1 ttl=52 time=189.9 ms > 64 bytes from 63.240.76.72: icmp_seq=2 ttl=52 time=180.0 ms > 64 bytes from 63.240.76.72: icmp_seq=3 ttl=52 time=179.9 ms > # Ctrl-C > aborts ping > --- comcast.net ping statistics --- > 4 packets transmitted, 4 packets received, 0% packet loss > round-trip min/avg/max = 179.9/189.7/209.1 ms > > # ping 63.240.76.72 > PING 63.240.76.72 (63.240.76.72): 56 data bytes > 64 bytes from 63.240.76.72: icmp_seq=0 ttl=52 time=179.8 ms > 64 bytes from 63.240.76.72: icmp_seq=1 ttl=52 time=190.0 ms > 64 bytes from 63.240.76.72: icmp_seq=2 ttl=52 time=170.0 ms > # Ctrl-C > aborts ping > > Should there be a success with: > # ping 63.240.76.72 > BUT a failure with the named address: > ping comcast.net > Then DNS has not been acquired. > Note that failure to stop ethernet service > # /sbin/ifconfig eth0 down > before starting a dialout, will commonly block DNS under ppp. > > To terminate the wvdial session, bring the action to the foreground (fg): > # fg wvdial > Ctrl-C to terminate: > wvdial > Caught signal #2! Attempting to exit gracefully... > : secondary DNS address 207.172.3.9 > : Terminating on signal 15. > : Connection terminated. > : Connect time 7.8 minutes. > --> Disconnecting at Sat Jul 26 14:06:53 2003 > > The Debian distribution provides a utility: > # pppconfig > for setting up a chatscript for ppp initiation. > Most dialers do use chatscripts and will produce similar records. > Below is the record of a dial out initiated by: > > # pon > : pppd 2.4.1 started by marv, uid 1000 > : abort on (BUSY) > : abort on (NO CARRIER) > : abort on (VOICE) > : abort on (NO DIALTONE) > : abort on (NO DIAL TONE) > : abort on (NO ANSWER) > : abort on (DELAYED) > : send (ATZ^M) > : expect (OK) > : ATZ^M^M > : OK > : -- got it > : send (ATQ0V1E1M0S0=0W2&C1&D2+FCLASS=0^M) > : expect (OK) > : ^M > : ATQ0V1E1M0S0=0W2&C1&D2+FCLASS=0^M^M > : OK > : -- got it > : send (ATDT3019178111^M) > : expect (CONNECT) > : ^M > : ATDT3019178111^M^M > : CONNECT > : -- got it > : send (\d) > : Serial connection established. > : Using interface ppp0 > : Connect: ppp0 <--> /dev/modem > : kernel does not support PPP filtering > Jul 26 14:08:39 stodolsklap kernel: PPP BSD Compression module registered > Jul 26 14:08:39 stodolsklap kernel: PPP Deflate Compression module registered > : local IP address 66.44.1.195 > : remote IP address 208.59.89.132 > : primary DNS address 207.172.3.8 > > Once your first CONNECT has been established, than in the future if should suffice > just to use your dialer of choice: wvdial , kppp .gnomeppp or whatever. > > Good surfing to you. > > 10) GENERAL ITEMS > > If attemped insertion of a modem driver evokes a complaint like: > unresolved symbol do_SAK_R9a0bcb74 > then the kernel-headers using in compiling the modem drivers > do not match those of your current kernel whose KernelVersion is displayed by: > uname -r > and whose kernel config file is often located at /boot/config-KernelVersion > The section above "COMPILING DRIVERS, for Newbies" relates how to make corrections. > > There are definitely IPs whose login protocols are Linux hostile. > If you cannot achieve a login, try another Internet Provider (IP). > or ask for someone on discuss@xxxxxxxxxxxxx to test your IP. > > Many driver packages provide for loading modem drivers on bootup. > Here is a description on how to set it up, if necessary: > http://linmodems.technion.ac.il/archive-fourth/msg00451.html > > PLEASE include the diagnostic output of the following Root command in any problem reports: > # setserial -agv /dev/ttyS* > > For instructions on having modem drivers loaded on bootup, > particularly the SmartLink slmodem drivers see: > http://linmodems.technion.ac.il/archive-fourth/msg00451.html > For automated removel of drivers after a PPP session see: > http://linmodems.technion.ac.il/archive-fourth/msg00145.html > > For general upto date advice: > http://linmodems.technion.ac.il/ > http://linmodems.technion.ac.il/resources.html > available in Russian at http://linmodems.nm.ru > for a general PCI_ID database > http://www.pcidatabase.com/ > the original Linux winmodems URL is: > http://linmodems.org > with a mailing list on Winmodems: > discuss@xxxxxxxxxxxxx > whose archives can be searched at: > http://linmodems.technion.ac.il/ (near bottom of the page) > There is an extensive modem database at: > http://start.at/modem/ > Locate your local Linux groups through: > http://www.linux.org/groups/index.html > USB modem information: http://www.linux-usb.org/USB-guide/x332.html > Laptop users should browse http://tuxmobil.org/modem_linux_add1.html > For debugging ppp: > http://www.cisco.com/warp/public/471/debug_ppp_negotiation.html > > ---------- end FOLLOW UP STEPS --------------- > > > Modem Type Readout and Supporting Software Identification. > ------------------------------------------------------- > Most add on cards to motherboards (including modems) adhere to a PCI standard, for > which there is firmware on the card which can be readout, providing setup parameters > and specification of the required software. This works under Linux provided that > drivers are resident. Herein is the practical problem. During the evolution of > modems, some of the complementing software components became Proprietary and > Closed Source. A consequence is that for reasons of Legality and/or Principle, > many Linux distributions do not distribute such modem drivers with the regular > releases, even when the modem chipset designer does provide Linux support code. > Without the drivers, additional assistance is needed to identify the modem > chipset and its complementing software. > > The scanModem script includes four routines to determine the software required: > 1) Readouts with a lspci tool accessing firmware on PCI cards. > 2) A test using modem drivers already on your system as part of the ALSA (Advanced Linux > Sound Architecture) software package. See DOCs/Smartlink.txt for details. > 3) Comparison of Primary+Subsystem PCI IDs with others historically gathered, and > then archived within scanModem. > 4) A test requiring the SmartLink slamr.ko driver. See DOCs/Smartlink.txt for details. > > Should these not be adequate, there are directions below for doing diagnostics during > an alernate Microsoft Windows bootup. > > Stop here on a first reading, and just run > ./scanModem > Read on later if you are interested in details, OR > need instructions for doing modem diagnostics under Microsoft. > > Using MicroSoft(MS) Windows: > ----------------------------- > MS installations do generally have adequate diagostic capability. Try the following > routine 1), beginning with mouse clicks on: > 1) Start > Settings > Control Panel > Classical View (for Window XP) > System > > Hardware > Device Manager > Modems > Click on the + > Modem. Double click to > expand the graphic. Manufacturer information may be displayed. For example, CXT > stands for Conexant. Click the Diagnostics Tab. Record any hardware ID or vendor > and device information. > Next do the Query Modem and record the ATI specifications displayed such as: > ATI3 - Agere SoftModem Version 2.1.22 > ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27 > Try to identify the modem setup file, with name perhaps MODEM.INF. > > 2) Open a COMM console. Send ATI commands to the modem (ATI, ATI1, ATI2, etc) > which may elicit chipset and driver information. Here is an example: > ATI3 - Agere SoftModem Version 2.1.22 > ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27 > successfully identifying an Agere SoftModem chipset, both by name and through > the softmodem SIL ID: AC97 ID:SIL REV:0x27 > > The IBM mwave modem: > This has a DSP chip usually seated on the motherboard. Not carried on a PCI card > it cannot be detected by scanModem. However, the mwave driver is included in > 2.6.n kernel releases. > So try: > # modprobe mwave > Either the module will load or the absence of the modem will be indicated by: > FATAL: Error inserting mwave (/lib/modules/2.6.10-1- > 686/kernel/drivers/char/mwave/mwave.ko): Input/output error > See http://www.linuxdocs.org/HOWTOs/mini/ACP-Modem/ for details on this modem. > > Modem evolution: > ---------------- > Here is a very abbreviated history on how modem evolutionary development. The > earliest modems (MOdulate and DEModulate signals for phone lines transmission) > managed all signal proceesing on the modem card through actions of expensive > Controllers chipsets with DSP (digital signal processing) capability. Copyrighted > Vn.nm compression routines were also encoded in the chipset. Under Linux, an Open > Source serial driver was the minimal complementing software. This generation of > Controller chipset modems placed minimal burden on the early slow central > processing unips (CPU) of personal computers, such as the Intel 386. > > As CPUs became faster, it was feasible to transfer some modem functions to > the CPU. A 2nd generation of modems retained a DSP chip, but Controller functions > were software driven on the CPU. A benefit was that modem hardware became cheaper. > But sadly the supporting software was Proprietary. Worst, some Intellectual Property > components were Closed Source to protect large investment in code development. Such > Controller free modems include the Conexant HCF, Intel-537EP and Mars chipset > modems from Lucent or its later subsidary, Agere Systems Inc. > > As CPUs became even faster, even DSP functions could be software code driven on > the CPU. This third generation of modems are commonly called "softmodems". Their > complementing software is comparable in sizeto that of the Linux kernel itself. The > residual "modem chip" is very cheap, but the development of the complementing > software is a large investment on the part of the chip designer/maker. > > Modem chipset determination under Linux: > --------------------------------------- > The chipset of a modem determines which complementing software is required. > The Manufacturer and Model of an assembled modem are often inadequate to identify > the chipset. But sometimes there is an easy chipset identification. There is > a "lspci" utility provided in the Linux pciutils package. It reports the PCI > identifiers (IDs hereafter) or the Primary card, its Subsystem, and some setup > parameters written in firmware. For example, there is a softmodem in the > PCI bus of address 00:11.6 on my laptop. Shown below is firmware information > acquired by two lspci commands: > $ lspci -s 00:11.6 > 00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller > $ lspci -s 00:11.6 -nv > 00:11.6 0780: 1106:3068 (rev 80) > Subsystem: 14ff:100b > Flags: medium devsel, IRQ 193 > I/O ports at e000 [size=256] > The translation is: The card inserted into PCI bus slot 00:11.6 is named > "Communication controller: VIA Technologies, Inc. AC'97 Modem Controller". The > modem was assembled by a Vendor with ID identification code 1106 . Among 1106's > products, it has a Device ID of 3068 in its 80th revison. This usually provides > adequate information, to get software from the Vendor designated by 1106 (VIA > Technologies, Inc. in this case) for their device designation 3068. The parameters > Flags: medium devsel, IRQ 193 > I/O ports at e000 [size=256] > are determining by the environment of the host computer as reading modem firmware. > It may change if other hardware is added/removed from the host computer, or > under a change or Operating System (OS) kernel. > > The problem for softmodems is that additional information is needed for the software > specification. The Subsystem Vendor_ID identifies only the assembler company. But > the modem chip housed in the Subsystem could be of a variety of types, each requiring > different support software. In general, a single Subsystem assembler could use a > variety of different softmodem chips. The Subsystem firwmare information on the chipset > is not accessible to lspci. Rather it requires usage of a modem driver, if one first had > some competent modem driver for minimal diagnostics. > > Fortunately there are the software tools and drivers of the ALSA (Advanced Linux > Sound Architecture) suite. This includes modem drivers lacking COMM proficiency by > themselves, but enough capability to readout the Subsystem firmware. For the VIA > modem above, the encoded modem codec is SIL22, reporting that the softmodem chip was > made by SmartLink Inc. > > It is important to emphasis, that AC'97 Modem Controllers are made by a variety > of companies, and each may house many different Subsystem modem chips. There is > an Archive within scanModem of those with previously identified codecs. For example, > the table for the 1106:3068 AC'97 Controller is: > codec SubSystems_with_codec ------------> > CXT 104d:8143 104d:80f6 1025:0030 > SIL27 1102:0033 1025:0046 1025:0033 1734:1078 1509:2870 1025:0046 > SIL22 1743:1032 10cf:118e 1734:1054 1462:309e 1631:e004 1543:4c22 161f:2032 and_more > SIL21 10cf:118e 13bd:1022 1543:4c21 1071:8375 1019:0c04 1458:1543 1019:b320 > MOT66 1734:109b > Because of hardware configuration issues, the ALSA tools may initially fail. Then this > Archive is a fall back reporting the codec, and therefrom the needed software. For reasons > obscure, a single Subsystem ID may have different codecs under different Primary > controllers. Thus the pair Primary+Subsystem IDs must BOTH be retained to record > the codec. > > In addition to the Modem Controllers adhering to the AC'97 specifications, softmodem > Subsystems may be hosted by High Definition Audio (HDA) cards such as the: > 8086:2668 Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller > These lack a softmodem codec. Instead the softmodem chip information acquired with ALSA > tools is within a folder: /proc/asound/card0/codec*#1/ > and includes the Vendor ID of the softmodem chip, such as 14f1 corresponding to Conexant. > > The software support: > --------------------- > The CXT designation above is an abbreviation of CXT_some_number, for Conexant HSF softmodem > codecs. These now number some 41 (perhaps more) CXT. Fortunately, all these codecs are > supported by a single hsfmodem software package provided through http://www.Linuxant.com > The trial package is free, but locked to speeds of 14,400 K. A software key must be > purchased to enable full speed support, with future software updates free. There is NO > freeware alternative for the hsfmodem software. But Linuxant does provide pre-compiled > drivers for the more common Linux kernels, and their support services are good. > > In the Table below, there are currently some 13 other softmodem codecs. Fortunately > all are supported by a combination of the ALSA modem drivers, the ALSA audio drivers > the modem drivers depend on, and a very smart helper utility from Smartlink Inc., > the slmodemd helper. Sasha Kharposky wrote the Linux slmodemd utility and remains its > volunteer maintainer. It provides the cleverness to interface between the low level > ALSA modem driver and the pppd package communications codes. For details do: > $ slmodemd --help > and read associated documentation. The slmodemd is provided with some Linux distributions, > and can also be downloaded in SLMODEMD packages from: > http://linmodems.technion.ac.il/packages/smartlink/ > > Subsystems of AC'97 Modem Controllers > --------------------------------------- > Subsystems for softmodems are primarily made by Silicon Labs (SIL) under > contract to companies like Intel, Agere Systems, Motorola etc. In the Table > below, ChipMadeBy does NOT imply software support directly from that > manufacturer. The chart of information below is largely harvested from messages > to discuss@xxxxxxxxxxxxxx > A codec_indent such as REV:0x27 is reported by diagnostics under Microsoft, as > illustrated above. The matching designations such as SIL27 are translations > under Linux, which are output by a diagnostic of the slamr.ko driver from the > SmartLink slmodem software. > SIL is an abbreviation for Silicon Laboratories Inc., which provides Subsystems > on order to many modem assemblers. > SML is used below as abbreviation for SmartLink Inc. with official driver > resources at http://www.smlink.com/main/index1.php?ln=en&main_id=40 . BUT use > updated resources at http://linmodems.technion.ac.il/packages/smartlink/. > ALSA+SML means use an ALSA modem driver plus the Smartlink slmodemd helper, > with the particular driver depending on the AC'97 or HDA host controller. > ID was originally a hexadecimal readout from 7c and 7e registers of the SubSystem, > but are translated into "english", as done automatically by the slamr driver. > > ID chip_maker driver/helper sources > ---------------- ---------------------- > CXTnm Conexant hsfmodem package from http://www.linuxant.com with several hsf* drivers. > nm - a number > SIL25 Intel ALSA+SML or INTEL-537EP supported AA variant > INT65 Intel ALSA+SML or INTEL-537EP supported EA variant > SIL26 SML SML, slamr driver plus slmodemd > SIL27 AgereSystems ALSA+SML > SIL2f " ALSA+SML > MOT66 " ALSA+SML > AGR01 " ALSA+SML > AGR02 " ALSA+SML > SIL21 PCTel ALSA+SML > SIL23 PCTel ALSA+SML > SIL22 SML ALSA+SML > SIL24 Broadcom ALSA+SML > BCM64 Broadcom ALSA+SML, under Intel ICH family, AC'97 controllers. > ---------------------------------------------- > Subsystems with the above characteristics could reside under any of > the primary softmodem controllers listed below. Ignore the stuff after the > . > It serves during parsing of the Table by scan modem > > Primary > PCI_IDs Name Possible support by: > --------------- ----------------------------- ------------------------- > 8086:2416 82801AA ICHAA AC97 Modem Controller> + A a p c . > 8086:2426 82801AB ICHAB AC97 Modem Controller> + A a . > 8086:7186 > c . > 8086:7196 82440MX Banister AC97 Modem Controller > + A a c . > 8086:2446 82801BA/BAM ICH2 AC97 Modem Controller > + A a p c . > 8086:2486 82801CA/CAM ICH3 AC97 Modem Controller > + A a p c i . > 8086:24c6 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)1DB ICH4 AC97 Modem Controller> + A a c i b . > 8086:25a7 6300ESB AC97 Modem Controller NEW > > 8086:24d6 82801EB/ER ICH5/ICH5SR AC97 Modem Controller> + A c i . > 8086:8280 1EB ICH6 AC97 Modem Controller> + A c . > 8086:2668 Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller> H c . > 8086:266d Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC97 Modem Controller > > 8086:2669 631xESB/632xESB AC97 Modem Controller NEW > > 8086:27d8 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller HDA > . > 8086:27dd (ICH7 Family) AC97 Modem Controller NEW > > 8086:xxxx types above are from Intel> > > 1039:7013 SIS 630 > + a p c i . > 1039:7018 SIS 960 > + i . > 10de:01c1 Nvidia Corp > + i . > 10de:00d9 Nvidia Corp > A c . > 1106:3068 VIA > + a p c i . > 1022:7446 AMD AC_LINK > + . > 10b9:5450 ALI 5450 > > 10b9:5451 ALI 5451 > + a c . > 10b9:5453 ALI 5453 AC-Link > p c . > 1025:5453 ALI 5453 AC-Link > c . > 10b9:5457 ALI 5457 AC-Link > + p c i . > 1025:5457 ALI 5457 AC-Link > c . . > 1002:434d ATI > T a c i . > 1002:437b ATI Audio device: ATI Technologies Inc SB450 HDA Audio a . > 1002:4378 ATI > c . > 1543:3052 SI3052 > > > Class 0403, High Definition Audio Controllers (HDA) > ----------------------------------------------------- > 8086:2668 Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) HDA Controller > 8086:27d8 Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller > 1002:437b Audio device: ATI Technologies Inc SB450 HDA Audio (rev 01) > 10de:026c nVidia Corporation MCP51 High Definition Audio > ---------------------------------------------------- > are the members of this family encountered as of September 2006. > From the file /proc/asound/card0/codec*#1/, there are the following Subsystem chips: > > Vendor IDs Chip maker Support type > ---------- ---------- ------------- > 0x14f12bfa Conexant hsfmodem , not slmodemd compatible > 0x14f12c06 > 0x11c13026 AgereSystems snd-hda-intel, slmodemd > 0x11c11040 " not supported into 2008 > 0x163c3055 Smartlink snd-hda-intel, slmodemd > 0x163c3155 " " " > 0x10573055 Motorola " " > 0x10573155 " " " > > > RATIONAL > > This scanModem service is sadly necessary because of the pre-compiled format > (binary, Closed Source) of some modem supporting code. Intellectual property > is protected within the binary component. But this prevents compatibility > assessments/debugging against Linux Open Source code. Skipping many details, > the consequence is that some Linux distributions do not deliver Closed Source code, > or tools adequate to fully identify the modem chipset. > This script tries to close this information gap. > > This script primarily utilizes the "lspci" utility from the package PCIUTILS. > Various component scriptlets interpret the information captured by lspci. > For many modems, directions to supporting software and/or more detailed information is enabled. > ISA bus modems, 16 bit PCMCIA card modems and USB modems will not be recognized. > See the output files for guidance on these cases. > > The script originated as scanPCI written by Chris Hebeisen, > to recognize modems with DSP (digital signal processing) chipsets made by Lucent/AgereSystems. > It now aspires to provide useful information on other modems as well. > For the Lucent/Agere DSP chip modems, System information is used to recommend Installers, > from the Installer list output from the repository: http://ltmodem.heby.de/ > For other modem chipsets fully identified, URLs to support sites are given. > > Three types of information are acquired from your System: > 1) General system information necessary for your guidance; > 2) The PCI_ID of the modem card, or for the increasingly prevalent "soft modems", > the PCI_IDs of its AC97/MC97 controller and its modem subsystem. > 3) For soft modems, a SIL_ID of the subsystem is either acquired > OR instructions provided for manual agetting it. > > The remainder of /home/dmitry/Рабочий Ñтол/Linux/Progi/Modem/scanModem is a repository of "modem gossip" or URLs thereto. > Only information blocks most relevant to your System will be output into > files written to the Modem/ folder > Should you need assistance after FIRST following all the advice and/or URLs, > 1) Browse the general information at: http://linmodems.technion.ac.il/ > 2) ONLY thereafter send ModemData.txt to: discuss@xxxxxxxxxxxxx > Modem/DOCs/General.txt has common information the List need not be bothered with. > 3) Also the archive SEARCH ENGINE at http://linmodems.technion.ac.il/ > may be useful once PCI or SIL IDs are acquired. > > The scanModem script can be read and word searched with a text browser. > Blocks of Information with little code begin and end with #####. > > In case of a failure concerning "lspci", rerun /home/dmitry/Рабочий Ñтол/Linux/Progi/Modem/scanModem after login to a console with > # su - root > as Root permission may be necessary for access to lspci. > > Updated on 2009_11_26 by Marv Stodolsk for access through: > http://linmodems.technion.ac.il/packages/scanModem.gz > Please do NOT use a scanModem.gz from any other site!! > > Vendor 11c1 is Lucent Technologies. Modem technologies were transferred to Agere Systems Inc, > which has now been incorporated into LSI Inc, http:/www.lsi.com . > Their Linux code developer/maintainer is Soumyendu Sarkar. Linuz support for a chipset and > its continued maintenance is typically only initiated at the request of a major chipset buyer, > or comparable sponsor. Several different modem chipset types with varying support under Linux are produced: > . > Device ID ChipType Linux drivers Comment > --------- ------------- -------------- ----------------------------- > 0480 Venus serial_drivers controller chipset 1673JV7 > 0440-045d Mars/Apollo martian # DSP (digital signal processing) chipsets > ltmodem older code format needed only for FAX services > 0462 ADSL Wildwire none > -- following modems have DSP done on the CPU, not the modem card ---- > 048(c or f) SV2P agrsm code resources for drivers: agrmodem + agrserial > 0620 Pinball agrsm In some HP desktop PCs > 0630 SV92EX agrsm In some newer PCs > 0600 ?? none Very few in use. > HDA_hosted 11c11040 agrsm on subsystems of some High Definition Audio cards > 062(1-3) SV92PP none in some HP desktop PCs > 047e:2828 USB modem* agrsm > 047e:2892 USB modem* agrsm > ---------------------------------- > * For USB modems with Proprietary Licenses, Linux compiling support is blocked > for 2.6.25 and later kernels. > # ltmodem is the code release from LSI/Agere. Alexei Chetsov's martian derivative > has only Open Source code in the single driver, martian_dev, with all the Closed Source code > shifted to a helper utility,martian_modem. > > martian - At http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/ > Both Intel and AMD x86_64 architectures are supported, though the martian_modem helper > must be encoded in 32 bit mode and complementary 23 bit libraries provided. > > The agrsm code packages compile into a agrmodem.ko + agrserial.ko driver pair. > But there are specialized packages for the different chipsets. The following resources > can be accessed at: http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ has resources. > More details are in the DOCs/Agrsm.txt > > > Intel modems > ============================== > Vendor=8086 is Intel, Inc. producing chipsets for 536EP host controller free (HCF) modems, > 537 soft modems, several AC'97 softmodem controllers and HDA (High Definition Audio) cards. > > For Ubuntu Linux users with Intel 536 and 537 chipsets the are driver > installation packages available, see: > https://help.ubuntu.com/community/DialupModemHowto/Intel537EP > https://help.ubuntu.com/community/DialupModemHowto/Intel536EP > with suggestions for improvements to c.marcano@xxxxxxxxx > > For INTEL537 and INTEL536 chipset modems, updated support sources are at: > http://linmodems.technion.ac.il/packages/intel/Philippe.Vouters/ > > After downloading the most recent package and copying to your Linux partition, > Compile and install with Root permission: > $ make clean > $ make 537 > $ su - root > # make install > or under Ubuntu with: > $ sudo make install > > Formal Intel support for Linux appears to have ceased updates. But their offical > support packages can be accessed through: > http://developer.intel.com/design/modems/support/drivers.htm > > The AC'97/CNR controllers of softmodems usually do NOT use Intel software. > Rather, the modem Subsystem determines the required software support. > Subsystems with Conexant chips require hsfmodem software from http:/www.linuxant.com > Other Subsytems are currently supported by Open Source ALSA drivers plus the slmodemd helper. > > The HDA cards may host softmodem chipsets, through a different bridging then the AC'97 types. > Both Conexant chip and ALSA supported chipset types have been encountered. > > For the 537 class softmodems, prior to software release 2.70.95.0, > there were distinct support packages: > PCI_id SubSystem_id Older_package Comment > ------------------------------------------------------------------------------- > e159:0001 8086:0003 537 TJ320 v2.0 controller > 8086:1080 8086:100[7,8,A,0] 537EP 8086:1080 AC'97 controller > 8086:1040 8086:1005 537SP 8086:1080 AC'97 controller > various various 537AA_secure primary AC'97 controller > over si3054 chip with SIL25 codec > si == Silicon Instruments > various various 537EA primary CNR controller > over si3038 chip with INT65 codec > -------------------------------------------------------------------------------- > But all are currently supported by a single Intel-537EP package > The 537AA and EA types may be alternatively be supported by an ALSA modem driver > and the Smartlink slmodemd. > > Intel-536 chipset modems have an onboard DSP (digital signal processor) chip. > They may alternatively be served by the 537EP software, with added CPU burden. > > A very detailed installation report cogent to 537 type modems is at: > http://linmodems.technion.ac.il/archive-fifth/msg00541.html > > For Debian like distros, a modified install script is at: > http://members.lycos.co.uk/persianlinux/downloads/intel536EP/Intel536_inst_debian > > ======= end Intel section ======= > > Do NOT send this text with common information to discuss@xxxxxxxxxxxxx > There are instructions to UNSUBSCRIBE from discuss@xxxxxxxxxxxxx at http://www.linmodems.org > ============== > > Several sections are included in this file: > The Summary of modem Support under Linux > description of the soft modem identity tests: SIL ids > some output from scanModem specific to your System > an explanation of the GCC 2.95 compiler warning > ethernet Interference with DNS (domain name service) > Please Linux Newbies read carefully, the companion > Modem/DOCs/DriverCompiling.txt and its > Followup Modem/DOCs/DriverTesting.txt section with dialout examples. > > It is the CHIPSET, and Not the modem BrandName which is informative for Linux support > > The chipset types that are fully supported under Linux, without proprietary drivers, > have the more expersive controller chipsets. These include the 3COM,Inc 3CXM556 and > AgereSystems FM560LK chipsets. Do a WWW search to find them. > > USB modems will not be detected through the acm.o driver with port /dev/ttyACM0 > UNTIL proper USB support is installed. > See http://www.linux-usb.org/USB-guide/x332.html, > Linux_kernel_source/Documentation/usb/acm.txt, and > http://www.usb.org/developers/devclass_docs/usbcdc11.pdf (page 15) > Among the USB modems with proprietary interfaces, there is support for > Conexant HSF modems are supported by the hsfmodem package at http://www.linuxant.com/drivers > HSF USB with Vendor:Product IDs - 0572:1300 0572:1301 0572:1302 0572:1303 08E3:0111 > with updates at http://www.linuxant.com/drivers/hsf/index.php > HCF Vendor ID: 0572 Product ID: 1290 (Cadmus2 HCF, Conexant) is supported, > but NOT the Cadmus I types: http://www.linuxant.com/drivers/hcf/faq.php#25 > HCF USB Vendor ID: 05AC Product ID: 8202 (Cadmus2 HCF, for Apple/Mac and not PCs) > SmartUSB56 (ST7554) based modems with ID: 0483:7554 > The SWEEX USB modem has the ST7554 chipset > Drivers are at http://www.smlink.com/main/index1.php?ln=en&main_id=40 > http://linmodems.technion.ac.il/archive-fourth/msg00176.html is an installation report. > To write out Smartlink information, use the proxy entry > ./scanModem test 1131:3400 > > PCMCIA card modems can serve if your laptops modem is not supported under Linux. > Look through > http://windows-breaker.devidal.tv:5190/~chris/winmodems/pcmcia_list.html > All modems with a green bar labelled OK on the left will work with Linux serial drivers. They will immediately be recognized by > # wvdialconf /etc/wvdial.conf > or under kppp as /dev/ttyS0 ...> /dev/ttyS3 > Also see http://freewebhosting.hostdepartment.com/g/gromitkc/pcmcia_list.html > The 3COM,Inc 3CXM556 and AgereSystems FM560LK chip modems use Open Source serial-cs.o drivers. > > For modems not recognized by scanModem, chipset information may be obtained under Microsoft Windows through: > 1) Start > Settings > Control Panel > Classical View (for WinXP) > Modem > or alternatively under Linux > # cat /proc/asound/mc97* > Try to identify the modem setup file, with name perhaps MODEM.INF > 2) Open a COMM console, and send ATI commands to the modem (ATI, ATI1, ATI2, etc) > which may elicit chipset and driver information. Here is an example > ATI3 - Agere SoftModem Version 2.1.22 > ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27 > successfully identifying an Agere SoftModem chipset, both by name and through > the:softmodem SIL ID: AC97 ID:SIL REV:0x27 > > SUPPORT SUMMARY - as of 2009_11_26 > ------------------------------------- > Controller chipsets are used in the most expensive modems and are supported. > They utilize the same serial drivers included with kernel+module installations, > and most commonly one of the ports /dev/ttyS0 thru 3. > Such chipsets are produced by 3Com, AgereSystems (the Venus chipset), > Topic Semiconductor Corp., and others. But the same companies may > produce unsupported WinModems. Do not depend on the Brand Name. > Look for an explicit statement of Linux support > > AVOID the following modem chipsets: > ESS - no formal support since 2.2.2 kernels, though there are kluges: > http://andywettstein.home.comcast.net/ess/ > http://tx.technion.ac.il/~raindel/ > 3Com/US Robotics winmodems - never supported under Linux > > SmartLink - newer chipsets are supported: http://www.smlink.com > ftp://ftp.smlink.com/linux/unsupported/ > Moreover, the slmodem-2.9.10 drivers will support Many but not all modem Ssubsystems > that serve under AC97/MC97 controllers. > > Conexant - all modems supported with drivers at: http://www.linuxant.com > Testcode for slow 14,400 mH support is free, BUT > there is a one time charge for the full speed support. > > Intel Inc. - http://developer.intel.com/design/modems/support/drivers.htm > For early releases check at: http://linmodems.technion.ac.il/resources.html > The HaM modem is supported, but code is no longer being updated; > there will likely be failures under emerging 2.6 kernels. > The 536EP and five Intel537 modem chipset variants are actively supported. > > Lucent /AgereSystems > The Venus chipset modem uses the Linux seraik drivers and is thus supported. > Modems with digital signal processing (DSP) chipsets are supported: http:/ltmodem.heby.de > For AC97/MC97 soft modems. Initiate software access through code sponsor IBM: > http://www-3.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-52698 > Coding of support for has Not yet begun PCI soft modems with PCI_IDs 11c1:048? > > > Motorola support is at: http://www.motorola.com/softmodem/sm56_download.htm > through 2.4.22 kernels. > > PCTel modem business has been sold to Conexant > Driver compiler resources are at: http://pctelcompdb.sourceforge.net/ > However, the pre-compiled binary component is yet to be assembled > with the gcc 3.nn used in newer Linux releases, > so forced (-f) insertions may be necessary: > insmod -f pctel > Some of the HSP soft modems are supported by the SmartLink slmodem-2.9.10 drivers. > > Broadcom modems in Dell laptops and PCs - can be made to function under 2.4 kernels, but code has not been updated recently. > > --------- end chipset section ---------------------- > > SUPPORT under the current 2.6.nn kernels. > > The more expensive Controller chipset modems are functioning. > SmartLink slmodem-2.9.9 drivers are functioning. > Conexant has 2.6.n support > The Lucent/Agere digital signal processing (DSP) chipsets do have > informal service into 2.6.n kernels and an AgereSystems release is soon expected. > Intel, Agere Systems and Linuxant are firmly expected to continue support into 2.6.nn, > though the Intel HaM software will not be updated to 2.6.n service > > ------------------------------------ > Preparing winmodem drivers will generally require compiling. > If you are not familar with this process DEFINITELY read carefully > the Modem/DOCs/DriverCompiling.txt > > > ======================================================= > COMPILING DRIVERS, for Linux Newbies > > Within the workshop there is an instruction set, the Makefile, and a few tools. You command: > make clean > An elf named "make" comes in, reads Makefile and then cleans up any debris of previous efforts. > Do ALWAYS command "make clean" as a first step before new driver compilations. > The major work of compiling drivers and any associated tools is commanded with: > make > or perhaps > make DriverName > There only remains to command installation of the modem driver(s) and tools with: > make install > Configuration of a dialout utility is done elsewhere, and you can access the Internet. > > It is really that simple, once the workshop with tools has been prepared. > But new drivers have to be compiled with every operaing system update. > The remainder of this text is thus aids you in the preparations, dealing with a variety of special cases. > Most points are covered in much more detail in the Linux Kernel-HOWTO, likely included among the > HOWTO documentation set installed within /usr/share/doc/ folders. > > The core operating system of a PC is comprised of a motherboard, the software kernel, > and its auxilliary code modules. The kernel is the file /boot/vmlinuz-2.6.31-15-generic. > Modules located in subfolders of /lib/modules/2.6.31-15-generic/ . They can be inserted into or removed > from the acting kernel upon demand. This provides adaptablity to the diverse > hardware components of PCs and changing requirments. > > Modem drivers are one type of module. As contrasted to most Linux software, modem driver codes have > some non-public code components. That is the drivers are not fully Open Source, to protect > Intellectual Property of the providing companies. This has a consequence that many Linux distributions > will not or cannot legally supply proprietary modem drivers. Rather the Users must get the > modem code package and direct compiling of the code and driver installation. > > A complementary resource for compiling is a family of FileNames.h, collectively called kernel-headers. > They are both code bits themselves and also call for other code bits their functioning depends on. > Depending on the Linux distribution, kernel-headers may not be automatically installed. > If not they will always be made available on installation media or some Linux repository. > They can be searched for by package names including: kernel-source, linux-source, kernel-headers and 44 > There are always some kernel-headers in afolder /usr/include/. But these are an INCOMPLETE, too small collection > and DO NOT suffice for compiling processes. > > In addition some software utilities may have to be installed. The instructions for compiling are read by make. > A set of compiler tools are installed as a gcc-SomeVersion package. After compiling, the various pieces > and linked dynamically together with "ld". Together wiith some simpler software tools, the ld will > already be installed on Linux systems. Systems using the Debian style maintanence system > additionally require a package "kernel-kbuild-3.n" to properly utilize kernel-headers or 2.6.n kernels. > > The "kernel-headers" are matched with an installed kernel, or must be generated from a kernel-source package. > These are provided in different ways by the various Linux distributions, under 2.6.n kernels: > Redhat and Fedora - installation is coincident with kernel installation, > with placement of the kernel-header base folder in /lib/modules/2.6.31-15-generic/build/ > Mandrake and SuSE/Novell - installation as part of a kernel-source or linux-source packages, > with location at /usr/src/kernel-headers-2.6.31-15-generic or /usr/src/linux-2.6.31-15-generic > Debian and distros using its Package.deb format have names: > kernel-headers-2.6.31-15-generic > linux-headers-2.6.31-15-generic for Ubuntu > and installation is into /usr/src/ > for Xandros, there is a xandros-kernel-source-version.deb which has to be installed > Unpack if necessary with > # cd /usr/src/ > # ls > # tar jxf xandros-kernel-source-version.tar.bz2 > see http://support.xandros.com/kb-view.php?topic=64 for details > but for 2.6.n kernels, the step after: > # make EXTRAVERSION=-x1 oldconfig > should be > # make EXTRAVERSION=-x1 bzImage > Others - ??? > > For the prior generation of 2.4.n kernels, there are special cases. Skip this if your kernel is a 2.6.n or a Debian type. > For RPM using distros, the kernel-source-2.6.31-15-generic or linux-source-2.6.31-15-generic packages must be installed and configured as described below: > 1) SuSE with KernelVersion 2.4.21-144-* or later - install the matching kernel-source package, which does also contain the kernel-headers; > 2) for Fedora II or later, kernel-headers are/were coinstalled with the kernel package; > 3) for all other cases of 2.4.n kernels, the kernel-headers must be prepared from kernel-source. > The preparation can be summarised in a few steps/actions: > Install a kernel-source package representing your kernel. > Change directory (cd) into its base folder. The kernel-source in general > will match only one of several kernels that could have been installed > and NOT necessarily yours. Thus clean out any remnants of earlier usages with: > make mrproper > Copy in your kernel configuration file and have it read with: > make oldconfig > If necessary edit ONLY the fourth line of the Makefile, which completes > the specification of where drivers will be installed to (details below). > The kernel-headers are then assembelled by either: > a) for 2.4.nn kernels by > make dep > b) for 2.6.n kernels, > make bzImage > which includes an integral "make dep" step. > > Modem related resources may or may not have been installed during the primary Linux installation, > as WinModem hardware is often NOT recognized. Search your Distro's package > descriptions for "modem" to reveal the status of related resources. Read > the package description to determine whether pre-compiled modem drivers were provided. > RESOURCES of a few types are needed to get on line. Do PREFERABLE use your System's > package maintenance system for the installation. This should guarantee that > any DEPENDENT packages will be called into the installation process. As a preliminary > 1) Install your distributions package providing the KPPP, WVDIAL and MINICOM dialer utilities. > Dependencies within such packages will also drive the unpacking of ppp related modules > from compressed to a functional form : > module.o.gz --> modules.o > or for 2.6.n kernels > module.ko.gz --> module.ko > In addition these dialers will later aid testing and configuration, > which is to be performed only AFTER, the modem's drivers are installed. > > 2) Download if necessary and modem driver package specific to your modem hardware. > 3a) Install if necessary your distrbution's kernel-source package, necessary for preparing kernel-headers under 2.4.n kernels > Or for Debian style distributions, > 3b) install the kernel-header-2.6.31-15-generic.deb package matching your kernel version 2.6.31-15-generic. > > A KERNEL-SOURCE package must be installed, if a full kernel-header set > is not otherwise provided. Kernel-source packages are now some 30-40 MB now even in compressed form. > The package provided by your Linux Distro SHOULD preferentially be used. > It will usually have some differences from that initially released at http://www.kernel.org . > Typically the installation process will set two symbolic links: > /lib/modules/2.6.31-15-generic/build --> PATH_to/kernel-source-version/ > /usr/src/linux --> PATH_to/kernel-source-version/ > These later enable access to the kernel-headers needed during the modem driver compiling. Check with: > ls -l /lib/modules/2.6.31-15-generic/build > ls -l /usr/src/linux > The former link is more usefull for Systems with alternative boot kernels, > and is mandatory for some modem compiler packages. > > HIGHLY IMPORTANT: the kernel-source as installed in generally does NOT > represent your current kernel version, EVEN if the kernel-version is the same. > Only one of several possible kernels was installed on your System, > and the unpacked kernel-source need NOT represent it exactly!!! > For example, in the RedHat Distro there is a set of kernel-configuration files within > /usr/src/linux/configs/ > Each is specialized for a different CPU (i586, i686, K6, etc), > Yet each will be represented by the VERY SAME version name: "uname -r" . > !!!! Thus a PROPER CONFIGURATION MUST BE DONE by You, before compiling drivers !!!! > > Examples provided below are partially customized from your System settings. > CONFIGURATION is started by moving into the kernel-source folder with one of: > cd /lib/modules/2.6.31-15-generic/build > cd /usr/src/linux > > There is a Makefile on your System at: /lib/modules/2.6.31-15-generic/build/Makefile > with first few lines: > > VERSION = 2 > PATCHLEVEL = 6 > SUBLEVEL = 31 > EXTRAVERSION = .4 > NAME = Man-Eating Seals of Antiquity > > # *DOCUMENTATION* > > For your current kernel, the fourth line should be > EXTRAVERSION = > where has been read from your current kernel version: 2.6.31-15-generic. > But it this does not match what is Actually in the Makefile, > then it represents a Different kernel-header set then that of your kernel!!! > > For Mandrake Linux their will generally be an included "mdk", such as: > EXTRAVERSION = -3.1mdk > SuSE 9.0 had: > EXTRAVERSION = -99-default > The first four makefile lines specify that: > a) the compiled kernel modules/drivers will have encoded version labels such as: > 2.4.21-3.1mkd OR 2.4.21-99-default > b) such modules including modem drivers are installed into sub-folders of > /lib/modules/2.4.21-3.1mkd/ > /lib/modules/2.4.21-99-default/ > The major points are that compiled drivers must be both > kernel-release (the 2.4.21) AND EXTRAVERSION matched with the installed kernel. > Otherwise they may be installed uselessly and not be detected by the kernel > OR there will be a failure upon attempted insertion, with message including: > a list of "unresolved symbols ". > > Kernel-headers may be resident from a prior usage of the kernel-source/. > Check with: > ls include/linux/ > which may display abundant FileNames.h > The version of these headers will be in the UTS line displayed by > cat include/linux/version.h > #define UTS_RELEASE "2.4.21-3.1mdk" (as an example) > > Next, list completely the contents of the kernel-source with: > ls -a > Where the " -a " additionally reveals ".dot-prefixed-confguration-files" such as > .config .hdepend .depends > which may be left over from the prior usage of the kernel-source. Below is an example: > ------------------- > .config .hdepend .depends > COPYING Makefile Rules.make init mm > CREDITS README arch drivers ipc net > Documentation conf.vars fs kernel scripts > MAINTAINERS REPORTING-BUGS crypto include lib > > Configuration of the kernel-source is where almost all the Mistakes occur!!! > Here is a way to do it correctly (but read through EXCEPTIONAL CASES below). > 1)Within kernel-source/ folder, browse the README file for general guidance. > It will relate that the command: > # make mrproper > cleans up leftovers from any previous usage .dot-files and the include/linux/ folder. > Additionally you may need to do an edit within Makefile, but ONLY that 4th line. > 2) If necessary to edit, FIRST make a backup: > cp Makefile Makefile.backup > then edit ONLY the 4th line of Makefile to match the EXTRAVERSION of 2.6.31-15-generic > EXTRAVERSION = - > NEVER change anything else within the Makefile. > > 3) Set the dependencies of the current kernel. > For SuSE 9.0 and later, there is a command which does the following steps > # make cloneconfig && make dep > Also browse the excellent README.SuSE in the kernel-source/ folder > For other Distros, the following steps are necessary, within the kernel-source/ folder > copy the kernel-config file to .config > and DO SPECIFY that " . " > But where is it? For many Distros, it will be the file like > /boot/config-2.6.31-15-generic > matching the output of: > uname -r > Or it may be the target of a symbolic link: /boot/config --> > So > cp /boot/config-2.6.31-15-generic .config > For SuSE 8.0 and earlier versions it is: > cp /boot/vmlinuz.config .config > PLEASE do not omit that "." in .config as it is crucially necessary. > View .config with a text browser. > It is simply a listing of the code components used in the kernel and its modules: > # > # Automatically generated make config: don't edit > # > CONFIG_X86=y > # CONFIG_SBUS is not set > CONFIG_UID16=y > etc. > > 4) The .config file will be read during > # make oldconfig > which feeds its specifications through a process specifying > the SAME inter-dependencies previously used in compiling your kernel, > and may generate additional .dot-config files . They can be displayed with: > # ls -al > > 5) Though it may be redundant after "make mrproper", it will do no harm to: > make clean > 5a) For the SuSe Linux versions 8.0 and previous , there will exist files: > /boot/vmlinuz.autoconf.h > /boot/vmlinuz.version.h > They MUST be copied as: > cp /boot/vmlinuz.autoconf.h /usr/src/linux/include/linux/autoconf.h > cp /boot/vmlinuz.version.h /usr/src/linux/include/linux/version.h > > 6) Now build kernel-headers with: > make dep > for 2.4.n kernels or for 2.6.n kernels > make bzImage > during which you can walk your dog, take a shower, have tea, etc. > 7) Check for resultant FileNames.h with: > ls include/linux/ > and > cat include/linux/version.h > to verify the version. > > COMPILING the MODEM DRIVERS can now finally be done. > Unpack the compiler kit for your modem drivers, > cd into its folder, read any README or INSTALL files, > make clean > FINALLY, your modem drivers will compiled by a command like > make OR make ModuleName > or perhaps > make all > During this process, some of the kernel-header code with be joined > with the supplied modem specific code, and ModemDrivers.o will be produced. > Follow and further instructions in the modem code resource > to install the drivers, often with: > make install > > THEORETICAL ISSUES > > WinModem driver packages commonly include: > 1) a readible Open Source component, which can be readily debugged by > experts in code. This component provides "wrappers" to common > kernel functions for an already complied, or BINARY format, component of the modem code. > > 2) A Closed Source component compiled into the binary form, in which > proprietary information is encrypted. This will include the copyrighted Vn.nn compression algorithms. > In 2004, pre-compiled modem drivers are beginning to be included > for a few winmodems by some Linux distributions. > But the binary format precludes incorporation of the modem drivers in some Linux distributions > for legal reasons, practical reasons, and/or reasons of principle. > > Since almost all the newer PCs are now equipped with WinModems, > many users will have to compile their own linux modem drivers. > Exceptions are the more expensive modems with Controller chipsets, > characteristic of the earliest modems. > They are supported by Open Source serial code included in Linux > distributions (Distros hereafter). > > Winmodems are less expensive because of greatly reduced hardware costs. > They lack Controller chips of the earliest modems, and may additionally lack Digital Signal Processor (DSP) chips of second generation modems. > Functions of Controller based chipsets are replaced by a combination of > software code and/or other System hardware. > > Modems without a controller chip are referred to as "controllerless modems" and > modems lacking both a DSP and controller chips are referred to as "soft modems". > With faster central processor units (CPU), some processing tasks are performed > by the CPU for the controllerless modems. The CPU does nearly all > the signal processing for the "soft modems" lacking a DSP. > > AC97 or MC97 soft modems conform to an ac97_codec, and can host a variety of Subsystems It is the CODEC of the Subsystem which determines which software should be utilized!! > and any modem controllers can host one of a variety of soft modem Subsystems. > There are additionally soft PCI modems without such controllers, which still utilize > the common ac97_modem.o driver. In general it will be YOUR task to identify > the Subsystem codec and compile the needed driver. > > ## end Modem/DOCs/DriverCompiling.txt > > > Packages "agrsm" provide resources for compiling a the agrmodem + agrserial driver pair. > Sadly, there is NO SUPPORT for x86_64 64 bit installations, through the same hardware > will be supported if a compatibile 32 bit Linux installation is done. > There is because of a precompiled 32 bit component, which cannot be united with 64 bit code. > > For the 11c11040 modem chips on High Definition Audio cards, the driver resource > is called dkms-agrsm and maintained at http://linux.zsolttech.com/linmodem/agrsm/ , > There are a few installation formats. First install your Distro's dkms package > The dkms toolset automates compiling, including compiling of needed update drivers > when an update kernel is installed. Test if already installed with: dkms --help > If not installed or on your installation media, check your distribution's repository. > See the example at http://linmodems.technion.ac.il/bigarch/archive-eighth/msg03863.html > For Ubuntu, the repository is at http://packages.ubuntu.com. Comments are more general compiling support are below. > > http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ has copies and some updates > in Debian installation formats and related documentation and tools. > There is a agrsm_howto.txt, though it's leading compilation section is not needed for all cases below. > There are a few cases of support implementation, depending on the host system and particular chip type. > The agrsm-tools package creates symbolic links and runs a first functional test, > provided the wvdial package is installed. > Upon download and copying into your Linux partition, installation can be done with: > sudo dpkg -i agrsm*.deb > or one of the more sophisticated installation tools. > > For a few Ubuntu kernels, driver installation packagea are at > agrsm-2.6.27-7-generic_2.6.27-7.14_i386.deb > agrsm-2.6.27-9-generic_2.6.27-9.14_i386.deb > for 2.6.27-7-generic and 2.6.27-9-generic kernels ONLY. > Resources are at http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ > > For the modem chips 11c1:0620, 11c1:0630 and 11c1:048c(or f), the current confirmed support is with the > agrsm-20090418.tar.gz at http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ > See Josh Crawford's report: http://linmodems.technion.ac.il/bigarch/archive-eighth/msg00475.html. > The 11c1:0620 chipset is also supported by the dkms-agrsm package (reports Hugo Canelli) > > For implementation guidance, get the agrsm_howto.txt from http://linmodems.technion.ac.il/packages/ltmodem/11c1040/ . > However the leading compiling section should be skipped for installation done with dkms tools. > For Debian/Ubuntu related systems also get the from http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ > the agrsm-tools_0.0.1_all.deb. Though lacking drivers, it automates setup of symbolic links initiated by > sudo modprobe agrserial > and also has a utility, called by: > sudo agrsm-test > > For kernels earlier than 2.6.26 the more laborious procedures. > A simplest route is to get from http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ one of: > kernel-2.6.21.0-22.i686.rpm > linux-image-2.6.21.0-22_2.6.21.0-22_i386.deb > as their module set contains the drivers, but just for kernel 2.6.21.0-22. > > For the Ubuntu 2.6.24-19-generic kernel, there is a driver package > agrsm-ubuntu8.04.1-2.6.24-19-generic.tar.gz > > For kernels between 2.6.21 and 2.6.26 read the HOWTO-Agere-11c11040-HDA.html, > which relates a laborious procedure involving kernel-source code. > > A single root/adm command: > modprobe agrserial > will provide for loading both drivers and symbolic /dev/ttySAGR link creation, > if the following two lines to some file in the /etc/modprobe folders. > > install agrserial /sbin/modprobe --ignore-install agrmodem ; /sbin/modprobe --ignore-install agrserial && test -e /dev/ttySAGR || ln -s /dev/ttyAGS3 /dev/ttySAGR > remove agrserial /sbin/modprobe -r --ignore-remove agrserial ; /sbin/modprobe -r --ignore-remove agrmodem && { if test -L /dev/ttySAGR; then rm /dev/ttySAGR; fi } ; true > > They will alternatively be installed by the package agrsm-tools_0.0.1_all.deb >
