[ubuntu] How do i set up a dial up connection? [Archive]

PDA

View Full Version : [ubuntu] How do i set up a dial up connection?

pnt101

May 11th, 2010, 03:27 AM

dineshs

May 11th, 2010, 03:46 AM

what modem is it?usb?serial?internal?
If USB post the output of
lsusb

pnt101

May 11th, 2010, 04:55 AM

O its internal i think. And i press log and this showed up.

--> Ignoring malformed input line: ";Do NOT edit this file by hand!"
--> WvDial: Internet dialer version 1.60
--> Cannot open /dev/modem: No such file or directory
--> Cannot open /dev/modem: No such file or directory
--> Cannot open /dev/modem: No such file or directory

hope that helps

pnt101

May 11th, 2010, 05:24 AM

if you need me to give more info go ahead and ask cuz i really want the internet to start working lol

dineshs

May 11th, 2010, 10:39 AM

I have heard that internal modems are difficult to work in Linux.Please open a terminal (applications-accessories-terminal)and post the output of

lspci
Also read
http://linmodems.technion.ac.il/

pnt101

May 11th, 2010, 10:56 PM

pnt@ubuntu:~$ lspci
00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub (rev 02)
00:01.0 PCI bridge: Intel Corporation 82945G/GZ/P/PL PCI Express Root Port (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
00:02.1 Display controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 01)
00:1d.0 USB Controller: Intel Corporation N10/ICH7 Family USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)
00:1f.2 IDE interface: Intel Corporation N10/ICH7 Family SATA IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 01)
03:02.0 Communication controller: Conexant Systems, Inc. Device 2702 (rev 01)
03:08.0 Ethernet controller: Intel Corporation N10/ICH 7 Family LAN Controller (rev 01)

thats what shows up after i enter the command, so is my modem capatible?

pnt101

May 11th, 2010, 11:27 PM

o yea btw heres my computer info:
windows xp duel booting ubuntu(lastest one)
dell dimension 5150
internal modem
dial up internet

if you need more ask

pnt101

May 12th, 2010, 12:11 AM

btw if you were to reccomend to buy a new modem that would work could u suggest some under $15?

linton575

May 12th, 2010, 02:17 AM

Ok please help me out, im a totally new to ubuntu or any OS other than windows xp. I've installed it and all went fine, now i want to set up a dial up connection witch i dont know how. I've tried going to system/adminstritive/networking but 'networking' isnt there. then i tyr gnome ppp but it says it cant detect a modem. Any help please:)

Hi there. a lot of information out there i found to be misleading, confusing and useless to do with setting up a modem on Ubuntu 9.04 and 10.04. after hours of mucking around i found it was as easy as two steps

sudo apt-get install wvdial

sudo apt-get install gnome-ppp

and thats it!!

if gnome-ppp does not create a symbolic link on the menu you can start it by presing alt-F2 and typing "gnome-ppp"

btw i found that by running "pppconfig" from the terminal which is sugessted in many guides was actually completely unrelated to getting my connection working! i eventually deleted the connection id set up with pppconfig as it was a massive fail. many guides suggest this :|

hope that helps!

pnt101

May 12th, 2010, 04:42 AM

pnt101

May 12th, 2010, 05:23 AM

alright when i type in wvdial command this is what comes after

pnt@ubuntu:~$ pnt@ubuntu:~$ sudo apt-get install wvdial
pnt@ubuntu:~$: command not found
pnt@ubuntu:~$ Reading package lists... Done
Reading: command not found
pnt@ubuntu:~$ Building dependency tree
Building: command not found
pnt@ubuntu:~$ Reading state information... Done
Reading: command not found
pnt@ubuntu:~$ wvdial is already the newest version.
--> WvDial: Internet dialer version 1.60
--> Warning: section [Dialer is] does not exist in wvdial.conf.
--> Warning: section [Dialer already] does not exist in wvdial.conf.
--> Warning: section [Dialer the] does not exist in wvdial.conf.
--> Warning: section [Dialer newest] does not exist in wvdial.conf.
--> Warning: section [Dialer version.] does not exist in wvdial.conf.
--> Cannot open /dev/modem: No such file or directory
--> Cannot open /dev/modem: No such file or directory
--> Cannot open /dev/modem: No such file or directory
pnt@ubuntu:~$ 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
0: command not found

when i type in gnome ppp this shows up

pnt@ubuntu:~$ sudo apt-get install gnome-ppp
Reading package lists... Done
Building dependency tree
Reading state information... Done
wvdial is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

dineshs

May 12th, 2010, 06:48 AM

03:02.0 Communication controller: Conexant Systems, Inc. Device 2702 (rev 01)

I think this is the internal modem.You need to first identify the chipset using scanmodem tool,get the driver,install it and then try gnome-ppp or wvdial.try this link
http://linmodems.org/
OR
http://www.linuxant.com/
(http://www.linuxant.com/drivers/modemident.php)

linton575

May 12th, 2010, 09:09 AM

sudo apt-get install wvdial

sudo apt-get install gnome-ppp

correct me if im wrong but doesnt that require a internet connection to even download that? And my problem right now is that i have gnome ppp installed already, its on my desktop and the icon is a red phone, when i try to set it up i press connect but then it says modem not detected then gives the log i posted above.

http://www.linuxjournal.com/article/5448

il get back to you on this one. ive been trying to get myne going all day now. that guide helped a bunch. but i got other problems holding me back now... :(

also http://tldp.org/HOWTO/Modem-HOWTO-18.html

Lafon

May 12th, 2010, 01:00 PM

What version of Ubuntu are you running? I have 10.04 and it doesn't have wvdial. To get your modem working you first need to use the scanModem tool (someone in this thread already posted the link)find the correct driver and then install it, and then put your dial-up data (number, username, password) in gnome-ppp. If the auto-detect doesn't work it means that your modem isn't recognized(it's probably missing the driver.
Hope this helps

P.S: It doesn't look like you need to update wvdial. from your post it looks like you have the newest version.

pnt101

May 12th, 2010, 11:31 PM

alright i download the tool, what do i do with it? sorry for the idioitic questions im new to this

pnt101

May 13th, 2010, 12:11 AM

o yea btw i found info on my modem if this helps

Name Conexant SmartHSFi V.9x 56K DF PCI Modem
Description Conexant SmartHSFi V.9x 56K DF PCI Modem
Device ID PCI\VEN_14F1&DEV_2702&SUBSYS_8D881028&REV_01\4&5855BE9&0&10F0
Device Type Internal Modem
Attached To COM3
Answer Mode Not Available
PNP Device ID PCI\VEN_14F1&DEV_2702&SUBSYS_8D881028&REV_01\4&5855BE9&0&10F0
Provider Name Conexant
Modem INF Path oem8.inf
Modem INF Section Modem1
Blind Off X4
Blind On X3
Compression Off +DS=0;
Compression On +DS=3;
Error Control Forced +ES=3,2,4;
Error Control Off +ES=1,0,1;
Error Control On +ES=3,0,2;
Flow Control Hard +IFC=2,2;
Flow Control Off +IFC=0,0;
Flow Control Soft +IFC=1,1;
DCB 
Default <
Inactivity Timeout Not Available
Modulation Bell Not Available
Modulation CCITT Not Available
Prefix AT
Pulse P
Reset ATZ<cr>
Responses Key Name Conexant SmartHSFi V.9x 56K DF PCI Modem::Conexant::Conexant
Speaker Mode Dial M1
Speaker Mode Off M0
Speaker Mode On M2
Speaker Mode Setup M3
Speaker Volume High L3
Speaker Volume Low L1
Speaker Volume Med L2
String Format Not Available
Terminator <cr>
Tone T
Memory Address 0xEFBF0000-0xEFBFFFFF
I/O Port 0x0000DCB8-0x0000DCBF
IRQ Channel IRQ 18

pnt101

May 13th, 2010, 12:26 AM

alright this is the outcome in terminal

pnt@ubuntu:~$ '/media/8894-CF21/scanModem.2010042905' gunzip scanModem.gz
UPDATE=2010_04_29
Continuing as this update is only 2 weeks old,
but the current Update is always at: http://linmodems.technion.ac.il

Please rename this script scanModem, or some files will not print out.
Abort with Ctrl-C, or wait 5 seconds to continue.

DISTRIB_ID=Ubuntu

Identifying PCI bus slots with candidate modems.
Running PCIbus cases
Analysing card in PCI bus 03:02.0, writing to scanout.03:02.0
Analysing card in PCI bus 00:1b.0, writing to scanout.00:1b.0
Using scanout.03:02.0 data, and writing guidance to ModemData.txt
Writing DOCs/Intel.txt
Writing DOCs/Conexant.txt
Using scanout.00:1b.0 data, and writing guidance to ModemData.txt

Writing residual guidance customized to your System.
A subfolder Modem/ has been written, containing these files with more detailed Information:
------------------------------------------------------------------------------------------
1stRead.txt Bootup.txt dmesg.txt DOCs ModemData.txt scanout.00:1b.0
scanout.03:02.0 tmp
and in the DOCs subfolder:
Conexant.txt DriverCompiling.txt InfoGeneral.txt Intel.txt Rational.txt
SoftModem.txt Testing.txt UNSUBSCRIBE.txt wvdial.txt YourSystem.txt
-------------------------------------------------------------------------------------------
Please read 1stRead.txt first for Guidance.

JPman

May 13th, 2010, 12:33 AM

Hi there. a lot of information out there i found to be misleading, confusing and useless to do with setting up a modem on Ubuntu 9.04 and 10.04. after hours of mucking around i found it was as easy as two steps

sudo apt-get install wvdial

sudo apt-get install gnome-ppp

and thats it!!

if gnome-ppp does not create a symbolic link on the menu you can start it by presing alt-F2 and typing "gnome-ppp"

btw i found that by running "pppconfig" from the terminal which is sugessted in many guides was actually completely unrelated to getting my connection working! i eventually deleted the connection id set up with pppconfig as it was a massive fail. many guides suggest this :|

hope that helps!

I have the very same problem. Sure if I could connect to the internet I could do the "apt-get" but, catch 22 amigo, I ain't got no internet connection with Ubuntu so?????

Is there a way to use XP to download those two files then install them to Ubuntu? Cause that's the only way to get 'em that I can see.

Please help the two of us out here...

JPMAN:(

pnt101

May 13th, 2010, 01:31 AM

hey dont try to steal my thread lol, what i know is that you can download the debs and then install it through that with the dependencies, so glad i have a iphone for deb knowledge lol

Lafon

May 13th, 2010, 02:31 AM

Alright here's the scoop. To install WvDial use your boot CD. First boot into Ubuntu 10.04 (that's what I have,) then open your installation media folder (memory stick,CD, whatever...)then go to pool/main/w/wvstreams and install all the .deb packages (it will say that these packages are available in the download stream. Forget this for know. Normally you would never do this, but you don't have internet yet). After that go to pool/main/w/wvdial. WvDial is all set (I figured this out like 10 minutes ago). Now to setup. First use the scanModem tool http://linmodems.technion.ac.il/ .
After you figure out your modem type and download and install the appropriate driver type in a terminal
wvdialconf. Or if you're lucky and have gnome-ppp use that. Now after you set up the connection type in a terminal
wvdial you should here the connection noise. I don't really remember after that (I got this far in Gutsy; I now have Lucid). Once you get on the 'net type in a terminal
sudo apt-get install gnome-ppp(if you don't already have it.)
Congratulations you now have a simple graphic dial-up connection in Ubuntu 10.04!

pnt101

May 13th, 2010, 02:33 AM

thats the problem i dont know how to find out what kind of modem i have with the modemscan tool. All i know is this:

Name Conexant SmartHSFi V.9x 56K DF PCI Modem
Description Conexant SmartHSFi V.9x 56K DF PCI Modem
Device ID PCI\VEN_14F1&DEV_2702&SUBSYS_8D881028&REV_01\4&585 5BE9&0&10F0
Device Type Internal Modem
Attached To COM3
Answer Mode Not Available
PNP Device ID PCI\VEN_14F1&DEV_2702&SUBSYS_8D881028&REV_01\4&585 5BE9&0&10F0
Provider Name Conexant
Modem INF Path oem8.inf
Modem INF Section Modem1
Blind Off X4
Blind On X3
Compression Off +DS=0;
Compression On +DS=3;
Error Control Forced +ES=3,2,4;
Error Control Off +ES=1,0,1;
Error Control On +ES=3,0,2;
Flow Control Hard +IFC=2,2;
Flow Control Off +IFC=0,0;
Flow Control Soft +IFC=1,1;
DCB 
Default <
Inactivity Timeout Not Available
Modulation Bell Not Available
Modulation CCITT Not Available
Prefix AT
Pulse P
Reset ATZ<cr>
Responses Key Name Conexant SmartHSFi V.9x 56K DF PCI Modem::Conexant::Conexant
Speaker Mode Dial M1
Speaker Mode Off M0
Speaker Mode On M2
Speaker Mode Setup M3
Speaker Volume High L3
Speaker Volume Low L1
Speaker Volume Med L2
String Format Not Available
Terminator <cr>
Tone T
Memory Address 0xEFBF0000-0xEFBFFFFF
I/O Port 0x0000DCB8-0x0000DCBF
IRQ Channel IRQ 18

Lafon

May 13th, 2010, 02:39 AM

for dell computers check out their website. Dell actually supports linux. I got my hsf softmodem drivers from their website.:popcorn:

alright this is the outcome in terminal

pnt@ubuntu:~$ '/media/8894-CF21/scanModem.2010042905' gunzip scanModem.gz
UPDATE=2010_04_29
Continuing as this update is only 2 weeks old,
but the current Update is always at: http://linmodems.technion.ac.il

Please rename this script scanModem, or some files will not print out.
Abort with Ctrl-C, or wait 5 seconds to continue.

DISTRIB_ID=Ubuntu

Identifying PCI bus slots with candidate modems.
Running PCIbus cases
Analysing card in PCI bus 03:02.0, writing to scanout.03:02.0
Analysing card in PCI bus 00:1b.0, writing to scanout.00:1b.0
Using scanout.03:02.0 data, and writing guidance to ModemData.txt
Writing DOCs/Intel.txt
Writing DOCs/Conexant.txt
Using scanout.00:1b.0 data, and writing guidance to ModemData.txt

Writing residual guidance customized to your System.
A subfolder Modem/ has been written, containing these files with more detailed Information:
------------------------------------------------------------------------------------------
1stRead.txt Bootup.txt dmesg.txt DOCs ModemData.txt scanout.00:1b.0
scanout.03:02.0 tmp
and in the DOCs subfolder:
Conexant.txt DriverCompiling.txt InfoGeneral.txt Intel.txt Rational.txt
SoftModem.txt Testing.txt UNSUBSCRIBE.txt wvdial.txt YourSystem.txt
-------------------------------------------------------------------------------------------
Please read 1stRead.txt first for Guidance.

Lafon

May 13th, 2010, 02:46 AM

It says in the description: its a Conexant SmartHSF1 V.9x 56K DF PCI Modem. You got lucky conexant hsf modems are the easiest to use. just google hsf softmodem drivers and you will find something. Just look around; even if you have to install and uninstall different drivers you will eventually find the right one. Good Luck! ;)

Quote:
Name Conexant SmartHSFi V.9x 56K DF PCI Modem
Description Conexant SmartHSFi V.9x 56K DF PCI Modem
Device ID PCI\VEN_14F1&DEV_2702&SUBSYS_8D881028&REV_01\4&585 5BE9&0&10F0
Device Type Internal Modem
Attached To COM3
Answer Mode Not Available
PNP Device ID PCI\VEN_14F1&DEV_2702&SUBSYS_8D881028&REV_01\4&585 5BE9&0&10F0
Provider Name Conexant
Modem INF Path oem8.inf
Modem INF Section Modem1
Blind Off X4
Blind On X3
Compression Off +DS=0;
Compression On +DS=3;
Error Control Forced +ES=3,2,4;
Error Control Off +ES=1,0,1;
Error Control On +ES=3,0,2;
Flow Control Hard +IFC=2,2;
Flow Control Off +IFC=0,0;
Flow Control Soft +IFC=1,1;
DCB 
Default <
Inactivity Timeout Not Available
Modulation Bell Not Available
Modulation CCITT Not Available
Prefix AT
Pulse P
Reset ATZ<cr>
Responses Key Name Conexant SmartHSFi V.9x 56K DF PCI Modem::Conexant::Conexant
Speaker Mode Dial M1
Speaker Mode Off M0
Speaker Mode On M2
Speaker Mode Setup M3
Speaker Volume High L3
Speaker Volume Low L1
Speaker Volume Med L2
String Format Not Available
Terminator <cr>
Tone T
Memory Address 0xEFBF0000-0xEFBFFFFF
I/O Port 0x0000DCB8-0x0000DCBF
IRQ Channel IRQ 18

mad.max

May 13th, 2010, 03:18 AM

foresthill

May 13th, 2010, 03:40 AM

dineshs

May 13th, 2010, 06:05 AM

Can you post the content of the file ModemData.txt

Lafon

May 13th, 2010, 10:29 AM

If you have Conexant modem the you should go here: DialupModemHowto Conexant (https://help.ubuntu.com/community/DialupModemHowto/Conexant).

There explains how to set up conexant modem, i successfully configured mine, the problem is tha its ubuntu 7.04 - 8.04... so if yours is ubuntu 10.04 im not sure it can work.

Also when i was seting up my modem i got help from linuxant people, you can email to support@linuxant.com

good luck.

I set up mine in gutsy (7.10)and in 10.04 WITHOUT the internet. Just look at one of my previous posts.:)

Been down this road before.

The problem with Linuxant is they charge you about the same amount for their buggy "driver" you'd pay for a brand new external modem. I have six or seven serial modems laying around (I used to collect them). Too bad postage is so expensive, or I'd give you a couple to try out.

If you are running a desktop computer, with a serial port, I would suggest getting a $20 external serial modem and be done with it. Serial modems are essentially plug and play in Linux.

I fought in vain for months trying to get Conexant software modems working in Linux, and believe me, even if your time is only worth 5 cents an hour, it's just not worth the hassle.

Ummm.... I didn't pay for my driver and I have the real thing (not the trial). Dell's Linux website (yes they actually support Ubuntu) has a lot of drivers for Conexant modems (their computers come pre-installed with them). Unfortunately I don't have the link (I'm trying to find it again). If I find the link I'll post it here.:)

Lafon

May 13th, 2010, 10:35 AM

Been down this road before.

The problem with Linuxant is they charge you about the same amount for their buggy "driver" you'd pay for a brand new external modem. I have six or seven serial modems laying around (I used to collect them). Too bad postage is so expensive, or I'd give you a couple to try out.

If you are running a desktop computer, with a serial port, I would suggest getting a $20 external serial modem and be done with it. Serial modems are essentially plug and play in Linux.

I fought in vain for months trying to get Conexant software modems working in Linux, and believe me, even if your time is only worth 5 cents an hour, it's just not worth the hassle.
:confused:
Skip Linuxant. The only thing they were good for was to point me in the direction of scanModem after that nothing works. Try looking for the drivers with Google.
I set up mine in about 2 hours so if my time is worth 5 cents an hour I only pay 10 cents (rather than $20 for the modem).

Did you even read the tutorial I put up? Before you complain I suggest you see how it works before posting all over a thread how yours didn't work (this is a how-to, NOT a how-not-to).

xblinker8

May 13th, 2010, 07:21 PM

@pnt101, try this

1) https://help.ubuntu.com/community/DialupModemHowto/ScanModem

2) https://help.ubuntu.com/community/DialupModemHowto

good luck

pnt101

May 14th, 2010, 03:15 AM

on this website https://help.ubuntu.com/community/DialupModemHowto/Conexant it says it only supports up to 9.04, will it work for 10.04?

pnt101

May 14th, 2010, 03:28 AM

here i ran the scan modem thing, here are all the text files

