[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: install vs generic kernel
Ok, bad idea.
I'll load up another machine tomorrow with 5.0.1 and then
build a kernel sans firewire. We'll see how that goes.
Thanks for your help!
On Fri, Aug 07, 2009 at 01:33:07PM -0400, Michael wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On Aug 7, 2009, at 10:39 AM, Bruce O'Neel wrote:
>> Back to my pismo with 5.0.1. It halts at uhub1 at usb1: vendor....
>> The next line with the install kernels is
>> adbkbd0 at nadb0 addr 2: PowerBook G3 keyboard
>> nadb0 is listed as (also INSTALL kernel):
>> nadb0 at pmu0: Apple Desktop Bus
>> I wonder if, from the config files, that the problem isn't
>> GENERIC:nadb* at adb_bus? # ADB bus enumerator,
>> at cuda or pmu
>> GENERIC:adbkbd* at nadb? # ADB keyboard
>> GENERIC:adbms* at nadb? # ADB mice and
>> GENERIC:adbbt* at nadb? # button device found
>> on *Books
>> INSTALL:#adb* at obio? # Apple Desktop Bus
>> INSTALL:#akbd* at adb? # ADB keyboard
>> INSTALL:nadb* at cuda? # new ADB Bus
>> INSTALL:nadb* at pmu? # new ADB Bus
>> INSTALL:adbkbd* at nadb? # ADB keyboard
>> I wonder if I added a line
>> nadb* at pmu?
>> to GENERIC and built a kernel if I shouldn't expect success.
> Err, why would you want to do that? nadb already attaches to your pmu.
> adb_bus is a place holder that matches both pmu and cuda. So, nadb is
> more or less the ADB device discovery code, it will look for devices
> after interrupts are enabled, more or less the same time the USB drivers
> will look for devices. Didn't you say earlier that your machine hangs
> during firewire initialization? GENERIC has firewire drivers, INSTALL
> does not.
>> Can I do this without a kernel rebuild?
> No, and it wouldn't change anything anyway.
> have fun
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (Darwin)
> -----END PGP SIGNATURE-----
Main Index |
Thread Index |