date:20120214

Re: [CFT] Xorg Upgrade 7.5.2

2012-02-14 Thread Luca Pizzamiglio

Running on:

* Intel Sandybridge (+ optimus, disabled) on FreeBSD 9.0
* NVidia GTS 450 on FreeBSD 8.2

Not unkwonw problem.
Usual problem on Intel Sandybridge (tty switch, KMS patch issues on
FreeBSD 9 and optimus incompatibility (/dev/dri/card1)).

Tested with KDE 4.7.4 and desktop effect activated. Not all effect are
available using openGL. AFAIK KDE 4.8 is able to use more OpenGL effects
using the same library.

Thanks for the great job you've done!

Best regards,
Luca

On 02/06/12 02:45, Martin Wilke wrote:

Knock knock...

The X11 Team is pleased to announce the next round of Xorg updates.
Note that this is experimental so you really have to know what you are
doing, read UPDATING in the repository, and follow our exact
instructions. We are specifically looking for feedback from Intel, ATI
and NVIDIA users.

Summary of changes:

xf86-video-nouveau has been removed along with the WITHOUT_NOUVEAU
knob. We suggest switching to the nvidia blob.

KMS Support [1]:
Unfortunately, the intel KMS driver will only work for the latest
FreeBSD 9-STABLE or 10-CURRENT users. The patch for HEAD current is
named all.13.1.patch. The higher the version the newer the patch is.
Other needed patches are already available in the Xorg update.

HEAD Users:
Get the latest patchset from Kib here:
http://people.freebsd.org/~kib/drm/

9-STABLE Users:
'meowthink' is currently maintaining the backport to 9 STABLE.
Make sure you have the latest FreeBSD 9-STABLE source.
Get the patch from here:
https://docs.google.com/leaf?id=0BxbPi2OX4_B-NWY3NWU3MzEtNDBjYy00NTljLThlZGItMWFlYjIyYjI4Yjk3&hl=en_US

Rebuild your Kernel and reboot.

Known issuse:
There will be a patch reject in the sys/dev/drm/i915_suspend.c file.
The solution is to manually undo the expansion of the $FreeBSD: $
tag, so it only saysis $FreeBSD$.

Checkout Xorg Development Repo:
You will need to install devel/subversion in order to checkout the xorg
repo. Next, you will need to add WITH_NEW_XORG=yes in
your /etc/make.conf if you want to try out the new Xorg and mesa.

Intel users: note that if you are not qualified for the KMS patch, you
shouldn't use WITH_NEW_XORG=yes because the old intel driver doesn't
build with the new X server. If you are qualified, you should also set
WITH_KMS=yes in /etc/make.conf.

svn co https://trillian.chruetertee.ch/svn/ports/tags/xorg_7_5_2

A small merge script to merge the svn checkout into the real portstree
can be found here:

http://people.freebsd.org/~miwi/xorg/xorgmerge

The script is a modified version of the old kdemerge script. Please set
the KDEDIR variable to the path of your X.org ports.

After merging, run one of the following command, depending on which
tool you use to manage your installed packages.

portupgrade -af \*
portmaster -a

After installing these, you will have to rebuild all xf86-* ports. We
will bump all related ports during the commit to the ports tree.

Roadmap:

Our current plan is to let the CFT running until the last weekend of
February. We hope to get a lot feedback to solve as many problems as
possible. So please help us to get the best xorg update ever in!

Links:
http://wiki.freebsd.org/Intel_GPU [1]
http://wiki.freebsd.org/Xorg
http://miwi.bsdcrew.de/2012/02/working-on-xorg-stuff/

Your FreeBSD Xorg Team

PS: Please reply to the x11@ mailing list. Cross posted due to the
potentially disruptive nature of the change and need to get a wide
variety of testers.

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: MCA UNCOR error

2012-02-14 Thread TAKAHASHI Yoshihiro

In article <201202131308.48171@freebsd.org>
John Baldwin  writes:

> On Sunday, February 12, 2012 4:55:49 am TAKAHASHI Yoshihiro wrote:
>> I get the following error and kernel panic on my pc98 at the boot time.
>> 
>> MCA: Bank 2, Status 0xb614
>> MCA: Global Cap 0x0005, Status 0x0004
>> MCA: Vendor "GenuineIntel", ID 0x616, APIC ID 0
>> MCA: CPU 0 UNCOR PCC no error
>> MCA: Address 0x3446ff003446ff
>> 
>> When I disable MCA with hw.mca.enabled=0 on loader prompt, the machine
>> works fine.  Does it mean my pc98 is broken?  Or other isssue?
>> 
>> It's spec is:
>> 
>> FreeBSD 10.0-CURRENT #5: Thu Feb  9 13:18:22 UTC 2012
>> CPU: Pentium Pro (198.95-MHz 686-class CPU)
>>   Origin = "GenuineIntel"  Id = 0x616  Family = 6  Model = 1  Stepping = 6
>>   Features=0xf9ff
>> real memory  = 134217728 (128 MB)
>> avail memory = 120471552 (114 MB)
> 
> Interesting, that is odd to get an error with no error code.
> 
> Can you tell from the stack trace if your CPU actually raised a machine check 
> exception (trap 28)?

