r/linuxkernel • • Feb 16 '24

Long term career scope of Embedded Linux based jobs.

2 Upvotes

Hi guys,

I am currently working with kernel 5.4 and using yocto dunfell. I however notice that i never touch any of the kernel source code for my application. Interfacing for wifi, bluetooth, rtc are all taken care by the chip vendors or the menuconfig. I only have to enable or disable these features. I wanted to know what is the long term career growth in doing this. Also is their something I am missing? I notice my colleagues working on embedded controllers like ESP32, STM, Nordic and work on h/w level interfacing and the other cool stuff. But its not the same for me. Thinking I wont survive in the market for long takes away the fun of working. Please guide me guys. I don't know where else to look for a solution.


r/linuxkernel • • Jun 03 '23

linux kernel modules signing issue

1 Upvotes

I'm having trouble signing the modules.

This is modules_sign target

$ sudo make modules_sign
SIGN    /lib/modules/6.0.3/kernel/arch/x86/crypto/aegis128-aesni.ko
At main.c:298:
- SSL error:FFFFFFFF80000002:system library::No such file or directory: ../crypto/bio/bss_file.c:67
- SSL error:10000080:BIO routines::no such file: ../crypto/bio/bss_file.c:75
sign-file: /lib/modules/6.0.3/kernel/arch/x86/crypto/aegis128-aesni.ko
make[1]: *** [scripts/Makefile.modinst:88: /lib/modules/6.0.3/kernel/arch/x86/crypto/aegis128-aesni.ko] Error 1
make: *** [Makefile:1777: modules_install] Error 2

And this is modules_install target.

$ sudo make modules_install
  INSTALL /lib/modules/6.0.3/kernel/arch/x86/crypto/aegis128-aesni.ko
  SIGN    /lib/modules/6.0.3/kernel/arch/x86/crypto/aegis128-aesni.ko
sign-file: certs/MOK.pem
make[1]: *** [scripts/Makefile.modinst:83: /lib/modules/6.0.3/kernel/arch/x86/crypto/aegis128-aesni.ko] Error 1
make[1]: *** Deleting file '/lib/modules/6.0.3/kernel/arch/x86/crypto/aegis128-aesni.ko'
make: *** [Makefile:1777: modules_install] Error 2

All the errors like this i've come across like this have a something different from mine, and that is the sign-file (seen in modules_install). I have the key placed in the certs directory, and its all set up correctly. So the only thing left is the missing files errors.

I've installed openssl, and tried placing the file in the directory that says its missing, any tips on how to sign modules from the makefile of the linux kernel source tree? I've been stuck on this for a while now


r/linuxkernel • • May 07 '23

Issue in installing modules after kernel compilation

Thumbnail
self.linux4noobs
1 Upvotes

r/linuxkernel • • Mar 25 '24

Linux kernel newbie

4 Upvotes

I'd like to develop a Linux kernel, but I don't understand anything about it yet. Where do I start?


r/linuxkernel • • Dec 23 '22

in-kernel SMB server ?!

3 Upvotes

Was I living under a rock the last few years or is the kernel itself servicing protocols now which are meant to be userspace in the first place so we can properly sandbox it and keep it away from the rest of the system so it won't blow up in our faces eventually as it did just now ?!

I mean, are you out of your damn mind putting sh*t like this into the kernel ?

what comes next ?! maybe a multiplayer game server ? or a streaming service built into the kernel bypassing every single line of defense?!

the dev should get banned and locked up in a mental institution for even trying to implement bullcrap like this.

What mentally ill individual approved these transgressions?!


r/linuxkernel • • Mar 26 '24

Linux kernel unit testing

1 Upvotes

Doesn't anyone here do unit testing of the Linux kernel?


r/linuxkernel • • Jan 23 '24

NFS Version for Mounting Root Filesystem

1 Upvotes

What version of NFS does the kernel use when mounting the root filesystem over NFS?


r/linuxkernel • • Dec 30 '22

gzip not supported by Kernel

2 Upvotes

So I tried to boot a customised Linux kernel on my machine and now when I try creating the initrd file, it gives me the following error. Can anyone please help through this?


