On 12/05/2012 10:44 AM, Peter Robinson wrote:
On Wed, Dec 5, 2012 at 4:30 PM, Mark Langsdorf
<mark.langsdorf(a)calxeda.com> wrote:
> On 12/04/2012 04:56 PM, Peter Robinson wrote:
>>>> We might need to add the new calxeda sata module (this is booting off
>>>> sata?) to the dracut include list. Remind me what the module name is
>>>> and I'll cross check it.
>>>
>>> This is booting off SATA. The module name is sata-highbank.
>>
>> Can you try this dracut and regenerate the initrd
>>
>>
http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=1282787
>
> Is there supposed to be an rpm I can download there? I don't see one.
> What am I missing here?
It's a scratch build task so you need to click on the arch (armv5tel /
armv7) to get the rpms.
The dracut took me straight into f19 dependency hell. Is there a way I
can update my system to f19 first?
>> But then I'm sure you build the sata kernel modules in
and specifying
>> Calxeda specifics as opposed to a generic unified kernel that is
>> ultimately going to need to support 100s of devices from numerous
>> SoCs.
>
> I always build the sata as a module.
>
> I should have said I don't have an issue when building 3.7-rcX, and I
> use the same scripts and dracut there (with the generic unified kernel)
> as I do when I'm building the stock 3.6 kernel.
>
> I'm not complaining, I'm just curious about the difference.
Do you have the modules specified in a config like modprobe.conf or
something? I'm not sure but I would love to find out.
I don't think so. I pulled the 3.7 kernel and then used a dracut script
that I got from David Marlin. I couldn't find a modprobe.conf or
anything similar - just modules.dep but that's created after the initramfs.
--Mark Langsdorf
Calxeda, Inc.