After I updated my Suse 9.2 installation using YOU (now it's 9.3 and there were a lot of other updates), my YaST doesn't work properly. I can open YaST, but I can't open any modules... Anyone else has the same problem?

Hi,

maybe you should try YAST as root or minimize YAST window and then maximize it . It worked for me.

I already rebooted several times and it didn't work. Furthermore, YaST asks for Root password when I run it.
Okay, maybe I wasn't clear enough when I opened this topic:

YaST DOES open up, but when I click on a module, my cursor changes to the loading cursor, and after a few seconds my loading cursor disappears and then nothing happens...

Try running "rpm --rebuilddb" in a shell as root, that fixed yast for me, before it opend up in the main menu but modules died.
I updated opensuse 10 beta2 to 10 beta3 when this happened.

That one didn't work either

Hi! I have to say that I had the same problems, when I tried updating 9.2 to 9.3. The only solution I found was to install Suse again from scratch with a 9.3 Installation dvd...

Well, good luck, and I'd sure be interested if you find another way out

Laura

I'm not going to look for another way to solve it... I only have two questions before I'm starting this one of... I don't want to open another thread for these questions, so here they are:

1. I used a mini-installation disc for Suse 9.2 (all the setup files and stuff are downloaded from the internet when installing ). Is it possible that I use this disc, but instead of 9.2 it install 9.3? and what about the Network Installation disc? Can you also use it to install Linux with files from ftp servers, or do you HAVE to have a network source?

2. I had to go through a lot of trouble to get this multi-boot system working. Is it possible that Suse doesn't change anything to my current GRUB boot settings? I have all the files GRUB needs (like menu.lst) on another FAT32 partition (it is my shared partition, so that win xp and linux can both work with it), but I don't want YaST to overwrite the MBR when installing.

No, you should use the boot.iso made for 9.3. Otherwise you will load an older kernel, which gives you the same trouble as updating from 9.2. You can find the 9.3 boot.iso in the folder 9.3/boot on any SUSE mirror. The FTP server is nothing different from any other network source, so you can use it.

During installation you can tell YaST not to write grub into the MBR. As a backup-plan you can write grub to a floppy, so if your current settings do not work you can enter your system from the floppy.

A friend of mine actually just managed to install SuSE 9.3, using the mini-install cd. And after that, just scour the ftp-sites with YaST for additional packages....

BTW, Liquid_T<NL>, are you Dutch?

Good luck,

Laura

Have you tried starting yast from a shell as root, it should give you some error messages
allso if you tipe "yast" not "yast2" it starts in text mode (ncurses) and might work that way and then i would reinstall all yast packages.

Well, I want to thank all of you for your help, I think I'm going to re-install Suse, but now 9.3 so I don't have any problems... I'm not very familiar with Linux so I don't want to get of on the wrong foot

Well I already got a back up of grub on a floppy so I don't think that would be any problem... But it's just the hassle of re-installing Grub again, because it has been a while since I worked with it for the last time...

abisko00, thank you for your quick response, I'm going to try it out this evening, so maybe if this thread isn't locked by that time, I'll try to post in this thread if everything has worked. Of course I'm going to do this in my new Suse 9.3 workstation :P

@alisic: Yeah I'm dutch, at least someone noticed the NL tag are you english too?

Yeah I'm Dutch too - geophysics student in Utrecht.

I do not completely understand your problem with GRUB, because when you insert the install cd or dvd, you are offered some choices where linux should install (i.e., on which partition it should be installed), and whether it should replace an old linux installation or not. Furthermore, you can give your preference in boot loader, GRUB or LILO, which the install cd/dvd will also install and configure for you. I think in this case, not necessarily things have to be changed in your MBR.

However, probably it is very wise to have the backup disk anyway

Please let me know how you succeed!


Laura

I know I know, I just asked to be sure And my GRUB did configure itself when I installed my current Linux distribution, but because it didn't hide/unhide any partitions, my XP partition got a little messed up :P And I don't want any weird partitions in my XP, only the XP partition and the shared data partition.
Anyway, thanks for the info, maybe I'm getting a spare system so I can experiment a little more

I just got home from my girlfriend, so I don't think I will try re-installing this evening... tomorrow is a new day with plenty of possibilities... I will let you know

Well, I re-installed Suse 9.3 with succes and currently I'm working with it
Installation was very easy, and I decided to do the installation overnight, because I knew I had to download about 2 GB of installation data Everything went ok, except one little thing, and that was my bootloader setup There wasn't a possibly to just let the bootloader as it is, so I had to install the bootloader, and then rewrite the menu.lst, so all the hiding/unhiding was perfect.
Still having 2 little problems though. I don't know if I should post it here, or if I should open a new thread. For now I'm going to post it here

1. My shared data partition (hda4) isn't mounted when I boot into Suse. I want this to happen automatically. I already tried using the partitioning program in YaST, and then it actually mount hda4 on /shared But when I reboot, I have to remount it again. Another partition of me (hda1) is perfectly mounted on /win98 and stays mounted. How do I fix this? The only big difference is that the extra options for fstab of the win98 partition are
and on the shared data partition there is nothing, but I don't see any relation between this mount options and the fact that the shared data partition doesn't mount by default.

2. My AmaroK refuses to play any file... Nothing happens, no error, nothing...

You can add the option 'auto' to the hda4 line in /etc/fstab. Then the drive will be mounted on boot.