In message from Greg Lindahl (Thu, 20 Aug 2009
11:23:25 -0700):
On Thu, Aug 20, 2009 at 08:06:07PM +0200, Reuti wrote:
AFAIK, initrd (as the kernel itself) is "universal" for
EM64T/x86-64,
The problem is not the type of CPU, but the chipset (i.e. the
necessary
kernel module) with which the
On Thu, Aug 20, 2009 at 08:06:07PM +0200, Reuti wrote:
>> AFAIK, initrd (as the kernel itself) is "universal" for EM64T/x86-64,
>
> The problem is not the type of CPU, but the chipset (i.e. the necessary
> kernel module) with which the HDD is accessed.
There are 2 aspects to this:
1: /etc/modpr
Am 20.08.2009 um 19:33 schrieb Mikhail Kuzminsky:
In message from Reuti (Thu, 20 Aug
2009 19:02:49 +0200):
Am 20.08.2009 um 16:29 schrieb Mikhail Kuzminsky:
In message from Reuti (Wed, 19 Aug
2009 21:07:19 +0200):
Maybe the disk id is different form the one recored in /etc/
fstab. Wh
Am 20.08.2009 um 16:29 schrieb Mikhail Kuzminsky:
In message from Reuti (Wed, 19 Aug
2009 21:07:19 +0200):
Maybe the disk id is different form the one recored in /etc/fstab.
What about using plain /dev/sda1 or alike, or mounting by volume
label?
At the moment of problem /etc/fstab, as
In message from Reuti (Wed, 19 Aug 2009
21:07:19 +0200):
Maybe the disk id is different form the one recored in /etc/fstab.
What about using plain /dev/sda1 or alike, or mounting by volume
label?
At the moment of problem /etc/fstab, as I understand, isn't used. And
/dev/sda* files are not
Am 19.08.2009 um 19:12 schrieb Mikhail Kuzminsky:
As it was discussed here, there are NUMA problems w/Nehalem on a
set of Linux distributions/kernels. I was informed that may be old
OpenSuSE 10.3 default kernel (2.6.22) works w/Nehalem OK in the
sense of NUMA, i.e. gives right /sys/devices/
As it was discussed here, there are NUMA problems w/Nehalem on a set
of Linux distributions/kernels. I was informed that may be old
OpenSuSE 10.3 default kernel (2.6.22) works w/Nehalem OK in the sense
of NUMA, i.e. gives right /sys/devices/system/node content.
I moved Western Digital SATA HDD
