Linux 3.3.2 kernel for Dockstar, GoFlex and many others

Tested in: Dockstar, GoFlex Net/Home, Pogoplug E02/V2, Zyxel NSA320

Requirements/Compatibility:

• Hardware: Any mainline-Linux-supported Kirkwood machine, plus many others: both SheevaPlugs, Cloud Engines Pogoplug V1/V2/V4, Seagate Dockstar & GoFlexNet/Home, the Zyxel NSA3x0 variants, QNAP TS-219/41x, all 3 OpenRD boards, all 4 LaCie (Inter)Netspace variants, HP's T5325 ThinClient, and all 4 original Marvell xx88F6xxx boards.
• U-Boot: U-Boot with L2-Cache Disable@Boot Feature, or a machine with a U-Boot that will correctly decompress a 3.2 (or higher) kernel, load it, and boot it.

Capabilities/Configuration: conforms to standard Debian Kirkwood kernel, but with added support for GoFlex Net (with SATA & LED support & fix for the NAND bad blocks symptoms). Will work fine on Pogoplug E02/V2 and Pogoplug E01/V1, but without perfect LED support. The kernel config file is here: config-3.3.2-dg-wide

Installation/Overview: the general steps are as follows:

1. prepare yourself and know what to do in case something goes wrong, before it goes wrong - read and understand - accept all responsibility for installing/using this kernel, since while it has been tested, there is no warranty, either implied or expressed
2. have either UART/serial connection or Netconsole connection and know how to use it
3. back up your current /boot dir in case there is some unforeseen problem
4. download kernel package and copy it to the root directory of your Kirkwood device
5. install kernel package
6. prepare uImage and uInitrd for U-Boot
7. reboot & check

Installation/Details/Commands:

# backup your /boot dir 
cd /
cp -r boot boot-backup



# get the kernel .deb  :    
# download it and copy it to the / (root) directory of your kirkwood device - via network, USB device, etc.



# install it
dpkg -i linux-image-3.3.2-kirkwood-dg_1.1_armel.deb


# prepare it for U-Boot
cd /boot
mkimage -A arm -O linux -T kernel  -C none -a 0x00008000 -e 0x00008000 -n Linux-3.3.2 -d vmlinuz-3.3.2-kirkwood-dg uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.3.2-kirkwood-dg -d initrd.img-3.3.2-kirkwood-dg uInitrd



# reboot and check
reboot
# monitor behavior via serial/UART console, or via Netconsole & check 
uname -a 

Expected Output Sample/Proof Install

root@AirDisk2:/# uname -a
Linux AirDisk2 3.2.0-2-kirkwood #1 Mon Mar 5 17:06:08 UTC 2012 armv5tel GNU/Linux
root@AirDisk2:/# cd /
root@AirDisk2:/# cp -r boot boot-backup
root@AirDisk2:/# cp /home/timemachine/linux-image-3.3.2-kirkwood-dg_1.1_armel.deb  .
root@AirDisk2:/# dpkg -i linux-image-3.3.2-kirkwood-dg_1.1_armel.deb
Selecting previously unselected package linux-image-3.3.2-kirkwood-dg.
(Reading database ... 47094 files and directories currently installed.)
Unpacking linux-image-3.3.2-kirkwood-dg (from linux-image-3.3.2-kirkwood-dg_1.1_armel.deb) ...
Done.
Setting up linux-image-3.3.2-kirkwood-dg (1.1) ...

 Hmm. There is a symbolic link /lib/modules/3.3.2-kirkwood-dg/build
 However, I can not read it: No such file or directory
 Therefore, I am deleting /lib/modules/3.3.2-kirkwood-dg/build


 Hmm. The package shipped with a symbolic link /lib/modules/3.3.2-kirkwood-dg/source
 However, I can not read the target: No such file or directory
 Therefore, I am deleting /lib/modules/3.3.2-kirkwood-dg/source

Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.3.2-kirkwood-dg /boot/vmlinuz-3.3.2-kirkwood-dg
update-initramfs: Generating /boot/initrd.img-3.3.2-kirkwood-dg
run-parts: executing /etc/kernel/postinst.d/zz-flash-kernel 3.3.2-kirkwood-dg /boot/vmlinuz-3.3.2-kirkwood-dg
root@AirDisk2:/# cd /boot
root@AirDisk2:/boot# mkimage -A arm -O linux -T kernel  -C none -a 0x00008000 -e 0x00008000 -n Linux-3.3.2 -d vmlinuz-3.3.2-kirkwood-dg uImage
Image Name:   Linux-3.3.2
Created:      Sat Apr 21 22:20:24 2012
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    2277984 Bytes = 2224.59 kB = 2.17 MB
Load Address: 00008000
Entry Point:  00008000
root@AirDisk2:/boot# mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.3.2-kirkwood-dg -d initrd.img-3.3.2-kirkwood-dg uInitrd
Image Name:   initramfs-3.3.2-kirkwood-dg
Created:      Sat Apr 21 22:20:30 2012
Image Type:   ARM Linux RAMDisk Image (gzip compressed)
Data Size:    7576044 Bytes = 7398.48 kB = 7.23 MB
Load Address: 00000000
Entry Point:  00000000
root@AirDisk2:/boot# reboot

