Re: [gentoo-user] Trouble with backup harddisks

2020-04-30 Thread tuxic
On 04/30 10:47, Wynn Wolf Arbor wrote:
> On 2020-04-30 22:21, Andrea Conti wrote:
> > It won't, as long as it recognizes it as a protective MBR. Which is the
> > right thing to do, as a disk with a protective MBR and no valid GPT is
> > inherently broken.
> 
> True. It was more my intention to depict what the system "should" do in
> order to access the file system.
> 
> > ... or just bypass the partition table altogether. The filesystem starts
> > at sector 1, i.e. 1*512B, so:
> > 
> > mount -o ro,offset=512 /dev/sdb /mnt/xxx
> 
> Interesting, thanks. I was initially considering something like this myself,
> but after a cursory check of the manual, I was under the assumption that
> 'offset' was only valid with loop devices and dismissed that solution.
> 
> Turns out if you mount a drive like this, the kernel uses a loop device in
> the background and you can use the 'offset' option with block devices as
> well. I feel the documentation could be improved here.
> 
> -- 
> Wolf
> 

Hi Andrea, hi Wolf

does my posting from this morning reached you ?
...I did not received anything back from the mailinglist...

Cheers!
Meino





Re: [gentoo-user] Trouble with backup harddisks

2020-04-30 Thread tuxic
On 04/30 08:32, antlists wrote:
> On 30/04/2020 18:04, tu...@posteo.de wrote:
> > I copied the first 230GB of that disk to an empty partition of my new
> > system and run "testdisk" on itafter the analysis it came back
> > with "this partition cannot be recovered" but did not sau. whether the
> > reason is a partition table, which is broken beyond repair, or simply
> > due to the incomplete image file...
> 
> Just come up with another idea that will hopefully give us some clues...
> 
> https://raid.wiki.kernel.org/index.php/Asking_for_help#lsdrv
> 
> Ignore the fact that it's the raid wiki - this tool basically delves into
> the drive and tries to find mbr, gpt, superblock, lvm and raid signatures,
> everything ...
> 
> So run that and see what it tells us ...
> 
> Cheers,
> Wol
> 

Hi Wol,

thank you for the link! I have installed mdadm (its on portage) but I
have not used it, since there is another soultion for this, which I
tried first. 

Andrea posted this wonderful line:

mount -o ro,offset=512 /dev/sdb /mnt/xxx

which mounts the filesystem by skipping the partitiontable completly.

Currently I am rescueing the data. If all is safed, I will tru
mdadm...

Thank you very much for your help!

As soon as there are more information, I will report back.
Maybe this can also help others with similiar problems.

Cheers!
Meino





[gentoo-user] Re: Upgrading old kernel

2020-04-30 Thread Jonathan Callen
On 4/16/20 3:43 AM, Nikos Chantziaras wrote:
> On 16/04/2020 10:21, Ashley Dixon wrote:
>> On Thu, Apr 16, 2020 at 10:08:45AM +0300, Nikos Chantziaras wrote:
>>> There's also sys-kernel/gentoo-kernel but it's description is
>>> confusing as
>>> hell: "Linux kernel built with Gentoo patches". Which to me sounds
>>> exactly
>>> like gentoo-kernel-bin just with slightly different wording... :-/
>>
>> The difference can be seen in the ebuild source U.R.I.s:
>>  gentoo-kernel-bin:
>> https://dev.gentoo.org/~mgorny/binpkg/amd64/kernel/ \
>>  sys-kernel/gentoo-kernel/${MY_P}.xpak
>>  gentoo-kernel: https://cdn.kernel.org/pub/linux/kernel/ ... +
>>  patches from
>> https://dev.gentoo.org/~mpagano/dist/genpatches
>>
>> The wording is horrible, but as the suffix ("-bin") would suggest, the
>> former is
>> a binary  .xpak  package,  whereas  the  latter  is  base  kernel 
>> sources  with
>> additional Gentoo developers' patches.
> 
> I still don't understand what that means. If it's a pre-built kernel,
> then it sounds the same as gentoo-kernel-bin. If it's sources, then it
> sounds the same as gentoo-sources.
> 

It's neither.  The package installs a kernel (not just sources for the
kernel), like gentoo-kernel-bin, but it does so by building it locally,
just like just about every other package that doesn't have a name ending
in "-bin". On the other hand, gentoo-kernel-bin downloads a precompiled
kernel and just installs it locally, not compiling anything.  The
gentoo-sources package also doesn't compile anything, it just dumps some
source code on your system for you to compile outside of portage.

In short:
  |  Downloaded  |  Installed
--+--+-
gentoo-sources| source code  | source code
gentoo-kernel | source code  | built kernel
gentoo-kernel-bin | built kernel | built kernel

-- 
Jonathan Callen



signature.asc
Description: OpenPGP digital signature


Re: [gentoo-user] Trouble with backup harddisks

2020-04-30 Thread Wynn Wolf Arbor

On 2020-04-30 22:21, Andrea Conti wrote:
It won't, as long as it recognizes it as a protective MBR. Which is the 
right thing to do, as a disk with a protective MBR and no valid GPT is 
inherently broken.


True. It was more my intention to depict what the system "should" do in 
order to access the file system.


... or just bypass the partition table altogether. The filesystem 
starts at sector 1, i.e. 1*512B, so:


mount -o ro,offset=512 /dev/sdb /mnt/xxx


Interesting, thanks. I was initially considering something like this 
myself, but after a cursory check of the manual, I was under the 
assumption that 'offset' was only valid with loop devices and dismissed 
that solution.


Turns out if you mount a drive like this, the kernel uses a loop device 
in the background and you can use the 'offset' option with block devices 
as well. I feel the documentation could be improved here.


--
Wolf



Re: [gentoo-user] Trouble with backup harddisks

2020-04-30 Thread Andrea Conti
> Since the disk was only ever accessed through an operating system that knew 
> solely about MBR, the GPT data meant nothing to it. It happily wrote data 
> past the MBR headers. Because the protective MBR is positioned before GPT 
> information, the primary GPT header was destroyed and most likely overwritten 
> with the file system. See also [1], the actual file system data probably 
> begins somewhere past LBA 0.

If it was created according to the MBR that was shown previously, it will start 
at the beginning of the protective entry, i.e. at sector 1.

> If the initial assumption is correct, GPT *must not* be restored. Your modern 
> PC sees the GPT partition type and assumes the existence of a GPT. It should, 
> however, access the MBR layout and interpret the partition marked with the 
> GPT ID as a regular partition.

It won't, as long as it recognizes it as a protective MBR. Which is the right 
thing to do, as a disk with a protective MBR and no valid GPT is inherently 
broken.

> 1) Boot an older system that only understands MBR, and mount the disk there. 
> This was suggested earlier but was dismissed because we assumed the sector 
> size had something to do with it. I do not think this is the case anymore - 
> the old system should be able to read it.
> 
> 2) Boot a VM with a kernel that only understands MBR, pass USB through to the 
> virtual machine, mount the disk there.
> 
> 3) Try confirming that there exists file system data past the MBR header.
>
> Maybe something like this:
> 
> # dd if=/dev/sdb of=sdb-data bs=512 skip=1 count=16384
> $ file sdb-data 


... or just bypass the partition table altogether. The filesystem starts at 
sector 1, i.e. 1*512B, so:

mount -o ro,offset=512 /dev/sdb /mnt/xxx

But while this will allow you to access your data, you will still have a broken 
disk until you fix the MBR.


andrea



Re: [gentoo-user] sddm-helper and high memory usage

2020-04-30 Thread Dale
Dale wrote:
> Howdy,
>
> <<>>
> When it did this the other day, I closed all my programs so I could
> logout, reset and log back in again.  After I hit logout, I noticed the
> little memory usage meter on the bottom of my screen was down to a more
> normal level.  It was already logging me out so to late to stop it.  It
> seems that it dropped after I closed Firefox.  I tend to have two
> profiles running and they use quite a bit of memory on their own.  The
> new thing is sddm using this much as well.  Could Firefox have some
> effect on this??
>
> <<>>
> Any ideas? 
>
> Dale
>
> :-)  :-) 
>


Ignore the part about Firefox.  I noticed it was up to about 4.3GBs or
13.5% again and closed all my browsers.  After that was done and it
settled a bit, it was using the same amount of memory.  Closing my
browsers has no effect on it's memory usage.  Logging out and back in
again, back to normal.  I'm sure it will start rising again tho.

Still curious to see if anyone else has this issue or has a idea on how
to fix it. 

Thanks.

Dale

:-)  :-) 


Re: [gentoo-user] Trouble with backup harddisks

2020-04-30 Thread Wynn Wolf Arbor

Hi Meino,

On 2020-04-30 21:46, tu...@posteo.de wrote:

I had booted into my old system, attached the disks and both show the
same behaviour: Only the device itself (/dev/sdb) was recognized.


Now that is very curious. Just to make sure, the old system definitely 
does not understand GPT? CONFIG_EFI_PARTITION should be unset.



'file' shows the following output:

file sdb-data
sdb-data: Linux rev 1.0 ext4 filesystem data, 
UUID=2f063705-0d3a-4790-9203-1b4edab7788c (extents) (64bit) (large files) (huge 
files)

Looks better than I have thought...or?


This does indeed look promising (and is what I expected in the best 
case). Now, of course, the problem is figuring out how to get to that 
data.



I will take a deeper look tommorrow...I am too tired to
"fix partition tables manually" this evening!

Read you tommorrow! :)


Hope the rest of your evening will be more relaxing!

--
Wolf



Re: [gentoo-user] Trouble with backup harddisks

2020-04-30 Thread tuxic
Hi Wolf,

thanks for your great input again!

(see below)

On 04/30 09:27, Wynn Wolf Arbor wrote:
> All the following assuming that the disk was originally partitioned as GPT,
> but after that exclusively accessed as an MBR disk.
> 
> > PT fdisk (gdisk) version 1.0.5
> > 
> > Caution: invalid main GPT header, but valid backup; regenerating main header
> > from backup!
> 
> This makes sense since the GPT backup at the very end of the disk would most
> likely still be intact. gdisk identifies it correctly, but assumes (wrongly)
> that the data on the disk is governed by the GPT layout.
> 
> Since the disk was only ever accessed through an operating system that knew
> solely about MBR, the GPT data meant nothing to it. It happily wrote data
> past the MBR headers. Because the protective MBR is positioned before GPT
> information, the primary GPT header was destroyed and most likely
> overwritten with the file system. See also [1], the actual file system data
> probably begins somewhere past LBA 0.
> 
> > Caution! After loading partitions, the CRC doesn't check out!
> > Warning: Invalid CRC on main header data; loaded backup partition table.
> > Warning! Main and backup partition tables differ! Use the 'c' and 'e' 
> > options
> > on the recovery & transformation menu to examine the two tables.
> 
> This is because the backup GPT written when first partitioned does no longer
> match the data present at the very beginning of the disk.
> 
> If the initial assumption is correct, GPT *must not* be restored. Your
> modern PC sees the GPT partition type and assumes the existence of a GPT. It
> should, however, access the MBR layout and interpret the partition marked
> with the GPT ID as a regular partition.
> 
> Now, how to fix this?
> 
> Like Andrea already said earlier:
> 
> > Since the disk is only 1TB, there is no reason to use GPT at all, so
> > your best bet is to use fdisk to make that a standard MBR by changing
> > the partition type from 'ee' to '83'.
> 
> This would *not* repartition or reformat any data, it would simply tell your
> modern operating system to access the protective partition as a regular one.
> 
> It would, however, require writing the new type to disk. What you could do
> to be more safe here is to take a backup of the first 512 bytes with `dd',
> then change the partition ID with `fdisk', and try mounting it.
> 
> If it works, great. If not, you can restore the first 512 bytes of the disk
> with the backup.
> 
> > "fix manually" scares me...especially because I have no place for
> > 1TB of an image file to with which I can experiment ...
> 
> > Any ideas which could ease my burden and to un-scare my
> > "need to fix it manually" ??? ;) ;)
> 
> There's a few alternatives:
> 
> 1) Boot an older system that only understands MBR, and mount the disk there.
> This was suggested earlier but was dismissed because we assumed the sector
> size had something to do with it. I do not think this is the case anymore -
> the old system should be able to read it.
> 
> 2) Boot a VM with a kernel that only understands MBR, pass USB through to
> the virtual machine, mount the disk there.
> 
> 3) Try confirming that there exists file system data past the MBR header.
> 
> Maybe something like this:
> 
> # dd if=/dev/sdb of=sdb-data bs=512 skip=1 count=16384
> $ file sdb-data
> 
> As established, the block size is 512 bytes. We skip the first 512 bytes
> since that is the protective MBR. sdb-data should then contain the first
> 8MiB worth of actual file system data. The `file' utility can tell you what
> kind of data it is.
> 
> [1] 
> https://en.wikipedia.org/wiki/GUID_Partition_Table#/media/File:GUID_Partition_Table_Scheme.svg
> 
> -- 
> Wolf
> 

I had booted into my old system, attached the disks and both show the
same behaviour: Only the device itself (/dev/sdb) was recognized.

'file' shows the following output:

file sdb-data
sdb-data: Linux rev 1.0 ext4 filesystem data, 
UUID=2f063705-0d3a-4790-9203-1b4edab7788c (extents) (64bit) (large files) (huge 
files)

Looks better than I have thought...or?

I will take a deeper look tommorrow...I am too tired to
"fix partition tables manually" this evening!

Read you tommorrow! :)

Cheers!
Meino




Re: [gentoo-user] Trouble with backup harddisks

2020-04-30 Thread antlists

On 30/04/2020 18:04, tu...@posteo.de wrote:

I copied the first 230GB of that disk to an empty partition of my new
system and run "testdisk" on itafter the analysis it came back
with "this partition cannot be recovered" but did not sau. whether the
reason is a partition table, which is broken beyond repair, or simply
due to the incomplete image file...


Just come up with another idea that will hopefully give us some clues...

https://raid.wiki.kernel.org/index.php/Asking_for_help#lsdrv

Ignore the fact that it's the raid wiki - this tool basically delves 
into the drive and tries to find mbr, gpt, superblock, lvm and raid 
signatures, everything ...


So run that and see what it tells us ...

Cheers,
Wol



Re: [gentoo-user] Trouble with backup harddisks

2020-04-30 Thread Wynn Wolf Arbor
All the following assuming that the disk was originally partitioned as 
GPT, but after that exclusively accessed as an MBR disk.



PT fdisk (gdisk) version 1.0.5

Caution: invalid main GPT header, but valid backup; regenerating main header
from backup!


This makes sense since the GPT backup at the very end of the disk would 
most likely still be intact. gdisk identifies it correctly, but assumes 
(wrongly) that the data on the disk is governed by the GPT layout.


Since the disk was only ever accessed through an operating system that 
knew solely about MBR, the GPT data meant nothing to it. It happily 
wrote data past the MBR headers. Because the protective MBR is 
positioned before GPT information, the primary GPT header was destroyed 
and most likely overwritten with the file system. See also [1], the 
actual file system data probably begins somewhere past LBA 0.



Caution! After loading partitions, the CRC doesn't check out!
Warning: Invalid CRC on main header data; loaded backup partition table.
Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.


This is because the backup GPT written when first partitioned does no 
longer match the data present at the very beginning of the disk.


If the initial assumption is correct, GPT *must not* be restored. Your 
modern PC sees the GPT partition type and assumes the existence of a 
GPT. It should, however, access the MBR layout and interpret the 
partition marked with the GPT ID as a regular partition.


Now, how to fix this?

Like Andrea already said earlier: 

Since the disk is only 1TB, there is no reason to use GPT at all, so 
your best bet is to use fdisk to make that a standard MBR by changing 
the partition type from 'ee' to '83'. 


This would *not* repartition or reformat any data, it would simply tell 
your modern operating system to access the protective partition as a 
regular one.


It would, however, require writing the new type to disk. What you could 
do to be more safe here is to take a backup of the first 512 bytes with 
`dd', then change the partition ID with `fdisk', and try mounting it.


If it works, great. If not, you can restore the first 512 bytes of the 
disk with the backup.



"fix manually" scares me...especially because I have no place for
1TB of an image file to with which I can experiment ...



Any ideas which could ease my burden and to un-scare my
"need to fix it manually" ??? ;) ;)


There's a few alternatives:

1) Boot an older system that only understands MBR, and mount the disk 
there. This was suggested earlier but was dismissed because we assumed 
the sector size had something to do with it. I do not think this is the 
case anymore - the old system should be able to read it.


2) Boot a VM with a kernel that only understands MBR, pass USB through 
to the virtual machine, mount the disk there.


3) Try confirming that there exists file system data past the MBR header.

Maybe something like this:

# dd if=/dev/sdb of=sdb-data bs=512 skip=1 count=16384
$ file sdb-data

As established, the block size is 512 bytes. We skip the first 512 bytes 
since that is the protective MBR. sdb-data should then contain the first 
8MiB worth of actual file system data. The `file' utility can tell you 
what kind of data it is.


[1] 
https://en.wikipedia.org/wiki/GUID_Partition_Table#/media/File:GUID_Partition_Table_Scheme.svg

--
Wolf



Re: [gentoo-user] gimp help not available, even with USE doc

2020-04-30 Thread Dale
n952162 wrote:
>
> Thank you, that was good.
>
> I had /usr/share/gimp/2.0/, now, after (3 hours of) emerging
> gimp-help, I also have help/en/
>
> Unfortunately, I still get the same error msg.
>
> Here are my USE flags:
>
> /* Found these USE flags for media-gfx/gimp-2.10.8-r1://
> // U I//
> // - - aalib    : Add support for media-libs/aalib
> (ASCII-Graphics Library)//
> // - - alsa : Add support for media-libs/alsa-lib
> (Advanced Linux Sound//
> //    Architecture)//
> // + + cpu_flags_x86_mmx    : Use the MMX instruction set//
> // + + cpu_flags_x86_sse    : Use the SSE instruction set//
> // - - debug    : Enable extra debug codepaths, like
> asserts and extra output.//
> //    If you want to get meaningful
> backtraces see https://wiki.ge//
> //   
> ntoo.org/wiki/Project:Quality_Assurance/Backtraces//
> // + + doc  : Add extra documentation (API,
> Javadoc, etc). It is//
> //    recommended to enable per package
> instead of globally//
> // - - gnome    : Add GNOME support//
> // - - heif : Enable support for ISO/IEC
> 23008-12:2017 HEIF files //
> // - - jpeg2k   : Support for JPEG 2000, a
> wavelet-based image compression//
> //    format//
> // - - mng  : Add support for libmng (MNG images)//
> // - - openexr  : Support for the OpenEXR graphics
> file format//
> // - - postscript   : Enable support for the PostScript
> language (often with//
> //    ghostscript-gpl or libspectre)//
> // - - python   : Add optional support/bindings for
> the Python language//
> // + + python_targets_python2_7 : Build with Python 2.7//
> // - - test : Enable dependencies and/or
> preparations necessary to run//
> //    tests (usually controlled by
> FEATURES=test but can be//
> //    toggled independently)//
> // - - udev : Enable virtual/udev integration
> (device discovery, power and//
> //    storage device support, etc)//
> // - - unwind   : Add support for call stack unwinding
> and function name//
> //    resolution//
> // - - vector-icons : Enable support for vector icons
> (experimental) //
> // - - webp : Add support for the WebP image format//
> // - - wmf  : Add support for the Windows Metafile
> vector image format//
> // - - xpm  : Add support for XPM graphics format/
>
> I have the feeling that, when gimp didn't see the help/ dir the first
> time, it set something, microsoft-like, in persistant storage, and
> doesn't even try to look locally anymore.
>
> And why it can't access the xml file, which is there, I have no idea. 
> But I see no flags that look related to GIO or GVFS.
>
> You have a lot of flags set... I hope I don't have to set those all,
> just to see if it helps...
>
>

Actually, I think the relevant flags are set.  That made me want to go
look elsewhere based on your idea that it changed a setting when you
didn't have the docs installed.  I went to Preferences, expand Interface
if needed then select Help System.  Here, I have the following checked.
Show tooltips and Show help buttons.  For User Manual drop menu, mine is
set to Use a locally installed copy and below that User interface
language. The rest shouldn't matter. 

See if that helps.  Maybe one of those settings got flipped around.

Dale

:-)  :-) 


[gentoo-user] sddm-helper and high memory usage

2020-04-30 Thread Dale
Howdy,

I been noticing that sddm is using a lot of memory.  In the past, it
would use a few hundred megabytes but nothing out of the norm for a GUI
command.  This is what ps aux shows.



USER   PID   %CPU %MEM    VSZ   RSS  TTY  STAT START   TIME
COMMAND
root   19256  1.0    10.3   3443932 3400112 ? S    02:40   6:36
/usr/libexec/sddm-helper --socket
/tmp/sddm-auth8e2859d9-6da1-4071-b479-b9caa969c3d8 --id 1 --start
/usr/bin/startplasma-x11 --user dale



When it did this the other day, I closed all my programs so I could
logout, reset and log back in again.  After I hit logout, I noticed the
little memory usage meter on the bottom of my screen was down to a more
normal level.  It was already logging me out so to late to stop it.  It
seems that it dropped after I closed Firefox.  I tend to have two
profiles running and they use quite a bit of memory on their own.  The
new thing is sddm using this much as well.  Could Firefox have some
effect on this??

When I first login, it is using the normal amount of memory. It seems to
build up from there.  Once it hits around 13 or 14%, it seems to stop
using any more.  I've let it run for a while and it seems to stop there. 

I'm pretty sure I upgraded sddm the other day.  This is where I'm at
right now.

kde-plasma/sddm-kcm-5.18.4.1
x11-misc/sddm-0.18.1-r1

Is anyone else noticing this?  I would go back a version but it is
masked, I'm assuming it has some known issues that may be worse than this. 

I might add, while I normally switch to the boot runlevel and back again
after a upgrade, I did have to shutdown last night.  I was trying to
replace my UPS batteries.  My new batteries are about 1/4" to tall.  New
set on the way.  Anyway, it is doing this even after a fresh power up.

I did a bug search on BGO but didn't see anything like this.

Any ideas? 

Dale

:-)  :-) 



Re: [gentoo-user] gimp help not available, even with USE doc

2020-04-30 Thread n952162

Thank you, that was good.

I had /usr/share/gimp/2.0/, now, after (3 hours of) emerging gimp-help, 
I also have help/en/


Unfortunately, I still get the same error msg.

Here are my USE flags:

/* Found these USE flags for media-gfx/gimp-2.10.8-r1://
// U I//
// - - aalib    : Add support for media-libs/aalib 
(ASCII-Graphics Library)//
// - - alsa : Add support for media-libs/alsa-lib 
(Advanced Linux Sound//

//    Architecture)//
// + + cpu_flags_x86_mmx    : Use the MMX instruction set//
// + + cpu_flags_x86_sse    : Use the SSE instruction set//
// - - debug    : Enable extra debug codepaths, like 
asserts and extra output.//
//    If you want to get meaningful 
backtraces see https://wiki.ge//

//ntoo.org/wiki/Project:Quality_Assurance/Backtraces//
// + + doc  : Add extra documentation (API, Javadoc, 
etc). It is//
//    recommended to enable per package 
instead of globally//

// - - gnome    : Add GNOME support//
// - - heif : Enable support for ISO/IEC 
23008-12:2017 HEIF files //
// - - jpeg2k   : Support for JPEG 2000, a wavelet-based 
image compression//

//    format//
// - - mng  : Add support for libmng (MNG images)//
// - - openexr  : Support for the OpenEXR graphics file 
format//
// - - postscript   : Enable support for the PostScript 
language (often with//

//    ghostscript-gpl or libspectre)//
// - - python   : Add optional support/bindings for the 
Python language//

// + + python_targets_python2_7 : Build with Python 2.7//
// - - test : Enable dependencies and/or 
preparations necessary to run//
//    tests (usually controlled by 
FEATURES=test but can be//

//    toggled independently)//
// - - udev : Enable virtual/udev integration 
(device discovery, power and//

//    storage device support, etc)//
// - - unwind   : Add support for call stack unwinding 
and function name//

//    resolution//
// - - vector-icons : Enable support for vector icons 
(experimental) //

// - - webp : Add support for the WebP image format//
// - - wmf  : Add support for the Windows Metafile 
vector image format//

// - - xpm  : Add support for XPM graphics format/

I have the feeling that, when gimp didn't see the help/ dir the first 
time, it set something, microsoft-like, in persistant storage, and 
doesn't even try to look locally anymore.


And why it can't access the xml file, which is there, I have no idea.  
But I see no flags that look related to GIO or GVFS.


You have a lot of flags set... I hope I don't have to set those all, 
just to see if it helps...



On 2020-04-30 14:31, Dale wrote:

n952162 wrote:


After emerging gimp, I tried to get help (after re-emerging with the 
doc USE flag), and got this:


/Could not open 'https://docs.gimp.org/2.10/en/gimp-help.xml' for
reading: Operation not supported//
//
//Perhaps you are missing GIO backends and need to install GVFS?/

Is there anything I can do?





When I open GIMP and go to help, it takes me here:

file:///usr/share/gimp/2.0/help/en/index.html

It opens in Seamonkey for me.  Seamonkey is set as my default 
browser.  This is my USE flag settings.




root@fireball / # emerge -pv app-doc/gimp-help media-gfx/gimp

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] app-doc/gimp-help-2.8.2:2::gentoo  0 KiB
[ebuild   R   ~] media-gfx/gimp-2.10.18-r1:2::gentoo  USE="alsa doc 
jpeg2k mng python udev wmf -aalib (-aqua) -debug -gnome -heif -openexr 
-postscript -test -unwind -vector-icons -webp -xpm" CPU_FLAGS_X86="mmx 
sse" PYTHON_SINGLE_TARGET="python2_7" 0 KiB


Total: 2 packages (2 reinstalls), Size of downloads: 0 KiB
root@fireball / #


Do you have the gimp-help package installed?  If so, your USE flags 
match mine?


Dale

:-)  :-)


Re: [gentoo-user] Trouble with backup harddisks

2020-04-30 Thread tuxic
On 04/30 03:44, Andrea Conti wrote:
> Hi,
> 
> > > CONFIG_PARTITION_ADVANCED=y
> > > CONFIG_MSDOS_PARTITION=y
> > > CONFIG_EFI_PARTITION=y
> 
> That's all you need.
> 
> > This could be the key. Sector sizes have been changing from 512 to 4096
> > over many years. If your kernel has been updated to expect/use 4096 byte
> > sectors, it might not be able to read the disk properly.
> 
> Sector size is only a (fixed) property of a specific block device, not 
> something expected or required by the kernel.
> Sector sizes other than 512B have been around for ages without any problems, 
> even in consumer hardware (e.g. CDs and DVDs have 2KB sectors).
> 
> > Disklabel type: dos
> 
> > Device Boot StartEndSectors   Size Id Type
> > /dev/sdb1   1 1953458175 1953458175 931.5G ee GPT
> 
> That looks... broken.
> fdisk is recognizing the disk as MBR (a GPT disk would have "Disklabel type: 
> gpt"), but the partition table is a protective MBR, which makes no sense in a 
> non-GPT disk.
> 
> My guess is that this disk was at some time partitioned with GPT (possibly it 
> came that way from WD?), but then it was only used in machines with no kernel 
> support for GPT.
> Such a machine will happily treat that as a normal MBR and allow you to 
> access the protective entry as a normal partition, which means you can create 
> a filesystem on it and fill it with data, destroying the GPT structures.
> 
> A GPT-aware kernel on the other hand will recognize that as a protective MBR 
> and it will ignore it --but since the disk does not contain any valid GPT 
> structures, it will not show any partitions.
> 
> Try running "gdisk -l /dev/sdb"; for a valid GPT disk it will say:
> 
> Partition table scan:
>   MBR: protective
>   BSD: not present
>   APM: not present
>   GPT: present
> 
> If that's not the case and you have no GPT, you will have to fix things 
> manually.
> Since the disk is only 1TB, there is no reason to use GPT at all, so your 
> best bet is to use fdisk to make that a standard MBR by changing the 
> partition type from 'ee' to '83'.
> 
> andrea
> 

Hi Andreas,

thank you very much for your analysis! :)

when doing a gdisk -l /dev/sdb I get this Rocky Horror Picture Show:


PT fdisk (gdisk) version 1.0.5

Caution: invalid main GPT header, but valid backup; regenerating main header
from backup!

Caution! After loading partitions, the CRC doesn't check out!
Warning: Invalid CRC on main header data; loaded backup partition table.
Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.

Warning! One or more CRCs don't match. You should repair the disk!
Main header: ERROR
Backup header: OK
Main partition table: ERROR
Backup partition table: ERROR

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: damaged


Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.

Disk /dev/sdb: 1953458176 sectors, 931.5 GiB
Model: Elements 25A2   
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): BCA95A74-1E0A-4648-9971-20ED4049CAE5
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 1953458142
Partitions will be aligned on 2048-sector boundaries
Total free space is 1953458109 sectors (931.5 GiB)

Number  Start (sector)End (sector)  Size   Code  Name



"fix manually" scares me...especially because I have no place for
1TB of an image file to with which I can experiment ...

Any ideas which could ease my burden and to un-scare my 
"need to fix it manually" ??? ;) ;)

Cheers!
Meino







Re: [gentoo-user] Trouble with backup harddisks

2020-04-30 Thread Wynn Wolf Arbor

Hi Meino,

Thanks very much for the info. At this point I'm convinced you're 
running into the problem Andrea described in another reply in this 
thread - best to follow up there :)


--
Wolf



[gentoo-user] Re: Problem understanding "eix"

2020-04-30 Thread Martin Vaeth
Dr Rainer Woitok  wrote:
>
> Yes.  To satisfy the requirements of package "sys-apps/fwupd" I long ago
> added the line
>
>>=app-crypt/tpm2-tss-2.2.3-r1 ~amd64

Ah! That explains it.

> But this only means  that I accept  an unstable  package here,  not that
> these versions  are regarded stable.

It is stabe according to the local configuration on your system.
What you look for is perhaps {wasstable} which returns the value
according to the default configuration.




Re: [gentoo-user] Trouble with backup harddisks

2020-04-30 Thread tuxic
Hi Wolf

thank you very much for your analysis ! :)

On 04/30 03:10, Wynn Wolf Arbor wrote:
> Hi,
> 
> On 2020-04-30 13:17, Wols Lists wrote:
> > All I can suggest is to check the kernel and see if it's an option that
> > has been disabled (512-byte sectors, that is).
> 
> As far as I know the kernel still uses 512 bytes internally [1], and I do
> not recall having seen an option that enables or disables support for 512/4K
> sectors.
> 
> That said, the problem may well be stemming from a sector size discrepancy,
> but as I understand it, it would have to do with how and when the partition
> table was created. That is, like described in [2], some USB enclosures seem
> to be a bit overzealous with obscure features, and might take eight disk
> sectors and bundle them together into one 4K sector.
> 
> If the disk was partitioned in the exact same enclosure, and is read from
> the exact same enclosure right now, there shouldn't be any problems. Is this
> the case, Meino?

I have two external disks of that kind, same product, nearly the same
contents, both have a "fixed case" (sorry...no native speaker...the
case and the disk mechanics/electronics is "one thing").
> 
> Also, when did you last access the drives successfully, and with which
> system?

Three weeks ago...about...guessed...with my old system.
Because these were backup disks I *NEVER* touch them with
any partitioning tool whatsoever...

It is complete unknown to me, what could have destroyed the
partitioning...

> On 2020-04-30 11:32, Meino wrote:
> > Disk /dev/sdb: 931.49 GiB, 1000170586112 bytes, 1953458176 sectors
> > Disk model: Elements 25A2   Units: sectors of 1 * 512 = 512 bytes
> > Sector size (logical/physical): 512 bytes / 512 bytes
> > I/O size (minimum/optimal): 512 bytes / 512 bytes
> > 
> > Disklabel type: dos
> > Disk identifier: 0x16f2a91f
> > 
> > Device Boot StartEndSectors   Size Id Type
> > /dev/sdb1   1 1953458175 1953458175 931.5G ee GPT
> 
> Interestingly, this reads *exactly* like the Protective MBR [3] that GPT
> has. That is, the disklabel type is DOS whilst the partition ID is EE.
> There's a single partition that spans the entire drive (and it's also
> seemingly not aligned properly - usually you see Start at 2048).

> As a comparison, here's the output from fdisk for the Protective MBR from
> one of my GPT drives:
> 
> > Disklabel type: dos
> > Disk identifier: 0x
> 
> > Device Boot StartEndSectors Size Id Type
> > /dev/sdc1   1 4294967295 4294967295   2T ee GPT
> 
> I'd assume that the missing disk identifier here is coming from different
> tools writing the protective MBR differently.
> 
> With that said, are you absolutely certain that you did not partition this
> drive with GPT instead of MBR? 

YES! These drives were used as backup and as backup of the backup. I
NEVER touched them with any partitioning tool after I had put a
filesystem and data on it.

> Did you do the partitioning in something like
> fdisk (which asks you specifically what you want), or some other
> application? Did you maybe format this drive on a Windows system?

Windows? no thank you...all my windows here are transparent and
open,.. ;)
Joke aside..
No Windows (tm) here. The disks are used only with my Linux box using
ext4 as filesystem.

> 
> I'm not one to discount entirely strange things happening, but I have never
> before seen a proper MBR laid out like a protective MBR. Indeed it would be
> quite impossible to have systems access data through such a table, since the
> partitions are hidden within that one huge contiguous block.
> 
> Ordinarily I'd point to fdisk not reading the partition table properly, but
> it seems that although your kernel has support for GPT, it doesn't seem to
> see the partitions either (assuming a proper GPT exists at all).

> Do you have some other GPT drives you can access successfully?
With my new PC (my old MBR-based system was 12 years old and needed to
be replaced. My kernel became "GPT aware onlu with my new PC.
Everything before was based on MBR.

My new PC can read GPT disks...my system is based on it.
> 
> I'd say that this requires some more forensic work. Perhaps extracting the
> first few megabytes of the disk and seeing whether there's a proper GPT or
> not. This would of course require manual work.

I copied the first 230GB of that disk to an empty partition of my new
system and run "testdisk" on itafter the analysis it came back
with "this partition cannot be recovered" but did not sau. whether the
reason is a partition table, which is broken beyond repair, or simply
due to the incomplete image file...

> 
> A few more things to try:
> 
> To see what the kernel uses for a particular disk, you can run the
> following: cat /sys/block/sdb/queue/{physical,logical}_block_size
 

host:/home/user>cat /sys/block/sdb/queue/physical_block_size 
512
solfire:/home/user>cat /sys/block/sdb/queue/logical_block_size 
512
host:/home/user>

> fdisk takes 

Re: [gentoo-user] Getting rid of unwanted languages (Was: Re: gimp help not available, even with USE doc)

2020-04-30 Thread Peter Humphrey
On Thursday, 30 April 2020 16:43:06 BST Michael wrote:
> On Thursday, 30 April 2020 16:15:54 BST Dale wrote:
> > Dr Rainer Woitok wrote:
> > > On Thursday, 2020-04-30 07:31:51 -0500, Dale wrote:
> > >> ...
> > >> [ebuild   R] app-doc/gimp-help-2.8.2:2::gentoo  0 KiB
> > > 
> > > Thanks for pointing me to a package I hadn't yet installed,  even though
> > > I have installed "media-gfx/gimp" (but use it rarely).  But installation
> > > took surprisingly long  because it included tons of messages in unneeded
> > > laguages.   I have  L10N="en-GB"  in my "make.conf" file,  but this only
> > > seems to request additional languages.
> > > 
> > > Is there a way to exclude megabytes  of message texts or manual pages in
> > > languages I don't understand anyway from being installed, something like
> > > "L10N="-* en-GB"?   And is there a way to again remove unnecessary lang-
> > > uages after they have been installed?
> > > 
> > > Under Ubuntu I used to use a package named "localepurge" which did both.
> > > 
> > > Sincerely,
> > > 
> > >   Rainer
> > 
> > These settings are from AGES ago.  I think they are still in use tho.
> > 
> > 
> > root@fireball / # cat /etc/make.conf | grep lang
> > LANG="en_US"
> > root@fireball / # cat /etc/make.conf | grep L10N
> > L10N="en en-US"
> > root@fireball / #
> > 
> > You would replace US with GB of course.  Oh, I put a link from
> > /etc/make.conf to the real one.  I'm used to the old location. :/
> > 
> Unless this page is out of date L10N USE expansion variable can be set
> either at make.conf, or on a per package basis:
> 
> https://wiki.gentoo.org/wiki/Localization/Guide#L10N
> 
> Meanwhile, I think the equivalent to debian's localepurge corresponds to a
> dual step process in Gentoo.  First update your locale as per above page,
> then run 'env-update && source /etc/profile', followed by 'localegen'. 
> Then if you have also setup additional localisations in L10N, you need to
> run emerge with option --newuse, or --changeduse to take account per
> package or global changes in the L10N USE settings.

I wondered whether gimp would just include all manner of junk regardless, so I 
checked what's installed here. It seems that setting locales in make.conf does 
indeed help - no excess languages here; just 2600 icons!

-- 
Regards,
Peter.






Re: [gentoo-user] Getting rid of unwanted languages (Was: Re: gimp help not available, even with USE doc)

2020-04-30 Thread Michael
On Thursday, 30 April 2020 16:15:54 BST Dale wrote:
> Dr Rainer Woitok wrote:
> > Greetings,
> > 
> > On Thursday, 2020-04-30 07:31:51 -0500, Dale wrote:
> >> ...
> >> [ebuild   R] app-doc/gimp-help-2.8.2:2::gentoo  0 KiB
> > 
> > Thanks for pointing me to a package I hadn't yet installed,  even though
> > I have installed "media-gfx/gimp" (but use it rarely).  But installation
> > took surprisingly long  because it included tons of messages in unneeded
> > laguages.   I have  L10N="en-GB"  in my "make.conf" file,  but this only
> > seems to request additional languages.
> > 
> > Is there a way to exclude megabytes  of message texts or manual pages in
> > languages I don't understand anyway from being installed, something like
> > "L10N="-* en-GB"?   And is there a way to again remove unnecessary lang-
> > uages after they have been installed?
> > 
> > Under Ubuntu I used to use a package named "localepurge" which did both.
> > 
> > Sincerely,
> > 
> >   Rainer
> 
> These settings are from AGES ago.  I think they are still in use tho. 
> 
> 
> root@fireball / # cat /etc/make.conf | grep lang
> LANG="en_US"
> root@fireball / # cat /etc/make.conf | grep L10N
> L10N="en en-US"
> root@fireball / #
> 
> 
> You would replace US with GB of course.  Oh, I put a link from
> /etc/make.conf to the real one.  I'm used to the old location. :/ 
> 
> That help? 
> 
> Dale
> 
> :-)  :-) 

Unless this page is out of date L10N USE expansion variable can be set either 
at make.conf, or on a per package basis:

https://wiki.gentoo.org/wiki/Localization/Guide#L10N

Meanwhile, I think the equivalent to debian's localepurge corresponds to a 
dual step process in Gentoo.  First update your locale as per above page, then 
run 'env-update && source /etc/profile', followed by 'localegen'.  Then if you 
have also setup additional localisations in L10N, you need to run emerge with 
option --newuse, or --changeduse to take account per package or global changes 
in the L10N USE settings.


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Getting rid of unwanted languages (Was: Re: gimp help not available, even with USE doc)

2020-04-30 Thread Dale
Dr Rainer Woitok wrote:
> Greetings,
>
> On Thursday, 2020-04-30 07:31:51 -0500, Dale wrote:
>
>> ...
>> [ebuild   R    ] app-doc/gimp-help-2.8.2:2::gentoo  0 KiB
> Thanks for pointing me to a package I hadn't yet installed,  even though
> I have installed "media-gfx/gimp" (but use it rarely).  But installation
> took surprisingly long  because it included tons of messages in unneeded
> laguages.   I have  L10N="en-GB"  in my "make.conf" file,  but this only
> seems to request additional languages.
>
> Is there a way to exclude megabytes  of message texts or manual pages in
> languages I don't understand anyway from being installed, something like
> "L10N="-* en-GB"?   And is there a way to again remove unnecessary lang-
> uages after they have been installed?
>
> Under Ubuntu I used to use a package named "localepurge" which did both.
>
> Sincerely,
>   Rainer
>
>
>


These settings are from AGES ago.  I think they are still in use tho. 


root@fireball / # cat /etc/make.conf | grep lang
LANG="en_US"
root@fireball / # cat /etc/make.conf | grep L10N
L10N="en en-US"
root@fireball / #


You would replace US with GB of course.  Oh, I put a link from
/etc/make.conf to the real one.  I'm used to the old location. :/ 

That help? 

Dale

:-)  :-) 


[gentoo-user] Getting rid of unwanted languages (Was: Re: gimp help not available, even with USE doc)

2020-04-30 Thread Dr Rainer Woitok
Greetings,

On Thursday, 2020-04-30 07:31:51 -0500, Dale wrote:

> ...
> [ebuild   R    ] app-doc/gimp-help-2.8.2:2::gentoo  0 KiB

Thanks for pointing me to a package I hadn't yet installed,  even though
I have installed "media-gfx/gimp" (but use it rarely).  But installation
took surprisingly long  because it included tons of messages in unneeded
laguages.   I have  L10N="en-GB"  in my "make.conf" file,  but this only
seems to request additional languages.

Is there a way to exclude megabytes  of message texts or manual pages in
languages I don't understand anyway from being installed, something like
"L10N="-* en-GB"?   And is there a way to again remove unnecessary lang-
uages after they have been installed?

Under Ubuntu I used to use a package named "localepurge" which did both.

Sincerely,
  Rainer




Re: [gentoo-user] Trouble with backup harddisks

2020-04-30 Thread Andrea Conti

Hi,


CONFIG_PARTITION_ADVANCED=y
CONFIG_MSDOS_PARTITION=y
CONFIG_EFI_PARTITION=y


That's all you need.


This could be the key. Sector sizes have been changing from 512 to 4096
over many years. If your kernel has been updated to expect/use 4096 byte
sectors, it might not be able to read the disk properly.


Sector size is only a (fixed) property of a specific block device, not 
something expected or required by the kernel.
Sector sizes other than 512B have been around for ages without any problems, 
even in consumer hardware (e.g. CDs and DVDs have 2KB sectors).


Disklabel type: dos



Device Boot StartEndSectors   Size Id Type
/dev/sdb1   1 1953458175 1953458175 931.5G ee GPT


That looks... broken.
fdisk is recognizing the disk as MBR (a GPT disk would have "Disklabel type: 
gpt"), but the partition table is a protective MBR, which makes no sense in a 
non-GPT disk.

My guess is that this disk was at some time partitioned with GPT (possibly it 
came that way from WD?), but then it was only used in machines with no kernel 
support for GPT.
Such a machine will happily treat that as a normal MBR and allow you to access 
the protective entry as a normal partition, which means you can create a 
filesystem on it and fill it with data, destroying the GPT structures.

A GPT-aware kernel on the other hand will recognize that as a protective MBR 
and it will ignore it --but since the disk does not contain any valid GPT 
structures, it will not show any partitions.

Try running "gdisk -l /dev/sdb"; for a valid GPT disk it will say:

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

If that's not the case and you have no GPT, you will have to fix things 
manually.
Since the disk is only 1TB, there is no reason to use GPT at all, so your best 
bet is to use fdisk to make that a standard MBR by changing the partition type 
from 'ee' to '83'.

andrea



Re: [gentoo-user] prevent users from shutting down while other users logged in

2020-04-30 Thread Neil Bothwick
On Thu, 30 Apr 2020 09:19:15 +, Raffaele BELARDI wrote:

> > Can you configure the shutdown/reboot command called by XFCE? If so,
> > you can set it to a script that checks whether anyone else is logged
> > in before either executing the shutdown or displaying a "Daddy's
> > using the computer" dialog.  
>  
> I was hoping for a 'system' level solution.

Of course, I was suggesting this as a Plan B option.


-- 
Neil Bothwick

The considered application of terror is also a form of communication.


pgpEtv2zKD7Ai.pgp
Description: OpenPGP digital signature


Re: [gentoo-user] Trouble with backup harddisks

2020-04-30 Thread Wynn Wolf Arbor

Hi,

On 2020-04-30 13:17, Wols Lists wrote:

All I can suggest is to check the kernel and see if it's an option that
has been disabled (512-byte sectors, that is).


As far as I know the kernel still uses 512 bytes internally [1], and I 
do not recall having seen an option that enables or disables support for 
512/4K sectors.


That said, the problem may well be stemming from a sector size 
discrepancy, but as I understand it, it would have to do with how and 
when the partition table was created. That is, like described in [2], 
some USB enclosures seem to be a bit overzealous with obscure features, 
and might take eight disk sectors and bundle them together into one 4K 
sector.


If the disk was partitioned in the exact same enclosure, and is read 
from the exact same enclosure right now, there shouldn't be any 
problems. Is this the case, Meino?


Also, when did you last access the drives successfully, and with which 
system?


On 2020-04-30 11:32, Meino wrote:

Disk /dev/sdb: 931.49 GiB, 1000170586112 bytes, 1953458176 sectors
Disk model: Elements 25A2   
Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disklabel type: dos
Disk identifier: 0x16f2a91f

Device Boot StartEndSectors   Size Id Type
/dev/sdb1   1 1953458175 1953458175 931.5G ee GPT


Interestingly, this reads *exactly* like the Protective MBR [3] that GPT 
has. That is, the disklabel type is DOS whilst the partition ID is EE.  
There's a single partition that spans the entire drive (and it's also 
seemingly not aligned properly - usually you see Start at 2048).


As a comparison, here's the output from fdisk for the Protective MBR 
from one of my GPT drives:



Disklabel type: dos
Disk identifier: 0x



Device Boot StartEndSectors Size Id Type
/dev/sdc1   1 4294967295 4294967295   2T ee GPT


I'd assume that the missing disk identifier here is coming from 
different tools writing the protective MBR differently.


With that said, are you absolutely certain that you did not partition 
this drive with GPT instead of MBR? Did you do the partitioning in 
something like fdisk (which asks you specifically what you want), or 
some other application? Did you maybe format this drive on a Windows 
system?


I'm not one to discount entirely strange things happening, but I have 
never before seen a proper MBR laid out like a protective MBR. Indeed it 
would be quite impossible to have systems access data through such a 
table, since the partitions are hidden within that one huge contiguous 
block.


Ordinarily I'd point to fdisk not reading the partition table properly, 
but it seems that although your kernel has support for GPT, it doesn't 
seem to see the partitions either (assuming a proper GPT exists at all).

Do you have some other GPT drives you can access successfully?

I'd say that this requires some more forensic work. Perhaps extracting 
the first few megabytes of the disk and seeing whether there's a proper 
GPT or not. This would of course require manual work.


A few more things to try:

To see what the kernel uses for a particular disk, you can run the 
following: cat /sys/block/sdb/queue/{physical,logical}_block_size


fdisk takes a sector size with -b, --sector-size (should be 
non-destructive as long as you don't write anything, but I am not sure). 
Also, fdisk has a compatibility mode for dos with -c=dos. Might be worth 
a short.


fdisk should support GPT starting with util-linux 2.23, but you can also 
try gptfdisk (it's in the tree).


Hope this helps.

[1] https://github.com/torvalds/linux/blob/master/include/linux/types.h#L120
[2] 
https://superuser.com/questions/679725/how-to-correct-512-byte-sector-mbr-on-a-4096-byte-sector-disk/679800#679800
[3] https://en.wikipedia.org/wiki/GUID_Partition_Table#PROTECTIVE-MBR

--
Wolf



Re: [gentoo-user] Graphics Card Advice

2020-04-30 Thread Dale
Michael wrote:
> On Wednesday, 29 April 2020 23:48:28 BST jdm wrote:
>> On Thu, 30 Apr 2020 10:17:37 +0200
>>
>> tu...@posteo.de wrote:
>>> On 04/29 06:05, jdm wrote:
 Hi,

 I have just bought a RX 5600 XT and after a few issues with screen
 freezing after kernel starts loading, resolved by compiling EFIFB
 (no previous FB compiled in) the card has been working fine for 2
 days booting normally. The machine then started not to boot, not
 even to get to BIOS (so you couldn't even press DEL to get to BIOS
 screen). I took the card out and replaced with old card and PC
 started fine. I tried this 4 times and still with new card PC would
 not even POST. I don't have a little speaker to here if there are
 any beeps.

 I am returning the card as it feels like that is the problem but
 have a nagging suspicion this could be some other problem like
 power supply. I have 700W coolermaster PSU which should be ample
 (according to websites) but is 9 years (amazingly they had the
 foresight to provide 8 and 6 pin cables which were both plugged in).

 My next issue is do I get another 5600 XT (different brand) or are
 nvidia equivalent better? I have always been an AMD fan. Could I
 end up in the same boat.

 PC spec - ASUS 470 Pro MB with 2700 Ryzen.

 Any advice would be much appreciated?

 John
>>> Hi John,
>>>
>>> what graphicscard you want depends heavily on what you want to
>>> do with your PC...
>>> What are the tasks, which put a heavy load on your PC/graphicscard and
>>> which you are do regularily?
>>> Do you do a lot of rendering (Blender for example) or video
>>> (re-)encoding? Do you AI related things (tesorflow for example)?
>>> Or is gaming you main application?
>>>
>>> Furthermore: You CPU must fit your graphicscard performancewise.
>>> It makes no sense to choose "a performance beast" and to combine
>>> it with a "entry level being".
>>> The fastest graphicscard can onlu as fast, as data are coming from
>>> the CPU and vice versa.
>>>
>>> On the internet you find a combination of the Ryzen 5 3600 with
>>> one of the nvidia RTX 20[678] SUPER cards. The RTX 2060 SUPER
>>> comes with 8GByte of video ram instead of 6 GBYte of the RTX 2060.
>>>
>>> "Linus Tech Tipps" and "Tom's Hardware" are probablu to look for.
>>>
>>> HTH!
>>>
>>> Cheers!
>>> Meino
>> Thanks for advice.
>>
>> I like playing games and noticed with current card that FPS is low on a
>> lot of games.
>> I have tried to get a balance between not paying too much and specs of
>> monitor (2560x1440 @60 fps). According to GPU check I should get max of
>> 80 fps @ 1440. So thought I would have some left in the bank with 5600
>> XT.
>>
>> I'll check CPU to GPU rate.
>>
>> There's too much choice and now a little worried that next card might
>> not work again.
>>
>> John
> PSUs do not last forever and if you experience power surges, lightning, etc. 
> they could last even less.  More often than not some early degradation causes 
> random crashes, when under load, rather than complete blackout.  It is not 
> easy to test a PSU without an oscilloscope, but you could look at the MoBo 
> voltages with a multimeter to see if they're broadly within limits and don't 
> drop off too much when a load in placed them.
>
> Personally I don't bother measuring voltages.  If you take the PSU out of the 
> case and visually inspect its capacitors you may find some have domed tops, 
> an 
> indication they have overheated and are on their way out.  A few pennies 
> would 
> buy you a bag of replacements which you can solder in to restore the PSU to 
> its original performance.  It used to be Panasonic capacitors were better 
> made 
> and had higher ratings, but I don't know what brands can claim better quality 
> of manufacture these days.  Burned resistors are an indication of 
> catastrophic 
> surges, although I have replaced resistors and capacitors on a cheap PSU 
> which 
> burnt out when sheet lightning hit our area one year and worked fine for 
> years 
> after that.
>
> Of course, if the problem is with the video card, the PSU won't fix your 
> problem.


Just in case the OP, or someone else that wants to go down this road,
wants to repair this.  This is the list I go by.  Link first, then list
of top tier in case one wants to skip reading the whole thing.


https://www.tomshardware.com/reviews/power-supplies-101,4193-5.html


All Japanese caps are considered of high quality, and we like to see the
following cap brands:

  * Rubycon
  * United Chemi-Con (or Nippon Chemi-Con)
  * Nichicon
  * Sanyo/Suncon
  * Panasonic
  * Hitachi
  * FPCAP or Functional Polymer Capacitor (ex-Fujitsu caps segment,
which was bought by Nichicon)
  * ELNA

Besides Japanese manufacturers there are also several US and European
vendors that make high-quality capacitors. Probably we won't meet any of
the below cap brands inside a consumer grade PSU, at least their

Re: [gentoo-user] gimp help not available, even with USE doc

2020-04-30 Thread Dale
n952162 wrote:
>
> After emerging gimp, I tried to get help (after re-emerging with the
> doc USE flag), and got this:
>
> /Could not open 'https://docs.gimp.org/2.10/en/gimp-help.xml' for
> reading: Operation not supported//
> //
> //Perhaps you are missing GIO backends and need to install GVFS?/
>
> Is there anything I can do?
>
>


When I open GIMP and go to help, it takes me here: 

file:///usr/share/gimp/2.0/help/en/index.html

It opens in Seamonkey for me.  Seamonkey is set as my default browser. 
This is my USE flag settings.



root@fireball / # emerge -pv app-doc/gimp-help media-gfx/gimp

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] app-doc/gimp-help-2.8.2:2::gentoo  0 KiB
[ebuild   R   ~] media-gfx/gimp-2.10.18-r1:2::gentoo  USE="alsa doc
jpeg2k mng python udev wmf -aalib (-aqua) -debug -gnome -heif -openexr
-postscript -test -unwind -vector-icons -webp -xpm" CPU_FLAGS_X86="mmx
sse" PYTHON_SINGLE_TARGET="python2_7" 0 KiB

Total: 2 packages (2 reinstalls), Size of downloads: 0 KiB
root@fireball / #


Do you have the gimp-help package installed?  If so, your USE flags
match mine? 

Dale

:-)  :-) 


Re: [gentoo-user] Trouble with backup harddisks

2020-04-30 Thread Wols Lists
On 30/04/20 11:36, tu...@posteo.de wrote:
> But than I have the same problem another way around: I can
> no longer access my new system ... due to the different 
> sector size
> 
> Are there any other ways to fix this problem?

All I can suggest is to check the kernel and see if it's an option that
has been disabled (512-byte sectors, that is).

Cheers,
Wol



Re: [gentoo-user] Graphics Card Advice

2020-04-30 Thread Michael
On Wednesday, 29 April 2020 23:48:28 BST jdm wrote:
> On Thu, 30 Apr 2020 10:17:37 +0200
> 
> tu...@posteo.de wrote:
> > On 04/29 06:05, jdm wrote:
> > > Hi,
> > > 
> > > I have just bought a RX 5600 XT and after a few issues with screen
> > > freezing after kernel starts loading, resolved by compiling EFIFB
> > > (no previous FB compiled in) the card has been working fine for 2
> > > days booting normally. The machine then started not to boot, not
> > > even to get to BIOS (so you couldn't even press DEL to get to BIOS
> > > screen). I took the card out and replaced with old card and PC
> > > started fine. I tried this 4 times and still with new card PC would
> > > not even POST. I don't have a little speaker to here if there are
> > > any beeps.
> > > 
> > > I am returning the card as it feels like that is the problem but
> > > have a nagging suspicion this could be some other problem like
> > > power supply. I have 700W coolermaster PSU which should be ample
> > > (according to websites) but is 9 years (amazingly they had the
> > > foresight to provide 8 and 6 pin cables which were both plugged in).
> > > 
> > > My next issue is do I get another 5600 XT (different brand) or are
> > > nvidia equivalent better? I have always been an AMD fan. Could I
> > > end up in the same boat.
> > > 
> > > PC spec - ASUS 470 Pro MB with 2700 Ryzen.
> > > 
> > > Any advice would be much appreciated?
> > > 
> > > John
> > 
> > Hi John,
> > 
> > what graphicscard you want depends heavily on what you want to
> > do with your PC...
> > What are the tasks, which put a heavy load on your PC/graphicscard and
> > which you are do regularily?
> > Do you do a lot of rendering (Blender for example) or video
> > (re-)encoding? Do you AI related things (tesorflow for example)?
> > Or is gaming you main application?
> > 
> > Furthermore: You CPU must fit your graphicscard performancewise.
> > It makes no sense to choose "a performance beast" and to combine
> > it with a "entry level being".
> > The fastest graphicscard can onlu as fast, as data are coming from
> > the CPU and vice versa.
> > 
> > On the internet you find a combination of the Ryzen 5 3600 with
> > one of the nvidia RTX 20[678] SUPER cards. The RTX 2060 SUPER
> > comes with 8GByte of video ram instead of 6 GBYte of the RTX 2060.
> > 
> > "Linus Tech Tipps" and "Tom's Hardware" are probablu to look for.
> > 
> > HTH!
> > 
> > Cheers!
> > Meino
> 
> Thanks for advice.
> 
> I like playing games and noticed with current card that FPS is low on a
> lot of games.
> I have tried to get a balance between not paying too much and specs of
> monitor (2560x1440 @60 fps). According to GPU check I should get max of
> 80 fps @ 1440. So thought I would have some left in the bank with 5600
> XT.
> 
> I'll check CPU to GPU rate.
> 
> There's too much choice and now a little worried that next card might
> not work again.
> 
> John

PSUs do not last forever and if you experience power surges, lightning, etc. 
they could last even less.  More often than not some early degradation causes 
random crashes, when under load, rather than complete blackout.  It is not 
easy to test a PSU without an oscilloscope, but you could look at the MoBo 
voltages with a multimeter to see if they're broadly within limits and don't 
drop off too much when a load in placed them.

Personally I don't bother measuring voltages.  If you take the PSU out of the 
case and visually inspect its capacitors you may find some have domed tops, an 
indication they have overheated and are on their way out.  A few pennies would 
buy you a bag of replacements which you can solder in to restore the PSU to 
its original performance.  It used to be Panasonic capacitors were better made 
and had higher ratings, but I don't know what brands can claim better quality 
of manufacture these days.  Burned resistors are an indication of catastrophic 
surges, although I have replaced resistors and capacitors on a cheap PSU which 
burnt out when sheet lightning hit our area one year and worked fine for years 
after that.

Of course, if the problem is with the video card, the PSU won't fix your 
problem.


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] prevent users from shutting down while other users logged in

2020-04-30 Thread Michael
On Thursday, 30 April 2020 10:19:15 BST Raffaele BELARDI wrote:
> > > Basically I'd like that:
> > > - if there is more than one user logged in, either locally via lighdm
> > > or remotely via SSH, the shutdown XFCE button is grayed out. Once all
> > > users except one have logged out, the button is again available
> > 
> > Can you configure the shutdown/reboot command called by XFCE? If so, you
> > can set it to a script that checks whether anyone else is logged in before
> > either executing the shutdown or displaying a "Daddy's using the computer"
> > dialog.
> 
> I was hoping for a 'system' level solution. I think it was consolekit that,
> when a user tried to shutdown while another user was logged presented a
> window asking for root password to execute the command. (ESC would let it
> continue and do the shutdown anyway, so it was not really working). I'll go
> for the manual way.
> 
> Thanks,
> 
> Raffaele

Yes, I recall the same, in particular when logged in on a console, or remotely 
over SSH, but I don't think I have not observed it on KDE/Plasma desktops for 
a while now.  Mind you, I have moved to elogind, so this may manage seats and 
signals differently.

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Graphics Card Advice

2020-04-30 Thread jdm
On Thu, 30 Apr 2020 10:17:37 +0200
tu...@posteo.de wrote:

> On 04/29 06:05, jdm wrote:
> > Hi,
> > 
> > I have just bought a RX 5600 XT and after a few issues with screen
> > freezing after kernel starts loading, resolved by compiling EFIFB
> > (no previous FB compiled in) the card has been working fine for 2
> > days booting normally. The machine then started not to boot, not
> > even to get to BIOS (so you couldn't even press DEL to get to BIOS
> > screen). I took the card out and replaced with old card and PC
> > started fine. I tried this 4 times and still with new card PC would
> > not even POST. I don't have a little speaker to here if there are
> > any beeps.
> > 
> > I am returning the card as it feels like that is the problem but
> > have a nagging suspicion this could be some other problem like
> > power supply. I have 700W coolermaster PSU which should be ample
> > (according to websites) but is 9 years (amazingly they had the
> > foresight to provide 8 and 6 pin cables which were both plugged in).
> > 
> > My next issue is do I get another 5600 XT (different brand) or are
> > nvidia equivalent better? I have always been an AMD fan. Could I
> > end up in the same boat.
> > 
> > PC spec - ASUS 470 Pro MB with 2700 Ryzen.
> > 
> > Any advice would be much appreciated?
> > 
> > John
> >   
> 
> Hi John,
> 
> what graphicscard you want depends heavily on what you want to
> do with your PC...
> What are the tasks, which put a heavy load on your PC/graphicscard and
> which you are do regularily?
> Do you do a lot of rendering (Blender for example) or video
> (re-)encoding? Do you AI related things (tesorflow for example)?
> Or is gaming you main application?
> 
> Furthermore: You CPU must fit your graphicscard performancewise.
> It makes no sense to choose "a performance beast" and to combine
> it with a "entry level being".
> The fastest graphicscard can onlu as fast, as data are coming from
> the CPU and vice versa.
> 
> On the internet you find a combination of the Ryzen 5 3600 with
> one of the nvidia RTX 20[678] SUPER cards. The RTX 2060 SUPER
> comes with 8GByte of video ram instead of 6 GBYte of the RTX 2060.
> 
> "Linus Tech Tipps" and "Tom's Hardware" are probablu to look for.
> 
> HTH!
> 
> Cheers!
> Meino
> 
> 

Thanks for advice.

I like playing games and noticed with current card that FPS is low on a
lot of games.
I have tried to get a balance between not paying too much and specs of
monitor (2560x1440 @60 fps). According to GPU check I should get max of
80 fps @ 1440. So thought I would have some left in the bank with 5600
XT.

I'll check CPU to GPU rate.

There's too much choice and now a little worried that next card might
not work again.

John



Re: [gentoo-user] Trouble with backup harddisks

2020-04-30 Thread tuxic
On 04/30 10:55, Wols Lists wrote:
> On 30/04/20 10:32, tu...@posteo.de wrote:
> > Hi,
> > 
> > recently I switched from the old MBR-scheme to GPT on
> > my new PC.
> > 
> > I have two external USB-harddisk, which were partioned/formatted with
> > a MBR-scheme/MSDOS partition (but were never used to boot from. They are 
> > pure
> > data containers).
> > 
> > When I connect these to my new PC, only the device is shown:
> > /dev/sdb, /dev/sdc.
> > 
> > The kernel is configured (beside other things) as follows:
> > 
> > #
> > # Partition Types
> > #
> > CONFIG_PARTITION_ADVANCED=y
> > # CONFIG_ACORN_PARTITION is not set
> > # CONFIG_AIX_PARTITION is not set
> > # CONFIG_OSF_PARTITION is not set
> > # CONFIG_AMIGA_PARTITION is not set
> > # CONFIG_ATARI_PARTITION is not set
> > # CONFIG_MAC_PARTITION is not set
> > CONFIG_MSDOS_PARTITION=y
> > # CONFIG_BSD_DISKLABEL is not set
> > # CONFIG_MINIX_SUBPARTITION is not set
> > # CONFIG_SOLARIS_X86_PARTITION is not set
> > # CONFIG_UNIXWARE_DISKLABEL is not set
> > # CONFIG_LDM_PARTITION is not set
> > # CONFIG_SGI_PARTITION is not set
> > # CONFIG_ULTRIX_PARTITION is not set
> > # CONFIG_SUN_PARTITION is not set
> > # CONFIG_KARMA_PARTITION is not set
> > CONFIG_EFI_PARTITION=y
> > # CONFIG_SYSV68_PARTITION is not set
> > # CONFIG_CMDLINE_PARTITION is not set
> > # end of Partition Types
> > 
> > CONFIG_BLOCK_COMPAT=y
> > CONFIG_BLK_MQ_PCI=y
> > CONFIG_BLK_MQ_VIRTIO=y
> > CONFIG_BLK_PM=y
> > 
> > dmesg shows this:
> > [14617.672363] usb 2-2: New USB device found, idVendor=1058, 
> > idProduct=25a2, bcdDevice=10.21
> > [14617.672364] usb 2-2: New USB device strings: Mfr=1, Product=2, 
> > SerialNumber=3
> > [14617.672364] usb 2-2: Product: Elements 25A2
> > [14617.672365] usb 2-2: Manufacturer: Western Digital
> > [14617.672366] usb 2-2: SerialNumber: 575844314132383959393934
> > [14617.681660] usb-storage 2-2:1.0: USB Mass Storage device detected
> > [14617.681737] scsi host10: usb-storage 2-2:1.0
> > [14618.725450] scsi 10:0:0:0: Direct-Access WD   Elements 25A2
> > 1021 PQ: 0 ANSI: 6
> > [14618.725594] sd 10:0:0:0: Attached scsi generic sg1 type 0
> > [14618.728090] sd 10:0:0:0: [sdb] Spinning up disk...
> > [14619.748918] ...ready
> > 
> > I tried different USB ports in a desperate hope of success...
> > ...no, same problem.
> > 
> > Interestingly fdisk shows the following:
> > 
> > host> sudo fdisk -l /dev/sdb
> > Disk /dev/sdb: 931.49 GiB, 1000170586112 bytes, 1953458176 sectors
> > Disk model: Elements 25A2   
> > Units: sectors of 1 * 512 = 512 bytes
> > Sector size (logical/physical): 512 bytes / 512 bytes
> > I/O size (minimum/optimal): 512 bytes / 512 bytes
> 
> This could be the key. Sector sizes have been changing from 512 to 4096
> over many years. If your kernel has been updated to expect/use 4096 byte
> sectors, it might not be able to read the disk properly.
> 
> > Disklabel type: dos
> > Disk identifier: 0x16f2a91f
> > 
> > Device Boot StartEndSectors   Size Id Type
> > /dev/sdb1   1 1953458175 1953458175 931.5G ee GPT
> > 
> > The type is shown as GPT...but the drive has a MSDOS partition table.
> > 
> > Reading my (old) internal harddrive with an external USB docking
> > station is possible without any problems, though.
> > 
> > Unfortunatelu I have no space for 1T image of that drive -- otherwise
> > I would have made an image copy and experiment with that.
> > 
> > So better ask, than sorry ;)
> > 
> > Is this fixable or did I lost my backups?
> > 
> Do you have access to an old kernel?
> 
> The other thing is try using gdisk (or that could be fdisk under another
> name :-( But some partitioning schemes can write a GPT with protective
> MBR - if you can find something that will take the MBR and write it as a
> GPT that might help, too.
> 
> Cheers,
> Wol
> 

Hi Wol,

thank you for your posting! :)

I switched to my new PC around 31.3.2020...
so there is no change "over the years" involved here...I think.
Where in the kernel this update is made?
I cannot remember to have configured such a thing manually...

Changing the partitiontable in any way is risky to the data 
I think...I am very unsure to do this.

I have access to an old kernel / system and can boot it.

But than I have the same problem another way around: I can
no longer access my new system ... due to the different 
sector size

Are there any other ways to fix this problem?

Cheers!
Meino







[gentoo-user] gimp help not available, even with USE doc

2020-04-30 Thread n952162

After emerging gimp, I tried to get help (after re-emerging with the doc
USE flag), and got this:

   /Could not open 'https://docs.gimp.org/2.10/en/gimp-help.xml' for
   reading: Operation not supported//
   //
   //Perhaps you are missing GIO backends and need to install GVFS?/

Is there anything I can do?




Re: [gentoo-user] Trouble with backup harddisks

2020-04-30 Thread Wols Lists
On 30/04/20 10:32, tu...@posteo.de wrote:
> Hi,
> 
> recently I switched from the old MBR-scheme to GPT on
> my new PC.
> 
> I have two external USB-harddisk, which were partioned/formatted with
> a MBR-scheme/MSDOS partition (but were never used to boot from. They are pure
> data containers).
> 
> When I connect these to my new PC, only the device is shown:
> /dev/sdb, /dev/sdc.
> 
> The kernel is configured (beside other things) as follows:
> 
> #
> # Partition Types
> #
> CONFIG_PARTITION_ADVANCED=y
> # CONFIG_ACORN_PARTITION is not set
> # CONFIG_AIX_PARTITION is not set
> # CONFIG_OSF_PARTITION is not set
> # CONFIG_AMIGA_PARTITION is not set
> # CONFIG_ATARI_PARTITION is not set
> # CONFIG_MAC_PARTITION is not set
> CONFIG_MSDOS_PARTITION=y
> # CONFIG_BSD_DISKLABEL is not set
> # CONFIG_MINIX_SUBPARTITION is not set
> # CONFIG_SOLARIS_X86_PARTITION is not set
> # CONFIG_UNIXWARE_DISKLABEL is not set
> # CONFIG_LDM_PARTITION is not set
> # CONFIG_SGI_PARTITION is not set
> # CONFIG_ULTRIX_PARTITION is not set
> # CONFIG_SUN_PARTITION is not set
> # CONFIG_KARMA_PARTITION is not set
> CONFIG_EFI_PARTITION=y
> # CONFIG_SYSV68_PARTITION is not set
> # CONFIG_CMDLINE_PARTITION is not set
> # end of Partition Types
> 
> CONFIG_BLOCK_COMPAT=y
> CONFIG_BLK_MQ_PCI=y
> CONFIG_BLK_MQ_VIRTIO=y
> CONFIG_BLK_PM=y
> 
> dmesg shows this:
> [14617.672363] usb 2-2: New USB device found, idVendor=1058, idProduct=25a2, 
> bcdDevice=10.21
> [14617.672364] usb 2-2: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
> [14617.672364] usb 2-2: Product: Elements 25A2
> [14617.672365] usb 2-2: Manufacturer: Western Digital
> [14617.672366] usb 2-2: SerialNumber: 575844314132383959393934
> [14617.681660] usb-storage 2-2:1.0: USB Mass Storage device detected
> [14617.681737] scsi host10: usb-storage 2-2:1.0
> [14618.725450] scsi 10:0:0:0: Direct-Access WD   Elements 25A2
> 1021 PQ: 0 ANSI: 6
> [14618.725594] sd 10:0:0:0: Attached scsi generic sg1 type 0
> [14618.728090] sd 10:0:0:0: [sdb] Spinning up disk...
> [14619.748918] ...ready
> 
> I tried different USB ports in a desperate hope of success...
> ...no, same problem.
> 
> Interestingly fdisk shows the following:
> 
> host> sudo fdisk -l /dev/sdb
> Disk /dev/sdb: 931.49 GiB, 1000170586112 bytes, 1953458176 sectors
> Disk model: Elements 25A2   
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes

This could be the key. Sector sizes have been changing from 512 to 4096
over many years. If your kernel has been updated to expect/use 4096 byte
sectors, it might not be able to read the disk properly.

> Disklabel type: dos
> Disk identifier: 0x16f2a91f
> 
> Device Boot StartEndSectors   Size Id Type
> /dev/sdb1   1 1953458175 1953458175 931.5G ee GPT
> 
> The type is shown as GPT...but the drive has a MSDOS partition table.
> 
> Reading my (old) internal harddrive with an external USB docking
> station is possible without any problems, though.
> 
> Unfortunatelu I have no space for 1T image of that drive -- otherwise
> I would have made an image copy and experiment with that.
> 
> So better ask, than sorry ;)
> 
> Is this fixable or did I lost my backups?
> 
Do you have access to an old kernel?

The other thing is try using gdisk (or that could be fdisk under another
name :-( But some partitioning schemes can write a GPT with protective
MBR - if you can find something that will take the MBR and write it as a
GPT that might help, too.

Cheers,
Wol




[gentoo-user] Trouble with backup harddisks

2020-04-30 Thread tuxic
Hi,

recently I switched from the old MBR-scheme to GPT on
my new PC.

I have two external USB-harddisk, which were partioned/formatted with
a MBR-scheme/MSDOS partition (but were never used to boot from. They are pure
data containers).

When I connect these to my new PC, only the device is shown:
/dev/sdb, /dev/sdc.

The kernel is configured (beside other things) as follows:

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_AIX_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not set
CONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
# CONFIG_CMDLINE_PARTITION is not set
# end of Partition Types

CONFIG_BLOCK_COMPAT=y
CONFIG_BLK_MQ_PCI=y
CONFIG_BLK_MQ_VIRTIO=y
CONFIG_BLK_PM=y

dmesg shows this:
[14617.672363] usb 2-2: New USB device found, idVendor=1058, idProduct=25a2, 
bcdDevice=10.21
[14617.672364] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[14617.672364] usb 2-2: Product: Elements 25A2
[14617.672365] usb 2-2: Manufacturer: Western Digital
[14617.672366] usb 2-2: SerialNumber: 575844314132383959393934
[14617.681660] usb-storage 2-2:1.0: USB Mass Storage device detected
[14617.681737] scsi host10: usb-storage 2-2:1.0
[14618.725450] scsi 10:0:0:0: Direct-Access WD   Elements 25A21021 
PQ: 0 ANSI: 6
[14618.725594] sd 10:0:0:0: Attached scsi generic sg1 type 0
[14618.728090] sd 10:0:0:0: [sdb] Spinning up disk...
[14619.748918] ...ready

I tried different USB ports in a desperate hope of success...
...no, same problem.

Interestingly fdisk shows the following:

host> sudo fdisk -l /dev/sdb
Disk /dev/sdb: 931.49 GiB, 1000170586112 bytes, 1953458176 sectors
Disk model: Elements 25A2   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x16f2a91f

Device Boot StartEndSectors   Size Id Type
/dev/sdb1   1 1953458175 1953458175 931.5G ee GPT

The type is shown as GPT...but the drive has a MSDOS partition table.

Reading my (old) internal harddrive with an external USB docking
station is possible without any problems, though.

Unfortunatelu I have no space for 1T image of that drive -- otherwise
I would have made an image copy and experiment with that.

So better ask, than sorry ;)

Is this fixable or did I lost my backups?

Cheers!
Meino










RE: [gentoo-user] prevent users from shutting down while other users logged in

2020-04-30 Thread Raffaele BELARDI
> > Basically I'd like that:
> > - if there is more than one user logged in, either locally via lighdm
> > or remotely via SSH, the shutdown XFCE button is grayed out. Once all
> > users except one have logged out, the button is again available
> 
> Can you configure the shutdown/reboot command called by XFCE? If so, you
> can set it to a script that checks whether anyone else is logged in before
> either executing the shutdown or displaying a "Daddy's using the computer"
> dialog.
 
I was hoping for a 'system' level solution. I think it was consolekit that, 
when a user tried to shutdown while another user was logged presented a window 
asking for root password to execute the command. (ESC would let it continue and 
do the shutdown anyway, so it was not really working). I'll go for the manual 
way.

Thanks,

Raffaele



[gentoo-user] Re: Problem understanding "eix"

2020-04-30 Thread Dr Rainer Woitok
Martin,

On Friday, 2020-04-24 17:32:09 -, you wrote:

> ...
> Maybe you run an unstable system, that is ACCEPT_KEYWORDS='~amd64'?

No.

> Or do you have a corresponding entry in package.{accept_,}keywords?

Yes.  To satisfy the requirements of package "sys-apps/fwupd" I long ago
added the line

   >=app-crypt/tpm2-tss-2.2.3-r1 ~amd64

But this only means  that I accept  an unstable  package here,  not that
these versions  are regarded stable.   After all,  the property is named
"{isstable}" and not "{isaccepted}".

Sincerely,
  Rainer



Re: [gentoo-user] Graphics Card Advice

2020-04-30 Thread tuxic
On 04/29 06:05, jdm wrote:
> Hi,
> 
> I have just bought a RX 5600 XT and after a few issues with screen
> freezing after kernel starts loading, resolved by compiling EFIFB (no
> previous FB compiled in) the card has been working fine for 2 days
> booting normally. The machine then started not to boot, not even to get
> to BIOS (so you couldn't even press DEL to get to BIOS screen). I took
> the card out and replaced with old card and PC started fine. I tried
> this 4 times and still with new card PC would not even POST. I don't
> have a little speaker to here if there are any beeps.
> 
> I am returning the card as it feels like that is the problem but have a
> nagging suspicion this could be some other problem like power supply. I
> have 700W coolermaster PSU which should be ample (according to websites)
> but is 9 years (amazingly they had the foresight to provide 8 and 6 pin
> cables which were both plugged in).
> 
> My next issue is do I get another 5600 XT (different brand) or are
> nvidia equivalent better? I have always been an AMD fan. Could I end up
> in the same boat.
> 
> PC spec - ASUS 470 Pro MB with 2700 Ryzen.
> 
> Any advice would be much appreciated?
> 
> John
> 

Hi John,

what graphicscard you want depends heavily on what you want to
do with your PC...
What are the tasks, which put a heavy load on your PC/graphicscard and
which you are do regularily?
Do you do a lot of rendering (Blender for example) or video
(re-)encoding? Do you AI related things (tesorflow for example)?
Or is gaming you main application?

Furthermore: You CPU must fit your graphicscard performancewise.
It makes no sense to choose "a performance beast" and to combine
it with a "entry level being".
The fastest graphicscard can onlu as fast, as data are coming from
the CPU and vice versa.

On the internet you find a combination of the Ryzen 5 3600 with
one of the nvidia RTX 20[678] SUPER cards. The RTX 2060 SUPER
comes with 8GByte of video ram instead of 6 GBYte of the RTX 2060.

"Linus Tech Tipps" and "Tom's Hardware" are probablu to look for.

HTH!

Cheers!
Meino




Re: [gentoo-user] transparent compression? (e.g. device mapper for compression)

2020-04-30 Thread Caveman Al Toraboran
On Thursday, April 30, 2020 9:59 AM, Adam Carter  wrote:

> https://btrfs.wiki.kernel.org/index.php/Compression

oo.  thanks, but my mistake.  i should've
clarified better.

i'm looking for a solution that works nicely with
ext4.  ideally i am thinking of a device mapper
solution.

e.g. we got a device mapper for encryption
(dm-crypt), but i think we lack one for
compression.




Re: [gentoo-user] transparent compression? (e.g. device mapper for compression)

2020-04-30 Thread Adam Carter
On Thu, Apr 30, 2020 at 1:24 PM Caveman Al Toraboran <
toraboracave...@protonmail.com> wrote:

> hi - any nice way to have compression at the file
> system level, without using zfs?  perhaps some
> kind of device mapper that compresses data?
>
> i find file system compression to speed up
> read/write to slow disks noticeably (e.g. sata).
>

https://btrfs.wiki.kernel.org/index.php/Compression