FreeBSD-Current said to ask you people.
Begin forwarded message:
From: Ron Hudson [EMAIL PROTECTED]
Date: May 8, 2005 12:52:04 PM PDT
To: freebsd-current@freebsd.org
Subject: Booting from DOS?
I have just installed 5.3
I have a 100mb dos partition, 70mb swap and the rest of the 2gb hard
drive
On Thursday 31 March 2005 08:36 am, Daniel Johansson wrote:
Hi, I really need some help here. I'm running a raid0, with
vinum, and read the errata about adding geom_vinum_load=YES
to loader.conf because vinim_start=YES in rc.conf paniced my
system when booting. I'm running 5.3-RELEASE
I am working on setting up what will end up being a fully automated
environment for setting up our FreeBSD systems. As part of the setup
process when they are racked they get plugged into a serial console
(Cyclades) and I have console=comconsole in the loader.conf that I'm
using in the PXE
Hello,
Do someone has the AOpen NIC [1] from www.disklessworkststions.com
doing diskless PXE booting properly with FreeBSD 5.3+ as server?
Ref.:
[1] http://www.disklessworkstations.com/cgi-bin/web/17.html
Best regards,
Alex
___
freebsd-questions
Hi, I really need some help here. I'm running a raid0, with vinum, and read
the errata about adding geom_vinum_load=YES to loader.conf because
vinim_start=YES in rc.conf paniced my system when booting. I'm running
5.3-RELEASE and the errata mentioned that one too.
So I added gvinum
On Thursday 31 March 2005 08:36 am, Daniel Johansson wrote:
Hi, I really need some help here. I'm running a raid0, with
vinum, and read the errata about adding geom_vinum_load=YES
to loader.conf because vinim_start=YES in rc.conf paniced my
system when booting. I'm running 5.3-RELEASE
Hello,
I have two IDE disks with the following Operating Systems:
IDE-0 -- ad0s1 -- Windows XP Pro
ad0s5 (extended) -- Windows 2000 Pro
IDE-1 -- ad2s1 -- Debian Sarge (managing LILO at IDE-1)
ad2s4 -- FreeBSD 5.3
I boot from the second disk. I have LILO in the MBR because
Hi,
I'm facing a rather severe problem installing 5.4 (or 5.4-Beta):
Hardware:
Compaq/HP Evo d310
latest available BIOS 3.18
HD: 40GB
Problem: When booting from a FreeBSD-Installation CD (either disc1,
bootonly - doesn't really matter) the system immediately crashes when
it comes to the FreeBSD
Hi,
I'm facing a rather severe problem installing 5.4 (or 5.4-Beta):
Hardware:
Compaq/HP Evo d310
latest available BIOS 3.18
HD: 40GB
Problem: When booting from a FreeBSD-Installation CD (either disc1,
bootonly - doesn't really matter) the system immediately crashes when
it comes
. However, when I choose the default
option from there I get some messages scrolling up about it booting
the kernel and detecting some ACPI stuff, but after a few seconds it
gets to this message and then hangs:
uhci0: Intel 82801DB (ICH4) USB Controller USB-A port 0xefe0-0xefff
irq 11 at device 29.0
Guys/Gals,
One of my embedded machines died a while back after several years of service
(enough to erase my memory.). I am trying to rebuild the flash file system
on the machine, and ran into a snag. I'm attempting to manually install
4.11-REL on this system, as it is a rather old device with
I have been trying, unsuccessfully, to boot a
kernel with an embedded root filesystem. I've
searched the mailing lists and the web without finding
an answer. I hope someone here can help.
Here's the procedure I have used:
1. My kernel is built with options: MFS, MD_ROOT and
MD_ROOT_SIZE=32768.
(addendum to prior -questions inquiry)
I found a way using Bochs (bochs.sourceforge.net). It will boot an iso image as
will vmware 4.5 (others?).
I have however run into a hiccup. 4.x will boot, 5.x won't. I've submitted it
as a possilbe bug to the
bochs bug tracker. If anyone in the freebsd
Has anyone ever seen, heard of, done it? I'm working on a FreeSBIE-built image
(w/ 5.3-Stable) and would like to pre-burn boot the final iso image.
I can mount and traverse the image fine but want to make sure I've crossed all
the t's with an actual boot before I start manufacturing shiny
On Mar 2, 2005, at 7:19 PM, [EMAIL PROTECTED]@comcast.net wrote:
Has anyone ever seen, heard of, done it? I'm working on a
FreeSBIE-built image (w/ 5.3-Stable) and would like to pre-burn boot
the final iso image.
I can mount and traverse the image fine but want to make sure I've
crossed all
I recently picked up an HP5460 AMD64 laptop, and I recently wanted to try
FreeBSD on it. Unfortunately, both the x86 and AMD64 versions will not boot,
actually shutting the power down shortly after the kernel finishes loading.
I've tried 5.3 and 4.8 with similar results, also cycling through
On Monday 28 February 2005 06:56 pm, Brian J. McGovern wrote:
I recently picked up an HP5460 AMD64 laptop, and I recently wanted
to try FreeBSD on it. Unfortunately, both the x86 and AMD64
versions will not boot, actually shutting the power down shortly
after the kernel finishes loading. I've
I created a bug report and nothing was entered,so I thought I would ask the
group again if anyone has seen this??
Brand new drives...brand new full install:
Using 5.3 release is when I 1st noticed this. CVSup to 5.3-STABLE does not
fix this trouble.
If both IDE channels are enabled and they
I am not an expert on FreeBSD and I am not an expert on hardware. I think I
am going nuts compiling my kernel of release 4.11. It compliles all right
but it wouldn't boot. The error I get is: panic no BSP found. Anyone has
an idea of what that means? I'll give you my configuration file just in
I am not an expert on FreeBSD and I am not an expert on hardware. I think I
am going nuts compiling my kernel of release 4.11. It compliles all right
but it wouldn't boot. The error I get is: panic no BSP found. Anyone has
an idea of what that means? I'll give you my configuration file just in
Teilhard Knight wrote:
I am not an expert on FreeBSD and I am not an expert on hardware.
Neither am I, but...
The error I get is: panic no BSP found. Anyone has
an idea of what that means? I'll give you my configuration file just in
case someone takes the trouble to have a look at it. My machine
- Original Message -
From: Toomas Aas [EMAIL PROTECTED]
To: Teilhard Knight [EMAIL PROTECTED]
Cc: FreeBSD freebsd-questions@freebsd.org
Sent: Wednesday, February 23, 2005 1:51 PM
Subject: Re: Booting problems
Teilhard Knight wrote:
I am not an expert on FreeBSD and I am not an expert
What do I get extra if I boot with verbose logging at the boot menu
during FreeBSD startup?
--
Anthony
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL
On Wed, 02 Feb 2005 16:05:06 +, Mark Ovens [EMAIL PROTECTED] wrote:
The limitation is in NTLDR because it's M$ so is only designed for
booting M$ OSes and the BOOTSECT file method is designed for booting DOS
and non-NT class Windows which could only boot from the first partition
On Wed, 02 Feb 2005, Adil F. Mamedov wrote:
Hello!
After my WINDOWS XP crashed, I decided to reinstall it... But I forgot
that during windows installation it overwrites the MBR. So, instead of
prompting me for the OS to load (FreeBSD or Windows), the system loads
Windows. When I found this
. Possibly BootPart modifies
the extracted bootsectors specially, changing the special parameters
to enable booting of the second disk from the first? Its a thought ...
maybe the way these files are written to the disk (from where dd
extracts them), the special parameters are not such that they can
On Wed, 2 Feb 2005 01:48:47 -0800, Loren M. Lang [EMAIL PROTECTED] wrote:
Unless BootPart specifically know about how the freebsd boot loaders
work and how to reconize them, I doubt that it's modifying those
parameters. Now the last 66 bytes of the MBR stores the partition table
of the hard
was extracted using BootPart blah blah ...
I don't know about BootPart, but the FreeBSD boot manager replaces the
MBR on _both_ disks and allows booting from either.
The limitation is in NTLDR because it's M$ so is only designed for
booting M$ OSes and the BOOTSECT file method is designed for booting DOS
with me coz
once I got those values, it was just a matter of noting them down and
then booting into Linux (coz that's what I had apart from FreeBSD) and
recreating the tables using its fdisk program. :))
IRCC, boot0 is the MBR and boot1 is the boot sector (of the FreeBSD
partition (slice
On Tue, 1 Feb 2005 04:10:49 -0800, Loren M. Lang [EMAIL PROTECTED] wrote:
I think that you should be able to use boot0 and boot1 as a file once
the apropriate fields are filled in. When boot0 and boot1 are written
to the disk in their special locations, several bytes of each file are
modified
to enable booting of the second disk from the first? Its a thought ...
maybe the way these files are written to the disk (from where dd
extracts them), the special parameters are not such that they can be
booted from the first disk. But when BootPart extracts the sectors, it
modifies these parameters
Hello!
After my WINDOWS XP crashed, I decided to reinstall it... But I forgot
that during windows installation it overwrites the MBR. So, instead of
prompting me for the OS to load (FreeBSD or Windows), the system loads
Windows. When I found this problem, I have booted my system from the CD,
then
Rakhesh Sasidharan wrote:
No, boot0 is just a normal file that is 512 bytes long. There is
nothing special about it. In it is a bootloader program that can be
used to boot FreeBSD, and if you run it during boot, it will read the
partition table and look for all OSes. I think it will modify the
On Mon, Jan 31, 2005 at 11:59:11AM +0400, Rakhesh Sasidharan wrote:
No, boot0 is just a normal file that is 512 bytes long. There is
nothing special about it. In it is a bootloader program that can be
used to boot FreeBSD, and if you run it during boot, it will read the
partition table
. Which explains why my MBR got messed up when I tried
booting FreeBSD this way. :(
But I'm still confused. How do I install boot0 using sysinstall? As
far as I remm, sysinstall gives three options -- (a) leave the MBR
untouched, (b) put a standard MBR, and (c) install BootEasy. My
understanding
So that means I should install boot0 to the MBR of my second disk,
using boot0cfg with the -o noupdate flag, and then extract that MBR
(using dd for instance) to a file like c:\bootsectbsd? That should
work?
Or wait, maybe there's no need to extract. When I install boot0 to the
MBR, possibly the
understand now is -- copying boot0 over to c:\bootsect.bsd
will *not* work. Which explains why my MBR got messed up when I tried
booting FreeBSD this way. :(
But I'm still confused. How do I install boot0 using sysinstall? As
far as I remm, sysinstall gives three options -- (a) leave the MBR
! :))
So what I understand now is -- copying boot0 over to c:\bootsect.bsd
will *not* work. Which explains why my MBR got messed up when I tried
booting FreeBSD this way. :(
But I'm still confused. How do I install boot0 using sysinstall? As
far as I remm, sysinstall gives three options -- (a) leave
On Mon, 31 Jan 2005 11:33:59 +, Mark Ovens [EMAIL PROTECTED] wrote:
I rewrote that section of the FAQ years ago (around FreeBSD 3.1!!)
because the previous wording was unclear and I did _exactly_ what
Rakhesh has done :-(
Ah! Glad to see I am not the only one. :))) Felt really goofy when I
Rakhesh Sasidharan wrote:
On Mon, 31 Jan 2005 11:33:59 +, Mark Ovens [EMAIL PROTECTED] wrote:
I rewrote that section of the FAQ years ago (around FreeBSD 3.1!!)
because the previous wording was unclear and I did _exactly_ what
Rakhesh has done :-(
Ah! Glad to see I am not the only one. :)))
Joe Kraft wrote:
Rakhesh Sasidharan wrote:
I'm doing it with Win2k, I haven't tried it yet with XP though. And
I'll preface this, with I'm doing this from memory because I can't find
the web page they originally came from.
Shame on me for taking a stab at this one without confirming what I was
and
then booting into Linux (coz that's what I had apart from FreeBSD) and
recreating the tables using its fdisk program. :))
IRCC, boot0 is the MBR and boot1 is the boot sector (of the FreeBSD
partition (slice)) and they only ontain info about the local disk, i.e.
_relative_ info in effect, so if FreeBSD
On Mon, 31 Jan 2005 17:22:48 +, Joe Kraft [EMAIL PROTECTED] wrote:
This should have said boot1, for all the reasons mentioned in the rest
of the thread and in the handbook. Sorry,
Nah! boot1 does not work either! I've tried ... I guess it might work
if FreeBSD is on the first disk, but it
] wrote:
Hi,
Are there any issues in booting FreeBSD using NTLDR? My machine has
Windows XP, Fedora Core 3, and FreeBSD-5.3, and while I know I can use
GRUB to boot FreeBSD, I want to try booting it using NTLDR. Just for
kicks -- its something I haven't tried so far. :))
My ad0 disk has WinXP
subscribed, its possible something is
wrong -- and so am resending it.
Sorry for the inconv. :))
On Sun, 30 Jan 2005 10:47:41 +0400, Rakhesh Sasidharan
[EMAIL PROTECTED] wrote:
Hi,
Are there any issues in booting FreeBSD using NTLDR? My machine has
Windows XP, Fedora Core 3
for the inconv. :))
On Sun, 30 Jan 2005 10:47:41 +0400, Rakhesh Sasidharan
[EMAIL PROTECTED] wrote:
Hi,
Are there any issues in booting FreeBSD using NTLDR? My machine has
Windows XP, Fedora Core 3, and FreeBSD-5.3, and while I know I can use
GRUB to boot FreeBSD, I want to try
On Sun, 30 Jan 2005 10:47:41 +0400, Rakhesh Sasidharan
[EMAIL PROTECTED] wrote:
Are there any issues in booting FreeBSD using NTLDR? My machine has
Windows XP, Fedora Core 3, and FreeBSD-5.3, and while I know I can use
GRUB to boot FreeBSD, I want to try booting it using NTLDR. Just for
kicks
No, boot0 is just a normal file that is 512 bytes long. There is
nothing special about it. In it is a bootloader program that can be
used to boot FreeBSD, and if you run it during boot, it will read the
partition table and look for all OSes. I think it will modify the
partition table,
Hi,
Are there any issues in booting FreeBSD using NTLDR? My machine has
Windows XP, Fedora Core 3, and FreeBSD-5.3, and while I know I can use
GRUB to boot FreeBSD, I want to try booting it using NTLDR. Just for
kicks -- its something I haven't tried so far. :))
My ad0 disk has WinXP (and NTLDR
,
Are there any issues in booting FreeBSD using NTLDR? My machine has
Windows XP, Fedora Core 3, and FreeBSD-5.3, and while I know I can use
GRUB to boot FreeBSD, I want to try booting it using NTLDR. Just for
kicks -- its something I haven't tried so far. :))
My ad0 disk has WinXP (and NTLDR), while ad1
fallback 1
# For booting FreeBSD
title FreeBSD - Unix
root (hd0,a)
kernel /boot/loader
# For booting Windows NT or Windows95
title Windows XP Menu
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd0,1)
chainloader +1
makeactive
Any help would be greatly appreciated, at this point this is my last
Get GAG (gag.sourceforge.net) and try booting to Windows...
HTH
On Mon, 24 Jan 2005 01:27:45 -0800, gabriel [EMAIL PROTECTED] wrote:
I'm trying to dual boot FreeBSD and Windows XP with two different
disks, I have manged to get FreeBSD running and installed the boot
manager and grub
I'd rather get grub working, I don't think installing another boot
loader is gonna solve anything. Plus I like grub :P
On Mon, 24 Jan 2005 02:21:07 -0800, Irvin Piraman [EMAIL PROTECTED] wrote:
Get GAG (gag.sourceforge.net) and try booting to Windows...
HTH
On Mon, 24 Jan 2005 01:27:45
:P
On Mon, 24 Jan 2005 02:21:07 -0800, Irvin Piraman [EMAIL PROTECTED] wrote:
Get GAG (gag.sourceforge.net) and try booting to Windows...
HTH
On Mon, 24 Jan 2005 01:27:45 -0800, gabriel [EMAIL PROTECTED] wrote:
I'm trying to dual boot FreeBSD and Windows XP with two different
I have been running a dual boot system with Windows and FreeBSD on
separate disks for several years. I use just the basic FreeBSD MBR boot
program, installed using the procedure described in the Handbook.
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html
Windows XP
In my case, freebsd is on the master and windows is on the slave, you
mean that it should be the other way around?
On Mon, 24 Jan 2005 08:45:44 -0800, Brian M. Kincaid [EMAIL PROTECTED] wrote:
I have been running a dual boot system with Windows and FreeBSD on
separate disks for several years.
Yup, Windows needs to be the first disk.
gabriel wrote:
In my case, freebsd is on the master and windows is on the slave, you
mean that it should be the other way around?
On Mon, 24 Jan 2005 08:45:44 -0800, Brian M. Kincaid [EMAIL PROTECTED]
wrote:
I have been running a dual boot system with
hmm.. I guess I can just change the jumper settings on the disks to
swap 'em out? *sigh*
What do you suggest?
On Mon, 24 Jan 2005 08:51:33 -0800, Brian M. Kincaid [EMAIL PROTECTED] wrote:
Yup, Windows needs to be the first disk.
gabriel wrote:
In my case, freebsd is on the master and
Gabriel:
What I would do is make sure that you can get Windows to boot up as the
master disk before doing any further modifications to the boot blocks.
If you get this far, then the FreeBSD Handbook procedure will handle the
rest.
If you can't get Windows to boot, there are several possible
error and it
halts.
Here's my menu.lst:
I have Grub booting just from 1 disk, not 2, but with 4 different partitions.
Here's my menu.lst as installed by Suse 9.2. I just moved the FreeBSD lines up
to the first place ;-). The lines to boot FreeBSD from the Linux Grub version
I found with a info
my menu.lst:
I have Grub booting just from 1 disk, not 2, but with 4 different partitions.
Here's my menu.lst as installed by Suse 9.2. I just moved the FreeBSD lines up
to the first place ;-). The lines to boot FreeBSD from the Linux Grub version
I found with a info grub under Suse
I reinstalled windows on the second disk, ran fdisk -B -b /boot/boot0
device then ran grub-install device. After that I configured grub as
such:
config:menu.lst
color black/cyan yellow/cyan
default 0
fallback 1
# For booting FreeBSD
title FreeBSD - Unix
root (hd0,a)
kernel /boot/loader
. The computer reboots, and does the same,
over and over again. That's about it. And I've tried many things:
1) Playing with the BIOS setup, disabling ACPI and DMA settings, as well
as looking for places to 'add a UNIX OS' but there are none.
2) Tried booting to my harddrive from the installation CD-ROM
to /boot/safe. I didnt want to run the install
world if the new kernel wont boot, fearing it would update and overwrite
crucial bits of the OS and prevent the laptop from booting the old kernel.
I'm lost really in where to go from here or what the best options are to try
and get the machine updated
to /boot/safe. I didnt want to run the install
world if the new kernel wont boot, fearing it would update and overwrite
crucial bits of the OS preventing the laptop from booting the old kernel.
I'm lost really in where to go from here or what the best options are to try
and get the machine updated
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Hi,
I have an amd64 server machine with a 3ware 8506-4lp raid controller and
succeeded in installing the FreeBSD 5.3-RELEASE on this machine in safe
mode, but it boots only in safe mode. I've upgraded the kernel to stable,
but there's no result.
I don't know what's the difference between the safe
Hello,
I have a problem after adding a firewire hard
disk to my system. I did format and label the
drive and the drive works without any problem.
After a reboot I am getting the following message
after the firewire was detected:
ffs_mountroot: can't find rootvp
The firewire disk is /dev/da1 and my
OK - I did find the answer ...
After plugging-in the firewire device, /dev/da0
changes to /dev/da1 while botting and /dev/da1
(aka firewire) changes to /dev/da0.
How can it be accomplished that /dev/da0
(my non-removable SCSI disk) remains /dev/da0,
no matter how many removable drives are added
to
Hello,
I'm hoping to use freebsd as a custom router. To minimize noise and failure
points, I was hoping to boot from a USB2 flash stick which have gotten dirt
cheap. I downloaded 5.3RELEASE-i386-miniinst.iso and burned it to CD -
stuck my 512MB flash drive into a USB port, and let the CD boot
On 26 Dec Juha Saarinen wrote:
It looks like Fafa is a troll. Same message was posted to the misc
OpenBSD list.
So what? He might think his problem is *BSD* related in stead of FreeBSD
alone causing the problem. So in asking there too he hoped for more
answers (?)
Just my 2p
--
dick --
Dear all of you,
My computer (HP Compaq DC7100) refuses to boot to FreeBSD. It enters
the= MBR, I then select FreeBSD
in the bootloader and the computer reboots! What kind of behavior is
thi= s, and why won't it give FreeBSD a chance?
I'm aware that some UNIX systems need a
Dear all of you,
My computer (HP Compaq DC7100) refuses to boot to FreeBSD. It enters
the= MBR, I then select FreeBSD
in the bootloader and the computer reboots! What kind of behavior is
thi= s, and why won't it give FreeBSD a chance?
I'm aware that some UNIX systems need a
On Sat, 25 Dec 2004 10:39 pm, Fafa Diliha Romanova wrote:
Dear all of you,
My computer (HP Compaq DC7100) refuses to boot to FreeBSD. It enters
the
in the bootloader and the computer reboots! What kind of behavior is
thi
I'm aware that some UNIX systems need a patch to
On Saturday 25 December 2004 06:11 pm, Malcolm Kay
[EMAIL PROTECTED] wrote:
On Sat, 25 Dec 2004 10:39 pm, Fafa Diliha Romanova wrote:
Dear all of you,
My computer (HP Compaq DC7100) refuses to boot to FreeBSD. It
enters the
in the bootloader and the computer reboots! What
My computer (HP Compaq DC7100) refuses to boot to FreeBSD. It enters
the MBR, I then select FreeBSD in the bootloader and the computer
reboots! What kind of behavior is this, and why won't it give FreeBSD a
chance?
I had the same symptom on different hardware. If I watched closely, I could
It looks like Fafa is a troll. Same message was posted to the misc
OpenBSD list.
--
Juha
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
A few days ago I tried to compile and install FreeBSD 5.3-p2 from a
FreeBSD 5.3-p1
Everething worked until I wanted to make installword. I switched to
single mode, and during the installation my computer stoped and shaw me
a error (I don't remember it). I had to reboot, and booting process
computer stoped and shaw me
a error (I don't remember it). I had to reboot, and booting process
stopped with some hexadecimal characters and with the string BTX Halted.
I downloaded the second disc of FBSD 5.3 release, and I could fix the
disk, and I could copy /boot/kernel directory from cd
Ahoy. I'm trying to install FreeBSD on a 486 to use as
a router. The BIOS has a 2 gig limitation for hard
drive, which is apparent because it automatically
detects my 13 gig drive as a 2 gig. So after
installing the base system and rebooting, it says it
cannot find the kernel. I know what you're
Good day,
I found out this very weired experience on
freebsd(4.10, 5.3) booting process one time when I was
using my home pc. I've installed cups and renamed the
cups.sh.sample to cups.sh to be able to run it at boot
time. I have successfully set up my printer and be
able to print some test
Hello,
This message is directed toward PXE masochists. I'm heading straight to
the gory details.
I loopback mounted 5.3-RELEASE-amd64-bootonly.iso and copied the entire
boot directory onto my OpenBSD DHCP server. I tweaked this by adding the
directive boot_askname= to loader.conf. Then I PXE
[EMAIL PROTECTED] wrote:
I wasn't able to discover much in the holographic console. That console
has rm but not ls. It has ifconfig but not netstat. I can cd into /stand
but hardly any other directory listed in the PATH variable. Next time
I'll try typing xyzzy to see if more commands
Mr Answer:
Sorry having troubled you to give me reasons about the solution to the question
9.10. How can I use the Windows NT loader to boot FreeBSD? listed on bsd
site. I have installed my first bsd on the second disk with whole space, and I
have chosen to install bootmgr. But when reboot, I
Yesterday I received hardware to complete a Tyan S2882 based system. In just a
few hours I had FreeBSD 5.3-STABLE / AMD64 running with all memory and
processors accounted for.
I have two hotswap IDE RAID devices installed. I have an old ARAID-99 from the
previous 4.x system where it
Tabor Kelly wrote:
[snip]
I have no idea what file it was or how it got changed, but thanks Ash.
I figured out what I did. I overwrote the default /boot/device.hints
with the 4 lines in my original email (I didn't realize there was a
default /boot/device.hints). This was all accomplished with
and there is
presently no man page for devfs.conf
Is there some reason under 5.3 that booting off the SATA SOHORAID would
prevent the PATA RAID drive detect? The ARAID-99/1000 appears to FreeBSD
as a single PATA disk drive echoing the geometry of whatever primary drive
is presently inserted
to
booting *with* ACPI on one system whereas it shows the default entry
with ACPI *disabled* on the other system.
What do I need to set/change so that a system comes up with ACPI
enabled by default (i.e. with ACPI being the default entry in the
boot menu)?
TIA for your help,
-ewald
: Thursday, November 18, 2004 20:48
To: [EMAIL PROTECTED]
Subject: Booting with ACPI enabled by default? (5.3)
Hi,
I've installed two system from scratch with 5.3 in the past few
days. One system by default comes up with ACPI enabled, the other with
ACPI disabled.
Close watch has revealed
On Thu, Nov 18, 2004 at 09:33:40PM +0530, Subhro wrote:
Can we have a dmesg -a on the box with ACPI disabled?
Sure - I'm including it below.
Please note, that the box *does* come up with ACPI enabled when I
manually choose the menu item on the boot menu (beastie.4th) that says
boot with acpi
The is on a Dell Inspiron 1100 notebook (celeron 2.3Ghz) running FreeBSD
5.3R. When I boot my laptop I see the Beastie menu, and after making a
selection, I get no output from boot1 or the kernel. So, when my laptop
is done booting, my screen looks like this:
/boot/kernel/acpi.ko text=0x3fbfc
Tabor Kelly wrote:
The is on a Dell Inspiron 1100 notebook (celeron 2.3Ghz) running FreeBSD
5.3R. When I boot my laptop I see the Beastie menu, and after making a
selection, I get no output from boot1 or the kernel. So, when my laptop
is done booting, my screen looks like this:
/boot/kernel
Ash wrote:
[snip]
Well, I looked and looked for what was wrong, and I was 100% sure it
wasn't anything in the /boot directory. However, just to be sure I
copied everything in /boot and /boot/default from another FreeBSD 5.3R
system I had, and it started working again.
I have no idea what file
I have this odd behaviour from both my 5.2 and my 5.3 installations.
GENERIC or my own.
When booting the console displays the usual messages like below:
1 Starting local daemons:.
2 Updating motd.
3 Configuring syscons: keymap blanktime.
4 Initial i386 initialization:.
5 Additional ABI support
Hi,
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andreas Davour
Sent: Tuesday, November 16, 2004 20:38
To: [EMAIL PROTECTED]
Subject: Mysterious freeze while booting
I have this odd behaviour from both my 5.2 and my 5.3 installations.
GENERIC or my
On Tue, 16 Nov 2004, Subhro wrote:
When booting the console displays the usual messages like below:
1 Starting local daemons:.
2 Updating motd.
3 Configuring syscons: keymap blanktime.
What is strange is that after line 3 the computer suddenly stops for a
long time, almost a minute, doing (as far
Hi,
-Original Message-
From: Andreas Davour [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004 20:58
To: Subhro
Cc: [EMAIL PROTECTED]
Subject: RE: Mysterious freeze while booting
snip
Why would adding the hostname work? What is it that's fooling around
with my hostname
On Tue, 16 Nov 2004, Subhro wrote:
/etc/hosts basically serves as a backup for cases where the DNS does not
work. Seems to me as if sshd is crating the seem to hang up as it can't get
the box hostname resolved properly.
Sshd? It shouldn't even be running! I guess I'll have to see if it is...
-Original Message-
From: Andreas Davour [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004 21:15
To: Subhro
Cc: [EMAIL PROTECTED]
Subject: RE: Mysterious freeze while booting
On Tue, 16 Nov 2004, Subhro wrote:
/etc/hosts basically serves as a backup for cases where the DNS
On Tue, 16 Nov 2004, Subhro wrote:
On Tue, 16 Nov 2004, Subhro wrote:
/etc/hosts basically serves as a backup for cases where the DNS does
not
work. Seems to me as if sshd is crating the seem to hang up as it can't
get
the box hostname resolved properly.
Sshd? It shouldn't even be running! I
601 - 700 of 1069 matches
Mail list logo
