David Chisnall wrote:
> http://wiki.freebsd.org/WhyUseFreeBSD
>
> Feedback welcome!
Quote:
> The RCng system that reads this file [rc.conf] understands
> dependencies between services and so can automatically launch
> them in parallel [...]
Can it? There have been patches in the lists, was one o
David Chisnall wrote:
> If you had
> to list the three things you most like about FreeBSD, which would you pick?
1. Large number of ports, including obscure programs other package
system don't have.
2. Relatively straightforward system configuration (i.e. rc.conf), as
opposed to options scattered
Antony Mawer wrote:
> Not sure if this is the right place to post it -- about 6 years ago I
> put together a module which displays an ASCII splash screen on boot
> (rather than the graphical splash_pcx and splash_bmp modules).
As a user, I think this is rather cool; at least it is more useful for
John Baldwin wrote:
> A true uncorrected machine check would trigger a MC# fault and panic. I
> think
> this is just garbage in the MCx banks. Are you running the latest 8-stable?
No, 8.1-RELEASE.
___
freebsd-stable@freebsd.org mailing list
http://
Jeremy Chadwick wrote:
> On Wed, Sep 29, 2010 at 09:57:53AM -0700, Chuck Swiger wrote:
>> Is prime95 testing running stable after waking from sleep?
Yes, 0 errors, 0 warnings.
> The Thinkpad hardware he's on is """old""" (note the quotes), so I
> wouldn't be surprised if the CPU (Intel Pentium M)
Chuck Swiger wrote:
>> MCA: Bank 1, Status 0xe20001f5
>> MCA: Global Cap 0x0005, Status 0x
>> MCA: Vendor "GenuineIntel", ID 0x695, APIC ID 0
>> MCA: CPU 0 UNCOR PCC OVER DCACHE L1 ??? error
>
> That is very likely to be a matter of luck. If I translate thi
Chuck Swiger wrote:
>> MCA: Bank 1, Status 0xe20001f5
>> MCA: Global Cap 0x0005, Status 0x
>> MCA: Vendor "GenuineIntel", ID 0x695, APIC ID 0
>> MCA: CPU 0 UNCOR PCC OVER DCACHE L1 ??? error
>
> That is very likely to be a matter of luck. If I translate thi
Jung-uk Kim wrote:
>> - the mouse doesn't work until I restart moused manually
>
> I always use hint.psm.0.flags="0x6000" in /boot/loader.conf, i.e.,
> turn on both HOOKRESUME and INITAFTERSUSPEND, to work around similar
> problem on different laptop.
Yes, that helps (after the stall period).
Ian Smith wrote:
> [...] During the 60s resume stall period, iff
> I'd suspended from a VTY, I found I could slowly (like maybe 3 seconds
> per character echoed) type a command, and some commands - possibly those
> cached? as there's no HD access - would run after another few seconds.
>
> In this
Ian Smith wrote:
> On Wed, 22 Sep 2010, Ted Faber wrote:
>
> > Sorry, Ian, I don't have anything new, wrt the ATA.
>
> Thanks Ted. Interesting that nobody else seems to have run into this
> issue, must be a (some?) Thinkpads thing ..
FWIW, my Thinkpad T40 does the same thing on 8.1: after res
Robert Noland wrote:
>> It is not, and yes I use WITHOUT_HAL. Currently disabling DRI helps;
>> should I try rebuilding xorg-server with HAL?
>
> Yes, you can still disable hal at runtime by setting AutoAddDevices
> "Off" in xorg.conf.
Seems to work with HAL.
Unloading radeon also works, but the
Andriy Gapon wrote:
> Please check if your X binary is linked with libthr (using ldd).
> I saw similar problems when it was not.
> That was because it was compiled without HAL support.
It is not, and yes I use WITHOUT_HAL. Currently disabling DRI helps;
should I try rebuilding xorg-server with HAL
Robert Noland wrote:
>> I have a similar problem with ATI Mobility Radeon 9000 (r250) and
>> FreeBSD 8.0-RELEASE-p2 i386 (dmesg is at [1]). The system hangs when I
>> run Xorg with xorg.conf obtained by `Xorg -configure' and do either of
>> these:
>>
>> * pkill Xorg
>> * close xorg via ^C and start
Oliver Pinter wrote:
> After updated the xorg* and dri* and dependency, the system going to
> deadlock at second start of xserver. I think it is not an uniqe issue,
> as others wrote them at freebsd-x11:
> http://lists.freebsd.org/pipermail/freebsd-x11/2010-February/009370.html
I have a similar pr
Jeremy Chadwick wrote:
>> Yes, ad0s1b is the swap, but I think it fails before doing newfs.
>> "Writing partition information to ad0" is the last message I see before
>> the error occurs, no newfs popups occur.
By the way, in the fixit console /dev has ad0b but not ad0s1b.
> Can you get this disk
Kevin Oberman wrote:
>> The setup tries to create filesystem and fails with this message:
>>
>> Unable to find device node for /dev/ad0s1b in /dev!
>
> Are you doing a 'W'rite in the labeling tools? I'm guess that you are
> not, but I wanted to be sure. You don't want to.
Nope, no write.
> Y
Greetings everyone. I'm trying to install FreeBSD 8.0 from Disk1 on
ThinkPad T40, so far unsuccessfully.
Here are the setup steps:
Installer complains that "77520/16/63" may not be a good geometry for
ad0, proposes "4864/255/63" instead (both eventually lead to failure).
I create a single disk-wid
17 matches
Mail list logo
