On Tue, 27 Mar 2007, Jason Gretz wrote:
Hey guys I am adding a hard drive to my FreeBSD 6.1 box and it stalls during
booting and makes a beeping noise. I know the hard drive is good because I just
swapped it out of another FreeBSD box…
So I’m kinda stumped, is there anyways to troubleshoot th
Each BIOS maps beep codes into a diagnostic message.
Also, are you getting video signal/BIOS on your monitor?
~BAS
http://www.computerhope.com/beep.htm
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
Each BIOS maps beep codes into a diagnostic message.
Also, are you getting video signal/BIOS on your monitor?
~BAS
On Tue, 2007-03-27 at 14:47 -0500, David J Brooks wrote:
> On Tuesday 27 March 2007 02:29:29 pm Jason Gretz wrote:
> > Hey guys I am adding a hard drive to my FreeBSD 6.1 box and it
On Tuesday 27 March 2007 02:29:29 pm Jason Gretz wrote:
> Hey guys I am adding a hard drive to my FreeBSD 6.1 box and it stalls
> during booting and makes a beeping noise. I know the hard drive is good
> because I just swapped it out of another FreeBSD box…
>
> So I’m kinda stumped, is there anyway
Hey guys I am adding a hard drive to my FreeBSD 6.1 box and it stalls during
booting and makes a beeping noise. I know the hard drive is good because I just
swapped it out of another FreeBSD box…
So I’m kinda stumped, is there anyways to troubleshoot this? I can’t even boot
in “safe” or “single
My apologies if this is wrong list.
I have a Vaio PCG-9251 laptop with a Seagate Momentus 20G hard drive that has
been working great
with 6.1 release. I had left it powered down for about 5 weeks, then on
powerup, it was booting
fine until it started bringing the wireless online. I noticed t
> On 11/8/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> The actual enclosure is made by Western Digital.
>>
>> If I run usbdevs I receive the following output.
>>
>> addr 1: UHCI root hub, Intel
>> addr 1: UHCI root hub, Intel
>> addr 1: EHCI root hub, Intel
>> addr 2: External HDD, Western
On 11/8/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> The actual enclosure is made by Western Digital.
>
> If I run usbdevs I receive the following output.
>
> addr 1: UHCI root hub, Intel
> addr 1: UHCI root hub, Intel
> addr 1: EHCI root hub, Intel
> addr 2: External HDD, Western Digital
>
If you have the chance I would suggest building a custom kernel with the
'device uhid'
Line commented out to see if that makes a difference. The only real problem
with this I believe will be that some devices that act as hids, keyboards
and mice (others too, not sure the entire scope) may
What I have found is that if I boot with the USB HDD attached to the
system, the system will hang when starting to mount the file systems.
However, if I connect the drive after the system is booted, everything is
fine. da0 appears, etc.
What should I be looking at to make the system boot with th
The actual enclosure is made by Western Digital.
If I run usbdevs I receive the following output.
addr 1: UHCI root hub, Intel
addr 1: UHCI root hub, Intel
addr 1: EHCI root hub, Intel
addr 2: External HDD, Western Digital
I'm guessing the device would be /dev/da0s1.
Thanks for your help.
J
What type of enclosure are you using, is the actual enclosure made by Western
Digital? We use a 'generic' enclosure with a 250GB ATA Western Digital drive in
it - and aside from not having USB 2.0 host/speed... it works quite well. Mounts
as /dev/da1s1d.
--
Nathan Vidican
[EMAIL PROTECTED]
Win
Recently, I purchased several Western Digital External Hard Drives to be
used for backup purposes. The test unit I purchased worked out of the
box, but I am having problems getting the newer ones to work.
When they are plugged in to a FreeBSD 5.3 or 5.4 server, I receive the
following messages:
13 matches
Mail list logo
