| View previous topic :: View next topic |
| Author |
Message |
nsahoo
l33t
Joined: 17 Jul 2003
Posts: 618
|
 Posted: Tue Nov 02, 2004 10:20 pm Post subject: |
 |
|
thanks .. i just noticed OP saying the same thing in the head post. 
MY first image was 2.1 G 
also it complains about boot/grub/stage2_eltorito .. should it be boot/grub/grub.conf ?
edit: just figured out that the stage2_eltorito appears in grub 0.95 and that is masked in portage. so, the usual drill,
| Code: |
echo sys-boot/grub ~x86 >>/etc/portage/package.keywords
emerge -va grub
|
|
|
| Back to top |
|
 |
nsahoo
l33t
Joined: 17 Jul 2003
Posts: 618
|
| Posted: Tue Nov 02, 2004 10:57 pm Post subject: |
|
|
still 761MB, do I need to include the proc file system ? it weighs at 1017MB
I don't have much package actually. The "system" a logger, hotplug, cron, vim and java5. no X, no kde, no gnome or anything .. still 761MB  |
|
| Back to top |
|
|
chunderbunny
Veteran
Joined: 31 May 2004
Posts: 1281
Location: 51°24'27" N, 0°57'15" W
|
| Posted: Tue Nov 02, 2004 11:06 pm Post subject: |
|
|
| Thta's insanely large. You don't need the proc file system (the kernel should generate it on boot) but it shouldn't be that large. You should make sure you exclude /usr/portage from the squashfs since you can't emerge stuff once you have booted the livecd anyway. |
|
| Back to top |
|
|
nsahoo
l33t
Joined: 17 Jul 2003
Posts: 618
|
| Posted: Tue Nov 02, 2004 11:12 pm Post subject: |
|
|
| chunderbunny wrote: | | Thta's insanely large. You don't need the proc file system (the kernel should generate it on boot) but it shouldn't be that large. You should make sure you exclude /usr/portage from the squashfs since you can't emerge stuff once you have booted the livecd anyway. |
ya .. i have usr/src and usr/portage excluded. I mounted the img file and verified.
There is a file called kcore in /proc of the host which is 1016M and that goes into the squashed file. that is why it's so large.
| Quote: |
You don't need the proc file system (the kernel should generate it on boot)
|
so .. i unmount the proc and do the stuff again .. right ? |
|
| Back to top |
|
|
nsahoo
l33t
Joined: 17 Jul 2003
Posts: 618
|
| Posted: Wed Nov 03, 2004 12:00 am Post subject: [SOLVED] |
|
|
In fact all my troubles are because, I didn't closely follow the excellent how to. They would be taken careof if one follows OP line by line.
edit: is there a way to auto login the root or another user while booting ? with a scrambled passwd may be ?
edit2: hmm .. so it's up  with network, sshd, java5 and all that stuff. Now I just need a little writable space to work in .. is mounting some tmpfs at a directory the best way to go about it ?
edit3: I used the livecd in my machine and it started alright. Also, I tested the cd with a friends machine having somewhat similar specification as mine, and it booted alright.
Now I am trying to use it in another machine. and getting some error while booting. The text scrolled by too fast and then I have only this much text visible.
| Code: |
Simple Boot Flag at 0x7a set to 0x1
Machine check exception polling timer started.
gx-suspmod: error: no MediaGX/Geode processor found!
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI
devfs: 2004-01-31 Richard Gooch (...)
devfs: boot_option: 0x0
Installing knfsd (copyright ...)
SGI XFS with large block numbers, no debug enabled.
Initializing Cryptographic API
inotify init: minor=63
Real Time Clock Driver v1.12
|
Then it seems to have a deadlock.
I used stage2 for pentium 4 system to make the build. Also, I used gentoo-dev-sources-2.6.9-r1 and genkernel to configure it, so that I'll have all the modules and hence it'll be compatible with many system.
I tried compiling the kernel with processor type pentium4 and with i486 with high mem support on and off. Got the same result.
Gentoo official livecd is starting alright.
The machine on which it's NOT starting is a dell optiplex gx270 with a p4 3.2 ghz processor with 1gb ram and on board sound and video.
edit4: I tried booting by removing the video parameter, i.e. when grub starts .. i edited the second line to remove video parameter. But, that also lead to the lockup, but, I get a little more text
| Code: |
Non-volatile memory driver v1.2
hw_random: RNG not detected.
vesafb: Intel Corporation, Intel(r)865G graphics controller, Hardware Version 0.
0 (OEM: Intel(r) 865G Graphics chip Accelerated VGA BIOS
vesafb: VBE version: 3.0
vesafb: hardware supports DCC2 transfers
vesafb: monitor limits: vf = 75 Hz, hf = 80 kHz, clk = 140 MHz
vesafb: scrolling: redraw
|
Then the lockup.
Any help ?
Thanks.
edit:5:
I switched to gentoo-dev-sources-2.6.8-r<latest> from gentoo-dev-sources-2.6.9-r1 and removed the video parameter from the kernel line in grub.conf. Then it started alright, although I have fewer rows and columns in the terminal.
Last edited by nsahoo on Fri Nov 05, 2004 12:18 am; edited 2 times in total |
|
| Back to top |
|
|
bin-doph
Guru
Joined: 23 May 2003
Posts: 302
|
| Posted: Wed Nov 03, 2004 10:13 am Post subject: |
|
|
Hi,
the whole thing looks pretty good, but if I boot from the cd I get this error message
| Quote: | warning: can't open /etc/fstab: No such file or directory
Unable to identify CD-ROM format. |
Then I get timeouts on the IDE-drives but the image boot's after a couple of minutes and works. Did I miss something?
_________________
perl -e '$_=q;4a75737420616e6f74686572205065726c204861636b65720as;;for(s;s;s;s;s;s;s;s;s;s;s;s){s;(..)s?;qq qprint chr 0x$1 and \161 ssq;excess;}' |
|
| Back to top |
|
|
veezi
Apprentice
Joined: 10 Nov 2003
Posts: 226
|
| Posted: Wed Nov 03, 2004 11:55 am Post subject: |
|
|
| bin-doph wrote: | Hi,
the whole thing looks pretty good, but if I boot from the cd I get this error message
| Quote: | warning: can't open /etc/fstab: No such file or directory
Unable to identify CD-ROM format. |
Then I get timeouts on the IDE-drives but the image boot's after a couple of minutes and works. Did I miss something? |
You probably forgot to include some of the required settings in kernel configuration of your livecd. Check all required kernel config as mentioned in the doc.
If all will, try to boot into '/bin/sh' (by changing the grub line on livecd boot from 'init=/linuxrc' to 'init=/bin/sh') and manually execute each line in linuxrc to figure out what's going wrong. |
|
| Back to top |
|
|
Illissius
Guru
Joined: 31 Jul 2004
Posts: 395
Location: Hungary
|
| Posted: Wed Nov 03, 2004 12:54 pm Post subject: |
|
|
Thanks for the help, I did the thing with the ext2 image on /misc mounted to ~/livecd, and that part seems to be working well; however, emerge system does this:
| Code: | >>> md5 src_uri ;-) gawk-3.1.3.tar.gz
>>> Unpacking source...
>>> Unpacking gawk-3.1.3.tar.gz to /var/tmp/portage/gawk-3.1.3-r1/work
* Applying 64bitnumfile.patch ... [ ok ]
* Using GNU config files from /usr/share/gnuconfig
* Updating config.sub [ ok ]
* Updating config.guess [ ok ]
>>> Source unpacked.
nls
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
configure: loading cache /dev/null
./configure: line 1: ./configure:: No such file or directory
checking for a BSD-compatible install... ./install-sh -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i586-pc-linux-gnu-strip... no
checking for strip... strip
checking for egrep... grep -E
checking for bison... bison -y
checking whether ln -s works... yes
checking for i586-pc-linux-gnu-gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... /lib/cpp
configure: error: C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
!!! ERROR: sys-apps/gawk-3.1.3-r1 failed.
!!! Function src_compile, Line 45, Exitcode 1
!!! (no error message)
|
Why?
_________________
Work is punishment for failing to procrastinate effectively.
last.fm |
|
| Back to top |
|
|
veezi
Apprentice
Joined: 10 Nov 2003
Posts: 226
|
| Posted: Wed Nov 03, 2004 1:25 pm Post subject: |
|
|
Try 'env-update; source /etc/profile' before 'emerge system'.
Is this the first package, or did other packages compile successfully before it.
Doesn't sound like a problem with your particular setup (root on loop file on FAT32). Sounds more like a regular installation problem.
I usually get better success by running 'emerge -u system'. I think. |
|
| Back to top |
|
|
Illissius
Guru
Joined: 31 Jul 2004
Posts: 395
Location: Hungary
|
| Posted: Wed Nov 03, 2004 2:12 pm Post subject: |
|
|
I did do env-update and source /etc/profile. It's the first package that fails -- with emerge -u system, ncurses is the first package, but that fails also:
| Code: | lenti / # env-update; source /etc/profile; emerge -u system
* Caching service dependencies...
Calculating system dependencies ...done!
>>> emerge (1 of 84) sys-libs/ncurses-5.4-r5 to /
>>> md5 src_uri ;-) ncurses-5.4.tar.gz
>>> Unpacking source...
>>> Unpacking ncurses-5.4.tar.gz to /var/tmp/portage/ncurses-5.4-r5/work
* Applying ncurses-5.4-xterm.patch ... [ ok ]
* Applying ncurses-5.4-share-sed.patch ... [ ok ]
* Using GNU config files from /usr/share/gnuconfig
* Updating config.sub [ ok ]
* Updating config.guess [ ok ]
>>> Source unpacked.
unicode
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
configure: loading cache /dev/null
./configure: line 1: ./configure:: No such file or directory
Configuring NCURSES 5.4 ABI 5 (Wed Nov 3 15:05:33 Local time zone must be set--see zic manual page 2004)
checking build system type... i686-pc-linux-gnu
checking host system type... i586-pc-linux-gnu
checking target system type... i586-pc-linux-gnu
Configuring for linux-gnu
checking for prefix... /usr
checking for i586-pc-linux-gnu-gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking version of gcc... 3.3.3
checking how to run the C preprocessor... gcc -E
checking whether gcc needs -traditional... no
checking for POSIXized ISC... no
checking for gcc option to accept ANSI C... -DCC_HAS_PROTOS
checking for ldconfig... /sbin/ldconfig
checking if you want to ensure bool is consistent with C++... yes
checking for i586-pc-linux-gnu-g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for g++... /usr/bin/g++
checking version of g++... g++ (GCC) 3.3.3 20040412 (Gentoo Linux 3.3.3-r6, ssp-3.3.2-2, pie-8.7.6)
checking if you want to build C++ binding and demo... yes
checking if you want to build with Ada95... no
checking if you want to build programs such as tic... yes
checking if you wish to install curses.h... yes
checking for mawk... no
checking for gawk... gawk
checking whether make sets ${MAKE}... yes
checking for a BSD compatible install... /bin/install -c
checking for long file names... yes
checking if filesystem supports mixed-case filenames... yes
checking whether ln -s works... yes
checking for ctags... no
checking for etags... no
checking for tdlint... no
checking for lint... no
checking for alint... no
checking for man... no
checking for man_db... no
checking for i586-pc-linux-gnu-ranlib... no
checking for ranlib... ranlib
checking for i586-pc-linux-gnu-ld... no
checking for ld... ld
checking for i586-pc-linux-gnu-ar... no
checking for ar... ar
checking for archiver options (symbol AR_OPTS)... rv
checking for makeflags variable...
checking if you have specified an install-prefix...
checking if you want to build libraries with libtool... no
checking if you want to build shared libraries... yes
checking if you want to build static libraries... yes
checking if you want to build debug libraries... no
checking if you want to build profiling libraries... no
checking for specified models... shared normal
checking for default model... shared
checking if you want to build a separate terminfo library... no
checking if you want to link with dbmalloc for testing... no
checking if you want to link with dmalloc for testing... no
checking if you want to link with the gpm mouse library... no
checking for default loader flags...
checking if rpath option should be used... no
checking if release/abi version should be used for shared libs... auto
checking which gcc option to use... -fPIC
checking if you wish to install ncurses overwriting curses... yes
checking if external terminfo-database is used... yes
checking which terminfo source-file will be installed... ${top_srcdir}/misc/terminfo.src
checking for list of fallback descriptions...
checking for list of terminfo directories... /etc/terminfo:/usr/share/terminfo
checking for default terminfo directory... /usr/share/terminfo
checking if big-core option selected... yes
checking if you want termcap-fallback support... no
checking if ~/.terminfo is wanted... checking for remove... yes
checking for unlink... yes
checking if link/symlink functions work... link symlink
checking if tic should use symbolic links... yes
checking if you want broken-linker support code... no
checking for type of bool... auto
checking for type of ospeed... short
checking if tputs should process BSD-style prefix padding... no
checking if RCS identifiers should be compiled-in... yes
checking format of man-pages... normal
checking for manpage renaming... no
checking if manpage aliases will be installed... yes
checking if manpage symlinks should be used... yes
checking for manpage tbl... no
checking if you want to build with function extensions... yes
checking for extended use of const keyword... no
checking if you want $NCURSES_NO_PADDING code... yes
checking if you want SIGWINCH handler... yes
checking if you want user-definable terminal capabilities like termcap... yes
checking if you want all development code... no
checking if you want hard-tabs code... no
checking if you want to use restrict environment when running as root... yes
checking if you want limited support for xmc... no
checking if you do not want to assume colors are white-on-black... yes
checking if you want hashmap scrolling-optimization code... yes
checking if you want colorfgbg code... no
checking if you want experimental safe-sprintf code... no
checking if we must define _GNU_SOURCE... yes
checking if you want experimental wide-character code... yes
checking if we must define _XOPEN_SOURCE... no
checking checking for compatible value versus 500... yes
checking if we must define _XOPEN_SOURCE_EXTENDED... no
checking for putwc... yes
checking for btowc... yes
checking for wctob... yes
checking for mbtowc... yes
checking for wctomb... yes
checking for mblen... yes
checking for mbrlen... yes
checking for mbrtowc... yes
checking if we must include wchar.h to declare mbstate_t... yes
checking if we must include wchar.h to declare wchar_t... no
checking if we must include wchar.h to declare wint_t... no
checking for terminal capabilities file... Caps
checking if you want to display full commands during build... yes
checking if you want to see compiler warnings...
configure: checking for gcc __attribute__ directives...
... scanf
... printf
... unused
... noreturn
checking if you want to enable runtime assertions... no
checking whether to add trace feature to all models...
checking for gettimeofday... yes
checking if -lm needed for math functions... yes
checking for ANSI C header files... yes
checking for dirent.h that defines DIR... no
checking for sys/ndir.h that defines DIR... no
checking for sys/dir.h that defines DIR... no
checking for ndir.h that defines DIR... no
checking for opendir in -lx... no
checking whether time.h and sys/time.h may both be included... yes
checking for regular-expression headers... regex.h
checking for fcntl.h... yes
checking for getopt.h... yes
checking for libc.h... no
checking for limits.h... no
checking for locale.h... yes
checking for poll.h... yes
checking for sys/bsdtypes.h... no
checking for sys/ioctl.h... no
checking for sys/param.h... no
checking for sys/poll.h... yes
checking for sys/select.h... yes
checking for sys/time.h... yes
checking for sys/times.h... yes
checking for ttyent.h... yes
checking for unistd.h... yes
checking for wctype.h... yes
checking if sys/time.h works with sys/select.h... yes
checking for gcc option to accept ANSI C... none needed
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking if unsigned literals are legal... yes
checking for type of chtype... long
checking if external errno is declared... no
checking if external errno exists... no
checking if data-only library module links... yes
checking for getcwd... yes
checking for getegid... yes
checking for geteuid... yes
checking for getttynam... yes
checking for issetugid... no
checking for memccpy... yes
checking for nanosleep... yes
checking for poll... yes
checking for remove... (cached) yes
checking for select... yes
checking for setbuf... yes
checking for setbuffer... yes
checking for setvbuf... yes
checking for sigaction... yes
checking for sigvec... yes
checking for strdup... yes
checking for strstr... yes
checking for tcgetpgrp... yes
checking for times... yes
checking for vsnprintf... yes
checking for isascii... yes
checking whether sigaction needs _POSIX_SOURCE... unknown
checking for termio.h... no
checking for termios.h... yes
checking for unistd.h... (cached) yes
checking whether termios.h needs _POSIX_SOURCE... no
checking for tcgetattr... yes
checking for vsscanf function or workaround... vsscanf
checking for working mkstemp... yes
checking whether setvbuf arguments are reversed... no
checking return type of signal handlers... int
checking for type sigaction_t... no
checking declaration of size-change... no
checking for memmove... yes
checking if poll really works... yes
checking if we should include stdbool.h... yes
checking for builtin bool type... no
checking for library stdc++... no
checking how to run the C++ preprocessor... /usr/bin/g++ -E
checking for typeinfo... yes
checking if we should include stdbool.h... (cached) yes
checking for builtin bool type... yes
checking for size of bool... unsigned char
checking for special defines needed for etip.h... none
checking if /usr/bin/g++ accepts parameter initialization... no
checking for strstream.h... no
checking if /usr/bin/g++ supports vscan function... stdio
checking for library subsets... termlib+ext_tinfo+base+widechar+ext_funcs
checking default library suffix... w
checking default library-dependency suffix... w.so
checking default object directory... obj_s
checking c++ library-dependency suffix... w.a
checking where we will install curses.h... ${prefix}/include
checking for src modules... ncurses progs tack panel menu form
configure: creating ./config.status
config.status: creating include/MKterm.h.awk
config.status: creating include/curses.head
config.status: creating include/termcap.h
config.status: creating include/unctrl.h
config.status: creating man/Makefile
config.status: creating include/Makefile
config.status: creating ncurses/Makefile
config.status: creating progs/Makefile
config.status: creating tack/Makefile
config.status: creating panel/Makefile
config.status: creating menu/Makefile
config.status: creating form/Makefile
config.status: creating test/Makefile
config.status: creating misc/Makefile
config.status: creating c++/Makefile
config.status: creating misc/run_tic.sh
config.status: creating Makefile
config.status: creating include/ncurses_cfg.h
Appending rules for shared model (ncurses: termlib+ext_tinfo+base+widechar+ext_funcs)
Appending rules for normal model (ncurses: termlib+ext_tinfo+base+widechar+ext_funcs)
Appending rules for shared model (progs: termlib+ext_tinfo+base+widechar+ext_funcs)
Appending rules for normal model (progs: termlib+ext_tinfo+base+widechar+ext_funcs)
Appending rules for shared model (tack: termlib+ext_tinfo+base+widechar+ext_funcs)
Appending rules for normal model (tack: termlib+ext_tinfo+base+widechar+ext_funcs)
Appending rules for shared model (panel: termlib+ext_tinfo+base+widechar+ext_funcs)
Appending rules for normal model (panel: termlib+ext_tinfo+base+widechar+ext_funcs)
Appending rules for shared model (menu: termlib+ext_tinfo+base+widechar+ext_funcs)
Appending rules for normal model (menu: termlib+ext_tinfo+base+widechar+ext_funcs)
Appending rules for shared model (form: termlib+ext_tinfo+base+widechar+ext_funcs)
Appending rules for normal model (form: termlib+ext_tinfo+base+widechar+ext_funcs)
Appending rules for shared model (test: termlib+ext_tinfo+base+widechar+ext_funcs)
Appending rules for normal model (test: termlib+ext_tinfo+base+widechar+ext_funcs)
Appending rules for shared model (c++: termlib+ext_tinfo+base+widechar+ext_funcs)
Appending rules for normal model (c++: termlib+ext_tinfo+base+widechar+ext_funcs)
creating headers.sh
** Configuration summary for NCURSES 5.4 20040208:
bin directory: /usr/bin
lib directory: /lib
include directory: /usr/include
man directory: /usr/share/man
terminfo directory: /usr/share/terminfo
cd man && make DESTDIR="" sources
make[1]: Entering directory `/var/tmp/portage/ncurses-5.4-r5/work/ncurses-5.4/man'
sh ./MKterminfo.sh ./terminfo.head ./../include/Caps ./terminfo.tail >terminfo.5
make[1]: Leaving directory `/var/tmp/portage/ncurses-5.4-r5/work/ncurses-5.4/man'
cd include && make DESTDIR="" sources
make[1]: Entering directory `/var/tmp/portage/ncurses-5.4-r5/work/ncurses-5.4/include'
cat curses.head >curses.h
AWK=gawk sh ./MKkey_defs.sh ./Caps >>curses.h
sh -c 'if test "cchar_t" = "cchar_t" ; then cat ./curses.wide >>curses.h ; fi'
cat ./curses.tail >>curses.h
sh ./MKhashsize.sh ./Caps >hashsize.h
AWK=gawk sh ./MKncurses_def.sh ./ncurses_defs >ncurses_def.h
AWK=gawk sh ./MKparametrized.sh ./Caps >parametrized.h
gawk -f MKterm.h.awk ./Caps > term.h
sh ./edit_cfg.sh ../include/ncurses_cfg.h term.h
** edit: HAVE_TCGETATTR 1
** edit: HAVE_TERMIOS_H 1
** edit: HAVE_TERMIO_H 0
** edit: BROKEN_LINKER 0
make[1]: Leaving directory `/var/tmp/portage/ncurses-5.4-r5/work/ncurses-5.4/include'
cd ncurses && make DESTDIR="" sources
make[1]: Entering directory `/var/tmp/portage/ncurses-5.4-r5/work/ncurses-5.4/ncurses'
sh ./base/MKlib_gen.sh "gcc -E -DHAVE_CONFIG_H -I../ncurses -I. -I. -I../include-D_GNU_SOURCE -DNDEBUG" "gawk" generated <../include/curses.h | \
fgrep undef >../include/nomacros.h
gawk -f ./tinfo/MKnames.awk ./../include/Caps
cat namehdr boolnames boolfnames numnames numfnames strnames strfnames nameftr >names.c
cat namehdr boolcodes numcodes strcodes codeftr >codes.c
rm -f namehdr nameftr codeftr boolnames boolfnames boolcodes numnames numfnames numcodes strnames strfnames strcodes
gcc -o make_hash -DHAVE_CONFIG_H -I../ncurses -I. -DHAVE_CONFIG_H -I../ncurses -I. -I. -I../include -D_GNU_SOURCE -DNDEBUG -march=i586 -mcpu=i686 -02 -pipe -fomit-frame-pointer -fPIC -DMAIN_PROGRAM ./tinfo/comp_hash.c
gcc: unrecognized option `-02'
In file included from /usr/include/errno.h:36,
from ../ncurses/curses.priv.h:94,
from tinfo/comp_hash.c:40:
/usr/include/bits/errno.h:25:26: linux/errno.h: No such file or directory
In file included from /usr/include/signal.h:326,
from ../ncurses/curses.priv.h:115,
from tinfo/comp_hash.c:40:
/usr/include/bits/sigcontext.h:28:29: asm/sigcontext.h: No such file or directory
In file included from tinfo/comp_hash.c:40:
../ncurses/curses.priv.h:511: error: `MB_LEN_MAX' undeclared here (not in a function)
In file included from tinfo/comp_hash.c:68:
../ncurses/tinfo/doalloc.c: In function `_nc_doalloc':
../ncurses/tinfo/doalloc.c:52: error: `ENOMEM' undeclared (first use in this function)
../ncurses/tinfo/doalloc.c:52: error: (Each undeclared identifier is reported only once
../ncurses/tinfo/doalloc.c:52: error: for each function it appears in.)
make[1]: *** [make_hash] Error 1
make[1]: Leaving directory `/var/tmp/portage/ncurses-5.4-r5/work/ncurses-5.4/ncurses'
make: *** [sources] Error 2
!!! ERROR: sys-libs/ncurses-5.4-r5 failed.
!!! Function src_compile, Line 78, Exitcode 2
!!! make sources failed
|
_________________
Work is punishment for failing to procrastinate effectively.
last.fm |
|
| Back to top |
|
|
bin-doph
Guru
Joined: 23 May 2003
Posts: 302
|
| Posted: Wed Nov 03, 2004 2:34 pm Post subject: |
|
|
| veezi wrote: |
If all will, try to boot into '/bin/sh' (by changing the grub line on livecd boot from 'init=/linuxrc' to 'init=/bin/sh') and manually execute each line in linuxrc to figure out what's going wrong. |
That sounds pretty good, I'll try that
thx
_________________
perl -e '$_=q;4a75737420616e6f74686572205065726c204861636b65720as;;for(s;s;s;s;s;s;s;s;s;s;s;s){s;(..)s?;qq qprint chr 0x$1 and \161 ssq;excess;}' |
|
| Back to top |
|
|
bin-doph
Guru
Joined: 23 May 2003
Posts: 302
|
| Posted: Wed Nov 03, 2004 3:53 pm Post subject: |
|
|
hmmm. if it tries to mount proc I get that error (fstab). after that the cdrom-mount-function ends up in timeoutin
_________________
perl -e '$_=q;4a75737420616e6f74686572205065726c204861636b65720as;;for(s;s;s;s;s;s;s;s;s;s;s;s){s;(..)s?;qq qprint chr 0x$1 and \161 ssq;excess;}' |
|
| Back to top |
|
|
veezi
Apprentice
Joined: 10 Nov 2003
Posts: 226
|
| Posted: Wed Nov 03, 2004 4:26 pm Post subject: |
|
|
| Sounds like your initrd is read only. Are you sure you specified 'rw' in the grub kernel line? |
|
| Back to top |
|
|
veezi
Apprentice
Joined: 10 Nov 2003
Posts: 226
|
| Posted: Wed Nov 03, 2004 4:31 pm Post subject: |
|
|
@Illissius
Sorry, don't have any other hint.
But, really seeams something is broken with your source environment. Double check that you downloaded the right stage2, and double check your make.conf (flags, march, etc.).
Can't think of anything else. 
Good luck |
|
| Back to top |
|
|
Illissius
Guru
Joined: 31 Jul 2004
Posts: 395
Location: Hungary
|
| Posted: Wed Nov 03, 2004 4:58 pm Post subject: |
|
|
Would using an x86 (=i386?) stage2 along with chost=i586-linux-gnu and CFLAGS=-march=i586 -mcpu=i686 cause any problems? I'm at a loss as to what else it could be.
_________________
Work is punishment for failing to procrastinate effectively.
last.fm |
|
| Back to top |
|
|
veezi
Apprentice
Joined: 10 Nov 2003
Posts: 226
|
| Posted: Wed Nov 03, 2004 5:13 pm Post subject: |
|
|
| Illissius wrote: | | Would using an x86 (=i386?) stage2 along with chost=i586-linux-gnu and CFLAGS=-march=i586 -mcpu=i686 cause any problems? I'm at a loss as to what else it could be. |
Not sure if chost of i586 is correct when using an x86 stage2.
For mcpu, people usually advise against it (since it opimizes for a specific architecture, and you don't want that on a livecd).
Why don't you try my combination. It worked fine here:
i686 stage2: http://gentoo.osuosl.org/releases/x86/2004.2/stages/i686/stage2-i686-2004.2.tar.bz2
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=i686 -O3 -pipe -fomit-frame-pointer" |
|
| Back to top |
|
|
Illissius
Guru
Joined: 31 Jul 2004
Posts: 395
Location: Hungary
|
| Posted: Wed Nov 03, 2004 6:59 pm Post subject: |
|
|
The problem with i686 is three out of five of the computers that it'll be used most likely/often on are K6s or P1 equivalents (read: Cyrix).... so guess I'll try straight i386 then.
As for -mcpu, isn't it supposed to be completely backwards compatible with the older stuff while optimized to be faster on newer stuff?
_________________
Work is punishment for failing to procrastinate effectively.
last.fm |
|
| Back to top |
|
|
dcoyaz
n00b
Joined: 09 Mar 2004
Posts: 10
Location: Arizona
|
| Posted: Fri Nov 05, 2004 7:21 am Post subject: |
|
|
| nsahoo wrote: | thanks veezi, you are indeed "tux' lil helper"
edit: is there a way to make sure that the image is alright before burning it onto the cd ? |
Thanks for a great howto veezi
One way is to emerge qemu and then issue a
| Code: | | qemu -cdrom livecd.iso -boot d |
This will allow you to test before burning, and maybe even throwing some qemu options to alter the running hardware.
HTH, |
|
| Back to top |
|
|
nsahoo
l33t
Joined: 17 Jul 2003
Posts: 618
|
| Posted: Fri Nov 05, 2004 5:40 pm Post subject: |
|
|
| dcoyaz wrote: | | nsahoo wrote: | thanks veezi, you are indeed "tux' lil helper"
edit: is there a way to make sure that the image is alright before burning it onto the cd ? |
Thanks for a great howto veezi
One way is to emerge qemu and then issue a
| Code: | | qemu -cdrom livecd.iso -boot d |
This will allow you to test before burning, and maybe even throwing some qemu options to alter the running hardware.
HTH, |
aha, why didn't it occure to me earlier, I can do the same using the vmware that i use.
Thanks |
|
| Back to top |
|
|
Match
Tux's lil' helper
Joined: 22 Mar 2004
Posts: 117
Location: England
|
| Posted: Mon Nov 08, 2004 2:41 pm Post subject: |
|
|
Hey all,
To start off let me say that I'm reasonably new to Linux and Gentoo, having installed my first system back in June and having reinstalled a couple of times since then. I'm eager to learn, but to be honest I don't know that much.
I do, however, understand about half of what has been written in this excellent guide, and just have a few questions.
1) I would like to make a LiveCD that works on most systems, like the Gentoo LiveCD or Knoppix. I gather the best idea would be to use genkernel to configure my kernel - however, that creates its own initrd image which the Handbook says "will be started immediately after booting to perform hardware autodetection (just like on the Live CD) before your 'real' system starts up." Can I just create the initrd as this guide explains and ignore the one created by genkernel? I'd assume yes, but the Handbook says that it "performs hardware autodetection just like on the LiveCD" which is what I want. Does the initrd created above do this also?
2) How would I, having followed the above instructions, then go back and install/upgrade a program for my LiveCD? Is it as simple as just "chroot /source etc., env-update, source /etc/profile, emerge package"? (Obviously I'd then recreate the ISO file.)
3) In this piece of code from the guide
| Code: |
ldd /bin/mount
linux-gate.so.1 => (0xffffe000)
libc.so.6 => /lib/libc.so.6 (0x4002e000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
cp /lib/libc.so.6 /mnt/initrd/lib/
cp /lib/ld-linux.so.2 /mnt/initrd/lib/ |
what is the linux-gate.so.1 thing about, and why don't you copy that as well?
4) Would it be possible to create a splash screen for it such as in https://forums.gentoo.org/viewtopic.php?t=206778 (this is obviously not as important as my other questions; I can do this later, if at all.)
5) Any problems with using gentoo-dev-sources or do you just like the default ones? 
6) What is udev and why might I need it? Bear in mind I don't use it on my normal install, that I know it's an alternative for devfs (or something, not sure) and manages /dev, but not much else. Is it worth me learning about it? Will it increase or decrease the chances of my LiveCD working on other computers?
_________________
O_o |
|
| Back to top |
|
|
nsahoo
l33t
Joined: 17 Jul 2003
Posts: 618
|
| Posted: Mon Nov 08, 2004 5:31 pm Post subject: |
|
|
| Quote: |
1) I would like to make a LiveCD that works on most systems, like the Gentoo LiveCD or Knoppix. I gather the best idea would be to use genkernel to configure my kernel - however, that creates its own initrd image which the Handbook says "will be started immediately after booting to perform hardware autodetection (just like on the Live CD) before your 'real' system starts up." Can I just create the initrd as this guide explains and ignore the one created by genkernel? I'd assume yes, but the Handbook says that it "performs hardware autodetection just like on the LiveCD" which is what I want. Does the initrd created above do this also?
|
I had some confusion at that point as well. But, I ignored the genkernel created initrd and used the one created in this tutorial. Livecd has worked so far on three different system. I guess most of the "auto-detection" work is achieved by having all the kernel modules compiled and hotplug installed. That way kernel can load the required driver module, on the fly. But, I guess someone can give a better answer than this.
| Quote: |
2) How would I, having followed the above instructions, then go back and install/upgrade a program for my LiveCD? Is it as simple as just "chroot /source etc., env-update, source /etc/profile, emerge package"? (Obviously I'd then recreate the ISO file.)
|
You are right. It's that simple. Thanks to Veezi.
| Quote: |
5) Any problems with using gentoo-dev-sources or do you just like the default ones?
|
No problem at all. I use it. With kernel 2.6.9 I had some issues on some system. So, I downgraded it to 2.6.8-r<latest> and removed the video parameter from the kernel line in grub.conf. It has worked fine after that.
| Quote: |
6) What is udev and why might I need it? Bear in mind I don't use it on my normal install, that I know it's an alternative for devfs (or something, not sure) and manages /dev, but not much else. Is it worth me learning about it? Will it increase or decrease the chances of my LiveCD working on other computers?
|
There is nothing much to learn actually. You just have to emerge it like any other package and uncheck dev filesystem support in kernel. Even if you decide to keep the devfs support in kernel, uncheck the automount option right below it. You are good to go. No configuration nothing. |
|
| Back to top |
|
|
Match
Tux's lil' helper
Joined: 22 Mar 2004
Posts: 117
Location: England
|
| Posted: Mon Nov 08, 2004 6:02 pm Post subject: |
|
|
| nsahoo wrote: | [
I had some confusion at that point as well. But, I ignored the genkernel created initrd and used the one created in this tutorial. Livecd has worked so far on three different system. I guess most of the "auto-detection" work is achieved by having all the kernel modules compiled and hotplug installed. That way kernel can load the required driver module, on the fly. But, I guess someone can give a better answer than this.
|
Well, I'll go with what you say and if someone's got a better answer I'd love to hear it also
| Quote: | | No problem at all. I use it. With kernel 2.6.9 I had some issues on some system. So, I downgraded it to 2.6.8-r<latest> and removed the video parameter from the kernel line in grub.conf. It has worked fine after that. |
I shall do as you say
| Quote: |
There is nothing much to learn actually. You just have to emerge it like any other package and uncheck dev filesystem support in kernel. Even if you decide to keep the devfs support in kernel, uncheck the automount option right below it. You are good to go. No configuration nothing. |
I add it to the default runlevel, right? Anyway, I'll try it out on my normal system at some point but I think I'll stick with what I know for this LiveCD
_________________
O_o |
|
| Back to top |
|
|
nsahoo
l33t
Joined: 17 Jul 2003
Posts: 618
|
| Posted: Mon Nov 08, 2004 7:32 pm Post subject: |
|
|
| Match wrote: |
I add it to the default runlevel, right? Anyway, I'll try it out on my normal system at some point but I think I'll stick with what I know for this LiveCD |
No man, you don't even have to do that. It's not a service .. just emerge and uncheck devfs menuconfig and recompile kernel .. if it's unchecked already .. leave it as it is. you are good to go. too easy to believe, eh? but, thats all there is to udevs. |
|
| Back to top |
|
|
Match
Tux's lil' helper
Joined: 22 Mar 2004
Posts: 117
Location: England
|
| Posted: Mon Nov 08, 2004 8:05 pm Post subject: |
|
|
Cool - and the syntax of fstab remains the same?
Another question. I've just got onto creating initrd, and have run the first two commands:
| Code: | touch /boot/initrd
dd if=/dev/zero of=/boot/initrd bs=1024k count=8 |
which have worked fine, I think. However, when I run the next command:
| Code: | | losetup /dev/loop0 /boot/initrd |
I get the message:
| Quote: | | /dev/loop0: No such device or address |
What do I need to do now?
_________________
O_o |
|
| Back to top |
|
|
chunderbunny
Veteran
Joined: 31 May 2004
Posts: 1281
Location: 51°24'27" N, 0°57'15" W
|
| Posted: Mon Nov 08, 2004 8:14 pm Post subject: |
|
|
Your fstab will mostly be the same with the switch to udev, anything relating to hard drives will be unchanged. If you currently use the /dev/cdrom symlink as you cdrom device you will have to replace this entry in your fstab with /dev/cdroms/cdrom0. Another thing to watch out for is that the default mouse device moves to /dev/input/mice, so you might need to adjust your /etc/X11/xorg.conf accordingly.
/dev/loop0 is part of the loopback interface, and needs to be compiled into your kernel as either a built in driver or as a module. The loopback interface option is located in "device drivers > block devices > loopback device support" in your kernel config. |
|
| Back to top |
|
|
|
Documentation, Tips & Tricks
