Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Sat Aug 18, 2018 5:33 pm

All times are UTC+01:00




Post new topic  Reply to topic  [ 36 posts ]  Go to page Previous 1 2 3 Next
Author Message
PostPosted: Fri Sep 19, 2008 4:31 pm 
Offline
Regular Member
User avatar

Joined: Fri Jul 25, 2008 3:23 pm
Posts: 160
Location: Kobe, Japan
Yes, RTC interrupt connection is not needed, when connected I get an error:
Code:
leds-gpio: probe of leds-gpio failed with error -16

When I removed RTC interrupt initialization, leds detected properly:
Code:
Registered led device: alarm:red
Registered led device: info:orange

One can control them via sysfs:
Code:
 echo 1 > /sys/class/leds/alarm\:*/brightness

The key also works, checked by cat /dev/input/event0


Top
   
PostPosted: Fri Sep 19, 2008 8:00 pm 
Offline
Developer

Joined: Mon Oct 03, 2005 11:32 pm
Posts: 399
Location: France
Great work ;)
I guess that you have something that looks like a real support patch now ;)
Now someone need to write a daemon to support the linkstation mini shutdown ;)

Sylver

_________________
Kurobox Pro 500GB (for dev) / Freelink / 2.6.26-rc4 kernel, QNAP TS-409 Pro 1TB, Maxtor Shared Storage II 500GB


Top
   
PostPosted: Sat Sep 20, 2008 1:49 pm 
Offline
Regular Member
User avatar

Joined: Fri Jul 25, 2008 3:23 pm
Posts: 160
Location: Kobe, Japan
Is there any easy way to read GPIOs from userspace?

I've seen how it was done in micro_evtd via /dev/mem, but I don't think it's the best way.

When booted with original kernel we have
Code:
/proc/buffalo/gpio/switch/auto_power
/proc/buffalo/gpio/switch/power

which can be read easily. They show off/on status.

Also, with original kernel the power switch does nothing,
which means that in original firmware shutdown job is definitely done in userspace too.


Top
   
PostPosted: Sun Sep 21, 2008 10:38 am 
Offline
Regular Member
User avatar

Joined: Fri Jul 25, 2008 3:23 pm
Posts: 160
Location: Kobe, Japan
We could get GPIO into userspace with CONFIG_GPIOLIB:
Code:
 This enables GPIO support through the generic GPIO library.
 You only need to enable this, if you also want to enable   
 one or more of the GPIO expansion card drivers below.     

But it won't built with Orion5x:
Code:
drivers/built-in.o: In function `gpio_free':
hid-quirks.c:(.text+0x4c8): multiple definition of `gpio_free'
arch/arm/mach-orion5x/built-in.o:lsmini-setup.c:(.text+0x7d8): first defined here
drivers/built-in.o: In function `gpio_direction_output':
hid-quirks.c:(.text+0x1ec): multiple definition of `gpio_direction_output'
arch/arm/mach-orion5x/built-in.o:lsmini-setup.c:(.text+0x9bc): first defined here
drivers/built-in.o: In function `gpio_direction_input':
hid-quirks.c:(.text+0x5c8): multiple definition of `gpio_direction_input'
arch/arm/mach-orion5x/built-in.o:lsmini-setup.c:(.text+0x900): first defined here
drivers/built-in.o: In function `gpio_request':
hid-quirks.c:(.text+0x6e0): multiple definition of `gpio_request'
arch/arm/mach-orion5x/built-in.o:lsmini-setup.c:(.text+0x840): first defined here
make: *** [vmlinux.o] Error 1


Top
   
PostPosted: Tue Sep 23, 2008 5:15 am 
Offline
Regular Member
User avatar

Joined: Fri Jul 25, 2008 3:23 pm
Posts: 160
Location: Kobe, Japan
With this patch now we are able to read and write system status in RTC from userspace:
Code:
 $ cat /proc/driver/rtc | grep alrm_time
alrm_time   : 00:40:00
 $ awk -F: '/alrm_time/{ print $3 }' /proc/driver/rtc
40


Top
   
PostPosted: Wed Sep 24, 2008 4:49 pm 
Offline
Regular Member
User avatar

