[Maverick] Installer

NoOp glgxg at sbcglobal.net
Fri Oct 1 03:14:26 UTC 2010


On 09/30/2010 07:47 PM, NoOp wrote:
> On 09/30/2010 06:42 PM, NoOp wrote:
>> I resized my Lucid partition & left a 20Gb unallocated section (from a
>> previous Maverick install) available to install/reinstall Maverick.
>> Using the Sept 29 daily Maverick liveCD (which has changed considerably
>> from previous versions) I select 'Install alongside other operating
>> systems' & the shows that my lucid is only 143.1GB (it's 173GB) and the
>> target /dev/sda6 is 30.2GB (it's only 20GB).
>> 
>> At this point I abort because I think that the installer is also picking
>> up the unallocated & Win7 recovery partitions & 5.9GB swap. If this is
>> the case then it's a pretty dangerous situation. I'll dig into it in
>> more detail tomorrow, but is anyone else seeing the same?
>> 
>> /dev/sda
>>  /dev/sda1 ntfs 208MB
>>  /dev/sda2 ntfs 104857MB (Win7)
>>  free space     2033MB
>>  /deb/sda5 ext4 173236MB (this is my lucid)
>>  free space     20975MB (this is the old maverick test partion)
>>  /dev/sda6 swap 5969MB
>>  /dev/sda3 ntfs 12788MB (Win7 recovery)
>> 
>> I can of course manually install to 'free space 20975MB', but the
>> differences in the 'Install alongside other operating systems' concerns
>> me. Why would it want to shrink my sda5?
> 
> And... silly me, I forgot to add that there is no sign of wireless once
> I installed on the new partion. Previous Maverick had wireless working
> just fine (but it was an lucid to maverick update so perhaps that is the
> reason). Boot to the lucid partition & wireless is working from the
> out-of-the-box install. Sigh..SOS... but we've now even more Ubuntu One
> defaults & that should make things much better, eh?

OK, I'll stop blogging... wifi works *if* you boot to Win7, enable wifi
there, and then boot back to Maverick. Interesting that if you boot to
lucid and do the same it doesn't work. Obviously it's not bios or Win7
that's holding up the wifi detection as otherwise it wouldn't work in
lucid on the same machine.

Same Old S#$% from previous installs whereby this *still isn't* fixed.
If I get ambitious tomorrow I'll try to find the bug for this. Good luck
to all in the next 10.10 days...







More information about the ubuntu-users mailing list