Hi
I have had that duplicate problem since Mdk7.2 was issued, and have
changed to Debian on the Internet.

I have a ASUS P34V board with Intel III 933 MHz, 256 MB Compaque 133 MHz

ram, an IBM 30 GB (not used at UDMA 66) because of this problem.

Harddrake usually puts 8139too as eth0 and rtl8139 as eth1 on the above
with a simple Planet rtl8139.

Observe! Debian Potato r2, Slackware 7.1 and RedHat 7.0 all finds my
single cheap rtl8139.

My latest messages.
RTL8139 Iterrupt time blocked, status ffff
eth0: PCI Bus error 2900004
...
eth0: Too much work at interrupt, IntrStatus=0xffdf

After that I have manually excluded the double rtl8139 in
/etc/modules.conf, this on a machine that was manually set up after
installation in linuxconf.

I have made two cooker downloads, to check, (by rsync), yesterday and
today and have had problems when installing. Everything seems to go so
fine fast that the installation does not cope, ex: reported that
XF86-SVGA, was nor found although it existed in the hd-image.

regards
guran


Hi
I have had that duplicate problem since Mdk7.2 was issued, and have
changed to Debian on the Internet.

I have a ASUS P34V board with Intel III 933 MHz, 256 MB Compaque 133 MHz
ram, an IBM 30 GB (not used at UDMA 66) because of this problem.

Harddrake usually puts 8139too as eth0 and rtl8139 as eth1 on the above
with a simple Planet rtl8139.

Observe! Debian Potato r2, Slackware 7.1 and RedHat 7.0 all finds my
single cheap rtl8139.

My latest messages.
RTL8139 Iterrupt time blocked, status ffff
eth0: PCI Bus error 2900004
...
eth0: Too much work at interrupt, IntrStatus=0xffdf

After that I have manually excluded the double rtl8139 in
/etc/modules.conf, this on a machine that was manually set up after
installation in linuxconf.

I have made two cooker downloads, to check, (by rsync), yesterday and
today and have had problems when installing. Everything seems to go so
fine fast that the installation does not cope, ex: reported that
XF86-SVGA, was nor found although it existed in the hd-image.

regards
guran



Reply via email to