Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Sun Aug 19, 2018 9:47 pm

All times are UTC+01:00




Post new topic  Reply to topic  [ 20 posts ]  Go to page 1 2 Next
Author Message
PostPosted: Fri Jun 26, 2009 6:56 am 
Offline
Regular Member

Joined: Mon Nov 07, 2005 4:37 pm
Posts: 205
Location: Germany
Hi there,

I created an kernel patch, based on the ls mini sources for the ls pro duo. I also compiled an kernel with it and the system boots and works for me. Here the patch:
Code:
diff -ruN linux-2.6.30/arch/arm/configs/orion5x_defconfig linux-2.6.30.mod1/arch/arm/configs/orion5x_defconfig
--- linux-2.6.30/arch/arm/configs/orion5x_defconfig     2009-06-10 05:05:27.000000000 +0200
+++ linux-2.6.30.mod1/arch/arm/configs/orion5x_defconfig        2009-06-15 21:05:12.000000000 +0200
@@ -182,6 +182,7 @@
CONFIG_MACH_TERASTATION_PRO2=y
CONFIG_MACH_LINKSTATION_PRO=y
CONFIG_MACH_LINKSTATION_MINI=y
+CONFIG_MACH_LINKSTATION_PRODUO=y
CONFIG_MACH_TS409=y
CONFIG_MACH_WRT350N_V2=y
CONFIG_MACH_TS78XX=y
diff -ruN linux-2.6.30/arch/arm/mach-orion5x/Kconfig linux-2.6.30.mod1/arch/arm/mach-orion5x/Kconfig
--- linux-2.6.30/arch/arm/mach-orion5x/Kconfig  2009-06-10 05:05:27.000000000 +0200
+++ linux-2.6.30.mod1/arch/arm/mach-orion5x/Kconfig     2009-06-15 21:05:12.000000000 +0200
@@ -57,6 +57,13 @@
          Say 'Y' here if you want your kernel to support the
          Buffalo Linkstation Mini platform.

+config MACH_LINKSTATION_PRODUO
+       bool "Buffalo Linkstation Pro Duo"
+       select I2C_BOARDINFO
+       help
+         Say 'Y' here if you want your kernel to support the
+         Buffalo Linkstation Pro Duo platform.
+
config MACH_TS409
        bool "QNAP TS-409"
        help
diff -ruN linux-2.6.30/arch/arm/mach-orion5x/lsproduo-setup.c linux-2.6.30.mod1/arch/arm/mach-orion5x/lsproduo-setup.c
--- linux-2.6.30/arch/arm/mach-orion5x/lsproduo-setup.c 1970-01-01 01:00:00.000000000 +0100
+++ linux-2.6.30.mod1/arch/arm/mach-orion5x/lsproduo-setup.c    2009-06-15 21:56:14.000000000 +0200
@@ -0,0 +1,268 @@
+/*
+ * arch/arm/mach-orion5x/lsproduo-setup.c
+ *
+ * Source taken from arch/arm/mach-orion5x/lsmini-setup.c - kernel 2.6.30
+ * Maintainer: Manuel Bernhardt <opensource@prodigy7.de>
+ *
+ * This file is licensed under the terms of the GNU General Public
+ * License version 2.  This program is licensed "as is" without any
+ * warranty of any kind, whether express or implied.
+ */
+
+#include <linux/kernel.h>
+#include <linux/init.h>
+#include <linux/platform_device.h>
+#include <linux/pci.h>
+#include <linux/mtd/physmap.h>
+#include <linux/mv643xx_eth.h>
+#include <linux/leds.h>
+#include <linux/gpio_keys.h>
+#include <linux/input.h>
+#include <linux/i2c.h>
+#include <linux/ata_platform.h>
+#include <asm/mach-types.h>
+#include <linux/gpio.h>
+#include <asm/mach/arch.h>
+#include "common.h"
+#include "mpp.h"
+#include "include/mach/system.h"
+
+/*****************************************************************************
+ * Linkstation Pro Duo Info
+ ****************************************************************************/
+
+/*
+ * 256K NOR flash Device bus boot chip select
+ */
+
+#define LSPRODUO_NOR_BOOT_BASE 0xf4000000
+#define LSPRODUO_NOR_BOOT_SIZE SZ_256K
+
+/*****************************************************************************
+ * 256KB NOR Flash on BOOT Device
+ ****************************************************************************/
+
+static struct physmap_flash_data lsproduo_nor_flash_data = {
+       .width          = 1,
+};
+
+static struct resource lsproduo_nor_flash_resource = {
+       .flags  = IORESOURCE_MEM,
+       .start  = LSPRODUO_NOR_BOOT_BASE,
+       .end    = LSPRODUO_NOR_BOOT_BASE + LSPRODUO_NOR_BOOT_SIZE - 1,
+};
+
+static struct platform_device lsproduo_nor_flash = {
+       .name                   = "physmap-flash",
+       .id                     = 0,
+       .dev            = {
+               .platform_data  = &lsproduo_nor_flash_data,
+       },
+       .num_resources          = 1,
+       .resource               = &lsproduo_nor_flash_resource,
+};
+
+/*****************************************************************************
+ * Ethernet
+ ****************************************************************************/
+
+static struct mv643xx_eth_platform_data lsproduo_eth_data = {
+       .phy_addr       = 8,
+};
+
+/*****************************************************************************
+ * RTC 5C372a on I2C bus
+ ****************************************************************************/
+
+static struct i2c_board_info __initdata lsproduo_i2c_rtc = {
+       I2C_BOARD_INFO("rs5c372a", 0x32),
+};
+
+/*****************************************************************************
+ * LEDs attached to GPIO
+ ****************************************************************************/
+
+#define LSPRODUO_GPIO_LED_ALARM        2
+#define LSPRODUO_GPIO_LED_INFO 3
+#define LSPRODUO_GPIO_LED_PWR  0
+
+static struct gpio_led lsproduo_led_pins[] = {
+       {
+               .name      = "alarm:red",
+               .gpio      = LSPRODUO_GPIO_LED_ALARM,
+               .active_low     = 1,
+       }, {
+               .name      = "info:amber",
+               .gpio      = LSPRODUO_GPIO_LED_INFO,
+               .active_low     = 1,
+       }, {
+               .name      = "power:blue:bottom",
+               .gpio      = LSPRODUO_GPIO_LED_PWR,
+       },
+};
+
+static struct gpio_led_platform_data lsproduo_led_data = {
+       .leds      = lsproduo_led_pins,
+       .num_leds       = ARRAY_SIZE(lsproduo_led_pins),
+};
+
+static struct platform_device lsproduo_leds = {
+       .name   = "leds-gpio",
+       .id     = -1,
+       .dev    = {
+               .platform_data  = &lsproduo_led_data,
+       },
+};
+
+/****************************************************************************
+ * GPIO Attached Keys
+ ****************************************************************************/
+
+#define LSPRODUO_GPIO_KEY_POWER                8
+#define LSPRODUO_GPIO_KEY_AUTOPOWER    10
+
+#define LSPRODUO_SW_POWER              0x00
+#define LSPRODUO_SW_AUTOPOWER          0x01
+
+static struct gpio_keys_button lsproduo_buttons[] = {
+       {
+               .type           = EV_SW,
+               .code      = LSPRODUO_SW_POWER,
+               .gpio      = LSPRODUO_GPIO_KEY_POWER,
+               .desc      = "Power-on Switch",
+               .active_low     = 1,
+       }, {
+               .type           = EV_SW,
+               .code      = LSPRODUO_SW_AUTOPOWER,
+               .gpio      = LSPRODUO_GPIO_KEY_AUTOPOWER,
+               .desc      = "Power-auto Switch",
+               .active_low     = 1,
+       },
+};
+
+static struct gpio_keys_platform_data lsproduo_button_data = {
+       .buttons        = lsproduo_buttons,
+       .nbuttons       = ARRAY_SIZE(lsproduo_buttons),
+};
+
+static struct platform_device lsproduo_button_device = {
+       .name      = "gpio-keys",
+       .id          = -1,
+       .num_resources  = 0,
+       .dev        = {
+               .platform_data  = &lsproduo_button_data,
+       },
+};
+
+
+/*****************************************************************************
+ * SATA
+ ****************************************************************************/
+static struct mv_sata_platform_data lsproduo_sata_data = {
+       .n_ports        = 2,
+};
+
+
+/*****************************************************************************
+ * Linkstation Pro Duo specific power off method: reboot
+ ****************************************************************************/
+/*
+ * On the Linkstation Pro Duo, the shutdown process is following:
+ * - Userland monitors key events until the power switch goes to off position
+ * - The board reboots
+ * - U-boot starts and goes into an idle mode waiting for the user
+ *   to move the switch to ON position
+ */
+
+static void lsproduo_power_off(void)
+{
+       arch_reset(0, NULL);
+}
+
+
+/*****************************************************************************
+ * General Setup
+ ****************************************************************************/
+
+#define LSPRODUO_GPIO_USB_POWER                9
+#define LSPRODUO_GPIO_AUTO_POWER       10
+#define LSPRODUO_GPIO_POWER            8
+
+#define LSPRODUO_GPIO_HDD_POWER0       1
+
+static struct orion5x_mpp_mode lsproduo_mpp_modes[] __initdata = {
+       {  0, MPP_GPIO },       /* LED_PWR */
+       {  1, MPP_GPIO },       /* HDD_PWR */
+       {  2, MPP_GPIO },       /* LED_ALARM */
+       {  3, MPP_GPIO },       /* LED_INFO */
+       {  4, MPP_UNUSED },
+       {  5, MPP_UNUSED },
+       {  6, MPP_GPIO },       /* FAN_LCK */
+       {  7, MPP_GPIO },       /* INIT */
+       {  8, MPP_GPIO },       /* POWER */
+       {  9, MPP_GPIO },       /* USB_PWR */
+       { 10, MPP_GPIO },       /* AUTO_POWER */
+       { 11, MPP_UNUSED },     /* LED_ETH dummy */
+       { 12, MPP_UNUSED },
+       { 13, MPP_UNUSED },
+       { 14, MPP_GPIO },       /* FAN_HIGH */
+       { 15, MPP_UNUSED },
+       { 16, MPP_UNUSED },
+       { 17, MPP_GPIO },       /* FAN_LOW */
+       { 18, MPP_UNUSED },
+       { 19, MPP_UNUSED },
+       { -1 },
+};
+
+static void __init lsproduo_init(void)
+{
+       /*
+        * Setup basic Orion functions. Need to be called early.
+        */
+       orion5x_init();
+
+       orion5x_mpp_conf(lsproduo_mpp_modes);
+
+       /*
+        * Configure peripherals.
+        */
+       orion5x_ehci0_init();
+       orion5x_ehci1_init();
+       orion5x_eth_init(&lsproduo_eth_data);
+       orion5x_i2c_init();
+       orion5x_sata_init(&lsproduo_sata_data);
+       orion5x_uart0_init();
+       orion5x_xor_init();
+
+       orion5x_setup_dev_boot_win(LSPRODUO_NOR_BOOT_BASE,
+                                  LSPRODUO_NOR_BOOT_SIZE);
+       platform_device_register(&lsproduo_nor_flash);
+
+       platform_device_register(&lsproduo_button_device);
+
+       platform_device_register(&lsproduo_leds);
+
+       i2c_register_board_info(0, &lsproduo_i2c_rtc, 1);
+
+       /* enable USB power */
+       gpio_set_value(LSPRODUO_GPIO_USB_POWER, 1);
+
+       /* register power-off method */
+       pm_power_off = lsproduo_power_off;
+
+       pr_info("%s: finished\n", __func__);
+}
+
+#ifdef CONFIG_MACH_LINKSTATION_PRODUO
+MACHINE_START(LINKSTATION_PRODUO, "Buffalo Linkstation Pro Duo")
+       /* Maintainer: Manuel Bernhardt <opensource@prodigy7.de> */
+       .phys_io        = ORION5X_REGS_PHYS_BASE,
+       .io_pg_offst    = ((ORION5X_REGS_VIRT_BASE) >> 18) & 0xFFFC,
+       .boot_params    = 0x00000100,
+       .init_machine   = lsproduo_init,
+       .map_io         = orion5x_map_io,
+       .init_irq       = orion5x_init_irq,
+       .timer          = &orion5x_timer,
+       .fixup          = tag_fixup_mem32,
+MACHINE_END
+#endif
diff -ruN linux-2.6.30/arch/arm/mach-orion5x/Makefile linux-2.6.30.mod1/arch/arm/mach-orion5x/Makefile
--- linux-2.6.30/arch/arm/mach-orion5x/Makefile 2009-06-10 05:05:27.000000000 +0200
+++ linux-2.6.30.mod1/arch/arm/mach-orion5x/Makefile    2009-06-15 21:05:12.000000000 +0200
@@ -5,6 +5,7 @@
obj-$(CONFIG_MACH_TERASTATION_PRO2)    += terastation_pro2-setup.o
obj-$(CONFIG_MACH_LINKSTATION_PRO) += kurobox_pro-setup.o
obj-$(CONFIG_MACH_LINKSTATION_MINI) += lsmini-setup.o
+obj-$(CONFIG_MACH_LINKSTATION_PRODUO) += lsproduo-setup.o
obj-$(CONFIG_MACH_DNS323)      += dns323-setup.o
obj-$(CONFIG_MACH_TS209)       += ts209-setup.o tsx09-common.o
obj-$(CONFIG_MACH_TS409)       += ts409-setup.o tsx09-common.o

Currently the support for the fan control is missing and I've no idea, the patch is working with newer duo versions (I've an release 1 device) - so:

This patch is experimental and you should use an kernel, build with it only you've serial access for your device!!!

When I've an idea, how the fan can be controlled, I'll post a patch or hint. The keys and leds are already working (can be found in /sys).

prodigy7

_________________
LS2 (U-Boot + Freelink) | Kurobox (U-Boot + Deboostraped) | LS Pro Duo (Freelink)


Last edited by prodigy7 on Wed Nov 24, 2010 4:25 pm, edited 2 times in total.

Top
   
PostPosted: Fri Jun 26, 2009 7:36 am 
Offline
Regular Member

Joined: Mon Nov 07, 2005 4:37 pm
Posts: 205
Location: Germany
Question to the kernel experts:
I inspect the buffalo kernel sources for parts, where the fan are controlled. I found there 4 fan speeds:
  • STOP
  • SLOW
  • FAST
  • FULL
The important part in the sources controll the fan with this:
Code:
BuffaloGpio_FanControlWrite(unsigned int value)
{
        switch(value){
        case BUFFALO_GPIO_FAN_STOP:
                //printk("%s > changing to stop\n", __FUNCTION__);
                MV_REG_BIT_SET(GPP_DATA_OUT_REG(0), (BIT(BIT_FAN_LOW)));
                MV_REG_BIT_SET(GPP_DATA_OUT_REG(0), (BIT(BIT_FAN_HIGH)));
                break;
        case BUFFALO_GPIO_FAN_SLOW:
                //printk("%s > changing to slow\n", __FUNCTION__);
                MV_REG_BIT_SET(GPP_DATA_OUT_REG(0), (BIT(BIT_FAN_LOW)));
                MV_REG_BIT_RESET(GPP_DATA_OUT_REG(0), (BIT(BIT_FAN_HIGH)));
                break;
        case BUFFALO_GPIO_FAN_FAST:
                //printk("%s > changing to fast\n", __FUNCTION__);
                MV_REG_BIT_RESET(GPP_DATA_OUT_REG(0), (BIT(BIT_FAN_LOW)));
                MV_REG_BIT_SET(GPP_DATA_OUT_REG(0), (BIT(BIT_FAN_HIGH)));
                break;
        case BUFFALO_GPIO_FAN_FULL:
                //printk("%s > changing to full\n", __FUNCTION__);
                MV_REG_BIT_RESET(GPP_DATA_OUT_REG(0), (BIT(BIT_FAN_LOW)));
                MV_REG_BIT_RESET(GPP_DATA_OUT_REG(0), (BIT(BIT_FAN_HIGH)));
                break;
        default:
                break;
        } // end of switch
}
When I port this informations in my head to the lsprodu-setup.c, I think, I should define
Code:
#define LSPRODUO_GPIO_FAN_LOW 17 
#define LSPRODUO_GPIO_FAN_HIGH 14
and could control the fan in the same manner when I use for example
Code:
gpio_set_value(LSPRODUO_GPIO_FAN_LOW, 1);
gpio_set_value(LSPRODUO_GPIO_FAN_HIGH, 1);
(should reflect STOP) - is that right? What I doesn't full understand - the meaning of MV_REG_BIT_RESET and MV_REG_BIT_SET:
Code:
#define MV_REG_BIT_SET(offset, bitMask)                 \
        (MV_MEMIO32_WRITE((INTER_REGS_BASE | (offset)), \
         (MV_MEMIO32_READ(INTER_REGS_BASE | (offset)) | \
          MV_32BIT_LE_FAST(bitMask))))

#define MV_REG_BIT_RESET(offset,bitMask)                \
        (MV_MEMIO32_WRITE((INTER_REGS_BASE | (offset)), \
         (MV_MEMIO32_READ(INTER_REGS_BASE | (offset)) & \
          MV_32BIT_LE_FAST(~bitMask))))
Does this only mean, that bitMask = 0 and ~bitMask = 1?

_________________
LS2 (U-Boot + Freelink) | Kurobox (U-Boot + Deboostraped) | LS Pro Duo (Freelink)


Top
   
PostPosted: Sat Jun 27, 2009 7:22 pm 
Offline
Newbie

Joined: Sat Jun 13, 2009 7:53 am
Posts: 18
That's very cool. What kernel version are you building? Is there a guide you followed for getting the kernel patched and built? I have a desktop running Ubuntu, if I can get set up to cross-compile the buffalo kernel I'll try out your patch.

I'm particularly interested in getting a kernel which has md (RAID) and USB support (either compiled-in or as modules) and which also has a way to adjust the fan speed.


Top
   
PostPosted: Sun Jun 28, 2009 9:10 am 
Offline
Regular Member

Joined: Mon Nov 07, 2005 4:37 pm
Posts: 205
Location: Germany
Hi,

i'll upload an precompiled 2.6.30 kernel with this patch next. But you should attend: It's high experimental. Means: It should not work with the stock firmware. I'll also upload then an modified initramfs so nothing can be destroyed, if the new kernel are loaded. Best way is, if you've serial access for your box.

Currently there are three things which must be done so that this patch is finally ready:
  • Fan support
  • Readout of the correct mac ... somehow, I've another mac address
  • Support for blinking lights (not so important....)

prodigy7

_________________
LS2 (U-Boot + Freelink) | Kurobox (U-Boot + Deboostraped) | LS Pro Duo (Freelink)


Top
   
PostPosted: Sun Jun 28, 2009 8:00 pm 
Offline
Regular Member

Joined: Mon Nov 07, 2005 4:37 pm
Posts: 205
Location: Germany
The ready compiled binaries can found here:
http://download.prodigy7.de/files/packa ... o-vanilla/

Please attend:
  • Because an other/newer driver handels the network interface, the interface name can changed because udev "detect" another nic - so you should configure eth1 before you boot this kernel.
  • The fan can't controlled - it runs always on the highest level (shouldn't be bad)
  • You should currently use this kernel only, if you've serial access
  • You should currently use this kernel only, if you don't use the stock system from buffalo - it wouldn't find his points in /proc/buffalo

I uploaded also my modified initrd - I remove the whole buffalo stuff - so if it can't boot, it should run into an minimal mode with ftp and telnet (known default ip address)

Any feedback are welcome and support from developers with kernel know-how too ;-)

_________________
LS2 (U-Boot + Freelink) | Kurobox (U-Boot + Deboostraped) | LS Pro Duo (Freelink)


Top
   
PostPosted: Thu Jul 09, 2009 6:30 am 
Offline
Newbie

Joined: Tue Jan 06, 2009 6:39 am
Posts: 5
Just for kicks I made a backup of my freelink install and tried running this kernel with it on my rev 3 pro duo. Of course it didn't boot, but it did load into your custom em mode and I was able to telnet in and poke around.


Top
   
PostPosted: Sun Jul 12, 2009 3:00 pm 
Offline
Regular Member

Joined: Mon Nov 07, 2005 4:37 pm
Posts: 205
Location: Germany
Okay ... thx for response. It could be, that the rev 3 has another device id... somewhere in /proc/buffalo there should be an file which contains the id - can you post it?

_________________
LS2 (U-Boot + Freelink) | Kurobox (U-Boot + Deboostraped) | LS Pro Duo (Freelink)


Top
   
PostPosted: Sun Jul 12, 2009 5:49 pm 
Offline
Newbie

Joined: Tue Jan 06, 2009 6:39 am
Posts: 5
Code:
root@Luggage:/proc/buffalo# ls
board_info  booting  cpu_status  debug  enet  firmware  gpio  kernevnt  power_sw
root@Luggage:/proc/buffalo# cat board_info
BoardId=1b
BoardName=BUFFALO_BOARD_LS_WTGL_R1_V3
BoardStrap=3d
root@Luggage:/proc/buffalo# cat firmware
SERIES=LinkStation
PRODUCTNAME=LS-WTGL/R1-V3(SEIMU)
VERSION=0.16
SUBVERSION=FLASH 0.00
PRODUCTID=0x00003004
BUILDDATE=2009/01/21 10:23:16
BOOTVER=1.13
root@Luggage:/proc/buffalo#


What rootfs are you using with your kernel?


Top
   
PostPosted: Tue Jul 14, 2009 8:00 pm 
Offline
Regular Member

Joined: Mon Nov 07, 2005 4:37 pm
Posts: 205
Location: Germany
My rootfs is debian 4.0.
If I find time, I'll check your board id - maybe it is not defined in the kernel and so the kernel doesn't boot.

_________________
LS2 (U-Boot + Freelink) | Kurobox (U-Boot + Deboostraped) | LS Pro Duo (Freelink)


Top
   
PostPosted: Fri Aug 07, 2009 3:03 pm 
Offline
Regular Member

Joined: Mon Nov 07, 2005 4:37 pm
Posts: 205
Location: Germany
Okay ... I checked it: Your version of ls pro duo is newer and I think, that's the reason why the kernel doesn't boot. Before I add the mach id of my device, the kernel stops booting with the hint, that the device id isn't known. Is anything known about the newer version? Can someone post informations like here -> http://buffalo.nas-central.org/wiki/LS_ ... -_Boot-Log ?

_________________
LS2 (U-Boot + Freelink) | Kurobox (U-Boot + Deboostraped) | LS Pro Duo (Freelink)


Top
   
PostPosted: Fri Aug 21, 2009 6:32 pm 
Offline
Newbie

Joined: Fri Aug 21, 2009 6:23 pm
Posts: 12
i buyed a linkstation pro duo some month ago.
flashed it today with freelink.

well, i though the pro duo got only 64mb ram. top, free -m and dmesg got 128mb.
whats that? maybe "newer" versions got 128mb or what?

anyway. what should i do to try out your kernel? i guess i should compile and patch it myself, because in your precompiled kernel is not the newer id (it's the same id as celeritys id).
i flashed the "stock" freelink and upgraded with apt-get (udev left). is anymore needed to get the 2.6.30er kernel running?

greetings, ahorn.

ps: maybe you can talk directly with me in irc @ freenode. my nick is ahorn.

_________________
LS Pro Duo (2.6.30.6, squeeze, armel)


Top
   
PostPosted: Fri Aug 21, 2009 8:48 pm 
Offline
Newbie

Joined: Fri Aug 21, 2009 6:23 pm
Posts: 12
so some news.

i flashed your uImage.buffalo, u-boot.buffalo.updated, initrd.buffalo and a self build hddrootfs.img with the 2.6.30er modules.

there was an error in the middle at the upgrade in LSUpdater.exe. Something with ACP_STATE.

anyway. i can login to EM-Mode and confirm that the 2.6.30er kernel is loaded

Code:
sh-2.05b# uname -a
Linux LS-GL-EM3F6 2.6.30-p7r1 #7 PREEMPT Sun Jun 28 20:51:26 CEST 2009 armv5tel unknown


also the box got 128mb ram

Code:
sh-2.05b# dmesg
ognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x41000403
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 32768
free_area_init_node: node 0, pgdat c04bd0dc, node_mem_map c04f7000
  Normal zone: 256 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 32512 pages, LIFO batch:7
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Kernel command line: console=ttyS0,115200 root=/dev/sda2 rw initrd=0x00800040,15
M panic=5 func=0 BOOTVER=1.13
NR_IRQS:64
PID hash table entries: 512 (order: 9, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 109352KB available (4280K code, 340K data, 140K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1


and the box uses Western Digital drives. maybe the green ones. i'll check this later by opening the case.

Code:
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-8: WDC WD10EADS-00L5B1, 01.01A01, max UDMA/133
ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      WDC WD10EADS-00L 01.0 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO
 or FUA
 sda: sda1 sda2 sda4 < sda5 sda6 >
sd 0:0:0:0: [sda] Attached SCSI disk
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-8: WDC WD10EADS-00L5B1, 01.01A01, max UDMA/133
ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata2.00: configured for UDMA/133
scsi 1:0:0:0: Direct-Access     ATA      WDC WD10EADS-00L 01.0 PQ: 0 ANSI: 5
sd 1:0:0:0: [sdb] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO
 or FUA
 sdb: sdb1 sdb2 sdb4 < sdb5 sdb6 >
sd 1:0:0:0: [sdb] Attached SCSI disk


so what can i do now? :) how can i load some real linux stuff with maybe boot-loaded raid?

ps: i found a mistake in /etc/init.d/daemonwatch.sh, there's a typo ehco should be echo.

_________________
LS Pro Duo (2.6.30.6, squeeze, armel)


Top
   
PostPosted: Wed Sep 09, 2009 10:48 pm 
Offline
Regular Member

Joined: Mon Nov 07, 2005 4:37 pm
Posts: 205
Location: Germany
Here you can find the next linux patch: http://download.prodigy7.de/files/packa ... la/patches

Includes now fan control support (/proc/linkstation/gpio/fan). Can be controlled with
Code:
echo [value] > /proc/linkstation/gpio/fan

[value] can be off, slow, fast, full. The kernel boot default with full.

Question to the kernel experts: What can I do, that the fan control devices is set under /sys ?

Hint: I've the feedback, that the kernel with this patch also boots on rev2/3 duo. This patch also includes support for the second usb port, if rev2/3 hardware is configured.

Some things are to do but the kernel can be used for production.

_________________
LS2 (U-Boot + Freelink) | Kurobox (U-Boot + Deboostraped) | LS Pro Duo (Freelink)


Top
   
PostPosted: Thu Sep 10, 2009 9:20 am 
Offline
Newbie

Joined: Fri Aug 21, 2009 6:23 pm
Posts: 12
this patch here helps us a lot. no need to mess with uboot.
http://marc.info/?l=linux-arm-kernel&m= ... 528005&w=2

in .config for example:
CONFIG_CMDLINE="init=/linuxrc root=/dev/ram0 real_root=/dev/md1 console=ttyS0,115200 rw initrd=0x00800040,15M panic=5 func=0 BOOTVER=1.13"
CONFIG_CMDLINE_OVERRIDE=y

you need the newer chroot/pivot_root method to mount the real root in your initrd. use this initrd http://www.ahorn.todesmut.org/lsproduo/initrd.buffalo

_________________
LS Pro Duo (2.6.30.6, squeeze, armel)


Top
   
PostPosted: Tue Jul 19, 2011 6:50 pm 
Offline
Regular Member
User avatar

Joined: Sun Nov 16, 2008 2:45 am
Posts: 105
Location: eu/fr/35/rennes
Can this patch be reported upstream ? I wish the device can support debian installer ...


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 20 posts ]  Go to page 1 2 Next

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 5 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Powered by phpBB® Forum Software © phpBB Limited