Woody Installation Problem
I'm a Linux newbie, and am having a problem installing Woody from CD. During the initial installation I ran tasksel with various tasks selected. While unpacking stuff from CD 3 and error occurred: cxref /usr/bin/dpkg returned error code (1) At that point [things are a bit fuzzy, this was several days ago] the installation routine appeared to return me to tasksel again. I didn't have time to continue and so aborted the process. The next time I booted the system I found that [with a little tweaking] I have a partially working Linux system. X-windows comes up, as does Gnome. However, various help pages are missing, for example, clicking on the gnome-help-manager returns the error Missing TOC I then attempted to run tasksel, thinking that it would finish up the installation. No luck. The only options it now allows are those I previously did NOT select; i.e. I assume it thinks it has correctly installed everything. I then ran dselect, but couldn't figure out how to tell it to find the files on the CDROM. So, now what do I do? Reboot from CD1 (or my boot floppy)? Thanks for any help Joe Riel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Woody Installation Problem
>Maybe that CD has errors on it. You can check it by mounting it, going to >the directory where it's mounted, then > >md5sum -c md5sums.txt > >No output = good, error output=bad Thanks, I'll try that. >If so you'll need to get a new cd or install those packages from http or ftp. > > >> I then ran dselect, but couldn't figure out how to tell it to find the >> files on the CDROM. So, now what do I do? Reboot from CD1 >> (or my boot floppy)? > >In dselect, choose "Access" from the main menu, and it has a cdrom option. >You could try uninstalling the broken package, then re-installing it from the >cd again from an ftp or http source (choose under "Access" again in dselect). I had tried that, but there was, alas, no option for multi-CD. I have no idea how many packages might be broken. During the install, only the first 3 CDs were used [except for the initial "indexing" of the CDs]. Is there a way to restart tasksel so that it will prompt for all the tasks again [not just the ones that weren't selected the previous time]? Joe Riel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Woody Installation Problem
>apt-get install dpkg-multicd > >(I think this should be in the dselect tutorial section of the debian install >manual but it isn't - I'll submit a bug report to install-doc unless someone >knows why I shouldn't) > >Then you will have access to the multicd method in dselect. There are >instructions for using it in the debian installation manual -> Advanced >Package Selection with dselect -> dselect tutorial: >http://www.debian.org/releases/stable/i386/dselect-beginner > >You can also add multiple cd's to your sources with apt-cdrom. >Just put a cd in and type "apt-cdrom add", or "apt-cdrom -cdrom /mountpoint >add" if it can't find your cd. "man apt-cdrom" for more info. Then you >could use > apt-get remove packagename and > apt-get install packagename >to re-install packages. I tried the first approach, running dselect and chosing multicd, after first installing dpkg-multicd. It was not at all clear what to do after that. http://www.debian.org/releases/stable/i386/dselect-beginner implies that using multicd access is a bit tricky; that is correct. I never got it to work. So I changed the access method to apt--- previously I had assumed that that was only for downloads from a web site---and things proceeded much smoother. dselect would now query for the proper CD when it needed to install a selected package. Thanks, Joe Riel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Ctrl-Alt-F7 doesn't work with Intel D845GBV M/B
I have installed the stable version of Woody and am running X. X can start fine, but if I switch to a console tty, say with Ctrl-Alt-F1, then I cannot get back to X via Alt-F7 or any other combination. The monitor "clunks", like it's trying to do something, but the screen stays black. I have an Intel D845GBV motherboard with no add-on graphics card. I checked the Intel site for this motherboard. It mentioned a few things (none clearly specific to my problem): (1) configure the bios for an 8MB frame buffer size (the default is 1MB). I did that, it increased the available resolution of the screen but the problem persists (2) there is some support for this graphic chip on the latest version Xfree86 (4.2.1?) That is not the version that ships with Woody. I haven't yet tried to upgrade X. Has anyone experienced this problem and found a resolution? Thanks, Joe Riel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Manually starting X
I have installed a basic X system (Woody stable). When the system boots, the gui login window comes up. When the window manager (twm) is shutdown, the screen goes black and the login window does not reappear. To get back into X I have to open a terminal console, login as root, and reboot the machine. Needless to say, this isn't convenient. As a workaround, I'm wondering how to change the init procedure so that X does not start (I tried removing the S99Xdm script in /etc/rc2.d; that did prevent X from starting but running startx had problems; I'm guessing parts of S99Xdm script must be run). Any suggestions on the proper way to setup the box so that it doesn't auto-start X? Even better would be a suggestion for getting the gui login window back; however, I suspect that that is related to the problem I with not being able to reconnect to X via Alt-F7. Thanks, Joe Riel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Manually starting X---Update
Here is the latest on my problem starting X manually. First, I'm running the stable version of version (obtained from the CDrom distribution). M/B is an Intel D845GBV (1.6GHz P4). Video is from the on-board device, there is no separate graphics card. I modified the /etc/X11/default-display-manager so that no dm was selected. After rebooting the system came up with a console login (no gui login, as was the previous case). I logged in as a user (not root) and ran startx >& joeX.log. The screen went black, the monitor "thunked", and then the screen returned to the console. X was running somewhere in the background, but I couldn't get it on the display. I then tried the same thing as root. This time the "screen" did not return to the console, it just stayed black. I opened a tty port and killed X. I posted a few files to my web page: /etc/X11/XF86Config-4 --> http://www.k-online.com/~joer/XF86Config-4 error log from starting X as user (joe) --> http://www.k-online.com/~joer/joeX.log error log from starting X as root --> http://www.k-online.com/~joer/rootX.log When I first checked the error log from startx, I noticed that there were some error messages due to a misconfigured mouse. I commented out appropriate sections of XF86Config-4; the file posted has those sections commented out. I then restored /etc/X11/default-display-manager so that it points to xdm. Following a reboot, the system started as before (gui login). Logging out of the system had the same problem (black screen, no way to login back into X). Is my next step to purchase a video-card and not use the built-in video circuitry on the Intel m/b? That seems a bit drastic. I'm reluctant to continue with my install until I have a reasonably functional system... Joe Riel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Manually starting X---Another update
11/9/02 2:41:37 AM, Shaul Karl <[EMAIL PROTECTED]> wrote: >1. Referring to your initial post, instead of booting to get another gui > login screen after terminating the previous one you might try to > issue > /etc/init.d/xdm restart. > This is not a solution in the long run but can help you to identify > where the problem is. It is not, alas, a solution in the short run, either. /etc/init.d/xdm restart does not get me back to an X login, just the "black screen of death". I removed xdm from the initialization process. Now, following a reboot, I can issue startx and X will start. I could also run /etc/init.d/xdm start and get a graphical login. However, if I ever log out of X I again have to reboot to get back in. Could the video chip [?] (I have an Intel D845GBV M/B and am using the onboard video) require some sort of reset? Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Setting default width of xman
When I select manual page in the xman startup window, the window for the manual is too narrow, I have to manually increase it to the proper size. How can I change the default size? I read the xman man page, it mentions the -pagesize option, which does work if I start xman from the command line, e.g. > xman -pagesize 800x900 & however, I would like to be able to start xman by using the mouse (I'm currentlly running fvwm). The xman man page does not mention a resource for setting page width, I tried Xman*Pagesize:800x900 in .Xdefaults, that had no effect. Xman*Geometry: 800x900 causes the xman start window (the little guy with three or four buttons) to be huge, not at all what I want. Thanks for any suggestion. Joe Riel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Setting default width of xman
11/15/02 9:05:08 AM, Michael Naumann <[EMAIL PROTECTED]> wrote: >What you want is >Xman*manualBrowser.geometry :800x900 >in your .Xdefaults. Thank you. How did you figure this out? More generally, how can I find the available resources for a particular X-client? The man pages for a client don't always have the information [I realize that "geometry" is part of the x-toolkit]. Specifically, how did you determine that the [I don't know the correct term] under Xman was "manualBrowser"? Thanks Joe Riel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Setting default width of xman
Just a followup: The width of the separate xman help page can also be set by Xman*help.geometry: 800x900 Joe Riel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Drawing graphs for use in Latex
11/20/02 9:00:37 AM, Mark Copper <[EMAIL PROTECTED]> wrote: >On Wed, 20 Nov 2002, Jens Kubieziel wrote: >> I'm looking for a tool where I can draw mathematical graphs like >> y=3x^4+5x^3+9x^2+2 and save them so that I can use it in Latex. Which >> packæges provide those functionality? You can use metapost (with the graph macro package). The learning curve is a bit steep, and it can be frustrating, at times, to debug; however, it provides excellent control of the appearance of the graph and labeling (fonts will match the text, you can use all the typesetting of TeX inside it). I've been using it for all my technical graphing. Joe Riel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Accessing the HOWTO documents
How are the HOWTO documents, distributed with Linux, intended to be read, that is, with what application? Joe Riel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Determining what packages are installed
How do I determine what packages are installed? Or determine whether a particular package is installed? I can use deselect to check a particular package, but there probably is a better way. Thanks, Joe Riel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Alt vs Meta key in Emacs
I use a pc104 keyboard, the bottom row looks like the following: Using xmodmap I swapped the key with the . In emacs (under X), acts like a key, doesn't do anything (using xev it shows up as "multi-key") and do nothing (they act as modifier keys, but that does nothing in emacs). behaves as . How do I change these keys? I tried using keysym in xmodmap, but my first attempt did not work with emacs. A search of the emacs info pages, web, and Debian HOWTOs wasn't a lot of help. I currently would like to have the and keys act as keys in emacs (in the long run it might be better to have the window keys become keys and the keys be a new modifier, however, I'm switching from NTEmacs where is and that's what my fingers want to type.) Thanks for any pointers, Joe Riel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alt vs Meta key in Emacs
Thanks to Charlie and Vincent for their responses, I got my keyboard properly configured. I did, however, do so in a slightly different manner. The usual method fo swapping Caps Lock and Control keys does just that, it swaps the keys; so, if you run xmodmap on the file twice they are back to how they started. That seems silly to me (though it hasn't been an issue except during testing) so I rewrote the .Xmodmap file so that it doesn't do that. Following what I currently have Joe Riel ! The commands in this file (.Xmodmap) are executed by ! ! xmodmap .Xmodmap ! ! This should be automatically executed when ! /etc/X11/Xsession.d/40custom_load-xmodmap ! is sourced by /etc/X11/Xsession. ! ! Swap Caps_Lock and Control_L (the left control key) ! ! remove Lock = Caps_Lock ! remove Control = Control_L ! keysym Control_L = Caps_Lock ! keysym Caps_Lock = Control_L ! add Lock = Caps_Lock ! add Control = Control_L ! ! Rather than swap the Caps_Lock and Control keys, assign them directly. ! This prevents successive merges from swapping the keys back. ! Also, change the Alt keys to Meta keys ! and the Window keys to Alt keys. ! It may be better to have the Window keys as Meta keys, ! however, I'm stuck with that layout on NTemacs. clear Lock clear Control clear mod1 clear mod4 keycode 66 = Control_L keycode 37 = Caps_Lock keycode 115 = Alt_L keycode 64 = Meta_L keycode 113 = Meta_R keycode 116 = Alt_R keycode 109 = Control_R add Lock = Caps_Lock add Control = Control_L Control_R add mod1 = Meta_L Meta_R add mod4 = Alt_L Alt_R -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: clearing the screen -> framebuffer insanity
Just wondering, what is a framebuffer console? And how would I know whether I was using one? Joe Riel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Using Java Console with FireFox 3 and Java 1.5
Is there a way to enable the Java Console in FireFox (iceweasel) 3.0 with Java 1.5? Previously I was able to use the Open Java Console add-on (the "regular" Java Console did not work with versions of Firefox greater than 2.0. I know almost nothing about java, but occasionally need to look at the console to debug problems when java doesn't work. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Disabling gpe18 at reboot
Following an upgrade to Wheezy, my Lenovo Y560p laptop showed 80% cpu usage on one core. This was due to constant interrupts on gpe18, see, udoremember.blogspot.com. I can stop this by executing sudo echo disable > /sys/firmware/acpi/interrupts/gpe18 I'd like to have that executed at reboot. To do so, I added the following cron file: # /etc/cron.d/30-disable-gpe18 @reboot root echo disable > /sys/firmware/acpi/interrupts/gpe18 Alas, that does not work. I've verified that the line is executed, however, the interrupt is not disabled. Any ideas why that would be the case? -- Joe Riel -- 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/87a9o0jke2@san.rr.com
Re: Disabling gpe18 at reboot
David Guntner writes: > Joe Riel grabbed a keyboard and wrote: >> Following an upgrade to Wheezy, my Lenovo Y560p laptop >> showed 80% cpu usage on one core. This was due to >> constant interrupts on gpe18, see, udoremember.blogspot.com. >> >> I can stop this by executing >> >> sudo echo disable > /sys/firmware/acpi/interrupts/gpe18 >> >> I'd like to have that executed at reboot. To do so, >> I added the following cron file: >> >> # /etc/cron.d/30-disable-gpe18 >> @reboot root echo disable > /sys/firmware/acpi/interrupts/gpe18 >> >> Alas, that does not work. I've verified that the line is executed, >> however, the interrupt is not disabled. Any ideas why that would >> be the case? > > Possibly a timing issue? Maybe the disable command you're running takes > effect *before* it's actually active, so it ends up running anyway? > (I.E., it goes active after you've tried to disable it.) > > Try moving the command to /etc/rc.local (which runs after all the other > init stuff has completed), and see if that helps. The things in > rc.local run as root as part of the startup, so you won't need the sudo. Thanks for the suggestion, alas, it isn't helping. I removed the cron file and added a line to rc.local to call the following script: #!/bin/bash INTERRUPT=/sys/firmware/acpi/interrupts/gpe18 LOG=/home/joe/disable-gpe18.log ( cat $INTERRUPT > $LOG echo clear > $INTERRUPT echo disable > $INTERRUPT cat $INTERRUPT >> $LOG ) 2>> $LOG After rebooting, I verified that the LOG file is written. It contains 1556129 enabled 1556180 enabled The second line should end with "disabled". If I manually execute the script with sudo, the log file contains 38085949 enabled 38085966 disabled -- Joe Riel. -- 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/8761yojao5@san.rr.com
Re: Gain owner of a file using vim :w!
Beco writes: > Dear users, > > I'm astonished by this (maybe I'm naive and I'm missing something). > > Yesterday as root I saved a file skel.bashrc in my /home/beco user, owned by > root, group root. > > Today I edited it, logged as beco, and vi told me "warning, read only!". I > edited anyway, just to test, and saved with :w! > > After that I checked the file and it has changed to owner beco, group beco. > > How is that possible? You have write permission to the directory, so you can delete the file and create a new one, with yourself as the owner. That is, essentially, what vi is doing. -- Joe Riel -- 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/87bo82czos@san.rr.com
Reinstall nouveau driver
After upgrading to Wheezy, I attempted to install an nvidia driver. It didn't work (X didn't come up). I managed to revert to using the nouveau driver, by removing /etc/X11/xorg.conf, which mostly works. However, I'm having an issue rendering some 3D stuff that used to work before the upgrade (I'm pretty sure I was using the nouveau driver with Squeeze). Do I need to reinstall/reconfigure the nouveau driver? What is the proper way to do so? Thanks -- Joe Riel -- 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/87zjvbvwyn@san.rr.com
Re: Reinstall nouveau driver
Sven Joachim writes: > On 2013-05-31 20:13 +0200, Joe Riel wrote: > >> After upgrading to Wheezy, I attempted to install an nvidia driver. It >> didn't work (X didn't come up). > > Using the Nvidia installer is not recommended, better use the packages > in non-free. > >> I managed to revert to using the >> nouveau driver, by removing /etc/X11/xorg.conf, which mostly works. >> However, I'm having an issue rendering some 3D stuff that used to work >> before the upgrade (I'm pretty sure I was using the nouveau driver with >> Squeeze). > > The nouveau driver in Squeeze does not provide 3D acceleration, so that > kind of stuff only works to a limited amount (by using the swrast > software renderer). > >> Do I need to reinstall/reconfigure the nouveau driver? What >> is the proper way to do so? > > Reinstall the xserver-xorg-core and libgl1-mesa-glx packages, those > contain files which are overwritten by the Nvidia installer. I tried that, didn't help. Well, I tried dpkg-reconfigure; that didn't help. -- Joe Riel -- 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/87sj13aq0f@san.rr.com
Re: Reinstall nouveau driver
Alan Ianson writes: > On Fri, 31 May 2013 11:13:52 -0700 > Joe Riel wrote: > >> After upgrading to Wheezy, I attempted to install an nvidia driver. >> It didn't work (X didn't come up). I managed to revert to using the >> nouveau driver, by removing /etc/X11/xorg.conf, which mostly works. >> However, I'm having an issue rendering some 3D stuff that used to work >> before the upgrade (I'm pretty sure I was using the nouveau driver >> with Squeeze). Do I need to reinstall/reconfigure the nouveau >> driver? What is the proper way to do so? > > Did you use nvidia-xconfig to create your xorg.conf? The debian > packaged nvidia driver works well for me. When I first upgraded to Wheezy, I believe that is what I did (used nvidia-xconfig to create xorg.conf) and was unable to start X. This time, after installing an nvidia driver using sudo aptitude -s install nvidia-kernel-dkms install linux-headers-amd64 I manually created /etc/xorg.conf.d using the directions at http://wiki.debian.org/NvidiaGraphicsDrivers. All went well. After a reboot, X started, the 3D stuff is working, scrolling in chrome is a lot faster. Fonts have changed slightly, it seems. I wouldn't say for the better but I'll adapt soon enough. Only thing I've noticed that is obviously worse is that the virtual terminal font is now big and ugly. I recall that the same occured when I previously tried an nvidia driver in Squeeze. -- Joe Riel -- 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/87obbqc43u@san.rr.com
Re: Reinstall nouveau driver
Alan Ianson writes: > On Fri, 31 May 2013 12:59:49 -0700 > Joe Riel wrote: > >> Alan Ianson writes: >> >> > On Fri, 31 May 2013 11:13:52 -0700 >> > Joe Riel wrote: >> > >> >> After upgrading to Wheezy, I attempted to install an nvidia driver. >> >> It didn't work (X didn't come up). I managed to revert to using >> >> the nouveau driver, by removing /etc/X11/xorg.conf, which mostly >> >> works. However, I'm having an issue rendering some 3D stuff that >> >> used to work before the upgrade (I'm pretty sure I was using the >> >> nouveau driver with Squeeze). Do I need to reinstall/reconfigure >> >> the nouveau driver? What is the proper way to do so? >> > >> > Did you use nvidia-xconfig to create your xorg.conf? The debian >> > packaged nvidia driver works well for me. >> >> When I first upgraded to Wheezy, I believe that is what I did (used >> nvidia-xconfig to create xorg.conf) and was unable to start X. This >> time, after installing an nvidia driver using >> >> sudo aptitude -s install nvidia-kernel-dkms install >> linux-headers-amd64 >> >> I manually created /etc/xorg.conf.d using the directions at >> http://wiki.debian.org/NvidiaGraphicsDrivers. >> >> All went well. After a reboot, X started, the 3D stuff is working, >> scrolling in chrome is a lot faster. Fonts have changed slightly, it >> seems. I wouldn't say for the better but I'll adapt soon enough. > > My desktop looks like it always has. Maybe you can adjust the > anti-aliasing or hinting of fonts on your desktop. > >> Only thing I've noticed that is obviously worse is that the virtual >> terminal font is now big and ugly. I recall that the same occured >> when I previously tried an nvidia driver in Squeeze. > > When using the nvidia driver I have always used vga=794 on my kernel > command line and I get good response time. I have tried the new > "gfxmode=" way of doing it but I find I have slow a terminal then. I do > need to experiment more with that though. My /etc/default/grub file contained GRUB_CMDLINE_LINUX_DEFAULT="quiet vga=775" should I remove the vga=775 when adding GRUB_GFXMODE=1280x1024 GRUB_GFXPAYLOAD_LINUX=keep I used dbeinfo when inside grub, after a reboot, to query the available resolutions. The highest I have, apparently, is 1280x1024. Is there a way to change the setting when inside grub, so that it immediately takes place (at least while in grub)? With the large font, the output of commands invariably scrolls off the screen. I tried set pager=1 that didn't do anything. > I also run "dpkg-reconfigure console-setup" and choose the "vga" font > which is what the kernel used to use by default IINM. I'm not sure why > the default font was changed but i think it supports more languages now > so the vga font may not work for everyone. How can I query what console font is in effect? -- Joe Riel -- 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/871u8l52m7@san.rr.com
installed console keymap not used following reboot
I have a TrulyErgonomic keyboard and move some of the keys around. To do this in the virtual terminals, I use loadkeys. I also use install-keymap, which creates /etc/console/boottime.kmap.gz. That keymap is supposed to be loaded following a reboot. It is not. Either that or the created file does not correspond to the keymap I generate; however, doing # install-keymap my-keymap activates the custom keymap and creates the previously mentioned file, so it is likely correct. Any idea why the keymap at /etc/console/boottime.kmap.gz is not being loaded? -- Joe Riel -- 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/878v2twdhq@san.rr.com
Re: installed console keymap not used following reboot
Joe Riel writes: > I have a TrulyErgonomic keyboard and move some of the keys around. To > do this in the virtual terminals, I use loadkeys. I also use > install-keymap, which creates /etc/console/boottime.kmap.gz. That > keymap is supposed to be loaded following a reboot. It is not. Either > that or the created file does not correspond to the keymap I generate; > however, doing > > # install-keymap my-keymap > > activates the custom keymap and creates the previously mentioned file, > so it is likely correct. > > Any idea why the keymap at /etc/console/boottime.kmap.gz is not > being loaded? With a bit of digging I resolved this. Because setupcon is installed, /etc/init.d/keymap.sh aborts. To handle this, I modified /etc/default/keyboard so that # KMAP=/etc/console-setup/defkeymap.kmap.gz is now KMAP=/etc/console-setup/truly-ergonomic.kmap.gz I could have made this KMAP=/etc/console/boottime.kmap.gz where that file was created by install-keymap, but it seemed better to rename it and move it to /etc/console-setup. -- Joe Riel -- 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/87r4glnu41@san.rr.com
Monitor network download speed
Any recommendations for a graphical tool to monitor, real-time, the download network speed. My connection to work frequently gets really slow, in which case I need to disconnect and reconnect. I currently use the gnome network monitor tool, however, its display of Network History connection speed is buggy. Right now, the vertical axis labels are: 00.0 KiB/s 20.0 KiB/s 40.0 KiB/s 60.0 KiB/s 80.0 KiB/s 00.0 KiB/s The fastest is supposed to be on the top, but what speed is it? I have no idea. This happens all the time. Other times I see all labels being 0.00 KiB/s. Even when the labeling is correct, the scaling is usually bad, so the entire graph extends to all 1/5 the height. There must be a better application. -- Joe Riel -- 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/87mwphi5n2@san.rr.com
Re: Squeeze freezes
That happened to me. A google search revealed the problem was common to other users of the motherboard I have (Asus P7PP5D) and the kernel (2.6.32). The fix was to use a USB keyboard and USB mouse. That has completely eliminated the lockups. Just changing to a USB mouse reduced the freeze rate to about once a day. I was able to ssh into the machine from another machine during lockups. This might have nothing to do with your problem, but trying a USB mouse is an easy test (it should work even during the lockup). On Tue, 8 Mar 2011 21:10:09 -0600 Aquiles Carattino wrote: > I have just upgraded from Lenny to Squeeze but when surfing internet > (both with Icewasel or Google Chromium) in some sites (like gmail, > for instance) the PC completely freezes (no way of going to console, > rebooting, etc.) I have to turn off the power. > I have no idea what may be causing this... > > Aquiles Carattino > e-mal / MSN:aqui.caratt...@gmail.com > Blog:http://www.aquic.com.ar -- Joe Riel -- 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/20110309133020.67f3d822@gauss
aptitude stuck "resolving dependencies..."
This morning I ran $ sudo aptitude update $ aptitude --simulate safe-upgrade Resolving dependencies... open: 16431; closed: 11272; defer: 105; conflict: 54 At this point it kept churning; the number of open dependencies kept increasing. Because of this I haven't run a real upgrade. How do I determine what is happening and whether a real upgrade would run normally? -- Joe Riel -- 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/20110319100447.15610d97@gauss
Re: aptitude stuck "resolving dependencies..."
On Sat, 19 Mar 2011 10:04:47 -0700 Joe Riel wrote: > This morning I ran > > $ sudo aptitude update > $ aptitude --simulate safe-upgrade > Resolving dependencies... > open: 16431; closed: 11272; defer: 105; conflict: 54 > > At this point it kept churning; the number of open dependencies kept > increasing. Because of this I haven't run a real upgrade. > How do I determine what is happening and whether a real upgrade > would run normally? > Found a similar question a bit earlier than mine. The resolution is to do full-upgrade. Sorry for the bother... -- Joe Riel -- 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/20110319101803.62c75b9c@gauss
libXm.so.3
Any idea where I can get a 64 bit version of libXm.so.3? My understanding is that it is part of libmotif3, but that isn't part of Debian. -- Joe Riel -- 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/20110324145843.102c394b@gauss
Reverting to an old version of libstdc++6
This weekend I upgraded, and libstdc++6 went from 4.5.2-4 -> 4.6.0-2. This has broken a commercial package I use; I now get symbol lookup error: /usr/lib/libstdc++.so.6: undefined symbol: _ZNSt14error_categoryD2Ev, version GLIBCXX_3.4.15 I have a few simple questions. (1) how do I determine what version of libstdc++6 that the previous debian version of that package was using? That, is, the current package provides the file /usr/lib/libstdc++.so.6.0.15 and a link /usr/lib/libstdc++.so.6 -> libstdc++.so.6.0.15. I assume the previous debian version did the same, but with some other file, maybe libstdc++.so.6.0.14? How do I find out what that file was? (2) How do I locate and install the previous version from a debian repository? -- Joe Riel -- 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/20110419082938.318ae0ac@gauss
Re: Reverting to an old version of libstdc++6
On Tue, 19 Apr 2011 19:07:01 +0200 Johan Grönqvist wrote: > 2011-04-19 17:29, Joe Riel skrev: > > This weekend I upgraded, and libstdc++6 went from > > 4.5.2-4 -> 4.6.0-2. > > > (1) how do I determine what version of libstdc++6 > > that the previous debian version of that package was using? > > That, is, the current package provides the file > > /usr/lib/libstdc++.so.6.0.15 and a link > > /usr/lib/libstdc++.so.6 -> libstdc++.so.6.0.15. > > I assume the previous debian version did the same, > > but with some other file, maybe libstdc++.so.6.0.14? > > How do I find out what that file was? > > > > I went to snapshot.debian.org, searched for the binary package > libstd++6, and grabbed the .deb file for version 4.5.2-4 on amd64. I > opened that deb-file (with the decompression program in gnome) and it > contained /usr/lib/libstdc++.so.6 and /usr/lib/libstdc++.so.6.0.14, > as you expected. > > > (2) How do I locate and install > > the previous version from a debian repository? > > > > Download the .deb from snapshots.debian.org and install. The normal > warnings and disclaimers when downgrading library packages all apply. > > <http://snapshot.debian.org/package/gcc-4.5/4.5.2-4/#libstdc:2b::2b:6_4.5.2-4> > Thank you, that fixes the immediate problem. -- Joe Riel -- 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/20110419103648.74b4725f@gauss
Keyboard freezing/repeating endlessly
First post to Debian-Users; I hope this isn't inappropriate. In December I upgraded Ubuntu 9.04 to 10.04. The keyboard and mouse would then freeze after about five minutes of use. At that point I installed Debian 6 (another machine uses Debian, but this computer had come with Ubuntu 9.04 installed, so I used that for a year with no problems). Alas, the same thing happened with Debian 6. I have a PS/2 mouse and keyboard. I noticed that an added USB mouse would continue to operate, so replaced the mouse with that. The keyboard lockup continued, but decreased in frequency to about one a day. That is still unacceptable, but temporarily manageable. There are no indications of anything wrong in any of the logs. The O/S is fully functional; I can log into it from another machine and restart it that way. When the lockup occurs, most of the time the keyboard continually repeats a key, but not always the same key. I've seen the escape key, the "l", the "k", and others. Pressing the same key (to get the driver to see the "release" does not stop it). Other times it appears as though no key is repeating (at least nothing happens when the mouse is placed in a client). I've searched google and found quite a few descriptions of what appears similar behavior, with no solutions. Any suggestions on what I can do? Replace the PS/2 keyboard with a USB? Something I recently noticed is that $ setxkbmap -print indicates that X thinks I'm using a pc105 keyboard when in fact I have a pc104. I changed that, from the command line, with $ setxkbmap -model pc104 That didn't improve anything (I still get lockups) nor did it change the keyboard operation, as far as I can tell. However, I'm wondering why X is using the wrong keyboard model. Maybe I entered the wrong model during the installation. What sets the default value (there is no xorg.conf file)? Thanks for any suggestions. -- Joe Riel -- 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/20110113090116.1f56f8de@gauss
Re: Keyboard freezing/repeating endlessly
A few details I omitted. Once the freeze occurs, the only way I've found to release it is to restart the machine. Restarting gdm3 (via a remote computer) does not help, it brings up the login screen, but the keyboard is not operational. The problem also occurs in a virtual terminal (though I've never been in a virtual terminal when it started). To get to a virtual terminal with the keyboard dead/repeating, I added a menu entry, accessible via the mouse, that calls chvt, and modified the sudoers permission to allow me to run that. In the virtual terminal I don't see the key repeating, but the keyboard does nothing. I normally run fvwm, but the problem also occurs in Gnome. If there isn't a fix, are there any ideas on how to at least clear the fault once it occurs (without restarting the machine)? As mentioned, typing the key that is repeating does not help. On Thu, 13 Jan 2011 09:01:16 -0800 Joe Riel wrote: > First post to Debian-Users; I hope this isn't inappropriate. > > In December I upgraded Ubuntu 9.04 to 10.04. The keyboard and mouse > would then freeze after about five minutes of use. At that point I > installed Debian 6 (another machine uses Debian, but this computer had > come with Ubuntu 9.04 installed, so I used that for a year with no > problems). Alas, the same thing happened with Debian 6. > > I have a PS/2 mouse and keyboard. I noticed that an added USB mouse > would continue to operate, so replaced the mouse with that. The > keyboard lockup continued, but decreased in frequency to about one a > day. That is still unacceptable, but temporarily manageable. > > There are no indications of anything wrong in any of the logs. > The O/S is fully functional; I can log into it from another machine > and restart it that way. > > When the lockup occurs, most of the time the keyboard continually > repeats a key, but not always the same key. I've seen the escape key, > the "l", the "k", and others. Pressing the same key (to get the > driver to see the "release" does not stop it). Other times it > appears as though no key is repeating (at least nothing happens when > the mouse is placed in a client). > > I've searched google and found quite a few descriptions of what > appears similar behavior, with no solutions. > > Any suggestions on what I can do? Replace the PS/2 keyboard with a > USB? > > Something I recently noticed is that > > $ setxkbmap -print > > indicates that X thinks I'm using a pc105 keyboard when in fact I have > a pc104. I changed that, from the command line, with > > $ setxkbmap -model pc104 > > That didn't improve anything (I still get lockups) nor did it change > the keyboard operation, as far as I can tell. However, I'm wondering > why X is using the wrong keyboard model. Maybe I entered the wrong > model during the installation. What sets the default value (there is > no xorg.conf file)? > > Thanks for any suggestions. -- Joe Riel -- 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/20110113092102.517a552f@gauss
Re: Keyboard freezing/repeating endlessly
> Are you sure the keyboard is good? No, but it would be quite the coincidence that the keyboard works fine for a year and fails within five minutes of installing a new O/S. However, to remove that possibility, I just now replaced it with another PS/2 keyboard. I'll respond when this locks up (though this old keyboard is a pain to type on). A useful suggestion, thanks. -- Joe Riel -- 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/20110113092740.0c8f0698@gauss
Re: Keyboard freezing/repeating endlessly
On Thu, 13 Jan 2011 17:44:38 + (UTC) Camaleón wrote: > > I'm wondering why X is using the wrong keyboard model. Maybe I > > entered the wrong model during the installation. What sets the > > default value (there is no xorg.conf file)? > > Keyboard setup is done in "/etc/default/keyboard" file. Thanks, fixed that. It was set to pc105, so presumably I screwed up when installing Debian. > OTOH, are you sure there is no information/warning about the lock in > "/ var/log/Xorg.0.log"? I'm not sure . Nothing jumped out at me, but I'm clueless. There is this: (II) AIGLX error: dlopen of /usr/lib/dri/nouveau_dri.so failed (/usr/lib/dri/nouveau_dri.so: cannot open shared object file: No such file or directory) Google search indicates that this isn't an issue (as does the II). Attached is the entire Xorg.0.log.old. > Have you tried with another PS/2 keyboard? :-? Am currently using another PS/2 keyboard; it hasn't locked up yet, but I've only used it for an hour and the frequency is about once a day (but 3 times yesterday). Does the fact that, when the PS/2 mouse is installed, it also locks up when the event occurs, mean anything? A USB mouse continues to work. -- Joe Riel Xorg.0.log.old Description: application/trash
Re: Keyboard freezing/repeating endlessly
On Thu, 13 Jan 2011 09:27:40 -0800 Joe Riel wrote: > > Are you sure the keyboard is good? > > No, but it would be quite the coincidence that the > keyboard works fine for a year and fails within > five minutes of installing a new O/S. However, > to remove that possibility, I just now replaced > it with another PS/2 keyboard. I'll respond > when this locks up (though this old keyboard is > a pain to type on). It just locked up with the old [different] PS/2 keyboard. I suppose the next thing to do is to try a USB keyboard, to avoid the PS/2 port/driver. I'll see if I can borrow one. -- Joe Riel -- 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/20110113112056.03a1b882@gauss
Re: Keyboard freezing/repeating endlessly
On Thu, 13 Jan 2011 19:17:32 + (UTC) Camaleón wrote: > On Thu, 13 Jan 2011 10:21:03 -0800, Joe Riel wrote: > > > On Thu, 13 Jan 2011 17:44:38 + (UTC) Camaleón wrote: > > >> OTOH, are you sure there is no information/warning about the lock > >> in "/ var/log/Xorg.0.log"? > > > > I'm not sure . Nothing jumped out at me, but I'm clueless. There is > > this: > > > > (II) AIGLX error: dlopen of /usr/lib/dri/nouveau_dri.so failed > > (/usr/lib/dri/nouveau_dri.so: cannot open shared object file: No > > such file or directory) > > > > Google search indicates that this isn't an issue (as does the II). > > Attached is the entire Xorg.0.log.old. > > Thanks... yup, I see something suspicious (or maybe not) at the end > of the file: > > *** > (II) Power Button: Device reopened after 1 attempts. > (II) Power Button: Device reopened after 1 attempts. > (II) UVC Camera (046d:09a1): Device reopened after 1 attempts. > (II) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): Device > reopened after 1 attempts. (II) AT Translated Set 2 keyboard: Device > reopened after 1 attempts. (II) Macintosh mouse button emulation: > Device reopened after 1 attempts. > > (II) Macintosh mouse button emulation: Close > (II) UnloadModule: "evdev" > (II) AT Translated Set 2 keyboard: Close > (II) UnloadModule: "evdev" > (II) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): Close > > (II) UnloadModule: "evdev" > (II) UVC Camera (046d:09a1): Close > (II) UnloadModule: "evdev" > (II) Power Button: Close > (II) UnloadModule: "evdev" > (II) Power Button: Close > (II) UnloadModule: "evdev" > *** > > "evdev" module is unloaded for no apparent reason but not sure if > this a normal/common log. To check this, I just restarted the machine and compared the Xorg.0.log.old file created with the one following a lockup (and subsequent restart). The unloading of evdev appears normal, however, what is not in the "normal" restart log are the lines > (II) Power Button: Device reopened after 1 attempts. ... > Device reopened after 1 attempts. Any idea what that might indicate? > >> Have you tried with another PS/2 keyboard? :-? > > > > Am currently using another PS/2 keyboard; it hasn't locked up yet, > > but I've only used it for an hour and the frequency is about once a > > day (but 3 times yesterday). As reported in a separate response, the replacement keyboard, also PS/2, locked up. -- Joe Riel -- 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/20110113114130.002b2ef8@gauss
Re: Keyboard freezing/repeating endlessly
On Thu, 13 Jan 2011 11:41:30 -0800 Joe Riel wrote: > On Thu, 13 Jan 2011 19:17:32 + (UTC) > Camaleón wrote: > > > On Thu, 13 Jan 2011 10:21:03 -0800, Joe Riel wrote: > > > > > On Thu, 13 Jan 2011 17:44:38 + (UTC) Camaleón wrote: > > > > >> OTOH, are you sure there is no information/warning about the lock > > >> in "/ var/log/Xorg.0.log"? > > > > > > I'm not sure . Nothing jumped out at me, but I'm clueless. There > > > is this: > > > > > > (II) AIGLX error: dlopen of /usr/lib/dri/nouveau_dri.so failed > > > (/usr/lib/dri/nouveau_dri.so: cannot open shared object file: No > > > such file or directory) > > > > > > Google search indicates that this isn't an issue (as does the II). > > > Attached is the entire Xorg.0.log.old. > > > > Thanks... yup, I see something suspicious (or maybe not) at the end > > of the file: > > > > *** > > (II) Power Button: Device reopened after 1 attempts. > > (II) Power Button: Device reopened after 1 attempts. > > (II) UVC Camera (046d:09a1): Device reopened after 1 attempts. > > (II) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): Device > > reopened after 1 attempts. (II) AT Translated Set 2 keyboard: Device > > reopened after 1 attempts. (II) Macintosh mouse button emulation: > > Device reopened after 1 attempts. > > > > (II) Macintosh mouse button emulation: Close > > (II) UnloadModule: "evdev" > > (II) AT Translated Set 2 keyboard: Close > > (II) UnloadModule: "evdev" > > (II) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): Close > > > > (II) UnloadModule: "evdev" > > (II) UVC Camera (046d:09a1): Close > > (II) UnloadModule: "evdev" > > (II) Power Button: Close > > (II) UnloadModule: "evdev" > > (II) Power Button: Close > > (II) UnloadModule: "evdev" > > *** > > > > "evdev" module is unloaded for no apparent reason but not sure if > > this a normal/common log. > > To check this, I just restarted the machine and compared the > Xorg.0.log.old file created with the one following a lockup > (and subsequent restart). The unloading of evdev appears normal, > however, what is not in the "normal" restart log are the lines > > > (II) Power Button: Device reopened after 1 attempts. > ... > > Device reopened after 1 attempts. > > Any idea what that might indicate? Those messages appear benign. That is the result of switching to a virtual terminal and then back to X. That action does not trigger the keyboard lockup. -- Joe Riel -- 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/20110113131000.6a8be1f7@gauss
Re: Keyboard freezing/repeating endlessly
On Thu, 13 Jan 2011 15:00:01 -0600 Hugo Vanwoerkom wrote: > Joe Riel wrote: > > On Thu, 13 Jan 2011 19:17:32 + (UTC) > > Camaleón wrote: > > > >> On Thu, 13 Jan 2011 10:21:03 -0800, Joe Riel wrote: > >> > >>> On Thu, 13 Jan 2011 17:44:38 + (UTC) Camaleón wrote: > >>>> OTOH, are you sure there is no information/warning about the lock > >>>> in "/ var/log/Xorg.0.log"? > >>> I'm not sure . Nothing jumped out at me, but I'm clueless. There > >>> is this: > >>> > >>> (II) AIGLX error: dlopen of /usr/lib/dri/nouveau_dri.so failed > >>> (/usr/lib/dri/nouveau_dri.so: cannot open shared object file: No > >>> such file or directory) > >>> > >>> Google search indicates that this isn't an issue (as does the II). > >>> Attached is the entire Xorg.0.log.old. > >> Thanks... yup, I see something suspicious (or maybe not) at the end > >> of the file: > >> > >> *** > >> (II) Power Button: Device reopened after 1 attempts. > >> (II) Power Button: Device reopened after 1 attempts. > >> (II) UVC Camera (046d:09a1): Device reopened after 1 attempts. > >> (II) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): Device > >> reopened after 1 attempts. (II) AT Translated Set 2 keyboard: > >> Device reopened after 1 attempts. (II) Macintosh mouse button > >> emulation: Device reopened after 1 attempts. > >> > >> (II) Macintosh mouse button emulation: Close > >> (II) UnloadModule: "evdev" > >> (II) AT Translated Set 2 keyboard: Close > >> (II) UnloadModule: "evdev" > >> (II) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): Close > >> > >> (II) UnloadModule: "evdev" > >> (II) UVC Camera (046d:09a1): Close > >> (II) UnloadModule: "evdev" > >> (II) Power Button: Close > >> (II) UnloadModule: "evdev" > >> (II) Power Button: Close > >> (II) UnloadModule: "evdev" > >> *** > >> > >> "evdev" module is unloaded for no apparent reason but not sure if > >> this a normal/common log. > > > > To check this, I just restarted the machine and compared the > > Xorg.0.log.old file created with the one following a lockup > > (and subsequent restart). The unloading of evdev appears normal, > > however, what is not in the "normal" restart log are the lines > > > >> (II) Power Button: Device reopened after 1 attempts. > > ... > >> Device reopened after 1 attempts. > > > > Any idea what that might indicate? > > > > Got that too: > > /var/logThu Jan 13-14:57:09# grep Power Xorg.0.log > (II) config/udev: Adding input device Power Button (/dev/input/event2) > (**) Power Button: Applying InputClass "evdev keyboard catchall" > (**) Power Button: always reports core events > (**) Power Button: Device: "/dev/input/event2" > (II) Power Button: Found keys > (II) Power Button: Configuring as keyboard > (II) XINPUT: Adding extended input device "Power Button" (type: > KEYBOARD) (II) config/udev: Adding input device Power Button > (/dev/input/event1) (**) Power Button: Applying InputClass "evdev > keyboard catchall" (**) Power Button: always reports core events > (**) Power Button: Device: "/dev/input/event1" > (II) Power Button: Found keys > (II) Power Button: Configuring as keyboard > (II) XINPUT: Adding extended input device "Power Button" (type: > KEYBOARD) (II) Power Button: Device reopened after 1 attempts. > (II) Power Button: Device reopened after 1 attempts. > (II) Power Button: Device reopened after 1 attempts. > (II) Power Button: Device reopened after 1 attempts. > (II) Power Button: Device reopened after 1 attempts. > (II) Power Button: Device reopened after 1 attempts. > (II) Power Button: Device reopened after 1 attempts. > (II) Power Button: Device reopened after 1 attempts. > (II) Power Button: Device reopened after 1 attempts. > (II) Power Button: Device reopened after 1 attempts. > (II) Power Button: Device reopened after 1 attempts. > (II) Power Button: Device reopened after 1 attempts. > (II) Power Button: Device reopened after 1 attempts. > (II) Power Button: Device reopened after 1 attempts. > /var/logThu Jan 13-14:57:22# > > ... > > Power Button configuring as keyboard? That does look suspicious. Thanks for pointing it out. At the very least, if normal, it is extremely cryptic. That information notice appears in all my Xorg.0.log files. Maybe I have to toggle the power button to clear the repeating key 8-) -- Joe Riel -- 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/20110113131505.7c76e5d8@gauss
Re: Keyboard freezing/repeating endlessly
On Thu, 13 Jan 2011 15:23:09 -0600 Hugo Vanwoerkom wrote: > Joe Riel wrote: > > On Thu, 13 Jan 2011 11:41:30 -0800 > > Joe Riel wrote: > > > >> On Thu, 13 Jan 2011 19:17:32 + (UTC) > >> Camaleón wrote: > >> > >>> On Thu, 13 Jan 2011 10:21:03 -0800, Joe Riel wrote: > >>> > >>>> On Thu, 13 Jan 2011 17:44:38 + (UTC) Camaleón wrote: > >>>>> OTOH, are you sure there is no information/warning about the > >>>>> lock in "/ var/log/Xorg.0.log"? > >>>> I'm not sure . Nothing jumped out at me, but I'm clueless. There > >>>> is this: > >>>> > >>>> (II) AIGLX error: dlopen of /usr/lib/dri/nouveau_dri.so failed > >>>> (/usr/lib/dri/nouveau_dri.so: cannot open shared object file: No > >>>> such file or directory) > >>>> > >>>> Google search indicates that this isn't an issue (as does the > >>>> II). Attached is the entire Xorg.0.log.old. > >>> Thanks... yup, I see something suspicious (or maybe not) at the > >>> end of the file: > >>> > >>> *** > >>> (II) Power Button: Device reopened after 1 attempts. > >>> (II) Power Button: Device reopened after 1 attempts. > >>> (II) UVC Camera (046d:09a1): Device reopened after 1 attempts. > >>> (II) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): > >>> Device reopened after 1 attempts. (II) AT Translated Set 2 > >>> keyboard: Device reopened after 1 attempts. (II) Macintosh mouse > >>> button emulation: Device reopened after 1 attempts. > >>> > >>> (II) Macintosh mouse button emulation: Close > >>> (II) UnloadModule: "evdev" > >>> (II) AT Translated Set 2 keyboard: Close > >>> (II) UnloadModule: "evdev" > >>> (II) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): Close > >>> > >>> (II) UnloadModule: "evdev" > >>> (II) UVC Camera (046d:09a1): Close > >>> (II) UnloadModule: "evdev" > >>> (II) Power Button: Close > >>> (II) UnloadModule: "evdev" > >>> (II) Power Button: Close > >>> (II) UnloadModule: "evdev" > >>> *** > >>> > >>> "evdev" module is unloaded for no apparent reason but not sure if > >>> this a normal/common log. > >> To check this, I just restarted the machine and compared the > >> Xorg.0.log.old file created with the one following a lockup > >> (and subsequent restart). The unloading of evdev appears normal, > >> however, what is not in the "normal" restart log are the lines > >> > >>> (II) Power Button: Device reopened after 1 attempts. > >> ... > >>> Device reopened after 1 attempts. > >> Any idea what that might indicate? > > > > Those messages appear benign. That is the result of switching to a > > virtual terminal and then back to X. That action does not trigger > > the keyboard lockup. > > > > Interesting. How did you figure that out? tail -f /var/log/Xorg.0.log then switched to VT1, then back to X (VT7). When I came back to X, I could see the log file being updated. My tentative conclusion is that that is normal behavior of X. Do you see anything similar? -- Joe Riel -- 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/20110113135603.5b91a2e0@gauss
Re: Keyboard freezing/repeating endlessly
On Fri, 14 Jan 2011 11:38:43 + (UTC)
Camaleón wrote:
> You can:
>
> 1/ Start the system with no xorg (console) and leave it so for
> sometine to check if the problem is still present (even with no x
> server).
I'll attempt to try this. Might be painful working in a
virtual terminal all the time. Kind of limits what I can
do. This is my work machine...
> 2/ Review you kernel log, just in case ("cat /var/log/kern.log | grep
> input").
>
> If this is something related to X server, as a workaround to avoid
> restarting the system when this occurs, you can restart gdm3 service
> ("/ etc/init.d/gdm3 restart").
A workaround (clear the fault without a reboot) would be quite
helpful. Alas, restarting gdm3 isn't it; I get the login prompt, but
the keyboard is still dead. This seems to indicate it isn't an X
issue, but I don't know enough.
--
Joe Riel
--
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/20110114074759.5c37659a@gauss
Re: Keyboard freezing/repeating endlessly
On Fri, 14 Jan 2011 07:47:59 -0800
Joe Riel wrote:
> On Fri, 14 Jan 2011 11:38:43 + (UTC)
> Camaleón wrote:
>
> > You can:
> >
> > 1/ Start the system with no xorg (console) and leave it so for
> > sometine to check if the problem is still present (even with no x
> > server).
>
> I'll attempt to try this. Might be painful working in a
> virtual terminal all the time. Kind of limits what I can
> do. This is my work machine...
Got lucky, sort of. I was just working in a virtual terminal
when the lockup occurred. That doesn't rule out X in that
X was running (I had just opened the terminal and was reading
a man page), however, it suggests the problem might not be
with X. That is consistent with the observation that restarting
gdm3 does not clear the fault.
>
> > 2/ Review you kernel log, just in case ("cat /var/log/kern.log |
> > grep input").
Found the following lines (more of same) in kern.log at the time
of the lockup. However, I don't see them for other lockups
(a lockup occurred while I was typing this email), so it could
be a red-herring:
Jan 15 09:20:58 gauss kernel: [164858.674186] [drm] nouveau :01:00.0:
nouveau_channel_free: freeing fifo 2
Jan 15 09:20:59 gauss kernel: [164859.749505] [drm] nouveau :01:00.0:
nouveau_channel_free: freeing fifo 1
Jan 15 09:20:59 gauss kernel: [164859.750491] [drm] nouveau :01:00.0:
PFIFO_CACHE_ERROR - Ch 1/5 Mthd 0x Data 0x8013
Jan 15 09:20:59 gauss kernel: [164859.750507] [drm] nouveau :01:00.0:
PGRAPH_ERROR - nSource: DATA_ERROR, nStatus: BAD_ARGUMENT
Jan 15 09:20:59 gauss kernel: [164859.750511] [drm] nouveau :01:00.0:
PGRAPH_ERROR - Ch 1/5 Class 0x008a Mthd 0x0300 Data 0x:0x
Jan 15 09:20:59 gauss kernel: [164859.750566] [drm] nouveau :01:00.0:
PFIFO_CACHE_ERROR - Ch 1/4 Mthd 0x Data 0x801a
Jan 15 09:20:59 gauss kernel: [164859.750580] [drm] nouveau :01:00.0:
PGRAPH_ERROR - nSource: ILLEGAL_MTHD, nStatus: BAD_ARGUMENT PROTECTION_FAULT
--
Joe Riel
--
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/20110115095554.5c9cbb44@gauss
Re: Keyboard freezing/repeating endlessly
On Sat, 15 Jan 2011 20:16:16 + (UTC)
Camaleón wrote:
> On Sat, 15 Jan 2011 09:55:54 -0800, Joe Riel wrote:
>
> > On Fri, 14 Jan 2011 07:47:59 -0800 Joe Riel wrote:
> >
> >> On Fri, 14 Jan 2011 11:38:43 + (UTC) Camaleón wrote:
> >>
> >> > You can:
> >> >
> >> > 1/ Start the system with no xorg (console) and leave it so for
> >> > sometine to check if the problem is still present (even with no x
> >> > server).
> >>
> >> I'll attempt to try this. Might be painful working in a virtual
> >> terminal all the time. Kind of limits what I can do. This is my
> >> work machine...
> >
> > Got lucky, sort of. I was just working in a virtual terminal when
> > the lockup occurred. That doesn't rule out X in that X was running
> > (I had just opened the terminal and was reading a man page),
> > however, it suggests the problem might not be with X. That is
> > consistent with the observation that restarting gdm3 does not clear
> > the fault.
>
> Hum... yes, then it can be something related to the kernel.
>
> >> > 2/ Review you kernel log, just in case ("cat /var/log/kern.log |
> >> > grep input").
> >
> > Found the following lines (more of same) in kern.log at the time of
> > the lockup. However, I don't see them for other lockups (a lockup
> > occurred while I was typing this email), so it could be a
> > red-herring:
> >
> > Jan 15 09:20:58 gauss kernel: [164858.674186] [drm] nouveau
> > :01:00.0: nouveau_channel_free: freeing fifo 2 Jan 15 09:20:59
> > gauss kernel: [164859.749505] [drm] nouveau :01:00.0:
> > nouveau_channel_free: freeing fifo 1 Jan 15 09:20:59 gauss kernel:
> > [164859.750491] [drm] nouveau :01:00.0: PFIFO_CACHE_ERROR - Ch
> > 1/5 Mthd 0x Data 0x8013 Jan 15 09:20:59 gauss kernel:
> > [164859.750507] [drm] nouveau :01:00.0: PGRAPH_ERROR - nSource:
> > DATA_ERROR, nStatus: BAD_ARGUMENT Jan 15 09:20:59 gauss kernel:
> > [164859.750511] [drm] nouveau :01:00.0: PGRAPH_ERROR - Ch 1/5
> > Class 0x008a Mthd 0x0300 Data 0x:0x Jan 15 09:20:59
> > gauss kernel: [164859.750566] [drm] nouveau :01:00.0:
> > PFIFO_CACHE_ERROR - Ch 1/4 Mthd 0x Data 0x801a Jan 15
> > 09:20:59 gauss kernel: [164859.750580] [drm] nouveau :01:00.0:
> > PGRAPH_ERROR - nSource: ILLEGAL_MTHD, nStatus: BAD_ARGUMENT
> > PROTECTION_FAULT
>
> If X server is not running, where are these logs entries coming from?
> (nouveau is the X driver for nvidia cards) >;-)
Well, the X server was running. I was originally in X and switched to
a virtual terminal. The lockup occurred while I was working in the
virtual terminal. I searched google for that error message and found
a few related bug reports in other forums. At least one user was
experiencing very similar behavior (keyboard goes away).
> > Anyway, the behaviour you are experiencing with the ps/2 keyboard
> > is weird enough to fill a bug in Debian BTS, I would go for it.
I'll do so.
--
Joe Riel
--
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/20110115123346.46efebe8@gauss
Re: Keyboard freezing/repeating endlessly
A followup. Yesterday I installed the nvidia driver, replacing the (default) nouveau driver. So far the keyboard has not locked up, however, given its random nature, there hasn't been enough time to conclude that the problem is solved. If it runs for a few days with no lockups (I've never gone more than 2 days without one), I'll submit a bug report against the nouveau driver. The nvidia driver has at least one annoying quirk; now my virtual-terminals are at a very coarse resolution. I've temporarily fixed that, but have related issues that will be the subject of a new thread. -- Joe Riel -- 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/20110116113550.6b836111@gauss
Re: Keyboard freezing/repeating endlessly
On Sun, 16 Jan 2011 11:35:50 -0800 Joe Riel wrote: > A followup. Yesterday I installed the nvidia driver, > replacing the (default) nouveau driver. So far the > keyboard has not locked up, however, given its > random nature, there hasn't been enough time to > conclude that the problem is solved. If it runs > for a few days with no lockups (I've never gone more > than 2 days without one), I'll submit a bug report > against the nouveau driver. So much for that...just had another lockup. Nothing in Xorg.0.log. The following tidbit is in syslog: Jan 17 10:50:42 gauss kernel: [48543.711837] atkbd.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0). Jan 17 10:50:42 gauss kernel: [48543.711842] atkbd.c: Use 'setkeycodes 00 ' to make it known. Jan 17 11:17:01 gauss /USR/SBIN/CRON[6167]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) The atkbd message occured at least 15 minutes before the lockup. The cron job occurred near the time of the lockout; I'll keep track of that in the future. Not sure how to file a useful Debian bug; what package would this apply? If I knew that ... -- Joe Riel -- 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/20110117120454.1387145d@gauss
Re: [SOLUTION] Keyboard freezing/repeating endlessly
A followup in case anyone has followed/found this thread with the same issue. A relevant fact is that I have an ASUS P7P55D Motherboard. An internet search revealed people with that (or similar numbered MB's) with the same issue; that is, the PS/2 keyboard would sporadically lock up, with Linux kernel 2.6.32. I've yet to find a fix. A useful thread is http://ubuntuforums.org/showthread.php?p=9818573 see, in particular, the post from Andrew Stevenson. Andrew suggests that reloading the psmouse kernel module during a lockup can be used to free it; I haven't confirmed that because I'm using the workaround (below). To do that, you need to access the machine remotely (or create a menu entry that does so, and which you can launch from a mouse). The work-around I have adopted, which has made the problem disappear, is to use a PS/2 to USB adapter and plug the keyboard into a USB port. -- 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/20110119111606.6b06407d@gauss
Cannot turn on bell in xterm
Is there some trick to enabling the bell in an xterm? $ xset q | grep bell bell percent: 100bell pitch: 400bell duration: 100 But echoing ^G, $ echo -v -g makes no beep. -- Joe Riel -- 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/20110120184025.0d0219e8@gauss
Cannot turn on bell in xterm
Is there some trick to enabling the bell in an xterm? $ xset q | grep bell bell percent: 100bell pitch: 400bell duration: 100 But echoing ^G, $ echo -v -g makes no beep. -- Joe Riel -- 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/20110120183835.22de4a21@gauss
Re: Cannot turn on bell in xterm
On Thu, 20 Jan 2011 20:15:01 -0700 Bob Proulx wrote: > Joe Riel wrote: > > Is there some trick to enabling the bell in an xterm? > > > > $ xset q | grep bell > > bell percent: 100bell pitch: 400bell duration: 100 > > > > But echoing ^G, > > > > $ echo -v -g > > > > makes no beep. > > Do you have the 'pcspkr' module loaded? > > lsmod | grep pcspkr Yes (thanks for this check): $ lsmod | grep pcspkr pcspkr 1699 0 > Is there a speaker attached to the motherboard hardware? I don't know. However, I've been using this motherboard for a year, so I'm certain it used to beep---just don't know whether the sound came from the external speakers or the MB. I suspect the MB; I frequently have the speakers turned off, but don't recall not hearing the beep. I've recently switched from Ubuntu 9.04 to Debian 6. I'm not sure whether the beep has occurred since that switch, or if it just went silent in the last day or so. The most recent changes I've made have been to switch to a USB keyboard (to avoid a lockup issue), and replace the neauveau driver with an nvidia driver (while debugging the lockup). > The terminal beep is one of those polarizing features. People either > love it or hate it. And so there isn't a right answer for having it > enable or disabled by default. I can live without it; at times it annoys me. But most of the time I like to have it. -- Joe Riel -- 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/20110120201255.57a3c43f@gauss
Re: Cannot turn on bell in xterm
On Fri, 21 Jan 2011 13:55:27 +0200 Andrei Popescu wrote: > On Jo, 20 ian 11, 18:38:35, Joe Riel wrote: > > Is there some trick to enabling the bell in an xterm? > > > > $ xset q | grep bell > > bell percent: 100bell pitch: 400bell duration: 100 > > > > But echoing ^G, > > > > $ echo -v -g > > > > makes no beep. > > Does it work on the console? Yes. That also confirms that the motherboard has a speaker. > beep That works; as expected the sound comes through the internal speakers. Must be an X configuration issue. Will look into that. -- Joe Riel -- 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/20110121071425.6cab5f33@gauss
Re: Cannot turn on bell in xterm
On Fri, 21 Jan 2011 07:14:25 -0800 Joe Riel wrote: > On Fri, 21 Jan 2011 13:55:27 +0200 > Andrei Popescu wrote: > > > On Jo, 20 ian 11, 18:38:35, Joe Riel wrote: > > > Is there some trick to enabling the bell in an xterm? > > > > > > $ xset q | grep bell > > > bell percent: 100bell pitch: 400bell duration: 100 > > > > > > But echoing ^G, > > > > > > $ echo -v -g > > > > > > makes no beep. > > > > Does it work on the console? > > Yes. That also confirms that the motherboard has a speaker. > > > beep > > That works; as expected the sound comes through the internal speakers. I meant "external" speakers. -- Joe Riel -- 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/20110121072756.049cf877@gauss
Re: Cannot turn on bell in xterm
On Fri, 21 Jan 2011 20:02:52 +0200 Andrei Popescu wrote: > On Vi, 21 ian 11, 07:14:25, Joe Riel wrote: > > > > > beep > > > > That works; as expected the sound comes through the internal > > speakers. > > Did you also try 'beep -e `tty`'? See beep(1) section "IOCTL > WACKINESS" if it fails. I get $ beep -e `tty` ioctl: Invalid argument ioctl: Invalid argument As corrected elsewhere, the sound from calling beep comes out of the external speakers. The sound I'm not hearing should come from the internal MB speaker. -- Joe Riel -- 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/20110121115107.682633d1@gauss
Re: Cannot turn on bell in xterm
On Fri, 21 Jan 2011 16:22:03 + (UTC) Camaleón wrote: > On Thu, 20 Jan 2011 18:38:35 -0800, Joe Riel wrote: > > > Is there some trick to enabling the bell in an xterm? > > > > $ xset q | grep bell > > bell percent: 100bell pitch: 400bell duration: 100 > > > > But echoing ^G, > > > > $ echo -v -g > > > > makes no beep. > > "echo ctrl+v" neither sounds here but "ctrl+g" and "echo -e "\a"" do > make speaker to beep. > Does it work under another terminal (i.e., aterm, gnome-terminal, > konsole...) inside an X session? No. So far, I've only got it work from a virtual terminal (console). > Another test to make "ring the bell" is searching for nonexistent > string in Iceweasel (ctrl+f). Emacs should ring the bell when I do something illegal. That's how I noticed it was silent. -- Joe Riel -- 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/20110121115633.4a3ed7ea@gauss
Re: Cannot turn on bell in xterm
On Sat, 22 Jan 2011 01:25:46 +0200 Andrei Popescu wrote: > On Vi, 21 ian 11, 11:51:07, Joe Riel wrote: > > On Fri, 21 Jan 2011 20:02:52 +0200 > > Andrei Popescu wrote: > > > > > On Vi, 21 ian 11, 07:14:25, Joe Riel wrote: > > > > > > > > > beep > > > > > > > > That works; as expected the sound comes through the internal > > > > speakers. > > > > > > Did you also try 'beep -e `tty`'? See beep(1) section "IOCTL > > > WACKINESS" if it fails. > > > > I get > > $ beep -e `tty` > > ioctl: Invalid argument > > ioctl: Invalid argument > > And does it beep? Under xfce4 this does produce a beep but not the > /usr/bin/beep one and nothing at all under lxde. See #610190. No beep when done in an xterm. It does beep when executed in a virtual terminal, and the ioctl error is not raised. > > As corrected elsewhere, the sound from calling beep > > comes out of the external speakers. The sound I'm > > not hearing should come from the internal MB speaker. I have to correct my correction. The sound from the beep command comes from the MB internal speakers, not from the external speakers. > Maybe you have issues with the "digital beep". Do you have a "Digital > Beep" and a "Beep" slider in alsamixer? Try muting/unmuting one or > the other. I don't have those controls on the alsamixer. Which option enables them? I looked at everything in the preferences tab. -- Joe Riel -- 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/20110121172203.3101b447@gauss
Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169
I just upgraded my system and got the warnings Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169 I then installed firmware-realtek, which provides the missing files. Do I need to reconfigure initramfs-tools for this to take effect? -- Joe Riel -- 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/20110122093638.08c02e16@gauss
Re: Cannot turn on bell in xterm
On Sat, 22 Jan 2011 16:56:44 + (UTC) Camaleón wrote: > On Fri, 21 Jan 2011 11:56:33 -0800, Joe Riel wrote: > > > On Fri, 21 Jan 2011 16:22:03 + (UTC) Camaleón wrote: > > > >> Does it work under another terminal (i.e., aterm, gnome-terminal, > >> konsole...) inside an X session? > > > > No. So far, I've only got it work from a virtual terminal > > (console). > > Hum... > > >> Another test to make "ring the bell" is searching for nonexistent > >> string in Iceweasel (ctrl+f). > > > > Emacs should ring the bell when I do something illegal. That's how I > > noticed it was silent. > > So this is a system wide issue, not just "xterm". > > What does "amixer" show on PC Speaker? I don't see any entries for "PC Speaker": $ amixer | grep control Simple mixer control 'Headphone',0 Simple mixer control 'PCM',0 Simple mixer control 'Front',0 Simple mixer control 'Front Mic',0 Simple mixer control 'Front Mic Boost',0 Simple mixer control 'Surround',0 Simple mixer control 'Center',0 Simple mixer control 'LFE',0 Simple mixer control 'Side',0 Simple mixer control 'Line',0 Simple mixer control 'CD',0 Simple mixer control 'Mic',0 Simple mixer control 'Mic Boost',0 Simple mixer control 'IEC958',0 Simple mixer control 'IEC958 Default PCM',0 Simple mixer control 'Capture',0 Simple mixer control 'Capture',1 Simple mixer control 'Digital',0 Simple mixer control 'Independent HP',0 Simple mixer control 'Input Source',0 Simple mixer control 'Input Source',1 Simple mixer control 'Smart 5.1',0 -- Joe Riel -- 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/20110122093900.52636b49@gauss
Re: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169
On Sat, 22 Jan 2011 18:09:38 + Roger Leigh wrote: > On Sat, Jan 22, 2011 at 06:43:04PM +0100, Hans-J. Ullrich wrote: > > Am Samstag, 22. Januar 2011 schrieb Joe Riel: > > > I just upgraded my system and got the warnings > > > > > > Processing triggers for initramfs-tools ... > > > update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64 > > > W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw > > > for module r8169 W: Possible missing > > > firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169 > > > > > > I then installed firmware-realtek, which provides the missing > > > files. Do I need to reconfigure initramfs-tools for this to take > > > effect? > > No, a far as I know, the required kernel-modules are searching > > in /lib/firmware and load, what they need. However, if you do not > > trust them, you can do "update-initramfs -u", which does not do > > dangerous things. > > The initramfs /might/ need the firmware before / is mounted (example: > netbooting) in which case the firmware will be needed in the initrd. > So running update-initramfs is certainly going to do no harm, and > may be required. Thanks. I ran update-initramfs. Don't know if *that* did anything, but following a reboot kern.log had changed: WAS: Jan 17 23:26:00 gauss kernel: [1.001780] r8169 :02:00.0:firmware: requesting rtl8168d-2.fw Jan 17 23:26:00 gauss kernel: [1.002981] eth0: unable to apply firmware patch IS: Jan 22 09:52:54 gauss kernel: [0.998226] r8169 :02:00.0:firmware: requesting rtl_nic/rtl8168d-2.fw -- Joe Riel -- 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/20110122123058.5b5f3492@gauss
Re: Cannot turn on bell in xterm
On Sun, 23 Jan 2011 19:47:51 + (UTC) Camaleón wrote: > On Sat, 22 Jan 2011 09:39:00 -0800, Joe Riel wrote: > > > On Sat, 22 Jan 2011 16:56:44 + (UTC) Camaleón wrote: > > > >> What does "amixer" show on PC Speaker? > > > > I don't see any entries for "PC Speaker": > > > > $ amixer | grep control > > (...) > > Hum... in fact, while I have a "PC speaker" entry in squeeze, I've > just checked in lenny and there is none (but the beep works). > > Just a silly question... have you somehow disabled the sytem bell > under your DE? In GNOME there is a checkbox you can toggle on/off. Where would that be? I just installed Debian 6 on a different computer, with vastly different hardware, and it behaves the same way, that is no bell. -- Joe Riel -- 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/20110123130415.6d2dff25@gauss
Re: Cannot turn on bell in xterm
On Sun, 23 Jan 2011 13:04:15 -0800 Joe Riel wrote: > On Sun, 23 Jan 2011 19:47:51 + (UTC) > Camaleón wrote: > > > On Sat, 22 Jan 2011 09:39:00 -0800, Joe Riel wrote: > > > > > On Sat, 22 Jan 2011 16:56:44 + (UTC) Camaleón wrote: > > > > > >> What does "amixer" show on PC Speaker? > > > > > > I don't see any entries for "PC Speaker": > > > > > > $ amixer | grep control > > > > (...) > > > > Hum... in fact, while I have a "PC speaker" entry in squeeze, I've > > just checked in lenny and there is none (but the beep works). > > > > Just a silly question... have you somehow disabled the sytem bell > > under your DE? In GNOME there is a checkbox you can toggle on/off. > > Where would that be? > > I just installed Debian 6 on a different computer, with vastly > different hardware, and it behaves the same way, that is no bell. I found a "terminal bell" checkbox in gnome-terminal (Edit -> General); it was checked. -- Joe Riel -- 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/20110123134638.56a38341@gauss
Re: Cannot turn on bell in xterm
On Sun, 23 Jan 2011 21:48:29 + (UTC) Camaleón wrote: > On Sun, 23 Jan 2011 13:04:15 -0800, Joe Riel wrote: > > > On Sun, 23 Jan 2011 19:47:51 + (UTC) Camaleón wrote: > > >> > I don't see any entries for "PC Speaker": > >> > > >> > $ amixer | grep control > >> > >> (...) > >> > >> Hum... in fact, while I have a "PC speaker" entry in squeeze, I've > >> just checked in lenny and there is none (but the beep works). > >> > >> Just a silly question... have you somehow disabled the sytem bell > >> under your DE? In GNOME there is a checkbox you can toggle on/off. > > > > Where would that be? > > > > I just installed Debian 6 on a different computer, with vastly > > different hardware, and it behaves the same way, that is no bell. > > It should be under "start / system / preferences / system sound, > sounds effects tab > alert volume" > > 8.4.4.1. Sound Effects Preferences > http://library.gnome.org/users/user-guide/2.30/goscustmulti-2.html.en#goscustmulti-TBL-6 I normally use fvwm, but brought up gnome to check this. I cannot find a "sound preferences" menu. The help page is useless; it doesn't say where the "sound preferences" submenu is located. It suggests it is under System -> Preferences, but the only relevant entry I see there is "Sound", which has none of the options discussed (just settings for alsa mixer). > > You may also want to ensure that Gnome-conf has the key > "/apps/metacity/ general/audible_bell" [x] checked. -- Joe Riel -- 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/20110123140447.50f04331@gauss
java 5 in squeeze
How can I install sun java 1.5 in squeeze? It isn't part of the release. -- Joe Riel -- 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/20110124105325.7e867e42@gauss
Re: java 5 in squeeze
On Mon, 24 Jan 2011 12:12:22 -0700 Bob Proulx wrote: > Joe Riel wrote: > > How can I install sun java 1.5 in squeeze? > > It isn't part of the release. > > Java 1.6 is included in the non-free section. > > apt-get install sun-java6-jre > > Useful information about this can be found on the wiki: > > http://wiki.debian.org/Java/Sun > > If you absolutely need Java 1.5 then you will need to install the > older version from the Lenny non-free archive. > > http://packages.debian.org/lenny/sun-java5-jre Right. How would I do that? My knowledge of debian's package manager is minimal. I'm guessing that I'm not supposed to modify sources.list, but rather do something else. Maybe just download the deb and install it with dpkg? Is there a proper way to do this? -- Joe Riel -- 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/20110124111921.0569d9a0@gauss
Re: Cannot turn on bell in xterm
On Mon, 24 Jan 2011 19:06:34 + (UTC) Camaleón wrote: > On Sun, 23 Jan 2011 14:04:47 -0800, Joe Riel wrote: > > > On Sun, 23 Jan 2011 21:48:29 + (UTC) Camaleón wrote: > > > >> > I just installed Debian 6 on a different computer, with vastly > >> > different hardware, and it behaves the same way, that is no bell. > >> > >> It should be under "start / system / preferences / system sound, > >> sounds effects tab > alert volume" > >> > >> 8.4.4.1. Sound Effects Preferences > >> http://library.gnome.org/users/user-guide/2.30/goscustmulti-2.html.en#goscustmulti-TBL-6 > > > > I normally use fvwm, but brought up gnome to check this. I cannot > > find a "sound preferences" menu. The help page is useless; it > > doesn't say where the "sound preferences" submenu is located. > > Usually it can be also launched with "gnome-sound-properties". > > > It suggests it is under System -> Preferences, but the only > > relevant entry I see there is "Sound", which has none of the > > options discussed (just settings for alsa mixer). > > Can you upload a snapshot (www.picpaste.com) of what you see in > there? I don't have a gnome-sound-properties executable. Also, $ apt-file find gnome-sound-properties gnome-colors-common: /usr/share/icons/gnome-colors-common/16x16/apps/gnome-sound-properties.png gnome-colors-common: /usr/share/icons/gnome-colors-common/22x22/apps/gnome-sound-properties.png gnome-colors-common: /usr/share/icons/gnome-colors-common/24x24/apps/gnome-sound-properties.png gnome-colors-common: /usr/share/icons/gnome-colors-common/32x32/apps/gnome-sound-properties.png gnome-colors-common: /usr/share/icons/gnome-colors-common/scalable/apps/gnome-sound-properties.svg xiphos-data: /usr/share/xiphos/gnome-sound-properties.png No executables in there -- Joe Riel -- 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/20110124112454.6143ed47@gauss
Re: java 5 in squeeze
On Mon, 24 Jan 2011 20:05:21 +0100 "Hans-J. Ullrich" wrote: > Am Montag, 24. Januar 2011 schrieb Joe Riel: > > How can I install sun java 1.5 in squeeze? > > It isn't part of the release. > > The package is sun-java5-jre. > > If it is not here, add the repositoey of stable in sources.list. No, it isn't there. It isn't part of squeeze. -- Joe Riel -- 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/2011012453.46ed5445@gauss
Re: Cannot turn on bell in xterm
On Mon, 24 Jan 2011 11:24:54 -0800 Joe Riel wrote: > On Mon, 24 Jan 2011 19:06:34 + (UTC) > Camaleón wrote: > > > On Sun, 23 Jan 2011 14:04:47 -0800, Joe Riel wrote: > > > > > On Sun, 23 Jan 2011 21:48:29 + (UTC) Camaleón wrote: > > > > > >> > I just installed Debian 6 on a different computer, with vastly > > >> > different hardware, and it behaves the same way, that is no > > >> > bell. > > >> > > >> It should be under "start / system / preferences / system sound, > > >> sounds effects tab > alert volume" > > >> > > >> 8.4.4.1. Sound Effects Preferences > > >> http://library.gnome.org/users/user-guide/2.30/goscustmulti-2.html.en#goscustmulti-TBL-6 > > > > > > I normally use fvwm, but brought up gnome to check this. I cannot > > > find a "sound preferences" menu. The help page is useless; it > > > doesn't say where the "sound preferences" submenu is located. > > > > Usually it can be also launched with "gnome-sound-properties". > > > > > It suggests it is under System -> Preferences, but the only > > > relevant entry I see there is "Sound", which has none of the > > > options discussed (just settings for alsa mixer). > > > > Can you upload a snapshot (www.picpaste.com) of what you see in > > there? > > I don't have a gnome-sound-properties executable. Also, > > $ apt-file find gnome-sound-properties > gnome-colors-common: > /usr/share/icons/gnome-colors-common/16x16/apps/gnome-sound-properties.png > gnome-colors-common: > /usr/share/icons/gnome-colors-common/22x22/apps/gnome-sound-properties.png > gnome-colors-common: > /usr/share/icons/gnome-colors-common/24x24/apps/gnome-sound-properties.png > gnome-colors-common: > /usr/share/icons/gnome-colors-common/32x32/apps/gnome-sound-properties.png > gnome-colors-common: > /usr/share/icons/gnome-colors-common/scalable/apps/gnome-sound-properties.svg > xiphos-data: /usr/share/xiphos/gnome-sound-properties.png > > No executables in there I have squeeze testing. I see that it exists in gnome-control-center, in unstable. -- Joe Riel -- 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/20110124113028.316b5bf7@gauss
Re: java 5 in squeeze
On Mon, 24 Jan 2011 21:32:48 +0100 Jochen Schulz wrote: > Joe Riel: > > Bob Proulx wrote: > > > >> If you absolutely need Java 1.5 then you will need to install the > >> older version from the Lenny non-free archive. > >> > >> http://packages.debian.org/lenny/sun-java5-jre > > > > Right. How would I do that? > > In order to install packages from the non-free section, just add > "non-free" at the end of your sources.list lines. Example for squeeze: > > deb http://ftp2.de.debian.org/debian/ squeeze main contrib non-free > > It works exactly the same for older Debian versions. After editing > sources.list, just 'apt-get update' (or 'aptitude update', whatever > you prefer) and go on installing the package you want. I meant, how would I get it from *lenny*. I've seen one recommendation to temporarily changes sources.list to use lenny rather than squeeze. Another said not to do that, but didn't give an alternative. -- Joe Riel -- 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/20110124123839.70373f78@gauss
Re: java 5 in squeeze
On Mon, 24 Jan 2011 14:08:06 -0600 "Boyd Stephen Smith Jr." wrote: > I recommend not changing back your sources.list and actually adding > the security repository for Lenny as well. I may have misinterpreted this. Are you saying to change it to lenny and not change it back after updating and installing java 5? Or are you saying not to change it to lenny in the first place [and do something else to obtain the files]? Thanks, -- Joe Riel -- 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/20110124131514.16ce33fe@gauss
Re: Cannot turn on bell in xterm
On Tue, 25 Jan 2011 12:03:14 + (UTC) Camaleón wrote: > On Mon, 24 Jan 2011 11:30:28 -0800, Joe Riel wrote: > > > On Mon, 24 Jan 2011 11:24:54 -0800 Joe Riel wrote: > > > >> On Mon, 24 Jan 2011 19:06:34 + (UTC) Camaleón wrote: > > (...) > > >> > Can you upload a snapshot (www.picpaste.com) of what you see in > >> > there? > > You forgot the image :-P > > >> I don't have a gnome-sound-properties executable. Also, > >> > >> $ apt-file find gnome-sound-properties > >> gnome-colors-common: > >> /usr/share/icons/gnome-colors-common/16x16/apps/gnome-sound-properties.png > >> gnome-colors-common: > >> /usr/share/icons/gnome-colors-common/22x22/apps/gnome-sound-properties.png > >> gnome-colors-common: > >> /usr/share/icons/gnome-colors-common/24x24/apps/gnome-sound-properties.png > >> gnome-colors-common: > >> /usr/share/icons/gnome-colors-common/32x32/apps/gnome-sound-properties.png > >> gnome-colors-common: > >> /usr/share/icons/gnome-colors-common/scalable/apps/gnome-sound-properties.svg > >> xiphos-data: /usr/share/xiphos/gnome-sound-properties.png > >> > >> No executables in there > > That probably means you don't have the full GNOME installed and I > guess that was your choice. > > > I have squeeze testing. I see that it exists in > > gnome-control-center, in unstable. > > The package is also available for lenny and squeeze, is part of the > GNOME desktop, but you said you were not using a DE at all but > "fvwm", and also said that the bell was working at tty so look into > fvwm sound settings or try to load a LiveCD with a full GNOME and > check if it working from there. While I normally run fvwm, I did the normal destop installation, so should have the complete Gnome. On my older machine, which just got a fresh installation, I don't (yet) run fvwm. On it, too, the bell does not work. Using the debian package search (http://www.debian.org/distrib/packages) I see that there is *no* listing for gnome-control-center in Debian *testing* (which is what I have). There is one in unstable and in stable. That seems a trifle strange. -- Joe Riel -- 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/20110125073257.3c91b2d5@gauss
Re: Cannot turn on bell in xterm
On Tue, 25 Jan 2011 15:56:35 + (UTC) Camaleón wrote: > On Tue, 25 Jan 2011 07:32:57 -0800, Joe Riel wrote: > > > On Tue, 25 Jan 2011 12:03:14 + (UTC) Camaleón wrote: > > > >> >> > Can you upload a snapshot (www.picpaste.com) of what you see > >> >> > in there? > >> > >> You forgot the image :-P > > No image this time :-) > > >> The package is also available for lenny and squeeze, is part of the > >> GNOME desktop, but you said you were not using a DE at all but > >> "fvwm", and also said that the bell was working at tty so look > >> into fvwm sound settings or try to load a LiveCD with a full GNOME > >> and check if it working from there. > > > > While I normally run fvwm, I did the normal destop installation, so > > should have the complete Gnome. On my older machine, which just > > got a fresh installation, I don't (yet) run fvwm. On it, too, the > > bell does not work. > > > > Using the debian package search > > (http://www.debian.org/distrib/packages) I see that there is *no* > > listing for gnome-control-center in Debian *testing* (which is what > > I have). There is one in unstable and in stable. That seems a > > trifle strange. > > I've got that piece of sowftware installed in my squeeze so it should > be available also for you :-) > > http://packages.debian.org/squeeze/gnome-control-center Errh, yes and no. I do have gnome-control-center installed: $ dpkg -s gnome-control-center Package: gnome-control-center Status: install ok installed Priority: optional Section: gnome Installed-Size: 2024 Maintainer: Debian GNOME Maintainers Architecture: amd64 Source: control-center Version: 1:2.30.1-2 however, that version of that package does *not* contain the desired sound executable: $ cat /var/lib/dpkg/info/gnome-control-center.list /. /usr /usr/share /usr/share/doc /usr/share/doc/gnome-control-center /usr/share/doc/gnome-control-center/README /usr/share/doc/gnome-control-center/TODO /usr/share/doc/gnome-control-center/AUTHORS /usr/share/doc/gnome-control-center/copyright /usr/share/doc/gnome-control-center/NEWS.gz /usr/share/doc/gnome-control-center/changelog.Debian.gz /usr/share/doc/gnome-control-center/changelog.gz /usr/share/man /usr/share/man/man1 /usr/share/man/man1/gnome-keyboard-properties.1.gz /usr/share/man/man1/gnome-control-center.1.gz /usr/share/menu /usr/share/menu/gnome-control-center /usr/share/pixmaps /usr/share/pixmaps/control-center2.xpm /usr/bin /usr/bin/gnome-at-properties /usr/bin/gnome-appearance-properties /usr/bin/gnome-default-applications-properties /usr/bin/gnome-at-visual /usr/bin/gnome-at-mobility /usr/bin/gnome-display-properties /usr/bin/gnome-keybinding-properties /usr/bin/gnome-keyboard-properties /usr/bin/gnome-mouse-properties /usr/bin/gnome-network-properties /usr/bin/gnome-window-properties /usr/bin/gnome-about-me /usr/bin/gnome-thumbnail-font /usr/bin/gnome-font-viewer /usr/bin/gnome-control-center /usr/bin/gnome-typing-monitor Presumably I'll have to get it from unstable. -- Joe Riel -- 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/20110125081554.669b2b0c@gauss
Re: Cannot turn on bell in xterm
On Tue, 25 Jan 2011 16:34:50 + (UTC) Camaleón wrote: > On Tue, 25 Jan 2011 08:15:54 -0800, Joe Riel wrote: > > > On Tue, 25 Jan 2011 15:56:35 + (UTC) Camaleón wrote: > > > >> On Tue, 25 Jan 2011 07:32:57 -0800, Joe Riel wrote: > >> > >> > On Tue, 25 Jan 2011 12:03:14 + (UTC) Camaleón wrote: > >> > > >> >> >> > Can you upload a snapshot (www.picpaste.com) of what you > >> >> >> > see in there? > >> >> > >> >> You forgot the image :-P > >> > >> No image this time :-) > > Maybe I should fill an online petition >:-P See http://www.picpaste.com/volume-control-k6X7Egse.png I enabled every option in "preferences". This control clearly has nothing to do with enabling the beep. > >> > Using the debian package search > >> > (http://www.debian.org/distrib/packages) I see that there is *no* > >> > listing for gnome-control-center in Debian *testing* (which is > >> > what I have). There is one in unstable and in stable. That > >> > seems a trifle strange. > >> > >> I've got that piece of sowftware installed in my squeeze so it > >> should be available also for you :-) > >> > >> http://packages.debian.org/squeeze/gnome-control-center > > > > Errh, yes and no. I do have gnome-control-center installed: > > > > $ dpkg -s gnome-control-center > > Package: gnome-control-center > > Status: install ok installed > > Priority: optional > > Section: gnome > > Installed-Size: 2024 > > Maintainer: Debian GNOME Maintainers > > Architecture: amd64 > > Source: control-center > > Version: 1:2.30.1-2 > > > > however, that version of that package does *not* contain the desired > > sound executable: > > > > $ cat /var/lib/dpkg/info/gnome-control-center.list /. > > (...) > > > Presumably I'll have to get it from unstable. > > Okay, no... is just it has been renamed in squeeze to "gnome-volume- > control". That (see posted png, above) does not appear to have anything to do with controlling sound properties. It is different from the help page description mentioned a while back in this thread. -- Joe Riel -- 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/20110125084916.74637f0d@gauss
Re: Cannot turn on bell in xterm
On Tue, 25 Jan 2011 17:19:07 + (UTC) Camaleón wrote: > On Tue, 25 Jan 2011 08:49:16 -0800, Joe Riel wrote: > > > On Tue, 25 Jan 2011 16:34:50 + (UTC) Camaleón wrote: > > > >> >> >> >> > Can you upload a snapshot (www.picpaste.com) of what > >> >> >> >> > you see in there? > >> >> >> > >> >> >> You forgot the image :-P > >> >> > >> >> No image this time :-) > >> > >> Maybe I should fill an online petition >:-P > > > > See http://www.picpaste.com/volume-control-k6X7Egse.png > > Yeepy! (thanx) > > > I enabled every option in "preferences". This control clearly has > > nothing to do with enabling the beep. > > Something interesting under "options" or "sound theme" tab? Nothing seemed relevant. The "options" tab has one check box, "Independent HP", which by default is enabled. I don't know what that does. The "sound theme" tab consists of five radio buttons: "Default", "Bark", "Drip", "Glass", and "Sonar". There is a check box to enable the selected effect (it is checked) > > >> > however, that version of that package does *not* contain the > >> > desired sound executable: > >> > > >> > $ cat /var/lib/dpkg/info/gnome-control-center.list /. > >> > >> (...) > >> > >> > Presumably I'll have to get it from unstable. > >> > >> Okay, no... is just it has been renamed in squeeze to > >> "gnome-volume- control". > > > > That (see posted png, above) does not appear to have anything to do > > with controlling sound properties. It is different from the help > > page description mentioned a while back in this thread. > > Oh, and now I guess why: "pulse audio". A default gnome installation > would expect to have PA installed and so that it appears documented > in their docs (I suggest you _do not_ install PA unless you really > know what you are doing). Thanks. I'll look into it, but cautiously. -- Joe Riel -- 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/20110125093108.2509ad9d@gauss
Remove nvidia driver and reinstall nouveau
Is there a nice way to remove the nvidia driver and replace it with the nouveau driver (which was originally installed with Debian squeeze)? I tried modifying xorg.conf and removing /etc/modprobe.d/nvidia-kernel-common.conf; that partially worked, however, glx didn't work because of the different kernel installed when nvidia was installed. -- Joe Riel -- 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/20110127221243.6e5d205f@gauss
Re: Cannot turn on bell in xterm [SOLVED]
On Thu, 20 Jan 2011 18:38:35 -0800 Joe Riel wrote: > Is there some trick to enabling the bell in an xterm? > > $ xset q | grep bell > bell percent: 100bell pitch: 400bell duration: 100 > > But echoing ^G, > > $ echo -v -g > > makes no beep. A partial solution, anyhow. I've found that reenabling the nouveau driver, which I had replaced with the nvidia driver to debug a different issue, enabled the beep. I'm now looking for a clean way to do the replacement (different thread). A related item. I noticed that /etc/modprobe.d/alsa-base-blacklist.conf contains # Comment this entry in order to load snd-pcsp driver blacklist snd-pcsp Is that be significant? Seems that might affect the pc speaker. I tried commenting it out [with nvidia driver active], but didn't notice a difference after rebooting. Does the snd-pcsp driver have to be loaded explicitly by something else? -- Joe Riel -- 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/20110127221857.696520ce@gauss
Re: Remove nvidia driver and reinstall nouveau
On Fri, 28 Jan 2011 08:32:02 +0100 Sven Joachim wrote: > On 2011-01-28 07:12 +0100, Joe Riel wrote: > > > Is there a nice way to remove the nvidia driver and replace > > it with the nouveau driver (which was originally installed > > with Debian squeeze)? > > If you have used the Debian packages in non-free, definitely. If you > have run NVidia's installer, I'm not so sure. Which method did you > choose? I used the Debian packages from non-free. Presumably I'll need to purge those. But do I also have to reconfigure/reinstall the nouveau driver package? Since the nvidia package installs a different kernel, do I have to manually (via aptitude) install a new one, or will aptitude know to do that? > > I tried modifying xorg.conf and > > removing /etc/modprobe.d/nvidia-kernel-common.conf; that > > partially worked, however, glx didn't work because of the > > different kernel installed when nvidia was installed. > > GLX not working has nothing to do with the kernel, it's because the > nvidia driver installs its own incompatible implementation. > > Sven > > -- Joe Riel -- 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/20110128072644.77a77f06@gauss
Re: Remove nvidia driver and reinstall nouveau
On Fri, 28 Jan 2011 18:02:50 +0100
Sven Joachim wrote:
> On 2011-01-28 16:26 +0100, Joe Riel wrote:
>
> > On Fri, 28 Jan 2011 08:32:02 +0100
> > Sven Joachim wrote:
> >
> >> On 2011-01-28 07:12 +0100, Joe Riel wrote:
> >>
> >> > Is there a nice way to remove the nvidia driver and replace
> >> > it with the nouveau driver (which was originally installed
> >> > with Debian squeeze)?
> >>
> >> If you have used the Debian packages in non-free, definitely. If
> >> you have run NVidia's installer, I'm not so sure. Which method
> >> did you choose?
> >
> > I used the Debian packages from non-free. Presumably I'll need to
> > purge those.
>
> Removing them should suffice, since you have already taken out the
> blacklist entry that nvidia-kernel-common has installed.
>
> > But do I also have to reconfigure/reinstall the
> > nouveau driver package?
>
> No.
>
> > Since the nvidia package installs a different
> > kernel, do I have to manually (via aptitude) install a new one, or
> > will aptitude know to do that?
>
> Hm? The nvidia packages do not install kernels, they only install
> _modules_ for your kernel(s). Those should be harmless, since the
> nvidia module is not autoloaded unless you also use the nvidia X
> driver.
Thanks, I got confused by the name: nvidia-kernel-2.6.32-5-amd64.
I assumed that was a kernel rather than a kernel module.
> It seems that the packaging of the nvidia stuff has changed in the
> last ten months, and you need to remove the
> libgl{1,x}-nvidia-alternatives packages to restore
> the /usr/lib/xorg/modules/extensions/libglx.so
> and /usr/lib/libGL.so.1 files that these packages divert.
--
Joe Riel
--
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/20110128102648.11b7a402@gauss
Re: Remove nvidia driver and reinstall nouveau
On Fri, 28 Jan 2011 08:42:30 +0100 Thierry Chatelet wrote: > On Friday 28 January 2011 07:12:43 Joe Riel wrote: > > Is there a nice way to remove the nvidia driver and replace > > it with the nouveau driver (which was originally installed > > with Debian squeeze)? > > > > I tried modifying xorg.conf and > > removing /etc/modprobe.d/nvidia-kernel-common.conf; that > > partially worked, however, glx didn't work because of the > > different kernel installed when nvidia was installed. > > Purge whatever nvidia staff you installed and move away xorg.conf, > it wont be needed any longer > Thierry > > Thanks for all the responses. I did dpkg --get-selections | grep nvidia | xargs sudo aptitude purge --assume-yes sudo rm /etc/X11/xorg.conf then rebooted. All is well, so far. This has restored the pc-speaker beep and improved the console font. -- Joe Riel -- 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/20110128225633.08c4b4c9@gauss
Release file expired
Ran apt-get update today and received E: Release file expired, ignoring http://linux.csua.berkeley.edu/debian/dists/testing/Release (invalid since 6h 36min 31s) Do I have to install/update an ssh key? -- Joe Riel -- 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/20110201125818.74f430ec@gauss
Re: Release file expired
On Tue, 01 Feb 2011 22:03:32 +0100 Jerome BENOIT wrote: > Hello Joe, > > On 01/02/11 21:58, Joe Riel wrote: > > Ran apt-get update today and received > > > > E: Release file expired, ignoring > > http://linux.csua.berkeley.edu/debian/dists/testing/Release (invalid > > since 6h 36min 31s) > > > > Do I have to install/update an ssh key? > > Have you tried an other mirror ? That fixed it. Sorry for the bother. Thanks for the solution. -- Joe Riel -- 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/20110201131359.47c11e8f@gauss
alternatives for gcc
Why are there no alternatives, configurable with update-alternatives, for gcc? Seems like I should be able to configure whether /usr/bin/gcc is linked to gcc-4.3, gcc-4.4, etc. Of course I can just set the link manually (which I do), but ... -- Joe Riel -- 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/20110201171131.491f2628@gauss
Re: alternatives for gcc
On Tue, 01 Feb 2011 21:01:13 -0500 Andrew Reid wrote: > On Tuesday 01 February 2011 20:11:31 Joe Riel wrote: > > Why are there no alternatives, configurable with > > update-alternatives, for gcc? Seems like I should be able to > > configure whether /usr/bin/gcc is linked to gcc-4.3, gcc-4.4, > > etc. Of course I can just set the link manually (which I do), > > but ... > > Can't you set up new alterantives within the update-alternatives > mechanism? > > I have never done this, but it was one of the options I was > considering a while ago to control which version of an app > was the default -- as it turned out, I was able to use the > "stow" mechanism to good effect, because it was a non-packaged > app, so I only got as far as reading the update-alterantives > documentation. > > The man-page says that the "--install" option sets up a new > batch of alternatives. > > I don't know if this will interact constructively with the > package manager. > > -- A. The following worked: sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.4 60 sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.3 50 Then, to configure 4.3 as the default, I did sudo update-alternatives --config gcc and selected 4.3. The packages that install gcc-4.3 and gcc-4.4 should possibly call update-alternatives --install as part of their postinstall routine. -- Joe Riel -- 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/20110201220515.1f365b41@gauss
Re: alternatives for gcc
On Wed, 02 Feb 2011 06:31:30 +0100 deloptes wrote: > Joe Riel wrote: > > > Why are there no alternatives, configurable with > > update-alternatives, for gcc? Seems like I should be able to > > configure whether /usr/bin/gcc is linked to gcc-4.3, gcc-4.4, > > etc. Of course I can just set the link manually (which I do), > > but ... > > > > every normal automake or cmake accepts the CC,CXX, CPP or equivalents > to manage this. Especially in later releases of gcc this seems to be > working very well, so I'm not sure if it's really necessary to do so. > Let me know if you are able to update it with update-alternatives > and how, because I've been asking myself how this could be setup as > default in the past. The problem I ran into was that Matlab R2010b works with gcc 4.3 but not 4.4 and I didn't know how to configure Matlab to use 4.3. However, I now see that that can be solved by editing ~/.matlab/R2010b/mexopts.sh, changing CC="gcc" to CC="gcc-4.3" So I didn't need the use the debian alternatives after all. But see my other response for how I did it. As you suggest, this is probably the typical case, which explains why alternatives are not used with gcc. -- Joe Riel -- 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/20110201221544.440805e1@gauss
Re: alternatives for gcc
On Wed, 02 Feb 2011 09:18:00 +0100 Sven Joachim wrote: > On 2011-02-02 03:01 +0100, Andrew Reid wrote: > > > On Tuesday 01 February 2011 20:11:31 Joe Riel wrote: > >> Why are there no alternatives, configurable with > >> update-alternatives, for gcc? Seems like I should be able to > >> configure whether /usr/bin/gcc is linked to gcc-4.3, gcc-4.4, > >> etc. Of course I can just set the link manually (which I do), > >> but ... > > See /usr/share/doc/gcc/README.Debian why gcc is not managed via > alternatives. Thanks for pointing me here. -- Joe Riel -- 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/20110202073203.2e563728@gauss
Proper way to restart network after modem/router reset
Occasionally I need reset the external cable modem/router that connects our home machines to the internet. After doing so, I frequently have to reboot my machine to establish a connection. Occasionally I've been successful just doing $ sudo dhclient -r $ sudo dhclient However, that frequently does not work. When on Ubuntu I occasionally was able to succeed with $ sudo /etc/init.d/networking restart Trying that on Squeeze gives the warning Running /etc/init.d/networking restart deprecated because it may not enable again some interfaces Web searching indicate that $ sudo service networking restart may be the proper way, however that was unclear. I haven't tried that yet. Is there a recommended method? Is there a Debian howto that recommends what should be done? -- Joe Riel -- 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/20110213083906.3d4e371f@gauss
Re: Proper way to restart network after modem/router reset
On Sun, 13 Feb 2011 19:10:08 +0200 Andrei Popescu wrote: > On Du, 13 feb 11, 08:39:06, Joe Riel wrote: > > > > may be the proper way, however that was unclear. I haven't tried > > that yet. Is there a recommended method? Is there a Debian howto > > that recommends what should be done? > > Assuming your network is configured via /etc/network/interfaces (you > didn't mention) then 'ifup' and 'ifdown' is what you are looking for > AFAIK. $ grep -v '^\#' /etc/network/interfaces auto lo iface lo inet loopback allow-hotplug eth0 Should I then do sudo ifdown eth0 sudo ifup etho0 Hmm. That doesn't work: $ sudo ifdown eth0 ifdown: interface eth0 not configured I haven't done anything in particular to configure my installation of Squeeze for the local network; just accepted the defaults. -- Joe Riel -- 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/20110213092706.46c74df1@gauss
Re: I want beep in urxvt terminal
I started a similar thread about two weeks ago. Finally resolved it by switching from the nvidia driver to the nouveau driver. Why that made a difference is beyond me, but it did. Joe Riel -- 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/20110215204734.5c36b1b8@gauss
Re: Proper way to restart network after modem/router reset
Thanks, all for the replies. As has been surmised, I'm using NetworkManager. So next time the cable modem needs to be rebooted, I'll try sudo /etc/init.d/network-manager restart and see if that reestablishes a connection. I gather I don't need to use NetworkManager---this is on a desktop PC with a ethernet connection, no wireless, etc. However, for the nonce I'll leave well enough alone. Joe -- 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/20110215211804.7ea9effd@gauss
Re: I want beep in urxvt terminal - SOLVED
On Fri, 18 Feb 2011 23:04:34 -0600 Ron Johnson wrote: > On 02/17/2011 09:58 AM, Brad Rogers wrote: > > On Thu, 17 Feb 2011 09:16:16 -0600 > > Ron Johnson wrote: > > > > Hello Ron, > > > >> Yes, I use nvidia, and no I won't use nouveau. > > > > Entirely your prerogative of course, but might I ask why? > > > > Performance. > Just curious, what do you notice? I don't notice a difference, but I don't really do much that would show up. An advantage for me of the noveau driver, besides restoring the beep in an xterm, was that the console font (in a virtual terminal) is much nicer. I had tried various configurations of the console font with the nvidia driver, but it never looked good---too big and kind of fuzzy. The console font with the nouveau driver is sharp, reasonably small, and didn't require any configuration on my part. I don't use the console much, but when I have to its nice to be able to comfortably read it. -- Joe Riel -- 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/20110219110906.70e9aef1@gauss
Re: Setup xterm to use TrueType Fonts in .Xdefaults or .Xresources
On Sun, 20 Feb 2011 18:06:56 +0100 Csanyi Pal wrote: > Csanyi Pal writes: > > > Lines that I tried to use for this setup in .Xdefaults doesn't works > > when I log out/in into X Window system, but only works when I run > > the command 'xrdb -merge .Xdefaults': > > > > xterm*geometry: 90x40 > > xterm*renderFont: default > > xterm*cursorBlink: true > > If I use .Xresources file instead then I get the right geometry and > the blinking cursor when I log out/in into X Window system. I believe .Xdefaults is no longer used. The system file /etc/X11/Xsession assigns USRRESOURCES=$HOME/.Xresources, which is what is used [by /etc/X11/Xsession.d/30x11-common_xresources] to merge your resource file. -- Joe Riel -- 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/20110220102145.01895146@gauss
Re: I want beep in urxvt terminal - SOLVED
On Mon, 21 Feb 2011 03:35:15 +0200 Andrei Popescu wrote: > On Sb, 19 feb 11, 11:09:06, Joe Riel wrote: > > > > An advantage for me of the noveau driver, besides restoring the > > beep in an xterm, was that the console font (in a virtual terminal) > > is much nicer. I had tried various configurations of the console > > font with the nvidia driver, but it never looked good---too big and > > kind of fuzzy. The console font with the nouveau driver is sharp, > > reasonably small, and didn't require any configuration on my part. > > > > I don't use the console much, but when I have to its nice to > > be able to comfortably read it. > > First step would be to use the correct resolution for your monitor, I > use this in /etc/default/grub > > GRUB_GFXMODE=1680x1050 > GRUB_GFXPAYLOAD_LINUX=keep I ran vbeinfo in grub to list the available resolutions, and used the highest one shown. The result wasn't as nice as what I get with nouveau; maybe I didn't spend enough time configuring it, but I went through several iterations with various fonts. None of them looked particularly nice. > > Unfortunately I am affected by #575624 :( > > Regards, > Andrei -- Joe Riel -- 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/20110221074821.76123270@gauss
