Re: Problem with X when changing to console
Hi. I am not familiar with nvidia, but I believe you need KMS/DRM mode: (See modeset setting) https://download.nvidia.com/XFree86/Linux-x86_64/396.51/README/kms.html This was an idea behind the DRM/KMS: both Xorg and Framebuffer (graphical mode linux command line console) work on top of the driver. When crashed, does it write something to the console and/or logs? On Sun, Feb 14, 2021 at 10:01 PM Hans wrote: > Hi folks, > > since some months I am looking for an issue and I hope, someone might know > more and can help. > > The issue is the following: I am running plasma and Nvidia proprietrary > driver. When I change to a console with CTL+ALT+F1, and after some seconds > back with ALT+F7, then X has crashed. > > It looks for me, that the nvidia module was unloaded, and I am rather > sure, > that I made a setting in the past, where the nvidia module should be > unloaded, > when changing to a console. > > But the problem is: I can not remember any more, where I did this setting! > > Does anyone know, where this option can be set / unset? > > If this is a bug in the nvidia module (what I do not believe at the > moment, as > on my other computers this behaviour does not appear), please drop me a > note. > > Thank you for any help and stay healthy > > Best regards > > Hans > > >
Problem with X when changing to console
Hi folks, since some months I am looking for an issue and I hope, someone might know more and can help. The issue is the following: I am running plasma and Nvidia proprietrary driver. When I change to a console with CTL+ALT+F1, and after some seconds back with ALT+F7, then X has crashed. It looks for me, that the nvidia module was unloaded, and I am rather sure, that I made a setting in the past, where the nvidia module should be unloaded, when changing to a console. But the problem is: I can not remember any more, where I did this setting! Does anyone know, where this option can be set / unset? If this is a bug in the nvidia module (what I do not believe at the moment, as on my other computers this behaviour does not appear), please drop me a note. Thank you for any help and stay healthy Best regards Hans
[SOLVED] emacs problem: M-x write-abbrev-file does not seem to work.
On Thu, Mar 19, 2020 at 1:57 PM davidson wrote: > On Thu, 19 Mar 2020, davidson wrote: > > On Wed, 18 Mar 2020, Default User wrote: > [snip] > > >> dummy@dummy:~$ sudo aptitude show emacs > >> [sudo] password for default: > > > > Just FYI, it would greatly surprise me if you actually needed root > > privileges for aptitude's "show" command. I wager you could get the > > same information with > > > > dummy@dummy:~$ aptitude show emacs > > > > and save yourself a password entry. > > > > (I am wagering, not promising, because I use apt-get exclusively, > > *apt-get and apt-cache > > > never aptitude.) > [big snip] > > > Then, in emacs, do > > > > M-x info > > > > This brings up a menu of info documentation properly installed on your > > system. You'll want to traverse "Emacs" > "Abbrevs". > > I now see that GW Haywood has already pointed you to a version of the > same document, posted on the web: > > > https://lists.debian.org/msgid-search/alpine.deb.2.21.2003191433310.9...@piplus.local.jubileegroup.co.uk > > -- > The day will come | Last words, August Spies (1855--1887). > When our silence will be | Hanged, by the U.S. state of Illinois, > More powerful than | alongside fellow journalists > The voices you strangle today | Adolf Fischer and Albert Parsons. > Davidson, thank you for the link to the information. 1) Yes, "dummy@dummy:~$ aptitude show emacs" does work just fine. I guess I just got into the habit of using "sudo" more than I really need to. 2) The book is Second Edition (1996). Almost a quarter of a century old, but still quite useful, especially for a "mature" program like Emacs. 3) I do have "emacs-common-non-dfsg" installed, and do have "non-free" in my /etc/apt/sources.list. I do use "info" from time to time, but I more often use man pages, or just search online. 4) The problem has been SOLVED. I believe it was due to the insistence on Emacs on using ~/.emacs.d/abbrev_defs to store the saved abbreviations, instead of ~/.abbrev_defs as suggested in the book. I am guessing this is due to the change in recent years to using ".d" supplemental directories. The fix was to change a section of".emacs" from this (in the book): (setq-default abbrev-mode t) (read-abbrev-file "~/.abbrev_defs") (setq save-abbrevs t) to this: (setq-default abbrev-mode t) (setq save-abbrevs t) (setq abbrev-file-name "~/.emacs.d/abbrev_defs") ;; tell emacs where to read abbrev definitions from . . . ;; (read-abbrev-file "~/.emacs.d/abbrev_defs") This line may be obsolete [from "Learning GNU Emacs"] [Note: it seems to work either with or without (read-abbrev-file "~/.emacs.d/abbrev_defs") being commented out]. So now "M-x write-abbrev-file" does seem to save the edited abbreviations as it was supposed to all along. I had mentioned that it was possible to manually edit ~/.emacs.d/abbrev_defs to remove the entry, and then save ~/.emacs.d/abbrev_defs, as a work-around. But if I should be able "To delete any abbreviation, delete the line for that abbreviation and save the file by typing M-x write-abbrev-file.", then I should be able to do so. Anyway, problem solved. Thanks to all for the help.
Re: emacs problem: M-x write-abbrev-file
On Thu, Mar 19, 2020 at 10:54 AM G.W. Haywood < debian-b...@jubileegroup.co.uk> wrote: > Hi there, > > On Thu, 19 Mar 2020, Default User wrote: > > > I'm trying to learn Emacs, using: > > "Learning GNU Emacs". > > Old, but it would still seem to be a reputable and authoritative source. > > Well I used to use that book, but that was 25 years ago. Try this instead: > > > https://www.gnu.org/software/emacs/manual/html_node/emacs/Abbrevs.html#Abbrevs > > -- > > 73, > Ged. > G.W., thanks for the link you provided to the Emacs information at GNU.org. I'm sure it will be quite helpful over time.
Re: emacs problem: M-x write-abbrev-file does not seem to work.
On Thu, 19 Mar 2020, davidson wrote: On Wed, 18 Mar 2020, Default User wrote: [snip] dummy@dummy:~$ sudo aptitude show emacs [sudo] password for default: Just FYI, it would greatly surprise me if you actually needed root privileges for aptitude's "show" command. I wager you could get the same information with dummy@dummy:~$ aptitude show emacs and save yourself a password entry. (I am wagering, not promising, because I use apt-get exclusively, *apt-get and apt-cache never aptitude.) [big snip] Then, in emacs, do M-x info This brings up a menu of info documentation properly installed on your system. You'll want to traverse "Emacs" > "Abbrevs". I now see that GW Haywood has already pointed you to a version of the same document, posted on the web: https://lists.debian.org/msgid-search/alpine.deb.2.21.2003191433310.9...@piplus.local.jubileegroup.co.uk -- The day will come | Last words, August Spies (1855--1887). When our silence will be | Hanged, by the U.S. state of Illinois, More powerful than | alongside fellow journalists The voices you strangle today | Adolf Fischer and Albert Parsons.
Re: emacs problem: M-x write-abbrev-file does not seem to work.
On Wed, 18 Mar 2020, Default User wrote: Hey, been working on this emacs problem all day. It would have taken me all day just to write up such a meticulous account. TLDR; I have never used the "abbrevs" functionality of emacs. So, (fair warning) you will not find a direct answer to your question in what I say below. I'm running Unstable, up to date. Cinnamon DE. 64-bit. dummy@dummy:~$ sudo aptitude show emacs [sudo] password for default: Just FYI, it would greatly surprise me if you actually needed root privileges for aptitude's "show" command. I wager you could get the same information with dummy@dummy:~$ aptitude show emacs and save yourself a password entry. (I am wagering, not promising, because I use apt-get exclusively, never aptitude.) Package: emacs Version: 1:26.3+1-1 [snip] I'm trying to learn Emacs, using: "Learning GNU Emacs". Old, but it would still seem to be a reputable and authoritative source. I am sympathetic to reading older, slightly out-of-date sources of documentation. I frequently do it myself. So I know that it can be informative (sometimes in unexpected ways), and I know that at times it has downsides as well, can add an extra layer of confusion, etc. That said, if I were you, and if I had not done so already, I would enable the non-free component in your sources.list, and then install the (non-free) package "emacs-common-non-dfsg": | emacs-common-non-dfsg - GNU Emacs common non-DFSG items, including the core documentation | This package includes the core Emacs documentation: the Emacs Info | pages, the Emacs Lisp Reference Manual, and the Emacs Lisp Intro. | . | GNU Emacs is the extensible self-documenting text editor. This | package contains the architecture independent infrastructure that | is not compliant with the Debian Free Software Guidelines. In | particular, this includes some of the GNU Emacs info pages, as they | are covered under the GFDL, and specify invariant sections. See | http://www.debian.org/vote/2006/vote_001 for more information. This should give you the info pages version of the Emacs manual, which contains a section on Abbrevs (under Advanced Features, I think). Then, in emacs, do M-x info This brings up a menu of info documentation properly installed on your system. You'll want to traverse "Emacs" > "Abbrevs". What little else I have to say would merely be bikeshedding or poorly-informed speculation, so I'll stop here. Maybe I'll go read about Abbrevs. I hope this helps a little, while you're waiting for an emacs wizard to show up. Good luck with your project. -- The day will come | Last words, August Spies (1855--1887). When our silence will be | Hanged, by the U.S. state of Illinois, More powerful than | alongside fellow journalists The voices you strangle today | Adolf Fischer and Albert Parsons.
Re: emacs problem: M-x write-abbrev-file
Hi there, On Thu, 19 Mar 2020, Default User wrote: I'm trying to learn Emacs, using: "Learning GNU Emacs". Old, but it would still seem to be a reputable and authoritative source. Well I used to use that book, but that was 25 years ago. Try this instead: https://www.gnu.org/software/emacs/manual/html_node/emacs/Abbrevs.html#Abbrevs -- 73, Ged.
emacs problem: M-x write-abbrev-file does not seem to work.
Hey, been working on this emacs problem all day. I'm running Unstable, up to date. Cinnamon DE. 64-bit. dummy@dummy:~$ sudo aptitude show emacs [sudo] password for default: Package: emacs Version: 1:26.3+1-1 New: yes State: installed Automatically installed: no Priority: optional Section: editors Maintainer: Rob Browning Architecture: all Uncompressed Size: 76.8 k Depends: emacs-gtk (>= 1:26.3) | emacs-lucid (>= 1:26.3) | emacs-nox (>= 1:26.3) Provided by: emacs-gtk (1:26.3+1-1), emacs-lucid (1:26.3+1-1), emacs-nox (1:26.3+1-1) Description: GNU Emacs editor (metapackage) GNU Emacs is the extensible self-documenting text editor. This is a metapackage that will always depend on the latest recommended Emacs variant (currently emacs-gtk). Homepage: https://www.gnu.org/software/emacs/ Tags: devel::editor, role::dummy, role::metapackage, role::program, suite::emacs, suite::gnu, use::editing I'm trying to learn Emacs, using: "Learning GNU Emacs". Old, but it would still seem to be a reputable and authoritative source. It says edit .emacs thus: (setq-default abbrev-mode t) (read-abbrev-file "~/.abbrev_defs") (setq save-abbrevs t) Emacs does NOT like that. It wants the read-abbrev-file to be in emacs.d instead, and not a hidden file, so: dummy@dummy:~$ ls ~/.emacs.d/abbrev_defs -rw-r--r-- 1 dummy dummy 1020 Mar 18 16:38 /home/dummy/.emacs.d/abbrev_defs and .emacs is like this: dummy@dummy:~$ cat ~/.emacs (custom-set-variables ;; custom-set-variables was added by Custom. ;; If you edit it by hand, you could mess it up, so be careful. ;; Your init file should contain only one such instance. ;; If there is more than one, they won't work right. '(ansi-color-faces-vector [default default default italic underline success warning error]) '(ansi-color-names-vector ["black" "red3" "ForestGreen" "yellow3" "blue" "magenta3" "DeepSkyBlue" "gray50"]) '(column-number-mode t) '(custom-enabled-themes (quote (whiteboard))) '(display-time-mode t) '(save-place-mode t) '(size-indication-mode t)) (custom-set-faces ;; custom-set-faces was added by Custom. ;; If you edit it by hand, you could mess it up, so be careful. ;; Your init file should contain only one such instance. ;; If there is more than one, they won't work right. '(default ((t (:family "DejaVu Sans" :foundry "PfEd" :slant normal :weight normal :height 181 :width normal) ;; insert date and time (defvar current-date-time-format "%Y-%m-%d %H:%M:%S %Z (%a)" "Format of date to insert with `insert-current-date-time' func See help of `format-time-string' for possible replacements") (defvar current-time-format "%H:%M:%S (%a)" "Format of date to insert with `insert-current-time' func. Note the weekly scope of the command's precision.") (defun insert-current-date-time () "insert the current date and time into current buffer. Uses `current-date-time-format' for the formatting the date/time." (interactive) (insert (format-time-string current-date-time-format (current-time))) (insert "\n\n") ) (defun insert-current-time () "insert the current time (1-week scope) into the current buffer." (interactive) (insert (format-time-string current-time-format (current-time))) (insert "\n\n") ) (global-set-key "\C-c\C-d" 'insert-current-date-time) (global-set-key "\C-c\C-t" 'insert-current-time) ;; customizations manually added by me: (setq column-number-indicator-zero-based nil) (setq default-major-mode 'text-mode) (add-hook 'text-mode-hook 'turn-on-auto-fill) (setq-default fill-column 79) (setq-default flyspell-mode t) (setq-default abbrev-mode t) (read-abbrev-file "~/.emacs.d/abbrev_defs") (setq save-abbrevs t) I re-start emacs in abbrev-mode (with .emacs, as above). Now add a word abbreviation: C-x a i g [Enter] teh [Enter] the [Enter] C-x C-c Emacs saves it in ~/.emacs.d/abbrev_defs (not ~/.abbrev_defs, as shown in book.) Re-start emacs. It loads the word abbreviation from ~/.emacs.d/abbrev_defs, and it works as expected. BUT, now to REMOVE the word abbreviation from ~/.emacs.d/abbrev_defs . . . The book says: "You can edit the word abbreviation list by typing M-x edit-abbrevs [Enter]". Then (the book says): "To delete any abbreviation, delete the line for that abbreviation and save the file by typing M-x write-abbrev-file." So, do: M-x edit-abbrevs [Enter] then delete the entry in question, then do: M-x write-abbrev-file It prompts with: "Write abbrev file: ~/.emacs.d/" At the prompt, I add "abbrev_defs" like this: "Write abbrev file: ~/.emacs.d/abbrev_defs" [Enter]. The prompt disappears, no error message. Good. Then do: C-x b to switch to default buffer. Then do: C-x C-c to exit emacs. Now re-enter Emacs. THE WORD ABBREVIATION I ENTERED STILL WORKS! IT WAS NEVER REMOVED FROM ~/.emacs.d/abbrev_defs! (Yes, I am shouting. After spending much of the day fighting with this, I am not happy.) Note: I can edit ~/.emacs.d/abbrev_defs, remove the entry, and
Re: Dell Inspiron 17 3000 Series 3785 problem with X
Received from ernst on Wed, 14 Aug 2019 09:10:55 -0400 Re: Dell Inspiron 17 3000 Series 3785 problem with X > On Wed, 2019-08-14 at 14:20 +0200, to...@tuxteam.de wrote: > > On Wed, Aug 14, 2019 at 08:11:34AM -0400, ernst doubt wrote: > > > Hi all, > > > > > > i had sent a message to debian-laptop a few hours back, but all > > > i've > > > seen so far is one response (suggesting i use q4os). i'm pretty > > > committed to using debian directly though (at least until i've > > > tried an > > > awful lot more things). > > > > > > After installing buster, this brand new laptop of mine seems to > > > hang on > > > X (GDM) starting -- after briefly showing a flashing underscore > > > char in > > > the top left corner of the screen, it drops back to command-line > > > output > > > (but doesn't allow me to login). > > > > [...] > > > > It seems that your X server is giving up for some reason. > > > > Not a graphics expert here, but you may get some hints by inpecting > > the X log file (called typically Xorg.0.log -- it usually lives in > > /var/log or perhaps in your home directory. Towards the end, you > > might find some lines tagged with (EE) -- those are errors. > > > > The content of that file might be of help to folks around here to > > diagnose your problem. > > > > Cheers > > -- tomás > > > Thanks for all the help folks. i managed to solve it on my own. Pretty > sure it was the linux-firmware-nonfree package that did it. > > best, > ~e I stayed away from AMD Ryzen™ 5 2500U Mobile Processor with Radeon after what I read about it, but did get a laptop with AMD graphics. Probably will never do that again, Installed Buster as legacy when it would not install EFI. Required all these to to have it stop locking up: firmware-linux firmware-linux-nonfree libdrm-amdgpu1 xserver-xorg-video-amdgpu llvm Found them in various discussions and information on the web. Maybe that will help someone else. Charlie East Gippsland Wildlife Rehabilitators Inc.. http://www.egwildlife.com.au/ -- Registered Linux User:- 329524 *** From error to error one discovers the entire truth. ---Sigmund Freud *** Debian GNU/Linux - Magic indeed. -
Re: Dell Inspiron 17 3000 Series 3785 problem with X
On Wed, 2019-08-14 at 14:20 +0200, to...@tuxteam.de wrote: > On Wed, Aug 14, 2019 at 08:11:34AM -0400, ernst doubt wrote: > > Hi all, > > > > i had sent a message to debian-laptop a few hours back, but all > > i've > > seen so far is one response (suggesting i use q4os). i'm pretty > > committed to using debian directly though (at least until i've > > tried an > > awful lot more things). > > > > After installing buster, this brand new laptop of mine seems to > > hang on > > X (GDM) starting -- after briefly showing a flashing underscore > > char in > > the top left corner of the screen, it drops back to command-line > > output > > (but doesn't allow me to login). > > [...] > > It seems that your X server is giving up for some reason. > > Not a graphics expert here, but you may get some hints by inpecting > the X log file (called typically Xorg.0.log -- it usually lives in > /var/log or perhaps in your home directory. Towards the end, you > might find some lines tagged with (EE) -- those are errors. > > The content of that file might be of help to folks around here to > diagnose your problem. > > Cheers > -- tomás Thanks for all the help folks. i managed to solve it on my own. Pretty sure it was the linux-firmware-nonfree package that did it. best, ~e
Re: Dell Inspiron 17 3000 Series 3785 problem with X
ernst doubt wrote: > After installing buster, this brand new laptop of mine seems to hang on > X (GDM) starting -- after briefly showing a flashing underscore char in > the top left corner of the screen, it drops back to command-line output > (but doesn't allow me to login). > > i'm booted into recovery mode right now and i've managed to get > networking up and running (and installed emacs-nox and gpm, yay!) and > i'm looking through /var/log/daemon.log from my failed boot last night. > > My assumption is that there's probably some non-free firmware package i > need to install (and maybe configure?) > > 20 years ago or so i remember fighting with modelines entries in order > to get X working, but i imagine things have changed. > > This machine purportedly has: > AMD Ryzen™ 5 2500U Mobile Processor with Radeon™ Vega 8 Graphics This needs the amdgpu server: xserver-xorg-video-amdgpu and firmware-amd-graphics and a reboot. The primary log file for this should be /var/log/Xorg.0.log -- look for complaints there. It should explicitly recognize your video chipset as an AMD Vega system and then produce lots of output with the amdgpu prefix. If it doesn't, Xorg isn't firing up the right driver and you may need to specify it. -dsr-
Re: Dell Inspiron 17 3000 Series 3785 problem with X
On Wed, Aug 14, 2019 at 08:11:34AM -0400, ernst doubt wrote: > Hi all, > > i had sent a message to debian-laptop a few hours back, but all i've > seen so far is one response (suggesting i use q4os). i'm pretty > committed to using debian directly though (at least until i've tried an > awful lot more things). > > After installing buster, this brand new laptop of mine seems to hang on > X (GDM) starting -- after briefly showing a flashing underscore char in > the top left corner of the screen, it drops back to command-line output > (but doesn't allow me to login). [...] It seems that your X server is giving up for some reason. Not a graphics expert here, but you may get some hints by inpecting the X log file (called typically Xorg.0.log -- it usually lives in /var/log or perhaps in your home directory. Towards the end, you might find some lines tagged with (EE) -- those are errors. The content of that file might be of help to folks around here to diagnose your problem. Cheers -- tomás signature.asc Description: Digital signature
Dell Inspiron 17 3000 Series 3785 problem with X
Hi all, i had sent a message to debian-laptop a few hours back, but all i've seen so far is one response (suggesting i use q4os). i'm pretty committed to using debian directly though (at least until i've tried an awful lot more things). After installing buster, this brand new laptop of mine seems to hang on X (GDM) starting -- after briefly showing a flashing underscore char in the top left corner of the screen, it drops back to command-line output (but doesn't allow me to login). i'm booted into recovery mode right now and i've managed to get networking up and running (and installed emacs-nox and gpm, yay!) and i'm looking through /var/log/daemon.log from my failed boot last night. My assumption is that there's probably some non-free firmware package i need to install (and maybe configure?) 20 years ago or so i remember fighting with modelines entries in order to get X working, but i imagine things have changed. This machine purportedly has: AMD Ryzen™ 5 2500U Mobile Processor with Radeon™ Vega 8 Graphics If anyone has any suggestions or hints about how to proceed with troubleshooting, i'm happy to share log files, chase down documentation, install packages, edit configuration files or whatever else is needed. i could also burn an ubuntu disk and boot that live to see what i could learn from that experience (a web search seems to indicate ubuntu would install fine on this laptop, but my preference is to stick with debian). thanks so much in advance, ~e
Problem with X or kdm
Hi there. After upgrading to debian jessie happens to me, that instead of X me shining black screen,after switching back from console, and will help only restart kdm. Along with this there is some other problem. When I log into X s, below my username I unsubscribe and thus starts kdm login dialog, but if subsequently known son, or another user, and logs are on, a black screen, but it radiates as if kdm underneath was because when moving the mouse arrow cursor changes to a text cursor in locations where potentially could be fields for a user name and password. nothing in the logs. Only in kdm.log any mention of that dbus is not working. But apparently dbus running. I running on a Debian Jessie and notebook Acer Extensa with GC with Radeon chipset. Met you by chance someone with such behavior? On internet I found nothing. I deleted the other users .kde directories. Them where to log in to the system created a new, but no change. I don't know where is problem. Thank's for help. Rony -- 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/8910830ea673c9738bc0d62ad58d4...@nethouse.sk
Re: Problem with X or kdm
On 08/19/2013 01:25 PM, Ronald Púpala wrote: Hi there. After upgrading to debian jessie happens to me, that instead of X me shining black screen,after switching back from console, and will help only restart kdm. Along with this there is some other problem. When I log into X s, below my username I unsubscribe and thus starts kdm login dialog, but if subsequently known son, or another user, and logs are on, a black screen, but it radiates as if kdm underneath was because when moving the mouse arrow cursor changes to a text cursor in locations where potentially could be fields for a user name and password. nothing in the logs. Only in kdm.log any mention of that dbus is not working. But apparently dbus running. I running on a Debian Jessie and notebook Acer Extensa with GC with Radeon chipset. Met you by chance someone with such behavior? On internet I found nothing. I deleted the other users .kde directories. Them where to log in to the system created a new, but no change. I don't know where is problem. Thank's for help. Rony I recently had some major KDE breakage; I finally fired up aptitude and did a search for kde (n for next instance; visually scan for a bold entry indicating an installed package, page down, n, repeat), deleting anything that looked KDE-ish. Then did an aptitude update followed by an aptitude dist-upgrade, then did an aptitude install task-kde-desktop, and now have a working KDE again, although it looks considerably different to what I had previously. (Oh, in the process, I added unstable to my apt sources; I already had testing.) I say all this to saythat I suspect there's some major KDE changes that don't always go well on an upgrade. You can start a different Desktop Environment (DE) or Window Manager (WM) just to make sure X itself is working properly(and to give you a GUI, if you're more comfortable in that environment). As always, your mileage may vary. -- Kent West *))) http://kentwest.blogspot.com Praise Yah! \o/ -- 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/52126c22.7000...@acu.edu
Problem with X
Hi, I try start X on my computer but when i type startx screen freezes. I can see desktop but I can't move mouse cursor nor use keyboard. First I installed basic debian system, then I installed xfce4. lspci: 00:00.0 Host bridge: VIA Technologies, Inc. P4M800 Host Bridge 00:00.1 Host bridge: VIA Technologies, Inc. P4M800 Host Bridge 00:00.2 Host bridge: VIA Technologies, Inc. P4M800 Host Bridge 00:00.3 Host bridge: VIA Technologies, Inc. P4M800 Host Bridge 00:00.4 Host bridge: VIA Technologies, Inc. P4M800 Host Bridge 00:00.7 Host bridge: VIA Technologies, Inc. P4M800 Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge 00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) 00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) 00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) 00:10.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South] 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60) 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78) 01:00.0 VGA compatible controller: VIA Technologies, Inc. KM400/KN400/P4M800 [S3 UniChrome] (rev 01) X -configure: X.Org X Server 1.10.1 Release Date: 2011-04-15 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-5-amd64 x86_64 Debian Current Operating System: Linux junior 2.6.38-2-amd64 #1 SMP Sun May 8 13:51:57 UTC 2011 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-2-amd64 root=UUID=28e5a1cb-af9d-4b03-bff6-c17ce707a6ce ro quiet Build Date: 28 April 2011 12:13:00PM xorg-server 2:1.10.1-2 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.21.8 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed May 18 15:03:07 2011 List of video drivers: radeon i128 nouveau intel vmwlegacy mga r128 s3 openchrome savage trident neomagic vmware mach64 cirrus ati tdfx sis ark chips rendition tseng s3virge voodoo sisusb apm siliconmotion fbdev vesa (EE) Failed to load module vmwgfx (module does not exist, 0) (EE) vmware: Please ignore the above warnings about not being able to to load module/driver vmwgfx (EE) vmware: Unexpected failure while loading the vmwlegacy driver. Giving up. (EE) Failed to load module vmware (a required submodule could not be loaded, 0) (++) Using config file: /root/xorg.conf.new (==) Using system config directory /usr/share/X11/xorg.conf.d (EE) open /dev/fb0: No such file or directory Number of created screens does not match number of detected devices. Configuration failed. It create xorg.conf.new xorg.conf.new file: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 Screen 1 Screen1 RightOf Screen0 Screen 2 Screen2 RightOf Screen1 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files ModulePath /usr/lib/xorg/modules FontPath /usr/share/fonts/X11/misc FontPath /usr/share/fonts/X11/cyrillic FontPath /usr/share/fonts/X11/100dpi/:unscaled FontPath /usr/share/fonts/X11/75dpi/:unscaled FontPath /usr/share/fonts/X11/Type1 FontPath /usr/share/fonts/X11/100dpi FontPath /usr/share/fonts/X11/75dpi FontPath /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType FontPath built-ins EndSection Section Module Load glx Load dri2 Load extmod Load record Load dbe Load dri EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse OptionProtocol auto OptionDevice /dev/input/mice OptionZAxisMapping 4 5 6 7 EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model EndSection Section Monitor Identifier Monitor1 VendorName Monitor Vendor ModelNameMonitor Model EndSection Section Monitor Identifier Monitor2 VendorName Monitor Vendor ModelNameMonitor Model EndSection Section Device
Re: Problem with X
Hi! Do you get a message during boot that udev failed to start? If so, try to delete /run and it should fix the problem. Best regards, Florian -- 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/8e9f2741ca6978f733a31e8918eea933-EhVaXlhEQB8JBgYCAQQGZx8aNEQGDggdMB8QRjBSWV5aVl8WXlx2H1dTMl5bQFsDXERcQEZUXA8wXnUBUFBYVl9GQQ==-webmail...@server02.webmailer.hosteurope.de
Re: Problem with X
On Mon, May 16, 2011 at 04:13:44PM +0100, pch0317 wrote: I try start X on my computer but when i type startx screen freezes. I can see desktop but I can't move mouse cursor nor use keyboard. First I installed basic debian system, then I installed xfce4. It's possibly an issue with udev not triggering initialisation of the input devices or some other device needed by X. Try restarting udev and checking the system logs. You might want to check your system is up to date. If it's unstable, check if you have a /run directory and that you're using the latest initscripts (2.88dsf-13.6), initramfs-tools (0.99) and udev. There was an issue with udev and /run a few weeks ago which could break X in this manner. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. signature.asc Description: Digital signature
Re: Problem with X
On Mon, May 16, 2011 at 05:17:54PM +0200, Florian Snow wrote: Do you get a message during boot that udev failed to start? If so, try to delete /run and it should fix the problem. Now that /run is created and used by all system services, deleting it is no longer advisable. If you're using initscripts 2.88dsf-13.6 (now in unstable), /run is mandatory since it replaces /var/run and /var/lock and is used by udev in early boot. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. signature.asc Description: Digital signature
Re: Problem with X
On Mon, 16 May 2011 16:13:44 +0100, pch0317 wrote: I try start X on my computer but when i type startx screen freezes. I can see desktop but I can't move mouse cursor nor use keyboard. First I installed basic debian system, then I installed xfce4. (...) (EE) Failed to load module vmwgfx (module does not exist, 0) (EE) vmware: Please ignore the above warnings about not being able to to load module/driver vmwgfx (EE) vmware: Unexpected failure while loading the vmwlegacy driver. Giving up. (EE) Failed to load module vmware (a required submodule could not be loaded, 0) Hum... It warns you about a missing module related to the VGA driver of the vmware guest, is that right? :-? In VirtualBox's guest additions this usually means that you updated the kernel on the client and did not recompiled the VGA module for the guest. Greetings, -- Camaleón -- 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/pan.2011.05.16.18.27...@gmail.com
Re: Problem z X-ami
On Sat, Aug 01, 2009 at 05:54:34PM +0200, maciek...@interia.pl wrote: Mój problem jest następujący. Gdy używam trybu graficznego (gnome) mając skonfigurowane połączenie z Internetem i nagle tracę to połączenie (np wywala się domyślna brama) to wówczas wszystkie aplikacje mulą mi niemiłosiernie, a dokładniej strasznie długo się odpalają, tak jakby mój komp najpierw chciał coś zrobić w sieci a potem dopiero uruchamia mi aplikację. Prawdopodobnie chodzi o DNS. Co masz w /etc/hosts i /etc/hostname? Z tego co mi się wydaje to serwer X używa adresu 127.0.0.1 a ten przecież mam cały czas dostępny. Lokalne aplikacje powinny raczej korzystać z gniazda rodziny UNIX, a nie TCP/IP, więc to raczej nie jest kwestia X serwera. -- Marcin Owsiany porri...@debian.org http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 -- To UNSUBSCRIBE, email to debian-user-polish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Problem z X-ami
On Wed, 5 Aug 2009 08:59:38 +0100 Marcin Owsiany porri...@debian.org wrote: On Sat, Aug 01, 2009 at 05:54:34PM +0200, maciek...@interia.pl wrote: Mój problem jest następujący. Gdy używam trybu graficznego (gnome) mając skonfigurowane połączenie z Internetem i nagle tracę to połączenie (np wywala się domyślna brama) to wówczas wszystkie aplikacje mulą mi niemiłosiernie, a dokładniej strasznie długo się odpalają, tak jakby mój komp najpierw chciał coś zrobić w sieci a potem dopiero uruchamia mi aplikację. Prawdopodobnie chodzi o DNS. Co masz w /etc/hosts i /etc/hostname? /etc/hosts 127.0.0.1 localhost laptop.local www.laptop.local mnm.laptop.local /etc/hostname laptop Z tego co mi się wydaje to serwer X używa adresu 127.0.0.1 a ten przecież mam cały czas dostępny. Lokalne aplikacje powinny raczej korzystać z gniazda rodziny UNIX, a nie TCP/IP, więc to raczej nie jest kwestia X serwera. no tylko gdzie szukać przyczyny jak przejdę do konsoli (np Ctrl + Alt + F1) wszystko jest ok (tam oczywiście nie uruchamiam programów graficznych :) ) jak wyłączę interfejs sieciowy też wszystko śmiga (włącznie z programami graficznymi) -- Marcin Owsiany porri...@debian.org http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 -- To UNSUBSCRIBE, email to debian-user-polish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- maciek...@interia.pl -- Zostan Dziewczyna lub Chlopakiem lata! Wygraj skuter http://link.interia.pl/f22a7 -- To UNSUBSCRIBE, email to debian-user-polish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Problem z X-ami
Dnia 2009-08-05, o godz. 13:00:42 maciek...@interia.pl napisał(a): On Wed, 5 Aug 2009 08:59:38 +0100 Marcin Owsiany porri...@debian.org wrote: On Sat, Aug 01, 2009 at 05:54:34PM +0200, maciek...@interia.pl wrote: Mój problem jest następujący. Gdy używam trybu graficznego (gnome) mając skonfigurowane połączenie z Internetem i nagle tracę to połączenie (np wywala się domyślna brama) to wówczas wszystkie aplikacje mulą mi niemiłosiernie, a dokładniej strasznie długo się odpalają, tak jakby mój komp najpierw chciał coś zrobić w sieci a potem dopiero uruchamia mi aplikację. Prawdopodobnie chodzi o DNS. Co masz w /etc/hosts i /etc/hostname? /etc/hosts 127.0.0.1 localhost laptop.local www.laptop.local mnm.laptop.local Zobacz czy zmiania powyższej linijki na taką: 127.0.0.1 localhost laptop.local laptop www.laptop.local mnm.laptop.local rozwiązuje Twój problem. /etc/hostname laptop -- Krzysztof Kaczmar -- To UNSUBSCRIBE, email to debian-user-polish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Problem z X-ami
On Wed, Aug 05, 2009 at 01:00:42PM +0200, maciek...@interia.pl wrote: On Wed, 5 Aug 2009 08:59:38 +0100 Marcin Owsiany porri...@debian.org wrote: On Sat, Aug 01, 2009 at 05:54:34PM +0200, maciek...@interia.pl wrote: Mój problem jest następujący. Gdy używam trybu graficznego (gnome) mając skonfigurowane połączenie z Internetem i nagle tracę to połączenie (np wywala się domyślna brama) to wówczas wszystkie aplikacje mulą mi niemiłosiernie, a dokładniej strasznie długo się odpalają, tak jakby mój komp najpierw chciał coś zrobić w sieci a potem dopiero uruchamia mi aplikację. Prawdopodobnie chodzi o DNS. Co masz w /etc/hosts i /etc/hostname? /etc/hosts 127.0.0.1 localhost laptop.local www.laptop.local mnm.laptop.local /etc/hostname laptop W takim razie spróbuj dorzucić samo laptop do tej linijki w /etc/hosts Z tego co mi się wydaje to serwer X używa adresu 127.0.0.1 a ten przecież mam cały czas dostępny. Lokalne aplikacje powinny raczej korzystać z gniazda rodziny UNIX, a nie TCP/IP, więc to raczej nie jest kwestia X serwera. no tylko gdzie szukać przyczyny jak przejdę do konsoli Chyba brakło Ci tutaj jakiegoś znaku przestankowego :P Do wyczajania takich rzeczy polecam strace. -- Marcin Owsiany porri...@debian.org http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 -- To UNSUBSCRIBE, email to debian-user-polish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Problem z X-ami
On Wed, 5 Aug 2009 13:30:24 +0200 Krzysztof Kaczmar arr...@o2.pl wrote: Dnia 2009-08-05, o godz. 13:00:42 maciek...@interia.pl napisał(a): On Wed, 5 Aug 2009 08:59:38 +0100 Marcin Owsiany porri...@debian.org wrote: On Sat, Aug 01, 2009 at 05:54:34PM +0200, maciek...@interia.pl wrote: Mój problem jest następujący. Gdy używam trybu graficznego (gnome) mając skonfigurowane połączenie z Internetem i nagle tracę to połączenie (np wywala się domyślna brama) to wówczas wszystkie aplikacje mulą mi niemiłosiernie, a dokładniej strasznie długo się odpalają, tak jakby mój komp najpierw chciał coś zrobić w sieci a potem dopiero uruchamia mi aplikację. Prawdopodobnie chodzi o DNS. Co masz w /etc/hosts i /etc/hostname? /etc/hosts 127.0.0.1 localhost laptop.local www.laptop.local mnm.laptop.local Zobacz czy zmiania powyższej linijki na taką: 127.0.0.1 localhost laptop.local laptop www.laptop.local mnm.laptop.local rozwiązuje Twój problem. Po dopisaniu laptop do /etc/hosts chodzi super. Dzięki za pomoc. Więc jednak TCP/IP a nie gniazda ? Ktoś może coś jeszcze na ten temat napisać ? /etc/hostname laptop -- Krzysztof Kaczmar -- To UNSUBSCRIBE, email to debian-user-polish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- maciek...@interia.pl -- Czy odnajde prawdziwa milosc? Zapytaj wrozke http://link.interia.pl/f22ae -- To UNSUBSCRIBE, email to debian-user-polish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Problem z X-ami
W dniu 5 sierpnia 2009 13:42 użytkownik maciek...@interia.pl napisał: 127.0.0.1 localhost laptop.local laptop www.laptop.local mnm.laptop.local rozwiązuje Twój problem. Po dopisaniu laptop do /etc/hosts chodzi super. Dzięki za pomoc. Więc jednak TCP/IP a nie gniazda ? Ktoś może coś jeszcze na ten temat napisać ? /etc/hostname laptop Przerabiałem problem z Xami i /etc/hosts bardzo dawno temu, i z tego co pamietam to serwer Xów uzywa warstwy sieciowej do wewnetrzej komunikacji uzywajac glownie hostname'a ktorego wpisales podczas instalacji. Jesli potem grzebales w /etc/hosts to system natrafia na nieresolvowalne nazwy i czeka 30s na przetlumaczenie. Po 30s wraca do starego dobrego home sweet home czyli 127.0.0.1;) pozdr. -- Wojciech Ziniewicz http://rfc.sunsite.dk/rfc/rfc2324.html
Problem z X-ami
Witam. Mój problem jest następujący. Gdy używam trybu graficznego (gnome) mając skonfigurowane połączenie z Internetem i nagle tracę to połączenie (np wywala się domyślna brama) to wówczas wszystkie aplikacje mulą mi niemiłosiernie, a dokładniej strasznie długo się odpalają, tak jakby mój komp najpierw chciał coś zrobić w sieci a potem dopiero uruchamia mi aplikację. Z tego co mi się wydaje to serwer X używa adresu 127.0.0.1 a ten przecież mam cały czas dostępny. Podobna sytuacja ma miejsce gdy używam iplusa (wysokie pingi) wtedy też wszysto się muli przy odpalaniu. Miał ktoś podobną sytuację ? w PLD tego nie miałem Może jakiś konfigurator używa zamiast 127.0.0.1 jakiego innego adresu. Pozdrawiam -- maciek...@interia.pl -- Zostan Dziewczyna lub Chlopakiem lata! Wygraj skuter http://link.interia.pl/f22a7 -- To UNSUBSCRIBE, email to debian-user-polish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: keyboard mapping problem under X
Jan Willem Stumpel wrote: Andrei Popescu wrote: changing /etc/default/console-setup should be enough, xorg.conf is ignored. Aah.. That explains it. Restart hal, at least in theory. Yes, in theory. In practice it may be different. I restarted it by means of /etc/init.d/hal restart, and got some weird results. It is also possible to make X ignore evdev altogether by setting in the ServerFlags section of xorg.conf: Option AutoAddDevices off Then you get the old behaviour back. xorg.conf again determines what is going on. Of course without the benefits of evdev. But I do not know what these benefits are anyway, so I do not miss them! In theory, again. I added the 'Option AutoAddDevices off' but the odd behavior of 2 arrow keys not repeating never ceased. The latest X is a mess for my purposes: http://bugs.debian.org/525736 Hugo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Re: keyboard mapping problem under X
Andrei Popescu wrote: changing /etc/default/console-setup should be enough, xorg.conf is ignored. Aah.. That explains it. Restart hal, at least in theory. Yes, in theory. In practice it may be different. I restarted it by means of /etc/init.d/hal restart, and got some weird results. It is also possible to make X ignore evdev altogether by setting in the ServerFlags section of xorg.conf: Option AutoAddDevices off Then you get the old behaviour back. xorg.conf again determines what is going on. Of course without the benefits of evdev. But I do not know what these benefits are anyway, so I do not miss them! Regards, Jan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Re: keyboard mapping problem under X
On Sat,23.May.09, 13:37:00, Jan Willem Stumpel wrote: Restart hal, at least in theory. Yes, in theory. In practice it may be different. I restarted it by means of /etc/init.d/hal restart, and got some weird results. Yes, that's why I said in theory. You did restart X after restarting hal, did you? I hope these quirks get solved until squeeze is released. It is also possible to make X ignore evdev altogether by setting in the ServerFlags section of xorg.conf: Option AutoAddDevices off Then you get the old behaviour back. xorg.conf again determines what is going on. Of course without the benefits of evdev. But I do not know what these benefits are anyway, so I do not miss them! Having only one place to configure all inputs and having a clean way to configure each individual input (my laptop has both a trackpoint and a touchpad and sometimes I use an external mouse). Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: keyboard mapping problem under X
- Jan Willem Stumpel jstum...@planet.nl a écrit : i use, whilst living in France, a german keyboard... You take the trouble to mention this: any special reason? For instance, do you want to type mostly French on a German keyboard? exactly! and if you ask why: the french layout is completely out of my taste... KDE or Gnome have GUI utilities that will make the keyboard do what you want (i.e. without directly editing system files). Probably in something called System, Keyboard. well my students call me dino... all that graphical stuff isn't really what i fancy, even if iy have to admit that having X running, that allows an impressive number of shells to be opened at the same moment and visible (still use screen though :D) and if i see how much ram that stuff takes that isn't then available to my numerical simulations If (like me) you want to avoid using KDE/Gnome, you can *also* make the keyboard do what you want. The German keyboard is called de. It has several so-called variants: i tried that in the xorg.conf without result setxkbmap de [-variant name of variant] heh, never too old to learn new stuff! that did it! and that's awesome! i directly integrated it into my bashrc that does bypass all those automatisms that don't seem to work at the moment! thanks a lot! You can use the setxkbmap command to experiment with keyboard layouts and variants. Once you have selected what you want, you can put it in /etc/X11/xorg.conf, in the keyboard section, in a slightly different format, using one line for the keyboard and another for the variant, e.g.: Option XkbLayout de Option XkbVariant deadgraveacute well that's the stuff i tryed and that didn't work... here's the section i tryed: Section InputDevice Identifier Generic Keyboard Driver kbd Option XkbRules xorg Option XkbModel pc105 Option XkbLayout de Option XkbOptionsctrl:nocaps EndSection kbd is still on nodeadkeys... but with the solution of setxkbdmap it works fine! -- ciao bboett == bbo...@adlp.org http://bboett.free.fr -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: keyboard mapping problem under X
Bruno Boettcher wrote: kbd is still on nodeadkeys... It appears that the keyboard system in X has changed. There is now something new and mysterious called evdev. To see if you have a system with evdev, type setxkbmap -print and see if evdev is mentioned. If it is, it seems that at the moment, to change the behaviour of the keyboard, you must specify things not only in etc/X11/xorg.conf, but *also* in /etc/default/console-setup. And then you must reboot! Stopping and restarting X is NOT enough. (There must be a better way though; I am going to investigate this, because obviously my international keyboards and fonts page needs serious updating.) Regards, Jan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: keyboard mapping problem under X
On Wed,20.May.09, 22:45:23, Jan Willem Stumpel wrote: Bruno Boettcher wrote: kbd is still on nodeadkeys... It appears that the keyboard system in X has changed. There is now something new and mysterious called evdev. To see if you have a system with evdev, type setxkbmap -print and see if evdev is mentioned. If it is, it seems that at the moment, to change the behaviour of the keyboard, you must specify things not only in etc/X11/xorg.conf, but *also* in /etc/default/console-setup. And changing /etc/default/console-setup should be enough, xorg.conf is ignored. then you must reboot! Stopping and restarting X is NOT enough. (There must be a better way though; I am going to investigate this, because obviously my international keyboards and fonts page needs serious updating.) Restart hal, at least in theory. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
keyboard mapping problem under X
Hello i have a problem on my debian machines lately concerning the keymapping of the keyboard... i use, whilst living in France, a german keyboard... from the beginning the default setting of no-dead-keys was annoying, but with a leattle tweakiing and configuring i could get rid of that annoying switch now it seems impossible to activate the dead-keys... as usual i reset the console keymap to use the normal de-latin1 mapping, and on the console i have the dead-keys but as of lately under X there seems no way to activate them i edited the xorg.conf, also found on old discussions /etc/default/console-setup where indeed was the dreaded nodeadkeys-switch i even made a grep on whole /etc to track down further occurences of that damned setting, but couldn't find none still, dead-keys aren't working so, what possibilities remain to activate them? without redefining a whole new keymapping, especially since the system seems to have changed? -- ciao bboett == bbo...@adlp.org http://inforezo.u-strasbg.fr/~bboett/ === -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: keyboard mapping problem under X
Bruno Boettcher wrote: Hello [..] i use, whilst living in France, a german keyboard... You take the trouble to mention this: any special reason? For instance, do you want to type mostly French on a German keyboard? still, dead-keys aren't working so, what possibilities remain to activate them? without redefining a whole new keymapping, especially since the system seems to have changed? KDE or Gnome have GUI utilities that will make the keyboard do what you want (i.e. without directly editing system files). Probably in something called System, Keyboard. If (like me) you want to avoid using KDE/Gnome, you can *also* make the keyboard do what you want. The German keyboard is called de. It has several so-called variants: -basic (this is the default, which has several dead keys) -nodeadkeys (no keys are dead) -deadgraveacute (only grave and acute are dead) -deadacute (only acute is dead) -ro (includes special characters for Romanian. I don't know why this is included in a German keyboard description; maybe German keyboards are commonly used in Romania) -ro_nodeadkeys -... etc, etc, ... See the file /usr/share/X11/xkb/symbols/de. The variants are described in sections beginning with xkb_symbols. You can select whatever variant you want by typing in a terminal (e.g. xterm) window: setxkbmap de [-variant name of variant] E.g. setxkbmap de -variant deadgraveacute If you just want to use the basic variant, you just type setxkbmap de You can use the setxkbmap command to experiment with keyboard layouts and variants. Once you have selected what you want, you can put it in /etc/X11/xorg.conf, in the keyboard section, in a slightly different format, using one line for the keyboard and another for the variant, e.g.: Option XkbLayout de Option XkbVariant deadgraveacute This will make your selection (semi-)permanent. There are many more possibilities for handling the keyboard in X (not so many on the console). For instance, you can switch between entirely different keyboard layouts by defining a special key. For details, see below, sections 6.1 and 6.2. Regards, Jan http://www.jw-stumpel.nl/stestu.html -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: weird problem in X with recent sid packages
Florian Kulzer wrote:
dibble:~# dpkg -l xkb\* x11-\* xserver-xorg-input\* libx11\* | awk '/^i/{print
$1,$2,$3}'
ii libx11-6 6.8.2.dfsg.1-6
[...]
The other packages listed were up-to-date for Sid, but your libx11-6 is
way too old. (Even Etch/oldstable has version 2:1.0.3-7 already!)
Upgrade this package to 2:1.2-1 and restart gdm.
That did the trick, thank you so very much :-]
You probably should run
aptitude search '~o|~U'
to check for other obsolete/upgradable packages on your system.
I certainly will, thanks for that tip.
I really appreciate your help,
~c
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: weird problem in X with recent sid packages
Florian Kulzer wrote:
[...]
Try to change the above section (and restart gdm):
Section InputDevice
Identifier Keyboard0
Driver kbd
Option CoreKeyboard
Option XkbRules xorg
Option XkbModel pc105
Option XkbLayout us
EndSection
The keyboard driver has been superseded by kdb for a while; see the
remarks in /usr/share/doc/xserver-xorg-input-kbd/NEWS.Debian.gz. The
xfree86 rules still exist as a legacy symlink, but it cannot hurt to
update the XkbRules line to xorg when you are editing the
configuration anyway.
Thanks for the quick reply. Unfortunately the symptoms remain (only every
other keystroke is registered in gdm).
If the new configuration does not solve your problem then I would like
to see the output of this command:
dpkg -l xkb\* x11-\* xserver-xorg-input\* libx11\* | awk '/^i/{print $1,$2,$3}'
dibble:~# dpkg -l xkb\* x11-\* xserver-xorg-input\* libx11\* | awk '/^i/{print
$1,$2,$3}'
ii libx11-6 6.8.2.dfsg.1-6
ii x11-apps 7.3+4
ii x11-common 1:7.3+18
ii x11-session-utils 7.3+1
ii x11-utils 7.4+1
ii x11-xfs-utils 7.4+1
ii x11-xkb-utils 7.4+2
ii x11-xserver-utils 7.3+5
ii xkb-data 1.5-2
ii xserver-xorg-input-all 1:7.3+18
ii xserver-xorg-input-evdev 1:2.0.8-1
ii xserver-xorg-input-kbd 1:1.3.1-1
ii xserver-xorg-input-mouse 1:1.3.0-1
ii xserver-xorg-input-synaptics 0.14.7~git20070706-3
ii xserver-xorg-input-wacom 0.8.1.6-1
thanks again for taking the time to look at this,
~c
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: weird problem in X with recent sid packages
On Wed, Mar 18, 2009 at 18:24:23 -0400, charlie derr wrote:
Florian Kulzer wrote:
[...]
Try to change the above section (and restart gdm):
Section InputDevice
Identifier Keyboard0
Driver kbd
Option CoreKeyboard
Option XkbRules xorg
Option XkbModel pc105
Option XkbLayout us
EndSection
[...]
Unfortunately the symptoms remain (only every other keystroke is registered
in gdm).
[...]
dpkg -l xkb\* x11-\* xserver-xorg-input\* libx11\* | awk '/^i/{print
$1,$2,$3}'
dibble:~# dpkg -l xkb\* x11-\* xserver-xorg-input\* libx11\* | awk
'/^i/{print $1,$2,$3}'
ii libx11-6 6.8.2.dfsg.1-6
[...]
The other packages listed were up-to-date for Sid, but your libx11-6 is
way too old. (Even Etch/oldstable has version 2:1.0.3-7 already!)
Upgrade this package to 2:1.2-1 and restart gdm.
You probably should run
aptitude search '~o|~U'
to check for other obsolete/upgradable packages on your system.
--
Regards,| http://users.icfo.es/Florian.Kulzer
Florian |
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: weird problem in X with recent sid packages
Florian Kulzer wrote: On Fri, Mar 13, 2009 at 20:56:03 -0400, charlie derr wrote: I have a machine that's quite old and underpowered that I've been running as Debian unstable for several years. A week or so ago, after upgrading a bunch of packages (including lots of xserver-xorg* and the kernel) I found that my keystrokes were not being properly registered (but only in X -- the command line and remote SSH sessions work fine). Basically I found that on the gdm login screen when I hit a key nothing would happen, but the second time I hit it, the character would be rendered on my screen. Going on a hunch I tried to login by typing every character in both my username and password twice and it succeeded. Once logged in (to KDE) things were worse (keystrokes were obviously being mapped to strange things, as I couldn't even get any letters to render in a konsole session). [...] How is your keyboard configured? Please post the output of these two commands (you can run them in a non-X terminal, e.g. CTRL+ALT+F1): Thank you very much for the response. awk '/Section InputDevice/,/EndSection/' /etc/X11/xorg.conf n...@dibble:~$ awk '/Section InputDevice/,/EndSection/' /etc/X11/xorg.conf Section InputDevice Identifier Keyboard0 Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout us EndSection Section InputDevice Identifier Serial Mouse Driver mouse Option Protocol Microsoft Option Device /dev/ttyS1 Option Emulate3Buttons true Option Emulate3Timeout 70 Option SendCoreEvents true EndSection Section InputDevice Identifier PS/2 Mouse Driver mouse Option Protocol auto Option ZAxisMapping 4 5 Option Device /dev/psaux Option Emulate3Buttons true Option Emulate3Timeout 70 Option SendCoreEvents true EndSection Section InputDevice Identifier USB Mouse Driver mouse #Option Device/dev/input/mice Option Device/dev/psaux Option SendCoreEventstrue Option Protocol auto Option ZAxisMapping 4 5 Option Buttons 5 EndSection grep -i keyboard /var/log/Xorg.0.log n...@dibble:~$ grep -i keyboard /var/log/Xorg.0.log (**) |--Input Device Keyboard0 (II) Initializing built-in extension XKEYBOARD (**) Option CoreKeyboard (**) Keyboard0: always reports core events (**) Keyboard0: Protocol: standard (**) Keyboard0: XkbRules: xfree86 (**) Keyboard0: XkbModel: pc105 (**) Keyboard0: XkbLayout: us (**) Keyboard0: CustomKeycodes disabled (II) evaluating device (Keyboard0) (II) XINPUT: Adding extended input device Keyboard0 (type: KEYBOARD) Thanks to anyone for any suggestions (or more requests for information). ~c -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: weird problem in X with recent sid packages
On Tue, Mar 17, 2009 at 08:34:14 -0400, charlie derr wrote:
Florian Kulzer wrote:
On Fri, Mar 13, 2009 at 20:56:03 -0400, charlie derr wrote:
I have a machine that's quite old and underpowered that I've been
running as Debian unstable for several years. A week or so ago,
after upgrading a bunch of packages (including lots of xserver-xorg*
and the kernel) I found that my keystrokes were not being properly
registered (but only in X -- the command line and remote SSH sessions
work fine). Basically I found that on the gdm login screen when I
hit a key nothing would happen, but the second time I hit it, the
character would be rendered on my screen.
[...]
awk '/Section InputDevice/,/EndSection/' /etc/X11/xorg.conf
n...@dibble:~$ awk '/Section InputDevice/,/EndSection/' /etc/X11/xorg.conf
Section InputDevice
Identifier Keyboard0
Driver keyboard
Option CoreKeyboard
Option XkbRules xfree86
Option XkbModel pc105
Option XkbLayout us
EndSection
[...]
Try to change the above section (and restart gdm):
Section InputDevice
Identifier Keyboard0
Driver kbd
Option CoreKeyboard
Option XkbRules xorg
Option XkbModel pc105
Option XkbLayout us
EndSection
The keyboard driver has been superseded by kdb for a while; see the
remarks in /usr/share/doc/xserver-xorg-input-kbd/NEWS.Debian.gz. The
xfree86 rules still exist as a legacy symlink, but it cannot hurt to
update the XkbRules line to xorg when you are editing the
configuration anyway.
If the new configuration does not solve your problem then I would like
to see the output of this command:
dpkg -l xkb\* x11-\* xserver-xorg-input\* libx11\* | awk '/^i/{print $1,$2,$3}'
--
Regards,| http://users.icfo.es/Florian.Kulzer
Florian |
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: weird problem in X with recent sid packages
On Fri, Mar 13, 2009 at 20:56:03 -0400, charlie derr wrote: I have a machine that's quite old and underpowered that I've been running as Debian unstable for several years. A week or so ago, after upgrading a bunch of packages (including lots of xserver-xorg* and the kernel) I found that my keystrokes were not being properly registered (but only in X -- the command line and remote SSH sessions work fine). Basically I found that on the gdm login screen when I hit a key nothing would happen, but the second time I hit it, the character would be rendered on my screen. Going on a hunch I tried to login by typing every character in both my username and password twice and it succeeded. Once logged in (to KDE) things were worse (keystrokes were obviously being mapped to strange things, as I couldn't even get any letters to render in a konsole session). [...] How is your keyboard configured? Please post the output of these two commands (you can run them in a non-X terminal, e.g. CTRL+ALT+F1): awk '/Section InputDevice/,/EndSection/' /etc/X11/xorg.conf grep -i keyboard /var/log/Xorg.0.log -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
weird problem in X with recent sid packages
I have a machine that's quite old and underpowered that I've been running as Debian unstable for several years. A week or so ago, after upgrading a bunch of packages (including lots of xserver-xorg* and the kernel) I found that my keystrokes were not being properly registered (but only in X -- the command line and remote SSH sessions work fine). Basically I found that on the gdm login screen when I hit a key nothing would happen, but the second time I hit it, the character would be rendered on my screen. Going on a hunch I tried to login by typing every character in both my username and password twice and it succeeded. Once logged in (to KDE) things were worse (keystrokes were obviously being mapped to strange things, as I couldn't even get any letters to render in a konsole session). I'm not providing many specifics because I don't really have a clue where to look. If someone can suggest a direction, I'd be happy to post configs, versions of packages or whatever. The processor in this machine is an AMD-K6 500MHz The kernel is 2.6.28-1-486 and while composing this message it occurred to me that I ought to try to boot back into my old kernel to see if the problem exists there, but due to all my upgrading I now get a kernel panic with a message stating kernel too old (the old kernel (that worked fine for many months if not years) was 2.6.17-1-486). thanks much in advance for any guidance, ~c -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
keymap problem with X
[please cc me, i'm not subscribed]
Hi,
I can't get an usb keyboard working in X in debian etch. The x is started from
root user (not great i know). The keyboard works fine in virtual terminals.
I've tried to manually compile the keymap, but the link get deleted on X start.
setxkbmap -rules xfree86 -model pc105 -layout it -print server-0
xkbcomp server-0
ln -s ~/server-0.xkm /var/lib/xkb/server-0.xkm
This is the relevant configuration:
Section InputDevice
Identifier Generic Keyboard
Driver kbd
Option CoreKeyboard
Option XkbRules xorg
Option XkbModel pc105
Option XkbLayout it
EndSection
These are the errors from /var/log/Xorg.0.log:
(II) XINPUT: Adding extended input device Generic Keyboard (type: KEYBOARD)
xkb_keycodes { include xfree86+aliases(qwerty) };
xkb_types{ include complete };
xkb_compatibility{ include complete };
xkb_symbols { include pc(pc105)+it };
xkb_geometry { include pc(pc105) };
(II) Configured Mouse: ps2EnableDataReporting: succeeded
xkb_types{ include % };
xkb_compatibility{ include % };
xkb_symbols { include % };
xkb_geometry { include % };
(EE) Error loading keymap /var/lib/xkb/server-0.xkm
xkb_types{ include % };
xkb_compatibility{ include % };
xkb_symbols { include % };
xkb_geometry { include % };
(EE) Error loading keymap /var/lib/xkb/server-0.xkm
thanks in advance
--
Riccardo Magliocchetti
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upgrade problem: dpkg: 'x' not found on PATH
I was able to fix it. Apparently if the error occurs, it doesn't install the package at all. So I put the necessary dirs in root's path and ran 'aptitude install' again for the failed packages and it was ok. Thanks. Nick -- Nick's Auditorium: http://users.pandora.be/nicks_auditorium History of and technical information on movie sound systems. De geschiedenis van en technische informatie over geluidssystemen voor cinema's. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] . -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upgrade problem: dpkg: 'x' not found on PATH
I was able to fix it. Apparently if the error occurs, it doesn't install the package at all. So I put the necessary dirs in root's path and ran 'aptitude install' again for the failed packages and it was ok. Thanks. Nick -- Nick's Auditorium: http://users.pandora.be/nicks_auditorium History of and technical information on movie sound systems. De geschiedenis van en technische informatie over geluidssystemen voor cinema's. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] .. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] . -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upgrade problem: dpkg: 'x' not found on PATH
I was able to fix it. Apparently if the error occurs, it doesn't install the package at all. So I put the necessary dirs in root's path and ran 'aptitude install' again for the failed packages and it was ok. Thanks. Nick -- Nick's Auditorium: http://users.pandora.be/nicks_auditorium History of and technical information on movie sound systems. De geschiedenis van en technische informatie over geluidssystemen voor cinema's. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] .. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] . -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upgrade problem: dpkg: 'x' not found on PATH
I was able to fix it. Apparently if the error occurs, it doesn't install the package at all. So I put the necessary dirs in root's path and ran 'aptitude install' again for the failed packages and it was ok. Thanks. Nick -- Nick's Auditorium: http://users.pandora.be/nicks_auditorium History of and technical information on movie sound systems. De geschiedenis van en technische informatie over geluidssystemen voor cinema's. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Upgrade problem: dpkg: 'x' not found on PATH
I'm trying to upgrade a Sarge box to Etch and several dpkg: `x' not found on PATH-errors occured. I followed the instructions in the release notes (http://www.nl.debian.org/releases/etch/i386/release-notes/ch- upgrading.en.html): I ran # aptitude upgrade # aptitude install initrd-tools # aptitude install libfam0 xlibmesa-glu When I ran the last command I noticed these errors: [...] Fetched 892kB in 2s (363kB/s) dpkg: `ldconfig' not found on PATH. dpkg: `start-stop-daemon' not found on PATH. dpkg: `install-info' not found on PATH. dpkg: `update-rc.d' not found on PATH. dpkg: 4 expected program(s) not found on PATH. NB: root's PATH should usually contain /usr/local/sbin, /usr/sbin and / sbin. E: Sub-process /usr/bin/dpkg returned an error code (2) Ack! Something bad happened while installing packages. Trying to recover: dpkg: `ldconfig' not found on PATH. dpkg: `start-stop-daemon' not found on PATH. dpkg: `install-info' not found on PATH. dpkg: `update-rc.d' not found on PATH. dpkg: 4 expected program(s) not found on PATH. NB: root's PATH should usually contain /usr/local/sbin, /usr/sbin and / sbin. [...] I checked and indeed, /sbin/ and /usr/sbin/ weren't in root's PATH variable. (I fixed that now) I suspected that these messages appeared in the previous commands too and indeed, with the upgrade of initrd-tools it had similar errors. For the 1st command I couldn't find the console output anymore but I fear the worst. What should I do? Thanks. Nick -- Nick's Auditorium: http://users.pandora.be/nicks_auditorium History of and technical information on movie sound systems. De geschiedenis van en technische informatie over geluidssystemen voor cinema's.
Re: Upgrade problem: dpkg: 'x' not found on PATH
On Wed, Sep 26, 2007 at 01:44:09PM +0200, Nick De Graeve wrote: I'm trying to upgrade a Sarge box to Etch and several dpkg: `x' not found on PATH-errors occured. I followed the instructions in the release notes (http://www.nl.debian.org/releases/etch/i386/release-notes/ch- upgrading.en.html): I ran # aptitude upgrade # aptitude install initrd-tools # aptitude install libfam0 xlibmesa-glu When I ran the last command I noticed these errors: [...] Fetched 892kB in 2s (363kB/s) dpkg: `ldconfig' not found on PATH. dpkg: `start-stop-daemon' not found on PATH. dpkg: `install-info' not found on PATH. dpkg: `update-rc.d' not found on PATH. dpkg: 4 expected program(s) not found on PATH. NB: root's PATH should usually contain /usr/local/sbin, /usr/sbin and / sbin. E: Sub-process /usr/bin/dpkg returned an error code (2) Ack! Something bad happened while installing packages. Trying to recover: dpkg: `ldconfig' not found on PATH. dpkg: `start-stop-daemon' not found on PATH. dpkg: `install-info' not found on PATH. dpkg: `update-rc.d' not found on PATH. dpkg: 4 expected program(s) not found on PATH. NB: root's PATH should usually contain /usr/local/sbin, /usr/sbin and / sbin. [...] I checked and indeed, /sbin/ and /usr/sbin/ weren't in root's PATH variable. (I fixed that now) I suspected that these messages appeared in the previous commands too and indeed, with the upgrade of initrd-tools it had similar errors. For the 1st command I couldn't find the console output anymore but I fear the worst. What should I do? First, confirm that the commands that weren't in the path are at least on the box. Then, ensuring that the paths are correct, I would run aptitude interactivly (text-based UI, not CLI) (perhaps after reading the aptitude manual if you haven't already) and see if it says that anything is broken. Then, still from the UI, do an update. See if there are any broken packages (couted, if any, in the second line header), then search for unconfigured packages (anything but a plain 'i' in the flag field). Once everything _appears_ correct, then do some serious testing. As always, ensure that you have good backups. Read the installation manual and if things don't work out rather quickly, do a full reinstall. My first upgrade from Sarge to Etch failed (died while updating libc6) and it was easier to reinstall. Since then, I've just reinstalled; it only takes 20 minutes or so. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problem with X
Hi all,On my testing box, where a lot of installation/removal happens as I both 1) test new configs and 2) learn how to do things without fear of data loss, I've run into an issue with X windowsNo graphical/X apps appear to be able to open. Fluxbox doesn't report anything, but trying to open a graphical app from shell fails with: Xlib: connection to :1 refused by serverXlib: No protocol specifiedSometimes multiple times per application. I do have Xauthority, I am running as user (not root), and my DISPLAY variable is set correctly. Any ideas folks?
The mouse erratic problem in X on AMD64 Debian Sarge box
I recently installed Debian Sarge on my AMD64 system. It all works fine until I start X (have tried startx and gdm). When I move the mouse, it jumps erratically around the screen. I have googled and found this problem, but the solutions I have found didn't work for me. One was the use of a fifo called gpmdata and the other was simply stopping gpm. Is there a website for figuring out: 1) which packages are required for X to work (preferably gnome) 2) how to make the mouse behave It is a logitech wireless mouse which works fine in my Slackware installation. I have also tried using xorg instead of xfree86. I tried to use the same config file that works on my Slack system too. Vicki -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: XKB problem with x-terminal
On Fri, Dec 09, 2005 at 11:22:30PM +0200, Simo Kauppi wrote:
On Thu, Dec 08, 2005 at 09:34:26PM +0100, Almut Behrens wrote:
On Wed, Dec 07, 2005 at 02:16:09PM +0200, Simo Kauppi wrote:
Is there a way to compile keyboard definitions for X and save them
somewhere, where XServer can read them, when it starts?
$ xkbcomp -xkm :0 keymap.xkm
Then, simply transfer the resulting keymap.xkm to your thinclient,
where you can make the X server load it upon startup using the option
-xkbmap keymap.xkm.
Thanks a lot, I hadn't figured this one out. Unfortunately, if I start X
with -xkbmap keymap.xkm, it says it doesn't like it!
If I start X with -xkbdb keymap.xkm, it doesn't complain, but the
keyboard doesn't behave properly :(
Not too surprising. That option's value is assigned to some variable
XkbDB (in xc/programs/Xserver/xkb/xkbInit.c) which isn't used anywhere
else beyond this assignment, in the entire X sources. Whatever that's
supposed to do, it isn't implemented yet ;)
The fact that -xkbmap doesn't work as advertised, isn't too surprising
either, 'cos I was telling rubbish (yeah, next time, Almut reminds
herself to actually verify the stuff she's claiming...)
Well actually, this option does work, kind of, but not in a manner as
straightforward as on might expect. However, I knew for sure I once
had it working already, so I've played around with it some more...
Well, found lots of weird things. But don't worry, I won't bore you
with the details. Just a brief description of how I finally got it
working, after lots of strace'ing and poking around in the X sources.
All in all, I can't help getting the impression, that Simo and me are
to the only two people in this world who have ever tried to make use of
this -xkbmap option :)
My main observations:
* you can't keep the X server from wanting to call xkbcomp, even in the
presence of a perfectly valid compiled xkbmap. At least, I dunno how.
* even though the output of the xkbcomp run isn't really used in this
case (AFAICT), it is good to have it succeed, superficially. In case
of any failures in this step, a couple of other things are being tried
which eventually lead to a complete failure of the whole shebang.
* you are expected to specify the bare name of the keymap (without the
.xkm extension); the X server looks for the map in certain predefined
directories (which do vary depending on which UID the server is started as)
* unless you have a dot in the keymap name, the X server deletes the
map before reading it. No kidding. This seems to be because the
path of the temporary output file (created during the useless run of
xkbcomp) is being set to where the real keymap is expected to be found.
And tempfile cleanup happens before the actual -xkbmap-related code
gets a chance to read it... Luckily, there's some odd sanitizing
being applied to the tempfile name (replacing '.' by '_'). That allows
us to play tricks here:
1: 6929 execve(/usr/bin/X11/XFree86, [/usr/X11R6/bin/X, :1, -xkbmap,
default.map], [/* 14 vars */]) = 0
2: 6930 execve(/usr/X11R6/lib/X11/xkb/xkbcomp,
[/usr/X11R6/lib/X11/xkb/xkbcomp, -w, 1, -R/usr/X11R6/lib/X11/xkb,
-xkm, -em1, The XKEYBOARD keymap compiler (x..., -emp, , -eml,
Errors from xkbcomp are not fata..., keymap/default.map,
compiled/default_map.xkm], [/* 14 vars */]) = 0
3: 6931 lstat64(/usr/X11R6/lib/X11/xkb/compiled/default_map.xkm, 0xba1c)
= -1 ENOENT (No such file or directory)
4: 6931 stat64(/usr/X11R6/lib/X11/xkb/keymap/default.map,
{st_mode=S_IFREG|0644, st_size=7804, ...}) = 0
5: 6931 open(/usr/X11R6/lib/X11/xkb/keymap/default.map,
O_RDONLY|O_LARGEFILE) = 6
6: 6931 open(/usr/X11R6/lib/X11/xkb/compiled/default_map.xkm,
O_WRONLY|O_CREAT|O_LARGEFILE, 0100644) = 7
7: 6929 open(/usr/X11R6/lib/X11/xkb/compiled/default_map.xkm, O_RDONLY) = 6
8: 6929 unlink(/usr/X11R6/lib/X11/xkb/compiled/default_map.xkm) = 0
9: 6929 open(/usr/X11R6/lib/X11/xkb/compiled/default.map.xkm, O_RDONLY) = 6
These are the relevant lines from the strace output when running X with
-xbkmap default.map (line numbers prepended). As you can see, for
some calls it uses default_map in place of default.map.
The open() in line 9 apparently is what finally makes things work.
The open() of the tempfile in line 7 has to succeed, too, or else weird
things happen, and the real open() in line 9 never takes place. Line 8
shows that tempfile cleanup now is no longer deleting the real file.
So, to summarize, here's what I did:
* moved away the original /usr/X11R6/lib/X11/xkb directory (a link to
/etc/X11/xkb, normally), preventing X from accessing anything in there.
* uncommented all 'Option Xkb*' entries in XF86Config-4/xorg.conf.
* created a dummy replacement for xkbcomp. This is just a simple script
which copies the precompiled keymap to the tempfile location where X is
expecting to find it -- hereby simulating a successful compile run:
#!/usr/bin/perl
$base = /usr/X11R6/lib/X11/xkb/;
$dest = pop
Re: XKB problem with x-terminal
On Sun, Dec 11, 2005 at 11:19:39PM +0100, Almut Behrens wrote: On Fri, Dec 09, 2005 at 11:22:30PM +0200, Simo Kauppi wrote: On Thu, Dec 08, 2005 at 09:34:26PM +0100, Almut Behrens wrote: On Wed, Dec 07, 2005 at 02:16:09PM +0200, Simo Kauppi wrote: Is there a way to compile keyboard definitions for X and save them somewhere, where XServer can read them, when it starts? $ xkbcomp -xkm :0 keymap.xkm Then, simply transfer the resulting keymap.xkm to your thinclient, where you can make the X server load it upon startup using the option -xkbmap keymap.xkm. If I start X with -xkbdb keymap.xkm, it doesn't complain, but the keyboard doesn't behave properly :( Not too surprising. That option's value is assigned to some variable XkbDB (in xc/programs/Xserver/xkb/xkbInit.c) which isn't used anywhere else beyond this assignment, in the entire X sources. Whatever that's supposed to do, it isn't implemented yet ;) The fact that -xkbmap doesn't work as advertised, isn't too surprising either, 'cos I was telling rubbish (yeah, next time, Almut reminds herself to actually verify the stuff she's claiming...) Well, it did make perfect sense :) I would have expected the -xkbmap to work exactly the way you described. All in all, I can't help getting the impression, that Simo and me are to the only two people in this world who have ever tried to make use of this -xkbmap option :) Maybe others just gave up when it didn't work the way one would expect. My main observations: * you can't keep the X server from wanting to call xkbcomp, even in the presence of a perfectly valid compiled xkbmap. At least, I dunno how. * even though the output of the xkbcomp run isn't really used in this case (AFAICT), it is good to have it succeed, superficially. In case of any failures in this step, a couple of other things are being tried which eventually lead to a complete failure of the whole shebang. * you are expected to specify the bare name of the keymap (without the .xkm extension); the X server looks for the map in certain predefined directories (which do vary depending on which UID the server is started as) * unless you have a dot in the keymap name, the X server deletes the map before reading it. No kidding. This seems to be because the path of the temporary output file (created during the useless run of xkbcomp) is being set to where the real keymap is expected to be found. And tempfile cleanup happens before the actual -xkbmap-related code gets a chance to read it... Luckily, there's some odd sanitizing being applied to the tempfile name (replacing '.' by '_'). That allows us to play tricks here: So, to summarize, here's what I did: * moved away the original /usr/X11R6/lib/X11/xkb directory (a link to /etc/X11/xkb, normally), preventing X from accessing anything in there. * uncommented all 'Option Xkb*' entries in XF86Config-4/xorg.conf. * created a dummy replacement for xkbcomp. This is just a simple script which copies the precompiled keymap to the tempfile location where X is expecting to find it -- hereby simulating a successful compile run: #!/usr/bin/perl $base = /usr/X11R6/lib/X11/xkb/; $dest = pop @ARGV;# of the 12 args that xkbcomp is called $src = $base . pop @ARGV;# with, the last two are of interest... $dest = $base$dest if $dest !~ m|^/|; system 'cp', $src, $dest; # create expected output exit 0# always succeed * created a new xkb directory, containing just the following: -rwxr-xr-x root/root 313 /usr/X11R6/lib/X11/xkb/xkbcomp drwxr-xr-x root/root 0 /usr/X11R6/lib/X11/xkb/keymap/ -rw-r--r-- root/root 7804 /usr/X11R6/lib/X11/xkb/keymap/default.map drwxr-xr-x root/root 0 /usr/X11R6/lib/X11/xkb/compiled/ lrwxrwxrwx root/root 0 /usr/X11R6/lib/X11/xkb/compiled/default.map.xkm - /usr/X11R6/lib/X11/xkb/keymap/default.map lrwxrwxrwx root/root 0 /var/tmp/default.map.xkm - /usr/X11R6/lib/X11/xkb/keymap/default.map (xkbcomp is the above script. default.map is the compiled keymap. The map in /var/tmp/ is used when X is run as a regular user.) I'm not saying this is way to do it -- just that it worked for me :) Tried with various versions of X from woody's XFree86 to Xorg-6.8.2. Let me know whether it works for you, too, Simo. I'm afraid I won't be able to help, if not, though -- just out of curiosity... Excellent work Almut! It works like a charm :) I can't thank you enough, figuring this out would have taken light years from me :)) Almut (...and I said, I wouldn't bore you with details... Well.) No worries there, having a software background myself, I find this really interesting. Yes, I know there must be something wrong with me :) Little sidenote: while searching for clues, I ran into this https://bugs.freedesktop.org/show_bug.cgi?id=4461, which seems to suggest that the default locations are going
Re: XKB problem with x-terminal
On Thu, Dec 08, 2005 at 09:34:26PM +0100, Almut Behrens wrote:
(okay, took me while to reply, but just in case you haven't figured it
out yourself in the meantime...)
Hi,
No, I still haven't figured it out totally, even though I have been
playing around with xkbcomp and its different options :)
On Wed, Dec 07, 2005 at 02:16:09PM +0200, Simo Kauppi wrote:
Hi,
Is there a way to compile keyboard definitions for X and save them
somewhere, where XServer can read them, when it starts?
The easiest way to create a compiled keymap is probably to extract
it from a running X server (on a machine which has xbase-clients
installed, and is running the desired xkb setup):
$ xkbcomp -xkm :0 keymap.xkm
Then, simply transfer the resulting keymap.xkm to your thinclient,
where you can make the X server load it upon startup using the option
-xkbmap keymap.xkm.
Thanks a lot, I hadn't figured this one out. Unfortunately, if I start X
with -xkbmap keymap.xkm, it says it doesn't like it!
If I start X with -xkbdb keymap.xkm, it doesn't complain, but the
keyboard doesn't behave properly :(
Another way would be to generate a specific keymap configuration from
options like you have in Xorg.conf. For example, I have in my section
InputDevice
...
Option XkbRules xfree86
Option XkbModel pc105
Option XkbLayout de
...
This would translate into the following commandline:
$ setxkbmap -rules xfree86 -model pc105 -layout de -print | xkbcomp -xkm -w 3
- keymap.xkm
The part before the pipe generates an xkb config file, like this
xkb_keymap {
xkb_keycodes { include xfree86+aliases(qwertz) };
xkb_types { include complete };
xkb_compat{ include complete };
xkb_symbols { include pc/pc(pc105)+pc/de};
xkb_geometry { include pc(pc105) };
};
This is the one I have been able to figure out :) The includes are
actually the files in the xkb/ directory for the five different
modules for the xkb configuration.
The trouble with this was, that I got a lot of warnings, but -w 3 doesn't
show them, so I believe that the compiled file should be OK. However, if
I load the file with -xkbdb, the keyboard doesn't behave correctly.
which essentially contains parameterized include statements for
individual xkb files, according to what has been determined via the
rules. This is then fed into xkbcomp to be compiled into keymap.xkm
(the -w 3 is just to reduce the warnings to a sensible level...).
Cheers,
Almut
Thanks a lot Almut! If you know any other tricks I could try, please let
me know...
Now that I have a proper keymap.xkm, I should figure out why it doesn't
work.
Simo
--
:r ~/.signature
signature.asc
Description: Digital signature
Re: XKB problem with x-terminal
(okay, took me while to reply, but just in case you haven't figured it
out yourself in the meantime...)
On Wed, Dec 07, 2005 at 02:16:09PM +0200, Simo Kauppi wrote:
Hi,
Is there a way to compile keyboard definitions for X and save them
somewhere, where XServer can read them, when it starts?
The reason I'm asking is that I set up a thinclient, i.e. an x-terminal
with just Xorg running on it. When X starts it gives the '(EE) Couldn't
load XKB keymap, falling back to pre-XKB keymap' -error and the keyboard
doesn't work properly.
It seems that when X starts it wants to compile the keyboard stuff on
the fly and feed it to the $DISPLAY.
The problem is that the xkb/rules are in the xlibs, which pulls all of
the xlibraries with it. To make things worse the, xkbcomp is in the
xbase-clients.
So, to be able to run x-terminal I would have to install all the
xlibraries and all the xclients into my terminal. For me this doesn't
seem very rational.
The easiest way to create a compiled keymap is probably to extract
it from a running X server (on a machine which has xbase-clients
installed, and is running the desired xkb setup):
$ xkbcomp -xkm :0 keymap.xkm
Then, simply transfer the resulting keymap.xkm to your thinclient,
where you can make the X server load it upon startup using the option
-xkbmap keymap.xkm.
Another way would be to generate a specific keymap configuration from
options like you have in Xorg.conf. For example, I have in my section
InputDevice
...
Option XkbRules xfree86
Option XkbModel pc105
Option XkbLayout de
...
This would translate into the following commandline:
$ setxkbmap -rules xfree86 -model pc105 -layout de -print | xkbcomp -xkm -w 3 -
keymap.xkm
The part before the pipe generates an xkb config file, like this
xkb_keymap {
xkb_keycodes { include xfree86+aliases(qwertz) };
xkb_types { include complete };
xkb_compat{ include complete };
xkb_symbols { include pc/pc(pc105)+pc/de};
xkb_geometry { include pc(pc105) };
};
which essentially contains parameterized include statements for
individual xkb files, according to what has been determined via the
rules. This is then fed into xkbcomp to be compiled into keymap.xkm
(the -w 3 is just to reduce the warnings to a sensible level...).
Cheers,
Almut
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
XKB problem with x-terminal
Hi, Is there a way to compile keyboard definitions for X and save them somewhere, where XServer can read them, when it starts? The reason I'm asking is that I set up a thinclient, i.e. an x-terminal with just Xorg running on it. When X starts it gives the '(EE) Couldn't load XKB keymap, falling back to pre-XKB keymap' -error and the keyboard doesn't work properly. It seems that when X starts it wants to compile the keyboard stuff on the fly and feed it to the $DISPLAY. The problem is that the xkb/rules are in the xlibs, which pulls all of the xlibraries with it. To make things worse the, xkbcomp is in the xbase-clients. So, to be able to run x-terminal I would have to install all the xlibraries and all the xclients into my terminal. For me this doesn't seem very rational. Any pointers highly appreciated. Simo -- :r ~/.signature signature.asc Description: Digital signature
udev und Problem mit X-Programmen als User
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joerg Rossdeutscher schrieb: Moin, Am Freitag, den 24.06.2005, 11:13 +0200 schrieb Christopher Hübner: Wenn ich ihn als normaler user starten will, egal ob startx oder mit kdm, dann passiert leider gar nichts. Möglicherweise hat das ja gar nix mit udev zu tun und ist bloss eine Duplizität der Ereignisse. Möglicherweise hat das Funktionieren unter root gar nichts mit Permissions zu tun, sondern einfach damit, dass root andere Einstellungen hat. Das glaube ich nicht, aber dazu später mehr. Sprich: 1. Geht ein evtl. neu anzulegender dritter User? Nein. 2. Ich nutze kein KDE, aber da gab es doch diesen ~/.kde3-Ordner, oder so ähnlich. Benenn den doch mal weg. KDE funktioniert Ein Versuch könnte es auch wert sein, einen neuen User anzulegen und den bloss ein nacktes X mit Terminal starten zu lassen, und wenn das läuft, daraus mal ein KDE-Programm zu starten und die Meldungen anzugucken. Genau das habe ich ausprobiert. xterm wollte nicht starten, weil angeblich keine ptys. Als root hat das schon funktioniert. Die Rechte von /dev/pty* waren leider so gesetzt das nur root darauf zugreifen konnte. Da _ich_ das sicher nicht gemacht habe kann ich mir nur noch einen Schuldigen vorstellen -- udev Die Rechte von /dev/null waren auch so gesetzt das postgresql den Start verweigert hat. Auch das war sicher nicht _ich_. Ich habe es geschafft mein KDE wieder zu starten indem ich der Gruppe users Zugriff auf /dev/pty* gegeben habe. Danach habe ich xinit ausgeführt und in das xterm startkde eingetippt. Der direkte Start von KDE (ob kdm oder startx) funktioniert leider immer noch nicht. Allerdings habe ich den Verdacht das das alles mit falschen Rechten (von udev vermasselt) unterhalb von /dev zu tun hat. Daher meine Frage: Wie kann ich diese Rechte wiederherstellen? Christopher -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iQEVAwUBQr/tC59mxmbqgAiXAQIgAAf+Ng6eE8STbsbI42sdo2NGJsem7XpvDqwa 6CA52kiQyAuUWRtnHpwZzuA3mbc8QSALwAVmDmmjyYwwKsg+QRGxz/Ur9znOd/6X PLnMJWOQLdpyUaRoaicSV7H/tKHX4GCsPN88iBtsahhaUIkSP20woJryK+OabTy1 /smsFztDZ6cYccgGTlFlFeu08AjtR1esAxGdeJtVl4QNh++3tTVMzFLwu01HT4TB y5O4DxnoyMn6IC/673NG0sK/uFf/8iuLxZ+sj347K1ndZXScYe31fc9C4Z+twtah ua4MLkOfp95t5PI2/4QcCkBvtPqfX+ENJhgsi4vOUN+X5AXdJ+JSYQ== =0jhO -END PGP SIGNATURE- -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Dziwny problem z X-ami
Dnia 04-05-2005, ro o godzinie 20:07 +0200, Jarek 111 napisa(a): Witam! Po wymianie monitora(!) zdechy mi czciowo X-y. Karta onboardowa i82965G, chodzca do tej pory bez problemw, po wymianie monitora na LCD zacza dziwnie si zachowywa. A byo to tak: 1024x768x85Hz - wszystko hulao. Po wymianie monitora, zrobiem dpkg-reconfigure i dexconf ustawiem na 1280x1024x60Hz i CRT-LCD. Po tej operacji gdm zdech. Co ciekawe, mog odpali X-y przez startx (ale tylko z root-a) inaczej nie dziaaj. W logu x-ow jest takie cos: (II) I810(0): [drm] removed 1 reserved context for kernel (II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xe0212000 at 0xb7e52000 (WW) I810(0): Setting the original video mode instead of restoring the saved state (II) I810(0): xf86UnbindGARTMemory: unbind key 7 (II) I810(0): xf86UnbindGARTMemory: unbind key 0 (II) I810(0): xf86UnbindGARTMemory: unbind key 2 (II) I810(0): xf86UnbindGARTMemory: unbind key 1 (II) I810(0): xf86UnbindGARTMemory: unbind key 3 (II) I810(0): xf86UnbindGARTMemory: unbind key 4 (II) I810(0): xf86UnbindGARTMemory: unbind key 5 (II) I810(0): xf86UnbindGARTMemory: unbind key 6 Przy odpalaniu gdm-a pojawia sie na chwile tryb graficzny (siateczka X-owa z zegarkiem) a potem wszystko znika. Debian unstable, (wszystko swiezo updateowane), kernel custom 2.6.11.6. Probowalem z FB i bez FB, zmienialem LCD na CRT - wszystko bez skutku. Bede wdzieczny za wszelkie sugestie. Witam. Pewnie niewiele Ci to pomoe, ale gdy niedawno wymieniaem minitor z baki Samsunga na LCD Philispa, wszystko byo OK. Rozidziake miaem tak jak u Ciebie: 1024x768 przy 85Hz. Odczyem jeden monitor, podczyem drugi - adnej rekonfiguracji i zero problemw... Co do odpalania X-w, to w Sage'u jest tak domylnie ustawione, e tylko root moe uruchamia okienka. Pozdrawiam e-gore
Dziwny problem z X-ami
Witam! Po wymianie monitora(!) zdechy mi czciowo X-y. Karta onboardowa i82965G, chodzca do tej pory bez problemw, po wymianie monitora na LCD zacza dziwnie si zachowywa. A byo to tak: 1024x768x85Hz - wszystko hulao. Po wymianie monitora, zrobiem dpkg-reconfigure i dexconf ustawiem na 1280x1024x60Hz i CRT-LCD. Po tej operacji gdm zdech. Co ciekawe, mog odpali X-y przez startx (ale tylko z root-a) inaczej nie dziaaj. W logu x-ow jest takie cos: (II) I810(0): [drm] removed 1 reserved context for kernel (II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xe0212000 at 0xb7e52000 (WW) I810(0): Setting the original video mode instead of restoring the saved state (II) I810(0): xf86UnbindGARTMemory: unbind key 7 (II) I810(0): xf86UnbindGARTMemory: unbind key 0 (II) I810(0): xf86UnbindGARTMemory: unbind key 2 (II) I810(0): xf86UnbindGARTMemory: unbind key 1 (II) I810(0): xf86UnbindGARTMemory: unbind key 3 (II) I810(0): xf86UnbindGARTMemory: unbind key 4 (II) I810(0): xf86UnbindGARTMemory: unbind key 5 (II) I810(0): xf86UnbindGARTMemory: unbind key 6 Przy odpalaniu gdm-a pojawia sie na chwile tryb graficzny (siateczka X-owa z zegarkiem) a potem wszystko znika. Debian unstable, (wszystko swiezo updateowane), kernel custom 2.6.11.6. Probowalem z FB i bez FB, zmienialem LCD na CRT - wszystko bez skutku. Bede wdzieczny za wszelkie sugestie. -- Jarek [EMAIL PROTECTED]
Problem starting x server
Hello! I'm new to Debian and this GNU/linux. I've installed from CD but the machine returns an error saying "I cannot start x server, it is likely that it is not set up correctly etc etc". Then next screen says "warning process set to nice value 0 instead of -10 as requested etc". Next screen "would you like to run the x config program etc" then "I will now try to restart x server again" then "I cannot start the x server". It either goes round in circles or I have to decline and get to the command prompt. The machine is not yet on either its network or the internet, the only way in is via CD (no-floppy). Can anyone tell me how (in simple terms please!) how to get through this and bring up the GUI? I copied the CD from a mirror. I've tried the faq's and other lists. Also I get loads of error messages, all the same, thus: ide2: unexpected interrupt, status=0xd0, count= (ascending number), I think it's because I've got a large SATA drive is this true? How canI lose the messages echoing to screen? Thanks Adrian [EMAIL PROTECTED]
Re: Problem starting x server
Adrian S. Glover wrote: Hello! I'm new to Debian and this GNU/linux. I've installed from CD but the machine returns an error saying I cannot start x server, it is likely that it is not set up correctly etc etc. Setting up X is one of the most common difficulties newbies have, especially if they're using the current Stable branch of Debian, Woody. Woody is ancient, and if this is what you have, you'd probably find life much easier if you could upgrade to Sarge (Testing) or Sid (Unstable), both of which are suitable for workstation use (whereas you'd probably do better to stick with Woody for a server, in which case, do you really need X?). Then next screen says warning process set to nice value 0 instead of -10 as requested etc. You can ignore this error; it's not the one causing you problems. Next screen would you like to run the x config program etc then I will now try to restart x server again then I cannot start the x server. It either goes round in circles or I have to decline and get to the command prompt. The machine is not yet on either its network or the internet Then upgrading to Sarge or Sid is more difficult. , the only way in is via CD (no-floppy). Can anyone tell me how (in simple terms please!) how to get through this and bring up the GUI? I copied the CD from a mirror. I've tried the faq's and other lists. Run lspci and see what video chipset you have; the output will look something like this: [EMAIL PROTECTED]:/home/westk/DOCS/KCARC/NEWSLETTERS/2005 lspci :00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333] :00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP] :00:09.0 Ethernet controller: Linksys NC100 Network Everywhere Fast Ethernet 10/100 (rev 11) :00:0b.0 VGA compatible controller: S3 Inc. 86c325 [ViRGE] (rev 06) :00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge :00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) :00:11.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1b) :00:11.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1b) :00:11.4 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1b) :00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 30) :01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 RL/VR AGP There are two lines referring to VGA controllers, indicating that this box has two video cards (yours probably (almost certainly) only has one); one is an S3 86c325; the other is an ATI Rage 128. Now that you know what video chipset you have, run dpkg-reconfigure xserver-xfree86, and select the corresponding driver for your chipset when prompted. After this program is finished, try starting X manually with the startx command. If it still fails, look on the screen (Shift-PgUP to scroll up) for any relevant error messages. Also you might look in /var/log/XFree86.0.log. As your other question is on a different topic, it really deserves its own thread. I'd still attempt answering it, however, if I were so qualified. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem starting x server
On Mon, 2004-12-27 at 17:08 +, Adrian S. Glover wrote: Hello! Adrian [EMAIL PROTECTED] Hi Adrian, in case of a misconfigured xserver you can do a couple of things that all come to basically the same thing: modifying your /etc/X11/XF86Config-4 This is your central xserver config file. You can run the configure tool again with a 'dpkg-reconfigure xserver-xfree86' or do it manually with a 'lspci' as root, find your graphics card and note it down. Edit the file with a 'nano /etc/X11/XF86Config-4', find a 'Section Device' and modify the 'Driver' statement to have the driver matching your card, don't forget to save. Start xfree86 again with a' /etc/init.d/gdm start'. Sincerely , Jan. -- John Smith [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
problem with X-4.3 + flat panels using dvi cables and nvidia graphics card
I am having a nagging problem with my Nvidia-GeForce FX 5200 video card. I am hoping to get some help from this forum(s) on how to correct the problem(s). Please reply directly or through the forum with advise on this problem. First, let me give some details of my setup. The video card is a PCI card, not AGP. This is because the Intel-SE7500CW2 server board I am using as my desktop does not have an AGP slot (found this out after I ordered it !) Part of my problem may be related to this fact (PCI card). I also have a DEL-2000FP flat-panel monitor with a DVI video cable coupling the video card to the monitor. I am using XFree86-4.3.0.dfsg.1-1 out of Debian/Sid distribution of Linux. I have also tried backports from snapshot.debian.net to 4.3.0-7 with no improvement. I am not exactly sure when this problem started to show up. Most likely when the card was initially installed replacing the ATI card. I do not think it is related to recent upgrades to X or the kernel. I do not have any of these problems on a similarly configured Debian/Sid at home that has a regular CRT monitor (not flat panel and not dvi). Therefore, I think the problem is unique to flat panel monitors with dvi inputs/cables. Also none of these problems (including the 2.6.x problems below) existed on using a slower ATI-Radeon 9200 pci card. I want the nvidia card to gain the speed for 3D graphics applications. I also like nvidia cards in general and have purchased several for several different computers. Here is what works: kernel version 2.4.26 + nvidia driver in any mode within X windows kernel version 2.4.26 + Xfree86 nv driver in 1024x768 resolution or less + vga console Here is what is crippled: kernel version 2.4.26 + nvidia driver at the vga console after X starts. The screen is full of streaks in both x and y direction with constant noise to the screen. Nothing appears to be able to remove this noise. Here is what is completely broken: kernel version 2.6.6 + nvidia or nv driver in X windows. It installs fine, but produces blank screens. Here is what I have tried in looking at FAQ and other questions answered on the net: As boot options (or append strings in lilo.conf): pci=noacpi acpi=off noapic acpi_skip_timer_override Essentially every available option in the nvidia driver including (currently commented out, trying one at a time): # Option FlatPanelProperties Scaling = default, Dithering = default # Option UseInt10Module 1 # use the following option only with DVI cards ## Option ConnectedMonitor DFP ## Option IgnoreDisplayDevices TV # Option NoBandWidthTest 1 # Option DigitalVibrance 255 # Option RenderAccel 0 # Option NoRenderExtension 1 # Option NoFlip 1 ## Option NvAGP 0 # Option SWCursor 1 # Option HWCursor 0 ## Option CursorShadow true # Option CursorShadowAlpha 64 # range 0 (transparent) to 255 (opaque) # Option CursorShadowYOffset 2 # range 0 to 32 pixels # Option MultisampleCompatibility 1 The following options in the nv driver: ## Driver nv ## Option FlatPanel 1 ## Option FPDither 1 Here is what I presently have in the relevant sections of my /etc/X11/XFConfig-4 file: Section Module Loaddbe Loadextmod Loadglx Loadrecord Loadbitmap Loadfreetype Loadspeedo Loadtype1 Loadvbe Loadint10 #nvidia Loadddc #nvidia Loaddri #nvidia Loadpex5 #nvidia LoadGLcore #nvidia Loadxie EndSection Section Device Identifier Chaintech GeForce FX-5200 Driver nvidia Option NoLogo true Option NoDDC true Option ConnectedMonitor DFP Option IgnoreDisplayDevices TV Option NvAGP 0 Option CursorShadow true EndSection Section Monitor Identifier Dell 2000FP HorizSync 31-80 VertRefresh 56-76 # vsync=60 and hxync=75 is the optimum for 1600x1200 according to Dell's specs ## VertRefresh 60 ## HorizSync 75 vendorname [Dell 2000FP] modelname [Dell 2000FP] Option dpms EndSection Section Screen Identifierfea DeviceChaintech GeForce FX-5200 Monitor Dell 2000FP DefaultDepth 24 DefaultFbBpp 32 SubSectionDisplay Depth 24 Modes 1600x1200 1400x1050 1280x1024 1152x864 1024x768 800x600 # only mode that appears to work correctly with the Xfree86 nv driver ##Modes 1024x768 EndSubSection EndSection Finally, here is the /var/log/XFree86.0.log file This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest
Re: dvd tv-out problem with X
Seems there aren't too many using / interested in tv out. Anyway, I managed to get tv-out to work (by using atitvout) with telling X to use the vesa driver instead of radeon. (I.e. by editing /etc/X11/XF86Config-4, looking up the device driver (was radeon) and changing it to vesa.) There's one problem with this fix though: I can't use (the video out (?) driver) xv anymore, but have to use x11 to playback movies etc.. /It works/ like this, but it would be nice to be able to use xv ... Not sure why it stopped working in the first place though: whatever made it not-work, must be something else than what I changed; I tried / looked at a backup of XF86Config-4, and I /had/ been using the `radeon' driver before (and it worked). Kristian Niemi wrote: Question I: I've got this strange problem; tvout in X doesn't work any more -- works fine from shell though (i.e. `bashing' on tv works ;) ). I have a ATI Radeon 7500 Mobile card on a Dell Inspiron laptop, running Debian unstable (up to date). I'm using the package atitvout to `attach' tv (command atitvout -f t) The thing is, and the strange part, that everything worked fine a couple of days ago, Tuesday to be exact. So my guess is that some package, that has gotten updated since Tuesday, is causing this. Perhaps there's some really easy setting(s) that I have forgotten about? Does anyone feel like taking a guess as to what package might be causing this / what settings I could try? I have a feeling it has something to do with X, not atitvout, but I could (very well) be wrong. Can you think of a package that might have something to do with this? The only thing I've really added to Debian since then, is XFCE-4, including all recommended packages. (Don't see how that might have an effect?) *Everything looks fine, works fine*, except when looking at it through the tv. The commands I use to attach the tv is as they were when it worked, as is XF86Config-4 (I tried with a backup conf). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dvd tv-out problem with X
Alright... I've been trying to find some more info. There are some posts on the net suggesting the problem might have something to do with kernel 2.6.*; I'm using 2.6.3. See http://www.via.ecp.fr/via/ml/libdvd...1/msg6.html There's also other posts suggesting the same thing, but I haven't found any /solutions/. When trying to play DVD with xine -- or mplayer, or ogle -- sooner or later, before the movie *should end* I get a libdvdread: Can't seek to block xxx Where x... usually, if not always, is above a number higher than 200. I'm using libdvdread3 0.9.4-4. Kristian Niemi wrote: Question II: This is a more trivial problem. I'm trying to play DVD's with my Samsung CD-RW/DVD -combo drive. Older DVD:s that I have work fine. Newer, however, all seem to `miss an ending' -- they just end abruptly, no credits, no nothing. Mplayer / xine just kind of state that `end of file', no more data. At first I thought it was faulty DVD:s, but now after I've tried *six different ones*, all showing the same `symptoms', I'm starting to doubt that something else might be going on ... Anyone else experiencing something similar? Have they started making DVD:s in some new way, creating DVD:s incompatible with my drive? (Samsung CD-RW/DVD-ROM SN-308B) Have I missed some mysterious settings? (Again, /has/ worked fine until now, never noticed any problems --- and still works fine with my /older/ DVD:s.) Any ideas whatsoever? Thanks, Kristian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dvd tv-out problem with X
Right ... Just installed kernel-image-2.6.4-1-686, and for some mysterious reason, the DVD:s just got several minutes longer. The previous kernel I used, 2.6.3, I had compiled myself. Obviously I did something wrong. :) Does anyone have any pointers as to where it went wrong? How was it possible that I could watch the better part of the DVD:s, and that they just `ended' before they should, /because of a kernel-setting/? h: Kristian Question II: This is a more trivial problem. I'm trying to play DVD's with my Samsung CD-RW/DVD -combo drive. Older DVD:s that I have work fine. Newer, however, all seem to `miss an ending' -- they just end abruptly, no credits, no nothing. Mplayer / xine just kind of state that `end of file', no more data. At first I thought it was faulty DVD:s, but now after I've tried *six different ones*, all showing the same `symptoms', I'm starting to doubt that something else might be going on ... Anyone else experiencing something similar? Have they started making DVD:s in some new way, creating DVD:s incompatible with my drive? (Samsung CD-RW/DVD-ROM SN-308B) Have I missed some mysterious settings? (Again, /has/ worked fine until now, never noticed any problems --- and still works fine with my /older/ DVD:s.) Any ideas whatsoever? Thanks, Kristian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problem: 2.6.x and network (e1000 Intel 82546EB)
Hi, after installing a fresh sarge on a Sun (dual XEON) with two e1000 Intel 82546EB Gigabit Ethernet Controller everything worked fine so far with the default 2.4.x kernel. But after changing to 2.6.x the network just does not work anymore. I use e1000 as the driver and the official kernel images (kernel-image-2.6.[34]-1-686-smp. Of course, I looked in /var/log/* for interesting messages, but got nothing out of it. rmmod e1000; modprobe e1000; /etc/init.d/networking restart gave Ignoring unknown interface eth0=hotplug and Ignoring unknown interface eth1=hotplug. Hotplug? Any ideas? Thanks in advance! -- W. Borgert [EMAIL PROTECTED], http://people.debian.org/~debacle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dvd tv-out problem with X
Hi, Question I: I've got this strange problem; tvout in X doesn't work any more -- works fine from shell though (i.e. `bashing' on tv works ;) ). I have a ATI Radeon 7500 Mobile card on a Dell Inspiron laptop, running Debian unstable (up to date). I'm using the package atitvout to `attach' tv (command atitvout -f t) The thing is, and the strange part, that everything worked fine a couple of days ago, Tuesday to be exact. So my guess is that some package, that has gotten updated since Tuesday, is causing this. Perhaps there's some really easy setting(s) that I have forgotten about? Does anyone feel like taking a guess as to what package might be causing this / what settings I could try? I have a feeling it has something to do with X, not atitvout, but I could (very well) be wrong. Can you think of a package that might have something to do with this? The only thing I've really added to Debian since then, is XFCE-4, including all recommended packages. (Don't see how that might have an effect?) *Everything looks fine, works fine*, except when looking at it through the tv. The commands I use to attach the tv is as they were when it worked, as is XF86Config-4 (I tried with a backup conf). Question II: This is a more trivial problem. I'm trying to play DVD's with my Samsung CD-RW/DVD -combo drive. Older DVD:s that I have work fine. Newer, however, all seem to `miss an ending' -- they just end abruptly, no credits, no nothing. Mplayer / xine just kind of state that `end of file', no more data. At first I thought it was faulty DVD:s, but now after I've tried *six different ones*, all showing the same `symptoms', I'm starting to doubt that something else might be going on ... Anyone else experiencing something similar? Have they started making DVD:s in some new way, creating DVD:s incompatible with my drive? (Samsung CD-RW/DVD-ROM SN-308B) Have I missed some mysterious settings? (Again, /has/ worked fine until now, never noticed any problems --- and still works fine with my /older/ DVD:s.) Any ideas whatsoever? Thanks, Kristian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
problem starting x
hello all firstly, i am not a member of the group. so, may i request you to send your replies to my e-mail address also? i have a hp pc running win xp. it has an hp72 monitor. from control panel - device managers following information is available. monitor - hp d 8904 display adapter - rage 128 pro gl i have made the system a double boot one by installing debian 3.0. the installation went on without any problem. however, now x refuses to start. i have attached the error file as well as the config file. could someone help me in setting it right? thanks in advance, sandip ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type man XF86Config-4 at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the ### BEGIN DEBCONF SECTION line above, and/or after the # ### END DEBCONF SECTION line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file? in /usr/share/doc/xfree86-common/FAQ.gz. Section Files FontPathunix/:7100# local font server # if the local font server has problems, we can fall back on these FontPath/usr/lib/X11/fonts/misc FontPath/usr/lib/X11/fonts/cyrillic FontPath/usr/lib/X11/fonts/100dpi/:unscaled FontPath/usr/lib/X11/fonts/75dpi/:unscaled FontPath/usr/lib/X11/fonts/Type1 FontPath/usr/lib/X11/fonts/Speedo FontPath/usr/lib/X11/fonts/100dpi FontPath/usr/lib/X11/fonts/75dpi EndSection Section Module LoadGLcore Loadbitmap Loaddbe Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadpex5 Loadrecord Loadspeedo Loadtype1 Loadvbe Loadxie EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc104 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/psaux Option Protocol PS/2 Option Emulate3Buttons true Option ZAxisMapping 4 5 EndSection Section InputDevice Identifier Generic Mouse Driver mouse Option SendCoreEventstrue Option Device/dev/input/mice Option Protocol ImPS/2 Option Emulate3Buttons true Option ZAxisMapping 4 5 EndSection Section Device Identifier Generic Video Card Driver i810 VideoRam8192 Option UseFBDev true EndSection Section Monitor Identifier Generic Monitor HorizSync 30-54 VertRefresh 50-85 Option DPMS EndSection Section Screen Identifier Default Screen Device Generic Video Card Monitor Generic Monitor DefaultDepth24 SubSection Display Depth 1 Modes 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes 800x600 640x480 EndSubSection SubSection Display Depth 24 Modes 800x600 640x480 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard InputDevice Configured Mouse InputDevice Generic Mouse EndSection Section DRI Mode0666 EndSection ### END DEBCONF SECTION This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted
Re: problem starting x
Hello Sandip P Deshmukh ([EMAIL PROTECTED]) wrote: firstly, i am not a member of the group. so, may i request you to send your replies to my e-mail address also? [XFree does not start with ATI rage 128 pr GL] (II) I810: Driver for Intel i810 chipset: i810, i810-dc100, i810e, i815 (II) Primary Device is: PCI 01:00:0 (EE) No devices detected. You try to use the wrong driver. I think you need to change it to ATI, you can check on xfree86.org under Support and Documentation. Run dpkg-reconfigure xserver-xfree86 and change the driver. Also try to set Use Kernel Framebuffer to no if still won't work with the correct driver. best regards Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 Registered Linux User #267976 http://www.andreas-janssen.de/debian-tipps.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem starting x
Sandip P Deshmukh wrote: What you told us you have . . . display adapter - rage 128 pro gl What you've told X you have . . . Section Device Identifier Generic Video Card Driver i810 VideoRam 8192 Option UseFBDev true EndSection What does lspci say you have? You might try running dpkg-reconfigure xserver-xfree86 and tell X to use ati or r128 (I'm not sure which you'll want). -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with X/icewm
#include hallo.h * Bob Parnes [Thu, Feb 19 2004, 09:03:37PM]: applications. XFree86.0.log has no error messages. I stopped the display manager (wdm) and started X from the console: same result, except that the console showed a long progression of lines, IceWm: Warning: glyph not found: XX where XX was a number. Apparently something was wiped out, but I don't know what it is. I upgraded icewm, but that did not help, so I assume Maybe something installed new or incompatible/broken fonts. Please try removing the last lines from /etc/X11/icewm/preferences and report whether it helps to [EMAIL PROTECTED] . Thanks, Eduard. -- DeVries Wann kommt Debian3.0? Jemand n ungefähres oder genaues Datum parat? Alfie DeVries: Wenn es fertig ist. Falky dwVries wenn es fertig ist weasel DeVries: ziemlich genau dann, wenn es fertig ist. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problem with X/icewm
Hello, I am running a combination of stable/testing, with icewm the window manager. On starting the system today, I found that all the text was missing from the popup menu, from the task bar, and from the title bar of applications. XFree86.0.log has no error messages. I stopped the display manager (wdm) and started X from the console: same result, except that the console showed a long progression of lines, IceWm: Warning: glyph not found: XX where XX was a number. Apparently something was wiped out, but I don't know what it is. I upgraded icewm, but that did not help, so I assume that something is missing from X. Fortunately, I backed up the system early in the month, and I have extra disk space, so I was able to restore the backup on a separate partition. The working system now is the same, except for applications downloaded since the backup. The ones installed yesterday, all from testing, are: upgrade of cupsys, cupsys-client, cupsys-bsd visual-tcl, itcl3 openoffice.org As it stands, I have the option of trying to fix what went wrong or installing these applications on the restored system. If someone can suggest what may have happened and whether I can fix the old system, I would be grateful. Thanks. -- Bob Parnes [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem with X
hey just want to say that X is working now. Wanted to thank eveyone who helped me. Thanks again. Clyde -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem with X
I have done some reading and I have commented out the lines in my XF86Config file load GLcore and load dri. It solved the problem with the errors I got in my XFree86 log. I am still having a problem with getting X up and running. I can get the Nvidia spash screen and then I get a black and white screen with a lot of dots on it and a black x for the mouse pointer. Then after a quick second it goes back to text mode. Here is my XFree86 log. I can not see what the problem is. Hopefully someone can give me a clue. Thanks Clyde This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.2.1.1 (Debian 4.2.1-12.1 20031003005825 [EMAIL PROTECTED]) / X\ Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 18 October 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.21-rc1-ac1-cryptoloop i686 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Sat Feb 7 20:17:38 2004 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Generic Monitor (**) | |--Device Generic Video Card (**) |--Input Device Generic Keyboard (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout se (**) XKB: layout: se (==) Keyboard: CustomKeycode disabled (**) |--Input Device Configured Mouse (WW) The directory /usr/lib/X11/fonts/CID does not exist. Entry deleted from font path. (WW) The directory /usr/lib/X11/fonts/cyrillic does not exist. Entry deleted from font path. (**) FontPath set to /usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/l\ib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi (==) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (WW) Open APM failed (/dev/apm_bios) (No such device) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.5 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.2.1.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.2.1.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8000480c, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,0305 card , rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,8305 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1106,0686 card 1106, rev 40 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1106,0571 card , rev 06 class 01,01,8a hdr 00 (II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 16 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 1106,3038 card 0925,1234 rev 16 class 0c,03,00 hdr 00 (II) PCI: 00:07:4: chip 1106,3057 card , rev 40 class 06,00,00 hdr 00 (II) PCI: 00:07:5: chip 1106,3058 card 1462,3300 rev 50 class 04,01,00 hdr 00 (II) PCI: 00:09:0: chip 1274,5000 card 4942,4c4c rev 00 class 04,01,00 hdr 00 (II) PCI: 00:0a:0: chip 10ec,8029 card , rev 00 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 10de,0111 card 1462,8829 rev b2 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.2.1.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) UnloadModule: scanpci (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) Host-to-PCI bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 00x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0
Re: problem with X
On February 7, 2004 11:45 am, Bytor the Destroyer wrote: I have done some reading and I have commented out the lines in my XF86Config file load GLcore and load dri. It solved the problem with the errors I got in my XFree86 log. I am still having a problem with getting X up and running. I can get the Nvidia spash screen and then I get a black and white screen with a lot of dots on it and a black x for the mouse pointer. Then after a quick second it goes back to text mode. Here is my XFree86 log. I can not see what the problem is. Hopefully someone can give me a clue. Thanks Clyde The white screen with a lot of dots means that you do indeed have X up and running. X is looking for a window manager or program to run and when it doesn't find one exits. Make sure you have KDE or Gnome or whatever window manager installed and then edit/create the .xsession file in your home directory. Mine looks as follows: exec wmaker # exec gnome-session # exec kde3 I uncomment what I feel like using that day. Some people prefer to use a display mamnager like kdm/gdm/xdm that logs you in and lets you select from a variety of installed window/session managers. hope this helps, R.J.P. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem with X
I have done some reading and I have commented out the lines in my XF86Config file load GLcore and load dri. It solved the problem with the errors I got in my XFree86 log. I am still having a problem with getting X up and running. I can get the Nvidia spash screen and then I get a black and white screen with a lot of dots on it and a black x for the mouse pointer. Then after a quick second it goes back to text mode. Here is my XFree86 log. I can not see what the problem is. Hopefully someone can give me a clue. Thanks Clyde This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.2.1.1 (Debian 4.2.1-12.1 20031003005825 [EMAIL PROTECTED]) / X\ Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 18 October 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.21-rc1-ac1-cryptoloop i686 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Sat Feb 7 20:17:38 2004 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Generic Monitor (**) | |--Device Generic Video Card (**) |--Input Device Generic Keyboard (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout se (**) XKB: layout: se (==) Keyboard: CustomKeycode disabled (**) |--Input Device Configured Mouse (WW) The directory /usr/lib/X11/fonts/CID does not exist. Entry deleted from font path. (WW) The directory /usr/lib/X11/fonts/cyrillic does not exist. Entry deleted from font path. (**) FontPath set to /usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/l\ib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi (==) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (WW) Open APM failed (/dev/apm_bios) (No such device) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.5 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.2.1.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.2.1.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8000480c, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,0305 card , rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,8305 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1106,0686 card 1106, rev 40 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1106,0571 card , rev 06 class 01,01,8a hdr 00 (II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 16 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 1106,3038 card 0925,1234 rev 16 class 0c,03,00 hdr 00 (II) PCI: 00:07:4: chip 1106,3057 card , rev 40 class 06,00,00 hdr 00 (II) PCI: 00:07:5: chip 1106,3058 card 1462,3300 rev 50 class 04,01,00 hdr 00 (II) PCI: 00:09:0: chip 1274,5000 card 4942,4c4c rev 00 class 04,01,00 hdr 00 (II) PCI: 00:0a:0: chip 10ec,8029 card , rev 00 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 10de,0111 card 1462,8829 rev b2 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.2.1.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) UnloadModule: scanpci (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) Host-to-PCI bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 00x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0
problem with X
i am running kernel 2.6.0 and sarge. I have a nvidia GForce 2MX. I have just installed the latest driver from nvidias web site. When I type startx I get the nvidia spash screen up and then after a couple of seconds I go directly back to text mode with the following showing XFree86 Version 4.2.1.1 (Debian 4.2.1-12.1 20031003005825 [EMAIL PROTECTED]) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 18 October 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.21-rc1-ac1-cryptoloop i686 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Thu Feb 5 17:22:23 2004 (==) Using config file: /etc/X11/XF86Config-4 (EE) Failed to load module GLcore (module does not exist, 0) Skipping /usr/X11R6/lib/modules/fonts/libspeedo.a:spencode.o: No symbols found Symbol __glXActiveScreens from module /usr/X11R6/lib/modules/extensions/libdri.a is unresolved! Symbol __glXActiveScreens from module /usr/X11R6/lib/modules/extensions/libdri.a is unresolved! (II) Initializing extension GLX I am wondering if anyone can help me out. Thanks Clyde -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem with X
On Thursday 05 February 2004 09:23, Bytor the Destroyer wrote: i am running kernel 2.6.0 and sarge. I have a nvidia GForce 2MX. I have just installed the latest driver from nvidias web site. When I type startx I get the nvidia spash screen up and then after a couple of seconds I go directly back to text mode with the following showing XFree86 Version 4.2.1.1 (Debian 4.2.1-12.1 20031003005825 [EMAIL PROTECTED]) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 18 October 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.21-rc1-ac1-cryptoloop i686 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Thu Feb 5 17:22:23 2004 (==) Using config file: /etc/X11/XF86Config-4 (EE) Failed to load module GLcore (module does not exist, 0) Skipping /usr/X11R6/lib/modules/fonts/libspeedo.a:spencode.o: No symbols found Symbol __glXActiveScreens from module /usr/X11R6/lib/modules/extensions/libdri.a is unresolved! Symbol __glXActiveScreens from module /usr/X11R6/lib/modules/extensions/libdri.a is unresolved! (II) Initializing extension GLX I am wondering if anyone can help me out. Thanks Clyde The (EE) line indicates X can't find the GLcore module. Mine is in /usr/ X11R6/lib/modules/extensions/libGLcore.a Do you have that file? What are its permissions? (mine are 0644). I don't use nvidia, so I'm not sure if it provides its own GLcore. If it does, it seems like X doesn't know where to find it. You might be able to just place it in the aforementioned directory, but I can't advise as to whether that's the preferred method. HTH. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem with X
The (EE) line indicates X can't find the GLcore module. Mine is in /usr/ X11R6/lib/modules/extensions/libGLcore.a Do you have that file? What are its permissions? (mine are 0644). HTH. Justin I can not seem to find the GLcore module. I look in /usr/X11R6/lib/modules/extensions/ but all I have is libdbe.a libextmod.a libglx.so.1.0.5336 libxtrap.a libdri.a libglx.so librecord.a How can I go about getting the GLcore module? Clyde -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem with X
On Thursday 05 February 2004 10:41, Bytor the Destroyer wrote: The (EE) line indicates X can't find the GLcore module. Mine is in /usr/ X11R6/lib/modules/extensions/libGLcore.a Do you have that file? What are its permissions? (mine are 0644). HTH. Justin I can not seem to find the GLcore module. I look in /usr/X11R6/lib/modules/extensions/ but all I have is libdbe.a libextmod.a libglx.so.1.0.5336 libxtrap.a libdri.a libglx.so librecord.a How can I go about getting the GLcore module? Clyde apt-file (or the Debian website search feature) is your friend here. apt-file shows GLcore comes from the package xserver-xfree86. Do you have that installed? If so, you might try a re-install. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem with X
Hello Bytor the Destroyer ([EMAIL PROTECTED]) wrote: The (EE) line indicates X can't find the GLcore module. Mine is in /usr/ X11R6/lib/modules/extensions/libGLcore.a Do you have that file? What are its permissions? (mine are 0644). I can not seem to find the GLcore module. I look in /usr/X11R6/lib/modules/extensions/ but all I have is libdbe.a libextmod.a libglx.so.1.0.5336 libxtrap.a libdri.a libglx.so librecord.a How can I go about getting the GLcore module? Clyde [EMAIL PROTECTED]:~$ locate libGLcore /usr/lib/libGLcore.so.1 /usr/lib/libGLcore.so.1.0.4363 with nvidia-driver 4363 best regards Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 Registered Linux User #267976 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem with X
On Thu, Feb 05, 2004 at 11:15:22AM -0700, Justin Guerin said On Thursday 05 February 2004 10:41, Bytor the Destroyer wrote: The (EE) line indicates X can't find the GLcore module. Mine is in /usr/ X11R6/lib/modules/extensions/libGLcore.a Do you have that file? What are its permissions? (mine are 0644). HTH. Justin I can not seem to find the GLcore module. I look in /usr/X11R6/lib/modules/extensions/ but all I have is libdbe.a libextmod.a libglx.so.1.0.5336 libxtrap.a libdri.a libglx.so librecord.a How can I go about getting the GLcore module? Clyde apt-file (or the Debian website search feature) is your friend here. apt-file shows GLcore comes from the package xserver-xfree86. Do you have that installed? If so, you might try a re-install. If (s)he's using the binary-only nvidia kernel module, (s)he also needs to use the binary-only nvidia X module. -- Rob Weir [EMAIL PROTECTED] | [EMAIL PROTECTED] | Do I look like I want a CC? Words of the day: high security Capricorn CID Treasury Fidel Castro SP4 bce signature.asc Description: Digital signature
problem with X
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problem with X cursor theme in KDE
Hello, I'm running Debian sid and recently did a dist-upgrade to KDE 3.1.5. It went well except my X cursor theme does not load anymore. I googled the problem and came across this http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=226545 Which about halfway down refrences this discussion http://lists.debian.org/debian-x/2004/debian-x-200401/msg00267.html I have attempted the corrections stated in those threads. Creating the sym link and installing the dev package. I still can not get my mouse theme to load/show except when waiting for a page to load in Mozilla the busy cursor is my mouse theme busy cursor. After the page is loaded it reverts back to the core cursor. My cursor theme is installed in ~/.icons/default Any hints, tips, or an outright fix welcomed :) thanks in advance eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problem mit X und Grafikkarte
Hi, Ich hoffe ich bin hier Richtig! I read I could write in german. If this is not correct, please send me a message (mailto:[EMAIL PROTECTED]). Ich habe auf meinen Rechner letztens Debian woody (r1) installiert. Nach der Konfiguartion von X mit hilfe von XF86config, wollte x starten, bekam jedoch folgende Fehlermeldung: (EE) No device detected Fatal server error no screen Ich habe versucht die BusID zu setzen wie mei der standart VGA, jedoch ohne Erfolg! (Die Fehlermeldung wurde Ergänzt durch: (ww) nv: No matching Device section for instance (BusID PCI 1:0:0:) found) mit cat /proc/pci wird die Karte jedoch angezeigt! Ich habe als Grafikkarte eine Geforce4 und das original XFree von woody (ver: 4.1.0.1) Kann mir einer weiterhelfen? - Danke! -- Best regards, Peter -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Problem mit X und Grafikkarte
Hallo Peter Kovacs ([EMAIL PROTECTED]) wrote: [XFree startet nicht] (Die Fehlermeldung wurde Ergänzt durch: (ww) nv: No matching Device section for instance (BusID PCI 1:0:0:) found) mit cat /proc/pci wird die Karte jedoch angezeigt! Ich habe als Grafikkarte eine Geforce4 und das original XFree von woody (ver: 4.1.0.1) Deine Karte wird von XFree 4.1 mit dem nv-Treiber nicht unterstützt. Das sagt die Fehlermeldung übrigens auch, denn im Output von startx bzw. im Log kannst Du nachlesen, welche Karten der Treiber kennt. Du kannst entweder den Vesa-Treiber verwenden, ein neueres XFree einspielen (www.apt-get.org) oder den Treiber von nvidia.com herunterladen und installieren. Wobei letzteres Dir auch 3D-Beschleunigung gibt. Die Frage wird hier regelmäßig gestellt, vielleicht schaust Du nächstes Mal erst ins Archiv, auf http://lists.debian.org oder http://groups.google.com, Gruppe linux.debian.user.german. Grüße Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 Registered Linux User #267976 -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
LINUX/AUROX 9.1. //Problem mit x-java-vm bei Mozilla
Hi, ich habe mir mal eure E-Mail Adressen zusammen gesucht, da ihr anderen schon mal in dieser Angelegenheit geholfen habt, Dachte ich mir ich schreibe euch mal an. Ich bin jetzt ca einen Monat beim Linux dabei, doch das ich das immer noch nicht geschaft habe ich weiß nicht mehr was ich machen soll... außer weiter zu Probieren. Eigendlich habe ich folgende 2 Prob`s: 1. Ich möchte Wissen, wie ich richtig vorgehen muß, um die Sache ins Lot zu bekomen! Ich will doch einfach nur das PlugIn (x-java-vm application) in den Mozilla implementieren 2. Das nächste ist eigendlich das selbe in grün nur mit einem Prog. Aber da schau ich erstmal selber befor ich anderen ihre Zeit klaue... Wenn mir einer von euch hilft, wäre ich sehr Dankbar! Gruß Mx... -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
LINUX/AUROX 9.1. //Problem mit x-java-vm bei Mozilla
Hi, ich habe mir mal eure E-Mail Adressen zusammen gesucht, nachdem wegen einer meiner Probleme mich umgeschaut habe. Da ihr anderen schon mal in dieser Angelegenheit geholfen habt, Dachte ich mir ich schreibe euch mal an. Kostet ja nichtsIch bin jetzt ca einen Monat beim Linux dabei, doch das ich das immer noch nicht geschaft habe ich weiß nicht mehr was ich machen soll... außer weiter zu Probieren. Eigendlich habe ich folgende 2 Prob`s: 1. Ich möchte Wissen, wie ich richtig vorgehen muß, um die Sache ins Lot zu bekomen! Ich will doch einfach nur das PlugIn (x-java-vm application) in den Mozilla implementieren 2. Das nächste ist eigendlich das selbe in grün nur mit einem Prog. Aber da schau ich erstmal selber befor ich anderen ihre Zeit klaue... Wenn mir einer von euch hilft, wäre ich sehr Dankbar! Gruß Mx... -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
another problem starting X with sarge-install
I did an install using the sarge install cd last night. Initially I was working on a very small installation because of my plans on setting up LVM. I installed the minimum software necessary. installed lvm10 using 'apt-get install lvm10' set up lvm disks. This went fine. Then I ran TaskSel and selected only the X-Window-Server. An interesting note to make here is that the installation and configuration was extremely fast and simple. However, there was one oddity in the X-Window-Server set-up that I didn't expect. Initially there was an autodetect made of my hardware, including my video card, all of which went fine. It completely recognized my video card and the memory available on my Matrox G400. At what I expect was the completion of the process, it started over again at the beginning asking me about my Geniric Video Card and how much memory it had. I assume this is an installation bug of the sarge-install process. Installed and configured all of those packages and tested X. X worked for both root and regular users. I was able to login using xdm and get to a twm (default) desktop as root and non-root users. I then ran dselect, which selected a number of files by default. I selected no other packages for installation except the package for msft fonts and continued with the install. After this completed, I rebooted (new kernel) and was able to start up xdm (did not start automatically). I could login using XDM to the WindowMaker desktop as root. As a non-root user, my login failed and I was sent back to the XDM login screen. Something was introduced of the MANY packages that has severely broken the X-Windows installation in a way that are a little difficult to debug because there are so many and I'm unable to find any specific errors that really have meaning. In every case there was an error about not being able to find mga_hal driver, but since it worked initially with this error I don't think it really matters and the 'EE' statement in XFree86.0.log is superficial. The only other 'EE' statement found was about a generic mouse configuration. Again, removing that configuration option in XF86Config-4 did nothing to fix the problem. At this point I will retry installation of Debian using only -stable packages to see if this can be set up correctly with those packages. I used this exact hardware for 4 years with Debian on it and only recently removed the installation. But now I'm unable to get back. ugh! I'm not sure where to go next. But I've been running without a workstation for almost two weeks and kind of need something. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: another problem starting X with sarge-install
Tom Allison wrote: I did an install using the sarge install cd last night. I installed the minimum software necessary. This went fine. Then I ran TaskSel and selected only the X-Window-Server. Initially there was an autodetect made of my hardware, including my video card, all of which went fine. It completely recognized my video card and the memory available on my Matrox G400. At what I expect was the completion of the process, it started over again at the beginning asking me about my Geniric Video Card and how much memory it had. Do you perhaps have two video cards in the system? Or is the G400 dual-headed? I assume this is an installation bug of the sarge-install process. Installed and configured all of those packages and tested X. X worked for both root and regular users. I was able to login using xdm and get to a twm (default) desktop as root and non-root users. I then ran dselect, which selected a number of files by default. I selected no other packages for installation except the package for msft fonts and continued with the install. After this completed, I rebooted (new kernel) and was able to start up xdm (did not start automatically). Odd that it did not start automatically. I could login using XDM to the WindowMaker desktop as root. As a non-root user, my login failed and I was sent back to the XDM login screen. Instead of using XDM, can you start X as a normal user with just the startx command? My first suspicion would be /etc/X11/Xwrapper.config having the line allowed_users=root instead of allowed_users=console. If so, you can change it manually or run dpkg-reconfigure xserver-common and properly answer the question about who can run X. At this point I will retry installation of Debian using only -stable packages to see if this can be set up correctly with those packages. Yikes! No need to reinstall. This is just an X issue, not an OS issue. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: another problem starting X with sarge-install
Tom Allison wrote: Do you perhaps have two video cards in the system? Or is the G400 dual-headed? No... Just one G400, single head. After this completed, I rebooted (new kernel) and was able to start up xdm (did not start automatically). Odd that it did not start automatically. Yes... it is. I could login using XDM to the WindowMaker desktop as root. As a non-root user, my login failed and I was sent back to the XDM login screen. Instead of using XDM, can you start X as a normal user with just the startx command? No I cannot run startx as normal user. My first suspicion would be /etc/X11/Xwrapper.config having the line allowed_users=root instead of allowed_users=console. If so, you can change it manually or run dpkg-reconfigure xserver-common and properly answer the question about who can run X. I was never asked, under Medium dialog, who could run this. I will check it when I get in front of my computer. If this does solve the matter, then I will consider filing a bugreport against the installation. Thanks for the suggestion. At this point I will retry installation of Debian using only -stable packages to see if this can be set up correctly with those packages. Yikes! No need to reinstall. This is just an X issue, not an OS issue. Normally true. But when I run into goofy stuff that I can't seem to identify after the experience overall and time on this one... It's faster to reinstall sometimes. This is a very new setup. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Installations-Problem von x-server
Hallo - vielleicht kann mir jemand bitte bei meinem Problem weiterhelfen?: Problembeschreibung: nach erfolgreicher Grund-Installation von Debian GNU/Linux 3.0 r1 Woody auf einem Intel Pentium PC konnte ich zunächst das System erfolgreich starten - auch habe ich eine entsprechende rescue-boot-disk erstellt. Als ich nun diverse anderen Programme mithilfe des Programmes tasksel nachinstallieren wollte habe ich mich zunächst auf das X-Windows-System konzentriert, und konnte schon während der Eingaben -für welche ich mich dann während dieser Installation in dem jeweiligen Auswahlmenue zu entscheiden hatte- feststellen, dass hierbei ein Abbruch -dieser Teil-installation (etwa bei Wahl eines falschen Wertes für den BS TAST etc)- gar nicht mehr möglich war. #8-| Nach Abschluß dieser Installation des x-Systems -mit offensichtlich unbrauchbaren Einstellungen- war ich nun nicht mehr in der Lage, den PC in einen gültigen Zustand zu booten. (auch nicht mit der rescue-disk) #8-( genauer: mithilfe der rescue-disk booted der Rechner zunächst mit Hilfe eines Standard-LinuxKernels Linux.bin danach schwenkt die ganze Sache auf die dann hierbei zu mountende hda1 um und lädt den Rest dieser konfiguration, auf welche ich bereits während dieses boot-Vorganges bereits keine Einfluß mehr vornehmen kann. Frage: wie muß ich diese Boot-diskette verändern- um wieder in diesen gültigen command-line-mode zu kommen um hier weider erneut die richtgen Installationen fahren zu können? - Oder gibt es hier vielleicht noch eine andere Möglichkeit das eine oder anderer nachinstallieren zu können. (eine Neuinstallation gestaltet sich hierbei etwas schwierig, als dass ich hier zunächst bei diesem REchner die FP erstmals mit Windo.. (lieber nicht) vor-formatieren müßte! ) Leider war hier auch nicht mit einer entsprechenden Tast-Kombination mehr weiterzukommen, als dass nicht nur der BS ungültig konfiguiert wurde, sondern auch die Tastatur (nach starten der entsprechenden windows-x-elemente) hier ebenfalls mir einfach ihren Dienst versagt hat. Vielen Dank für jeden Hinweis -hepa _ 5 neue Buddies = 50 FreeSMS. http://messenger-mania.msn.de MSN Messenger empfehlen und kräftig abräumen! -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Problem z X-ami
Po dzisiejszym upgrejdzie (sarge) nie wstja mi X-y. Log w zalaczniku. Konfiguracja fontow w XF86Config-4 jest na 100% dobra. Czy ktos mi moze pomoc, czy ma kots podobne objawy po dzisiejszym upgrade. Fatal server error: could not open default font 'fixed'; the X server's font paths might be misconfigured, remote font server(s) may be unreachable, and/or local fonts may not be installed or are not configured correctly. People inexperienced with the X Window System should have either the x-window-system or x-window-system-core packages installed. # apt-get install x-window-system-core # apt-get install x-window-system Other useful commands to run include: $ dpkg --status xserver-common $ dpkg --status xfonts-base $ zmore /usr/share/doc/xfree86-common/FAQ.gz When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED]
Re: Problem z X-ami
Użytkownik Grzegorz Kolorz napisał: Po dzisiejszym upgrejdzie (sarge) nie wstja mi X-y. mi nadal wstają ;) Log w zalaczniku. słaby ten log ;) Konfiguracja fontow w XF86Config-4 jest na 100% dobra. być może When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. ten zapewne wiecej powie, zagladałeś tam ??? -- 5E2F 6BEF 77EC A2FF 99C1 AB42 FD77 C1A5 4572 A858
Re: Problem z X-ami
On Wed, Oct 08, 2003 at 08:49:28PM +0200, Marcin Rosowski wrote: This can be found in the log file /var/log/XFree86.0.log. ten zapewne wiecej powie, zagladałeś tam ??? To co bylo w zalaczniku to wlasnie z tego pliku. Nie ma tam zadnych innych informacji o bledach. grzegorz
Re: Problem z X-ami
On Wed, Oct 08, 2003 at 08:59:34PM +0200, Grzegorz Kolorz wrote: Juz wszystko wrocilo do normy. Pomoglo przeinstalowanie na nowo pakietu xfonts-base. grzegorz
Re: Problem z X-ami
Użytkownik Grzegorz Kolorz napisał: On Wed, Oct 08, 2003 at 08:49:28PM +0200, Marcin Rosowski wrote: This can be found in the log file /var/log/XFree86.0.log. ten zapewne wiecej powie, zagladałeś tam ??? To co bylo w zalaczniku to wlasnie z tego pliku. Nie ma tam zadnych innych informacji o bledach. ..jeżeli tak naprawde wyglada ten log to jedyny pomysł jaki mam to brak wolnego miejsca na dysku lub zabity XFS ? -- 5E2F 6BEF 77EC A2FF 99C1 AB42 FD77 C1A5 4572 A858
Re: Problem with X
Hello Hooman ([EMAIL PROTECTED]) wrote: --- Andreas Janssen [EMAIL PROTECTED] wrote: However, If you didn't do it, please first try to turn off the Kernel framebuffer option as Stephane already proposed. Many nvidia cards won't work if it is activated. How exactly should I turn framebuffer off? I didn't find any item about framebuffer in XF86config-4 file. Look out for this option in the Device Section: Option UseFBDev true Comment it out or set it to false. Or, as already proposed, use dpkg-reconfigure xserver-xfree86 and select no when debconf asks for the option. best regards Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 Registered Linux User #267976 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with X
--- Andreas Janssen [EMAIL PROTECTED] wrote: Hello Hooman ([EMAIL PROTECTED]) wrote: --- Andreas Janssen [EMAIL PROTECTED] wrote: However, If you didn't do it, please first try to turn off the Kernel framebuffer option as Stephane already proposed. Many nvidia cards won't work if it is activated. How exactly should I turn framebuffer off? I didn't find any item about framebuffer in XF86config-4 file. Look out for this option in the Device Section: Option UseFBDev true Comment it out or set it to false. Or, as already proposed, use dpkg-reconfigure xserver-xfree86 and select no when debconf asks for the option. best regards Andreas Janssen Hi, Thanks a lot. Finally, I could boot with Gnome or any other Windows manager. Now I have another problem(s). First, when I want to login as root from login screen, the system doesn't let me in and issues an error message. Why is that? I tried other Windows manager sessions like X-window, KDE, .. but still I can't login as root. Second, how can I change monitor resoloution from Gnome menus? These are the questions for now. Special thanks to Andreas and Glenn Regards, = Hooman A newbie in Linux world __ Post your free ad now! http://personals.yahoo.ca -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
