radvd has nothing to do with DVDs.

Indeed, but it was keen to get involved after I issued the command to install the libdvdcss2 package. Hmmmm.

I'm starting to suspect, though, after having subsequent issues with DisklessCreate script as well that I've mucked things up somewhere and it may be the judicious use of apt-get update.... I read on another thread recently that if you're using the 8.10 final snapshot, you shouldn't need to do this and could mess things up doing so...

I have started re-installing to test this theory and may have to come back and eat my words here before I lead others too far off track.

Pretty sure some more/different drivers are going to be required. But this is a lot closer. I will see what I can come up with.

Scripting this moves into a bit more work, because we don't want other repo/ppa's in sources. So I will have to figure out a scheme to get and build these drivers from source, figure out if they conflict with other intel stuff, and if so, differentiate between them...

Chances are that you will simply have to add these things yourself on 1004. They should work automagically when we get to 1204.

Well, thanks for the help so far... let me know if you want to script it and I'll give it a whirl. In the meantime I'll get clonezilla going so I can image my machine in case we want to try a clean install.

Had a brief issue adding the libdvdcss2 ilbarary to my 8.10 install, thought I'd mention it here in case it helps someone-

Code:

apt-get update
apt-get install libdvdcss2

ran fine until I got errors:

Code:

Setting up radvd (1:1.1-2ubuntu2) ...                                           
Starting radvd: [Apr 11 08:05:41] radvd: syntax error in /etc/radvd.conf, line 2:                                                                               
[Apr 11 08:05:41] radvd: error parsing or activating the config file: /etc/radvd.conf                                                                           
failed.                                                                         
invoke-rc.d: initscript radvd, action "start" failed.                           
dpkg: error processing radvd (--configure):                                     
 subprocess post-installation script returned error exit status 1               
Setting up libdvdcss2 (1.2.10-0.2medibuntu1) ...                               

Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Errors were encountered while processing:   
 radvd                                       
E: Sub-process /usr/bin/dpkg returned an error code (1)
dcerouter_1027763:~# cp /usr/share/doc/radvd/examples/simple-radvd.conf /etc/radvd.conf   

I followed the steps in the following

I had the same issue.  I solved it by copying radvd.conf from /usr/share/doc/radvd/examples/simple-radvd.conf to /etc/radvd.conf, and then doing apt-get install to resume the upgrade.  I would concur with Murdock as it's likely an upstream issue.  The radvd.conf file that was installed by apt had two blank lines in it, which is why apt barfed an error on trying to restart the service.

/Mike

And that got past the initial errors but when I reran apt-get install libdvdcss2 I got errors relating to the eth0 card:

Code:

