Yum offers kernel-3.7.3-101.fc17.armv7l.rpm for armv5tel F17 install, does not boot on qemu vexpress-a9
12:19 p.m.
A few days ago, I updated my qemu virtual machine, which runs F17 with -M vexpress-a9. The
yum update installed kernel-3.7.3-101.fc17.armv7l.rpm . Today I got around to rebooting
the machine with the provided vmlinuz and initramfs. However, the boot
process stalls with no messages. Not even "Uncompressing Linux...". I reverted
to the previous kernel, kernel-3.5.6-1.fc17.armv5tel . What am I doing wrong? Should I use
a different qemu emulation? The strange thing is that the vexpress-a9 emulation
reports armv7l, so the instruction set is supposed to be OK.
My boot script looks like this. The 3.7.3 kernel is commented out.
#!/bin/sh
BASEDIR=`dirname $0`
QEMU_MACH=vexpress-a9
#KERNELVER=3.3.6-3.fc17.armv5tel
# 3.4.2-3.fc17.armv5tel requiere physmap.enabled=0
#KERNELVER=3.4.2-3.fc17.armv5tel
#KERNELVER=3.5.3-1.fc17.armv5tel
KERNELVER=3.5.6-1.fc17.armv5tel
#KERNELVER=3.7.3-101.fc17.armv7l
rm -f $BASEDIR/*.sock
/home/palosanto/programa/qemu-build/arm-softmmu/qemu-system-arm -nographic -m 512 -M
$QEMU_MACH -kernel $BASEDIR/boot/vmlinuz-$KERNELVER -initrd
$BASEDIR/boot/initramfs-$KERNELVER.img -append "root=LABEL=rootfs console=ttyAMA0
physmap.enabled=0" -drive
if=sd,cache=writeback,file=$BASEDIR/fedora-17-arm.vmdk -net nic,vlan=0 -net bridge,vlan=0
-monitor unix:$BASEDIR/qemu-arm-monitor.sock,server,nowait -serial
unix:$BASEDIR/qemu-arm-serial.sock,server,nowait -daemonize
12:47 p.m.
On 02/08/2013 10:19 AM, Alex Villacís Lasso wrote:
A few days ago, I updated my qemu virtual machine, which runs F17
with
-M vexpress-a9. The yum update installed
kernel-3.7.3-101.fc17.armv7l.rpm . Today I got around to rebooting the
machine with the provided vmlinuz and initramfs. However, the boot
process stalls with no messages. Not even "Uncompressing Linux...". I
reverted to the previous kernel, kernel-3.5.6-1.fc17.armv5tel . What am
I doing wrong? Should I use a different qemu emulation? The strange
thing is that the vexpress-a9 emulation reports armv7l, so the
instruction set is supposed to be OK.
You need to use a device tree blob with the 3.7 kernels on versatile
express. The latest f18 3.7 kernel includes the device tree you need
under /boot. Not sure about f17. Don't worry about the armv7l bit,
that's the right arch for armv5tel on versatile express.
--
Brendan Conoboy / Red Hat, Inc. / blc(a)redhat.com
2 p.m.
El 08/02/13 13:47, Brendan Conoboy escribió:
On 02/08/2013 10:19 AM, Alex Villacís Lasso wrote:
> A few days ago, I updated my qemu virtual machine, which runs F17 with
> -M vexpress-a9. The yum update installed
> kernel-3.7.3-101.fc17.armv7l.rpm . Today I got around to rebooting the
> machine with the provided vmlinuz and initramfs. However, the boot
> process stalls with no messages. Not even "Uncompressing Linux...". I
> reverted to the previous kernel, kernel-3.5.6-1.fc17.armv5tel . What am
> I doing wrong? Should I use a different qemu emulation? The strange
> thing is that the vexpress-a9 emulation reports armv7l, so the
> instruction set is supposed to be OK.
You need to use a device tree blob with the 3.7 kernels on versatile express. The latest
f18 3.7 kernel includes the device tree you need under /boot. Not sure about f17.
Don't worry about the armv7l bit, that's the right arch for armv5tel on
versatile express.
[root@rpmbuild-arm var]# rpm -ql kernel-3.7.3-101.fc17.armv7l | grep boot
/boot/.vmlinuz-3.7.3-101.fc17.armv7l.hmac
/boot/System.map-3.7.3-101.fc17.armv7l
/boot/config-3.7.3-101.fc17.armv7l
/boot/initramfs-3.7.3-101.fc17.armv7l.img
/boot/vmlinuz-3.7.3-101.fc17.armv7l
What is the file that is supposed to appear?
2:09 p.m.
On 02/08/2013 12:00 PM, Alex Villacís Lasso wrote:
[root@rpmbuild-arm var]# rpm -ql kernel-3.7.3-101.fc17.armv7l | grep
boot
/boot/.vmlinuz-3.7.3-101.fc17.armv7l.hmac
/boot/System.map-3.7.3-101.fc17.armv7l
/boot/config-3.7.3-101.fc17.armv7l
/boot/initramfs-3.7.3-101.fc17.armv7l.img
/boot/vmlinuz-3.7.3-101.fc17.armv7l
Appears it's not in the F17 3.7 kernel, just F18. I see it on
3.7.5-201.fc18 for instance.
--
Brendan Conoboy / Red Hat, Inc. / blc(a)redhat.com
5:23 a.m.
On Fri, Feb 8, 2013 at 8:09 PM, Brendan Conoboy <blc(a)redhat.com> wrote:
On 02/08/2013 12:00 PM, Alex Villacís Lasso wrote:
>
> [root@rpmbuild-arm var]# rpm -ql kernel-3.7.3-101.fc17.armv7l | grep boot
> /boot/.vmlinuz-3.7.3-101.fc17.armv7l.hmac
> /boot/System.map-3.7.3-101.fc17.armv7l
> /boot/config-3.7.3-101.fc17.armv7l
> /boot/initramfs-3.7.3-101.fc17.armv7l.img
> /boot/vmlinuz-3.7.3-101.fc17.armv7l
Appears it's not in the F17 3.7 kernel, just F18. I see it on
3.7.5-201.fc18 for instance.
dtb files? They were added from 3.7.5-101 but I suggest using
3.7.6-101 as it has other fixes needed for the vexpress that blocked
the F18 release (removal of OABI support which was causing other
issues).
Peter
4:16 p.m.
El 09/02/13 06:23, Peter Robinson escribió:
On Fri, Feb 8, 2013 at 8:09 PM, Brendan Conoboy
<blc(a)redhat.com> wrote:
> On 02/08/2013 12:00 PM, Alex Villacís Lasso wrote:
>> [root@rpmbuild-arm var]# rpm -ql kernel-3.7.3-101.fc17.armv7l | grep boot
>> /boot/.vmlinuz-3.7.3-101.fc17.armv7l.hmac
>> /boot/System.map-3.7.3-101.fc17.armv7l
>> /boot/config-3.7.3-101.fc17.armv7l
>> /boot/initramfs-3.7.3-101.fc17.armv7l.img
>> /boot/vmlinuz-3.7.3-101.fc17.armv7l
>
> Appears it's not in the F17 3.7 kernel, just F18. I see it on
> 3.7.5-201.fc18 for instance.
Is there a way to generate a dtb file from kernel and kernel-devel, without having
to recompile everything? If so, how was this kernel tested to boot?
3:30 a.m.
>>> [root@rpmbuild-arm var]# rpm -ql
kernel-3.7.3-101.fc17.armv7l | grep
>>> boot
>>> /boot/.vmlinuz-3.7.3-101.fc17.armv7l.hmac
>>> /boot/System.map-3.7.3-101.fc17.armv7l
>>> /boot/config-3.7.3-101.fc17.armv7l
>>> /boot/initramfs-3.7.3-101.fc17.armv7l.img
>>> /boot/vmlinuz-3.7.3-101.fc17.armv7l
>>
>>
>> Appears it's not in the F17 3.7 kernel, just F18. I see it on
>> 3.7.5-201.fc18 for instance.
>
>
Is there a way to generate a dtb file from kernel and kernel-devel, without
having to recompile everything? If so, how was this kernel tested to boot?
Not with kernel and kernel-devel you need source but you can do it
without recompiling everything.
Not sure what you'd achieve by doing so, what are you trying to achieve?
peter
9:58 a.m.
El 15/02/13 04:30, Peter Robinson escribió:
>>>> [root@rpmbuild-arm var]# rpm -ql
kernel-3.7.3-101.fc17.armv7l | grep
>>>> boot
>>>> /boot/.vmlinuz-3.7.3-101.fc17.armv7l.hmac
>>>> /boot/System.map-3.7.3-101.fc17.armv7l
>>>> /boot/config-3.7.3-101.fc17.armv7l
>>>> /boot/initramfs-3.7.3-101.fc17.armv7l.img
>>>> /boot/vmlinuz-3.7.3-101.fc17.armv7l
>>>
>>> Appears it's not in the F17 3.7 kernel, just F18. I see it on
>>> 3.7.5-201.fc18 for instance.
>>
> Is there a way to generate a dtb file from kernel and kernel-devel, without
> having to recompile everything? If so, how was this kernel tested to boot?
Not with kernel and kernel-devel you need source but you can do it
without recompiling everything.
Not sure what you'd achieve by doing so, what are you trying to achieve?
peter
As explained in the thread subject, kernel-3.7.3-101.fc17.armv7l.rpm provides
a vmlinuz and initramfs that fail to boot under qemu. The previous version,
kernel-3.5.6-1.fc17.armv5tel, does boot under qemu. From comments in the thread, I
concluded that
3.7.3 needs a device tree file (dtb) that is not being provided by the rpm, as an
additional parameter to qemu (-dtb neededfile.dtb). I am using -M vexpress-a9, so the
machine model is supposedly fine.
10:02 a.m.
On 15 Feb 2013 15:58, "Alex Villacís Lasso" <a_villacis(a)palosanto.com>
wrote:
El 15/02/13 04:30, Peter Robinson escribió:
>>>>> [root@rpmbuild-arm var]# rpm -ql kernel-3.7.3-101.fc17.armv7l | grep
>>>>> boot
>>>>> /boot/.vmlinuz-3.7.3-101.fc17.armv7l.hmac
>>>>> /boot/System.map-3.7.3-101.fc17.armv7l
>>>>> /boot/config-3.7.3-101.fc17.armv7l
>>>>> /boot/initramfs-3.7.3-101.fc17.armv7l.img
>>>>> /boot/vmlinuz-3.7.3-101.fc17.armv7l
>>>>
>>>>
>>>> Appears it's not in the F17 3.7 kernel, just F18. I see it on
>>>> 3.7.5-201.fc18 for instance.
>>>
>>>
>> Is there a way to generate a dtb file from kernel and kernel-devel,
without
>> having to recompile everything? If so, how was this kernel
tested to
boot?
>
> Not with kernel and kernel-devel you need source but you can do it
> without recompiling everything.
>
> Not sure what you'd achieve by doing so, what are you trying to achieve?
>
> peter
As explained in the thread subject, kernel-3.7.3-101.fc17.armv7l.rpm
provides a
vmlinuz and initramfs that fail to boot under qemu. The previous
version, kernel-3.5.6-1.fc17.armv5tel, does boot under qemu. From comments
in the thread, I concluded that 3.7.3 needs a device tree file (dtb) that
is not being provided by the rpm, as an additional parameter to qemu (-dtb
neededfile.dtb). I am using -M vexpress-a9, so the machine model is
supposedly fine.
Use a later version of 3.7 as they're enabled by default, 3.7.6+ from
memory.
Peter
4110
days inactive
4117
days old
8 comments
3 participants
participants (3)
-
Alex Villacís Lasso -
Brendan Conoboy -
Peter Robinson