As Adam pointed out, you can try the "vanilla" OCO module at http://www10.software.ibm.com/developerworks/opensource/linux390/current2_4_ 19-may2002.shtml#qeth20021219
You may need to turn on some other options in your kernel if you still get unresolved reference errors. Post those errors, and someone should be able to help you figure out what to turn on or off in your kernel config. Mark Post -----Original Message----- From: Alex Leyva [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 11, 2003 6:00 PM To: [EMAIL PROTECTED] Subject: Re: QDIO for virtual NIC i've tried with almost all the differents oco modules, but i only get "unresolved symbols", its because i have a redhat installed, but with another kernel, so my system doesnt get into any category: Red Hat Linux 7.2 kernel version (31-bit): kernel version 2.4.9-38 (OCOs dated 2002-12-19) kernel version 2.4.9-37 (OCOs dated 2002-08-16) kernel version 2.4.9-17 (OCOs dated 2002-01-15) so what can i do? On Tue, 11 Mar 2003, Adam Thornton wrote: > On Tue, Mar 11, 2003 at 04:32:02PM -0600, Alex Leyva wrote: > > Hi all, im configuring some guest lans, but im having problems with the > > linux side, im using RedHat 7.2, with kernel 2.4.19, i've compiled the > > kernel to have QDIO as a module, but i have only the qdio.o module, i dont > > have qeth.o, i have the definitions in modules.conf and chandev.conf > > correct, but i just cant locate the qeth.o module, its strange to me > > because the kernel config includes the QDIO support as a module, so i dont > > understand why it dosnt have it. > > The QDIO infrastructure support is Open Source. > > The qeth OSA/Hipersockets driver, which plugs into the QDIO support, is > OCO. Get it from IBM; it's available for free download from their > Linux/390 DeveloperWorks site. > > Adam > -- Alejandro Leyva Rabinovich. Jefe de la Unidad Departamental de Soporte Ticnico (Administracisn de Mainframe). Direccisn General de Informatica. Secretarma de Finanzas. Gobierno del Distrito Federal.
