On Wed, 28 Jan 2015 15:45:30 +1100, Adam Carter wrote:
> > (x11-base/xorg-server-1.13.4-r1:0/1.13.4::gentoo, installed) pulled
> > in by x11-base/xorg-server:0/1.13.4= required by
> > (x11-drivers/xf86-input-mouse-1.9.0:0/0::gentoo, installed)
> >^^
> >
On 01/28/2015 12:07 AM, Jan Sever wrote:
I found the bugzilla:
https://bugs.gentoo.org/show_bug.cgi?id=510340
So marking as SOLVED.
Thank you,
Jan Sever
P.S. Btw. poli in politics is from latin word polis = a place, not poly = many.
But it's a nice parallel.
Both a greek words, not latin.
p
On 01/27/2015 11:48 PM, Neil Bothwick wrote:
> On Tue, 27 Jan 2015 23:07:15 +0100 (CET), Jan Sever wrote:
>> P.S. Btw. poli in politics is from latin word polis = a place, not poly
>> = many. But it's a nice parallel.
>
> Yes, and a tic is a nervous twitch, the blood sucking parasite is a tick,
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28.01.2015 01:36, Neil Bothwick wrote:
> On Wed, 28 Jan 2015 00:40:32 +0100, Stefan G. Weichinger wrote:
>
>>> No need for chainloading with UEFI. Set Gummiboot as the
>>> default boot option and hold down Esc (or whichever key your
>>> motherboard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This worked now :
# grub2-install --target=x86_64-efi --efi-directory=/boot/efi
cleaning up the entries ... I get
# grub2-install --target=x86_64-efi --efi-directory=/boot/efi
Installing for x86_64-efi platform.
efibootmgr: Could not set variable B
On Wed, Jan 28, 2015 at 1:23 PM, Stefan G. Weichinger wrote:
> On 28.01.2015 01:36, Neil Bothwick wrote:
>> On Wed, 28 Jan 2015 00:40:32 +0100, Stefan G. Weichinger wrote:
No need for chainloading with UEFI. Set Gummiboot as the
default boot option and hold down Esc (or whichever ke
On 28.01.2015 19:38, Tom H wrote:
> Try to add '--efi-directory=/boot' to your grub-install invocation
> although I wonder whether grub-mkconfig will find your kernels and
> initramfs's if they aren't in the root of '/boot'.
Thanks. Got it already ->
# rm /sys/firmware/efi/efivars/dump-type0-*
On Sat, Jan 24, 2015 at 10:34 AM, Marc Stürmer wrote:
> Am 22.01.2015 um 19:06 schrieb Tom H:
>>
>> Sure. My point was that anyone can claim that systemd is (un)popular
>> in the embedded space.
>
> I don't know if it is popular; in embedded systems though the last thing you
> need are fast moving
On 28.01.2015 19:44, Stefan G. Weichinger wrote:
> So now "Linux Boot Manager" is gummiboot ... and grub is grub ;)
And for the records:
renaming "Linux Boot Manager" to "gummiboot" was done by:
# efibootmgr -b -B
# efibootmgr -c -L "gummiboot"
nice!
On Tue, Jan 27, 2015 at 5:31 PM, Mick wrote:
>
> ... and if you have no need for multi-booting then the kernel efi stub is very
> simple to configure and still works reliably (with openrc and no initrd here).
> No need to install a separate boot manager.
It's not just multi-booting that might nee
On 28.01.2015 19:50, Stefan G. Weichinger wrote:
> On 28.01.2015 19:44, Stefan G. Weichinger wrote:
>
>> So now "Linux Boot Manager" is gummiboot ... and grub is grub ;)
>
> And for the records:
>
> renaming "Linux Boot Manager" to "gummiboot" was done by:
>
> # efibootmgr -b -B
>
> # efi
On 01/28/2015 05:12 PM, Jan Sever wrote:
On 01/28/2015 1:24 AM, Thanasis wrote:
Both a greek words, not latin.
polis = city
poly = many/much
Thanks for correcting, I don't know why I had fixed in mind that polis is from
latin and poly from greek. But I thought polis should be a city and won
On 01/28/2015 08:06 PM, Thanasis wrote:
> On 01/28/2015 05:12 PM, Jan Sever wrote:
>> On 01/28/2015 1:24 AM, Thanasis wrote:
>>> Both a greek words, not latin.
>>> polis = city
>>> poly = many/much
>>
>> Thanks for correcting, I don't know why I had fixed in mind that polis is
>> from
>> latin a
On Wed, Jan 28, 2015 at 2:02 PM, Stefan G. Weichinger wrote:
> On 28.01.2015 19:50, Stefan G. Weichinger wrote:
>> On 28.01.2015 19:44, Stefan G. Weichinger wrote:
>>
>>> So now "Linux Boot Manager" is gummiboot ... and grub is grub ;)
>>
>> And for the records:
>>
>> renaming "Linux Boot Manager
On 28.01.2015 20:47, Tom H wrote:
> On Wed, Jan 28, 2015 at 2:02 PM, Stefan G. Weichinger wrote:
>> On 28.01.2015 19:50, Stefan G. Weichinger wrote:
>>> On 28.01.2015 19:44, Stefan G. Weichinger wrote:
>>>
So now "Linux Boot Manager" is gummiboot ... and grub is grub ;)
>>>
>>> And for the r
On 28.01.2015 21:31, Stefan G. Weichinger wrote:
> My command lead to a non-booting machine ... the gummiboot-entry was
> removed from UEFI.
tried your command and rebooted, worked, thanks!
I now have:
# efibootmgr
BootCurrent: 0008
Timeout: 0 seconds
BootOrder: 0008,,0001,0002,0003,0004,00
On 28.01.2015 21:36, Tom H wrote:
>> My command lead to a non-booting machine ... the gummiboot-entry was
>> removed from UEFI.
>
> But IIRC the 'tree' output that you'd posted, you shouldn't have the
> leading '\EFI'.
the "EFI" is under /boot/efi
from my trial and error today ->
# ls -l /boo
On Wed, Jan 28, 2015 at 3:31 PM, Stefan G. Weichinger wrote:
> On 28.01.2015 20:47, Tom H wrote:
>> On Wed, Jan 28, 2015 at 2:02 PM, Stefan G. Weichinger wrote:
>>> On 28.01.2015 19:50, Stefan G. Weichinger wrote:
On 28.01.2015 19:44, Stefan G. Weichinger wrote:
> So now "Linux Boot
On Wed, 28 Jan 2015 21:34:31 +0100, Stefan G. Weichinger wrote:
> Would you mind sharing the tree of your /boot ... ?
> I tried booting grub and it didn't work yet.
To answer this and your previous question. I already had a 1 GB ESP
mounted at /boot. Grub's files live in /boot/EFI/GRUB2.
--
Ne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28.01.2015 21:42, Neil Bothwick wrote:
> On Wed, 28 Jan 2015 21:34:31 +0100, Stefan G. Weichinger wrote:
>
>> Would you mind sharing the tree of your /boot ... ? I tried
>> booting grub and it didn't work yet.
>
> To answer this and your previous
On Wed, 28 Jan 2015 21:50:19 +0100, Stefan G. Weichinger wrote:
> > To answer this and your previous question. I already had a 1 GB
> > ESP mounted at /boot. Grub's files live in /boot/EFI/GRUB2.
>
> hmm. No luck here so far with chosing "grub_uefi".
> It skips to gummiboot somehow.
>
>
> # e
On Tue, Jan 27, 2015 at 7:25 PM, Philip Webb wrote:
>
> I'm running 2.19-r1 , installed 140802 ; vulnerable are < 2.18 .
>
> Linux systems are at risk only when admins don't keep versions upto-date.
Unless the patch was backported, distros like debian stable are
potentially vulnerable. Gentoo sh
On Wed, Jan 28, 2015 at 3:34 PM, Stefan G. Weichinger wrote:
> On 28.01.2015 21:31, Stefan G. Weichinger wrote:
>> My command lead to a non-booting machine ... the gummiboot-entry was
>> removed from UEFI.
>
> tried your command and rebooted, worked, thanks!
You're welcome.
> Would you mind s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28.01.2015 22:16, Neil Bothwick wrote:
> Which could be because Grub can't find it's files. It installed
> them in /boot/EFI/GRUB2 here.
>
> % ls -1 /boot/EFI/**/*.efi /boot/EFI/Boot/bootx64.efi
> /boot/EFI/GRUB2/grubx64.efi /boot/EFI/GRUB2/x86_6
On 28.01.2015 22:32, Tom H wrote:
> On Wed, Jan 28, 2015 at 3:34 PM, Stefan G. Weichinger wrote:
>> On 28.01.2015 21:31, Stefan G. Weichinger wrote:
>
>
>>> My command lead to a non-booting machine ... the gummiboot-entry was
>>> removed from UEFI.
>>
>> tried your command and rebooted, worked,
On Wed, Jan 28, 2015 at 3:38 PM, Stefan G. Weichinger wrote:
> On 28.01.2015 21:36, Tom H wrote:
>>> My command lead to a non-booting machine ... the gummiboot-entry was
>>> removed from UEFI.
>>
>> But IIRC the 'tree' output that you'd posted, you shouldn't have the
>> leading '\EFI'.
>
> the "
On 28.01.2015 22:37, Stefan G. Weichinger wrote:
> thanks, I will go through this asap (hopefully tomorrow).
> Just in case someone else is motivated right now ;-)
>
> -> mine (with definitely too much grub-content in there)
should I go for it and format the ESP ... remount and re-install both
g
On 28.01.2015 22:55, Tom H wrote:
> You need a 'grub.cfg' in '/boot/efi/EFI/grub_uefi'.
>
> I've deleted your email with the 'tree' output. I'm going to have to
> look it up in the archives because you shouldn't have 'efi' in your
> path if the ESP mountpoint is '/boot'.
forget the old mail.
I
On Wed, Jan 28, 2015 at 5:20 PM, Stefan G. Weichinger wrote:
> I rm`ed the ESP and started over.
>
> gummiboot boots fine again.
>
> I added some entries to /etc/grub.d/40_custom
> (some pointers to isos etc)
>
> and ran
>
> grub2-mkconfig -o /boot/efi/EFI/grub_uefi/grub.cfg
>
> When I chose gru
On 28.01.2015 23:51, Tom H wrote:
> Why two EFIs?
>
> One of them's unnecessary but if you want to have both, you have to
> have them both in the efibootmgr invocation.
I don't know why.
What I did:
cd /boot
rm -fr *
gummiboot install
grub2-install --target=x86_64-efi --efi-directory=/boot/efi
Alec Ten Harmsel alectenharmsel.com> writes:
> Assuming that disks are formatted, a stage3 has been freshly extracted,
> bossman is installed, and the role/config files are on a mounted
> filesystem, it should be similar to the role below:
I think the list needs to be expanded, generically firs
Yesterday I installed 4GB more of RAM in this machine for a total of 8GB, and
the machine soon began random segfaulting and even a kernel crash or two, so
obviously I suspected the new RAM was faulty.
I let memtest86+ run overnight and it found zero memory errors. Today I
exchanged the new RAM any
Howdy,
So I was reading PGO (Planet.Gentoo.org) and Patrick's post
got thinking. Yep, X was set in make.conf, like I have done
for a very long time on any gentoo "workstation". Now it may be
time to rethink this flag. The gist of what I understand is that
X is set, per profile, if appropriate. On
Philip Webb ca.inter.net> writes:
>
> 150127 Joseph wrote:
> > Does anybody know more about this "security flaw
> > in the open-source Linux GNU C Library" :
http://www.theglobeandmail.com/technology/linux-makers-release-patch-to-thwart-new-ghost-cyber-threat/article22662060/?cmpid=rss1
>
> Acc
On 01/27/2015 02:48 PM, Neil Bothwick wrote:
> but when did jokes have to be linguistically accurate?
When they're being compiled, silly.
> The preferred option is to use x11-drivers/xf86-input-evdev and remove
> the separate mouse and keyboard drivers.
>
>
OP, you will need CONFIG_INPUT_EVDEV enabled in your kernel, but the ebuild
will notify you if its not enabled.
On 28/01/2015 01:28, walt wrote:
> Yesterday I installed 4GB more of RAM in this machine for a total of 8GB, and
> the machine soon began random segfaulting and even a kernel crash or two, so
> obviously I suspected the new RAM was faulty.
>
> I let memtest86+ run overnight and it found zero memor
On 27/01/2015 20:54, James wrote:
> Howdy,
>
>
> So I was reading PGO (Planet.Gentoo.org) and Patrick's post
> got thinking. Yep, X was set in make.conf, like I have done
> for a very long time on any gentoo "workstation". Now it may be
> time to rethink this flag. The gist of what I understand i
On Tue, 27 Jan 2015 15:10:12 -0800, walt wrote:
> On 01/27/2015 02:48 PM, Neil Bothwick wrote:
> > but when did jokes have to be linguistically accurate?
>
> When they're being compiled, silly.
I never compile my own taglines, I let someone else do that and then
steal them ;-)
--
Neil Bothw
Hi folks,
has anybody experiences with 4k monitors and the open source ATI video
driver?
I wanna buy a LG 31MU97-B monitor. My GPUs will be a Sapphire Radeon R7
250E and in a second machine a Sapphire Vapor-X R9 280X.
Does anybody know if the xf86-video-ati driver is capable to handle
such high
40 matches
Mail list logo
