On Tuesday, December 15, 2020 8:08:46 AM CET bobwxc wrote:
> 在 2020/12/15 下午2:59, the...@sys-concept.com 写道:
> > On 12/14/2020 11:50 PM, J. Roeleveld wrote:
> >> On Tuesday, December 15, 2020 7:17:57 AM CET the...@sys-concept.com
wrote:
> >>> On 12/14/2020 06:21 PM, the...@sys-concept.com wrote:
在 2020/12/15 下午2:59, the...@sys-concept.com 写道:
On 12/14/2020 11:50 PM, J. Roeleveld wrote:
On Tuesday, December 15, 2020 7:17:57 AM CET the...@sys-concept.com wrote:
On 12/14/2020 06:21 PM, the...@sys-concept.com wrote:
By mistake on new installation I untar wrong: stage-3 x86_64 instead of
On 12/14/2020 11:50 PM, J. Roeleveld wrote:
> On Tuesday, December 15, 2020 7:17:57 AM CET the...@sys-concept.com wrote:
>> On 12/14/2020 06:21 PM, the...@sys-concept.com wrote:
>>> By mistake on new installation I untar wrong: stage-3 x86_64 instead of
>>> i686
>>>
>>> during kernel compiling I
On 15/12/2020 03:21, the...@sys-concept.com wrote:
By mistake on new installation I untar wrong: stage-3 x86_64 instead of
i686
during kernel compiling I got:
cc1: error: CPU you selected does not support x86-64 instruction set
Is it possible to untar new stage-3 (i686) over current one, or
On Tuesday, December 15, 2020 7:17:57 AM CET the...@sys-concept.com wrote:
> On 12/14/2020 06:21 PM, the...@sys-concept.com wrote:
> > By mistake on new installation I untar wrong: stage-3 x86_64 instead of
> > i686
> >
> > during kernel compiling I got:
> > cc1: error: CPU you selected does not
在 2020/12/15 下午2:33, the...@sys-concept.com 写道:
On 12/14/2020 11:17 PM, the...@sys-concept.com wrote:
On 12/14/2020 06:21 PM, the...@sys-concept.com wrote:
By mistake on new installation I untar wrong: stage-3 x86_64 instead of
i686
during kernel compiling I got:
cc1: error: CPU you selected
On 12/14/2020 11:17 PM, the...@sys-concept.com wrote:
> On 12/14/2020 06:21 PM, the...@sys-concept.com wrote:
>>
>> By mistake on new installation I untar wrong: stage-3 x86_64 instead of
>> i686
>>
>> during kernel compiling I got:
>> cc1: error: CPU you selected does not support x86-64
On 12/14/2020 06:21 PM, the...@sys-concept.com wrote:
>
> By mistake on new installation I untar wrong: stage-3 x86_64 instead of
> i686
>
> during kernel compiling I got:
> cc1: error: CPU you selected does not support x86-64 instruction set
>
> Is it possible to untar new stage-3 (i686) over
On 12/14/2020 09:38 PM, J. Roeleveld wrote:
> On 15 December 2020 02:21:22 CET, the...@sys-concept.com wrote:
>>
>> By mistake on new installation I untar wrong: stage-3 x86_64 instead
>> of
>> i686
>>
>> during kernel compiling I got:
>> cc1: error: CPU you selected does not support x86-64
On 15 December 2020 02:21:22 CET, the...@sys-concept.com wrote:
>
>By mistake on new installation I untar wrong: stage-3 x86_64 instead
>of
>i686
>
>during kernel compiling I got:
>cc1: error: CPU you selected does not support x86-64 instruction set
>
>Is it possible to untar new stage-3 (i686)
By mistake on new installation I untar wrong: stage-3 x86_64 instead of
i686
during kernel compiling I got:
cc1: error: CPU you selected does not support x86-64 instruction set
Is it possible to untar new stage-3 (i686) over current one, or I need
to delete all the folders?
On 12/14/20 10:55 AM, Walter Dnes wrote:
I ordered a Dell XPS 8940 which arrived in October, but life got in
the way, and I'm only now getting around to setting it up. First thing
I noticed today is that Dell "had the courage to remove the VGA port"
. It has HDMI and Displayport. I've got
在 2020/12/15 上午3:38, the...@sys-concept.com 写道:
I'm having similar problem as "n952162" upgrading an old (last updated
1.8-year ago)
It sync OK, updated the profile.
Looking instruction on this page:
https://wiki.gentoo.org/wiki/Upgrading_Gentoo
root #mv /usr/portage /usr/portage.latest
root
On 14/12/2020 22:35, Neil Bothwick wrote:
On Mon, 14 Dec 2020 15:18:19 -0700, the...@sys-concept.com wrote:
Moving forward like a snail.
Unmerged portage to local directory and running:
./portage-portage-3.0.12/bin/emerge -1 portage
gives me two blockers:
[blocks B ]
Probably not. It
On 12/14/2020 02:03 AM, Michael wrote:
> On Monday, 14 December 2020 00:27:03 GMT the...@sys-concept.com wrote:
>> On 12/13/2020 04:44 PM, Michael wrote:
>>> On Sunday, 13 December 2020 18:52:51 GMT the...@sys-concept.com wrote:
I have "nouveau" build into kernel but it doesn't work:
On 2020-12-14, antlists wrote:
> What I would do is find out whatever -march fits the oldest chip, and
> then set that for all the machines. Especially if, as you say, they're
> all AMD the chances are the newer chips will be a superset of the old,
FWIW, that's not always the case.
On 14/12/2020 18:55, Walter Dnes wrote:
But I want to attach the XPS 8940 to the older monitor, which only has
VGA and DVI-D. I use the older monitor for setup/install and to keep
the "hot backup" machine up-to-date. What are my options? For the main
machine I'll buy an HDMI cable. Are
On 14/12/2020 12:55, n952162 wrote:
On 12/14/20 11:17 AM, Wols Lists wrote:
On 14/12/20 08:51, Dale wrote:
If you are able, maybe you can compile the bigger packages on a faster
system? If it is a option, it may help.
If I have multiple similar machines, I create a shared a shared local
On Monday, 14 December 2020 19:30:32 GMT Neil Bothwick wrote:
> On Mon, 14 Dec 2020 10:07:37 +, Michael wrote:
> > > This shows that you have 20201022-r3 installed but eix says the latest
> > > available is 20201022-r2 so you have a version it thinks is not in the
> > > tree.
> > >
> > > Did
On Mon, 14 Dec 2020 15:18:19 -0700, the...@sys-concept.com wrote:
> Moving forward like a snail.
> Unmerged portage to local directory and running:
> ./portage-portage-3.0.12/bin/emerge -1 portage
>
> gives me two blockers:
> [blocks B ] (" [blocks B ] <=dev-lang/python-2.7.18-r3:2.7
On 12/14/2020 02:55 PM, Grant Edwards wrote:
> On 2020-12-14, the...@sys-concept.com wrote:
>> I'm having similar problem as "n952162" upgrading an old (last updated
>> 1.8-year ago)
>
> If I were youe, I'd just reinstall after 1.8 years. Updating is going
> to take way, way more work.
>
> --
>
On 12/14/2020 02:58 PM, Arve Barsnes wrote:
> On Mon, 14 Dec 2020 at 22:20, wrote:
>> Looking at this directory:
>> https://github.com/gentoo/portage/releases/tag/portage-3.0.12
>>
>> file: portage-portage-3.0.12.tar.gz has totally different structure
>> If I run: tar xzf
On 2020-12-14, the...@sys-concept.com wrote:
> I'm having similar problem as "n952162" upgrading an old (last updated
> 1.8-year ago)
If I were youe, I'd just reinstall after 1.8 years. Updating is going
to take way, way more work.
--
Grant
On Mon, 14 Dec 2020 at 22:20, wrote:
> Looking at this directory:
> https://github.com/gentoo/portage/releases/tag/portage-3.0.12
>
> file: portage-portage-3.0.12.tar.gz has totally different structure
> If I run: tar xzf portage-portage-3.0.12.tar.gz -C /usr
> it will create directory
[snip]
emerge --update --oneshot portage
!!! All ebuilds that could satisfy
">=app-crypt/openpgp-keys-gentoo-release-20180706" have been masked.
!!! One of the following masked packages is required to complete your request:
- app-crypt/openpgp-keys-gentoo-release-20200704::gentoo (masked by:
Hello,
I am trying to install a data visualization package (VisIt) which
installs locally, on its own, a qt package (qt-everywhere-src-5.14.2).
The config output says:
[snip]
X11 specific:
XLib . no
XCB Xlib . no
On 2020-12-14, Walter Dnes wrote:
> But I want to attach the XPS 8940 to the older monitor, which only has
> VGA and DVI-D. I use the older monitor for setup/install and to keep
> the "hot backup" machine up-to-date. What are my options? For the main
> machine I'll buy an HDMI cable. Are
On 12/14/2020 12:52 PM, Arve Barsnes wrote:
> On Mon, 14 Dec 2020 at 20:38, wrote:
>> but that portage "portage-20090720.tar.bz2" seems old; what is the
>> latest one?
>
> They're generated every day, so pick your poison. Notice it mentions
> updating the portage tree 3-4 months at a time, so
On 14 December 2020 19:55:42 CET, Walter Dnes wrote:
> I ordered a Dell XPS 8940 which arrived in October, but life got in
>the way, and I'm only now getting around to setting it up. First thing
>I noticed today is that Dell "had the courage to remove the VGA port"
>. It has HDMI and
On Mon, 14 Dec 2020 at 20:38, wrote:
> but that portage "portage-20090720.tar.bz2" seems old; what is the
> latest one?
They're generated every day, so pick your poison. Notice it mentions
updating the portage tree 3-4 months at a time, so just pick some
dates at reasonable intervals from your
I'm having similar problem as "n952162" upgrading an old (last updated
1.8-year ago)
It sync OK, updated the profile.
Looking instruction on this page:
https://wiki.gentoo.org/wiki/Upgrading_Gentoo
root #mv /usr/portage /usr/portage.latest
root #tar xjpf /path/to/portage-20090720.tar.bz2 -C /usr
On Mon, 14 Dec 2020 13:55:42 -0500, Walter Dnes wrote:
> I ordered a Dell XPS 8940 which arrived in October, but life got in
> the way, and I'm only now getting around to setting it up. First thing
> I noticed today is that Dell "had the courage to remove the VGA port"
> . It has HDMI and
On Mon, 14 Dec 2020 10:07:37 +, Michael wrote:
> > This shows that you have 20201022-r3 installed but eix says the latest
> > available is 20201022-r2 so you have a version it thinks is not in the
> > tree.
> >
> > Did you run eix-update after syncing?
>
> Just sync'ed and on the mirror I
I ordered a Dell XPS 8940 which arrived in October, but life got in
the way, and I'm only now getting around to setting it up. First thing
I noticed today is that Dell "had the courage to remove the VGA port"
. It has HDMI and Displayport. I've got two monitors for my PCs.
My main one has
On Monday, 14 December 2020 12:55:33 GMT n952162 wrote:
> On 12/14/20 11:17 AM, Wols Lists wrote:
> > On 14/12/20 08:51, Dale wrote:
> >> If you are able, maybe you can compile the bigger packages on a faster
> >> system? If it is a option, it may help.
> >
> > If I have multiple similar
On 2020-12-14, the...@sys-concept.com wrote:
> On 12/13/2020 09:05 PM, Grant Edwards wrote:
>> On 2020-12-14, the...@sys-concept.com wrote:
>>
>>> I removed "vfat" boot partition and created/change it to ext2
>>>
>>> But now when i try to install grub:
>>>
>>> grub-install /dev/nvme0n1p2
>>>
On 12/14/20 11:17 AM, Wols Lists wrote:
On 14/12/20 08:51, Dale wrote:
If you are able, maybe you can compile the bigger packages on a faster
system? If it is a option, it may help.
If I have multiple similar machines, I create a shared a shared local
repository. Then I run emerge with the
On Monday, 14 December 2020 01:21:34 GMT the...@sys-concept.com wrote:
> On 12/13/2020 05:56 PM, the...@sys-concept.com wrote:
> > After running in "/" directory:
> > touch forcefsck
> >
> > The file is gone now, but every time I reboot the system the root
> > partition goes into force check:
> >
On Monday, 14 December 2020 06:07:40 GMT the...@sys-concept.com wrote:
> On 12/13/2020 06:33 AM, Victor Ivanov wrote:
> [snip]
>
> > Out of curiosity, do you have the "sys-fs/dosfstools" package installed?
> >
> > This is the package that provides the fsck.fat binary. It's not a
> > dependency
On Monday, 14 December 2020 08:36:03 GMT Neil Bothwick wrote:
> On Sun, 13 Dec 2020 17:32:12 -0700, the...@sys-concept.com wrote:
> > > It means the version you have installed is no longer in the tree. You
> > > should update to the latest.
> >
> > Something is wrong, I just --sync and reinstall
On Monday, 14 December 2020 05:41:46 GMT Thomas Mueller wrote:
> Excerpt from Michael:
> > Right, on UEFI MoBos the ESP partition used by the UEFI firmware to locate
> > and run *.EFI executables must be FAT32. Such .EFI executables stored on
> > the ESP may be OS boot managers/loaders, or other
On 14/12/20 08:51, Dale wrote:
> If you are able, maybe you can compile the bigger packages on a faster
> system? If it is a option, it may help.
If I have multiple similar machines, I create a shared a shared local
repository. Then I run emerge with the settings (can't remember what
they are)
On 14/12/20 05:41, Thomas Mueller wrote:
> Excerpt from Michael:
>
>> Right, on UEFI MoBos the ESP partition used by the UEFI firmware to locate
>> and
>> run *.EFI executables must be FAT32. Such .EFI executables stored on the
>> ESP
>> may be OS boot managers/loaders, or other UEFI
On Monday, 14 December 2020 00:27:03 GMT the...@sys-concept.com wrote:
> On 12/13/2020 04:44 PM, Michael wrote:
> > On Sunday, 13 December 2020 18:52:51 GMT the...@sys-concept.com wrote:
> >> I have "nouveau" build into kernel but it doesn't work:
> >>
> >> Fom dmesg:
> >>
> >> nouveau
n952162 wrote:
>
> On 12/14/20 4:54 AM, Grant Edwards wrote:
>> On 2020-12-13, n952162 wrote:
>>> On 12/13/20 9:18 AM, Neil Bothwick wrote:
Nearly 2 months, quite a long time in Gentoo update terms.
>>> Okay, is the solution then to re-install?
>> That's _a_ solution, and might be less work.
On Mon, 14 Dec 2020 07:54:55 +0100, n952162 wrote:
> One thing about frequent updating... I thought I was following the
> advice here by developing a procedure to update at the start of every
> month. When I did that, llvm, rust, clang, firefox, and thunderbird
> would rebuild every time, for
On Sun, 13 Dec 2020 17:32:12 -0700, the...@sys-concept.com wrote:
> > It means the version you have installed is no longer in the tree. You
> > should update to the latest.
> >
>
> Something is wrong, I just --sync and reinstall linux-firmware but the
> output is still the same:
>
> eix
On Sun, Dec 13, 2020 at 11:16:05AM +, Nuno Silva wrote
> On 2020-12-12, Walter Dnes wrote:
>
> > I used to get stuff going to tty12, e.g.when attaching a USB drive,
> > etc. My recent fresh install doesn't have this output. What am I doing
> > wrong?
>
> Have you installed something for
48 matches
Mail list logo
