Hey all,
First time trying to setup my cubietruck/cubieboard3. I used fedora-arm-installer[1] to fill in an 8GB sd card on my host machine, using Fedora-Minimal-armhfp-21-5-sda.raw.xz.
Pop it into my cubietruck, connect via serial console, start it up. Machine passes uboot fine and boots the initrd, but eventually fails waiting for the root mount point to show up, and falls back to dracut.
Comparing my boot output to kashyap's[2], my machine has all the same messages referencing 'mmc1', but there's nothing about mmc0. mmcblk0 never shows up, so the boot fails after a timeout.
So I populated a SATA drive in the same way as above, hooked that to the cubietruck, and it boots successfully. But I still can't access the sdcard from fedora. The only thing under /sys/block is sda. Tried removing and re-inserting the sunxi_mmc module, doesn't seem to help. Tried another sd card, didn't make a difference.
I updated the kernel on the sdcard (by updating /boot on the sata drive, sticking the sdcard in a USB adapter, rsyncing the contents), booted into the latest lpae kernel, but still the sdcard isn't detected.
Anyone have any ideas? Googling didn't turn up anything.
If not, is it possible to make the cubietruck boot directly off the sata drive? Doesn't seem to work for me, but if I can make that work I don't need to worry about the sdcard.
Thanks, Cole
[1]: https://fedoraproject.org/wiki/Architectures/ARM/F21/Installation#Scripted [2]: https://kashyapc.fedorapeople.org/arm/boot-messages-into-f21-arm-kernel-on-c...
On 02/25/2015 09:19 AM, Cole Robinson wrote:
Hey all,
First time trying to setup my cubietruck/cubieboard3. I used fedora-arm-installer[1] to fill in an 8GB sd card on my host machine, using Fedora-Minimal-armhfp-21-5-sda.raw.xz.
Did you include
--target=Cubietruck
on the installer script command? (case insensitive, ir you read the script)
I have run this successfully on my Cubietruck and Cubieboard2 (I sent in a script change to support the C2, don't know if it has been rolled in).
Though I am now working with F22 Alpha to get video support.
Pop it into my cubietruck, connect via serial console, start it up. Machine passes uboot fine and boots the initrd, but eventually fails waiting for the root mount point to show up, and falls back to dracut.
Mount the card on your host system and see that you get the __boot and __ partitions. Perhaps there is something wrong with your card install step. After I build an SD card, I use gparted to increase the __ partition to max size for the card. The I pull out the card from my host system. I would like to see this step automated in the script.
Comparing my boot output to kashyap's[2], my machine has all the same messages referencing 'mmc1', but there's nothing about mmc0. mmcblk0 never shows up, so the boot fails after a timeout.
So I populated a SATA drive in the same way as above, hooked that to the cubietruck, and it boots successfully. But I still can't access the sdcard from fedora. The only thing under /sys/block is sda. Tried removing and re-inserting the sunxi_mmc module, doesn't seem to help. Tried another sd card, didn't make a difference.
I updated the kernel on the sdcard (by updating /boot on the sata drive, sticking the sdcard in a USB adapter, rsyncing the contents), booted into the latest lpae kernel, but still the sdcard isn't detected.
Anyone have any ideas? Googling didn't turn up anything.
If not, is it possible to make the cubietruck boot directly off the sata drive? Doesn't seem to work for me, but if I can make that work I don't need to worry about the sdcard.
Thanks, Cole
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On 02/25/2015 09:33 AM, Robert Moskowitz wrote:
On 02/25/2015 09:19 AM, Cole Robinson wrote:
Hey all,
First time trying to setup my cubietruck/cubieboard3. I used fedora-arm-installer[1] to fill in an 8GB sd card on my host machine, using Fedora-Minimal-armhfp-21-5-sda.raw.xz.
Did you include
--target=Cubietruck
Yes, I used --target=Cubietruck.
on the installer script command? (case insensitive, ir you read the script)
I have run this successfully on my Cubietruck and Cubieboard2 (I sent in a script change to support the C2, don't know if it has been rolled in).
Though I am now working with F22 Alpha to get video support.
Pop it into my cubietruck, connect via serial console, start it up. Machine passes uboot fine and boots the initrd, but eventually fails waiting for the root mount point to show up, and falls back to dracut.
Mount the card on your host system and see that you get the __boot and __ partitions. Perhaps there is something wrong with your card install step. After I build an SD card, I use gparted to increase the __ partition to max size for the card. The I pull out the card from my host system. I would like to see this step automated in the script.
The sdcard mounts fine on multiple machines using an sd-to-usb adapter, and all partitions are accounted for. That's the only other way I have to test an sdcard
Thanks, Cole
On 02/25/2015 09:43 AM, Cole Robinson wrote:
On 02/25/2015 09:33 AM, Robert Moskowitz wrote:
On 02/25/2015 09:19 AM, Cole Robinson wrote:
Hey all,
First time trying to setup my cubietruck/cubieboard3. I used fedora-arm-installer[1] to fill in an 8GB sd card on my host machine, using Fedora-Minimal-armhfp-21-5-sda.raw.xz.
Did you include
--target=Cubietruck
Yes, I used --target=Cubietruck.
on the installer script command? (case insensitive, ir you read the script)
I have run this successfully on my Cubietruck and Cubieboard2 (I sent in a script change to support the C2, don't know if it has been rolled in).
Though I am now working with F22 Alpha to get video support.
Pop it into my cubietruck, connect via serial console, start it up. Machine passes uboot fine and boots the initrd, but eventually fails waiting for the root mount point to show up, and falls back to dracut.
Mount the card on your host system and see that you get the __boot and __ partitions. Perhaps there is something wrong with your card install step. After I build an SD card, I use gparted to increase the __ partition to max size for the card. The I pull out the card from my host system. I would like to see this step automated in the script.
The sdcard mounts fine on multiple machines using an sd-to-usb adapter, and all partitions are accounted for. That's the only other way I have to test an sdcard
Thinking back to this build, I occationally had a problem with boot failing and dropping back to dracut. I would pull power, repower and the second time it would work. Like there was some problem with NAND or something. Happened like every other setup, that some state was left wrong. I have not seen this behaviour with Rawhide/F22 and forgot about it.
Pressing the power button to reboot did not fix this. I had to pull the powerplug and then back in to get it to boot right.
Hi,
On 25-02-15 15:19, Cole Robinson wrote:
Hey all,
First time trying to setup my cubietruck/cubieboard3. I used fedora-arm-installer[1] to fill in an 8GB sd card on my host machine, using Fedora-Minimal-armhfp-21-5-sda.raw.xz.
Pop it into my cubietruck, connect via serial console, start it up. Machine passes uboot fine and boots the initrd, but eventually fails waiting for the root mount point to show up, and falls back to dracut.
Comparing my boot output to kashyap's[2], my machine has all the same messages referencing 'mmc1', but there's nothing about mmc0. mmcblk0 never shows up, so the boot fails after a timeout.
So I populated a SATA drive in the same way as above, hooked that to the cubietruck, and it boots successfully. But I still can't access the sdcard from fedora. The only thing under /sys/block is sda. Tried removing and re-inserting the sunxi_mmc module, doesn't seem to help. Tried another sd card, didn't make a difference.
I updated the kernel on the sdcard (by updating /boot on the sata drive, sticking the sdcard in a USB adapter, rsyncing the contents), booted into the latest lpae kernel, but still the sdcard isn't detected.
Anyone have any ideas? Googling didn't turn up anything.
So there are no mmc0 messages from the kernel at all ? Sounds like there is an issue with the card-detect pin on your sdcard slot (u-boot does not use this, it assumes the card is there as it is booting from it), you could tree cleaning the slot a bit, e.g. blow some air through it.
If not, is it possible to make the cubietruck boot directly off the sata drive? Doesn't seem to work for me, but if I can make that work I don't need to worry about the sdcard.
There is no way to make things boot directly from sata, you always need u-boot somewhere else as the bootrom inside the soc does not support sata.
You could leave a tiny sdcard in the slot with just u-boot though, and run everything else from sata.
Regards,
Hans
On 02/25/2015 09:55 AM, Hans de Goede wrote:
Hi,
On 25-02-15 15:19, Cole Robinson wrote:
Hey all,
First time trying to setup my cubietruck/cubieboard3. I used fedora-arm-installer[1] to fill in an 8GB sd card on my host machine, using Fedora-Minimal-armhfp-21-5-sda.raw.xz.
Pop it into my cubietruck, connect via serial console, start it up. Machine passes uboot fine and boots the initrd, but eventually fails waiting for the root mount point to show up, and falls back to dracut.
Comparing my boot output to kashyap's[2], my machine has all the same messages referencing 'mmc1', but there's nothing about mmc0. mmcblk0 never shows up, so the boot fails after a timeout.
So I populated a SATA drive in the same way as above, hooked that to the cubietruck, and it boots successfully. But I still can't access the sdcard from fedora. The only thing under /sys/block is sda. Tried removing and re-inserting the sunxi_mmc module, doesn't seem to help. Tried another sd card, didn't make a difference.
I updated the kernel on the sdcard (by updating /boot on the sata drive, sticking the sdcard in a USB adapter, rsyncing the contents), booted into the latest lpae kernel, but still the sdcard isn't detected.
Anyone have any ideas? Googling didn't turn up anything.
So there are no mmc0 messages from the kernel at all ? Sounds like there is an issue with the card-detect pin on your sdcard slot (u-boot does not use this, it assumes the card is there as it is booting from it), you could tree cleaning the slot a bit, e.g. blow some air through it.
Interesting. I wiggled the card some and blew air in a few places, and some time during that fedora spit out:
mmc0: host does not support reading read-only switch. assuming write-enable.
Which I see in kashyap's output as well. However that's all I got and I can't reproduce yet, and not sure specifically what I did during that time.
Would there be mmc0 messages in the kernel output even if no sdcard is inserted? Or is it dependent on a card being present?
If not, is it possible to make the cubietruck boot directly off the sata drive? Doesn't seem to work for me, but if I can make that work I don't need to worry about the sdcard.
There is no way to make things boot directly from sata, you always need u-boot somewhere else as the bootrom inside the soc does not support sata.
You could leave a tiny sdcard in the slot with just u-boot though, and run everything else from sata.
Does /boot need to populated on the sdcard as well? Or can I make uboot on the sdcard use /boot from my sata drive?
Thanks, Cole
Hi,
On 25-02-15 16:10, Cole Robinson wrote:
On 02/25/2015 09:55 AM, Hans de Goede wrote:
Hi,
On 25-02-15 15:19, Cole Robinson wrote:
Hey all,
First time trying to setup my cubietruck/cubieboard3. I used fedora-arm-installer[1] to fill in an 8GB sd card on my host machine, using Fedora-Minimal-armhfp-21-5-sda.raw.xz.
Pop it into my cubietruck, connect via serial console, start it up. Machine passes uboot fine and boots the initrd, but eventually fails waiting for the root mount point to show up, and falls back to dracut.
Comparing my boot output to kashyap's[2], my machine has all the same messages referencing 'mmc1', but there's nothing about mmc0. mmcblk0 never shows up, so the boot fails after a timeout.
So I populated a SATA drive in the same way as above, hooked that to the cubietruck, and it boots successfully. But I still can't access the sdcard from fedora. The only thing under /sys/block is sda. Tried removing and re-inserting the sunxi_mmc module, doesn't seem to help. Tried another sd card, didn't make a difference.
I updated the kernel on the sdcard (by updating /boot on the sata drive, sticking the sdcard in a USB adapter, rsyncing the contents), booted into the latest lpae kernel, but still the sdcard isn't detected.
Anyone have any ideas? Googling didn't turn up anything.
So there are no mmc0 messages from the kernel at all ? Sounds like there is an issue with the card-detect pin on your sdcard slot (u-boot does not use this, it assumes the card is there as it is booting from it), you could tree cleaning the slot a bit, e.g. blow some air through it.
Interesting. I wiggled the card some and blew air in a few places, and some time during that fedora spit out:
mmc0: host does not support reading read-only switch. assuming write-enable.
Which I see in kashyap's output as well.
Yeah that is normal.
However that's all I got and I can't reproduce yet, and not sure specifically what I did during that time.
Would there be mmc0 messages in the kernel output even if no sdcard is inserted?
I don't think so, other the initializing the controller, the kernel will not do anything if the card-detect pin does not signal that there is a card inside the lost.
Or is it dependent on a card being present?
Right.
If not, is it possible to make the cubietruck boot directly off the sata drive? Doesn't seem to work for me, but if I can make that work I don't need to worry about the sdcard.
There is no way to make things boot directly from sata, you always need u-boot somewhere else as the bootrom inside the soc does not support sata.
You could leave a tiny sdcard in the slot with just u-boot though, and run everything else from sata.
Does /boot need to populated on the sdcard as well? Or can I make uboot on the sdcard use /boot from my sata drive?
You can blow away the entire partition table from the sdcard, and have all partitions on the sata disk. All you need is the u-boot binary which sits between 8k and 1M from the start of the card.
Regards,
Hans
On 02/25/2015 10:14 AM, Hans de Goede wrote:
Hi,
On 25-02-15 16:10, Cole Robinson wrote:
On 02/25/2015 09:55 AM, Hans de Goede wrote:
Hi,
On 25-02-15 15:19, Cole Robinson wrote:
Hey all,
First time trying to setup my cubietruck/cubieboard3. I used fedora-arm-installer[1] to fill in an 8GB sd card on my host machine, using Fedora-Minimal-armhfp-21-5-sda.raw.xz.
Pop it into my cubietruck, connect via serial console, start it up. Machine passes uboot fine and boots the initrd, but eventually fails waiting for the root mount point to show up, and falls back to dracut.
Comparing my boot output to kashyap's[2], my machine has all the same messages referencing 'mmc1', but there's nothing about mmc0. mmcblk0 never shows up, so the boot fails after a timeout.
So I populated a SATA drive in the same way as above, hooked that to the cubietruck, and it boots successfully. But I still can't access the sdcard from fedora. The only thing under /sys/block is sda. Tried removing and re-inserting the sunxi_mmc module, doesn't seem to help. Tried another sd card, didn't make a difference.
I updated the kernel on the sdcard (by updating /boot on the sata drive, sticking the sdcard in a USB adapter, rsyncing the contents), booted into the latest lpae kernel, but still the sdcard isn't detected.
Anyone have any ideas? Googling didn't turn up anything.
So there are no mmc0 messages from the kernel at all ? Sounds like there is an issue with the card-detect pin on your sdcard slot (u-boot does not use this, it assumes the card is there as it is booting from it), you could tree cleaning the slot a bit, e.g. blow some air through it.
Interesting. I wiggled the card some and blew air in a few places, and some time during that fedora spit out:
mmc0: host does not support reading read-only switch. assuming write-enable.
Which I see in kashyap's output as well.
Yeah that is normal.
However that's all I got and I can't reproduce yet, and not sure specifically what I did during that time.
Would there be mmc0 messages in the kernel output even if no sdcard is inserted?
I don't think so, other the initializing the controller, the kernel will not do anything if the card-detect pin does not signal that there is a card inside the lost.
Or is it dependent on a card being present?
Right.
Reproduced it a bit more. If I wiggle the card vertically while inserting I can get it to trigger about 1/5 of the time. Affects the two sdcards I have. So my cubietruck hardware must be flaky :(
If not, is it possible to make the cubietruck boot directly off the sata drive? Doesn't seem to work for me, but if I can make that work I don't need to worry about the sdcard.
There is no way to make things boot directly from sata, you always need u-boot somewhere else as the bootrom inside the soc does not support sata.
You could leave a tiny sdcard in the slot with just u-boot though, and run everything else from sata.
Does /boot need to populated on the sdcard as well? Or can I make uboot on the sdcard use /boot from my sata drive?
You can blow away the entire partition table from the sdcard, and have all partitions on the sata disk. All you need is the u-boot binary which sits between 8k and 1M from the start of the card.
Cool I can live with that, I'll give it a shot.
Thanks, Cole
On 25 February 2015 at 08:32, Cole Robinson crobinso@redhat.com wrote:
On 02/25/2015 10:14 AM, Hans de Goede wrote:
Reproduced it a bit more. If I wiggle the card vertically while inserting I can get it to trigger about 1/5 of the time. Affects the two sdcards I have. So my cubietruck hardware must be flaky :(
I ran into this last weekend with my trimslices and trying to use MMC cards in them. The mmc uses point contact 'brushes' to touch the card. Almost anything can make this flake out from corrosion, skin oil, temperature differences causing the brush not to contact carefully, bent wires etc. [The problem with mine turned out to be heat oriented.. if the system was cold it could read the card well, once it got warm it stopped seeing the card or would report other errors] I found I had to use a USB key in the end to boot the system as the connectors in that are much less prone to accidental damage.
On 02/25/2015 10:10 AM, Cole Robinson wrote:
On 02/25/2015 09:55 AM, Hans de Goede wrote:
Hi,
On 25-02-15 15:19, Cole Robinson wrote:
Hey all,
First time trying to setup my cubietruck/cubieboard3. I used fedora-arm-installer[1] to fill in an 8GB sd card on my host machine, using Fedora-Minimal-armhfp-21-5-sda.raw.xz.
Pop it into my cubietruck, connect via serial console, start it up. Machine passes uboot fine and boots the initrd, but eventually fails waiting for the root mount point to show up, and falls back to dracut.
Comparing my boot output to kashyap's[2], my machine has all the same messages referencing 'mmc1', but there's nothing about mmc0. mmcblk0 never shows up, so the boot fails after a timeout.
So I populated a SATA drive in the same way as above, hooked that to the cubietruck, and it boots successfully. But I still can't access the sdcard from fedora. The only thing under /sys/block is sda. Tried removing and re-inserting the sunxi_mmc module, doesn't seem to help. Tried another sd card, didn't make a difference.
I updated the kernel on the sdcard (by updating /boot on the sata drive, sticking the sdcard in a USB adapter, rsyncing the contents), booted into the latest lpae kernel, but still the sdcard isn't detected.
Anyone have any ideas? Googling didn't turn up anything.
So there are no mmc0 messages from the kernel at all ? Sounds like there is an issue with the card-detect pin on your sdcard slot (u-boot does not use this, it assumes the card is there as it is booting from it), you could tree cleaning the slot a bit, e.g. blow some air through it.
Interesting. I wiggled the card some and blew air in a few places, and some time during that fedora spit out:
mmc0: host does not support reading read-only switch. assuming write-enable.
I did not know that any microSD cards have the read/write lock switch. I was at one point pulling out what hair I have on burning a card in an SD adapter (my notebook has an SD slot), only to see that the lock switch was set on the SD adapter.
But this might indicate you have a connection problem in your Cubie.
Which I see in kashyap's output as well. However that's all I got and I can't reproduce yet, and not sure specifically what I did during that time.
Would there be mmc0 messages in the kernel output even if no sdcard is inserted? Or is it dependent on a card being present?
With no SD card, it tries to boot of NAND.
If not, is it possible to make the cubietruck boot directly off the sata drive? Doesn't seem to work for me, but if I can make that work I don't need to worry about the sdcard.
There is no way to make things boot directly from sata, you always need u-boot somewhere else as the bootrom inside the soc does not support sata.
You could leave a tiny sdcard in the slot with just u-boot though, and run everything else from sata.
Does /boot need to populated on the sdcard as well? Or can I make uboot on the sdcard use /boot from my sata drive?
No partitions at all on the SD card. All on the sata, per a private discussion I had with Hans.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, 25 Feb 2015 09:19:13 -0500 Cole Robinson crobinso@redhat.com wrote:
Hey all,
First time trying to setup my cubietruck/cubieboard3. I used fedora-arm-installer[1] to fill in an 8GB sd card on my host machine, using Fedora-Minimal-armhfp-21-5-sda.raw.xz.
Pop it into my cubietruck, connect via serial console, start it up. Machine passes uboot fine and boots the initrd, but eventually fails waiting for the root mount point to show up, and falls back to dracut.
Comparing my boot output to kashyap's[2], my machine has all the same messages referencing 'mmc1', but there's nothing about mmc0. mmcblk0 never shows up, so the boot fails after a timeout.
So I populated a SATA drive in the same way as above, hooked that to the cubietruck, and it boots successfully. But I still can't access the sdcard from fedora. The only thing under /sys/block is sda. Tried removing and re-inserting the sunxi_mmc module, doesn't seem to help. Tried another sd card, didn't make a difference.
I updated the kernel on the sdcard (by updating /boot on the sata drive, sticking the sdcard in a USB adapter, rsyncing the contents), booted into the latest lpae kernel, but still the sdcard isn't detected.
Anyone have any ideas? Googling didn't turn up anything.
If not, is it possible to make the cubietruck boot directly off the sata drive? Doesn't seem to work for me, but if I can make that work I don't need to worry about the sdcard.
potentially you hit https://bugzilla.redhat.com/show_bug.cgi?id=1109603
Dennis
-
Cole Robinson -
Dennis Gilmore -
Hans de Goede -
Robert Moskowitz -
Stephen John Smoogen