> My only problem are when an operation on the unit fails, the
> /dev/cd0 device disappears, and a mknod to recreate the device
> doesn't work either.
Good. It has devfs. Could you
try to read simple CD. It will
remake tracks. (As root, I think.
Cdcontrol.)
> The most recent causes have been usi
To complete the closure on this, have installed a complete system
successfully and rebuilt kernel to enable SMP.
Thanks again for the responses.
Mark
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscr
On Sun, Dec 05, 2004 at 02:43:48AM +, Marta Resende wrote:
> Hey,i upgrade using that options:
>
> #cd /usr/src
> #make buildworld
> #make buildkernel KERNCONF=MINE
> #make installkernel KERNCONF=MINE
> #reboot
> (press 4 for single-user mode)
> #fsck -p
> #mount -u /
> #mount -a
> #cd /usr/sr
On Thu, Dec 02, 2004 at 01:04:12PM -0800, Kyle Mott wrote:
>
> Hi, I just tried to build a 5.3-STABLE kernel with 'options DDB,
> DDB_UNATTENDED', and got an error saying DDB_UNATTENDED was an
> unrecognized option. If we enable DDB, during a crash the system won't
> automagically reboot, correct?
Hey,i upgrade using that options:
#cd /usr/src
#make buildworld
#make buildkernel KERNCONF=MINE
#make installkernel KERNCONF=MINE
#reboot
(press 4 for single-user mode)
#fsck -p
#mount -u /
#mount -a
#cd /usr/src
#mergemaster -p
#make installworld
#mergemaster
and when i reboot, freebsd stops under
Hi, I just tried to build a 5.3-STABLE kernel with 'options DDB,
DDB_UNATTENDED', and got an error saying DDB_UNATTENDED was an
unrecognized option. If we enable DDB, during a crash the system won't
automagically reboot, correct? We need to have the DDB_UNATTENDED
option, or am I just missing some
Hi,
Thanks to all that responded.
- Original Message -
From: "Sam Nilsson <[EMAIL PROTECTED]>"
To: To [EMAIL PROTECTED]
Date: Sat, 04 Dec, 2004 21:42 GMT
Subject: Re: make buildworld fails for 5-Stable cvsup'd today
> Godwin Stewart wrote:
> >On Sat, 4 Dec 2004 20:23:22 +, Stacey R
On Sat, Dec 04, 2004 at 04:20:53PM -0800, Doug White wrote:
> On Sat, 4 Dec 2004, Stacey Roberts wrote:
>
> > CPUTYPE?=i686
>
> There is no CPUTYPE "i686".
Yes, there is.
>
> See /usr/share/examples/etc/make.conf for a list of valid CPUTYPEs.
That file lists "i686" as a valid value for CPUT
Doug White said:
> On Wed, 1 Dec 2004, Mike Jakubik wrote:
>
>> Hi,
>>
>> I am getting the following errors on the GigaByte GA-K8VM800M
>> Motherboard.
>> The system seems to run fine however. Latest BIOS installed.
>
> Either there's a bug in our ACPI code or their ACPI bytecode was not
> generate
On Sat, 4 Dec 2004, Stacey Roberts wrote:
> CPUTYPE?=i686
There is no CPUTYPE "i686".
See /usr/share/examples/etc/make.conf for a list of valid CPUTYPEs.
--
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
__
On Thu, 2 Dec 2004, Arjan Van Leeuwen wrote:
> Hi,
>
> I have a weird problem on a dual Xeon 550MHz system running
> 5.3-RELEASE. Everything takes twice as long as it should.
>
> Example:
> winston% time sleep 2
> sleep 2 0.00s user 0.00s system 0% cpu 4.006 total
>
> The same for pings, the scsi
On Thu, 2 Dec 2004, Wei-Kai Wu wrote:
> On Sun, Nov 28, 2004 at 11:16:39PM +0800, Xin LI wrote:
> > Hmm... Is it possible to obtain a backtrace (bt full under kgdb) and post
> > it?
> > Additionally I suggest that you post the same thing to -stable@ and cc to
> > rwatson@, along with your dmesg.
On Wed, 1 Dec 2004, Mike Jakubik wrote:
> Hi,
>
> I am getting the following errors on the GigaByte GA-K8VM800M Motherboard.
> The system seems to run fine however. Latest BIOS installed.
Either there's a bug in our ACPI code or their ACPI bytecode was not
generated for amd64. If you are running
Hi All,
Thanks to all that responded.
- Original Message -
From: "Mark Nipper <[EMAIL PROTECTED]>"
To: To Stacey Roberts
Date: Sat, 04 Dec, 2004 20:28 GMT
Subject: Re: make buildworld fails for 5-Stable cvsup'd today
> On 04 Dec 2004, Stacey Roberts wrote:
> > Hello,
> > I've just
Godwin Stewart wrote:
On Sat, 4 Dec 2004 20:23:22 +, Stacey Roberts
<[EMAIL PROTECTED]> wrote:
internal compiler error: Segmentation fault
Faulty RAM, maybe?
A machine throwing a segfault is fairly characteristic of a CPU overheating
and/or of a faulty RAM stick.
I'll chime in here (again!) a
On Sat, 4 Dec 2004 20:23:22 +, Stacey Roberts
<[EMAIL PROTECTED]> wrote:
> internal compiler error: Segmentation fault
Faulty RAM, maybe?
A machine throwing a segfault is fairly characteristic of a CPU overheating
and/or of a faulty RAM stick.
--
G. Stewart - [EMAIL PROTECTED]
Which is wo
On 04 Dec 2004, Stacey Roberts wrote:
> Hello,
> I've just installed FreeBSD-5.3 REL on a machine here and I'm attempting
> to cvsup to Stable.
>
> After running through the instructions at
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html,
> Step "19.4.7.2 Compile
Hello,
I've just installed FreeBSD-5.3 REL on a machine here and I'm attempting
to cvsup to Stable.
After running through the instructions at
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html, Step
"19.4.7.2 Compile the Base System" fails repeatedly.
Here's the unam
Erik Trulsson wrote:
It is not necessary to reboot or go into single user mode in order to
run mergemaster, and I doubt the handbook says it is necessary.
It is sometimes necessary to reboot with a new kernel to let
installworld work properly, but most of the time rebooting is not
needed.
It is usu
On Sat, Dec 04, 2004 at 06:49:15PM +0100, ptitoliv wrote:
> Hello everybody,
>
> I would like to upgrade one of my FreeBSD boxes but I have a little
> problem with the mergemaster. It is said in the handbook that is
> necessary to reboot on single mode in order to modify config file using
> mer
Hello everybody,
I would like to upgrade one of my FreeBSD boxes but I have a little
problem with the mergemaster. It is said in the handbook that is
necessary to reboot on single mode in order to modify config file using
mergemaster. But the problem is that the box concerned is not physically
On Dec 3, 2004, at 21:03, Adrian Wontroba wrote:
On Fri, Dec 03, 2004 at 02:36:09PM +, Ceri Davies wrote:
Should I expect a dump taken from 4.X to be restorable on 5.X
though?
Yes.
Phew.
I didn't even think about the possibility of dump not being forwards
compatible (8-(
Maybe a note should be
On Sat, Dec 04, 2004 at 12:37:35PM +0100, Godwin Stewart wrote:
> (II) R128(0): Direct rendering enabled
That's beginning to look like it...
> And yet:
> $ glxinfo | grep direct
> direct rendering: No
> OpenGL renderer string: Mesa GLX Indirect
Hmm. Bummer. What kind of framerate does glxgears p
On Sat, 4 Dec 2004 12:37:35 +0100, Godwin Stewart <[EMAIL PROTECTED]>
wrote:
> And yet:
> $ glxinfo | grep direct
> direct rendering: No
> OpenGL renderer string: Mesa GLX Indirect
>
> G.
Installing $PORTS/graphics/dri certainly helped...
/me wipes egg off face.
--
G. Stewart - [EMAIL
On Sat, 4 Dec 2004 23:26, Godwin Stewart wrote:
> wrote:
> > What does..
> > pkgdb /usr/X11R6/lib/libGL.so
> >
> > say?
>
> $ pkg_info -W /usr/X11R6/lib/libGL.so
> /usr/X11R6/lib/libGL.so was installed by package xorg-libraries-6.7.0_3
Hmm, well I didn't use pkg_info because it stops at the first
On Sat, 4 Dec 2004 23:20:46 +1030, "Daniel O'Connor" <[EMAIL PROTECTED]>
wrote:
> What does..
> pkgdb /usr/X11R6/lib/libGL.so
>
> say?
$ pkg_info -W /usr/X11R6/lib/libGL.so
/usr/X11R6/lib/libGL.so was installed by package xorg-libraries-6.7.0_3
Could it be that this is just a stub? I ask becaus
On Sat, 4 Dec 2004 23:12, Godwin Stewart wrote:
> Not that wild...
>
> I only installed what is included with the ports version of xorg, which I
> assume to be MESA. If the ATI R128 requires something extra then that would
> be a good reason for this not working...
It shouldn't need anything but t
On Sat, 4 Dec 2004 23:03:15 +1030, "Daniel O'Connor" <[EMAIL PROTECTED]>
wrote:
> Sure you don't have nvidia GL, or bog standard MESA libraries installed
> for some crazy reason?
> (Wild stab in the dark..)
Not that wild...
I only installed what is included with the ports version of xorg, which
On Sat, 4 Dec 2004 22:07, Godwin Stewart wrote:
> And yet:
> $ glxinfo | grep direct
> direct rendering: No
> OpenGL renderer string: Mesa GLX Indirect
>
> G.
Sure you don't have nvidia GL, or bog standard MESA libraries installed for
some crazy reason?
(Wild stab in the dark..)
--
Dani
On Sat, 4 Dec 2004 11:10:15 +0100, Godwin Stewart <[EMAIL PROTECTED]>
wrote:
> You're probably on to something there. I *do* get the "Direct rendering
> enabled" message on the Linux setup, although the logs also say that
> there's a problem with AGP and that it's falling back to PCI mode.
That w
On Sat, 4 Dec 2004 01:00:18 +0100, Roland Smith <[EMAIL PROTECTED]> wrote:
> > (II) R128(0): [drm] dma control initialized, using IRQ 11
>
> Right after this line I get (for my radeon):
>
> (II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808
>
> Followed by:
>
> (II) RADEON(0):
31 matches
Mail list logo
