recentpopularlog in

kme : kernel   87

« earlier  
107583 – Linux: REGRESSION: drm: cmdline EDID override mechanisms broken since 4.15
There was a patch committed in the 5.2.x series at 48eaeb7664c76139438724d520a1ea4a84a3ed92. Did it land in 5.3, 5.4, ...?
linux  kernel  drm  kms  edid  sony  vaio  bootoption  graphics  annoyance  needshelp 
7 weeks ago by kme
kernel - How to check that KPTI is enabled on my Ubuntu? - Ask Ubuntu
<code class="language-bash">
grep -q "cpu_insecure\|cpu_meltdown\|kaiser" /proc/cpuinfo && \
echo "patched :)" || echo "unpatched :("
</code>

Not super-reliable, since there are several separate vulnerabilities (and several mitigations); try https://github.com/speed47/spectre-meltdown-checker.
linux  kernel  kpti  meltdown  spectre  security  vulnerability  howto 
january 2018 by kme
​Major Linux redesign in the works to deal with Intel security flaw | ZDNet
To say Linux developers were unhappy about this would be a massive understatement. When the set of fixes' name was changed from KAISER to Kernel Page Table Isolation (KPTI), some of the suggested names were User Address Space Separation, prefix uass_ and Forcefully Unmap Complete Kernel With Interrupt Trampolines, prefix fuckwit_.
linux  kernel  devel  kpti  aslr  meltdown  spectre 
january 2018 by kme
About the security content of macOS High Sierra 10.13.2, Security Update 2017-002 Sierra, and Security Update 2017-005 El Capitan - Apple Support | https://support.apple.com/
Kernel

Available for: macOS High Sierra 10.13.1, macOS Sierra 10.12.6, OS X El Capitan 10.11.6

Impact: An application may be able to read kernel memory

Description: Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache.

CVE-2017-5754: Jann Horn of Google Project Zero, Werner Haas and Thomas Prescher of Cyberus T...
macos  kernel  security  update  meltdown 
january 2018 by kme
Kernel Mode Setting (KMS) is great, but may not work as expected
The real solution is, thus, to optionally disable probing of the monitor and to directly feed appropriate monitor data into the kernel. For this purpose, the kernel configuration item CONFIG_DRM_LOAD_EDID_FIRMWARE was introduced. If enabled, the drm_kms_helper module will accept the parameter edid_firmware=, search for the given file in the /lib/firmware directory and use its data, if valid, to initialize the monitor timings of the graphics adapter as if it had been received from the monitor. Four standard timings are hard-coded in the driver and available immediately:

Resolution

Name

1024x768/60 Hz

edid/1024x768.bin

1280x1024/60 Hz

edid/1280x1024.bin

1680x1050/60 Hz

edid/1680x1050.bin

1920x1080/60 Hz

edid/1920x1080.bin

To force, for example, a screen resolution of 1280x1024/60 Hz, simply remove nomodeset from, add drm_kms_helper.edid_firmware=edid/1280x1024.bin to the kernel command, and enjoy a much faster screen and all the eye candy you missed so long.
linux  edid  kernel  graphics  driver  troubleshooting  maybesolution  vaio  vgcjs110j 
may 2017 by kme
EDID and HowTo make one
The key part below is that there is no corresponding file in /lib/firmware for these built-in modes.
KMS requires an EDID, and while you can override the EDID in org.conf, the plan is to get X11 away from the hardware and that will stop working. It is possible to override the EDID at the kernel level though. To do so, be sure CONFIG_DRM_LOAD_EDID_FIRMWARE is selected and passing drm_kms_helper.edid_firmware= one of the following 5 special parameters on the kernel command line, corresponding to the desired resolution:

edid/1024x768.bin
edid/1280x1024.bin
edid/1600x1200.bin
edid/1680x1050.bin
edid/1920x1080.bin

Note that these values are hardcoded in the driver, there is no corresponding /lib/firmware file (although if it exists it will override the built-in ones)

It is possible to create custom EDID if needed: see Documentation/EDID/HOWTO.txt in the kernel sources for the details.
video  linux  kernel  edid  troubleshooting  vaio  vgcjs110j  solution 
may 2017 by kme
a/esr-sharing
When you were in college, did you ever meet bright kids who graduated
top of their class in high-school and then floundered freshman year
in college because they had never learned how to study? It's a common
trap. A friend of mine calls it "the curse of the gifted" -- a tendency
to lean on your native ability too much, because you've always been
rewarded for doing that and self-discipline would take actual work.
linux  kernel  history  development  curseofthegifted 
april 2017 by kme
devpts: Attempting to get it right [LWN.net]
This gave me some clue as to what the permissions were *supposed* to be for /dev/pts and related files. The (short-term) solution to the problem I was having was to 'chmod 666 /dev/pts/ptmx', but possibly a permanent solution is discussed here: http://lxr.free-electrons.com/source/Documentation/filesystems/devpts.txt
linux  kernel  devpts  ptmx  permissions 
december 2016 by kme
linux - Failed to connect to the VirtualBox kernel service - Super User

Make sure you have dkms installed.

apt-cache search dkms | grep '^dkms'
dkms - Dynamic Kernel Module Support Framework

If this is the case try the following:

$ sudo /etc/init.d/vboxdrv setup
again  virtualbox  linux  kernel  errormessage  ubuntu  maybesolution  annoyance 
february 2016 by kme
virtualbox - Error: kernel headers not found. (But they are in place) - Ask Ubuntu

The message is misleading.

In my case it was actually missing dkms so before you install the addition run

sudo apt-get install build-essential linux-headers-`uname -r` dkms


Installing 'dkms' fixed the problem. The specific error message was
The headers for the current running kernel were not found. If the following
module compilation fails then this could be the reason.
kernel  build  modules  errormessage  solution 
september 2015 by kme
Failed at step EXEC spawning /bin/plymouth: No such file or directory / Pacman & Package Upgrade Issues / Arch Linux Forums
You are right - the halt is caused by the error message on the screenshot. I had the feeling that plymouth was not to blame, but /srv/nfs/trunk got mounted eventually and that mislead me.

I had a bad entry in /etc/fstab. Why in the fuck should a bad entry in fstab cause the system to halt?
linux  kernel  vbox  solution  wtf 
september 2015 by kme
Creating a Custom Linux Kernel in Debian GNU/Linux
make-kpkg --append-to-version -4custom01-686-pae \
--revision 3.16.7-ckt9-3~deb8u1 --initrd --rootcmd fakeroot \
kernel_image kernel_headers
kernel  compile  howto  debian 
august 2015 by kme
« earlier      
per page:    204080120160

Copy this bookmark:





to read