I'm having an issue with a PC ( Gateway GT5220 ), with Ubuntu 64 bit 8.04 installed. There was Vista originally installed in it.
Now, every time I execute shutdown from GUI or command line, the PC reboots and never shuts down on its own, I have to keep pressed the power button for a few secs to power it off. It's very irritating and I don't know wether it's a Ubuntu or a BIOS issue.
i just bought a new computer today and Ubuntu 11.04 reboots whenever i try to shut it down. Most of the time it just hangs there. I've tried to ALT+CTRL+F2 and shut down with the terminal there by "sudo poweroff" but the system freezes and hangs at that screen, not allowing me to see what's going on. If i leave it for 5 minutes or so in that state, it'll reboot. I've also tried Lubuntu, Kubuntu and Xubuntu and they all have the same issue. I've tried their latest versions.
I've searched endlessly, i've messed with the BIOS settings and nothing. I've added "acpi=off" and "acpi=forced" and neither worked. The only way i can shut down my computer is by holding the physical power button.The computer is an HP P6710F. AMD Athlon II 640 x4 processor. ATI Radeon HD 4200 graphics card. 4GB of memory. 1TB of HDD space.
Offlate I installed F11 i586 on my laptop. F11 shares the hard disk with Vista Home Premium 32-bit. The problem is that when running F11 (or even Ubuntu), my system shut off suddenly(not a normal OS shut down, but a sudden power off without any warning). This could have been a hardware trouble(heating) but it doesn't happen with Vista.
Machine specifications:
Maker: Toshiba
Model: Satellite L305D-S5881
AMD Turion X2 Dual Core Mobile Processor RM-70
3072 MB 800 MHz SDRAM
I don't want to open up my machine unnecessarily, if it isn't a hardware issue.
I am not sure how to verify the bit length of the machine and the OS and does it create a compatibility issue ?
Your advise would be highly appreciated.
Raman
I installed Fedora 12 and after I wantd to shut down the system. I waited but fedora not going to shut down. I got black screen with Power Down
View 7 Replies View RelatedI have a 10.10 machine where it has taken to refusing to logout of one specific user account. When I choose logout/restart/whatever from the possible options, it takes me to the main login screen (with the drums) and it shows thet that user is still logged in. The only way, once this occurs, to rid myself of this is to sign in as an administrator and run shutdown -r 00 under sudo. Then it reboots. (Using the admin account to choose restart/shutdown also returns me to the mail login screen where that unpriv'd user is still logged in.) (The machine is fully up to date.)
View 4 Replies View Related24" intel iMac , 4gb ram, fully updated.
I have installed amd64bit 10.04 for some reason the system will reboot without warning. I can not see any issues that point to any major problems in the logs.
All hardware appears to be working well although i have not yet tested the built in web cam.
Are there any extra debug log settings i can switch on to try and track down whats causing the reboot.
Prior to this version of ubuntu my laptop (an old P4 gateway) shut down just fine. It acted fine in windows xp, and ubuntu 9.04, 9.10, and 10.04. Starting with my first shutdown after upgrading to maverick (as opposed to a fresh install, which is what I've done for every time I went to the new version before this), it just reboots the computer instead of shutting down.I've tried clicking the icon in the corner, I've tried pushing the power button and clicking shutdown on that screen, I've even tried shutting down from the command prompt, but each of these just reboots the computer.
View 1 Replies View RelatedI am trying to write a script to add to crontab that I can use to auto update my system a couple times a week.I've done that much before, but I want to make the script a bit smarter about rebooting. Before I had it reboot after running the "apt-get upgrade" command, regardless of whether it needed to or not. Easy peesy stuff, just a sequential command using "&&".What I would like to know at this point is how I can have the script look to see if the reboot is even necessary. I am assuming there is something I can tell the script to look for in an if statement, but I'm not sure what or where. Can anyone point me in the right direction for this?
View 7 Replies View RelatedI have Mevarick's problem with suspend. When i do suspend on SONY vaio fw31e screen goes black but when i press any key it won't suspend. It boots like i just turned it on.
View 4 Replies View RelatedEverything was going great earlier today when suddenly, my PC on a fresh boot, gave me a message that said something like "Ubuntu is running on low graphics mode ..". It was running a low res, i think it was 640x480, and gave me some repair options like a. Boot in low res mode for just one session b. Trouble shoot this error etc..There were 3 more options but i don't remember what they were.
i chose "boot in low res just for this one session", but it gave me the same error the next boot. Then i tried troubleshooting, which didn't work (restoring to a backup config was no use). Then finally i rebooted and started Ubuntu in Recovery mode, and i did something like "Fix broken packages" because , from the list of options it seemed like the only one which would help at that time.
But now, whenever i choose the Ubuntu option after starting my PC, it just restarts my computer. My other OS is Windows 7 which boots just fine. Hope someone can help me with this . In the meanwhile i'll try making a new MBR or something.
I downloaded and installed Ubuntu desktop on 9/26/10. Not sure what version that would be but that is my download date. Running a dual boot XP 32bit/Ubuntu 64bitNo problems at all so far and I've been keeping up with updates manager. Two days ago I went start my machine and chose Ubuntu from the OS selection screen as usual. The only thing that shows up on the next screen (grub menu I believe?) is "HD (0,0) NTFS5" for about 1.5 sec and then reboots.
Windows boots and runs fine. They are both installed on the same physical drive. Not sure what else to search for or include for information. I've tried searching the forums but not sure what nomenclature to use.Trying to avoid reinstalling. p.s. I knew I was enjoying Ubuntu but didn't realize how much until I was forced back to using just XP.
I installed Ubuntu 10.10 on my computer from a USB. I did not use wubi to install ubuntu. The computer already had Windows 7 installed. According to gparted, Windows 7 is installed in sda1, linux swap space is in sda2. Then sda3 is shown as a drop down menu containing sda5, where linux is installed. A picture to show this is attached . sda4 is a recovery partition that came with the computer.
The problem is that Windows 7 sometimes boots, and sometimes it does not boot. Most of the times it does not. Ubuntu boots perfectly. The process to boot is the usual, turning on the computer, wait for grub to load. If I pick Windows, it goes to the splash screen (which is by the way not the usual windows 7 splash screen, it resembles more the vista splash screen, picture attached. I do not know the reason, and I have no idea if it has anything to do with the problem) About 80% of the time, it simply reboots a few seconds after the windows splash screen is shown. The reboot takes me back to the usual HP splash screen, then grub again. The other 20% of the time, it boots normally and works perfectly well.
Right after I installed ubuntu Windows was shown in grub as installed at sdb1. I updated grub and now it is shown as sda1. I already tried some grub custom entries for loading Windows differently, but they all present the same problem. Please do not discard a custom entry as a solution, as the source I used for these custom entries was not entirely trustable.
I also tried popping in the windows installation disk and trying a system repair, but apparently no errors were found.
Reinstalling grub using Ubuntu live cd (booted from a USB) did not work either...
I've been trying to get Ubuntu on my computer for months now and after having googled no relevant cases which may help me I would like some help.
I am trying to install Ubuntu on my computer (which already has windows and I don't want to lose it yet)
I have already burnt 3 CDs yet the problem is the same each time, that's why I believe the problem does not come from the burning. I checked the md5sum and there was no problem.
However when I try to install Ubuntu (or sometimes during a live session) after partitionning my computer and selecting mounting points, having "format" checked on the concerned partitions, the installation goes halfway through the "copying files" process and my computer simply reboots. More precisely, in the middle of installation the screen is replaced with the loading page of Ubuntu (like when you start with the live CD) then my computer reboots, no questions asked (not even to remove the CD, it reboots with the CD in it... while during a manual shutdown it would open the tray and ask you to close it)
I keep having issues at the main password screen. The computer starts, I click my login name, type password, start to hear the music, screen distorted, then reboot. Sometimes I have to do this up to 20 times before it finally logs in.
I am running a Biostar U8668-D Motherboard with 1gb ram. Video is onboard. I am not sure what type. I think it may be S3 Pro Savage.
Since I know there's a lot of support threads going, I wouldn't ask unless I was really stumped and couldn't google. I'll get right to it.
10.04 fresh installed fine, working, few reboots, all good. Installed Nvidia 195 drivers. Not so good, still works fine, but framerates not as good as the 190 drivers I'd been using with karmic. So I installed nvidia-glx-190 and nvidia-190-modaliases with the nvidia PPA for jaunty. They didn't appear on the restricted drivers list, I rebooted in the hope they would, and now my boot process is as follows.
Boot, met with a blinking _
Goes blank
Another blinking _
Green static appears momentarily, then very fast the Ubuntu splash appears, the white orbs all turn orange, and there it hangs. The splash itself is in the wrong resolution.
Everything is the same as when it was working except it didn't totally freeze at the end. It responds to nothing except the power button (and sometimes not), I can't access a shell or the grub menu at any stage during the boot process like I usually would, and nothing in the boot log seems out of the ordinary.
What should I do? I'm on a LiveCD desktop, got the harddrive mounted.
Macbook pro 4,1, 2GB ram, Core2duo with Nvidia Geforce 8600GT
This happened with 09.something and again with 10.04. When I plug in my Palm Centro smartphone, it starts endless rebooting. I solved it last time by removing modem-manager from /usr/bin.But that program didn't reappear through my upgrade.
Well, when I first upgraded, then plugged in my Palm through a USB cable, the phone rebooted. Then, I was able to sync to JPilot. Attempting the same thing later, the phone rebooted continuously.Today, I seem to be able to sync again.
Whenever I select windows 7 from grub it will boot up to the splash screen and then restart.I do NOT have a repair cd.
View 3 Replies View Relatedwhen I select Vista/Longhorn from my grub list, it shows a black screen, then shows GRUB again. I recently had to reset my menu.lst, so I'm not sure if the settings for the windows option are correct. This is my /boot/grub/menu.lst:
Code:
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
[code]....
I was wondering if there was a script that would run on log in telling me the history of when the server was rebooted or such, along with the last user and motd (which is a roflcopter in my case)
View 8 Replies View RelatedI'm trying to install Ubuntu 8.04 on my pc but every time I select an option to install from the cd, the pc reboots and I go through the same thing again.
I've tried installing within windows but that just installs a folder with Ubuntu in but I can't start Ubuntu up when it's finished installing?
I've been googling my brains out looking for a solution to this. So far, nothing.
As the title suggests, every time I attempt to shut the computer down it instantly reboots the moment the internal fans stop whirring.
So far I've tried:
-shutting down via the terminal (this actually makes the reboot happen instantly rather than waiting for the fans to stop)
-looking in the BIOS for any obvious settings which may be causing this
-performing a dpkg repair
-Allowing "Proposed" updates in the Updater
-installing (slightly) older Kernel (2.6.35-22 as opposed to 2.6.35-23)
-installing newer (2.6.36) kernel
I know others are having this issue, but other threads I've read seem to have fizzled out with no conclusion. Has anyone managed to find a way to make this work if they've had the bug?
Any advice at all? Is it worth trying an even older kernel? Or an even older version of Linux?
I've installed Ubuntu inside Windows 7 with the Ubuntu Windows installer. I have previously had problems with booting Ubuntu, but it always got to GRUB at least. Now it shows the Windows bootloader, I select Ubuntu and the computer just reboots.
View 4 Replies View RelatedThis is a strange one. Ever since upgrading to 11.04 64-bit, I've had this problem and I've just been dealing with it...
After the machine posts, grub presents itself. Before upgrading, it would timeout after 5 seconds and boot the first/default entry. Since the upgrade, it no longer automatically boots the first entry. In addition, it reboots the computer after selecting the first entry. After it comes back up to grub, you select the first option and this time it boots.
I'm pulling my hair out on this one. I'm by no means a Linux expert, but I've been running Ubuntu for a few years now and this is one of the first issues that I've been unable to work through.
Can't boot the x64 version of the official install DVD or any mini-image from Alien Bob. Either way, the computer reboots a few seconds after loading the kernel. Running 13.1 x64 on the very same hardware right now. Edit: this system ran Slack 100% stably for about a year, and Ubuntu for a few years before that. I am using it to write this, and have no reason to suspect any kind of hardware failure. memtest passes.
I managed to snap a picture of the screen just before the reboot, here is the end:
Code:
Just as reported by AlleyTrotter below, every installation media I tried for 13.1 hangs right after loading initrd, and every installation media I tried for 13.37 rebooted with the message posted just above. I havent tried all the combinations (official, alien, DVD, CD, x64, x32, USB, PXE), but I tried a lot of them, all with the same consistent results.
I have 4G of RAM, and the workaround provided below by AlleyTrotter (booting with huge.s mem=3700M) worked. That is to say, I booted from the official x64 DVD and was able to log in as root, and everything seemed OK. I did not try to install, though, since I already successfully installed a minimal system from 13.0 media and then upgraded directly to full 13.37. Once again, my system is Dell XPS 630i. I see no reason to post other system specs since I don't know what exactly is at fault.
I have been using grub2 experimental from fzielcke's ppa. I tried to use the gfxmenu by modifying grub.cfg downloaded from grub.gibibit.com and overlaying the overlay file from that website. When I rebooted by laptop, it shows the graphical menu for about 1 to 2 secs before rebooting my laptop. Has anyone else experienced the same problem (and maybe found the solution)?Alternatively I also tried to download the source from grub's experimental branch. Everything went smoothly until I issued the make command... It is missing some files e.g. loader.S (an include file for ~/experimental/kern/i386/pc/startup.S). Can anyone help me obtain the complete source files for the experimental branch?
View 1 Replies View Relatedi wanted to know what script i would put where that would tell me the last 5 times the server rebooted whenever i logged on.
View 9 Replies View RelatedI have used ubuntu 8.04 in a dual boot system together with windows xp and wanted to upgrade to ubuntu 10.04.
Since the upgrade did not work (the usr partition was to small and I couldn't make it big enough) I downloaded the ubuntu-10.04-desktop-i386 edition and tried to install it.
Everything worked find during the installation process but when I tried to start ubuntu I could only see the ubuntu desktop for a second and then the computer began to reboot.
Then I thought that I can solve this problem by installing ubuntu 8.04.4 again and trying to upgrade to ubuntu 10.04.
After the installation I could start ubuntu 8.04.4 without problems but after upgrading to ubuntu 10.04 the same problem occurs again: ubuntu 10.04 causes the computer to reboot every time I try to start ubuntu.
I installed Ubuntu 10.04 LTS x64 on my laptop about a month back and I have been very, very pleased with its maturity and stability. However, I have seem to have hit a snag with my ventures into desktop Linux: I also dual-boot Windows 7 Professional x64, and it seems that every time I run Ubuntu 10.04, Windows 7 will immediately bluescreen on boot, reboot, and then be fine. I'm not sure what kind of harm this could be doing to the system, but it strikes me as very odd, and it's something I would like to resolve.
I have suspected this may have to do with mounting NTFS drives under Ubuntu, because my Windows OS and all of my media is stored on NTFS partitions. Needless to say, I would really rather not change this, because NTFS seems to be one of the few filesystems with large-file-support that will run with ease under Windows and Linux.
I have tried removing my main Windows 7 OS partition from the fstab in Ubuntu to see if that made any difference, but the problem persists. Could a secondary NTFS media partition mounted in Ubuntu really cause these sort of issues?
Just a random question out of curiosity and probably ignorance. But why have updates started requiring a reboot almost every single time recently? I'm using Lucid, but the rate of required reboots was already on the up in Jaunty. As far as I understood, you should only really need to reboot if something's been changed in the Kernel - is that wrong?
Surely the updates can include restarting of demons or just the software if need be, it's starting to become like windows in this respect....
A weird problem arose a few months ago in my box and has plagued me ever since: the PC immediately reboots whenever I try to suspend or hibernate Ubuntu. It's actually instantaneous, as if I pushed the reset button.Way more days into googling than I wished I had to, I have tried just about every solution related to suspension/hibernation problems,but none really applies to the exact situation I'm experiencing, since most are about being unable to resume after suspending/hibernating, and in my case it seems the system is instantly killed and therefore doesn't even start said operation.
After rebooting, applications behave exactly as when the PC is hard-reset, which I think is an indication that running processes aren't being properly terminated and the system is just going down abruptly (if the less-than-a-second it takes to go down and restart the boot sequence isn't obvious enough).Before you ask:
everything was working fine before;
upgraded to Maverick but the problem remained;
every suspend/hibernate method that I know of (GUI, CLI) does the same;
can't easily test in another OS since I only have Ubuntu installed (no dual-boot or the like);swap partition is larger than RAM; /etc/initramfs-tools/conf.d/resume is pointing to the correct swap UUID;
tried several SUSPEND_METHODS and video-related options in /etc/default/acpi-support;
enabling/disabling the acpid and acpi_support services in BUM (Boot-Up Manager) has no effect;
enabling/disabling BIOS STR (Suspend-To-RAM)-related options has no effect;
unsetting NvAGP or setting it to 1 in /etc/X11/xorg.conf has no effect;
adding/removing the agpgart and intel_agp modules to /etc/modprobe.d/blacklist.conf has no effect;
installing the hibernate package has no effect;
not sure what I'd be looking for, but nothing strikes me as relevant in /var/log/messages.
This is really strange. May it be a hardware failure of some sort? What else can I try to work this one out or at the very least understand what's happening?