Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
> during startup message says something like start-up of eth0 delayed (there are > probably log files I should quote???). > I set it up at IRQ 10 and I/O of 0xb800(from PCI bus info)...at shutdown get a > message saying....conflict at that address...I think. > > thanks for the response and interest > Don't assign IRQ's yourself unless you have a need to. Leave the BIOS setup on 'auto' for PCI bus IRQ assignments. The board will report the IRQ it's using to the driver - this is not a configuration parameter. Things to check: 1. In the directory /lib/modules, the file 'preferred' should be a symbolic link to a the directory with the driver modules. If you created your own kernel, this won't be set up correctly. Look at /etc/rc.d/rc.sysinit to see how this is used. 2. The file /etc/conf.modules should have a line to associate the eth0 device with the correct module. The driver module eth0 points to must exist in /lib/modules/preferred/net. 3. You should try debugging the problem by executing the script /etc/sysconfig/network-scripts/ifup eth0 This is the script that's used to turn the interface on during bootstrap - you can execute it after boot as root. Note the lines: # is this device available? (this catches PCMCIA devices for us) /sbin/ifconfig ${REALDEVICE} 2>&1 | grep -s "unknown interface" > /dev/null if [ "$?" = "0" ]; then echo "Delaying ${DEVICE} initialization." exit 0 fi - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |