On 30/12/2017 02:44, Peter Humphrey wrote:
> On Friday, 29 December 2017 16:45:33 GMT Wols Lists wrote:
>
>> (Plus, of course, so much development is done for the American market,
>> so they don't realise how hard it is to get a change like A4 to stick :-(
>
> Damned colonials. It's like the base
On 30/12/17 12:55, Alan McKinnon wrote:
> [2nd random OT factoid]
> It's the "world series" because the first sponsor was a newspaper "News
> of the World" iirc (plus some typical US bravado)
Actually it was the New York World. So actually imho it was originally
perfectly legit.
As usual, however
On Sat, 30 Dec 2017 14:32:32 +, Wols Lists wrote:
> [3rd random OT factoid]
> The News Of The World was a British tabloid, which shut down after the
> phone hacking scandal - a lot of their stories were obtained by hacking
> into celebrities, politicians, royals voicemails, and while it was ve
On Sat, 2017-12-30 at 11:58 +1100, Adam Carter wrote:
> > The segfault message would exist in the dmesg/journalctl. Please
> > open a user shell in Gnome and type "gedit ", substituting a
> > text file for . Press enter. Does this segfault and if so
> > is there anything else printed?
> >
> >
I realized I don't really understand it - I just repeat by rote some
keystrokes. In particular:
What do the 'z' and 'n' commands do exactly, and what's the difference
between them?
After I do a 'm', how do I actually use the result of the merge? Is the
merged file now the same as the 'new' one,
On Sat, Dec 30, 2017 at 1:10 PM, Ian Zimmerman wrote:
> I realized I don't really understand it - I just repeat by rote some
> keystrokes. In particular:
>
> What do the 'z' and 'n' commands do exactly, and what's the difference
> between them?
The 'z' command throws away the new config file, le
Recently there was a kernel update and I don't want to reconfigure it
from scratch. In the official documentation, it told me to move the old
.config into the new kernel source tree and type
make oldconfig
This is where I'm confused; which .config file (/proc/config.gz or
/boot/config) and where i
On 30/12/17 18:43, Jalus Bilieyich wrote:
Recently there was a kernel update and I don't want to reconfigure it
from scratch. In the official documentation, it told me to move the old
.config into the new kernel source tree and type
make oldconfig
This is where I'm confused; which .config file (
Hi Jalus,
> This is where I'm confused; which .config file (/proc/config.gz or
> /boot/config)
The two should have the same content most of the time. You can use
either. config.gz needs to be decompressed (e.g. with zcat).
> where in the kernel source tree do I put this file in.
In the root of
Hi Jalus,
On Saturday, 30 December 2017 18:43:12 GMT Jalus Bilieyich wrote:
> Recently there was a kernel update and I don't want to reconfigure it
> from scratch. In the official documentation, it told me to move the old
> .config into the new kernel source tree and type
> make oldconfig
>
> Thi
On 30/12/17 19:11, Mick wrote:
to remove the symlink pointing to the previous kernel,
to create a new symlink to the new kernel sources directory,
Or, to use the supplied gentoo tools ...
eselect kernel list
eselect kernel set n
to see what kernels the system thinks are available, and to cha
This worked.
Thank you all a thousand times!
On 30/12/2017 20:43, Jalus Bilieyich wrote:
> Recently there was a kernel update and I don't want to reconfigure it
> from scratch. In the official documentation, it told me to move the old
> .config into the new kernel source tree and type
> make oldconfig
>
> This is where I'm confused; which .c
On Sat, Dec 30, 2017 at 02:18:12AM +0200, Alan McKinnon wrote:
> It's probably a dodgy kernel point bersion, 4.14 is problematic.
>
> Alice Ferrazzi posted this to gentoo-dev earlier today:
>
> =start quote=
> [ lots of problems ]
> = end quote=
Now that’s interesting. On my thi
It took a lot of work, but this latest kernel 14.4 enables support for
machines with 128 pebibytes of RAM, up from the old limit of 256 TiB.
On 12/30/2017 05:16 PM, Frank Steinmetzger wrote:
>
> On my thinkpad, 4.14 crashes ... when I build audio support into it.
But who uses that?
* Install gdb if it isn't already installed
>
> * Make sure a core file is presend in coredumpd, coredumpctl should
> show; if not, have it crash again so it's fresh and saved in there
>
> * coredumpctl gdb gedit
>
> * bt full
>
> Post output of that "bt full"
>
> (gdb) bt full
#0 0x7f60cd333
On 2017-12-30 17:26, Michael Orlitzky wrote:
> It took a lot of work, but this latest kernel 14.4 enables support for
> machines with 128 pebibytes of RAM, up from the old limit of 256 TiB.
>
>
> On 12/30/2017 05:16 PM, Frank Steinmetzger wrote:
> >
> > On my thinkpad, 4.14 crashes ... when I
On Sat, 30 Dec 2017 10:10:33 -0800, Ian Zimmerman wrote:
> I realized I don't really understand it - I just repeat by rote some
> keystrokes. In particular:
>
> What do the 'z' and 'n' commands do exactly, and what's the difference
> between them?
>
> After I do a 'm', how do I actually use the
On Saturday, 30 December 2017 00:18:12 GMT Alan McKinnon wrote:
> If you want to fix the bugs, then by all means soldier on. But if your
> intent is to have a working system that boots, probably drop using
> 4.14.x and go back to say 4.12.x ?
But the whole 4.12 branch has been masked, so that won
On Sunday, 31 December 2017 00:33:34 GMT Peter Humphrey wrote:
> On Saturday, 30 December 2017 00:18:12 GMT Alan McKinnon wrote:
> > If you want to fix the bugs, then by all means soldier on. But if your
> > intent is to have a working system that boots, probably drop using
> > 4.14.x and go back t
On 2017-12-31 00:33, Peter Humphrey wrote:
> But the whole 4.12 branch has been masked, so that won't do. Here,
> I've had to go back to 4.9.49-r1 (amd64, not ~amd64). But now I see
> 4.9.72 has been stabilised. I think I'll wait for some stabiliity in
> the kernel version offerings before I make
On Sunday, 31 December 2017 01:13:26 GMT Ian Zimmerman wrote:
> On 2017-12-31 00:33, Peter Humphrey wrote:
> > But the whole 4.12 branch has been masked, so that won't do. Here,
> > I've had to go back to 4.9.49-r1 (amd64, not ~amd64). But now I see
> > 4.9.72 has been stabilised. I think I'll wait
On Saturday, 30 December 2017 14:32:32 GMT Wols Lists wrote:
> On 30/12/17 12:55, Alan McKinnon wrote:
> > [2nd random OT factoid]
> > It's the "world series" because the first sponsor was a newspaper "News
> > of the World" iirc (plus some typical US bravado)
>
> Actually it was the New York Worl
Some background:
A little while back I had a drive drop out of my hardware RAID. I don't
think this has anything to do with the problem I'm having, but I thought
I should mention it. The RAID health is fine and I can see there's not
any delay in dmesg (the RAID array is detected as /dev/sdc).
On Sun, Dec 31, 2017 at 2:22 PM, Daniel Frey wrote:
> Some background:
>
> A little while back I had a drive drop out of my hardware RAID. I don't
> think this has anything to do with the problem I'm having, but I thought I
> should mention it. The RAID health is fine and I can see there's not an
I'm getting a strange error trying to boot my system.
init id c5 response too fast disabled for 5 min
the error appears right after when it to start mysql at boot.
In addition when the system starts I see:
ata4.00 failed command read DMA
It is hart to post any information as I can not even boot
that would most likely be a failing/failed hard drive or a bad
connection/cable. I'd suggest carefully checking the cable and then boot off a
cd and back up anything you care about on the drive, you might check the SMART
status of the drive. In any case back it up first, worry about understand
I boot-strap the system from CD and run:
fsck /dev/sda5
got bunch of errors eg.:
Directories count wrong for group #1567 (1, counted=0).
Fix? yes
Free inodes count wrong for group #1568 (8073, counted=8192).
Fix? yes
Directories count wrong for group #1568 (1, counted=0).
Fix? yes
Free inodes c
likely dying soon, or if you are lucky a key sector went out, if not the drive
may be getting worse with every rotation. If the drive is badly corrupted fsck
can damage what is left. definately DO NOT run fsck without knowing if the
hardware has serious problems, also if part of it won't read
with the seg fault, you may have other problems. you might want to unplug the
hard drive (so you aren't spinning it) and run whatever diagnostics you can on
the machine, just to make sure it's not failing/loosing it's little silicon
mind.
seg fault shouldn't happen (from drive issues) i don
30 matches
Mail list logo
