Hi all,
I have a legacy system --- 4xXeon (PIII, 700MHz, 2MB cache), 16GB ECC
RAM and 300GB Harddisk on an ICP Vortex Raid Controller --- which I
tried to bring from RedHat6 to something more current and supported.
(Un)Fortunately the only system that wanted to install on the machine is
Jason C. Wells wrote this message on Thu, Aug 25, 2005 at 16:43 -0700:
Is there a way to run TCP/IP with the PCI bus as a network interface?
You'd have to write your own driver to do it...
I am installing FreeBSD on CompactPCI processor boards. It would be really
slick if I could network
Is there a way to run TCP/IP with the PCI bus as a network interface?
I am installing FreeBSD on CompactPCI processor boards. It would be really
slick if I could network the boards via the PCI backplane.
Thanks,
Jason C. Wells
___
freebsd-stable
But now I am getting spontaneous rebooting of the computer.
I'm seeing the same on my Thinkpad T22 -- pccard works again, but the
machine's spontaneously rebooting after a while when I use a pcmcia
WaveLAN card. It's a bit unfortunate. It doesn't reboot if I use the
mini-PCI fxp card,
I recently cvsuped one of my 4.3 stable boxes and now there
is no PCI bus and no fxp interfaces.(or any other that are on the pci)
If I boot an older kernel the bus is found. If I boot
the new 4.4 code it is not found. I have the device for pci
etc in the new kernel build. Something here
On Wed, Aug 22, 2001 at 06:28:44PM -0400, Mike wrote:
There was a bug yesterday (IIRC) that in the mean time has been fixed.
re-cvsup and things should be OK again
W/
I recently cvsuped one of my 4.3 stable boxes and now there
is no PCI bus and no fxp interfaces.(or any other
The PCI spec basicly states that buses are to be probed depth first. As a
PCI bridge is found, it is assigned the next sequential bus number and
probed for additional bridges beyond it. As a new bridge is found, all the
parent bridges' subordinat bus number register is updated to the
From: "Fred Clift" [EMAIL PROTECTED]
Hm so does that mean that non-bridge devices on those busses should also
be done depth first? I understand wanting to find all the busses first,
but devices too? All the bioses I've seen seem to find all the busses,
then assign resources to devices