Debian on Linksys EA4500 / EA4200
Posted by megal0maniac
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 02:43PM |
Registered: 9 years ago Posts: 429 |
megal0maniac Wrote:
> It also seems to be ignoring bootcmd. I first
> changed it to boot from USB followed by flash,
> then removed the section about flash altogether
> but it still boots from flash. Not sure what the
> entry point is if not bootcmd...
Don't forget you need to saveenv if you want to make the boot environment changes permanent after a power cycle. But hold off on doing that until you are certain your env's are correct, i.e. confirm functionality with a set of env modification through a few boot cycles. If they're good to go, then saveenv.
> It also seems to be ignoring bootcmd. I first
> changed it to boot from USB followed by flash,
> then removed the section about flash altogether
> but it still boots from flash. Not sure what the
> entry point is if not bootcmd...
Don't forget you need to saveenv if you want to make the boot environment changes permanent after a power cycle. But hold off on doing that until you are certain your env's are correct, i.e. confirm functionality with a set of env modification through a few boot cycles. If they're good to go, then saveenv.
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 02:48PM |
Registered: 9 years ago Posts: 1,037 |
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 02:48PM |
Registered: 9 years ago Posts: 429 |
bobafetthotmail Wrote:
-------------------------------------------------------
> Can you test if your box can kwboot a sheevaplug
> u-boot? (must use the command line ending with -p
> with the images we have)
megal0maniac Wrote:
-------------------------------------------------------
>JTAG.
>Unfortunately it doesn't work with this version of u-boot
.>/kwboot -b /home/michael/uboot.2015.10-tld-1.sheevaplug.mtd0.kwb -t -B 115200 /dev/ttyUSB0
>Sending boot message. Please reboot the target...|
>Sending boot image...
>xmodem: Bad message
I've seen bodhi suggest rapid successive attempts at this if it's not cooperative as the handshaking can sometimes be problematic.
-------------------------------------------------------
> Can you test if your box can kwboot a sheevaplug
> u-boot? (must use the command line ending with -p
> with the images we have)
megal0maniac Wrote:
-------------------------------------------------------
>JTAG.
>Unfortunately it doesn't work with this version of u-boot
.>/kwboot -b /home/michael/uboot.2015.10-tld-1.sheevaplug.mtd0.kwb -t -B 115200 /dev/ttyUSB0
>Sending boot message. Please reboot the target...|
>Sending boot image...
>xmodem: Bad message
I've seen bodhi suggest rapid successive attempts at this if it's not cooperative as the handshaking can sometimes be problematic.
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 02:56PM |
Registered: 9 years ago Posts: 1,037 |
if you run out of patience with the kwboot - i did - my issue was a noisy adaptor, but thats another story..
try this. first of all make sure you have a tftp server available on your network,
To attempt chainloading
load your uboot onto the tftp server
break the boot sequence
from the console try the following commands
dont save! just reboot if nothing usable happens
Edited my rather poor instructions!
Edited 3 time(s). Last edit at 03/24/2016 03:04PM by Gravelrash.
try this. first of all make sure you have a tftp server available on your network,
To attempt chainloading
load your uboot onto the tftp server
break the boot sequence
from the console try the following commands
setenv serverip 10.0.0.10 # IP of your TFTP server setenv ipaddr 10.0.0.6 # IP for your devicer tftpboot 0x0800000 ubootname.kwb # a kirkwoody-esque load address go 0x800200
dont save! just reboot if nothing usable happens
Edited my rather poor instructions!
Edited 3 time(s). Last edit at 03/24/2016 03:04PM by Gravelrash.
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 03:35PM |
Registered: 8 years ago Posts: 298 |
> post the .dtb, im certain Mr Bodhi, would love to look at it....
The dtb is a binary blob for the kernel.
Bodhi isn't a machine, he needs the dts, the human-readable sourcecode used to make the dtb.
I'm attaching it to this post.
I don't understand where exactly the dts I'm uploading here came from as the openwrt git is just a bunch of scripts, but I have it in my on-disk build environment of "openwrt-for-kirkwood" (done for the other project in this same offtopic section), and it bears the mails of 2 openwrt devs, so I assume it is from them.
I don't see it in mainline linux.
The dtb is a binary blob for the kernel.
Bodhi isn't a machine, he needs the dts, the human-readable sourcecode used to make the dtb.
I'm attaching it to this post.
I don't understand where exactly the dts I'm uploading here came from as the openwrt git is just a bunch of scripts, but I have it in my on-disk build environment of "openwrt-for-kirkwood" (done for the other project in this same offtopic section), and it bears the mails of 2 openwrt devs, so I assume it is from them.
I don't see it in mainline linux.
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 03:36PM |
Registered: 10 years ago Posts: 82 |
I did saveenv after making changes - looks like auto_recovery needed to be set to 'no' in order for it not to boot from flash every time. That's all well and good, but it appears to set itself back to 'yes' after booting from flash :/
Another good reason to run a custom u-boot...
I'll try the chain loading in the morning. Thanks for all the advice!
Another good reason to run a custom u-boot...
I'll try the chain loading in the morning. Thanks for all the advice!
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 03:46PM |
Registered: 8 years ago Posts: 298 |
> Unfortunately it doesn't work with this version of u-boot
kwboot talks to the SoC's onboard boot ROM, the one that looks into NAND and then boots the u-boot. Current uboot version is not relevant as this is there to save your backside even if the NAND is erased or damaged, if the SoC is new enough, the feature will be there.
Anyway, you typed the wrong command (everyone did, me too back then), I should have been more explicit.
You must add a -p at the end like in this line as the u-boots here are for nand-flashing and kwboot has to adjust things.
write this command and let's see if it runs (note the -p at the end)
Edited 2 time(s). Last edit at 03/24/2016 03:50PM by bobafetthotmail.
kwboot talks to the SoC's onboard boot ROM, the one that looks into NAND and then boots the u-boot. Current uboot version is not relevant as this is there to save your backside even if the NAND is erased or damaged, if the SoC is new enough, the feature will be there.
Anyway, you typed the wrong command (everyone did, me too back then), I should have been more explicit.
You must add a -p at the end like in this line as the u-boots here are for nand-flashing and kwboot has to adjust things.
write this command and let's see if it runs (note the -p at the end)
./kwboot -b /home/michael/uboot.2015.10-tld-1.sheevaplug.mtd0.kwb -t -B 115200 /dev/ttyUSB0 -p
Edited 2 time(s). Last edit at 03/24/2016 03:50PM by bobafetthotmail.
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 03:49PM |
Registered: 11 years ago Posts: 149 |
kwboot is mostly supported for this device as it passed handshaking stage!
Please patch your kwboot and try again.
patch for kwboot
-syong
Please patch your kwboot and try again.
patch for kwboot
-syong
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 03:54PM |
Registered: 10 years ago Posts: 82 |
Hah! It does work. Thanks for pointing out my error.
Unfortunately, it won't boot the sheevaplug image - it gets stuck just before it prints out the amount of RAM.
Unfortunately, it won't boot the sheevaplug image - it gets stuck just before it prints out the amount of RAM.
99 % [....................................] [Type Ctrl-\ + c to quit] U-Boot 2015.10-tld-1 (Nov 08 2015 - 21:01:07 -0800) Marvell-Sheevaplug SoC: Kirkwood 88F6282_A1 DRAM:
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 03:57PM |
Admin Registered: 13 years ago Posts: 18,545 |
Are we having fun :) I went to bed and woke up with 30+ posts in this thread :))
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 03:57PM |
Registered: 11 years ago Posts: 149 |
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 03:59PM |
Admin Registered: 13 years ago Posts: 18,545 |
Ok so to recap:
- Debian works with stock u-boot
- kwboot works, just need a different u-boot. Let me take a closer look at the serial boot log.
Good job to all :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
- Debian works with stock u-boot
- kwboot works, just need a different u-boot. Let me take a closer look at the serial boot log.
Good job to all :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 04:00PM |
Registered: 8 years ago Posts: 298 |
> kwboot works, just need a different u-boot. Let me take a closer look at the serial boot log.
I also posted the dts a few posts above.
> Hah! It does work. Thanks for pointing out my error.
Awesome. This will make testing a new u-boot easy and safe.
> Unfortunately, it won't boot the sheevaplug image
Not a problem. What matters here is that it loads the u-boot over serial and boots it, sheevaplug's u-boot isn't configured to initialize this board.
Edited 1 time(s). Last edit at 03/24/2016 04:01PM by bobafetthotmail.
I also posted the dts a few posts above.
> Hah! It does work. Thanks for pointing out my error.
Awesome. This will make testing a new u-boot easy and safe.
> Unfortunately, it won't boot the sheevaplug image
Not a problem. What matters here is that it loads the u-boot over serial and boots it, sheevaplug's u-boot isn't configured to initialize this board.
Edited 1 time(s). Last edit at 03/24/2016 04:01PM by bobafetthotmail.
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 04:02PM |
Registered: 9 years ago Posts: 1,037 |
bobafetthotmail Wrote:
----------------------------------------------------
> Bodhi isn't a machine, he needs the dts, the
> human-readable sourcecode used to make the dtb.
>
> I'm attaching it to this post.
oops... *skulks off back to his evil lair to plot the demise of more unsuspecting HP kit*
----------------------------------------------------
> Bodhi isn't a machine, he needs the dts, the
> human-readable sourcecode used to make the dtb.
>
> I'm attaching it to this post.
oops... *skulks off back to his evil lair to plot the demise of more unsuspecting HP kit*
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 04:04PM |
Admin Registered: 13 years ago Posts: 18,545 |
bobafetthotmail,
> Bodhi isn't a machine, he needs the dts, the
> human-readable sourcecode used to make the dtb.
:))
>
> I'm attaching it to this post.
>
Could you find the DTS with the same name as the dtb that megalomaniac used?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Bodhi isn't a machine, he needs the dts, the
> human-readable sourcecode used to make the dtb.
:))
>
> I'm attaching it to this post.
>
Could you find the DTS with the same name as the dtb that megalomaniac used?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 04:06PM |
Admin Registered: 13 years ago Posts: 18,545 |
Gravelrash Wrote:
-------------------------------------------------------
> bobafetthotmail Wrote:
> --------------------------------------------------
> --
> > Bodhi isn't a machine, he needs the dts, the
> > human-readable sourcecode used to make the dtb.
>
> >
> > I'm attaching it to this post.
>
> oops... *skulks off back to his evil lair to plot
> the demise of more unsuspecting HP kit*
:))
Actually even with the lack of DTS, DTB would be OK too (reverse engineering works).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> bobafetthotmail Wrote:
> --------------------------------------------------
> --
> > Bodhi isn't a machine, he needs the dts, the
> > human-readable sourcecode used to make the dtb.
>
> >
> > I'm attaching it to this post.
>
> oops... *skulks off back to his evil lair to plot
> the demise of more unsuspecting HP kit*
:))
Actually even with the lack of DTS, DTB would be OK too (reverse engineering works).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 04:15PM |
Registered: 10 years ago Posts: 82 |
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 04:15PM |
Registered: 8 years ago Posts: 298 |
bodhi Wrote:
-------------------------------------------------------
>
> Could you find the DTS with the same name as the
> dtb that megalomaniac used?
Mine comes from openwrt trunk (current sources), his own comes from openwrt 15, released in october 2015.
I don't have one with the same name, but the one I posted is 100% that device, as seen inside the dts, and because "viper" is the codename of that board, as seen in openwrt wiki https://wiki.openwrt.org/toh/linksys/ea4500
It seems like Linksys E4200v2 and EA4500 have the same board or something, as in newer openwrt builds they are both supported by the same image with "viper" in the name.
-------------------------------------------------------
>
> Could you find the DTS with the same name as the
> dtb that megalomaniac used?
Mine comes from openwrt trunk (current sources), his own comes from openwrt 15, released in october 2015.
I don't have one with the same name, but the one I posted is 100% that device, as seen inside the dts, and because "viper" is the codename of that board, as seen in openwrt wiki https://wiki.openwrt.org/toh/linksys/ea4500
It seems like Linksys E4200v2 and EA4500 have the same board or something, as in newer openwrt builds they are both supported by the same image with "viper" in the name.
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 04:20PM |
Registered: 10 years ago Posts: 82 |
bobafetthotmail Wrote:
> It seems like Linksys E4200v2 and EA4500 have the
> same board or something, as in newer openwrt
> builds they are both supported by the same image
> with "viper" in the name.
It is in fact exactly the same hardware. Only the firmware differs between devices. OpenWRT doesn't know which board it's running on and it doesn't care :)
> It seems like Linksys E4200v2 and EA4500 have the
> same board or something, as in newer openwrt
> builds they are both supported by the same image
> with "viper" in the name.
It is in fact exactly the same hardware. Only the firmware differs between devices. OpenWRT doesn't know which board it's running on and it doesn't care :)
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 06:46PM |
Admin Registered: 13 years ago Posts: 18,545 |
I've moved this to Debian forum, since it is Debian and u-boot now.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 3 time(s). Last edit at 03/24/2016 07:02PM by bodhi.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 3 time(s). Last edit at 03/24/2016 07:02PM by bodhi.
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 06:48PM |
Admin Registered: 13 years ago Posts: 18,545 |
megal0maniac,
Coud you also print out the envs in serial console right before executing "boot"
And please post the entire serial console from kwboot command to the Debian prompt. Thanks!
UPDATE:
In Debian, also get:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/24/2016 07:02PM by bodhi.
Coud you also print out the envs in serial console right before executing "boot"
...... printenv boot
And please post the entire serial console from kwboot command to the Debian prompt. Thanks!
UPDATE:
In Debian, also get:
lsmod ifconfig -a
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/24/2016 07:02PM by bodhi.
|
Re: Linksys EA4500 / EA4200 support March 24, 2016 08:21PM |
Admin Registered: 13 years ago Posts: 18,545 |
Try kwboot with the Dockstar u-boot:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
uboot.2015.10-tld-1.dockstar.bodhi.tar md5 296b7bb1ee2da2335510496136bb98a4
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Linksys EA4500 / EA4200 support March 25, 2016 01:31AM |
Registered: 10 years ago Posts: 82 |
The device boots with the Dockstar u-boot, but the network interfaces don't come up (wired or wireless)
I don't even get link lights so it seems like hardware initialisation failure.
There is a cable connected to what should be eth0.
Everything works in the stock u-boot.
I don't even get link lights so it seems like hardware initialisation failure.
There is a cable connected to what should be eth0.
Everything works in the stock u-boot.
./kwboot -b /home/michael/uboot.2015.10-tld-1.dockstar.mtd0.kwb -t -B 115200 /dev/ttyUSB0 -p
Sending boot message. Please reboot the target...\
Sending boot image...
0 % [......................................................................]
1 % [......................................................................]
(snipped)
97 % [......................................................................]
99 % [....................................]
[Type Ctrl-\ + c to quit]
U-Boot 2015.10-tld-1 (Nov 06 2015 - 15:56:21 -0800)
Seagate FreeAgent DockStar
SoC: Kirkwood 88F6282_A1
DRAM: 128 MiB (ECC not enabled)
WARNING: Caches not enabled
NAND: 128 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: egiga0
PHY reset timed out
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 0
DockStar> printenv
arcNumber=2097
baudrate=115200
bootcmd=run bootcmd_uenv; run bootcmd_usb; reset
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
ethaddr=b6:d0:5e:0f:a1:17
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
rootdelay=10
rootfstype=ext2
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
stderr=serial
stdin=serial
stdout=serial
uenv_import=echo importing envs ...; env import -t 0x810000
uenv_load=usb start; setenv uenv_loaded 0; for devtype in usb; do for disknum in 0; do run uenv_read_disk; done; done
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 0x810000 /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if $devtype part $disknum; then run uenv_read; fi
usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1
Environment size: 1430/131068 bytes
DockStar> boot
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
Partition Map for USB device 0 -- Partition Type: DOS
Part Start Sector Num Sectors UUID Type
1 2048 15631360 0001222a-01 83
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **
3166062 bytes read in 382 ms (7.9 MiB/s)
7179935 bytes read in 503 ms (13.6 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-4.4.0-kirkwood-tld-1
Created: 2016-03-24 17:59:28 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3165998 Bytes = 3 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-4.4.0-kirkwood-tld-1
Created: 2016-03-24 17:59:48 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7179871 Bytes = 6.8 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 4.4.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Mon Jan 25 20:35:24 PST 2016
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine model: Linksys EA4500
[ 0.000000] Memory policy: 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=/dev/sda1 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] Memory: 113628K/131072K available (6007K kernel code, 573K rwdata, 1992K rodata, 296K init, 312K bss, 17444K reserved, 0K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xc8800000 - 0xff800000 ( 880 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc07d7ef4 (8000 kB)
[ 0.000000] .init : 0xc07d8000 - 0xc0822000 ( 296 kB)
[ 0.000000] .data : 0xc0822000 - 0xc08b169c ( 574 kB)
[ 0.000000] .bss : 0xc08b169c - 0xc08ff9d0 ( 313 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Build-time adjustment of leaf fanout to 32.
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[ 0.000009] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[ 0.000328] Console: colour dummy device 80x30
[ 0.000359] Calibrating delay loop... 1196.85 BogoMIPS (lpj=5984256)
[ 0.090099] pid_max: default: 32768 minimum: 301
[ 0.090209] Security Framework initialized
[ 0.090286] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090306] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.091103] Initializing cgroup subsys io
[ 0.091137] Initializing cgroup subsys devices
[ 0.091162] Initializing cgroup subsys freezer
[ 0.091196] Initializing cgroup subsys net_cls
[ 0.091280] CPU: Testing write buffer coherency: ok
[ 0.091753] Setting up static identity map for 0x8200 - 0x8258
[ 0.092060] mvebu-soc-id: MVEBU SoC ID=0x6282, Rev=0x1
[ 0.095805] devtmpfs: initialized
[ 0.100671] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.101155] prandom: seed boundary self test passed
[ 0.104893] prandom: 100 self tests passed
[ 0.104920] pinctrl core: initialized pinctrl subsystem
[ 0.106312] NET: Registered protocol family 16
[ 0.106790] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.130107] cpuidle: using governor ladder
[ 0.160103] cpuidle: using governor menu
[ 0.160539] Feroceon L2: Enabling L2
[ 0.160586] Feroceon L2: Cache support initialised.
[ 0.160970] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[ 0.161077] [Firmware Info]: /ocp@f1000000/ethernet-controller@76000/ethernet1-port@0: local-mac-address is not set
[ 0.165970] No ATAGs?
[ 0.201619] vgaarb: loaded
[ 0.201989] usbcore: registered new interface driver usbfs
[ 0.202071] usbcore: registered new interface driver hub
[ 0.202143] usbcore: registered new device driver usb
[ 0.203259] clocksource: Switched to clocksource orion_clocksource
[ 0.258779] NET: Registered protocol family 2
[ 0.259594] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.259621] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.259642] TCP: Hash tables configured (established 1024 bind 1024)
[ 0.259711] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.259734] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.259929] NET: Registered protocol family 1
[ 0.260339] RPC: Registered named UNIX socket transport module.
[ 0.260352] RPC: Registered udp transport module.
[ 0.260359] RPC: Registered tcp transport module.
[ 0.260367] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.260655] Unpacking initramfs...
[ 0.902264] Freeing initrd memory: 7012K (c1100000 - c17d9000)
[ 0.902410] NetWinder Floating Point Emulator V0.97 (double precision)
[ 0.903586] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.903660] audit: initializing netlink subsys (disabled)
[ 0.903714] audit: type=2000 audit(0.900:1): initialized
[ 0.904072] Initialise system trusted keyring
[ 0.904482] zbud: loaded
[ 0.904773] VFS: Disk quotas dquot_6.6.0
[ 0.904840] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.905399] NFS: Registering the id_resolver key type
[ 0.905439] Key type id_resolver registered
[ 0.905449] Key type id_legacy registered
[ 0.905475] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.905490] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 0.905711] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 0.906237] Key type big_key registered
[ 0.926493] Key type asymmetric registered
[ 0.926517] Asymmetric key parser 'x509' registered
[ 0.926618] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.926640] io scheduler noop registered
[ 0.926656] io scheduler deadline registered
[ 0.926719] io scheduler cfq registered (default)
[ 0.928103] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[ 0.928766] irq: Cannot allocate irq_descs @ IRQ31, assuming pre-allocated
[ 0.929190] irq: Cannot allocate irq_descs @ IRQ63, assuming pre-allocated
[ 0.930085] mvebu-pcie mbus:pcie-controller: PCI host bridge to bus 0000:00
[ 0.930106] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
[ 0.930119] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 0.930133] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.930858] PCI: bus0: Fast back to back transfers disabled
[ 0.930884] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.930912] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.931111] PCI: bus1: Fast back to back transfers enabled
[ 0.931333] PCI: bus2: Fast back to back transfers enabled
[ 0.931451] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.931470] pci 0000:00:02.0: PCI bridge to [bus 02]
[ 0.931867] mv_xor f1060800.xor: Marvell shared XOR driver
[ 0.973965] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 0.974223] mv_xor f1060900.xor: Marvell shared XOR driver
[ 1.013930] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 1.014437] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 1.015873] console [ttyS0] disabled
[ 1.015938] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
[ 1.695165] console [ttyS0] enabled
[ 1.700002] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[ 1.706428] nand: Hynix H27U1G8F2BTR-BC
[ 1.710282] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 1.717911] Scanning device for bad blocks
[ 1.799993] 4 cmdlinepart partitions found on MTD device orion_nand
[ 1.806307] Creating 4 MTD partitions on "orion_nand":
[ 1.811473] 0x000000000000-0x000000100000 : "u-boot"
[ 1.817782] 0x000000100000-0x000000500000 : "uImage"
[ 1.824047] 0x000000500000-0x000002500000 : "rootfs"
[ 1.830317] 0x000002500000-0x000008000000 : "data"
[ 1.837617] libphy: Fixed MDIO Bus: probed
[ 1.842087] libphy: orion_mdio_bus: probed
[ 1.846430] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 1.854759] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address b6:d0:5e:0f:a1:17
[ 1.864224] mv643xx_eth_port mv643xx_eth_port.1 eth1: port 0 with MAC address 00:00:00:00:00:00
[ 1.873112] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.879725] ehci-pci: EHCI PCI platform driver
[ 1.884290] ehci-orion: EHCI orion driver
[ 1.888501] orion-ehci f1050000.ehci: EHCI Host Controller
[ 1.894069] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[ 1.901921] orion-ehci f1050000.ehci: irq 29, io mem 0xf1050000
[ 1.923298] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 1.929574] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.936421] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.943694] usb usb1: Product: EHCI Host Controller
[ 1.948591] usb usb1: Manufacturer: Linux 4.4.0-kirkwood-tld-1 ehci_hcd
[ 1.955254] usb usb1: SerialNumber: f1050000.ehci
[ 1.960736] hub 1-0:1.0: USB hub found
[ 1.964595] hub 1-0:1.0: 1 port detected
[ 1.969496] mousedev: PS/2 mouse device common for all mice
[ 1.975528] i2c /dev entries driver
[ 1.980245] hidraw: raw HID events driver (C) Jiri Kosina
[ 1.986120] drop_monitor: Initializing network drop monitor service
[ 1.992671] NET: Registered protocol family 17
[ 1.997467] Key type dns_resolver registered
[ 2.002622] registered taskstats version 1
[ 2.006826] Loading compiled-in X.509 certificates
[ 2.011693] zswap: loaded using pool lzo/zbud
[ 2.025063] Key type encrypted registered
[ 2.029682] hctosys: unable to open rtc device (rtc0)
[ 2.037156] Freeing unused kernel memory: 296K (c07d8000 - c0822000)
Loading, please wait...
[ 2.114453] systemd-udevd[81]: starting version 215
[ 2.121424] random: systemd-udevd urandom read with 3 bits of entropy available
[ 2.283358] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 2.444310] usb 1-1: New USB device found, idVendor=0781, idProduct=5571
[ 2.451064] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.458263] usb 1-1: Product: Cruzer Fit
[ 2.462218] usb 1-1: Manufacturer: SanDisk
[ 2.466353] usb 1-1: SerialNumber: 4C530008220226116131
[ 2.489612] SCSI subsystem initialized
[ 2.498115] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 2.504753] scsi host0: usb-storage 1-1:1.0
[ 2.510714] usbcore: registered new interface driver usb-storage
[ 2.519895] usbcore: registered new interface driver uas
[ 3.504776] scsi 0:0:0:0: Direct-Access SanDisk Cruzer Fit 1.27 PQ: 0 ANSI: 6
[ 3.522748] sd 0:0:0:0: [sda] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
[ 3.532210] sd 0:0:0:0: [sda] Write Protect is off
[ 3.537832] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 3.554085] sda: sda1
[ 3.560085] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 3.569840] sd 0:0:0:0: Attached scsi generic sg0 type 0
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Checking root file system ... fsck from util-linux 2.25.2
rootfs: clean, 17223/488640 files, 298746/1953920 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 2.88 booting
[info] Using makefile-style concurrent boot in runlevel S.
[....] Starting the hotplug events dispatcher: udevd[ 14.076388] systemd-udevd[288]: starting version 215
. ok
[....] Synthesizing the initial hotplug events...[ 14.373027] input: gpio_keys as /devices/platform/gpio_keys/input/input0
done.
[ 14.422616] marvell-cesa: probe of f1030000.crypto failed with error -524
[....] Waiting for /dev to be fully populated...[ 14.647744] orion_wdt: Initial timeout 21 sec
done.
[ ok ] Activating swap...done.
[....] Checking root file system...fsck from util-linux 2.25.2
rootfs: clean, 17223/488640 files, 298746/1953920 blocks
done.
[ 15.687233] random: nonblocking pool is initialized
[ ok ] Activating lvm and md swap...done.
[....] Checking file systems...fsck from util-linux 2.25.2
done.
[ ok ] Loading kernel modules...done.
[ ok ] Cleaning up temporary files... /tmp.
[ ok ] Mounting local filesystems...done.
[ ok ] Activating swapfile swap...done.
[ ok ] Cleaning up temporary files....
[ ok ] Setting kernel variables ...done.
[ 18.305807] NET: Registered protocol family 10
[ 18.396032] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/b6:d0:5e:0f:a1:17
Sending on LPF/eth0/b6:d0:5e:0f:a1:17
Sending on Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67
send_packet: Network is down
dhclient.c:2255: Failed to send 300 byte long packet over eth1 interface.
receive_packet failed on eth1: Network is down
DHCPREQUEST on eth1 to 255.255.255.255 port 67
send_packet: Network is down
dhclient.c:2255: Failed to send 300 byte long packet over eth1 interface.
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
send_packet: Network is down
dhclient.c:1966: Failed to send 300 byte long packet over eth1 interface.
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
send_packet: Network is down
dhclient.c:1966: Failed to send 300 byte long packet over eth1 interface.
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
send_packet: Network is down
dhclient.c:1966: Failed to send 300 byte long packet over eth1 interface.
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 19
send_packet: Network is down
dhclient.c:1966: Failed to send 300 byte long packet over eth1 interface.
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
send_packet: Network is down
dhclient.c:1966: Failed to send 300 byte long packet over eth1 interface.
No DHCPOFFERS received.
Trying recorded lease 192.168.0.154
connect: Network is unreachable
bound: renewal in 808 seconds.
grep: /etc/resolv.conf: No such file or directory
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
Failed to bring up wlan1.
done.
[ ok ] Starting rpcbind daemon....
[ ok ] Starting NFS common utilities: statd idmapd.
[ ok ] Cleaning up temporary files....
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
[....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd...
1302 (syslogd)
. ok
[....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd...
1305 (klogd)
. ok
[ ok ] Starting system message bus: dbus.
[ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
[ ok ] Starting NFS common utilities: statd idmapd.
[ ok ] Starting NTP server: ntpd.
[warn] Not starting NFS kernel daemon: no exports. ... (warning).
[ ok ] Starting OpenBSD Secure Shell server: sshd.
Debian GNU/Linux 8 debian ttyS0
debian login:
|
Re: Linksys EA4500 / EA4200 support March 25, 2016 01:38AM |
Registered: 10 years ago Posts: 82 |
lsmod and ifconfig -a with dockstar u-boot:
With stock u-boot:
root@debian:~# lsmod
Module Size Used by
cfg80211 403331 0
rfkill 15810 1 cfg80211
ipv6 313462 38
evdev 10805 0
orion_wdt 6105 0
kirkwood_thermal 1886 0
marvell_cesa 24992 0
des_generic 16866 1 marvell_cesa
gpio_keys 7743 0
uio_pdrv_genirq 2946 0
uio 7231 1 uio_pdrv_genirq
ext2 55958 1
sg 22041 0
sd_mod 29877 2
uas 12147 0
usb_storage 42753 2 uas
scsi_mod 174199 4 sg,uas,usb_storage,sd_mod
root@debian:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr b6:d0:5e:0f:a1:17
inet6 addr: fe80::b4d0:5eff:fe0f:a117/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:6737 (6.5 KiB)
Interrupt:83
eth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
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:84
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:376 (376.0 B) TX bytes:376 (376.0 B)
root@debian:~#
With stock u-boot:
root@debian:~# lsmod
Module Size Used by
ccm 7685 2
ipv6 313462 48
arc4 1689 4
evdev 10805 0
mwl8k 41524 0
mac80211 500049 1 mwl8k
orion_wdt 6105 0
cfg80211 403331 2 mwl8k,mac80211
rfkill 15810 2 cfg80211
kirkwood_thermal 1886 0
marvell_cesa 24992 0
des_generic 16866 1 marvell_cesa
gpio_keys 7743 0
uio_pdrv_genirq 2946 0
uio 7231 1 uio_pdrv_genirq
ext2 55958 1
sg 22041 0
sd_mod 29877 2
uas 12147 0
usb_storage 42753 2 uas
scsi_mod 174199 4 sg,uas,usb_storage,sd_mod
root@debian:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr 20:aa:4b:e5:d2:cf
inet addr:192.168.0.153 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::22aa:4bff:fee5:d2cf/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:31 errors:0 dropped:0 overruns:0 frame:0
TX packets:105 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3001 (2.9 KiB) TX bytes:11849 (11.5 KiB)
Interrupt:85
eth1 Link encap:Ethernet HWaddr 20:aa:4b:e5:d2:d0
inet addr:192.168.0.154 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::22aa:4bff:fee5:d2d0/64 Scope:Link
inet6 addr: fde1:cf10:3af6:0:22aa:4bff:fee5:d2d0/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:106 errors:0 dropped:0 overruns:0 frame:0
TX packets:53 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13172 (12.8 KiB) TX bytes:8779 (8.5 KiB)
Interrupt:86
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:58 errors:0 dropped:0 overruns:0 frame:0
TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5896 (5.7 KiB) TX bytes:5896 (5.7 KiB)
wlan0 Link encap:Ethernet HWaddr 20:aa:4b:e5:d2:d3
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)
wlan1 Link encap:Ethernet HWaddr 20:aa:4b:e5:d2:d1
inet addr:192.168.0.155 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::22aa:4bff:fee5:d2d1/64 Scope:Link
inet6 addr: fde1:cf10:3af6:0:22aa:4bff:fee5:d2d1/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:101 errors:0 dropped:0 overruns:0 frame:0
TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11921 (11.6 KiB) TX bytes:8764 (8.5 KiB)
root@debian:~#
|
Re: Linksys EA4500 / EA4200 support March 25, 2016 02:10AM |
Admin Registered: 13 years ago Posts: 18,545 |
megal0maniac,
> The device boots with the Dockstar u-boot
This is excellent! Meaning we have a recovery path already. And we are on the right track, the Dockstar u-boot is close enough to be a base. This u-boot has enable booting into Debian.
> but the
> network interfaces don't come up (wired or
> wireless)
> I don't even get link lights so it seems like
> hardware initialisation failure.
> There is a cable connected to what should be
> eth0.
This is expected, since you have not set the envs correctly yet. Currently it is the default set of envs internal to the Dockstar, so it will not be correct.
Go ahead and set the ethaddr envs before executing boot:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> The device boots with the Dockstar u-boot
This is excellent! Meaning we have a recovery path already. And we are on the right track, the Dockstar u-boot is close enough to be a base. This u-boot has enable booting into Debian.
> but the
> network interfaces don't come up (wired or
> wireless)
> I don't even get link lights so it seems like
> hardware initialisation failure.
> There is a cable connected to what should be
> eth0.
This is expected, since you have not set the envs correctly yet. Currently it is the default set of envs internal to the Dockstar, so it will not be correct.
Go ahead and set the ethaddr envs before executing boot:
setenv ethaddr '20:AA:4B:E5:D2:CF' setenv eth1addr '20:AA:4B:E5:D2:D0'
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Linksys EA4500 / EA4200 support March 25, 2016 02:29AM |
Admin Registered: 13 years ago Posts: 18,545 |
And we should find out which chip is used in this box for the 4 Gigabit ports. I hope it is the Marvell DSA chip. You could open the box and take a picture of that chip.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Linksys EA4500 / EA4200 support March 25, 2016 02:31AM |
Registered: 10 years ago Posts: 82 |
Setting the ethaddr doesn't make any difference. I suspect that it is an issue with the switch, as all the external ports are connected via the switch.
Internally it is a 7 port switch with 0 - 4 external and 5 - 6 internal.
VLAN 1: 0, 1, 2, 3, 5 (LAN)
VLAN2: 4, 6 (WAN)
From the OpenWRT bootlog:
From teardowns, it is identified as a MV88E6171R (careful inspection confirms: http://www.vbye.com/bbs/attachment/Mon_1204/51_2_5acaeed64b4c0e8.jpg)
Edited 1 time(s). Last edit at 03/25/2016 02:38AM by megal0maniac.
Internally it is a 7 port switch with 0 - 4 external and 5 - 6 internal.
VLAN 1: 0, 1, 2, 3, 5 (LAN)
VLAN2: 4, 6 (WAN)
From the OpenWRT bootlog:
mvsw61xx 10.mvsw61xx: Found MV88E6171 at f1072004.mdio-bu:10
From teardowns, it is identified as a MV88E6171R (careful inspection confirms: http://www.vbye.com/bbs/attachment/Mon_1204/51_2_5acaeed64b4c0e8.jpg)
Edited 1 time(s). Last edit at 03/25/2016 02:38AM by megal0maniac.
|
Re: Linksys EA4500 / EA4200 support March 25, 2016 02:38AM |
Admin Registered: 13 years ago Posts: 18,545 |
megal0maniac Wrote:
-------------------------------------------------------
> Setting the ethaddr doesn't make any difference. I
> suspect that it is an issue with the switch, as
> all the external ports are connected via the
> switch.
> Internally it is a 7 port switch with 0 - 4
> external and 5 - 6 internal.
> VLAN 1: 0, 1, 2, 3, 5 (LAN)
> VLAN2: 4, 6 (WAN)
Sometime it take a long time to get a lease with DHCP when you're changing MAC address. You should use static IP and see if it comes up quicker.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Setting the ethaddr doesn't make any difference. I
> suspect that it is an issue with the switch, as
> all the external ports are connected via the
> switch.
> Internally it is a 7 port switch with 0 - 4
> external and 5 - 6 internal.
> VLAN 1: 0, 1, 2, 3, 5 (LAN)
> VLAN2: 4, 6 (WAN)
Sometime it take a long time to get a lease with DHCP when you're changing MAC address. You should use static IP and see if it comes up quicker.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Linksys EA4500 / EA4200 support March 25, 2016 02:41AM |
Registered: 10 years ago Posts: 82 |
|
Re: Linksys EA4500 / EA4200 support March 25, 2016 02:49AM |
Admin Registered: 13 years ago Posts: 18,545 |
megal0maniac Wrote:
-------------------------------------------------------
> Sorry, I edited that post with more information.
> By "doesn't come up" I mean there is no link
> whatsoever, at any point, when using the
> Dockstar's u-boot.
> My switch doesn't detect that there's a device on
> the other end of the cable.
Looks like it did come up:
But the MAC addresses were wrong. The first one is the default local MAC from the Dockstar u-boot, the 2nd one is missing.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Sorry, I edited that post with more information.
> By "doesn't come up" I mean there is no link
> whatsoever, at any point, when using the
> Dockstar's u-boot.
> My switch doesn't detect that there's a device on
> the other end of the cable.
Looks like it did come up:
[ 1.846430] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [ 1.854759] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address b6:d0:5e:0f:a1:17 [ 1.864224] mv643xx_eth_port mv643xx_eth_port.1 eth1: port 0 with MAC address 00:00:00:00:00:00 [ 18.305807] NET: Registered protocol family 10 [ 18.396032] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
But the MAC addresses were wrong. The first one is the default local MAC from the Dockstar u-boot, the 2nd one is missing.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
