[SOLVED] Mandriva Linux 2010.0 hanging

pauljam20 · 12-02-2009, 04:44 AM

I get regularly hangs and I can't find any way out of it, I've tried all the ctrl-alt-* key combinations and nothing happens.

I've got a 1.7GHz Intel processor and use Mandriva 2010.0 with Gnome 2.28.0. I only use Linux, am not an expert

I don't think it is to do with Mozilla pluginwrapper problems as I've switched to Opera and it still happens - whether or not I'm using a browser.

When it happens, the mouse usually continues to work but not always. If I am watching a video or listening to a BBC iPlayer console, the video hangs but the sound carries on without problems.

I don't know whether it is relevant, but with the system running now, in system monitor I can see several references to GVFS (is this needed?) and synce-trayicon (I want to use this but can't get it to work).

I'd appreciate suggestions as I'm getting fed-up with it, and although I think Linux is a lot better than that other thing, I can't honestly recommend it to friends at the moment.

GlennsPref · 12-03-2009, 07:17 PM

Hi, I've been watch your thread and have noticed no replies as yet.

Although I use kde4, and not gnome, I though I may be able to help.

Quote:

Gvfs is a userspace virtual filesystem with backends for things like sftp, ftp, dav, smb, obexftp, etc.

ref. https://fedoraproject.org/wiki/Features/Gvfs
and http://en.wikipedia.org/wiki/GVFS

It uses fuse, and may not be required if you don't need remote access to your desktop.
(please correct me If I err)

I read that is was mostly useful for remote desktop access, but can't find that reference now.

I have a few suggestions that may point you in the right direction.

from a command line run....you need to be root or use sudo

Code:

rpm --rebuilddb && rpm -Va | grep miss

this will take a while, what it does is rebuilds the installed rpm's database and

then searches it looking for missing packages.

Go through the list installing any thing missing and it's dependant packages.

I had initially installed mandriva with both kde4 and lxde desktops, and this is probably how I got gvfs installed.

I also found it hogged memory and processor power.

I simply removed the package, but as I said, I don't run gnome (or lxde) as my current desktop manager.

see how you go, post back here with any questions and we'll continue from there.

cheers and regards Glenn

ps, sometimes it is worth sitting at console 12 (ctrl+alt+F12) and view the kernel output as the system is running, sometimes revealing a kernel hang, or some such problem that may lead to an answer to this kind of problem. GW

pauljam20 · 12-04-2009, 04:55 AM

It only mentioned /usr/lib/mozilla/plugins/npwrapper.so as missing so presumably not a problem unless using Firefox. I have removed GVFS using the software manager. I've only just logged in, but everything still works, I'll watch and see what happens and let you know.

A bit more information:
The display card is intel 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device. I haven't been able to find out which is the display driver.
The frequency of hanging varies, sometimes quite soon after switching on, but usually after an hour or two.

I've checked under "set up the display manager" and find KDM - is this odd because I use the Gnome desktop?

KDM KDE display manager - selected
GDM Gnome display manager
XDM X display manager

Quote:

Originally Posted by GlennsPref

Hi, I've been watch your thread and have noticed no replies as yet.

Although I use kde4, and not gnome, I though I may be able to help.

ref. https://fedoraproject.org/wiki/Features/Gvfs
and http://en.wikipedia.org/wiki/GVFS

It uses fuse, and may not be required if you don't need remote access to your desktop.
(please correct me If I err)

I read that is was mostly useful for remote desktop access, but can't find that reference now.

I have a few suggestions that may point you in the right direction.

from a command line run....you need to be root or use sudo

Code:

rpm --rebuilddb && rpm -Va | grep miss

this will take a while, what it does is rebuilds the installed rpm's database and

then searches it looking for missing packages.

Go through the list installing any thing missing and it's dependant packages.

I had initially installed mandriva with both kde4 and lxde desktops, and this is probably how I got gvfs installed.

I also found it hogged memory and processor power.

I simply removed the package, but as I said, I don't run gnome (or lxde) as my current desktop manager.

see how you go, post back here with any questions and we'll continue from there.

cheers and regards Glenn

ps, sometimes it is worth sitting at console 12 (ctrl+alt+F12) and view the kernel output as the system is running, sometimes revealing a kernel hang, or some such problem that may lead to an answer to this kind of problem. GW

pauljam20 · 12-04-2009, 05:28 AM

It's just hung again.

I was watching the screen created by ctrl-alt-F12 and saw something called cron run and a message containing "unable to read EDID block" and something like "VGA-1 no EDID data". I switched back to the desktop a couple of times without problem, then when I tried again later it had hung.

GlennsPref · 12-04-2009, 06:59 AM

Hi, EDID data is the xorg looking to the display monitor chip to find out it's frequency and resolution properties.

You may be able to circumvent this behaviour
by editing the /etc/X11/xorg.conf file monitor section.

Adding in the properties you want, and that your monitor can do.
Here is mine....

Code:

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "MEA"
    ModelName 	   "1280x1024 @ 50 Hz"#"DV177/SB"
    HorizSync      31.5 - 64.3
    VertRefresh    50.0 - 70.0
    Option         "DPMS"
EndSection

otherwise uninstall a package like this...
urpme monitor-edid-2.5-1mdv2010.0.x86_64

See how you go. Regards Glenn

Quote:

/usr/lib/mozilla/plugins/npwrapper.so

is only necessary for viewing flash in a web page.

ernie · 12-04-2009, 09:15 AM

As cautionary note, and to emphasize the importance that you use the settings for your display, not those Glenn posted (they are for his display). If you try to make your display operate at a frequency or resolution it is not capable of, you could damage it. All the information you need should be included in your displayś user manual. If you do not have a users manual for your display, google for it by manufacturer and model on the WEB.

HTH,

pauljam20 · 12-04-2009, 11:44 AM

After I had removed GVFS I couldn't see anything on my desktop or use the file manager - error message, so it looks as though it's needed! I've had to re-install the system.

I'm no expert so am only guessing, but since other things continue to work I don't think it is a kernel problem but something to do with X-windows or the Gnome desktop.

GlennsPref · 12-04-2009, 05:34 PM

hi, sorry to cause you to reinstall mandy. Not my intention at all.

I hope it's working ok and have a few tips for you to check out.

Quote:

I haven't been able to find out which is the display driver.

typing lsmod in a terminal will list all the loaded modules(drivers) on your system.

you may need root access to do this.

you can cut down that list by grepping (grep) the name you're looking for.

Like this....using the info you provided....

Quote:

intel 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device

Code:

lsmod | grep intel

If you have an intel based system that is bound to show a few modules,
(I don't have an intel based system so)
I'm running blind here and you may need to change things around to suit your system,
btw, this is just info gathering, not changing things.

or the chip number....

Code:

lsmod | grep 82845G

what this command does is
lists loaded modules, (lsmod)
piped (|) through grep searching for the name of the device entered after the term grep.

another way to check is lspci, but you already know what the device is called.

I think you maybe correct in your assumption that it could be an X problem.

A keyboard error may also cause a crash, locking up the terminal.

There are updates available for mandy 2010.0, be selective about what you upgrade, you'll get a better understanding of what is required as opposed to what is desired.

One last thing, to change the login to gdm, go to MCC (configure your computer), boot, set up display manager.

you should see the option there.

cheers Glenn

rolf · 12-06-2009, 09:09 AM

The 845 chipset driver has a bug that might be related to your problem. I think it would be easy and not hurt to try the workaround I pointed to in another thread: http://www.linuxquestions.org/questi...5/#post3781738

pauljam20 · 12-07-2009, 07:15 AM

Rolf - I've looked into your suggestion, it seems to relate to a problem that occurs on startup, so probably not the answer. Also the line that started "Simply..." in one of the messages was completely beyond me - so I think I'll leave it thanks!

Quote:

Originally Posted by rolf

The 845 chipset driver has a bug that might be related to your problem. I think it would be easy and not hurt to try the workaround I pointed to in another thread: http://www.linuxquestions.org/questi...5/#post3781738

pauljam20 · 12-07-2009, 08:03 AM

Glenn

I have logged in as root and typed lsmod, but there were no references to intel or 82845G.
I have switched off the screen saver, because a lot of hangs occurred when it was displaying and I have changed to GDM. Since doing this yesterday, the computer has run for ~5 hours before crashing. There may be some clues there...

I get occasional crashes of (I think - I should have made a note) the taskbar, which include a comment about increasing
fs.inotify.max_user_watches to 65536 in /etc/sysctl.conf. Could this be a problem when a lot of files are opened and closed with browser or screensaver? There is currently no statement like this in this file.

Quote:

Originally Posted by GlennsPref

hi, sorry to cause you to reinstall mandy. Not my intention at all.

I hope it's working ok and have a few tips for you to check out.......

cheers Glenn

rolf · 12-07-2009, 08:13 AM

Quote:

Simply edit your command line on the gfxboot by pressing [F3], then choose Default, end add i915.modeset=0 to the command line. Just press [Enter] to boot your computer

This refers to the graphical grub boot menu. Something like the attached screenie but with more choices, such as failsafe, perhaps a windows installation. When you see this menu screen, press F3 and add the i915.modeset=0 switch at the end of the kernel command line, separated by a space. In the linked post, I give more verbose instructions from the point of view of using the text grub menu, which I do, some of which apply to editing the menu entry for the graphical boot, also.

For perspective, the menu entries can be seen in /boot/grub/menu.lst for example:

title linux
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=1b785fa1-2ce3-4964-8e5c-43cec6dcaa3c vga=788 speedboot=no
initrd (hd0,4)/boot/initrd.img

The first line, title, specifies what you see in the menu. The second is the command line for the kernel. This is the line to which you add the kernel switch of interest. The third line points to the initrd, which contains drivers for the hardware on your machine, in order to start the system.

This link takes forever to load but it's a report of this switch solving X crashing, not just the startup problem: http://bugs.debian.org/cgi-bin/bugre...?bug=536011#10

Another, perhaps clearer howto for testing the switch by one-time edit of the grub kernel command line: http://blogs.sbsun.com/click/2009/11...d-in-ubun.html

GlennsPref · 12-07-2009, 07:40 PM

Hi, this could be another problem.

Quote:

fs.inotify.max_user_watches to 65536 in /etc/sysctl.conf

and may well be the culprit of your latest crash.

You need root access to save the edit of this file.
just copy and paste the line to the end of the list.
/etc/sysctl.conf

Code:

fs.inotify.max_user_watches=65536

like this....using vi in a shell(cli) (if sudo is not setup, su to root first....

Code:

sudo vi /etc/sysctl.conf

press i to go to insert mode.
use arrows keys to navigate to the end of the file
copy this line....
fs.inotify.max_user_watches=65536
paste in to terminal(cli)
hit enter to get a blank line at the end.
press esc to exit insert mode.
press :wq to write the file and quit.
type exit to leave root if necessary.
after you have rebooted the kernel, test.

wait for a crash.....I hope you don't get any more.

please don't disregard rolf's advise.

Quote:

pressing [F3], then choose Default, end add i915.modeset=0 to the command line. Just press [Enter] to boot your computer

regards Glenn

pauljam20 · 12-08-2009, 12:50 PM

Rolf

Quote:

Originally Posted by rolf

This refers to the graphical grub boot menu...

Your second post convinced me - and thanks for the simple explanation! I tried this on boot up and the PC ran for 24 hours without any problems, even using the F-Spot screensaver (although that didn't work properly until I rebooted), so I think you've cracked it! I've tried to find out what it does and I think it switches Kernel Mode-Setting off - I sort-of understand that, and that it is a new thing, which possibly needs development or is not suitable for my graphics card.

As an aside, I recently noticed an error message on boot "loading i915 module cannot open file delete" it hasn't changed since applying your patch, so I don't know whether it is relevant.

Thanks for your help - I really appreciate it!

pauljam20 · 12-08-2009, 12:51 PM

Thanks Ernie - point taken!

Quote:

Originally Posted by ernie

As cautionary note, and to emphasize the importance that you use the settings for your display, not those Glenn posted (they are for his display). If you try to make your display operate at a frequency or resolution it is not capable of, you could damage it. All the information you need should be included in your displayś user manual. If you do not have a users manual for your display, google for it by manufacturer and model on the WEB.

HTH,