How does one install F35? I've got the workstation iso on a DVD. It runs, but clicking on install seems to have little or no effect. I certainly do not get any prompts for the next step. What is the magic formula?
BTW I do not have the wiggle room for dual boot. I backed up my home directory and edited my partitions before running the DVD.
Do I need to have an internet connection available to do the install? The first time I tried this, an "update" or whatever it was doing took over an hour before I gave up. I'd prefer a separate update step that I can watch.
The joy of installion is a reason I do it so rarely.
On 4/3/22 14:23, Michael Hennebry wrote:
How does one install F35? I've got the workstation iso on a DVD. It runs, but clicking on install seems to have little or no effect. I certainly do not get any prompts for the next step. What is the magic formula?
Clicking the install button should bring up the Anaconda installer window. If that doesn't work, then open a terminal and run "liveinst" to see what's going wrong.
Do I need to have an internet connection available to do the install?
You don't need an internet connection if you use the workstation live installer.
The first time I tried this, an "update" or whatever it was doing took over an hour before I gave up.
That doesn't make sense. The live image should not be doing any updates.
I'd prefer a separate update step that I can watch.
That is the way it works. This late in the cycle, I recommend using a live respin instead to reduce the amount of updates required after installing.
The joy of installion is a reason I do it so rarely.
I've never had trouble with the installer. It's quick and simple. But I prefer to update so I don't have to do all the personal configuration and extra packages all over again.
On Sun, 3 Apr 2022, Samuel Sieb wrote:
Clicking the install button should bring up the Anaconda installer window. If that doesn't work, then open a terminal and run "liveinst" to see what's going wrong.
Alas: liveuser@localhost-live ~]$ su [root@localhost-live liveuser]# liveinst Starting installer, one moment... anaconda 35.22.2-3.fc35 for Fedora 35 started. * installation log files are stored in /tmp during the installation * shell is available on TTY2 and in second TMUX pane (ctrl+b, then press 2) * when reporting a bug add logs from /tmp as separate text/plain attachments
(anaconda:2388): PkGtkModule-WARNING **: 19:39:05.696: Error connecting to PK session instance: Error receiving data: Connection reset by peer
At least its an error message, even if I do not know what it means. I did have an internet connection available, but I'm not sure that matters here.
Here is /tmp/anaconda.log : 19:38:45,766 INF core.configuration.profile: Loading information about profiles from /etc/anaconda/profile.d. 19:38:45,769 INF core.configuration.profile: Found the 'centos' profile at /etc/anaconda/profile.d/centos.conf. 19:38:45,769 INF core.configuration.profile: Found the 'fedora-eln' profile at /etc/anaconda/profile.d/fedora-eln.conf. 19:38:45,770 INF core.configuration.profile: Found the 'fedora-iot' profile at /etc/anaconda/profile.d/fedora-iot.conf. 19:38:45,771 INF core.configuration.profile: Found the 'fedora-server' profile at /etc/anaconda/profile.d/fedora-server.conf. 19:38:45,772 INF core.configuration.profile: Found the 'fedora-silverblue' profile at /etc/anaconda/profile.d/fedora-silverblue.conf. 19:38:45,773 INF core.configuration.profile: Found the 'fedora-workstation' profile at /etc/anaconda/profile.d/fedora-workstation.conf. 19:38:45,773 INF core.configuration.profile: Found the 'fedora' profile at /etc/anaconda/profile.d/fedora.conf. 19:38:45,774 INF core.configuration.profile: Found the 'ovirt' profile at /etc/anaconda/profile.d/ovirt.conf. 19:38:45,776 INF core.configuration.profile: Found the 'rhel' profile at /etc/anaconda/profile.d/rhel.conf. 19:38:45,777 INF core.configuration.profile: Found the 'rhvh' profile at /etc/anaconda/profile.d/rhvh.conf. 19:38:45,778 INF core.configuration.profile: Found the 'scientific-linux' profile at /etc/anaconda/profile.d/scientific-linux.conf. 19:38:45,778 DBG core.configuration.profile: Detecting a profile for ID=fedora, VARIANT_ID=workstation. 19:38:45,778 INF core.configuration.profile: The 'fedora-workstation' profile is detected. 19:38:45,779 INF core.configuration.anaconda: Load the 'fedora-workstation' profile configuration. 19:38:45,788 INF main: /sbin/anaconda 35.22.2-3.fc35 19:38:45,801 INF core.util: Reporting the IPMI event: 7 19:38:48,103 INF isys: 8179144 kB (7987 MB) are available 19:38:48,120 INF startup_utils: check_memory(): total:7987, needed:320, graphical:410 19:38:48,121 DBG startup_utils: Don't set up proxy variables. 19:38:48,126 INF startup_utils: Unable to connect to DBus session bus: Unable to connect to session bus: g-io-error-quark: Error sending credentials: Error sending message: Broken pipe (44) 19:38:48,127 INF main: anaconda called with cmdline = ['/sbin/anaconda', '--liveinst', '--graphical'] 19:38:48,127 INF main: Default encoding = utf-8 19:38:48,128 INF misc: Configuration loaded from: ['/etc/anaconda/anaconda.conf', '/etc/anaconda/profile.d/fedora.conf', '/etc/anaconda/profile.d/fedora-workstation.conf', '/etc/anaconda/conf.d/00-do-nothing.conf', '/etc/anaconda/conf.d/01-still-do-nothing.conf'] 19:38:48,129 INF misc: Writing the runtime configuration to: /run/anaconda/anaconda.conf 19:38:48,298 INF core.dbus: Connecting to the Anaconda bus at unix:abstract=/tmp/dbus-k8Ev0FXkSL,guid=69b96da7ddc97115a474f084624a3008. 19:38:54,762 INF main: Found a kickstart file: /usr/share/anaconda/interactive-defaults.ks 19:38:54,845 INF startup_utils: Parsing kickstart: /usr/share/anaconda/interactive-defaults.ks 19:38:55,128 WRN misc: /usr/lib64/python3.10/site-packages/pyanaconda/modules/payloads/base/utils.py:24: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives from distutils.version import LooseVersion
19:38:55,194 DBG localization: setting locale to: en_US.UTF-8 19:38:55,210 INF threading: Running Thread: AnaWaitForConnectingNMThread (140252639958592) 19:38:55,211 DBG anaconda: setting display mode to GUI 19:38:55,227 INF anaconda: Display mode is set to 'interactive graphical mode'. 19:38:55,231 INF isys: 8179144 kB (7987 MB) are available 19:38:55,242 INF network: got 0 NTP servers from DHCP 19:38:55,246 INF startup_utils: check_memory(): total:7987, needed:320, graphical:410 19:38:55,250 INF threading: Thread Done: AnaWaitForConnectingNMThread (140252639958592) 19:38:57,879 DBG ui.lib.addons: Loading spokes into module path for addon com_redhat_kdump 19:38:58,190 DBG core.storage: LABEL=OEMDRV matches [] for devicetree=None and disks_only=True 19:38:58,209 INF threading: Running Thread: AnaStorageThread (140252639958592) 19:38:58,215 INF threading: Running Thread: AnaTimeInitThread (140252279944768) 19:38:58,228 DBG payload.manager: Restarting payload thread 19:38:58,232 INF threading: Running Thread: AnaPayloadRestartThread (140252271552064) 19:38:58,234 INF geoloc: Geolocation is enabled. 19:38:58,236 INF threading: Running Thread: AnaPayloadThread (140252263159360) 19:38:58,236 INF threading: Thread Done: AnaPayloadRestartThread (140252271552064) 19:38:58,237 DBG payload.manager: Updating payload thread state: STARTED 19:38:58,237 DBG payload.manager: Updating payload thread state: WAITING_STORAGE 19:38:58,239 INF threading: Running Thread: AnaGeolocationRefreshThread (140252254766656) 19:38:58,239 DBG startup_utils: Skip the time synchronization. 19:38:58,239 INF geoloc: Starting geolocation lookup 9:38:58,241 INF geoloc: Geolocation provider: Fedora GeoIP 19:38:59,759 WRN misc: /usr/lib/python3.10/site-packages/urllib3/connection.py:512: DeprecationWarning: ssl.match_hostname() is deprecated match_hostname(cert, asserted_hostname)
19:39:00,343 DBG ui.gui: Window scale set to 1 by XSETTINGS, not scaling 19:39:00,457 INF geoloc: Geolocation lookup finished in 2.2 seconds 19:39:00,457 INF geoloc: got results from geolocation 19:39:00,458 INF threading: Thread Done: AnaGeolocationRefreshThread (140252254766656) 19:39:00,619 DBG localization: setting locale to: en_US.UTF-8 19:39:01,093 DBG localization: setting locale to: en_US.UTF-8 19:39:01,180 DBG ui.common: Entered spoke: WelcomeLanguageSpoke 19:39:01,185 WRN misc: /usr/lib/python3.10/site-packages/gi/overrides/Gdk.py:329: DeprecationWarning: Gdk.Cursor.new is deprecated return cls.new(*args, **kwds)
19:39:09,100 INF threading: Thread Done: AnaStorageThread (140252639958592) 19:39:09,101 DBG payload.manager: Updating payload thread state: WAITING_NETWORK 19:39:09,212 DBG payload.manager: Updating payload thread state: FINISHED 19:39:09,212 INF threading: Thread Done: AnaPayloadThread (140252263159360) 18:39:10,004 INF threading: Thread Done: AnaTimeInitThread (140252279944768)
I do see some complaints (Unable to connect) in there, but none seem fatal.
I copied the DVD, /dev/sr0 , to an iso file. Its sha256sum is correct.
I need food.
On 4/3/22 17:17, Michael Hennebry wrote:
On Sun, 3 Apr 2022, Samuel Sieb wrote:
Clicking the install button should bring up the Anaconda installer window. If that doesn't work, then open a terminal and run "liveinst" to see what's going wrong.
Alas: liveuser@localhost-live ~]$ su [root@localhost-live liveuser]# liveinst
You need to run it as the user, not root.
Just wondering if the iso burned to DVD "completely / correctly"?....I've done countless Fedora installs/updates/upgrades, and a lot of times the DVD / CD procedure doesn't work as well as the USB procedure does....just my two cents...
EGO II
On Sun, Apr 3, 2022, 5:24 PM Michael Hennebry < hennebry@web.cs.ndsu.nodak.edu> wrote:
How does one install F35? I've got the workstation iso on a DVD. It runs, but clicking on install seems to have little or no effect. I certainly do not get any prompts for the next step. What is the magic formula?
BTW I do not have the wiggle room for dual boot. I backed up my home directory and edited my partitions before running the DVD.
Do I need to have an internet connection available to do the install? The first time I tried this, an "update" or whatever it was doing took over an hour before I gave up. I'd prefer a separate update step that I can watch.
The joy of installion is a reason I do it so rarely.
-- Michael hennebry@web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Sun, 2022-04-03 at 16:23 -0500, Michael Hennebry wrote:
How does one install F35? I've got the workstation iso on a DVD. It runs, but clicking on install seems to have little or no effect. I certainly do not get any prompts for the next step. What is the magic formula?
Have you booted from the disc?
I don't think you can slip the disc into a running installation and start installing from the disc, that way.
BTW I do not have the wiggle room for dual boot. I backed up my home directory and edited my partitions before running the DVD.
A problem with pre-partitioning is that installations may want to only use free space on your drive. Free space isn't a formatted partition with no files on it, it's un-used, unpartitioned, space. Also you may pick partition sizes that don't work well, or boot partitions of the wrong type (UEFI versus old-school, etc).
There are usually install options which say to use the whole drive, in which case it was pointless pre-partitioning your drive. It's going to wipe the lot.
With a certain amount of hunting around it was possible to go into manual partitioning in the installers and select ones you'd already made, overriding it doing things automatically. Not that I can recall trying this with recent releases.
Do I need to have an internet connection available to do the install?
Shouldn't be needed. It might help with installation logs, if you want them to have correct times.
The first time I tried this, an "update" or whatever it was doing took over an hour before I gave up. I'd prefer a separate update step that I can watch.
My experience has been doing installs from Live ISO files lately, where it virtually dumps the live ISO contents onto the hard drive. Afterwards, your first boot offered to do updates.
Other distro installs (I've done a few recently, so my recollections of how each one went is getting scrambled), can do a basic install of set package groups controlled from the installer, but actually fetching the most recent packages from the internet instead of from the install disc. I think only NetInstall discs did this on Fedora.
The joy of installion is a reason I do it so rarely.
Likewise. I don't install each Fedora release, as well the installing, it's too much wasting of my time to figure out where things have changed to, to do it that often. On other computers I've been trying out long-term versions for the same reason (CentOS on a server, Ubuntu for friends, Mint on my ancient laptop).
I can't remember if my last install was Fedora 34 or 35. I do recall it wasn't practical on my laptop (too old and slow for the graphical desktop, and the screen kept flashing in use).
On 4/3/22 23:00, Tim via users wrote:
With a certain amount of hunting around it was possible to go into manual partitioning in the installers and select ones you'd already made, overriding it doing things automatically. Not that I can recall trying this with recent releases.
I've never had any trouble telling Anaconda that I want to use a custom partitioning scheme.
Tim:
With a certain amount of hunting around it was possible to go into manual partitioning in the installers and select ones you'd already made, overriding it doing things automatically. Not that I can recall trying this with recent releases.
Joe Zeff:
I've never had any trouble telling Anaconda that I want to use a custom partitioning scheme.
It might have been a release or two back, but there was one where it wasn't very obvious how to get into customising such things. Some nondescript icon in the corner of the display.
On Tue, 5 Apr 2022, Tim via users wrote:
Joe Zeff:
I've never had any trouble telling Anaconda that I want to use a custom partitioning scheme.
It might have been a release or two back, but there was one where it wasn't very obvious how to get into customising such things. Some nondescript icon in the corner of the display.
In the case at hand, there was automatic; custom and advanced custom; i.e. the one on the corner. Custom accepted a list of partition sizes and would repartition the volume. Advanced custom allowed using existing partitions.
On Mon, 4 Apr 2022, Tim via users wrote:
On Sun, 2022-04-03 at 16:23 -0500, Michael Hennebry wrote:
How does one install F35? I've got the workstation iso on a DVD. It runs, but clicking on install seems to have little or no effect. I certainly do not get any prompts for the next step. What is the magic formula?
Have you booted from the disc?
I booted from the DVD. Starting the installer from the GUI did not work. Starting the installer from a terminal, either as root or as liveuser did not work.
Eventually I discovered the simple graphical version or something like that. It ran, though horribly not well. After suffering greatly because necessary parts of images overflowed the screen, I decided to put the whole works on partition 3 and fix it by hand later. Some things scrolled, but not all. After getting things set up, lo and behold, no begin button on screen. One tab and a return did not work. Two tabs and a return did.
It told me it was finished without prompting me for a root password or another user name. I was under the impression it was supposed to do that.
The shadow password file on partition 3 is full of empty passwords.
I don't think you can slip the disc into a running installation and start installing from the disc, that way.
On Mon, 4 Apr 2022, Samuel Sieb wrote:
On 4/3/22 23:10, Michael Hennebry wrote:
It told me it was finished without prompting me for a root password or another user name. I was under the impression it was supposed to do that.
The workstation install sets up the initial user at the first boot of the installed system.
From what documentation I could find, root gets its password at install time and the intial user is optional.
That said, I'll try it.
On Mon, 4 Apr 2022, Michael Hennebry wrote:
On Mon, 4 Apr 2022, Samuel Sieb wrote:
On 4/3/22 23:10, Michael Hennebry wrote:
It told me it was finished without prompting me for a root password or another user name. I was under the impression it was supposed to do that.
The workstation install sets up the initial user at the first boot of the installed system.
From what documentation I could find, root gets its password at install time and the intial user is optional.
That said, I'll try it.
I tried it. It asked for an intial user, but no root password. Also, I was looking at gshadow rather than shadow. shadow contains dots and asterisks for passwords. I couldn't su to root, but I could sudo sh.
There are other problems. I seem to have the same screen resolution as I did when installing. I do not know the actual resolution. xwininfo is not present. xrdb hangs. The resolution is not good.
It might be twelve hours or more before I can get back to this computer.
On 4/4/22 08:59, Michael Hennebry wrote:
On Mon, 4 Apr 2022, Michael Hennebry wrote:
On Mon, 4 Apr 2022, Samuel Sieb wrote:
On 4/3/22 23:10, Michael Hennebry wrote:
It told me it was finished without prompting me for a root password or another user name. I was under the impression it was supposed to do that.
The workstation install sets up the initial user at the first boot of the installed system.
From what documentation I could find, root gets its password at install time and the intial user is optional.
That said, I'll try it.
I tried it. It asked for an intial user, but no root password. Also, I was looking at gshadow rather than shadow. shadow contains dots and asterisks for passwords. I couldn't su to root, but I could sudo sh.
Yes, it doesn't set the root password. You are expected to use sudo. If you want to directly use root, then you can do "sudo passwd" to set the password.
There are other problems. I seem to have the same screen resolution as I did when installing.
That is expected. It's the same OS that you used for installing.
I do not know the actual resolution. xwininfo is not present. xrdb hangs. The resolution is not good.
What is your video device? Workstation uses Wayland by default, so the X info applications are not very useful, they will be getting info from the XWayland server. If you want to know the resolution, use the Displays panel in Settings.
On 4/4/22 11:21, Samuel Sieb wrote:
Yes, it doesn't set the root password. You are expected to use sudo. If you want to directly use root, then you can do "sudo passwd" to set the password.
Actually, in the GUI version of Anaconda, there's a place where you can set the root password, but you don't have to do it and it looks like you're not supposed to because most people don't want it set.
On 4/4/22 10:54, Joe Zeff wrote:
On 4/4/22 11:21, Samuel Sieb wrote:
Yes, it doesn't set the root password. You are expected to use sudo. If you want to directly use root, then you can do "sudo passwd" to set the password.
Actually, in the GUI version of Anaconda, there's a place where you can set the root password, but you don't have to do it and it looks like you're not supposed to because most people don't want it set.
Not in the live installer (at least for workstation).
On 4/4/22 12:49, Samuel Sieb wrote:
On 4/4/22 10:54, Joe Zeff wrote:
On 4/4/22 11:21, Samuel Sieb wrote:
Yes, it doesn't set the root password. You are expected to use sudo. If you want to directly use root, then you can do "sudo passwd" to set the password.
Actually, in the GUI version of Anaconda, there's a place where you can set the root password, but you don't have to do it and it looks like you're not supposed to because most people don't want it set.
Not in the live installer (at least for workstation).
Really? Because that's what I used to install F 35 on this laptop and part of the installation was setting the root password.
On 4/4/22 12:06, Joe Zeff wrote:
On 4/4/22 12:49, Samuel Sieb wrote:
On 4/4/22 10:54, Joe Zeff wrote:
On 4/4/22 11:21, Samuel Sieb wrote:
Yes, it doesn't set the root password. You are expected to use sudo. If you want to directly use root, then you can do "sudo passwd" to set the password.
Actually, in the GUI version of Anaconda, there's a place where you can set the root password, but you don't have to do it and it looks like you're not supposed to because most people don't want it set.
Not in the live installer (at least for workstation).
Really? Because that's what I used to install F 35 on this laptop and part of the installation was setting the root password.
Was it the workstation live image? I just checked it and the only options are Keyboard, Time & Date, and Storage.
I usually use the netinst image and that has all the options.
On 4/4/22 13:19, Samuel Sieb wrote:
Was it the workstation live image? I just checked it and the only options are Keyboard, Time & Date, and Storage.
It was the regular XFCE live image. It looks like the option to set the root password isn't active but if you click on it you're allowed to set it.
On 4/4/22 13:00, Joe Zeff wrote:
On 4/4/22 13:19, Samuel Sieb wrote:
Was it the workstation live image? I just checked it and the only options are Keyboard, Time & Date, and Storage.
It was the regular XFCE live image. It looks like the option to set the root password isn't active but if you click on it you're allowed to set it.
Yes, some of the spins have user and/or root configuration, but this has all been about workstation specifically.
On Mon, 4 Apr 2022, Samuel Sieb wrote:
On 4/4/22 08:59, Michael Hennebry wrote:
On Mon, 4 Apr 2022, Michael Hennebry wrote:
On Mon, 4 Apr 2022, Samuel Sieb wrote:
On 4/3/22 23:10, Michael Hennebry wrote:
It told me it was finished without prompting me for a root password or another user name. I was under the impression it was supposed to do that.
There are other problems. I seem to have the same screen resolution as I did when installing.
That is expected. It's the same OS that you used for installing.
I do not know the actual resolution. xwininfo is not present. xrdb hangs. The resolution is not good.
What is your video device? Workstation uses Wayland by default, so the X info applications are not very useful, they will be getting info from the XWayland server. If you want to know the resolution, use the Displays panel in Settings.
00:02.0 VGA compatible controller: Intel Corporation 82Q33 Express Integrated Graphics Controller (rev 02) The monitor is an Acer V193 19" 1440 x 900 (8:5) "Compatible with Vista".
According to settings, I am getting 640 x 480. According to ps -e , Xorg is running and Xwayland is not.
How do I fix the resolution? 640 x 480 is bad enough on terminals. On web sites, it's a bit of a horror.
My recollection is that I had resolution problems with F33, but that they did not appear until after installing.
I think it strange that F35 could handle my monitor until asked to install.
Will need bed soon.
On 4/4/22 23:06, Michael Hennebry wrote:
On Mon, 4 Apr 2022, Samuel Sieb wrote:
What is your video device? Workstation uses Wayland by default, so the X info applications are not very useful, they will be getting info from the XWayland server. If you want to know the resolution, use the Displays panel in Settings.
00:02.0 VGA compatible controller: Intel Corporation 82Q33 Express Integrated Graphics Controller (rev 02) The monitor is an Acer V193 19" 1440 x 900 (8:5) "Compatible with Vista".
According to settings, I am getting 640 x 480. According to ps -e , Xorg is running and Xwayland is not.
How do I fix the resolution? 640 x 480 is bad enough on terminals. On web sites, it's a bit of a horror.
My recollection is that I had resolution problems with F33, but that they did not appear until after installing.
I think it strange that F35 could handle my monitor until asked to install.
Run "cat /proc/cmdline". Is there a "nomodeset" option in there?
Install "monitor-edid" and run it. See if it sees the correct monitor resolutions.
On Tue, 5 Apr 2022, Samuel Sieb wrote:
On 4/4/22 23:06, Michael Hennebry wrote:
00:02.0 VGA compatible controller: Intel Corporation 82Q33 Express Integrated Graphics Controller (rev 02) The monitor is an Acer V193 19" 1440 x 900 (8:5) "Compatible with Vista".
According to settings, I am getting 640 x 480. According to ps -e , Xorg is running and Xwayland is not.
How do I fix the resolution? 640 x 480 is bad enough on terminals. On web sites, it's a bit of a horror.
My recollection is that I had resolution problems with F33, but that they did not appear until after installing.
I think it strange that F35 could handle my monitor until asked to install.
Run "cat /proc/cmdline". Is there a "nomodeset" option in there?
Install "monitor-edid" and run it. See if it sees the correct monitor resolutions.
omplete! $ monitor-edid you must be root to run this program $ sudo monitor-edid mmap /dev/mem: Permission denied $ sudo sh sh-5.1# whoami root sh-5.1# monitor-edid mmap /dev/mem: Permission denied sh-5.1# ls -l /dev/mem crw-r-----. 1 root kmem 1, 1 Apr 5 02:58 /dev/mem sh-5.1#
Had it worked, would the screen have changed instantly?
On Tue, 5 Apr 2022, Michael Hennebry wrote:
On Tue, 5 Apr 2022, Samuel Sieb wrote:
Run "cat /proc/cmdline". Is there a "nomodeset" option in there?
Install "monitor-edid" and run it. See if it sees the correct monitor resolutions.
omplete! $ monitor-edid you must be root to run this program $ sudo monitor-edid mmap /dev/mem: Permission denied $ sudo sh sh-5.1# whoami root sh-5.1# monitor-edid mmap /dev/mem: Permission denied sh-5.1# ls -l /dev/mem crw-r-----. 1 root kmem 1, 1 Apr 5 02:58 /dev/mem sh-5.1#
Had it worked, would the screen have changed instantly?
Rebooting without nomodeset did the trick. How do I make that permanent? Any idea why I got a permission denied error?
Now I just need to move /var and /home to partitions.
On Tue, 5 Apr 2022, Michael Hennebry wrote:
On Tue, 5 Apr 2022, Michael Hennebry wrote:
On Tue, 5 Apr 2022, Samuel Sieb wrote:
Run "cat /proc/cmdline". Is there a "nomodeset" option in there?
Install "monitor-edid" and run it. See if it sees the correct monitor resolutions.
omplete! $ monitor-edid you must be root to run this program $ sudo monitor-edid mmap /dev/mem: Permission denied $ sudo sh sh-5.1# whoami root sh-5.1# monitor-edid mmap /dev/mem: Permission denied sh-5.1# ls -l /dev/mem crw-r-----. 1 root kmem 1, 1 Apr 5 02:58 /dev/mem sh-5.1#
Had it worked, would the screen have changed instantly?
Rebooting without nomodeset did the trick. How do I make that permanent? Any idea why I got a permission denied error?
Now I just need to move /var and /home to partitions.
'Tis done. It seems to work, but gnome's activities mechanism is jerky. Also 'twould be nice to not have to remove nomodeset by hand each time. What file do I edit to make it permanant?
BTW getting rid of nomodeset also worked for the basic graphics mode of the installer. Had I known that, I could have saved myself a lot of trouble.
Thanks much. My recollection is that I had a much harder time installing F33.
On Tue, 5 Apr 2022 14:12:09 -0500 (CDT) Michael Hennebry hennebry@web.cs.ndsu.nodak.edu wrote:
Had it worked, would the screen have changed instantly?
Rebooting without nomodeset did the trick. How do I make that permanent? Any idea why I got a permission denied error?
Now I just need to move /var and /home to partitions.
'Tis done. It seems to work, but gnome's activities mechanism is jerky. Also 'twould be nice to not have to remove nomodeset by hand each time. What file do I edit to make it permanant?
/etc/default/grub
BR, Bob
On 4/5/22 12:58, Bob Marcan wrote:
On Tue, 5 Apr 2022 14:12:09 -0500 (CDT) Michael Hennebry hennebry@web.cs.ndsu.nodak.edu wrote:
Had it worked, would the screen have changed instantly?
Rebooting without nomodeset did the trick. How do I make that permanent? Any idea why I got a permission denied error?
Now I just need to move /var and /home to partitions.
'Tis done. It seems to work, but gnome's activities mechanism is jerky. Also 'twould be nice to not have to remove nomodeset by hand each time. What file do I edit to make it permanant?
/etc/default/grub
You need to edit that, but that's not enough. You need to also either edit the /boot/grub2/grub.cfg to change the "kernelopts" line or run "grub2-mkconfig -o /boot/grub2/grub.cfg" to update the file.
On Tue, 5 Apr 2022 14:20:20 -0700 Samuel Sieb samuel@sieb.net wrote:
Also 'twould be nice to not have to remove nomodeset by hand each time. What file do I edit to make it permanant?
/etc/default/grub
You need to edit that, but that's not enough. You need to also either edit the /boot/grub2/grub.cfg to change the "kernelopts" line or run "grub2-mkconfig -o /boot/grub2/grub.cfg" to update the file.
According to the few first lines in the /boot/grub2/grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub2-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ... "grub2-mkconfig -o /boot/grub2/grub.cfg" is the proper way.
On Tue, 5 Apr 2022, Bob Marcan wrote:
According to the few first lines in the /boot/grub2/grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub2-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ... "grub2-mkconfig -o /boot/grub2/grub.cfg" is the proper way.
Done, but not yet tested.
On 4/5/22 08:51, Michael Hennebry wrote:
On Tue, 5 Apr 2022, Samuel Sieb wrote:
Install "monitor-edid" and run it. See if it sees the correct monitor resolutions.
$ monitor-edid you must be root to run this program
That is strange. It worked for me as a user.
$ sudo monitor-edid mmap /dev/mem: Permission denied $ sudo sh sh-5.1# whoami root sh-5.1# monitor-edid mmap /dev/mem: Permission denied sh-5.1# ls -l /dev/mem crw-r-----. 1 root kmem 1, 1 Apr 5 02:58 /dev/mem sh-5.1#
I wonder if it's because you have secure boot enabled.
Had it worked, would the screen have changed instantly?
No, that just lists the available modes of the monitor. I was trying to check if the EDID was working properly.
Another way that might work with secure boot enabled is to use "decode-edid" instead. Install it, then run "find /sys -name edid". On my system, that gives me: /sys/devices/pci0000:00/0000:00:08.1/0000:05:00.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci0000:00/0000:00:08.1/0000:05:00.0/drm/card0/card0-HDMI-A-2/edid /sys/devices/pci0000:00/0000:00:08.1/0000:05:00.0/drm/card0/card0-DP-1/edid
My monitor is connected to "HDMI-A-2". If you don't know which one, then just cat each one until you get a bunch of garbage on the terminal. Then run the following, but replace with the right path.
edid-decode < /sys/devices/pci0000:00/0000:00:08.1/0000:05:00.0/drm/card0/card0-HDMI-A-2/edid
On Tue, 5 Apr 2022, Samuel Sieb wrote:
On 4/5/22 08:51, Michael Hennebry wrote:
On Tue, 5 Apr 2022, Samuel Sieb wrote:
Install "monitor-edid" and run it. See if it sees the correct monitor resolutions.
$ monitor-edid you must be root to run this program
That is strange. It worked for me as a user.
$ sudo monitor-edid mmap /dev/mem: Permission denied $ sudo sh sh-5.1# whoami root sh-5.1# monitor-edid mmap /dev/mem: Permission denied sh-5.1# ls -l /dev/mem crw-r-----. 1 root kmem 1, 1 Apr 5 02:58 /dev/mem sh-5.1#
I wonder if it's because you have secure boot enabled.
I think my machine predates secure boot. It's an HP Compaq dc5800 . Is there a way to ask it?
Had it worked, would the screen have changed instantly?
No, that just lists the available modes of the monitor. I was trying to check if the EDID was working properly.
Another way that might work with secure boot enabled is to use "decode-edid" instead. Install it, then run "find /sys -name edid". On my system, that gives me: /sys/devices/pci0000:00/0000:00:08.1/0000:05:00.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci0000:00/0000:00:08.1/0000:05:00.0/drm/card0/card0-HDMI-A-2/edid /sys/devices/pci0000:00/0000:00:08.1/0000:05:00.0/drm/card0/card0-DP-1/edid
My monitor is connected to "HDMI-A-2". If you don't know which one, then just cat each one until you get a bunch of garbage on the terminal. Then run the following, but replace with the right path.
edid-decode < /sys/devices/pci0000:00/0000:00:08.1/0000:05:00.0/drm/card0/card0-HDMI-A-2/edid
I'll get to it. At the moment, I'm distracted by other things: an unmet need for food and drink, a horde of dnf -y installs of F35 versions of my F33 packages and a black window that appears when I try to use gvim.
Any suggestions regarding that last?
On 4/5/22 14:40, Michael Hennebry wrote:
On Tue, 5 Apr 2022, Samuel Sieb wrote:
On 4/5/22 08:51, Michael Hennebry wrote:
On Tue, 5 Apr 2022, Samuel Sieb wrote:
Install "monitor-edid" and run it. See if it sees the correct monitor resolutions.
$ monitor-edid you must be root to run this program
That is strange. It worked for me as a user.
$ sudo monitor-edid mmap /dev/mem: Permission denied $ sudo sh sh-5.1# whoami root sh-5.1# monitor-edid mmap /dev/mem: Permission denied sh-5.1# ls -l /dev/mem crw-r-----. 1 root kmem 1, 1 Apr 5 02:58 /dev/mem sh-5.1#
I wonder if it's because you have secure boot enabled.
I think my machine predates secure boot. It's an HP Compaq dc5800 . Is there a way to ask it?
mokutil --sb-state But if you aren't using EFI, then you won't have secure boot. I wonder why it wouldn't run for you.
a black window that appears when I try to use gvim.
Any suggestions regarding that last?
What does "echo $XDG_SESSION_TYPE" show? I'm using wayland and it works fine and I can't imagine it would work less on X.
On Tue, 5 Apr 2022, Samuel Sieb wrote:
On 4/5/22 14:40, Michael Hennebry wrote:
a black window that appears when I try to use gvim.
Any suggestions regarding that last?
What does "echo $XDG_SESSION_TYPE" show? I'm using wayland and it works fine and I can't imagine it would work less on X.
On F33, I think I had X. [hennebry@localhost-live ~]$ echo $XDG_SESSION_TYPE wayland [hennebry@localhost-live ~]$
How do I tell F35 to use X?
I'm also getting weird behavior from the video player. It'll claim unable to play for want of a MPEG4-4 AAC decoder. From cancel/find in software , I pick cancel. I can then play the video.
On 4/5/22 18:58, Michael Hennebry wrote:
On Tue, 5 Apr 2022, Samuel Sieb wrote:
On 4/5/22 14:40, Michael Hennebry wrote:
a black window that appears when I try to use gvim.
Any suggestions regarding that last?
What does "echo $XDG_SESSION_TYPE" show? I'm using wayland and it works fine and I can't imagine it would work less on X.
On F33, I think I had X. [hennebry@localhost-live ~]$ echo $XDG_SESSION_TYPE wayland [hennebry@localhost-live ~]$
How do I tell F35 to use X?
Assuming you're not actually on the live boot, when you are at the login screen, click on your user. Then before you enter your password, there should be a gear icon somewhere. Click on it and choose a different session. It should be pretty clear. One might say wayland or one might say Xorg. Either choose the X(org) one or the one that isn't wayland.
On Tue, 5 Apr 2022, Samuel Sieb wrote:
On 4/5/22 18:58, Michael Hennebry wrote:
How do I tell F35 to use X?
Assuming you're not actually on the live boot, when you are at the login screen, click on your user. Then before you enter your password, there should be a gear icon somewhere. Click on it and choose a different session. It should be pretty clear. One might say wayland or one might say Xorg. Either choose the X(org) one or the one that isn't wayland.
Thanks again. The options were Gnome, Gnome Classic and Gnome with Xorg. I picked the last. gvim works now.
On Mon, 4 Apr 2022, Samuel Sieb wrote:
On 4/3/22 23:10, Michael Hennebry wrote:
The shadow password file on partition 3 is full of empty passwords.
They aren't empty, they are disabled. You can't login to those accounts with a password.
Not :*:, :: . That said, I'll try it.
On 4/4/22 07:53, Michael Hennebry wrote:
On Mon, 4 Apr 2022, Samuel Sieb wrote:
On 4/3/22 23:10, Michael Hennebry wrote:
The shadow password file on partition 3 is full of empty passwords.
They aren't empty, they are disabled. You can't login to those accounts with a password.
Not :*:, :: . That said, I'll try it.
Are you sure? All of mine have either * or !! for the password. Being empty would be really bad.
nobody:*:18656:0:99999:7::: dbus:!!:18903::::::
-
Bob Marcan -
Eddie O'Connor -
Joe Zeff -
Michael Hennebry -
Samuel Sieb -
Tim