[gentoo-user] Will ZFS clobber my MBR?
Hello, My / (root) lives on /dev/sdb1. My /dev/sda has no partitions and no data except for what I presume is the mbr written by lilo. [history: sdb is an SSD and I never wanted to use the slow sda] I have been playing with ZFS on a USB drive and I am ready to create a zpool on /dev/sda. ZFS recommends that I give it the entire drive (partitioning discouraged). In this case I hesitate to give ZFS my entire drive as I worry ZFS will clobber my MBR rendering my system unbootable. Are my fears warranted? If so, what should I do about it? If you recommend that I partition sda, what parameters do I used to avoid a clobber? Thank you, Chris
Re: [gentoo-user] Will ZFS clobber my MBR?
Am 22.01.2014 10:01, schrieb Chris Stankevitz: Hello, My / (root) lives on /dev/sdb1. My /dev/sda has no partitions and no data except for what I presume is the mbr written by lilo. [history: sdb is an SSD and I never wanted to use the slow sda] I have been playing with ZFS on a USB drive and I am ready to create a zpool on /dev/sda. ZFS recommends that I give it the entire drive (partitioning discouraged). In this case I hesitate to give ZFS my entire drive as I worry ZFS will clobber my MBR rendering my system unbootable. Are my fears warranted? If so, what should I do about it? If you recommend that I partition sda, what parameters do I used to avoid a clobber? I don't know if creating a ZFS volume on /dev/sda kill break your mbr. But why don't you install lilo on /dev/sdb ? You change change the boot order in BIOS after that. signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] webcam software
On Tue, Jan 21 2014, Canek Peláez Valdés wrote: On Tue, Jan 21, 2014 at 9:30 PM, gottl...@nyu.edu wrote: On Sat, Jan 18 2014, Canek Peláez Valdés wrote: On Jan 18, 2014 4:02 PM, gottl...@nyu.edu wrote: My main system is a dell latitude E6430s. I am embarrassed to say that, although I have had this system for a while, I just now realized that it has a build in webcam. What software do you recommend and what should I start reading to learn how to use it. To play with it, and of you already use GNOME, I recommend Cheese. It's actually fun to use. Thank you canek (and walt, james, and eroen) but I didn't make clear the level of my ignorance. I have never used a webcam, but I recently became a grandfather so figured I should learn. I must need a driver for the camera. According to lsusb I have Bus 001 Device 004: ID 0c45:646b Microdia (the 400 line verbose output is at the end of this msg). [snip] But, as I mentioned, I am a complete novice with webcams and wonder if I am way off base here. Is the above the right path to follow? [Humongous snip] Ah, you need first the drivers then. Don't bother with out-of-tree drivers. Try (directly in your kernel) USB_VIDEO_CLASS (a.k.a. UVC), CONFIG_USB_GSPCA, and if that doesn't work enable all of CONFIG_USB_GSPCA_*. Mine works only with CONFIG_USB_GSPCA. After loading the modules, or booting with the new kernel, see if you have /dev/v4l (it's a dir). Then any modern software (e.g., Cheese or google-talkplugin) will autodetect the camera. Regards. Sounds like a plan. thanks, allan
Re: [gentoo-user] OT - memory testing
Hiya Mick; Thanks for your response. Great ideas. I'll pass it along. -Skippy On 1/21/2014 11:42 PM, Mick wrote: On Tuesday 21 Jan 2014 23:11:24 Skippy wrote: Have you ever found a program in linux that allows you to locate bad dims if you have faults? I’ve tried memtest86, memconf, memtester and none of them can point out what slot on the motherboard has the bad RAM. memtest86+ is what I use, but I have not found an application that will identify and report on its own a faulty module or controller out of a whole bank of them. Press F2 when it starts, to enable SMT support and get the tests done a bit faster. I know usually you just plug in one at a time. But memtest86 takes hours and I have…wait for it….16 slots to test DIMs on for this specific server with memory failure. You don't have to test 16 modules one at a time, although you will have to run the test more than once: Remove half (8) of the memory modules. Ensure what is left is installed in the slot combination recommended by the MoBo manufacturer. Test these. If no fault is found swap them for the other half. As soon as a fault is reported, remove half of this batch (4) and install the other 4 as recommended by the MoBo manufacturer. Rinse and repeat. This way you will eventually isolate the dodgy DIMM module, by running the test fewer than 16 times. Usually errors show in the first round of tests, but some times you may need to wait for more than 8 passes. Before you start any of this it is a good idea to just reseat the modules one at a time in case you have some dirt or oxidisation in any of the contacts. That could save a lot of hours ... Make sure you have marked clearly which batches have showed no errors - if you mix them up you will have to start from the beginning. I know I am stating the obvious, but I have been there with colleagues who like to tidy up other people's work space sigh.
Re: [gentoo-user] cannot boot using systemd and initrd
Mike Gilbert flop...@gentoo.org wrote: On Mon, Jan 20, 2014 at 7:38 AM, cov...@ccs.covici.com wrote: Hi. I am having a problem booting using systemd and an initrd generated by genkernel. I get the message that says (may be slight paraphrase) that /dev/mapper/linux--files-64--root does not appear to be a valid /, try again. Now in the gentoo guide to systemd, I did what I think it wanted me to do and wrote in my lilo append line real_init=/usr/lib/systemd/systemd . Now looking at the linuxsrc in the initrd, /usr is not even mounted when it is looking for its init -- after all that fuss about /usr -- and it only seems to look in /sbin for its init and dies. How can I solve this problem -- I suppose I could copy systemd over, but that seems nasty to me and I would have to remember to update it every time systemd was updated! Any assistance on this would be appreciated. This is bug 479730. https://bugs.gentoo.org/show_bug.cgi?id=479730 One solution would be to switch to genkernel-next. I recommend the latest ~arch version. Another solution would be to use dracut. OK, thanks -- gentoo-next looks like a good solution -- I hope it will still work with openrc since until I am sure systemd will do what I need, I will use openrc and forget gnome exists. Thanks again. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] webcam software
On Wednesday 22 Jan 2014 12:52:25 gottl...@nyu.edu wrote: On Tue, Jan 21 2014, Canek Peláez Valdés wrote: On Tue, Jan 21, 2014 at 9:30 PM, gottl...@nyu.edu wrote: On Sat, Jan 18 2014, Canek Peláez Valdés wrote: On Jan 18, 2014 4:02 PM, gottl...@nyu.edu wrote: My main system is a dell latitude E6430s. I am embarrassed to say that, although I have had this system for a while, I just now realized that it has a build in webcam. What software do you recommend and what should I start reading to learn how to use it. To play with it, and of you already use GNOME, I recommend Cheese. It's actually fun to use. Thank you canek (and walt, james, and eroen) but I didn't make clear the level of my ignorance. I have never used a webcam, but I recently became a grandfather so figured I should learn. I must need a driver for the camera. According to lsusb I have Bus 001 Device 004: ID 0c45:646b Microdia (the 400 line verbose output is at the end of this msg). [snip] But, as I mentioned, I am a complete novice with webcams and wonder if I am way off base here. Is the above the right path to follow? [Humongous snip] Ah, you need first the drivers then. Don't bother with out-of-tree drivers. Try (directly in your kernel) USB_VIDEO_CLASS (a.k.a. UVC), CONFIG_USB_GSPCA, and if that doesn't work enable all of CONFIG_USB_GSPCA_*. Mine works only with CONFIG_USB_GSPCA. After loading the modules, or booting with the new kernel, see if you have /dev/v4l (it's a dir). Then any modern software (e.g., Cheese or google-talkplugin) will autodetect the camera. Regards. Sounds like a plan. thanks, allan I have a similar camera (from lsusb): idVendor 0x0c45 Microdia idProduct 0x640e bcdDevice 95.06 iManufacturer 2 M092S-J00-9C14-SC1NT iProduct1 Laptop_Integrated_Webcam_2M These are modules enabled in the kernel: $ egrep -i GSPCA /usr/src/linux/.config CONFIG_USB_GSPCA=m # CONFIG_USB_GSPCA_BENQ is not set # CONFIG_USB_GSPCA_CONEX is not set # CONFIG_USB_GSPCA_CPIA1 is not set # CONFIG_USB_GSPCA_ETOMS is not set # CONFIG_USB_GSPCA_FINEPIX is not set # CONFIG_USB_GSPCA_JEILINJ is not set # CONFIG_USB_GSPCA_JL2005BCD is not set # CONFIG_USB_GSPCA_KINECT is not set # CONFIG_USB_GSPCA_KONICA is not set # CONFIG_USB_GSPCA_MARS is not set # CONFIG_USB_GSPCA_MR97310A is not set # CONFIG_USB_GSPCA_NW80X is not set # CONFIG_USB_GSPCA_OV519 is not set # CONFIG_USB_GSPCA_OV534 is not set # CONFIG_USB_GSPCA_OV534_9 is not set # CONFIG_USB_GSPCA_PAC207 is not set # CONFIG_USB_GSPCA_PAC7302 is not set # CONFIG_USB_GSPCA_PAC7311 is not set # CONFIG_USB_GSPCA_SE401 is not set # CONFIG_USB_GSPCA_SN9C2028 is not set CONFIG_USB_GSPCA_SN9C20X=m CONFIG_USB_GSPCA_SONIXB=m CONFIG_USB_GSPCA_SONIXJ=m # CONFIG_USB_GSPCA_SPCA500 is not set # CONFIG_USB_GSPCA_SPCA501 is not set # CONFIG_USB_GSPCA_SPCA505 is not set # CONFIG_USB_GSPCA_SPCA506 is not set # CONFIG_USB_GSPCA_SPCA508 is not set # CONFIG_USB_GSPCA_SPCA561 is not set # CONFIG_USB_GSPCA_SPCA1528 is not set # CONFIG_USB_GSPCA_SQ905 is not set # CONFIG_USB_GSPCA_SQ905C is not set # CONFIG_USB_GSPCA_SQ930X is not set # CONFIG_USB_GSPCA_STK014 is not set # CONFIG_USB_GSPCA_STV0680 is not set # CONFIG_USB_GSPCA_SUNPLUS is not set # CONFIG_USB_GSPCA_T613 is not set # CONFIG_USB_GSPCA_TOPRO is not set # CONFIG_USB_GSPCA_TV8532 is not set # CONFIG_USB_GSPCA_VC032X is not set # CONFIG_USB_GSPCA_VICAM is not set # CONFIG_USB_GSPCA_XIRLINK_CIT is not set # CONFIG_USB_GSPCA_ZC3XX is not set I can't recall how I arrived at these, but probably Google helped me at the time. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] g++ -fnothrow-opt
Hi list! I'm wondering if anyone tried setting -fnothrow-opt as a CXX_FLAG in make.conf? It makes C++ throw() statements behave like C++11 nothrow. This could have measurable performance benefits and will reduce code size. The only downside is that, when a function violates its throw() guarantee, terminate() will be called instead of unexpected(). However, neither function is allowed to do anything but terminate the program. So all you possibly lose is a meaningful error message just before the program crashes. So, what do you think? Safe to enable by default? Thanks in advance! Florian Philipp signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] webcam software
On Wed, Jan 22 2014, Mick wrote: On Wednesday 22 Jan 2014 12:52:25 gottl...@nyu.edu wrote: On Tue, Jan 21 2014, Canek Peláez Valdés wrote: On Tue, Jan 21, 2014 at 9:30 PM, gottl...@nyu.edu wrote: On Sat, Jan 18 2014, Canek Peláez Valdés wrote: On Jan 18, 2014 4:02 PM, gottl...@nyu.edu wrote: My main system is a dell latitude E6430s. I am embarrassed to say that, although I have had this system for a while, I just now realized that it has a build in webcam. What software do you recommend and what should I start reading to learn how to use it. To play with it, and of you already use GNOME, I recommend Cheese. It's actually fun to use. Thank you canek (and walt, james, and eroen) but I didn't make clear the level of my ignorance. I have never used a webcam, but I recently became a grandfather so figured I should learn. I must need a driver for the camera. According to lsusb I have Bus 001 Device 004: ID 0c45:646b Microdia (the 400 line verbose output is at the end of this msg). [snip] But, as I mentioned, I am a complete novice with webcams and wonder if I am way off base here. Is the above the right path to follow? [Humongous snip] Ah, you need first the drivers then. Don't bother with out-of-tree drivers. Try (directly in your kernel) USB_VIDEO_CLASS (a.k.a. UVC), CONFIG_USB_GSPCA, and if that doesn't work enable all of CONFIG_USB_GSPCA_*. Mine works only with CONFIG_USB_GSPCA. After loading the modules, or booting with the new kernel, see if you have /dev/v4l (it's a dir). Then any modern software (e.g., Cheese or google-talkplugin) will autodetect the camera. Regards. Sounds like a plan. thanks, allan I have a similar camera (from lsusb): idVendor 0x0c45 Microdia idProduct 0x640e bcdDevice 95.06 iManufacturer 2 M092S-J00-9C14-SC1NT iProduct1 Laptop_Integrated_Webcam_2M These are modules enabled in the kernel: $ egrep -i GSPCA /usr/src/linux/.config CONFIG_USB_GSPCA=m # CONFIG_USB_GSPCA_BENQ is not set # CONFIG_USB_GSPCA_CONEX is not set # CONFIG_USB_GSPCA_CPIA1 is not set # CONFIG_USB_GSPCA_ETOMS is not set # CONFIG_USB_GSPCA_FINEPIX is not set # CONFIG_USB_GSPCA_JEILINJ is not set # CONFIG_USB_GSPCA_JL2005BCD is not set # CONFIG_USB_GSPCA_KINECT is not set # CONFIG_USB_GSPCA_KONICA is not set # CONFIG_USB_GSPCA_MARS is not set # CONFIG_USB_GSPCA_MR97310A is not set # CONFIG_USB_GSPCA_NW80X is not set # CONFIG_USB_GSPCA_OV519 is not set # CONFIG_USB_GSPCA_OV534 is not set # CONFIG_USB_GSPCA_OV534_9 is not set # CONFIG_USB_GSPCA_PAC207 is not set # CONFIG_USB_GSPCA_PAC7302 is not set # CONFIG_USB_GSPCA_PAC7311 is not set # CONFIG_USB_GSPCA_SE401 is not set # CONFIG_USB_GSPCA_SN9C2028 is not set CONFIG_USB_GSPCA_SN9C20X=m CONFIG_USB_GSPCA_SONIXB=m CONFIG_USB_GSPCA_SONIXJ=m # CONFIG_USB_GSPCA_SPCA500 is not set # CONFIG_USB_GSPCA_SPCA501 is not set # CONFIG_USB_GSPCA_SPCA505 is not set # CONFIG_USB_GSPCA_SPCA506 is not set # CONFIG_USB_GSPCA_SPCA508 is not set # CONFIG_USB_GSPCA_SPCA561 is not set # CONFIG_USB_GSPCA_SPCA1528 is not set # CONFIG_USB_GSPCA_SQ905 is not set # CONFIG_USB_GSPCA_SQ905C is not set # CONFIG_USB_GSPCA_SQ930X is not set # CONFIG_USB_GSPCA_STK014 is not set # CONFIG_USB_GSPCA_STV0680 is not set # CONFIG_USB_GSPCA_SUNPLUS is not set # CONFIG_USB_GSPCA_T613 is not set # CONFIG_USB_GSPCA_TOPRO is not set # CONFIG_USB_GSPCA_TV8532 is not set # CONFIG_USB_GSPCA_VC032X is not set # CONFIG_USB_GSPCA_VICAM is not set # CONFIG_USB_GSPCA_XIRLINK_CIT is not set # CONFIG_USB_GSPCA_ZC3XX is not set I can't recall how I arrived at these, but probably Google helped me at the time. Thank you Mick. allan
[gentoo-user] Re: webcam software
On 01/21/2014 07:30 PM, gottl...@nyu.edu wrote: I recently became a grandfather... OMG! You're the youngest person in this group :)
[gentoo-user] trouble with gentoo-sources-3.10.25 and gnome
Today, on one amd64/systemd machine, I tried updating 3.10.17 to 3.10.25. As expected make oldconfig showed nothing new, so I thought the new kernel would just work. However gdm failed, with several pairs of messages Jan 22 17:04:49 localhost gdm[276]: GLib-GObject: g_object_ref: assertion `object-ref_count 0' failed. Jan 22 17:04:49 localhost gdm[276]: GLib-GObject: g_object_unref: assertion `object-ref_count 0' failed. Has anyone had a similar problem, and perhaps a fix? Since 3.10.17 works fine for me, my current plan is to wait for the next stable kernel ebuild to hit and hope that one is better thanks, allan PS some more context from journalctl (the lines are very long) Jan 22 17:04:48 localhost ntpd[318]: Listen normally on 5 wired fe80::21e:c9ff:fe48:f9a0 UDP 123 Jan 22 17:04:48 localhost ntpd[318]: peers refreshed Jan 22 17:04:49 localhost gdm[276]: Child process 297 was already dead. Jan 22 17:04:49 localhost gdm[276]: GLib-GObject: g_object_ref: assertion `object-ref_count 0' failed Jan 22 17:04:49 localhost gdm[276]: GLib-GObject: g_object_unref: assertion `object-ref_count 0' failed Jan 22 17:04:49 localhost dbus-daemon[272]: dbus[272]: [system] Rejected send message, 1 matched rules; type=method_call, sender=:1.1 (uid=0 pid=276 comm=/usr/sbin/gdm ) interface=org.freedesktop.DBus.Properties member=GetAll error name=(unset) requested_reply=0 destination=:1.6 (uid=0 pid=391 comm=/usr/libexec/gdm-simple-slave --display-id /org/gn) Jan 22 17:04:49 localhost dbus[272]: [system] Rejected send message, 1 matched rules; type=method_call, sender=:1.1 (uid=0 pid=276 comm=/usr/sbin/gdm ) interface=org.freedesktop.DBus.Properties member=GetAll error name=(unset) requested_reply=0 destination=:1.6 (uid=0 pid=391 comm=/usr/libexec/gdm-simple-slave --display-id /org/gn) Jan 22 17:04:49 localhost gdm[276]: Child process 395 was already dead. Jan 22 17:04:49 localhost gdm[276]: GLib-GObject: g_object_ref: assertion `object-ref_count 0' failed Jan 22 17:04:49 localhost gdm[276]: GLib-GObject: g_object_unref: assertion `object-ref_count 0' failed Jan 22 17:04:49 localhost gdm[276]: GdmDisplay: display lasted 0.050362 seconds Jan 22 17:04:49 localhost dbus-daemon[272]: dbus[272]: [system] Rejected send message, 1 matched rules; type=method_call, sender=:1.1 (uid=0 pid=276 comm=/usr/sbin/gdm ) interface=org.freedesktop.DBus.Properties member=GetAll error name=(unset) requested_reply=0 destination=:1.7 (uid=0 pid=397 comm=/usr/libexec/gdm-simple-slave --display-id /org/gn) Jan 22 17:04:49 localhost dbus[272]: [system] Rejected send message, 1 matched rules; type=method_call, sender=:1.1 (uid=0 pid=276 comm=/usr/sbin/gdm ) interface=org.freedesktop.DBus.Properties member=GetAll error name=(unset) requested_reply=0 destination=:1.7 (uid=0 pid=397 comm=/usr/libexec/gdm-simple-slave --display-id /org/gn) Jan 22 17:04:49 localhost gdm[276]: Child process 401 was already dead.
[gentoo-user] Re: Will ZFS clobber my MBR?
On Wednesday, January 22, 2014, Michael Hampicke m...@hadt.biz wrote: But why don't you install lilo on /dev/sdb? You change change the boot order in BIOS after that. Michael, Thank you, that worked perfectly. Chris
Re: [gentoo-user] Re: webcam software
On Wed, Jan 22 2014, walt wrote: On 01/21/2014 07:30 PM, gottl...@nyu.edu wrote: I recently became a grandfather... OMG! You're the youngest person in this group :) Well I was born (just) before WWII ended, specifically 2 aug 45. I hadn't considered the possibility that I was younger than anyone! :-) allan
Re: [gentoo-user] Re: Will ZFS clobber my MBR?
On 23/01/14 07:58, Chris Stankevitz wrote: On Wednesday, January 22, 2014, Michael Hampicke m...@hadt.biz wrote: But why don't you install lilo on /dev/sdb? You change change the boot order in BIOS after that. Michael, Thank you, that worked perfectly. Chris Being someone who is always fiddling with a machines innards ... I usually embed grub in multiple disks with the menu sometimes pointing to a rescue partition as well as the main system - saved me a few times. However, a systemrescuecd usb stick is my current fallback ... and after a couple of such rescues I think grub2 sucks :) BillK
Re: [gentoo-user] trouble with gentoo-sources-3.10.25 and gnome
On Jan 22, 2014 5:55 PM, gottl...@nyu.edu wrote: Today, on one amd64/systemd machine, I tried updating 3.10.17 to 3.10.25. As expected make oldconfig showed nothing new, so I thought the new kernel would just work. However gdm failed, with several pairs of messages Jan 22 17:04:49 localhost gdm[276]: GLib-GObject: g_object_ref: assertion `object-ref_count 0' failed. Jan 22 17:04:49 localhost gdm[276]: GLib-GObject: g_object_unref: assertion `object-ref_count 0' failed. Has anyone had a similar problem, and perhaps a fix? Since 3.10.17 works fine for me, my current plan is to wait for the next stable kernel ebuild to hit and hope that one is better thanks, allan PS some more context from journalctl (the lines are very long) Jan 22 17:04:48 localhost ntpd[318]: Listen normally on 5 wired fe80::21e:c9ff:fe48:f9a0 UDP 123 Jan 22 17:04:48 localhost ntpd[318]: peers refreshed Jan 22 17:04:49 localhost gdm[276]: Child process 297 was already dead. Jan 22 17:04:49 localhost gdm[276]: GLib-GObject: g_object_ref: assertion `object-ref_count 0' failed Jan 22 17:04:49 localhost gdm[276]: GLib-GObject: g_object_unref: assertion `object-ref_count 0' failed Jan 22 17:04:49 localhost dbus-daemon[272]: dbus[272]: [system] Rejected send message, 1 matched rules; type=method_call, sender=:1.1 (uid=0 pid=276 comm=/usr/sbin/gdm ) interface=org.freedesktop.DBus.Properties member=GetAll error name=(unset) requested_reply=0 destination=:1.6 (uid=0 pid=391 comm=/usr/libexec/gdm-simple-slave --display-id /org/gn) Jan 22 17:04:49 localhost dbus[272]: [system] Rejected send message, 1 matched rules; type=method_call, sender=:1.1 (uid=0 pid=276 comm=/usr/sbin/gdm ) interface=org.freedesktop.DBus.Properties member=GetAll error name=(unset) requested_reply=0 destination=:1.6 (uid=0 pid=391 comm=/usr/libexec/gdm-simple-slave --display-id /org/gn) Jan 22 17:04:49 localhost gdm[276]: Child process 395 was already dead. Jan 22 17:04:49 localhost gdm[276]: GLib-GObject: g_object_ref: assertion `object-ref_count 0' failed Jan 22 17:04:49 localhost gdm[276]: GLib-GObject: g_object_unref: assertion `object-ref_count 0' failed Jan 22 17:04:49 localhost gdm[276]: GdmDisplay: display lasted 0.050362 seconds Jan 22 17:04:49 localhost dbus-daemon[272]: dbus[272]: [system] Rejected send message, 1 matched rules; type=method_call, sender=:1.1 (uid=0 pid=276 comm=/usr/sbin/gdm ) interface=org.freedesktop.DBus.Properties member=GetAll error name=(unset) requested_reply=0 destination=:1.7 (uid=0 pid=397 comm=/usr/libexec/gdm-simple-slave --display-id /org/gn) Jan 22 17:04:49 localhost dbus[272]: [system] Rejected send message, 1 matched rules; type=method_call, sender=:1.1 (uid=0 pid=276 comm=/usr/sbin/gdm ) interface=org.freedesktop.DBus.Properties member=GetAll error name=(unset) requested_reply=0 destination=:1.7 (uid=0 pid=397 comm=/usr/libexec/gdm-simple-slave --display-id /org/gn) Jan 22 17:04:49 localhost gdm[276]: Child process 401 was already dead. Really? It works with one kernel, but not the other? Are you sure both kernels boot with init=/usr/lib/systemd/systemd? Regard.
Re: [gentoo-user] trouble with gentoo-sources-3.10.25 and gnome
On Wed, Jan 22 2014, Canek Peláez Valdés wrote: On Jan 22, 2014 5:55 PM, gottl...@nyu.edu wrote: Today, on one amd64/systemd machine, I tried updating 3.10.17 to 3.10.25. As expected make oldconfig showed nothing new, so I thought the new kernel would just work. However gdm failed, with several pairs of messages Jan 22 17:04:49 localhost gdm[276]: GLib-GObject: g_object_ref: assertion `object-ref_count 0' failed. Jan 22 17:04:49 localhost gdm[276]: GLib-GObject: g_object_unref: assertion `object-ref_count 0' failed. Has anyone had a similar problem, and perhaps a fix? Since 3.10.17 works fine for me, my current plan is to wait for the next stable kernel ebuild to hit and hope that one is better thanks, Really? It works with one kernel, but not the other? Surprised me too. I does work, i.e. the system boots and I can use the text terminals, but gdm is a nogo Are you sure both kernels boot with init=/usr/lib/systemd/systemd? I think so. For one thing the output I included is from journalctl. This system is grub1 and here is grub.conf default 0 timeout 10 splashimage=(hd0,2)/boot/grub/splash.xpm.gz title Gentoo Linux (vmlinuz) root (hd0,2) kernel /boot/vmlinuz root=/dev/sda3 init=/usr/lib/systemd/systemd title Gentoo Linux, Previous Compilation (vmlinuz.old) root (hd0,2) kernel /boot/vmlinuz.old root=/dev/sda3 init=/usr/lib/systemd/systemd title Gentoo Linux, known working (vmlinuz.works) root (hd0,2) kernel /boot/vmlinuz.works root=/dev/sda3 init=/usr/lib/systemd/systemd single title Windows Vista rootnoverify (hd0,1) makeactive chainloader +1 All I change is the target of /boot/vmlinuz, System.map, and config allan
Re: [gentoo-user] trouble with gentoo-sources-3.10.25 and gnome
On Wed, Jan 22, 2014 at 7:54 PM, gottl...@nyu.edu wrote: On Wed, Jan 22 2014, Canek Peláez Valdés wrote: On Jan 22, 2014 5:55 PM, gottl...@nyu.edu wrote: Today, on one amd64/systemd machine, I tried updating 3.10.17 to 3.10.25. As expected make oldconfig showed nothing new, so I thought the new kernel would just work. However gdm failed, with several pairs of messages Jan 22 17:04:49 localhost gdm[276]: GLib-GObject: g_object_ref: assertion `object-ref_count 0' failed. Jan 22 17:04:49 localhost gdm[276]: GLib-GObject: g_object_unref: assertion `object-ref_count 0' failed. Has anyone had a similar problem, and perhaps a fix? Since 3.10.17 works fine for me, my current plan is to wait for the next stable kernel ebuild to hit and hope that one is better thanks, Really? It works with one kernel, but not the other? Surprised me too. I does work, i.e. the system boots and I can use the text terminals, but gdm is a nogo Are you sure both kernels boot with init=/usr/lib/systemd/systemd? I think so. For one thing the output I included is from journalctl. This system is grub1 and here is grub.conf default 0 timeout 10 splashimage=(hd0,2)/boot/grub/splash.xpm.gz title Gentoo Linux (vmlinuz) root (hd0,2) kernel /boot/vmlinuz root=/dev/sda3 init=/usr/lib/systemd/systemd title Gentoo Linux, Previous Compilation (vmlinuz.old) root (hd0,2) kernel /boot/vmlinuz.old root=/dev/sda3 init=/usr/lib/systemd/systemd title Gentoo Linux, known working (vmlinuz.works) root (hd0,2) kernel /boot/vmlinuz.works root=/dev/sda3 init=/usr/lib/systemd/systemd single title Windows Vista rootnoverify (hd0,1) makeactive chainloader +1 All I change is the target of /boot/vmlinuz, System.map, and config Oh, I just got it too. It's neither gdm nor systemd; it's the nvidia binary module. Check lsmod, I bet you don't have it loaded, and dmesg will have nvidia: Unknown symbol acpi_os_wait_events_complete (err 0). No nvidia, no X, no X, no gdm (although the error message it gives does sound weird). I'm checking how to get the nvidia drivers in 3.13. 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] trouble with gentoo-sources-3.10.25 and gnome
On Wed, Jan 22, 2014 at 11:13 PM, Canek Peláez Valdés can...@gmail.com wrote: On Wed, Jan 22, 2014 at 7:54 PM, gottl...@nyu.edu wrote: On Wed, Jan 22 2014, Canek Peláez Valdés wrote: On Jan 22, 2014 5:55 PM, gottl...@nyu.edu wrote: Today, on one amd64/systemd machine, I tried updating 3.10.17 to 3.10.25. As expected make oldconfig showed nothing new, so I thought the new kernel would just work. However gdm failed, with several pairs of messages Jan 22 17:04:49 localhost gdm[276]: GLib-GObject: g_object_ref: assertion `object-ref_count 0' failed. Jan 22 17:04:49 localhost gdm[276]: GLib-GObject: g_object_unref: assertion `object-ref_count 0' failed. Has anyone had a similar problem, and perhaps a fix? Since 3.10.17 works fine for me, my current plan is to wait for the next stable kernel ebuild to hit and hope that one is better thanks, Really? It works with one kernel, but not the other? Surprised me too. I does work, i.e. the system boots and I can use the text terminals, but gdm is a nogo Are you sure both kernels boot with init=/usr/lib/systemd/systemd? I think so. For one thing the output I included is from journalctl. This system is grub1 and here is grub.conf default 0 timeout 10 splashimage=(hd0,2)/boot/grub/splash.xpm.gz title Gentoo Linux (vmlinuz) root (hd0,2) kernel /boot/vmlinuz root=/dev/sda3 init=/usr/lib/systemd/systemd title Gentoo Linux, Previous Compilation (vmlinuz.old) root (hd0,2) kernel /boot/vmlinuz.old root=/dev/sda3 init=/usr/lib/systemd/systemd title Gentoo Linux, known working (vmlinuz.works) root (hd0,2) kernel /boot/vmlinuz.works root=/dev/sda3 init=/usr/lib/systemd/systemd single title Windows Vista rootnoverify (hd0,1) makeactive chainloader +1 All I change is the target of /boot/vmlinuz, System.map, and config Oh, I just got it too. It's neither gdm nor systemd; it's the nvidia binary module. Check lsmod, I bet you don't have it loaded, and dmesg will have nvidia: Unknown symbol acpi_os_wait_events_complete (err 0). No nvidia, no X, no X, no gdm (although the error message it gives does sound weird). I'm checking how to get the nvidia drivers in 3.13. Got it: https://devtalk.nvidia.com/default/topic/644906/331-20-on-3-13-rc1-kernel/ Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
