Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: Manual rebuilding of proprietary graphic drivers?

  1. #1

    Default Manual rebuilding of proprietary graphic drivers?

    I'm new to Opensuse, coming over from Kubuntu. While looking around at things, I came across the Tumbleweed portal, which sounds like something I'd like to follow. It worries me though, that the first topic I see is entitled Who should try Tumbleweed?, where it states "Due to the Linux kernel being updated very frequently, users who rely on proprietary graphic drivers should not use the Tumbleweed repository unless they are familiar with updating these drivers from source on their own." Are you seriously telling me that if I update the kernel, I'll have to rebuild the graphic drivers manually? I can't recall the last time I had to do that. I installed Nvidas drivers because the system was unusable after the first reboot without them. I've never really cared for the nv drivers and would have done it anyway. I've always used the official Nvidia drivers. What about VirtualBox? I installed dkms while installing that, will that work for VB and the Nvidia drivers, or just VB, or neither? Am I going to have to freeze my kernel to keep from breaking my system on an update?

  2. #2
    dd@home.dk NNTP User

    Default Re: Manual rebuilding of proprietary graphic drivers?

    On 09/10/2012 11:06 AM, suseconvert wrote:
    > Are you seriously telling me that if I update the kernel,
    > I'll have to rebuild the graphic drivers manually?


    do it the way you wish....but, i'd recommend a good backup.

    and, if you run into a black screen after a kernel change, you can
    search the forums here and learn why it happened and how to once again
    have the driver match the kernel..

    --
    dd http://goo.gl/PUjnL


  3. #3
    Join Date
    Oct 2008
    Location
    Glasgow, Scotland
    Posts
    1,130

    Default Re: Manual rebuilding of proprietary graphic drivers?

    Tumbleweed is intended to be in constant flux, but should be less unpredictable than Factory. If you want to use the Nvidia drivers, then you will have use a kernel that is supported by Nvidia. This generally means not using the latest stable kernel, never mind anything newer. The only alternative is to build your own. (You might be better using a non-Free friendly Gentoo-based distribution such as SabayonLinux. ) Dkms cannot help with closed-source code. Nv drivers are very old; the Free drvers for Nvidia chips are called nouveau.

    As for VirtualBox, that depends on whether you use a Free version from the SuSE Build Service (openSuSE repositories), or download from Oracle. If the latter you will have to reinstall the rpm whenever you change the kernel version.

    You cannot really compare using a well-defined stable system intended for beginners with a proprietary mind-set, with a bleeding-edge experimental system.

  4. #4
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: Manual rebuilding of proprietary graphic drivers?

    Am 10.09.2012 11:06, schrieb suseconvert:
    > What about VirtualBox? I
    > installed dkms while installing that, will that work for VB and the
    > Nvidia drivers, or just VB, or neither?


    If you installed the rpm directly from www.virtualbox.org the dkms will
    take care for you to keep the vbox kernel modules synced with your
    kernel, it works for me.
    For nvidia you have to recompile if you use Tumbleweed, the rpm's are
    just for the standard openSUSE versions (which is what I use), so for
    11.4, 12.1, 12.2 you never have to compile the driver and the rpm system
    handles it for you.

    In principle the nvidia kernel module can also be done with dkms, Mageia
    does it. When I find some time (probably not even this month) I will
    look up how they do it and try to apply that to an openSUSE system.

    You could open a thread about "Proprietary nvidia driver with dkms" or
    something similar to get the attention of people who probably know how
    to do that if this thread is not attractive enough for them to look into
    and maybe you should post that then to the Tumbleweed forum where the
    users are.
    But wait a bit who else comments here.

    --
    PC: oS 12.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
    ThinkPad E320: oS 12.2 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
    eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10

  5. #5
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: Manual rebuilding of proprietary graphic drivers?

    If you are experienced enough you can try to transfer that howto from
    ubuntu to your openSUSE system
    http://ubuntuforums.org/showthread.php?t=1036788

    --
    PC: oS 12.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
    ThinkPad E320: oS 12.2 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
    eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10

  6. #6
    Join Date
    Mar 2008
    Location
    Oz
    Posts
    11,727
    Blog Entries
    2

    Default Re: Manual rebuilding of proprietary graphic drivers?

    On 09/10/2012 07:06 PM, suseconvert wrote:
    >
    > I'm new to Opensuse, coming over from Kubuntu. While looking around at
    > things, I came across the 'Tumbleweed portal'
    > (http://en.opensuse.org/Portal:Tumbleweed), which sounds like something
    > I'd like to follow. It worries me though, that the first topic I see is
    > entitled *Who should try Tumbleweed?*, where it states "-Due to the
    > Linux kernel being updated very frequently, users who rely on
    > proprietary graphic drivers should not use the Tumbleweed repository
    > unless they are familiar with updating these drivers from source on
    > their own.-" Are you seriously telling me that if I update the kernel,
    > I'll have to rebuild the graphic drivers manually? I can't recall the
    > last time I had to do that. I installed Nvidas drivers because the
    > system was unusable after the first reboot without them. I've never
    > really cared for the nv drivers and would have done it anyway. I've
    > always used the official Nvidia drivers. What about VirtualBox? I
    > installed dkms while installing that, will that work for VB and the
    > Nvidia drivers, or just VB, or neither? Am I going to have to freeze my
    > kernel to keep from breaking my system on an update?
    >
    >


    I have tumbleweed with nvidia and VBox. I haven't had significant
    problems with either of them in Tumbleweed. With each kernel update I
    have to reboot and run one script to get Nvidia reset and one command to
    get VBox reset. After you do it once, it's almost trivial housekeeping.
    There are HowTos for both nvidia and VBox in Tumbleweed.

    --
    Regards
    swerdna

  7. #7
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: Manual rebuilding of proprietary graphic drivers?

    Am 10.09.2012 14:45, schrieb swerdna:
    > I have tumbleweed with nvidia and VBox. I haven't had significant
    > problems with either of them in Tumbleweed. With each kernel update I
    > have to reboot and run one script to get Nvidia reset and one command to
    > get VBox reset. After you do it once, it's almost trivial housekeeping.
    > There are HowTos for both nvidia and VBox in Tumbleweed.
    >

    Swerdna, do you really need every time to trigger VBox manually to be
    compatible with the kernel on TW?
    I have on my office notebook 12.1 64bit but with the kernel from
    kernel:stable (3.5) and every time there is a kernel update I can see
    VBox running its rebuild itself via dkms automatically without me doing
    anything about that and it works afterwards. I wonder if that does not
    work for TW?
    I use the rpm directly from http://www.virtualbox.org

    --
    PC: oS 12.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
    ThinkPad E320: oS 12.2 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
    eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10

  8. #8
    Join Date
    Oct 2008
    Location
    Glasgow, Scotland
    Posts
    1,130

    Default Re: Manual rebuilding of proprietary graphic drivers?

    If you installed the rpm directly from www.virtualbox.org the dkms will take care for you to keep the vbox kernel modules synced with your kernel, it works for me.
    I must be doing something wrong. I have dkms-2.1.1.2 from Packman. It appears to modify the vbox kernel modules, but I cannot use VBoxManage or the VirtualBo GUI without e.g. rpm -Uvh --force VirtualBox-4.1-4.1.22_80657_openSUSE114-1.x86_64.rpm after booting a new kernel.

    rayH

  9. #9
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: Manual rebuilding of proprietary graphic drivers?

    Am 10.09.2012 15:06, schrieb eng-int:
    > I must be doing something wrong. I have -dkms-2.1.1.2- from Packman.
    > It appears to modify the vbox kernel modules, but I cannot use
    > VBoxManage or the VirtualBo GUI without e.g. - rpm -Uvh --force
    > VirtualBox-4.1-4.1.22_80657_openSUSE114-1.x86_64.rpm- after booting a
    > new kernel.


    I have no need to do that, but have an older VBox version on my 12.1 machine
    Code:
    martinh@pyxis:~> rpm -qa '*VirtualBox*'
    VirtualBox-4.1-4.1.18_78361_openSUSE114-1.x86_64
    I am willing to update that tonight and give you feedback how it works
    for me with 4.1.22.

    --
    PC: oS 12.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
    ThinkPad E320: oS 12.2 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
    eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10

  10. #10
    Join Date
    Oct 2008
    Location
    Glasgow, Scotland
    Posts
    1,130

    Default Re: Manual rebuilding of proprietary graphic drivers?

    >> rpm -Uvh --force VirtualBox-4.1-4.1.22_80657_openSUSE114-1.x86_64.rpm
    > I have no need to do that, but have an older VBox version on my 12.1 machine

    That was just an "e.g.". I am actually running on production (headless):

    openSuSE-11.4, kernel-default-2.6.37.6-0.20.1.x86_64, VirtualBox-4.1-4.1.18_78361_openSUSE114-1.x86_64

    and on this test machine (KDE-4.9.1):

    openSuSE-12.2, kernel-desktop-3.5.3-1.1.x86_64, VirtualBox-4.1-4.1.20_80170_openSUSE114-1.x86_64

    Now that I know how dkms should work, I will play around with it, but it might have to wait until the weekend.

    thanks,
    rayH

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •