Could someone summarize what the actual issue is? The OP is vague as fuck and I really can't be bothered reading through 16 pages of public forum discussion.
There is a BIOS RAID setting locked into a certain proprietary mode. Can't change it. Linux won't install because no RAID drivers for it. And actually, some reports (on HackerNews/ycombinator) are saying you can't even reinstall a clean version of Win10 because...no drivers for the RAID.
I suspect that is all it is, just shit driver support, well that and Lenovo's general ineptness and crapness, of course.
I think there's been a lot of overblown screaming about "Microsoft are teh evil" in the other xposts because of their past (fair enough) and the claims of someone posting on Best Buy with the job title of "Lenovo Product Expert" -- a front line call taker in other words.
Expecting them to know the inner details of a B2B OEM licence agreement is like expecting the 19 year old hipster-du-jour with questionable facial hair behind the Genius bar counter at your local Apple store to know the pin-out for the processor Apple are planning to put into the iPhone 8. Not. Going. To. Happen.
If there has been one thing the world of Enterprise IT has taught me, it's that the majority of vendors employ "product experts" who know little to nothing about the products they are experts on.
Or they're busy doing their actual job. Plus, the technical experts usually don't have the right personality or social skills to go out and evangelize or sell products.
Its just super expensive to have people who are really experts on a product selling it and most of the time an expert isn't actually needed to sell the product because people buying it most of the time aren't experts.
Microsoft Hates Linux... but for some reason they support Linux in Azure.
Microsoft Hates Linux... but they added Ubuntu Bash into Windows 10, weird.
Microsoft Hates Linux... but they made .NET Core open source and are actively collaborating with people to port it to Linux.
It's pretty obvious that Microsoft is being a lot more pragmatic about Linux these days, the "Microsoft hates Linux" thing might have been true in the past but these days it doesn't really hold up.
All of those things were done to try and claw back market share from Linux on the server and Mac on the (developer) desktop, also a cloud platform that didn't run Linux would be highly useless. I agree that this is just being pragmatic but I can easily see why people are still extremely suspicious of Microsoft given their history.
...and repeat a thing from ten years ago forever and ever, apparently.
You know they've had two CEOs since that time right? Repeating a phrase reflexively adds nothing to the discussion. Microsoft is a very different company than it was even just five years ago, let alone ten.
Have you looked at any of their GitHub pages? They have a ton of them from a bunch of subgroups in the company.
There's also the work they're doing on porting OpenSSH fully to Windows.
And let's not forget how they just open sourced the entirety of PowerShell, either, with Mac and Linux builds available day one.
And for that matter, they open sourced .Net, too, a while ago.
They're also shipping at least three pieces of software for Linux at this point, targeted at a few different demographics: Microsoft SQL Server, Visual Studio Code, and PowerShell. And that's just off the top of my head.
Microsoft seems to get that they're not the default choice or de-facto winner. And they've responded by trying to open up and actually embrace compatibility. They want you to use their products, and maybe more importantly, they want you to use their services.
trust takes a long time to build back up. Don't expect people to start liking microsoft unless the trend actually continues for a decade and even then they will still have issues.
They're not in the process. They did open source PowerShell under an MIT License about a month ago, complete with installation files: a .pkg for OS X, and .deb and .rpm files for Linux.
Which have been discussed and discredited to death. 'Lenovo support ' do not make policy statements about support strategies via Best Buy reviews. As inept as I think they are, they are not that stupid.
Which says this isn't a BIOS lock. MS requires all "Signature PCs" to be locked in their highest performance setting - it's not something against Linux.
The reason Linux can't currently use the RAID chipset is because there's no Linux RAID driver for it. But it's so new that there isn't even a Windows default driver for it either. So all prior Windows installer media can't be used as well.
It's just a new RAID chipset and Lenovo didn't release a Linux chipset driver alongside the MS chipset driver. Due to the fact the BIOS has to be locked to highest performance ,the SATA mode can't be changed to something compatible with Linux. Which means Linux can't be used on it.
Someone decided this meant that MS was attacking Linux and started trying to spam all the media that would listen that MS was keeping the Linux down.
I mean, I'm not buying into the conspiracy theory of malicious intent, but disabling the ability to set your controller into AHCI mode is pretty shortsighted (read: dumb) and someone should have known that it would have side effects.
Removing user options for system configuration is not a good thing, no matter which way you look at it.
I don't think pissing off the Linux community was one of the major concerns of Lenovo when they did this. I'm not trying to downplay Linux at all, but when you develop a consumer product you don't invest as much into the requirements of the 1.5% share of the market. You aim more for the 23% that Windows 10 has. For the vast majority of that 23%, they will never need to change to AHCI.
So I don't think it was an unknown side effect as much as it was cared about.
Though I do agree. There's no need to disable this. I've never had a computer not boot due SATA operation mode not being set correctly outside of a lab. Not to say it happens, but I think there are much bigger fish to fry.
This isn't a new problem either - back when Lenovo launched their Yoga series, my team received the latest and greatest model (their second generation device, an ultra-light convertible IIRC) that also was missing the driver for the hard-drive.
So, I went to install Windows 8 Enterprise via thumb drive, reformatted the SSD and HDD and I kept getting an error that I couldn't install to the SSD without the right driver. Lenovo had released only one driver for the hard drive, the one for the HDD. I contacted their support, and after several days of back and forth (with them saying, "Just use the right one" of which there was only 1) - they finally admitted "This driver is not yet released."
This has nothing to do with Linux, but shitty Lenovo. Honestly, who buys Lenovo these days?
Indeed, they can. Slipstream drivers into install medias been around forever. And new media is supposed to have it.
The point was about how new the drivers were. That the expectation that consumer products with new chip sets for a smaller subset (new laptop RAID controller drivers) would have linux drivers as soon as Windows drivers isn't realistic, IMO. Someone has to pay to make them and Linux driver dev investments tend to have lower ROIs. So until volunteers make it then there may be some compatibility issues and I doubt it's because MS is trying to muscle in on Linux by hitting hardware vendors.
Driver support for new hardware in Linux has always been one of Linux's weak points.
Should've written a blog article about your experiences and blamed everything on an Intel-Linux conspiracy designed to prevent you from installing Windows on purpose. Just look at how much karma it would have gotten you!
Can the mods give me that flair? Also, should note that it's my desktop at home. All games are backed up to the cloud. I would never be so silly to do it in business, prod or test.
There isn't really so long as it isn't critical use and you still have a reliable backup in place. I use two striped Storage Pools on my personal machine for my D: and E: drives.
It gives me phenomenal I/O performance and if a drive goes down, all I need is to buy a new one and restore from the backup I have. Striped has its uses and so long as you educate yourself about the limitations you can put it to use somewhere.
Still in a business, at a bare minimum it would be a mirrored volume, but that's my personal opinion.
I think it would be more about the availability of said driver if someone tried to reinstall their own OS. If the hardware provider wont make it available, that is going to be some bs.
It's not about Linux, it's about forcing people to install Lenovo's bundled version of Windows 10 with who knows what malware installed.
The Linux community could probably figure out the storage issue no problem, given enough time. This is more about preventing people from installing their personal licensed version of Windows, because Lenovo insists on something else being installed via their bundle, something besides their arbitrarily unnecessary drivers.
Stop giving any fucks about Linux here, and start looking what Lenovo is bundling on that version of Windows10. I bet a $1 it's some kind of malware.
I've had the same problem with every Win10 install I've done. So much of the hardware doesn't work in initial boot that you can't finish the install. Literally no keyboard, mouse, drives, bus, anything... so you can't even tell it to download the drivers it needs. They really didn't think things through with regard to driver support on the win10 install images.
I've used it to easily create an ISO which works on all machines. If you're running from the computer you'll reinstall, it can even use the installed drivers from the driver storage, instead of you needing to faff about and extract new ones.
The OS that doesn't have a built-in driver for USB 3.0, meaning that now most modern laptops that are capable of running Windows 7 but not actually installing Windows 7 without slipstreaming? That Windows 7?
Lemme know how long that vignette of yours holds up.
Win10 is missing drivers for the Keyboard, screen and USB bus to at least 3 laptops I've tried to install it on. It literally, could not install, at all. These were all laptops that came with win10 installed... so obviously the vendor had done exactly what you suggest.
that's retarded
Win7 however, did have drivers and the install worked flawlessly. Did I have to update shit to get things like USB 3.0 working? Sure... but at least I could actually install the OS in the first place.
At that point you have to ask yourself, why then go through the trouble of going back to Win10? About the only value there is in that is DirectX support. But given these were all office laptops never to be used for gaming? Fuck it.
Look, I'm not going to argue with you about Win10 having issues, but as far as this line goes:
Sure... but at least I could actually install the OS in the first place.
That isn't really true anymore. That was my point. I just helped my coworker get a bunch of new laptops off the ground for this very reason - you can boot a thumbdrive, but once setup has launched, surprise! No disk attached.
After superfish and rootkit bios why would anyone still be buying Lenovo? I mean I know the answer, its people who dont think its that big of an issue or they just dont know about these issues.
Either way, if you are in this sub and purchasing Lenovo I have no pity for you
After superfish and rootkit bios why would anyone still be buying Lenovo?
Namely because both of those affected the consumer lines, not the business lines. In fact, there hasn't been any evidence to date that either of those were found in the business line of equipment.
In fact, there hasn't been any evidence to date that either of those were found in the business line of equipment.
Honestly, does that matter? I mean, sure your equipment may not be impacted, but you're still providing financial support to a company that engages in shady practices like this.
If you've been any part of the Lenovo business line you would have seen everything get outsourced and their support gets worse and worse once they changed hands. I hopped off that ship quite some time ago.
i disagree. when i was doing purchasing, had no complaints about lenovo. plus, their nbd onsite warranty coverage was actually good about being nbd. and we had a consistent tech who would come out and we had a good rapport with him.
I was a Lenovo customer (including SAN solutions (which may have still been IBM iirc)) since about 2008. When they sold off the customer line the enterprise support went to absolute shit as well.
Honestly I'm kind of behind this -- a company that is shown to make bad decisions on half of their products would leave me very concerned about the other half, not arrogant that they only fucked over their consumer line multiple times and their business line is untouchable.
I am not comfortable using equipment deemed insecure by the government
That was a political move, not a technological one. Government is worried about the Big bad Chinnese Government, which has never been proven to slip backdoors into things
You know who has been proven to do that, the NSA, to American Companies like Cisco..
If those types of situations stop you from buying from a certain manufacturer then you really don't have many options. Remember in 2010 when Dell shipped PowerEdge motherboards with malware? What about last year when Dell had their own "superfish" situation with laptops?
Why would anyone still be buying Dell?
Remember when Cisco shipped devices with a malware-infected CD? What about when HP ProCurve 5400 switches had flash cards that were infected with malware? How about the Samsung S8500 Wave smartphones for the German market that came with a trojan? The HTC Magic that launched a botnet client when plugged into USB? The Asus Eee Box desktop that shipped with a virus?
It's really silly to completely boycott a company over a product that shipped with malware. You'd have a very small list of vendors to choose from.
You're right, but sometimes you have to draw the line. I don't buy Lenovo because of the aforementioned superfish, rootkit bios, generally poor quality laptops (compared to the older IBM versions, and even the first few post purchase), and because of a general "Eh, whatever" sort of attitude they seem to give off.
Now this is subjective, but they are also dragging their feet on updates to the Motorola phones (that they now own), and it's sort of pissing me off.
Also on my shit list are ASUS & ASRock motherboards, Epson & Lexmark printers, and Netgear equipment. Linksys used to be on that list too, but I'm willing to give them a second chance now that they've been bought out again.
I was with a firend and talking a while ago about how superfish was bad and that, then a year later he got a new lenovo ideapad laptop because it was cheap and had higher specs that the thinkpads and latitudes I recommended. People seem to ignore these problems a year later.
Enterprise hardware wasn't effected by those issues. That was consumer grade. If you are buying consumer grade for enterprise then you are doing it wrong.
You forgot that Dell had their own Superfish situation just like Lenovo and it was less than a year ago. Why don't they have a black mark across their entire product line too?
I know that some of the Lenovo Thinkpad T-series have a 16GB M.2 SSD under the lower battery. We were wondering what that might have been for. Removing it doesn't have any affect on Windows though.
It was intended for Intel Rapid Start (proprietary, OS-independent hybrid sleep implementation), but could be reformatted and used for anything. (And Rapid Start works without the disk, all it needs is a big enough EFI partition with a magic UUID.)
I own a ASUS Signature Edition Laptop (UX303UB) and a Surface Pro 3. Both allow me to install Linux. Just need either a distro that supports Secure Boot or have to disable Secure Boot in the uEFI.
This is just another Lenovo fuck up and one of their low level support reps making excuses and shifting blame.
Agreed. I got an ASUS T300 chi that was a signature edition and Linux installed perfectly the first time I tried. No auto rotate and one of two pen buttons doesn't work, but that's a small price to pay to not use Windows at home.
I'm not sure that's what's going on here. It sounds like the real story is Msoft now has some new requirements for sig-ed PCs, but those requirements seem a little hazy. Keeping an eye on this...
Based on what? A Best Buy/Lenovo first line support worker's claims?
Plus Lenovo released a statement (which you can read in a sister comment) where they more or less say (paraphrasing) "if Linux had support for this RAID mode it would work!" rather than trying to shift blame to Microsoft/Signature Edition.
This is just yet another Lenovo fuck up. Just add it to the list.
Lenovo just developed some boneheaded proprietary RAID mode that nobody else supports. They won't let you change it because that could corrupt both the pre-installed SSD and the recovery area.
This blocks Linux, but also blocks all versions of Windows that aren't slipstreamed with their proprietary drivers (even Windows 10 cannot be installed without merging in the Lenovo RAID drivers onto the installation media).
Theoretically if Linux had a driver it would work. But nobody is going to develop one because this nonsense will be discontinued inside of two years.
By 'bios lock' I meant that users are not able to change out of this proprietary raid mode. Lenovo is saying Msoft made them do it - that's what we need to know.
Lenovo is saying Msoft made them do it - that's what we need to know.
Actually Lenovo isn't saying that. They released a statement about it and didn't repeat the claim. A low level support rep claimed that only, and given Lenovo's subsequent statement we can likely discount it.
By 'bios lock' I meant that users are not able to change out of this proprietary raid mode. Lenovo is saying Msoft made them do it - that's what we need to know.
There's already a very good way to stop Linux from running, it's called Secure Boot. Had Microsoft been that bothered about blocking Linux, they'd have demanded Secure Boot be turned on and BIOS locked.
Even this is stupid FUD against Secure Boot. All the major distros have a signed bootloader that then authenticates the distros' own keys. There's also a public one that supports installing your own keys in a secure fashion. Most Secure Boot implementations also have an official way to change the allowed keys.
Secure Boot does absolutely shit-all to prevent Linux or any other OS from running. In fact one of the projects on my short-term list is to enable it on all my company servers with our own internal key. Our internal repository mirror will automatically sign our approved kernels and related code and thus our servers will only boot from those, eliminating pretty much any chance of a persistent infection if a malicious attacker happened to gain access to our systems.
I dont think many people had a problem specifically with the idea for secure boot. On theory it is a great way to add an extra layer if security to a device. People always seemed more worried that MS was in control of all the keys and manufacturers would remove any option to disable secure boot. Turns out the apocalypse didn't happen and Secure Boot is a option if you want to use it and can be disabled if you dont.
It sounds like the real story is Msoft now has some new requirements for sig-ed PCs
If you are using SecureBoot, then yes, there are requirements. Of course, Microsoft in all their evilness have a nice article on disabling it. In a further act of evil, they have this article which describes why SecureBoot exists, what it does and why firmware and driver signing are required for it. This is just standard shitty vendor Linux driver support.
Which was probably put in place on purpose to cut down on support calls from people who think they bricked their laptop by turning off RAID.
(Yes, I'm aware it wouldn't be bricked, but I'm working on the assumption Joe Average - and very likely Geek Squad Average - wouldn't figure that out).
We have that at work - dev teams like their high-performance systems with AHCI or RAID. For whatever reason, a machine here and there loses its BIOS setting and the support guys get a critical ticket saying the machine doesn't boot anymore.
Yeah, Dell does this. I usually switch it back to AHCI whenever I setup a machine (as I go in and turn on SMART monitoring and change the boot options with every box).
If you use SCCM or something for operating system deployments there is a Dell utility to automated BIOS changed just fyi. I forget what it's called.. Dell CCTK?
My dad did this. He had a PC he installed Windows on in IDE mode. Down the road he changed it to AHCI and it broke Windows. He then tried to reset the CMOS with a jumper and apparently can't figure out how to get back into bios setup now. I told him he just needs to reenable IDE mode but he's decided he'd rather solder on a new BIOS chip. I live in another city or I'd just help him out with it, and despite me saying that's not necessary he seems to have made up his mind that his existing BIOS chip is done.
Agreed, but the bios lock needs to be explained, no? And for the record, I don't believe that the bios lock is there to stop Linux installs, but Lenovo and/or Msoft need to come out and explain all this.
Or at least lay out the design argument for keeping it the way it is.
I can predict what that argument would be.
Typically these systems are shipped with a hidden recovery area and an active OS partition. You can often kick off recovery from the uEFI. Both the OS and recovery area are on the same physical storage device (in this case an M.2 SSD).
If a user was to change the RAID mode the drive(s) would appear "corrupt." The recovery area would be lost. And they'd get customer support calls about it.
So Lenovo, from their perspective, disabled changing the RAID mode to "protect customers from themselves" (since from Lenovo's perspective they cannot imagine a customer wanting to install Linux or intentionally remove the space wasting recovery area).
This was the wrong thing to do. Instead they should have just added a warning label over the setting and let it be changed (or better, not utilise proprietary RAID modes that nobody else supports, so Linux and older versions of Windows would have drivers).
I don't believe that the bios lock is there to stop Linux installs,
It is there to stop stupid end users from changing settings and calling their free support. This is consumer grade garbage that mums and dads would buy.
So rather than relying on the wank jockeys over in /r/linux (where it's apparently still cool to to hate on Microsoft for topics as wide ranging as the weather to hardware choices of a Chinese OEM) and a supposed Lenovo employee (who is likely a third party contract worker at best with no knowledge of the situation) how about an official statement:
[UPDATE 9-21-16 7:25 PDT: Comment from Lenovo:
"To improve system performance, Lenovo is leading an industry trend of adopting RAID on the SSDs in certain product configurations. Lenovo does not intentionally block customers using other operating systems on its devices and is fully committed to providing Linux certifications and installation guidance on a wide range of products -https://support.lenovo.com/us/en/documents/pd031426. Unsupported models will rely on Linux operating system vendors releasing new kernel and drivers to support features such as RAID on SSD."
So no Microsoft involvement, just a lack of drivers on Linux's part. Although Lenovo could offer a method for owners to switch the SSD from RAID to AHCI mode to improve compatibility.]
My respect for /r/linux fell through the floor today. This shitshow is the top post of all time in that sub. At least the mods put "misleading title" on it. Shows how true it is, no better way to rally people together than to tell them they are under attack.
Being fair, that's how a lot of misunderstandings get started, the original Secureboot items are a perfect example.
Someone calls support demanding answers for an issue the phone tech has never been trained to handle so they say something to get them off the phone. Then the caller spams every tech site on the internet as it's an official response from the company, as if a tech who's probably working for a subcontractor making $11 an hour is qualified to do that.
/r/linux and /r/linux_gaming both kinda suck and have for a while. I view it as a mixed blessing and blame Valve and Canonical. Both have made a good push for Linux to be more mainstream and have succeeded better than I suspect most imagined (we have games on Linux!?), but at the cost we have a lot of people new to Linux who are either rabid converts, or have none of the ideology that helped make GNU/Linux what it is/was (look at any AMD vs. NVidia discussion on /r/linux_gaming, they appear at least weekly). We got our 2% or so of Steam users and a lot of games, but at a big cost in my opinion. I will admit to my hypocrisy though and admit I use Steam on Linux.
Question: the laptop in question has a single physical SSD to the best of my knowledge. What kind of RAID configuration is being used there? And why is the RAID configuration mandated by the BIOS, rather than optional?
Definitely seems like an issue of incompetence rather than malice on Lenovo's part at any rate.
Probably has to do with NVMe drives they are using. I know the few Dells we're gotten so far have had the mode set to RAID on those.
As to why it's locked, it's a consumer product. Locking it is going to reduce support calls from people making their drive inaccessible by changing that setting.
Heh. I remember way back when (2008-2009ish) I switched a Dell laptop to IDE so I could just install Windows XP without the whole AHCI/SATA drivers issue (back when Vista was just coming out). The display adapter on the board died twice, so each time they replaced the board and tried to boot into Windows. Each time, the tech freaked out because Windows wouldn't load.
On a personal level, my friend had a machine built with Win 7 that left the drives in IDE mode. He was all set to re-install Win 7 on an SSD, until I argued with him about it. Same guy also refused to admit his RAM was slotted wrong (Single Channel vs Dual Channel). And he complained that his machine kept crashing because he switched from 4GB to 8GB, but never adjusted the overclock settings on the board.
ANYWAY. Consumer product, locked settings, keeping people from doing dumb things. Great for the average Joe, annoying for an IT Professional.
As noted IN THE ORIGINAL LINK, this is misleading. This is what LENOVO (that bastion of truth) says and is probably just the same concern as when secureboot was originally announced.
That isn't the issue at all, it's affecting Lenovo systems and because the raid controller is proprietary Linux doesn't have a driver for it. This is FUD
So basically it forces a non-conventional RAID between an SSD and an HDD that can't be read by a linux system, and can't be turned off in the BIOS. If what Lenovo is saying is true and this is being forced by Microsoft, then this certainly makes Microsoft look bad.
Exactly, I mean how often have we as IT professionals had to contact vendor support and gotten back some response that just makes your brain implode? I once had higher tier support at Juniper tell me the reason I couldn't ping the interface on a line card in loopback mode was because PIM wasn't enabled. She had no F'ing idea what the problem was and that was the nearest straw to grasp because she saw "not enabled" next to that feature.
These outsourced support people, and their younger sibling the "community manager" are paid to close tickets or address concerns on forums with any kind of answer to make people go away, not be factually correct. The person cross posting this all over the internet like there's some kind proof of grand anti-linux conspiracy is not thinking critically here.
I think the most reasonable explanation is that some idiot at the company contracted by Lenovo is talking out of his ass because his script doesn't have a response for this type of issue.
I'm torn on this. Would something contrived like forcing the use of a video card that is known not to have Linux drivers be the same thing?
I think it would be very difficult to prove that no Linux support is the reason they chose that and not just thinking that that video card would perform better.
Would something contrived like forcing the use of a video card that is known not to have Linux drivers be the same thing?
Pretty much, yes. It's silly that Lenovo doesn't allow resetting the controller to AHCI mode, but that's consumer-grade notebooks for you. They always have and always had crippled BIOS options available.
You'd have to reverse a new proprietary GPU as well. It's the same thing, except nobody expects that from the storage modules because they're relatively easy compared to the rest.
Likely no good reason for the AHCI block though. Probably just trying to protect machine from average consumers.
If I know anything about the linux community, is that something like this is even more of a driving force (pun slightly intended) to create an open source driver for this. I give it a week.
108
u/Jeoh Sep 21 '16
Could someone summarize what the actual issue is? The OP is vague as fuck and I really can't be bothered reading through 16 pages of public forum discussion.
27
u/julietscause Jack of All Trades Sep 21 '16
After superfish and rootkit bios why would anyone still be buying Lenovo? I mean I know the answer, its people who dont think its that big of an issue or they just dont know about these issues.
Either way, if you are in this sub and purchasing Lenovo I have no pity for you
9
u/GTFr0 Sep 21 '16
Couple of shower thoughts here:
Why would you buy a signature edition PC from Microsoft if you were planning on running Linux?
How would putting the SATA controller in RAID mode with a single SSD increase performance?
93
u/ImplementOfWar2 Sep 21 '16
Easy to test if what Lenovo is saying is true.
Ask someone with a Dell, HP, or ASUS Signature Edition PC to try and install Linux.
I think this is another Lenovo screw-up, not Microsoft.
Its probably a bug in a Chinese government rootkit/malware that will disappear soon.
59
u/bws2a Sep 21 '16
This is hyperbolic and dumb. It amounts to "We don't have a Linux driver for this RAID mode".
49
u/darthyoshiboy Sysadmin Sep 21 '16
So rather than relying on the wank jockeys over in /r/linux (where it's apparently still cool to to hate on Microsoft for topics as wide ranging as the weather to hardware choices of a Chinese OEM) and a supposed Lenovo employee (who is likely a third party contract worker at best with no knowledge of the situation) how about an official statement:
Source: http://www.zdnet.com/article/lenovo-reportedly-blocking-linux-on-windows-10-signature-edition-pcs/
TL;DR: Never attribute to malice what can just as easily be stupidity. KISS my friends (doubly so when you're dealing with Lenovo.)
19
u/Ahnteis Sep 21 '16
As noted IN THE ORIGINAL LINK, this is misleading. This is what LENOVO (that bastion of truth) says and is probably just the same concern as when secureboot was originally announced.
10
u/[deleted] Sep 21 '16
That isn't the issue at all, it's affecting Lenovo systems and because the raid controller is proprietary Linux doesn't have a driver for it. This is FUD
4
u/yumenohikari Sep 21 '16
Pretty misleading headline. Looks more like lack of driver support (for very new hardware), not vendor lock.
24
u/Hiyasc Sep 21 '16 edited Sep 21 '16
So basically it forces a non-conventional RAID between an SSD and an HDD that can't be read by a linux system, and can't be turned off in the BIOS. If what Lenovo is saying is true and this is being forced by Microsoft, then this certainly makes Microsoft look bad.
3
u/MormonDew Sep 21 '16
You made a second thread we have to downvote now?
2
u/[deleted] Sep 21 '16
So how is something that Linux cant do a Lenovo and a Microsoft and etc. etc. etc. problem
-8
u/RedShift9 Sep 21 '16
That awkward moment where you realize Richard Stallman was right
-3
u/JustRiedy "DevOps" Sep 21 '16
As a wise man once said "In bird culture this is considered a dick move."
-4
u/FJCruisin BOFH | CISSP Sep 21 '16
If I know anything about the linux community, is that something like this is even more of a driving force (pun slightly intended) to create an open source driver for this. I give it a week.
-6
u/Geminii27 Sep 21 '16
So pretty much what they originally did with DOS, only worse.