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

Thread: TW 20170913 prevent my intel graphic work

  1. #1
    Join Date
    Jun 2015
    Location
    Toulouse
    Posts
    133

    Default TW 20170913 prevent my intel graphic work

    Hello :-)

    Until today, my old dell mini 10 worked perfectly with tumbleweed 32 bits.

    I updated it (zypper up) to TW 20170913 and now it do not start anymore: the screen is blurred, I'm not even sure it started X, because adding "3" on the grub linux line do not gives the init 3 start.

    adding "nomodeset" allows me to start.

    video is intel 945GSE and seems to be seen in X logs

    any hint?

    thanks
    jdd

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,795

    Default Re: TW 20170913 prevent my intel graphic work

    I have no idea if it has anything to do with your problem, but Tumbleweed should be updated using
    Code:
    zypper dup
    and not zypper up.
    Henk van Velden

  3. #3
    Join Date
    Jun 2015
    Location
    Toulouse
    Posts
    133

    Default Re: TW 20170913 prevent my intel graphic work

    Quote Originally Posted by hcvv View Post
    I have no idea if it has anything to do with your problem, but Tumbleweed should be updated using
    Code:
    zypper dup
    and not zypper up.
    I have often seen discussions about this, with usually opposite results (that is each discussion opposit from the previous).

    But I just try it, with as first result than packman apps are pulled from opensuse, so I will need a zypper dup --from "Packman Repository"

    As it's running, I will report after it done

    thanks
    jdd

  4. #4
    Join Date
    Jun 2015
    Location
    Toulouse
    Posts
    133

    Default Re: TW 20170913 prevent my intel graphic work

    well... no change

    a zypper dup did not make any good (nor any more bad...)

    it's too late today to test anymore

    thanks
    jdd

  5. #5
    Join Date
    Sep 2008
    Posts
    2,997

    Default Re: TW 20170913 prevent my intel graphic work

    maybe a package mixup from a 3rd party repo what's your repo list
    Code:
    zypper lr -d
    the proper way to upgrade TW after you've added and done a vendor change to packman is
    Code:
    zypper dup --no-allow-vendor-change

  6. #6
    Join Date
    Nov 2013
    Location
    Kamloops, BC, Canada
    Posts
    4,029

    Default Re: TW 20170913 prevent my intel graphic work

    Quote Originally Posted by jdd View Post
    I have often seen discussions about this, with usually opposite results (that is each discussion opposit from the previous).
    ... you may not have understood those discussions, because it is, for a long time
    Code:
    zypper dup
    for Tumbleweed.

    ... and that has never changed.
    "Take a Walk on a Sunny Day, Greet everyone along the way, and Make Somebody Smile, Today"
    Gerry Jack Macks"Walk On A Sunny Day" GerryJackMacks.net

  7. #7
    Join Date
    Jun 2015
    Location
    Toulouse
    Posts
    133

    Default Re: TW 20170913 prevent my intel graphic work

    Quote Originally Posted by Fraser_Bell View Post
    ... you may not have understood those discussions, because it is, for a long time
    Code:
    zypper dup
    for Tumbleweed.

    ... and that has never changed.
    so Richard Brown is wrong?

    https://lists.opensuse.org/opensuse-.../msg00341.html

    jdd

  8. #8
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,704
    Blog Entries
    1

    Default Re: TW 20170913 prevent my intel graphic work

    Quote Originally Posted by jdd View Post
    Well, more recently he wrote
    https://lists.opensuse.org/opensuse-.../msg00243.html
    zypper up is a partial solution, as it doesn't allow packages to
    change their repos (aka vendor change), but has its own flaws, as it
    is often too conservative and doesn't tidy up after itself. This can
    lead to old packages lying around after they've been dropped from TW
    or your OBS repos, leading to weird dependency chains of old packages
    lurking around when you should have actually upgraded them all.

    this also leads to weird breakages and odd behaviour.

    "zypper dup --now-allow-vendor-change" forces zypper dup to use the
    most important feature of zypper up "keep using the packages from the
    same repositories from which I installed them from". But otherwise
    preserves all the usual zypper dup behaviour of ensuring you have a
    complete, consistent, tumbleweed installation based on what packages
    are, or are no longer, in our repositories.

    This avoids the issues with 'zypper up' leaving 'cruft', prevents the
    problem described in 2), and does the best job possible to mitigate
    the problems described in 1) - but of course you're still at the mercy
    of whatever maintainers do in their OBS repos, and they do not benefit
    from the review, integration work, and testing which the main
    repositories benefit from.

    Hope this helps,
    R

  9. #9
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,704
    Blog Entries
    1

    Default Re: TW 20170913 prevent my intel graphic work

    The proper way to update (effectively upgrade) TW....

    https://lwn.net/Articles/717489/

  10. #10
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,704
    Blog Entries
    1

    Default Re: TW 20170913 prevent my intel graphic work

    ....and here...
    https://en.opensuse.org/Portal:Tumbleweed

    Follow the opensuse-factory mailing list to get notified about updates. New snapshots are released as often as they are ready and automatic QA has passed. This can be as often as daily but sometimes also takes a few weeks, when bigger changes are integrated. (Note that there can be some subtleties with updates, especially with multiple repositories. See for example recent discussion about using zypper dup versus zypper up)
    Once you are running Tumbleweed to get updates every time a new snapshot has been released enter the following command as root (ideally inside a screen session):
    Code:
    zypper dup --no-allow-vendor-change
    A recent libzypp update meant that /etc/zypp/zypp.conf was changed so that for most TW users running 'zypper dup' will default to inhibiting vendor changes as documented here
    https://bugzilla.suse.com/show_bug.cgi?id=1031756

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
  •