I recently got my pi board and started working on it. I decided my first aim to install a OS image on SD card and boot from it. So i downloaded Arch Linux image file in zip format from here http://www.raspberrypi.org/downloads.
After that i installed .img file in my SD card Verbatim 8GB (I do not know why 4hr is also written here ?) using Ubuntu 12.04LTs . I used following commands :
sudo umount /dev/sdb1
sudo dd bs=1M if=/path/to/img/file of=/dev/sdb
After successful installation , when i tried to boot from it using PI board , then my monitor shows NO SIGNAL , i checked all the cables and i also borrowed another SD card from my friend preloaded with Raspbian , it was working fine, that is problem is with installation.So i again put SD card in my Laptop and i got surprised that it is not detecting it. I used Gparted , it shows unknown file system error.I again tried but the problem remain same .
Now my questions are :
How to install Arc Linux image in SD card ?
Why it is showing unknown file system after installing Arch Linux ?
After loads of Googling, I am convinced that we are not the only ones with this problem and probably the problem is with the 2014.01 and 2014.02 image itself. I myself spent around 4 hours thinking I am going wrong somewhere. Downloading another image from http://archlinuxarm.org should help.
Related
I got this error in raspberry pi 64 bit OS when im importing torch
"from torch.nn.utils.rnn import pad_sequence"
So far I have used the following solution:
export LD_PRELOAD=/usr/lib/aarch64-linux-gnu/libgomp.so.1:/$LD_PRELOAD
and
source ~/.bashrc
But still getting this error
Okay , I got it solved by putting this line at the beginning of the code:
from torch.nn.utils.rnn import pad_sequence
I don't know how it worked and solved the error.
For some reason, the pre-built aarch64 wheel from PyTorch seems to encounter this error on 64-bit Raspberry Pi OS.
However, a wheel built on-device seems to work fine. If you don't want to build it yourself, the wheel built by Q-engineering on an RPi seems to work without issues. Check it out here (RPi 3B & 4, 64-bit Raspberry Pi OS).
I've just gotten my Raspberry Pi Pico and am trying to get it ready to accept code. I've tried dragging and dropping MicroPython from the webpage and using Thonny to handle it automatically, but when I do either, it ejects itself and nothing has loaded. I'm trying to do this from a Pi 4. Any help would be greatly appreciated.
This is how I do it (but not on a RaspPI)... hold the BootSel button on the Pico and then plug it in. A new "disk" should appear to the OS (or on the desktop). Drag the Micropython UF2 file onto the new disk - this installs Micropython on the Pico. The file gets copied, the Pico saves it to flash, and the "disk" ejects itself.
Now, in Thonny, you have to select the correct board (Pico) and the correct serial interface device (/dev/it-depends-on-your-system). The Thonny page has notes for this. At this point, with Micropython, we talk to it over the serial line, not as a disk.
HTH.
I really does sound as if you are trying to install MicroPython without downloading it and/or to run a MicroPython program without installing the MicroPython system. You first have to install the MicroPython system, download a uf2 file, and only then can you install and run a MicroPython program using Thonny.
Answering here because I had trouble getting mine to work too. In my case, I somehow got my pico into such a state that Mass Storage Device mode would randomly disconnect / eject, often before I could even drag a new UF2 file to the device.
Since I didn't have the time to be successful with drag/drop before the device disconnected, I built and used picotool to push the "nuke memory" UF2 file (see link here). (BOOTSEL held down, plugin, hit enter on the terminal to run ASAP before the pico disconnects)
I actually had to do this two or three times, but after that it stopped being weird and Mass Storage mode works correctly again; I was able to install the MicroPython UF2 file with the normal drag and drop method and Thonny no longer disconnects.
I hope someone out there can help me!
I'm working on a Toshiba SATELLITE-L50-A-1DN, and I am having problems connecting a camera to the USB ports, as well as the integrated webcam not being recognised.
I am using Ubuntu 16.04 with kernel 4.13.0-45-generic
After plugging in an external webcam, lsusb does not change, indicating no device has been recognised.
ls -ltrh /dev/video* returns the error: ls: cannot access '/dev/video*': No such file or directory
I have tried installing uvcvideo, but the most up to date version is already installed. Related to this, I cannot access the Video4Linux module required to use one of the two cameras I am trying to use.
I am aware of the same question being posted here: cannot access /dev/video*: No such file or directory but I can't seem to make that solution work for me.
In dev is there root direct:
my#my-u18gv:~$ cd /dev/video0
If the bellow msg come:
No such file or directory
Then there may be two cases if i found and try to fix:
*
1.) The ubuntu machine or linux machine.
*
There may be various scenario or dependencies which may be causing
this but this what i check on both condition. The the packages and
retart the system
sudo apt-get update
To check the webcamp you can use cheese or any other it depends on
you:
sudo apt-get install cheese
cheese
*
2.) Ubuntu in Virtual Machine running on windows.
*
I'm using ubuntu 18.04, virtual machine 5.2.14 on windows 10 64bit.
Steps:
Open the VM Virtual Box and select the snapshot you are using.
Select the Settings
Select the USB menu at the left
Enable the usb controller and select the USB 2.0 (EHCI) cintroller
Click from USB Device_filter there is a usb cable icon with '+' sign at the right side.
Select your device from the list. In my list it was realtek semiconductor corp.
Here you may face one issue:
while selecting and USB 2.0 and when you start then if you get below error.
failed to install extension pack VERR_SYMBOL_NOT_FOUND ..
Then you need to install VM VirtualBox Extension Pack.
Note: take care that the version of the VM virtualbox and extension package should be same or it might give you error.
Steps: For installing VM VirtualBox Extension Pack
link:https://www.virtualbox.org/wiki/Download_Old_Builds_5_2
For every version you will find the extension package you need in above link.
Open the VM Virtual Box and click on File --> Preferences --> Extensions
Click on Plus icon and Add the extension which you downloaded.
Execute the command:
enter image description here
system error:
[ERROR] [1575905480.653251919]: Unable to identify '/dev/video0': 2, No such file or directory
enter image description here
Answers:
First of all, try your own laptop camera good or bad (do a QQ search, etc...); no problem found
Then review the virtual machine settings. The blue circle has not been opened before and the virtual machine must be turned off for it to be marked;
enter image description here
Reboot, the camera device can now be found in the virtual machine and check "Connect (disconnect from host)".
enter image description here
Re-run the command, the camera can open correctly
enter image description here
I hope it works
I am trying to install CentOs 6.7 on a VPS. I downloaded the LiveCD iso from CentOs's website and put it on a bootable thumb drive, and even burned it to CD, however when booting from either sources, I get this error.
I have even re-download the same file from different source links but the same thing happens.
use second newest kernel.
i.e:
During a startup, press ESC to stop the boot
login and remove the kernel you are using. download the newest kernel then restart
I'm using a Python application that accesses a USB device (pipsta printer) and executes a routine. It's running fine outside the container, but when it comes to the container it returns a error like this:
(File "usr/local/lib/python2.7/dist-packages/usb/backend/libusb0.py", line 386, in _check:
raise USBError(errmsg, ret)
USB.core.USBError: [Errno None] couldn't opendir(): No such a file or directory)
In my dockerfile, I've included all the packages relevant to Python and USB, and I also moved the relevant files to /etc/udev/rules.d and restarted udev.
Make sure you:
followed every step from assembly instruction and https://bitbucket.org/ablesystems/pipsta/wiki/Pipsta%20First-Time%20Setup
printer is connected to the power
printer is connected via usb to raspberry
printer's led doesn't blink (should be green constantly)
proper usb library is installed (or try to install different version of the usb library). What version are you using? python: print(usb.__version__) , it works fine for me with version 1.0.0rc1
is printer visible to the os? command: ls /dev/ap1400
I know this is an old question (I've only just encountered it). The following is a paraphrasing of the FAQ. The following steps should help diagnose the problem.
Download the latest set of Pipsta examples..
Extract the contents of the zip file.
Change directory to where the files were extracted
Change directory to the Examples folder.
Using a terminal run the command python verify_pipsta_install.py. This will try and help diagnose problems.
The following will should fix the python usb library error.
If your Pipsta printer firmware is V9.2.03 please upgrade the firmware to V9.2.08 using the fpu (both can be found in the downloads section of bit bucket.
Install the latest version of the Pipsta examples (download from bitbucket).
Copy the new pipsta/Examples/system_scripts/ to /etc/udev/rules.d/60-ablesystems-pyusb.rules
Restart the Raspberry Pi
If the printer still fails to be discovered then -
The following workaround may work.
1. Unplug the printer from the USB port
1. Enter the command sudo lsusb
1. Reconnect the printer
1. Enter the command sudo lsusb
If the printer has been detected by the Linux environment then either /dev/ap1400 or /dev/pipsta should exist in the filesystem.
NOTE The Pipsta now has Debian packages to help with installation. I have a link limit on my account but search for pipsta-printer-utilities-1.1.1-Linux.deb and pipsta-cups-driver-0.3.0-armhf.deb for more information.