CPU0 CPU1
0: 73 0 IO-APIC-edge timer
1: 4 0 IO-APIC-edge i8042
8: 1 0 IO-APIC-edge rtc0
9: 0 0 IO-APIC-fasteoi acpi
12: 6 0 IO-APIC-edge i8042
14: 1904 0 IO-APIC-edge ata_piix
15: 0 0 IO-APIC-edge ata_piix
16: 493 1190 IO-APIC-fasteoi i915, HDA Intel
18: 0 0 IO-APIC-fasteoi uhci_hcd:usb4
20: 5850 0 IO-APIC-fasteoi ata_piix, eth0
21: 6231 0 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb2
22: 0 0 IO-APIC-fasteoi uhci_hcd:usb3
23: 0 0 IO-APIC-fasteoi uhci_hcd:usb5
NMI: 0 0 Non-maskable interrupts
LOC: 25843 11706 Local timer interrupts
SPU: 0 0 Spurious interrupts
PMI: 0 0 Performance monitoring interrupts
PND: 0 0 Performance pending work
RES: 4865 2323 Rescheduling interrupts
CAL: 89 989 Function call interrupts
TLB: 644 319 TLB shootdowns
TRM: 0 0 Thermal event interrupts
THR: 0 0 Threshold APIC interrupts
MCE: 0 0 Machine check exceptions
MCP: 1 1 Machine check polls
ERR: 1
MIS: 0

