System continues to boot OK and everything seems to work fine as I expect. I am not sure what the above causes. It looks related to USB, but I am not sure. lsusb gives:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
However, when I boot with this, tboot.gz seems to have an error that makes the computer to restart. So I want to see the log of booting tboot.gz. This is before ubuntu is booted.get the log of this tboot.gz boot?
I installed Fedora 13 on a separate partition and it deleted all of my openSUSE entries in grub. Or the boot menu, whichever is correct. From another thread, I found these commands and tried it:
Code:
grub root (hd0,3) setup (hd0) quit reboot
hd0,3 contained one of my openSUSE installs. Everything went well and grub accepted all of these commands except quit. So I used esc and rebooted. The reboot brought up the grub shell again. I could find no way to boot anything. Then I used the 'repair installation' option from the 11.2 dvd and installed a new boot loader for /dev/sda2 which contains 11.2.
This was successful, so I went to the YaST bootloader tool and added /dev/sda3 (Milestone 5) and /dev/sda4 (Fedora) and rebooted. But these two partitions still boot into grub instead of loading the correct kernel.
I have windows7 installed in my laptop. I tried installing Redhat linux in it, and I was successful. But then I logged in with windows7 and deleted the partition in which I had installed redhat through computer management. Now my system doesnt boot with windows instead it boots with GRUB. Also to inform that the deleted linux partition I merged with Windows.
I am getting an error after the self boot sequence when after X minutes the system auto boots the highlighted option in my case it is mint 7 after that screen an error comes up with Random numbers and letters then Stuck?
I've tried to install 9.10 on my PowerBook G3, with both a CD and DVD. However, the system shows a folder with a question mark and boots into the default OS 8.6. I even tried with an older ubuntu disc (8 point something) that had worked on another computer, but this didn't work either. I know the computer can boot from the CD drive, as it works with my OS X 10.4 DVD.
I switched today to slackware-current on one of my desktops to play with it and ran directly into a problem.
Since ages my lilo.conf has two entries for slackware. One for runlevel 3 and one for runlevel 4.
Code:
Since the upgrade this is no more possible because I get a kernel panic as soon as udevadm trigger is called. The stack says something about an unknown boot option. Because that i removed the append lines from my lilo.conf and i was able to boot the system. The crash happens when udev is called from within the ramdisk and afterwards. I tried both.
My question is now. Is this a bug in udev or expected? I have this setup since at least 5 years and had never problems with that. What do I have to do to be able to select the runlevel at boot time?
I tend to get constant crashes when using internet browsers ( Google Chrome and Firefox ) basically the application hangs not moving in any way, then eventually completely freezes up, the system then locks up and finally crashes.
Upon system re-start I get "Read Error" at boot ( No further information, it literally just says "Read Error" ).
It is sometimes fixed by going into the BIOS and select "Hold on No Error".
I tried installing OpenBios to see if using different BIOS firmware would resolve the issue, but the OpenBios install failed ....so no dice there either.
I am trying to work out if it is a hard drive problem or if it is purely a problem with Fedora.
It was working fine for a couple of months and when it does boot up ... the system works fine, ( Until another crash ).
It seems like the internet browsers crash the system and then the system crashes and can then no longer remember how to boot up.
what this could be that could be software based....if not it looks like I will need a new hard-drive.
First of all, my computer is running Debian Jessie. uname -a gives me this output: Code: Select allLinux felix-PC 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux
So today I updated my system with aptitude update and aptitude upgrade, and there was few paquages that were updated. Among them was one "linux-image" or "linux-headers". I believe that it is linked to this security update: [URL].... .
During the time aptitude upgrade was running, I was simply surfing on Iceweasel. However, it seems that my system suddenly restarted, without asking me the permission or without notifying me. It really looked like I pressed the restart key, but I actually didn't. My computer battery was full charged and plugged in. So, I do believe that it is my system that rebooted himself after the aptitude upgrade was completed (or even during the upgrade, I don't know).
So my computer restarts, and brings me to GRUB menu: I boot Debian and then I get the usual [ OK ] ***** lines telling that the system boots normally. But this time, I get some errors:
Code: Select all[FAILED] Failed to set up automount Arbitrary Executable file format file system Automount point ... [FAILED] Failed to start load kernel module ... [FAILED] Failed to mount /boot/efi [DEPEND] Dependency failed for Local File Systems
I arrive then in Emergency mode with this message: Code: Select all Welcome to emergency mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode. Give root password for maintenance (or type Control-D to continue):
I tried systemctl default but it doesn't boot my system normally. I also tried Control-D but it just reprints the same message. And finally I typed journalctl -xb, which gives me a long log file (855 lines) that I do not understand.
I would give this log file, but it seems that my internet connexion is broken (because of the kernel, I mean), even with an Ethernet cable. So I can't connect with ssh to the computer I use at the moment, and I can't either send it to myself by mail. I tried to mount an usb key, but it seems that any key won't be mounted because of a kernel problem.
An obvious solution to my problem may be to come back to an older kernel version. However, only the lasted kernel version (x86_64 Linux 3.16.0-4-amd64) is installed. dpkg --list | grep linux-image gives me indeed:
Code: Select alliF linux-image-3.16.0-4-amd64 3.16.7-ckt11-1+deb8u3 amd64 Linux 3.16 for 64-bit PCs ii linux-image-amd64 3.16+63 amd64 Linux for 64-bit PCs (meta-package)
I do not know how to come back to an older kernel, as far as I haven't any internet connection and as far as I seem to not be able to load an usb key.
I am on debian jessie. I ran "apt-get update && apt-get upgrade" and midway through the upgrade my computer suddenly rebooted.
I wasn't paying close attention to the upgrade process so I didnt see if there was any error messages right before the reboot. The laptop was plugged in, fully charged and I've never had issues with overheating.
When I boot now I get to a shell with a message that says:
Code: Select allWelcome to emergency mode. After logging in type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode.
If I try "systemctl default" there's a message that simply says "Hangup", nothing else happens.
Looking through "journalctl -xb" I see this:
Code: Select allFailed to insert module 'autofs4' Failed to open /dev/autofs: No such file or directory Failed to initialize automounter: No such file or directory Failed to set up automount Arbitrary Executable File Formats File System Automount Point. Failed to start Load Kernel Modules. If I retry "apt-get upgrade" it says: Code: Select alldpkg was interrupted, you must maually run dpkg --configure -a to correct the problem If I run "dpkg --configure -a" stops at the package cups-browsed with message saying "Hangup"
Output of a few commands I saw in another forum thread:
Is this fixable without jumping through too many hoops or should I just reinstall the system? I need the computer for work so Im not gonna spend days trying to fix it without reinstalling.
I've been having a problem on my AMD based machine, 4cpu, gigabyte ga-ma78gm-s2h Mobo, 8GB mem, two 2 terabyte Sata HDs.One thing I've found is that any kernel after 2.6.32-17 has a randomness at boot time whether the system will completely boot or not.
For instance just today I downloaded and installed 2.6.32-24
It fails to boot (I've tried cold boot, warm boot).Running its repair also fails to completely boot.My experience is that if I keep trying it "may" eventually boot but I believe there was some change after 2.6.32-17-generic that's causing the problem.Because as with 2.6.32.23... which also fails to complete bootup many times... eventually my guess is that 2.6.32.24 will also boot "sometimes".But why does 2.6.32.17 always boot for me? Something changed and its not my setup.
I write the network driver. Transmission of packets in user space I do through netlink socket`s. In user space there is a handling of packets and their transmission on other device (however, it isn't important).
Problem in that any time, packets through the driver in system, and is reverse, are transferred normally. But then there comes the moment when the kernel crash. If to look in syslog it seems to me that comes deadlock. Also I think that it is related with netlink socket`s.
I can't find the information on that anywhere how correctly to use netlink socket`s in kernel space. Can at you will any a reason into the account of synchronization of sockets and the driver in kernel space?
I upgraded a PC from 10.04.1 to 10.10 and it will not boot into the new kernel. Because the system started as Ubuntu 7.10, it is using Grub 1.
It gets to the point where it displays "Starting up..." then displays a flashing cursor at the upper left of the screen, it does nothing further.
Yet it will boot into the previous kernel from the 10.04.1 installation, but X will crash if I login using the XFCE desktop, yet it will log into LXDE without a problem.
Is this a known issue (not booting up with new kernel)?
The CPU is an AMD Athlon 32-bit which does have CMOV (per cat /proc/cpuinfo). I have also manually run various apt-get commands to upgrade/update everything, no change resulted.
I;m installing RTAI and I get this message. I can't seem to find the solution, because I really don't know exactly what the main problem is. There are a list of error,s and warnings that I 'm not sure from where should I tackle the problem: Here is what I get when I boot my 2.6.31.8 kernel with GRUB. (I used the RTAI x86 compatible patch):
I use release 11.2 and this one works very well. I try new release 11.3 and my system crash when I wont to start system on runlevel 5. There is Sempron 2 GHz CPU and nvidia fx550 graphics card. Keyboard PS2 does not responds but mouse on USB work well. When I start "safe" boot option system work well. What I can to do ? What I must change
Applied several updates last night including a 2.6.30.5-43 kernel and a suggest kmod-nvidia but the 5-43 kernel boots to a wallpaper gnome screen the first time.
Booted to the "fallback" 2.6.29....17 kernel and it worked fine.
Then 2.6.30.5.-43 also booted but without nvidia.
Installing akmod-nvidia as sugggested in other posts. Also see a kmod for this kernel.
I have a problem with the kernel update to 2.6.34.6. Up until 2.6.33.x my system boots fine, but with this update the boot stops at the moment that the mouse cursor should become visible. To resolve the problem, I've gone back to 2.6.33.x and removed the 2.6.34 kernel but I wonder what happens with the next kernel update. Anyone else having this problem?
I have updated to the new kernel that was available from 11.2 and now I cant use my system.
It boots up into kde 4.3.5 and then right when its just finishing it freezes everytime and I hear that last tone of the bootup sound ring continually until I force a shutdown. Anyone else have this issue with the update?
I wasn't using my laptop for at least a few hours, but when I looked at it, it had seemed to crash. I am hoping to figure out what caused this, and to prevent it from happening again. I believe it has something to do with drm or b43 as that is what I could decipher from the screen. I have checked some logs and found nothing irregular. I do not want this to happen again. I am running kernel 2.6.33.1 with no patches and a custom config tailored to my processor. The reason I am running 2.6.33.1 is because of support for my Wifi.
I have a dual boot laptop with OpenSUSE and Ubuntu. The boot loader used is Ubuntus Grub that came with the Ubuntu installation.
I have done a zypper dup and upgraded to OpenSUSE 11.4. When I reboot my system I can no longer boot into OpenSUSE, Grub says something about a missing kernel.
I think I understand whats wrong here; the OpenSUSE entry in Grubs table hasn't been updated with the changes brought in by the zypper dup (new kernel i guess).
I'm I correct to assume this? How do I fix the problem? Booting into Ubuntu I tried to find /boot/grub/menu.lst to examine it by I cannot find it. I know Ubuntu use a newer version of Grub, does it have a different file layout?
I installed ubuntu inside windows, thing were going good, till windows got affected with virus, so had to reinstall it, now boots directly in windows 7. I have a 500 GB HDD with two equal partitions, C: drive has windows D: drive has ubuntu I tried the boot-repair, didn't work, instead it corrupted windows boot, which got fixed using startup recovery but I want ubuntu back...
Running Karmic on my laptop, I get very occasional kernel panics (suspect it has something to do with the Broadcom WiFi because it only seems to happen with heavy network traffic or HDD access), but just my lucky, this time it Panic'd on me during my recent update -> linux-kernel 2.6.31-20. My system still 'works', but I get the following when doing any other updates, now:
Code: sudo dpkg --configure -a [sudo] password for tango: Setting up linux-image-2.6.31-20-generic (2.6.31-20.57) ... dpkg (subprocess): unable to execute installed post-installation script: Exec format error dpkg: error processing linux-image-2.6.31-20-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-2.6.31-20-generic; however: Package linux-image-2.6.31-20-generic is not configured yet. dpkg: error processing linux-image-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 2.6.31.20.33); however: Package linux-image-generic is not configured yet. dpkg: error processing linux-generic (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.31-20-generic linux-image-generic linux-generic
Now I cannot seem to get rid of that, and of course, I am stuck in the prior version. Granted everything 'works' - but it bothers me. What's the best way to go about tracking down and hashing out a problem like this?
Don't know if this is a coincidence, but the other day we had a power cut and my laptop went off. When I tried to reboot it got to the ubuntu start up screen, but when it tries to get to the "desk top" screen it all goes blue and black flashes. I have XP and Vista on the same machine and these both start up ok
I updated the kernel to 2.6.35.10-74.fc14.x86_64 and had to reinstall and rebuild the kernel module for my ATi driver as usual, so I edited the kernel arguments at the grub splash screen so that I could boot into single user mode and install the driver (i.e appending the relevant line with '1'). The interesting thing is, the system booted directly into single user mode as root when the system started up. No password was required.
After upgrading from 9.10 to 10.04 my System no longer boots. I had a Dual-Boot System. On Boot I get - "error : the symbol 'grub_puts_' not found grub rescue> (prompt): If I run 'insmode /boot/grub/normal.mod' (I get the same error) If I run 'insmode /boot/grub/ext2.mod' (I get 'The symbol 'grub_xasprinf' not found) If I run ls /boot (The Kernel File Names look Ok)
If I run in Rescue Mode it Reports (The installer could not find any partitions, so you will not be able to mount a root file system. This may be caused by the Kernel failing to detect your hard disk drive or failing to read the partition table, or the disk may be unpartitioned. If you wish, you may investigate this from a shell in the installer environment.) I ran the recommended reporting script and got the following output:-
Code: = Boot Info Summary: = => Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in partition #4 for /boot/grub. => Windows is installed in the MBR of /dev/sdb => Syslinux is installed in the MBR of /dev/sdd <<< This is my USB Flashdrive .....
how do I start a ruby on rails application when my Ubuntu server starts up/is rebooted? I start the application by cd-ing into the ruby application's root directory(the application I'm using is Bibapp) and execute the command;
