UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi, I hope you could understand my poor english. I'm running a Kubuntu hardy with this huge problem: input peripherals are randomly associated with the devices in /proc/bus/input/devices, but they work only if associated with one of them. Here the example, this is a good one:
Everything works: I can use my remote for the tvcard, the mouse works and the pc speaker do. Sometimes the remote is in "...event6" and "...input6", the mouse in "....input5" and "...event5" and when it happens they don't work. Sometimes the pc speaker steal the place of the remote or the mouse, so I have wesnoth without sound and the mouse or the remote broken.
Is there something I can do to stop this?
Has this happened with other distrubutions that you have tried?....if so....I suspect you have the wrong bios options
2) have you got your motherboard manual or can you download it....so you can see the various options in your bios
3) what is the name of the bios supplier? award or phoenix etc
4) what is the name of your bootloader? is it lilo or grub or what?
5) assuming its grub you add (with root powers so save works).to your /boot/grub/menu.lst kernel line at end..........pci=routeirq
but please be aware that we can only make one change at a time.
6) also you may have a interrupt conflict.....a conflict is more serious than a interrupt that is shared.
conflicts normally occur if your bios is set to pic and not apic
open a shell and run commands
Code:
su
cat /proc/interrupts
if you see 2 or more devices on the same line you either have a share or conflict but the lines at the bottom of the command as above will tell us so post the output please
Do you see something wrong? It's the first time it happens, I have used for a long time suse (9.1,9.2,9.3) , kanotix and pclinuxos (0.92,0.93,2007,2008). My bios is made by phoenix.
I have grub, but I don't understand this:
Quote:
but please be aware that we can only make one change at a time.
What does it mean? I have to change only one kernel line at a time?
Last edited by sloteel; 06-05-2008 at 06:22 AM.
Reason: I forgot an answer
title Ubuntu 8.04, kernel 2.6.24-18-rt (recovery mode)
root (hd0,4)
kernel /boot/vmlinuz-2.6.24-18-rt root=UUID=50b20193-b0fe-4221-a90d-5d26c129dde8 ro single pci=routeirq
initrd /boot/initrd.img-2.6.24-18-rt
title Ubuntu 8.04, memtest86+
root (hd0,4)
kernel /boot/memtest86+.bin
quiet
title Other operating systems:
root
title Windows XP Home Edition
root (hd0,0)
chainloader +1
savedefault
makeactive
Do I write it right?
By the way, I have booted 2 times the generic kernel and 2 times the rt kernel: the generic one seems to work now, the rt doesn't: maybe this option is not supported by that kernel?
did you write it correctly....yes....your observations are good as well...I do not use ubuntu but I have requests for you.
1) from now on ignore the recovery kernels pls
2) try only the generic and whatever the rt is....btw in your package manager there should be a description of rt...if you find it let me know pls....it may help others as well
now for both...kernels...upload your /var/log/syslog to a online site that you can link to....if you do not have one...use www.ripway.com and its free.
this is more work for you...and for others to read....but these logs tend to be large and may turn off others reading it so the link posted here is easier on the eye if you agree?
3) for each kernel I would like a link for the output of your cat /proc/interrupts AND I would like a link for each for the output of lsmod command....this lsmod command may not be useful...but we won't know until we read it eh?
4) can I suggest you name each file something like
gen-syslog and rt-syslog
gen-irq (for interrupts) and rt-irq
gen-lsmod and rt-lsmod
5) Please remove that grub parameter from your (recovery mode) kernel kernel lines
Now the other questions you ask and my reasons are:
to troubleshoot...you only want to make change at a time...so you know what u did and so know what has changed the effects.
2) did you have the same issue with the other distros?......what was wrong with them if it did not? as if I or others can not help....it may not be you....I suspect it never was...but your choice of distro....leaping ahead pclinuxos is based on mandriva....heh heh
3) knowing it is phoenix allows us to think about whether we should flash it...and where to get the flash files.....but altho I am experienced at it....it is the last resort and not recommended in case we can solve it for software issues.
again...if your other distros did not have the problem....it is not your bios...but until you answer I am not sure ok?
First of all, thanks a lot for you help, really. Then, here is the description of the rt-kernel:
Quote:
Linux kernel image for version 2.6.24 on Ingo Molnar's full real time preemption patch (2.6.24.3-rt3)
This package contains the Linux kernel image for version 2.6.24 on
Ingo Molnar's full real time preemption patch (2.6.24.3-rt3).
Also includes the corresponding System.map file, the modules built by the
packager, and scripts that try to ensure that the system is not left in an
unbootable state after an update.
Supports Generic processors.
RT kernel
You likely do not want to install this package directly. Instead, install
the linux-rt meta-package, which will ensure that upgrades work
correctly, and that supporting packages are also installed.
No, it still doesn't work, but maybe I forgot something important:
To make the ircommand work I put in rc.local this line:
/usr/sbin/lircd -H dev/input -d /dev/input/event5
I tried to erase "-d /dev/input/event5" and reboot: even with the mouse in "...input5" (the place that the remote should have) the mouse itself works.... but the ircommand doesn't.
Following the guide I use to configure the tvcard to indicate the device is a condition not escapable. Maybe this is the root of the problem? I have used this trick in every distro I got.
remove all work you did on attempt for pcskr since it failed.
2) you won't like it but please try this
remove that rc.local line that fixes ir device to event5
reboot
run your cat /proc/bus/input/devices command to see what events are free
run manually /usr/sbin/lircd -H dev/input -d /dev/input/eventN where N is a free number
And irKick said that there weren't any remotes available. So I lunched "sudo /usr/sbin/lircd -H dev/input -d /dev/input/event5" and it stars to work.
I know that /dev/input/event5 is the place where it always worked but after 10 boots I couldn't have it in another place! But I think that this is the problem. Maybe I should write a script that read the content of /proc/bus/input/devices and sets the line I use to start lircd...
I hopefully solved the problem with a very rough solution. First, I blacklisted pcspkr: I don't really need it, and its presence is going to complicate the situation. Then, I made this script:
Quote:
#!/bin/bash
STRINGA=$(/bin/cat /proc/bus/input/devices | /bin/grep -n saa)
I="4"
if [[ $STRINGA != '41:N: Name="saa7134 IR (LifeView/Typhoon Fl"' ]]
then
I="5"
fi
/usr/sbin/lircd -H dev/input -d /dev/input/event$I
This script start lircd with "-d /dev/input/event4" if the remote is in event4, "-d /dev/input/event5" if it is elsewhere, but without the pc speaker I'm confident that the remote will be only in input4 or input5. So I copied this in /usr/bin and I wrote /usr/bin/remotestart (the name of the script) in rc.local. Now I'm studying bash programming to upgrade the script and make it handle more situations.
Aus9, thanks a lot for your time, your help and your learnings.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.