(SP1) Gparted fix

Another one bites the dust!

This has been an ongoing problem, not just in Puppy 4.x. On some systems, when Gparted starts up it takes a very long time to scan the drives. In the latest report, the scan went on indefinitely.

The workaround is to provide a drive on the commandline, for example 'gparted /dev/sda', and then Gparted will only scan that drive.

So, I have written a little wrapper GUI, /usr/sbin/gparted_shell, that puts up a list of drives, you select the one you want, then Gparted is executed. It also has the option of scanning all drives.


Posted on 25 Oct 2008, 17:31


Comments:

Posted on 25 Oct 2008, 18:34 by Dougal
Slow Starting
I know one thing I noticed that caused Gparted to be slow to start is the existence of device nodes such as /dev/ram0 or "mem0" or something (nodes that didn't exist in the static /dev) and which Gparted listed among the available devices...


Posted on 26 Oct 2008, 8:19 by eprv
Gparted
From my experience it is related to BIOS settings, if a device such as CDROM or floppy is not installed it should be disabled in the BIOS, otherwise Gparted will wait for that device very long time


Posted on 26 Oct 2008, 9:52 by PaulBx1
wrapper
Barry, that gparted wrapper would be a good place to warn people not to mess with the Vista partition as I mentioned earlier (it makes Vista unbootable, and in some cases is not fixable). No problem with an XP partition.


Posted on 26 Oct 2008, 13:18 by rarsa
Welcome addition
Up to now I've been starting GParted from the command line,

Greta forward thinking to solve the problem for the rest.


Posted on 27 Oct 2008, 7:55 by BarryK
Re: Vista partition
Ok, I have added the warning about Vista.



Posted on 27 Oct 2008, 18:11 by tempestuous
915resolution
Barry,
For 4.1.1 - I just updated 915resolution to support the Intel GM965 chipset.
This has been tested by forum member PuppyUSBUser.
http://www.murga-linux.com/puppy/viewtopic.php?p=223799

Also a suggestion about the PREFLIST:
the ath5k wifi driver has been widely reported as unreliable under the 2.6.25 kernel. I would give preference to the ath_pci module.
Also I would give preference to the new r8101 over the r8169. They claim an overlapping range of pci id's.


Posted on 28 Oct 2008, 6:35 by happypuppy
Even more bugs to report
There's a bug in the Puppy Boot Configuration wizard:

In the wizard where you manually select additional modules to be loaded at bootup,if you add more than one module in the box at the right, none of those modules will get loaded after a reboot.

Instead of adding each module in a separate line,the wizard places all of them in one line as they were additional parameters for the first module.
Same for the box where you are asked to specify a parameter for the module.They're all mixed up.

A small but annoying little bugger.



Posted on 28 Oct 2008, 8:36 by BarryK
RE: BootManager
happypuppy,
Huh? That one was solved prior to release of 4.1.1rc. Are you actually testing 4.1.1rc?