# ~jhs/src/bsd/fixes/FreeBSD/src/jhs/boot/loader.conf.master {A # /host/lapa/boot/loader.conf - for lapa aci }A {D # /host/lapd/boot/loader.conf - for lapd digital Ultra 2000 # Later manually to be copied periodically to # ~jhs/public_html/hardware/digital/loader.conf }D {L # /host/lapl/boot/loader.conf - for lapl libretto toshiba # To be copied periodically to # ~jhs/public_html/hardware/toshiba/libretto/boot/loader.conf }L {S # /host/laps/boot/loader.conf - for laps satellite toshiba # To be copied periodically to # ~jhs/public_html/hardware/toshiba/satellite.s5100-603/loader.conf }S # See also /boot/defaults/loader.conf # See Also: # man acpi # man sysctl # sysctl -a # shows all values # sysctl -a -d # Print description instead of value userconfig_script_load="YES" debug.bootverbose=1 # A `sysctl` variable. # Default 0 {L # Astrid's 50CT & Julian 70CT both boot without anything below here. }L {A hw.pcic.intr_path="1" hw.pcic.irq="0" }A {S hw.acpi.verbose=1 # A `man acpi` variable, not a `man sysctl` variable. }S {S hw.pci.enable_io_modes=0 }S # 5.5 may not need this. # A `sysctl` variable. # Without hw.pci.enable_io_modes=0 boot hangs after agp. # sysctl -d says: # Enable I/O and memory bits in the config register. # Some BIOSes do not enable these bits correctly. # We'd like to do this all the time, but there are # Without hw.pci.enable_io_modes=0 boot hangs after agp on some # machine other than lapl. # Enable I/O and memory bits in the config register. # Some BIOSes do not enable these bits correctly. # We'd like to do this all the time, but there are # hw.pcic.intr_path="1" # host=lapa: hw.pcic.intr_path="1" # sysctl -a -d: # hw.pcic.intr_path: Which path to send the interrupts over. # Normally interrupts for # cardbus bridges are routed over the PCI bus (2). However, some laptops # will hang when using PCI interrupts due to bugs in this code. Those # bugs can be worked around by forcings ISA interrupts (1). # Warner wrote: # L-50 and L-70 machines have only ISA PCMICA bridges # This is also not a Cardbus. # host=lapa: hw.pcic.irq="0" # hw.pcic.irq="0" # sysctl -a -d: # hw.pcic.irq: Override the IRQ configured by the config system for all pcic devices # Not in defaults/loaders.conf # machdep.pccard.pcic_irq="0" # Assigns PCCARD controller IRQ (0=polled) # defaults/loaders.conf: (commented out) Assigns PCCARD controller IRQ (0=polled) # machdep.pccard.pcic_irq=11 # lapa demsg reports: # pccard0: on pcic0 # pccard1: on pcic0 # so although one bay, looks like s/ware provision for 2 ? # machdep.bios.pci=disable # not in defaults/loader.conf: machdep.bios.pci=disable # machdep.bios.pnp=disable # not in defaults/loader.conf: machdep.bios.pnp=disable # sysctl -a -d: # hw.pcic.init_routing: Force the interrupt routing to be # initialized on those bridges where doing so will cause # probelms. This is very rare and generally is not needed. # The default of 0 is almost always appropriate. Only set # to 1 if instructed to do so for debugging. Only TI bridges # are affected by this option, and what the code does is of # dubious value. This option is obsolete and will be deleted # before FreeBSD 4.8. # sysctl -a -d: # hw.pcic.ignore_pci: When set, driver ignores pci cardbus bridges # it would otherwise claim. # Generally speaking, this option is not needed for anything other # than as an aid in debugging. # sysctl -a -d: # hw.pcic.pd6729_intr_path: Determine the interrupt path or method for Cirrus Logic PD6729 and # similar I/O space based pcmcia bridge. Chips on a PCI expansion card need # a value of 2, while chips installed in a laptop need a value of 1 (which is # also the default). This is similar to hw.pcic.intr_path, but separate so # that it can default to ISA when intr_path defaults to PCI. # sysctl -a -d: # hw.pcic.ti12xx_enable_pci_clock: Some TI-12xx parts need to have the PCI clock enabled. These designs do # not provide a clock themselves. Most of the reference boards have the # required oscillator parts, so the number of machines that needs this to be # set is vanishingly small. # debug.acpi.avoid= # where is this from ? # debug.acpi.disable # A `man acpi` variable, not a `man sysctl` variable. # Selectively disables portions of ACPI for debugging purposes. # hint.acpi.0.disabled=0 # Hashed 10.12.200 # A `man acpi` variable, not a `man sysctl` variable. # On 5.2.1-RELEASE & 5.2.1-RELEASE-p9, & without this, # sometimes it wont even boot & if it does, xdm will crash # on start, & xinit will crash on exit. hint.acpi.0.disabled=1 # makes fxp far too damn slow or intermittently dead, but so # does manually booting with option 2: no acpi # hw.acpi.reset_video=0 # hw.fxp_rnr= # A `sysctl` variable. # default: 1 fxp rnr events # hw.fxp0.bundle_max: 6 # A `sysctl` variable. # hw.fxp0.int_delay: 1000 # A `sysctl` variable. # hw.fxp_noflow=1 # Hashed 10.12.200 # A `sysctl` variable. # was 0 by default, but was timing out after running a while multi user. # so now experimentally turned on. # however, interface still times out during boot # I havent run long & hard multi user to test it properly #machdep.hlt_logical_cpus=1 # Message-id: <200505131525.j4DFP0pR029309@freefall.freebsd.org> # Avoid multi CPU snooping of ssh keys # using HIT = "Hyper-Threading Technology" on # Intel Pentium 4, Mobile Pentium 4, and Xeon processors. # After patching kernel: # For users that are certain that their environment is not affected # by this vulnerability, such as single-user systems, Hyper-Threading # Technology may be re-enabled by setting the tunable # "machdep.hyperthreading_allowed".` # on 5.4-RELEASE-p1 Janet Sullivan wrote: # I am unable to get my DVD or CD drives out of PIO4 mode on two machines. # One has an ICH3 controller, the other is Nforce2 based. # When I put hw.ata.atapi_dma="1" in /boot/loader.conf and reboot, I'm # still stuck in PIO4. What am I doing wrong? #------ # From: Michael Nottebrock # The drives probably don't support any UDMA modes. WDMA modes aren't enabled # for atapi devices because there's a very large number of devices which don't # implement them right or not at all, yet claim to support them. # # You can enable whatever DMA modes those drives support with the atacontrol # utility after the kernel has booted up. # ---- # That was it. The drives only support WDMA modes. Thanks! # ---- # From: Holger Kipp # Have you tried something like # # atacontrol mode 1 UDMA6 UDMA6 # # to change the mode to the highest values possible? # # I have # katrin# atacontrol info 1 # Master: acd0 ATA/ATAPI revision 5 # Slave: acd1 ATA/ATAPI revision 0 # katrin# atacontrol info 0 # Master: ad0 ATA/ATAPI revision 7 # Slave: ad1 ATA/ATAPI revision 7 # # with # # katrin# atacontrol mode 1 # Master = UDMA33 # Slave = PIO4 # # after boot and end up with # # katrin# atacontrol mode 1 UDMA6 UDMA6 # Master = UDMA33 # Slave = WDMA2 # # Usually I only use acd0, so I didn't care (real life runs # at a higher priority right now).