Login
Username:

Password:

Remember me



Lost Password?

Register now!
Main Menu
Who's Online
1 user(s) are online (1 user(s) are browsing Forum)

Members: 0
Guests: 1

more...
   All Posts (DizzyOfCRN)


(1) 2 3 4 ... 101 »


Re: Waiting for bootable media

Joined:
2008/2/5 6:58
From Sunny Finland
Group:
Member
Posts: 1006
Offline
Quote:

Kalamatee wrote:
The problem is not that the timeout values are too short, it is that AROS does not wake the devices when they are put in a low power state.

Sure, making the timeouts larger might alleviate the issue a little, however at some point the devices will still get powered down unless you are using them constantly - And will not be usable again until the machine is reset (note: just restarting AROS will not bring them back to life).

I also have not encountered a situation where this occurs until you have atleast reached the desktop environment (e.g. Wanderer) - So I would suspect something else is amiss, perhaps the SATA controller is not AHCI compliant.

You would be best to boot AROS to the early startup menu (add bootmenu to the boot command line) and check if the devices are listed at all.

Edit:

There are also issues with some CD/DVD Writers where the device is not exposed as the type AROS expects (they act more like hard drives), and so it does not try the correct filesystems on them. This does show the symptoms you experience, since after loading the kernel AROS no longer then sees the media as bootable.

