160329 cov...@ccs.covici.com wrote:
> With 4.1.20 the nvidia drivers I am using get an invalid argument
> when trying to modprobe it. Its version 355.11-r4.
> If I try the latest version, I get modeset errors,
> although it stops giving me the invalid argument.
I had a problem with 358 + 361 , bu
Philip Webb wrote:
> 160329 cov...@ccs.covici.com wrote:
> > With 4.1.20 the nvidia drivers I am using get an invalid argument
> > when trying to modprobe it. Its version 355.11-r4.
> > If I try the latest version, I get modeset errors,
> > although it stops giving me the invalid argument.
>
>
Hi,
since companies know their usbstick internals best, they
format their drives in a way, that the performance is best.
That's why I want to make a complete image "backup" of my
new usbstick first before using it in case of needing to
reset the whole thing.
The stick is a 64GB vfat formatted
On Tue, 29 Mar 2016 01:03:14 -0400
Philip Webb wrote:
> 160328 Corbin wrote:
> > The "x11-misc/rss-glx" screensavers work just fine.
>
> I hadn't come across it before.
> If I emerge it, will it automatically be adopted by Xscreensaver ?
Yes -- after emerging it you'll see its savers in xscr
Did you do a emerge @module-rebuild after updating your kernel?
On Tue, Mar 29, 2016, 04:26 wrote:
> Philip Webb wrote:
>
> > 160329 cov...@ccs.covici.com wrote:
> > > With 4.1.20 the nvidia drivers I am using get an invalid argument
> > > when trying to modprobe it. Its version 355.11-r4.
> >
If you're gonna dd a drive you either go the same space or larger. To be
sure you get everything you can just
dd if=/dev/oldstick of=/dev/newstick
Replacing old/newstick with the correct device.
You can even keep a backup image with
dd if=/dev/oldstick of=/home/user/whateveryounamedit.img
Whic
Hi Ia,
thanks for your reply ! :)
The usbstick I want to make an initial backup is 64GB of size.
That means, I will backup mostly zeroes.
Where are the partioning/format defining on the device?
If there are only stored the beginning of the device: How
much do I need to copy?
or:
If there are t
Checkout partclone, I think it does what you're looking for.
On Tue, Mar 29, 2016, 12:19 wrote:
> Hi Ia,
>
> thanks for your reply ! :)
>
> The usbstick I want to make an initial backup is 64GB of size.
> That means, I will backup mostly zeroes.
>
> Where are the partioning/format defining on th
Hi Ian,
If I do a
eix partclone
I get
No matches found.
[1]7241 exit 1 eix -n partclone
. May be a typo... ;)
Ian Bloss [16-03-29 18:30]:
> Checkout partclone, I think it does what you're looking for.
>
> On Tue, Mar 29, 2016, 12:19 wrote:
>
> > Hi Ia,
> >
> >
On Tuesday 29 Mar 2016 18:33:01 meino.cra...@gmx.de wrote:
> Hi Ian,
>
> If I do a
>
> eix partclone
>
> I get
>
> No matches found.
> [1]7241 exit 1 eix -n partclone
>
> . May be a typo... ;)
Please try not to top-post, it confuses the flow of the thread.
Ian's suggestio
I did and nvidia was installed, but modprobe nvidia in this kernel says
invalid argument.
Ian Bloss wrote:
> Did you do a emerge @module-rebuild after updating your kernel?
>
> On Tue, Mar 29, 2016, 04:26 wrote:
>
> > Philip Webb wrote:
> >
> > > 160329 cov...@ccs.covici.com wrote:
> > > > W
Mick [16-03-29 19:12]:
> On Tuesday 29 Mar 2016 18:33:01 meino.cra...@gmx.de wrote:
> > Hi Ian,
> >
> > If I do a
> >
> > eix partclone
> >
> > I get
> >
> > No matches found.
> > [1]7241 exit 1 eix -n partclone
> >
> > . May be a typo... ;)
>
> Please try not to top-post
The USB drive should be exposed via the mass storage interface as just
plain storage. You don't need to do anything special.
Older drives needed the user to be aware of the physical layout. Now the
firmware mostly takes care of it.
R0b0t1 [16-03-29 20:12]:
> The USB drive should be exposed via the mass storage interface as just
> plain storage. You don't need to do anything special.
>
> Older drives needed the user to be aware of the physical layout. Now the
> firmware mostly takes care of it.
Hi R0b0t1
...I read this
htt
That article implies you can do special things to increase performance.
Maybe, don't care to check.
What it mentions that are widely applicable are block sizes and trimming
which are built into modern filesystems/drivers.
I had performance decrease over time but am not sure the reason he gives is
On Tuesday 29 Mar 2016 19:53:45 meino.cra...@gmx.de wrote:
> The real thing:
> The usbstick has a partition table, which was the reason to ask
> for a way to preserve it.
OK, I wasn't sure if it did.
In this case as I suggested, fdisk will show you the number and size of
partitions. minfo will
So, I want to install packages from an overlay, but only from a specific
group. In this case, the dev-qt/ group. The overlay name is "qt".
It doesn't work:
package.mask: */*::qt
package.unmask: dev-qt/*-5.6*::qt
With this, 5.6 versions are still masked.
How do I do this?
Not entirely sure what you wish. Maybe package sets?
On 29/03/16 23:21, R0b0t1 wrote:
Not entirely sure what you wish. Maybe package sets?
Not sure what *you* mean :-) How would package sets help me in masking
all packages from an overlay and then whilelist only specific ones?
On Tue, 29 Mar 2016 23:01:16 +0300, Nikos Chantziaras wrote:
> So, I want to install packages from an overlay, but only from a
> specific group. In this case, the dev-qt/ group. The overlay name is
> "qt".
Add the overlay with layman but don't add it to repos.conf. Then symlink
the dev-qt directo
They lets you do the bin-ary algebruhs with lotsa da thingies at wunce.
On 29/03/16 23:01, Nikos Chantziaras wrote:
So, I want to install packages from an overlay, but only from a specific
group. In this case, the dev-qt/ group. The overlay name is "qt".
It doesn't work:
package.mask: */*::qt
package.unmask: dev-qt/*-5.6*::qt
With this, 5.6 versions are stil
Why don't you mask versions higher than 5.7 instead?
On Tue, Mar 29, 2016, 17:00 Nikos Chantziaras wrote:
> On 29/03/16 23:01, Nikos Chantziaras wrote:
> > So, I want to install packages from an overlay, but only from a specific
> > group. In this case, the dev-qt/ group. The overlay name is "qt
Because that is already covered by:
*/*::qt
in package.mask. This masks everything from the qt overlay, including
versions of Qt higher or equal to 5.7.
I only masked >=5.7, then the other packages from the qt overlay would
not be masked. What I need is mask ALL packages in the qt overlay
On 30 March 2016 05:01:16 GMT+09:00, Nikos Chantziaras wrote:
>So, I want to install packages from an overlay, but only from a
>specific
>group. In this case, the dev-qt/ group. The overlay name is "qt".
>
>It doesn't work:
>
> package.mask: */*::qt
> package.unmask: dev-qt/*-5.6*::qt
>
>With
Mick [16-03-30 03:56]:
> On Tuesday 29 Mar 2016 19:53:45 meino.cra...@gmx.de wrote:
>
> > The real thing:
> > The usbstick has a partition table, which was the reason to ask
> > for a way to preserve it.
>
> OK, I wasn't sure if it did.
>
> In this case as I suggested, fdisk will show you the n
On Tuesday, March 29, 2016 01:56:22 PM R0b0t1 wrote:
> That article implies you can do special things to increase performance.
> Maybe, don't care to check.
>
> What it mentions that are widely applicable are block sizes and trimming
> which are built into modern filesystems/drivers.
>
> I had pe
On Wednesday 30 Mar 2016 05:28:29 meino.cra...@gmx.de wrote:
> Mick [16-03-30 03:56]:
> > On Tuesday 29 Mar 2016 19:53:45 meino.cra...@gmx.de wrote:
> > > The real thing:
> > > The usbstick has a partition table, which was the reason to ask
> > > for a way to preserve it.
> >
> > OK, I wasn't sur
28 matches
Mail list logo
