Open FMog opened 9 years ago
@FMog I was joking about it being for Jīngjīngs's laptop :-) Jīngjīng does not need to use the burner.
The burners should now only offer to flash removable disks. But that includes and USB sticks and hard drives. So we reduced the number because we only supply 8G sd cards and if we need to supply 32G cards some time in the future, we can always change the burner (I added a field in the JSON file by which we can prompt users to download a newer version). This way people are less likely to trash their own stuff. We can easily change the limit, so if you still think this is too low perhaps you could get the customer service team to agree on a figure.
On 12 May 2015 at 14:45, FMog notifications@github.com wrote:
GAT tester reported that 32gb card wasn't being detected by Kano Burner, apparently this was intentionally done to prevent wiping JingJing's netbook?
Can we let JingJing use the old burner and we fix this for the public, maybe add additional protection to prevent people wiping drives?
See report below:
Affected items: Windows Priority: Medium
ACTUAL RESULTS: The Kano Burner does not find an SD Card when attempting to burn the OS onto the Micro SD Card
EXPECTED RESULTS: To find and be able to burn the OS onto the Micro SD Card
OTHER NOTES / ERROR MESSAGES:
- Samsung EVO 32gb Class 10 Micro SD
http://bugs8.gatserver.com/uploads/b875fb81f6fbca0f2f36724531421615.mov
Steps to reproduce:
- Insert Micro SD Card
- Download and open the Kano Burner.
- Click on 'Select Device'.
- Reports back that it can not find SD Card
KanoComputing/GlobalAppTesting#152 https://github.com/KanoComputing/GlobalAppTesting/issues/152
— Reply to this email directly or view it on GitHub https://github.com/KanoComputing/kano-burners/issues/43.
@Ealdwulf - I think 32GB might be useful as they are very reasonably priced to a consumer and more and more people are starting to have them (maybe not just our customers, but our non Kano Kit users), no need to expand to 64GB at this point though in my opinion.
What do you think @alex5imon ?
we can extend it 32GB, not that much of a problem... the users just need to be careful
@FMog feel free to mark them as duplicate so they don't report it again
@alex5imon - I already had, don't worry :)
Afternoon all.
Just ran in to this problem trying this out on a Fedora system, and am obviously running in to the same issue.
I was a little surprised, as based on the wiki page, the tool ignores between 4 and 64GB, howeve rmy 32GB is also being ignored. Update: Sorry, that should have read below 4GB and above 64GB.
Scanning drives.. ran: [parted --list | grep 'Disk /dev/.*:' | awk '{print $2}'] 0 ran: [parted /dev/sda unit B print] 0 Ignoring {'size': 128.03567616, 'id': '/dev/sda', 'name': 'ATA PLEXTOR PX-128M3 (scsi)'} ran: [parted /dev/mmcblk0 unit B print] 0 Ignoring {'size': 31.914983424, 'id': '/dev/mmcblk0', 'name': 'SD SU32G (sd/mmc)'} Removing temp files
I'm happy to test the update json file that has this limit set in it.
I just tried to use the Kano Burner native OSX app on a 32GB sandisk card, and the burner GUI does not detect the card. I checked the card with Disk Utility, looked fine, was FAT32, reformatted it anyway, still no luck.
From my amateurish poking around the build script it looks like the disk size is checked by the backend, does that mean that 32GB is still a hard limit in place on the backend?
Edit: I found the disk-size limit in the repo, I don't know what I was thinking.
Concerned by @alex5imon's reply that users should be careful if /when 32GB cards are recognized. I'm still in the stumbling phase with linux (mostly virtualbox experimentation) and this is my first Raspberry Pi, so I don't know what to look out for when using a larger-than-intended volume in a machine like this.
@langgaibo we put that limit to make sure the user don't format the main hard drive of the computer... I know it's a bit of a harsh measure, but we want to avoid "accidents" as much as possible.
Thanks @alex5imon! I understand the need for the limit, it's better to prevent damage from mindless clicking than to shake a finger later.
I was able to build the kano-burners OSX app with raised 32.5GB limit after forking, but while the card was then recognized, the burn process didn't work.
Not to worry, I just went ahead and purchased a smaller SD card and burned it.
I'm incredibly impressed with Kano, there is a huge impact to be made and it's clearly the right track. Keep up the amazing work!
My 7 year old son wrote a for-loop in Minecraft and I just about soiled myself.
@alex5imon If you're not changing those size limits then the wiki needs to be fixed, as currently it states...
By default, disks smaller than 4GB and larger than 64GB will not be listed to avoid hard drive wipes.
However that is not the case.
The above, is checking below 3.5 and above 16.5, not 64.
@langgaibo thanks for the kind words!
@wibbit, you are absolutely right. Fixing that right now!
@alex5imon thank you! although I see that it is still listed as 64GB on this page https://github.com/KanoComputing/kano-burners#how-it-works which is one of the common landing points when searching the issue on google
@langgaibo fixed!
Hi,
Love Kano…
Is there anyway to manually burn (from the command line, for example) the image to these larger drives (on Mac OS X)? I live in a rather remote place and they only have 32 and 64GB cards (they don't carry much inventory and only the latest models as they can't sell older stuff). These instructions look promising:
https://www.raspberrypi.org/documentation/installation/installing-images/mac.md
Thanks for an awesome product (but my SD card bit the dust so now I'm looking for alternative ways to play).
Ted Stresen-Reuter
Hi Ted, Yes, you can burn using the command line. The instructions at that link should work. You can get our most recent image from: http://downloads.kano.me/public/Kanux-Beta-v2.1.0-release.img.gz That's compressed, so to decompress it do gzip -d http://downloads.kano.me/public/Kanux-Beta-v2.1.0-release.img.gz and then replace 2015-09-24-raspbian-jessie.img with Kanux-Beta-v2.1.0-release.img
Hope this helps, Alex
On 4 November 2015 at 15:47, Ted Stresen-Reuter notifications@github.com wrote:
Hi,
Love Kano…
Is there anyway to manually burn (from the command line, for example) the image to these larger drives (on Mac OS X)? I live in a rather remote place and they only have 32 and 64GB cards (they don't carry much inventory and only the latest models as they can't sell older stuff). These instructions look promising:
https://www.raspberrypi.org/documentation/installation/installing-images/mac.md
Thanks for an awesome product (but my SD card bit the dust so now I'm looking for alternative ways to play).
Ted Stresen-Reuter
— Reply to this email directly or view it on GitHub https://github.com/KanoComputing/kano-burners/issues/43#issuecomment-153769063 .
Alex,
I just went through the steps you recommended to Ted and it worked like a charm on a 32 GB SD card.
For anyone else trying this, I used the alternative method from the page Ted found. The one thing I will add is that once you hit enter, in terminal, after your version of this line: sudo dd bs=1m if=2015-11-21-raspbian-jessie.img of=/dev/rdisk3, be patient. It takes awhile to write the image to disk and the terminal gives no indication that progress is being made.
My guess is that it took a good five minutes for me to complete flashing the Kano image to my SD.
Thanks!!
GAT tester reported that 32gb card wasn't being detected by Kano Burner, apparently this was intentionally done to prevent wiping JingJing's netbook?
Can we let JingJing use the old burner and we fix this for the public, maybe add additional protection to prevent people wiping drives?
See report below:
Affected items: Windows Priority: Medium
ACTUAL RESULTS: The Kano Burner does not find an SD Card when attempting to burn the OS onto the Micro SD Card
EXPECTED RESULTS: To find and be able to burn the OS onto the Micro SD Card
OTHER NOTES / ERROR MESSAGES:
http://bugs8.gatserver.com/uploads/b875fb81f6fbca0f2f36724531421615.mov
Steps to reproduce:
https://github.com/KanoComputing/GlobalAppTesting/issues/152