Re: What is Castor ? Att.Jonathan Billings.

2024-05-12 Thread Ger van Dijck 
Op Sat, 04 May 2024 18:27:48 +0200 schreef Roger Heflin  
:



castor is someplace on your machine defined as the linux node's hostname.

dhcp-client does deliver the defined hostname in the dhcp
requests/responses to the router when it asks for the IP address.

What does 'hostname' report?   and 'hostnamectl' report as the hostname?

Hostname gives castor and hostnamectl gives castor static and a lot of  
information like bios version , type laptop , OS version etc. etc.


On Sat, May 4, 2024 at 10:17 AM Ger van Dijck   
wrote:


Hi,


A bit late Jonathan but here is my answer.


After upgrade to Fedora 40 all runs perfect , but the login prompt looks
as follows :


[root@castor GervanDijck] #


Suddenly the router a Fritz-Box 7490 detects the Name Castor with
IP192.168.178.29 (not connectebel) with a MAC number and the connection
is WLAN.


I just do not understand it : What does it represent ?




Ger van Dijck.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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, report it:  
https://pagure.io/fedora-infrastructure/new_issue

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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, report it:  
https://pagure.io/fedora-infrastructure/new_issue



--
Gemaakt met Opera's e-mailprogramma: http://www.opera.com/mail/
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: What is Castor ? Att.Jonathan Billings.

2024-05-11 Thread Robert McBroom via users 

On 5/11/24 08:36, John Pilkington wrote:

On 10/05/2024 15:51, John Pilkington wrote:

On 10/05/2024 15:00, George N. White III wrote:
On Wed, May 8, 2024 at 5:13 PM John Pilkington 
mailto:johnpilk...@gmail.com>> wrote:


    On 08/05/2024 20:13, Samuel Sieb wrote:
 > On 5/8/24 10:50 AM, John Pilkington wrote:
 >> 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:
 >
 > Nouveau is included with the kernel, it doesn't have its own 
package.


    xorg-x11-drv-nouveau is supplied by fedora, but I was told that the
    kernel driver was more up to date, so I removed the fformer.


I have a late 2012 iMac with Nvidia that was using 470xx.  I mostly 
use nouveau

with wayland, but do have xorg-x11-drv-nouveau.

There were issues with 470xx failing to build in F40 with the akmods 
install from
rpmfusion, but now there is a testing version that does install.  
Some users have
success with the Nvidia installer. I have the rpmfusion-testing 
package installed

but haven't had time to test it.  I don't think it supports Wayland.



Thanks for your comment.  I posted later, in this thread but with a 
subject-line change. It does show in HyperKitty and I've put a link 
to it on the rpmfusion list.


I have just updated that, re the dual-boot box.  See below:

I have removed all nouveau packages and installed all *470xx" 
packages, which installed the new versions.  That gave HDMI and vga 
screens with their expected resolutions but essentially no user 
interactivity because active kwin_wayland runs all cpus at full 
throttle. Perhaps that's 'not supported'.


Ctrl/Alt/F3 still works, and I have 6.8.9 now.  That complained that 
there was "no space on /boot/efi/EFI/Linux/Fedora " (200 MB) but 
seems to run (with the same cpu runaway) after I deleted several f39 
files.


I hope this doesn't offend any 'religious' beliefs.  Installing

plasma-workspace-x11

(in the updates repo but NOT supported by the Fedora KDE SIG)

and selecting "Desktop Session: Plasma (X11)" in the login screen, has 
apparently restored this system to a usable state.  At present 
password entry still has a sluggish keyboard.



The single-boot box is still running nouveau.


Same experience here with a gt710. Mouse action in wayland is very 
hesitant. Still on X11.


--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: What is Castor ? Att.Jonathan Billings.

2024-05-11 Thread John Pilkington 

On 10/05/2024 15:51, John Pilkington wrote:

On 10/05/2024 15:00, George N. White III wrote:
On Wed, May 8, 2024 at 5:13 PM John Pilkington > wrote:


    On 08/05/2024 20:13, Samuel Sieb wrote:
 > On 5/8/24 10:50 AM, John Pilkington wrote:
 >> 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:
 >
 > Nouveau is included with the kernel, it doesn't have its own 
package.


    xorg-x11-drv-nouveau is supplied by fedora, but I was told that the
    kernel driver was more up to date, so I removed the fformer.


I have a late 2012 iMac with Nvidia that was using 470xx.  I mostly 
use nouveau

with wayland, but do have xorg-x11-drv-nouveau.

There were issues with 470xx failing to build in F40 with the akmods 
install from
rpmfusion, but now there is a testing version that does install.  Some 
users have
success with the Nvidia installer. I have the rpmfusion-testing 
package installed

but haven't had time to test it.  I don't think it supports Wayland.



Thanks for your comment.  I posted later, in this thread but with a 
subject-line change. It does show in HyperKitty and I've put a link to 
it on the rpmfusion list.


I have just updated that, re the dual-boot box.  See below:

I have removed all nouveau packages and installed all *470xx" packages, 
which installed the new versions.  That gave HDMI and vga screens with 
their expected resolutions but essentially no user interactivity because 
active kwin_wayland runs all cpus at full throttle. Perhaps that's 'not 
supported'.


Ctrl/Alt/F3 still works, and I have 6.8.9 now.  That complained that 
there was "no space on /boot/efi/EFI/Linux/Fedora " (200 MB) but seems 
to run (with the same cpu runaway) after I deleted several f39 files.


I hope this doesn't offend any 'religious' beliefs.  Installing

plasma-workspace-x11

(in the updates repo but NOT supported by the Fedora KDE SIG)

and selecting "Desktop Session: Plasma (X11)" in the login screen, has 
apparently restored this system to a usable state.  At present password 
entry still has a sluggish keyboard.



The single-boot box is still running nouveau.



Cheers,

John


--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: What is Castor ? Att.Jonathan Billings.

2024-05-10 Thread John Pilkington 

On 10/05/2024 15:00, George N. White III wrote:
On Wed, May 8, 2024 at 5:13 PM John Pilkington > wrote:


On 08/05/2024 20:13, Samuel Sieb wrote:
 > On 5/8/24 10:50 AM, John Pilkington wrote:
 >> 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:
 >
 > Nouveau is included with the kernel, it doesn't have its own package.

xorg-x11-drv-nouveau is supplied by fedora, but I was told that the
kernel driver was more up to date, so I removed the fformer.


I have a late 2012 iMac with Nvidia that was using 470xx.  I mostly use 
nouveau

with wayland, but do have xorg-x11-drv-nouveau.

There were issues with 470xx failing to build in F40 with the akmods 
install from
rpmfusion, but now there is a testing version that does install.  Some 
users have
success with the Nvidia installer. I have the rpmfusion-testing package 
installed

but haven't had time to test it.  I don't think it supports Wayland.



Thanks for your comment.  I posted later, in this thread but with a 
subject-line change. It does show in HyperKitty and I've put a link to 
it on the rpmfusion list.


I have removed all nouveau packages and installed all *470xx" packages, 
which installed the new versions.  That gave HDMI and vga screens with 
their expected resolutions but essentially no user interactivity because 
active kwin_wayland runs all cpus at full throttle. Perhaps that's 'not 
supported'.


Ctrl/Alt/F3 still works, and I have 6.8.9 now.  That complained that 
there was "no space on /boot/efi/EFI/Linux/Fedora " (200 MB) but seems 
to run (with the same cpu runaway) after I deleted several f39 files.


The single-boot box is still running nouveau.

Cheers,

John
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: What is Castor ? Att.Jonathan Billings.

2024-05-10 Thread George N. White III 
On Wed, May 8, 2024 at 5:13 PM John Pilkington 
wrote:

> On 08/05/2024 20:13, Samuel Sieb wrote:
> > On 5/8/24 10:50 AM, John Pilkington wrote:
> >> 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:
> >
> > Nouveau is included with the kernel, it doesn't have its own package.
>
> xorg-x11-drv-nouveau is supplied by fedora, but I was told that the
> kernel driver was more up to date, so I removed the fformer.
>

I have a late 2012 iMac with Nvidia that was using 470xx.  I mostly use
nouveau
with wayland, but do have xorg-x11-drv-nouveau.

There were issues with 470xx failing to build in F40 with the akmods
install from
rpmfusion, but now there is a testing version that does install.  Some
users have
success with the Nvidia installer. I have the rpmfusion-testing package
installed
but haven't had time to test it.  I don't think it supports Wayland.

-- 
George N. White III
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

F40 dual-boot problem, was Re: What is Castor ? Att.Jonathan Billings.

2024-05-09 Thread John Pilkington 

On 08/05/2024 21:57, Samuel Sieb wrote:

On 5/8/24 1:13 PM, John Pilkington wrote:

On 08/05/2024 20:13, Samuel Sieb wrote:

