Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Mon May 21, 2018 12:34 am

All times are UTC+01:00




Post new topic  Reply to topic  [ 57 posts ]  Go to page 1 2 3 4 Next
Author Message
PostPosted: Sun Nov 30, 2008 6:27 pm 
Offline
Newbie

Joined: Mon Nov 17, 2008 12:23 am
Posts: 38
Location: Stuttgart, Germany
Hi,

I'm trying to compile a kernel for the LS-CHL, but I fail.

Therefore, I provide some information on the LS-CHL here. Maybe someone has an idea how to adjust the kernel configuration to let the self-made kernel run on the LS-CHL.

A good start seem to be following articles

I followed the last one, but the kernel does not boot.
Replacing the first 8 bytes (you know, the devio-patch) by the first 8 bytes of the original uImage.buffalo didn't help either.

Besides the hardware info listed in the Wiki (http://buffalo.nas-central.org/index.php?title=Category:LS-CHL), I found following information browsing through dmesg:
  • Marvell USB EHCI Host controller, Marvell Ethernet Driver 'mv_ethernet', Marvell SCSI to SATA adapter,
  • MICON ctrl (C) BUFFALO INC. V.1.00 installed.
  • Buffalo CPU Inerupts Driver (C) BUFFALO INC. Ver.0.01 alpha1 installed.
  • Buffalo Gpio Control Driver (C) BUFFALO INC. Ver.0.02 installed.

Since I'm not that hardware expert, I just notice down all the information contained on the chips on the board:
  • 88F5-BEG1 - GW73451A.0 - 0803 A2E - TW - 88f5182-A2 - C400
  • 80E+11B-NNC1 - GZ11221.3 - 0824 A1P - TW
  • nanya 0741 - NT5TU32M16AG-3C - 727138R1BV TW (exists 2 times)
  • SST LSC01 - 39VF020 - 70-4C-WHE - 0826073-G
  • V25.00 - KDSH 8F

Maybe that information is useful for someone?

Finally, I wonder why the GPL-code of the most recent firmware cannot be found at http://www.buffalotech.com/files/downloads/Buffalo_GPL.html. Do I really have to spend 20€ to order the source?

Cheers


Top
   
PostPosted: Mon Dec 01, 2008 1:23 pm 
Offline
Total Newbie

Joined: Mon Aug 25, 2008 2:27 pm
Posts: 2
hi dsplayer

You can get the source of LS-CHL from here
http://opensource.buffalo.jp/ls-chl-102.html


Top
   
PostPosted: Sun Mar 29, 2009 12:58 am 
Offline
Newbie

Joined: Mon Nov 17, 2008 12:23 am
Posts: 38
Location: Stuttgart, Germany
The 2.6.26 from ftp://ftp.dmik.org/pub/common/buffalo/lspro/davy_gravy/ works also at LS-CHL / lenny.

2.6.16.57-lsp_eabi-dh_v works, too.

Thanx to viewtopic.php?f=18&t=16251&start=0

However, USB does not work here for both kernels...


Top
   
PostPosted: Sun Mar 29, 2009 2:33 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
OK, I've been slacking off lately... time to build a 2.6.28.8+ for armel boxes ... w/ ext4 support...

_________________
LS1 (foonas, nfs, Tranmission & p910nd print server, Firefly for my Roku)
LS-HG500 (Lenny)
Various LS-Pros v1,v2 (unbricked w/ serial & jtag)
KuroPro, LS2 & KuroHG (foonas)
Working on davysweather.dyndns.org lately...

=> wooohooo!
wooohooo!
Unknown command 'wooohooo!' - try 'help'


Top
   
PostPosted: Mon Mar 30, 2009 8:26 pm 
Offline
Newbie

Joined: Mon Nov 17, 2008 12:23 am
Posts: 38
Location: Stuttgart, Germany
davy_gravy wrote:
OK, I've been slacking off lately... time to build a 2.6.28.8+ for armel boxes ... w/ ext4 support...

Yes, please :). Maybe you could post/link your .config here or give some hints/links of your compiling procedure...

