reopened - LM13 Wired connection - RX frame errors

Questions about Wi-Fi and other network devices, file sharing, firewalls, connection sharing etc
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
Tandem78

reopened - LM13 Wired connection - RX frame errors

Post by Tandem78 »

Update 3:
I've made progress! A workaround solution is

Code: Select all

sudo ip link set eth0 mtu 1496
Question - how can I make this a permanent change, or get the setting into the startup? I found this - http://forums.linuxmint.com/viewtopic.p ... 0&p=894227 which suggests I could edit /etc/dhcp/dhclient.conf but doesn't indicate how. Then there's this http://www.cyberciti.biz/faq/how-can-i- ... interface/ but that seems to configure a totally static IP address as well.

Update 2:
I apologize for the confusion, it comes from trying to write a post after working on a problem all night.
The correct story is as follows. The ethernet wired connection and LM 13 Maya installation works correctly on my home base, but here in Mexico connected to ethernet wired connection, I get really bad framing errors making access to the internet impossible.

Code: Select all

ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1e:33:00:ea:cb  
          inet addr:192.168.0.6  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::21e:33ff:fe00:eacb/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:74 errors:76 dropped:0 overruns:0 frame:76
          TX packets:191 errors:0 dropped:0 overruns:0 carrier:0
          collisions:4 txqueuelen:1000 
          RX bytes:18811 (18.8 KB)  TX bytes:28320 (28.3 KB)
          Interrupt:19 Base address:0xdead 

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:66 errors:0 dropped:0 overruns:0 frame:0
          TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:9932 (9.9 KB)  TX bytes:9932 (9.9 KB)
I can ping URLs, the DNS resolution works, and the pings work - presumably with short packets
The Windows partition on the machine works perfectly, no problems.

In the mean time, in desperation, I D/Ld LM17.1 under windows, setup up a USB boot stick and installed LM17.1 - and voila, no dropped frames. Except that I can't get the SIS671 video drivers to work under 17.1, but that's a different battlefield. I now reinstalled LM13 and the dropped frames problem is back again. So it looks like the lack of SIS support is scr*ing me both on LM13 and on LM17.1

more system info about the LM 13 setup -

Code: Select all

inxi -nF
System:    Host: super-ESPRIMO-Mobile-V5535 Kernel: 3.2.0-23-generic i686 (32 bit) 
           Desktop: Xfce 4.10.0 Distro: Linux Mint 13 Maya
Machine:   System: FUJITSU SIEMENS (portable) product: ESPRIMO Mobile V5535 version: V1.02
           Mobo: FUJITSU SIEMENS model: Z17M2.0 version: V1.02 Bios: Phoenix version: V1.06 date: 05/30/08
CPU:       Single core Intel Celeron CPU 540 (-UP-) cache: 1024 KB flags: (lm nx sse sse2 sse3 ssse3) clocked at 1866.737 MHz 
Graphics:  Card: Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter 
           X.Org: 1.11.3 drivers: vesa (unloaded: sis,fbdev) Resolution: 1024x768@61.0hz 
           GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 0x300) GLX Version: 2.1 Mesa 8.0.2
Audio:     Card: Silicon Integrated Systems [SiS] Azalia Audio Controller driver: snd_hda_intel Sound: ALSA ver: 1.0.24
Network:   Card-1: Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) driver: ath5k 
           IF: wlan0 state: down mac: 00:16:44:83:4f:23
           Card-2: Silicon Integrated Systems [SiS] 191 Gigabit Ethernet Adapter driver: sis190 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:1e:33:00:ea:cb
Drives:    HDD Total Size: 82.1GB (4.6% used) 1: /dev/sda WDC_WD800BEVS 80.0GB 
           2: USB /dev/sdb Flash_Disk 2.1GB 
Partition: ID: / size: 9.4G used: 3.0G (34%) fs: ext4 ID: /home size: 25G used: 527M (3%) fs: ext4 
           ID: swap-1 size: 1.34GB used: 0.00GB (0%) fs: swap 
