Jump to content
funtoo forums

mortenlj

Members
  • Content Count

    7
  • Joined

  • Last visited

  1. mortenlj

    Help me debug missing card reader

    It turns out that after enabling CONFIG_MISC_RTSX_PCI a new option under "MMC/SD/SDIO card support" was revealed that I hadn't noticed: CONFIG_MMC_REALTEK_PCI. Once I enabled this one, the card reader works. Thanks for the help!
  2. mortenlj

    Help me debug missing card reader

    Hi Some months ago, my SD card reader was working fine. Since then I have upgraded to newer kernels several times, and probably made other changes to the system as well. Now, my machine wont recognize that a card is inserted at all, and I'm struggling to find out which pieces of the puzzle to debug. My machine is a Lenovo Thinkpad P51 with an integrated card reader. I have a kernel built from gentoo-sources with my own configuration, but I haven't made any significant changes to this since the card reader worked as far as I can recall. After some googling I discovered that the config options related to this type of card was changed from kernel 4.15 to 4.16, but after updating my config to use the new symbols it still doesn't work. The relevant options used to be called CONFIG_MFD_RTSX and CONFIG_MFD_RTSX_PCI, but changed name to CONFIG_MISC_RTSX and CONFIG_MISC_RTSX_PCI. A related option called CONFIG_MFD_RTSX_USB also exists, but as far as I can tell is only relevant if the card reader is attached via USB (I have tried enabling it with no change in behavior). # lspci | grep -i card 3f:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) # zcat /proc/config.gz | grep RTSX CONFIG_MISC_RTSX=y CONFIG_MISC_RTSX_PCI=y # CONFIG_MISC_RTSX_USB is not set If I boot using just about any live CD, it works, so it's not a hardware failure. There is something in my system/kernel that has changed since the last time I used it, but I can't figure out what it is. Most of the reason for this problem is that I don't know which pieces are involved. Obviously the kernel needs to be configured to include drivers. This is now fixed but it's still not detected. Which other pieces are involved when I insert a card and dmesg prints out that it has detected a new device with X partitions? Does this involve udev or similar? Is there some other configuration that might be different? Are there other kernel options that could cause this, which are not directly related to the ones mentioned above? Any help or hints is appreciated.
  3. mortenlj

    Metro documentation

    I'm also looking for some more detailed Metro documentation. The problem with your theory that users should help out fixing bugs so that the main developers can free up time to write documentation is that only the main developers knows how to fix the bugs because there is no documentation... :) This is a typical problem that happens on many projects. If you don't take care to make it easy for new users/developers from the start, by the time it gets popular you don't have time to write the needed documentation, and you're stuck in a bugfixing loop. The only way to break out of the loop is to let bugs be bugs for a while, so that you can make it easier for new users/developers to start helping out, and hope that your users will forgive you for not fixing their bugs right away. It usually hurts a little, especially in your pride, but it's better in the long term. In particular, I'm wondering if it's possible to remove packages from a stage3 with Metro? Say I want to create a minimal edition with no "upgrade" option, could I as a final step remove gcc and all other "build essentials"? I'm tinkering with the idea of a minimal, "immutable" install, where you would just delete the instance and create a new one instead of upgrading the current one.
  4. I finally managed to figure out what was going on. It turns out that dbus had been installed without support for X, and my setup scripts didn't trigger a proper rebuild after changing the profiles to include the `desktop` flavor. After rebuilding dbus, things started working.
  5. I guess my description was a bit unclear. The problem in this thread is only on the SDDM login screen, it doesn't matter if I try logging in or not. Serves me right for cutting away so much of the screenshots that you can't actually see where it's at. :) I agree that there seems to be some sort of race condition, but a race with what? What decides if SDDM should present me with options to restart or shutdown? If I know what to wait for, I can look into setting up some dependency in the rc-scripts. (On the other matter, I can log in on the console and run startxfce4, and that works, but this is a company computer and I'm not allowed to boot into a logged in session)
  6. I'm installing a new machine, testing out ansible on a virtualbox before trying to apply the same setup to a real computer. The process has already spawned one thread (https://forums.funtoo.org/topic/1368-cant-get-a-session-when-using-sddm-and-xfce4-on-new-installation/), but I have another problem that I don't think is related to the problem in that thread. When sddm first starts, I get the user selector, and clock and other things, but no power controls. This means it's impossible to restart or shutdown from the sddm screen, which is somewhat annoying. Strangely enough, if I log in on the console, and run `eselect rc restart xdm`, sddm is restarted, and now suddenly I have power controls in the upper right corner. What gives?
  7. I have a new laptop, and I'm trying to get an ansible setup to configure it, testing out that setup on virtualbox. On my current laptop, I use xfce4 and sddm, so I figured I would use the same on the new one. I've had the old laptop for over four years, and I have no idea what I did when installing any of the things on it, so whenever something doesn't work on the new setup, it's a treasure hunt trying to figure out why it works on the old one. My latest problem has me stumped though, probably because I don't really understand how this stuff is supposed to work. If I log in on the console, and run startxfce4, it works. If I log in using sddm, I get kicked out immediately. From what I can gather, it seems to be related to the session, but I can't figure out what is wrong. I have compared /etc/sddm.conf and /etc/pam.d/* on the old and new, and can't find any relevant differences. I thought for a while the problem was related to consolekit being enabled or not, but I think that is now set up identically on both machines, and I'm also not entirely sure it's supposed to even be involved at all? This is the only trace of an error I can find in any logs, but it's not all that helpful # cat /home/mortenlj/.local/share/sddm/xorg-session.log (xfce4-session:3029): Gtk-ERROR **: failed to add UI: The resource at '/org/xfce/libxfce4ui/libxfce4ui-dialog-ui.ui' does not exist /etc/xdg/xfce4/xinitrc: line 114: 3029 Trace/breakpoint trap xfce4-session I have a couple questions: Should I use consolekit or not, it's not entirely clear? (lots of stuff on the internet says no, but it seems it's because they use systemd, which I don't) Is there a way to get some more useful error messages from sddm/xfce4-session?
×