I follow this tutorial
https://docs.aws.amazon.com/deepracer/latest/developerguide/deepracer-ubuntu-update.html
on updating the deep racer software stack to Ubuntu 20.04 Software Stack. After installing the new ubuntu, I cannot enter my OS because it said "ubuntu has been blocked by the current security policy". In the BIOS menu, it doesn't have the option to disable security boot.
After that, I follow this tutorial https://github.com/awsdocs/aws-deepracer-developer-guide/blob/master/doc_source/deepracer-vehicle-factory-reset-preparation.md to try to install old Linux to revert back the process. It also gives me the same error as "ubuntu has been blocked by the current security policy".
I try to reinstall multiple times and still had no luck. I also see on AWS re:Post that some ppl are facing same issue too but n
I solved my problem, as deep racer bios do not have the option to disable secure boot. You have to make sure that the factory reset folder is unzipped, and drag all the files to the second partition of your USB as the document shows.
https://docs.aws.amazon.com/deepracer/latest/developerguide/deepracer-ubuntu-update.html
After that, you will select to boot from the USB drive after you enter the ubuntu, click install ubuntu 20. x.x.x. After installation, u need to once again to boot from USB and run the shell script in the factory reset folder in order to enter the Ubuntu. Otherwise, it will show the error it is blocked by the current security policy.
When I run the shell script, the first time I run I encountered an error saying cannot find the GPT partition table. The reason is that I skip some of the steps in the document and did not follow the step to do the partition. After I repeat the partition process. I was able to run a factory reset shell script. You should see it doing a writing block operation. After the script is finished
you should able to enter ubuntu 20. x.x.x without error.
Related
I have been trying to run vagrant up but I keep getting an error, though I have run a command for the box vagrant init ubuntu/focal64 and the result said I am ready to vagrant up but I keep getting the error message as shown in the screenshot below.
Please how can I resolve this issue?
I am in need of quick help.
You need to enable virtualization within the BIOS of your machine. When you first boot the computer, there's usually a screen saying "Hit F2" or "Hit Del" to enter setup (the key varies per motherboard manufacturer). You need to go into the BIOS setup and enable Hardware Virtualization support (VT-x on Intel machines). Consult your computer/motherboard manufacturer manual.
I have been trying to install macOS Catalina on virtual box foloowing this tutorial:
https://techsprobe.com/install-macos-catalina-virtualbox-windows/
When getting to the step of having to actually install catalina the virtual machine boots into an EFI shell
The same person who wrote the tutorial wrote a supposed fix:
https://techsprobe.com/how-to-fix-efi-internal-shell-on-macos-catalina-on-virtualbox/
The fix adds an ISO file which contains parts of an apple file system which is loaded via a startup.nsh file which you create in the shell.
The fix itself however does not work either. Now I have no idea about how EFI shells work or how "fs#" relates to loading files from the apfs ISO. Here is the startup.nsh file as well as the error associated with trying to run it:
Now like I said I dont have much of an idea of how EFI works or whats going on here in general, so feel free to educate me.
I was able to fix the UEFI problems as follows (credit to techrechard website):
At UEFI prompt: Type exit
You’ll be brought into an EFI text-mode GUI.
Select Boot Maintenance Manager and click.
Select Boot From File and click
You should see two entries in a list (they are cryptic looking PCI bus paths).
The first PCI path in the list is probably the boot partition that doesn’t contain bootable firmware. The second PCI path is probably to the recovery partition, the one you need to boot from. If the 2nd partition isn’t the recovery partition, look under the paths in the list to see if one of them is it. If the recovery partition isn’t present and valid, these instructions won’t work.
Click the 2nd entry, you should see (and then click):
macOS Install Data
Then click:
Locked Files
Then (if present), click
Boot Files
And finally click:
boot.efi
Installation will continue, or you will boot into the OS or get the Recovery Utilities menu (where macOS can be reinstalled from or Disk Utilities run). The ambiguity of that last statement is I did that awhile before writing this comment and I don’t recall what I booted into first, only that it worked and was not hard to figure out what to do at that point. If you have a recovery partition, to boot directly into the Recovery Mode turn on the Mac and immediately press and hold (⌘)-R
Apparently if you follow this link how to install catalina, you will get an error like the one you got (This is probably due tu the way virtualbox reads disks--> uefi or legacy). Mine was :‘FSL: \ system/library/coreservices \ boot EFI’ is not recognized as an internal or external command, operable program, or script file?. On another forum I found this command:
> Install.nsh
If you write it in the command line of your virtualbox MAC environment it should proceed. It worked fine when I typed it.
As a beginner with Virtual Machines and Linux I have my trouble understanding how to properly upgrade Linux on the Tegra - Board. I found some good explanations but they all were too advanced for a beginner - a student - and not a professional in the field.
Therefore, I would like to know how to properly upgrade the Linux Version on the Tegra X1 Board with a Windows machine
Step1:
Make sure you have the following items:
The Tegra Board
Admin priviliges on the Windows machine (needed once)
Micro USB-B to USB Cable
HDMI Cable and Monitor
These are all the things needed before.
Step 2
Download Linux 14.04 - it is the only distribution compatible with the Tegra Board at the moment.
http://releases.ubuntu.com/14.04/ubuntu-14.04.4-desktop-amd64.iso
Step 3
Download and install Oracle Virtual Machine. You will need admin privilages for install.
http://download.virtualbox.org/virtualbox/5.1.8/VirtualBox-5.1.8-111374-Win.exe
Step 4
Set up an NVIDIA Developer Account
https://developer.nvidia.com/group/node/873376/subscribe/og_user_node?downloadable_file=874988
Step 5
Set up the virtual machine. To do so start the installed Oracle VM Virtual Box (see Step 3). On the upper left you find the button "new". After clicking on it a window will pop up. At the bottom you can change to "Expert-Mode".
In the field "Name" you can give it a fitting phrase like "Ubuntu for Tegra" etc.. The next field Typ should be obiously Linux, and the Version 64 bit.
Set the memory size to a good fitting size, depending on how much RAM you got on your machine. It works fine with 6 GB, anything smaller could lead to some lagging, but will still run.
Put the radio button in the middle so it will create a hard drive.
Go to the next step by hitting "Create"
Step 6
In this window two inputs are interesting. Firstly, it needs a path where to create the virtual environment. So choose a path to a disk that has enough space. Secondly, how many space you give to the environment - 50 gb will work fine.
Step 7
Launch it by selecting the newly created environemt and then hitting "Start". You will be asked to choose a medium to be booted. Here select the downloaded .iso file from step 2.
Step 8
You will be greeted with the Linux-Install environemnt. You can choose between "Try" and "Install". You must choose "Install".
Step 9
After you instaleld Linux you must restart the Virtual Machine. To do so, you can either do it by "normaly" shutting down Linux via the GUI or the command Line tool or from the VM-Software directly by right-clicking on the running virtual machine - close - power down.
Step 10
You may encounter the problem that you do not see the full screen of the Linux environment. To fix this you need to restart the virtual machine. On the virtual machine display at the top bar you can see the entry "devices". If you click on it a drop down menu will open, the last point is "guest additions", click on it and install them. After that reboot the virtual machine.
Step 11
On the virtual machine log in on your NVIDIA Account and download the latest Jetpack Version.
https://developer.nvidia.com/embedded/downloads?#?dn=jetpack-for-l4t-2-3
https://developer.nvidia.com/embedded/jetpack
Step 12
After downloading a file with the extension .run should be in your Downloads-Folder. This is the installation file needed, but it is not executable yet. To make it executable open a shell (right click on the upper left ubuntu symbol, search for terminal and open it).
Go to the Downloads folder with:
cd ~/Downloads
and make the run file executable:
sudo chmod u+x *.run
Step 12
Run the .run file with
sudo *./run
Step 12
In the installer choose the board and the software you want to be installed, also agree the software license agreements. After some downloading time the installer will open a terminal.
If the prompt asks you about Network Layout. If it does, choose eth0 if you have you board connected via ethernet cable, if it is connected via Wi-fi choose wlan0.
Step 13
You need to put the Tegra Board in recovery mode. Make sure that all your data is saved, since it will wipe everything clean.
Follow the instructions on the terminal to put the Tegra Board in recovery mode. If directions unclear follow this youtube video (which also includes some followign steps):
https://youtu.be/4JUWS9i_FCQ
Step 14
When you think the Tegra is in recovery mode check by doing the following: At the virtual machine, on the top bar go the "devices" and then to USB. Select the NVIDIA entry. If it is not there, the board is not in recovery mode. Make sure that this was really selected. (It is highlighted blue when selected)
Step 15
Back in the Linux virtual machine enter lsusb on a second terminal. If there is an entry with NVIDIA Corp the tegra board was successfully put into recovery mode. Press enter, now the flashing starts - this will take some time
Step 16
After flashing finishes, the jetson board will auomatically boot. Connect it to an HDMI Cable and Monitor. If a login is asked, the username and password are ubuntu.
Step 17
Connect to the Internet
Either connect it to the ethernet or a Wifi - depending on what you have chosen at step 12. You may need to disable Wifi to connect via ethernet cable.
Step 18
If you use static IPs you can skip this part since you already now the IP-Adress you gave to the tegra board. If not you have to run
ifconfig
in a terminal. It will show you your adapters and what IP-Adresses they have, note the one that you chose.
Step 19
The Post Installation in the virtual machine either has given up and was unable to determine the IP adress of the Jetson Developer Kit or has found it. If it has not found it give it manually the ip adress you found out by entering "2". After this a GUI is shown where you can enter the Ip-Adress and the username password combo, which is ubuntu.
Step 20
After hitting Next the installation will continue.
I installed linux debian as a 2nd system and it works fine, however when I choose Windows in loader(lilo) to boot, it stops on a windows logo.
I tried to boot in safe mode, and it stops on classpnp.sys driver.
I'm not sure whether the problem is in classpnp or in some other driver which is failed to load after it.
I also tried to boot with bootlog (ntbtlog), however it is not created (I check C:\Windows).
It seems like smth is wrong with hard drive configuration with several partitions.
I've googled a lot of similiar issues with classpnp.sys, but none of the solutions helped:
-I tried to change bios SATA coniguration from IDE to AHCI,
-restore backup configuration files (SAM, DEFAULT, SECURITY etc).
If anyone knows what else can I do with this, please help.
This belongs on super user, but you need to press F8 and select safe mode. There you can fix your problems
I am trying to build v1.2 of firefox os for my zte-open. With a few hiccups I was a able to configure and build it using the inari device profile. But the process fails at the last stage of flashing.
here is the output of the ./flash.sh command
rog% sudo ./flash.sh
[sudo] password for abhiram:
< waiting for device >
erasing 'cache'...
OKAY [ 0.531s]
finished. total time: 0.531s
erasing 'userdata'...
OKAY [ 1.399s]
finished. total time: 1.399s
sending 'userdata' (53571 KB)...
OKAY [ 4.518s]
writing 'userdata'...
FAILED (status read failed (No such device))
finished. total time: 9.911s
After that the device starts fresh with no userdata (obviously). Right now I am guessing that if it passes the user-data phase it might flash the system and boot partitions.
Btw, my phone running the version 1.1 of the firmware, which was from an official Zte update.
update
I tried flashing separate partitions of (system and boot) but the it gives me the same error.
with ./flash.sh system
FAILED (status read failed (No such device))
I have this same problem. However I do not think that fastboot is disabled.. I say that because I can see ROAMER2 if I do a
fastboot devices
Please note.. if you cannot preform that command try running the following command first
adb reboot bootloader
after this I bet you will be able to see the devices using the fastboot command.
So fastboot seems to be able to connect to the device and the fastboot command erasing cache seemed to have worked, and the fastboot command erasing userdata command worked. So my guess is that it is not fastboot itself but the device preventing the push from occurring.
Perhaps there is a log we can read somewhere?
Update:
I called the company. Their official line is that they do not support updating the phone and you should only use the Update feature on the phone itself. There is an update coming however it is being pushed out one a time not a global push to all devices. In some blogs on this subject I saw users complain that the device is advertised as open but is not in fact open. Point being this: If the device is preventing the push as I suspect (then we as a consumer have been tricked) and the device is operating correctly.
Update: (more info)
There is a set of problems and it depends on if you upgraded your phone or not. If you read the discussion here I think it pretty much covers everything: http://www.reddit.com/r/FireFoxOS/comments/1ugx5g/firefoxos_buils_for_zte_open/
Also check to see if your device is rooted by the following
adb shell
if you see $ continue to the next command, if you see # you have root
su
If you are in the same boat as me, and have updated to 1.1 using the ZTE images. Then you are a little stuck. We need to downgrade back to 1.0 revision 2 (B02). This will require the clockwork mod recovery to do this. The problem is that we also need the original img. ZTE has taken this image down. If you have this image or if you can find it please upload it and post it here and in the link I provided (you'll be a hero to a very small group of nerds). Otherwise.. a Mozilla developer stated that ZTE will have yet another update coming soon. (However chances are this is going to be yet another locked down version). So the hunt in on for the original image.
After emailing the b2g-dev mailing list, I figured out that this was a problem with the firmware of the zte-open.
AFAIK, the latest firmware update to 1.1 brings all the devices to OPEN_US_DEV_FFOS_V1.10B01 firmware, which for some reason comes with fast-boot disabled. Hence it is not possible to flash it.
It looks like zte are working to bring out a new update that comes with fastboot enabled. So I guess I'll have to just wait it out.
Update
It took me a while to figure out how to update the damn phone, to upgrade you need to downgrade to the firmware 1.0B02 on which fastboot seems to work.
To downgrade I had to install clockworkmod as the default recovery program complains of signature mismatch( Zte! can't I donwngrade to your older official firmware?).
Rooting and installing clockworkmod, I had to remove some assert checks on the device-name from the updater-script and then pack it. Once this is done downgrading the device is quite simple.
After this I had to individually flash the three images (boot,system,userdata) using fastboot flash command