13 ms·
I think this is basically what OSX has had forever. And I think this is one of those things that's _really_ easy to miss how big of a deal it is in making the e
by Waterluvian 8y ago
I think this is basically what OSX has had forever. And I think this is one of those things that's _really_ easy to miss how big of a deal it is in making the experience feel solid.
My Ubuntu 16.04 machine does this weird thing where it shows my login in 1/4 of the screen then suddenly it stretches to fill. Really sets the tone for how janky the experience is going to be.
The startup experience sets the tone for the entire thing. I know some engineers who won't get why it's a big deal. It's a _big_ deal.
- hannasanarion 8y agoIt's probably been such low priority in the Linux community because most of us are big nerds and we like seeing different technologies interact, it can be nice to be able to see the boot sequence bios>bootloader>OS>Desktop. OSx does the same thing, but hides it all behind a single load screen, as if all of those elements from hardware to DE were a monolithic "mac". It feels like lying to the user to me. Bios isn't in control anymore, why is the motherboard logo still on the screen? How do I know when the OS takes over from grub if both are hidden under the motherboard logo?
- another-cuppa 8y agoTrue that. I want to see the output of OpenRC when I boot to make sure it all looks familiar (I only reboot after a kernel upgrade really). Then I login and type startx. I understand I'm completely out of touch with how normal people use computers. I don't care.
- rayiner 8y ago> True that. I want to see the output of OpenRC when I boot to make sure it all looks familiar (I only reboot after a kernel upgrade really). Then I login and type startx. What's wrong with dmesg?
- derefr 8y agoYou can still see the output of your kernel and init system... on the serial console. Personally, I wish serial-over-USB (and serial-over-Lightning) cables were more common. (I don't mean that they're expensive—they're dirt cheap. It's just that nobody has any idea they exist.) They used to be a kind of arcane thing—why would you need serial access over USB when the PC already has a serial port? And why are you debugging a PC on another PC—(taking up a quite lot of space on your desk, eh?)—when you could instead debug the PC on the PC itself? But these days, almost nothing has a serial port, and we have perfect "secondary PCs" to serve as the recipient of the serial input: our phones and tablets. (Heck, they probably have space reserved for them on your desk already!) Imagine: sit an iPad or some cheapo Android tablet below your monitor. Plug the "send" end of the serial-over-USB cable into the USB hub built into your monitor. Plug the "receive" end of the cable into your tablet. Open a terminal-emulator app on your phone/tablet. Bam: console logs, flowing along below your PC, as needed. Best of all, it's not unidirectional; your phone/tablet is now a VT100, and you can log into your computer over it, even if the display server or login manager or desktop environment is wedged. If owning these little cables was common, I'd honestly suggest just turning off the Linux text-console virtual framebuffers entirely for the Desktop versions of distributions. You want to see what's going on underneath the gloss? Tap in.
- Dylan16807 8y agoI'm not really impressed by that idea. Pretend I copied your whole post, except it's about wanting to run a web browser. It's so convenient to grab an entire different device to tether into your computer to browse on, why would you want to use the built-in screen for browsing?
- apetresc 8y agoHuh? Because you want to see/interact with what's on the screen approximately 100% of the time when browsing, but a tiny percentage of the time (only when something's broken) when booting.
- Dylan16807 8y ago
- LordDragonfang 8y ago>It feels like lying to the user to me I think it's fair to say that in general, users want to be lied to. That's why UX patterns like screenshots of suspended apps being displayed while the app actually loads became standard. The appearance of speed is effectively as valuable as actual speed, just like the appearance of polish is valuable regardless of the cruft that lies beneath it.
- FullyFunctional 8y agoLying has nothing to do with it. Users don't _care_ about the details of what the system is doing and it's just cognitive noise, distracting from the task at hand. The suspended app screenshot is way more that appearance. We all need a moment to remember to context of what we were doing. Showing us a screenshot of the suspended state enables us to use the loading time productively so that we are immediately ready to interact once it's up.
- Dylan16807 8y agoThe task at hand is waiting. People love to be distracted from waiting without any evidence of progress. Isn't that why they put speakers into so many dial-up modems?
- FullyFunctional 8y agoI'd assume they the speaker was for diagnosis, eg. if you could hear an "Ahoy?" then you should probably start over.
- ansible 8y agoSpeaking as a user of dial up modems in the past, no. The speaker was vital to inform the user as to what was happening. If the phone line was in user, if there was a dialing problem, if you called the wrong number, etc. And it also gave you an indication of the connection speed and line quality.
- pythonaut_16 8y agoAll (graphical) user interfaces are a lie. The only real question is whether they're lying to benefit the user or not.
- fipple 8y agoWhy not a single logo on the boot screen, and if you hold down Shift you can get the full dump of everything that's going on.
- audidude 8y agoTo change the initial splash (from power-on), you'd need to get that pixmap embedded into your EFI. However, with the recent changes, any of these systems after initial EFI can alter the framebuffer and have that persisted up until wayland/xorg/etc. Pressing a key to get the "full dump" is in fact how plymouth works, which many Linux distributions use from the kernel up until gdm/display-manager.
- ryandrake 8y agoI’m a big nerd but I don’t care when the bios hands off to the bootloader or when that hands off to the kernel ow when that hands off to the window manager. I just want those steps to go as quickly as possible without a bunch of manufacturers spamming their logos at me. The only time I want to see these handoffs and a ugly text dump is when things are broken and I’m debugging it, which should never happen anyway. Why do we expect such mediocrity out of our software?
- jlawer 8y ago> Why do we expect such mediocrity out of our software? Experience
- NeedMoreTea 8y agoI imagine most would simply like to turn it on and get a prompt right away, like used to happen with a C64. A ridiculous amount of modern products have gained a boot sequence that should not need one, and didn't used to. Hiding it doesn't fix the real issue.
- bmn__ 8y agoThings are possible if one puts one's mind to it. five seconds, year 2008: https://lwn.net/Articles/299483/ https://lwn.net/Articles/299483/ two seconds, year 2017: https://www.youtube.com/watch?v=IUUtZjd6UA4&t=17 https://www.youtube.com/watch?v=IUUtZjd6UA4&t=17
- userbinator 8y agowhich should never happen anyway. "The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or repair." -Douglas Adams
- grumdan 8y agoI think it's a matter of taste. I find seeing boot messages about services starting up etc. more aesthetically pleasing than some logo. It reminds me of people who buy mechanical watches where the gears are visible. Seeing the underlying bits of a complex system exposed can certainly be appealing to some people.
- audidude 8y ago> Bios isn't in control anymore, why is the motherboard logo still on the screen? There is nothing stopping any of these components from changing the display framebuffer. The "news" here, so to speak, is that finally we'll have things working where you can avoid any buffer changes and simply start drawing on the old background. If you want, you could have grub2/etc change the framebuffer and now that could persist up to the gdm hand-off.
- stefan_ 8y agoIt's not in there because it's generally a gigantic hack. For the 40 or 50 years that people have been developing device driver's the basic principles have largely not changed: you start with a clean slate ans do a reset to put the HW into a known good state. Every block of silicon ever devised comes with means to reset it's internal state. What this is doing is telling the driver to ignore it's normal reset procedure because someone else, but specifically not you, has already done the super complex modesetting and you are to trust it implicitly. So next year, when the sales people come up with the idea that they want to show an animation across all your DisplayPort chained monitors at boot, the guys at Apple buckle down for a month, hack that into the bootloader and then hack their kernel to recognize it, ships the same year. On Linux, for the first ten years, nobody cares because there are much larger fires to put out, then ten years are spent on a vendor and display technology agnostic VR ready boot up animation description format, ten more years pass for a critical mass of boot firmware and kernel graphics drivers to support it, then it ships with Ubuntu but every third boot has flicker or a weird rotation issue.
- deleted 8y ago[deleted]
- def_ConGame 8y agoIt originates from the PEBKAC RTFM subculture of everything being your fault, because you haven't memorized how to touch-type 150 command line tools, and every possible switch to pass each of them, plus the arbitrary positioning of arguments in between. Everyone's just supposed to know that X.org windowing environments are totally insecure, and that's why system administrators refuse to be caught dead using one, production or not, with or without their custom, backlit Cherry MX keycaps. Do your homework, and read the entire corpus of source code, no matter whether it contains more characters than the library of congress. If you didn't build the binaries yourself, then you aren't entitled to lay blame. You caused that screen flicker by being part of the problem, and not part of the solution. If you were a guru, you'd already know what's wrong. Learn to fix your own problems. Have you ever heard of Aesop's fables? Here's a little parable to help relate why free software is always 100% perfect as is: https://en.wikipedia.org/wiki/The_Little_Red_Hen https://en.wikipedia.org/wiki/The_Little_Red_Hen
- deleted 8y ago[deleted]
- linksnapzz 8y agoShow us where the evil sysadmin touched you....
- def_ConGame 8y agoIt was dark, but I remember finger and touch commands being invoked inside my chroot jail... when I tried to use who, it just said nobody.
- dang 8y agoWould you please stop posting uncivil comments and rants to HN? It's against the site guidelines, and you've done a lot of it. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- def_ConGame 8y ago
- agumonkey 8y agoI wouldn't mind a non sophisticated boot display. A TUI can be superb if it conveys something interesting in a cute way (a bit like language design). But mumbled sheared terminal output is none of that.
- burfog 8y agoOSX couldn't do that on a random PC. Every distinct piece of Apple's boot process (firmware, boot loader, kernel, desktop) can have the correct video driver, be aware of the desired final video resolution, and trust that any previous piece has left the video card in the proper state. It all ships together. The PC BIOS doesn't know you want 2560x1600 for your desktop. It just picks a mode suitable for the BIOS. If anything, the BIOS is required to leave the screen in VGA text mode. The boot loader faces the same issue. At best, a Linux distribution might decide to use a VESA mode, but that can't cover the desired 2560x1600. (VESA doesn't go that high)
- wmf 8y agoThe PC BIOS doesn't know you want 2560x1600 for your desktop... That's why we switched to UEFI around a decade ago; I'm pretty sure it doesn't have all those problems. So a modern PC can boot directly into the correct resolution.
- semi-extrinsic 8y agoUEFI stands for “Unified Extensible Firmware Interface”, where “Firmware” is an ancient African word meaning “Why do something right when you can do it so wrong that children will weep and brave adults will cower before you”, and “UEI” is Celtic for “We missed DOS so we burned it into your ROMs”. –Matthew Garrett (he wrote a lot of the Linux kernel UEFI implementation)
- sometimesijust 8y agohttps://lore.kernel.org/patchwork/patch/250840/ https://lore.kernel.org/patchwork/patch/250840/
- jaclaz 8y agoThank you for the Matthew Garret quote, very nice "alternate" definition of UEFI.
- chuckdries 8y agoMy custom build shows the motherboard logo at the correct resolution immediately on POST and never has to mode switch even through grub. It flashes off and on to load the nvidia proprietary drivers, but never has to do so when I boot to windows.
- bluedino 8y agoWhat about the random pixel pattern that pops up when my MacBook Pro first comes out of sleep?
- NullPrefix 8y agoBut is it the same resolution as your desktop?
- atombender 8y agoBug in certain older models, or older OS version. I had it on my 2015 model (discrete GPU).
- rsynnott 8y agoI’ve used various MacBook Pro models from 2007 to 2018; they’ve all done this at least occasionally. The iBook I had previously didn’t, though. Apple’s PPC stuff always felt just that little bit saner.
- fyfy18 8y agoWhat I’d really love is Linux to be able to unlock a fully encrypted root partition similar to macOS. On macOS the user is prompted to login at a very early stage of the boot process, and after this the disk is decrypted and the OS is booted. The user is then logged in automatically, so they only need to enter their password once to decrypt the disk and authenticate their account.
- coder543 8y agoIt's definitely possible to configure this... it's just not a default on any distro I'm aware of. Linux Full Disk Encryption definitely stops very early and asks for the FDE password before being able to continue booting. After that, you would just have to have your user set to "automatically log in" for it to just go all the way in. In fact, I think you could choose to set it up this way from the Ubuntu installer directly. By default, it just encourages you to sign in manually in addition to setting up FDE.
- riquito 8y agoThat's my setup since some years. It's one of the options during Fedora's installation, I think that Ubuntu allows that too (and likely others).
- ekianjo 8y agoLinux does that too. It asks for the encryption password very early in the boot sequence and that is it.
- seodisparate 8y agoActually I have my desktop configured with an encrypted root. Turns out GRUB can actually decrypt the partition holding /boot before loading the grub.cfg. Though I have this set up on ArchLinux and had to refer to the Arch wiki a lot to get this set up properly. Definitely not that user friendly, but I can say it is a possible setup after having used it for years on my desktop now. EDIT: To clarify, my setup requires inputting passwords twice: once for decrypting the root partition, and once to login after everything has booted. During the boot process the system needs to remount everything, so I had the encrypted partition(s) also be decrypted with a key file (typically `dd if=/dev/urandom of=keyfile bs=1M count=4`; LUKS encryption can have multiple keyfiles/passwords to decrypt) and had the key file(s) put in the initramfs so after GRUB has decrypted root and loaded /boot/grub.cfg, the booted system could decrypt and mount everything needed with the key file(s).
- walrus01 8y agoI specifically search out the kernel option to pass in grub2 to see the dmesg scroll past in text during boot, so I think I am the opposite of people who care about flickers and visual disturbances during boot. More than once having the kernel boot visible has helped diagnose hardware failure or other OSI layer 1 issues with the system.
- mediocrejoker 8y agoI agree with another comment that said they want the pretty picture when it works and the text dump only when something has gone wrong. The best of both worlds.
- sjwright 8y agoFlicker-free boot can help you too—it's not a synonym for concealing the boot process. Wouldn't it be nice to watch the text logs progress tidily as the graphics drivers load? "Flickers and visual disturbances" can disrupt your ability to read potentially important boot text. The level of disruption can vary greatly depending on your particular hardware; some external monitors take multiple seconds to show an image after the display mode is changed.
- twic 8y agoMy favourite thing my Ubuntu machine does is that when you wake it from sleep, it shows you the desktop as it was when you put it to sleep for a fraction of a second, then flickers a few times while it puts up a lock screen, then shows two login dialogs stacked on top of each other, one larger than the other.
- rrdharan 8y agoYep, also obviously a security (information disclosure / privacy) flaw that is quite difficult to solve apparently.
- rhizome 8y agoA decent place to start reading: https://askubuntu.com/questions/453296/privacy-issue-when-waking-up-suspended-machine https://askubuntu.com/questions/453296/privacy-issue-when-wa...
- wlll 8y agoMy mac does that. I've not tested it on Mojave, but it did it every time without fail on High Sierra.
- deleted 8y ago[deleted]
- wlll 8y agoTested this, my mac still does this on Mojave.
- kreetx 8y agoSame here on ubuntu with xfce. They should at least overlay something before going to sleep as a quick fix.
- pbhjpbhj 8y agoLike, the lockscreen, perhaps.
- pbarnes_1 8y agoOn my external 5k display connected to a 2013 Mac Pro, the File Vault protected login screen is displayed in the middle of the screen using maybe 30% of the screen real estate. Once logged in you get the full 5k. So it's still not 100% over in Mac land. :D
- Insanity 8y agoIt never actually bothered me (as a tech person) but I can see how a non-tech person might think something is wrong. Then again, dependint on the distro, they don't really cater to the average user.
- taeric 8y agoI think this is also one of those things that is easy to overstate. OSX has often annoyed me by how obviously unready it was for me, even though the login screen was there. For the most part, though, I just don't notice it. One way or the other.
- Nition 8y agoMy Windows 10 machine, if I start it up before I turn the screen on (DisplayPort connection), shows the login screen with the background picture in what looks like a stretched super low JPEG-artifacted resolution. If I turn the screen on first, or if I use the login screen again later, it's fine. The background image is a local, high-resolution image file on my computer. It didn't happen in early versions on Windows 10. It started with one of the major updates. My guess is if you don't have a screen on when the login page first shows, it down-samples your background image to some low resolution, and then just stretches it out to fit to your actual screen res when you do turn your screen on.
- n4s33r 8y agoIt definitely is a big deal and it is also _lot_ of work, it probably sounds like it's something easy to do, just by the sound of it, but nope ...
- tambourine_man 8y ago>I think this is basically what OSX has had forever. And classic Mac. First time I saw Windows 3.1.1 boot my jaw dropped. What an ugly hack. That’s what’s conquering the world? The monitor wouldn’t even turn itself on. Never mind having to manually eject a floppy after you just told the computer to do it for you.
- deleted 8y ago[deleted]
- eudora 8y agoIt is a big deal, for experience, and you're right about it being the kind of thing certain engineers don't see as a big deal. But- I'd rather they fix a bunch of other things first. I'd put "things that don't work" in the first todo bucket, then move on to "things that are painful to endure", followed by "things that make it feel janky" I wanted to use Fedora recently and it totally failed to handle my perfectly common laptop graphics card. Ubuntu did it fine.
- kelnos 8y agoTo start: yes, I'm an engineer. I don't think it's a big deal at all. Or rather, I think it's important, but it's the last bit of polish that you put on things after the rest of your house is in order. It's a nice-to-have. Meanwhile, I installed Debian buster on a 2016 MacBook Pro -- a two year old laptop -- and sound and suspend-to-RAM don't work (hell, the keyboard and trackpad didn't even work at all without installing an out-of-tree driver post-OS-install; I had to do the install using a USB keyboard). Yes, I get that this probably isn't super common hardware, and it's also a bit exotic, but... c'mon. I just don't care if my screen jumps between text and graphics mode or changes resolution a couple times before I get to the login screen. It just isn't on my radar at all. The Xorg touchpad drivers are a mess: libevent is one-size-fits-none, synaptics is buggy and unmaintained, and the fork of mtrack that's still maintained might be able to come close to something decent, but I'm not sure because I've already spent a couple hours tweaking its settings, and I still can't get it to not randomly send scroll and button events while I'm typing. So no, I don't care at all about something useless like "flicker free boot". I want my laptop to be actually polished in ways that are functional first. And I get it: it's not up to me to tell people what to work on during their free time. Everyone has their own itch to scratch, and that's a very personal thing. But to then (as you have) arbitrarily decide that visual polish during a functionally-irrelevant period of the machine's operation is more important than day-to-day functional polish while I'm actually interacting with the machine? Nope... not buying it.
- cameronhowe 8y agoI believe some of your trouble would go away if you bought a laptop from a GNU Linux vendor. It seems unfair to compare your mac experience on a mac to your GNU Linux experience on a mac.
- alpaca128 8y agoThis is just a matter of target audience. I think if you want ordinary people to use your OS a flickering boot will get noticed and not make a great first impression. The users who don't care at all about it are probably already using Linux. And I agree with you that the basics need to run well first, but in my experience many common distros got that covered. Debian is one of the exceptions, it's pretty much the only Linux distro where not everything runs fine out of the box on my laptop.
- thatsaguy 8y agoWell, tear-free video on intel gfx would be a _big_ deal (you remember, stuff we had in the 80-90ies?). Flicker-free boot is nice to have, but it's not a _big_ deal. I can live just fine if the boot flickers twice. But somehow doing animation with tearing for the rest of the work-day is quite a bit more annoying.
- BoorishBears 8y agoIt's not a big deal for you, it's a big deal for UX. UX isn't about what you as a user feel, it's about what users feel, and OP is probably talking about UX for all users, not just those comfortable with Linux and it's tendency to have a janky UI.