Re: [Cooker] RC3 Bugs (second try)
I'll give your suggestions a try, however as I said previously I'm going to wait for 9.0 to go gold. Alan - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, September 22, 2002 2:50 PM Subject: Re: [Cooker] RC3 Bugs (second try) > On Sat, 21 Sep 2002, Alan Hughes wrote: > > > I originally fiddled with the mixer settings, volume and just about > > everything else. Nothing worked, nada, just the big silence. Switching over > > to the audigy (sp?) driver (which I understand is OSS) and everything worked > > perfectly immediately. > > > Assuming you use analog speakers on rear channel: > > Try again, use alsamixer or alsamixergui, mute the very last channel > (analog output jack), increase Wave surround volume. > Does it work now? > > Easier say: plug your speakers into front channel. > > Danny > PS: the audigy driver is not really ment of a sblive, but will work. > > > > My box is a dual P-III running the SMP kernel, vanilla RC3 with the > > exception that I put the latest initscripts RPM on (USB problems as > > previously reported here). > > > > I plan some more fiddling, but not until after 9.0 goes gold - I've got some > > other things to do, including educating the wife on Linux so that she can > > start to teach people at work. > > > > Alan > > > > ----- Original Message - > > From: <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Saturday, September 21, 2002 1:26 PM > > Subject: Re: [Cooker] RC3 Bugs (second try) > > > > > > > On Sat, 21 Sep 2002, Alan Hughes wrote: > > > > > > > Sorted it out last night, although I use HardDrake to set the OSS > > driver. I > > > > think that ALSA just does not support SoundBlaster Live properly (along > > with > > > I disagree, because it works fine for some other people. > > > David may say it doesn't work but that is only because he gets artifacts > > > on his specific systems. > > > ALSA drivers work fine on most SBLives. But there are a few different > > > kinds, and YMMV. Some people like ALSA better, because it supports more > > > features and is the best maintained. I hope David will report the > > > artifacts to alsa-devel, so they are fixed in the next version. > > > > > > Alan, it would be better to figure out why it was not working on your > > > setup, because you did not really explain. If it was that you did not > > > hear sone on your rear channel than it is a mixer configuration issue, > > > which I hoped would be fixed, but you can always manually set your mixer > > > correct. > > > > > > Danny > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: [Cooker] RC3 Bugs (second try)
On Sat, 21 Sep 2002, David Walser wrote: > > What about all of the many other people on this list > reporting problems completely different from my own? I've been reading the list, and in my opinion, all the problems arise due to wrong mixer settings, or even unrelated problems like issues with artsd. Execept for your problem, which also affected one other person. If you disgree, give me a link to a different problem than the staticity you are hearing. > > > To this point you haven't asked me, or the numerous They were not numerous:) > other people reporting problems to report something to > alsa-devel. I'm 100% willing to do so, what info. can > I give them to be the most helpful to them? You, of all people should have done it immediatly on the moment you heard staticity, because you know how the development works. Just give a list of your hardware, alsa version, mixersetting and problems to alsa-devel. Perhaps it would allready be fixed. > > Unfortunately a lot of the other people who reported > problems probably aren't still watching this list. I do not understand the references to loads of other peoples. I read the list, and it is a veyr limited numer of people, only 2 of them have a real problem. > > A simple fix, that applies to some of the other people > who've had problems too. Don't you think we should a) > fix the default ALSA mixer values so they're not > screwed up out of the box, or b) use OSS by default > until we can manage to do a)? Yes, and I think I asked Thierry to do this (a), he seemed positive but has not gotten around to it yet. However, I am sure he will apply a patch provided by you. bye Danny
Re: [Cooker] RC3 Bugs (second try)
On Sat, 21 Sep 2002, Alan Hughes wrote: > I originally fiddled with the mixer settings, volume and just about > everything else. Nothing worked, nada, just the big silence. Switching over > to the audigy (sp?) driver (which I understand is OSS) and everything worked > perfectly immediately. > Assuming you use analog speakers on rear channel: Try again, use alsamixer or alsamixergui, mute the very last channel (analog output jack), increase Wave surround volume. Does it work now? Easier say: plug your speakers into front channel. Danny PS: the audigy driver is not really ment of a sblive, but will work. > My box is a dual P-III running the SMP kernel, vanilla RC3 with the > exception that I put the latest initscripts RPM on (USB problems as > previously reported here). > > I plan some more fiddling, but not until after 9.0 goes gold - I've got some > other things to do, including educating the wife on Linux so that she can > start to teach people at work. > > Alan > > - Original Message - > From: <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Saturday, September 21, 2002 1:26 PM > Subject: Re: [Cooker] RC3 Bugs (second try) > > > > On Sat, 21 Sep 2002, Alan Hughes wrote: > > > > > Sorted it out last night, although I use HardDrake to set the OSS > driver. I > > > think that ALSA just does not support SoundBlaster Live properly (along > with > > I disagree, because it works fine for some other people. > > David may say it doesn't work but that is only because he gets artifacts > > on his specific systems. > > ALSA drivers work fine on most SBLives. But there are a few different > > kinds, and YMMV. Some people like ALSA better, because it supports more > > features and is the best maintained. I hope David will report the > > artifacts to alsa-devel, so they are fixed in the next version. > > > > Alan, it would be better to figure out why it was not working on your > > setup, because you did not really explain. If it was that you did not > > hear sone on your rear channel than it is a mixer configuration issue, > > which I hoped would be fixed, but you can always manually set your mixer > > correct. > > > > Danny > > > > > > > > > > > > > > > > >
Re: [Cooker] RC3 Bugs (second try)
I originally fiddled with the mixer settings, volume and just about everything else. Nothing worked, nada, just the big silence. Switching over to the audigy (sp?) driver (which I understand is OSS) and everything worked perfectly immediately. My box is a dual P-III running the SMP kernel, vanilla RC3 with the exception that I put the latest initscripts RPM on (USB problems as previously reported here). I plan some more fiddling, but not until after 9.0 goes gold - I've got some other things to do, including educating the wife on Linux so that she can start to teach people at work. Alan - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, September 21, 2002 1:26 PM Subject: Re: [Cooker] RC3 Bugs (second try) > On Sat, 21 Sep 2002, Alan Hughes wrote: > > > Sorted it out last night, although I use HardDrake to set the OSS driver. I > > think that ALSA just does not support SoundBlaster Live properly (along with > I disagree, because it works fine for some other people. > David may say it doesn't work but that is only because he gets artifacts > on his specific systems. > ALSA drivers work fine on most SBLives. But there are a few different > kinds, and YMMV. Some people like ALSA better, because it supports more > features and is the best maintained. I hope David will report the > artifacts to alsa-devel, so they are fixed in the next version. > > Alan, it would be better to figure out why it was not working on your > setup, because you did not really explain. If it was that you did not > hear sone on your rear channel than it is a mixer configuration issue, > which I hoped would be fixed, but you can always manually set your mixer > correct. > > Danny > > > > > > >
Re: [Cooker] RC3 Bugs (second try)
--- [EMAIL PROTECTED] wrote: > On Sat, 21 Sep 2002, Alan Hughes wrote: > > > Sorted it out last night, although I use HardDrake > to set the OSS driver. I > > think that ALSA just does not support SoundBlaster > Live properly (along with > I disagree, because it works fine for some other > people. > David may say it doesn't work but that is only > because he gets artifacts > on his specific systems. > ALSA drivers work fine on most SBLives. But there What about all of the many other people on this list reporting problems completely different from my own? > are a few different > kinds, and YMMV. Some people like ALSA better, > because it supports more > features and is the best maintained. I hope David > will report the > artifacts to alsa-devel, so they are fixed in the > next version. To this point you haven't asked me, or the numerous other people reporting problems to report something to alsa-devel. I'm 100% willing to do so, what info. can I give them to be the most helpful to them? Unfortunately a lot of the other people who reported problems probably aren't still watching this list. > Alan, it would be better to figure out why it was > not working on your > setup, because you did not really explain. If it was > that you did not > hear sone on your rear channel than it is a mixer > configuration issue, > which I hoped would be fixed, but you can always > manually set your mixer > correct. A simple fix, that applies to some of the other people who've had problems too. Don't you think we should a) fix the default ALSA mixer values so they're not screwed up out of the box, or b) use OSS by default until we can manage to do a)? __ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com
Re: [Cooker] RC3 Bugs (second try)
On Sat, 21 Sep 2002, Alan Hughes wrote: > Sorted it out last night, although I use HardDrake to set the OSS driver. I > think that ALSA just does not support SoundBlaster Live properly (along with I disagree, because it works fine for some other people. David may say it doesn't work but that is only because he gets artifacts on his specific systems. ALSA drivers work fine on most SBLives. But there are a few different kinds, and YMMV. Some people like ALSA better, because it supports more features and is the best maintained. I hope David will report the artifacts to alsa-devel, so they are fixed in the next version. Alan, it would be better to figure out why it was not working on your setup, because you did not really explain. If it was that you did not hear sone on your rear channel than it is a mixer configuration issue, which I hoped would be fixed, but you can always manually set your mixer correct. Danny
Re: [Cooker] RC3 Bugs (second try)
Sorted it out last night, although I use HardDrake to set the OSS driver. I think that ALSA just does not support SoundBlaster Live properly (along with some other sound cards from what I gather in some of the other messages). Other than that everything is looking OK, although I'm not using USB periphals at the moment. Alan - Original Message - From: "David Walser" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 20, 2002 8:14 PM Subject: Re: [Cooker] RC3 Bugs (second try) > Run draksound. I think RC3 still uses the problematic > ALSA module by default, this still hasn't been fixed > AFAIK. > > --- Alan Hughes <[EMAIL PROTECTED]> > wrote: > > Yep, the new initscripts worked. Now just have to > > get my SOundBlaster Live > > working (correct module, worked in 8.2, not in RC3). > > __ > Do you Yahoo!? > New DSL Internet Access from SBC & Yahoo! > http://sbc.yahoo.com >
Re: [Cooker] RC3 Bugs (second try)
Run draksound. I think RC3 still uses the problematic ALSA module by default, this still hasn't been fixed AFAIK. --- Alan Hughes <[EMAIL PROTECTED]> wrote: > Yep, the new initscripts worked. Now just have to > get my SOundBlaster Live > working (correct module, worked in 8.2, not in RC3). __ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com
Re: [Cooker] RC3 Bugs (second try)
Yep, the new initscripts worked. Now just have to get my SOundBlaster Live working (correct module, worked in 8.2, not in RC3). Alan - Original Message - From: "Alan Hughes" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 20, 2002 7:32 PM Subject: Re: [Cooker] RC3 Bugs (second try) Thanks, I'm going to try initscripts 10 as soon as I've done a re-install. The problem with /usr is however a major headache - I never have /usr integrated with /, either at home or at work. I just hope this will be fixed for 9.0 final. For the moment I'm doing a re-install so that I can play with some of the options. The VFS message looks like the one I've seen, although I've never got a good look at it. The "Have a nice day..." bit sounds like a piece of kernel code however :-) Alan - Original Message - From: "Götz Waschk" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 20, 2002 8:45 AM Subject: Re: [Cooker] RC3 Bugs (second try) Hi, I'd like to comment some of your problems. Am Freitag, 20. September 2002, 07:53:45 Uhr MET, schrieb [EMAIL PROTECTED]: > 2. I reformatted partitions originally created for RC2. / is mounted from > /dev/hda12 (ReiserFS), while /usr, /var, /tmp and /home are mounted from LVM > partitions (XFS). mkfs.xfs reports that it could not find the lvdisplay > command (see in ddebug.log). At the moment there are still problems with /usr on a separate partition. You could try to install again with /usr on the root partition. > 3. On booting RC3 it reported an error in /etc/init.d/usb (line 1: eval not > found). This is early on in the boot process, just after the host name is > set, but before the LVM volumes are mounted (I think). This and your USB mouse problem relate to the fact mentioned above. The usb script requires a binary from /usr, but that partition in't mounted then. This has been fixed in initscripts 10mdk. > 4. On shutting down the system I briefly saw a message in which the VFS > seemed to say that some inode where still open. The system still shut down > OK. Not sure what these messages meant, and they appeared and disappered so quickly I was not able to work out excatly what they said. I also had this problem, however I could identify the message: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day... That message is from fs/super.c I am not a kernel hacker, but I think some partition didn't umount successfully, maybe you could try to disable supermount and see if this helps. -- Götz Waschk <> master of computer science <> University of Rostock http://wwwtec.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key --> Logout Fascism! <--
Re: [Cooker] RC3 Bugs (second try)
Thanks, I'm going to try initscripts 10 as soon as I've done a re-install. The problem with /usr is however a major headache - I never have /usr integrated with /, either at home or at work. I just hope this will be fixed for 9.0 final. For the moment I'm doing a re-install so that I can play with some of the options. The VFS message looks like the one I've seen, although I've never got a good look at it. The "Have a nice day..." bit sounds like a piece of kernel code however :-) Alan - Original Message - From: "Götz Waschk" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 20, 2002 8:45 AM Subject: Re: [Cooker] RC3 Bugs (second try) Hi, I'd like to comment some of your problems. Am Freitag, 20. September 2002, 07:53:45 Uhr MET, schrieb [EMAIL PROTECTED]: > 2. I reformatted partitions originally created for RC2. / is mounted from > /dev/hda12 (ReiserFS), while /usr, /var, /tmp and /home are mounted from LVM > partitions (XFS). mkfs.xfs reports that it could not find the lvdisplay > command (see in ddebug.log). At the moment there are still problems with /usr on a separate partition. You could try to install again with /usr on the root partition. > 3. On booting RC3 it reported an error in /etc/init.d/usb (line 1: eval not > found). This is early on in the boot process, just after the host name is > set, but before the LVM volumes are mounted (I think). This and your USB mouse problem relate to the fact mentioned above. The usb script requires a binary from /usr, but that partition in't mounted then. This has been fixed in initscripts 10mdk. > 4. On shutting down the system I briefly saw a message in which the VFS > seemed to say that some inode where still open. The system still shut down > OK. Not sure what these messages meant, and they appeared and disappered so quickly I was not able to work out excatly what they said. I also had this problem, however I could identify the message: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day... That message is from fs/super.c I am not a kernel hacker, but I think some partition didn't umount successfully, maybe you could try to disable supermount and see if this helps. -- Götz Waschk <> master of computer science <> University of Rostock http://wwwtec.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key --> Logout Fascism! <--
Re: [Cooker] RC3 Bugs (second try)
Hi, I'd like to comment some of your problems. Am Freitag, 20. September 2002, 07:53:45 Uhr MET, schrieb [EMAIL PROTECTED]: > 2. I reformatted partitions originally created for RC2. / is mounted from > /dev/hda12 (ReiserFS), while /usr, /var, /tmp and /home are mounted from LVM > partitions (XFS). mkfs.xfs reports that it could not find the lvdisplay > command (see in ddebug.log). At the moment there are still problems with /usr on a separate partition. You could try to install again with /usr on the root partition. > 3. On booting RC3 it reported an error in /etc/init.d/usb (line 1: eval not > found). This is early on in the boot process, just after the host name is > set, but before the LVM volumes are mounted (I think). This and your USB mouse problem relate to the fact mentioned above. The usb script requires a binary from /usr, but that partition in't mounted then. This has been fixed in initscripts 10mdk. > 4. On shutting down the system I briefly saw a message in which the VFS > seemed to say that some inode where still open. The system still shut down > OK. Not sure what these messages meant, and they appeared and disappered so quickly >I was not able to work out excatly what they said. I also had this problem, however I could identify the message: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day... That message is from fs/super.c I am not a kernel hacker, but I think some partition didn't umount successfully, maybe you could try to disable supermount and see if this helps. -- Götz Waschk <> master of computer science <> University of Rostock http://wwwtec.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key --> Logout Fascism! <--
