dselect wants to uninstall everything?
Hello ! I am new in Debian. And I have a problem similar to the one of Brian. I also have a fresh stable woody (installed today). And I did the folling steps : 1 - 'apt-get install harden' to securise my system 2 - 'apt-get install kde' 3 - I tried dselect and I selected a package called fam (I'm quite sure of the name of the package, but not at 100%). This package conflits with harden. 4 - So I reselected harden to undo my choice. Here dselect wanted to remove kde Why does harden conflits with kde after the step 4, but not between steps 2 and 3 ? I hope my english is understandable. Thanks for help, Prakash _ On Monday 02 December 2002 17:49, Brian Kendig wrote: I have a fresh install of Debian Linux 3.0. I want to use dselect to install some additional packages... but it appears that, by default, dselect wants to *uninstall* most of my Debian installation, unless I go through the list by hand and tell it to keep each installed package! I run 'dselect' from a command line and I can get it to load and display the list of available packages. But if I don't change the list of packages at all, and instead go directly to the 'install' option, then it tries to deinstall hundreds of packages (including basic stuff like 'at' and 'adduser' and 'cpp' and 'dc'). If I go back to the 'select' list and try to tell it to keep any of these packages, it complains about dependency problems and lists a lot of packages which seem to have nothing to do with the one I'm trying to keep prevent being deleted. What the heck am I doing wrong here? How do I get dselect to simply leave alone the stuff I've already got installed, and just let me select new packages to install? You have some dependancies which are unsatified. dselect try to make your system coherent. Maybe some of your packages depends on other packages which are not avaible. What is your sources.list file? You will not be able to use dselect with broken dependancies, which is not a bad thing: a broken dependancy make a package unusable. I suggest you to check the dependancy with "apt-cache unmet" and to repair your system by hand using "apt-get install" to install a new package and "dpkg deinstall" to deinstall package. By the way, what medium have you used to install your system. The default installation with the CD's does not have this kind of problems. When you use dselect for the first time, it try to install packages (and you should accept). It may be also a solution to reinstall compltetly your system with the CD's. Possibly after having made a backup of your important file. Install the package you want and accept all dselect suggestions according to the dependancies. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Wrong size with ls
Hi ! I've just installed a Debian Woody (stable) and I encourtered something strange in my '/var/log' directory. When using both the '-l' and '-s' options of 'ls', the sizes given are incoherent. For information, 'du -k' gives the same sizes as 'ls -s'. pc-atinf2:/var/log(58)ls -lsk total 1024 32 -rw-r--r--1 root root24082 Dec 7 20:57 XFree86.0.log 4 drwxr-xr-x2 root root 4096 Dec 7 14:08 aide/ 48 -rw-r-1 root adm 16411 Dec 7 21:02 auth.log 272 -rw-r--r--1 root root 242805 Dec 7 21:03 daemon.log 4 -rw-r--r--1 root root 1219 Dec 7 20:57 debug 8 -rw-r--r--1 root root 7287 Dec 7 12:02 dmesg 4 drwxr-s---2 mail adm 4096 Dec 7 11:08 exim/ 16 -rw-r--r--1 root root 530664 Dec 7 20:37 faillog 124 -rw-r--r--1 root root 121772 Dec 7 11:42 installer.log 8 -rw-r--r--1 root root 7066 Dec 7 11:42 installer.timings 92 -rw-r--r--1 root root66927 Dec 7 20:57 kdm.log 16 -rw-r--r--1 root root15232 Dec 7 20:57 kern.log 4 drwxr-xr-x2 root root 4096 Dec 7 14:54 ksymoops/ 24 -rw-rw-r--1 root utmp 6456412 Dec 7 20:59 lastlog ... I tried to fix it with 'fsck' on the '/var' partition, but this program told me everything is ok. Has anyone already had this problem ? Is it a bug or a wrong installation from my part ? TIA, Prakash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Wrong size with ls
Thanks ! I understand know why the file lastlog takes only 24 1k-block instead of 6306. That's because there are a lot of zeros it. 24 -rw-rw-r--1 root utmp 6456412 Dec 7 20:59 lastlog Prakash ___ [EMAIL PROTECTED] (Bob Proulx) writes: Disk blocks used and size of files are related only in that the latter will always be less than the former on an uncompressed filesystem. Not quite. Files on (most) Unix filesystems can contain "holes". If there's a large block of zeros in a file, and the file is created in the right way (like by seeking to a position and then writing) the blocks containing zeros don't actually take up space on disk. If you copy or tar files like that, you may need to specify an option to allow sparse files. -- Alan Shutko <[EMAIL PROTECTED]> - In a variety of flavors! Language is a human virus from outer space. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
libGL
Hi, I asked this question on the french list two weeks ago, but didn't have any answer :( When I launch an application which use libGL (openoffice, glGo, licq, glxinfo, etc.) I have the following error message (even if the application works) : libGL error: drmMap of sarea failed What should I do to solve this problem ? TIA, -- Prakash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: libGL
Hi, First, here is the result of glxinfo with the libGL debug flag : bash-2.05a$ export LIBGL_DEBUG=1 bash-2.05a$ glxinfo name of display: :0.0 libGL error: drmMap of sarea failed display: :0 screen: 0 direct rendering: No server glx vendor string: SGI server glx version string: 1.2 server glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context client glx vendor string: SGI client glx version string: 1.2 client glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context GLX extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context OpenGL vendor string: VA Linux Systems, Inc. OpenGL renderer string: Mesa GLX Indirect OpenGL version string: 1.2 Mesa 3.4.2 OpenGL extensions: GL_ARB_multitexture, GL_EXT_abgr, GL_EXT_blend_color, GL_EXT_blend_minmax, GL_EXT_blend_subtract glu version: 1.3 glu extensions: GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat -- 0x23 24 tc 0 24 0 r y . 8 8 8 0 0 24 0 0 0 0 0 0 0 None 0x24 24 tc 0 24 0 r y . 8 8 8 0 0 24 8 0 0 0 0 0 0 Slow 0x25 24 tc 0 24 0 r y . 8 8 8 0 0 24 0 16 16 16 0 0 0 Slow 0x26 24 tc 0 24 0 r y . 8 8 8 0 0 24 8 16 16 16 0 0 0 Slow 0x27 24 dc 0 24 0 r y . 8 8 8 0 0 24 0 0 0 0 0 0 0 None 0x28 24 dc 0 24 0 r y . 8 8 8 0 0 24 8 0 0 0 0 0 0 Slow 0x29 24 dc 0 24 0 r y . 8 8 8 0 0 24 0 16 16 16 0 0 0 Slow 0x2a 24 dc 0 24 0 r y . 8 8 8 0 0 24 8 16 16 16 0 0 0 Slow Señor Bazo Agujereado a écrit: Is there any other error output in Xfree86*log? You may see something like 'drm: initialization failed' or 'DRI: not enabled' or some such. If that is the case, then the problem is that DRI/DRM is not being enabled for your graphics card. These modules allow hardware accelleration in X. That's strange, most of the lines about dri and drm are OK (begin with "(II)"). But there is only one failure in XFree86.1.log : (==) R128(0): Write-combining range (0xe400,0x100) (II) R128(0): [drm] drmSetBusid failed (6, PCI:1:0:0) (EE) R128(0): [dri] DRIScreenInit failed. Disabling DRI. (II) R128(0): Memory manager initialized to (0,0) (1280,3276) (II) R128(0): Reserved area from (0,1024) to (1280,1026) (II) R128(0): Largest offscreen area available: 1280 x 2250 (==) R128(0): Backing store disabled (==) R128(0): Silken mouse enabled (II) R128(0): Using XFree86 Acceleration Architecture (XAA) The problem may be that: - You are using two monitors, and X isn't able to use DRI with two monitors with the current driver, or I've only got one monitor. - The agp chipset driver for your motherboard isn't being loaded. For example. my mb agp bridge is ' [AMD] AMD-751 [Irongate] AGP Bridge', and I need to load the 'amd_k7_agp' module The chipset driver wasn't loaded (I thought that CONFIG_KMOD=1 automatically loads needed modules in the kernel). So I loaded the module via-agp (I've got a VIA apollo KT266 series mainboard, so I guess it's the right module) with insmod (modprobe surprisingly doesn't work with the kernel 2.6.8), restarted the X server. But the error persists. I also tried amd-k7-agp and ati-agp modules. - DRI is turned off in XFree86Config (check for 'load dri', 'load glx' in section 'Module') dri and glx are loaded in the XFree Configuration file You might want to check out the DRI wiki for more help: http://dri.sourceforge.net/cgi-bin/moin.cgi/ Have you recently changed anything with your configuration, or added a new graphics card? It's an old error, but when it appeared I didn't have time to handle it. -- Prakash PS : Thanks having cc-ed me as I'm not on the list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: libGL
Hi, Pene Chamuscado del Caballo a écrit: Yes, this means that DRI and DRM are not being initialized. I had the same problem, but I can't remember the exact steps I took to resolve it. I beleive you need to load the module 'agpgart' if it is not already built into the kernel, and then load your agp chipset module 'via-agp' if that is the correct one. agpgart is already built in the kernel. And I think via-agp is the right module. I'm not sure :) But make sure you did a make modules_install as root, that should set up the module dependencies properly. I compiled the kernel with kernel-package which handled it. After you have loaded the module, check the output of dmesg to see if it successfully detected your chipset. I get something like: agpgart: Detected AMD Irongate chipset agpgart: Maximum main memory to use for agp memory: 176M agpgart: AGP aperture is 64M @ 0xe800 ... agpgart: Found an AGP 1.0 compliant device at :00:00.0. agpgart: Putting AGP V2 device at :00:00.0 into 1x mode agpgart: Putting AGP V2 device at :01:05.0 into 1x mode The module seems to be loaded : $ lsmod Module Size Used by ati_agp 6476 0 amd_k7_agp 5836 0 via_agp 7168 1 ... But I haven't got the same message (the second part misses): $ dmesg | grep agp Linux agpgart interface v0.100 (c) Dave Jones agpgart: Detected VIA KT266/KY266x/KT333 chipset agpgart: Maximum main memory to use for agp memory: 96M agpgart: AGP aperture is 64M @ 0xe000 I tried glxinfo with tcsh and I obtained the following information : $ setenv LIBGL_DEBUG verbose $ glxinfo > /dev/null libGL: XF86DRIGetClientDriverName: 4.0.1 r128 (screen 0) libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/r128_dri.so libGL: XF86DRIGetClientDriverName: 4.0.1 r128 (screen 0) drmOpenByBusid: busid is PCI:1:0:0 drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 4, (OK) drmOpenByBusid: drmOpenMinor returns 4 drmOpenByBusid: drmGetBusid reports PCI:1:0:0 libGL error: drmMap of sarea failed Finally, I read the DriTroubleshooting, (http://dri.sourceforge.net/cgi-bin/moin.cgi/) but there were no information about my problem. It helped me to detect an unresolved symbol: $ grep unresolved /var/log/XFree86.0.log Symbol fbdevHWGetLineLength from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! (DRI is loaded in XF86Config-4 and libglx.so isn't present on my computer.) I don't agree the sentence : "If you've made it this far, glxinfo should be printing direct rendering: Yes" Have you got any more ideas ? TIA, -- Prakash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