On one laptop that I tried AROS on the system most of the time booted just fine. This may be because AROS boots quite fast now. (Didn't it use to wait on the SATA driver just a bit too long? Some port scans or something?)

Trouble started when AROS entered Wanderer. There I had to press "cancel" or "retry" on system notice when accessing the HD. With those timeout values changed this stopped.

When the system informed to retry or cancel the iorequest the HD did wake up, but it was a bit messy way to access the HD.

The behaviour may depend on the motherboard/chipset/BIOS/drives firmware and what not if the HD wakes up or not.

Ofcourse there may be some other problems with the system not booting, like bad installation or something.

Posted on: 10/12 4:20
Transfer the post to other applications Transfer


Re: Waiting for bootable media

Joined:
2008/2/5 6:58
From Sunny Finland
Group:
Member
Posts: 1006
Offline
Quote:

origami wrote:
Is your BIOS able to use legacy/IDE mode ?

If so, then write down your original BIOS-settings (so that you are able to revert back), change into IDE legacy mode and try again. Try that with a cold-start.

In case it is related to your cd-rom/dvd-rom drive spinning down directly after boot then i'm afraid the only way to solve that is by booting AROS from USB pendrive.

I had an issue with the SATA drive going to "sleep" (drive could not spin fast enough before AROS driver timeouts ran to zero) I bumped one timeout up a little bit and don't remember who bumped up some other timeout value. (Schulz?) These were done on the ABIV1, I don't know if these values are back ported. For me it did a huge difference.

It might be that AROS fails on certain SATA drives/controllers just because the timeouts are a bit too low. There's no penalty for waiting just a little bit longer. If it fails then it fails, but if it works with relaxed timeout then at least it's some what usable.

Posted on: 10/10 4:26
Transfer the post to other applications Transfer


Re: Waiting for bootable media

Joined:
2008/2/5 6:58
From Sunny Finland
Group:
Member
Posts: 1006
Offline
AROS uses the grub2 bootloader, it will load the kernel and what else but when the computer leaves the grub environment then everything has to be handled by AROS code.

From one lspci listing from the net I see that the zenbook has SATA-controller. SATA driver may or may not work perfectly on AROS.

If there is an option on BIOS to use legacy ide mode on the sata controller then try that.

It doesn't mean much if AROS is able to load it's modules from CD/DVD rom these are handed to AROS by the boot loader (grub2)

If the please insert bootable disk appears then it means AROS wasn't able to find any device it can boot from.

Note for the lspci listing: https://forums.gentoo.org/viewtopic-t-1046070-start-0.html

Posted on: 10/10 4:10
Transfer the post to other applications Transfer


Re: State of AROS Drivers

Joined:
2008/2/5 6:58
From Sunny Finland
Group:
Member
Posts: 1006
Offline
I think that there is a bug at compiler/includes/devices/usb_hub.h with the definition of UHCS_THINK_TIME and UHCF_THINK_TIME(_xx)

These seem to start from bit 13, but from http://sdphca.ucsd.edu/lab_equip_manuals/usb_20.pdf page 417 wHubCharacteristics has them in bits 5 to 6. Is it from endian conversion?

hub.class.c uses it on line 870 with psdSetAttrs(PGA_DEVICE, nch->nch_Device, DA_HubThinkTime, (nch->nch_HubAttr & UHCM_THINK_TIME)>>UHCS_THINK_TIME, TAG_END);

and nch->nch_HubAttr = AROS_WORD2LE(uhd->wHubCharacteristics);

Could ncafferkey or someone else take a look at it? At the moment I can't install AROS natively.

Posted on: 10/2 0:30
Transfer the post to other applications Transfer


Re: lsusb -> "Please use c:loadresource"

Joined:
2008/2/5 6:58
From Sunny Finland
Group:
Member
Posts: 1006
Offline
Quote:

jeffrey1138 wrote:
Hi

Sorry to resurrect an old thread but do you still have the source for the PS3eye.class as it would be a shame to lose it as an example of what can be done or possible?

Might also be fun to see what it can do.

Jeff


I placed a work in progress Zune gui app in rom/usb/guiapps/ps3eye as a Poseidon usb stack usage example. I was hoping that the more there is examples then the easier it would be for someone interested to start fiddling with usb on AROS. Not everyone liked that I put it in there. It doesn't show any video output, but it can take the ps3eye camera and grap it for it's own use and if you start another instance of ps3eye then that can take another camera.

I have the complete datasheet for the bridge chip used in ps3eye on my harddisk but that's on the shelf.

https://youtu.be/XCANfVh5FIY

Remove the usbaudio.class from Trident or else AROS will hang as it also wants to grab the camera device as it has a microphone, but there's really no isoc-transfers present on AROS usb drivers.

Posted on: 10/1 21:22

Edited by DizzyOfCRN on 2017/10/1 21:42:49
Transfer the post to other applications Transfer


Re: State of AROS Drivers

Joined:
2008/2/5 6:58
From Sunny Finland
Group:
Member
Posts: 1006
Offline
Just tested the VUSBHCI driver and it still builds ok.

These are the steps needed to get hosted usb "working"

1. build the hosted version of AROS (It now needs to be build with --enable_usb30_code)
2. cd into the build directory
3. issue make kernel-usb (if it doesn't build everything then just make the rest)
4. issue make kernel-usb-vusbhci
5. issue make kernel-fs-fat (if intending to use fat usb sticks)
6. issue make kernel-partition (otherwise AROS will crash as it tries to use the partition.library, bug? it should know it hasn't opened it)
7. issue make kernel-usb-classes-hubss

My Linux distribution doesn't allow user to access usb devices, so I made a rule in /etc/udev/rules.d

# Allow user to access all usb devices
SUBSYSTEMS=="usb", \
MODE:="0666"

And saved it as "49-all-usb-devices.rules"

Start hosted AROS and go to prefs and open Trident.
Go to "Controllers" and press "New" and select "vusbhci.device" as unit number 0. press "Online" and press "Save"
Go again to "Controllers" and press "New" and select "vusbhci.device", as unit number 1. press "Online" and press "Save"

Unit 0 is now USB2 roothub and unit 1 is USB3 roothub. (hardcoded, I think that the order isn't significant)

Trident needs to be opened everytime you boot into the hosted version of AROS. There's no usbrombootstrap for the hosted version so Trident is used to setup the USB stack.

VUSBHCI.device depends on libusb so it will need the includes for it on Linux side (libusb-dev or something...)

VUSBHCI may output a lot of debug messages at the moment (I haven't looked it up at this point) Those go of course to the console if started from it.

VUSBHCI just means (V)irtual (USB) (H)ost (C)ontroller (I)nterface

There's only one virtual port per virtual host controller (usb2/usb3 (usb3 not implemented yeat)) AROS will see the usb device when Trident is started and the device plugged in after. AROS can't take a device already plugged in as the driver uses libusb's plug in event. Linux has already enumerated and reset the device so a bit of hackery is needed on AROS side. VUSHCI driver will not reset the device nor issue it a new address. Otherwise it would confuse Linux. AROS will then own the device and use it as it will.

If one wishes to start coding for the USB3 (vusbhci.device now doesn't build without it) then AROS build needs to be configured with the "--enable-usb30-code" switch. This will alter the Poseidon USB stack quite a bit to be USB3 aware. There's a lot of work to do to make sure it's solid.

Posted on: 9/28 4:23

Edited by DizzyOfCRN on 2017/9/28 4:44:09
Edited by DizzyOfCRN on 2017/9/28 4:45:19
Edited by DizzyOfCRN on 2017/9/28 4:59:04
Edited by DizzyOfCRN on 2017/9/28 5:14:36
Edited by DizzyOfCRN on 2017/10/1 3:45:02
Edited by DizzyOfCRN on 2017/10/1 3:45:45
Edited by DizzyOfCRN on 2017/10/1 3:47:48
Transfer the post to other applications Transfer


Re: State of AROS Drivers

Joined:
2008/2/5 6:58
From Sunny Finland
Group:
Member
Posts: 1006
Offline
I've taken a closer look at the XHCI driver and it seems there's some more work to do than I remembered...

The driver needs to present two units per controller if the XHCI has both usb3 and usb2 ports. That's because we need to give Poseidon the correct roothub (hub or hubss) and one driver unit can only present one roothub per unit.

There's already code present int the VUSBHCI to sort of implement this but there's no code for the usb3 part.

Higher level usb3 code can be coded with the VUSBHCI driver even before we have a native XHCI driver via the said hosted driver.

Posted on: 9/26 21:35
Transfer the post to other applications Transfer


Re: State of AROS Drivers

Joined:
2008/2/5 6:58
From Sunny Finland
Group:
Member
Posts: 1006
Offline
Quote:

ncafferkey wrote:
@DizzyOfCRN

In the case of my Gigabyte board, the EHCI controller can't be seen in the list of PCI devices under either AROS or Ubuntu. I presume it can't be used in that case.

Is it just AROS or does it show up with other OS'es?

It might be that there's only an XHCI controller on your MB.

Oh... I should have read better. :)

The function BOOL PCIXHCI_FindPorts(struct PCIXHCIUnit *unit) from pcixhci_controller.c should be able to detect the usb3.0 and usb2.0 ports from the XHCI controller. I've only tested it with my setup, but it seems to work...

I don't think that there's a lot of work involved in getting the XHCI driver to somewhat operational state.

Jason back then suggested to use his sata driver's slab memory allocator. Memory allocations are bad in XHCI. That is one issue.

We don't need PCI-X interrupts, I coded the init routine such that it uses PCI INT (event handler 0 only) With PCI-X other event rings can also be used.

Then there's the removal of huge switch statement and adding all the usb3 commands (not all of them are needed at start) and coding the hubss.class to use them.

Also the hardware ring buffers need to be implemented correctly.

One benefit would be that we should get ISOC transfers as the XHCI takes care of lining them up and there's no need to make an scheduler for the different packets.

Posted on: 9/26 20:43

Edited by DizzyOfCRN on 2017/9/26 21:07:36
Transfer the post to other applications Transfer


Re: State of AROS Drivers

Joined:
2008/2/5 6:58
From Sunny Finland
Group:
Member
Posts: 1006
Offline
Quote:

ncafferkey wrote:
Quote:

ntromans wrote:
On the Gigabyte board nothing works - not USB 1, 2 or 3. Neil has the same board and confirms AROS simply cannot use the onboard USB at all. On the Acer, to be fair, a memory stick can be opened - but when accessing its contents the machine quickly crashes so that's not too useable either.


Yes, the two similar Gigabyte boards that Nigel and I have are essentially XHCI-only. They do have EHCI controllers onboard (at least mine does) but the BIOS doesn't make them available in any configuration. I've filed a bug report with Gigabyte about this and they say they may fix it in a future BIOS version, but I'm not holding my breath!

I faintly recall that on some motherboards the order in which XHCI and USB2 hosts are brought online is important, can't remember the details. We would need a working XHCI driver in order for those motherboards to be able to use USB2 host controller.

This is also true for the older host controllers, e.g. EHCI versus UHCHI/OHCI. EHCI has to have it's companion controller on corresponding PCI slot otherwise it doesn't know which port is it's companion port and can't release it's port (well it can but it needs to know beforehand if that port has a companion port...). On poseidon there's just one PCIUSB driver and all those hosts are on a single driver and some quirks are used for the port forwarding but they doesn't need to be on the same driver. The chipset is able to detect when a port is released and the companion host controller will automaticly take over the port.

In the early days when XHCI came out there was a lot of confusion why USB2 doesn't work out of the box on some machines. There's a lot of talk of it online.

https://superuser.com/questions/480045 ... ing-xhci-pre-boot-mode-do

https://www.tonymacx86.com/threads/usb ... plained.57694/#post372656

Take a look in here from page 227 onwards:
https://www.intel.com/content/dam/www/ ... er-interface-usb-xhci.pdf

The current AROS XHCI driver code can find the USB3 and USB2 ports from the host controller and create a port list for them as well corresponding roothubs.

On some motherboards the XHCI might only have USB3 ports on it's controller and a real EHCI chip and the usb data lines are directed via a digital MUX.

Posted on: 9/25 23:06

Edited by DizzyOfCRN on 2017/9/25 23:29:55
Edited by DizzyOfCRN on 2017/9/25 23:31:22
Edited by DizzyOfCRN on 2017/9/25 23:58:27
Edited by DizzyOfCRN on 2017/9/26 0:04:10
Transfer the post to other applications Transfer


Re: State of AROS Drivers

Joined:
2008/2/5 6:58
From Sunny Finland
Group:
Member
Posts: 1006
Offline
Quote:

clusteruk wrote:
DizzyOfCRN

So if you had an Aros machine you would have time to work on some areas?

If so please PM me.

Steve

What I lack is time and at the moment I have so much other things to do. I really don't have any spare time left. Wife and three kids keeps me quite busy.

I've also switched to a newer Linux distro and all of my AROS tools and scripts are on the shelf with the hard drive.

Native driver development is difficult and time consuming. I think I used to burn CD's every time I tested the thing...? Can't really remember. I think now I could use hosted AROS to write new driver on a bootable USB stick with AROS installed on it.

Posted on: 9/22 6:39
Transfer the post to other applications Transfer



 Top
(1) 2 3 4 ... 101 »




Search
Top Posters
1 paolone
paolone
4364
2 magorium
magorium
4095
3 phoenixkonsole
phoenixkonsole
3892
4 nikolaos
nikolaos
3694
5 deadwood
deadwood
2923
6 ncafferkey
ncafferkey
2648
7 mazze
mazze
2214
8 clusteruk
clusteruk
2111
9 Kalamatee
Kalamatee
2024
10 damocles
damocles
1789
© 2004-2017 AROS Exec