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

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.

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.

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

Other option is to buy a serial line and watch it boot up from another device.

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:

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):

You can put the above code anywhere in your cmdline.txt file.

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.

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?

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.

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 😆

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

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.

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.

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.

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 !