LinHES Forums
http://forum.linhes.org/

R5E50 Install - Missing /etc/modprobe.conf altogether
http://forum.linhes.org/viewtopic.php?f=6&t=13347
Page 1 of 2

Author:  strick1226 [ Sun Jan 07, 2007 5:42 am ]
Post subject:  R5E50 Install - Missing /etc/modprobe.conf altogether

OK, I followed tjc's guide, and have my system running R5E50.

I modified the recording profiles for my PVR-150's to 720x480, and guessed bitrate 8000 min/max, as I'm not sure what else to do. That fixed the major clipping/tearing issue- thanks!

Now I'm trying to determine just what is happening that's causing occasional blips/stuttering and pixelation.

In an attempt to make things as smooth/jerk-free as possible, I performed a manual install and set /myth to an XFS partition on a new Seagate 7200.10 16MB 320GB SATA drive. hdparm -t seems to think it's a good 5-8 MB/s faster than my old WD3200JB IDE drive, so I guess that's a good sign...

I attempted to follow tjc's Known Issues tip #4 in regards to the TCL_M2523_SOMETHING_E_fix.sh script and discovered I don't actually have a modprobe.conf.

This may sound stupid--but is this normal? I don't think I was able to get my 3rd PVR-150 (with this buggy chipset) to work without a modprobe.conf on R5D1, especially in that it needed a specific option set to work correctly.

If this isn't right, then how do I create a modprobe.conf ?


For what it's worth, here are the details of my ivtv config in dmesg:

Code:
ivtv:  ==================== START INIT IVTV ====================
ivtv:  version 0.8.2 (tagged release) loading
ivtv:  Linux version: 2.6.18-chw-13 SMP preempt mod_unload 586 gcc-4.1
ivtv:  In case of problems please include the debug info between
ivtv:  the START INIT IVTV and END INIT IVTV lines, along with
ivtv:  any module options, when mailing the ivtv-users mailinglist.
ivtv0: Autodetected Hauppauge card (cx23416 based)
ACPI: PCI Interrupt 0000:02:04.0[A] -> GSI 20 (level, low) -> IRQ 21
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
usb 2-2: new full speed USB device using uhci_hcd and address 3
usb 2-2: configuration #1 chosen from 1 choice
lirc_dev: IR Remote Control driver registered, at major 61

lirc_mceusb2: Philips eHome USB IR Transciever and Microsoft MCE 2005 Remote Con
trol driver for LIRC v0.26
lirc_mceusb2: Daniel Melander <lirc@rajidae.se>, Martin Blatter <martin_a_blatte
r@yahoo.com>
usb 2-2: reset full speed USB device using uhci_hcd and address 3
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
lirc_dev: lirc_register_plugin: sample_rate: 0
lirc_mceusb2[3]: Philips eHome Infrared Transceiver on usb2:3
usbcore: registered new driver lirc_mceusb2
tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
tveeprom 0-0050: Hauppauge model 26132, rev G1B2, serial# 9545781
tveeprom 0-0050: tuner model is TCL M2523_5N_E (idx 112, type 50)
tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 0-0050: audio processor is CX25841 (idx 35)
tveeprom 0-0050: decoder processor is CX25841 (idx 28)
tveeprom 0-0050: has no radio, has IR remote
ivtv0: Autodetected Hauppauge WinTV PVR-150
ivtv0: reopen i2c bus for IR-blaster support
tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
cx25840 0-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 0-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: Encoder revision: 0x02050032
ivtv0: Registered device video0 for encoder MPEG
ivtv0: Registered device video32 for encoder YUV
ivtv0: Registered device vbi0 for encoder VBI
ivtv0: Registered device video24 for encoder PCM audio
tuner 0-0061: type set to 50 (TCL 2002N)
ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
ivtv:  ======================  NEXT CARD  ======================
ivtv1: Autodetected Hauppauge card (cx23416 based)
ACPI: PCI Interrupt 0000:02:06.0[A] -> GSI 22 (level, low) -> IRQ 22
ivtv1: Unreasonably low latency timer, setting to 64 (was 32)
ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #1)
cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #1)
cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #1)
tveeprom 1-0050: Hauppauge model 26032, rev C199, serial# 8181677
tveeprom 1-0050: tuner model is TCL 2002N 5H (idx 99, type 50)
tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 1-0050: audio processor is CX25841 (idx 35)
tveeprom 1-0050: decoder processor is CX25841 (idx 28)
tveeprom 1-0050: has no radio, has IR remote
ivtv1: Autodetected Hauppauge WinTV PVR-150
ivtv1: reopen i2c bus for IR-blaster support
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #1)
cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #1)
cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #1)
ivtv1: Encoder revision: 0x02050032
ivtv1: Registered device video1 for encoder MPEG
ivtv1: Registered device video33 for encoder YUV
ivtv1: Registered device vbi1 for encoder VBI
ivtv1: Registered device video25 for encoder PCM audio
tuner 1-0061: type set to 50 (TCL 2002N)
ivtv1: Initialized Hauppauge WinTV PVR-150, card #1
ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 17 (level, low) -> IRQ 16
ACPI: PCI Interrupt 0000:02:05.0[A] -> GSI 21 (level, low) -> IRQ 23
ivtv:  ======================  NEXT CARD  ======================
ivtv2: Autodetected Hauppauge card (cx23416 based)
ACPI: PCI Interrupt 0000:02:07.0[A] -> GSI 23 (level, low) -> IRQ 20
ivtv2: Unreasonably low latency timer, setting to 64 (was 32)
ivtv2: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #2)
cx25840 3-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #2)
cx25840 3-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #2)
tveeprom 3-0050: Hauppauge model 26032, rev C199, serial# 7783754
tveeprom 3-0050: tuner model is TCL 2002N 5H (idx 99, type 50)
tveeprom 3-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 3-0050: audio processor is CX25841 (idx 35)
tveeprom 3-0050: decoder processor is CX25841 (idx 28)
tveeprom 3-0050: has no radio, has IR remote
ivtv2: Autodetected Hauppauge WinTV PVR-150
ivtv2: reopen i2c bus for IR-blaster support
tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #2)
cx25840 3-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #2)
cx25840 3-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #2)
ivtv2: Encoder revision: 0x02050032
ivtv2: Registered device video2 for encoder MPEG
ivtv2: Registered device video34 for encoder YUV
ivtv2: Registered device vbi2 for encoder VBI
ivtv2: Registered device video26 for encoder PCM audio
tuner 3-0061: type set to 50 (TCL 2002N)
ivtv2: Initialized Hauppauge WinTV PVR-150, card #2
ivtv:  ====================  END INIT IVTV  ====================


Any ideas on where to go from here? I could try checking out my old modprobe.conf from the R5D1 drive, but I didn't want to do something that would mess up the settings on the new box without checking first...

Thanks in advance!!

Author:  slowtolearn [ Sun Jan 07, 2007 8:06 am ]
Post subject:  Re: R5E50 Install - Missing /etc/modprobe.conf altogether

strick1226 wrote:
Code:
tuner 0-0061: type set to 50 (TCL 2002N)
tuner 1-0061: type set to 50 (TCL 2002N)
tuner 3-0061: type set to 50 (TCL 2002N)

What problem are you having? According to your dmesg output, your 3 150s are being set correctly (type set to 50).

Author:  strick1226 [ Sun Jan 07, 2007 8:24 am ]
Post subject: 

Lots of pixelation in flickering while watching LiveTV, specifically--but not constantly. It appears to happen the most when a mythcommflag happens, as when I disable it, it seems to go away. Possibly not enough CPU... but then again, it happens every once in a while, for no reason that I can see.

I have two older PVR-150 cards, and a more recent one with the supposedly troublesome Toshiba chipset or something. That's why I was trying to make sure the modprobe.conf had the right options listed--and that's when I discovered there IS no modprobe.conf on my setup!?


Could it be a lack of CPU?

I checked top, and it looks like "mythfrontend" averages ~30% watching LiveTV. mythbackend is around 6%.

There's also another ~8.5% for "ivtv-enc-vbi" every active tuner.
(I need that CC support--one of the biggest reasons for moving to R5E50 for us, so I can't disable that.)

Still, watching a LiveTV and recording another program in the backgrounds looks to take mythfrontend up to 35% + 17% for two vbi-enc + 12% for the backend = 64 %. Doesn't sound like too much, does it?

Perhaps my 2.2 GHz P4 isn't enough for this setup. If so, I can pick up a 3.2 GHz Prescott for the box, perhaps, and have it double as a space heater :) But I can't afford to switch over to a new system requiring DDR2 etc.

Author:  L0o0ky [ Thu Jan 25, 2007 5:23 pm ]
Post subject: 

Strick1226,

I'm running a pvr500...

I was having issues with distortions and flickering in the recorded image--wasn't just in the playback. I was able to confirm this by playing the recording in vlc on my pc...

Check out the info here:
http://mysettopbox.tv/phpBB2/viewtopic.php?t=13257

Author:  strick1226 [ Fri Jan 26, 2007 8:49 am ]
Post subject: 

L0o0ky,

Neat--missed this one! I'll give it a whirl and report the results.

Thanks for the reply!

Author:  L0o0ky [ Fri Jan 26, 2007 10:21 am ]
Post subject: 

strick1226 wrote:
L0o0ky,

Neat--missed this one! I'll give it a whirl and report the results.

Thanks for the reply!


To give you an update...

It seems to have helped with most channels--except not completely on channel 7(discovery channel--comcast cable). The flickering has almost disappeared there, but it's not gone. I'm still digging into this one myself...

thanks,

Author:  jmairs [ Sun Jan 28, 2007 11:10 am ]
Post subject: 

I too was missing the modproble.conf. I created it by hand and ran

CL_M2523_SOMETHING_E_fix.sh. I'm also missing /dev/lirc0 so I can't get my Hauppauge Silver remote to work. That remote plugs into the back of the 250 card.

Author:  tjc [ Sun Jan 28, 2007 11:33 am ]
Post subject: 

jmairs wrote:
I'm also missing /dev/lirc0 so I can't get my Hauppauge Silver remote to work. That remote plugs into the back of the 250 card.

(This is R5E50 right? Things will differ under older versions.) Run the lirc-reconfig.sh script by hand. Tell it Hauppauge for the card and the appropriate remote type. Then go and make sure that your /etc/lirc/hardware.conf looks like this:
Code:
root@black2:/etc/lirc# cat hardware.conf
# /etc/lirc/hardware.conf
#
# Arguments which will be used when launching lircd
LIRCD_ARGS=""

#Don't start lircmd even if there seems to be a good config file
START_LIRCMD=false

#Try to load appropriate kernel modules
LOAD_MODULES=true

# Run "lircd --driver=help" for a list of supported drivers.
DRIVER="default"
# If DEVICE is set to /dev/lirc and devfs is in use /dev/lirc/0 will be
# automatically used instead
DEVICE="/dev/lirc0"
MODULES="lirc_dev lirc_i2c"

Now lets look at /dev:
Code:
root@black2:/dev# ls -al /dev/lirc*
crw-rw---- 1 root video 61, 0 Jan 27 17:25 /dev/lirc0
crw-rw---- 1 root video 61, 1 Jan 27 17:25 /dev/lirc1
srw-rw-rw- 1 root root      0 Jan 27 20:04 /dev/lircd

and your processes:
Code:
root@black2:/dev# pgrep -fl lirc
2834 lirc_dev
2837 lirc_dev
5792 /usr/sbin/lircd --driver=default --device=/dev/lirc0

BTW - I've got two cards which is why there are multiple lirc devs shown here. If you don't have the device and/or the process try modprobing the lirc_dev and lirc_i2c modules...

Oh, and double check that you're plugged into the right connector (the black 3/32" one rather than the silver 1/8" one) and that the plug is all the way in. You may need to nip a corner off the plastic on the plug so it won't hit the case.

Author:  jmairs [ Sun Jan 28, 2007 12:29 pm ]
Post subject: 

Here' what it looks like

Code:
root@mythtv:/etc/lirc# ls -al /dev/lirc*
srw-rw-rw- 1 root root 0 Jan 28 11:52 /dev/lircd
root@mythtv:/etc/lirc# pgrep -fl lirc
3165 /usr/sbin/lircd --device=/dev/lirc0


How do I modprobe lirc_dev and lirc_i2c?

Author:  jmairs [ Sun Jan 28, 2007 12:31 pm ]
Post subject: 

got it

modprobe lirc_dev
modprobe lirc_i2c

/dev/lirc0 now exists!

Author:  tjc [ Sun Jan 28, 2007 1:30 pm ]
Post subject: 

Replacing your truncated hardware.conf with the one I posted should cure the problem for future reboots...

Author:  jmairs [ Sun Jan 28, 2007 1:48 pm ]
Post subject: 

I did. Thanks for your time. After I rebooted my HDTV channels were actually loaded (see other problem below)

http://www.mysettopbox.tv/phpBB2/viewtopic.php?t=13895

but I rebooted again because I'm also trying to get a serial cable to control my directtv receiver vice IR (cuz its slow) and the channels are gone again.

Author:  JoeMcCracken [ Sun Feb 25, 2007 1:39 pm ]
Post subject: 

TJC -- Maybe you could offer some help on my lirc problem. Same hauppauge remote.

I'm basically in the same boat as the others. I only have /dev/lircd showing up. After modifying the hardware.conf file to match your suggestion, I now am getting lirc_dev and lirc_i2c appearing as loaded modules (lsmod shows them). However, I am still only getting /dev/lircd showing up. No lirc or lirc0 device. I will try a long poweroff and see if theres a problem with corrupted firmware in the pvr-150 causing this problem. Currently a clean install of R5E50. The remote worked in R4D1, although sometimes it would stop working and require a long poweroff. Hopefully this is the same problem...
[/code]

Author:  tjc [ Sun Feb 25, 2007 1:52 pm ]
Post subject: 

What does: lsmod | grep ir show?

Author:  JoeMcCracken [ Sun Feb 25, 2007 2:36 pm ]
Post subject: 

Code:
root@mythtv:/dev# lsmod |grep lirc
lirc_i2c               12420  0
lirc_dev               16628  1 lirc_i2c
i2c_core               20864  22 cx88xx,lirc_i2c,dvb_bt8xx,nxt6000,mt352,sp887x,dst,bttv,dvb_pll,cx24110,or51211,zl10353,lgdt330x,nvidiafb,wm8775,cx25840,tuner,i2c_viapro,ivtv,i2c_algo_bit,tveeprom,nvidia


The modules seem to be loaded.

Page 1 of 2 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/