Some doubts in BLFS system & books.

stoat · 12-29-2014, 08:35 PM

As already suggested above, I think it is very likely that the kernel has the driver for your wired Ethernet device. Try studying the output of lspci -k and lsmod in your host. From that information you might be able to figure out the module(s) needed by the card. Then find out if it(they) is(are) enabled in your LFS kernel. If not then compile a new kernel. In the kernel config editor (menuconfig), the Ethernet stuff will be found in Device Drivers ---> Network device support ---> Ethernet driver support.

veerain · 12-29-2014, 08:52 PM

Nowadays systemd is used instead of consolekit.

For ethernet Virtual box ethernet drivers are supported by Linux Kernel.

But you should have enabled drivers for it when building the Linux Kernel.

And I say if your host is connected to internet then you would not have to use ethernet for accessing internet.

ReaperX7 · 12-29-2014, 08:59 PM

You can use ConsoleKit still as the book still uses it quite well. ConsoleKit2 has been added to the future include list as well.

Unless you need the package however, just ignore it.

The only case where you may want to use optional dependencies are multimedia packages and desktop utilities.

As far as drivers, just cheat and use the latest testing kernel config from Slackware-Current. It's your best option.

paletroxz · 12-29-2014, 10:23 PM

Quote:

Originally Posted by stoat

As already suggested above, I think it is very likely that the kernel has the driver for your wired Ethernet device. Try studying the output of lspci -k and lsmod in your host. From that information you might be able to figure out the module(s) needed by the card. Then find out if it(they) is(are) enabled in your LFS kernel. If not then compile a new kernel. In the kernel config editor (menuconfig), the Ethernet stuff will be found in Device Drivers ---> Network device support ---> Ethernet driver support.

Bro thanks it worked I'm now having a working eth0 driver. I won't forget this help. Thanks again bro.

paletroxz · 12-30-2014, 04:11 AM

Hello again guys but does iptables screwup the internet connection? I installed it and now it seems like BLFS system doesn't even ping... Any suggestions?

spiky0011 · 12-30-2014, 04:29 AM

Hi

Did you read this page
http://www.linuxfromscratch.org/blfs.../firewall.html

Also google iptable rules

stoat · 12-30-2014, 10:40 AM

Quote:

Originally Posted by paletroxz

I installed it and now it seems like BLFS system doesn't even ping... Any suggestions?

As root, iptables -L will output the iptables rules in force. I don't think the generic rules offered in the BLFS book will create a problem if the underlying connection is working.

Maybe it's your dhcp configuration. Try confirming that the interface has an IP address with /sbin/ifconfig. That should display an inet addr for the eth0 interface. If there is no inet addr for eth0, then nothing will go until that is fixed. Try backing up to a simple static IP address (LFS chapter 7). IMO, it's easier to troubleshoot and untangle a simple static connection. Once static connection details are understood and removed as a possible confounding issue, the dhcp stuff might be easier to get right.

paletroxz · 12-30-2014, 11:01 AM

I installed fluxbox as windows manager, gnome as desktop environment & installed some x windows software that were required. But when I boot into my BLFS system and type startx I get this error:

Code:

-bash startx:command not found

And so when I searched online I found out that I need to install xinit for it to work. And xTerm is required so while trying to install it I came across Xorg Applications in which I get the following error at x11perf:

Code:

/sources/app
/sources/app/x11perf-1.5.4 /sources/app
configure: WARNING: unrecognized options: --disable-static
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for gcc... gcc
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... no
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 ISO C89... none needed
checking dependency style of gcc... gcc3
checking for gcc option to accept ISO C99... -std=gnu99
checking how to run the C preprocessor... gcc -std=gnu99 -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether __clang__ is declared... no
checking whether __INTEL_COMPILER is declared... no
checking whether __SUNPRO_C is declared... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking if gcc -std=gnu99 supports -Werror=attributes... no
checking return type of signal handlers... void
checking for mktemp... /usr/bin/mktemp
checking for X11PERF... yes
checking for XRENDER... yes
checking for XFT... yes
checking for XEXT... yes
checking for XShmQueryExtension... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating man/Makefile
config.status: creating config.h
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --disable-static
make  all-recursive
make[1]: Entering directory '/sources/app/x11perf-1.5.4'
Making all in man
make[2]: Entering directory '/sources/app/x11perf-1.5.4/man'
  GEN    x11perfcomp.1
  GEN    x11perf.1
  GEN    Xmark.1
