this post was submitted on 12 Dec 2023
11 points (92.3% liked)

Linux

8119 readers
57 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 1 year ago
MODERATORS
MigratingtoLemmy@lemmy.world
11
Linux 6.6.x won't boot on my System (lemmy.world)
submitted 11 months ago by node815@lemmy.world to c/linux@lemmy.world
7 comments fedilink hide all child comments
 

I've noticed that when 6.6.1 came out and it came time to reboot after it installed, I couldn't boot into the OS anymore, it simply hangs on a black screen for about 10-15 minutes then reboots after selecting it. I'm currently on the LTS kernel which is 6.1.67-1-lts (64-bit) with no issues. I figured after updating to the latest one 6.6.6. things may be better but no. Each new kernel release, I test it with the same results.

CPU is CPU: quad core Intel Core i7-2600S (-MT MCP-) on Dell Optiplex 990 SFF PC with 16GB Ram in UEFI mode. Via either Grub or Systemd-boot. On one hand, I'm thinking that my computer's time may have finally come up once the LTS moves to 6.6.1 but, until then, and I can procure a newer system, I'd like to see if anyone else has encountered such a thing.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] tal@lemmy.today -1 points 11 months ago* (last edited 11 months ago) (1 children)

I mean, no, but this probably isn't the way you want to go about dealing with it.

If you know how to build and install your own kernel out of git, and how to run a git bisect, you could go back and identify the exact commit to the kernel that introduced your problem, which would probably do a lot to help accelerate getting the problem fixed.

[โ€“] node815@lemmy.world 1 points 11 months ago

I'm not that good with building kernels, in fact have never done it. By LTS I mean "Long Term Support" as in a kernel which will not be unsupported for a few years yet.