Linux Kernel 6.7.5 Kirkwood package and Debian rootfs

The results of lsmod are attached. Since installing 3.11.1, I have experenced other problems with samba, and failed reboots.



Edited 1 time(s). Last edit at 11/04/2013 11:30AM by gee-man.

@bodhi:

good point you made with different uBoot versions on NSA320, both of my boxes still have the
stock firmware zyxel uBoot, maybe I should test davygravy's uBoot version,... he explicitly mentions
the ability to boot from BOTH sata ports with his uBoot version,.. which seems not to work with the stock uBoot,..
and also incorporated the [U-Boot] [PATCH] fix IDE_BUS(dev) macro,..

so perhaps there really is something different with SATA port number assignments and stock firmware uBoot,..
before building 3.10.18 longterm and incorporating your ide-disk patch I will switch to davygravy's uBoot version
and report back,..


best wishes pbg4



Edited 1 time(s). Last edit at 11/04/2013 02:42PM by pbg4.

I have a Pogoplug E02 with Kernel 3.8.11.

Can i update my Kernel with yours 3.11.1?
What is the changelog of this Kernel ?

I have buy it with this Kernel.
Can you give me a little How To ?

You can refer here

https://www.kernel.org/pub/linux/kernel/v3.x/

gee-man Wrote:
-------------------------------------------------------
> The results of lsmod are attached. Since
> installing 3.11.1, I have experenced other
> problems with samba, and failed reboots.

gee-man,

There are differences in the list of modules loaded. I suspect that is your problem. I would do this:

Make a clone of your USB 3.3.2 rootfs stick. Use the new stick, boot the box, upgrade the kernel to 3.11.1, and then do
apt-get update
apt-get upgrade

See if it helps.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I tried what you suggested, but I am still having the same problems. My system was already up to date, so apt-get update and apt-get upgrade didn't have any effect. I tried re-installing strongswan, but am still having the same problem.

Is this kernel missing AES support?? I can't seem to find the aes_generic and mv_cesa (for hardware accelerated encryption) modules that were included in 3.3.2..



Edited 4 time(s). Last edit at 11/07/2013 12:51PM by gee-man.

Maybe the modules are now built in? Already checked the kernel config?

ingmar_k Wrote:
-------------------------------------------------------
> Maybe the modules are now built in? Already
> checked the kernel config?

The modules were not built in. But I have not compared the 2 configs to see if any thing AES-related missing.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi, a few days ago that u-boot install in my nas320 and everything works perfect, but today tried to install a second hard drive and now not boot.

Hard drives are Seagate 2TB, with either boots, but if I put the two no.

This is what appears when you start:

U-Boot 2011.12 (May 03 2012 - 17:04:23)
ZyXEL NSA320 2-Bay Power Media Server

SoC:   Kirkwood 88F6281_A1
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
MV88E1318 PHY initialized on egiga0
Using egiga0 device
ping failed; host 192.168.11.149 is not alive
Hit any key to stop autoboot:  0 

Reset IDE: Bus 0: ............................................................** Timeout **
** Bad partition 1 **
** Bad partition 1 **
Wrong Image Format for bootm command
Error occured, error code = 108
ERROR: can't get kernel image!

Reset IDE: Bus 0: ............................................................** Timeout **
** Bad partition 1 **
** Bad partition 1 **
Wrong Image Format for bootm command
Error occured, error code = 108
ERROR: can't get kernel image!
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
Error occured, error code = 108
ERROR: can't get kernel image!
stopping USB..
## Error: "bootcmd_rescue" not defined
resetting ...

