HP 5325 ethernet stopped working
Posted by Koen
|
Re: HP 5325 ethernet stopped working November 02, 2018 06:26PM |
Admin Registered: 12 years ago Posts: 17,933 |
When it was disabled
So my system, as long as the clock is close to correct (not messed up too bad), the connection is insant.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/02/2018 06:27PM by bodhi.
[Fri Nov 2 16:23:36 2018] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled [Fri Nov 2 16:23:36 2018] NET: Registered protocol family 10 [Fri Nov 2 16:23:36 2018] Segment Routing with IPv6 [Fri Nov 2 16:23:39 2018] NET: Registered protocol family 15
So my system, as long as the clock is close to correct (not messed up too bad), the connection is insant.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/02/2018 06:27PM by bodhi.
|
Re: HP 5325 ethernet stopped working November 02, 2018 07:16PM |
Registered: 6 years ago Posts: 57 |
bodhi,
I believe I have IPv6 disabled now, unfortunately I still can't get a connection.
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 [Fri Nov 2 17:11:09 2018] pci 0000:00:01.0: enabling bus mastering [Fri Nov 2 17:11:09 2018] xgifb 0000:01:00.0: enabling device (0140 -> 0143) [Fri Nov 2 17:11:09 2018] xgifb 0000:01:00.0: chipid = 32 [Fri Nov 2 17:11:09 2018] xgifb: SR14=51 DramSzie 2000000 ChannelNum 1 [Fri Nov 2 17:11:09 2018] marvell-cesa f1030000.crypto: CESA device successfully registered [Fri Nov 2 17:11:09 2018] orion_wdt: Initial timeout 21 sec [Fri Nov 2 17:11:10 2018] xgifb 0000:01:00.0: Framebuffer at 0xe0000000, mapped to 0xe1000000, size 32768k [Fri Nov 2 17:11:10 2018] sd 0:0:0:0: Attached scsi generic sg0 type 0 [Fri Nov 2 17:11:10 2018] sd 2:0:0:0: Attached scsi generic sg1 type 0 [Fri Nov 2 17:11:10 2018] xgifb 0000:01:00.0: MMIO at 0xe4000000, mapped to 0xe0f40000, size 256k [Fri Nov 2 17:11:10 2018] asoc-simple-card sound: alc5621-hifi <-> i2s mapping ok [Fri Nov 2 17:11:10 2018] xgifb 0000:01:00.0: No or unknown bridge type detected [Fri Nov 2 17:11:10 2018] xgifb: Default mode is 800x600x16 (60Hz) [Fri Nov 2 17:11:10 2018] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled [Fri Nov 2 17:11:10 2018] random: crng init done [Fri Nov 2 17:11:11 2018] NET: Registered protocol family 10 [Fri Nov 2 17:11:11 2018] Segment Routing with IPv6 [Fri Nov 2 17:11:11 2018] EXT4-fs (sdb1): re-mounted. Opts: (null) [Fri Nov 2 17:11:12 2018] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro [Fri Nov 2 17:12:35 2018] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled
|
Re: HP 5325 ethernet stopped working November 02, 2018 08:02PM |
Admin Registered: 12 years ago Posts: 17,933 |
fortis,
What do you see the router does when this occured?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
What do you see the router does when this occured?
[Fri Nov 2 17:12:35 2018] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: HP 5325 ethernet stopped working November 03, 2018 10:36AM |
Registered: 5 years ago Posts: 180 |
Switching off ipv6 didn't make a difference. So I decided to try to go back to stock which was a mistake.
mtd layout in Debian:
backed up original partitions:
t5325.mtd3 is the old uboot, t5325.mtd0 are the old envs. So I did the following to copy them over the current uboot and envs:
Which resulted in a brick, even serial doesn't give any output.
The flash in my device is mx25l8005 which is supported by flashrom. So I'll try to access it using my raspberry pi. If that works I may have an option to de-brick the unit but otherwise it is gone I presume.
Koen
mtd layout in Debian:
root@HP5325:/koen# cat /proc/mtd dev: size erasesize name mtd0: 00080000 00010000 "uboot" mtd1: 00040000 00010000 "sdd_firmware" mtd2: 00010000 00010000 "uboot_env" mtd3: 00010000 00010000 "permanent_uboot_env" mtd4: 00010000 00010000 "hp_env" root@HP5325:/koen#
backed up original partitions:
root@HP5325:/koen# ll total 1312 drwxr-xr-x 2 root root 4096 Oct 30 22:39 . drwxr-xr-x 22 root root 4096 Sep 6 2033 .. -rw-r--r-- 1 root root 65536 Oct 30 22:39 t5325.mtd0 -rw-r--r-- 1 root root 524288 Oct 30 22:39 t5325.mtd3
t5325.mtd3 is the old uboot, t5325.mtd0 are the old envs. So I did the following to copy them over the current uboot and envs:
root@HP5325:/koen# dd if=t5325.mtd3 of=/dev/mtd0 bs=512k conv=sync 1+0 records in 1+0 records out 524288 bytes (524 kB, 512 KiB) copied, 1.64804 s, 318 kB/s root@HP5325:/koen# dd if=t5325.mtd0 of=/dev/mtd2 bs=64k conv=sync 1+0 records in 1+0 records out 65536 bytes (66 kB, 64 KiB) copied, 0.133128 s, 492 kB/s root@HP5325:/koen# reboot
Which resulted in a brick, even serial doesn't give any output.
The flash in my device is mx25l8005 which is supported by flashrom. So I'll try to access it using my raspberry pi. If that works I may have an option to de-brick the unit but otherwise it is gone I presume.
Koen
|
Re: HP 5325 ethernet stopped working November 03, 2018 11:40AM |
Registered: 6 years ago Posts: 57 |
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?
Playing around with dhcpdump, it seems to be requesting IP 192.168.0.16, from I assume 192.168.0.1
.
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 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/52:3b:20:9c:11:51 Sending on LPF/eth0/52:3b:20:9c:11:51 Sending on Socket/fallback DHCPRELEASE on eth0 to 192.168.0.1 port 67 root@debian:~# ifup eth0 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/52:3b:20:9c:11:51 Sending on LPF/eth0/52:3b:20:9c:11:51 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 12 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 No DHCPOFFERS received. No working leases in persistent database - sleeping.
Playing around with dhcpdump, it seems to be requesting IP 192.168.0.16, from I assume 192.168.0.1
.
root@debian:~# dhcpdump -i eth0[ 4310.502145] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 4312.001253] device eth0 entered promiscuous mode
[ 4312.092969] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled
[ 4312.102843] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
TIME: 2018-11-03 11:32:17.848
IP: 0.0.0.0 (52:3b:20:9c:11:51) > 255.255.255.255 (ff:ff:ff:ff:ff:ff)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 0
XID: 80f12a17
SECS: 3
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: 52:3b:20:9c:11:51:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 1 (DHCPDISCOVER)
OPTION: 12 ( 6) Host name debian
OPTION: 55 ( 12) Parameter Request List 1 (Subnet mask)
28 (Broadcast address)
2 (Time offset)
3 (Routers)
15 (Domainname)
6 (DNS server)
119 (Domain Search)
12 (Host name)
44 (NetBIOS name server)
47 (NetBIOS scope)
26 (Interface MTU)
42 (NTP servers)
---------------------------------------------------------------------------
TIME: 2018-11-03 11:32:19.248
IP: 0.0.0.0 (52:3b:20:9c:11:51) > 255.255.255.255 (ff:ff:ff:ff:ff:ff)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 0
XID: 813d6664
SECS: 5
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: 52:3b:20:9c:11:51:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 1 (DHCPDISCOVER)
OPTION: 50 ( 4) Request IP address 192.168.0.16
OPTION: 12 ( 6) Host name debian
OPTION: 55 ( 12) Parameter Request List 1 (Subnet mask)
28 (Broadcast address)
2 (Time offset)
3 (Routers)
15 (Domainname)
6 (DNS server)
119 (Domain Search)
12 (Host name)
44 (NetBIOS name server)
47 (NetBIOS scope)
26 (Interface MTU)
42 (NTP servers)
---------------------------------------------------------------------------
TIME: 2018-11-03 11:32:22.248
IP: 0.0.0.0 (52:3b:20:9c:11:51) > 255.255.255.255 (ff:ff:ff:ff:ff:ff)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 0
XID: 80f12a17
SECS: 8
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: 52:3b:20:9c:11:51:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 1 (DHCPDISCOVER)
OPTION: 12 ( 6) Host name debian
OPTION: 55 ( 12) Parameter Request List 1 (Subnet mask)
28 (Broadcast address)
2 (Time offset)
3 (Routers)
15 (Domainname)
6 (DNS server)
119 (Domain Search)
12 (Host name)
44 (NetBIOS name server)
47 (NetBIOS scope)
26 (Interface MTU)
42 (NTP servers)
---------------------------------------------------------------------------
TIME: 2018-11-03 11:32:23.548
IP: 0.0.0.0 (52:3b:20:9c:11:51) > 255.255.255.255 (ff:ff:ff:ff:ff:ff)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 0
XID: 889a4509
SECS: 30
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: 52:3b:20:9c:11:51:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 1 (DHCPDISCOVER)
OPTION: 12 ( 6) Host name debian
OPTION: 55 ( 12) Parameter Request List 1 (Subnet mask)
28 (Broadcast address)
2 (Time offset)
3 (Routers)
15 (Domainname)
6 (DNS server)
119 (Domain Search)
12 (Host name)
44 (NetBIOS name server)
47 (NetBIOS scope)
26 (Interface MTU)
42 (NTP servers)
---------------------------------------------------------------------------
TIME: 2018-11-03 11:32:30.148
IP: 0.0.0.0 (52:3b:20:9c:11:51) > 255.255.255.255 (ff:ff:ff:ff:ff:ff)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 0
XID: 889a4509
SECS: 37
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: 52:3b:20:9c:11:51:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 1 (DHCPDISCOVER)
OPTION: 12 ( 6) Host name debian
OPTION: 55 ( 12) Parameter Request List 1 (Subnet mask)
28 (Broadcast address)
2 (Time offset)
3 (Routers)
15 (Domainname)
6 (DNS server)
119 (Domain Search)
12 (Host name)
44 (NetBIOS name server)
47 (NetBIOS scope)
26 (Interface MTU)
42 (NTP servers)
---------------------------------------------------------------------------
TIME: 2018-11-03 11:32:30.748
IP: 0.0.0.0 (52:3b:20:9c:11:51) > 255.255.255.255 (ff:ff:ff:ff:ff:ff)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 0
XID: 813d6664
SECS: 16
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: 52:3b:20:9c:11:51:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 1 (DHCPDISCOVER)
OPTION: 50 ( 4) Request IP address 192.168.0.16
OPTION: 12 ( 6) Host name debian
OPTION: 55 ( 12) Parameter Request List 1 (Subnet mask)
28 (Broadcast address)
2 (Time offset)
3 (Routers)
15 (Domainname)
6 (DNS server)
119 (Domain Search)
12 (Host name)
44 (NetBIOS name server)
47 (NetBIOS scope)
26 (Interface MTU)
42 (NTP servers)
---------------------------------------------------------------------------
TIME: 2018-11-03 11:32:36.348
IP: 0.0.0.0 (52:3b:20:9c:11:51) > 255.255.255.255 (ff:ff:ff:ff:ff:ff)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 0
XID: 80f12a17
SECS: 22
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: 52:3b:20:9c:11:51:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 1 (DHCPDISCOVER)
OPTION: 12 ( 6) Host name debian
OPTION: 55 ( 12) Parameter Request List 1 (Subnet mask)
28 (Broadcast address)
2 (Time offset)
3 (Routers)
15 (Domainname)
6 (DNS server)
119 (Domain Search)
12 (Host name)
44 (NetBIOS name server)
47 (NetBIOS scope)
26 (Interface MTU)
42 (NTP servers)
---------------------------------------------------------------------------
TIME: 2018-11-03 11:32:39.648
IP: 0.0.0.0 (52:3b:20:9c:11:51) > 255.255.255.255 (ff:ff:ff:ff:ff:ff)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 0
XID: 813d6664
SECS: 25
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: 52:3b:20:9c:11:51:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 1 (DHCPDISCOVER)
OPTION: 50 ( 4) Request IP address 192.168.0.16
OPTION: 12 ( 6) Host name debian
OPTION: 55 ( 12) Parameter Request List 1 (Subnet mask)
28 (Broadcast address)
2 (Time offset)
3 (Routers)
15 (Domainname)
6 (DNS server)
119 (Domain Search)
12 (Host name)
44 (NetBIOS name server)
47 (NetBIOS scope)
26 (Interface MTU)
42 (NTP servers)
---------------------------------------------------------------------------
TIME: 2018-11-03 11:32:48.348
IP: 0.0.0.0 (52:3b:20:9c:11:51) > 255.255.255.255 (ff:ff:ff:ff:ff:ff)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 0
XID: 80f12a17
SECS: 34
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: 52:3b:20:9c:11:51:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 1 (DHCPDISCOVER)
OPTION: 12 ( 6) Host name debian
OPTION: 55 ( 12) Parameter Request List 1 (Subnet mask)
28 (Broadcast address)
2 (Time offset)
3 (Routers)
15 (Domainname)
6 (DNS server)
119 (Domain Search)
12 (Host name)
44 (NetBIOS name server)
47 (NetBIOS scope)
26 (Interface MTU)
42 (NTP servers)
---------------------------------------------------------------------------
TIME: 2018-11-03 11:32:50.648
IP: 0.0.0.0 (52:3b:20:9c:11:51) > 255.255.255.255 (ff:ff:ff:ff:ff:ff)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 0
XID: 889a4509
SECS: 57
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: 52:3b:20:9c:11:51:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 1 (DHCPDISCOVER)
OPTION: 12 ( 6) Host name debian
OPTION: 55 ( 12) Parameter Request List 1 (Subnet mask)
28 (Broadcast address)
2 (Time offset)
3 (Routers)
15 (Domainname)
6 (DNS server)
119 (Domain Search)
12 (Host name)
44 (NetBIOS name server)
47 (NetBIOS scope)
26 (Interface MTU)
42 (NTP servers)
---------------------------------------------------------------------------
TIME: 2018-11-03 11:33:00.348
IP: 0.0.0.0 (52:3b:20:9c:11:51) > 255.255.255.255 (ff:ff:ff:ff:ff:ff)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 0
XID: 813d6664
SECS: 46
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: 52:3b:20:9c:11:51:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 1 (DHCPDISCOVER)
OPTION: 50 ( 4) Request IP address 192.168.0.16
OPTION: 12 ( 6) Host name debian
OPTION: 55 ( 12) Parameter Request List 1 (Subnet mask)
28 (Broadcast address)
2 (Time offset)
3 (Routers)
15 (Domainname)
6 (DNS server)
119 (Domain Search)
12 (Host name)
44 (NetBIOS name server)
47 (NetBIOS scope)
26 (Interface MTU)
42 (NTP servers)
---------------------------------------------------------------------------
TIME: 2018-11-03 11:33:06.748
IP: 0.0.0.0 (52:3b:20:9c:11:51) > 255.255.255.255 (ff:ff:ff:ff:ff:ff)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 0
XID: 80f12a17
SECS: 52
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: 52:3b:20:9c:11:51:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 1 (DHCPDISCOVER)
OPTION: 12 ( 6) Host name debian
OPTION: 55 ( 12) Parameter Request List 1 (Subnet mask)
28 (Broadcast address)
2 (Time offset)
3 (Routers)
15 (Domainname)
6 (DNS server)
119 (Domain Search)
12 (Host name)
44 (NetBIOS name server)
47 (NetBIOS scope)
26 (Interface MTU)
42 (NTP servers)
---------------------------------------------------------------------------
|
Re: HP 5325 ethernet stopped working November 03, 2018 01:35PM |
Registered: 5 years ago Posts: 180 |
OK I've managed to read the spi chip with flashrom following the instructions on this website:
https://www.rototron.info/recover-bricked-bios-using-flashrom-on-a-raspberry-pi/
(I didn't desolder the chip but used a 8 pin clip instead)
I then needed to create a file to write back to spi. I'm not sure if flashrom can write only certain sections of the spi chip so I decided to create a file with the same size as the file I just read. I did this by concatenating 2 hp t5325 kwboot files together. When I write this back to the spi chip on the device it shows an uboot prompt again. So it is not perfect yet but at least it is not a brick anymore however it still doesn't connect to the router.
Koen
Edited 1 time(s). Last edit at 11/03/2018 01:39PM by Koen.
https://www.rototron.info/recover-bricked-bios-using-flashrom-on-a-raspberry-pi/
(I didn't desolder the chip but used a 8 pin clip instead)
I then needed to create a file to write back to spi. I'm not sure if flashrom can write only certain sections of the spi chip so I decided to create a file with the same size as the file I just read. I did this by concatenating 2 hp t5325 kwboot files together. When I write this back to the spi chip on the device it shows an uboot prompt again. So it is not perfect yet but at least it is not a brick anymore however it still doesn't connect to the router.
T5325> ping 192.168.1.1 Using egiga0 device ARP Retry count exceeded; starting again ping failed; host 192.168.1.1 is not alive T5325>
Koen
Edited 1 time(s). Last edit at 11/03/2018 01:39PM by Koen.
|
Re: HP 5325 ethernet stopped working November 03, 2018 01:57PM |
Registered: 5 years ago Posts: 180 |
After setting up the environment variables I can boot back into Debian. However after messing up I can't go back to stock anymore since I don't have backups of all the original mtd partitions. So if someone is willing to share their "permanent u-boot env", "HP env" and "SSD firmware" mtd partitions that would be great.
Koen
Koen
|
Re: HP 5325 ethernet stopped working November 03, 2018 04:39PM |
Admin Registered: 12 years ago Posts: 17,933 |
Hi Koen,
That's the wrong way to restore. You need to use flashcp. As an example:
And
In this situation, you should use kwboot to boot the box, and then restore. It was not completely bricked. There is no need to use hardware tool to recover this box at all.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 11/03/2018 04:48PM by bodhi.
Quote
> t5325.mtd3 is the old uboot, t5325.mtd0 are the
> old envs. So I did the following to copy them over
> the current uboot and envs:
>
>> root@HP5325:/koen# dd if=t5325.mtd3 of=/dev/mtd0 > bs=512k conv=sync > 1+0 records in > 1+0 records out > 524288 bytes (524 kB, 512 KiB) copied, 1.64804 s, > 318 kB/s > root@HP5325:/koen# dd if=t5325.mtd0 of=/dev/mtd2 > bs=64k conv=sync > 1+0 records in > 1+0 records out > 65536 bytes (66 kB, 64 KiB) copied, 0.133128 s, > 492 kB/s > root@HP5325:/koen# reboot >>
That's the wrong way to restore. You need to use flashcp. As an example:
Quote
T5325 installation instruction
4. Flash u-boot to mtd3
cd /tmp/sdb1/boot
flash_unlock /dev/mtd3
flashcp -v uboot.2017.07-tld-1.t5325.mtd0.kwb /dev/mtd3
And
Quote
> Which resulted in a brick, even serial doesn't
> give any output.
In this situation, you should use kwboot to boot the box, and then restore. It was not completely bricked. There is no need to use hardware tool to recover this box at all.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 11/03/2018 04:48PM by bodhi.
|
Re: HP 5325 ethernet stopped working November 03, 2018 05:02PM |
Admin Registered: 12 years ago Posts: 17,933 |
fortis,
> 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?
Not that I know of. I think it must have been a default value in the ISC DHCP Client.
Your test is quite informative! so it gave me an idea for another 2 tests.
1. At u-boot serial console, set some additional envs to force the issue:
2. At u-boot serial console,
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/03/2018 05:40PM by 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?
Not that I know of. I think it must have been a default value in the ISC DHCP Client.
Your test is quite informative! so it gave me an idea for another 2 tests.
1. At u-boot serial console, set some additional envs to force the issue:
setenv netmask 255.255.255.0 setenv gatewayip 192.168.1.1 setenv ipaddr 192.168.1.22 setenv serverip 192.168.1.23 #### this should be the box where you have serial console converter running ping 192.168.1.1 #### try a few pings here
2. At u-boot serial console,
setenv netmask 255.255.255.0 setenv gatewayip 192.168.1.1 setenv ipaddr 192.168.1.22 setenv serverip 192.168.1.23 #### this should be the box where you have serial console converter running dhcp #### it will attemp to load boot image from 192.168.1.23
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/03/2018 05:40PM by bodhi.
|
Re: HP 5325 ethernet stopped working November 04, 2018 12:25AM |
Admin Registered: 12 years ago Posts: 17,933 |
> someone is willing to share their "permanent
> u-boot env", "HP env" and "SSD firmware" mtd
> partitions that would be great.
Let me see if I can find my mtds backup.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> u-boot env", "HP env" and "SSD firmware" mtd
> partitions that would be great.
Let me see if I can find my mtds backup.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: HP 5325 ethernet stopped working November 04, 2018 03:36PM |
Registered: 5 years ago Posts: 180 |
Hi bodhi,
when I run the ping test this is the output:
and the dhcp boot test results in this:
Koen
when I run the ping test this is the output:
T5325> ping 192.168.1.1 Using egiga0 device ARP Retry count exceeded; starting again ping failed; host 192.168.1.1 is not alive T5325>
and the dhcp boot test results in this:
T5325> dhcp BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 BOOTP broadcast 4 BOOTP broadcast 5 BOOTP broadcast 6 BOOTP broadcast 7 BOOTP broadcast 8 BOOTP broadcast 9 BOOTP broadcast 10 BOOTP broadcast 11 BOOTP broadcast 12 BOOTP broadcast 13 BOOTP broadcast 14 BOOTP broadcast 15 BOOTP broadcast 16 BOOTP broadcast 17 Retry time exceeded; starting again T5325>
Koen
|
Re: HP 5325 ethernet stopped working November 04, 2018 04:32PM |
Admin Registered: 12 years ago Posts: 17,933 |
Koen,
There is a mii command and a few subcommands in u-boot. At u-boot prompt
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
There is a mii command and a few subcommands in u-boot. At u-boot prompt
mii info
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: HP 5325 ethernet stopped working November 04, 2018 04:48PM |
Admin Registered: 12 years ago Posts: 17,933 |
Koen,
I think there are only 2 possibilities:
1. your box somehow has a different network chip (not likely though). U-Boot does not periodically monitor the link like the kernel does so we can't see if the link is really inactive.
or
2. Something in the configuration of router that bring the link down (as you reported previously).
There is a mii command in u-boot. At u-boot prompt, see if we can find out more info.
My test:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 11/04/2018 05:01PM by bodhi.
I think there are only 2 possibilities:
1. your box somehow has a different network chip (not likely though). U-Boot does not periodically monitor the link like the kernel does so we can't see if the link is really inactive.
or
2. Something in the configuration of router that bring the link down (as you reported previously).
There is a mii command in u-boot. At u-boot prompt, see if we can find out more info.
mii info
My test:
U-Boot 2017.07-tld-1 (Nov 01 2017 - 00:58:19 -0700) HP Thin Client T5325 T5325> mii info PHY 0x08: OUI = 0x5043, Model = 0x22, Rev = 0x00, 100baseT, FDX T5325> ping 192.168.0.1 Using egiga0 device host 192.168.0.1 is alive T5325>
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 11/04/2018 05:01PM by bodhi.
|
Re: HP 5325 ethernet stopped working November 04, 2018 05:05PM |
Admin Registered: 12 years ago Posts: 17,933 |
Here is the register dump for 0-5.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/04/2018 05:06PM by bodhi.
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 (0800:0000) 0.11 = 0 power-down (0400:0000) 0.10 = 0 isolate (0200:0000) 0. 9 = 0 restart A/N (0100:0100) 0. 8 = 1 duplex = full (0080:0000) 0. 7 = 0 collision test enable (003f:0000) 0. 5- 0 = 0 (reserved) T5325> mii dump 8 1 1. (78ed) -- PHY status register -- (8000:0000) 1.15 = 0 100BASE-T4 able (4000:4000) 1.14 = 1 100BASE-X full duplex able (2000:2000) 1.13 = 1 100BASE-X half duplex able (1000:1000) 1.12 = 1 10 Mbps full duplex able (0800:0800) 1.11 = 1 10 Mbps half duplex able (0400:0000) 1.10 = 0 100BASE-T2 full duplex able (0200:0000) 1. 9 = 0 100BASE-T2 half duplex able (0100:0000) 1. 8 = 0 extended status (0080:0080) 1. 7 = 1 (reserved) (0040:0040) 1. 6 = 1 MF preamble suppression (0020:0020) 1. 5 = 1 A/N complete (0010:0000) 1. 4 = 0 remote fault (0008:0008) 1. 3 = 1 A/N able (0004:0004) 1. 2 = 1 link status (0002:0000) 1. 1 = 0 jabber detect (0001:0001) 1. 0 = 1 extended capabilities T5325> mii dump 8 2 2. (0141) -- PHY ID 1 register -- (ffff:0141) 2.15- 0 = 321 OUI portion T5325> mii dump 8 3 3. (0e20) -- PHY ID 2 register -- (fc00:0c00) 3.15-10 = 3 OUI portion (03f0:0220) 3. 9- 4 = 34 manufacturer part number (000f:0000) 3. 3- 0 = 0 manufacturer rev. number T5325> mii dump 8 4 4. (01e1) -- Autonegotiation advertisement register -- (8000:0000) 4.15 = 0 next page able (4000:0000) 4.14 = 0 (reserved) (2000:0000) 4.13 = 0 remote fault (1000:0000) 4.12 = 0 (reserved) (0800:0000) 4.11 = 0 asymmetric pause (0400:0000) 4.10 = 0 pause enable (0200:0000) 4. 9 = 0 100BASE-T4 able (0100:0100) 4. 8 = 1 100BASE-TX full duplex able (0080:0080) 4. 7 = 1 100BASE-TX able (0040:0040) 4. 6 = 1 10BASE-T full duplex able (0020:0020) 4. 5 = 1 10BASE-T able (001f:0001) 4. 4- 0 = 1 selector = IEEE 802.3 T5325> mii dump 8 5 5. (c5e1) -- Autonegotiation partner abilities register -- (8000:8000) 5.15 = 1 next page able (4000:4000) 5.14 = 1 acknowledge (2000:0000) 5.13 = 0 remote fault (1000:0000) 5.12 = 0 (reserved) (0800:0000) 5.11 = 0 asymmetric pause able (0400:0400) 5.10 = 1 pause able (0200:0000) 5. 9 = 0 100BASE-T4 able (0100:0100) 5. 8 = 1 100BASE-X full duplex able (0080:0080) 5. 7 = 1 100BASE-TX able (0040:0040) 5. 6 = 1 10BASE-T full duplex able (0020:0020) 5. 5 = 1 10BASE-T able (001f:0001) 5. 4- 0 = 1 selector = IEEE 802.3
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/04/2018 05:06PM by bodhi.
|
Re: HP 5325 ethernet stopped working November 05, 2018 06:04AM |
Registered: 9 years ago Posts: 1,037 |
|
Re: HP 5325 ethernet stopped working November 05, 2018 07:01AM |
Admin Registered: 12 years ago Posts: 17,933 |
Gravelrash Wrote:
-------------------------------------------------------
> im favouring a hardware fault
I'm tend to think that too. But the chance of both Koen and fortis having the same bad batch of hardware is rare! so I can't say before seeing Koen's stock boot log. Will upload the stock mtds once I can get to it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/05/2018 07:01AM by bodhi.
-------------------------------------------------------
> im favouring a hardware fault
I'm tend to think that too. But the chance of both Koen and fortis having the same bad batch of hardware is rare! so I can't say before seeing Koen's stock boot log. Will upload the stock mtds once I can get to it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/05/2018 07:01AM by bodhi.
|
Re: HP 5325 ethernet stopped working November 05, 2018 06:11PM |
Registered: 5 years ago Posts: 180 |
Hi bodhi,
this is the same as yours:
And here the dump of 0 - 5. Looks similar but there are some differences in dump 5 as highlighted further down this post.
my device dump 5 lines:
bodhi's lines which differ:
Not sure if this is due to messing around with ethtool or actually different capabilities / errors within the chip?
Koen
this is the same as yours:
T5325> mii info PHY 0x08: OUI = 0x5043, Model = 0x22, Rev = 0x00, 100baseT, FDX
And here the dump of 0 - 5. Looks similar but there are some differences in dump 5 as highlighted further down this post.
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 (0800:0000) 0.11 = 0 power-down (0400:0000) 0.10 = 0 isolate (0200:0000) 0. 9 = 0 restart A/N (0100:0100) 0. 8 = 1 duplex = full (0080:0000) 0. 7 = 0 collision test enable (003f:0000) 0. 5- 0 = 0 (reserved) T5325> mii dump 8 1 1. (78ed) -- PHY status register -- (8000:0000) 1.15 = 0 100BASE-T4 able (4000:4000) 1.14 = 1 100BASE-X full duplex able (2000:2000) 1.13 = 1 100BASE-X half duplex able (1000:1000) 1.12 = 1 10 Mbps full duplex able (0800:0800) 1.11 = 1 10 Mbps half duplex able (0400:0000) 1.10 = 0 100BASE-T2 full duplex able (0200:0000) 1. 9 = 0 100BASE-T2 half duplex able (0100:0000) 1. 8 = 0 extended status (0080:0080) 1. 7 = 1 (reserved) (0040:0040) 1. 6 = 1 MF preamble suppression (0020:0020) 1. 5 = 1 A/N complete (0010:0000) 1. 4 = 0 remote fault (0008:0008) 1. 3 = 1 A/N able (0004:0004) 1. 2 = 1 link status (0002:0000) 1. 1 = 0 jabber detect (0001:0001) 1. 0 = 1 extended capabilities T5325> mii dump 8 2 2. (0141) -- PHY ID 1 register -- (ffff:0141) 2.15- 0 = 321 OUI portion T5325> mii dump 8 3 3. (0e20) -- PHY ID 2 register -- (fc00:0c00) 3.15-10 = 3 OUI portion (03f0:0220) 3. 9- 4 = 34 manufacturer part number (000f:0000) 3. 3- 0 = 0 manufacturer rev. number T5325> mii dump 8 4 4. (01e1) -- Autonegotiation advertisement register -- (8000:0000) 4.15 = 0 next page able (4000:0000) 4.14 = 0 (reserved) (2000:0000) 4.13 = 0 remote fault (1000:0000) 4.12 = 0 (reserved) (0800:0000) 4.11 = 0 asymmetric pause (0400:0000) 4.10 = 0 pause enable (0200:0000) 4. 9 = 0 100BASE-T4 able (0100:0100) 4. 8 = 1 100BASE-TX full duplex able (0080:0080) 4. 7 = 1 100BASE-TX able (0040:0040) 4. 6 = 1 10BASE-T full duplex able (0020:0020) 4. 5 = 1 10BASE-T able (001f:0001) 4. 4- 0 = 1 selector = IEEE 802.3 T5325> mii dump 8 5 5. (c1e1) -- Autonegotiation partner abilities register -- (8000:8000) 5.15 = 1 next page able (4000:4000) 5.14 = 1 acknowledge (2000:0000) 5.13 = 0 remote fault (1000:0000) 5.12 = 0 (reserved) (0800:0000) 5.11 = 0 asymmetric pause able (0400:0000) 5.10 = 0 pause able (0200:0000) 5. 9 = 0 100BASE-T4 able (0100:0100) 5. 8 = 1 100BASE-X full duplex able (0080:0080) 5. 7 = 1 100BASE-TX able (0040:0040) 5. 6 = 1 10BASE-T full duplex able (0020:0020) 5. 5 = 1 10BASE-T able (001f:0001) 5. 4- 0 = 1 selector = IEEE 802.3
my device dump 5 lines:
5. (c1e1) -- Autonegotiation partner abilities register -- (0400:0000) 5.10 = 0 pause able
bodhi's lines which differ:
5. (c5e1) -- Autonegotiation partner abilities register -- (0400:0400) 5.10 = 1 pause able
Not sure if this is due to messing around with ethtool or actually different capabilities / errors within the chip?
Koen
|
Re: HP 5325 ethernet stopped working November 05, 2018 06:39PM |
Registered: 6 years ago Posts: 57 |
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 (0800:0000) 0.11 = 0 power-down (0400:0000) 0.10 = 0 isolate (0200:0000) 0. 9 = 0 restart A/N (0100:0100) 0. 8 = 1 duplex = full (0080:0000) 0. 7 = 0 collision test enable (003f:0000) 0. 5- 0 = 0 (reserved) T5325> mii dump 8 1 1. (78ed) -- PHY status register -- (8000:0000) 1.15 = 0 100BASE-T4 able (4000:4000) 1.14 = 1 100BASE-X full duplex able (2000:2000) 1.13 = 1 100BASE-X half duplex able (1000:1000) 1.12 = 1 10 Mbps full duplex able (0800:0800) 1.11 = 1 10 Mbps half duplex able (0400:0000) 1.10 = 0 100BASE-T2 full duplex able (0200:0000) 1. 9 = 0 100BASE-T2 half duplex able (0100:0000) 1. 8 = 0 extended status (0080:0080) 1. 7 = 1 (reserved) (0040:0040) 1. 6 = 1 MF preamble suppression (0020:0020) 1. 5 = 1 A/N complete (0010:0000) 1. 4 = 0 remote fault (0008:0008) 1. 3 = 1 A/N able (0004:0004) 1. 2 = 1 link status (0002:0000) 1. 1 = 0 jabber detect (0001:0001) 1. 0 = 1 extended capabilities T5325> mii dump 8 2 2. (0141) -- PHY ID 1 register -- (ffff:0141) 2.15- 0 = 321 OUI portion T5325> mii dump 8 3 3. (0e20) -- PHY ID 2 register -- (fc00:0c00) 3.15-10 = 3 OUI portion (03f0:0220) 3. 9- 4 = 34 manufacturer part number (000f:0000) 3. 3- 0 = 0 manufacturer rev. number T5325> mii dump 8 4 4. (01e1) -- Autonegotiation advertisement register -- (8000:0000) 4.15 = 0 next page able (4000:0000) 4.14 = 0 (reserved) (2000:0000) 4.13 = 0 remote fault (1000:0000) 4.12 = 0 (reserved) (0800:0000) 4.11 = 0 asymmetric pause (0400:0000) 4.10 = 0 pause enable (0200:0000) 4. 9 = 0 100BASE-T4 able (0100:0100) 4. 8 = 1 100BASE-TX full duplex able (0080:0080) 4. 7 = 1 100BASE-TX able (0040:0040) 4. 6 = 1 10BASE-T full duplex able (0020:0020) 4. 5 = 1 10BASE-T able (001f:0001) 4. 4- 0 = 1 selector = IEEE 802.3 T5325> mii dump 8 5 5. (cde1) -- Autonegotiation partner abilities register -- (8000:8000) 5.15 = 1 next page able (4000:4000) 5.14 = 1 acknowledge (2000:0000) 5.13 = 0 remote fault (1000:0000) 5.12 = 0 (reserved) (0800:0800) 5.11 = 1 asymmetric pause able (0400:0400) 5.10 = 1 pause able (0200:0000) 5. 9 = 0 100BASE-T4 able (0100:0100) 5. 8 = 1 100BASE-X full duplex able (0080:0080) 5. 7 = 1 100BASE-TX able (0040:0040) 5. 6 = 1 10BASE-T full duplex able (0020:0020) 5. 5 = 1 10BASE-T able (001f:0001) 5. 4- 0 = 1 selector = IEEE 802.3
|
Re: HP 5325 ethernet stopped working November 05, 2018 09:15PM |
Admin Registered: 12 years ago Posts: 17,933 |
Koen,
> my device dump 5 lines:
>
>
> bodhi's lines which differ:
>
>
> Not sure if this is due to messing around with
> ethtool or actually different capabilities /
> errors within the chip?
>
That's flow control setting. I think that must have been from your playing with ethtool. My box has flow control turned on by u-boot by default. But it will be disabled by the kernel.
Now given everything else matches in the PHY dump, I'd blame hardware (from the cable to the switch), or configuration (from the switch to the router). Network chip difference is another matter that I'm not sure how we can verify that other than looking at the marking (which you already did).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/05/2018 09:16PM by bodhi.
> my device dump 5 lines:
>
>
> 5. (c1e1) -- Autonegotiation > partner abilities register -- > (0400:0000) 5.10 = 0 pause able >>
> bodhi's lines which differ:
>
>
> 5. (c5e1) -- Autonegotiation > partner abilities register -- > (0400:0400) 5.10 = 1 pause able >>
> Not sure if this is due to messing around with
> ethtool or actually different capabilities /
> errors within the chip?
>
That's flow control setting. I think that must have been from your playing with ethtool. My box has flow control turned on by u-boot by default. But it will be disabled by the kernel.
[ 19.205518] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled
Now given everything else matches in the PHY dump, I'd blame hardware (from the cable to the switch), or configuration (from the switch to the router). Network chip difference is another matter that I'm not sure how we can verify that other than looking at the marking (which you already did).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/05/2018 09:16PM by bodhi.
|
Re: HP 5325 ethernet stopped working November 06, 2018 01:17PM |
Registered: 5 years ago Posts: 180 |
I've dug out the router supplied by my ISP and connected it to the hp t5325 using a different cable. I get the exact same results. The router shows a 100 Mbps connection on the lan1 port but the device does not show up in the list of connected clients. Sending a ping does not work and there is no working connection. So the only thing left to test is going back to stock and check if it is a hardware problem. I've messed up the mtd when I previously tried to go back to stock so it would be appreciated if someone can share a copy of their "permanent u-boot env", "HP env" and "SSD firmware" mtd partitions.
Koen
Koen
|
Re: HP 5325 ethernet stopped working November 06, 2018 01:51PM |
Registered: 6 years ago Posts: 57 |
|
Re: HP 5325 ethernet stopped working November 06, 2018 03:38PM |
Admin Registered: 12 years ago Posts: 17,933 |
fortis91 Wrote:
-------------------------------------------------------
> 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.
Let me post the commands for you.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> 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.
Let me post the commands for you.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: HP 5325 ethernet stopped working December 03, 2018 06:19AM |
Registered: 9 years ago Posts: 1,037 |
|
Re: HP 5325 ethernet stopped working December 03, 2018 03:32PM |
Registered: 5 years ago Posts: 180 |
No not yet. I've been quite busy with work and other stuff recently so haven't got around to do more testing. I still think it is a hardware problem but the only way to test that assumption is to go back to stock. I haven't got a backup of all the original mtd partitions so would need someone else to upload their copy / backup to be able to test this.
Koen
Koen
|
Re: HP 5325 ethernet stopped working December 03, 2018 05:21PM |
Admin Registered: 12 years ago Posts: 17,933 |
Sorry I forgot about this thread! I need to provide fortis the mtd backup commands.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: HP 5325 ethernet stopped working December 03, 2018 09:50PM |
Admin Registered: 12 years ago Posts: 17,933 |
fortis,
Your mtds:
Here are the commnands:
After, check the file sizes to see if the backup mtds are OK:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Your mtds:
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 "hp_env"
Here are the commnands:
dd if=/dev/mtd0 of=mtd0.t5325.u-boot bs=512k conv=sync dd if=/dev/mtd1 of=mtd1.t5325.sdd_firmware bs=256K conv=sync dd if=/dev/mtd2 of=mtd2.t5325.u-boot_env bs=64K conv=sync dd if=/dev/mtd3 of=mtd3.t5325.permanent_u_boot_env bs=64K conv=sync dd if=/dev/mtd4 of=mtd4.t5325.hp_env bs=64K conv=sync
After, check the file sizes to see if the backup mtds are OK:
ls -lh mtd*
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: HP 5325 ethernet stopped working December 05, 2018 05:18PM |
Registered: 6 years ago Posts: 57 |
Hi Guy,
Here you go:
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 in 1+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0.833651 s, 629 kB/s v=syncebian:~/mtd-backup# dd if=/dev/mtd1 of=mtd1.t5325.sdd_firmware bs=256K conv 1+0 records in 1+0 records out 262144 bytes (262 kB, 256 KiB) copied, 0.418295 s, 627 kB/s ynct@debian:~/mtd-backup# dd if=/dev/mtd2 of=mtd2.t5325.u-boot_env bs=64K conv=sy 1+0 records in 1+0 records out 65536 bytes (66 kB, 64 KiB) copied, 0.103755 s, 632 kB/s 64K conv=sync/mtd-backup# dd if=/dev/mtd3 of=mtd3.t5325.permanent_u_boot_env bs=6 1+0 records in 1+0 records out 65536 bytes (66 kB, 64 KiB) copied, 0.10403 s, 630 kB/s root@debian:~/mtd-backup# dd if=/dev/mtd4 of=mtd4.t5325.hp_env bs=64K conv=sync 1+0 records in 1+0 records out 65536 bytes (66 kB, 64 KiB) copied, 0.104202 s, 629 kB/s root@debian:~/mtd-backup# ls -lrht mtd* -rw-r--r-- 1 root root 512K Dec 5 15:07 mtd0.t5325.u-boot -rw-r--r-- 1 root root 256K Dec 5 15:07 mtd1.t5325.sdd_firmware -rw-r--r-- 1 root root 64K Dec 5 15:07 mtd2.t5325.u-boot_env -rw-r--r-- 1 root root 64K Dec 5 15:07 mtd3.t5325.permanent_u_boot_env -rw-r--r-- 1 root root 64K Dec 5 15:08 mtd4.t5325.hp_env
|
Re: HP 5325 ethernet stopped working December 05, 2018 05:18PM |
Registered: 6 years ago Posts: 57 |
|
Re: HP 5325 ethernet stopped working December 05, 2018 06:06PM |
Registered: 5 years ago Posts: 180 |
|
Re: HP 5325 ethernet stopped working December 09, 2018 10:08AM |
Registered: 5 years ago Posts: 180 |
I've used to following section of the original stock dmesg output to put together the different mtd files in the correct order (using my backup of uboot and the env combined with the other files supplied by fortis91). I've used cat to merge all the files together and added an empty file to the end to match the size of the 1M chip. I've then used flashrom on my raspberry pi to flash the 1M file to the chip.
When I boot the device it is running HP uboot and starts booting the stock firmware on the device. I'm not getting anything else on serial so will plug in a monitor and keyboard to see what is happening.
Edited 1 time(s). Last edit at 12/09/2018 10:23AM by Koen.
[ 1.070000] Creating 5 MTD partitions on "spi_flash": [ 1.070000] 0x000c0000-0x000d0000 : "u-boot env" [ 1.070000] 0x000d0000-0x000e0000 : "permanent u-boot env" [ 1.070000] 0x000e0000-0x000f0000 : "HP env" [ 1.070000] 0x00000000-0x00080000 : "u-boot" [ 1.080000] 0x00080000-0x000c0000 : "SSD firmware"
When I boot the device it is running HP uboot and starts booting the stock firmware on the device. I'm not getting anything else on serial so will plug in a monitor and keyboard to see what is happening.
picocom v2.2
port is : /dev/ttyUSB0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
stopbits are : 1
escape is : C-a
local echo is : no
noinit is : no
noreset is : no
nolock is : no
send_cmd is : sz -vv
receive_cmd is : rz -vv -E
imap is :
omap is :
emap is : crcrlf,delbs,
Type [C-a] [C-h] to see available commands
Terminal ready
�
_ _ .____
| |_| | | _ \
| _ | | (_))
| |-| | | |
|_| |_| |_| ..
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** LOADER **
** BOARD: DB-88F6281A-BP LE
U-Boot 1.1.4 (Jan 8 2010 - 14:03:56) MIC version : 3.4.19-16
U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CD4E0
Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz
DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM CS[1] base 0x10000000 size 256MB
DRAM Total size 512MB 16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
[1024kB@f8000000] Flash: 1 MB
CPU : Marvell Feroceon (Rev 1)
.
Un-Protected 1 sectors
Erasing Flash...
.
Erased 1 sectors
Writing to Flash... done
.
Protected 1 sectors
.
Un-Protected 1 sectors
Erasing Flash...
.
Erased 1 sectors
Writing to Flash... done
.
Protected 1 sectors
Streaming disabled
Write allocate disabled
USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
Net: egiga0 [PRIME], egiga1
Hit any key to stop autoboot: 0
Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
Device 0 @ 0 0:
Model: SM22 Firm: I052 Ser#: (03)5526888-20080228
Type: Hard Disk
Capacity: 463.6 MB = 0.4 GB (949536 x 512)
1888432 bytes read
Checking Button Status: off
Checking GotoWOL Status: Not set, Setting to off
.
Un-Protected 1 sectors
Erasing Flash...
.
Erased 1 sectors
Writing to Flash... done
.
Protected 1 sectors
## Booting image at 00200000 ...
Image Name: Linux-2.6.22.18-2-armel
Created: 2009-11-17 18:35:01 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1888368 Bytes = 1.8 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK
Starting kernel ...
Uncompressing Linux......................................................................................................................... done, booting the kernel.
FATAL: term closed
Edited 1 time(s). Last edit at 12/09/2018 10:23AM by Koen.
