I seem to be having a problem booting into ubuntu 10.04 (and 9.10 before I upgraded a while back). It's been ongoing for a while now, but I can't seem to actually even get to the login screen. Some kernels just give me a blank screen, and others hang at the ubuntu logo (http://i.cbsi.com.au/story_media/339...ic-koala_1.jpg). It seems to be totally random, and I can't seem to even narrow down which kernels do what. It seems to be a game every time I reboot. Perhaps it has something to do with the beta 2.6.32-rc6 kernel I installed (by clicking on the .deb) a while back? I'm not too sure how to uninstall it, but I first installed it I think back at 9.04, and it always seems to be the first option in grub. Can I clean out my old kernels somehow? Or is that dangerous?
Maybe it's caused by graphics drivers? "Safe mode" doesn't seem to work any better though. And I can't get to the TTY terminals by <ctrl><alt><1-6> either, which would suggest to me that it isn't a graphics issue? I don't see the login screen, nor do I always see the splash screen.
Instaled ubuntu 9.10 and i like it more than win xp because you can setup it in your way. Now my problem is when i compile older kernel with my setup and restart ubuntu i get grub with no loads like config is gone or something so i cant boot any of default kernels. I folowed this guide for compile [URL]... because i want to create lan hlds server with 1000hz kernel and have best response and latency server. can anyone confirm is this guide working with this 9.10 version or problem is that i cant set older kernel with newest ubuntu? Compiled few times and annoyed to wait again 2h just to try some other explanations i found on internet.
yesterday I removed old kernels via. the synaptic manager- I'm 100% certain I did not removed the latest stable kernel, and the version before- I did however removed the oldest two. Now after restart I'm dead in the water- i cant get past the initial boot- the screen goes black. I i'm running ubuntu 9.10 double-booted with windows vista, and right now I cant even get into vista...
Let's say that I messed up with removing old kernels, and removed sth, that shouldn't be removed- but how does this mess up vista?
i'm having a problem with every single kernel upgrade since 2.6.32-21.I'm currently upgraded to 10.10 using GRUB2 and LVM disk configuration and all newer kernels (up to the latest 2.6.35-23) crash with the following errors:/init: .: line 61: can't open '/scripts/functions'Kernel panic - not syncing: Attempted to kill init!Pid: 1, comm: init not taintedI've already double checked all the entries in GRUB regarding paths, etc and i can't seem to find any difference between the working 2.6.32.21 and all the others
My OS boots with 2.6.35-22-generic, if using more new kernels (2.6.38-8-generic, 2.6.38-10-generic and 3.0.0-0300rc7-generic), the system doesn't boot normally: the monitor doesn't light, upper and lower gnome panels are absent. Machine configuration: Acer Aspire 5734Z, Intel Pentium Dual-Core T4500 2.3 GHz, 2 GB DDR3 Memory, videocard Mobile Intel 4(R) Series Express Chipset Family.
I received an alarm on a server stating that the /boot partition was 90% used. The partition contains several old kernels so I removed all but the current and previous 2 known stable versions using apt. This did not purge the files from the /boot partition.The /boot partition still contains the kernel files for 12 old versions. Is it safe to delete these files after the kernel has been removed using apt? Below is the output of the /boot partition.
I'm unable to boot my box since the first 2.6.34 kernel arrived.I hoped the second will fix the problem but it didn't.The display just enters in the power save mode after a second and that's it.The system boots fine with the 2.6.33.8-149.fc13.i686 kernel.The lspci result is:
I just installed Maverick Studio on a new hard drive, and am using an NVIDIA GeForce 7300 LE GPU. If I boot into the 2.6.35-22-generic kernel, everything runs fine, but if I try to boot into either the 2.6.35-20-Low Latency, or 2.6.33-29-Realtime kernels (installed from Synaptic), the computer boots straight to a command prompt instead of the desktop. Does anybody know what causes this? I need to be able to use one of these kernels for doing music production.
Yesterday i updated fedora 13.After reboot problems started with te display driver.Scrolling sreens goes very slow and with little steps.Moving a screen from one side to the other goes also very slow.It seems there is a problem with the ATI driver.I also have problems after new kernel updates.The new kernels simply won't boot? The boot proces hangs everytime the fedora logo turns wite.
lately I compiled the 2.6.35 kernel and met the following problem: the kernel I get it is a generic kernel so I have two generic kernels. I want to have a possibility to boot both kernels: the new and the old one. I cannot resolve the problem of a creating initrd as mkinitrd run for the new kernel would overwrite the initrd.gz generated for the old kernel. So , I make a new directory where I put this new kernel. Is there a way to have both kernels together in /boot ?
I am using a Dell XPS m1330 with ubuntu Maverick 10.10 and with a Nvidia card. Recently I wanted to add plymouth support to my boot screens via this script: [URL].... but maybe i did something that ruined my pc and now, in GRUB, i can only see recovery kernels. The situation is this: in grub i see
linux recovery kernel 1 linux recovery kernel 2 (old one) memtest windows 7
My "normal" linux kernels disappeared. When I want to boot linux I use a recovery kernel, then I simply hit "resume" in the process, do the textual login and than use the command "startx" to start the system. However i'm getting no Plymouth and no normal boot. I have already tried to fix grub recreating the linux kernels, but they just don't show.
how would i go about deleting my old kernel?i have my ubuntu machine partitioned the way gentoo would partition a drive with a seperate boot directory. my boot directory is only 200 megs so i can probably fit 4 kernels max into it and need to eject the old ones.
I'm running Fedora 12 - Linux 2.6.32.21 with a boot partion on /dev/sdb3 of a hard disk.
I downloaded a vanilla kernel version 2.6.35.4 and have built it and run it successfully. I built this kernel to play with building device drivers.
My grub configuration uses the same root filesystem for my fedora installation as my vanilla 2.6.35.4 kernel; both use the LVM root filesystem. (/dev/sd4 /dev/sdb5 /dev/sdb6)
When I'm running fedora 12 (2.6.32.21) I can see the files in /boot which contains my kernel, system-map, initramfs, grub directory, etc. I also see my vanilla kernel 2.6.35.4 and it's associated support files (map, initramfs, etc.)
My question is when I boot into my vanilla 2.6.35.4 kernel and I look in /boot, I only see my vanilla kernel and it's associated support files. No grub, no fedora kernel. If I do a df -a, I see that /dev/sdb3 is not mounted like it is when I'm running my fedora kernel. I'm confused as to what is going on here. Can anyone shed some light on this?
I'm looking for a script that copies a random .jpg from a random folder in my ~/Pictures folder to my ~/temp folder with a standard filename. This file will then be displayed in Conky. I can fix the last part, but I cannot find a way to do the first part.
I'm having trouble with Ubuntu 11.04. Every now and then when my laptop boots into the OS (It's a Toshiba Satellite L10) I get a weird desktop layout, that I have never used before (it has happened a few times though).
After upgrade to 10.04, my disks are randomly named (sda, sdb, sdc) at each boot. My drive labeled "XP" is sometimes named "sdb" and sometimes "sdc", while my other drive "DATA" is respectively "sdc" or "sdb". This wasn't the case before upgrade with KUbuntu 9.10.
Due to this random naming, my auto-mount in fstab often fail at boot time !
Any solution for this (not found here by myself) ?
Is this linked to Grub troubles reported many times here ?
Not having a good night. Typing away on some code and load & run my latest changes in chrome, mouse starts lagging and system slows right down, ok maybe it's a bug in chromeI close chrome, try to get to a terminal to kill processes, no luck, go away for a while and come back hoping it sorts itself out, still frozen so I reboot.Now I get a horrible crash almost immediately on boot with a bunch of cryptic numeric error codes then:
Begin: Running /scripts/local-bottom ... mounting /dev on /root/dev failed: no such file or directory
I have a Raid0 setup (see below for details) connected to the ICH10R raid chip on my Gigabyte EX58-UD4P motherboard. On every second og third boot I get the following error:
Code: udevd-work[157]: inotify_add_watch(6, /dev/dm-1, 10) failed: no such file or directory udevd-work[179]: inotify_add_watch(6, /dev/dm-1, 10) failed: no such file or directory The system halts for a seconds or two and then boots on like nothing has happend.
My setup is as follows:
Two 500gb discs in Raid0 on the ICH10R. The first partition 100 mb is a Windows 7 system partition (gaming etc.) and then a 300gb partition for the actual Windos install. Then Ubuntu 10.10 with /, /home, /swap and then five data partitions. Grub is on the Windows system partition.
Ubuntu 10.10 x64 installed via USB. No problems during install. Besides that I have 2x300gb dics on the Gigabyte built in raid controller. Installed with a Hackintos setup using Mac software raid.My fstab looks like this:
Code: # /etc/fstab: static file system information. # # Use 'blkid -o value -s UUID' to print the universally unique identifier # for a device; this may be used with UUID= as a more robust way to name # devices that works even if disks are added and removed. See fstab(5).
I am using Ubuntu Lucid Lynx 10.04 (64 bits) in my Asus U30JC laptop (Core i3 M350, intel 4500MHD + nvidia 310M with nvidia Optimus, 4GB RAM). I am content with Lucid and I don't want to upgrade to 10.10 for now. However I read that the new 2.6.36 kernel has some good improvements, such as improving system interactivity while intensive I/O (such as copying large files), and improved energy management for i3/i5 processors (which I hope translates into more battery time, which is a problem of Ubuntu vs Win7 in my laptop).
I discovered I had 2 options: compile the kernel myself, or use the Ubuntu Kernel PPA (maintained by the Ubuntu Kernel Team). I decided to use the PPA, so I added it to my software sources and installed the generic"linux-lts-backport-natty" kernel (2.6.36-1).
Package installation went fine, and after reboot, I could log in to the desktop no problem. Everything seemed fine, but after a few minutes, the system freezes completely: mouse did not move, none of the indicators moved, even Ctrl + Alt + F1 did not work.Where is the log file where there might be a message related to the freeze? Do you think that the kernel developers would try to fix a bug that probably only affects people running the 2.6.36-1 kernel on a distribution that was not built around it?
Why is it that about 98 to 99% of the time my computer will boot to Ubuntu/Lucid just fine but on rare / random occasions after seeing the initial BIOS boot screen and initial cursor just after initial BIOS boot screens, the video will just go BLANK, i.e. does not boot to Ubuntu desktop ?
If I then do ALT,CRL,DEL sequence the SPLASH screen is displayed on the monitor and the system then reboots and then goes thru the complete boot process all the way to the desktop just fine.Why this occasional failure to boot completely to the desktop ?
I have triple boot pc (xp, ubuntu, and fedora), installed in that order. xp and ubuntu seem to be stable. i have had to pull the power cord 3 or 4 times while booted in fedora. i noticed the last 2 times i can still move the mouse around, but can't get it to open anything. the keyboard is locked up, can't alt-f1 or f2 or anything to get console. can't get it to do anything, other than watch the mouse tail move around (weird).
i installed a new power supply (and at least i now have a power switch - the old one never had one), but that didn't fix the lock up problem. i haven't ran yum update since the fc10 live cd gnome install. was planning on doing that later.. not sure how long it will stay up to download all the 300 or so updates. right now the only thing open is a terminal (can't type in it).. what should i look at to fix this lock up problem?
Code: Select allrandom: nonblocking pool is initialized and Code: Select allPM: Starting manual resume from disk etc.
When everything is ok boot took around 20seconds. But when this problem occur it can take around 5 minutes. It occure during normal boot, but there are some information about resume from hibernation in log. But I didn't hibernate it. And hibernation doesn't work reliably so I removed uswsusp because I tried to fix hibernation with installing uswsusp first.
My laptop: MSI EX600X-033Sk (C2D T5250, Nvidia 8400g, It has firewire, usb2.0, ...)
I tried to google stuff like "Jessie slow boot", "Stack on random: nonblocking pool is initialized" etc but I didn't found any solution.
Here is few parts of my kern.log:
Code: Select allDec 2 21:27:57 MSI-EX600X-033SK kernel: [ 1.950232] sd 0:0:0:0: [sda] 468862128 512-byte logical blocks: (240 GB/223 GiB) Dec 2 21:27:57 MSI-EX600X-033SK kernel: [ 1.952800] sd 0:0:0:0: [sda] Write Protect is off Dec 2 21:27:57 MSI-EX600X-033SK kernel: [ 1.955190] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 Dec 2 21:27:57 MSI-EX600X-033SK kernel: [ 1.955218] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
I have an IBM server with a: "SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07)", meaning kernel module CONFIG_FUSION. This is the real hardware, not emulated by vmware. With recent kernels (2.6.30-35) the boot results in one of three situations:
1.) Most common: kernel panic, way too long stack dump to see anything useful but did have a terminal briefly to debug this and its just not being able to communicate with the scsi subsystems, google for errors found nothing of use.
2.) Sometimes: A hang waiting for the scsi disks after the controller fails to initialize properly, does not pass in a couple of hours.
3.) Very rarely: A long wait for the scsi controller to initialize but a succesful boot afterwards. ACPI subsystems are taking all CPU power. This is the state the machine is at now, working somewhat.
I can boot the machine with a Gentoo live install disk (kernel 2.6.29 I think) and under that version the controller initializes instantly and there are no problems whatsover using the disks so the hardware seems to be solid!
There were some MPT changes in 2.6.25rc5 so thats the latest kernel I've tried. The errors during boot change to a bit more verbose but thats about it. Unfortunately I don't have a serial terminal with me anymore so cannot capture these errors but it was something about an "unexpected doorbell" with 2.6.24 and nothing memorable with .25. Long story short tho, googling the errors provides no solutions and the little I find points to the controller being too slow to initialize somehow.
I'm running out of ideas here and the server is burning fans like theres no tomorrow (ACPI taking everything it can) so is my only option to downgrade to 2.6.29 (and downgrade udev, lvm2, so on and on and on)? I can't believe I'm the only one for whom this has been broken for several minor versions.
Kernels tried:
- 2.6.29-gentoo (live disk) - works, blazing fast initialization - 2.6.32-gentoo-r7 - random boot failures and successes - 2.6.34-gentoo-r1 - same - 2.6.35-rc5 vanilla - same, better errors, zero useful google results.
I'm not very keen on longshot attempts since it can take a couple of hours of panic-loops to get the machine booted up again and the server functions cannot be transferred to another machine. Also, I'm a bit hesitant to mention this, but the boot has only ever succeeded when a serial cable with something at the other end is connected. At first it was the testing serial terminal and now its just a connection to a UPS.
Attached: bootlog of succesfull-ish boot with 2.6.34 (had to cut some out to make the sizelimit):
Code:
Linux version 2.6.34-gentoo-r1 (root@livecd) (gcc version 4.3.4 (Gentoo Hardened 4.3.4 p1.1, pie-10.1.5) ) #1 SMP Sun Jul 18 18:54:48 EEST 2010 BIOS-provided physical RAM map:
I am running a dual boot system with windows 7 and Ubuntu. Both have run smoothly on my machine (Core 2 quad core on Gigabyte board) I recently upgraded to 10.10 from 10.04 via the update manager within 10.04. Following the upgrade the initial boot failed at the login screen ( i simply got the purple colored screen with a white box in the center of it). Instead of trying to figure out what went wrong, I simply re-installed 10.10 from live CD on top of the upgraded Ubuntu that was failing at the login screen. The live CD install seemed to fix everything for the most part ( I did notice some quickly flashing text right before the login screen. I think it was an error message but it was too fast to read)
My problem now is that I am trying to remove some of my old kernels from the Grub2 boot screen and I cant. I have read many posts on how to remove the old kernels, but my system is proving to be difficult. The old kernels definitely show during boot, but whenever I go into Synaptic they are not there. I have downloaded Ubuntu Tweak, and they do not show in it either. I have read the information at [URL] I went to http://www.fixthecode.com/remove-hug...sts-in-ubuntu/ and thought this would fix my problem but I keep getting an error: "awk: 1: unexpected character 0xe2" when i try to run: "dpkg -l | grep ^ii | grep 2.6.3x-xx | awk -F{print $2} I am running kernel 2.6.35-22 The kernels i want to remove are 2.6.32-23 and 2.6.32-24.
I am using Ubuntu 9.10 and am facing an issue while booting up. It goes into initfs command prompt on one of the 4 kernels that show up in the boot menu. I tried to look around for a likely solution and hence did the following:1. ran "chkdsk c: /f" in my windows partition.2. Added "rootdelay=90" in "/boot/grub/menu.lst" file.This is how my /boot/grub/menu.lst file looks and the problem is with the kernel 2.6.31-20-generic:
I have an issue with apt-get that has been bugging me, namely that it tries to delete kernels I did not specify for deletion.
This is an issue that has been present over at least the last three releases and is present for both 32bit and 64bit, so it might actually be a feature and not a bug, however I can't see it's usefulness.
When I use the command:
Code: sudo apt-get remove --purge 2.6.32-21*
It not only tries to remove the kernel 2.6.32.21 but gives me the following output:
Code: sudo apt-get remove --purge 2.6.32-22* Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting linux-headers-lbm-2.6.32-24-generic for regex '2.6.32-22*' Note, selecting linux-headers-2.6.32-21-preempt for regex '2.6.32-22*'
[Code]....
When I go through with this command to remove the oldest kernel on the system, it will actually delete all kernels present on my PC (as I painfully learned when I first tried it). Why is that the case? Wouldn't it make more sense to only remove the kernel 2.6.32.22?
I am running Maverick and I have installed through the terminal those two kernel versions (26 and 27). Once I restart the system and choose either of those kernels to start, I can only work in console mode. I am using 2.6.35-23 without a problem and I have been having this same problem with version 25 too.
I'm having an issue with my suspend, and nothing seems to be fixing it. Every time I suspend, the computer starts up as if it were shut down. Somebody recommended that I use a previous kernel, such as 2.6.35-28, rather than the current kernel, 2.6.38-. When I open Synaptic, no previous kernels are listed, so I wanted to see if anybody else knew how to install previous kernels.
