Current (0.11) does not install on /dev/mmcblk0

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Current (0.11) does not install on /dev/mmcblk0

Erik van Linstee
This post was updated on .
I read in the Changelog that voyage-util supports MMC block devices (e.g. mmvblk0p1), so I expected that would also include all the other parts the expect block devices, especially voyage.update.

But it seems it does not. It accepts /dev/mmcblk0 as a device name, but than happily cuts of the '0'.
So when asked about the system device, it does not accept p0. It does accept 0p1, which leads it to continu until somewhere further on in the process it dies on 0p1 not being numerical. Obviously.

I am very sad to see Voyage Linux having stagnated for so long. The APU devices have been out for a long while now, even re-engineered into APU2 already, but still no decent support from Voyage.

I have been satisfied with Voyage on Alix devices for a long time, and have been putting off APU for a long time now to give Voyage a chance to catch up. I can't any longer.

Before I have used symlinks to the mmcblk0 devices in order to fool voyage.update. I will be trying that again to see if 0.11 supports the APU2 mmc so that I can access the SD slot, and if it is stable enough.
I might even invest some time into trying to fix the scripts. But I do hope Voyage gets more love and attention.
Reply | Threaded
Open this post in threaded view
|

Re: Current (0.11) does not install on /dev/mmcblk0

Kim-man 'Punky' TSE-2
Hi Erik,

format-cf.sh support MMC, but voyage.update has not fixed yet.

I normally install voyage to SD card via USB reader (so it would be /dev/sdX device).  And voyage in SD can boot on APU2.

I welcome anyone to fix voyage.update scripts and send me the patch.

Regards,
Punky

On 3/28/2017 6:59 PM, Erik van Linstee wrote:

> I read in the Changelog that voyage-util supports MMC block devices (e.g.
> mmvblk0p1), so I expected that would also include all the other parts the
> expect block devices, especially voyage.update.
>
> But it seems it does not. It accepts /dev/mmcblk0 as a device name, but than
> happily cuts of the '0'.
> So when asked about the system device, it does not accept p0. It does accept
> 0p1, which leads it to continu until somewhere further on in the process it
> dies on 0p1 not being numerical. Obviously.
>
> I am very sad to see Voyage Linux having stagnated for so long. The APU
> devices have been out for a long while now, even re-engineered into APU
> already, but still no decent support from Voyage.
>
> I have been satisfied with Voyage on Alix devices for a long time, and have
> been putting off APU for a long time now to give Voyage a chance to catch
> up. I can't any longer.
>
> Before I have used symlinks to the mmcblk0 devices in order to fool
> voyage.update. I will be trying that again to see if 0.11 supports the APU2
> mmc so that I can access the SD slot, and if it is stable enough.
> I might even invest some time into trying to fix the scripts. But I do hope
> Voyage gets more love and attention.
>
>
>
> --
> View this message in context: http://voyage-linux.34677.n3.nabble.com/Current-0-11-does-not-install-on-dev-mmcblk0-tp4026560.html
> Sent from the Voyage Linux mailing list archive at Nabble.com.
>
> _______________________________________________
> Voyage-linux mailing list
> [hidden email]
> http://list.voyage.hk/mailman/listinfo/voyage-linux


--
Regards,
Kim-man "Punky" Tse

* Open Source Embedded Solutions and Systems
   - Voyage Linux (http://linux.voyage.hk)
   - Voyage MPD   (http://linux.voyage.hk/voyage-mpd)
   - Voyage MuBox (http://mubox.voyage.hk)
* Voyage Store   (http://store.voyage.hk)


_______________________________________________
Voyage-linux mailing list
[hidden email]
http://list.voyage.hk/mailman/listinfo/voyage-linux