Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - mike

Pages: 1 [2] 3
16
Storage / Re: oddities with OS2AHCI version 2.04
« on: January 01, 2018, 08:26:07 pm »
That is interesting, could you please ask them to give us some information.  I have not been able to do that on boards with the X370 chipset, the B350 chipset and the A320 chipset using both a Ryzen 7 and Ryzen 5 CPU.  Even an A12 APU with those chipsets is problematic.
I will try to find out.. Also don't forget that with Ryzen some ports are severed directly by the integrated chipset from the CPU, with the A12 (Bristol Ridge?) its integrated chipset is disabled when used together with a external chipset like in your case. What means problematic? Write errors?

Quote
Also, any board with as ASMedia chipset for AHCI is a no go.  From that the only conclusion that can be drawn is that there is NO standard unless it is an Intel or Intel supported chipset with our OS2AHCI driver.
This ASMedia ship is not a so called fake raid adapter? There is a standard, just because new hardware doesn't work from the start is another issue, or why work older amd ahci chipsets with no problem?

17
Storage / Re: oddities with OS2AHCI version 2.04
« on: January 01, 2018, 08:14:48 pm »
I cannot find any proof for this claims. In fact the Advanced Host Controller Interface is a specification by Intel.
It is true that Intel introduced this AHCI specification but its a general standard like most interface specifications.

Quote
The OS2AHCI adapter device driver is based on older code from Linux or BSD. There has never been a certification process (that would fail) at all.
If I'm not mistaken then the core driver was ported around 2012, BSD code.  A "funny" thing is when we still need to bother with AHCI but should already move to NVMe.  Somebody has an open ticket at AN for a non working AHCI driver on a current system? What is not working, the initialization ?  Lars should open a ticket for his issue anyway.

18
Storage / Re: oddities with OS2AHCI version 2.04
« on: January 01, 2018, 03:34:03 pm »
It is almost as if testing on AMD systems is an afterthought or what units they use for testing are old ones (I would like to get ArcaOS working on my Ryzen 8 core system or even the A12 APU system but...) since it apparently works on Intel's latest and greatest.

It should not matter if the system is amd or intel based, as the SATA AHCI interface is a standard and the os2ahci driver should support the hardware. The Bulldozer and not latest Core I7 CPU have a chipset that contains the controller, and not the CPU itself.
Not sure how, but some people got a "OS/2" to work on a Ryzen based system.

19
Programming / Re: os4: KEE update notification
« on: May 21, 2017, 05:40:01 pm »
Another benefit of a new kernel is also to avoid to add patches to PSDs, drivers and other places to fix or add workarounds to the kernel but adding new functions and fixes to the krnl itself, which is the right place. When i remember correctly its only possible to load one psd so 'every' psd in use need to add this code to provide it to old krnl based systems,

20
Applications / Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
« on: February 23, 2016, 08:30:09 pm »
Just for fun I created a.o. replacements of bkscalls.dll and kbdcalls.dll with source code.

Wim = hero  ;)
Has this some relation to the console API?

21
General Discussion / Re: News from the front line
« on: July 09, 2015, 11:22:09 pm »

.. but I also noticed a boycott campaign by someone calling OS/2 community members one by one to tell to do not help XEU at all.

That really throws some light to some phone calls I had, thanks for this information, Martin!

Interesting fact that people got mad to do something like this... unpaid people from the old company? In general people should decide on their  own. XEU was announced over a year now. Not much has happened since..  XEU needs new updates for eCS or they will just try to sell what they just have - the time will tell.


22
Hardware / Re: Webcam Support for OS/2 and eCS!!
« on: August 17, 2014, 06:27:43 pm »

I created rxusb.dll in order to be able test my usbcalls.dll and usbresmg.sys device driver.

It appears that your installation does not use my usbresmg.sys driver. You have to recheck your config.sys file again to see what file the device driver statement points to and to verify that it is my usbresmg.sys driver.


After working around this issue and with the latest release of usbresmgr/webview my cam now works in one mode.  Again thanks for the hard work making this possible !

mike

23
Hardware / Re: Webcam Support for OS/2 and eCS!!
« on: July 20, 2014, 10:39:25 pm »

Unfortunately USB Device Monitor Version 0.9.7 cannot be used because it provides incorrect and incomplete data. So I wrote my own :) uvc webcam compound descriptor retrieval utility in rexx. Download http://home.hccnet.nl/w.m.brul/uvcvideo/uvcprobe.zip and run uvcprobe.cmd and it will create uvcprobe.bin containing the descriptors.

It would be nice when this or any other tool could be fixed to make it usable again. Now it gets interesting, because its nice that REXX is in place now :) Getting the data however seems to be a hard task.. I get the following output when running the tool:

C:\TOOLS\USBCAM\RXUSB.DLL
Found 3 usb devices.
FFEA UsbGetDeviceReport failure!



24
Hardware / Re: Webcam Support for OS/2 and eCS!!
« on: July 18, 2014, 08:50:32 pm »

Use the output of lsusb from Paul Smedley for your camera.

https://dl.dropboxusercontent.com/u/76425158/lsusb-20130526.zip

1. when I typed lsusb I got

Bus 001 Device 001: ID 046d:0804 Logitech, Inc. Webcam C250

2. When I typed lsusb -d 046d:0804 -v > 046d0804.txt

I got the descriptors in the created 046d0804.txt file.

lsusb is not working, it seems that it has problems finding/loading the usb.ids file,  the %OS_DIR% var is  not used. lsusb.exe -h works.

Killed by SIGSEGV
pid=0x001b ppid=0x001a tid=0x0001 slot=0x003b pri=0x0200 mc=0x0001
C:\TOOLS\USB\LSUSB.EXE
LSUSB 0:0000f3b6
cs:eip=005b:0001f3b6      ss:esp=0053:0081ff30      ebp=0081ffa0
 ds=0053      es=0053      fs=150b      gs=150b     efl=00010246
eax=00000000 ebx=ffffffff ecx=ffffffff edx=00000000 edi=00000000 esi=0081ffbc
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.

 I will send the output from the other usb tool, maybe it will tell what is required.

25
Hardware / Re: Webcam Support for OS/2 and eCS!!
« on: July 18, 2014, 11:15:43 am »

It seems that my programs did not find a suitable endpoint descriptor.
Start USBDock /bin and attach your camera's .BIN file for me to inspect.

this system doesn't have the USBDock installed, is there a way to get these data from the USB Monitor tool?



26
Hardware / Re: Webcam Support for OS/2 and eCS!!
« on: July 17, 2014, 10:00:13 pm »
I have replaced WebSeeBeta1.zip on my website :) and updated http://home.hccnet.nl/w.m.brul/uvcvideo/index.html

NOTE: I did not spend time to solve device driver and multiple cpu issues. I first ;) want to iron out these programs.

Thanks for the update. Here  both webview and uncview report a frame size error:

started.
[0104241B]
[0105241E]
YUYV
[00000000]
frame size error.
stopped.

27
Hardware / Re: Webcam Support for OS/2 and eCS!!
« on: July 10, 2014, 10:09:03 pm »

Hi Mike,

Yes, but it is easier for me to work on weblook first because it is a vio program. Mind you, the associated webview program is a pm program. The aim is to move away from usbecd.sys for generic webcam support. See my previous posts in this thread.

Wim.


Helllo Wim,
the generic webcam support sounds good. I could install now all the latest files, made the usbecd.sys  config and then tried  weblock.exe

started.
[0104241B]
[0105242A]
YUYV
[000007F8]
[00000018]
bind: Address not available
[open isochronous]

the cam led is on but webview.exe shows just a black window the same happens with uvcview.exe. Any ideas?

mike


28
Hardware / Re: Webcam Support for OS/2 and eCS!!
« on: July 01, 2014, 10:08:21 pm »
About the webcam access,  doest it mean we can now have a generic pm application that can show the video of the connected usb webcam?

Yes.

hello,
is it possible to recycle the one that was already compiled for different usb cams on your site? What about USBECD.SYS ?



29
Hardware / Re: Webcam Support for OS/2 and eCS!!
« on: June 30, 2014, 09:45:01 pm »

Since October 2013 I have been working on the implementation of isochronous transfers in USB Resource Manager. The current sources are at netlabs in my private branch:

I have produced a (beta test) matched set of usbcalls and usbresmg.sys that is backwards compatible. I have removed old code both in usbresmg.sys and usbcalls.dll for functions that were never properly supported. Existing synchronous transfer functions work well again and I have implemented these as asynchronous too. I have added code for the new asynchronous isochronous transfer functions. I am getting video from my Logitech C250 camera.


These are good news, thanks for the work on it  :)
About the webcam access,  doest it mean we can now have a generic pm application that can show the video of the connected usb webcam?



30
Networking / Re: e1000e driver - test updates
« on: January 26, 2014, 01:29:38 pm »
Hi All,

I've done some updates to the multimac e1000e driver to update the linux kernel version it is based on.

At this time, I have three fourfive test versions available.

To test:
1) backup the existing \ibmcom\mac\e1000e.os2
2) replace with one in the test zips.

URLs for test builds:
http://smedley.id.au/tmp/e1000e-3.4.77.zip
http://smedley.id.au/tmp/e1000e-3.6.11.zip
http://smedley.id.au/tmp/e1000e-3.8.13.zip
http://smedley.id.au/tmp/e1000e-3.10.27.zip
http://smedley.id.au/tmp/e1000e-3.12.8.zip

Note these have been lightly tested on a Thinkpad T60 only.  Lightly tested basically means ensure the machine boots, gets an IP using dhcp, and can connect to a website.

YMMV.

Intent is to try and get this up to the latest kernel code and get the changes included in the multimac source code, and to learn a bit about how multimac works.

Cheers,

Paul.


hello paul,
thanks for the update on the multimac drivers! The lan adapter has the device id of 8086:153A i tried all drivers, esp. the one in e1000e-3.12.8.zip but lantran.log always reports "E1000E No supported hardware was found."

mike




Pages: 1 [2] 3