Brad Klinghagen wrote:
I'm obviously missing something regarding burning the CD. I tried again with
both CD images. The _usb_...img (I uncompressed the file) version burned a
blank CD again, and with _iso_bin I couldn't even get Nero to burn the
image because of unrecognized format
Brad
Brad Klinghagen wrote:
If it ain't syslinux, then I know I downloaded the most recent versions of
the modules -
Yes, but your kernel was not the latest and greatest.
I ended up downloading them straight from the website. The
only way I could have the wrong kernel is that one of the
Brad
Brad Klinghagen wrote:
I copied the Linux file from the floppy disk generated by the pre-packaged
download file and I executed syslinux from the floppy (after installing
hdsupp). When I booted my system (not my target, but the pseudo-duplicate),
then entered the command uname -a, the
I think I may have found how to make it work. I tried a couple older drivers
for 8139too.o. I tried the module from the 2.4.26 modules and 2.4.32
modules. The xx.26 version failed completely, but the 2.4.32 worked. I now
have connection through my NEW system. The file sizes for the 2.4.32 and the
Brad
Brad Klinghagen wrote:
I think I may have found how to make it work. I tried a couple older drivers
for 8139too.o. I tried the module from the 2.4.26 modules and 2.4.32
modules. The xx.26 version failed completely, but the 2.4.32 worked. I now
have connection through my NEW system. The
Your last statement is what I did. I started from scratch using only the
latest and greatest from the 3.1 release. I didn't use any old drivers (only
previous config files - which that release didn't have configdb or moddb
which made upgrading a royal pain).
I only made the mistake initially of
Brad
Brad Klinghagen schrieb:
Your last statement is what I did. I started from scratch using only the
latest and greatest from the 3.1 release. I didn't use any old drivers (only
previous config files - which that release didn't have configdb or moddb
which made upgrading a royal pain).