Joined: Fri Jul 25, 2008 3:23 pm
Posts: 160
Location: Kobe, Japan
I made a simple proof-of-concept program to monitor power switch:
Code:
 $ ./keys 
Power ON
Power OFF
Auto ON
Auto OFF
Power ON
Power OFF
Power ON


Code:
#include <stdlib.h>
#include <stdio.h>
#include <fcntl.h>
#include <unistd.h>
#include <linux/input.h>

#define LSMINI_SW_POWER      0x00
#define LSMINI_SW_AUTOPOWER   0x01

#define EVENT_SOURCE "/dev/input/event0"

int main() {
   int fd = open(EVENT_SOURCE, O_RDONLY);

   struct input_event ev;
   while (1) {
      read(fd, (char *)&ev, sizeof(struct input_event));
      if (ev.type != 5) continue;

      switch (ev.code) {
      case LSMINI_SW_POWER:
         if (ev.value) printf("Power ON\n");
         else printf("Power OFF\n");
      break;
      case LSMINI_SW_AUTOPOWER:
         if (ev.value) printf("Auto ON\n");
         else printf("Auto OFF\n");
      break;
      }

   }
}


Now I want to find out if we really need to monitor and write system status into RTC ALARM_B_MIN


Top
   
PostPosted: Thu Sep 25, 2008 9:20 pm 
Offline
Developer

Joined: Mon Oct 03, 2005 11:32 pm
Posts: 399
Location: France
Just seen your patch on LAK, good you managed to make something that is working !
It's quite different from the first patch you've posted few days ago ;)

_________________
Kurobox Pro 500GB (for dev) / Freelink / 2.6.26-rc4 kernel, QNAP TS-409 Pro 1TB, Maxtor Shared Storage II 500GB


Top
   
PostPosted: Fri Sep 26, 2008 8:31 am 
Offline
Regular Member
User avatar

Joined: Fri Jul 25, 2008 3:23 pm
Posts: 160
Location: Kobe, Japan
Sylver wrote:
Just seen your patch on LAK, good you managed to make something that is working !

It won't happen without you help, Sylver. Thanks a lot!

BTW the patch was accepted by Nicolas.


Top
   
PostPosted: Mon Sep 29, 2008 3:19 am 
Offline
Regular Member
User avatar

Joined: Fri Jul 25, 2008 3:23 pm
Posts: 160
Location: Kobe, Japan
Still I need to get this accepted:
http://lkml.org/lkml/2008/9/23/473 - it will allow us to read system status from ALARM_B_MIN

This patch would greatly simplify our life:
http://marc.info/?l=linux-arm-kernel&m= ... 528005&w=2
(we would be able to distribute custom firmware for LS Mini without need to access serial port and without any other hacks)


Top
   
PostPosted: Tue Sep 30, 2008 6:56 pm 
Offline
Site Admin
User avatar

Joined: Mon Jul 11, 2005 7:19 am
Posts: 7703
Location: Austria, Vienna
great work.

really nice to see this ongoing development for the LS mini!

_________________
LS1 (2.6 kernel, foonas svn1062, 750 GB, UBoot 1.2) & LS Pro (FreeLink/jtymod/GenLink, changes all the time)
Thx to all donators!


Top
   
PostPosted: Mon May 11, 2009 7:27 pm 
Offline
Newbie

Joined: Mon Aug 25, 2008 6:50 am
Posts: 42
Do you know if you patches will work for LS live v3, too???? V3 uses GPIOs only... so it should be nearly the same hardware (if not an identical board).


Top
   
PostPosted: Sat Jun 13, 2009 8:46 am 
Offline
Regular Member

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

i found out, that the linkstation pro duo has the same hardware like the mini - how I can patch the panel, that it works with duo? Currently I get this message:
Code:
Uncompressing Linux................................................................................................................................. done, booting the kernel.

Error: unrecognized/unsupported machine ID (r1 = 0x00000727).

Available machine support:

ID (hex)        NAME
0000054e        Marvell Orion-2 Development Board
000005e4        Marvell Orion-NAS Reference Design
00000631        Buffalo Linkstation Pro/Live
000005e5        Buffalo/Revogear Kurobox Pro
00000630        Buffalo Terastation Pro II/Live
00000742        Buffalo Linkstation Mini
00000606        D-Link DNS-323
0000061d        QNAP TS-109/TS-209
00000641        QNAP TS-409
00000661        Linksys WRT350N v2
00000674        Technologic Systems TS-78xx SBC
0000069d        HP Media Vault mv2120
000006dc        LaCie Ethernet Disk mini V2
000006e6        Maxtor Shared Storage II
00000709        Netgear WNR854T
00000714        Marvell Orion-VoIP GE Reference Design
0000071a        Marvell Orion-VoIP FXO Reference Design
00000766        Marvell Orion-1-90 AP GE Reference Design

Please check your kernel config and/or bootloader.

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


Top
   
PostPosted: Sun Jun 14, 2009 1:33 pm 
Offline
Regular Member

Joined: Mon Nov 07, 2005 4:37 pm
Posts: 205
Location: Germany
Okay ... I made an "quick and dirty" patch and now I can let run the kernel on my linkstation pro duo - here the first sucessfull start:
Code:
Bytes transferred = 5682190 (56b40e hex)       
## Booting image at 00100000 ... 
   Image Name:   linux           
   Created:      2009-06-14  11:51:36 UTC     
   Image Type:   ARM Linux Kernel Image (uncompressed)     
   Data Size:    2449096 Bytes =  2.3 MB       
   Load Address: 00008000         
   Entry Point:  00008000         
   Verifying Checksum ... OK     
OK     
## Loading Ramdisk Image at 00800000 ...       
   Image Name:   initrd           
   Created:      2009-06-06  20:24:37 UTC     
   Image Type:   ARM Linux RAMDisk Image (gzip compressed) 
   Data Size:    5682126 Bytes =  5.4 MB       
   Load Address: 00000000         
   Entry Point:  00000000         
   Verifying Checksum ... OK     
       
Starting kernel ... 
       
arg:console=ttyS0,115200 mem=64m root=/dev/md1 rw initrd=0x00800040,15M panic=5 BOOTVER=1.13 tftpboot=yes       
Uncompressing Linux..............................................................................................................................................................
Linux version 2.6.30 (manuel@bigbrother) (gcc version 4.2.1 (CodeSourcery Sourcery G++ Lite 2007q3-53)) #2 PREEMPT Sun Jun 14 13:51:25 CEST 2009       
CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a0053177
CPU: VIVT data cache, VIVT instruction cache   
Machine: Buffalo Linkstation Pro Duo           
Clearing invalid memory bank 0KB@0xffffffff   
Clearing invalid memory bank 0KB@0xffffffff   
Clearing invalid memory bank 0KB@0xffffffff   
Ignoring unrecognised tag 0x00000000           
Ignoring unrecognised tag 0x00000000           
Ignoring unrecognised tag 0x00000000           
Ignoring unrecognised tag 0x41000403           
Memory policy: ECC disabled, Data cache writeback           
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256           
Kernel command line: console=ttyS0,115200 mem=64m root=/dev/md1 rw initrd=0x00800040,15M panic=5 BOOTVER=1.13 tftpboot=yes   
NR_IRQS:64           
PID hash table entries: 256 (order: 8, 1024 bytes)         
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)           
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total         
Memory: 59548KB available (4500K code, 394K data, 136K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 
Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104)     
Mount-cache hash table entries: 512           
CPU: Testing write buffer coherency: ok       
net_namespace: 520 bytes         
xor: measuring software checksum speed         
   arm4regs  :   302.000 MB/sec   
   8regs     :   248.000 MB/sec   
   32regs    :   269.200 MB/sec   
