• Home
  • Help
  • Search
  • Login
  • Register
Pages: 1 [2]
Author Topic: 3.2 new kernel available  (Read 6608 times)
spinifex
Full Member
***

Karma: 8
Posts: 167



View Profile WWW
« Reply #15 on: January 13, 2012, 02:16:47 PM »

Quote
i wonder if spinifex could do it
spinifex does not have cross compilers anymore. I use a Sheevaplug running Debian Wheezy to build the kernels and SDLAN drivers. I have had no problems building any of the later 3.1 kernels using the .config that biker has placed on xilka.com. (However, I think I need to ressurect cross compiling for Marvell Dove. )

On the kernel front, I cannot get 3.2 or 3.2.1 to twitch on the Dreamplug. No boot. Further, on 3.2 kernels I cannot compile the SDLAN drivers on 3.2. The newer SD8787 drivers source code is unavailable to compile the new sd8xxx.ko/mlan.ko (and it is probably 3.2 incompatible anyway). For Dreamplugs, Linux kernels effectively stop at 3.1.
Logged

weltall
Newbie
*

Karma: 1
Posts: 11


View Profile
« Reply #16 on: January 16, 2012, 09:16:50 AM »

after more than 10 builds it seems the bisect didn't bring much good results. I ended up with this. I never had such a thing before...
The merge base efb8d21b2c6db3497655cc6a033ae8a9883e4063 is bad.
This means the bug has been fixed between efb8d21b2c6db3497655cc6a033ae8a9883e4063 and [8686a0e200419322654a75155e2e6f80346a1297 b96d71571f7745216ef63f13770b5a10b94ddd34 c3b92c8787367a8bb53d57d9789b558f1295cc96 efb8d21b2c6db3497655cc6a033ae8a9883e4063].
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #17 on: January 16, 2012, 09:58:14 AM »

after more than 10 builds it seems the bisect didn't bring much good results. I ended up with this. I never had such a thing before...
The merge base efb8d21b2c6db3497655cc6a033ae8a9883e4063 is bad.
This means the bug has been fixed between efb8d21b2c6db3497655cc6a033ae8a9883e4063 and [8686a0e200419322654a75155e2e6f80346a1297 b96d71571f7745216ef63f13770b5a10b94ddd34 c3b92c8787367a8bb53d57d9789b558f1295cc96 efb8d21b2c6db3497655cc6a033ae8a9883e4063].


Looks like they messed up a commit.  http://comments.gmane.org/gmane.linux.serial/6231

I wonder how the last commit prior to efb8d2... would work.  I see they were messing with serial code with that commit and some of the following commits.  Maybe they messed up something up in serial.

Also, maybe for testing you could just disable serial support for testing and see if you can get it to boot, that'd at least narrow the search down.

Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #18 on: January 20, 2012, 11:03:55 AM »

Can I get someone the boot problem with 3.2.x to try out my latest 3.2.1 please?

I rebuilt it with a different (older) toolchain and turned on DEBUG_LL.

I was having a no-boot problem on my new cubox kernel until I reverted back to an older compiler.  So, if we're lucky the same fix will take care of the Dreamplug no-boot.
Logged

jgoewert
Newbie
*

Karma: 0
Posts: 1


View Profile
« Reply #19 on: January 23, 2012, 07:54:58 AM »

My Sheevaplug is still stopping after loading the 3.2.1 kernel. I am about to try the 3.1.9.

Code:
U-Boot 2011.12 (Jan 08 2012 - 21:53:47)
Marvell-Sheevaplug - eSATA - SD/MMC

SoC:   Kirkwood 88F6281_A1
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  512 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0
Marvell>> usbstart
Unknown command 'usbstart' - try 'help'
Marvell>> usb start
(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... 1 Storage Device(s) found
Marvell>> fatload usb 0:1 0x00800000 /sheeva-3.2.1-uImage
reading /sheeva-3.2.1-uImage

2918568 bytes read
Marvell>> fatload usb 0:1 0x01100000 /uInitrd
reading /uInitrd

4305500 bytes read
Marvell>> setenv bootargs console=ttyS0,115200n8 base-installer/initramfs-tools/driver-policy=most
Marvell>> bootm 0x00800000 0x01100000
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.2.1
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2918504 Bytes = 2.8 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   debian-installer ramdisk
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4305436 Bytes = 4.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Marvell>> ls
mtdids not defined, no default present
Marvell>> usb start
(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... 1 Storage Device(s) found
Marvell>> printenv
arcNumber=2097
baudrate=115200
bootargs=console=ttyS0,115200 rootdelay=10
bootargs_console=console=ttyS0,115200
bootargs_root= root_delay=10
bootcmd=setenv bootargs $(bootargs_console) rootdelay=10; run bootcmd_mmc; bootm 0x00800000 0x01100000
bootcmd_mmc=mmc init; ext2load mmc 0:1 0x00800000 /uImage; ext2load mmc 0:1 0x01100000 /uInitrd
bootdelay=3
ethact=egiga0
ethaddr=F0:AD:4E:00:D9:35
filesize=2C88A8
mainlineLinux=yes
stderr=serial
stdin=serial
stdout=serial
x_bootargs=console=ttyS0,115200 mtdparts=orion_nand:512k(uboot),4m@1m(kernel),507m@5m(rootfs) rw
x_bootargs_root=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
x_bootcmd_kernel=nand read 0x6400000 0x100000 0x400000
x_bootcmd_sata=ide reset;
x_bootcmd_usb=usb start;
Logged

Pages: 1 [2]
Print
Jump to: