my problem was because i had the rpm + alpha drivers installed once i removed those it worked and my dsl light came on
now i need to get it to connect to aol (unfortunatly i don't pay bill so no say over isp)
i tried rp-pppoe got a connection time out.
had to ctrl+c the alpha drivers to stop it trying to connect.
dsl light stayed on tho : o)

o well, i'll just have to keep attacking till i get online with it : o)

well had another install of it. but this time i screenshotted it so anyone can see what i did, i hope this helps people help me resolve my issue.

images

WOW! I'm often told off on forums for not providing enough info. Now THAT's how it should be done.
The only thing I can think of is that under dns servers you have been putting aol.com.
Do you have the actual dns addresses in numbers? eg 123.456.78.90

unfortunatly aol doesn't provide there dns numbers
so i need a program that will dhcp the dns. to get the ip.
or so i have been told.
i am just about to go fiddle again see if i can get it working.

well whilst on phone to my gf i fiddled with the setting some more and well guess what....
i am posting this from linux mandrake 10.2
online through aol using a bt voyager 105 modem.

i will document what i have done to get online. then i'll post it in all posts that i have posted in for this, well ok just the ony and i'll link other posts to this one.

guess all it took was for me to take my mind off it, to think of what ima get when i see my gf tomoz, and wam bam thank you mam, it works : o)

will start documenting in abit : o)

ok seeing as i don't have a webhost thats perm. i'll type up the steps instead of
giving you lot images, i know images would have been easier but sorry...

[edit]Make sure you have the ppp package installed libcap is required by ppp, otherwise you won't be able to connect to the internet.[/edit]

first off get the drivers from here:
Drivers

if they are not avaliable, CURRENTLY get the alpha Nortek drivers. from here:
Driver home page

once they are downloaded
download the pdf below and port all of it over to linux

Pdf docs


follow the pdf's step by step, untill u get to configuration.
here are the settings i have in my configuration:

user: user full user name ie: user@aol.com
password: your password
vpi: 0
vci: 38

check update provider dns
dns1: aol.co.uk
dns2: aol.com

selection modem: i put bt voyager 105, IF yours is not on there, follow steps in the pdf file


make sure you have the right synch .bin file mine was synch03.bin

ppp mode: VCM_RFC2364
use DHCP: checked (so its on)

click create config.

i guess steps are same when using the text over consol. just enter the same data.

i hope that helps people

once i had done all that i typed eciadsl-start
it synched and about 10 seconds later i was connected.

if i am missing any details please let me know


regards Damnation

Hi,
I'm a bit of a linux newbie but so far have not really had many problems till now, i too am with AOhell.. (AOL),and i have a bloody bt 105 voyager.
I can run the eciadsl-config-tk and then eciadsl-start with no probs and i get a a connection but i cant view any web sites.
When i use adsl-start i just get timed out even though adsl-setup with rp-pppoe went smooth.
when i try to use harddrake it detects tap0 wich is what eci is setup to use as my aol use's 'RFC 1483 IPOATM Bridged LLC' but when i get to testing connection it say's not connected?...plz help.
I have all programmes that ive heard of in the forums ie...rp-pppoe..pppoverATM...kppp...and all other bloody thing i can think of that has any thing to do with adsl modems.
My dsl lights up and the data light flashes a little but nothing else i end up just having to stop the modem and fiddle a bit more and now i'm pulling my hair out and nearly on the phone to aol to tell them to shove there crap service up there arse.....grrr..
So far i really like mandrake and i so want to get on line in linux so i'm not forced to use bill gate's crap...Damnation if you read this please get in touch with me ta..


PS.. i have went through most of the problems that are the same as mine but with no luck i even followed Damnations to the letter apart from the escapulation mode as mine needs to be LLC or it dosent even synch.

ok sorry i have been away been at mygf's sorting out net there, we had a tiff and i got arrested for her breach of the peave and brung to my mums, the police love me : oP

basicallyi have had the same issue as you, the problem i had is that the built in firewall (linux)
i had to disable the firewall.

i suggest u try that, u can re-enable and open specific ports. so that certain programs can access the net, but without the firewall you should be fine.

Ok

I'm new to linux, (I'm sure you've never heard that before) And when i first read up about linux and the BT voyager 105 i pooped my lil' panties. Nothing but horror stories.

Read through the above post and the documentation on the eciadsl page and had it up and running first time.

I was sh*t scared i'd never get it to work, took me ten minutes.

Anyone reading this:

Im using simplyMepis 3.3.1
BT Broadband
BT voyager 105
the drivers supplied in the guide above which are readily available on the home site
synch file 3 which you need to obtain seperately from the driver files (a link is given in the driver documentation included in the post above)

Magic.


Many thanks to the posters on this thread and a HUGE thank you to the writers of these drivers!

Kind Regards,

Mitch.

I've been trying a few different distros and this modem has proved to be a nightmare on many.
Everything seems to depend on having the right packages installed on your system.

Kanotix, PCLinuxOS, Mepis, Fedora Core 3/4 all worked fine with no problems.
Ubuntu - You need to install gcc and (if I remember correctly) kernel headers from the installation disk then it works fine.
FoX Desktop - You need to get the extras disk then install the development packages and it works fine (I tried downloading gcc and it's dependencies seperately but it wouldn't work and I couldn't find a kernel headers package).
I couldn't get it working on Vector, Slax, gNOX, Blag, Berry, Arch or Vidalinux.

Well instead of starting a new post I figured I'd reply to this seeing as though it's got alot of info in already and it's relevant to my post. So basically I can't get online with AOL and eciadsl and I thought you kind folks here at LQ might be willing to help me.:rolleyes:

I've tried and tried but can't seem to get it working, however when I first had eciadsl I did manage to. Since then I've had to do a format and install again. I've searched alot of posts regarding eciadsl and noone of the things suggested therein would seem work for me.

I get it working before on Slackware 10.2 and after reinstalling it I coolant get it to work again. I had some channel error message. So after reading a few posts on here I decided to try another distro, SimplyMepis 3.4, thanks to the guy who wrote that brilliant article regarding it, it's so much more friendlier than Slackware, which is a huge benefit to an uber noob like myself. This time however I do manage to get it working it just wont connect, it fails on step 4.
It just hangs there, I've gone down and had dinner while I left it work it's magic but it just doesn't change. I've tried various settings step-by-step from various posts and articles none seem to change. I'm using sync3, which as you can see, works fine. I'm also using a BT Voyage 105. If there's anything I've missed out that you need to know, please post and I'll get it for you straight away.

With regards,

Evok3

I tried mepis a while ago and eciadsl worked ok so it may be a configuration problem.
Where did you get the driver? I've always used the one from the flashtux site - http://eciadsl.flashtux.org/download.php?lang=en and I normally use the source package though I used the fedora rpm on fedora core 5 and have used the debian i386 package on ubuntu and kanotix and they both worked ok so should work on mepis.
A couple of things to try, when it is synching, open another terminal and do eciadsl-stop then try eciadsl-start again and see if it brings up any errors.
Also try running eciadsl-doctor, if there is a problem it usually tells you, even when eciadsl-start doesn't.
If you can find some sort of error it should be easier to work out a solution.

Thanks alot, I'm writing this from Mepis right now :D Turns out I didn't delete my /etc/eciadsl/options file. Which eciadsl doctor told me.I can't believe I didn't try the doctor, I did it so many times on Slackware.

Realy, *really* thanks again fannymites, I really appreciate your reply. <3 ^^

I thought I'd post my eciadsl.conf because I know how hard it is to solve something sometimes and if so many hadn't replied to this I'd proably still be working it out.

You're welcome.

For future reference, I have had errors occasionaly about the /etc/eciadsl/options or /etc/ppp/options files not being found and haven't been able to connect (this has only happened to me on debian based systems for some reason), if you ever get that error, just re-install the eciadsl driver.