Screen freezes after logging in

asimov · 2016-11-05 02:15:51

Hello there BL community new member here and a little bit of a linux noob. I was able to install Hydrogen via CD to an old desktop. (HP pavilion AMD Athlon 63 dual-Core, 2gb ram 320gb HDD) The only problem I've run into so far is that after I logged out the first time and went to log in, after typing in my credentials it goes to log in and then freezes with this type of screen. sorry for the small image. Now I'm no expert but I"m thinking either two things it has to do with me doing an offline insstallation or something with the graphics of the PC. I looked around on the fourms for things like this and either I didn't look enough or didn't use the right search terms. If any of you guys know if anyone has encountered a similar problem or know of a fix it would be much appreciated.

Thanks in advance for any/all help!

Last edited by asimov (2016-11-05 02:16:08)

Horizon_Brave · 2016-11-05 04:26:21

Does this happen consistently? What about from a cold boot, or does it just happen when you log out and log back in? What graphics card do you have? What's the output of the command:

lspci -knn

asimov · 2016-11-05 11:53:07

So I tried agian today and yes it happened again from cold boot. From my online research the graphics should be nvidia GeForce 6150 SE. Also I'm a pretty much a beginner here so would there be anyway to start in CLI to get the output of

lspci -knn

or do you think that would just cause it to freeze still?

Head_on_a_Stick · 2016-11-05 12:00:01

asimov wrote:

would there be anyway to start in CLI

Highlight the BunsenLabs entry in the GRUB menu then press "e" and add this to the end of the line that starts with "linux":

systemd.unit=multi-user.target

Then press <Ctrl>+x (at the same time) to boot the modified entry.

Also, to save you typing out lots of output, we only really need to know the

Kernel driver in use:

and the [Vendor ID:Product ID] numbers for that card, see this link for more:

https://wiki.debian.org/HowToIdentifyADevice/PCI

Please also check the `lspci` output for any Intel video chips, if you have those as well then you should check this link:

https://wiki.debian.org/Bumblebee

ohnonot · 2016-11-05 15:36:16

HoaS, i had a pretty similar amd mobo with maybe even the same nvidia card.
it definitely isn't a dual graphics setup.
it is possible to put in another gpu in the pci slot, but the nvidia is some sort of inbuilt gpu.

asimov wrote:

nvidia GeForce 6150 SE.

from the look of your image i'd say it is indeed a graphics driver problem.

we need that lspci output.

iirc, it was ebneficial to install the proprietary driver, but it has to be the proper legacy version.
see here:
https://wiki.archlinux.org/index.php/Nv … stallation

"For GeForce 6000/7000 series cards [NV4x and NV6x] from around 2004-2006, install the nvidia-304xx or nvidia-304xx-lts package along with nvidia-304xx-libgl."

this is for archlinux, but the packages will have similar names on debian because the versioning comes from nvidia.

similar howto's are available on the debian wiki.

asimov · 2016-11-05 18:53:01

Alright so thanks so much Head_on_a_Stick for the CLI start up also I found for what looks to be the graphics card

Kernel driver in use: nouveau

with vendor/product ID's [10de:03d0]

Head_on_a_Stick · 2016-11-05 19:44:34

asimov wrote:

vendor/product ID's [10de:03d0]

A quick search of that ID and the word "debian" turned up this thread over at fdn:

http://forums.debian.net/viewtopic.php?f=7&t=128332

The OP appears to have the same card and notes that:

xserver-xorg-video-nouveau : intermittent system freeze (random pattern on screen)

So perhaps you should try the proprietary driver, although @stevepusser advises trying a newer kernel version first.

According to the thread, your device is supported by the legacy NVIDIA driver but you should check by using `nvidia-detect`, as per https://wiki.debian.org/NvidiaGraphicsDrivers

Horizon_Brave · 2016-11-05 21:28:24

asimov wrote:

So I tried agian today and yes it happened again from cold boot. From my online research the graphics should be nvidia GeForce 6150 SE. Also I'm a pretty much a beginner here so would there be anyway to start in CLI to get the output of
lspci -knn
or do you think that would just cause it to freeze still?

My apologies asimov, didn't mean to assume any prior knowledge!

asimov · 2016-11-05 23:39:16

Horizon_Brave wrote:

My apologies asimov, didn't mean to assume any prior knowledge!

No problem thanks for the help!

Head_on_a_Stick wrote:

A quick search of that ID and the word "debian" turned up this thread over at fdn:
http://forums.debian.net/viewtopic.php?f=7&t=128332
The OP appears to have the same card

Alrighty cool I'll check it out and get back to y'all when I get results or am faced with more questions! Thanks so much everybody!

Horizon_Brave · 2016-11-06 04:18:43

Head_on_a_Stick wrote:

asimov wrote:
vendor/product ID's [10de:03d0]
A quick search of that ID and the word "debian" turned up this thread over at fdn:
http://forums.debian.net/viewtopic.php?f=7&t=128332
The OP appears to have the same card and notes that:
xserver-xorg-video-nouveau : intermittent system freeze (random pattern on screen)
So perhaps you should try the proprietary driver, although @stevepusser advises trying a newer kernel version first.
According to the thread, your device is supported by the legacy NVIDIA driver but you should check by using `nvidia-detect`, as per https://wiki.debian.org/NvidiaGraphicsDrivers

HoaS, just for completeness here... why would upgrading to a newer kernel version be a better option than using the legacy nVidia driver? Wouldn't installing and running a newer kernel possibly present compatibility issues with existing packages, moreso than just adding the nvidia driver that's written for his current kernel version?

Last edited by Horizon_Brave (2016-11-06 04:19:03)

Head_on_a_Stick · 2016-11-06 10:00:22

Horizon_Brave wrote:

why would upgrading to a newer kernel version be a better option than using the legacy nVidia driver?

In a word?

Blobs...

This is from the OpenBSD people but it applies to all operating systems:

Blobs are expedient. Many other open source operating systems cheerfully incorporate them; in fact their users demand them.
But when you need to trust the system, how do you check the blob for quality? For adherence to standards? How do you know the blob contains no malicious code? No incompetent code? Inspection is impossible; you can only test the black box. And when it breaks, you have no idea why.

https://www.openbsd.org/lyrics.html#39

The useful thing about kernel upgrades is that the old kernel can still be booted into should there be any problems.

#1 2016-11-05 02:15:51

Screen freezes after logging in

#2 2016-11-05 04:26:21

Re: Screen freezes after logging in

#3 2016-11-05 11:53:07

Re: Screen freezes after logging in

#4 2016-11-05 12:00:01

Re: Screen freezes after logging in

#5 2016-11-05 15:36:16

Re: Screen freezes after logging in

#6 2016-11-05 18:53:01

Re: Screen freezes after logging in

#7 2016-11-05 19:44:34

Re: Screen freezes after logging in

#8 2016-11-05 21:28:24

Re: Screen freezes after logging in

#9 2016-11-05 23:39:16

Re: Screen freezes after logging in

#10 2016-11-06 04:18:43

Re: Screen freezes after logging in

#11 2016-11-06 10:00:22

Re: Screen freezes after logging in

Board footer