Michael,

Your .sha1 file for genx88_64 (video) is incorrect

$ curl -sSfL 
http://download.ipcsolutions.com.au/13se/genx86_64/astlinux-1.3.7.1.tar.gz | 
shasum
cfde4639295579c540240498ee0fc979bbd53858  -
$ curl -sSfL 
http://download.ipcsolutions.com.au/13se/genx86_64/astlinux-1.3.7.1.tar.gz.sha1
bfa72ef0057b204996eda91bfaded4b132655047  astlinux-1.3.7.1.tar.gz

But for your genx88_64-serial (serial) it is OK

$ curl -sSfL 
http://download.ipcsolutions.com.au/13se/genx86_64-serial/astlinux-1.3.7.1.tar.gz
 | shasum
e985d6f2755b122908d969e4b681a67106ada348  -
$ curl -sSfL 
http://download.ipcsolutions.com.au/13se/genx86_64-serial/astlinux-1.3.7.1.tar.gz.sha1
e985d6f2755b122908d969e4b681a67106ada348  astlinux-1.3.7.1.tar.gz


So the Qotom has a genx88_64 (video) image.

Lonnie


> On Apr 7, 2020, at 9:03 PM, Michael Knill <michael.kn...@ipcsolutions.com.au> 
> wrote:
> 
> Hi Guys. I'm having this problem again Grrr.
> I have a Qotom that has been built with a board type of genx86_64-serial. 
> Could this be what is breaking it?
>  
> I tried to upgrade to VGA:
> 3066-Detlevs-CM1 kd # upgrade-run-image upgrade 
> http://download.ipcsolutions.com.au/13se 64
> Firmware verification failed.
>  
> Then just normal:
> 3066-Detlevs-CM1 kd # upgrade-run-image upgrade 
> http://download.ipcsolutions.com.au/13se
> Firmware verification failed.
>  
> I haven’t tried the official repository yet as its on 1.3.8 and I don't want 
> to go there yet.
>  
> Any ideas why I'm getting this and what I can do about it?
>  
> Regards
> Michael Knill
>  
> From: Michael Knill <michael.kn...@ipcsolutions.com.au>
> Reply to: AstLinux List <astlinux-users@lists.sourceforge.net>
> Date: Monday, 20 January 2020 at 5:43 am
> To: AstLinux List <astlinux-users@lists.sourceforge.net>
> Subject: Re: [Astlinux-users] Getting 'Firmware verification failed' on some 
> boxes when I try to upgrade
>  
> Thanks Lonnie. Private repo it is.
> Hmm good idea Michael. I think I will do that. Thanks.
>  
> Regards
> Michael Knill
>  
> From: Michael Keuter <li...@mksolutions.info>
> Reply to: AstLinux List <astlinux-users@lists.sourceforge.net>
> Date: Monday, 20 January 2020 at 3:48 am
> To: AstLinux List <astlinux-users@lists.sourceforge.net>
> Subject: Re: [Astlinux-users] Getting 'Firmware verification failed' on some 
> boxes when I try to upgrade
>  
> 
> 
> 
> 
>> Am 19.01.2020 um 07:56 schrieb Michael Knill 
>> <michael.kn...@ipcsolutions.com.au>:
>> 
>> Maybe one day!
>> 
>> So any chance you would consider putting previous releases into their own 
>> subdirectory?
>> E.g. current release is 
>> http://mirror.astlinux-project.org/ast13se-firmware-1.x/<board type> or 
>> specific version is 
>> http://mirror.astlinux-project.org/ast13se-firmware-1.x/<board 
>> type>/<version>
> 
> If you would do it the other way round for your own repo:
> 
> .../version/board-type/
> 
> then you could include the version number in your "Repository URL" in the 
> Prefs and it would work as before.
> You would need a "board-type" folder structure for every release in that case.
> 
> 
> 
>> I wouldn't bother with my own repository if that was the case!
>> 
>> Regards
>> Michael Knill
>> 
>> On 19/1/20, 9:48 am, "Lonnie Abelbeck" <li...@lonnie.abelbeck.com> wrote:
>> 
>>   Hi Michael,
>> 
>> 
>> 
>>> I have been using a Private Repository ...
>> 
>> 
>> 
>>> I just copy in the upgrade files from the official Astlinux Repository.
>> 
>>   Ahh, OK ... simple enough.
>> 
>>   I was thinking you were somehow adding your "special sauce" to the 
>> official images to create custom images, which I did not know how you could 
>> do that without building images yourself.
>> 
>>   Lonnie
>> 
>> 
>> 
>> 
>> 
>>> On Jan 18, 2020, at 4:40 PM, Michael Knill 
>>> <michael.kn...@ipcsolutions.com.au> wrote:
>>> 
>>> Thanks guys
>>> 
>>> I was not aware of that doco to convert to a vm board type. Excellent I 
>>> will do this and then it should all work.
>>> 
>>> Lonnie I have been using a Private Repository for years now and have never 
>>> had a problem. The main reason for using it was purely to determine the 
>>> 'Current' release for my systems and the ability to upgrade(or downgrade) 
>>> to any version I want by appending the version directory to the repository 
>>> URL. I just copy in the upgrade files from the official Astlinux Repository.
>>> I would be happy to use the Astlinux repository if I could do the above.
>>> 
>>> Regards
>>> Michael Knill
>>> 
>>> On 19/1/20, 1:36 am, "Lonnie Abelbeck" <li...@lonnie.abelbeck.com> wrote:
>>> 
>>> 
>>> 
>>> 
>>> 
>>>> On Jan 18, 2020, at 6:06 AM, Michael Keuter <li...@mksolutions.info> wrote:
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>>> Am 18.01.2020 um 01:15 schrieb Michael Knill 
>>>>> <michael.kn...@ipcsolutions.com.au>:
>>>>> 
>>>>> Hi group
>>>>> 
>>>>> Strangely it appears that with all my genx86_64 systems, on multiple 
>>>>> astlinux versions, I am unable to perform an upgrade from my private 
>>>>> repository as it comes up with ‘Firmware verification failed’. genx86_vm 
>>>>> and genx86_64-serial upgrades work fine. 
>>>>> 
>>>>> I have tried upgrading to both 1.3.6 and 1.3.7.1 and it does the same 
>>>>> thing. I have downloaded it multiple times into the repository so I don't 
>>>>> believe the sha1 file is corrupted.
>>>>> It does work however when I point the repository to 
>>>>> http://mirror.astlinux-project.org/ast13se-firmware-1.x so this indicates 
>>>>> that there must be something wrong with my repository and I cant for the 
>>>>> life of me work out what.
>>>>> 
>>>>> So my questions are:
>>>>> • Any ideas what this could be and what to try to fix it?
>>>>> • How do I show the board type for a system (before it was shown on 
>>>>> login)?
>>>>> • Is there a way I can upgrade to a specific version using the Astlinux 
>>>>> repository?
>>>>> • How can I move to a different board type e.g. all my genx86_64 systems 
>>>>> are on vm’s so they really should be a genx86_vm board type?
>>>>> 
>>>>> Sorry for the lots of questions. Thanks all.
>>>>> 
>>>>> Regards
>>>>> Michael Knill
>>>> 
>>>> Hi Michael,
>>>> 
>>>> short answers to 3. + 4.:
>>>> 
>>>> 3. it depends on the "ver" file in the repo folder which contains the 
>>>> (latest) version. E.g. "astlinux-1.3.7.1".
>>>> 
>>>> 4. You can switch on the commandline between genx86_64 and genx86_64-vm 
>>>> (but not between serial and vga):
>>>> 
>>>> https://doc.astlinux.org/devdoc:devdoc_switch_genx86_64_and_vm
>>>> 
>>>> 
>>>> Michael
>>> 
>>>  +1 and for completeness I'll add this link:
>>> 
>>>  Create a Private Repository
>>>  https://doc.astlinux-project.org/devdoc:devdoc_create_repository
>>> 
>>>  Michael (Knill), you mentioned you are not building your own images (yet), 
>>> so that begs the question ... how are you generating custom images for your 
>>> private repository ?
>>> 
>>>  Lonnie
> 
> Michael
>  
> http://www.mksolutions.info
>  
> 
> 
> 
> 
> _______________________________________________
> Astlinux-users mailing list
> Astlinux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to 
> pay...@krisk.org.



_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
pay...@krisk.org.

Reply via email to