Don't take the following too serious because I am losing my mind. Ok so I use SuSe since 5.3. Great product and it has come along nicely. Once in a while you cross a problem though where you think: what a fucking shit. yast2 is such problem. I read others here complain about yast2. I mean who to fuck needs this graphics crap? all I want is a working utility which assists in setup. yast1 used to be this tool and keeps being handy for my work. yast2 never really crosses my mind. previous to suse 6.4 getting sound was a bit difficult. You had to usually compile it yourself. I remember spending months in 5.3 to get my sound to work. Once I finally did it worked perfectly. until 6.4 rolled around and with it yast2 and the fact that SuSe started trying to include sound setup with its distro. From there on sound setup may have become easy for people who like yast2 and think it does a good job. For me yast2 makes sound almost impossible to enjoy. I got opl3sa2 card. The problem is that if I use the alsa.rpm and alsadev.rpm and use yast2 to set sound up it gives me sound but loops forever. it's not sound its noise. So there I tell myself that I just don't use yast2 and compile my sound like in the past myself. The problem is ever since suse created this automatic sound setup its impossible to compile alsa yourself. I constantly get this stupid error: amixer: Mixer 0/0 open error: Invalid argument So now I spend 3 hours on trying to get my sound back. I had it achieved once under 6.4 and 7.0 but it took me hours and now where I put new HD in my box I came to the same problem again. The sound is harder to configure than it was before suse tried to do it for me. The problem now isn;t even that I don't have sound. The mixer 0/0 problem will not even vanish if I uninstall and reinstall packages freshly. what a junk. I wish we all go back to good old text file setup and none of this yast2 junk. sorry for the rant. mk PS: I noticed there was now a conf.modules and modules.conf file in the distro. Maybe I slept but since when did this happen? It's not even symlinked. They are separate files. is SuSE so special that it needs it both ways? _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com
I had the same problem getting my sound chip (same as yours) working, and like you I could only use YaST2 to try Alsa, which didn't work for me either. So, since my OSS license was still good I got an upgrade and installed it. Sound is great now. I agree with you. SuSE, are you listening? Don't leave YaST1 behind and put all your updates into YaST2. In my opinion, YaST1 is more powerful and flexible. jlk On Saturday 06 January 2001 18:27, Purple Shirt wrote:
Don't take the following too serious because I am losing my mind.
Ok so I use SuSe since 5.3. Great product and it has come along nicely. Once in a while you cross a problem though where you think: what a fucking shit.
yast2 is such problem. I read others here complain about yast2. I mean who to fuck needs this graphics crap? all I want is a working utility which assists in setup. yast1 used to be this tool and keeps being handy for my work. yast2 never really crosses my mind.
previous to suse 6.4 getting sound was a bit difficult. You had to usually compile it yourself. I remember spending months in 5.3 to get my sound to work. Once I finally did it worked perfectly.
until 6.4 rolled around and with it yast2 and the fact that SuSe started trying to include sound setup with its distro. From there on sound setup may have become easy for people who like yast2 and think it does a good job. For me yast2 makes sound almost impossible to enjoy. I got opl3sa2 card.
The problem is that if I use the alsa.rpm and alsadev.rpm and use yast2 to set sound up it gives me sound but loops forever. it's not sound its noise. So there I tell myself that I just don't use yast2 and compile my sound like in the past myself.
The problem is ever since suse created this automatic sound setup its impossible to compile alsa yourself. I constantly get this stupid error:
amixer: Mixer 0/0 open error: Invalid argument
So now I spend 3 hours on trying to get my sound back. I had it achieved once under 6.4 and 7.0 but it took me hours and now where I put new HD in my box I came to the same problem again. The sound is harder to configure than it was before suse tried to do it for me.
The problem now isn;t even that I don't have sound. The mixer 0/0 problem will not even vanish if I uninstall and reinstall packages freshly. what a junk.
I wish we all go back to good old text file setup and none of this yast2 junk.
sorry for the rant.
mk
PS: I noticed there was now a conf.modules and modules.conf file in the distro. Maybe I slept but since when did this happen? It's not even symlinked. They are separate files. is SuSE so special that it needs it both ways?
_________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com
-- Scientific theories, according to Sir Karl Popper, can be "falsified," or proven wrong, by experiment. Unscientific theories -Marxist dialectical history and Freudian psychology were Popper's favorites- are formed in such a way that they cannot be falsified by data.
On Sat, Jan 06, 2001 at 09:05:22PM -0600, Jerry Kreps wrote:
I had the same problem getting my sound chip (same as yours) working, and like you I could only use YaST2 to try Alsa, which didn't work for me either. So, since my OSS license was still good I got an upgrade and installed it. Sound is great now.
I agree with you. SuSE, are you listening? Don't leave YaST1 behind and put all your updates into YaST2. In my opinion, YaST1 is more powerful and flexible. jlk
No they are not listening. Yast1 works but doesn't look very pretty Yast2 looks pretty but it's beauty is skin deep, underneath it is dumb..and slow. Which one pleases the marketing men at computer shows with hot-shit 1Ghz processors with 256MB memory ..etc.. ? I have complained about yast2 here, and email'ed them outside the list. They say bugger-all. Cliff
On Saturday 06 January 2001 18:27, Purple Shirt wrote:
Don't take the following too serious because I am losing my mind.
Ok so I use SuSe since 5.3. Great product and it has come along nicely. Once in a while you cross a problem though where you think: what a fucking shit.
yast2 is such problem. I read others here complain about yast2. I mean who to fuck needs this graphics crap? all I want is a working utility which assists in setup. yast1 used to be this tool and keeps being handy for my work. yast2 never really crosses my mind.
previous to suse 6.4 getting sound was a bit difficult. You had to usually compile it yourself. I remember spending months in 5.3 to get my sound to work. Once I finally did it worked perfectly.
until 6.4 rolled around and with it yast2 and the fact that SuSe started trying to include sound setup with its distro. From there on sound setup may have become easy for people who like yast2 and think it does a good job. For me yast2 makes sound almost impossible to enjoy. I got opl3sa2 card.
The problem is that if I use the alsa.rpm and alsadev.rpm and use yast2 to set sound up it gives me sound but loops forever. it's not sound its noise. So there I tell myself that I just don't use yast2 and compile my sound like in the past myself.
The problem is ever since suse created this automatic sound setup its impossible to compile alsa yourself. I constantly get this stupid error:
amixer: Mixer 0/0 open error: Invalid argument
So now I spend 3 hours on trying to get my sound back. I had it achieved once under 6.4 and 7.0 but it took me hours and now where I put new HD in my box I came to the same problem again. The sound is harder to configure than it was before suse tried to do it for me.
The problem now isn;t even that I don't have sound. The mixer 0/0 problem will not even vanish if I uninstall and reinstall packages freshly. what a junk.
I wish we all go back to good old text file setup and none of this yast2 junk.
sorry for the rant.
mk
PS: I noticed there was now a conf.modules and modules.conf file in the distro. Maybe I slept but since when did this happen? It's not even symlinked. They are separate files. is SuSE so special that it needs it both ways?
_________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com
-- Scientific theories, according to Sir Karl Popper, can be "falsified," or proven wrong, by experiment. Unscientific theories -Marxist dialectical history and Freudian psychology were Popper's favorites- are formed in such a way that they cannot be falsified by data.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
and now for my two (useless) cents: i have yet to do an install, where yast2 would even work after the linuxrc step finished.... on a couple of machines it worked after the install was completed....in it's defense, it did configure the sound for me (SuSE7.0, before that had to do it manually)-but- i have a very common sound card (sb16)... then there's sax and now sax2- both need serious revamping or trash them............ i have a 17" hp monitor (no, of course the model isn't listed in sax), and it supposed to be able to run at a maximum 1280x1024 at 60hz, according to the mfg. i was able to run it on SuSE 6.4 using both xf86 v.3.3.6 and 4.0 at 1248x960 (this was manually set-up) best i can do using sax 2, is some weird 1152x870.......... it has always baffled me why after so many years of great forward leaps, we still can't get xwindows to run painlessly.......... yast1 has been a good utility and i continue to learn more of its features one complaint about 7.0, the upgrade seems to have removed my /usr/docs/howto/mini/en directory and files..?? Cliff Sarginson wrote:
On Sat, Jan 06, 2001 at 09:05:22PM -0600, Jerry Kreps wrote:
I had the same problem getting my sound chip (same as yours) working, and like you I could only use YaST2 to try Alsa, which didn't work for me either. So, since my OSS license was still good I got an upgrade and installed it. Sound is great now.
I agree with you. SuSE, are you listening? Don't leave YaST1 behind and put all your updates into YaST2. In my opinion, YaST1 is more powerful and flexible. jlk
No they are not listening. Yast1 works but doesn't look very pretty Yast2 looks pretty but it's beauty is skin deep, underneath it is dumb..and slow.
Which one pleases the marketing men at computer shows with hot-shit 1Ghz processors with 256MB memory ..etc.. ?
I have complained about yast2 here, and email'ed them outside the list. They say bugger-all.
Cliff
On Saturday 06 January 2001 18:27, Purple Shirt wrote:
Don't take the following too serious because I am losing my mind.
Ok so I use SuSe since 5.3. Great product and it has come along nicely. Once in a while you cross a problem though where you think: what a fucking shit.
yast2 is such problem. I read others here complain about yast2. I mean who to fuck needs this graphics crap? all I want is a working utility which assists in setup. yast1 used to be this tool and keeps being handy for my work. yast2 never really crosses my mind.
previous to suse 6.4 getting sound was a bit difficult. You had to usually compile it yourself. I remember spending months in 5.3 to get my sound to work. Once I finally did it worked perfectly.
until 6.4 rolled around and with it yast2 and the fact that SuSe started trying to include sound setup with its distro. From there on sound setup may have become easy for people who like yast2 and think it does a good job. For me yast2 makes sound almost impossible to enjoy. I got opl3sa2 card.
The problem is that if I use the alsa.rpm and alsadev.rpm and use yast2 to set sound up it gives me sound but loops forever. it's not sound its noise. So there I tell myself that I just don't use yast2 and compile my sound like in the past myself.
The problem is ever since suse created this automatic sound setup its impossible to compile alsa yourself. I constantly get this stupid error:
amixer: Mixer 0/0 open error: Invalid argument
So now I spend 3 hours on trying to get my sound back. I had it achieved once under 6.4 and 7.0 but it took me hours and now where I put new HD in my box I came to the same problem again. The sound is harder to configure than it was before suse tried to do it for me.
The problem now isn;t even that I don't have sound. The mixer 0/0 problem will not even vanish if I uninstall and reinstall packages freshly. what a junk.
I wish we all go back to good old text file setup and none of this yast2 junk.
sorry for the rant.
mk
PS: I noticed there was now a conf.modules and modules.conf file in the distro. Maybe I slept but since when did this happen? It's not even symlinked. They are separate files. is SuSE so special that it needs it both ways?
_________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com
-- Scientific theories, according to Sir Karl Popper, can be "falsified," or proven wrong, by experiment. Unscientific theories -Marxist dialectical history and Freudian psychology were Popper's favorites- are formed in such a way that they cannot be falsified by data.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- proud Linux user since kernel 1.1.54 icq#42235604
"Donald G. Knecht" wrote:
one complaint about 7.0, the upgrade seems to have removed my /usr/docs/howto/mini/en directory and files..??
All docs (should) have been placed in /usr/share/doc, as per the FHS (Filesystem Hierarchy Standard). You can find your HOWTOs in /usr/share/doc/howto/en. Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
hey, thanks chris! guess i need to keep up with the times! was there an email to root about that? i don't remember seeing one..... -don Chris Reeves wrote:
"Donald G. Knecht" wrote:
one complaint about 7.0, the upgrade seems to have removed my /usr/docs/howto/mini/en directory and files..??
All docs (should) have been placed in /usr/share/doc, as per the FHS (Filesystem Hierarchy Standard). You can find your HOWTOs in /usr/share/doc/howto/en.
Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
-- LINUX - Because time is money..... and rebooting is a waste of time.
Purple Shirt wrote:
PS: I noticed there was now a conf.modules and modules.conf file in the distro. Maybe I slept but since when did this happen? It's not even symlinked. They are separate files. is SuSE so special that it needs it both ways?
Keep your shirt on, it has nothing to do with SuSE. Somewhere along the way the name changed from module.conf to conf.modules, or the other way around.
From file:/usr/src/linux/Documentation/modules.txt:
Finally, for the "purists": You can name the modprobe configuration either "/etc/conf.modules" or "/etc/modules.conf", since modprobe knows what to do in each case... On my box (SuSE 6.4), conf.modules is a sym-link to modules.conf: $ ll /etc/*modules* lrwxrwxrwx 1 root root 12 May 18 2000 /etc/conf.modules -> modules.conf -r--r--r-- 1 root root 15452 Sep 4 16:04 /etc/modules.conf I suspect you have done a copy or restore without preserving the link, expanding it to a normal file. Paul.
_________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com
Duhhh, I tried, but I couldn't find the Linux version.... _____________________________________________________________ Get your FREE download of anything else at ftp://ftp.suse.com
On January 6, 2001 07:27 pm, Purple Shirt wrote:
until 6.4 rolled around and with it yast2 and the fact that SuSe started trying to include sound setup with its distro. From there on sound setup may have become easy for people who like yast2 and think it does a good job. For me yast2 makes sound almost impossible to enjoy. I got opl3sa2 card.
The problem is that if I use the alsa.rpm and alsadev.rpm and use yast2 to set sound up it gives me sound but loops forever. it's not sound its noise. So there I tell myself that I just don't use yast2 and compile my sound like in the past myself.
The problem is ever since suse created this automatic sound setup its impossible to compile alsa yourself. I constantly get this stupid error:
amixer: Mixer 0/0 open error: Invalid argument
That doesn't sound like a compiler error. I haven't looked at yast2 in awhile but last time I did all the program did was call the alsa utilities. There is nothing stopping you from manually running alsactl. Or from hand editing the asound.conf file.
I wish we all go back to good old text file setup and none of this yast2 junk.
So don't use it. Edit the file yourself. Alsa compiles just fine here. At least when I got the kernel fixed. Just grab the tarball and do it. Nothing stopped me. All the old tools are still there. Nobody forces you to use rpm or cute programs like yast2. Nick
Purple Shirt wrote:
[...]
yast2 is such problem. I read others here complain about yast2. I mean who to fuck needs this graphics crap? all I want is a working utility which assists in setup. yast1 used to be this tool and keeps being handy for my work. yast2 never really crosses my mind.
[...] Yeeeap , Who needs YaST2, well just marketing department at SuSE.
I wish we all go back to good old text file setup and none of this yast2 junk.
So do I. Cheers j.
participants (9)
-
Chris Reeves -
Cliff Sarginson -
Donald G. Knecht -
Donald G. Knecht,KR4JX
-
Jerry Kreps -
julg＠home.com -
Nick Zentena -
P.C. Uiterlinden -
Purple Shirt