Broadcast message from root@AirDisk2 (pts/0) (Sat Apr 21 22:21:04 2012):

The system is going down for reboot NOW!
root@AirDisk2:/boot# Connection to ***.***.**.*** closed by remote host.
Connection to ***.***.**.*** closed.
davygravy@bitbaker64:~/Desktop$ sudo ssh root@***.***.**.***
[sudo] password for davygravy: 
root@***.***.**.***'s password: 
Linux AirDisk2 3.3.2-kirkwood-dg #1 Sat Apr 21 13:30:43 CDT 2012 armv5tel

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Apr 21 22:05:09 2012 from bitbaker64.local
root@AirDisk2:~# uname -a
Linux AirDisk2 3.3.2-kirkwood-dg #1 Sat Apr 21 13:30:43 CDT 2012 armv5tel GNU/Linux
root@AirDisk2:~#

=====================================================

• davy's Github Repo's rescue-dg

Edited 13 time(s). Last edit at 08/24/2012 10:00PM by davygravy.

Thanks Davygravy

I have a goflex net and am suffering from the bad eraseblocks problem you pointed out in another thread. Just wondering if this kernel has the fix and how you boot it? I can boot into 2.6.32-5-kirkwood, but not this. Uboot is jeff's uboot. Thanks,


Bo

Hi Bo, I understand what you are asking... and I figured out that I had a "bad link" in the top-of-thread-post...

it should be...

U-Boot with L2-Cache Disable@Boot Feature ... I mistakenly had that leading back to the same article, IIRC...

You will need a newer U-Boot to run (default-ish) 3.2 and higher kernels... that version of U-Boot for the goflex is running right now in my goflex...

=====================================================

• davy's Github Repo's rescue-dg

hi davy,

i'm trying to compile a new kernel, but i've some errors while update-initramfs.
can u please give me your .config?

major

Attached now above, top post of thread... I don't know why I didn't think of it before...

=====================================================

• davy's Github Repo's rescue-dg

Hi, Davy

flashed new uboot and am booting into this kernel, still have miles of bad eraseblock and too few good blocks in range. Do I really have to do a nand scrub? If so, could you let me know what your uboot variables are? Thanks!


Bo




