By: Linus Torvalds (torvalds.delete@this.linux-foundation.org), January 4, 2011 11:53 am
Room: Moderated Discussions
David Kanter (dkanter@realworldtech.com) on 1/3/11 wrote:
>
>Can anyone with perhaps more direct experience with Linux graphics comment on the
>issues here? It seems like this is relatively benign, given that products aren't
>on sale yet. Even if the release lags by a few days, it shouldn't be a huge issue...
The problem is that it's not looking like "a few days".
Because all the distros are using stable versions from
several months ago (or more), it really doesn't help that
the support "exists" in newer source trees.
So I have a SB system, and it works, but it was annoying
to actually get working. This is the "hard core" way of
doing it:
- install a distro using "safe video" (slow, VESA) from
a DVD with full development environment
- compile a new kernel just to get support for networking
(which the distro kernel likely doesn't support either,
because it's been in the mainline kernel for only six
months).
Because networking doesn't work, use a USB stick to get
the kernel source tree over.
- compile support for intel graphics while you're at it,
but disable it at runtime by using "nomodeset", because
otherwise your VESA-based safe graphics setup won't be
working when you reboot.
- install the kernel, reboot. You now have networking,
which makes the following steps much easier..
- upgrade the distro to the latest version.
- curse, because it still doesn't actually have the X
support for sandybridge graphics
- compile your own version of "libdrm" and the intel
graphics driver (which involves things like setting
PKG_CONFIG_PATH by hand to let the thing know that
you have your private drivers in magic places)
- tell X to use the new driver module, and now you can
boot with the kernel mode setting enabled.
That's to get just basic graphics working. But it won't
actually get you any real 3D accelerated graphics, because
all the system libraries are still the old ones that don't
know how to do 3D on sandybridge (the above just does the
core X graphics driver itself).
In short: if you're happy building a lot of stuff yourself,
you can certainly do it. It's not hard, it's just annoying.
And you do have to know how to avoid the problems that crop
up before you've installed the new versions (which I guess
does count as "hard").
And if you actually want to do any real work instead of
messing around with these bits, wait for the distros to
support it.
Today, I think you can do the Ubuntu 11.04 alpha ("Natty
Narwhal"), and you'll have working graphics and networking.
Probably more reasonable than the above games that I went
through. Get the "daily build", since you're pretty bleeding
edge anyway, so you might as well be as recent as possible.
But the actual release schedule for those distros are not
"a few days". They're more like "April 2011". Before that,
you'll have to find things like daily builds or do your
own.
(Of course, I do hope that most distros end up backporting
the drivers to their stable repository before that. So it
may be a bit better than the above fairly soon, as people
start buying the new hardware)
Linus
>
>Can anyone with perhaps more direct experience with Linux graphics comment on the
>issues here? It seems like this is relatively benign, given that products aren't
>on sale yet. Even if the release lags by a few days, it shouldn't be a huge issue...
The problem is that it's not looking like "a few days".
Because all the distros are using stable versions from
several months ago (or more), it really doesn't help that
the support "exists" in newer source trees.
So I have a SB system, and it works, but it was annoying
to actually get working. This is the "hard core" way of
doing it:
- install a distro using "safe video" (slow, VESA) from
a DVD with full development environment
- compile a new kernel just to get support for networking
(which the distro kernel likely doesn't support either,
because it's been in the mainline kernel for only six
months).
Because networking doesn't work, use a USB stick to get
the kernel source tree over.
- compile support for intel graphics while you're at it,
but disable it at runtime by using "nomodeset", because
otherwise your VESA-based safe graphics setup won't be
working when you reboot.
- install the kernel, reboot. You now have networking,
which makes the following steps much easier..
- upgrade the distro to the latest version.
- curse, because it still doesn't actually have the X
support for sandybridge graphics
- compile your own version of "libdrm" and the intel
graphics driver (which involves things like setting
PKG_CONFIG_PATH by hand to let the thing know that
you have your private drivers in magic places)
- tell X to use the new driver module, and now you can
boot with the kernel mode setting enabled.
That's to get just basic graphics working. But it won't
actually get you any real 3D accelerated graphics, because
all the system libraries are still the old ones that don't
know how to do 3D on sandybridge (the above just does the
core X graphics driver itself).
In short: if you're happy building a lot of stuff yourself,
you can certainly do it. It's not hard, it's just annoying.
And you do have to know how to avoid the problems that crop
up before you've installed the new versions (which I guess
does count as "hard").
And if you actually want to do any real work instead of
messing around with these bits, wait for the distros to
support it.
Today, I think you can do the Ubuntu 11.04 alpha ("Natty
Narwhal"), and you'll have working graphics and networking.
Probably more reasonable than the above games that I went
through. Get the "daily build", since you're pretty bleeding
edge anyway, so you might as well be as recent as possible.
But the actual release schedule for those distros are not
"a few days". They're more like "April 2011". Before that,
you'll have to find things like daily builds or do your
own.
(Of course, I do hope that most distros end up backporting
the drivers to their stable repository before that. So it
may be a bit better than the above fairly soon, as people
start buying the new hardware)
Linus
Topic | Posted By | Date |
---|---|---|
Sandy Bridge Reviews | David Kanter | 2011/01/03 12:00 AM |
Sandy Bridge Reviews | Michael S | 2011/01/03 03:11 AM |
VS2008 compilation test | Michael S | 2011/01/03 03:39 AM |
VS2008 compilation test | ajensen | 2011/01/03 05:44 AM |
VS2008 compilation test | IntelUser2000 | 2011/01/03 06:24 AM |
Sandy Bridge Reviews | Carlie Coats | 2011/01/03 10:41 AM |
Sandy Bridge Reviews | Linus Torvalds | 2011/01/03 11:00 AM |
Sandy Bridge Reviews | Carlie Coats | 2011/01/03 11:30 AM |
Sandy Bridge Reviews | Anon | 2011/01/03 03:55 PM |
Sandy Bridge Reviews | a reader | 2011/01/03 05:34 PM |
Sandy Bridge Reviews | Linus Torvalds | 2011/01/03 06:11 PM |
Sandy Bridge Reviews | Aaron Spink | 2011/01/04 01:56 PM |
Sandy Bridge Reviews | EduardoS | 2011/01/04 02:38 PM |
Sandy Bridge Reviews | Azazel | 2011/01/10 01:27 AM |
Sandy Bridge Reviews | Steve Underwood | 2011/01/10 04:28 AM |
Sandy Bridge Reviews | Antti-Ville Tuunainen | 2011/01/10 05:56 AM |
Sandy Bridge Reviews | Anon | 2011/01/10 08:19 PM |
Sandy Bridge Reviews | someone | 2011/01/11 11:26 AM |
Sandy Bridge Reviews | Groo | 2011/01/11 01:08 PM |
Sandy Bridge Reviews | Linus Torvalds | 2011/01/11 04:25 PM |
Sandy Bridge Reviews | Aaron Spink | 2011/01/04 01:54 PM |
Sandy Bridge Reviews | Azazel | 2011/01/10 01:32 AM |
Sandy Bridge Reviews | Eric Bron | 2011/01/03 12:17 PM |
Sandy Bridge Reviews | Carlie Coats | 2011/01/03 01:03 PM |
Sandy Bridge Reviews | Michael S | 2011/01/03 01:18 PM |
Sandy Bridge Reviews | anon | 2011/01/04 02:03 AM |
Sandy Bridge Reviews | Michael S | 2011/01/04 03:12 AM |
Sandy Bridge Reviews | Carlie Coats | 2011/01/04 06:33 AM |
Sandy Bridge Reviews | Eric Bron | 2011/01/05 01:39 AM |
Sandy Bridge Reviews | Michael S | 2011/01/05 08:10 AM |
Sandy Bridge Reviews | Eric Bron | 2011/01/05 12:01 PM |
Sandy Bridge Reviews | Michael S | 2011/01/05 03:59 PM |
Sandy Bridge Reviews | MS | 2011/01/06 09:53 AM |
Sandy Bridge Reviews | Michael S | 2011/01/06 10:35 AM |
Sandy Bridge Reviews | MS | 2011/01/06 11:32 AM |
Sandy Bridge Reviews | EduardoS | 2011/01/05 12:57 PM |
Sandy Bridge Reviews | Michael S | 2011/01/05 03:57 PM |
Sandy Bridge Reviews | EduardoS | 2011/01/06 01:31 PM |
Sandy Bridge GPU and Linux support | David Kanter | 2011/01/03 09:07 PM |
Sandy Bridge GPU and Linux support | Jack | 2011/01/03 10:05 PM |
Sandy Bridge GPU and Linux support | Wes Felter | 2011/01/03 10:22 PM |
Sandy Bridge GPU and Linux support | anon | 2011/01/04 01:37 AM |
Sandy Bridge GPU and Linux support | David Kanter | 2011/01/04 03:33 AM |
Sandy Bridge GPU and Linux support | anon | 2011/01/04 05:29 AM |
Sandy Bridge GPU and Linux support | David Kanter | 2011/01/04 05:45 AM |
Sandy Bridge GPU and Linux support | Groo | 2011/01/08 10:57 PM |
Sandy Bridge GPU and Linux support | Michael S | 2011/01/09 05:44 AM |
Sandy Bridge GPU and Linux support | Foo_ | 2011/01/09 07:22 AM |
Sandy Bridge GPU and Linux support | Eric Bron | 2011/01/04 04:20 AM |
Sandy Bridge GPU and Linux support | Rohit | 2011/01/04 07:08 AM |
Sandy Bridge GPU and Linux support | Linus Torvalds | 2011/01/04 11:53 AM |
Sandy Bridge GPU and Linux support | Aaron Spink | 2011/01/04 01:48 PM |
Sandy Bridge GPU and Linux support | Linus Torvalds | 2011/01/04 03:23 PM |
Sandy Bridge GPU and Linux support | Paul | 2011/01/04 03:44 PM |
Sandy Bridge GPU and Linux support | Rob Thorpe | 2011/01/04 06:20 PM |
Sandy Bridge GPU and Linux support | Groo | 2011/01/08 11:09 PM |
Sandy Bridge GPU and Linux support | Paul D | 2011/01/08 08:12 AM |
Sandy Bridge GPU and Linux support | Foo_ | 2011/01/08 02:27 PM |
What were you expecting from the Michael Moore of the IT net press? (NT) | Nikolas | 2011/01/05 02:33 AM |
Blame nVidia? | Mark Roulo | 2011/01/05 09:31 AM |