Re: [gentoo-user] CPU you selected does not support x86-64 instruction set

2016-05-04 Thread John Blinka
On Wed, May 4, 2016 at 6:51 PM, Neil Bothwick wrote: > > SystemRescueCd has boot menu options for picking the kernel, just pick > either rescue64 or altker64. > I did try that at least once, but I think I compensated for doing the right thing at that point with making

Re: [gentoo-user] CPU you selected does not support x86-64 instruction set

2016-05-04 Thread John Blinka
On Wed, May 4, 2016 at 12:36 PM, Ron Farrer wrote: > > Generally, 'uname -m' should report x86_64 for 64-bit (amd64) and i686 > for 32-bit (x86). uname -m did give x86_64, but... > ... another check can be 'file /sbin/init' which will report as something > along the

Re: [gentoo-user] CPU you selected does not support x86-64 instruction set

2016-05-04 Thread Neil Bothwick
On Wed, 4 May 2016 12:08:22 -0400, John Blinka wrote: > I had read similar thoughts about booting into a 64 bit environment > before posting and had gone to some effort to figure out whether the > sysrescuecd kernel was, in fact, 64 bit. Its /proc/config.gz seemed to > indicate 64 bit, as did

[gentoo-user] Re: DRM Problem : Radeon HD 7670M

2016-05-04 Thread James
Neil Bothwick digimed.co.uk> writes: > > Therefore, I check the configuration of grub2 and fstab. Then I found > > that I forgot to modify mount options in fstab. > > The option of my boot partition was set as noauto. So that I don't use > > the kernel compiled by myself at all. > We've all

Re: [gentoo-user] CPU you selected does not support x86-64 instruction set

2016-05-04 Thread Ron Farrer
On Wed, May 4, 2016 at 9:08 AM, John Blinka wrote: > > I had read similar thoughts about booting into a 64 bit environment before > posting and had gone to some effort to figure out whether the sysrescuecd > kernel was, in fact, 64 bit. Its /proc/config.gz seemed to

Re: [gentoo-user] CPU you selected does not support x86-64 instruction set

2016-05-04 Thread John Blinka
On Wed, May 4, 2016 at 11:31 AM, Michael Mol wrote: > > You should use the AMD64 handbook, not the x86 handbook, if you're trying > to > install on x86_64 hardware. > > https://wiki.gentoo.org/wiki/Handbook:AMD64 > > More importantly, you should be booted into a 64-bit

Re: [gentoo-user] CPU you selected does not support x86-64 instruction set

2016-05-04 Thread Michael Mol
On Wednesday, May 04, 2016 09:58:37 AM John Blinka wrote: > Hello, Gentooers: > > I have a new Dell 17 5759 with core i5-6200U skylake cpu on which I'm > trying to dual boot windows 10 and gentoo. All the rest of my gentoo > hardware is much older, so this new laptop introduces 2 technologies

[gentoo-user] Re: How to stop ls from quoting output

2016-05-04 Thread Nikos Chantziaras
On 03/05/16 20:07, Daniel Quinn wrote: Some time ago after an update |ls| started returning output that looked like this: |8hOk25T.jpg 'Janeway Wallpaper-iPhone.png' 'Screenshot from 2016-04-06 16-15-15.png' microsoft.png 'Away mission Wallpaper-iPhone.png' 'Screenshot from 2016-03-18

[gentoo-user] CPU you selected does not support x86-64 instruction set

2016-05-04 Thread John Blinka
Hello, Gentooers: I have a new Dell 17 5759 with core i5-6200U skylake cpu on which I'm trying to dual boot windows 10 and gentoo. All the rest of my gentoo hardware is much older, so this new laptop introduces 2 technologies new to me: uefi and 64 bit kernels. I installed gentoo using the x86

Re: SOLVED Re: [gentoo-user] ATLAS@home and VirtualBox

2016-05-04 Thread Peter Humphrey
On Tuesday 03 May 2016 18:47:39 Andrew Savchenko wrote: > On Tue, 03 May 2016 09:56:29 +0100 Peter Humphrey wrote: --->8 > > What is the approved method of reading change-logs nowadays? > > If you are using git sync, just go to /usr/portage/sci-misc/boinc > and run `git log .` there. > > If

Re: [gentoo-user] Re: DRM Problem : Radeon HD 7670M

2016-05-04 Thread Neil Bothwick
On Wed, 4 May 2016 13:06:45 +0800, JingYuan Chen wrote: > I found that I made a big mistake after I installed kernel 4.4.6. My > laptop still used kernel 4.1.5 to boot. It come as a surprise to me. > > Therefore, I check the configuration of grub2 and fstab. Then I found > that I forgot to