How did your 5.4-->5.5 upgrade(s) go?

General support questions including new installations
User avatar
AlanBartlett
Forum Moderator
Posts: 9345
Joined: 2007/10/22 11:30:09
Location: ~/Earth/UK/England/Suffolk
Contact:

Re: How did your 5.4-->5.5 upgrade(s) go?

Post by AlanBartlett » 2010/06/04 19:59:56

[quote]
Another question, is that I have noticed that both the 32-bit and 64-bit versions are installed.
I have a 64-bit install of CentOS and so would expect only to see the 64-bit versions of the applications unless I had specifically installed 32-bit or that was the only version available, but I wouldn't expect to see both.
[/quote]
Please see [url=http://wiki.centos.org/FAQ/General#head-357346ff0bf7c14b0849c3bcce39677aaca528e9]FAQ #22[/url].

cwatson
Posts: 134
Joined: 2007/10/02 18:55:02

Re: How did your 5.4-->5.5 upgrade(s) go?

Post by cwatson » 2010/06/10 03:33:48

1) 64-bit server at work updated without any issues
2) 64-bit workstation at home, same as above
3) 32-bit laptop at home: everything seems to be fine, except I had to exclude system-config-securitylevel because I kept getting this message:
[code]
file /usr/share/locale/zh_TW/LC_MESSAGES/system-config-securitylevel.ko from install of system-config-securitylevel-1.6.29.1-5.el5.i386
conflicts with file from package system-config-securitylevel-tui-1.6.29.1-2.1.el5.i386
[/code]

User avatar
AlanBartlett
Forum Moderator
Posts: 9345
Joined: 2007/10/22 11:30:09
Location: ~/Earth/UK/England/Suffolk
Contact:

Re: How did your 5.4-->5.5 upgrade(s) go?

Post by AlanBartlett » 2010/06/10 13:09:43

[b]Chris[/b] -- (3) Is odd. I suggest --

[code]
[b]yum remove system-config-securitylevel system-config-securitylevel-tui
yum install system-config-securitylevel system-config-securitylevel-tui[/b]
[/code]
Please open a new thread if the above doesn't resolve the oddity.

cwatson
Posts: 134
Joined: 2007/10/02 18:55:02

Re: How did your 5.4-->5.5 upgrade(s) go?

Post by cwatson » 2010/06/10 16:30:05

Hi Alan, I was worried about doing that because it said it would remove "firstboot" and a couple other things because of dependencies. If I am just going to re-install though, it shouldn't be a problem, right?

Thanks,
Chris

User avatar
AlanBartlett
Forum Moderator
Posts: 9345
Joined: 2007/10/22 11:30:09
Location: ~/Earth/UK/England/Suffolk
Contact:

Re: How did your 5.4-->5.5 upgrade(s) go?

Post by AlanBartlett » 2010/06/10 18:23:53

Keep a note of what will be removed with those packages -- [i]firstboot[/i] is only really essential at the first reboot following an installation -- and just re-install them.

cwatson
Posts: 134
Joined: 2007/10/02 18:55:02

Re: How did your 5.4-->5.5 upgrade(s) go?

Post by cwatson » 2010/06/11 00:56:36

Yes, that worked. Thanks Alan!

cyberbot
Posts: 31
Joined: 2010/02/12 18:25:26

Re: How did your 5.4-->5.5 upgrade(s) go?

Post by cyberbot » 2010/06/16 14:52:23

mine didnt goes well,
my Yum is not working anymore, i am behind proxy,

User avatar
MikeDuncan
Posts: 9
Joined: 2010/05/20 19:53:09
Location: Annandale, VA
Contact:

Re: How did your 5.4-->5.5 upgrade(s) go?

Post by MikeDuncan » 2010/08/19 02:36:07

My mileage is certainly different on this,,,
:-) one system, an eMachines T4200 upgraded via yum smoothly with no hiccups and has given me no problems.

:-o a second machine, a Dell E521, is giving me a severe headache and appears to be experiencing a udev error that was common back in RHEL 3. I have looked around the forums and the Net and don't see any comments later than about 2008.

So, 5.4 boots and runs with no problems, I have noapic specified in grub.conf. I can boot that kernel at any time.

I upgraded to 5.5 via yum and now have a kernel panic on boot. Tech details below. Being curious, I pulled out my DVDs for x32 and x64 5.5 to see what if anything would be different if I booted from them. The x64 version absolutely won't boot. The x32 version boots correctly and will install on the E521. However, once installed, I get the same kind of panic that I got from the yum upgraded version.

I spent some time trying to figure out if there were any additional options besides noapic that I could try in grub.conf. No joy. Maybe someone can shed some useful light on this issue?

Summation: kernel-2.6.18-164.el5 boots just fine, but kernel-2.6.18-194.11.1.el5 always panics when it gets to the udev routines. Since there was no logging, I took photos with my iPhone and I can supply the jpgs via email. Two of the panics that I photographed occurred during _uinput.sh which may have been me trying to enter "I".

By having quick fingers during the boot process, I managed (once) to type "I" at the right point in time and somehow got past the udev panic. The data below is from that one successful boot. I also have a lengthy dmesg file that details the system diagnostics from 2.6.18-194.11.1.el5. I can provide that via email rather than clutter up this message.

[code]
== BEGIN uname -rmi ==
2.6.18-194.11.1.el5 i686 i386
== END uname -rmi ==

== BEGIN rpm -q centos-release ==
centos-release-5-5.el5.centos
== END rpm -q centos-release ==

== BEGIN getenforce ==
Enforcing
== END getenforce ==

== BEGIN rpm -qa kernel\* | sort ==
kernel-2.6.18-164.el5
kernel-2.6.18-194.11.1.el5
== END rpm -qa kernel\* | sort ==

== BEGIN lspci ==
00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:05.0 VGA compatible controller: nVidia Corporation C51 [GeForce 6150 LE] (rev a2)
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3)
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
04:07.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
== END lspci ==

== BEGIN lspci -n ==
00:00.0 0500: 10de:02f0 (rev a2)
00:00.1 0500: 10de:02fa (rev a2)
00:00.2 0500: 10de:02fe (rev a2)
00:00.3 0500: 10de:02f8 (rev a2)
00:00.4 0500: 10de:02f9 (rev a2)
00:00.5 0500: 10de:02ff (rev a2)
00:00.6 0500: 10de:027f (rev a2)
00:00.7 0500: 10de:027e (rev a2)
00:02.0 0604: 10de:02fc (rev a1)
00:03.0 0604: 10de:02fd (rev a1)
00:04.0 0604: 10de:02fb (rev a1)
00:05.0 0300: 10de:0241 (rev a2)
00:09.0 0500: 10de:0270 (rev a2)
00:0a.0 0601: 10de:0260 (rev a3)
00:0a.1 0c05: 10de:0264 (rev a3)
00:0a.2 0500: 10de:0272 (rev a3)
00:0b.0 0c03: 10de:026d (rev a3)
00:0b.1 0c03: 10de:026e (rev a3)
00:0e.0 0101: 10de:0266 (rev a1)
00:0f.0 0101: 10de:0267 (rev a1)
00:10.0 0604: 10de:026f (rev a2)
00:10.1 0403: 10de:026c (rev a2)
00:18.0 0600: 1022:1100
00:18.1 0600: 1022:1101
00:18.2 0600: 1022:1102
00:18.3 0600: 1022:1103
04:07.0 0200: 14e4:170c (rev 02)
== END lspci -n ==
[/code]
Regards, Mike

User avatar
MikeDuncan
Posts: 9
Joined: 2010/05/20 19:53:09
Location: Annandale, VA
Contact:

Re: How did your 5.4-->5.5 upgrade(s) go?

Post by MikeDuncan » 2010/08/19 23:38:01

Regarding the previous post about the Dell E521 not booting with 5.5 x86, I found a solution. Buried in an old (2006) Dell forum, there were a number of comments about the USB chipset causing problems. One of the recommended solutions was to use ACPI=noirq as a boot parameter. It worked! :-)

It's clear to me that I won't be able to run the 64bit version of CentOS 5.5 on this motherboard without disabling the USB chipset and possibly using a PCI USB board. I'm not sure that this machine is worth that level of effort. Strangely enough, I was able to run the 64bit version of SOLARIS 10 x86 for about 3 years with only one persistent USB mouse related quirk.

Best Regards,
Mike

User avatar
MikeDuncan
Posts: 9
Joined: 2010/05/20 19:53:09
Location: Annandale, VA
Contact:

Re: How did your 5.4-->5.5 upgrade(s) go?

Post by MikeDuncan » 2010/08/21 03:13:15

Regarding the comment about the x86_64 kernel not booting, tonight I found a June, 2009 post on the Fedora Forum by RLK that said "We've used 64-bit CentOS 5 on Dell Dimension E521 desktops for a while now and they work fairly well, once you realise you need "pci=noacpi udevtimeout=10" on the command line for any kernels you install that is!"

Well, doh! That sounded pretty good to me. First I tried it by changing my x86 5.5 grub.conf and it worked much better than what I had previously tried. Then I tried booting the install cdrom using it and it worked just fine. Now, I'm doing a full x86_64 install and hope to proceed into production status after some testing.

Regards,
Mike

Post Reply