Re: 9.1 - new install questions
Hi, I don't often comment here and don't really have much to add in this case but; What have you tried to discover the answers to your questions? I just noticed that this post seemed to have been missed. some leads might be: http://www.freebsd.org/releases/9.1R/relnotes.html http://tools.ietf.org/html/rfc4862 - have a good day, 'a5 > I just installed 9.1 on a clean disk. The dmesg is at the end of this > message. > > > > For the network configuration, I selected DHCP for IPv4 and SLAAC for > IPv6. When I boot the PC, it appears that dhclient tries to load > twice. Why does it try to load the second time? > >>From the console log: > > May 18 17:53:15 a31p kernel: Starting dhclient. > May 18 17:53:15 a31p kernel: DHCPREQUEST on fxp0 to 255.255.255.255 > port 67 > May 18 17:53:15 a31p kernel: DHCPREQUEST on fxp0 to 255.255.255.255 > port 67 > May 18 17:53:15 a31p kernel: DHCPACK from 10.20.1.1 > May 18 17:53:15 a31p kernel: bound to 10.20.2.14 -- renewal in 36 > seconds. > May 18 17:53:15 a31p kernel: dhclient already running? (pid=1233). > > > > > > > Also during the boot process, but earlier, is this message: > > (aprobe0:ata1:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 > 00 00 00 > (aprobe0:ata1:0:1:0): CAM status: Command timeout > (aprobe0:ata1:0:1:0): Error 5, Retry was blocked > run_interrupt_driven_hooks: still waiting after 60 seconds for > xpt_config > (aprobe0:ata1:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 > 00 00 00 > (aprobe0:ata1:0:1:0): CAM status: Command timeout > (aprobe0:ata1:0:1:0): Error 5, Retry was blocked > > > > What is that trying to tell me? The disk appears to work fine, i.e., > 9.1 loads up and runs OK. The above adds significantly to the boot > time. If it is just informational, is there a way to bypass it? > > > Thanks. > > > > > > dmesg: > > Copyright (c) 1992-2012 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 9.1-RELEASE #0 r243826: Tue Dec 4 06:55:39 UTC 2012 > [email protected]:/usr/obj/usr/src/sys/GENERIC i386 > CPU: Intel(R) Pentium(R) 4 Mobile CPU 1.70GHz (1698.61-MHz 686-class > CPU) > Origin = "GenuineIntel" Id = 0xf24 Family = f Model = 2 Stepping > = 4 > Features=0x3febf9ff A,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM> > real memory = 1073741824 (1024 MB) > avail memory = 1031213056 (983 MB) > kbd1 at kbdmux0 > ctl: CAM Target Layer loaded > acpi0: on motherboard > acpi_ec0: port 0x62,0x66 on acpi0 > acpi0: Power Button (fixed) > acpi0: reservation of 0, a (3) failed > acpi0: reservation of 10, 3ff0 (3) failed > cpu0: on acpi0 > attimer0: port 0x40-0x43 irq 0 on acpi0 > Timecounter "i8254" frequency 1193182 Hz quality 0 > Event timer "i8254" frequency 1193182 Hz quality 100 > atrtc0: port 0x70-0x71 irq 8 on acpi0 > Event timer "RTC" frequency 32768 Hz quality 0 > Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 > acpi_lid0: on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > agp0: on hostb0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > vgapci0: port 0x3000-0x30ff mem > 0xe800-0xefff,0xd010-0xd010 irq 11 at device 0.0 on > pci1 > uhci0: port > 0x1800-0x181f irq 11 at device 29.0 on pci0 > usbus0 on uhci0 > uhci1: port > 0x1820-0x183f irq 11 at device 29.1 on pci0 > usbus1 on uhci1 > uhci2: port > 0x1840-0x185f irq 11 at device 29.2 on pci0 > usbus2 on uhci2 > pcib2: at device 30.0 on pci0 > pci2: on pcib2 > cbb0: mem 0x5000-0x5fff irq 11 at > device 0.0 on pci2 > cardbus0: on cbb0 > pccard0: <16-bit PCCard bus> on cbb0 > cbb1: mem 0x5010-0x50100fff irq 11 at > device 0.1 on pci2 > cardbus1: on cbb1 > pccard1: <16-bit PCCard bus> on cbb1 > fwohci0: mem 0xd0201000-0xd02017ff irq 11 at device 0.2 > on pci2 > fwohci0: OHCI version 1.0 (ROM=0) > fwohci0: No. of Isochronous channels is 4. > fwohci0: EUI64 00:06:1b:00:10:00:6d:38 > fwohci0: Phy 1394a available S400, 2 ports. > fwohci0: Link S400, max_rec 2048 bytes. > firewire0: on fwohci0 > fwe0: on firewire0 > if_fwe0: Fake Ethernet address: 02:06:1b:00:6d:38 > fwe0: Ethernet address: 02:06:1b:00:6d:38 > fwip0: on firewire0 > fwip0: Firewire address: 00:06:1b:00:10:00:6d:38 @ 0xfffe, > S400, maxrec 2048 > dcons_crom0: on firewire0 > dcons_crom0: bus_addr 0x14a > fwohci0: Initiate bus reset > fwohci0: fwohci_intr_core: BUS reset > fwohci0: fwohci_intr_core: node_id=0x, SelfID Count=1, > CYCLEMASTER mode > fxp0: port 0x8000-0x803f > mem 0xd020-0xd0200fff irq 11 at device 8.0 on pci2 > miibus0: on fxp0 > inphy0: PHY 1 on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, > auto-flow > fxp0: Ethernet address: 00:
9.1 - new install questions
I just installed 9.1 on a clean disk. The dmesg is at the end of this message. For the network configuration, I selected DHCP for IPv4 and SLAAC for IPv6. When I boot the PC, it appears that dhclient tries to load twice. Why does it try to load the second time? >From the console log: May 18 17:53:15 a31p kernel: Starting dhclient. May 18 17:53:15 a31p kernel: DHCPREQUEST on fxp0 to 255.255.255.255 port 67 May 18 17:53:15 a31p kernel: DHCPREQUEST on fxp0 to 255.255.255.255 port 67 May 18 17:53:15 a31p kernel: DHCPACK from 10.20.1.1 May 18 17:53:15 a31p kernel: bound to 10.20.2.14 -- renewal in 36 seconds. May 18 17:53:15 a31p kernel: dhclient already running? (pid=1233). Also during the boot process, but earlier, is this message: (aprobe0:ata1:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 00 00 00 (aprobe0:ata1:0:1:0): CAM status: Command timeout (aprobe0:ata1:0:1:0): Error 5, Retry was blocked run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config (aprobe0:ata1:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 00 00 00 (aprobe0:ata1:0:1:0): CAM status: Command timeout (aprobe0:ata1:0:1:0): Error 5, Retry was blocked What is that trying to tell me? The disk appears to work fine, i.e., 9.1 loads up and runs OK. The above adds significantly to the boot time. If it is just informational, is there a way to bypass it? Thanks. dmesg: Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.1-RELEASE #0 r243826: Tue Dec 4 06:55:39 UTC 2012 [email protected]:/usr/obj/usr/src/sys/GENERIC i386 CPU: Intel(R) Pentium(R) 4 Mobile CPU 1.70GHz (1698.61-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Family = f Model = 2 Stepping = 4 Features=0x3febf9ff real memory = 1073741824 (1024 MB) avail memory = 1031213056 (983 MB) kbd1 at kbdmux0 ctl: CAM Target Layer loaded acpi0: on motherboard acpi_ec0: port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3ff0 (3) failed cpu0: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: on hostb0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0x3000-0x30ff mem 0xe800-0xefff,0xd010-0xd010 irq 11 at device 0.0 on pci1 uhci0: port 0x1800-0x181f irq 11 at device 29.0 on pci0 usbus0 on uhci0 uhci1: port 0x1820-0x183f irq 11 at device 29.1 on pci0 usbus1 on uhci1 uhci2: port 0x1840-0x185f irq 11 at device 29.2 on pci0 usbus2 on uhci2 pcib2: at device 30.0 on pci0 pci2: on pcib2 cbb0: mem 0x5000-0x5fff irq 11 at device 0.0 on pci2 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb1: mem 0x5010-0x50100fff irq 11 at device 0.1 on pci2 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 fwohci0: mem 0xd0201000-0xd02017ff irq 11 at device 0.2 on pci2 fwohci0: OHCI version 1.0 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:06:1b:00:10:00:6d:38 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:06:1b:00:6d:38 fwe0: Ethernet address: 02:06:1b:00:6d:38 fwip0: on firewire0 fwip0: Firewire address: 00:06:1b:00:10:00:6d:38 @ 0xfffe, S400, maxrec 2048 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x14a fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x, SelfID Count=1, CYCLEMASTER mode fxp0: port 0x8000-0x803f mem 0xd020-0xd0200fff irq 11 at device 8.0 on pci2 miibus0: on fxp0 inphy0: PHY 1 on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow fxp0: Ethernet address: 00:0e:9b:2c:c7:f6 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1860-0x186f at device 31.1 on pci0 ata0: at channel 0 on atapci0 ata1: at channel 1 on atapci0 pci0: at device 31.3 (no driver attached) pcm0: port 0x1c00-0x1cff,0x18c0-0x18ff irq 11 at device 31.5 on pci0 pcm0: pci0: at device 31.6 (no driver attached) acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
