Raspberry Pi3 anyone loose eth0 with the last update?
Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
FWIW I lost wlan0 after one of the previous updates. It'll connect but won't associate (if that is the correct term) with my house wifi. I can ssh into it via wifi but nothing I have tried will get the wifi to (a)surf the net and (b)connect on boot.
I've googled the thing for hours and tried every config of inet1.conf and wpa_supplicant I could find, reverted to older firmware etc etc etc but I just am missing something. Bluetooth is a no-go also.
Right now it's on
Code:
uname -r
4.4.11-v7-arm
and chugging along quite well so I'm nervous to run another update or upgrade.
Perhaps something went wonky on the Broadcom side of things?
Well that is odd, just putting the microSD back in the Pi3 it booted fine.
I had that too, each update from rpi-update caused a kernel panic upon reboot. I worked around it by doing an fsck -trawl on the first partition of the card on a separate machine.
Sometimes Slackware ARM on my RPi3 crashes, which usually only happens while compiling. I haven't worked out yet what causes the problem but ejecting and re-inserting the microSD card usually solves it. This can happen after the same card has been working for days/weeks without a problem and, from experience, I've found this happens with the Samsung EVO microSD cards more so than other brands.
I do the same thing on the rare occasions when it crashes during boot-up and/or results in a kernel panic. There's no reason why taking the microSD card out and plugging it straight back in should fix the problem, but it seems to work every time.
I used rasbain's cmdline.txt and just removed what I didn't need and added a couple thing I did.
My working system gave an error on the sd card last night and rebooted to a kernel panic. Pulling the card out and putting it back in it did boot without a panic but the drive needed checked. After checking and fixing it reboots to a panic again.
I used to be able to run for months without a problem until I started running the rpi-update so maybe there is something related there.
Ok, so confirmed something with the kernel or drivers rpi-update installs. I rebuilt one and didn't do the update and its been fine.
I used to be able to run for months without a problem until I started running the rpi-update so maybe there is something related there.
It would surprise me to learn that rpi-update was the culprit. I have been advised by somebody more qualified and learned than me that it could be a timing (sync) problem between the system and sd card which causes problem such as these.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.