Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Linux, Unix › ubuntu laptop install problem
New Posts  All Forums:Forum Nav:

ubuntu laptop install problem

post #1 of 6
Thread Starter 
Any 1 know this problem. I have just download a new copy of Ubunty 6.10 GUI install disk.
Put the disk in the drive . cd boots ok . pick install 2 secs later it hangs on section

Quote:
[32.519166]<0> Kernel Panic – Not syncing: Attempted to kill init!
[32.159292]

Any ideas I am using a laptop with a Celeron M
The Wee System
(13 items)
 
  
CPUMotherboardGraphicsRAM
I7 2600 K ASUS P8P67 Pro CF MSI R6950/70 Flashed 2GB 16 GB Mushkin Silverline 1333 4*4GB 
Hard DriveOSMonitorKeyboard
OCZ Solid 3 60GB SSD, 1TB Samsung F1 WIN 7 ULT x64/ MInt Samsung 24" lcd Razor Blackwidow 
PowerCaseMouse
1kw BFG Coolermaster HAF 932 Logitec G9 
  hide details  
Reply
The Wee System
(13 items)
 
  
CPUMotherboardGraphicsRAM
I7 2600 K ASUS P8P67 Pro CF MSI R6950/70 Flashed 2GB 16 GB Mushkin Silverline 1333 4*4GB 
Hard DriveOSMonitorKeyboard
OCZ Solid 3 60GB SSD, 1TB Samsung F1 WIN 7 ULT x64/ MInt Samsung 24" lcd Razor Blackwidow 
PowerCaseMouse
1kw BFG Coolermaster HAF 932 Logitec G9 
  hide details  
Reply
post #2 of 6
When the kernel gets into a situation where it does not know how to proceed (most often during booting, but at other times), it issues a kernel panic by calling the panic(msg) routine defined in kernel/panic.c. (Good name, huh?) This is a call from which No One Ever Returns.

The panic() routine adds text to the front of the message, telling you more about what the system was actually doing when the panic occurred ... basically how big and bad the trail of debris in the filesystem is likely to be. This is where the "not syncing" part comes from, and when you see that, it's good. (panic() does try to issue a sinc() system-call to push all buffered data out to the hard-disks before it goes down.)

The second part of the message is what was provided by the original call to panic(). For example, we find panic("Tried to kill init!") in kernel/exit.c.

So, what does this actually mean? Well, in this case it really doesn't mean that someone tried to kill the magical init process (process #1...), but simply that it tried to die. This process is not allowed to die or to be killed.

When you see this message, it's almost always at boot-time, and the real messages ... the cause of the actual failure ... will be found in the startup messages immediately preceding this one. This is often the case with kernel-panics. init encountered something "really bad," and it didn't know what to do, so it died, so the kernel died too.

BTW, the kernel-panic code is rather cute. It can blink lights and beep the system-speaker in Morse code. It can reboot the system automagically. Obviously the people who wrote this stuff encountered it a lot...

In diagnosing, or at least understanding, kernel-panics, I find it extremely helpful to have on-hand a copy of the Linux source-code, which is usually stored someplace like /usr/src/linux-2.x. You can use the grep utility to locate the actual code which caused the panic to occur.

That was from http://www.linuxquestions.org/questi...d.php?t=353920
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 Asus Lappy GeForce GT520M 4096 
Hard DriveOptical DriveOSMonitor
500GB LG W7=64 ult + Slackware13.1_64 + MineOS HP w2207h 
KeyboardCaseMouse
logitech G11 Fugly, lol logitech mx518 
  hide details  
Reply
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 Asus Lappy GeForce GT520M 4096 
Hard DriveOptical DriveOSMonitor
500GB LG W7=64 ult + Slackware13.1_64 + MineOS HP w2207h 
KeyboardCaseMouse
logitech G11 Fugly, lol logitech mx518 
  hide details  
Reply
post #3 of 6
Quote:
Originally Posted by newphase View Post
When the kernel gets into a situation where it does not know how to proceed (most often during booting, but at other times), it issues a kernel panic by calling the panic(msg) routine defined in kernel/panic.c. (Good name, huh?) This is a call from which No One Ever Returns.

The panic() routine adds text to the front of the message, telling you more about what the system was actually doing when the panic occurred ... basically how big and bad the trail of debris in the filesystem is likely to be. This is where the "not syncing" part comes from, and when you see that, it's good. (panic() does try to issue a sinc() system-call to push all buffered data out to the hard-disks before it goes down.)

The second part of the message is what was provided by the original call to panic(). For example, we find panic("Tried to kill init!") in kernel/exit.c.

So, what does this actually mean? Well, in this case it really doesn't mean that someone tried to kill the magical init process (process #1...), but simply that it tried to die. This process is not allowed to die or to be killed.

When you see this message, it's almost always at boot-time, and the real messages ... the cause of the actual failure ... will be found in the startup messages immediately preceding this one. This is often the case with kernel-panics. init encountered something "really bad," and it didn't know what to do, so it died, so the kernel died too.

BTW, the kernel-panic code is rather cute. It can blink lights and beep the system-speaker in Morse code. It can reboot the system automagically. Obviously the people who wrote this stuff encountered it a lot...

In diagnosing, or at least understanding, kernel-panics, I find it extremely helpful to have on-hand a copy of the Linux source-code, which is usually stored someplace like /usr/src/linux-2.x. You can use the grep utility to locate the actual code which caused the panic to occur.

That was from http://www.linuxquestions.org/questi...d.php?t=353920

Kernel panics are awesome .

@scotishhaggis
You can try simply redoing the install process. I get kernel panics once in awhile when trying to install new linux distros, so I just keep trying until it works (usually by the third attempt).
Magicbox
(17 items)
 
crapbox
(13 items)
 
 
CPUMotherboardGraphicsRAM
FX 8320 Sabertooth 990FX Nitro+ RX480 Kingston HyperX Fury 
Hard DriveHard DriveHard DriveCooling
Samsung 850 EVO  Kingston HyperX 3K Seagate Barracuda 7200.14 Noctua NH-D15 
OSOSMonitorKeyboard
Kubuntu  Windows 10 Pro Dell U2515H CM Quickfire TK (Cherry Blue) 
PowerCaseMouseMouse Pad
Cooler Master Silent Pro M 850W Enthoo Pro Logitech G502 Logitech G440 
Audio
Xonar DX 
CPUMotherboardGraphicsRAM
Sempron 3300+ HP stock mobo (laptop) 200M (IGP) 2x1GB PC3200 
Hard DriveOptical DriveOSMonitor
100GB ATA133 DVD/CDRW Kubuntu 32 bit 14.1" (1280x768) 
Power
6 cell 
  hide details  
Reply
Magicbox
(17 items)
 
crapbox
(13 items)
 
 
CPUMotherboardGraphicsRAM
FX 8320 Sabertooth 990FX Nitro+ RX480 Kingston HyperX Fury 
Hard DriveHard DriveHard DriveCooling
Samsung 850 EVO  Kingston HyperX 3K Seagate Barracuda 7200.14 Noctua NH-D15 
OSOSMonitorKeyboard
Kubuntu  Windows 10 Pro Dell U2515H CM Quickfire TK (Cherry Blue) 
PowerCaseMouseMouse Pad
Cooler Master Silent Pro M 850W Enthoo Pro Logitech G502 Logitech G440 
Audio
Xonar DX 
CPUMotherboardGraphicsRAM
Sempron 3300+ HP stock mobo (laptop) 200M (IGP) 2x1GB PC3200 
Hard DriveOptical DriveOSMonitor
100GB ATA133 DVD/CDRW Kubuntu 32 bit 14.1" (1280x768) 
Power
6 cell 
  hide details  
Reply
post #4 of 6
Thread Starter 
thing is this when i put the cd in and try installing it. i also get it when i check the cd for defects . tried to burn it on 3 differnt systems no still no luck same problem
The Wee System
(13 items)
 
  
CPUMotherboardGraphicsRAM
I7 2600 K ASUS P8P67 Pro CF MSI R6950/70 Flashed 2GB 16 GB Mushkin Silverline 1333 4*4GB 
Hard DriveOSMonitorKeyboard
OCZ Solid 3 60GB SSD, 1TB Samsung F1 WIN 7 ULT x64/ MInt Samsung 24" lcd Razor Blackwidow 
PowerCaseMouse
1kw BFG Coolermaster HAF 932 Logitec G9 
  hide details  
Reply
The Wee System
(13 items)
 
  
CPUMotherboardGraphicsRAM
I7 2600 K ASUS P8P67 Pro CF MSI R6950/70 Flashed 2GB 16 GB Mushkin Silverline 1333 4*4GB 
Hard DriveOSMonitorKeyboard
OCZ Solid 3 60GB SSD, 1TB Samsung F1 WIN 7 ULT x64/ MInt Samsung 24" lcd Razor Blackwidow 
PowerCaseMouse
1kw BFG Coolermaster HAF 932 Logitec G9 
  hide details  
Reply
post #5 of 6
you probably did... but did you check the MD5sum?
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 Asus Lappy GeForce GT520M 4096 
Hard DriveOptical DriveOSMonitor
500GB LG W7=64 ult + Slackware13.1_64 + MineOS HP w2207h 
KeyboardCaseMouse
logitech G11 Fugly, lol logitech mx518 
  hide details  
Reply
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 Asus Lappy GeForce GT520M 4096 
Hard DriveOptical DriveOSMonitor
500GB LG W7=64 ult + Slackware13.1_64 + MineOS HP w2207h 
KeyboardCaseMouse
logitech G11 Fugly, lol logitech mx518 
  hide details  
Reply
post #6 of 6
Thread Starter 
yeah i did . i just went and bought linux format the mag. it had a bootable unbuntu i386 disk it . it does not work ether
The Wee System
(13 items)
 
  
CPUMotherboardGraphicsRAM
I7 2600 K ASUS P8P67 Pro CF MSI R6950/70 Flashed 2GB 16 GB Mushkin Silverline 1333 4*4GB 
Hard DriveOSMonitorKeyboard
OCZ Solid 3 60GB SSD, 1TB Samsung F1 WIN 7 ULT x64/ MInt Samsung 24" lcd Razor Blackwidow 
PowerCaseMouse
1kw BFG Coolermaster HAF 932 Logitec G9 
  hide details  
Reply
The Wee System
(13 items)
 
  
CPUMotherboardGraphicsRAM
I7 2600 K ASUS P8P67 Pro CF MSI R6950/70 Flashed 2GB 16 GB Mushkin Silverline 1333 4*4GB 
Hard DriveOSMonitorKeyboard
OCZ Solid 3 60GB SSD, 1TB Samsung F1 WIN 7 ULT x64/ MInt Samsung 24" lcd Razor Blackwidow 
PowerCaseMouse
1kw BFG Coolermaster HAF 932 Logitec G9 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Linux, Unix
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Linux, Unix › ubuntu laptop install problem