Hey all,
After spending months messing around with FreeBSD in a VM, I decided to finally install it. Naturally, this was not a seamless transition.
Installation was issue free, except for issues getting an IP address through DHCP. I have 2 different NICs, and both silently failed while getting an IP address (and, in fact, required ctrl+c'ing or a hard reboot). After several attempts at installing, I was finally successful using a different install CD. Must have been a CD problem. Rejoice! All is well!
Not as much as I'd hoped. After installation, the problem returns during boot. As this is a headless server, this is a bit problematic. I've tried both interfaces via DHCP and static addresses. When it comes time to assign either of them an IP address (either static or DHCP), the boot process hangs indefinitely. This happens roughly every other time the system is rebooted.
The hang occurs right after the interface is put down and then back up. Not sure why the down/up happens, but I've been unable to stop it from happening (and it happens on successful boots).
If I have a video card/keyboard plugged in, I can interrupt the process of assigning an IP address after it hangs with ctrl+c. This allows the boot to continue. After logging in, I am then able to assign an IP either through DHCP or statically.
Am I overlooking something obvious? Is there a known bug that hasn't turned up in my (fruitless) search?
Relevant (?) command output below:
Sorry if this is in the wrong forum. Feel free to point and laugh if it is. I'd even suffice a solution wherein the system finishes booting and then runs dhclient automatically, although this would make address binding with server daemons a difficult prospect.
Thanks in advance.
After spending months messing around with FreeBSD in a VM, I decided to finally install it. Naturally, this was not a seamless transition.
Installation was issue free, except for issues getting an IP address through DHCP. I have 2 different NICs, and both silently failed while getting an IP address (and, in fact, required ctrl+c'ing or a hard reboot). After several attempts at installing, I was finally successful using a different install CD. Must have been a CD problem. Rejoice! All is well!
Not as much as I'd hoped. After installation, the problem returns during boot. As this is a headless server, this is a bit problematic. I've tried both interfaces via DHCP and static addresses. When it comes time to assign either of them an IP address (either static or DHCP), the boot process hangs indefinitely. This happens roughly every other time the system is rebooted.
The hang occurs right after the interface is put down and then back up. Not sure why the down/up happens, but I've been unable to stop it from happening (and it happens on successful boots).
If I have a video card/keyboard plugged in, I can interrupt the process of assigning an IP address after it hangs with ctrl+c. This allows the boot to continue. After logging in, I am then able to assign an IP either through DHCP or statically.
Am I overlooking something obvious? Is there a known bug that hasn't turned up in my (fruitless) search?
Relevant (?) command output below:
Code:
#pciconf -lv
none0@pci0:0:20:0: class=0x0c0500 card=0x43851043 chip=0x43851002 rev=0x13 hdr=0x00
vendor = 'ATI Technologies Inc'
device = 'IXP SB600 SMBUS Controller'
class = serial bus
subclass = SMBus
isab0@pci0:0:20:3: class=0x060100 card=0x438d1002 chip=0x438d1002 rev=0x00 hdr=0x00
vendor = 'ATI Technologies Inc'
device = 'IXP SB600 PCI to LPC Bridge'
class = bridge
subclass = PCI-ISA
pcib2@pci0:0:20:4: class=0x060401 card=0x00000000 chip=0x43841002 rev=0x00 hdr=0x01
vendor = 'ATI Technologies Inc'
device = 'IXP SB600 PCI to PCI Bridge'
class = bridge
subclass = PCI-PCI
vr0@pci0:2:1:0: class=0x020000 card=0x14061186 chip=0x31061106 rev=0x86 hdr=0x00
vendor = 'VIA Technologies Inc'
device = 'VT6105M/LOM Rhine III PCI Fast Ethernet Controller'
class = network
subclass = ethernet
skc0@pci0:2:4:0: class=0x020000 card=0x811a1043 chip=0x432011ab rev=0x13 hdr=0x00
vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)'
device = 'Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller (Copper)'
class = network
subclass = ethernet
Code:
$dmesg | egrep 'sk0|vr0'
vr0: <VIA VT6105 Rhine III 10/100BaseTX> port 0xe800-0xe8ff mem 0xfbfffc00-0xfbfffcff irq 21 at device 1.0 on pci2
vr0: Quirks: 0x0
vr0: Revision: 0x86
miibus0: <MII bus> on vr0
vr0: Ethernet address: 00:15:e9:82:02:12
vr0: [ITHREAD]
sk0: <Marvell Semiconductor, Inc. Yukon> on skc0
sk0: Ethernet address: 00:1e:8c:72:f2:f2
miibus2: <MII bus> on sk0
vr0: <VIA VT6105 Rhine III 10/100BaseTX> port 0xe800-0xe8ff mem 0xfbfffc00-0xfbfffcff irq 21 at device 1.0 on pci2
vr0: Quirks: 0x0
vr0: Revision: 0x86
miibus0: <MII bus> on vr0
vr0: Ethernet address: 00:15:e9:82:02:12
vr0: [ITHREAD]
sk0: <Marvell Semiconductor, Inc. Yukon> on skc0
sk0: Ethernet address: 00:1e:8c:72:f2:f2
miibus2: <MII bus> on sk0
Sorry if this is in the wrong forum. Feel free to point and laugh if it is. I'd even suffice a solution wherein the system finishes booting and then runs dhclient automatically, although this would make address binding with server daemons a difficult prospect.
Thanks in advance.