Share with the community your gutsy install/upgrade experience

[AverySimonsen]

Upgraded feisty -> gutsy on a thinkpad T41p. 2.6.22 won't boot, I get grub error 18. 2.6.20 boots fine however.

Still haven't resolved the Error 18 issue, but everything seems to run ok with 2.6.20. Voted upgrade ok after fiddling.. call me an optimist

[diogenes_3]

Clean install on top of an XP system. Live CD worked nice enough. Upon install and activation of NVIDIA drivers re-booted into blank screen. Re-re-booted to find things OK - let's keep fingers crossed...

Also keeps forgetting WLAN WPA PSK key.

Was positively surprised that
- WLAN works out of the box now
- it writes to NTFS partitions now
- it suggests by itself to install "bad, bad" codecs for MP3, DivX et al. now

[agillett]

I chose to back up my home directory and do a fresh install so that I could re-arrange some disk partitions. The pc is an AMD XP2000+ system, mostly about 5 years old.

The live desktop CD wouldn't boot at all, but the alternate CD worked and installed without any drama.

The only issue I've found is that the boot is now very slow. Looking at dmesg, it seems that the kernel is trying to set the IDE bus to UDMA/100, which fails. After four timeouts (30 seconds each) it tries UDMA/66 which works just fine.

[   34.444000] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[   34.444000] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 4096 in
[   34.444000]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   34.444000] ata1: soft resetting port
[   34.740000] ata1.00: configured for UDMA/100
[   34.740000] ata1: EH complete

This error is repeated after 64 and 94 seconds. The at 125 seconds I get:

[  125.276000] ata1.00: limiting speed to UDMA/66:PIO4
[  125.276000] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[  125.276000] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 4096 in
[  125.276000]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[  125.276000] ata1: soft resetting port
[  125.576000] ata1.00: configured for UDMA/66
[  125.576000] ata1: EH complete

After the boot completes, a hdparm command gives:

$ sudo hdparm -v -i /dev/sda
/dev/sda:
 IO_support    =  0 (default 16-bit)
 readonly      =  0 (off)
 readahead     = 256 (on)
 geometry      = 19457/255/63, sectors = 312581808, start = 0

 Model=ST3160812A                              , FwRev=3.AAJ   , SerialNo=            4LS5Q55W
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
 BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=?16?
 CurCHS=4317/15/255, CurSects=16512525, LBA=yes, LBAsects=268435455
 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4 
 DMA modes:  mdma0 mdma1 mdma2 
 UDMA modes: udma0 udma1 udma2 udma3 *udma4 udma5 
 AdvancedPM=no WriteCache=enabled
 Drive conforms to: Unspecified:  ATA/ATAPI-1,2,3,4,5,6,7

 * signifies the current active mode

I've tried adding the following options in menu.1st to try and force the kernel to use UDMA/66 (mode 4) instead of UDMA/100 (mode 5): ide0=ata66 ide1=ata66 idebus=66 but they have had no effect.

On the whole, I'm very impressed with Gutsy given the age of the pc. If I didn't have the two minutes of timeout during boot I would be delighted with it.


Andrew.

[kashey_be]

Did an upgrade.
Previous Ubuntu was an upgraded dapper -> edgy -> feisty.
The following issues came up during feisty to gutsy upgrade:
upgrade process crashed somewhere in the area of 85%.
got kernel panic -> solved by logging to previous kernel and completing the upgrade process with apt.
after reboot X did not load and got tons of messaged regarding device mapper ioctl on all vt's.
solved that by entering old kernel again & fixing xorg.conf manually.
rebooted to new kernel and still had the wired device mapper errors, started X -> discovered that my /home is not mounted. Had to restart X with root.
Removing evms solved device mapper issues and all partitions mounted correctly afterwards.

This is about it.
NOT very pleasant, NOT for the absolute beginner, and NOT smooth at all.
overall score: 1/10
conclusion: NOT ready for the desktop, but still far superior than the alternatives due to 0$ cost and spyware/adware/virus free world of computing.

[will103]

