Find the answer to your Linux question:
Results 1 to 4 of 4
Hello, I'm experiencing a rather strange hardware conflict, which I was unable to reproduce on my own, so any ideas are appreciated. I'm using a ECS K7SEM (v1.0) motherboard with ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jul 2005
    Posts
    13

    Strange hardware conflict ALSA/Ethernet


    Hello, I'm experiencing a rather strange hardware conflict, which I was unable to reproduce on my own, so any ideas are appreciated.

    I'm using a ECS K7SEM (v1.0) motherboard with integrated sound (SiS 701 and ethernet controller (Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+), which work perfectly on their own. Recently I installed a second ethernet controller (again Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+) for internet connection sharing purposes, which drove ALSA crazy. Here are several examples: Totem plays only 6 seconds of a movie and then locks completely, seeking a song in Audacious locks again, immense sound stuttering in MPlayer during movie playback and so on. I tried recompiling the kernel, recompiling the ALSA drivers, playing with settings, but nothing worked. Removing physically the external ethernet controller fixes all of the problems.

    I have named the interfaces using udev:

    KERNEL=="eth?", SYSFS{address}=="00:14:78:04:79:1c", NAME="eth0" (the external one)
    KERNEL=="eth?", SYSFS{address}=="00:0a:e6:35:45:06", NAME="eth1" (the integrated one)

    Here's ifconfig:

    eth0 Link encap:Ethernet HWaddr 00:14:78:04:79:1C
    inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
    inet6 addr: fe80::214:78ff:fe04:791c/64 Scope:Link
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:1134 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1247 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:188929 (184.5 KiB) TX bytes:268512 (262.2 KiB)
    Interrupt:5 Base address:0xdc00

    eth1 Link encap:Ethernet HWaddr 00:0A:E6:35:45:06
    inet addr:85.187.36.94 Bcast:85.187.36.255 Mask:255.255.255.0
    inet6 addr: fe80::20a:e6ff:fe35:4506/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:1982825 errors:0 dropped:0 overruns:0 frame:0
    TX packets:340108 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:873505612 (833.0 MiB) TX bytes:106034206 (101.1 MiB)
    Interrupt:11 Base address:0xe000

    dmesg | grep 8139 :

    8139too Fast Ethernet driver 0.9.28
    eth0: RealTek RTL8139 at 0xdc00, 00:14:78:04:79:1c, IRQ 5
    eth0: Identified 8139 chip type 'RTL-8100B/8139D'
    eth1: RealTek RTL8139 at 0xe000, 00:0a:e6:35:45:06, IRQ 11
    eth1: Identified 8139 chip type 'RTL-8139C'

    lspci :

    00:00.0 Host bridge: Silicon Integrated Systems [SiS] 730 Host (rev 02)
    00:00.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
    00:01.0 ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC Bridge)
    00:01.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 07)
    00:01.3 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 07)
    00:01.4 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS PCI Audio Accelerator (rev 02)
    00:02.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP)
    00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
    00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
    01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 440] (rev a3)


    I'm using Linux 2.6.19.1 and ALSA 1.0.14rc1. Thank you!

  2. #2
    Linux Enthusiast
    Join Date
    Jun 2005
    Posts
    668
    it could be a result of IRQ sharing or ACPI, try passing the noacpi option to the kernel on boot. or physically changing the second network card to another PCI slot. it could just be an irq conflict, maybe


  3. #3
    Just Joined!
    Join Date
    Jul 2005
    Posts
    13
    Quote Originally Posted by kern
    it could be a result of IRQ sharing or ACPI, try passing the noacpi option to the kernel on boot. or physically changing the second network card to another PCI slot. it could just be an irq conflict, maybe

    pci=noacpi fixed it. Thanks a million, kern.

  4. #4
    Linux Enthusiast
    Join Date
    Jun 2005
    Posts
    668
    heh excellent

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •