On Fri, Jan 07, 2011 at 09:51:40AM +0000, David Aveiro wrote: > Hi! > > I'm using rc5 and I can do suspend with no problems. Even the screen > going blank after resume and the brightness adjustment which were > not working in previous releases now work. My only problem while > using intel is no sound. > > I did apply the infamous patch to the BIOS so I can do static > switching and only one card is active at any time. I suppose that > may be one reason I can suspend/resume ok and you cannot... >
Yes, I think that's probably right. I'm running the 2.6.37-rc kernels with a normal BIOS and have been unable to suspend for a while now. I've reported this to the pm-utils maintainer: https://bugzilla.redhat.com/show_bug.cgi?id=665343 Adam > > On 01/07/2011 09:40 AM, Holger Schwenk wrote: > > > >Hello David, > > > >thanks a lot for your fast answer ! > > > >I took the kernel-2.7.37-0.rc3.git2.1.fc15.x86_14 and it does work > >! I now can use the full resolution of 1920x1080. However, I had > >to remove "nomodeset" in the kernel params. > > > >Do you rather recommend one of the other 2.7.37 kernels ? In fact, > >in the current version, suspend to RAM and disk does not work, nor > >the audio. > >Looking at the threads, it seems to be "normal" that audio does > >not work, but other people seem to have suspend working. > >This would be very useful for me since I usually never boot me laptop ;-) > > > >Also, both graphic cards are on (using lspci) and I get 23.8W > >power consumption ! Is there a way to "switch off" the Nvidia card > >? > > > >Holger > > > >On 01/06/2011 12:26 AM, David Aveiro wrote: > >>Hi, > >> > >>I am also a Fedora fan and I'm using two kernels: > >> > >>*Nvidia* - (noveau driver) - most recent Fedora kernel from updates > >>*Intel* - most recent fedora 15 kernel release candidate, > >>available here: http://kyle.fedorapeople.org/kernel/ > >> > >>Check my message from 11/18/2010 on the archives with some hints > >>for configuration/install and solving resume/suspend problem. > >> > >>I just updated to the rc5 kernel but I still have the problem of > >>not having sound available... > >> > >>I tried running > >> > >>alsamixer -c0 > >> > >>And I get the following output: > >> > >> > >>?????????????????????????????? AlsaMixer v1.0.23 > >>?????????????????????????????? > >>? Card: HDA Intel F1: Help > >>? > >>? Chip: Realtek ALC889 F2: > >>System information ? > >>? View: F3: Playback F4: Capture F5: All F6: > >>Select sound card ? > >>? Item: Esc: Exit > >>? > >>? > >>? > >>? This sound device does not have any controls. > >> > >> > >>Which is strange, the card seems to be detected but cannot be > >>used. In Gnome Sound properties no hardware is present. > >> > >>Any hints? > >> > >>Kind regards, > >>David > >> > >>On 01/05/2011 09:19 PM, Holger Schwenk wrote: > >>>Hello, > >>> > >>>I am using Linux on a Vaio VGN-SZXWN since more than three years and I > >>>really like this machine. Everything works fine (using Fedora Core 12). > >>> > >>>I just got a new Vaio, a VPC-Z13 which has i7 M640 CPU, 1920x1080 > >>>display and SSD disks. Unfortunately, I've quite some trouble installing > >>>Linux on it. I'm used to Fedora and KDE, and I tried FC14. This comes > >>>with an 2.6.35.6-45 kernel and grub 0.97. > >>> > >>>It only installs when I use the vesa X11 driver (version 2.3.0-1) and I > >>>end up with an ugly 1280x1024 resolution. The Fedora release notes quote > >>>that this is related to missing eDP support in this kernel. There are > >>>quite some messages on various lists about this issue, but I've trouble > >>>to filter out a clear solution (if there is one :-( > >>>There seems to be a specific solution for Ubuntu > >>>(http://www.voip-x.co.uk/files/adam/IMPORTANT_README), but if possible > >>>I'd like to keep Fedora, simply because I'm used to it ;-) > >>> > >>>Can you please recommend a version of the kernel, grub, X11 that will > >>>work with a 1920x1080 resolution (I don't care about the Nvidia > >>>Graphics) ? > >>> > >>>By the way, an update of all the packages resulted in a X11 freeze after > >>>reboot. Right now, I don't know whether this happens because of newer > >>>drivers or a different X11 configuration (not vesa anymore). I would > >>>need to go again though a complete reinstall, but I could of course do > >>>this if it is useful ;-) > >>> > >>>Upgrading the kernel alone seems to be OK (2.6.35.10-74), removing > >>>"nomodeset" from the kernel params results in a freeze ... > >>> > >>>Thanks a lot for your help ! > >>> > >>>Holger > >> > >> > >>_______________________________________________ > >>Mailing list:https://launchpad.net/~sony-vaio-z-series > >>Post to :[email protected] > >>Unsubscribe :https://launchpad.net/~sony-vaio-z-series > >>More help :https://help.launchpad.net/ListHelp > > > _______________________________________________ > Mailing list: https://launchpad.net/~sony-vaio-z-series > Post to : [email protected] > Unsubscribe : https://launchpad.net/~sony-vaio-z-series > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~sony-vaio-z-series Post to : [email protected] Unsubscribe : https://launchpad.net/~sony-vaio-z-series More help : https://help.launchpad.net/ListHelp
