From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0;
Description of problem:
Remote installation through an RSA2 service processor fails when
prompting for the 2nd CD. The 2nd CD appears not to mount properly so
the file transfer fails.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Attach Windows client to RSA2
2.Login to RSA2 from web browser
3.Launch remote console
4.Insert installation CD into Windows client CDROM drive
5.Mount remote CD from remote console
6.Power up local server
7.Proceed with text-based install
8.Insert 2nd CD when prompted
Actual Results: I/O error when attempting file transfer from 2nd CD
Expected Results: Installation should proceed
You must have an RSA2 service processor installed in an appropriate
IBM server to recreate this problem. Mike Gehagan should already have
an RSA2 adapter.
The remote client browser must be run on a Windows workstation
because of a java applet dependency on Windows JRE.
Do the same workarounds as in bug 112327 apply here? If so, then I
really think that your service processor stuff is screwing stuff up
(and since we don't have the source to the modules, we can't support them)
This has nothing to do with the ibmusbasm daemon and niether does bug
112327. Therefore you do not need any source code for ibmusbasm.
The problem is that even WITHOUT ibmusbasm installed, there are USB
support issues with the RSA2 device. RSA2 is a composite USB device
and it appears that USB support in linux may not provide adequate
support for this type of device.
Please provide a status update.
I'm reassigning this to our USB maintainer.
Please refer to bugzilla 120645 for a patch which is a possible
resolution for this problem.
*** This bug has been marked as a duplicate of 120645 ***
A fix for this problem has just been committed to the RHEL3 U4
patch pool this evening (in kernel version 2.4.21-20.7.EL).
An errata has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.