Loading ...
Sorry, an error occurred while loading the content.

5817Re: [LinkStation_General] Stock v2.6 Kernel on a Linkstation HS : Working!

Expand Messages
  • David Yip
    Jan 30, 2007
    • 0 Attachment
      Hi Guennadi,

      Another success - thanks.

      Actually putting the "rtc-rs5c372.probe=0,0x32" actually seems to be working now.

      I recompiled u-boot and reflashed it and now I have

      i2c /dev entries driver
      rtc-rs5c372 0-0032: assuming rs5c372b
      rtc-rs5c372 0-0032: rs5c372b found, 24hr, driver version 0.4
      rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
      TCP cubic registered
      NET: Registered protocol family 1
      NET: Registered protocol family 17
      rtc-rs5c372 0-0032: setting the system clock to 2007-01-30 19:14:10 (1170184450)

      And kernel messages through nc

      So, everything is working fine on the Linkstation - now I have to try it on the Kurobox!! (which is quite strange, since I use exactly the same config file for uboot on the kurobox!!!!)

      Thanks for all of your help


      Guennadi Liakhovetski wrote:

      On Mon, 29 Jan 2007, David Yip wrote:

      > I believe that under v2.6.19 the hwclock is working
      > LinkStation: /sys/devices# hwclock
      > Mon Jan 29 12:00:23 2007 -0.954070 seconds
      > LinkStation: /sys/devices# find . -print | grep i2
      > ./platform/fsl- i2c.1/i2c- 0/0-0032
      > ./platform/fsl- i2c.1/i2c- 0/0-0032/ name

      Yep, that's fine and the address is the same. Have no clue why it should
      not work under 2.6.20... You ARE absolutely sure that if you specify
      "rtc-rs5c372. probe=0,0x32" your kernel hangs on both KuroboxHG and LS
      HS?... Can you send the same "find" output from a 2.6.20 on 1 of the 2
      NASs without that command line option? Well, I could suggest 2 ways to
      debug it:

      1. boot as normal one of your 2 systems with 2.6.20 and do "i2cdetect 0
      0x30 0x3f". i2cdetect is in lm-sensors package.

      2. Compile rtc-rs5c372 as a module and (after issuing "sync" 3 times:-))
      and while logging with netcat do "modprobe rtc-rs5x372 probe=0,0x32"

      Hm, something rings the bell... I think, they changed the register access
      to rs5c372 to "method 3" with 2.6.20... But that works on my and some
      other systems...

      Guennadi Liakhovetski

    • Show all 16 messages in this topic