-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Bob Hoffman Sent: Friday, October 07, 2011 9:14 PM To: CentOS mailing list Subject: [CentOS] CentOS 6 is a bear

Gotta say, centos has been tough to install and get working.

The anaconda installer makes large drive setups horridly tedious (especially if reinstalling a lot).

Package selection seems a bit off...

I did a virtualization package, no custom..did not install qemu, libvirt, and all attempts to do any virtualization failed due to non-installed packages.

Then I decided to select all the virtualization packages in custom, but had selected 'web server' as the base package. I was never able to connect to the net here at home...apparently some things with 'modprobe' did not install and the eth devices 'does not exist' or something like that.

Then I decided on the entire gnome package, with all the bells and whistles...everything worked, but who wants that? I removed some packages in gnome to see and reboot made machine dead. Did that 4 different times with very few package removals.

Did a number of various tries with custom selections, but the dependencies seem to not be grabbing all it needs to work. Never got a non gnome setup to recognize eth devices (well, one time, but it never was able to get the net).

I just installed a custom set up, all virtualization packages- virtualization selected as base. I added some gnome stuff and a few other doo dads.....booted up..went right to the command line.... no virt software works, errors everywhere. Display will not come up (x, vnc, or gnome no matter what)..

Every installation, in first boot up had major missing or odd problems. One time I booted up with a gnome set up and selinux was stopping 5 differetn gdm programs..at boot...due to security risks... wtf?

Any attempt to disable or make selinux permissive results in a dead machine, unable to ever boot again (left one up for 12 hours, never came back up, thought it was relabeling, but no message.)

Removing packages with the gnome running only worked about 10% of the time, all others resulted in dead machine at reboot.

I am considering, the only way to actually install and use this as a virtualized host is to go full desktop and hope the selinux enforcing will not break the system (with all the programs it will not let run on boot)...

I have never, not once, been able to connect to the net in the command line setups...I know how to configure eths, network, dns, etc...not once, not even dhcp..config eth0 up, etc.. Gnome has not a single issue with the same exact file setups.. Many command line setups would not even see the eth devices, something about modprobe this or that not installed.....wth?

quite an interesting task. I have now taken the server out of the center and am just going to endlessly install until I get a system that is low resources and actually allows the virtualization to work.

My last install, with all virt packages selected...?..... cannot run virt-manager, libvirt, though some virt programs do work...why? something each needed to run was not installed as a dependency....<smacks head>

Reinstalling would not be so bad, but the anaconda installer does not quite set up the drives the same on a reinstall forcing a deletion of partitions and redoing the entire setup..quite annoying

/rant off _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

Dooood!!

I'm not the sharpest knife in the drawer, but I initally installed CentOS 6.0 as a desktop and added from there. After that, I uninstalled the 'fluff'.

here is just a small sample of the errors in the messages log after initial boot....... I think there is a bug with the video, something to do with grub according to peeps on the net. I want to get rid of abrtd but the computer will never start again if I do..which does not make sense. errors with network manager, gtk warngings, selinux has 5 things it wants to stop from running.. this is all at a first boot and second boot... welcome to centos 6

these here literally make a hundred or so appearances in different forms Oct 7 23:39:04 main kernel: [drm:radeon_i2c_sw_put_byte] *ERROR* i2c 0x08 0x3b write failed Oct 7 23:39:04 main kernel: [drm:r100_bandwidth_update] *ERROR* You may not have enough display bandwidth for current mode Oct 7 23:39:04 main kernel: If you have flickering problem, try to lower resolution, refresh rate, or color depth Oct 7 23:39:46 main kernel: composite sync not supported

Oct 7 23:38:47 main abrtd: Can't load public GPG key /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-auxiliary Oct 7 23:38:47 main abrtd: Can't load public GPG key /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-beta-2 Oct 7 23:38:47 main abrtd: Can't load public GPG key /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-legacy-beta Oct 7 23:38:47 main abrtd: Can't load public GPG key /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-legacy-former Oct 7 23:38:47 main abrtd: Can't load public GPG key /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-legacy-release Oct 7 23:38:47 main abrtd: Can't load public GPG key /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-legacy-rhx Oct 7 23:38:47 main abrtd: Init complete, entering main loop Oct 7 23:38:47 main kernel: [drm:radeon_i2c_sw_put_byte] *ERROR*

Oct 7 23:39:13 main gdm-simple-greeter[2948]: Gtk-WARNING: gtkwidget.c:5460: widget not within a GtkWindow Oct 7 23:39:13 main rtkit-daemon[2961]: Sucessfully made thread 2959 of process 2959 (/usr/bin/pulseaudio) owned by '42' high priority at nice level -11. Oct 7 23:39:44 main NetworkManager[2258]: <error> [1318045184.982544] [nm-manager.c:1312] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name Oct 7 23:39:45 main NetworkManager[2258]: <error> [1318045185.234050] [nm-manager.c:1312] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name Oct 7 23:39:46 main kernel: fuse init (API version 7.13) Oct 7 23:39:49 main setroubleshoot: SELinux is preventing gdm-session-wor "read write" access on root. For complete SELinux messages. run sealert -l 61e6aeb2-d3a0-4bab-be99-f3a0e4f705f0 Oct 7 23:39:49 main setroubleshoot: SELinux is preventing gdm-session-wor "read write" access on .xsession-errors. For complete SELinux messages. run sealert -l 02e77817-cb29-411f-9337-30c296d5cc7e Oct 7 23:39:49 main setroubleshoot: SELinux is preventing gdm-session-wor "remove_name" access on .xsession-errors. For complete SELinux messages. run sealert -l 5b8b16b9-339a-4b8f-aaef-4ab911a30857 Oct 7 23:39:49 main setroubleshoot: SELinux is preventing gdm-session-wor "remove_name" access on .xsession-errors. For complete SELinux messages. run sealert -l 5b8b16b9-339a-4b8f-aaef-4ab911a30857 Oct 7 23:39:50 main setroubleshoot: SELinux is preventing gdm-session-wor "remove_name" access on .xsession-errors. For complete SELinux messages. run sealert -l 5b8b16b9-339a-4b8f-aaef-4ab911a30857 Oct 7 23:39:50 main setroubleshoot: SELinux is preventing gdm-session-wor "create" access on .xsession-errors. For complete SELinux messages. run sealert -l e3fe44e2-c58f-4aeb-88d8-8f3531a00cfa Oct 7 23:39:50 main setroubleshoot: SELinux is preventing gdm-session-wor "create" access on .xsession-errors. For complete SELinux messages. run sealert -l e3fe44e2-c58f-4aeb-88d8-8f3531a00cfa Oct 7 23:39:50 main setroubleshoot: SELinux is preventing gdm-session-wor "setattr" access on .xsession-errors. For complete SELinux messages. run sealert -l 15201ed3-3f1a-40c0-a0d2-a91bb5c55f9a Oct 7 23:39:51 main kernel: composite sync not supported Oct 7 23:39:51 main kernel: composite sync not supported Oct 7 23:47:36 main kernel: composite sync not supported Oct 7 23:47:36 main kernel: composite sync not supported

On 10/8/11, Bob Hoffman bob@bobhoffman.com wrote:

Gotta say, centos has been tough to install and get working.

The anaconda installer makes large drive setups horridly tedious (especially if reinstalling a lot).

I usually try to speed reinstall up by using small / and not reformating /home. Not sure if it would be useful in your case.

That said, I haven't had all the troubles you have on my sole C6 test server, before and after installing the desktop package.

Any attempt to disable or make selinux permissive results in a dead machine, unable to ever boot again (left one up for 12 hours, never came back up, thought it was relabeling, but no message.)

This is rather odd, I only ever had problems with selinux set to enforcing. It should be relabelling if you had disabled it. Could there be some problem with your server hardware that's throwing you off with all these spurious problems?

I have never, not once, been able to connect to the net in the command line setups...I know how to configure eths, network, dns, etc...not once, not even dhcp..config eth0 up, etc.. Gnome has not a single issue with the same exact file setups.. Many command line setups would not even see the eth devices, something about modprobe this or that not installed.....wth?

Do you happen to be using an Intel NIC ? Several of us were having problems until we switched to using the kmod drivers from elrepo.

On 08.10.2011 5:14, Bob Hoffman wrote:

Gotta say, centos has been tough to install and get working.

The anaconda installer makes large drive setups horridly tedious (especially if reinstalling a lot).

Package selection seems a bit off...

I did a virtualization package, no custom..did not install qemu, libvirt, and all attempts to do any virtualization failed due to non-installed packages.

Then I decided to select all the virtualization packages in custom, but had selected 'web server' as the base package. I was never able to connect to the net here at home...apparently some things with 'modprobe' did not install and the eth devices 'does not exist' or something like that.

Then I decided on the entire gnome package, with all the bells and whistles...everything worked, but who wants that? I removed some packages in gnome to see and reboot made machine dead. Did that 4 different times with very few package removals.

Did a number of various tries with custom selections, but the dependencies seem to not be grabbing all it needs to work. Never got a non gnome setup to recognize eth devices (well, one time, but it never was able to get the net).

I just installed a custom set up, all virtualization packages- virtualization selected as base. I added some gnome stuff and a few other doo dads.....booted up..went right to the command line.... no virt software works, errors everywhere. Display will not come up (x, vnc, or gnome no matter what)..

Every installation, in first boot up had major missing or odd problems. One time I booted up with a gnome set up and selinux was stopping 5 differetn gdm programs..at boot...due to security risks... wtf?

Any attempt to disable or make selinux permissive results in a dead machine, unable to ever boot again (left one up for 12 hours, never came back up, thought it was relabeling, but no message.)

Removing packages with the gnome running only worked about 10% of the time, all others resulted in dead machine at reboot.

I am considering, the only way to actually install and use this as a virtualized host is to go full desktop and hope the selinux enforcing will not break the system (with all the programs it will not let run on boot)...

I have never, not once, been able to connect to the net in the command line setups...I know how to configure eths, network, dns, etc...not once, not even dhcp..config eth0 up, etc.. Gnome has not a single issue with the same exact file setups.. Many command line setups would not even see the eth devices, something about modprobe this or that not installed.....wth?

quite an interesting task. I have now taken the server out of the center and am just going to endlessly install until I get a system that is low resources and actually allows the virtualization to work.

My last install, with all virt packages selected...?..... cannot run virt-manager, libvirt, though some virt programs do work...why? something each needed to run was not installed as a dependency....<smacks head>

Reinstalling would not be so bad, but the anaconda installer does not quite set up the drives the same on a reinstall forcing a deletion of partitions and redoing the entire setup..quite annoying

/rant off _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

Would you summarize what problems with NIC(s) do you have? Its model/chip and kernel log (dmesg) would be nice as well.

In case this is Intel EXPI9301CTBLK NIC (according to your YT profile), which is seemed to be 82574L based, you should take into account known issues with stock e1000e module shipped with C6.0 [1] and that chip.

//br

1. http://lists.centos.org/pipermail/centos/2011-September/118027.html