OS2World OLD-STATIC-BACKUP Forum
OS/2 - Technical => Setup & Installation => Topic started by: Charl on 2008.08.12, 11:56:25
-
Hi Guys,
I'm struggling with USB support on OS/2 Warp 3. (Mounting a Flash Stick)
(I can't upgrade to Warp 4 or eCom because of other legacy issues)
More on the Lenovo M57:
http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-68844 (http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-68844)
# Q35 North Bridge - Intel 82Q35 Graphics and Memory Controller Hub (GMCH)
# ICH9 South Bridge - 82801IO ICH9DO I/O Controller Hub
Every time I install USBBASIC on the OS the PC hangs on the next reboot.
From the USBBasic.txt:
Universal Serial Bus Base Stack README
December 2, 2005
So I assume this is a relatively new driver.
After executing the USBINST.EXE the following gets added to the bottom of the config.sys:
BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBD.SYS /REQ:USBUHCD$,USBOHCD$,USBEHCD$
BASEDEV=USBHID.SYS
The system hangs just before entering OS/2 GUI.
I've left it on overnight with no luck of it going any further.
HCIMONIT picks up the following:
You have 6 PCI USB UHCI host controller(s)
You have 2 PCI USB EHCI host controller(s)
Any and all help would be greatly appreciated!
Thanks,
Charl
-
Hi Charl,
the first thing I notice is that while you apparently have 6 UHCI controllers, there's "only" 5 USBUHCD drivers in your config.sys... maybe you simply pasted too few lines in the post, also - anyway - I don't think it would cause such problems to have 1 driver too *few* loaded. ;)
My best guess is that you should check if the machines BIOS perhaps has an option to assign IRQs to the USB controllers (are these onboard controllers?). If so, set it to yes. I had experienced problems in the past when trying to run USB in OS/2 using "IRQ-free" options in the BIOS setup.
Next item on my "let's see what happens if..." list would be to make OS/2 boot with the USB stick attached to the port. I don't think it makes a difference as this is usually done to overcome Warp not being able to access the USB drive. Here, the problem is different as the driver does not even load.
I cannot remember if you had to have the absolutely latest Warp3 FP installed for USB to work properly. But I fear that FP35 (or whatever latest one) is required. Can someone else chip in with info regarding requirements for USB in regards of kernel+driver(s) versions?
HTH
Thomas
-
The first thing you need to do is remove the /req: usbuhcd$, usbohcd$, usbehcd$ from the usbd.sys line. According to the Dec. 2005 usbbasic readme that is generally not needed.
Another thing you need to check is that you have the correct idedasd, (from the readme: For Warp 4 and Warp 3 the IDEDASD package from the OS/2 DDPak also should be
applied if installing OS/2 on a hard drive larger than 8.4GB.) and the usbmsd driver.
With the hardware you have I find it strange that you can't use warp4.
As warpcafe says you need the latest fixpack FP40 or FP43 plus at least dd02 otherwise you don't have the chance of a snowball in hell of getting usb working.
-
Hi,
quick addition to what I wrote (and what Ivan correctly added):
To make sure to actually find the cause, press Alt + F2 when the system is booting (in the very moment when the white square in upper left corner of the screen is displayed - the so-called "boot blob"). This will display the drivers names, perhaps this reveals more information.
I don't remember what to do to get the "popuplog.os2" file created... might be worth trying out. But I can't also remember if that is possible within Warp3... ???
Cheers
Thomas
-
I don't remember what to do to get the "popuplog.os2" file created... might be worth trying out. But I can't also remember if that is possible within Warp3... ???
Hi,
To add to Ivan's and Thomas' wonderful help, to enable logging to POPUPLOG.OS2, modify your config.sys file by adding this line (anywhere... I drop it at the bottom):
SUPPRESSPOPUPS=C
(or change "C" to whatever letter you want OS/2 to create the popuplog.os2 file on)
After reboot, if something crashes (that would normally generate a system modal dialog box with an error) OS/2 will create the file in the root directory of the drive selected in that statement. The down side is that you will not see the error on the screen... so if something crashes, you would need to load popuplog.os2 into a text editor and review the details in it.
You can, btw, delete the file at any time... OS/2 will simply recreate it if and when needed (inotherwords, if it is getting big, or if you have reviewed everything in it and want to make it easy to find new entries, simply delete the file, and the next time something crashes, OS/2 will recreate it).
As a side note, most but not all system modal popups will now be routed to that file instead of being displayed. Some instances where that will not happen are certain out of resource error messages, which will still create a system modal dialog box with the error (and wont log it to the popuplog.os2 file if memory serves).
And as a definition, a "system modal" dialog box is a dialog box/notification window that you cannot bypass... when it appears on your screen, all you can do is select an action on it to close it - at which time you can continue with other work. Inotherwords, it is a dialog box that grabs keyboard and mouse focus and does not let it go until you clear it.
According to EDM/2, that config.sys command works with OS/2 2.x, and OS/2 Warp 3 (with FixpPack 29 or later applied) and of course all versions including and since Warp 4.
http://www.edm2.com/index.php/The_Config.sys_Documentation_Project/OS/2-eCS_Commands
I have no idea why it would work in OS/2 2.x, but then not work until FixPack 29 on Warp 3, so if you dont have FP29 installed, try it anyway... the most that will happen is it will ignore the option or prompt you about an "invalid config.sys statement (Press Enter to continue)"
-Robert
-
Wow!
Will give these suggestions a go a bit later today and report back.
Thanks guys!
-
Minor notes
(a) The /REQ parameter. One cause of problems can be /REQ:USBOHCD$ because you aren't loading any USBOHCD.SYS drivers. USBD.SYS will try to get USBOHCD$ IDC entry point and it gets none. If you want the /REQ parameter then remove the USBOHCD$ specification.
(b) A mismatch between USB drivers an USB devices should not cause a Chernobyl screen. It will cause non-functionality of some USB devices. Note that you cannot add more than 4 drivers for each USB specification during installation (this was true for eCS 2.0 RC1, I am not sure whether it is true now) so that you can get non-functional USB devices during install. This will be fixed later, after installation.
My own experience (6 UHCI, 2 EHCI) - mouse does not work after PM shell startup. The mouse gets alive and kicking after updating CONFIG.SYS and rebooting.
(c) A very good USB information and configuration utility: see Hobbes, usbcfg7a.zip
-
the first thing I notice is that while you apparently have 6 UHCI controllers, there's "only" 5 USBUHCD drivers in your config.sys... maybe you simply pasted too few lines in the post, also - anyway - I don't think it would cause such problems to have 1 driver too *few* loaded. Wink
You are 100% correct, I forgot to add the 6th one. All of them are on-board.
My best guess is that you should check if the machines BIOS perhaps has an option to assign IRQs to the USB controllers (are these onboard controllers?). If so, set it to yes. I had experienced problems in the past when trying to run USB in OS/2 using "IRQ-free" options in the BIOS setup.
There are no options in the BIOS for IRQ assignment on USB port (Only serial and parallel)
Next item on my "let's see what happens if..." list would be to make OS/2 boot with the USB stick attached to the port. I don't think it makes a difference as this is usually done to overcome Warp not being able to access the USB drive. Here, the problem is different as the driver does not even load.
No change with the USB Stick in
How do I check the current version of Warp as well as the current FixPak installed?
The first thing you need to do is remove the /req: usbuhcd$, usbohcd$, usbehcd$ from the usbd.sys line. According to the Dec. 2005 usbbasic readme that is generally not needed.
I've removed those and get the same problem
Please note guys: This exact image of OS/2 I'm using here works with USB drivers installed on another model of Lenovo PC's which isn't available any more. That is why I'm trying to get USB working on this model.
To make sure to actually find the cause, press Alt + F2 when the system is booting (in the very moment when the white square in upper left corner of the screen is displayed - the so-called "boot blob"). This will display the drivers names, perhaps this reveals more information.
ALT + F2 reveals that the USBUHCI drivers load fine and it eventually hangs at IBMCOM\MACS\NULLDIS.OS2 which is the LAN driver I believe. (I'm unable to find LAN drivers for this model as well so using the NULL drivers is the only alternative)
-
ALT + F2 reveals that the USBUHCI drivers load fine and it eventually hangs at IBMCOM\MACS\NULLDIS.OS2 which is the LAN driver I believe. (I'm unable to find LAN drivers for this model as well so using the NULL drivers is the only alternative)
That information says you have an irq conflict. Rem out the null mac driver in config.sys then try to boot.
Once you have solved the usb problem then you can go on to investigate network drivers (maybe genmac would help but I'm not sure it will work with warp3).
-
That information says you have an irq conflict. Rem out the null mac driver in config.sys then try to boot.
hehe, after I remmed out that it hangs at the second last one: C:\IBMCOM\PROTOCOL\NETBIOS.OS2
??? No lucky break for me! ???
-
hehe, after I remmed out that it hangs at the second last one: C:\IBMCOM\PROTOCOL\NETBIOS.OS2
It is looking more like a network problem than a usb one. It's so long ago that I used warp3 that I may misremember some things.
First we need to establish which is causing the problem. I tend to think it is the network because I have usb sharing irqs without problems. The old network drivers would not (the problems of shifting cards on pci to get them on a different irq don't bare mentioning).
You should first rem out all the network lines in config.sys, if it boots with usb then you will have to find newer networking fixpacks, plus a driver for your network card, or disable it in bios and use a pci card that has drivers that share irq.
-
Sounds good,
I will give it a go in a little while or tomorrow morning.
How good is the USB drivers I'm using?
Aren't there maybe alternatives to these?
Thanks,
Charl
-
Hi,
yes... I know you will hate me and it certainly does neither help you nor answer the question, but I cannot keep myself from saying it:
How good is the USB drivers I'm using?
Aren't there maybe alternatives to these?
There is actually an alternative to using Warp3 in 2008 - it's called "eComStation".
Sorry, I had to say it.
Now for the question:
I seem to remember that Chris Wolgemuth some time back had a release of USB drivers called "CWUSB...."-something (?) IIRC and that I had good results with that in Warp4 regarding MSD's (USB thumb drives). Most likely, it also works with Warp3. Can't tell. I'ld suggest looking for USB-stuff at Hobbes (http://hobbes.nmsu.edu (http://hobbes.nmsu.edu)) they also list CW-USBMSD... by Chris as I noticed right now.
But wait - hey! He's having his own space right here at
http://www.os2world.com/cdwriting (http://www.os2world.com/cdwriting)
On the left, scroll down to "other programs" and click the last link "cw usb mass-storage driver".
Or launch http://www.os2world.com/cdwriting/cwusbmsd/cwusbmsd.htm (http://www.os2world.com/cdwriting/cwusbmsd/cwusbmsd.htm) directly (will make you lose the navigation frame).
Note: I can't tell if that works on Warp3 or whether that solves your problem...
Anyway - hope it helps, good luck,
Thomas
-
I've tried the CWUSB drivers with no luck...
I enable BASEDEV=CWUSBUHC.SYS /V
and the PC loads fine
I then add BASEDEV=CWUSBD.SYS /V
And the PC stalls again
...
Any other suggestions?
-
Hi charl,
did you follow the suggestions (up the thread) regarding turning "networking" stuff off for the purpose of drilling down the culprit?
Cheers,
Thomas
-
Hmmm, seem to have misread that one...
I'm on it today! Will report back a bit later.
Thanks!
-
Right, I've dumbed out everything network related (According to EDM/2 and Intuition) from the config.sys with no luck.
It still hangs...
-
Hi charl,
ehhh... well. OK, then let's try something on top of that:
Please make an effort to "rem" out the lines in config.sys that deal with multimedia (soundcard drivers) if there are any. If there are none... well, I'm stuck. Perhaps then it would be time to start pulling out adapter cards from your machine which are not absolutely needed (network? sound? anything...?) in order to make their Plug'n'Play power-on routines not interfere with .. whatever... who knows.
And BTW: Is there any setting in BIOS configuration that differ between the two machines, especially regarding ACPI, APM, P'n'P?
Sorry, cheers,
Thomas
-
Hi all and sorry for the long time of no posts!
I've removed any and all IRQ conflicts from the config.sys
I've removed any multimedia as well as network lines from the config.sys
I've tried another version of USBBASIC
The BIOS is configured the same as the other PC