On Sat, 2013-12-07 at 21:41 +, Richard Melville wrote:
> The atom has come a long way since its inauguration; the latest
> Silverton range featuring the Avoton processors boast up to an eight
> core model with a 2.6 GHz clock speed per core and a 64 bit
> instruction set. The L3 cache is up t
>
> Good luck - I guess that compiling a kernel on an atom will be
> slow.
>
> ?en
> --
> das eine Mal als Trag?die, dieses Mal als Farce
>
The atom has come a long way since its inauguration; the latest Silverton
range featuring the Avoton processors boast up to an eight core model with
a 2.6 G
On Fri, Dec 6, 2013 at 7:02 PM, William Harrington
wrote:
>> Good luck - I guess that compiling a kernel on an atom will be
>> slow.
>>
>> ĸen
>
> All hail the power of cross compilers with faster machines!
I'll give it a try.
> Hopefully it does get fixed so this thread will help someone. Lots
On Dec 6, 2013, at 10:51 AM, Ken Moffat wrote:
> Good luck - I guess that compiling a kernel on an atom will be
> slow.
>
> ĸen
All hail the power of cross compilers with faster machines!
Hopefully it does get fixed so this thread will help someone. Lots of
information here.
Sincerely,
Wil
On Fri, Dec 06, 2013 at 02:26:24PM +0100, Alexey Orishko wrote:
> On Thu, Dec 5, 2013 at 11:01 PM, Ken Moffat wrote:
> >
> > I still think my suggestion of checking every key will identify if
> > any of the keys are being garbled in the kernel, and therefore if
> > this is a kernel _input_ proble
On Thu, Dec 5, 2013 at 11:01 PM, Ken Moffat wrote:
>
> I still think my suggestion of checking every key will identify if
> any of the keys are being garbled in the kernel, and therefore if
> this is a kernel _input_ problem.
>
> But here is an alternative train of thought :
>
> When you trigge
On Fri, Dec 6, 2013 at 1:04 AM, Ken Moffat wrote:
> > Forgot to attach it the first time, and when I did it bounced (too
> > big, whoops!). So here's the third attempt, using xz to compress it
> > from 177K to < 7K.
>
> Thanks and sorry for confusion!
> I had no Unicode initially, but added it
On Fri, Dec 6, 2013 at 1:04 AM, Ken Moffat wrote:
> Forgot to attach it the first time, and when I did it bounced (too
> big, whoops!). So here's the third attempt, using xz to compress it
> from 177K to < 7K.
Thanks and sorry for confusion!
I had no Unicode initially, but added it after initi
On Thu, Dec 05, 2013 at 10:01:00PM +, Ken Moffat wrote:
>
> Your LatArCyrHeb font has two, possibly three, characters which
> match a "white square". If you manage to prove that it is a kernel
> video problem, can you please "loadkeys LatGrkCyr-8x16" and repeat
> the test. I'm guessing you
On Thu, Dec 05, 2013 at 05:43:28PM +0100, Alexey Orishko wrote:
> On Thu, Dec 5, 2013 at 4:40 PM, Ken Moffat wrote:
> >>
> > This gets weirder and weirder. Most of us don't have a stock of
> > different motherboards to play with, and I've no experience in this
> > area. I think you said that sh
On Thu, Dec 5, 2013 at 4:40 PM, Ken Moffat wrote:
>>
> This gets weirder and weirder. Most of us don't have a stock of
> different motherboards to play with, and I've no experience in this
> area. I think you said that showkey and dumpkeys reported the
> keyboard was giving the expected values
On Thu, Dec 05, 2013 at 03:06:01PM +0100, Alexey Orishko wrote:
> On Wed, Dec 4, 2013 at 7:27 PM, Ken Moffat wrote:
> >
> > In my previous reply I included an invalid-unicode symbol, code
> > U+FFFD displaying as reverse-video question mark : � : if you read
> > the mail on the LFS-7.4 machine (o
On Wed, Dec 4, 2013 at 7:27 PM, Ken Moffat wrote:
>
> In my previous reply I included an invalid-unicode symbol, code
> U+FFFD displaying as reverse-video question mark : � : if you read
> the mail on the LFS-7.4 machine (or copy this paragraph to a file,
> scp that file to the LFS machine, and t
Le 04/12/2013 20:38, Alexey Orishko a écrit :
> On Wed, Dec 4, 2013 at 7:27 PM, Ken Moffat wrote:
>>
>> I now wonder if you are using a non-unicode console font ?
>
> I've built LFS using ALFS scripts and didn't change anything regarding
> fonts... should I?
ALFS (jhalfs) does not set anything
On 12/04/2013 08:38 PM, Alexey Orishko wrote:
> On Wed, Dec 4, 2013 at 7:27 PM, Ken Moffat wrote:
>>
>> I now wonder if you are using a non-unicode console font ?
>
> I've built LFS using ALFS scripts and didn't change anything regarding
> fonts... should I?
What does your /etc/sysconfig/consol
On Wed, Dec 04, 2013 at 08:38:12PM +0100, Alexey Orishko wrote:
> On Wed, Dec 4, 2013 at 7:27 PM, Ken Moffat wrote:
> >
> > I now wonder if you are using a non-unicode console font ?
>
> I've built LFS using ALFS scripts and didn't change anything regarding
> fonts... should I?
> I'll check the
On Wed, Dec 4, 2013 at 7:27 PM, Ken Moffat wrote:
>
> I now wonder if you are using a non-unicode console font ?
I've built LFS using ALFS scripts and didn't change anything regarding
fonts... should I?
I'll check the rest tomorrow.
/alexey
--
http://linuxfromscratch.org/mailman/listinfo/blfs-
On Wed, Dec 04, 2013 at 01:11:00PM +0100, Alexey Orishko wrote:
> On Tue, Dec 3, 2013 at 10:53 PM, Ken Moffat wrote:
> > On Tue, Dec 03, 2013 at 08:29:42PM +, Ken Moffat wrote:
> >>
> >> What are the locales (LC_ALL or similar) in BOTH systems ?
> Neither has LC_ALL set
>
> Ubuntu and LFS-7.
On Tue, Dec 3, 2013 at 10:53 PM, Ken Moffat wrote:
> On Tue, Dec 03, 2013 at 08:29:42PM +, Ken Moffat wrote:
>>
>> What are the locales (LC_ALL or similar) in BOTH systems ?
Neither has LC_ALL set
Ubuntu and LFS-7.4 had this set:
LANG=en_US.UTF-8
My old LFS-6.3 has
LANG=en_US.ISO-8859-1
>>
On Tue, Dec 03, 2013 at 08:29:42PM +, Ken Moffat wrote:
>
> Other things to consider:
>
> What are the locales (LC_ALL or similar) in BOTH systems ?
>
> Using 'showkey' [ in a tty ], find the values for the Backspace and
> Del keys - on a regular 102-key keyboard mine are 14 and 111 - the
On Tue, Dec 03, 2013 at 12:41:26PM -0600, William Harrington wrote:
>
> On Dec 3, 2013, at 10:14 AM, Alexey Orishko wrote:
>
> > At least LANG=en_US.UTF-8 and non-us keyboard are working file with
> > Ubuntu...
> > I wonder what's wrong with my LFS setup...
>
> utf-8 (Unicode ), iso-8859-1, is
On Dec 3, 2013, at 10:14 AM, Alexey Orishko wrote:
> At least LANG=en_US.UTF-8 and non-us keyboard are working file with
> Ubuntu...
> I wonder what's wrong with my LFS setup...
utf-8 (Unicode ), iso-8859-1, iso-8859-15 (with euro symbol)
For norwegian you need to load the "no" keymap
There
>
> Hi folks,
>
> I wonder if anyone could guess what's wrong with my text terminal.
> I've recently built LFS-7.4 (32bit) and most of BLFS (I'm not using X
> Windows, just text terminals only) on Atom D2550 motherboard, VGA display
> resolution.
>
> When I logged in if I try to edit bash command l
Hi folks,
I wonder if anyone could guess what's wrong with my text terminal.
I've recently built LFS-7.4 (32bit) and most of BLFS (I'm not using X
Windows, just text terminals only) on Atom D2550 motherboard, VGA display
resolution.
When I logged in if I try to edit bash command line by deleting
24 matches
Mail list logo