17.919046] Bad eraseblock 1917 at 0x00000efa0000
[ 17.923807] Bad eraseblock 1918 at 0x00000efc0000
[ 17.928576] Bad eraseblock 1919 at 0x00000efe0000
[ 17.933338] Bad eraseblock 1920 at 0x00000f000000
[ 17.938107] Bad eraseblock 1921 at 0x00000f020000
[ 17.942868] Bad eraseblock 1922 at 0x00000f040000
[ 17.947639] Bad eraseblock 1923 at 0x00000f060000
[ 17.952400] Bad eraseblock 1924 at 0x00000f080000
[ 17.957170] Bad eraseblock 1925 at 0x00000f0a0000
[ 17.961930] Bad eraseblock 1926 at 0x00000f0c0000
[ 17.966691] Bad eraseblock 1927 at 0x00000f0e0000
[ 17.971461] Bad eraseblock 1928 at 0x00000f100000
[ 17.976223] Bad eraseblock 1929 at 0x00000f120000
[ 17.980993] Bad eraseblock 1930 at 0x00000f140000
[ 17.985753] Bad eraseblock 1931 at 0x00000f160000
[ 17.990524] Bad eraseblock 1932 at 0x00000f180000
[ 17.995284] Bad eraseblock 1933 at 0x00000f1a0000
[ 18.000054] Bad eraseblock 1934 at 0x00000f1c0000
[ 18.004815] Bad eraseblock 1935 at 0x00000f1e0000
[ 18.009586] Bad eraseblock 1936 at 0x00000f200000
[ 18.014346] Bad eraseblock 1937 at 0x00000f220000
[ 18.019116] Bad eraseblock 1938 at 0x00000f240000
[ 18.023876] Bad eraseblock 1939 at 0x00000f260000
[ 18.028648] Bad eraseblock 1940 at 0x00000f280000
[ 18.033408] Bad eraseblock 1941 at 0x00000f2a0000
[ 18.038178] Bad eraseblock 1942 at 0x00000f2c0000
[ 18.042939] Bad eraseblock 1943 at 0x00000f2e0000
[ 18.047709] Bad eraseblock 1944 at 0x00000f300000
[ 18.052470] Bad eraseblock 1945 at 0x00000f320000
[ 18.057240] Bad eraseblock 1946 at 0x00000f340000
[ 18.062001] Bad eraseblock 1947 at 0x00000f360000
[ 18.066771] Bad eraseblock 1948 at 0x00000f380000
[ 18.071532] Bad eraseblock 1949 at 0x00000f3a0000
[ 18.076292] Bad eraseblock 1950 at 0x00000f3c0000
[ 18.081064] Bad eraseblock 1951 at 0x00000f3e0000
[ 18.085824] Bad eraseblock 1952 at 0x00000f400000
[ 18.090594] Bad eraseblock 1953 at 0x00000f420000
[ 18.095354] Bad eraseblock 1954 at 0x00000f440000
[ 18.100125] Bad eraseblock 1955 at 0x00000f460000
[ 18.104886] Bad eraseblock 1956 at 0x00000f480000
[ 18.109656] Bad eraseblock 1957 at 0x00000f4a0000
[ 18.114417] Bad eraseblock 1958 at 0x00000f4c0000
[ 18.119187] Bad eraseblock 1959 at 0x00000f4e0000
[ 18.123947] Bad eraseblock 1960 at 0x00000f500000
[ 18.128718] Bad eraseblock 1961 at 0x00000f520000
[ 18.133478] Bad eraseblock 1962 at 0x00000f540000
[ 18.138250] Bad eraseblock 1963 at 0x00000f560000
[ 18.143010] Bad eraseblock 1964 at 0x00000f580000
[ 18.147780] Bad eraseblock 1965 at 0x00000f5a0000
[ 18.152541] Bad eraseblock 1966 at 0x00000f5c0000
[ 18.157311] Bad eraseblock 1967 at 0x00000f5e0000
[ 18.162071] Bad eraseblock 1968 at 0x00000f600000
[ 18.166841] Bad eraseblock 1969 at 0x00000f620000
[ 18.171603] Bad eraseblock 1970 at 0x00000f640000
[ 18.176363] Bad eraseblock 1971 at 0x00000f660000
[ 18.181134] Bad eraseblock 1972 at 0x00000f680000
[ 18.185894] Bad eraseblock 1973 at 0x00000f6a0000
[ 18.190665] Bad eraseblock 1974 at 0x00000f6c0000
[ 18.195425] Bad eraseblock 1975 at 0x00000f6e0000
[ 18.200196] Bad eraseblock 1976 at 0x00000f700000
[ 18.204957] Bad eraseblock 1977 at 0x00000f720000
[ 18.209728] Bad eraseblock 1978 at 0x00000f740000
[ 18.214487] Bad eraseblock 1979 at 0x00000f760000
[ 18.219259] Bad eraseblock 1980 at 0x00000f780000
[ 18.224018] Bad eraseblock 1981 at 0x00000f7a0000
[ 18.228789] Bad eraseblock 1982 at 0x00000f7c0000
[ 18.233549] Bad eraseblock 1983 at 0x00000f7e0000
[ 18.238320] Bad eraseblock 1984 at 0x00000f800000
[ 18.243080] Bad eraseblock 1985 at 0x00000f820000
[ 18.247850] Bad eraseblock 1986 at 0x00000f840000
[ 18.252611] Bad eraseblock 1987 at 0x00000f860000
[ 18.257382] Bad eraseblock 1988 at 0x00000f880000
[ 18.262143] Bad eraseblock 1989 at 0x00000f8a0000
[ 18.266913] Bad eraseblock 1990 at 0x00000f8c0000
[ 18.271674] Bad eraseblock 1991 at 0x00000f8e0000
[ 18.276434] Bad eraseblock 1992 at 0x00000f900000
[ 18.281205] Bad eraseblock 1993 at 0x00000f920000
[ 18.285965] Bad eraseblock 1994 at 0x00000f940000
[ 18.290736] Bad eraseblock 1995 at 0x00000f960000
[ 18.295496] Bad eraseblock 1996 at 0x00000f980000
[ 18.300266] Bad eraseblock 1997 at 0x00000f9a0000
[ 18.305028] Bad eraseblock 1998 at 0x00000f9c0000
[ 18.309798] Bad eraseblock 1999 at 0x00000f9e0000
[ 18.314558] Bad eraseblock 2000 at 0x00000fa00000
[ 18.319329] Bad eraseblock 2001 at 0x00000fa20000
[ 18.324089] Bad eraseblock 2002 at 0x00000fa40000
[ 18.328860] Bad eraseblock 2003 at 0x00000fa60000
[ 18.333620] Bad eraseblock 2004 at 0x00000fa80000
[ 18.338391] Bad eraseblock 2005 at 0x00000faa0000
[ 18.343151] Bad eraseblock 2006 at 0x00000fac0000
[ 18.347922] Bad eraseblock 2007 at 0x00000fae0000
[ 18.352682] Bad eraseblock 2008 at 0x00000fb00000
[ 18.357452] Bad eraseblock 2009 at 0x00000fb20000
[ 18.362213] Bad eraseblock 2010 at 0x00000fb40000
[ 18.366983] Bad eraseblock 2011 at 0x00000fb60000
[ 18.371744] Bad eraseblock 2012 at 0x00000fb80000
[ 18.376504] Bad eraseblock 2013 at 0x00000fba0000
[ 18.381276] Bad eraseblock 2014 at 0x00000fbc0000
[ 18.386036] Bad eraseblock 2015 at 0x00000fbe0000
[ 18.390807] Bad eraseblock 2016 at 0x00000fc00000
[ 18.395567] Bad eraseblock 2017 at 0x00000fc20000
[ 18.400338] Bad eraseblock 2018 at 0x00000fc40000
[ 18.405098] Bad eraseblock 2019 at 0x00000fc60000
[ 18.409869] Bad eraseblock 2020 at 0x00000fc80000
[ 18.414629] Bad eraseblock 2021 at 0x00000fca0000
[ 18.419400] Bad eraseblock 2022 at 0x00000fcc0000
[ 18.424160] Bad eraseblock 2023 at 0x00000fce0000
[ 18.428931] Bad eraseblock 2024 at 0x00000fd00000
[ 18.433691] Bad eraseblock 2025 at 0x00000fd20000
[ 18.438461] Bad eraseblock 2026 at 0x00000fd40000
[ 18.443222] Bad eraseblock 2027 at 0x00000fd60000
[ 18.447992] Bad eraseblock 2028 at 0x00000fd80000
[ 18.452752] Bad eraseblock 2029 at 0x00000fda0000
[ 18.457523] Bad eraseblock 2030 at 0x00000fdc0000
[ 18.462283] Bad eraseblock 2031 at 0x00000fde0000
[ 18.467053] Bad eraseblock 2032 at 0x00000fe00000
[ 18.471815] Bad eraseblock 2033 at 0x00000fe20000
[ 18.476576] Bad eraseblock 2034 at 0x00000fe40000
[ 18.481346] Bad eraseblock 2035 at 0x00000fe60000
[ 18.486107] Bad eraseblock 2036 at 0x00000fe80000
[ 18.490880] Bad eraseblock 2037 at 0x00000fea0000
[ 18.495638] Bad eraseblock 2038 at 0x00000fec0000
[ 18.500408] Bad eraseblock 2039 at 0x00000fee0000
[ 18.505169] Bad eraseblock 2040 at 0x00000ff00000
[ 18.509939] Bad eraseblock 2041 at 0x00000ff20000
[ 18.514700] Bad eraseblock 2042 at 0x00000ff40000
[ 18.519470] Bad eraseblock 2043 at 0x00000ff60000
[ 18.524230] Bad eraseblock 2044 at 0x00000ff80000
[ 18.529001] Bad eraseblock 2045 at 0x00000ffa0000
[ 18.533761] Bad eraseblock 2046 at 0x00000ffc0000
[ 18.538533] Bad eraseblock 2047 at 0x00000ffe0000
[ 18.543274] sched: RT throttling activated
[ 18.547438] 4 cmdlinepart partitions found on MTD device orion_nand
[ 18.553737] Creating 4 MTD partitions on "orion_nand":
[ 18.559091] 0x000000000000-0x000000100000 : "u-boot"
[ 18.564908] 0x000000100000-0x000000500000 : "uImage"
[ 18.570676] 0x000000500000-0x000002500000 : "rootfs"
[ 18.576450] 0x000002500000-0x000010000000 : "data"
[ 18.582924] mousedev: PS/2 mouse device common for all mice
[ 19.596771] rtc-mv rtc-mv: internal RTC not ticking
[ 19.601753] i2c /dev entries driver
[ 19.605379] cpuidle: using governor ladder
[ 19.609581] cpuidle: using governor menu
[ 19.613666] Registered led device: plug:red:misc
[ 19.613762] Registered led device: plug:green:health
[ 19.614648] TCP cubic registered
[ 19.617913] NET: Registered protocol family 17
[ 19.622386] Registering the dns_resolver key type
[ 19.627148] Gating clock of unused units
[ 19.627157] before: 0x00dfc3fd
[ 19.627165] after: 0x00c701d9
[ 19.627585] registered taskstats version 1
[ 19.632142] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 19.638497] Initializing network drop monitor service
[ 19.644159] Freeing init memory: 140K
[ 19.727116] udev[47]: starting version 164
[ 19.784106] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 19.846331] usbcore: registered new interface driver usbfs
[ 19.925387] mv643xx_eth smi: probed
[ 19.956475] mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
[ 19.972487] usbcore: registered new interface driver hub
[ 19.983418] usbcore: registered new device driver usb
[ 19.990209] mv643xx_eth_port mv643xx_eth_port.0: eth0: port 0 with MAC address 00:10:75:26:90:2e
[ 20.001870] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 20.014596] orion-ehci orion-ehci.0: Marvell Orion EHCI
[ 20.020429] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[ 20.056844] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[ 20.076793] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[ 20.082818] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 20.089659] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 20.096927] usb usb1: Product: Marvell Orion EHCI
[ 20.101651] usb usb1: Manufacturer: Linux 3.3.2-kirkwood-dg ehci_hcd
[ 20.108043] usb usb1: SerialNumber: orion-ehci.0
[ 20.113575] hub 1-0:1.0: USB hub found
[ 20.117372] hub 1-0:1.0: 1 port detected
[ 20.436786] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 20.588610] usb 1-1: New USB device found, idVendor=090c, idProduct=1000
[ 20.595348] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 20.602531] usb 1-1: Product: USB DISK
[ 20.606294] usb 1-1: Manufacturer: SMI Corporation
[ 20.611123] usb 1-1: SerialNumber: AA04012700007620
[ 20.637865] SCSI subsystem initialized
[ 20.644232] usbcore: registered new interface driver uas
[ 20.654117] Initializing USB Mass Storage driver...
[ 20.659337] scsi0 : usb-storage 1-1:1.0
[ 20.664520] usbcore: registered new interface driver usb-storage
[ 20.670575] USB Mass Storage support registered.
[ 21.657952] scsi 0:0:0:0: Direct-Access USB Flash Disk 1100 PQ: 0 ANSI: 0 CCS
[ 21.679666] sd 0:0:0:0: [sda] 1957888 512-byte logical blocks: (1.00 GB/956 MiB)
[ 21.688140] sd 0:0:0:0: [sda] Write Protect is off
[ 21.692958] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[ 21.693631] sd 0:0:0:0: [sda] No Caching mode page present
[ 21.699164] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 21.709382] sd 0:0:0:0: [sda] No Caching mode page present
[ 21.714895] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 21.722009] sda: sda1
[ 21.727258] sd 0:0:0:0: [sda] No Caching mode page present
[ 21.732772] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 21.738908] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 30.873125] udev[141]: starting version 164
[ 34.143422] mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 100 Mb/s, full duplex, flow control disabled
[ 34.382392] NET: Registered protocol family 10
[ 35.062747] sshd (736): /proc/736/oom_adj is deprecated, please use /proc/736/oom_score_adj instead.
[ 44.496764] eth0: no IPv6 routers present
root@debian:~# fw_print
-bash: fw_print: command not found
root@debian:~# fw_printenv
Too few good blocks within range
root@debian:~# uname -r
3.3.2-kirkwood-dg
root@debian:~#

