Date: Mon, 10 Sep 2001 23:05:07 -0400 From: "Andrew C. Hornback" <achornback@worldnet.att.net> To: "FreeBSD-Questions" <freebsd-questions@freebsd.org> Cc: <freebsd-smp@freebsd.org> Subject: Breakage - Compaq ProLiant 1500 (SMP) Message-ID: <007001c13a6e$8f91dfc0$0e00000a@tomcat>
next in thread | raw e-mail | index | archive | help
(Note: Crossposted with the SMP list, please CC replies from there as I'm not subscribed, ATM) Hi everyone, I'm working on setting up this old ProLiant server for the local community college here (I'm donating the machine), and I'm having some trouble. The machine used to have 4.2-Release on it, and booted fine (recognized the funky RAID controller, recognized all 64 Megs of memory, and even recognized both processors). I took it out of storage, went to put 4.3-Release on it (latest version I've got), and all sorts of things have started going wrong. Here's what it's doing: 1. Install with 4.3-Release works fine (recognizes the RAID controller, only sees 16 Megs of memory [already noted problem with this model], and only seems one processor as per the GENERIC kernel). 2. I recompile with support for the amount of memory in the machine (64 Megs), and it works fine. 3. I recompile with support for SMP, and things go haywire. I end up with: no such device 'idad' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: <fstype>:<device> Mount <device> using filesystem <fstype> eg. ufs:/dev/da0s1a ? List valid disk boot devices <empty line> Abort manual input mountroot> When I input ?, I get: Possibly valid devices for 'ufs' root: "console" "ctty" "mem" "pts" "ptc" "log" "fd" "sc" "sa" "cd" "FD" "bpf" "sio" "pass" "tun" "pci" "md" "xpt" "kbd" "asr" "MFS" No "idad" listed. I'm out of ideas. I could go back to 4.2-Release and be able to use both processors, all of the memory and the RAID. I could stick with 4.3-Release and use one processor. Or, we can figure out what the problem is here and get this thing working properly. I'd like to eventually track the STABLE branch once I get the machine on the network it will eventually be on (I don't currently have the bandwidth for getting STABLE onto it). Also, I realize a dmesg output would be handy on this one, but I'm not sure how I would go about getting it as I have to do a reboot at this point in order to get the machine to where I can get the output from dmesg! There's no major rush on this, but I'd like to get it fixed as soon as possible. Any ideas? --- Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?007001c13a6e$8f91dfc0$0e00000a>