Browsing this Thread:
1 Anonymous Users
|
Re: AROS64 USB storage device
|
||||
|---|---|---|---|---|
|
Home away from home
 
|
Thanks Dizzy. That is great news :)
Posted on: 2018/4/20 12:28
|
|||
|
www.aspireos.com
|
||||
|
||||
|
Re: AROS64 USB storage device
|
||||
|---|---|---|---|---|
|
Home away from home
|
@Dizzy
Great News! Keep up the good work! 
Posted on: 2018/4/20 12:23
|
|||
|
||||
|
Re: AROS64 USB storage device
|
||||
|---|---|---|---|---|
|
Home away from home
|
Managed to get the vusbhci.device working on 64-bit linux and hosted AROS
https://youtu.be/BsEUUgSfAK0 It might be that our other drivers aren't 64-bit friendly or there is some other problem as Poseidon is happy on 64-bit hosted. (not tested much though)
Posted on: 2018/4/20 10:41
|
|||
|
Jyrki.J.Koivisto
|
||||
|
||||
|
Re: AROS64 USB storage device
|
||||
|---|---|---|---|---|
|
Home away from home
|
Well, this is interesting...
I littered do_libusb_ctrl_transfer(struct IOUsbHWReq *ioreq) with debug statements and suddenly it started to work again... (some devices that don't bind with anything are recognized, some are not) Something is asking the device something before it is ready to answer... This might be one reason why the usb stack works for someone and not for the other. EDIT: Doing this request takes a very long time to complete [VUSBHCI2.00] do_libusb_ctrl_transfer: ioreq->iouh_SetupData.bmRequestType 80 [VUSBHCI2.00] do_libusb_ctrl_transfer: ioreq->iouh_SetupData.bRequest 6 [VUSBHCI2.00] do_libusb_ctrl_transfer: ioreq->iouh_SetupData.wValue 301 [VUSBHCI2.00] do_libusb_ctrl_transfer: ioreq->iouh_SetupData.wIndex 409 [VUSBHCI2.00] do_libusb_ctrl_transfer: ioreq->iouh_SetupData.wLength 2 [VUSBHCI2.00] do_libusb_ctrl_transfer: ioreq->iouh_Length 2 [VUSBHCI2.00] do_libusb_ctrl_transfer: Done! This would be the get descriptor request for language id or something from the top of my head... EDIT: This might just be a problem on my setup and the vusbhci.device that's the culprit. Don't really remember where I left it... EDIT: I remember doing something to the vusbhci.device how it handles usb2.0 and usb3.0 devices plugged into usb2.0 host or usb3.0 host, maybe my problems are due to just that. EDIT: My hosted AROS build is based upon ABIv1 as is the AROS 64-bit (If I have understod it correctly... :) ) and my Linux distribution is also 64-bit. That's the relevance with Nikolaos problems and mine. EDIT: Poseidon is really anal about the debugs, too much and it won't work and too little seems to be the same. Something ain't right with it...
Posted on: 2018/4/17 11:18
Edited by DizzyOfCRN on 2018/4/17 12:16:42
Edited by DizzyOfCRN on 2018/4/17 13:11:49 Edited by DizzyOfCRN on 2018/4/17 17:19:50 Edited by DizzyOfCRN on 2018/4/17 17:25:07 Edited by DizzyOfCRN on 2018/4/17 17:30:58 Edited by DizzyOfCRN on 2018/4/17 17:41:27 |
|||
|
Jyrki.J.Koivisto
|
||||
|
||||
|
Re: AROS64 USB storage device
|
||||
|---|---|---|---|---|
|
Home away from home
|
Just managed to compile the hosted version of AROS on my Fedora 27 installation. Had to make an older version of gcc and compile AROS hosted with that. AROS build system doesn't like the gcc 7.3.0 as bundled with Fedora 27 or vice versa...
massstorage.class doesn't work with my hosted build and vusbhci.device either anymore... Something has changed... I tried a fat formatted usb drive and it seems to hang right after filtering out setaddress. Those devices that don't bind with any classes are recognized and AROS does not hang.
Posted on: 2018/4/17 10:42
|
|||
|
||||
|
AROS64 USB storage device
|
||||
|---|---|---|---|---|
|
Home away from home
|
AROS64 boots fine from live CD on my Aspire 57342 laptop but after installation to USB storage device I get black screen.
I see grub and select screenmode and I see some debug but after that nothing. I tried many different screenmodes and the same.
Posted on: 2018/4/15 16:11
|
|||
|
www.aspireos.com
|
||||
|
||||
You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.
You cannot use topic type.
You cannot use HTML syntax.
You cannot use signature.
You cannot create PDF files.
You cannot get print page.