NSA320> printenv
arcNumber=3956
baudrate=115200
boot_sata1=mw 0x800000 0 1; setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 $mtdparts; ide reset; ext2load ide 0:1 0x800000 /boot/uImage; ext2load ide 0:1 0x01100000 /boot/uInitrd; bootm 0x00800000 0x01100000
boot_sata2=mw 0x800000 0 1; setenv bootargs console=ttyS0,115200 root=/dev/sdb1 rootdelay=10 $mtdparts; ide reset; ext2load ide 1:1 0x800000 /boot/uImage; ext2load ide 1:1 0x01100000 /boot/uInitrd; bootm 0x00800000 0x01100000
bootcmd=run boot_sata1; run boot_sata2; run bootcmd_usb; usb stop; run bootcmd_rescue; reset
bootcmd_usb=run usb_init; run usb_load_uimage; run set_bootargs_usb; run usb_boot;
bootdelay=3
console=ttyS0,115200
ethact=egiga0
ethaddr=b0:b2:dc:f0:fb:bd
if_netconsole=ping $serverip
ipaddr=192.168.11.150
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),512K(uboot_env),512K(key_store),512K(info),10M(etc),10M(kernel_1),48896K(rootfs1),10M(kernel_2),-(rootfs2)
netmask=255.255.255.0
partition=nand0,2
preboot=run if_netconsole start_netconsole
serverip=192.168.11.149
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
usb_boot=if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000;else bootm 0x800000;fi;
usb_device=0:1
usb_init=usb start
usb_load_uimage=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage
usb_root=LABEL=USBROOT
usb_rootdelay=10
usb_rootfstype=ext2

I tested with a 500Gb hard drive and one of the Seagate and works with two disks attached.

Any idea?

mbmsof Wrote:
-------------------------------------------------------
> Hi, a few days ago that u-boot install in my
> nas320 and everything works perfect, but today
> tried to install a second hard drive and now not
> boot.
>
> Hard drives are Seagate 2TB, with either boots,
> but if I put the two no.
>
> This is what appears when you start:
>
>

> U-Boot 2011.12 (May 03 2012 - 17:04:23)
> ZyXEL NSA320 2-Bay Power Media Server
> 
> SoC:   Kirkwood 88F6281_A1
> DRAM:  512 MiB
> WARNING: Caches not enabled
> NAND:  128 MiB
> In:    serial
> Out:   serial
> Err:   serial
> Net:   egiga0
> MV88E1318 PHY initialized on egiga0
> Using egiga0 device
> ping failed; host 192.168.11.149 is not alive
> Hit any key to stop autoboot:  0 
> 
> Reset IDE: Bus 0:
> ..................................................
> ..........** Timeout **
> ** Bad partition 1 **
> ** Bad partition 1 **
> Wrong Image Format for bootm command
> Error occured, error code = 108
> ERROR: can't get kernel image!
> 
> Reset IDE: Bus 0:
> ..................................................
> ..........** Timeout **
> ** Bad partition 1 **
> ** Bad partition 1 **
> Wrong Image Format for bootm command
> Error occured, error code = 108
> ERROR: can't get kernel image!
> (Re)start USB...
> USB:   Register 10011 NbrPorts 1
> USB EHCI 1.00
> scanning bus for devices... 2 USB Device(s) found
>        scanning bus for storage devices... 0
> Storage Device(s) found
> ** Block device usb 0 not supported
> ** Block device usb 0 not supported
> Wrong Image Format for bootm command
> Error occured, error code = 108
> ERROR: can't get kernel image!
> stopping USB..
> ## Error: "bootcmd_rescue" not defined
> resetting ...
>

>
>
>
>

> NSA320> printenv
> arcNumber=3956
> baudrate=115200
> boot_sata1=mw 0x800000 0 1; setenv bootargs
> console=ttyS0,115200 root=/dev/sda1 rootdelay=10
> $mtdparts; ide reset; ext2load ide 0:1 0x800000
> /boot/uImage; ext2load ide 0:1 0x01100000
> /boot/uInitrd; bootm 0x00800000 0x01100000
> boot_sata2=mw 0x800000 0 1; setenv bootargs
> console=ttyS0,115200 root=/dev/sdb1 rootdelay=10
> $mtdparts; ide reset; ext2load ide 1:1 0x800000
> /boot/uImage; ext2load ide 1:1 0x01100000
> /boot/uInitrd; bootm 0x00800000 0x01100000
> bootcmd=run boot_sata1; run boot_sata2; run
> bootcmd_usb; usb stop; run bootcmd_rescue; reset
> bootcmd_usb=run usb_init; run usb_load_uimage; run
> set_bootargs_usb; run usb_boot;
> bootdelay=3
> console=ttyS0,115200
> ethact=egiga0
> ethaddr=b0:b2:dc:f0:fb:bd
> if_netconsole=ping $serverip
> ipaddr=192.168.11.150
> mainlineLinux=yes
> mtdids=nand0=orion_nand
> mtdparts=mtdparts=orion_nand:1M(u-boot),512K(uboot
> _env),512K(key_store),512K(info),10M(etc),10M(kern
> el_1),48896K(rootfs1),10M(kernel_2),-(rootfs2)
> netmask=255.255.255.0
> partition=nand0,2
> preboot=run if_netconsole start_netconsole
> serverip=192.168.11.149
> set_bootargs_usb=setenv bootargs console=$console
> root=$usb_root rootdelay=$usb_rootdelay
> rootfstype=$usb_rootfstype $mtdparts
> start_netconsole=setenv ncip $serverip; setenv
> bootdelay 10; setenv stdin nc; setenv stdout nc;
> setenv stderr nc; version;
> stderr=serial
> stdin=serial
> stdout=serial
> usb_boot=if ext2load usb $usb_device 0x1100000
> /boot/uInitrd; then bootm 0x800000 0x1100000;else
> bootm 0x800000;fi;
> usb_device=0:1
> usb_init=usb start
> usb_load_uimage=mw 0x800000 0 1; ext2load usb
> $usb_device 0x800000 /boot/uImage
> usb_root=LABEL=USBROOT
> usb_rootdelay=10
> usb_rootfstype=ext2
> 
>

>
> I tested with a 500Gb hard drive and one of the
> Seagate and works with two disks attached.
>
> Any idea?

Which disk has the system rootfs? Or are they identical? Your uBoot envs probably needed to be adjusted a little to enable booting with the correct disk.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:

> Which disk has the system rootfs? Or are they
> identical? Your uBoot envs probably needed to be
> adjusted a little to enable booting with the
> correct disk.

Thank you for your help.

I tested the following configurations:

- Seagate HDD Kernel 3.11.1 + Seagate HDD partition ext4 = not work.

- Seagate HDD Kernel 3.11.1 + Seagate HDD Kernel 3.3.2 = not work.

- Seagate HDD Kernel 3.11.1 + Samsung HDD partition Zyxel = works.

- Seagete HDD Kernel 3.11.1 = works.

- Seagate HDD Kernel 3.3.2 = works.

The HDD are identical, Seagate Barracuda 2TB ST2000DM001.

I have also tried placing the second HDD once set up the NSA320, recognizes it perfectly and if I do a reboot starts without problems, but if I poweroff does not boot.

Bodhi,

To try building this kernel myself, which kernel source should I download? From kernel.org with no patches, or should I get the debian source that has all the debian patches applied (package linux-source-3.11)?

After I do that, I will apply your kernel patch, and use the kernel config in my /boot directory for this kernel.... I already downloaded and installed shyd's toolchain (http://dev.shyd.de/2011/03/dockstar-crosscompile-newer-kernel-set-toolchain/), will this work to compile this kernel?


Thanks!

gee-man,

The source should be from kernel.org with no patch. I'm not familiar with shyd's tool chain so can't comment on that. But it should compile if it is for the Dockstar. The problem you might run into is the difference in config options.

I'm building kernel 3.12, and will take a look in the config to see if any AES-related option is missing.
(UPDATE: just checked, nothing is missing, all options for crypto are selected).

Upstream Kernel 3.12 has removed all the Kirkwood patches for mach-types :)) They expect that everybody has switched to FDT scheme. So it is a little time consuming to get back all those files from 3.11.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/08/2013 03:44PM by bodhi.

@mbmsof,

Please repost this problem in a new thread (It should be in uBoot section).

My question was: is only one of the 2 disks have Linux system on it? or both?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/08/2013 03:34PM by bodhi.

