Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Sun Sep 04, 2011 4:09 pm

All times are UTC [ DST ]




Post new topic Reply to topic  [ 55 posts ]  Go to page Previous  1, 2, 3, 4  Next
Author Message
PostPosted: Sun Apr 04, 2010 3:55 pm 
Offline
Regular Member

Joined: Tue Sep 09, 2008 10:28 pm
Posts: 199
at least some-one now shows some interest, would it be of use to others ? as far as I know this systemboard is used in the spd8020 from Philips and the lacie network space (version 1)

My and pbg4 efforts only add 88F6082 support to the orion5x kernel.
However this orin5x kernel will be suitable for many popular devices out there, as other Lacies, linkstations etc etc
Compiling the newest kernel for my box becomes easy now, its amazing what this little box with its tiny memory still can do.


Top
 Profile  
 
PostPosted: Mon Apr 05, 2010 7:44 pm 
Offline
Newbie

Joined: Mon Apr 05, 2010 7:35 pm
Posts: 7
Location: Breda, The Netherlands
fvdw are you willing to share your setup file?

I have a Lacie Network Space and would like to test the compatibility. I already tested the patches pbg4 posted before and I got it to boot. However if you already have the GPIO pins it seems like a waste of time for em to re-invent the wheel :) I'm looking forward to finishing the support and make it run on all the 88F6082 boards :)


Top
 Profile  
 
PostPosted: Tue Apr 06, 2010 9:11 pm 
Offline
Regular Member

Joined: Tue Sep 09, 2008 10:28 pm
Posts: 199
Maybe I will do that but I am currently still testing, furthermore I posted regular here also with some questions but I did not get much support, I saw many people viewed the topic, but no help so I am a little disappointed about that, its a lot of work you know :p .
The trick is not so much knowing which gpio pins does what, but more how to use them in your firmware and how to adapt several daemons in the firmware that make use of them. As you might know I have " developed' a home made firmware for the spd8020 and lacie network space (vs1), my plan is to release a new kernel together with an updated firmware, the one doesn't go without the other.


Top
 Profile  
 
PostPosted: Tue Apr 06, 2010 9:32 pm 
Offline
Newbie

Joined: Mon Apr 05, 2010 7:35 pm
Posts: 7
Location: Breda, The Netherlands
I was not aware you made one for the Lacie NS. Where would i go to find it?

EDIT: Another quick question. Did you get the reboot and shutdown working using a daemon aswell?


Top
 Profile  
 
PostPosted: Tue Apr 06, 2010 10:46 pm 
Offline
Regular Member

Joined: Tue Sep 09, 2008 10:28 pm
Posts: 199
Mavy wrote:
I was not aware you made one for the Lacie NS. Where would i go to find it?

EDIT: Another quick question. Did you get the reboot and shutdown working using a daemon aswell?


To get the fvdw firmware you have to go to the convopit forum there is a sticky in the convopit computer section of the forum specific for the lacie network space

http://convopit.org/forum3/viewtopic.php?f=120&t=21953

It gives also a nice how to install guide and much more info like screen shots of the firmware and tips and tricks, experiences of other.
PS Convopit website seem to have a problem this evening server is down on the moment but I am sure the site admin will sort this problem soon and that the website will be up again on short notice.

To your second question , yep I got the buttons also working in the spd8020 using a daemon, that was one of the difficult parts, to let it communicate properly with the kernel.
I don't know if this buttons daemon will also work on the the network space, as I can not test it as I don't own a network space. But in the previous release of my firmware nobody complained about it that it didn't work so I guess the new daemon will work as well on the network space. Only testing will tell.

PS this kernel only will run on the network space vs 1 as that has a 88F6082 board.
The lacie netwok space vs 2 or lacie internet space can not use this kernel as they have different hardware, but they can run the rest of the fvdw firmware using the original kernel od lacie. See more info in the convopit forum. of course board specific daemons like buttons and fan control will probably not work in that case.
Looking to the hardware in the network space 2 and internet space it should not be to difficult to compile a newer kernel for these boxes using the orion5x git


Top
 Profile  
 
PostPosted: Tue Apr 06, 2010 10:49 pm 
Offline
Newbie

Joined: Mon Apr 05, 2010 7:35 pm
Posts: 7
Location: Breda, The Netherlands
Just a quick message with my current kernel booting Debian on the Lacie NS. It boots and runs fine.

Code:

Bootstrap 02.09
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
_   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/    |____/ \___/ \___/ \__|  ** LOADER **
** MARVELL BOARD: RD-88F6082-MICRO-DAS-NAS LE

U-Boot 1.1.4 (Feb  8 2008 - 09:08:25) Lacie version: 2.4.2-TINY

U-Boot code: 00200000 -> 0023EE00  BSS: -> 0024D2D0

Soc: 88F6082 A1 (DDR1)
CPU running @ 333Mhz
SysClock = 166Mhz , TClock = 133Mhz

DRAM CS[0] base 0x00000000   size   8MB
DRAM CS[1] base 0x00800000   size   8MB
DRAM Total size  16MB  16bit width
Memory test pattern: 0x55555555, 0xAAAAAAAA,  Pass
[256kB@f8100000] Flash: 256 kB
Addresses 4M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (4M - 3M): Done

CPU : ARM926 (Rev 0)
gpiovalue:3CE1

USB 0: host mode
PCI 0: PCI Express Root Complex Interface
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  3  2  1  0
Waiting for LUMP (2)
no lump receive; continuing

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
  Device 0: OK
Model: ST31000333AS                             Firm: LC15     Ser#:             9TE0S4QR
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)


Loading from IDE device 0, partition 6: Name: hda6
  Type: U-Boot
   Image Name:   linux
   Created:      2010-04-06  20:31:08 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1923892 Bytes =  1.8 MB
   Load Address: 00008000
   Entry Point:  00008000
## Booting image at 00400000 ...
   Image Name:   linux
   Created:      2010-04-06  20:31:08 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1923892 Bytes =  1.8 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.34-rc2-00017-g5efda86-dirty (root@debian-dev) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 PREEMPT Tue Apr 6 22:30:26 CEST 2010
CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a0053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Lacie Network Space V1
Clearing invalid memory bank 0KB@0x00000000
Clearing invalid memory bank 0KB@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 off.  Total pages: 4064
Kernel command line: console=ttyS0,115200 root=/dev/sda7 ro boardType=mv88F6082 productType=Aston reset=0
PID hash table entries: 64 (order: -4, 256 bytes)
Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
Memory: 8MB 8MB = 16MB total
Memory: 12072k/12072k available, 4312k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xc1800000 - 0xfd800000   ( 960 MB)
    lowmem  : 0xc0000000 - 0xc1000000   (  16 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc0028000   ( 128 kB)
      .text : 0xc0028000 - 0xc03a0000   (3552 kB)
      .data : 0xc03de000 - 0xc03fc380   ( 121 kB)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:64
start_kernel(): bug: interrupts were enabled early
Calibrating delay loop... 218.72 BogoMIPS (lpj=1093632)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Orion ID: Device-Unknown. TCLK=133333333.
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 512 (order: 0, 4096 bytes)
TCP bind hash table entries: 512 (order: -1, 2048 bytes)
TCP: Hash tables configured (established 512 bind 512)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
msgmni has been set to 23
io scheduler noop 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
sata_mv sata_mv.0: version 1.28
sata_mv sata_mv.0: slots 32 ports 1
scsi0 : sata_mv
ata1: SATA max UDMA/133 irq 29
physmap platform flash device: 00040000 at f8100000
physmap-flash physmap-flash.0: map_probe failed
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
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
hub 1-0:1.0: USB hub found
hub 1-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
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
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
VFP support v0.3: not present
rtc-rs5c372 0-0032: setting system clock to 2010-04-06 22:22:07 UTC (1270592527)
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-8: ST31000333AS, LC15, 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      ST31000333AS     LC15 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 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 < sda5 sda6 sda7 > sda2
sd 0:0:0:0: [sda] Attached SCSI disk
EXT3-fs (sda7): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) readonly on device 8:7.
Freeing init memory: 128K
kjournald starting.  Commit interval 5 seconds

INIT: version 2.86 booting

.udev/ already exists on the static /dev! (warning).
Starting the hotplug events dispatcher: udevd.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...udev: renamed network interface eth0 to eth1
done.
Setting the system clock.
Activating swap...Adding 256972k swap on /dev/sda5.  Priority:-1 extents:1 across:256972k
done.
Checking root file system...fsck 1.41.3 (12-Oct-2008)
/dev/sda7: clean, 9571/124672 files, 78424/498007 blocks
done.
EXT3-fs (sda7): using internal journal
Setting the system clock.
Cleaning up ifupdown....
Loading kernel modules...done.
Checking file systems...fsck 1.41.3 (12-Oct-2008)
/sbin/fsck.xfs: XFS file system.
done.
Setting kernel variables (/etc/sysctl.conf)...done.
Mounting local filesystems...mount: unknown filesystem type 'xfs'
failed.
Activating swapfile swap...done.
Setting up networking....
Configuring network interfaces...done.
eth1: link up, 1000 Mb/s, full duplex, flow control disabled

INIT: Entering runlevel: 2

Starting enhanced syslogd: rsyslogd.
Starting OpenBSD Secure Shell server: sshd.
Starting periodic command scheduler: crond.

Debian GNU/Linux 5.0 lacie ttyS0

lacie login:


As you can see XFS is not working yet. When adding xfs to the kernel it will fail to boot. I have yet to try the module.
Apart from xfs the only real problems are reboot and shutdown not actually turning of the board (HDD spins down).

The led is a nice to have but not a must.

PS: The link you posted is giving a 404.


Top
 Profile  
 
PostPosted: Tue Apr 06, 2010 10:59 pm 
Offline
Regular Member

Joined: Tue Sep 09, 2008 10:28 pm
Posts: 199
Mavy wrote:


As you can see XFS is not working yet. When adding xfs to the kernel it will fail to boot. I have yet to try the module.
Apart from xfs the only real problems are reboot and shutdown not actually turning of the board (HDD spins down).

