Re: [CentOS] died again
On 12/6/2013 11:09 PM, Michael Hennebry wrote: I noticed the TPM 1.2 . Am I going have to start dealing with the trusted computing crap when I get another computer? TPM is totally optional to use. it can be used so your system can establish a chain of trust with a server or network or whatever, but there's absolutely no requirement to use it.it also can be used as a trust store for secureboot and full disk encryption... If the OS has been secured this way, and you reset the TPM via the BIOS, you will have to reformat the disks to use them. we looked at TPM for authenticating unattended clients making ssl connections, but getting all that working just so seemed a little too sketchy so we abandoned the idea. -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] died again
On 12/6/2013 11:47 PM, Eliezer Croitoru wrote: The TPM can be an issue but once you install the OS(LINUX) on DISK(maybe on another machine) it should fly by default. What is the meaning of Trusted by HP\COMPAQ? I do not know yet. From what I understand a Refurbished means Used and was used in a company\office the last time before being tested in lab. refurbs can also be open box mechandise. retail product returns. at dell outlet, a lot of the systems they sell are production overruns and order cancellations. XYZ Corp ordered 30 of a specific configuration Latitude E7440, then cut back to 20, so Dell has 10 extra. I've bought stuff from Dell Outlet, both the business version and the home version, its been fine.you have to check it a couple times a day for a few weeks if you want a specific configuration (say, a E6420 14, with the FHD screen, the backlit keyboard, a good CPU, and extended battery). -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] died again
On 12/6/2013 7:02 PM, Michael Hennebry wrote: If I remove the right screws, I think that moving it farther into the case would allow it to be removed. For that, I'd want it on its side so that it didn't fall on something. nearly all PC power supplies are standard ATX/EPS format. remove side panel, case on side, unplug ALL the power wires, untangle and extract the power harness, remove the 4 screws on the back panel around the PSU vents, and it lifts out from the inside of the case. replace with a decent brand supply of equal or higher wattage rating, and the correct ATX version (v2.1 or whatever). really old systems used much more 5V than modern PSU's offer, and used less 12V. modern PSU's are mostly all about the 12V, the other voltages are lower current. many newer systems need additional 12V plugs for the mainboard, like 2x2 or 2x3 connectors. In some system cases, the PSU is screwed to a shelf or bracket or back plate that comes out with it as a unit, then you disassemble them. -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] how to inject a kmod driver from elrepo into kickstart
On 12/07/2013 05:15 AM, psavoie1783 wrote: On 06/12/13 09:37 PM, Patrick Lists wrote: On 12/07/2013 02:39 AM, psavoie1783 wrote: Hi All, I have a marvel chipset for my wired laptop connection. It uses the kmod-sk98lin-10.93.3.3-1.el6.elrepo.x86_64.rpm driver at elrepo. I would like to use this driver to activate the wired connection to kickstart my laptop as I have pxe booting set upon my home network. Could anyone please enlighten me as to how to get the drivers/firmware from this package loaded on my laqptop so I can use kickstart to load the OS, please? Add a local apache/httpd powered repo to your kickstart: repo --name=sk98 repo --baseurl=http://myrepo/CentOS/6/x86_64/kmod-sk98lin-10.93.3.3-1.el6.elrepo.x86_64.rpm; 'myrepo' is the pxe/kickstart server hostname and the kmod-sk98lin rpm driver has been copied to /var/www/html/CentOS/6/x86_64. Make sure httpd is running # service httpd start Run createrepo: # cd /var/www/html/CentOS/6/x86_64/ # createrepo -v -d . Fire up laptop and kickstart it. Regards, Patrick Thank you Patrick, I am pxe booting off the marvel card and in order to be able to do what you suggest, I think I need the driver to be installed to get the kickstart file first. Otherwise, how would the installer get it? Sorry, misread the question. I guess you need to create a driver disk. Google how to create them or check these links: http://serverfault.com/questions/374870/how-to-build-a-driver-disk-for-an-anaconda-install-centos-6 http://www.ruizs.org/archives/49 And when booting you need something like linux dd=url_to_driver.img Regards, Patrick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] how to inject a kmod driver from elrepo into kickstart
On 07.12.2013 04:15, psavoie1783 wrote: I am pxe booting off the marvel card and in order to be able to do what you suggest, I think I need the driver to be installed to get the kickstart file first. Otherwise, how would the installer get it? Phil When you PXE boot you get a kernel (vmlinuz) and a ramdisk (initrd.img), you can use a custom ramdisk that you generate on the local machine and include the needed driver, then transfer it on to the PXE server. Make sure the vmlinuz and initrd.img have the exact same version. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] died again
On Sat, 2013-12-07 at 00:58 -0500, Darr247 wrote: On 07 December 2013 @02:57 zulu, Michael Hennebry wrote: The CPU heat sink is under the fan pointing down towards the motherboard. You lift those 2 levers to release it, and there's likely another lever under it all locking the CPU into the socket. The picture is not very clear, but it looks as if the heatsink on the processor has collected a lot of dust, probably blocking the air flow. Do not yet remove the heat sink ( I am always weary of doing so) but try to remove the dust first if there is a lot of it. Louis ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] died again
On 12/7/2013 3:01 AM, Louis Lagendijk wrote: On Sat, 2013-12-07 at 00:58 -0500, Darr247 wrote: On 07 December 2013 @02:57 zulu, Michael Hennebry wrote: The CPU heat sink is under the fan pointing down towards the motherboard. You lift those 2 levers to release it, and there's likely another lever under it all locking the CPU into the socket. The picture is not very clear, but it looks as if the heatsink on the processor has collected a lot of dust, probably blocking the air flow. Do not yet remove the heat sink ( I am always weary of doing so) but try to remove the dust first if there is a lot of it. geez, its a 10 year old pentium-4, and not even a late p4, a middle aged 32bit-only one put it out of its misery, its been living on borrowed time for the last 5 years. -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] died again
On 12/06/2013 06:57 PM, Michael Hennebry wrote: I suspect the pincushiony thing between the video card and the big black Intel fan of being the heat sink for the CPU, but I do not know. That case looks very dusty and 60C for an Intel CPU tells us that it is most likely overheating. The big black Intel fan is the fan for the CPU heatsink - which is what it is physically mounted on. *Don't try to remove it.* Since you didn't recognize a CPU fan on sight you clearly have no background in disassembling and reassembling PCs and you will most likely damage the CPU before you are done. Failure to reattach the CPU cooling fan correctly (which involves cleaning off the old heatsink compound and applying new heatsink compound correctly) **will** cause CPU overheating and system problems and can damage the CPU. I would start by gettting a can of compressed air, gently place a finger on the black Intel fan blades so it doesn't spin (spinning up a fan with air turns it into a generator pushing damaging voltage back into the motherboard - you don't want to do that) and blow the all the dust out of the heat sink for the CPU while moving the fan blades with your finger to allow access to the entire heatsink. Then boot the machine and verify that the CPU fan is in fact spinning. Also blow the dust out of the power supply (the silver box at the top left) and off the fins of the video card. -- Benjamin Franz ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] md5sum mismatch between CentOS 6.4 and 6.5 repository
On 12/06/2013 12:49 PM, Lars Hecking wrote: Something got mixed up somewhere. The first one (md5 20bb...) is from the x86_64 branch, both 6.4 and 6.5, and the second one (md5 d37f...) is from the i386 branch, also 6.4 and 6.5. d37fe4404a7a5fdb27b29f9b5ed09c73 ./6.4/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm 20bb02e6f3b7b71e09dcaff7f3b0ca02 ./6.4/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm d37fe4404a7a5fdb27b29f9b5ed09c73 ./6.5/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm 20bb02e6f3b7b71e09dcaff7f3b0ca02 ./6.5/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm Hm, am I the only mirror maintainer that runs hardlinkpy on the tree after each mirror? Why are there different md5sum's on these files? They are noarch rpms, so they should be identical in i386 and x86_64? I get the following: # md5sum `locate python-slip-dbus-0.2.20-1.el6_2.noarch.rpm` d37fe4404a7a5fdb27b29f9b5ed09c73 /var/ftp/pub/mirrors/centos/6.4/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm 20bb02e6f3b7b71e09dcaff7f3b0ca02 /var/ftp/pub/mirrors/centos/6.4/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm d37fe4404a7a5fdb27b29f9b5ed09c73 /var/ftp/pub/mirrors/centos/6.5/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm d37fe4404a7a5fdb27b29f9b5ed09c73 /var/ftp/pub/mirrors/centos/6.5/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm and: # ls -li `locate python-slip-dbus-0.2.20-1.el6_2.noarch.rpm` 98845547 -rw-rw-r-- 3 mk 500 30844 Mar 26 2012 /var/ftp/pub/mirrors/centos/6.4/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm 98315857 -rw-rw-r-- 1 mk 500 30844 Mar 26 2012 /var/ftp/pub/mirrors/centos/6.4/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm 98845547 -rw-rw-r-- 3 mk 500 30844 Mar 26 2012 /var/ftp/pub/mirrors/centos/6.5/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm 98845547 -rw-rw-r-- 3 mk 500 30844 Mar 26 2012 /var/ftp/pub/mirrors/centos/6.5/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm Mogens -- Mogens Kjaer, m...@lemo.dk http://www.lemo.dk ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] how to inject a kmod driver from elrepo into kickstart
On 07/12/13 05:23 AM, Nux! wrote: On 07.12.2013 04:15, psavoie1783 wrote: I am pxe booting off the marvel card and in order to be able to do what you suggest, I think I need the driver to be installed to get the kickstart file first. Otherwise, how would the installer get it? Phil When you PXE boot you get a kernel (vmlinuz) and a ramdisk (initrd.img), you can use a custom ramdisk that you generate on the local machine and include the needed driver, then transfer it on to the PXE server. Make sure the vmlinuz and initrd.img have the exact same version. That would work... but what if I install the kmod driver right after I install the notebook and took the new initramfs file and threw it on the pxe server would this work? Phil -- To err, is human To never grow up, is divine ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] DMAR Problem since 6.5
Hello List, I updated my server to CentOS 6.5. When i boot the system with the new kernel: 2.6.32-431.el6.x86_64 I get repeating the following message: dmar: DRHD: handling fault status reg 3 dmar: DMAR:[DMA Read] Request device [00:02.0] fault addr 1fc0 DMAR:[fault reason 06] PTE Read access is not set I use a Intel Core i5-3550 CPU with vt-d enabled to use a DVB-S Card inside a Windows VM (kvm). With the old 6.4 Kernel all works (2.6.32-358.23.2.el6.x86_64) lscpi shows this: [...] 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) [...] Is this a problem with the intel driver or anything else? Regards, Sebastian Marten ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Build environment for totem-2.16.7-7.el5_6.1.src.rpm
This package has a build requirement 'gecko-devel' which is fulfilled by 'xulrunner-devel'. But in the process of building the browser plugins two tools named 'xpidl' and 'xpt_link' are necessary. They werde once part of 'gecko-devel' but are now replaced by other tools. I haven't found any package that has these tools all the way back to 5.0. Maybe the makers of CentOS can give a hint. After all this package was build for C5. Thanks Michael ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] how to inject a kmod driver from elrepo into kickstart
On 07.12.2013 15:09, psavoie1783 wrote: That would work... but what if I install the kmod driver right after I install the notebook and took the new initramfs file and threw it on the pxe server would this work? Phil Should work, try it and let us know. :) -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
