| Author |
Message |
|
Flavor
|
 Posted: Sun Sep 09, 2007 11:11 pm |
|
|
Joined: Wed Oct 04, 2006 1:25 pm
Posts: 34
|
|
The whole Schedules Direct deal has forced me to finally upgrade to a newer version. I can't recall offhand the version of KnoppMyth that I had previously, but it was using MythTV 0.19.
Anyway, it seems to be running alright, except I've been spinning my wheels for hours now trying to get my Packard Bell remote working. I had it working fine before, but it's all screwy now.
I have the receiver connected to serial port 0. That used to be /dev/ttyS0, but now that doesn't exist. I also get messages from lirc telling me to do a setserial uart none on /dev/ttyS0, but I can't comply since it's not there.
I finally decided to compile lirc myself, but I've run into a problem there, also. It gets to the point of wanting to #include <linux/i2c-id.h>. The issue now is that file doesn't exist. It's a symlink to /root/v4l-dvb-SOMTHING/linux/include/linux/i2c-id.h. I suppose that existed on the machine that was used to create R5F27, but it never made it to mine.
So, does anyone have any good ideas on how I should compile lirc or even better yet, how I can just get the installed R5F27 version configured to use my serial port receiver?
Last edited by Flavor on Mon Sep 10, 2007 8:00 am, edited 1 time in total.
|
|
| Top |
|
 |
|
mjl
|
Posted: Mon Sep 10, 2007 5:53 am |
|
|
Joined: Sun Jun 12, 2005 10:55 pm
Posts: 3161
Location:
Warwick, RI
|
|
Hi,
Does your machine have an actual 9 pin serial connector? Some newer boxes, (sff) don't. Even some of the older sff don't as I have a GateWay in that situation. It actually does have a mb connector but isn't enabled by the manufacturer.. parts missing.
Also the ttyS0 could be an internal modem and if you have a connector that would be most likely ttyS1. ttyS0 &1 should be default irq 4 & 3 and there not be a need to run setserial.
Mike
|
|
| Top |
|
|
|
Flavor
|
Posted: Mon Sep 10, 2007 7:58 am |
|
|
Joined: Wed Oct 04, 2006 1:25 pm
Posts: 34
|
It's an actual 9-pin serial port. The remote/receiver are just like this
http://www.overclockersclub.com/reviews/packbellremote/
I'm a bit surprised that my topic got moved. My main problem was that the kernel headers were not properly installed on the new R5F27 release. Perhaps my topic title should have been about that.
There isn't an internal modem on my motherboard. When I was running my previous KnoppMyth (for about a year), I had the PBell remote working fine on /dev/ttyS0. The hardware/bios hasn't changed since then. I just installed a new KnoppMyth.
there are NO /dev/ttyS# nodes at all, now. I think it has to do with the switch to udev. Also, I believe that the setserial business wasn't for changing the port/irq. I think it was for setting the UART params.
|
|
| Top |
|
|
|
Flavor
|
Posted: Mon Sep 10, 2007 8:54 am |
|
|
Joined: Wed Oct 04, 2006 1:25 pm
Posts: 34
|
|
Just a quick update...
1) I changed the topic's title to better reflect the problem of missing kernel headers.
2) I think that my previous KnoppMyth was R5D1. I had run that for just over a year. R5D1 didn't properly configure my PBell remote, either. I had to get it working then, too. So, I had a completely working R5D1 setup, and I upgraded to R5F27 and for the most part, it's just my remote that's a problem. That's actually a big improvement over last time when I had issues with my video and my widescreen.
|
|
| Top |
|
|
|
cecil
|
Posted: Mon Sep 10, 2007 11:29 am |
|
 |
| Site Admin |
Joined: Fri Sep 19, 2003 6:37 pm
Posts: 2659
Location:
Whittier, Ca
|
The kernel headers aren't missing. I believe the Packard Bell remote may use the lirc_gpio which is broken due to kernel changes. You might be able to use it however. Take a look at this: http://bugs.archlinux.org/task/7660?pagenum=11
|
|
| Top |
|
|
|
Flavor
|
Posted: Mon Sep 10, 2007 11:55 am |
|
|
Joined: Wed Oct 04, 2006 1:25 pm
Posts: 34
|
|
| Top |
|
|
|
cecil
|
Posted: Mon Sep 10, 2007 12:45 pm |
|
|
| Site Admin |
Joined: Fri Sep 19, 2003 6:37 pm
Posts: 2659
Location:
Whittier, Ca
|
Flavor wrote: Why do you say that the header's aren't missing?
I only packaged the distribution. Did you even read my statements about lirc_gpio. Having the full source or doing a make kernel-links w/ v4l-dvb isn't going to get your remote to work if it uses the lirc_gpio module. Yes, the kernel source is the same.
|
|
| Top |
|
|
|
Flavor
|
Posted: Mon Sep 10, 2007 1:54 pm |
|
|
Joined: Wed Oct 04, 2006 1:25 pm
Posts: 34
|
cecil wrote: I only packaged the distribution. Did you even read my statements about lirc_gpio. Having the full source or doing a make kernel-links w/ v4l-dvb isn't going to get your remote to work if it uses the lirc_gpio module. Yes, the kernel source is the same.
First of all, thank you very much for doing the packaging work. It's a huge help to have such a nice distro.
I don't think that my serial receiver needs lirc_gpio. I think it uses lirc_serial, but maybe those aren't mutually exclusive. I don't think I ever used lirc_gpio on R5D1, but I can't be 100% sure.
I assume that my problem isn't specific to the Packard Bell receiver. I would assume that anyone using a serial-port receiver would have similar issues, but I could be wrong about that.
I have no idea if building lirc myself will help anything, but I know that the config script has support for all my serial needs. I don't know much about udev and how it handles this stuff.
Thanks for the help.
|
|
| Top |
|
|
|
Flavor
|
Posted: Tue Sep 11, 2007 11:49 am |
|
|
Joined: Wed Oct 04, 2006 1:25 pm
Posts: 34
|
I just wanted to give an update. I got my remote working last night.
I got ftp://knoppmyth.net/R5/v4l-dvb-b5798581eeb3.tar.bz2, then I downloaded the CVS source of lirc (0.8.3?) and compiled it.
I still couldn't get things to work properly. I kept getting annoyed that serial_core, 8250, and 8250_pnp modules kept getting loaded and I'd have to rmmod them. I removed them from /lib/modules so that they wouldn't get loaded at boot time. After that, it worked.
I'm not sure, but it may have worked with the KnoppMyth-supplied binaries for lirc_serial and lirc_dev. All I know is that it works now and that ftp://knoppmyth.net/R5/v4l-dvb-b5798581eeb3.tar.bz2 satisfied my missing kernel headers.
My guess is that 8250 was messing with the serial port somehow and now that isn't happening.
|
|
| Top |
|
|
|
randomhtpcguy
|
Posted: Thu Sep 20, 2007 7:43 pm |
|
|
Joined: Mon Nov 07, 2005 10:09 am
Posts: 153
|
|
In recent versions, I have not need to recompile lirc or anything.
I chose RCA8in1 using the lirc script provided. That sets up the correct modules and the serial port in hardware.conf... then i just copy my lircd.conf and lircrc and it works. There is a setserial ttyS0 command in /etc/init.d/bootmisc.sh but i'm not sure if its needed...
also, i comment out the reference to ttyS0 in the serial mouse section of xorg.conf
However, after upgrading from R5d1, my packard bell will not work either.
i will try to disable these modules you mention....
I think you meant to say that to disable them you comment (#) them out in /etc/modules
edit: commenting out these three modules didn't change things... still doesn't work.
Last edited by randomhtpcguy on Fri Sep 21, 2007 2:55 pm, edited 1 time in total.
|
|
| Top |
|
|
|
tdevittc
|
Posted: Thu Sep 20, 2007 10:21 pm |
|
|
Joined: Thu Sep 06, 2007 11:37 pm
Posts: 2
|
|
Hey...
Just wanted to second Flavors reply that the linux headers have a dead symlink. This file probably exists on the machine that the headers were packaged on. This is what I see on my system as well...
lrwxrwxrwx 1 root src 55 Sep 17 12:48 /usr/src/linux-headers-2.6.18-chw-13/include/linux/i2c-id.h -> /root/v4l-dvb-1387dc197077/linux/include/linux/i2c-id.h
And of course this file doesn't exist for me.
-T
|
|
| Top |
|
|
|
Flavor
|
Posted: Fri Sep 21, 2007 7:59 am |
|
|
Joined: Wed Oct 04, 2006 1:25 pm
Posts: 34
|
randomhtpcguy wrote: i will try to disable these modules you mention....
I think you meant to say that to disable them you comment (#) them out in /etc/modules
No, actually, when I did that, they still got loaded. I'm not sure what was loading them. I went into /lib/modules/..., found the modules in question, and renamed them so that they couldn't load.
|
|
| Top |
|
|
|
randomhtpcguy
|
Posted: Fri Sep 21, 2007 3:58 pm |
|
|
Joined: Mon Nov 07, 2005 10:09 am
Posts: 153
|
Code: oot@mythtvmaster:/lib/modules/2.6.18-chw-13# locate 8250
/dev/.udev/failed/devices@platform@serial8250
/lib/modules/2.6.18-chw-13/kernel/drivers/serial/8250.ko
/lib/modules/2.6.18-chw-13/kernel/drivers/serial/8250_pci.ko
/lib/modules/2.6.18-chw-13/kernel/drivers/serial/8250_pnp.ko
/sys/bus/platform/devices/serial8250
/sys/bus/platform/drivers/serial8250
/sys/bus/platform/drivers/serial8250/bind
/sys/bus/platform/drivers/serial8250/module
/sys/bus/platform/drivers/serial8250/serial8250
/sys/bus/platform/drivers/serial8250/unbind
/sys/devices/platform/serial8250
/sys/devices/platform/serial8250/bus
/sys/devices/platform/serial8250/driver
/sys/devices/platform/serial8250/modalias
/sys/devices/platform/serial8250/power
/sys/devices/platform/serial8250/power/state
/sys/devices/platform/serial8250/power/wakeup
/sys/devices/platform/serial8250/subsystem
/sys/devices/platform/serial8250/tty:ttyS2
/sys/devices/platform/serial8250/tty:ttyS3
/sys/devices/platform/serial8250/uevent
/sys/module/8250
/sys/module/8250/parameters
/sys/module/8250/parameters/nr_uarts
/sys/module/8250/parameters/share_irqs
/sys/module/8250/refcnt
/sys/module/8250/sections
/sys/module/8250/sections/.bss
/sys/module/8250/sections/.data
/sys/module/8250/sections/.exit.text
/sys/module/8250/sections/.gnu.linkonce.this_module
/sys/module/8250/sections/.init.text
/sys/module/8250/sections/.rodata
/sys/module/8250/sections/.rodata.str1.1
/sys/module/8250/sections/.rodata.str1.4
/sys/module/8250/sections/.strtab
/sys/module/8250/sections/.symtab
/sys/module/8250/sections/.text
/sys/module/8250/sections/__ksymtab
/sys/module/8250/sections/__ksymtab_strings
/sys/module/8250/sections/__param
/sys/module/8250_pnp
/sys/module/8250_pnp/refcnt
/sys/module/8250_pnp/sections
/sys/module/8250_pnp/sections/.bss
/sys/module/8250_pnp/sections/.data
/sys/module/8250_pnp/sections/.exit.text
/sys/module/8250_pnp/sections/.gnu.linkonce.this_module
/sys/module/8250_pnp/sections/.init.text
/sys/module/8250_pnp/sections/.rodata
/sys/module/8250_pnp/sections/.rodata.str1.1
/sys/module/8250_pnp/sections/.strtab
/sys/module/8250_pnp/sections/.symtab
/sys/module/8250_pnp/sections/.text
Code: class@scsi_device@3:0:0:0 devices@platform@serial8250
devices@pci0000:00@0000:00:00.1 devices@platform@vesafb.0
devices@pci0000:00@0000:00:00.2 devices@pnp0@00:01
devices@pci0000:00@0000:00:00.3 devices@pnp0@00:05
devices@pci0000:00@0000:00:01.0 devices@pnp0@00:06
devices@pci0000:00@0000:00:05.0 devices@pnp0@00:07
devices@platform@i8042@serio1 devices@pnp0@00:08
devices@platform@pcspkr
|
|
| Top |
|
|
|
Flavor
|
Posted: Fri Sep 21, 2007 4:09 pm |
|
|
Joined: Wed Oct 04, 2006 1:25 pm
Posts: 34
|
Yeah, okay.
Unfortunately, I can't check that machine right now, but here's what I think I did (based on your paste).
Code: cd /lib/modules/2.6.18-chw-13/kernel/drivers/serial/
mv 8250.ko 8250.ko.old
mv 8250_pnp.ko 8250_pnp.ko.old
mv serial_core.ko serial_core.ko.old Then reboot. Then try to Code: modprobe lirc_serial
modprobe lirc_dev
|
|
| Top |
|
|
|
tdevittc
|
Posted: Fri Sep 21, 2007 11:30 pm |
|
|
Joined: Thu Sep 06, 2007 11:37 pm
Posts: 2
|
|
Another quick update. I came accross severl files named Kconfig that were dead sim links in the headers as well. Just FYI.
|
|
| Top |
|
|
View unanswered posts
View active topics
KnoppMyth 
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register