Re: [gentoo-user] Re: Firefox occasionally stalls

Alan McKinnon wrote: > > I got fed up dealing with Firefox addons, so took the alternate route I > used about every 6 months or so: > > emerge -et world > > and everything is nice and stable now after 48 hours running. I actually > suspect an intel driver/mesa problem as I would often also get

Re: [gentoo-user] eclean-pkg strips everything out

Peter Humphrey wrote: > > Hello list, > > > > Has anyone else noticed that running "eclean-pkg -d" removes all > packages, or nearly so? I've had it happen recently on a few amd64 > systems and an x86 system, and it's becoming annoying. Well, no, > actually it's long since become annoying. > >

Re: [gentoo-user] Re: Heads up: A reason *NOT* to have xorg.conf file

Neil Bothwick wrote: > On Tue, 4 Apr 2017 16:45:07 -0500, Dale wrote: > >> Until I do >> that, I won't know if I need a xorg file or just a couple files in >> xorg.conf.d or something else. That also is not to mention that I have >> no idea what needs to go into those new files at this time, if

[gentoo-user] eclean-pkg strips everything out

Hello list, Has anyone else noticed that running "eclean-pkg -d" removes all packages, or nearly so? I've had it happen recently on a few amd64 systems and an x86 system, and it's becoming annoying. Well, no, actually it's long since become annoying. -- Regards Peter

[gentoo-user] Re: soliciting a DHCP lease / carrier lost

Am Tue, 4 Apr 2017 15:05:57 -0700 schrieb Daniel Frey : > On 04/04/2017 02:49 PM, Kai Krakow wrote: > > No, if you have the same wrong on both sides, the LEDs will still > > show correct blinking order. Think of it like this: If you use order > > 7-5-3-1-2-4-6-8 on both sides,

Re: [gentoo-user] Re: soliciting a DHCP lease / carrier lost

On 04/04/2017 02:49 PM, Kai Krakow wrote: > No, if you have the same wrong on both sides, the LEDs will still show > correct blinking order. Think of it like this: If you use order > 7-5-3-1-2-4-6-8 on both sides, blinking LED 1 on one side will blink > the same LED on the other side because they

Re: [gentoo-user] Re: Heads up: A reason *NOT* to have xorg.conf file

On Tue, 4 Apr 2017 16:45:07 -0500, Dale wrote: > Until I do > that, I won't know if I need a xorg file or just a couple files in > xorg.conf.d or something else. That also is not to mention that I have > no idea what needs to go into those new files at this time, if anything > is needed. The

[gentoo-user] Re: soliciting a DHCP lease / carrier lost

Am Tue, 4 Apr 2017 15:05:13 -0600 schrieb the...@sys-concept.com: > On 04/04/2017 02:56 PM, Kai Krakow wrote: > > Am Tue, 4 Apr 2017 14:28:23 -0600 > > schrieb the...@sys-concept.com: > > > [snip] > >> > >> I have reconnected another cable and the unit in remote location > >> works. Both cable

Re: [gentoo-user] Ryzen initial results.

On 04/04/2017 10:37 PM, Alan Grimes wrote: > I installed my Ryzen system today, using a mATX b350 mobo. > > My existing kernel mostly works, > > > > .00] Linux version 4.6.7 (root@tortoise) (gcc version 5.4.0 (Gentoo > 5.4.0-r3 p1.3, pie-0.6.5) ) #6 SMP Tue Apr 4 22:34:38 EDT 2017 >From

Re: [gentoo-user] Re: Heads up: A reason *NOT* to have xorg.conf file

Nikos Chantziaras wrote: > On 04/02/2017 07:35 AM, Dale wrote: >> Nikos Chantziaras wrote: >>> On 04/02/2017 06:55 AM, Walter Dnes wrote: My best guess is that the problem was due to a recent update to x11-base/xorg-server On both my systems it now requires USE="glamor". This may

[gentoo-user] Ryzen initial results.

I installed my Ryzen system today, using a mATX b350 mobo. My existing kernel mostly works, .00] Linux version 4.6.7 (root@tortoise) (gcc version 5.4.0 (Gentoo 5.4.0-r3 p1.3, pie-0.6.5) ) #6 SMP Tue Apr 4 22:34:38 EDT 2017 0.00] Command line: BOOT_IMAGE=/vmlinuz-4.6.7 root=/dev/sda3 ro

Re: [gentoo-user] Re: Heads up: A reason *NOT* to have xorg.conf file

On Tue, 4 Apr 2017 22:27:57 +0200 (CEST), k...@aspodata.se wrote: > > I have an /etc/X11/xorg.conf.d/mouse.conf file. I use it to set the > > default acceleration profile. In your case, you should be able to > > delete your xorg.conf and instead just use this in mouse.conf: > > > >Section

Re: [gentoo-user] Re: soliciting a DHCP lease / carrier lost

On 04/04/2017 02:56 PM, Kai Krakow wrote: > Am Tue, 4 Apr 2017 14:28:23 -0600 > schrieb the...@sys-concept.com: > [snip] >> >> I have reconnected another cable and the unit in remote location >> works. Both cable have a good pinout but one is working and the other >> is not. Both cable are

[gentoo-user] Re: soliciting a DHCP lease / carrier lost

Am Tue, 4 Apr 2017 14:28:23 -0600 schrieb the...@sys-concept.com: > On 04/04/2017 10:02 AM, Mick wrote: > > On Tuesday 04 Apr 2017 09:12:16 the...@sys-concept.com wrote: > >> On 04/04/2017 01:26 AM, Mick wrote: > [...] > > > [...] > > > > This may merely indicate they have been

[gentoo-user] Re: soliciting a DHCP lease / carrier lost

Am Tue, 4 Apr 2017 09:12:16 -0600 schrieb the...@sys-concept.com: > On 04/04/2017 01:26 AM, Mick wrote: > > On Monday 03 Apr 2017 20:21:28 the...@sys-concept.com wrote: > >> The new box I installed in remote location has a problem obtaining > >> IP address. The box was working perfectly on my

Re: [gentoo-user] soliciting a DHCP lease / carrier lost

On 04/04/2017 10:02 AM, Mick wrote: > On Tuesday 04 Apr 2017 09:12:16 the...@sys-concept.com wrote: >> On 04/04/2017 01:26 AM, Mick wrote: >>> On Monday 03 Apr 2017 20:21:28 the...@sys-concept.com wrote: > The Cat5 is about 15-20meter long, I test it with a cable tester, it is good (all

Re: [gentoo-user] Re: Heads up: A reason *NOT* to have xorg.conf file

Nikos: > On 04/04/2017 12:11 AM, k...@aspodata.se wrote: > > Walter Dnes: > > ... > >> This state of affairs seems to have evolved slowly. There wasn't one > >> version where it worked for nobody, immediately followed by the next > >> version that worked for everybody. Years ago, X would not

Re: [gentoo-user] soliciting a DHCP lease / carrier lost

On Tuesday 04 Apr 2017 09:12:16 the...@sys-concept.com wrote: > On 04/04/2017 01:26 AM, Mick wrote: > > On Monday 03 Apr 2017 20:21:28 the...@sys-concept.com wrote: > >> The Cat5 is about 15-20meter long, I test it with a cable tester, it is > >> good (all the lights light up in correct order). >

Re: [gentoo-user] soliciting a DHCP lease / carrier lost

On 04/04/2017 01:26 AM, Mick wrote: > On Monday 03 Apr 2017 20:21:28 the...@sys-concept.com wrote: >> The new box I installed in remote location has a problem obtaining IP >> address. The box was working perfectly on my local LAN. >> >> In remote location I assigned static IP to it 10.10.0.5 >

[gentoo-user] Re: [OT] Tools for putting HDD back to new state

On 04/04/2017 04:07 PM, Harry Putnam wrote: I've googled fairly extensively on the subject and did not find a way described anywhere to return a disk to what is called its raw state. There's not such thing. When shipping, the disk might contain all zero-bytes, or random bytes. There may

[gentoo-user] Re: [OT] Tools for putting HDD back to new state

Mike Gilbert writes: [...] > If you are not worried about securely removing all data and simply > want to fool fdisk into thinking your drive is empty, use the wipefs > utility. This will zero-out key bytes like the MBR, partition table, > filesystem magic numbers, etc. > >

[gentoo-user] Re: [OT] Tools for putting HDD back to new state

On 04/03/2017 09:11 PM, Harry Putnam wrote: I probably should know this, but off the top of my head I don't remember ever running into anything like this. I'd like to do what ever is done to set a used disk back to the state it was in when new... Not sure what that state is, but at least no

[gentoo-user] Re: Heads up: A reason *NOT* to have xorg.conf file

On 04/04/2017 12:11 AM, k...@aspodata.se wrote: Walter Dnes: ... This state of affairs seems to have evolved slowly. There wasn't one version where it worked for nobody, immediately followed by the next version that worked for everybody. Years ago, X would not run without an xorg.conf file.

Re: [gentoo-user] soliciting a DHCP lease / carrier lost

On Monday 03 Apr 2017 20:21:28 the...@sys-concept.com wrote: > The new box I installed in remote location has a problem obtaining IP > address. The box was working perfectly on my local LAN. > > In remote location I assigned static IP to it 10.10.0.5 Where and how? At the router IP address