View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 15 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Fri Apr 02, 2004 11:56 am 
Offline
Joined: Fri Apr 02, 2004 10:08 am
Posts: 1637
Location: Virginia, USA
OK, trying to get R4V2 up and running on a Shuttle SN41G2 (nForce2) + PVR-350 . It's not going so well and would just like to confirm something before trying yet again.

In the Auto Install instructions, it refers to what to do if you have an nVidia chipset. It says "DO NOT install it until after configuration has started and the frontend starts for the first time." Then it describes exiting the front end, logging in as root, installing install-ix86-x or lx, and the nVidia drivers (although it refers to install-nvidia, but I guess it's supposed to be install-nvidia.sh).

First question: is exiting the front end still necessary with R4V2? It seems that, after restarting from the CD install, it asks some questions (about lirc and XvMC) that lead to installing the appropriate versions. So it doesn't seem that you'd need to ctrl-alt-F1 out to do this.

Second question: if the answer to the above is "yes, you do still need to do this" my question is, exactly when in the process _do_ you need to exit and handle those installs? I've tried it before it asks any of those questions, and I've tried it after it's automatically run mythtvsetup, and I can't seem to tell a difference. I just want to make sure I do it at the right spot so I have removed that as a potential source of problems.

Specifically, I can't seem to get the onboard networking to work, so once it tries to contact XMLTV, it fails, and of course nothing works at that point. But for now, I just want to make sure I'm getting the initial setup right. Thanks for the help.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 02, 2004 12:19 pm 
Offline
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location: Fontana, Ca
Follow the instructions... "DO NOT install it until after configuration has started and the frontend starts for the first time." The source for nvnet is included, you should see it installing after rebooting and after you entered the root password.

_________________
cesman

When the source is open, the possibilities are endless!


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 02, 2004 12:32 pm 
Offline
Joined: Fri Apr 02, 2004 10:08 am
Posts: 1637
Location: Virginia, USA
Thanks for replying, but I just want to clarify those instructions so I can follow them.

I'm supposed to exit the front end, not mythtvsetup of the back end, right? Even though mythtvsetup is not running correctly and I'm getting all these errors because it's not connecting to xmltv? I wait until the front end runs, then bail and (re?) install those packages?

Again, thanks.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 02, 2004 12:47 pm 
Offline
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location: Fontana, Ca
"DO NOT install it until after configuration has started and the frontend starts for the first time." If you are having a problems w/ your NIC that should be your first priority.
<CTRL><ALT><F1>
log in as root
install-nvnet.sh
netcardconfig

Does that work?

_________________
cesman

When the source is open, the possibilities are endless!


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 02, 2004 1:06 pm 
Offline
Joined: Fri Apr 02, 2004 10:08 am
Posts: 1637
Location: Virginia, USA
Quote:
<CTRL><ALT><F1>
log in as root
install-nvnet.sh
netcardconfig
Does that work?


Well, I've done the following.

1.) I've installed from CD, then let it go through its configuration, which says it's installing "nforce drivers" and then asks me about DHCP Broadcast (to which I say yes, since I want it to use my router's DHCP server).

2.) I've used an installed non-functional setup, logged in as root, done install-nvnet.sh (where I see the same text that I saw in 1 above about it installing nforce drivers), done netcardconfig (where I see the same text screens about DHCP, or manual IP config if I say no to DHCP broadcast), and then restarted and tried to do mythfilldatabase, which also fails (don't have the errors in front of me but it seems apparent that it's not talking to XMLTV).

Will try again with a fresh install, will let it go through all its own config and mythbackend config, then will bail out of the front end and do the install-i686-lx thing. (Why does it seem to do this during the initial setup after the initial install, or if it is doing it, why do I have to do it again?)[/quote]


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 02, 2004 2:08 pm 
Offline
Joined: Mon Oct 06, 2003 10:38 am
Posts: 4978
Location: Nashville, TN
when you see the installing nvnet are there any errors? does it seem happy? when you say yes pull dhcp does it say succesful faild anything? sounds like your NIC is not getting setup properly which would be why it couldn't get to xmltv(zap2it)


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 02, 2004 2:10 pm 
Offline
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location: Fontana, Ca
You're going in circles... If you did 1 why are you doing 2? After you see the nForce driver message and you say yes to DHCP, it will attempt to get an IP. When it goes to the next step. <CTRL><ALT><F1> log in as root and run ipconfig. Do you have an IP? If so then <CTRL><ALT><F7> and continue. You have need to be patient when attempting to connect to zap2it.com.

_________________
cesman

When the source is open, the possibilities are endless!


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 02, 2004 2:12 pm 
Offline
Joined: Mon Oct 06, 2003 10:38 am
Posts: 4978
Location: Nashville, TN
cesman Linux not windows ifconfig. LOL


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 02, 2004 2:23 pm 
Offline
Joined: Fri Apr 02, 2004 10:08 am
Posts: 1637
Location: Virginia, USA
cesman wrote:
You're going in circles... If you did 1 why are you doing 2?


Because 1 didn't work, or didn't seem to work. When it started up the back end configuration, and I got to the screen where I enter my zip code, I did let it sit there (because I know that pulling the info down takes a long time--I've run through other MythTV installs as practice for doing it to this system), but MythTV gave me an error, something to the effect that it couldn't connect to XMLTV. And then trying to run mythfilldatabase produces a whole string of similar connection errors.

So I searched this forum and saw other postings that recommended running the things that you suggested I run (install-nvnet.sh and netcardconfig). Which is why I got into Situation #2 (running those things on a seemingly non-working install)

And since THAT didn't work, I decided to post and ask about exactly when and where I need to let the Knoppmyth install do its thing, and when exactly I need to interrupt and do things as root manually.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 02, 2004 2:25 pm 
Offline
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location: Fontana, Ca
Do as I stated in above post, except it is ifconfig not ipconfig...

_________________
cesman

When the source is open, the possibilities are endless!


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 02, 2004 2:26 pm 
Offline
Joined: Fri Apr 02, 2004 10:08 am
Posts: 1637
Location: Virginia, USA
Xsecrets wrote:
when you see the installing nvnet are there any errors? does it seem happy? when you say yes pull dhcp does it say succesful faild anything?


I believe it says something terse like "OK." Will go try it yet again and take more detailed notes on errors.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 02, 2004 2:26 pm 
Offline
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location: Fontana, Ca
Xsecrets wrote:
cesman Linux not windows ifconfig. LOL
As little as I use Windows, I cannot believe I made that mistake.

_________________
cesman

When the source is open, the possibilities are endless!


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 02, 2004 7:33 pm 
Offline
Joined: Fri Apr 02, 2004 10:08 am
Posts: 1637
Location: Virginia, USA
First, thanks for everyone's help.

Second, yes, I'm feeling stupid, as now Knoppmyth is up and running in all its glory.

Here were my snagging points:

1) After the initial install, then the configuration, the configuration program running in the terminal says that it's going to start up the front end program. But instead I just got the KnoppMyth desktop graphic: no MythTV. THIS is the point where you bail out of X, log in as root, and run install-i686-lx.

2) Being a novice Linux person, when the instructions say to then run "install-nvidia", that's what I typed, instead of "install-nvidia.sh". Works much better the second way

3) After the reboot, things worked much better (i.e. I got the back end configured and the front end running), but the program guide was still empty. I quit, opened a terminal, switched to su, and ran mythfilldatabase. Didn't work. Managed to figure out one of the errors, and exited back to the mythtv account, THEN ran mythfilldatabase. This worked.

After those things, everything is working (seemingly) perfectly.

Again, thanks for the help, I appreciate that and your patience.


Top
 Profile  
 
 Post subject: BIOS update also
PostPosted: Sat Apr 03, 2004 9:55 am 
Offline
Joined: Sat Feb 28, 2004 10:04 am
Posts: 173
Location: Canton, MI USA
I have the same system. Make sure you install the latest bios for it. It add support for DMA IDE mode. Without this, my Shuttle would crash after less than a day. It's file is fn41s025.bin

I think this link will get you there:
http://www.shuttle.com/hq/support/download/dwn.asp#


Top
 Profile  
 
 Post subject:
PostPosted: Sat Apr 03, 2004 11:10 am 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
Upgrading the BIOS to the latest (fn41s025) is key. Shuttle's change notes make it seem unimportant but it will make all the difference in the world. Without it the machine will be totally unstable especially when there is activity on the PVR card and the disk at the same time. Don't forget to follow their directions to "load optimized defaults" after you flash the BIOS. This sets several changed defaults that are very important.

Second thing, make sure your HD is jumpered for cable select, especially if it's a Western Digital.

I've been meaning to write this up in detail for the tier 2 section...


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 15 posts ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: Bing [Bot] and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu