[fedora-arm] ARM kernel moving forward 3.7+

Josh Boyer jwboyer at gmail.com
Tue Dec 4 16:50:22 UTC 2012


On Tue, Dec 4, 2012 at 11:07 AM, Mark Langsdorf
<mark.langsdorf at calxeda.com> wrote:
> On 12/01/2012 03:33 AM, Peter Robinson wrote:
>> Hi Mark,
>>
>> Would love feedback on the 3.7-rc7 unified kernel on Calxeda HW.
>>
>> http://arm.koji.fedoraproject.org/koji/buildinfo?buildID=102860
>
> I installed kernel, kernel-tools, kernel-tools-libs, and
> kernel-modules-extra. The boot started, which was nice, and proceeded

You shouldn't need kernel-modules-extra or kernel-tools.  Just an FYI.

> through driver probing. When it came time to find the hard drive, though:
>
> [    3.223097] uart-pl011 fff36000.serial: no DMA platform data
> [    3.293171] loop: module loaded
> [    3.304994] libphy: Fixed MDIO Bus: probed
> [    3.312008] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
> [    3.320476] usbcore: registered new interface driver usbserial
> [    3.326778] usbcore: registered new interface driver usbserial_generic
> [    3.334087] usbserial: USB Serial support registered for generic
> [    3.343052] mousedev: PS/2 mouse device common for all mice
> [    3.357270] rtc-pl031 fff35000.rtc: rtc core: registered pl031 as rtc0
> [    3.372647] device-mapper: uevent: version 1.0.3
> [    3.382934] device-mapper: ioctl: 4.23.0-ioctl (2012-07-25)
> initialised: dm-devel at redhat.com
> [    3.398526] cpuidle: using governor ladder
> [    3.402673] cpuidle: using governor menu
> [    3.415758] usbcore: registered new interface driver usbhid
> [    3.421367] usbhid: USB HID core driver
> [    3.427469] drop_monitor: Initializing network drop monitor service
> [    3.436043] ip_tables: (C) 2000-2006 Netfilter Core Team
> [    3.442094] TCP: cubic registered
> [    3.445452] Initializing XFRM netlink socket
> [    3.460771] NET: Registered protocol family 10
> [    3.479839] mip6: Mobile IPv6
> [    3.482861] NET: Registered protocol family 17
> [    3.488783] Key type dns_resolver registered
> [    3.493269] VFP support v0.3: implementor 41 architecture 3 part 30
> variant 9 rev 4
> [    3.501052] ThumbEE CPU extension supported.
> [    3.505441] Registering SWP/SWPB emulation handler
> [    3.516209] registered taskstats version 1
> [    3.529645] rtc-pl031 fff35000.rtc: setting system clock to
> 2012-12-04 11:54:39 UTC (1354622079)
> [    3.543436] md: Waiting for all devices to be available before autodetect
> [    3.550225] md: If you don't use raid, use raid=noautodetect
> [    3.568496] md: Autodetecting RAID arrays.
> [    3.572649] md: Scanned 0 and added 0 devices.
> [    3.577091] md: autorun ...
> [    3.579884] md: ... autorun DONE.
> [    3.584812] Waiting for root device LABEL=rootfs...

That looks more like "I didn't use an initramfs" or "my initramfs didn't
load" than anything.  What was the full cmdline passed and do you see
messages earlier in the boot about the initramfs?

> it should look more like:

<snip>

> [    1.782285] Freeing init memory: 320K
> [    1.941240] dracut: dracut-018-105.git20120927.fc17

initramfs ^

josh


More information about the arm mailing list