I have been trying to build a usable PC out of old - but previously
unused hardware (motherboards, CPUs, RAM, 80GB Seagate disks, power
supplies) - but whatever combination I use I continually get core dumps
- I have reinstalled on numerous occasions and sometimes the PC works
for hours without a problem and then fails - but quite frequently it
fails on bootup! I have tried with 2G RAM but that had problems so I
went back to 1G thinking that one SIMM might be faulty but no
combination works for any reasonable length of time.
I can't do screen captures of course but I have taken a photo of the
most recent crash and I can see:
- at 21s:
search_binary_handler+ . . .
do_execve_common+ . . .
SyS_execve . . .
Code: . . . string of two digit hex numbers
EIP: . . .
CR2: . . .
--[ end trace . . .
firewalld: segfault at . . .
- at 3308s:
----------------------[ cut here ]---------------------------
kernel BUG at fs/ext4/inode.c:2393!
invalid opcode: 0000 [#2] SMP
Modules . . .
CPU 0 PID: 29049 . . .
Hardware name: /865M01, BIOS 6.00 PG 12/25/2004
task: . . .
EIP: . . .
EIP: . . .
EAX: . . .
ESI: . . .
BS: . . .
CR0: . . .
Stack: . . .
Code: . . .
EIP: . . .
--[ end trace . . .
I can put this 2.3M photo somewhere if it is of use for anyone to look
at? Any ideas what the problem(s) might be? It sort of looks like a
RAM problem to me but ALL the SIMMS can't be faulty . .
GPO Box 3411
Sydney NSW 2001
As I type this, I'm installing Fedora 20 on a UEFI system which already
has CentOS 7 (and nothing else).
Should the two systems share /boot/efi?
As I understand it, the answer is yes: /boot/efi is universal on a
machine. It is where the firmware goes to load things. Not just OS
bootloader: manufacturer-supplied EFI utilities can live there too.
But Fedora, by default, wants to create a new /boot/efi.
What is the right thing to do? What will work?
In the current installation, I've forced Fedora to use the existing
/boot/efi. I guess I'll see how that turns out.
I could not see any guidance in the Fedora 20 installation guide.
In fact, the appendix on disk partitions didn't deal with
EFI/UEFI/GPT, something I could have used. (After 20 years of living
with MBR, I kind of got the hang of it.)
See inline responses to three replies:
> Date: Sun, 31 Aug 2014 17:22:23 +0930
> From: Tim <ignored_mailbox(a)yahoo.com.au>
> On Sun, 2014-08-31 at 14:12 +1000, Philip Rhoades wrote:
>> It sort of looks like a RAM problem to me but ALL the SIMMS can't be
> Well, they can... When it comes to recycling, all bets are off,
> particularly if nobody took anti-static precautions while handling the
I haven't had that sort of bad SIMM frequency before but it is possible
I guess . .
> But, for the sake of a simple thing to try, I'd try cleaning the
> contacts in the RAM sockets, and the on the RAM sticks, with electrical
> contact cleaner and lubricant. Likewise, for other plug-in cards.
OK, I will try that when I am on site again in a week or so.
> If you have another power supply to try, substitute it.
Yep, did that with a new (current) PS - crashed on bootup . .
> Date: Sun, 31 Aug 2014 10:48:37 +0200
> From: Ralf Corsepius <rc040203(a)freenet.de>
> On 08/31/2014 06:12 AM, Philip Rhoades wrote:
>> I have been trying to build a usable PC out of old - but previously
>> unused hardware (motherboards, CPUs, RAM, 80GB Seagate disks, power
>> supplies) - but whatever combination I use I continually get core
>> - I have reinstalled on numerous occasions and sometimes the PC works
>> for hours without a problem and then fails - but quite frequently it
>> fails on bootup! I have tried with 2G RAM but that had problems so I
>> went back to 1G thinking that one SIMM might be faulty but no
>> combination works for any reasonable length of time.
> Which CPU are you using? Unless it's a hardware defect somewhere, I'm
> inclined to believe you could be trying to run an incompatible kernel.
Hmmm . . that MB is for Socket478 processors and I definitely installed
the 32 bit F20 (LiveCD install) - how could it be incompatible? Would
F20 64bit even install?
> Date: Sun, 31 Aug 2014 02:48:40 -0700
> From: Tod Merley <todbot88(a)gmail.com>
> Yes, I think a HW list along with the SW being tried would likely prove
> helpful here.
OK, that will have to wait till I can get back on site again too - of
course my remote ssh connection doesn't work now because of another
crash - I'm surprised it lasted as long as it did!
> On Sun, Aug 31, 2014 at 1:48 AM, Ralf Corsepius <rc040203(a)freenet.de>
>> On 08/31/2014 06:12 AM, Philip Rhoades wrote:
>>> I have been trying to build a usable PC out of old - but previously
>>> unused hardware (motherboards, CPUs, RAM, 80GB Seagate disks, power
>>> supplies) - but whatever combination I use I continually get core
>>> - I have reinstalled on numerous occasions and sometimes the PC works
>>> for hours without a problem and then fails - but quite frequently it
>>> fails on bootup! I have tried with 2G RAM but that had problems so I
>>> went back to 1G thinking that one SIMM might be faulty but no
>>> combination works for any reasonable length of time.
>> Which CPU are you using? Unless it's a hardware defect somewhere, I'm
>> inclined to believe you could be trying to run an incompatible kernel.
Thanks people - more info to come later!
GPO Box 3411
Sydney NSW 2001
hi all, I just had a question. so I have been hearing that md5 has been
compromised, how much of a security threat does this impose? if it is
something that poses a large concern is it possible to change the
encryption method from md5 to crypt? or another method that is not
I was recently gifted an old Dell Latitude E6400 laptop and, given its age
and what I've read, I thought getting Fedora 20 going on it would be smooth.
And, to some extent, it was. I was primarily concerned with the wireless,
but that seems to have been fixed for some time.
Sadly, it wasn't without issues. I'm currently having issues getting my
trackpad and my webcam going. I've done some looking around with no luck.
For the touchpad, I get basic functionality. I can "tap to click" and use
the pointer, but I can't use the scroll areas on the side/bottom for
scrolling. Clicking both physical buttons don't perform a middle-click, and
tapping with 2-fingers don't give me a "right" click. Going under "mouse &
touchpad" in Settings only gives me very basic options.
Running "xinput list" shows it being seen as a "PS/2 ALPS DualPoint
TouchPad". Searching for Fedora and this don't yield much/anything.
I'm running Fedora 20 updated as of today. Kernel is
I also would like to get the webcam going. When I try to run Cheese, I get
a "no device found" error. Running lsusb doesn't show a camera attached.
Any help would be greatly appreciated. Thank you.
I'm attempting to switch to Linux from Mac OS on a Macbook Pro model number
MacBookPro10,1 with the latest BIOS and firmware. I need to have full-disk
encryption for work, so I allowed the fedora installer to set up an
encrypted LVM volume alongside my Mac partition (I'm dual-booting). But
alas! Upon booting for the first time, I get this error message:
(In yellow) [3.226029] pci 0000:00:01.0: ASPM: Could not configure common
[4.258867] i915 0000:00:02.0: Invalid ROM contents
The boot then hangs...and nothing happens.
i915 refers to the graphics chipset on my laptop. I had previously tried
Ubuntu (which didn't end up being what I was looking for) and found that
when I installed the server version, without the graphical boot, Ubuntu
booted, but when I installed the desktop version, with a graphical boot, it
So I currently wish to disable graphical boot in Fedora. I'd also be happy
to do a new installation to get rid of the graphical boot if that's what it
Any kind advice?
When using firefox I'm repeatedly confronted by a popup asking if I want
to install flash (usually to view some advertising). This must happen
dozens of times a day.
Does anybody know if it is possible to stop that, and if so, how to do it?
> On my old system I use 1TB disks, with /boot as raid1, and grub
> boot-loader installed on all disks. On that one I can boot the system
> from any of disks. Which is quite handy.
> The problem here seem to be that due to the disks being large (larger
> than 1TB) they are setup as GPT (GUID Partition Table), and they then
> also need a BIOS boot partition to work on non UEFI based systems (if I
> have understood it correctly).
> So, to be able to boot from any of the disks, I need a BIOS boot
> partition on all disks, but anaconda seem to only install it on one of
> the disks (i.e. I want the exactly identical partition tables on all disks).
gdisk will seamlessly convert an existing DOS partition table made by say
fdisk, parted, gparted, ... to GPT format on the fly without disturbing the
any actual parttions ( you may want to back up first though ... ) .
Additionally, I have not had any problems getting 3-4 year old standard dumb
BIOS to boot from a 3TB drive . Never tried with UEFI though.
Is it just me? After closing Chrome, ps -ef |grep chrome shows a chrome
process running for each tab I had open. I have unchecked the option to
allow background processes to run after closing chrome.
killall chrome does not kill them.