Hi to all! Im posting this message here coz ive this problem: with Suse 9.3 Professional i cannot use my network adapter, an Intel 10/100 integrated in the motherboard. Mainly it does so: if i disable it in the Bios of course Suse cannot see it, then i enable it and Suse handles it perfectly, i can ping the card, the router, the external ip, all ok, i can go online, and do all. If i reboot the pc all the network card profile stays on but the card is unreachable and i cannot do anything. Ive tried to:

-use pci=noroute, pci=noacpi, pci=routeacpi as boot options, to disable the acpi and pnp from bios (means to put as "reserved the irq handling of the card = irq11");

-put a string in the ifcfg.* for force the dhcp to use the first eth device;

-modified the /etc/sysconfig kernel module adding the device e100 module to be loaded up during boot, also the eepro100, the modules which are present when the card works are also present when it doenst.

A guy from Suse told it's a know kernel bug, but now i ask to myself how it's possibile to have such a kind of bug considerin how common is my ethernet chip and all the Suse installation around the world.

Does anyone have any idea or faced the same? In Suse/Novell discussion Server Forum i met some but i think everyone of us still have it.

Thanks!

Riccardo