>Randomly disabling things during boot is a sure way to make things even worse.
>
>Good luck.
>
>-ml

I admit it was a wild guess but it paid off. Disabling acpi lead me to 
eventually booting the OS compared to not having the ability to do so.
And correct me if im mistaken but is there a way to find out the exact error if 
its not verbosed. I was too busy setting up my system to look further into 
dmseg.I will try to do that later and report a bug if I find something out.

I now have a functiong system and x worked automagically after the radeondrm 
worked.
I also found out x window system setup question is skipped if 
machdep.allowaperture=2. I believe this is done auto. So all is good.

Sent from ProtonMail mobile

-------- Original Message --------
On 26 Sep 2018, 11:57, Mike Larkin wrote:

> On Tue, Sep 25, [2018](tel:2018) at 05:30:15PM +0000, Dr.Boutari wrote:
>> Thanks for the on point help, and again excuse my ignorance at some 
>> parts.See bottom for a conclusion of my trial results.
>>
>> 1.As per your instructions updated my laptop's firmware, but that didnt 
>> help. I still got a shutdown crash on booting from the installer cd.amd64 
>> openbsd 6.3
>>
>> Last verbose before crash is "root on rd0a swap on rd0b dump on rd0b''
>> So it probably doesnt give any error message at this stage before the sudden 
>> crash.
>>
>> (Please ignore the message I sent in my 2nd email. That was actually the 
>> error booting after installation with disable acpi but no disable radeondrm)
>>
>> 2.Retry install. Boot -c then disable acpi and continue install successfully 
>> like last time. Did syspatch & fw_update. Restarted still same shutdown 
>> crash if acpi isnt disabled.
>> Disabling acpi without disabling radeondrm gets the kernel panic with errors 
>> I sent you in the first email+trace+pf.
>>
>
> Randomly disabling things during boot is a sure way to make things even worse.
>
> Good luck.
>
> -ml
>
>> 3.Since im ok with disabling acpi and radeon permenantly and only running x 
>> with vesa driver and openbox I continued but that still fails and I cant 
>> startx.
>>
>> I retraced my steps and found a weird bug. If I issue disable acpi when 
>> loading the installer cd the question : ''Do you expect to run the x window 
>> system?'' Doesnt show up. It took me sometime to notice this, because I was 
>> looking for an error related to xorg. I dont know what configuration is done 
>> behind the scenes with this prompt, but Ill try to setup x manually and see 
>> if it works.
>>
>> 4.Moving system to current branch.
>> Booting bsd.rd gives shutdown crash again.
>> Rebooted boot bsd.rd -c then disable acpi. Continued system upgrade to 
>> latest snapshot.
>> Upgrade done. Rebooted without disabling acpi or radeon,shutdown crash 
>> again.Reboot disable acpi only. No more kernel panic like before and the vga 
>> radeon firmware was autoinstalled.
>>
>> In conclusion
>>
>> 1. Upgrading to current snapshot solved the radeondrm related kernel crash.
>>
>> 2.Shutdown crash without any error messages related to acpi persisted along 
>> 3 branches.
>>
>> 3. Installer bug skips x window system setup question if you issue disable 
>> acpi when booting from installer cd.
>>
>> Thanks.
>>
>> Sent from ProtonMail mobile

Reply via email to