Frog problems

Sp00n · 24 Oct 2002 at 21:48

I have fixed all of that, the alcaudsl.sys does exist, the modem_run -m -f /root/alcaudsl.sys command was corrected and runs without error.

Altered Corpse · 24 Oct 2002 at 23:00

Originally posted by Shak

That sums up whats wrong!

/edit: I think this is a clear case of my GIMP skills own!

Shak

Shak, i answered that problem the 5th post down (he had a spelling mistake).

And yes, your GIMP skills do own!

Altered Corpse · 24 Oct 2002 at 23:02

Originally posted by Sp00n

/etc/ppp/peers/adsl:

pty "/usr/local/sbin/pppoa3 -m 1 -c -vpi 8 -vci 35"

That's your problem. Your VPI should be 0 (not 8) and your VCI should be 38 (not 35).

Change that file to the correct settings, and restart your computer (it's the only way i can think of to clear the microcode from the frog).

Sp00n · 24 Oct 2002 at 23:35

It works

...........but, now there is a DNS issue as i can only visit ip's rather than urls

Ben · 24 Oct 2002 at 23:40

Originally posted by Sp00n
It works ...........but, now there is a DNS issue as i can only visit ip's rather than urls

echo "nameserver 158.43.128.26" >> /etc/resolv.conf

I chose pipex since it was the first one I could look up, even though I'm not on pipex

Sp00n · 24 Oct 2002 at 23:42

Originally posted by Ben
echo "nameserver 158.43.128.26" >> /etc/resolv.conf

...sorry, what? :confused:

[SIZE=0.5]yes, i am a newb[/SIZE]

Ben · 24 Oct 2002 at 23:44

Originally posted by Sp00n
...sorry, what?

[SIZE=0.5]yes, i am a newb[/SIZE]

Sorry, since you were running commands I thought you were in the swing of things

as root, run that command (in a shell), it'll add a nameserver entry to your resolv.conf file, which should solve your dns problem

Sp00n · 24 Oct 2002 at 23:55

that dns doesnt work :/

Altered Corpse · 24 Oct 2002 at 23:57

Type the following in a shell:

Code:

ln -s /etc/ppp/resolv.conf /etc/resolv.conf

Sp00n · 25 Oct 2002 at 00:10

'/etc/resolv.conf : file exists

Altered Corpse · 25 Oct 2002 at 00:14

Originally posted by Sp00n

Remove it then.

Code:

rm /etc/resolve.conf

And then run the ln command/

Sp00n · 25 Oct 2002 at 00:23

Sorted

posting from redhat now, just gotta sort out my other problems, find out about msn on linux and im sorted

thanks again

iam · 25 Oct 2002 at 01:11

Originally posted by Sp00n
Sorted posting from redhat now, just gotta sort out my other problems, find out about msn on linux and im sorted thanks again

I belive Shak uses Trillian

Sp00n · 25 Oct 2002 at 01:38

trillian sucks

I'm trying to install amsn with another whole host of problems.

Shak · 25 Oct 2002 at 08:02

Originally posted by iam
I belive Shak uses Trillian

Trillian is for Winblows mate, I run GAIM, so I can use ICQ/AIM/MSN, is should be installed as standrd for your distro.

Shak

Lior · 25 Oct 2002 at 19:24

sp00n what distro are u using mate

im having probs getting the frog to work myself

Shak · 25 Oct 2002 at 19:29

He's using Redhat 8.0, why not post your problem here, and we'll have a look at it.

Have you followed the above HOWTO?

If you're using RH 7.3 then you'll want to get the latest version of the kernel and compile it otherwise it wont work for you

There was a bug in the 2.4.18 series of Kernels that had USB problems

Shak

Altered Corpse · 25 Oct 2002 at 19:51

Originally posted by Shak
He's using Redhat 8.0, why not post your problem here, and we'll have a look at it.

Have you followed the above HOWTO?

If you're using RH 7.3 then you'll want to get the latest version of the kernel and compile it otherwise it wont work for you There was a bug in the 2.4.18 series of Kernels that had USB problems

Shak

Eh? There is absolutely no reason why it won't work in RedHat 7.3. As for a bug in 2.4.18, i've never had any problems with any of my USB devices.

Shak · 25 Oct 2002 at 19:58

Originally posted by Altered Corpse
Eh? There is absolutely no reason why it won't work in RedHat 7.3. As for a bug in 2.4.18, i've never had any problems with any of my USB devices.

I was reading and there was a USB Timeout bug in one of the kernels (I seem to recall it being 2.4.18 on RH 7.3) this caused the USB modules just to report timeouts on every time a device was accessed, I was pretty sure that it was 2.4.18, Ill have to verify this.

It may have been a bug in the frog drivers.

Shak

Lior · 25 Oct 2002 at 20:46

No matter

I got it working

after weeks of trying

Thanks guys