Locked out of bios?

[Smackenroll]

Has the new bios been completely locked and no longer accessible?   I've tried the "esc" key and the "f5" key, but no luck.  If I don't press any keys then the system will start normal.  However, if I press either the esc or f5 keys then it never boots..  It just sits on a blank screen until I restart the system..  Am I doing something wrong or have they locked us out..

Thanks,

Brad

[stirrell]

Just tested with the F8 key and it gave me the option to boot into the firmware. My system is up-to-date. I also verified that the AtariCelebrates password worked for me.

[Smackenroll]

I finally figured out why I thought the system was hanging.  Apparently during boot up the signal from the VCS was not sending properly through my receiver to the TV..  So, I thought it was stuck, but it was actually sitting on the selection screen.  I plugged the VCS directly into the tv and now I can get to the bios menu.  Unfortunately, because I have a new system with the new bios, the Celebrates password won't work.  Looks like I've got to roll back the bios...  

 

Thanks for the help!

[Linux_Lover]

15 hours ago, Smackenroll said:

I finally figured out why I thought the system was hanging.  Apparently during boot up the signal from the VCS was not sending properly through my receiver to the TV..  So, I thought it was stuck, but it was actually sitting on the selection screen.  I plugged the VCS directly into the tv and now I can get to the bios menu.  Unfortunately, because I have a new system with the new bios, the Celebrates password won't work.  Looks like I've got to roll back the bios...  

 

Thanks for the help!

