DSM-G600, DNS-3xx and NSA-220 Hack Forum

mig · 2010-02-16 10:59:15

I have followed Martin Michlmayr's Debian install guide on a DNS-323 (B1), the installation went fine. [great work ]

I then applied pseudonym404's kernel and fan/led/button daemon from http://dns323.randomhacking.net

The dns323d script didn't seem to work, and when I start it at the command line, I get:

Code:

styx:/# /etc/init.d/dns323d  start
Starting DNS323 fan, button and led control: dns323derror: couldn't open temperature input "/sys/class/i2c-adapter/i2c-0/0-0048/temp1_input"
.

inspection of /sys/class/i2c-adapter/i2c-0/0-0048/ shows no 'temp1_input':

Code:

styx:/# ls -la /sys/class/i2c-adapter/i2c-0/0-0048/
total 0
drwxr-xr-x 2 root root    0 1969-12-31 16:00 .
drwxr-xr-x 6 root root    0 1969-12-31 16:00 ..
-r--r--r-- 1 root root 4096 2010-02-16 00:29 modalias
-r--r--r-- 1 root root 4096 2010-02-16 00:29 name
lrwxrwxrwx 1 root root    0 2010-02-16 00:29 subsystem -> ../../../../../bus/i2c
-rw-r--r-- 1 root root 4096 1969-12-31 16:00 uevent

I then looked at dmesg and found several errors:

Code:

styx:/# dmesg
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.32-dns323-orion5x (Debian 2.6.32-5) (bradshaw.laurie@gmail.com) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 Wed Feb 10 00:36:04 UTC 2010
[    0.000000] CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a0053177
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: D-Link DNS-323
[    0.000000] Clearing invalid memory bank 0KB@0xffffffff
[    0.000000] Clearing invalid memory bank 0KB@0xffffffff
[    0.000000] Clearing invalid memory bank 0KB@0xffffffff
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x41000403
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] On node 0 totalpages: 16384
[    0.000000] free_area_init_node: node 0, pgdat c0386a0c, node_mem_map c03ef000
[    0.000000]   Normal zone: 128 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 16256 pages, LIFO batch:3
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
[    0.000000] Kernel command line: root=/dev/ram console=ttyS0,115200 :::DB88FXX81:egiga0:none
[    0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)
[    0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Memory: 64MB = 64MB total
[    0.000000] Memory: 58732KB available (3196K code, 564K data, 120K init, 0K highmem)
[    0.000000] SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:64
[    0.000000] Console: colour dummy device 80x30
[    0.000241] Calibrating delay loop... 332.59 BogoMIPS (lpj=1662976)
[    0.220163] Security Framework initialized
[    0.220204] SELinux:  Disabled at boot.
[    0.220264] Mount-cache hash table entries: 512
[    0.220886] Initializing cgroup subsys ns
[    0.220916] Initializing cgroup subsys cpuacct
[    0.220940] Initializing cgroup subsys devices
[    0.220963] Initializing cgroup subsys freezer
[    0.220986] Initializing cgroup subsys net_cls
[    0.221081] CPU: Testing write buffer coherency: ok
[    0.222617] devtmpfs: initialized
[    0.225693] regulator: core version 0.5
[    0.226139] NET: Registered protocol family 16
[    0.227219] Orion ID: MV88F5182-A2. TCLK=166666667.
[    0.228024] DNS323: Found ethernet MAC address: 00:1c:f0:a5:1f:51.
[    0.232700] bio: create slab <bio-0> at 0
[    0.233456] vgaarb: loaded
[    0.234742] Switching to clocksource orion_clocksource
[    0.245443] NET: Registered protocol family 2
[    0.245984] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.247792] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[    0.247904] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[    0.247971] TCP: Hash tables configured (established 2048 bind 2048)
[    0.247997] TCP reno registered
[    0.248416] NET: Registered protocol family 1
[    0.248866] Unpacking initramfs...
[    0.812161] Freeing initrd memory: 2152K
[    0.812329] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.813016] audit: initializing netlink socket (disabled)
[    0.813096] type=2000 audit(0.800:1): initialized
[    0.832021] VFS: Disk quotas dquot_6.5.2
[    0.832718] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.833005] msgmni has been set to 119
[    0.834721] alg: No test for stdrng (krng)
[    0.835102] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    0.835137] io scheduler noop registered
[    0.835158] io scheduler anticipatory registered
[    0.835180] io scheduler deadline registered
[    0.835763] io scheduler cfq registered (default)
[    0.852650] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.853763] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3) is a 16550A
[    1.194844] console [ttyS0] enabled
[    1.199317] physmap platform flash device: 00800000 at f4000000
[    1.205602] physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank
[    1.212053]  Amd/Fujitsu Extended Query Table at 0x0040
[    1.217363] number of CFI chips: 1
[    1.220768] cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
[    1.275558] RedBoot partition parsing not available
[    1.280434] Using physmap partition information
[    1.285022] Creating 5 MTD partitions on "physmap-flash.0":
[    1.290598] 0x000000000000-0x000000010000 : "MTD1"
[    1.296847] 0x000000010000-0x000000020000 : "MTD2"
[    1.302815] 0x000000020000-0x0000001a0000 : "Linux Kernel"
[    1.309655] 0x0000001a0000-0x0000007d0000 : "File System"
[    1.316406] 0x0000007d0000-0x000000800000 : "u-boot"
[    1.323417] mice: PS/2 mouse device common for all mice
[    1.329722] i2c /dev entries driver
[    1.334126] rtc-m41t80 0-0068: chip found, driver version 0.05
[    1.340477] rtc-m41t80 0-0068: rtc core: registered m41t80 as rtc0
[    1.351750] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x68, flags: 0x0
[    1.361029] rtc-m41t80 0-0068: Can't clear HT bit
[    1.366048] rtc-m41t80: probe of 0-0068 failed with error -5
[    1.372354] Registered led device: power:blue
[    1.376929] Registered led device: right:amber
[    1.381520] Registered led device: left:amber
[    1.388864] TCP cubic registered
[    1.392101] NET: Registered protocol family 17
[    1.396634] VFP support v0.3: not present
[    1.401473] registered taskstats version 1
[    1.405818] /home/laurie/software/dns323/newkernel/linux-2.6-2.6.32/debian/build/source_armel_none/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.419776] Freeing init memory: 120K
[    1.985445] SCSI subsystem initialized
[    2.225555] libata version 3.00 loaded.
[    2.276972] sata_mv sata_mv.0: version 1.28
[    2.282160] sata_mv sata_mv.0: slots 32 ports 2
[    2.288297] scsi0 : sata_mv
[    2.291872] scsi1 : sata_mv
[    2.295102] ata1: SATA max UDMA/133 irq 29
[    2.299199] ata2: SATA max UDMA/133 irq 29
[    6.884872] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    7.004932] ata1.00: ATA-7: ST380815AS, 3.AAD, max UDMA/133
[    7.010508] ata1.00: 156301488 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    7.115035] ata1.00: configured for UDMA/133
[    7.120016] scsi 0:0:0:0: Direct-Access     ATA      ST380815AS       3.AA PQ: 0 ANSI: 5
[    7.474866] ata2: SATA link down (SStatus 0 SControl 300)
[    9.025322] sd 0:0:0:0: [sda] 156301488 512-byte logical blocks: (80.0 GB/74.5 GiB)
[    9.115533] sd 0:0:0:0: [sda] Write Protect is off
[    9.120336] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    9.173332] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    9.265442]  sda: sda1 sda2 sda3 < sda5 >
[    9.351883] sd 0:0:0:0: [sda] Attached SCSI disk
[   10.307512] kjournald starting.  Commit interval 5 seconds
[   10.313047] EXT3-fs: mounted filesystem with ordered data mode.
[   13.810403] udevd version 125 started
[   23.274541] usbcore: registered new interface driver usbfs
[   23.309191] usbcore: registered new interface driver hub
[   23.328383] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[   23.350930] usbcore: registered new device driver usb
[   23.382748] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x48, flags: 0x0
[   23.392163] lm75: probe of 0-0048 failed with error -5
[   23.416440] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x49, flags: 0x0
[   23.429040] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x4a, flags: 0x0
[   23.441613] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x4b, flags: 0x0
[   23.453917] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x4c, flags: 0x0
[   23.465972] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x4d, flags: 0x0
[   23.477926] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x4e, flags: 0x0
[   23.557680] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x4f, flags: 0x0
[   23.729522] MV-643xx 10/100/1000 ethernet driver version 1.4
[   23.780986] mv643xx_eth smi: probed
[   23.806881] net eth0: port 0 with MAC address 00:1c:f0:a5:1f:51
[   23.860462] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   23.905082] orion-ehci orion-ehci.0: Marvell Orion EHCI
[   23.910445] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[   23.994980] orion-ehci orion-ehci.0: irq 17, io mem 0xf1050000
[   24.014945] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   24.021014] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   24.027873] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   24.035137] usb usb1: Product: Marvell Orion EHCI
[   24.039842] usb usb1: Manufacturer: Linux 2.6.32-dns323-orion5x ehci_hcd
[   24.046578] usb usb1: SerialNumber: orion-ehci.0
[   24.103549] usb usb1: configuration #1 chosen from 1 choice
[   24.116515] hub 1-0:1.0: USB hub found
[   24.120359] hub 1-0:1.0: 1 port detected
[   26.863637] Adding 176672k swap on /dev/sda5.  Priority:-1 extents:1 across:176672k
[   27.829374] EXT3 FS on sda2, internal journal
[   29.459276] loop: module loaded
[   37.083922] eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[   38.461885] NET: Registered protocol family 10
[   38.479057] lo: Disabled Privacy Extensions
[   44.180997] RPC: Registered udp transport module.
[   44.185804] RPC: Registered tcp transport module.
[   44.190506] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   44.538275] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   48.504826] eth0: no IPv6 routers present
[   48.576673] NET: Registered protocol family 5
[   48.596147] warning: `ntpd' uses 32-bit capabilities (legacy support in use)
[  189.095851] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x3e, flags: 0x0
[  189.108338] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x3e, flags: 0x0
[  189.119577] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x3e, flags: 0x0
[  189.131140] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x3e, flags: 0x0
[  213.126468] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x3e, flags: 0x0
[  213.139311] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x3e, flags: 0x0
[  213.150418] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x3e, flags: 0x0
[  213.163003] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x3e, flags: 0x0

I see the lm75: probe failed, is this an indication of a hardware problem? Or am I missing something with
debian setup? Any help or insight would be appreciated.

The system is functioning, I have a blinking power button and the fan never spins, but the network and HD leds
operate correctly.

Last edited by mig (2010-02-16 11:00:07)

oxygen · 2010-02-17 23:17:31

there is no need for a third party kernel. the kernel in testing works fine (led and fan control). backport for lenny here: http://merkel.debian.org/~tbm/tmp/kerne … _armel.deb
in fact. there is not need for a additional deamon at all. all functions (fan need fancontrol daemon though) works out of the box in debian with a recent kernel.

Last edited by oxygen (2010-02-17 23:21:14)

mig · 2010-02-18 11:04:57

Thanks, oxygen. I loaded the kernel you posted and the power led stopped flashing.

Code:

styx:/# uname -a
Linux styx 2.6.32-trunk-orion5x #1 Fri Dec 18 21:46:04 UTC 2009 armv5tel GNU/Linux

The last two problems are lack of fan and power button off control. I still have many errors in my dmesg

Code:

styx:~# dmesg | grep -i error
[    1.335985] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x68, flags: 0x0
[    1.350192] rtc-m41t80: probe of 0-0068 failed with error -5
[   18.988711] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x48, flags: 0x0
[   18.998250] lm75: probe of 0-0048 failed with error -5
[   19.082171] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x49, flags: 0x0
[   19.092651] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x4a, flags: 0x0
[   19.103103] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x4b, flags: 0x0
[   19.113502] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x4c, flags: 0x0
[   19.123875] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x4d, flags: 0x0
[   19.134223] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x4e, flags: 0x0
[   19.144579] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x4f, flags: 0x0
[   29.663151] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x3e, flags: 0x0
[   29.673559] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x3e, flags: 0x0
[   29.683897] i2c i2c-0: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x3, status: 0x0, addr: 0x3e, flags: 0x0

and when I try to run pwmconfg I get:

Code:

styx:/# pwmconfig
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.

We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.

Found the following devices:
   hwmon0/device is g760a

Found the following PWM controls:
   hwmon0/device/pwm1

Giving the fans some time to reach full speed...
Found the following fan sensors:
   hwmon0/device/fan1_input     current speed: 0 ... skipping!

There are no working fan sensors, all readings are 0.
Make sure you have a 3-wire fan connected.
You may also need to increase the fan divisors.
See doc/fan-divisors for more information.

How should I be able to control the fan? I'd be happy if I could just get it to turn on
at any speed.

Last edited by mig (2010-02-18 11:10:20)

oxygen · 2010-02-18 11:26:38

wierd. i dont have such errors in my dmesg.

try the following /etc/fancontrol:

Code:

# Configuration file generated by pwmconfig, changes will be lost
INTERVAL=120
FCTEMPS=hwmon1/device/pwm1=hwmon0/device/temp1_input
FCFANS=hwmon1/device/pwm1=hwmon1/device/fan1_input
MINTEMP=hwmon1/device/pwm1=42
MAXTEMP=hwmon1/device/pwm1=56
MINSTART=hwmon1/device/pwm1=50
MINSTOP=hwmon1/device/pwm1=2
MAXPWM=hwmon1/device/pwm1=230

(you might need to exchange hwmon0 and hwmon1. for some reason it changes on my machine sometimes.

mig · 2010-02-18 19:02:52

Yeah, weird

I don't have a /etc/fancontrol file, I don't think the pwmconfig program created it
because pwmconfig could not find any fan sensors.

This is looking like a hardware failure to me, since dmesg reports it can not probe the
temp sensor 'lm75' or real time clock 'rtc-m41t80'. I have ntp running and this
DNS-323 does keep good time.

oxygen · 2010-02-18 19:57:09

mig wrote:
This is looking like a hardware failure to me, since dmesg reports it can not probe the
temp sensor 'lm75' or real time clock 'rtc-m41t80'. I have ntp running and this
DNS-323 does keep good time.

could be. the sensors is mv64xxx_i2c not lm75. but it reports erros, too that i dont have in my dmesg.

Kai · 2010-02-19 13:17:09

Odd.. looks like a hardware failure. Did you have temperature control and fan running before going native debian?

I'm running the same config and kernel and never seen issues like that.

Here is how the i2c device tree looks at my device (a CH3SNAS which is a revision B to my knowledge)

Code:

/sys/class/i2c-adapter/i2c-0# tree
.
|-- 0-003e
|   |-- driver -> ../../../../../bus/i2c/drivers/g760a
|   |-- fan1_alarm
|   |-- fan1_input
|   |-- hwmon
|   |   `-- hwmon0
|   |       |-- device -> ../../../0-003e
|   |       |-- subsystem -> ../../../../../../../class/hwmon
|   |       `-- uevent
|   |-- modalias
|   |-- name
|   |-- pwm1
|   |-- subsystem -> ../../../../../bus/i2c
|   `-- uevent
|-- 0-0048
|   |-- driver -> ../../../../../bus/i2c/drivers/lm75
|   |-- hwmon
|   |   `-- hwmon1
|   |       |-- device -> ../../../0-0048
|   |       |-- subsystem -> ../../../../../../../class/hwmon
|   |       `-- uevent
|   |-- modalias
|   |-- name
|   |-- subsystem -> ../../../../../bus/i2c
|   |-- temp1_input
|   |-- temp1_max
|   |-- temp1_max_hyst
|   `-- uevent
|-- 0-0068
|   |-- driver -> ../../../../../bus/i2c/drivers/rtc-m41t80
|   |-- flags
|   |-- modalias
|   |-- name
|   |-- rtc
|   |   `-- rtc0
|   |       |-- date
|   |       |-- dev
|   |       |-- device -> ../../../0-0068
|   |       |-- hctosys
|   |       |-- max_user_freq
|   |       |-- name
|   |       |-- since_epoch
|   |       |-- subsystem -> ../../../../../../../class/rtc
|   |       |-- time
|   |       `-- uevent
|   |-- sqwfreq
|   |-- subsystem -> ../../../../../bus/i2c
|   `-- uevent
|-- delete_device
|-- device -> ../../mv64xxx_i2c.0
|-- i2c-dev
|   `-- i2c-0
|       |-- dev
|       |-- device -> ../../../i2c-0
|       |-- name
|       |-- subsystem -> ../../../../../../class/i2c-dev
|       `-- uevent
|-- name
|-- new_device
|-- subsystem -> ../../../../bus/i2c
`-- uevent

You may want to ask lm sensor or kernel driver maintainers for further means of debugging this.

mig · 2010-02-22 07:44:02

Kai wrote:
Odd.. looks like a hardware failure. Did you have temperature control and fan running before going native debian?

I'm really not sure, this is not my primary DNS-323. I just used it as a dev box to try new stuff.
It was running (fine I think? I never checked for temps or fan) before I flashed Debian.
The i2c device tree sure looks incomplete:

Code:

mig@styx:/sys/class/i2c-adapter/i2c-0$ tree
.
|-- 0-003e
|   |-- driver -> ../../../../../bus/i2c/drivers/g760a
|   |-- fan1_alarm
|   |-- fan1_input
|   |-- hwmon
|   |   `-- hwmon0
|   |       |-- device -> ../../../0-003e
|   |       |-- subsystem -> ../../../../../../../class/hwmon
|   |       `-- uevent
|   |-- modalias
|   |-- name
|   |-- pwm1
|   |-- subsystem -> ../../../../../bus/i2c
|   `-- uevent
|-- 0-0048
|   |-- modalias
|   |-- name
|   |-- subsystem -> ../../../../../bus/i2c
|   `-- uevent
|-- 0-0068
|   |-- modalias
|   |-- name
|   |-- subsystem -> ../../../../../bus/i2c
|   `-- uevent
|-- delete_device
|-- device -> ../../mv64xxx_i2c.0
|-- i2c-dev
|   `-- i2c-0
|       |-- dev
|       |-- device -> ../../../i2c-0
|       |-- name
|       |-- subsystem -> ../../../../../../class/i2c-dev
|       `-- uevent
|-- name
|-- new_device
|-- subsystem -> ../../../../bus/i2c
`-- uevent

Denny · 2010-03-21 02:40:48

hi,

same problem here with 2.6.33.1. The fan stops after the kernel starts. I can't change the value from the fan. It keeps between 0-18 and he says, the fan is running at 2073 RPM, what is wrong.

Code:

nas:~# sensors
g760a-i2c-0-3e
Adapter: mv64xxx_i2c adapter
fan1:       2073 RPM  ALARM

lm75-i2c-0-48
Adapter: mv64xxx_i2c adapter
temp1:       +48.5 C  (high = +80.0 C, hyst = +75.0 C)

Code:

nas:~# cat /sys/class/hwmon/hwmon0/device/pwm1
18

echo 0 >  /sys/class/hwmon/hwmon0/device/pwm1
nas:~# cat /sys/class/hwmon/hwmon0/device/pwm1
18


echo 255 >  /sys/class/hwmon/hwmon0/device/pwm1
nas:~# cat /sys/class/hwmon/hwmon0/device/pwm1
18

i can't the fan disabled, 'cause the sensor goes over 50° ... thats to hot.

any suggestions?

Last edited by Denny (2010-03-21 02:54:24)

DSM-G600, DNS-3xx and NSA-220 Hack Forum

Announcement

#1 2010-02-16 10:59:15

Native Debian issues (B1)

Code:

Code:

Code:

#2 2010-02-17 23:17:31

Re: Native Debian issues (B1)

#3 2010-02-18 11:04:57

Re: Native Debian issues (B1)

Code:

Code:

Code:

#4 2010-02-18 11:26:38

Re: Native Debian issues (B1)

Code:

#5 2010-02-18 19:02:52

Re: Native Debian issues (B1)

#6 2010-02-18 19:57:09

Re: Native Debian issues (B1)

mig wrote:

#7 2010-02-19 13:17:09

Re: Native Debian issues (B1)

Code:

#8 2010-02-22 07:44:02

Re: Native Debian issues (B1)

Kai wrote:

Code:

#9 2010-03-21 02:40:48

Re: Native Debian issues (B1)

Code:

Code:

Board footer