Ubuntu Installation :: Uncompression Error - System Halted On Fresh 10.10 Install
Oct 14, 2010
I'm trying to install 10.10 64bit on a DFI X48 mainboard with 8Gb RAM, I've tried installing from the Desktop CD, Alternate CD and USB stick, but all attempts fail with
-- System halted
I've run memtest86 and the RAM passes OK, I've even tried running the install with just 4Gb RAM but without any luck. I've even tried three different CD/DVD drives.10.04 64bit runs from the Live CD without any problems, but 10.10 isn't playing ball...
Since yesterday my computer behaves really strange. I fear it's a hardware issue. At most I did some minor updates, but no big software or OS change.
When I turn it on it goes immediately to [url]
I guess it reads
Code: Chasis intruded Fatal Error... System Halted.
So this happens before the boot manager... When I press the reboot button it goes to the boot manager and works seemingly fine - all I noticed that it doesn't remember the time, or better remembered the time form the last usage but doesn't count it forward. While using the time seems to pass in a normal speed.
What could this be? Some chip on the mainboard broken? Some BIOS virus (does something like that exist?) Or maybe just a cable which got lose?
I don't know which other informations could be helpful. I built it myself some years ago and the parts are pretty random (back then I didn't even know about linux compatibility nor used it at all). I have a dual boot with openSUSE 11.2 and windows xp, but the network card is deactived in xp for a year at least already.
I using an old 1999 PC 512 MB RAM used to have W-2000. I had difficulties getting CD to be boot drive. I had to remove floppy drive to stop it from being the first drive. I'm using the Linux Starter Kit with Ubantu Live 9.10. My PC was having issues so I skipped the dual boot and went straight to a clean install. I had to double click on WUBI in the disk directory to get the install started. Install appeared to be going fine about 60%... then I got distracted to fix lunch for sick kid. When I came back screen was black and I could not wake up screen with mouse or keyboard. I turned off PC.. restarted and have message that says NO ROM BASIC System Halted.
After a fresh install of Debian I came across an error Im hoping you guys can help me with. Ive searched for the error and it appears there are multiple reasons that could be causing it. To compound the problem, Im at work so I dont have the specific error messages....so I just installed Lenny (standard install, no desktop) using a USB installer and everything went very smooth. On first boot, the system paused while waiting for the root file system. After a minute or two it just errored out complaining it could not find the root file system and put me at a (vmlinuz) prompt?My guess is that I need to go into my bios and change my boot priority.. but again, thats just a guess.
After upgrading to a new kernel (via an official update from Ubuntu) today, my computer will no longer boot properly. After rebooting to apply the update, my system ran its scheduled disk check (I think it's set to every 30 mounts or something like that). Errors were found and, as the message said, I "[Pressed] F to attempt to fix the Errors." They were fixed. Re-checking now in Knoppix reveals the file system is clean and it is, in fact, mounted as I post. After leaving the computer alone for a while to check, it seems that it had rebooted without my intervention. It's a laptop on AC power and with a full battery so I ruled out a power interruption, but the screen says:
I figure "Ok, new kernel has an issue, I'll boot from one of the backups." I boot from the two previous versions (2.6.32-23 and 2.6.32-22) and both error out with a Kernel Panic and complains:
Code: Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0).So now I'm stuck with the prospect of backing up all of my data (a lot) and returning my computer to factory settings (Ubuntu 8.10) and re-upgrading or re-installing from scratch losing some of the Dell-supplied software.
The system asked me to reboot and I just shut down the computer.Some hours ago, I wanted to start the computer and the system halted after the first logo showed of Ubuntu, after 15 minutes waiting, nothing happened. I tried to push keys on the keyboard, nothing helped (I even couldn't put on CAPS or num lock on the keyboard).After a secoind reboot I didn't even saw the Ubuntu logo. When there's a black screen, it just sits there.I have no idea if there was a kernel update (I assume there was, because the system wanted me to reboot)
I have an odd problem. I custom-built a workstation: MSI Speedster 1 mobo 2x Opteron 2352 4x DDR2 ECC 4GB 3x 150GB WD Raptor, hardware RAID 0 1x 2TB WD Green, standalone
I had Linux Mint 8 installed, but before putting the machine to real use decided to toss Windows 7 on there to see how it worked. Now I am attempting to put Mint 8 back on to get everything set up. There have been no hardware changes since I had Mint installed before.
I can successfully install, but when I reboot I get a Grub error 17. The partition table looks like: 50GB / ext4 400GB /home ext4 ... 2TB /backup /ext3
Grub is installed to (hd0), which is the 450GB hardware RAID. It does not make a difference when I run the installation (and then reboot) with the 2TB drive disconnected. Thinking maybe the new ext4 format was messing with Grub, I tried: 200MB /boot ext2 50GB / ext4 400GB /home ext4 And installed again and rebooted. No dice. I'd guess Grub has issues recognizing the hardware raid, except it worked before
I have a dual boot machine (Win XP + Ubuntu 9.10 on separate physical drives) which was working fine. I now want to replace the Ubuntu 9.10 with LinuxMCE which is based on Ubuntu 8.10. Using the LinuxMCE install disk, I did a fresh install of Ubuntu 8.10 over the top of Ubuntu 9.10 (repartitioning the whole drive). On reboot, I now get a Grub "no such disk" error. I have run the boot info script which produced the following RESULT.txt:
Code: Boot Info Summary: => Grub 2 is installed in the MBR of /dev/sda and looks for (UUID=6a59ab9e-041f-41e2-b27c-02b8ada4c1af)/boot/grub. => Grub 0.97 is installed in the MBR of /dev/sdb and looks on the same drive in partition #1 for /boot/grub/stage2 and /boot/grub/menu.lst. => Windows is installed in the MBR of /dev/sdc
This is my first linux install, Fresh install of Ubuntu 10.10, and first thing I do is update. I can't update because I get this message "The package System is broken Check if you are using third party repositories. If so disable them, since they are a common source of problems.
Furthermore run the following command in a Terminal: apt-get install -f"
This a brand new fresh install, how can there be problems already!?
In terminal I've tried " apt-get install -f" and get "E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied) E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?"
I have a somewhat old box that I want to install 11.04 on for experimentation. Eventually I'll want to run server and LVM, but for now I'm just going for simple. The box is an AMD 4800+ with 3 SATA hard drives. It previously ran Windows, but I've made every effort to blow all HD contents away and start fresh.The big picture problem is that I can't reliably get the system to boot from the SATA drives. After my first install of the 64-bit 11.04 from CD, it installed OK and booted fine. I then subsequently reinstalled the next day and the troubles began.
I've been booting into the "trial mode" from CD, then attempting to reinstall from there.After getting all the way through the setup, it gets to the grub install. It says that it can't install grub. It then offered to install it on the other /SD'x' devices (/SDA, /SDC, etc...) but failed to install grub there as well.Thinking there may have been leftover state from a previous install, I've tried blowing away all the contents of the 3 hard drives. However, I can't do that either. Running the "disk editor" from within the "trial" mode, any attempt to erase a partition is met with a failure, with the error message "daemon is inhibited".
So the two big questions I have are:1) Why is the grub install failing, and how can I deal with it?2) Is there some expectation of what the drives look like prior to an install? And if so, how go I get them into that state? I'm lost on how to "uninhibit the daemon"If it's helpful, I grabbed the relevant section of the log file that has what looks like more detailed errors from the grub install.
The computer went into low graphics mode all by itself and then later threw a error that said incompatible processor system halted!the computer was getting really slow and made alot of noise.later the computer did something stranger..it restarted but normally when my computer normally restarts it bypasses the password page setup in bios of the computer. This time I still had to enter a password before it could reboot.Another thing...when it the ethernet cable was connected to the computer (internet connection was on) it was slow when it was unplugged it was not.I have read that unless you're running a server or something it is highly unlikeley you'll be hacked.
I tried to update one of my home machines with a fresh install. This is far from new to me so I did not expect any problem. But I was proven wrong. First: did install the system as usual. First anomaly: system blocked during the install process but did restart it flawlessly one I tried to eject the DVD from the player. It needed actually that intervention to retake working. It then went to install and froze during the first system start. I rebooted with failsafe settings, it then correctly configured. I reached a beautiful desktop. I performed the updates from the update repository and I joined the nvidia proprietary driver repository (which updated to the G02 driver).
I then rebooted the machine and now I am in trouble. In normal mode the system (dual boot Opensuse, XP) does not boot at all and freezes immediately after hitting enter as before. In safe mode it goes further but does not reach X anymore. It blocks with the following line statement: "system console stolen at line 266". I then tried "startx". But the system goes into a scrolling loop that does not allow me to read the output. how to get at least the error message of the loop? I read some line passing by that the system might have an X11 authorization problem.
Athlon Phenom X4 905e Nividea G7600 graphic card Former system installed and running flawlessly: 11.1
I've just upgraded my wife's netbook to UNR 9.10. This seemed to go well and the netbook has been working fine since. Yesterday my daughter used the netbook with out any issues, but when my wife tried it halted during boot with:
Swap waiting for UUID: xxxxxxxxxxxxxx
After a couple of reboots it started working fine, but looking at /etc/fstab the entry for swap is different to the UUID shown in blkid Do I just update fstab with the UUID from blkid?
I have Fedora12 with dual boot WinXP on my laptop. Everything was working fine but suddenly one day I booted up my system and selected Fedora from boot menu , an error screen came - "[...]ERROR: tried to remove a fb that we didn't own Boot has failed, sleeping forever"
I don't know why It's happening ? The last thing I did on Fedora was to install some packages to start Wi fi and It was working fine from last 2 months, then why suddenly this bug ?
I googled about it but most of the cases are of Live CDs or USBs but in my case I had a whole different space assigned in my hdd for Fedora and everything was supercool.
Does it mean I have to do a fresh install of fedora12 again ?
I have had a new install of Karmic from CD and have done all updates and added a few applications like VLC and a few others. I have several different media players, Totem, VLC, Xine, and gxine. I started out thinking Totem might be enough, but added VLC as it can handle just about anything, and then the other just to see of any thing happened.
I have installed all restricted and unrestricted packages from the Medibuntu depositories I can find. Still my laptop will not read any kind of DVD. I am region 2, but have tried both bought region 1 and region 2 DVDs. I had this problem last time I installed Ubuntu, but after installations of a few applications and messing about it suddenly worked. I really didn't know why or what suddenly was working.
Just did a clean install on my desktop of 10.04. Net was working fine, until I installed GIMP and restarted. A little "NO" symbol pops up next to my wireless indicator, and it tells me to either do an apt-get check from terminal or start the package manager to find out what the problem is...so, I do the apt-get check.
Here's what I get returned from the terminal:
E: Unable to write to /var/cache/apt/
E: The package lists or status file could not be parsed or opened.
I just installed the newest version of Xubuntu using the LiveCD, I chose to install it alongside my current installation of Windows 7, everything went well it seemed, but now when I choose Windows 7 under the GRUB menu it just restarts my system and then takes me back to the grub menu, Xubuntu works fine though and boots fine, I tried sudo update-grub, didn't fix it.Heres the boot info from a script I found, but being rather poor when it comes to diagnosing Linux, I figured it'd be best to post this and see
Code: Boot Info Script 0.55 dated February 15th, 2010 ============================= Boot Info Summary: ==============================
Sometimes httpd (the apache web server) fails to start and displays an error (98: Address already in use: make_sock: could not bind to address xxx.xxx.xxx.xxx:80). This happens even when no other service is listening on port 80, as evident from the output of "lsof -i :80" and "netstat -A inet -lnp". This is due to a configuration file mixup. Both /etc/httpd/conf/httpd.conf and /etc/httpd/conf.d/system-config-httpd.conf contain the directive "Listen :80". If you comment out the "Listen 80" in /etc/httpd/conf.d/system-config-httpd.conf, httpd will again start.
I have installed Suse 11.3 on my computer yesterday but since then I have been trying to update it but unable to do so. Everytime I try I get this error message: "system management is locked by the application with pid 6953 (usr/sbin/packagekitd). close this appliaction before trying again."
I have just done a reinstall of Centos 5.3 on a dedicated server (via a KVM). My partition arrangement was the default presented to me by the installer:
As you can see, I'm using LVM for everything other than /boot (I need to use LVM for an app I am testing).
On reboot, I get the following:
It looks like it can't find vmlinuz-2.6.18-128.el5 in /boot.
I have rebooted using the Centos Install Disk 1 and gone in to rescue mode. Rescue mode mounted my / under /mnt/sysimage, from there I could see that /boot had been mounted from /dev/sda1 as it should be.
However, there was no initrd.image or /vmlinuz-2.6.18-128.el5 under /boot or /boot/grub. Shouldn't the CentOS installer have created these?
I have installed Centos 5.6 on a fresh VPS. After install I ran yum update command. After update was finished I noticed a message saying "Your system kernel may have been updated. Current kernel (2.6.18-238.e15) has been changed to : 2.6.18-238.12.1.e15)". When I reboot, I see two boot option in GRUB. one is Centos 5.6 (2.6.18-238.12.1.e15) Default and other is Centos 5.6 (2.6.18-238.e15). When Centos boots from default, it fails with fatal error. But when I boot with other option, the system boots as normal.
I need to know how to resolve this situation. Why yum update results in Kernel update and 2nd option in GRUB boot loader. and why Centos refuses to boot with update Kernel.
I'm trying to run Mac OSX Leopard + Ubuntu on my Macbook White 4,1. I've read multiple user guides, but for some reason it screwed up when I hit the partition button on rEFit. I received the 'gpsync' (sp?) error. I couldn't delete any of my partitions or make them go back to normal... As we speak I'm wiping my hard drive. I would really LOVE to start over FRESH. With Mac OSX, then to install Ubuntu. How can I go about installing Ubuntu on my Macbook without getting the sync error, and screwing up my partitions. Yes I read the user guide, and yes.. I did it step by step and still received the errors. I would love to fool around on Ubuntu, but the errors were stopping me.
I've got a Puppy system running version 4.3.0 that I'm trying to get on the home network. I'm using a D-Link DWA-130 (H/W revision C), which has a Realtek RTL8192U chipset. I got the drivers off of D-Link's website, and they compiled and installed just fine, but when either a) I try to connect to the network, or b) while I'm browsing the web, the system locks up completely. No mouse, no keyboard, no Ctrl-Alt-Bksp to get out of X, nothing.
I'll outline my steps: Install Puppy using a "Full" HDD install (not "Frugal"). Copy the "devx_430.sfs" file (which I got from the Puppy website) from a thumb drive to the "my-documents" folder (although the exact location proabably doesn't matter). Mount it, cd to the mounted directory and execute "cp -a --remove-destination ./* /" and "sync". Copy the kernel source for 22.214.171.124 ("kernel_src-126.96.36.199-patched.sfs4.sfs") to the same directory. Mount it and execute the same commands as before. Copy the folder containing the RTL8192U drivers ("rtl8192u_linux_2.6.0006.1031.2008") to the root directory (i.e. "/"). cd to the folder in the terminal and run "make", "make install".Reboot the machine. Set up networking using the Puppy Internet Connection Wizard. HERE'S WHERE IT SCREWS UP: It connects, but after a while (e.g. just after logging into LQ through it, as a test) it freezes the entire system.
I have to do a hard reboot ("panic button"), then a soft reboot (for some odd reason the usb module won't load after a hard reboot, so the mouse won't work) to get the system working again, only to have it lock up again once it connects to the network.
Are these drivers broken? Outdated? Is there anything I can do to fix this? EDIT: I should add that this only occurs when the adapter is plugged in. If I boot the system with it unplugged, it works fine (probably because it never loads the kernel module).