Discuss

discuss@lists.centos.org

34753 discussions

Strange behavior in X, esp. VMWare Windows
by Mark Hull-Richter 01 May '07

01 May '07

Last Thursday, for some reason (possibly a power failure), my work desktop had a different video configuration than when I left Wednesday evening. I have two 17" flat panels configured as a two-head wide (side-by-side) single display. When I arrived on Thu, I had two individual desktops instead, the resolution was down to 800x600, and so on. The monitor type had been reset to generic 800x600, and the vido card was unknown. (This was not true before.) After a lot of fooling around with the xorg.conf file, I finally got it back to where it should be, for the most part. My current xorg.conf is included below. The problem is that I typically run certain apps on the right screen, including seamonkey and Windows under VMWare workstation, and since the new configuration came in, the mouse cursor is not where it should be. Items light up when I run the mouse over them, but a little below and to the right of the tip of the pointer. It is only a slight dislocation, but significantly worse in the Windows on VMWare, and it is really annoying when I have to mis-aim the cursor to hit certain selections (check boxes, bullets, etc.). Can anyone explain this? Here's my xorg.conf: # Xorg configuration created by system-config-display Section "ServerLayout" Identifier "Default Layout" Screen 0 "aticonfig-Screen[0]" 0 0 Screen "aticonfig-Screen[1]" RightOf "aticonfig-Screen[0]" InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" Option "Xinerama" "on" Option "Clone" "off" EndSection Section "Files" # RgbPath is the location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. # Multiple FontPath entries are allowed (they are concatenated together) # By default, Red Hat 6.0 and later now use a font server independent of # the X server to render fonts. RgbPath "/usr/X11R6/lib/X11/rgb" FontPath "unix/:7100" EndSection Section "Module" Load "dbe" Load "extmod" Load "fbdevhw" Load "glx" Load "record" Load "freetype" Load "type1" Load "dri" EndSection Section "InputDevice" # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) # Option "Xleds" "1 2 3" # To disable the XKEYBOARD extension, uncomment XkbDisable. # Option "XkbDisable" # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use: # Option "XkbModel" "pc102" # If you have a US Microsoft Natural keyboard, you can use: # Option "XkbModel" "microsoft" # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # Option "XkbLayout" "de" # or: # Option "XkbLayout" "de" # Option "XkbVariant" "nodeadkeys" # # If you'd like to switch the positions of your capslock and # control keys, use: # Option "XkbOptions" "ctrl:swapcaps" # Or if you just want both to be control, use: # Option "XkbOptions" "ctrl:nocaps" # Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "yes" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Dell 1704FPT (Digital)" HorizSync 30.0 - 81.0 VertRefresh 56.0 - 76.0 Option "dpms" EndSection Section "Monitor" Identifier "Monitor1" VendorName "Monitor Vendor" ModelName "Dell 1704FPT (Digital)" HorizSync 30.0 - 81.0 VertRefresh 56.0 - 76.0 Option "dpms" EndSection Section "Monitor" Identifier "aticonfig-Monitor[0]" VendorName "ATI Proprietary Driver" ModelName "LCD Panel 1280x1024" HorizSync 31.5 - 67.0 VertRefresh 50.0 - 75.0 Option "DPMS" "true" EndSection Section "Monitor" Identifier "aticonfig-Monitor[1]" VendorName "ATI Proprietary Driver" ModelName "Generic Autodetecting Monitor" Option "DPMS" "true" EndSection Section "Device" Identifier "Videocard0" Driver "vesa" VendorName "Videocard vendor" BoardName "VESA driver (generic)" EndSection Section "Device" Identifier "aticonfig-Device[0]" Driver "fglrx" BoardName "Unknown video card" BusID "PCI:1:0:0" EndSection Section "Device" Identifier "aticonfig-Device[1]" Driver "fglrx" BusID "PCI:1:0:0" Screen 1 EndSection Section "Screen" # SubSection "Display" # Viewport 0 0 # Depth 16 # Modes "800x600" "640x480" # EndSubSection Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480" EndSubSection EndSection Section "Screen" Identifier "aticonfig-Screen[0]" Device "aticonfig-Device[0]" Monitor "aticonfig-Monitor[0]" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480" EndSubSection EndSection Section "Screen" Identifier "aticonfig-Screen[1]" Device "aticonfig-Device[1]" Monitor "aticonfig-Monitor[1]" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection Section "DRI" Group 0 Mode 0666 EndSection -- Mark Hull-Richter, Linux Kernel Engineer DATAllegro (www.datallegro.com) 85 Enterprise, Second Floor, Aliso Viejo, CA 92656 949-680-3082 - Office 949-330-7691 - fax

3 4

BlueZ
by clorden＠altern.org 01 May '07

01 May '07

Hello all. Does anyone know how to get bluetooth working on CentOS 5? I can't pair any device. Things work perfectly on CentOS 4. Here is what happens: root@miho ~]# /etc/rc.d/init.d/bluetooth start Starting Bluetooth services: [ OK ] [root@miho ~]# hcitool scan Scanning ... 00:12:EE:XX:XX:XX K750i [root@miho ~]# hcitool cc 00:12:EE:XX:XX:XX [root@miho ~]# hcitool auth 00:12:EE:XX:XX:XX HCI authentication request failed: Input/output error I got no PIN requester on either phone and PC. On the same time on another console I have: [root@miho ~]# hcidump HCI sniffer - Bluetooth packet analyzer ver 1.32 device: hci0 snap_len: 1028 filter: 0xffffffff (scan) < HCI Command: Inquiry (0x01|0x0001) plen 5 > HCI Event: Command Status (0x0f) plen 4 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 > HCI Event: Inquiry Complete (0x01) plen 1 (connect) < HCI Command: Create Connection (0x01|0x0005) plen 13 > HCI Event: Command Status (0x0f) plen 4 > HCI Event: Connect Complete (0x03) plen 11 < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2 > HCI Event: Command Status (0x0f) plen 4 < HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4 > HCI Event: Read Remote Supported Features (0x0b) plen 11 > HCI Event: Command Complete (0x0e) plen 6 < HCI Command: Remote Name Request (0x01|0x0019) plen 10 > HCI Event: Command Status (0x0f) plen 4 > HCI Event: Max Slots Change (0x1b) plen 3 > HCI Event: Remote Name Req Complete (0x07) plen 255 (auth) < HCI Command: Authentication Requested (0x01|0x0011) plen 2 > HCI Event: Link Key Request (0x17) plen 6 > HCI Event: Command Status (0x0f) plen 4 < HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6 > HCI Event: Command Complete (0x0e) plen 10 > HCI Event: PIN Code Request (0x16) plen 6 < HCI Command: PIN Code Request Negative Reply (0x01|0x000e) plen 6 > HCI Event: Auth Complete (0x06) plen 3 > HCI Event: Command Complete (0x0e) plen 10 On CentOS 4 things work perfectly: [root@miho ~]# hcidump HCIDump - HCI packet analyzer ver 1.11 device: hci0 snap_len: 1028 filter: 0xffffffff (scan) < HCI Command: Inquiry (0x01|0x0001) plen 5 > HCI Event: Command Status (0x0f) plen 4 > HCI Event: Inquiry Result (0x02) plen 15 > HCI Event: Inquiry Result (0x02) plen 15 > HCI Event: Inquiry Result (0x02) plen 15 > HCI Event: Inquiry Result (0x02) plen 15 > HCI Event: Inquiry Result (0x02) plen 15 > HCI Event: Inquiry Result (0x02) plen 15 > HCI Event: Inquiry Result (0x02) plen 15 > HCI Event: Inquiry Result (0x02) plen 15 > HCI Event: Inquiry Result (0x02) plen 15 > HCI Event: Inquiry Result (0x02) plen 15 > HCI Event: Inquiry Result (0x02) plen 15 > HCI Event: Inquiry Result (0x02) plen 15 > HCI Event: Inquiry Result (0x02) plen 15 > HCI Event: Inquiry Result (0x02) plen 15 > HCI Event: Inquiry Result (0x02) plen 15 > HCI Event: Inquiry Result (0x02) plen 15 > HCI Event: Inquiry Result (0x02) plen 15 > HCI Event: Inquiry Result (0x02) plen 15 > HCI Event: Inquiry Result (0x02) plen 15 > HCI Event: Inquiry Complete (0x01) plen 1 < HCI Command: Remote Name Request (0x01|0x0019) plen 10 > HCI Event: Command Status (0x0f) plen 4 > HCI Event: Remote Name Req Complete (0x07) plen 255 (connect) < HCI Command: Create Connection (0x01|0x0005) plen 13 > HCI Event: Command Status (0x0f) plen 4 > HCI Event: Connect Complete (0x03) plen 11 < HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4 > HCI Event: Command Complete (0x0e) plen 6 > HCI Event: Max Slots Change (0x1b) plen 3 (auth) < HCI Command: Authentication Requested (0x01|0x0011) plen 2 > HCI Event: Link Key Request (0x17) plen 6 > HCI Event: Command Status (0x0f) plen 4 < HCI Command: Link Key Request Reply (0x01|0x000b) plen 22 > HCI Event: Command Complete (0x0e) plen 10 > HCI Event: PIN Code Request (0x16) plen 6 < HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23 > HCI Event: Command Complete (0x0e) plen 10 > HCI Event: Link Key Notification (0x18) plen 23 > HCI Event: Auth Complete (0x06) plen 3 Does anyone have any idea!? Something seems to have changed with the new BlueZ version (2.10 vs. 3.7)... Thanks! --Clorden

1 0

hi
by Dave 01 May '07

01 May '07

Hi I just joined I have a serer who's purpose life is to be a fileserver/print server right now it is running windows 98 because it is an older computer look at an alternate os such as this will this allow windows based machines to talk to it save files retrieve files and also how difficult is it to install.

9 18

Making rpm from tar.gz
by Ioannis Vranos 01 May '07

01 May '07

OS: CentOS 5 x86. I have read in some places that we can make an rpm package from tar.gz, by issuing rpmbuild -ta. However it doesn't seem to work. Any hints?

8 9

Intel G965 chipset + ICH8
by Yoshizumi HAYAKAWA 01 May '07

01 May '07

Hello everyone ! I will buy a new PC for CentOS 5.0. I install Linux on PC for the first time. I do not have the skill of it. Here are my candidates of mabo : Intel DG965WH Intel DG965YCK Intel DG965WHMKR ASUS P5B-V All mabos have Intel G965 chipset + ICH8 Did anyone succeed to install CentOS 5.0 on these mabos, and to set up network configuration ? Could you give me any information about how to install CentOS 5.0 ? Thanks in advance. HAYAKAWA

2 1

Re: CentOS 4.4 - added disk prevents system from booting past initrd
by Simen Timian Thoresen 01 May '07

01 May '07

centos-request(a)centos.org wrote: ... > > Thus fsck'ing /dev/sda1 does not bring any useful. But why? > > > > Why does the initrd insist on fsck'in /dev/sda1, when it should check > > LABEL=/? > > > > Is there something I'm not getting here? > it should be a grub problem: even if filesystems are now labelled, > grub enumerates present hard drives ... and have the same problems > than Lninux with sda becoming sdb. > Its configuration file (SATA:/boot/grub/menu.lst) should be updated as > well, especially the root keyword. > > grub is launched from the first bootable drive (/dev/sdb) that is saw > as disk hd(1) I guess. > > So in its configuration file, you should duplicate the default entry > (when installed on SATA standalone disk) and change "root hd(0,1)" > into "root hd(1,1)" > > To achieve it, boot from CD/DVD in rescue mode, mount manually your > /boot (in / perhaps) and edit /boot/grub/menu.lst > > my $0.02 > > Pierre Bourgin Hi Pierre, I thought about grub (but have not tried changing anything there yet), but am a bit uncertain if grub is the issue as - the BIOS boots the SATA disk, and reads the grub bootloader. - The grub bootloader loads both the kernel and the correct initrd - The kernel is told to mount LABEL=/ as root - It is while executing something in the initrd that system decides to fsck /dev/sda1 - Once /dev/sda1 is fsck-able (ie after changing the partition layout), the system boots without issues. The filesystem on /dev/sda1 does not at any time contain anything useful (it started out as just being an extended partition, and now is completely empty. At no time did it have any label set). Yours, -S -- Simen Thoresen, Dolphin ICS Systems Administration and Wulfkit Support

2 1

problem with centos 4.4 and the time´s pc
by Orlando Mederos 01 May '07

01 May '07

I install centos 4.4 in a serveraltos9100, every thing was ok, but the watch´s time on the system is going very fast, the second goin very fast. The time in the bios setup is ok, the time go fine, but when I booting the centos 4.4 , the time is wrong, I repair with the command date, but minuts later all is crazy again Please I need help. Note: the time Zone is ok, this is set correctly with my country zone Este Mensaje se encuentra libre de Virus, Chequeado por MDaemon AntiVirus: AVirus: v2.2.7 Fuente del motor de AV: Alt-N Technologies, Ltd (excellent) Versión del motor de AV: 4.0.1.14 Servidor de Correo "Hotel Tuxpan".Varadero.Cuba

1 0

Intel G965 chipset + ICH8 for CentOS 5.0
by Yoshizumi HAYAKAWA 01 May '07

01 May '07

2 1

CentOS 5 single DVD for i386 and x86_64
by Luciano Miguel Ferreira Rocha 01 May '07

01 May '07

Hello, I'd like to announce a release of a CentOS 5 DVD image, with i386 and x86_64 installations. This is an independent work, so please don't bother CentOS lists with bugs related to the installer only. Summary of changes: * i686 and x86_64 install from a single dvd (automatic detection on boot) * updates as of 2007-04-26 * no kdelibs-api-docs, openoffice.org, tetex-doc and most *-javadoc sha1sum: 63885249695c60a87443e304212d6cf9af678165 centos5_32and64.iso md5sum: 0db291c3e4f7dc4fb4e6ea052b77e95d centos5_32and64.iso torrent: ftp://ftp.gil.di.uminho.pt/pub/users/strange/centos/c5_32+64.torrent iso: ftp://ftp.gil.di.uminho.pt/pub/users/strange/centos/centos5_32and64.iso Detailed changes: * All rpms are the originals from CentOS 5. However, the *.i386.rpm and *.noarch.rpm for the x86_64 are the ones from the i386 DVD, not from the x86_64, as the contents are the same and the rpm headers differ only on the Build Date and/or Signature. * each install (x86_64 or i386) only has knowledge of rpms originally in their DVDs, so x86_64 installs won't be bloated with more i386 packages than the originals. * Some packages are missing. It's a pity some subpackages that don't depend on %arch are still built as .%arch.rpm, but there's nothing I'm willing to do about that. The missing packages are: - openoffice.org - tetex-doc - kdelibs-apidocs - Deployment_Guide, except for en_US and pt-BR - *-javadoc, except for: - java-1.4.2-gcj-compat-javadoc (required by eclipse) - bsh-javadoc and xmlrpc-javadoc (part of java-devel group) Note that both Deployment_Guide and openoffice.org have updates, so if you don't care about kdelibs-apidocs, tetex-doc and *-javadoc, you can still use this image as a local base. * The updates as of 2007-04-26 from CentOS replace their originals: - autofs-5.0.1-0.rc2.43.0.2 - bind-9.3.3-8 - cups-1.2.4-11.5.1 - Deployment_Guide-(en-US and pt_BR)-5.0.0-21 - dhcp-3.0.5-5 - ekiga-2.0.2-7.0.2 - emacs-21.4-18.1 - evolution-data-server-1.8.0-15.0.2 - file-4.17-9 - firefox-1.5.0.10-2.el5 - freetype-2.2.1-17 - gcc-4.1.1-52.el5.2 - gnupg-1.4.5-13 - kernel-2.6.18-8.1.1 - krb5-1.5-23 - libwpd-0.8.7-3 - libX11-1.0.3-8.0.1 - libXfont-1.2.2-1.0.2 - module-init-tools-3.3-0.pre3.1.16.0.1 - net-snmp-5.3.1-14.0.1 - nss-3.11.5-3.el5 - php-5.1.6-11 - postgresql-8.1.8-1 - samba-3.0.23c-2.el5.2 - spamassassin-3.1.8-2 - squid-2.6.STABLE6-4 - thunderbird-1.5.0.10-1.el5 - tzdata-2007d-1 - virt-manager-0.2.6-7.0.2 - wireshark-0.99.5-1 - xen-3.0.3-25.0.3 - xorg-x11-apps-7.1-4.0.1 - xorg-x11-server-1.1.1-48.13.0.1 - yelp-2.16.0-14.0.1 * automatic detection on boot for i386 or x86_64 install - default label linux now calls com32 module l32or64 (attachment l32or64.c) that selects 32 or 64 bits kernel according to long_mode flag in cpuid - new boot targets linux32 and linux64 that force 32 bit or 64 kernel * single 32 bits initrd for i386 and x86_64 - new /init (attachment renmod.c), that symlinks /modules to the correct version - /modules.i386 with the original modules from the i386 initrd - /modules.x86_64 with the original modules from the x86_64, but with the paths in modules.cgz changed to $kver/i686/ instead of the original $kver/x86_64/, as the anaconda loader was looking there for the modules (it's probably ignoring the run-time arch and relying on the compile time one) - the space savings from using a single initrd aren't that much (1.5), so using the two separated initrds is still feasible (and l32or64 supports it), but the x86_64 initrd needs it's .buildstamp replaced with the one from i386. * single 32 bits minstage2 and stage2 - anaconda support for space separated list of available archs in .discinfo (attachment discinfo.patch) (anaconda has at least 4 different places where it parses the .discinfo file. something should be done about that!) - yum support for repodata.%arch location (attachment repodata.arch.patch): -> repodata.i386 and repodata.x86_64 (there was a supposed fallback to repodata if no repodata.%arch existed, but it didn't work in my tests, so you won't be able to use these stages with original repositories for network installs (ln -s repodata repodata.x86_64 or repodata.i386 should be enough, though)) - runtime replacing of usr/lib/rpm/macros with the correct one for the arch (attachment rpm_macros.patch) usr/lib/rpm/macros.i386 from i386/images/stage2/usr/lib/rpm/macros usr/lib/rpm/macros.x86_64 from x86_64/images/stage2/usr/lib/rpm/macros ln -fs /tmp/rpmmacros usr/lib/rpm/macros - symlinks for directories or files with i386/i686 in their name, with i386/i686 replaced with x86_64 (not sure if this was needed, but I didn't feel like making more tests): ln -s i686-redhat-linux-gnu etc/gtk-2.0/x86_64-redhat-linux-gnu ln -s i386-redhat-linux-gnu etc/pango/x86_64-redhat-linux-gnu ln -s keymaps-override-i386 usr/lib/anaconda-runtime/keymaps-override-x86_64 ln -s screenfont-i386.gz usr/lib/anaconda-runtime/screenfont-x86_64.gz ln -s i386-redhat usr/share/grub/x86_64-redhat To recreate the image with your own packages or comps.xml: 1. populate the CentOS rpm directory with the rpms of your choosing; 2. call createrepo in the iso root dir: createrepo -g path_to_comps.xml . 3. rename repodata to repodata.i386 or repodata.x86_64 and fix the relative paths in repodata.%arch/repomd.xml: perl -pi -e 's/repodata/repodata.i386/g' repodata.i386/repomd.xml 4. repeate for the other arch. 5. create the iso: mkisofs -o ../centos5_32and64.iso -b isolinux/isolinux.bin \ -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table \ -r -pad -J -joliet-long -V "CentOS" . 6. add checksum to iso: implantisomd5 ../centos5_32and64.iso 7. record it: growisofs -Z /dev/cdrom=../centos5_32and64.iso -- lfr 0/0

1 1

Installed CentOS 5 today, question about an error I'm getting
by Preston Crawford 01 May '07

01 May '07

So I did a fresh install today. Decided to go ahead and upgrade. Everything seems okay save for three problems. #1 - I get a message during boot saying that an Intel microcode update didn't work. Something about not being able to find /proc/microcode. #2 - I can't use the Firefox extension HTML Parser. Anyone use this. #3 - Off and on GDM crashes and I get dropped into a prompt. Any ideas? Preston

3 6

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss