search

tvogel / vaio-f11-linux

Automatically exported from code.google.com/p/vaio-f11-linux
7 stars 2 forks source link

Ubuntu 10.10 Release Candidate #33

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
If, by chance, any user comes here before they choose to upgrade their laptop, 
I would HIGHLY RECOMMEND NOT upgrading. I typically download the newest version 
of Ubuntu at about the third Alpha release, so I'm used to the errors and bugs 
that come along with it. 10.10 has by far given me the most trouble I think 
I've ever had.

It messed up my display, and will not even load it or recognize that there is 
an error. The previous work-around that I think just about everyone was using 
will NOT fix this. I've tried. Just to be able to properly boot into Ubuntu 
using x I had to boot into the safe mode and uninstall the Nvidia drivers.

Also, closing the laptop lid will no longer send you computer into standby, it 
instead chooses to turn it off completely.

I'm not trying to run here and complain, I'm aware that these will more than 
likely be fixed soon, I'm just trying to warn others of the potential dangers 
of updating!

Original issue reported on code.google.com by xxBartonxx@gmail.com on 6 Oct 2010 at 12:55

GoogleCodeExporter commented 9 years ago 
I have been giving the same advice for a while. I've been using the
10.10 (Maverick) beta since its inception and while I expected the usual
problems and progressive improvements, in reality, things have become
progressively worse.

We have solved a lot of issues, but many are being parked.

I suspect the issue that you've hit is because of the inclusion of the
most recent nvidia drivers, 260.19.06. This was a premature act, and
unfortunately is a reflection of the lack of experience of much of the
Ubuntu team. This driver does not work on many cards, and, certainly not
for the GeForce GT 330M in my Sony Vaio F-series.

Keep in mind that Ubuntu have a release target of 10/10/10 and I get the
impression that regardless of issues, this date will be kept.  One can
only speculate that there is a lot of prepared marketing behind that
unique date.

My solution to the video driver issue is to load the 256.53 drivers
available directly from the Nvidia site. This must be installed without
X running, so it's easiest to boot to recovery mode and install it
there.

For the suspend/resume issue, you could try this:

  http://ubuntuforums.org/showthread.php?t=1586178

I am currently running the 2.6.32-0206322109-generic kernel, since it is
the only one that resumes reliably.

Thus to make things work on Maverick I am using a quite old Lucid kernel
and "old" non-packaged Nvidia drivers.

<rant>
The amount of work required to keep Ubuntu running reminds me of Linux
in the 1990s. Of course, when it works it's fine. The problem is that
they have removed all the edge cases and made diagnostics and fixing
incredibly difficult. Linux is not like Apple. It can't be opinionated
software, because there are far too many variables. Doesn't stop
Shuttleworth's mission, though.
</rant>

For my part, I spent yesterday trying out Fedora 13 on an old machine.
It seems like a great distro, and when I have the time, I expect to move
my Vaio onto it. This is not a decision taken lightly, as it require
days of effort to make the move, but such has Ubuntu become that I
think it will be repaid quite quickly.

Original comment by auxb...@gmail.com on 6 Oct 2010 at 10:59

GoogleCodeExporter commented 9 years ago 
Yeah, looks like it's time to go back to 10.04. At least that version was 
manageable. My laptop was at least usable last night (albeit the horrible 
resolution problems, no advanced graphics, etc) but as of this morning it 
somehow got worse! Even without the Nvidia drivers being used my display 
freaked out. There was absolutely no backlight whatsoever. If I squinted or 
shined a light on my screen, I could barely make out what was being display. 
Trying to fix it was horrible. Looks like I'm just copying my config files and 
going back to 10.04 for a while. :/

P.S. As I was writing this I realized I probably could have hooked my computer 
up to a second monitor to try to fix it, but at this point it's really not even 
worth the effort. If people are reading this, DO NOT UPGRADE! It's bad.

P.P.S. Thanks for the info though auxbuss, I appreciate the reply. I would have 
tried out the solutions you mentioned, but...

Original comment by xxBartonxx@gmail.com on 6 Oct 2010 at 5:19

GoogleCodeExporter commented 9 years ago 
same for me, unluckly I didn't read this topic before the upgrade. 

so:

- nvidia drivers bugged, they didn't start X at all. I had to restore defualt 
driver and then install them from the nvidia website

- notification area fails to launch. I don't know why but the network, 
bluetooth and battery applet won't load even if they are right configured

- some blank screen not recoverable when tryed to set up power management 
settings

- X laggish

Why the hell they realeased that version I still don't know. Maybe Ubuntu is 
managed by Microsoft instead of Canonical.

I'm switching to 10.04

Original comment by omar.fre...@gmail.com on 12 Oct 2010 at 6:09

GoogleCodeExporter commented 9 years ago 
I also upgraded too early from lucid to maverick and was bitten by this problem 
on my VPC F12 S1E. Finally, though, I found the following solution:

Install nvidia-current version 256.52-0ubuntu0sarvatt available from the 
xorg-edgers repository on launchpad, i.e. add

deb http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu maverick main
deb-src http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu maverick main

to your /etc/apt/sources.list (or a xyz.list file in /etc/apt/sources.list.d/) 
and select the specific version 256.52... to install in aptitude (or whatever 
you use that permits choosing a particular version).

