Post #92,153
3/27/03 10:35:32 AM
|
just a couple issues so far
1) the system only has USB 2.0 so I changed the config.sys lines to read:
BASEDEV=USBEHCD.SYS
BASEDEV=USBD.SYS /REQ:USBEHCD$
I cannot get it to recognize devices plugged into it. Using RMVIEW /IRQ I noticed that the USB controller was sharing IRQ 10 with the sound card(I also noticed the built in NIC was sharing one with the SCSI controller). I figure either the USB driver doesn't like to share the IRQ, or maybe I need to load the 1.x USB driver along side the 2.0 USB driver since the only devices I have are 1.x.
2) I installed Xworkplace but it won't let me select auto-power-off. Apparently the APM.SYS isn't installed as it lists the version as 0. I've installed the driver FP3 and base FP3. I've not done any research on this issue yet as it was well past my bedtime :-)
As an aside - I was skimming the motherboard's manual in bed and find that I can individually assign IRQs for the PCI slots. That'll let me change the sound card to a different IRQ so the USB controller has it's own IRQ. While the NIC and SCSI controllers appear to be cooperating, I'll set them up to have their own IRQs as well.
I think I figured out the long pause before the eCS blob shows up. The boot device selections only gave me the choice of "none" or "floppy" for boot sequences 1, 2 and 3. No options for CDROM, ZIP, etc. I set 1 to floppy and the others to none. The last option for boot sequence is "check others?" which I set to YES. The "check others" sequence has SCSI as the last thing to check for after along list of other devices; of course, my system is SCSI based. I think the reason it only showed floppy was I'd forgotten to connect the SCSI cable to the controller the first time I booted, so it didn't recognize any bootable SCSI devices when I set up the bios options. I'll have to check tonight to see if it now lists SCSI.
Darrell Spice, Jr. [link|http://www.spiceware.org/cgi-bin/spa.pl?album=./Artistic%20Overpass|Artistic Overpass]\n[link|http://www.spiceware.org/|SpiceWare] - We don't do Windows, it's too much of a chore
|
Post #92,179
3/27/03 11:22:12 AM
|
Which devices?
1) the system only has USB 2.0 so I changed the config.sys lines to read: \r\n\r\nBASEDEV=USBEHCD.SYS\r\nBASEDEV=USBD.SYS /REQ:USBEHCD$ \r\n\r\nI cannot get it to recognize devices plugged into it. Using RMVIEW /IRQ I noticed that the USB controller was sharing IRQ 10 with the sound card(I also noticed the built in NIC was sharing one with the SCSI controller). I figure either the USB driver doesn't like to share the IRQ, or maybe I need to load the 1.x USB driver along side the 2.0 USB driver since the only devices I have are 1.x.
\r\n\r\n That shouldn't be it. Are you loading the other drivers? Eg- you need to load the MSD driver if you're trying to plug in a camera (USBMSD.SYS). Further, go take a look at Hobbes; there's a recently released version that's been modified to be able to recognise more cameras. \r\n\r\n If you're trying to use a USB mouse and keyboard, you'll want to include USBKBD.SYS and USBMOUSE.SYS (check spelling). \r\n\r\n Etc. \r\n\r\n 2) I installed Xworkplace but it won't let me select auto-power-off. Apparently the APM.SYS isn't installed as it lists the version as 0. I've installed the driver FP3 and base FP3. I've not done any research on this issue yet as it was well past my bedtime :-)
\r\n\r\n Make sure you have a "RUN=APMDAEMN.EXE" in the config.sys too. \r\n\r\n As an aside - I was skimming the motherboard's manual in bed and find that I can individually assign IRQs for the PCI slots. That'll let me change the sound card to a different IRQ so the USB controller has it's own IRQ. While the NIC and SCSI controllers appear to be cooperating, I'll set them up to have their own IRQs as well.
\r\n\r\n So far, I've had very good luck with sharing IRQs; it mostly appears to be a problem with older NIC and sound card drivers that haven't been updated. \r\n\r\n I think I figured out the long pause before the eCS blob shows up. The boot device selections only gave me the choice of "none" or "floppy" for boot sequences 1, 2 and 3. No options for CDROM, ZIP, etc. I set 1 to floppy and the others to none. The last option for boot sequence is "check others?" which I set to YES. The "check others" sequence has SCSI as the last thing to check for after along list of other devices; of course, my system is SCSI based. I think the reason it only showed floppy was I'd forgotten to connect the SCSI cable to the controller the first time I booted, so it didn't recognize any bootable SCSI devices when I set up the bios options. I'll have to check tonight to see if it now lists SCSI.
\r\n\r\n Well, the boot blob is the first thing that os2ldr does, so any pauses before it shows up aren't the responsibility of the Op Sys... as I'm sure you know:) --\r\n-------------------------------------------------------------------\r\n* Jack Troughton jake at consultron.ca *\r\n* [link|http://consultron.ca|http://consultron.ca] [link|irc://irc.ecomstation.ca|irc://irc.ecomstation.ca] *\r\n* Kingston Ontario Canada [link|news://news.consultron.ca|news://news.consultron.ca] *\r\n-------------------------------------------------------------------
|
Post #92,188
3/27/03 12:04:55 PM
|
Re: Which devices?
That shouldn't be it. Are you loading the other drivers? all the other USB lines are still in the config.sys, I only listed those 2 lines as those were the only lines I'd changed for 2.0 support. Forgot to mention - one of the last things I did last night was add a /V at the end of it to make sure it was loading, and it is. I originally had BASEDEV=USBEHCD.SYS in there a few times because there's 6 USB ports(I had to add multiple 1.x driver entries to get the SOYO's multiple USB ports to work). However, the additional entries put up a message along the lines of "no other USB controllers found". I suspect either the USB 2.0 driver automatically handles multiple controllers, or the 6 USB ports are really a built-in 6 port hub. Make sure you have a "RUN=APMDAEMN.EXE" in the config.sys too. I'll check that tonight. So far, I've had very good luck with sharing IRQs; it mostly appears to be a problem with older NIC and sound card drivers that haven't been updated. The ESS Solo's driver is from '99, so the sound card sharing it's IRQ with the USB controller just might be the problem. I don't always mention it - but mega thanx for all your help :-) Darrell Spice, Jr. [link|http://www.spiceware.org/cgi-bin/spa.pl?album=./Artistic%20Overpass|Artistic Overpass]\n[link|http://www.spiceware.org/|SpiceWare] - We don't do Windows, it's too much of a chore
|
Post #92,298
3/27/03 8:33:50 PM
|
Re: Which devices?
"all the other USB lines are still in the config.sys, I only listed those 2 lines as those were the only lines I'd changed for 2.0 support. Forgot to mention - one of the last things I did last night was add a /V at the end of it to make sure it was loading, and it is. I originally had BASEDEV=USBEHCD.SYS in there a few times because there's 6 USB ports(I had to add multiple 1.x driver entries to get the SOYO's multiple USB ports to work). However, the additional entries put up a message along the lines of "no other USB controllers found". I suspect either the USB 2.0 driver automatically handles multiple controllers, or the 6 USB ports are really a built-in 6 port hub."
I have read that the OS/2 USB drivers only supports up to 4 controllers. Also did you leave the USB 1.1 drivers in config.sys? I have read that these are required to support backward compatibilty. That for each 2.0 controller there is a 1.1 controller to handle any 1.1 USB devices attached. This is all just what I have read in Usenet, as I have no USB 2.0 to play with. Do you have USB 2.0 devices to plug in?
Most times there are 2 USB ports for each controller I think, or in the case of 2.0 I think there may be 3 USB 2.0 ports and 3 USB 1.1 ports. Are any of the ports labelled differently? You should run PCI.EXE to see what you actually have. In my case PCI.EXE shows only two UHCI controllers, and I have only 2 USB ports.:
"Vendor 8086h Intel Corporation
Device 2442h 82801BA/BAM USB Controller #1 (ICH2/ICH2-M B5 step)
Command 0005h (I/O Access, BusMaster)
Status 0280h (Supports Back-To-Back Trans., Medium Timing)
Revision 05h, Header Type 00h, Bus Latency 00h
Self test 00h (Self test not supported)
PCI Class Serial, type USB (UHCI)
Subsystem ID 10271025h Unknown
Subsystem Vendor 1025h Acer Inc
Address 4 is an I/O Port : 00008000h
System IRQ 11, INT# D
Vendor 8086h Intel Corporation
Device 2444h 82801BA/BAM USB Controller #2 (ICH2/ICH2-M B5 step)
Command 0005h (I/O Access, BusMaster)
Status 0280h (Supports Back-To-Back Trans., Medium Timing)
Revision 05h, Header Type 00h, Bus Latency 00h
Self test 00h (Self test not supported)
PCI Class Serial, type USB (UHCI)
Subsystem ID 10271025h Unknown
Subsystem Vendor 1025h Acer Inc
Address 4 is an I/O Port : 00008060h
System IRQ 11, INT# C"
Mark
For a choice in the future JOIN VOICE NOW
check out [link|http://www.os2voice.org/index.html|http://www.os2voice.org/index.html]
|
Post #92,308
3/27/03 9:01:26 PM
|
it needed the OHCI lines
I ended up with EHCI once on irq 10 and OHCI three times on irqs 5, 14 and 15. I tested the 6 ports with my Linksys 64MB "memory disk", and each instance of OHCI handled 2 ports. Reading in the motherboard manual I find this rather interesting statement Each of the six USB ports can be automatically routed to support a High-speed USB 2.0 devices or Low-speed USB 1.1 devices. Sounds like EHCI only comes into play if there's a 2.0 device plugged in. I don't have any USB 2.0 devices to test it out with. I got the memory disk for $10 at Fry's(it lists for $45). I suspect the 1.1 versions of the memory disks are being cleared out for faster 2.0 versions. Darrell Spice, Jr. [link|http://www.spiceware.org/cgi-bin/spa.pl?album=./Artistic%20Overpass|Artistic Overpass]\n[link|http://www.spiceware.org/|SpiceWare] - We don't do Windows, it's too much of a chore
|
Post #92,315
3/27/03 9:21:30 PM
|
update
1) USB - as mentioned in my reply to [link|/forums/render/user?username=madodel|madodel], [link|/forums/render/content/show?contentid=92308|Post #92308], the USB controllers act like 1.1 controllers until a 2.0 device is plugged in.
2) mis-read the screen about the APM version. APM driver 10.070 was loaded, but the system's APM level is 0. It's 0 because the motherboard uses ACPI instead of APM. I googled up a [link|http://www.mail-archive.com/acpi-os2%40netlabs.org/|mailing list archive] started by Netlabs in November 2002. Don't think they're too far along yet as Netlab's site doesn't mention the mailing list anywhere.
As far as the eCS blob goes - now that the SCSI cable's plugged in the boot sequence lets me select "Legacy SCSI". However, it still has the long pause before it starts booting off SCSI. I even tried having SCSI as the only boot option :-/
Darrell Spice, Jr. [link|http://www.spiceware.org/cgi-bin/spa.pl?album=./Artistic%20Overpass|Artistic Overpass]\n[link|http://www.spiceware.org/|SpiceWare] - We don't do Windows, it's too much of a chore
|
Post #92,417
3/28/03 10:10:50 AM
|
ACPI
There's a chance that Daniela Engert might take on building an ACPI PSD. That would be interesting, because OS2APIC.PSD is one of the key files that permits SMP on SMP OS/2, the other ones being os2krnl, os2ldr, and doscall1.dll. I don't know if she'd be trying to deal with SMP or not, but might be because one of the motivations is to get to work with Hyperthreading. The big question is whether she has the time to do it or not. That would be quite cool as it could go a long way to fixing the power management issues around a lot of the newer computers too, and mean that OS/2 will continue to run on x86 for a while to come; as "legacy free" machines (ie- ones where you can't tell the hardware what to do;) become more and more common.
--\n-------------------------------------------------------------------\n* Jack Troughton jake at consultron.ca *\n* [link|http://consultron.ca|http://consultron.ca] [link|irc://irc.ecomstation.ca|irc://irc.ecomstation.ca] *\n* Kingston Ontario Canada [link|news://news.consultron.ca|news://news.consultron.ca] *\n-------------------------------------------------------------------
|
Post #92,808
3/29/03 11:54:33 AM
|
So what's the hardware verdict on Soyo Ath vs Abit P4?
Hi Darryl,
Are you happy with either of the recent hardware combinations you've tried with eCS? Lately I've been a fan of Soyo Dragon+ boards (seemed wonderful until I had to turn off Turbo mode in the BIOS to get it to recognize the USB port - no problems otherwise), and I've used an ABIT K7V (IIRC) Athlon system without problems either. Both of these boards are running Win2k.
As I read your reports, you've been able to get eCS running with most/all of the peripherals on either system, but have trouble applying eCS fixpacks. Is that the gist of it?
My OS/2 system is running Warp 3 Connect on a 486/133 SCSI box. I'm considering finally buying a new box for Warp and/or eCS, but your reports make me nervous. :-/ It makes me more strongly consider that Virtual PC for OS/2 might be the way to go.
What hardware would you recommend? Is it worth the hassle for a dedicated eCS box? Thanks.
Cheers,
Scott.
|
Post #92,823
3/29/03 1:07:14 PM
|
Re: So what's the hardware verdict on Soyo Ath vs Abit P4?
Considering I'd get various hangs at different times(booting, already running) I think I had flacky hardware with the Soyo/Athlon. For the most part everything has been fine with the Abit/P4.
I was having a problem installing Visual Age C++ 3.0 - the second phase of installation(after the reboot) never happens. Somebody else posted something about this a while back at the forums at [link|http://www.ecomstation.com|http://www.ecomstation.com] though I can no longer find that thread.
I'd never had a problem installing VAC on eCS before, though I realized that I'd not installed any fix packs like I had done this time. So I reinstalled eCS and I was able to get VAC installed by doing it before any of the fixpacks. Today I'll be reinstalling the fixpacks.
The only fixpack I've consistently had problems with was the TCP/IP one. Jack mentioned that others with a Matrox video card have seen the same problem - so it's not the motherboard/CPU. Even though the install hangs, TCP/IP seems to function fine. I have not yet installed the TCP/IP fixpack on the Abit/P4 so I'll report back the results later today.
Darrell Spice, Jr. [link|http://www.spiceware.org/cgi-bin/spa.pl?album=./Artistic%20Overpass|Artistic Overpass]\n[link|http://www.spiceware.org/|SpiceWare] - We don't do Windows, it's too much of a chore
|