Sensors:   Error: You do not have the sensors app installed.
Info:      Processes: 137 Uptime: 1 min Memory: 191.0/1441.9MB Client: Shell inxi: 1.7.33 


nm-tool

NetworkManager Tool

State: connected (global)

- Device: wlan0 ----------------------------------------------------------------
  Type:              802.11 WiFi
  Driver:            ath5k
  State:             unavailable
  Default:           no
  HW Address:        00:16:44:83:4F:23

  Capabilities:

  Wireless Properties
    WEP Encryption:  yes
    WPA Encryption:  yes
    WPA2 Encryption: yes

  Wireless Access Points 


- Device: eth0  [Wired connection 1] -------------------------------------------
  Type:              Wired
  Driver:            sis190
  State:             connected
  Default:           yes
  HW Address:        00:1E:33:00:EA:CB

  Capabilities:
    Carrier Detect:  yes
    Speed:           100 Mb/s

  Wired Properties
    Carrier:         on

  IPv4 Settings:
    Address:         192.168.0.6
    Prefix:          24 (255.255.255.0)
    Gateway:         192.168.0.1

    DNS:             200.79.231.5
    DNS:             200.79.231.6


Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
jtarin

Re: reopened - LM13 Wired connection - RX frame errors

Post by jtarin »

What kernel are you using in both iterations of Mint?(uname -r) Is it possible an upgrade to the newest stable kernel(3.19.2) will alleviate these issues? This card seems to be problematic to some users....either no connection at all or only intermittent. However there seems to be some fixes around for the video card. (google)
The latest driver(s) for net and video are available at
http://w3.sis.com/download/agreement.php?url=/download/

Which includes information on installing.
Last edited by jtarin on Mon Mar 23, 2015 8:34 am, edited 1 time in total.
Tandem78

Re: reopened - LM13 Wired connection - RX frame errors

Post by Tandem78 »

this is running

Code: Select all

uname -r
3.2.0-23-generic
I have no idea how to change the kernel. Given that the SIS video drivers no longer work correctly in LM17.1, I don't want to start on yet another battlefield.
Like I say, it's the MTU settng. How to change it permanently in LM13?
Last edited by Tandem78 on Mon Mar 23, 2015 8:38 am, edited 1 time in total.
jtarin

Re: reopened - LM13 Wired connection - RX frame errors

Post by jtarin »

Tandem78 wrote:this is running

Code: Select all

uname -r
3.2.0-23-generic
Like I say, it's the MTU settng. How to change it permanently?
http://www.cyberciti.biz/faq/centos-rhe ... -mtu-size/
http://www.debianhelp.co.uk/mtu.htm
Tandem78

Re: reopened - LM13 Wired connection - RX frame errors

Post by Tandem78 »

jtarin,
thanks for the reply - reading the links and from what I'd already researched, in order to predefine MTU you have to define eth0 as static in the network/interfaces file, meaning you turn off DHCP, not exactly a flexible solution.
My interfaces file currently looks like this -

Code: Select all

auto lo
iface lo inet loopback
The debianhelp suggests this, but says it's deprecated -

Code: Select all

iface eth0 inet dhcp
hostname "mymachine"
name LAN Interface
pre-up /sbin/ifconfig $IFACE mtu 1492
[update]
I tried the following to match the info in nm-tool:

Code: Select all

iface eth0 inet static
                address 192.168.0.6
                network 192.168.0.0
                gateway 192.168.0.1
                netmask 255.255.255.0
                mtu 1492
The effect is that the eth0 does not come up at all. So there's something wrong but no idea what. How can I be sure that the router will even work with a static IP address?

As I said above somewhere, the problem does not appear to exist in 17.1, but I can't use that on account of the SIS video drivers. So in what way is 17.1 different?
Locked

Return to “Networking”