Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
no network installation
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2  
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
rekonrad
Apprentice
Apprentice


Joined: 01 Jun 2003
Posts: 201
Location: Winnipeg, MB

PostPosted: Thu Jun 11, 2015 8:49 pm    Post subject: boot problems Reply with quote

This sounds like more work than starting over again - so I will start over again..

The reason why I chose to put /boot on my flash drive is because there are no more partitions left on my hard drive. I originally wanted also to install grub there but I decided to put it on the Mint grub as you advised. Is it really necessary to have a separate partition for /boot and format it to a different file system ie ext2 as the handbook instructs? It would make the whole process easier if I keep the /boot in the same file system and partition as my root. That way I could fit everything on my hard drive. thanks again.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Thu Jun 11, 2015 9:09 pm    Post subject: Reply with quote

rekonrad,

A separate /boot is a symptom of the race of the growth oy hard drive sizes and BIOSes to keep up.
To be able to have /boot as a directory on /, the BIOS mush be able to read the entire hard drive.

From time to time in the history of the PC, hard drives grew bigger that the BIOS could read.
The workaround wan to keep all the files read by the BIOS in a small partition at the front of the drive, called /boot.
The last time this happened was when HDD reached 137G.
The first time was at 528Mb.

So, it will probably work for you without a /boot partition. Copy the content to the /boot directory and adjust grub and /etc/fstab to suit.
_________________
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
cwr
Veteran
Veteran


Joined: 17 Dec 2005
Posts: 1969

PostPosted: Fri Jun 12, 2015 11:11 am    Post subject: Reply with quote

You definitely don't _need_ a separate /boot partition, though it's usually convenient.
A standard Ubuntu install doesn't use a separate partition, for instance, though I
usually boot it from my (separate) Gentoo /boot.

I really don't think you need to start over. Describe your partition layout here,
and someone will have some ideas on setting it up the way you want.

Will
Back to top
View user's profile Send private message
rekonrad
Apprentice
Apprentice


Joined: 01 Jun 2003
Posts: 201
Location: Winnipeg, MB

PostPosted: Fri Jun 12, 2015 3:13 pm    Post subject: restart Reply with quote

Thanks. Changing to the other boot directory worked just fine. But I'm encountering other problems including X not starting up and an emerge failure etc. I think I have loaded a ton of crap on chroot and maybe I shouldn't have.....I'll probably start the process over again. I really want my wlan0 wireless to work on reboot and that may be why I started loading lots of stuff. Though I will probably start over, I got an emerge failure at "pillow (python)". I looked at the log and it seems that it wants to put some files in /run/shw but can't? Anyway here is the last part of the log:

Quote:
PIL SETUP SUMMARY
--------------------------------------------------------------------
version Pillow 2.8.1
platform linux2 2.7.9 (default, Jun 11 2015, 11:13:45)
[GCC 4.8.4]
--------------------------------------------------------------------
*** TKINTER support not available
--- JPEG support available
*** OPENJPEG (JPEG2000) support not available
--- ZLIB (PNG/ZIP) support available
--- LIBTIFF support available
--- FREETYPE2 support available
--- LITTLECMS2 support available
*** WEBP support not available
*** WEBPMUX support not available
--------------------------------------------------------------------
To add a missing option, make sure you have the required
library, and set the corresponding ROOT variable in the
setup.py script.

To check the build, run the selftest.py script.

running build_scripts
creating /var/tmp/portage/dev-python/pillow-2.8.1/work/Pillow-2.8.1-python2_7/build/scripts
copying and adjusting Scripts/pilfont.py -> /var/tmp/portage/dev-python/pillow-2.8.1/work/Pillow-2.8.1-python2_7/build/scripts
copying and adjusting Scripts/pildriver.py -> /var/tmp/portage/dev-python/pillow-2.8.1/work/Pillow-2.8.1-python2_7/build/scripts
copying and adjusting Scripts/pilprint.py -> /var/tmp/portage/dev-python/pillow-2.8.1/work/Pillow-2.8.1-python2_7/build/scripts
copying and adjusting Scripts/pilconvert.py -> /var/tmp/portage/dev-python/pillow-2.8.1/work/Pillow-2.8.1-python2_7/build/scripts
copying and adjusting Scripts/pilfile.py -> /var/tmp/portage/dev-python/pillow-2.8.1/work/Pillow-2.8.1-python2_7/build/scripts
changing mode of /var/tmp/portage/dev-python/pillow-2.8.1/work/Pillow-2.8.1-python2_7/build/scripts/pilfont.py from 644 to 755
changing mode of /var/tmp/portage/dev-python/pillow-2.8.1/work/Pillow-2.8.1-python2_7/build/scripts/pildriver.py from 644 to 755
changing mode of /var/tmp/portage/dev-python/pillow-2.8.1/work/Pillow-2.8.1-python2_7/build/scripts/pilprint.py from 644 to 755
changing mode of /var/tmp/portage/dev-python/pillow-2.8.1/work/Pillow-2.8.1-python2_7/build/scripts/pilconvert.py from 644 to 755
changing mode of /var/tmp/portage/dev-python/pillow-2.8.1/work/Pillow-2.8.1-python2_7/build/scripts/pilfile.py from 644 to 755
* python2_7: running distutils-r1_run_phase python_compile_all
>>> Source compiled.
* --------------------------- ACCESS VIOLATION SUMMARY ---------------------------
* LOG FILE: "/var/log/sandbox/sandbox-12784.log"
*
VERSION 1.0
FORMAT: F - Function called
FORMAT: S - Access Status
FORMAT: P - Path as passed to function
FORMAT: A - Absolute Path (not canonical)
FORMAT: R - Canonical Path
FORMAT: C - Command Line

F: link
S: deny
P: /run/shm/sem.mp12877-0
A: /run/shm/sem.mp12877-0
R: /run/shm/sem.mp12877-0
C: /usr/bin/python3.3 setup.py build

F: unlink
S: deny
P: /run/shm/sem.1XT8Lz
A: /run/shm/sem.1XT8Lz
R: /run/shm/sem.1XT8Lz
C: /usr/bin/python3.3 setup.py build

F: link
S: deny
P: /run/shm/sem.mp13178-0
A: /run/shm/sem.mp13178-0
R: /run/shm/sem.mp13178-0
C: /usr/bin/python2.7 setup.py build

F: unlink
S: deny
P: /run/shm/sem.9LYzOc
A: /run/shm/sem.9LYzOc
R: /run/shm/sem.9LYzOc
C: /usr/bin/python2.7 setup.py build


If this can be made to work - I may continue to try....
Back to top
View user's profile Send private message
rekonrad
Apprentice
Apprentice


Joined: 01 Jun 2003
Posts: 201
Location: Winnipeg, MB

PostPosted: Fri Jun 12, 2015 4:24 pm    Post subject: solved Reply with quote

I did mkdir in /mnt/gentoo/dev/shw, then chmod 1777 then chrooted. That seemed to work! Pillow is done - moving on..

Richard
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 Previous  1, 2
Page 2 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