Ryan, When you run scanModem you see in the bottom of the output stuff like: > Checking pppd properties: > -rwsr-xr-- 1 root dip 277352 2009-02-20 11:25 /usr/sbin/pppd > > In case of an "error 17" "serial loopback" problem, see: > http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html > > To enable dialout without Root permission do: > $ su - root (not for Ubuntu) > sudo chmod a+x /usr/sbin/pppd > or under Ubuntu related Linuxes > sudo chmod a+x /usr/sbin/pppd > > Checking settings of: /etc/ppp/options > asyncmap 0 > noauth > crtscts > lock > hide-password > modem > proxyarp > lcp-echo-interval 30 > lcp-echo-failure 4 > noipx > > In case of a message like: > Warning: Could not modify /etc/ppp/pap-secrets: Permission denied > see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html > > Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 usb0 > Which can interfere with Browser naviagation. > > Don't worry about the following, it is for experts should trouble shooting > be necessary. > ========================================================== > > Checking for modem support lines: > -------------------------------------- > /device/modem symbolic link: > slmodemd created symbolic link /dev/ttySL0: > Within /etc/udev/ files: > > Within /etc/modprobe.conf files: > /etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2 > /etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2 > /etc/modprobe.d/blacklist-modem.conf:# Uncomment these entries in order to > blacklist unwanted modem drivers > /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-atiixp-modem > /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-via82xx-modem > Within any ancient /etc/devfs files: > > Within ancient kernel 2.4.n /etc/module.conf files: > > --------- end modem support lines -------- When you send in ModemData.txt. Ryan since it is difficult to get something going, I will CC: Phillpe Vouters the maintainer of 536 and 537 modem drivers. I believe he can be of better help here. I will copy + paste part of original mail that was sent to list so that he can try to see how to fix this. From: Antonio Olivares <olivares14031@xxxxxxxxx> To: Ryan Mckeown <ryanmckeown@xxxxxxxxxxx> Cc: Discuss@xxxxxxxxxxxxx Sent: Sat, 13 Jun 2009 4:13 pm Subject: Re: Ryan Mckeown, Northern Ireland kernel 2.6.28-11-generic Ryan, sacanModem recommends http://linmodems.technion.ac.il/packages/intel/Philippe.Vouters/intel-5337EP_secure-2.60.80.0_2009_02_08.tar.bz2 but you tried other prebuilt drivers? but also scanModem detects an iterrupt problem: or candidate card in slot 01:01.0, firmware information and bootup diagnostics are: PCI slot PCI ID SubsystemID Name ---------- --------- --------- -------------- 01:01.0 8086:1080 1028:1000 Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI Modem interrupt assignment and sharing: --- Bootup diagnostics for card in PCI slot 01:01.0 ---- [ 0.678108] pci 0000:01:01.0: reg 10 32bit mmio: [0xfeafe000-0xfeafefff] [ 0.678115] pci 0000:01:01.0: reg 14 io port: [0xde00-0xdeff] [ 0.678152] pci 0000:01:01.0: PME# supported from D0 D3hot D3cold [ 0.678156] pci 0000:01:01.0: PME# disabled [ 1.979232] serial 0000:01:01.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 [ 1.979345] 0000:01:01.0: ttyS1 at I/O 0xde08 (irq = 22) is a 16450 [ 1.979420] 0000:01:01.0: ttyS2 at I/O 0xde10 (irq = 22) is a 8250 [ 1.979494] 0000:01:01.0: ttyS3 at I/O 0xde18 (irq = 22) is a 16450 [ 1.979519] Couldn't register serial port 0000:01:01.0: -28 The PCI slot 01:01.0 of the modem card may be disabled early in a bootup process, but then enabled later. If modem drivers load but the modem is not responsive, read DOCs/Bootup.txt about possible fixes. Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx if help is needed. I guess we need to deal with this first. There are reports though about modems with name FA82537EP 56K V.92 Data/Fax Modem PCI that don't work so of this I am not sure since scanModem recommends the driver from Phillipe Vouters? send us dmesg.txt and we'll saee how we can help. Regards, Antonio On 6/13/09, Ryan Mckeown <ryanmckeown@xxxxxxxxxxx> wrote: Hey. Ok so heres the problem I'm faced with: A few weeks ago I received the Ubuntu 9.04 (Jaunty Jackelope) CD and I installed it alongside my Windows XP OS on my Dell Dimension 3000. I think I'm right in saying that Ubuntu 9.04 has the kernal 2.6.28-11 (whether that's important or not is beyond me). Anyway I installed it with success and was quite happy until I decided to try to get online. I looked up the installed manual (System > Help and Support) and it said that "NetworkManager manages wired, wireless, mobile broadband, vpn and dsl connections. It does not currently support dialup modem connections but there is help available in Chapter 6 -- Modems". So I went to chapter 6.1 titled "Identifying your modem" and from the instructions there, I downloaded scanModem from http://linmodems.technion.ac.il/packages/scanModem.gz (under Windows XP) and followed the rest of the instructions to open "ModemData.txt". ModemData.txt is attached. I also went to the link at the bottom of the page (also under XP): https://help.ubuntu.com/community/DialupModemHowto and I found that installing a dial-up modem should be as simple as: 1. Identify the modem 2. Download a driver for your modem or buy a more suited modem 3. Configure the connection to your ISP Seemed straight forward enough. I already had identified my modem using scanModem and its a: Intel Corporation FA82 537EP 56k V.92 DATA/FAX MODEM found on the PCI. I also20know its in (windows settings) COM 3.20 So then I proceeded and clicked on the link "Setup Intel537EP driver" (https://help.ubuntu.com/community/DialupModemHowto/Intel537EP) and found that the driver was "pre-packaged" for new users (me!) into a .deb file. So I downloaded it and ran it with apparent success in Ubuntu. Therefore, I continued to the third stage, I downloaded gnome-ppp (I heard it was good from threads I read and I found a useful page: https://help.ubuntu.com/community/DialupModemHowto/SetUpDialer.htm which gave me instructions as to how to install and run gnome-ppp) along with the dependencies it needed and ran it. I added myself to the dip and dialout groups, configured gnome-ppp and tried to dial. However, when I click "dial" the message appears "Sending password" and it stays like that until the thing times out. I then decided to use wvdialconf to see if it detected my modem and it said it didn't. I've tried loads of things since then and got nowhere. I found out that my modem has a Ambient MD3200 chipset and that Intel's support for the driver has all but ran out. Intel is actually telling me to try to contact the manufacturer because apparently Intel never actually manufactured the product themselves, they just put their name on it. I also learnt that Intel was formerly Ambient which was formerly Cirrus Logic. Apparently too there was a driver released for Linux for my modem back in about 2002 but I can't seem to find it anywhere. My ISP is Tiscali and I know the phone number to dial, the username and I have a fair idea of what my password is to use. I also know that the DNS address is determined on connection and the ISP uses PPP transfer methods. I think that the driver I installed didn't work so can you please help me to find another? Also can you please explain everything in lots of detail because, even though I have some experience in programming under Windows, Linux is still very new to me and hardware wouldn't really be my strong point either. Thanks Ryan =========================================================================================== Sorry to bother you Phillipe, but I have run out of ideas to help Ryan get online. Regards, Antonio On Thu, Jun 18, 2009 at 11:22 AM, Ryan<ryanmckeown@xxxxxxxxxxx> wrote: > Antonio > > Where is the PAP/CHAP stuff from the scanModem output? > > What do you mean by what is required from your ISP? > > > I'm confused > Have you any ideas? > Ryan > > > ----- Original Message ----- From: "Antonio Olivares" > <olivares14031@xxxxxxxxx> > To: "Ryan" <ryanmckeown@xxxxxxxxxxx> > Sent: Thursday, June 18, 2009 4:02 PM > Subject: Re: Ryan Mckeown, Northern Ireland kernel 2.6.28-11-generic > > > Ryan, > > Then check with the PAP/Chap stuff from scanModem output. Also it > might be beneficial to find out what is required from your ISP and > that way we can figure out. > > Regards, > > Antonio > > On Thu, Jun 18, 2009 at 9:51 AM, Ryan<ryanmckeown@xxxxxxxxxxx> wrote: >> >> Antonio. >> >> The settings were as I assumed. My user name, password and number to dial >> are correct but I am still getting the following when I try to dial: >> >> ryan@Ryan:~$ sudo wvdial >> --> WvDial: Internet dialer version 1.55 >> --> Warning: inherited section [Modem0] does not exist in wvdial.conf >> --> Initializing modem. >> --> Sending: ATZ >> ATZ >> OK >> --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >> OK >> --> Modem initialized. >> --> Sending: ATDT08440575000 >> --> Waiting for carrier. >> ATDT08440575000 >> CONNECT 49333 >> User Access Verification >> login: >> --> Carrier detected. Waiting for prompt. >> --> Connected, but carrier signal lost! Retrying... >> --> Sending: ATDT08440575000 >> --> Waiting for carrier. >> login: >> login: >> login: >> login:ATDT08440575000 >> Password: >> % Password: timeout expired! >> % Authentication failed. >> login: >> % login: timeout expired! >> % Authentication failed. >> login: >> % login: timeout expired! >> % Authentication failed. >> >> As you can see, another loop, until I press Ctrl + C and then: >> >> ^CCaught signal 2: Attempting to exit gracefully... >> --> Disconnecting at Thu Jun 18 15:36:39 2009 >> ryan@Ryan:~$ >> >> Have you any more ideas? >> >> I have an idea. I was looking through the Windows setting for the >> connection >> and I found that the connection call a PPP server which is commun in >> Windows >> servers but SLIP is commun in Unix servers. Is that at all relevant? >> >> It also uses PAP metods of authentication, if thats relevant either. >> PPP multilink framing is off also. >> >> Can any of this help? >> >> >> Ryan >> >> ----- Original Message ----- From: "Antonio Olivares" >> <olivares14031@xxxxxxxxx> >> To: "Ryan" <ryanmckeown@xxxxxxxxxxx> >> Sent: Thursday, June 18, 2009 3:06 PM >> Subject: Re: Ryan Mckeown, Northern Ireland kernel 2.6.28-11-generic >> >> >> Anyway, is there any other way of extracting my password from the >> Windows settings? >> >> You can try selecting the password and cutting & pasting into an >> application like notepad/wordpad. ? >> >> Regards, >> >> Antonio >> >> On Thu, Jun 18, 2009 at 8:52 AM, Ryan<ryanmckeown@xxxxxxxxxxx> wrote: >>> >>> Antonio. >>> >>> Sorry I haven't got back to you in a while - I was checking with tiscali >>> that my password is what I think it is, but they are being very stubborn >>> and >>> refusing to give me my password over email and they are insisting that my >>> dad, who has his name on the account because he pays the bills (I'm only >>> 15), phone them up and talk to them. However, the number they gave me is >>> 5p >>> per minute on Tiscali Talk and goodness knows how much on BT (which we >>> use >>> for phone calls). Anyway, is there any other way of extracting my >>> password >>> from the Windows settings? >>> >>> >>> Ryan >>> ----- Original Message ----- From: "Antonio Olivares" >>> <olivares14031@xxxxxxxxx> >>> To: "Ryan" <ryanmckeown@xxxxxxxxxxx> >>> Sent: Wednesday, June 17, 2009 3:27 PM >>> Subject: Re: Ryan Mckeown, Northern Ireland kernel 2.6.28-11-generic >>> >>> >>> Ryan >>> >>> The following part which you sent : >>> >>> ryan@Ryan:~$ wvdial >>> >>> --> WvDial: Internet dialer version 1.55 >>> >>> --> Warning: inherited section [Modem0] does not exist in wvdial.conf >>> --> Initializing modem. >>> --> Sending: ATZ >>> ATZ >>> OK >>> --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >>> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >>> OK >>> --> Modem initialized. >>> --> Sending: ATDT08440575000 >>> --> Waiting for carrier. >>> ATDT08440575000 >>> >>> CONNECT 49333 >>> - Show quoted text - >>> >>> User Access Verification >>> login: >>> --> Carrier detected. Waiting for prompt. >>> --> Connected, but carrier signal lost! Retrying... >>> --> Sending: ATDT08440575000 >>> --> Waiting for carrier. >>> login: >>> login: >>> login: >>> login:ATDT08440575000 >>> Password: >>> % Password: timeout expired! >>> % Authentication failed. >>> login: >>> % login: timeout expired! >>> % Authentication failed. >>> login: >>> % login: timeout expired! >>> % Authentication failed. >>> NO CARRIER >>> --> No Carrier! Trying again. >>> --> Sending: ATDT08440575000 >>> --> Waiting for carrier. >>> ATDT08440575000 >>> CONNECT 50666 >>> User Access Verification >>> login: >>> --> Carrier detected. Waiting for prompt. >>> --> Connected, but carrier signal lost! Retrying... >>> --> Sending: ATDT08440575000 >>> --> Waiting for carrier. >>> login: >>> login: >>> login: >>> login:ATDT08440575000 >>> Password: >>> % Password: timeout expired! >>> % Authentication failed. >>> login: >>> % login: timeout expired! >>> % Authentication failed. >>> login: >>> % login: timeout expired! >>> % Authentication failed. >>> NO CARRIER >>> --> No Carrier! Trying again. >>> >>> --> Sending: ATDT08440575000 >>> --> Waiting for carrier. >>> ATDT08440575000 >>> >>> CONNECT 49333 >>> >>> User Access Verification >>> login: >>> --> Carrier detected. Waiting for prompt. >>> --> Connected, but carrier signal lost! Retrying... >>> --> Sending: ATDT08440575000 >>> --> Waiting for carrier. >>> login: >>> login: >>> login: >>> login:ATDT08440575000 >>> Password: >>> % Password: timeout expired! >>> % Authentication failed. >>> >>> login:^CCaught signal 2: Attempting to exit gracefully... >>> >>> --> Disconnecting at Wed Jun 17 00:46:16 2009 >>> ryan@Ryan:~$ >>> >>> Shows that wvdial connected. But Authentication failed. This could >>> imply that the password you put in /etc/wvdial.conf might be >>> incorrect. Check that the password is the same. The connection is >>> succeeding. All should be well. You are indeed very close. It is a >>> matter of checking that part of wvdial.conf. Also once you make sure >>> that the file is correct, and you can connect, you see the following: >>> >>> ATDT08440575000 >>> >>> CONNECT 49333 >>> >>> That means that you are connected but you can't browse, hope you can >>> see some numbers in the bottom which are the nameservers. >>> >>> Check that out and report back. >>> >>> Regards, >>> >>> Antonio >>> >>> On Tue, Jun 16, 2009 at 6:57 PM, Ryan<ryanmckeown@xxxxxxxxxxx> wrote: >>>> >>>> Antonio. >>>> >>>> I have 3 dialers: wvdial, gnome-ppp (which is a frontend for wvdial) and >>>> pppconfig. I read somewhere that KPPP was for Kubuntu but I have Ubuntu. >>>> Anyway, I've tried to connect with all 3 of them and none have worked. >>>> >>>> As for your other idea, I opened 2 terminal tabs and tried to dial >>>> (using >>>> $ >>>> wvdial) on the first with the following appearing: >>>> >>>> ryan@Ryan:~$ wvdial >>>> --> WvDial: Internet dialer version 1.55 >>>> --> Warning: inherited section [Modem0] does not exist in wvdial.conf >>>> --> Initializing modem. >>>> --> Sending: ATZ >>>> ATZ >>>> OK >>>> --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >>>> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >>>> OK >>>> --> Modem initialized. >>>> --> Sending: ATDT08440575000 >>>> --> Waiting for carrier. >>>> ATDT08440575000 >>>> CONNECT 49333 >>>> User Access Verification >>>> login: >>>> --> Carrier detected. Waiting for prompt. >>>> --> Connected, but carrier signal lost! Retrying... >>>> --> Sending: ATDT08440575000 >>>> --> Waiting for carrier. >>>> login: >>>> login: >>>> login: >>>> login:ATDT08440575000 >>>> Password: >>>> % Password: timeout expired! >>>> % Authentication failed. >>>> login: >>>> % login: timeout expired! >>>> % Authentication failed. >>>> login: >>>> % login: timeout expired! >>>> % Authentication failed. >>>> NO CARRIER >>>> --> No Carrier! Trying again. >>>> --> Sending: ATDT08440575000 >>>> --> Waiting for carrier. >>>> ATDT08440575000 >>>> CONNECT 50666 >>>> User Access Verification >>>> login: >>>> --> Carrier detected. Waiting for prompt. >>>> --> Connected, but carrier signal lost! Retrying... >>>> --> Sending: ATDT08440575000 >>>> --> Waiting for carrier. >>>> login: >>>> login: >>>> login: >>>> login:ATDT08440575000 >>>> Password: >>>> % Password: timeout expired! >>>> % Authentication failed. >>>> login: >>>> % login: timeout expired! >>>> % Authentication failed. >>>> login: >>>> % login: timeout expired! >>>> % Authentication failed. >>>> NO CARRIER >>>> --> No Carrier! Trying again. >>>> --> Sending: ATDT08440575000 >>>> --> Waiting for carrier. >>>> ATDT08440575000 >>>> CONNECT 49333 >>>> User Access Verification >>>> login: >>>> --> Carrier detected. Waiting for prompt. >>>> --> Connected, but carrier signal lost! Retrying... >>>> --> Sending: ATDT08440575000 >>>> --> Waiting for carrier. >>>> login: >>>> login: >>>> login: >>>> login:ATDT08440575000 >>>> Password: >>>> % Password: timeout expired! >>>> % Authentication failed. >>>> login:^CCaught signal 2: Attempting to exit gracefully... >>>> >>>> --> Disconnecting at Wed Jun 17 00:46:16 2009 >>>> ryan@Ryan:~$ >>>> >>>> As you can see, the program went into a continuous loop, until I >>>> disconnected. >>>> And on the second tab here is exactly what the terminal looks like: >>>> >>>> ryan@Ryan:~$ sudo lsmod | grep intel53* >>>> [sudo] password for ryan: >>>> ryan@Ryan:~$ tail -f /var/log/messages >>>> Jun 17 00:40:51 Ryan kernel: [ 589.456912] [<c0180475>] >>>> handle_fasteoi_irq+0x65/0xd0 >>>> Jun 17 00:40:51 Ryan kernel: [ 589.456917] [<c015b7e7>] ? >>>> tick_check_idle+0x17/0x30 >>>> Jun 17 00:40:51 Ryan kernel: [ 589.456922] [<c010684e>] do_IRQ+0x7e/0xa0 >>>> Jun 17 00:40:51 Ryan kernel: [ 589.456926] [<c01817e7>] ? >>>> rcu_needs_cpu+0x37/0x50 >>>> Jun 17 00:40:51 Ryan kernel: [ 589.456929] [<c050104a>] ? >>>> schedule+0x41a/0x710 >>>> Jun 17 00:40:51 Ryan kernel: [ 589.456932] [<c01051f3>] >>>> common_interrupt+0x23/0x30 >>>> Jun 17 00:40:51 Ryan kernel: [ 589.456936] [<c010b012>] ? >>>> mwait_idle+0x42/0x50 >>>> Jun 17 00:40:51 Ryan kernel: [ 589.456939] [<c010285d>] >>>> cpu_idle+0x6d/0xd0 >>>> Jun 17 00:40:51 Ryan kernel: [ 589.456991] [<c04f110e>] >>>> rest_init+0x4e/0x60 >>>> Jun 17 00:40:51 Ryan kernel: [ 589.456995] ---[ end trace >>>> 06f06adfa78d443b >>>> ]--- >>>> >>>> >>>> Any ideas? >>>> Ryan >>>> >>>> >>>> >>>> ----- Original Message ----- From: "Antonio Olivares" >>>> <olivares14031@xxxxxxxxx> >>>> To: "Ryan" <ryanmckeown@xxxxxxxxxxx> >>>> Sent: Tuesday, June 16, 2009 9:28 PM >>>> Subject: Re: Ryan Mckeown, Northern Ireland kernel 2.6.28-11-generic >>>> >>>> >>>>> Ryan, >>>>> >>>>> I am thinking about this. I don't know how to advise. I have an >>>>> intel 536 modem and I made a slax module to use while using Slax live >>>>> cd. But your modem is 537 which is a bit different. I had working >>>>> instructions for intel 536. I tried wvdialconf with it and I got same >>>>> message that no modem was found. However, since Slax comes with KPPP >>>>> I just put in username, password and phone no. The modem link was >>>>> /dev/modem ---> /dev/536 and the modem responded and connected. But >>>>> it took a little while. >>>>> >>>>> If you have other dialer like KPPP available, you may go ahead and try >>>>> it. Modem takes a while to respond. Otherwise if you can and if you >>>>> don't mind. Try to save the following: >>>>> >>>>> Open two terminals or terminal tabs on one you try the connection and >>>>> copy + paste the details and on the other one, you may post output of >>>>> $ sudo lsmod | grep intel53* >>>>> and immediately following that >>>>> $ tail -f /var/log/messages >>>>> >>>>> when you are trying to connect with wvdial or kppp? >>>>> $ wvdail >>>>> >>>>> Other than that we should submit the problems encountered here to list >>>>> and hope that they(other users) could provide advise so that you can >>>>> get your modem working. >>>>> >>>>> Regards, >>>>> >>>>> Antonio >>>>> >>>>> On 6/15/09, Ryan <ryanmckeown@xxxxxxxxxxx> wrote: >>>>>> >>>>>> Antonio, I haven't heard from you in a while. Don't worry about it, >>>>>> I'm >>>>>> sure >>>>>> you have a reason for it but I'm just checking that you received my >>>>>> email >>>>>> ok. On it I wrote: >>>>>> >>>>>> Yea I did change my ISP, username and password to the correct values >>>>>> and >>>>>> what happened was as I described below. >>>>>> >>>>>> >>>>>> Ryan >>>>>> >>>>>> ----- Original Message ----- >>>>>> From: "Antonio Olivares" <olivares14031@xxxxxxxxx> >>>>>> To: "Ryan" <ryanmckeown@xxxxxxxxxxx> >>>>>> Sent: Monday, June 15, 2009 9:29 PM >>>>>> Subject: Re: Ryan Mckeown, Northern Ireland kernel 2.6.28-11-generic >>>>>> >>>>>> >>>>>> BTW, >>>>>> >>>>>> Sorry I got out of focus. I was watching the Confederations Cup in >>>>>> South Africa and USA was beating Italy 1 to 0, but Italy came back to >>>>>> win 3 - 1. >>>>>> >>>>>> Regards, >>>>>> >>>>>> Antonio >>>>>> >>>>>> On Mon, Jun 15, 2009 at 3:27 PM, Antonio >>>>>> Olivares<olivares14031@xxxxxxxxx> wrote: >>>>>>> >>>>>>> Ryan, >>>>>>> >>>>>>> Please change/modify username, phone, and password add the ones that >>>>>>> you need for your ISP, then try to connect again. >>>>>>> >>>>>>> Instead of >>>>>>> >>>>>>> Username = PUT_YOUR_USERNAME_HERE >>>>>>> Password = PUT_your ISP provided password >>>>>>> Phone = PUT_your ISP phone number >>>>>>> >>>>>>> Then try to dial out again. >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Antonio >>>>>>> >>>>>>> On Mon, Jun 15, 2009 at 11:30 AM, Ryan<ryanmckeown@xxxxxxxxxxx> >>>>>>> wrote: >>>>>>>> >>>>>>>> Antonio. >>>>>>>> >>>>>>>> Nope. >>>>>>>> Ok, copied and pasted the /etc/wvdial.conf file (I had to use the >>>>>>>> command: $ >>>>>>>> sudo nano /etc/wvdial.conf to modify it.) >>>>>>>> When I tried to connect, this appeared: >>>>>>>> --> WvDial: Internet dialer version 1.55 >>>>>>>> --> Warning: section [Dialer /etc/wvdial.conf] does not exist in >>>>>>>> wvdial.conf. >>>>>>>> --> Warning: inherited section [Modem0] does not exist in >>>>>>>> wvdial.conf >>>>>>>> --> Initializing modem. >>>>>>>> --> Sending: ATZ >>>>>>>> ATZ >>>>>>>> OK >>>>>>>> --> Modem initialized. >>>>>>>> --> Configuration does not specify a valid phone number. >>>>>>>> --> Configuration does not specify a valid login name. >>>>>>>> --> Configuration does not specify a valid password. >>>>>>>> >>>>>>>> So I changed the line >>>>>>>> [Dialer tiscali] >>>>>>>> to >>>>>>>> [Dialer Defaults] >>>>>>>> and tried to connect again, with the following appearing: >>>>>>>> --> WvDial: Internet dialer version 1.55 >>>>>>>> --> Warning: section [Dialer /etc/wvdial.conf] does not exist in >>>>>>>> wvdial.conf. >>>>>>>> --> Warning: inherited section [Modem0] does not exist in >>>>>>>> wvdial.conf >>>>>>>> --> Initializing modem. >>>>>>>> --> Sending: ATZ >>>>>>>> ATZ >>>>>>>> OK >>>>>>>> --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >>>>>>>> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >>>>>>>> OK >>>>>>>> --> Modem initialized. >>>>>>>> --> Sending: ATDT08440575000 >>>>>>>> --> Waiting for carrier. >>>>>>>> ATDT08440575000 >>>>>>>> --> Timed out while dialing. Trying again. >>>>>>>> --> Sending: ATDT08440575000 >>>>>>>> --> Waiting for carrier. >>>>>>>> NO CARRIER >>>>>>>> ATDT08440575000 >>>>>>>> --> No Carrier! Trying again. >>>>>>>> --> Sending: ATDT08440575000 >>>>>>>> --> Waiting for carrier. >>>>>>>> NO CARRIER >>>>>>>> ATDT08440575000 >>>>>>>> --> No Carrier! Trying again. >>>>>>>> --> Sending: ATDT08440575000 >>>>>>>> --> Waiting for carrier. >>>>>>>> NO CARRIER >>>>>>>> >>>>>>>> ... and on >>>>>>>> ... and on >>>>>>>> ... like that until I press Ctrl + C to disconnect. >>>>>>>> >>>>>>>> >>>>>>>> Also, when I run: >>>>>>>> $ sudo ifconfig -a >>>>>>>> the following appears: >>>>>>>> eth0 Link encap:Ethernet HWaddr 00:11:11:a0:f2:56 >>>>>>>> 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:4 errors:0 dropped:0 overruns:0 frame:0 >>>>>>>> TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 >>>>>>>> collisions:0 txqueuelen:0 >>>>>>>> RX bytes:240 (240.0 B) TX bytes:240 (240.0 B) >>>>>>>> >>>>>>>> pan0 Link encap:Ethernet HWaddr de:99:94:a0:30:de >>>>>>>> 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:0 >>>>>>>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) >>>>>>>> >>>>>>>> >>>>>>>> This does seem very strange. >>>>>>>> Can you help any further? >>>>>>>> Even cheating doesn't seem to be working. >>>>>>>> >>>>>>>> Ryan >>>>>>>> >>>>>>>> >>>>>>>> ----- Original Message ----- From: "Antonio Olivares" >>>>>>>> <olivares14031@xxxxxxxxx> >>>>>>>> To: "Ryan Mckeown" <ryanmckeown@xxxxxxxxxxx> >>>>>>>> Sent: Monday, June 15, 2009 12:50 PM >>>>>>>> Subject: Re: Ryan Mckeown, Northern Ireland kernel 2.6.28-11-generic >>>>>>>> >>>>>>>> >>>>>>>> Ryan, >>>>>>>> >>>>>>>> This is strange. Can you try to cheat a little bit. How, >>>>>>>> >>>>>>>> Copy the following by cutting and pasting to a file on your >>>>>>>> computer: >>>>>>>> >>>>>>>> Modem = /dev/modem >>>>>>>> Baud = 115200 >>>>>>>> SetVolume = 3 >>>>>>>> Dial Command = ATDT >>>>>>>> Init1 = ATZ >>>>>>>> Init2 = AT+GCI=3D >>>>>>>> Init3 = ATM1L3 >>>>>>>> Carrier Check = no >>>>>>>> FlowControl = CRTSCTS >>>>>>>> #Stupid Mode = yes >>>>>>>> [Dialer tiscali] >>>>>>>> Username = <your ISP provided user name> >>>>>>>> Password = <your ISP provided password> >>>>>>>> Phone = <your ISP phone number> >>>>>>>> Init1 = ATZ >>>>>>>> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >>>>>>>> Inherits = Modem0 >>>>>>>> >>>>>>>> tiscali is my Internet provider. You may replace the string [Dialer >>>>>>>> tiscali] >>>>>>>> by >>>>>>>> [Dialer <your provider name>]. >>>>>>>> >>>>>>>> >>>>>>>> Save it as /etc/wvdial.conf >>>>>>>> >>>>>>>> Replace tiscali with your own ISP and also add your Username, >>>>>>>> Password >>>>>>>> Phone, etc. Try to dialout. It should try to connect. Sometimes >>>>>>>> this happens to me, and I save the working wvdial.conf to a usb >>>>>>>> drive, >>>>>>>> I cut and paste it and everything works again. This sample >>>>>>>> wvdial.conf comes from >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> http://linmodems.technion.ac.il/packages/intel/Philippe.Vouters/Intel-Readme.txt >>>>>>>> >>>>>>>> Report back presently hopefully with a successfull connection. >>>>>>>> >>>>>>>> BTW, >>>>>>>> Should you be able to connect, but you try to browse and nothing >>>>>>>> happens. Please do the following: >>>>>>>> $ sudo cp /etc/pppd/resolv.conf /etc/resolv.conf >>>>>>>> >>>>>>>> and you should happily browse now. Also it would help if no network >>>>>>>> stuff is active by checking >>>>>>>> >>>>>>>> $ sudo ifconfig -a >>>>>>>> >>>>>>>> Regards, >>>>>>>> >>>>>>>> Antonio >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Jun 15, 2009 at 6:35 AM, Ryan >>>>>>>> Mckeown<ryanmckeown@xxxxxxxxxxx> >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Antonio, >>>>>>>>> >>>>>>>>> After running: >>>>>>>>> $ sudo lsmod >>>>>>>>> I can see this at the very first line: >>>>>>>>> Module Size Used by >>>>>>>>> Intel537 4324708 0 >>>>>>>>> >>>>>>>>> When I run: >>>>>>>>> $ sudo wvdial /etc/wvdial.conf >>>>>>>>> The following appears: >>>>>>>>> --> WvDial: Internet dialer version 1.55 >>>>>>>>> --> Warning: section [Dialer /etc/wvdial.conf] does not exist in >>>>>>>>> wvdial.conf. >>>>>>>>> --> Initializing modem. >>>>>>>>> --> Sending: ATZ >>>>>>>>> ATZ >>>>>>>>> OK >>>>>>>>> --> Modem initialized. >>>>>>>>> --> Sending: ATDT08440575000 >>>>>>>>> --> Waiting for carrier. >>>>>>>>> ATDT08440575000 >>>>>>>>> CONNECT 50666 >>>>>>>>> User Access Verification >>>>>>>>> login: >>>>>>>>> --> Carrier detected. Waiting for prompt. >>>>>>>>> --> Connected, but carrier signal lost! Retrying... >>>>>>>>> --> Sending: ATDT08440575000 >>>>>>>>> --> Waiting for carrier. >>>>>>>>> login: >>>>>>>>> login: >>>>>>>>> login: >>>>>>>>> login:ATDT08440575000 >>>>>>>>> Password: >>>>>>>>> % Password: timeout expired! >>>>>>>>> % Authentication failed. >>>>>>>>> login: >>>>>>>>> % login: timeout expired! >>>>>>>>> % Authentication failed. >>>>>>>>> login: >>>>>>>>> % login: timeout expired! >>>>>>>>> % Authentication failed. >>>>>>>>> NO CARRIER >>>>>>>>> --> No Carrier! Trying again. >>>>>>>>> --> Maximum Attempts Exceeded..Aborting!! >>>>>>>>> --> Disconnecting at Mon Jun 15 12:18:58 2009 >>>>>>>>> >>>>>>>>> Also if I try: >>>>>>>>> $ sudo wvdialconf /etc/wvdial.conf >>>>>>>>> The following still appears: >>>>>>>>> Editing `/etc/wvdial.conf'. >>>>>>>>> >>>>>>>>> Scanning your serial ports for a modem. >>>>>>>>> >>>>>>>>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud >>>>>>>>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 >>>>>>>>> baud >>>>>>>>> ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>>>>>>>> ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud >>>>>>>>> ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 >>>>>>>>> baud >>>>>>>>> ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>>>>>>>> ttyS2<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud >>>>>>>>> ttyS2<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 >>>>>>>>> baud >>>>>>>>> ttyS2<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>>>>>>>> ttyS3<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud >>>>>>>>> ttyS3<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 >>>>>>>>> baud >>>>>>>>> ttyS3<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>>>>>>>> >>>>>>>>> Sorry, no modem was detected! Is it in use by another program? >>>>>>>>> Did you configure it properly with setserial? >>>>>>>>> Please read the FAQ at http://open.nit.ca/wiki/?WvDial >>>>>>>>> >>>>>>>>> If you still have problems, send mail to >>>>>>>>> <wvdial-list@xxxxxxxxxxxx>. >>>>>>>>> >>>>>>>>> If I try: >>>>>>>>> $ ls -l /dev/modem >>>>>>>>> The following appears: >>>>>>>>> lrwxrwxrwx 1 root root 8 2009-06-15 12:10 /dev/modem -> /dev/537 >>>>>>>>> >>>>>>>>> And if I try: >>>>>>>>> $ ls -l /dev/537* >>>>>>>>> The following appears: >>>>>>>>> crw-rw-rw- 1 root dialout 240, 1 2009-06-15 12:18 /dev/537 >>>>>>>>> crw-rw---- 1 root root 240, 1 2009-06-15 12:10 /dev/5370 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Thanks for your help so far. >>>>>>>>> Can you help me further? >>>>>>>>> Ryan >>>>>>>>> >>>>>>>>> >>>>>>>>> -----Original Message----- >>>>>>>>> From: Antonio Olivares <olivares14031@xxxxxxxxx> >>>>>>>>> To: Ryan Mckeown <ryanmckeown@xxxxxxxxxxx> >>>>>>>>> Sent: Sun, 14 Jun 2009 8:24 pm >>>>>>>>> Subject: Re: Ryan Mckeown, Northern Ireland kernel >>>>>>>>> 2.6.28-11-generic >>>>>>>>> >>>>>>>>> Ryan, >>>>>>>>> >>>>>>>>> $ sudo modprobe Intel537 >>>>>>>>> returns nothing. >>>>>>>>> >>>>>>>>> it should not return anything, however if you do an >>>>>>>>> >>>>>>>>> $ sudo lsmod >>>>>>>>> >>>>>>>>> it should be there. >>>>>>>>> >>>>>>>>> After running above command, the modem should be detected >>>>>>>>> >>>>>>>>> $ sudo wvdial /etc/wvdial.conf >>>>>>>>> >>>>>>>>> If it is not and >>>>>>>>> $ ls -l /dev/modem >>>>>>>>> or >>>>>>>>> $ ls -l /dev/537* >>>>>>>>> >>>>>>>>> have the appropriate or corresponding entries it should work. >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> >>>>>>>>> Antonio >>>>>>>>> >>>>>>>>> On 6/14/09, Ryan Mckeown <ryanmckeown@xxxxxxxxxxx> wrote: >>>>>>>>>> >>>>>>>>>> Antonio. >>>>>>>>>> >>>>>>>>>> $ dmesg >>>>>>>>>> returns a whole lot of data, with the last 3 lines being: >>>>>>>>>> [ 18.874307] sound disabled >>>>>>>>>> [ 18.874325] Intel 537EP card found >>>>>>>>>> [ 20.929942] ADDRCONF(NETDEV_UP): eth0: link is not ready >>>>>>>>>> >>>>>>>>>> $ ls -l /dev/modem >>>>>>>>>> returns: >>>>>>>>>> lrwxrwxrwx 1 root root 8 2009-06-14 19:54 /dev/modem -> /dev/537 >>>>>>>>>> >>>>>>>>>> $ ls -l /dev/536* >>>>>>>>>> returns: >>>>>>>>>> ls: cannot access /dev/536*: No such file or directory >>>>>>>>>> >>>>>>>>>> however what I think you meant: >>>>>>>>>> $ ls -l /dev/537* >>>>>>>>>> returns: >>>>>>>>>> crw-rw-rw- 1 root dialout 240, 1 2009-06-14 19:54 /dev/537 >>>>>>>>>> crw-rw---- 1 root root 240, 1 2009-06-14 19:54 /dev/5370 >>>>>>>>>> >>>>>>>>>> $ sudo modprobe Intel537 >>>>>>>>>> returns nothing. >>>>>>>>>> >>>>>>>>>> However, >>>>>>>>>> $ sudo wvdial /etc/wvdial.conf >>>>>>>>>> still returns: >>>>>>>>>> Editing `/etc/wvdial.conf'. >>>>>>>>>> >>>>>>>>>> Scanning your serial ports for a modem. >>>>>>>>>> >>>>>>>>>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 >>>>>>>>>> baud >>>>>>>>>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 >>>>>>>>>> baud >>>>>>>>>> ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>>>>>>>>> ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 >>>>>>>>>> baud >>>>>>>>>> ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 >>>>>>>>>> baud >>>>>>>>>> ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>>>>>>>>> ttyS2<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 >>>>>>>>>> baud >>>>>>>>>> ttyS2<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 >>>>>>>>>> baud >>>>>>>>>> ttyS2<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>>>>>>>>> ttyS3<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 >>>>>>>>>> baud >>>>>>>>>> ttyS3<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 >>>>>>>>>> baud >>>>>>>>>> ttyS3<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Sorry, no modem was detected! Is it in use by another program? >>>>>>>>>> Did you configure it properly with setserial? >>>>>>>>>> >>>>>>>>>> Please read the FAQ at http://open.nit.ca/wiki/?WvDial >>>>>>>>>> >>>>>>>>>> If you still have problems, send mail to >>>>>>>>>> <wvdial-list@xxxxxxxxxxxx>. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Thanks and can you please advise me more... >>>>>>>>>> Ryan >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -----Original Message----- >>>>>>>>>> From: Antonio Olivares <olivares14031@xxxxxxxxx> >>>>>>>>>> To: Ryan Mckeown <ryanmckeown@xxxxxxxxxxx> >>>>>>>>>> Sent: Sun, 14 Jun 2009 7:13 pm >>>>>>>>>> Subject: Re: Ryan Mckeown, Northern Ireland kernel >>>>>>>>>> 2.6.28-11-generic >>>>>>>>>> >>>>>>>>>> Ryan, >>>>>>>>>> >>>>>>>>>> I believe that after successful installation, i.e, you ran >>>>>>>>>> $ make clean >>>>>>>>>> $ make 537 >>>>>>>>>> $ sudo make install >>>>>>>>>> >>>>>>>>>> Check with: >>>>>>>>>> $ dmesg >>>>>>>>>> for any driver's run-time problem. >>>>>>>>>> >>>>>>>>>> 4/ Checking the installation. >>>>>>>>>> Assuming you have a 537EP modem, you should see the following: >>>>>>>>>> $ ls -l /dev/modem >>>>>>>>>> lrwxrwxrwx 1 root root 10 jan 22 12:37 /dev/modem -> /dev/537ep >>>>>>>>>> $ ls -l /dev/536* >>>>>>>>>> crw-rw-rw- 1 root root 240, 1 jan 22 13:08 /dev/537ep >>>>>>>>>> crw-rw---- 1 root root 240, 1 jan 22 13:08 /dev/537ep0 >>>>>>>>>> >>>>>>>>>> This is by looking at the howto: >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> http://linmodems.technion.ac.il/packages/intel/Philippe.Vouters/Intel-Readme.txt >>>>>>>>>> >>>>>>>>>> Also you can check the following one >>>>>>>>>> http://ubuntuforums.org/showthread.php?t=210405 >>>>>>>>>> >>>>>>>>>> But essentially, I believe that you can do >>>>>>>>>> $ sudo modprobe Intel537 >>>>>>>>>> >>>>>>>>>> $ sudo wvdialconf /etc/wvdial.conf >>>>>>>>>> >>>>>>>>>> should scan and find modem port /dev/modem or /dev/537 >>>>>>>>>> >>>>>>>>>> edit username, password and ISP phone number try to dialout. >>>>>>>>>> Should >>>>>>>>>> something not work correctly don't hesitate to email back to me >>>>>>>>>> and >>>>>>>>>> to >>>>>>>>>> list. There might be other users who have your modem and can offer >>>>>>>>>> better advice than I do. >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> >>>>>>>>>> Antonio >>>>>>>>>> >>>>>>>>>> On Sun, Jun 14, 2009 at 12:54 PM, Ryan >>>>>>>>> >>>>>>>>> Mckeown<ryanmckeown@xxxxxxxxxxx> >>>>>>>>>> >>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>> Sorry, this email HAS the attachment... >>>>>>>>>>> >>>>>>>>>>> -----Original Message----- >>>>>>>>>>> From: Ryan Mckeown <ryanmckeown@xxxxxxxxxxx> >>>>>>>>>>> To: olivares14031@xxxxxxxxx >>>>>>>>>>> Sent: Sun, 14 Jun 2009 6:42 pm >>>>>>>>>>> Subject: Re: Ryan Mckeown, Northern Ireland kernel >>>>>>>>>>> 2.6.28-11-generic >>>>>>>>>>> >>>>>>>>>>> Antonio, >>>>>>>>>>> Find attached the dmesg.txt file. I also downloaded the Philippe >>>>>>>>>>> Vouters package and ran it with success. (I now have a file >>>>>>>>>> >>>>>>>>>> /dev/modem) >>>>>>>>>>> >>>>>>>>>>> The place where I first downloaded the pre-packaged driver was >>>>>>>>>>> here >>>>>>>>>> >>>>>>>>>> (it >>>>>>>>>>> >>>>>>>>>>> also seems to be from Philippe): >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> http://download192.mediafire.com/wzyvvhshdjpg/qfiisd4myym/intel537ep-jaunty_2-Philippe.Vouters_i386.deb >>>>>>>>>>> >>>>>>>>>>> Can you please advise further? >>>>>>>>>>> >>>>>>>>>>> Also I have received emails in my inbox which were addressed to >>>>>>>>> >>>>>>>>> Lilia, >>>>>>>>>>> >>>>>>>>>>> Zsolt and Gaurang. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Thanks again. >>>>>>>>>>> Ryan >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -----Original Message----- >>>>>>>>>>> From: Antonio Olivares <olivares14031@xxxxxxxxx> >>>>>>>>>>> To: Ryan Mckeown <ryanmckeown@xxxxxxxxxxx> >>>>>>>>>>> Cc: Discuss@xxxxxxxxxxxxx >>>>>>>>>>> Sent: Sat, 13 Jun 2009 4:13 pm >>>>>>>>>>> Subject: Re: Ryan Mckeown, Northern Ireland kernel >>>>>>>>>>> 2.6.28-11-generic >>>>>>>>>>> >>>>>>>>>>> Ryan, >>>>>>>>>>> >>>>>>>>>>> sacanModem recommends >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> http://linmodems.technion.ac.il/packages/intel/Philippe.Vouters/intel-5337EP_secure-2.60.80.0_2009_02_08.tar.bz2 >>>>>>>>>>> >>>>>>>>>>> but you tried other prebuilt drivers? >>>>>>>>>>> >>>>>>>>>>> but also scanModem detects an iterrupt problem: >>>>>>>>>>> >>>>>>>>>>> or candidate card in slot 01:01.0, firmware information and >>>>>>>>>>> bootup >>>>>>>>>>> diagnostics are: >>>>>>>>>>> PCI slot PCI ID SubsystemID Name >>>>>>>>>>> ---------- --------- --------- -------------- >>>>>>>>>>> 01:01.0 8086:1080 1028:1000 Modem: Intel Corporation >>>>>>>>> >>>>>>>>> FA82537EP >>>>>>>>>>> >>>>>>>>>>> 56K >>>>>>>>>>> V.92 Data/Fax Modem PCI >>>>>>>>>>> >>>>>>>>>>> Modem interrupt assignment and sharing: >>>>>>>>>>> --- Bootup diagnostics for card in PCI slot 01:01.0 ---- >>>>>>>>>>> [ 0.678108] pci 0000:01:01.0: reg 10 32bit mmio: >>>>>>>>>>> [0xfeafe000-0xfeafefff] >>>>>>>>>>> [ 0.678115] pci 0000:01:01.0: reg 14 io port: [0xde00-0xdeff] >>>>>>>>>>> [ 0.678152] pci 0000:01:01.0: PME# supported from D0 D3hot D3cold >>>>>>>>>>> [ 0.678156] pci 0000:01:01.0: PME# disabled >>>>>>>>>>> [ 1.979232] serial 0000:01:01.0: PCI INT A -> GSI 22 (level, low) >>>>>>>>>> >>>>>>>>>> -> >>>>>>>>>>> >>>>>>>>>>> IRQ 22 >>>>>>>>>>> [ 1.979345] 0000:01:01.0: ttyS1 at I/O 0xde08 (irq = 22) is a >>>>>>>>> >>>>>>>>> 16450 >>>>>>>>>>> >>>>>>>>>>> [ 1.979420] 0000:01:01.0: ttyS2 at I/O 0xde10 (irq = 22) is a >>>>>>>>>>> 8250 >>>>>>>>>>> [ 1.979494] 0000:01:01.0: ttyS3 at I/O 0xde18 (irq = 22) is a >>>>>>>>> >>>>>>>>> 16450 >>>>>>>>>>> >>>>>>>>>>> [ 1.979519] Couldn't register serial port 0000:01:01.0: -28 >>>>>>>>>>> >>>>>>>>>>> The PCI slot 01:01.0 of the modem card may be disabled early in >>>>>>>>>>> a bootup process, but then enabled later. If modem drivers load >>>>>>>>>>> but the modem is not responsive, read DOCs/Bootup.txt about >>>>>>>>> >>>>>>>>> possible >>>>>>>>>>> >>>>>>>>>>> fixes. >>>>>>>>>>> Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx >>>>>>>>>>> if help is needed. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> I guess we need to deal with this first. There are reports though >>>>>>>>>>> about modems with name >>>>>>>>>>> >>>>>>>>>>> FA82537EP 56K V.92 Data/Fax Modem PCI >>>>>>>>>>> >>>>>>>>>>> that don't work so of this I am not sure since scanModem >>>>>>>>>>> recommends >>>>>>>>>>> the driver from Phillipe Vouters? >>>>>>>>>>> >>>>>>>>>>> send us dmesg.txt and we'll saee how we can help. >>>>>>>>>>> >>>>>>>>>>> Regards, >>>>>>>>>>> >>>>>>>>>>> Antonio >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 6/13/09, Ryan Mckeown <ryanmckeown@xxxxxxxxxxx> wrote: >>>>>>>>>>>> >>>>>>>>>>>> Hey. >>>>>>>>>>>> Ok so heres the problem I'm faced with: >>>>>>>>>>>> >>>>>>>>>>>> A few weeks ago I received the Ubuntu 9.04 (Jaunty Jackelope) CD >>>>>>>>>>>> and >>>>>>>>>> >>>>>>>>>> I >>>>>>>>>>>> >>>>>>>>>>>> installed it alongside my Windows XP OS on my Dell Dimension >>>>>>>>>>>> 3000. >>>>>>>>>>>> I >>>>>>>>>>>> think I'm right in saying that Ubuntu 9.04 has the kernal >>>>>>>>>>>> 2.6.28-11 >>>>>>>>>>>> (whether that's important or not is beyond me). Anyway I >>>>>>>>>>>> installed >>>>>>>>> >>>>>>>>> it >>>>>>>>>>>> >>>>>>>>>>>> with success and was quite happy until I decided to try to get >>>>>>>>>> >>>>>>>>>> online. >>>>>>>>>>>> >>>>>>>>>>>> I looked up the installed manual (System > Help and Support) and >>>>>>>>>>>> it >>>>>>>>>>>> said that "NetworkManager manages wired, wireless, mobile >>>>>>>>>>>> broadband, >>>>>>>>>>>> vpn and dsl connections. It does not currently support dialup >>>>>>>>>>>> modem >>>>>>>>>>>> connections but there is help available in Chapter 6 -- Modems". >>>>>>>>>>>> So >>>>>>>>> >>>>>>>>> I >>>>>>>>>>>> >>>>>>>>>>>> went to chapter 6.1 titled "Identifying your modem" and from the >>>>>>>>>>>> instructions there, I downloaded scanModem from >>>>>>>>>>>> http://linmodems.technion.ac.il/packages/scanModem.gz (under >>>>>>>>>>>> Windows >>>>>>>>>>>> XP) and followed the rest of the instructions to open >>>>>>>>>> >>>>>>>>>> "ModemData.txt". >>>>>>>>>>>> >>>>>>>>>>>> ModemData.txt is attached. >>>>>>>>>>>> >>>>>>>>>>>> I also went to the link at the bottom of the page (also under >>>>>>>>>>>> XP): >>>>>>>>>>>> https://help.ubuntu.com/community/DialupModemHowto and I found >>>>>>>>>>>> that >>>>>>>>>>>> installing a dial-up modem should be as simple as: >>>>>>>>>>>> 1. Identify the modem >>>>>>>>>>>> 2. Download a driver for your modem or buy a more suited modem >>>>>>>>>>>> 3. Configure the connection to your ISP >>>>>>>>>>>> >>>>>>>>>>>> Seemed straight forward enough. I already had identified my >>>>>>>>>>>> modem >>>>>>>>>>> >>>>>>>>>>> using >>>>>>>>>>>> >>>>>>>>>>>> scanModem and its a: Intel Corporation FA82 537EP 56k V.92 >>>>>>>>>>>> DATA/FAX >>>>>>>>>>>> MODEM found on the PCI. I also20know its in (windows settings) >>>>>>>>>>>> COM >>>>>>>>>>> >>>>>>>>>>> 3.20 >>>>>>>>>>>> >>>>>>>>>>>> So >>>>>>>>>>>> then I proceeded and clicked on the link "Setup Intel537EP >>>>>>>>>>>> driver" >>>>>>>>>>>> (https://help.ubuntu.com/community/DialupModemHowto/Intel537EP) >>>>>>>>>>>> and >>>>>>>>>>>> found that the driver was "pre-packaged" for new users (me!) >>>>>>>>>>>> into >>>>>>>>>>>> a >>>>>>>>>>>> .deb file. So I downloaded it and ran it with apparent success >>>>>>>>>>>> in >>>>>>>>>>>> Ubuntu. >>>>>>>>>>>> >>>>>>>>>>>> Therefore, I continued to the third stage, I downloaded >>>>>>>>>>>> gnome-ppp >>>>>>>>>>>> (I >>>>>>>>>>>> heard it was good from threads I read and I found a useful page: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> https://help.ubuntu.com/community/DialupModemHowto/SetUpDialer.htm >>>>>>>>>>>> which gave me instructions as to how to install and run >>>>>>>>>>>> gnome-ppp) >>>>>>>>>>>> along with the dependencies it needed and ran it. I added myself >>>>>>>>>>>> to >>>>>>>>>>> >>>>>>>>>>> the >>>>>>>>>>>> >>>>>>>>>>>> dip and dialout groups, configured gnome-ppp and tried to dial. >>>>>>>>>>>> However, when I click "dial" the message appears "Sending >>>>>>>>>>>> password" >>>>>>>>>>> >>>>>>>>>>> and >>>>>>>>>>>> >>>>>>>>>>>> it stays like that until the thing times out. I then decided to >>>>>>>>>>>> use >>>>>>>>>>>> wvdialconf to see if it detected my modem and it said it didn't. >>>>>>>>>>>> >>>>>>>>>>>> I've tried loads of things since then and got nowhere. I found >>>>>>>>>>>> out >>>>>>>>>>> >>>>>>>>>>> that >>>>>>>>>>>> >>>>>>>>>>>> my modem has a Ambient MD3200 chipset and that Intel's support >>>>>>>>>>>> for >>>>>>>>>> >>>>>>>>>> the >>>>>>>>>>>> >>>>>>>>>>>> driver has all but ran out. Intel is actually telling me to try >>>>>>>>>>>> to >>>>>>>>>>>> contact the manufacturer because apparently Intel never actually >>>>>>>>>>>> manufactured the product themselves, they just put their name on >>>>>>>>>>>> it. >>>>>>>>>> >>>>>>>>>> I >>>>>>>>>>>> >>>>>>>>>>>> also learnt that Intel was formerly Ambient which was formerly >>>>>>>>> >>>>>>>>> Cirrus >>>>>>>>>>>> >>>>>>>>>>>> Logic. Apparently too there was a driver released for Linux for >>>>>>>>>>>> my >>>>>>>>>>>> modem back in about 2002 >>>>>>>>>>>> but I can't seem to find it anywhere. >>>>>>>>>>>> >>>>>>>>>>>> My ISP is Tiscali and I know >>>>>>>>>>>> the phone number to dial, the username and >>>>>>>>>>>> I have a fair idea of what my password is to use. I also know >>>>>>>>>>>> that >>>>>>>>>> >>>>>>>>>> the >>>>>>>>>>>> >>>>>>>>>>>> DNS address is determined on connection and the ISP uses PPP >>>>>>>>> >>>>>>>>> transfer >>>>>>>>>>>> >>>>>>>>>>>> methods. >>>>>>>>>>>> >>>>>>>>>>>> I think that the driver I installed didn't work so can you >>>>>>>>>>>> please >>>>>>>>>> >>>>>>>>>> help >>>>>>>>>>>> >>>>>>>>>>>> me to find another? >>>>>>>>>>>> >>>>>>>>>>>> Also can you please explain everything in lots of detail >>>>>>>>>>>> because, >>>>>>>>>> >>>>>>>>>> even >>>>>>>>>>>> >>>>>>>>>>>> though I have some experience in programming under Windows, >>>>>>>>>>>> Linux >>>>>>>>>>>> is >>>>>>>>>>>> still very new to me and hardware wouldn't really be my strong >>>>>>>>>>>> point >>>>>>>>>>>> either. >>>>>>>>>>>> >>>>>>>>>>>> Thanks >>>>>>>>>>>> Ryan >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> ________________________________________________________________________ >>>>>>>>>>>> >>>>>>>>>>>> Don't let your email address define you - Define yourself at >>>>>>>>>>>> http://www.tunome.com today! >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> ________________________________________________________________________ >>>>>>>>>>> >>>>>>>>>>> Don't let your email address define you - Define yourself at >>>>>>>>>>> http://www.tunome.com today! >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> ________________________________________________________________________ >>>>>>>>>>> >>>>>>>>>>> Don't let your email address define you - Define yourself at >>>>>>>>>>> http://www.tunome.com today! >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> ________________________________________________________________________ >>>>>>>>>> >>>>>>>>>> Don't let your email address define you - Define yourself at >>>>>>>>>> http://www.tunome.com today! >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> ________________________________________________________________________ >>>>>>>>> Don't let your email address define you - Define yourself at >>>>>>>>> http://www.tunome.com today! >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>> >>>> >>> >>> >> >> > >
