Alessandro Suardi wrote: > Kernel pcmcia code works fine with 2.4.0-test8 and my Xircom RBEM56G100TX, > in fact I am writing from my laptop connected through it. See lsmod output > and relevant part of .config. > > [asuardi@princess asuardi]$ lsmod > Module Size Used by > serial_cb 1456 1 > xircom_tulip_cb 30168 1 > cb_enabler 2536 2 [serial_cb] > ds 6540 2 [cb_enabler] > yenta_socket 9932 4 > pcmcia_core 39264 0 [cb_enabler ds yenta_socket] > sb 1712 1 (autoclean) > sb_lib 33660 0 (autoclean) [sb] > uart401 6436 0 (autoclean) [sb_lib] > [asuardi@princess asuardi]$ For a good many people, yes it does work. For this hardware it doesn't work. pcmcia_core and yenta_socket are the only two modules I can load, and once loaded they can't be unloaded. Trying to rmmod yenta_socket yeilds a segfault and the module remains in a (deleted) state. The kernel pcmcia can't get the sockets set up correctly. It used to work; on 1 socket only and randomly blew up the kernel. The other socket hung the interrupts. -d -- "The difference between 'involvement' and 'commitment' is like an eggs-and-ham breakfast: the chicken was 'involved' - the pig was 'committed'."
begin:vcard n:Ford;David x-mozilla-html:TRUE org:<img src="http://www.kalifornia.com/images/paradise.jpg"> adr:;;;;;; version:2.1 email;internet:[EMAIL PROTECTED] title:Blue Labs Developer x-mozilla-cpt:;28256 fn:David Ford end:vcard