Thanks bodhi.

I just try another 2TB Samsung HDD from another computer and it works.

Now I have the 4 TB in the NSA, working.

There must be an incompatibility to put the two identical Seagate.

Kernel 3.12.0-kirkwood-tld-1 package was uploaded. Please see 1st post for download link.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hello,

i have some problem with installation:


dpkg -i linux-image-3.12.0-kirkwood-tld-1_1.0_armel.deb
Selecting previously unselected package linux-image-3.12.0-kirkwood-tld-1.
(Reading database ... 53050 files and directories currently installed.)
Unpacking linux-image-3.12.0-kirkwood-tld-1 (from linux-image-3.12.0-kirkwood-tld-1_1.0_armel.deb) ...
Examining /etc/kernel/preinst.d/
Done.
Setting up linux-image-3.12.0-kirkwood-tld-1 (1.0) ...

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


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

Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.12.0-kirkwood-tld-1 /boot/vmlinuz-3.12.0-kirkwood-tld-1

daveeeee,

Output below is normal. Since the kernel source is not included in the kernel deb package. You can safely ignore it.

> 
> dpkg -i
> linux-image-3.12.0-kirkwood-tld-1_1.0_armel.deb
> Selecting previously unselected package
> linux-image-3.12.0-kirkwood-tld-1.
> (Reading database ... 53050 files and directories
> currently installed.)
> Unpacking linux-image-3.12.0-kirkwood-tld-1 (from
> linux-image-3.12.0-kirkwood-tld-1_1.0_armel.deb)
> ...
> Examining /etc/kernel/preinst.d/
> Done.
> Setting up linux-image-3.12.0-kirkwood-tld-1 (1.0)
> ...
> 
>  Hmm. There is a symbolic link
> /lib/modules/3.12.0-kirkwood-tld-1/build
>  However, I can not read it: No such file or
> directory
>  Therefore, I am deleting
> /lib/modules/3.12.0-kirkwood-tld-1/build
> 
> 
>  Hmm. The package shipped with a symbolic link
> /lib/modules/3.12.0-kirkwood-tld-1/source
>  However, I can not read the target: No such file
> or directory
>  Therefore, I am deleting
> /lib/modules/3.12.0-kirkwood-tld-1/source
> 
> Running depmod.
> Examining /etc/kernel/postinst.d.

Below, I'm not sure why, perhaps something about your system. Is this the entire log? or there are more after this?

> run-parts: executing
> /etc/kernel/postinst.d/apt-auto-removal
> 3.12.0-kirkwood-tld-1
> /boot/vmlinuz-3.12.0-kirkwood-tld-1

What is in your output of:

cat /etc/apt/apt.conf.d/01autoremove

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/09/2013 04:28AM by bodhi.

This is the entire log of dpkg.
After that, vmlinuz-3.12.0-kirkwood-tld-1 is in the /boot directory, but initrd.img-3.12.0-kirkwood-tld-1 is not.

Quote
bodhi
What is in your output of:
cat /etc/apt/apt.conf.d/01autoremove

cat /etc/apt/apt.conf.d/01autoremove
APT
{
  NeverAutoRemove
  {
        "^firmware-linux.*";
        "^linux-firmware$";
        "^kfreebsd-image.*";
        "^gnumach$";
        "^gnumach-image.*";
  };

  Never-MarkAuto-Sections
  {
        "metapackages";
        "restricted/metapackages";
        "universe/metapackages";
        "multiverse/metapackages";
        "oldlibs";
        "restricted/oldlibs";
        "universe/oldlibs";
        "multiverse/oldlibs";
  };
};

Thank you for your help.

daveeeee,

This is my autoremove settings. I think you should have "^linux-image.*", and other options too, in your NeverAutoRemove list. Modify your list and reboot to verify that it takes effect after the next boot. Remember to check your kernel files in /boot to make sure they are consistent before you reboot.

See it will let dpkg finish.

cat /etc/apt/apt.conf.d/01autoremove 
APT
{
  NeverAutoRemove
  {
	"^firmware-linux.*";
	"^linux-firmware$";
	"^linux-image.*";
	"^kfreebsd-image.*";
	"^linux-restricted-modules.*";
	"^linux-ubuntu-modules-.*";
	"^gnumach$";
	"^gnumach-image.*";
  };

  Never-MarkAuto-Sections
  {
	"metapackages";
	"restricted/metapackages";
	"universe/metapackages";
	"multiverse/metapackages";
	"oldlibs";
	"restricted/oldlibs";
	"universe/oldlibs";
	"multiverse/oldlibs";
  };
};

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 11/09/2013 02:18PM by bodhi.

Modified list,

here is the output:

 dpkg -i linux-image-3.12.0-kirkwood-tld-1_1.0_armel.deb
(Reading database ... 55294 files and directories currently installed.)
Preparing to replace linux-image-3.12.0-kirkwood-tld-1 1.0 (using linux-image-3.12.0-kirkwood-tld-1_1.0_armel.deb) ...
Examining /etc/kernel/preinst.d/
Done.
Unpacking replacement linux-image-3.12.0-kirkwood-tld-1 ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.12.0-kirkwood-tld-1 /boot/vmlinuz-3.12.0-kirkwood-tld-1
run-parts: executing /etc/kernel/postrm.d/zz-flash-kernel 3.12.0-kirkwood-tld-1 /boot/vmlinuz-3.12.0-kirkwood-tld-1
Setting up linux-image-3.12.0-kirkwood-tld-1 (1.0) ...

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


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

Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.12.0-kirkwood-tld-1 /boot/vmlinuz-3.12.0-kirkwood-tld-1
┌─[root@nas]─[/boot]
└──> ls /boot
config-3.12.0-kirkwood-tld-1                               linux-3.12.0-tld-1-kirkwood.patch                  uImage
config-3.3.2-kirkwood-dg                                   linux-headers-3.12.0-kirkwood-tld-1_1.0_armel.deb  uInitrd
initrd.img-3.3.2-kirkwood-dg                               linux-image-3.12.0-kirkwood-tld-1_1.0_armel.deb    vmlinux-3.3.2-kirkwood-dg
initrd.img-3.3.2-kirkwood-dg.dpkg-bak                      System.map-3.12.0-kirkwood-tld-1                   vmlinuz-3.12.0-kirkwood-tld-1
linux-3.12.0-kirkwood-tld-1-bodhi.tar.bz2.tar.bz2.tar.bz2  System.map-3.3.2-kirkwood-dg                       vmlinuz-3.3.2-kirkwood-dg

initrd.img is still not here.

Thanks,

daveeeee

Hi,

I noticed a strange problem.
I first compiled my own 3.11.6 kernel uImage and saw the problem and now tried your kernel 3.12 with the same results.

I have tried to setup different swap partitions/files whatever, which get recongnized and seen correctly, but it seems that these never get used. And that, although free memory gets VERY low while copying huge files. Even to the point where the OOM starts kicking in. VERY STRANGE!

Anyone of you checked their SWAP usage?
Does this work for you?

Greets from bavaria

Ingmar

Edit: Nevermind! Problem solved, although I don't know yet, how. I went back to using my own kernel and again added the entry for a swap partition on a USB stick into my fstab. And now, using stress as a test tool, I can see the system using swap. Very strange indeed. Will have to investigate why it didn't work before.

Edit 2: OK, had zcache and zswap enabled via the kernel commandline. One or both of those two probably made the "normal" swap not work anymore. Don't know if that is by design, or buggy behaviour. I would guess the latter.
Edit 3: Hmm, those were not even included in bodhi's kernel. So I guess it should've been something else. Oh well, maybe I will figure it out.



Edited 4 time(s). Last edit at 11/10/2013 10:09AM by ingmar_k.

bodhi Wrote:
-------------------------------------------------------
> Upstream Kernel 3.12 has removed all the Kirkwood
> patches for mach-types :)) They expect that
> everybody has switched to FDT scheme. So it is a
> little time consuming to get back all those files
> from 3.11.

With those patches removed, does this mean the 3.12 kernel will not work as well as earlier versions? I tried compiling the kernel myself with your 3.12 configuration file and some additions. The goflex seems to have booted up, the solid green light came on, but then, I couldn't communicate (ping or ssh) at all with the device...

I'm now trying to build this kernel with the config file from 3.3.2 with some minor additions to the .config on the goflex itself. It will be another 5 hours before it finishes...

As bodhi already provides a 3.12 kernel, you can be pretty sure that the problem is taken care of.
It probably was "just" (understatement ;-) ) a question of changing the original 3.11 patches a bit.

ingmar_k,

I've been running kernel 3.12 on the GoFlex Net since

Linux version 3.12.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 PREEMPT Fri Nov 8 15:57:44 PST 2013
 13:27:42 up 1 day, 11:25,  1 user,  load average: 0.15, 0.05, 0.06

free -m
             total       used       free     shared    buffers     cached
Mem:           120        109         10          0         26         37
-/+ buffers/cache:         46         73
Swap:         7999          7       7992

I've compiled uBoot several times since then. So that probably explains the 7M swap (on SATA rootfs).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 11/10/2013 04:06PM by bodhi.

gee-man,

> With those patches removed, does this mean the
> 3.12 kernel will not work as well as earlier
> versions?

It works the same way. Just a matter of copy files back to their old place, and modify the configuration files to point the the old location. To compile the kernel you will need to apply the patches. Without them, the mainline code won't work for Kirkwook boxes with the current uBoot any more.

One observation: since you're upgrading from 3.3.2 to 3.11 or 3.12, I think a few of package configuration files might have changed. You might end up with the same errors even with your onw build.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

daveeeee,

How did you create your rootfs? from davygravy's NSA320 image? or from Jeff's script and then later upgraded with davygravy's kernel 3.3.2?

Do you have enough space in /boot ?

Another thought, what's your output of cat /etc/apt/apt.conf ?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/10/2013 04:30PM by bodhi.

Bodhi:
6 hours later... The kernel has finished building :)

My latest attempt to compile 3.12 with your patch and the 3.3.2 config has failed again. Netconsole isn't very helpful:

D:\netcat>nc -l -u -p 6666
[ 35.436934] netconsole: network logging started
[ 45.700525] usbcore: registered new interface driver usbfs
[ 45.707033] usbcore: registered new interface driver hub
[ 45.712537] usbcore: registered new device driver usb
[ 45.719800] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 45.736071] uhci_hcd: USB Universal Host Controller Interface driver
[ 45.751305] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 45.769964] hidraw: raw HID events driver (C) Jiri Kosina
[ 45.779636] usbcore: registered new interface driver usbhid
[ 45.785274] usbhid: USB HID core driver
[ 35.347263] console [netcon0] enabled
[ 35.350954] netconsole: network logging started
[ 45.615765] usbcore: registered new interface driver usbfs
[ 45.622235] usbcore: registered new interface driver hub
[ 45.627771] usbcore: registered new device driver usb
[ 45.635016] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 45.651232] uhci_hcd: USB Universal Host Controller Interface driver
[ 45.666547] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 45.685185] hidraw: raw HID events driver (C) Jiri Kosina
[ 45.694863] usbcore: registered new interface driver usbhid
[ 45.700531] usbhid: USB HID core driver

That's all that happens, and the goflex shows a solid green light, but I can't ping the device or anything...I am going to try downloading and compiling 3.11 with your kernel source patch, and this config file and see if that works..

Can someone take a look at this kernel that I compiled for my goflex net and see if they can determine why it won't boot? You can find it here: http://wikisend.com/download/194860/linux-image-3.12.0-flex_3_armel.deb



Edited 2 time(s). Last edit at 11/10/2013 07:24PM by gee-man.

gee-man,

Since you're going to roll your own kernel, I would recommend to have serial console to watch the kernel booting progress. Netconsole does not show you the type of details needed to troubleshoot kernel booting.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Debian rootfs 3.12.0 was uploaded. Please see 1st for download link.