Forum › Forums › New users › New Users and General Questions › Antix ignores 64 Gigabyte SD-card
- This topic has 26 replies, 6 voices, and was last updated Mar 25-7:28 am by ModdIt.
-
AuthorPosts
-
March 22, 2021 at 9:57 pm #56258Member
JohanS
I have recently downloaded Antix 19.3 and I have made a Live-USB which i can boot on a small Asus-laptop.
So I think it is Beautiful ( The dark colours are kind both to my eyes and to the battery of my old laptop).
Well the big problem is. I bought a 64 Gigabyte SD-card 6 months ago. It was a lot cheaper than to by two 32 Gigabyte SD-cards, and I had quite a lot of Video-recordings from my cell-phone that I needed to save somewhere.
Sadly I can not read the SD-card in Antix. I have an Asus Laptop with an SD-card-reader. When i tried Bodhi Linux i could read my 64 Gb SD-card if i first used a Terminal and run,
sudo apt update
and
sudo apt install exfat-utils
( the terminal in Bodhi was helpful to tell me that I also needed exfat-fuse and I only had to answer Yes ),
So I know the hardware in my Laptop have the possibility to read a 64 Gb SD-card since Bodhi Linux could read this SD-card on the very same old computer, but Antix can not. Is there another solution???
I did try of course to open a Terminal and type,
sudo apt install exfat-utils,
since this worked in Bodhi Linux, But the strange thing is that The terminal in Antix “answered” ,
“exfat-utils is already the newest version,
but still Antix ignores my 64 Gb SD-card.
Is there another solution to make it work in Antix???
When i tried Antix 19.3 I choosed the Desktop Environment icewm because I think it is most comfortable, I dont believe my problem will be solved if I choose another D.E. ( but of course I am happy to hear any advice that could solve my problem ).Attachments:
March 22, 2021 at 10:06 pm #56261Anonymous
::Hi JohanS,
can you open the terminal and post a screenshot of
inxi -Fxzso others know what the physical laptop hardware is.
March 22, 2021 at 10:41 pm #56263Forum Admin
rokytnji
::Also with sd card plugged in.
sudo parted -lWould be helpful also. Also with sd card plugged in.
The tail end of terminal readout with the
dmesgcommand should list any errors with sd card mounting. I am olso wondering if you got a corrupt iso download also since no mention of md5sum checksum done on downloaded iso. Howdy and Welcome.
Edit: I mention the above since it has been years since AntiX has not mounted any of my sd cards on my many laptops.
- This reply was modified 2 years, 1 month ago by rokytnji.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsMarch 22, 2021 at 10:44 pm #56266MemberJohanS
::linuxdaddy, Waoo! I did try this, “inxi -Fxz”, and it did return a lot of “information” 😉 I needed to take two Screen-shots to show the whole answer. I will try to “load up” booth of them here, if it is allowed to Attach two pictures.
March 22, 2021 at 10:51 pm #56271Forum Admin
rokytnji
::Instead of screen shots. Just copy and paste the readout for the readouts in your post. I will clean it up later with using the code tags on the reply tool bar if you have hard time figuring it out.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsMarch 22, 2021 at 11:10 pm #56272MemberJohanS
::Forum Admin, Puhh! I tried your “advice” , I mean to type this “sudo parted -l”, and lots of things happened.
When I typed that command I had only two windows opened. It was the Terminal of course, and this web-page. When I hit Enter the terminal also asked me to type the password. And immediately after i wrote the password, a lot of windows opened. I believe it was “file managers”, and it looked like one of them did show the harddrive (it is a very small hardrive of only 30 Gigabyte), but as you recommended, I did put in the 64 Gigabyte SD-card in the computer before i ran this “sudo parted -l”. The harddrive is I guess formatted as ntfs, because It has Windows 10 on it. ( after some updates Windows have eaten up every byte on that poor hard drive). So the 3 windows that I guess is the file-manager was not opened by me. They where just a reaction on this “sudo parted -l”.Attachments:
March 22, 2021 at 11:43 pm #56274Forum Admin
rokytnji
::https://www.urbandictionary.com/define.php?term=Puhh
Never mind then. I take insults personally by the way.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsMarch 22, 2021 at 11:49 pm #56275MemberJohanS
::When I tried the command dmesg , the Terminal showed a lot of lines with the same text,
[ 339.538612] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/16466)
the line above , or something similar, was written more than 50 times in the Terminal, I believe the Asus computer have a touchpad called something with ELAN.
But after the multiple lines about this “ELAN1200:00
There was also some information about some SDHC, I did try to copy that from the terminal,
I will try to paste it down here,[ 339.705592] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/16466) [ 483.058101] snd_hda_intel 0000:00:0e.0: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. [ 531.905160] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [ 2797.212485] mmc1: cannot verify signal voltage switch [ 2797.517070] mmc1: error -110 whilst initialising SD card [ 2798.332504] mmc1: cannot verify signal voltage switch [ 2798.637059] mmc1: error -110 whilst initialising SD card [ 2799.452525] mmc1: cannot verify signal voltage switch [ 2799.757057] mmc1: error -110 whilst initialising SD card [ 2914.656357] mmc1: cannot verify signal voltage switch [ 2914.771128] mmc1: new ultra high speed SDR104 SDHC card at address aaaa [ 2914.790778] mmcblk1: mmc1:aaaa SC32G 29.7 GiB [ 2914.796202] mmcblk1: p1 [ 2915.391373] FAT-fs (mmcblk1p1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [ 2915.398404] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 3882.455893] device-mapper: uevent: version 1.0.3 [ 3882.456363] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised: dm-devel@redhat.com [ 3887.420548] mmc1: card aaaa removed [10130.521989] mmc1: cannot verify signal voltage switch [10130.636709] mmc1: new ultra high speed SDR104 SDHC card at address aaaa [10130.640225] mmcblk1: mmc1:aaaa SC32G 29.7 GiB [10130.643524] mmcblk1: p1 [10131.129749] FAT-fs (mmcblk1p1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [10131.134602] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [10265.373847] asus_wmi: Unknown key cf pressed [10664.222554] mmc1: card aaaa removed [10687.062150] mmc1: cannot verify signal voltage switch [10687.366096] mmc1: error -110 whilst initialising SD card [10688.181481] mmc1: cannot verify signal voltage switch [10688.485991] mmc1: error -110 whilst initialising SD card [10689.301488] mmc1: cannot verify signal voltage switch [10689.606114] mmc1: error -110 whilst initialising SD card [11592.645496] blk_update_request: I/O error, dev mmcblk0rpmb, sector 0 [11592.679240] blk_update_request: I/O error, dev mmcblk0rpmb, sector 0 [11592.680334] mmcblk0: p1 p2 p3 p4 [11593.596214] FAT-fs (mmcblk0p1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [13253.902571] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun demo@antix1:~ $ ^CSo, I did not copy everything that was returned after the command dmesg, Because more than 40 lines was just about this ELAN1200 . And before i typed this dmesg, I also made sure that the 64 GB SD-card was in the computers SD-card-reader. I believe the hard drive in this computer have been called an SDCARD by some other Linux-system.
- This reply was modified 2 years, 1 month ago by rokytnji.
March 23, 2021 at 12:16 am #56276MemberJohanS
::Forum Admin , Thanks for the dictionary-advice. I am very sorry, I had no idea about that meaning of the expression. English is not my home language. In Swedish the expression “Puhh!” means that you take a deep breath. I did that, I took a deep breath, when I saw the huge amount of information that was returned from a single command. I apologize.
March 23, 2021 at 12:19 am #56278Forum Admin
rokytnji
::Understood. Language can be a bitch sometimes. I have thick skin. No worries.
I will let other members look at your dmesg output and comment.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsMarch 23, 2021 at 12:56 am #56279Anonymous
::@JohanS,
on commands that output a lot. you could also pipe the out put to a text file
and upload it as an attachment such as.
inxi -Fxz >> ~/Documents/inxi.txt
dmesg >> ~/Documents/dmesg.txtnot sure why it’s not mounting it when it sees it though.
but the kernel is only showing 32gb not a 64gb card
[10130.640225] mmcblk1: mmc1:aaaa SC32G 29.7 GiBthe inxi shows it as /dev/mmcblk0 and 32gb.
Thanks Robin for correction.March 23, 2021 at 5:48 am #56287MemberRobin
::Hello JohanS
inxi does not show your SD-card mounted (it would be listed under the headline “partitons”), but recognised only as a device (/dev/mmcblk1). The devicename of its first partition should read /dev/mmcblk1p1 then (the second would be /dev/mmcblk1p2 and so on) Don’t mix up drivenames and partitionnames. And also don’t mix up devicenames and mountpoints. You can only mount partitions, from a device to a mountpoint.
So try
lsblk
to verify. (Maybe the drive is reported as another devicenumber, e.g. /dev/mmcblk0 or /dev/mmcblk2, then use this instead.) But if there is no mountpoint displayed for the device in the last column of the output of lsblk, the partition on your card is not mounted.
In this case try to mount it manually, something likemkdir -p '~/test/SD-Card' sudo mount '/dev/mmcblk1p1' '~/test/SD-Card'from the commandline and watch out for the output: if no output comes up, everything is fine and your device is mounted now. Look into the folder ~/test/SD-Card using a file manager.
If something is dumped from the mount command to the console it is an error (e.g. “mount: /dev/mmcblk1p1: can’t read superblock”) and you might try to read this card on a windows machine. There are strange things happening sometimes concerning SD-Cards on linux systems.
Greetings to Sweden
Robin- This reply was modified 2 years, 1 month ago by Robin.
- This reply was modified 2 years, 1 month ago by Robin.
- This reply was modified 2 years, 1 month ago by Robin.
Windows is like a submarine. Open a window and serious problems will start.
March 23, 2021 at 8:49 am #56295MemberModdIt
::Hallo JohanS, as others have said sometimes SD cards are bothersome.
did you install exfat-fuse already, you will need it on antix too.
You might find it easier to look for your card using Gparted, check what you can see with no card plugged in, again after,
do not forget to refresh. Only check, make no changes…On my system sd cards automount under media. If you are using an adapter, please do try another, I have found them often a cause of trouble.
In the controll center you can configure automount. I think the tab will be media in english.
March 23, 2021 at 5:23 pm #56312MemberJohanS
::Yes Moddit. I did try to open a terminal and install exfat-fuse,
But the Terminal in Antix gave me the answer,
exfat-fuse is already the newest version (1.3.0-1).
and i got a similar answer from terminal, when i wrote ,sudo apt install exfat-utils. ( i attach a screen shot on the answer ).
this is the frustrating thing. Antix tells me all needed drivers for exfat support is already installed, but the file manager do not show the 64 Gigabyte SD-card. To make sure that my computer was not broken I did take out a 32 GB SD from a camera, it was an SD-micro so I had to put it in an adapter (SD-micro to SD-original size), because my computer have a reader for Full-size SD-card. When i put this 32 Gb SD-card in the computors SD-reader, The File manager in Antix opened “automatically” after 3 seconds and showed the content of that 32 Gb SD-card. And yes it was shown that it was “placed” (I am sorry for my poor english), in the path (I guess it is not really called a directory, maybe mount-point or path) “/media/demo/My32Gb_SD”. This path was used by Antix File manager.
I am running Antix as live-session, i guess that is why it uses the path /media/demo . I had no problem to open any file and directory on this small 32 GB SD-micro.
So the integrated SD-card-reader can be used by Antix to open a 32 Gb SD-card in 3 seconds. And Antix tells me it already have the newest exfat-fuse, But when I put a 64 Gigabyte SD-card in the same card-reader it is totally ignored. I was worried that the card was broken so I did borrow a computer when visiting a friend today to see if the card was broken. But it worked fine to read that 64 Gb SD from Windows 10 on my friends computer.Attachments:
March 23, 2021 at 7:25 pm #56316MemberModdIt
::Hi JohanS, so now we know the card is not the culprit,
First time seeing this particular error for me.checking your posted readout I see an error.
cannot verify signal voltage switch
[ 2799.757057] mmc1: error -110 whilst initialising SD cardSearching that points to a linux kernel bug which affects some card readers,
card combinations. That might well explain why Bodhi was able to see the card.Would you please do lspci and post so we can see which reader you have.
You could meanwhile try a different kernel or plugin an external card reader.
If you have a spare usb stick you could also see if bullseye alpha can mount your
card.
On 19.3 you are using and bullseye anticapitalista recently recommended to update
the kernel for security reasons. -
AuthorPosts
- You must be logged in to reply to this topic.