[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.32-21-generic (buildd@rothera) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #32-Ubuntu SMP Fri Apr 16 08:10:02 UTC 2010 (Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2)
[ 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 - 00000000000a0000 (usable)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000003f688c00 (usable)
[ 0.000000] BIOS-e820: 000000003f688c00 - 000000003f68ac00 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000003f68ac00 - 000000003f68cc00 (ACPI data)
[ 0.000000] BIOS-e820: 000000003f68cc00 - 0000000040000000 (reserved)
[ 0.000000] BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fed00400 (reserved)
[ 0.000000] BIOS-e820: 00000000fed20000 - 00000000feda0000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
[ 0.000000] DMI 2.3 present.
[ 0.000000] last_pfn = 0x3f688 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-CFFFF write-protect
[ 0.000000] D0000-EFFFF uncachable
[ 0.000000] F0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask FC0000000 write-back
[ 0.000000] 1 base 03F800000 mask FFF800000 uncachable
[ 0.000000] 2 base 03F700000 mask FFFF00000 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 - 00000000000a0000 (usable)
[ 0.000000] modified: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] modified: 0000000000100000 - 000000003f688c00 (usable)
[ 0.000000] modified: 000000003f688c00 - 000000003f68ac00 (ACPI NVS)
[ 0.000000] modified: 000000003f68ac00 - 000000003f68cc00 (ACPI data)
[ 0.000000] modified: 000000003f68cc00 - 0000000040000000 (reserved)
[ 0.000000] modified: 00000000f0000000 - 00000000f4000000 (reserved)
[ 0.000000] modified: 00000000fec00000 - 00000000fed00400 (reserved)
[ 0.000000] modified: 00000000fed20000 - 00000000feda0000 (reserved)
[ 0.000000] modified: 00000000fee00000 - 00000000fef00000 (reserved)
[ 0.000000] modified: 00000000ffb00000 - 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: 2f13f000 - 2f926122
[ 0.000000] ACPI: RSDP 000feb00 00024 (v02 DELL )
[ 0.000000] ACPI: XSDT 000fd267 0005C (v01 DELL DM051 00000007 ASL 00000061)
[ 0.000000] ACPI: FACP 000fd35f 000F4 (v03 DELL DM051 00000007 ASL 00000061)
[ 0.000000] ACPI: DSDT fffc755f 02D0E (v01 DELL dt_ex 00001000 INTL 20050309)
[ 0.000000] ACPI: FACS 3f688c00 00040
[ 0.000000] ACPI: SSDT fffca38e 000AC (v01 DELL st_ex 00001000 INTL 20050309)
[ 0.000000] ACPI: APIC 000fd453 00072 (v01 DELL DM051 00000007 ASL 00000061)
[ 0.000000] ACPI: BOOT 000fd4c5 00028 (v01 DELL DM051 00000007 ASL 00000061)
[ 0.000000] ACPI: ASF! 000fd4ed 00067 (v16 DELL DM051 00000007 ASL 00000061)
[ 0.000000] ACPI: MCFG 000fd554 0003E (v01 DELL DM051 00000007 ASL 00000061)
[ 0.000000] ACPI: HPET 000fd592 00038 (v01 DELL DM051 00000007 ASL 00000061)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] 126MB 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 - 00008d9e98] TEXT DATA BSS ==> [0000100000 - 00008d9e98]
[ 0.000000] #4 [002f13f000 - 002f926122] RAMDISK ==> [002f13f000 - 002f926122]
[ 0.000000] #5 [000009fc00 - 0000100000] BIOS reserved ==> [000009fc00 - 0000100000]
[ 0.000000] #6 [00008da000 - 00008dd1d4] BRK ==> [00008da000 - 00008dd1d4]
[ 0.000000] #7 [0000007000 - 0000008000] PGTABLE ==> [0000007000 - 0000008000]
[ 0.000000] #8 [0000008000 - 000000f000] BOOTMAP ==> [0000008000 - 000000f000]
[ 0.000000] found SMP MP-table at [c00fe710] fe710
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000000 -> 0x00001000
[ 0.000000] Normal 0x00001000 -> 0x000377fe
[ 0.000000] HighMem 0x000377fe -> 0x0003f688
[ 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 -> 0x000000a0
[ 0.000000] 0: 0x00000100 -> 0x0003f688
[ 0.000000] On node 0 totalpages: 259620
[ 0.000000] free_area_init_node: node 0, pgdat c0798720, node_mem_map c1001000
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 3964 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: 254 pages used for memmap
[ 0.000000] HighMem zone: 32140 pages, LIFO batch:7
[ 0.000000] Using APIC driver default
[ 0.000000] ACPI: PM-Timer IO Port: 0x808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x05] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] disabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 8, 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] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[ 0.000000] SMP: Allowing 4 CPUs, 2 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 24
[ 0.000000] PM: Registered nosave memory: 0000000000002000 - 0000000000006000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
[ 0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
[ 0.000000] Allocating PCI resources starting at 40000000 (gap: 40000000:b0000000)
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:4 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 14 pages/cpu @c1800000 s36024 r0 d21320 u1048576
[ 0.000000] pcpu-alloc: s36024 r0 d21320 u1048576 alloc=1*4194304
[ 0.000000] pcpu-alloc: [0] 0 1 2 3
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 257590
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro quiet splash
[ 0.000000] PID hash table entries: 4096 (order: 2, 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 5194400 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:0003f688)
[ 0.000000] Memory: 1007196k/1038880k available (4673k kernel code, 30428k reserved, 2122k data, 656k init, 129576k 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 : 0xc07a3000 - 0xc0847000 ( 656 kB)
[ 0.000000] .data : 0xc0590613 - 0xc07a2e48 (2122 kB)
[ 0.000000] .text : 0xc0100000 - 0xc0590613 (4673 kB)
[ 0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
[ 0.000000] SLUB: Genslabs=13, HWalign=128, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:2304 nr_irqs:440
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] hpet clockevent registered
[ 0.000000] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
[ 0.000000] Fast TSC calibration using PIT
[ 0.000000] Detected 2793.012 MHz processor.
[ 0.004007] Calibrating delay loop (skipped), value calculated using timer frequency.. 5586.02 BogoMIPS (lpj=11172048)
[ 0.004028] Security Framework initialized
[ 0.004053] AppArmor: AppArmor initialized
[ 0.004063] Mount-cache hash table entries: 512
[ 0.008174] Initializing cgroup subsys ns
[ 0.008180] Initializing cgroup subsys cpuacct
[ 0.008186] Initializing cgroup subsys memory
[ 0.008197] Initializing cgroup subsys devices
[ 0.008201] Initializing cgroup subsys freezer
[ 0.008204] Initializing cgroup subsys net_cls
[ 0.008237] CPU: Trace cache: 12K uops, L1 D cache: 16K
[ 0.008242] CPU: L2 cache: 1024K
[ 0.008245] CPU: Physical Processor ID: 0
[ 0.008248] CPU: Processor Core ID: 0
[ 0.008252] mce: CPU supports 4 MCE banks
[ 0.008267] CPU0: Thermal monitoring enabled (TM1)
[ 0.008273] using mwait in idle threads.
[ 0.008282] Performance Events: no PMU driver, software events only.
[ 0.008291] Checking 'hlt' instruction... OK.
[ 0.028321] ACPI: Core revision 20090903
[ 0.138910] ftrace: converting mcount calls to 0f 1f 44 00 00
[ 0.138917] ftrace: allocating 21771 entries in 43 pages
[ 0.140075] Enabling APIC mode: Flat. Using 1 I/O APICs
[ 0.140405] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.183454] CPU0: Intel(R) Pentium(R) D CPU 2.80GHz stepping 04
[ 0.184001] Booting processor 1 APIC 0x1 ip 0x6000
[ 0.008000] Initializing CPU#1
[ 0.008000] CPU: Trace cache: 12K uops, L1 D cache: 16K
[ 0.008000] CPU: L2 cache: 1024K
[ 0.008000] CPU: Physical Processor ID: 0
[ 0.008000] CPU: Processor Core ID: 1
[ 0.008000] CPU1: Thermal monitoring enabled (TM1)
[ 0.268049] CPU1: Intel(R) Pentium(R) D CPU 2.80GHz stepping 04
[ 0.268067] checking TSC synchronization [CPU#0 -> CPU#1]: passed.
[ 0.272022] Brought up 2 CPUs
[ 0.272026] Total of 2 processors activated (11172.13 BogoMIPS).
[ 0.272376] CPU0 attaching sched-domain:
[ 0.272382] domain 0: span 0-1 level CPU
[ 0.272386] groups: 0 1
[ 0.272394] CPU1 attaching sched-domain:
[ 0.272397] domain 0: span 0-1 level CPU
[ 0.272400] groups: 1 0
[ 0.272509] devtmpfs: initialized
[ 0.272509] regulator: core version 0.5
[ 0.272509] Time: 19:19:15 Date: 05/13/10
[ 0.272509] NET: Registered protocol family 16
[ 0.272509] Trying to unpack rootfs image as initramfs...
[ 0.272509] EISA bus registered
[ 0.272509] ACPI: bus type pci registered
[ 0.272509] PCI: MCFG configuration 0: base f0000000 segment 0 buses 0 - 63
[ 0.272509] PCI: MCFG area at f0000000 reserved in E820
[ 0.272509] PCI: Using MMCONFIG for extended config space
[ 0.272509] PCI: Using configuration type 1 for base access
[ 0.280158] bio: create slab <bio-0> at 0
[ 0.280949] ACPI: EC: Look up EC in DSDT
[ 0.309183] ACPI: BIOS _OSI(Linux) query ignored
[ 0.321999] ACPI: Interpreter enabled
[ 0.322016] ACPI: (supports S0 S1 S3 S4 S5)
[ 0.322052] ACPI: Using IOAPIC for interrupt routing
[ 0.378787] ACPI: No dock devices found.
[ 0.381763] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 0.381929] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 0.381935] pci 0000:00:01.0: PME# disabled
[ 0.381975] pci 0000:00:02.0: reg 10 32bit mmio: [0xeff00000-0xeff7ffff]
[ 0.381982] pci 0000:00:02.0: reg 14 io port: [0xecd8-0xecdf]
[ 0.381989] pci 0000:00:02.0: reg 18 32bit mmio pref: [0xd0000000-0xdfffffff]
[ 0.381996] pci 0000:00:02.0: reg 1c 32bit mmio: [0xefec0000-0xefefffff]
[ 0.382051] pci 0000:00:02.1: reg 10 32bit mmio: [0xeff80000-0xefffffff]
[ 0.382168] pci 0000:00:1b.0: reg 10 64bit mmio: [0xefebc000-0xefebffff]
[ 0.382222] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.382227] pci 0000:00:1b.0: PME# disabled
[ 0.382313] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 0.382318] pci 0000:00:1c.0: PME# disabled
[ 0.382383] pci 0000:00:1d.0: reg 20 io port: [0xff80-0xff9f]
[ 0.382445] pci 0000:00:1d.1: reg 20 io port: [0xff60-0xff7f]
[ 0.382507] pci 0000:00:1d.2: reg 20 io port: [0xff40-0xff5f]
[ 0.382569] pci 0000:00:1d.3: reg 20 io port: [0xff20-0xff3f]
[ 0.382637] pci 0000:00:1d.7: reg 10 32bit mmio: [0xffa80800-0xffa80bff]
[ 0.382699] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[ 0.382705] pci 0000:00:1d.7: PME# disabled
[ 0.382864] pci 0000:00:1f.0: quirk: region 0800-087f claimed by ICH6 ACPI/GPIO/TCO
[ 0.382870] pci 0000:00:1f.0: quirk: region 0880-08bf claimed by ICH6 GPIO
[ 0.382875] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0c00 (mask 007f)
[ 0.382880] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 00e0 (mask 0007)
[ 0.382938] pci 0000:00:1f.1: reg 10 io port: [0x1f0-0x1f7]
[ 0.382947] pci 0000:00:1f.1: reg 14 io port: [0x3f4-0x3f7]
[ 0.382956] pci 0000:00:1f.1: reg 18 io port: [0x170-0x177]
[ 0.382964] pci 0000:00:1f.1: reg 1c io port: [0x374-0x377]
[ 0.382972] pci 0000:00:1f.1: reg 20 io port: [0xffa0-0xffaf]
[ 0.383027] pci 0000:00:1f.2: reg 10 io port: [0xfe00-0xfe07]
[ 0.383035] pci 0000:00:1f.2: reg 14 io port: [0xfe10-0xfe13]
[ 0.383043] pci 0000:00:1f.2: reg 18 io port: [0xfe20-0xfe27]
[ 0.383052] pci 0000:00:1f.2: reg 1c io port: [0xfe30-0xfe33]
[ 0.383060] pci 0000:00:1f.2: reg 20 io port: [0xfea0-0xfeaf]
[ 0.383068] pci 0000:00:1f.2: reg 24 32bit mmio: [0x000000-0x0003ff]
[ 0.383095] pci 0000:00:1f.2: PME# supported from D3hot
[ 0.383100] pci 0000:00:1f.2: PME# disabled
[ 0.383156] pci 0000:00:1f.3: reg 20 io port: [0xece0-0xecff]
[ 0.383242] pci 0000:00:01.0: bridge 32bit mmio: [0xefd00000-0xefdfffff]
[ 0.383303] pci 0000:00:1c.0: bridge 32bit mmio: [0xefc00000-0xefcfffff]
[ 0.383354] pci 0000:03:02.0: reg 10 32bit mmio: [0xefbf0000-0xefbfffff]
[ 0.383363] pci 0000:03:02.0: reg 14 io port: [0xdcb8-0xdcbf]
[ 0.383414] pci 0000:03:02.0: PME# supported from D3hot D3cold
[ 0.383420] pci 0000:03:02.0: PME# disabled
[ 0.383469] pci 0000:03:08.0: reg 10 32bit mmio: [0xefbef000-0xefbeffff]
[ 0.383478] pci 0000:03:08.0: reg 14 io port: [0xdcc0-0xdcff]
[ 0.383530] pci 0000:03:08.0: supports D1 D2
[ 0.383533] pci 0000:03:08.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.383539] pci 0000:03:08.0: PME# disabled
[ 0.383583] pci 0000:00:1e.0: transparent bridge
[ 0.383588] pci 0000:00:1e.0: bridge io port: [0xd000-0xdfff]
[ 0.383594] pci 0000:00:1e.0: bridge 32bit mmio: [0xefb00000-0xefbfffff]
[ 0.383617] pci_bus 0000:00: on NUMA node 0
[ 0.383624] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 0.384141] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI4._PRT]
[ 0.384514] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI2._PRT]
[ 0.384806] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
[ 0.886276] Freeing initrd memory: 8092k freed
[ 1.015839] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 15)
[ 1.016391] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *9 10 11 12 15)
[ 1.016796] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 15)
[ 1.017193] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 11 12 15) *0, disabled.
[ 1.017643] ACPI: PCI Interrupt Link [LNKE] (IRQs *3 4 5 6 7 9 10 11 12 15)
[ 1.018031] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 *10 11 12 15)
[ 1.018449] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 *9 10 11 12 15)
[ 1.018870] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 *4 5 6 7 9 10 11 12 15)
[ 1.019071] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks= none
[ 1.019090] vgaarb: loaded
[ 1.019269] SCSI subsystem initialized
[ 1.019317] libata version 3.00 loaded.
[ 1.019317] usbcore: registered new interface driver usbfs
[ 1.019317] usbcore: registered new interface driver hub
[ 1.019317] usbcore: registered new device driver usb
[ 1.019317] ACPI: WMI: Mapper loaded
[ 1.019317] PCI: Using ACPI for IRQ routing
[ 1.020010] NetLabel: Initializing
[ 1.020013] NetLabel: domain hash size = 128
[ 1.020015] NetLabel: protocols = UNLABELED CIPSOv4
[ 1.020034] NetLabel: unlabeled traffic allowed by default
[ 1.020091] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 1.020100] hpet0: 3 comparators, 64-bit 14.318180 MHz counter
[ 1.024019] Switching to clocksource tsc
[ 1.026907] AppArmor: AppArmor Filesystem Enabled
[ 1.026925] pnp: PnP ACPI init
[ 1.026946] ACPI: bus type pnp registered
[ 1.032529] pnp 00:01: io resource (0x800-0x85f) overlaps 0000:00:1f.0 BAR 13 (0x800-0x87f), disabling
[ 1.032535] pnp 00:01: io resource (0x860-0x8ff) overlaps 0000:00:1f.0 BAR 13 (0x800-0x87f), disabling
[ 1.052102] pnp: PnP ACPI: found 8 devices
[ 1.052105] ACPI: ACPI bus type pnp unregistered
[ 1.052112] PnPBIOS: Disabled by ACPI PNP
[ 1.052129] system 00:01: ioport range 0xc00-0xc7f has been reserved
[ 1.052143] system 00:06: iomem range 0x0-0x9ffff could not be reserved
[ 1.052149] system 00:06: iomem range 0x100000-0xffffff could not be reserved
[ 1.052154] system 00:06: iomem range 0x1000000-0x3f688bff could not be reserved
[ 1.052158] system 00:06: iomem range 0xf0000-0xfffff could not be reserved
[ 1.052162] system 00:06: iomem range 0xc0000-0xcffff could not be reserved
[ 1.052166] system 00:06: iomem range 0xfec00000-0xfecfffff could not be reserved
[ 1.052170] system 00:06: iomem range 0xfee00000-0xfeefffff has been reserved
[ 1.052174] system 00:06: iomem range 0xfed20000-0xfed9ffff has been reserved
[ 1.052178] system 00:06: iomem range 0xffb00000-0xffbfffff has been reserved
[ 1.052182] system 00:06: iomem range 0xffc00000-0xffffffff has been reserved
[ 1.052191] system 00:07: ioport range 0x100-0x1fe could not be reserved
[ 1.052195] system 00:07: ioport range 0x200-0x277 has been reserved
[ 1.052199] system 00:07: ioport range 0x280-0x2e7 has been reserved
[ 1.052203] system 00:07: ioport range 0x2e8-0x2ef has been reserved
[ 1.052206] system 00:07: ioport range 0x2f0-0x2f7 has been reserved
[ 1.052210] system 00:07: ioport range 0x2f8-0x2ff has been reserved
[ 1.052214] system 00:07: ioport range 0x300-0x377 could not be reserved
[ 1.052217] system 00:07: ioport range 0x380-0x3bb has been reserved
[ 1.052221] system 00:07: ioport range 0x3c0-0x3e7 could not be reserved
[ 1.052225] system 00:07: ioport range 0x3f6-0x3f7 could not be reserved
[ 1.052229] system 00:07: ioport range 0x400-0x4cf has been reserved
[ 1.052232] system 00:07: ioport range 0x4d2-0x57f has been reserved
[ 1.052236] system 00:07: ioport range 0x580-0x677 has been reserved
[ 1.052240] system 00:07: ioport range 0x680-0x777 has been reserved
[ 1.052243] system 00:07: ioport range 0x780-0x7bb has been reserved
[ 1.052247] system 00:07: ioport range 0x7c0-0x7ff has been reserved
[ 1.052251] system 00:07: ioport range 0x8e0-0x8ff has been reserved
[ 1.052255] system 00:07: ioport range 0x900-0x9fe has been reserved
[ 1.052258] system 00:07: ioport range 0xa00-0xafe has been reserved
[ 1.052262] system 00:07: ioport range 0xb00-0xbfe has been reserved
[ 1.052266] system 00:07: ioport range 0xc80-0xcaf has been reserved
[ 1.052269] system 00:07: ioport range 0xcb0-0xcbf has been reserved
[ 1.052273] system 00:07: ioport range 0xcc0-0xcf7 has been reserved
[ 1.052277] system 00:07: ioport range 0xd00-0xdfe has been reserved
[ 1.052280] system 00:07: ioport range 0xe00-0xefe has been reserved
[ 1.052284] system 00:07: ioport range 0xf00-0xffe has been reserved
[ 1.052288] system 00:07: ioport range 0x2000-0x20fe has been reserved
[ 1.052292] system 00:07: ioport range 0x2100-0x21fe has been reserved
[ 1.052296] system 00:07: ioport range 0x2200-0x22fe has been reserved
[ 1.052299] system 00:07: ioport range 0x2300-0x23fe has been reserved
[ 1.052303] system 00:07: ioport range 0x2400-0x24fe has been reserved
[ 1.052307] system 00:07: ioport range 0x2500-0x25fe has been reserved
[ 1.052311] system 00:07: ioport range 0x2600-0x26fe has been reserved
[ 1.052315] system 00:07: ioport range 0x2700-0x27fe has been reserved
[ 1.052318] system 00:07: ioport range 0x2800-0x28fe has been reserved
[ 1.052322] system 00:07: ioport range 0x2900-0x29fe has been reserved
[ 1.052326] system 00:07: ioport range 0x2a00-0x2afe has been reserved
[ 1.052330] system 00:07: ioport range 0x2b00-0x2bfe has been reserved
[ 1.052334] system 00:07: ioport range 0x2c00-0x2cfe has been reserved
[ 1.052338] system 00:07: ioport range 0x2d00-0x2dfe has been reserved
[ 1.052342] system 00:07: ioport range 0x2e00-0x2efe has been reserved
[ 1.052345] system 00:07: ioport range 0x2f00-0x2ffe has been reserved
[ 1.052349] system 00:07: ioport range 0x5000-0x50fe has been reserved
[ 1.052353] system 00:07: ioport range 0x5100-0x51fe has been reserved
[ 1.052357] system 00:07: ioport range 0x5200-0x52fe has been reserved
[ 1.052361] system 00:07: ioport range 0x5300-0x53fe has been reserved
[ 1.052365] system 00:07: ioport range 0x5400-0x54fe has been reserved
[ 1.052369] system 00:07: ioport range 0x5500-0x55fe has been reserved
[ 1.052372] system 00:07: ioport range 0x5600-0x56fe has been reserved
[ 1.052376] system 00:07: ioport range 0x5700-0x57fe has been reserved
[ 1.052380] system 00:07: ioport range 0x5800-0x58fe has been reserved
[ 1.052384] system 00:07: ioport range 0x5900-0x59fe has been reserved
[ 1.052388] system 00:07: ioport range 0x5a00-0x5afe has been reserved
[ 1.052397] system 00:07: ioport range 0x5b00-0x5bfe has been reserved
[ 1.052402] system 00:07: ioport range 0x5c00-0x5cfe has been reserved
[ 1.052406] system 00:07: ioport range 0x5d00-0x5dfe has been reserved
[ 1.052410] system 00:07: ioport range 0x5e00-0x5efe has been reserved
[ 1.052414] system 00:07: ioport range 0x5f00-0x5ffe has been reserved
[ 1.052418] system 00:07: ioport range 0x6000-0x60fe has been reserved
[ 1.052422] system 00:07: ioport range 0x6100-0x61fe has been reserved
[ 1.052426] system 00:07: ioport range 0x6200-0x62fe has been reserved
[ 1.052430] system 00:07: ioport range 0x6300-0x63fe has been reserved
[ 1.052434] system 00:07: ioport range 0x6400-0x64fe has been reserved
[ 1.052438] system 00:07: ioport range 0x6500-0x65fe has been reserved
[ 1.052442] system 00:07: ioport range 0x6600-0x66fe has been reserved
[ 1.052446] system 00:07: ioport range 0x6700-0x67fe has been reserved
[ 1.052451] system 00:07: ioport range 0x6800-0x68fe has been reserved
[ 1.052455] system 00:07: ioport range 0x6900-0x69fe has been reserved
[ 1.052459] system 00:07: ioport range 0x6a00-0x6afe has been reserved
[ 1.052463] system 00:07: ioport range 0x6b00-0x6bfe has been reserved
[ 1.052467] system 00:07: ioport range 0x6c00-0x6cfe has been reserved
[ 1.052471] system 00:07: ioport range 0x6d00-0x6dfe has been reserved
[ 1.052475] system 00:07: ioport range 0x6e00-0x6efe has been reserved
[ 1.052479] system 00:07: ioport range 0x6f00-0x6ffe has been reserved
[ 1.052484] system 00:07: ioport range 0xa000-0xa0fe has been reserved
[ 1.052488] system 00:07: ioport range 0xa100-0xa1fe has been reserved
[ 1.052492] system 00:07: ioport range 0xa200-0xa2fe has been reserved
[ 1.052496] system 00:07: ioport range 0xa300-0xa3fe has been reserved
[ 1.052501] system 00:07: ioport range 0xa400-0xa4fe has been reserved
[ 1.052505] system 00:07: ioport range 0xa500-0xa5fe has been reserved
[ 1.052509] system 00:07: ioport range 0xa600-0xa6fe has been reserved
[ 1.052514] system 00:07: ioport range 0xa700-0xa7fe has been reserved
[ 1.052518] system 00:07: ioport range 0xa800-0xa8fe has been reserved
[ 1.052523] system 00:07: ioport range 0xa900-0xa9fe has been reserved
[ 1.052527] system 00:07: ioport range 0xaa00-0xaafe has been reserved
[ 1.052531] system 00:07: ioport range 0xab00-0xabfe has been reserved
[ 1.052536] system 00:07: ioport range 0xac00-0xacfe has been reserved
[ 1.052544] system 00:07: ioport range 0xad00-0xadfe has been reserved
[ 1.052550] system 00:07: ioport range 0xae00-0xaefe has been reserved
[ 1.052554] system 00:07: ioport range 0xaf00-0xaffe has been reserved
[ 1.052559] system 00:07: iomem range 0xf0000000-0xf3ffffff has been reserved
[ 1.052563] system 00:07: iomem range 0xfeda0000-0xfedacfff has been reserved
[ 1.087385] pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
[ 1.087389] pci 0000:00:01.0: IO window: disabled
[ 1.087395] pci 0000:00:01.0: MEM window: 0xefd00000-0xefdfffff
[ 1.087399] pci 0000:00:01.0: PREFETCH window: disabled
[ 1.087406] pci 0000:00:1c.0: PCI bridge, secondary bus 0000:02
[ 1.087410] pci 0000:00:1c.0: IO window: 0x1000-0x1fff
[ 1.087417] pci 0000:00:1c.0: MEM window: 0xefc00000-0xefcfffff
[ 1.087423] pci 0000:00:1c.0: PREFETCH window: 0x00000040000000-0x000000401fffff
[ 1.087431] pci 0000:00:1e.0: PCI bridge, secondary bus 0000:03
[ 1.087435] pci 0000:00:1e.0: IO window: 0xd000-0xdfff
[ 1.087442] pci 0000:00:1e.0: MEM window: 0xefb00000-0xefbfffff
[ 1.087447] pci 0000:00:1e.0: PREFETCH window: disabled
[ 1.087463] alloc irq_desc for 16 on node -1
[ 1.087466] alloc kstat_irqs on node -1
[ 1.087474] pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 1.087480] pci 0000:00:01.0: setting latency timer to 64
[ 1.087491] pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 1.087496] pci 0000:00:1c.0: setting latency timer to 64
[ 1.087505] pci 0000:00:1e.0: setting latency timer to 64
[ 1.087511] pci_bus 0000:00: resource 0 io: [0x00-0xffff]
[ 1.087515] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
[ 1.087518] pci_bus 0000:01: resource 1 mem: [0xefd00000-0xefdfffff]
[ 1.087522] pci_bus 0000:02: resource 0 io: [0x1000-0x1fff]
[ 1.087526] pci_bus 0000:02: resource 1 mem: [0xefc00000-0xefcfffff]
[ 1.087529] pci_bus 0000:02: resource 2 pref mem [0x40000000-0x401fffff]
[ 1.087533] pci_bus 0000:03: resource 0 io: [0xd000-0xdfff]
[ 1.087536] pci_bus 0000:03: resource 1 mem: [0xefb00000-0xefbfffff]
[ 1.087540] pci_bus 0000:03: resource 3 io: [0x00-0xffff]
[ 1.087543] pci_bus 0000:03: resource 4 mem: [0x000000-0xffffffff]
[ 1.087596] NET: Registered protocol family 2
[ 1.087747] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 1.088231] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[ 1.088785] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[ 1.089090] TCP: Hash tables configured (established 131072 bind 65536)
[ 1.089094] TCP reno registered
[ 1.089242] NET: Registered protocol family 1
[ 1.089274] pci 0000:00:02.0: Boot video device
[ 1.089392] pci 0000:03:08.0: Firmware left e100 interrupts enabled; disabling
[ 1.089434] Simple Boot Flag at 0x7a set to 0x1
[ 1.089677] cpufreq-nforce2: No nForce2 chipset.
[ 1.089721] Scanning for low memory corruption every 60 seconds
[ 1.089886] audit: initializing netlink socket (disabled)
[ 1.089901] type=2000 audit(1273778356.088:1): initialized
[ 1.099657] highmem bounce pool size: 64 pages
[ 1.099665] HugeTLB registered 4 MB page size, pre-allocated 0 pages
[ 1.101883] VFS: Disk quotas dquot_6.5.2
[ 1.101972] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 1.102841] fuse init (API version 7.13)
[ 1.102972] msgmni has been set to 1731
[ 1.103298] alg: No test for stdrng (krng)
[ 1.103384] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[ 1.103388] io scheduler noop registered
[ 1.103391] io scheduler anticipatory registered
[ 1.103394] io scheduler deadline registered
[ 1.103453] io scheduler cfq registered (default)
[ 1.103643] alloc irq_desc for 24 on node -1
[ 1.103647] alloc kstat_irqs on node -1
[ 1.103659] pcieport 0000:00:01.0: irq 24 for MSI/MSI-X
[ 1.103667] pcieport 0000:00:01.0: setting latency timer to 64
[ 1.103804] alloc irq_desc for 25 on node -1
[ 1.103807] alloc kstat_irqs on node -1
[ 1.103817] pcieport 0000:00:1c.0: irq 25 for MSI/MSI-X
[ 1.103828] pcieport 0000:00:1c.0: setting latency timer to 64
[ 1.103952] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 1.104055] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 1.104176] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
[ 1.104187] ACPI: Power Button [VBTN]
[ 1.104261] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[ 1.104265] ACPI: Power Button [PWRF]
[ 1.105037] processor LNXCPU:00: registered as cooling_device0
[ 1.105091] processor LNXCPU:01: registered as cooling_device1
[ 1.154675] isapnp: Scanning for PnP cards...
[ 1.156810] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 1.158649] brd: module loaded
[ 1.159362] loop: module loaded
[ 1.159495] input: Macintosh mouse button emulation as /devices/virtual/input/input2
[ 1.159627] ata_piix 0000:00:1f.1: version 2.13
[ 1.159644] ata_piix 0000:00:1f.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 1.159698] ata_piix 0000:00:1f.1: setting latency timer to 64
[ 1.159811] scsi0 : ata_piix
[ 1.159924] scsi1 : ata_piix
[ 1.159976] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
[ 1.159980] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
[ 1.160027] alloc irq_desc for 20 on node -1
[ 1.160030] alloc kstat_irqs on node -1
[ 1.160039] ata_piix 0000:00:1f.2: PCI INT C -> GSI 20 (level, low) -> IRQ 20
[ 1.160046] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
[ 1.208196] ata2: port disabled. ignoring.
[ 1.320021] ata_piix 0000:00:1f.2: setting latency timer to 64
[ 1.320084] scsi2 : ata_piix
[ 1.320165] scsi3 : ata_piix
[ 1.320218] ata3: SATA max UDMA/133 cmd 0xfe00 ctl 0xfe10 bmdma 0xfea0 irq 20
[ 1.320222] ata4: SATA max UDMA/133 cmd 0xfe20 ctl 0xfe30 bmdma 0xfea8 irq 20
[ 1.320819] Fixed MDIO Bus: probed
[ 1.320874] PPP generic driver version 2.4.2
[ 1.320939] tun: Universal TUN/TAP device driver, 1.6
[ 1.320943] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 1.321069] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.321094] alloc irq_desc for 21 on node -1
[ 1.321097] alloc kstat_irqs on node -1
[ 1.321104] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 1.321123] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[ 1.321128] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[ 1.321172] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
[ 1.321201] ehci_hcd 0000:00:1d.7: using broken periodic workaround
[ 1.321215] ehci_hcd 0000:00:1d.7: debug port 1
[ 1.325116] ehci_hcd 0000:00:1d.7: cache line size of 128 is not supported
[ 1.325164] ehci_hcd 0000:00:1d.7: irq 21, io mem 0xffa80800
[ 1.344013] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 1.344154] usb usb1: configuration #1 chosen from 1 choice
[ 1.344198] hub 1-0:1.0: USB hub found
[ 1.344209] hub 1-0:1.0: 8 ports detected
[ 1.344296] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.344321] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.344357] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 1.344368] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[ 1.344372] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 1.344420] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
[ 1.344447] uhci_hcd 0000:00:1d.0: irq 21, io base 0x0000ff80
[ 1.344569] usb usb2: configuration #1 chosen from 1 choice
[ 1.344608] hub 2-0:1.0: USB hub found
[ 1.344617] hub 2-0:1.0: 2 ports detected
[ 1.344681] alloc irq_desc for 22 on node -1
[ 1.344685] alloc kstat_irqs on node -1
[ 1.344691] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 22 (level, low) -> IRQ 22
[ 1.344699] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 1.344704] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 1.344751] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
[ 1.344785] uhci_hcd 0000:00:1d.1: irq 22, io base 0x0000ff60
[ 1.344902] usb usb3: configuration #1 chosen from 1 choice
[ 1.344941] hub 3-0:1.0: USB hub found
[ 1.344951] hub 3-0:1.0: 2 ports detected
[ 1.345017] alloc irq_desc for 18 on node -1
[ 1.345020] alloc kstat_irqs on node -1
[ 1.345026] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[ 1.345034] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[ 1.345039] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[ 1.345084] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
[ 1.345123] uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000ff40
[ 1.345246] usb usb4: configuration #1 chosen from 1 choice
[ 1.345288] hub 4-0:1.0: USB hub found
[ 1.345298] hub 4-0:1.0: 2 ports detected
[ 1.345361] alloc irq_desc for 23 on node -1
[ 1.345364] alloc kstat_irqs on node -1
[ 1.345370] uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 23 (level, low) -> IRQ 23
[ 1.345379] uhci_hcd 0000:00:1d.3: setting latency timer to 64
[ 1.345383] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[ 1.345433] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
[ 1.345466] uhci_hcd 0000:00:1d.3: irq 23, io base 0x0000ff20
[ 1.345588] usb usb5: configuration #1 chosen from 1 choice
[ 1.345630] hub 5-0:1.0: USB hub found
[ 1.345639] hub 5-0:1.0: 2 ports detected
[ 1.345780] PNP: No PS/2 controller found. Probing ports directly.
[ 1.348648] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.348659] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 1.348770] mice: PS/2 mouse device common for all mice
[ 1.348930] rtc_cmos 00:05: RTC can wake from S4
[ 1.348985] rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
[ 1.349015] rtc0: alarms up to one day, 242 bytes nvram, hpet irqs
[ 1.349167] device-mapper: uevent: version 1.0.3
[ 1.349307] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
[ 1.349392] device-mapper: multipath: version 1.1.0 loaded
[ 1.349396] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 1.349555] EISA: Probing bus 0 at eisa.0
[ 1.349559] EISA: Cannot allocate resource for mainboard
[ 1.349563] Cannot allocate resource for EISA slot 1
[ 1.349565] Cannot allocate resource for EISA slot 2
[ 1.349576] Cannot allocate resource for EISA slot 5
[ 1.349579] Cannot allocate resource for EISA slot 6
[ 1.349590] EISA: Detected 0 cards.
[ 1.349694] cpuidle: using governor ladder
[ 1.349698] cpuidle: using governor menu
[ 1.350363] TCP cubic registered
[ 1.350550] NET: Registered protocol family 10
[ 1.351240] lo: Disabled Privacy Extensions
[ 1.351783] NET: Registered protocol family 17
[ 1.351852] Using IPI No-Shortcut mode
[ 1.351960] PM: Resume from disk failed.
[ 1.351980] registered taskstats version 1
[ 1.352334] Magic number: 10:257:344
[ 1.352356] tty tty61: hash matches
[ 1.352418] rtc_cmos 00:05: setting system clock to 2010-05-13 19:19:16 UTC (1273778356)
[ 1.352422] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 1.352425] EDD information not available.
[ 1.376357] ata1.00: ATAPI: Optiarc DVD+/-RW ND-3570A, 104B, max UDMA/33
[ 1.428262] ata1.00: configured for UDMA/33
[ 1.499217] ata3.00: ATA-7: WDC WD800JD-75MSA3, 10.01E04, max UDMA/133
[ 1.499221] ata3.00: 156250000 sectors, multi 8: LBA48 NCQ (depth 0/32)
[ 1.507856] isapnp: No Plug & Play device found
[ 1.508379] ata3.00: configured for UDMA/133
[ 1.509254] scsi 0:0:0:0: CD-ROM Optiarc DVD+-RW ND-3570A 104B PQ: 0 ANSI: 5
[ 1.512128] sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
[ 1.512132] Uniform CD-ROM driver Revision: 3.20
[ 1.512275] sr 0:0:0:0: Attached scsi CD-ROM sr0
[ 1.512354] sr 0:0:0:0: Attached scsi generic sg0 type 5
[ 1.512537] scsi 2:0:0:0: Direct-Access ATA WDC WD800JD-75MS 10.0 PQ: 0 ANSI: 5
[ 1.512714] sd 2:0:0:0: Attached scsi generic sg1 type 0
[ 1.512741] sd 2:0:0:0: [sda] 156250000 512-byte logical blocks: (80.0 GB/74.5 GiB)
[ 1.512835] sd 2:0:0:0: [sda] Write Protect is off
[ 1.512840] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.512877] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.513104] sda: sda1
[ 1.542791] sd 2:0:0:0: [sda] Attached SCSI disk
[ 1.542824] Freeing unused kernel memory: 656k freed
[ 1.543364] Write protecting the kernel text: 4676k
[ 1.543423] Write protecting the kernel read-only data: 1840k
[ 1.568977] udev: starting version 151
[ 1.691181] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[ 1.691186] e100: Copyright(c) 1999-2006 Intel Corporation
[ 1.691237] e100 0000:03:08.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 1.717638] e100 0000:03:08.0: PME# disabled
[ 1.718822] e100: eth0: e100_probe: addr 0xefbef000, irq 20, MAC addr 00:13:72:c9:99:99
[ 1.764028] usb 1-8: new high speed USB device using ehci_hcd and address 4
[ 1.902225] usb 1-8: configuration #1 chosen from 1 choice
[ 1.912687] Initializing USB Mass Storage driver...
[ 1.912841] scsi4 : SCSI emulation for USB Mass Storage devices
[ 1.913001] usbcore: registered new interface driver usb-storage
[ 1.913005] USB Mass Storage support registered.
[ 1.913142] usb-storage: device found at 4
[ 1.913144] usb-storage: waiting for device to settle before scanning
[ 2.140015] usb 2-1: new low speed USB device using uhci_hcd and address 2
[ 2.322609] usb 2-1: configuration #1 chosen from 1 choice
[ 2.340237] usbcore: registered new interface driver hiddev
[ 2.353809] input: Microsoft Microsoft® 2.4GHz Transceiver V1.0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input3
[ 2.353933] generic-usb 0003:045E:071D.0001: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Microsoft® 2.4GHz Transceiver V1.0] on usb-0000:00:1d.0-1/input0
[ 2.483734] input: Microsoft Microsoft® 2.4GHz Transceiver V1.0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.1/input/input4
[ 2.483860] generic-usb 0003:045E:071D.0002: input,hidraw1: USB HID v1.11 Mouse [Microsoft Microsoft® 2.4GHz Transceiver V1.0] on usb-0000:00:1d.0-1/input1
[ 2.483898] usbcore: registered new interface driver usbhid
[ 2.483902] usbhid: v2.6:USB HID core driver
[ 2.564015] usb 2-2: new low speed USB device using uhci_hcd and address 3
[ 2.744605] usb 2-2: configuration #1 chosen from 1 choice
[ 2.789239] input: Microsoft Microsoft USB Wireless Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/input/input5
[ 2.789800] generic-usb 0003:045E:00B9.0003: input,hidraw2: USB HID v1.11 Mouse [Microsoft Microsoft USB Wireless Mouse] on usb-0000:00:1d.0-2/input0
[ 6.912998] usb-storage: device scan complete
[ 6.915232] scsi 4:0:0:0: Direct-Access Generic STORAGE DEVICE 9407 PQ: 0 ANSI: 0
[ 6.916327] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 7.148457] sd 4:0:0:0: [sdb] 3862528 512-byte logical blocks: (1.97 GB/1.84 GiB)
[ 7.149574] sd 4:0:0:0: [sdb] Write Protect is off
[ 7.149578] sd 4:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 7.149582] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 7.152324] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 7.152329] sdb: sdb1 sdb2 < sdb5 >
[ 7.159944] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 7.159949] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[ 7.253059] EXT4-fs (loop0): mounted filesystem with ordered data mode
[ 17.380280] udev: starting version 151
[ 17.604588] Linux agpgart interface v0.103
[ 17.611272] intel_rng: Firmware space is locked read-only. If you can't or
[ 17.611275] intel_rng: don't want to disable this in firmware setup, and if
[ 17.611277] intel_rng: you are certain that your system has a functional
[ 17.611278] intel_rng: RNG, try using the 'no_fwh_detect' option.
[ 17.611351] agpgart-intel 0000:00:00.0: Intel 945G Chipset
[ 17.611827] agpgart-intel 0000:00:00.0: detected 7932K stolen memory
[ 17.615369] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
[ 17.633150] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
[ 17.742235] dell-wmi: No known WMI GUID found
[ 17.758242] [drm] Initialized drm 1.1.0 20060810
[ 17.770810] lp: driver loaded but no devices found
[ 17.782616] type=1505 audit(1273799972.927:2): operation="profile_load" pid=554 name="/sbin/dhclient3"
[ 17.783435] type=1505 audit(1273799972.927:3): operation="profile_load" pid=554 name="/usr/lib/NetworkManager/nm-dhcp-client.action"
[ 17.783833] type=1505 audit(1273799972.927:4): operation="profile_load" pid=554 name="/usr/lib/connman/scripts/dhclient-script"
[ 17.848766] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 17.848776] i915 0000:00:02.0: setting latency timer to 64
[ 17.868585] [drm] set up 7M of stolen space
[ 17.869433] [drm] initialized overlay support
[ 18.037466] fb0: inteldrmfb frame buffer device
[ 18.037471] registered panic notifier
[ 18.037481] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[ 18.042418] vga16fb: initializing
[ 18.042424] vga16fb: mapped to 0xc00a0000
[ 18.042431] vga16fb: not registering due to another framebuffer present
[ 18.128611] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 18.128710] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 18.186116] Console: switching to colour frame buffer device 160x64
[ 18.237395] input: HDA Intel Line In at Ext Rear Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input6
[ 18.237654] input: HDA Intel Mic at Ext Front Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
[ 18.237944] input: HDA Intel Mic at Ext Rear Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[ 18.238310] input: HDA Intel Speaker at Ext Rear Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[ 18.238573] input: HDA Intel Speaker at Ext Rear Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[ 18.238825] input: HDA Intel Speaker at Ext Rear Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 18.239077] input: HDA Intel HP Out at Ext Front Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[ 19.629423] Adding 261112k swap on /host/ubuntu/disks/swap.disk. Priority:-1 extents:1 across:261112k
[ 19.824347] type=1505 audit(1273799974.971:5): operation="profile_load" pid=728 name="/usr/share/gdm/guest-session/Xsession"
[ 19.826711] type=1505 audit(1273799974.971:6): operation="profile_replace" pid=729 name="/sbin/dhclient3"
[ 19.827466] type=1505 audit(1273799974.971:7): operation="profile_replace" pid=729 name="/usr/lib/NetworkManager/nm-dhcp-client.action"
[ 19.827873] type=1505 audit(1273799974.971:8): operation="profile_replace" pid=729 name="/usr/lib/connman/scripts/dhclient-script"
[ 19.832121] type=1505 audit(1273799974.979:9): operation="profile_load" pid=730 name="/usr/bin/evince"
[ 19.841910] type=1505 audit(1273799974.987:10): operation="profile_load" pid=730 name="/usr/bin/evince-previewer"
[ 19.847695] type=1505 audit(1273799974.991:11): operation="profile_load" pid=730 name="/usr/bin/evince-thumbnailer"
[ 19.914509] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 20.113238] ppdev: user-space parallel port driver

