GR8NET Network connection trouble

Page 1/2
| 2

By The Apeman

Resident (55)

The Apeman's picture

05-08-2020, 20:16

I have a peculiar problem. When I boot my Philips VG-8235 with my GR8NET in slot 1 (target mapper 18) it shows me the results of a successful dhcp request after which I get a Nextor prompt. Often, but not always, some tools won't acknowledge the network connection:

A:\>hub list
*** No network connection available.
A:\>hget msx.org
...
*** Unknown host name

Yet, I can use sofaftp without any problem, I can ping the GR8NET from any other PC in my network and _netbrowse in BASIC allows me to navigate "Internet" without issue.

This problem occurs often since about a week, but not always. Can someone help me find out what is going on here?

Login or register to post comments

By sdsnatcher73

Paragon (1095)

sdsnatcher73's picture

06-08-2020, 12:07

Just out of curiosity, did you upgrade to 0.12 release a week ago? If so that may explain the timeline (and you might have stumbled upon a bug in that release, which includes Nextor 2.1.0 final). If you have not updated you could give it a try and see if the situation improves.

By The Apeman

Resident (55)

The Apeman's picture

06-08-2020, 17:20

I have NEXTOR.SYS version 2.11. I did upgrade the firmware and image of the GR8NET yesterday, but that was after the problems had started.

And now _netbrowse->Internet fails with a Device I/O error. So I went trough the steps in the GR8NET-manual under "Every networking command (NETBLOAD, NETBROWSE) returns Device I/O error" but without results.

I can still login to the vsftp server on my Linux box and ping the IP of the GR8NET from that machine.

By Pencioner

Scribe (1149)

Pencioner's picture

06-08-2020, 18:09

do you log in to your vsftp server by ip? if so - it looks like you got no working DNS there (either DHCP didn't work properly or whatever). try to do _NETDHCP manually few times again and then _NETBROWSE - and if it works - then that's it. I had similar problem after changing network equipment and it turned out that DHCP timeouts were too short on new one. i had to increase the DHCP timeouts (i don't remember which comand exactly does that but it is in GR8NET manual), and after increasing it and saving settings with _NETSAVE - everything works as it should

By The Apeman

Resident (55)

The Apeman's picture

06-08-2020, 20:04

No, I log in by hostname, so the DNS is okay. Or does sofaftp has some sort of DNS caching? Also, I put ping.com (from nextor tools) and and it also works by hostname.

Is there a difference between the dhcp request at boot and _netdhcp? I always get and IP at boot without problem and _netdhcp also works without issue. But not only UDP works: I downloaded the latest hget and usign it I can download stuff over http again.

So now _netbrowse and hub do not work, but ping, sofaftp and hget do. oO

By Pencioner

Scribe (1149)

Pencioner's picture

06-08-2020, 20:32

might also be some configuration issue after the firmware upgrade. if you didn't update configuration area ("to not lose my settings"), this is not working sometimes like that. some bad bytes might end up in the url string used by _netbrowse which may give errors. i would reconfigure it with _netconfig and in the future i recommend to use the _netexprt and _netimprt commands which are designed for retaining config between fw updates

By sdsnatcher73

Paragon (1095)

sdsnatcher73's picture

06-08-2020, 20:53

I agree, with Pencioner. If you did not flash with a clean config issues like this can occur. However in my experience just running _netconfig will not be enough. You have to reflash the firmware (not FPGA) and this time clear the config during flashing. You won’t be able to do this using _netbrowse (as that is not working, which also happened to me). I don’t recall the exact procedure that fixed it for me (I suspect putting the update on floppy and _netbload’ing it did the trick).

However as this issue started before the update it may still be something different. Although reflashing won’t hurt.

By The Apeman

Resident (55)

The Apeman's picture

07-08-2020, 10:23

sdsnatcher73 wrote:

I agree, with Pencioner. If you did not flash with a clean config issues like this can occur. However in my experience just running _netconfig will not be enough. You have to reflash the firmware (not FPGA) and this time clear the config during flashing.

Thanks. I will try that tonight.

By edoz

Prophet (2298)

edoz's picture

07-08-2020, 17:30

Does it work in SymbOS?

By The Apeman

Resident (55)

The Apeman's picture

07-08-2020, 22:42

sdsnatcher73 wrote:

You have to reflash the firmware (not FPGA) and this time clear the config during flashing. (I suspect putting the update on floppy and _netbload’ing it did the trick).

I just made matters worse. I tried doing what you suggested by following chapter 10.5.1. Offline update of the onboard flash chip in the manual, by putting the files from http://www.gr8bit.ru/software/firmware/GR8NET/bloadable/ on a floppy and running fwupdate.bas. After it finished, I tried doing a _flupdate. It immediate rebooted my MSX and since when I boot the MSX with the GR8NET inserted, all I get is a blue screen. ;(

Since I can't boot the computer with the GR8NET inserted, is there a way to solve it, or did I just brick it?

By Pencioner

Scribe (1149)

Pencioner's picture

07-08-2020, 23:39

pressing arrow up on boot should skip initialization rom, therefore giving you chance to try offline update again (did you miss something?)

Page 1/2
| 2