Re: 5.1-RELEASE Windows XP dual-boot issues
On Monday 30 June 2003 7:19 pm, Scott Reese wrote: Previously, I had a dual-boot setup with FreeBSD 5.0 and Windows XP. I was using booteasy as the boot loader and I had no problem booting into either Windows or FreeBSD. However, I found myself having to reinstall FreeBSD so I decided to go with 5.1-RELEASE. As usual, I chose to use the FreeBSD boot loader on ad0 (the Windows drive) and to install a standard mbr on ad1 (the FreeBSD drive). After the install, I was able to boot FreeBSD with no problems at all, but when I went to boot up Windows, I received the dreaded 'NTLDR missing' message. So, to get the point, I was wondering if there was a way to make the Windows disk bootable again *without* having to reinstall Windows. I know that if I reinstall Windows, it will think it's king of the universe and write over booteasy and thus make my FreeBSD installation unbootable. I've tried searching google and the list archives, but, surprisingly enough (as I know there have been about a billion threads along this line), was unable to find anything useful. Any advice or pointers on how to do this would be *greatly* appreciated. This seems to be a recurring problem after 5-RELEASE. I had exactly the same problem, and I know of others that are the same. For some reason -current doesn't seem to be inter-operating well with the WinXP/Win2k loader anymore. I'm not sure if it's only happening to some installations - but I was certainly in the same boat. I ended up having to re-install Win2k and I used Grub as my new bootloader. Cheers. Andrew. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.1-RELEASE Windows XP dual-boot issues
On Monday 30 June 2003 11:36 pm, Scott Reese wrote: On Mon, 2003-06-30 at 22:10, Andrew Boothman wrote: On Monday 30 June 2003 7:19 pm, Scott Reese wrote: Previously, I had a dual-boot setup with FreeBSD 5.0 and Windows XP. I was using booteasy as the boot loader and I had no problem booting into either Windows or FreeBSD. However, I found myself having to reinstall FreeBSD so I decided to go with 5.1-RELEASE. As usual, I chose to use the FreeBSD boot loader on ad0 (the Windows drive) and to install a standard mbr on ad1 (the FreeBSD drive). After the install, I was able to boot FreeBSD with no problems at all, but when I went to boot up Windows, I received the dreaded 'NTLDR missing' message. This seems to be a recurring problem after 5-RELEASE. I had exactly the same problem, and I know of others that are the same. For some reason -current doesn't seem to be inter-operating well with the WinXP/Win2k loader anymore. I'm not sure if it's only happening to some installations - but I was certainly in the same boat. I ended up having to re-install Win2k and I used Grub as my new bootloader. This sounds promising. If you don't mind my asking, what steps did you follow exactly? I've never used grub before and I'd like to avoid reversing my current situation (having a bootable Windows installation, but suddenly rendering my FreeBSD install unreachable). Here's a message from George Hartzell that he posted to -current in response to me having trouble. For some reason I can't persuade the mailing list search mechanism to return anything at the moment so here's the message again in it's entirety : (Unfortunately - by stunning coincidence - I recently hosed by Grub installation so I can't use my own system to show others how to get it working ;) Hopefully this email will be enough to get you going) -- Forwarded Message -- Subject: Re: NTLDR missing after 5-RELEASE install Date: Thursday 27 February 2003 6:52 pm From: George Hartzell [EMAIL PROTECTED] To: Andrew Boothman [EMAIL PROTECTED] Cc: Darryl Okahata [EMAIL PROTECTED], [EMAIL PROTECTED] 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
Re: libthr and 1:1 threading.
Terry Lambert wrote: Stijn Hoop wrote: On Mon, Mar 31, 2003 at 10:54:45PM -0500, Jeff Roberson wrote: I have commited libthr. To try this out you'll need to do the following I know very very little about threads, but I'm interested as to what the purpose is of this library. Is there a document available somewhere that describes the relationships between this, KSE, libc_r, pthreads, the Giant-unwinding-make-SMP-work-better project and some of the other threads and SMP related libraries and terminology? Here's a thumbnail sketch, though (forgive me, KSE folks, if I mung it too badly): Good explanations Terry! Even I could understand it :) If this is all reasonably accurate enough for everyone, could it be marked up for a FAQ or Handbook entry? As we move towards a 5-STABLE I think it would be useful to have a document to point to that describes these things. I'm happy to do the markup if you're happy for your words (or a close approximation) to be used. Thanks. Andrew. ___ [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
George Hartzell wrote: 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 Here's what I'd do. Hi everyone! I'm posting from a different email address now I've got FreeBSD back up and running. George's one-man tutorial on how to install Grub was excellent and everything is now working perfectly. Thanks to everyone who replied. Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: NTLDR missing after 5-RELEASE install
My experience with the FBSD boot manager is virtually zero, so I can't address it's workings, but I use GRUB as a booter just because it gets me out of so many jams like yours -- if something isn't where you thought it was you can point GRUB at your disks and let it do the looking for you. The secret is to make a boot floppy with GRUB installed on it. Once you have that there's no machine that's unbootable, and you can reinstall GRUB in seconds if it gets overwritten by Bill Co. For example, IIRC, I just went thru this myself (although it's all so routine now I can't even remember what I do to bail out anymore) when I installed XP on a brand new disk and then installed FBSD afterwards. I got the MBR screwed up just like you, then ran the XP install disk in Repair mode which got XP to boot again but overwrote the FBSD booter. So all I did was boot my trusty GRUB floppy and reinstalled GRUB on the MBR in about 60 seconds and -- done. The next evil news is that I've never really gotten FBSD's incarnation of GRUB to work right for me, so I just install in on the floppy from a linux machine and use that for the FBSD machine. If you have access to GRUB and need instructions I'd be happy to help. Just let me know. Thanks for the tip! I'll give GRUB a try :) Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: NTLDR missing after 5-RELEASE install
George Hartzell wrote: 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. 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 :-/ Thanks anyway! :) Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: NTLDR missing after 5-RELEASE install
Quoting Lucas Holt [EMAIL PROTECTED]: It probably is. You need to put in the win 2k CD and do a repair on your windows install.. unfortunetely this may screw up your freebsd install. On Tuesday, February 25, 2003, at 05:58 AM, Andrew Boothman wrote: Hi! I've just installed 5-RELEASE, and I asked for the FreeBSD Boot Manager to be installed on both my HDDs. When the machine boots I'm given options for : F1 - DOS F5 - Drive 2 Hitting F5 takes me to a second menu, where I can boot FreeBSD no problem. My problem is that Win2k will no longer boot Hitting F1 displays a message that, NTLDR is missing. I've tried all the repair options on the Win2k setup disc to no avail I think. I'm sorry this isn't directly FreeBSD related, but I really hope my Win2k installation isn't hosed. Thanks for replying! I can't understand how the 5.x boot manager has managed to break my windows boot, i've never had any trouble under 3.x or 4.x, both of which played with windows perfectly nicely. I think i've tried all of the various repair options on the Win2k CD, including getting it to do a fresh installation into a different folder (c:\tempwin), but even that failed with the NTLDR missing message! However you no longer get the booteasy (F1 F2) menu anymore, so Windows must have rewritten something. It still doesn't explain why Win2k still won't boot. I'm running out of ideas and I *really* don't want to have to reformat my windows drive! Other than this (fairly major) problem, my 5.0 installation went really well, even ACPI seems to be working perfectly and I even found a KLD to support my on- board sound card! :) I really want to get windows booting again so I can continue to play with 5.0 without worrying... Any help is much appricated! Thanks! Andrew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: NTLDR missing after 5-RELEASE install
Quoting Matt Smith [EMAIL PROTECTED]: What does your Drive Layout look like? Is your W2k partition FAT32? Has it always been the first partition on the drive, or did you move it, using something like partition magic? Is freeBSD in the extended partition? -Matt On Tue, 2003-02-25 at 11:58, Andrew Boothman wrote: Quoting Lucas Holt [EMAIL PROTECTED]: It probably is. You need to put in the win 2k CD and do a repair on your windows install.. unfortunetely this may screw up your freebsd install. On Tuesday, February 25, 2003, at 05:58 AM, Andrew Boothman wrote: Hi! I've just installed 5-RELEASE, and I asked for the FreeBSD Boot Manager to be installed on both my HDDs. When the machine boots I'm given options for : F1 - DOS F5 - Drive 2 Hitting F5 takes me to a second menu, where I can boot FreeBSD no problem. My problem is that Win2k will no longer boot Hitting F1 displays a message that, NTLDR is missing. I've tried all the repair options on the Win2k setup disc to no avail I think. I'm sorry this isn't directly FreeBSD related, but I really hope my Win2k installation isn't hosed. 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 :) Thanks. Andrew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
panic: ffs_blkfree in recent JPSNAP
'ello all! My 5.0-CURRENT-20021215-JPSNAP system is reliably panic-ing and dropping into the debugger a few minutes after booting. I was in the process of trying to boot 5.0-RC2's installation floppies, and the boot failed due to a faulty floppy. So I told the loader to boot from my root partition on my HDD instead. This produced some error messages about filesystems not being properly dismounted (not sure if that is true...), but booted anyway. Now, every boot from the HDD produces the panics. After being up for a few minutes, the machine panics saying (all messages hand-transcribed): dev=ad0s1e, block=6, fs=/tmp panic: ffs_blkfree: freeing free block Debugger(panic) Stopped at Debugger+0x54: xchgl %ebx, in_Debugger() Unfortunately I don't (yet) know the first thing about how to debug something like this, so for the hell of it I typed trace and got the following (I'm missing out the values inside the ()'s as thats a lot of writing - but I'll report back anything that the developers need to know) : Debugger(...) panic(...) ffs_blkfree(...) indir_trunc(...) handle_workitem_freeblocks(...) process_worklist_item(...) softdep_process_worklist(...) sched_sync(...) fork_exit(...) fork_trampoline(...) If anybody needs more information then please let me know, as I said I have it panic-ing reliably. I guess that booting single-user and then fsck-ing might well fix the problem, but I wanted to take the opportunity to report what is one of the very few panics I've had in many years of FreeBSD usage. And I'm planning to install RC2 on this machine anyway. Thanks! Andrew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Reboot failure and dmesg corruption
Hi everyone! I recently installed 5.0-CURRENT-20021215-JPSNAP from current.freebsd.org and two small problems have come to light. Firstly my box (a P2-350 Compaq Deskpro) refuses to reboot. When I issue a 'shutdown -r now' the system gets as far as displaying the system uptime and then seems to stop. The monitor goes into powersaving but the machine never reboots, and I need to hit the power button to get it to reboot. I tried disabling ACPI by adding hint.acpi.0.disabled=1 to /boot/device.hints but it made no difference. Secondly when I first installed -current onto this machine (DP1 I think) I had a strange problem where the system's dmesg becomes corrupted. This problem is still present and seems to be able to appear and dssappear. Here is an exerpt from dmesg where the corruption suddenly appeared : uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0x2020-0x203f irq 11 at device 20.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: bridge, PCI-unknown at device 20.3 (no driver attached) orm0: Option ROMs at ikmem 0xe-0xe7fff,0xc-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0:Keyboard controller (i8042) !t port 0x64,0x60 onisa\^P atkbd08 AT Keyboard blags0x1 irq 1 on adjbdc0 kbd0 at atkbd0 fdc0: Enhanced floppy conTroller (I82077, FE72065 or alone `t port 0x3f7,0x2f0-0x3f4 )rq 6 drq 2 on isa0 fdb0: FIFO enabled, 8 b\^Xtes thR%shmld fd0: 144\^P-K@ 3.% dpive on fdc0 drive\^P Both of these problems have been reported to -current before but never with any resolution. As we near 5.0-REL, I thought I would check again if anyone has any ideas on what might be wrong. Many thanks. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: The great perl rewrite - progress report
Will Andrews wrote: On Thu, Jun 06, 2002 at 05:31:12PM +0100, Mark Murray wrote: /usr/sbin/sysinstall * - fix - * What part of this uses perl?? Perhaps it was just a general comment ;-) Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Logitech iFeel Optical USB Mouse cannot be attached.
Ian Logan wrote: Hello all, I've got an iFeel at home, plugged directly into the machine. Gives the exact same error. At one point last summer I started trying to look into it, and from what I saw in the code and what I remember it looked like some sort of timeout was happening while trying to talk to the mouse. I'll see if I can find my notes on it, or reproduce it. Maybe that will help someone smarter than me figure it out, if not sorry for the me too. Sorry for this second generation me too, but I have an iFeel Mouseman which works completely perfectly here. It plugs directly into an AMD-756 OHCI USB Controller Root Hub. Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: bash in /usr/local/bin?
On Monday 13 August 2001 3:08 am, The Anarcat wrote: [This email contains coarse language due to the absurdity of the thread level we're in. My apologies to those offended. Also, my apologies to the author of the original mail. You have triggered very sensitive areas of my mind. :)] Swearing adds absolutely nothing to your argument, you've devalued your own opinion by giving the impression you're incapable of expressing yourself without resorting to swearing. I personally got sick of it a short way down and gave up reading. -- Andrew Boothman [EMAIL PROTECTED] http://sour.cream.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
