I have a clean install of 12.2 on my ASUS ET2701INKI. It has an nvidia gt640n graphics card. I’ve had a couple of desktop freezes which I suspected is an nvidia issue that I’ve seen on the forums but hadn’t got around to dealing with yet. Yesterday my system worked fine and I didn’t do and manual/auto updates.
This morning, now lunch time, I can’t login, it hangs at Starting LSB: susefirewall2 phase 2. I can got to terminal. I guess this is the nividia issues and after some searching found some forums that suggested adding nomodest to /etc/default/grub the line GRUB_CMDLINE_LINUX_DEFAULT and then running grub2-mkconfig.
Great, but… I made the changes but can’t save. I get a E514: write Error (file system full) problem. Some more searching and a df suggests that rootfs and /dev/sda2 are at 100%.
However, I’m now at the limit of my linux self-help knowledge. I don’t know how to resolve the E514 prob to save the changes and see if nomodest will work and get my system up and running again. Any suggestions/help/alternatives greatly anticipated.
Some more searching and a df suggests that rootfs and /dev/sda2 are at 100%.
This may well be your main problem, and needs to be rectified before attempting any changes to bootloader settings, or anything else.
Please show us that ‘df’ output, (please use code tags for that output, the # button).
Forgive the formatting if the columns haven’t lned up, I had to type it in. Dvhenry, you may be right about this being the issue, though I’ve never had this as a problem before today.
Some further info, my /var/log/messages is about 17gb that’s filling the space, but not sure why. Do not ask me to copy in a tail of the messages file, I’m accessing the forum on my tablet
Some further info, my /var/log/messages is about 17gb that’s filling the space, but not sure why. is about 17gb that’s filling the space, but not sure why.
I recall a thread on this forum where, I believe the same issue with /var/log/messages occurred, you may find your answer with a search of the forum, or hopefully, one of those involved in that discussion may see this thread.
It may be worth starting a new thread with a title that indicates the problem of ‘/var/log/messages filling the partition’, as this would gain the attention of those best able to solve the problem.
Ok, that login was apparently a bit of a fluke. Managed to login, system froze after about 20 minutes. Logged in again after a reboot, and got the nvidia driver. Logged out to install the nvidia driver according to the forum post sdb installing nvidia the hard way, went to log back in again and now I can’t get in at all.
I’m back to hanging at the susefirewall2 phase 2. This time, the df says rootfs uses 35% and /dev/sda2 uses 35% so the partition isn’t full.
No idea what the problem is. Getting a little frustrated as having to do all work on my tablet which is not the best way to be writing my phd thesis. I know, not everyone else’s problem. But would like to get this thing working and stable. So any other suggestions from the community? Thanks to dvhenry for his help so far.
I do not think it hangs. Login prompt on console is displayed before all services finished startup, and suse firewall just happens to be the last one. Press RETURN or Alt-F2 and you should see login prompt.
Not really. You made it harder to find out, since /var/log/messages may have contained repeating errors about something causing the flooding of the file.
It does not get far enough to display the normal login screen. As mentioned above, I can login via the terminal but that is it. I can’t login through the regular GUI. The boot process halts before reaching that point.
I was aware of that option, but getting logged in at all was a priority and was suggested to me by smaug42. As it turns out, it was a temporary solution as I can’t fully boot up again, and this time /var/log/messages is not filling the partition. Currently, rootfs is still only using 35% of the partition as it was late yesterday. There must be some other issues.
On 2012-11-17 20:06, rosiescape wrote:
>
> arvidjaar;2504381 Wrote:
>> I do not think it hangs. Login prompt on console is displayed before all
>> services finished startup, and suse firewall just happens to be the last
>> one. Press RETURN or Alt-F2 and you should see login prompt.
>
> It does not get far enough to display the normal login screen. As
> mentioned above, I can login via the terminal but that is it. I can’t
> login through the regular GUI. The boot process halts before reaching
> that point.
Just try to press Enter anyway. You should get a terminal prompt.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))
As from the first message in the thread, I haven’t said that I can’t login to the terminal, I can. That was how I was able tocheck /var/log/ and stuff. I am unable to get my system to show the gui login and gointo the kde desktop. I’m sorry if I have written this in a way that is understood. On my system, it begins to boot. I get the green screen with the fireflies, then it goes black, which it used to before but only for a moment and then normally the gui login screen would show. However, now when it goes black, it shows starting/started several messages zand ok for things like network manager and stops at the line started lsb: susefirewall2 phase2. It just hangs here. I am then able to hit ENTER and go to terminal and login. But I can’t get to kde desktop. I can only do things in the terminal.
Again, my apologi3s if everyone has miss understood my previous posts.
On 2012-11-18 20:26, rosiescape wrote:
> for things like network manager and stops at the line started lsb:
> susefirewall2 phase2. It just hangs here. I am then able to hit ENTER
> and go to terminal and login. But I can’t get to kde desktop. I can only
> do things in the terminal.
I see…
I could be a video problem, then :-?
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))
Yup, it’s a video problem. Here’s the update on the situation. My system has an nvidia GT640M video card installed, but as it has an i7 cpu, that also means it has an integrated intel gpu on the cpu. Note, it is not an optimus system, they don’t work together, they are independent of each other.
With the nvidia drivers installed, what was happening is that during boot, the nvidia driver starts to install but stops about a third of the way through and the intel drivers take over and install. Thus causing some problems. I’ve removed the nividia drivers and at this time the system loads and I can login via X with no problems. This is also what was leading to the increased size of /var/log/messages which caused an additional problem of filling the root partition. By removing the nvidia drivers and just uing the intel gpu, /varlog/messages remains at a reasonably small size.
However, I would really love to be able to use the nvidia gpu instead. I can’t find any way to disable the intel gpu. It’s not an option in the bios. So does anyone have any suggestions on how to have the system ignore the intel gpu and just focus on the nvidia drivers during startup?
> However, I would really love to be able to use the nvidia gpu instead.
> I can’t find any way to disable the intel gpu. It’s not an option in the
> bios. So does anyone have any suggestions on how to have the system
> ignore the intel gpu and just focus on the nvidia drivers during
> startup?
No idea, sorry.
> If needed, I can start this as a new post.
I think that’s a good idea, asking with an appropriate title to the turn
of things.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))
So does anyone have any suggestions on how to have the system ignore the intel gpu and just focus on the nvidia drivers during startup?
Yes, I have some, but I would like to see your xorg log (use SUSE Paste and provide a link).
Further to conram’s point about a bios setting for the boot device (which may or may not effect the initialization of the other graphics adapters), you will likely find the option for the discrete adapter described as PEG (PCIe Graphics). Given your description it would seem that the nvidia device is already set as the boot device anyway. The output from
Hi, wanted to let you know I will post the details you’ve asked for. At a conference this week and back next week. Thanks for your reply and suggestions.
