This is a weird issue, so bear with the description. I am hoping that someone out there will have an idea of what I should try next.

A couple of years ago, I purchased a new AmigaOne 500 system direct from ACube. Great service, loved the machine. It came with Amiga OS 4.1 Update 2. I installed the 3 and 4 updates. Everything seemed to work fine, and I used the machine on and off.

The other day, I went to boot her up and she booted fine but once Amiga OS loaded, the machine seemed locked---no mouse or keyboard response. After some debugging, I discovered that if I kept the network cable unplugged, the system worked fine. As soon as I would plug in the Ethernet cable, the machine would lock with no mouse/keyboard response. Still get a light on the mouse, but the keyboard won't even give me a caps lock response

I reinstalled the original 4.1 U2 from the SD card; same result. I ordered and installed 4.1 FE---same result. I installed 4.1 FE on a spare SD card, disconnected the hard drive completely---same result. I have tried both DHCP and static connections.

The machine has 2 gb ram, a SATA card, and I am using the onboard USB, ethernet, and VGA.

If I remove the network set up from the system, I can boot with the network cable installed without a lockup. But, as soon as I configure the network---it locks.

I booted with an Ubuntu PPC live disk---no graphics but the console saw the ethernet adaptor and connected without issue. So, it doesn't sound like a hardware issue. It seems to be a driver issue, but it worked once and then stopped without a change. So I am puzzled.

I am willing to use a card for ethernet or USB but I'd like some indication of what might need to be done.

Any thoughts? Even wacky ones

thanks,
kenny

@kmoorman

Check if time (hour/date) is correct when booting.

_________________
PowerMac G5 2,7Ghz - 2GB - Radeon 9650 - MorphOS 3.14
AmigaONE X1000, 2GB, Sapphire Radeon HD 7700
FPGA Replay + DB 68060 at 85Mhz

@kmoorman

Looks like another flavor of the famous USB stack bug.

I have sometimes trouble with USB dropping off. Often it can be fixed by removing and reconnecting USB devices. Does it work for you?

I had not noticed any link with network being in connected state or not, but I will pay attention to it next time.

++

"I discovered that if I kept the network cable unplugged, the system worked fine."

Perhaps something has changed on signal grounding of ethernet or AC side.
At least SAM440 is known to be sensitive with that.

Have you tried if it works when network cable is connected but network stack is not running?

+++!!!
"If I remove the network set up from the system, I can boot with the network cable installed without a lockup. But, as soon as I configure the network---it locks."

Great, you tried also that.
So, it's a SW/driver issue!

(the ethernet driver might be messing some memory area that belongs to USB stack or USB side uses memory outside it's reserved area.
For you, the issue has perhaps come "live" after some update. On my SAM440 I have seen those on/off since 4.1 first release.)

I think A1X1000 users have not had these problems, so I think ACube needs to re-check their low level drivers.

(+ now I noticed a reason why I should have PPC linux installed, to debug this kind of phenomenoms))

Last edited by KimmoK on 03-Jul-2015 at 06:55 AM.
Last edited by KimmoK on 03-Jul-2015 at 06:53 AM.
Last edited by KimmoK on 03-Jul-2015 at 06:51 AM.
Last edited by KimmoK on 03-Jul-2015 at 06:48 AM.
Last edited by KimmoK on 03-Jul-2015 at 06:40 AM.
Last edited by KimmoK on 03-Jul-2015 at 06:38 AM.

_________________
- KimmoK
// For freedom, for honor, for AMIGA
//
// Thing that I should find more time for: CC64 - 64bit Community Computer?

@K-L

Nope, the date and time are off. I assume I need a new battery. Would that affect
the other stuff?

thanks,
kenny

@kmoorman

Not being able to help you, I at least bump this thread.


And of course...

Welcome!

@kmoorman

>Would that affect the other stuff?

Everything is possible with bad battery, they say.
(it seems to be the nbr. 1 thing to check, after the main fuse of your house)

_________________
- KimmoK
// For freedom, for honor, for AMIGA
//
// Thing that I should find more time for: CC64 - 64bit Community Computer?

@kmoorman

What do you mean by "off" ?

When you boot without ethernet, try setting correct date and time and then try to connect the net.

_________________
PowerMac G5 2,7Ghz - 2GB - Radeon 9650 - MorphOS 3.14
AmigaONE X1000, 2GB, Sapphire Radeon HD 7700
FPGA Replay + DB 68060 at 85Mhz

@K-L

Initially, the year is set to 2035; I believe the month and day are 1/1.

I will try to boot w/o ethernet, set the clock, and then try setting up ethernet.

I'll also dig out a new battery

thanks for the idea,
kenny

@kmoorman

Is that turned off or off by a fraction?

You may need to use the date command in UBoot. Then the OS. But if the dirver is tripping up over a date and locking up that's worthy of bug report. If you had a serial cable.

More info.

First, setting the correct time in uboot and amigaOS does not change the behavior.

Second, although I had thought previously that the mouse was still lit up after the hang, I see now that it
is only lit until I unplug it. When I plug it back in, the mouse light flickers then nothing.

Very frustrating. More so since it used to work.

thanks for all the comments and advice,
kenny

@kmoorman

This may only turn out to be of diagnostic use, but it does something you can't, it does a " usb reset" without a working keyboard.
http://os4depot.net/index.php?function=showfile&file=utility/misc/usbrecycle.lha

Draby

@Draby

Thanks for the pointer to USBRecycle---I had hopes for that. However, no change. It still locks
up.

more things I have tried:

a) I don't loadwb at the end of the startup sequence. Same problem.
b) Both static and dynamic IPs suffer
c) Physically moved the machine to a new location, tried a new power cable, 2 new ethernet cords.
Same issue.
d) Popped out the 2gig memory chip and replaced with a spare 1 gig. Same issue.

It's still a beautiful machine just no network.

kenny

@kmoorman

type this in Shell.

list Devs/NetInterfaces/

copy past the result.

type this in Shell

c:ShowNetStatus

copy past the result.

type this in Shell

c:GetNetStatus

copy past the result.

Last edited by NutsAboutAmiga on 07-Jul-2015 at 06:26 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@kmoorman

Here's a thought, assuming you have USBRecycle in User-Startup, Network-Startup follows that, try moving USBRecycle to the end of Network-Startup.
Just tried it in mine, apart from a small fart from the speakers, nothing broke.

Draby

@Draby

Thanks.

I had the USBRecycle in S:Startup-Sequence, right before loadwb and after the
network-startup should execute.

kenny

@NutsAboutAmiga

Here it all is. Also, thanks for the GetNetStatus, I had missed that command while looking for things to help me.

5.Workbench:> list Devs/NetInterfaces/
Directory "Devs/NetInterfaces" on Wednesday 08-Jul-15
PPC460EX_ETH.info 10086 ----rw-d Today 11:17:29
PPC460EX_ETH 191 ----rwed Today 11:17:29
2 files - 10K bytes - 13 blocks used


**** Contents of that file:

# DEVS:NetInterfaces/PPC460EX_ETH
# File generated by Dialer 53.2 (3.10.2009)
# On Wednesday, 08-Jul-15 at 11:17:29
device=ppc460ex_eth.device
unit=0
address=10.20.3.85
netmask=255.255.255.0



5.Workbench:> shownetstatus
Network status summary
Local host address = 10.20.3.85 (on interface 'PPC460EX_ETH')
Default gateway address = 10.20.3.1
Domain name system servers = 10.20.70.16



5.Workbench:> getnetstatus
bsdsocket.library 4.307 (9.2.2012) [Roadshow 4.307 (9.2.2012)]
Networking interfaces are available and configured.
No point-to-point networking interfaces are available and configured.
Broadcast networking interfaces are available and configured.
Name resolution servers are configured.
Routing information is configured.
The default route is configured.

@kmoorman

Can you ping your router 10.20.3.1?
If you type this in Shell:

Ping 10.20.3.1

"Domain name system servers = 10.20.70.16"

You can try changing this to "10.20.3.1", normally the router can take care of DNS hookups, as router normally gets its DNS servers from your ISP.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Well, in the 5 to 10 seconds that the system will have before locking up,
a ping returns icmp unknown protocol.

However, I can ping the amiga from my other (Linux) machine without
trouble. Until the lock up of course.

kenny

@kmoorman

Quote:

Well, in the 5 to 10 seconds that the system will have before locking up.

I think, your problems are else where, maybe RAM, maybe PSU, have you installed anything lately that run in s:user-startup or wbstartup.

I will suggest disabling screenblankers, they have tendency to mess things up.

You might also have corruped config files, you can try to delete files, and reconfigure.

Quote:

a ping returns icmp unknown protocol.

The network stack takes time to startup, if you look in s:startup-sequence, you can see the "run" command is used to start a new process that start network-startup. So network might not be ready, so early on.

DHCP normally takes a bit of time to; negotiate a local IP with the internet router.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

I have tried different ram; same results. There were no changes software wise; I had not used
the system in a while---it had worked fine the last time. I've also reinstalled 4.1 U2 through 4.1 FE to the same result.

I hadn't thought about the screen blankers but I have created the problem without workbench loading, so I don't think it will be the blankers.

I have thought about the power supply but don't have a current spare to try. I could cannibalize one from another machine, but that will be a later project.

thanks,
kenny