New Updates For A New Decade | The Roundup #14

elfprince

JoshStrobl I will wait a little before doing this update. Thank you for clearing up my other questions. 😃

WetGeek

JoshStrobl We've tested this for like a week now and you can see all the reports of it being fine.

He uses his one and only computer for work. What if some proprietary piece of software that's required for his work has a serious problem with the upgrade? I.e., software that hasn't been tested for a week?

In that case, I'd be nervous, too. Elfprince, just be sure you have a good backup available when you do upgrade.

JoshStrobl

WetGeek What if some proprietary piece of software that's required for his work has a serious problem with the upgrade? I.e., software that hasn't been tested for a week?

If it's a proprietary piece of software it's not likely going to be in the repo in the first place, in which how would it ever be tested? I'm sorry but it's just not a good argument.

WetGeek

JoshStrobl I'm sorry but it's just not a good argument

It is if his computer runs what he uses at work just fine now, but perhaps won't run it after this update. That's why I suggested creating a backup before the upgrade, if he doesn't have one already. What got my attention was where he stated that he has only that one work machine available. I'd be careful, too.

[deleted]

Another Budgie update for some friends were successful, used the terminal to do the following: sudo eopkg up, sudo eopkg up (just to be sure), sudo usysconf run -f, sudo sync, logout, hold power button. Logged back in after the update and did a: sudo usysconf run -f , which completed without any issues.

Tried with a new Solus Gnome installation in gnome-boxes, where i installed the latest version of these extensions Arc Menu, Dash to panel, Show desktop button, the update went well with no issues. Will update my colleagues exact same Gnome installation on monday, but just to be sure i will remove any extensions first, and reinstall the latest version of the extension after the update...

Have not had any issues so far using Solus Budgie during the day, after i did the update this morning. it's been running like a champ.

paracetamol

WetGeek With all due respect, someone stressing this much over upgrades due to relying on just one machine should rethink using a rolling distro and choose a LTS super stable workhorse such as Debian.

elfprince Reading your post I get a suspicion there's some confusion. You won't need to log out (an optional step) and hard reset your machine every time after the update. Just once, to allow the new systemd to kick in.

Leandros_Adigard

I woke up this morning and updated my system, to my shame, without reading anything beforehand. So, it was entirely my fault when I was not able to shutdown -r now due to access permissions, etc. I rolled back to the previous eopkg operation listed by sudo eopkg history, came to the forum and realized that I was a dunce for not reading before an update!

After following instructions, I had a flawless update (other than the previously reported udisks issue). sudo eopkg up then sudo usysconf run -f followed by sudo sync and I was able to logout and hard reboot. No problems.

Thanks again Solus dev team for delivering a brilliant system.

Cheers

WetGeek

paracetamol With all due respect, someone stressing this much over upgrades due to relying on just one machine should rethink using a rolling distro and choose a LTS super stable workhorse such as Debian.

I fully agree, so long as that choice is available to him. Although, I'd probably choose openSUSE Leap -- just personal preference.

Where I've worked, it wasn't my decision which OS I used. It was up to our IT department instead. We couldn't even use Windows 10 for the first year it was available. It just wasn't a priority for IT until Windows 7 got closer to end-of-support.

elfprince

paracetamol Can you blame me if I prefer Solus? 🤣 Would you turn away potential Window and other Linux distro converts from Solus, just because they like system stability but they love Solus? They just shy away from potential system crashes, requiring a reinstall. I have tons of stuff installed over the years. No intention to have to repeat the effort.

Tuxramus

Thanks for all the hard work, guys! Loving today's update, ESync works now in Lutris, woohoo! My system is also running a bit smoother and definitely a lot cooler.

elfprince

Decided to 'bite the bullet'. Followed the steps supplied by Solus dev team. Update smooth. No problems, except still no wifi with the new kernel, so will use the 5.3.18-140-1 for now. Thanks for all the encouragement guys!

WetGeek

elfprince Decided to 'bite the bullet'.

I'm glad it worked out for you!

Renard

elfprince Huh? No WiFi with the new kernel? What kind of hardware are you using Solus on?

By the way, I am still pleased to know that you were able to use Solus with an older kernel.

elfprince

WetGeek Thanks, me too!

brent

elfprince
I read the documentation and was scared as crap of this update. I only have one system, too. And my WIN backup is gone. I decided to "grip it and rip it" in golfing parlance..I did not take precautions as others did. Blind faith has got me this far with solus🙂. It was bumpy today. Black screen, tty logn, error messages in red type. It all worked out eventually. I think.

elfprince

Renard
$ inxi -Fxxxza --no-host System: Kernel: 5.4.12-143.current x86_64 bits: 64 compiler: gcc v: 9.2.0 parameters: initrd=\EFI\com.solus-project\initrd-com.solus-project.current.5.4.12-143 root=UUID=d15e0285-f59b-4347-8f0c-e7a49581cb66 quiet loglevel=3 splash systemd.show_status=false rw radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 systemd.unified_cgroup_hierarchy=0 resume=UUID=0ab6d17f-b0cf-4898-8a3f-3ba3912bea6a Desktop: Budgie 10.5.1 info: budgie-panel wm: budgie-wm dm: LightDM 1.30.0 Distro: Solus 4.0 Machine: Type: Mini-pc System: Intel product: NUC7CJYH v: J67971-400 serial: <filter> Chassis: type: 35 v: 2.0 serial: <filter> Mobo: Intel model: NUC7JYB v: J67967-400 serial: <filter> UEFI: Intel v: JYGLKCPX.86A.0043.2018.0814.1104 date: 08/14/2018 CPU: Topology: Dual Core model: Intel Celeron J4005 bits: 64 type: MCP arch: Goldmont Plus family: 6 model-id: 7A (122) stepping: 1 microcode: 32 L2 cache: 4096 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 7987 Speed: 2660 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 2645 2: 2596 Vulnerabilities: Type: itlb_multihit status: Not affected Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown mitigation: PTI Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling Type: tsx_async_abort status: Not affected Graphics: Device-1: Intel UHD Graphics 605 driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3185 Display: x11 server: X.Org 1.20.6 driver: modesetting unloaded: fbdev,vesa alternate: intel compositor: budgie-wm resolution: 2560x1440~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics 600 (Geminilake 2x6) v: 4.6 Mesa 19.3.2 compat-v: 3.0 direct render: Yes Audio: Device-1: Intel driver: snd_hda_intel v: kernel bus ID: 00:0e.0 chip ID: 8086:3198 Device-2: Logitech Webcam C200 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-3:2 chip ID: 046d:0802 serial: <filter> Sound Server: ALSA v: k5.4.12-143.current Network: Device-1: Intel driver: iwlwifi v: kernel port: f000 bus ID: 00:0c.0 chip ID: 8086:31dc IF: wlo2 state: N/A mac: N/A Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Intel driver: r8169 v: kernel port: e000 bus ID: 02:00.0 chip ID: 10ec:8168 IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter> Drives: Local Storage: total: 59.63 GiB used: 25.76 GiB (43.2%) ID-1: /dev/sda vendor: Kingston model: SNV425S264GB size: 59.63 GiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 126a scheme: GPT Partition: ID-1: / raw size: 55.42 GiB size: 54.30 GiB (97.98%) used: 25.76 GiB (47.4%) fs: ext4 dev: /dev/dm-1 Sensors: System Temperatures: cpu: 54.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 210 Uptime: 1h 04m Memory: 7.37 GiB used: 3.04 GiB (41.3%) Init: systemd v: 244 runlevel: 5 Compilers: gcc: 9.2.0 Shell: bash v: 5.0.11 running in: gnome-terminal inxi: 3.0.37

EbonJaeger

Renard The 5.4 kernel series has some hardware regressions. Go figure, considering it's going to be the new LTS.

elfprince

brent Wow, good to hear it worked out in the end. 👍️

N1X3L

Fair winds and smooth sailing here on my UEFI system update. My BIOS system is slated for updating when I return to campus Monday. I'll post if something comes up, but otherwise no news is good news. Thanks, Team!

Quinix

Ran the update over the software center. Then a sudo sync in the terminal, then logout and switched off using the switch as described.
Then switched on and everything apparently went well. No problem found so far.

Very well done guys or solus team
Thanks and best regards

« Previous Page Next Page »