Module Size Used by
nls_iso8859_1 3249 1
nls_cp437 4919 1
vfat 8901 1
fat 47767 1 vfat
binfmt_misc 6587 1
ppdev 5259 0
snd_hda_codec_idt 51914 1
snd_hda_intel 21877 2
snd_hda_codec 74201 2 snd_hda_codec_idt,snd_hda_intel
snd_hwdep 5412 1 snd_hda_codec
snd_pcm_oss 35308 0
snd_mixer_oss 13746 1 snd_pcm_oss
fbcon 35102 71
tileblit 2031 1 fbcon
font 7557 1 fbcon
bitblit 4707 1 fbcon
softcursor 1189 1 bitblit
snd_pcm 70662 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
vga16fb 11385 0
vgastate 8961 1 vga16fb
snd_seq_dummy 1338 0
snd_seq_oss 26726 0
snd_seq_midi 4557 0
snd_rawmidi 19056 1 snd_seq_midi
snd_seq_midi_event 6003 2 snd_seq_oss,snd_seq_midi
snd_seq 47263 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
snd_timer 19098 2 snd_pcm,snd_seq
snd_seq_device 5700 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
i915 282354 3
drm_kms_helper 29297 1 i915
snd 54148 16 snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_ hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_os s,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
lp 7028 0
dell_wmi 1793 0
drm 162471 4 i915,drm_kms_helper
dcdbas 5422 0
psmouse 63245 0
serio_raw 3978 0
joydev 8708 0
parport 32635 2 ppdev,lp
soundcore 6620 1 snd
intel_agp 24177 2 i915
agpgart 31724 2 drm,intel_agp
i2c_algo_bit 5028 1 i915
video 17375 1 i915
output 1871 1 video
snd_page_alloc 7076 2 snd_hda_intel,snd_pcm
usbhid 36110 0
hid 67032 1 usbhid
usb_storage 39425 1
e100 28211 0
mii 4381 1 e100