xor: using function: arm4regs (302.000 MB/sec)
NET: Registered protocol family 16
Orion ID: MV88F5182-A2. TCLK=166666667.       
lsmini_init: finished
bio: create slab <bio-0> at 0     
SCSI subsystem initialized       
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub   
usbcore: registered new device driver usb     
raid6: int32x1     18 MB/s       
raid6: int32x2     26 MB/s       
raid6: int32x4     33 MB/s       
raid6: int32x8     31 MB/s       
raid6: using algorithm int32x4 (33 MB/s)       
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)           
TCP established hash table entries: 2048 (order: 2, 16384 bytes)         
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)   
TCP: Hash tables configured (established 2048 bind 2048)   
TCP reno registered 
NET: Registered protocol family 1
NetWinder Floating Point Emulator V0.97 (double precision) 
VFS: Disk quotas dquot_6.5.2     
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) 
JFFS2 version 2.2. (NAND) �� 2001-2006 Red Hat, Inc.       
JFS: nTxBlock = 465, nTxLock = 3725           
SGI XFS with ACLs, security attributes, realtime, no debug enabled       
SGI XFS Quota Management subsystem
msgmni has been set to 116       
async_tx: api initialized (async)
io scheduler noop registered     
io scheduler anticipatory registered           
io scheduler deadline registered 
io scheduler cfq registered (default)         
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled   
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3) is a 16550A
console [ttyS0] enabled           
loop: module loaded 
Driver 'sd' needs updating - please use bus_type methods   
sata_mv sata_mv.0: version 1.28   
sata_mv sata_mv.0: slots 32 ports 2           
scsi0 : sata_mv     
scsi1 : sata_mv     
ata1: SATA max UDMA/133 irq 29   
ata2: SATA max UDMA/133 irq 29   
MV-643xx 10/100/1000 ethernet driver version 1.4           
mv643xx_eth smi: probed           
net eth0: port 0 with MAC address 00:00:00:00:51:81         
physmap platform flash device: 00040000 at f4000000         
Found: SST 39LF020   
physmap-flash.0: Found 1 x8 devices at 0x0 in 8-bit bank   
number of JEDEC chips: 1         
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
RedBoot partition parsing not available       
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver 
orion-ehci orion-ehci.0: Marvell Orion EHCI   
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1   
orion-ehci orion-ehci.0: irq 17, io mem 0xf1050000         
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00         
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found       
hub 1-0:1.0: 1 port detected     
orion-ehci orion-ehci.1: Marvell Orion EHCI   
orion-ehci orion-ehci.1: new USB bus registered, assigned bus number 2   
orion-ehci orion-ehci.1: irq 12, io mem 0xf10a0000         
orion-ehci orion-ehci.1: USB 2.0 started, EHCI 1.00         
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found       
hub 2-0:1.0: 1 port detected     
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...       
usbcore: registered new interface driver usb-storage       
USB Mass Storage support registered.           
usbcore: registered new interface driver ums-datafab       
usbcore: registered new interface driver ums-freecom       
usbcore: registered new interface driver ums-jumpshot       
usbcore: registered new interface driver ums-sddr09         
usbcore: registered new interface driver ums-sddr55         
input: gpio-keys as /class/input/input0       
i2c /dev entries driver           
rtc-rs5c372 0-0032: rs5c372a found, 24hr, driver version 0.6
rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
md: linear personality registered for level -1
md: raid0 personality registered for level 0   
md: raid1 personality registered for level 1   
md: raid10 personality registered for level 10
md: raid6 personality registered for level 6   
md: raid5 personality registered for level 5   
md: raid4 personality registered for level 4   
Registered led device: alarm:red 
Registered led device: info:amber
Registered led device: func:blue:top           
Registered led device: power:blue:bottom       
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver   
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )     
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver 
oprofile: using timer interrupt. 
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.         
RPC: Registered tcp transport module.         
VFP support v0.3: not present     
rtc-rs5c372 0-0032: setting system clock to 2009-06-14 12:15:04 UTC (1244981704)     
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)     
ata1.00: ATA-8: WDC WD5000AACS-00G8B1, 05.04C05, max UDMA/133           
ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133 
scsi 0:0:0:0: Direct-Access     ATA      WDC WD5000AACS-0 05.0 PQ: 0 ANSI: 5         
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors: (500 GB/465 GiB) 
sd 0:0:0:0: [sda] Write Protect is off         
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 WD5000AACS-00G8B1, 05.04C05, max UDMA/133           
ata2.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata2.00: configured for UDMA/133 
scsi 1:0:0:0: Direct-Access     ATA      WDC WD5000AACS-0 05.0 PQ: 0 ANSI: 5         
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors: (500 GB/465 GiB) 
sd 1:0:0:0: [sdb] Write Protect is off         
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           
md: Waiting for all devices to be available before autodetect           
md: If you don't use raid, use raid=noautodetect           
md: Autodetecting RAID arrays.   
md: Scanned 8 and added 8 devices.
md: autorun ...     
md: considering sdb6 ...         
md:  adding sdb6 ...
md: sdb5 has different UUID to sdb6           
md: sdb2 has different UUID to sdb6           
md: sdb1 has different UUID to sdb6           
md:  adding sda6 ...
md: sda5 has different UUID to sdb6           
md: sda2 has different UUID to sdb6           
md: sda1 has different UUID to sdb6           
md: created md3     
md: bind<sda6>       
md: bind<sdb6>       
md: running: <sdb6><sda6>         
raid1: raid set md3 active with 2 out of 2 mirrors         
md: considering sdb5 ...         
md:  adding sdb5 ...
md: sdb2 has different UUID to sdb5           
md: sdb1 has different UUID to sdb5           
md:  adding sda5 ...
md: sda2 has different UUID to sdb5           
md: sda1 has different UUID to sdb5           
md: created md2     
md: bind<sda5>       
md: bind<sdb5>       
md: running: <sdb5><sda5>         
raid1: raid set md2 active with 2 out of 2 mirrors         
md: considering sdb2 ...         
md:  adding sdb2 ...
md: sdb1 has different UUID to sdb2           
md:  adding sda2 ...
md: sda1 has different UUID to sdb2           
md: created md1     
md: bind<sda2>       
md: bind<sdb2>       
md: running: <sdb2><sda2>         
raid1: raid set md1 active with 2 out of 2 mirrors         
md: considering sdb1 ...         
md:  adding sdb1 ...
md:  adding sda1 ...
md: created md0     
md: bind<sda1>       
md: bind<sdb1>       
md: running: <sdb1><sda1>         
raid1: raid set md0 active with 2 out of 2 mirrors         
md: ... autorun DONE.
 md1: unknown partition table     
kjournald starting.  Commit interval 5 seconds
EXT3 FS on md1, internal journal 
EXT3-fs: mounted filesystem with writeback data mode.       
VFS: Mounted root (ext3 filesystem) on device 9:1.         
Freeing init memory: 136K         
modprobe: FATAL: Could not load /lib/modules/2.6.30/modules.dep: No such file or directory         
       
modprobe: FATAL: Could not load /lib/modules/2.6.30/modules.dep: No such file or directory         
       
INIT: version 2.86 booting       
* .udev/ already exists on the static /dev!   
Starting the hotplug events dispatcher: udevd.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...done.
GCouldnt get a file descriptor referring to the console     
* Problem when loading /etc/console/boottime.kmap.gz, use install-keymap
Setting parameters of disc: (none).           
Activating swap:swapon on /dev/m md2:d2       
 unknown partition table         
Adding 1003896k swap on /dev/md2.  Priority:-1 extents:1 across:1003896k
.       
Will now check root file system:fsck 1.40-WIP (14-Nov-2006)
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -y -C0 /dev/md1       
e2fsck 1.40-WIP (14-Nov-2006)     
/dev/md1: clean, 52577/626496 files, 351016/1251040 blocks 
.       
EXT3 FS on md1, internal journal 
Setting the system clock..       
Cannot access the Hardware Clock via any known method.     
Use the --debug option to see the details of our search for an access method.         
System Clock set. Local time: Sun Jun 14 12:15:25 UTC 2009.
Cleaning up ifupdown....         
Loading kernel module usb-storage.
FATAL: Could not load /lib/modules/2.6.30/modules.dep: No such file or directory     
Loading kernel module ehci-marvell-hcd.       
FATAL: Could not load /lib/modules/2.6.30/modules.dep: No such file or directory     
Loading kernel module tun.       
FATAL: Could not load /lib/modules/2.6.30/modules.dep: No such file or directory     
FATAL: Could not load /lib/modules/2.6.30/modules.dep: No such file or directory     
Loading device-mapper support.   
 md0: unknown partition table     
 md3: unknown partition table     
Generating udev events for MD arrays...done.   
Will now check all file systems. 
fsck 1.40-WIP (14-Nov-2006)       
Checking all file systems.       
[/sbin/fsck.ext2 (1) -- /boot] fsck.ext2 -y -C0 /dev/md0   
e2fsck 1.40-WIP (14-Nov-2006)     
/dev/md0: clean, 18/125696 files, 7614/250976 blocks       
[/sbin/fsck.ext3 (1) -- /data] fsck.ext3 -y -C0 /dev/md3   
e2fsck 1.40-WIP (14-Nov-2006)     
/dev/md3: clean, 105411/60063744 files, 79634928/120119984 blocks       
Done checking file systems.       
A log is being saved in /var/log/fsck/checkfs if that location is writable.           
Setting kernel variables...done. 
Will now mount local filesystems:mount: none already mounted or /dev/pts busy         
mount: according to mtab, devpts is already mounted on /dev/pts         
kjournald starting.  Commit interval 5 seconds
EXT3 FS on md3, internal journal 
EXT3-fs: mounted filesystem with writeback data mode.       
 failed!
Will now activate swapfile swap:done.         
Checking quotas...done.           
Turning on quotas...modprobe: FATAL: Could not load /lib/modules/2.6.30/modules.dep: No such file or directory 
       
quotaon: using /data/quota.group on /dev/md3 [/data]: No such process   
quotaon: Quota format not supported in kernel.
modprobe: FATAL: Could not load /lib/modules/2.6.30/modules.dep: No such file or directory         
       
quotaon: using /data/quota.user on /dev/md3 [/data]: No such process     
quotaon: Quota format not supported in kernel.
Cleaning /tmp...done.
Cleaning /var/run...done.         
Cleaning /var/lock...done.       
Setting up resolvconf...done.     
Setting up networking....         
* /etc/network/options is deprecated (see README.Debian of netbase).     
Setting up IP spoofing protection...done (rp_filter).       
Configuring network interfaces...modprobe: FATAL: Could not load /lib/modules/2.6.30/modules.dep: No such file or directory 
       
SIOCSIFADDR: No such device       
modprobe: FATAL: Could not load /lib/modules/2.6.30/modules.dep: No such file or directory         
       
eth0: ERROR while getting interface flags: No such device
modprobe: FATAL: Could not load /lib/modules/2.6.30/modules.dep: No such file or directory

SIOCSIFNETMASK: No such device
modprobe: FATAL: Could not load /lib/modules/2.6.30/modules.dep: No such file or directory

SIOCSIFBRDADDR: No such device
modprobe: FATAL: Could not load /lib/modules/2.6.30/modules.dep: No such file or directory

eth0: ERROR while getting interface flags: No such device
modprobe: FATAL: Could not load /lib/modules/2.6.30/modules.dep: No such file or directory

