Hello Anthony,
I made a few step ahead (at least on my side) and tried to follow the
recommendation from the handbook (
http://www.pl.freebsd.org/doc/handbook/acpi-debug.html).
I was able to turn on the verbose boot and here you can find the output:
http://pastebin.com/kkDAZEVb. At boot time I
Hi Ian,
I have just rebooted the PC after turning the deep debug on. Here is the
output: http://pastebin.com/H61zJhqc. It is very likely that the dmesg has
been cut due to the large amount of output. Is there any way to have it all?
Cheers,
Daniele.
2014-07-15 20:22 GMT+02:00 Ian Smith
On 07/15/2014 13:49, Daniele Mazzotti wrote:
Hello Anthony,
I just noticed that I forgot to answer the part where you proposed me to
patch my ACPI. Unfortunately I am running and AMD 64 architecture and I
do not think this is fitting with what you already patched.
x86-based architectures use
Hi Anthony,
I tried to apply the patch but it seems like 6 out of 7 entries are
dismissed. Is it enough to just type
# cd /usr/src patch path/to/atrtc.c.patch
as root? Shouldn't I recompile anything?
Cheers,
Daniele.
2014-07-15 21:39 GMT+02:00 Anthony Jenkins anthony.b.jenk...@att.net:
What's the error(s)? As root, you should type
cd /usr/src patch path/to/atrtc.c.patch
...the '#' was just an indicator of the root user shell prompt. If it applies
properly, rebuild the kernel and reboot. If not, send your
/usr/src/sys/x86/isa/atrtc.c file and I can manually patch it and
