upgrading 11.0 to 13.0

hirohitosan · 12-26-2009, 09:32 AM

Hi there. I installed Slack 11 on my old laptop Toshiba 510CDT. I chose 11. 0 for there are floppies for install (my laptop cannot boot from CD).
I'm for the first time in Slack world so I have some questions:
1. my PCMCIA card doesn't start. I installed PCMCIA support but still no network (my only network is an PCMCIA D-Link DFE-650TXD). Do I have to start it manually?
How do I know that the kernel has recognize it?
2. It is possible to upgrade the system to 13.0 without reinstall everything? I cannot boot my system just from floppy or HDD.

thanks for now

GrapefruiTgirl · 12-26-2009, 09:51 AM

First thing I would suggest regarding the PCMCIA card, would be to see that the file /etc/rc.d/rc.pcmcia is executable, and if it is so, then execute it like this:

shell# /etc/rc.d/rc.pcmcia start

and with any luck, that will start the card. You will likely then need to configure the networking aspect of it, in /etc/rc.d/rc.inet1.conf which is the network configuration file. After configuring that, restart the network using:

shell# /etc/rc.d/rc.inet1 restart

If this process doesn't work, or something seems to go wrong during this process, please post for us the output from the following commands (AFTER doing the rc.pcmcia step above):

shell# lspci -vv
shell# ifconfig -a

..and we will try to figure out where to go next. It appears from some googling though, that the PCMCIA socket and than card should be fairly easy to get working, and they are supported for quite some time now.

PS - If the rc.pcmcia script is set executable, it will run at boot all by itself, and you won't need to manually restart it.

Sasha

gnashley · 12-26-2009, 12:10 PM

You may neeed to load the kernel module for the pcmcia driver. As far as upgrading, the only proper way to do it would be to upgrade through each inetrvening version -11.0 to 12.0, 12.0 to 12.1, 12.1 to 12.2, 12.2 to 13.0 -unless you study really, really hard the UPGRADE.TXT notes for each version and figure out how to get directly from 11.0 to 13.0. Actually, I guess you could do that, but you'd need to feel very secure about fixing any glitches which come up.

Ivshti · 12-26-2009, 01:04 PM

Just install all the packages from Slackware 13.0 with the command "upgradepkg --install-new ".
For example, you mount the slackware dvd, then change directory into the directory with packages, and do:
upgradepkg --install-new a/*.t?z ap/*.t?z l/*.t?z n/*.t?z ...etc (all the categories you want).

Then you should correct your files in /etc. It's well described in UPGRADE.TXT. Be ready to sacrifice most of the custom files in /etc. If you run the script in UPGRADE.TXT, your old config files will stay with a ".bkp" (or something like this) suffix, so don't be worried. Another thing: be ready to delete most of the configurations in your home directory. For example, if you use KDE, you'll have to delete (or move) the ".kde" folder.

Good luck!

hirohitosan · 12-26-2009, 02:09 PM

thanx!

Quote:

Originally Posted by GrapefruiTgirl

shell# /etc/rc.d/rc.pcmcia start
After configuring that, restart the network using:
shell# /etc/rc.d/rc.inet1 restart

I did

Code:

# /etc/rc.d/rc.pcmcia restart
Shutting down PCMCIA services: cardmgr modules.
Starting PCMCIA services:
  <Probing for PCIC: edit /etc/rc.d/rc.pcmcia>

but I don't have rc.inet1 in /etc/rc.d/ did I miss something at installation time?

GrapefruiTgirl · 12-26-2009, 02:17 PM

Humm.. Even if you *had* missed something, I would think that rc.inet1 would definitely be there

If you don't have it around, it will definitely be somewhere on your install CD. You'll need the rc.inet1.conf file that goes with it too. Not sure if you need anything else to go with those.

Since you're here, may as well post the output of `lspci -vv` for the time being, while you locate an rc.inet1.

Sasha

hirohitosan · 12-26-2009, 02:25 PM

Quote:

Originally Posted by GrapefruiTgirl

Since you're here, may as well post the output of `lspci -vv` for the time being, while you locate an rc.inet1.

here is:

Code:

00:00.0 Host bridge: Toshiba America Info Systems CPU to PCI bridge (rev 11)
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
	Latency: 0, Cache Line Size: 32 bytes

00:02.0 CardBus bridge: Toshiba America Info Systems ToPIC95 (rev 07)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at 10000000 (32-bit, non-prefetchable) [size=4K]
	Bus: primary=00, secondary=14, subordinate=14, sec-latency=0
	Memory window 0: 10400000-107ff000 (prefetchable)
	Memory window 1: 10800000-10bff000
	I/O window 0: 00004000-000040ff
	I/O window 1: 00004400-000044ff
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt+ PostWrite+

00:02.1 CardBus bridge: Toshiba America Info Systems ToPIC95 (rev 07)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin B routed to IRQ 11
	Region 0: Memory at 10001000 (32-bit, non-prefetchable) [size=4K]
	Bus: primary=00, secondary=15, subordinate=15, sec-latency=0
	Memory window 0: 10c00000-10fff000 (prefetchable)
	Memory window 1: 11000000-113ff000
	I/O window 0: 00004800-000048ff
	I/O window 1: 00004c00-00004cff
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt+ PostWrite+

00:04.0 VGA compatible controller: Chips and Technologies F65550 (rev 45) (prog-if 00 [VGA])
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Region 0: Memory at fe000000 (32-bit, non-prefetchable) [size=16M]
	Expansion ROM at <unassigned> [disabled] [size=256K]

and # ifconfig -a gives me:
ifconfig cannot find or something like that. Sorry I cannot paste the exact output for every time I have to reboot in win for reply. BTW in win98 my PCMCIA card is working and also I installed SLAX and it works as well.

GrapefruiTgirl · 12-26-2009, 02:29 PM

OK, I don't see any network device in your lspci list, and also, if `ifconfig` gives a "command not found" type of error, I suspect you somehow did manage to NOT install some important networking stuff.

I suggest at this point, your easiest place to start would be to boot the install CD again, and go through the installer and make sure you install all the networking stuff (TCP-IP Networking Utilities, or whatever it's called in there). Make sure you do not re-format anything!! You don't need to do a fresh full install; only tell the installer what is your root partition, maybe your swap partition too, and then proceed to the "install packages" section, where you can select all the networking packages and install them. Also, you do not need to re-install LILO or anything like that, ONLY your networking stuff.

When that's all done, exit the installer and reboot your distro, and we shall start again near the top of this thread

Sasha

hirohitosan · 12-26-2009, 04:29 PM

Thanks Sasha

After a little work I have now:

Code:

# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:50:BA:81:6B:40  
          BROADCAST MULTICAST  MTU:1500  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:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:3 Base address:0x300 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          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)

I conect through DHCP so there is a program to scan for DHCP servers or something loke that?

and

Code:

# lspci -vv
00:00.0 Host bridge: Toshiba America Info Systems CPU to PCI bridge (rev 11)
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
	Latency: 0, Cache Line Size: 32 bytes

00:04.0 VGA compatible controller: Chips and Technologies F65550 (rev 45) (prog-if 00 [VGA])
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Region 0: Memory at fe000000 (32-bit, non-prefetchable) [size=16M]
	Expansion ROM at <unassigned> [disabled] [size=256K]

and here's what I have in /etc/rc.d

Code:

# ls -al
total 184
drwxr-xr-x  2 root root  4096 Dec 22 00:03 ./
drwxr-xr-x 34 root root  4096 Dec 22 00:10 ../
lrwxrwxrwx  1 root root     4 Dec 22  2009 rc.0 -> rc.6*
-rwxr-xr-x  1 root root  1160 Sep 25  2006 rc.4*
-rwxr-xr-x  1 root root  6782 Sep 25  2006 rc.6*
-rwxr-xr-x  1 root root  2322 Sep 25  2006 rc.K*
-rwxr-xr-x  1 root root 10022 Sep 25  2006 rc.M*
-rwxr-xr-x  1 root root 14408 Sep 25  2006 rc.S*
-rwxr-xr-x  1 root root   466 Nov  5  2004 rc.acpid*
-rwxr-xr-x  1 root root  1614 Aug  5  2006 rc.alsa*
-rwxr-xr-x  1 root root  1148 Dec 22  2009 rc.gpm*
-rwxr-xr-x  1 root root  2243 Sep 21  2006 rc.hotplug*
-rwxr-xr-x  1 root root  8325 Sep 21  2006 rc.inet1*
-rw-r--r--  1 root root  3759 Sep 21  2006 rc.inet1.conf
-rwxr-xr-x  1 root root  4477 Sep 21  2006 rc.inet2*
-rwxr-xr-x  1 root root   497 Sep 12  2003 rc.inetd*
-rw-r--r--  1 root root  1924 Sep 14  2003 rc.ip_forward
-rwxr-xr-x  1 root root   272 Sep 25  2006 rc.local*
lrwxrwxrwx  1 root root    19 Dec 22  2009 rc.modules -> rc.modules-2.4.33.3*
-rwxr-xr-x  1 root root 25553 Sep  1  2006 rc.modules-2.4.33.3*
-rwxr-xr-x  1 root root  2444 Sep 21  2006 rc.nfsd*
-rwxr-xr-x  1 root root  5090 Aug 16  2006 rc.pcmcia*
-rw-r--r--  1 root root  2000 Sep 22  2006 rc.rpc
-rwxr-xr-x  1 root root   967 Sep 25  2006 rc.scanluns*
-rwxr-xr-x  1 root root   687 Jun  5  2002 rc.sendmail*
-rw-r--r--  1 root root  2895 Sep 25  2006 rc.serial
-rwxr-xr-x  1 root root  1222 Sep 29  2006 rc.sshd*
-rwxr-xr-x  1 root root   860 May  3  2004 rc.syslog*
-rwxr-xr-x  1 root root  1740 Sep 25  2006 rc.sysvinit*
-rwxr-xr-x  1 root root  4711 Sep 14  2006 rc.udev*
-rwxr-xr-x  1 root root  2323 Aug  1  2005 rc.yp*

GrapefruiTgirl · 12-26-2009, 04:34 PM

Cool! Good work, that looks much better! Looks like you basically need to get an IP address and bring up that network card

Yes, DHCP is no problem. As a test, you could try:

shell# dhcpcd eth0

and see if you get an IP address, but this is really cutting corners

You should do it the right way: configure rc.inet1.conf to use DHCP, save the file, and then restart your network with:

/etc/rc.d/rc.inet1 restart

and see how that works.

DHCP should configure your nameservers in /etc/resolv.conf automatically, but in case it does not do this initially (we'll fix that later) then you will want to know the IP addresses of your ISP's nameservers and put them into /etc/resolv.conf. That will allow for DNS lookups to work.

I must go for supper now, but I will check back after supper to see where you're at!

Best of success,
Sasha

hirohitosan · 12-27-2009, 06:32 AM

Quote:

Originally Posted by GrapefruiTgirl

shell# dhcpcd eth0

thanks it works. I have now IP and everything and I can connect to IN.

Quote:

Originally Posted by GrapefruiTgirl

configure rc.inet1.conf to use DHCP

How? I edit rc.inet1.conf and as you know thare are some fields:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""

and in /etc/resolv.conf I have:
nameserver 111.222.333.444
nameserver 55.66.777.88

so what I have to do is to put the nameserver in the rc.inet1.conf?

and how to set to use DHCP everytime when I start up my comp.

GrapefruiTgirl · 12-27-2009, 10:58 AM

In rc.inet1.conf, you want to configure only two items for your setup (assuming you have just one interface, eth0), so like this:

IFNAME[0]="eth0"
USE_DHCP[0]="yes"

And that's it

It appears that your DHCP is automatically putting the nameservers into resolv.conf so you do not need to worry about that -- it's done

Sasha

hirohitosan · 12-27-2009, 02:38 PM

Thanks Sasha

It works fine now.

Now, comming back to the begining of my post. Can I upgrade to Slack 13?

My ideea was to upgrade to 2.6 kernel (now I have 2.4.33.3) and then install X with fluxbox and Opera.

GrapefruiTgirl · 12-27-2009, 05:57 PM

Yes, you can upgrade to 13.0. As per Gnashleys post above (post # 3) you can do it one of at least two ways: either go from one release to the next, in order, following the instructions in UPGRADE.TXT with each release; or, just go ahead and change your slackpkg mirror to a 13.0 mirror and go crazy

but you are bound to run into a numberof things that will need your attention, if you want stuff to not go all berzerk on you.

I myself did not upgrade; I had been using Slack 11 for a couple years, and then I installed -current-13 fresh, and when 13.0 went stable and was officially released, I just synced my install with the 13.0 stable mirror and was all done.

I can't really advise you what to do, but I can tell you this: there are lots of LQ threads on the exact subject of upgrading to 13.0, so I recommend you search around in the Slackware forum some more, because all (or most of) your questions and/or problems you encounter, have already been encountered by someone else, and solutions will have been posted.

Good luck! And, if you upgrade and run into trouble and cannot find a thread about the problem, by all means, create a new thread describing what you've done and what's going wrong, and we'll do our best to help you out.

Sasha

hirohitosan · 12-28-2009, 04:30 AM

Reading UPGRADE.TXT for 13 I understood that I don't need network for upgrading. It was my misunderstanding. I believed that for upgrading I need to connect to Internet somehow. I'll try to upgrade ... see what happens