Just upgraded on the weekend and it worked flawlessly. The team has obviously done a power of work on this. Thanks.

will103

[teddydov]

Upgrade Feisty --> Gusty

All went well during Upgrade, my issue was (and still is to a point) my video card.
It seems that Ubuntu no longer likes my video card and is now forcing me to use VESA (big pain in the A**)

See Thread regarding this: (Input welcome)
http://ubuntuforums.org/showthread.php?t=580963

[rs3]

I performed a fresh install on two systems; no snags. (I tried the RC and everything went to pot very quickly, so I'm quite pleased that the final release is so much better.)

[spyrakos]

After an upgrade on 7.04 which resulted in a total mess with computer unbootable (first time since upgrades from 6.06), I did a clean install.

Major issues:

- The screens and graphics utility is completely broken: didn't manage to get a working and usable dual display until I restored my xorg.conf from the previous installation. (ATI X700, tried with both radeon and fglrx driver). On a second computer with an R280-based ATI VGA that worked flawlessly before on the radeon driver, same mess: don't know how it figured out that 1600x1200@43Hz would be a workable resolution,but that's what happened. Thank God for dpkg-reconfigure xserver-xorg, for it saved the day.

- Swapped MAC addresses between the ethernet and wireless adapters. To my surprise, the Ethernet adapter got the IP reserved for the wireless one (using Mac address-bind for IP assignment in router). Dunno if it's network-manager, bcm43xx firmware or else's fault.

- No sensible change in performance, I'd say Gnome boots a little more slowly,if any.

Overall, I wouldn't recommend it to any new users I know. The obvious cause is the screens and graphics tool situation. I think it's much worse to have a GUI tool that doesn't work, than to not have it at all. When I first used Ubuntu, I knew I had to get my hands dirty in console and stuff, I read the documentation and made it through. If I expected everything to work out of the box or through a GUI tool and didn't make it, I'd probably think it's broken and never got anywhere near Linux in the future.

To my experience, they should have waited until next release for this feature in order to do a more extensive beta testing on it. I'm convinced it moves to the right direction (usability, user-friendliness) though.

[unixcrab]

The upgrade made such a mess of my system. The only thing different on my Feisty system from the std. install was that I had to manually install Xgl (ATI card etc.). After the upgrade it was just a dogs breakfast with too many things wrong to list here. Not a train smash so I did a clean install.
But I had a far more serious problem today. My machine refused to boot because of fsck errors about orphaned inodes. I had to boot off the cd and manually check the filesystem. This is a bad situation for a distribution thats only been out for days, used on a machine for nothing more than web browsing and openoffice

[Chip]

Upgraded 2 computers, one a Dell Inspiron 8200 laptop and the other a Dell Dimension 8250 desktop with a GeForce 7600GS graphics card and 2407WFP display. I had problems with the nvidia drivers on both. I upgraded from 7.04 and restricted nvidia drivers were running fine on both before I started the upgrade.

On the Dell Inspiron 8200 laptop the install seemed to go fine but the laptop display panel came up blank with the backlight off. In this case the upgrade chose nvidia-glx as opposed to nvidia-glx-new as the driver. I guess the laptop is too old. It seemed to make the normal startup sounds and I was able to login even with no screen. I connected an external monitor to the VGA output of the laptop and could see the desktop fine. I solved this problem by adding "UseDisplayDevice" "DFP" to the xorg.conf file as outlined in bug#109414. At this point it all works and you can play with the Compiz Fusion to your hearts content. If you don't need the eye candy the open source nv driver seems to work just as well.

On the Dell Dimension 8250 desktop with the GeForce 7600GS the install picked the nvidia-glx-new driver as the restricted driver of choice. On bootup the driver said that it cannot find the board or display and so resorts to a 800x600 EGA type low-res display. A check of supported devices on the Nvidia website shows the GeForce 7600GS to be a supported device for this driver. If I remove the restricted driver and go back to the open source nv driver everything works fine. However, without the restricted driver you can't play with Compiz Fusion. I tried re-installing and it did the same thing. I have not resolved this problem and so am stuck with nv.