Hmmm...let me look... Maybe that was the one thing I forgot to repatch. (though after looking at the code, it looks like I did indeed patch it)

There is nothing wrong w your uboot and whatever you do don't scrub it.

Give me a moment to look into it.

==================================

Bo, please post back output from the following:

In Linux :

dmesg | grep Machine

In U-Boot (from either netconsole or from serial):

print arcNumber

print machid

My guess is that your arcNumber is improperly set, which would cause it to be identified as another machine.

It may say Sheevaplug eSATA, or perhaps Dockstar...

It should say Seagate GoFlex Net.

The proper arcNumber value for GoFlex Net is 3089.

=====================================================

• davy's Github Repo's rescue-dg

Edited 1 time(s). Last edit at 04/25/2012 08:52PM by davygravy.

@davy

thnx for your .config.
the complier is running ;-)

cya
major-tom

YAY! Changing the arcNumber works! I always thought that goflex can live with 2097! Thanks Davy!

Hi davygravy,
unfortunately the link does not work anymore. Can you upload it somewhere else?
Thanks.

HellG

@HellG

Fixed... but I'll start providing a secondary (faster, too) link as well.

=====================================================

• davy's Github Repo's rescue-dg

funny that if I do not attach the serial lines now, goflex wouldn't boot at all but blinks green. Every time I boot I have to attach the serial lines, and it just works. Any ideas?

