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 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: on acpi0 > | acpi_perf0: on cpu0 > | acpi_perf0: failed in PERF_STATUS attach > | device_attach: acpi_perf0 attach returned 6 > | ... > | acpi_perf0: 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
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: on acpi0 > | acpi_perf0: on cpu0 > | acpi_perf0: failed in PERF_STATUS attach > | device_attach: acpi_perf0 attach returned 6 > | ... > | acpi_perf0: 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]"
Odd PCI and ACPI messages on 'INSYDE RSDT_000' laptop
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: on acpi0 | acpi_perf0: on cpu0 | acpi_perf0: failed in PERF_STATUS attach | device_attach: acpi_perf0 attach returned 6 | ... | acpi_perf0: 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. Yours, -- Ed Schouten <[EMAIL PROTECTED]> WWW: http://g-rave.nl/ Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-STABLE #0: Thu Jul 27 15:07:26 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KIEBORT Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) M processor 1500MHz (1498.73-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x695 Stepping = 5 Features=0xa7e9f9bf Features2=0x180 real memory = 520028160 (495 MB) avail memory = 503705600 (480 MB) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 cpu0: on acpi0 acpi_perf0: on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 acpi_throttle0: on cpu0 acpi_perf0: on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci_link0: BIOS IRQ 11 for 0.2.INTA is invalid pci_link1: BIOS IRQ 5 for 0.31.INTB is invalid pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 2.0 (no driver attached) pci0: at device 2.1 (no driver attached) pci0: at device 29.0 (no driver attached) pci0: at device 29.1 (no driver attached) pci0: at device 29.2 (no driver attached) pci0: at device 29.7 (no driver attached) pcib1: at device 30.0 on pci0 pci_link4: BIOS IRQ 11 for 1.0.INTA is invalid pci_link5: BIOS IRQ 11 for 1.1.INTA is invalid pci1: on pcib1 pci1: at device 0.0 (no driver attached) rl0: port 0xc000-0xc0ff mem 0xe000-0xe0ff irq 9 at device 1.0 on pci1 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:02:3f:12:cd:5a pci1: at device 4.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1100-0x110f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 31.3 (no driver attached) pcm0: port 0xe100-0xe1ff,0xe200-0xe23f mem 0xf0080400-0xf00805ff,0xf0080600-0xf00806ff irq 9 at device 31.5 on pci0 pcm0: pci0: at device 31.6 (no driver attached) atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd0: [GIANT-LOCKED] acpi_acad0: on acpi0 battery0: on acpi0 orm0: at iomem 0xe-0xe17ff,0xe6000-0xe6fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter "TSC" frequency 1498733692 Hz quality 800 Timecounters tick every 1.000 msec ad0: DMA limited to UDMA33, controller found non-ATA66 cable ad0: 38154MB at ata0-master UDMA33 acd0: DVDR at ata1-master UDMA33 Trying to mount root from ufs:/dev/ad0s1a pgpduz8VRuMqS.pgp Description: PGP signature