I'm in the same boat--can't unlock secure boot b/c the password doesn't work at all.  Have a service ticket w/atari where they had me use a flash utility and usb drive but it still didn't work.  Also I can't always access the bios w/the ESC key--more often than not, I get a black screen.  The VCS is directly connected via HDMI to the tv (no switchers).  After I told them I flashed it and the password still didn't work, they told me to try it again--which is a non-answer.  I will give them a few more days to respond to my last response made on Friday.  They marketed it as a mini-PC and are pushing it more that way than a console.  The PC mode feature was a major selling point for me.  You shouldn't have to do anything extraordinary to make it work like it was marketed to be so.  It's supposed to be a mini-pc one can add an OS of their choice.  I have no qualms w/Atari OS by itself (except the fact that the PC Mode app doesn't actually boot me into Ubuntu--an officially mentioned and recognized OS along w/Windows, per their marketing).  I do hope they rectify this since it seemed like they were being dismissive and perhaps thought I was the only one where the password didn't work.

Edited April 5, 2022 by Linux_Lover

[.nIk0.]

Atari VCS BIOS password reset
The BIOS password on the retail consoles requires flashing the BIOS back to 1.0.21 to set it to the “Celerbrate” password that it is out in the wild.
The guide and recovery image can be found at the following link. For the most part the guide is not very useful other than to tell you how to create the recovery flash drive, so I would refer to for those steps.

https://drive.google.com/drive/folders/1pgC39vlSaK-8am4cbGKLgQrnKILRU1iK?usp=sharing

There are steps you have to do that aren't in the guide, and you will need a keyboard connected to your Atari VCS to complete these steps. If you don't have a keyboard it will only flash the Atari OS not resolve the issue.
 With the power off, plug in the USB drive and connect a keyboard to your Atari VCS
You need to use the keyboard and select the flash BIOS option from the menu that appears on the screen when you power on your Atari VCS with the Atari OS Recovery USB drive the you created from the downloaded image (if you don't select anything then it will just flash the Atari OS). From the menu select "BIOS Upgrade & Reset Settings (VCS21)" and press the Enter key using the keyboard that you have connected to your Atari VCS. This process will downgrade the BIOS from 1.0.23 to 1.0.21 (the BIOS will automatically get updated again to 1.0.23 the next the the Atari VCS boot into the Atari OS).
You shouldn't need to reimage the Atari OS, but I did that as my first step before the BIOS. If you find just flashing the BIOS doesn't work then reimage the Atari OS, power off & then on again and flash the Atari VCS BIOS before the system boots into the Atari OS. After then boot into the Atari OS and let the system update the BIOS. Be patient as this might take 15-20 minutes to complete.
Once done you should be able to access the BIOS using the Atari Celebrate password.

Thanks to "xyz79001"

Atari_VCS_BIOS_password_reset__recommeded_settings.pdf

[Smackenroll]

I had to follow the guide listed above to roll back the BIOS.  I was then able to enter the bios and make the changes needed.  I've since been able to install Win10 on an internal SSD M2 drive and have it set up on the Atari.  Now I've just got to figure out the whole dual boot fiasco...  Unfortunately, because I'm running the system through my A/V receiver I can't really use the "esc" key method to boot to windows because I would be trying to do it blind..  I really need to figure out either Grub or reFind.  I see that .nIkO. has posted a reFind guide so I'll start there!  

Edited April 8, 2022 by Smackenroll

[zzip]

On 4/5/2022 at 5:13 AM, Linux_Lover said:

I have no qualms w/Atari OS by itself (except the fact that the PC Mode app doesn't actually boot me into Ubuntu--an officially mentioned and recognized OS along w/Windows, per their marketing). 

Ubuntu and Windows do work because they support secure boot.    The main issue is when people want to use OSes that don't support Secure Boot,  like Batocera for instance.

 

1 hour ago, Smackenroll said:

I really need to figure out either Grub or reFind.  I see that .nIkO. has posted a reFind guide so I'll start there!  

reFind is pretty easy,  you can put it on a bootable USB plug it in and it will detect your bootable OSes

 

After that, you may want to give it a nicer theme than the default,  and delete any bootable options you don't want to see on the boot screen.

[Linux_Lover]

On 4/8/2022 at 9:35 AM, zzip said:

Ubuntu and Windows do work because they support secure boot.    The main issue is when people want to use OSes that don't support Secure Boot,  like Batocera for instance.

 

when I don't get a black screen at boot and can load ubuntu, it works, but choosing PC mode app w/in atari os does not take me to ubuntu, which I understand is supposed to happen.  Anyway, in interviews while M.Artz was with atari and promoting the vcs, he indicated OS of your choice a couple of times.  Severe Secure Boot (for all intents and purposes is really DRM, mostly made to maintain a Windows monopoly or receive a license fee) was not a marketing point, but "freedom" was mentioned a few times and their feet should be held to the fire regarding this.

Edited April 10, 2022 by Linux_Lover

[zzip]

On 4/10/2022 at 6:41 AM, Linux_Lover said:

when I don't get a black screen at boot and can load ubuntu, it works, but choosing PC mode app w/in atari os does not take me to ubuntu, which I understand is supposed to happen.  Anyway, in interviews while M.Artz was with atari and promoting the vcs, he indicated OS of your choice a couple of times.  Severe Secure Boot (for all intents and purposes is really DRM, mostly made to maintain a Windows monopoly or receive a license fee) was not a marketing point, but "freedom" was mentioned a few times and their feet should be held to the fire regarding this.

I don't bother with choosing "PC Mode",  if your alternative OS is on an external USB drive, then plugging it in will load it by default.

For internal m.2, put grub on a USB key and choose it at boot.   I believe Grub supports secureboot, but reFind doesn't.  

[Linux_Lover]

5 hours ago, zzip said:

I don't bother with choosing "PC Mode",  if your alternative OS is on an external USB drive, then plugging it in will load it by default.

For internal m.2, put grub on a USB key and choose it at boot.   I believe Grub supports secureboot, but reFind doesn't.  

To clarify, I can access ubuntu (if and) only when I choose the drive via the boot manager.  Many times at boot I only get a black screen freeze after hitting the ESC key.  Sometimes I have to power down and wait as that usually results in more success being likely to get into the uefi bios.  Just plugging in the drive via usb has never worked for me as it does for you or others, irregardless of which port it is connected to.  PC mode app w/in Atari OS is supposed to allow one to reboot directly into Ubuntu (in my case, which is a touted OS that should definitely work per Atari's marketing).  It seems like most people can't use the PC mode option w/in Atari OS, although I could be wrong.  I won't add an M.2 (or buy any games) unless my problems w/the device are ultimately resolved by Atari.  I just got a response indicating they have referred my ticket to their engineering department so hopefully they can help.  If one installs an m.2, using a usb drive for grub may be redundant as Grub should be able to be installed into the m.2, unless one just prefers it that way.  I'm a fan of Grub, but it ironically wouldn't overcome not loading my prior peppermint 11 install.  It indicated the kernels were not signed, even though I ironically installed and ran the OS for about a day before ever installing Ubuntu as it is faster and more lightweight.  I was even able to power down the VCS and load Peppermint a few times before complaining about not being signed and refusing to load.  I don't understand why it would install and work, then complain about not being signed soon thereafter, I mean either it's supposed to be blocked from the beginning or not blocked--it's not supposed to have occurred like this afaik.  I tried to load the Peppermint kernel via Super Grub Disk 2, but the VCS refused to boot the flash drive probably b/c this software wasn't "signed" as well it seems, las Ubuntu on flash drive was able to install.  Peppermint is UEFI capable, but I guess it is not considered signed, but it's still a mystery why it initially worked, then didn't as I didn't amend or alter anything.  I have been able to run Peppermint from a myriad of PC's, including those that have a UEFI bios, but I think I disabled secure boot on most if not all of them iirc.  I'm sure if the atari passwords worked for me, disabling secure boot would allow me to run Peppermint again w/no problem

[zzip]

6 minutes ago, Linux_Lover said:

To clarify, I can access ubuntu (if and) only when I choose the drive via the boot manager.  Many times at boot I only get a black screen freeze after hitting the ESC key.  Sometimes I have to power down and wait as that usually results in more success being likely to get into the uefi bios.  Just plugging in the drive via usb has never worked for me as it does for you or others, irregardless of which port it is connected to.  PC mode app w/in Atari OS is supposed to allow one to reboot directly into Ubuntu (in my case, which is a touted OS that should definitely work per Atari's marketing).  It seems like most people can't use the PC mode option w/in Atari OS, although I could be wrong.  I won't add an M.2 (or buy any games) unless my problems w/the device are ultimately resolved by Atari.  I just got a response indicating they have referred my ticket to their engineering department so hopefully they can help.  If one installs an m.2, using a usb drive for grub may be redundant as Grub should be able to be installed into the m.2, unless one just prefers it that way.  I'm a fan of Grub, but it ironically wouldn't overcome not loading my prior peppermint 11 install.  It indicated the kernels were not signed, even though I ironically installed and ran the OS for about a day before ever installing Ubuntu as it is faster and more lightweight.  I was even able to power down the VCS and load Peppermint a few times before complaining about not being signed and refusing to load.  I don't understand why it would install and work, then complain about not being signed soon thereafter, I mean either it's supposed to be blocked from the beginning or not blocked--it's not supposed to have occurred like this afaik.  I tried to load the Peppermint kernel via Super Grub Disk 2, but the VCS refused to boot the flash drive probably b/c this software wasn't "signed" as well it seems, las Ubuntu on flash drive was able to install.  Peppermint is UEFI capable, but I guess it is not considered signed, but it's still a mystery why it initially worked, then didn't as I didn't amend or alter anything.  I have been able to run Peppermint from a myriad of PC's, including those that have a UEFI bios, but I think I disabled secure boot on most if not all of them iirc.  I'm sure if the atari passwords worked for me, disabling secure boot would allow me to run Peppermint again w/no problem

There is a lot in there, so I will respond to a few points:

 

1. The PC Mode option in Atari OS does work for me, but I find it a pain in the butt to boot into Atari OS just to reboot into Ubuntu,  so I prefer to boot directrly into Ubuntu.

2. Using the ESC key to select OS is a pain as well, it doesn't give you enough time and sometimes doesn't work.   I've seen other BIOSes with easier to access boot managers, I wish this had it.   It's why I recommend putting a boot manager on a USB key or drive.

3. It is supposed to boot USB first by default I thought?   Do you have to go into the boot manager to get USB install media to boot or does it boot automatically?   It's possible I switched my BIOS to give USB first priority, but I don't think I did.   I think this was the default.

4. The issue I've run into with m.2 is that the BIOS seems to treat it as the same class of device as the eMMC the Atari OS is installed on.   That means eMMC always takes boot priority over m.2 except when selecting "PC Mode".   I've tried all sorts of BIOS settings, I've tried changing the boot order with "efibootmgr" under linux,  but Atari OS always boots first.   This is why I had to resort to GRUB on a USB stick to get me boot control.    Some people here tell me that it is possible to make m.2 boot first in BIOS, but nobody has explained how.    So if you want your OS to have boot priority over Atari OS, USB is the way to go.   You could put Grub on that disk.

 

I supposed it's possible to install Grub/Refind onto the eMMC as well, but I don't really want to alter that.

5. Yes with a working password you can disable secure boot and get virtually any Linux distribution running.

 

EDIT:  Just found this document which confirms that external USB boots first, but also says that m.2 gets second priority.   Hmmm

https://atari.gamecentergroup.com/index.php?/VCS/Knowledgebase/Article/View/565/150/what-is-the-boot-order-when-using-multiple-operating-systems

[Linux_Lover]

It's good that your PC mode works--it's just that irregardless if one uses it or not, it should work.  I could see scenarios where one changes their mind or is finished playing games in Atari OS, and decides to go into Ubuntu/Linux or windows to do some work related tasks and choosing PC mode at that point should be faster than rebooting directly.  Remember, my VCS seems to be a lemon or arguably more wonky than others' and won't boot from usb at all unless manually going into the bios.  If you're not getting black screen freezes at boot, your vcs is working as it is supposed to afaict.  I hold down ESC even before the unit is powered on and that should work 100% of the time (mashing on this device is not required like many other pc's for some unknown reason).  That is when I'm actually able to access the uefi and not get the black screen.  That being said, based on my experience and of some others, I wouldn't doubt you still have problems after hitting the ESC key and are probably doing it according to protocol most of the time I'd bet.  I wish it did offer another key just to reach a boot mgr though like most other pc's.  I could understand and even live with having to access the bios to boot from another drive, as long as my unit was reliably accessing the OS and I could use my other preferred distro(s), like the VCS was marketed as being generally friendly like any PC.  I get that Atari OS is priority for them for the users to access and I'm not one who just bought it to be a mini PC--I bought it for all its features and even made many Youtube comments on what I'd like to see from Atari before I got the VCS and learned firsthand of its PC deficiencies as a possible worst case example.  I have followed and still follow their game announcements  although this situation has taken some of my enthusiasm.  I remain optimistic that Atari can help me, but it feels strange when I see YouTubers whose experiences have been mostly positive, at least if they're not using as a PC, and exclusively use Atari OS.  I feel disconnected b/c I want to enjoy all aspects including Atari OS, but the glaring problems of PC mode instills a cautionary mindset to enjoying much news about it.  I have read of the M.2 issues you mentioned and understand why grub works out better for you there.  I agree w/not touching the eMMC at all as someone mentioned it could just later be wiped via an Atari update anyway.  About 6 months ago, I was able to install an nvme ssd as a boot drive in an older, pre-nvme protocol pc via PCIE adaptor.  I may look back at those notes to see if I can trick the VCS to run my non-signed Peppermint since my unit is rejecting passwords thus far.  Right now, just gonna play the waiting game and not dedicate as much time into my vcs or its issues as hopefully Atari can help me eventually sort it out.  Thanks for the doc, will check it out.

[zzip]

16 hours ago, Linux_Lover said:

I remain optimistic that Atari can help me, but it feels strange when I see YouTubers whose experiences have been mostly positive, at least if they're not using as a PC, and exclusively use Atari OS.  I feel disconnected b/c I want to enjoy all aspects including Atari OS, but the glaring problems of PC mode instills a cautionary mindset to enjoying much news about it.

PC mode works pretty well.   Sounds like your main issue is the password.    Once you are in the BIOS you can disable secure boot, check out the assigned boot order and hopefully get it working the way you want.

 

One question though,  when you went to install a new Linux OS on the VCS and created a flash drive to install-   Does your VCS automatically boot from that flash drive,  or did you have to hit ESC to even get it to boot from that?