Welcome, Guest. Please login or register.
Amiga Kit Amiga Store Iridium Banner AMIStore App Store A1200/A600 4xIDE Interface

AuthorTopic: Problem upgrading to OS4.1 update 1  (Read 352 times)

0 Members and 1 Guest are viewing this topic.

Offline SteveH

Problem upgrading to OS4.1 update 1
« on: July 10, 2021, 04:18:37 PM »
I thought I'd finally take the plunge and update my X1000 backup partition from OS4.1FE to the current version, update 4. I realise I first need to upgrade to update 1 but when I have done this (using the archive on Hyperion's site), I get a Grim Reaper telling me that "HID keyboard" has generated an unknown error (task 0x626b2b30). Although I can see WB, and the WB clock is running, neither the keyboard nor the mouse is responsive, so I am unable to do anything other than do a hard re-set (and boot into my normal partition).
Any thoughts on what's causing the error or what I need to check in order to fix it?
Steve
 

Offline nbache

Re: Problem upgrading to OS4.1 update 1
« Reply #1 on: July 10, 2021, 06:07:49 PM »
I would start by comparing the files in the two partitions, especially Kickstart/usbsys.device and Kickstart/usbresource.library plus the uhci/ohci/ehci ones, and then everything in Devs/USB/*/. If you find one that is different in the two partitions, try copying the one from your working partition over to the other one (after renaming the one you have, just in case).

If this doesn't do it, a serial log might give some clues; I don't know if you are able to capture one?

Best regards,

Niels
 

Offline SteveH

Re: Problem upgrading to OS4.1 update 1
« Reply #2 on: July 10, 2021, 11:36:26 PM »
I would start by comparing the files in the two partitions, ...
If this doesn't do it, a serial log might give some clues; I don't know if you are able to capture one?
I've already compared files on the back-up partition with the files on the boot CD but can find no differences :(
Yes, serial logging is next - I just need to fetch down a Linux box from upstairs.
 

Offline SteveH

Re: Problem upgrading to OS4.1 update 1
« Reply #3 on: July 12, 2021, 01:14:36 PM »
OK, serial log attached - not sure whether it helps!
Steve
 

Offline nbache

Re: Problem upgrading to OS4.1 update 1
« Reply #4 on: July 12, 2021, 02:02:22 PM »
Well, it at least seems to confirm something spooky is going on with USB and the HID stuff.

But why it is doing it, I can't tell.

If you have more space available on the drive, maybe you should make another partition and try installing all the way - FE from CD, then update1 (manually, not via AmiUpdate!), then update2 and whatever else AmiUpdate offers at that point, bit by bit. Hopefully you'll be able to get through it that way - it has worked for many others, myself included.

You don't happen to have a very special keyboard or mouse, do you? If so, try replacing them (at least temporarily) with more simple standard ones.

Best regards,

Niels
 

Offline SteveH

Re: Problem upgrading to OS4.1 update 1
« Reply #5 on: July 12, 2021, 02:33:14 PM »
Well, it at least seems to confirm something spooky is going on with USB and the HID stuff ... You don't happen to have a very special keyboard or mouse, do you? If so, try replacing them (at least temporarily) with more simple standard ones.
Thanks for checking the log output. The keyboard and mouse are both "official" AmigaONE ones that came with my X1000.
There's nothing on the backup partition I need, so I think I'll reinstall from scratch on to that.
Steve
 

Offline nbache

Re: Problem upgrading to OS4.1 update 1
« Reply #6 on: July 12, 2021, 03:40:12 PM »
Maybe it would be good if you made a complete backup of the backup partition before you reformat it, then you could compare e.g. with DirDiff afterwards so we might get a clue which file(s) were causing it?

Best regards,

Niels
 

Offline SteveH

Re: Problem upgrading to OS4.1 update 1
« Reply #7 on: July 12, 2021, 04:14:37 PM »
Maybe it would be good if you made a complete backup of the backup partition before you reformat it, then you could compare e.g. with DirDiff afterwards so we might get a clue which file(s) were causing it?
An excellent suggestion - I will do that.
Thanks,
Steve