You are not logged in.
I'm not so sure what relevant information I can give.
I press ctrl-alt-f1 (or any of the other f-keys other than f7) and after a moment of black screen my monitor flashes it's "No input detected" screen and goes for a nap. It's probably worth mentioning that I followed this guide to install the proprietary nvidia drivers and I must have been able to switch to different tty's when I was doing that because you need to drop into a different tty to stop the lightdm.
Any ideas on how to go about fixing this? Any help is very appreciated.
Davy
I'm marking this thread as solved because there's no longer an issue with the tty now that I'm on the nouveau driver. If I can't solve the additional related problems I'll post them as a separate thread.
Last edited by Davy (2018-06-10 20:33:34)
Offline
I followed this guide to install the proprietary nvidia drivers
Why did you install the proprietary drivers?
I would strongly recommend sticking with the default nouveau drivers in BunsenLabs — the non-free alternatives have a performance advantage but are considerably more buggy, as you have now found.
Offline
I was having issues with resolution and screen tearing which were fixed by the proprietary drivers. You did offer a solution for the resolution where I get to keep the nouveau drivers but I had already installed the proprietary drivers by then. Is it easy to switch between? I could try revert back to the nouveau drivers and try fix the screen tearing and resolution issues, but at the end of the day, I'm not too fussed about being able to use the other tty's. It's handy on the rare occasion when something freezes and I can't alt-tab out because I can jump into another tty and open up htop to end the process in question, but it's not much more bother to just restart.
Offline
Is it easy to switch between?
Change back to nouveau with https://wiki.debian.org/NvidiaGraphicsD … of_failure
I think the Debian stretch version of nouveau will probably support your card better, the next release of BunsenLabs will be based on that.
Until then you can try using compton to control vsync and reduce tearing by adding these flags:
--backend glx --vsync opengl-mswc
Copy /usr/bin/bl-compositor to ~/bin/ and edit that file to change the flags.
Offline
i have a different idea.
- last time i used nvidia it wasn't capable of full resolution in tty, so the resolution would change when leaving the gui.
- what is the monitor? esp. some TVs are very sensitive to resolution changes, and might go into "No Signal" mode.
Offline
Oh! I thought I had replied here.
@ohnonot It's an Asus VX228H.
@Head_on_a_Stick I think I might just do that. I think I'll wait for the next release, though: It's not a pressing issue in the meantime.
I came back to this thread because I had a spare monitor sitting about and I thought I'd go for a dual monitor set-up. It is vga, and my graphics card has no vga port, so on a whim I decided to try the motherboards vga port. Funnily enough, plugged into the motherboard, this monitor *only* works when I'm in a different tty.
Last edited by Davy (2018-04-01 22:52:51)
Offline
We have a "live" ISO image for the beta version of the next release, you could try that and see if nouveau behaves better for you there:
https://forums.bunsenlabs.org/viewtopic.php?id=4698
We should have the release out soon (hopefully).
Offline
Oh, that's just lovely. I tried it out on a live usb. Works a charm. Can't wait!
Offline
Let me know if you still have issues with the proprietary nvidia drivers. I find the “use nouveau” answer a bit dissatisfying - you paid for hardware, may as well try to get it performing as intended. Open source drivers unfortunately won’t get you there. Let me know if you want to chase this down a bit, I’m happy to try to help.
Offline
Speaking of ctrl-alt-f1: If I change to tty1, why can't I login as root? At least using "root" and "rootpassword" does not work for me (neither user login). I always get "login incorrect".
Offline
@martix Just to make sure: did you create a separate root account during install? Otherwise you'd be left with sudo.
Offline
@vinzv That was it then, thank you for the hint. I did not create a separate root account (was thinking there is one by default). I did check it again and user login works fine (must have mistyped something first). Getting such a login without X is a good way to test how working with a pure cli distro would look like.
Offline
Until Jessie you had to explicitly select creation of just a user with sudo privileges. That account creation behaviour changed with Stretch iirc.
Offline
@cloverskull thanks for the offer! I'm quite happy to try the nouveau drivers again when Helium comes out. From the brief bit of testing I did from my live usb I didn't come across anything objectionable. In the meantime, apart from the tty problem the Nvidia drivers are working nicely.
Offline
Until Jessie you had to explicitly select creation of just a user with sudo privileges. That account creation behaviour changed with Stretch iirc.
I don't know what the Debian Stretch default is, but BL uses a preseed setting which specifically calls for the sudo setup, not a root account.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
I thought I'd put an update here now that I've upgraded. The Nouveau drivers are working, I think: The tty issue is no longer there. I haven't played any games yet so I can't say for sure but as far as I can tell: there has been no screen tearing.
I have a couple of new problems now:
I'm not entirely certain if my computer is using my graphics card...
Screenfetch calls my GPU "Gallium 0.4 on NV126" and
lspci -vnnn | perl -lne 'print if /^\d+\:.+(\[\S+\:\S+\])/' | grep VGA
outputs
00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 [VGA controller])
I read online that [VGA controller] should indicate which is active.
Additionally, I have problems starting steam:
davy@fainna:~$ steam
rm: cannot remove '/home/davy/.steam/bin': Is a directory
Running Steam on bunsenlabs 9.4 64-bit
STEAM_RUNTIME is enabled automatically
Installing breakpad exception handler for appid(steam)/version(0)
libGL error: unable to load driver: nouveau_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: nouveau
libGL error: unable to load driver: nouveau_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: nouveau
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
Anyway, that's all. Thanks for reading. If I find any solutions I'll put them here.
Last edited by Davy (2018-06-10 16:30:43)
Offline
Since this thread is marked [Solved] it would be better to start a new one for any new problems. In fact, if the problems are unrelated, several threads.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline