I was just trying to get used to everything and I noticed something in the task bar that said you have updates that failed to install (or something along those lines). So I opted to install them manually with YAST2 and during the installation some of the files were failing to download, I was unsure what to do with these files (their was a ton of them, I had to actually sit at my pc for over an hour because I couldn't let it go through on it's own due to all the failing downloads and installs) and so I just decided to skip them, everything seemed to be going along normally. Then my computer froze, so I restarted and tried to boot into opensuse and it kept freezing, (I even went to my brothers house to play the xbox with him for a while) and no matter how long I waited for it wouldn't boot into opensuse. I tried the failsafe mode and it just kept coming up with an error (I probably should have written the error down, I wasn't really thinking about that at the time) and after about half a dozen tries, decided to reformat everything all over again.
So with these failing downloads in YAST2, what am I supposed to do with them? If I retry they just keep failing, so the only other options are abort and skip, am I supposed to skip them or is that what caused this to happen in the first place?
I ran the upgrade from ubuntu 9.10 yesterday and it's now a mess. Is there something I can do to refloat this ship?
The file download stage seemed to be working OK: I was watching it when it only had three minutes left to go. I went away and came back a few minutes later and the screen had gone black. OK I thought, this must be all part of the plan, so I went away and came back over an hour later: still nothing. I decided, perhaps foolishly, to press the power button and boot it up.
Eek! Now I get the following errors:
mounting none on dev failed: no such device
chroot:cannot execute /etc/apparmor/initramfs: no such file or directory
Then the message Ubuntu 10.04 LTS cruncher tty1 and a login prompt. I can log in OK but don't know what to do next to recover the situation.
Rather alarmingly there is some activity on the system: lots of messages beginning with a number like [22.71309.
The 486 kernel works just fine, and while I have only 1GB of RAM at the moment I hope to have 2GB someday and would like to take advantage of the dual core CPU, so I would like to configure grub to run the 686 kernel by default. For whatever reason, it runs the 486 right now and the 686 fails in a major way: there is no network connectivity at all. It could be plugged into my cable modem router and it shows no wired connections. The fact that one works and the other doesn't puzzles me since I haven't touched either since the install and a few rounds of upgrades.
I should mention I'm newbie but getting better; I managed to install debian on this x60, yet while preserving the factory install rescue & recovery partition and preserving the factory install MBR so that ibm-specific hardware functions (thinkvantage button, etc.) still work. This required me to use dd to copy the first 512 bytes of my debian partition to a file in the windows partition, etc., and modifying the windows bootloader. (I wish I had learned dd long ago--it rocks). I did this because if I ever resell the X60, the fact is most people use MS Windows and having that partition adds a perception of value to some potential buyers; not to mention I paid $ for it (I was young & stupid) so why should I delete it. I also backed up the recovery partition on another drive using dd over NFS in case the hd ever heads south.
Anyway, I've never been comfy with messing with the kernel. I did once recompile a module for ALSA because it had a bug in it for an old Yamaha integrated sound card on an old PIII and the newer version worked [alsa fails on this x60 too but I think I found a post on here that has a solution I will try later]. But I'm clueless as to networking modules, not to mention the correct module is installed already from Intel for this chipset. So what is there to do?
Here's a clue: the ifconfig output is radically different from the 686 and 486 kernels. Looks like hardware is not being detected since eth0 fails to show:
I would show the diff output below if it weren't so long--and not allowed--upon 2 text files, the first holding the output of modprobe -l under the 486 kernel and the second under the 686 kernel.
I'm experiencing constant system freezes, and was wondering which log file to view in order to determine what is causing it. I switched over from linux mint as it was giving me the same issues now being experience on my debian setup.
When my system does freeze, the keyboard is unresponsive (caps lock won't even turn on) and I have to use the power button to get out of it. The only thing that does work is my wireless mouse which I can still move around.
I'm having a problem with my Ubuntu 10.10 system. After installing the OS it worked fine. But after one or two restarts it totally freezes i mean NO Ctrl+Alt+Bckspc , NO Ctrl+Alt+F1 and Ctrl+Alt+Del works for me. I have the same problem with Ubuntu 10.04 , 9.10 also. ( Only Ubuntu version 9.04 Works fine for me ). But i want to make use the latest one. code...
After Ubuntu fails some time it crush the GRUB loader, so that i can't boot windows either. Any buddy tell me why this happen to me?
I've try to install Linux Mint 10 also but it freezes while installing..!!
Now I loaded the openSUSE 11.4 milestone 3. It works fine for now but i can't connect to internet , it asks for "linux-atm-lib" . i don't know how to do that .
am starting to get this figured out. finally got the wifi working on a HP touchsmart tx2 laptop and once i give ubuntu a total system shutdown command this system restarts, is this normal or do i need to fix something?
As per the above calculation 81% of memory is used.Is this correct? and if so Am I running out of memory?what is the limit in % that I should maintain for a better performance?
Today while browsing the web and attempting to listen to a mp3 file on the site of a musician, this laptop with Lucid CRASHED badly! It went into a black screen and the only solution was a reboot! I am not a masochist, but I could repeat the crash a couple of times just to verify it.
This is the worst crash that I have seen on GNU/Linux! I expect things to go down in a more controlled way: maybe first the crash of a plug-in, then the crash of a web browser, eventually the crash of a windows manager. But I don't like seeing that playing an mp3 is leading to kernel crash on what is supposed to be a LTS-release!
Any observations of similar behavior or hints on the cause? Is it possible that the crash is related to intel graphics 85x on this system that are now very problematic on Lucid?
By the way, the music file in question is probably not malformed and plays perfectly on Mac and Windows. I am digging into system logs to try to find any record of the problem. For the the record: I've been around Ubuntu since 5.04, on Linux since 2003, on Unix since 1988, and on computers since 1979.
Ubuntu boots fine with wireless turned off via the laptop wireless button on the case, and fine with wireless on but no networks remembered, but as soon as I try to connect to a network, I get the strobing wireless icon in the top panel and then the whole system freezes. It switches to a black screen with a non-flashing terminal cursor in the top left corner of the screen plus a frozen mouse pointer in the last position from when Ubuntu was working. If I force a power-off after this, which I have to, then unless I manually turn off wifi using the laptop button then Ubuntu never boots and I just get a black screen after the BIOS screen. I can connect to the internet via wired connection.
l am failing to do a network installation thru the pxe server. am getting the following error: failure to mount on block on block ..., please append the "root=" boot options.....kernel Panic..Not syncing....
I have (had) Debian Testing running on a 250GB IDE hard drive, partitioned normally.
I also have 4x 1TB drives in a raid 5 using mdadm, and 2x 500GB drives in a raid 1 also with mdadm.
I put the two arrays in lvm using:
I then used "lvcreate" to make storage/backup 300GB, and the rest went to storage/media (approx. 2TB usable). I put an xfs filesystem on both and mounted them.
All was working fine until the system drive shorted out and died on me this morning. As far as I can tell, all my other drives and everything else is fine. I do a daily rsnapshot of the filesystem, which of course is residing on storage/backup (stupid, I know). So I have full backups of everything, but I'll have to put a new hard drive in and reinstall Debian before I can restore everything.
I've reinstalled before and simply reassembled mdadm arrays and remounted them before with no problems, but this is the first time I've used lvm, so I'm not sure what I have to do to restore everything. Is it as simple as reinstalling the system then doing a:
Basically they all cover running a 32bit app running on 64bit host and so on.I want to have an isolated system in total chroot (running lighttpd, mysql, ssh, etc from there).(For security reasons I have to isolate the dev from the live one.) So I installed the chroot environment, mounted all the neccessary things and chrooted in. Everything went fine. Edited /etc/ssh/sshd_config to use port 22222 instead of 22. Used service ssh start then. It says service running but if I try this: ssh -p 22222 localhost I get "Connection refused". The chrooted is system is very minimal so far so there is no firewall, hosts.allow/deny or anything.
ps.: The chroot environment will be a development area as I already mentioned. I thought chroot is the easiest way but if you say KVM is better or something I can go for it. The machine is easily capable of running even 10 VMs easily.
I need to know: how do not automatically restart GNU/Linux after a critical system failure(kernel panic). For some reason the pc is rebooted, actually throws the error screen Reboot just moments before, but I can't to read it before you reboot.
I get a complete system failure when my CPU is stressed. It's not the temperature because when it crashes the CPU temp is only ~55 C. When it crashes the video freezes but the sound repeats itself. Example. I start handbraking a movie, then open a tv show in VLC. This is what I hear.
Did you get that tire - then it freezes
get that tire get that tire get that tire get that tire ... etc
That continues until I reboot my computer. This crash is pretty reliable, as every time I load my CPU that happens. If I don't do anything CPU intensive, I don't get the crash. Also, if I only load up one core of my CPU, then everything is fine. However if I run something such as prime95 or handbrake (which both utilize all 4 of my cores) the computer will crash within 30 seconds.
Ubuntu 10.04 Corsair 750 TX PSU AMD Phenom x4 @ 2.3 GHz 4 GB G.Skill 1066 DDR2 Memory Nvidia GTS 250 1 GB edition Biostar AMD 770 AM2+/AM2 Motherboard Three HDs, two are WD of 1 TB and 120 GB, and a 32 GB SSD.
Been running Fedora for a while now, iterating up through versions to 12. Decided to to a clean install upgrade to 14. Apparently, bug mistake. Everything seems to be progressing fine, but after 'transferring install image to harddrive', the 'Starting Install Process' fails withsystem-config-lvm-1.1.15-1.fc14.narach.rpm cannot be opened.I have no idea what to do with this. I've reburned the install disk a couple of times (and checked the HASH) -- no apparent problems with the install media.Tech details: x86_64 install on a multi-pro box with a 3ware raid 5 controller (5 disk). I've never run LVMs. Two simple hard partitions (/ and /home). Fedora 12 installed with no problems (as did every other version of Fedora <=12).---------- Post added at 12:29 PM ---------- Previous post was at 11:54 AM ----------Some additional information:1 tried Fedora 13 -- wouldn't even recognize my disks. Installer hung at trying to find basic storage. Not a good sign2 tried my old Fedora 12 install DVD -- again, worked like a charm. Expect that F12 repos are now closed.
So, it seems as if some 'change' between F12 and F13/14 has made some part of the install process choke on my 'hardware' (I'm guessing something related to 3ware RAID card). ---------- Post added at 01:51 PM ---------- Previous post was at 12:29 PM ----------I just tried CentOS 5.5 (x86_64). Also installed fine. For some reason, Fedora >= 13 absolutely won't let me get past the problem noted in the OP. I suppose I could go with CentOS (for long EOL support), but I need some of the newer compiler/dev libs in Fedora 14 for some projects I'm working on.
We have a four socket amd machine, running barcelona processors, with 64gb ram.The system runs for extended periods just fine when the system is running up to or below the 64gb memory limit. A typical load on the machine has short periods where the machine uses heavy amounts of swap space (30+ Gb). We have a swap partition of around 96Gb. When we push the machine into heavy swapping, the machine will fail within 24hrs. Has anyone experienced this problem and is there a solution other than buying more physical memory? Or am I wrong and maybe the physical memory is the issue? I thought maybe it was the memory itself, and after stripping the memory down, I get the same problem...failure upon heavy swapping
the power on my street went out overnight, and I came home to a rebooted computer at the command line. I shut it down and rebooted again, also tried the failsafe mode, but it keeps going to the command line. Looked in the BIOS and it didn't see my hard drive settings. But I can see the HD fine when I booted using the live CD (that's how I am able to post here
I'm at a loss in trying to debug a problem I have with my media centre. Basically I'm getting random system hangs and when I say hang I mean proper hang - processor stops dead. No animation, not network connectivity, no keyboard/mouse response, nothing. As for it being random - it has happened during movie playback, during idle, after being up a short time, or a long time, it doesn't matter, so it can happen any time really. The logs show nothing suspect, except they just stop and there is nothing common between the logs of two failures. It happens on both my 'old' ubuntu 9.04 partition and on my new 10.04 partition.
I recently installed Lynx 10.04 amd64. Twice now, my entire file system has become unusable -- each time after a short power outage (2 seconds).
In the first setup, I had two primary partitions: 1) / that was ext4; 2) /home that was ext4.
In the second setup, I changed the /home to ext3.
Both times, after booting up following the power outage, I received a message saying that "serious errors" were found in /home. But, after several reboots, I was able to login and use the system. Then, some time later, I would started getting "Read Only" messages when trying to write to the file system.
fsck gave the following message: "/home terminated with status 4". I received numerous "I/O error" on sda messages.
My question: Is this vulnerability due to using ext4 or is it related more to something else in Lynx 10.04? Further, what can I do (other than buying a power backup device) to avoid my file system becoming unusable after a power outage?
I recently had to restore my system via clonezilla due to hdd failure. I frequently back up my /etc/apt folder as well as some other configuration files and settings that I use in my system to bring my restored image up to date with my ever changing preferences, etc.
I noticed the problem when I replaced the etc/apt folder with my backup version. After replacing the folder, I ran 'sudo apt-get update' and imported a list of all my previously installed software. Then I ran 'sudo apt-get upgrade'. I didn't get any errors at all during any part of the update and upgrade process.Then this popped up in my panel, and won't seem to go away.
I'm trying to come up with a startup init script that will check to see if the system was shut down gracefully, or if it is rebooting from a poweroff or something similar?Anyone know of a way to check for this condition with the least amount of room for false positives or vice versa?My intial thought is just a startup script that will will check for a file on startup, and on a proper reboot/shutdown just touch the file. But id like to avoid that type of script if possible,
I am using Linux operating system fedora 6 .Before today everything is going well. But today internet connection gets failed. It can not connect to the server for the internet connection. But in the same computer,installed windows operating system shows the internet connection.Please try to answer my question why the Linux operating system can not connect to the internet?
An error occurred during the filesystem check. Dropping you to the shell; the system will reboot when you leave the shell. Warning -- SELinux is active Disabling security enforcement for system recovery Run 'setenforce 1' to reenable
The situation is I removed the ADSL card from my desktop as I have no use for it for the moment. I am guessing that the motherboard is still trying to detect the Sangoma ADSL card. What is the best way to resolve this problem, uninstall the drivers for the ADSL card or change the settings in the system configuration files?
The system is not affected by this removal, just get prompted regularly about this error as configured in the kerneloops client.
Debian 5.0. Lately after login following warning popup;Your system had a kernel failure
There is diagnostic information availiable for this failure. Do you want to submit this infomation to the www.kerneloops.org
-> Yes
$ uname -aLinux vm0.debian50 2.6.26-2-686 #1 SMP Wed May 12 21:56:10 UTC 2010 i686 GNU/Linux
Reboot to old kernel 2.6.26-1 the said warning doesn't popup. Reboot again to kernel 2.6.26-2 and after login no kernel failure warning popup. I did it twice. IIRC I encountered this problem before.
I have a flash drive that I regularly use on my laptop. If I unplug the flash drive without first unmounting it, I get a popup notification of a kernel failure (with diagnostics sent to kerneloops.org). Then, if I attempt to shut down the system via the console, it hangs on "The system is going down for halt/reboot NOW!" and doesn't actually shut down. Using Gnome's graphical System > Shut Down feature just logs me out and sends me to the login screen; the shutdown feature from there does nothing. I have to disconnect the power cord on the laptop in order to shut it down, and I don't like doing this.
System: 32-bit Debian Squeeze stable with kernel version 2.6.32-5-686, running Gnome 2.30.2, on an Acer Aspire 5570z.
I use Keepassx to store my passwords and keep the keyfile for my password database on the flash drive in question. I mention this just in case it helps determine what's causing the failure.
