| Title | Date | Comments |
| Kernel Link Failures | 2000 09 | |
- That's a pretty awful feeling, isn't it? You've got to link a new kernel because you need to change a value or needed to add something, and it fails. -
|
| *** !!! nic !!! adding nic !!! *** -->Re adding secondNIC - was Kernel relink error | 1997-2004 | |
- Since we now see "> name=eeE1 vec=- dma=- Scan PCI failed" it's obvious the the reboot DID indicate a problem. Perhaps you don't know that hwconfig collects its info from the last boot? -
|
| netgear kernel link error ngrpci0 -->Re Kernel relinkerror | 1997-2004 | |
- Netgear FA310? cat /etc/conf/node.d/ngrpci0 It's probably corrupt (compare to other node enties). It's hard to imagine a circumstance where rebooting would alleviate kernel linking problems. This sounds like MSOFT voodoo: anything that doesn't work right might be fixed by a reboot. There's no rational reason that I can think of where it could possibly help this. This driver is missing files that are required for linking. It's as simple as that. WHY they are missing is a "who knows"- I've heard of some problems with installing this card but other folks say they have used them. -
|
| link failure tape drive install | 1997-2004 | |
- link failure tape drive install -
|
| pci nic pro100 -->Re adding second NIC - was Kernel relink error | 1997-2004 | |
- Once you have fed the right triplet of numbers to give to SCO netconfig, relink the kernel and reboot. That's as close as you're going to get: either it works then, or the chipset is incompatible with the driver. -
|
| link fails sdevice.d kernel -->Re corrupt /etc/conf --link_unix fails | 1997-2004 | |
- link fails sdevice.d kernel -->Re: corrupt /etc/conf --link_unix fails -
|
| |
| |
|
| |
| |