Re: system hangs on; Probing devices, please wait (this can take a while)...
No I'm not going to start ripping my computer apart because FreeBSD can't deal with my hard drive. I think the problem is a shortcoming in FreeBSD where it can't deal with drives that have old stale RAID metadata on them. I'm just going to have to wait until they can. Until then no FreeBSD for me. Back to crappy windows. Don't think you have to go back to crappy windows until you've tried NetBSD and/or Linux. NetBSD install is easier than FreeBSD install, I've done both. There are lots of Linux live CDs that you can run without changing anything on the hard drive. You would get a dmesg that you could examine. You can get a lot of information on the many Linux distributions, and BSD too, on http://distrowatch.com/ NetBSD installation CD also gives you a good dmesg that you can examine, and you can go to a /bin/sh shell to view it with less. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
Rich, if you can't get either the installation CD or live-file-system CD to boot (FreeBSD), maybe your computer is allergic to FreeBSD? I've had that problem with both FreeBSD and NetBSD on the older computer (Cx486DX-2 at 66 MHz; 1.2 GB hard drive). One thing that could possibly help is if you could get a custom installation kernel or running kernel, but you'd need a different computer to build it on. Any way to cross-compile a FreeBSD kernel from NetBSD or Linux? Does anybody know? NetBSD guide tells how to make customized installation kernels and media, but I see nothing like that for FreeBSD. You might read the sysinstall man page from FreeBSD web site. Under NOTES This product is currently at the end of its life cycle and will eventu- ally be replaced. Under BUGS, toward the end This utility is a prototype which lasted several years past its expira- tion date and is greatly in need of death. I guess you and I both agree on this last statement. I also have to say that splitting the installation sets into 1392 KB chunks like base.aa, base.ab, and so on, is much less user-friendly and more error-prone than one .tgz or .tbz file for each installation set: base.tgz, etc.tgz, man.tgz and so on. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
I agree, but I might start pulling parts and see if it works then. swap video cards if you can, etc. On Jul 22, 2010, at 3:28 AM, Thomas Mueller wrote: Rich, if you can't get either the installation CD or live-file-system CD to boot (FreeBSD), maybe your computer is allergic to FreeBSD? I've had that problem with both FreeBSD and NetBSD on the older computer (Cx486DX-2 at 66 MHz; 1.2 GB hard drive). One thing that could possibly help is if you could get a custom installation kernel or running kernel, but you'd need a different computer to build it on. Any way to cross-compile a FreeBSD kernel from NetBSD or Linux? Does anybody know? NetBSD guide tells how to make customized installation kernels and media, but I see nothing like that for FreeBSD. You might read the sysinstall man page from FreeBSD web site. Under NOTES This product is currently at the end of its life cycle and will eventu- ally be replaced. Under BUGS, toward the end This utility is a prototype which lasted several years past its expira- tion date and is greatly in need of death. I guess you and I both agree on this last statement. I also have to say that splitting the installation sets into 1392 KB chunks like base.aa, base.ab, and so on, is much less user-friendly and more error-prone than one .tgz or .tbz file for each installation set: base.tgz, etc.tgz, man.tgz and so on. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
No I'm not going to start ripping my computer apart because FreeBSD can't deal with my hard drive. I think the problem is a shortcoming in FreeBSD where it can't deal with drives that have old stale RAID metadata on them. I'm just going to have to wait until they can. Until then no FreeBSD for me. Back to crappy windows. From: Ryan Coleman ryan.cole...@cwis.biz To: User Questions freebsd-questions@freebsd.org Sent: Thu, July 22, 2010 7:19:28 AM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... I agree, but I might start pulling parts and see if it works then. swap video cards if you can, etc. On Jul 22, 2010, at 3:28 AM, Thomas Mueller wrote: Rich, if you can't get either the installation CD or live-file-system CD to boot (FreeBSD), maybe your computer is allergic to FreeBSD? I've had that problem with both FreeBSD and NetBSD on the older computer (Cx486DX-2 at 66 MHz; 1.2 GB hard drive). One thing that could possibly help is if you could get a custom installation kernel or running kernel, but you'd need a different computer to build it on. Any way to cross-compile a FreeBSD kernel from NetBSD or Linux? Does anybody know? NetBSD guide tells how to make customized installation kernels and media, but I see nothing like that for FreeBSD. You might read the sysinstall man page from FreeBSD web site. Under NOTES This product is currently at the end of its life cycle and will eventu- ally be replaced. Under BUGS, toward the end This utility is a prototype which lasted several years past its expira- tion date and is greatly in need of death. I guess you and I both agree on this last statement. I also have to say that splitting the installation sets into 1392 KB chunks like base.aa, base.ab, and so on, is much less user-friendly and more error-prone than one .tgz or .tbz file for each installation set: base.tgz, etc.tgz, man.tgz and so on. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
Then you can suffer through crappy windows or spend $50 on a hard drive... On Jul 22, 2010, at 1:15 PM, Rich wrote: No I'm not going to start ripping my computer apart because FreeBSD can't deal with my hard drive. I think the problem is a shortcoming in FreeBSD where it can't deal with drives that have old stale RAID metadata on them. I'm just going to have to wait until they can. Until then no FreeBSD for me. Back to crappy windows. From: Ryan Coleman ryan.cole...@cwis.biz To: User Questions freebsd-questions@freebsd.org Sent: Thu, July 22, 2010 7:19:28 AM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... I agree, but I might start pulling parts and see if it works then. swap video cards if you can, etc. On Jul 22, 2010, at 3:28 AM, Thomas Mueller wrote: Rich, if you can't get either the installation CD or live-file-system CD to boot (FreeBSD), maybe your computer is allergic to FreeBSD? I've had that problem with both FreeBSD and NetBSD on the older computer (Cx486DX-2 at 66 MHz; 1.2 GB hard drive). One thing that could possibly help is if you could get a custom installation kernel or running kernel, but you'd need a different computer to build it on. Any way to cross-compile a FreeBSD kernel from NetBSD or Linux? Does anybody know? NetBSD guide tells how to make customized installation kernels and media, but I see nothing like that for FreeBSD. You might read the sysinstall man page from FreeBSD web site. Under NOTES This product is currently at the end of its life cycle and will eventu- ally be replaced. Under BUGS, toward the end This utility is a prototype which lasted several years past its expira- tion date and is greatly in need of death. I guess you and I both agree on this last statement. I also have to say that splitting the installation sets into 1392 KB chunks like base.aa, base.ab, and so on, is much less user-friendly and more error-prone than one .tgz or .tbz file for each installation set: base.tgz, etc.tgz, man.tgz and so on. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
Lol, true. From: Ryan Coleman ryan.cole...@cwis.biz To: Rich rl...@pacbell.net Cc: User Questions freebsd-questions@freebsd.org Sent: Thu, July 22, 2010 11:50:58 AM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... Then you can suffer through crappy windows or spend $50 on a hard drive... On Jul 22, 2010, at 1:15 PM, Rich wrote: No I'm not going to start ripping my computer apart because FreeBSD can't deal with my hard drive. I think the problem is a shortcoming in FreeBSD where it can't deal with drives that have old stale RAID metadata on them. I'm just going to have to wait until they can. Until then no FreeBSD for me. Back to crappy windows. From: Ryan Coleman ryan.cole...@cwis.biz To: User Questions freebsd-questions@freebsd.org Sent: Thu, July 22, 2010 7:19:28 AM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... I agree, but I might start pulling parts and see if it works then. swap video cards if you can, etc. On Jul 22, 2010, at 3:28 AM, Thomas Mueller wrote: Rich, if you can't get either the installation CD or live-file-system CD to boot (FreeBSD), maybe your computer is allergic to FreeBSD? I've had that problem with both FreeBSD and NetBSD on the older computer (Cx486DX-2 at 66 MHz; 1.2 GB hard drive). One thing that could possibly help is if you could get a custom installation kernel or running kernel, but you'd need a different computer to build it on. Any way to cross-compile a FreeBSD kernel from NetBSD or Linux? Does anybody know? NetBSD guide tells how to make customized installation kernels and media, but I see nothing like that for FreeBSD. You might read the sysinstall man page from FreeBSD web site. Under NOTES This product is currently at the end of its life cycle and will eventu- ally be replaced. Under BUGS, toward the end This utility is a prototype which lasted several years past its expira- tion date and is greatly in need of death. I guess you and I both agree on this last statement. I also have to say that splitting the installation sets into 1392 KB chunks like base.aa, base.ab, and so on, is much less user-friendly and more error-prone than one .tgz or .tbz file for each installation set: base.tgz, etc.tgz, man.tgz and so on. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On Thu, 22 Jul 2010 11:54:29 -0700 (PDT) Rich rl...@pacbell.net articulated: Lol, true. Two top posters in succession. My lucky day. In any case, the OP should NOT have to suffer the agita of being forced to due either. While the ability do accomplish what the OP desires does not exist ab initio in FreeBSD, it does not preclude its eventual inclusion. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
Any ideas anyone ? I'm stuck. Cannot install FreeBSD on my computer. Every other OS besides FreeBSD boots up and installs. What else can I check? I offered my admittedly cumbersome force-fitting suggestion. Maybe start with a minimal installation, possibly base and etc only, or as little as possible to get something to start with. If this can be booted, then continue with sysinstall from the hard drive with the downloaded FreeBSD sets on CD or an msdos/vfat partition. But then if you can untar the base and etc sets in accordance with the sysinstall scripts, the same could be done with the other installation sets. Possibly, booting a live-file-system FreeBSD CD, you could have the installation CD image on an msdos/vfat partition, and mdconfig and mount that. You could bsdlabel, newfs, and hopefully be able to proceed from there. I wonder if FreeBSD is the only OS with Probing devices, please wait (this can take a while)... Nothing like this occurs in NetBSD or Linux; I've also installed various DOSes (MS-DOS 4.01 and upgrade to 5; DR-DOS 7.03 and FreeDOS; OS/2 1.3 through (Warp) 4) although MS-DOS 4.01 (back in 1990) and OS/2 had their own problems. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On 20 Jul 2010 at 23:46, Bruce Cran wrote: On Tue, 20 Jul 2010 14:59:04 -0700 (PDT) Rich rl...@pacbell.net wrote: Any ideas anyone ? I'm stuck. Cannot install FreeBSD on my computer. Every other OS besides FreeBSD boots up and installs. What else can I check? It looks like it's stopping/spinning at the section where it parses the slices/partitions. I don't know why it would be getting stuck there, though. -- Bruce Cran Hi, I'm not a developer (of OS's at least) but from that DEBUG: list, it almost looks like it thinks it can see just about every hardware device it knows about, existing or not, and is trying to use them all. I know someone mentioned memory tests, but I didn't see what results they came up with, or how much memory you have. I do know however from my own frustrating experience in the past, that often some software will run just fine on bad memory, if the problems don't screw up the code or it's workspace. Where as other software will crash badly, making you think the program is bad. The same is sadly true of hard disk errors too! Did you run a recent memtest86 (self boot CD) and let it do several Full passes (can take many many hours per pass if you have lots of ram! And or a not so fast CPU) ? Just idle musings. Dave B. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On Wed, 21 Jul 2010 11:56:50 +0100 Dave d...@g8kbv.demon.co.uk wrote: Hi, I'm not a developer (of OS's at least) but from that DEBUG: list, it almost looks like it thinks it can see just about every hardware device it knows about, existing or not, and is trying to use them all. The debug output is saying that it can't open the vast majority of the devices it's trying. The device_names array just contains a list of all devices sysinstall knows about: for USB mass storage devices it tries to open da0-da15. I guess it's not been updated for devfs where it should see which device nodes actually exist - or, better, use geom to enumerate the devices. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On Wed, 21 Jul 2010 09:04:53 + Thomas Mueller mueller6...@bellsouth.net wrote: I wonder if FreeBSD is the only OS with Probing devices, please wait (this can take a while)... Nothing like this occurs in NetBSD or Linux; I've also installed various DOSes (MS-DOS 4.01 and upgrade to 5; DR-DOS 7.03 and FreeDOS; OS/2 1.3 through (Warp) 4) although MS-DOS 4.01 (back in 1990) and OS/2 had their own problems. Only FreeBSD has sysinstall - that message gets displayed when sysinstall starts as it checks what devices are available for it to register internally. It's a message from userspace, not the kernel. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
From: Dave d...@g8kbv.demon.co.uk To: Bruce Cran br...@cran.org.uk Cc: freebsd-questions@freebsd.org Sent: Wed, July 21, 2010 3:56:50 AM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... On 20 Jul 2010 at 23:46, Bruce Cran wrote: On Tue, 20 Jul 2010 14:59:04 -0700 (PDT) Rich rl...@pacbell.net wrote: Any ideas anyone ? I'm stuck. Cannot install FreeBSD on my computer. Every other OS besides FreeBSD boots up and installs. What else can I check? It looks like it's stopping/spinning at the section where it parses the slices/partitions. I don't know why it would be getting stuck there, though. Maybe because there might be old RAID metadata from being in one of those stupid fakeraids. I had this problem last year and somehow (can't remember) wiped the drives and got it working. The system worked for about a year then crashed. I thought it a good time to move to 9.0 but now having the same problem again. I didn't put them back in the fakeraid. From what I understand FreeBSD can't be installed on those fakeraids. Maybe it has something to do with that. -- Bruce Cran Hi, I'm not a developer (of OS's at least) but from that DEBUG: list, it almost looks like it thinks it can see just about every hardware device it knows about, existing or not, and is trying to use them all. I know someone mentioned memory tests, but I didn't see what results they came up with, or how much memory you have. I do know however from my own frustrating experience in the past, that often some software will run just fine on bad memory, if the problems don't screw up the code or it's workspace. Where as other software will crash badly, making you think the program is bad. The same is sadly true of hard disk errors too! Did you run a recent memtest86 (self boot CD) and let it do several Full passes (can take many many hours per pass if you have lots of ram! And or a not so fast CPU) ? Just idle musings. Dave B. No I didn't run a mem test since every other OS works perfectly fine. There's something in the FreeBSD code that is hanging. When it hangs it says Probing devices (this may take a while). What does a while mean? A few seconds? few hours? few days? That's a really dumb message IMHO. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On Wed, Jul 21, 2010 at 8:45 AM, Rich rl...@pacbell.net wrote: From: Dave d...@g8kbv.demon.co.uk To: Bruce Cran br...@cran.org.uk Cc: freebsd-questions@freebsd.org Sent: Wed, July 21, 2010 3:56:50 AM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... On 20 Jul 2010 at 23:46, Bruce Cran wrote: On Tue, 20 Jul 2010 14:59:04 -0700 (PDT) Rich rl...@pacbell.net wrote: Any ideas anyone ? I'm stuck. Cannot install FreeBSD on my computer. Every other OS besides FreeBSD boots up and installs. What else can I check? It looks like it's stopping/spinning at the section where it parses the slices/partitions. I don't know why it would be getting stuck there, though. Maybe because there might be old RAID metadata from being in one of those stupid fakeraids. I had this problem last year and somehow (can't remember) wiped the drives and got it working. The system worked for about a year then crashed. I thought it a good time to move to 9.0 but now having the same problem again. I didn't put them back in the fakeraid. From what I understand FreeBSD can't be installed on those fakeraids. Maybe it has something to do with that. -- Bruce Cran Hi, I'm not a developer (of OS's at least) but from that DEBUG: list, it almost looks like it thinks it can see just about every hardware device it knows about, existing or not, and is trying to use them all. I know someone mentioned memory tests, but I didn't see what results they came up with, or how much memory you have. I do know however from my own frustrating experience in the past, that often some software will run just fine on bad memory, if the problems don't screw up the code or it's workspace. Where as other software will crash badly, making you think the program is bad. The same is sadly true of hard disk errors too! Did you run a recent memtest86 (self boot CD) and let it do several Full passes (can take many many hours per pass if you have lots of ram! And or a not so fast CPU) ? Just idle musings. Dave B. No I didn't run a mem test since every other OS works perfectly fine. There's something in the FreeBSD code that is hanging. When it hangs it says Probing devices (this may take a while). What does a while mean? A few seconds? few hours? few days? That's a really dumb message IMHO. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org It's not a memory problem. I've never seen this before. I'll see if I can take a look at the code tonight (I'm at work right now) and figure out why you might be getting this. Clearly doing a minimal install (as some have suggested) isn't going to work because you don't even get to the menu. I know *what* the code is doing - and this is actually something we're getting rid of soon. This was written before devfs was implemented, so it is going through looking for every possible device. I'm just not sure what order it does it in off the top of my head, so I don't know what comes after the scan for SCSI disks, as it's clearly getting through that part just fine. Hmmm. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On Mon, 19 Jul 2010 16:17:06 -0700 Chuck Swiger cswi...@mac.com wrote: There's not quite enough information here to identify your motherboard, but you should make sure there aren't any BIOS upgrades available for it, as those might help resolve this level of issue. Check your BIOS config for the disks carefully, and try adjusting the options you have. In particular, try choosing LBA mode rather than auto or CHS, and try to toggle through ACPI (or SATA mode) vs. IDE (or PATA compatibility) vs. enhanced (often meaning some form of BIOS RAID is enabled) and see whether any of them work. If that doesn't do the trick, you could wander through your BIOS menus, and disable all of the non-essential stuff like parallel serial ports, second NIC, or anything else which is not needed, and see whether that does any good...but that's getting into stuff which is less likely to make a difference. The code that's being run does the following: 1. Finds all network interfaces. 2. Finds all CDROM, floppy, disk and network devices that might be needed for installation. 3. Finds all partitions on the disks to register. I'd guess it's hanging on a syscall somewhere, but there really isn't much debugging output in usr.sbin/sysinstall/devices.c to know where, unless the kernel has printed some errors to the debug console. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On Mon, Jul 19, 2010 at 11:09 PM, Bruce Cran br...@cran.org.uk wrote: On Mon, 19 Jul 2010 16:17:06 -0700 Chuck Swiger cswi...@mac.com wrote: There's not quite enough information here to identify your motherboard, but you should make sure there aren't any BIOS upgrades available for it, as those might help resolve this level of issue. Check your BIOS config for the disks carefully, and try adjusting the options you have. In particular, try choosing LBA mode rather than auto or CHS, and try to toggle through ACPI (or SATA mode) vs. IDE (or PATA compatibility) vs. enhanced (often meaning some form of BIOS RAID is enabled) and see whether any of them work. If that doesn't do the trick, you could wander through your BIOS menus, and disable all of the non-essential stuff like parallel serial ports, second NIC, or anything else which is not needed, and see whether that does any good...but that's getting into stuff which is less likely to make a difference. The code that's being run does the following: 1. Finds all network interfaces. 2. Finds all CDROM, floppy, disk and network devices that might be needed for installation. 3. Finds all partitions on the disks to register. I'd guess it's hanging on a syscall somewhere, but there really isn't much debugging output in usr.sbin/sysinstall/devices.c to know where, unless the kernel has printed some errors to the debug console. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org This is why I suspected #3 - maybe querying the disk and hanging because of bad disk? Hard to say without debug logs. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
I had this problem trying to install FreeBSD on my old computer: Cx486DX2 CPU at 66 MHz; 20 MB RAM; 1.2 GB IDE hard drive; 2x Texel, now Plextor, CD-ROM on Trantor T130B SCSI (NCR5380 chip; no support in FreeBSD = 3.0); Iomega Zip 250 on same SCSI card. That was in the days of FreeBSD 4.x. No such problem on my newer computer with FreeBSD 7.x and now 8.0. I wondered if this part had been revamped with FreeBSD 5.x. If you could boot a FreeBSD live file system, for which downloadable iso images are now available, you might be able to look at the sysinstall scripts, and after partitioning/disklabeling (bsdlabel), you might be able to newfs and make mount points, and untar the pieces (base.aa, base.ab, etc) onto the desired FreeBSD target slice. I've wondered why FreeBSD installation sets (base, etc, games, comp, man and others) are broken into pieces of 1392 KB each as opposed to each installation set in a single .tgz or .tbz (base.tgz, etc.tgz, comp.tgz, and others: that's how NetBSD does it). NetBSD installation CD also offers a utility shell (sh). With floppy disks and floppy drives showing their age, I wouldn't be able to get enough good floppy disks together to install FreeBSD from floppies, and I believe others would have the same problem. I never actually did this, so I can't be sure if I'd succeed: decidedly not user-friendly but might be interesting to try in a pinch. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
Ok I booted on the 8.0 live CD and pressed Alt-F2 when it gets hung. In verbose mode it says this: DEBUG: ioctl(3, TIOCCONC, NULL) = 0 (success) DEBUG: MADT: Found CPUAPIC ID 1 enabled DEBUG: MADT: Found CPUAPIC ID 2 enabled DEBUG: MADT: Found CPUAPIC ID 3 enabled DEBUG: MADT: Found CPUAPIC ID 4 enabled DEBUG: Notify: Probing devices, please wait (this can take a while)... DEBUG: Found a network device named re0 DEBUG: Found a network device named re1 DEBUG: Found a network device named fwe0 DEBUG: Found a network device named fwip0 DEBUG: deviceTry: attempting to open /dev/cd0 DEBUG: deviceTry: open of /dev/cd0 failed. DEBUG: deviceTry: attempting to open /dev/cd1 DEBUG: deviceTry: open of /dev/cd1 failed. DEBUG: deviceTry: attempting to open /dev/cd2 DEBUG: deviceTry: open of /dev/cd2 failed. DEBUG: deviceTry: attempting to open /dev/cd3 DEBUG: deviceTry: open of /dev/cd3 failed. DEBUG: deviceTry: attempting to open /dev/mcd0 DEBUG: deviceTry: open of /dev/mcd0 failed. DEBUG: deviceTry: attempting to open /dev/mcd1 DEBUG: deviceTry: open of /dev/mcd1 failed. DEBUG: deviceTry: attempting to open /dev/mcd2 DEBUG: deviceTry: open of /dev/mcd2 failed. DEBUG: deviceTry: attempting to open /dev/mcd3 DEBUG: deviceTry: open of /dev/mcd3 failed. DEBUG: deviceTry: attempting to open /dev/scd0 DEBUG: deviceTry: open of /dev/scd0 failed. DEBUG: deviceTry: attempting to open /dev/scd1 DEBUG: deviceTry: open of /dev/scd1 failed. DEBUG: deviceTry: attempting to open /dev/scd2 DEBUG: deviceTry: open of /dev/scd2 failed. DEBUG: deviceTry: attempting to open /dev/scd3 DEBUG: deviceTry: open of /dev/scd3 failed. DEBUG: deviceTry: attempting to open /dev/acd0 DEBUG: deviceTry: open of /dev/acd0 succeeded on first try. DEBUG: deviceTry: attempting to open /dev/acd1 DEBUG: deviceTry: open of /dev/acd1 failed. DEBUG: deviceTry: attempting to open /dev/acd2 DEBUG: deviceTry: open of /dev/acd2 failed. DEBUG: deviceTry: attempting to open /dev/acd3 DEBUG: deviceTry: open of /dev/acd3 failed. DEBUG: deviceTry: attempting to open /dev/fd0 DEBUG: deviceTry: open of /dev/fd0 failed. DEBUG: deviceTry: attempting to open /dev/fd1 DEBUG: deviceTry: open of /dev/fd1 failed. DEBUG: deviceTry: attempting to open /dev/fd2 DEBUG: deviceTry: open of /dev/fd2 failed. DEBUG: deviceTry: attempting to open /dev/fd3 DEBUG: deviceTry: open of /dev/fd3 failed. DEBUG: deviceTry: attempting to open /dev/scd0 DEBUG: deviceTry: open of /dev/scd0 failed. DEBUG: deviceTry: attempting to open /dev/cuad0 DEBUG: deviceTry: open of /dev/cuacd0 failed. DEBUG: deviceTry: attempting to open /dev/cuad1 DEBUG: deviceTry: open of /dev/cuacd1 failed. DEBUG: deviceTry: attempting to open /dev/cuad2 DEBUG: deviceTry: open of /dev/cuacd2 failed. DEBUG: deviceTry: attempting to open /dev/cuad3 DEBUG: deviceTry: open of /dev/cuacd3 failed. DEBUG: deviceTry: attempting to open /dev/cuad4 DEBUG: deviceTry: open of /dev/cuacd4 failed. DEBUG: deviceTry: attempting to open /dev/cuad5 DEBUG: deviceTry: open of /dev/cuacd5 failed. DEBUG: deviceTry: attempting to open /dev/cuad6 DEBUG: deviceTry: open of /dev/cuacd6 failed. DEBUG: deviceTry: attempting to open /dev/cuad7 DEBUG: deviceTry: open of /dev/cuacd7 failed. DEBUG: deviceTry: attempting to open /dev/cuad8 DEBUG: deviceTry: open of /dev/cuacd8 failed. DEBUG: deviceTry: attempting to open /dev/cuad9 DEBUG: deviceTry: open of /dev/cuacd9 failed. DEBUG: deviceTry: attempting to open /dev/cuad10 DEBUG: deviceTry: open of /dev/cuacd10 failed. DEBUG: deviceTry: attempting to open /dev/cuad11 DEBUG: deviceTry: open of /dev/cuacd11 failed. DEBUG: deviceTry: attempting to open /dev/cuad12 DEBUG: deviceTry: open of /dev/cuacd12 failed. DEBUG: deviceTry: attempting to open /dev/cuad13 DEBUG: deviceTry: open of /dev/cuacd13 failed. DEBUG: deviceTry: attempting to open /dev/cuad14 DEBUG: deviceTry: open of /dev/cuacd14 failed. DEBUG: deviceTry: attempting to open /dev/cuad15 DEBUG: deviceTry: open of /dev/cuacd15 failed. DEBUG: deviceTry: attempting to open /dev/da0 DEBUG: deviceTry: open of /dev/da0 failed. DEBUG: deviceTry: attempting to open /dev/da1 DEBUG: deviceTry: open of /dev/da1 failed. DEBUG: deviceTry: attempting to open /dev/da2 DEBUG: deviceTry: open of /dev/da2 failed. DEBUG: deviceTry: attempting to open /dev/da3 DEBUG: deviceTry: open of /dev/da3 failed. DEBUG: deviceTry: attempting to open /dev/da4 DEBUG: deviceTry: open of /dev/da4 failed. DEBUG: deviceTry: attempting to open /dev/da5 DEBUG: deviceTry: open of /dev/da5 failed. DEBUG: deviceTry: attempting to open /dev/da6 DEBUG: deviceTry: open of /dev/da6 failed. DEBUG: deviceTry: attempting to open /dev/da7 DEBUG: deviceTry: open of /dev/da7 failed. DEBUG: deviceTry: attempting to open /dev/da8 DEBUG: deviceTry: open of /dev/da8 failed. DEBUG: deviceTry: attempting to open /dev/da9 DEBUG: deviceTry: open of /dev/da9 failed. DEBUG: deviceTry: attempting to open /dev/da10 DEBUG: deviceTry: open of /dev/da10 failed. DEBUG: deviceTry: attempting to open /dev/da11
Re: system hangs on; Probing devices, please wait (this can take a while)...
Disks are not bad. Works with other OSes. Problem is with FreeBSD. I've tried versions 4.6, 7.2, 8.0 and 9.0. Only FreeBSD 4.6 boots without hanging. I've not tried 5 or 6 but I guess I could if it would help to narrow down what the changes were in those versions. Something obviously changed along the way to cause it to hang. From: Randi Harper ra...@freebsd.org To: Bruce Cran br...@cran.org.uk Cc: Chuck Swiger cswi...@mac.com; FreeBSD - freebsd-questions@freebsd.org; Rich rl...@pacbell.net Sent: Mon, July 19, 2010 11:19:06 PM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... On Mon, Jul 19, 2010 at 11:09 PM, Bruce Cran br...@cran.org.uk wrote: On Mon, 19 Jul 2010 16:17:06 -0700 Chuck Swiger cswi...@mac.com wrote: There's not quite enough information here to identify your motherboard, but you should make sure there aren't any BIOS upgrades available for it, as those might help resolve this level of issue. Check your BIOS config for the disks carefully, and try adjusting the options you have. In particular, try choosing LBA mode rather than auto or CHS, and try to toggle through ACPI (or SATA mode) vs. IDE (or PATA compatibility) vs. enhanced (often meaning some form of BIOS RAID is enabled) and see whether any of them work. If that doesn't do the trick, you could wander through your BIOS menus, and disable all of the non-essential stuff like parallel serial ports, second NIC, or anything else which is not needed, and see whether that does any good...but that's getting into stuff which is less likely to make a difference. The code that's being run does the following: 1. Finds all network interfaces. 2. Finds all CDROM, floppy, disk and network devices that might be needed for installation. 3. Finds all partitions on the disks to register. I'd guess it's hanging on a syscall somewhere, but there really isn't much debugging output in usr.sbin/sysinstall/devices.c to know where, unless the kernel has printed some errors to the debug console. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org This is why I suspected #3 - maybe querying the disk and hanging because of bad disk? Hard to say without debug logs. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On 07/20/2010 02:42 AM, Thomas Mueller wrote: I've wondered why FreeBSD installation sets (base, etc, games, comp, man and others) are broken into pieces of 1392 KB each as opposed to each installation set in a single .tgz or .tbz (base.tgz, etc.tgz, comp.tgz, and others: that's how NetBSD does it). NetBSD installation CD also offers a utility shell (sh). With floppy disks and floppy drives showing their age, I wouldn't be able to get enough good floppy disks together to install FreeBSD from floppies... If I were to hazard a guess, I'd say it's because not everyone who uses FreeBSD is on a broadband connection, and a 56MB download (just for base.??) is a bit too large to fetch in a single session, if for some reason you are unable to resume the transfer after interruption. But the floppy thing might be a good reason too. Especially since all you really need is one working floppy disk and two floppy-drive-equipped computers to do it. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
Any ideas anyone ? I'm stuck. Cannot install FreeBSD on my computer. Every other OS besides FreeBSD boots up and installs. What else can I check? From: Thomas Mueller mueller6...@bellsouth.net To: freebsd-questions@freebsd.org Sent: Tue, July 20, 2010 12:42:09 AM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... I had this problem trying to install FreeBSD on my old computer: Cx486DX2 CPU at 66 MHz; 20 MB RAM; 1.2 GB IDE hard drive; 2x Texel, now Plextor, CD-ROM on Trantor T130B SCSI (NCR5380 chip; no support in FreeBSD = 3.0); Iomega Zip 250 on same SCSI card. That was in the days of FreeBSD 4.x. No such problem on my newer computer with FreeBSD 7.x and now 8.0. I wondered if this part had been revamped with FreeBSD 5.x. If you could boot a FreeBSD live file system, for which downloadable iso images are now available, you might be able to look at the sysinstall scripts, and after partitioning/disklabeling (bsdlabel), you might be able to newfs and make mount points, and untar the pieces (base.aa, base.ab, etc) onto the desired FreeBSD target slice. I've wondered why FreeBSD installation sets (base, etc, games, comp, man and others) are broken into pieces of 1392 KB each as opposed to each installation set in a single .tgz or .tbz (base.tgz, etc.tgz, comp.tgz, and others: that's how NetBSD does it). NetBSD installation CD also offers a utility shell (sh). With floppy disks and floppy drives showing their age, I wouldn't be able to get enough good floppy disks together to install FreeBSD from floppies, and I believe others would have the same problem. I never actually did this, so I can't be sure if I'd succeed: decidedly not user-friendly but might be interesting to try in a pinch. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On Tue, 20 Jul 2010 14:59:04 -0700 (PDT) Rich rl...@pacbell.net wrote: Any ideas anyone ? I'm stuck. Cannot install FreeBSD on my computer. Every other OS besides FreeBSD boots up and installs. What else can I check? It looks like it's stopping/spinning at the section where it parses the slices/partitions. I don't know why it would be getting stuck there, though. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
Yes I have, that's not it. It's very frustrating because every CD I can find boots up except the FreeBSD CD. If it's not a bad drive nobody seems to know what else it could be. It's deeper than that. Something in the FreeBSD code. Isn't there a developer somewhere that can tell me what his code is doing? From: Andrew Gould andrewlylego...@gmail.com To: Rich rl...@pacbell.net Sent: Tue, July 20, 2010 3:52:21 PM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... On Tue, Jul 20, 2010 at 4:59 PM, Rich rl...@pacbell.net wrote: Any ideas anyone ? I'm stuck. Cannot install FreeBSD on my computer. Every other OS besides FreeBSD boots up and installs. What else can I check? Have you tried booting up with ACPI disabled? Best of luck, Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On Mon, 19 Jul 2010 13:16:46 -0700 (PDT) Rich rl...@pacbell.net wrote: Probing devices, please wait (this can take a while)... I've waited almost an hour. how long is it supposed to take? It would be nice if there were a status bar or spinning wheel or something to let you know if it's doing anything or hung. What can I do to get this to install. It should take less than a second to complete. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
Ok well at least that's good to know. So I disconnected my hard drives and now it boots up further on the CD only but obviously I can't install it with no hard drives. Why does it hang on my drives and what can I do about it? They are just regular Seagate SATA drives. I have windows 7 installed on the first partition and trying to dual-boot FreeBSD on a second partition (well actually the third since win 7 needs two). AMD Phenom 9500 Quad-Core 2.20 GHz 2G RAM Drives: Seagate ST31000333AS From: Bruce Cran br...@cran.org.uk To: Rich rl...@pacbell.net Cc: freebsd-questions@freebsd.org Sent: Mon, July 19, 2010 3:05:32 PM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... On Mon, 19 Jul 2010 13:16:46 -0700 (PDT) Rich rl...@pacbell.net wrote: Probing devices, please wait (this can take a while)... I've waited almost an hour. how long is it supposed to take? It would be nice if there were a status bar or spinning wheel or something to let you know if it's doing anything or hung. What can I do to get this to install. It should take less than a second to complete. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On Mon, 19 Jul 2010 15:38:20 -0700 (PDT), Rich rl...@pacbell.net wrote: Ok well at least that's good to know. So I disconnected my hard drives and now it boots up further on the CD only but obviously I can't install it with no hard drives. Why does it hang on my drives and what can I do about it? They are just regular Seagate SATA drives. I would suggest to boot with the live system CD, e. g. of 8.0-RELEASE. It should not launch sysinstall automatically (you can even boot the CD into SUM), so you end up with a regular shell. First, check all the kernel's output for things that look... strange... and maybe you even decide to install the system without sysinstall (if THAT is what's causing all the trouble). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On Tue, 20 Jul 2010 00:59:58 +0200 Polytropon free...@edvax.de wrote: I would suggest to boot with the live system CD, e. g. of 8.0-RELEASE. It should not launch sysinstall automatically (you can even boot the CD into SUM), so you end up with a regular shell. First, check all the kernel's output for things that look... strange... and maybe you even decide to install the system without sysinstall (if THAT is what's causing all the trouble). Unfortunately the LiveFS CD does run sysinstall by default - you need to go to the Fixit menu to get the shell. I'd suggest trying to boot with debug output enabled and seeing if that produces any clues - I suspect not, but it's worth a go. To do that, press 6 when you see the boot menu to get command prompt and enter boot -v. You should see any debug output on the 2nd console (press F2 when sysinstall hangs). -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
Hi-- On Jul 19, 2010, at 3:38 PM, Rich wrote: Ok well at least that's good to know. So I disconnected my hard drives and now it boots up further on the CD only but obviously I can't install it with no hard drives. Why does it hang on my drives and what can I do about it? They are just regular Seagate SATA drives. I have windows 7 installed on the first partition and trying to dual-boot FreeBSD on a second partition (well actually the third since win 7 needs two). AMD Phenom 9500 Quad-Core 2.20 GHz 2G RAM There's not quite enough information here to identify your motherboard, but you should make sure there aren't any BIOS upgrades available for it, as those might help resolve this level of issue. Check your BIOS config for the disks carefully, and try adjusting the options you have. In particular, try choosing LBA mode rather than auto or CHS, and try to toggle through ACPI (or SATA mode) vs. IDE (or PATA compatibility) vs. enhanced (often meaning some form of BIOS RAID is enabled) and see whether any of them work. If that doesn't do the trick, you could wander through your BIOS menus, and disable all of the non-essential stuff like parallel serial ports, second NIC, or anything else which is not needed, and see whether that does any good...but that's getting into stuff which is less likely to make a difference. Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On Mon, Jul 19, 2010 at 1:16 PM, Rich rl...@pacbell.net wrote: I'm trying to boot on the 9.0 Current or 8.0 Release CD to install and it just hangs on; Probing devices, please wait (this can take a while)... I've waited almost an hour. how long is it supposed to take? It would be nice if there were a status bar or spinning wheel or something to let you know if it's doing anything or hung. What can I do to get this to install. AMD Phenom 9500 Quad-Core 2.20 GHz 2G RAM Drive: Seagate ST31000333AS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org This is probably just grasping at straws, but any chance your hard drive is failing? -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On Tue, 20 Jul 2010 00:16:27 +0100, Bruce Cran br...@cran.org.uk wrote: On Tue, 20 Jul 2010 00:59:58 +0200 Polytropon free...@edvax.de wrote: I would suggest to boot with the live system CD, e. g. of 8.0-RELEASE. It should not launch sysinstall automatically (you can even boot the CD into SUM), so you end up with a regular shell. First, check all the kernel's output for things that look... strange... and maybe you even decide to install the system without sysinstall (if THAT is what's causing all the trouble). Unfortunately the LiveFS CD does run sysinstall by default - you need to go to the Fixit menu to get the shell. Yes - that's what I intended to suggest. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
I tried this but pressing F2 doesn't do anything. From: Bruce Cran br...@cran.org.uk To: Polytropon free...@edvax.de Cc: freebsd-questions@freebsd.org; Rich rl...@pacbell.net Sent: Mon, July 19, 2010 4:16:27 PM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... On Tue, 20 Jul 2010 00:59:58 +0200 Polytropon free...@edvax.de wrote: I would suggest to boot with the live system CD, e. g. of 8.0-RELEASE. It should not launch sysinstall automatically (you can even boot the CD into SUM), so you end up with a regular shell. First, check all the kernel's output for things that look... strange... and maybe you even decide to install the system without sysinstall (if THAT is what's causing all the trouble). Unfortunately the LiveFS CD does run sysinstall by default - you need to go to the Fixit menu to get the shell. I'd suggest trying to boot with debug output enabled and seeing if that produces any clues - I suspect not, but it's worth a go. To do that, press 6 when you see the boot menu to get command prompt and enter boot -v. You should see any debug output on the 2nd console (press F2 when sysinstall hangs). -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
Drive is perfectly fine. Windows runs perfect on first partition. BTW both drives are doing it, I doubt both drives would go bad at the same time. Windows and Linux workfine. Only FreeBSD has trouble. From: Garrett Cooper gcoo...@freebsd.org To: Randi Harper ra...@freebsd.org Cc: Rich rl...@pacbell.net; freebsd-questions@freebsd.org; freebsd-sysinst...@freebsd.org Sent: Mon, July 19, 2010 5:53:21 PM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... On Mon, Jul 19, 2010 at 4:32 PM, Randi Harper ra...@freebsd.org wrote: On Mon, Jul 19, 2010 at 1:16 PM, Rich rl...@pacbell.net wrote: I'm trying to boot on the 9.0 Current or 8.0 Release CD to install and it just hangs on; Probing devices, please wait (this can take a while)... I've waited almost an hour. how long is it supposed to take? It would be nice if there were a status bar or spinning wheel or something to let you know if it's doing anything or hung. What can I do to get this to install. AMD Phenom 9500 Quad-Core 2.20 GHz 2G RAM Drive: Seagate ST31000333AS This is probably just grasping at straws, but any chance your hard drive is failing? Time to try checking the SMART data on the drive? Cheers, -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
Motherbd is Foxconn Digitalife A79A-S. BIOS settings don't make any difference. From: Chuck Swiger cswi...@mac.com To: Rich rl...@pacbell.net Cc: FreeBSD - freebsd-questions@freebsd.org Sent: Mon, July 19, 2010 4:17:06 PM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... Hi-- On Jul 19, 2010, at 3:38 PM, Rich wrote: Ok well at least that's good to know. So I disconnected my hard drives and now it boots up further on the CD only but obviously I can't install it with no hard drives. Why does it hang on my drives and what can I do about it? They are just regular Seagate SATA drives. I have windows 7 installed on the first partition and trying to dual-boot FreeBSD on a second partition (well actually the third since win 7 needs two). AMD Phenom 9500 Quad-Core 2.20 GHz 2G RAM There's not quite enough information here to identify your motherboard, but you should make sure there aren't any BIOS upgrades available for it, as those might help resolve this level of issue. Check your BIOS config for the disks carefully, and try adjusting the options you have. In particular, try choosing LBA mode rather than auto or CHS, and try to toggle through ACPI (or SATA mode) vs. IDE (or PATA compatibility) vs. enhanced (often meaning some form of BIOS RAID is enabled) and see whether any of them work. If that doesn't do the trick, you could wander through your BIOS menus, and disable all of the non-essential stuff like parallel serial ports, second NIC, or anything else which is not needed, and see whether that does any good...but that's getting into stuff which is less likely to make a difference. Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
I couldn't find a live CD fro 8.0 Release. All I could find was at this site; http://livecd.sourceforge.net/download.php It's 4.6, is that useful? Anyway, it booted up to the login prompt without hanging. What does that tell us? Is there anything I can check with this disk or is there somewhere I can get the 8.0 live CD? From: Polytropon free...@edvax.de To: Bruce Cran br...@cran.org.uk Cc: freebsd-questions@freebsd.org; Rich rl...@pacbell.net Sent: Mon, July 19, 2010 4:34:18 PM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... On Tue, 20 Jul 2010 00:16:27 +0100, Bruce Cran br...@cran.org.uk wrote: On Tue, 20 Jul 2010 00:59:58 +0200 Polytropon free...@edvax.de wrote: I would suggest to boot with the live system CD, e. g. of 8.0-RELEASE. It should not launch sysinstall automatically (you can even boot the CD into SUM), so you end up with a regular shell. First, check all the kernel's output for things that look... strange... and maybe you even decide to install the system without sysinstall (if THAT is what's causing all the trouble). Unfortunately the LiveFS CD does run sysinstall by default - you need to go to the Fixit menu to get the shell. Yes - that's what I intended to suggest. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On Mon, Jul 19, 2010 at 4:32 PM, Randi Harper ra...@freebsd.org wrote: On Mon, Jul 19, 2010 at 1:16 PM, Rich rl...@pacbell.net wrote: I'm trying to boot on the 9.0 Current or 8.0 Release CD to install and it just hangs on; Probing devices, please wait (this can take a while)... I've waited almost an hour. how long is it supposed to take? It would be nice if there were a status bar or spinning wheel or something to let you know if it's doing anything or hung. What can I do to get this to install. AMD Phenom 9500 Quad-Core 2.20 GHz 2G RAM Drive: Seagate ST31000333AS This is probably just grasping at straws, but any chance your hard drive is failing? Time to try checking the SMART data on the drive? Cheers, -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
Ok I booted on that disc and it hangs at the same place. not sure what to do next. What is the fixit menu? From: Ryan Coleman ryan.cole...@cwis.biz To: Rich rl...@pacbell.net Sent: Mon, July 19, 2010 6:23:45 PM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... Rich, Here they are: 8.0 i386: ftp://ftp11.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/8.0/8.0-RELEASE-i386-livefs.iso 8.0 AMD64: ftp://ftp11.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/8.0/8.0-RELEASE-amd64-livefs.iso Each is 640MB On Jul 19, 2010, at 8:11 PM, Rich wrote: I couldn't find a live CD fro 8.0 Release. All I could find was at this site; http://livecd.sourceforge.net/download.php It's 4.6, is that useful? Anyway, it booted up to the login prompt without hanging. What does that tell us? Is there anything I can check with this disk or is there somewhere I can get the 8.0 live CD? From: Polytropon free...@edvax.de To: Bruce Cran br...@cran.org.uk Cc: freebsd-questions@freebsd.org; Rich rl...@pacbell.net Sent: Mon, July 19, 2010 4:34:18 PM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... On Tue, 20 Jul 2010 00:16:27 +0100, Bruce Cran br...@cran.org.uk wrote: On Tue, 20 Jul 2010 00:59:58 +0200 Polytropon free...@edvax.de wrote: I would suggest to boot with the live system CD, e. g. of 8.0-RELEASE. It should not launch sysinstall automatically (you can even boot the CD into SUM), so you end up with a regular shell. First, check all the kernel's output for things that look... strange... and maybe you even decide to install the system without sysinstall (if THAT is what's causing all the trouble). Unfortunately the LiveFS CD does run sysinstall by default - you need to go to the Fixit menu to get the shell. Yes - that's what I intended to suggest. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On Mon, 19 Jul 2010 17:53:30 -0700 (PDT) Rich rl...@pacbell.net wrote: I tried this but pressing F2 doesn't do anything. Sorry - I meant Alt-F2 to switch VTYs. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
