HP 5325 ethernet stopped working
Posted by Koen
|
Re: HP 5325 ethernet stopped working October 25, 2018 06:27PM |
Admin Registered: 13 years ago Posts: 18,843 |
@Koen,
Please try kwboot this version:
uboot.2016.05-tld-1.t5325.bodhi.tar
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/25/2018 06:29PM by bodhi.
Please try kwboot this version:
uboot.2016.05-tld-1.t5325.bodhi.tar
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/25/2018 06:29PM by bodhi.
|
Re: HP 5325 ethernet stopped working October 25, 2018 06:30PM |
Registered: 6 years ago Posts: 183 |
|
Re: HP 5325 ethernet stopped working October 25, 2018 06:30PM |
Admin Registered: 13 years ago Posts: 18,843 |
fortis & Koen,
I think you should try kwboot the previous version to see if the network is working.
uboot.2016.05-tld-1.t5325.bodhi.tar
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
I think you should try kwboot the previous version to see if the network is working.
uboot.2016.05-tld-1.t5325.bodhi.tar
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: HP 5325 ethernet stopped working October 25, 2018 06:31PM |
Registered: 7 years ago Posts: 57 |
|
Re: HP 5325 ethernet stopped working October 25, 2018 07:31PM |
Registered: 7 years ago Posts: 57 |
kwboot
Still no network
One thing I noticed when shutting down:
My router is 192.168.1.1, is it also trying to get an IP from 192.168.0.1?
Edited 2 time(s). Last edit at 10/25/2018 08:35PM by fortis91.
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 % [......................................................................] 5 % [......................................................................] 6 % [......................................................................] 8 % [......................................................................] 10 % [......................................................................] 11 % [......................................................................] 13 % [......................................................................] 15 % [......................................................................] 17 % [......................................................................] 18 % [......................................................................] 20 % [......................................................................] 22 % [......................................................................] 23 % [......................................................................] 25 % [......................................................................] 27 % [......................................................................] 29 % [......................................................................] 30 % [......................................................................] 32 % [......................................................................] 34 % [......................................................................] 35 % [......................................................................] 37 % [......................................................................] 39 % [......................................................................] 41 % [......................................................................] 42 % [......................................................................] 44 % [......................................................................] 46 % [......................................................................] 47 % [......................................................................] 49 % [......................................................................] 51 % [......................................................................] 53 % [......................................................................] 54 % [......................................................................] 56 % [......................................................................] 58 % [......................................................................] 59 % [......................................................................] 61 % [......................................................................] 63 % [......................................................................] 64 % [......................................................................] 66 % [......................................................................] 68 % [......................................................................] 70 % [......................................................................] 71 % [......................................................................] 73 % [......................................................................] 75 % [......................................................................] 76 % [......................................................................] 78 % [......................................................................] 80 % [......................................................................] 82 % [......................................................................] 83 % [......................................................................] 85 % [......................................................................] 87 % [......................................................................] 88 % [......................................................................] 90 % [......................................................................] 92 % [......................................................................] 94 % [......................................................................] 95 % [......................................................................] 97 % [......................................................................] 99 % [....................................] [Type Ctrl-\ + c to quit] U-Boot 2016.05-tld-1 (Jun 12 2016 - 14:06:08 -0700) HP Thin Client T5325 SoC: Kirkwood 88F6281_A1 SPI: ready DRAM: 512 MiB WARNING: Caches not enabled SF: Detected SST25VF080B with page size 256 Bytes, erase size 64 KiB, total 1 MiB In: serial Out: serial Err: serial Net: egiga0 PHY reset timed out 88E1116 Initialized on egiga0 Hit any key to stop autoboot: 0 T5325>
Still no network
T5325> printenv ipaddr ipaddr=192.168.1.253 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
One thing I noticed when shutting down:
Sending on Socket/fallback DHCPRELEASE on eth0 to 192.168.0.1 port 67 send_packet: Network is unreachable send_packet: please consult README file regarding broadcast address. dhclient.c:2733: Failed to send 300 byte long packet over fallback interface. done.
My router is 192.168.1.1, is it also trying to get an IP from 192.168.0.1?
Edited 2 time(s). Last edit at 10/25/2018 08:35PM by fortis91.
|
Re: HP 5325 ethernet stopped working October 25, 2018 09:22PM |
Admin Registered: 13 years ago Posts: 18,843 |
Koen Wrote:
-------------------------------------------------------
> Chip number is 88E3016-NNC1
>
> Koen
That matches the chip in the new uboot 2017.07-tld-1.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Chip number is 88E3016-NNC1
>
> Koen
That matches the chip in the new uboot 2017.07-tld-1.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: HP 5325 ethernet stopped working October 25, 2018 09:25PM |
Admin Registered: 13 years ago Posts: 18,843 |
All,
What is the content of your /etc/resolv.conf?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
What is the content of your /etc/resolv.conf?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: HP 5325 ethernet stopped working October 25, 2018 10:00PM |
Registered: 7 years ago Posts: 57 |
|
Re: HP 5325 ethernet stopped working October 26, 2018 12:17AM |
Admin Registered: 13 years ago Posts: 18,843 |
fortis,
>
> I only flashed these:
>
> Networking was working fine with those.
Let me make sure I understood.
Does it not working in u-boot console now, if you power up and interrupt console and ping the router?
Or it is not working after the kernel booted?
Or both not working?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
>
> 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 make sure I understood.
Does it not working in u-boot console now, if you power up and interrupt console and ping the router?
Or it is not working after the kernel booted?
Or both not working?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: HP 5325 ethernet stopped working October 26, 2018 12:59AM |
Admin Registered: 13 years ago Posts: 18,843 |
Here is my serial console boot log
And ping router again, and Google.com
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/26/2018 01:04AM by bodhi.
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 m25p80 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> ping 192.168.0.1 Using egiga0 device host 192.168.0.1 is alive T5325> printenv arcNumber=2846 bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi bootdelay=10 bootdev=usb custom_params=earlyprintk=serial device=0:1 devices=usb ide disks=0 1 2 3 dtb_file=/boot/dts/kirkwood-t5325.dtb ethact=egiga0 ethaddr=f4:ce:xx:xx:xx:xx if_netconsole=ping $serverip ipaddr=192.168.0.243 led_error=orange blinking led_exit=green off led_init=green blinking load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file load_dtb_addr=0x1c00000 load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd load_initrd_addr=0x1100000 load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage load_uimage_addr=0x800000 mainlineLinux=yes mtdids=nand0=orion_nand mtdparts=mtdparts=spi0.0:512K(uboot),256K(sdd_firmware),64K(uboot_env),64K(permanent_uboot_env),64K(hp_env) partition=nand0,2 preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then ./run start_netconsole; fi scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start"; setenv scan_ide "ide reset"; setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done serverip=192.168.0.220 set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version; stderr=serial stdin=serial stdout=serial uboot_version=U-Boot 2017.07-tld-1 (Nov 01 2017 - 00:58:19 -0700) uenv_addr=0x810000 uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize uenv_init_devices=setenv init_usb "usb start"; setenv init_ide "ide reset"; setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done; uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices; 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 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read; fi; else if $devtype part $disknum; then run uenv_read; fi; fi usb_ready_retry=15 Environment size: 3115/65532 bytes T5325>
And ping router again, and Google.com
T5325> ping 192.168.0.1 Using egiga0 device host 192.168.0.1 is alive T5325> setenv gatewayip 192.168.0.1 T5325> setenv netmask 255.255.255.0 T5325> ping 8.8.8.8 Using egiga0 device host 8.8.8.8 is alive T5325>
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/26/2018 01:04AM by bodhi.
|
Re: HP 5325 ethernet stopped working October 26, 2018 03:52AM |
Admin Registered: 13 years ago Posts: 18,843 |
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
Test 2
Unplug the power cord.
Wait for a while, at least 10 seconds.
Power up, interrupt serial console
Ping the router
If ping was not successful, unplug the ethernet cable, wait a few seconds and plug it back in and ping the router again.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 10/26/2018 04:29AM by bodhi.
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
Test 2
Unplug the power cord.
Wait for a while, at least 10 seconds.
Power up, interrupt serial console
Ping the router
If ping was not successful, unplug the ethernet cable, wait a few seconds and plug it back in and ping the router again.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 10/26/2018 04:29AM by bodhi.
|
Re: HP 5325 ethernet stopped working October 26, 2018 07:14AM |
Registered: 7 years ago Posts: 57 |
bodhi Wrote:
-------------------------------------------------------
bodhi,
sorry for any confusion. It is both not working.
> fortis,
> >
> > I only flashed these:
> >
> > Networking was working fine with those.
>
> Let me make sure I understood.
>
> Does it not working in u-boot console now, if you
> power up and interrupt console and ping the
> router?
>
> Or it is not working after the kernel booted?
>
> Or both not working?
-------------------------------------------------------
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 make sure I understood.
>
> Does it not working in u-boot console now, if you
> power up and interrupt console and ping the
> router?
>
> Or it is not working after the kernel booted?
>
> Or both not working?
|
Re: HP 5325 ethernet stopped working October 26, 2018 07:18AM |
Registered: 7 years ago Posts: 57 |
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
>
>
> Test 2
>
> Unplug the power cord.
> Wait for a while, at least 10 seconds.
> Power up, interrupt serial console
> Ping the router
> If ping was not successful, unplug the ethernet
> cable, wait a few seconds and plug it back in and
> ping the router again.
-------------------------------------------------------
> 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
>
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> ping 192.168.1.1 No link on egiga0 ping failed; host 192.168.1.1 is not alive T5325> ping 192.168.1.1 No link on egiga0 ping failed; host 192.168.1.1 is not alive T5325> ping 192.168.1.1 No link on egiga0 ping failed; host 192.168.1.1 is not alive T5325> ping 192.168.1.1 No link on egiga0 ping failed; host 192.168.1.1 is not alive T5325> ping 192.168.1.1 No link on egiga0 ping failed; host 192.168.1.1 is not alive T5325>
>
> Test 2
>
> Unplug the power cord.
> Wait for a while, at least 10 seconds.
> Power up, interrupt serial console
> Ping the router
> If ping was not successful, unplug the ethernet
> cable, wait a few seconds and plug it back in and
> ping the router again.
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> 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> 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> 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> 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> 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> 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>
|
Re: HP 5325 ethernet stopped working October 26, 2018 04:36PM |
Admin Registered: 13 years ago Posts: 18,843 |
fortis,
That's too bad! I thought it might help to make sure that the multiple pings would help to eliminate false negative.
What I observed while testing was: some of the times (I cannot repeat this test each time), when the box is powering up, u-boot running, and the network connection was not up fast enought, so I would get 1 failed ping. And then when I start pinging the router again, it would establish connection.
Another observation: when you tried kwboot with the 2016.05 u-boot, the PHY was timed out. That was the behavior I expected, since the network chip was in incorrect in that u-boot version. I've fixed this in the 2017.07 u-boot.
Normally, my box ethernet works fine with both cold boot or warm boot. So it is not easy to make it fails. FWIW, the other end of my cable is a Gigabit switch. That switch is connected to a wireless bridge.
I can't think of any reason that it would not work in yours and Koen's box :) other than HW. But HW does not make sense because you both have the same problem.
UPDATE:
I'm asking Ray to try this on his box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 3 time(s). Last edit at 10/26/2018 06:32PM by bodhi.
That's too bad! I thought it might help to make sure that the multiple pings would help to eliminate false negative.
What I observed while testing was: some of the times (I cannot repeat this test each time), when the box is powering up, u-boot running, and the network connection was not up fast enought, so I would get 1 failed ping. And then when I start pinging the router again, it would establish connection.
Another observation: when you tried kwboot with the 2016.05 u-boot, the PHY was timed out. That was the behavior I expected, since the network chip was in incorrect in that u-boot version. I've fixed this in the 2017.07 u-boot.
Normally, my box ethernet works fine with both cold boot or warm boot. So it is not easy to make it fails. FWIW, the other end of my cable is a Gigabit switch. That switch is connected to a wireless bridge.
I can't think of any reason that it would not work in yours and Koen's box :) other than HW. But HW does not make sense because you both have the same problem.
UPDATE:
I'm asking Ray to try this on his box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 3 time(s). Last edit at 10/26/2018 06:32PM by bodhi.
|
Re: HP 5325 ethernet stopped working October 26, 2018 05:36PM |
Registered: 6 years ago Posts: 183 |
Hi bodhi,
I'm getting the same result as fortis91 when doing the 2 tests. I've tried kwboot multiple times but have never got the box to respond. Not sure why since I know the serial connection works fine. I still have backups of the stock mtd0 and mtd3 partitions. Is it worth going back to stock and test the networking to see if it might be a hardware problem?
Koen
I'm getting the same result as fortis91 when doing the 2 tests. I've tried kwboot multiple times but have never got the box to respond. Not sure why since I know the serial connection works fine. I still have backups of the stock mtd0 and mtd3 partitions. Is it worth going back to stock and test the networking to see if it might be a hardware problem?
Koen
|
Re: HP 5325 ethernet stopped working October 26, 2018 06:38PM |
Admin Registered: 13 years ago Posts: 18,843 |
Hi Koen,
> Is it worth going back to stock and
> test the networking to see if it might be a
> hardware problem?
>
Definitely! that would help eliminate some unknowns. This is one of boxes that I think I got every thing figured out, but we'd never know, because we saw there are some differences in various production lots (e.g. flash chip, so who knows what else).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Is it worth going back to stock and
> test the networking to see if it might be a
> hardware problem?
>
Definitely! that would help eliminate some unknowns. This is one of boxes that I think I got every thing figured out, but we'd never know, because we saw there are some differences in various production lots (e.g. flash chip, so who knows what else).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: HP 5325 ethernet stopped working October 27, 2018 03:24AM |
Registered: 9 years ago Posts: 453 |
Looking through the DTS files for some of the other kirkwood systems the ethphy is configured with a compatible line. For instance the kirkwood-dockstar.dts has the following for ethphy0
Which makes me wonder if there would be less problems with the kirkwood-t5325.dts if we modified the ethphy0 definition to:
I've been using a USB Ethernet adapter on my T5325 for some time now as I was constantly having problems with it recognizing the internal port correctly.
Ray
ethphy0: ethernet-phy@0 {
compatible = "marvell,88e1116";
reg = <0>;
};
Which makes me wonder if there would be less problems with the kirkwood-t5325.dts if we modified the ethphy0 definition to:
ethphy0: ethernet-phy@8 {
device_type = "ethernet-phy";
compatible = "marvell,88e3016";
reg = <8>;
};
I've been using a USB Ethernet adapter on my T5325 for some time now as I was constantly having problems with it recognizing the internal port correctly.
Ray
|
Re: HP 5325 ethernet stopped working October 27, 2018 04:32AM |
Admin Registered: 13 years ago Posts: 18,843 |
rayknight,
>
That's a very good point. But because Koen's and fortis's problem occured in u-boot (before the kernel loaded), I think it is perhaps something else about hardware that we don't know about (could be the differences for various releases of this box).
Now that I know you also had some problem with the network, I think that we might need to revisit the GPL and search for hints if there really are more than 1 HW configuration.
The puzzle is that I don't have this problem even though I am running the same u-boot and kernel, and DTB, as everybody else!!!. That's why I thought perhaps hardware configuration plays a role in this problem.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
>
> ethphy0: ethernet-phy@8 {
> device_type = "ethernet-phy";
> compatible =
> "marvell,88e3016";
> reg = <8>;
> };
>
That's a very good point. But because Koen's and fortis's problem occured in u-boot (before the kernel loaded), I think it is perhaps something else about hardware that we don't know about (could be the differences for various releases of this box).
Now that I know you also had some problem with the network, I think that we might need to revisit the GPL and search for hints if there really are more than 1 HW configuration.
The puzzle is that I don't have this problem even though I am running the same u-boot and kernel, and DTB, as everybody else!!!. That's why I thought perhaps hardware configuration plays a role in this problem.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: HP 5325 ethernet stopped working October 27, 2018 06:22AM |
Registered: 6 years ago Posts: 183 |
OK I will have a look at going back to stock to see if it is a hardware issue. Without working ethernet the device is of not much use so may as well give this a try. Accessing the mtd partitions from Debian doesn't work properly on my box at the moment so I guess the best way is via serial connection. I've not got much time this weekend but will start reading up on this so I've got a better idea of the steps involved.
Koen
Koen
|
Re: HP 5325 ethernet stopped working October 27, 2018 05:01PM |
Admin Registered: 13 years ago Posts: 18,843 |
Koen,
> OK I will have a look at going back to stock to
> see if it is a hardware issue.
Or perhaps before going back to stock, you should go through the new u-boot installation again in Debian first to see if it helps.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> OK I will have a look at going back to stock to
> see if it is a hardware issue.
Or perhaps before going back to stock, you should go through the new u-boot installation again in Debian first to see if it helps.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: HP 5325 ethernet stopped working October 27, 2018 06:09PM |
Registered: 7 years ago Posts: 57 |
bodhi,
If you can verify my MTD flash definition is good, I don't mind doing the installation again.
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 "hp_env"
|
Re: HP 5325 ethernet stopped working October 27, 2018 07:05PM |
Admin Registered: 13 years ago Posts: 18,843 |
fortis,
Before doing that, could you try this test in serial console. Basically we want to set the ethaddr to a local MAC address. This MAC addr was randomly generated and set as default in the default envs image "uboot.2016.05-tld-1.environment.64K.img".
Note that it is OK to use this MAC permanently, since it cannot be reached from outside your network. If you have another box that you want to use a local MAC address, then you should generate a new one using a tool (I could upload that binary here for everybody to use).
Power up, interrupt serial console and
After reset, interrupt serial console again and do some tests like I suggested before (i.e. pinging the router a few times).
If you still have network problem, power down, unplug the power cord for a while, and then cold start. And repeat the tests.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Before doing that, could you try this test in serial console. Basically we want to set the ethaddr to a local MAC address. This MAC addr was randomly generated and set as default in the default envs image "uboot.2016.05-tld-1.environment.64K.img".
Note that it is OK to use this MAC permanently, since it cannot be reached from outside your network. If you have another box that you want to use a local MAC address, then you should generate a new one using a tool (I could upload that binary here for everybody to use).
Power up, interrupt serial console and
setenv ethaddr '52:3b:20:9c:11:51' saveenv reset
After reset, interrupt serial console again and do some tests like I suggested before (i.e. pinging the router a few times).
If you still have network problem, power down, unplug the power cord for a while, and then cold start. And repeat the tests.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: HP 5325 ethernet stopped working October 27, 2018 07:17PM |
Registered: 7 years ago Posts: 57 |
|
Re: HP 5325 ethernet stopped working October 27, 2018 08:02PM |
Admin Registered: 13 years ago Posts: 18,843 |
fortis91 Wrote:
-------------------------------------------------------
> bodhi,
>
> Just to confirm it's ok to save:
>
Yes it is ok to save.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> 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.
Yes it is ok to save.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: HP 5325 ethernet stopped working October 27, 2018 08:17PM |
Registered: 7 years ago Posts: 57 |
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> 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 T5325> saveenv Saving Environment to SPI Flash... SF: Detected sst25vf080b with page size 256 Bytes, erase size 64 KiB, total 1 MiB Erasing SPI flash...Writing to SPI flash...done T5325> reset resetting ... 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> 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> 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> 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> 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> ping 192.168.1.1 Using egiga0 device ARP Retry count exceeded; starting again ping failed; host 192.168.1.1 is not alive
Will power down now then repeat.... same result after powering down.
Edited 1 time(s). Last edit at 10/27/2018 08:41PM by fortis91.
|
Re: HP 5325 ethernet stopped working October 27, 2018 10:03PM |
Admin Registered: 13 years ago Posts: 18,843 |
> Will power down now then repeat.... same result
> after powering down.
Bummer :) it must be either hardware or the network chip is different.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> after powering down.
Bummer :) it must be either hardware or the network chip is different.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: HP 5325 ethernet stopped working October 27, 2018 10:08PM |
Admin Registered: 13 years ago Posts: 18,843 |
fortis,
In Debian, use ethtool to list the info
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
In Debian, use ethtool to list the info
ifconfig -a ethtool eth0
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: HP 5325 ethernet stopped working October 27, 2018 10:36PM |
Registered: 7 years ago Posts: 57 |
bodhi,
Here you go:
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 (4.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 38
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 2 bytes 140 (140.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2 bytes 140 (140.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@debian:~# ethtool eth0 Settings for eth0: Supported ports: [ TP AUI BNC MII FIBRE ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 8 Transceiver: internal Auto-negotiation: on Supports Wake-on: d Wake-on: d Link detected: yes
|
Re: HP 5325 ethernet stopped working October 27, 2018 11:14PM |
Admin Registered: 13 years ago Posts: 18,843 |
This is suspect:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Link partner advertised pause frame use: Symmetric Receive-only
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: HP 5325 ethernet stopped working October 27, 2018 11:41PM |
Admin Registered: 13 years ago Posts: 18,843 |
What type of ethernet cable you guys are using? CAT 5, CAT 5e? and what is that cable connect to, a Gigabit switch/router?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
