Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
new install will not boot [solved]
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
cwc
Veteran
Veteran


Joined: 20 Mar 2006
Posts: 1107
Location: Tri-Cities, WA USA

PostPosted: Sat Aug 15, 2015 10:45 pm    Post subject: new install will not boot [solved] Reply with quote

I have an athlon64 system. 4GB of ram.

I just reinstalled Gentoo with grub2
The boot loader will not recognize my root partition. (ext4)

I am going to start over.

My current partition table is:

/boot 500mb
swap 8gb
/ 200+ GB

Question? Will this work with grub2.

I rea the manual and it indicated I need a bios partition.

If that is so would I be better to have:
biosboot
/boot
swap
/

I am using gparted with the sytem rescue cd.
How is a boisboot partition created.

Thanks
_________________
Without diversity there can be no evolution:)


Last edited by cwc on Tue Aug 18, 2015 12:38 pm; edited 1 time in total
Back to top
View user's profile Send private message
skiwarz
Tux's lil' helper
Tux's lil' helper


Joined: 23 Feb 2014
Posts: 128

PostPosted: Sat Aug 15, 2015 11:08 pm    Post subject: Reply with quote

I did this last year. Here's my post and solution on it. Hopefully it helps
https://forums.gentoo.org/viewtopic-t-987448-highlight-.html
Back to top
View user's profile Send private message
ian.au
Guru
Guru


Joined: 07 Apr 2011
Posts: 434
Location: Australia

PostPosted: Sat Aug 15, 2015 11:22 pm    Post subject: Reply with quote

cwc,

These options relate to whether you are booting with efi or not. Here's an easy way to check:

When you boot sysrescuecd is it booting its initial menu with a blue background or black and white?

If it booted with a blue background, you are using legacy bios, if black and white, it's booted UEFI.
Back to top
View user's profile Send private message
skiwarz
Tux's lil' helper
Tux's lil' helper


Joined: 23 Feb 2014
Posts: 128

PostPosted: Sat Aug 15, 2015 11:27 pm    Post subject: Reply with quote

To shorten your reading, here's the guide and section I used:
https://wiki.gentoo.org/wiki/GRUB2#BIOS_with_GPT

I may or may not have had to set GRUB_PLATFORMS="pc" in /etc/portage/make.conf. I can't remember, and I don't have that computer with me. So if all the instructions in that wiki fail, you might try messing with that setting.



[edit]: Ok, so after actually READING your question... yes it will work with GRUB2. In parted, use
Code:
mkpart primary 1MB 3MB

or something really similar. Then use
Code:
set bios_grub on
to make it type ef02. Then I believe** grub should automatically detect and use it when you run grub2-install
Back to top
View user's profile Send private message
cwc
Veteran
Veteran


Joined: 20 Mar 2006
Posts: 1107
Location: Tri-Cities, WA USA

PostPosted: Sun Aug 16, 2015 12:59 pm    Post subject: Reply with quote

my system is definitely a legacy system
should i use:
3 partitions
/boot 500mb
swap 8gb
/ 200+ GB

or
partitions
4 part
biosboot
/boot
swap
/
_________________
Without diversity there can be no evolution:)
Back to top
View user's profile Send private message
ian.au
Guru
Guru


Joined: 07 Apr 2011
Posts: 434
Location: Australia

PostPosted: Sun Aug 16, 2015 2:06 pm    Post subject: Reply with quote

I'm assuming here that you selected GPT for your partition layout, although you haven't specifically said that. On your hardware, with a small hard drive, GPT format isn't going to provide you with any benefit, and may cause you unnecessary grief.

From the handbook, under the heading GPT or MBR
Quote:
Some buggy BIOSes or EFIs configured to boot in BIOS/CSM/legacy mode might also have problems with booting from GPT labeled disks. If that is the case, it might be possible to work around the problem by adding the boot/active flag on the protective MBR partition which has to be done through fdisk with the -t dos option to force it to read the partition table using the MBR format.

so you have 3 options, try the workaround there is a detailed example in the handbook at https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks#GPT_or_MBR; or,

There are utilities that can convert you back from GPT to MBR if you don't want to reinstall. gdisk on sysrescuecd can do it. I'm sorry but I don't have the time to do a walk-through of that with you, but there are good instructions from the gdisk developer here http://www.rodsbooks.com/gdisk/mbr2gpt.html#gpt2mbr

If you manage to rescue your current install, it is not mandatory to have the additional bios_boot partition with MBR, just set the boot flag as normal and grub2 will probably pick it up. I still have machines here with
Code:
Device     Boot   Start        End    Sectors  Size Id Type
/dev/sda1  *       2048      67583      65536   32M 83 Linux
/dev/sda2         67584    1116159    1048576  512M 82 Linux swap / Solaris
/dev/sda3       1116160 1953525167 1952409008  931G 83 Linux
and grub2 has no problem with them. Only caveat is that the boot sector must not start <2048

Otherwise, if you choose to reinstall - use the https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks#Alternative:_Using_fdisk_to_partition_the_disk handbook instructions and just use fdisk to create your partitions as MBR and make the grub bios partition as instructed there.
Back to top
View user's profile Send private message
cwc
Veteran
Veteran


Joined: 20 Mar 2006
Posts: 1107
Location: Tri-Cities, WA USA

PostPosted: Sun Aug 16, 2015 2:23 pm    Post subject: Reply with quote

ian.au wrote:


Otherwise, if you choose to reinstall - use the https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks#Alternative:_Using_fdisk_to_partition_the_disk handbook instructions and just use fdisk to create your partitions as MBR and make the grub bios partition as instructed there.


thanks ian.au I am going to try 4 partitions
biosboot
boot
swap
root

I'm sure I'll need more help. thanks
_________________
Without diversity there can be no evolution:)
Back to top
View user's profile Send private message
cwc
Veteran
Veteran


Joined: 20 Mar 2006
Posts: 1107
Location: Tri-Cities, WA USA

PostPosted: Sun Aug 16, 2015 3:20 pm    Post subject: Reply with quote

Partition Description
/dev/sda1 BIOS boot partition
/dev/sda2 Boot partition
/dev/sda3 Swap partition
/dev/sda4 Root partition


What file system is the BOIS boot without efi?

Code:

Command (m for help): t
Selected partition 1
Hex code (type L to list codes): l

 0  Empty           24  NEC DOS         81  Minix / old Lin bf  Solaris       
 1  FAT12           27  Hidden NTFS Win 82  Linux swap / So c1  DRDOS/sec (FAT-
 2  XENIX root      39  Plan 9          83  Linux           c4  DRDOS/sec (FAT-
 3  XENIX usr       3c  PartitionMagic  84  OS/2 hidden C:  c6  DRDOS/sec (FAT-
 4  FAT16 <32M      40  Venix 80286     85  Linux extended  c7  Syrinx         
 5  Extended        41  PPC PReP Boot   86  NTFS volume set da  Non-FS data   
 6  FAT16           42  SFS             87  NTFS volume set db  CP/M / CTOS / .
 7  HPFS/NTFS/exFAT 4d  QNX4.x          88  Linux plaintext de  Dell Utility   
 8  AIX             4e  QNX4.x 2nd part 8e  Linux LVM       df  BootIt         
 9  AIX bootable    4f  QNX4.x 3rd part 93  Amoeba          e1  DOS access     
 a  OS/2 Boot Manag 50  OnTrack DM      94  Amoeba BBT      e3  DOS R/O       
 b  W95 FAT32       51  OnTrack DM6 Aux 9f  BSD/OS          e4  SpeedStor     
 c  W95 FAT32 (LBA) 52  CP/M            a0  IBM Thinkpad hi eb  BeOS fs       
 e  W95 FAT16 (LBA) 53  OnTrack DM6 Aux a5  FreeBSD         ee  GPT           
 f  W95 Ext'd (LBA) 54  OnTrackDM6      a6  OpenBSD         ef  EFI (FAT-12/16/
10  OPUS            55  EZ-Drive        a7  NeXTSTEP        f0  Linux/PA-RISC b
11  Hidden FAT12    56  Golden Bow      a8  Darwin UFS      f1  SpeedStor     
12  Compaq diagnost 5c  Priam Edisk     a9  NetBSD          f4  SpeedStor     
14  Hidden FAT16 <3 61  SpeedStor       ab  Darwin boot     f2  DOS secondary 
16  Hidden FAT16    63  GNU HURD or Sys af  HFS / HFS+      fb  VMware VMFS   
17  Hidden HPFS/NTF 64  Novell Netware  b7  BSDI fs         fc  VMware VMKCORE
18  AST SmartSleep  65  Novell Netware  b8  BSDI swap       fd  Linux raid auto
1b  Hidden W95 FAT3 70  DiskSecure Mult bb  Boot Wizard hid fe  LANstep       
1c  Hidden W95 FAT3 75  PC/IX           be  Solaris boot    ff  BBT           
1e  Hidden W95 FAT1 80  Old Minix     
Hex code (type L to list codes):



_________________
Without diversity there can be no evolution:)
Back to top
View user's profile Send private message
skiwarz
Tux's lil' helper
Tux's lil' helper


Joined: 23 Feb 2014
Posts: 128

PostPosted: Sun Aug 16, 2015 3:26 pm    Post subject: Reply with quote

If you're using gdisk, it's type ef02. If you're using parted, all you need is
Code:
set bios_grub on

No filesystem needed there. Grub will do whatever it needs when installing. At least, that's all I did.

[edit] It's
Code:
set bios_grub on
not bios_boot. Sorry. I fixed it in my reply
Back to top
View user's profile Send private message
cwc
Veteran
Veteran


Joined: 20 Mar 2006
Posts: 1107
Location: Tri-Cities, WA USA

PostPosted: Sun Aug 16, 2015 3:46 pm    Post subject: Reply with quote

skiwarz wrote:
If you're using gdisk, it's type ef02. If you're using parted, all you need is
Code:
set bios_grub on

No filesystem needed there. Grub will do whatever it needs when installing. At least, that's all I did.

[edit] It's
Code:
set bios_grub on
not bios_boot. Sorry. I fixed it in my reply


I'm using fdisk.

parted errored on me with :
set 1 bios_grub on

Code:


(parted) set bios_grub on
Error: Expecting a partition number.                                     
(parted) set 1 bios_grub on                                                 
parted: invalid token: bios_grub
Flag to Invert?                                                           





_________________
Without diversity there can be no evolution:)
Back to top
View user's profile Send private message
skiwarz
Tux's lil' helper
Tux's lil' helper


Joined: 23 Feb 2014
Posts: 128

PostPosted: Sun Aug 16, 2015 5:25 pm    Post subject: Reply with quote

I don't think you can manipulate gpt partitions in fdisk. You can manipulate the "protective MBR partition" that surrounds the GPT disk, but seeing as you're using fdisk, you may actually have an MBR disk. That would explain the error in parted. If you're 100% sure it's a GPT disk, I'd try using gdisk first. It's built for GPT disks.
Can you post the "disklabel type" field that is output by
Code:
fdisk -l
Back to top
View user's profile Send private message
cwc
Veteran
Veteran


Joined: 20 Mar 2006
Posts: 1107
Location: Tri-Cities, WA USA

PostPosted: Sun Aug 16, 2015 6:57 pm    Post subject: Reply with quote

skiwarz wrote:
I don't think you can manipulate gpt partitions in fdisk. You can manipulate the "protective MBR partition" that surrounds the GPT disk, but seeing as you're using fdisk, you may actually have an MBR disk. That would explain the error in parted. If you're 100% sure it's a GPT disk, I'd try using gdisk first. It's built for GPT disks.
Can you post the "disklabel type" field that is output by
Code:
fdisk -l


thanks for the help. i learnb so much from this forum
I honestly did know the difference between an mbr and gpt disk until i had trouble with this install.
Back with windows 3.1 I we used the kill mbr virus by using C:\>fdisk /mbr
Would I also do this with my system to clear the mbr.

Would you recommend mbr or guid gpt on my legacy system?

Here is my fdisk -l output. I have a clear partition table expect for a partition that will become a bios boot.

Code:

root@sysresccd /root % fdisk -l

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *          63  1953525167   976762552+  83  Linux

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0003a2dc

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *          63  1953525167   976762552+  83  Linux

Disk /dev/sda: 320.1 GB, 320072933376 bytes
98 heads, 34 sectors/track, 187617 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0008d967

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1            2048        6144        2048+  83  Linux
root@sysresccd /root %


_________________
Without diversity there can be no evolution:)
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43192
Location: 56N 3W

PostPosted: Sun Aug 16, 2015 8:06 pm    Post subject: Reply with quote

cwc,

A few seemingly randam facts.
1. Bootloaders do not fit in LBA 0, they all need some extra space.
2. The MSDOS partition table starts in LBA 0, the overflow is scattered arounh the drive.
3. A GPT partition table starts in LBA 1
4. BIOS (not UEFI) closes its eyes and loads LBA 0.

With BIOS and a MSDOS partition table, it all works. The extra space the bootloader needs is before the start of the first partition. You don't need to provide it.
Some brain dead BIOSes check the boot flag in the MSDOS partition table.

With BIOS and GPT its more complicated. The GPT starts in block 1, so there is no empty space for the bootloader to use.
You need to allocate some in the form of the BIOS boot partition. The boot loader uses this for its own code. Any filesystem you may put here is ignored.
The BIOS still loads and may try to check the MSDOS partition table. It has no idea you are using GPT and no way to read it either.

So with BIOS and GPT, you still get a free MSDOS partition table, and its here you need to set the bootable flag.
There will be one partition of type ee.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
skiwarz
Tux's lil' helper
Tux's lil' helper


Joined: 23 Feb 2014
Posts: 128

PostPosted: Sun Aug 16, 2015 9:10 pm    Post subject: Reply with quote

Ok. I thought you had already partitioned it and everything. Since you have an older (legacy) system, I'd just use MBR. You don't need GPT, and I don't really think there's any benefit to having it.

In summary, you can have either MBR booted by BIOS (old), GPT booted by BIOS (a bridge between new and old), or GPT booted by EFI (the modern way). All the stuff I was saying in my earlier posts was in regards to booting a GPT disk with BIOS, because I thought that's what you were trying to do. It is the most complicated of those methods.

MBR+BIOS:
Just partition your disk in fdisk, using only the partitions you need, such as [/, /boot, swap]. This is what you're probably used to doing, as it's been the standard setup basically forever. You could also use cfdisk, which is a menu-driven form of fdisk.

GPT+BIOS:
This is where everything gets complicated. You need to create the GPT disk and partition table first, including that small BIOS boot partition we've been talking about. You need to leave sufficient space at the beginning of the disk for the partition table and protective MBR (LBA63 is the first usable block, I think. I started my first partition at 1MB, which is LBA2048 on my system). This BIOS boot partition is where most of grub's boot code goes, because the protective MBR has insufficient space for it (unlike the MBR disk). 2MB is sufficient for it. It will have type ef02 or have the bios_grub flag "on" in parted. You need to use either gdisk or parted to manipulate GPT disks. fdisk won't work, to my knowledge. After that first BIOS boot partition, you can place the rest of your partitions. AFTER partitioning your whole disk, use fdisk to set the "protective MBR" bootable. You will only see one partition, covering your whole disk, as that's all fdisk can see. That's the protective MBR, of type EE like NeddySeagoon said. That's what your BIOS will see and boot from, and that code it loads will further load grub, which reads the GPT and loads your OS.

GPT+EFI:
The new standard. You need EFI firmware to boot it (probably newer than 2008). Honestly, I've never done this on linux, so I don't know how it works. I DO know that you don't need the BIOS boot partition anymore, but instead need a ~200MB EFI partition, which I believe grub will install to. No promises on this one.

This article will teach you a lot, if you feel like reading: https://en.wikipedia.org/wiki/GUID_Partition_Table

Also, NeddySeagoon... dude you are a legend. I see you everywhere on here, and you always seem to have the answer.
Back to top
View user's profile Send private message
ian.au
Guru
Guru


Joined: 07 Apr 2011
Posts: 434
Location: Australia

PostPosted: Sun Aug 16, 2015 9:51 pm    Post subject: Reply with quote

cwc,

You really need to pick just one option and follow it through. For your legacy system that option is MBR, use fdisk to set it up as is clearly documented in the handbook link I posted before I went to bed last night.

Your partition table was set up correctly,
cwc wrote:
Partition Description
/dev/sda1 BIOS boot partition
/dev/sda2 Boot partition
/dev/sda3 Swap partition
/dev/sda4 Root partition
and you should have just persevered with the fdisk instructions, which tell you how to set the bios partition and the file type on it (ie. partition 1, starting the first sector at 2048 and applying the type to BIOS boot which is done by selecting the -t option on partition 1 and selecting hex code 4).

I really hope you didn't follow the advice to use parted and set up another efi partition, don't second-guess it, just follow the handbook and do an MBR install with fdisk. Unfortunately I went to bed after posting, so I only just saw your follow up post.

I told you already that you don't *need* a BIOS boot partition for MBR, Neddy has told you why. As the handbook recommends it though, and to keep you focussed on the objective of getting a booting system, just set one up anyway as you were doing, it won't hurt - and means you can follow the handbook exactly later when you get to installing the bootloader.

I think you are becoming distracted by alternatives that simply don't apply to your hardware. Follow the handbook, its written by experts to get you booting and it will do that.
Back to top
View user's profile Send private message
cwc
Veteran
Veteran


Joined: 20 Mar 2006
Posts: 1107
Location: Tri-Cities, WA USA

PostPosted: Sun Aug 16, 2015 9:53 pm    Post subject: Reply with quote

Thank you all for the posts! I'll research and get to work.

Neddy you are legendary. The British Rock! I went and saw Mufford & Sons last night. 2.5 hours. It was epic!
http://www.gentlemenoftheroad.com/stopovers/walla-walla/
_________________
Without diversity there can be no evolution:)
Back to top
View user's profile Send private message
skiwarz
Tux's lil' helper
Tux's lil' helper


Joined: 23 Feb 2014
Posts: 128

PostPosted: Sun Aug 16, 2015 10:02 pm    Post subject: Reply with quote

To be clear, in your case (booting MBR with BIOS), you DO NOT NEED a bios boot partition. Just the root, /boot, and swap.
Back to top
View user's profile Send private message
cwc
Veteran
Veteran


Joined: 20 Mar 2006
Posts: 1107
Location: Tri-Cities, WA USA

PostPosted: Mon Aug 17, 2015 3:55 am    Post subject: Reply with quote

skiwarz wrote:
To be clear, in your case (booting MBR with BIOS), you DO NOT NEED a bios boot partition. Just the root, /boot, and swap.


Got it. Thanks for all the help skiwarz!
_________________
Without diversity there can be no evolution:)
Back to top
View user's profile Send private message
cwc
Veteran
Veteran


Joined: 20 Mar 2006
Posts: 1107
Location: Tri-Cities, WA USA

PostPosted: Mon Aug 17, 2015 4:25 am    Post subject: Reply with quote

Thanks ian.au!
_________________
Without diversity there can be no evolution:)
Back to top
View user's profile Send private message
cwc
Veteran
Veteran


Joined: 20 Mar 2006
Posts: 1107
Location: Tri-Cities, WA USA

PostPosted: Tue Aug 18, 2015 12:44 pm    Post subject: Reply with quote

I got the system to boot. But there is no eth0.
[5] default/linux/amd64/13.0/desktop/gnome/systemd *


Solution:

Paritions created using fdisk

/boot
swap
/

Make sure to follow the grub2 directions:
Code:

Configuring GRUB2
Next, install the necessary GRUB2 files in /boot/grub/. Assuming the first disk (the one where the system boots from) is /dev/sda, the following command will do this:

root #grub2-install /dev/sda

root #grub2-mkconfig -o /boot/grub/grub.cfg


Now I need to figure out the eth0 problem.

I have nothing in the: /etc/udev/rules.d/ directory
# pwd
/etc/udev/rules.d
sysresccd rules.d # ls

Thanks for all the help. I learned a lot. I'll post if I can not get eth0 working after I try to update world.
_________________
Without diversity there can be no evolution:)
Back to top
View user's profile Send private message
ian.au
Guru
Guru


Joined: 07 Apr 2011
Posts: 434
Location: Australia

PostPosted: Tue Aug 18, 2015 1:05 pm    Post subject: Reply with quote

