On Thursday 25 October 2007 22:54:11 Randall R Schulz wrote: > On Thursday 25 October 2007 14:33, Andrew Johnson wrote: > > On Thursday 25 October 2007 21:28:23 Randall R Schulz wrote: > > > It is, but see below. I recall one person recently mentioning here > > > (this list) successfully doing a 10.0 -> 10.3 upgrade. More below. > > > > I have just done a 10.1 to 10.3 upgrade with hardly any problems. > > Unless they were entirely idiosyncratic or perhaps just cockpit error, > it might be helpful to hear a bit about the problems you did encounter > and how you resolved them. On my Suse 10.1 installation I used ndiswrapper to run my wireless card which was a Belkin (Broadcom Air Force One) wireless card (which 10.2 and 10.3 both recognise) but then Yast tells me that I have to add some software to get it to work. Fine. Tried bcm43xx-fwcutter which fails because apparently it doesn't find a matching serial number in my bcmwl5.sys recovered from Belkin CD. I can't remember the exact train of events but somehow it finally dawned on me that before I could use ndiswrapper, I needed to remove the bcm43xx modulefrom the kernel. Once I had removed that with modprobe -r, the installation of ndiswrapper and setup of my wireless card went just as easily as setting it up in 10.1 (I have used 10.2 but I just didn't like it for some reason that now escapes me).
I also had a problem with one of the Java 1.5 files that Yast refused to upgrade because it insisted the file wasn't there. In the end after seeing advice elsewhere (I think on this list), I downloaded the installer from Sun Microsystems web site and loaded it in that way. Subsequently my Java is thoroughly well behaved. The original error here may have been cockpit error in what I told Yast to do to resolve dependencies so I can'y say whether this was a bug or not. -- Andrew Johnson -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
