[01:00] <Varro> I have NVidia and an integrated graphics on my laptop. How do I disable the NVidia graphics temporarily to save power?
[01:04] <Bashing-om> Varro: Intel chip as the integrated ? try then ' sudo prime-select intel '.
[01:05] <Varro> Yeah integrated. Thanks
=== gnuself1 is now known as gnuself
=== shokohsc5108 is now known as shokohsc510
=== tristan123 is now known as tristan_
[04:48] <illuminated> on an ubuntu box I have an external hard drive that is detected but unmountable.. is there a fix?
[04:49] <rbox> what does "unmountable" mean
[04:52] <illuminated> it doesn't mount
[04:53] <rbox> what error
[04:57] <illuminated> I'm going to try to fsck it
=== guiverc2 is now known as guiverc
[07:32] <jea0p> hay.
[07:32] <jea0p> heloww
=== TristanLh1 is now known as TristanLh
[07:59] <guiverc> illuminated, you mount partitions & particularly file-systems; drives rarely (since the 1980s where some unix machines didn't partition unlike DOS/windows/Linux) don't have partitions or file-systems on them.
[08:14] <weedmic> illuminated: pls repeast the issue - i seem to have missed it and only see one response.
[08:51] <zphinx> can i use preseed for ubuntu 20.04 uefi installs? im trying to get a packer config going for an uefi install but i cant seem to progress
[09:04] <zach> hi
[09:04] <zach> i install kde-full in ubuntu
[09:05] <zach> i face a problem, when i am working on laptop its become blank screen and suspend session
[09:05] <zach> can anyone one help how to fix this problem
=== ripple is now known as ripple1
[10:09] <pat> Hi. I'm using Ubuntu 22.04 with the proprietary nvidia drivers (latest version, 535.86.05). Graphics card rtx 4090 and 3090ti, with two displays. Using gdk3. I have nouveau drivers blacklisted. I was previously on an older version of the drivers, but I noticed a bug, whenever I go fullscreen in vlc player watching a video my primary display (LG CX1) keeps flickering on and off, displaying "The Instant Game Response is launched".
[10:09] <pat> This is a problem that has happened before with this screen and playstations, and is related to VRR (g-sync) and ALLM. If I disable gsync, the problem does not occur because ALLM is never activated, so I don't get the flicker. However the choppiness makes watching videos untenable. I suspected it might be a bug in the proprietary nvidia drivers, so I updated to the latest version of the drivers. The bug is still present. HOWEVER, I
[10:09] <pat> noticed that in my Gnome Screen Display settings, if I set my scale to 100%, the bug does not occur. It's only when I'm scaling my monitor to 125% that this problem happens. So I'm not sure if this is a Ubuntu bug, a bug with the nvidia proprietary drivers, or a combination of both. Not sure what to do or who to message about this. Any suggestions?
[10:18] <weedmic> pat:  1st, which DE are you using if it is not gnome?  which compositor are you using:  "inxi -Gxx | grep compositor"?
[10:18] <pat> @weedmic,   Display: x11 server: X.Org v: 1.21.1.4 compositor: gnome-shell v: 42.9
[10:25] <weedmic> pat - i was afraid it might be wayland - since I keep hearing about issues with that and nvidia, but... not your case - i'm re-reading your posts.
[10:26] <pat> Linux pc 6.2.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 13 16:27:29 UTC 2 x86_64 x86_64 x86_64 GNU/Linux (if it helps)
[10:27] <weedmic> isn't vlc player a way to watch mp3 files? - is there a chance you do have a game runnign in the background you did not actually exit.  I know one of my kids often leaves steam running - although he swears he exits properly.
[10:28] <weedmic> I do not understand what playstation has to do with ubuntu 22.04 - are you using a monitor that is plugged into something else - but communicating w ubuntu through some output cable?
[10:30] <weedmic> let's ensure you are using nvidia also - "inxi -Gxx | grep Device"
[10:32] <pat> VLC does video & audio I believe. It happens with the default video player as well. No games, no, I don't have any installed/don't use games on this PC. The playstation thing was how I figured out it's related to VRR/gsync/ALLM activation. No, it's just directly into my PC via HDMI.
[10:33] <pat>   Device-1: NVIDIA vendor: ASUSTeK driver: nvidia v: 535.86.05 pcie:
[10:33] <pat>   Device-2: NVIDIA vendor: ASUSTeK driver: nvidia v: 535.86.05 pcie:
[10:34] <weedmic> run this to see if it actually loaded "lsmod"
[10:35] <weedmic> I do not understand this at all -  "The Instant Game Response is launched" - any help is appreciated.
[10:35] <pat> video                  73728  2 asus_wmi,nvidia_modeset
[10:35] <pat> lots of mentions of nvidia_drm
[10:36] <weedmic> also, did you reboot since the nvidia was compiled into the kernel?
[10:36] <weedmic> sure seems as if you are using nvidia and the machine knows there are two different cards.
[10:37] <pat> So that is what this screen (LG CX1) displays when ALLM (auto low latency mode) is activated. It's related to interactions with gsync (VRR). When apps go full screen (like games or videos), the screen automatically displays that message and briefly goes blank. This is normal behavior (on Windows etc). However getting stuck in a loop of that message is not normal.
[10:37] <pat> Yeah I did
[10:40] <pat> https://img.nerdburglars.net/wp-content/uploads/2022/05/20220504_211915.jpg here's an example of that popup
[10:40] <pat> https://nerdburglars.net/hardwareguides/lg-cx-flickering-instant-game-response-launched-on-ps5/ - the thread about it happening with PS5 that points to being related to VRR/gsync activating ALLM
[10:42] <pat> and another: https://www.reddit.com/r/OLED/comments/m4k6wb/instant_game_response_activating_over_and_over/ -- someone in here saying they had the same problem on PC with a 3080. This all works fine on windows btw, and with scaling at 100%. the weird part is that scaling set to 125% in ubuntu seems to be the trigger
[10:42] <weedmic> I might not get the sentence exactly, but I do not know what ALLM is (but appreciate you spelling it out).  Seems to me you need gsync, but I don't know what gsync VRR is.    however, after seeing the pic, I think it is a physical setting on the monitor.  now I get what the ALLM is.
[10:43] <weedmic> perhaps a chat room with the manufacturer of the monitor?  I now believe this is not ubuntu related (nor really nvidia related either).  I think you just need the right setting.
[10:47] <pat> Hmm, if not ubuntu or nvidia related why does this not happen on Windows, and why does the Ubuntu scaling setting seem to impact whether it happens or not? (not saying you're wrong, just trying to understand the logic)
[10:49] <weedmic> ask again - someone else may have an idea, but it seems likely to me that if works when you do some settings on the monitor which means nvidia and ubuntu are working.  I, unfortunately, dnk, how to proceed (other than to asks others with similar monitors).
[10:54] <pat> It seems to be an issue of getting stuck in a loop of activating ALLM. When I go fullscreen in VLC, Ubuntu and/or the nvidia drivers must be sending a signal to the graphics card to tell it that it should enable/is ready to enable ALLM. it's possible that it's a bug with the TV, but also possible to be a bug with the OS and/or nvidia drivers as well. It's really hard to say/diagnose though :( Like is the TV getting stuck in a weird
[10:54] <pat> loop, or is it sending a triggering signal from the graphics card over and over again. Maybe there's some log somewhere that could help indicate that but I couldn't see anything in the logs I did look at (xorg logs etc)
[10:55] <pat> The fact that it doesnt happen in Windows is interesting though. Perhaps due to nvidia driver differences across the two sending different signals or behaving differently and the TV not handling one particular case properly. Or perhaps due to a bug in the nvidia driver in Ubuntu. And then also, the fact scaling seems to change the behavior is extra odd as well. All around very strange.
[12:04] <imhere> let's get this party started
[12:54] <tekisui> ni hao
[12:54] <tekisui> i have a hammer 2 smurfphone
[12:54] <tekisui> now i found out i can charge it with the usb port in the monitor
[12:54] <tekisui> but i also use it to connect to the interweb
[12:54] <tekisui> there the usb -thetering doesn´t wolk somehow ?
[12:54] <tekisui> i have Lubuntu 22.04
[12:57] <tomreyn> tekisui: we don't know anything about the usb hub on your monitor. you seem to have a hardware question.
[12:57] <tekisui> ahh i hoped hardware would solve it
[12:57] <tekisui> software*
[12:57] <tomreyn> passing through data *might* work if you have a usb-c connection between computer and monitor
[12:57] <tekisui> i think it recognized the usb stick in 18.04
[12:57] <tekisui> am pretty sure ubuntu could connect before
[12:59] <tekisui> is it an nvidia server problem ?
[13:00] <tekisui> would usb-usb cable fix it ?
[13:00] <tekisui> if i plug an usb cable in the dekstop and also in the monitor
[13:01] <tekisui> or do i blow up the monitor ?:D
[13:01] <tekisui> damn i think the thing got digital input also
[13:04] <tekisui> well i guess it´s protected
[13:05] <tomreyn> so you have an android smartphone connected to a monitor (which?). and you have some connection (which?) between the computer and the monitor (which?). and now you expect to be able to use the smartphone fort tethering. this might work if you have a usb-c connection between the computer and the monitor, which connects this to the usb connected smartphone. First of all you'd want to check what your monitor supports. Then, if it does support this
[13:05] <tomreyn> scenario, check whether you have suitable wiring between the devices. Then check what is logged in    journalctl -f    or    sudo udevadmin monitor   when you connect the monitor and, seperately, the phone
[13:06] <tekisui> ok..
[13:06] <tekisui> am pretty sure in ubuntu 18.04 the monitor recognized an usb stick
[13:06] <tekisui> i could also use my fuji film
[13:07] <weedmic> tekisui: most phones do not allow you to use the cable for simulateous data and power.  you have to pick one.  you might want to post your question in #hardware with the model number of the monitor and phone
[13:07] <tekisui> ok
[13:07] <tekisui> reroute
[13:08] <weedmic> i connect my phone to a monitor, then the monitor allows me to attach all kinds of things - including power, but it is to power the monitor.  I generally start w a fully charged phone.
[13:13] <tekisui> is there a way to reset ubuntu, if you mess up ??
[13:13] <tekisui> sometimes it won´t start
[13:14] <tekisui> like go back before you made the changes
[13:14] <tomreyn> you can reinstall, but it may be better to understand why "sometimes it won't start up"
[13:14] <tekisui> umm
[13:14] <tekisui> i mean can you enter safe mode or something ?
[13:15] <tomreyn> there's a recovery mode, and a safe graphics mode. but they may not do what you expect.
[13:15] <tekisui> hmm
[13:15] <tekisui> ok, merci
[13:16] <tomreyn> restoring an earlier system state is only possible if you use a file system supporting that and have it setup accordingly
[13:16] <tomreyn> normally we use backups for this purpose.
[13:16] <tomreyn> or... better yet.. identify and fix issues.
[13:16] <tekisui> umm
[13:17] <tomreyn> because... on linux ... most of the time... you can!
[13:18] <tekisui> :)
[13:18] <tekisui> you use ubuntu touch ?
[13:18] <weedmic> define "mess up"?  you can do anything you want - even change apt to zypper, kde to gnome to xfce.  but... sometimes it's just not worth the time b/c a new install takes like 8 mins.
[13:19] <tekisui> https://i.imgur.com/Q346G9A.png
[13:20] <tekisui> would changing to binairy driver solve it ?
[13:20] <tomreyn> what is "it"?
[13:20] <tekisui> the usb port in the monitor not working properly
[13:20] <tekisui> it use to work in ubuntu 18.04
[13:20] <tekisui> am pretty sure
[13:21] <tomreyn> to fix the usb port in your monitor, fix your monitor
[13:21] <tekisui> hmm if i break the system i can select safe graphic mode and it will use Xorg ?
[13:22] <weedmic> not likely if you need the 390 driver - which one do you need?
[13:22] <tekisui> one that works
[13:22] <tekisui> well cross fingers..
[13:23] <weedmic> search the nvidia card you have and "which driver" "ubuntu" and see.
=== jack is now known as fred101
[13:31] <fred101> ubuntu 22.04.3 - tried to install from nvidia site 535 - dont work - cant get nouveau to work again.
[13:39] <tomreyn> fred101: sudo apt update && sudo apt purge nvidia*
[13:40] <tomreyn> + reboot
=== shokohsc5105 is now known as shokohsc510
[13:40] <tomreyn> and don't install nvidia.com downloaded drivers in the future, use ubuntu's
[13:40] <fred101> ok tom, thanks.
[13:46] <AxelW> anybody here?
[13:51] <tomreyn> AxelW: a lot. you'll get a better response when you'll ask an ubuntu support question
=== jack is now known as fred101
[14:04] <fred101> tomreyn,  it blacklisted nouveau - all fixed -  thanks.
=== Levy is now known as qiedk1
[14:05] <fred101> have a good day.
[14:12] <haoms> can anyone tell me which man page section is denoted by "3X". just 3 ist for library functions, but what is 3X?
[14:18] <tekisui> i found lsusb
[14:18] <tekisui> it shows the usb´s connected
[14:22] <tomreyn> haoms: https://en.wikipedia.org/wiki/Man_page#Manual_sections
[14:23] <tomreyn> the "x" in "3x" *might* refer to X window system specific libs, but i'm guessing.
[14:44] <haoms> tomreyn: thanks, i have already looked there, but didnt find the 3X section. notably, the ncurses pages are sorted into 3X, and I am looking why that is, but had no success.
[14:44] <haoms> I dont think that the X stands for x windows system.
=== shlom is now known as V1A
[15:09] <deadrom> hi
[15:10] <deadrom> got an usb3-togbit adapter here (broken mobo nic) which is at 100mbit only. device should allow gbit. powercycled the switch (run of the mill 8port desktop), told the interface to renegotiate with ethtool -r , still at 100. anybody have any other ideas?
[15:11] <deadrom> *usb3-to-gbit
[15:11] <deadrom> 22.04LTS
[15:17] <mybalzitch> diff cable/
[15:17] <mybalzitch> what chipset does the usb to ethernet device use
[15:17] <mybalzitch> you can also try forcing it to link at gbit, YMMV
=== chris14_ is now known as chris14
[15:21] <deadrom> got an intel pcie lying around, ill go for that
[15:33] <tekisui> well i fixed the nokia
[15:33] <tekisui> :)
[16:22] <confuseus> +-+
[17:09] <tekisui> https://www.ubuntu-nl.org/live-chat/
[17:09] <tekisui> is not working
[17:10] <leftyfb> !nl | tekisui
[17:10] <ubottu> tekisui: Nederlandstalige ondersteuning voor Ubuntu (en vers gezette koffie) is te vinden in #ubuntu-nl
[17:11] <tekisui> aha
[17:11] <tekisui> danke
=== jean-loups is now known as white-wolf
[18:02] <francas> 2023
[18:17] <zetheroo> My Ubuntu 22.04 system keeps intermittently freezing up. I have a few things running, but there is plenty of memory available and CPU usage is ~25%. I suspect the SSD might be getting worn out. How can I see the health of the SSD and if that is the performance bottleneck?
[18:21] <oerheks> gnome disks > smart selftest from the menu
[18:22] <zetheroo> ok, the disk is only 6.5 months old.
[18:23] <zetheroo> Uncorrectable ECC Count is over 9000
[18:23] <oerheks> that is not good.
[18:23] <oerheks> RMA ?
[18:23] <zetheroo> Maybe :/
[18:24] <zetheroo> What would be a count that is negligible?
[18:24] <zetheroo> Power Cycle Count is 2882
[18:25] <oerheks> Not sure what the warranty says, 1000?
[18:26] <oerheks> like acceptable lcd bits errors, 10
[18:27] <oerheks> you might want to do a long test https://help.ubuntu.com/community/Smartmontools
[18:28] <oerheks> !info gSmartcontrol
[18:28] <ubottu> gsmartcontrol (1.1.4-1, lunar): graphical user interface for smartctl. In component universe, is extra. Built by gsmartcontrol. Size 528 kB / 1,698 kB
[18:28] <zetheroo> according to my purchase records, this SSD is 4 years old :/
[18:28] <zetheroo> How is the SMART value saying only 6 months and 18 days?
[18:29] <oerheks> probably a low level format
[18:29] <zetheroo> hmm ok
[18:42] <jhutchins> zetheroo: Has it been in continuous service since you got it?
[18:43] <zetheroo> pretty much
[18:43] <zetheroo> it's in my main laptop
[18:45] <zetheroo> I notice especially if I am copying data to an NFS share that things tend to lockup as well
[19:09] <leftyfb> zetheroo: backup data, replace SSD, rebuild from scratch.
=== pretty-baby is now known as snapd-pb
[19:24] <zetheroo>  leftyfb: would it be a bad idea to do a clonezilla disk clone to a new SSD?
[19:30] <toddc> zetheroo: that is a good way  easy if the new drive is the same size or bigger  follow the prompts beginner easy
[19:31] <zetheroo> yes, toddc - I've done it many times before. Was just wondering if there was any reason not to do it in this case.
[19:33] <zetheroo> On another topic - is it normal for the transfer of data to an NFS share/mount to be very fast initially but then come to a complete halt for a while before continuing?
[19:33] <zetheroo> With an SMB share/mount the transfer speed is slower but continuous
[19:37] <jdsfighter> Anyone had issues with boot hanging for an unspecified amount of time when using `quiet splash`? Removing quiet splash results in completely normal boots, albeit filled with logs. Adding splash in any capacity causes boot to hang for 1-infinity minutes, depending on how the laptop is feeling apparently. (Intel/nvidia rtx 4070m graphics. 23.04)
[19:41] <lotuspsychje> jdsfighter: both text and normal boots should result the same in time, can you trace in textboot, where the bottleneck is/stalls at?
[19:44] <jdsfighter> lotuspsychje: I'm unfortunately not familiar with the process
[19:45] <lotuspsychje> jdsfighter: removing 'quiet splash' changes your boot to text mode booting, then where your boot hangs, write it down at that point
[19:46] <lotuspsychje> jdsfighter: did you update-grub too after the grub edit?
[19:46] <snapd-pb> Perte de contrôle pour les développeurs et les utilisateurs Linux expérimentés Quid de Snapd.
[19:46] <lotuspsychje> !fr | snapd-pb
[19:46] <ubottu> snapd-pb: Nous sommes desoles mais ce canal est en anglais uniquement. Si vous avez besoin d'aide ou voulez discuter en français, veuillez taper «/join #ubuntu-fr» ou «/join #ubuntu-qc». Merci.
[19:46] <snapd-pb> https://www.zdnet.fr/actualites/un-nouvel-ubuntu-est-en-preparation-avec-un-linux-immuable-oui-je-vous-explique-ce-que-c-est-39959014.htm
[19:46] <snapd-pb> okay
[19:48] <jdsfighter> lotuspsychje: Ah, yes. I do have that recorded. I also did do update-grub. The boot hangs at the following line every time: "Bluetooth: hci0: Malformed MSFT vendor event:0x02". There are additional logs present that vary based on whether `quiet` is present or not
[19:49] <lotuspsychje> jdsfighter: if you noticed your booting is text only, quiet splash was done correctly
[19:50] <lotuspsychje> jdsfighter: "quiet splash" =normal boot  "" = text boot
[19:51] <jdsfighter> lotuspsychje: with "quiet splash" there is still a small amount of text that shows a few errors. After a varying amount of time, the system loads into the desktop environment/login screen. My expectation is that rather than seeing those handful of errors, I would see the plymouth screen
[19:52] <lotuspsychje> jdsfighter: the small amount of text you see with "quiet splash" ON is normal thing just before gdm booting into your desktop
[19:52] <jdsfighter> lotuspsychje: Instead, what happens is that with quiet splash, the boot takes much longer and I have no real information as to why. With text-boot, the system fully boots in < 10 seconds. With splash, the system boots in anywhere from 10 seconds to 40+ minutes.
[19:52] <lotuspsychje> jdsfighter: the real bottleneck might show when you boot into textmode
[19:54] <lotuspsychje> jdsfighter: heres what you can do, after login to desktop try; systemd-analyze blame
[19:55] <lotuspsychje> jdsfighter: and/or systemd-analyze  or systemd-analyze critical-chain
[19:55] <lotuspsychje> that might give you an overview to see whats happening under your system hood
[19:55] <jdsfighter> lotuspsychje: 1min 35.557s plymouth-quit-wait.service | 1min 31.728s gpu-manager.service
[19:56] <jdsfighter> lotuspsychje: Looks like it
[19:59] <lotuspsychje> jdsfighter: yeah both looks long times, are you on an ssd or HD spinner?
[19:59] <jdsfighter> I'm running all NVME SSD on a brand new laptop
[19:59] <lotuspsychje> oof
[19:59] <lotuspsychje> jdsfighter: nvidia card?
[19:59] <jdsfighter> It's pretty bleeding edge
[19:59] <jdsfighter> Yeah, RTX 4070m
[19:59] <lotuspsychje> jdsfighter: login to xorg or wayland?
[20:00] <jdsfighter> I'm unfortunately not sure. Bit new to *nix as a desktop environment. Mostly a windows user that does some docker/dev work against linux
[20:00] <jdsfighter> I think xorg
[20:01] <lotuspsychje> jdsfighter: nvidia and wayland is a work in progress, so xorg is needed in your case
[20:01] <jdsfighter> lotuspsychje: echo $XDG_SESSION_TYPE tells me x11
[20:01] <lotuspsychje> jdsfighter: you also might wanna check your dmesg is graphics drivers are lacking
[20:01] <lotuspsychje> as your analyze shows gpu related delay
[20:02] <lotuspsychje> sudo lshw -C video , can also help find out
[20:04] <jdsfighter> lotuspsychje: Seems fairly standard to me: https://paste.ubuntu.com/p/KyXsVDPdwp/
[20:05] <lotuspsychje> jdsfighter: yeah driver is loaded, pastebin your full dmesg?
[20:06] <lotuspsychje> jdsfighter: i just gonna log off for tonight, other volunteers surely will continue with you
[20:08] <jdsfighter> lotuspsychje: No worries! I've been working on this all day and I've really gotta get back to actually writing some code. Maybe an issue for another day
[20:09] <geth_> kp
[20:10] <tekisui> hello, am trying to get the usb port on my monitor to work
[20:10] <tekisui> i tried powertop
[20:10] <tekisui> can i enable anything there ?
[20:11] <rbox> what does dmesg say when you plug the monitors usb cable in
[20:12] <tekisui> Where should i look, itś a long list
[20:13] <rbox> look at dmesg
[20:13] <rbox> plug it in
[20:13] <rbox> look again
[20:13] <rbox> the new stuf will be at the bottom
[20:14] <tekisui>    1.130276] hub 3-0:1.0: USB hub found
[20:14] <tekisui> [    1.130287] hub 3-0:1.0: 2 ports detected
[20:14] <tekisui> maybe this is it ?
[20:14] <rbox> thats all it says? 2 lines?
[20:14] <tekisui> nahh a whole bunch
[20:14] <tekisui> well it finds more hubs so it seems
[20:15] <tekisui> ah snap
[20:15] <tekisui> seems firefox is blocking the terminal
[20:17] <tekisui> this is in red: [ 1547.658015] sd 7:0:0:0: [sdf] No Caching mode page found
[20:17] <tekisui> [ 1547.658021] sd 7:0:0:0: [sdf] Assuming drive cache: write through
[20:18] <rbox> thats fine
[20:18] <tekisui> ok
[20:19] <tekisui> [ 1546.131362] usb 3-2: new high-speed USB device number 5 using xhci_hcd
[20:19] <tekisui> is this it ?
[20:19] <rbox> is this what
[20:20] <tekisui> the usb port from the monitor
[20:20] <tekisui> it does have electricity
[20:21] <tekisui> [ 1547.941255] FAT-fs (sdf): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[20:21] <tekisui> fsck doesn´t seem a good idea
[20:22] <tekisui> well i think an hdmi cable might solve it
=== LVSMBDHRLBDIK is now known as zerotwo
[20:24] <Menzador> I have a stupid question. Is there another place I need to have nvidia-settings write xorg.conf for it to work? I'm running Ubuntu 23.04 on a custom machine (ASUS TUF Gaming Z490-PLUS, NVIDIA RTX 3070) and I've been saving to the default location (/etc/X11/xorg.conf), specifically to take advantage of my 240 Hz monitor, but the refresh rate change is lost on reboot
[20:24] <Menzador> (the xorg.conf file is still saved in /etc/X11/)
[20:24] <tekisui> nvidia x server
[20:24] <jdsfighter> I captured a slow started dmesg after any ideas what's going wrong? https://paste.ubuntu.com/p/qX6kwsCrnN/
[20:24] <tarzeau> Menzador: i've got 100 machines with nvidia cards from 6 years ago to until right now. i never have to write xorg.conf. from 1 to 4 screens
[20:25] <Menzador> tekisui: Yes, the package name for "NVIDIA X Server Settings" is nvidia-settings
[20:26] <Menzador> tarzeau: So simply clicking "Apply" kept your settings? Did you start on an older version of Ubuntu and run release upgrades when they became available? Just gathering more info
[20:26] <tarzeau> Menzador: yes 6 generations of lts releases with nvidia repo drivers including cuda
[20:27] <tarzeau> new installation when system disk breaks.
[20:27] <Menzador> tarzeau: Can't blame ya, I just switched *back* to Ubuntu from Arch Linux
[20:27] <tarzeau> Menzador: when you have 100 machines, you don't want to run anything interactive gui tool 100 times
[20:27] <tarzeau> Menzador: we decided to switch back to debian
[20:27] <Menzador> Well I only have one :P
[20:28] <tarzeau> well it's not exactly mine. but i'm root@
[20:28] <Menzador> I mean I could try with [ sudo -i ] if I wanted
[20:28] <jdsfighter> I'm almost positive my slow startup is related to Nvidia somehow. This is a 2023 model Lenovo Legion 5 Pro intel i9, nvidia rtx 4070.
[20:28] <Menzador> jdsfighter: Is that a laptop or a desktop?
[20:28] <jdsfighter> Menzador: laptop
[20:29] <Menzador> jdsfighter: Mmm. I doubt it, unless you're getting tons of live dmesg input with a cursor (in which case the display manager is taking forever to load)
[20:30] <jdsfighter> Menzador: I posted my dmesg: https://paste.ubuntu.com/p/qX6kwsCrnN/ I'm not sure what's going on. It's intermittent, but the one constant is that is only happens when I have "splash" in my startup
[20:31] <Menzador> jdsfighter: So Plymouth is the application that controls the splash screen. Lemme look at it
[20:32] <Menzador> ight lines 1211-19 tell me modesetting is an issue. You said you took out 'splash' in GRUB?
[20:33] <Menzador> This might sound silly but you may not be able to use your splash screen - a valid solution, although not too shiny, would be to get rid of 'splash' in /etc/default/grub and regenerate your GRUB configuration file jdsfighter
[20:33] <jdsfighter> Menzador: those logs are with "slash" in grub.
[20:33] <Menzador> Yeah
[20:33] <jdsfighter> Without splash, it works great. I was just hoping for no visible logs
[20:34] <Menzador> You could do 'nomodeset' but that will ignore your configuration and you probably don't want that
[20:34] <jdsfighter> Still happens with `nomodeset`
[20:35] <Menzador> Ah in that case just ditch 'splash' in /etc/default/grub and run `update-grub` to update the config file
[20:35] <Menzador> I'm not expecting much for flashy objects on 40 series cards
[20:35] <jdsfighter> Well, darn. No real solution for now then?
[20:35] <Menzador> Ofc all of this is assuming you're using the NVIDIA driver and not nouveat
[20:35] <Menzador> *nouveau
[20:36] <jdsfighter> Yeah, I *think* it's NVIDIA
[20:36] <Menzador> Check in jockey ("Additional Drivers")
[20:36] <Menzador> just to be sure
[20:38] <jdsfighter> Shows "Using NVIDIA driver metapackage from nvidia-driver-535 (proprietary, tested)"
[20:38]  * Menzador thumbs up
[20:39] <Menzador> OK yeah, so the only solution I can think of is to get rid of the splash screen in your GRUB configuration. I know it's not optimal, but at least you'll have a working system. Sometimes, not using an extra feature is required. See !lnw
[20:40] <Menzador> !lnw
[20:40] <ubottu> Want to know the differences between Windows and Linux? This guide, called "Linux is Not Windows" is a pretty good read -- http://linux.oneandoneis2.org/LNW.htm
=== pah is now known as pa
=== shlom is now known as V1A
[21:11] <Menzador> OK, forget everything I said trying to troubleshooting my own issue - I forgot GNOME had its own configuration and I thought I was using the new Unity 7-based distro
=== NoSQL is now known as SQL