Anyone out there have linux running on a DFI PS35-BL? I have been unable to perform a Redhat install. I get kernel dumps and interrupt exceptions from 7.3,8,9,2.1 and now 3. I have the latest bios and have disabled practically everything including sata,apic,usb and ide. The only card installed in a pci slot is a single adaptec controller card. If the DFI does not work with Redhat, what motherboard is recommended for Redhat. I have an Intel 2.0 GHZ cpu with PC2700 memory. I would hate to spend $700-1500 for a HP blade server. I just wanted to play around with Linux at home.

Very strange. No idea about that mainboard specifically, but if you can post the exceptions or kernel logs or something, us folks might be able to help you out.

<i>Knock Knock, Neo</i>

I cannot get any Linux distribution to install at all, so no logs are available.

Here are some exceptions that I have written down from the display screen:
Freebsd - fatal trap 12: page fault while in kernel mode, trap =12, page fault, current process = 20 (swi3: cambio)
termiate acpi, panic vm_page_free: freeing free page

mandrake - error exec of stage 2 fatal error in stage 1, I can't recover from this install exited abnormally received signal 11

redhat - installed exited abnormally - received signal 11, sending termination signal, sending kill signal, disabling swap, call trace ee00c5ebc code: 86 41 34 of a3 18 19 c0 31 d2 85 c0 75 15 f6 41 19 04 74 0a

Have you tried the usual burn-in and testing routine? Eg, memtest86 and friends?

<i>Knock Knock, Neo</i>

are you trying to install on a serial harddrive? if not turn the serial harddrive controller off. its not suported untill kernel 2.6
also I found the same problems with cheep memory. try this go to www.morphix.org download a live cd. boot the system. see what devices it see's. and remember red hat 9 is old try fedora core 1 and ignore post from impatent people who can' tsearch google for there answers.

Willaim S. Huskey
Network Engineer
SAIC
"there are 10 types of people in this world. They who understand binary and they how do not"

Try to ignore posts from impatient people who won't take the time to either read or spell properly, too. iccaros, you'll notice that tschus had already disabled his SATA controller and also that FreedBSD failed ungracefully as well, hence the suggestion to run diagnostics like memtest86 on the timing-critical high-speed memory. A Linux distro based on kernel 2.6 is certainly worth a shot, but the odds of that magically fixing this one are slim, in my opinion.

<i>Knock Knock, Neo</i>

Poorboy, While I apologies for my lack of grammar to a quick post nothing was aimed at you. I was am still am a little irritated at a post on a different thread (Linux is weird) where a person gave up on Fedora because he could not find his second hard drive. A simple google search would have helped this person. I feel bad if you thought it was you I was referring to. As for spelling most of it is typing errors and to my detriment at times stops people from understanding what I am trying to say. Free BSD has had problems with DDR ram I can reproduce it in my lab at work. I did miss where he said that he disabled the serial ATA but that was a suggestion that just came to mind as I had the same problem with Red Hat and Free BSD with what I thought was disabled serial ATA. Red Hat 9 has install problems with newer Ram ( I can reproduce this in the lab with Nforce2 Boards and DDR 400) and newer video cards. As for the suggestion of the Morphix cd. This is a live cd if it boots than he/she can start running more test. I agree that a memtest is an outstanding starting point. FSCK is also a good check as some motherboards with hard drive monitoring kill anaconda when the BIOS reports errors. SuSE live demo CD helped me narrow down a bad voltage control transistor (or led me in to that direction) by letting me see the voltage's reported by the BIOS and seeing what there are when it crashes. I have been able to get most live cd's to boot on systems with bad hardware and give more trouble shooting tools after running a memtest86. ( a note on older versions memtest86 as I have seen them fail on early DDR modules when the memory test good on a DIMM test machine, in other words use the newest versions available). As for the 2.6 upgrade. I put that in there because on the Linux Kernel Mailing list 2.6rc1 “i865G chipset AGP support “ is now listed with a follow up. Most problems reported with this chip set are AGP problems so I don't know if It would help his/her problem. A Power supply or memory problem can kill BSD and anaconda. So in the end I'm sorry if I offended you poorboy as I read your post on here and some have entered my Linux book of knowledge I keep.
Thanks for reading. Hope some part of this can help.

Willaim S. Huskey
Network Engineer
SAIC
"there are 10 types of people in this world. They who understand binary and they how do not"

iccaros, yes, I read your comment as being directed at me. Posting a one-line reply as I did could have been taken as an impatient non-researched post. Thanks for clearing that up.

<i>Knock Knock, Neo</i>

one more point if I enter the errors listed in to google all related messages point to a bios hang while probing hardware and 9 out of 10 point to the video chipset as the unoffical issue. What the hell disable the built in video and use an external card. what eles can go wrong. by the way acording the the book im studing for my RHCE redhat - signal 11 - means sorry try again. a sugestion is to try and look at other ttys to see if you can see at what process it dunps. (use ctrl - alt f1 f2 f3 ect.)
an abstract of the question posted to a BSD list.
while it has to do with tcp its poiting to a BIOS flag locking after a tcp stack dump.



Has anyone else seen that in the FreeBSD 5.1-p2 if one is binding to a socket
that has earliear been closed but the tcp connection is still in time wait
state will cause a panic in kernel with following error code:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x6
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc03aa50e
stack pointer = 0x10:0xdcc62c0c
frame pointer = 0x10:0xdcc62c54
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 33485
trap number = 12
panic: page fault

It seems that the problem is in the in6_pcbbind where the in6_pcblookup_local
is called (in6_pcb.c:231). If the socket has been closed the t->inp_socket
struct has been already freed and set null but the t exists because there
exists a state time wait still for the connection and that's why the
lookup_local will return a valid value for t. After the lookup_local has
returned the in6_pcbbinf will try to access t->inp_socket->so_options which
of course will cause a Fatal trap because it is a NULL pointer.

I've included as an attachment a patch that I have used to fix the problem and
allso as attached a short program which can be used to regenerate the problem
in unpatched FreeBSD 5.1-p2.

It seems that this problem also exists in the KAME SNAP.

BR. Jan


Willaim S. Huskey
Network Engineer
SAIC
"there are 10 types of people in this world. They who understand binary and they how do not"