| === ancientz6 is now known as ancientz | ||
| sudobash | how do I remove a BPF prog with bpftool? | 01:41 |
|---|---|---|
| MrHAPPY | rm -Rf /sys/fs/bpf/your_ebpf_program | 01:48 |
| === jgee0372 is now known as jgee037 | ||
| JoelJoel | is there a way to dump the x.org config as it is fully running at a given point in time? | 02:14 |
| === JoelJoel is now known as Joel | ||
| sudobash | MrHAPPY, what about the bpf progs that show with: bpftool prog list | 02:15 |
| sudobash | those seems completely different than what is in /sys/fs/bpf/ | 02:15 |
| sudobash | Those are eBPF maps? | 02:15 |
| sudobash | The state of Linux Security is completely broken | 02:17 |
| === froike166 is now known as froike16 | ||
| === jgee0376 is now known as jgee037 | ||
| NorrinRadd | how do you add another workspace on the default gnome? | 03:29 |
| NorrinRadd | I see no plus sign | 03:29 |
| NorrinRadd | when looking in the activitis view | 03:29 |
| toddc | NorrinRadd: https://help.ubuntu.com/stable/ubuntu-help/shell-workspaces-switch.html.en | 03:30 |
| NorrinRadd | toddc: any way i can find those instructions for Focal? | 03:33 |
| NorrinRadd | my activities view isn't looking like that | 03:33 |
| toddc | NorrinRadd: looking 1 sec | 03:33 |
| toddc | NorrinRadd: that Feature was not includded but can be added see https://askubuntu.com/questions/1236190/how-to-create-workspaces-in-ubuntu-20-04 | 03:37 |
| NorrinRadd | lol | 03:46 |
| NorrinRadd | removed like a 30 year old feature | 03:46 |
| NorrinRadd | toddc: thanks so much! | 03:47 |
| toddc | NorrinRadd: more like time to intergrate features to new window manager | 03:53 |
| NorrinRadd | toddc: taht link worked | 03:58 |
| NorrinRadd | tweaks | 03:58 |
| === drew` is now known as drew | ||
| Guest22 | Good day. I've just installed Ubuntu 24.04. It get a black screen on log in and desktop. TTY switch works (I'm currently chatting in the new desktop). My GPU is 'Nvidia GTX 1660 SUPER' (NVIDIA 565.77 is my current driver, default/preinstall was nvidia-driver-550 (proprietary, tested) which I changed, the problem continues. I'm running on kernel | 09:48 |
| Guest22 | 6.11.0-19. X.Org Nouveau works without a problem. Here is the output from nvidia-smi (https://pastebin.com/d5vdHnHy)& dmesg (https://pastebin.com/gaPbzsAV). | 09:48 |
| Guest24 | =D | 10:47 |
| Guest24 | ddd | 10:47 |
| Guest24 | dd | 10:47 |
| Guest24 | d | 10:47 |
| Guest24 | ddd | 10:47 |
| Guest24 | d | 10:47 |
| h1 | how do I arrange my apps in alphabetical order in stock ubuntu? | 10:48 |
| h1 | in the show apps on 24.04 | 10:49 |
| h1 | second question is how to use a more uptodate version of python in vscode venv on ubuntu ? | 10:50 |
| h1 | currently on 3.12.3 I want to use 3.12.2 | 10:51 |
| h1 | 3.13.2 | 10:51 |
| cbreak_ | h1: 3.12 is very new for ubuntu, 24.04 only has 3.12.3 by default, even 24.10 only has 3.12.7. | 10:55 |
| cbreak_ | you can use some third party source for python though | 10:55 |
| cbreak_ | either a system-wide one like this ppa: https://launchpad.net/~deadsnakes/+archive/ubuntu/ppa | 10:56 |
| cbreak_ | or something venv local, like conda, mamba, micromamba or what ever else the snake people come up with next | 10:56 |
| cbreak_ | maybe this one: https://docs.astral.sh/uv/ | 10:56 |
| * cbreak_ hasn't used those | 10:57 | |
| Yakov | I've tried to set path to my bashrc file with echo 'export SCROLLVIEW_PATH=/home/j/tesseract/java/libs/ScrollView.jar' >> ~/.bashrc | 10:59 |
| Yakov | and now I recieve these kind of output for any system call I make | https://justpaste.it/9vqrb | 10:59 |
| h1 | cbreak_: thanks | 11:00 |
| Yakov | @cbreak_ could you please give any pointers how to repair it? | 11:02 |
| cbreak_ | (my coworkers at work switch all the time, from conda to mamba to micromamba and now they're recommending uv sometimes... ah well...) | 11:02 |
| cbreak_ | Yakov: don't know... how about deleting that line from .bashrc again? | 11:02 |
| Yakov | cbreak_, I already did it :) | 11:03 |
| cbreak_ | looks like you deleted PATH too though | 11:03 |
| tomreyn | Yakov: please use a pastebin which supports a monospaced font in the future | 11:03 |
| cbreak_ | Yakov: you could just mv .bashrc .bashrc.old | 11:04 |
| tomreyn | for command output that's a lot more readable | 11:04 |
| cbreak_ | and then cp /etc/skel/.bashrc ~/ | 11:04 |
| Guest22 | I've a fresh install of Ubuntu 24.04. It get a black screen on log in and desktop, TTY switch gets me through it. My GPU is 'Nvidia GTX 1660 SUPER' (NVIDIA 565.77 is my current driver, default/preinstall was nvidia-driver-550 (proprietary, tested) which I changed, the problem continues. I'm running on kernel 6.11.0-19. X.Org Nouveau works without a | 11:04 |
| Guest22 | problem. Here is the output from nvidia-smi (https://pastebin.com/d5vdHnHy) & dmesg (https://pastebin.com/gaPbzsAV). Can someone advise what's likely the problem? | 11:04 |
| tomreyn | Yakov: you seem to have set PATH incorrectly. can you show what you did? | 11:04 |
| Yakov | I already reverted to previous bashrc state | 11:06 |
| Yakov | but after I could not call source ~/.bashrc as I get same errors | 11:06 |
| tomreyn | have you tried to logout and login again? | 11:07 |
| Yakov | I'm scared, really :D | 11:07 |
| Yakov | should I? | 11:07 |
| cbreak_ | or just exec /usr/bin/bash | 11:07 |
| cbreak_ | Yakov: even if your bashrc is broken, you could try to start an other shell with absolute path and fix it from there :) | 11:08 |
| Yakov | its says Command lesspipe is available in the following places | 11:08 |
| tomreyn | if you had only modified ~/.bashrc and this introduced the issue, and you have since reverted ~/.bashrc to the previous state, then logout + login will revert the situation to the previous state. | 11:08 |
| h1 | how do I arrange my apps in alphabetical order in stock ubuntu? | 11:09 |
| cbreak_ | Yakov: it could be that you also clobbered something by editing ~/.profile or some other bash related file | 11:09 |
| Yakov | What should I do now? I dont want to reinstall OS :J | 11:09 |
| Yakov | is logout safe? | 11:10 |
| cbreak_ | you can copy templates for all these files from /etc/skel | 11:10 |
| cbreak_ | you could also create a fresh user to play around with, new users get their own copy of all these files | 11:10 |
| cbreak_ | and for your current shell, you could just export PATH=/usr/bin:/usr/local/bin:$PATH | 11:10 |
| tomreyn | Guest22: can you revert to the *ubuntu packaged* nvidia-driver-550 (proprietary, tested) and switch to a tty and run sudo journalctl -kp4 | nc termbin.com 9999 and share the url it returns here? | 11:11 |
| tomreyn | Guest22: this would post any kernel warnings (or worse, like errors) to termbin.com, a pastebin-like site. | 11:12 |
| Guest22 | tomreyn: Okay, I'll try now | 11:13 |
| Yakov | Thanks! It works | 11:14 |
| Guest22 | tomreyn - https://termbin.com/lm0wx | 11:22 |
| tomreyn | Guest22: oh, let me check | 11:32 |
| tech-pc | Hello guys | 11:35 |
| tech-pc | How are you ? | 11:35 |
| spinningCat | same old same old | 11:35 |
| tomreyn | Guest22: you have some ACPI errors there. i assume these are unrelated ("SAT0" should refer to the SATA bus), but it can hint at an outdated bios, which may have other issues, so a bios upgrade *can* be useful. | 11:35 |
| tomreyn | Guest22: "nvidia-gpu 0000:01:00.3: i2c timeout error e0000000" is the first graphics related error message. | 11:36 |
| tomreyn | Guest22: i'm pointing this out because searching the web for the first specific error message can often help find related bug reports and potentially workarunds. | 11:36 |
| tomreyn | Guest22: did you boot with failsafe graphics or "nomodeset" by chance? i'm asking because the nvidia driver reports that it "failed to grab modeset ownership" (which refer to kernel/user initiated graphics mode setting, only one can work at a time, and the common approach is kernel modesetting nowadays). | 11:39 |
| Guest22 | tomreyn: Sure thing. Problem is I don't understand much of it. I'm okay with running new installs, but the minute problems like this appear, I'm kinda useless. I'm that kind of person who'd rather reinstall, if I can't solve the graphic card issues. I did try and messed up the system somehow. | 11:40 |
| Guest22 | tomreyn: I did, but not with this fresh install. Its right out of the live USB, this system. | 11:40 |
| tomreyn | Guest22: so are you saying that graphics did work fine after initial installation but they stopped working after you applied changes? | 11:41 |
| Guest22 | tomreyn: No. Right from the initial installation I was getting the black screen on log in. After installation and removing the usb, the first boot did it and on both installs | 11:42 |
| tomreyn | i see, that's good to know. and not a great "experience". :-/ | 11:43 |
| tomreyn | so, when you gathered the log for me, you just booted normally, did not make any selections on a menu during boot, right? | 11:43 |
| tomreyn | and then you ran into the black screen, and switched to y TTY by pressing ctrl-alt-Fsomething? | 11:44 |
| tomreyn | * to *a* TTY | 11:44 |
| Guest22 | tomreyn: Especially when one isn't adept at this kind of thing. Can be frustrating not knowing enough. | 11:46 |
| Guest22 | Straight boot, no tinkering. Then the log in screen, I entered details, it loaded into a black desktop. Ctrl+Alt+F2 then Ctrl+Alt+F1 and the desktop appeared. | 11:46 |
| Guest22 | Let me post more output from the fresher install. | 11:47 |
| tomreyn | oh, so you have the graphical login which works fine, then login and get a black screen, then switch to a textual tty and back to the graphical screen and it starts working. | 11:48 |
| Guest22 | Yes | 11:49 |
| jack8 | hello | 11:49 |
| gry | hi | 11:49 |
| jack8 | If I install Ubuntu with two separate partitions, home and root / . How many gigabytes do you recommend for the / partition? Is 50 gigabytes enough or rather 80 gigabytes? | 11:51 |
| lotuspsychje | !partitioning | jack8 | 11:52 |
| ubottu | jack8: For help with partitioning a new install see https://help.ubuntu.com/community/HowtoPartition | For partitioning programs, see Gnome Disks, !GParted or !PartitionManager. Other partitioning topics include !fstab, !home, and !swap | 11:52 |
| Guest22 | tomreyn: These are the outputs I ran after a fresh install - https://pastebin.com/56yU1y0T | 11:53 |
| tomreyn | Guest22: sorry, i didn't seem to understand this situation from reading your initial description. i can see how that's a frustrating situation, yes. it doesn't help you now, but for the future, it may help you to know that you usually don't run into such issues when you buy hardware which is supported by the linux kernel itself (i.e. not nvidia (if we ignore the open source but feature limited "nouveau" driver)) | 11:54 |
| jack8 | lotuspsychje :I think I know how to partition, that's not the problem. I want to know what would be the best space for a partition/separate, is 50 GB enough or much more | 11:56 |
| tomreyn | Guest22: okay, those look similar to what i had you share | 11:58 |
| tomreyn | Guest22: i'm trying to find a previous report of this specific situation, but am not having much luck, yet | 11:58 |
| BluesKaj | Hi all | 11:59 |
| Guest22 | tomreyn: Funny thing is, all worked well for a good 4 years on 22.04. Hardly an issue, in my wisdom I decided it would be great to do a full reinstall to 24.04. Then the fun started "nouveau" driver doesn't have the black screen issue, its only Nvidia. I think I fixed it on the first install. But there was a big issue after a few reboots which sent | 11:59 |
| Guest22 | my system into emergency mode. Let me check for the 'fix". | 11:59 |
| tomreyn | Guest22: i'm rading the 24.04 releas enotes, which state that the "TPM-backed full-disk encryption (FDE)" option the 24.04 installer offers is incompatible with external drivers, such as nvidia. so i'm wondering whether you chose this disk encryption option during installation? | 12:01 |
| tomreyn | https://discourse.ubuntu.com/t/ubuntu-24-04-lts-noble-numbat-release-notes/39890 | 12:01 |
| tomreyn | reading, not rading ;) | 12:02 |
| Guest22 | tomreyn: No I didn't choose the disk encryption option. | 12:03 |
| tomreyn | okay, i assume this would have prevented the driver from loading in the first place | 12:03 |
| tomreyn | i also assume the issue you faced with 22.04 LTS may be unrelated. but it can still be worth looking it up if you have notes on how you fixed it. | 12:04 |
| lotuspsychje | jack8: the users choice really, i think ubuntu needs an 8GB+ to make an installation these days | 12:06 |
| Guest22 | tomreyn: I didn't have any issue with 22.04. Likely graphic in the beginning but was fine once i got the driver installed. I used something like this on my first 24.04 issue which fixed the black screen, can't remember it all: sudo nvidia-xconfig - "WARNING: Unable to locate/open X configuration file.New X configuration file written to | 12:08 |
| Guest22 | '/etc/X11/xorg.conf'" | 12:08 |
| Guest22 | Don't know what I did after but it worked | 12:08 |
| tomreyn | Guest22: oh this was on 24.04, too, not 22.04, sorry. | 12:08 |
| tomreyn | i don't think you should run nvidia-xconfig as root, but i could be wrong (don't have much experience with nvidia myself) | 12:10 |
| tomreyn | normally, the X configuration is generated dynamically, and, where configuration is needed, should be done on a per user level, not system wide. | 12:11 |
| tomreyn | Guest22: you could try this: echo "blacklist i2c_nvidia_gpu" | sudo tee /etc/modprobe.d/blacklist_i2c-nvidia-gpu.conf >/dev/null && sudo update-initramfs -u | 12:11 |
| tomreyn | then reboot | 12:11 |
| tomreyn | to undo this later, you would: sudo rm /etc/modprobe.d/blacklist_i2c-nvidia-gpu.conf && sudo update-initramfs -u then reboot. | 12:12 |
| Guest12 | tomreyn: Woops, sorry I'm back incase I missed something. Yes, 22.04 LTS was all fine. Everything I've been discussing is as a result of 24.04 LTS. | 12:14 |
| tomreyn | Guest12: this was the latest chat https://bpa.st/HBRA | 12:15 |
| tomreyn | by the way, you can change your nickname to something less generic by typing this here: /nick someothernick | 12:16 |
| tomreyn | Guest12: also, did you install any pending software updates, yet? | 12:20 |
| tomreyn | sudo apt update && sudo apt full-upgrade | 12:20 |
| tomreyn | (and reboot) | 12:20 |
| Guest12 | tomreyn: Okay so what will that command do? - Yes I ran that upon entering the new install. I figured it would solve my issues :( | 12:21 |
| tomreyn | oh, good to know that. | 12:21 |
| tomreyn | what this command does is to prevent the "i2c_nvidia_gpu" driver from loading | 12:22 |
| Guest12 | I hate that it didn't work. | 12:23 |
| Guest12 | tomreyn: So I'll run that command and see what it does? | 12:23 |
| tomreyn | this is a driver which can provide some additional functionality though the nvidia hardwares' I2C bus, but which seems ot be causing issues in your situation | 12:23 |
| tomreyn | if you have not run it yet? i just understaood that you said "Yes I ran that upon entering the new install", so you would already have run this command? | 12:24 |
| tomreyn | if so, running it again won't do any good | 12:24 |
| tomreyn | or maybe you were referring to the "sudo apt update && sudo apt full-upgrade" commands? | 12:24 |
| Guest12 | tomreyn: Apologies, let me clarify. I ran "sudo apt update && sudo apt full-upgrade" after the fresh install. I was asking about trying "echo "blacklist i2c_nvidia_gpu" | sudo tee /etc/modprobe.d/blacklist_i2c-nvidia-gpu.conf >/dev/null && sudo update-initramfs -u"? | 12:25 |
| tomreyn | Guest12: i do recommend that you run this, if you have not done so, yet: echo "blacklist i2c_nvidia_gpu" | sudo tee /etc/modprobe.d/blacklist_i2c-nvidia-gpu.conf >/dev/null && sudo update-initramfs -u | 12:26 |
| tomreyn | thanks for clarifying. | 12:27 |
| tomreyn | before you reboot, can you share the one-line output of cat /prod/cmdline here? | 12:27 |
| Guest12 | tomreyn: Okay done. Out put is "cat: /prod/cmdline: No such file or directory" | 12:29 |
| tomreyn | Guest12: sorry, i fat fingered this. can you run this, please: | 12:29 |
| tomreyn | cat /proc/cmdline | 12:30 |
| Guest12 | Thank goodness its not me :D | 12:30 |
| Guest12 | BOOT_IMAGE=/boot/vmlinuz-6.11.0-19-generic root=UUID=134821a6-94ae-485d-9338-8f957406fcdd ro quiet splash vt.handoff=7 | 12:30 |
| tomreyn | thanks | 12:31 |
| tomreyn | feel free to reboot | 12:31 |
| tomreyn | and you're welcome to pick a different nickname when you return | 12:31 |
| tomreyn | (tab completion is difficult on Guest...) | 12:31 |
| Guest12 | Alright. Be right back. I'll take 'Bluewolf" with 123 after if its taken :) | 12:32 |
| tomreyn | thanks | 12:32 |
| tomreyn | welcome back, Bluewolf | 12:35 |
| Bluewolf | :) | 12:36 |
| Bluewolf | Still had to TTF switch | 12:36 |
| tomreyn | :-/ | 12:36 |
| tomreyn | would you mind giving a bios upgrade a try? | 12:37 |
| Bluewolf | I sure could, not quite sure how to go about it. Was told in the past not to play around with bios upgrades | 12:37 |
| Bluewolf | Think that could solve this issue? Not something like a miss match between Nvidia and Kernel? | 12:38 |
| tomreyn | there's always a chance that bios upgrades fix issues which the OS can or cannot detect or work around. but it's a bit of a wild guess. | 12:40 |
| tomreyn | to me, it's not something unusual to do, but sure, there's always a (very little) bit of risk involved | 12:41 |
| lotuspsychje | Bluewolf: apt spits out errors? | 12:42 |
| tomreyn | Bluewolf: something else you could try is to choose a different graphics server on login. that is, on the screen you enter or select your username, click on the gear wheel and select one of the options available there which you have not tried so far. | 12:43 |
| Bluewolf | lotuspsychje: Any specific command, I can copy and paste? | 12:43 |
| lotuspsychje | Bluewolf: sudo apt update && sudo apt full-upgrade | 12:44 |
| Bluewolf | tomreyn: I think I tried 'Gnome' from 'Ubuntu' but it didn't switch | 12:44 |
| tomreyn | lotuspsychje: this is not to discourage you, just making sure you didn't miss this info: it's a fresh 24.04 installation, the issue existed since first boot (from installed system), also after installing pending updates. the issue is that the screen goes black after (grahpical) login and is worked abround by switching to a tty and back again. | 12:46 |
| lotuspsychje | recoverymode? | 12:46 |
| tomreyn | that'd cause nomodeset and thus nouveau, i think? that's probably less desirable than siwtching to tty andd back again and use nvidia | 12:47 |
| Bluewolf | lotuspsychje: First thing I ran. All was butterflies and rainbows after that. Then the issue struck :) | 12:47 |
| lotuspsychje | Bluewolf: logging into xorg or wayland? | 12:48 |
| tomreyn | <Bluewolf> tomreyn: I think I tried 'Gnome' from 'Ubuntu' but it didn't switch | 12:49 |
| Bluewolf | lotuspsychje: At one point I disabled wayland. Didn't make a difference | 12:49 |
| tomreyn | Bluewolf: if you like you could post a full kernel log, maybe i can spot something relevant which wasn't included in the first log i had you post | 12:50 |
| tomreyn | Bluewolf: so that'd be journalctl -k | nc termbin.com 9999 | 12:50 |
| Bluewolf | tomreyn: Secrets out now xD - https://termbin.com/0ig0 | 12:51 |
| tomreyn | or even include userspace processes, but then the log may well get too long (but can still be useful): journalctl -b | nc termbin.com 9999 | 12:51 |
| tomreyn | yay, reading | 12:52 |
| tomreyn | this is a Gigabyte B365M DS3H, BIOS F5 08/13/2019 | 12:52 |
| Bluewolf | tomreyn: That would be correct. I've no shame in not having updated it. I should, but as I mentioned about playing around in things I'm not familiar with :D | 12:57 |
| tomreyn | sadly nothing else is new on the log | 12:58 |
| tomreyn | let's see how difficult it is dto do the bios upgrade | 12:58 |
| Bluewolf | tomreyn: Oh, speaking of. Sorry - https://termbin.com/60qh | 12:59 |
| tomreyn | https://www.gigabyte.com/Motherboard/B365M-DS3H-rev-10/support#support-dl-bios lists the available bios versions and version / installation notes | 13:00 |
| tomreyn | F7 is the newest version, so 2 later than what you have now | 13:01 |
| tomreyn | the bios update is provided as a DOS executable. i assume you could also just load it from the bios-embedded self-updater, though | 13:03 |
| Bluewolf | lotuspsychje: "sudo nano /etc/gdm3/custom.conf" is what I ran to uncomment "WaylandEnable=false". FYI | 13:03 |
| Bluewolf | tomreyn: You reckon this could be a better likelihood over Nvidia conflict with kernel or say GDM or GNOME Session Initialization? | 13:04 |
| Bluewolf | Just curious | 13:05 |
| tomreyn | i.e. unzip the B365MDSH.F7 file, place this on a FAT formatted file system such as /boot/efi/ or a usb stick (where the first partition is a FAT file system), then boot to bios setup screen and sleect the option to update the bios from a disk/usb | 13:05 |
| tomreyn | Bluewolf: i'd say there is a somewhat small chance that the bios update would fix this issue. | 13:06 |
| tomreyn | however, you may havenoticed "Major vulnerabilities updates, customers are strongly encouraged to update to this release at the earliest." | 13:07 |
| Bluewolf | Yes I saw | 13:07 |
| tomreyn | (there is a chance that this is also mitigated in software/by linux, potentially with a performance impact) | 13:09 |
| tomreyn | thanks for the other log, i have not read this one, yet | 13:10 |
| Bluewolf | tomreyn: You mentioned my bios was F5. Can I upgrade directly from that to F7 or must I Update to F6 then F7? | 13:12 |
| Bluewolf | Got my USB with the BIOS updated ready. Will give it a go if you haven't found anything else on that other log? | 13:19 |
| tomreyn | Bluewolf: i would expect that you can upgrade directly from bios F5 to F7, since the notes on the bios download page do not indicate otherwise (they usually would if you could not). | 13:21 |
| tomreyn | Bluewolf: i have just found this line on https://termbin.com/60qh : xf86EnableIO: failed to enable I/O ports 0000-03ff (Operation not permitted) | 13:22 |
| tomreyn | this is followed by two X errors. but this is during gdm initialization and your (visible) issue occurs after that. | 13:23 |
| Bluewolf | Okay. I've just confirmed the F5 to F7 while reading, thanks. Now about the 'failed to enable'? (Sorry about code trawling) | 13:24 |
| Bluewolf | tomreyn: What are you thinking now? | 13:24 |
| tomreyn | i'm still reading. this error re-occurs during initialuzation of the graphical desktop session | 13:28 |
| tomreyn | so gnome-shell/mutter | 13:28 |
| tomreyn | i don't know (yet) whether it is relevant or benign | 13:28 |
| tomreyn | (EE) NVIDIA(GPU-1): Failed to initialize the NVIDIA graphics device! | 13:29 |
| tomreyn | and "(EE) NVIDIA(G0): Failing initialization of X screen" sound critical | 13:30 |
| tomreyn | so the issue seems to be related to the nvidia driver itself somehow. but i cannot really tell more | 13:33 |
| tomreyn | it seems that the nouveau Xorg driver is also loading, which i think, if nvidia is, it shouldn't be. i think you'd usually have nouveau blacklisted by the nvidia driver, so that it is not loaded. | 13:35 |
| Bluewolf | If this is a brand new install, it shouldn't have this conflict? | 13:39 |
| lotuspsychje | maybe a 6.11 glitch | 13:40 |
| tomreyn | no, it shouldn't. but it's not (at least no longer when the log was produced) a brand new install, you already installed third party software | 13:40 |
| Bluewolf | Yes I installed third party software with the install or is it best I redo a clean installation and exclude it? | 13:42 |
| tomreyn | (i do understand that you reported that this issue occurred during the first boot) | 13:42 |
| Bluewolf | Yes | 13:42 |
| Bluewolf | Correct | 13:42 |
| tomreyn | i'm afraid i think i did all i could, you'd need to have someone with a better understanding of the graphics stack and nvidia drivers look into this | 13:43 |
| tomreyn | you could file a bug report about this | 13:43 |
| tomreyn | !bug | 13:43 |
| ubottu | If you find a bug in Ubuntu or any of its official !flavors, please report it using the command « ubuntu-bug <package> » - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs. | 13:43 |
| tomreyn | if this issue occurred both during the first boot, as well as both [ before you installed third party software and after installing any pending ubuntu updates and rebooting ] then this is a bug in ubuntu | 13:45 |
| tomreyn | (otherwise it can or cannot be) | 13:45 |
| tomreyn | if this issue is known to occur on a fresh install of the latest 24.04 version, i'd expect this to be documented in the release notes (but it is not). | 13:47 |
| tomreyn | Bluewolf: within the above constraints, i don't see how a fresh install would do any good. | 13:48 |
| tomreyn | not of the very same 24.04 release anyways | 13:48 |
| Bluewolf | tomreyn: So, to confirm. You strongly think this is Nvidia related rather than anything else? | 13:49 |
| tomreyn | yes | 13:49 |
| Bluewolf | This install I've been using isn't 'the latest' | 13:49 |
| tomreyn | "nvidia" proprietary driver related specifically | 13:49 |
| Bluewolf | I've been sitting with it under my pillow for a while. What about downloading a 'new' .iso? | 13:50 |
| tomreyn | it could be worth a try. | 13:50 |
| tomreyn | that's if this is a newer micro version than the one you used | 13:50 |
| Bluewolf | Well, I downloaded this .iso last year. So... | 13:51 |
| tomreyn | on the other hand, just purging nvidia* and then installing nvidia-driver-550 *should* do the same | 13:52 |
| tomreyn | ubuntu-24.04.2-desktop-amd64.iso was released on 2025-02-15 | 13:53 |
| Bluewolf | I did do purge nvidia a couple times :) | 13:53 |
| tomreyn | i see. i'm afraid i have no other suggestions at this point. | 13:54 |
| Bluewolf | Yeah so might be an idea to use that. I would have thought that a simple 'update' after install would solve that kind of issue | 13:54 |
| tomreyn | it would not | 13:54 |
| tomreyn | not "apt update" anyways | 13:54 |
| tomreyn | but "apt update && apt full-upgrade" should | 13:55 |
| Bluewolf | That's what I'm saying. Least, that was my understanding that 'apt update && sudo apt full-upgrade' should do the same thing than having to get a new .iso. Unless there is something more complicated that I'm missing, I'm no software engineer after all? :P | 13:57 |
| tomreyn | however, configuration files which were not part of an older package version may not have been installed by the new package version (which may have included them) if a package upgrade was carried out rather than a package purge and install (or it was requested that configuration files would be 'replaced') | 13:57 |
| Bluewolf | So then perhaps its worth a shot. When ones desperate, one will try anything. Like peeling potatoes with Scissors :D | 13:59 |
| tomreyn | put simply: apt full-upgrade with an existing nvidia-driver-... package may give different results than apt purge nvidia* followed by apt install nvidia-driver-... | 13:59 |
| Bluewolf | Its worth a shot. I got a new install. Tanked the last. No biggie if I ruin this. So just to confirm, 'sudo apt full-upgrade' ? | 14:04 |
| lotuspsychje | Bluewolf: your dmesg is full of weird errors | 14:31 |
| Bluewolf | lotuspsychje: That it is my friend and I don't know why. I was very much considering reinstalling and not touching a think to run some outputs | 14:32 |
| lotuspsychje | but this was a fresh install? | 14:33 |
| Bluewolf | lotuspsychje: Well yes. Then I removed 550 nvidia drivers and put 565 on then changed the PPA because 565 wasn't available. | 14:35 |
| Bluewolf | I don't know if I've changed too much already and caused other problems | 14:36 |
| lotuspsychje | thats weird, as nvidia graphics ppa and ubuntu repos should be pretty synced these days | 14:36 |
| lotuspsychje | i wonder why your dmesg spits out so much gnome-shell warnings on a clean install | 14:36 |
| Bluewolf | I'm confused myself. The problem is also as I mentioned. I don't understand enough to explain problems or probably identify them. | 14:38 |
| lotuspsychje | Bluewolf: so you installed fresh and then after the reboot got into a black screen? | 14:41 |
| lotuspsychje | Bluewolf: or did you enter your desktop and start installing all sorts at one point? | 14:42 |
| geomanss | hi | 14:43 |
| Bluewolf | lotuspsychje: Directly after installing. "remove usb & press enter to reboot". That very boot up, screen resolution of the ubuntu symbol changed from bloated and stretched to 'normal' (To fit my screen). Then the login screen appeared. Then I entered in details. Screen went black. TTF switches and the desktop appeared and the system notification | 14:47 |
| Bluewolf | greeted me 'Preparing for first use' | 14:47 |
| lotuspsychje | Bluewolf: i see nordvpn errors in your dmesg, at wich point did you add those? | 14:47 |
| Bluewolf | After the software updates | 14:48 |
| lotuspsychje | what else did you install when you could Bluewolf | 14:49 |
| Bluewolf | lotuspsychje: Just the updates, then the VPN. Then I messed around with the different Nvidia drivers | 14:50 |
| lotuspsychje | gnome-shell[2536]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1800004 | 14:51 |
| lotuspsychje | a lot of weird errors we shouldnt suspect on a fresh install or just nvidia issues | 14:51 |
| Bluewolf | I don't know either. | 14:52 |
| lotuspsychje | Bluewolf: what i would do is try fixing stuff from recoverymode | 14:54 |
| lotuspsychje | enable networking from there and fallback to a rootshell | 14:55 |
| lotuspsychje | and update system and debug | 14:55 |
| Bluewolf | lotuspsychje: I don't know enough to do that on my own. I'm sure no one is prepared to talk me through it all and I don't expect them to, its quite time consuming, not to mention frustrating for me but more so for the poor soul who offers help. | 14:58 |
| === EoflaOE- is now known as EoflaOE | ||
| lotuspsychje | Bluewolf: entering recoverymode is not so hard, hold shift at boot to enter grub, then pick ubuntu (recovery) from your list | 14:59 |
| Bluewolf | I know enough to 'get by'. I'm alas limited. Best I can do is make changes while speaking with someone :( | 14:59 |
| lotuspsychje | Bluewolf: https://static1.xdaimages.com/wordpress/wp-content/uploads/wm/2023/12/up5j7-1-1-1.png | 15:00 |
| lotuspsychje | Bluewolf: https://www.maketecheasier.com/assets/uploads/2019/03/ubuntu-recovery-root.jpg | 15:00 |
| Bluewolf | lotuspsychje: Okay. I follow. Update system and debug after? | 15:02 |
| lotuspsychje | Bluewolf: sudo apt update && sudo apt full-upgrade to start with | 15:03 |
| lotuspsychje | Bluewolf: dont forget to enable networking and drop to a rootshell in recoverymode | 15:03 |
| lotuspsychje | Bluewolf: once we know for sure your system is up to date and apt doesnt spit out errors, volunteers can help you on the next step | 15:04 |
| Bluewolf | lotuspsychje: Okay. I'll try now. Will update you when I'm back :y: | 15:05 |
| tomreyn | lotuspsychje: just to make sure this was mentioned: Bluewolf reported that they installed using a 24.04 iso before of a previous point release. their graphics work fine, using the default nvidia-550 driver (which should be compatible to this graphics card according to nvidia.com - not "legacy"), with the exception that the screen goes dark after loggin into gnome-shell, but recovers after switching to a different tty and back again. | 15:09 |
| tomreyn | so it's not a total failure, the driver works generally. and these symptoms were the same on first boot (post install) before any third party software was installed. | 15:10 |
| lotuspsychje | tomreyn: tnx, what worrys me is the huge ammount of dmesg errors of different corners on a fresh setup | 15:10 |
| tomreyn | i didn't spot *that* many really | 15:10 |
| lotuspsychje | acpi issues, gdm issues, nvidia issues, gnome-shell, nordvpn,.. | 15:10 |
| tomreyn | i think nordvpn messages weren't in dmesg, just in the journal (incl. user space) | 15:11 |
| lotuspsychje | ah | 15:11 |
| tomreyn | same for gnome-shell, both should be user space | 15:12 |
| tomreyn | gdm too | 15:12 |
| tomreyn | the acpi warnings are about sata if i interpreted those correctly | 15:12 |
| tomreyn | _SB.PCI0.SAT0.PRT* | 15:13 |
| lotuspsychje | tomreyn: found a bug about the advice you gave earlier too, bug #2016924 | 15:13 |
| -ubottu:#ubuntu- Bug 2016924 in linux-nvidia (Ubuntu) "nvidia_drm Failed to grab modeset ownership" [Undecided, Fix Released] https://launchpad.net/bugs/2016924 | 15:13 | |
| emi_engineer | hi | 15:14 |
| lotuspsychje | welcome emi_engineer | 15:14 |
| lotuspsychje | wb Bluewolf | 15:14 |
| tomreyn | lotuspsychje: i spotted this bug report, too. it's about 22.04 (not 24.04, but who knows...), but i had them try this and it didn't fix the screen blanking issue | 15:15 |
| emi_engineer | thak you lotuspsychje | 15:15 |
| emi_engineer | i'm rookie | 15:15 |
| lotuspsychje | tomreyn: did we see a clean dmesg from Bluewolf ? | 15:15 |
| tomreyn | lotuspsychje: "clean" as in? | 15:16 |
| lotuspsychje | as not in not journal :p | 15:16 |
| tomreyn | oh, no, i only asked for journalctl with and without -k | 15:16 |
| tomreyn | https://termbin.com/0ig0 was journalctl -k | 15:17 |
| Bluewolf | lotuspsychje: Ty. Done. The black screen still appears. However its worth noting, I disabled the login screen (From the settings) and it started up into the desktop without a problem. I enabled the password and the black screen returned. | 15:18 |
| Bluewolf | tomreyn: https://pastebin.com/EWywMaWx | 15:18 |
| tomreyn | Bluewolf: what's this? | 15:19 |
| lotuspsychje | Bluewolf: can you also pastebin a full; sudo dmesg | 15:19 |
| lotuspsychje | Bluewolf: was system up to date? | 15:21 |
| tomreyn | lotuspsychje: i assume you may need to explain how to share dmesg output (without less paging issues, cut off lines), i did not explain this other than providing commands which pipe into termbin | 15:21 |
| Bluewolf | tomreyn: journalctl output? =# | 15:23 |
| Bluewolf | lotuspsychje: It said so? sudo dmesg | tail -n 50 ? | 15:23 |
| tomreyn | Bluewolf: thanks. (i don't think i suggested to share it, though?) | 15:24 |
| lotuspsychje | Bluewolf: sudo dmesg | nc termbin.com 9999 | 15:25 |
| Bluewolf | tomreyn: Sorry. I got ahead of myself :( | 15:25 |
| tomreyn | ;-) no worries | 15:25 |
| Bluewolf | lotuspsychje: https://termbin.com/bpyj | 15:26 |
| lotuspsychje | ok tnx that looks a bit better | 15:28 |
| lotuspsychje | still the acpi errors and nvidia errors | 15:28 |
| lotuspsychje | Bluewolf: what gives ubuntu-drivers list | 15:30 |
| Bluewolf | lotuspsychje: https://pastebin.com/48axPw0e | 15:34 |
| tomreyn | Bluewolf: i just realize that you may have a different nvidia-driver-550 version installed (possibly from a PPA?). your dmesg reports "NVIDIA UNIX x86_64 Kernel Module 550.144.03 Mon Dec 30 17:44:08 UTC 2024" whereas ubuntu 24.04's nvidia-driver-550 seems to provide version 550.120 according to https://packages.ubuntu.com/noble/nvidia-driver-550 | 15:36 |
| tomreyn | you could run apt policy nvidia-driver-550 | nc termbin.com 9999 to clarify this | 15:36 |
| lotuspsychje | yeah that could fix some stuff, try to switch drivers | 15:37 |
| lotuspsychje | (and make sure its booting into xorg) | 15:37 |
| Bluewolf | tomreyn: Yes its a possibility. Cause the defauk 550 I removed then later put them back but wasn't the same. https://termbin.com/7wgl | 15:38 |
| Bluewolf | lotuspsychje: I don't know how to check that? | 15:38 |
| lotuspsychje | Bluewolf: maybe try a lower nvidia driver as a test, 545 for example | 15:38 |
| lotuspsychje | Bluewolf: xorg vs wayland can be chosen at login/gdm stage | 15:39 |
| tomreyn | Bluewolf: right, so you're using the version from the graphics-drivers PPA. you can disable or remove the PPA (using, e.g., the "software-properties-gtk" application, then downgrade nvidia-drivers-550 to version 550.120-0ubuntu0.24.04.1 using sudo apt install -t noble-updates nvidia-driver-550 | 15:41 |
| Bluewolf | lotuspsychje: On my previous install I tried the 535 driver (I understood it was most stable?). Oh sorry, it is booting into Xorg. Wayland is set to false. | 15:44 |
| tomreyn | so the WaylandEnable setting you changed in the gdm configuration - this applies only to gdm, which is just the graphical login. | 15:45 |
| tomreyn | it does not apply to the graphical session you get after loggin in | 15:45 |
| tomreyn | (i.e. you may have the gaphical login run on wayland, then the actual desktop on Xorg, or the other way around, or something else) | 15:46 |
| Bluewolf | tomreyn: Okay. This would need to be clarified, I can't confirm. | 15:47 |
| Bluewolf | tomreyn: The PPA you were referring to is in the system GUI where it can be removed there. Am I running this? sudo apt install -t noble-updates nvidia-driver-550 | 15:48 |
| Guest81 | Good evening from GMT4 | 15:49 |
| Guest81 | It is my first time on this channel | 15:49 |
| === Guest81 is now known as yougottabeit | ||
| Bluewolf | tomreyn: I updated the PPA somewhere along the lines, the default 550 that comes with the new install isn't in the "Additional Drivers" section, the GUI. There are a whole bunch more thought it doesn't state the exact versions of each other than "550" or "570" | 15:50 |
| tomreyn | Bluewolf: yes, you can remove the ppa from the system GUI. and yes, you can then run sudo apt install -t noble-updates nvidia-driver-550 which should trigger a downgrade of the nvidia driver package to the version ubuntu 24.04 provides. | 15:52 |
| tomreyn | Welcome to ubuntu support, yougottabeit ! | 15:53 |
| yougottabeit | oh, so this is a support channel? | 15:53 |
| yougottabeit | As in asking for tips about your ubuntu setup? | 15:53 |
| tomreyn | Bluewolf: the GUI you are referring to in your second message is for switching between different series of the nvidia driver (those three digit ones), not for switching between the PPA and ubuntu's default version of the 550 series driver. | 15:54 |
| tomreyn | Bluewolf: i'm trying to get you to do the latter | 15:54 |
| tomreyn | yougottabeit: yes, please see the /topic for details. | 15:54 |
| yougottabeit | Good to know, thank you! | 15:55 |
| Bluewolf | tomreyn: Just making sure, its this one with a tick next to it?: https://ppalaunchpadcontent.net/graphics-drivers/ppa/ubuntu/noble main | 15:55 |
| Bluewolf | In "Software & Updates" app | 15:55 |
| yougottabeit | I have a useful discovery regarding a certain HP laptop product's fan boost feature, should I share it here so devs could implement it in the next product? | 15:56 |
| yougottabeit | Or should I push the solution we(me and a guy from peru) have found somewhere else? | 15:56 |
| tomreyn | Bluewolf: that's the one you should disable, correct | 15:56 |
| cbreak | HP? People still deal with those? :/ | 15:57 |
| yougottabeit | cbreak HP Victus to be exact, yes. That's what I'm currently using. | 15:57 |
| tomreyn | yougottabeit: in this case it's best to do a blog post or file a bug report on it, that's the best way people will find out about it | 15:57 |
| tomreyn | yougottabeit: maybe https://community.ubuntu.com would also work if you're looking for a suitable location | 15:58 |
| yougottabeit | tomreyn people have been using it through the reddit threads I have shared the codebase, it seems all Debian based distros are able to use that script. | 15:58 |
| yougottabeit | thanks for the advice! | 15:59 |
| tomreyn | this channel is more useful for discussing specific issues which aren't working for someone who is looking for a fix for them (you seem to have already found a fix for something) | 15:59 |
| tomreyn | you're welcome | 16:00 |
| Bluewolf | tomreyn: This is the output after removing that PPA, I'm wondering if a restart is needed?: https://pastebin.com/jMdpxPNX | 16:00 |
| yougottabeit | tomreyn I do have an issue about bluetooth but I believe that is a painful topic for many. | 16:00 |
| tomreyn | Bluewolf: sorry, probably my fault again. can you run sudo apt update then repeat sudo apt install -t noble-updates nvidia-driver-550 | 16:01 |
| Bluewolf | tomreyn: Not at all. It has the same output | 16:02 |
| tomreyn | how about: sudo apt install nvidia-driver-550/noble-updates ? | 16:02 |
| Bluewolf | tomreyn: Oh, that's working | 16:03 |
| tomreyn | see, my fault :) | 16:03 |
| Bluewolf | tomreyn: I don't know enough to contest that :P | 16:03 |
| tomreyn | hehe | 16:03 |
| tomreyn | unfortunately, for all we know, the original noble version you're now again installing will trigger the same issue, too. | 16:05 |
| === tom is now known as shartcrisis | ||
| tomreyn | (since you must have had this originally) | 16:05 |
| tomreyn | it's still better to work with the default version, at least while trying to work out what's wrong | 16:05 |
| Bluewolf | Got a wild thought brewing. I'm thinking of doing a fresh install again (not touch a thing, other than the web browser to get back on here) Then running some systems scans. Maybe even doing the bios? | 16:05 |
| Bluewolf | Maybe use an updated .iso too? | 16:06 |
| tomreyn | if you won't loose relevant data this way, i'd do the fresh install with the latest 24.04 ISO, and upgrade the bios. | 16:07 |
| oerheks | daily build? https://cdimage.ubuntu.com/daily-live/20240421/ | 16:07 |
| Bluewolf | I've no data to loose. Its a new install. Everything's sitting, congested on back up drives :D | 16:07 |
| tomreyn | oerheks: this date (in the url) sounds pretty old. | 16:09 |
| tomreyn | (the isos's there are, too) | 16:09 |
| oerheks | oops, https://cdimage.ubuntu.com/daily-live/current/ | 16:09 |
| oerheks | that is also wrong, sorry | 16:10 |
| tomreyn | personally, i would go with the latest point release unless i had indications that the latest daily build is both (a) stable and (b) fixes the issue | 16:10 |
| tomreyn | i.e. just download the 24.04 desktop off ubuntu.com | 16:11 |
| tomreyn | Bluewolf: i'm not sure what you mean by "running some system scans", I assume this is not needed (although I'm not sure what it really means). | 16:12 |
| Bluewolf | tomreyn: I just mean like 'dmesg' or 'nvidia-smi' to give relevant output | 16:14 |
| tomreyn | oh ok, that'd be good, yes | 16:14 |
| Bluewolf | tomreyn: Alright. Let me get this show rolling. Thanks for you time and help thus far, you will be remembered :D :y: | 16:17 |
| Bluewolf | lotuspsychje: You are not forgotten either good sir. Thank you. | 16:17 |
| tomreyn | Bluewolf: you're welcome, good luck | 16:20 |
| stolen | when I ssh into an ubuntu desktop and run some make command or wget a large file, the commands are interrupted if I lose the ssh connection. How to prevent that? So as to ensure that the commands are still running if my ssh connection is not up anymore? | 16:38 |
| zaggynl | sounds like a connection issue | 16:39 |
| zaggynl | usually you use tmux or screen to keep things running | 16:39 |
| stolen | can I not make sure the wget keeps running in the host machine even when I turn off my ssh machine? | 16:39 |
| zaggynl | that or connect to your desktop session by something like nomachine or sunshine/moonlight | 16:39 |
| tomreyn | there's also the "nohup" command | 16:40 |
| tomreyn | https://www.gnu.org/software/coreutils/manual/html_node/nohup-invocation.html#nohup-invocation | 16:40 |
| tomreyn | but a terminal multiplexer (such as GNU screen or tmux or byobu) is usually easier. | 16:41 |
| stolen | hmm, i guess nohup is what I was searching for, but can I still se the progress for the wget or I can't see it anymore unless i dump into log files? | 16:41 |
| tomreyn | you can see it as long as your network connection remains active | 16:42 |
| stolen | i guess that is something tmux does, right? attach the lost wget... | 16:42 |
| tomreyn | no, it just keep the process running remotely, just like nohub, but you can reattach to a running tmux, whereas you cannot to a lost shell | 16:43 |
| tomreyn | *nohup | 16:43 |
| stolen | hmm that seems convenient, thanks for the recommendation! | 16:43 |
| tomreyn | many run irssi (a CLI IRC client) in a GNU screen or tmux session for this purpose | 16:44 |
| tomreyn | the connection from the system between irssi and the irc server can remain established while the ssh connection to system running the tmux session can be lost | 16:45 |
| stolen | that is clever, that is like a self hosted bouncer active 24x7! | 16:48 |
| tomreyn | without needing to expose irc(s), yes | 16:50 |
| Bluewolf | tomreyn: Okay. I'm back with an updated Bios and a fresh install of Ubuntu. The black screen still persists :( | 17:32 |
| Bluewolf34 | tomreyn: Experiencing technical difficulties in terms of internet connectivity :D | 17:45 |
| tomreyn | Bluewolf: dang, sorry to hear this. you're wlecome to share another journalctl -k |& nc termbin.com 9999 if you like. i won't be able to review it now, though (maybe later tonight, or someone else) | 17:45 |
| tomreyn | Bluewolf34: maybe filing a bug report would actually be better, though | 17:46 |
| tomreyn | !bug | Bluewolf34 | 17:46 |
| ubottu | Bluewolf34: If you find a bug in Ubuntu or any of its official !flavors, please report it using the command « ubuntu-bug <package> » - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs. | 17:46 |
| tomreyn | the package would be nvidia-driver-550 | 17:46 |
| Bluewolf34 | Yeah sure. Also removing the login screen seems to work too :D | 17:47 |
| Bluewolf34 | tomreyn: https://termbin.com/io4w | 17:48 |
| Bluewolf34 | lotuspsychje: Still around? | 17:48 |
| tomreyn | Bluewolf34: i'll be back in some hours, sorry. | 17:49 |
| Bluewolf34 | tomreyn: No problem. Message if I'm on. Thanks | 17:50 |
| Bluewolf34 | Anyone else here able to help with Nvidia problems, black screen after login (TTF switching required to get onto the desktop) This is journalctl output?: https://termbin.com/io4w | 18:08 |
| Jeremy31 | Bluewolf34: any result from terminal for> lsmod | grep i2c_nvidia_gpu | 18:19 |
| Bluewolf34 | Jeremy31: Just: | 18:22 |
| Bluewolf34 | i2c_nvidia_gpu 12288 0 | 18:22 |
| Bluewolf34 | i2c_ccgx_ucsi 12288 1 i2c_nvidia_gpu | 18:22 |
| Jeremy31 | https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2016924 | 18:27 |
| -ubottu:#ubuntu- Launchpad bug 2016924 in linux-nvidia (Ubuntu) "nvidia_drm Failed to grab modeset ownership" [Undecided, Fix Released] | 18:27 | |
| monty_hall | just installed ubuntu 24 yesterday. Don't know what happend, but now the gdm3 login manager is stuck at a gray screen, when I look at the "journactl -u gdm" I see " Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed. What's going on? I'm diagnosing over ssh. | 18:30 |
| monty_hall | " | 18:30 |
| Bluewolf34 | Jeremy31: So basically run: echo "blacklist i2c_nvidia_gpu" > /etc/modprobe.d/blacklist_i2c-nvidia-gpu.conf | 18:30 |
| Bluewolf34 | Then: sudo update-initramfs -u | 18:30 |
| monty_hall | I have titan x and 1070GTX, the main display is the titanx | 18:31 |
| Bluewolf34 | monty_hall: Funny. Mine did the same thing. Then I reinstalled the whole OS | 18:31 |
| Bluewolf34 | Didn't figure out what the issue was though. | 18:31 |
| Jeremy31 | Bluewolf34: It might work | 18:33 |
| monty_hall | that's depressing then. Now I'm a bit worried about reinstallation wiping my home dir | 18:33 |
| Jeremy31 | Or if you can edit grub at boot time, scroll down and over to quiet splash and add modprobe.blacklist=i2c_nvidia_gpu | 18:34 |
| Bluewolf34 | Jeremy31: I'm sure I tried it earlier...Damn. I can't quite remember, nor do I have the history to check.... | 18:34 |
| Bluewolf34 | Sounds familiar | 18:35 |
| Jeremy31 | could check in terminal> history|grep nvidia | 18:35 |
| Bluewolf34 | Jeremy31: I've just reinstalled the whole system. Something like this, "echo "blacklist i2c_nvidia_gpu" | sudo tee /etc/modprobe.d/blacklist_i2c-nvidia-gpu.conf >/dev/null && sudo update-initramfs -u" | 18:43 |
| Jeremy31 | That should work | 18:44 |
| ioria | Bluewolf34, correct me: your system boots correctly, but you need to switch to tty in order to get the desktop ? | 18:48 |
| Bluewolf34 | ioria: Correct. I enter details on the login screen. Then the screen goes black. When TTF switch, the login screen appears again. I repeat the process then get onto the desktop | 18:49 |
| Bluewolf34 | System boots just fine | 18:49 |
| ioria | what is TTF ? | 18:50 |
| Bluewolf34 | Jeremy31: This doesn't lead to system crashes | 18:50 |
| Jeremy31 | TTF, might be TTY | 18:51 |
| Bluewolf34 | On login screen pressing Ctrl+Alt+F2 which brings up a 'terminal' screen. TTY sorry =( | 18:51 |
| Bluewolf34 | ioria: Long day :( | 18:51 |
| Jeremy31 | So it works fine now? | 18:51 |
| ioria | Bluewolf34, systemctl get-default | 18:53 |
| Bluewolf34 | Jeremy31: I haven't entered it. I'm scared. I embarked on a journey. 3 reinstalls later I'm scared of falling down the hill :D | 18:54 |
| Bluewolf34 | ioria: What's this for? | 18:55 |
| ioria | Bluewolf34, just to check; don't be scared | 18:55 |
| Jeremy31 | Bluewolf34: editing grub at boot will do the same thing as a test of the commans | 18:55 |
| Jeremy31 | modprobe.blacklist=i2c_nvidia_gpu right next to quiet splash, then I think F10 to boot | 18:56 |
| Bluewolf34 | ioria: graphical.target | 18:57 |
| Bluewolf34 | That's the output. What does that mean? | 18:58 |
| Bluewolf34 | Or what did it do rather? | 18:58 |
| ioria | Bluewolf34, sudo dpkg-reconfigure gdm | 18:58 |
| Bluewolf34 | ioria: Why GDM? | 18:59 |
| ioria | Bluewolf34, because is the default dm | 19:00 |
| ioria | Bluewolf34, unless you changed it with something else | 19:01 |
| Bluewolf34 | ioria: Yeah by why the need to reconfigure, surely its not linked to this issue? | 19:01 |
| Bluewolf34 | Thought it was only with Nvidia? | 19:01 |
| dell | german? | 20:28 |
| sealdistrict | Hey there Ubuntu. Hope you are all doing great. I been having tech issues with regards to monitors.By the way i am running Bionic Beaver if that helps out. It i just because whenever i try and turn the laptop off n the display settings it turns off. tried disabling the screensaver but did have any lv. Please help | 20:53 |
| sealdistrict | *luck i meant instead of lv. Sorry, my keyboard is shit. | 20:54 |
| rbox | if you're having issues with something so ancient... probably should use something a little newer | 20:56 |
| tomreyn | sealdistrict: please note the ubuntu versions supported here (as listed in /topic) | 20:56 |
| sealdistrict | Yes, however I am constraint because I am on a 32 bit laptop. | 20:57 |
| tomreyn | there are probably other linux distros which still support i686, or try to, try #linux | 20:58 |
| sealdistrict | Thanks. Have a good one | 20:59 |
| tomreyn | you, too! | 20:59 |
| hwspeedy | WANTED: Ubuntu packaging maintainer | 21:05 |
| hwspeedy | Program: hardinfo2 (Community ed. of hardinfo) | 21:05 |
| hwspeedy | Hardinfo can show information about hardware and some software and benchmark your PC. Online database. | 21:05 |
| hwspeedy | See https://hardinfo2.org | 21:05 |
| hwspeedy | Status: Is in newest pull from Debian, can build for all maintained Ubuntu. | 21:05 |
| hwspeedy | Task: Maintain in all maintained Ubuntu | 21:05 |
| tomreyn | hwspeedy: this is an ubuntu support channel, please post your maintainer requests elsewhere. | 21:08 |
| hwspeedy | tomreyn: Okay, sorry, thx | 21:09 |
| Bluewolf | tomreyn: Back I presume? | 21:15 |
| tomreyn | Bluewolf: yes. you. too, i see. :) | 21:16 |
| Bluewolf | For a moment... | 21:16 |
| tomreyn | !logs | Bluewolf you seemed to wonder about this | 21:17 |
| ubottu | Bluewolf you seemed to wonder about this: Official channel logs can be found at https://irclogs.ubuntu.com/ . LoCo channels are now logged there too. Meetingology logs at https://ubottu.com/meetingology/logs/ | 21:17 |
| tomreyn | Bluewolf: did you post a bug report, yet? | 21:18 |
| Bluewolf | Huh, the more you know. I hardly ever get onto chats. I haven't, got some possible solutions from fella's was gonna check. | 21:19 |
| Bluewolf | tomreyn: Someone shared this: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2016924 | 21:21 |
| Bluewolf | Or this command instead of the one on that site: | 21:21 |
| Bluewolf | echo "blacklist i2c_nvidia_gpu" | sudo tee /etc/modprobe.d/blacklist_i2c-nvidia-gpu.conf >/dev/null && sudo update-initramfs -u | 21:21 |
| -ubottu:#ubuntu- Launchpad bug 2016924 in linux-nvidia (Ubuntu) "nvidia_drm Failed to grab modeset ownership" [Undecided, Fix Released] | 21:21 | |
| Bluewolf | Also, haven't updated anything yet. What's you opinion on the way to proceed? | 21:21 |
| tomreyn | Bluewolf: filing a bug report, continue using the workaround for now. | 21:22 |
| tomreyn | oh, and certainly install the latest updates | 21:23 |
| Bluewolf | Oh, was the 'echo' the work around? | 21:23 |
| tomreyn | switching to a tty and back agoun is the workaround i know of | 21:23 |
| Bluewolf | Or removing the login screen all together it seems | 21:24 |
| Bluewolf | That worked. | 21:24 |
| Bluewolf | Then I won't run that command above. | 21:24 |
| tomreyn | i had you try disabling i2c_nvidia_gpu back when you were Guest22 | 21:27 |
| tomreyn | and, from what i understood then, you stated you had done so and it did not help | 21:28 |
| Bluewolf | tomreyn: I can't actually remember anymore :( | 21:39 |
| Bluewolf | What package name do I use for the bug report? nvidia? | 21:39 |
| tomreyn | you have access to the logs, though | 21:42 |
| tomreyn | <tomreyn> the package would be nvidia-driver-550 | 21:42 |
| Bluewolf | Apologies, haven't done this before. "ubuntu-bug nvidia-driver-550" in terminal then follow the prompts? | 21:44 |
| tomreyn | yes, exactly, you'll need to register an ubuntu sso account, if you haven't done so before | 21:44 |
| tomreyn | but the process will guide you | 21:45 |
| Bluewolf | Makes sense it will be all the nvidia ones, cause they all had the same issue for me. | 21:45 |
| tomreyn | maybe you actually need to file it against "nvidia-graphics-drivers-550", but it should tell you if nvidia-driver-550 is not a valid target | 21:48 |
| Bluewolf | Its done, nvidia-driver-550 has gone through | 21:49 |
| tomreyn | can you share the bug's id or url? | 21:50 |
| tomreyn | Bluewolf: ^ | 21:56 |
| Bluewolf | Will do. Its giving me the run around of verifying email and such. How annoying | 21:57 |
| tomreyn | It's a one-time registration only, though | 21:57 |
| Bluewolf | Okay now that I've been tormented by that, where do I find the URL? | 22:02 |
| Bluewolf | It doesn't show me my bug report or I start again? | 22:04 |
| tomreyn | hmm if you didn't get forwarded to the bug reporting location then i assume you need to start again. but you can reuse your existing account. | 22:06 |
| Bluewolf | tomreyn: bug #2103957 | 22:10 |
| -ubottu:#ubuntu- Bug 2103957 in Canonical SSO provider "nvidia-graphics-drivers-550 Crash on log. Black Screen" [Undecided, New] https://launchpad.net/bugs/2103957 | 22:10 | |
| byrobot | wow | 23:13 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!
