Author
Topic: 1004: The time has come. (Read 37856 times)

one more thing. I could not setup 1080p 50hz in AV wizard on my MD. On the first boot 1080p did not work at all. Probably soemthing with the Nvidia driver beeing updated? (does it reboot after that? I did not stay with the screen all the time). I did then setup 720p and that worked.On the second boot where i activated the AV wizard again from within advanced setings I could choose 1080p and it showed something, but I assume it used 720p size as the AV wizard was not completely shown a part of it was outside the "TV screen". this time I also tried 24 and 60hz, but the did not work in 1080p either.

Hi viking... as your issues are not related to the DVD install, but instead are generic 1004 issues, I would appreciate opening threads pertaining to them. People might be under the impression, based on the OP, that installing from DVD means their tv won't be found.

Everything boots well (after pushing enter at 'boot:'). I've got the menu where i can choose which version i want to install. But once the status balk starts, it freeze. The balk is at 70% and doens't do anything anymore. I've left it for about 30 minutes, but even the numlock led isn't doing anything anymore.Only thing i can do is a hard reset.

Everything boots well (after pushing enter at 'boot:'). I've got the menu where i can choose which version i want to install. But once the status balk starts, it freeze. The balk is at 70% and doens't do anything anymore. I've left it for about 30 minutes, but even the numlock led isn't doing anything anymore.Only thing i can do is a hard reset.

ps linuxMCE 8.10 runs fine on this system (except video capture what i don't really use (for the moment))...

Well that is a bummer. This is the first hard lock. Thank you for eliminating the ssd as the culprit, it would have been my first goto.

There is a log, if you can log in to live boot (av wizard will probably fight with you after you hit desktop. Just ctrl alt f7 your way back after avwizard stops blinking). From there you can open dolphin probably and just click to mount the drive, and pastebinit /var/log/pluto/install.log or... hmm... a quick scan reveals that I never re-enabled the log, fearing that it was causing a problem at some point...

You could check the dmesg/syslog but... Need to reenable that log so I can figure out where it is breaking.

I've tried 4 options. Each time it's the same error. This happens really quick. So i guess it's a hardware related issue. I'll try to have more info this evening (with the tip of l3mce (ctrl-alt-f7...)

I'm in the office now, so no access to the machine. But if i'm not wrong, these were following options:

LinuxMCE live

LinuxMCE core + MD

LinuxMCE headless

Failsafe

On the side:

Not sure what the headless is. Maybe this could be integrated in the installation screen? A small explanation, what-to-choose on the bottom (or F1, or ...)?

Maybe another option could be a kind of verbose installation option? That you don't have the graphical screen / status bar (what i love by the way), but a complete view of installations files, checks...?

I'm not sure if this possible, i don't have enough software knowledge for that.

Live is running LMCE without installing it.Core and MD is installing LMCE on a system with terminal/keyboard etc. and you can use this system as a Media Director to watch videos, listen to music etc.Headless is just the Core system. You stuff this in a closet and its basically like a server. You create MD's elsewhere on the network to watch videos, etc

Personally I usually build a Core and MD system as more of a troubleshooting unit. If it doesn't work on a MD does it work on the Core/MD?

Until very recently, I finally changed my Core/MD to another not so old hardware platform, I used to need to run the option (F6?) and remove rghb quiet and add all_generic_ide to the kernel line.

For some reason the install would fire up run for so long and bomb. Something didn't like my hardware platform - which I figured was something to do with my DVD drive.

The thing is... at 70% or whatever, this is not part of LMCE specifically that is busting... this is the generic kubuntu install process that is bombing. I tend to agree with pigdog... this is likely resolved with a grub parameter. all_generic_ide perhaps... or maybe more to do with your ATI... there are a couple of ATI grub params like radeon.modeset=1 or maybe ACPI=off... sometimes acpi causes issues.

I believe this to be a generic install problem... and you could test this theory, if you were so inclined, by downloading a generic kubuntu 10.04 32bit desktop iso, and trying to install it.