Re: [gentoo-user] Problem with dosbox and latest Nvidia driver plus xorg
On Tue, Nov 20, 2012 at 03:50:25PM -0500, Walter Dnes wrote > > My first instinct was to revert from nvidia-drivers-304.64 back to > nvidia-drivers-295.71. However, that would also force a downgrade from > x11-base/xorg-server-1.13.0-r1 to x11-base/xorg-server-1.12.4, which I > am reluctant to do. Anybody have any ideas for a better solution? I also tried keywording and installing nvidia-drivers-310.19. No change at all. -- Walter Dnes We are apparently better off trying to avoid udev like the plague. Linus Torvalds; 2012/10/03 https://lkml.org/lkml/2012/10/3/349
Re: [gentoo-user] Kernel 3.6: No external Monitor
Am 20.11.2012 21:35, schrieb Norman Rieß: > Am 20.11.2012 20:08, schrieb Damien Levac: >> On 11/20/12 13:33, Norman Rieß wrote: >>> Am 20.11.2012 19:02, schrieb Florian Philipp: Am 20.11.2012 14:52, schrieb Norman Rieß: > Am 20.11.2012 13:51, schrieb Bruce Hill: >> On Tue, Nov 20, 2012 at 08:44:08AM +0100, Norman Rieß wrote: >>> Hello, >>> >>> i am using a Thinkpad X301 with a DVI Monitor connected to the mini >>> displayport. >>> That worked perfectly for years, but with Kernel 3.6 (and 3.7rc) the DVI >>> Monitor stays black on boot and it is not visible in xrandr. As if it >>> wasn't connected at all. [...] What does `xrandr --current` say? (from x11-apps/xrandr) >>> In what situation? 3.5 or 3.6 kernel? >>> >> In doubt, both. But I'm fairly sure he meant 3.6 since there are no >> problem to solve in 3.5. :P >> > > Yeah, i was kinda irritated by that question, as i allready said, that > xrandr does not show the display. [...] Sorry, missed that part. Can you try without KMS? http://wiki.debian.org/KernelModesetting Regards, Florian Philipp signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] OpenRC update to 0.11.5 - safe if using older udev (pinned to udev-181)?
On Tue, Nov 20, 2012 at 02:17:17PM -0500, Tanstaafl wrote: Hey, should be no worries now ... openrc-0.11.5 got moved to stable today, so it should work fine with >=sys-fs/udev-181 (stable udev atm). -- Happy Penguin Computers >') 126 Fenco Drive ( \ Tupelo, MS 38801 ^^ supp...@happypenguincomputers.com 662-269-2706 662-205-6424 http://happypenguincomputers.com/ Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
Re: [gentoo-user] Kernel 3.6: No external Monitor
On 11/20/12 15:35, Norman Rieß wrote: > Am 20.11.2012 20:08, schrieb Damien Levac: >> On 11/20/12 13:33, Norman Rieß wrote: >>> Am 20.11.2012 19:02, schrieb Florian Philipp: Am 20.11.2012 14:52, schrieb Norman Rieß: > Am 20.11.2012 13:51, schrieb Bruce Hill: >> On Tue, Nov 20, 2012 at 08:44:08AM +0100, Norman Rieß wrote: >>> Hello, >>> >>> i am using a Thinkpad X301 with a DVI Monitor connected to the mini >>> displayport. >>> That worked perfectly for years, but with Kernel 3.6 (and 3.7rc) the DVI >>> Monitor stays black on boot and it is not visible in xrandr. As if it >>> wasn't connected at all. >>> Rebooting with 3.5 brings back the Display with full functionality. >>> >>> All i found about this was a Fedora bugreport stating the issue, but is >>> unanswered for a month now. >>> >>> Does someone got an idea here or faced the same issue and solved it? >>> >>> Regards, >>> Norman >> Can you give us a link to: >> >> (1) the Fedora bug report >> (2) your 3.5 kernel .config >> (3) your 3.6 (and 3.7rc) kernel .config(s) >> > Yes. > (1) https://bugzilla.redhat.com/show_bug.cgi?id=869824 > > (2) http://smash-net.org/temp/config-3.5.4 > (3) http://smash-net.org/temp/config-3.6.6 > http://smash-net.org/temp/config-3.7.0-rc6 > > > What does `xrandr --current` say? (from x11-apps/xrandr) Regards, Florian Philipp >>> In what situation? 3.5 or 3.6 kernel? >>> >> In doubt, both. But I'm fairly sure he meant 3.6 since there are no >> problem to solve in 3.5. :P >> >> Damien >> > Yeah, i was kinda irritated by that question, as i allready said, that > xrandr does not show the display. > 3.5 activates the display during kernel loading, on 3.6 it stays shut > off during the whole boot process. > > > 3.6: > xrandr --current > Screen 0: minimum 320 x 200, current 1440 x 900, maximum 32767 x 32767 > LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis) > 287mm x 180mm >1440x900 60.0*+ 50.0 >1024x768 60.0 >800x60060.3 56.2 >640x48059.9 > VGA1 disconnected (normal left inverted right x axis y axis) > HDMI1 disconnected (normal left inverted right x axis y axis) > DP1 disconnected (normal left inverted right x axis y axis) > DP2 disconnected (normal left inverted right x axis y axis) > > - > 3.5 both screens mirrored: > xrandr --current > Screen 0: minimum 320 x 200, current 1440 x 900, maximum 32767 x 32767 > LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis) > 287mm x 180mm >1440x900 60.0*+ 50.0 >1024x768 60.0 >800x60060.3 56.2 >640x48059.9 > VGA1 disconnected (normal left inverted right x axis y axis) > HDMI1 connected 1440x900+0+0 (normal left inverted right x axis y axis) > 518mm x 324mm >1920x1200 60.0 + >1600x1200 60.0 >1680x1050 59.9 >1680x945 60.0 >1400x1050 59.9 >1600x900 60.0 >1280x1024 60.0 >1440x900 59.9* >1280x960 60.0 >1366x768 60.0 >1360x768 60.0 >1280x800 59.9 >1280x768 60.0 >1024x768 60.0 >1024x576 60.0 >800x60060.3 56.2 >848x48060.0 >640x48060.0 > DP1 disconnected (normal left inverted right x axis y axis) > DP2 disconnected (normal left inverted right x axis y axis) > > - > 3.5 in my dualscreen setup: > xrandr --current > Screen 0: minimum 320 x 200, current 3360 x 1200, maximum 32767 x 32767 > LVDS1 connected 1440x900+1920+0 (normal left inverted right x axis y > axis) 287mm x 180mm >1440x900 60.0*+ 50.0 >1024x768 60.0 >800x60060.3 56.2 >640x48059.9 > VGA1 disconnected (normal left inverted right x axis y axis) > HDMI1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) > 518mm x 324mm >1920x1200 60.0*+ >1600x1200 60.0 >1680x1050 59.9 >1680x945 60.0 >1400x1050 59.9 >1600x900 60.0 >1280x1024 60.0 >1440x900 59.9 >1280x960 60.0 >1366x768 60.0 >1360x768 60.0 >1280x800 59.9 >1280x768 60.0 >1024x768 60.0 >1024x576 60.0 >800x60060.3 56.2 >848x48060.0 >640x48060.0 > DP1 disconnected (normal left inverted right x axis y axis) > DP2 disconnected (normal left inverted right x axis y axis) > I know this is not really what you want to hear about, but you should wait for the fix to solve itself. The reason I'm saying this is that Intel programmers are really working hard on their graphics drivers with Steam comming to Linux and this is probably just a bug in their drivers to which we have no power. I could
Re: [gentoo-user] OpenRC update to 0.11.5 - safe if using older udev (pinned to udev-181)?
On Tue, Nov 20, 2012 at 02:17:17PM -0500, Tanstaafl wrote:
>
> RDEPEND="virtual/init
> kernel_FreeBSD? ( || ( >=sys-freebsd/freebsd-ubin-9.0_rc
> sys-process/fuser-bsd ) )
> elibc_glibc? ( >=sys-libs/glibc-2.5 )
> ncurses? ( sys-libs/ncurses )
> pam? ( sys-auth/pambase )
> >=sys-apps/baselayout-2.1-r1
> kernel_linux? (
> sys-process/psmisc
> )
> !
> So, *maybe* the last line means it needs a udev not less than 133 - but
> I don't know enough about how ebuilds to work to risk an unbootable
> system if it doesn't mean what I think it means.
>
> Sorry, I'm not a programmer and don't know what to look for (or even
> where to look until you pointed me to the file), so how about just a
> simple answer?
You are correct in that it requires !=OpenRC-0.11.3 requires udev-mount to be in the sysinit runlevel with udev.
migrate_udev_mount_script() {
if [ -e "${EROOT}"etc/runlevels/sysinit/udev -a \
! -e "${EROOT}"etc/runlevels/sysinit/udev-mount ]; then
add_boot_init udev-mount sysinit
fi
return 0
}
Since sys-apps/openrc-0.11.5 is still ~arch (where arch is architecture, such
as x86, amd64; and ~ means unstable), you might find bugs. It has been
submittied for stable request https://bugs.gentoo.org/show_bug.cgi?id=435756
but not yet approved as stable.
Do you mind asking why you want to use unstable openrc? Is there some feature
you need?
--
Happy Penguin Computers >')
126 Fenco Drive ( \
Tupelo, MS 38801 ^^
supp...@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/
Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
Re: [gentoo-user] OpenRC update to 0.11.5 - safe if using older udev (pinned to udev-181)?
On Tuesday 20 Nov 2012 19:38:40 Mark Knecht wrote: > On Tue, Nov 20, 2012 at 5:46 AM, Tanstaafl wrote: > > Anyone? > > > > I don't see any news blurbs warning about it, but with everything going > > on with udev, systemd, etc, I'm not risking updating unless/until I know > > it is safe. > > > > Tia... > > > > Charles > > I took one stable machine with almost no ~amd64 packages and updated. > No problems here. YMMV. Ditto. Just rebooted after updating /etc/rc.conf and all is good. Now I'm updating a x86 box. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] Problem with dosbox and latest Nvidia driver plus xorg
I did an update world yesterday, which updated both nvidia-drivers and xorg-server. I'm probably a niche here, but I use dosbox to play ye olde DOS games. It's been running fine for the last few months. But after the update, a dosbox textmode "fullscreen" is "letterboxed". I.e. there is a black bar at the top and at the bottom. I tried tweaking the dosbox config, to no avail. I even locked up the machine in the process. Fortunately, Magic-SysReq got me out with a clean reboot. My first instinct was to revert from nvidia-drivers-304.64 back to nvidia-drivers-295.71. However, that would also force a downgrade from x11-base/xorg-server-1.13.0-r1 to x11-base/xorg-server-1.12.4, which I am reluctant to do. Anybody have any ideas for a better solution? -- Walter Dnes We are apparently better off trying to avoid udev like the plague. Linus Torvalds; 2012/10/03 https://lkml.org/lkml/2012/10/3/349
Re: [gentoo-user] Kernel 3.6: No external Monitor
Am 20.11.2012 20:08, schrieb Damien Levac: > On 11/20/12 13:33, Norman Rieß wrote: >> Am 20.11.2012 19:02, schrieb Florian Philipp: >>> Am 20.11.2012 14:52, schrieb Norman Rieß: Am 20.11.2012 13:51, schrieb Bruce Hill: > On Tue, Nov 20, 2012 at 08:44:08AM +0100, Norman Rieß wrote: >> Hello, >> >> i am using a Thinkpad X301 with a DVI Monitor connected to the mini >> displayport. >> That worked perfectly for years, but with Kernel 3.6 (and 3.7rc) the DVI >> Monitor stays black on boot and it is not visible in xrandr. As if it >> wasn't connected at all. >> Rebooting with 3.5 brings back the Display with full functionality. >> >> All i found about this was a Fedora bugreport stating the issue, but is >> unanswered for a month now. >> >> Does someone got an idea here or faced the same issue and solved it? >> >> Regards, >> Norman > Can you give us a link to: > > (1) the Fedora bug report > (2) your 3.5 kernel .config > (3) your 3.6 (and 3.7rc) kernel .config(s) > Yes. (1) https://bugzilla.redhat.com/show_bug.cgi?id=869824 (2) http://smash-net.org/temp/config-3.5.4 (3) http://smash-net.org/temp/config-3.6.6 http://smash-net.org/temp/config-3.7.0-rc6 >>> What does `xrandr --current` say? (from x11-apps/xrandr) >>> >>> Regards, >>> Florian Philipp >>> >> In what situation? 3.5 or 3.6 kernel? >> > In doubt, both. But I'm fairly sure he meant 3.6 since there are no > problem to solve in 3.5. :P > > Damien > Yeah, i was kinda irritated by that question, as i allready said, that xrandr does not show the display. 3.5 activates the display during kernel loading, on 3.6 it stays shut off during the whole boot process. 3.6: xrandr --current Screen 0: minimum 320 x 200, current 1440 x 900, maximum 32767 x 32767 LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 287mm x 180mm 1440x900 60.0*+ 50.0 1024x768 60.0 800x60060.3 56.2 640x48059.9 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) - 3.5 both screens mirrored: xrandr --current Screen 0: minimum 320 x 200, current 1440 x 900, maximum 32767 x 32767 LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 287mm x 180mm 1440x900 60.0*+ 50.0 1024x768 60.0 800x60060.3 56.2 640x48059.9 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0 + 1600x1200 60.0 1680x1050 59.9 1680x945 60.0 1400x1050 59.9 1600x900 60.0 1280x1024 60.0 1440x900 59.9* 1280x960 60.0 1366x768 60.0 1360x768 60.0 1280x800 59.9 1280x768 60.0 1024x768 60.0 1024x576 60.0 800x60060.3 56.2 848x48060.0 640x48060.0 DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) - 3.5 in my dualscreen setup: xrandr --current Screen 0: minimum 320 x 200, current 3360 x 1200, maximum 32767 x 32767 LVDS1 connected 1440x900+1920+0 (normal left inverted right x axis y axis) 287mm x 180mm 1440x900 60.0*+ 50.0 1024x768 60.0 800x60060.3 56.2 640x48059.9 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0*+ 1600x1200 60.0 1680x1050 59.9 1680x945 60.0 1400x1050 59.9 1600x900 60.0 1280x1024 60.0 1440x900 59.9 1280x960 60.0 1366x768 60.0 1360x768 60.0 1280x800 59.9 1280x768 60.0 1024x768 60.0 1024x576 60.0 800x60060.3 56.2 848x48060.0 640x48060.0 DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis)
Re: [gentoo-user] OpenRC update to 0.11.5 - safe if using older udev (pinned to udev-181)?
On Tue, 20 Nov 2012 14:17:17 -0500 Tanstaafl wrote: > On 2012-11-20 12:05 PM, Bruce Hill > wrote: > > On Tue, Nov 20, 2012 at 08:46:59AM -0500, Tanstaafl wrote: > >> Anyone? > >> > >> I don't see any news blurbs warning about it, but with everything > >> going on with udev, systemd, etc, I'm not risking updating > >> unless/until I know it is safe. > > > Have you read the requirements in > > /usr/portage/sys-apps/openrc/openrc-0.11.5.ebuild ? > > I don't see anything in there labeled 'requirements'... > > All I found was: > > RDEPEND="virtual/init > kernel_FreeBSD? ( || ( >=sys-freebsd/freebsd-ubin-9.0_rc > sys-process/fuser-bsd ) ) > elibc_glibc? ( >=sys-libs/glibc-2.5 ) > ncurses? ( sys-libs/ncurses ) > pam? ( sys-auth/pambase ) > >=sys-apps/baselayout-2.1-r1 > kernel_linux? ( > sys-process/psmisc > ) > ! > So, *maybe* the last line means it needs a udev not less than 133 - > but I don't know enough about how ebuilds to work to risk an > unbootable system if it doesn't mean what I think it means. > > Sorry, I'm not a programmer and don't know what to look for (or even > where to look until you pointed me to the file), so how about just a > simple answer? He probably means all the elogs and ewarns in there - that ebuild is littered with the things. View the ebuild in less and search on "equire", you'll see what I mean. "!
Re: [gentoo-user] [Solved] Wine anybody?
On 11/19/2012 10:00:06 PM, Alan McKinnon wrote: On Mon, 19 Nov 2012 17:42:18 +0100 Helmut Jarausch wrote: > Hi, > has any been successful in using Wine-1.5.17 on an AMD 64bit machine? > > When I run /usr/bin/wine it says file not found. > > I'm seeing the wine32 and wine64 use flags. Removing the wine64 use > flags makes > emerge fail : configure: error: No OpenGL library found on this > system. > > eselect opengl list > shows "ati" here. > > Previous versions didn't show these problems. > > Has anybody encountered similar problems? > > Thanks, > Helmut. > Just like Marc, I also don't see the issues you are having. And I also have USE=-win64 on a 64bit Gentoo system (I mostly run corporatey Windows apps and you'd be amazed how many are still 32 bit only...) Is there any further clue as to what file is not being found in the first case? What do you get if you run ldd against the wine binary? In the second case, I suspect there's something wrong with your 32 bit OpenGL install. If you have USE=opengl then app-emulation/emul-linux-x86-opengl is pulled in as a dep and it should JustWork What are all your USE settings for wine? It turned out that the symlink /lib/ld-linux.so.2 -> ../lib32/ld-linux.so.2 had been removed (don't ask me why) This was hard to find out even strace didn't help initially. Thanks to all who have helped, Helmut.
Re: [gentoo-user] OpenRC update to 0.11.5 - safe if using older udev (pinned to udev-181)?
On Tue, Nov 20, 2012 at 5:46 AM, Tanstaafl wrote: > Anyone? > > I don't see any news blurbs warning about it, but with everything going on > with udev, systemd, etc, I'm not risking updating unless/until I know it is > safe. > > Tia... > > Charles > I took one stable machine with almost no ~amd64 packages and updated. No problems here. YMMV. HTH, Mark
Re: [gentoo-user] OpenRC update to 0.11.5 - safe if using older udev (pinned to udev-181)?
On 2012-11-20 12:05 PM, Bruce Hill wrote: On Tue, Nov 20, 2012 at 08:46:59AM -0500, Tanstaafl wrote: Anyone? I don't see any news blurbs warning about it, but with everything going on with udev, systemd, etc, I'm not risking updating unless/until I know it is safe. Have you read the requirements in /usr/portage/sys-apps/openrc/openrc-0.11.5.ebuild ? I don't see anything in there labeled 'requirements'... All I found was: RDEPEND="virtual/init kernel_FreeBSD? ( || ( >=sys-freebsd/freebsd-ubin-9.0_rc sys-process/fuser-bsd ) ) elibc_glibc? ( >=sys-libs/glibc-2.5 ) ncurses? ( sys-libs/ncurses ) pam? ( sys-auth/pambase ) >=sys-apps/baselayout-2.1-r1 kernel_linux? ( sys-process/psmisc ) !So, *maybe* the last line means it needs a udev not less than 133 - but I don't know enough about how ebuilds to work to risk an unbootable system if it doesn't mean what I think it means. Sorry, I'm not a programmer and don't know what to look for (or even where to look until you pointed me to the file), so how about just a simple answer?
Re: [gentoo-user] Kernel 3.6: No external Monitor
On 11/20/12 13:33, Norman Rieß wrote: > Am 20.11.2012 19:02, schrieb Florian Philipp: >> Am 20.11.2012 14:52, schrieb Norman Rieß: >>> Am 20.11.2012 13:51, schrieb Bruce Hill: On Tue, Nov 20, 2012 at 08:44:08AM +0100, Norman Rieß wrote: > Hello, > > i am using a Thinkpad X301 with a DVI Monitor connected to the mini > displayport. > That worked perfectly for years, but with Kernel 3.6 (and 3.7rc) the DVI > Monitor stays black on boot and it is not visible in xrandr. As if it > wasn't connected at all. > Rebooting with 3.5 brings back the Display with full functionality. > > All i found about this was a Fedora bugreport stating the issue, but is > unanswered for a month now. > > Does someone got an idea here or faced the same issue and solved it? > > Regards, > Norman Can you give us a link to: (1) the Fedora bug report (2) your 3.5 kernel .config (3) your 3.6 (and 3.7rc) kernel .config(s) >>> Yes. >>> (1) https://bugzilla.redhat.com/show_bug.cgi?id=869824 >>> >>> (2) http://smash-net.org/temp/config-3.5.4 >>> (3) http://smash-net.org/temp/config-3.6.6 >>> http://smash-net.org/temp/config-3.7.0-rc6 >>> >>> >>> >> What does `xrandr --current` say? (from x11-apps/xrandr) >> >> Regards, >> Florian Philipp >> > In what situation? 3.5 or 3.6 kernel? > In doubt, both. But I'm fairly sure he meant 3.6 since there are no problem to solve in 3.5. :P Damien
Re: [gentoo-user] Kernel 3.6: No external Monitor
Am 20.11.2012 19:02, schrieb Florian Philipp: > Am 20.11.2012 14:52, schrieb Norman Rieß: >> Am 20.11.2012 13:51, schrieb Bruce Hill: >>> On Tue, Nov 20, 2012 at 08:44:08AM +0100, Norman Rieß wrote: Hello, i am using a Thinkpad X301 with a DVI Monitor connected to the mini displayport. That worked perfectly for years, but with Kernel 3.6 (and 3.7rc) the DVI Monitor stays black on boot and it is not visible in xrandr. As if it wasn't connected at all. Rebooting with 3.5 brings back the Display with full functionality. All i found about this was a Fedora bugreport stating the issue, but is unanswered for a month now. Does someone got an idea here or faced the same issue and solved it? Regards, Norman >>> >>> Can you give us a link to: >>> >>> (1) the Fedora bug report >>> (2) your 3.5 kernel .config >>> (3) your 3.6 (and 3.7rc) kernel .config(s) >>> >> >> Yes. >> (1) https://bugzilla.redhat.com/show_bug.cgi?id=869824 >> >> (2) http://smash-net.org/temp/config-3.5.4 >> (3) http://smash-net.org/temp/config-3.6.6 >> http://smash-net.org/temp/config-3.7.0-rc6 >> >> >> > > What does `xrandr --current` say? (from x11-apps/xrandr) > > Regards, > Florian Philipp > In what situation? 3.5 or 3.6 kernel?
Re: [gentoo-user] Kernel 3.6: No external Monitor
Am 20.11.2012 14:52, schrieb Norman Rieß: > Am 20.11.2012 13:51, schrieb Bruce Hill: >> On Tue, Nov 20, 2012 at 08:44:08AM +0100, Norman Rieß wrote: >>> Hello, >>> >>> i am using a Thinkpad X301 with a DVI Monitor connected to the mini >>> displayport. >>> That worked perfectly for years, but with Kernel 3.6 (and 3.7rc) the DVI >>> Monitor stays black on boot and it is not visible in xrandr. As if it >>> wasn't connected at all. >>> Rebooting with 3.5 brings back the Display with full functionality. >>> >>> All i found about this was a Fedora bugreport stating the issue, but is >>> unanswered for a month now. >>> >>> Does someone got an idea here or faced the same issue and solved it? >>> >>> Regards, >>> Norman >> >> Can you give us a link to: >> >> (1) the Fedora bug report >> (2) your 3.5 kernel .config >> (3) your 3.6 (and 3.7rc) kernel .config(s) >> > > Yes. > (1) https://bugzilla.redhat.com/show_bug.cgi?id=869824 > > (2) http://smash-net.org/temp/config-3.5.4 > (3) http://smash-net.org/temp/config-3.6.6 > http://smash-net.org/temp/config-3.7.0-rc6 > > > What does `xrandr --current` say? (from x11-apps/xrandr) Regards, Florian Philipp signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] OpenRC update to 0.11.5 - safe if using older udev (pinned to udev-181)?
On Tue, Nov 20, 2012 at 08:46:59AM -0500, Tanstaafl wrote: > Anyone? > > I don't see any news blurbs warning about it, but with everything going > on with udev, systemd, etc, I'm not risking updating unless/until I know > it is safe. > > Tia... > > Charles Have you read the requirements in /usr/portage/sys-apps/openrc/openrc-0.11.5.ebuild ?
Re: [gentoo-user] OpenRC update to 0.11.5 - safe if using older udev (pinned to udev-181)?
On 2012-11-20 9:36 AM, Markos Chandras wrote: On Tue, Nov 20, 2012 at 1:46 PM, Tanstaafl wrote: Anyone? I don't see any news blurbs warning about it, but with everything going on with udev, systemd, etc, I'm not risking updating unless/until I know it is safe. The ebuild will usually take care of dependency versions. So unless the ebuild restricts it, I see no reason to stay with the old udev. OpenRC maintainers are very careful in this area as they are well aware of the problems a new udev can cause. I am staying with the old udev because I have /usr on a separate partition, and have no desire to bugger my system because of the machinations of the systemd/udev maintainers. I would have already migrated to mdev if I were a more capable linux admin, but I'm only barely passable. But as it is, I'm simply avoiding the whole mess unless/until I have to do a reinstall from scratch - which may be soon, since I need more disk space anyway (just wish I had a decent guide on installing gentoo in a vmware esxi server VM)...
Re: [gentoo-user] xfce4 Filed to execute default File Manager
On 11/20/12 01:20, Joseph wrote: > On 11/20/12 05:52, J. Roeleveld wrote: >> Joseph wrote: >> >>> I'm running xfce4. >>> When I try to click on Home folder I get: >>> >>> Filed to execute default File Manager >>> gutenprint (Permission denied). >> >> Can you open a text console and try to start " gutenprint" from there? >> >> If that works it's possibly something in xfce and someone else who >> uses that might be able to help. >> >> If it doesn't. Can you give the results of the following 2 commands: >> # which gutenprint >> # ls -lsa >> >> It could be file permissions. >> >> -- >> Joost >> -- >> Sent from my Android phone with K-9 Mail. Please excuse my brevity. > > For some reason or another, during upgrade, setting in: > Application Menu --> Setting --> Preferred Applications > FileManger got changed to "gutenprint" > > How did it happened, don't ask me. > In any case, Gutenprint is just a collection of drivers for printers (in many cases used by Cups). Set that back to thunar or whatever file manager you normally use. Regards, Damien
Re: [gentoo-user] OpenRC update to 0.11.5 - safe if using older udev (pinned to udev-181)?
On Tue, Nov 20, 2012 at 1:46 PM, Tanstaafl wrote: > Anyone? > > I don't see any news blurbs warning about it, but with everything going on > with udev, systemd, etc, I'm not risking updating unless/until I know it is > safe. > > Tia... > > Charles > The ebuild will usually take care of dependency versions. So unless the ebuild restricts it, I see no reason to stay with the old udev. OpenRC maintainers are very careful in this area as they are well aware of the problems a new udev can cause. -- Regards, Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
Re: [gentoo-user] Kernel 3.6: No external Monitor
Am 20.11.2012 13:51, schrieb Bruce Hill: > On Tue, Nov 20, 2012 at 08:44:08AM +0100, Norman Rieß wrote: >> Hello, >> >> i am using a Thinkpad X301 with a DVI Monitor connected to the mini >> displayport. >> That worked perfectly for years, but with Kernel 3.6 (and 3.7rc) the DVI >> Monitor stays black on boot and it is not visible in xrandr. As if it >> wasn't connected at all. >> Rebooting with 3.5 brings back the Display with full functionality. >> >> All i found about this was a Fedora bugreport stating the issue, but is >> unanswered for a month now. >> >> Does someone got an idea here or faced the same issue and solved it? >> >> Regards, >> Norman > > Can you give us a link to: > > (1) the Fedora bug report > (2) your 3.5 kernel .config > (3) your 3.6 (and 3.7rc) kernel .config(s) > Yes. (1) https://bugzilla.redhat.com/show_bug.cgi?id=869824 (2) http://smash-net.org/temp/config-3.5.4 (3) http://smash-net.org/temp/config-3.6.6 http://smash-net.org/temp/config-3.7.0-rc6
[gentoo-user] OpenRC update to 0.11.5 - safe if using older udev (pinned to udev-181)?
Anyone? I don't see any news blurbs warning about it, but with everything going on with udev, systemd, etc, I'm not risking updating unless/until I know it is safe. Tia... Charles
Re: [gentoo-user] Kernel 3.6: No external Monitor
On Tue, Nov 20, 2012 at 08:44:08AM +0100, Norman Rieß wrote: > Hello, > > i am using a Thinkpad X301 with a DVI Monitor connected to the mini > displayport. > That worked perfectly for years, but with Kernel 3.6 (and 3.7rc) the DVI > Monitor stays black on boot and it is not visible in xrandr. As if it > wasn't connected at all. > Rebooting with 3.5 brings back the Display with full functionality. > > All i found about this was a Fedora bugreport stating the issue, but is > unanswered for a month now. > > Does someone got an idea here or faced the same issue and solved it? > > Regards, > Norman Can you give us a link to: (1) the Fedora bug report (2) your 3.5 kernel .config (3) your 3.6 (and 3.7rc) kernel .config(s) -- Happy Penguin Computers >') 126 Fenco Drive ( \ Tupelo, MS 38801 ^^ supp...@happypenguincomputers.com 662-269-2706 662-205-6424 http://happypenguincomputers.com/ Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
