On 08/05/2024 17:54, Roger Heflin wrote:
On Wed, May 8, 2024 at 5:09 AM John Pilkington <johnpilk222@xxxxxxxxx> wrote:
On 08/05/2024 10:18, Tim via users wrote:
On Tue, 2024-05-07 at 17:36 -0400, Jonathan Billings wrote:
Some home router/gateways will remember the hostname a system used as
part of their network, and when handing out the same IP to a new
host, re-uses the saved hostname.
I've yet to come across a home gateway that handles name resolution,
they just dole out numerical IPs from their DHCP server, it also seems
to be a bit of a rarity for a client to accept a hostname that a DHCP
server does supply (if it does). DHCP clients can also request the
DHCP server lets them use their own hostname, and that's often ignored,
too.
More often than not, a client would to a reverse DNS look-up on its
assigned IP to see what domain/hostname is associated with that IP
(which could be a DNS query, but first it looks in the hosts file).
Not everyone has a DNS server, or a configurable one, nor adjusts their
hosts file (often fighting with Network Mangler over it). So:
Set your preferred hostname either in GNOME Settings (or whatever
DE’s settings) or with hostnamectl.
Which stores a setting somewhere naming itself consistently, whatever
IP address you get given.
This can get messy if you get assigned different numerical IPs from
time to time.
It occurs to me that my new 'dual-boot' problems with F40 KDE might be
related to this, but I'm not clear how I could test it. I've posted
both here and on the kde list.
I have two screen-devices, HDMI tv and vga monitor. By default booting
is to Windows, but 'escape' early on goes to an HP-provided
boot-selection sequence and grub.
Choosing "modesetting" starts booting with both screens active, but
freezes shortly after a cursor appears.
"nomodeset" gives a usable system, but with the vga screen never active
and final HDMI resolution fixed at 800x600.
Could this perhaps be a conflict of hostnames set at power-on and by Fedora?
John P
No.
Whatever the hostname is it really does not matter for booting or not.
The fact that nomodeset works tells me that the graphics driver in the
kernel is unable to handle your card and/or monitors in some critical
way.
What kind of vga/video card do you have?
Thanks, Tim and Roger, for both these replies.
The harware was working well, before my recent upgrades from f38,
briefly to f39 and now to f40. Then I was using the rpmfusion 470xx
builds of the nvidia legacy drivers. Now the dual-boot box has no
nvidia or nouveau rpms installed (rpm -qa) although I suppose bits of
config might remain; inxi still finds nvidia traces:
{{{
ohn@FedWin4c1:~$ inxi -G
Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] driver: N/A
Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.6
compositor: kwin_wayland driver: X: loaded: nvidia
unloaded: fbdev,modesetting,nouveau,vesa gpu: N/A resolution: 800x600
API: EGL v: 1.5 drivers: kms_swrast,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.5 vendor: mesa v: 24.0.6 renderer: llvmpipe (LLVM 18.1.1
256 bits)
API: Vulkan v: 1.3.280 drivers: N/A surfaces: xcb,xlib,wayland
$ sudo dmesg | less
[ 0.000000] Command line:
BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.8.8-300.fc40.x86_64
root=/dev/mapper/fedora_localhost--live-root ro
rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset
resume=/dev/mapper/fedora_localhost--live-swap
rd.lvm.lv=fedora_localhost-live/root
rd.lvm.lv=fedora_localhost-live/swap rhgb quiet
rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset
Mose variations of this give a frozen system.
}}}
John
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue