MacBookPro issues

[coreplayer2]

I recently came across these issues attempting to boot tc-4.1 on a MacBookPro5,5 

Issue #1 on boot
"...Starting udev daemon for hotplug support....Done.
apple 0003:05AC:0236.0003: claimed by neither input, hiddev nor hidraw
apple 0003:05AC:0236.0003: hw start failed"

My interpretation of this is likely no kernel support for the apple keyboard/track pad..??
no big deal I guess as long as there is a keyboard..



Issue #2 on boot
"Sending discover...
ata1: exception Emask 0x10 SAct 0x0 SErr 0x1990000 action 0xe frozen
ata1: irq_stat 0x00400000, PHY RDY changed
ata1: SError: { PHYRdyChg 10B8B DisPar LinkSeq TrSTATrns }
failed in waitforX
tc@box:"$ Sending discover...
No Lease, forking to background"
resulting in no boot

My interpretation of this is while the network and video errors look suspicious, I believe possible file system corruption on a HDD or a physical connection with the HDD caused this problem bring the whole system to a halt.  Oh and do to the system freeze am unable to recover the dmsg

I have yet to see the outcome of my diagnosis so meanwhile, I'm really interested in what the hardware guru's think about this?

[Juanito]

How have you set the machine up to boot tc, single boot tc, dual boot with the mac os or are you trying to boot from cd?

Using the boot code "text" might help with the "waitforX" error.

[coreplayer2]

Thanks for the input.

The machine is set up to boot from a cd with tc-4.1

[coreplayer2]

I was thinking that both the Xvesa and the network errors were a byproduct of the main HDD connection issue.   Which I'm thinking may just be as simple as drive corruption, but the error message may also indicate a driver, or physical connection issue.

[Juanito]

The machine is set up to boot from a cd with tc-4.1

If that's the case, then I'm not sure hdd errors would prevent boot.

I was thinking that both the Xvesa and the network errors were a byproduct of the main HDD connection issue

If you're booting from cd, I doubt it - did you try booting with the "text" boot code?

[coreplayer2]

After reading up on SATA SError registers, it looks like the  PHY RDY changed &  PHYRdyChg 10B8B Dispar LinkSeq
refer to a loose physical connection error with either the SATA cable or power issue.

But I'm all ears for input.

So this may not actually be the cause of the halt in booting, how much the system is frozen at this point is still undermined.   I've seen the waitforX error before which is going to be investigated further.  thx Juanito

[Rich]

Hi coreplayer2
If you use the boot code   text   as Juanito suggested, it might get you to a command prompt.
From there, you could examine the output of dmesg, save it to a text file, copy it to a thumb drive, and
attach the file to your next post.

[coreplayer2]

Thanks Rich

Yes am working on getting the dmesg output.

Meanwhile, I've discovered that removing the HDD from one of the effected MacBookPro's results in a perfectly booted live TinyCore, the notebook boots into OSX when reinstalled (but responds erratically) but unable to boot TC. 

[coreplayer2]

Looks like this is the first issue,  no driver??

Code: [Select]

input: Apple, Inc. Apple Internal Keyboard / Trackpad as /devices/pci0000:00/0000:00:04.0/usb3/3-6/3-6:1.0/input/input6
apple 0003:05AC:0236.0003: input: USB HID v1.11 Keyboard [Apple, Inc. Apple Internal Keyboard / Trackpad] on usb-0000:00:04.0-6/input0
apple 0003:05AC:0236.0004: claimed by neither input, hiddev nor hidraw
apple 0003:05AC:0236.0004: hw start failed