DISREGARD Re[2]: [mythtv-users] Fresh Install From Scratch

[Myth Man]

Hello,

I found the problem.

I forgot to re-introduce the "   export KERNEL=`uname -r`  " line
after reboot...
DOH!!!!

Although I still see that "ll /dev/video0" still shows 'root root'
the rest seems to be back on track.





Saturday, December 20, 2003, 12:19:11 PM, you wrote:

MM> Hello,

MM> OK, I see where things went ker-flooey..

MM> "(Lines with $ as the prompt are executed as user mythtv, lines with #
MM> as the prompt are executed as root)."

MM> When I read the above line, I thought that Jarod was letting noobies
MM> know that, in a LINUX environment, # is root and $ is user.

MM> Reading it again, I realized that Jarod was telling that, IN HIS
MM> DOCUMENTION, # is root and $ is mythtv(user).

MM> So, looking at his docs again, with this in mind, I can see I did not
MM> screw up as I thought I had.

MM> But that leaves the question as to why, when I got to Step #11, why
MM> the modprob of ivtv did not work and there is no config entry ini
MM> /var/log/dmesg.  But sbin/lspci -v does show:

MM>         Subsystem: Hauppauge computer works Inc.: Unknown device 4000
MM>         Flags: bus master, medium devsel, latency 32, IRQ 11
MM>         Memory at f0000000 (32-bit, prefetchable) [size=64M]
MM>         Capabilities: <available only to root>


MM> So it appears that something was done, but not properly.

MM> Oh and a complete shutdown and reboot did not fix the problem.




MM> Saturday, December 20, 2003, 11:53:37 AM, you wrote:

MM>> Hello Myth,

MM>> Saturday, December 20, 2003, 11:40:40 AM, you wrote:

MM>>> Hello mythtv-users,

MM>>>   I am doing a completely virgin install of RH9 and MythTV using
MM>>>   Jarod's
MM>>> http://pvrhw.goldfish.org/tiki-page.php?pageName=rh9pvr250

MM>>>   Ran into a little snafu...

MM>>>   The RH9 install went fine.  I created a 'mythtv' user.  I then SU'd
MM>>>   to 'mythtv' to continue the rest of install.

MM>>>   Well, I couldn't go any further as mythtv, so I continued as root
MM>>>   until such time as I would switch back to mythtv user.  I figured
MM>>>   right before I did the apt-get mythtv-suite.

MM>>>   Well, suffice it to say, I forgot.  :^(

MM>>>   I have gone past that part as root.  And now I am at the spot where
MM>>>   I am configuring the ivtv drivers and it's not working.

MM>>>   As 'mythtv' I do a '/sbin/depmod -a' and I get

MM>>>  depmod: Can't open
MM>>> /lib/modules/2.4.20-24_31.rh9.at/modules.dep for writing

MM>>>   So, I am guessing that I have to be at 'mythtv' user from the get
MM>>>   go, just like it said in Jarod's docs.  Imagine that!  :^(

MM>>>   My question is, how can I get back to that point, w/o having to
MM>>>   whack everything and start over.  Or would that be the best course
MM>>>   of action?  Simply to whack the drive and start over.

MM>>>   Thanx...

  
MM>> UPDATE:

MM>> This is what happened when I tried to proceed as 'mythtv' user at
MM>> STEP #6:

MM>> [root at myth root]# su mythtv
MM>> [mythtv at myth root]$ cd /
MM>> [mythtv at myth /]$ rpm -ivh
MM>> http://atrpms.physik.fu-berlin.de/dist/rh9/atrpms-kickstart/atrpms-kickstart-19-1.rh9.at.i386.rpm
MM>> Retrieving
MM>> http://atrpms.physik.fu-berlin.de/dist/rh9/atrpms-kickstart/atrpms-kickstart-19-1.rh9.at.i386.rpm
MM>> error: cannot get exclusive lock on /var/lib/rpm/Packages
MM>> error: cannot open Packages index using db3 - Operation not permitted (1)
MM>> error: cannot open Packages database in /var/lib/rpm
MM>> [mythtv at myth /]$ 












-- 
Best regards,
 Myth                            mailto:mythtv at pln.cc