Setting up radvd (1:1.1-2ubuntu2) ...
Starting radvd: [Apr 11 08:11:51] radvd: interface eth0 is not RUNNING
[Apr 11 08:11:51] radvd: interface eth0 does not exist
[Apr 11 08:11:51] radvd: error parsing or activating the config file: /etc/radvd.conf
failed.
invoke-rc.d: initscript radvd, action "start" failed.
dpkg: error processing radvd (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 radvd
E: Sub-process /usr/bin/dpkg returned an error code (1)

It seems that radvd was trying to do something with eth0 and on my system eth0 is actually the internal network... so I checked out the /etc/radvd.conf file and it had:

Code:

interface eth0
{
   AdvSendAdvert on;
   prefix 2001:db8::/64
   {
   };
};

So I switched the eth0 to eth1 in the above conf file and then the apt-get-install libdvdcss2 ran through fine.

I presume the above conf file needs to point to an external (internet) network.

You probably need the DVD CSS libraries to decrypt the DVDs (if legal in your region, of course,    ). Nice to know the the backports worked.

Yup, I did install those... didn't appear to change the black screen issue though. Will see when I redo the install via snapshot- maybe I missed a step somewhere.

My rant: As far as DRM goes, my conscience is clear- I legitimately obtain any digital media and for my viewing/listening convenience I make a digital copy. To try to prevent me from doing so because the same technology might make it easier for me to do something illegal is ridiculous...

Big thanks to L3mce, we had some success on this issue. Basically, I ran the inernet install script and prior to reboot, the steps in the link posted by JaseP above:

Code:

apt-add-repository ppa:kernel-ppa/ppa
apt-add-repository ppa:glasen/intel-driver
apt-add-repository ppa:f-hackenberger/x220-intel-mesa

apt-get update
apt-get install -y linux-image-generic-pae-lts-backport-natty
apt-get dist-upgrade -y

Many thanks for finding these JaseP.

Then reboot and, hey-presto, AVWizard.

In the end I was able to get UI2 but couldn't get vids to show using alpha-blending... not sure why- The DVD title page would start but once "play movie" was selected the screen would just be black with sound. I only tried with DVDs, unfortunately didn't have any other decent vid files to tinker with... Still, the video is good and working well. Yay!

Next step is for l3mce to get this scripted into the install and I'll retry with a snapshot install.

Thanks for the ideas and suggestions, guys. Difficult to know the path to follow here because this is just my core I'm talking about and it sits in a cupboard (closet) when it's not being installed so the graphics really aren't an issue for me personally (provided I can still use the machine as a headless core or at least a hybrid that never gets used as such). Of course if sorting them out could help others then it would be worth doing! If not, I don't want to waste all of your time tinkering with it!

First a couple of embarassing newbie questions... if someone could clarify it would help me-

1. How is it that the basic Kubuntu 10.04 X-server appears to work easily but the linux-mce configuration battles? I presume the Kubuntu basic install uses some kind of simple default x-config that wouldn't hack it for the video requirements of MCE? If that is the case, is it not possible to fall back to this basic configuration where more advanced can't be done? I guess for most people that would be no good because the whole point of the install is to get decent video but in my case all I really need is the dcerouter. Video is nice for the initial setup (sarah etc) and checking everything is installed and working but no train-smash if I just get the basics.

2. If I were to buy an N-vidia pci-e card and throw that in, presumably that would improve my chances of getting this baby up and running?

OK, now for the way forward-

l3mce, if you want to try to get this thing sorted on my hardware for the benefits of others, I'm happy to be of as much assistance as I can be... just let me know what you need to do. PM me or post here when you want to have a go- we'll have to co-ordinate times because I'm GMT+2 so it'll take a bit of organisation to get a compatible time-zone. Also let me know what you need on my side- obviously I'll have the system at a point where all is installed but avwizard is at the "failed to setup X" point and will be using another machine to communicate. I'll check out the chat channel in the meantime.

The initrd is the last thing that happens on that image. There is a log... It should have tried (and failed) to reboot after that, displaying (and hanging) on the shutdown bootsplash. Pressing enter should have competed the reboot.

Darn, I forgot to look at the log but I had another go on this 201203211118 dvd installer and same thing- last white message across splash screen is "initrd and vmlinuz fix" or something to that effect. DVD does not eject and pressing enter does not reboot. When I hit the reset button, it boots but fails on

Code:

[ OK ] * Starting upnp media server and mediatomb
         rm: cannot remove '/dev/nbd*': no such file or directory

As shown in attachment.

Going back to internet install unless there is another promising snapshot available.

OK, snapshot 201203310416 did not work for me -

Tried both the hybrid and the headless install from the menu and get the same for both. Summary:

Install went normally up to reboot required. I was away from the machine but at the point where it was required (I assume) all I saw was a black screen with an orange stripe in the middle (dvd drive had auto-ejected). I assumed (from previous discussion) this was the reboot point so I pressed enter and, sure enough, reboot happened. So far so good.

Lots of activity on the screen during the next boot including a full screen of text which scrolls by really quickly. All seems to go ok and a message says the next screen I see should be AVWizard. System reboots again.

Then it all seems to do exactly the same thing and just keeps going in a circle - reboot and each time I see the "firstboot" script running?

Any ideas? Anyone else having same issue?

So there're two issues - the failed to setup X thing, which I will deal with in another thread and the hanging after initrd which can carry on here. Currently waiting for bongo's recommended snapshot to download...

OK, I'm starting a new forking thread here. I mean, I'm forking the thread or something like that because my other can deal with the hanging after initrd on dvd install which is something else.
http://forum.linuxmce.org/index.php/topic,12499.0.html

The problem, to re-iterate, is "Failed to setup X".

The chipset is Intel Sandy Bridge graphics.

Code:

00:02.0 VGA compatible controller [0300]: Intel Corporation Sandy Bridge Integrated Graphics Controller [8086:0102] (rev 09)

The auto-setup wants to use an intel driver (fair enough, it's an intel chip) but the comment from l3mce below probably still applies

....

I will tell you that this will NOT work on Sandy Bridge/HD3000. Just too new for 1004.

So, where to now? Well, as far as the x-configuration goes - this is ultimately my headless core so I really just need basic graphics on it. Is there some way we can fall back to a simple vesa driver or something like that?

Or should I be doing something nasty to configure this one that will not work for everyone else

eg. I did find a link to a set of steps for getting sandy bridge graphics working under 10.04
http://ubuntuforums.org/showthread.php?t=1879121

I guess first prize would be to get it working well for everyone (ie right driver auto-installed etc). If possible, I'd like to help with that. Let me know l3mce?

2nd prize would be to get it working badly for everyone - ie wrong driver but enough graphics performance to use on very basic core.

3rd prize would be a nasty hack that allows me to set up my own system but has to be repeated by anyone else with similar hardware.

Ta, I'm busy downloading. Remember we have 3rd world line speeds here...

Anyway, here's what's on lspci for l3mce to dig through. Is there another way to get hardware specs that would be more useful?

Code:

0:00.0 Host bridge [0600]: Intel Corporation Device [8086:0100] (rev 09)
00:02.0 VGA compatible controller [0300]: Intel Corporation Sandy Bridge Integrated Graphics Controller [8086:0102] (rev 09)
00:16.0 Communication controller [0780]: Intel Corporation Cougar Point HECI Controller #1 [8086:1c3a] (rev 04)
00:1a.0 USB Controller [0c03]: Intel Corporation Cougar Point USB Enhanced Host Controller #2 [8086:1c2d] (rev 05)
00:1b.0 Audio device [0403]: Intel Corporation Cougar Point High Definition Audio Controller [8086:1c20] (rev 05)
00:1c.0 PCI bridge [0604]: Intel Corporation Cougar Point PCI Express Root Port 1 [8086:1c10] (rev b5)
00:1c.1 PCI bridge [0604]: Intel Corporation Cougar Point PCI Express Root Port 2 [8086:1c12] (rev b5)
00:1c.2 PCI bridge [0604]: Intel Corporation Cougar Point PCI Express Root Port 3 [8086:1c14] (rev b5)
00:1d.0 USB Controller [0c03]: Intel Corporation Cougar Point USB Enhanced Host Controller #1 [8086:1c26] (rev 05)
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:1c5c] (rev 05)
00:1f.2 SATA controller [0106]: Intel Corporation Cougar Point 6 port SATA AHCI Controller [8086:1c02] (rev 05)
00:1f.3 SMBus [0c05]: Intel Corporation Cougar Point SMBus Controller [8086:1c22] (rev 05)
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)
03:00.0 PCI bridge [0604]: Integrated Technology Express, Inc. Device [1283:8893] (rev 30)
04:01.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet [10ec:8169] (rev 10)

Thanks for the response, l3, so many paths to follow-

OK, so it sounds as if the install was more or less complete but just not rebooting. I did hard-power it down and then start up again but assumed the install hadn't completed so didn't expect much. Definitely didn't go to AVWizard but I can't quite remember what happened.

What I have done in the meantime is internet install from a base kubuntu 10.04 and the restart happened and I'm at the "Failed to setup X" screen. Yay, familiar territory ;-)

So I think what I'll do at this stage is go and dig through that ATI testing thread of yours and see if I can pick up some suggestions to resolve this one and at the same time will try to gather some more detail on my hardware for you.

P.S. - where is the install log if I should go the DVD route again?

I may also set to downloading the latest snapshot just to keep the ADSL line busy....

Giving 1004 a go....

1. Downloaded 201203211118 snapshot and burned to DVD.
2. Install past the kubuntu stuff, seemed to go fine, got to the point where the text messages from lmce were coming up
3. Last text message that came up on the screen over the splash image was something to do with INITRD... stayed there a while, when I moved the mouse it disappeared and no activity
after that.

Eventually +- hour with no hdd or dvd activity and I powered off.

Is there any install log or anything I can look at to see how far it got and what the problem was?

In the meantime, I will try the internet install...

P.S. hardware:

Mobo: FOXCONN H61MX-V DDR3 LGA1155
CPU: INTEL CORE I5 2400 3.1GHZ
NIC1: Integrated
Graphics: Integrated
NIC2: Realtek something or other PCI.

I use "putty" to ssh from my work laptop (MS Windows OS) into my core, when I'm at home and need todo updates and maintenance.
Karel

Likewise, I use ssh from fedora 16 box (our home workstation). From my work laptop I use openssh from within Cygwin. Cygwin is brilliant- a set of unix tools for windows... if you are used to unix command line tools, try it.

Well... I don't know why you would switch tty's on an MD in the first place... they are useless as you will not have a password to supply it. If you have forced a password on it, then it is broken... and this behavior is likely due to this.


Switching between desktop and orbiter is glitchy on the whole. I plan on fixing this in short order.

Good questions:

Why switch to a tty?
A number of reasons, primarily to get to the command line to do stuff like lspci, check the logs, run diskless_create etc etc? Sure, I wouldn't want to do it as part of my home-automation and media watching activities but when getting things set up and figuring out why stuff is/isn't working the command line is essential to me. Most often, I'd use it as a route to ssh onto the core (dcerouter). Mine sits in the server closet and has no screen or keyboard so if I want to go command line, I go via a media director.

How to log in?
If I recall (my system is semi broken at present as the mobo replacement changed the ethernet NIC and I'm having some issues there), I just log in with my username/password that I created during the install process. Then when I hit the command line I usually ssh to dcerouter. I haven't forced any passwords, anywhere, I promise. I will confirm that this is how I log in when it is up again. Are others not able to do this? Is it unusual? How does everyone else access dcerouter if it is a headless core?

Glitchy desktop/orbiter switching
Many thanks for addressing this. It will help me a lot. I generally don't go to the KDE desktop partly for this reason and partly because I think some of my MDs are quite low spec so they're fairly slow running it... which is why I prefer to hit the tty command line.

Thanks for the response l3mce, I appreciate all the input and if I'm fighting the system by all means let me know....

[EDIT]: Oh, I forgot, the reason I wanted to go to command line on the CORE was because I had my core at work plugged into a keyboard/mouse/screen because I was setting up the BIOS after the shop replaced the motherboard.... so I thought I'd fire up a video and see how it played. The video played but I had no way of stopping it. I couldn't bring  up the on-screen orbiter - no mouse or keyboard events seemed to be responsive and because it wasn't plugged into my network, I had no other orbiters to control it so in desparation I hit ctrl-alt-f2 to get to the tty and I thought maybe just switching back to the X-session would bring up the orbiter. Nope.