Ubuntu Installation :: Gnome Init Freezes In 9.10 On New Intel DH55TC
Jan 13, 2010
I just purchased a new Intel DH55TC motherboard, a Core i5-661 processor, a WD Caviar Green 640GB drive, and a Linksys WMP110 card. I was able to successfully install 9.10, but every time it loads to the desktop it freezes. It seems like it may be an ACPI problem with the built-in H55 graphics card on the CPU. I hit 'e' at the grub prompt, and added 'noacpi' to the end of both the kernel (or linux?) line and the initrd line. WHen I did that, I was able to get to a point that it was fully loaded and I could move the mouse around, but as soon as I opened a menu, like 'Applications', the desktop froze again.
(NOTE: I have today's daily 10.04 on a USB, and will try that next as a live disk)
[A word of explanation: initially the post below followed a post by Adam Williamson in another thread devoted to inability to load GNOME 3 in VM; this is why I address Adam in the opening.]
Adam, the situation with the GNOME 3 support for Intel integrated graphics seems to be a little confusing. You are probably among the most competent to clarify it.
Let me tell my own story first.
I was installing earlier today Fedora 15 on an HP dm4-1160US laptop with i5 and Intel graphics, and the anaconda installer hung right after "Waiting for hardware to initialize..." flashed on the screen, before even Media Check screen was reached. I tried a few times, always with the sae result: anaconda hung. Then I decided to add nomodeset to the boot parameters and the anaconda installer went on and I was able to complete the installation without a slightest problem.
I rebooted and without a problem reached the GDM login screen. When logging into GNOME, a pop-up window informed me that the system was unable to load GNOME and that instead I would be logged into the fall back mode. By the way, I haven't experienced the problems that plagued "Classic GNOME" on another laptop of mine where instead of clean install I preupgraded from Fedora 14 (strictly following the guidelines for preupgrading).
Wireless card was recognized and wlan initialized, nearby wireless networks seen, yet I wasn't able to connect to my own wireless network (I tried to do this already in the process of installation, equally unsuccessfully).
I was able to connect via Ethernet cable, and then I proceeded to perform yum update.
The update brought a new kernel. I went into grub.conf and noticed that nomodeset has been automatically added to the boot parameters for each of the two kernels. I decided to perform an experiment: I removed nomodeset from the boot options for the new kernel, and left it in place for the anaconda installed kernel.
I rebooted into the new kernel. Right after the grub menu disappeared, the screen turned pitch black and stayed this way for good 10 seconds. I thought that the former situation repeats itself making impossible to boot without the nomodeset option. Suddenly, the screen lit up and the GDM login screen appeared.
I logged into a shiny GNOME 3 where I am writing these words right now. Ah, and I was also able to connect to the wireless (I made yet another attempt using the network manager applet -- this time it worked).
What does that seem to indicate? That GNOME 3 support is already available for Intel graphics chips? But one may need to play with the nomodeset cheatcode, as I described this above?
I installed Debian Squeeze-testing weekly build today, with CD1 alone. It took 1 Hour 38 minutes to install and configure on my Pentium 4 2.7 Ghz , 1GB ram HP machine. I have some trouble with the installation. Sometimes the desktop just freezes while moving Icons, or opening Xterm. I cannot use Ctrl-Alt-Backspace, OR Ctrl-Alt-Delete keys. I have to physically reboot. Why doesn't Ctrl-Alt-Backspace work on GNOME? Is there a IRC chat for Debian Help and what applications does one use on GNOME for IRC chat?
I just upgraded my system from oS 11.2 to oS 11.3 on Thursday. I've chosen the network-CD and booted from an USB-pen-drive, as my netbook doesn't have a CD-drive.I new experience that my computer freezes obviously randomly. It's not just a programme crashing, but the whole computer just halts. Nothings working anymore - mouse is not moving, keyboard doesn't respond, I can't even switch to another tty.I tried to remember what I was doing right before the crashes. Once I used the new netbook-desktop of KDE and had typed for an application in that "cool" new desktop. The desktop wend "blank" (the application folders disappeared and I was waiting till the results were shown) and then the computer froze. Just right now I used Okular, selected some text and opened the context-menu when the computer died, the other time I closed the Yakuake with F12 and the computer didn't respond just right before the window was minimized at the top and last but not least I had that "Expose"-like window arrangement opened and clicked at the black background when everything hang up.
What could be the reason for it? oS 11.2 worked perfectly - I hadn't had any crash during 5 months of intense use. I suspected the new graphics driver, but I can't find any reported bug about the Intel 945 GMA* or anything about the new KDE 4.4.4 on atom processors.
I have a debian system that's freezing in the boot sequence at "Setting system clock".Several sites I looked at recommended changing the init scripts to disallow hardware access to the clock. But, I can't boot! Is there a parameter I can pass to the kernel at boot so that it will skip init scripts?
I have recently installed Ubuntu 10.04.1 lts server on my Intel "fakeraid" (software raid) (2x250 sata).To test my RAID 1 I turned off one HD and start the system.The first screen (Intel software screen) show Status = Degraded, but the system starts normally with just one HD.Then I turned off the system and turned on the HD again, so the first screen (Intel software screen) shows Status = Rebuild. If I enter in the software raid panel the folowing message is showed: "Volumes with "Rebuild" status will be rebuilt within the operating system"The system starts normally... but this message status stays permanently even I restart the system again
I've been dual booting 10.10 with Windows7 for about a month. Today is the first time I've encountered a serious problem.
This morning, nothing functioned properly after trying to open several programs. The computer seemed to be "frozen", although the mouse was working fine.
I decided to reboot, but then encountered an even bigger problem.
It failed to boot and got this message: no init found. try passing init= bootarg
The problem now is that it requires a Live CD session and I keep getting this: GLib-WARNING **: getpwuid_r(): failed due to unknown user id (0)
In case it matters, I didn't install 10.10 from an ISO, I just upgraded from 10.04.
Ubuntu 9.10 will not boot! System froze this morning, I restarted and it is now failing to boot. Starts loading grub and I get this message:
mount: mounting /dev/disk/by-uuid/04aa3697-7bc0-45b5-b86a-77a1e6534bd5 on /root failed: invalid argument mount: mounting /sys on /root/sys failed: no such file or directory mount: mounting /dev on /root/sys failed: no such file or directory
[code]....
I booted with 9.04 LiveCD discovered the drive could not be mounted-ran fsck -ln and it told me the drive has no valid partition table. I have had intermittent problems mounting flash drives before this, so I'm kind of worried it might be a hardware issue.Also have files on that drive I would rather not lose, so reinstalling is hopefully a last resort.
All open-source fanatics out there like me hate industry and large companies for being on such a high horse all the time. Well, some of us have stooped to their level (towards ubuntu noobs).
after I installed gnome-do and set it to start at start-up, my computer has started freezing right after gnome-do initiates.what happens is I turn on my laptop and log in, and then when the desktop initiates, gnome-do starts and then immediately the prompt window for the login keyring pops up and then my dekstop environment freezes. I can move my cursor around, but when I click nothing happens and the keyboard is unresponsive. the only option is to hard reboot, but the same thing happens all over again. the curious thing though, is that the notification for connecting to a network is perfectly functional and the system monitor continues to record.
I've both tried installing GNOME 3 on Ubuntu 11.04 (via ppa) and Fedora Core 15, but I can't use GNOME shell up to 10 minutes continuously. It freezes every time. Sometimes I see "Panic occurred". My chipset is Intel 915.
When my wife tries to login to her computer, Gnome usually freezes. Nothing in Gnome responds to the mouse or keyboard and all I can do is go to a console and restart gdm. I can always log into Gnome under my username. I am not sure how to troubleshoot this problem. Presumably it is something in the startup apps or a config file. The quick and dirty method would be to create another user and move her data but this would be a lot of work and the problem might come back.
I have a suspicion that it is related to gnome-keyring. This is because (against my advice) she insisted on an automatic login without entering a password. This was a waste of time as gnome-keyring promptly complained and demanded a password. Many times I changed her settings to ask for a login password but it does not always change the behaviour. When it tries to log in automatically without a password Gnome locks up around the time that gnome-keyring asks for its password. The default language for her is Portuguese and mine is English if that makes any difference.
My gnome-panel freezes frequently. Temporary solution: I have added gnome-terminal to my startup programs, and enter "killall gnome-panel" command whenever the panel freezes. However, this is inconvenient especially when the panel freezes every now and then.
Quite interestingly, all icons, menus, and applets freeze including run dialog [Alt-F2], except logout, battery, volume, etc. in the system (applets indicator) tray [time & calendar icon also freezes in system-tray]. I have tried killing all processes related to evolution, but to no avail. someone also suggested removing applets... well, it is not mentioned which applet to remove..
At random times (approx. once a day), my whole ubuntu/gnome interface freezes. mouseover-animiations (for example on the icons in the taskbar) keep working, but clicking doesn't do anything anymore. On the keyboard, tab and arrows keeps working, but most other keys don't do anything. The only option seems to be to reboot. After that reboot everything is fine again (for a while)
Once the freeze happens, it freezes both the standard ubuntu panels but also the program I have open at that moment. It doesn't seem to be connected to a specific program I run.
Is there some log, or anything else that I can use to figure out where these freezes are coming from?
I am on Ubuntu 10.04, and I think I have had this problem since I installed it. When I type my password into gnome-screensaver and click "Unlock," all the buttons become disabled and the cursor turns into the "busy" look. I have to go into one of the virtual terminals and do "killall gnome-screensaver." This happens maybe 75% of the time when the screen locks.
Also, this last week or two there is a new problem where the gnome-screensaver covers only part of the screen and I can still see and use most of the desktop.
Gnome (or XORG, I'm not sure which name to give it) freezes up not always, but about once every 24 hours after I close the laptop's cover/lid. I know this happens when I close the lid rather than open it judging by the time the clock is locked at. The cursor will move around on the screen, but noting will react to it in any way. Other services such as FTP and Samba still work just fine when the computer is "locked down". Without more details to why the problem is occurring, I have no idea what to search for or where to get started solving the problem. I have attached the XORG logs (found in var/log) in case they are of any use.
i had tried to install ubuntu karmic koala and recently unbuntu TLS 10.04 along with windows 7 but every time i login the screen freezes. i dont know the details, my PC consists of a 160gb HDD, 1gb RAM with pentium dual core processor. i even tried knoppix live cd version. is this because ubuntu is installed along with windows?
I have been trying to enable compiz on my fedora 14, but when i enable the desktop effects the graphics just crashes and fedora freezes. When i type lspci -nnk | grep VGA for the graphics card i get:
I made alot of research on how to get Intel graphics work on Fedora, but couldnt find any solution
Firefox 4 becomes completely unresponsive for about 5 seconds. It seems to be happening mostly but not exclusively when switching tabs. At first I thought the problem was flash related but I was wrong, it happens regardless of the pages contents. Also, the problem seems to be more frequent as more tabs are open.It's interesting that it happens only on my computer at work (Intel Q33) but not at home (NVidia GTX 570). Both computers run Fedora 15 with Gnome 3 (HW accelerated). I also tried starting in fallback mode but the problem remained.
I have updated Opensuse 11.3 to 11.4. I have also updated to the latest NVIDIA drivers. Now, when Gnome desktop starts it freezes: it draws all the shortcuts on the desktop but I cannot use my wired mouse to click anything as if the desktop has freezed. The cursor shows that something is loading. I cannot also use Ctl + F2 to start xterm... But I can use Ctl + Alt + F12, so the keyboard is working.
I don't know why but since I upgraded the KDE 4.4 desktop from openSUSE 11.3 to 4.5, the desktop just freezes some times.
If i was listening music, or watching a video I can still hear everything and even move the mouse, but nothing works.
So I switch to TTy1, perform a init 3, then init 5 to restart all the graphic system, and start again. This happens without message, without log, and without clue...
Should I downgrade to 4.4 or this has a Workaround?
I upgraded Ubuntu 10.10 to 11.04 on my IBM Thinkpad T41. [URL]... Since I did this, my gnome desktop freezes constantly after I connected to a wireless lan. It doesn't freeze immediately but a couple of minutes later. syslog gave me the hint that it could be a mistake in loading a module for my intel wireless card. syslog:
Code: Jun 21 14:40:16 BlackBox pulseaudio[1508]: module-alsa-card.c: Failed to find a working profile. Jun 21 14:40:16 BlackBox pulseaudio[1508]: module.c: Failed to load module "module-alsa-card" (argument: "device_id="29" name="platform-thinkpad_acpi" card_name="alsa_card.platform-thinkpad_acpi" tsched=yes ignore_dB=no card_properties="module-udev-detect.discovered=1""): initialization failed. Jun 21 14:40:19 BlackBox NetworkManager[479]: <info> WiFi now disabled by radio killswitch Jun 21 14:40:19 BlackBox NetworkManager[479]: <info> (eth1): device state change: 3 -> 2 (reason 0) Jun 21 14:40:19 BlackBox NetworkManager[479]: <info> (eth1): deactivating device (reason: 0).
Lubuntu 11.04 on laptop (PIII ATI Rage Mobility). Playing a WMV or MPEG file, system freezes when playback ends. I have not tried any other formats.
I looked at mplayer Preferences
In the Player tab, "Video Output" was blank - I set it to "x11"
This corrected the freeze problem, at least the first time that I tried it. However, it did not seem to persist through multiple plays of the MPEG file, whether or not accompanied by an mplayer quit and rerun or a reboot, even though I did not change the parameters. I tried setting vo=x11 in the etc/mplayer/config file, but that did not help. It is sporadic. It will work a few times with the MPEG file, then hang, for no apparent reason. One thing it does seem to do consistently is hang on the WMV file, regardless of the vo setting, and on both files, when vo is not specified (what I started with). This is a time-consuming task, with a reboot on every failure, and I have run out of ideas on what to try next. When it hangs on the MPEG file I noticed that the elapsed time ends up at 20 sec, even though the video total time is 16 sec. When it doesn't hang, the elpased time goes to 20 sec, then returns to 16 sec.
I've read some past issues with this and was wondering if anyone else has issues with F12 / F13.
When I logout of gnome or kde on a fresh install of Fedora 13 the panels disapear but I never receive the log on window. I cannot switch to command either the screen is locked completely.
I havn't run updates or anything, the install is nearly out of box except for the installation of kde.. The issue existed before I installed kde, I was hoping it didn't have this issue lol. fat chance of that..
I`m running openSUSE 11.2, with GNOME 2.28 - made a fresh install.
Everything went smooth and nice, and I did not made any changes to my system, when I saw that GNOME System Monitor freezes when clicking on the "System" tab.
I have configured my system to suspend whenever I close the lid, by using the Power Management applet provided by my desktop manager (see my later comment). However, sometimes, when I reopen the lid, I see that the laptop is switched on but it won't resume, while the CPU heats up. I must shutdown forcefully. What could be causing this?
I have found this thread [URL] .... in regard to OpenSUSE. Is it relevant for Debian as well?
System info: - Debian GNU/Linux: 8.1 - Linux Kernel 3.16.0-4-amd64 - MATE desktop 1.8.1 - GNOME Shell 3.14.4
Clarified that the suspend is a user-level setting.
