While booting the 2004.2 amd64 universal liveCD, I get this error message repeated a screenful of times, and then I have to use tthe power off/on buttons to reboot the machine. Ctrl-Alt-Del doesn't work in this case : instead, it prints more to the screen, with references about "lost ticks". I have tried booting with the gentoo and gentoo-nofb kernels, with the same result. I have also tried the noapic boot parm without success. I am using a Compaq Presario R3240 ( http://www.shopping.hp.com/cgi-bin/hpdirect/shopping/scripts/product_detail/product_detail_view.jsp?BV_SessionID=@@@@1954374018.1091800724@@@@&BV_EngineID=ccdhadcmeklhlhmcfngcfkmdfondfgf.0&landing=computers&category=notebooks/compaq_presario/R3000Z_series&subcat1=rts&catLevel=4&product_code=PF153UA%23ABA&tab=detailed_specs#defaultAnchor ) I can reproduce the problem 5 times out of 6. Reproducible: Sometimes Steps to Reproduce: 1. Boot with amd64 universal liveCD Actual Results: prints a screenful of "vt: argh, driver_data is NULL!" and freezes. Expected Results: finish booting, get a root prompt
Problem can also be reproduced when booting with gentoo-smp, gentoo-smp noapic. I have no problem booting from the SystemRescueCD version 0.2.14 (www.http://sourceforge.net/projects/systemrescuecd). SystemRescueCD is based from the Gentoo liveCD.
I also got this problem, the very strange thing is that I was able to boot two times without errors, then the third time, this appeared. Now I tried it again and again, it doesn't stop. I was using AMD64 2004.2 universal CD, with a AMD Athlon 64 3000+ processor, a phoenix BIOS and a 200GB HDD. When booting, it begins printing a couple of errors, too fast to read, and then prints "vt: argh, driver_data is NULL!" until the screen is full with this. Now if I type anything, it doesn't appear on the screen. ALT+CTRL+DEL also doesn't work. An error message (quite long) appears; kernel problem etc. When pressing ALT+F4, a LiveCD login appears. Here I can use ALT+CTRL+DEL to reboot. The very strange thing, as mentioned before: It worked 2 times without any problem. Now I tried it about 20 times or more, it doesn't work, also turning all power off for about 10 minutes or so doesn't help. The Expected Results, I also got this problem, the very strange thing is that I was able to boot two times without errors, then the third time, this appeared. Now I tried it again and again, it doesn't stop. I was using AMD64 2004.2 universal CD, with a AMD Athlon 64 3000+ processor, a phoenix BIOS and a 200GB HDD. When booting, it begins printing a couple of errors, too fast to read, and then prints "vt: argh, driver_data is NULL!" until the screen is full with this. Now if I type anything, it doesn't appear on the screen. ALT+CTRL+DEL also doesn't work. An error message (quite long) appears; kernel problem etc. When pressing ALT+F4, a LiveCD login appears. Here I can use ALT+CTRL+DEL to reboot. The very strange thing, as mentioned before: It worked 2 times without any problem. Now I tried it about 20 times or more, it doesn't work, also turning all power off for about 10 minutes or so doesn't help. The Expected results, finish booting, get a root prompt, worked 2 times, now they don't.
I have the same problem. It occurs with livecd universal 2004.2. But with minimal 2004.1 it works fine, so the bug was probably introduced between 2004.1 and 2004.2
Booting with "gentoo noapic" works.
Never mind, I just reproduced it with "gentoo noapic" as well. Now it keeps doing it all the time too.
I have the same issue on a Dell Precision 470 (Dual Xeon 3.4 EM64T) It did it a lot (along with "your time source seems to be instable" errors). I had booted with gentoo-nofb noapic and it worked once, and now it doesn't seem to work.
i'm having the same problem. AMD64 2004.2 minimal CD AMD Athlon 64 3000+ processor SATA drives ASUS KV8
Same here. Pretty much the same system as Ben Moss above, but without sata drives.
Please try the latest 2004.3 prerelease LiveCD for amd64. It's out on the mirrors in the /experimental/amd64/livecd directory. This is a bare-bones LiveCD, so a stage tarball and portage snapshot are REQUIRED. The portage snapshot is in my devspace here: http://dev.gentoo.org/~jhuebel/2004.3-testing/ If you decide not to use the portage snapshot, then make sure you manually mark portage-2.0.51_rc9 stable or bootstrap will likely fail.
is this still an issue with 2004.3? if so, please reopen
Actually...
There we go. This should be fixed. If not, follow blubb's advice and REOPEN.