Re: FreeBSD 5.3 Boot issues - reposted
On Saturday 21 May 2005 03:42, the author Thomas Hurst contributed to the dialogue on Re: FreeBSD 5.3 Boot issues - reposted: * Vizion ([EMAIL PROTECTED]) wrote: This system has been built in a mini ATX case and has a Proxim Harmony 802.11a Model 8150 PCI card on (I am on a boat - then intention is to be able to disconnect it from the ships network, lug it to a position in range of a wireless network and do a portupgrade as the need arises chuckles). Is this card recognized by freebsd. Is there a suitable driver? How do I set it up? Looks like it's based on the Prism2 chipset, which should be supported by the wi(4) driver (man wi). kldload if_wi and see if it's detected, and follow the examples in the driver manpage to set it up. Aha -- actually I found it is based on the Atheros chips BUT is configured on the pci card to be recognized as fw!!! anyway your input made me get the card out and I now have it working.. Thanks David -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing May bound for Europe via Panama Canal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.3 Boot issues - reposted
* Vizion ([EMAIL PROTECTED]) wrote: This system has been built in a mini ATX case and has a Proxim Harmony 802.11a Model 8150 PCI card on (I am on a boat - then intention is to be able to disconnect it from the ships network, lug it to a position in range of a wireless network and do a portupgrade as the need arises chuckles). Is this card recognized by freebsd. Is there a suitable driver? How do I set it up? Looks like it's based on the Prism2 chipset, which should be supported by the wi(4) driver (man wi). kldload if_wi and see if it's detected, and follow the examples in the driver manpage to set it up. 2. Uhicio [GIANT LOCKED] What does this mean? It means the uhci (USB Host Controller) driver isn't multi-processor safe, and thus needs to grab the Big Giant Lock around the kernel when it's doing stuff to operate safely. Don't worry about it; if you really want to get rid of it, it looks like it's been made MPSAFE in 5.4. 3. (da1:umass-sim0:0:0:1): Unretryable error What is the significance if any of these lines? USB mass storage devices use the SCSI Direct Access (da) driver. You don't have any memory cards in your card reader, so attempts to read from them to determine the size of the disks are producing an unretryable error. Again, this is normal. 4. I want to use energy saving (mainly to protect the drive from unnecessary risk of damage in rough weather) to turn off the hard drive when access is not required. How do I do that? Look at sysutils/ataidle. Taking measures to avoid unnecessary disk access is left as an exercise for the reader ;) -- Thomas 'Freaky' Hurst http://hur.st/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.3 Boot issues - reposted
On Saturday 21 May 2005 03:42, the author Thomas Hurst contributed to the dialogue on Re: FreeBSD 5.3 Boot issues - reposted: * Vizion ([EMAIL PROTECTED]) wrote: This system has been built in a mini ATX case and has a Proxim Harmony 802.11a Model 8150 PCI card on (I am on a boat - then intention is to be able to disconnect it from the ships network, lug it to a position in range of a wireless network and do a portupgrade as the need arises chuckles). Is this card recognized by freebsd. Is there a suitable driver? How do I set it up? Looks like it's based on the Prism2 chipset, which should be supported by the wi(4) driver (man wi). kldload if_wi and see if it's detected, and follow the examples in the driver manpage to set it up. 2. Uhicio [GIANT LOCKED] What does this mean? It means the uhci (USB Host Controller) driver isn't multi-processor safe, and thus needs to grab the Big Giant Lock around the kernel when it's doing stuff to operate safely. Don't worry about it; if you really want to get rid of it, it looks like it's been made MPSAFE in 5.4. 3. (da1:umass-sim0:0:0:1): Unretryable error What is the significance if any of these lines? USB mass storage devices use the SCSI Direct Access (da) driver. You don't have any memory cards in your card reader, so attempts to read from them to determine the size of the disks are producing an unretryable error. Again, this is normal. 4. I want to use energy saving (mainly to protect the drive from unnecessary risk of damage in rough weather) to turn off the hard drive when access is not required. How do I do that? Look at sysutils/ataidle. Taking measures to avoid unnecessary disk access is left as an exercise for the reader ;) Thankl you very much for a very helpful posting David -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing May bound for Europe via Panama Canal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.3 Boot issues - reposted
I hope noone minds but as I have not had a reply I thought I would repost hoping that someone would pick up the thread. Thanks David Original follows: - Hi Below is the output from dmesg.boot I have some questions: 1. re: 802.11a This system has been built in a mini ATX case and has a Proxim Harmony 802.11a Model 8150 PCI card on (I am on a boat - then intention is to be able to disconnect it from the ships network, lug it to a position in range of a wireless network and do a portupgrade as the need arises chuckles). Is this card recognized by freebsd. Is there a suitable driver? How do I set it up? 2. Uhicio [GIANT LOCKED] What does this mean? 3. (da1:umass-sim0:0:0:1): Unretryable error What is the significance if any of these lines? 4. I want to use energy saving (mainly to protect the drive from unnecessary risk of damage in rough weather) to turn off the hard drive when access is not required. How do I do that? Copyright (c) 1992-2004 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 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) XP (1593.55-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x6a0 Stepping = 0 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc048MP,AMIE,DSP,3DNow! real memory = 1006567424 (959 MB) avail memory = 975376384 (930 MB) ACPI APIC Table: KM400A AWRDACPI ioapic0 Version 0.3 irqs 0-23 on motherboard npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: KM400A AWRDACPI on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 cpu0: ACPI CPU (3 Cx states) on acpi0 acpi_tz0: Thermal Zone on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: VIA Generic host to PCI bridge mem 0xd000-0xd7ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) pci0: network, ethernet at device 9.0 (no driver attached) fwohci0: Texas Instruments TSB43AB23 mem 0xde01-0xde013fff,0xde014000-0xde0147ff irq 18 at device 10.0 on pci0 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:d0:03:56:00:b2:b7:e6 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: IEEE1394(FireWire) bus on fwohci0 fwe0: Ethernet over FireWire on firewire0 if_fwe0: Fake Ethernet address: 02:d0:03:b2:b7:e6 fwe0: Ethernet address: 02:d0:03:b2:b7:e6 fwe0: if_start running deferred for Giant sbp0: SBP-2/SCSI over FireWire on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop = 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) atapci0: VIA 6420 SATA150 controller port 0xa400-0xa4ff,0xa000-0xa00f,0x9c00-0x9c03,0x9800-0x9807,0x9400-0x9403,0x9000-0x9007 irq 20 at device 15.0 on pc i0 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 atapci1: VIA 8237 UDMA133 controller port 0xa800-0xa80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 ata0: channel #0 on atapci1 ata1: channel #1 on atapci1 uhci0: VIA 83C572 USB controller port 0xac00-0xac1f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] usb0: VIA 83C572 USB controller on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: VIA 83C572 USB controller port 0xb000-0xb01f irq 21 at device 16.1 on pci0 uhci1: [GIANT-LOCKED] usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: VIA 83C572 USB controller port 0xb400-0xb41f irq 21 at device 16.2 on pci0 uhci2: [GIANT-LOCKED] usb2: VIA 83C572 USB controller on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered umass0: USB2.0 CardReader, rev 2.00/91.38, addr 2 uhci3: VIA 83C572 USB controller port 0xb800-0xb81f irq 21 at device 16.3 on pci0 uhci3: [GIANT-LOCKED] usb3: VIA 83C572 USB controller on uhci3 usb3: USB revision 1.0 uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci0: serial bus, USB at device 16.4 (no driver attached) isab0: PCI-ISA bridge at device 17.0 on pci0 isa0: ISA bus on isab0 pci0: multimedia, audio at device 17.5 (no driver attached) vr0: VIA VT6102 Rhine II 10/100BaseTX port 0xc400-0xc4ff mem
FreeBSD 5.3 Boot issues
Hi Below is the output from dmesg.boot I have some questions: 1. re: 802.11a This system has been built in a mini ATX case and has a Proxim Harmony 802.11a Model 8150 PCI card on (I am on a boat - then intention is to be able to disconnect it from the ships network, lug it to a position in range of a wireless network and do a portupgrade as the need arises chuckles). Is this card recognized by freebsd. Is there a suitable driver? How do I set it up? 2. Uhicio [GIANT LOCKED] What does this mean? 3. (da1:umass-sim0:0:0:1): Unretryable error What is the significance if any of these lines? 4. I want to use energy saving (mainly to protect the drive from unnecessary risk of damage in rough weather) to turn off the hard drive when access is not required. How do I do that? Copyright (c) 1992-2004 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 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) XP (1593.55-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x6a0 Stepping = 0 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc048MP,AMIE,DSP,3DNow! real memory = 1006567424 (959 MB) avail memory = 975376384 (930 MB) ACPI APIC Table: KM400A AWRDACPI ioapic0 Version 0.3 irqs 0-23 on motherboard npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: KM400A AWRDACPI on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 cpu0: ACPI CPU (3 Cx states) on acpi0 acpi_tz0: Thermal Zone on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: VIA Generic host to PCI bridge mem 0xd000-0xd7ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) pci0: network, ethernet at device 9.0 (no driver attached) fwohci0: Texas Instruments TSB43AB23 mem 0xde01-0xde013fff,0xde014000-0xde0147ff irq 18 at device 10.0 on pci0 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:d0:03:56:00:b2:b7:e6 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: IEEE1394(FireWire) bus on fwohci0 fwe0: Ethernet over FireWire on firewire0 if_fwe0: Fake Ethernet address: 02:d0:03:b2:b7:e6 fwe0: Ethernet address: 02:d0:03:b2:b7:e6 fwe0: if_start running deferred for Giant sbp0: SBP-2/SCSI over FireWire on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop = 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) atapci0: VIA 6420 SATA150 controller port 0xa400-0xa4ff,0xa000-0xa00f,0x9c00-0x9c03,0x9800-0x9807,0x9400-0x9403,0x9000-0x9007 irq 20 at device 15.0 on pc i0 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 atapci1: VIA 8237 UDMA133 controller port 0xa800-0xa80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 ata0: channel #0 on atapci1 ata1: channel #1 on atapci1 uhci0: VIA 83C572 USB controller port 0xac00-0xac1f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] usb0: VIA 83C572 USB controller on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: VIA 83C572 USB controller port 0xb000-0xb01f irq 21 at device 16.1 on pci0 uhci1: [GIANT-LOCKED] usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: VIA 83C572 USB controller port 0xb400-0xb41f irq 21 at device 16.2 on pci0 uhci2: [GIANT-LOCKED] usb2: VIA 83C572 USB controller on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered umass0: USB2.0 CardReader, rev 2.00/91.38, addr 2 uhci3: VIA 83C572 USB controller port 0xb800-0xb81f irq 21 at device 16.3 on pci0 uhci3: [GIANT-LOCKED] usb3: VIA 83C572 USB controller on uhci3 usb3: USB revision 1.0 uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci0: serial bus, USB at device 16.4 (no driver attached) isab0: PCI-ISA bridge at device 17.0 on pci0 isa0: ISA bus on isab0 pci0: multimedia, audio at device 17.5 (no driver attached) vr0: VIA VT6102 Rhine II 10/100BaseTX port 0xc400-0xc4ff mem 0xde016000-0xde0160ff irq 23 at device 18.0 on pci0 miibus0: MII bus on vr0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet address:
