Messages

That is a so called fake-raid card: http://linuxmafia.com/faq/Hardware/sata.html#highpoint2240, which means it does software raid in a vendor specific and non-standard proprietary way, not really what I would call a huge plus, instead of tied to OS or machine you are now tied to a specific SATA controller. 

Ah, i should have looked that up before posting.  Thanks Zaerc.  I just figured the ammount of cash he spent on it, it wasn't a fakeraid card.

[ONLY]

ok, all i have up on the screen is the "core" window. the only options i see are the tabs up top which are: Start, Connections, Log Options, View Log, Configuration Files
where are the "advanced" options?
all i want to do is be able to bring up the full kde desktop temporarily so i can add drivers and do a few other things. other than that i plan to leave it in the closet.

Ah, so your core is not a hybrid so you don't have any of the menu's.  On that box you should have an option to check mark "Auto Start Media Station" on the "Start Tab" Also there should be another button to "Start Media Station".  However you'll still need to check mark the box for the first one.  Reboot and you should get the menu.  Another way is press ctrl+alt+f1, this will drop you to a terminal.  type in, "telinit 5" and it should boot you to a gui.  From there you should see an option for MORE -> Advanced Options -> KDE
-

Ahh... What are you talking about here?  driver for the raid?   But on the topic of packages, you will always use Debian because K/Ubuntu is debian based.

they ONLY give me the options of red had enterprise, fedora, suse/enterprise, freebsd and open source. do i use suse? and if so, which one? since highpoint has open source drivers it would be nice if the Linux MCE or ubuntu team included some of these raid drivers in the installation.
[/quote]
Please reread what i said about what kind of packages to choose and i think your, "should i use suse" question should be answered

if i have to go with open source, any pointers on best/easiest way to compile them? i'm a *nix n00b, but am not afraid of a terminal or command lines

I looked in the kernel options and it looks like rocketraid 3xxx controllers are built in but not the 2xxx series.  so you will either need to find a debian/ubuntu/kubuntu package for them or build it from source.  Personally i would do some digging around the ubuntu/kubuntu community and see if someone has build a .deb package for it already.  If not, building from source could be a bit of a pain.  You will have to get the kernel source to start off.  you can use apt-get to download it.  if you do a "uname -a" in the CLI you'll find out what kernel version you have then learn how to download that kernel version using apt-get.  once you have the sources you will can download the sources for your raid driver.  you could install them to /tmp/raid or something to that effect.  go to that dir you untared them to and read the README or INSTALL file (or whatever is similar)  it'll tell you what to type in to build the driver.  Usually it's just "make" and "make install" then sudo modprobe <insert driver name here>  (without the < >)

There is lots of documentation out there, find it and read it.  If you do get stuck and not sure how to interpret the documentation post back and we'll work through it.

please update to RC1 and report back.

My suggestion would be update to 710 RC1.
What did you change or modify to get this though?

i want to install the highpoint raid drivers on my lmce core (never been used/setup) machine. its on the lan but i haven't gotten much further.

I'm not familiar with that name nor did i look it up, it sounds like an onboard raid for a MB though.  If that's the case, don't even bother with it.  software raid is the way to go.

first of all, on the core i have no idea how to bring up the kde desktop or a terminal. i'm a n00b!

That's easy and just a little bit of exploring should solve that anyways.  Don't be afraid of breaking anything or you'll never learn.  If you think it's a bad idea, ask before you do it.  The secret location of KDE is in the advanced options section though.

secondly, i'm so confused. i don't know which driver to use. is it supposed to be debian? they give me the option of red had enterprise, fedora, suse/enterprise, freebsd and open source.
what/how is the easiest way to install these so i can start using the box.
btw, for clarification. i already have the core working off a regular drive the raid is for media.

Ahh... What are you talking about here?  driver for the raid?   But on the topic of packages, you will always use Debian because K/Ubuntu is debian based.

I don't know about the package it tried to fetch and failed.  probably because you weren't hooked up to your network correctly like the rest of your post suggests.

From the sounds of it you are trying to hook up your core to your wireless network and thats a no no.  You need to have your core fully wired and it also might sound like you have DHCP on the core and possibly your wireless router in your network and when that happens that can cause lots of issues, like not connecting to a network.
what i recommend is, unless you have networking experience, hook it up like the following
DSL/Cable Modem -> External core NIC -- Internal core NIC -> Wireless router (DHCP OFF) -> OTHER PC's
on your wireless router, besure to plug everything into the LAN ports and not the WAN port for anything wired.

from your description it looks like you have everything hooked up correctly.  I have a dlink gaming router and have(don't currently) done what you are trying to do on it as well.  One of the things that pops up in the back of my head is that i had to IP the internal interface before i could use it correctly.  When you IP the internal interface you would give it an IP of something like 192.168.1.254/255.255.255.0/192.168.1.1 (or whatever your LMCE IP's are) the order that is staticIPforRouter/netmask/gateway

As long as you have everything plugged into the LAN ports you should be fine.

First off let me say that I really appreciate the effort the developers have put into this. I would recommend however that the official video be removed because it gives the average user false hope about LINUXMCE's current state of development. Things have a loooooong way to go.

LinuxMCE RC1 Failed across the board here's why...

Core Machine:
gigabyte Ep35-DS3R
Intel Dual core 2.2 ghz
Geforce 8500
Intel Nic and Onboard Realtek NIC
Samsung 17 LCD monitor (DVI)

Media Director
Gigabyte P35-DQ6
Intel Dual core 2.4 ghz
Geforce 8600
Sharp Aquos 46" 1080p native

I installed the Kubuntu CD onto the core machine with the recommended ISO in the Wiki
I then downloaded the 2 CD installer 710RC1 and MD5 checksummed both discs
*1*LinuxMCE took around 3 hours to install. This seems abnormal for a linux system.
*2* When the Core booted for the first time, the fonts and resolution were horrible. Prior to LinuxMCE, Kubuntu looked fine.
*3*I tried a diskless boot of the Media Director. It got about half way and in red letters "DISKLESS SETUP FAILED" and it halted.
*4*I did some research on the web, and found out that LINUXMCE tried diskless booting my media director as an AMD64 architecture.
*5*I corrected the architecture and rebooted the Media Director.
*6*The media Director made it to the A/V Wizard. I selected 1080p, LINUXMCE did not output 1080p (640X480)
*7*My iMON remote isn't working out of the box. Almost any media center package I've played with supports this.
*8*Everything looks ugly and nothing reliably works...looks like this needs some work before it can be taken seriously.

A couple of questions for the developers.
1)Why are the newest (check your version vs. current version on the web)  nvidia drivers not implemented supporting 8x00 series cards. the 8 series of cards are easily the most popular card used in average systems nowadays.
2)Why is LinuxMCE installing ontop of Kubuntu and not following the example of MythBuntu. (Product release in sync)

Some comments.
All of my hardware worked in VistaMCE.
All of the hardware worked in Ubuntu
All of the hardware worked in MythTV

This is an exciting product but unfortunately it's failed to leave the ground. I'll keep my eye on it, but it's not ready to impress.

If you have any questions about my hardware please don't hesitate to ask.

Sparkie, create a new thread with your issue so that it can be more focused on.

First lets have you upgrade to RC1, it has the latest nvidia drivers and should help you out in that direction.

Once you upgrade, rerun the avwizard and go at it again.  If you still experiance the same issue of only being able to do 640x480, lets check your xorg.conf and make sure you aren't using the vesa driver.  that would definitely be a show stopper.

I'm sorry i couldn't make the first one.  I had some family stuff pop up right after i had spoke with you in IRC Dan.  Hopefully Thoms recording software didn't blowup this time cuz i'd really like to see what ruby has to offer.  Sounds pretty cool.

Does anyone know if yuuguu works under wine?  It seems a little ironic to have to install windows just for linux mce development conference...    And yes, that means I'm currently windows free and liking it!   

Have fun,
Roy

Ahh, if you read the first post by me i think you will understand it runs under linux.

Okay, tested it out with quite a few people and it seems to work great.
Next test is to actually use it for a demonstration.  Anyone have anything they want to demonstrate or do a class to further test it out?

Last night some of you helped me out by testing out that yuuguu program for desktop sharing and it didn't work.  I later found out because it had to do with the fact i use dual monitors.  Once i disabled one of them from nvidia's control panel it worked.

I tried to get a few more of ya to test it out again this morning but i failed

So, this is how you get it to work.
Go here http://yuuguu.com/
Download the MAC version.
Unzip in whatever DIR you want, IE: ~/yuuguu
Open CLI

Code Select Expand

cd ~/yuuguu/Yuuguu.app/Contents/Resources/Java
java -jar YuuguuLauncher.jar
you'll need to create an account.
and thats it.  Just need to test with a few people being connected to see how well it performs.

These are some Q's i had that went unanswered.  Answer at your leisure

(1:00:02 PM) agentc0reWORK: danielk22, TSCHAKWerk, hari, Hey i am back.  I got wrapped up in work but i'm taking my lunch now.   So back to the sudo thing.  I'm not sure it would be a good thing, either, to have a specific user with nopassword rights to execute telinit either.  isn't that really just another way of setuid root on telinit?  Maybe there are other security risks involved with doing a setuid.

