does my posting from this morning reached you ?
...I did not received anything back from the mailinglist...
Nope. Just this night's response to Wol.
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 depi
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
>
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
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 th
> 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 likel
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 t
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_
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
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
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 th
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//
> //
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
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
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
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
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
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 kern
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 poin
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, eve
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
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 lon
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
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"
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
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, res
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
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
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 compi
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 i
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 workin
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
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 anythin
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).
>
>
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:
> > 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 cal
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
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 b
38 matches
Mail list logo