eth0: ERROR while getting interface flags: No such device
Failed to bring up eth0.
done.
Start services: micro_evtd
Starting portmap daemon....
Setting console screen modes and fonts.
Initializing random number generator...done.
Setting up X server socket directory /tmp/.X11-unix....
Setting up ICE socket directory /tmp/.ICE-unix....
INIT: Entering runlevel: 2
grep: /boot/linkstation_release: No such file or directory
err: RecvPacket: readlen=0.
Starting system log daemon: syslogd.
Starting kernel log daemon: klogd.
Starting DNS forwarder and DHCP server: dnsmasqwarning: `dnsmasq' uses 32-bit capabilities (legacy support in use)
.
Starting portmap daemon...Already running..
Starting bfilter: Could not bind to "192.168.100.100:8080"
Updating the operating system logo...done.
FATAL: Could not load /lib/modules/2.6.30/modules.dep: No such file or directory
* Not starting NFS kernel daemon: no support in current kernel.
* Not starting internet superserver: no services enabled.
Starting Postfix Mail Transport Agent: postfix.
Starting Samba daemons: nmbd smbd.
* To enable saslauthd, edit /etc/default/saslauthd and set START=yes
Enabling S.M.A.R.T..../dev/sda...unable to fetch IEC (SMART) mode page [unsupported field in scsi command]
(failed).../dev/sdb...unable to fetch IEC (SMART) mode page [unsupported field in scsi command]
(failed)...done.
Starting S.M.A.R.T. daemon: smartdprogram smartd is using a deprecated SCSI ioctl, please convert it to SG_IO
program smartd is using a deprecated SCSI ioctl, please convert it to SG_IO
 failed!
Starting OpenBSD Secure Shell server: sshd.
Starting NFS common utilities: statdFATAL: Could not load /lib/modules/2.6.30/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.30/modules.dep: No such file or directory
 idmapd.
Starting quota service: rpc.rquotad.
Starting MD monitoring service: mdadm --monitor.
Starting periodic command scheduler: crond.
Running local boot scripts (/etc/rc.local).

BUFFALO INC. LinkStation series LS-GL(IESADA)
lansrv01 login:
What I'd noticed:
  • I can control the leds in /sys
  • If the kernel is booted, the fan goes high - is there an method, control the fan?
  • My custom initramfs isn't booted - so I must configure u-boot for booting md1 (root fs) directly
  • The kernel does detect another MAC address and so udev does create the new device eth1
  • I miss the status information, we can get from the stockkernel in /proc
Here is the patch:
Code:
diff -ru linux-2.6.30/arch/arm/configs/orion5x_defconfig linux-2.6.30.mod//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.mod//arch/arm/configs/orion5x_defconfig        2009-06-13 14:05:34.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 -ru linux-2.6.30/arch/arm/mach-orion5x/Kconfig linux-2.6.30.mod//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.mod//arch/arm/mach-orion5x/Kconfig     2009-06-13 14:01:05.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 -ru linux-2.6.30/arch/arm/mach-orion5x/lsmini-setup.c linux-2.6.30.mod//arch/arm/mach-orion5x/lsmini-setup.c
--- linux-2.6.30/arch/arm/mach-orion5x/lsmini-setup.c   2009-06-10 05:05:27.000000000 +0200
+++ linux-2.6.30.mod//arch/arm/mach-orion5x/lsmini-setup.c      2009-06-13 14:29:17.000000000 +0200
@@ -277,3 +277,17 @@
        .fixup          = tag_fixup_mem32,
 MACHINE_END
 #endif
+
+#ifdef CONFIG_MACH_LINKSTATION_PRODUO
+MACHINE_START(LINKSTATION_PRODUO, "Buffalo Linkstation Pro Duo")
+       /* Maintainer: Alexey Kopytko <alexey@kopytko.ru> */
+       .phys_io        = ORION5X_REGS_PHYS_BASE,
+       .io_pg_offst    = ((ORION5X_REGS_VIRT_BASE) >> 18) & 0xFFFC,
+       .boot_params    = 0x00000100,
+       .init_machine   = lsmini_init,
+       .map_io         = orion5x_map_io,
+       .init_irq       = orion5x_init_irq,
+       .timer          = &orion5x_timer,
+       .fixup          = tag_fixup_mem32,
+MACHINE_END
+#endif
diff -ru linux-2.6.30/arch/arm/mach-orion5x/Makefile linux-2.6.30.mod//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.mod//arch/arm/mach-orion5x/Makefile    2009-06-13 14:04:46.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) += lsmini-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

I've no clue about kernel development - so I would need a little bit assistance, make the kernel more duo compliant ;-)

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


Top
   
PostPosted: Sun Jun 14, 2009 2:26 pm 
Offline
Newbie

Joined: Mon Aug 25, 2008 6:50 am
Posts: 42
I wonder If Mini, Duo and LS-CHL (live v3) share the same GPIOs (Buttons & Leds & Power).... Will try to compile a kernel for Mini and run it using uboot on LS-CHL ... ;)


Top
   
PostPosted: Mon Jun 15, 2009 1:01 pm 
Offline
Regular Member

Joined: Mon Nov 07, 2005 4:37 pm
Posts: 205
Location: Germany
Now ... i'm happy, that all this devices use the same implementation - so I got support for my duo and when the newer kernels run on my device, I can also use a newer debian distribution ;-)
For people with knowledge about it:
Code:
Clearing invalid memory bank 0KB@0xffffffff   
Clearing invalid memory bank 0KB@0xffffffff   
Clearing invalid memory bank 0KB@0xffffffff   
Ignoring unrecognised tag 0x00000000           
Ignoring unrecognised tag 0x00000000           
Ignoring unrecognised tag 0x00000000           
Ignoring unrecognised tag 0x41000403 
I use an old duo model which only have 64M - i think the kernel tries to address here higher memory regions which are not available, or?

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


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

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 3 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