I tested with debugger enabled kernel.
Please get from:
http://home.jp.freebsd.org/~nyan/mca-error1.jpg
http://home.jp.freebsd.org/~nyan/mca-error2.jpg
(Sorry for jpeg images)

---
TAKAHASHI Yoshihiro 
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: loader is aborted with 'out of memory'

2012-02-14 Thread TAKAHASHI Yoshihiro

In article <4f393b95.7070...@gmail.com>
Chuck Burns  writes:

> On 2/13/2012 7:06 AM, TAKAHASHI Yoshihiro wrote:
>> I got the following error of the current loader if I put the xxx_after
>> line into loader.conf to wait a key after load the xxx module.
>>
>> ---
>> Error: out of memory
>> Module xxx
>> Error executing read -p "Press Enter"
>> Aborted!
>> ---
>>
>> The loader.conf is:
>> xxx_load="YES"
>> xxx_after="read -p \"Press Enter\""
>>
>> Does anyone know what is wrong?
>>
> Uhm, yea.. it's having trouble executing the command 'read -p "Press
> Enter"'
> 
> My guess is, it can't run that command "read". Perhaps it needs a full
> path, or something? grasping at straws on the fix you want, but the
> error message is pretty clear..  and without the _after line I'm
> betting it would boot fine.

What I'd like to do is making boot and mfsroot floppy images to install
for pc98.  So I want to fix this problem.

If I tested the loader image on current with the forth scripts on 8.x,
the _before and _after work fine.

---
TAKAHASHI Yoshihiro 
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Mesa 8.0 Info

2012-02-14 Thread vehemens

On Monday 13 February 2012 13:57:12 Pietro Cerutti wrote:
> On 2012-Feb-13, 00:34, vehemens wrote:
> >  >8e1c9c163ed2b91bc>
>
> FWIW, I'm going to update graphics/libosmesa within the next few days.

A long as you account for removed changes such as "300c, r600c: Remove these 
DRI drivers.", you should be fine.


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Does anyone regularly build HEAD with clang?

2012-02-14 Thread Jordan K. Hubbard

On Feb 13, 2012, at 9:09 AM, Niclas Zeising wrote:

> The ML ate the attachments. Either attach them as text/plain or post
> them online somewhere.

Well, Brandon Falk actually appears to have nailed the root cause.  I followed 
older instructions on http://wiki.freebsd.org/BuildingFreeBSDWithClang which 
said to set CPP="clang -E" and this has been updated to "clang-cpp", which I 
didn't realize it.  Once I made that change in make.conf, everything is 
proceeding perfectly!  It's on a slow atom box so my "make world kernel" hasn't 
actually completed yet, but I think it's gone far enough that I can assume 
success!

Sorry for the stale build settings which led to a false alarm on my part, and 
thanks to Brandon for replying off-list with the solution!

- Jordan

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Enhancing the user experience with tcsh

2012-02-14 Thread timp

My diff:
+set autolist

-setenv PAGER   more
+setenv PAGER   less

 if ($?prompt) then
# An interactive shell -- set some stuff up
+   set promptchars = '$#'
+   set prompt = "%{^[[50;73;1m%}\[`whoami`@%m %~\]%#%{^[[m%} "


I think 'set autolist' must have everyone.
PAGER is not necessary.
And this is best prompt I think =)

--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Enhancing-the-user-experience-with-tcsh-tp5471144p5481784.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Enhancing the user experience with tcsh

2012-02-14 Thread Eitan Adler

On Tue, Feb 14, 2012 at 8:19 AM, Astrodog  wrote:
> Personally, I pay very little attention to the prompt. That being said...
> Plenty of people prefer widely different configurations for the prompt.
> I think everyone agrees that the default prompt isn't particularly
> informative, however, achieving consensus here is going to be almost
> impossible. I suggest that it be handled as a seperate discussion,
> perhaps?

That would result in even more of a bikeshed than this thread. I'm
pretty sure I'm going to go with one of the prompts posted to this
thread after a bit of experimentation.
Remember that the prompts are for inexperienced users and those of you
with awesome prompts are not the target audience for the change.

> I am against this change, barring a more compelling reason to include
> it. Default behavior limits $PATH to areas that are only writable as
> root, and there is no garuntee that $HOME can only be written by the
> user. As a result, the change may create unanticipated and unnoticed
> security consequences some installations. I believe this outweighs the
> functionality provided by the proposed change, given how trivial this
> is to configure after the fact.

 set path = (/sbin /bin /usr/sbin /usr/bin /usr/games /usr/local/sbin
/usr/local/bin $HOME/bin)

is the default


-- 
Eitan Adler
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Enhancing the user experience with tcsh

2012-02-14 Thread Astrodog

On Tue, Feb 14, 2012 at 7:26 AM, Eitan Adler  wrote:
> On Tue, Feb 14, 2012 at 8:19 AM, Astrodog  wrote:
>> Personally, I pay very little attention to the prompt. That being said...
>> Plenty of people prefer widely different configurations for the prompt.
>> I think everyone agrees that the default prompt isn't particularly
>> informative, however, achieving consensus here is going to be almost
>> impossible. I suggest that it be handled as a seperate discussion,
>> perhaps?
>
> That would result in even more of a bikeshed than this thread. I'm
> pretty sure I'm going to go with one of the prompts posted to this
> thread after a bit of experimentation.
> Remember that the prompts are for inexperienced users and those of you
> with awesome prompts are not the target audience for the change.

I'm not actually against any of the prompts that have been suggested.
They're all fine with me. I use too many shared machines, or use
machines temporarly to expect anything at all from the prompt anyway.

>
>> I am against this change, barring a more compelling reason to include
>> it. Default behavior limits $PATH to areas that are only writable as
>> root, and there is no garuntee that $HOME can only be written by the
>> user. As a result, the change may create unanticipated and unnoticed
>> security consequences some installations. I believe this outweighs the
>> functionality provided by the proposed change, given how trivial this
>> is to configure after the fact.
>
>  set path = (/sbin /bin /usr/sbin /usr/bin /usr/games /usr/local/sbin
> /usr/local/bin $HOME/bin)
>
> is the default
>

Whoops. I should have known a couple of years ago that adding a
handful of random patches to my build machine wasn't a great idea.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Enhancing the user experience with tcsh

2012-02-14 Thread Ivan Voras

On 10/02/2012 17:25, Eitan Adler wrote:

>  setenv BLOCKSIZE   K

Why note BLOCKSIZE M? It's pretty much ridiculous to count kilobytes
nowadays.

> Many people had alternative suggestions for the prompt. Can you please
> clarify why you believe your prompt should be the _default_ one?

My prompt suggestion:

set prompt="%U%m%u:%B%~%b%# "

It makes the prompt lines clearly and loudly visible in a screen full of
busy commands.

signature.asc
Description: OpenPGP digital signature

Re: Enhancing the user experience with tcsh

2012-02-14 Thread Astrodog

... snip ...

>  if ($?prompt) then
>   # An interactive shell -- set some stuff up
> -   set prompt = "`/bin/hostname -s`# "
> +   set prompt = "[%n@%m]%c04%# "
> +   set promptchars = "%#"
>
> Many people had alternative suggestions for the prompt. Can you please
> clarify why you believe your prompt should be the _default_ one?
> While many admins are able to deal with short non-descriptive prompts
> it helps new users to have more detail on the prompt line. I'd like to
> commit some change to the default: currently it is very undescriptive.
> I am leaving open which prompt I am going with at the end though.

Personally, I pay very little attention to the prompt. That being said...
Plenty of people prefer widely different configurations for the prompt.
I think everyone agrees that the default prompt isn't particularly
informative, however, achieving consensus here is going to be almost
impossible. I suggest that it be handled as a seperate discussion,
perhaps?

>
>   set filec
> -   set history = 100
> -   set savehist = 100
> +   set history = 1
> +   set savehist = 1
>
> No one complained about this one - it is almost certainly going to
> stay it the final version.
>
> +   set autolist
>
> set autolist=ambiguous makes sense here - I will likely go with that.
>
> +   # Use history to aid expansion
> +   set autoexpand
>
> No one complained about this  - it is almost certainly going to stay
> it the final version.
>
> Now to address some comments made in the thread. I'm sorry for not
> preserving attribution here.
>
>> How about adding stuff like this to /usr/share/examples/tcsh/complete.tcsh ?
>> Along with a comment in .cshrc pointing to that file (or even a commented 
>> line to source it), it would be an improvement.
>
> +1 I'll add a comment addressing this file.
>
>> I use the $HOME/bin on my machines but I am not so sure to make this a 
>> general thing.
>
> Many people expect it, and given that it is the last item in the path
> it won't affect all that much.

I am against this change, barring a more compelling reason to include
it. Default behavior limits $PATH to areas that are only writable as
root, and there is no garuntee that $HOME can only be written by the
user. As a result, the change may create unanticipated and unnoticed
security consequences some installations. I believe this outweighs the
functionality provided by the proposed change, given how trivial this
is to configure after the fact.

... snip ...

These two issues aside, I do like the idea here. Here's hoping it
doesn't collapse under thousands of coats of paint.

--- Harrison
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

88 matches

Mail list logo