Opened 10 years ago

Closed 9 years ago

Last modified 3 years ago

#78 closed defect (fixed)

v10.197 does not recognize mass storage (stick)

Reported by: ecs273 Owned by: Lars Erdmann
Priority: major Component: basedrv
Version: 10.197 Keywords: msd stick
Cc:

Description

There is no trap. Inserting stick does nothing. I have one with an access light, it shows nothing. There is nothing shown on the neowps usb widget to eject. There is no beep inserting or pulling out. USB mouse works fine. Using ps2 keyboard.

If I boot with the stick inserted then it works and I can read it. I can eject it normally with neowps widget. But re-insertion does nothing. The stick works normally in other eCS computers. The stick works normally w/ v10.162 drivers.

Running eCS v2.1, kernel 14.105 w/ four cores, acpi 3.22.01. No switches.

snipped config.sys showing usb statements: ========== rem ..DEVICE=C:\OS2\BOOT\USBPRT.SYS DEVICE=C:\ECS\SYSTEM\AMouse\AMOUSE.SYS SMP DEVICE=C:\ECS\SYSTEM\AMouse\USBMOUSE.SYS /V ..<snip>.. rem ..DEVICE=C:\OS2\BOOT\USBKBD.SYS ..<snip>.. REM DEVICE=C:\OS2\BOOT\USBCOM.SYS ..<snip>.. IFS=C:\ECS\BOOT\EVFS.IFS DEVICE=C:\ecs\boot\USBRESMG.SYS /V ..<snip>.. BASEDEV=CHKDSK.SYS BASEDEV=USBOHCD.SYS BASEDEV=USBOHCD.SYS BASEDEV=USBOHCD.SYS BASEDEV=USBOHCD.SYS BASEDEV=USBOHCD.SYS BASEDEV=USBEHCD.SYS BASEDEV=USBEHCD.SYS BASEDEV=USBD.SYS BASEDEV=USBHID.SYS ..<snip>.. REM BASEDEV=IBM2FLPY.ADD BASEDEV=USBMSD.ADD /REMOVABLES:8 /FLOPPIES:1 ========== attaching: usb197-1.txt trace with stick inserted usb197-2.txt trace booted with stick inserted pcirpt.txt = pci -D

The drivers I am using are from files usbhcd197.zip & usbhid197.zip. When I revert to v10.162 I keep the hid197 files installed, reverting only from the 5 drivers in hcd197.

I note that it takes nearly 4x longer to boot w/ 10.162 vs 10.197

Rgds, Jon

Attachments (1)

ecs273.zip (44.2 KB) - added by ecs273 10 years ago.
2 trace files and 1 pci report

Download all attachments as: .zip

Change History (16)

Changed 10 years ago by ecs273

Attachment: ecs273.zip added

2 trace files and 1 pci report

comment:1 Changed 10 years ago by David Azarewicz

I recommend the version 11.05 USB stack. Also, the neowps USB widget is known buggy and is known to cause failure and/or corruption of USB MSD devices. I do not recommend using it.

comment:2 Changed 10 years ago by ecs273

OK, is 11.05 avail only at betazone? I did not renew when my subscription when it expired.

What is the recommended replacement for neoWPS USB widget?

I have gone through the config.sys swapping versions of the drivers. My problem definitely is in usbehcd.sys. With all drivers from 10.197 except using ehcd from 10.162 then the mem stick works.

I also have a new trace in this configuration but I suppose it is not needed until I can get the newer drivers. Correct?

Rgds, jon

comment:3 Changed 10 years ago by David Azarewicz

11.05 is in the betazone not SSS. No subscription is required.

There is no replacement for the USB widget. A fixed version is in the works.

Do not mix versions of the drivers.

No trace is needed. You can also use the 11.06 drivers. They should also work OK on your hardware.

comment:4 Changed 10 years ago by David Azarewicz

Because of all the problems with the USB widget, I remove it from all my systems and put back the old IBM USBMSDD.EXE. It always works. Plus I hate programs that beep.

comment:5 Changed 10 years ago by ecs273

11.06 isn't doing it for me. I also tried after removing the neoWPS widget, in cmd window ran usbmsdd. Plugged in stick and tried refresh removable drive. Nothing.

Then renamed usbshold.dll (not sure about this one but I think it goes with neoWPS). Rebooted, ran in cmd window usbmsdd. Still nothing.

Does usbmsdd take a switch or do I need to run something else with it? I haven't located any info other than placing it in startup folder (I'll try that next but don't see how that is different than opening a cmd window).

I'll try 11.05 on Sunday w/ usbmsdd in startup folder but would appreciate some pointers on usbmsdd in case I'm doing it wrong.

jon

comment:6 Changed 10 years ago by Anchieri

You have to insert in parameters field this data: x:\ecs\boot\usbmsdd.ini where x: is the drive that hold your ecs system. In my eCS 2.2 beta version this is the parameter that is present in object on startup folder

comment:7 Changed 10 years ago by ecs273

None of the suggestions here have worked for me.

In addition to trying v11.06 & v11.05, I have removed my ps2 keyboard and am using usbkbd and removed pscom.sys from config.sys

I removed neoWPS & also made the change Anchieri suggested.

FWIW, booting with the stick inserted works, and I can read & eject it. But it is not recognized if I reinsert it and refresh removable devices.

The only driver that has worked so far is v10.162

Rgds, Jon

comment:8 Changed 10 years ago by Lars Erdmann

Owner: set to Lars Erdmann
Status: newaccepted

Hallo Jon,

I cannot attach anything to this ticket. Please email me directly: lars.erdmann@…

comment:9 Changed 10 years ago by Lars Erdmann

milestone: Future Version
Version: 10.197

comment:10 Changed 10 years ago by David Azarewicz

I have the exact same hardware as you do and I have absolutely no problems with it. I can plug any number of USB devices in and they are all properly recognized every time. I suggest your problem is not with the version 11.xx USB drivers, but is somewhere else.

comment:11 Changed 10 years ago by ecs273

Dave: I'm aware that you have the same HW, except perhaps not 2 nics but I don't see that as a factor here, unless it has to do with IRQ sharing. I don't think all of the usb connectors on the MB are hooked up (I didn't build this unit), I have 4 rear and 2 front. If you think that is important, I can open it up and look around.

I'll email Lars as requested and see what he has to say.

Thanks, Jon

comment:12 Changed 10 years ago by ecs273

I've found a solution to my problem.

The bios configuration was set for USB Legacy = auto. In this mode, if no usb device is detected, it is disabled. Setting this option = on and now my mem sticks are detected as expected.

Why they were detected using driver 10.162 and not any of the later drivers is odd.

Jon

comment:13 Changed 9 years ago by Lars Erdmann

Resolution: fixed
Status: acceptedclosed

comment:14 Changed 9 years ago by Lars Erdmann

fixed by changing BIOS settings

comment:15 Changed 3 years ago by Lars Erdmann

milestone: Future Version

Milestone deleted

Note: See TracTickets for help on using tickets.