selrahal/user-documentation
1
0
Fork 0
forked from server/user-documentation
Code Pull requests Activity

Revoke nomodeset workaround that is no longer required by 1.4.

Browse source
This commit is contained in:
Peter Boy 2024-11-10 16:47:42 +01:00
commit 155912dda9
1 changed files with 8 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

27
docs/modules/ROOT/pages/installation/interactive-remote.adoc
View file

@ -2,7 +2,7 @@
Peter Boy; Kevin Fenzi; Jan Kuparinen
:page-authors: {author}, {author_2}, {author_3}
:revnumber: F35-F40
:revdate: 2024-04-26
:revdate: 2024-11-10
:numbered:
@ -68,20 +68,12 @@ There are several options to boot the server, depending on the ethernet connecti
+
image:installation/interactive-remote-010.png[Boot Menu]
2. In the menu, select the kernel you want to boot and type _e_ to get access to the boot options
+
In case of F40 and earlier append the options
2. In the menu, select the kernel you want to boot and type _e_ to get access to the boot options and append
+
--
inst.vnc inst.vncpassword=PASSWORD
--
+
In case of F41 append the options
+
--
nomedeset inst.vnc inst.vncpassword=PASSWORD
--
+
to the end of the command line. Setting a password is not optional here. Replace PASSWORD with the password of your choice. It must be between 6 and 8 characters long.
+
[IMPORTANT]
@ -94,12 +86,6 @@ The above configuration requires an active DHCP server. With none available, you
--
ip=ip::gateway:netmask:hostname:interface:none inst.vnc inst.vncpassword=PASSWORD
--
+
In case of F41 it is
+
--
nomodeset ip=ip::gateway:netmask:hostname:interface:none inst.vnc inst.vncpassword=PASSWORD
--
3. Leave the editing mode by <ctrl>-x or F10 to continue to boot and to start the installation using the selected kernel and the edited options. You get the message
+
@ -183,8 +169,6 @@ If the network configuration does not allow or enable static interface configura
. On your server, connect the installation medium as well as the OEMDRV medium and boot. The server will use the OEMDRV stick, configure the interface and start VNC. Just in case you have at least a monitor without keyboard and mouse, you will see the corresponding message. Otherwise, trust your configuration.
_Mind you, you can't use this method with release f41!_
Continue with __3.2. Connecting to the server__.
==== No console access available – patch installation medium
@ -224,7 +208,7 @@ Host is up (0.00068s latency).
Nmap done: 256 IP addresses (12 hosts up) scanned in 2.38 seconds
----
+
Look for an entry with open state of port 5091 and no hostname or unknown hostname. Among them you will probably find the device you are looking for. In the example above it is 192.168.158.200.
Look for an entry with open state of port 5901 and no hostname or unknown hostname. Among them you will probably find the device you are looking for. In the example above it is 192.168.158.200.
. On the desktop start the VNC viewer, enter the IP address obtained in the previous step and port 5901 into the Connection Details dialog. Then, click Connect. The VNC viewer will now connect to the installation system. If you set up a VNC password, enter it when prompted and press OK.
@ -236,6 +220,11 @@ You will be presented with the familiar language selection menu.
image:installation/interactive-remote-015.png[]
+
This window will provide full remote access to the installer until the installation finishes and the system reboots for the first time.
+
[TIP]
====
If the screen freezes after some mouse or keyboard actions, add the kernel option __nomodeset__ before the term _inst.vnc_ to the kernel commad line in step __3.1.1__.
====
You can then proceed with xref::installation/interactive-local.adoc[Fedora Server interactive local installation].