Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.advocacy > #685942 > unrolled thread

Re: It's Alive! Xeon W-1270P Has Booted!

Back to article view | Back to comp.os.linux.advocacy

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: It's Alive! Xeon W-1270P Has Booted! Physfitfreak <physfitfreak@gmail.com> - 2025-02-15 14:18 -0600
    Re: It's Alive! Xeon W-1270P Has Booted! -hh <recscuba_google@huntzinger.com> - 2025-02-16 12:22 -0500
      Re: It's Alive! Xeon W-1270P Has Booted! Physfitfreak <physfitfreak@gmail.com> - 2025-02-16 15:22 -0600
    Re: It's Alive! Xeon W-1270P Has Booted! Farley Flud <ff@linux.rocks> - 2025-02-16 18:36 +0000
      Re: It's Alive! Xeon W-1270P Has Booted! Physfitfreak <physfitfreak@gmail.com> - 2025-02-16 15:40 -0600
        Re: It's Alive! Xeon W-1270P Has Booted! Farley Flud <ff@linux.rocks> - 2025-02-17 09:03 +0000
          Re: It's Alive! Xeon W-1270P Has Booted! Physfitfreak <physfitfreak@gmail.com> - 2025-02-17 11:57 -0600
            Re: It's Alive! Xeon W-1270P Has Booted! Farley Flud <fsquared@fsquared.linux> - 2025-02-17 18:18 +0000
              Re: It's Alive! Xeon W-1270P Has Booted! Joel <joelcrump@gmail.com> - 2025-02-17 13:33 -0500
              Re: It's Alive! Xeon W-1270P Has Booted! Physfitfreak <physfitfreak@gmail.com> - 2025-02-17 13:17 -0600
              Re: It's Alive! Xeon W-1270P Has Booted! Physfitfreak <physfitfreak@gmail.com> - 2025-02-17 13:18 -0600
              Re: It's Alive! Xeon W-1270P Has Booted! Physfitfreak <physfitfreak@gmail.com> - 2025-02-17 13:20 -0600

#685942 — Re: It's Alive! Xeon W-1270P Has Booted!

On 2/15/25 11:15 AM, Farley Flud wrote:
> My fantastic Xeon W-1270P machine has finally booted.
> 
> 
> 


My Xeon machine still crashes when I install linux mint on it. It gets 
installed each time, no problems there, but about one minute into using 
the computer it freezes and screen, computer, keyboard, everything 
becomes non-responsive.

If yours hasn't crashed, then either your cpu is an improved one, or 
there's something about mint that messes mine up.

When I acquire the knowledge to carefully install gentoo on my Xeon 
machine, I'll see whether linux can be used with it or not.

[toc] | [next] | [standalone]

#686088

On 2/15/25 15:18, Physfitfreak wrote:
> On 2/15/25 11:15 AM, Farley Flud wrote:
>> My fantastic Xeon W-1270P machine has finally booted.
>>
>> {deleted:  saga of five weeks of unproductive WIP }
>>
> 
> 
> My Xeon machine still crashes when I install linux mint on it. It gets 
> installed each time, no problems there, but about one minute into using 
> the computer it freezes and screen, computer, keyboard, everything 
> becomes non-responsive.
> 
> If yours hasn't crashed, then either your cpu is an improved one, or 
> there's something about mint that messes mine up.

Sounds like one needs to do a backup, wipe & reinstall to troubleshoot.


> When I acquire the knowledge to carefully install gentoo on my Xeon 
> machine, I'll see whether linux can be used with it or not.

Or there's MS-Windows, of course /s


-hh

[toc] | [prev] | [next] | [standalone]

#686113

On 2/16/25 11:22 AM, -hh wrote:
> On 2/15/25 15:18, Physfitfreak wrote:
>> On 2/15/25 11:15 AM, Farley Flud wrote:
>>> My fantastic Xeon W-1270P machine has finally booted.
>>>
>>> {deleted:  saga of five weeks of unproductive WIP }
>>>
>>
>>
>> My Xeon machine still crashes when I install linux mint on it. It gets 
>> installed each time, no problems there, but about one minute into 
>> using the computer it freezes and screen, computer, keyboard, 
>> everything becomes non-responsive.
>>
>> If yours hasn't crashed, then either your cpu is an improved one, or 
>> there's something about mint that messes mine up.
> 
> Sounds like one needs to do a backup, wipe & reinstall to troubleshoot.
> 
> 
>> When I acquire the knowledge to carefully install gentoo on my Xeon 
>> machine, I'll see whether linux can be used with it or not.
> 
> Or there's MS-Windows, of course /s
> 
> 
> -hh


It has absolutely no problem with Windows. I've tried a few different 
HDs in installing linux mint on it. Never worked, or works fine but for 
about a minute or two. Something builds up and at some point system 
crashes.

I don't like to go back to Windows on that machine. Even with 24 gigs of 
ram it is slow as hell to come up. I literally go get some stuff done in 
the house and come back to see if it has finished booting up. And often 
times some of the icons are still "coming up" and a couple of cats have 
urinated at the screen :) Quite ironic.

I'm not exaggerating.

[toc] | [prev] | [next] | [standalone]

#686092

On Sat, 15 Feb 2025 14:18:51 -0600, Physfitfreak wrote:

> 
> When I acquire the knowledge to carefully install gentoo on my Xeon 
> machine, I'll see whether linux can be used with it or not.
>

It'll work.

However, installing Gentoo is a huge PITA, being almost the same
as installing LFS.

I do not strictly use Gentoo, but only their automated build
system known as Portage.

My strategy has always been to clone my existing installations
onto a new machine.  Ideally, this would involve cross compiling
which is another PITA.  But if the new CPU ranks above the old
CPU then a straightforward copy will allow the new machine to
boot with the old software packages.

In my current case, however, I assumed that the Xeon W-2223
would be identical, except for AVX-512, with the Xeon W-1270P.
However, it is not and the new machine would not boot using
software compiled on the Xeon W-2223.

I had to fall back to the Core i7 machine to build the software
and in this way the new Xeon W-1270P now boots.  The Core i7 is
"below" the Xeon W-1270P.

The next step is to use Gentoo Portage to rebuild everything
(i.e. the "world") according to the Xeon W-1270P specs.

My approach is totally unconventional but it works magnificently.
I eschew both systemd and SysV for booting and use my own boot
scripts (derived from LFS).  Gentoo Portage is used only for
automated building.  Otherwise my systems are not Gentoo.

I should post my unique GNU/Linux "distro" to GitLab, but
most users are lackeys and would never take notice.

Yes, my systems are different from any other GNU/Linux
"distro."  I should perhaps create "Farley's Fantastic Linux"
but, as I already indicated, the lackeys would never notice.




-- 
Systemd: solving all the problems that you never knew you had.

[toc] | [prev] | [next] | [standalone]

#686118

On 2/16/25 12:36 PM, Farley Flud wrote:
> On Sat, 15 Feb 2025 14:18:51 -0600, Physfitfreak wrote:
> 
>>
>> When I acquire the knowledge to carefully install gentoo on my Xeon
>> machine, I'll see whether linux can be used with it or not.
>>
> 
> It'll work.
> 
> However, installing Gentoo is a huge PITA, being almost the same
> as installing LFS.
> 
> I do not strictly use Gentoo, but only their automated build
> system known as Portage.
> 
> My strategy has always been to clone my existing installations
> onto a new machine.  Ideally, this would involve cross compiling
> which is another PITA.  But if the new CPU ranks above the old
> CPU then a straightforward copy will allow the new machine to
> boot with the old software packages.
> 
> In my current case, however, I assumed that the Xeon W-2223
> would be identical, except for AVX-512, with the Xeon W-1270P.
> However, it is not and the new machine would not boot using
> software compiled on the Xeon W-2223.
> 
> I had to fall back to the Core i7 machine to build the software
> and in this way the new Xeon W-1270P now boots.  The Core i7 is
> "below" the Xeon W-1270P.
> 
> The next step is to use Gentoo Portage to rebuild everything
> (i.e. the "world") according to the Xeon W-1270P specs.
> 
> My approach is totally unconventional but it works magnificently.
> I eschew both systemd and SysV for booting and use my own boot
> scripts (derived from LFS).  Gentoo Portage is used only for
> automated building.  Otherwise my systems are not Gentoo.
> 
> I should post my unique GNU/Linux "distro" to GitLab, but
> most users are lackeys and would never take notice.
> 
> Yes, my systems are different from any other GNU/Linux
> "distro."  I should perhaps create "Farley's Fantastic Linux"
> but, as I already indicated, the lackeys would never notice.
> 
> 
> 
> 


Go for it. Right now I don't even know what you're talking about. But if 
I take a step toward finding whether my Xeon computer works with linux 
then I will have to take that opportunity to delve inside everything 
about workings of linux. Otherwise it won't be worth the effort, I feel.

I wanted to do this about 2 years ago but got distracted by political 
events, which are always injected into me each time I video-talk live 
with folks in Iran.

[toc] | [prev] | [next] | [standalone]

#686133

On Sun, 16 Feb 2025 15:40:21 -0600, Physfitfreak wrote:

> 
> But if 
> I take a step toward finding whether my Xeon computer works with linux 
> then I will have to take that opportunity to delve inside everything 
> about workings of linux. Otherwise it won't be worth the effort, I feel.
> 

Get a copy of the Gentoo LiveGUI USB:

https://www.gentoo.org/downloads/

Write the ISO file to a USB thumb drive:

https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Media#Writing_a_bootable_USB

Basically, the command is:

dd if=livegui.iso of=/dev/sdX bs=4096 status=progress && sync

You just need to know what drive (/dev/sdX) is the USB.

After booting the LiveGUI, your Xeon will work.





-- 
Systemd: solving all the problems that you never knew you had.

[toc] | [prev] | [next] | [standalone]

#686167

On 2/17/25 3:03 AM, Farley Flud wrote:
> On Sun, 16 Feb 2025 15:40:21 -0600, Physfitfreak wrote:
> 
>>
>> But if
>> I take a step toward finding whether my Xeon computer works with linux
>> then I will have to take that opportunity to delve inside everything
>> about workings of linux. Otherwise it won't be worth the effort, I feel.
>>
> 
> Get a copy of the Gentoo LiveGUI USB:
> 
> https://www.gentoo.org/downloads/
> 
> Write the ISO file to a USB thumb drive:
> 
> https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Media#Writing_a_bootable_USB
> 
> Basically, the command is:
> 
> dd if=livegui.iso of=/dev/sdX bs=4096 status=progress && sync
> 
> You just need to know what drive (/dev/sdX) is the USB.
> 
> After booting the LiveGUI, your Xeon will work.
> 
> 
> 
> 
> 


My Xeon works fine with Knoppix on a USB drive too. I want to use it 
with a full-featured linux os installed on the HD, not from a USB, if 
that's what you're telling me to do.

[toc] | [prev] | [next] | [standalone]

#686169

On Mon, 17 Feb 2025 11:57:24 -0600, Physfitfreak wrote:

> 
> 
> My Xeon works fine with Knoppix on a USB drive too. I want to use it 
> with a full-featured linux os installed on the HD, not from a USB, if 
> that's what you're telling me to do.
>

I was just giving you a way to test it.

On a system where you experience failure, you need to examine the log
messages, which on a SysV init system are located in /var/log.
You should have a look at /var/log/kernel.  Also you may want to increase
the log level to capture more output.

On a systemd init, however, things are much different and I know nothing
about systemd.  Maybe others on this group can let you know how to read
the systemd logs.

But the news that a Xeon CPU fails with GNU/Linux is very surprising.
Basically, failure should not occur.




-- 
Hail Linux!  Hail FOSS!  Hail Stallman!

[toc] | [prev] | [next] | [standalone]

#686170

Farley Flud <fsquared@fsquared.linux> wrote:
>On Mon, 17 Feb 2025 11:57:24 -0600, Physfitfreak wrote:
>
>> My Xeon works fine with Knoppix on a USB drive too. I want to use it 
>> with a full-featured linux os installed on the HD, not from a USB, if 
>> that's what you're telling me to do.
>
>I was just giving you a way to test it.
>
>On a system where you experience failure, you need to examine the log
>messages, which on a SysV init system are located in /var/log.
>You should have a look at /var/log/kernel.  Also you may want to increase
>the log level to capture more output.
>
>On a systemd init, however, things are much different and I know nothing
>about systemd.  Maybe others on this group can let you know how to read
>the systemd logs.
>
>But the news that a Xeon CPU fails with GNU/Linux is very surprising.
>Basically, failure should not occur.


You are such a lame-ass.

-- 
Joel W. Crump

Amendment XIV
Section 1.

[...] No state shall make or enforce any law which shall
abridge the privileges or immunities of citizens of the
United States; nor shall any state deprive any person of
life, liberty, or property, without due process of law;
nor deny to any person within its jurisdiction the equal
protection of the laws.

Dobbs rewrites this, it is invalid precedent.  States are
liable for denying needed abortions, e.g. TX.

[toc] | [prev] | [next] | [standalone]

#686176

On 2/17/25 12:18 PM, Farley Flud wrote:
> On a systemd init, however, things are much different and I know nothing
> about systemd.  Maybe others on this group can let you know how to read
> the systemd logs.



Hahhahhahh :-) Don't forget that my dick has rendered them mere shadows 
of their former selves :)

Hahhahhahh :-)

I bet they're attending Church more often than before my dick 
relentlessly poked their stupid brains.

That's what happens when you try to educate the inherently stupid.

[toc] | [prev] | [next] | [standalone]

#686177

On 2/17/25 12:18 PM, Farley Flud wrote:
> But the news that a Xeon CPU fails with GNU/Linux is very surprising.
> Basically, failure should not occur.


The CPU is old, from 2009 I think.

[toc] | [prev] | [next] | [standalone]

#686178

On 2/17/25 12:18 PM, Farley Flud wrote:
> On a system where you experience failure, you need to examine the log
> messages, which on a SysV init system are located in /var/log.
> You should have a look at /var/log/kernel.  Also you may want to increase
> the log level to capture more output.


I'll keep this post to use it later. Right now I've got floors to mop!

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.advocacy

csiph-web