search for: n270

...s. I have a very old Ubuntu netbook-remix on it, and it really, *really* needs to be updated to something current. I, of course, would prefer CentOS.... The question is: I see that *if* the specs I just looked up (I'm at work, not home, where I could just turn it on, but they sound right) Atom N270 CPU, 2G RAM, 160GB drive - what should I put on it, C6 or C7? Upgrading the memory's not going to happen, so it's got to live with that size. Opinions (please, no flame wars), just what will be most responsive on a machine this small? mark

...-remix on it, and it really, *really* needs to be updated to >> something current. I, of course, would prefer CentOS.... >> >> The question is: I see that *if* the specs I just looked up (I'm at work, >> not home, where I could just turn it on, but they sound right) Atom N270 >> CPU, 2G RAM, 160GB drive - what should I put on it, C6 or C7? Upgrading >> the memory's not going to happen, so it's got to live with that size. >> >> Opinions (please, no flame wars), just what will be most responsive on a >> machine this small? > >...

System: Microsoft Windows XP Home Edition CPUs: Intel(R) Atom(TM) CPU N270 @1.60GHz setup for the 'Git for Windows' with MSYS2 gcc-6.1.0 plus utilties and libraries were added http://nurmi-labs.blogspot.com/2016/11/git.html obviously, with Home Edition, no network was setup http://nurmi-labs.blogspot.com/p/xapian-ms.html System: Slackware Linux (version 14.0...

...ml" if you don't believe me ;) > > Martin Martin Many thanks for helping me get to the bottom of this, though could you clarify what you mean when you say that the difference is only in the "syscall" feature? I've looked at cpu_map.xml, and compared the features for n270 (pentiumpro+coreduo+ssse3) with SandyBridge (pentiumpro+Conroe+Penryn+Nehalem+Westmere+pclmuldq+SandyBridge) and am seeing quite a few differences (see below). The main issue though for me, is that the libvirt architecture need not be representative of the virtualisation architecture. Apart fro...

On Mon, 5 Jun 2017, m.roth at 5-cent.us wrote: > Mmmm... looks like I may go for C6, then, since unlike that Ubuntu, I will > want to do updates at least every time I get ready for a trip (other > times, it sits in the closet turned off). I went for C6 on a Samsung NC10 (1.6GHz Atom N270 1GB RAM), only because it refused to boot off the C7 ISO for some reason, and I didn't want to waste time tracking down why. Works like a charm without any fiddling with an alternate DE like I would have with C7. I have no complaints. jh

...;) > > > > Martin > Martin > > Many thanks for helping me get to the bottom of this, though could you > clarify what you mean when you say that the difference is only in the > "syscall" feature? I've looked at cpu_map.xml, and compared the features > for n270 (pentiumpro+coreduo+ssse3) with SandyBridge > (pentiumpro+Conroe+Penryn+Nehalem+Westmere+pclmuldq+SandyBridge) and am > seeing quite a few differences (see below). The main issue though for You have to also add the features that libvirt added in the output of 'virsh capabilities' and...

Please can anyone enlighten me as to why linux qemu-kvm always creates the console on my terminal, when I am trying to direct all of its input and output to a pipe ? I have created : $ mkfifo /tmp/el6x32{.in,.out,.monitor} and use the command: $ /usr/libexec/qemu-kvm -M rhel6.4.0 -cpu n270 -smp 1 \ -hda /home/rpmbuild/OEL6/img/OEL6_32.img \ -kernel /home/rpmbuild/OEL6/boot/vmlinuz-2.6.39-400.215.14.el6uek.i686 \ -initrd /home/rpmbuild/OEL6/boot/initramfs 2.6.39-400.215.14.el6uek.i686.img \ -append 'root=/dev/sda rw selinux=0 enforcing=0 console=0' \ -...

Aha! Thank you. Yes that does prevent the default stdio console . But no output appears on the input pipe, and outputting to input end has no effect: In one terminal, I do: $ cat /tmp/el6x32.out in the main terminal, I run: $ /usr/libexec/qemu-kvm -M rhel6.4.0 -cpu n270 -smp 1 -hda /home/rpmbuild/OEL6/img/OEL6_32.img -kernel /home/rpmbuild/OEL6/boot/vmlinuz-2.6.39-400.215.14.el6uek.i686 -initrd /home/rpmbuild/OEL6/boot/initramfs-2.6.39-400.215.14.el6uek.i686.img -append 'root=/dev/sda rw selinux=0 enforcing=0 console=0' -m 2048 -k en-gb -nographic -vga non...

Hi On a range of Dell servers containing Intel 64bit processors, 'virsh capabilities' reports the cpu differently on Debian Wheezy-amd64 and Wheezy-i386. The results given by the Wheezy-i386 version seem very wrong (since n270 is an Atom processor). Apart from architecture, the package versions of libvirt-bin are identical: 1.2.1-1~bpo70+1. /usr/share/libvirt/cpu_map.xml files are identical. Is this a known issue? Details for one server are: # cat /proc/cpuinfo| head -n 26 processor : 0 vendor_id : Genuin...

...a range of Dell servers containing Intel 64bit processors, 'virsh >>>>>> capabilities' reports the cpu differently on Debian Wheezy-amd64 and >>>>>> Wheezy-i386. The results given by the Wheezy-i386 version seem very >>>>>> wrong (since n270 is an Atom processor). Apart from architecture, the >>>>>> package versions of libvirt-bin are identical: 1.2.1-1~bpo70+1. >>>>>> /usr/share/libvirt/cpu_map.xml files are identical. Is this a known >>>>>> issue? Details for one server are: >&...

...tu > netbook-remix on it, and it really, *really* needs to be updated to > something current. I, of course, would prefer CentOS.... > > The question is: I see that *if* the specs I just looked up (I'm at work, > not home, where I could just turn it on, but they sound right) Atom N270 > CPU, 2G RAM, 160GB drive - what should I put on it, C6 or C7? Upgrading > the memory's not going to happen, so it's got to live with that size. > > Opinions (please, no flame wars), just what will be most responsive on a > machine this small? I think the Atom N270 is a 32...

...*really* needs to be updated to >>> something current. I, of course, would prefer CentOS.... >>> >>> The question is: I see that *if* the specs I just looked up (I'm at >>> work, not home, where I could just turn it on, but they sound right) Atom >>> N270 CPU, 2G RAM, 160GB drive - what should I put on it, C6 or C7? Upgrading >>> the memory's not going to happen, so it's got to live with that size. <snip> >> I think the Atom N270 is a 32-bit processor, no? I think so. Given the date, and the price (had I paid full price...

System: Slackware Linux (version 14.0) CPUs: Intel(R) Atom(TM) CPU N270 @1.60GHz xapian-core-1.4.1.tar.xz http://nurmi-labs.blogspot.com/p/xapian-linux-sse.html

...ntu installed. I'm happy that it worked, but I also know this is not normal behavior so I joined the mailing list in order to help bring back compatibility. Here are details of the machine. I hope this is going to be of some help. Acer Aspire One Netbook AOA150 Insyde H2O Bios 3.5 Intel Atom N270 (single core) 1.6ghz VGA Bios Intel V 1585 Acer bios version 0.3310 If you need more information, I will gladly help. Thanks Fran?ois

hi, I'm using the SCD-20 solar controller from IVT Gmbh in combination with a 230Ah battery and a photovoltaic panel to power a small server based on an Intel ATOM N270 CPU. the controller is (will be) connected to the server via RS232 (1200 8n1) and works like this: - if the battery voltage drops below 12V, a warning LED is switched on - if the battery voltage drops below 10.5V, the load (the server) is powered off to prevent exhaustive battery discharge - if t...

...Bartlett wrote: >> Hi >> >> On a range of Dell servers containing Intel 64bit processors, 'virsh >> capabilities' reports the cpu differently on Debian Wheezy-amd64 and >> Wheezy-i386. The results given by the Wheezy-i386 version seem very >> wrong (since n270 is an Atom processor). Apart from architecture, the >> package versions of libvirt-bin are identical: 1.2.1-1~bpo70+1. >> /usr/share/libvirt/cpu_map.xml files are identical. Is this a known >> issue? Details for one server are: >> >> # cat /proc/cpuinfo| head -n 26 &gt...

...turns me the following capabilities : $ kvm -cpu ? x86 qemu64 x86 phenom x86 core2duo x86 kvm64 x86 qemu32 x86 coreduo x86 486 x86 pentium x86 pentium2 x86 pentium3 x86 athlon x86 n270 Moreover, if i decide to use the pentium3 cpumodel for my KVM VM, the CentOS freeze during its loading. My libvirt and kvm are the following on a Debian Squeeeze : $ virsh version Compiled against library: libvir 0.8.3 Using library: libvir 0.8.3 Using API: QEMU 0.8.3 Running hypervisor: QEMU 0...

...3:45:01PM +0000, Struan Bartlett wrote: > Hi > > On a range of Dell servers containing Intel 64bit processors, 'virsh > capabilities' reports the cpu differently on Debian Wheezy-amd64 and > Wheezy-i386. The results given by the Wheezy-i386 version seem very > wrong (since n270 is an Atom processor). Apart from architecture, the > package versions of libvirt-bin are identical: 1.2.1-1~bpo70+1. > /usr/share/libvirt/cpu_map.xml files are identical. Is this a known > issue? Details for one server are: > > # cat /proc/cpuinfo| head -n 26 > processor :...

...> >>>> On a range of Dell servers containing Intel 64bit processors, 'virsh >>>> capabilities' reports the cpu differently on Debian Wheezy-amd64 and >>>> Wheezy-i386. The results given by the Wheezy-i386 version seem very >>>> wrong (since n270 is an Atom processor). Apart from architecture, the >>>> package versions of libvirt-bin are identical: 1.2.1-1~bpo70+1. >>>> /usr/share/libvirt/cpu_map.xml files are identical. Is this a known >>>> issue? Details for one server are: >>>> >>>...

...Hi > >> > >> On a range of Dell servers containing Intel 64bit processors, 'virsh > >> capabilities' reports the cpu differently on Debian Wheezy-amd64 and > >> Wheezy-i386. The results given by the Wheezy-i386 version seem very > >> wrong (since n270 is an Atom processor). Apart from architecture, the > >> package versions of libvirt-bin are identical: 1.2.1-1~bpo70+1. > >> /usr/share/libvirt/cpu_map.xml files are identical. Is this a known > >> issue? Details for one server are: > >> > >> # cat /pro...