Re: Odd PCI and ACPI messages on 'INSYDE RSDT_000' laptop
On Mon, Jul 31, 2006 at 12:33:58AM +0200, Ed Schouten wrote: Hello, Last week I got a laptop from a few friends of mine with a broken screen. I removed the screen from the device and connected a regular CRT to it to install FreeBSD 6.1 on it for serving as a jukebox (silent, doesn't consume too much power). I first tried FreeSBIE 1.1, which just deadlocked during the bootsplash. After that I downloaded a FreeBSD 6.1 CD. When I boot FreeBSD 6.1 without the ACPI kernel module, it panics (fatal trap 12) right after probing uhci0. When I boot with ACPI, it boots like it should. Because the laptop doesn't have a serial connector, I didn't copy the kernel backtrace. If it is really needed, I'll boot the CD once again and type over the screen contents. Anyway, I installed FreeBSD 6.1 on it, with the ACPI module loaded, but I still get some really strange messages in my dmesg I thought would be useful to mention: | ... | cpu0: ACPI CPU on acpi0 | acpi_perf0: ACPI CPU Frequency Control on cpu0 | acpi_perf0: failed in PERF_STATUS attach | device_attach: acpi_perf0 attach returned 6 | ... | acpi_perf0: ACPI CPU Frequency Control on cpu0 | acpi_perf0: failed in PERF_STATUS attach | device_attach: acpi_perf0 attach returned 6 | ... This means you can't get configuration for speedstep on this processor via ACPI because something is broken into the bios. But since we have that: CPU: Intel(R) Pentium(R) M processor 1500MHz (1498.73-MHz 686-class CPU) Origin = GenuineIntel Id = 0x695 Stepping = 5 ^^^ speedstep should work if you put: cpufreq_load=YES into /boot/loader.conf and you don't need acpi_perf anyway. -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Odd PCI and ACPI messages on 'INSYDE RSDT_000' laptop
Hello Bruno, * Bruno Ducrot [EMAIL PROTECTED] wrote: This means you can't get configuration for speedstep on this processor via ACPI because something is broken into the bios. But since we have that: CPU: Intel(R) Pentium(R) M processor 1500MHz (1498.73-MHz 686-class CPU) Origin = GenuineIntel Id = 0x695 Stepping = 5 ^^^ speedstep should work if you put: cpufreq_load=YES into /boot/loader.conf and you don't need acpi_perf anyway. I built the cpufreq module and rebooted. I now have an est0 and p4tcc0 device. Powerd now sets the processor to a lower clockrate. Thanks a lot! Yours, -- Ed Schouten [EMAIL PROTECTED] WWW: http://g-rave.nl/ pgp1ecVq3zNXK.pgp Description: PGP signature
Re: Odd PCI and ACPI messages on 'INSYDE RSDT_000' laptop
On Sunday 30 July 2006 18:33, Ed Schouten wrote: Hello, Last week I got a laptop from a few friends of mine with a broken screen. I removed the screen from the device and connected a regular CRT to it to install FreeBSD 6.1 on it for serving as a jukebox (silent, doesn't consume too much power). I first tried FreeSBIE 1.1, which just deadlocked during the bootsplash. After that I downloaded a FreeBSD 6.1 CD. When I boot FreeBSD 6.1 without the ACPI kernel module, it panics (fatal trap 12) right after probing uhci0. When I boot with ACPI, it boots like it should. Because the laptop doesn't have a serial connector, I didn't copy the kernel backtrace. If it is really needed, I'll boot the CD once again and type over the screen contents. Anyway, I installed FreeBSD 6.1 on it, with the ACPI module loaded, but I still get some really strange messages in my dmesg I thought would be useful to mention: | ... | cpu0: ACPI CPU on acpi0 | acpi_perf0: ACPI CPU Frequency Control on cpu0 | acpi_perf0: failed in PERF_STATUS attach | device_attach: acpi_perf0 attach returned 6 | ... | acpi_perf0: ACPI CPU Frequency Control on cpu0 | acpi_perf0: failed in PERF_STATUS attach | device_attach: acpi_perf0 attach returned 6 | ... And these: | ... | pci_link0: BIOS IRQ 11 for 0.2.INTA is invalid | pci_link1: BIOS IRQ 5 for 0.31.INTB is invalid | ... | pci_link4: BIOS IRQ 11 for 1.0.INTA is invalid | pci_link5: BIOS IRQ 11 for 1.1.INTA is invalid | ... The device Just Works at the moment, so I can live with it, but I was wondering if these messages do any harm. I've attached the entire dmesg of the device for those who are interested. If your machine works, then don't worry about the pci_link messages. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
