2.4.5 and pppd/pppoe

2.4.5 and pppd/pppoe

[Daniel Rose]

Hello,
I'm having problems with 2.4.5 and my pppoe connection.
The kernel compiles fine, and works fine too, until I reboot, at which
time it decides it no longer wants to work, and any time I attempt to
call my start-pppoe script, i get:

May 28 15:54:28 rocket pppd[3091]: pppd 2.4.1 started by root, uid 0
May 28 15:54:28 rocket pppd[3091]: Using interface ppp0
May 28 15:54:28 rocket pppd[3091]: Connect: ppp0 <--> /dev/ttyp0
May 28 15:54:43 rocket pppd[3091]: Hangup (SIGHUP)
May 28 15:54:43 rocket pppd[3091]: Modem hangup
May 28 15:54:43 rocket pppd[3091]: Connection terminated.
May 28 15:54:44 rocket pppd[3091]: Exit.

I am assuming that this is because of my eth0, which shows in ifconfig:

eth0      Link encap:Ethernet  HWaddr 00:00:00:00:00:00 (it's using
via-rhine chipset, compiled into kernel, not a module)

This _only_ occurs after I reboot (ie. i can start up the new 2.4.5
kernel and work it perfectly once, then reboot and it doesnt work)

Anybody have any ideas?

Thanks,

Daniel Rose

Re: (via-rhine.c problem) 2.4.5 and pppd/pppoe

[Daniel Rose]

Ok, I have decided the problem lays in via-rhine.c, the ethernet driver
for my card. The second boot finds the mac address as 00's all the time,
regardless of whether the driver is compiled as a module, or monolith.

On 28 May 2001 16:18:55 -0400, Daniel Rose wrote:
> 
> Hello,
> I'm having problems with 2.4.5 and my pppoe connection.
> The kernel compiles fine, and works fine too, until I reboot, at which
> time it decides it no longer wants to work, and any time I attempt to
> call my start-pppoe script, i get:
> 
> May 28 15:54:28 rocket pppd[3091]: pppd 2.4.1 started by root, uid 0
> May 28 15:54:28 rocket pppd[3091]: Using interface ppp0
> May 28 15:54:28 rocket pppd[3091]: Connect: ppp0 <--> /dev/ttyp0
> May 28 15:54:43 rocket pppd[3091]: Hangup (SIGHUP)
> May 28 15:54:43 rocket pppd[3091]: Modem hangup
> May 28 15:54:43 rocket pppd[3091]: Connection terminated.
> May 28 15:54:44 rocket pppd[3091]: Exit.
> 
> I am assuming that this is because of my eth0, which shows in ifconfig:
> 
> eth0      Link encap:Ethernet  HWaddr 00:00:00:00:00:00 (it's using
> via-rhine chipset, compiled into kernel, not a module)
> 
> This _only_ occurs after I reboot (ie. i can start up the new 2.4.5
> kernel and work it perfectly once, then reboot and it doesnt work)
> 
> Anybody have any ideas?
> 
> Thanks,
> 
> Daniel Rose
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: (via-rhine.c problem) 2.4.5 and pppd/pppoe

[Urban Widmark]

On 29 May 2001, Daniel Rose wrote:

> Ok, I have decided the problem lays in via-rhine.c, the ethernet driver
> for my card. The second boot finds the mac address as 00's all the time,
> regardless of whether the driver is compiled as a module, or monolith.

Do you boot something else in between? Like win98? There is a known
problem with the via-rhine driver not being able to restart some versions
of the card after win98 has shut it down. Perhaps some bioses do similar
clever things.

This seems to only happen with newer chips that have power management
support. If you don't boot into win98, perhaps you can play with bios
settings until the driver is fixed (or fix the driver of course).

Which type of via-rhine do you have? (manufacturer, model of card)
When you boot what does dmesg say about eth0? (or lspci -n)


D-Link makes a card called DFE-530TX. If you have that it can be one of
(at least) 2 different versions. Could you in addition to sending lspci
info identify which of these images match best?

DFE-530TX REV-A1 (vt3043, PCI ID 1106:3043)
http://www.intozgc.com/2001jrsc/200103/200103image/26%B5%DA%B6%FE%D6%D6.jpg

DFE-530TX REV-B1 (hopefully vt6102, PCI ID 1106:3065 but I'm not sure)
http://www.intozgc.com/2001jrsc/200103/200103image/26%D5%FD%C6%B7.jpg

or this which is also called B1 ... but a chip with different markings.
http://www.intozgc.com/2001jrsc/200103/200103image/26%B5%DA%D2%BB%D6%D6.jpg

This page tries to explain something about card versions, but I don't
speak the language (which ever it is).
http://www.intozgc.com/2001jrsc/200103/20010326.htm

I think the conclusion is DL10030A -> REV-B1, DL10030 -> REV-A1.

/Urban