I've used the qeth.o module that Adam send to me, and activated the ipv6,
and now its working, but i have to load the qdio module, then ipv6, and
then qeth.o, and now:
# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
MULTICAST MTU:1492 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:8
iucv0 Link encap:Serial Line IP
inet addr:10.1.70.17 P-t-P:10.1.70.12 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MTU:9216 Metric:1
RX packets:223 errors:0 dropped:0 overruns:0 frame:0
TX packets:142 errors:9 dropped:9 overruns:0 carrier:9
collisions:0 txqueuelen:32796
RX bytes:17832 (17.4 Kb) TX bytes:37769 (36.8 Kb)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:19 errors:0 dropped:0 overruns:0 frame:0
TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1768 (1.7 Kb) TX bytes:1768 (1.7 Kb)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
i've never saw a sit0 interface, i dont know if i can dissapear it or only
ignore it, but now i have eth0, thanks a lot for all the help Alan, Adam
and all the people that have helped me, thanks a lot.
On Wed, 12 Mar 2003, Alan Cox wrote:
> On Wed, 2003-03-12 at 00:05, Adam Thornton wrote:
> > On Tue, Mar 11, 2003 at 05:01:20PM -0600, Alex Leyva wrote:
> > > the stock qeth?
> > > from suse?
> > > or where i get it?
> > > when i builded the kernel it only made the qdio.o module, i dont have any
> > > qeth.o, thats the problem.
> >
> > Oh dear. Has Red Hat gone and done something silly with the symbol
> > table?
> >
> > If you tried the 2.4.19 OCO module and it didn't work, then RH has done
> > something silly with the symbol table. I guess.
>
> You must build the modules and kernel with the same basic options, often
> the same compiler options and same patches to the tree if they affect
> any internal structures. Linux doesn't have a module ABI.
>
> Anything else people do on their own heads and in a production
> environment I'd advise extreme caution because you might not find out
> about a mismatch (especially if you use -f or non symbol versioned
> modules) until far too late
>
--
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.
