Talk:Clevo D901C

From LinuxLaptopWiki

Jump to: navigation, search

Contents

[edit] Network Problems

Intermittent network connection using both WiFi and Gig-E connections.

Experiencing similar problems in network connection whether using wired (Gig-E NIC) or wireless connectivity. Both adapters “work”; i.e. they will get a correct IP address via DHCP, along with corresponding gateway, DNS IPs and subnet mask. Both can access a web page – if it is relatively low-bandwidth.

Problem: Both will download a maximum of approx. 64 KB before either disconnecting or timing-out. After a random amount of time, both will reconnect and, if possible, resume downloading another 64KB where they will disconnect again. This process will continue ad nauseum. If the file is larger than 64KB – for example I am downloading a 2 MB file – it will connect and reconnect multiple times until the file is downloaded. Over a 500 Kbps connection, the result is maybe a 32 Kbps speed due to the frequent timing-out.

Given that both interfaces have the same problem, I am wondering if it is a bus problem. Both connect over the PCI-X bus (I believe). I have used multiple drivers for both in an attempt to alleviate the problem, and though many have “worked” (Intel’s various flavors of the 4965 driver, and ndiswrapper or various other approved drivers for the Gig-E), they all exhibit the same timing out after approx. 64 KB download problem. This also occurs under all Linux distros I have tried, based on Debian, Mandrake/Mandriva, PCLinuxOS, or Suse, etc (to whit, SamLinux, Ubuntu/Kubuntu, Debian, Mandriva 2008.1, Fedora’s latest, PcLinuxOS, OpenSUSE 10+, Gentoo, and probably a few others I’ve tried.

Yes – both work extremely well under Windows. No, it is not the WOL (wake-on-LAN) problem. This is disabled for both in XP, and the symptom exhibited by that problem is not on/off/on/off connectivity it is either go/no-go.

-timekills

[edit] Report #2

I've noticed the following things about the WiFi:

  1. Recently (last two weeks), the card constantly disassociates from the AP. Authentication fails until the driver is unloaded and reloaded, usually. Sometimes a reboot is required. This seems to occur both randomly and during peak network activity (downloads > 700K/sec).
  2. I have no proof but I'm convinced the driver/hardware are crashing my system. At university, my computer constantly crashes. The only difference I can think of is the wireless network there. Also, sometimes my PC crashes during peak network activity.

To the original poster:

  1. If you happen to recall, please post the range of kernels, iwl4965 drivers and iwl4965 firmwares you used.
  2. Have you tried disabling bluetooth with Fn-12? Just a guess.
  3. Try booting with the irqpoll kernel option. This didn't work well for me, make sure you can turn it off too :)

As for me, dmesg output:

iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.26kds
iwl4965: Copyright(c) 2003-2008 Intel Corporation
ACPI: PCI Interrupt 0000:09:00.0[A] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:09:00.0 to 64
iwl4965: Detected Intel Wireless WiFi Link 4965AGN
iwl4965: Tunable channels: 11 802.11bg, 13 802.11a channels
phy0: Selected rate control algorithm 'iwl-4965-rs'
ACPI: PCI interrupt for device 0000:09:00.0 disabled

kernel 2.6.24.4-64.fc8 (Fedora Core 8) and iwl4965-firmware-4.44.1.20-1.

Update!

After writing the above I added the following lines to my /etc/modprobe.conf:

options cfg80211 ieee80211_regdom="JP"
options iwl4965 hwcrypto=1 disable_hw_scan=1

It's been about a week since then and no crashes! And I've been doing a lot of high speed network activity, both from the internet and from the local network here. So let's hope I didn't just jinx myself and hopefully it will help you... of course you said your wired network card was affected too...don't know what's up with that. Good luck!

[edit] Report #3

(timekills) dmesg output:

iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.0
iwl4965: Copyright(c) 2003-2007 Intel Corporation
ACPI: PCI Interrupt 0000:09:00.0[A] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:09:00.0 to 64
iwl4965: Detected Intel Wireless WiFi Link 4965AGN
ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1b.0 to 64
iwl4965: Tunable channels: 11 802.11bg, 13 802.11a channels
wmaster0: Selected rate control algorithm 'iwl-4965-rs'

and for wired:

eth0: RTL8168b/8111b at 0xf8888000, 00:90:f5:57:75:7e, XID 38000000 IRQ 218
r8169 Gigabit Ethernet driver 2.2LK loaded
r8169: eth0: link up
r8169: eth0: link up
eth0: no IPv6 routers present
r8169: eth0: link up
eth0: no IPv6 routers present

kernel (currently): 2.6.24-16-generic (2.6.24-16-generic SMP mod_unload 586)

more ethernet info:

filename:       /lib/modules/2.6.24-16-generic/kernel/drivers/net/8139too.ko
version:        0.9.28
license:        GPL
description:    RealTek RTL-8139 Fast Ethernet driver
author:         Jeff Garzik <jgarzik@pobox.com>
srcversion:     69C244F6E1FEDCB14385855

Not sure how to check the firmware versions, when I use ethtool it gives me a blank line after the firmware, ie:

driver: r8169
version: 2.2LK
firmware-version: 
bus-info: 0000:07:00.0

I wonder if it is an IPV6 incompatibility or if my original hypothesis of a bus problem is correct.

[edit] ROCK D901C Fedora 10 Experience

[edit] Issues With Dual Nvidia 9800M GTX cards Fedora 10

Had a lot of problems initially getting the Fedora install to finalise due to the two video cards and xorg not knowing which bus to use. I tracked down the the problem and using nvidia's own drivers got all to work but still struggled as it was driving both heads at once. I finally got to the end by editing out of my xorg.conf the information for the second card. Ironically it was the higher bus id which was driving the LCD.

Below is my xorg.conf:

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 1.0  (buildmeister@builder62)  Sat Apr  4 07:37:37 PST 2009

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
#    Screen      1  "Screen1" RightOf "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
    FontPath        "/usr/share/fonts/default/Type1"
EndSection

Section "Module"
    Load           "dbe"
    Load           "extmod"
    Load           "type1"
    Load           "freetype"
    Load           "glx"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/input/mice"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from data in "/etc/sysconfig/keyboard"
    Identifier     "Keyboard0"
    Driver         "kbd"
    Option         "XkbLayout" "gb"
    Option         "XkbModel" "pc105"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

#Section "Monitor"
#    Identifier     "Monitor1"
#    VendorName     "Unknown"
#    ModelName      "Unknown"
#    HorizSync       28.0 - 33.0
#    VertRefresh     43.0 - 72.0
#    Option         "DPMS"
#EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce 9800M GTX"
    BusID          "PCI:4:0:0"
EndSection

#Section "Device"
#    Identifier     "Device1"
#    Driver         "nvidia"
#    VendorName     "NVIDIA Corporation"
#    BoardName      "GeForce 9800M GTX"
#    BusID          "PCI:4:0:0"
#EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

#Section "Screen"
#    Identifier     "Screen1"
#    Device         "Device1"
#    Monitor        "Monitor1"
#    DefaultDepth    24
#    SubSection     "Display"
#        Depth       24
#    EndSubSection
#EndSection

[edit] Webcam

I also found that my webcam works straight out of the box after I'd read your wiki and turned it on that is!

usb 2-6: new high speed USB device using ehci_hcd and address 2
usb 2-6: configuration #1 chosen from 1 choice
usb 2-6: New USB device found, idVendor=5986, idProduct=0303
usb 2-6: New USB device strings: Mfr=0, Product=1, SerialNumber=0
usb 2-6: Product: BisonCam, NB Pro
Linux video capture interface: v2.00
uvcvideo: Found UVC 1.00 device BisonCam, NB Pro (5986:0303)
uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround.
input: BisonCam, NB Pro as /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.0/input/input9
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
uvcvideo: UVC non compliance - GET_MIN/MAX(PROBE) incorrectly supported. Enabling workaround.
uvcvideo: device BisonCam, NB Pro requested null bandwidth, defaulting to lowest.
uvcvideo: device BisonCam, NB Pro requested null bandwidth, defaulting to lowest.
uvcvideo: device BisonCam, NB Pro requested null bandwidth, defaulting to lowest.
uvcvideo: device BisonCam, NB Pro requested null bandwidth, defaulting to lowest.

Strangely lsusb gives:

Bus 002 Device 004: ID 5986:0303 Acer, Inc

[edit] Running Temp

Great TIP using fn and 1 to turn on the fans to full power. At the moment I've not managed to get the CPUs over 60 deg C they sit around 40 most of the time and thats even whilst I'm compiling CCTBX on the quads. I have noticed a dmesg saying that the sensors are reporting "relative temperatures"? Need to investigate.

[edit] Webcam driver (Ali m5602)

The ALI m5602 web-camera now works perfectly with the new in-kernel driver: gspca_m5602. I believe it's been in there since 2.6.28.

Personal tools