[mythtv-users] Jarod's FC3 how to

[Wayne Steenburg]

On Tue, 2004-11-30 at 13:57 -0800, Marc Infield wrote:
> Hi,
> 
> I am pretty much a beginner but I was able to get through Jarod's FC2 
> tutorial and am happily running mythtv at home. Thank you for making it 
> possible. :)
> I am trying out the FC3 install on a spiffy new box and have run into a 
> couple wording things and of course some problems. Probably my errors, 
> but I just thought I would share my pain.
> 
> Section 3 wording:
> -SQL Database Server (selecting only mysql-server under the "Details" 
> section)
> MYSQL has it's own entry in FC3
> 
> -Kernel Development (if you want/need to compile any of your own 
> drivers)
> this no longer exists in FC3
> 
> Section 4 wording:
> -When prompted, you'll have to type in "Yes, do as I say!" to go ahead 
> with this change.
> I did not get the "Yes, do as I say!" prompt, I just got the [Y/n] 
> prompt. I am doing a clean install.
> 
> And this may just be me or my hardware but . . .
> 
> -When i ran # apt-get update && apt-get dist-upgrade
> the first time I ran it it timed out on two packages, (libraw1394 and 
> xml-common). I ran it second time and it updated with three errors:
> 
> 1)
> sgml rpm 		warning:/etc/sgml/catalog saved as /etc/sqml/catalog.rpmsave
> 
> 2)
> xml-common 	warning:/etc/xml/catalog saved as /etc/xml/catalog.rpmsave
> 
> 3)
> warning: /usr/share/sgml/docbook/xmlcatalog saved as
> /usr/share/sgml/docbook/xmlcatalog.rpmsave
> Failed to remove entry from /etc/sgml/catalog
> Failed to remove entry from /etc/sgml/catalog
> Failed to remove entry from /etc/sgml/catalog
> Failed to remove entry from /etc/sgml/catalog
> Failed to remove entry from /etc/sgml/catalog
> Failed to remove entry from /etc/sgml/catalog
> Failed to remove entry from /etc/sgml/catalog
> Failed to remove entry from /etc/sgml/catalog
> Failed to remove entry from /etc/sgml/catalog
> /var/tmp/rpm-tmp.92483: line 59: [: : integer expression expected
> 
> 
> - I then restart my machine and now get some errors in my boot log.
> 
> Nov 30 11:28:31 localhost lm_sensors: Starting up sensors:
> Nov 30 11:28:31 localhost lm_sensors: Can't access procfs/sysfs file
> Nov 30 11:28:31 localhost lm_sensors:
> Nov 30 11:28:31 localhost lm_sensors: Unable to find i2c bus 
> information;
> Nov 30 11:28:31 localhost lm_sensors: For 2.6 kernels, make sure you 
> have mounted sysfs and done
> Nov 30 11:28:31 localhost lm_sensors: 'modprobe i2c_sensor'!
> Nov 30 11:28:31 localhost lm_sensors: For older kernels, make sure you 
> have done 'modprobe i2c-proc'!
> Nov 30 11:28:31 localhost rc: Starting lm_sensors:  failed
> 
> -Then I ran
> # apt-get install kernel#2.6.9-1.681_FC3
> 
> When I reboot the machine with the new Kernel I get a error:
> hdb: drive not ready for command.
> 
> But it starts fine with the old kernel.?
> 
> Here is my system:
> mobo: Chaintech 7NJL6
> CPU: Athlon 3200
> Video: Chaintech Geforce FX 5200
> Sound: Chaintech AV710 7.1
> Memory: 1x 512 DDR 3200
> Drives: 2 X 200GB barracuda 7200 (formatted the video partitions as fsx)
> 
> That's where I am for now.
> 
> Thanks,
> -marc
> 
> _______________________________________________________
> Marc Infield                        <marc(AT)InfieldDesign.com>
> 
I was helping a friend with a FC3/MythTV install last night.  I also
couldn't find gnome-alsa mixer at Freshrpms.net for Core 3.  I added
freshrpms to my sources.list and manually searched the ftp server with
no success. 

On every machine FC3 machine I've setup I've also gotten the warnings
for /etc/sgml/catalog and /etc/xml/catalog those are just letting you
know that apt is saving the old versions of those files in case you
should need them.  I've also gotten the "/var/tmp/rpm-tmp.92483: line
59: [: : integer expression expected". I have no idead what this is
about, but I haven't had any issues.  

The errors about lm_sensors is because the service is automatically
started but needs to be configured first.  You can either set it up ( I
believe you just run sensors-config and modify /etc/modprobe.conf
and /etc/rc.local with the output.  It walks you through it.) or disable
the service.  

I'm not sure about your problem with the kernel upgrade. Perhaps a
filesystem label problem?  Check /var/log/messages for information
regarding the failure.

Wayne Steenburg