The led is a nice to have but not a must.

PS: The link you posted is giving a 404.



yes I know about the 404, convopit is down at the moment see my remark. It will be back soon I expect, sorry for that.

I did not test xfs as I do not use it but I have the module, I compiled the kernel with loading it manual. I will try if it loads.


Top
 Profile  
 
PostPosted: Tue Apr 06, 2010 11:03 pm 
Offline
Newbie

Joined: Mon Apr 05, 2010 7:35 pm
Posts: 7
Location: Breda, The Netherlands
Just re-read your post and noticed the remark. Apologies.

Just tested loading xfs as a module and that works just fine. I will do some debugging tomorrow to find out what is causing it to fail when in the kernel.


Last edited by Mavy on Tue Apr 06, 2010 11:06 pm, edited 1 time in total.

Top
 Profile  
 
PostPosted: Tue Apr 06, 2010 11:06 pm 
Offline
Regular Member

Joined: Tue Sep 09, 2008 10:28 pm
Posts: 199
confirmed: xfs module seems to load fine in my kernel as well

Code:
~ # insmod /boot/xfs.ko
SGI XFS with security attributes, large block/inode numbers, no debug enabled
~ #


Top
 Profile  
 
PostPosted: Tue Apr 06, 2010 11:08 pm 
Offline
Newbie

Joined: Mon Apr 05, 2010 7:35 pm
Posts: 7
Location: Breda, The Netherlands
Next step is to get the board to reboot instead of hang and halt.

Code:
Will now restart.
sd 0:0:0:0: [sda] Synchronizing SCSI cache
Restarting system.
Reboot failed -- System halted


Top
 Profile  
 
PostPosted: Tue Apr 06, 2010 11:30 pm 
Offline
Regular Member

Joined: Tue Sep 09, 2008 10:28 pm
Posts: 199
it can be done... ;)

Code:
~ #
~ # reset button pressed for more then 1 seconds. Executing reboot now...

Bootstrap 02.09
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
_   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/    |____/ \___/ \___/ \__|  ** LOADER **
** MARVELL BOARD: RD-88F6082-NAS-PH LE

U-Boot 1.1.4 (Apr 10 2007 - 14:27:58) Marvell version: 2.3.9_2-TINY

U-Boot code: 00200000 -> 0023EE00  BSS: -> 0024CF30

Soc: MV88F6082 Rev 1 (DDR1)
CPU running @ 333Mhz
SysClock = 166Mhz , TClock = 133Mhz

DRAM CS[0] base 0x00000000   size   8MB
DRAM CS[1] base 0x01000000   size   8MB
DRAM Total size  16MB  16bit width
[256kB@f8100000] Flash: 256 kB
Addresses 4M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (4M - 3M): Done

CPU : ARM926 (Rev 0)

USB 0: host mode
PCI 0: PCI Express Root Complex Interface
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found

  Device 0: OK
Model: Hitachi HDP725050GLA360                  Firm: GM4OA52A Ser#:       GEA530RE0NBSLE
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)

ext2load ide 0:2 1000000 /boot/uImage

1845408 bytes read
bootm 1000000
## Booting image at 01000000 ...
   Image Name:   Linux-2.6.33.1
   Created:      2010-04-05  13:22:23 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1845344 Bytes =  1.8 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.33.1 (root@linux-fw1) (gcc version 4.2.0 20070413 (prerelease) (CodeSourcery Sourcery G++ Lite 2007q1-21)) #45 PREEMPT Mon Apr 5 15:22:10 CEST 2010
CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a0053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Philips NAS SPD8020 CC


Top
 Profile  
 
PostPosted: Wed Apr 07, 2010 11:24 am 
Offline
Newbie

Joined: Mon Apr 05, 2010 7:35 pm
Posts: 7
Location: Breda, The Netherlands
The NSv1 does not have a reset button. I need a way to reboot from command line.
I will have a look at the code tonight.

PS: The convopit registration is broken.


Top
 Profile  
 
PostPosted: Wed Apr 07, 2010 1:02 pm 
Offline
Regular Member

Joined: Tue Sep 09, 2008 10:28 pm
Posts: 199
The reboot as performed via buttons can also be from the command line.

The linux standard reboot command doesn't work for this board as it uses a non standard reset procedure. The mach-orion code uses a standard procedure/command supported by many board but unfortunately this board doesn't support those commands.
The reboot procedure and commands must be coded in the kernel specific for this board.


Top
 Profile  
 
PostPosted: Wed Apr 07, 2010 1:14 pm 
Offline
Newbie

Joined: Mon Apr 05, 2010 7:35 pm
Posts: 7
Location: Breda, The Netherlands
Any idea where i can find this info?


Top
 Profile  
 
PostPosted: Wed Apr 07, 2010 2:33 pm 
Offline
Regular Member

Joined: Tue Sep 09, 2008 10:28 pm
Posts: 199
yes I figured it out how to make it work, but I will not publish it right now, I am still modyfying

convopit registration is working again


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

All times are UTC [ DST ]


Who is online

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

Protected by Anti-Spam ACP
Protected by Anti-Spam ACP Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group