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

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

Expand Messages
  • Guennadi Liakhovetski
    ... Ok, I am not sure what a Linkstation HS exactly is. The stock kernel / bootloader configuration has been tested so far on KuroBox HG and HD. Is the LS HS
    Message 1 of 16 , Jan 28, 2007
    • 0 Attachment
      On Sat, 27 Jan 2007, daveyip wrote:

      > I have a Linkstation HS that I have installed u-boot on according to
      >
      > http://www.kurobox.com/mwiki/index.php/Kurobox_support_in_stock_2.6_kernels
      >
      > Over at the Kurobox wiki
      >
      > I have everything installed and a 2.6.20-rc5 kernel booting over nc
      >
      > But have run up against
      >
      > linkstation: disarming the AVR watchdog:
      > VFS: Cannot open root device "sda1" or unknown-block(0,0)
      > Please append a correct "root=" boot option
      > Kernel panic - not syncing: VFS: Unable to mount root fs on
      > unknown-block(0,0)
      >
      > I have used the stock .config file for the linkstation out of the
      > kernel that has IDE disabled and PATA enabled. My fstab looks like

      Ok, I am not sure what a Linkstation HS exactly is. The stock kernel /
      bootloader configuration has been tested so far on KuroBox HG and HD. Is
      the LS HS hardware identical to kuro HG? Looks like there might be a
      slight difference. Maybe you'll need a special device tree. To clarify
      that, please post your complete dmesg captured with your nc. Would also be
      good to see dmesg from a running kernel on such a system, as well as
      output from lspci -vv, /proc/interrupts.

      > # /etc/fstab: static file system information.
      > #
      > # <file system> <mount point> <type> <options> <dump>
      > <pass>
      > /dev/sda1 / ext3 defaults,noatime,errors=remount-ro
      > 0 0
      > proc /proc proc defaults
      > 0 0
      > none /dev/pts devpts gid=5,mode=20
      > 0 0
      > /dev/sda2 swap swap defaults
      > 0 0
      > /dev/sda3 /datafiles ext3 defaults,noatime
      > 0 0

      Correct, but you haven't got that far - your kernel cannot mount the root
      as specified on the command line, i.e., your /etc/fstab has not been read
      yet:-)

      > My u-boot config for CONFIG_BOOTARGS looks like
      >
      > #define CONFIG_BOOTARGS "root=/dev/sda1
      > netconsole=6666@192.168.0.13/,@192.168.0.7/00:11:D8:1A:78:21"
      >
      > (Incidently, the instructions say to have rtc-rs5c372.probe=0,0x32 in
      > there to, but I found that this causes no kernel messages to be
      > displayed in nc)

      This also hints at some differences in the hardware.

      Thanks
      Guennadi
      ---
      Guennadi Liakhovetski
    • David Yip
      Hi, A Linkstation HS is very similiar to a Kurobox HG, I think, from what I can gather from http://www.linkstationwiki.net/index.php?title=Category:HS which
      Message 2 of 16 , Jan 28, 2007
      • 0 Attachment
        Hi,

        A Linkstation HS is very similiar to a Kurobox HG, I think, from what I can gather from

        http://www.linkstationwiki.net/index.php?title=Category:HS
        which says that a HS is like a HD-HGLAN and from
        http://www.linkstationwiki.net/index.php?title=LS_Hardware_and_Software_information
        which says a HD-HGLAN is like a Kurobox HG

        I actually, I have a Kurobox HG which I have followed  the instructions for and an running a stock v2.6.20-rc5 kernel.

        So, that I why I chose to buy a HS, following your excellent advice on getting  my Kurobox running.

        (An side, I really like Buffalo products - I have a Terastation as well!)

        Ok, I am not sure what a Linkstation HS exactly is. The stock kernel / 
        bootloader configuration has been tested so far on KuroBox HG and HD. Is 
        the LS HS hardware identical to kuro HG? Looks like there might be a 
        slight difference. Maybe you'll need a special device tree. To clarify 
        that, please post your complete dmesg captured with your nc. Would also be 
        good to see dmesg from a running kernel on such a system, as well as 
        output from lspci -vv, /proc/interrupts.
          
        --------------------------------------------dmesg from nc -----------------------------
        U-Boot 1.2.0-g2817d7ce-dirty (Jan 27 2007 - 13:03:32) LinkStation HG / KuroBox H
        G
        stdin :   nc
        stdout:   nc
        stderr:   nc
        IDE:   Bus 0: OK
          Device 0: Model: SAMSUNG HD300LD Firm: WK100-12 Ser#: S0A4J1LLA01108
                    Type: Hard Disk
                    Supports 48-bit addressing
                    Capacity: 286168.1 MB = 279.4 GB (586072368 x 512)
        Boot in 01 seconds ('s' to stop)...
        Loading 0:1:boot/vmlinux.UBoot

        1562762 bytes read

        2373 bytes read
        ## Booting image at 00800000 ...
           Image Name:   Linux-2.6.20-rc5-kuroboxHG
           Image Type:   PowerPC Linux Kernel Image (gzip compressed)
           Data Size:    1562698 Bytes =  1.5 MB
           Load Address: 00000000
           Entry Point:  00000000
           Verifying Checksum ... OK
           Uncompressing Kernel Image ... OK
           Booting using flat device tree at 0x7f0000
        Using Buffalo Linkstation machine description
        Linux version 2.6.20-rc5-kuroboxHG (root@LinkStation) (gcc version 3.3.5 (Debian
         1:3.3.5-13)) #1 Sat Jan 27 22:00:25 GMT 2007
        Adding PCI host bridge /soc10x/pci@fec00000
        BUFFALO Network Attached Storage Series
        (C) 2002-2005 BUFFALO INC.
        Zone PFN ranges:
          DMA             0 ->    32768
          Normal      32768 ->    32768
        early_node_map[1] active PFN ranges
            0:        0 ->    32768
        Built 1 zonelists.  Total pages: 32512
        Kernel command line: root=/dev/sda1 netconsole=6666@192.168.0.13/,@192.168.0.7/0
        0:11:D8:1A:78:21
        netconsole: local port 6666
        netconsole: local IP 192.168.0.13
        netconsole: interface eth0
        netconsole: remote port 6666
        netconsole: remote IP 192.168.0.7
        netconsole: remote ethernet address 00:11:d8:1a:78:21
        mpic: Setting up MPIC " EPIC     " version 1.2 at 80040000, max 1 CPUs
        mpic: ISU size: 4, shift: 2, mask: 3
        mpic: Initializing for 12 sources
        PID hash table entries: 512 (order: 9, 2048 bytes)
        Console: colour dummy device 80x25
        Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
        Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
        Memory: 126432k/131072k available (3060k kernel code, 4496k reserved, 116k data,
         101k bss, 144k init)
        Mount-cache hash table entries: 512
        NET: Registered protocol family 16
        PCI: Probing PCI hardware
        PCI: Cannot allocate resource region 1 of device 0000:00:00.0
        SCSI subsystem initialized
        usbcore: registered new interface driver usbfs
        usbcore: registered new interface driver hub
        usbcore: registered new device driver usb
        NET: Registered protocol family 2
        IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
        TCP established hash table entries: 4096 (order: 2, 16384 bytes)
        TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
        TCP: Hash tables configured (established 4096 bind 2048)
        TCP reno registered
        io scheduler noop registered
        io scheduler anticipatory registered (default)
        io scheduler deadline registered
        io scheduler cfq registered
        Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
        serial8250.0: ttyS0 at MMIO 0x80004500 (irq = 16) is a 16550A
        serial8250.0: ttyS1 at MMIO 0x80004600 (irq = 17) is a 16550A
        RAMDISK driver initialized: 2 RAM disks of 8192K size 1024 blocksize
        loop: loaded (max 8 devices)
        r8169 Gigabit Ethernet driver 2.2LK loaded
        r8169 0000:00:0b.0: PowerManagement capability not found.
        eth0: RTL8169s/8110s at 0xc9004c00, 00:0d:0b:b7:c5:b9, IRQ 19
        usbcore: registered new interface driver zd1201
        netconsole: device eth0 not up yet, forcing it
        r8169: eth0: link down
        r8169: eth0: link up
        netconsole: network logging started
        physmap platform flash device: 00400000 at ffc00000
        physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank
         Amd/Fujitsu Extended Query Table at 0x0040
        number of CFI chips: 1
        cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
        cmdlinepart partition parsing not available
        RedBoot partition parsing not available
        Using physmap partition information
        Creating 6 MTD partitions on "physmap-flash.0":
        0x00000000-0x00300000 : "mtd_firmimg"
        0x00300000-0x00370000 : "mtd_bootcode"
        0x00370000-0x00380000 : "mtd_status"
        0x00380000-0x00400000 : "mtd_conf"
        0x00000000-0x00400000 : "mtd_allflash"
        0x00310000-0x00400000 : "mtd_data"
        usbmon: debugfs is not available
        ehci_hcd 0000:00:0e.2: EHCI Host Controller
        ehci_hcd 0000:00:0e.2: new USB bus registered, assigned bus number 1
        ehci_hcd 0000:00:0e.2: irq 21, io mem 0xbfffcf00
        ehci_hcd 0000:00:0e.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
        usb usb1: configuration #1 chosen from 1 choice
        hub 1-0:1.0: USB hub found
        hub 1-0:1.0: 5 ports detected
        ohci_hcd 0000:00:0e.0: OHCI Host Controller
        ohci_hcd 0000:00:0e.0: new USB bus registered, assigned bus number 2
        ohci_hcd 0000:00:0e.0: irq 21, io mem 0xbfffe000
        usb usb2: configuration #1 chosen from 1 choice
        hub 2-0:1.0: USB hub found
        hub 2-0:1.0: 3 ports detected
        ohci_hcd 0000:00:0e.1: OHCI Host Controller
        ohci_hcd 0000:00:0e.1: new USB bus registered, assigned bus number 3
        ohci_hcd 0000:00:0e.1: irq 21, io mem 0xbfffd000
        usb usb3: configuration #1 chosen from 1 choice
        hub 3-0:1.0: USB hub found
        hub 3-0:1.0: 2 ports detected
        usbcore: registered new interface driver usblp
        drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
        usbcore: registered new interface driver usbserial
        drivers/usb/serial/usb-serial.c: USB Serial Driver core
        drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Seri
        al Device
        usbcore: registered new interface driver ftdi_sio
        drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
        mice: PS/2 mouse device common for all mice
        i2c /dev entries driver
        TCP cubic registered
        NET: Registered protocol family 1
        NET: Registered protocol family 17
        drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
        linkstation: disarming the AVR watchdog:
        Root-NFS: No NFS server available, giving up.
        VFS: Unable to mount root fs via NFS, trying floppy.
        VFS: Cannot open root device "sda1" or unknown-block(2,0)
        Please append a correct "root=" boot option
        Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
         <0>Rebooting in 180 seconds..

        ---------------------------------dmesg from running a 2.6.19.2 kernel via loader.o----------
        KERNELBASE=c0000000 (r6=71c371c r7=71c372a) r3=0 (r4=0 r5=0)
        Linux version 2.6.19.2-kuroboxHG (root@ls) (gcc version 3.3.5 (Debian 1:3.3.5-13)) #9 Fri Jan 12 07:52:20 CET 2007
        Early serial console at MMIO 0x80004600 (options '57600n8')
        BUFFALO Network Attached Storage Series
        (C) 2002-2005 BUFFALO INC.
        Entering add_active_range(0, 0, 32768) 0 entries of 256 used
        Zone PFN ranges:
          DMA             0 ->    32768
          Normal      32768 ->    32768
        early_node_map[1] active PFN ranges
            0:        0 ->    32768
        On node 0 totalpages: 32768
          DMA zone: 256 pages used for memmap
          DMA zone: 0 pages reserved
          DMA zone: 32512 pages, LIFO batch:7
          Normal zone: 0 pages used for memmap
        Built 1 zonelists.  Total pages: 32512
        Kernel command line: root=/dev/hda1
        OpenPIC Version 1.2 (1 CPUs and 11 IRQ sources) at 80040000
        PID hash table entries: 512 (order: 9, 2048 bytes)
        decrementer frequency = 32.522240 MHz
        Console: colour dummy device 80x25
        Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
        Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
        Memory: 126336k available (2432k kernel code, 1008k data, 124k init, 0k highmem)
        Calibrating delay loop... 173.05 BogoMIPS (lpj=346112)
        Security Framework v1.0.0 initialized
        Mount-cache hash table entries: 512
        NET: Registered protocol family 16
        PCI: Probing PCI hardware
        PCI: Cannot allocate resource region 1 of device 0000:00:00.0
        Registering openpic with sysfs...
        SCSI subsystem initialized
        usbcore: registered new interface driver usbfs
        usbcore: registered new interface driver hub
        usbcore: registered new device driver usb
        NET: Registered protocol family 2
        IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
        TCP established hash table entries: 4096 (order: 2, 16384 bytes)
        TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
        TCP: Hash tables configured (established 4096 bind 2048)
        TCP reno registered
        VFS: Disk quotas dquot_6.5.1
        Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
        NTFS driver 2.1.27 [Flags: R/W].
        io scheduler noop registered
        io scheduler anticipatory registered (default)
        io scheduler deadline registered
        io scheduler cfq registered
        I2C: rs5c372 RTC driver successfully loaded
        Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
        serial8250.0: ttyS0 at MMIO 0x80004500 (irq = 25) is a 16550A
        serial8250.1: ttyS1 at MMIO 0x80004600 (irq = 26) is a 16550A
        RAMDISK driver initialized: 2 RAM disks of 8192K size 1024 blocksize
        loop: loaded (max 8 devices)
        tun: Universal TUN/TAP device driver, 1.6
        tun: (C) 1999-2004 Max Krasnyansky <maxk@...>
        r8169 Gigabit Ethernet driver 2.2LK loaded
        r8169 0000:00:0b.0: PowerManagement capability not found.
        eth0: RTL8169s/8110s at 0xc9000f00, 00:0d:0b:b7:c5:b9, IRQ 16
        eth0: 100Mbps Half-duplex operation.
        Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
        ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
        IT8212: IDE controller at PCI slot 0000:00:0c.0
        IT8212: chipset revision 19
        it821x: controller in pass through mode.
        IT8212: 100% native mode on irq 17
            ide0: BM-DMA at 0xbffed0-0xbffed7, BIOS settings: hda:DMA, hdb:DMA
            ide1: BM-DMA at 0xbffed8-0xbffedf, BIOS settings: hdc:DMA, hdd:DMA
        Probing IDE interface ide0...
        hda: SAMSUNG HD300LD, ATA DISK drive
        ide0 at 0xbffef8-0xbffeff,0xbffef6 on irq 17
        Probing IDE interface ide1...
        hda: max request size: 512KiB
        hda: 586072368 sectors (300069 MB) w/8192KiB Cache, CHS=36481/255/63, UDMA(100)
        hda: cache flushes supported
         hda: hda1 hda2 hda3
        physmap platform flash device: 00400000 at ffc00000
        physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank
         Amd/Fujitsu Extended Query Table at 0x0040
        number of CFI chips: 1
        cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
        cmdlinepart partition parsing not available
        RedBoot partition parsing not available
        Using physmap partition information
        Creating 5 MTD partitions on "physmap-flash.0":
        0x00000000-0x00300000 : "mtd_firmimg"
        0x00300000-0x00370000 : "mtd_bootcode"
        0x00370000-0x00380000 : "mtd_status"
        0x00380000-0x00400000 : "mtd_conf"
        0x00000000-0x00400000 : "mtd_allflash"
        usbmon: debugfs is not available
        ehci_hcd 0000:00:0e.2: EHCI Host Controller
        ehci_hcd 0000:00:0e.2: new USB bus registered, assigned bus number 1
        ehci_hcd 0000:00:0e.2: irq 19, io mem 0xbfffcf00
        ehci_hcd 0000:00:0e.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
        usb usb1: configuration #1 chosen from 1 choice
        hub 1-0:1.0: USB hub found
        hub 1-0:1.0: 5 ports detected
        ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
        ohci_hcd 0000:00:0e.0: OHCI Host Controller
        ohci_hcd 0000:00:0e.0: new USB bus registered, assigned bus number 2
        ohci_hcd 0000:00:0e.0: irq 19, io mem 0xbfffe000
        usb usb2: configuration #1 chosen from 1 choice
        hub 2-0:1.0: USB hub found
        hub 2-0:1.0: 3 ports detected
        ohci_hcd 0000:00:0e.1: OHCI Host Controller
        ohci_hcd 0000:00:0e.1: new USB bus registered, assigned bus number 3
        ohci_hcd 0000:00:0e.1: irq 19, io mem 0xbfffd000
        usb usb3: configuration #1 chosen from 1 choice
        hub 3-0:1.0: USB hub found
        hub 3-0:1.0: 2 ports detected
        USB Universal Host Controller Interface driver v3.0
        usbcore: registered new interface driver usblp
        drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
        Initializing USB Mass Storage driver...
        usbcore: registered new interface driver usb-storage
        USB Mass Storage support registered.
        mice: PS/2 mouse device common for all mice
        i2c /dev entries driver
        TCP cubic registered
        NET: Registered protocol family 1
        NET: Registered protocol family 17
        NET: Registered protocol family 5
        Adding console on ttyS1 at MMIO 0x80004600 (options '57600n8')
        linkstation: disarming the AVR watchdog:
        kjournald starting.  Commit interval 5 seconds
        EXT3-fs: mounted filesystem with ordered data mode.
        VFS: Mounted root (ext3 filesystem) readonly.
        Freeing unused kernel memory: 124k init
        EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
        EXT3 FS on hda1, internal journal
        r8169: eth0: link up
        eth0: 1000Mbps Full-duplex operation.
        NET: Registered protocol family 10
        lo: Disabled Privacy Extensions
        eth0: no IPv6 routers present
        Installing knfsd (copyright (C) 1996 okir@...).
        NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
        NFSD: unable to find recovery directory /var/lib/nfs/v4recovery
        NFSD: starting 90-second grace period
        nfsd: last server has exited
        nfsd: unexporting all filesystems
        RPC: failed to contact portmap (errno -5).

        --------------------------------------------------------------------------------------------------------------------------

        LinkStation:~# lspci -v -v
        0000:00:00.0 Host bridge: Motorola MPC8245 [Unity] (rev 14)
                Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
                Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
                Latency: 32, Cache Line Size: 0x08 (32 bytes)
                Interrupt: pin A routed to IRQ 0
                Region 0: Memory at <unassigned> (32-bit, prefetchable)
                Region 2: Memory at <unassigned> (32-bit, prefetchable)

        0000:00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
                Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
                Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
                Latency: 128 (8000ns min, 16000ns max), Cache Line Size: 0x08 (32 bytes)
                Interrupt: pin A routed to IRQ 16
                Region 0: I/O ports at bfff00 [size=256]
                Region 1: Memory at bfffff00 (32-bit, non-prefetchable) [size=256]
                Capabilities: [dc] Power Management version 0
                        Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                        Status: D0 PME-Enable- DSel=0 DScale=0 PME-

        0000:00:0c.0 Unknown mass storage controller: Integrated Technology Express, Inc. IT/ITE8212 Dual channel ATA RAID controller (PCI version seems to be IT8212, embedded seems (rev 13)
                Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
                Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
                Latency: 128 (2000ns min, 2000ns max)
                Interrupt: pin A routed to IRQ 17
                Region 0: I/O ports at bffef8 [size=8]
                Region 1: I/O ports at bffef4 [size=4]
                Region 2: I/O ports at bffee8 [size=8]
                Region 3: I/O ports at bffee4 [size=4]
                Region 4: I/O ports at bffed0 [size=16]
                Capabilities: [80] Power Management version 2
                        Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                        Status: D0 PME-Enable- DSel=0 DScale=0 PME-

        0000:00:0e.0 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 [OHCI])
                Subsystem: NEC Corporation USB
                Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
                Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
                Latency: 128 (250ns min, 10500ns max), Cache Line Size: 0x08 (32 bytes)
                Interrupt: pin A routed to IRQ 19
                Region 0: Memory at bfffe000 (32-bit, non-prefetchable) [size=4K]
                Capabilities: [40] Power Management version 2
                        Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
                        Status: D0 PME-Enable- DSel=0 DScale=0 PME-

        0000:00:0e.1 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 [OHCI])
                Subsystem: NEC Corporation USB
                Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
                Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
                Latency: 128 (250ns min, 10500ns max), Cache Line Size: 0x08 (32 bytes)
                Interrupt: pin B routed to IRQ 19
                Region 0: Memory at bfffd000 (32-bit, non-prefetchable) [size=4K]
                Capabilities: [40] Power Management version 2
                        Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
                        Status: D0 PME-Enable- DSel=0 DScale=0 PME-

        0000:00:0e.2 USB Controller: NEC Corporation USB 2.0 (rev 04) (prog-if 20 [EHCI])
                Subsystem: NEC Corporation USB 2.0
                Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
                Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
                Latency: 128 (4000ns min, 8500ns max), Cache Line Size: 0x08 (32 bytes)
                Interrupt: pin C routed to IRQ 19
                Region 0: Memory at bfffcf00 (32-bit, non-prefetchable) [size=256]
                Capabilities: [40] Power Management version 2
                        Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
                        Status: D0 PME-Enable- DSel=0 DScale=0 PME-

        -----------------------------------------------------------------------------------------------------------------
        LinkStation:~# more /proc/interrupts
                   CPU0
         16:        447   OpenPIC   Level     eth0
         17:       1484   OpenPIC   Level     ide0
         19:          0   OpenPIC   Level     ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb
        3
         21:      12606   OpenPIC   Level     i2c-mpc
         25:         18   OpenPIC   Level     serial
         26:        228   OpenPIC   Level     serial
        BAD:         11

          
        My u-boot config for CONFIG_BOOTARGS looks like 
        
        #define CONFIG_BOOTARGS         "root=/dev/sda1
        netconsole=6666@192.168.0.13/,@192.168.0.7/00:11:D8:1A:78:21"
        
        (Incidently, the instructions say to have rtc-rs5c372.probe=0,0x32 in
        there to, but I found that this causes no kernel messages to be
        displayed in nc)
            
        This also hints at some differences in the hardware.
          
        Actually, on my Kurobox HG and with the "rtc-rs5c372.probe=0,0x32" I never got any kernel messages from nc

        Any help is appreciated

        Thanks,

        David
      • Guennadi Liakhovetski
        ... Good. Could you, please, confirm that adding IT821x was the only addition you needed to get it running? or just send me a diff or your complete .config.
        Message 3 of 16 , Jan 28, 2007
        • 0 Attachment
          On Sun, 28 Jan 2007, David Yip wrote:

          > >Auch, here. It's a different IDE controller. Please, enable ADDITIONALLY
          > >in your kernel configuration CONFIG_PATA_IT821X. And report if it works
          > >then. I'd include this option in the standard configuration too.
          >
          > Success - that did the trick.

          Good. Could you, please, confirm that adding IT821x was the only addition
          you needed to get it running? or just send me a diff or your complete
          .config.

          And the realtime clock... It should work on your HG because it does on
          mine. As for the LS HS, would be nice to find out what they need as RTC.
          Under your 2.6.19 you also have rs5c372 driver. Does hwclock work there?
          If it does, could you, please, look at what I2C address it is on your LS
          HS? Somewhere under /sys/devices/.../i2c-0/ there should be a file like
          0-0032, but the number will be different if you have it at a different
          address.

          Thanks
          Guennadi
          ---
          Guennadi Liakhovetski
        • David Yip
          Hi, Yes, adding the CONFIG_PATA_IT821X was all I did in addition to using your stock config file from arch/powerpc/configs/linkstation_defconfig (I added a
          Message 4 of 16 , Jan 28, 2007
          • 0 Attachment
            Hi,

            Yes, adding the CONFIG_PATA_IT821X was all I did in addition to using your stock config file from

            arch/powerpc/configs/linkstation_defconfig

            (I added a couple of USB stuff that I wanted)

            I shall have to look at the RTC issue a little bit later, I am just making tea and getting everyone off to bed.

            Cheers,

            David

            Guennadi Liakhovetski wrote:

            On Sun, 28 Jan 2007, David Yip wrote:

            > >Auch, here. It's a different IDE controller. Please, enable ADDITIONALLY
            > >in your kernel configuration CONFIG_PATA_ IT821X. And report if it works
            > >then. I'd include this option in the standard configuration too.
            >
            > Success - that did the trick.

            Good. Could you, please, confirm that adding IT821x was the only addition
            you needed to get it running? or just send me a diff or your complete
            .config.

            And the realtime clock... It should work on your HG because it does on
            mine. As for the LS HS, would be nice to find out what they need as RTC.
            Under your 2.6.19 you also have rs5c372 driver. Does hwclock work there?
            If it does, could you, please, look at what I2C address it is on your LS
            HS? Somewhere under /sys/devices/ .../i2c-0/ there should be a file like
            0-0032, but the number will be different if you have it at a different
            address.

            Thanks
            Guennadi
            ---
            Guennadi Liakhovetski

          • David Yip
            Hi (again), 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 And I have
            Message 5 of 16 , Jan 29, 2007
            • 0 Attachment
              Hi (again),

              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

              And I have

              LinkStation:/sys/devices# find . -print | grep i2
              ./platform/fsl-i2c.1
              ./platform/fsl-i2c.1/driver
              ./platform/fsl-i2c.1/i2c-0
              ./platform/fsl-i2c.1/i2c-0/i2c-dev:i2c-0
              ./platform/fsl-i2c.1/i2c-0/0-0032
              ./platform/fsl-i2c.1/i2c-0/0-0032/name
              ./platform/fsl-i2c.1/i2c-0/0-0032/driver
              ./platform/fsl-i2c.1/i2c-0/0-0032/bus
              ./platform/fsl-i2c.1/i2c-0/0-0032/subsystem
              ./platform/fsl-i2c.1/i2c-0/0-0032/uevent
              ./platform/fsl-i2c.1/i2c-0/i2c-adapter:i2c-0
              ./platform/fsl-i2c.1/i2c-0/name
              ./platform/fsl-i2c.1/i2c-0/uevent
              ./platform/fsl-i2c.1/bus
              ./platform/fsl-i2c.1/subsystem
              ./platform/fsl-i2c.1/modalias
              ./platform/fsl-i2c.1/uevent

              If you let me know what I am looking for, I will get it back to you

              Thanks,

              David

              David Yip wrote:

              Hi,

              Yes, adding the CONFIG_PATA_ IT821X was all I did in addition to using your stock config file from

              arch/powerpc/ configs/linkstat ion_defconfig

              (I added a couple of USB stuff that I wanted)

              I shall have to look at the RTC issue a little bit later, I am just making tea and getting everyone off to bed.

              Cheers,

              David

              Guennadi Liakhovetski wrote:

              On Sun, 28 Jan 2007, David Yip wrote:

              > >Auch, here. It's a different IDE controller. Please, enable ADDITIONALLY
              > >in your kernel configuration CONFIG_PATA_ IT821X. And report if it works
              > >then. I'd include this option in the standard configuration too.
              >
              > Success - that did the trick.

              Good. Could you, please, confirm that adding IT821x was the only addition
              you needed to get it running? or just send me a diff or your complete
              .config.

              And the realtime clock... It should work on your HG because it does on
              mine. As for the LS HS, would be nice to find out what they need as RTC.
              Under your 2.6.19 you also have rs5c372 driver. Does hwclock work there?
              If it does, could you, please, look at what I2C address it is on your LS
              HS? Somewhere under /sys/devices/ .../i2c-0/ there should be a file like
              0-0032, but the number will be different if you have it at a different
              address.

              Thanks
              Guennadi
              ---
              Guennadi Liakhovetski

            • Guennadi Liakhovetski
              ... 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
              Message 6 of 16 , Jan 29, 2007
              • 0 Attachment
                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...

                Thanks
                Guennadi
                ---
                Guennadi Liakhovetski
              • David Yip
                Hi Guennadi, Just a quick reply, The problem with me is that when I have the rtc-rs5c372.probe=0,0x32 in my uboot config, I dont get *any* kernel messages
                Message 7 of 16 , Jan 30, 2007
                • 0 Attachment
                  Hi Guennadi,

                  Just a quick reply,

                  The problem with me is that when I have the "rtc-rs5c372.probe=0,0x32" in my uboot config, I dont get *any* kernel messages through from  nc from the kurobox, but when I took it out from the uboot on my Linkstation, I did get messages from the kernel.

                  I will put the above line back on my Linkstation uboot config line and let you know what happens

                  ie I will put back
                  "root=/dev/sda1 netconsole=6666@1.2.3.4/,@5.6.7.8/ rtc-rs5c372.probe=0,0x32"
                  
                  
                  Cheers,

                  David




                  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...

                  Thanks
                  Guennadi
                  ---
                  Guennadi Liakhovetski

                • David Yip
                  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
                  Message 8 of 16 , 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

                    David

                    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...

                    Thanks
                    Guennadi
                    ---
                    Guennadi Liakhovetski

                  • Guennadi Liakhovetski
                    ... Good. One more thing in case you haven t yet realised - you can perfectly compile and use just 1 kernel for your LS and Kurobox. Same configuration, same
                    Message 9 of 16 , Jan 30, 2007
                    • 0 Attachment
                      On Tue, 30 Jan 2007, David Yip wrote:

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

                      Good. One more thing in case you haven't yet realised - you can
                      perfectly compile and use just 1 kernel for your LS and Kurobox. Same
                      configuration, same kernel and module binaries. Only bootloaders and
                      device-trees have to be different.

                      As a side note, I submitted a patch to ppc-dev ML with an extra .dts for
                      "slower" LS / Kurobox and extended defconfig to cover HD and HS systems.
                      Hope it will appear in 2.6.21.

                      Thanks
                      Guennadi
                      ---
                      Guennadi Liakhovetski
                    • David Yip
                      Hi (again), I have gotten the hwclock on the Kurobox to finally work, I took your advice and rebuilt the module and suddenly, it popped up in the kernel
                      Message 10 of 16 , Jan 31, 2007
                      • 0 Attachment
                        Hi (again),

                        I have gotten the hwclock on the Kurobox to finally work, I took your advice and rebuilt the module and suddenly, it popped up in the kernel messages

                        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-31 21:55:58 (1170280558)
                        linkstation: disarming the AVR watchdog:

                        One strange thing is that I had to create a link for /dev/rtc to /dev/rtc0, which was already created on the Linkstation (perhaps from installing the original Debian OS)

                        So, a big thank you for all of your help.

                        I must admit that getting a stock kernel up an running on the Linkstation was more troublesome than on the Kurobox, because I originally patched my firmware with freelink and you need it kept on rebooting with a v2.4 kernel (as expected and documented). But it can be done, and I think it is a great leap forward!

                        Cheers,

                        David

                        Guennadi Liakhovetski wrote:

                        On Tue, 30 Jan 2007, David Yip wrote:

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

                        Good. One more thing in case you haven't yet realised - you can
                        perfectly compile and use just 1 kernel for your LS and Kurobox. Same
                        configuration, same kernel and module binaries. Only bootloaders and
                        device-trees have to be different.

                        As a side note, I submitted a patch to ppc-dev ML with an extra .dts for
                        "slower" LS / Kurobox and extended defconfig to cover HD and HS systems.
                        Hope it will appear in 2.6.21.

                        Thanks
                        Guennadi
                        ---
                        Guennadi Liakhovetski

                      • cherrytreeproduction
                        ... can be ... i also agree that this was nice work. we really should create a simple way of installing UBoot-images to all linkstations...kuroguy summed up
                        Message 11 of 16 , Feb 1, 2007
                        • 0 Attachment
                          > I must admit that getting a stock kernel up an running on the
                          > Linkstation was more troublesome than on the Kurobox, because I
                          > originally patched my firmware with freelink and you need it kept on
                          > rebooting with a v2.4 kernel (as expected and documented). But it
                          can be
                          > done, and I think it is a great leap forward!

                          i also agree that this was nice work.

                          we really should create a simple way of installing UBoot-images to all
                          linkstations...kuroguy summed up the way we outlined already here:
                          http://forum.linkstationwiki.net/index.php?action=vthread&forum=7&topic=1760&page=1#msg17689

                          when i have time i think i will look at that again....

                          LNI`s UBoot still is the best one...
                        Your message has been successfully submitted and would be delivered to recipients shortly.