make[2]: Leaving directory '/sources/app/x11perf-1.5.4/man'
make[2]: Entering directory '/sources/app/x11perf-1.5.4'
  CC     bitmaps.o
  CC     do_arcs.o
  CC     do_blt.o
  CC     do_complex.o
  CC     do_dots.o
  CC     do_lines.o
  CC     do_movewin.o
  CC     do_rects.o
  CC     do_segs.o
  CC     do_simple.o
  CC     do_tests.o
  CC     do_text.o
  CC     do_traps.o
  CC     do_tris.o
  CC     do_valgc.o
  CC     do_windows.o
  CC     x11perf.o
  CCLD   x11perf
  GEN    x11perfcomp
make[2]: Leaving directory '/sources/app/x11perf-1.5.4'
make[1]: Leaving directory '/sources/app/x11perf-1.5.4'
Making install in man
make[1]: Entering directory '/sources/app/x11perf-1.5.4/man'
make[2]: Entering directory '/sources/app/x11perf-1.5.4/man'
make[2]: Nothing to be done for 'install-exec-am'.
test -z "/usr/share/man/man1" || /bin/mkdir -p "/usr/share/man/man1"
 /usr/bin/install -c -m 644 x11perfcomp.1 x11perf.1 Xmark.1 '/usr/share/man/man1'
make[2]: Leaving directory '/sources/app/x11perf-1.5.4/man'
make[1]: Leaving directory '/sources/app/x11perf-1.5.4/man'
make[1]: Entering directory '/sources/app/x11perf-1.5.4'
make[2]: Entering directory '/sources/app/x11perf-1.5.4'
test -z "/usr/bin" || /bin/mkdir -p "/usr/bin"
  /usr/bin/install -c x11perf '/usr/bin'
test -z "/usr/bin" || /bin/mkdir -p "/usr/bin"
 /usr/bin/install -c x11perfcomp '/usr/bin'
test -z "/usr/lib/X11/x11perfcomp" || /bin/mkdir -p "/usr/lib/X11/x11perfcomp"
/bin/mkdir: cannot create directory ‘/usr/lib/X11’: Too many levels of symbolic links
Makefile:477: recipe for target 'install-dist_x11perfcompSCRIPTS' failed
make[2]: *** [install-dist_x11perfcompSCRIPTS] Error 1
make[2]: Leaving directory '/sources/app/x11perf-1.5.4'
Makefile:878: recipe for target 'install-am' failed
make[1]: *** [install-am] Error 2
make[1]: Leaving directory '/sources/app/x11perf-1.5.4'
Makefile:558: recipe for target 'install-recursive' failed
make: *** [install-recursive] Error 1

Previously on my first BLFS trial I got this error but I keep getting this error still. It says "Too many levels of symbolic links" so is there any way to force it? I mean inside the "for" used inside the new bash shell??

ReaperX7 · 12-30-2014, 11:08 AM

It means you tried to setup x11 using the alternative paths, and it hardlinked against your main system somehow.

spiky0011 · 12-30-2014, 12:04 PM

Hi

This page
http://www.linuxfromscratch.org/blfs...n/x/x7lib.html

at the bottom, the symlinks, you will have to delete the symlinks

paletroxz · 12-31-2014, 05:56 AM

Thanks mates now I've everything setup, except for the UI part. I installed IceWM and GNOME DE and after I login and type "startx" or "xinit" I get the following error:

Code:

xinit: unable to run server "/usr/bin/X": No such file or directory
Use the -- option, or make sure that /usr/bin is in your path and
that "/usr/bin/X" is a program or a link to the right type of server
for your display.  Possible server names include:

    Xorg        Common X server for most displays
    Xvfb        Virtual frame buffer
    Xfake       kdrive-based virtual frame buffer
    Xnest       X server nested in a window on another X server
    Xephyr      kdrive-based nested X server
    Xvnc        X server accessed over VNC's RFB protocol
    Xdmx        Distributed Multi-head X server

Invalid MIT-MAGIC-COOKIE-1 keyxinit: giving up
xinit: unable to connect to X server: Resource temporarily unavailable
xinit: server error

ReaperX7 · 12-31-2014, 08:53 AM

Did you install all the packages from the X chapter?

paletroxz · 12-31-2014, 09:59 AM

Yes I did.

ReaperX7 · 12-31-2014, 06:56 PM

Okay did you do ANYTHING, even in the slightest, different from the book?

paletroxz · 12-31-2014, 08:15 PM

No sir. Since I always mess things up, for safety I followed the book exactly.