AW: FreeBSD 2.2.9 / Installation problem
Thank you very much for your ideas. I switched to 4.11 after realizing that it would work as well. Besides, it would be much easier to install packages, as they are available on CD - for 2.2.9, as far as I saw it, I have to download them. This would have to happen on the Compaq. However, the HP-disk and the LAN-card which I need for internet access would use the same PCMCIA-slot. -Ursprüngliche Nachricht- Von: Josh Paetzel [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 16. März 2007 00:05 An: freebsd-questions@freebsd.org Cc: Kris Kennaway; Nino Ivanov Betreff: Re: FreeBSD 2.2.9 / Installation problem On Thursday 15 March 2007, Kris Kennaway wrote: On Thu, Mar 15, 2007 at 08:43:32PM +0100, Nino Ivanov wrote: Dear Chistian, Dear Kris, I also think the RAM will not be the issue, as it is a text-only install, and indeed, I am not planning to get fancy. I completely don't need X. Midnight Commander is perfectly fine as a working environment. 4.11 seemed OK. But I am having a different problem right now, which I am still researching: It does not recognize the device from where to mount root correctly. I mean the following: When I put FreeBSD into the Compaq for installation, the harddrive is ad4 or ad8. But in the system where I want to run it, the HP Omnibook, it is ad0. Now, when I start it back in the HP Omnibook, it says that swap is not configured correctly on ad8s-something. Which is true, it should look for it on ad0... I have only once been able till now to mount root. (And this is my basis for assuming that even 4.11 CAN potentially run.) I said as command ufs:/dev/ad0 when it asked me where to mount root from. This worked, however, e.g. ufs:/dev/ad0s1 did not work. I am thinking that I might have made a mistake, and should have said ad0s1a. Yet, the principal new problem persists: FreeBSD does not realize that it should now look at ad0 instead of ad4 or ad8. (However, in the booting process, it correctly sees ad0 as having 325 MB etc.) Is there a way to solve this? Probably the /etc/fstab is wrong and refers to the ad4 or ad8 devices. The root should indeed typically be ufs:/dev/ad0s1a. Kris I'm a tad confused, as I thought we were talking about FBSD 2.x, which would've called your drive wd0, not ad0. But Kris is correct in that your fstab is wrong...your /boot/loader.conf probably has the wrong root device as well. -- Thanks, Josh Paetzel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
AW: FreeBSD 2.2.9 / Installation problem
I tried to send to freebsd-questions the following twice, and twice failed!: Dear Sir or Madam, I tried reaching ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/ from my Windows XP machine, using Firefox 2.0.0.2, and it requires me to input a username and a password. The same happens with IE7. I would like to download old ISO images. Is this a bug, or is it some new regular behaviour, and in any case, is there a way to download these images? NetBSD archives work well, so it is not a problem in my machine I think. Regards, Nino Ivanov -Ursprüngliche Nachricht- Von: Josh Paetzel [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 16. März 2007 00:05 An: freebsd-questions@freebsd.org Cc: Kris Kennaway; Nino Ivanov Betreff: Re: FreeBSD 2.2.9 / Installation problem On Thursday 15 March 2007, Kris Kennaway wrote: On Thu, Mar 15, 2007 at 08:43:32PM +0100, Nino Ivanov wrote: Dear Chistian, Dear Kris, I also think the RAM will not be the issue, as it is a text-only install, and indeed, I am not planning to get fancy. I completely don't need X. Midnight Commander is perfectly fine as a working environment. 4.11 seemed OK. But I am having a different problem right now, which I am still researching: It does not recognize the device from where to mount root correctly. I mean the following: When I put FreeBSD into the Compaq for installation, the harddrive is ad4 or ad8. But in the system where I want to run it, the HP Omnibook, it is ad0. Now, when I start it back in the HP Omnibook, it says that swap is not configured correctly on ad8s-something. Which is true, it should look for it on ad0... I have only once been able till now to mount root. (And this is my basis for assuming that even 4.11 CAN potentially run.) I said as command ufs:/dev/ad0 when it asked me where to mount root from. This worked, however, e.g. ufs:/dev/ad0s1 did not work. I am thinking that I might have made a mistake, and should have said ad0s1a. Yet, the principal new problem persists: FreeBSD does not realize that it should now look at ad0 instead of ad4 or ad8. (However, in the booting process, it correctly sees ad0 as having 325 MB etc.) Is there a way to solve this? Probably the /etc/fstab is wrong and refers to the ad4 or ad8 devices. The root should indeed typically be ufs:/dev/ad0s1a. Kris I'm a tad confused, as I thought we were talking about FBSD 2.x, which would've called your drive wd0, not ad0. But Kris is correct in that your fstab is wrong...your /boot/loader.conf probably has the wrong root device as well. -- Thanks, Josh Paetzel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
AW: FreeBSD 2.2.9 / Installation problem
Dear Chistian, Dear Kris, I also think the RAM will not be the issue, as it is a text-only install, and indeed, I am not planning to get fancy. I completely don't need X. Midnight Commander is perfectly fine as a working environment. 4.11 seemed OK. But I am having a different problem right now, which I am still researching: It does not recognize the device from where to mount root correctly. I mean the following: When I put FreeBSD into the Compaq for installation, the harddrive is ad4 or ad8. But in the system where I want to run it, the HP Omnibook, it is ad0. Now, when I start it back in the HP Omnibook, it says that swap is not configured correctly on ad8s-something. Which is true, it should look for it on ad0... I have only once been able till now to mount root. (And this is my basis for assuming that even 4.11 CAN potentially run.) I said as command ufs:/dev/ad0 when it asked me where to mount root from. This worked, however, e.g. ufs:/dev/ad0s1 did not work. I am thinking that I might have made a mistake, and should have said ad0s1a. Yet, the principal new problem persists: FreeBSD does not realize that it should now look at ad0 instead of ad4 or ad8. (However, in the booting process, it correctly sees ad0 as having 325 MB etc.) Is there a way to solve this? If this really works I think I'll write a step-by-step guide... I really appreciate your help in this matter - thank you a lot! -Ursprüngliche Nachricht- Von: Kris Kennaway [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 15. März 2007 19:13 An: Christian Walther Cc: Nino Ivanov; freebsd-questions@freebsd.org Betreff: Re: FreeBSD 2.2.9 / Installation problem On Thu, Mar 15, 2007 at 12:28:12PM +0100, Christian Walther wrote: On 15/03/07, Nino Ivanov [EMAIL PROTECTED] wrote: Dear Sir or Madam, [...] The target machine is a HP Omnibook 600c laptop with 8MB RAM, a 486 DX4 processor, 300 MB disk space. No CD drive. No network available. External floppy drive without DMA. (I tried NetBSD, but because of the lack of DMA it did not work properly.) The functioning of the floppy drive is critical, being the machine's only practical means of communicating with the outer world. Due to cost and time considerations, no upgrades are possible. If the target machine is not suitable for an installation of FreeBSD, please let me know so I stop further attempts. I guess you're without luck in this case. AFAIK FreeBSD needs at least 64 MB RAM to work happily. I tried installing it on an P1/133MHz Laptop with 16MB RAM, and it freezes after a few minutes. And it's dead slow. Well it is only true of more modern versions that they do not function well on systems with e.g. 8MB. FreeBSD 2.x was happy with as little as 4MB. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
