Re: PII SMP system hangs during boot with ACPI enabled
Nate Lawson writes: No way! Good (non-386) equipment is never to old. :) Please add debug.acpi.disable=cpu to loader.conf or type that in at the loader prompt. If it boots ok, we'll have to debug the acpi_cpu_startup path. Speaking of which, I have a Good (see above...) motherboard looking for a worthy home. It's a dual 266MHZ processor PII motherboard (Supermicro P6DLE) with 256MB of ram. It was running just fine when I removed it from it's case (I upgraded that box to a 370DLE). It's been comfortably running -stable for a long time, and deserves a good home. Some info is available at: http://www.supermicro.com/PRODUCT/MotherBoards/440LX/p6dle.htm It's free to anyone who can convince me that they'll give it a good home. g. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
More info [was Re: Sony PCG-GRX570 laptop, panic on boot w/ 5.1R...]
George Hartzell writes: I've been trying to install something 5-ish on a Sony PCG-GRX570 laptop. I started off trying to boot off of the 5.1 release CD, normally, w/out acpi, and safe. Every option panic-ed, with essentially the same message (see below), although it followed a different driver depending on how it was booted. Then I installed 4.7 (since I had the CD), cvsup-ed my repository, and cvs up'ed /usr/src to the 5-current. I followed the section on moving from 4 to 5-current in UPDATING to build the world, etc I had to work around a bit of previously reported 4.7/5 weirdness in /usr/include, but it went w/out any trouble. When I reached the point where I was supposed to boot the new kernel in single user mode, the 5-current kernel paniced: miibus0: MII bux in fxp0 inphy0: i82562ET 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x63696d20 fault code = supervisor write, page not present instruction pointer= 0x8:0xc0659df3 stack pointer = 0x10:0xc0c217ac frame pointer = 0x10:0xc0c217cc code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process= 0 (swapper) kernel: type 12 trap, code=0 Stopped at ithread_add_handler+0x163: movl%ebx,0(%eax) db I've seen several similar reports in the archives for late last summer. The general answer seemed to be that people were having hardware trouble. I don't think that is the case in my case, unless -current is doing something very strange, since the same machine runs well enough under 4.7 to buildworld and buildkernel, and the same hardware has been running Suse and Win2000. How can I help get this solved? It turns out that the 5.0 release CD also boots successfully, so it seems to be something that's happened in -current since then. Help? g. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Sony PCG-GRX570 laptop, panic on boot w/ 5.1R and -current
I've been trying to install something 5-ish on a Sony PCG-GRX570 laptop. I started off trying to boot off of the 5.1 release CD, normally, w/out acpi, and safe. Every option panic-ed, with essentially the same message (see below), although it followed a different driver depending on how it was booted. Then I installed 4.7 (since I had the CD), cvsup-ed my repository, and cvs up'ed /usr/src to the 5-current. I followed the section on moving from 4 to 5-current in UPDATING to build the world, etc I had to work around a bit of previously reported 4.7/5 weirdness in /usr/include, but it went w/out any trouble. When I reached the point where I was supposed to boot the new kernel in single user mode, the 5-current kernel paniced: miibus0: MII bux in fxp0 inphy0: i82562ET 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x63696d20 fault code= supervisor write, page not present instruction pointer = 0x8:0xc0659df3 stack pointer = 0x10:0xc0c217ac frame pointer = 0x10:0xc0c217cc code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) kernel: type 12 trap, code=0 Stopped atithread_add_handler+0x163: movl%ebx,0(%eax) db I've seen several similar reports in the archives for late last summer. The general answer seemed to be that people were having hardware trouble. I don't think that is the case in my case, unless -current is doing something very strange, since the same machine runs well enough under 4.7 to buildworld and buildkernel, and the same hardware has been running Suse and Win2000. How can I help get this solved? g. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTLDR missing after 5-RELEASE install
Andrew Boothman writes: [...] OK Guys, I think I'm still a little confused here. I've just had a few botched installs of GRUB so I think I need a little more direction, if you could :) I've got GRUB on a floppy and it boots fine. If I type : rootnoverify (hd0,0) makeactive chainloader +1 boot I get Win2k booted no problem! So, following the instructions in the Grub Manual, I typed root(fd0) setup(hd0) I remove the floppy from the drive and reboot On boot I get Loading GRUB... Please Wait... but after that I get GRUB Error 17 which according to the manual means that GRUB doesn't know how to load the selected partition. Even though when I boot from the floppy it starts no problem and I can type commands to get it to boot Win2k That told it to install GRUB into the beginning of (hd0) [e.g. the Master Boot record], but configured it to use (fd0) as the root of the place to find stuff. Since the floppy wasn't in when you booted, it didn't do anything useful. There are some grub things that need to be on the disk that you give the root designation too, e.g. stage1, etc... I don't know how/where to install those files into an NTFS partition, I assume that GRUB can read NTFS filesystems, and you could tuck them there, but I don't know for sure. Here's what I'd do. Get yourself booted into freebsd any way that you can. PRINT OUT THE INFORMATION ABOUT YOUR BIOS PARTITION TABLE AND YOUR FREEBSD DISKLABEL, AND SAVE IT. fdisk -s and disklabel -r diskname are your friends Build grub from the ports tree and install it. It installs all of the juicy bits into some directory in /usr/local/share/grub/i386-freebsd/..., which doesn't seem to be a place where grub can find it. I make a directory called /boot/grub and copy all of them there. Start grub (e.g. boot from your grub floppy). Under the 5.0 systems, GEOM is picky about letting you doink with disks that you have mounted, so you either need the let me shoot myself in the foot sysctl patch (ftp://ftp.jurai.net/users/winter/patches/geom-foot.patch) or boot from something else (e.g. floppy, live cdrom, ...) Make sure that grub can see it's various interesting bits: grub find /boot/grub/stage1 and it should say: (hd0,1,a) assuming that you have Something Else (e.g. windows) in the first primary BIOS partition/slice, a set of FreeBSD slices in the second primary BIOS partition/slice, and the /boot/grub stuff is in the first (a) BSD_DISKLABEL/slice. If you have the grub bits living in a Linux filesystem in the third primary BIOS partition, it'd say (hd0,2). If you had them in a Linux filesystem living in the first extended partition, it'd say (hd0,4), etc That's the drive that you want to declare as your root, which just configures the low level grub code that setup installs so that it knows where to look for it's various useful bits. e.g. grub root (hd0,1,a) Then you need to install grub onto somewhere where the computer will trip over it and boot it. One possibility is to install it into the master boot record, which would be: grub setup (hd0) Here you boot process would be power on-bios-load the MBR which is really GRUB-grub loads its stage1,... Or you could leave a normal MBR at the beginning of the disk and install GRUB into the beginning of the FreeBSD BIOS partition (assuming that FreeBSD is in the second primary parition): grub setup (hd0,1) If that's all that you do, thing's won't quite boot. You'll need to also mark that partition active, so that the stock MBR code will jump to it. I always do that by getting to this point, booting by hook or by crook (e.g. a grub boot floppy, a bootable freebsd CD, a bootable linux CD) and using some utility (e.g. partition magic from windows, fdisk from windows, fdisk from freebsd, fdisk or cfdisk from linux) to mark the partition active. I prefer partition magic because I believe that it has the most robust partition table integrity checks, but whatever you trust Now, your boot process will look like: power on-bios-real MBR which jumps to the active parition - (next line) ... - GRUB at the beginning of active partition - GRUB stage1,... When grub get's up and running, it'll look for a file called menu.lst (unless you override the name when you setup) which contains the info for the boot menu. Here's mine (notice that there are a bunch of mutually exclusive things that I've tucked into the 3rd BIOS partition at various times and I just keep the info around for reference. As long as I don't actually choose any of the wrong selections, there's no trouble. default=0 timeout=10 title FreeBSD 4.7 root (hd0,1,a) kernel /boot/loader title FreeBSD 5.0 root (hd0,2,a) kernel /boot/loader title Redhat Linux 8.0 root (hd0,2) kernel /boot/vmlinuz-2.4.18-14 ro root=/dev/hda3 initrd /boot/initrd-2.4.18-14.img title Redhat Linux 8.0 (hires) root (hd0,2)
Re: NTLDR missing after 5-RELEASE install
George Hartzell writes: [...] grub setup (hd0) Here you boot process would be power on-bios-load the MBR which is really GRUB-grub loads its stage1,... Or you could leave a normal MBR at the beginning of the disk and install GRUB into the beginning of the FreeBSD BIOS partition (assuming that FreeBSD is in the second primary parition): grub setup (hd0,1) I left out a detail: I use the --prefix=/boot/grub option to setup. e.g. setup --prefix=/boot/grub (hd0) or setup --prefix=/boot/grub (hd0,1) g. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: NTLDR missing after 5-RELEASE install
Andrew Boothman writes: [...] It's possible I guess that we both suffered from the same problem. I'd be inclined to think that it must be operator error over something wrong with sysinstall since I've not seen people complaining of these problems before, yet there must be loads of people dual-booting. Having said that, I still can't understand what I did differently or how to prevent the same thing from happening in the future. I guess I'll just use GRUB or something instead. Looks like my Windows drive is heading for a reformat :-/ I'm pretty sure that it's not operator error on my part, since it happened several times. I suspect that there aren't that many people playing with 5.0 that don't install the standard boot stuff, and so that path isn't exercised too much. It happened repeatedly for me, and one of the things that's on my list of things to do is to recreate it and file a PR, but it hasn't risen to the top of the queue yet. It's a bit problematic because I don't really want to loose the contents of that drive (it takes *forever* to get windows and office updated after the intial installs: reboot, reboot, reboot...) and it's not hard to imagine that whatever's bitten me the past few times might get me irrecoverably the next time... GRUB is cool. Backup's of your partition/slice/disklabel info are extra cool. g. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: NTLDR missing after 5-RELEASE install
Darryl Okahata writes: [...] I installed 5.0 with the booteasy MBR on my IBM laptop, and it worked fine. The problem I had was that *ANY* MBR-based boot program interfered with IBM's special product recovery software, and so I instead decided to just use Win2K/XP's boot mechanism to boot FreeBSD (as I explained in my previous message). [ Yes, FreeBSD and XP (in my case) would still have worked if I kept booteasy, but I really wanted to keep IBM's product recovery software, and so I switched to using 2K/XP's method. In hindsight, that's probably the best approach, as it doesn't require any MBR changes or boot floppies/CDs. ] What we're doing is almost the same thing. In your case, your windows partition is the active partition, so you run the vendor's MBR, which jumps to the Windows loader, which jumps to whatever you choose. MBR -- NTLR ---+-- FreeBSD | +-- Windows I mark the partition that contains grub active (these days have a freebsd world in my second slice/partition, with grub installed at the beginning of that) and use it to jump wherever. MBR -- GRUB ---+-- FreeBSD | +-- Windows Only differences are which partition we mark active and what boot loader lives there. g. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: NTLDR missing after 5-RELEASE install
Darryl Okahata writes: [EMAIL PROTECTED] (George Hartzell) wrote: Only differences are which partition we mark active and what boot loader lives there. True, but that's the key point: ... and what boot loader lives there. There are times when not touching the boot loader is desirable. While GRUB, booteasy, and others are quite perfectly usable for many people, some of us may be better off with an untouched MBR. But I'm not touching the MBR either. I run a stock sony vaio MBR, and install GRUB into the beginning of my freebsd partition. GRUB and LILO behave nicely there, the standard freebsd boot loader (booteasy?) seems to insist on being in the MBR. If I boot windows, my boot sequence goes MBR - GRUB (because it's installed in the beginning of the partition that's marked active) - the window's loader (because grub's been told to chainload to the loader that's in the beginning of the first partition) -- windows. FreeBSD goes something like MBR - GRUB (ditto, above) -- /boot/loader from the freebsd filesystem (because that's what grub's been told to load for that title loader does the normal freebsd stuff, loading the kernel and going for it. It's also possible to have grub boot the freebsd kernel directly, but I like to have both boot up in as much of a native world as possible. g. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: NTLDR missing after 5-RELEASE install
Andrew Boothman writes: [...] I didn't really change much about my system when I installed FreeBSD. Windows is installed on the whole of the first HDD, and FreeBSD on the whole of the second. Prior to installing 5.0, the second disc had an old installation of 4.6 that I wasn't using. When installing, I asked sysinstall to install booteasy on the first drive, but otherwise leave it unchanged. I removed the existing slice on the second drive and got sysinstall to create a new slice filling the drive, I then allowed sysinstall to auto-size the partitions and complete the installation. I've tried every repair option that I can find on the Win2k CD. I've tried the fixboot and fixmbr commands in the recovery console many times, and despite fixmbr complaining about an unusual mbr every time, installing a new one apparently makes no difference. I eventually managed to remove booteasy from the first drive so that NTLDR is missing appears straight away, but that is hardly a victory. I even followed Microsoft's instructions in knowledgebase article 318728 and performed a brand new installation of windows into c:\tempwin but even this new installation failed to boot with the same problem. Therefore it would seem that whatever the problem is, Win2k's setup prog either can't fix it or is oblivious to it. It's looking more and more like I'm going to have to reformat this drive as I seem to have no way of getting Win2k operating again, but I'd _really_ like to understand what happened here, not least to ensure I don't repeat the same problems when I come to try and dual- boot again! Apologies for this getting increasingly off-topic, but I can't understand what I've done wrong here as I've done this many times before with 4.x. As ever, any light-shedding would be much appricated :) I had several problems installing 5.0 release onto my sandbox machine, and the solution might be relevant. My sandbox machine had a single disk, uses a stock (what came on the drive) master boot record, and had several primary partitions (aka slices). The first partition/slice contained a windows2000 install, the second partition had a linux installation w/ the GRUB boot loader installed in the beginning of the partition. The linux parition is marked active (using Partition Magic from windows), so the normal boot sequence goes: MBR -- GRUB ---+-- Linux | +-- Windows depending on the choice made in grub. I boot this way because the sandbox machine is a test environment for my laptop, and suspend to disk stuff doesn't seem to work on the laptop unless the vendor's MBR is in place. My intent was to add Freebsd to the third partition. I ran through the install and told the installer to just leave the MBR alone. Among the things that I discovered were: - both the linux partition *AND* the newly installed FreeBSD partition ended up marked active. - There was a problem with data somewhere in the BIOS/DOS partition table concerning CHS values and LBA values for various parts of the partition. (might have the acronym's wrong). Both of these rendered the machine unable to boot, I recovered it once by booting from a floppy, getting into windows, and running partition magic, and on a separate test run by booting from a live linux cd and playing with various fdisk-oid programs available there. So, all that said, maybe your partition table is slightly scrod, not so badly that it won't get through the MBR but badly enough that it can't find the NT partition? It'd be interesting to see what parition magic had to say about it. g. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
