Upgrade problem

The SARPi project forum. For anything and everything relating to Slackware ARM on a Raspberry Pi 1, 2, and 3. This forum is NOT a replacement or substitute for the Slackware (ARM) forums on Linux Questions website! Please try to seek help there first about any issues you may be experiencing, or question you might have, before posting on here.
User avatar
linicks
Registered user
Registered user
Posts: 126
Joined: Mon Oct 27 2014 - 20:26:01
Location: Pompey, England

Upgrade problem

Postby linicks » Mon Oct 27 2014 - 20:55:34

Hi Guys,

Great guide - being a Slacker for 12 years, found it easy.

But I just hit a major show stopper - after getting my pi up and running and doing a slackpkg upgrade; slackpkg upgrade-all it trashed the builds from wrong Glibc and rendered the system useless:

Code: Select all

   Package glibc-solibs-2.15-arm-9_slack14.0.tgz is already in cache - not downloading
   Upgrading glibc-solibs-2.15-arm-9_slack14.0...

+==============================================================================
| Upgrading glibc-solibs-2.20-arm-1 package using ./glibc-solibs-2.15-arm-9_slack14.0.tgz
+==============================================================================

Pre-installing package glibc-solibs-2.15-arm-9_slack14.0...
cp: /lib/libc.so.6: version `GLIBC_2.17' not found (required by cp)
/sbin/ldconfig: Cannot lstat ld-2.15.so: No such file or directory
/proc/self/fd/0: line 56: /bin/basename: No such file or directory
/proc/self/fd/0: line 56: /bin/rm: No such file or directory
/proc/self/fd/0: line 57: /bin/basename: No such file or directory
/proc/self/fd/0: line 57: /bin/cp: No such file or directory
/proc/self/fd/0: line 58: /bin/basename: No such file or directory
/proc/self/fd/0: line 59: /bin/rm: No such file or directory
/proc/self/fd/0: line 56: /bin/basename: No such file or directory
/proc/self/fd/0: line 56: /bin/rm: No such file or directory
/proc/self/fd/0: line 57: /bin/basename: No such file or directory
/proc/self/fd/0: line 57: /bin/cp: No such file or directory
...


No big deal :) I will just start again, but this needs looking at what is going on.

Thanks,

Nick
https://linicks.net/

Q. What is the difference between a duck and an elephant?
A. You can't get down off an elephant.

User avatar
Exaga
FatDog Network Administrator
FatDog Network Administrator
Posts: 204
Joined: Wed Apr 18 2012 - 02:01:03
Location: England [UK]

Re: Upgrade problem

Postby Exaga » Mon Oct 27 2014 - 23:45:52

Hi linicks,

I'm glad you found our SARPi guide useful. ;)

I've just done a test with slackpkg (mirror=ftp://ftp.slackware.org.uk/slackwarearm/slackwarearm-14.1/) and in my case everything installed correctly, without any errors. I noticed it installed the correct glibc packages and didn't break anything afterwards.

Code: Select all

Package glibc-2.17-arm-15_slack14.1.txz is already in cache - not downloading
        Upgrading glibc-2.17-arm-15_slack14.1...

+==============================================================================
| Upgrading glibc-2.17-arm-14 package using ./glibc-2.17-arm-15_slack14.1.txz
+==============================================================================

Pre-installing package glibc-2.17-arm-15_slack14.1...
Verifying package glibc-2.17-arm-15_slack14.1.txz.
Installing package glibc-2.17-arm-15_slack14.1.txz:

Executing install script for glibc-2.17-arm-15_slack14.1.txz.
Package glibc-2.17-arm-15_slack14.1.txz installed.


I really cannot imagine what went wrong for you. I've never had issues like this before. Which version of slackpkg are you using and which mirror did you specify?
Exaga

====
__ KEEP THE DOG ALIVE!!!
()'`; /
/\|` W00f W00f W00f
www.fatdog.eu

User avatar
linicks
Registered user
Registered user
Posts: 126
Joined: Mon Oct 27 2014 - 20:26:01
Location: Pompey, England

Re: Upgrade problem

Postby linicks » Tue Oct 28 2014 - 00:00:44

I don't know what version, as I just followed the guide, so didn't see what version slackpkg upgrade pulled in.

I am currently installing again ... let me get the pi back up and let's see.

Nick
https://linicks.net/

Q. What is the difference between a duck and an elephant?
A. You can't get down off an elephant.

User avatar
linicks
Registered user
Registered user
Posts: 126
Joined: Mon Oct 27 2014 - 20:26:01
Location: Pompey, England

Re: Upgrade problem

Postby linicks » Tue Oct 28 2014 - 22:26:59

OK, quick update. For some reason, after three new installs over network using SSH, I could not connect to the pi.

After a lot of head scratching tonight, I sussed it.

On initial boot and installing Slack, interface was eth0. After all was done and reboot, interface changed to eth1 which wasn't configured. I could see the lan light was on the pi, so edited the sd card on my notebook to add ip settings to /etc/rc.d/rc.inet1.conf to all 3 eth interfaces.


Back on line :) For some reason pi uses eth1 but slack tools only config eth0.

I also found out that using any slack tools to config network, it only sets eth0, but pi wants to use eth1 for some reason... anyhow, all sorted now ~ I wonder if this is because I have left the USB stick in (i.e. that is now eth0, I dunno)?

Now, as to my first post re the glibc error - that was me. I installed slack-current, but used slack-14.1 to upgrade to :roll:

Anyhow, another error now on doing slackpkg update - all I get is md5sum checksum error from all -current mirrors, so am loath to go further at this stage. Are all the mirrors up-to-date?

Nick
https://linicks.net/

Q. What is the difference between a duck and an elephant?
A. You can't get down off an elephant.

User avatar
Exaga
FatDog Network Administrator
FatDog Network Administrator
Posts: 204
Joined: Wed Apr 18 2012 - 02:01:03
Location: England [UK]

Re: Upgrade problem

Postby Exaga » Wed Oct 29 2014 - 09:09:50

linicks wrote:Anyhow, another error now on doing slackpkg update - all I get is md5sum checksum error from all -current mirrors, so am loath to go further at this stage. Are all the mirrors up-to-date?

Nick


I have had this same issue with slackpkg. Download slackpkg-2.82.0-noarch-13.txz and...

# upgradepkg slackpkg-2.82.0-noarch-13.txz

Then set a mirror and you should be all good to go. Let me know if this doesn't work for you.
Exaga

====
__ KEEP THE DOG ALIVE!!!
()'`; /
/\|` W00f W00f W00f
www.fatdog.eu

User avatar
linicks
Registered user
Registered user
Posts: 126
Joined: Mon Oct 27 2014 - 20:26:01
Location: Pompey, England

Re: Upgrade problem

Postby linicks » Wed Oct 29 2014 - 18:44:03

OK, thanks.

I had to removepkg then installpkg as it said I was already using that version, but it wasn't...

Code: Select all

root@slackpi:~# upgradepkg slackpkg-2.82.0-noarch-13.txz

+==========================================================
| Skipping package slackpkg-2.82.0-noarch-13 (already installed)
+==========================================================


Anyhow, all works fine now.

Thanks for your help.

I am a bit busy at the moment, but I will post later on some things I found need improving/clarifying in the install guide.

Great job!

Nick
P.S. BTW, I am impressed with how fast Slackware is on the Pi compared with Raspbian or whatever it's called...
https://linicks.net/

Q. What is the difference between a duck and an elephant?
A. You can't get down off an elephant.

User avatar
Stackware
New member
New member
Posts: 1
Joined: Sat Nov 01 2014 - 17:18:33

Re: Upgrade problem

Postby Stackware » Sat Nov 01 2014 - 17:26:47

To fix the problem whit no eth0:

cd /etc/udev/rules.d
joe 70-presistent-net.rules
and change NAME="eth1" to NAME="eth0" at the end of the line
save and reboot.
Weiler's Law
Nothing is impossible to a person who dosen't have to do the work.

User avatar
linicks
Registered user
Registered user
Posts: 126
Joined: Mon Oct 27 2014 - 20:26:01
Location: Pompey, England

Re: Upgrade problem

Postby linicks » Mon Nov 03 2014 - 13:27:55

Stackware wrote:To fix the problem whit no eth0:

cd /etc/udev/rules.d
joe 70-presistent-net.rules
and change NAME="eth1" to NAME="eth0" at the end of the line
save and reboot.


Thanks, away at the moment and have checked the file, so will look at this when I get home - don't want to do it remotely as these sort of things can go tits-up :)

Nick

EDIT: OK, I done it remotely from a bar in Malta :) All worked great. Thanks. Any idea why the udev rules default to eth1 and not eth0, or is it a Raspberry Pi where eth0 is reserved for something under the 'official' OS?
https://linicks.net/

Q. What is the difference between a duck and an elephant?
A. You can't get down off an elephant.

Return to “SARPi Project - Slackware ARM on a Raspberry Pi”

Who is online

Users browsing this forum: CommonCrawl [Bot] and 6 guests