LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM
User Name
Password
Slackware - ARM This forum is for the discussion of Slackware ARM.

Notices


Reply
  Search this Thread
Old 12-11-2019, 01:06 PM   #1
Tonus
Member
 
Registered: Jan 2007
Location: Paris, France
Distribution: Slackware-current
Posts: 584
Blog Entries: 3

Rep: Reputation: 152Reputation: 152
Can't ssh in current installer on rpi3 b+


Hi all,

Everything is in the title. The 14.2 is up and running but it is a bit old and I would rather have the same version on rpi3 and rpi4...

Since I have no screen nor spare mouse and keyboard I don't have a clue about what's going on. I troubleshooted almost everything I thought of before trying 14.2 instead of current (ethernet cable, sdcard, gateway, power).

Any advice would be thankfully welcomed!

Regards

Last edited by Tonus; 12-14-2019 at 04:59 PM. Reason: Changed title to be exact
 
Old 12-11-2019, 02:51 PM   #2
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 10,851

Rep: Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236
ADVICE:

Stop messing about, beg/borrow or buy a spare keyboard & mouse, & sort yourself out. You're only making work for yourself until you do.
 
Old 12-11-2019, 03:15 PM   #3
mralk3
Senior Member
 
Registered: May 2015
Location: Utah, USA
Distribution: Slackware
Posts: 1,391

Rep: Reputation: 770Reputation: 770Reputation: 770Reputation: 770Reputation: 770Reputation: 770Reputation: 770
Can't boot current on rpi3 b+

Try powering down and inserting the SD card into a laptop or something. Then check the log files. With this sort of thing, it's usually a fairly simple fix after seeing the log files.
 
Old 12-11-2019, 05:08 PM   #4
Tonus
Member
 
Registered: Jan 2007
Location: Paris, France
Distribution: Slackware-current
Posts: 584

Original Poster
Blog Entries: 3

Rep: Reputation: 152Reputation: 152
Yes I will... If I do not find whats going on...

I will soon have another try. Hope some logs will be useful.

Thanks for the pointers
 
Old 12-11-2019, 11:00 PM   #5
mralk3
Senior Member
 
Registered: May 2015
Location: Utah, USA
Distribution: Slackware
Posts: 1,391

Rep: Reputation: 770Reputation: 770Reputation: 770Reputation: 770Reputation: 770Reputation: 770Reputation: 770
Can't boot current on rpi3 b+

Other option is to buy a serial line and watch it boot up from another device.
 
Old 12-12-2019, 04:40 PM   #6
Exaga
Member
 
Registered: Nov 2012
Posts: 214

Rep: Reputation: 96
Quote:
Originally Posted by Tonus View Post
Since I have no screen nor spare mouse and keyboard I don't have a clue about what's going on. I troubleshooted almost everything I thought of before trying 14.2 instead of current (ethernet cable, sdcard, gateway, power).

Any advice would be thankfully welcomed!
Add the following code to your /boot/cmdline.txt file and reboot - and specify the correct network interface - this will hopefully give you networking and allow you login remotely. In this example the network relies on DHCP to get an IP address and eth0 is the network interface:

Code:
kbd=us nic=auto:eth0:dhcp
Alternatively, if your network does not have DHCP enabled you should specify an IP address and netmask. In this example the IP address is 192.168.1.100 and the netmask is 255.255.255.0 (24-bit netmask):

Code:
kbd=us nic=auto:eth0:static:192.168.1.100:24
You can put the above code anywhere in your cmdline.txt file.
 
Old 12-13-2019, 03:42 PM   #7
Tonus
Member
 
Registered: Jan 2007
Location: Paris, France
Distribution: Slackware-current
Posts: 584

Original Poster
Blog Entries: 3

Rep: Reputation: 152Reputation: 152
Quote:
Originally Posted by Exaga View Post

Code:
kbd=us nic=auto:eth0:dhcp
Thanks for your input. I read carefully the man and that's what I usually do (and it worked same day on the new rpi4 with current). Unfortunately, it failed on the old rpi3 with current... But it is working with 14.2

That is really what puzzles me : why would it fail with current?

Since it is actually working with 14.2, I was wondering if I could check some hardware spec or sanity that would explain the fail.
 
Old 12-14-2019, 02:00 AM   #8
Exaga
Member
 
Registered: Nov 2012
Posts: 214

Rep: Reputation: 96
Quote:
Originally Posted by Tonus View Post
That is really what puzzles me : why would it fail with current?

Since it is actually working with 14.2, I was wondering if I could check some hardware spec or sanity that would explain the fail.
Hi. I'm really struggling to answer why Slackware ARM current would fail in this way when 14.2 is working fine. There must be another factor that's contributing to this problem. I build with and test the current version on the RPi 2/3/4 and failure in my experience is always attributed to some human element. I'm not even sure that Slackware [ARM] knows what failure is!

There have been times when Slackware ARM has had problems/issues running on the RPis due to poor quality power supplies, and also the SD card can be a huge factor in this. Some SD cards don't seem to work as well as others and changing them for a different one often makes all the difference. So, I'd try re-installing Slackware ARM current on a different SD card first of all.

Other than that, did you make absolutely sure that you installed correctly and missed nothing out? Did Slackware ARM current fail to boot into the installer? Or did Slackware ARM current fail to boot after installation?
 
Old 12-14-2019, 05:42 AM   #9
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 10,851

Rep: Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236
We can find out why it won't boot if the OP will turn up some logs, which are on the present sd card. Why not do that?
 
Old 12-14-2019, 12:42 PM   #10
Exaga
Member
 
Registered: Nov 2012
Posts: 214

Rep: Reputation: 96
Quote:
Originally Posted by business_kid View Post
We can find out why it won't boot if the OP will turn up some logs, which are on the present sd card. Why not do that?
Go for it. Let me know what the logs say.
 
Old 12-14-2019, 03:31 PM   #11
Tonus
Member
 
Registered: Jan 2007
Location: Paris, France
Distribution: Slackware-current
Posts: 584

Original Poster
Blog Entries: 3

Rep: Reputation: 152Reputation: 152
Can't boot current on rpi3 b+

Guys, thanks for your replies :

Human failure, that sounds... Likely?

It's the installer that couldn't be reached by ssh.

I have no more logs : there's 14.2 on the SD now, running fine.

I will try tonight another current install. The rpi4 can stand alone for that time and wait for his friend!

You'll soon see here success... Or logs 😆
 
Old 12-14-2019, 04:12 PM   #12
Tonus
Member
 
Registered: Jan 2007
Location: Paris, France
Distribution: Slackware-current
Posts: 584

Original Poster
Blog Entries: 3

Rep: Reputation: 152Reputation: 152
So I just pulled the sd card, put on it the installer, edited the cmdline.txt and put back the card in the pi3 : connection refused

I'm going to fetch the logs. Unfortunately, there seem to be no logs for the installer...

Edit : even tried to ssh from the pi4 for the same result

Last edited by Tonus; 12-14-2019 at 04:30 PM.
 
Old 12-14-2019, 04:59 PM   #13
Tonus
Member
 
Registered: Jan 2007
Location: Paris, France
Distribution: Slackware-current
Posts: 584

Original Poster
Blog Entries: 3

Rep: Reputation: 152Reputation: 152
After trying to plug the pi3 to some video projector while still plugged in short ethernet cable, just to try to see something on a small part of a wall... And realize that my hdmi cable does not fit well in the pi...

Tryed again and... I'm in ! Currently installing current.

I bet I never will understand.

Thanks all and sorry for the noise, this has (automagically?) solved itself.
 
Old 12-15-2019, 10:36 AM   #14
Exaga
Member
 
Registered: Nov 2012
Posts: 214

Rep: Reputation: 96
Quote:
Originally Posted by Tonus View Post
Human failure, that sounds... Likely?

It's the installer that couldn't be reached by ssh.
You can never discount the human element when dealing with a Raspberry Pi running Slackware (or anything else for that matter). In my experience it's culpable for most things that go awry in life!

You should be able to login normally via ssh even without any HDMI cable connected. No reason to plug one in if you're working headless. I only connect one up when I need to which isn't very often.

Quote:
Originally Posted by Tonus View Post
After trying to plug the pi3 to some video projector while still plugged in short ethernet cable, just to try to see something on a small part of a wall... And realize that my hdmi cable does not fit well in the pi...

Tryed again and... I'm in ! Currently installing current.

I bet I never will understand.

Thanks all and sorry for the noise, this has (automagically?) solved itself.
I've only had problems with RPi4 micro-HDMI cables and never with any RPi1/2/3 HDMI cables. Glad you fixed the issue. Now you know what to look for the next time this happens.
 
Old 12-15-2019, 07:02 PM   #15
Tonus
Member
 
Registered: Jan 2007
Location: Paris, France
Distribution: Slackware-current
Posts: 584

Original Poster
Blog Entries: 3

Rep: Reputation: 152Reputation: 152
Yes, humans... :-D

I tried the hdmi because I wanted to see if some output would help me to solve the problem. No output but no more problem :-)

Ssh works flawlessly. I'm just in trouble with ssh-add but I believe it could be related to an uncomplete install.

Might be related to other troubles trying to have clerk (tmux TUI for mpd with ncmpcpp) installed : having hard time since I haven't installed anything from e/x/xap/kde/kdei/xfce/y and avahi seems to need quite some stuff from X...

Still happy to learn !
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
14.2-current on RPi3, no sound on headphone jack or HDMI robmckennon68 Slackware - ARM 19 06-09-2018 01:12 PM
AArch64 kernel and modules to install Slackware ARM current on the RPi3 Exaga Slackware - ARM 27 02-07-2017 11:45 AM
Can''t connect to rpi3, slackware installation image by Fatdog Reedych Slackware - ARM 4 08-20-2016 01:26 PM
Glibc for rpi3 Tonus Slackware - ARM 2 04-20-2016 06:06 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM

All times are GMT -5. The time now is 02:27 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration