https://hardware.slashdot.org/story/16/09/21/1516230/microsoft-signature-pc- requirements-now-blocks-linux-installation-reports?sbsrc=md
It was nice while it lasted.
<sigh>
Wow, is MS desperate or something?
On Wed, Sep 28, 2016 at 11:24 AM, Francis Gerund via arch-general arch-general@archlinux.org wrote:
https://hardware.slashdot.org/story/16/09/21/1516230/microsoft-signature-pc- requirements-now-blocks-linux-installation-reports?sbsrc=md
It was nice while it lasted.
<sigh>
If anything, it's intel being asswipe lazy to not upstream linux drivers for this new raid mode.
cheers! mar77i
On 28/09/16 17:24, Francis Gerund via arch-general wrote:
https://hardware.slashdot.org/story/16/09/21/1516230/microsoft-signature-pc- requirements-now-blocks-linux-installation-reports?sbsrc=md
It was nice while it lasted.
<sigh>
Actually, this story is a bit old and misleading. This has nothing to do with Microsoft, but mostly *Intel* and probably a bit to Lenovo. It's Intel's fault that this happens, as Lenovo's MS signiture device has BIOS locked into RAID mode, and this is not supported by Linux as the drivers are not provided by Intel.
The reason Lenovo did this is to achieve lower power consumption + temperature using this proprietary technique. Obviously, they did not care much about Linux when making that decision. It would have been nice if they let users change the BIOS option at their own risk, even if it would cause harm to the devices' integrity.
Cheers, Kwang
On Wed, 28 Sep 2016 11:24:25 -0400 Francis Gerund via arch-general arch-general@archlinux.org wrote:
https://hardware.slashdot.org/story/16/09/21/1516230/microsoft-signature-pc- requirements-now-blocks-linux-installation-reports?sbsrc=md
It was nice while it lasted.
<sigh>
They don't "block" Linux. They are using a higher performance RAID setup that there's simply no Linux driver for yet. Once someone creates one, you'll be able to install Linux. This is normal with new hardware, it happens all of the time.
I'm not gonna lie, this is all a tad technical even for me, but wouldn't intsalling an AMD chip solve the issue?
On Wed, Sep 28, 2016 at 11:45 AM, Doug Newgard scimmia@archlinux.info wrote:
On Wed, 28 Sep 2016 11:24:25 -0400 Francis Gerund via arch-general arch-general@archlinux.org wrote:
https://hardware.slashdot.org/story/16/09/21/1516230/microsoft-signature-pc- requirements-now-blocks-linux-installation-reports?sbsrc=md
It was nice while it lasted.
<sigh>
They don't "block" Linux. They are using a higher performance RAID setup that there's simply no Linux driver for yet. Once someone creates one, you'll be able to install Linux. This is normal with new hardware, it happens all of the time.
2016/09/29 1:22 "D C via arch-general" arch-general@archlinux.org:
I'm not gonna lie, this is all a tad technical even for me, but wouldn't intsalling an AMD chip solve the issue?
On Wed, Sep 28, 2016 at 11:45 AM, Doug Newgard scimmia@archlinux.info
wrote:
On Wed, 28 Sep 2016 11:24:25 -0400 Francis Gerund via arch-general arch-general@archlinux.org wrote:
https://hardware.slashdot.org/story/16/09/21/1516230/microsoft-signature-pc-
requirements-now-blocks-linux-installation-reports?sbsrc=md
It was nice while it lasted.
<sigh>
They don't "block" Linux. They are using a higher performance RAID
setup that
there's simply no Linux driver for yet. Once someone creates one,
you'll be
able to install Linux. This is normal with new hardware, it happens all
of the
time.
-- Public_Key_Block.asc
hmm. Interesting. rather " 'driver' should be included inside kernel, or not" will separates priority and difficulty... All we need is wait. I assume.
On 28.09.2016 17:24, Francis Gerund via arch-general wrote:
<sigh>
That was my reaction when I saw you post a long debunked FUD story to this list. The problem lies with Intel and Lenovo, not Microsoft, and it was not a malicious move against Linux, no matter how hard you want to be the victim here. If you want to run on modern computers, keep up with hardware developments, otherwise you're just dragging everyone else down.
Stop getting your only source of information from shit websites with shit users such as slashdot.
On Thu, Sep 29, 2016 at 11:58 AM, Nicolas F. archlist@fratti.ch wrote:
On 28.09.2016 17:24, Francis Gerund via arch-general wrote:
<sigh>
That was my reaction when I saw you post a long debunked FUD story to this list. The problem lies with Intel and Lenovo, not Microsoft, and it was not a malicious move against Linux, no matter how hard you want to be the victim here. If you want to run on modern computers, keep up with hardware developments, otherwise you're just dragging everyone else down.
Stop getting your only source of information from shit websites with shit users such as slashdot.
Ouch!
Okay . . . then would you please recommend one or more sites that you consider less "shit" than Slashdot?
arch-general@lists.archlinux.org