I'm facing the same issue as KleberCabral with my corporate Macbook Pro Serie 2019. The Keyboard and Trackpad are not responding in any mode (exam, test, recovery).
"After booting to the RE Image, were you able to click 'ok' or hit 'enter' at the "Welcome to Red Hat Remote Exams - Click OK to configure your keyboard layout" screen? "
From this screen, my pointer is in the bottom right corner and not responding.
I cannot use the keyboard (ESC, enter, arrows, ...) to validate the Welcome message.
And unfortunately, I don't have any spare USB ports available to plug an external keyboard or mouse. Last Macbook pro series comes with Thunderbolt 3 (USB-C) adapters only. I have a USB-C network adapter to plug a network cable, and a USB-C adapter to plug the USB image.
In addition, I even tried to get into a single boot mode from the grub. But in fact, I cannot send the Ctrl+x signal to start from the modified grub. Ctrl+c is working using the Control+Command+c keys.
I used the RHEL-20200630 image to build my USB device. Is there any newer version?
Furthermore, please be aware that the last Mac series includes a T2 security chip to avoid external device boot. You may have to include a link to the Apple support article to explain how to modify the secure boot.
Booting on the Fedora USB image requires the following option to be selected:
- No security
- Allow booting from external media
In my case, I also had to select the right-hand EFI boot image from the device list to get to the menu, the left one was redirecting to the Macbook utility "Startup Manager"
Waiting to hear from you soon about a fix for Macbook Pro Series 2019.
Hi @vincentlours, I haven't read your entire post, yet.
I saw you mentioned about using a corporate laptop, that's not the first time some users are trying that.
There is nothing against it in theory. In practice, these are usually secured and restricted by other teams, and there are changes outside of most users control. For example if Secure Boot is enabled in the bios, it's usually not possible to boot to an USB device.
There are also some technical restrictions, when a corporate computer has to be compliant with specific security standards, that disable the use of any USB device.
I am a bit conflicted with that information, I will report that to the team writing the "Getting Ready" document, for further analysis!
Thanks for sharing your feedback!
1) And unfortunately, I don't have any spare USB ports available to plug an external keyboard or mouse.
Candidates are responsible for "Getting Ready". Currently, it means that your laptop is not matching the requirements in terms of USB ports. (well, since there is a technical issue not allowing you to use keyboard + track pad).
You are allowed to use an USB Hub : One wired USB hub is allowed if a hub is needed to accommodate permitted peripheral devices as described below.
These devices are very cheap usually, or even borrow one, as a temporary workaround.
2) I used the RHEL-20200630 image to build my USB device. Is there any newer version?
The latest image is here:
Currently, there is no versionning or method to verify the iso file integrity. That feedback was sent to the relevant teams and they are working on improving that.
3) You may have to include a link to the Apple support article to explain how to modify the secure boot.
Thanks for the information and the suggestion! Secure Boot is an example of security implementation, that can prevent users from booting their computer from a live usb device. There are actually many other implementations like that.
I think it's not practical to list explanations and configurations changes for every type of hardware. I also think that it would be nice to have some generic information about that in the "Getting Ready" document, for candidates who are less familiar with that topic. I have forwarded your feedback also, to the relevant team. For your information, various teams are reading the candidates feedback on learn.redhat.com and also the feedback sent using the comments form. It's possible they are are aware of similar feedback and working on improving the documentation.
4) I heard the technical team is looking at Macbook Pro Series 2019 compatibility issue(s). Since currently there is no versionning, I wonder how they will communicate about that. @shefeeqyr Could you kindly shed some light on that one?
Can anyone clarify, is it possible to use wi-fi connection or wired connection required? I don't have physical possibility to use wired connection, only wi-fi.
Possible it is, but red hat dont recommend it, there are more posibilities of connection error, but yes it is possible with wifi.
Hi @Tim_757 ,
I'll quote the comment from an earlier discussion on wireless connections - https://learn.redhat.com/t5/General/Questions-about-getting-ready-for-your-Red-Hat-remote-exam/m-p/1...
Wireless connection: We strongly recommend a wired connection for better stability. Wireless is not prohibited perse, however it is considered as a second choice due to many variables that can impact wireless performance. I would login to the wireless router and block any other device accessing the internet at the time of my exam. Or simply tell other users to pause the usage during that timeframe.
Personally, I was also in the same boat as you and had no choice but to use a wireless connection for my remote exam. My own experience on WiFi was positive and I did not encounter any network/connection errors for the entire duration of the exam.
I have only my government issue national identity card which is not in English language.so I choose the that option when I scheduleing my remote exam. But when I proceed to the exam proctor said he need a english version to prove my identity.due to the connection issues I couldn't do the exam.But how could I prove my identity cosidering I don't have any government issue english language identity method(passport or driving license).what alternative redhat can offer me to considering my situation .
The scheduler application is supposed to prompt for countries with non-English ID for pre-approval. I would recommend raising a ticket with the support team to get this sorted.