Panagiotis Astithas wrote: > Jon Noack wrote: > >> On 1/29/2004 6:02 AM, Panagiotis Astithas wrote: >> >>> I found out that booting with "Safe mode" (I knew there should be >>> some use for it :-)) allows me to complete the process and get to >>> sysinstall, in both 5.2-RELEASE & the -current snapshot from 24/1. >>> But I tried to do the same from the loader prompt, to no avail. I >>> used the following and then "boot" or "boot -v" but every attempt >>> resulted in the traditional freeze. >>> >>> unset acpi_load >>> set hint.acpi.0.disabled=1 >>> set loader.acpi_disabled_by_user=1 >>> set hw.ata.ata_dma=0 >>> set hw.ata.atapi_dma=0 >>> set hw.ata.wc=0 >>> set hw.eisa_slots=0 >>> >>> From what I can tell from the beastie.4th file, that is all that >>> should be needed. Am I missing something? >> >> >> >> You missed disabling apic: >> set hint.apic.0.disabled=1 > > > Bingo! > But I still can't see how it is being set via the loader's "Safe mode" > option. Granted, my forth skills are lacking, but an inquiring mind > needs to know :-) > > Thanks, Look for this segment in beastie.4th: dup bootsafekey _at_ = if s" arch-i386" environment? if s" acpi_load" unsetenv s" 1" s" hint.acpi.0.disabled" setenv s" 1" s" loader.acpi_disabled_by_user" setenv ----> s" 1" s" hint.apic.0.disabled" setenv then s" 0" s" hw.ata.ata_dma" setenv s" 0" s" hw.ata.atapi_dma" setenv s" 0" s" hw.ata.wc" setenv s" 0" s" hw.eisa_slots" setenv 0 boot thenReceived on Mon Feb 02 2004 - 00:29:00 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:41 UTC