Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
#
# MMC/SD/SDIO Host Controller Drivers
#
CONFIG_MMC_SDHCI=m
CONFIG_MMC_SDHCI_PCI=m
# CONFIG_MMC_RICOH_MMC is not set
CONFIG_MMC_SDHCI_ACPI=m
CONFIG_MMC_SDHCI_PLTFM=m
# CONFIG_MMC_WBSD is not set
# CONFIG_MMC_TIFM_SD is not set
# CONFIG_MMC_SDRICOH_CS is not set
# CONFIG_MMC_CB710 is not set
# CONFIG_MMC_VIA_SDMMC is not set
# CONFIG_MMC_VUB300 is not set
# CONFIG_MMC_USHC is not set
# CONFIG_MMC_USDHI6ROL0 is not set
# CONFIG_MMC_TOSHIBA_PCI is not set
# CONFIG_MMC_MTK is not set
# CONFIG_MEMSTICK is not set
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=m
# CONFIG_LEDS_CLASS_FLASH is not set
Is this a good sdcard? Does it work elsewhere? Is it a usb-1.x, usb-2.x or usb-3.x socket?
It looks to me like a hardware over-current reaction, where irq 19 is mapped to that usb. The usable current in usb 1-3 sockets varies, usb-1.x being 100mA, usb-3.x being 500mA, and usb-2.x in between.
If it is overcurrent, the sdcard is toast.
That's old. Does it know about usb 2, or 3? What usb modules load? Is the hardware old? To solve your problems, answers are needed, because your information is insufficient.
What is insufficient is your reading and comprehension (obviously a victim of public education)
Do you know anything about Linux ? about kernel 4.8.9 and its hatred towards sdcards ? (windows has no objection to sdcards)
Have you ever compiled a kernel ?
Do you know anything about Slackware ? Slackware 14.1 ?
What is insufficient is your reading and comprehension (obviously a victim of public education)
Do you know anything about Linux ? about kernel 4.8.9 and its hatred towards sdcards ? (windows has no objection to sdcards)
Have you ever compiled a kernel ?
Do you know anything about Slackware ? Slackware 14.1 ?
I'm not responding in kind to that. Just about every detail is wrong. Being an ex Mensa member and privately educated, my reading and comprehension are not limited. I've been using linux since the 1990s,I know plenty about linux, I've been running slackware nearly 10 years except for a dalliance with slamd-12.2. I had 2 boxes running 14.1 when it was current and make a practise of compiling my own kernels.
789, please use wording that conforms to a professional businesslike standard. Personal attacks are not allowed. I'd further ask that you please edit your post.
An idea to your issue may be this.
"
Using the kernel parameter "noirqdebug" appears to remedy the problem.
Note, this problem has been observed on debian as well. I believe that it concerns the kernel and/or the manufacturer's implementation of PCI PNP. "
kernel parameter "noirqdebug" appears to remedy the problem.
'noirqdebug' or 'irqpoll' did not work in my case, "fdisk -l" still does not see the SDCARD. The only change is that kernel parameter (if added at boot time, using "tab") stopped the "disabling irq 19" response to inserting an SDCARD ---the machine now does not slow down, it doesn't need to be rebooted.
At least we now know that my compiling the kernel is not the cause of the problem (of not recognizing SD cards
__________________
As for your guru friend: you should direct your response to him ---I merely asked a question if he knew anything about linux, because his reply gives the impression that he did not comprehend what I posted (if he read the question at all)
10,000 posts ?! no girlfriend, no wife ? now life ? no job ?
I watch the news as little as possible. Politicians on all sides screaming this and that. Once in a while I use different forums and the people are openly insulting each other. Guess it's part of the times maybe. Fortunately LQ has been trying to maintain a place that is open and welcoming to members. The general areas of LQ are much more lax. I ask you again to try to use this site for what is it. Free help from volunteers. Please use the technical forums for technical issues.
The people who are members here are mostly laid back for of people who volunteer their time to assist on questions. Some get to do it from work and some may be working from home and select the questions they try to help on. I's assume that many use this as one of their hobbies. I get to do this from work if everything is going OK.
There is nothing wrong with linux-4.8.9, there is no bug; the cause of the predicament was my compiling .
After several trys and fails, I managed to make a .config which not only compiles a kernel and modules that recognize SDcard, but as a side effect, compiles dell-laptop.c, dell-smbios.c, dell-smm-hwmon.c modules, too.
Now I can even change the kbd_backlight timeout.
Without any help from these gurus and cadets (so much for 10,000 posts)
I don't know what I did right this time, but I noticed (in conky) that the IRQ assignment seems to be different.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.