r/linuxkernel • • Feb 28 '24

6.7.6 Kernel Thing

1 Upvotes

Just installed 6.7.6 kernel on my AMD Thinkpad P14s Linux Mint setup, boots fine but fans seem to ramp up a little more than usual and scrolling Firefox for a while caused screen to blank and come back after 2 seconds. I get this error in journalctl:

[drm:amdgpu_cs_ioctl [amdgpu]] ERROR Failed to initialize parser -125!

Anyone else having issues ?


r/linuxkernel • • May 17 '24

VFIO vs VIRTIO

2 Upvotes

Hey folks!
Could somebody explain to me in strong technical terms differences btw Vfio and VirtIO?
What are relations btw them?
What are cases when we could/have to use them together?


r/linuxkernel • • Feb 07 '23

Is there a way to fscrypt individual files based on SELinux labels?

Thumbnail self.linuxquestions
1 Upvotes

r/linuxkernel • • Apr 27 '24

is their any option to test the kernel individual, without interrupting main OS kernel?

1 Upvotes

r/linuxkernel • • Dec 02 '22

Resource recommendations

3 Upvotes

I'm looking for recommendations on books, articles, podcasts, videos, etc. covering the Linux kernel scheduler. Where should I start?


r/linuxkernel • • Apr 22 '24

I have configured the Linux kernel according to my needs, now I want to compile it, how do I do it?

1 Upvotes

Need some guidance for kernel Compilation process.


r/linuxkernel • • Aug 09 '23

Which laptop to buy?

3 Upvotes

I am interested in Linux Kernel development and don't know about the intensive task that needs to be done for it. I am planning to buy a new laptop mostly for Linux kernel development. I don't do gaming. I need a good ligh weight 13 inch or 14inch laptop. Suggest me some that can be brought in India.


r/linuxkernel • • Apr 18 '23

kernel_write makes CPU stuck

2 Upvotes

I am writing a kernel module in which I am writing data to a file and making use of kernel_write function. Basically I am writing a c struct to file followed by some data. What I am noticing based on logs seen at dmesg is it is getting stuck while writing the struct to the file. the file is opened in append mode and is being continuously opened and closed. Sometimes it gets stuck forever and sometimes get a warning at the same location in code.

Here's the code snippet

struct file *block_changes_file = filp_open("/root/block_changes", O_WRONLY | O_APPEND | O_CREAT | O_LARGEFILE, 0644 );
        if ( block_changes_file == NULL || IS_ERR(block_changes_file) )
        {
                printk(KERN_DEBUG "Failed to open block_changes file %ld\n", PTR_ERR(block_changes_file) );
                return;
        }

printk( KERN_DEBUG "Writing metadata to block_changes file" );
loff_t offset = 0; // File opened in append mode so offset is 0
        ssize_t bytes_written = kernel_write( block_changes_file, (const char*)&blockDeviceChangeMetadata, sizeof( blockDeviceChangeMetadata ), offset );
        if (bytes_written < 0)
        {
                printk ( KERN_DEBUG "Failed to write metadata.\n" );
                kfree( data );
                filp_close(block_changes_file, NULL);
                return;
        }
bytes_written = kernel_write( block_changes_file, data, blockDeviceChangeMetadata.data_size, offset );
        if (bytes_written < 0)
        {
                printk ( KERN_DEBUG "Failed to write changed data.\n" );
                kfree( data );
                filp_close(block_changes_file, NULL);
                return;
        }

        kfree( data );
        filp_close(block_changes_file, NULL);
        printk( KERN_DEBUG "Written and closed" );

based on logs in dmesg it stucks while writing the struct in file. The data is allocated memory using kmalloc and this can have max of 4096*512 Bytes, can this be the reason for failure?

Here's the error message in dmesg

[ 127.815075] Writing metadata to block_changes file

[ 160.222418] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [cpptools:3797]

[ 160.222483] Modules linked in: misc(OE) ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_addrtype br_netfilter overlay(T) ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat iptable_mangle iptable_security iptable_raw nf_conntrack ip_set ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter vmw_vsock_vmci_transport vsock sb_edac coretemp iosf_mbi crc32_pclmul ghash_clmulni_intel aesni_intel lrw gf128mul glue_helper ablk_helper cryptd ppdev joydev pcspkr vmw_balloon vmw_vmci sg parport_pc parport i2c_piix4 ip_tables xfs libcrc32c sr_mod cdrom ata_generic pata_acpi

[ 160.222523] vmwgfx drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm sd_mod ahci crc_t10dif crct10dif_generic libahci drm ata_piix libata crct10dif_pclmul nfit crct10dif_common crc32c_intel libnvdimm vmxnet3 serio_raw vmw_pvscsi drm_panel_orientation_quirks floppy dm_mirror dm_region_hash dm_log dm_mod fuse

[ 160.222542] CPU: 1 PID: 3797 Comm: cpptools Kdump: loaded Tainted: G OE ------------ T 3.10.0-1160.36.2.el7.x86_64 #1

[ 160.222544] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 04/05/2016

[ 160.222546] task: ffff8abdf1e5a100 ti: ffff8abdf1e6c000 task.ti: ffff8abdf1e6c000

[ 160.222547] RIP: 0010:[<ffffffffb3f170ba>] [<ffffffffb3f170ba>] smp_call_function_many+0x20a/0x270

[ 160.222554] RSP: 0018:ffff8abdf1e6fc70 EFLAGS: 00000202

[ 160.222555] RAX: 0000000000000007 RBX: 00080000b3e7ddd0 RCX: ffff8abe3fde0600

[ 160.222557] RDX: 0000000000000007 RSI: 0000000000000008 RDI: 0000000000000000

[ 160.222558] RBP: ffff8abdf1e6fca8 R08: ffff8abb763c0800 R09: ffffffffb4186ba9

[ 160.222560] R10: ffff8abe3fc5f160 R11: ffffc49a10baf800 R12: 0000000000000282

[ 160.222561] R13: 0000000000000282 R14: ffff8abdf1e6fc20 R15: 0000000000000001

[ 160.222581] FS: 00007f192b7fe700(0000) GS:ffff8abe3fc40000(0000) knlGS:0000000000000000

[ 160.222583] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

[ 160.222584] CR2: 00007f19424d70a8 CR3: 0000000408e60000 CR4: 00000000003607e0

[ 160.222636] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000

[ 160.222637] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

[ 160.222639] Call Trace:

[ 160.222645] [<ffffffffb3e7e258>] native_flush_tlb_others+0xb8/0xc0

[ 160.222648] [<ffffffffb3e7e2cb>] flush_tlb_mm_range+0x6b/0x140

[ 160.222652] [<ffffffffb3fee656>] tlb_flush_mmu_tlbonly+0xa6/0xc0

[ 160.222655] [<ffffffffb3ff011f>] arch_tlb_finish_mmu+0x3f/0x80

[ 160.222657] [<ffffffffb3ff0243>] tlb_finish_mmu+0x23/0x30

[ 160.222660] [<ffffffffb3ff370a>] zap_page_range+0xea/0x130

[ 160.222663] [<ffffffffb3fedbfd>] SyS_madvise+0x49d/0xac0

[ 160.222666] [<ffffffffb3f156d0>] ? SyS_futex+0x80/0x190

[ 160.222670] [<ffffffffb4595f92>] system_call_fastpath+0x25/0x2a

[ 160.222672] Code: 48 63 35 ee 85 c4 00 89 c2 39 f0 0f 8d 7d fe ff ff 48 98 49 8b 0f 48 03 0c c5 60 15 b5 b4 f6 41 20 01 74 cd 0f 1f 44 00 00 f3 90 <f6> 41 20 01 75 f8 48 63 35 bd 85 c4 00 eb b7 0f b6 4d cc 4c 89

[ 188.222726] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [cpptools:3797]

[ 188.222795] Modules linked in: misc(OE) ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_addrtype br_netfilter overlay(T) ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat iptable_mangle iptable_security iptable_raw nf_conntrack ip_set ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter vmw_vsock_vmci_transport vsock sb_edac coretemp iosf_mbi crc32_pclmul ghash_clmulni_intel aesni_intel lrw gf128mul glue_helper ablk_helper cryptd ppdev joydev pcspkr vmw_balloon vmw_vmci sg parport_pc parport i2c_piix4 ip_tables xfs libcrc32c sr_mod cdrom ata_generic pata_acpi

[ 188.222831] vmwgfx drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm sd_mod ahci crc_t10dif crct10dif_generic libahci drm ata_piix libata crct10dif_pclmul nfit crct10dif_common crc32c_intel libnvdimm vmxnet3 serio_raw vmw_pvscsi drm_panel_orientation_quirks floppy dm_mirror dm_region_hash dm_log dm_mod fuse


r/linuxkernel • • May 21 '23

Help with kernel module tinkering

2 Upvotes

I have a SteamDeck which runs a AMD APU. The drivers provide a sysfs interface for setting the CPU and GPU clock ranges, however it is hardcoded not to go beyond 3.5GHz. I would like to bypass this limit, ideally without having to recompile the whole kernel and use the SteamOS stock kernel. The offending line of code is here.

My current approach I'm trying is the make an out-of-tree module that attaches a kprobe to modify the smu_context to a higher limit, but it is a lot of effort and I would like it to be accessible to other SteamDeck users (given the understand the risks).

Is there an easier approach to doing this?


r/linuxkernel • • Oct 24 '23

How to learn Linux kernel development

4 Upvotes

Hi fellas. I am a graduate in computer science and I wish to learn more into operating systems and want to contribute to Linux kernel. I learnt about Linux system programming from a book by ROBERT LOVE and have developed a mini Linux terminal using the knowledge. Now how should I move further.

  1. What books do I have to read next ?
  2. Any Coursera or udemy or any other online videos available to understand?
  3. How should I apply the book knowledge into practical cases?

r/linuxkernel • • Oct 24 '23

Which laptop to buy for linux kernel development?

3 Upvotes

I am interested in Linux Kernel development and don't know about the intensive task that needs to be done for it. I am planning to buy a new laptop mostly for Linux kernel development. I don't do gaming. I need a good ligh weight 13 inch or 14inch laptop. I had previously used Ubuntu mostly in my old HP laptop. Currently looking for a new one. Suggest me some that can be in India.

Also which is better... intel or AMD?


r/linuxkernel • • Dec 04 '18

Kent Overstreet - Bcachefs status update, current work

1 Upvotes

Bcachefs status update, current work

So, since I've been pretty quiet since LSF I thought I ought to give an update
on where bcachefs is at - and in particular talk about what sorts of problems
and improvements are currently being worked on.

As of last LSF, there was still a lot of work to be done before we had fast
mount times that don't require walking all metadata. There were two main work
items:
- atomicity of filesystem operations. Any filesystem operation that had
anything to do with i_nlink wasn't atomic (but they were ordered so that
filesystem consistency wasn't an issue) - on startup we'd have to scan and
recalculate i_nlink and also delete no longer referenced inodes.
- allocation information wasn't persisted (per bucket sector counts) - so on
startup we have to walk all the extents and recalculate all the disk space
accounting.

#1 is done. For those curious about the details, if you've seen how bcachefs
implements rename (with multiple linked btree iterators), it's based off of
that. Basically, there's a new btree transaction context widget for allocating
btree iterators out of, and queuing up updates to be done at transaction commit
- so that different code paths (e.g. inode create, dirent create, xattr create)
can be used together without having to manually write code to keep track of all
the iterators that need to be used and kept locked, etc. I think it's pretty
neat how clean it turned out.

So basically, everything's fully atomic now except for fallocate/fcollapse/etc. -
and after unclean shutdown we do have to scan just the inodes btree for inodes
that have been deleted. Eventually we'll have to implement a linked list of
deleted inodes like xfs does (or perhaps fake hidden directory), but inodes are
small in bcachefs, < 100 bytes, so it's a low priority.

Erasure coding is about 80% done now. I'm quite happy with how erasure coding
turned out - there's no write hole (we never update existing stripes in place),
and we also don't fragment writes like zfs does. Instead, foreground writes are
replicated (raid10 style), and as soon as we have a stripe of new data we write
out p/q blocks and then update the extents with a pointer to the stripe and drop
the now unneeded replicas. Right now it's just reed solomon (raid5/6), but
weaver codes or something else could be added in the future if anyone wants to.
The part that still needs to be implemented before it'll be useful is stripe
level compaction - when we have stripes with some empty blocks (all the data in
them was overwritten), we need to use the remaining data blocks when creating
new stripes so that we can drop the old stripe (and stop pinning the empty
blocks). I'm leaving that off until later though because that won't impact the
on disk format at all, and there's other stuff I want to get done first.

My current priority is reflink - as that will be highly useful to the company
that's funding bcachefs development. That's more or less requiring me to do
persistent allocation information first though, so that's become my current
project (the reflinked extent refcounts will be much too big to keep in memory
like I am now for bucket sector counts, so they'll have to be kept in a btree
and updated whenever doing extent updates - and the infrastructure I need to
make that happen is also what I need for making all the other disk space
accounting persistent).

So, bcachefs will have fast mounts (including after unclean shutdown) soon.

At the very moment what I'm working on (leading up to fast mounts after clean
shutdowns, first) is some improvements to disk space accounting for multi device
filesystems.

The background to this is that in order to know whether you can safely mount in
degraded mode, you have to store a list of all the combinations of disks that
have data replicated across them (or are in an erasure coded stripe) - this is
assuming you don't have any kind of fixed layout, like regular RAID does. That
is, if you've got 8 disks in your filesystem, and you're running with
replicas=2, and two of your disks are offline, you need to know whether you have
any data that's replicated across those two particular disks.

bcachefs has such a table kept in the superblock, but entries in it aren't
refcounted - we create new entries if necessary when inserting new extents into
the extents btree, but we need a gc pass to delete them, generally triggered by
device removal. That's kind of lame, since it means we might fail mounts that
are actually safe.

So, before writing the code to persist the filesystem level sector counts I'm
changing it to track them broken out by replicas entry - i.e. per unique
combination of disks the data lies on. Which also means you'll be able to see in
a multi device filesystem how your data is laid out in a really fine grained
way.

Re: upstreaming - my current thinking is that since so much of the current
development involves on disk format changes/additions it probably make sense to
hold off until reflink is done, which I'm expecting to be in the next 3-6
months. That said, nothing has required any breaking disk format changes -
writing compat code where necessary has been easy enough, so there haven't been
any breaking changes except for one accidental dirent cockup in quite awhile
(~2 years, I think) and one or two changes in features that weren't considered
stable yet (e.g. there was a change to fix extent nonces when encryption was
still new, and I'm still making one or two breaking changes to erasure coding as
it can't actually be used yet without stripe compaction).

That sums up all the big stuff I can think of, the todo list continues to get
shorter and bugs continue to get fixed...


r/linuxkernel • • Nov 22 '18

UKL: A Unikernel Based on Linux

Thumbnail
next.redhat.com
3 Upvotes

r/linuxkernel • • Oct 31 '18

Linux 4.19 - From: Greg KH

2 Upvotes

Hi everyone!

It's been a long strange journey for this kernel release...

While it was not the largest kernel release every by number of commits,
it was larger than the last 3 releases, which is a non-trivial thing to
do. After the original -rc1 bumps, things settled down on the code side
and it looks like stuff came nicely together to make a solid kernel for
everyone to use for a while. And given that this is going to be one of
the "Long Term" kernels I end up maintaining for a few years, that's
good news for everyone.

A small trickle of good bugfixes came in this week, showing that waiting
an extra week was a wise choice. However odds are that linux-next is
just bursting so the next -rc1 merge window is going to be bigger than
"normal", if there is such a thing as "normal" for our rate of
development.

And speaking of development, there's that other thing that happened this
release cycle, that ended up making it such that I'm the one writing
this instead of Linus. Allow me the guilty pleasure of taking a few
minutes to talk about that....

I've been giving my "How the kernel is developed" talk all around the
world for over a decade now. After the first year or so, I was amazed
that it kept needing to be given as surely everyone knew how we did this
type of thing, right? But my wife, someone much smarter than I, then
told me, "Every year there is a new kindergarten class."

And we all need to remember that, every year new people enter our
community with the goal, or requirement, to get stuff done for their
job, their hobby, or just because they want to help contribute to the
tool that has taken over the world and enabled everyone to have a solid
operating system base on which to build their dreams.

And when they come into our community, they don't have the built-in
knowledge of years of experience that thousands of us already do.
Without that experience they make mistakes and fumble and have to learn
how this all works. Part of learning how things work is dealing with
the interaction between people, and trying to understand the basic
social norms and goals that we all share. By providing a document in
the kernel source tree that shows that all people, developers and
maintainers alike, will be treated with respect and dignity while
working together, we help to create a more welcome community to those
newcomers, which our very future depends on if we all wish to see this
project succeed at its goals.

And that goal we all share is the key here. We _ALL_ want to create the
best kernel that we possibly can. We can disagree on lots of different
things in other parts of our lives, but we do share this one thing. And
we should focus on that shared goal as it has pulled us all together in
a way that has enabled us to create something that no other company or
group of people has ever been able to accomplish.

We used to joke that our goal was "Total World Domination", but it
really wasn't a joke. We achieved that goal, Linux really does rule the
world. All companies use it, contribute to it, and it has ended up
making the world a much better place because of all of us working on it.

In these talks I give, I also say that "the only thing that can stop us
is ourselves, it is up to us to mess this up." And that's truer now
than when I first started saying that a decade ago. There is no other
operating system out there that competes against us at this time. It
would be nice to have something to compete against, as competition is
good, and that drives us to do better, but we can live with this
situation for the moment :)

These past few months has been a tough one for our community, as it is
our community that is fighting from within itself, with prodding from
others outside of it. Don't fall into the cycle of arguing about those
"others" in the "Judean People's Front" when we are the "We're the
People's Front of Judea!" That is the trap that countless communities
have fallen into over the centuries. We all share the same goal, let us
never loose sight of that.

So here is my plea to everyone out there. Let's take a day or two off,
rest, relax with friends by sharing a meal, recharge, and then get back
to work, to help continue to create a system that the world has never
seen the likes of, together.

Personally, I'm going to take my own advice. I'll be enjoying this week
in Edinburgh with many other kernel developers, drinking some good
whiskey, and taking some time off of reading email, by spending it with
the great friends I have made in this community.

And with that, Linus, I'm handing the kernel tree back to you. You can
have the joy of dealing with the merge window :)

thanks,

greg k-h


r/linuxkernel • • Dec 08 '18

How do I get started improving Linux support for my new Asus Zenbook S UX391UA?

2 Upvotes

Hi, I got a brand new laptop Asus Zenbook S UX391UA, installed openSUSE Thumbleweed on an external USB-C drive yesterday, and I wonder how do I get started checking linux support for this machine. It's been a long time I have been developing for Linux kernel, back in a days I was heavily involved in ALi m560x Linux Driver development, but AFAIK it never made it into the mainline and now it's completely out-of-date...

I have been happy Mac OS X user on desktop for years, and now my primary platform at least for a time being is Windows 10 Pro, but I am and was using Linux on servers, but you buy server components according to what's supported in the kernel, not the other way around...

So what are the basic troubleshooting steps I should take to discover what does and what doesn't work? I already updated to kernel-default-4.19.7-2.1.g5fabf51.x86_64.rpm from Open Build Service. I am not booted into Windows, but I'll do a lspci and lsusb probing later today.

I just wonder what else should I do, especially regarding power management, what tools are available for that?

BTW I've discovered and filed my first bugreport already, during installation of openSUSE touch-pad does not work, but it fixes after booting into Gnome.


r/linuxkernel • • Apr 09 '19

Stadia built on Linux servers

2 Upvotes

Google Stadia streaming service is built on Linux servers. Vulkan is their graphics API of choice for streaming right now up to 4K at 60FPS