Re: Booting question
On Monday 11 May 2009 03:57:21 Michel Di Croci wrote: Yes it is in. And it's not the sendmail that is slow, it's the detection / kernel step... not the service steps. Please choose verbose boot from the menu and hand-copy the lines right before,right after and during which the hang occurs. You can use scroll-lock and page up/down to find them again after it scrolls up. Disable any X/G/Kdm display manager you might have auto started or press ctrl- alt-f1 to get back to the original console. -- Mel ___ 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: Booting question
On Sun, 10 May 2009, Michel Di Croci wrote: When I boot, it takes about 5 mins before being up and running. Since it's my first FreeBSD, I didn't thought there was an issue, but I think there's one ;) I have a P4 2.8 HT which is too bad computer and I really think the issue is in freeBSD and the Giant Locked and stuff like that. The computer stays in a waiting mode for about 3 minutes or something like that. It's unbearable, however, since I reboot like once in a month, it's not that bad ;) But I'm still wondering why it's so slow. It would help to know what shows on the screen. But my first guess is sendmail trying to get a FQDN and timing out. What happens if you press ctrl-c when it's waiting? Second guess is that you have some external USB device that your BIOS is trying to use for booting. Without knowing what the screen shows, it's hard to say. -Warren Block * Rapid City, South Dakota USA ___ 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
Booting question
Hello! When I boot, it takes about 5 mins before being up and running. Since it's my first FreeBSD, I didn't thought there was an issue, but I think there's one ;) I have a P4 2.8 HT which is too bad computer and I really think the issue is in freeBSD and the Giant Locked and stuff like that. The computer stays in a waiting mode for about 3 minutes or something like that. It's unbearable, however, since I reboot like once in a month, it's not that bad ;) But I'm still wondering why it's so slow. I have compiled my own kernel, removed driver I don't use but I kept all usb drivers. Like I told you, it's really the USB part that seems to be long to load. It's like it's waiting for a stabilization mode that is never coming. Anyone had that kind of issue? I'm running 7.2 and it's been there since the installation with 7.1. Thanks and have a nice day Michel ___ 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: Booting question
On Sun, May 10, 2009 at 8:31 PM, Michel Di Croci michel.dicr...@gmail.com wrote: Hello! When I boot, it takes about 5 mins before being up and running. Since it's my first FreeBSD, I didn't thought there was an issue, but I think there's one ;) I have a P4 2.8 HT which is too bad computer and I really think the issue is in freeBSD and the Giant Locked and stuff like that. The computer stays in a waiting mode for about 3 minutes or something like that. It's unbearable, however, since I reboot like once in a month, it's not that bad ;) But I'm still wondering why it's so slow. I have compiled my own kernel, removed driver I don't use but I kept all usb drivers. Like I told you, it's really the USB part that seems to be long to load. It's like it's waiting for a stabilization mode that is never coming. Anyone had that kind of issue? I'm running 7.2 and it's been there since the installation with 7.1. Did it hang with GENERIC? If not, do a diff on your config and the GENERIC config, and paste it for us. (On a side note, is your machine's `hostname` in /etc/hosts? I've had a problem with sendmail hanging for some time because the hostname was not resolvable. Just a side-thought.) -- Glen Barber ___ 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: Booting question
On Sun, May 10, 2009 at 9:57 PM, Michel Di Croci michel.dicr...@gmail.com wrote: Did it hang with GENERIC? If not, do a diff on your config and the GENERIC config, and paste it for us. If I remember correctly, yes but I don,t remember. Can you tell me if I don't want to lose my actual kernel, how can I make a new kernel and install it not as principal one. This is explained in the handbook and the manual pages. http://www.freebsd.org/doc/en/books/handbook/kernelconfig-trouble.html You want to use 'nextboot' and specify the kernel location. (On a side note, is your machine's `hostname` in /etc/hosts? I've had a problem with sendmail hanging for some time because the hostname was not resolvable. Just a side-thought.) Yes it is in. And it's not the sendmail that is slow, it's the detection / kernel step... not the service steps. If you're using 7.2 (-RELEASE I assume?) and this has been happening since 7.1, it's not something that has changed recently. I don't recall seeing issues like this on this list (or stable@ for that matter). Perhaps it is a hardware problem, but I've never been good at diagnosing hardware issues. -- Glen Barber ___ 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: Booting question
On Sun, May 10, 2009 at 9:52 PM, Glen Barber glen.j.bar...@gmail.comwrote: On Sun, May 10, 2009 at 8:31 PM, Michel Di Croci michel.dicr...@gmail.com wrote: Hello! When I boot, it takes about 5 mins before being up and running. Since it's my first FreeBSD, I didn't thought there was an issue, but I think there's one ;) I have a P4 2.8 HT which is too bad computer and I really think the issue is in freeBSD and the Giant Locked and stuff like that. The computer stays in a waiting mode for about 3 minutes or something like that. It's unbearable, however, since I reboot like once in a month, it's not that bad ;) But I'm still wondering why it's so slow. I have compiled my own kernel, removed driver I don't use but I kept all usb drivers. Like I told you, it's really the USB part that seems to be long to load. It's like it's waiting for a stabilization mode that is never coming. Anyone had that kind of issue? I'm running 7.2 and it's been there since the installation with 7.1. Did it hang with GENERIC? If not, do a diff on your config and the GENERIC config, and paste it for us. If I remember correctly, yes but I don,t remember. Can you tell me if I don't want to lose my actual kernel, how can I make a new kernel and install it not as principal one. (On a side note, is your machine's `hostname` in /etc/hosts? I've had a problem with sendmail hanging for some time because the hostname was not resolvable. Just a side-thought.) Yes it is in. And it's not the sendmail that is slow, it's the detection / kernel step... not the service steps. Michel -- Glen Barber ___ 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
BSD Booting question (with windows)?
Hi. I just installed freebsd on my laptop yesterday. I have a previous version of windows on there (windows XP Home) as well. I was told by a friend that I would be able to boot between BSD and windows easily, however I seem to be having some problems. I am using that bootloader that BSD recommends you use. My problem is that when I reach the boot screen, and try to boot to DOS (windows), it gives me the following error: Windows could not start because the following file is missing or corrupt: Windows root\system32\hal.dll. Please re-install a copy of the above file. And that is about it. I've never formally used BSD before, so I am kind of in the dark on what to do next. I know the logical thing would be to just replace the file, and that is really easy for me to do from DOS, but I am not sure how to go about doing this in BSD. Could you please help me? -- - Andy Scheriff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BSD Booting question (with windows)?
On Monday 04 October 2004 11:03 am, Andy Scheriff wrote: Hi. I just installed freebsd on my laptop yesterday. I have a previous version of windows on there (windows XP Home) as well. I was told by a friend that I would be able to boot between BSD and windows easily, however I seem to be having some problems. I am using that bootloader that BSD recommends you use. My problem is that when I reach the boot screen, and try to boot to DOS (windows), it gives me the following error: Windows could not start because the following file is missing or corrupt: Windows root\system32\hal.dll. Please re-install a copy of the above file. Did you repartition in order to accomplish your dual boot? If so your windows boot.ini may no longer be correctly configured. Try Microsoft Knowledge base article: 330184 And that is about it. I've never formally used BSD before, so I am kind of in the dark on what to do next. I know the logical thing would be to just replace the file, and that is really easy for me to do from DOS, but I am not sure how to go about doing this in BSD. Could you please help me? -- Regards, Eric ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BSD Booting question (with windows)?
More importantly did you defrag the windows installation _before_ doing any repartitioning?? Note that defrag doesnt necessarily move _all_ files down to the low end of the disk. I had to scour the net for other tools to finally get EVERYTHING packed down low on the disk. Then and only then can you safely repartition the disk without destroying some semi-essential chunk on something that windows thinks it needs. mjt On Tue, 2004-10-05 at 02:17, Eric Schuele wrote: On Monday 04 October 2004 11:03 am, Andy Scheriff wrote: Hi. I just installed freebsd on my laptop yesterday. I have a previous version of windows on there (windows XP Home) as well. I was told by a friend that I would be able to boot between BSD and windows easily, however I seem to be having some problems. I am using that bootloader that BSD recommends you use. My problem is that when I reach the boot screen, and try to boot to DOS (windows), it gives me the following error: Windows could not start because the following file is missing or corrupt: Windows root\system32\hal.dll. Please re-install a copy of the above file. Did you repartition in order to accomplish your dual boot? If so your windows boot.ini may no longer be correctly configured. Try Microsoft Knowledge base article: 330184 And that is about it. I've never formally used BSD before, so I am kind of in the dark on what to do next. I know the logical thing would be to just replace the file, and that is really easy for me to do from DOS, but I am not sure how to go about doing this in BSD. Could you please help me? -- Murray Taylor Special Projects Engineer - Bytecraft Systems Entertainment P: +61 3 8710 2555 F: +61 3 8710 2599 D: +61 3 9238 4275 M: +61 417 319 256 E: [EMAIL PROTECTED] or visit us on the web http://www.bytecraftsystems.com http://www.bytecraftentertainment.com --- The information transmitted in this e-mail is for the exclusive use of the intended addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. E-mails may not be secure, may contain computer viruses and may be corrupted in transmission. Please carefully check this e-mail (and any attachment) accordingly. No warranties are given and no liability is accepted for any loss or damage caused by such matters. --- This Email has been scanned for Viruses by MailMarshal. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: booting question
no, it didn't help. it's still trying to boot from da0s1a insted of da0s1e. # The root device and filesystem type can be compiled in; # this provides a fallback option if the root device cannot # be correctly guessed by the bootstrap code, or an override if # the RB_DFLTROOT flag (-r) is specified when booting the kernel. # options ROOTDEVNAME=\ufs:da0s2e\ (I've no idea why, but /boot.config in this case doesn't work) If it's not mounted, how can it be read? Regards, (? ?) Ilia Chipitsine ( ???) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: booting question
10/5/2002 5:14:51 AM, ??? [EMAIL PROTECTED] wrote: no, it didn't help. it's still trying to boot from da0s1a insted of da0s1e. # The root device and filesystem type can be compiled in; # this provides a fallback option if the root device cannot # be correctly guessed by the bootstrap code, or an override if # the RB_DFLTROOT flag (-r) is specified when booting the kernel. # options ROOTDEVNAME=\ufs:da0s2e\ (I've no idea why, but /boot.config in this case doesn't work) If it's not mounted, how can it be read? Regards, (? ?) Ilia Chipitsine ( ???) Just curious - I think the technical level of this discussion is probably way beyond me, but what does /etc/fstab say? Jud To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: booting question
On Fri, Oct 04, 2002 at 08:27:17AM +0600, ??? typed: Dear Sirs, how to force booting from da0s1e, not from da0s1a ?? Read LINT: # # The root device and filesystem type can be compiled in; # this provides a fallback option if the root device cannot # be correctly guessed by the bootstrap code, or an override if # the RB_DFLTROOT flag (-r) is specified when booting the kernel. # options ROOTDEVNAME=\ufs:da0s2e\ (I've no idea why, but /boot.config in this case doesn't work) If it's not mounted, how can it be read? Regards, (? ?) Ilia Chipitsine ( ???) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
booting question
Dear Sirs, how to force booting from da0s1e, not from da0s1a ?? (I've no idea why, but /boot.config in this case doesn't work) Regards, (îÁÉÌÕÞÛÉÅ ÐÏÖÅÌÁÎÉÑ) Ilia Chipitsine (éÌØÑ ûÉÐÉÃÉÎ) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
