Crash on install: AMD64 - dapper 6.06 - kernel panic - not syncing

[Patrick Dechent]

After inserting the install-CD (dapper 6.06) I can see the first menu.
Installing UBUNTU causes a crash on my ACER Aspire T140 - AMD64 - S-ATA 200GB.
Error messages:
Loading Linux Kernel
...
kernel panic - not syncing: Attempted to kill init!

What I've done already:
- I checked the CD with md5sum - CD is OK
- I tried: install -noapic -nolapic - same problem.

[Matt Zimmerman (mdz)]

https://wiki.ubuntu.com/DebuggingSystemCrash

[medy (matej-delakorda)]

I would like to add several info as I have allmost same problems:

My hardware:
Notebook HP PAvilion Dv 5000 series
- AMD Turion 64 bit processor
- ATI X200 graphichal card

Using Dapper 6.06 beta und several daily builds (from 10th to 20th of May) all result in same problem.

After booting (install and live CD for AMD64 platforms), the system hangs on line:
<0> Kernel panic - not syncing: Attemped to kill init!

I tried severel other boot options (vga=771, noapic nolapic, expert and server mode, all results in same crash)

- My memory (RAM) in ok, it has been checked several times
- Notebook is brand new

What might be interesting is:
- when trying to install other distribution, i got next results:
- Gentoo (AMD 64) gives me same probles (kernel panic at startuap. also tries several options)
- Debian (AMD 64) netinstall daily build worked for me. It is using kernel 2.6.15-1-amd64-generic and 2.6.16-1-amd64-generic and it works.
- Knoppix (live CD) worked ( based on Debian build)
- Ubuntu 5.10 Breezy (AMD 64) - installation went well and trough, but graphical interface didn't work. Even the text console (ctrl+alt+F1,F2...) It gave fuzzy screen.

I read some similar bug reports and forum post but didnt find solution on this issues. But I admit it is a tricky connection (AMD 64, ATI and Linux)

[Justin Payne (neolithium82)]

Thanks for taking the time to report this bug, however we are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. Please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Regards,
Justin