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?
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 18.104.22.168 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
# 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).
The above instructions worked for me on the 2.6.26 debian kernel, 22.214.171.124 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"