Marvell 88E8055 MTU problem

CollieJim · 07-16-2011, 09:19 PM

I'm trying to get networking up on a Toshiba Satellite M200, which has

Code:

02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E Gigabit Ethernet Controller (rev 12)
03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)

for networking. Wireless appears dead, probably because the antenna was in the broken screen that I threw away (external monitor used now).

The Marvell 88E8055 works with the Sky2 driver but only with coaxing. The default MTU is 576, and I get a *lot* of length errors in /var/log/messages. If I set MTU to 1500 everything works - for a while. Then something resets MTU back to 576 again.

What, and why? And how do I stop it?

TIA
Jim

andrewthomas · 07-16-2011, 09:46 PM

How are you connected to the internet?

Is your router configured @1492 possibly?

CollieJim · 07-17-2011, 02:50 AM

Westnet satellite.

I have a TP-Link router. Its LAN page only has fields for the address and mask, but the WAN page has a lot more including MTU which is 1500. I've set MTU for eth1 to 1492 to see what happens...

CollieJim · 07-18-2011, 08:23 AM

Every hour the following appears in /var/log/messages:

Code:

Jul 18 21:04:52 toshiba1 dhcpcd[2898]: eth0: renewing lease of 192.168.1.105
Jul 18 21:04:52 toshiba1 dhcpcd[2898]: eth0: acknowledged 192.168.1.105 from 192.168.1.1 `ÿ'
Jul 18 21:04:52 toshiba1 dhcpcd[2898]: eth0: leased 192.168.1.105 for 7200 seconds
Jul 18 21:04:52 toshiba1 dhcpcd[7434]: eth0: eth0: MTU set to 576

The next step is to find out how to set a much longer lease period, as well as an initial MTU.

andrewthomas · 07-18-2011, 08:41 AM

Do you have any lines uncommented in /etc/conf.d/network?

I don't have any lines that are not comments.

Have you altered /etc/dhcpcd.conf?

I think that the following is an unaltered dhcpcd.conf

Code:

# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Inform the DHCP server of our hostname for DDNS.
hostname
# To share the DHCP lease across OSX and Windows a ClientID is needed.
# Enabling this may get a different lease than the kernel DHCP client.
# Some upstream DHCP servers may also require a ClientID, such as FRITZ!Box.
#clientid

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU.
option interface_mtu
# A ServerID is required by RFC2131.
require dhcp_server_identifier

# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname