Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Tue Aug 22, 2017 4:22 am

All times are UTC+01:00




Post new topic  Reply to topic  [ 168 posts ]  Go to page Previous 1 2 3 4 512 Next
Author Message
PostPosted: Sat Aug 25, 2012 5:14 pm 
Offline
Regular Member
User avatar

Joined: Mon Jun 18, 2012 2:12 pm
Posts: 116
all drivers needed for the linkstation to boot/run are in the kernel, so technically you shouldn't need the modules to boot it.
check your formatting, especially ext4 for sda2/rootfs, and make sure you use an empty initrd.
and if nothing helps, test the 2.6.32 one.

i will upload 3.2.21-fjen-2 soon, which adds dnotify support needed for nfs server.

_________________
## Linkstation LS-CHLv2 and LS-XHL stuff:
Debian 7 Wheezy - Rootfs
Kernel 3.13


Top
   
PostPosted: Sun Aug 26, 2012 6:53 pm 
Offline
Newbie
User avatar

Joined: Fri Aug 03, 2012 4:40 pm
Posts: 14
SirKiosk wrote:
I could get neither 3.2.18-fjen-5 nor 3.2.21-fjen-1 to boot properly with Debian Squeeze. [...] then there's an abrupt clean shutdown.

Exactly what I am experiencing, even with my self built kernel based on fjen sources, patch and config. The only thing I added was ext2/3 to use the default partition table.

It's hard to debug without serial access though. :shock:

--Dennis

_________________
LS-CHLv2, Dockstar, Goflex Net, Raspberry Pi - all running Debian Squeeze


Top
   
PostPosted: Mon Aug 27, 2012 12:46 pm 
Offline
Regular Member
User avatar

Joined: Mon Jun 18, 2012 2:12 pm
Posts: 116
i have no idea why you're experiencing these problems and i can't do much without any logs.
i uploaded the new kernel with fixed nfs server support and an older 2.6.32.
The 2.6.32 was basically build with the instructions in the wiki and patched with the "original" lswxl patch, but with usb support added. If that one does not work, something other must be wrong.
So please try 2.6.32-45-fjen-1 and report.

_________________
## Linkstation LS-CHLv2 and LS-XHL stuff:
Debian 7 Wheezy - Rootfs
Kernel 3.13


Top
   
PostPosted: Wed Aug 29, 2012 7:30 am 
Offline
Newbie

Joined: Fri Jan 06, 2012 10:37 pm
Posts: 9
@fjen: just looked into your kernel for the lschlv2 and found, that the MPP_GPIO and led configuration are wrong :( :( seems to be the ones from the LS-WXL.


Top
   
PostPosted: Wed Aug 29, 2012 8:15 am 
Offline
Newbie
User avatar

Joined: Fri Aug 03, 2012 4:40 pm
Posts: 14
@mg21: That sounds interesting, the names of the stock kernel are:
Code:
ls /proc/buffalo/gpio/led/
alarm        eth   func2        func_blink  info_blink  power_blink
alarm_blink  func  func2_blink  info        power


Do you know the correct GPIOs for "static struct gpio_led lschlv2_led_pins[]"?

With that in mind I remember the LED stopped flashing after some time. Maybe it's flashing until we leave uboot and start booting the kernel.

_________________
LS-CHLv2, Dockstar, Goflex Net, Raspberry Pi - all running Debian Squeeze


Top
   
PostPosted: Wed Aug 29, 2012 10:16 am 
Offline
Newbie

Joined: Fri Jan 06, 2012 10:37 pm
Posts: 9
Taken from an old 2.6 patch
Code:
static unsigned int lschlv2_mpp_config[] __initdata = {
        MPP10_GPO,    /* HDD Power */
        MPP11_GPIO,   /* USB VBUS EN */
        MPP18_GPO,    /* FAN HIGH: on:0, off:1 */
        MPP19_GPO,    /* FAN LOW: on:0, off:1 */
        MPP36_GPIO, /* FUNC LED */
        MPP37_GPIO, /* ALARM LED */
        MPP38_GPIO, /* INFO LED */
        MPP39_GPIO, /* POWER LED */
        MPP40_GPIO, /* FAN LOCK */
        MPP41_GPIO, /* FUNC SW */
        MPP42_GPIO, /* POWER SW */
        MPP43_GPIO, /* POWER AUTO SW */
        MPP48_GPIO, /* FUNC RED LED */
        MPP49_GPIO, /* UART EN */
   0
};

static struct mv_sata_platform_data lschlv2_sata_data = {
   .n_ports   = 1,
};

static struct gpio_led lschlv2_led_pins[] = {
        {
                .name                   = "func",
                .gpio                   = 36,
                .active_low             = 1,
        },
        {
                .name                   = "alarm",
                .gpio                   = 37,
                .active_low             = 1,
        },
        {
                .name                   = "info",
                .gpio                   = 38,
                .active_low             = 1,
        },
        {
                .name                   = "power",
                .gpio                   = 39,
                .default_trigger        = "default-on",
                .active_low             = 1,
        },
        {
                .name                   = "func2",
                .gpio                   = 48,
                .active_low             = 1,
        },
};

... next going to try the lastest 3.4 kernel


Top
   
PostPosted: Wed Aug 29, 2012 10:28 am 
Offline
Regular Member
User avatar

Joined: Mon Jun 18, 2012 2:12 pm
Posts: 116
mg21 wrote:
@fjen: just looked into your kernel for the lschlv2 and found, that the MPP_GPIO and led configuration are wrong :( :( seems to be the ones from the LS-WXL.

Thats right, i did not find a corresponding LS-CHLv2 patch and this was one was mentioned in the wiki. Works for me.

Where did you find the "old 2.6 patch"? Im going to recompile my kernel with the correct config now.

_________________
## Linkstation LS-CHLv2 and LS-XHL stuff:
Debian 7 Wheezy - Rootfs
Kernel 3.13


Top
   
PostPosted: Wed Aug 29, 2012 10:36 am 
Offline
Newbie

Joined: Fri Jan 06, 2012 10:37 pm
Posts: 9
You might know, that LS-XHL and LS-CHLv2 are almost identical ...

http://tyche.pu-toyama.ac.jp/~a-urasim/lsxhl/data/kernel-2.6.31-lsxhl.patch


Top
   
PostPosted: Wed Aug 29, 2012 11:11 am 
Offline
Regular Member
User avatar

Joined: Mon Jun 18, 2012 2:12 pm
Posts: 116
Yes, i know that from the kernel 3.6 commit, but did not investigate further. Thank you for that link!

_________________
## Linkstation LS-CHLv2 and LS-XHL stuff:
Debian 7 Wheezy - Rootfs
Kernel 3.13


Top
   
PostPosted: Wed Aug 29, 2012 4:58 pm 
Offline
Regular Member
User avatar

Joined: Mon Jun 18, 2012 2:12 pm
Posts: 116
My LS-CHLv2 is now running a vanilla 3.2.28 with a modified patch, so i uploaded that.
GPIO numbers are changed to what mg21 posted. I don't know if it's good to take more from the LS-XHL patch.
ext4 should also accept and mount ext[23] as rootfs with CONFIG_EXT4_USE_FOR_EXT23.

shyd, could you please test the new one?

_________________
## Linkstation LS-CHLv2 and LS-XHL stuff:
Debian 7 Wheezy - Rootfs
Kernel 3.13


Top
   
PostPosted: Wed Aug 29, 2012 5:08 pm 
Offline
Newbie
User avatar

Joined: Fri Aug 03, 2012 4:40 pm
Posts: 14
Nice one - I'll test it later on!

_________________
LS-CHLv2, Dockstar, Goflex Net, Raspberry Pi - all running Debian Squeeze


Top
   
PostPosted: Thu Aug 30, 2012 10:28 am 
Offline
Newbie
User avatar

Joined: Fri Aug 03, 2012 4:40 pm
Posts: 14
Well, the GPIOs seem to work properly now. ext[23] will be mounted with ext4 subsystem. The LED turns solid blue. Everything's fine for now.
But about 10 sec after solid blue the hdd clicks and the LS turns into its bootloop again.
I have no idea so far, because dmesg, kern.log and messages are looking quite fine if I look at them connected to a laptop. :?

[edit:]
I uploaded the dmesg of the stock and your kernel: http://dev.shyd.de/linkstation/fjen-debug/
Some testing showed, that the LS is pingable until it reboots! Closer looking at dmesg output makes me think about the tun module...

_________________
LS-CHLv2, Dockstar, Goflex Net, Raspberry Pi - all running Debian Squeeze


Top
   
PostPosted: Thu Aug 30, 2012 1:59 pm 
Offline
Regular Member
User avatar

Joined: Mon Jun 18, 2012 2:12 pm
Posts: 116
The problem was the buffalo specific lsmonitor script. It rebootet the Linkstation after it was startet.
From lsmonitor:
Code:
      # Tell whether switch is in "on" position
      ON=0
      S=$(cat /proc/buffalo/gpio/switch/power)
      if [ "$S" = "on" ] ; then
         ON=1
      else
         S=$(cat /proc/buffalo/gpio/switch/auto_power)
         if [ "$S" = "on" ] ; then
            ON=1
         fi
      fi

      # Terminate when in OFF state
      if [ $ON -eq 0 ] ; then
         break
      fi


Do not use /etc/init.d/lsmonitor from blstools. Use this this one instead: http://neboola.de/fjen/lschlv2/lsmonitor/lsmonitor
/etc/init.d/usb is also not needed.

_________________
## Linkstation LS-CHLv2 and LS-XHL stuff:
Debian 7 Wheezy - Rootfs
Kernel 3.13


Top
   
PostPosted: Thu Aug 30, 2012 3:54 pm 
Offline
Newbie
User avatar

Joined: Fri Aug 03, 2012 4:40 pm
Posts: 14
That's it! The old lsmonitor made the LS reboot when the buffalo specific ports were scanned.
Thanks again! :up:

_________________
LS-CHLv2, Dockstar, Goflex Net, Raspberry Pi - all running Debian Squeeze


Top
   
PostPosted: Sat Sep 01, 2012 11:36 pm 
Offline
Newbie

Joined: Fri Jan 06, 2012 10:37 pm
Posts: 9
Since I was playing with u-boot nvram, I needed to add the flash partitions to the kernel ...
Code:
--- linux-3.2.28_orig/arch/arm/mach-kirkwood/lschlv2-setup.c
+++  linux-3.2.28/arch/arm/mach-kirkwood/lschlv2-setup.c
@@ -17,6 +17,9 @@
 #include <linux/platform_device.h>
 #include <linux/ata_platform.h>
 #include <linux/mv643xx_eth.h>
+#include <linux/mtd/physmap.h>
+#include <linux/spi/flash.h>
+#include <linux/spi/spi.h>
 #include <asm/mach-types.h>
 #include <asm/mach/arch.h>
 #include "include/mach/system.h"
@@ -24,6 +27,40 @@
 #include "common.h"
 #include "mpp.h"
 
+/*****************************************************************************
+ * 512KB SPI Flash on BOOT Device
+ ****************************************************************************/
+static struct mtd_partition lschlv2_partitions[] = {
+   {
+      .name      = "u-boot",
+      .offset      = 0x00000,
+      .size      = 0x70000,
+      .mask_flags    = MTD_WRITEABLE,
+   },
+   {
+      .name      = "u-boot env",
+      .offset      = MTDPART_OFS_APPEND,
+      .size      = 0x10000,
+   }
+};
+
+static struct flash_platform_data lschlv2_spi_slave_data = {
+   .type      = "m25p40",
+   .parts      = lschlv2_partitions,
+   .nr_parts   = ARRAY_SIZE(lschlv2_partitions),
+};
+
+static struct spi_board_info __initdata lschlv2_spi_slave_info[] = {
+   {
+      .modalias   = "m25p80",
+      .platform_data   = &lschlv2_spi_slave_data,
+      .irq      = -1,
+      .max_speed_hz   = 20000000,
+      .bus_num   = 0,
+      .chip_select   = 0,
+   }
+};
+
 static struct mv643xx_eth_platform_data lschlv2_ge00_data = {
    .phy_addr   = MV643XX_ETH_PHY_ADDR(0),
 };
@@ -152,6 +189,9 @@
    platform_device_register(&lschlv2_leds);
    platform_device_register(&lschlv2_button_device);
 
+   spi_register_board_info(lschlv2_spi_slave_info,
+            ARRAY_SIZE(lschlv2_spi_slave_info));
+
    /* register power-off method */
    pm_power_off = lschlv2_power_off;

In order to access the mtd0, mtd1 a number of MTD and SPI configs need to be activated ...


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 168 posts ]  Go to page Previous 1 2 3 4 512 Next

All times are UTC+01:00


Who is online

Users browsing this forum: Baidu [Spider] and 2 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