Re: [gentoo-user] Issues with =x11-drivers/xf86-video-ati-6.14.4: driver issue or hardware issue?
On Tue, Jun 5, 2012 at 11:41 AM, Michael Scherer a6702...@unet.univie.ac.at wrote: On Fri, 1 Jun 2012 04:11:35 -0400 Andrey Moshbear andrey@gmail.com wrote: On Wed, May 23, 2012 at 11:12 AM, Michael Scherer a6702...@unet.univie.ac.at wrote: - Original Message - From: Andrey Moshbear andrey@gmail.com To: gentoo-user gentoo-user@lists.gentoo.org Sent: Tuesday, 22 May, 2012 08:02 Subject: [gentoo-user] Issues with =x11-drivers/xf86-video-ati-6.14.4: driver issue or hardware issue? Lately, I've been having some issues with segfaults when running startx and it's been pretty persistent. Xorg.0.log and emerge --info are available at https://gist.github.com/2766926 . Kernel config is available at https://gist.github.com/276943 . I've tried downgrading, but =x11-drivers/xf86-video-ati-6.14.2 fails to compile due to incomplete structs. Is this more a driver or a hardware issue? first thing thing is your usage of ACCEPT_KEYWORDS=amd64 ~amd64. with ~amd64 you globally allow all packages masked for amd64. unless you are a developer/tester for gentoo you should remove this keyword, because gentoo usually has good reasons to mask some packages. if for some reason you really need a masked package, you can do this easily only for that package. global unmasking alone might be the reason for half of your troubles. second, it is advisable to use kernel modesetting, which is obviously not enabled. gentoo has a detailed howto for this under http://www.gentoo.org/doc/en/xorg-config.xml. this gives you all necessary details. just a quick shot for the moment. your kernel config doesn't under the link you give, I'd like to see that too, and maybe /etc/X11/xorg.conf or the contents of /etc/X11/xorg.conf.d, if you have any of these, Well, I added radeon drm modesetting and the kernel is crashing right after the microcode is loaded, but without any signs of panic, be it flashing keyboard lights or kernel backtrace with register values. Also, the segfault was caused by the DRI code interpreting a DRI opcode as a pointer, hence 0xa4 or similar in the back trace. in any case, I'd need some more information: the link to your .config is broken, I only get an empty page. if the kernel is involved, output of dmesg and rc.log would be needed to. Here's the .config of the kernel which crashed when loading the radeon microcode: http://servbox.moshbear.net/r9k-3.3.6-pf-.config.txt On 3.3.6, dmesg did tend to fill up with uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default settings. Also, I'm unsure how use of userspace modeseting contributes to X's drm code confusing an opcode for a pointer. xorg.conf is blank since X's hardware detection is sufficiently functional to not require a xorg.conf. by the way, did you anything with your ACCEPT_KEYWORDS? if not, the best thing would be set it simply = (and afterwards --update world, --depclean and revdep-rebuild), but that's up to you. I use ~amd64 because I like having everything be recent. Otherwise, it tends to feel a bit like a fast version of debian. That, and 99.9% functionality is enough. I've been able to fix almost all issues that arise by means of google - this one is simply proving to be tricky.
Re: [gentoo-user] Issues with =x11-drivers/xf86-video-ati-6.14.4: driver issue or hardware issue?
On Tue, Jun 5, 2012 at 11:41 AM, Michael Scherer a6702...@unet.univie.ac.at wrote: On Fri, 1 Jun 2012 04:11:35 -0400 Andrey Moshbear andrey@gmail.com wrote: On Wed, May 23, 2012 at 11:12 AM, Michael Scherer a6702...@unet.univie.ac.at wrote: - Original Message - From: Andrey Moshbear andrey@gmail.com To: gentoo-user gentoo-user@lists.gentoo.org Sent: Tuesday, 22 May, 2012 08:02 Subject: [gentoo-user] Issues with =x11-drivers/xf86-video-ati-6.14.4: driver issue or hardware issue? Lately, I've been having some issues with segfaults when running startx and it's been pretty persistent. Xorg.0.log and emerge --info are available at https://gist.github.com/2766926 . Kernel config is available at https://gist.github.com/276943 . I've tried downgrading, but =x11-drivers/xf86-video-ati-6.14.2 fails to compile due to incomplete structs. Is this more a driver or a hardware issue? first thing thing is your usage of ACCEPT_KEYWORDS=amd64 ~amd64. with ~amd64 you globally allow all packages masked for amd64. unless you are a developer/tester for gentoo you should remove this keyword, because gentoo usually has good reasons to mask some packages. if for some reason you really need a masked package, you can do this easily only for that package. global unmasking alone might be the reason for half of your troubles. second, it is advisable to use kernel modesetting, which is obviously not enabled. gentoo has a detailed howto for this under http://www.gentoo.org/doc/en/xorg-config.xml. this gives you all necessary details. just a quick shot for the moment. your kernel config doesn't under the link you give, I'd like to see that too, and maybe /etc/X11/xorg.conf or the contents of /etc/X11/xorg.conf.d, if you have any of these, regards, nichael Well, I added radeon drm modesetting and the kernel is crashing right after the microcode is loaded, but without any signs of panic, be it flashing keyboard lights or kernel backtrace with register values. Also, the segfault was caused by the DRI code interpreting a DRI opcode as a pointer, hence 0xa4 or similar in the back trace. -- m0shbear in any case, I'd need some more information: the link to your .config is broken, I only get an empty page. if the kernel is involved, output of dmesg and rc.log would be needed to. by the way, did you anything with your ACCEPT_KEYWORDS? if not, the best thing would be set it simply = (and afterwards --update world, --depclean and revdep-rebuild), but that's up to you. please send me the requested information, otherwise it's difficult to find out what's wrong. Also, I've noticed that that radeon.ko autodetection configures it as a RS780, whereas, according to motherboard documentation, it should be RS880 (780G vs 785G). This may be a reason for crashing, since the video card dies due to being supplied bad microcode.
Re: [gentoo-user] Issues with =x11-drivers/xf86-video-ati-6.14.4: driver issue or hardware issue?
On Thu, 7 Jun 2012 04:52:35 -0400 Andrey Moshbear andrey@gmail.com wrote: On Tue, Jun 5, 2012 at 11:41 AM, Michael Scherer a6702...@unet.univie.ac.at wrote: On Fri, 1 Jun 2012 04:11:35 -0400 Andrey Moshbear andrey@gmail.com wrote: On Wed, May 23, 2012 at 11:12 AM, Michael Scherer a6702...@unet.univie.ac.at wrote: - Original Message - From: Andrey Moshbear andrey@gmail.com To: gentoo-user gentoo-user@lists.gentoo.org Sent: Tuesday, 22 May, 2012 08:02 Subject: [gentoo-user] Issues with =x11-drivers/xf86-video-ati-6.14.4: driver issue or hardware issue? Lately, I've been having some issues with segfaults when running startx and it's been pretty persistent. Xorg.0.log and emerge --info are available at https://gist.github.com/2766926 . Kernel config is available at https://gist.github.com/276943 . I've tried downgrading, but =x11-drivers/xf86-video-ati-6.14.2 fails to compile due to incomplete structs. Is this more a driver or a hardware issue? first thing thing is your usage of ACCEPT_KEYWORDS=amd64 ~amd64. with ~amd64 you globally allow all packages masked for amd64. unless you are a developer/tester for gentoo you should remove this keyword, because gentoo usually has good reasons to mask some packages. if for some reason you really need a masked package, you can do this easily only for that package. global unmasking alone might be the reason for half of your troubles. second, it is advisable to use kernel modesetting, which is obviously not enabled. gentoo has a detailed howto for this under http://www.gentoo.org/doc/en/xorg-config.xml. this gives you all necessary details. just a quick shot for the moment. your kernel config doesn't under the link you give, I'd like to see that too, and maybe /etc/X11/xorg.conf or the contents of /etc/X11/xorg.conf.d, if you have any of these, regards, nichael Well, I added radeon drm modesetting and the kernel is crashing right after the microcode is loaded, but without any signs of panic, be it flashing keyboard lights or kernel backtrace with register values. Also, the segfault was caused by the DRI code interpreting a DRI opcode as a pointer, hence 0xa4 or similar in the back trace. -- m0shbear in any case, I'd need some more information: the link to your .config is broken, I only get an empty page. if the kernel is involved, output of dmesg and rc.log would be needed to. by the way, did you anything with your ACCEPT_KEYWORDS? if not, the best thing would be set it simply = (and afterwards --update world, --depclean and revdep-rebuild), but that's up to you. please send me the requested information, otherwise it's difficult to find out what's wrong. Also, I've noticed that that radeon.ko autodetection configures it as a RS780, whereas, according to motherboard documentation, it should be RS880 (780G vs 785G). This may be a reason for crashing, since the video card dies due to being supplied bad microcode. according to the gentoo manual, under device drivers-graphics- support for framebufferdevices you should uncheck -everything- except enable video mode handling helpers. instead of uvesafb in the kernel parameters you may use radeondrmfb, if anything at all. from the Xorg radeon page: First of all check that you don't load radeonfb, uvesafb or vesafb module. This includes no vga parameters for kernel when using KMS. Console is provided by fbcon and radeondrmfb frame buffer console. So it is best to make sure that fbcon module is loaded disabling vesa also should rid you of uvesa messages in Xorg.0.log. the rs880 and configuring as rs780 is indeed probably at the root of your troubles. seems that you got the wrong firmware. I have found other postings with the exact same problem, but as yet no clear solution. I'll see what I can find and let you know. regards, michael
Re: [gentoo-user] Lockdown: free/open OS maker pays Microsoft ransom for the right to boot on users' computers
On 7 June 2012, at 00:50, William Kenworthy wrote: ... I dont mean cpu power management, I meant under the kernel config option which you may not have enabled. As for the Dell iDREC, google it. This stuff is old in enterprise equipment, and I suspect not widely used but it is out there. Did you mean Dell DRAC? This is not obsolete at all, although in current models it is branded iDRAC. I don't believe DRAC remote access is really related to IPMI, however. I'm pretty sure that IPMI will work with a PowerEdge even lacking the DRAC module. OP is taking about having a laptop, anyway, so that seems like a clupea rubra. Stroller.
Re: [gentoo-user] USE=jpeg not part of hardened/linux/x86 profile
On Thu, Jun 7, 2012 at 12:39 AM, Grant emailgr...@gmail.com wrote: One of my desktops runs a hardened profile: # eselect profile list Available profile symlink targets: [1] default/linux/x86/10.0 [2] default/linux/x86/10.0/selinux [3] default/linux/x86/10.0/desktop [4] default/linux/x86/10.0/desktop/gnome [5] default/linux/x86/10.0/desktop/kde [6] default/linux/x86/10.0/developer [7] default/linux/x86/10.0/server [8] hardened/linux/x86 * [9] hardened/linux/x86/selinux I noticed USE=jpeg is not enabled by default so I took a look around and noticed these: # locate hardened/linux/x86 /usr/portage/profiles/hardened/linux/x86/10.0 /usr/portage/profiles/hardened/linux/x86/desktop /usr/portage/profiles/hardened/linux/x86/developer /usr/portage/profiles/hardened/linux/x86/minimal /usr/portage/profiles/hardened/linux/x86/server Why can't I eselect a profile like hardened/linux/x86/desktop which would hopefully have more desktop-oriented USE defaults than hardened/linux/x86? I have never used hardened and am not in any way informed about it, but I seem to recall reading that hardened on desktop was not supported and that it is primarily intended for use on servers. Maybe that profile is masked. You may still be able to use it by manually updating your profile symlink (rather than having eselect do it for you).
[gentoo-user] resume_list.py
I used to use this python script to display the packages that would be emerged when using the --resume option. But it does't work with python3.2 interpreter: ~ # cat resume_list.py import portage resume_list=portage.mtimedb[resume][mergelist] for i in range(len(resume_list)): print =+resume_list[i][2] ~ # ~ # python ~/resume_list.py File /root/resume_list.py, line 6 print =+resume_list[i][2] ^ SyntaxError: invalid syntax ~ # Q: Is there a way to make it work with python3.2 ?
Re: [gentoo-user] resume_list.py
On Thu, Jun 7, 2012 at 1:25 PM, Thanasis thana...@asyr.hopto.org wrote: I used to use this python script to display the packages that would be emerged when using the --resume option. But it does't work with python3.2 interpreter: ~ # cat resume_list.py import portage resume_list=portage.mtimedb[resume][mergelist] for i in range(len(resume_list)): print =+resume_list[i][2] ~ # ~ # python ~/resume_list.py File /root/resume_list.py, line 6 print =+resume_list[i][2] ^ SyntaxError: invalid syntax ~ # Q: Is there a way to make it work with python3.2 ? I believe parentheses are mandatory for print function in python 3.x. So try to change it to: print(=+resume_list[i][2]) Disclaimer: I do not know python. :)
Re: [gentoo-user] resume_list.py
On Thu, Jun 7, 2012 at 2:25 PM, Thanasis thana...@asyr.hopto.org wrote: I used to use this python script to display the packages that would be emerged when using the --resume option. But it does't work with python3.2 interpreter: ~ # cat resume_list.py import portage resume_list=portage.mtimedb[resume][mergelist] for i in range(len(resume_list)): print =+resume_list[i][2] ~ # ~ # python ~/resume_list.py File /root/resume_list.py, line 6 print =+resume_list[i][2] ^ SyntaxError: invalid syntax ~ # Q: Is there a way to make it work with python3.2 ? In Python 3.x, 'print' is a function, not a builtin. So it'd be print( blah ) instead of print blah There are standard scripts out there for converting between py2 and py3, FWIW. -- :wq
SOLVED [gentoo-user] resume_list.py
on 06/07/2012 09:37 PM Paul Hartman wrote the following: On Thu, Jun 7, 2012 at 1:25 PM, Thanasis thana...@asyr.hopto.org wrote: I used to use this python script to display the packages that would be emerged when using the --resume option. But it does't work with python3.2 interpreter: ~ # cat resume_list.py import portage resume_list=portage.mtimedb[resume][mergelist] for i in range(len(resume_list)): print =+resume_list[i][2] ~ # ~ # python ~/resume_list.py File /root/resume_list.py, line 6 print =+resume_list[i][2] ^ SyntaxError: invalid syntax ~ # Q: Is there a way to make it work with python3.2 ? I believe parentheses are mandatory for print function in python 3.x. So try to change it to: print(=+resume_list[i][2]) Disclaimer: I do not know python. :) That was it! Thanks!
Re: [gentoo-user] resume_list.py
on 06/07/2012 09:41 PM Michael Mol wrote the following: In Python 3.x, 'print' is a function, not a builtin. So it'd be print( blah ) instead of print blah There are standard scripts out there for converting between py2 and py3, FWIW. Correct! Thanks!
[gentoo-user] [OT] USB hard drive puzzle
I have an add-on usb3 adapter (based on ASMedia ASM1042 usb chip, using xhci kernel driver), which I dearly love except for one very annoying 'feature' ;) When I power up the outboard hard-disk docking station (plugged into the usb3 adapter) the computer never sees the docking station or its hard disk until I reboot the computer. Something in the BIOS apparently resets some hardware thingy, and then it all works extremely well thereafter. Having to reboot the computer to use a usb docking station kinda defeats the whole point of usb. (Or am I just being grumpy? :) Can anyone think of some trick I could use in lieu of rebooting to get the adapter/disk combination properly initialized? Any hints would be very much appreciated.
Re: [gentoo-user] [OT] USB hard drive puzzle
On Thu, 07 Jun 2012 15:53:53 -0700, walt wrote: When I power up the outboard hard-disk docking station (plugged into the usb3 adapter) the computer never sees the docking station or its hard disk until I reboot the computer. Something in the BIOS apparently resets some hardware thingy, and then it all works extremely well thereafter. Having to reboot the computer to use a usb docking station kinda defeats the whole point of usb. (Or am I just being grumpy? :) There's nothing wrong with being grumpy. Can anyone think of some trick I could use in lieu of rebooting to get the adapter/disk combination properly initialized? Does unloading and reloading the xhci module help? -- Neil Bothwick Veni, vermini, vomui I came, I got ratted, I threw up signature.asc Description: PGP signature
[gentoo-user] Firefox 13 and blank page
Hi, I recently upgraded to firefox 13. In the preferenced I had set When firefox starts to about:blank and Home Page to about:blank. This had worked for several versions. Now -- after visiting a site -- a thumbnail of that site is shown on the blank page now. I had looked through my addons, what may be guilty for that and found nothing. How can I get back a really blank page again? Thank you very much in advance! Best regards, mcc
Re: [gentoo-user] Firefox 13 and blank page
I recently upgraded to firefox 13. In the preferenced I had set When firefox starts to about:blank and Home Page to about:blank. This had worked for several versions. Now -- after visiting a site -- a thumbnail of that site is shown on the blank page now. Its a new feature of v13. When opening a new tab, users are now presented with their most visited pages https://www.mozilla.org/en-US/firefox/13.0/releasenotes/
[gentoo-user] Re: Firefox 13 and blank page
On 08/06/12 05:49, meino.cra...@gmx.de wrote: Hi, I recently upgraded to firefox 13. In the preferenced I had set When firefox starts to about:blank and Home Page to about:blank. This had worked for several versions. Now -- after visiting a site -- a thumbnail of that site is shown on the blank page now. I had looked through my addons, what may be guilty for that and found nothing. How can I get back a really blank page again? That's the new blank page of FF13. It's not a bug. It's feature :-P
Re: [gentoo-user] Re: Firefox 13 and blank page
Also, there's a grid icon in the top right of the page that lets you select a blank page instead. Cheers, Bryan On Fri, 08 Jun 2012 06:36:45 +0300 Nikos Chantziaras rea...@gmail.com wrote: On 08/06/12 05:49, meino.cra...@gmx.de wrote: Hi, I recently upgraded to firefox 13. In the preferenced I had set When firefox starts to about:blank and Home Page to about:blank. This had worked for several versions. Now -- after visiting a site -- a thumbnail of that site is shown on the blank page now. I had looked through my addons, what may be guilty for that and found nothing. How can I get back a really blank page again? That's the new blank page of FF13. It's not a bug. It's feature :-P
Re: [gentoo-user] USE=jpeg not part of hardened/linux/x86 profile
One of my desktops runs a hardened profile: # eselect profile list Available profile symlink targets: [1] default/linux/x86/10.0 [2] default/linux/x86/10.0/selinux [3] default/linux/x86/10.0/desktop [4] default/linux/x86/10.0/desktop/gnome [5] default/linux/x86/10.0/desktop/kde [6] default/linux/x86/10.0/developer [7] default/linux/x86/10.0/server [8] hardened/linux/x86 * [9] hardened/linux/x86/selinux I noticed USE=jpeg is not enabled by default so I took a look around and noticed these: # locate hardened/linux/x86 /usr/portage/profiles/hardened/linux/x86/10.0 /usr/portage/profiles/hardened/linux/x86/desktop /usr/portage/profiles/hardened/linux/x86/developer /usr/portage/profiles/hardened/linux/x86/minimal /usr/portage/profiles/hardened/linux/x86/server Why can't I eselect a profile like hardened/linux/x86/desktop which would hopefully have more desktop-oriented USE defaults than hardened/linux/x86? I have never used hardened and am not in any way informed about it, but I seem to recall reading that hardened on desktop was not supported and that it is primarily intended for use on servers. Can anyone confirm that a hardened profile is only supported for servers? I'm seeking a more desktop-friendly hardened profile but I don't want to use an unsupported one. - Grant Maybe that profile is masked. You may still be able to use it by manually updating your profile symlink (rather than having eselect do it for you).
