How do you expect people to help you if can't even post exact error messages?

If you don't know how then tell us. Well, here's a tip:

adsl-start > adsl-start-dump.txt
adsl-stop > adsl-stop-dump.txt
adsl-connect > adsl-connect-dump.txt

Then copy all those *.txt files onto a Windows FAT32 partition, or easier still, onto a floppy disk.

Open it when you boot up using Windows, or go to a working teminal and paste the results in the *.txt files here.

Not that difficult right?

here's the output


while netconfig is configured using loopback:

root@miguet:~# adsl-start
................TIMED OUT
/usr/sbin/adsl-start: line 194: 737 Terminated $CONNECT "$@" >/dev/null 2>&1
root@miguet:~# adsl-status
adsl-status: Link is down (can't read pppoe PID file /var/run/pppoe.conf-adsl.pid.pppoe)
root@miguet:~# adsl-connect
Using interface ppp0
Connect: ppp0 <--> /dev/pts/1
LCP: timeout sending Config-Requests
Connection terminated.
pppoe: Timeout waiting for PADO packets
Using interface ppp0
Connect: ppp0 <--> /dev/pts/1
LCP: timeout sending Config-Requests
Connection terminated.
pppoe: Timeout waiting for PADO packets
Using interface ppp0


while adsl-connect is on:

root@miguet:~# adsl-status
adsl-status: Link is attached to ppp0, but ppp0 is down


after hitting ctrl-z:

root@miguet:~# adsl-status
adsl-status: Link is down -- could not find interface corresponding to
pppd pid 1021


after adsl-connect is stopped:

root@miguet:~# adsl-stop
Killing pppd (1021)
cat: /var/run/pppoe.conf-adsl.pid.start: No such file or directory
Killing adsl-connect (958)








while netconfig is configured using DHCP:

root@miguet:~# adsl-start
................TIMED OUT
/usr/sbin/adsl-start: line 194: 1438 Terminated $CONNECT "$@" >/dev/null 2>&1
root@miguet:~# adsl-status
adsl-status: Link is down (can't read pppoe PID file /var/run/pppoe.conf-adsl.pid.pppoe)
root@miguet:~# adsl-connect
Using interface ppp0
Connect: ppp0 <--> /dev/pts/1
LCP: timeout sending Config-Requests
Connection terminated.
pppoe: Timeout waiting for PADO packets
Using interface ppp0
Connect: ppp0 <--> /dev/pts/1

[1]+ Stopped adsl-connect
root@miguet:~# adsl-stop
Killing pppd (1698)
Terminating on signal 15.
cat: /var/run/pppoe.conf-adsl.pid.start: No such file or directory
Killing adsl-connect (1659)
root@miguet:~# Connection terminated.
pppoe: Timeout waiting for PADO packets


while adsl-connect is on:

root@miguet:~# adsl-status
adsl-status: Link is attached to ppp0, but ppp0 is down


after hitting ifconfig eth0:

root@miguet:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:07:95:43:BA:12
inet addr:4.46.27.230 Bcast:4.46.31.255 Mask:255.255.224.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29 errors:0 dropped:0 overruns:0 frame:0
TX packets:53 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:2845 (2.7 Kb) TX bytes:3874 (3.7 Kb)
Interrupt:11 Base address:0xd400


i don't know what else i'm missing.. my connection doesn't require chaps or options in adsl-setup.. i ran another linux distro and getting packages on the internet while installing was no hassle..

Did you compile the kernel with module support for your NIC? And also asynch support (under Networking, if I'm not mistaken).

It seems from your ifconfig eth0 output that your NIC is supported, I'm just asking to confirm. The asynch support should be there if you're using the Slack bare.i kernel, I don't know whether you've recompiled a newer one.

i did a fresh install of slackware 9 choosing the option newbie.. so everything got copied including the latest stable kernel..

the NIC was probed while installing and the module might have been installed to support the NIC..

the HOWTO for rp-pppoe says that my NIC could work in half duplex mode.. from the default install, my NIC is configured for full duplex.. i don't know how to change the setting for half duplex.. so i haven't tried that.. if you know how to do it, please mention it for me to try..

Hi,

I'm a newbie and using Red Hat 8. I'm using DSL to connect to Internet (provider is SBC)..Also am not using any router etc..

But for me, it was very easy via the GUI...I just had to provide the provider name, login and pasowrd, along with the server information..

Previoulshy I had assigned a dummy static IP addr to eth0..
After I configured my DSL, I removed the static IP and made it to DHCP...and everytime I reboot the m/c, it would stop for 10 minutes at eth0 entry and fail....Then somebody pointed out that if I am not using any router then I should re-assign the dummy IP to eth0...

After that everything was fine...

dunno how much this will help ...but thought I might share this with U...

Good luck !!

nevermind.. the problem was configuring adsl-setup itself..

i didn't need to configure adsl-setup.. after a fresh install of slackware 9, the install caught my ethernet and after that, everything was setup for me to get on the internet.. no configuring adsl-setup.. no configuring eth0.. everything worked right out of the box.. thank you slackware..