Thanks, I tried and failed though, it wouldn't seem to do anything in tftp64. Is there anything else I should be doing in tftp64? The led on router lights up when the lan cable is connected.
It isn't stated in the original instructions, but you need an Ethernet cable connecting your PC and router.
(I'm sure you figured that out, but sometimes we overlook the obvious)
Other details for tftpd64...
- ensure the Current Directory contains the vmlinuz file
- ensure the Server Interface is the Windows adapter to which you've assigned 192.168.1.2 (mine defaulted to the loopback adapter 127.0.0.1)
- once you've successfully booted to openwrt, stop tftpd64 or unplug the ethernet cable connecting router/PC, otherwise your router will pickup vmlinuz upon its next reboot
SORRY, but that is simply NOT true.
All you have to do is install its old driver on a WIN10 machine.
I rarely use mine but sometimes I stiil do and always have to install the 'Prolific' driver if using the WIN10 computer.
I have the drivers here ---> 'Installing profilic-drivers on Windows 10' ... that was just a part of the 'DD-WRT EA8500' install guide I put up few years back
Windows 8/8.1/10 are NOT supported in PL-2303HXA and PL-2303X EOL chip versions.
Run PL2303 CheckChipVersion tool program in Windows XP/Vista/7 to check chip version.
Windows Vista, XP, 2000, 98 and Windows ME driver technical support are discontinued.
Prolific recommends to use PL-2303HXD (HX Rev D) or PL2303TA chip.
Gradius,
THERE IS NO OFFICIAL WINDOWS 10 INSTALLER.
and
Actaully there were many counterfeit PL-2303HX using Prolific's name but if you have one that works fine on your old system then it will work fine in WIN10.
Why don't you do like I ask and try it rather than posting a five year old article
and
if you looked at the link I posted you will see that the driver I used is from 2008.....they just never made an official WIN 10 installer.
Hi yes ethernet cable is connected and changed default ip in tftp64 nothing is shown in log viewer though. Vmlinuz is in the same directory as tftpd
flyzipper wrote:
darkteckno wrote:
Thanks, I tried and failed though, it wouldn't seem to do anything in tftp64. Is there anything else I should be doing in tftp64? The led on router lights up when the lan cable is connected.
It isn't stated in the original instructions, but you need an Ethernet cable connecting your PC and router.
(I'm sure you figured that out, but sometimes we overlook the obvious)
Other details for tftpd64...
- ensure the Current Directory contains the vmlinuz file
- ensure the Server Interface is the Windows adapter to which you've assigned 192.168.1.2 (mine defaulted to the loopback adapter 127.0.0.1)
- once you've successfully booted to openwrt, stop tftpd64 or unplug the ethernet cable connecting router/PC, otherwise your router will pickup vmlinuz upon its next reboot
Posted: Sun Jul 28, 2019 10:49 Post subject: Re: New Firmware
kernel-panic69 wrote:
mrjcd wrote:
labrok wrote:
Has anyone tgried the new firmware r40443? I am a bit afraid to try it again if anyone do succesfull flash inform us guys!
yea tis working on RT-N12D1 / E2500 / E1200v2
The RT-N12D1 is only one I run 24/7 and he is just a WAP... all good.
Same ol VAP problem --- I tested on the others.
So, it doesn't break Broadcom MIPS? I guess I'll open a new build thread, since nobody else has yet
@labrok, if THIS build only breaks ARM, then I wouldn't bother as I have seen no commits to revert what I think broke things. Just my $0.02
Last time i was lucky, my DIR-868L rev C just soft bricked, next time might not been as lucky, i will wait for a couple of days.
Joined: 08 May 2018 Posts: 14125 Location: Texas, USA
Posted: Sun Jul 28, 2019 10:58 Post subject: Re: New Firmware
labrok wrote:
kernel-panic69 wrote:
mrjcd wrote:
labrok wrote:
Has anyone tgried the new firmware r40443? I am a bit afraid to try it again if anyone do succesfull flash inform us guys!
yea tis working on RT-N12D1 / E2500 / E1200v2
The RT-N12D1 is only one I run 24/7 and he is just a WAP... all good.
Same ol VAP problem --- I tested on the others.
So, it doesn't break Broadcom MIPS? I guess I'll open a new build thread, since nobody else has yet
@labrok, if THIS build only breaks ARM, then I wouldn't bother as I have seen no commits to revert what I think broke things. Just my $0.02
Last time i was lucky, my DIR-868L rev C just soft bricked, next time might not been as lucky, i will wait for a couple of days.
I am wondering if they were all technically soft bricks, and if a power cycle would've cured the issue. It's like the serial console messages I have been getting for quite a while related to xc and kernel panics post-flash. One of many things that really do not make sense to me. FWIW, there have been positive reports on Broadcom ARM devices in the 40443 build thread.
now start router and within 10 seconds it will load the file to memory.
now wait and now you can get into openwrt probably trough 192.168.1.1 (in browser) use username root and pw admin and now I could load an old dd-wrt version.
I hope this will help you too.
Cant believe I got this working again by myself
I got this process to work, however, i cannot get to the browser. Is this for R7000 only, or is the vmlinuz generic?
Hi yes ethernet cable is connected and changed default ip in tftp64 nothing is shown in log viewer though. Vmlinuz is in the same directory as tftpd
flyzipper wrote:
darkteckno wrote:
Thanks, I tried and failed though, it wouldn't seem to do anything in tftp64. Is there anything else I should be doing in tftp64? The led on router lights up when the lan cable is connected.
It isn't stated in the original instructions, but you need an Ethernet cable connecting your PC and router.
(I'm sure you figured that out, but sometimes we overlook the obvious)
Other details for tftpd64...
- ensure the Current Directory contains the vmlinuz file
- ensure the Server Interface is the Windows adapter to which you've assigned 192.168.1.2 (mine defaulted to the loopback adapter 127.0.0.1)
- once you've successfully booted to openwrt, stop tftpd64 or unplug the ethernet cable connecting router/PC, otherwise your router will pickup vmlinuz upon its next reboot
Make sure you client ip is 1.2 and your gateway is 1.1
now start router and within 10 seconds it will load the file to memory.
now wait and now you can get into openwrt probably trough 192.168.1.1 (in browser) use username root and pw admin and now I could load an old dd-wrt version.
I hope this will help you too.
Cant believe I got this working again by myself
I got this process to work, however, i cannot get to the browser. Is this for R7000 only, or is the vmlinuz generic?
I guess this is generic, but cant find the forum anymore. Maybe you can search for a specific R7000 vmlinux. Good luck