View Single Post
  #3   (View Single Post)  
Old 9th September 2011
marcv marcv is offline
New User
 
Join Date: Sep 2011
Posts: 5
Default

Quote:
Originally Posted by jggimi View Post
Hello and welcome. Thank you for describing your problem so clearly, and including your dmesg and what you could capture with your camera.
Thanks for the welcome !

Quote:
If I've interpreted it all properly, when you boot the ramdisk kernel (the one used to install the OS), you must always disable ACPI otherwise you often get an invalid opcode fault. When you boot the full kernel (after installation, booting the hard drive) you often get a protection fault trap.
Let me put it another way: without disabling ACPI on the ramdisk kernel I've not been able to boot it properly. However, I get the feeling that it is possible to boot from the ramdisk kernel when ACPI is enabled but that the chances are slim.

Quote:
...
I should ask -- the next time you successfully get the OS running -- check to see if you have any files stored in /var/crash; this directory will store information from a panic on restart, if possible.
Did that - nothing there besides a file called minfree that has the number 4096 in it. I guess it's too early in the boot to write something there ...

Quote:
I am going to make a set of recommendations for you:

1) Try an i386-current snapshot. The -current environment is already a couple of months of development beyond 5.0-release, which is expected November 1. 4.9-release was built in February, so it is possible whatever this is has been fixed between then and now. See your nearest mirror, typically in /pub/OpenBSD/snapshots/i386/.
I'll give it a go.

Quote:
2) Try an amd64 version -- it's the same OS, just a different architecture, and if I read your dmesg correctly, your processor is 64-bit capable. You may get different results. Look in /pub/OpenBSD/4.9/amd64/ and /pub/OpenBSD/snapshots/amd64/
I'll try that too.

Quote:
3) Post a detailed report to the misc@ mailing list. About half of the developers follow it, as well as many technically astute users. You are likely to get some good advice if you approach the list requesting recommendations for assistance. Be sure to post your dmesg in-line with your message (misc@ does not accept attachments), and you may provide a direct link to your .zip you've attached here, as long as you let the list know the link points to photos of the console.

Posts to misc@ (and to all the other mailing lists) need to be plain text, and wrap at around 72 columns. See removed_url_because_of_limitation_as_a_new_user for further information on posting to the lists.
Thanks for the help and recommendations. I'll try the -current snapshot first to see what that gives. If I still get a failure I'll post to the misc@ list.

Regards,

Marc
Reply With Quote