Fedora ADSL Connection Problem

Hi all,I am facing a problem in connecting to INTERNET in LINUX mode (FEDORA CORE 3). I am having Huawei SmartAX MT882 ADSL router from BSNL. It is working fine under WINDOWS XP.In Linux, I ran adsl-setup and entered the neccessery info. After that I ran (as instructed) ifup ppp0 and after a minute or so got an error saying:adsl_start: line 217: 1534 Terminated $CONNECT "$@" >/dev/null 2>^1Then, I ran adsl-connect, it is giving the following error😛ppo /dev/pts/3.........................................LCP: timeout sending Config-Requestspppo: Timeout waiting for PADO packets.............................................................................what is the problem? Eagerly waiting for ur response.Thanx in advance.regardsarjun reddy

I just gone thru earlier posts on this topic. Under topic"Dataone on Linux", it was written that i need to
edit this file

/etc/sysconfig/network-scripts/ifcfg-eth0 and put this there.

DEVICE=eth0
BOOTPROTO= none
IPADDR=192.168.1.20
ONBOOT=yes
NETMASK=255.255.255.0

and restart the network..
Does this work?

regards
arjun reddy

Originally posted by bheemarjun@Mar 24 2006, 02:52 PM
Hi all,

I am facing a problem in connecting to INTERNET in LINUX mode (FEDORA CORE 3).
I am having Huawei SmartAX MT882 ADSL router from BSNL. It is working fine under WINDOWS XP.

In Linux, I ran adsl-setup and entered the neccessery info. After that I ran (as instructed) ifup ppp0 and after a minute or so got an error saying:

adsl_start: line 217: 1534 Terminated $CONNECT "$@" >/dev/null 2>^1

Then, I ran adsl-connect, it is giving the following error:

pppo /dev/pts/3
.........................................
LCP: timeout sending Config-Requests
pppo: Timeout waiting for PADO packets
.......................................
......................................

what is the problem? Eagerly waiting for ur response.
Thanx in advance.

regards
arjun reddy
[snapback]45661[/snapback]

Click to expand...

[/quote]

Originally posted by bheemarjun@Mar 24 2006, 03:32 PM
Does this work?[snapback]45671[/snapback]

Click to expand...

[/quote]You wouldn't know it till you try it.... :blink:

Originally posted by bheemarjun@Mar 24 2006, 02:52 PM
what is the problem?[snapback]45661[/snapback]

Click to expand...

[/quote]The old version of fedora that you're running!
Core5 has the relevant packages updated. Run "rp-pppoe"

HI, I have moved from Windows 2000 to Linux Fedora Core 4.BSNL broadband connection worked fine in Windows 2000 and it is also working fine in Windows XP(my laptop). I have problem in Linux Fedora Core 4. There are 2 ways to establish the connection from ADSL modem MT882 right? 1) Ethernet and 2) USB 1) First I tried with the Ethernet connection, Fedora Core 4 is not detecting the hardware automatically.I Could not see the hardware entry in the "Desktop > System Settings > Network" Screen.I have Realtek 8139 Lan Card. If I add the harware manually and add the device manually with the respective driver, I could not activate it.I get an error "seems dost not exist, delaying Initialization".2)Then I tried the USB connection, luckily Fedora Core 4 detected the hardware automatically this time.I added a device for this hardware and set the IP for it instaed of fetching automatically from DHCP.I could activate the device, but I could not ping 192.168.1.1 and I could not access internet 🙁Then I thought let me intall the USB driver software that came along with the modem.Looks like the driver is written for kernel 2.4, I have 2.6.11 in Fedora Core 4 🙁.I do not want to downgrade the kernel version.Now I am thinking what to do...1) Buy another Lan Card assuming that will be detected by Fedora Core 4 and everything will go smooth...2) Downgrade the kernel to 2.4 and install the USB driver that came with the modem or look for the USB driver for the kernel 2.6.11I appreciate your help on this to configure my desktop in Linux....Thanks in Advance...Raffi

^ check this post if it helps :
( see also previous posts in this thread )

Seshu, Thanks for the quick response.Unfortunately, that driver is for Intex - sc92031 , not Advik - Realtek 8139 ...Thanks,Raffi

QUOTE(raffimd @ Oct 7 2006, 02:09 PM) [snapback]64407[/snapback]
Seshu,
Thanks for the quick response.
Unfortunately, that driver is for Intex - sc92031 , not Advik - Realtek 8139 ...

Thanks,
Raffi [/b]
Realtek 8139 drivers at www.realtek.com.tw are for kernel 2.4,the kernel 2.6.x should be able to detect rtl 8139 chipset.

QUOTE(harman163 @ Oct 7 2006, 04:34 PM) [snapback]64418[/snapback]
Realtek 8139 drivers at www.realtek.com.tw are for kernel 2.4,the kernel 2.6.x should be able to detect rtl 8139 chipset.
[/b]

I am downloading Fedora Core 5, hope that gets complete by tommorrow.
Will try to setup with FC5.

QUOTE(raffimd @ Oct 7 2006, 02:09 PM) [snapback]64407[/snapback]
Seshu,
Thanks for the quick response.
Unfortunately, that driver is for Intex - sc92031 , not Advik - Realtek 8139 ...

Thanks,
Raffi
[/b]

RTL8139 has native driver in kernel.org repo, try 8139too or 8139cp.
Beware intex and some other vendors sell totally different chipset based card
as RTL8139 based one, but in real underlying chipset is different.


QUOTE(raffimd @ Oct 7 2006, 01:26 PM) [snapback]64403[/snapback]
I have problem in Linux Fedora Core 4. There are 2 ways to establish the connection from ADSL modem MT882 right? 1) Ethernet and 2) USB
[/b]

Stick to ETHERNET based solution

1)
First I tried with the Ethernet connection, Fedora Core 4 is not detecting the hardware automatically.
I Could not see the hardware entry in the "Desktop > System Settings > Network" Screen.
I have Realtek 8139 Lan Card. If I add the harware manually and add the device manually with the respective driver, I could not activate it.
I get an error "seems dost not exist, delaying Initialization".
[/b]

Strange FC4 does have driver for RTL8139 based ETHERNET card, I suspect you having a card that been sold as RTL8138 based but having completely different chipset.

Could you please paste the output of command
lspci -vv -xx

You have to be root to execute above command.

QUOTE(vichitra @ Oct 7 2006, 07:10 PM) [snapback]64431[/snapback]

Could you please paste the output of command
lspci -vv -xx

You have to be root to execute above command.
[/b]

This is most sensible suggestion. However, you do not need to be root to run this command (just tried this on Debian).

Next, you should also paste the output of the following command ($> means the command prompt)
$> ifconfig -a

You may need to be root to run this though. Or try "/sbin/ifconfig" instead of just "ifconfig".

The realtex 8139 driver is so common that I find it very strange that your card runs with this driver and FC was not able to recognize it. The above two commands will clarify many things and we can start debugging from there.

Finally, I think you can open a GUI window to control your networking settings (after your card detection works). You should look for System->Networking in the main menu on your desktop. OR, you can run this gui from the command line using the following command:
$> network-admin

You will need root password to actually use this gui.

GL.

Hi folks,I have been wringing my hair out and digging around with truss all this week, but not been able to figure out why I get the error message as "kernel NETDEV WATCHDOG eth0 timeout" whenever I boot and openup "dmesg". I am using a PIII (Coppermine) with a USB MT882 modem which works fine under XP. I have tried Fedora core version 5, 3 and even Redhat ES relaease 4, RH 7.3, and even tried rebuilding kernel 2.6, 2.4 with options to include ppp and exclude apic. I have tried to use rp-pppoe3.8, but have found no success in even pinging 192.168.1.1, let alone getting connected to internet. I do not have a ethernet card and want to use the USB (CDCEthernet mode) only. Somewhere I remember to have read, interrupt to these USB devices are either level sensitive or edge sensitive. Is this some hardware prob that my PC can not drive the modem? Can someone help me?Thanks in advance-krishnacgh

QUOTE(krishnacgh @ Oct 12 2006, 07:39 PM) [snapback]65040[/snapback]
Hi folks,

I have been wringing my hair out and digging around with truss all this week, but not been able
to figure out why I get the error message as "kernel NETDEV WATCHDOG eth0 timeout" whenever
I boot and openup "dmesg". I am using a PIII (Coppermine) with a USB MT882 modem which works
fine under XP. I have tried Fedora core version 5, 3 and even Redhat ES relaease 4, RH 7.3, and
even tried rebuilding kernel 2.6, 2.4 with options to include ppp and exclude apic. I have tried to
use rp-pppoe3.8, but have found no success in even pinging 192.168.1.1, let alone getting connected
to internet. I do not have a ethernet card and want to use the USB (CDCEthernet mode) only.
Somewhere I remember to have read, interrupt to these USB devices are either level sensitive or
edge sensitive. Is this some hardware prob that my PC can not drive the modem?
Can someone help me?

Thanks in advance

-krishnacgh
[/b]

paste the output of dmesg and lsusb.
Are you sure eth0 instance of your USB interface is properly configured ?

/IMHO get one NIC card and use it./

QUOTE(vichitra @ Oct 12 2006, 07:48 PM) [snapback]65042[/snapback]
paste the output of dmesg and lsusb.
Are you sure eth0 instance of your USB interface is properly configured ?

/IMHO get one NIC card and use it./
[/b]


The relevant outputs are:

eth0 Link encap:Ethernet HWaddr 00:0F:A3:8E:2D:88
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20f:a3ff:fe8e:2d88/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:312 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:126 (126.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:1874 errors:0 dropped:0 overruns:0 frame:0
TX packets:1874 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2584070 (2.4 MiB) TX bytes:2584070 (2.4 MiB)
---------------------
netstat -rn

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

---------------------
lsusb gives

Bus 001 Device 004: ID 05fe:2001 Chic Technology Corp.
Bus 001 Device 003: ID 1110:5c01 Analog Devices Canada, Ltd (Allied Telesyn)
Bus 001 Device 002: ID 058f:9254 Alcor Micro Corp. Hub
Bus 001 Device 001: ID 0000:0000
----------------------
lspci -vv -xx gives

00:00.0 Host bridge: Intel Corp. 82810E DC-133 GMCH [Graphics Memory Controller Hub] (rev 03)
Subsystem: Intel Corp. 82810E DC-133 GMCH [Graphics Memory Controller Hub]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-

QUOTE(krishnacgh @ Oct 12 2006, 10:57 PM) [snapback]65089[/snapback]
The relevant outputs are:

eth0 Link encap:Ethernet HWaddr 00:0F:A3:8E:2D:88
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20f:a3ff:fe8e:2d88/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:312 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:126 (126.0 B)
[/b]

hmm .. that 312 errors signal a serious problem with your networking. I have never used USB with adsl modem. Actually, use of USB connection is strongly discouraged. To be quite honest, the best option would be to go the LAN card connection route.

Here are a few questions that come to mind:
1. Are you sure your USB connection to the ADSL modem is seen as eth0 by your Linux machine?
2. What is your configuration of your eth0? (see /etc/sysconfig/network-scripts/ifcfg-eth0 file)
3. Could you post the output of "lsmod", "usbmodules" and "lsusb" commands.

Other than that, please take a look at these few lines:
http://www.faqs.org/docs/Linux-HOWTO/DSL-HOWTO.html#AEN420

QUOTE(krishnacgh @ Oct 12 2006, 10:57 PM) [snapback]65089[/snapback]
---------------------
dmesg contains

NETDEV WATCHDOG: eth0: transmit timed out
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
parport0: PC-style at 0x378 [PCSPP,TRISTATE]
---------------------

Thanks

-krishnacgh
[/b]

please post complete output of /dmesg/.