2017.07- 2024.10 U-Boot Kirkwood
Posted by bodhi
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug December 30, 2014 12:16PM |
Registered: 9 years ago Posts: 24 |
ok, i have tried all 3 ports
Marvell>> usb start
(Re)start USB...
USB: scanning bus for devices... 1 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
0 Storage Device(s) found
This changes when i move usb key from one usb to another, count changes from 2 to 1 but storage device ount remains at zero even if i try different usb key drives
thanks
Marvell>> usb start
(Re)start USB...
USB: scanning bus for devices... 1 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
0 Storage Device(s) found
This changes when i move usb key from one usb to another, count changes from 2 to 1 but storage device ount remains at zero even if i try different usb key drives
thanks
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug December 30, 2014 12:46PM |
Admin Registered: 13 years ago Posts: 19,102 |
jochar Wrote:
-------------------------------------------------------
> ok, i have tried all 3 ports
>
> Marvell>> usb start
> (Re)start USB...
> USB: scanning bus for devices... 1 USB Device(s)
> found
> Waiting for storage device(s) to settle before
> scanning...
> 0 Storage Device(s) found
>
> This changes when i move usb key from one usb to
> another, count changes from 2 to 1 but storage
> device ount remains at zero even if i try
> different usb key drives
>
> thanks
This could be quirk with the stock u-boot.
On the NSA325, booting with stock u-boot, the USB power was not enable. So a work around was:
However, since I don't have access to the NSA320S, I don't know if the above is true for it. It could be the NSA320S stock u-boot has similar problem.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> ok, i have tried all 3 ports
>
> Marvell>> usb start
> (Re)start USB...
> USB: scanning bus for devices... 1 USB Device(s)
> found
> Waiting for storage device(s) to settle before
> scanning...
> 0 Storage Device(s) found
>
> This changes when i move usb key from one usb to
> another, count changes from 2 to 1 but storage
> device ount remains at zero even if i try
> different usb key drives
>
> thanks
This could be quirk with the stock u-boot.
On the NSA325, booting with stock u-boot, the USB power was not enable. So a work around was:
mw.l f1010100 0020c000 usb reset
However, since I don't have access to the NSA320S, I don't know if the above is true for it. It could be the NSA320S stock u-boot has similar problem.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Pogoplug E02 with Bad eraseblock 4 December 30, 2014 01:09PM |
Registered: 10 years ago Posts: 10 |
bodhi Wrote:
-------------------------------------------------------
> rickgtx Wrote:
> --------------------------------------------------
> -----
> > Pogoplug E02 dmesg:
> >
>
> rickgtx,
>
> Even though the bad block is in 1st 1M, it's in
> the unused portion of NAND (block 4 is the 5th
> block). So you can follow the instruction in the
> first post to flash u-boot as normal. Don't need
> to do work around. Make sure to double check that
> you don't see any error during flashing.
U-Boot installed fine.
So bad eraseblocks 0,1,2,3 are the problem.
Thanks again Bodhi!
-------------------------------------------------------
> rickgtx Wrote:
> --------------------------------------------------
> -----
> > Pogoplug E02 dmesg:
> >
> > [root@pogoplug ~]# dmesg | grep -i 'bad' > > [ 10.728488] Scanning device for bad blocks > > [ 10.732941] Bad eraseblock 4 at > 0x000000080000 > >> >
>
> rickgtx,
>
> Even though the bad block is in 1st 1M, it's in
> the unused portion of NAND (block 4 is the 5th
> block). So you can follow the instruction in the
> first post to flash u-boot as normal. Don't need
> to do work around. Make sure to double check that
> you don't see any error during flashing.
U-Boot installed fine.
So bad eraseblocks 0,1,2,3 are the problem.
Thanks again Bodhi!
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug December 30, 2014 05:22PM |
Registered: 9 years ago Posts: 24 |
bodhi Wrote:
-------------------------------------------------------
> This could be quirk with the stock u-boot.
>
> On the NSA325, booting with stock u-boot, the USB
> power was not enable. So a work around was:
>
> However, since I don't have access to the NSA320S,
> I don't know if the above is true for it. It could
> be the NSA320S stock u-boot has similar problem.
This is pure magic you write here:
-------------------------------------------------------
> This could be quirk with the stock u-boot.
>
> On the NSA325, booting with stock u-boot, the USB
> power was not enable. So a work around was:
>
> mw.l f1010100 0020c000 > usb reset >>
> However, since I don't have access to the NSA320S,
> I don't know if the above is true for it. It could
> be the NSA320S stock u-boot has similar problem.
This is pure magic you write here:
Marvell>> mw.l f1010100 0020c000 Marvell>> usb reset (Re)start USB... USB: scanning bus for devices... 3 USB Device(s) found Waiting for storage device(s) to settle before scanning... 1 Storage Device(s) found
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug December 31, 2014 02:23AM |
Admin Registered: 13 years ago Posts: 19,102 |
Cool! so next to set up u-boot envs to boot USB.
The envs can be extracted from the default envs in this section in the 1st post and modified a bit:
The relevant envs to boot USB:
To set it in serial console:
And then boot it:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 12/31/2014 02:38AM by bodhi.
The envs can be extracted from the default envs in this section in the 1st post and modified a bit:
Quote
B. Flashing default u-boot envs image
........
uboot.2014.07-tld-2.environment (the content of the default envs in text format)
The relevant envs to boot USB:
mainlineLinux=yes device=0:1 rootdelay=10 rootfstype=ext3 usb_root=/dev/sda1 usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd usb_boot=run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype usb_init=mw.l f1010100 0020c000; usb reset bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot; bootcmd=run bootcmd_usb; reset
To set it in serial console:
setenv mainlineLinux 'yes' ...... setenv usb_load_uimage 'ext2load usb $device 0x800000 /boot/uImage' ...... setenv set_bootargs_usb 'setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype' .... and so on
And then boot it:
boot
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 12/31/2014 02:38AM by bodhi.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug December 31, 2014 05:53AM |
Registered: 9 years ago Posts: 24 |
ok this nearly worked
Marvell>> setenv mainlineLinux 'yes' Marvell>> setenv device '0:1' Marvell>> setenv rootdelay '10' Marvell>> setenv rootfstype 'ext3' Marvell>> setenv usb_root '/dev/sda1' Marvell>> setenv usb_load_uimage 'ext2load usb $device 0x800000 /boot/uImage' Marvell>> setenv usb_load_uinitrd 'ext2load usb $device 0x1100000 /boot/uInitrd' Marvell>> setenv usb_boot 'run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi' Marvell>> setenv usb_boot 'run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi' Marvell>> setenv set_bootargs_usb 'setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype' Marvell>> setenv usb_init 'mw.l f1010100 0020c000; usb reset' Marvell>> setenv bootcmd_usb 'run usb_init; run set_bootargs_usb; run usb_boot;' Marvell>> setenv bootcmd 'run bootcmd_usb; reset' Marvell>> boot (Re)start USB... USB: scanning bus for devices... 3 USB Device(s) found Waiting for storage device(s) to settle before scanning... 1 Storage Device(s) found ** Invalid boot device, use `dev[:part]' ** Unknown command 'if' - try 'help' Unknown command 'then' - try 'help' Unknown command 'else' - try 'help' This command can be used only if enaMonExt is set!
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug December 31, 2014 06:07AM |
Admin Registered: 13 years ago Posts: 19,102 |
Good progress :) Almost there.
Stock u-boot is limited so envs need to be adjusted:
This might still have syntax errors, especially the last line (you probably need to look at what stock Zyxel envs looks like and adjust to a similar syntax).
If the 1st 2 lines still have this syntax error
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 3 time(s). Last edit at 12/31/2014 06:13AM by bodhi.
Stock u-boot is limited so envs need to be adjusted:
usb_load_uimage=ext2load usb $(device) 0x800000 /boot/uImage usb_load_uinitrd=ext2load usb $(device) 0x1100000 /boot/uInitrd usb_boot=run usb_load_uimage; run usb_load_uinitrd; bootm 0x800000 0x1100000 set_bootargs_usb=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext3
This might still have syntax errors, especially the last line (you probably need to look at what stock Zyxel envs looks like and adjust to a similar syntax).
If the 1st 2 lines still have this syntax error
** Invalid boot device, use `dev[:part]' **then use these:
usb_load_uimage=ext2load usb 0:1 0x800000 /boot/uImage usb_load_uinitrd=ext2load usb 0:1 0x1100000 /boot/uInitrd
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 3 time(s). Last edit at 12/31/2014 06:13AM by bodhi.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug December 31, 2014 07:35AM |
Registered: 9 years ago Posts: 24 |
Here it iz:
so whats the next step? and for some reason console is spammed by:
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** MARVELL BOARD: DB6702A-GMtech LE
U-Boot 1.1.4 (Sep 3 2013 - 16:27:22) Marvell version: 3.6.0
U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CFB00
Soc: 88F6702 A1 CPU running @ 1000Mhz L2 running @ 500Mhz
SysClock = 400Mhz , TClock = 166Mhz
DRAM (DDR2) CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM Total size 256MB 16bit width
Addresses 10M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (10M - 7M): Done
NAND:128 MB
Flash: 0 kB
CPU : Marvell Feroceon (Rev 1)
Kernel address is 0xc80000.
Streaming disabled
Write allocate disabled
USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME]
Hit any key to stop autoboot: 0
Marvell>> setenv mainlineLinux 'yes'
Marvell>> setenv device '0:1'
Marvell>> setenv rootdelay '10'
Marvell>> setenv rootfstype 'ext3'
Marvell>> setenv usb_root '/dev/sda1'
Marvell>> setenv usb_load_uimage 'ext2load usb $(device) 0x800000 /boot/uImage'
Marvell>> setenv usb_load_uinitrd 'ext2load usb $(device) 0x1100000 /boot/uInitrd'
Marvell>> setenv usb_boot 'run usb_load_uimage; run usb_load_uinitrd; bootm 0x800000 0x1100000'
Marvell>> setenv set_bootargs_usb 'setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext3'
Marvell>> setenv usb_init 'mw.l f1010100 0020c000; usb reset'
Marvell>> setenv bootcmd_usb 'run usb_init; run set_bootargs_usb; run usb_boot;'
Marvell>> setenv bootcmd 'run bootcmd_usb; reset'
Marvell>> boot
(Re)start USB...
USB: scanning bus for devices... 3 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
1 Storage Device(s) found
....
.
......
............
.........................
...................................................
......................................................................................................
........................................................................
2835406 bytes read
....
.
...................
.........................
...................................................
......................................................................................................
.................................................................................................................................................................................................................
......................................................................................................................................................................................
6114335 bytes read
## Booting image at 00800000 ...
Image Name: Linux-3.17.0-kirkwood-tld-1
Created: 2014-12-30 1:03:18 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2835342 Bytes = 2.7 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000 ...
Image Name: initramfs-3.17.0-kirkwood-tld-1
Created: 2014-10-25 3:29:30 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 6114271 Bytes = 5.8 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
so whats the next step? and for some reason console is spammed by:
[ 117.494056] rtc-pcf8563 0-0051: pcf8563_write_block_data: err=-6 addr=02, data=57 [ 117.510851] rtc-pcf8563 0-0051: pcf8563_read_block_data: read error [ 117.524312] rtc-pcf8563 0-0051: pcf8563_read_block_data: read error [ 117.530728] rtc-pcf8563 0-0051: pcf8563_write_block_data: err=-6 addr=02, data=58 [ 117.543914] rtc-pcf8563 0-0051: pcf8563_read_block_data: read error [ 117.560030] rtc-pcf8563 0-0051: pcf8563_read_block_data: read error
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug December 31, 2014 08:25AM |
Registered: 9 years ago Posts: 24 |
also theres no network, dhcp wont get an IP, its very hard to use it cause of the rtc errors theres and error there every second abou 4 lines
EDIT:
This can be fixed by setting correct time, now i just need to figure out the network somehow
Edited 1 time(s). Last edit at 12/31/2014 08:31AM by jochar.
EDIT:
This can be fixed by setting correct time, now i just need to figure out the network somehow
Edited 1 time(s). Last edit at 12/31/2014 08:31AM by jochar.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug December 31, 2014 09:13AM |
Registered: 9 years ago Posts: 24 |
This is about all i get
not sure what to do now
root@debian:~# ifup eth0 Internet Systems Consortium DHCP Client 4.2.2 Copyright 2004-2011 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ [ 3863.644560] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Listening on LPF/eth0/4c:9e:ff:0b:73:72 Sending on LPF/eth0/4c:9e:ff:0b:73:72 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 No DHCPOFFERS received. No working leases in persistent database - sleeping.
root@debian:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp
cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# Unknown net device (/devices/platform/mv643xx_eth_port.0/net/eth0) (mv643xx_eth_port)
# Unknown net device (/devices/platform/mv643xx_eth_port.0/net/eth0) (mv643xx_eth_port)
#SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="xx:xx:xx:xx:xx:xx", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
not sure what to do now
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug December 31, 2014 10:13AM |
Registered: 10 years ago Posts: 70 |
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug December 31, 2014 10:47AM |
Admin Registered: 13 years ago Posts: 19,102 |
jochar Wrote:
-------------------------------------------------------
> This is about all i get
>
>
>
> not sure what to do now
I don't think you need allow-hotplug. But you do need "auto eth0".
And there is another file to check (I forgot the correct spelling):
/lib/udev/rules.d/xx-persistent...
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 12/31/2014 10:58AM by bodhi.
-------------------------------------------------------
> This is about all i get
>
> root@debian:~# ifup eth0 > Internet Systems Consortium DHCP Client 4.2.2 > Copyright 2004-2011 Internet Systems Consortium. > All rights reserved. > For info, please visit > https://www.isc.org/software/dhcp/ > > [ 3863.644560] IPv6: ADDRCONF(NETDEV_UP): eth0: > link is not ready > Listening on LPF/eth0/4c:9e:ff:0b:73:72 > Sending on LPF/eth0/4c:9e:ff:0b:73:72 > Sending on Socket/fallback > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 > interval 7 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 > interval 7 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 > interval 15 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 > interval 8 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 > interval 15 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 > interval 9 > No DHCPOFFERS received. > No working leases in persistent database - > sleeping. >>
>
> root@debian:~# cat /etc/network/interfaces > # This file describes the network interfaces > available on your system > # and how to activate them. For more information, > see interfaces(5). > > # The loopback network interface > auto lo > iface lo inet loopback > > # The primary network interface > allow-hotplug eth0 > iface eth0 inet dhcp >>
>
> cat /etc/udev/rules.d/70-persistent-net.rules
> # This file was automatically generated by the
> /lib/udev/write_net_rules
> # program, run by the
> persistent-net-generator.rules rules file.
> #
> # You can modify it, as long as you keep each rule
> on a single
> # line, and change only the value of the NAME=
> key.
>
> # Unknown net device
> (/devices/platform/mv643xx_eth_port.0/net/eth0)
> (mv643xx_eth_port)
>
> # Unknown net device
> (/devices/platform/mv643xx_eth_port.0/net/eth0)
> (mv643xx_eth_port)
> #SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="xx:xx:xx:xx:xx:xx",
> ATTR{dev_id}=="0x0", ATTR{type}=="1",
> KERNEL=="eth*", NAME="eth0"
>
>
> not sure what to do now
I don't think you need allow-hotplug. But you do need "auto eth0".
And there is another file to check (I forgot the correct spelling):
/lib/udev/rules.d/xx-persistent...
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 12/31/2014 10:58AM by bodhi.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug January 01, 2015 05:15PM |
Registered: 9 years ago Posts: 24 |
ls /lib/udev/rules.d/ 42-qemu-usb.rules 75-cd-aliases-generator.rules 50-udev-default.rules 75-net-description.rules 55-dm.rules 75-persistent-net-generator.rules 60-cdrom_id.rules 75-probe_mtd.rules 60-gnupg.rules 75-tty-description.rules 60-persistent-alsa.rules 78-sound-card.rules 60-persistent-input.rules 80-drivers.rules 60-persistent-serial.rules 80-networking.rules 60-persistent-storage-dm.rules 85-hwclock.rules 60-persistent-storage-tape.rules 91-permissions.rules 60-persistent-storage.rules 95-keyboard-force-release.rules 60-persistent-v4l.rules 95-keymap.rules 61-accelerometer.rules 95-udev-late.rules 70-udev-acl.rules
root@debian:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 allow-hotplug eth0 iface eth0 inet dhcp
this didnt work, still theres no network access
So how do i permanently make this device to boot into linux instead of the original software so i dont have to use ttl console to get some info from it?
net issue i bet has somethign to do with modules and or wrong module loaded
and hardware rtc clock is broken aswell no idea how to fix that as i never faced such an issue
dmesg | grep net [ 0.091137] Initializing cgroup subsys net_cls [ 0.110779] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set [ 0.780251] audit: initializing netlink subsys (disabled) [ 1.686762] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [ 2.937476] drop_monitor: Initializing network drop monitor service
Thanks for all the help and support so far, i bet we will have this up and running in a jiffy :)
Edited 2 time(s). Last edit at 01/01/2015 05:24PM by jochar.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug January 01, 2015 10:54PM |
Admin Registered: 13 years ago Posts: 19,102 |
jochar,
cat /lib/udev/rules.d/75-persistent-net-generator.rules
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
cat /lib/udev/rules.d/75-persistent-net-generator.rules
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug January 02, 2015 04:15AM |
Registered: 9 years ago Posts: 24 |
root@debian:/# cat /lib/udev/rules.d/75-persistent-net-generator.rules
# These rules generate rules to keep network interface names unchanged
# across reboots and write them to /etc/udev/rules.d/70-persistent-net.rules.
# variables used to communicate:
# MATCHADDR MAC address used for the match
# MATCHID bus_id used for the match
# MATCHDRV driver name used for the match
# MATCHIFTYPE interface type match
# COMMENT comment to add to the generated rule
# INTERFACE_NAME requested name supplied by external tool
# INTERFACE_NEW new interface name returned by rule writer
ACTION!="add", GOTO="persistent_net_generator_end"
SUBSYSTEM!="net", GOTO="persistent_net_generator_end"
# ignore the interface if a name has already been set
NAME=="?*", GOTO="persistent_net_generator_end"
# device name whitelist
KERNEL!="Eth*|ath*|Wlan*[0-9]|msh*|ra*|sta*|ctc*|lcs*|hsi*", \
GOTO="persistent_net_generator_end"
# ignore Xen virtual interfaces
SUBSYSTEMS=="xen", GOTO="persistent_net_generator_end"
# ignore UML virtual interfaces
DRIVERS=="uml-netdev", GOTO="persistent_net_generator_end"
# ignore "secondary" raw interfaces of the madwifi driver
KERNEL=="ath*", ATTRS{type}=="802", GOTO="persistent_net_generator_end"
# ignore "secondary" monitor interfaces of mac80211 drivers
KERNEL=="wlan*", ATTRS{type}=="803", GOTO="persistent_net_generator_end"
# by default match on the MAC address and interface type
ENV{MATCHADDR}="$attr{address}"
ENV{MATCHIFTYPE}="$attr{type}"
# match interface dev_id
ATTR{dev_id}=="?*", ENV{MATCHDEVID}="$attr{dev_id}"
# These vendors are known to violate the local MAC address assignment scheme
# Interlan, DEC (UNIBUS or QBUS), Apollo, Cisco, Racal-Datacom
ENV{MATCHADDR}=="02:07:01:*", GOTO="globally_administered_whitelist"
# 3Com
ENV{MATCHADDR}=="02:60:60:*", GOTO="globally_administered_whitelist"
# 3Com IBM PC; Imagen; Valid; Cisco; Apple
ENV{MATCHADDR}=="02:60:8c:*", GOTO="globally_administered_whitelist"
# Intel
ENV{MATCHADDR}=="02:a0:c9:*", GOTO="globally_administered_whitelist"
# Olivetti
ENV{MATCHADDR}=="02:aa:3c:*", GOTO="globally_administered_whitelist"
# CMC Masscomp; Silicon Graphics; Prime EXL
ENV{MATCHADDR}=="02:cf:1f:*", GOTO="globally_administered_whitelist"
# Prominet Corporation Gigabit Ethernet Switch
ENV{MATCHADDR}=="02:e0:3b:*", GOTO="globally_administered_whitelist"
# BTI (Bus-Tech, Inc.) IBM Mainframes
ENV{MATCHADDR}=="02:e6:d3:*", GOTO="globally_administered_whitelist"
# Novell 2000
ENV{MATCHADDR}=="52:54:4c:*", GOTO="globally_administered_whitelist"
# Realtec
ENV{MATCHADDR}=="52:54:ab:*", GOTO="globally_administered_whitelist"
# Kingston Technologies
ENV{MATCHADDR}=="e2:0c:0f:*", GOTO="globally_administered_whitelist"
# ignore interfaces with locally administered or null MAC addresses
# and VMWare, Hyper-V, KVM, Virtualbox and Xen virtual interfaces
ENV{MATCHADDR}=="?[2367abef]:*", ENV{MATCHADDR}=""
ENV{MATCHADDR}=="00:00:00:00:00:00", ENV{MATCHADDR}=""
ENV{MATCHADDR}=="00:0c:29:*|00:50:56:*|00:05:69:*|00:1C:14:*", \
ENV{MATCHADDR}=""
ENV{MATCHADDR}=="00:15:5d:*", ENV{MATCHADDR}=""
ENV{MATCHADDR}=="52:54:00:*|54:52:00:*", ENV{MATCHADDR}=""
ENV{MATCHADDR}=="08:00:27:*", ENV{MATCHADDR}=""
ENV{MATCHADDR}=="00:16:3e:*", ENV{MATCHADDR}=""
LABEL="globally_administered_whitelist"
# ibmveth interfaces have stable locally administered MAC addresses
SUBSYSTEMS=="ibmveth", ENV{MATCHADDR}="$attr{address}"
# S/390 interfaces are matched only by id
SUBSYSTEMS=="ccwgroup", \
ENV{MATCHDRV}="$driver", ENV{MATCHID}="$id", \
ENV{MATCHADDR}="", ENV{MATCHDEVID}=""
# terminate processing if there are not enough conditions to create a rule
ENV{MATCHADDR}=="", ENV{MATCHID}=="", ENV{INTERFACE_NAME}=="", \
GOTO="persistent_net_generator_end"
# provide nice comments for the generated rules
SUBSYSTEMS=="pci", \
ENV{COMMENT}="PCI device $attr{vendor}:$attr{device}"
SUBSYSTEMS=="pcmcia", \
ENV{COMMENT}="PCMCIA device $attr{card_id}:$attr{manf_id}"
SUBSYSTEMS=="usb", \
ENV{COMMENT}="USB device 0x$attr{idVendor}:0x$attr{idProduct}"
SUBSYSTEMS=="ccwgroup", \
ENV{COMMENT}="S/390 device at $id"
SUBSYSTEMS=="ibmveth", \
ENV{COMMENT}="LPAR virtual device at $id"
SUBSYSTEMS=="ieee1394", \
ENV{COMMENT}="Firewire device $attr{host_id}"
ENV{COMMENT}=="", \
ENV{COMMENT}="Unknown $env{SUBSYSTEM} device ($env{DEVPATH})"
ATTRS{driver}=="?*", \
ENV{COMMENT}="$env{COMMENT} ($attr{driver})"
# ignore interfaces without a driver link like bridges and VLANs, otherwise
# generate and write the rule
DRIVERS=="?*", IMPORT{program}="write_net_rules"
# rename the interface if requested
ENV{INTERFACE_NEW}=="?*", NAME="$env{INTERFACE_NEW}"
LABEL="persistent_net_generator_end"
Edited 1 time(s). Last edit at 01/02/2015 04:16AM by jochar.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug January 02, 2015 04:22AM |
Admin Registered: 13 years ago Posts: 19,102 |
OK. Let's delete everything in
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
/etc/resolve.configand replace with Google server
nameserver 8.8.8.8
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug January 02, 2015 06:19AM |
Registered: 9 years ago Posts: 24 |
bodhi Wrote:
-------------------------------------------------------
> OK. Let's delete everything in
>
>
>
it wont give me a Ip address neighter a static one works, so theres issues there with the adapter itself not the config, i wish i would be better in troubleshooting this type of faults
is it possible that wrong driver is loaded alltogether? meaning that there is a different chip like in NSA325
Edited 1 time(s). Last edit at 01/02/2015 06:21AM by jochar.
-------------------------------------------------------
> OK. Let's delete everything in
>
>
> /etc/resolve.config >> and replace with Google server
>
> nameserver 8.8.8.8 >i was desperate so i did that already
root@debian:~# cat /etc/resolv.conf nameserver 8.8.8.8
it wont give me a Ip address neighter a static one works, so theres issues there with the adapter itself not the config, i wish i would be better in troubleshooting this type of faults
is it possible that wrong driver is loaded alltogether? meaning that there is a different chip like in NSA325
Edited 1 time(s). Last edit at 01/02/2015 06:21AM by jochar.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug January 02, 2015 09:43AM |
Admin Registered: 13 years ago Posts: 19,102 |
Driver looks OK:
Did you check your router to see if it received the request?
If you've tried static IP, what was in /etc/network/interfaces and what did dmesg show?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
[ 1.686727] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [ 1.774735] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 4c:9e:ff:0b:73:72and then
[....] Configuring network interfaces...[ 23.529595] NET: Registered protocol family 10 Internet Systems Consortium DHCP Client 4.2.2 Copyright 2004-2011 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/But later:
DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 No DHCPOFFERS received.
Did you check your router to see if it received the request?
If you've tried static IP, what was in /etc/network/interfaces and what did dmesg show?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug January 02, 2015 10:09AM |
Registered: 9 years ago Posts: 24 |
cat /etc/network/interfaces # The primary network interface auto eth0 allow-hotplug eth0 iface eth0 inet static address 192.168.0.10 gateway 192.168.0.1 netmask 255.255.255.0 iface eth0 inet6 auto
ifconfig
eth0 Link encap:Ethernet HWaddr 4c:9e:ff:0b:73:72
inet addr:192.168.0.10 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:88
dmesg shows no relater errors just the rtc ones
dunno what to do next, if you want you can teamviewer in to see if you can get it going....
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug January 02, 2015 11:09AM |
Admin Registered: 13 years ago Posts: 19,102 |
Even with this, you still can't
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 01/02/2015 11:10AM by bodhi.
ssh root@192.168.0.10? it is a really strange problem.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 01/02/2015 11:10AM by bodhi.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug January 02, 2015 12:00PM |
Admin Registered: 13 years ago Posts: 19,102 |
jochar Wrote:
-------------------------------------------------------
>
>
> dmesg shows no relater errors just the rtc ones
>
> dunno what to do next, if you want you can
> teamviewer in to see if you can get it going....
Further thought, with static IP as above, can you ping the box from another box ?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
>
> cat /etc/network/interfaces > # The primary network interface > auto eth0 > allow-hotplug eth0 > iface eth0 inet static > address 192.168.0.10 > gateway 192.168.0.1 > netmask 255.255.255.0 > iface eth0 inet6 auto >>
>
> ifconfig > eth0 Link encap:Ethernet HWaddr > 4c:9e:ff:0b:73:72 > inet addr:192.168.0.10 > Bcast:192.168.0.255 Mask:255.255.255.0 > UP BROADCAST MULTICAST MTU:1500 > Metric:1 > RX packets:0 errors:0 dropped:0 > overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 > overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > Interrupt:88 >>
> dmesg shows no relater errors just the rtc ones
>
> dunno what to do next, if you want you can
> teamviewer in to see if you can get it going....
Further thought, with static IP as above, can you ping the box from another box ?
ping 192.168.0.10
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug January 02, 2015 08:26PM |
Registered: 9 years ago Posts: 24 |
Im traveling tomorrow and next few days so i wont be able to post progress...
but i have tried LAN ping test before when i had a ttl connection and im sure i was not able to ping the router (192.168.0.1) not sure if the other way will work if that directin fails with 100% packet loss
Thanks for the updates
but i have tried LAN ping test before when i had a ttl connection and im sure i was not able to ping the router (192.168.0.1) not sure if the other way will work if that directin fails with 100% packet loss
Thanks for the updates
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug January 02, 2015 09:00PM |
Admin Registered: 13 years ago Posts: 19,102 |
jochar Wrote:
-------------------------------------------------------
> Im traveling tomorrow and next few days so i wont
> be able to post progress...
>
> but i have tried LAN ping test before when i had a
> ttl connection and im sure i was not able to ping
> the router (192.168.0.1) not sure if the other way
> will work if that directin fails with 100% packet
> loss
>
> Thanks for the updates
No wonder! if you can't ping the router then problem is with your network :) nothing to do with the box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Im traveling tomorrow and next few days so i wont
> be able to post progress...
>
> but i have tried LAN ping test before when i had a
> ttl connection and im sure i was not able to ping
> the router (192.168.0.1) not sure if the other way
> will work if that directin fails with 100% packet
> loss
>
> Thanks for the updates
No wonder! if you can't ping the router then problem is with your network :) nothing to do with the box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
bastel
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug January 04, 2015 03:12PM |
I have a NSA320 (serial console etc)
with this uboot: uboot.NAND-NSA320-IDEfixedv4-scripted.kwb
and this rootfs: Debian-3.17.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
right now no SATA HDDs, and a USB conencted HDD. Plan is to use USB to boot and SATA as pure data drives.
I've run into some trouble, first USB power was not on (like mentioned above), I used usb start; sleep 5; usb start but mw.l f1010100 0020c000 is better. So it loads the uImage and kernel, but right before starting the kernel USB power is removed again, and the kernel can't find the root fs.
I have no idea how to get usb power enabled when the kernel starts...
(and what is modprobe: module i8042 not found in modules.dep, probably at keyboard..)
Log:
fail.txt
with this uboot: uboot.NAND-NSA320-IDEfixedv4-scripted.kwb
and this rootfs: Debian-3.17.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
right now no SATA HDDs, and a USB conencted HDD. Plan is to use USB to boot and SATA as pure data drives.
I've run into some trouble, first USB power was not on (like mentioned above), I used usb start; sleep 5; usb start but mw.l f1010100 0020c000 is better. So it loads the uImage and kernel, but right before starting the kernel USB power is removed again, and the kernel can't find the root fs.
I have no idea how to get usb power enabled when the kernel starts...
(and what is modprobe: module i8042 not found in modules.dep, probably at keyboard..)
Log:
fail.txt
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile January 06, 2015 09:54AM |
Registered: 9 years ago Posts: 50 |
Hello,
I believe I successfully tested UART flashing of uboot.2013.10-tld-1.nsa325.uart.kwb on NSA-325v2
What I am trying to find out is if I need to upgrade my U-boot to have possibility to use 3TB disk (GPT) without Hybrid MBR and maybe boot standard debian testing kernel? The box currently have following stock version of U-boot but I cannot find any changelog of U-boot with such information.
Can anyone give me advice about this?
Thanks,
Tomas
I believe I successfully tested UART flashing of uboot.2013.10-tld-1.nsa325.uart.kwb on NSA-325v2
U-Boot 2013.10-tld-1 (Aug 29 2014 - 22:07:26) ZyXEL NSA325 2-Bay Power Media Server SoC: Kirkwood 88F6282_?? DRAM: 512 MiB WARNING: Caches not enabled NAND: 128 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: egiga0 Warning: failed to set MAC address MV88E1318 PHY initialized on egiga0 NSA325>
What I am trying to find out is if I need to upgrade my U-boot to have possibility to use 3TB disk (GPT) without Hybrid MBR and maybe boot standard debian testing kernel? The box currently have following stock version of U-boot but I cannot find any changelog of U-boot with such information.
U-Boot 1.1.4 (Jul 18 2013 - 10:47:29) Marvell version: 3.5.9 U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CFB00
Can anyone give me advice about this?
Thanks,
Tomas
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile January 06, 2015 11:42AM |
Admin Registered: 13 years ago Posts: 19,102 |
Tomas,
uboot.2013.10-tld-1 does have capability of booting 3TB GPT. No need to use hybrid MBR. These features are supported:
- both FDT and non-FDT kernel booting
- supports EFI/GPT partition > 2TB (SATA and USB) either for booting or just attached.
- boot Ext4 rootfs
- SNTP (Simple NTP to set date time during U-Boot booting)
- bootz (boot with zImage).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 01/06/2015 11:45AM by bodhi.
uboot.2013.10-tld-1 does have capability of booting 3TB GPT. No need to use hybrid MBR. These features are supported:
- both FDT and non-FDT kernel booting
- supports EFI/GPT partition > 2TB (SATA and USB) either for booting or just attached.
- boot Ext4 rootfs
- SNTP (Simple NTP to set date time during U-Boot booting)
- bootz (boot with zImage).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 01/06/2015 11:45AM by bodhi.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile January 06, 2015 12:04PM |
Registered: 9 years ago Posts: 50 |
Bodhi,
my question was if I need to update from current version? As I am unable to find any feature list of U-Boot 1.1.4.
The update is risky process from my point of view as I do not completely understand what am I doing and how stable is the uboot.2013.10-tld-1.
And maybe another question (as I do not understand FDT features) is that if it could maybe be able to boot default debian kernel from testing? That would be nice as I would like to run default debian installer image. Whis I so far did by modifing the image with your kernel.
Thanks,
Tomas
my question was if I need to update from current version? As I am unable to find any feature list of U-Boot 1.1.4.
The update is risky process from my point of view as I do not completely understand what am I doing and how stable is the uboot.2013.10-tld-1.
And maybe another question (as I do not understand FDT features) is that if it could maybe be able to boot default debian kernel from testing? That would be nice as I would like to run default debian installer image. Whis I so far did by modifing the image with your kernel.
Thanks,
Tomas
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile January 06, 2015 12:30PM |
Admin Registered: 13 years ago Posts: 19,102 |
Tomas,
Stock u-boot does not have >2 TB HDD GPT support. So in order to boot with GPT 3TB HDD, you will need new u-boot.
And no, you can't install mainline Debian, because it is not available for NSA325.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Stock u-boot does not have >2 TB HDD GPT support. So in order to boot with GPT 3TB HDD, you will need new u-boot.
And no, you can't install mainline Debian, because it is not available for NSA325.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug January 07, 2015 02:13AM |
Registered: 9 years ago Posts: 50 |
Bodhi,
thank you very much, so I will try to update.
Why I thought that booting mainline Debian kernel could be possible is because when you don't have arcNumber set the kernel gives you list of supported platforms.
Your kernel listed:
And Debians listed:
So I thought that last option might work with the new U-boot.
Tomas
thank you very much, so I will try to update.
Why I thought that booting mainline Debian kernel could be possible is because when you don't have arcNumber set the kernel gives you list of supported platforms.
Your kernel listed:
ID (hex) NAME 0000089b LaCie d2 Network v2 0000089e LaCie 5Big Network v2 0000089c LaCie 2Big Network v2 00000b44 Marvell OpenRD Ultimate Board 00000939 Marvell OpenRD Client Board 00000915 Marvell OpenRD Base Board 00000691 Marvell RD-88F6192-NAS Development Board 00000692 Marvell RD-88F6281 Reference Board 00000b1e HP t5325 Thin Client 0000085b QNAP TS-119/TS-219 000009c6 QNAP TS-41x 00000bb6 Seagate FreeAgent DockStar 00000a76 Marvell eSATA SheevaPlug Reference Board 00000831 Marvell SheevaPlug Reference Board 00000a63 Marvell GuruPlug Reference Board 00000c11 Seagate GoFlex Net 00000d0a Seagate GoFlex Home 00000b36 Iomega iConnect Wireless 00000f78 Pogoplug V4 00000dd6 Pogoplug E02 00000f74 ZyXEL NSA320 2-Bay Power Media Server 00001005 USI Topkick 00000fb6 Zyxel NSA-310 0000118f ZyXEL NSA325 2-Bay Power Media Server 00000ab7 Netgear MS2110
And Debians listed:
ID (hex) NAME 0000089b LaCie d2 Network v2 0000089e LaCie 5Big Network v2 0000089c LaCie 2Big Network v2 00000b44 Marvell OpenRD Ultimate Board 00000939 Marvell OpenRD Client Board 00000915 Marvell OpenRD Base Board 00000691 Marvell RD-88F6192-NAS Development Board 00000692 Marvell RD-88F6281 Reference Board 00000b1e HP t5325 Thin Client 0000085b QNAP TS-119/TS-219 000009c6 QNAP TS-41x ffffffff Marvell Kirkwood (Flattened Device Tree)
So I thought that last option might work with the new U-boot.
Tomas
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug January 07, 2015 03:55AM |
Admin Registered: 13 years ago Posts: 19,102 |
@Tomas,
Very perceptive! you are right in a way. Since mainline kernel support Kirwood FDT, you can basically install it and use the appropriate DTS to boot the kernel. However, the NSA325 DTS is not in the mainine yet, so you need to use the NSA325 DTS I've included in the patch in the kernel thread and boot with it. This will give you a basic NSA325 supports. But in the Kirkwood patch set, there are individual patches that are customized functionalities for Kirkwood boxes. For examples, LED patches.
So the bottom line is: yes the mailine kernel will work with the NSA325 DTS (in the patch), but it will lack some functionalities that we have in my kernel build.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Very perceptive! you are right in a way. Since mainline kernel support Kirwood FDT, you can basically install it and use the appropriate DTS to boot the kernel. However, the NSA325 DTS is not in the mainine yet, so you need to use the NSA325 DTS I've included in the patch in the kernel thread and boot with it. This will give you a basic NSA325 supports. But in the Kirkwood patch set, there are individual patches that are customized functionalities for Kirkwood boxes. For examples, LED patches.
So the bottom line is: yes the mailine kernel will work with the NSA325 DTS (in the patch), but it will lack some functionalities that we have in my kernel build.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Sorry, you can't reply to this topic. It has been closed.