install finishes, but boot fails

I also bought a brand new PC (a while ago) but at the time I bought it, it had an older version of the bios than was available online. And to top it, the newest version still had bugs... I had to wait 4 Long months for the bios before I could even install 64studio on my PC. It was a beta bios release, but I could not wait any longer. Real time kernels give full priority to hardware and software that has the highest proirities. This has the sometimes detrimental effect on single processor PC's that the thing will appear like it is hanging under heavy load. Ubuntu, made for a more general creative crowd, did not want to run the risk, so they only opted for the low latency kernel, with a Real time kernel available optionally (which I heard unofficially IS the 64studio RT kernel, remixed) Cheers,

The bios should be up to date, the computer is new [well, end of year sale], but it may have something else going on. I wonder if it has been set up differently for Vista. I'll see if I can find out if it handles the two kernels differently. On one of the other threads here, someone said that for him the 64Studio kernel produced lower latencies in music processing than the Ubuntu kernel. Is that generally true for all systems? Thanks

I had something similar once, but I cannot remember what I had to do to fix this... Is your Bios on your motherboard up to date? It seems that most hardware problems can be attributed to strange things in the bios. Some OSes gets past, but others won't. Remember that 64studio has a Real Time kernel, and not a Low Latency as Ubuntu studio does. This could be it.

Thought I would try the Ubuntu Studio DVD to see if it [or my machine] had the same problems. It installed quickly and smoothly and even found and uses my ethernet card. I still want to use 64Studio if I can. I'll try burning the DVD at a slower speed.

The above message should (3rd line changed) read: Warning: missing mdadm.conf file, trying to create one Success: mdadm.conf created mdadm: No arrays found in config file or automatically Failure: failed to assemble all arrays I took pictures of the screen and copied the messages and can send them if you like. While doing that, after some minutes, these new messages appeared: check root = bootarg cat/proc/cmdline or missing modules, devices: cat/proc/modules ls/dev ALERT! /dev/hda2 does not exist. Dropping to a shell! Busy Box v1.1.13 (Debian 1:1.1.3-4) Built in shell (ash) Enter 'help' for list of built-in commands Saying that hda2 does not exist is odd, because that is the partition that the installation itself formatted as ext3. And when it said I hadn't designated a boot partition I gave it the "/" And is where, I presume, it installed the software, although it doesn't actually say which partition it is installing in. I tried installing in rescue mode (the problem with not recgnizing my ethernet card or successfully doing network config remains) I set up partitions #2 ext3 / #5 swap This seemed OK until the base system install began, then I got a red screen and an error message: Base system install error The debootstrap program exited with an error (return value 1) check /var/log/syslog or see virtual console 4 for details I hit "continue" and got The base system installation into /target/failed check /var/log/syslog or see virtual console 4 for details I started over again from the Debian screen, in rescue mode, specifying hda2 to be formatted ext3 and the same messages appeared. I started over again from the Debian screen, just hitting enter. Once again the installation seemed to set up hda2 and to go thru the installation, but upon restarting the computer, the 64Studio screen came up, nothing else happened, and hitting F2 gave the same messages as before, including saying that hda2 does not exist. Does this ring any bells?

Check the sum of the iso image, not the disk. If that is ok try to burn another disk. Failing that, try to capture the screen with a camera - I also have the speed handwriting problem... Good luck!