(1:01:12 PM) agentc0reWORK: Also, setting the KDM script to telinit 1.  Is that what we really want it to do?  we want an option for it to drop there or do we just want people to type in that command?  i mean it's really all the same thing.  Maybe there was something else you guys had in mind with having that script do that?

I edited out all the other BS that was going on.  Thought i'd put it in the forums to keep track.

(11:04:13 AM) agentc0reWORK: danielk22, ddamron, TSCHAKWerk: Hey, so i have a semi working KDM init script... it's very ruff, and i've been searching on how to do this properly while also figuring out how pluto did it their custom way.  My current script still uses their processes.  I know you all wanted to be able to drop to the telinit 1 from the kdm script, but why?  Also, i keep hearing that killing a process with kill -9 is a bad thing, but why?  Thats another thing i don't understand right now.

(11:09:10 AM) danielk22: agentc0re: kill -9 prevents the process from shutting down cleanly.
(11:09:26 AM) hari: yeah, -15 is better
(11:09:28 AM) danielk22: agentc0re: but a normal kill should be safe
(11:09:40 AM) TSCHAKWerk: agentc0reWORK: yes... when you SIGKILL, it causes the process to immediately detach... when you SIGTERM, you give a process time to close itself

(11:13:51 AM) agentc0reWORK: danielk22: Ah okay.  that makes sense.
(11:14:04 AM) TSCHAKWerk: agentc0reWORK: only use SIGKILL when you have to
(11:14:08 AM) TSCHAKWerk: agentc0reWORK: big emphasis on have to
(11:14:12 AM) agentc0reWORK: hari: i'll look that up, and look into it.
(11:14:27 AM) agentc0reWORK: TSCHAKWerk: I'm not even using that command to kill things.
(11:14:42 AM) hari: agentc0re -15 == SIGTERM
(11:14:46 AM) agentc0reWORK: TSCHAKWerk: pluto wasn't either.  they were doing a kill -9 pidofX
(11:14:56 AM) TSCHAKWerk: agentc0reWORK: oh YIKES!
(11:15:08 AM) TSCHAKWerk: that can leave video hardware in an unpredictable state!
(11:15:10 AM) hari: i usually do a -15 first, -9 is a last resort weapon when the process misbehaves
(11:15:37 AM) TSCHAKWerk: mirttex: since a core takes over the internal network, other machines can boot off of it, over the network
(11:15:40 AM) hari: agentc0reWORK: they are sending a -9 to the X server?
(11:15:47 AM) hari: not nice
(11:15:48 AM) TSCHAKWerk: mirttex: once this happens, they get the LinuxMCE system.
(11:16:00 AM) agentc0reWORK: danielk22: I'll experiment on my dev vbox and see if it's not killable nicely and if thats why they have it in there.
(11:16:17 AM) agentc0reWORK: hari: yes, they are sending a -9 to the X server.

(11:18:29 AM) agentc0reWORK: Hari, TSCHAKWerk, danielk22: Before i started looking some stuff up on different KDM startup/shut down scripts i created mine to use the telinit process to start and shut everything down.  everything works except for a restart.  But again, im not sure if thats the best way to go about things.
(11:19:14 AM) TSCHAKWerk: agentc0reWORK: well, we'll take a look at it..but i don't have a problem with it.

(11:19:55 AM) agentc0reWORK: TSCHAKWerk: In order for it to work like that, we also have to set suid to root on /sbin/telinit
(11:20:00 AM) grepico left the room (quit: Read error: 110 (Connection timed out)).
(11:20:02 AM) TSCHAKWerk: agentc0reWORK: ooo um..ouch...
(11:20:07 AM) hari: posde: marko is already on my list
(11:20:12 AM) TSCHAKWerk: agentc0reWORK: would RATHER NOT do that.
(11:20:37 AM) hari: agentc0reWORK: setuid is bad, use sudo instead if there is no other solution
(11:20:39 AM) TSCHAKWerk: agentc0reWORK: let's try to find a way to do a limited privilege escalation.
(11:20:56 AM) TSCHAKWerk: agentc0reWORK: either with sudo or whatever.
(11:23:48 AM) agentc0reWORK: TSCHAKWerk, hari; if we were to use sudo in a script though, a user would be prompted to type in the password which is something we definitely do not want to do.
(11:24:33 AM) hari: agentc0reWORK: you can use the NOPASSWD directive with sudo
(11:25:08 AM) agentc0reWORK: TSCHAKWerk, hari: didn't know about that one.  how does that work?
(11:25:47 AM) hari: agentc0reWORK: eg admin    ALL = NOPASSWD: ALL
(11:26:03 AM) hari: kampfpanzer: google sudo NOPASSWD
(11:26:04 AM) kampfpanzer: sudo NOPASSWD: http://www.gratisoft.us/sudo/man/sudoers.html