Conexant chipset modems section
--------------------------------
Vendors 14f1 is Conexant, inheritor of the former vendor 127a Rockwell modem technology. Several other modem assemblers use Conexant chips too.
There are also Conexant chipsets in some modems assembled by other vendors.
Jonathan <modem.support@linuxant.com> provides support for Conexant chipset modems.

Support types are:
hcfpcimodem package - for older HCF chipset modems
hsfmodem package - for hsfmodem chipsets, including those hosted on some USB modems,
dgcmodem package - UBS modems with Digital Call Progress software interface.
Try the hsfmodem package in case of problems.

For the modems hosted on High Definition Audio (HDA) cards, there is dependence upon the snd-hda-intel ALSA driver already on your System. In sound support is broken by installation of the hsfmodem drivers, follow the guidance on http://www.linuxant.com/alsa-driver/
Should you upgrade ALSA beyond the version used in the Linuxant driver code, the hsfmodem drivers may fail.

For users who want to upgrade their kernels regularly, there can be used a generic package for the drivers.
These generic packages require more support installed on the host system: the gcc C compiler and the kernel
headers. However they will survive minor kernel upgrades, the new modules needed will be automatically
recompiled when a new kernel is booted. These generic packages can be downloaded at:
HSF: http://www.linuxant.com/drivers/hsf/full/downloads.php#generic
HCF: http://www.linuxant.com/drivers/hcf/full/downloads.php#generic

The 14f1:2f00 chipset has a free support package: http://ubuntuforums.org/showthread.php?t=180632

Dell is providing hsfmodem package for its PCs: http://linux.dell.com/files/ubuntu/modem-drivers/ .
with the folder http://linux.dell.com/files/ubuntu/modem-drivers/hsf-custom/
having the version 7.68 needed for your ALSA version 1.0.4
hsfmodem-7.68.00.06tst1oem-1.i386.rpm 18-Jan-2008 16:24 1.4M
hsfmodem-7.68.00.06tst1oem.tar.gz 18-Jan-2008 16:24 1.4M
hsfmodem_7.68.00.06tst1oem-1_i386.deb 18-Jan-2008 16:24 1.3M

But the orginal source of the hsfmodem Linux code packages for
Conexant chipset modems is http://www.linuxant.com/drivers.
There are free test packages available there providing only a low 14K speed.
A software key must be purchased to enable full speed 56K service.
The HCF chipset modems have a dsp
(digital signal processing) chip, while the HSF lack a dsp and
this function is performed by the CPU under software direction.

For a crash issue with the 2.6.16 kernel, please make sure that your
kernel was not compiled with the CONFIG_4KSTACKS option is not set as
the HSF modem driver is known to requires more than 4K of stacks in a
few cases. The are several alternate kernels supporting hsfmodem
available at http://www.linuxant.com. Look for their Link/URL on the
page with your needed hsfmodem package.

To get software, go to http://www.linuxant.com/drivers
-Find the HCF or HSF menu in the left part of the screen.
-Read README.
-Read INSTALLATION: http://www.linuxant.com/drivers/hsf/install.php
-Click DOWNLOAD.
-Accept conditions.
-Find text: You can download HCF or HSF modem packages from the driver
download page. and click there.
-Look for your distribution, your processor, and your kernel.
-Download the matching file.
-Read again and, if you do this under Windows, print the installation
instructions matching the kind of driver file which you downloaded.
-Now just follow these instructions.

http://www.linuxant.com/drivers/hsf/downloads-patches.php has patches
that may be necessary for recent kernels.

A detailed software installation example is provided at:
http://linmodems.technion.ac.il/archive-fourth/msg00350.html

After loading of HSF drivers, there will be selective displayed by command:
# /sbin/lsmod | grep hsf
with an output like:
-----------
Module Size Used by Tainted:
hsfich 119116 0 (autoclean)
hsfserial 26388 0 (autoclean)
hsfengine 1126348 0 (autoclean) [hsfserial]
hsfosspec 35328 0 (autoclean) [hsfich hsfserial hsfengine]
---------
plus many others not modem related.
While drivers are pre-compiled for some Linux distributions,
the installation of the HCF/HSF packages DOES in general require kernel-source/
preparation, as described in Modem/DOCs/DriverCompiling.txt.

There is good support from Linuxant.com, but first gather data.
In a terminal
# su - root or prefix commands with sudo for Ubuntu related distributions.
hsfconfig --dumpdiag
If this command crashes your machine, please try instead:
hsfconfig --dumpdiag --noprobe
Send the hsfdiag.txt located in the folder /tmp/
to MODEM.SUPPORT@linuxant.com

There is a conflict between modules snd-intel8x0m and hsfmc97ich.
The snd-intel8x0m Must be loaded first or the system may hang upon hsfmc97ich insertion.
http://linmodems.technion.ac.il/archive-fourth/msg03027.html

http://www.lorenzobettini.it/linux/LinuxSonyVaioVGN-S5VP_B reports a
problem and solution in stalling a key, after testing of the free low
speed test package.

From http://www.linuxant.com/drivers,
get package(s) with 2.6.32_21_generic included in the filename.
If such a package cannot be found, get the generic package,
for which compiling drivers will be necessary.

Copy the package to your Linux partition. Unpack with:
unzip *.zip
Under root/admin permission, install with package with
sudo dpkg -i *.deb
Should the modem hardware not be a Conexant type,
the installation will ABORT with an informative message.

Continue with any output instructions. Following a successfull installation,
The modem should be detected during the root/admin command:
wvdialconf /etc/wvdial.conf
Edit your personal information in with:
$ sudo gedit /etc/wvdial.conf
See details on dialout usage in DOCs/Testing.txt

====== end Conexant section section =======

================================================== =====
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.32-21-generic.
Modules located in subfolders of /lib/modules/2.6.32-21-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.32-21-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.32-21-generic or /usr/src/linux-2.6.32-21-generic
Debian and distros using its Package.deb format have names:
kernel-headers-2.6.32-21-generic
linux-headers-2.6.32-21-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.32-21-generic or linux-source-2.6.32-21-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.32-21-generic.deb package matching your kernel version 2.6.32-21-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.32-21-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.32-21-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.32-21-generic/build
cd /usr/src/linux

There is a Makefile on your System at: /lib/modules/2.6.32-21-generic/build/Makefile
with first few lines:

VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 32
EXTRAVERSION = .11+drm33.2
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.32-21-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.32-21-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.32-21-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.32-21-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

Do NOT send this text with common information to discuss@linmodems.org
There are instructions to UNSUBSCRIBE from discuss@linmodems.org 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 2010_04_29
-------------------------------------
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

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@gmail.com

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 =======

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 ./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@linmodems.org
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 ./scanModem after login to a console with
# su - root
as Root permission may be necessary for access to lspci.

Updated on 2010_04_29 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!!

pnt101

May 14th, 2010, 03:29 AM

continue....

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@linmodems.org.
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 " " "

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.32-21-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@linmodems.org 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@linmodems.org
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 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

This file should NOT be sent to Discuss@Linmodems.org
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:13:72:c9:99:99
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
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:72 errors:0 dropped:0 overruns:0 frame:0
TX packets:72 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5600 (5.6 KB) TX bytes:5600 (5.6 KB)

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/

pnt101

May 15th, 2010, 03:39 AM

any help?

Ebere

May 15th, 2010, 06:25 AM

any help?

Did you just download your entire hard drive to this thread ???

;)

pnt101

May 15th, 2010, 06:10 PM

lol no if i would the forum wouldnt be able to support the data lol. Thats just what i got from the text files.

pnt101

May 15th, 2010, 09:51 PM

anyone?

pnt101

May 16th, 2010, 03:43 AM

again anyone?

Ebere

May 16th, 2010, 03:55 AM

again anyone?

I wish I could help.

I have no idea what the solution is.

I have an external dialup modem, and Ubuntu, Kubuntu, and Mint have all found and utilized the modem, immediately. (Once GNOME PPP was installed.)

foresthill

May 16th, 2010, 03:57 AM

The solution is:

Find an external modem and use that.

pnt101

May 16th, 2010, 06:31 AM

reccomend a external modem?

R3VAMP3D

May 16th, 2010, 07:07 AM

Ebere

May 16th, 2010, 07:20 AM

reccomend a external modem?

Mine is a "ModemSURFR".

It's close to 15 years old.

I am sure there are new ones that are much better.

Try searching external modem at ebay.

Ebere

May 16th, 2010, 07:26 AM

Don't know any off the back of my hand, but what internet provider do you use for dial-up? Majority of dial up ISP's want you to use their own crappy software to dial out and getting the information to dial out with third party programs is usually a pain, or impossible.

They may -want- you to. But if you have the phone number, your username, and your password... on the majority of them you can simply set GNOME PPP to dial it and connect.

My dialup ISP -wants- me to use their software. They claim I can't make a connection without doing so.

But I have done a simple dialup connection for 10 years through windows 95, then 98 then XP. And now through Ubuntu, Kubuntu, and Mint.

It's not rocket surgery.

pnt101

May 16th, 2010, 09:36 PM

the problem is not working with the ISP, its that gnome ppp cant detect me modem

Lafon

May 17th, 2010, 10:30 PM

Ok softModems are NOT supported in Ubuntu 9.04 and later releases. So it's easier to buy a external modem.
BTW did any get wvdial to work from the boot cd?

lkraemer

May 18th, 2010, 02:10 AM

This statement isn't true:
Ok softModems are NOT supported in Ubuntu 9.04 and later releases. So it's easier to buy a external modem.

www.linmodems.org is a good place to start for support for the Winmodems.
Marvin and the folks there will assist you with your request. Just be sure
your email is set for PLAIN TEXT, or it will be rejected.

Give Marvin and those folks a chance to help, but it will be a several day
ordeal, not a five minute fix.

And the External Serial Hardware modem is a much quicker solution.

lk

Lafon

May 18th, 2010, 02:36 PM

Sorry wrong choice of words. What I meant was that you can't find PRECOMPILED drivers for softModems on Ubuntu LUCID LYNX. Precompiled drivers exist only up to 8.10. lkraemer is right but it's easier to buy an external modem (Just make sure you look at the price. A store in my area is selling one for $99.92 which is ridiculous.:0)

This statement isn't true:
Ok softModems are NOT supported in Ubuntu 9.04 and later releases. So it's easier to buy a external modem.

www.linmodems.org is a good place to start for support for the Winmodems.
Marvin and the folks there will assist you with your request. Just be sure
your email is set for PLAIN TEXT, or it will be rejected.

Give Marvin and those folks a chance to help, but it will be a several day
ordeal, not a five minute fix.

And the External Serial Hardware modem is a much quicker solution.

lk

Lafon

June 18th, 2010, 03:12 AM

Ok i solved the problem. :-)
I'll post again soon with the answer. (Ihave ANOTHER problem with my computer!!!)

Lafon

June 19th, 2010, 09:18 PM

Ok here's how to install and use a CONEXANT modem. First download the diaco hsfmodem package from http://ubuntuforums.org/showthread.php?t=1308328 then put it on your desktop.
Next in a terminal write

cd Desktop/(name of downloaded file here)
Then
sudo ./configure
then
sudo make install
And your conexant modem should now work in lucid lynx.
Lafon

alexfish

June 19th, 2010, 09:48 PM

Hi all

for info

https://help.ubuntu.com/community/DialupModemHowto

regards

alexfish

greenawaltsscrap

August 6th, 2010, 03:59 AM

Newbie, trying to use a Motorola Tundra va76r as a dial up modem. Can anyone point me to a good howto for setting it up?
Thanks

TopEnder

August 6th, 2010, 04:29 AM

Newbie, trying to use a Motorola Tundra va76r as a dial up modem. Can anyone point me to a good howto for setting it up?
Thanks
Checkout previous posts to your's, and the link at post #50 should help you get connected.