USBCtrl fails

A forum for general AmigaOS 4.x support questions that are not platform-specific

Re: USBCtrl fails

Postby Moxee » Sat Sep 17, 2011 4:48 am

mechanic wrote:For Up3 are you un-checking the box on the last install screen before clicking 'Finalize' ?


Yes. I read that in one of Roy Leith's postings. I never heard why that should be so since Hyperion's instructions say otherwise.
_______________
Moxee
- AmigaOne XE G4 (Early Bird Model)
User avatar
Moxee
 
Posts: 23
Joined: Mon Sep 12, 2011 2:28 am
Location: NW USA

Re: USBCtrl fails

Postby Moxee » Sat Sep 17, 2011 5:18 am

tonyw wrote:You should always have the CD set as "Boot1" in U-Boot. Then "Boot2" and "Boot3" can be your on-board and SiI devices.


Yes, my UBoot has always been set that way.

Bear in mind that as soon as you go into U-Boot menu, it clears Boot2 and Boot3.


I wonder why that is.

It's safer to use "nvgetvar/nvsetvar" to change U-Boot parameters - you can do that from the Shell on the CD.


I've never used those before. nvgetvar reported this:
boot1=ssii
boot2=cdrom
boot3=
boot4=floppy

I've changed it to read:
boot1=cdrom
boot2=ssii
boot3=ide
boot3=floppy

My UBoot Prefs always was set with cdrom as boot1. Plus every time I opened UBoot it read boot1=cdrom, so I don't understand why nvgetvar would report different settings.

OK, now I've got a booting system again, but it is still booting into the same old original problem. Well, at least it is booting. I'll recheck the priorities again, but tomorrow. It is time for sleeping now.
_______________
Moxee
- AmigaOne XE G4 (Early Bird Model)
User avatar
Moxee
 
Posts: 23
Joined: Mon Sep 12, 2011 2:28 am
Location: NW USA

Re: USBCtrl fails

Postby Noel Fuller » Sun Sep 18, 2011 10:22 am

After installing update 3 on the SAM 460ex harddrive I thought to boot update 2 from
the original USB card plugged in , when I want, to the port on the mobo. I also wanted
to check out this failure to initiate USB that I got whenever I had a stick planted in a
USB port. OK the machine booted fine from the card but came up with the same message
moxee got. Seemed like update 2 was no longer viable. I installed update 3 on the USB
card and that problem disappeared, but that is avoiding the issue rather than resolving it.

Noel
User avatar
Noel Fuller
Beta Tester
Beta Tester
 
Posts: 13
Joined: Wed Aug 31, 2011 10:07 pm

Re: USBCtrl fails

Postby Rigo » Sun Sep 18, 2011 12:07 pm

Installed systems MUST match between kickstart and the system files.

Booting Update 2 kickstart and Update 3 files (or any other combination) is never going to work, for reasons that are becoming apparent.

If you have multiple boot sources, check to make sure that everything has been installed correctly.

A "version usbsys.device" in a shell should produce a number which matches that of USBCtrl in the C: assign. This proves that the kickstart being loaded matches the booted system files.

Simon
User avatar
Rigo
AmigaOS Core Developer
AmigaOS Core Developer
 
Posts: 339
Joined: Mon Jan 17, 2011 10:42 pm

Re: USBCtrl fails

Postby Moxee » Sun Sep 18, 2011 8:07 pm

Hi Simon,

Rigo wrote:Installed systems MUST match between kickstart and the system files.

Booting Update 2 kickstart and Update 3 files (or any other combination) is never going to work, for reasons that are becoming apparent.

If you have multiple boot sources, check to make sure that everything has been installed correctly.


We all know that mine are mis-matched. I am loading an old kickstart along with Update 3. I just don't know why and how to correct it.

I thank everyone here for trying to help me, but apparently this is my problem and I'll have to figure it out alone since none of the suggestions are helping. I have re-installed again and again to old partitions and new partitions, removed other bootable partitions, followed the instructions down to a T, all to no avail.

Right now I think my only solution is to disconnect my old HDs and install a new HD for Update 3. I am in amazing good spirits for all this frustration, but I am tiring of the attempts.

Something which has me perplexed is the Update 3 Docs which states:
Please note that the main archive (which this file resides in) does not carry any USB hardware drivers (HCDs). You will need to download an archive holding a HCD for your USB hardware separately. The HCD must be copied into the "Kickstart" or "DEVS:USB/hcd" drawer.

Where are these hardware drivers downloaded from, the manufacturers?

A "version usbsys.device" in a shell should produce a number which matches that of USBCtrl in the C: assign. This proves that the kickstart being loaded matches the booted system files.


I have:
usbsys.device 53.6
USBCtrl 53.11

A new empty HD installed and the other HDs disconnected should get me a good working installation of Update 3. Then I'll clean the OS from the two original HDs, make just one OS backup, and use the rest for non-bootable purposes. Do you see any problems with that?
_______________
Moxee
- AmigaOne XE G4 (Early Bird Model)
User avatar
Moxee
 
Posts: 23
Joined: Mon Sep 12, 2011 2:28 am
Location: NW USA

Re: USBCtrl fails

Postby mechanic » Mon Sep 19, 2011 2:48 pm

Bootmouse and Bootkbd are used before the USB stack is booted.

Loading the HID stuff before the stack start is useless, and
the stack is started in S:Startup-Sequence after IPrefs.

Make sure BootMouse and Bootkeyboard are active in Kicklayout
first, then .........
Try this experiment. Put a semicolon (;) before the line
'C:USBCtrl START' in Startup-Sequence,and reboot either soft,
Ctrl+Alt+Alt, or hard.

Then look in RAM:T. You should NOT have a usb.log file.
Now open a shell and enter 'usbctrl start', check RAM:T
again and you will see that Bootmouse/Kbd are being pre empted.
Thats because (in other words) the HID drivers have taken over
and consider Bootmouse/kbd unsuitable.

Remove the semicolon.

I also had problems with my wireless mouse until moving it to
one specific front port.

As for USBCtrl Restart, it fails unless the ONLY devices I'm
using are mouse and keyboard. Still looking for this bugger.
A-Eon A1X1000
User avatar
mechanic
 
Posts: 496
Joined: Sat Jun 25, 2011 10:22 pm

Re: USBCtrl fails

Postby mechanic » Mon Sep 19, 2011 6:37 pm

Here is some other things I have noticed.

To get to the Early Start Menu.

If you have a optical wired mouse. Turn it over so you can see
the light. Reset the computer, then watch and see when the light
comes on. Mine turns on USB power just before the Splash screen.
So holding down buttons/keys until the port is active may not be
the workable way to get to Early Start Menu.

Some mice/keyboards, especially wireless, seem to not send the
first click/keystroke, in which case rapid clicking of both mouse
buttons, or more easily, tapping on the Scroll Lock key may get
the desired results instead of simply holding them down constant.

Note:
Another thing about the USB stack.
If you look at the log just after the first start and then do a
'usbctrl restart' you'll notice on the restart Bootmouse and
Bootkeyboard do not show during the restart phase because they
are only started as a kickstart module. I think thats right?
A-Eon A1X1000
User avatar
mechanic
 
Posts: 496
Joined: Sat Jun 25, 2011 10:22 pm

Re: USBCtrl fails

Postby Moxee » Tue Sep 20, 2011 2:04 am

mechanic wrote:Bootmouse and Bootkbd are used before the USB stack is booted.

Loading the HID stuff before the stack start is useless, and
the stack is started in S:Startup-Sequence after IPrefs.

Make sure BootMouse and Bootkeyboard are active in Kicklayout
first, then .........
Try this experiment. Put a semicolon (;) before the line
'C:USBCtrl START' in Startup-Sequence,and reboot either soft,
Ctrl+Alt+Alt, or hard.

Then look in RAM:T. You should NOT have a usb.log file.


If you are talking to me, then everything is true up to this point.

Now open a shell and enter 'usbctrl start', check RAM:T
again and you will see that Bootmouse/Kbd are being pre empted.
Thats because (in other words) the HID drivers have taken over
and consider Bootmouse/kbd unsuitable.


This is not happening here because "USBCtrl START still brings up that same Error Message: "USBCtrl only works with USB Stack v53.11"

My problem is that an old version of Kickstart is being loaded and I don't know how to solve it. I figured that I would start all over fresh and installed a new Sata HD today and disconnected the old Sata drive and the two Pata drives. I installed OS4.1 Update 1 on it. Don't you know that this drive would not boot Update 1 unless I reconnected the two Pata drives. I don't know what is going on here, but I am about to call it a day because nothing is working and I am still right back to where I was in the beginning.

Who needs USB? I guess I'll have to get along without it.

Remove the semicolon.


I think I will leave it in so I don't get the delay of that Error Message. Who needs USB?
_______________
Moxee
- AmigaOne XE G4 (Early Bird Model)
User avatar
Moxee
 
Posts: 23
Joined: Mon Sep 12, 2011 2:28 am
Location: NW USA

Re: USBCtrl fails

Postby mechanic » Tue Sep 20, 2011 5:28 pm

@Moxee

I can't help with the SATA. It seems that booting from there would
be a UBoot setting. If the other drives have System drawers on them
it could cause confusion as to where SYS:System is. You may want to
check with someone else first, but if you are sure it is booting off
of the SATA (with the PATA drives installed) then try renaming the
System drawers on the PATA drives to OLDSystem, OLD2System or something
and do the installs on the SATA. If Uboot is looking at the PATA drives
first then maybe it is picking one of those regardless of the boot
priority of the SATA drive, maybe.?????

You might have to set the drives your not booting from as not bootable
with Media Toolbox.

I looked around on the updates and for usbsys.device.......
OS4.1----52.11
Up1 -----53.6
Up2 -----None
Up3 -----53.11

So if you have the Up1 installed and booting from SATA just leave
USBCtrl START commented out and continue with the updates. If when
you have installed all 3 USBCtrl START is still giving problems then
start checking version numbers on Kickstart/usbsys.device. You may have
to copy over from Up3 the USB stuff.

Phew! Hope that helps.
A-Eon A1X1000
User avatar
mechanic
 
Posts: 496
Joined: Sat Jun 25, 2011 10:22 pm

Re: USBCtrl fails

Postby Moxee » Tue Sep 20, 2011 9:01 pm

mechanic wrote:I can't help with the SATA. It seems that booting from there would
be a UBoot setting. If the other drives have System drawers on them
it could cause confusion as to where SYS:System is.


Seems possible.

You may want to
check with someone else first, but if you are sure it is booting off
of the SATA (with the PATA drives installed)


I am not sure of anything any more. I made my first Update 3 install on my original SATA drive and after re-booting it printed out this at the top of the screen: "Amiga Operating System Release 4.1 - Update 3". It is just that something is forcing the use of an old Kickstart from a PATA drive to get there. That is why I disconnected the PATA drives and installed a new SATA drive. Figuring that with only one bootable drive the Update 1, 2, and 3 would go flawlessly. Then without the PATA drives installed the new SATA drive won't boot into OS4.1 Update 1. Leaving this new SATA drive in and re-installing the PATA drives boots up a copy of Update 3 on the PATA, but using Kickstart from Update 1. Crazy! Using the original SATA drive, it would boot up Update 3 from the SATA using the Update 1 Kickstart.

then try renaming the
System drawers on the PATA drives to OLDSystem, OLD2System or something
and do the installs on the SATA.


I'll try that next.

If Uboot is looking at the PATA drives
first then maybe it is picking one of those regardless of the boot
priority of the SATA drive, maybe.?????


I'd say that is exactly what is happening. But what could make it insist on a PATA drive when they are disconnected? I've even tried taking the PATA out of UBoot using the nvsetvar and also tried that using the Prefs/UBoot. It is almost like something is wrong with my UBoot.

You might have to set the drives your not booting from as not bootable
with Media Toolbox.


Oh God no! I tried that already and got a complete non booting system reporting that all the SLBs were missing from all HDs.

I looked around on the updates and for usbsys.device.......
OS4.1----52.11
Up1 -----53.6
Up2 -----None
Up3 -----53.11

So if you have the Up1 installed and booting from SATA just leave
USBCtrl START commented out and continue with the updates. If when
you have installed all 3 USBCtrl START is still giving problems then
start checking version numbers on Kickstart/usbsys.device. You may have
to copy over from Up3 the USB stuff.

Phew! Hope that helps.


Sorry, but Update 1 on the new SATA drive will not boot with it being the only HD connected. So I reconnected the PATA drives to see what would happen. Update 3 booted. So, right now I believe it is booting up a backup of Update 3 from the PATA, but still using the same old Update 1 Kickstart files. I am so confused now I am not even sure what is happening.

I am going to try your idea of renaming the drawers on the PATA drives to see if that works. I can't do it until tomorrow though because I am busy outside trying to finish painting the exterior of my buildings while it is still warm enough to do to.

I'd like to make the PATA partitions unbootable, but not after what happened the first time. Removing the PATA drives from the equation by disconnection should also have worked, but it didn't.

I do have a ghost in my house having died only 4 feet from my AmigaOne, but he doesn't do harmful things.
_______________
Moxee
- AmigaOne XE G4 (Early Bird Model)
User avatar
Moxee
 
Posts: 23
Joined: Mon Sep 12, 2011 2:28 am
Location: NW USA

PreviousNext

Return to General AmigaOS

Who is online

Users browsing this forum: No registered users and 4 guests