Mmc1 error 110 whilst initialising sd card

I have a problem trying to mount a SD card in Ubuntu 12.04. The message what I get from the system is: mmc0: error -110 whilst initialising SD card I'm on the 3.5.0-24-generic kernel. I check pr...

I have a problem trying to mount a SD card in Ubuntu 12.04. The message what I get from the system is:

mmc0: error -110 whilst initialising SD card

I’m on the 3.5.0-24-generic kernel.

I check previous kernel 3.5.0-15 and card is on the system. I think is some bug in kernel.

I was looking some solution on web. They say my card is dead (but is working)

What I should do?

Some more information on this issue here. If someone have more question about my hardware just ask.

Braiam's user avatar

Braiam

66.2k30 gold badges174 silver badges262 bronze badges

asked Feb 16, 2013 at 12:49

Grabasimo's user avatar

5

Basically this error arises only when the SDcard got damaged. But as you mentioned its working, Please try the following steps and share your feedback.

  • Please check the output of dmesg or lsusb to check whether it detects the SD card.
  • Open the «Disk Utility» application and check whether your SD card is listed. If its listed, just click it -> Unmount Volume -> Format the Volume with suitable filesystem.
  • Also, try mounting the SD card on Windows and check whether it is working or not.

Also, you can downgrade your kernel by installing the old kernel / latest stable kernel version with sudo apt-get update && sudo apt-get dist-upgrade && sudo apt-get autoremove.

wget the latest stable kernal from Kernel Website and install it with sudo dpkg -i *.deb && sudo update-grub2

Please select the proper kernel while booting and check whether your SD card mounts well!

Kalle Richter's user avatar

Kalle Richter

5,78619 gold badges67 silver badges100 bronze badges

answered Feb 24, 2014 at 11:29

Naga2Raja's user avatar

Naga2RajaNaga2Raja

2582 silver badges7 bronze badges

WhatTheDickens

Posts: 8
Joined: Sat Dec 29, 2012 4:13 pm

Error -110 whilst initializing SD card

I can’t boot up my new Pi :?

I successfully (I think!) set up my SDHC card using the instructions for «Copying an image to the SD card in Mac OS X (mostly graphical interface)» here:

http://elinux.org/RPi_Easy_SD_Card_Setup

I used the 2012-12-16-wheezy-raspbian.zip.torrent. Checksum checked out. All the files seem to be there when I look at the card on my Mac. But when I try to boot up, I get this line over and over

mmc0: error -110 whilst initialising SD card

Eventually, the screen just goes black.

I looked at this page for updating the firmware

http://elinux.org/R-Pi_Troubleshooting# … re_version

However, these instructions don’t appear to include an option for Mac OS. By the way, the green light seems to blink in a 4-pattern, indicating loader.bin not launched, but loader. bin isn’t included in the installation I did (i.e., writing the image didn’t put that file on my card), and various pages I’ve looked at indicate that this file is no longer necessary.


User avatar

Jim JKla

Posts: 2218
Joined: Sun Jan 29, 2012 11:15 pm
Location: Newcastle upon Tyne UK

Re: Error -110 whilst initializing SD card

Mon Jan 07, 2013 2:31 pm

Sorry you had to wait nine days for a reply.

But you did the right thing dropping the link into another post the other option is to reply to your own post so it bumps back to the top of the list the forum has such a high turnover. It is not good news yet because I’m a Windows Linux kind of guy but with a little bit of nudging I’m sure there will be Mac people here soon. ;)

Noob is not derogatory the noob is just the lower end of the noob—geek spectrum being a noob is just your first step towards being an uber-geek ;)

If you find a solution please post it in the wiki the forum dies too quick


WhatTheDickens

Posts: 8
Joined: Sat Dec 29, 2012 4:13 pm

Re: Error -110 whilst initializing SD card

Mon Jan 07, 2013 2:50 pm

Thanks for responding. I hope someone has some ideas. Meanwhile, I’ll take your advice and bump the original query back up every so often.

Jim JKla wrote:Sorry you had to wait nine days for a reply.

But you did the right thing dropping the link into another post the other option is to reply to your own post so it bumps back to the top of the list the forum has such a high turnover. It is not good news yet because I’m a Windows Linux kind of guy but with a little bit of nudging I’m sure there will be Mac people here soon. ;)


SirLagz

Posts: 1705
Joined: Mon Feb 20, 2012 8:53 am
Location: Perth, Australia

Re: Error -110 whilst initializing SD card

Mon Jan 07, 2013 3:35 pm

I had the same issue with my Micro SD card inside an Adapter.
Re-Imaged it again and it seemed to work ok after that.
Have you tried re-imaging the SD Card ?
Are you using a plain SD card or Micro SD Card inside an adapter ?

My Blog — http://www.sirlagz.net
Visit my blog for Tips, Tricks, Guides and More !
WiFi Issues ? Have a look at this post ! http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=44044


WhatTheDickens

Posts: 8
Joined: Sat Dec 29, 2012 4:13 pm

Re: Error -110 whilst initializing SD card

Mon Jan 07, 2013 3:53 pm

I’ve imaged it twice — same result both times. I’m using a Dane-Elec 4GB SDHC. I ordered it from Allied Electronics together with the Pi and an enclosure.

SirLagz wrote:I had the same issue with my Micro SD card inside an Adapter.
Re-Imaged it again and it seemed to work ok after that.
Have you tried re-imaging the SD Card ?
Are you using a plain SD card or Micro SD Card inside an adapter ?


M33P

Posts: 199
Joined: Sun Sep 02, 2012 1:14 pm

Re: Error -110 whilst initializing SD card

Mon Jan 07, 2013 7:45 pm

WhatTheDickens wrote:I can’t boot up my new Pi :?

I successfully (I think!) set up my SDHC card using the instructions for «Copying an image to the SD card in Mac OS X (mostly graphical interface)» here:

http://elinux.org/RPi_Easy_SD_Card_Setup

I used the 2012-12-16-wheezy-raspbian.zip.torrent. Checksum checked out. All the files seem to be there when I look at the card on my Mac. But when I try to boot up, I get this line over and over

mmc0: error -110 whilst initialising SD card

Eventually, the screen just goes black.

I looked at this page for updating the firmware

http://elinux.org/R-Pi_Troubleshooting# … re_version

However, these instructions don’t appear to include an option for Mac OS. By the way, the green light seems to blink in a 4-pattern, indicating loader.bin not launched, but loader. bin isn’t included in the installation I did (i.e., writing the image didn’t put that file on my card), and various pages I’ve looked at indicate that this file is no longer necessary.

Error -110 is a timeout. If the card works in your PC but not on your Pi, then the only thing that (really) changes when you move it between the two is the connector in which it sits.

The bootloader in the Pi is a very simple ROM that will read bootcode.bin from the SD card and then run it. bootcode then loads the GPU firmware blob and the linux kernel image. This 2-stage approach allows the GPU firmware and kernel to be arbitrary since they live on the SD card. My bet is that the first stage does this in a very basic SD card mode (that all SD cards must employ when they power up) but when the kernel copied from the SD card tries to use the SD card with its all-singing all-dancing driver it fails.

In short: pins. The leaf-sping pins inside the socket have been known to dislodge/be stuck/gunked up as a result of the soldering process. Are there any that look out of alignment vertically? They should also be springy in their plastic slots.


WhatTheDickens

Posts: 8
Joined: Sat Dec 29, 2012 4:13 pm

Re: Error -110 whilst initializing SD card

Mon Jan 07, 2013 8:43 pm

Thanks! The pins look good to me and feel springy, but here’s a photo. Am I missing anything?

PINS_photo.JPG
PINS_photo.JPG (22.29 KiB) Viewed 27018 times


M33P

Posts: 199
Joined: Sun Sep 02, 2012 1:14 pm

Re: Error -110 whilst initializing SD card

Tue Jan 08, 2013 3:32 pm

What happens when you power on the pi whilst putting pressure on the SD card over where the pins are?

I.e. pinch it gently with your thumb on the SD card and your index finger on the plastic ribbon connector on the topside?


User avatar

Jim JKla

Posts: 2218
Joined: Sun Jan 29, 2012 11:15 pm
Location: Newcastle upon Tyne UK

Re: Error -110 whilst initializing SD card

Tue Jan 08, 2013 4:44 pm

Or a plastic clothes peg/pin the type that uses a spring. ;)

Noob is not derogatory the noob is just the lower end of the noob—geek spectrum being a noob is just your first step towards being an uber-geek ;)

If you find a solution please post it in the wiki the forum dies too quick


User avatar

pluggy

Posts: 3635
Joined: Thu May 31, 2012 3:52 pm
Location: Barnoldswick, Lancashire,UK

Re: Error -110 whilst initializing SD card

Tue Jan 08, 2013 5:28 pm

First thing I’d try is a different SD card. The Pi can be tetchy about ’em and the fact that it works on another computer doesn’t mean a whole lot.

Don’t judge Linux by the Pi…….
I must not tread on too many sacred cows……


User avatar

Jim JKla

Posts: 2218
Joined: Sun Jan 29, 2012 11:15 pm
Location: Newcastle upon Tyne UK

Re: Error -110 whilst initializing SD card

Tue Jan 08, 2013 5:41 pm

I agree a new card is a good bet. I only mention the clothes peg as this was one of the first temp fixes by a user with a smashed SD card holder. ;)

Noob is not derogatory the noob is just the lower end of the noob—geek spectrum being a noob is just your first step towards being an uber-geek ;)

If you find a solution please post it in the wiki the forum dies too quick


Alimian

Posts: 1
Joined: Tue Jan 08, 2013 8:49 pm

Re: Error -110 whilst initializing SD card

Tue Jan 08, 2013 8:57 pm

I have precisely the same problem! I also purchased my Rpi from allied electronics along with their starter kit which had a case, sd card, power supply, hdmi cable etc… I used a MacBook Pro to set up the sd card just like the original poster, and used the same exact protocol to save the .img file to the ad card… This seemed to work fine, and the sd card had some files on it after the protocol…the startup recognizes my mouse and keyboard but then gives the 110 error exactly as above… Perhaps the problem is Allied electronics and faulty sd connectors? The contacts look fine and I tried squeezing the card as suggested, this made no difference…please help!! Very disappointing… Ali in Chicago


User avatar

pluggy

Posts: 3635
Joined: Thu May 31, 2012 3:52 pm
Location: Barnoldswick, Lancashire,UK

Re: Error -110 whilst initializing SD card

Tue Jan 08, 2013 11:25 pm

Same advice, try another SD card. I’d make it a plain class 4 and not too big……

Don’t judge Linux by the Pi…….
I must not tread on too many sacred cows……


WhatTheDickens

Posts: 8
Joined: Sat Dec 29, 2012 4:13 pm

Re: Error -110 whilst initializing SD card

Thu Jan 10, 2013 12:40 am

Okay: Bought a PNY 4GB Class 4, and … success!

It’s kind of irritating that the starter kit was sold with an incompatible card, but I’m so thrilled about finally getting launched that I’m not sweating it right now.

Thanks, everyone, for the help!


User avatar

Jim JKla

Posts: 2218
Joined: Sun Jan 29, 2012 11:15 pm
Location: Newcastle upon Tyne UK

Re: Error -110 whilst initializing SD card

Thu Jan 10, 2013 7:42 am

Would not do any harm to contact the kit supplier with some feedback. ;)

Noob is not derogatory the noob is just the lower end of the noob—geek spectrum being a noob is just your first step towards being an uber-geek ;)

If you find a solution please post it in the wiki the forum dies too quick


WhatTheDickens

Posts: 8
Joined: Sat Dec 29, 2012 4:13 pm

Re: Error -110 whilst initializing SD card

Thu Jan 10, 2013 1:29 pm

Yep. I’ve done that. Kinda feel like this information also belongs on the wiki page for SD cards at http://elinux.org/RPi_SD_cards, but as a noob I’m hesitant to create a wiki account. (Lots of experience with wikis, just next-to-none with Linux.) The Mfr. Part# for the Dane-Elec is DA-SD-4096-R if anyone with a wiki account cares to add it to the list as «nok». Based on Alimian’s post above, I don’t seem to be the only person who has had a bad experience with this particular card.


User avatar

Jim JKla

Posts: 2218
Joined: Sun Jan 29, 2012 11:15 pm
Location: Newcastle upon Tyne UK

Re: Error -110 whilst initializing SD card

Thu Jan 10, 2013 1:52 pm

There is no better place to learn than on this wiki you will have lots of ADVICE from the wiki admin but don’t worry try and be respectful humble self depricating and they will back off.

Eventually :D

Make sure you goto the help there’s a section about categories (they get a bit flaky about that but aslong as you have the Category RaspberryPi you should be ok.

Make sure you put something in your profile you click on your name once you have your login note the way the e-mail is structured

This is what i put in mine

Code: Select all

* Native Geordie (NE England) Newcastle upon Tyne resident.
* Currently a freelance I.T./Network support engineer.
* Builder of Linux boxes and webservers from re-cycled hardware.
* Uru Age (Virtual 3D worlds) Builder (J'Kla) using Blender. 
* Scoreboard Support provider for Newcastle Eagles Basketball UK BBL.
* Programme Publisher/Editor Newcastle Benfield F.C.
* Former contactor rollout engineer for P&G and others. 
* Former RAF Motor mechanic/fitter.
* IT user since the Sinclair Spectrum Launch.
* Still using XP and Ubuntu/Linux sucessfully resisting move to Vista/Win7 (spit).

Email: jimclark.jkla AT gmail DOT com

Putting stuff on the wiki is another step towards geekdom. ;)

This is a RapberryPi wiki and there are only about a dozen members over 1 year old ;)

Noob is not derogatory the noob is just the lower end of the noob—geek spectrum being a noob is just your first step towards being an uber-geek ;)

If you find a solution please post it in the wiki the forum dies too quick



gxwarr

Posts: 1
Joined: Fri Feb 22, 2013 1:50 pm

Re: Error -110 whilst initializing SD card

Fri Mar 01, 2013 6:04 pm

I also am having the same problem with the same sd card, same kit bought along with the PI, although i am using Windows 7 / Ubuntu, not Mac. Im happy to find this post, ill try a different sd card. I read before that it was a power problem. Ive tried so many different micro usb cables / plug combos. I used all different wires from different Android phones that ive had and also the one from my SGS3 that I read works. I couldnt understand why one of the plugs at least wouldnt work.
I was just about to buy some more micro usb wires to try but luckily i found this post. Ill give it a shot tonight!


HDenekamp

Posts: 5
Joined: Mon May 08, 2017 7:29 am

Re: Error -110 whilst initializing SD card

Tue May 09, 2017 7:54 am

I have exactly the same problem. The only problem perceived is that the bluetooth adapter and wireless interface is not found, it boots correctly otherwise. However, when I put the same SD card in another RaspberryPi, it doesn’t give the error and the bluetooth adapter and wireless interface do work. Anyone know what the problem might be?


jamesh

Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 32178
Joined: Sat Jul 30, 2011 7:41 pm

Re: Error -110 whilst initializing SD card

Tue May 09, 2017 8:45 am

An impressive thread necro — might be the oldest one so far!

That said, valid question and related!

Have you tried a different SD card?

Principal Software Engineer at Raspberry Pi Ltd.
Working in the Applications Team.


jfraga88

Posts: 1
Joined: Wed Mar 07, 2018 4:15 am

Re: Error -110 whilst initializing SD card

Wed Mar 07, 2018 4:18 am

Hey all,

I have the same issue. I just bought a new Samsung 32GB 95MB/s (U1) MicroSD EVO because it was apparently the best performer and I still get that message. Everything else is working properly. But I won’t mess around with buy new cards for now. I am just curious about the error.

Joaquin


Return to “Troubleshooting”

Содержание

  1. Arch Linux
  2. #1 2012-06-17 09:14:06
  3. error -110 whilst initialising SD card
  4. #2 2012-06-25 10:51:53
  5. Re: error -110 whilst initialising SD card
  6. #3 2012-06-30 22:10:38
  7. Re: error -110 whilst initialising SD card
  8. #4 2012-07-03 21:58:23
  9. Re: error -110 whilst initialising SD card
  10. #5 2015-02-14 19:30:33
  11. Re: error -110 whilst initialising SD card
  12. #6 2015-02-14 19:43:51
  13. Re: error -110 whilst initialising SD card
  14. Mmc1 error 110 whilst initialising sd card
  15. Re: mmc1: error -110 whilst initialising SDIO card
  16. Re: mmc1: error -110 whilst initialising SDIO card
  17. Re: mmc1: error -110 whilst initialising SDIO card
  18. Re: mmc1: error -110 whilst initialising SDIO card
  19. mmc0: ошибка -110 при инициализации SD-карты [закрыто]
  20. Mmc1 error 110 whilst initialising sd card
  21. Re: Error -110 whilst initializing SD Card
  22. Mmc1 error 110 whilst initialising sd card
  23. Re: Error -110 whilst initializing SD card
  24. Re: Error -110 whilst initializing SD card
  25. Re: Error -110 whilst initializing SD card
  26. Re: Error -110 whilst initializing SD card
  27. Re: Error -110 whilst initializing SD card

Arch Linux

You are not logged in.

#1 2012-06-17 09:14:06

error -110 whilst initialising SD card

When I enter my 8GB Class 6 Samsung MicroSD card into the cardreader (mmc), 4 times out of 5 it does not mount. dmesg gives this:

I am not sure, but it appears to be timeout issue (the system does not wait long enough?).

The behaviour of the card in the mobile phone:
The same card mounts perfectly fine each and every time on Android 2.4 and/or ClockWordMod bootloader, but on Android 4 and/or 4ext bootloader it exhibits the same issues as on Arch.

Last edited by Lockheed (2012-06-17 09:16:08)

Laptop: ThinkPad T420s, i7/i5, 16GB RAM, 1080p IPS mod, Arch | HTPC/Server/fw: Zotac AQ01, A4-5000 Kabini, 8GB, Arch/lxd NethServer

#2 2012-06-25 10:51:53

Re: error -110 whilst initialising SD card

Same problem here on a XPS M1330. Since the last two kernel updates my Samsung 16GB class6 SD card won’t get mounted. Dmesg gives me the same error message.

I think this is a kernel driver problem, as others have this error too:
https://bbs.archlinux.org/viewtopic.php … 8#p1118218

sorry for my bad english

#3 2012-06-30 22:10:38

Re: error -110 whilst initialising SD card

Try removing and reinserting the card several times. Mine usually mounts once in ever 7 times.

Laptop: ThinkPad T420s, i7/i5, 16GB RAM, 1080p IPS mod, Arch | HTPC/Server/fw: Zotac AQ01, A4-5000 Kabini, 8GB, Arch/lxd NethServer

#4 2012-07-03 21:58:23

Re: error -110 whilst initialising SD card

This is not really a fix for the problem. No one else having this error?

sorry for my bad english

#5 2015-02-14 19:30:33

Re: error -110 whilst initialising SD card

Did you find a solution back than? I have the same problem for the first time today!

#6 2015-02-14 19:43:51

Re: error -110 whilst initialising SD card

The problem is that some cards are just too slow to initialise, and kernel gives up on waiting for them.
For mobile phone, there is no solution other than using older kernel (in some GingerBread ROM) or changing the SD card.
For computer, just change the card. I don’t think it’s worth the trouble trying to solve it in other ways.

Last edited by Lockheed (2015-02-14 19:46:08)

Laptop: ThinkPad T420s, i7/i5, 16GB RAM, 1080p IPS mod, Arch | HTPC/Server/fw: Zotac AQ01, A4-5000 Kabini, 8GB, Arch/lxd NethServer

Источник

Mmc1 error 110 whilst initialising sd card

I have a raspberry pi 3 with Jessie lite (10-APR-2017) that worked perfectly until yesterday. Now WIFI & Bluetooth don’t work anymore — LAN is OK.
dmesg shows mmc1: error -110 whilst initialising SDIO card
I re-imaged the SD-card with the newest Jessie Lite (05-JUL-2017)
dmesg shows mmc1: error -110 whilst initialising SDIO card
hcitool scan shows Device is not available: No such device

Don’t know what the problem is.

Re: mmc1: error -110 whilst initialising SDIO card

Re: mmc1: error -110 whilst initialising SDIO card

What have you added to /boot/config.txt?

Strip it back to a file that looks EXACTLY like this

yes, just one lone octothorpe character.

Then add the lines from your current /boot/config.txt one at a time, until you find the line that causes your error.

Languages using left-hand whitespace for syntax are ridiculous

DMs sent on https://twitter.com/DougieLawson or LinkedIn will be answered next month.
Fake doctors — are all on my foes list.

The use of crystal balls and mind reading is prohibited.

Re: mmc1: error -110 whilst initialising SDIO card

Re: mmc1: error -110 whilst initialising SDIO card

What additional hardware is connected to your RPi?

Have you tried Raspbian Jessie Lite 2017-07-05?

Languages using left-hand whitespace for syntax are ridiculous

DMs sent on https://twitter.com/DougieLawson or LinkedIn will be answered next month.
Fake doctors — are all on my foes list.

The use of crystal balls and mind reading is prohibited.

Источник

mmc0: ошибка -110 при инициализации SD-карты [закрыто]

Хотите улучшить этот вопрос? Обновите вопрос, чтобы он соответствовал теме Ask Ubuntu.

Закрыто 5 лет назад .

У меня проблема при попытке смонтировать SD-карту в Ubuntu 12.04. Сообщение, которое я получаю из системы:

Я в 3.5.0-24-generic ядре.

Я проверяю предыдущее ядро ​​3.5.0-15 и карта находится в системе. Я думаю, что это ошибка в ядре.

Я искал какое-то решение в сети. Они говорят, что моя карта мертва (но работает)

Что я должен делать?

Еще немного информации по этому вопросу здесь . Если у кого-то есть еще вопросы по поводу моего оборудования, просто спросите.

В основном эта ошибка возникает только тогда, когда SD-карта была повреждена. Но, как вы упомянули о его работе, пожалуйста, попробуйте следующие шаги и поделитесь своим мнением.

  • Пожалуйста, проверьте вывод dmesg или lsusb проверьте, обнаруживает ли он SD-карту.
  • Откройте приложение «Дисковая утилита» и проверьте, есть ли ваша SD-карта в списке. Если он указан, просто щелкните по нему -> Размонтировать том -> Отформатируйте том с помощью подходящей файловой системы.
  • Также попробуйте смонтировать SD-карту в Windows и проверьте, работает она или нет.

Также вы можете понизить ядро, установив старое ядро ​​/ последнюю стабильную версию ядра с помощью sudo apt-get update && sudo apt-get dist-upgrade && sudo apt-get autoremove .

wget последнюю стабильную версию Kernel с веб-сайта Kernel и установите ее с sudo dpkg -i *.deb && sudo update-grub2

Пожалуйста, выберите правильное ядро ​​во время загрузки и проверьте, хорошо ли монтируется ваша SD-карта!

Источник

Mmc1 error 110 whilst initialising sd card

Hi guys,
Yesterday my RPi 4b 4GB Arrived. I bought new SanDisk 16GB SD Card. I installed NOOBS on it, and from it installed full Raspbian. And today, when I came back from university I noticed that I cannot connect to internet. I did a reboot and Raspberry Pi didn’t boot. It showed a communicate:
[ 1.036379] mmc0: error -110 whilst initializing SD card

So, I formatted SD Card on my laptop (it’s working under Arch) and copied NOOBS files again. Once again the same communicate.

Next thing I did was to destroy partitions on SD Card using command dd if=/dev/zero of=/dev/sdb and then using the same I installed on it raspian (from .img file) — dd if=/raspian.img of=/dev/sdb.

Unfortunately Raspberry Pi 4b still doesn’t boot. There are 4 green blinks, a break and again 4 green blinks, break and again, again and again.

Power supply parameters: output DC 5V, 3.1A.

What’s wrong with my RPi? Maybe. Is something wrong with my SD Card?

Re: Error -110 whilst initializing SD Card

Read the boot problem sticky in beginners.

Why do you feel the need to «delete partitions» after formatting, if you use the official formatter from the SD-card association, the result is just one FAT32 partition. It really resets the card to factory settings.

Better yet, forget about NOOBS, and use Etcher, to image the card with Raspbian.img

No formatting or unzipping needed, and no strange partition deleting, which only creates more havoc.

Источник

Mmc1 error 110 whilst initialising sd card

I can’t boot up my new Pi

I successfully (I think!) set up my SDHC card using the instructions for «Copying an image to the SD card in Mac OS X (mostly graphical interface)» here:

I used the 2012-12-16-wheezy-raspbian.zip.torrent. Checksum checked out. All the files seem to be there when I look at the card on my Mac. But when I try to boot up, I get this line over and over

mmc0: error -110 whilst initialising SD card

Eventually, the screen just goes black.

I looked at this page for updating the firmware

However, these instructions don’t appear to include an option for Mac OS. By the way, the green light seems to blink in a 4-pattern, indicating loader.bin not launched, but loader. bin isn’t included in the installation I did (i.e., writing the image didn’t put that file on my card), and various pages I’ve looked at indicate that this file is no longer necessary.

Re: Error -110 whilst initializing SD card

Sorry you had to wait nine days for a reply.

But you did the right thing dropping the link into another post the other option is to reply to your own post so it bumps back to the top of the list the forum has such a high turnover. It is not good news yet because I’m a Windows Linux kind of guy but with a little bit of nudging I’m sure there will be Mac people here soon.

Noob is not derogatory the noob is just the lower end of the noob—geek spectrum being a noob is just your first step towards being an uber-geek

If you find a solution please post it in the wiki the forum dies too quick

Re: Error -110 whilst initializing SD card

Jim JKla wrote: Sorry you had to wait nine days for a reply.

But you did the right thing dropping the link into another post the other option is to reply to your own post so it bumps back to the top of the list the forum has such a high turnover. It is not good news yet because I’m a Windows Linux kind of guy but with a little bit of nudging I’m sure there will be Mac people here soon.

Re: Error -110 whilst initializing SD card

Re: Error -110 whilst initializing SD card

Re: Error -110 whilst initializing SD card

WhatTheDickens wrote: I can’t boot up my new Pi

I successfully (I think!) set up my SDHC card using the instructions for «Copying an image to the SD card in Mac OS X (mostly graphical interface)» here:

I used the 2012-12-16-wheezy-raspbian.zip.torrent. Checksum checked out. All the files seem to be there when I look at the card on my Mac. But when I try to boot up, I get this line over and over

mmc0: error -110 whilst initialising SD card

Eventually, the screen just goes black.

I looked at this page for updating the firmware

However, these instructions don’t appear to include an option for Mac OS. By the way, the green light seems to blink in a 4-pattern, indicating loader.bin not launched, but loader. bin isn’t included in the installation I did (i.e., writing the image didn’t put that file on my card), and various pages I’ve looked at indicate that this file is no longer necessary.

Error -110 is a timeout. If the card works in your PC but not on your Pi, then the only thing that (really) changes when you move it between the two is the connector in which it sits.

The bootloader in the Pi is a very simple ROM that will read bootcode.bin from the SD card and then run it. bootcode then loads the GPU firmware blob and the linux kernel image. This 2-stage approach allows the GPU firmware and kernel to be arbitrary since they live on the SD card. My bet is that the first stage does this in a very basic SD card mode (that all SD cards must employ when they power up) but when the kernel copied from the SD card tries to use the SD card with its all-singing all-dancing driver it fails.

In short: pins. The leaf-sping pins inside the socket have been known to dislodge/be stuck/gunked up as a result of the soldering process. Are there any that look out of alignment vertically? They should also be springy in their plastic slots.

Источник

@iamhssingh

WiFi on my Raspberry Pi has disappeared. This is not the first time. It occured a while ago but when I inserted an external WiFi Dongle (and did a lot of other stuff from Google), it showed up. This time, it’s not working.

Bluetooth & WiFi were working on my Raspberry Pi 3 Model B Rev 1.2 when I bought it in 2016. I did not use it for a while and in 2018, I tried OSMC and there was no WiFi. So I installed Raspbian & still no WiFi. So I Googled and tried a lot of things. Thinking it’s a hardware issue, I bought an external WiFi Dongle and as soon as I inserted it, internal WiFi showed up.

All this while, Bluetooth was working fine.
Almost 6 months later, I format the SD Card and installed latest Raspbian, and again, there is no wlan0. Tried external WiFi, it shows up, but the internal WiFi has disappeared.

I thought it’s some driver issue so I installed:

  • 2016-05-10-raspbian-jessie (What I had used in 2016 maybe). No WiFi.
  • 2017-01-11-raspbian-jessie -> Again, No WiFi.

I have tried dtoverlay=sdtweak and dtoverlay=pi3-enable-wifi but with no success.

System
A constant error message that I got in all raspbian installation is:
mmc1: error -110 whilst initialising SDIO card

Initially, this error was with SD Card (and not SDIO) and there were some brcmfmac errors, but in older raspbian, this is all I get. I newer, sometimes there are some extra brcmfmac errors.

  • Model: Raspberry Pi 3 Model B Rev 1.2
  • Raspbian 2016-05-10 / 2017-01-11 / 2018-11-13

dmesg
mmc1: error -110 whilst initialising SDIO card

Additional context
Bluetooth & Ethernet are showing up. I have not tried to connect them. I have tried to format and boot up with no external hardware (except for HDMI) and still no success. I am using Logitech Wireless K400+ Keyboard / Mouse and it works. External USB WiFi dongle also works. I have yet not tried to change SD card as I have been using this for a while and I don’t have extra, but I will try that also & update here.

@iamhssingh

I tried with 32 GB (Sandisk Ultra some better class SD) and now I am getting some other errors as well.

Oh, Ethernet is working perfectly! I am posting this via my RPi with eth0.

Here are some raw output:

dmesg

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.79-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1159 SMP Sun Nov 4 17:50:20 GMT 2018
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Rev 1.2
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 8 MiB at 0x3ac00000
[    0.000000] On node 0 totalpages: 242688
[    0.000000] free_area_init_node: node 0, pgdat 80c85280, node_mem_map ba39f000
[    0.000000]   Normal zone: 2133 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 242688 pages, LIFO batch:31
[    0.000000] percpu: Embedded 17 pages/cpu @ba348000 s38720 r8192 d22720 u69632
[    0.000000] pcpu-alloc: s38720 r8192 d22720 u69632 alloc=17*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 240555
[    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTUUID=e21979c8-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 940232K/970752K available (7168K kernel code, 576K rwdata, 2076K rodata, 1024K init, 698K bss, 22328K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xbb800000 - 0xff800000   (1088 MB)
                   lowmem  : 0x80000000 - 0xbb400000   ( 948 MB)
                   modules : 0x7f000000 - 0x80000000   (  16 MB)
                     .text : 0x80008000 - 0x80800000   (8160 kB)
                     .init : 0x80b00000 - 0x80c00000   (1024 kB)
                     .data : 0x80c00000 - 0x80c9017c   ( 577 kB)
                      .bss : 0x80c97f04 - 0x80d468b0   ( 699 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 25287 entries in 75 pages
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[    0.000019] Switching to timer-based delay loop, resolution 52ns
[    0.000266] Console: colour dummy device 80x30
[    0.000283] console [tty1] enabled
[    0.000308] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[    0.000323] pid_max: default: 32768 minimum: 301
[    0.000643] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000657] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001594] Disabling memory control group subsystem
[    0.001671] CPU: Testing write buffer coherency: ok
[    0.002084] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.002485] Setting up static identity map for 0x100000 - 0x10003c
[    0.002605] Hierarchical SRCU implementation.
[    0.003274] smp: Bringing up secondary CPUs ...
[    0.004049] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.004890] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.005712] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.005816] smp: Brought up 1 node, 4 CPUs
[    0.005827] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[    0.005832] CPU: All CPU(s) started in HYP mode.
[    0.005836] CPU: Virtualization extensions available.
[    0.006762] devtmpfs: initialized
[    0.017000] random: get_random_u32 called from bucket_table_alloc+0xfc/0x24c with crng_init=0
[    0.017764] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[    0.017984] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.018001] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.018556] pinctrl core: initialized pinctrl subsystem
[    0.019303] NET: Registered protocol family 16
[    0.022046] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.026932] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.026939] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.027153] Serial: AMBA PL011 UART driver
[    0.028812] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.029273] uart-pl011 3f201000.serial: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe
[    0.061041] bcm2835-dma 3f007000.dma: DMA legacy API manager at bb813000, dmachans=0x1
[    0.062460] SCSI subsystem initialized
[    0.062681] usbcore: registered new interface driver usbfs
[    0.062732] usbcore: registered new interface driver hub
[    0.062822] usbcore: registered new device driver usb
[    0.070087] raspberrypi-firmware soc:firmware: Attached to firmware from 2018-11-04 16:31
[    0.071489] clocksource: Switched to clocksource arch_sys_counter
[    0.148408] VFS: Disk quotas dquot_6.6.0
[    0.148496] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.148681] FS-Cache: Loaded
[    0.148881] CacheFiles: Loaded
[    0.157760] NET: Registered protocol family 2
[    0.158481] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.158590] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.158776] TCP: Hash tables configured (established 8192 bind 8192)
[    0.158903] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.158947] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.159177] NET: Registered protocol family 1
[    0.159636] RPC: Registered named UNIX socket transport module.
[    0.159642] RPC: Registered udp transport module.
[    0.159647] RPC: Registered tcp transport module.
[    0.159652] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.161242] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[    0.164001] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[    0.171995] FS-Cache: Netfs 'nfs' registered for caching
[    0.172587] NFS: Registering the id_resolver key type
[    0.172613] Key type id_resolver registered
[    0.172619] Key type id_legacy registered
[    0.172633] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.174517] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    0.174641] io scheduler noop registered
[    0.174648] io scheduler deadline registered (default)
[    0.174818] io scheduler cfq registered
[    0.174825] io scheduler mq-deadline registered
[    0.174831] io scheduler kyber registered
[    0.177524] BCM2708FB: allocated DMA memory fad10000
[    0.177550] BCM2708FB: allocated DMA channel 0 @ bb813000
[    0.227485] Console: switching to colour frame buffer device 228x61
[    0.257833] bcm2835-rng 3f104000.rng: hwrng registered
[    0.257966] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
[    0.258458] vc-sm: Videocore shared memory driver
[    0.258731] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    0.268357] brd: module loaded
[    0.277292] loop: module loaded
[    0.277306] Loading iSCSI transport class v2.0-870.
[    0.277995] libphy: Fixed MDIO Bus: probed
[    0.278098] usbcore: registered new interface driver lan78xx
[    0.278152] usbcore: registered new interface driver smsc95xx
[    0.278167] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    0.306072] dwc_otg 3f980000.usb: base=0xf0980000
[    0.506281] Core Release: 2.80a
[    0.506293] Setting default values for core params
[    0.506326] Finished setting default values for core params
[    0.706589] Using Buffer DMA mode
[    0.706595] Periodic Transfer Interrupt Enhancement - disabled
[    0.706601] Multiprocessor Interrupt Enhancement - disabled
[    0.706607] OTG VER PARAM: 0, OTG VER FLAG: 0
[    0.706620] Dedicated Tx FIFOs mode
[    0.707033] WARN::dwc_otg_hcd_init:1046: FIQ DMA bounce buffers: virt = 0xbad04000 dma = 0xfad04000 len=9024
[    0.707061] FIQ FSM acceleration enabled for :
               Non-periodic Split Transactions
               Periodic Split Transactions
               High-Speed Isochronous Endpoints
               Interrupt/Control Split Transaction hack enabled
[    0.707068] dwc_otg: Microframe scheduler enabled
[    0.707116] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x805ea470
[    0.707127] WARN::hcd_init_fiq:460: FIQ ASM at 0x805ea7d8 length 36
[    0.707139] WARN::hcd_init_fiq:486: MPHI regs_base at 0xf0006000
[    0.707190] dwc_otg 3f980000.usb: DWC OTG Controller
[    0.707222] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    0.707254] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[    0.707304] Init: Port Power? op_state=1
[    0.707309] Init: Power Port (0)
[    0.707515] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.707526] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.707535] usb usb1: Product: DWC OTG Controller
[    0.707543] usb usb1: Manufacturer: Linux 4.14.79-v7+ dwc_otg_hcd
[    0.707551] usb usb1: SerialNumber: 3f980000.usb
[    0.708167] hub 1-0:1.0: USB hub found
[    0.708206] hub 1-0:1.0: 1 port detected
[    0.708701] dwc_otg: FIQ enabled
[    0.708706] dwc_otg: NAK holdoff enabled
[    0.708711] dwc_otg: FIQ split-transaction FSM enabled
[    0.708721] Module dwc_common_port init
[    0.708940] usbcore: registered new interface driver usb-storage
[    0.709101] mousedev: PS/2 mouse device common for all mice
[    0.709167] IR NEC protocol handler initialized
[    0.709173] IR RC5(x/sz) protocol handler initialized
[    0.709177] IR RC6 protocol handler initialized
[    0.709183] IR JVC protocol handler initialized
[    0.709187] IR Sony protocol handler initialized
[    0.709192] IR SANYO protocol handler initialized
[    0.709197] IR Sharp protocol handler initialized
[    0.709202] IR MCE Keyboard/mouse protocol handler initialized
[    0.709207] IR XMP protocol handler initialized
[    0.709870] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[    0.710125] bcm2835-cpufreq: min=600000 max=1200000
[    0.710474] sdhci: Secure Digital Host Controller Interface driver
[    0.710479] sdhci: Copyright(c) Pierre Ossman
[    0.710842] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe
[    0.711173] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
[    0.711269] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.712721] ledtrig-cpu: registered to indicate activity on CPUs
[    0.712900] hidraw: raw HID events driver (C) Jiri Kosina
[    0.713048] usbcore: registered new interface driver usbhid
[    0.713053] usbhid: USB HID core driver
[    0.713826] vchiq: vchiq_init_state: slot_zero = bad80000, is_master = 0
[    0.715357] [vc_sm_connected_init]: start
[    0.725190] [vc_sm_connected_init]: end - returning 0
[    0.725787] Initializing XFRM netlink socket
[    0.725809] NET: Registered protocol family 17
[    0.725904] Key type dns_resolver registered
[    0.726433] Registering SWP/SWPB emulation handler
[    0.726975] registered taskstats version 1
[    0.732943] uart-pl011 3f201000.serial: cts_event_workaround enabled
[    0.733019] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[    0.734805] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[    0.734813] mmc-bcm2835 3f300000.mmc: DMA channel allocated
[    0.792087] sdhost: log_buf @ bad07000 (fad07000)
[    0.818903] mmc-bcm2835 3f300000.mmc: card claims to support voltages below defined range
[    0.818912] mmc-bcm2835 3f300000.mmc: exceeding card's volts
[    0.871537] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    0.872610] of_cfs_init
[    0.872763] of_cfs_init: OK
[    0.873356] Waiting for root device PARTUUID=e21979c8-02...
[    0.921629] Indeed it is in host mode hprt0 = 00021501
[    1.008033] random: fast init done
[    1.053476] mmc0: host does not support reading read-only switch, assuming write-enable
[    1.056727] mmc0: new high speed SDHC card at address aaaa
[    1.057219] mmcblk0: mmc0:aaaa SL32G 29.7 GiB
[    1.058719]  mmcblk0: p1 p2
[    1.097047] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    1.097103] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    1.105958] devtmpfs: mounted
[    1.109267] Freeing unused kernel memory: 1024K
[    1.131875] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    1.132034] Indeed it is in host mode hprt0 = 00001101
[    1.371900] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[    1.371919] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.372593] hub 1-1:1.0: USB hub found
[    1.372697] hub 1-1:1.0: 5 ports detected
[    1.540580] systemd[1]: System time before build time, advancing clock.
[    1.662055] NET: Registered protocol family 10
[    1.663129] Segment Routing with IPv6
[    1.683793] ip_tables: (C) 2000-2006 Netfilter Core Team
[    1.702106] random: systemd: uninitialized urandom read (16 bytes read)
[    1.708114] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[    1.708669] systemd[1]: Detected architecture arm.
[    1.709531] systemd[1]: Set hostname to <raspberrypi>.
[    1.711594] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    1.752030] random: systemd: uninitialized urandom read (16 bytes read)
[    1.785709] random: systemd-sysv-ge: uninitialized urandom read (16 bytes read)
[    1.841916] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    1.841931] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.844633] smsc95xx v1.0.6
[    1.935226] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:4a:5b:01
[    2.031561] usb 1-1.2: new low-speed USB device number 4 using dwc_otg
[    2.071618] Under-voltage detected! (0x00050005)
[    2.166855] usb 1-1.2: New USB device found, idVendor=413c, idProduct=301a
[    2.166870] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.166880] usb 1-1.2: Product: Dell MS116 USB Optical Mouse
[    2.166889] usb 1-1.2: Manufacturer: PixArt
[    2.171238] input: PixArt Dell MS116 USB Optical Mouse as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.0/0003:413C:301A.0001/input/input0
[    2.171703] hid-generic 0003:413C:301A.0001: input,hidraw0: USB HID v1.11 Mouse [PixArt Dell MS116 USB Optical Mouse] on usb-3f980000.usb-1.2/input0
[    2.204121] systemd[1]: Created slice User and Session Slice.
[    2.204792] systemd[1]: Listening on Journal Socket.
[    2.205161] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    2.205779] systemd[1]: Created slice System Slice.
[    2.205937] systemd[1]: Reached target Slices.
[    2.206605] systemd[1]: Created slice system-getty.slice.
[    2.206846] systemd[1]: Listening on udev Kernel Socket.
[    2.271643] usb 1-1.4: new low-speed USB device number 5 using dwc_otg
[    2.319819] i2c /dev entries driver
[    2.421827] usb 1-1.4: New USB device found, idVendor=413c, idProduct=2003
[    2.421849] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.421861] usb 1-1.4: Product: Dell USB Keyboard
[    2.421869] usb 1-1.4: Manufacturer: Dell
[    2.444158] input: Dell Dell USB Keyboard as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4:1.0/0003:413C:2003.0002/input/input1
[    2.512290] hid-generic 0003:413C:2003.0002: input,hidraw1: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-3f980000.usb-1.4/input0
[    2.851780] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    2.999914] systemd-journald[88]: Received request to flush runtime journal from PID 1
[    3.197839] mmc1: error -84 whilst initialising SDIO card
[    3.207199] mmc-bcm2835 3f300000.mmc: card claims to support voltages below defined range
[    3.207210] mmc-bcm2835 3f300000.mmc: exceeding card's volts
[    3.262991] mmc1: error -84 whilst initialising MMC card
[    3.332820] mmc-bcm2835 3f300000.mmc: card claims to support voltages below defined range
[    3.332838] mmc-bcm2835 3f300000.mmc: exceeding card's volts
[    3.808211] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[    3.810893] bcm2835_alsa bcm2835_alsa: card created with 8 channels
[    4.406739] mmc1: error -84 whilst initialising SDIO card
[    5.094581] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[    5.094923] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    5.242606] uart-pl011 3f201000.serial: no DMA platform data
[    6.427513] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k SSFS
[    6.625474] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    6.628300] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[    7.888452] random: crng init done
[    7.888463] random: 7 urandom warning(s) missed due to ratelimiting
[    8.311577] Voltage normalised (0x00000000)
[    9.757005] Bluetooth: Core ver 2.22
[    9.757062] NET: Registered protocol family 31
[    9.757066] Bluetooth: HCI device and connection manager initialized
[    9.757084] Bluetooth: HCI socket layer initialized
[    9.757093] Bluetooth: L2CAP socket layer initialized
[    9.757115] Bluetooth: SCO socket layer initialized
[    9.767113] Bluetooth: HCI UART driver ver 2.3
[    9.767125] Bluetooth: HCI UART protocol H4 registered
[    9.767128] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    9.767305] Bluetooth: HCI UART protocol Broadcom registered
[   10.089375] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   10.089383] Bluetooth: BNEP filters: protocol multicast
[   10.089400] Bluetooth: BNEP socket layer initialized
[   10.137169] Bluetooth: RFCOMM TTY layer initialized
[   10.137208] Bluetooth: RFCOMM socket layer initialized
[   10.137234] Bluetooth: RFCOMM ver 1.11
[   13.731395] fuse init (API version 7.26)

lsusb

Bus 001 Device 005: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 001 Device 004: ID 413c:301a Dell Computer Corp. 
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

@iamhssingh

I ran sudo rpi-update and after that, following happened:

  • No WiFi
  • Bluetooth is there
  • First 3 boot showed no error
  • Post that, error -110 disappeared

Here’s the dmesg output:

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.94-v7+ (dom@dom-XPS-13-9370) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1193 SMP Tue Jan 22 15:34:30 GMT 2019
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Rev 1.2
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 8 MiB at 0x3ac00000
[    0.000000] On node 0 totalpages: 242688
[    0.000000] free_area_init_node: node 0, pgdat 80c85780, node_mem_map ba39f000
[    0.000000]   Normal zone: 2133 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 242688 pages, LIFO batch:31
[    0.000000] percpu: Embedded 17 pages/cpu @ba348000 s38720 r8192 d22720 u69632
[    0.000000] pcpu-alloc: s38720 r8192 d22720 u69632 alloc=17*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 240555
[    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTUUID=e21979c8-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 940232K/970752K available (7168K kernel code, 577K rwdata, 2080K rodata, 1024K init, 698K bss, 22328K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xbb800000 - 0xff800000   (1088 MB)
                   lowmem  : 0x80000000 - 0xbb400000   ( 948 MB)
                   modules : 0x7f000000 - 0x80000000   (  16 MB)
                     .text : 0x80008000 - 0x80800000   (8160 kB)
                     .init : 0x80b00000 - 0x80c00000   (1024 kB)
                     .data : 0x80c00000 - 0x80c906b4   ( 578 kB)
                      .bss : 0x80c97ef8 - 0x80d468f0   ( 699 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 25296 entries in 75 pages
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[    0.000018] Switching to timer-based delay loop, resolution 52ns
[    0.000266] Console: colour dummy device 80x30
[    0.000285] console [tty1] enabled
[    0.000309] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[    0.000324] pid_max: default: 32768 minimum: 301
[    0.000645] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000659] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001596] Disabling memory control group subsystem
[    0.001673] CPU: Testing write buffer coherency: ok
[    0.002087] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.002491] Setting up static identity map for 0x100000 - 0x10003c
[    0.002614] Hierarchical SRCU implementation.
[    0.003295] smp: Bringing up secondary CPUs ...
[    0.004078] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.004926] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.005750] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.005855] smp: Brought up 1 node, 4 CPUs
[    0.005866] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[    0.005871] CPU: All CPU(s) started in HYP mode.
[    0.005875] CPU: Virtualization extensions available.
[    0.006797] devtmpfs: initialized
[    0.016927] random: get_random_u32 called from bucket_table_alloc+0xfc/0x24c with crng_init=0
[    0.017695] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[    0.017914] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.017932] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.018490] pinctrl core: initialized pinctrl subsystem
[    0.019232] NET: Registered protocol family 16
[    0.021978] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.026788] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.026795] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.027003] Serial: AMBA PL011 UART driver
[    0.028662] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.029124] uart-pl011 3f201000.serial: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe
[    0.060591] bcm2835-dma 3f007000.dma: DMA legacy API manager at bb813000, dmachans=0x1
[    0.062022] SCSI subsystem initialized
[    0.062241] usbcore: registered new interface driver usbfs
[    0.062292] usbcore: registered new interface driver hub
[    0.062382] usbcore: registered new device driver usb
[    0.070087] raspberrypi-firmware soc:firmware: Attached to firmware from 2019-01-22 16:50
[    0.071491] clocksource: Switched to clocksource arch_sys_counter
[    0.148486] VFS: Disk quotas dquot_6.6.0
[    0.148567] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.148754] FS-Cache: Loaded
[    0.148936] CacheFiles: Loaded
[    0.156815] NET: Registered protocol family 2
[    0.157536] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.157645] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.157830] TCP: Hash tables configured (established 8192 bind 8192)
[    0.157959] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.158003] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.158231] NET: Registered protocol family 1
[    0.158702] RPC: Registered named UNIX socket transport module.
[    0.158708] RPC: Registered udp transport module.
[    0.158713] RPC: Registered tcp transport module.
[    0.158718] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.160371] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[    0.163145] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[    0.171011] FS-Cache: Netfs 'nfs' registered for caching
[    0.171640] NFS: Registering the id_resolver key type
[    0.171670] Key type id_resolver registered
[    0.171676] Key type id_legacy registered
[    0.171691] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.173609] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    0.173741] io scheduler noop registered
[    0.173748] io scheduler deadline registered (default)
[    0.173914] io scheduler cfq registered
[    0.173921] io scheduler mq-deadline registered
[    0.173926] io scheduler kyber registered
[    0.176645] BCM2708FB: allocated DMA memory fad10000
[    0.176672] BCM2708FB: allocated DMA channel 0 @ bb813000
[    0.234650] Console: switching to colour frame buffer device 240x67
[    0.269690] bcm2835-rng 3f104000.rng: hwrng registered
[    0.269825] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
[    0.270283] vc-sm: Videocore shared memory driver
[    0.270556] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    0.280216] brd: module loaded
[    0.289271] loop: module loaded
[    0.289285] Loading iSCSI transport class v2.0-870.
[    0.290001] libphy: Fixed MDIO Bus: probed
[    0.290104] usbcore: registered new interface driver lan78xx
[    0.290155] usbcore: registered new interface driver smsc95xx
[    0.290171] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    0.318090] dwc_otg 3f980000.usb: base=0xf0980000
[    0.518316] Core Release: 2.80a
[    0.518325] Setting default values for core params
[    0.518358] Finished setting default values for core params
[    0.718621] Using Buffer DMA mode
[    0.718628] Periodic Transfer Interrupt Enhancement - disabled
[    0.718633] Multiprocessor Interrupt Enhancement - disabled
[    0.718640] OTG VER PARAM: 0, OTG VER FLAG: 0
[    0.718653] Dedicated Tx FIFOs mode
[    0.719005] WARN::dwc_otg_hcd_init:1046: FIQ DMA bounce buffers: virt = 0xbad04000 dma = 0xfad04000 len=9024
[    0.719031] FIQ FSM acceleration enabled for :
               Non-periodic Split Transactions
               Periodic Split Transactions
               High-Speed Isochronous Endpoints
               Interrupt/Control Split Transaction hack enabled
[    0.719038] dwc_otg: Microframe scheduler enabled
[    0.719092] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x805ed1d4
[    0.719103] WARN::hcd_init_fiq:460: FIQ ASM at 0x805ed53c length 36
[    0.719117] WARN::hcd_init_fiq:486: MPHI regs_base at 0xf0006000
[    0.719174] dwc_otg 3f980000.usb: DWC OTG Controller
[    0.719208] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    0.719240] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[    0.719289] Init: Port Power? op_state=1
[    0.719293] Init: Power Port (0)
[    0.719500] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.719510] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.719519] usb usb1: Product: DWC OTG Controller
[    0.719527] usb usb1: Manufacturer: Linux 4.14.94-v7+ dwc_otg_hcd
[    0.719536] usb usb1: SerialNumber: 3f980000.usb
[    0.720141] hub 1-0:1.0: USB hub found
[    0.720181] hub 1-0:1.0: 1 port detected
[    0.720726] dwc_otg: FIQ enabled
[    0.720731] dwc_otg: NAK holdoff enabled
[    0.720737] dwc_otg: FIQ split-transaction FSM enabled
[    0.720746] Module dwc_common_port init
[    0.721020] usbcore: registered new interface driver usb-storage
[    0.721193] mousedev: PS/2 mouse device common for all mice
[    0.721268] IR NEC protocol handler initialized
[    0.721273] IR RC5(x/sz) protocol handler initialized
[    0.721278] IR RC6 protocol handler initialized
[    0.721283] IR JVC protocol handler initialized
[    0.721288] IR Sony protocol handler initialized
[    0.721293] IR SANYO protocol handler initialized
[    0.721299] IR Sharp protocol handler initialized
[    0.721304] IR MCE Keyboard/mouse protocol handler initialized
[    0.721309] IR XMP protocol handler initialized
[    0.722050] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[    0.722335] bcm2835-cpufreq: min=600000 max=1200000
[    0.722694] sdhci: Secure Digital Host Controller Interface driver
[    0.722699] sdhci: Copyright(c) Pierre Ossman
[    0.723045] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe
[    0.723371] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
[    0.723466] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.724893] ledtrig-cpu: registered to indicate activity on CPUs
[    0.725082] hidraw: raw HID events driver (C) Jiri Kosina
[    0.725207] usbcore: registered new interface driver usbhid
[    0.725212] usbhid: USB HID core driver
[    0.725990] vchiq: vchiq_init_state: slot_zero = bad80000, is_master = 0
[    0.727556] [vc_sm_connected_init]: start
[    0.738196] [vc_sm_connected_init]: end - returning 0
[    0.738838] Initializing XFRM netlink socket
[    0.738862] NET: Registered protocol family 17
[    0.738964] Key type dns_resolver registered
[    0.739505] Registering SWP/SWPB emulation handler
[    0.740089] registered taskstats version 1
[    0.746077] uart-pl011 3f201000.serial: cts_event_workaround enabled
[    0.746162] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[    0.747947] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[    0.747957] mmc-bcm2835 3f300000.mmc: DMA channel allocated
[    0.812159] sdhost: log_buf @ bad07000 (fad07000)
[    0.855972] mmc-bcm2835 3f300000.mmc: card claims to support voltages below defined range
[    0.855981] mmc-bcm2835 3f300000.mmc: exceeding card's volts
[    0.891229] mmc1: error -110 whilst initialising MMC card
[    0.892495] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    0.893563] of_cfs_init
[    0.893712] of_cfs_init: OK
[    0.894263] Waiting for root device PARTUUID=e21979c8-02...
[    0.941602] Indeed it is in host mode hprt0 = 00021501
[    1.025395] random: fast init done
[    1.073471] mmc0: host does not support reading read-only switch, assuming write-enable
[    1.076700] mmc0: new high speed SDHC card at address aaaa
[    1.077236] mmcblk0: mmc0:aaaa SL32G 29.7 GiB
[    1.080089]  mmcblk0: p1 p2
[    1.125819] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    1.125879] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    1.137690] devtmpfs: mounted
[    1.141224] Freeing unused kernel memory: 1024K
[    1.151553] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    1.151690] Indeed it is in host mode hprt0 = 00001101
[    1.401845] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[    1.401863] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.402620] hub 1-1:1.0: USB hub found
[    1.402716] hub 1-1:1.0: 5 ports detected
[    1.605605] systemd[1]: System time before build time, advancing clock.
[    1.721643] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    1.736812] NET: Registered protocol family 10
[    1.737939] Segment Routing with IPv6
[    1.752214] ip_tables: (C) 2000-2006 Netfilter Core Team
[    1.771731] random: systemd: uninitialized urandom read (16 bytes read)
[    1.777968] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[    1.778547] systemd[1]: Detected architecture arm.
[    1.779467] systemd[1]: Set hostname to <raspberrypi>.
[    1.823244] random: systemd: uninitialized urandom read (16 bytes read)
[    1.852228] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    1.852251] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.855427] smsc95xx v1.0.6
[    1.859762] random: systemd-cryptse: uninitialized urandom read (16 bytes read)
[    1.945366] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:4a:5b:01
[    2.041587] usb 1-1.2: new low-speed USB device number 4 using dwc_otg
[    2.071865] Under-voltage detected! (0x00050005)
[    2.187066] usb 1-1.2: New USB device found, idVendor=413c, idProduct=301a
[    2.187080] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.187089] usb 1-1.2: Product: Dell MS116 USB Optical Mouse
[    2.187097] usb 1-1.2: Manufacturer: PixArt
[    2.191666] input: PixArt Dell MS116 USB Optical Mouse as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.0/0003:413C:301A.0001/input/input0
[    2.192037] hid-generic 0003:413C:301A.0001: input,hidraw0: USB HID v1.11 Mouse [PixArt Dell MS116 USB Optical Mouse] on usb-3f980000.usb-1.2/input0
[    2.291574] usb 1-1.4: new low-speed USB device number 5 using dwc_otg
[    2.306799] systemd[1]: Listening on udev Control Socket.
[    2.328025] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    2.328385] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[    2.328652] systemd[1]: Listening on fsck to fsckd communication Socket.
[    2.328891] systemd[1]: Listening on udev Kernel Socket.
[    2.329052] systemd[1]: Reached target Swap.
[    2.329832] systemd[1]: Created slice User and Session Slice.
[    2.436487] usb 1-1.4: New USB device found, idVendor=413c, idProduct=2003
[    2.436515] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.436524] usb 1-1.4: Product: Dell USB Keyboard
[    2.436532] usb 1-1.4: Manufacturer: Dell
[    2.449375] i2c /dev entries driver
[    2.458163] input: Dell Dell USB Keyboard as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4:1.0/0003:413C:2003.0002/input/input1
[    2.523008] hid-generic 0003:413C:2003.0002: input,hidraw1: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-3f980000.usb-1.4/input0
[    3.052762] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    3.134550] systemd-journald[86]: Received request to flush runtime journal from PID 1
[    3.924797] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[    3.930391] bcm2835_alsa bcm2835_alsa: card created with 8 channels
[    5.178843] uart-pl011 3f201000.serial: no DMA platform data
[    5.513658] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[    5.513916] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    6.537886] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k SSFS
[    7.132696] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[    7.134063] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    8.088737] random: crng init done
[    8.088747] random: 7 urandom warning(s) missed due to ratelimiting
[    8.311540] Voltage normalised (0x00000000)
[    9.861867] Bluetooth: Core ver 2.22
[    9.861926] NET: Registered protocol family 31
[    9.861930] Bluetooth: HCI device and connection manager initialized
[    9.861945] Bluetooth: HCI socket layer initialized
[    9.861954] Bluetooth: L2CAP socket layer initialized
[    9.861973] Bluetooth: SCO socket layer initialized
[    9.871229] Bluetooth: HCI UART driver ver 2.3
[    9.871238] Bluetooth: HCI UART protocol H4 registered
[    9.871242] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    9.871384] Bluetooth: HCI UART protocol Broadcom registered
[   10.210618] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   10.210627] Bluetooth: BNEP filters: protocol multicast
[   10.210643] Bluetooth: BNEP socket layer initialized
[   10.253563] Bluetooth: RFCOMM TTY layer initialized
[   10.253593] Bluetooth: RFCOMM socket layer initialized
[   10.253618] Bluetooth: RFCOMM ver 1.11
[   12.615171] fuse init (API version 7.26)

And then, I am getting different errors in each boot. Sometimes its:

  • [ 1.046241] mmc1: error -22 whilst initialising SDIO card
  • Sometimes it’s both, error -110 & error -84 on `MMC Card, such as below:
[    1.512902] mmc1: error -84 whilst initialising MMC card
[    1.602537] mmc-bcm2835 3f300000.mmc: card claims to support voltages below defined range
[    1.602558] mmc-bcm2835 3f300000.mmc: exceeding card's volts
[    1.628018] systemd[1]: System time before build time, advancing clock.
[    1.664046] mmc1: error -110 whilst initialising MMC card

@pelwell

I have never seen errors like that from a Pi. There is a slight chance that the Pi is being underpowered — what does vcgencmd get_throttled report? — but I think you have faulty hardware.

@iamhssingh

@pelwell I also thought that but it had happen earlier also, but somehow it got fix when I inserted an external WiFi. Also, the errors are not consistent.

Here’s the output of vcgencmd get_throttled:
throttled=0x50000

@pelwell

That output tells us that the Pi has suffered from a lack of voltage since it was first started to boot. The startup process is highly parallel, and current draw can be very high depending on the exact timing of events, something that will be affected by the addition of an external USB dongle.

We recommend a 2.5A supply for all Pi 3s, and take care to use good USB cables to avoid transmission losses. Powered hubs are preferred for most USB devices.

@iamhssingh

The same adapter and cable was working fine earlier. I will update on rating here. error -84 whilst initialising SDIO Card is consistently coming up. External WiFi Dongle is working fine. Bluetooth is also fine.

@pelwell

I also thought that but it had happen earlier also, but somehow it got fix when I inserted an external WiFi

I will update on rating here. error -84 whilst initialising SDIO Card is consistently coming up.

Read together, these statements could seem contradictory. Does the onboard WiFi ever work or not?

@iamhssingh

I also thought that but it had happen earlier also, but somehow it got fix when I inserted an external WiFi

This happened about 6-7 months ago. The same error came up but it fixed itself. WiFi used to work back in 2016 and then in 2017. In 2018 this error came up for the first time but it recovered by itself when I inserted external WiFi.

Now, this is 2019 and it’s not recovering.

@pelwell

So I stand by my original assessment that you have faulty hardware, with a side order of inadequate power supply. You could try to reduce your power consumption by adding «arm_freq=600» to config.txt and «nr_cpus=1» to cmdline.txt — yes, this will cripple performance, but it is just a test for now — but I have a feeling it won’t help.

@iamhssingh

@pelwell I am trying with One+ Dash Charger 5V & 4A adapter. Will update you on the same.

@iamhssingh

So I tried with One+ Dash Charge. No power undervoltage issue.

On the first boot I got some errors similar to this (I forgot to save dmesg):

[ 25.295147] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08000, err: -110
[ 25.295154] brcmfmac: brcmf_chip_recognition: chip backplane type 15 is not supported
[ 25.295158] brcmfmac: brcmf_sdio_probe_attach: brcmf_chip_attach failed!
[ 25.295162] brcmfmac: brcmf_sdio_probe: brcmf_sdio_probe_attach failed
[ 25.295231] brcmfmac: brcmf_ops_sdio_probe: F2 error, probe failed -19...

But on all future reboot I kept on getting:

mmc1: error -110 whilst initialising MMC card
mmc1: error -110 whilst initialising SDIO card

@pelwell

At the risk of sounding like a stuck record, I think your Pi has developed a hardware fault.

@iamhssingh

Well, unable to find a solution, I am also finally thinking that. If I upload images of my RPi, can someone on internet check and tell if there’s any burnt circuit or something like that? I hope I don’t sound dumb.

@pelwell

It’s very unlikely one could learn anything by inspection. The fact that the MMC interface sometimes find the WiFi chips suggests that there will be no obvious gross faults.

@iamhssingh

Well, damn! I did nothing wrong with my poor Raspberry Pi 3 to kill it’s WiFi. It’s sad.

@pelwell

It is sad — I’ve lost a few well-used (and misused) Pis over the years.

@iamhssingh

I know the issue is closed, but still sharing new dmesg output for other’s reference.

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.94-v7+ (dom@dom-XPS-13-9370) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1193 SMP Tue Jan 22 15:34:30 GMT 2019
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Rev 1.2
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 8 MiB at 0x3ac00000
[    0.000000] On node 0 totalpages: 242688
[    0.000000] free_area_init_node: node 0, pgdat 80c85780, node_mem_map ba39f000
[    0.000000]   Normal zone: 2133 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 242688 pages, LIFO batch:31
[    0.000000] percpu: Embedded 17 pages/cpu @ba348000 s38720 r8192 d22720 u69632
[    0.000000] pcpu-alloc: s38720 r8192 d22720 u69632 alloc=17*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 240555
[    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTUUID=e21979c8-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 940232K/970752K available (7168K kernel code, 577K rwdata, 2080K rodata, 1024K init, 698K bss, 22328K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xbb800000 - 0xff800000   (1088 MB)
                   lowmem  : 0x80000000 - 0xbb400000   ( 948 MB)
                   modules : 0x7f000000 - 0x80000000   (  16 MB)
                     .text : 0x80008000 - 0x80800000   (8160 kB)
                     .init : 0x80b00000 - 0x80c00000   (1024 kB)
                     .data : 0x80c00000 - 0x80c906b4   ( 578 kB)
                      .bss : 0x80c97ef8 - 0x80d468f0   ( 699 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 25296 entries in 75 pages
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[    0.000018] Switching to timer-based delay loop, resolution 52ns
[    0.000267] Console: colour dummy device 80x30
[    0.000286] console [tty1] enabled
[    0.000311] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[    0.000326] pid_max: default: 32768 minimum: 301
[    0.000645] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000660] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001599] Disabling memory control group subsystem
[    0.001675] CPU: Testing write buffer coherency: ok
[    0.002090] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.002495] Setting up static identity map for 0x100000 - 0x10003c
[    0.002618] Hierarchical SRCU implementation.
[    0.003298] smp: Bringing up secondary CPUs ...
[    0.004077] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.004925] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.005751] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.005855] smp: Brought up 1 node, 4 CPUs
[    0.005866] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[    0.005872] CPU: All CPU(s) started in HYP mode.
[    0.005876] CPU: Virtualization extensions available.
[    0.006799] devtmpfs: initialized
[    0.016929] random: get_random_u32 called from bucket_table_alloc+0xfc/0x24c with crng_init=0
[    0.017699] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[    0.017919] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.017936] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.018489] pinctrl core: initialized pinctrl subsystem
[    0.019232] NET: Registered protocol family 16
[    0.021975] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.026783] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.026791] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.026995] Serial: AMBA PL011 UART driver
[    0.028652] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.029114] uart-pl011 3f201000.serial: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe
[    0.060425] bcm2835-dma 3f007000.dma: DMA legacy API manager at bb813000, dmachans=0x1
[    0.061856] SCSI subsystem initialized
[    0.062079] usbcore: registered new interface driver usbfs
[    0.062130] usbcore: registered new interface driver hub
[    0.062215] usbcore: registered new device driver usb
[    0.070085] raspberrypi-firmware soc:firmware: Attached to firmware from 2019-01-22 16:50
[    0.071486] clocksource: Switched to clocksource arch_sys_counter
[    0.148555] VFS: Disk quotas dquot_6.6.0
[    0.148637] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.148822] FS-Cache: Loaded
[    0.149004] CacheFiles: Loaded
[    0.156878] NET: Registered protocol family 2
[    0.157594] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.157717] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.157903] TCP: Hash tables configured (established 8192 bind 8192)
[    0.158033] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.158076] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.158306] NET: Registered protocol family 1
[    0.158779] RPC: Registered named UNIX socket transport module.
[    0.158785] RPC: Registered udp transport module.
[    0.158790] RPC: Registered tcp transport module.
[    0.158795] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.160439] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[    0.163204] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[    0.171080] FS-Cache: Netfs 'nfs' registered for caching
[    0.171710] NFS: Registering the id_resolver key type
[    0.171742] Key type id_resolver registered
[    0.171748] Key type id_legacy registered
[    0.171764] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.173680] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    0.173812] io scheduler noop registered
[    0.173819] io scheduler deadline registered (default)
[    0.173983] io scheduler cfq registered
[    0.173990] io scheduler mq-deadline registered
[    0.173995] io scheduler kyber registered
[    0.176713] BCM2708FB: allocated DMA memory fad10000
[    0.176740] BCM2708FB: allocated DMA channel 0 @ bb813000
[    0.187208] Console: switching to colour frame buffer device 90x30
[    0.194378] bcm2835-rng 3f104000.rng: hwrng registered
[    0.194508] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
[    0.194937] vc-sm: Videocore shared memory driver
[    0.195208] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    0.204650] brd: module loaded
[    0.213305] loop: module loaded
[    0.213318] Loading iSCSI transport class v2.0-870.
[    0.213958] libphy: Fixed MDIO Bus: probed
[    0.214052] usbcore: registered new interface driver lan78xx
[    0.214103] usbcore: registered new interface driver smsc95xx
[    0.214118] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    0.242001] dwc_otg 3f980000.usb: base=0xf0980000
[    0.442204] Core Release: 2.80a
[    0.442213] Setting default values for core params
[    0.442243] Finished setting default values for core params
[    0.642496] Using Buffer DMA mode
[    0.642502] Periodic Transfer Interrupt Enhancement - disabled
[    0.642507] Multiprocessor Interrupt Enhancement - disabled
[    0.642513] OTG VER PARAM: 0, OTG VER FLAG: 0
[    0.642530] Dedicated Tx FIFOs mode
[    0.642893] WARN::dwc_otg_hcd_init:1046: FIQ DMA bounce buffers: virt = 0xbad04000 dma = 0xfad04000 len=9024
[    0.642917] FIQ FSM acceleration enabled for :
               Non-periodic Split Transactions
               Periodic Split Transactions
               High-Speed Isochronous Endpoints
               Interrupt/Control Split Transaction hack enabled
[    0.642925] dwc_otg: Microframe scheduler enabled
[    0.642970] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x805ed1d4
[    0.642981] WARN::hcd_init_fiq:460: FIQ ASM at 0x805ed53c length 36
[    0.642993] WARN::hcd_init_fiq:486: MPHI regs_base at 0xf0006000
[    0.643043] dwc_otg 3f980000.usb: DWC OTG Controller
[    0.643074] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    0.643105] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[    0.643152] Init: Port Power? op_state=1
[    0.643157] Init: Power Port (0)
[    0.643353] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.643364] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.643372] usb usb1: Product: DWC OTG Controller
[    0.643380] usb usb1: Manufacturer: Linux 4.14.94-v7+ dwc_otg_hcd
[    0.643388] usb usb1: SerialNumber: 3f980000.usb
[    0.643969] hub 1-0:1.0: USB hub found
[    0.644007] hub 1-0:1.0: 1 port detected
[    0.644495] dwc_otg: FIQ enabled
[    0.644501] dwc_otg: NAK holdoff enabled
[    0.644505] dwc_otg: FIQ split-transaction FSM enabled
[    0.644514] Module dwc_common_port init
[    0.644725] usbcore: registered new interface driver usb-storage
[    0.644885] mousedev: PS/2 mouse device common for all mice
[    0.644952] IR NEC protocol handler initialized
[    0.644958] IR RC5(x/sz) protocol handler initialized
[    0.644963] IR RC6 protocol handler initialized
[    0.644968] IR JVC protocol handler initialized
[    0.644972] IR Sony protocol handler initialized
[    0.644977] IR SANYO protocol handler initialized
[    0.644982] IR Sharp protocol handler initialized
[    0.644988] IR MCE Keyboard/mouse protocol handler initialized
[    0.644993] IR XMP protocol handler initialized
[    0.645650] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[    0.645902] bcm2835-cpufreq: min=600000 max=1200000
[    0.646245] sdhci: Secure Digital Host Controller Interface driver
[    0.646250] sdhci: Copyright(c) Pierre Ossman
[    0.646594] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe
[    0.646911] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
[    0.647003] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.648380] ledtrig-cpu: registered to indicate activity on CPUs
[    0.648547] hidraw: raw HID events driver (C) Jiri Kosina
[    0.648699] usbcore: registered new interface driver usbhid
[    0.648704] usbhid: USB HID core driver
[    0.649415] vchiq: vchiq_init_state: slot_zero = bad80000, is_master = 0
[    0.650794] [vc_sm_connected_init]: start
[    0.659492] [vc_sm_connected_init]: end - returning 0
[    0.660101] Initializing XFRM netlink socket
[    0.660123] NET: Registered protocol family 17
[    0.660222] Key type dns_resolver registered
[    0.660783] Registering SWP/SWPB emulation handler
[    0.661323] registered taskstats version 1
[    0.667218] uart-pl011 3f201000.serial: cts_event_workaround enabled
[    0.667286] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[    0.669025] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[    0.669035] mmc-bcm2835 3f300000.mmc: DMA channel allocated
[    0.722122] sdhost: log_buf @ bad07000 (fad07000)
[    0.760673] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    0.762240] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.763788] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.766565] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    0.801507] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    0.802508] of_cfs_init
[    0.802597] of_cfs_init: OK
[    0.803169] Waiting for root device PARTUUID=e21979c8-02...
[    0.844026] random: fast init done
[    0.861688] Indeed it is in host mode hprt0 = 00021501
[    0.943419] mmc1: new high speed SDIO card at address 0001
[    0.963325] mmc0: host does not support reading read-only switch, assuming write-enable
[    0.966573] mmc0: new high speed SDHC card at address aaaa
[    0.966999] mmcblk0: mmc0:aaaa SL32G 29.7 GiB
[    0.969490]  mmcblk0: p1 p2
[    0.997829] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
[    0.997845] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
[    1.071531] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    1.071674] Indeed it is in host mode hprt0 = 00001101
[    1.179600] EXT4-fs (mmcblk0p2): recovery complete
[    1.217745] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    1.217805] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    1.227231] devtmpfs: mounted
[    1.230647] Freeing unused kernel memory: 1024K
[    1.311798] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[    1.311812] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.312413] hub 1-1:1.0: USB hub found
[    1.312503] hub 1-1:1.0: 5 ports detected
[    1.631535] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    1.643297] systemd[1]: System time before build time, advancing clock.
[    1.761839] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    1.761857] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.764599] smsc95xx v1.0.6
[    1.781986] NET: Registered protocol family 10
[    1.783018] Segment Routing with IPv6
[    1.796921] ip_tables: (C) 2000-2006 Netfilter Core Team
[    1.815742] random: systemd: uninitialized urandom read (16 bytes read)
[    1.822711] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[    1.823954] systemd[1]: Detected architecture arm.
[    1.829052] systemd[1]: Set hostname to <raspberrypi>.
[    1.855093] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:4a:5b:01
[    1.875035] random: systemd: uninitialized urandom read (16 bytes read)
[    1.900436] random: systemd-sysv-ge: uninitialized urandom read (16 bytes read)
[    2.352710] systemd[1]: Listening on udev Kernel Socket.
[    2.353323] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    2.353603] systemd[1]: Listening on udev Control Socket.
[    2.353882] systemd[1]: Listening on Syslog Socket.
[    2.354629] systemd[1]: Created slice System Slice.
[    2.355287] systemd[1]: Created slice system-systemdx2dfsck.slice.
[    2.358671] systemd[1]: Mounting Debug File System...
[    2.469696] i2c /dev entries driver
[    2.927464] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    2.999378] systemd-journald[87]: Received request to flush runtime journal from PID 1
[    3.614626] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[    3.623475] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001
[    3.623714] usbcore: registered new interface driver brcmfmac
[    3.665323] brcmfmac: brcmf_sdiod_ramrw: membytes transfer failed
[    3.669653] brcmfmac: brcmf_sdio_download_code_file: error -110 on writing 388739 membytes at 0x00000000
[    3.669727] brcmfmac: brcmf_sdio_download_firmware: dongle image file download failed
[    3.726150] brcmfmac: brcmf_sdiod_regrw_helper: failed to write data F1@0x1000e, err: -110
[    3.726166] brcmfmac: brcmf_sdio_htclk: HT Avail request error: -110
[    3.730555] brcmfmac: brcmf_sdiod_regrw_helper: failed to write data F1@0x0a024, err: -110
[    3.734840] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1000e, err: -110
[    3.734855] brcmfmac: brcmf_sdio_bus_stop: Failed to force clock for F2: err -110
[    3.739115] brcmfmac: brcmf_sdiod_regrw_helper: failed to write data F1@0x0a020, err: -110
[    3.743677] brcmfmac: brcmf_sdiod_regrw_helper: failed to write data F1@0x1000e, err: -110
[    3.743690] brcmfmac: brcmf_sdio_htclk: HT Avail request error: -110
[    3.788216] brcmfmac: brcmf_sdiod_regrw_helper: failed to write data F1@0x0b800, err: -110
[    3.791768] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0b800, err: -110
[    3.796100] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0b800, err: -110
[    3.800398] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0b800, err: -110
[    3.803688] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0b800, err: -110
[    3.807854] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0b800, err: -110
[    3.820257] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0c800, err: -110
[    3.823704] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0c800, err: -110
[    3.827893] brcmfmac: brcmf_sdiod_regrw_helper: failed to write data F1@0x0c800, err: -110
[    3.833636] brcmfmac: brcmf_sdiod_regrw_helper: failed to write data F1@0x0c408, err: -110
[    3.837786] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0c408, err: -110
[    3.841553] brcmfmac: brcmf_sdiod_regrw_helper: failed to write data F1@0x1000a, err: -110
[    3.841566] brcmfmac: brcmf_sdiod_set_sbaddr_window: failed at addr: 0x1000a
[    3.845727] brcmfmac: brcmf_sdiod_regrw_helper: failed to write data F1@0x1000b, err: -110
[    3.845735] brcmfmac: brcmf_sdiod_set_sbaddr_window: failed at addr: 0x1000b
[    5.729808] uart-pl011 3f201000.serial: no DMA platform data
[    6.012902] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[    6.013038] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    6.037381] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k SSFS
[    7.648623] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[    7.650777] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    9.359142] random: crng init done
[    9.359152] random: 7 urandom warning(s) missed due to ratelimiting
[   11.438336] Bluetooth: Core ver 2.22
[   11.438420] NET: Registered protocol family 31
[   11.438426] Bluetooth: HCI device and connection manager initialized
[   11.438446] Bluetooth: HCI socket layer initialized
[   11.438459] Bluetooth: L2CAP socket layer initialized
[   11.438494] Bluetooth: SCO socket layer initialized
[   11.464882] Bluetooth: HCI UART driver ver 2.3
[   11.464901] Bluetooth: HCI UART protocol H4 registered
[   11.464907] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   11.465175] Bluetooth: HCI UART protocol Broadcom registered
[   11.743960] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   11.743970] Bluetooth: BNEP filters: protocol multicast
[   11.743982] Bluetooth: BNEP socket layer initialized
[   11.792830] Bluetooth: RFCOMM TTY layer initialized
[   11.792849] Bluetooth: RFCOMM socket layer initialized
[   11.792868] Bluetooth: RFCOMM ver 1.11
[   11.896904] fuse init (API version 7.26)

All brcmfmac are in red.

@MarcDorval

Most probably an issue similar to what I’m facing… SDIO speed changed from 125/3=41.66 to 200/4=50.0 MHz, and your HW doesn’t support this speed.
You may get it to work adding
dtoverlay=wfx-sdio,sdio_overclock=42
to your /boot/config.txt file

@cigzigwon

@iamhssingh funny stuff isn’t it? Mine lasted for like two months and died. It’s hardware related but I will assume @MarcDorval has a good experiment me for today. I have a pile building up and I doubt these boards interface with the SDIO isn’t the issue but they are fs slow

I have a problem trying to mount a SD card in Ubuntu 12.04. The message what I get from the system is:

mmc0: error -110 whilst initialising SD card

I’m on the 3.5.0-24-generic kernel.

I check previous kernel 3.5.0-15 and card is on the system. I think is some bug in kernel.

I was looking some solution on web. They say my card is dead (but is working)

What I should do?

Some more information on this issue here. If someone have more question about my hardware just ask.

Braiam's user avatar

Braiam

66.2k30 gold badges174 silver badges262 bronze badges

asked Feb 16, 2013 at 12:49

Grabasimo's user avatar

5

Basically this error arises only when the SDcard got damaged. But as you mentioned its working, Please try the following steps and share your feedback.

  • Please check the output of dmesg or lsusb to check whether it detects the SD card.
  • Open the «Disk Utility» application and check whether your SD card is listed. If its listed, just click it -> Unmount Volume -> Format the Volume with suitable filesystem.
  • Also, try mounting the SD card on Windows and check whether it is working or not.

Also, you can downgrade your kernel by installing the old kernel / latest stable kernel version with sudo apt-get update && sudo apt-get dist-upgrade && sudo apt-get autoremove.

wget the latest stable kernal from Kernel Website and install it with sudo dpkg -i *.deb && sudo update-grub2

Please select the proper kernel while booting and check whether your SD card mounts well!

Kalle Richter's user avatar

Kalle Richter

5,78619 gold badges67 silver badges100 bronze badges

answered Feb 24, 2014 at 11:29

Naga2Raja's user avatar

Naga2RajaNaga2Raja

2582 silver badges7 bronze badges

#1 2012-06-17 09:14:06

Lockheed
Member
Registered: 2010-03-16
Posts: 1,475

error -110 whilst initialising SD card

When I enter my 8GB Class 6 Samsung MicroSD card into the cardreader (mmc), 4 times out of 5 it does not mount. dmesg gives this:

error -110 whilst initialising SD card

I am not sure, but it appears to be timeout issue (the system does not wait long enough?).

The behaviour of the card in the mobile phone:
The same card mounts perfectly fine each and every time on Android 2.4 and/or ClockWordMod bootloader, but on Android 4 and/or 4ext bootloader it exhibits the same issues as on Arch.

Last edited by Lockheed (2012-06-17 09:16:08)


Laptop: ThinkPad T420s, i7/i5, 16GB RAM, 1080p IPS mod, Arch | HTPC/Server/fw: Zotac AQ01, A4-5000 Kabini, 8GB, Arch/lxd NethServer

#2 2012-06-25 10:51:53

iggy
Member
From: Germany, L.E. — Leipzig
Registered: 2004-10-17
Posts: 367

Re: error -110 whilst initialising SD card

Same problem here on a XPS M1330. Since the last two kernel updates my Samsung 16GB class6 SD card won’t get mounted. Dmesg gives me the same error message.

I think this is a kernel driver problem, as others have this error too:
https://bbs.archlinux.org/viewtopic.php … 8#p1118218


sorry for my bad english smile

#3 2012-06-30 22:10:38

Lockheed
Member
Registered: 2010-03-16
Posts: 1,475

Re: error -110 whilst initialising SD card

Try removing and reinserting the card several times. Mine usually mounts once in ever 7 times.


Laptop: ThinkPad T420s, i7/i5, 16GB RAM, 1080p IPS mod, Arch | HTPC/Server/fw: Zotac AQ01, A4-5000 Kabini, 8GB, Arch/lxd NethServer

#4 2012-07-03 21:58:23

iggy
Member
From: Germany, L.E. — Leipzig
Registered: 2004-10-17
Posts: 367

Re: error -110 whilst initialising SD card

This is not really a fix for the problem. No one else having this error?


sorry for my bad english smile

#5 2015-02-14 19:30:33

friendofarch
Member
Registered: 2013-12-30
Posts: 59

Re: error -110 whilst initialising SD card

Did you find a solution back than? I have the same problem for the first time today!

#6 2015-02-14 19:43:51

Lockheed
Member
Registered: 2010-03-16
Posts: 1,475

Re: error -110 whilst initialising SD card

The problem is that some cards are just too slow to initialise, and kernel gives up on waiting for them.
For mobile phone,  there is no solution other than using older kernel (in some GingerBread ROM) or changing the SD card.
For computer, just change the card. I don’t think it’s worth the trouble trying to solve it in other ways.

Last edited by Lockheed (2015-02-14 19:46:08)


Laptop: ThinkPad T420s, i7/i5, 16GB RAM, 1080p IPS mod, Arch | HTPC/Server/fw: Zotac AQ01, A4-5000 Kabini, 8GB, Arch/lxd NethServer

I have noticed troubles with my microSD card in my Android phone and when I tried to insert it into my Linux laptop, I get the following error in dmesg:

[  247.588279] mmc0: error -123 whilst initialising SD card
[  247.591314] sdhci-pci 0000:0d:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
[  247.648629] sdhci-pci 0000:0d:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
[  248.903044] mmc0: card never left busy state
[  248.903051] mmc0: error -110 whilst initialising SD card
[  248.907007] sdhci-pci 0000:0d:00.1: Will use DMA mode even though HW doesn't fully claim to support it.

Does this mean my microSD card is broken? How could it suddenly happen in my phone? Is there no way to recover eve partially the data on it?

drs's user avatar

drs

2,5942 gold badges15 silver badges15 bronze badges

asked Dec 7, 2014 at 20:05

denisq's user avatar

2

Your SD card has died. This happens over time, anything like a drop or a lot of use can cause a SD card to die. I have had the same thing happen to me on a 16GB micro SD card used with my Raspberry Pi 2. It just stopped working one day.

The only way you could possibly get the data off the SD card at this point is to take it to a professional in the Data Recovery Field.

Kalle Richter's user avatar

answered Nov 18, 2015 at 14:04

Lektonic's user avatar

LektonicLektonic

8527 silver badges17 bronze badges

2

Do you use an SD adapter with a mechanical write lock switch?

Indeed, an old SD card of mine (no adapter needed) has the same problem on my Lenovo ThinkPad E540. The solution in my case is toggling the write lock switch a couple times. Since this is purely mechanical, I suspect a buggy/mangled card port — mine looks and… «sounds» pretty flimsy!

answered Dec 7, 2017 at 20:58

sphakka's user avatar

sphakkasphakka

1971 silver badge4 bronze badges

1

I see exactly the same error in my Lenovo Laptop while trying to mount a SD card, and I must say that SD cards support on the Linux desktop is unfortunately suboptimal. The same card works perfectly fine in my Android phone and in my camera!

As a workaround, to make it work in the desktop, the only solution I have found is leaving it connected, and waiting for a few minutes until the error stops and the device appears.

answered Oct 25, 2016 at 2:57

admirabilis's user avatar

2

Try connecting the SD card using a USB memory card reader.

This worked in my case, a Lenovo laptop running Ubuntu 16.04, and the SD card is definitely recognized in other operating systems.

Instead of getting the error messages when running dmesg

[  882.603991] mmc0: card never left busy state
[  882.604001] mmc0: error -110 whilst initialising SD card

I get the success messages

[ 1724.883050] sd 6:0:0:2: [sdd] 250607616 512-byte logical blocks: (128 GB/119 GiB)
[ 1724.888318]  sdd: sdd1

I’m not sure if reading speed is as fast as connecting the SD directly to the laptop but I’m glad the SD is at least recognized.

answered Nov 6, 2016 at 13:39

Organic Addict's user avatar

I’ve run into this with almost-new SD cards on modern Linux machines, where the same cards work fine in Raspberry Pis (running Linux!) with no hitches. My suggestion is first to:

  • remove, wait a few seconds, and re-insert the card
  • running sudo partprobe occasionally works (you might need to install a package first depending on your system)
  • as Teresa says, wait a few minutes and the kernel will be able to detect the card

Oh, and backup your card because it could well be about to die, regardless of age.

answered Jul 12, 2017 at 14:22

Jonny's user avatar

JonnyJonny

1214 bronze badges

0

τοΖεη,

gena@Lenovo-B570e ~ $ lsusb
Bus 002 Device 004: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Bus 002 Device 003: ID 046d:c24a Logitech, Inc. G600 Gaming Mouse
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0bda:58e4 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
gena@Lenovo-B570e ~ $ lsmod
Module                  Size  Used by
bbswitch               16384  0
bnep                   20480  2
rfcomm                 69632  0
bluetooth             516096  10 bnep,rfcomm
binfmt_misc            20480  1
arc4                   16384  2
brcmsmac              565248  0
cordic                 16384  1 brcmsmac
brcmutil               16384  1 brcmsmac
b43                   413696  0
mac80211              733184  2 b43,brcmsmac
nvidia               8642560  65
cfg80211              561152  3 b43,brcmsmac,mac80211
uvcvideo               90112  0
ssb                    65536  1 b43
videobuf2_vmalloc      16384  1 uvcvideo
videobuf2_memops       16384  1 videobuf2_vmalloc
videobuf2_v4l2         28672  1 uvcvideo
videobuf2_core         36864  2 uvcvideo,videobuf2_v4l2
v4l2_common            16384  1 videobuf2_v4l2
videodev              180224  4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2
snd_hda_codec_hdmi     53248  1
acer_wmi               20480  0
snd_hda_codec_realtek    81920  1
snd_hda_codec_generic    73728  1 snd_hda_codec_realtek
rtsx_usb_ms            20480  0
media                  24576  2 uvcvideo,videodev
memstick               20480  1 rtsx_usb_ms
snd_hda_intel          36864  6
snd_hda_codec         135168  4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel
snd_hda_core           73728  5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
intel_rapl             20480  0
x86_pkg_temp_thermal    16384  0
snd_hwdep              16384  1 snd_hda_codec
intel_powerclamp       16384  0
coretemp               16384  0
kvm_intel             167936  0
snd_pcm               106496  6 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_core
kvm                   532480  1 kvm_intel
snd_seq_midi           16384  0
snd_seq_midi_event     16384  1 snd_seq_midi
snd_rawmidi            32768  1 snd_seq_midi
snd_seq                69632  2 snd_seq_midi_event,snd_seq_midi
snd_seq_device         16384  3 snd_seq,snd_rawmidi,snd_seq_midi
snd_timer              32768  2 snd_pcm,snd_seq
snd                    81920  21 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,snd_seq_device
bcma                   53248  3 b43,brcmsmac
dm_multipath           24576  0
irqbypass              16384  1 kvm
crct10dif_pclmul       16384  0
crc32_pclmul           16384  0
cryptd                 20480  0
mei_me                 36864  0
mei                   102400  1 mei_me
joydev                 20480  0
input_leds             16384  0
serio_raw              16384  0
soundcore              16384  1 snd
shpchp                 36864  0
lpc_ich                24576  0
parport_pc             36864  0
ppdev                  20480  0
ideapad_laptop         24576  0
mac_hid                16384  0
sparse_keymap          16384  2 acer_wmi,ideapad_laptop
wmi                    20480  2 acer_wmi,ideapad_laptop
lp                     20480  0
parport                49152  3 lp,ppdev,parport_pc
dm_mirror              24576  0
dm_region_hash         20480  1 dm_mirror
dm_log                 20480  2 dm_region_hash,dm_mirror
rtsx_usb_sdmmc         28672  0
rtsx_usb               24576  2 rtsx_usb_sdmmc,rtsx_usb_ms
hid_generic            16384  0
usbhid                 49152  0
hid                   118784  2 hid_generic,usbhid
i915                 1204224  3
i2c_algo_bit           16384  1 i915
drm_kms_helper        139264  1 i915
syscopyarea            16384  1 drm_kms_helper
ahci                   36864  3
sysfillrect            16384  1 drm_kms_helper
sysimgblt              16384  1 drm_kms_helper
libahci                32768  1 ahci
psmouse               122880  0
fb_sys_fops            16384  1 drm_kms_helper
r8169                  81920  0
drm                   360448  9 i915,drm_kms_helper,nvidia
mii                    16384  1 r8169
video                  40960  3 i915,acer_wmi,ideapad_laptop
fjes                   28672  0

victor00000, а как понять, что именно его?

jura12, к сожалению, нет(

I have an issue with my Arch.I insert the SD I can’t detect it.

Also I find the following error kernel log:

  uname -a 
    Linux localhost.localdomain 4.9.6-1-ARCH #1 SMP PREEMPT Thu Jan 26 09:22:26 CET 2017 x86_64 GNU/Linux

    dmesg
    [    3.663535] mmc0: error -110 whilst initialising SD card
    [    4.515911] random: fast init done
    [    4.720224] mmc0: error -110 whilst initialising SD card

lspci -v 
00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 08)
    Subsystem: Lenovo Device 5048
    Flags: bus master, fast devsel, latency 0
    Capabilities: <access denied>
    Kernel driver in use: skl_uncore

00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) (prog-if 00 [VGA controller])
    Subsystem: Lenovo Device 5048
    Flags: bus master, fast devsel, latency 0, IRQ 128
    Memory at f0000000 (64-bit, non-prefetchable) [size=16M]
    Memory at e0000000 (64-bit, prefetchable) [size=256M]
    I/O ports at 3000 [size=64]
    [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
    Capabilities: <access denied>
    Kernel driver in use: i915
    Kernel modules: i915

00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) (prog-if 30 [XHCI])
    Subsystem: Lenovo Device 5048
    Flags: bus master, medium devsel, latency 0, IRQ 123
    Memory at f1220000 (64-bit, non-prefetchable) [size=64K]
    Capabilities: <access denied>
    Kernel driver in use: xhci_hcd
    Kernel modules: xhci_pci

00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
    Subsystem: Lenovo Device 5048
    Flags: bus master, fast devsel, latency 0, IRQ 18
    Memory at f124a000 (64-bit, non-prefetchable) [size=4K]
    Capabilities: <access denied>
    Kernel driver in use: intel_pch_thermal
    Kernel modules: intel_pch_thermal

00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
    Subsystem: Lenovo Device 5048
    Flags: bus master, fast devsel, latency 0, IRQ 127
    Memory at f124b000 (64-bit, non-prefetchable) [size=4K]
    Capabilities: <access denied>
    Kernel driver in use: mei_me
    Kernel modules: mei_me

00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21) (prog-if 01 [AHCI 1.0])
    Subsystem: Lenovo Device 5048
    Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 124
    Memory at f1248000 (32-bit, non-prefetchable) [size=8K]
    Memory at f124e000 (32-bit, non-prefetchable) [size=256]
    I/O ports at 3080 [size=8]
    I/O ports at 3088 [size=4]
    I/O ports at 3060 [size=32]
    Memory at f124c000 (32-bit, non-prefetchable) [size=2K]
    Capabilities: <access denied>
    Kernel driver in use: ahci
    Kernel modules: ahci

00:1c.0 PCI bridge: Intel Corporation Device 9d12 (rev f1) (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0, IRQ 18
    Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
    Memory behind bridge: f1100000-f11fffff
    Capabilities: <access denied>
    Kernel driver in use: pcieport
    Kernel modules: shpchp

00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0, IRQ 17
    Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
    Memory behind bridge: f1000000-f10fffff
    Capabilities: <access denied>
    Kernel driver in use: pcieport
    Kernel modules: shpchp

00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
    Subsystem: Lenovo Device 5048
    Flags: bus master, medium devsel, latency 0

00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
    Subsystem: Lenovo Device 5048
    Flags: bus master, fast devsel, latency 0
    Memory at f1244000 (32-bit, non-prefetchable) [size=16K]
    Kernel driver in use: intel_pmc_core

00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
    Subsystem: Lenovo Device 5048
    Flags: bus master, fast devsel, latency 64, IRQ 129
    Memory at f1240000 (64-bit, non-prefetchable) [size=16K]
    Memory at f1230000 (64-bit, non-prefetchable) [size=64K]
    Capabilities: <access denied>
    Kernel driver in use: snd_hda_intel
    Kernel modules: snd_hda_intel, snd_soc_skl

00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
    Subsystem: Lenovo Device 5048
    Flags: medium devsel, IRQ 16
    Memory at f124d000 (64-bit, non-prefetchable) [size=256]
    I/O ports at efa0 [size=32]
    Kernel driver in use: i801_smbus
    Kernel modules: i2c_i801

00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection I219-V (rev 21)
    Subsystem: Lenovo Device 5048
    Flags: bus master, fast devsel, latency 0, IRQ 125
    Memory at f1200000 (32-bit, non-prefetchable) [size=128K]
    Capabilities: <access denied>
    Kernel driver in use: e1000e
    Kernel modules: e1000e

01:00.0 Network controller: Intel Corporation Intel Dual Band Wireless-AC 3165 Plus Bluetooth (rev 99)
    Subsystem: Intel Corporation Device 4210
    Flags: bus master, fast devsel, latency 0, IRQ 126
    Memory at f1100000 (64-bit, non-prefetchable) [size=8K]
    Capabilities: <access denied>
    Kernel driver in use: iwlwifi
    Kernel modules: iwlwifi

02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01)
    Subsystem: Lenovo Device 5048
    Flags: bus master, fast devsel, latency 0, IRQ 122
    Memory at f1000000 (32-bit, non-prefetchable) [size=4K]
    Capabilities: <access denied>
    Kernel driver in use: rtsx_pci
    Kernel modules: rtsx_pci

So I can fix this?

Понравилась статья? Поделить с друзьями:
  • Mmc has detected an error in a snap in and will unload it
  • Mmc exe системная ошибка
  • Mmc exe администратор заблокировал выполнение этого приложения как исправить
  • Mmc asa hardlock error 14
  • Mlt как изменить формат