bodhi, I just restored the latest u-boot to the box and booting with usb wifi adapter. It doesn't hurt to have a couple USB Ethernet adapter on hand, so I'll pick up a couple cheap ones later. Thanks again.by fortis91 - Debian
bodi, I can use your u-boot with a with a USB wifi adapter, or if it's not too much I could try the env setup on stock u-boot to boot Debian. I wouldn't want to take too much more of your time on this, I'm sure you have other boxes you want to get to. Thanks again for all your help.by fortis91 - Debian
No luck with kwboot vm-ubuntu-server:~/kwboot-tool$ sudo ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.t5325.mtd0.kwb -p Sending boot message. Please reboot the target...\ Sending boot image... 0 % [......................................................................] 1 % [......................................................................] 3 % [...............by fortis91 - Debian
bodi, Got good results from u-boot: HP>> ping 192.168.1.1 Using egiga0 device ## Warning: gatewayip needed but not set ping failed; host 192.168.1.1 is not alive HP>> setenv netmask 255.255.255.0 HP>> setenv gatewayip 192.168.1.1 HP>> dhcp BOOTP broadcast 1 *** Unhandled DHCP Option in OFFER/ACK: 28 *** Unhandled DHCP Option in OFFER/ACK: 28 DHCP client bouby fortis91 - Debian
Went ahead and flash mtd0 and mtd3, still unable to get IP. Booting back into stock, I seem to lost logging on the console _ _ .____ | |_| | | _ \ | _ | | (_)) | |-| | | | |_| |_| |_| .. _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_)by fortis91 - Debian
Hi bodhi, I'm not sure if I can boot back to stock without flashing back to original uboot. I tried doing as you suggest but got error on the unlock. root@debian:~# flash_unlock /dev/mtd0 flash_unlock: error!: could not unlock device: /dev/mtd0 error 95 (Operation not supported) root@debian:~# flash_unlock /dev/mtd3 flash_unlock: error!: could not unlock device:by fortis91 - Debian
Hi Guy, Here you go: root@debian:~/mtd-backup# cat /proc/mtd dev: size erasesize name mtd0: 00080000 00001000 "u-boot" mtd1: 00040000 00001000 "SSD firmware" mtd2: 00010000 00001000 "u-boot env" mtd3: 00010000 00001000 "permanent u-boot env" root@debian:~/mtd-backup# dd if=/dev/mtd0 of=mtd0.t5325.u-boot bs=512k conv=sync 1+0 records inby fortis91 - Debian
Koen, I'm not sure if you want to use mine, otherwise I don't mind sharing. If so, post the commands you want me to use to do the backup and I'll do it later today.by fortis91 - Debian
I'll add mine here too... T5325> mii info PHY 0x08: OUI = 0x5043, Model = 0x22, Rev = 0x00, 100baseT, FDX T5325> mii dump 8 0 0. (3100) -- PHY control register -- (8000:0000) 0.15 = 0 reset (4000:0000) 0.14 = 0 loopback (2040:2000) 0. 6,13 = b01 speed selection = 100 Mbps (1000:1000) 0.12 = 1 A/N enable (by fortis91 - Debian
Koen, Hope you can recover your box. I'm not having much success here either. My only other option now is to try and flash uBoot gain. bodhi, Is there anything in uBoot where the box would be trying to get an IP from 192.168.01 instead of 192.168.1.1? root@debian:~# ifdown eth0 Killed old client process Internet Systems Consortium DHCP Client 4.3.1 Copyright 2004-2014 Interneby fortis91 - Debian
bodhi, I believe I have IPv6 disabled now, unfortunately I still can't get a connection. root@debian:~# ifdown eth0 root@debian:~# ifup eth0 [ 107.822647] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled root@debian:~# dmesg -T | tail -20 pci 0000:00:01.0: enabling bus mastering xgifb 0000:01:00.0: enabling device (0140 -> 014by fortis91 - Debian
bodhi Wrote: ------------------------------------------------------- > fortis, > Try ifdown/ifup again. Didn't seem to help, I even disabled IPv6 on my router's lan side. root@debian:~# ifdown eth0 root@debian:~# ifup eth0 [ 156.105361] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 157.693952] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, fullby fortis91 - Debian
Disabling IPv6 didn't seem to have any effect: root@debian:~# cat /etc/sysctl.d/local.conf net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.lo.disable_ipv6 = 1 Did both sysctl --system and rebooted box root@debian:~# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. From 192.168.1.22 icmp_seq=1 Destination Host Unreachaby fortis91 - Debian
uBoot U-Boot 2017.07-tld-1 (Nov 01 2017 - 00:58:19 -0700) HP Thin Client T5325 SoC: Kirkwood 88F6281_A1 SPI: ready DRAM: 512 MiB WARNING: Caches not enabled MMC: SF: Detected sst25vf080b with page size 256 Bytes, erase size 64 KiB, total 1 MiB In: serial Out: serial Err: serial Net: egiga0 88E3016 Initialized on egiga0 Hit any key to stop autoboot: 0 T5325>by fortis91 - Debian
Gave static IP a try without success, while the IP is set it just doesn't seem to be getting a connection to the router. U-Boot 2017.07-tld-1 (Nov 01 2017 - 00:58:19 -0700) HP Thin Client T5325 SoC: Kirkwood 88F6281_A1 SPI: ready DRAM: 512 MiB WARNING: Caches not enabled MMC: SF: Detected sst25vf080b with page size 256 Bytes, erase size 64 KiB, total 1 MiB In: serialby fortis91 - Debian
I'm also running Openwrt, maybe it's just coincidence. I tried a stock router with the same result. Koen Wrote: ------------------------------------------------------- > I'm running openwrt on my router and there are > some messages in the kernel log and system log: > > Koenby fortis91 - Debian
In this case I'm using a CAT 5e connected to a Gigabit router. Here is the same cable, connected to a Dockstar on the same router port: debian-dockstar:~$ sudo ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.132 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fdd2:7368:e358:0:210:75ff:fe1a:877 prefixlen 64 scopeid 0x0<by fortis91 - Debian
bodhi, Here you go: root@debian:~# ifconfig -a eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::503b:20ff:fe9c:1151 prefixlen 64 scopeid 0x20<link> ether 52:3b:20:9c:11:51 txqueuelen 1000 (Ethernet) RX packets 449 bytes 29261 (28.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 24 bytes 4344 (by fortis91 - Debian
U-Boot 2017.07-tld-1 (Nov 01 2017 - 00:58:19 -0700) HP Thin Client T5325 SoC: Kirkwood 88F6281_A1 SPI: ready DRAM: 512 MiB WARNING: Caches not enabled MMC: SF: Detected sst25vf080b with page size 256 Bytes, erase size 64 KiB, total 1 MiB In: serial Out: serial Err: serial Net: egiga0 88E3016 Initialized on egiga0 Hit any key to stop autoboot: 0 T5325> setenby fortis91 - Debian
bodhi, Just to confirm it's ok to save: T5325> setenv ethaddr '52:3b:20:9c:11:51' Warning: egiga0 MAC addresses don't match: Address in SROM is 52:3b:20:9c:11:51 Address in environment is f4:ce:xx:xx:xx:xx Yes, I edited original MAC.by fortis91 - Debian
bodhi, If you can verify my MTD flash definition is good, I don't mind doing the installation again. root@debian:~# cat /proc/mtd dev: size erasesize name mtd0: 00080000 00001000 "uboot" mtd1: 00040000 00001000 "sdd_firmware" mtd2: 00010000 00001000 "uboot_env" mtd3: 00010000 00001000 "permanent_uboot_env" mtd4: 00010000 00001000 &quby fortis91 - Debian
bodhi Wrote: ------------------------------------------------------- > All, > > I was able to create a failure case with my box! > > Please try these 2 test to see my assumption is > correct. > > Test 1 > > Unplug the power cord. > Wait for a while, at least 10 seconds. > Power up, interrupt serial console > Ping the router 5 times >by fortis91 - Debian
bodhi Wrote: ------------------------------------------------------- bodhi, sorry for any confusion. It is both not working. > fortis, > > > > I only flashed these: > > > > uboot.2017.07-tld-1.t5325.bodhi.tar > > uboot.2016.05-tld-1.environment.bodhi.tar > > > > > > Networking was working fine with those. > > Let me makby fortis91 - Debian
root@debian:/etc# cat /etc/resolv.conf nameserver 8.8.8.8by fortis91 - Debian
kwboot tmp# kwboot -t -B 115200 /dev/ttyUSB1 -b uboot.2016.05-tld-1.t5325.mtd0.kwb -p Sending boot message. Please reboot the target...- Sending boot image... 0 % [......................................................................] 1 % [......................................................................] 3 % [................................................................by fortis91 - Debian
bodhi, I only flashed these: uboot.2017.07-tld-1.t5325.bodhi.tar uboot.2016.05-tld-1.environment.bodhi.tar Networking was working fine with those.by fortis91 - Debian
bodhi Wrote: ------------------------------------------------------- > All, > > I wonder if there is a different network chip in > your boxes? > > @fortis, > Yes, edited for privacy. > I want to make sure, was it blanked out for > privacy? > > ethaddr=f4:ce:xx:xx:xx:xx >by fortis91 - Debian
Thanks Koen. edit.... Bodhi, let me know if you need me to run any commands. Here is the rest of my info: mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3 jffs2: version 2.2. (NAND) (SUMMARY) \xffffffc2\xffffffa9 2001-2006 Red Hat, Inc. m25p80 spi0.0: found sst25vf080b, expected m25p80 root@debian:~# cat /proc/mtd dev: size erasesize name mtd0: 00080000 00001000 "uboot"by fortis91 - Debian
I'll compare to my boot log later. Thanksby fortis91 - Debian