Date: Mon, 22 Sep 1997 21:22:20 -0700 (PDT) From: Doug White <dwhite@gdi.uoregon.edu> To: "William D. Ward" <euswdwj@exu.ericsson.se> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Compaq XL 590-PCNet problem? Message-ID: <Pine.BSF.3.96.970922212010.6177F-100000@gdi.uoregon.edu> In-Reply-To: <199709230103.UAA22711@b04h32.exu.ericsson.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 22 Sep 1997, William D. Ward wrote: > I'm having some difficulties getting the Ethernet interface to work on a Compaq > Deskpro XL 590. Currently ifconfig on this machine results in a syslog message > reporting 'lnc0: Initialisation failed' (which perhaps means that the > initialization failed). Okay, do you know if this is connected to the PCI bus or ISA bus? I assume it's on the PCI bus based on the I/O port provided below. > I am using 2.2.2-RELEASE. My procedure is as follows: > > 1. boot from custom boot floppy that does not go into /stand/sysinstall but > instead starts /etc/rc script containing just /stand/sh. it also has ifconfig, > mount, ping, route, and dmesg (crunched dmesg isn't working thus no verbose > boot info in this note. i could use some help here too maybe. separate issue). > > 2. boot -c. set port for lnc0 to 0x7000 and continue boot. the > hardware is probed. i see the following: That isn't necessary; the lnc device probes on the PCI bus for you. > > a. pci0:0 is probed but no driver is assigned. (bad sign or not?) No problem. > b. lnc1 shown to be detected even though there is only one interface. this > is immediately after pci0:0 is probed. (hmmm) Standard behavior for PCI Ethernet cards that support both PCI and ISA cards. > c. lnc0 is shown to be detected later on when the rest of the Ethernet > interfaces are looked for. Okay, standard behavior. > 3. /stand/sh is invoked. from command line issue: > > # ifconfig lnc0 161.76.4.7 > > lnc0: Initialisation failed > ^ ^ ^ > (note case and spelling.) Try not changing the I/O port for the lnc device, then try it. > 4. floppies/boot.flp does not work on this system. it appears to hang when > sysinstall would normally display its UI. this is not a problem as it is > possible for me to load the machine manually once the network interface is > configured. it is only a problem in getting verbose boot messages as the > fixit floppy which probably has a working dmesg is not accessible. It happens on my laptop too, I don't know what causes it. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major Spam routed to /dev/null by Procmail | Death to Cyberpromo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970922212010.6177F-100000>