t happened, but something changed and
this current version lookes identical to SL 7.5.
Many thanks,
Stefano
Messaggio originale
Oggetto: Re: issues with migrating to SL 7.6
Da: Gilles Detillieux
A: "S. Vergani" ,John Pilkington
CC: scientific-linux-users@fnal.gov
Hi,
Hi, Stefano.
Don't pay too much attention to the SL version number in the grub2 boot
menu. These labels are set when the kernel is installed or updated, and
don't necessarily reflect the SL version you're currently running. If
you updated the kernel to the latest version (3.10.0-957.1.3.el7) b
sable glamor on that system too.
On 12/4/18 11:33 AM, Andreas Nowack wrote:
Hi Gilles!
Am 03.12.18 um 21:20 schrieb Gilles Detillieux:
Section "Device"
Identifier "Radeon"
Driver "radeon"
# Option "AccelMethod" "glamor"
Optio
018-12-03 14:20, Gilles Detillieux wrote:
Thanks, Pat.
Yes, I've done more digging since speculating on the cause of this,
and that confirms that it's something deeper than that. It seems the
problem is the ati driver hasn't kept up with changes to the Xorg 1.20
server. There is
is really only related to udev probing.
There was a large jump in the ati driver from 7.5 to 7.6. My initial
thoughts are in that direction...
Pat
[1]
https://urldefense.proofpoint.com/v2/url?u=https-3A__gitlab.freedesktop.org_xorg_xserver_commit_0816e8fca6194dfb4cc94c3a7fcb2c7f2a921386&d=DwIDbA&c
Thanks for the feedback, Andreas. That saves me some testing time. It
looks like the security bug
(https://urldefense.proofpoint.com/v2/url?u=https-3A__access.redhat.com_security_cve_cve-2D2018-2D14665&d=DwIDbA&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8
I've gotten the same errors on one of my SL 7 systems since the updates
on Monday & Tuesday last week. I thought it was a hardware failure of
the on-board GPU (an ASUS M5A78L-M/USB3 motherboard with on-board Radeon
3000), so I put in a PCIe graphics card (Radeon X1300/X1550) and didn't
have fur
I got one of those e-mails yesterday too. I hadn't looked that closely
at the headers, but you're right, it does seem that the Fermilab
Listserv has been moved to Microsoft servers (outlook.com &
office365.com in the Received headers). Other people who've reported
this removal on this list all
zN as revealed
through a ls of /dev/ .
Question: what does one do if, after inserting a USB storage device,
one gets /dev/xyz, say, but there is no /dev/xyzN despite parted
reporting that the device does indeed have "MS" partitions as well as a
filesystem?
On 09/26/2018 07:47 AM, Gill
On 09/26/2018 08:34 AM, Howard, Chris wrote:
Why do parted and mount have this difference?
/dev/sdg1 ?
What he said.
/dev/sdg is the whole device
/dev/sdg1 is the first partition on that device.
Partitions have file systems. Partitions with file systems can be mounted.
parted works on the wh
According to me:
> According to Eve V. E. Kovacs:
> > When I try to use the gui interface provided in
> > /usr/bin/system-config-printer
> >
> > on an SL6 system I get the error:
> >
> > File "/usr/share/system-config-printer/system-config-printer.py", line 28,
> > in
> > import gtk.glade
According to Eve V. E. Kovacs:
> When I try to use the gui interface provided in
> /usr/bin/system-config-printer
>
> on an SL6 system I get the error:
>
> File "/usr/share/system-config-printer/system-config-printer.py", line 28,
> in
> import gtk.glade
> ImportError: No module named gtk.
On 2018-05-23 17:26, Orion Poplawski wrote:
On 05/15/2018 05:45 PM, Orion Poplawski wrote:
On 05/15/2018 05:41 PM, Orion Poplawski wrote:
On 05/15/2018 12:23 PM, Maarten wrote:
I have the same problem on all of my systems, running the same package
versions and kernel, also under 7.5:
libsepol
On 2018-05-12 04:29, jdow wrote:
On 20180511 21:26, jdow wrote:
I have yum-conf-sl7x.noarch installed. 7.5 seems to be out. But yum
update still leaves the system declaring it is 7.4.
{o.o} Joanne
At least that's what I get on one system. The other is still declaring
7.3:
[... /etc]$ cat
It appears that there was a problem in how the updateinfo.xml file was
built for the sl-security repository yesterday, which conflicted with a
similar entry for the SLEA-2017:1977 ID in the sl repository. Whatever
it was seems to have been repaired now, because I'm not seeing this same
error to
On 05/01/2018 11:26 AM, Marius Rometsch wrote:
Hello dear SL Users,
I was directed here from the scientificlinuxforum.org because I seem to have
encountered unusual behavior of yum and SL.
I switched from OpenSUSE to SL7 yesterday and while setting it up, yum could
not install or update any pac
On 03/09/2018 03:00 PM, Stephan Wiesand wrote:
On 09.Mar 2018, at 21:51, Gilles Detillieux
wrote:
I wasn't sure if you could safely mix code compiled with and without the
retpoline extensions into the same kernel, which is why I thought the Makefile
threw an error.
Looks like upstream
Pat
On 03/08/2018 11:46 AM, Gilles Detillieux wrote:
I realize this problem was likely introduced by upsteam updates, but I thought
I'd point it out here anyway so you're aware of it. An unintended consequence
of this latest kernel update is that it breaks recompilation of third-party
I realize this problem was likely introduced by upsteam updates, but I
thought I'd point it out here anyway so you're aware of it. An
unintended consequence of this latest kernel update is that it breaks
recompilation of third-party kernel modules. The new kernel was built
with CONFIG_RETPOLINE
19 matches
Mail list logo
