* Gaudenz Steinlin <[EMAIL PROTECTED]> [2004-01-11 19:10]: > > (BTW, I think discover switched all eepro100 modules to e100; but > > apparently [according to some mails I saw, e.g. on -boot] some kinds > > don't work with e100 yet, although they do work with eepre100) > Do you have some more exact pointers?
OK, the mail I had in mind was: #220800 discover-data: e100 loaded instead of eepro100. IIRC, there was another posting (to which JoeyH added eepro100 again as a module), but I cannot find it right now. The submitter claims that his laptop only works with the eepro100 module, not with e100. This has been fixed this then, but since (afaik) all occurences of eepro100 have been changed to e100 in a previous version of discover-data, I wonder if anyone actually checked if e100 supports all cards eepro100 does. > > insmod: unresolved symbol mitt_check_link_R0f2ff551 > > modprobe: failed to load module eepro100 > > > I fail to see why this problem is related to discover. This user tries > to load the eepro100 module and this module has unresolved symbols. This Right. What I wanted to say is that this might be a card which requires the eepro100 modules instead of e100. But that's something that has to be confirmed with the submtter. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
