So far we couldn't find a suitable Cardbus driver for that chip. The
ones we tried either don't work or hang the system upon loading.
Is there
- a Cardbus package around that supports this TI chip?
- a (modified/enhanced) driver supporting it
and in case the answer to any one or more of the above questions happens
to be Yes, where can we find that precious work?
BTW, does anyone know the usual max. current limit on a notebook's
combined mouse/KB PS/2 jack (pin 4)?
Is there some kind of a standard or is it up to each manufacturer/model?
> We are currently trying to set up an older Cpq notebook with a
> TI PCI-1410 PC-Card Cardbus Controller
> to add urgently needed USB 2.0 support.
Tried ss2ticb2.zip (Dani's version) at http://www.os2site.com/sw/drivers/laptop/index.html
?
Thanks Ian, unfortunately, Dani's modification doesn't seem to do the
trick. At boot time we are getting a message that the driver wasn't
installed. :-(
Looks like we are out of luck on this one with OS/2 or eCS and it has to
become a Linux or BSD 'puter.
> We are currently trying to set up an older Cpq notebook with a
> TI PCI-1410 PC-Card Cardbus Controller
> to add urgently needed USB 2.0 support.
>
> So far we couldn't find a suitable Cardbus driver for that chip. The
> ones we tried either don't work or hang the system upon loading.
>
> Is there
> - a Cardbus package around that supports this TI chip?
> - a (modified/enhanced) driver supporting it
>
I have both an older Compaq Armada 1571 notebook and an Armada 7400
that both work under the "playwill" PCMCIA card driver. I have a disk
--
Hi Paul,
do they actually use this controller version: TI PCI-1410?
I'm just asking, since I'm wondering why IBM would have removed support
for a controller chip, working with an earlier/different? version of the
CardBus or PCMCIA driver package Dani used for her patching.
If this one is listed as being supported, then I'd be happy to give it a
try. Could you then email me the driver?
Thanks
Both Armada Laptops must be older than yours. They both have TI chips
Armada 1571 PCI-1131
Armada 7400 PCI-1250
Possibly your PCI-1410 is too new. Here are my notes on what I did
. . .
----- Notes ----------
This info is for the Compaq Armada 1571 Laptop to get the PCMCIA Slots
working.
First, setup the PCMCIA support in OS/2 Warp. I set it up for the
newest Compaq
Second, place PLAYWILL.EXE in a temporary directory and run it.
Just use the "Chembook"
drivers initially. These do not work with the Armada 1571 and
will be changed
Third, the driver that does work is the SS2PCIC2.SYS. It needs to
be dissolved out of the
SS2PCIC2.EXE
Fourth, place the SS2PCIC2.SYS driver into the \OS2 directory.
Modify CONFIG.SYS by
replacing the "chembook" driver with SS2PCI2.SYS
Things should now work!
Other IBM2xxxxx.SYS drivers are included for completion. They were
tried and do not work on the Armada 1571.
Oct 2001
-------- End Notes --------------------
I think these both are still on line if you have not tried them.
Paul
--
This matches my experiance with an HP Omnibook 800 with TI 1131
chipset.
Steve N.
PCI1410:
* iSeries 1422, iSeries 1442, iSeries 1482, iSeries 1483, iSeries 1492
* iSeries 1542, iSeries 1562, iSeries 1592
PCI1410A:
* A21e, A22e
* G40
* R31, R32
Does anyone have one of those models and managed to get the PC-Card
Cardbus Controller work in it with OS/2 or eCS?
Am 12.04.09 06.53 schrieb Wolfi:
> I just found, that according to http://www.thinkwiki.org/wiki/TI_PCI1410
> apparently the PCI1410(A) can also be found in the following ThinkPads:
>
> PCI1410:
> * iSeries 1422, iSeries 1442, iSeries 1482, iSeries 1483, iSeries 1492
> * iSeries 1542, iSeries 1562, iSeries 1592
>
> PCI1410A:
> * A21e, A22e
> * G40
> * R31, R32
>
> Does anyone have one of those models and managed to get the PC-Card
> Cardbus Controller work in it with OS/2 or eCS?
I have an R31, but as I mentioned I've never been able to get the PCMCIA
working (with Dani's driver or any other). Haven't tried the TSSC driver
because I don't want to buy it blind.
--
Alex Taylor
Fukushima, Japan
http://www.socis.ca/~ataylo00
Please take off hat when replying.
Hi Wolfi,
I had an A21e laptop, and I did get the TI1410 Cardbus Controller
working by patching the driver. It was a long time ago, so don't ask me
for detailed instructions :-) Anyway, I've found my old TI1410.SYS
driver, if you want to give it a try?
Rgds,
Richard.
Hi Alex,
Please find the relevant stuff here:
http://homepage.ntlworld.com/richjmartin/pub/
No guarantees it will work - I cannot test it as my A21e blew up many
years ago!!
Rgds,
Richard
Oh yes! I most definitively am :-)
> Hi Alex,
>
> Please find the relevant stuff here:
>
> http://homepage.ntlworld.com/richjmartin/pub/
>
> No guarantees it will work - I cannot test it as my A21e blew up many
> years ago!!
>
Thanks a lot Richard, I'll give it a try.
Thank you for the info.
I have a TI Chipset in my desktop (PCI card and 2 ports) and I have not had
time to make it work. If I have time I may give this a try.
Thanks again,
Bart
First the good news: your patched driver is loading here as well :-)
but I don't know yet, if it actually will work with my CB card.
Unfortunately the laptop now gets stuck during boot-up with the line
IFS=e:\OS2\BOOT\JFS.ifs being the last one shown.
When I try to run CHKDSK /F:3 on the eCS boot partition from the CD's
Maintenance Console, it says
"JDS0138: CHKDSK Checking a mounted file system does not produce
dependable results.
CHKDSK File system is clean".
There is however one thing that makes me wonder:
the first line of CHKDSK's screen output says "Unable to open for write
access. Proceeding in read-only mode"
So now the 1. question: how does one unmount a JFS partition to satisfy
CHKDSK and how does one mount it again afterwards.
Since we are still having ACPI-related hang problems, requiring to turn
off power and restart, apparently the FS was still dirty, when I was
shifting efforts again to Linux the other day and trying to get the eCS
partitions mounted from there.
In order to be able to do so, I ran CHKDSK on those eCS JFS partitions
from Linux and was then able to mount and access them.
So now the 2. and more important question: why does JFS.ifs get stuck
when I try to boot up eCS from HDD, but doesn't have any problem when
booted from the eCS CD and accessing those partitions and how can I fix it?
Have you compared the actual lines in config.sys?
FYI every time I've tried to add more memory to my machine it is JFS.ifs
which fails. It seems to be very sensitive to things not being quite right.
Dave
ps the CAD popup program has a menu item for unmounting a partition.
Works fine as long as nothing has been loaded from that partition.
http://hobbes.nmsu.edu/download/pub/os2/util/process/cadh.zip
> Please find the relevant stuff here:
>
> http://homepage.ntlworld.com/richjmartin/pub/
>
> No guarantees it will work - I cannot test it as my A21e blew up many
> years ago!!
Thanks.
Alas, it yields the same results as SS2TICB: namely, the driver loads
successfully, and the socket services themselves work... but any card
inserted (a NIC, in my case) gets detected as "Memory".
Looks like you are a bit more lucky then, here on this Compaq SS2TICB
doesn't even load :-(
The HDD one reads:
IFS=e:\OS2\JFS.IFS /LW:5,20,4 /AUTOCHECK:*
and the one from the Maintenance Console:
IFS=z:\JFS.IFS /CACHE:512 /LAZYWRITE:16,64,2
I also just noticed, when I wanted to remove 2 Bootable partitions from
the BM menu, that LVM doesn't allow me to do that.
I only could add 2 others, that don't have the Bootable attribute yet in
LVM.
That admittedly is kind of odd as well and I haven't found a solution
for that issue yet either :-(
Looks like something is really a bit fishy here. Question now of course,
how to fix it.
> > FYI every time I've tried to add more memory to my machine it is JFS.ifs
> > which fails. It seems to be very sensitive to things not being quite
right.
Ooops?! That sounds weird and at the same time kind of discouraging to
use JFS :-\
A FS shouldn't care at all, if memory is added to a system.
How do you then recover from it?
> > Dave
> > ps the CAD popup program has a menu item for unmounting a partition.
> > Works fine as long as nothing has been loaded from that partition.
> > http://hobbes.nmsu.edu/download/pub/os2/util/process/cadh.zip
Mmmh, but that would require that I actually first get booted from HDD,
in order to try that :-\
It would appear you have found the main reason for NOT using JFS as a
boot partition.
Since there are no recovery tools available that work, there is a
potential mine field waiting for anyone that uses bootable jfs. If
eCS is going to use a bootable jfs partition then they need to produce
the tools to recover it and not do the windows thing of re-installing
when there is a problem.
ivan
--
Wolfi wrote:
> Am 30.05.09 23.55 schrieb Dave Yeo:
>>> On 05/30/09 07:10 pm, Wolfi wrote:
>>>>> So now the 2. and more important question: why does JFS.ifs get stuck
>>>>> when I try to boot up eCS from HDD, but doesn't have any problem when
>>>>> booted from the eCS CD and accessing those partitions and how can I
>>>>> fix it?
>>>
>>> Have you compared the actual lines in config.sys?
>
> The HDD one reads:
> IFS=e:\OS2\JFS.IFS /LW:5,20,4 /AUTOCHECK:*
>
You could change the above to
IFS=e:\OS2\JFS.IFS /LW:5,20,4 /AUTOCHECK:+E
That would force a full chkdsk at boot on drive E: - add any other
drives requiring checking using the same method eg +F+G
Regards
Pete
The memory that I've tried to add is somewhat mismatched and may even be
wrong for my MB. (I once bought some memory that absolutely didn't work
in my then current MB but worked fine in my next one)
I've just reverted to the simm that came with this computer. My current
simm is EEC while the ones I've tried replacing it with are just plain
cheap ones.
Dave
Thanks Pete, that does the trick :-)
But is is still ridiculous, I not only have to remove the "*" in the JFS
line permanently, but in the following HPFS.ifs line in Config.sys as
well, to prevent it from becoming the next unintended halt, even though
that I don't even have any HPFS partitions.
Something is here really very fragile and extremely easy to break.
And weirdly, Richards patched TI1410.sys now also doesn't load anymore.
So I'm now back to square one :-(
Unfortunately it really appears to be that way :-(
> Since there are no recovery tools available that work, there is a
> potential mine field waiting for anyone that uses bootable jfs. If
> eCS is going to use a bootable jfs partition then they need to produce
> the tools to recover it and not do the windows thing of re-installing
> when there is a problem.
I expected bootable JFS to be as robust and trouble free as HPFS on my
W4 box proved to be over the last some 15 years, but that sadly just
doesn't seem to be the case.
> On Wed, 27 May 2009 00:56:22 UTC, Wolfi <public...@yahoo.fr> wrote:
>
> > I just found, that according to http://www.thinkwiki.org/wiki/TI_PCI1410
> > apparently the PCI1410(A) can also be found in the following ThinkPads:
> >
> > PCI1410:
> > * iSeries 1422, iSeries 1442, iSeries 1482, iSeries 1483, iSeries 1492
> > * iSeries 1542, iSeries 1562, iSeries 1592
> >
> > PCI1410A:
> > * A21e, A22e
> > * G40
> > * R31, R32
> >
> > Does anyone have one of those models and managed to get the PC-Card
> > Cardbus Controller work in it with OS/2 or eCS?
>
> I have an R31, but as I mentioned I've never been able to get the PCMCIA
> working (with Dani's driver or any other). Haven't tried the TSSC driver
> because I don't want to buy it blind.
>
Alex: this is the right decision, especially now with eCS2 and ACPI:
the TSSC driver is not compatible with ACPI, and TSSC expects a
certain number of license fees before they do any work on the driver
to make it ACPI compatible. This new work would not even include
adding new chips to the driver.
I started collecting names of people who would be interested in an
update some time ago, but I never even got close to the required
number, and this count was not accounting for requests that TSSC may
not have wanted to satisfy.
Therefore, it appears the the TSSC driver will never be compatible
with ACPI (and, thus, with the default installation of eCS2).
--
A.-P. P.
I have a copy of the TSSC driver I bought in 2002 or so. It will
likely work with the R31 if I recall the time frame correctly but I am
surprised the IBM driver isn't. At the time I bought the TSSC driver
the IBM driver did not support the TI chipset I had but later Dani's
patched driver worked and then IBM's own later driver was updated.
The TSSC driver also does not work with cbenable. What would be nice
is if there were enough interest to get ACPI, the drivers updated to
the level that at least their windows stuff is at, and an ability to
do as cbenable does for us so that cbenable is not required.
--
Andy