[gentoo-user] Re: The End Is Near ... or, get the vaseline, they're on the way!
On 17/03/12 06:11, Bruce Hill, Jr. wrote: This item just appeared after eix-sync: HTPC ~ # eselect news read 2012-03-16-udev-181-unmasking Title udev-181 unmasking AuthorWilliam Hubbs Posted2012-03-16 Revision 1 udev-181 is being unmasked on 2012-03-19. This news item is to inform you that once you upgrade to a version of udev>=181, if you have /usr on a separate partition, you must boot your system with an initramfs which pre-mounts /usr. An initramfs which does this is created by =sys-kernel/genkernel-3.4.25.1 or =sys-kernel/dracut-017-r1. If you do not want to use these tools, be sure any initramfs you create pre-mounts /usr. Also, if you are using OpenRC, you must upgrade to>= openrc-0.9.9. For more information on why this has been done, see the following URL: http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken Happy Computer Users, systemd is on your horizon. Houston, we have a problem! No, we don't. I hope systemd arrives soon. It's the best init system I ever saw.
Re: [gentoo-user] The End Is Near ... or, get the vaseline, they're on the way!
On Mar 17, 2012 11:15 AM, "Bruce Hill, Jr." wrote: > > This item just appeared after eix-sync: > > HTPC ~ # eselect news read > 2012-03-16-udev-181-unmasking > Title udev-181 unmasking > AuthorWilliam Hubbs > Posted2012-03-16 > Revision 1 > > udev-181 is being unmasked on 2012-03-19. > > This news item is to inform you that once you upgrade to a version of > udev >=181, if you have /usr on a separate partition, you must boot your > system with an initramfs which pre-mounts /usr. > > An initramfs which does this is created by > >=sys-kernel/genkernel-3.4.25.1 or > >=sys-kernel/dracut-017-r1. If you do not want to use these tools, be > sure any initramfs you create pre-mounts /usr. > > Also, if you are using OpenRC, you must upgrade to >= openrc-0.9.9. > > For more information on why this has been done, see the following URL: > http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken > > > > Happy Computer Users, systemd is on your horizon. > > Houston, we have a problem! > All my servers are now happily running mdev, USE="-udev", and sys-fs/udev in package.mask... Houston... we've landed. And it's beautiful here... there's lots of work to do to prepare the colony, but it's a whole new horizon... a new world! ;-) Rgds,
Re: [gentoo-user] The End Is Near ... or, get the vaseline, they're on the way!
On Fri, Mar 16, 2012 at 10:37 PM, Bruce Hill, Jr. wrote: > -- > > > > On March 17, 2012 at 12:19 AM "Canek Peláez Valdés" > wrote: > >> > http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken >> > >> > >> > >> > Happy Computer Users (for now), systemd is on your horizon. >> > >> > Houston, we have a problem! >> >> You can always try Walter's et. al. mdev replacement: >> >> http://www.waltdnes.org/mdev/ > > > Sad fact is systemd will soon be required in Gentoo. I don't think so. Not in the near future at least. Of course, *I* don't think that will be a sad fact, but that's another matter :D > Forget the udev/mdev argument ... Oh, I have never cared that much for it ;) > systemd is poorly coded, Many people think that it tries to solve a problem that "doesn't exists", or that it has failures in its design. However, even the more fervent critics agree that Lennart is a really good programmer. You are the first person I read saying that systemd is "poorly coded". In other words: [citation needed] > and we're > getting so much further from a good, reliable DE to compete with the likes > of Windows 7. Just horse manure DEs in Gentoo now. I would say that we are actually better than them in several ways. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] How can I trigger kernel panic?
On March 14, 2012 at 2:41 PM "ZHANG, Le" wrote: > On Wed, Mar 14, 2012 at 11:23 AM, Jarry wrote: > > > Hi, > > > > my question might seem silly, but I have reason for it: > > I have heard there is way to auto-reboot linux after kernel > > panic using "kernel.panic=" in /etc/sysctl.conf. > > > > This might come handy as my server is far from me and I do > > not have any remote console. But I would like to test it > > and see if it works (first on my desktop). > > > > So my question is: Can I somehow deliberately trigger > > "kernel panic" (or "kernel oops")? > > > For panic, echo c > /proc/sysrq-trigger > > -- > Zhang Le, Robert > Gentoo/Loongson(龙芯) Developer > http://zhangle.is-a-geek.org Nasty way to do it, but I thought that should be: echo b > / proc / sysrq-trigger Isn't b for reboot? -- Happy Penguin Computers>`) 126 Fenco Drive( \ Tupelo, MS 38801^^ 662-269-2706; 662-491-8613 support at happypenguincomputers dot com http://www.happypenguincomputers.com
Re: [gentoo-user] The End Is Near ... or, get the vaseline, they're on the way!
-- On March 17, 2012 at 12:19 AM "Canek Peláez Valdés" wrote: > > http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken > > > > > > > > Happy Computer Users (for now), systemd is on your horizon. > > > > Houston, we have a problem! > > You can always try Walter's et. al. mdev replacement: > > http://www.waltdnes.org/mdev/ Sad fact is systemd will soon be required in Gentoo. Forget the udev/mdev argument ... systemd is poorly coded, and we're getting so much further from a good, reliable DE to compete with the likes of Windows 7. Just horse manure DEs in Gentoo now. -- Happy Penguin Computers>`) 126 Fenco Drive( \ Tupelo, MS 38801^^ 662-269-2706; 662-491-8613 support at happypenguincomputers dot com http://www.happypenguincomputers.com
Re: [gentoo-user] Beta test Gentoo with mdev instead of udev; version 5 - failure :-(
On Fri, Mar 16, 2012 at 10:20 PM, Bruce Hill, Jr. wrote: > > > > On March 14, 2012 at 1:22 PM "Canek Peláez Valdés" > wrote: > > >> Alan, the "vast majority" of Linux users right now are phone users. > >> At least, that's how I see it. > >> Again, think about phones. And tablets. And TVs. And >> [insert-here-cool-gadgets-from-the-future]. > >> Right now Linux runs in my phone, my TV's, my routers and every >> computer I own. I have a couple of Windows installations, which I use >> once or twice every three months (I ported a PyGTK program to Windows >> last week, so I had to boot into Windows for the first time this >> year). I want Linux running on *everything*, and what is more: I don't >> want android in my handhelds, I want the full GNOME experience. > >> Regards. >> -- > > What phone do you have running which "Linux"? > > I'm curious because a couple months ago we got new Samsung Galaxy S phones. > > I'd previously used an iPhone 3GS for a bit over a year. Since I can't > stand Apple, as a company, it was with great joy that we could get 2 of > these Galaxy S phones for free (with the 2-year contract, of course). Sony XPeria Play, with Android 2.3.3, I believe. I'm a gamer. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] Beta test Gentoo with mdev instead of udev; version 5 - failure :-(
On March 14, 2012 at 1:22 PM "Canek Peláez Valdés" wrote: > Alan, the "vast majority" of Linux users right now are phone users. > At least, that's how I see it. > Again, think about phones. And tablets. And TVs. And > [insert-here-cool-gadgets-from-the-future]. > Right now Linux runs in my phone, my TV's, my routers and every > computer I own. I have a couple of Windows installations, which I use > once or twice every three months (I ported a PyGTK program to Windows > last week, so I had to boot into Windows for the first time this > year). I want Linux running on *everything*, and what is more: I don't > want android in my handhelds, I want the full GNOME experience. > Regards. > -- What phone do you have running which "Linux"? I'm curious because a couple months ago we got new Samsung Galaxy S phones. I'd previously used an iPhone 3GS for a bit over a year. Since I can't stand Apple, as a company, it was with great joy that we could get 2 of these Galaxy S phones for free (with the 2-year contract, of course). -- Happy Penguin Computers>`) 126 Fenco Drive( \ Tupelo, MS 38801^^ 662-269-2706; 662-491-8613 support at happypenguincomputers dot com http://www.happypenguincomputers.com
Re: [gentoo-user] The End Is Near ... or, get the vaseline, they're on the way!
On Fri, Mar 16, 2012 at 10:11 PM, Bruce Hill, Jr. wrote: > This item just appeared after eix-sync: > > HTPC ~ # eselect news read > 2012-03-16-udev-181-unmasking > Title udev-181 unmasking > Author William Hubbs > Posted 2012-03-16 > Revision 1 > > udev-181 is being unmasked on 2012-03-19. > > This news item is to inform you that once you upgrade to a version of > udev >=181, if you have /usr on a separate partition, you must boot your > system with an initramfs which pre-mounts /usr. > > An initramfs which does this is created by >>=sys-kernel/genkernel-3.4.25.1 or >>=sys-kernel/dracut-017-r1. If you do not want to use these tools, be > sure any initramfs you create pre-mounts /usr. > > Also, if you are using OpenRC, you must upgrade to >= openrc-0.9.9. > > For more information on why this has been done, see the following URL: > http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken > > > > Happy Computer Users, systemd is on your horizon. > > Houston, we have a problem! You can always try Walter's et. al. mdev replacement: http://www.waltdnes.org/mdev/ Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] mdev for udev substitution instructions web page is up
On Mar 17, 2012 9:54 AM, "Walter Dnes" wrote: > > The instructions for replacing udev with mdev are now up at > http://www.waltdnes.org/mdev/ validator.w3.org complains about a couple > of extensions I used, but it appears to work OK in both Firefox and > Midori. Any comments from users of other browsers? The page will be > permanently "under construction", i.e. evolving as we find out more > about how mdev works. > Walter, I've been reading on mdev, and I think there are some things we ought to try : 1. *IMPORTANT* make sure there's /etc/mdev.conf ! 2. Adding 'mdev -s' into /sbin/linuxrc after mounting sys/proc. man busybox says that 'mdev -s' populates /dev with devices it detects during boot. Maybe we won't need kernel devtmpfs anymore? 3. To handle hotplug events, ' echo /bin/mdev > /proc/sys/kernel/hotplug '. But I'm not sure which kernel config to enable to make that sysctl knob appear.
[gentoo-user] The End Is Near ... or, get the vaseline, they're on the way!
This item just appeared after eix-sync: HTPC ~ # eselect news read 2012-03-16-udev-181-unmasking Title udev-181 unmasking AuthorWilliam Hubbs Posted2012-03-16 Revision 1 udev-181 is being unmasked on 2012-03-19. This news item is to inform you that once you upgrade to a version of udev >=181, if you have /usr on a separate partition, you must boot your system with an initramfs which pre-mounts /usr. An initramfs which does this is created by >=sys-kernel/genkernel-3.4.25.1 or >=sys-kernel/dracut-017-r1. If you do not want to use these tools, be sure any initramfs you create pre-mounts /usr. Also, if you are using OpenRC, you must upgrade to >= openrc-0.9.9. For more information on why this has been done, see the following URL: http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken Happy Computer Users, systemd is on your horizon. Houston, we have a problem! -- Happy Penguin Computers>`) 126 Fenco Drive( \ Tupelo, MS 38801^^ 662-269-2706; 662-491-8613 support at happypenguincomputers dot com http://www.happypenguincomputers.com
Re: [gentoo-user] mdev for udev substitution instructions web page is up
Walter Dnes wrote: > The instructions for replacing udev with mdev are now up at > http://www.waltdnes.org/mdev/ validator.w3.org complains about a couple > of extensions I used, but it appears to work OK in both Firefox and > Midori. Any comments from users of other browsers? The page will be > permanently "under construction", i.e. evolving as we find out more > about how mdev works. > Looks fine on Seamonkey2. Glad you got a web page. Another step taken. ;-) Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
[gentoo-user] mdev for udev substitution instructions web page is up
The instructions for replacing udev with mdev are now up at http://www.waltdnes.org/mdev/ validator.w3.org complains about a couple of extensions I used, but it appears to work OK in both Firefox and Midori. Any comments from users of other browsers? The page will be permanently "under construction", i.e. evolving as we find out more about how mdev works. -- Walter Dnes
Re: [gentoo-user] Where does /sys/class/backlight/intel_backlight come from?
>> Does anyone know which kernel option would be responsible for >> /sys/class/backlight/intel_backlight? I've disabled some backlight >> stuff in the kernel but the directory still appears. I get screen >> backlight control on my laptop if I do: > > Probably from the intel video driver (i915 or whatever) Sounds like I won't be able to remove it without removing support for my video card. I have to enter 'echo 0 > /sys/class/backlight/intel_backlight/brightness' again every time xlockmore comes on. Does anyone know what's going on there? - Grant
Re: [gentoo-user] Where does /sys/class/backlight/intel_backlight come from?
>> Does anyone know which kernel option would be responsible for >> /sys/class/backlight/intel_backlight? I've disabled some backlight >> stuff in the kernel but the directory still appears. I get screen >> backlight control on my laptop if I do: >> >> echo 0 > /sys/class/backlight/intel_backlight/brightness >> >> but if xlockmore blanks my screen, I have to issue the above again >> before screen backlight control works again. I also have acpi_video0 >> in /sys/class/backlight and I think removing intel_backlight might fix >> the problem. >> >> I could try deleting the directory. Is that safe? Are the files and >> folders in /sys generated dynamically at boot? > > The /sys directory is like /proc; it's a virtual directory which > serves as interface to several kernel knobs. I don't think you can > remove any dir from it, and if you do, next boot it will show up > again. You're right, "operation not permitted" there. - Grant
Re: [gentoo-user] Re: Backlight problems
>> > I do have baselayout1.start/stop stuff so it seems our systems are >> > fairly different. >> >> My new install doesn't have them, but all of my old installs do have >> them and 'equery b /etc/local.d/baselayout1.start' comes back with >> nothing so I don't think they're being installed anymore. > > They never were installed in the sense of being files in the openrc > package. The ebuild created them from the old style baselayout start/stop > files if they were present, so you wouldn't expect to see them on a new > install - or an old install in which you'd renamed them to something more > helpful. Thanks Neil. - Grant
Re: [gentoo-user] Re: Backlight problems
On Fri, 16 Mar 2012 13:06:17 -0700, Grant wrote: > > I do have baselayout1.start/stop stuff so it seems our systems are > > fairly different. > > My new install doesn't have them, but all of my old installs do have > them and 'equery b /etc/local.d/baselayout1.start' comes back with > nothing so I don't think they're being installed anymore. They never were installed in the sense of being files in the openrc package. The ebuild created them from the old style baselayout start/stop files if they were present, so you wouldn't expect to see them on a new install - or an old install in which you'd renamed them to something more helpful. -- Neil Bothwick Middle-age - because your age starts to show at your middle. signature.asc Description: PGP signature
Re: [gentoo-user] Beta test Gentoo with mdev instead of udev; version 5 - failure :-(
On Fri, 16 Mar 2012 15:44:03 +0100, Joost Roeleveld wrote: > > This is for running programs from the computer against the device, not > > autorunning programs on the device - such as initialising USB > > modems. > > How long till autorunning programs becomes "the next great thing" on > the desktop for Linux? When people want them... or when Canonical tell people they want them :( > > > That is, untill someone comes up with the "clever" idea of shoving > > > an automounter into udev. (Will it then also auto-unmount when I > > > want my CD back?) > > > > That's already been done, > > > > * sys-apps/uam > > Available versions: 0.2.1 (~)0.3 > > Homepage:https://github.com/mgorny/uam/ > > Description: Simple udev-based automounter for removable > > USB media > > This is an automounter, not autounmounter... You said automounter. > What I would like is one where a CDrom is automounted when inserted and > when I press the eject-button, the cdrom is umounted and I get my cd > back... That would require a more intelligent optical drive that sent a signal to the computer when the eject button was pressed. The computer could then run the eject command, which also unmounts the drive. Although that seem more the province of ACPI than udev. > > I also have a rule on a headless media server to run a script that > > mounts a USB stick, copies files to it, unmounts it and lets me know > > when it is done. I can mark files for copying at any time and my wife > > can just plug in a stick when she wants to copy them for viewing on a > > small, non-connected TV by her treadmill (her treadmill, I emphasise > > - I find a keyboard and trackball give me all the exercise I want). > > Why not connect that TV? ;) Because the hardware to do so would cost around £100, USB sticks cost rather less :P -- Neil Bothwick Puns are bad, but poetry is verse... signature.asc Description: PGP signature
Re: [gentoo-user] To mount or not to Mount proc, that is the question
On Fri, Mar 16, 2012 at 2:40 PM, Canek Peláez Valdés wrote: > On Fri, Mar 16, 2012 at 3:18 PM, Mark Knecht wrote: >> On Fri, Mar 16, 2012 at 12:47 PM, Canek Peláez Valdés >> wrote: >>> On Fri, Mar 16, 2012 at 1:40 PM, Mark Knecht wrote: >> Looking at the Gentoo amd64 install guide here: http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8 it appears that the recommendation is to mount proc. [QUOTE] /dev/sda1 /boot ext2 defaults,noatime 1 2 /dev/sda2 none swap sw 0 0 /dev/sda3 / ext3 noatime 0 1 /dev/cdrom /mnt/cdrom auto noauto,user 0 0 proc /proc proc defaults 0 0 shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 [QUOTE] >> >>> >>> I haven't put /proc explicitly on my /etc/fstab since a long time ago, >>> and everything seems to be working. However, I use systemd, which >>> always mounts /proc with the default options, and only uses the entry >>> in /etc/fstab (if present) to override the default options. In other >>> words, systemd always mounts /proc, no matter if it's listed in >>> /etc/fstab or not. >>> >>> I don't know what OpenRC does, but it would not surprise me that it's >>> something similar. >>> >>> Regards. >>> -- >>> Canek Peláez Valdés >>> Posgrado en Ciencia e Ingeniería de la Computación >>> Universidad Nacional Autónoma de México >>> >> >> Thanks Canek. I appreciate your response. >> >> It seems when rereading the link above the authors do put the work >> 'example' in italics, implying that possibly I should know what I'm >> doing and not depend on the text on that page. I'm fine with the not >> depending part. I'm not so sure about the 'know what I'm doing' part. >> ;-) >> >> I'm going to take a wild guess that it's somehow mounted in an init >> script these days but I have no reason to know that's actually how it >> gets done. I did read the kernel docs and it doesn't seem to be done >> automatically by the kernel AFAICT. > > No, it's the init system; look at /lib/rc/sh/init.sh:66: > > # By default VServer already has /proc mounted, but OpenVZ does not! > # However, some of our users have an old proc image in /proc > # NFC how they managed that, but the end result means we have to test if > # /proc actually works or not. We do this by comparing two reads of > # /proc/self/environ for which we have set the variable VAR to two > # different values. If the comparison comes back equal, we know that > # /proc is not working. > mountproc=true > f=/proc/self/environ > if [ -e $f ]; then > if [ "$(VAR=a cat $f)" = "$(VAR=b cat $f)" ]; then > eerror "You have cruft in /proc that should be deleted" > else > einfo "/proc is already mounted, skipping" > mountproc=false > fi > fi > unset f > > if $mountproc; then > procfs="proc" > [ "$RC_UNAME" = "GNU/kFreeBSD" ] && proc="linprocfs" > ebegin "Mounting /proc" > if ! fstabinfo --mount /proc; then > mount -n -t "$procfs" -o noexec,nosuid,nodev proc /proc > fi > eend $? > fi > > Mistery solved :D > > Regards. > -- > Canek Peláez Valdés > Posgrado en Ciencia e Ingeniería de la Computación > Universidad Nacional Autónoma de México > Yep, that's it. Somewhat interestingly it was at line 89 in my file but that may well be differences between OpenRC and systemd, etc. Anyway, the code looks identical and at least on the one machine I've tested it doesn't seem to have hurt anythign to remove it from my fstab file. !Thanks! Cheers, Mark
Re: [gentoo-user] To mount or not to Mount proc, that is the question
On Fri, Mar 16, 2012 at 3:18 PM, Mark Knecht wrote: > On Fri, Mar 16, 2012 at 12:47 PM, Canek Peláez Valdés > wrote: >> On Fri, Mar 16, 2012 at 1:40 PM, Mark Knecht wrote: > >>> Looking at the Gentoo amd64 install guide here: >>> >>> http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8 >>> >>> it appears that the recommendation is to mount proc. >>> >>> [QUOTE] >>> >>> /dev/sda1 /boot ext2 defaults,noatime 1 2 >>> /dev/sda2 none swap sw 0 0 >>> /dev/sda3 / ext3 noatime 0 1 >>> >>> /dev/cdrom /mnt/cdrom auto noauto,user 0 0 >>> >>> proc /proc proc defaults 0 0 >>> shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 >>> >>> [QUOTE] > >> >> I haven't put /proc explicitly on my /etc/fstab since a long time ago, >> and everything seems to be working. However, I use systemd, which >> always mounts /proc with the default options, and only uses the entry >> in /etc/fstab (if present) to override the default options. In other >> words, systemd always mounts /proc, no matter if it's listed in >> /etc/fstab or not. >> >> I don't know what OpenRC does, but it would not surprise me that it's >> something similar. >> >> Regards. >> -- >> Canek Peláez Valdés >> Posgrado en Ciencia e Ingeniería de la Computación >> Universidad Nacional Autónoma de México >> > > Thanks Canek. I appreciate your response. > > It seems when rereading the link above the authors do put the work > 'example' in italics, implying that possibly I should know what I'm > doing and not depend on the text on that page. I'm fine with the not > depending part. I'm not so sure about the 'know what I'm doing' part. > ;-) > > I'm going to take a wild guess that it's somehow mounted in an init > script these days but I have no reason to know that's actually how it > gets done. I did read the kernel docs and it doesn't seem to be done > automatically by the kernel AFAICT. No, it's the init system; look at /lib/rc/sh/init.sh:66: # By default VServer already has /proc mounted, but OpenVZ does not! # However, some of our users have an old proc image in /proc # NFC how they managed that, but the end result means we have to test if # /proc actually works or not. We do this by comparing two reads of # /proc/self/environ for which we have set the variable VAR to two # different values. If the comparison comes back equal, we know that # /proc is not working. mountproc=true f=/proc/self/environ if [ -e $f ]; then if [ "$(VAR=a cat $f)" = "$(VAR=b cat $f)" ]; then eerror "You have cruft in /proc that should be deleted" else einfo "/proc is already mounted, skipping" mountproc=false fi fi unset f if $mountproc; then procfs="proc" [ "$RC_UNAME" = "GNU/kFreeBSD" ] && proc="linprocfs" ebegin "Mounting /proc" if ! fstabinfo --mount /proc; then mount -n -t "$procfs" -o noexec,nosuid,nodev proc /proc fi eend $? fi Mistery solved :D Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] Where does /sys/class/backlight/intel_backlight come from?
On Fri, Mar 16, 2012 at 3:14 PM, Grant wrote: > Does anyone know which kernel option would be responsible for > /sys/class/backlight/intel_backlight? I've disabled some backlight > stuff in the kernel but the directory still appears. I get screen > backlight control on my laptop if I do: Probably from the intel video driver (i915 or whatever)
Re: [gentoo-user] To mount or not to Mount proc, that is the question
On Fri, Mar 16, 2012 at 12:47 PM, Canek Peláez Valdés wrote: > On Fri, Mar 16, 2012 at 1:40 PM, Mark Knecht wrote: >> Looking at the Gentoo amd64 install guide here: >> >> http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8 >> >> it appears that the recommendation is to mount proc. >> >> [QUOTE] >> >> /dev/sda1 /boot ext2 defaults,noatime 1 2 >> /dev/sda2 none swap sw 0 0 >> /dev/sda3 / ext3 noatime 0 1 >> >> /dev/cdrom /mnt/cdrom auto noauto,user 0 0 >> >> proc /proc proc defaults 0 0 >> shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 >> >> [QUOTE] > > I haven't put /proc explicitly on my /etc/fstab since a long time ago, > and everything seems to be working. However, I use systemd, which > always mounts /proc with the default options, and only uses the entry > in /etc/fstab (if present) to override the default options. In other > words, systemd always mounts /proc, no matter if it's listed in > /etc/fstab or not. > > I don't know what OpenRC does, but it would not surprise me that it's > something similar. > > Regards. > -- > Canek Peláez Valdés > Posgrado en Ciencia e Ingeniería de la Computación > Universidad Nacional Autónoma de México > Thanks Canek. I appreciate your response. It seems when rereading the link above the authors do put the work 'example' in italics, implying that possibly I should know what I'm doing and not depend on the text on that page. I'm fine with the not depending part. I'm not so sure about the 'know what I'm doing' part. ;-) I'm going to take a wild guess that it's somehow mounted in an init script these days but I have no reason to know that's actually how it gets done. I did read the kernel docs and it doesn't seem to be done automatically by the kernel AFAICT. Thanks, Mark
Re: [gentoo-user] Where does /sys/class/backlight/intel_backlight come from?
On Fri, Mar 16, 2012 at 2:14 PM, Grant wrote: > Does anyone know which kernel option would be responsible for > /sys/class/backlight/intel_backlight? I've disabled some backlight > stuff in the kernel but the directory still appears. I get screen > backlight control on my laptop if I do: > > echo 0 > /sys/class/backlight/intel_backlight/brightness > > but if xlockmore blanks my screen, I have to issue the above again > before screen backlight control works again. I also have acpi_video0 > in /sys/class/backlight and I think removing intel_backlight might fix > the problem. > > I could try deleting the directory. Is that safe? Are the files and > folders in /sys generated dynamically at boot? The /sys directory is like /proc; it's a virtual directory which serves as interface to several kernel knobs. I don't think you can remove any dir from it, and if you do, next boot it will show up again. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
[gentoo-user] Where does /sys/class/backlight/intel_backlight come from?
Does anyone know which kernel option would be responsible for /sys/class/backlight/intel_backlight? I've disabled some backlight stuff in the kernel but the directory still appears. I get screen backlight control on my laptop if I do: echo 0 > /sys/class/backlight/intel_backlight/brightness but if xlockmore blanks my screen, I have to issue the above again before screen backlight control works again. I also have acpi_video0 in /sys/class/backlight and I think removing intel_backlight might fix the problem. I could try deleting the directory. Is that safe? Are the files and folders in /sys generated dynamically at boot? - Grant
Re: [gentoo-user] Re: Backlight problems
[snip] >> Hey Mark, I'm happy to say I just fixed the screen backlighting on my >> system, but I'm sorry to say I don't think it will help you with >> keyboard backlighting. To fix it, I removed 'acpi_backlight=vendor' >> from grub and added 'echo 0 > >> /sys/class/backlight/intel_backlight/brightness' to >> /etc/local.d/backlight.start and made that file executable. Now >> backlight control works perfectly via the keyboard shortcuts with no >> other configuration and no xbacklight. I'm on >> hardened-sources-3.2.2-r1. >> >> BTW, I noticed baselayout1.start and baselayout1.stop are no longer >> created in /etc/local.d. >> >> - Grant >> > > Hi Grant, > OK, that's interesting info. Here's what I'm currently seeing: > > slinky ~ # uname -a > Linux slinky 3.2.10 #1 SMP PREEMPT Tue Mar 13 09:45:35 PDT 2012 x86_64 > Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz GenuineIntel GNU/Linux > slinky ~ # ls -al /etc/local.d/ > total 20 > drwxr-xr-x 2 root root 4096 Feb 23 21:03 . > drwxr-xr-x 72 root root 4096 Mar 16 11:53 .. > -rw-r--r-- 1 root root 387 Feb 23 21:03 README > -rwxr-xr-x 1 root root 123 May 3 2011 baselayout1.start > -rwxr-xr-x 1 root root 217 May 3 2011 baselayout1.stop > slinky ~ # ls -la /sys/class/backlight/asus_laptop/ > total 0 > drwxr-xr-x 2 root root 0 Mar 16 04:35 . > drwxr-xr-x 3 root root 0 Mar 16 04:35 .. > -r--r--r-- 1 root root 4096 Mar 16 12:09 actual_brightness > -rw-r--r-- 1 root root 4096 Mar 16 12:09 bl_power > -rw-r--r-- 1 root root 4096 Mar 16 11:40 brightness > lrwxrwxrwx 1 root root 0 Mar 16 12:09 device -> > ../../../asus_laptop > -r--r--r-- 1 root root 4096 Mar 16 11:40 max_brightness > lrwxrwxrwx 1 root root 0 Mar 16 04:35 subsystem -> > ../../../../../class/backlight > -r--r--r-- 1 root root 4096 Mar 16 12:09 type > -rw-r--r-- 1 root root 4096 Mar 16 04:35 uevent > slinky ~ # cat /sys/class/backlight/asus_laptop/brightness > 15 > slinky ~ # > > So, it seems to me that following your example, if I wanted to > experiment with screen backlighting what would I do? I'm in KDE BTW in > case we're doing something different in that regard. > > I see in the Global Keyboard Shortcuts in KDE that there are > Monitor Brightness Down/Up controls defined but I'm not understanding > what keys actually control those. I Googled around for a minute and > found Fn-ArrowUp/ArrowDn but they didn't work o I'm hoping you can > tell me and save me a few minutes. Maybe it's because I haven't > started something required? > > acpi_listen on n-ArrowUp/Dn does produce a response so maybe I > don't have something properly mapped? Have you tried adding 'acpi_osi=Linux acpi_backlight=vendor' to grub? Is asus_laptop all you have in /sys/class/backlight? > I do have baselayout1.start/stop stuff so it seems our systems are > fairly different. My new install doesn't have them, but all of my old installs do have them and 'equery b /etc/local.d/baselayout1.start' comes back with nothing so I don't think they're being installed anymore. - Grant
Re: [gentoo-user] To mount or not to Mount proc, that is the question
On Fri, Mar 16, 2012 at 1:40 PM, Mark Knecht wrote: > I've been trying to debug a problem where one laptop's networking, as > controlled by wicd, seems to randomly go offline once in awhile. In > the process of reviewing 5 machines I ran across an inconsistency > across a bunch of my machines, new and old. It seems some of them > mount proc in fstab while others do not. Some of these machines have > been around for a few years not mounting proc and except for the > laptop's networking issues there really haven't been any problems. > > Looking at the Gentoo amd64 install guide here: > > http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8 > > it appears that the recommendation is to mount proc. > > [QUOTE] > > /dev/sda1 /boot ext2 defaults,noatime 1 2 > /dev/sda2 none swap sw 0 0 > /dev/sda3 / ext3 noatime 0 1 > > /dev/cdrom /mnt/cdrom auto noauto,user 0 0 > > proc /proc proc defaults 0 0 > shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 > > [QUOTE] > > > What would the issues be with proc not mounted? For instance, this > machine doesn't mount proc in fstab but still has proc: > > laptop1 ~ # cat /etc/fstab > > /dev/sdb1 /boot ext2 noauto,noatime 1 2 > /dev/sdb4 / ext3 noatime 0 1 > /dev/sdb2 none swap sw 0 0 > /dev/cdrom /mnt/cdrom auto noauto,ro 0 0 > > shm /dev/shm tmpfs > nodev,nosuid,noexec 0 0 > > > laptop1 ~ # cat /proc/mdstat > Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] > md127 : active (auto-read-only) raid1 sdb3[1] sda3[0] > 343758245 blocks super 1.2 [2/2] [UU] > > unused devices: > laptop1 ~ # I haven't put /proc explicitly on my /etc/fstab since a long time ago, and everything seems to be working. However, I use systemd, which always mounts /proc with the default options, and only uses the entry in /etc/fstab (if present) to override the default options. In other words, systemd always mounts /proc, no matter if it's listed in /etc/fstab or not. I don't know what OpenRC does, but it would not surprise me that it's something similar. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
[gentoo-user] To mount or not to Mount proc, that is the question
I've been trying to debug a problem where one laptop's networking, as controlled by wicd, seems to randomly go offline once in awhile. In the process of reviewing 5 machines I ran across an inconsistency across a bunch of my machines, new and old. It seems some of them mount proc in fstab while others do not. Some of these machines have been around for a few years not mounting proc and except for the laptop's networking issues there really haven't been any problems. Looking at the Gentoo amd64 install guide here: http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8 it appears that the recommendation is to mount proc. [QUOTE] /dev/sda1 /bootext2defaults,noatime 1 2 /dev/sda2 none swapsw 0 0 /dev/sda3 /ext3noatime 0 1 /dev/cdrom /mnt/cdrom autonoauto,user 0 0 proc/procprocdefaults 0 0 shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 [QUOTE] What would the issues be with proc not mounted? For instance, this machine doesn't mount proc in fstab but still has proc: laptop1 ~ # cat /etc/fstab /dev/sdb1 /boot ext2noauto,noatime 1 2 /dev/sdb4 / ext3noatime 0 1 /dev/sdb2 noneswapsw 0 0 /dev/cdrom /mnt/cdrom autonoauto,ro 0 0 shm /dev/shmtmpfs nodev,nosuid,noexec 0 0 laptop1 ~ # cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md127 : active (auto-read-only) raid1 sdb3[1] sda3[0] 343758245 blocks super 1.2 [2/2] [UU] unused devices: laptop1 ~ # Thanks, Mark
Re: [gentoo-user] Re: Backlight problems
On Fri, Mar 16, 2012 at 12:25 PM, Mark Knecht wrote: > acpi_listen on n-ArrowUp/Dn does produce a response so maybe I > don't have something properly mapped? It seems that on this Asus laptop the Fn-Arrow keys are mapped to audio events of some type. (Reading xev responses) Looking at my keyboard visually and interpreting the symbols it appears that the following key are what Asus intended for keyboard and monitor brightness: Fn-F3 - Keyboard brightness down Fn-F4 - Keyboard brightness up Fn-F5 - Monitor brightness down Fn-F6 - Monitor brightness up In acpi_listen all 4 keys produce events In xev only the keyboard brightness keys do anything. xev remains mute when trying the monitor keys. - Mark
Re: [gentoo-user] Re: Backlight problems
On Fri, Mar 16, 2012 at 11:55 AM, Grant wrote: >> Grant, >> Sorry I missed this thread earlier. I've got an Asus 17" laptop >> that I've been trying unsuccessfully to get the keyboard backlighting >> to work correctly for weeks (maybe months - I no longer remember how >> long) On my machine I get keyboard backlighting when I boot the >> machine, but if I turn off the lights with the switch on the machine I >> cannot so far turn them back on by any means. >> >> On this machine xbacklight -get responds that nothing has backlight >> properties so I've clearly got some configuration issues. >> >> As for the kernel I'm using vanilla-sources-3.2.10 so I don't think >> there's a lot that is newer than that. >> >> I don't care much about screen backlighting but keyboard >> backlighting is important to me. >> >> - Mark > > Hey Mark, I'm happy to say I just fixed the screen backlighting on my > system, but I'm sorry to say I don't think it will help you with > keyboard backlighting. To fix it, I removed 'acpi_backlight=vendor' > from grub and added 'echo 0 > > /sys/class/backlight/intel_backlight/brightness' to > /etc/local.d/backlight.start and made that file executable. Now > backlight control works perfectly via the keyboard shortcuts with no > other configuration and no xbacklight. I'm on > hardened-sources-3.2.2-r1. > > BTW, I noticed baselayout1.start and baselayout1.stop are no longer > created in /etc/local.d. > > - Grant > Hi Grant, OK, that's interesting info. Here's what I'm currently seeing: slinky ~ # uname -a Linux slinky 3.2.10 #1 SMP PREEMPT Tue Mar 13 09:45:35 PDT 2012 x86_64 Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz GenuineIntel GNU/Linux slinky ~ # ls -al /etc/local.d/ total 20 drwxr-xr-x 2 root root 4096 Feb 23 21:03 . drwxr-xr-x 72 root root 4096 Mar 16 11:53 .. -rw-r--r-- 1 root root 387 Feb 23 21:03 README -rwxr-xr-x 1 root root 123 May 3 2011 baselayout1.start -rwxr-xr-x 1 root root 217 May 3 2011 baselayout1.stop slinky ~ # ls -la /sys/class/backlight/asus_laptop/ total 0 drwxr-xr-x 2 root root0 Mar 16 04:35 . drwxr-xr-x 3 root root0 Mar 16 04:35 .. -r--r--r-- 1 root root 4096 Mar 16 12:09 actual_brightness -rw-r--r-- 1 root root 4096 Mar 16 12:09 bl_power -rw-r--r-- 1 root root 4096 Mar 16 11:40 brightness lrwxrwxrwx 1 root root0 Mar 16 12:09 device -> ../../../asus_laptop -r--r--r-- 1 root root 4096 Mar 16 11:40 max_brightness lrwxrwxrwx 1 root root0 Mar 16 04:35 subsystem -> ../../../../../class/backlight -r--r--r-- 1 root root 4096 Mar 16 12:09 type -rw-r--r-- 1 root root 4096 Mar 16 04:35 uevent slinky ~ # cat /sys/class/backlight/asus_laptop/brightness 15 slinky ~ # So, it seems to me that following your example, if I wanted to experiment with screen backlighting what would I do? I'm in KDE BTW in case we're doing something different in that regard. I see in the Global Keyboard Shortcuts in KDE that there are Monitor Brightness Down/Up controls defined but I'm not understanding what keys actually control those. I Googled around for a minute and found Fn-ArrowUp/ArrowDn but they didn't work o I'm hoping you can tell me and save me a few minutes. Maybe it's because I haven't started something required? acpi_listen on n-ArrowUp/Dn does produce a response so maybe I don't have something properly mapped? I do have baselayout1.start/stop stuff so it seems our systems are fairly different. Thank in advance, Mark
Re: [gentoo-user] Re: Backlight problems
On my just-released Dell XPS 13 Ultrabook, I can control the backlight with 'xbacklight -set 0' and 'xbacklight -set 100'. Any other values cause the screen to blink and flash. The keyboard backlight shortcuts don't work unless I map them to xbacklight 0 and 100. Also xbacklight doesn't work at all if I'm unplugged from AC. I've tried acpi_osi=Linux and acpi_backlight=vendor in grub.conf. acpi_osi doesn't seem to make any difference and xbacklight doesn't work at all without acpi_backlight. Do I just need to wait for a newer kernel? >>> >>> Does the gentoo install CD or a rescue CD give you any way to test the >>> same backlight functions? If the backlight works correctly when running >>> such a CD then listing the loaded kernel modules might give you a clue. >> >> I tried the latest Kubuntu and Ubuntu LiveCDs via unetbootin but the >> backlight behavior is the same as with Gentoo. Please let me know if >> anyone has any ideas on this. >> >> - Grant >> > > Grant, > Sorry I missed this thread earlier. I've got an Asus 17" laptop > that I've been trying unsuccessfully to get the keyboard backlighting > to work correctly for weeks (maybe months - I no longer remember how > long) On my machine I get keyboard backlighting when I boot the > machine, but if I turn off the lights with the switch on the machine I > cannot so far turn them back on by any means. > > On this machine xbacklight -get responds that nothing has backlight > properties so I've clearly got some configuration issues. > > As for the kernel I'm using vanilla-sources-3.2.10 so I don't think > there's a lot that is newer than that. > > I don't care much about screen backlighting but keyboard > backlighting is important to me. > > - Mark Hey Mark, I'm happy to say I just fixed the screen backlighting on my system, but I'm sorry to say I don't think it will help you with keyboard backlighting. To fix it, I removed 'acpi_backlight=vendor' from grub and added 'echo 0 > /sys/class/backlight/intel_backlight/brightness' to /etc/local.d/backlight.start and made that file executable. Now backlight control works perfectly via the keyboard shortcuts with no other configuration and no xbacklight. I'm on hardened-sources-3.2.2-r1. BTW, I noticed baselayout1.start and baselayout1.stop are no longer created in /etc/local.d. - Grant
Re: [gentoo-user] Re: Backlight problems
On Fri, Mar 16, 2012 at 10:58 AM, Grant wrote: >>> On my just-released Dell XPS 13 Ultrabook, I can control the backlight >>> with 'xbacklight -set 0' and 'xbacklight -set 100'. Any other values >>> cause the screen to blink and flash. The keyboard backlight shortcuts >>> don't work unless I map them to xbacklight 0 and 100. Also xbacklight >>> doesn't work at all if I'm unplugged from AC. I've tried >>> acpi_osi=Linux and acpi_backlight=vendor in grub.conf. acpi_osi >>> doesn't seem to make any difference and xbacklight doesn't work at all >>> without acpi_backlight. Do I just need to wait for a newer kernel? >> >> Does the gentoo install CD or a rescue CD give you any way to test the >> same backlight functions? If the backlight works correctly when running >> such a CD then listing the loaded kernel modules might give you a clue. > > I tried the latest Kubuntu and Ubuntu LiveCDs via unetbootin but the > backlight behavior is the same as with Gentoo. Please let me know if > anyone has any ideas on this. > > - Grant > Grant, Sorry I missed this thread earlier. I've got an Asus 17" laptop that I've been trying unsuccessfully to get the keyboard backlighting to work correctly for weeks (maybe months - I no longer remember how long) On my machine I get keyboard backlighting when I boot the machine, but if I turn off the lights with the switch on the machine I cannot so far turn them back on by any means. On this machine xbacklight -get responds that nothing has backlight properties so I've clearly got some configuration issues. As for the kernel I'm using vanilla-sources-3.2.10 so I don't think there's a lot that is newer than that. I don't care much about screen backlighting but keyboard backlighting is important to me. - Mark
Re: [gentoo-user] Re: LVM, /usr and really really bad thoughts.
Mike Edenfield wrote: >> From: Dale [mailto:rdalek1...@gmail.com] > >> This has been one of my points too. I could go out and buy me a bluetooth >> mouse/keyboard but I don't because it to complicates matters. > > I had a long reply to Walt that I (probably wisely) decided not to send, but > the basic point of it is also relevant here. My response to his (IMO > needlessly aggressive) email was basically this: > > Why *shouldn't I* be able to go but a Bluetooth keyboard and mouse if I > wanted to? Those things *work perfectly fine with udev*. And why wouldn't I > want to use the *same* solution for all of my various machines, even if that > solution is "overkill" for half of them? Just because my laptop doesn't need > bluetoothd support in udev doesn't mean using udev there *is bad*. (I don't > need 80% of what's in the Linux kernel but I still install one...) > > I am not in any way denigrating the work he's doing. I think it's awesome > and I've tried to help where I can. But I'm pretty fed up with people like > him acting as if the current udev solution is the end of the world. I've > heard it called everything from "design mistake" to "out of control truck > full of manure". > > I have three PCs in my home running Gentoo. Two of them would boot correctly > using Walt's new solution (mdev and no /usr mounted at boot) and one would > not. *All three of them* boot correctly using udev. 100% success > 66% > success, so clearly the udev solution is a perfectly legitimate solution to > a real world problem. At work, those numbers are likely different, and > Walt's solution might be a working approach -- if udev didn't already work > fine in 100% of those cases, too. > > Instead of asking why everyone else should be "forced" to use the udev > solution *that already works*, you should be focusing on explaining to > everyone else the reasons why it is worth the time and effort to configure > *something different* for those same machines. There was a reason why people > stopped using static /dev, and devfs; maybe there is a reason why people > should stop using udev, but thus far that reason seems to be "initramfs > makes us cranky." > > There's no need to get mean-spirited just because you choose a different > audience that freedesktop.org as the target for your solution. It just makes > you look petty and childish. Produce an alternative to > "udev/initramfs/single root" that works, provide (accurate) details on the > differences, and let users pick which one they want. > > --Mike > > > I have a question or two. If udev was going to *break* your bluetooth keyboard, what would you say then? To me, having a bluetooth keyboard is a bit out there. If udev was going to break a PS/2 keyboard, what would you say then? I suspect PS/2 keyboards outnumber bluetooth and most likely by a wide margin. Right now, udev is going to ruin my system while yours works. What if it was going to make my system work while breaking yours? Would you make the same argument? One other question, does your BIOS allow you to use your bluetooth keyboard? Just a thought. I'm going to take my meds. Ya'll argue for a while. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
Re: [gentoo-user] Re: Backlight problems
>> On my just-released Dell XPS 13 Ultrabook, I can control the backlight >> with 'xbacklight -set 0' and 'xbacklight -set 100'. Any other values >> cause the screen to blink and flash. The keyboard backlight shortcuts >> don't work unless I map them to xbacklight 0 and 100. Also xbacklight >> doesn't work at all if I'm unplugged from AC. I've tried >> acpi_osi=Linux and acpi_backlight=vendor in grub.conf. acpi_osi >> doesn't seem to make any difference and xbacklight doesn't work at all >> without acpi_backlight. Do I just need to wait for a newer kernel? > > Does the gentoo install CD or a rescue CD give you any way to test the > same backlight functions? If the backlight works correctly when running > such a CD then listing the loaded kernel modules might give you a clue. I tried the latest Kubuntu and Ubuntu LiveCDs via unetbootin but the backlight behavior is the same as with Gentoo. Please let me know if anyone has any ideas on this. - Grant
Re: [gentoo-user] How are Fn-F# ACPI events mapped?
On Tue, Mar 13, 2012 at 5:27 AM, YoYo Siska wrote: > On Sun, Mar 11, 2012 at 03:23:28PM -0700, Mark Knecht wrote: >> Hi, >> I'm trying to figure out how my Asus laptop maps function key >> events. This is being driven by an emerge message telling me that the >> acpi4asus package is being obsoleted and removed in 30 days and >> replaced by an in-kernel driver. I've removed the package and rebuilt >> my kernels to use this driver, and for vanilla-sources-3.2.7 the >> results are similar as with the acpi4asus package. > > don't know anything about the assus packages/drivers, but the general > direction in all such drivers is to move these things where they belong: > to the input subsystem, so my guess is the new driver doesn't produce > acpi events, but insted create a "input device" and produce key > press/release events on that device... > > (note that sleep / hibernate actions are usually still reported also > throgh acpi, because some programs expect them to come from there, that > would explaing your Fn-F1/sleep working) > > to test this, just run as root on the linux console (not in a termnal in > X): > > showkey -s > > and then pres the keys (ie Fn-F4,) to stop showkeys, just don't press > anything for 10 seconds... > if you see numbers appearing after each keypress / release, then the key > directly generates keyboard ivents and its possible you will see them > directly in X, for that jus run (now under X) > > xev > > and (the window that appears must have focus / be active) press the keys > again, xev will print the X keycodes/keysyms to its output... > if you see reasonable names there, then you should be able to map those > keys in the programs you are using (ie global hotkeys in kde, etc...) > note however that qt/kde doesn't recognise some of the more exotic > keysyms... (in my case XF86TouchpadToggle produced by Fn-F8 on > thinkpads ;) > > if you can see the key in showkey -s but not in xev, the problem might > be in kernel keyboard map (though i'm not sure if the x's evdev driver > uses that) or in the evdev driver not mapping that key > > basically the kernel driver reports scan codes (what showkey -s shows), > kernel translates that to keycodes (showkey -k to see them) and then X's > input driver (ie evdev) translates those to the X keycodes X server > again trasnlates them to keysym-s > > yoyo > Hi, Sorry about the late reply. I messed with this a few days ago but never wrote to say thanks. My bad. Basic outcome - there seemed to be three things I learned: 1) The basic message architecture, thanks to your post. Thanks for that. 2) There is some problem with vanilla-sources-3.2.9 which is apparently fixed in 3.2.10. Thanks to kernel devs I suppose for that. Almost all the function keys now produce some sort of message in acpi_listen, showkey & xev. 3) The function I seem to be missing at this point is being able to actually control the brightness of keyboard backlights. I can do this in Windows but not in Linux. However I don't know yet if Linux even has a driver with that capability so I'll have to spend some time looking for that over the weekend. Again, thanks for the response. It was quite helpful. Cheers, Mark
Re: [gentoo-user] gentoo on compiz problems
Hi Nilesh! Am 16.03.2012 13:49, schrieb Nilesh Govindrajan: > I think you need to be present in the video group. I am; > Clearly the problem is because access is denied to your video card. > Just ls -l /dev/nvidiactl (you should see group video there) tamer@office ~ $ ls -lA /dev/nvidiactl crw-rw 1 root video 195, 255 16. Mär 17:25 /dev/nvidiactl > yourself to the group. > > gpasswd -a video > It is. and I still get the same message :( NVIDIA: could not open the device file /dev/nvidiactl (Permission denied). I looked at my xorg.conf and added certain lines: At Section "ServerLayout" I added: Option"AIGLX" "true" At Section "Extensions" I added: Option "Composite" "Enable" an t Section "Screen" I added as well: Option "AddARGBGLXVisuals" "True" > If the group is something else as the ls -l reveals, add yourself to > that group (unless it's root or wheel). If the group is root or wheel, > you need to modify udev/mdev rules which I'm not aware of much. > but always, even if I run compiz-manager as root (sudo compiz-manager), I receive THIS ERROR: Checking for Xgl: not present and I am not getting smart what I did wrong. xorg was built with these flags: x11-base/xorg-server-1.11.2-r2 was built with the following: USE="ipv6 kdrive (multilib) nptl udev xorg -dmx -doc -minimal -static-libs -tslib -xnest -xvfb" LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,-z,lazy" here is my xorg.xonf. http://pastebin.mozilla.org/1522488 Tamer
Re: [gentoo-user] Beta test Gentoo with mdev instead of udev; version 5 - failure :-(
On Friday, March 16, 2012 08:46:05 AM Neil Bothwick wrote: > On Fri, 16 Mar 2012 07:13:46 +0100, Joost Roeleveld wrote: > > Auto-starting programs when a device is added. Great, when are we > > getting "autostart" support for CDs and USB-keys and under which > > user-account will these be executed? > > This is for running programs from the computer against the device, not > autorunning programs on the device - such as initialising USB modems. How long till autorunning programs becomes "the next great thing" on the desktop for Linux? > > That is, untill someone comes up with the "clever" idea of shoving an > > automounter into udev. (Will it then also auto-unmount when I want my > > CD back?) > > That's already been done, > > * sys-apps/uam > Available versions: 0.2.1 (~)0.3 > Homepage:https://github.com/mgorny/uam/ > Description: Simple udev-based automounter for removable USB > media This is an automounter, not autounmounter... What I would like is one where a CDrom is automounted when inserted and when I press the eject-button, the cdrom is umounted and I get my cd back... The action that (used to) cause BSODs on MS Windows... > I also have a rule on a headless media server to run a script that > mounts a USB stick, copies files to it, unmounts it and lets me know when > it is done. I can mark files for copying at any time and my wife can just > plug in a stick when she wants to copy them for viewing on a small, > non-connected TV by her treadmill (her treadmill, I emphasise - I find a > keyboard and trackball give me all the exercise I want). Why not connect that TV? ;) -- Joost
Re: [gentoo-user] gentoo on compiz problems
On Fri, Mar 16, 2012 at 3:00 PM, Tamer Higazi wrote: > Hi! > I am running a stable port of gentoo with gnome 2.31.1 and I want to run > compiz. > > How do I run compiz proparly?! I am pretty sure, that I do something > wrong. For any advise, I would thank you. > > > Tamer > > > > When I open gnome-terminal (shell) and run "compiz-manager" I get the > following output: > > > tamer@office ~ $ compiz-manager > Checking for Xgl: not present. > xset q doesn't reveal the location of the log file. Using fallback > /var/log/Xorg.0.log > Detected PCI ID for VGA: 04:00.0 0300: 10de:1244 (rev a1) (prog-if 00 > [VGA controller]) > Checking for texture_from_pixmap: present. > Checking for non power of two support: present. > Checking for Composite extension: present. > NVIDIA: could not open the device file /dev/nvidiactl (Permission denied). > Comparing resolution (1920x1080) to maximum 3D texture size (16384): Passed. > Checking for nVidia: present. > Checking for FBConfig: NVIDIA: could not open the device file > /dev/nvidiactl (Permission denied). > present. > Checking for Xgl: not present. > Starting emerald > NVIDIA: could not open the device file /dev/nvidiactl (Permission denied). > > > I think you need to be present in the video group. Clearly the problem is because access is denied to your video card. Just ls -l /dev/nvidiactl (you should see group video there) and add yourself to the group. gpasswd -a video If the group is something else as the ls -l reveals, add yourself to that group (unless it's root or wheel). If the group is root or wheel, you need to modify udev/mdev rules which I'm not aware of much. -- Nilesh Govindarajan http://nileshgr.com
Re: [gentoo-user] How can I trigger kernel panic?
Claudio Roberto França Pereira wrote: > Just to be sure, r e i s u b may be input in low case, without shift, right? > > Like hold Alt + SysRq and type r e i s u b then release Alt + SysRq? > > As the most experienced user of SysReq, that is correct. Thank hal for all the experience too. That #$*%^ *$&%^#*$&% piece of software. I hope udev follows that thing. ROFL Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
Re: [gentoo-user] mdev + xorg + Gnome up and running. :-)
Hello, Walter. On Thu, Mar 15, 2012 at 08:55:53PM -0400, Walter Dnes wrote: > On Thu, Mar 15, 2012 at 04:17:14AM +, Alan Mackenzie wrote > > Hi, Gentoo. > > Yes, I've got Gnome going under mdev. Thanks to Mike Edenfield for > > the tip about needing to configure things in xorg.conf. > > Here's how I did it: > Great. Is that GNOME version 2 or version 3? I'm working on getting > a simple webpage set up. The instructions and special cases are getting > to be a bit much for an email. I hope to have the webhosting account set > up on Friday, and DNS for the webpage propagated over the weekend. I'm still on Gnome 2. But I have a feeling it might not matter - couldn't it be that all the dev related code is in xorg-server? > -- > Walter Dnes -- Alan Mackenzie (Nuremberg, Germany).
[gentoo-user] gentoo on compiz problems
Hi! I am running a stable port of gentoo with gnome 2.31.1 and I want to run compiz. How do I run compiz proparly?! I am pretty sure, that I do something wrong. For any advise, I would thank you. Tamer When I open gnome-terminal (shell) and run "compiz-manager" I get the following output: tamer@office ~ $ compiz-manager Checking for Xgl: not present. xset q doesn't reveal the location of the log file. Using fallback /var/log/Xorg.0.log Detected PCI ID for VGA: 04:00.0 0300: 10de:1244 (rev a1) (prog-if 00 [VGA controller]) Checking for texture_from_pixmap: present. Checking for non power of two support: present. Checking for Composite extension: present. NVIDIA: could not open the device file /dev/nvidiactl (Permission denied). Comparing resolution (1920x1080) to maximum 3D texture size (16384): Passed. Checking for nVidia: present. Checking for FBConfig: NVIDIA: could not open the device file /dev/nvidiactl (Permission denied). present. Checking for Xgl: not present. Starting emerald NVIDIA: could not open the device file /dev/nvidiactl (Permission denied).
Re: [gentoo-user] virt-manager-0.9.1 broken?
Solved with patch from: https://bugs.gentoo.org/show_bug.cgi?id=329987
Re: [gentoo-user] decrypt a use flag - how to
On Fri, Mar 16, 2012 at 15:54, Helmut Jarausch
wrote:
> Hi,
>
> when I do
>
> emerge -vp sys-libs/glibc
>
> I see the use flag (-nls%*)
> What are these special characters '(' '%' and '*' about?
>
man emerge contains the complete information, search for "%" ;-)
But, in a nutshell:
The parens ( ) mean the flag's state (enabled/disabled) is forced by
the profile in use.
The "%" means there's a change of the flag (the flag gets deleted, or
forced, or a new flag)
The "*" means the flag's state has transitioned (enabled-->disabled or
vice versa)
In your case, I'd say the explanation would be: The nls flag for that
package was previously enabled (perhaps globally), but now it's forced
to be disabled by the profile.
CMIIW
Rgds,
--
FdS Pandu E Poluan
~ IT Optimizer ~
• LOPSA Member #15248
• Blog : http://pepoluan.tumblr.com
• Linked-In : http://id.linkedin.com/in/pepoluan
Re: [gentoo-user] mdev + xorg + Gnome up and running. :-)
On Fri, Mar 16, 2012 at 15:41, Joost Roeleveld wrote: > On Friday, March 16, 2012 02:54:16 PM Pandu Poluan wrote: >> What I have in mind for "helper scripts" would be (for example) a >> script to ensure that, on boot, ethernet devices will maintain their >> relative order. This needs to be stuck into /etc/mdev.conf (already >> part of stage3). >> >> (And if someone's well-versed enough in Linux, maybe he/she will >> convert the shellscript into a simple -- and faster -- binary with >> exact same functionality). > > I think you are talking about a script that handles a more "dynamic" database > to force renames/softlinks for devices keeping names identical? > I haven't played with mdev yet, but isn't that already in mdev? > Or does mdev require it to be set manually? > Well, to make mdev simple enough for embedded devices (whose devices always come up in the same order), busybox devs do not include any database of devices. However, mdev is perfectly able to execute a program (script or binary) when it detects a device coming up, and it can choose which program to execute based on the device name. Let's say you have two NICs, one will get eth0, the other will get eth1, depending on the order that the kernel initializes the device name. For that, you don't have to do a thing. However, if the devices somehow gets initialized at the same time (e.g., hotplug events), it's a toss which dev will get which name. That is why, the busybox devs recommended the "linuxrc" file to contain the line "mdev -s", which will handle dev initializations during boot in a sequential fashion, ensuring exact same device names. > Btw, the "keep same devicename" is rather annoying when having to replace the > network card and the network then doesn't come back up... > There are several scenarios: Scenario 1: eth1 is replaced, eth0 stays -- if the new card is initialized after eth0, it will automatically assume eth1. If the new card is initialized before eth0, it will become the new eth0, and the previous eth0 will become eth1 automatically. Scenario 2: eth0 is replaced, eth1 stays -- if the new card is initialized before eth1, it will automatically assume eth0. If the new card is initialized after eth1, the previous eth1 gets eth0, while the new card gets eth1. The program (script) I'm planning will have a simple 'database' (actually, a text file) containing pairs of MAC address and devname. This should ensure that devices with a certain MAC address will *always* get the same devname, while devices not listed in the database will get the first available devname. Thus, in the case where devname swapping would happen (see the second situation in Scenarios 1 & 2), *at least* the non-replaced device will get the exact devname as before replacement happens. Rgds, -- FdS Pandu E Poluan ~ IT Optimizer ~ • LOPSA Member #15248 • Blog : http://pepoluan.tumblr.com • Linked-In : http://id.linkedin.com/in/pepoluan
[gentoo-user] decrypt a use flag - how to
Hi,
when I do
emerge -vp sys-libs/glibc
I see the use flag(-nls%*)
What are these special characters '(' '%' and '*' about?
Many thanks for a hint,
Helmut.
Re: [gentoo-user] Re: LVM, /usr and really really bad thoughts.
On Fri, 16 Mar 2012 06:39:44 +0100, Joost Roeleveld wrote: > > Technically, we are all using an initramfs as all 2.6/3 kernels mount > > an initramfs when they load. If does not contain an init script, they > > fall back to the legacy behaviour. > > > > See /usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt > > Even when the init-options are not set? Yes, read the readme. > admin@hera ~ $ zcat /proc/config.gz | grep -i init > # CONFIG_BLK_DEV_INITRD is not set That's for an old style initrd, I don't have that set either. -- Neil Bothwick Oxymoron: Clearly Misunderstood. signature.asc Description: PGP signature
Re: [gentoo-user] Beta test Gentoo with mdev instead of udev; version 5 - failure :-(
On Fri, 16 Mar 2012 07:13:46 +0100, Joost Roeleveld wrote: > Auto-starting programs when a device is added. Great, when are we > getting "autostart" support for CDs and USB-keys and under which > user-account will these be executed? This is for running programs from the computer against the device, not autorunning programs on the device - such as initialising USB modems. > That is, untill someone comes up with the "clever" idea of shoving an > automounter into udev. (Will it then also auto-unmount when I want my > CD back?) That's already been done, * sys-apps/uam Available versions: 0.2.1 (~)0.3 Homepage:https://github.com/mgorny/uam/ Description: Simple udev-based automounter for removable USB media I also have a rule on a headless media server to run a script that mounts a USB stick, copies files to it, unmounts it and lets me know when it is done. I can mark files for copying at any time and my wife can just plug in a stick when she wants to copy them for viewing on a small, non-connected TV by her treadmill (her treadmill, I emphasise - I find a keyboard and trackball give me all the exercise I want). -- Neil Bothwick New Intel opcode #007 PUKE: Put unmeaningful keywords everywhere signature.asc Description: PGP signature
Re: [gentoo-user] mdev + xorg + Gnome up and running. :-)
On Friday, March 16, 2012 02:54:16 PM Pandu Poluan wrote:
> On Fri, Mar 16, 2012 at 14:32, Walter Dnes wrote:
> > On Fri, Mar 16, 2012 at 08:41:48AM +0700, Pandu Poluan wrote
> >
> > > Hmmm... are you planning to host an overlay?
> > >
> > > If so, I'll be willing to donate some of my time to provide some
> > > patched ebuilds for packages that can function without udev but
> > > lazily specify DEPEND=sys-fs/udev...
> >
> > I wouldn't call it "lazy". Before the hulabaloo about udev/initramfs,
> > I don't think anybody was running mdev on Gentoo. So there was no need
> > for mdev in the ebuilds. The only non-embedded distro to use mdev was
> > Alpine linux. And they also use uclibc.
>
> Ah yes, sorry. That was originally tongue-in-cheek, but I now see it
> may be too disparaging. My bad.
>
> > I'm not familiar with the server side of things. I can follow
> > instructions if supplied. I don't know if the hosting provider I'm
> > thinking of does rsync. I never theought to ask.
> >
> > I'll check on the dev list about the etiquitte regarding contacting
> > upstream. Even if a package works today with mdev, there's no guarantee
> > about tomorrow. It'll help if upstream knows that people are using
> > their packages with mdev, and they take that into account when updating
> > the software.
> >
> > Note that my request for updating virtual/dev-manager went through OK.
> > Once we test a "udev-required" package with mdev, and confirm it works,
> > we should post a request on the Gentoo bugzilla to update Gentoo's
> > ebuild.
>
> Good idea.
>
> > > ... and while at it, let's see if I can make a package containing
> > > scripts to ease transitioning from udev to mdev. Maybe call it,
> > > sys-utils/mdev-helper?
> >
> > The kernel reconfig and rebuild, and sticking "init=/sbin/linuxrc"
> > into the append line are user-specific. I dual-boot 2 kernels
> > ("production" and "experimental"), and I run lilo. Somebody with only
> > one kernel, and/or running GRUB will need to do things differently. So
> > a script won't help. This is simple enough to copy+paste from docs
> > to your terminal.
>
> Well... as to the kernel requirement... nothing's stopping one from
> emerging sys-fs/reiserfsprogs even when the kernel doesn't support
> reiserfs ;)
>
> The "init=/sbin/linuxrc" can be automated using script (and sed),
> which we can imbue with the intelligence necessary to edit LILO/GRUB
> conf. I do have a collection of my own scripts to make it easier to
> install new Gentoo systems; one of them I whup up to automatically add
> a new kernel into menu.lst and (optionally) modify the default kernel
> [1].
>
> What I have in mind for "helper scripts" would be (for example) a
> script to ensure that, on boot, ethernet devices will maintain their
> relative order. This needs to be stuck into /etc/mdev.conf (already
> part of stage3).
>
> (And if someone's well-versed enough in Linux, maybe he/she will
> convert the shellscript into a simple -- and faster -- binary with
> exact same functionality).
I think you are talking about a script that handles a more "dynamic" database
to force renames/softlinks for devices keeping names identical?
I haven't played with mdev yet, but isn't that already in mdev?
Or does mdev require it to be set manually?
Btw, the "keep same devicename" is rather annoying when having to replace the
network card and the network then doesn't come back up...
--
Joost
Re: [gentoo-user] mdev + xorg + Gnome up and running. :-)
On Fri, Mar 16, 2012 at 14:32, Walter Dnes wrote:
>
> On Fri, Mar 16, 2012 at 08:41:48AM +0700, Pandu Poluan wrote
>
> > Hmmm... are you planning to host an overlay?
> >
> > If so, I'll be willing to donate some of my time to provide some patched
> > ebuilds for packages that can function without udev but lazily specify
> > DEPEND=sys-fs/udev...
>
> I wouldn't call it "lazy". Before the hulabaloo about udev/initramfs,
> I don't think anybody was running mdev on Gentoo. So there was no need
> for mdev in the ebuilds. The only non-embedded distro to use mdev was
> Alpine linux. And they also use uclibc.
>
Ah yes, sorry. That was originally tongue-in-cheek, but I now see it
may be too disparaging. My bad.
> I'm not familiar with the server side of things. I can follow
> instructions if supplied. I don't know if the hosting provider I'm
> thinking of does rsync. I never theought to ask.
>
> I'll check on the dev list about the etiquitte regarding contacting
> upstream. Even if a package works today with mdev, there's no guarantee
> about tomorrow. It'll help if upstream knows that people are using
> their packages with mdev, and they take that into account when updating
> the software.
>
> Note that my request for updating virtual/dev-manager went through OK.
> Once we test a "udev-required" package with mdev, and confirm it works,
> we should post a request on the Gentoo bugzilla to update Gentoo's
> ebuild.
>
Good idea.
> > ... and while at it, let's see if I can make a package containing
> > scripts to ease transitioning from udev to mdev. Maybe call it,
> > sys-utils/mdev-helper?
>
> The kernel reconfig and rebuild, and sticking "init=/sbin/linuxrc"
> into the append line are user-specific. I dual-boot 2 kernels
> ("production" and "experimental"), and I run lilo. Somebody with only
> one kernel, and/or running GRUB will need to do things differently. So
> a script won't help. This is simple enough to copy+paste from docs
> to your terminal.
>
Well... as to the kernel requirement... nothing's stopping one from
emerging sys-fs/reiserfsprogs even when the kernel doesn't support
reiserfs ;)
The "init=/sbin/linuxrc" can be automated using script (and sed),
which we can imbue with the intelligence necessary to edit LILO/GRUB
conf. I do have a collection of my own scripts to make it easier to
install new Gentoo systems; one of them I whup up to automatically add
a new kernel into menu.lst and (optionally) modify the default kernel
[1].
What I have in mind for "helper scripts" would be (for example) a
script to ensure that, on boot, ethernet devices will maintain their
relative order. This needs to be stuck into /etc/mdev.conf (already
part of stage3).
(And if someone's well-versed enough in Linux, maybe he/she will
convert the shellscript into a simple -- and faster -- binary with
exact same functionality).
[1]
https://bitbucket.org/pepoluan/gentoo-admin-kit/src/4ed95722b38f/grub-add-kernel.sh
Rgds,
--
FdS Pandu E Poluan
~ IT Optimizer ~
• LOPSA Member #15248
• Blog : http://pepoluan.tumblr.com
• Linked-In : http://id.linkedin.com/in/pepoluan
Re: [gentoo-user] mdev + xorg + Gnome up and running. :-)
On Fri, Mar 16, 2012 at 08:41:48AM +0700, Pandu Poluan wrote
> Hmmm... are you planning to host an overlay?
>
> If so, I'll be willing to donate some of my time to provide some patched
> ebuilds for packages that can function without udev but lazily specify
> DEPEND=sys-fs/udev...
I wouldn't call it "lazy". Before the hulabaloo about udev/initramfs,
I don't think anybody was running mdev on Gentoo. So there was no need
for mdev in the ebuilds. The only non-embedded distro to use mdev was
Alpine linux. And they also use uclibc.
I'm not familiar with the server side of things. I can follow
instructions if supplied. I don't know if the hosting provider I'm
thinking of does rsync. I never theought to ask.
I'll check on the dev list about the etiquitte regarding contacting
upstream. Even if a package works today with mdev, there's no guarantee
about tomorrow. It'll help if upstream knows that people are using
their packages with mdev, and they take that into account when updating
the software.
Note that my request for updating virtual/dev-manager went through OK.
Once we test a "udev-required" package with mdev, and confirm it works,
we should post a request on the Gentoo bugzilla to update Gentoo's
ebuild.
> ... and while at it, let's see if I can make a package containing
> scripts to ease transitioning from udev to mdev. Maybe call it,
> sys-utils/mdev-helper?
The kernel reconfig and rebuild, and sticking "init=/sbin/linuxrc"
into the append line are user-specific. I dual-boot 2 kernels
("production" and "experimental"), and I run lilo. Somebody with only
one kernel, and/or running GRUB will need to do things differently. So
a script won't help. This is simple enough to copy+paste from docs
to your terminal.
--
Walter Dnes