Bo Wrote:
-------------------------------------------------------
> funny that if I do not attach the serial lines
> now, goflex wouldn't boot at all but blinks green.
> Every time I boot I have to attach the serial
> lines, and it just works. Any ideas?

Well, mine both work fine. The kernel change should not cause any such behavioral change in booting w.r.t. serial or netconsole. I assume you are using the 3.3.2 v1.1 that I posted?

3 questions:
1. which uboot are you using and what are your uboot env contents? [ different u-boots occasionally have different (almost certainly very minor differences) requirements at for variables and booting operands... I haven't seen any difference on any of the U-Boots that I rolled in comparison to previous environments,but I don't know what your machines uboot env contents look like]


2. Can you post: (a) the output you see from serial booting , and (b) the output from netconsole [you can troubleshoot this all from netconsole]


3. What drives do you have attached? 2 SATA's and a USB maybe?

=====================================================

• davy's Github Repo's rescue-dg

Edited 1 time(s). Last edit at 05/03/2012 07:39PM by davygravy.

This will get bumped to 3.3.3 or something else suitable soon... a few users have mentioned that 3.3.4 breaks some network pptp related things, so I'm holding off for now.

And yes, 3.4.1 is out... I've not had a chance to try it yet.

=====================================================

• davy's Github Repo's rescue-dg

I'm running 3.4.1 with a hacked up set of ArchLinux ARM patches. So far the only fault I can find is it doesn't reboot on it's own. The kernel halts, but never kicks the GFN over. 3.4 did the same thing...

Hmmm... that may be something related to ALARM in particular. I built a Buildroot image last night w/ 3.4.1 and it was fine - I did check reboot and halt - both worked as expected. I haven't tried it in Debian, but if it works in Buildroot, then it should prolly be ok in Debian.

=====================================================

• davy's Github Repo's rescue-dg

@davygravy

How would I go about building your kernel from source? I'm guessing that I would basically follow the instructions here except that I would

• Use linux kernel 3.3.2 source here.
• Not apply the patches in the linked article but instead apply the patches from your Dropbox site, i.e. these patches.
• Use your kernel config file.

Have I got that right? Thanks.

Are you building it on your GoFlex, or cross-compiling? I use the CoreSourcery 2011q-somethingorother toolchain... Vlad mentions 2009q3, but IIRC I saw a compiler error w/ that, so I used a newer one.

As far as a config, I think that once your boot my kernel on your GoFlex, then go to /proc/config.gz . IIRC, I built it w/ the config accessible there - you can cp it to your data partition, and then gunzip it.

Make sure you back up your /boot dir just in case something is funky.

=====================================================

• davy's Github Repo's rescue-dg

Cross compile.

I'm new to cross compiling for embedded systems, so perhaps someone could tolerate to answer a few basic (probably really stupid) questions. :)

How does one decide which combinations of kernel, toolchain, gcc, and rootfs work together?

First, the kernel. I could just reproduce what davygravy did for kernel 3.3.2, but I'm thinking I'd like to build the very latest kernel and rootfs that would work on my GoFlex Home.) So I'm thinking kernel 3.4. I'm aware that I might have to figure out what patches from 3.3.2 would be needed in 3.4. That doesn't strike me as too hard (famous last words).

Next, toolchain. I'm thinking I'm going to use the emdebian toolchain, mostly because I've already installed it and used it successfully for another project Building Debian From Source Code for Mele, and also because folks have used it successfully in the past to build the kirkwood kernel for dockstar. The emdebian wiki says to use the squeeze (stable) toolchain, even if building on a testing or unstable system.

Next, gcc. The emdebian squeeze toolchain seems to offer a choice of gcc 4.3, 4.4, or 4.5. The system I'm building on is gcc 4.6.3 but I don't think that matters? I'm vaguely aware that the choice of gcc can impact the root filesystem I install? In the project I linked above, I built using gcc 4.4 and targeted a squeeze rootfs. But suppose I want wheezy (testing) or even sid (unstable)? How do I determine which gcc to use?

Finally, root filesystem. I'm running testing (with a little bit of unstable) on my AMD/i386 desktop. So that is what I'm most familiar with, so I'm thinking testing is my target rootfs. The richness of the apt repository matters here. How can one judge this?

Hi davygravy,
thanks for the kernel, it works great on my Dockstar@1.5GHz (overclocking info at http://gsg-elektronik.de/index.php?id=96). Could you please upload the kernel-headers somewhere? I am trying to compile some DVB applications and for that I need the header files. Thank you.

Best regards,
HellG

Davey,
Unfortunately when I try to install the kernel package, I keep getting an error: gzip read error: '<fd:0>: data error'
I tried to re-download it from both Pogoplug link and from your dropbox. Using the Vista desktop, tried TFTP and wget directly to the device. All attempts are with the same error. Please advise!
Thank you!

davygravy Wrote:
-------------------------------------------------------
> Hmmm... that may be something related to ALARM in
> particular. I built a Buildroot image last night
> w/ 3.4.1 and it was fine - I did check reboot and
> halt - both worked as expected. I haven't tried
> it in Debian, but if it works in Buildroot, then
> it should prolly be ok in Debian.


If you still have the 3.4.1 src you built from, after patching/etc, could I take a look? i'm up to 3.4.6 and still hanging on reboot, another user has confirmed my kernel hangs at reboot on his PogoPlug v4 as well. I'm hoping I can spot a difference between our two patch sets and fix mine.

In other news, I've got 3.5-rc7 up and running using Device Tree on the GFN, works slick.

I keep seeing this error message when I run an apt-get upgrade:

Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.3.2-kirkwood-dg
Kernel suffix dg does not match any of the expected flavors (kirkwood), therefore not writing it to flash.

Is there a way to fix this?

davygravy, can you please upload your Kernel Config and Package again?

davygravy, the kernel / config is in your public dropbox, isn't it?

The link to the kernel .deb download appears to no longer work.

FYI, I've got 3.5.2 working smoothly now, fixed my (stupid) reboot issue.

Don't suppose this is compatible with the pogoplug v3 is it ?

Nope, V3 is a completely different SoC/processor...

=====================================================

• davy's Github Repo's rescue-dg

Hi Davey,

Appreciate your work.

Attempting the upgrade, I have encountered some errors. This is the last part of the installation output:

Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.3.2-kirkwood-dg /boot/vmlinuz-3.3.2-kirkwood-dg
update-initramfs: Generating /boot/initrd.img-3.3.2-kirkwood-dg
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
W: mdadm: no arrays defined in configuration file.
flash-kernel: deferring update (trigger activated)
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.3.2-kirkwood-dg /boot/vmlinuz-3.3.2-kirkwood-dg
run-parts: executing /etc/kernel/postinst.d/zz-flash-kernel 3.3.2-kirkwood-dg /boot/vmlinuz-3.3.2-kirkwood-dg
flash-kernel: deferring update (trigger activated)
Processing triggers for flash-kernel ...
Kernel suffix dg does not match any of the expected flavors (kirkwood), therefore not writing it to flash.
benpogo@pogoplug:/$

Background info: Pogoplug originally with Squeeze, updated Uboot, upgraded to Wheezy 3.2.0 by apt-get dist-upgrade.

I have not continued with the next step as I am only a linux newbie with basic understanding, and do not want to brick my Pogoplug.

Any help would be appreciated.

Thanks,

Ben