Re: macbook2,2 latest git mmconfig issues

[Justin Mattock]

On Sat, Jul 19, 2008 at 9:28 AM, Jack Howarth <howarth@xxxxxxxxxxxxxxxxx> wrote:
> On Sat, Jul 19, 2008 at 08:54:58AM -0700, Justin Mattock wrote:
>>
>> >From over here; do you think grub
>> has something to do with this error?
>> why: when installing the intaller was broken
>> thus having to download the latest grub and manually
>> plug in the partitions and so forth.
>>  when using the latest git(a day ago) I was using
>> an older version it seems of grub. But this wouldn't explain
>> why I received the PCI: not using MMCONFIG error
>> I need right now to make sure the name is correct
>> "MacBook2" and "Apple", and make sure 0x3f
>> is right also. You never know maybe these get changed with
>> each version of the mac's. Overall this is a pretty nasty bug
>> leaving completely out of business.
>> --
>> Justin P. Mattock
>
> Justin,
>   The current tip from earlier this morning is booting fine under
> Fedora 9 here on my MacBook Pro v2 (build with CONFIG_PCIEASPM unset).
> I am rebuilding tip with CONFIG_PCIEASPM=y in case the issue is fixed
> or has gone latent on tip. If not, I'll update my bugzilla and try
> to get Jesse to take a look at it.
>                     Jack
>
>

when using the boot options
debug initctl_debug vga=790
I'm able to see the hardisk is being mounted alsa
is activated netfiler is being activated, but then
just stops giving me the:
VFS cannot mount on root filesystem error
keep in mind this is when using "any" option
in PCI, when using MMCONFIG
im getting what you where getting
I'm just confused on how the system was working
without any errors with "Direct" in pci
and now none of the options are working.
The posotive side is better work this issue now,
rather than later. what I'll try is loading a fresh install
of nubuntu, and then compile the kernel with there .config
to see if I'm able to start. Also they added apparmor so I'm not sure if
this is causing problems as well.
-- 
Justin P. Mattock
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/