cwc,
You'll probably have a device, using systemd it will be called something other than eth0. It's easiest just to use the name your device has been given rather than forcing it to be eth0.
To find out what that device is called:
Code:
ifconfig -a
There will likely be a device like enp?s0 listed there. Using that device in place of eth0 and proceed to set up your hostname, etc as per the handbook from the section https://wiki.gentoo.org/wiki/Systemd#Post-installation_configuration

Edit - Corrected link
Back to top
View user's profile Send private message
cwc
Veteran
Veteran


Joined: 20 Mar 2006
Posts: 1107
Location: Tri-Cities, WA USA

PostPosted: Tue Aug 18, 2015 1:24 pm    Post subject: Reply with quote

ian.au wrote:
cwc,
You'll probably have a device, using systemd it will be called something other than eth0. It's easiest just to use the name your device has been given rather than forcing it to be eth0.
To find out what that device is called:
Code:
ifconfig -a
There will likely be a device like enp?s0 listed there. Using that device in place of eth0 and proceed to set up your hostname, etc as per the handbook from the section https://wiki.gentoo.org/wiki/Systemd#Post-installation_configuration

Edit - Corrected link


thanks ian.au,

Do you use systemd? I am having a bit of a problems with systemd again. Not fully understanding why virtual/udev gets pulled if udev is part of systemd.
Do I mask udev?
I am going to install gnome and I have systemd selected in my profile:

[5] default/linux/amd64/13.0/desktop/gnome/systemd *


Code:

emerge -avuD world

 * IMPORTANT: 9 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.


These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild     U  ] app-shells/bash-4.3_p39::gentoo [4.3_p33-r2::gentoo] USE="net nls (readline) -afs -bashlogger -examples -mem-scramble -plugins -vanilla" 7,990 KiB
[ebuild  N     ] virtual/udev-215::gentoo  USE="(systemd)" 0 KiB




I uninstalled virtual/udev becuase if gave me the following when installed:

Code:

# emerge -avuD world

 * IMPORTANT: 9 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.


These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild     U  ] app-shells/bash-4.3_p39::gentoo [4.3_p33-r2::gentoo] USE="net nls (readline) -afs -bashlogger -examples -mem-scramble -plugins -vanilla" 7,990 KiB
[ebuild  N    #] sys-fs/udev-216::gentoo  USE="acl firmware-loader gudev introspection kmod -doc (-selinux) -static-libs" ABI_X86="(64) -32 (-x32)" 3,530 KiB
[blocks B      ] sys-apps/gentoo-systemd-integration ("sys-apps/gentoo-systemd-integration" is blocking sys-fs/udev-216)
[blocks B      ] sys-apps/systemd ("sys-apps/systemd" is blocking sys-fs/udev-216)
[blocks B      ] sys-fs/udev ("sys-fs/udev" is blocking sys-apps/systemd-218-r3, sys-apps/gentoo-systemd-integration-4)

Total: 2 packages (1 upgrade, 1 new), Size of downloads: 11,520 KiB
Conflict: 3 blocks (3 unsatisfied)

 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (sys-fs/udev-216:0/0::gentoo, ebuild scheduled for merge) pulled in by
    >=sys-fs/udev-208-r1 required by (virtual/udev-215:0/0::gentoo, installed)

  (sys-apps/systemd-218-r3:0/2::gentoo, installed) pulled in by
    sys-apps/systemd:0= required by (sys-apps/dbus-1.8.16:0/0::gentoo, installed)
    >=sys-apps/systemd-44:0/2= required by (x11-misc/colord-1.2.10:0/2::gentoo, installed)
    sys-apps/systemd required by (net-print/cups-2.0.3:0/0::gentoo, installed)
    sys-apps/systemd:0= required by (sys-auth/polkit-0.112-r3:0/0::gentoo, installed)
    sys-apps/systemd required by (app-admin/syslog-ng-3.6.4:0/0::gentoo, installed)
    sys-apps/systemd:0/2= required by (sys-auth/polkit-0.112-r3:0/0::gentoo, installed)
    >=sys-apps/systemd-212-r5:0/2[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?] (>=sys-apps/systemd-212-r5:0/2[abi_x86_64(-)]) required by (virtual/libudev-215-r1:0/1::gentoo, installed)
    >=sys-apps/systemd-212-r5:0/2[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,gudev(-),introspection(-)?] (>=sys-apps/systemd-212-r5:0/2[abi_x86_64(-),gudev(-),introspection(-)]) required by (virtual/libgudev-215-r3:0/0::gentoo, installed)
    >=sys-apps/systemd-44:0= required by (x11-misc/colord-1.2.10:0/2::gentoo, installed)
    sys-apps/systemd:0/2= required by (sys-apps/dbus-1.8.16:0/0::gentoo, installed)
    >=sys-apps/systemd-207 required by (sys-apps/gentoo-systemd-integration-4:0/0::gentoo, installed)


For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):

