On Mon, Nov 18, 2013 at 1:56 PM, Jos Vos jos@xos.nl wrote:
Hi,
Does somebody have experience with the F20 Beta-5 image on a BeagleBone Black?
I followed the instructions I found on https://fedoraproject.org/wiki/Architectures/ARM/F20/Installation and tried to boot from it (powercycling while pushing the boot button above the microSD slot), but nothing seems to happen after that.
When booting Angstrom and inserting the microSD, it sees all partitions etc. so the content of the microSD looks "technically" ok.
I've successfully gone through the install / startup with that image, using a serial console cable. It just worked.
I used F20 Beta on an x86_64 system with the Adafruit USB to TTL serial cable.
Regards, Robert
On Tue, Nov 19, 2013 at 07:42:47AM -0500, Robert Knight wrote:
I used F20 Beta on an x86_64 system with the Adafruit USB to TTL serial cable.
What do you mean with "on an x86_64 system"?
In the meantime, I found out that a Debian image works fine, using the same microSD card (I tried 2) and power supply (I tried 3), so I'm more or less sure that there is something wrong with the F20 Beta-5 image.
On 11/19/2013 9:42 AM, Jos Vos wrote:
On Tue, Nov 19, 2013 at 07:42:47AM -0500, Robert Knight wrote:
I used F20 Beta on an x86_64 system with the Adafruit USB to TTL serial cable.
What do you mean with "on an x86_64 system"?
I used a Fedora 20 Beta system running on a x86_64, running minicom, to connect to the BeagleBone Black through a USB serial adapter. I was trying to provide enough details so that the experiment could be repeated.
In the meantime, I found out that a Debian image works fine, using the same microSD card (I tried 2) and power supply (I tried 3), so I'm more or less sure that there is something wrong with the F20 Beta-5 image.
On Tue, Nov 19, 2013 at 10:09:47AM -0500, Robert Knight wrote:
I used a Fedora 20 Beta system running on a x86_64, running minicom, to connect to the BeagleBone Black through a USB serial adapter. I was trying to provide enough details so that the experiment could be repeated.
OK. But my problem is that the BBB not even seems to start booting with the F20 image, even none of the USR LEDs turn on.
When booting the Debian image in exactly the same way (even the same microSD card), the LEDs turn on after a second or so (and then I release the boot button) and Debian boots fine.
I have currently nothing attached to the BBB, only a network cable and a power cable (USB or external, I tried both in both scenarios). Could that be a problem?
On 11/19/2013 10:20 AM, Jos Vos wrote:
I have currently nothing attached to the BBB, only a network cable and a power cable (USB or external, I tried both in both scenarios). Could that be a problem?
There's a procedural problem. The boot is into an installer. The installer wants answers to its questions. Without a way to provide those answers, the BBB will hang, waiting in anaconda.
So, I can offer to try to duplicate your problem with the image, but I can't think of a way to distinguish a malfunction from anaconda, just waiting.
On Tue, Nov 19, 2013 at 3:20 PM, Jos Vos jos@xos.nl wrote:
On Tue, Nov 19, 2013 at 10:09:47AM -0500, Robert Knight wrote:
I used a Fedora 20 Beta system running on a x86_64, running minicom, to connect to the BeagleBone Black through a USB serial adapter. I was trying to provide enough details so that the experiment could be repeated.
OK. But my problem is that the BBB not even seems to start booting with the F20 image, even none of the USR LEDs turn on.
When booting the Debian image in exactly the same way (even the same microSD card), the LEDs turn on after a second or so (and then I release the boot button) and Debian boots fine.
I have currently nothing attached to the BBB, only a network cable and a power cable (USB or external, I tried both in both scenarios). Could that be a problem?
At the moment you must have a serial console attached to the serial pins as with the 3.11.x kernel we don't have USB/HDMI support. Without a serial console it will sit on the console awaiting input to create a user and to set a root password.
Peter
Hi,
Was just going to add:
http://www.digikey.com/product-detail/en/TTL-232R-3V3/768-1015-ND/1836393
This was my first stop before doing anything with the BBB.
Regards
On Tue, Nov 19, 2013 at 10:50 AM, Peter Robinson pbrobinson@gmail.comwrote:
On Tue, Nov 19, 2013 at 3:20 PM, Jos Vos jos@xos.nl wrote:
On Tue, Nov 19, 2013 at 10:09:47AM -0500, Robert Knight wrote:
I used a Fedora 20 Beta system running on a x86_64, running minicom, to connect to the BeagleBone Black through a USB serial adapter. I was trying to provide enough details so that the experiment could be
repeated.
OK. But my problem is that the BBB not even seems to start booting with the F20 image, even none of the USR LEDs turn on.
When booting the Debian image in exactly the same way (even the same microSD card), the LEDs turn on after a second or so (and then I release the boot button) and Debian boots fine.
I have currently nothing attached to the BBB, only a network cable and a power cable (USB or external, I tried both in both scenarios). Could that be a problem?
At the moment you must have a serial console attached to the serial pins as with the 3.11.x kernel we don't have USB/HDMI support. Without a serial console it will sit on the console awaiting input to create a user and to set a root password.
Peter _______________________________________________ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
El Tue, 19 Nov 2013 16:20:43 +0100 Jos Vos jos@xos.nl escribió:
On Tue, Nov 19, 2013 at 10:09:47AM -0500, Robert Knight wrote:
I used a Fedora 20 Beta system running on a x86_64, running minicom, to connect to the BeagleBone Black through a USB serial adapter. I was trying to provide enough details so that the experiment could be repeated.
OK. But my problem is that the BBB not even seems to start booting with the F20 image, even none of the USR LEDs turn on.
When booting the Debian image in exactly the same way (even the same microSD card), the LEDs turn on after a second or so (and then I release the boot button) and Debian boots fine.
I have currently nothing attached to the BBB, only a network cable and a power cable (USB or external, I tried both in both scenarios). Could that be a problem?
Dumb question, how did you put the image onto the sdcard?
Dennis
On Tue, Nov 19, 2013 at 12:41:06PM -0600, Dennis Gilmore wrote:
Dumb question, how did you put the image onto the sdcard?
xzcat .... | dd of=/dev/sdb ...
(on another Linux system with a multicard reader) And the partitions look well under both that Linux and Angstrom.
Still, what I don't understand is why the LEDs don't turn on when (trying to) boot from the card. Shouldn't this happen before any script waits for something?
On Tue, Nov 19, 2013 at 7:59 PM, Jos Vos jos@xos.nl wrote:
On Tue, Nov 19, 2013 at 12:41:06PM -0600, Dennis Gilmore wrote:
Dumb question, how did you put the image onto the sdcard?
xzcat .... | dd of=/dev/sdb ...
(on another Linux system with a multicard reader) And the partitions look well under both that Linux and Angstrom.
Still, what I don't understand is why the LEDs don't turn on when (trying to) boot from the card. Shouldn't this happen before any script waits for something?
Did you copy the uEnv.txt and MLO files to the boot partition, are described on the download page?
Regards, Geert
On Thu, Nov 28, 2013 at 09:25:53PM +0100, Geert Jansen wrote:
Did you copy the uEnv.txt and MLO files to the boot partition, are described on the download page?
Yep.
On Thu, Nov 28, 2013 at 9:31 PM, Jos Vos jos@xos.nl wrote:
On Thu, Nov 28, 2013 at 09:25:53PM +0100, Geert Jansen wrote:
Did you copy the uEnv.txt and MLO files to the boot partition, are described on the download page?
Yep.
At first I thought I had the same problem, but then I noticed 2 things:
- The LEDs don't work on Fedora (they do on Angstrom). But the kernel does boot. - It takes at least 20 seconds or so before the kernel spits out any output.
Do you have the USB to serial adapter connected? What is the last output you see?
Regards, Geert
On Thu, Nov 28, 2013 at 09:43:12PM +0100, Geert Jansen wrote:
At first I thought I had the same problem, but then I noticed 2 things:
- The LEDs don't work on Fedora (they do on Angstrom). But the kernel does
boot.
FWIW: they do also work with Debian that I'm running now (just for several performance and application tests, I still want to move to Fedora asap...).
- It takes at least 20 seconds or so before the kernel spits out any
output.
Do you have the USB to serial adapter connected? What is the last output you see?
I did not have anything connected except RJ45 (I read somewhere USB doesn't work with Fedora, so USB does work for a serial console?), I only looked at my DHCP server log to see if the BB asked for an address.
I also got several comments about anaconda or other scripts waiting for input (I expected the image to be ready-to-use, is this not true)?
Tomorrow I will give it another try with a serial monitor connected using an USB-to-serial cable.
On Thu, Nov 28, 2013 at 10:09:03PM +0100, Jos Vos wrote:
I did not have anything connected except RJ45 (I read somewhere USB doesn't work with Fedora, so USB does work for a serial console?),
USB serial connectors certainly do work in Fedora.
Rich.
On Fri, Nov 29, 2013 at 10:19 AM, Richard W.M. Jones rjones@redhat.com wrote:
On Thu, Nov 28, 2013 at 10:09:03PM +0100, Jos Vos wrote:
I did not have anything connected except RJ45 (I read somewhere USB doesn't work with Fedora, so USB does work for a serial console?),
USB serial connectors certainly do work in Fedora.
I believe he's referring to using the OTG port on the board as a serial adapter. In the 3.11.x release that will be GA that functionality doesn't work. I have all the kernel stuff enabled in 3.12 but I need to finish hacking up some systemd stuff so that I can make it work OOTB with the adapter.
Just to clarify for everyone else here at the moment you need a USB to TTY serial adapter to plug into the 6 pin header on the BBBlack motherboard. The USB OTG port doesn't currently work.
As for the LEDs similarly the reason they don't work is that the support isn't currently in the Device Tree file. We have all the required drivers there and I'm looking to make sure this is in place for the 3.12 kernel as well.
Peter
On Fri, Nov 29, 2013 at 4:27 AM, Peter Robinson pbrobinson@gmail.com wrote:
On Fri, Nov 29, 2013 at 10:19 AM, Richard W.M. Jones rjones@redhat.com wrote:
On Thu, Nov 28, 2013 at 10:09:03PM +0100, Jos Vos wrote:
I did not have anything connected except RJ45 (I read somewhere USB doesn't work with Fedora, so USB does work for a serial console?),
USB serial connectors certainly do work in Fedora.
I believe he's referring to using the OTG port on the board as a serial adapter. In the 3.11.x release that will be GA that functionality doesn't work. I have all the kernel stuff enabled in 3.12 but I need to finish hacking up some systemd stuff so that I can make it work OOTB with the adapter.
Just to clarify for everyone else here at the moment you need a USB to TTY serial adapter to plug into the 6 pin header on the BBBlack motherboard. The USB OTG port doesn't currently work.
As for the LEDs similarly the reason they don't work is that the support isn't currently in the Device Tree file. We have all the required drivers there and I'm looking to make sure this is in place for the 3.12 kernel as well.
The "boot" LED's are utilized in Angstrom/Ubuntu/Debian via u-boot, purely for end user debugging..
https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v201...
not upstream..
Regards,
----- Original Message -----
On Thu, Nov 28, 2013 at 09:25:53PM +0100, Geert Jansen wrote:
Did you copy the uEnv.txt and MLO files to the boot partition, are described on the download page?
Yep.
If you hold the 'boot' button you will not see any LEDs at all in the U-Boot we provide. If you do not hold the 'boot' button the U-Boot from eMMC is used and the LEDs are lit, but will then shut off and remain off when the Fedora kernel is loaded.
If not using a serial cable you can use the FAQ section[1] at the bottom of the installation wiki.
If you're still stuck, please drop by #fedora-arm on Freenode.
Paul
[1] - https://fedoraproject.org/wiki/Architectures/ARM/F20/Installation#FAQ
On Thu, Nov 28, 2013 at 03:55:20PM -0500, Paul Whalen wrote:
If you hold the 'boot' button you will not see any LEDs at all in the U-Boot we provide. If you do not hold the 'boot' button the U-Boot from eMMC is used and the LEDs are lit, but will then shut off and remain off when the Fedora kernel is loaded.
OK, I always assumed the boot failed when not seeing any LEDs turn on, so this is really important to be aware of.
If not using a serial cable you can use the FAQ section[1] at the bottom of the installation wiki.
I remember doing that once too, and I removed the root password from the shadow file (instead of adding ssh keys). But with the new info (and not having clear in mind what I tried and when I gave up), it's worth trying again.
----- Original Message -----
----- Original Message -----
On Thu, Nov 28, 2013 at 09:25:53PM +0100, Geert Jansen wrote:
Did you copy the uEnv.txt and MLO files to the boot partition, are described on the download page?
Yep.
If you hold the 'boot' button you will not see any LEDs at all in the U-Boot we provide. If you do not hold the 'boot' button the U-Boot from eMMC is used and the LEDs are lit, but will then shut off and remain off when the Fedora kernel is loaded.
I've tested this now, it looks like arm-boot-config is using the wrong load addresses when booting from the U-Boot we provide.
I'll look into this further, in the mean time you should be able to boot and get going using the headless/serial-less tips I added to the wiki.
Thanks for bringing this to our attention!
Paul
On Thu, Nov 28, 2013 at 10:18 PM, Paul Whalen pwhalen@redhat.com wrote:
I'll look into this further, in the mean time you should be able to boot and get going using the headless/serial-less tips I added to the wiki.
Thanks for bringing this to our attention!
What is the status on making USB and HDMI work on this board by the way?
Thanks, Geert
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
El Tue, 19 Nov 2013 19:59:50 +0100 Jos Vos jos@xos.nl escribió:
On Tue, Nov 19, 2013 at 12:41:06PM -0600, Dennis Gilmore wrote:
Dumb question, how did you put the image onto the sdcard?
xzcat .... | dd of=/dev/sdb ...
(on another Linux system with a multicard reader) And the partitions look well under both that Linux and Angstrom.
Still, what I don't understand is why the LEDs don't turn on when (trying to) boot from the card. Shouldn't this happen before any script waits for something?
thats a odd way to put the image on the card. but should work. I usually just do xzcat <image> >/dev/<mmc|sd>
i believe we don't have support for the leds. i have mine in a case and can't actually see. you do need a serial port. which should let you see what is going on.
Dennis
On Fri, Nov 29, 2013 at 5:21 AM, Dennis Gilmore dennis@ausil.us wrote:
xzcat .... | dd of=/dev/sdb ...
thats a odd way to put the image on the card. but should work. I usually just do xzcat <image> >/dev/<mmc|sd>
An advantage of using dd is that it allow you to see progress by sending it SIGUSR1. Also you can use oflag=direct to bypass the buffer cache.
Regards, Geert
I had the same experience with the beaglebone black, No hdmi and no usb support = no good. Why bother releasing an image that is not functional. I am a big fedora fan & promoter, but I went to debian wheezy 7.2 for my BBB ham radio setup. I create HR rpm's for arm systems and Pidora 19 alpa is a disappointment with the repository in a mess, too many 'missing requires' ;
No ftdi support in the base image kernel, not able to update kernel getting 'obsoleted' etc. I can install my rpms ok, but cannot connect a ftdi device to use it.
I intend to do this software in rpm's for Pidora 19 & BBB > Fedora 20 when it is ready.
I wonder why Debian are so far in front of Fedora on these fronts? Fedora always had a reputation for great hardware support, but not here not now.
Adrian ... vk4tux
-----Original Message----- From: Dennis Gilmore dennis@ausil.us To: arm@lists.fedoraproject.org Subject: Re: [fedora-arm] F20 Beta-5 on BeagleBone Black Date: Tue, 19 Nov 2013 12:41:06 -0600
El Tue, 19 Nov 2013 16:20:43 +0100 Jos Vos jos@xos.nl escribió:
On Tue, Nov 19, 2013 at 10:09:47AM -0500, Robert Knight wrote:
I used a Fedora 20 Beta system running on a x86_64, running minicom, to connect to the BeagleBone Black through a USB serial adapter. I was trying to provide enough details so that the experiment could be repeated.
OK. But my problem is that the BBB not even seems to start booting with the F20 image, even none of the USR LEDs turn on.
When booting the Debian image in exactly the same way (even the same microSD card), the LEDs turn on after a second or so (and then I release the boot button) and Debian boots fine.
I have currently nothing attached to the BBB, only a network cable and a power cable (USB or external, I tried both in both scenarios). Could that be a problem?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
El Wed, 20 Nov 2013 05:44:18 +1000 Adrian vk4tux@bigpond.com escribió:
I had the same experience with the beaglebone black, No hdmi and no usb support = no good. Why bother releasing an image that is not functional. I am a big fedora fan & promoter, but I went to debian wheezy 7.2 for my BBB ham radio setup. I create HR rpm's for arm systems and Pidora 19 alpa is a disappointment with the repository in a mess, too many 'missing requires' ;
No ftdi support in the base image kernel, not able to update kernel getting 'obsoleted' etc. I can install my rpms ok, but cannot connect a ftdi device to use it.
I intend to do this software in rpm's for Pidora 19 & BBB > Fedora 20 when it is ready.
I wonder why Debian are so far in front of Fedora on these fronts? Fedora always had a reputation for great hardware support, but not here not now.
Adrian ... vk4tux
-----Original Message----- From: Dennis Gilmore dennis@ausil.us To: arm@lists.fedoraproject.org Subject: Re: [fedora-arm] F20 Beta-5 on BeagleBone Black Date: Tue, 19 Nov 2013 12:41:06 -0600
El Tue, 19 Nov 2013 16:20:43 +0100 Jos Vos jos@xos.nl escribió:
On Tue, Nov 19, 2013 at 10:09:47AM -0500, Robert Knight wrote:
I used a Fedora 20 Beta system running on a x86_64, running minicom, to connect to the BeagleBone Black through a USB serial adapter. I was trying to provide enough details so that the experiment could be repeated.
OK. But my problem is that the BBB not even seems to start booting with the F20 image, even none of the USR LEDs turn on.
When booting the Debian image in exactly the same way (even the same microSD card), the LEDs turn on after a second or so (and then I release the boot button) and Debian boots fine.
I have currently nothing attached to the BBB, only a network cable and a power cable (USB or external, I tried both in both scenarios). Could that be a problem?
The issue is that Debian is willing to take a bunch of forked kernels and not care if the support makes it to the mainline kernel, where in Fedora we closely follow the mainline linux kernel tree, which is what we ship. things are getting better and vendors are realising that they need to get things upstream.
its a matter of Fedora is doing the right thing for the greater good and some other distros are taking shortcuts for short term gain.
First boot of a Fedora release initial-setup runs and you are prompted for configuring the system, there are ways around it but thats a different discussion.
Dennis