USB mouse/kb troubles on sam460

[mechanic]

Most welcome.

Be sure to keep tinkering.

Perhaps you could be of help to @kilaueabart in the thread 'Another USB2 hub problem -- sort of solved'
as he is also having some troubles. Might even come in handy for your review/troubleshooting guide.

One of the things I wonder about is the context(?) switching when you plug a 1.1 device into a 2.0 hub.

I mean, if there is a 2.0 data stream moving through the hub and then you start mousing around with a
1.1 device plugged into the same 2.0 hub, , , it all goes down the same wires, , , just sounds messy.

[metalheart]

It appears it's NOT solved.....

Problems returned. But this time I have to unplug/plug the mouse/kb sometimes several times before they work.
Also the USB mouse sometimes has this behaviour.

Going back to an earlier install when everything seemed to work.....

[chris]

@metalheart

See also viewtopic.php?f=14&t=744 (and I'm pretty sure there are more older ones of the same ilk)

USB has been pretty unreliable since Update 3.

[metalheart]

Great !

So, now it seems to be a USB bug in OS4.1.4 ?

Time to get it fixed me thinks....


Thanks

[mechanic]

@metalheart
USB has been pretty unreliable since Update 3.

I believe Up 3 introduced USB2 (EHCI). Maybe just not ready for primetime. (?)

[metalheart]

Exactly... My problem started when I installed upd 3...
But it worked fine for a while... I dont get that.

Right now it is again working fine (upd 4) with a USB wired mouse and kb connected to the back port, and the wireless mouse/kb connected via a PS2 to USB adapter to the front ports of my tower. (again... wireless mouse/kb seems to be working fine)

When is update 5 due ?

[chris]

@metalheart
USB has been pretty unreliable since Update 3.

I believe Up 3 introduced USB2 (EHCI). Maybe just not ready for primetime. (?)

Unfortunately disabling the EHCI drivers doesn't resolve the problem, I daresay the introduction of USB2 is related but there's something else going on here.

[mechanic]

@metelheart
Going wireless for M&K solved my problems as well, even before Up3.

@chris

Unfortunately disabling the EHCI drivers doesn't resolve the problem,
I daresay the introduction of USB2 is related but there's something else
going on here.

I agree. EHCI is working fine on my 440ep. Though I seldom have real need
for the extra speed.

I know this sounds stupid, but its almost as if the software is outrunning
the hardware as far as configuration goes.

[Belxjander]

All this talk about USB2 devices seems really odd to me... but then I am using a combined Wireless Keyboard and mouse from bootup without any issues...

the only thing I have apparently done differently to everyone else was once I had installed from the CD I updated further by hand for my sam440-flex boards setup... as the installers didn't work...

I installed the "common" fileset first followed by the 440 specific files.

I've only ever had 2x boot issues from my own forgetting to update the KickLayout before restarting and needing to work out the SObjs that are essential along with installing any extras that may be additionally required.

I've been deliberately installing the SObjs singularly and making Soft-Links with the Makelink command myself (I'm considering automating this)

The only other issues I have had are non-functional python and TimberWolf applications (not everything is going to work right away is what I understand)

and I think that is related to missing some SObjs:#?.so files for both python and TimberWolf

[nbache]

the only thing I have apparently done differently to everyone else was once I had installed from the CD I updated further by hand for my sam440-flex boards setup... as the installers didn't work...

If you could elaborate on this, it would be most welcome.

A sizable group of betatesters with diverse system setups go through lengthy testing every time an update archive is nearing completion, with focus especially on the installer to work (at least).

So if you happen to have circumstances where this was not the case, it would be great if you could open a thread here in the AmigaOS support forum and describe those circumstances, so we can try checking for them in future testing. Also don't forget to tell us in which way the installers "didn't work", i.e. what happened, and when.

Thanks.

Best regards,

Niels