Failing to install Slackware 12.0 from memory stick.

Didier Spaier · 02-04-2017, 10:50 PM

Quote:

Originally Posted by stf92

The FAQ.TXT method assumes you are able to run setup. Now, do type 'setup' on a root console and tell me what happens, if you please. Without irony, I can't understand how I am supposed to run the installer.

I have usbboot.img from slackware 14.1 (12.0 has no directory usb-and-pxe-installers/). So

Code:

1.  dd usbboot.img into the stick and boot from the stick.
2.  When asked for the sources mount the ISO on /foo (RAM)  and give the installer its path.

is the procedure I have just followed. But it's in vain. The installer without complain begins installing (it seems so) but the result is an empty directory on the root partition.

[I already told you that dd usbboot.img will not work. If you are not able or do not want to use Rufus to make a bootable USB stick of slackware-12.0-install-d1.iso then sorry, you won't succeed.

If you succeed in making a bootvble USB stick from slackware-12.0-install-d1.iso, then start the installer, log in as root, issue the command

Code:

blkid

and post the results here so that we can give you further detailed instructions.

colorpurple21859 · 02-04-2017, 11:09 PM

you will have to create two new directories to mount the iso, You can't use /mnt or it's subdirectories because /mnt is where the target partition is mounted during setup. one for the drive that the iso is located on and one for the iso.

Didier Spaier · 02-04-2017, 11:25 PM

Quote:

Originally Posted by colorpurple21859

you will have to create two new directories to mount the iso, You can't use /mnt or it's subdirectories because /mnt is where the target partition is mounted during setup. one for the drive that the iso is located on and one for the iso.

Hopefully will see the USB stick with the content of the ISO will be seen as a block device. Then something what like I wrote in posts #13 or #14 will work.

colorpurple21859 · 02-04-2017, 11:37 PM

if the op wrote the 12.0 iso to usb using rufus, at the source selection select the hard drive partition option, select /dev/(the usb nomenclature) and /slackware for the directory.

stf92 · 02-05-2017, 08:23 AM

I was wrong. Slackware 12.0 does have a usbboot.img and it DOES work. I used it and had no problem. But that's not the whole story. Before I discovered the usbboot.img file is in disk 2 of the distro, I proceeded to install manually. Just used installpkg with option --root. But found one surprising thing. I could not start the desktop manager. I first ran pkgtool and told it to use KDE. But KDE output the following notification: Could not start kstartupconfig. Then I tried with Xfce, and got

Code:

Agent pid 2922
which: no dbus-launch in (/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/share/texmf/bin:.)
/usr/bin/xfce4-session: error while loading shared libraries: libstartup-notification-1.so.0: cannot open shared object file: No such file or directory
Agent pid 2922 killed

It seems I won't be able to run Slackware 12.0 after all. However the machine, an HP Mini 210-1100, is from year 2000, and 12.0 is newer than that.

Didier Spaier · 02-05-2017, 08:40 AM

This just shows that you didn't install the package startup-notification-0.8-i486-2.tgz from the l/ series of packages, or failed to install it properly. The machine is certainly able to run Slackware 12.0, if you install it properly.

This kind of issue sometimes happens when people do not do a full installation. Did you do a full installation?

stf92 · 02-05-2017, 08:49 AM

Well, I thought the l series was the internationalization series (multiple languages) and did not install it.

Didier Spaier · 02-05-2017, 09:00 AM

Quote:

Originally Posted by stf92

Well, I thought the l series was the internationalization series (multiple languages) and did not install it.

So after ten years using Slackware you don't know that l is for libraries?

Anyway I won't answer any more question in this thread until you make a full install, which has always been recommended for newbies. Going out for a walk, see you later maybe.

PS You are also missing l/dbus, so your system lacks a way for processes to communicate with each other. As a consequence even if you were able to start Xfce most of its features wouldn't work.

Alien Bob · 02-05-2017, 09:42 AM

[QUOTE=Didier Spaier;5665475]So after ten years using Slackware you don't know that l is for libraries?[/QOUTE]
I often think this person is a troll, trying to get people to look into ridiculous issues. I have given that exact same reply in several other threads created by this person. You can not be using Linux, and Slackware, for 10 years, and pretend you are not aware of the basest of basics.

Quote:

Anyway I won't answer any more question in this thread until you make a full install, which has always been recommended for newbies. Going out for a walk, see you later maybe.

I applaud you for the effort, albeit a wasted effort probably.

stf92 · 02-05-2017, 05:00 PM

Well, I installed the l series, only one missing, so I've got a full installation now. I debuted running KDE (I liked Xfce because the instructions to set the mail going were much clearer). Now I face the problem of making the system to connect to the Internet, a thing I haven't been able to do yet. I did run pkgtools and went trough netconfig, but the classical window saying it cannot connect to the web location is issued.

Didier Spaier · 02-05-2017, 05:14 PM

Just to be sure...

Has this computer a network card?
How is this network card connected to the internet (modem, NAT router, ADSL device, whatever?)
Did you choose DHCP to set up IP address in netconfig?

Please provide output of these commands, typed as root:

Code:

ifconfig -a
route

stf92 · 02-05-2017, 05:48 PM

I did a thing I did once and gave me a good headache. I ran again pkgtool>netconfig just to be sure, and then I changed the hostname I had initially given, hostname_1 to darkstar. So starting Xfce, Xfce immediately told me he could not I don't know what hostname_1. So I ran netconfig again and change darkstar to hostaname_1. But then Xfce said he couldn't ... connect perhaps is the word... darkstar.

I went to /etc and did 'grep -irl darkstar *' and it was in a good many files, included files related to ssh. So, despite the changes made through netconfig, there's still this name mismatching in the system.

Didier Spaier · 02-05-2017, 05:53 PM

The machine's naming has most probably nothing to do with your issue.

I you want help please answer all the questions I asked in my previous post.

stf92 · 02-05-2017, 06:04 PM

Code:

root@darkstar:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr C8:0A:A9:C4:09:39
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:4294967287 overruns:0 frame:0
          TX packets:0 errors:0 dropped:8 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:16 Base address:0x4000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

root@darkstar:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
loopback        *               255.0.0.0       U     0      0        0 lo
root@darkstar:~#

1. Has this computer a network card? Yes, it has.
2. How is this network card connected to the internet (modem, NAT router, ADSL device, whatever?): Wi-Fi
3. Did you choose DHCP to set up IP address in netconfig? Yes, I did.

Didier Spaier · 02-05-2017, 06:16 PM

Type this as root

Code:

ifconfig eth0 up
dhclient eth0

If you are granted a lease you are all set. Check typing "route" again.