Re: Smileys don't animate [Unsolved again]
On 28/11/10 17:10:28, Barry Samuels wrote: I have found that creating a new browser profile has cured the problem on Firefox. That, however, is a bit of a nuisance as it means transferring bookmarks, re-installing add-ons etc. It would be nice to know what part of the profile is causing the problem so that it would be possible to correct it. The problem still occurs in Opera and Chromium though. Why should a problem like that affect different browsers in the same way? Well that 'cure' lasted less than 24 hours and the problem is back. What the hell is going on? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1291025022.903...@dataman1
Re: Smileys don't animate [Unsolved again]
On 29/11/10 10:21:56, Camaleón wrote: On Mon, 29 Nov 2010 10:03:42 +, Barry Samuels wrote: On 28/11/10 17:10:28, Barry Samuels wrote: I have found that creating a new browser profile has cured the problem on Firefox. That, however, is a bit of a nuisance as it means transferring bookmarks, re-installing add-ons etc. It would be nice to know what part of the profile is causing the problem so that it would be possible to correct it. The problem still occurs in Opera and Chromium though. Why should a problem like that affect different browsers in the same way? Well that 'cure' lasted less than 24 hours and the problem is back. What the hell is going on? We can't tell if you do not provide the requested data. Does it work using a proxy? Can you tell us the link? Greetings, -- Camaleón Going through hidemyass.com makes no difference - the smileys do not animate. If you mean the link to the page with the smileys: http://www.beemthere-donethat.org.uk/bbHpp/viewtopic.php? f=10t=180sid=531ee08ae92329873213f0568dd2830c It appears that only part of the GIF image file is being downloaded by the browser. If I save one of the non-animated smileys and compare it with a version that does animate then the size of the non-animated GIF is much smaller. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1291029245.1961...@dataman1
Re: Smileys don't animate [Solved again - Yes really!]
On 29/11/10 11:29:46, Camaleón wrote: On Mon, 29 Nov 2010 11:14:05 +, Barry Samuels wrote: On 29/11/10 10:21:56, Camaleón wrote: Well that 'cure' lasted less than 24 hours and the problem is back. What the hell is going on? We can't tell if you do not provide the requested data. Does it work using a proxy? Can you tell us the link? Going through hidemyass.com makes no difference - the smileys do not animate. Okay. I was thinking the problem could have come from your own ISP proxy or caching service and using an external proxy should have render the site from scratch. But if does not work, then we can forget the ISP variable. If you mean the link to the page with the smileys: http://www.beemthere-donethat.org.uk/bbHpp/viewtopic.php? f=10t=180sid=531ee08ae92329873213f0568dd2830c I mean the true URI so we can check :-) It appears that only part of the GIF image file is being downloaded by the browser. If I save one of the non-animated smileys and compare it with a version that does animate then the size of the non-animated GIF is much smaller. If we can't see it, we cannot tell. Are your experiencing the same problem from another computer? The problem was Privoxy. There is a 'deanimate-gifs' setting and this was the culprit. Adding my web site to the list of exceptions has cured the problem. Setting up a new browser profile cured the problem temporarily until I remembered that I hadn't set the proxy. Doing that, which then routes everything through Privoxy, brought the problem back but I hadn't realised that until I tried disabling Privoxy today. Ah well we live and learn. Well, I learn until I forget. (easy at my age) :-)) Thanks to Sven and Camaleon for trying. Special thanks to Camaleon for seeming very determined to solve my problem. :-)) -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1291050705.497...@dataman1
Smileys don't animate
I run my own (non-commercial) web site which includes a forum. There are smileys which can be used in the posts which are supposed to animate except that they don't animate on my desktop machine. My desktop runs Debian Testing/Squeeze, up to date, and uses a 2.6.34 kernel plus the nouveau graphics driver. I used to use the nv graphics driver which exhibited the same problem. I understand that these animated smileys are multi-layered GIFs and it seems that I only see one layer which in some cases is not enough to even identify the smiley image. If I boot the same machine from an oldish Knoppix DVD (kernel 2.6.19) the smileys animate as expected. That DVD appears to use the nv driver. I can view the same page on my Laptop and the smilies animate on that. The really strange part is that I also have a local copy of the web site running under Apache on my desktop and the smileys do animate on that. Any ideas? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1290942899.104...@dataman1
Re: Smileys don't animate
On 28/11/10 11:59:25, Camaleón wrote: On Sun, 28 Nov 2010 11:14:59 +, Barry Samuels wrote: I run my own (non-commercial) web site which includes a forum. There are smileys which can be used in the posts which are supposed to animate except that they don't animate on my desktop machine. (...) Try by empty your browser's cache (temporary files and cookies) or loading the animated gif with another browser as Sven suggested and see what happens. Greetings, -- Camaleón Thanks. See my reply to Sven. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1290946655.840...@dataman1
Re: Smileys don't animate
On 28/11/10 11:35:01, Sven Joachim wrote: On 2010-11-28 12:14 +0100, Barry Samuels wrote: I run my own (non-commercial) web site which includes a forum. There are smileys which can be used in the posts which are supposed to animate except that they don't animate on my desktop machine. Do other GIFs animate there? As I said originally the same GIFs animate on the same machine if they are on the local version of the web site but not on the remote site. My desktop runs Debian Testing/Squeeze, up to date, and uses a 2.6.34 kernel plus the nouveau graphics driver. I used to use the nv graphics driver which exhibited the same problem. I understand that these animated smileys are multi-layered GIFs and it seems that I only see one layer which in some cases is not enough to even identify the smiley image. If I boot the same machine from an oldish Knoppix DVD (kernel 2.6.19) the smileys animate as expected. That DVD appears to use the nv driver. I can view the same page on my Laptop and the smilies animate on that. The really strange part is that I also have a local copy of the web site running under Apache on my desktop and the smileys do animate on that. With the same web browser? Yes, with the same browser and with any other browsers that I've tried. The problem occurs when using Chromium and Opera Browsers in the same way i.e. the animation will work with the local site but not with the remote site. Any ideas? Not really, but in Mozilla based browsers you may want to check the value of image.animation_mode in about:config. Sven If that setting was the problem wouldn't it prevent smileys on the local machine from animating? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1290946584.840...@dataman1
Re: Smileys don't animate [Partly solved]
On 28/11/10 12:16:24, Barry Samuels wrote: On 28/11/10 11:35:01, Sven Joachim wrote: On 2010-11-28 12:14 +0100, Barry Samuels wrote: I run my own (non-commercial) web site which includes a forum. There are smileys which can be used in the posts which are supposed to animate except that they don't animate on my desktop machine. Do other GIFs animate there? As I said originally the same GIFs animate on the same machine if they are on the local version of the web site but not on the remote site. My desktop runs Debian Testing/Squeeze, up to date, and uses a 2.6.34 kernel plus the nouveau graphics driver. I used to use the nv graphics driver which exhibited the same problem. I understand that these animated smileys are multi-layered GIFs and it seems that I only see one layer which in some cases is not enough to even identify the smiley image. If I boot the same machine from an oldish Knoppix DVD (kernel 2.6.19) the smileys animate as expected. That DVD appears to use the nv driver. I can view the same page on my Laptop and the smilies animate on that. The really strange part is that I also have a local copy of the web site running under Apache on my desktop and the smileys do animate on that. With the same web browser? Yes, with the same browser and with any other browsers that I've tried. The problem occurs when using Chromium and Opera Browsers in the same way i.e. the animation will work with the local site but not with the remote site. Any ideas? Not really, but in Mozilla based browsers you may want to check the value of image.animation_mode in about:config. Sven If that setting was the problem wouldn't it prevent smileys on the local machine from animating? I have found that creating a new browser profile has cured the problem on Firefox. That, however, is a bit of a nuisance as it means transferring bookmarks, re-installing add-ons etc. It would be nice to know what part of the profile is causing the problem so that it would be possible to correct it. The problem still occurs in Opera and Chromium though. Why should a problem like that affect different browsers in the same way? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1290960934.1557...@dataman1
Re: Smileys don't animate [Partly solved]
On 28/11/10 16:19:45, Camaleón wrote: On Sun, 28 Nov 2010 16:15:34 +, Barry Samuels wrote: On 28/11/10 12:16:24, Barry Samuels wrote: On 28/11/10 11:35:01, Sven Joachim wrote: (...) If that setting was the problem wouldn't it prevent smileys on the local machine from animating? I have found that creating a new browser profile has cured the problem on Firefox. That, however, is a bit of a nuisance as it means transferring bookmarks, re-installing add-ons etc. It would be nice to know what part of the profile is causing the problem so that it would be possible to correct it. The problem still occurs in Opera and Chromium though. Why should a problem like that affect different browsers in the same way? It is called cache and it can be annoying :-) Try by empty all the stored cache files. Greetings, -- Camaleón The first thing I tried was to empty the cache but it made no difference. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1290964228.2292...@dataman1
Bluetooth and Blueman
I have had a Thinkpad R51 for some years now. This laptop has built-in Bluetooth which I have never had occasion to use until now. I have recently aquired an Android 'phone so I thought I'd try out this Bluetooth thing. The Thinkpad is running Debian Testing/Squeeze with a 2.6.34 kernel. The first thing I discovered was that the Bluetooth adapter wasn't being recognised at all. Compiling in a few extra modules in the kernel solved that one. I also had to install the rfkill package and a few other Bluetooth related packages. The Bluetooth indicator light now lights up when the laptop is booted and I can turn it on and off using Blueman. So far so good. I managed to pair the laptop with my 'phone and it shows up in the Blueman-Manager as a device. This is where things start to go pear shaped. At the righthand end of the bar which shows my 'phone in Blueman there are some coloured icons and if I hover my mouse cursor over that it displays a popup showing signal quality and strength. These icons appear and disappear regularly about every three seconds. When the icons are visible the signal strength is shown as about 60% and the link quality 100% but when the icons disappear the link quality is -1 and the signal strength is -1. Is that normal? If I try and send a file to the 'phone using Blueman it gets as far as displaying 'Contacting' but nothing more happens. If I try and 'Browse' files on my 'phone Nautilus opens and displays a message 'Could not display obex:// Protocol not supported'. Can anyone shed any light on this please? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1290251911.2176...@dataman1
Re: pl2303 Serial/USB problem - /dev/ttyUSB0 not created
On 09/08/10 17:41:28, Celejar wrote: On Fri, 06 Aug 2010 14:02:11 +0100 Barry Samuels ba...@beenthere.mail1.co.uk wrote: Desktop and Laptop both have Debian Testing installed and up to date; both with self-compiled kernel 2.6.32. I have a CurrentCost electricity usage monitor which is normally connected to my desktop via USB and is working properly. When the unit is plugged in I get a number of lines in syslog like so: kernel: usb 4-1: new full speed USB device using uhci_hcd and address 12 kernel: pl2303 4-1:1.0: pl2303 converter detected kernel: usb 4-1: pl2303 converter now attached to ttyUSB0 I am trying to get this same device working on my laptop but this time I see the following in syslog: kernel: pl2303: Prolific PL2303 USB to serial adaptor driver but nothing else i.e no 'attached to ttyUSB0'. Looking in /dev there is no ttyUSBn Whereas the desktop also loads the pl2303 and usbserial kernel modules automatically when the device is connected the laptop does not and when I load them manually I get only the above mentioned line in syslog. When the USB device is plugged in there is apparently no reaction from the operating system on the laptop when watching /var/syslog using 'tail'. That, I think, is the main problem. Other USB devices on the laptop do work. Needless to say the software which monitors the device won't connect. Any suggestions please? Are you using the *exact* same kernel on both systems? No of course not. One's a desktop the other's a laptop and they both have different requirements e.g. different graphics drivers. Do you have the same problem with a Debian stock kernel? The first step when debugging problems with self-compiled kernels is always to check if the problem exists with stock kernels, or only with one's own. I haven't tried a stock kernel but I have, since, tried a Knoppix Live DVD in the laptop and it doesn't work with that either. No reaction from the OS when the device is plugged in. I don't know if Knoppix uses a stock kernel. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1281374029.2416...@dataman1
pl2303 Serial/USB problem - /dev/ttyUSB0 not created
Desktop and Laptop both have Debian Testing installed and up to date; both with self-compiled kernel 2.6.32. I have a CurrentCost electricity usage monitor which is normally connected to my desktop via USB and is working properly. When the unit is plugged in I get a number of lines in syslog like so: kernel: usb 4-1: new full speed USB device using uhci_hcd and address 12 kernel: pl2303 4-1:1.0: pl2303 converter detected kernel: usb 4-1: pl2303 converter now attached to ttyUSB0 I am trying to get this same device working on my laptop but this time I see the following in syslog: kernel: pl2303: Prolific PL2303 USB to serial adaptor driver but nothing else i.e no 'attached to ttyUSB0'. Looking in /dev there is no ttyUSBn Whereas the desktop also loads the pl2303 and usbserial kernel modules automatically when the device is connected the laptop does not and when I load them manually I get only the above mentioned line in syslog. When the USB device is plugged in there is apparently no reaction from the operating system on the laptop when watching /var/syslog using 'tail'. That, I think, is the main problem. Other USB devices on the laptop do work. Needless to say the software which monitors the device won't connect. Any suggestions please? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1281099731.2810...@dataman1
Iceweasel/Firefox profiles
Using up to date Iceweasel on Debian Testing. I have noticed that in Iceweasel/Firefox after setting up a new profile I start to lose functionality after some months of use. For example I find now that some graphics are no longer displaying whereas they used to display. If I go to http://www.openstreetmap.org I see the map window together with a zoom control but there is no map. If I view the same page using a new clean profile I do see the map. This happens with some graphics but not all. I have disabled all the installed add-ons to no effect. The strange thing is that my wife's computer uses the same browser on the same operating system and she doesn't have any such problem. I'm getting a little fed up at having to start a new profile when this happens. Any suggestions would be gratefully received. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1279034723.2163...@dataman1
Strange printing effect
I use Debian Testing/Squeeze with the 2.6.32 kernel, hplip and hplip-cups. My printer is a networked HP LaserJet 4500 colour laser. I get a strange print output sometimes where parts of the background are black where it should be white. This only occurs on areas which are empty i.e. there is nothing there to print. The areas which have text do have a white background. The easiest way to understand is to look at this image of a printed page: http://www.beenthere-donethat.org.uk/system/print-sample.jpg All those black bands and lines shouldn't be there i.e. they should all be white. If I print a CUPS test page it prints perfectly. If I print a text document from the OpenOffice word processor this effect does not show but if I print a spreadsheet from OpenOffice it does show. A print from the Iceweasel browser shows some thin lines on the outer edges only and printing from a PDF document using the Adobe Reader produces the black baground effect. It's all rather baffling and any suggestions would be greatly appreciated. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1274866014.2783...@dataman1
Re: Strange printing effect
On 26/05/10 11:52:22, Brad Rogers wrote: On Wed, 26 May 2010 10:26:54 +0100 Barry Samuels ba...@beenthere.mail1.co.uk wrote: It's all rather baffling and any suggestions would be greatly appreciated. I don't have an answer, but I can tell you it's not 'just you'. Using an HP 1200 Business Inkjet, hplip Cups I get similar things. The only difference being that the unwanted background here is printed in yellow. That's not fair! It's prettier than mine. :-)) It's nice to know I'm not alone and I did wonder if it might be the driver although I can't imagine it being released, even for Squeeze, with such glaring faults. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1274872533.909...@dataman1
Re: Strange printing effect
On 26/05/10 12:08:23, Camaleón wrote: On Wed, 26 May 2010 10:26:54 +0100, Barry Samuels wrote: I use Debian Testing/Squeeze with the 2.6.32 kernel, hplip and hplip-cups. My printer is a networked HP LaserJet 4500 colour laser. I get a strange print output sometimes where parts of the background are black where it should be white. This only occurs on areas which are empty i.e. there is nothing there to print. The areas which have text do have a white background. (...) Make a quick test: create a new printer using CUPS interface (select a PS driver) and try to print the same page with the newly created printer to see if it happens the same. -- Camaleón I created a new CUPS printer using the Generic Postscript driver and it does not appear to produce the problem. Printing a test page from the CUPS maintenance screen it prints perfectly but in monochrome only. Printing a spreadsheet using this printer doesn't produce the problem either but I did select 'Postscript 2' and 'Colour' rather than 'from driver' and it did print colour. It does look like the HPLIP driver is causing the problem. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1274883389.3135...@dataman1
Re: Strange printing effect *WORKAROUND*
On 26/05/10 17:30:55, Brad Rogers wrote: On Wed, 26 May 2010 15:16:29 +0100 Barry Samuels ba...@beenthere.mail1.co.uk wrote: Hello Barry, It does look like the HPLIP driver is causing the problem. It certainly seems to be. Although the thread meantioned below also throws suspicion on ghostscript. After some poking around (Google, HPLIP support site [which is a real PITA to navigate]) I managed to find this thread; https://bugs.launchpad.net/hplip/+bug/578920 Which offers a workaround. It worked for me, but I'm not sure whether it will for you as the symptoms aren't the same (black o/p instead of yellow/cream). Here's what to do: Edit; /usr/lib/cups/filter/pstopdf Change; PS2PDF_OPTIONS=$PS2PS_OPTIONS -dColorImageFilter=/FlateEncode \ -dPDFSETTINGS=/printer -dUseCIEColor to; PS2PDF_OPTIONS=$PS2PS_OPTIONS -dColorImageFilter=/FlateEncode \ -dPDFSETTINGS=/printer It worked for me. No doubt, at the next upgrade, things will get changed back but hopefully, the bug will be fixed before that. Brad Thanks for posting that but it didn't work for me but I do have the plain vanilla postscript driver which does work. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1274894773.2243...@dataman1
Re: Thinkpad Touchpad no longer works
On 16/10/09 22:30:54, Florian Kulzer wrote: On Fri, Oct 16, 2009 at 21:49:34 +0100, Barry Samuels wrote: SynPS/2 Synaptics Touchpad The /dev/input/event* device nodes seem to be missing Just noticed something. On my desktop event0, event1, mice, mouse0 etc are in /dev/input but on the laptop they are in /dev and /dev/input has only by-id and by-path Is that significant? Yes, it is; it probably means that something goes wrong when udev creates the device node for the touchpad. My first guess is that you upgraded to a newer version of udev, and that it now expects some novel piece of information that your custom kernel does not provide. (IOW, I side with Celejar and Andrew in suspecting your kernel configuration is the cause of your problems.) Please install the newest stock kernel and boot into it; this will immediately tell us if we are on the right track. Once we have established that, we can delve into the details to find the relevant setting. Installed linux-image-2.6.30-2-486 but sorry to report that there is no difference - the touchpad still doesn't work and the event nodes are still in /dev. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thinkpad Touchpad no longer works
On 17/10/09 12:26:11, Florian Kulzer wrote: On Sat, Oct 17, 2009 at 10:21:52 +0100, Barry Samuels wrote: Installed linux-image-2.6.30-2-486 but sorry to report that there is no difference - the touchpad still doesn't work and the event nodes are still in /dev. OK, we can stop worrying about the kernel configuration for the moment. Now I would be interested in some details about your misplaced event devices; please show me the output of: stat /dev/event7 File: `/dev/event7' Size: 0 Blocks: 0 IO Block: 4096 character special file Device: bh/11d Inode: 33604 Links: 1 Device type: d,47 Access: (0660/crw-rw) Uid: (0/root) Gid: (0/root) Access: 2009-10-17 12:38:41.209641864 +0100 Modify: 2009-10-17 12:38:41.209641864 +0100 Change: 2009-10-17 12:38:41.209641864 +0100 Also, let's check what udev is doing, with this command: udevadm test /class/input/input7/event7 There wasn't much output so I've included it here: run_command: calling: test udevadm_test: version 141 udev_rules_new: rule file basename '/etc/udev/rules.d/50-udev.rules' already added, ignoring '/lib/udev/rules.d/50-udev.rules' parse_file: reading '/etc/udev/rules.d/025_libgphoto2.rules' as rules file parse_file: reading '/etc/udev/rules.d/50-udev.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-gnupg.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-libsane-extras.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-libsane.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-input.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-serial.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-storage-tape.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-storage.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-v4l.rules' as rules file parse_file: reading '/dev/.udev/rules.d/61-dev-root-link.rules' as rules file parse_file: reading '/lib/udev/rules.d/62-bluez-hid2hci.rules' as rules file parse_file: reading '/etc/udev/rules.d/70-persistent-cd.rules' as rules file parse_file: reading '/etc/udev/rules.d/70-persistent-net.rules' as rules file parse_file: reading '/lib/udev/rules.d/75-cd-aliases-generator.rules' as rules file parse_file: reading '/lib/udev/rules.d/75-persistent-net-generator.rules' as rules file parse_file: reading '/lib/udev/rules.d/80-alsa.rules' as rules file parse_file: reading '/lib/udev/rules.d/80-drivers.rules' as rules file parse_file: reading '/lib/udev/rules.d/85-hwclock.rules' as rules file parse_file: reading '/etc/udev/rules.d/85-pcmcia.rules' as rules file parse_file: reading '/lib/udev/rules.d/90-hal.rules' as rules file parse_file: reading '/lib/udev/rules.d/91-permissions.rules' as rules file util_lookup_group: specified group 'nvram' unknown util_lookup_user: specified user 'tss' unknown util_lookup_group: specified group 'tss' unknown util_lookup_group: specified group 'kvm' unknown util_lookup_group: specified group 'rdma' unknown parse_file: reading '/lib/udev/rules.d/95-late.rules' as rules file parse_file: reading '/etc/udev/rules.d/z60_gpsd.rules' as rules file parse_file: reading '/etc/udev/rules.d/z60_hdparm.rules' as rules file parse_file: reading '/etc/udev/rules.d/z60_libccid.rules' as rules file udev_rules_new: rules use 100692 bytes tokens (8391 * 12 bytes), 13475 bytes buffer udev_rules_new: temporary index used 30820 bytes (1541 * 20 bytes) unable to open device '/sys/class/input/input7/event7' -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thinkpad Touchpad no longer works
On 17/10/09 14:07:52, Barry Samuels wrote: On 17/10/09 12:26:11, Florian Kulzer wrote: On Sat, Oct 17, 2009 at 10:21:52 +0100, Barry Samuels wrote: Installed linux-image-2.6.30-2-486 but sorry to report that there is no difference - the touchpad still doesn't work and the event nodes are still in /dev. OK, we can stop worrying about the kernel configuration for the moment. Now I would be interested in some details about your misplaced event devices; please show me the output of: stat /dev/event7 File: `/dev/event7' Size: 0 Blocks: 0 IO Block: 4096 character special file Device: bh/11dInode: 33604 Links: 1 Device type: d,47 Access: (0660/crw-rw) Uid: (0/root) Gid: (0/root) Access: 2009-10-17 12:38:41.209641864 +0100 Modify: 2009-10-17 12:38:41.209641864 +0100 Change: 2009-10-17 12:38:41.209641864 +0100 Also, let's check what udev is doing, with this command: udevadm test /class/input/input7/event7 /class/input/input7/event7 does not exist but /class/input/event7 does so I've done the same with that. Output below: run_command: calling: test udevadm_test: version 141 udev_rules_new: rule file basename '/etc/udev/rules.d/50-udev.rules' already added, ignoring '/lib/udev/rules.d/50-udev.rules' parse_file: reading '/etc/udev/rules.d/025_libgphoto2.rules' as rules file parse_file: reading '/etc/udev/rules.d/50-udev.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-gnupg.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-libsane-extras.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-libsane.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-input.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-serial.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-storage-tape.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-storage.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-v4l.rules' as rules file parse_file: reading '/dev/.udev/rules.d/61-dev-root-link.rules' as rules file parse_file: reading '/lib/udev/rules.d/62-bluez-hid2hci.rules' as rules file parse_file: reading '/etc/udev/rules.d/70-persistent-cd.rules' as rules file parse_file: reading '/etc/udev/rules.d/70-persistent-net.rules' as rules file parse_file: reading '/lib/udev/rules.d/75-cd-aliases-generator.rules' as rules file parse_file: reading '/lib/udev/rules.d/75-persistent-net-generator.rules' as rules file parse_file: reading '/lib/udev/rules.d/80-alsa.rules' as rules file parse_file: reading '/lib/udev/rules.d/80-drivers.rules' as rules file parse_file: reading '/lib/udev/rules.d/85-hwclock.rules' as rules file parse_file: reading '/etc/udev/rules.d/85-pcmcia.rules' as rules file parse_file: reading '/lib/udev/rules.d/90-hal.rules' as rules file parse_file: reading '/lib/udev/rules.d/91-permissions.rules' as rules file util_lookup_group: specified group 'nvram' unknown util_lookup_user: specified user 'tss' unknown util_lookup_group: specified group 'tss' unknown util_lookup_group: specified group 'kvm' unknown util_lookup_group: specified group 'rdma' unknown parse_file: reading '/lib/udev/rules.d/95-late.rules' as rules file parse_file: reading '/etc/udev/rules.d/z60_gpsd.rules' as rules file parse_file: reading '/etc/udev/rules.d/z60_hdparm.rules' as rules file parse_file: reading '/etc/udev/rules.d/z60_libccid.rules' as rules file udev_rules_new: rules use 100692 bytes tokens (8391 * 12 bytes), 13475 bytes buffer udev_rules_new: temporary index used 30820 bytes (1541 * 20 bytes) udev_device_new_from_syspath: device 0x8074d10 has devpath '/devices/ platform/i8042/serio1/input/input10/event7' udev_device_new_from_syspath: device 0x80747e8 has devpath '/devices/ platform/i8042/serio1/input/input10/event7' udev_device_read_db: device 0x80747e8 filled with db file data udev_device_new_from_syspath: device 0x8074a80 has devpath '/devices/ platform/i8042/serio1/input/input10' udev_device_new_from_syspath: device 0x8064318 has devpath '/devices/ platform/i8042/serio1' udev_device_new_from_syspath: device 0x80644c0 has devpath '/devices/ platform/i8042' udev_device_new_from_syspath: device 0x8064658 has devpath '/devices/ platform' udev_rules_apply_to_event: IMPORT 'path_id /devices/platform/i8042/serio1/ input/input10/event7' /lib/udev/rules.d/60-persistent-input.rules:45 util_run_program: 'path_id /devices/platform/i8042/serio1/input/input10/ event7' util_run_program: '/lib/udev/path_id' (stdout) 'ID_PATH=platform-i8042- serio-1' util_run_program: '/lib/udev/path_id' returned with status 0 udev_rules_apply_to_event: LINK 'input/by-path/platform-i8042-serio-1- event-mouse' /lib/udev/rules.d/60-persistent-input.rules:49 udev_rules_apply_to_event: RUN 'socket:@/org/freedesktop/hal/udev_event' / lib/udev/rules.d/90-hal.rules:2 udev_event_execute_rules: no node
Re: Thinkpad Touchpad no longer works [Solved]
On 17/10/09 15:12:35, Florian Kulzer wrote: It seems that you have an outdated 50-udev.rules file in /etc/udev/rules.d/, which means that the up-to-date file in /lib/udev/rules.d/ is ignored. Quoting from udev's NEWS.Debian.gz: The default rules files have been moved to /lib/udev/rules.d/ and /etc/udev/rules.d/ is supposed to contain only generated files or custom directives. (starting udev version 0.140-1) Florian You are so right! Removing that file has cured the problem. All that file had in it was: KERNEL=='rtc0', SYMLINK+=rtc I can't honestly say now whether I put that there or not. Thank you so much for your help. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Thinkpad Touchpad no longer works
I have an IBM Thinkpad R61 running Debian Testing with kernel 2.6.30. After a recent system update the touchpad no longer works. The red button thing, whatever they call it, embedded in the keyboard and its associated buttons all work but the touchpad and its associated buttons don't. I have tried various xorg.conf configurations and no xorg.conf at all but it makes no difference. I've tried booting from a Knoppix DVD v5.1 with a 2.6.19 kernel and it works with that. Can anyone suggest a reason for this? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thinkpad Touchpad no longer works
On 16/10/09 14:31:33, Osamu Aoki wrote: Hi, On Fri, Oct 16, 2009 at 02:08:45PM +0100, Barry Samuels wrote: I have an IBM Thinkpad R61 running Debian Testing with kernel 2.6.30. After a recent system update the touchpad no longer works. The red button thing, whatever they call it, embedded in the keyboard and its associated buttons all work but the touchpad and its associated buttons don't. I have tried various xorg.conf configurations and no xorg.conf at all but it makes no difference. But I can not tell what you tried. I've tried booting from a Knoppix DVD v5.1 with a 2.6.19 kernel and it works with that. Did you copy xorg.conf from Knoppix? Yes - no difference. Can anyone suggest a reason for this? Did you install xfree86-driver-synaptics ? No but I do have xserver-xorg-input-synaptics. Let me stress that it was working perfectly before the update. I haven't changed anything directly myself. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thinkpad Touchpad no longer works
On 16/10/09 16:59:55, Andrew Sackville-West wrote: On Fri, Oct 16, 2009 at 04:25:52PM +0100, Barry Samuels wrote: On 16/10/09 14:31:33, Osamu Aoki wrote: [...] Did you install xfree86-driver-synaptics ? No but I do have xserver-xorg-input-synaptics. Let me stress that it was working perfectly before the update. I haven't changed anything directly myself. can you get synclient to connect to the synaptics driver? Does Xorg.0.log show any reference to synaptics? I hadn't thought of looking in there but, yes, there is a line which says: SynPS/2 Synaptics Touchpad The /dev/input/event* device nodes seem to be missing What would that mean? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thinkpad Touchpad no longer works
On 16/10/09 20:13:45, Andrew Sackville-West wrote:
On Fri, Oct 16, 2009 at 02:12:59PM -0400, Celejar wrote:
On Fri, 16 Oct 2009 18:42:05 +0100
Barry Samuels ba...@beenthere.mail1.co.uk wrote:
...
SynPS/2 Synaptics Touchpad The /dev/input/event* device nodes seem
to be missing
What would that mean?
Not sure, but in the kernel config, there's something called
CONFIG_INPUT_DEV (Device Drivers / Input device support / Event
interface). From its help:
Say Y here if you want your input device events be accessible
under char device 13:64+ - /dev/input/eventX in a generic way.
To compile this driver as a module, choose M here: the
module will be called evdev.
Perhaps your kernel doesn't have this enabled?
It is enabled.
from the tone of the prior thread, I assume it's a stock kernel, so,
OP, let us know if it's not.
No it's not. I compile my own kernels.
Apropos the xorg log, if the synaptics module can't find the device
then it won't work, I would assume :)
Seems fair.
Can you provide the logs of what packages you upgraded that brought
about this failure? I'm thinking maybe this points to a hal problem,
perhaps (but know nothing about hal...).
Is there a log for that? The last upgrade was a little overdue and I think
about 150 packages were upgraded.
The output of lshal -u $(hal-find-by-capability --capability
input.touchpad) is:
udi = '/org/freedesktop/Hal/devices/
platform_i8042_i8042_AUX_port_logicaldev_input'
info.capabilities = {'input', 'input.touchpad'} (string list)
info.category = 'input' (string)
info.parent = '/org/freedesktop/Hal/devices/
platform_i8042_i8042_AUX_port' (string)
info.product = 'SynPS/2 Synaptics TouchPad' (string)
info.subsystem = 'input' (string)
info.udi = '/org/freedesktop/Hal/devices/
platform_i8042_i8042_AUX_port_logicaldev_input' (string)
input.device = '/dev/event7' (string)
input.originating_device = '/org/freedesktop/Hal/devices/
platform_i8042_i8042_AUX_port' (string)
input.product = 'SynPS/2 Synaptics TouchPad' (string)
input.x11_driver = 'synaptics' (string)
input.x11_options.SHMConfig = 'On' (string)
linux.device_file = '/dev/event7' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'input' (string)
linux.sysfs_path = '/sys/class/input/input7/event7' (string)
I hope it means more to you than it does to me. :)
--
Barry Samuels
http://www.beenthere-donethat.org.uk
The Unofficial Guide to Great Britain
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thinkpad Touchpad no longer works
On 16/10/09 21:22:22, Barry Samuels wrote:
On 16/10/09 20:13:45, Andrew Sackville-West wrote:
On Fri, Oct 16, 2009 at 02:12:59PM -0400, Celejar wrote:
On Fri, 16 Oct 2009 18:42:05 +0100
Barry Samuels ba...@beenthere.mail1.co.uk wrote:
...
SynPS/2 Synaptics Touchpad The /dev/input/event* device nodes seem
to be missing
What would that mean?
Not sure, but in the kernel config, there's something called
CONFIG_INPUT_DEV (Device Drivers / Input device support / Event
interface). From its help:
Say Y here if you want your input device events be accessible
under char device 13:64+ - /dev/input/eventX in a generic way.
To compile this driver as a module, choose M here: the
module will be called evdev.
Perhaps your kernel doesn't have this enabled?
It is enabled.
from the tone of the prior thread, I assume it's a stock kernel, so,
OP, let us know if it's not.
No it's not. I compile my own kernels.
Apropos the xorg log, if the synaptics module can't find the device
then it won't work, I would assume :)
Seems fair.
Can you provide the logs of what packages you upgraded that brought
about this failure? I'm thinking maybe this points to a hal problem,
perhaps (but know nothing about hal...).
Is there a log for that? The last upgrade was a little overdue and I
think
about 150 packages were upgraded.
The output of lshal -u $(hal-find-by-capability --capability
input.touchpad) is:
udi = '/org/freedesktop/Hal/devices/
platform_i8042_i8042_AUX_port_logicaldev_input'
info.capabilities = {'input', 'input.touchpad'} (string list)
info.category = 'input' (string)
info.parent = '/org/freedesktop/Hal/devices/
platform_i8042_i8042_AUX_port' (string)
info.product = 'SynPS/2 Synaptics TouchPad' (string)
info.subsystem = 'input' (string)
info.udi = '/org/freedesktop/Hal/devices/
platform_i8042_i8042_AUX_port_logicaldev_input' (string)
input.device = '/dev/event7' (string)
input.originating_device = '/org/freedesktop/Hal/devices/
platform_i8042_i8042_AUX_port' (string)
input.product = 'SynPS/2 Synaptics TouchPad' (string)
input.x11_driver = 'synaptics' (string)
input.x11_options.SHMConfig = 'On' (string)
linux.device_file = '/dev/event7' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'input' (string)
linux.sysfs_path = '/sys/class/input/input7/event7' (string)
I hope it means more to you than it does to me. :)
Just noticed something. On my desktop event0, event1, mice, mouse0 etc are
in /dev/input but on the laptop they are in /dev and /dev/input has only
by-id and by-path
Is that significant?
--
Barry Samuels
http://www.beenthere-donethat.org.uk
The Unofficial Guide to Great Britain
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Frequent crashes whilst using X (try 2)
On 25/07/09 22:27:30, lee wrote: On Sat, Jul 25, 2009 at 04:46:31PM +0100, Barry Samuels wrote: I would be nice to know if other people *aren't* getting this as it would then mean the problem must be on my system. That would at least be a clue although I cannot imagine why it started suddenly. Well, I'm not getting such messages. Is it possible that have run out of memory? In that case, the X server can get killed. I don't think so. I have 2GB of RAM and there wasn't a lot running. It's useful to know that you aren't affected in the same way although I could have something installed that you don't. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Frequent crashes whilst using X (try 2)
On 26/07/09 13:18:58, Chris Davies wrote: Barry Samuels ba...@beenthere.mail1.co.uk wrote: A few weeks ago after some packages were updated X applications started crashing and sometimes brought X down as well. Ah. Someone else, too! I'm getting segementation violations (signal 11) but since I use the proprietary NVidia driver I've not seen any way of reporting this as a fault. For me, it seems to happen no more than once a day or so, when I'm using compiz on a dual screen configuration, and the segv happens around the time I open a new window - typically using icedove when about to reply to someone's email. May be totally unrelated, of course, other than it also started just a few weeks ago. Chris A few weeks ago would be about right. I've also had it happen when I'm using Iceweasel. Once a day could be about right except in my case Balsa seems particularly vulnerable and could easily crash three times in a row. I'm using the xorg nv driver but I have swapped to the vesa driver as a test with no change - still crashes. That would seem to rule out a graphics driver problem. Welcome to the club. :-)) -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Frequent crashes whilst using X (try 2)
Debian Squeeze/Testing with kernel 2.6.26 and the nv driver. A few weeks ago after some packages were updated X applications started crashing and sometimes brought X down as well. I use Balsa as my mailer and often when I click on a mail folder to open it Balsa just crashes (disappears). Today I started Qemu and when I clicked inside the window to capture the mouse pointer X crashed and I was back at the KDM login. The only error I can find for the Qemu crash is in Xorg.0.log.old: (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded Fatal server error: bogus pointer event from ddx I've assumed that there may be a bug in one of the upgraded packages but I've no idea which one. Is anyone else experiencing this? UPDATE: It does seem to be mouse related. I have also seen this in .xsession-errors: balsa: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. I would be nice to know if other people *aren't* getting this as it would then mean the problem must be on my system. That would at least be a clue although I cannot imagine why it started suddenly. Anyone? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Frequent crashes whilst using X
Debian Squeeze/Testing with kernel 2.6.26 and the nv driver. A few weeks ago after some packages were updated X applications started crashing and sometimes brought X down as well. I use Balsa as my mailer and often when I click on a mail folder to open it Balsa just crashes (disappears). Today I started Qemu and when I clicked inside the window to capture the mouse pointer X crashed and I was back at the KDM login. The only error I can find for the Qemu crash is in Xorg.0.log.old: (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded Fatal server error: bogus pointer event from ddx I've assumed that there may be a bug in one of the upgraded packages but I've no idea which one. Is anyone else experiencing this? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Sensors and pwmconfig
Debian Squeeze/Testing Kernel 2.6.26 I've installed the lm-sensors package and Gkrellm will display both temperature and fan speed. If I run 'sensors', however, I get: Can't access procfs/sysfs file Unable to find i2c bus information; For 2.6 kernels, make sure you have mounted sysfs and libsensors was compiled with sysfs support! For older kernels, make sure you have done 'modprobe i2c-proc'! I've checked that sysfs is mounted. pwmconfig when run produces: /usr/local/sbin/pwmconfig: No sensors found! (modprobe sensor modules?) Are these problems related and can anyone advise me what to do to get them to work? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Is there a way to stop a SATA disc?
I have, in the last few days, changed my 2 x 250 GB IDE drives for 2 x 1 TB SATA drives. One drive is used once a day to mirror the other. Previously I used hdparm to spin down the mirror drive after a short period of inactivity and I've tried to do the same with one of the new drives but I suspect it isn't working. If I issue the command 'sg_start --stop /dev/sdb' I hear a click from the computer as if the drive is being switched off but can't detect any difference in noise. That could be because the drive is ultra quiet but if I then try to mount a partition on the drive it mounts instantly. With the previous drives if I did that there would be a significant pause whilst the drive was spinning up to running speed. Does the fact that there is no pause of any sort when mounting the drive mean that it hasn't stopped? I've also tried 'sdparm --command=stop /dev/sdb' with the same results. If I issue the command sdparm --command=ready /dev/sdb then it comes back with 'ready'. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: hard crash on leap second
On 01/01/09 00:25:25, Travis Crump wrote: I had a hard crash of my lenny system precisely when the leap second was added. While X has flaked in the past, I've never had a hard crash before. I have no other evidence they were related, but I wasn't doing anything unusual at the time. Any ideas? Travis My system, which runs 24 hours a day, also crashed at around, I suspect, midnight. I run Testing/Lenny and this machine has been stable for a number of years. The latest entry in any of the logs is in syslog: Dec 31 23:57:58 dataman1 -- MARK -- There is nothing after that and there is, apparently, nothing untoward in the logs. This morning the machine was totally unresponsive to mouse and keyboard. Trying to connect via ssh failed - no route to host and the magic sysrq keys had no effect. The timing does seem to be significant. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I've lost my keyboard repeat.
Since upgrading my Debian Testing system yesterday the keys on my keyboard no longer repeat when held down. I suspect the xserver-xorg packages as this problem occurs in any X application but the keys still repeat normally when in an ordinary text console. I have just noticed another strange keyboard problem. The 'm' key produces a character only on every other keypress i.e. I have to press the 'm' key twice to get one character. All other letter keys are working normally. Anyone else experience this? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Accessing a TV adapter via my network
On 05/02/08 10:13:37, Nate Duehr wrote: On Feb 5, 2008, at 2:26 AM, Barry Samuels wrote: I don't intend a cardboard box to be a permanent solution but I've no intention of buying a case until I know that the whole setup works. Looks like it's time to get a case. The Hauppauge WinTV Nova-T 500 adapter is now installed in my cardboard computer and I have the MythTV Backend installed on the same machine and the MythTV Frontend on my normal desktop. I can now watch and record television - whoopee! I did have to get an digital signal amplifier for the aerial connection to the card as I was getting only about a 27% signal strength for BBC1 - one of our strongest channels. For the same channel on our television, connected to the same aerial socket, we get a signal strength of around 90%. Perhaps the tuner in the television is more sensitive than the tuners in the TV adapter. With the amplifier in place it's now up to 51%. Having made 3 test recordings I can say that recording works and so does the scheduling. Just a bit of tidying up then. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Re: computer case; was Re: Accessing a TV adapter via my network
On 05/02/08 17:44:26, PETER EASTHOPE wrote: Barry, At Feb 5, 2008, at 2:26 AM you wrote, ... buying a case until I know that the whole setup works. So many computers are discarded these days; few people really need to buy a computer let alone a case. The problem is finding people who have parts that they no longer want. If friends haven't offered you several, Friends ? :-)) there should be a steady supply on various loading docks and back corridors, waiting for disposal. If postage weren't so costly, I'd mail you one. Regards, ... Peter E. That's a nice thought Peter - thank you. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Re: Accessing a TV adapter via my network
On 05/02/08 05:26:58, Nate Duehr wrote: On Jan 31, 2008, at 3:36 AM, Mihira Fernando wrote: Barry Samuels wrote: [snip] I have setup my cardboard computer (it's in a cardboard box) using [snip] it would a lot safer to get a proper casing for that. You're looking at a fire hazard with a cardboard box and those components. Not to mention throwing small but annoying amounts of RF interference everywhere RF shielding has gotten pretty poor on modern cases, but a cardboard box takes the cake. I don't intend a cardboard box to be a permanent solution but I've no intention of buying a case until I know that the whole setup works. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Re: Accessing a TV adapter via my network
On 26/01/08 23:22:47, Andrew Sackville-West wrote: On Sat, Jan 26, 2008 at 05:19:10PM +, Barry Samuels wrote: I would like to get a Hauppauge WinTV Nova T 500 adapter which I understand works with Linux. Unless they've changed recently, this card should work. It has onboard mpeg2 compression which means that you can capture on it with a pretty low power system (important for your idea below). ... My idea would be to assemble another computer using some spare parts I would be looking at a minimal install of Linux on the new box with all the processing done on my desktop. frankly there's not much processing to do with that card.. it already compresses for you. But if you want to commercial flag, or transcode recordings, then that does take a little horsepower. Myth allows you to use other machines for these jobs if they also have the backend installed. YOu can configure the backends to be master and slaves. The master will control all the scheduling. The slaves just do what the master says: record shows, flag commercials, etc.. What's the minimum RAM I would need? not much frankly. If all you're doing is recording shows, it's just an mpeg2 stream taken straight to disk. My rig with two cards has 512MB memory but hardly uses any of it. I think it would be fine with 256MB. I would also need to aquire an IDE hard drive. What's the minimum size I could get away with for an appropriate Debian system? I run debian on a couple machines with old 4.3GB drives, but it's a little tight. TV recording will be done on my main desktop via the network. Well, not sure how well that works with myth. YOu could mount the desktop drive as an NFS share, but it could be a real bottleneck. Storage is cheap, stick a drive in the other machine and mount it as a NFS share to your desktop. That will keep you from getting IO bound on the recording machine. IIRC, the pvr500 has to inputs, which means in theory, you'd be trying to cram two shows down that pipe at once, probably not a good idea even with gigabit ethernet. I wouldn't normally want to use a screen or keyboard after the machine has been setup - would that cause problems when booting? depends on the bios, but probably not. Andrew, many thanks for the advice. There has now been a slight change of plan. I have setup my cardboard computer (it's in a cardboard box) using an old main board with a 750 MHz Athlon K7 and 768 MB of RAM. I fitted a PCI ethernet card and a PCI wireless card. There is a 6.5 GB hard drive which is certainly big enough for the operating system only (Debian) which I have now installed and it's all up and running. I have also aquired (free) a 20GB hard drive for storing the test recodings and it is now fitted and running. I have decided to put it near the television aerial wall point and it can connect to my wireless access point from there solving my wireless problem. There was nothing in the BIOS about stopping on errors so I tried it without keyboard or screen and it boots without problems. I can control it via SSH from my desktop so my next step will be to buy a Hauppauge WinTV Nova T 500 adapter. I'm going to run the MythTV backend on the cardboard machine and the front (controlling) end on my desktop which MythTV is apparently setup to do. If it all works as hoped I'll even buy it a proper case and a larger hard drive. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Accessing a TV adapter via my network
I would like to get a Hauppauge WinTV Nova T 500 adapter which I understand works with Linux. That's the easy part. It would be very inconvenient to install it in my desktop because it would require a connection to a TV aerial socket and I don't have one near my desktop. My idea would be to assemble another computer using some spare parts that I have together with some parts that I would have to re-aquire. I say 're-aquire' because I would have had all the necessary parts if I hadn't given away a lot of them (CPUs, hard drives, RAM) to a local computer recycling charity a few months ago. Why is it that one does not have a use for these parts until they've gone? I'm assuming that if I assemble the said computer with the TV adapter in it (putting it near a TV aerial socket) and can connect wirelessly to my desktop then I could access the TV adapter from my desktop using something like MythTV. Would such a thing be possible? I would be looking at a minimal install of Linux on the new box with all the processing done on my desktop. This would assume that I could connect the two boxes using nothing more than a wireless adapter in each i.e. no router. My desktop has an on- board wireless adapter and I have two spare PCI adapters one of which I could use in the new box. Is it possible to get two wireless adapters to communicate in this way? Would that be fast enough to cope with the data from the TV adapter? What sort of specification for the new machine would be required? I have a Gigabyte GA-7ZXE mainboard which takes a Socket A Athlon (which I would have to aquire) and it takes PC-133 SDRam (which I would also have to aquire). What's the minimum RAM I would need? I would also need to aquire an IDE hard drive. What's the minimum size I could get away with for an appropriate Debian system? TV recording will be done on my main desktop via the network. I wouldn't normally want to use a screen or keyboard after the machine has been setup - would that cause problems when booting? What else haven't I thought of? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Re: powerline ethernet
On 17/01/08 18:14:05, Scott Lair wrote: Barry Samuels wrote: I have recently purchased two Solwise 200Mbps NET-PL-200AV-PUSH. They installed (nothing other than plugging them in really) and worked. I've had no trouble with them and transfer speed is good. One of the reasons I chose them is that they offered to take them back and give a full refund if the units didn't work properly in my situation. I use Debian Testing. Very good, just what I wanted to hear. Have you tested the throughput on them? Just curious if you are getting around 20MBs or more like 10MBs. scott I had tested them originally and remember that the speed was satisfactory but couldn't remember what the speeds actually were so I've just done it again. I connected my laptop directly to the router with an ethernet cable so that wireless speeds don't enter the equation. I uploaded a large .iso file from my desktop, on one end of the HomePlug system, to the laptop and got 50-60 Mbs (note 'bits' not 'bytes') and then downloaded from the laptop to my desktop and got 40-50 Mbs. These Solwise HomePlug units are rated at 200 Mbs but there is obviously some loss over the mains. We also have electric heating in the house which is controlled from a central controller also by sending signals along the mains cables. I don't know whether there is any loss on the HomePlug system because of that but both the ethernet transmissions and the heating signals appear to be quite reliable. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Re: powerline ethernet
On 15/01/08 16:35:41, Scott Lair wrote: Anyone using a powerline ethernet with debian? I've got some difficult to wire locations so I thought I'd investigate my options. I've tried wireless and it's a bit spotty so I'm hoping that some debian folks have some good experiences with powerline. I've seen them from Dlink, Linksys etc. and from about 14Mbs to 200Mbs. If I can get about 50Mbs reliably I'd be happy. Any thoughts on security for these things? I have recently purchased two Solwise 200Mbps NET-PL-200AV-PUSH. They installed (nothing other than plugging them in really) and worked. I've had no trouble with them and transfer speed is good. One of the reasons I chose them is that they offered to take them back and give a full refund if the units didn't work properly in my situation. I use Debian Testing. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Re: Postfix and SASL authentication (Solved)
On 26/11/07 10:44:50, Mihira Fernando wrote: Barry Samuels wrote: I have tried twice before to set up SASL authentication for Postfix and failed to get it working both times. I am now trying a third time. I have three remote mail servers to which I can send outgoing mail. I use Balsa as a mail client and, as a test, I set the value of the Remote Server, in the Balsa settings, to each of the three mail servers in turn together with the appropriate values for username and password. I sent an email using each setting and they all arrived. This shows that my username/password combinations are correct for each of the remote servers. Many thanks to those who replied. I don't know what I did wrong this time BUT it all works. :-)) Whoo Hoo! One thing I've discovered is that usernames that work in Balsa don't necessarily work with SASL. I had to change some slightly to get it to work. Another thing is that one of my remote mail servers is GMail and I've seen a number of Howtos for GMail all of which involve what seems to be a complex procedure for creating a certificate but I saw one which said just to put the following in postfix/main.cf: # For servers (e.g. GMail) that need SSL support smtp_tls_policy_maps = hash:/etc/postfix/tls_policy smtp_tls_security_level = may That's all I've done (I did create the tls_policy file) and it works apparently without this certificate thingy. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Postfix and SASL authentication
I have tried twice before to set up SASL authentication for Postfix and failed to get it working both times. I am now trying a third time. I have three remote mail servers to which I can send outgoing mail. I use Balsa as a mail client and, as a test, I set the value of the Remote Server, in the Balsa settings, to each of the three mail servers in turn together with the appropriate values for username and password. I sent an email using each setting and they all arrived. This shows that my username/password combinations are correct for each of the remote servers. I then created an /etc/postfix/sasl_passwd file and transferred the values for all three servers in the form: server.name username:password I then ran postmap hash:/etc/postfix/sasl_passwd. So far so good. Before I go any further I'd like to check the format of the sasl_passwd file. I have seen the form shown above on various howtos after searching on the Internet but I have also seen them where the server is encased in square brackets - [server.name]. Are those brackets required? Having got an answer to that question I'll carry on with the SASL setup and will probably be back with further questions. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Could somebody PLEASE help with an Alsa problem?
I've been struggling with this for days without getting anywhere. I've done endless searches and made some previous postings without any useful results. Debian Testing up to date as of today. Kernel 2.6.22.6 plus alsa modules What is really irritating is that if I boot the same machine using a Knoppix v5 live CD it all works properly. Playback seems to work but recording does not. If I record my voice using the microphone the result is of rather low volume accompanied by an obvious hiss or hum and something that sounds like a motorbike engine. If I try to record using my USB record turntable with Audacity the resulting sound is very choppy but Knoppix does it perfectly. I noticed that when using Knoppix the sound devices listed in Audacity are /dev/dsp, dsp1 and dsp2 but running my normal operating system I get names like 'ALSA: HDA Intel ALC882 Analog (hw:0,0)' Can anyone suggest a course of action? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Re: Could somebody PLEASE help with an Alsa problem?
On 20/09/07 11:13:18, Gabrielle Chatelet wrote: What is the chipset on your sound card? The mainboard is an Asus P5W DH Deluxe with on-board sound Realtek ALC882M. Is that what you meant? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Audacity errors
If I start Audacity from a terminal I see a lot of errors. Is this to be expected? Expression 'SetApproximateSampleRate( pcm, hwParams, sr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1124 Expression 'PaAlsaStreamComponent_InitialConfigure( self-capture, inParams, self-primeBuffers, hwParamsCapture, realSr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1675 Expression 'PaAlsaStream_Configure( stream, inputParameters, outputParameters, sampleRate, framesPerBuffer, inputLatency, outputLatency, hostBufferSizeMode )' failed in 'src/hostapi/alsa/ pa_linux_alsa.c', line: 1799 Expression 'SetApproximateSampleRate( pcm, hwParams, sr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1124 Expression 'PaAlsaStreamComponent_InitialConfigure( self-capture, inParams, self-primeBuffers, hwParamsCapture, realSr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1675 Expression 'PaAlsaStream_Configure( stream, inputParameters, outputParameters, sampleRate, framesPerBuffer, inputLatency, outputLatency, hostBufferSizeMode )' failed in 'src/hostapi/alsa/ pa_linux_alsa.c', line: 1799 Expression 'ret' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 945 Expression 'ret' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 945 Expression 'ret' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 945 Expression 'ret' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 945 Expression 'ret' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 945 Expression 'ret' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 945 Expression 'ret' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 945 Expression 'snd_pcm_start( stream-capture.pcm )' failed in 'src/ hostapi/alsa/pa_linux_alsa.c', line: 1886 Expression 'AlsaStart( stream, 0 )' failed in 'src/hostapi/alsa/ pa_linux_alsa.c', line: 2987 -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Re: Audacity errors
On 16/09/07 13:00:27, Chris Bannister wrote: On Sun, Sep 16, 2007 at 11:41:04AM +0100, Barry Samuels wrote: If I start Audacity from a terminal I see a lot of errors. Is this to be expected? [heaps of errors snipped] You seems to be having a few problems, but you aren't really giving out much information. I didn't know what information might be required. What is the output of: apt-cache policy audacity audacity: Installed: 1.3.3-1+b1 Candidate: 1.3.3-1+b1 Version table: *** 1.3.3-1+b1 0 990 http://ftp.ticklers.org testing/main Packages 100 /var/lib/dpkg/status apt-cache policy alsa-base alsa-base: Installed: (none) Candidate: 1.0.14-1 Version table: 1.0.14-1 0 990 http://ftp.ticklers.org testing/main Packages apt-cache policy alsa-utils alsa-utils: Installed: 1.0.14-1 Candidate: 1.0.14-1 Version table: *** 1.0.14-1 0 990 http://ftp.ticklers.org testing/main Packages 100 /var/lib/dpkg/status uname -r 2.6.22.6 lspci | grep audio 01:00.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07) NOTE: Although there is a SB Live adapter pugged in to the board I am using the mainboard's built in sound chip Intel HDA. 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) That didn't appear in the 'lspci | grep audio' output because it produces 'Audio' and not 'audio'. Can you hear anything out of your souncard when you 'play' anything? Yes. I can play, for example, midi files without problem. I can use Skype with microphone and speakers without problems. I did manage to use Audacity about a year ago for recording and it worked 'out of the box' but since then I've changed the mainboard, the kernel and there have been numerous Debian Testing updates. Many thanks for trying to help. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
cannot submit datapipe for urb 0
Can anyone explain what this error message means? kernel: cannot submit datapipe for urb 0, error -38: enable CONFIG_USB_EHCI_SPLIT_ISO to play through a hub I get this appear in the logs when I click the 'record' button in Audacity which then freezes. I'm trying to record from a record deck with a USB connector and I'm not using a USB hub. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
I hate Alsa [Solved]
Further to my previous posting I have, at last, got sound recording from a microphone working properly again. I don't, however, dislike Alsa any less because I don't know exactly what I did to put it right. I had already run alsaconf twice before posting but tried it again for a third time. There was no indication of any change. I then ran alsamixergui and tried altering the levels of some of the controls. There are 25 sliders on alsamixergui which gives a very large number of combinations. Although the 'Microphone Boost' had no apparent effect in Kmix I tried it with alsamixergui and that together with a lower setting on the 'digital' slider gave me an acceptable result. I 'Transferred' those settings to Kmix and it's still working. USB audio recording still doesn't work at all. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
I hate Alsa
Debian Testing up to date as of yesterday. Kernel 2.6.22 Sound from on-board Intel (snd_hda_intel) Kmix as the mixer When I used OSS I had no audio problems at all - everything (playback and recording) just worked but since I went over to Alsa (about a year ago) I've had trouble getting recording to work. Normally I find that playback gives no problems and I did for a short period get playback and recording working properly then after a Debian upgrade the recording stopped working properly again. If I try to record (arecord) using a microphone I cannot move the recording volume slider above 70% otherwise I start getting extremely distorted sound on playback (aplay) and although the recording volume is adequate there is a loud background hum. If I reduce the recording volume to about 60% the loud hum changes to a noticeable hiss but the recorded voice is too low. I have to use the 'Digital' slider on the Kmix input tab to control microphone volume - none of the other sliders seem to do anything. I also have to have the first capture slider on (un-muted) to get any sound at all but it makes no difference whether that slider is at the bottom or not - it does not affect the volume. I also have a record deck with a USB connection which I last used under OSS. The setup was working then and, as I remember, it was pretty straightforward to set up. Since that time there have been many Debian updates and I'm almost certainly using a later kernel and I'm now using Alsa. When I came to use it this time in conjunction with Audacity, which I was using last time, I can't get a peep out of it. I have tried various inputs without success. The appropriate modules are loaded including snd_usb_audio. When the USB lead is plugged in I get this in the logs: kernel: usb 1-7.1: new full speed USB device using ehci_hcd and address 6 kernel: usb 1-7.1: configuration #1 chosen from 1 choice kernel: input: Burr-Brown from TI USB Audio CODEC as /class/input/input4 kernel: input: USB HID v1.00 Device [Burr-Brown from TI USB Audio CODEC ] on usb-:00:1d.7-7.1 kernel: usbcore: registered new interface driver snd-usb-audio a little further on in the log I see: kernel: cannot submit datapipe for urb 0, error -28: not enough bandwidth Originally I got this in the log: kernel: cannot submit datapipe for urb 0, error -38: enable CONFIG_USB_EHCI_SPLIT_ISO to play through a hub so I enabled that in the kernel and recompiled although I'm not using a USB hub and then got the 'not enough bandwidth' error. As you may have gathered I'm beginning to take a dislike to Alsa. Can anyone suggest some fault tracing procedures please? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Can't get USB Audio to work
I have a record deck with a USB connection which I last used about 9 months ago. The setup was working then and, as I remember, it was pretty straightforward to set up. Since that time there have been many Debian updates and I'm almost certainly using a later kernel. When I came to use it this time in conjunction with Audacity, which I was using last time, I can't get a peep out of it although playing sound files, e.g. midi, does work. I have tried various inputs without success. The appropriate modules are loaded including snd_usb_audio. When the USB lead is plugged in I get this in the logs: kernel: usb 1-7.1: new full speed USB device using ehci_hcd and address 6 kernel: usb 1-7.1: configuration #1 chosen from 1 choice kernel: input: Burr-Brown from TI USB Audio CODEC as /class/input/input4 kernel: input: USB HID v1.00 Device [Burr-Brown from TI USB Audio CODEC ] on usb-:00:1d.7-7.1 kernel: usbcore: registered new interface driver snd-usb-audio a little further on in the log I see: kernel: cannot submit datapipe for urb 0, error -28: not enough bandwidth Originally I got this in the log: kernel: cannot submit datapipe for urb 0, error -38: enable CONFIG_USB_EHCI_SPLIT_ISO to play through a hub so I enabled that in the kernel and recompiled although I'm not using a USB hub and then got the 'not enough bandwidth' error. I'm running an uptodate (today) Debian Testing with kernel 2.6.22 and Alsa modules. Can anyone suggest what I could do to try and trace the fault as I'm way out of my depth here? Regards -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Screensaver killed by some applications
I'm running Debian Testing with KDM/KDE. If I run Qemu it stops the screensaver from working and the only way I've found to get it working again is to stop and re-start X after I have closed Qemu. Anyone else have this? Is there a better way to restart the screensaver? I have tried resetting it in the KDE Control Centre but although screen blanking works power off of the screen after a set time does not work. I have seen this happen occasionally when I'm not running Qemu and I suspect another application but I haven't been able to identify it yet. Regards -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Re: Screensaver killed by some applications
On 19/08/07 14:58:05, Ralph Katz wrote: On 08/19/2007 07:46 AM, Barry Samuels wrote: Is there a better way to restart the screensaver? I have tried resetting it in the KDE Control Centre but although screen blanking works power off of the screen after a set time does not work. Don't know about Qemu or kde, but ~$ man xscreensaver-command may help. mplayer sometimes fails to restart xscreensaver on this box (with openbox window manager). The problem resolves when I invoke this script that I also use sometimes, so a full restart hasn't been necessary: xscreensaver-command -activate sleep 7 xset -display :0.0 dpms force suspend Thanks Ralph. I was using the built in KDE screensaver but I've now disabled that and installed xscreensaver. I'll see what happens with that. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Re: Network printing problem.
On 19/07/07 20:37:22, Florian Kulzer wrote: On Thu, Jul 19, 2007 at 10:58:13 +0100, Barry Samuels wrote: I have two computers at home on a small network both of which are connected to a router. Both computers are running Debian Testing. Computer A has two ethernet ports one of which is connected to the router and one is connected to a network printer. Computer B sends its printing jobs to the network printer via the router. Everything was working well until I upgraded the kernel on computer A from 2.6.20.1 to 2.6.22. After that upgrade network printing from computer B would no longer work with the message 'waiting for IP address to come up'. The odd thing is that I could ping the ethernet port on computer A to which the printer is connect but not the printer itself. Reverting to kernel 2.20.1 on computer A cured the printing problem but means that the sensors temperatures that have worked properly for the first time with 2.6.22 now cannot be displayed (bother!). That seems to mean either a bug in kernel 2.6.22 or a new setting that I have not set. I did copy my 2.6.20.1 config to 2.6.22 and did a make oldconfig. Any comments, suggestions or revalations please? Maybe there was a network-related change in some kernel configuration options and make oldconfig did not take that into account properly. For example, a missing netfilter module might make your firewall on Computer A unduly restrictive. Do you see any network or firewall related error messages in dmesg? I would simply try a stock Debian 2.6.22 kernel image (available in Sid); if that works then you know the problem is the configuration of your custom kernel. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | Florian Thanks for your suggestion. Computer A is normally running 24 hours each day and the last time it would have been re-booted would have been when the new (2.6.22) kernel was installed. Computer B is turned on and off each day. This morning I decided to revert to the 2.6.22 kernel, having been running the 2.6.20.1 kernel since this problem appeared, to try some more investigation. Having re-booted computer A and turned on computer B I find that the printing is now working perfectly again. When the problem first appeared I also tried printing from my laptop which connects via wireless and that couldn't print either so I'm assuming the problem was with computer A. I have no idea what it might have been but it has gone away. Thanks for trying to help. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Network printing problem.
I have two computers at home on a small network both of which are connected to a router. Both computers are running Debian Testing. Computer A has two ethernet ports one of which is connected to the router and one is connected to a network printer. Computer B sends its printing jobs to the network printer via the router. Everything was working well until I upgraded the kernel on computer A from 2.6.20.1 to 2.6.22. After that upgrade network printing from computer B would no longer work with the message 'waiting for IP address to come up'. The odd thing is that I could ping the ethernet port on computer A to which the printer is connect but not the printer itself. Reverting to kernel 2.20.1 on computer A cured the printing problem but means that the sensors temperatures that have worked properly for the first time with 2.6.22 now cannot be displayed (bother!). That seems to mean either a bug in kernel 2.6.22 or a new setting that I have not set. I did copy my 2.6.20.1 config to 2.6.22 and did a make oldconfig. Any comments, suggestions or revalations please? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Audio problems
I'm running Debian Testing - up to date as of yesterday and I'm using Kmix. Since I have updated my kernel to 2.6.22 from kernel.org I am having audio problems with the on-board Intel HDA system. Sound output through the speakers is fine but sound from the microphone is dreadful. The only slider which will control the microphone volume is labelled 'Digital' and the voice volume level is reasonable with the slider at about 55% but there is a very loud background hum/hiss which makes the result unacceptable and I haven't found a way of improving that. I have to have the first 'Capture' slider set on but the slider position makes no difference and can be set at the bottom. As I couldn't make things any better with the HDA I thought that I'd put a SoundBlaster Live adapter I had into the computer as well. The results from that seem even stranger. If I tap the microphone I can hear the sound from the speakers but using Timidity to play a music file produces nothing from the speakers and using Skype gives a deafening silence too. I can't help feeling that I've forgotten something very obvious but not being anything approaching an audio expert I'm stumped. Any miracles gratefully accepted. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
mplayer permissions?
I posted very recently about a problem I was having with mplayer starting and immediately stopping on one of our machines. I have noticed another poster in this list with, apparently, the same problem. I have discovered that root can run mplayer without problems so it seems to be a permissions thing. The user is already in the video group. Can anyone suggest what permissions might be wrong? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
mplayer permissions?
Further to my previous post I discovered that by deleting the mplayer configuration in the user's home directory I could then get mlayer to start from the command line although it would still have the same problem with videos on the web. I realised that on the machine that did work it did have a load of codecs in /usr/lib/codecs which the problem machine didn't have so I installed the w32codecs package and now it all works after a fashion. I say that because after starting, stopping and relaoding a webcam about 2-3 times it goes back to it's old behaviour until the browser is closed and re-started. Anyone with ideas on that please? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
(g)mplayer stops
I have two machines both running uptodate Debian Testing. They both have Mplayer and mozilla-mplayer installed. One of them will play video from the web using Iceweasel and the other won't. On the one that won't I see a message saying 'buffering' then a short while later 'stopped'. Restarting produces the same 'stopped' message. Also on the machine that doesn't play if I start gmplayer or mplayer from a console window the lines displayed are the same as on the machine that does work except for the last line which is: Option Creating needs a parameter at line 1 and then back to the console prompt. Any ideas please? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Audio control problem
I am running 32-bit Debian Testing with a 2.6.20.1 kernel. I am using Alsa modules from that kernel. I don't have any other Alsa packages installed except alsamixergui. I have an Asus P5W DH Deluxe mainboard which has a Realtek ALC882M chipset which works with the snd_hda_intel kernel module. This all works up to a point. Using KMix, xmixer or aumix I can control the speaker volume but not the microphone volume. There are two microphone controls on each of those mixers labelled 'Front Mic' and 'Mic' and neither of them do anything. If I use alsamixergui I see many more control sliders than on the mixers mentioned above. On alsamixergui, although it also has 'Front Mic' and 'Mic' controls, I find that the microphone volume is controlled by a slider called 'Capture' which seems to work well although it seems that the controls settings are not saved between boots. Is there any way of saving the mixer settings? Why the difference in the mixers controls? Why doesn't KMix have the extra sliders that alsamixergui has? I prefer having access to KMix from the KDE Panel so that I can adjust volumes on the fly. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Problems with a Gainward Bliss 7300LE and the nv driver
ASUS P5W DH DeLuxe mainboard Gainward Bliss 7300LE graphics card Debian Testing (up to date) with kernel 2.6.20.1 and Xorg This is in two parts. 1. Using the Xorg nv driver the display is, in general use, perfectly acceptable but when restoring the screen after the screensaver has blanked it or switching back from a text console to the X display I sometimes get a very peculiar effect. It is almost as if parts of the display appear as a negative - white becomes black, yellow becomes blue etc. Any text appears very broken to the point that it is illegible. This only affects parts of some areas of colours i.e. an area of yellow will appear blue in the top half but yellow in the bottom half but another area of white will appear black all over. Have you ever seen a little Tux with green feet? If I then switch to a text console and then back to the X display it nearly always rights itself although sometimes two or more switches are necessary. It cannot be produced on demand. Switching consoles sometimes has no detrimental effect. I did, once, save the screen to a graphic image to try and demonstrate the effect but when viewed the screen in the image looked perfectly normal!!! 2. After the above problems wouldn't go away I installed the nVidia driver from the nVidia web site. To date, I have no problems under X. However when I boot the machine (I have vga=extended in my lilo.conf) the console display is fine until the nvidia driver is loaded. If I then switch back to any text console every line is displayed one and a half times, which is very difficult to read, and, with a screen full of text, the prompt is off the bottom of the screen. Reverting to vga=normal and re-running lilo cures the problem but I would prefer to keep vga=extended. Does anyone have any ideas or suggestions regarding the above? I would really appreciate some help on this. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
waproamd and encryption key
I have waproamd installed on Sarge/Testing and everything seems to work except for assigning a key automatically. I have a file in /etc/waproamd/keys of the form 00:00:00:00:00:00.wep which contains one key. The key _is_ correct as I can copy and paste it onto the command line and it works. However although my wireless card connects I cannot reach the network until I type iwconfig wlan0 key xxx. I have discovered, by running waproamd in the foreground, that the script in /etc/waproamd/scripts is being run and that it extracts and applies the correct encryption key. dhclient is then run which contacts the DHCP server on my network and is assigned an IP address. I assume from this that at this point the wireless network link is made - otherwise how could the DHCP server be contacted? However when this processing has finished the network encryption key appears to have been lost, iwconfig shows 'enc: off', and the network connection is no longer active. The light on the wireless Cardbus card is glowing steadily through all this. If I then set the key with iwconfig as mentioned above everything starts working. I don't understand why this is happening - can anyone help? I'm not subscribed to the list but read it via Usenet. I'm running Debian Sarge/Testing kernel 2.4.27 waproamd 0.6-7 hotplug 0.0.2004032 ndiswrapper Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
A serious X problem after Testing upgrade
I'm running Debian Testing and I did an update last Sunday. I think one, or more, of the packages was X related. I really can't remember any more than that. I did not reboot at that time. One of the new packages was updated source code (minor changes) for my kernel which is 2.4.19. I compiled and installed that and then rebooted. My normal GUI, KDE 2, seems to start and run normally up to a point. If I try to change to a text console using ctrlaltFn the whole machine freezes. Absolutely nothing works after that. I have the magic sysrq key option in the kernel activated but even that did nothing. Only a hard reset would work. I tried booting using my previous kernel with the same results so I've ruled out the new kernel for the time being. If I try to close X in the normal way the machine locks and if I try to kill the X server with ctrlaltbackspace the machine locks. If I try to logout of KDE and return to the KDM login screen the screen goes black with just the graphical mouse cursor showing and the machine locks at that point. ctrlaltdel does the same. The same things happen if I use Icewm so it's not KDE. I am assuming that this is an X problem. The new X packages re-created /etc/X11/XF86Config-4 so I restored my original to no effect. Still just as bad. I have no idea where, or how, to start looking and some advice is sorely needed and would be very welcome. Barry Samuels I redirected X output to a file which is included below and the XFree log is also appended below in case it means anything to anybody. I'm sorry if it seems rather long. NOTE: The reference to ATI is an on-board video chip which is not used. === X output: hostname 2.08 X: warning; process set to priority 0 instead of requested priority -10 XFree86 Version 4.2.1 (Debian 4.2.1-3 20021016191246 [EMAIL PROTECTED]) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.18 i686 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Wed Nov 6 11:51:21 2002 (==) Using config file: /etc/X11/XF86Config-4 (EE) MGA: Failed to load module mga_hal (module does not exist, 0) modprobe: Can't locate module mga [drm] failed to load kernel module mga (EE) MGA(0): [drm] DRIScreenInit failed. Disabling DRI. IceWM: Bad option: TaskBarShowPPPStatus IceWM: Bad option: IgnoreNoFocusHint IceWM: Bad option: ShowXButton IceWM: Bad option: WindowListFontName === /var/log/XFree86.0.log: XFree86 Version 4.2.1 (Debian 4.2.1-3 20021016191246 [EMAIL PROTECTED]) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.18 i686 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Wed Nov 6 08:36:41 2002 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Iiyama Vision Master 17 (**) | |--Device Matrox G400 (**) |--Input Device Generic Keyboard (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout us (**) XKB: layout: us (**) Option XkbVariant uk (**) XKB: variant: uk (==) Keyboard: CustomKeycode disabled (**) |--Input Device Configured Mouse (WW) The directory /usr/lib/X11/fonts/cyrillic does not exist. Entry deleted from font path. (**) FontPath set to unix/:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi (==) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (++) using VT number 7 (WW) Open APM failed (/dev/apm_bios) (No such file or directory) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.5 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (II) Loader running on linux (II) LoadModule
2nd try - Faxgetty, MGetty and data calls
I've spent hours and hours trying to set up Hylafax/Faxgetty to auto detect fax/data calls and respond appropriately for data calls. I have had partial success in that I can now get it to distinguish between fax and data calls and accept the fax or start mgetty for a data call. Fax calls, receiving and sending, work well. Part of my original problem was that the Debian default config.ttyS1 GettyArgs included -h as the first option which caused Mgetty to start and then immediately stop after printing a 'Usage' line in the log. I have, at least been able to correct that. My current config.ttyS1 gettyargs is: GettyArgs: -D %l dx_%s I have also tried -r -s %s %l together with many other combinations. If I dial in from another machine the call is answered as a data call and mgetty started but on the machine that I dialled in from I see a line of about two dozen characters, most of which appear to be '?', then the cursor returns to the beginning of the line, overwrites part of the existing line before dropping down one line, printing a few more characters then dropping down another line and displays 'NO CARRIER'. I never get to see a login prompt and these tests are costing me a fortune in telephone calls! It doesn't seem to make any difference whatever options I try the result is always as described above. The getty on the Hylafax machine is left running and has to be killed. The mgetty log shows: 02/23 09:52:33 yS1 mgetty: experimental test release 1.1.21-Jul24 02/23 09:52:33 yS1 check for lockfiles 02/23 09:52:33 yS1 huh? It's *our* lock file! 02/23 09:52:33 yS1 locking the line 02/23 09:52:33 yS1 makelock(ttyS1) called 02/23 09:52:33 yS1 do_makelock: lock='/var/lock/LCK..ttyS1' 02/23 09:52:33 yS1 we *have* the line! 02/23 09:52:33 yS1 lock made 02/23 09:52:34 yS1 tio_get_rs232_lines: status: RTS CTS DSR DTR 02/23 09:52:34 yS1 tss: set speed to 115200 (10002) 02/23 09:52:34 yS1 tio_set_flow_control( HARD ) 02/23 09:52:34 yS1 waiting for line to clear (VTIME), read: 02/23 09:52:34 yS1 send: \d\d\d+++\d\d\dATZ[0d] 02/23 09:52:37 yS1 waiting for ``OK'' 02/23 09:52:37 yS1 got: [0d][0a]CONNECT[0d][0a][0d][0a]OK ** found ** 02/23 09:52:43 yS1 waiting for line to clear (VTIME), read: [0d][0a] 02/23 09:52:43 yS1 removing lock file 02/23 09:52:43 yS1 waiting... Although, in this section, the modem is reset I have tried other options which give the following in the log: 02/23 09:40:20 yS1 mgetty: experimental test release 1.1.21-Jul24 02/23 09:40:20 yS1 check for lockfiles 02/23 09:40:20 yS1 huh? It's *our* lock file! 02/23 09:40:20 yS1 locking the line 02/23 09:40:20 yS1 makelock(ttyS1) called 02/23 09:40:20 yS1 do_makelock: lock='/var/lock/LCK..ttyS1' 02/23 09:40:20 yS1 we *have* the line! 02/23 09:40:20 yS1 lock made 02/23 09:40:20 yS1 tio_get_rs232_lines: status: RTS CTS DSR DTR 02/23 09:40:20 yS1 tss: set speed to 115200 (10002) 02/23 09:40:20 yS1 tio_set_flow_control( HARD ) 02/23 09:40:20 yS1 waiting for line to clear (VTIME), read: 02/23 09:40:20 yS1 send: \dATQ0V1H0[0d] 02/23 09:40:21 yS1 waiting for ``OK'' 02/23 09:40:21 yS1 got: [0d][0a]OK ** found ** 02/23 09:40:21 yS1 send: AT[0d] 02/23 09:40:21 yS1 waiting for ``OK'' 02/23 09:40:21 yS1 got: [0d][0a][0d][0a]OK ** found ** 02/23 09:40:21 yS1 waiting for line to clear (VTIME), read: [0d][0a] 02/23 09:40:22 yS1 removing lock file 02/23 09:40:22 yS1 waiting... I have also read as much documentation as I could find without any luck and have tried posting on two newsgroups and the Debian mailing list once before but have had no replies. I am running Debian 2.2 with kernel 2.2.18pre21, I have a Hayes Accura 56k fax/data modem and I am running Hylafax version 4.0.2-14. The machine that I'm dialling in from is running Windows 95 although I have tried it from another Debian machine using Minicom with exactly the same results. I'm no longer subscribed to the list so any e-mail (see address below) replies would be welcome. I do follow the list in the Debian archives but that lags behind by about a day. I apologise in advance for that bit of important information that I have almost certainly forgotten to include. What am I doing wrong? Help would be very much appreciated. Barry Samuels My real e-mail address is: bsamuels (AT) datamansys (DOT) co (DOT) uk
Faxgetty, Mgetty and data calls are driving me potty!
I've spent hours and hours trying to set up Hylafax/Faxgetty to auto detect fax/data calls and respond appropriately. I have had partial success in that I can now get it to distinguish between fax and data calls and accept the fax or start a getty for a data call. Part of my original problem was that the default config.ttyS1 GettyArgs included -h as the first option which caused Mgetty to start and then immediately stop after printing a 'Usage' line in the log. My current config.ttyS1 gettyargs is: GettyArgs: -D %l dx_%s I have also tried -r -s %s %l together with many other combinations. If I dial in from another machine the call is answered as a data call and the getty started but on the machine that I dialled in from I see a line of about two dozen characters, most of which appear to be '?', then the cursor returns to the beginning of the line, overwrites part of the existing line before dropping down one line, printing a few more characters then dropping down another line and displays 'NO CARRIER'. I never get to see a login prompt and these tests are costing me a fortune in telephone calls! The getty on the Hylafax machine is left running and has to be killed. My current config.ttyS1 gettyargs is: GettyArgs: -D %l dx_%s I have also tried -r -s %s %l together with many other combinations. The mgetty log shows: 02/23 09:52:33 yS1 mgetty: experimental test release 1.1.21-Jul24 02/23 09:52:33 yS1 check for lockfiles 02/23 09:52:33 yS1 huh? It's *our* lock file! 02/23 09:52:33 yS1 locking the line 02/23 09:52:33 yS1 makelock(ttyS1) called 02/23 09:52:33 yS1 do_makelock: lock='/var/lock/LCK..ttyS1' 02/23 09:52:33 yS1 we *have* the line! 02/23 09:52:33 yS1 lock made 02/23 09:52:34 yS1 tio_get_rs232_lines: status: RTS CTS DSR DTR 02/23 09:52:34 yS1 tss: set speed to 115200 (10002) 02/23 09:52:34 yS1 tio_set_flow_control( HARD ) 02/23 09:52:34 yS1 waiting for line to clear (VTIME), read: 02/23 09:52:34 yS1 send: \d\d\d+++\d\d\dATZ[0d] 02/23 09:52:37 yS1 waiting for ``OK'' 02/23 09:52:37 yS1 got: [0d][0a]CONNECT[0d][0a][0d][0a]OK ** found ** 02/23 09:52:43 yS1 waiting for line to clear (VTIME), read: [0d][0a] 02/23 09:52:43 yS1 removing lock file 02/23 09:52:43 yS1 waiting... Although, in this section, the modem is reset I have tried other options which give the following in the log: 02/23 09:40:20 yS1 mgetty: experimental test release 1.1.21-Jul24 02/23 09:40:20 yS1 check for lockfiles 02/23 09:40:20 yS1 huh? It's *our* lock file! 02/23 09:40:20 yS1 locking the line 02/23 09:40:20 yS1 makelock(ttyS1) called 02/23 09:40:20 yS1 do_makelock: lock='/var/lock/LCK..ttyS1' 02/23 09:40:20 yS1 we *have* the line! 02/23 09:40:20 yS1 lock made 02/23 09:40:20 yS1 tio_get_rs232_lines: status: RTS CTS DSR DTR 02/23 09:40:20 yS1 tss: set speed to 115200 (10002) 02/23 09:40:20 yS1 tio_set_flow_control( HARD ) 02/23 09:40:20 yS1 waiting for line to clear (VTIME), read: 02/23 09:40:20 yS1 send: \dATQ0V1H0[0d] 02/23 09:40:21 yS1 waiting for ``OK'' 02/23 09:40:21 yS1 got: [0d][0a]OK ** found ** 02/23 09:40:21 yS1 send: AT[0d] 02/23 09:40:21 yS1 waiting for ``OK'' 02/23 09:40:21 yS1 got: [0d][0a][0d][0a]OK ** found ** 02/23 09:40:21 yS1 waiting for line to clear (VTIME), read: [0d][0a] 02/23 09:40:22 yS1 removing lock file 02/23 09:40:22 yS1 waiting... I am running Debian 2.2 with kernel 2.2.18pre21, I have a Hayes Accura 56k fax/data modem and I am running Hylafax version 4.0.2-14. The machine that I'm dialling in from is running Windows 95. I apologise in advance for that bit of important information that I have almost certainly forgotten to include. What am I doing wrong? Help would be very much appreciated. I'm no longer subscribed to the list so any e-mail (see below) replies would be welcome. I do follow the list in the Debian archives but that lags behind by about a day. I have also read as much documentation as I could find without any luck and have tried posting on two newsgroups but have had no replies. Barry Samuels My real e-mail address is: bsamuels (AT) datamansys (DOT) co (DOT) uk
Surely someone must have a solution to my recording problem?
I have a SoundBlaster PCI 128 Live and I am running Debian 2.2 with kernel 2.2.17. Using the Emu modules everything works as expected except for sound recording. Sound recording creates a properly formated .Wav file except that the values are so low as to be inaudible! I am trying to record using input via the line input and this certainly gives audible sound via the speakers even when recording is supposed to be taking place. I haven't forgotten anything so silly as to un-mute the appropriate inputs unless there is a hidden mute somewhere that I don't know about. If I boot the machine into Windows and use the software supplied with the SoundBlaster I can create normal recordings, using signals from the line input, which will also play back under Debian. So I have ruled out hardware problems. I did contact the Emu people at Creative and I quote part of the reply below: === I looked at the file, and as you suspected it is a properly-formatted WAV file with almost-null data in it. Quite telling is the fact that the data isn't actually null -- but the values are incredibly small and aren't audible. What this is telling me is that recording _is_ taking place, but on an input which is inactive (through software or hardware -- can't tell). I was not expecting these results. I was thinking that either the file would be formatted incorrectly or that it would have true null data. In either of those cases, the problem would have likely been with either faulty recording software or with the configuration of the Live. As it is, I'm stumped as to what the problem is. === I have tried recording using a number of different Linux applications (e.g. khdrec, kmedia, krecord, gramofile) for recording together with different mixers ( e.g. kmix, aumix ) and various versions of the Emu modules but all to no avail. So - a brief resume: 1. He's stumped. 2. I'm stumped. 3. Everybody else, so far, is stumped. Is there a genius in the house? Barry Samuels
Re: libc5 / libc6
Liam Ward [EMAIL PROTECTED] wrote: I decided to see if asking APT to install the libc5 package in simulate mode would suggest the removal of libc6 and it doesn't, which suggests I could simply install the libc5 package. However, I'm too scared to do it without checking that I'm not going to break everything. I am running WordPerfect which requires libc5 and, consequently, I have libc5 installed as well as libc6. It has caused me no problems whatsoever. Barry Samuels
Re: Multiple netscapes; multiple x servers; a question
Douglas Eck [EMAIL PROTECTED] wrote: My wife and I use the same debian box. We don't want to log in and out, and so I've been logging in as her in KDE, doing an xhost + mymachine and then using telnet/ssh to log in as me. snip Two possible solutions: 1) Netscape 4.75 works and all is well. We can continue with this plan. 2) Run 2 xservers and ctrl-alt-Fx back and forth. Does this second solution slow things down a lot? I have a 350K6 with 128Mb RAM. Also, is there a MINI-HOWTO on setting up two Xservers. I thought it would be really easy but had some troubles getting everything to work just so. I have used your second option on my machine (233 MHz Pentium x 2 SMP and 128 Mb ram) to run two X servers both with KDE. I have not noticed any difference from when I have just the one X server running. I just change to console tty2 (CTR-ALT-F2) and start X thus: startx kde -- :1 I have not noticed any problems. Barry Samuels
Any knowledgeable Afio people out there?
After Afio has created an archive it produces a message similar to: 'afio: Final count: 7m+12k+0 bytes written' Is the size given the size of the files before they were archived or is it the size of the compressed archive? My next query is not produced by Afio but by the SCSI Tape module when Afio was running. I use Afio in my backup script and the last backupo failed because, I think, the tape was faulty. I have since re-run the backup successfully with a different tape. However during the failed backup the following messages were added to /var/log/messages: Sep 26 09:07:55 DATAMAN1 kernel: st0: Error with sense data: Info fld=0x3fff, Current st09:00: sense key Medium Error Sep 26 09:07:55 DATAMAN1 kernel: Additional sense indicates Medium format corrupted This in itself is not surprising but there were about 20,000 similar lines. Could that be considered normal under the circumstances? Barry Samuels
Re: graphic login failure
Michael P. Soulier [EMAIL PROTECTED] wrote:
Just did a dist-upgrade from woody, helixcode and kde2.
login as root fails, but can 'su', 'su - root' from terminal.
Check the startup procedure for startx. Look for a $HOME/.xsession file in
the home directory, that gets run if it's there. You mention that it's root,
does that mean that it's not other users having the problem? I suspect
.xsession then.
I'm having the same problem. Can't login as root ('login failed') but I can
login as user
but root does not have an .xsession file. Can get in to KDE2 via a console.
Barry Samuels
Re: Bug in xconfig???
Cam Ellison [EMAIL PROTECTED] wrote: After building the 2.2.17 kernel several times using xconfig, I have come to the conclusion that it is incomplete or I'm either half-blind or losing it. I cannot find any reference to setting up ppp. It's in Network Device Support. Barry Samuels
Re: pppd dies immediately in kppp
Thomas Halahan [EMAIL PROTECTED] wrote: I cannot get kppp to work. After the handshake with my ISP, I can see it connect, but the pppd daemon dies immediately. I can connect with the 'pon' command. I get the following error with kppp: pppd: The remote system is required to authenticate itself pppd: but I couldn't find any suitable secret (password) for it to use to do so. pppd: (None of the available passwords would let it use an IP address.) Look in your /etc/ppp/options file for 'auth' on a line on its own and change it to 'noauth' then try again. Barry Samuels
Re: no PPP support
john gennard [EMAIL PROTECTED] wrote: Have recently installed Debian 2.2 (already run 2.1), and use KDE 1.1.2. When I launch Kppp the following message appears:- This kernel has no PPP support neither compiled in nor via the kernel module loader. To solve this problem:- * contact your system administator or * install a kernel with PPP support At this point, I click 'connect', download my mail and send any outgoing messages, (this is one). After installing Potato, I recompiled the kernel to my normal requirements - these include PPP support. Any ideas why the error message appears, and how to eradicate it? Upgrading to the latest version of kppp 1.6.25 cured the problem for me! Best of luck Barry Samuels
Re: Firewall message in /var/log
Rino Mardo [EMAIL PROTECTED] wrote: On Tue, Sep 05, 2000 at 04:46:44PM +0100 or thereabouts, Barry Samuels wrote: Can anyone tell me why I should keep getting this message in my /var/log/messages (I'm afraid I don't speak ipchains): kernel: Packet log: input DENY eth0 PROTO=17 192.14.17.1:513 192.14.17.255:513 L=136 S=0x00 I=244 F=0x T=64 (#30) I set my firewall up with PMFirewall supposedly to ignore my internal network. you didn't tell us more about the services or setup you're running. did you setup pm using the defaults? I believe that I accepted most of the defaults except that I remember replacing eth0 with ppp0 at one point. I was aiming to filter packets from the internet whilst leaving my small internal network alone. Barry Samuels
Re: Firewall message in /var/log
John L . Fjellstad [EMAIL PROTECTED] wrote: On Tue, Sep 05, 2000 at 04:46:44PM +0100, Barry Samuels wrote: kernel: Packet log: input DENY eth0 PROTO=17 192.14.17.1:513 192.14.17.255:513 L=136 S=0x00 I=244 F=0x T=64 (#30) Check the IPCHAINS-HOWTO. I have. I tend to find quite a few of these documents moderately incomprehensible. In short, kernel - message from kernel Packet log - log stamp I can understand that! input - chain in which packet got logged Not sure about that (chain?). DENY - access I can understand that! PROTO=17 - udp Looked up 'man udp'. Found that to be _totally_ incomprehensible. 192.14.17.1:513 - source of package with originating at port 513 (who port) 192.14.17.255:513 - destination of package, connecting at port 513 Looked up 'man rwhod' and could understand some of that. So I suppose the Ipchains rules need to be modified to stop it whingeing about that. This is where it gets very tricky. I used pmfirewall, on someone's recommendation, because I wanted to avoid messing about with something that I don't understand and found pmfirewall to be just my sort of thing. Perhaps I'll just put up with the messages. Barry Samuels
Re: Seyon with incoming calls
Dave Thayer [EMAIL PROTECTED] wrote: Thanks for your reply Dave - the only one so far. On Fri, Sep 01, 2000 at 10:45:14AM +0100, Barry Samuels wrote: I am trying to get Seyon to answer incoming calls and there is, strangely, no mention of answering incoming calls in the documentation. [...] What do I need to do to establish a connection for file transfer for an incoming call? IMO, Seyon wasn't really designed to handle incoming calls. I recommend installing mgetty to listen on your modem line. Mgetty gracefully shares serial lines with dialout programs like seyon or minicom, but will handle incoming connections and even take incoming faxes. I already have mgetty installed, together with Hylafax, and I understand that mgetty will pass on non-fax calls but how does it know where to pass those calls to ( e.g. Seyon) ? Depending upon what sort of remote system you are using you could just log into a shell and use zmodem or kermit to transfer files, or you could get fancy and set up pppd and samba or nfs to remotely access your filesystems. The remote system is a friend who is a complete computer Dumbo but who can, just about, work a windows comms package to dial my machine at which point I want to initiate a file transfer. Why do I want to do it this way round? He pays for the call! I have been doing this with ZOC on OS/2 but am now, slowly, transferring operations to Linux. Barry Samuels
Firewall message in /var/log
Can anyone tell me why I should keep getting this message in my /var/log/messages (I'm afraid I don't speak ipchains): kernel: Packet log: input DENY eth0 PROTO=17 192.14.17.1:513 192.14.17.255:513 L=136 S=0x00 I=244 F=0x T=64 (#30) I set my firewall up with PMFirewall supposedly to ignore my internal network. Barry Samuels
Seyon with incoming calls
I am trying to get Seyon to answer incoming calls and there is, strangely, no mention of answering incoming calls in the documentation. I have set up an extra button, as per documentation, to transmit an ATA to the modem. This does cause the modem to answer but no proper connection between the two modems is made. What do I need to do to establish a connection for file transfer for an incoming call? Barry Samuels
Re: Restoring with taper
Dr. Orange [EMAIL PROTECTED] wrote: Is there a way to choose individual files or directories with taper. I enter the restore section and i don't see a way of entering the info file in order to do this. I don't know much about Taper. Tried it once and couldn't get it to work properly. I imagine it's possible, but if it's not, could someone point me to another backup tool (besides tar) that is good, and can restore individual files or dirs. Have you tried Afio? That's what I use. Barry Samuels
Re: Very strange system/sound problem
Philipp Schulte [EMAIL PROTECTED] wrote: I am running Debian Potato on a machine which is totally SCSI ( I feel that way myself sometimes) and includes a PlexWriter CD-Writer and a SoundBlaster Live 1024. I hadn't used my machine this morning and I happened to enter the room to hear clicks coming from both speakers. I tried lsmod and no sound modules were loaded. I also discovered that every movement of the mouse produced rapid clicks from the speakers. The mouse, by the way, is on IRQ 5 and the sound card on an IRQ above 10. Using the keyboard also produced clicks as did ejecting the CD tray (no CD). I decided to close down and reboot the machine. The clicks continued right through closedown and didn't stop until the machine actually started to reboot. Did the clicks stop after the reboot? Yes for about 4 hours then started up again gradually becoming more pronounced with time. To me it sounds like a physical phenomenon - not software. You have to realize that there are many different forms of electricity inside a computer system and under special circumstances they might produce strange things. Do you know about induction? Phil It may well be physical (yes I know about Induction). The first time it happened I tried to reboot immediately but the boot wouldn't go past the SCSI bios part so I powered down and left the machine off for about 30 minutes and then restarted. After about 4 hours the sound problem restarted and when trying to reboot the machine it again wouldn't go past the SCSI bios part. I turned off again for about 5 minutes and restarted. That was about 24 hours ago with no recurrence of the problem yet!!! My suspects are in order of likelyhood: Mains electricity supply (although the computer is on an UPS). Faulty component somewhere. Software. I have never come across anything like this before but then I've not had a sound card before and with the speakers turned off there is no indication of any problem. I shall wait and see what happens over time. Barry Samuels
Very strange system/sound problem
I am running Debian Potato on a machine which is totally SCSI ( I feel that way myself sometimes) and includes a PlexWriter CD-Writer and a SoundBlaster Live 1024. I hadn't used my machine this morning and I happened to enter the room to hear clicks coming from both speakers. I tried lsmod and no sound modules were loaded. I also discovered that every movement of the mouse produced rapid clicks from the speakers. The mouse, by the way, is on IRQ 5 and the sound card on an IRQ above 10. Using the keyboard also produced clicks as did ejecting the CD tray (no CD). I decided to close down and reboot the machine. The clicks continued right through closedown and didn't stop until the machine actually started to reboot. Any ideas? Barry Samuels
KDE and Potato
One thing puzzles me about the Potato KDE list on kde.tdyc.com. If I try to upgrade to the Potato KDE packages I find that some of the packages use qt1 and some use libqt1. Because qt1 and libqt1 are incompatible this causes DSelect to automatically mark quite a lot of packages for removal that I want to keep. Because of this I have stayed with the Slink versions. Is there any way to upgrade and keep all the KDE packages that I have currently installed? Barry Samuels
Re: kde.tdyc.com
One thing puzzles me about the Potato KDE list. If I try to upgrade to the Potato KDE packages I find that some of the packages use qt1 and some use libqt1. Because qt1 and libqt1 are incompatible this causes DSelect to automatically mark some packages for removal that I want to keep. Because of this I have stayed with the Slink versions. Is there any way to upgrade and keep all the KDE packages that I have currently installed? Barry Samuels
Potato and emu
Running Debian Potato (frozen) and Slink KDE I have an SB Live 1024 Player and a recent version (2721) of the Emu sound module . Should I get any output from cat /dev/sndstat? All I do get is 'No such device'. There is definitely a 'sndstat' in /dev and I do get sound when playing a CD. Barry Samuels
Re: My first ever incursion into sound isn't very successful
On Mon, 24 Jul 2000, you wrote: Steve Thanks for your reply. As far as getting modules to load at boot, just put whatever modules you would specify after modprobe into /etc/modules. I have no experience with your sound card, but it seems that any true SB should not be too difficult, since most others operate in SB emulation mode under Linux. I have found ALSA to be far and away the best solution for the cards I have installed.Good luck, Steve Stancliff I already have the appropriate statement in /etc/modules but I understand that the module should load automatically on demand as do other modules on my system. This module won't. Barry Samuels ---
My first ever incursion into sound isn't very successful
Debian Potato (frozen) with Slink KDE I have just bought my first ever soundcard, a SoundBlaster Live 1024 Player, and my attempts to setup sound have been only partially successful. I first tried the latest (2721) Creative Emu driver. Downloaded, compiled the source and installed the modules. First problem - the module(s) won't load automatically as other modules do. I can, of course, load them with modprobe and, using kscd, I can play a CD successfully. But I would rather have them load automatically. Is there a way to do this? I have also ldownoaded an application called Broadcast which records onto the hard drive. However the record/playback part of this doesn't work and displays a message in the console window to the effect that it cannot access the sound device. Perhaps it won't work with the emu drivers but there is no clue in the documentation as to what the sound device is from this applications point of view. The appropriate sound devices do appear to be in /dev (audio, dsp, midi, mixer, sequencer, sndstat). I then decided to try the Alsa drivers and installed the appropriate Alsa Potato packages. This appeared to successful except that there were no actual driver modules included or installed. I find this a bit puzzling. I downloaded matching version drivers from the Alsa site and installed them. The nearest card in the list was a SB PCI 128 but the module would not load (device busy). Incompatible with the 1024 perhaps. I removed the Alsa stuff altogether. Any advice would be welcome as I am a total beginner when it comes to sound. Barry Samuels
Re: A strange little kppp error
On Sat, 22 Jul 2000, John Hasler wrote: That doesn't explain why the same error message is *not* displayed when running kppp as root. The message originates with pppd. When it is unable to access the resources it needs it jumps to the erroneous conclusion that there is no ppp support in the kernel. When run by root it can access anything. -- John Hasler I had assumed some permissions problem. Is that what you are saying and if so can you suggest where I might look? Barry Samuels
Re: Background mail transfers
On Tue, 18 Jul 2000, Simon Michael wrote: hmm.. surely fetchmail normally would take this in stride, re-fetching the message next time ? Whoops! Embarrassing admission time. Your remark above triggered the thought processes and I've work out what I think happened. I am not yet using the linux mail processing as my main mail handler until I'm satisfied that it's working properly so I have set fetchmail not to delete mail from the server. But I also download the mail using OS/2 which then deletes the mail from the server. So I suspect that having chopped off Fetchmail's download leaving half an e-mail I subsequently re-booted into OS/2 and downloaded the mail. This would have then deleted the mail from the server so that the next time the mail server was checked using Fetchmail the e-mail as mentioned above was no longer there. I hadn't thought that through when I posted to this list. Apologies all round. If you ignore me I may go away! Barry Samuels
Background mail transfers
I normally work within a window manager environment (mostly KDE) when using Debian Potato and have used KMail to download mail directly from my ISP pop3 accounts. I recently decided to setup fetchmail to poll my pop3 mail servers in the background, download any waiting mail and pass it on to procmail for sorting into appropriate folders and then access these folders using KMail. This works well but I have realised recently that, because this is now happening in the background, if I disconnect from my ISP without thinking I can cut a mail download off in mid-stream. I have half an e-mail to prove it. Can anyone suggest a way to prevent this apart from running Fetchmail manually? Barry Samuels
I cannot get JunkBuster to work
I have JunkBuster installed on Potato and it is running as a daemon but it won't filter anything. I also have Woffle running on port 8080 and that is specified as the proxy server in Netscape. I understand that to get JunkBuster to work as well I need to make appropriate entries in the JunkBuster forward file. I havn't specified a specific listening address and I don't understand a word of the instructions for the forward file. The examples given don't seem appropriate to my case. I have tried a number of different entries in the forward file but none of them have produced the required result. Could someone please explain what I need to do. Barry Samuels
