Re: [gentoo-user] Building a new root for my Gentoo: Permission denied?
On 14.02.2017 03:12, meino.cra...@gmx.de wrote:
> Johannes Rosenberger [17-02-14 02:43]:
>> On 13.02.2017 19:20, meino.cra...@gmx.de wrote:
>>> Johannes Rosenberger [17-02-13 19:04]:
On 13.02.2017 17:57, meino.cra...@gmx.de wrote:
> Hogren [17-02-13 17:06]:
>> On 13/02/2017 04:42, meino.cra...@gmx.de wrote:
>>> Hi,
>>>
>>> got a mysterious error message this morning (still building a new
>>> root...)
>>>
>>> One of the updates was gnutls:
>>> It ends with:
>>> ...
>>> checking for i686-pc-linux-gnu-pkg-config...
>>> /usr/bin/i686-pc-linux-gnu-pkg-config
>>> checking pkg-config is at least version 0.9.0...
>>> /var/tmp/portage/net-libs/gnutls-3.5.9/work/gnutls-3.5.9/configure:
>>> line 5020: /usr/bin/i686-pc-linux-gnu-pkg-config: Permission denied
>>> no
>>> checking for i686-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc -m32
>>> checking whether the C compiler works... yes
>>> checking for C compiler default output file name... a.out
>>> checking for suffix of executables...
>>> checking whether we are cross compiling... configure: error: in
>>> `/var/tmp/portage/net-libs/gnutls-3.5.9/work/gnutls-3.5.9-abi_x86_32.x86':
>>> configure: error: cannot run C compiled programs.
>>> If you meant to cross compile, use `--host'.
>>> See `config.log' for more details
>>> ...
>>>
>>> I tried:
>>> computer# ldd /usr/bin/i686-pc-linux-gnu-pkg-config
>>> not a dynamic executable
>>> computer# /usr/bin/i686-pc-linux-gnu-pkg-config
>>> zsh: permission denied: /usr/bin/i686-pc-linux-gnu-pkg-config
>>>
>>> computer# file /usr/bin/i686-pc-linux-gnu-pkg-config
>>> /usr/bin/i686-pc-linux-gnu-pkg-config: ELF 32-bit LSB executable, Intel
>>> 80386, version 1 (SYSV), dynamically linked, interpreter
>>> /lib/ld-linux.so.2, for GNU/Linux 2.6.32, stripped, with debug_info
>>>
>>> I choosed multilib right from the beginning of this adventure ...
>>>
>>> How can I check, whether the problem is caysed by gnutls or by the
>>> system setup (regarding 32bit)?
>>>
>>> Cheers
>>> Meino
>>>
>>>
>>>
>>>
>>>
>> Hello,
>>
>> Can you give us more details of what do you want to do, what do you
>> already do, etc.
>>
>> Does /usr/bin/i686-pc-linux-gnu-pkg-config have the x (executable)
>> permission ? (ls -l /usr/bin/i686-pc-linux-gnu-pkg-config)
>>
>>
>>
>> Hogren
>>
>>
>>
>>
> More mysterious hickups:
>
Regenerating /etc/ld.so.cache...
> /sbin/ldconfig: File /lib64/ld-linux.so.2 is empty, not checked.
>
> Did it screwed up my new root?
>
> Cheers
> Meino
>
>
>
>
Maybe. But maybe it is fixable. /lib64/ld-linux.so.2 is a symlink to
glibc. But glibc cannot be wholly broken because if it were, then
nothing would work at all.
I'd first investigate if only the symlink needs to be fixed (should
point to /lib/ld-.so).
Have you updated glibc recently?Or any other important package/package
from @system?
Have you tried if 'revdep-rebuild' finds any broken libraries?
If glibc is really broken you can
1. chroot into a stage3
2. build a binpkg (type 'quickpkg glibc')
3. copy the binpkg from
'/usr/portage/packages/sys-libs/glibc-*.tbz2' in the stage3 to
the same directory in your new root
4. install the binary glibc ('emerge ')
Then you should have a clean glibc install.
If you suspect an update of breaking anything you can always build
binary packages ahead. They are built from the installed package, so you
don't have any additional compiling. Then you can roll back quickly if
anything is damaged.
If you have a working glibc then you could also try re-emerging pkg-config.
Regards
Johannes
>>> Hi Johannes,
>>>
>>> thanks for your offered help! :)
>>>
>>> I fixed that symlink but I ran into more weird problems... :(
>>> Normally I alway run a revdep-rebuild cycle after each
>>> update...
>>>
>>> How did you set ABI_X86 in make.conf?
>>> Do you use multilib or a pure 64bit setup?
>>>
>>> Cheers
>>> Meino
>>>
>> Hi Meino,
>>
>> you are welcome!
>>
>> With the portage FEATURE 'preserve-libs' (active by default) you don't
>> need to revep-rebuild, normally. Just emerge @preserved-rebuild after
>> every update.
>>
>> Does pkg-config work, now? Can you describe your "weird problems"? Have
>> you emerged any potentially broken and important (e.g. from @system)
>> packages recently?
>>
>> Since I use a pure 64bit setup with abi_x86_32 activated selectively for
>> 399 packages (mostly graphics related, because i still have flash
>> installed), i have no ABI_X86 var in my make.conf but use a pure amd64
>> profile (where this var is set).
>> What
Re: [gentoo-user] Re: xorg wiki and graphics drivers
Harry Putnam wrote: Willie Mattthews writes: Not sure I'm following you here. THe guest addtions come with the Vbox and I've already installed them. This is a windows 10 host and the vbox is the one installable on windows. This is version 5.1.14 Guest additinos have nothing to do with gentoo kernel config. What I'm asking about it setting up a kernel for gentoo os preparatory to installing X. As described in the Xorg gentoo wiki. Vbox vm's need drivers like any other os. I'm asking which driver works with the vbox graphics adapter. And how to get a hi-res frame buffer using kernel KMS. I've never done that (building kernel for a VM) so can't offer a solution but in my Lubuntu VM the list of modules does not seem to include a specific driver for the Windows Host graphic card (NVidia NVS3100); there is instead a vboxvideo module and a generic drm_kms_helper. $ lsmod Module Size Used by isofs 40960 1 arc4 16384 0 md416384 0 nls_utf8 16384 3 cifs 638976 4 fscache61440 1 cifs vboxsf 45056 1 snd_intel8x0 40960 1 crct10dif_pclmul 16384 0 snd_ac97_codec131072 1 snd_intel8x0 crc32_pclmul 16384 0 ac97_bus 16384 1 snd_ac97_codec ghash_clmulni_intel16384 0 snd_pcm 106496 2 snd_ac97_codec,snd_intel8x0 aesni_intel 167936 0 ppdev 20480 0 aes_x86_64 20480 1 aesni_intel lrw16384 1 aesni_intel snd_seq_midi 16384 0 snd_seq_midi_event 16384 1 snd_seq_midi gf128mul 16384 1 lrw snd_rawmidi32768 1 snd_seq_midi glue_helper16384 1 aesni_intel snd_seq69632 2 snd_seq_midi_event,snd_seq_midi ablk_helper16384 1 aesni_intel input_leds 16384 0 snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi serio_raw 16384 0 joydev 20480 0 cryptd 20480 3 ghash_clmulni_intel,aesni_intel,ablk_helper snd_timer 32768 2 snd_pcm,snd_seq snd81920 9 snd_ac97_codec,snd_intel8x0,snd_timer,snd_pcm,snd_seq,snd_rawmidi,snd_seq_device mac_hid16384 0 8250_fintek16384 0 i2c_piix4 24576 0 parport_pc 32768 0 soundcore 16384 1 snd parport49152 2 ppdev,parport_pc autofs440960 2 hid_generic16384 0 usbhid 49152 0 hid 118784 2 hid_generic,usbhid vboxvideo 49152 2 psmouse 131072 0 ttm94208 1 vboxvideo ahci 36864 2 drm_kms_helper155648 1 vboxvideo libahci32768 1 ahci syscopyarea16384 2 drm_kms_helper,vboxvideo sysfillrect16384 2 drm_kms_helper,vboxvideo sysimgblt 16384 2 drm_kms_helper,vboxvideo fjes 28672 0 fb_sys_fops16384 1 drm_kms_helper video 40960 0 drm 364544 5 ttm,drm_kms_helper,vboxvideo e1000 135168 0 vboxguest 282624 6 vboxsf,vboxvideo pata_acpi 16384 0 bye, raffaele
[gentoo-user] custom kernel with nvidia-drivers
Time ago when I upgraded nvidia-drivers from 295 to 3xx series there was no way to start X, it would crash immediately with my custom built kernel. After many tests I switched to a kernel config taken from a live CD which worked (and still works) fine with the 3xx nvidia-drivers but pulls in a lot of stuff don't think I really need. I started to remove kernel options one by one to go back to a custom kernel but that is a painful road. Is there a minimal set of kernel options required to run the nvidia-driver documented somewhere? The gentoo wiki suggests to remove framebuffer, DRM, noveau but apparently that is not sufficient. The current graphic board is a GTX750-based, if it matters. thanks, raffaele
Re: [gentoo-user] custom kernel with nvidia-drivers
On Tue, Feb 14, 2017 at 12:33 PM, Raffaele Belardi
wrote:
> Time ago when I upgraded nvidia-drivers from 295 to 3xx series there was no
> way to start X, it would crash immediately with my custom built kernel.
> After many tests I switched to a kernel config taken from a live CD which
> worked (and still works) fine with the 3xx nvidia-drivers but pulls in a lot
> of stuff don't think I really need. I started to remove kernel options one
> by one to go back to a custom kernel but that is a painful road.
>
> Is there a minimal set of kernel options required to run the nvidia-driver
> documented somewhere? The gentoo wiki suggests to remove framebuffer, DRM,
> noveau but apparently that is not sufficient.
>
> The current graphic board is a GTX750-based, if it matters.
>
> thanks,
>
> raffaele
>
As far as generating a custom config file based on what modules are
loaded, you could try "make localmodconfig":
It's purpose is described here,
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/plain/README?id=refs/tags/v4.9.9:
Create a config based on current config and loaded modules (lsmod).
Disables any module option that is not needed for the loaded modules.
To generate a custom config for a given architecture, "make defconfig"
might be a good way to start.
Create a ./.config file by using the default symbol values from either
arch/$ARCH/defconfig or arch/$ARCH/configs/${PLATFORM}_defconfig,
depending on the architecture.
I personally found the Gentoo wiki article that describes the initial
kernel configuration as well as which kernel options to set for my
nvidia card to be a good foundation to build upon.
Hope this makes sense.
Re: [gentoo-user] Re: xorg wiki and graphics drivers
On 02/14/17 07:30, Raffaele Belardi wrote: Harry Putnam wrote: Willie Mattthews writes: Not sure I'm following you here. THe guest addtions come with the Vbox and I've already installed them. This is a windows 10 host and the vbox is the one installable on windows. This is version 5.1.14 Guest additinos have nothing to do with gentoo kernel config. What I'm asking about it setting up a kernel for gentoo os preparatory to installing X. As described in the Xorg gentoo wiki. Vbox vm's need drivers like any other os. I'm asking which driver works with the vbox graphics adapter. x11-drivers/xf86-video-virtualbox I do not know what you need for the hi-res frame buffer using kernel KMS. ---snipped--- -- Urs
Re: [gentoo-user] systemd - pulled IN "can not win" :-/
disable systemd via package mask; https://github.com/dantrell/gentoo-project-gnome-without-systemd/blob/master/HACKING.md#differences-between-gnome-profiles user flag settings On Feb 10, 2017 6:02 AM, "Alan McKinnon" wrote: > On 10/02/2017 06:15, the...@sys-concept.com wrote: > > On 02/09/2017 08:37 PM, the...@sys-concept.com wrote: > >> On 02/09/2017 08:30 PM, the...@sys-concept.com wrote: > >>> I have in > >>> USE="gnome -qt4 -hal -arts -berkdb X qtk -qt3 -kde dvd alsa cdr cups > apache2 ssl foomaticdb ppds mysql -acl \ > >>> java tiff png usb scanner gimp gimpprint cgi fam nptl truetype > kpathsea type1 opengl tetex spell consolekit dbus policykit -systemd" > >>> > >>> But some application managed to pull it IN. > >>> How to fix this blockage? > >>> > > [snip] > > > > Solved. libreoffice-bin was pulling "systemd". I was trying to save > > time on emerge. > > > > -- > > Thelma > > > > > Every time you fins yourself asking these questions: > > > But some application managed to pull it IN. > > How to fix this blockage? > > ALWAYS run emerge with -t option and the output will give the answer you > seek. > > Most replies on this list will ask you do it, so just get in the habit > of doing it yourself > > > -- > Alan McKinnon > alan.mckin...@gmail.com > > >
Re: [gentoo-user] WARNING: Crucial MX300 drives SUUUUUCK!!!!
Mick wrote: > On Tuesday 14 Feb 2017 01:51:01 wabe wrote: > > Mick wrote: > > > > Have you noticed a difference between mounting partitions on them > > > with the discard option, Vs running fstrim on a cron job? > > > > I noticed a big performance impact with my old Corsair 60GB SSD > > (Force3 IIRC) when I used the discard option in fstab. So I decided > > to use the fstrim command instead, before I did my weekly backups. > > The fstrim command always needed about 10 minutes or so to complete > > its job. > > > > About 1 year ago I replaced the Corsair with a Samsung SSD 850 PRO. > > With this device I did not notice a performance impact when the > > discard option is enabled and so I decided to use it. > > Btw: On the Samsung SSDs the fstrim command only needs a second or > > so to do its job. > > > > I never used a benchmark program to check if there is really no > > difference. But at least I don't notice any in my every day use. > > > > My old Corsair SSD (bought it in 2011) is still in use as swap > > space device in my Win7 machine (together with a SSD 850 PRO as > > system device). Before that, I used it as system disk on my gentoo > > machine. I also used it for my users mail and thumbnail directories > > and also for /log, /tmp, /var and the whole portage tree. Before > > I upgraded my gentoo machine to 16GB RAM I also used the SSD for > > portages temporary files. So it was really in heavy use. And is > > still running without problems. > > Before I installed the Corsair SSD into my Win machine, I used > > fstrim to increase the reserved space to 50%. I hope that it will > > run for at least another 6 years. ;-) > > > > -- > > Regards > > wabe > > Thanks wabe, this is really interesting. I was using discard and > can't say I noticed any performance penalty on the OCZ drive. I > removed it and set up a fstrim cron job and suddenly there is a major > I/O bottleneck when the cron job runs. Perhaps I should be running > it more often ... I only used fstrim in single user mode before I made my weekly backup. I can imagine that it will cause a I/O bottleneck while it runs. P.S.: I wrote by mistake, that I used fstrim to reserve free space on the drives. Actually I used hdparm for that. -- Regards wabe
[gentoo-user] package.provided?
Setup: Installing X on Vbox vm runnning gentoo (amd64 not strict). Host is win10 (64bit) Installing the xorg-server is calling for the installation of app-emulation/virtualbox-guest-additions-5.0.32 However, my version of vbox is for a windows host (5.1.14). And actually has the guest additions for that version already installed. Also before I noticed what was getting installed emerge had tried and failed to install the cited above package. I noticed the version that matches my vbox version (5.1.14) is available but masked unless setting ~amd64. I'm trying for a stable setup so, put this in /etc/portage/package.accept_keywords: =app-emulation/virtualbox-guest-additions-5.1.14 ~amd64 I tried to emerge it directly with: emerge app-emulation/virtualbox-guest-additions And sure enough emerge selected the right version but again the install failed. I did not understand the failure from the build log. But since I have the proper version and am able to install it with the regular method vbox expects (mount the additions and install with sh VBoxLinuxAdditions.run And since that method uses the currently installed kernel for its installation. Seems I can just reinstall the addtions using that method and tell gentoo about it with package.provided. Ok, `man portage' does not appear to mention where that file should reside. Googling about it I find /etc/portage/profile is mentioned. Is that still correct? I ask because I put /etc/portage/profile/package.provided: =app-emulation/virtualbox-guest-additions-5.0.32 (removed the prior /etc/portage/package.accept_keywords/ virtualbox-guest-additions: =app-emulation/virtualbox-guest-additions-5.1.14 ~amd64) in place, but emerge still tries to install it so, either the syntax if faulty or the location is, I guess. I moved package.provided to /etc/portage/package.provided but still emerge trys to install the guest-additions. Can anyone offer suggestions about this... is it even the right way to proceed?
Re: [gentoo-user] package.provided?
On 14.02.2017 16:09, Harry Putnam wrote: > Setup: > >Installing X on Vbox vm runnning gentoo (amd64 not strict). Host >is win10 (64bit) > > Installing the xorg-server is calling for the installation of > app-emulation/virtualbox-guest-additions-5.0.32 > > However, my version of vbox is for a windows host (5.1.14). And > actually has the guest additions for that version already installed. > > Also before I noticed what was getting installed emerge had tried and > failed to install the cited above package. > > I noticed the version that matches my vbox version (5.1.14) is > available but masked unless setting ~amd64. I'm trying for a stable > setup so, put this in /etc/portage/package.accept_keywords: > > =app-emulation/virtualbox-guest-additions-5.1.14 ~amd64 > > I tried to emerge it directly with: >emerge app-emulation/virtualbox-guest-additions > > And sure enough emerge selected the right version but again the > install failed. I did not understand the failure from the build log. > > But since I have the proper version and am able to install it with the > regular method vbox expects (mount the additions and install with > > sh VBoxLinuxAdditions.run > > And since that method uses the currently installed kernel for its > installation. Seems I can just reinstall the addtions using that > method and tell gentoo about it with package.provided. > > Ok, `man portage' does not appear to mention where that file should > reside. Googling about it I find /etc/portage/profile is mentioned. > Is that still correct? > > I ask because I put /etc/portage/profile/package.provided: > > =app-emulation/virtualbox-guest-additions-5.0.32 > > (removed the prior /etc/portage/package.accept_keywords/ > virtualbox-guest-additions: > =app-emulation/virtualbox-guest-additions-5.1.14 ~amd64) > > in place, but emerge still tries to install it so, either the syntax > if faulty or the location is, I guess. > > I moved package.provided to /etc/portage/package.provided but still > emerge trys to install the guest-additions. > > Can anyone offer suggestions about this... is it even the right way to > proceed? > > Hello! I have portage-2.3.3 installed and in my portage manpage it is mentioned: The file shall reside in etc/(make.profile|portage/(make.)?profile) and the syntax is /- without the '=' in the front. Greetz Johannes
Re: [gentoo-user] package.provided?
Harry Putnam wrote:
Setup:
Installing X on Vbox vm runnning gentoo (amd64 not strict). Host
is win10 (64bit)
Installing the xorg-server is calling for the installation of
app-emulation/virtualbox-guest-additions-5.0.32
However, my version of vbox is for a windows host (5.1.14). And
actually has the guest additions for that version already installed.
Also before I noticed what was getting installed emerge had tried and
failed to install the cited above package.
I noticed the version that matches my vbox version (5.1.14) is
available but masked unless setting ~amd64. I'm trying for a stable
setup so, put this in /etc/portage/package.accept_keywords:
=app-emulation/virtualbox-guest-additions-5.1.14 ~amd64
I tried to emerge it directly with:
emerge app-emulation/virtualbox-guest-additions
And sure enough emerge selected the right version but again the
install failed. I did not understand the failure from the build log.
But since I have the proper version and am able to install it with the
regular method vbox expects (mount the additions and install with
sh VBoxLinuxAdditions.run
And since that method uses the currently installed kernel for its
installation. Seems I can just reinstall the addtions using that
method and tell gentoo about it with package.provided.
Again no solution from me, but looking at the virtualbox-guest-additions-5.1.14.ebuild
there is a postinst log which you probably did not see due to the emerge failure, that
suggests a number of operations required to make the guest additions work properly:
elog "Please add users to the \"vboxguest\" group so they can"
elog "benefit from seamless mode, auto-resize and clipboard."
elog ""
elog "The vboxsf group has been added to make automount services work."
elog "These services are part of the shared folders support."
elog ""
elog "Please add:"
elog "/etc/init.d/${PN}"
elog "to the default runlevel in order to start"
elog "needed services."
elog "To use the VirtualBox X driver, use the following"
elog "file as your /etc/X11/xorg.conf:"
elog "/usr/share/doc/${PF}/xorg.conf.vbox"
elog ""
elog "Also make sure you use the Mesa library for OpenGL:"
elog "eselect opengl set xorg-x11"
elog ""
elog "An autostart .desktop file has been installed to start"
elog "VBoxClient in desktop sessions."
elog ""
elog "You can mount shared folders with:"
elog "mount -t vboxsf "
elog ""
elog "Warning:"
elog "this ebuild is only needed if you are running gentoo"
elog "inside a VirtualBox Virtual Machine, you don't need"
elog "it to run VirtualBox itself."
If you did not do the above you might incur in trouble later. Apart from this if I were
you I'd try to understand why the guest-additions emerge failed. Maybe you could try to
post the ebuild log?
raffaele
[gentoo-user] xf86-video-nouveau-1.0.12" is blocking x11-base/xorg-drivers-1.18-r1
The box that I'm upgrading is giving me: [blocks B ] =x11-base/xorg-server-1.18[udev] required by (x11-drivers/xf86-input-evdev-2.10.3:0/0::gentoo, ebuild scheduled for merge) ^^ (x11-base/xorg-server-1.17.4:0/1.17.4::gentoo, installed) pulled in by
Re: [gentoo-user] xf86-video-nouveau-1.0.12" is blocking x11-base/xorg-drivers-1.18-r1
the...@sys-concept.com wrote:
> The box that I'm upgrading is giving me:
>
> [blocks B ] (" x11-base/xorg-drivers-1.18-r1)
>
> !!! Multiple package instances within a single package slot have been
> pulled !!! into the dependency graph, resulting in a slot conflict:
>
> x11-base/xorg-server:0
>
> (x11-base/xorg-server-1.18.4:0/1.18.4::gentoo, ebuild scheduled for
> merge) pulled in by
> >=x11-base/xorg-server-1.18[udev] required by
> >(x11-drivers/xf86-input-evdev-2.10.3:0/0::gentoo, ebuild
> >scheduled for merge)
> ^^
>
>
>
> (x11-base/xorg-server-1.17.4:0/1.17.4::gentoo, installed) pulled in
> by (x11-drivers/xf86-video-nouveau-1.0.11:0/0::gentoo, installed)
> ^ ^^ x11-base/xorg-server:0/1.17.4= required
> by (x11-drivers/xf86-video-nouveau-1.0.11:0/0::gentoo, installed)
>
> Normally I would just unmerge and emerge a new one:
>
> emerge -C x11-drivers/xf86-video-nouveau (1.0.11)
> and
> emerge -uq x11-drivers/xf86-video-nouveau (1.0.12)
>
> But this is a video driver my box is using, and I'm logged into it
> directly so if I unmerge the drive in use the xorg-server will crash
> and I I'll be in a login prompt, isn't it?
>
> Is it better to do this upgrade over "ssh" from another box?
You could also use a text console on the local machine.
--
Regards
wabe
Re: [gentoo-user] xf86-video-nouveau-1.0.12" is blocking x11-base/xorg-drivers-1.18-r1
the...@sys-concept.com wrote: The box that I'm upgrading is giving me: [blocks B ] ... But this is a video driver my box is using, and I'm logged into it directly so if I unmerge the drive in use the xorg-server will crash and I I'll be in a login prompt, isn't it? Is it better to do this upgrade over "ssh" from another box? The kernel will not actually delete a file if there is some user accessing it (xorg in this case) so unmerging xf86-video-nouveau should not affect the currently running graphical environment. Obviously don't reboot before re-emerging it. Let me add that I'm not completely sure of what I'm writing so be ready for ssh... raffaele
[gentoo-user] Re: package.provided?
Johannes Rosenberger writes: >> Can anyone offer suggestions about this... is it even the right way to >> proceed? >> >> > > Hello! > > I have portage-2.3.3 installed and in my portage manpage it is mentioned: > > The file shall reside in etc/(make.profile|portage/(make.)?profile) and > the syntax is > /- without the '=' in the front. Thanks for that. I'm not at all sure what that line means. something like /etc/ (then either make a directory named `profile' or one named `portage' if necessary) / (then make `profile' if necessary.) So, /etc/portage/profile/package.provided I followed a newish dictum of using the package part as a directory name. So /etc/portage/profle/package.provided/FnameAndContentHere It worked... thanks again. It worked.. still not getting everything installed but that part worked... Something else about this entry in `man portage': [...] SYNOPSIS /etc/portage/make.profile/ or /etc/make.profile/ site-specific overrides go in /etc/portage/profile/ deprecated [...] So is the plan to do away with package.provided or just relocate it?
Re: [gentoo-user] WARNING: Crucial MX300 drives SUUUUUCK!!!!
On 02/13/2017 10:25 PM, Mick wrote: > I was using discard and can't say I > noticed any performance penalty on the OCZ drive. I removed it and set up a > fstrim cron job and suddenly there is a major I/O bottleneck when the cron > job > runs. Perhaps I should be running it more often ... > Yeah, I read something that recommended weekly fstrim but it was noticeable. I found doing it more frequently (I set mine up to daily. Or was it twice a day?) it doesn't take as long. Also make sure that the job runs if it's missed. Dan
Re: [gentoo-user] WARNING: Crucial MX300 drives SUUUUUCK!!!!
On 02/13/2017 10:17 AM, Poison BL. wrote: > > I've had more than one spinning rust drive fail hard over the years as > well, though yes, you do usually have some chance of recovery from > those. Gambling on that chance by leaving a given disk as a single point > of failure is still a bad idea, spinning disk or not. The point that you > went from single-disk SSD back to raid10 makes me question why, if your > uptime requirements (even if only for your own desires on a personal > machine) justify raid10, you weren't on at least raid1 with the SSD setup. I finally got tired and replaced my old laptop with a ThinkPad P70, and boy is it so much faster than anything else I own. Compile times are crazy fast on this new laptop of mine, but it came equipped with an i7 with 8 threads and 16GB of RAM, which I'm sure helps A LOT. I'm going to get an SSD (or maybe an NVMe drive) for the new laptop and leave /home on ol' reliable rust disks. I do have backups. That's not the concern - the concern for me was turning on the PC and having it completely crap out. I used to have an SSD on my mythtv backend server, and it started behaving strangely one day. I could not log in to the console. X froze. Logged in via ssh and files appeared to be missing on the root partition. Rebooted the backend server and it was completely dead, no warnings or anything. Dan
Re: [gentoo-user] custom kernel with nvidia-drivers
On 02/14/2017 02:33 AM, Raffaele Belardi wrote: > Time ago when I upgraded nvidia-drivers from 295 to 3xx series there was > no way to start X, it would crash immediately with my custom built > kernel. After many tests I switched to a kernel config taken from a live > CD which worked (and still works) fine with the 3xx nvidia-drivers but > pulls in a lot of stuff don't think I really need. I started to remove > kernel options one by one to go back to a custom kernel but that is a > painful road. > > Is there a minimal set of kernel options required to run the > nvidia-driver documented somewhere? The gentoo wiki suggests to remove > framebuffer, DRM, noveau but apparently that is not sufficient. > > The current graphic board is a GTX750-based, if it matters. > > thanks, > > raffaele > I have: [IP-] [ ] x11-drivers/nvidia-drivers-375.26:0/375 installed with no issues with my custom kernel (I've been using custom kernels from day one using Gentoo.) I have only enabled drivers for this specific machine and I didn't have issues with X. I did forget to remove KMS support from the kernel (nvidia provides their own KMS blob, apparently) and that give me issues with framebuffer corruption at the console, but X itself worked fine. All you can do is check `lspci -k`, `lsusb`, and dmesg output and figure out what your kernel needs for your machine. Or in the case you get to the point where X won't start attach the Xorg log and the kernel .config, so that it can be looked at. With new hardware I find it easier to boot a liveCD and save its dmesg, lspci, lsusb to a USB key and use hits from it to build my own kernel, removing all the bits not needed. Dan
Re: [gentoo-user] Re: Gentoo on a Surface Pro 3?
On 02/05/2017 05:12 PM, Alex Thorne wrote: > A wiki article would be great. I'd be happy to contribute my experiences > with my Surface Pro 4 if I eventually get round to installing Gentoo on it. > I'm still plodding away at this. I found some patches to enable multitouch and some other bits but it seems the newer kernel I'm using already has parts of these patches installed, so I have to go through them one by one and update the patches to add only the bits missing. After that, I should be able to start figuring out writing a wiki article. I haven't had a lot of time in the last week or so, but I'll get around to it eventually. Dan
[gentoo-user] Re: not understanding failed build log
Setup: VBox vm running gentoo(amd64) guest on a win-10 (64bit) host Hardware: HP xw8600 - 2x Xeon CPU X5450 @ 3.00GHz - 32 GB ram Harry Putnam writes: [...] > Sorry to post the raw pile of output but last time a used a http link > to a long log someone here told me that many of you would not bother > to follow it or help. > > So here it is inlined: > > xf86-video-virtualbox-5.1.14 > > /var/tmp/portage/x11-drivers/xf86-video-virtualbox-5.1.14/temp/build.log [...] Please disregard that massive post. Once I noticed that the package it refers too: xf86-video-virtualbox Was something that comes from inside app-emulation/virtualbox-guest-additions And since I've already declared that in package.provided as something I've supplied. Then I realized I should be able to do the same thing with that package since it is already installed when I installed the guest additions from the vbox version that is housing this gentoo intall. Seems to be working ok so far.
Re: [gentoo-user] WARNING: Crucial MX300 drives SUUUUUCK!!!!
On Tue, Feb 14, 2017 at 3:46 PM, Daniel Frey wrote: > On 02/13/2017 10:17 AM, Poison BL. wrote: > > > > I've had more than one spinning rust drive fail hard over the years as > > well, though yes, you do usually have some chance of recovery from > > those. Gambling on that chance by leaving a given disk as a single point > > of failure is still a bad idea, spinning disk or not. The point that you > > went from single-disk SSD back to raid10 makes me question why, if your > > uptime requirements (even if only for your own desires on a personal > > machine) justify raid10, you weren't on at least raid1 with the SSD > setup. > > I finally got tired and replaced my old laptop with a ThinkPad P70, and > boy is it so much faster than anything else I own. Compile times are > crazy fast on this new laptop of mine, but it came equipped with an i7 > with 8 threads and 16GB of RAM, which I'm sure helps A LOT. > > I'm going to get an SSD (or maybe an NVMe drive) for the new laptop and > leave /home on ol' reliable rust disks. > > I do have backups. That's not the concern - the concern for me was > turning on the PC and having it completely crap out. > > I used to have an SSD on my mythtv backend server, and it started > behaving strangely one day. I could not log in to the console. X froze. > Logged in via ssh and files appeared to be missing on the root > partition. Rebooted the backend server and it was completely dead, no > warnings or anything. > > Dan > > > > I actually see both sides of it... as nice as it is to have a chance to recover the information from between the last backup and the death of the drive, the reduced chance of corrupt data from a silently failing (spinning) disk making it into backups is a bit of a good balancing point for me. -- Poison [BLX] Joshua M. Murphy
Re: [gentoo-user] WARNING: Crucial MX300 drives SUUUUUCK!!!!
I had a crucial SSD drive too and it failed in the warranty but as I didn't have the receipt they refused to honor it and said I was out of warranty as based on the date they sold it to the store not the day the store sold it to me. Apparently failures on my model were a very common thing due to a manufacturing defect. Thank god for backups. Bunch of jerks, don't buy from them.
Re: [gentoo-user] Re: package.provided?
On 14.02.2017 21:22, Harry Putnam wrote: > Johannes Rosenberger writes: > >>> Can anyone offer suggestions about this... is it even the right way to >>> proceed? >>> >>> >> Hello! >> >> I have portage-2.3.3 installed and in my portage manpage it is mentioned: >> >> The file shall reside in etc/(make.profile|portage/(make.)?profile) and >> the syntax is >> /- without the '=' in the front. > Thanks for that. I'm not at all sure what that line means. > > something like /etc/ (then either make a directory named `profile' or > one named `portage' if necessary) / (then make `profile' if > necessary.) That line is a regular expression (like in grep, sed, awk, vim,…): Parentheses always group something into an atom and pipes mark an alternative. '?' means that the preceding atom occurs zero or one time. So the expression means 'etc/' (I missed out the preceding slash), followed by alternatively 'make.profile' or 'portage/(make.)?profile'. The latter means 'portage/profile' with an optional 'make.' in between. As you (hopefully) see, the expression resolves to the three alternatives mentioned in the man page. > > So, /etc/portage/profile/package.provided > > I followed a newish dictum of using the package part as a directory > name. So /etc/portage/profle/package.provided/FnameAndContentHere > It worked... thanks again. I find the package.*-dirs very nice, too. Unfortunately, the tools like emerge, flaggie etc. seem to not always use the same file to write to, so the files get messed up over time. > > It worked.. still not getting everything installed but that > part worked... Well, that's not too astonishing… ;-) Especially if you do anything uncommon: I'm trying to build a musl-clang-4.0.0_rc1 system at the time, currently. And it took me some days to hack out how to let clang compile itself with incompatible symbols produced by gcc and clang… > Something else about this entry in `man portage': > > [...] > SYNOPSIS >/etc/portage/make.profile/ or /etc/make.profile/ > site-specific overrides go in /etc/portage/profile/ > deprecated > [...] > > So is the plan to do away with package.provided or just relocate it? No. "deprecated" is one of the files that reside in the profile, just like "make.profile". It marks a profile as deprecated and contains the successing profile and optionally upgrading instructions.
[gentoo-user] Perhaps add "gentoo-" in beginning of file name for iso files
When i download Gentoo Linux the file name might be called something like: livedvd-amd64-multilib-20160704.iso This might be fine if you just want that file and want to use it straight away. But lets say like i just did downloaded multiple linux distributions because i want to test them out so i have like 10-20 iso files or what ever. Then later one when i see the file name livedvd-amd64-multilib-20160704.iso i have no idea what distribution that was. The other distributions i have downloaded all seem to start with the name of the distribution in the file name. I Think Gentoo Linux is the only one yet that does not. So would it not be better to use a file name like this?: gentoo-livedvd-amd64-multilib-20160704.iso
Re: [gentoo-user] Perhaps add "gentoo-" in beginning of file name for iso files
On 15.02.2017 00:00, scootergrisen wrote: > When i download Gentoo Linux the file name might be called something > like: > livedvd-amd64-multilib-20160704.iso > > This might be fine if you just want that file and want to use it > straight away. > > But lets say like i just did downloaded multiple linux distributions > because i want to test them out so i have like 10-20 iso files or what > ever. > > Then later one when i see the file name > livedvd-amd64-multilib-20160704.iso i have no idea what distribution > that was. > > The other distributions i have downloaded all seem to start with the > name of the distribution in the file name. I Think Gentoo Linux is the > only one yet that does not. > So you can identify it uniquely. ;-) > So would it not be better to use a file name like this?: > gentoo-livedvd-amd64-multilib-20160704.iso > Could be nice. But not important. You can always run 'wget -O '. You could write a GLEP? But then, you could just file a bug/ask somebody responsible for the naming.
Re: [gentoo-user] WARNING: Crucial MX300 drives SUUUUUCK!!!!
All this raises an interesting question: How much effort is it reasonable to expect a user to undertake just to use one of these drives? I mean it's going to be very tough to argue that it should require more than "plug in -> add partitions > boogie" I mean half of what I'm hearing about how to set these up sounds like superstition based on how flash was 10 years ago. =\ I mean there needs to be a protocol where the drive communicates with the operating system what it needs, and the OS should just do it, and the user shouldn't know about it prior to running utilities on the volume/drive... It is really not reasonable to expect the user to know, understand, and actively administrate delicate tuning parameters for specific makes and models of drives and evolving tools to use these drives. Right now my drive is set up as if it were a black box that contains bits. I don't think it's reasonable for me to do anything more than that. =\ Daniel Frey wrote: > On 02/13/2017 10:25 PM, Mick wrote: >> I was using discard and can't say I >> noticed any performance penalty on the OCZ drive. I removed it and set up a >> fstrim cron job and suddenly there is a major I/O bottleneck when the cron >> job >> runs. Perhaps I should be running it more often ... >> > Yeah, I read something that recommended weekly fstrim but it was > noticeable. I found doing it more frequently (I set mine up to daily. Or > was it twice a day?) it doesn't take as long. > > Also make sure that the job runs if it's missed. -- Strange Game. The only winning move is not to play. Powers are not rights.
Re: [gentoo-user] Re: package.provided?
On Tue, 14 Feb 2017 15:22:50 -0500, Harry Putnam wrote: > Something else about this entry in `man portage': > > [...] > SYNOPSIS >/etc/portage/make.profile/ or /etc/make.profile/ > site-specific overrides go in /etc/portage/profile/ > deprecated > [...] > > So is the plan to do away with package.provided or just relocate it? You missed the blank line above deprecated. The lines below it are a list of files that can go in the profile, the first of which is called "deprecated" -- Neil Bothwick SITCOM: Single Income, Two Children, Oppressive Mortgage pgpQDUW7hso6O.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Re: package.provided?
On Tue, 14 Feb 2017 23:00:03 +0100, Johannes Rosenberger wrote: > I find the package.*-dirs very nice, too. Unfortunately, the tools like > emerge, flaggie etc. seem to not always use the same file to write to, > so the files get messed up over time. Portage always writes to the end of the last file in the directory, to make sure that its entry is not overridden by a subsequent entry. I create an empty file called zzz-auto-unmask in package.use etc. Then I can move the settings from that file to a more suitable place. -- Neil Bothwick Bus: (n.) a connector you plug money into, something like a slot machine. pgplulCBF7AXF.pgp Description: OpenPGP digital signature
Re: [gentoo-user] WARNING: Crucial MX300 drives SUUUUUCK!!!!
On Tuesday 14 Feb 2017 18:29:49 Alan Grimes wrote: > Right now my drive is set up as if it were a black box that contains bits. > I don't think it's reasonable for me to do anything more than that. =\ Well, no, but then you wouldn't, would you? Anybody else might take an interest in the health of his system. -- Regards Peter
Re: [gentoo-user] Perhaps add "gentoo-" in beginning of file name for iso files
Johannes Rosenberger wrote: > On 15.02.2017 00:00, scootergrisen wrote: >> When i download Gentoo Linux the file name might be called something >> like: >> livedvd-amd64-multilib-20160704.iso >> >> This might be fine if you just want that file and want to use it >> straight away. >> >> But lets say like i just did downloaded multiple linux distributions >> because i want to test them out so i have like 10-20 iso files or what >> ever. >> >> Then later one when i see the file name >> livedvd-amd64-multilib-20160704.iso i have no idea what distribution >> that was. >> >> The other distributions i have downloaded all seem to start with the >> name of the distribution in the file name. I Think Gentoo Linux is the >> only one yet that does not. >> > So you can identify it uniquely. ;-) >> So would it not be better to use a file name like this?: >> gentoo-livedvd-amd64-multilib-20160704.iso >> > Could be nice. But not important. > You can always run 'wget -O '. > > You could write a GLEP? But then, you could just file a bug/ask somebody > responsible for the naming. > > > Or just put each distro in a separate directory. That's how I do it here. I have Mandriva, Gentoo and Kubuntu and also keep sysrescue and Knoppix laying around as well. Dale :-) :-)
Re: [gentoo-user] WARNING: Crucial MX300 drives SUUUUUCK!!!!
On Tue, Feb 14, 2017 at 6:29 PM, Alan Grimes wrote: > All this raises an interesting question: How much effort is it > reasonable to expect a user to undertake just to use one of these > drives? I mean it's going to be very tough to argue that it should > require more than "plug in -> add partitions > boogie" I mean half of > what I'm hearing about how to set these up sounds like superstition > based on how flash was 10 years ago. =\ I mean there needs to be a > protocol where the drive communicates with the operating system what it > needs, and the OS should just do it, and the user shouldn't know about > it prior to running utilities on the volume/drive... > > It is really not reasonable to expect the user to know, understand, and > actively administrate delicate tuning parameters for specific makes and > models of drives and evolving tools to use these drives. Right now my > drive is set up as if it were a black box that contains bits. I don't > think it's reasonable for me to do anything more than that. =\ And, on the range of OSes that cater to users who don't care to know, understand, or actively administer their systems they tend to detect that it's an SSD, enable trim, and then let the user suffer with the defaults, getting better performance than a spinning disk, even if they're not getting the *most* out of their drive. For the users that *do* wish to, there's options, whether via a different OS, third party software (like Samsung Magician for their drives on Windows), or manually adjusting the settings for the drive in their OS. They do tend to 'just work', but like anything else, you don't get the best performance out of them by expecting them to just plug in and go. Even spinning disks benefit from some tweaking of filesystem parameters away from the defaults for best performance under specific workloads. -- Poison [BLX] Joshua M. Murphy
[gentoo-user] Pentoo... is it still being developed
Can any say if pentoo is still under developement?
Re: [gentoo-user] Pentoo... is it still being developed
On 02/14/2017 09:09 PM, Harry Putnam wrote: > Can any say if pentoo is still under developement? > > It looks like they have a beta from January. http://mirror.switch.ch/ftp/mirror/pentoo/Beta/Pentoo_amd64_default/ -- Willie Matthews matthews.willi...@gmail.com signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] Perhaps add "gentoo-" in beginning of file name for iso files
On Wed, Feb 15, 2017 at 7:00 AM, scootergrisen wrote: > So would it not be better to use a file name like this?: > gentoo-livedvd-amd64-multilib-20160704.iso This is the correct approach, but people here hate making changes unless it's coming from them and gives them merit. -- konsolebox