https://wiki.gentoo.org/wiki/Handbook:X86/Working/Portage#Blocked_packages


The following mask changes are necessary to proceed:
 (see "package.unmask" in the portage(5) man page for more details)
# required by virtual/udev-215::gentoo
# required by x11-misc/colord-1.2.10::gentoo
# required by x11-libs/gtk+-3.14.13::gentoo
# required by gnome-extra/polkit-gnome-0.105-r1::gentoo
# required by sys-auth/polkit-0.112-r3::gentoo[gtk]
# required by sys-apps/systemd-218-r3::gentoo[policykit]
# required by virtual/libudev-215-r1::gentoo
# required by dev-libs/libusb-1.0.19::gentoo
# required by virtual/libusb-1-r1::gentoo
# required by net-print/cups-2.0.3::gentoo[usb]
# required by net-print/cups-filters-1.0.71::gentoo
# /usr/portage/profiles/targets/systemd/package.mask:
# Pacho Ramos <pacho@gentoo.org> (21 Apr 2015)
# This is for running sys-apps/systemd and also helps
# portage to not try to pull in other providers leading to
# strange blockers.
=sys-fs/udev-216

NOTE: The --autounmask-keep-masks option will prevent emerge
      from creating package.unmask or ** keyword changes.

Would you like to add these changes to your config files? [Yes/No] n
sysresccd home # emerge --search udev




_________________
Without diversity there can be no evolution:)
Back to top
View user's profile Send private message
ian.au
Guru
Guru


Joined: 07 Apr 2011
Posts: 434
Location: Australia

PostPosted: Tue Aug 18, 2015 1:32 pm    Post subject: Reply with quote

cwc
I use both supported inits. I have systemd on all my gnome desktops.
You shouldn't have unmerged virtual/udev, you need that one with systemd,
you should have unmerged sys-fs/udev so just unmerge that now and try updating world again.
Back to top
View user's profile Send private message
cwc
Veteran
Veteran


Joined: 20 Mar 2006
Posts: 1107
Location: Tri-Cities, WA USA

PostPosted: Tue Aug 18, 2015 2:09 pm    Post subject: Reply with quote

ian.au wrote:
cwc
I use both supported inits. I have systemd on all my gnome desktops.
You shouldn't have unmerged virtual/udev, you need that one with systemd,
you should have unmerged sys-fs/udev so just unmerge that now and try updating world again.


thanks again ian,

I missed that I havd udev installed. Update world is cooking.

Now I get the following errors: (thow me a bone please)
Code:

# hostnamectl set-hostname azzerare
Failed to create bus connection: No such file or directory
sysresccd ~ # timedatectl
Failed to create bus connection: No such file or directory

I never realized systemctl was systemd. I run centos on my laptop and use systemctl to start and stop services.

I need to get to work.
_________________
Without diversity there can be no evolution:)
Back to top
View user's profile Send private message
ian.au
Guru
Guru


Joined: 07 Apr 2011
Posts: 434
Location: Australia

PostPosted: Tue Aug 18, 2015 2:21 pm    Post subject: Reply with quote

I think you'll have to wait until you reboot into your systemd system, my guess is you're booted with openrc right now (as systemd wasn't installed due to those Blocks and world is still updating?) easiest way to check is to see what's sitting on pid1 :wink:
Code:
ps -ax |less
If not
Code:
1 ?        Ss     0:08 /usr/lib/systemd/systemd
then none of the systemctl functionality is available yet.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum