Re: SL5 installation on AMD processor#8207;
Hi, Thank you for the detail. From what I see, the hardware is supported on SL 5.5. From the description of the sounds and symptoms, I believe you are having hardware problems, particularly the hard drive. I would look in /var/log/messages and see if there is anything there dealing with your hard drives. I don't have an example right now of what to look for, maybe someone else has some log examples of hard drives going bad. Troy Rhykie Ron wrote: Hi, Here are the outputs for cat /proc/cpuinfo and lspci commands, respective ly: * /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 17 model : 3 model name : AMD Athlon(tm)X2 DualCore QL-66 stepping: 1 cpu MHz : 1100.000 cache size : 512 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush mmx fxsr sse sse2 ht nx mmxext fxsr_opt lm 3dnowext 3dnow constant_tsc nonstop_tsc pni cx16 lahf_lm cmp_legacy svm extapic cr8legac y 3dnowprefetch osvw ts ttp tm stc 100mhzsteps hwpstate [8] bogomips: 2751.92 processor : 1 vendor_id : AuthenticAMD cpu family : 17 model : 3 model name : AMD Athlon(tm)X2 DualCore QL-66 stepping: 1 cpu MHz : 1100.000 cache size : 512 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush mmx fxsr sse sse2 ht nx mmxext fxsr_opt lm 3dnowext 3dnow constant_tsc up nonstop_tsc pni cx16 lahf_lm cmp_legacy svm extapic cr8legacy 3dnowprefetch osvw ts ttp tm stc 100mhzsteps hwpstate [8] bogomips: 2751.92 *** lspci 00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge 00:01.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (int gfx) 00:04.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 0) 00:07.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 3) 00:09.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 4) 00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] 00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Contro ller 00:12.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller 00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Control ler 00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Contro ller 00:13.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller 00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Control ler 00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3a) 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) 00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller 00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge 00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 Contro ller 00:18.0 Host bridge: Advanced Micro Devices [AMD] Mobile K10 [Turion X2, Athlon X2, Sempron] HyperTransport Configuration (rev 40) 00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 11h [Turion X2, Athlon X2, Sempron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] Mobile K10 [Turion X2, Athlon X2, Sempron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] Mobile K10 [Turion X2, Athlon X2, Sempron] Miscellaneous Control 00:18.4 Host bridge: Advanced Micro Devices [AMD] Mobile K10 [Turion X2, Athlon X2, Sempron] Link Control 01:05.0 VGA compatible controller: ATI Technologies Inc RS780M/RS780MN [Radeon HD 3200 Graphics] 02:00.0 Ethernet controller: Marvell Technology Group Ltd. Unknown device 4357 (rev 10) 06:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 0 1) Actually, the system boots up fine, but sometimes some sounds comes as though there is a problem inside, and i am able to log in. When opening t he browser and scrolling through the page the browser just goes off; the sam e thing happens when dealing with PDF files. I was firstly using using SL5.4, but then i had the problem of audio soun d and the previously mentioned problems, and also the system making those clutching sound during booting and shutting down. I moved to SL5.5 and the only thing that has improved being the audio. cheers -- __ Troy Dawson daw...@fnal.gov (630)840-6468 Fermilab ComputingDivision/LSCS/CSI/USS Group __
Re: TESTING - openafs update for SL5
On Jul 8, 2010, at 19:11 , Dag Wieers wrote: On Thu, 8 Jul 2010, Troy Dawson wrote: Dag Wieers wrote: On Thu, 8 Jul 2010, Troy Dawson wrote: With many minor releases, we update the version of openafs for that minor release. This new version then get's pushed out to the rest of the releases. With SL 5.5 we updated openafs to 1.4.12, and we are about to push that version out to the rest of the SL5 releases. It currently is in testing, and it has passed every updating test I could think to throw at it and it updated without any problems. We plan on pushing this out on Monday - 12 July 2010 To test or update SL5 --- yum --enablerepo=sl-testing update kernel-module-openafs\* or you can download rpm's by hand at http: //ftp.scientificlinux.org/linux/scientific/5rolling/testing/i386/openafs/ http: //ftp.scientificlinux.org/linux/scientific/5rolling/testing/x86_64/openafs/ Would there be any interest if we provided kmod-openafs modules that are kernel-agnostic (or kABI-tracking as we say) from ELRepo ? The advantage is that the modules keep on working through kernel-updates, which makes update-cycles (and maintenance) to be less work. I am tempted to create those packages, but without an interested party that can provide sufficient testing the effort is kinda moot. Let me know, I thought that the openafs kernel modules didn't work well with kABI, but I would love to find that incorrect. If you think it is possible, please build it, and I'm certain we'll have plenty of testers. If that is true we might have a discussion with Red Hat to see whether we can have those symbols as part of the kABI whitelist. Let's find out :-) There are symbols missing from the whitelist, so there was no way to use kABI-tracking modules cleanly. That being said, it probably would have worked. If someone has the time, it would be really interesting to force the module built for the SL5.0 GA kernel into -194.8.1 and see whether that works. The guy in charge at Red Hat (Jon Masters) seems very openminded, so talking to them is certainly worth the effort. I have my doubts though whether there's any chance to have the whitelist extended while it still matters. For SL5, I'd like to stick with what we have with the supported release, but I'm very sure that we would have plenty of users wiling to test and use the kmod-openafs module. If everything goes well, we could offer it as an alternative. For SL6, if this works we could use that and save us from having to create kernel modules with each kernel update. Sure, I don't want to force anyone anyway. A clean upgrade path will be very hard due to the fact that these kernel-module packages have the kernel-version in the name. So your position makes a lot of sense. That's my point of view as well. SL5 should not drop the kernel-module packages (at least not anytime soon), but having kmods for testing would be very useful. With SL6, AFAIK, the whitelist problem is going to vanish, and IMO we should use kABI for the next major release if at all possible. We should also make an effort to (re-)unite the SL/Elrepo/... packaging with the one from openafs.org. And Christof Hanke, who's crafting the OpenSuSE RPMs, also expressed interest in a unified spec during the European AFS Workshop in Rome last autumn. This is probably the time to actually try getting there. It may turn out that it's not feasible, but let's try. Opinions? -- -- dag wieers, d...@wieers.com, http://dag.wieers.com/ -- [Any errors in spelling, tact or fact are transmission errors] -- Stephan Wiesand DESY -DV- Platanenenallee 6 15738 Zeuthen, Germany
Re: TESTING - openafs update for SL5
On 14/07/10 20:06, Stephan Wiesand wrote: On Jul 8, 2010, at 19:11 , Dag Wieers wrote: If that is true we might have a discussion with Red Hat to see whether we can have those symbols as part of the kABI whitelist. Let's find out :-) There are symbols missing from the whitelist, so there was no way to use kABI-tracking modules cleanly. That being said, it probably would have worked. If someone has the time, it would be really interesting to force the module built for the SL5.0 GA kernel into -194.8.1 and see whether that works. The guy in charge at Red Hat (Jon Masters) seems very openminded, so talking to them is certainly worth the effort. I have my doubts though whether there's any chance to have the whitelist extended while it still matters. Jon requested we file bugs for missing symbols for the third party kmod drivers we have built. Please feel free to use the existing bug to report/log further symbols: https://bugzilla.redhat.com/show_bug.cgi?id=520891
Terrabyte file systems and SL5.0
For the first time I will be using a 1-2 Terrabyte hard drive on any SL release, in particular, on an older SL5.0 (boron) OS. There's plenty on the web about pros and cons for larger file systems (resier, xfs, ext3, ext4, ...). I've usually stayed with ext3 (200-500 Gb HD that are NFS mounted to linux or windows using MS windows for unix). So, vanilla; not too splashy a set up. No clusters. I've not used LVM. I think my question is which of these choices is as well developed, mature, and easy to use as ext3 for the SL5.0 boron version of SL? I'm most familiar with ext3 and do these stray IT tasks as needed, so I've not kept up on the latest and greatest. Thanks for any comments, Bill Lutter
Re: Terrabyte file systems and SL5.0
On Wed, Jul 14, 2010 at 06:31:48PM -0700, Isaac wrote: Well, ext3 will supposedly work with up to 16 TB in RHEL5, so SL should have similar limits. I can confirm that at least a 7 TB ext3 filesystem is possible. I have one 8x1TB RAID5 array running ext3 built with stock SL ext3 tools. I cannot confirm the 16 TB limit. Can you point us to a reference somewhere? Here is my information: I looked into this several years ago when building an 11 TB filesystem. The SL mke2fs refused to make an ext3 filesystem that big and it turned out that mke2fs sources had a hardwired limit of 8 TB maximum filesystem size. Instead, I made an 11 TB XFS filesystem and it is still running just fine thank you very much. -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
