Re: Not enough info, so no point
- From: Louis Lagendijk <louis@xxxxxxxxxxxxxxxxxxx>
- Date: Fri, 03 Jun 2011 16:41:50 +0200
On Fri, 2011-06-03 at 15:15 +0100, n2xssvv.g02gfr12930 wrote:
The probability is quite (not to say very) high that this will solve theCurrently nothing is attached to the SCSI controller. So I'm wondering
if I actually remove it, the problem will disappear.
issue, yes. If not, I would run e memtest to see if you have memory
issues.
I'm fairly sure the Fedora 15 install is mostly up to date, as IMount the F15 on /mnt including the additional mount point, chroot /mnt
installed direct from the Fedora repos, release and updates.
and you run yum update as suggested in the other mail. No meed to stop
This should be a riskless operation. It is actually also what a rescue
operation does, but in this case you can use the F14 network setup that
makes it even easier. I would hoever recommend removing the SCSI
controller first
Louis
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
- Follow-Ups:
- Re: Not enough info, so no point
- From: n2xssvv.g02gfr12930
- Re: Not enough info, so no point
- References:
- Re: Not enough info, so no point
- From: Marko Vojinovic
- Re: Not enough info, so no point
- From: n2xssvv.g02gfr12930
- Re: Not enough info, so no point
- From: Marko Vojinovic
- Re: Not enough info, so no point
- From: n2xssvv.g02gfr12930
- Re: Not enough info, so no point
- Prev by Date: Re: CUPS service not starting after upgrade to F15
- Next by Date: Re: F15: fail2ban not in iptables status
- Previous by thread: Re: Not enough info, so no point
- Next by thread: Re: Not enough info, so no point
- Index(es):