Re: Newer uBoot as workaround to 3.2 kernel problem? March 19, 2012 07:57PM |
Registered: 12 years ago Posts: 501 |
Marvell>> tftpboot 0x800000 uboot.mtd0.kwb-stable2011.12-goflexnetv1 tftpboot 0x800000 uboot.mtd0.kwb-stable2011.12-goflexnetv1 Using egiga0 device TFTP from server 192.168.11.149; our IP address is 192.168.11.150 Filename 'uboot.mtd0.kwb-stable2011.12-goflexnetv1'. Load address: 0x800000 Loading: #################################### done Bytes transferred = 524288 (80000 hex) Marvell>> nand erase 0x0 0x80000 nand erase 0x0 0x80000 NAND erase: device 0 offset 0x0, size 0x80000 Erasing at 0x60000 -- 100% complete. OK Marvell>> nand write.e 0x800000 0x0 0x80000 nand write.e 0x800000 0x0 0x80000 NAND write: device 0 offset 0x0, size 0x80000 524288 bytes written: OK Marvell>> reset reset resetting ... U-Boot 2011.12 (Mar 19 2012 - 19:46:24) Seagate GoFlexNet arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1 GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709 Hit any key to stop autoboot: 4This is pretty much a reworking of everything so far... based loosely on the openrd setup, and the dns-325, as well as looking at the LaCie devices.
Re: Newer uBoot as workaround to 3.2 kernel problem? March 19, 2012 10:59PM |
Registered: 12 years ago Posts: 12 |
Robert Mugabe
Re: Newer uBoot as workaround to 3.2 kernel problem? March 20, 2012 05:30AM |
Re: Newer uBoot as workaround to 3.2 kernel problem? March 20, 2012 12:09PM |
Registered: 12 years ago Posts: 12 |
Re: Newer uBoot as workaround to 3.2 kernel problem? March 20, 2012 08:04PM |
Registered: 12 years ago Posts: 501 |
GoFlexNet> reset reset resetting ... U-Boot 2011.12 (Mar 19 2012 - 22:10:07) Seagate GoFlexNet arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1 GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709 Hit any key to stop autoboot: 10 9 0 GoFlexNet> GoFlexNet> GoFlexNet> ide reset ide reset Reset IDE: Bus 0: OK Bus 1: OK Device 0: Model: TOSHIBA MK1655GSX Firm: FG010D Ser#: X9AHTNGQT Type: Hard Disk Supports 48-bit addressing Capacity: 152627.8 MB = 149.0 GB (312581808 x 512) Device 1: not available GoFlexNet>
Re: Newer uBoot as workaround to 3.2 kernel problem? March 21, 2012 08:39PM |
Registered: 12 years ago Posts: 501 |
dpffan
Re: Newer uBoot as workaround to 3.2 kernel problem? March 22, 2012 12:30AM |
Re: Newer uBoot as workaround to 3.2 kernel problem? March 22, 2012 07:03AM |
Registered: 12 years ago Posts: 501 |
#define CONFIG_SYS_ATA_IDE0_OFFSET MV_SATA_PORT0_OFFSETfrom the SATA driver section below, it does then use Device 1 (left port).
/* * SATA Driver configuration */ #undef CONFIG_SYS_IDE_MAXBUS #define CONFIG_SYS_IDE_MAXBUS 1 /* hide phantom-nonexistent bus */ #ifdef CONFIG_MVSATA_IDE #define CONFIG_SYS_ATA_IDE0_OFFSET MV_SATA_PORT0_OFFSET #define CONFIG_SYS_ATA_IDE1_OFFSET MV_SATA_PORT1_OFFSET #endif /*CONFIG_MVSATA_IDE*/Yields
GoFlexNet> ide reset ide reset Reset IDE: Bus 0: OK Device 0: Model: TOSHIBA MK1655GSX Firm: FG010D Ser#: X9AHTNGQT Type: Hard Disk Supports 48-bit addressing Capacity: 152627.8 MB = 149.0 GB (312581808 x 512) Device 1: not available
Reset IDE: Bus 0: OKinstead of
Reset IDE: Bus 0: .OK Bus 1: OKwhich at least makes sense since it only has one bus available.
Re: Newer uBoot as workaround to 3.2 kernel problem? March 26, 2012 05:30PM |
Registered: 12 years ago Posts: 501 |
Re: Newer uBoot as workaround to 3.2 kernel problem? March 26, 2012 10:19PM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: Newer uBoot as workaround to 3.2 kernel problem? March 26, 2012 11:57PM |
Registered: 12 years ago Posts: 501 |
Re: Newer uBoot as workaround to 3.2 kernel problem? March 27, 2012 03:27AM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: Newer uBoot as workaround to 3.2 kernel problem? March 27, 2012 01:54PM |
Registered: 13 years ago Posts: 264 |
Re: Newer uBoot as workaround to 3.2 kernel problem? March 27, 2012 03:21PM |
Registered: 12 years ago Posts: 501 |
Re: Newer uBoot as workaround to 3.2 kernel problem? March 31, 2012 01:57PM |
Registered: 14 years ago Posts: 78 |
Marvell>> tftpboot 0x800000 uboot.mtd0.kwb-pogo_e02-DGL2CDisabled.tar.gz tftpboot 0x800000 uboot.mtd0.kwb-pogo_e02-DGL2CDisabled.tar.gz Using egiga0 device TFTP from server 192.168.1.75; our IP address is 192.168.1.161 Filename 'uboot.mtd0.kwb-pogo_e02-DGL2CDisabled.tar.gz'. Load address: 0x800000 Loading: ####################################### done Bytes transferred = 197182 (3023e hex) Marvell>>Your example use the dockstar file and I'm using the E02 file. Should the bytes transferred for the E02 also be hex 80000 or is what I'm getting (hex 3023e) correct?
Re: Newer uBoot as workaround to 3.2 kernel problem? March 31, 2012 02:24PM |
Registered: 12 years ago Posts: 501 |
Re: Newer uBoot as workaround to 3.2 kernel problem? March 31, 2012 03:31PM |
Registered: 14 years ago Posts: 78 |
tftpboot 0x800000 uboot.mtd0.kwb-pogo_e02-DGL2CDisabled Using egiga0 device TFTP from server 192.168.1.75; our IP address is 192.168.1.161 Filename 'uboot.mtd0.kwb-pogo_e02-DGL2CDisabled'. Load address: 0x800000 Loading: ################################################################# ###################################### done Bytes transferred = 524288 (80000 hex)
U-Boot 2011.12 (Feb 20 2012 - 21:21:59) Pogoplug E02 arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1 GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709 Hit any key to stop autoboot: 5 u-boot>>
Re: Newer uBoot as workaround to 3.2 kernel problem? March 31, 2012 06:24PM |
Registered: 12 years ago Posts: 501 |
Re: Newer uBoot as workaround to 3.2 kernel problem? April 04, 2012 11:25AM |
Registered: 12 years ago Posts: 2 |
Re: Newer uBoot as workaround to 3.2 kernel problem? April 04, 2012 01:05PM |
Registered: 13 years ago Posts: 78 |
Re: Newer uBoot as workaround to 3.2 kernel problem? April 04, 2012 02:43PM |
Registered: 12 years ago Posts: 2 |
Re: Newer uBoot as workaround to 3.2 kernel problem? April 10, 2012 01:25PM |
Registered: 12 years ago Posts: 27 |
U-Boot 2011.12 (Feb 20 2012 - 21:21:59) Pogoplug E02 arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1 GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709 Hit any key to stop autoboot: 0 (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 4 USB Device(s) found scanning bus for storage devices... 1 Storage Device(s) found Loading file "/rescueme" from usb device 0:1 (usbda1) ** File not found /rescueme reading /rescueme.txt ** Unable to read "/rescueme.txt" from usb 0:1 ** Creating 1 MTD partitions on "nand0": 0x000002500000-0x000008000000 : "mtd=3" UBI: attaching mtd1 to ubi0 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size: 129024 bytes UBI: smallest flash I/O unit: 2048 UBI: sub-page size: 512 UBI: VID header offset: 512 (aligned 512) UBI: data offset: 2048 UBI: attached mtd1 to ubi0 UBI: MTD device name: "mtd=3" UBI: MTD device size: 91 MiB UBI: number of good PEBs: 722 UBI: number of bad PEBs: 6 UBI: max. allowed volumes: 128 UBI: wear-leveling threshold: 4096 UBI: number of internal volumes: 1 UBI: number of user volumes: 0 UBI: available PEBs: 711 UBI: total number of reserved PEBs: 11 UBI: number of PEBs reserved for bad PEB handling: 7 UBI: max/mean erase counter: 1/1 UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19 Error reading superblock on volume 'ubi:rootfs'! Loading file "/boot/uImage" from usb device 0:1 (usbda1) 1 bytes read Found bootable drive on usb 0:1 Loading file "/boot/uImage" from usb device 0:1 (usbda1) 1574408 bytes read Loading file "/boot/uInitrd" from usb device 0:1 (usbda1) 6760358 bytes read ## Booting kernel from Legacy Image at 00800000 ... Image Name: kernel 3.2.0-2-kirkwood Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1574344 Bytes = 1.5 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 01100000 ... Image Name: ramdisk 3.2.0-2-kirkwood Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 6760294 Bytes = 6.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ...
Re: Newer uBoot as workaround to 3.2 kernel problem? April 10, 2012 07:28PM |
Registered: 12 years ago Posts: 501 |
Re: Newer uBoot as workaround to 3.2 kernel problem? April 10, 2012 08:30PM |
Registered: 12 years ago Posts: 27 |
Re: Newer uBoot as workaround to 3.2 kernel problem? April 10, 2012 10:39PM |
Registered: 13 years ago Posts: 264 |
Re: Newer uBoot as workaround to 3.2 kernel problem? April 16, 2012 04:04PM |
Registered: 13 years ago Posts: 21 |
Re: Newer uBoot as workaround to 3.2 kernel problem? April 16, 2012 07:51PM |
Registered: 12 years ago Posts: 501 |
Re: Newer uBoot as workaround to 3.2 kernel problem? April 17, 2012 12:31AM |
Admin Registered: 13 years ago Posts: 18,821 |
Boot the GFN from BOTH SATA PORTS - Re: Newer uBoot ... April 18, 2012 04:27PM |
Registered: 12 years ago Posts: 501 |
U-Boot 2011.12 (Apr 17 2012 - 16:35:46) Seagate GoFlexNet SoC: Kirkwood 88F6281_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 256 MiB In: serial Out: serial Err: serial Net: egiga0 88E1116 Initialized on egiga0 Hit any key to stop autoboot: 0 GoFlexNet> GoFlexNet> ide reset; ext2load ide 1:1 0x800000 /boot/uImage; ext2load ide 1:1 0x1100000 /boot/uInitrd; setenv bootargs 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)'; bootm 0x800000 0x1100000 Reset IDE: Bus 0: OK Bus 1: OK Device 0: Model: TOSHIBA MK1655GSX Firm: FG010D Ser#: X9AHTNGQT Type: Hard Disk Supports 48-bit addressing Capacity: 152627.8 MB = 149.0 GB (312581808 x 512) Device 1: Model: ST9320325AS Firm: 0002BSM1 Ser#: 5VD35RQG Type: Hard Disk Supports 48-bit addressing Capacity: 305245.3 MB = 298.0 GB (625142448 x 512) Loading file "/boot/uImage" from ide device 1:1 (hdb1) 1574664 bytes read Loading file "/boot/uInitrd" from ide device 1:1 (hdb1) 5739979 bytes read ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-3.1.10-kirkwood Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1574600 Bytes = 1.5 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 01100000 ... Image Name: initramfs-3.1.10-kirkwood Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5739915 Bytes = 5.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.1.10-kirkwood (root@debian) (gcc version 4.6.2 (Debian 4.6.2-11) ) #1 Thu Jan 19 06:14:30 UTC 2012 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] Machine: Marvell eSATA SheevaPlug Reference Board [ 0.000000] Memory policy: ECC disabled, Data cache writeback [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 [ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) [ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes) [ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [ 0.000000] allocated 524288 bytes of page_cgroup [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups ... [ 44.410849] NET: Registered protocol family 10 Cleaning up temporary files.... INIT: Entering runlevel: 2 Using makefile-style concurrent boot in runlevel 2. Starting internet superserver: inetd. Starting OpenBSD Secure Shell server: sshd. Starting Samba daemons: nmbd smbd. [ 47.473712] ip_tables: (C) 2000-2006 Netfilter Core Team /etc/rc.local: 17: /etc/rc.local: cannot create /sys/class/leds/dockstar:orange:misc/trigger: Directory nonexistent startpar: service(s) returned failure: rc.local ... failed! Debian GNU/Linux wheezy/sid debian ttyS0 debian login:
Re: Newer uBoot as workaround to 3.2 kernel problem? April 18, 2012 06:02PM |
Registered: 12 years ago Posts: 501 |