FreeBSD installation problem - hex code streaming down the screen

Lord Evermore

Diamond Member
Oct 10, 1999
9,558
0
76
This is really weird. I'm building a FreeBSD server (used to be Win2k but it kept crashing). The Acer CDRW drive I've got it in apparently doesn't support CD booting or is just broken (verified the CD itself works and the BIOS does attempt to boot to CD).

So I'm trying to do a floppy boot. I KNOW this should work, as I've done it once already with this exact same system. The server sits at my office, before I brought it home to work on it, I started a FreeBSD network install, booting from floppy, just because I had spare time at work and wanted to see what it looked like. That worked fine, and I got all the way to creating the hard drive partitions/slices before I stopped and took it home.

Now, I've got almost the same system. The only difference is that I changed the hard drive to a larger one (and it is a known good drive, and the problem doesn't even involve the hard drive).

So, I create a new set of boot floppies using the images on the freebsd.org server. Boot, it seems to work fine, and it gets all the way to the boot prompt (press enter to boot or any other key for a command prompt) and it automatically started booting the kernel. After a few seconds of the cursor spinning thing, text starts streaming down the screen, sort of like the Matrix. It appears to be hex code, but it's going too fast to make out exactly what it says. Each line goes about 2/3 across the screen, in 4 columns, and it appears to be 2 or 3 lines that repeat.

So I figured maybe one of the floppies was corrupted, since I couldn't think of anything else to cause this. I reformatted them, reimaged them, and the same thing happened. So I tried two other floppies, and they do the same thing.

By the time anybody reads this or feels like responding, I'll probably have resolved it by swapping in a CD drive that can CD boot, but it'd be nice to figure out what the problem is.
 

n0cmonkey

Elite Member
Jun 10, 2001
42,936
1
0
wow, Ive never seen this problem (or one like it before). Im wondering if the new hard drive has something to do with it after all. Try putting the old hard drive back in (if you can) and try the install again just to see what happens.
 

Lord Evermore

Diamond Member
Oct 10, 1999
9,558
0
76
Freakiest thing, but I fixed it.

First I reformatted and did a surface scan on the floppies to be sure they weren't just bad (all 4?, don't think so). They were fine.

So I tried was re-enabling AGP 4X. I'm using a Stealth III S540 Extreme for video, and I'd disabled 4X simply to maybe avoid any compatibility issues. (I did also update the BIOS when I got it home, so I had to reset everything there, and did that at the same time.)

That got me to the point that now the system was rebooting every time it tried to boot to the kernel, rather than the text on the screen.

So, I figured I'd see if some of the BIOS settings were just making the system unstable. First thing, turned the memory down to 100MHz (though I'm almost positive it's PC133, but I haven't checked again yet). It was sitting at 133MHz CAS3, so it wasn't like I was doing CAS2 on it or anything. Reboot, suddenly it works fine.

I'm going to check to see what memory I have in there. It may well be PC100, or maybe one stick of it is and the rest is 133, but I thought otherwise since I'd been wanting to make this a high performance game server.
 

n0cmonkey

Elite Member
Jun 10, 2001
42,936
1
0


<< Freakiest thing, but I fixed it.

First I reformatted and did a surface scan on the floppies to be sure they weren't just bad (all 4?, don't think so). They were fine.

So I tried was re-enabling AGP 4X. I'm using a Stealth III S540 Extreme for video, and I'd disabled 4X simply to maybe avoid any compatibility issues. (I did also update the BIOS when I got it home, so I had to reset everything there, and did that at the same time.)

That got me to the point that now the system was rebooting every time it tried to boot to the kernel, rather than the text on the screen.

So, I figured I'd see if some of the BIOS settings were just making the system unstable. First thing, turned the memory down to 100MHz (though I'm almost positive it's PC133, but I haven't checked again yet). It was sitting at 133MHz CAS3, so it wasn't like I was doing CAS2 on it or anything. Reboot, suddenly it works fine.

I'm going to check to see what memory I have in there. It may well be PC100, or maybe one stick of it is and the rest is 133, but I thought otherwise since I'd been wanting to make this a high performance game server.
>>



Well thats cool. Ive never really had any problems installing FreeBSD, but I actually havent installed it on a recent machine since probably 4.0
 

tweakmm

Lifer
May 28, 2001
18,436
4
0
Sure, I've never run BSD in my life, and am just starting to use linux,
I can safely say, i would love to see that
 

n0cmonkey

Elite Member
Jun 10, 2001
42,936
1
0


<< Sure, I've never run BSD in my life, and am just starting to use linux,
I can safely say, i would love to see that
>>



A failed installation? :p
 

n0cmonkey

Elite Member
Jun 10, 2001
42,936
1
0


<< What do you mean? >>



You said you would like to see that. I was wondering if what you wanted to see was a failed FreeBSD isntallation. Sorry bad joke.
 

tweakmm

Lifer
May 28, 2001
18,436
4
0
lol, yeah, I get it now. I was kinda slow yesterday(not enough sleep for 2 weeks:()