If you want to prevent your system from accidentally upgrading to 260.xx, put 
the following into your /etc/apt/preferences:

Package: nvidia-current
Pin: version 260.19.06*
Pin-Priority: -1000

This will effectively forbid installing that version. Resist the urge to put 
that stanza into a file under /etc/apt/preferences.d/ if you use aptitude. 
After some research I found it to be a known bug^H^H^H feature that some of the 
debian/ubuntu tools don't pick up on that directory, among which aptitude.

Of course, the problems known from lucid with the Vaio's graphics unit are 
still there, but at least, I'm back to what I was used to under lucid with 
maverick, i.e. accelerated 3d and smooth suspend/resume.

Hope this is useful for someone... Cheers, 
Lars

Original comment by dr.peter...@gmail.com on 12 Oct 2010 at 7:07

GoogleCodeExporter commented 9 years ago 
VPCF11C5E here.
I was happy with Maverick beta since a few day before the release, when 
nvidia-current was updated to 260.19.
Thus I installed 256.53 from nvidia site and it seems to work fine with these 
two annotations:

EDID hack in xorg.conf seems not necessary anymore. Without xorg.conf Maverick 
starts in low res, but all it's needed is to force nvidia driver with an 
xorg.conf having this single section:

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
EndSection

Fn+F5 and Fn+F6 (brightness) don't work anymore, while they used to work with 
Lucid.

Original comment by stefano....@gmail.com on 12 Oct 2010 at 8:47

GoogleCodeExporter commented 9 years ago 
Eh, I already went back to 10.04 and don't really see any reason on trying 
10.10 again for at least a while. 10.04 is pretty stable, and everything is 
rather predictable at this point. I'm glad there are efforts already to get 
this fixed, since I'm sure at some point I'll be needing them once I update.

I'll probably turn my eye to 10.10 around January or so and see how things look.

Original comment by SEALBar...@gmail.com on 12 Oct 2010 at 9:38

GoogleCodeExporter commented 9 years ago 
I installed the 10.04.1 and I had the same issue of the 10.10: nm-applet and 
bluetooth-applet does not start automatically. I have to launch them with a 
terminal (or alt-f2) command. I tried in a fresh home, thinking it was a 
corrupted file, but without success. In "startup programs" they are right 
configured, if I copy&paste the command written there in a terminal they start 
without problems.

Does anybody have the same issue? Do you have some tips?

Original comment by omar.fre...@gmail.com on 15 Oct 2010 at 9:01

GoogleCodeExporter commented 9 years ago 
I've actually never had that problem, and I've installed 10.04 on three 
different occasions on my laptop. Did you install a direct image of 10.04.1, or 
install 10.
04 and it has since updated? I don't really see why it would make any 
difference, but that's the only thing I can think of.

Original comment by xxBartonxx@gmail.com on 16 Oct 2010 at 12:01

GoogleCodeExporter commented 9 years ago 
I found the "issue", sorry it was banal but I went crazy until I noticed that 
in the gdm login it was selected "Ubuntu desktop edition (safe mode)" and not 
the normal mode. Damn. Thanks anyway :-)

Original comment by omar.fre...@gmail.com on 16 Oct 2010 at 10:15

GoogleCodeExporter commented 9 years ago 
After my upgrade from 10.04 to 10.10, X didn't work anymore. So I decided to 
remove all nvidia packages, remove xorg.conf and restart my computer to use 
nouveau.

Now it works by default using nouveau. My resolution is correctly detected 
1920x1080. It's the principal for my work.

Now, I'ld like to find a solution to fix brightness and use compiz.

For info, I use Sony Vaio VPCF11Z1E

Original comment by mathieu....@gmail.com on 16 Oct 2010 at 12:10

GoogleCodeExporter commented 9 years ago 
3d isn't officially supported for nouveau, but it still seems to work pretty 
well. So I'll try to enable it with this tuto : 

http://ubuntuforums.org/showthread.php?t=1590367

I keep you informed

Original comment by mathieu....@gmail.com on 16 Oct 2010 at 12:35

GoogleCodeExporter commented 9 years ago 
Try following this:
http://code.google.com/p/vaio-f11-linux/wiki/NVIDIASetup

When I upgraded from 10.04 to 10.10, my xorg.conf file went from a bunch of 
lines to about 20.  You need to run nvidia-xconfig to regenerate that file 
(after installing a good driver).  Then add any needed changes to xorg.conf

Original comment by earthme...@gmail.com on 22 Oct 2010 at 4:25

GoogleCodeExporter commented 9 years ago 
Hi, I tried to upgrade without reading this topic in advance too...

I solved my problems following dr.petersen's suggestion and installing 
nvidia-current version 256.52-0ubuntu0sarvatt (see above).

As far as the hibernation/suspension issue is regarded I enabled them by adding 
the option "acpi_sleep=nonvs" to the kernel commands in grub (the idea came 
from this thread: 
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/654870, comment n. #5).

Now I have a fully working Maverick with Kde 4.5.3.

Original comment by kilo...@gmail.com on 7 Nov 2010 at 10:38

GoogleCodeExporter commented 9 years ago 
This is not a forum. Please use issues for individual items.

Original comment by Jason.Donenfeld on 9 Nov 2010 at 5:44