I downloaded:
https://dl.fedoraproject.org/pub/alt/stage/21_Beta_TC4/Images/armhfp/Fedora-...
And the checksum (sha256sum) agrees. I build the SD card with:
/home/rgm/arm/fedora-arm-image-installer/fedora-arm-image-installer.sh --image=/home/rgm/arm/Fedora-Minimal-armhfp-21_Beta-TC4-sda.raw.xz --target=Cubietruck --media=/dev/sdb --norootpass
I put the SD card in my Cubietruck and here is what I get on the serial console:
Fedora-Minimal-armhfp-21_Beta-TC4 Boot Options. 1: Fedora-Minimal-armhfp-21_Beta-TC4 (3.17.0-301.fc21.armv7hl) Enter choice: 1: Fedora-Minimal-armhfp-21_Beta-TC4 (3.17.0-301.fc21.armv7hl) Retrieving file: /initramfs-3.17.0-301.fc21.armv7hl.img 28085684 bytes read in 1456 ms (18.4 MiB/s) Retrieving file: /vmlinuz-3.17.0-301.fc21.armv7hl 5538024 bytes read in 471 ms (11.2 MiB/s) append: ro root=UUID=b6a0bdb6-46ac-4206-b116-72e95429cfcd Retrieving file: /dtb-3.17.0-301.fc21.armv7hl/sun7i-a20-cubietruck.dtb 22431 bytes read in 1239 ms (17.6 KiB/s) Kernel image @ 0x42000000 [ 0x000000 - 0x5480e8 ] ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 4e537000, end 4ffffdb4 ... OK Loading Device Tree to 4e52e000, end 4e53679e ... OK
Starting kernel ...
and there it sits.
I have a couple days for testing until I start travel, what should I try to trouble shoot this?
Also I see that there is now a /usr/share/uboot/cubieboard2/ directory, but it is not one of the script install options. How do I build a cubieboard2 SD card for testing?
thanks
----- Original Message -----
I downloaded:
https://dl.fedoraproject.org/pub/alt/stage/21_Beta_TC4/Images/armhfp/Fedora-...
And the checksum (sha256sum) agrees. I build the SD card with:
/home/rgm/arm/fedora-arm-image-installer/fedora-arm-image-installer.sh --image=/home/rgm/arm/Fedora-Minimal-armhfp-21_Beta-TC4-sda.raw.xz --target=Cubietruck --media=/dev/sdb --norootpass
I put the SD card in my Cubietruck and here is what I get on the serial console:
Fedora-Minimal-armhfp-21_Beta-TC4 Boot Options. 1: Fedora-Minimal-armhfp-21_Beta-TC4 (3.17.0-301.fc21.armv7hl) Enter choice: 1: Fedora-Minimal-armhfp-21_Beta-TC4 (3.17.0-301.fc21.armv7hl) Retrieving file: /initramfs-3.17.0-301.fc21.armv7hl.img 28085684 bytes read in 1456 ms (18.4 MiB/s) Retrieving file: /vmlinuz-3.17.0-301.fc21.armv7hl 5538024 bytes read in 471 ms (11.2 MiB/s) append: ro root=UUID=b6a0bdb6-46ac-4206-b116-72e95429cfcd Retrieving file: /dtb-3.17.0-301.fc21.armv7hl/sun7i-a20-cubietruck.dtb 22431 bytes read in 1239 ms (17.6 KiB/s) Kernel image @ 0x42000000 [ 0x000000 - 0x5480e8 ] ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 4e537000, end 4ffffdb4 ... OK Loading Device Tree to 4e52e000, end 4e53679e ... OK
Starting kernel ...
and there it sits.
Add the console to your extlinux.conf. For Cubietruck -'console=ttyS0,115200'.
In F20 there was some logic to pull in the appropriate console from uboot if missing in the append line. We needs this back or an alternative.
I have a couple days for testing until I start travel, what should I try to trouble shoot this?
Also I see that there is now a /usr/share/uboot/cubieboard2/ directory, but it is not one of the script install options. How do I build a cubieboard2 SD card for testing?
For the 'arm-installer' script you can drop a 'config' file in the 'boards.d' directory and it should work. Take a look at the others for an example. Let me know it's working and I can add it.
Paul
thanks
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On 10/22/2014 05:49 PM, Paul Whalen wrote:
----- Original Message -----
I downloaded:
https://dl.fedoraproject.org/pub/alt/stage/21_Beta_TC4/Images/armhfp/Fedora-...
And the checksum (sha256sum) agrees. I build the SD card with:
/home/rgm/arm/fedora-arm-image-installer/fedora-arm-image-installer.sh --image=/home/rgm/arm/Fedora-Minimal-armhfp-21_Beta-TC4-sda.raw.xz --target=Cubietruck --media=/dev/sdb --norootpass
I put the SD card in my Cubietruck and here is what I get on the serial console:
Fedora-Minimal-armhfp-21_Beta-TC4 Boot Options. 1: Fedora-Minimal-armhfp-21_Beta-TC4 (3.17.0-301.fc21.armv7hl) Enter choice: 1: Fedora-Minimal-armhfp-21_Beta-TC4 (3.17.0-301.fc21.armv7hl) Retrieving file: /initramfs-3.17.0-301.fc21.armv7hl.img 28085684 bytes read in 1456 ms (18.4 MiB/s) Retrieving file: /vmlinuz-3.17.0-301.fc21.armv7hl 5538024 bytes read in 471 ms (11.2 MiB/s) append: ro root=UUID=b6a0bdb6-46ac-4206-b116-72e95429cfcd Retrieving file: /dtb-3.17.0-301.fc21.armv7hl/sun7i-a20-cubietruck.dtb 22431 bytes read in 1239 ms (17.6 KiB/s) Kernel image @ 0x42000000 [ 0x000000 - 0x5480e8 ] ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 4e537000, end 4ffffdb4 ... OK Loading Device Tree to 4e52e000, end 4e53679e ... OK
Starting kernel ...
and there it sits.
Add the console to your extlinux.conf. For Cubietruck -'console=ttyS0,115200'.
What is the syntax for adding this? To what line of:
# extlinux.conf generated by appliance-creator ui menu.c32 menu autoboot Welcome to Fedora-Minimal-armhfp-21_Beta-TC4. Automatic boot in # second{,s}. Press a key for options. menu title Fedora-Minimal-armhfp-21_Beta-TC4 Boot Options. menu hidden timeout 20 totaltimeout 600
label Fedora-Minimal-armhfp-21_Beta-TC4 (3.17.0-301.fc21.armv7hl) kernel /vmlinuz-3.17.0-301.fc21.armv7hl append ro root=UUID=b6a0bdb6-46ac-4206-b116-72e95429cfcd fdtdir /dtb-3.17.0-301.fc21.armv7hl/ initrd /initramfs-3.17.0-301.fc21.armv7hl.img
I tried putting it as a line after that last, but it did not make a difference...
In F20 there was some logic to pull in the appropriate console from uboot if missing in the append line. We needs this back or an alternative.
I did not have to do this pre-alpha, but I suspect this is the new uboot serial console issue being discussed?
I have a couple days for testing until I start travel, what should I try to trouble shoot this?
Also I see that there is now a /usr/share/uboot/cubieboard2/ directory, but it is not one of the script install options. How do I build a cubieboard2 SD card for testing?
For the 'arm-installer' script you can drop a 'config' file in the 'boards.d' directory and it should work. Take a look at the others for an example. Let me know it's working and I can add it.
Paul
thanks
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On 23 October 2014 11:41:05 GMT+08:00, Robert Moskowitz rgm@htt-consult.com wrote:
On 10/22/2014 05:49 PM, Paul Whalen wrote:
----- Original Message -----
I downloaded:
https://dl.fedoraproject.org/pub/alt/stage/21_Beta_TC4/Images/armhfp/Fedora-...
And the checksum (sha256sum) agrees. I build the SD card with:
/home/rgm/arm/fedora-arm-image-installer/fedora-arm-image-installer.sh
--image=/home/rgm/arm/Fedora-Minimal-armhfp-21_Beta-TC4-sda.raw.xz --target=Cubietruck --media=/dev/sdb --norootpass
I put the SD card in my Cubietruck and here is what I get on the
serial
console:
Fedora-Minimal-armhfp-21_Beta-TC4 Boot Options. 1: Fedora-Minimal-armhfp-21_Beta-TC4 (3.17.0-301.fc21.armv7hl) Enter choice: 1: Fedora-Minimal-armhfp-21_Beta-TC4 (3.17.0-301.fc21.armv7hl) Retrieving file: /initramfs-3.17.0-301.fc21.armv7hl.img 28085684 bytes read in 1456 ms (18.4 MiB/s) Retrieving file: /vmlinuz-3.17.0-301.fc21.armv7hl 5538024 bytes read in 471 ms (11.2 MiB/s) append: ro root=UUID=b6a0bdb6-46ac-4206-b116-72e95429cfcd Retrieving file:
/dtb-3.17.0-301.fc21.armv7hl/sun7i-a20-cubietruck.dtb
22431 bytes read in 1239 ms (17.6 KiB/s) Kernel image @ 0x42000000 [ 0x000000 - 0x5480e8 ] ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 4e537000, end 4ffffdb4 ... OK Loading Device Tree to 4e52e000, end 4e53679e ... OK
Starting kernel ...
and there it sits.
Add the console to your extlinux.conf. For Cubietruck
-'console=ttyS0,115200'.
What is the syntax for adding this? To what line of:
# extlinux.conf generated by appliance-creator ui menu.c32 menu autoboot Welcome to Fedora-Minimal-armhfp-21_Beta-TC4. Automatic boot in # second{,s}. Press a key for options. menu title Fedora-Minimal-armhfp-21_Beta-TC4 Boot Options. menu hidden timeout 20 totaltimeout 600
label Fedora-Minimal-armhfp-21_Beta-TC4 (3.17.0-301.fc21.armv7hl) kernel /vmlinuz-3.17.0-301.fc21.armv7hl append ro root=UUID=b6a0bdb6-46ac-4206-b116-72e95429cfcd
Stick it on the append line.
I pointed out having to do this on the list a few weeks ago but it evidently got ignored and rediscovered.
BTW I also have a cubietruck and Fedora-Minimal-armhfp-rawhide-20141019-sda.raw.xz failed to do anything useful until the uboot on the SD was replaced.
-Andy
fdtdir /dtb-3.17.0-301.fc21.armv7hl/ initrd /initramfs-3.17.0-301.fc21.armv7hl.imgI tried putting it as a line after that last, but it did not make a difference...
In F20 there was some logic to pull in the appropriate console from
uboot
if missing in the append line. We needs this back or an alternative.
I did not have to do this pre-alpha, but I suspect this is the new uboot serial console issue being discussed?
I have a couple days for testing until I start travel, what should I
try
to trouble shoot this?
Also I see that there is now a /usr/share/uboot/cubieboard2/
directory,
but it is not one of the script install options. How do I build a cubieboard2 SD card for testing?
For the 'arm-installer' script you can drop a 'config' file in the
'boards.d'
directory and it should work. Take a look at the others for an
example. Let me
know it's working and I can add it.
Paul
thanks
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On 10/22/2014 11:49 PM, Andy Green wrote:
On 23 October 2014 11:41:05 GMT+08:00, Robert Moskowitz rgm@htt-consult.com wrote:
On 10/22/2014 05:49 PM, Paul Whalen wrote:
----- Original Message -----
I downloaded:
https://dl.fedoraproject.org/pub/alt/stage/21_Beta_TC4/Images/armhfp/Fedora-...
And the checksum (sha256sum) agrees. I build the SD card with:
/home/rgm/arm/fedora-arm-image-installer/fedora-arm-image-installer.sh
--image=/home/rgm/arm/Fedora-Minimal-armhfp-21_Beta-TC4-sda.raw.xz --target=Cubietruck --media=/dev/sdb --norootpass
I put the SD card in my Cubietruck and here is what I get on the
serial
console:
Fedora-Minimal-armhfp-21_Beta-TC4 Boot Options. 1: Fedora-Minimal-armhfp-21_Beta-TC4 (3.17.0-301.fc21.armv7hl) Enter choice: 1: Fedora-Minimal-armhfp-21_Beta-TC4 (3.17.0-301.fc21.armv7hl) Retrieving file: /initramfs-3.17.0-301.fc21.armv7hl.img 28085684 bytes read in 1456 ms (18.4 MiB/s) Retrieving file: /vmlinuz-3.17.0-301.fc21.armv7hl 5538024 bytes read in 471 ms (11.2 MiB/s) append: ro root=UUID=b6a0bdb6-46ac-4206-b116-72e95429cfcd Retrieving file:
/dtb-3.17.0-301.fc21.armv7hl/sun7i-a20-cubietruck.dtb
22431 bytes read in 1239 ms (17.6 KiB/s) Kernel image @ 0x42000000 [ 0x000000 - 0x5480e8 ] ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 4e537000, end 4ffffdb4 ... OK Loading Device Tree to 4e52e000, end 4e53679e ... OK
Starting kernel ...
and there it sits.
Add the console to your extlinux.conf. For Cubietruck
-'console=ttyS0,115200'.
What is the syntax for adding this? To what line of:
# extlinux.conf generated by appliance-creator ui menu.c32 menu autoboot Welcome to Fedora-Minimal-armhfp-21_Beta-TC4. Automatic boot in # second{,s}. Press a key for options. menu title Fedora-Minimal-armhfp-21_Beta-TC4 Boot Options. menu hidden timeout 20 totaltimeout 600
label Fedora-Minimal-armhfp-21_Beta-TC4 (3.17.0-301.fc21.armv7hl) kernel /vmlinuz-3.17.0-301.fc21.armv7hl append ro root=UUID=b6a0bdb6-46ac-4206-b116-72e95429cfcd
Stick it on the append line.
I pointed out having to do this on the list a few weeks ago but it evidently got ignored and rediscovered.
Oh, I saw it, but was in no position at the time to figure out what it all meant (by doing it).
BTW I also have a cubietruck and Fedora-Minimal-armhfp-rawhide-20141019-sda.raw.xz failed to do anything useful until the uboot on the SD was replaced.
What do you mean by this? That I have to separately do:
dd if=/run/media/rgm/__/usr/share/uboot/Cubietruck/u-boot-sunxi-with-spl.bin of=/dev/sdb bs=1024 seek=8; sync
?
And since cubieboard2 is not one of the installation options, but there is a
/usr/share/uboot/Cubieboard2/u-boot-sunxi-with-spl.bin
That all I need to do is dd this .bin and I can test on my C2?
-Andy
fdtdir /dtb-3.17.0-301.fc21.armv7hl/ initrd /initramfs-3.17.0-301.fc21.armv7hl.imgI tried putting it as a line after that last, but it did not make a difference...
In F20 there was some logic to pull in the appropriate console from
uboot
if missing in the append line. We needs this back or an alternative.
I did not have to do this pre-alpha, but I suspect this is the new uboot serial console issue being discussed?
I have a couple days for testing until I start travel, what should I
try
to trouble shoot this?
Also I see that there is now a /usr/share/uboot/cubieboard2/
directory,
but it is not one of the script install options. How do I build a cubieboard2 SD card for testing?
For the 'arm-installer' script you can drop a 'config' file in the
'boards.d'
directory and it should work. Take a look at the others for an
example. Let me
know it's working and I can add it.
Paul
thanks
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On 23 October 2014 12:33:59 GMT+08:00, Robert Moskowitz rgm@htt-consult.com wrote:
On 10/22/2014 11:49 PM, Andy Green wrote:
On 23 October 2014 11:41:05 GMT+08:00, Robert Moskowitz
rgm@htt-consult.com wrote:
On 10/22/2014 05:49 PM, Paul Whalen wrote:
----- Original Message -----
I downloaded:
https://dl.fedoraproject.org/pub/alt/stage/21_Beta_TC4/Images/armhfp/Fedora-...
And the checksum (sha256sum) agrees. I build the SD card with:
/home/rgm/arm/fedora-arm-image-installer/fedora-arm-image-installer.sh
--image=/home/rgm/arm/Fedora-Minimal-armhfp-21_Beta-TC4-sda.raw.xz --target=Cubietruck --media=/dev/sdb --norootpass
I put the SD card in my Cubietruck and here is what I get on the
serial
console:
Fedora-Minimal-armhfp-21_Beta-TC4 Boot Options. 1: Fedora-Minimal-armhfp-21_Beta-TC4
(3.17.0-301.fc21.armv7hl)
Enter choice: 1: Fedora-Minimal-armhfp-21_Beta-TC4 (3.17.0-301.fc21.armv7hl) Retrieving file: /initramfs-3.17.0-301.fc21.armv7hl.img 28085684 bytes read in 1456 ms (18.4 MiB/s) Retrieving file: /vmlinuz-3.17.0-301.fc21.armv7hl 5538024 bytes read in 471 ms (11.2 MiB/s) append: ro root=UUID=b6a0bdb6-46ac-4206-b116-72e95429cfcd Retrieving file:
/dtb-3.17.0-301.fc21.armv7hl/sun7i-a20-cubietruck.dtb
22431 bytes read in 1239 ms (17.6 KiB/s) Kernel image @ 0x42000000 [ 0x000000 - 0x5480e8 ] ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 4e537000, end 4ffffdb4 ... OK Loading Device Tree to 4e52e000, end 4e53679e ... OK
Starting kernel ...
and there it sits.
Add the console to your extlinux.conf. For Cubietruck
-'console=ttyS0,115200'.
What is the syntax for adding this? To what line of:
# extlinux.conf generated by appliance-creator ui menu.c32 menu autoboot Welcome to Fedora-Minimal-armhfp-21_Beta-TC4.
Automatic
boot in # second{,s}. Press a key for options. menu title Fedora-Minimal-armhfp-21_Beta-TC4 Boot Options. menu hidden timeout 20 totaltimeout 600
label Fedora-Minimal-armhfp-21_Beta-TC4 (3.17.0-301.fc21.armv7hl) kernel /vmlinuz-3.17.0-301.fc21.armv7hl append ro root=UUID=b6a0bdb6-46ac-4206-b116-72e95429cfcd
Stick it on the append line.
I pointed out having to do this on the list a few weeks ago but it
evidently got ignored and rediscovered.
Oh, I saw it, but was in no position at the time to figure out what it all meant (by doing it).
I meant not fixed in Fedora. I wasn't expecting you to do anything about it.
BTW I also have a cubietruck and
Fedora-Minimal-armhfp-rawhide-20141019-sda.raw.xz failed to do anything useful until the uboot on the SD was replaced.
What do you mean by this? That I have to separately do:
dd if=/run/media/rgm/__/usr/share/uboot/Cubietruck/u-boot-sunxi-with-spl.bin of=/dev/sdb bs=1024 seek=8; sync
?
And since cubieboard2 is not one of the installation options, but there is a
/usr/share/uboot/Cubieboard2/u-boot-sunxi-with-spl.bin
That all I need to do is dd this .bin and I can test on my C2?
Who knows. I just reported my personal experience with a specific build which should be interesting for the Fedora guys.
-Andy
-Andy
fdtdir /dtb-3.17.0-301.fc21.armv7hl/ initrd /initramfs-3.17.0-301.fc21.armv7hl.imgI tried putting it as a line after that last, but it did not make a difference...
In F20 there was some logic to pull in the appropriate console from
uboot
if missing in the append line. We needs this back or an
alternative.
I did not have to do this pre-alpha, but I suspect this is the new uboot serial console issue being discussed?
I have a couple days for testing until I start travel, what should
I
try
to trouble shoot this?
Also I see that there is now a /usr/share/uboot/cubieboard2/
directory,
but it is not one of the script install options. How do I build a cubieboard2 SD card for testing?
For the 'arm-installer' script you can drop a 'config' file in the
'boards.d'
directory and it should work. Take a look at the others for an
example. Let me
know it's working and I can add it.
Paul
thanks
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
-
Andy Green -
Paul Whalen -
Robert Moskowitz