On 5/8/24 10:50 AM, John Pilkington wrote:
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:


Nouveau is included with the kernel, it doesn't have its own package.


xorg-x11-drv-nouveau is supplied by fedora, but I was told that the 
kernel driver was more up to date, so I removed the fformer.


xorg-x11-drv-nouveau is the xorg driver that uses (and requires) the 
kernel driver.  You need both.


llvmpipe means it's using software 3D rendering because it doesn't 
have a 3d hardware driver.


I don't think I want 3D


KDE/wayland uses 3D rendering.


   API: Vulkan v: 1.3.280 drivers: N/A surfaces: xcb,xlib,wayland


$ sudo dmesg | less

[    0.00] 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


There are a lot of duplicates in that list.  If you include 
"nomodeset", then you'll be using the lowest common factor display 
options.  Is there a reason you don't want to use the rpmfusion 
drivers?  It appears that nouveau isn't working for your system, or 
else something is mixed up. You could check the logs for a previous 
boot that didn't work.


I have happily used the rpmfusion builds of 470xx until a few weeks 
ago; but it was said that wayland support was missing, and for some 
time akmods failed to build anyway.  I hoped to be able to use the 
reverse-engineered FOSS drivers.  And a few days ago, after reverting 
to 470xx, kwin_wayland appeared to be running 4 cpu cores at 90% and 
the mouse was unusable.


As far as I know, the NVidia drivers have had Wayland support for a long 
time.  That CPU usage is likely if you're using software 3D rendering. 
You need to sort out what you have installed.


On the linux-only box I have nvidia-gpu-firmware installed.  It may 
not be loading (MythTV says vdpau isn't available) but that system 
currently does the jobs that I want.


My apologies, by the way, for what looks like a hijack.


Yes, you definitely should have started a new thread.


but it seems better to continue here.

On the dual-boot box I have done

"sudo dnf remove *nouveau*", which removed nouveau-firmware and 
xorg-x11-drv-nouveau


"sudo dnf install *470xx*", which pulled in the rpmfusion builds of the 
legacy nvidia driver and updated the kernel command line.  Wayland 
support has been said to start at series 490, which is why I had been 
looking at nouveau.


"sudo dnf upgrade" because things are moving quickly at present.

Now booting goes as expected, giving two screens at their expected 
resolution *BUT* the cursor movement is jerky, keyboard response is very 
slow, and "atop" shows 4 3GHz cores at 99%, for kwin_wayland. 
Ctrl/Alt/F3 is the only way to make progress.


Throughout this saga there have been fleeting complaints about the abrtd 
service.  It's the only one that "systemctl" lists in red.


Ctrl/Alt/F1 says the abrtd.service failed to start and lists Dependency 
issues for four abrtd services.  I haven't investigated more.


In some ways this is progress, but the system is less usable than the 
800x600 nouveau-only form.


{{{

$ inxi -GA

Graphics:
  Device-1: NVIDIA GK208B [GeForce GT 710] driver: nvidia v: 470.239.06
  Device-2: Chicony HP 720p HD Monitor Webcam driver: 
snd-usb-audio,uvcvideo type: USB
  Display: server: X.org v: 1.20.14 with: Xwayland v: 23.2.6 driver: X: 
loaded: nvidia
unloaded: fbdev,modesetting,nouveau,vesa gpu: 
nvidia,nvidia-nvswitch tty: 100x37 resolution:

1: 1360x768 2: 1920x1080
  API: EGL v: 1.5 drivers: kms_swrast,nvidia,swrast platforms: 
gbm,wayland,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: mesa v: 24.0.6 note: 
console (EGL sourced)
renderer: llvmpipe (LLVM 18.1.1 256 bits), NVIDIA GeForce GT 
710/PCIe/SSE2

  API: Vulkan v: 1.3.280 drivers: N/A surfaces: wayland
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio 
driver: snd_hda_intel

  Device-2: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel
  Device-3: Chicony HP 720p HD Monitor Webcam driver: 
snd-usb-audio,uvcvideo type: USB
  Device-4: C-Media USB PnP Sound Device driver: 
hid-generic,snd-usb-audio,usbhid type: USB

  API: ALSA v: k6.8.8-300.fc40.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.5 status: active

}}}
--
___
users mailing list --

Re: What is Castor ? Att.Jonathan Billings.

2024-05-08 Thread Samuel Sieb 

On 5/8/24 1:13 PM, John Pilkington wrote:

On 08/05/2024 20:13, Samuel Sieb wrote:

On 5/8/24 10:50 AM, John Pilkington wrote:
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:


Nouveau is included with the kernel, it doesn't have its own package.


xorg-x11-drv-nouveau is supplied by fedora, but I was told that the 
kernel driver was more up to date, so I removed the fformer.


xorg-x11-drv-nouveau is the xorg driver that uses (and requires) the 
kernel driver.  You need both.


llvmpipe means it's using software 3D rendering because it doesn't 
have a 3d hardware driver.


I don't think I want 3D


KDE/wayland uses 3D rendering.


   API: Vulkan v: 1.3.280 drivers: N/A surfaces: xcb,xlib,wayland


$ sudo dmesg | less

[    0.00] 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


There are a lot of duplicates in that list.  If you include 
"nomodeset", then you'll be using the lowest common factor display 
options.  Is there a reason you don't want to use the rpmfusion 
drivers?  It appears that nouveau isn't working for your system, or 
else something is mixed up. You could check the logs for a previous 
boot that didn't work.


I have happily used the rpmfusion builds of 470xx until a few weeks ago; 
but it was said that wayland support was missing, and for some time 
akmods failed to build anyway.  I hoped to be able to use the 
reverse-engineered FOSS drivers.  And a few days ago, after reverting to 
470xx, kwin_wayland appeared to be running 4 cpu cores at 90% and the 
mouse was unusable.


As far as I know, the NVidia drivers have had Wayland support for a long 
time.  That CPU usage is likely if you're using software 3D rendering. 
You need to sort out what you have installed.


On the linux-only box I have nvidia-gpu-firmware installed.  It may not 
be loading (MythTV says vdpau isn't available) but that system currently 
does the jobs that I want.


My apologies, by the way, for what looks like a hijack.


Yes, you definitely should have started a new thread.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: What is Castor ? Att.Jonathan Billings.

2024-05-08 Thread John Pilkington 

On 08/05/2024 20:13, Samuel Sieb wrote:

On 5/8/24 10:50 AM, John Pilkington wrote:
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:


Nouveau is included with the kernel, it doesn't have its own package.


xorg-x11-drv-nouveau is supplied by fedora, but I was told that the 
kernel driver was more up to date, so I removed the fformer.



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


This is the xorg nvidia drive, but I assume it's not working if the 
kernel driver isn't loaded.


 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)


llvmpipe means it's using software 3D rendering because it doesn't have 
a 3d hardware driver.


I don't think I want 3D



   API: Vulkan v: 1.3.280 drivers: N/A surfaces: xcb,xlib,wayland


$ sudo dmesg | less

[    0.00] 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


There are a lot of duplicates in that list.  If you include "nomodeset", 
then you'll be using the lowest common factor display options.  Is there 
a reason you don't want to use the rpmfusion drivers?  It appears that 
nouveau isn't working for your system, or else something is mixed up. 
You could check the logs for a previous boot that didn't work.



I have happily used the rpmfusion builds of 470xx until a few weeks ago; 
but it was said that wayland support was missing, and for some time 
akmods failed to build anyway.  I hoped to be able to use the 
reverse-engineered FOSS drivers.  And a few days ago, after reverting to 
470xx, kwin_wayland appeared to be running 4 cpu cores at 90% and the 
mouse was unusable.


On the linux-only box I have nvidia-gpu-firmware installed.  It may not 
be loading (MythTV says vdpau isn't available) but that system 
currently does the jobs that I want.


My apologies, by the way, for what looks like a hijack.

John
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: What is Castor ? Att.Jonathan Billings.

2024-05-08 Thread Samuel Sieb 

On 5/8/24 10:50 AM, John Pilkington wrote:
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:


Nouveau is included with the kernel, it doesn't have its own package.


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


This is the xorg nvidia drive, but I assume it's not working if the 
kernel driver isn't loaded.



     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)


llvmpipe means it's using software 3D rendering because it doesn't have 
a 3d hardware driver.



   API: Vulkan v: 1.3.280 drivers: N/A surfaces: xcb,xlib,wayland


$ sudo dmesg | less

[    0.00] 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


There are a lot of duplicates in that list.  If you include "nomodeset", 
then you'll be using the lowest common factor display options.  Is there 
a reason you don't want to use the rpmfusion drivers?  It appears that 
nouveau isn't working for your system, or else something is mixed up. 
You could check the logs for a previous boot that didn't work.

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: What is Castor ? Att.Jonathan Billings.

2024-05-08 Thread John Pilkington 

On 08/05/2024 17:54, Roger Heflin wrote:

On Wed, May 8, 2024 at 5:09 AM John Pilkington  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.00] 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@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: What is Castor ? Att.Jonathan Billings.

2024-05-08 Thread Roger Heflin 
On Wed, May 8, 2024 at 5:09 AM John Pilkington  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?
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: What is Castor ? Att.Jonathan Billings.

2024-05-08 Thread Tim via users 
On Wed, 2024-05-08 at 11:08 +0100, John Pilkington wrote:
> 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?

I wouldn't have thought so (re DNS, IPs, & DHCP).  Video output (other
than networked KVM kind of things) is direct hardware to monitor, no
network should be involved.  I don't recall you mentioning KVM, though
could have forgotten.  Normally, screen set up is long before
networking starts.

Manual modesetting overrides the OS automatically picking a graphics
mode, to some degree.  Normally a monitor identifies itself, and the
graphics system works out a list of compatible modes that the monitor
and the graphics card can both use, and picks the highest resolution
possible with the fastest refresh rate.

If you have a monitor that doesn't identify itself, or doesn't do it
properly (and some don't), or your graphic card is just as bad at it,
than manual overrides is the way to go.  I seem to remember it was Tom
Horsley who had a website page detailing his battles with such things.

Hardware KVMs can have the same problems with display ID data, they may
have a broken implementation of it.  Or only support one mode.  Or,
alternatively, they could be a solution, forcing a mode that works for
you.

If you simply prefer a different graphics mode (different scan/refresh
rates, different resolutions), then that should be possible to select
after you've booted up with the display settings.  800 by 600 is a bit
nasty.  While it may produce a screen size that some people want, many
GUIs expect bigger screen dimensions and don't fit, or you're left with
a looking-through-a-keyhole view of them.

This EDID info is sent over different wires (DDC) in the video
connector than the picture signal.  It is possible to have broken pins
in the plugs or sockets, or wiring in the cable, that stops this info.
If the cable can be completely unplugged from monitor *and* PC, it may
be worth trying another.  And sometimes a clean toothbrush scrub of the
connector contacts fixes problems up.
 
-- 
 
NB:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the list.
 
The following system info data is generated fresh for each post:
 
uname -rsvp
Linux 6.2.15-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 11 16:51:53
UTC 2023 x86_64
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: What is Castor ? Att.Jonathan Billings.

2024-05-08 Thread John Pilkington 

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



--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: What is Castor ? Att.Jonathan Billings.

2024-05-08 Thread Tim via users 
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.

-- 
 
uname -rsvp
Linux 3.10.0-1160.114.2.el7.x86_64 #1 SMP Wed Mar 20 15:54:52 UTC 2024 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: What is Castor ? Att.Jonathan Billings.

2024-05-07 Thread Jonathan Billings 
On May 4, 2024, at 12:28, Roger Heflin  wrote:
> 
> castor is someplace on your machine defined as the linux node's hostname.
> 
> dhcp-client does deliver the defined hostname in the dhcp
> requests/responses to the router when it asks for the IP address.
> 
> What does 'hostname' report?   and 'hostnamectl' report as the hostname?

This is the correct answer. “Castor” is your systems host name.

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 never encountered one of these devices, but I’ve heard of windows systems 
and even phones can do this.

Set your preferred hostname either in GNOME Settings (or whatever DE’s 
settings) or with hostnamectl.

-- 
Jonathan Billings
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: What is Castor ? Att.Jonathan Billings.

2024-05-04 Thread Roger Heflin 
castor is someplace on your machine defined as the linux node's hostname.

dhcp-client does deliver the defined hostname in the dhcp
requests/responses to the router when it asks for the IP address.

What does 'hostname' report?   and 'hostnamectl' report as the hostname?

On Sat, May 4, 2024 at 10:17 AM Ger van Dijck  wrote:
>
> Hi,
>
>
> A bit late Jonathan but here is my answer.
>
>
> After upgrade to Fedora 40 all runs perfect , but the login prompt looks
> as follows :
>
>
> [root@castor GervanDijck] #
>
>
> Suddenly the router a Fritz-Box 7490 detects the Name Castor with
> IP192.168.178.29 (not connectebel) with a MAC number and the connection
> is WLAN.
>
>
> I just do not understand it : What does it represent ?
>
>
>
>
> Ger van Dijck.
> --
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@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, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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, report it: 
https://pagure.io/fedora-infrastructure/new_issue