I know we all like to shit on what Canonical has become, but you have to respect just how much work they’ve put into the Linux ecosystem to make it more user friendly and mainstream over the years.
Agreed. Before the dark times, Ubuntu was the kickstarter for “wide” adoption to the “masses” (notice the quotes, lol) and making Linux even more accessible at that time. Similar to a degree of what Valve has an effect nowadays.
I actually never used the very first Ubuntu version and need to test it in a VM too. My first experience with Linux was probably Knoppix and my first installation SUSE Linux 9.2, but it was not ready back then. I switched to Linux full time by removing Windows XP and installing Ubuntu 8.04. Time definitely has passed, you can’t argue with that.
Nice! I read about that they would sent CDs for no cost. Also in countries where internet infrastructure wasn’t there yet, they were giving out CDs for free locally in a bus in example, like advertisements. Having a millionaire backing up a distribution surely helped its adoption. :D Actually this was one of the reason why I had confidence in the future of Ubuntu, back then.
I got a 6.0ish disk after giving them an email back in the day. I also remember the UI being easily modified. It was by far the easiest linux to get up and running with drivers for a couple of years.
I remember when Ubuntu came out I was working in a PC repair shop. Not gonna give any opinion on this but the standard procedure for people wanting a fresh XP but didn’t have a license key was “well it’s $90 for a fresh install, or we can put a pirate pro corporate on it”. I e-mailed canonical and they sent me a whole stack of Ubuntu CDs in nice branded sleeves. I kept it by the register and started offering that as an alternative to piracy for people that didn’t have a license key and didn’t wanna fork over the cash for one, Not many people chose that option, but I had a lot of good talks with people and plenty of people took a CD to try the live Ubuntu. I hope some of them ended up making the switch. I’m kinda disgruntled with conical these days but I’m an old greybeard who grew up in Slackware. I still recommend Ubuntu to beginners along with fedora.
I’ve enjoyed seeing some of these blasts from the past, but I admit it’s not as nice when the VM host window is captured as well. Just something to consider… I appreciate it all the same.
You can just cut the window border, to show the content of the VM. Doesn’t VirtualBox have a screenshot functionality for that? So you don’t need to edit the image or try to select with a border to capture the area. I used VirtualBox in the past (now on something better ;-) Quemu+Kvm+virt-manager), but totally forgot if it has this function at all.
With the maturity of the EXT4 file-system it’s not too often seeing any huge feature additions for this commonly used Linux file-system but there’s still the occasional wild performance optimization to uncover… With Linux 6.11 the EXT4 file-system can see upwards of a 20% performance boost in some scenarios.
Ted Ts’o sent out the EXT4 updates today for Linux 6.11.
He explained in that pull request: "Many cleanups and bug fixes in ext4, especially for the fast commit feature.
Up to 20% faster for fast devices using async direct I/O thanks to JBD2 optimizations.
Indeed the patch from Huawei’s Zhang Yi to speed up jbd2_transaction_committed() shows off some great improvements:
It’s great continuing to see EXT4 uncover new performance optimizations.
The original article contains 144 words, the summary contains 120 words. Saved 17%. I’m a bot and I’m open source!
When trying to install the one kernel I get exactly the same message as the first image in the post. The first error hints at an error in a posts installation script, which I have had issues with before. I used to delete these script to get over errors aaand that worked fine for some time. In case there has been some change in the error I’m getting, I haven’t picked up on it yet. Either way, here’s the output
EDIT: At the top of the message it says " Newest version already installed" so it seems to be blocking itself? Like I’m trying to install a package and it’s like -But I need that package to build this one-
I used to delete these script to get over errors aaand that worked fine for some time.
I can’t think of one time that I’ve done that in 20 years outside of repackaging applications for work because of crappy vendor supplied packages.
And you’re sure dkms and the headers are installed?
In situations like this, if bad enough I would usually temporarily remove mentioned packages until the apt fix works cleanly again and then reinstall whatever I was trying to do. But you’re saying you have removed post install scripts and manipulated packages? Hmm that seems like trouble.
I’m positive if I was infront of the terminal I could help you out, but I’m starting work for the day. Maybe someone else has a better idea. Sorry bro. But on a positive note, your system is certainly not beyond repair. This seems trivial with a little work and maybe someone who sees the issue better than I right now.
For others taking a look…. What was the command run before the apt fix?
Fair. The first thing I did was yesterday where I tried to add testing, experimental and unstable packages to apt. That didn’t quite work sonI reverted my changes my removing the .list files and recovering the previous default sources.list file. Then today In started up my PC and this was what I got, a black screen with a blinking white cursor. The apt-fix-broken is just something I picked up on during my many times I had to fix my distro… So that was one of the first things i tried after trying the startxcommand.
OK so when installing the the unsigned kernel, I get an error that the normal version isn’t installed. But when I try to install the normal version, it complains that the unsigned version isn’t installed…
I have now taken a look at the Xorg log files and they seem to be complaining about it not finding the nvidia kernel module, even though I just installed the nvidia-driver package. This is the complete file content
/var/logs/Xorg.0.log[ 271.351] X.Org X Server 1.21.1.11 X Protocol Version 11, Revision 0 [ 271.351] Current Operating System: Linux Marty-PC 6.9.7+bpo-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.9.7-1~bpo12+1 (2024-07-03) x86_64 [ 271.351] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.9.7+bpo-amd64 root=UUID=d4a79dc4-42f3-4ca3-a115-9e7fede5ab33 ro quiet splash nvidia-drm.modeset=1 [ 271.351] xorg-server 2:21.1.12-1 (https://www.debian.org/support) [ 271.351] Current version of pixman: 0.42.2 [ 271.351] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 271.351] Markers: (–) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 271.351] (==) Log file: “/var/log/Xorg.0.log”, Time: Thu Jul 18 20:00:51 2024 [ 271.351] (==) Using config file: “/etc/X11/xorg.conf” [ 271.351] (==) Using config directory: “/etc/X11/xorg.conf.d” [ 271.351] (==) Using system config directory “/usr/share/X11/xorg.conf.d” [ 271.352] (==) ServerLayout “Layout0” [ 271.352] (**) |–>Screen “Screen0” (0) [ 271.352] (**) | |–>Monitor “Monitor0” [ 271.352] (**) | |–>Device “Device0” [ 271.352] (**) | |–>GPUDevice “Device0” [ 271.352] (**) |–>Input Device “Keyboard0” [ 271.352] (**) |–>Input Device “Mouse0” [ 271.352] (**) Option “Xinerama” “0” [ 271.352] (**) Allowing byte-swapped clients [ 271.352] (==) Automatically adding devices [ 271.352] (==) Automatically enabling devices [ 271.352] (==) Automatically adding GPU devices [ 271.352] (==) Automatically binding GPU devices [ 271.352] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 271.352] (WW) The directory “/usr/share/fonts/X11/cyrillic” does not exist. [ 271.352] Entry deleted from font path. [ 271.352] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 271.352] (==) ModulePath set to “/usr/lib/xorg/modules” [ 271.352] (WW) Hotplugging is on, devices using drivers ‘kbd’, ‘mouse’ or ‘vmmouse’ will be disabled. [ 271.352] (WW) Disabling Keyboard0 [ 271.352] (WW) Disabling Mouse0 [ 271.352] (II) Loader magic: 0x559f2898ff00 [ 271.352] (II) Module ABI versions: [ 271.352] X.Org ANSI C Emulation: 0.4 [ 271.352] X.Org Video Driver: 25.2 [ 271.352] X.Org XInput driver : 24.4 [ 271.352] X.Org Server Extension : 10.0 [ 271.353] (++) using VT number 2 [ 271.355] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_32 [ 271.357] (–) PCI:*(1@0:0:0) 10de:1b83:10de:1b83 rev 161, Mem @ 0xd2000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00003000/128, BIOS @ 0x???/131072 [ 271.357] (II) LoadModule: “glx” [ 271.357] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 271.357] (II) Module glx: vendor=“X.Org Foundation” [ 271.357] compiled for 1.21.1.11, module version = 1.0.0 [ 271.357] ABI class: X.Org Server Extension, version 10.0 [ 271.357] (II) LoadModule: “nvidia” [ 271.358] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so [ 271.358] (II) Module nvidia: vendor=“NVIDIA Corporation” [ 271.358] compiled for 1.6.99.901, module version = 1.0.0 [ 271.358] Module class: X.Org Video Driver [ 271.358] (II) NVIDIA dlloader X Driver 535.183.01 Sun May 12 19:35:37 UTC 2024 [ 271.358] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 271.358] (II) Loading sub module “fb” [ 271.358] (II) LoadModule: “fb” [ 271.358] (II) Module “fb” already built-in [ 271.358] (II) Loading sub module “wfb” [ 271.358] (II) LoadModule: “wfb” [ 271.358] (II) Loading /usr/lib/xorg/modules/libwfb.so [ 271.358] (II) Module wfb: vendor=“X.Org Foundation” [ 271.358] compiled for 1.21.1.11, module version = 1.0.0 [ 271.358] ABI class: X.Org ANSI C Emulation, version 0.4 [ 271.363] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 271.363] (EE) NVIDIA: system’s kernel log for additional error messages and [ 271.363] (EE) NVIDIA: consult the NVIDIA README for details. [ 271.368] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 271.368] (EE) NVIDIA: system’s kernel log for additional error messages and [ 271.368] (EE) NVIDIA: consult the NVIDIA README for details. [ 271.368] (EE) No devices detected. [ 271.369] (EE) Fatal server error: [ 271.369] (EE) no screens found(EE) [ 271.369] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 271.369] (EE) Please also check the log file at “/var/log/Xorg.0.log” for additional information. [ 271.369] (EE) [ 271.371] (EE) Server terminated with error (1). Closing log file.
You left out the NVIDIA card part. This is super important. So you have two kernels in a bad state and the NVIDIA driver is probably not building out.
You’ve got a chicken and egg issue.
This isn’t a technical answer but simply a generalization of what probably needs to happen.
I would start over on whatever kernel situation you have going.
First uninstall the NVIDIA driver.
Then remove that unsigned kernel and its headers. Use the force option if necessary.
Ensure the base kernel and its headers are installed.
Reboot using standard kernel and then install nvidia-dkms package. Reboot.
It’s tough to tell you exactly what needs to be done because I’m not really sure what kind of damage you did or what the full extent of the errors are. You might need some force options or whatever but generally that’s all that needs to happen. YOU do not have a NVIDIA driver built for whatever kernel you’re using.
a posts installation script, which I have had issues with before. I used to delete these script to get over errors aaand that worked fine for some time.
You da hero!
Please tell me that you also tinker with used cars.
It appears that you're trying to install a kernel for which dkms can't build the version of the v4l2loopback kernel module that you have.
I don't see why this would affect Gnome, but if it's causing problems for the rest of the system maybe try uninstalling v4l2loopback-dkms until you can get a version that works, or else use an older kernel.
Alternately, if you're feeling brave and this is the same version that's in debian stable right now, you could edit /usr/src/v4l2loopback-0.12.7/v4l2loopback.c and replace strlcpy with strscpy in two places.
I really like the idea of BTRFS and what it can do. For my recent system, build in end of 2023 (not a year ago) I really thought about and compared the systems, but end up using EXT4. Here some thoughts I had:
I want to use BTRFS as my main system FS, but I wasn’t sure which alternative FS to use (there are other contenders too), if I need the extra functionality, if its 100% stable for me on a non Fedora system and I also did not want to spent the time learning and experimenting with it, yet. But I will. And if other distributions I install or boot into would work well with BTRFS, if they are not on the newest Kernel yet.
Sure! I’m interested into the “current” state or real world experience of it. Wouldn’t mind if you post it here. Although I am not sure how relevant it is 1 year later, because the filesystem is quite under development.
That its under development means that it’s being maintained. EXT4 is still being developed, so is xfs. And the other ones that are fairly popular, for that matter.
Thanks. But it’s important to note your experience report is based on the experience of 2019 and the slight edits aren’t changing that. That its being developed is not the same as under maintenance. EXT4 is fully developed and there are only optimizations in performance expected, if anything, while BTRFS still needs active development to improve compatibility and some other features.
I’m still curious to how to work with it and such a report is still welcome. I’ll give it a read. Edit: Hopefully my reply didn’t sound too negative. I’m interested in the process of going all of this, so the article is useful in a practical sense.
I’m not quite sure why people are still worried about the stability of btrfs when it has been rock solid for years. Synology has been using it for quite a while now in their NAS systems, they surely wouldn’t if it’d mean a lot of customers were at risk of losing their data.
There are valid reasons not to be using btrfs (although I’d argue most ordinary use cases don’t have a valid reason), but stability certainly isn’t one of them, independent of the distribution used (unless it’s ancient).
Wait til your table with all the checksums gets messed up on an “older” btrfs install. Happened to me on a VM because I didn’t know copy-on-write should be disabled for large frequently partially updated files. It also slowed that VMs IO down a lot.
Like most file systems, BTRFS is great if you know the edge cases. I recently moved to ZFS on my new work system, which has been a great change in terms of in-line snapshots and the like.
If EXT4 meets your needs, that’s awesome. If you understand how to use a different FS well or are willing to learn (and risk), I would also encourage other options as well.
Note my research of BTRFS is almost a year old now. And there was still a few headlines making round of problems with BTRFS in some cases. A controlled NAS system is not the same as random user configuration of a random desktop user. And as said in my comment, I was not sure if it would be stable for my installation (when I did my research) and did not claim it to be unstable. On the other side, I know for a fact that EXT4 is stable and I did not research more or experiment to find out which one is better for me.
Current state of BTRFS: btrfs.readthedocs.io/en/latest/Status.html (note when I did my research, Linux was at Kernel v6.4, therefore BTRFS was in a worse situation than today)
Interesting… but that just replaces an existing step with another step. I’d like to reduce the overall steps to get to each system. And if I can’t do that, I’d at least like to switch the order to win>EOS>Deb
I’d have a look at the archwiki and install GRUB on eos, and in your bios set eos to be the first boot option, and that will give you the grub boot menu with the option to boot eos, debian or windows.
A lot of us were running Debian when Ubuntu came out. It was polished and integrated to a degree that Debian wasn’t. It became popular for very good reasons.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.