Something wrong with 2.2.2 release?

[honkinberry 0]

I saw there was a 2.2.2 release today and got very excited.

But when I image the SD it is unreadable.  Am I missing something?  Perhaps I downloaded it before it's ready?

 

--J

[tooz 52]

hello J, 

are you able to boot up the board with the SD card you flashed? 

[SeLeRiki 0]

Horrible release 2.2.2. HWCLOCK does not work properly - it has grabbed onto rtc0 and cannot be changed to 1. There is no configuration file - only the default one, and it works inadequately - it stupidly does not see i2c. Libs6 and utilit-linux libraries are old, it is unrealistic to update them to the required ones without crashing the kernel. The real-time clock generally stuck to the date 2016 November 16 17:45. This is the first time I have seen. The gap with video playback in chromium remained unchanged = CPU overheating and throttling.

[honkinberry 0]

As I said, it is unreadable after I flash it (balenaEtcher on a Mac).

If I flash a previous version, the SD is readable and functional.

I have to ask - does it work for you?

 

--J

[honkinberry 0]

Now that I pause to compare the actual IMG files, it's patently obvious, that is not an IMG file.

So no, it doesn't work for you, or for anybody.

And it's taken you weeks to even approve this post.

I started out very excited with the Tinkerboard, but now I guess I can see that this is just not ready for prime time, with no serious level of support.  For something that is... really quite easy to address.  We're talking replacing an incorrect file download, something that should have taken a few minutes.  And yet, here we are....

 

--J

[Frank3_Wu 2]

41 minutes ago, honkinberry said:

Now that I pause to compare the actual IMG files, it's patently obvious, that is not an IMG file.

So no, it doesn't work for you, or for anybody.

And it's taken you weeks to even approve this post.

I started out very excited with the Tinkerboard, but now I guess I can see that this is just not ready for prime time, with no serious level of support.  For something that is... really quite easy to address.  We're talking replacing an incorrect file download, something that should have taken a few minutes.  And yet, here we are....

 

--J

Hi @honkinberry,

Can you help to try again to see if you can directly boot up or not after the OS flashed.

Since your problem, may just because the image formfactor been changed from the SoC vendor, so it let you may not to directly see all the partitions (no partition table, or unsupported FS on your pc/mac, like linux's fs, EXTF4). But the image should be able to work.

Thanks, and looking forward to hearing your updates.

[honkinberry 0]

My problem is that IMG file is invalid.

All previous releases are a valid IMG file, 2.2.2 is not.

I asked before, I'll ask again -- does it work for you?  Eh, I already know the answer, no it doesn't, you thought you'd just through some fun technobabble at me.

This is insane.  It is a very nice board, worlds better engineering than a Raspberry Pi, but this "support" is beyond pathetic.

 

--J

[Frank3_Wu 2]

2 hours ago, honkinberry said:

My problem is that IMG file is invalid.

All previous releases are a valid IMG file, 2.2.2 is not.

I asked before, I'll ask again -- does it work for you?  Eh, I already know the answer, no it doesn't, you thought you'd just through some fun technobabble at me.

This is insane.  It is a very nice board, worlds better engineering than a Raspberry Pi, but this "support" is beyond pathetic.

 

--J

Hi @honkinberry,

Yes, the image is workable, have you been tried to boot it up?

It should just be the image format and structure, as mentioned earlier, so you can't see the filesystem directly in your computer. (like other systems, e.g. the most common is Android image.)

BTW, is their any other problems you found, or what other to make you think it might be invalid? We can try to help you deal with the OS problem. Or can you check and compare the hash with the zip file you downloaded?

 

[honkinberry 0]

The 2.2.2 IMG file is *not* an IMG file.

I made little screenshots to show this to you, but the forum won't allow me to upload them.

So this is just laughable at this point.

 

--J

[Frank3_Wu 2]

The forum system may have some issue in some times. We have kept in watch with the vendor of the forum system.

Can you share your screenshot via https://imgur.com/ ?

 

BTW, we still not get it, why is not IMG file? IMG is a "Filename Extension", we cannot just use "Filename Extension" to think the file is what kind of truly file format. (see more: https://en.wikipedia.org/wiki/Filename_extension & https://en.wikipedia.org/wiki/IMG_(file_format))

This image format is also used on lots of other products, also our Android image. It cannot be directly read because the PC does not how to identify or support it, as previously stated. But it is supported for Tinker Board and its processors.

[honkinberry 0]

As I stated, I am on a Mac, using balenaEtcher to image the SD.

Macs can mount an IMG file.  But it can't mount 2.2.2.  and balenaEtcher says that it is not a valid image.

And I wasn't just looking at the extension, thank you for your condescending attitude.  I was looking at the files themselves.

2.0.11: https://imgur.com/a/TctNGVR

2.1.11: https://imgur.com/a/U5yPTJW

2.1.16: https://imgur.com/a/OgY19qB

2.2.2: https://imgur.com/a/wO3QOdZ

 

--J

[Frank3_Wu 2]

Hi,

Thanks for your sharing photo. I think the problem still the same.

Since the IMG file is a binary file with custom format. But this time the format is different with before. Therefore, it is reasonable to be different in HEX.

For macOS, it is just possible to mount some IMG or Disk files. But it needs to be a specific formats or Filesystem's dump (contain partition define information, etc).

But in this case our new IMG is customized format from the SoC vendor. So you can not mount in the PC, but it still can be work & bootable for Tinker Board after you flash the OS.

[honkinberry 0]

I can confirm, that yet again, it does not work.

The downloaded IMG file, which all resources say Mac OS should be able to mount, is unable to be mounted.

balenaEtcher, after flashing the SD, reports the image is not valid.

And when using that SD to attempt to boot up, nothing happens.

Almost as if.... the IMG file not a valid IMG file.....

 

--J

[honkinberry 0]

Any chance I can get some actual assistance on this?

As I have said, using balenaEtcher on a Mac reports an error, and the resultant SD does not boot.

 

--J

[tonymac32 0]

Hi Honkinberry, I just came across this and wanted to say, I downloaded the 2.2.2 (beta), flashed it to a Samsung EVO Select 32 GB SD card with Balena Etcher 1.5.41 on PC.  It boots on the Tinker Board, and Tinker Board S.

I would check that the file wasn't corrupted during download:

 

SHA256:
df3689b2bc20d4d6e53caeab2bd73d3e4eee153ecf273c95d9bfeca1485fc87b (zip)

[Joe 3]

Hi
"balenaEtcher says that it is not a valid image." 
Is as https://imgur.com/vzanC6G ??
Missing Partition Table Issue --> https://forums.balena.io/t/missing-partition-table-issue/175129

[Check]
(1) My Mac load normal. My Etcher version is 1.5.116
(2) My Tinker_Board-Debian-Stretch-v2.2.2-20210326.img size 3.38 GB (3,631,173,632 bytes)
(3) md5sum Tinker_Board-Debian-Stretch-v2.2.2-20210326.img
    07385e98a4c3689d396409fb48508c65  Tinker_Board-Debian-Stretch-v2.2.2-20210326.img
How about you??

[honkinberry 0]

I appreciate the help, thank you.

My Etcher was 1.5.115, I updated it to 1.5.116, but still the same.

The file size of the IMG matches.

But I still get the error (warning) from Etcher that the volume is not valid, and when inserted into Tinkerboard it doesn't boot.

I really don't mean to be difficult, I'm sorry, it is just not working for me.

I repeat the steps with the 2.1.16 download, and it boots right up.

No matter how many times I shampoo rinse and repeat, it does not boot.  So I don't know what to say.

What else can I try?

 

--J

[Joe 3]

Hi
Can you provide burn img, let me try it??  (download Link)
"But I still get the error (warning) from Etcher"  <--  is https://imgur.com/vzanC6G ??

[honkinberry 0]

Joe,

I'm not sure how I could do that.

As I said, all I am doing is using Etcher on a Mac.  After which, Ether says the image does not appear valid, and when I insert the SD into the Mac it says it needs to be initialized.  So have no idea how I could image that for you.

Is there some justifiable reason that 2.2.2 needs to be a different format?  I rather liked the ability to be able to mount the image on my Mac and customize it if desired.  This "custom format" or whatever just sure seems more trouble than it's worth.  I would like just a normal IMG file that is easily verifiable.

 

--J

[hamadanwar432 0]

On 4/22/2021 at 9:06 PM, honkinberry said:

As I stated, I am on a Mac, using balenaEtcher to image the SD.

Macs can mount an IMG file.  But it can't mount 2.2.2.  and balenaEtcher says that it is not a valid image.

And I wasn't just looking at the extension, thank you for your condescending attitude.  I was looking at the files themselves.

2.0.11: https://imgur.com/a/TctNGVR

2.1.11: https://imgur.com/a/U5yPTJW

2.1.16: https://imgur.com/a/OgY19qB

2.2.2: https://imgur.com/a/wO3QOdZ

 

--J

Same the case with me. IMG files can be mounted on Macs.  However, it cannot mount 2.2.2.  It says there is a problem with the image.
Here it says: https://imgur.com/a/wO3QOdZ

Edited May 30, 2021 by hamadanwar432

[gregb49 0]

I cannot even download the zip file as it gets halfway though and then says: "Insufficient permissions" so cannot even get to the Etcher stage. Is something strange going on?

[gregb49 0]

"I cannot even download the zip file as it gets halfway though and then says: "Insufficient permissions" so cannot even get to the Etcher stage. Is something strange going on?"

Please ignore. It was an USB problem. I've now downloaded Tinker Board Debian Stretch V2.2.9 which Pi Imager wrote to an SD Card without difficulty. It loads and boots, but after updates is crashing occasionally. I've reverted to an earlier version that seems more stable.