Re: More boot questions

2020-06-16 Thread George N. White III
On Tue, 16 Jun 2020 at 02:08, Tim via users 
wrote:

> On Mon, 2020-06-15 at 17:56 +0100, Patrick O'Callaghan wrote:
> > My system disk is a Samsung EVO SSD (2TB) and I'm unaware of any
> > problems with it. Smartcontrol shows no errors.
>
> Likewise.  And I just bought a new 500 gig Samsung Evo 860  to install
> in a server.
>

Reports of problems using AMD hardware:
https://eu.community.samsung.com/t5/Computers-IT/860-EVO-250GB-causing-freezes-on-AMD-system/td-p/575813

 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI]
SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40)
Subsystem: Gigabyte Technology Co., Ltd SB7x0/SB8x0/SB9x0 SATA Controller
[AHCI mode]
Kernel driver in use: ahci
Kernel modules: ahci

I wrote to Samsung's EU support (samsungmem...@hanaro.eu) and they told me
to "use an Intel controller or SATA AHCI controller." to which I explained
that it's obvious that the controller in the AMD chipset is SATA AHCI.
After few more mails where I explained that it's not normal for the SSD to
act like that, they continued to blame the AMD SATA controller, I clearly
stated that I'm not going to buy new system just to get the SSD working
correctly and that the issue is in their SSD controller and not the AMD
SATA controller and it's up to them to fix it with firmware update. Well,
it's seems that it's not going to happen - they told me to return the SSD
back to the retailer or to send it to their service center in the
Netherlands



-- 
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


Re: How do I change the grub kernel boot parameters in F32 ?

2020-06-16 Thread Stephen Morris

On 16/6/20 9:06 am, Ed Greshko wrote:

On 2020-06-16 07:01, Tom H wrote:

The kernel options are in the BLS entries, so it doesn't matter what
you have in grubenv.

 From the grub2 changelog on may 13th:

Store cmdline in BLS snippets instead of using a grubenv variable

The kernel cmdline was stored as a kernelopts variable in the grubenv
file and the BLS snippets used that. But this turned out to be fragile
since the grubenv file could be removed or get corrupted easily.

To prevent the entries to not have a cmdline if the grubenv can't be
read, a fallback variable was set in the GRUB config file. But this
still caused issues since the config needs to be re-generated to change
the parameters.

Instead, let's store the cmdline in the BLS snippets. This will make
the configuration more robust, since it will work even without the
grubenv file and the BLS entries will contain all the information
needed to boot.

Thanks for that.

Just to complete my understanding, by the BLS snippets you mean the

/boot/loader/entries/*.conf

files?

Hi Ed,
    If

GRUB_ENABLE_BLSCFG=false is not going to be supported anymore, how does one 
disable BLS if we don't want it?

regards,
Steve

___
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


Re: How do I change the grub kernel boot parameters in F32 ?

2020-06-16 Thread Ed Greshko
On 2020-06-16 19:42, Stephen Morris wrote:
> If
>
> GRUB_ENABLE_BLSCFG=false is not going to be supported anymore, how does one 
> disable BLS if we don't want it? 

If that should happen then one needs to learn how to work with BLS.  Legacy 
methods aren't supported
forever.  Just like we don't have System V init scripts.

-- 
The key to getting good answers is to ask good questions.
___
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


systemctl status distccd

2020-06-16 Thread Michael J. Baars
Hi,

Since it's awfully quiet on the initscripts-devel mailing list.

Best regards,
Mischa.




distccd.service.d.tar.xz
Description: application/xz-compressed-tar
[root@tp02 ~]# systemctl status distccd
● distccd.service - Distccd A Distributed Compilation Server
 Loaded: loaded (/usr/lib/systemd/system/distccd.service; enabled; vendor 
preset: disabled)
 Active: failed (Result: exit-code) since Tue 2020-06-16 09:35:00 CEST; 
21min ago
Process: 741 ExecStart=/usr/bin/distccd --no-detach --daemon 
--whitelist=/etc/distcc/clients.allow $OPTIONS (code=exited, status=102)
   Main PID: 741 (code=exited, status=102)
CPU: 16ms

Jun 16 09:35:00 tp02.localdomain systemd[1]: Started Distccd A Distributed 
Compilation Server.
Jun 16 09:35:00 tp02.localdomain distccd[741]: (dcc_listen_by_addr) ERROR: bind 
of 192.168.0.2:3632 failed: Cannot assign requested address
Jun 16 09:35:00 tp02.localdomain systemd[1]: distccd.service: Main process 
exited, code=exited, status=102/n/a
Jun 16 09:35:00 tp02.localdomain systemd[1]: distccd.service: Failed with 
result 'exit-code'.

[root@tp02 mjbaars1977]# systemctl status distccd
● distccd.service - Distccd A Distributed Compilation Server
 Loaded: loaded (/usr/lib/systemd/system/distccd.service; enabled; vendor 
preset: disabled)
Drop-In: /etc/systemd/system/distccd.service.d
 └─distccd.service.conf
 Active: active (running) since Tue 2020-06-16 12:47:54 CEST; 46s ago
   Main PID: 945 (distccd)
  Tasks: 5 (limit: 4488)
 Memory: 1.7M
CPU: 20ms
 CGroup: /system.slice/distccd.service
 ├─ 945 /usr/bin/distccd --no-detach --daemon 
--whitelist=/etc/distcc/clients.allow --jobs 4 --listen 192.168.0.3 --allow 
192.168.0.0/4
 ├─ 952 /usr/bin/distccd --no-detach --daemon 
--whitelist=/etc/distcc/clients.allow --jobs 4 --listen 192.168.0.3 --allow 
192.168.0.0/4
 ├─ 994 /usr/bin/distccd --no-detach --daemon 
--whitelist=/etc/distcc/clients.allow --jobs 4 --listen 192.168.0.3 --allow 
192.168.0.0/4
 ├─1038 /usr/bin/distccd --no-detach --daemon 
--whitelist=/etc/distcc/clients.allow --jobs 4 --listen 192.168.0.3 --allow 
192.168.0.0/4
 └─1056 /usr/bin/distccd --no-detach --daemon 
--whitelist=/etc/distcc/clients.allow --jobs 4 --listen 192.168.0.3 --allow 
192.168.0.0/4

Jun 16 12:47:54 tp03.localdomain systemd[1]: Started Distccd A Distributed 
Compilation Server.

___
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


systemctl status distccd

2020-06-16 Thread Michael J. Baars
Hi,

Since it's awfully quiet on the initscripts-devel mailing list.

Best regards,
Mischa.




distccd.service.d.tar.xz
Description: application/xz-compressed-tar
[root@tp02 ~]# systemctl status distccd
● distccd.service - Distccd A Distributed Compilation Server
 Loaded: loaded (/usr/lib/systemd/system/distccd.service; enabled; vendor 
preset: disabled)
 Active: failed (Result: exit-code) since Tue 2020-06-16 09:35:00 CEST; 
21min ago
Process: 741 ExecStart=/usr/bin/distccd --no-detach --daemon 
--whitelist=/etc/distcc/clients.allow $OPTIONS (code=exited, status=102)
   Main PID: 741 (code=exited, status=102)
CPU: 16ms

Jun 16 09:35:00 tp02.localdomain systemd[1]: Started Distccd A Distributed 
Compilation Server.
Jun 16 09:35:00 tp02.localdomain distccd[741]: (dcc_listen_by_addr) ERROR: bind 
of 192.168.0.2:3632 failed: Cannot assign requested address
Jun 16 09:35:00 tp02.localdomain systemd[1]: distccd.service: Main process 
exited, code=exited, status=102/n/a
Jun 16 09:35:00 tp02.localdomain systemd[1]: distccd.service: Failed with 
result 'exit-code'.

[root@tp02 mjbaars1977]# systemctl status distccd
● distccd.service - Distccd A Distributed Compilation Server
 Loaded: loaded (/usr/lib/systemd/system/distccd.service; enabled; vendor 
preset: disabled)
Drop-In: /etc/systemd/system/distccd.service.d
 └─distccd.service.conf
 Active: active (running) since Tue 2020-06-16 12:47:54 CEST; 46s ago
   Main PID: 945 (distccd)
  Tasks: 5 (limit: 4488)
 Memory: 1.7M
CPU: 20ms
 CGroup: /system.slice/distccd.service
 ├─ 945 /usr/bin/distccd --no-detach --daemon 
--whitelist=/etc/distcc/clients.allow --jobs 4 --listen 192.168.0.3 --allow 
192.168.0.0/4
 ├─ 952 /usr/bin/distccd --no-detach --daemon 
--whitelist=/etc/distcc/clients.allow --jobs 4 --listen 192.168.0.3 --allow 
192.168.0.0/4
 ├─ 994 /usr/bin/distccd --no-detach --daemon 
--whitelist=/etc/distcc/clients.allow --jobs 4 --listen 192.168.0.3 --allow 
192.168.0.0/4
 ├─1038 /usr/bin/distccd --no-detach --daemon 
--whitelist=/etc/distcc/clients.allow --jobs 4 --listen 192.168.0.3 --allow 
192.168.0.0/4
 └─1056 /usr/bin/distccd --no-detach --daemon 
--whitelist=/etc/distcc/clients.allow --jobs 4 --listen 192.168.0.3 --allow 
192.168.0.0/4

Jun 16 12:47:54 tp03.localdomain systemd[1]: Started Distccd A Distributed 
Compilation Server.

___
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


New HPLIP release 3.20.6 doesn't require plugin for printers whose needed plugin in the past

2020-06-16 Thread Zdenek Dohnal
Hi all,

I'm HPLIP maintainer in Fedora and I would like to ask *the users which
have HP printers which needed their HP plugin to test the scratch build*
of new hplip.

HPLIP released a new version 3.20.6, where most models, which previously
required HP plugin, were set to do not require plugin anymore.

Although requirement of HP plugin was questionable with some printer
models, other models may really needed it and they will not work without it.

Please try the following scratch builds:

Rawhide:

https://koji.fedoraproject.org/koji/taskinfo?taskID=45790790

F32:

https://koji.fedoraproject.org/koji/taskinfo?taskID=45790902

F31:

https://koji.fedoraproject.org/koji/taskinfo?taskID=45790908

And if the update breaks printing or scanning for you, please let the
upstream know here:

https://bugs.launchpad.net/hplip


Thank you in advance for helping with testing!


Zdenek

-- 
Zdenek Dohnal
Software Engineer
Red Hat Czech - Brno TPB-C



signature.asc
Description: OpenPGP digital signature
___
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


Re: New HPLIP release 3.20.6 doesn't require plugin for printers whose needed plugin in the past

2020-06-16 Thread Zdenek Dohnal
There isn't a sucg list, but basically you can check git log at
https://github.com/zdohnal/hplip .

On 6/16/20 3:14 PM, Tomasz Torcz wrote:
> On Tue, Jun 16, 2020 at 03:01:22PM +0200, Zdenek Dohnal wrote:
>> Hi all,
>>
>> I'm HPLIP maintainer in Fedora and I would like to ask *the users which
>> have HP printers which needed their HP plugin to test the scratch build*
>> of new hplip.
>>
>> HPLIP released a new version 3.20.6, where most models, which previously
>> required HP plugin, were set to do not require plugin anymore.
>   Is there a list of printers not requiring plugin anymore?
>   Downloading this plugin was the most cumbersome.  In line with
> Murphys's laws, I was noticing hplip was upgraded, and thus requiring
> re-downloading plugin, when I had to print/scan something urgently.
>
>
-- 
Zdenek Dohnal
Software Engineer
Red Hat Czech - Brno TPB-C




signature.asc
Description: OpenPGP digital signature
___
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


Re: New HPLIP release 3.20.6 doesn't require plugin for printers whose needed plugin in the past

2020-06-16 Thread Zdenek Dohnal
And please don't try to reinstall plugin. It seems they haven't built a
new one yet or they aren't planning to.

See http://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/

On 6/16/20 3:01 PM, Zdenek Dohnal wrote:
>
> Hi all,
>
> I'm HPLIP maintainer in Fedora and I would like to ask *the users
> which have HP printers which needed their HP plugin to test the
> scratch build* of new hplip.
>
> HPLIP released a new version 3.20.6, where most models, which
> previously required HP plugin, were set to do not require plugin anymore.
>
> Although requirement of HP plugin was questionable with some printer
> models, other models may really needed it and they will not work
> without it.
>
> Please try the following scratch builds:
>
> Rawhide:
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=45790790
>
> F32:
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=45790902
>
> F31:
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=45790908
>
> And if the update breaks printing or scanning for you, please let the
> upstream know here:
>
> https://bugs.launchpad.net/hplip
>
>
> Thank you in advance for helping with testing!
>
>
> Zdenek
>
> -- 
> Zdenek Dohnal
> Software Engineer
> Red Hat Czech - Brno TPB-C
>
> ___
> devel mailing list -- de...@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/de...@lists.fedoraproject.org

-- 
Zdenek Dohnal
Software Engineer
Red Hat Czech - Brno TPB-C



signature.asc
Description: OpenPGP digital signature
___
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


Re: More boot questions

2020-06-16 Thread Patrick O'Callaghan
On Tue, 2020-06-16 at 07:59 -0300, George N. White III wrote:
> On Tue, 16 Jun 2020 at 02:08, Tim via users 
> wrote:
> 
> > On Mon, 2020-06-15 at 17:56 +0100, Patrick O'Callaghan wrote:
> > > My system disk is a Samsung EVO SSD (2TB) and I'm unaware of any
> > > problems with it. Smartcontrol shows no errors.
> > 
> > Likewise.  And I just bought a new 500 gig Samsung Evo 860  to install
> > in a server.
> > 
> 
> Reports of problems using AMD hardware:
> https://eu.community.samsung.com/t5/Computers-IT/860-EVO-250GB-causing-freezes-on-AMD-system/td-p/575813
> 
>  00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI]
> SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40)
> Subsystem: Gigabyte Technology Co., Ltd SB7x0/SB8x0/SB9x0 SATA Controller
> [AHCI mode]
> Kernel driver in use: ahci
> Kernel modules: ahci
> 
> I wrote to Samsung's EU support (samsungmem...@hanaro.eu) and they told me
> to "use an Intel controller or SATA AHCI controller." to which I explained
> that it's obvious that the controller in the AMD chipset is SATA AHCI.
> After few more mails where I explained that it's not normal for the SSD to
> act like that, they continued to blame the AMD SATA controller, I clearly
> stated that I'm not going to buy new system just to get the SSD working
> correctly and that the issue is in their SSD controller and not the AMD
> SATA controller and it's up to them to fix it with firmware update. Well,
> it's seems that it's not going to happen - they told me to return the SSD
> back to the retailer or to send it to their service center in the
> Netherlands

My mobo is a fairly old MSI with an Intel chipset. The SSD is connected
to a SATA-3 header.

poc
___
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


Re: How do I change the grub kernel boot parameters in F32 ?

2020-06-16 Thread Tom H
On Tue, Jun 16, 2020 Stephen Morris  wrote:
> On 16/6/20 9:06 am, Ed Greshko wrote:
>> On 2020-06-16 07:01, Tom H wrote:
>>>
>>> The kernel options are in the BLS entries, so it doesn't matter
>>> what you have in grubenv.
>>>
>>> From the grub2 changelog on may 13th:
>>>
>>> Store cmdline in BLS snippets instead of using a grubenv variable
>>>
>>> The kernel cmdline was stored as a kernelopts variable in the
>>> grubenv file and the BLS snippets used that. But this turned out to
>>> be fragile since the grubenv file could be removed or get corrupted
>>> easily.
>>>
>>> To prevent the entries to not have a cmdline if the grubenv can't
>>> be read, a fallback variable was set in the GRUB config file. But
>>> this still caused issues since the config needs to be re-generated
>>> to change the parameters.
>>>
>>> Instead, let's store the cmdline in the BLS snippets. This will
>>> make the configuration more robust, since it will work even without
>>> the grubenv file and the BLS entries will contain all the
>>> information needed to boot.
>>
>> Thanks for that.
>>
>> Just to complete my understanding, by the BLS snippets you mean the
>>
>> /boot/loader/entries/*.conf
>>
>> files?
>
> If GRUB_ENABLE_BLSCFG=false is not going to be supported anymore, how
> does one disable BLS if we don't want it?

You MAY be right in assuming that Fedora might choose only to support BLS.

If that day comes, we'll use BLS. I hope that, by then, we'll have a
way to customize the snippets, for example, not to use the machine-id
UUIDs.
___
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


Re: systemctl status distccd

2020-06-16 Thread Patrick O'Callaghan
On Tue, 2020-06-16 at 13:50 +0200, Michael J. Baars wrote:
> Hi,
> 
> Since it's awfully quiet on the initscripts-devel mailing list.

What is this and why is it relevant to this list rather than
initscripts-devel? I'd appreciate being able to read what something's
about without having to open an attached tar file.

I also see you appear to have reposted the exact same message twice.

poc
___
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


Re: How do I change the grub kernel boot parameters in F32 ?

2020-06-16 Thread Tom H
On Tue, Jun 16, 2020 at 1:50 PM Ed Greshko  wrote:
> On 2020-06-16 19:42, Stephen Morris wrote:
>>
>> If GRUB_ENABLE_BLSCFG=false is not going to be supported anymore,
>> how does one disable BLS if we don't want it?
>
> If that should happen then one needs to learn how to work with BLS.
> Legacy methods aren't supported forever. Just like we don't have
> System V init scripts.

LOL. I don't think that you can call the grub config that every
distribution other than Fedora and RHEL uses "legacy." I wonder
whether BLSCFG's been upstreamed.
___
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


Re: How do I change the grub kernel boot parameters in F32 ?

2020-06-16 Thread Ed Greshko
On 2020-06-17 00:38, Tom H wrote:
> On Tue, Jun 16, 2020 at 1:50 PM Ed Greshko  wrote:
>> On 2020-06-16 19:42, Stephen Morris wrote:
>>> If GRUB_ENABLE_BLSCFG=false is not going to be supported anymore,
>>> how does one disable BLS if we don't want it?
>> If that should happen then one needs to learn how to work with BLS.
>> Legacy methods aren't supported forever. Just like we don't have
>> System V init scripts.
> LOL. I don't think that you can call the grub config that every
> distribution other than Fedora and RHEL uses "legacy." I wonder
> whether BLSCFG's been upstreamed.

Well, I do think that if a given distribution has decided to no longer support 
a feature it
can be call "legacy" within that distribution. 

What was the arc of systemd?

Oh, and it seems, BLS is an outgrowth of systemd?   
https://systemd.io/BOOT_LOADER_SPECIFICATION/

-- 
The key to getting good answers is to ask good questions.
___
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


Re: systemctl status distccd

2020-06-16 Thread Tim via users
On Tue, 2020-06-16 at 13:50 +0200, Michael J. Baars wrote:
> Since it's awfully quiet on the initscripts-devel mailing list.

There doesn't seem to be a question in your email.
 
-- 
 
uname -rsvp
Linux 3.10.0-1127.10.1.el7.x86_64 #1 SMP Wed Jun 3 14:28:03 UTC 2020 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


Re: More boot questions

2020-06-16 Thread Tim via users
Tim:
>> And I just bought a new 500 gig Samsung Evo 860  to install
>> in a server.


George N. White III:
> Reports of problems using AMD hardware:
> https://eu.community.samsung.com/t5/Computers-IT/860-EVO-250GB-causing-freezes-on-AMD-system/td-p/575813
> 
> >  00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI]
> > SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40)
> > Subsystem: Gigabyte Technology Co., Ltd SB7x0/SB8x0/SB9x0 SATA
> > Controller [AHCI mode]
> > Kernel driver in use: ahci
> > Kernel modules: ahci
> > 
> > I wrote to Samsung's EU support (samsungmem...@hanaro.eu) and they
> > told me to "use an Intel controller or SATA AHCI controller." to
> > which I explained that it's obvious that the controller in the AMD
> > chipset is SATA AHCI. After few more mails where I explained that
> > it's not normal for the SSD to act like that, they continued to
> > blame the AMD SATA controller, I clearly stated that I'm not going
> > to buy new system just to get the SSD working correctly and that
> > the issue is in their SSD controller and not the AMD SATA
> > controller and it's up to them to fix it with firmware update.
> > Well, it's seems that it's not going to happen - they told me to
> > return the SSD back to the retailer or to send it to their service
> > center in the Netherlands

My motherboards are both ASRock B250M Pro4, I can't find anything
saying what chipset is involved with SATA, just this:

  6 x SATA3 6.0 Gb/s Connectors, support NCQ, AHCI and Hot Plug
https://www.asrock.com/MB/Intel/B250M%20Pro4/index.asp#Specification

Very unenlightening.

One of the PCs has been using a 500 gig Samsung 860 drive for a couple
of years without noticing any drive problems.  Nor had I done anything
special in the UEFI for it, just plugged it in and let Fedora install
itself.  The other's been using a hard drive, and I just bought the
same model drive to use in it.

-- 
 
uname -rsvp
Linux 3.10.0-1127.10.1.el7.x86_64 #1 SMP Wed Jun 3 14:28:03 UTC 2020 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


Re: systemctl status distccd

2020-06-16 Thread Ed Greshko
On 2020-06-17 09:53, Tim via users wrote:
> On Tue, 2020-06-16 at 13:50 +0200, Michael J. Baars wrote:
>> Since it's awfully quiet on the initscripts-devel mailing list.
> There doesn't seem to be a question in your email.
>  

You have to open the attachments to learn what is the issue.

-- 
The key to getting good answers is to ask good questions.
___
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


Re: More boot questions

2020-06-16 Thread Robert McBroom via users

On 6/15/20 12:57 AM, Samuel Sieb wrote:

On 6/14/20 9:40 PM, Robert McBroom via users wrote:

On 6/14/20 3:12 PM, Samuel Sieb wrote:

On 6/14/20 9:39 AM, Robert McBroom via users wrote:
Copied my fedora 29 system to an SSD partition. Booting takes me to 
Grub-rescue>


SuperGrub2 2.04s1 finds the system and boots it but it is read 
only.?? Knoppix reads and writes to the system with no problem. 
Used Knoppix to fix /etc/fstab and grub.cfg. I think grub-install 
is needed from fedora but have to be able to write to the drive.


You need to provide more details.  What do you mean it's read only? 
And grub-install write to the raw hard drive, not to a filesystem.  
A Fedora live boot or a net install rescue boot is a good way to fix 
things.

___
Any attempt to write to the system gets a message that the file 
system is read only.  grub2-install /dev/sda fails trying writes to 
/boot/grub2/i386-pc. ls -l gives a list that looks completely normal 
with the expected permissions owners and groups.


Oh, right, it wants to set up the modules too.
What does "mount" show?  Try running "mount -o rw,remount /".  Or use 
"/boot" instead if you have a separate partition for it.


The simplest method though is still to download a Fedora net install 
image and use the rescue mode.  It sets everything up for you to 
chroot to the installed system and run whatever you want. Just be 
aware that it will do a full relabel on reboot.  If you're sure you 
didn't change anything important, you can remove the /.autorelabel 
file before rebooting.


Found my problem and it is a curiosity on how the disk designations
interact.  In entering the / UUID in fstab a 6 became a b.  The entries
in grub.cfg were correct and apparently allowed the system to boot and
run as long as there was nothing needing to be written to the drive.  I
boot to a terminal and then start the graphical display which could not
happen without writing to the .serverauth.xxx and .Xauthority files
among others.  Corrected, the system is working without problems and
upgraded from f29 to f32.  Didn't have to dig out the warranty on the
drive after all.

___
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


Re: systemctl status distccd

2020-06-16 Thread Tim via users
Tim:
>> There doesn't seem to be a question in your email.
 

Ed Greshko:
> You have to open the attachments to learn what is the issue.

I did, before I wrote that.  There still isn't a question, just some
submitted log files.  He doesn't ask anything about them.  I don't know
if this is some kind of bug report, or if he's asking for help with
solving a configuration, or what kind of help he needs.  The batteries
in my crystal ball have gone flat.
 
-- 
 
uname -rsvp
Linux 3.10.0-1127.10.1.el7.x86_64 #1 SMP Wed Jun 3 14:28:03 UTC 2020 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