I have recently bought a USB, which is initially formatted using exFAT. Then I tried wiping it off and format it with ext4. But then, Linux Mint 20 doesn't seem to be able to mount it. When I checked the "disks" utility, the USB appeared, but it just displayed the loading loop. I tried to cancel the mount job, no luck either. Then I tried a live Linux Mint 19, also can't open the USB, so this is clearly not a problem with my existing computer.
Then I booted up my Windows copy (dual boot with Mint 20), plugged the USB in, formatted it to exFAT, and Windows can then open it. Then I boot up Mint 20 and live Mint 19 and both can open it. So my question is, do USB manufacturers restrict the type of filesystems a USB can have? I have never heard of this phenomenon, and can you give me some source to read more?
So I have dug into this a whole lot for the past few days and I think I know what's wrong. I tried to create an ext4 partition, didn't work. I then tried to fix it using fsck, also no dice. Then I tried to create an ext4 partition with less size (60GB), and then it works, with no corruption. It turns out that I just got scammed by the manufacturer.
Related
I am writing to you to ask you about the following: I am working on a custom embedded Linux distro for a Zynq700 based board. One of the features to be added is support for USB in host mode, which I have achieved.
This way, with rootfs I have a combination of udev rules & fstab entries that allow a given USB stick to be automounted with a certain conditions. However, if we change the filesystem to initramfs, the flash drive not only does not automount, it is not recognised.
I looked at the output of dmesg, lsusb & lsmod to make sure of this & confirmed that no driver function is called. In addition, I also notice that the USB stick is not receiving any power (the HW is correct because with the same hdf and roofs I have it functional).
Is there some peculiarity of initramfs compared to rootfs that I'm missing that has this effect?
Thanks in advance
I am trying to set up Tinker Board headlessly as I don't have access to a wired keyboard and mouse.
One method I know that works for Raspi is by creating an SSH file while setting it up and a wpa_supplicant.conf file to provide wifi details. I have flashed the latest Tinker OS v2.2.9 onto the eMMC present on the board as per the instructions. But, in this case I am not able to access the drive once flashed (Contrary to raspi setup).
Is there a way to set it up headlessly?
Thank you for taking out time to read this and helping out.
I cannot connect to my beaglebone black via ssh or usb,
I could connect via ssh/ethernet before I edited a file, and rebooted.
I thnink the file I changed was uEnv.txt and I think I commented out the line about HDMI
Any ideas? do i just need to reinstall the debian OS? via the memory card?
thanks for your help.
If it really was the uEnv.tx-file you don't need to reflash your img.
You can edit the uEnv.txt file again (easly with the plugged USB and explorer). If you comment things out in this file, the driver can't work properly. If you can tell me your img version (that's very usefull if you write it by every question down) I can show you the unmodified uEnv file.
You can easy also google that file.
An alternative way is to reflash the img. Recommendable for new BBB / Linux users. The img an guide is available at beaglebone.org
I hope I answered your question, otherwise write again!
I have this strange problem in an embedded system (linux) we build, so I don't have normal GUI trouble-shooting tools on Linux or Windows machines.
The problem is the NIC is no longer usable after cable removed. Even if I re-plug the cable, the lights on it never come back on again and nothing can be sent or received. ifconfig still works on the surface, but doesn't have real effect. Only a reboot will solve the problem. I guess the problem is in the ethernet driver.
My question is how the trouble-shoot it. Any clues/hints? Thanks.
====================
Thank you guys! The board is a gumstix and the PHY is SMSC911x. We are running on Linux 3.0.12. It turns out the smsc911x_soft_reset() of the NIC fails when driver calls smsc911x_open(). The symptom also includes we must run ifconfig multiple times (not consistent) to bring the NIC up and the system can detect it.
I did a search on "SMSC911x soft reset failed" and find this link. http://comments.gmane.org/gmane.linux.network/216467. I removed SMSC_PHY=y in the linux build config file and that fixed the problem. It seems the driver is not compatible. Can somebody explain this, or is there a better solution?
I've set up raspbian "wheezy" (more information here, and image file here) on my recently arrived raspberry-pi (model B, but with 256MB RAM). Since I plan to use it via SSH from other locations, I was looking for a way to lock the console on the actual machine.
Raspbian is the first unix based OS I am working with, so I'm not really familiar with it, but I think I am looking for something like "vlock".
I installed vlock like this:
apt-get install vlock
When I now log into my pi via SSH from my Windows PC vlock works just fine, but when I try using it on the machine itself it shows a strange behaviour.
If I enter a wrong password, I get the usual message:
vlock: Authentication failure
but immediately after that the commandline shows up as if I entered the right one. So basically everyone can just roll his or her head over my keyboard to unlock my pi.
Does anyone know if this is a known bug (or even intended)? Or are there any equivalents to vlock that I could try?
Thanks in advance.
PS: This is my first question on stackoverflow so I hope I provided enough information. If I didn't, feel free to comment/ask.