I found a German cross-compile howto for Ubuntu 8.10, but did not succeed yet. :(


Top
   
PostPosted: Mon Mar 30, 2009 11:03 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
well, I'm working on it ... I built 2.6.28.8 and 2.6.29 but oddly, neither kernel/module set would boot - strange since this is the same setup I used for 2.6.25.6-2.6.27.8.

I will retry with a pull of OE dev tonight and see if that helps any ... http://wiki.openembedded.net/index.php/Main_Page is what I am using ... or the foonas fork @ foonas.org

_________________
LS1 (foonas, nfs, Tranmission & p910nd print server, Firefly for my Roku)
LS-HG500 (Lenny)
Various LS-Pros v1,v2 (unbricked w/ serial & jtag)
KuroPro, LS2 & KuroHG (foonas)
Working on davysweather.dyndns.org lately...

=> wooohooo!
wooohooo!
Unknown command 'wooohooo!' - try 'help'


Top
   
PostPosted: Fri May 29, 2009 7:00 am 
Offline
Newbie

Joined: Mon Aug 25, 2008 6:50 am
Posts: 42
@lb_worm, davy_gravy:

What's up with LS-CHL Kernel support? Will it be supported in final 2.6.30? And is there a list of the used GPIOs? :)

Balou1974


Top
   
PostPosted: Wed Jun 17, 2009 4:40 pm 
Offline
Total Newbie

Joined: Wed Jun 17, 2009 4:36 pm
Posts: 3
Which .config file did you use to complie the stock kernel for LS-CHL?

Thanks in advance,


Top
   
PostPosted: Wed Jun 17, 2009 9:10 pm 
Offline
Regular Member

Joined: Mon Nov 07, 2005 4:37 pm
Posts: 205
Location: Germany
So far I read, the LS-CHL has the same hardware base like the mini and pro duo - maybe my "duo kernel intention" here could be also helpfull for ls-chl ?

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


Top
   
PostPosted: Thu Jun 18, 2009 4:23 am 
Offline
Newbie

Joined: Mon May 25, 2009 4:11 pm
Posts: 30
dsplayer wrote:
Hi,

I'm trying to compile a kernel for the LS-CHL, but I fail.

Therefore, I provide some information on the LS-CHL here. Maybe someone has an idea how to adjust the kernel configuration to let the self-made kernel run on the LS-CHL.

A good start seem to be following articles

I followed the last one, but the kernel does not boot.
Replacing the first 8 bytes (you know, the devio-patch) by the first 8 bytes of the original uImage.buffalo didn't help either.

Besides the hardware info listed in the Wiki (http://buffalo.nas-central.org/index.php?title=Category:LS-CHL), I found following information browsing through dmesg:
  • Marvell USB EHCI Host controller, Marvell Ethernet Driver 'mv_ethernet', Marvell SCSI to SATA adapter,
  • MICON ctrl (C) BUFFALO INC. V.1.00 installed.
  • Buffalo CPU Inerupts Driver (C) BUFFALO INC. Ver.0.01 alpha1 installed.
  • Buffalo Gpio Control Driver (C) BUFFALO INC. Ver.0.02 installed.

Since I'm not that hardware expert, I just notice down all the information contained on the chips on the board:
  • 88F5-BEG1 - GW73451A.0 - 0803 A2E - TW - 88f5182-A2 - C400
  • 80E+11B-NNC1 - GZ11221.3 - 0824 A1P - TW
  • nanya 0741 - NT5TU32M16AG-3C - 727138R1BV TW (exists 2 times)
  • SST LSC01 - 39VF020 - 70-4C-WHE - 0826073-G
  • V25.00 - KDSH 8F

Maybe that information is useful for someone?

Finally, I wonder why the GPL-code of the most recent firmware cannot be found at http://www.buffalotech.com/files/downloads/Buffalo_GPL.html. Do I really have to spend 20€ to order the source?

Cheers



I found this via google cache. It may be of help to you.

"== Make your own kernel. ==

--> if you want to compile your own kernel.
To compile your own kernel. do the following ->
1. download the latest stable kernel (or other if you want its up to you) from kernel.org, check the sig (gpg) / verify the download.
2. extract it. I would make it owned by a user other than root and then use that user to do the next few steps (you do not have to, you could do it as root).
3. cd into the extracted kernel folder.
4. make clean.
5. copy the configuration from Davey's 2.6.27.4 kernel to the folder (checking who it is owned by). (should be in /boot/config kernel...
6. make menuconfig -> load up davey's config options (this just makes things faster you could configure it your self -> up to you).
7. make your changes ....
8. make zImage
9.
-->
# The version number at the end of each line is the kernel version that first
# supported that device. Run only the line that corresponds to your device:
devio > foo 'wl 0xe3a01c06,4' 'wl 0xe3811031,4' # Linkstation Pro/Live (2.6.26)
//

10.cat foo arch/arm/boot/zImage > zImage.new
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n 'linux' -d zImage.new uImage.new
rm foo zImage.new

11. The new uImage will be called uImage.new, copy this to its destination. For a Linkstation/Kuro this is the /boot/uImage.buffalo.
(you are not done yet).

12. make modules
13. make modules_install
14. Remember to adjust the link / what you have uImage.buffalo as... You should name uImage.new something like uImage.2.6.2XXX(kernel version).
15. reboot.
16 ?????
17. profit.

//
The above instructions worked for me on the 2.6.26 debian kernel, 2.6.27.10 kernel and the 2.6.28 kernel.

This is taken from the other pages on this wiki with a few adjustments -> note this was done on the linkstation pro v2. I used a screen session when compiling, as it takes a few hours for the linkstation to compile the kernel.

// for reference
(for other devices). -> this is taken from the wiki.
devio > foo 'wl 0xe3a01c05,4' 'wl 0xe38110e5,4' # Kurobox Pro (2.6.25)
devio > foo 'wl 0xe3a01c06,4' 'wl 0xe381101d,4' # QNAP TS-109/TS-209 (2.6.25)
devio > foo 'wl 0xe3a01c06,4' 'wl 0xe3811041,4' # QNAP TS-409 (2.6.27?)
devio > foo 'wl 0xe3a01c06,4' 'wl 0xe3811006,4' # D-Link DNS-323 (2.6.25)
devio > foo 'wl 0xe3a01c06,4' 'wl 0xe381109d,4' # HP Media Vault MV2120 (2.6.27?)
devio > foo 'wl 0xe3a01c06,4' 'wl 0xe3811074,4' # Technologic Systems TS-78xx SBC (2.6.27?)
devio > foo 'wl 0xe3a01c06,4' 'wl 0xe3811061,4' # Linksys WRT350N v2 (2.6.27?)
devio > foo 'wl 0xe3a01c07,4' 'wl 0xe3811027,4' # Buffalo Linkstation Pro Duo (Is this right?)
devio > foo 'wl 0xe3a01c07,4' 'wl 0xe3811042,4' # Buffalo Linkstation Mini
devio > foo 'wl 0xe3a01c06,4' 'wl 0xe3811030,4' # Buffalo TS Pro V2 (not yet supported in Vanilla 2.6.26 as of Aug. 10th, 2008)
devio > foo 'wl 0xe3a01c07,4' 'wl 0xe3811065,4' # Netronix NH-233"


Top
   
PostPosted: Sun Jun 28, 2009 7:19 pm 
Offline
Newbie

Joined: Fri Jun 26, 2009 1:24 pm
Posts: 6
Does anyone know the default .config for the stock kernel provided on buffalo's page? I want to recompile the stock kernel and don't want to brick my LS-CHL again.


Top
   
PostPosted: Thu Aug 20, 2009 9:07 pm 
Offline
Total Newbie

Joined: Tue Aug 04, 2009 9:32 pm
Posts: 4
The Linux kernel source contains a script called "extract-ikconfig" which extracts the kernel configuration from a (b)zImage.

The Buffalo stock kernel however is a uImage (generated with mkimage from "Das U-Boot").

What we need is either a way to convert a uImage to a (b)zImage or a modified version of "extract-ikconfig".

Before I dive deeper into the latter: Anyone with an idea on how to convert the image?


Top
   
PostPosted: Tue Dec 15, 2009 12:16 pm 
Offline
Newbie

Joined: Sat Mar 17, 2007 12:45 pm
Posts: 10
Location: United Kingdom (Great Britain)
Well I have reached the same point as above.

I have got a clean compile of 2.6.32 but at this point can't figure out the 'devio' values or get anything meaningful from 'extract-ikconfig'. I did a native compile on one of my LS-CHLv2's so no cross compile issues.

What I did find useful was the 'make menuconfig' utility. I loaded the '.config' files from the 2.6.31 version for the Orion based linkstation and modified it using the Kirkwood and 'dmesg' output options. as it is a first time for me, I undoubtedly have something wrong. But now I'm stuck!

BTW I found http://www.debianadmin.com/step-by-step-tutorial-howto-compile-kernel-in-debian-5-0-lenny.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+DebianAdmin+%28Debian+Admin%29 useful. I guess the Gnome GUI menuconfig is only suitable for cross compilation.

I have been trying to figure out the 'devio' byte values but cannot co-relate to version numbers. Plainly the output file 'foo' contains the 8 bytes (only) taken from the two 32 bit words in little endian form. I can't find a decent how-to about using devio in conjunction with the LS values. Not sure that anything to do with the Sheevaplug helps. Anyone?

Once we have a good 'zImage.new', the 'mkimage' parameters might need attention. Again a first time so anyone able to advise?

On a general note, it is a pity that the LS-CHLv2 is limited to 64Mb RAM and no possibility of adding or changing the RAM. I don't fancy changing a BGA RAM chip! It seems the Sheevaplug can have 512Mb which would certainly reduce the number of disk access for virtual memory. But then I guess the LS-CHL is intended just as a NAS box and the Sheevaplug for home automation without a disk.


Top
   
PostPosted: Wed Jan 06, 2010 9:38 am 
Offline
Regular Member
User avatar

Joined: Fri Jul 25, 2008 3:23 pm
Posts: 160
Location: Kobe, Japan
dsplayer wrote:
However, USB does not work here for both kernels...

I'd bet it is disabled by default and should have manually enabled via MICON or by means of GPIO just like on the LS Mini.

Have you read my crosscompiling guide?
Personally I am working on Debian because it is stable and use a descent Gentoo chroot for the crosscompiling.

Also, if you ever need to deal with GPIO, this could help:
http://buffalo.jpfast.net/mpp.php


Top
   
PostPosted: Wed Jan 06, 2010 9:41 am 
Offline
Regular Member
User avatar

Joined: Fri Jul 25, 2008 3:23 pm
Posts: 160
Location: Kobe, Japan
apemberton wrote:
I have been trying to figure out the 'devio' byte values but cannot co-relate to version numbers

And yes, you can chop required number of bytes from the stock kernel with dd.


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

All times are UTC+01:00


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:
Powered by phpBB® Forum Software © phpBB Limited