Mailinglist Archive: opensuse-kde (218 mails)

[Carl <quantum@xxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well I've been compiling my red arse off, and think I have a workaround.
VMware is behind, and their new release doesn't fix this, as it purports.

But now when I boot I get the error message: 

<notice>/etc/init.d/rc5.d/S13alsasound start
Starting sound driver<notice>'/etc/init.d/rc5.d/S13alsasound start' exits with 
status 0
:  snd_cs46xxmodprobe: Can't locate module snd_cs46xx
failed

A check in modules.conf shows indeed that snd_cs46xx is being called, but the 
module is actually cs46xx.  So I presume there is some invisible massaging, 
that has now broken.  I did disable most sound modules, leaving only the 
generic ones, Soundblaster, Crystal, and OPL.

Anyone have a clue? 



On Monday, 30 September 2002 11:15, you wrote:
> Carl,
> None of the problems you describe look like SuSE; they seem to be VMware
> related. Shouldn't you try their tech support and lists?
>
> If your business is affected that seriously you should consider SuSE's
> "Paid Support" services.
>
> Best of Luck ............ PeterB
>
> On Monday 30 September 2002 09:20, Carl wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > This is a deal-killer for me.
> >
> > When I install and config VMware the whole system goes unstable,
> > particularly networking.  For some reason VMware insists on putting both
> > HostOnly and NAT on vmnet8, which thereafter hangs the network and
> > completely precludes a clean system shutdown.  vmware-config.pl cannot
> > shut down networking services once started and Aborts, so I get one shot
> > per hang/powerdown/boot.  As the system is unstable this way, there's no
> > tinkering with VMware.
> >
> > So I config VMware with NO networking and I can then config and reboot,
> > but when I power on the VM...  Segfault (no Oops).
> >
> > I have an IBM A22p notebook with 512MB of RAM, and
> > Suse8/K3.0.3/kernel2.4.18-154, with all updates.
> >
> > Google wisdom seems to be the problem is a patch in Suse's kernel which
> > enables 4GB of RAM.  Suse's workaround (
> > http://sdb.suse.de/en/sdb/html/fhassel_vmware_segfault.html ) is to add
> > to lilo.conf  append = "mem=512M" and lilo.  But it doesn't help for me.
> >
> > Googlers say to ditch the Suse kernel, or at least turn off upper memory
> > and recompile.  Well the kernel compile went fine, but  make modules
> > crashes with some arcane error that I just don't have time to decipher.
> >
> > VMware 3.2 says one of its new features is 'support for Suse8', which is
> > interesting.  But I've tried every vmware tar and rpm available
> > (including stock one from Suse8) and all have the same problems.
> >
> > So, will Suse assist here?
> > This is mission-critical for us.
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.0.6 (GNU/Linux)
> > Comment: For info see http://www.gnupg.org
> >
> > iEYEARECAAYFAj2YXaMACgkQnQ18+PFcZJueLQCfT7oPmzOYXV0JW4MafhWZbrQ4
> > QAEAn13OdyOK5WSQBY+CqNBCf6u+N9Yk
> > =0QQC
> > -----END PGP SIGNATURE-----

- -- 
Remember, drive defensively!  And of course, the best defense is a good
offense!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAj2YnbUACgkQnQ18+PFcZJtu6wCdEobTkK3jYIEBVsV1HejFeLnr
ZnoAn3io3LyPDAJ/zOKNAFERgQ+o6p/x
=3HoL
-----END PGP SIGNATURE-----