Re: Connie Sieh, founder of Scientific Linux, retires from Fermilab
Best wishes to Connie! She and the support provided by Fermilab truly changed scientific computing throughout the world. We are all very grateful! On 02/24/2017 03:52 PM, Bonnie King wrote: > Friends, > > The Scientific Linux team is at once happy and sad to announce Connie > Sieh's retirement after 23 years. Today is her last full-time day at > Fermilab. > > Connie Sieh founded the Fermi Linux and Scientific Linux projects and > has worked on them continuously. She has sometimes preferred to toil > behind the scenes and leave public announcements to others, but has > always been a driving force behind the projects. > > The Scientific Linux story started in the late 1990s when Connie's group > explored using commodity PC hardware and Linux as an alternative to > commercial servers with proprietary UNIX operating systems. From the > distributions available at the time, Red Hat Linux was chosen. > > In 1998, Connie announced Fermi Linux at HEPiX, a semi-annual meeting of > High Energy Physics IT staff. Fermi Linux was a customized and > re-branded version of Red Hat Linux with some tweaks for integration > with the Fermilab environment. It also introduced an installer > modification called Workgroups, a framework to customize package sets > for use at different sites and for different purposes. The Workgroups > concept lives on today in the form of Contexts for SL7. > > In October 2003 TUV changed their product model and introduced Red Hat > Enterprise Linux. Enterprise Linux was no longer freely distributed in > binary form, but sources remained available. > > Connie and her colleagues started building from these sources, creating > one of the first Enterprise Linux rebuilds. A preview, dubbed HEPL, was > presented at spring HEPiX 2004. In May 2004, the rebuild was released as > Scientific Linux. The name was chosen to reflect the goals and user base > of the product. > > Our colleagues at CERN collaborated, customizing and using Scientific > Linux as Scientific Linux CERN (SLC). SL became a standard OS for > Scientific Computing in High Energy Physics at Fermilab, CERN and beyond. > > SL is freely available to the general public, and is a popular > Enterprise Linux rebuild. As a result, it has built a community outside > of Fermilab and HEP. > > With gratitude, the Scientific Linux team would like to recognize > Connie's many years of service and her immense contribution to the > project she founded. > > Connie's outstanding technical and non-technical judgement are the > foundation of Scientific Linux. Her legacy will continue to inform the > way we run SL and we hope she'll remain as a collaborator. > > All the best to Connie in her well-earned retirement. She will be dearly > missed! > <> signature.asc Description: OpenPGP digital signature
Re: encryption of root filesystem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 encrypting the root file system sounds difficult but likely using ecryptfs-create/mount-private can be used and would cover a users intimates. On 03/10/2014 06:29 AM, Urs Beyerle wrote: > Hi, > > I have to admit that I don't know, if this is possible. You can have an > encrypted /home stored on a flash drive using livecd-iso-to-disk. > I only remember one email asking for an encrypted / on > liv...@lists.fedoraproject.org > https://lists.fedoraproject.org/pipermail/livecd/2011-October/006936.html > > Maybe you want to ask once again on > https://lists.fedoraproject.org/mailman/listinfo/livecd and report it > back to this list. > > Cheers, > > Urs > > > On 03/07/2014 06:33 PM, Boryeu Mao wrote: >> In building a bootable DVD image (in the manner of >> SL-65-x86_64-2014-02-06-LiveDVD.iso), is it possible to encrypt the >> system? If so, should the file LiveOS/squashfs.img be encrypted, or >> the file ext3fs.img contained therein? and what other changes (for >> example in the boot configuration) would be needed? Hopefully this >> is a question not outside of the design goals. Thanks in advance for >> any help/pointers. >> -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJTHcnGAAoJEPQM1KNWz8QaQaYH/RPnEuQhzCFd+8erjoZmnA7z eNaN6a9tuPy6ig+hBi7HKOwgLbd5JiyDhbWta5YI9GEt5xe5HFqftWvrM1sIQGUh TDYMIRup6/MF1pJTzxFBmA97DIMWWvU6X5nz2gPMO7WQcg13Sa1jYUvbgNkQp0oD ZuZKSvSSAblrm8mSKYR3Jqxi6EJJlWR0ZvMAVEClUM9gCbxJKNT+7B2OvoQnCwWU YMpcapy5acxRmA0B/RhR4xcbfSbuZyZ1oBlu8Srahg4S9V+KAU7X+15VqV8DZGTn uqoKt9erjpZghcfo1UBupP+unhugcTtZ1wqkuVJwHX759APDiPV8M66FGSr0WVY= =fNmp -END PGP SIGNATURE- <>
Re: USB mouse and wired eth0 internet would not load on hard drive installation or on booting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Check the bios and see if IOMMU is disabled. I had a similar problem with a recent Gigabyte MB and found that the factory setting disables it. USB depends on this being enabled for linux. On 01/29/2014 12:46 PM, Akemi Yagi wrote: > On Wed, Jan 29, 2014 at 6:11 AM, sserve2013 wrote: >> Hello, >> I have a new gigabyte motherboard 970A-UD3P (rev 1.0) installed. >> Bios F1 07/06/2013. Serial Number SN133640037609. >> VGA ATI Radeon Sapphire HD 5450. >> CPU AMD FX 6300 3.50 Ghertz. >> Memory 8G kingston DDR3 1600 Ghertz. Power supply 600 watts. >> I am having problems loading Linux software. >> >> No USB mouse is laoding.Error "usb 9-1" is seen. >> >> No network internet eth0 is loading= no wired connection error given. >> >> All settings is set to legacy since this Linux worked before on my old UFI >> motherbaord with all the same standard settings. >> This is a Uefi/efi/legacy board. >> Some Linus OS not loading are:- >> >> --- Scientific Linux SL-64-x86_os_18 is not loading. >> >> Any advice? >> I am sure many thousands of Linux customers and users are having the same >> issues with this and equivalent motherboards from other manufacturers. > > Scientific Linux 6.5 will be officially released tomorrow. You may > want to give it a try. Also more detailed info about the NIC device > (device IDs) will help us help you. > > Akemi > -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJS6VkJAAoJEPQM1KNWz8QaTBsH/An97923/pYlRpyzUS/qK96X TZ2ypIEgU2IdaoZ6p1SYv89+JDuPuoHgrkrUvyOajWLVb9JVhUFyK2L6PbeACsn0 MMMYupyHNfsrsfaqySxoKoRRu28OXLz57j73Jt0Xa1l6EaR6hTJe54IjGbC1VvlQ 8hf/csriMbbIS+LKlBodWAgbasAI49KhtfcnEUOhCB5FXOwI+RhZGF/VULa1phu9 fWT9b7zLUgFnHRWnYGYk0ZcB4aC7opWsTLWS98AnLtChDWWFhn5C2UJZ39BFygLQ A+zEDE/Qr0BROol2rO2wAG2BvDhYhusvVBD4FpMGzdu+mQOSkwIHS+TAWP/SrkM= =y3Gw -END PGP SIGNATURE- <>
Re: Drop Box on SL 5.10
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've used the python script documented at http://www.dropboxwiki.com/tips-and-tricks/using-the-official-dropbox-command-line-interface-cli for years - it worked fine under sl5 and under ubuntu 12.10. On 12/15/2013 01:52 PM, Larry Linder wrote: > Help: > > A number of project guys would like to have a drop box folder to share > project > info with others working on same project. > Tried to install drop box on SL 5.10 with numerous packages out of date or > libs not found. > I there a clean install for this. > > We are slowly working our way into a corner as we have added a lot of libs to > support unique apps. Even though they are all backed up I view this as a > real future problem. > > Thank You > Marry Christmas > > Larry Linder > -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJSr0NfAAoJEPQM1KNWz8QanMMH/101+DsOYCmyu7/QeGuj7s3c fTgBzKgJ89oOS/4SHHWCao4QaciSnXoG+KG/ci6PJpovmBdUNjBEjjpU5fd3Yqks iwaDL2SARoYXmQ3YS04+Kc9cehAoLunEAvLTXQpvOWatYoak3iP89WizogA62KGp XrXMIuo+4pQ/YkJ6cjsTBGdaHsgTGZA3/0s2E6mBZ3nT1S3Xg3ap66g6rvrVfENg m+Db+gn+n4LIQRYSgxIPBkIRj9rPUQLp0o/6kPwh+ArUMxrfXmqQa+gGSlO2Xpp6 OIHYFLgX4jtk9AqKFxcep13umDuEWSDHoBOtA3PTL8lLet2bSKTQwXMtFFuKb6I= =Y5M6 -END PGP SIGNATURE- <>
furlough?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Will sl6 updates be available if FNAL shuts down due to the absence of a CR? Is there a plan for continuing support in the event FNAL furloughs its workforce? Just wondering since we are now discussing the options here at Argonne. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJSWEShAAoJEPQM1KNWz8QaJdsIAJRd4NDjdF8DI52m2uiLfFSe ktRFKJ+Pz1Da/BBi01aWCvmDq32FXko/khpDjm5ttrC1TYGj+cSOmXnPUZ3EomeB GczqgU+Oz7Sj3OZ8kfm4g6QnBcVWFoTlC/eaSKi11MzuxW+rkZkSRfvGzhKVsxfw rabZqWXvQI3aac+NGIVMCQSWq26OxyLxH6FY65RddRjVbj5uNkqSsopUKA0VWQrc ugNA8wbKTdoRAv4VT0L85jzdD8QuzQpdxty/FN+Ce/bXS6007Wo/oH9E8OS60EFd FYcBWAm9Y/A7kheJn7xki2Q/55PmEFYylqpTjQjlVCmiMSWiXGPBHCTS0QB3qE0= =/bqB -END PGP SIGNATURE- <>
Re: New Install of 6.4 - no Internet
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 If this is like the board I got a while ago - one issue is the BIOS defaults (the USB problems). The board I had had IOMMU disabled by default and this needs to be enabled for USB to work under linux. On 08/08/2013 10:45 AM, Akemi Yagi wrote: > On Thu, Aug 8, 2013 at 8:11 AM, Larry Linder > wrote: > >> After searching the net there are a number of people who have the same >> problem. Gigabyte GA-970-DS3 mother boards have several problems out of the >> box. With Ubuntu 64 bit systems they do not work or support the RealTech >> RTL8168/811E chip set. Other reported failures appear to be USB3. >> >> I looks like we have a windows only board at the moment. >> >> A fix is to download the latest driver for the chip set, compile it and >> install it, & test it. According to article Ubuntu's newest has updated >> driver. >> Our MB is also a version 1.0 and now they are up to 3.0. The good deal for >> a >> few $ may be an expensive one in labor. >> >> When we are done, will post a how to fix this for SL. >> >> This system is really quick with a Quad core and 4.1 GHz clock. It looked >> initially like a super computer at a steal and is well worth the time spent >> if fix works. >> >> Larry Linder > > Have you looked at ELRepo? Particularly, FAQ#4 at > http://elrepo.org/tiki/FAQ may help you find the right driver for the > NIC. > > Akemi > -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJSA8SlAAoJEPQM1KNWz8QauCUIAM6++rC8eFlV0azP97QRfJK2 3b26txQDNmhIzlYSurpaBbAHW4J9q8X9JBAiGXBCvv8UiTQSinIQVFAXpLxmbJ2c 4Mb16GU1wcTLK2uQkQg5wHqankvnff5lL6VTOFrSGaPmu53bdN2Dg3eIcTv9XHUX ggzI4430AHvJ6K1fpEbmxmXQlbHSyyGFWiASGaPtBgtGg+v0+2NcDW2jZ98wgDgz 4N2mfyZuJ9bod9aLuzNNH+iiMU9kP72t/14wAQfQNxM/3LKknA43m0fpgkut/aCj cYrINrLL4CEW9bfQEATS098uAAKLDkrraCWBNeOLOZ0c3W2+VrJSKO9f/QfiPJI= =Mmsf -END PGP SIGNATURE- <>
Re: peculiar statd/mountd problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just a little more detail on the problem described. We have designated a fixed port for statd, but it appears to listen on the designated port and grab the corresponding UDP port but it also grabbed the UDP mountd port before mountd was started which resulted in mountd failing to launch. On 06/26/2013 01:38 PM, Steven C Timm wrote: > According to the man pages for rpc.statd it is possible to specify a fixed > port for that daemon at startup. I've never tried. > > Steve Timm > > > -Original Message- > From: owner-scientific-linux-us...@listserv.fnal.gov > [mailto:owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of Steven C > Timm > Sent: Wednesday, June 26, 2013 1:34 PM > To: Eve V. E. Kovacs; scientific-linux-users > Cc: Patrick Riehecky > Subject: RE: peculiar statd/mountd problem > > I have a SLF5 system which is only an NFS client but I see the same issue > that rpc.statd is running on a different port for UDP than it is for TCP. We > have seen some strange issues with the automount on this system failing a > couple of times to mount the remote client system. Wonder if this is related > to what you are seeing. It could be. > > Steve Timm > > > -Original Message- > From: owner-scientific-linux-us...@listserv.fnal.gov > [mailto:owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of Eve V. > E. Kovacs > Sent: Wednesday, June 26, 2013 1:24 PM > To: scientific-linux-users > Cc: Patrick Riehecky > Subject: peculiar statd/mountd problem > > We have an SL5.5 nfs server that has developed an odd problem. > We have configured /etc/sysconfig/nfs to assign port numbers for the various > services, 662 for statd and 892 for mountd, in particular. > For reasons unknown, rpc.statd, in addition to running on port 662 as > directed, has grabbed port 892 for running udp. > > We see, on the server: > rpc.statd 2412 rpcuser3u IPv4 7443 UDP *:662 > rpc.statd 2412 rpcuser6u IPv4 7434 UDP *:892 > rpc.statd 2412 rpcuser7u IPv4 7446 TCP *:662 (LISTEN) > > Since 892 was the port that was assigned to mountd, it caused mountd to fail, > and hence nfs mounts from the clients to fail. > > We have switched mountd to run on port 895 for the time being, so we are > functional, but we would like to understand what happened. > We are running an identical backup server, and interestingly, there, the > extra port being grabbed by statd is 982 not 892! > > Has anyone else seen this behavior, or have any idea why the two servers are > behaving differently? > Presumably this extra port for statd is being assigned by portmap. > Is there any way to fix this port assigment so that we don't get a collision > like this in the future? > > Thanks > Eve > > ps. we tried booting to the previous kernel but that did not fix the problem > *** > Eve Kovacs > Argonne National Laboratory, > Room L-177, Bldg. 360, HEP > 9700 S. Cass Ave. > Argonne, IL 60439 USA > Phone: (630)-252-6208 > Fax: (630)-252-5047 > email: kov...@anl.gov > *** > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBAgAGBQJRyzxZAAoJEPQM1KNWz8QaoJUIAMQfc3ZPBUA2nXoh6o8vnBP6 VsFvVOKISw1zrGbx5OYSSOINubEOMaJrKu7ZTX3CWLIEW6TmxV/tWe7TR0q2KaSZ JgGuZLnMfLfH8lV8cRgKqHBj82N65D7S9BXnL8znIWoSjjlcBLz/fbEQZWmUlB3s cFbY3B6QFry2UIvYxuNEZMBe1Qzr56OyypVIYF4TEbzeVHJMZgenFAEJNqkw+9rG EGmsykhrQlWM3zxMSuWsjDq3ZM61bT/JyLwFumyFv+6DR0+nviw6rmDUDXJCErrf Kh0NLaTJT9hFhD1QAe9AiZMJB1ibLfU/p6Q+ei1mrp4f/+Zp8Bt+6B+BVlue+5M= =d8LR -END PGP SIGNATURE- <>
Re: Flash and Chrome - was Re: FireFox Error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 An odd feature of the list of supported linuxen for chrome is that it indicates fedora 14 (not fedora 14+). The current release of fedora is 18 and I didn't notice a warning on my fedora installs. I wonder if this is just a typo? On 04/02/2013 04:09 AM, Dr Andrew C Aitchison wrote: > On Mon, 1 Apr 2013, Robert Blair wrote: > >> Slightly off topic but related: now that 1) adobe is no longer >> supporting flash for linux firefox plugins and 2) google is no longer >> supporting google-chrome on SL, do we have a flash crisis? Is there a >> plan to deal with this by TUV? > > 1) According to > http://www.adobe.com/devnet/flashplatform/whitepapers/roadmap.html > Adobe will support non-pepper flash 11.2 for five years from release, > so we have another four years and it isn't a crisis yet. > > 2) For those who haven't heard this, some links: > http://support.google.com/chrome/bin/answer.py?hl=en-GB&answer=95411 > http://www.muktware.com/5203/google-says-red-hat-enterprise-linux-6-obsolete > > > Seems that the issue is Google want to use C++11 / gcc4.6 which > is not standard on RHEL6/SL6. > > (I'm out of the loop but "developers ... prefer the new C++11 for the > obvious security reasons" comes as a suprise to me.) > -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJRWvy+AAoJEPQM1KNWz8QaY/YH/3JCWFmJVrlURvb3tvfJz1/y bH0hhRBAM5/VwjgKRI2UFnzhjFcTh4e0ISZ0zVVvZnsmCEXp2yV11WnpprhVqWqH BOyA6OjZnVwiB36BtKKoIM8wnOLeFOKvp0IjKaCpN8E5X6SoLGqJhFVcRH6PlwUe A0S8m8II4oMwRb9P09MEVECpHgS5HGU9Qajcz4o2SXg2/ICDdce4yyQcnQaoktmM ahyxBL+KqtlJEXHVI3aVVVtiIs+W6zqe2WRT1z2iyn/wrdjA6e+e8FUITtIS+8Al PO1LlxbpRSX32BcR2clRkthn7JBuxutfX9TCWpEETj5qmQGTA93oPLTpidFnBLQ= =+3SU -END PGP SIGNATURE- <>
Re: FireFox Error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I suspect your best approach is to install a personal copy from Mozilla.org in your home area. It updates automatically and, aside from resource issues - as in how many people need to do this, should function just fine. I used to do this to get a more recent version for my own use. An install of google-chrome made this unnecessary but... Slightly off topic but related: now that 1) adobe is no longer supporting flash for linux firefox plugins and 2) google is no longer supporting google-chrome on SL, do we have a flash crisis? Is there a plan to deal with this by TUV? On 03/31/2013 03:25 PM, Larry Linder wrote: > Excuse me but I have been ignoring the FireFox discussion, but now our > purchasing group needs to use it. > > SL Linux 5.8. > > When I try to launch a FireFox app. > The error message is: > Error: Platform version '10.0.3' is not compatible with > minVersion >= 10.0.12 > maxVersion <= 10.0.12 > > Any Suggestions? > > Thank You > Larry Linder > -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJRWa7sAAoJEPQM1KNWz8QaxRMH/1lmdpHDzerhMu6ESXhlk/yV WqMn0Iwfs3jh9h8RnHXLdwzx9otPXiM/bZu6+oL0bdtGI01tfvocEPYx/sSPD8J+ glFlrpspFJKgQqdn/N/kNm83GeKwVY09LkjmSb6zbVPKtcaMTqX0J2FMOlQp6zSx derlruDc/ORJbUFZeq2pXrR3eV2eUyN4wYyJcYz6Q0N1AYhOzDqvspQLHtzVs3tm NXel+CZpA0XJ+9TzDKtZQn+Rgt7VA/3vx6zVXcA0bRz8Nu9ptvGOo1cK1beHxdVq fie4KlDw7ndxfLf0It+trP7Pq2wsu6ou7k/vZ6gbZ6/KASdRXL5YpQILIMoipMI= =uVV5 -END PGP SIGNATURE- <>
Re: Any recommendations for a compatible USB WiFi?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Very odd. My laptop has this card and works just fine under sl6.3 x86_64. I'm using it as I type now. Could this be a firmware issue? I seem to recall loading firmware a long time ago for this card (the timestamp on the file is Apr 23 2009 and the details below), but I did a clean install on this system a few months ago. iwl3945 :0c:00.0: Detected Intel Wireless WiFi Link 3945ABG iwl3945 :0c:00.0: firmware: requesting iwlwifi-3945-2.ucode iwl3945 :0c:00.0: loaded firmware version 15.32.2.9 On 03/26/2013 02:14 PM, Andras Horvath wrote: > I cannot recommend what would be the best, but instead I'd like to > point out which one's not a good buy. > > From one point of update since SL 6.2 I was continuously having > problems with my Intel 3945 ABG wifi card. Serious kernel panics and > hangings happened after a couple of minutes uptime. I read about > similar problems on the net from CentOS systems too around the same > time of my update. > > This card was working just fine before on SL, and even after on > different Linux systems - later I even bought another card > with the same chipset - but SL still produced the errors. So I replaced > my card with one from Atheros and problems are gone. > > Andras > > > On Tue, 26 Mar 2013 11:22:14 -0700 > Joseph Areeda wrote: > >> I tried to use the Broadcom WiFi that came with the motherboard >> (don't have the model number right now). >> >> It seemed to not be recognized although Windows sees it fine in >> another system. >> >> Would someone recommend a good USB Wifi that has current drivers for >> SL6.3? Or point me to a list of drivers available in the release >> repositories? >> >> It's a long story but we need both wired and wireless on this system >> and easier to buy a compatible interface rather than do much work to >> find non-standard drivers. >> >> Thank you, >> >> Joe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJRUfdEAAoJEPQM1KNWz8Qabj4H/3ozxohpfqoDpHfaE+Zpofho Wseg0bH0CGbKDTuuTCzkAPDHqfBES3gQ2x8saF+AqVLA6nZgN1O1gxXbzgnPBRxq 5ZB9L+NLiah5avykDGu0gE0CJ1zQCEAFA1oqyM+Mdo+I/R4UoSb/x5W0+r9JFhyh vpoG3F6Lea3Zis7o+T1xCIgRjKUiONBd0xqAJWDiYKdncZNAi/SzatRHu489p7pD 2r6AoM2X8Fhp97eDCbiTKO0BpYTcoBjBu3KoTDVM+TLprQxZYCJAvktoE1PoS2KO jI5nkjafinIPSB9fqqmNPQb9v1sjNyHSi7X0QuKvJL0nx9cH7zrnE2AlCiYnaBM= =J+6V -END PGP SIGNATURE- <>
Re: Issues with the recent kernel and proprietary nvidia drivers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks. I suspect, however, that the issues identified by this don't apply since the two cards were a GT240 and a GT220 which are not part of the legacy group that this is meant to help with. I'm sort of committed to moving to nouveau since it weans me from these awkward special support modes and nouveau appears to have reached a reasonable level of maturity. I've been using nouveau on a laptop with an add on monitor for some time now and find it a bit better than the nvidia twinview stuff. This is not to mention that disentangling the proprietary drivers is a bit painful. Returning to the nvidia proprietary approach would have to have certain success to be worth going back. At the moment I have stable operation with two screens and can live this way. On 03/25/2013 09:53 AM, Andras Horvath wrote: > Bob, > > Elrepo announced not long ago the availability of the nvidia-detect > package from their repository. I suggest you to take a look at that. > > The relevant mail: > http://lists.elrepo.org/pipermail/elrepo/2013-February/001652.html > > Andras > > > On Mon, 25 Mar 2013 09:36:12 -0500 > Robert Blair wrote: > > I have an SL6 system which uses the epel nvidia kmod modules. Just > recently X began crashing whenever a flash or other video is played. I > presume this is related to the most recent kernel update. The system > was a bit unusual in that it had two video cards and four monitors. > Is this unique to my setup or have others observed this? > > As a follow up I converted to the nouveau driver which doesn't have > this problem but I have yet to get the system to drive more than two > monitors off one card. Anyone know of a good resource for > multicard/monitor nouveau setup/troubleshooting? > > Cheers, > Bob Blair -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJRUGcNAAoJEPQM1KNWz8QasGIH/1hCCV+3l42p+27iDCSLdnzo 5Pizp+tG7PXjkhgfuMZ0l/awISb2N88hj9NQzGC91mtip/HJt48P3SjARfv4VOAB U32gsj0I2qWNi1AT7bxYExQ7572nIv8luXKI3Dk75dr7luBcL70iKEY7dLXy1grr l2bvvOkh/36TmILl1H8AbCcmXZBIi9iZgPh3eCgmcd9ApqPdcomViqbiX20C+iLQ Siv0KXsLHZOfv4LMPdsi2o3/I+xs2t9iA0orQV4ZIFADmHYyHlhockd+4zCB6Bcc lsFqGllrowayzVgSXu/OVhIvApE9ZGCz2rKTaZGSPwiFfy3Ita199wRZCjxQdBk= =5vuF -END PGP SIGNATURE- <>
Issues with the recent kernel and proprietary nvidia drivers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have an SL6 system which uses the epel nvidia kmod modules. Just recently X began crashing whenever a flash or other video is played. I presume this is related to the most recent kernel update. The system was a bit unusual in that it had two video cards and four monitors. Is this unique to my setup or have others observed this? As a follow up I converted to the nouveau driver which doesn't have this problem but I have yet to get the system to drive more than two monitors off one card. Anyone know of a good resource for multicard/monitor nouveau setup/troubleshooting? Cheers, Bob Blair -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJRUGDcAAoJEPQM1KNWz8QaBHwH/jl1VstctkmVzgaAt2jM0c1q K26yUbuQv2v3Kn3EcAIcV9qU3B3aNXDlTE7Dpbmbc4OK+6PPL2LoxhNxHsZ8qHg5 rebzjbfgqWrpjl59CMAHLMKIjcxEMPGAKOdzhGxh+6uX9Gy4Kfp41oU5tlDyaUwr 0P8nmC2gdpKEveRVGD+Yx5ZKKro36cv3hGeNCltbKm3BsXrRnMuJTnjVgvcGnKXI 6yPqKzMtd4mGdLzdgfk4g5QGaI7i9LpFIadT1VRz2WuygmbisLB6yfu+CuVEWF7Z iEXptLcVmjzBuMIqvq6dmkTTTzKZYxmeLUxExoyAurOjsK8tuThXiPwnYh9AsiM= =kHps -END PGP SIGNATURE- <>
Re: [SCIENTIFIC-LINUX-USERS] Installing on a new laptop
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Maybe I've missed something here. If a generic "MS signed shim" is available what value does this add? Wouldn't such a shim make booting anything alternative possible? On 02/28/2013 01:35 PM, Tom H wrote: > On Wed, Feb 27, 2013 at 6:48 PM, zxq9 wrote: >> On 02/28/2013 12:53 AM, Dale Dellutri wrote: >>> On Wed, Feb 27, 2013 at 6:27 AM, zxq9 wrote: There is a silver lining. The board makers themselves are out to sell boards and laptops and tablets and can be reasoned with. My company is an extremely small player in the hardware field but we've had positive response from vendors when inquiring about having our own keys included on boards alongside Microsoft's when doing bulk orders. We haven't had to go that route yet so I'm unsure how much of a pain that would actually be to manage (doesn't appear much more difficult than managing repository keys though, for example), but this leaves the door open for even tiny computing companies and larger IT departments to arrange for their own "secure" boot keys to be pre-installed by the board manufacturers and not violate Microsoft's requirements, even on ARM. That said, since we don't do showroom marketing anyway neither we nor our suppliers have a need to put little "Windows8 Ready" stickers on anything they ship to us anyway. >>> >>> Doesn't this lower the eventual resale value of the laptop? >>> Doesn't it restrict the laptop to run only what either MS wants >>> or what you installed? >>> >>> I buy refurbished laptops and install Fedora, but I might want >>> to try *BSD or Ubuntu or something else in the future. Doesn't >>> the "silver lining" restrict that with these UEFI laptops? >> >> It does indeed lower the overall value to the buyer -- which is >> why we're not satisfied with the concept of "secure boot", even >> if a board maker puts our keys on the device: we want to sell >> hardware, and providing a device the user can do whatever he >> wants to independent of us is a more competitive selling position >> than selling, essentially, a "locked" device. >> >> This is not a good move for the industry for this exact reason. >> Of course, laptop makers think this means they will be able to >> sell one device per instance/OS a user wants -- but especially in >> the consumer space this is wishful thinking. >> >> If standard UEFI situation ever moves from "user disable-able" to >> "always on by default" then every device sold will essentially be >> a locked device that requires jailbreaking to work properly. >> Offering unlocked devices is far more competitive -- but the >> dialogue of the industry has made a mystical security claim that >> lay users don't understand and magically transformed >> vendor-jailing of devices from a usability impediment into a >> must-have feature. > > I wouldn't be surprised if SB became "un-disable-able" in the next > few years. We'd then have to use an MS-signed shim to boot, as is > now the case with the default Fedora and Ubuntu SB setups. > -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJRL7IrAAoJEPQM1KNWz8QadQ8H/jQCPdNYn48NF7d4gMApltt2 q23jgD12vksdM0hzhxbMaJhHJGBTNtatgambocYLNr4IcgjrAFlVvwXHLErpNA6c qx2vMSG4SDKUCetI6lJ30oC8Z0O0oaWzcXlPd1LTrL8eLOqIgh0h2+QFhI5TaaW5 RFNRCS+rSG+QwindFwuA0yIDGTiwJNOW0Orod+/+tuLl2u8WrJZi1leYnsb0qVRh esoshMH8cHHxlgLQztM4TvEC5AqhgroxdUYsIi/7JCAX5qFyc5icPvI+cX28mv5J htJwwDuNI/atCYOL+Htf+1nBgDM/wf6MV0ft2D/xB6ZkCvmGN7/zyTDkDgelXLo= =Fl7J -END PGP SIGNATURE- <>
Re: Installing on a new laptop
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Will FNAL or CERN get some certification to allow them to take advantage of the secure boot option? One of the weakest points of many systems is the ability to boot unauthorized media. This option could work for us but I gather it needs work to get certified (and maybe it's too late given there are products being sold now with it?). Does the TUV effort generalize to derived ones like SL? On 02/26/2013 11:46 AM, Connie Sieh wrote: > On Tue, 26 Feb 2013, Scott_Gates wrote: > >> OK, If I needed a desktop, I'd just roll my own. Probably starting >> with=20= >> >> something bare-bones from TigerDirect. >> >> I'm thinking of buying a new laptop, rather than just recycling old >> ones,= >> =20 >> like I have been.=20 >> >> I have HEARD there are issues with trying to install on computers >> with=20= >> >> Windows8 already installed--the only source I have of "CHEAP" >> laptops.=20= >> =20 > > If a i386/x86_64 laptop is certified for the "Windows 8 logo" then it > has to have "secure boot" enabled in the bios(uefi) by default as > required by Microsoft. Secure boot requires a 'signed by microsoft' > program to boot. But the bios(uefi) is REQUIRED to have a method to turn > off the "secure boot" option and thus not require a microsoft signed os. > > Note that ARM based laptop with "Windows 8 logo" are required to enable > "secure boot" but are required to not allow that it be changed. Again > as required by microsoft. > >> Basically a Wal-mart or Best-buy boxes that I can get in the $250-$400 >> ra= >> nge. >> >> Does anybody have experience with this? Yeah, I know I'll be Voiding >> the= >> =20 >> Warranty--but, I need a laptop for real work--not socializing or net=20 >> flicking. You know what I mean. >> > > -Connie Sieh -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJRLQ22AAoJEPQM1KNWz8QajY0H/As82xpbkKIkJsIoWYKWRi6S 7BnsE80KCkfqzyt1udm6BJh4+PDS8/9uhA6KnCyRG3PH4GzGIe90/Wll22d9caK7 B4wS7wYh0SPjrFJSmuAWx9tlh7x8hDTk/IbssW4Wz/M8jm5r0M8cBWK9tgR71p52 2bAaLFUU1P8sYe/pwDDH/jjG+Y9a+981M3OlDBVJTNgiFNjcEi0yC53K2Teat717 pqcbwFuu0ZPmiMekWnbv7IO+MkQs51iGTwPCAFqOG+jnyjPIdGn1Fe2NLlhohm9H 0D8kP/cvSRqaZG9UeS+Q1MR4x//zgYBWo+HI+t1dqKlexXW02qsYONDd+s3+qb0= =MsdT -END PGP SIGNATURE- <>
