Jack Malmostoso <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > I have them builtin. Maybe it's something bluetooth module related, I > think the kernel sees it as USB. I'll make a couple of tries.
I have tried disabling all bluetooth stuff (daemons and kernel modules) but the problem still is present. This is the output of # tail -f /var/log/messages as I close and reopen the lid: Nov 21 18:15:04 localhost kernel: eth0: suspending, WakeOnLan disabled Nov 21 18:15:06 localhost kernel: PCI: Enabling device 0000:00:10.0 (0000 -> 000 3) Nov 21 18:15:06 localhost kernel: Apple USB OHCI 0001:10:18.0 disabled by firmwa re Nov 21 18:15:06 localhost kernel: Apple USB OHCI 0001:10:19.0 disabled by firmwa re Nov 21 18:15:06 localhost kernel: enable_irq(29) unbalanced Nov 21 18:15:06 localhost kernel: enable_irq(63) unbalanced Nov 21 18:15:06 localhost kernel: enable_irq(63) unbalanced Nov 21 18:15:07 localhost kernel: eth0: resuming Nov 21 18:15:26 localhost kernel: hda: Enabling Ultra DMA 5 Nov 21 18:15:26 localhost kernel: hdc: Enabling MultiWord DMA 2 Nov 21 18:15:26 localhost kernel: adb: starting probe task... Nov 21 18:15:26 localhost kernel: ADB keyboard at 2, handler 1 Nov 21 18:15:26 localhost kernel: ADB mouse at 3, handler set to 4 (trackpad) Nov 21 18:15:26 localhost kernel: adb: finished probe task... Nov 21 18:15:26 localhost kernel: agpgart: Putting AGP V2 device at 0000:00:0b.0 into 4x mode Nov 21 18:15:26 localhost kernel: agpgart: Putting AGP V2 device at 0000:00:10.0 into 4x mode Nov 21 18:15:26 localhost kernel: [drm] Loading R200 Microcode That "Apple USB OHCI" part sounds suspicious, but I really have not a clue. Thanks for any help.
