robgreene
Group: Members
Posts: 8
Joined: April 2005 |
|
Posted: April 16 2005,21:10 |
|
Ok, corrections here:
1) FreeBSD does work. Network is ok. I don't ran out of inodes installing and don't have a graphic environment, so that stank, but I could ssh to another Linux box on the network and use links to browse. A solution, but not a good one.
2) With all prior configuration wiped from the drives (both needed to be reformatted to get FreeBSD to work), DSL still decides I have two network devices!
As asked before, here's the hardware: * Not sure what the motherboard is - sorry. It is a VESA Local Bus machine, however. Gateway model 4DX33V. * 4 cards in the machine: - ISA Etherlink III 3c509b - ISA Soundblaster (SB16, I think) - VLB SIIG Fast EIDE Controller (Enhanced IDE Master VL) - VLB Speedstar Pro * Drives: - MadDog CDRW, using secondary connector on SIIG card - WD 340MB disk, primary connector on SIIG card; master - WD 540MB disk, primary connector on SIIG card; slave - Combo 3.5, 5.25 drive that came with computer
Because of the age of this computer, I'm using SmartBtMgr to boot from floppy and then boot from the CDROM. (Is this bad? Does DSL have a boot floppy that I can - or must - install from?)
What I did notice while putzing around: * DSL autodetects the eth0 and eth1 devices. Neither work, and I don't know how to figure out what physical device DSL thinks eth0 or eth1 are. * lsmod does show 3c509 driver loaded * lsmod also shows USB related stuff as well as ieee1394 being loaded (could this be the network devices?). This still shows up after doing a "dsl noscsi nopcmcia nousb noagp noapm noapic nomce noddc" at the boot prompt. * After removing the USB and ieee1394 from the loaded modules, the network devices still didn't load. * I added an alias in /etc/modprobe.d/network of "alias eth0 3c509" but that didn't work at all.
This is all from the bootup. I haven't reinstalled DSL to the harddisk yet.
Suggestions?
Thanks! -Rob
|