Stage 1/3 Installation Support - Gentoo 2004.3 & GCC 343

[dedeaux]

I have done a successful Stage3/1 install today.
Two notes :
-I had the /etc/mtab problem. It was quickly solved by a cp /proc/mounts /mnt/gentoo/etc/mtab (on the LiveCD), as many people seem to be affected by this problem, may I suggest you put a note in your howto reminding the users to check this.
- my root partition (jfs) wouldn't mount rw, until I discovered I had stupidly left the notail option in the fstab for it (jfs doesn't support notail, and therefore the partition wouldn't mount rw).
Other than that it went pretty fine and I now have a new shiny system (my previous one was crashed into oblivion by a massive file corruption caused by reiserfs, which is why I went for jfs (well-tried fs, eats less ram than xfs, and faster than ext3, plus I never tried it before and I like trying new software ).

Good notes -- thanks. I actually haven't had time to resurrect the intall yet -- maybe this afternoon.

[Master One]

Don't use Reiser4 with this installation method. Although it is possible to perform a Stage 1/3 installation with Reiser4, quite a few deviations from the guide are necessary and the installation is subject to many potential pitfalls. My recommendation would be to drop Reiser 4. You can't do it with this Guide as it is written, and this Guide doesn't support it.

I can tell, that using this revolutionary installation method (thank's a lot, Bob P, for writing your guide) does absolutely work out fine with Reiser4. The only variations in the install process are:

- used lxnay's fabulous liveCD instead of the Gentoo liveCD
- used nitro-sources instead of gentoo-dev-sources

There is really nothing more about it. The installation medium (so which liveCD) does not have any effect at all for the installation itself, because it all depends on only the right stage3-tarball.

Besides that, I only can give the same tip, as Bob P already gave a lot of times: Stick exactly with the described install procedure, then everything should be alright.

[Bob P]

I can tell, that using this revolutionary installation method (thank's a lot, Bob P, for writing your guide) does absolutely work out fine with Reiser4. The only variations in the install process are:

- used lxnay's fabulous liveCD instead of the Gentoo liveCD
- used nitro-sources instead of gentoo-dev-sources

There is really nothing more about it. The installation medium (so which liveCD) does not have any effect at all for the installation itself, because it all depends on only the right stage3-tarball.

Besides that, I only can give the same tip, as Bob P already gave a lot of times: Stick exactly with the described install procedure, then everything should be alright.

thanks for clarifying that point with Reiser 4. DrWoland had told me that he had used a different Live CD and a different kernel, but i had completely forgotten the details.

[dedeaux]

After inspection there were quite a few files that needed updating via etc-update. I was booting with the 2004.3 cd and chrooting to look around. After doing the etc update process and making sure nothing was overwritten that I needed I exited the chroot and unmount and rebooted and was welcomed with a clean boot w/o the errors. That is all I did. I had been reading the forums about the rc-splash issues, but none matched close enough to my problem. So...

Thanks for the guide. My laptop is grinding away at gnome right now.

[rh6866]

I've finished the install Stage 1 on 3 by Bob P and also encountered the same problem upon boot as the 4 or more others encountered.

* Checking root filesystem [ok]
Failed to open the device '/dev/hda1': No such file or directory

/sbin/rc:line 250: rc_splash:command not found
* Filesystem couldn't be fixed Sad [!!]

/dev/console: No such file or directory
Give root password for maintenance
(or type Control-D for normal startup)

I rebooted to the live cd and ran the make menuconifg again just to check if there may have been something I missed. Then ran the

make && make modules && make modules_install && make install

again to ensure it ran properly.

I was able to get a sucessful reboot to grub and chose the 768x1024 which is what my laptop supports.

The first boot got me a login prompt where I was able to login and su -, but there were several errors after it got past the starting init 3 section of bootup. The errors were not able to load the netconfig, usb and others. I did not write them down. Sorry.

I rebooted the machine just to see if I get the errors again. It does produce the errors at the same part of the boot process but the screen now goes black and I can't get any information to write down the errors.

I have rebooted again with the live cd and am connected from this pc using ssh with putty. Please tell me if there is a log file or something that is created at boot that I can get to so I can see exactly what these errors are and give you more information to help me.

My emerge --info

livecd / # emerge --info
Portage 2.0.51-r15 (default-linux/x86/2004.3, gcc-3.4.3-20050110, glibc-2.3.4.20050125-r0, 2.6.9-rc1-mm5-livecd i686)
=================================================================
System uname: 2.6.9-rc1-mm5-livecd i686
Gentoo Base System version 1.4.16
Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 26 2005, 15:30:13)]
dev-lang/python: 2.3.4-r1
sys-devel/autoconf: 2.13, 2.59-r6
sys-devel/automake: 1.5, 1.8.5-r3, 1.6.3, 1.7.9-r1, 1.4_p6, 1.9.4
sys-devel/binutils: 2.15.92.0.2-r1
sys-devel/libtool: 1.5.10-r4
virtual/os-headers: 2.6.8.1-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -march=pentium3m -fforce-addr -momit-leaf-frame-pointer -fomit-frame-pointer -ftracer -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=pentium3m -fforce-addr -momit-leaf-frame-pointer -fomit-frame-pointer -ftracer -pipe -fvisibility-inlines-hidden"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms"
GENTOO_MIRRORS="http://mirrors.datapipe.net/gentoo http://gentoo.osuosl.org http://www.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X acpi apm arts avi berkdb bitmap-fonts crypt cups emboss encode f77 font-server foomaticdb fortran gdbm gif gnome gpm gtk gtk2 imlib ipv6 ithreads jpeg kde ldap libg++ libwww mad mikmod motif mpeg ncurses nls nptl oggvorbis opengl oss pam pdflib perl png pthreads python qt quicktime readline samba sdl spell ssl svga tcpd truetype truetype-fonts type1-fonts xml2 xmms xv zlib"
Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS

Anything else you require please let me know what and where it is.

Thanks,

Rick

BTW, I'm running ext2 on /boot and ext3 on / and /home. I ran into issues in the past trying to get this install working with using ReiserFS that made me believe my HD was going bad. Just to test this before I went out and bought another HD I used the handbooks default fs's. I had previously installed Gentoo using the handbook a couple of times before without HD issues.

[rh6866]

Here is also the dmesg. It doesn't list any of the errors at the end of the last boot without the live cd. Could the one have been generated from booting the live cd?

Rick

livecd / # dmesg
Linux version 2.6.9-rc1-mm5-livecd (root@mars) (gcc version 3.3.3 20040412 (Gentoo Linux 3.3.3-r6, ssp-3.3.2-2, pie-8.7.6)) #1 Thu Sep 16 07:16:08 UTC 2004
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 0000000000100000 - 000000001ffea800 (usable)
BIOS-e820: 000000001ffea800 - 0000000020000000 (reserved)
BIOS-e820: 00000000feea0000 - 00000000fef00000 (reserved)
BIOS-e820: 00000000ffb80000 - 0000000100000000 (reserved)
511MB LOWMEM available.
On node 0 totalpages: 131050
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 126954 pages, LIFO batch:16
HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
ACPI: RSDP (v000 DELL ) @ 0x000fde50
ACPI: RSDT (v001 DELL CPi R 0x27d30303 ASL 0x00000061) @ 0x000fde64
ACPI: FADT (v001 DELL CPi R 0x27d30303 ASL 0x00000061) @ 0x000fde90
ACPI: DSDT (v001 INT430 SYSFexxx 0x00001001 MSFT 0x0100000e) @ 0x00000000
ACPI: PM-Timer IO Port: 0x808
Built 1 zonelists
Initializing CPU#0
Kernel command line: initrd=gentoo.igz root=/dev/ram0 init=/linuxrc looptype=zisofs loop=/zisofs pci=routeirq cdroot vga=791 splash=silent BOOT_IMAGE=gentoo ide=nodma
ide_setup: ide=nodmaIDE: Prevented DMA
PID hash table entries: 2048 (order: 11, 32768 bytes)
Detected 996.674 MHz processor.
Using pmtmr for high-res timesource
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 510112k/524200k available (4957k kernel code, 13528k reserved, 1953k data, 252k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 1978.36 BogoMIPS (lpj=989184)
Security Scaffold v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0383fbff 00000000 00000000 00000000
CPU: After vendor identify, caps: 0383fbff 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU: After all inits, caps: 0383fbff 00000000 00000000 00000040
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel(R) Pentium(R) III Mobile CPU 1000MHz stepping 01
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
ACPI: IRQ9 SCI: Edge set to Level Trigger.
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 1106k freed
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfc06e, last bus=2
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040816
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 *11)
ACPI: PCI Interrupt Link [LNKB] (IRQs *5 7)
ACPI: PCI Interrupt Link [LNKC] (IRQs 9 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 *10 11)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIE._PRT]
ACPI: Power Resource [PADA] (on)
Linux Plug and Play Support v0.97 (c) Adam Belay
SCSI subsystem initialized
Linux Kernel Card Services
options: [pci] [cardbus] [pm]
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
** Routing PCI interrupts for all devices because "pci=routeirq"
** was specified. If this was required to make a driver work,
** please email the output of "lspci" to bjorn.helgaas@hp.com
** so I can fix the driver.
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
ACPI: PCI interrupt 0000:00:1f.2[D] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5
ACPI: PCI interrupt 0000:02:03.0[A] -> GSI 5 (level, low) -> IRQ 5
ACPI: PCI interrupt 0000:02:06.0[A] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI interrupt 0000:02:06.1[A] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI interrupt 0000:02:0f.0[A] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI interrupt 0000:02:0f.1[A] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI interrupt 0000:02:0f.2[A] -> GSI 10 (level, low) -> IRQ 10
Machine check exception polling timer started.
gx-suspmod: error: no MediaGX/Geode processor found!
cpufreq: Intel(R) SpeedStep(TM) for this chipset not (yet) available.
audit: initializing netlink socket (disabled)
audit(1109484844.179:0): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Coda Kernel/Venus communications, v6.0.0, coda@cs.cmu.edu
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
NTFS driver 2.1.17 [Flags: R/O].
QNX4 filesystem 0.2.3 registered.
SGI XFS with ACLs, security attributes, large block numbers, no debug enabled
SGI XFS Quota Management subsystem
Initializing Cryptographic API
vesafb: framebuffer at 0xe0000000, mapped to 0xe0880000, size 3072k
vesafb: mode is 1024x768x16, linelength=2048, pages=1
vesafb: protected mode interface info at c000:d690
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
ACPI: AC Adapter [AC] (on-line)
ACPI: Battery Slot [BAT0] (battery absent)
ACPI: Battery Slot [BAT1] (battery present)
ACPI: Lid Switch [LID]
ACPI: Power Button (CM) [PBTN]
ACPI: Sleep Button (CM) [SBTN]
ACPI: Processor [CPU0] (supports C1 C2)
ACPI: Thermal Zone [THM] (74 C)
lp: driver loaded but no devices found
Real Time Clock Driver v1.12
ppdev: user-space parallel port driver
Linux agpgart interface v0.100 (c) Dave Jones
i8042: ACPI [KBC] at I/O 0x60, 0x64, irq 1
i8042: ACPI [PS2M] at irq 12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
parkbd: no such parport
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
parport0: PC-style at 0x378 (0x778) [PCSPP(,...)]
parport0: irq 7 detected
lp0: using parport0 (polling).
floppy: ACPI [FDC0] at I/O 0x3f2-0x3f5, 0x3f7 irq 6 dma channel 2
Using anticipatory io scheduler
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH2M: IDE controller at PCI slot 0000:00:1f.1
ICH2M: chipset revision 3
ICH2M: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xbfa0-0xbfa7, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xbfa8-0xbfaf, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: TOSHIBA MK4019GAX, ATA DISK drive
hdb: MATSHITA CD-RW UJDA330, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
Probing IDE interface ide1...
Probing IDE interface ide2...
ide2: Wait for ready failed before probe !
Probing IDE interface ide3...
ide3: Wait for ready failed before probe !
Probing IDE interface ide4...
ide4: Wait for ready failed before probe !
Probing IDE interface ide5...
ide5: Wait for ready failed before probe !
hda: max request size: 128KiB
hda: 78140160 sectors (40007 MB), CHS=65535/16/63
hda: cache flushes supported
/dev/ide/host0/bus0/target0/lun0: p1 p2 p3 p4
hdb: ATAPI 24X CD-ROM CD-R/RW drive, 2048kB Cache
Uniform CD-ROM driver Revision: 3.20
st: Version 20040403, fixed bufsize 32768, s/g segs 256
osst :I: Tape driver with OnStream support version 0.99.1
osst :I: $Id: osst.c,v 1.70 2003/12/23 14:22:12 wriede Exp $
ieee1394: Initialized config rom entry `ip1394'
ohci1394: $Rev: 1226 $ Ben Collins <bcollins@debian.org>
ACPI: PCI interrupt 0000:02:0f.2[A] -> GSI 10 (level, low) -> IRQ 10
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[10] MMIO=[f8ffc800-f8ffcfff] Max Packet=[2048]
video1394: Installed video1394 module
ieee1394: raw1394: /dev/raw1394 device initialized
sbp2: $Rev: 1231 $ Ben Collins <bcollins@debian.org>
ip1394: $Rev: 1231 $ Ben Collins <bcollins@debian.org>
ip1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard on isa0060/serio0
input: ImPS/2 Generic Wheel Mouse on isa0060/serio1
I2O Core - (C) Copyright 1999 Red Hat Software
i2o: max_drivers=4
I2O configuration manager v 0.04.
(C) Copyright 1999 Red Hat Software
I2O Block Storage OSM v0.9
(c) Copyright 1999-2001 Red Hat Software.
I2O SCSI Peripheral OSM
device-mapper: 4.1.0-ioctl (2003-12-10) initialised: dm@uk.sistina.com
Advanced Linux Sound Architecture Driver Version 1.0.6 (Sun Aug 15 07:17:53 2004 UTC).
ALSA device list:
No soundcards found.
oprofile: using NMI interrupt.
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
arp_tables: (C) 2002 David S. Miller
NET: Registered protocol family 1
NET: Registered protocol family 17
ACPI: (supports S0 S1 S3 S4 S4bios S5)
ACPI wakeup devices:
LID PBTN PCI0 UAR1 USB0 PCIE MPCI
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 252k freed
ieee1394: Host added: ID:BUS[0-00:1023] GUID[324fc0000d49ac21]
cdrom: hdb: mmc-3 profile capable, current profile: 8h
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
ACPI: PCI interrupt 0000:02:06.0[A] -> GSI 10 (level, low) -> IRQ 10
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
0000:02:06.0: 3Com PCI 3c556 Laptop Tornado at 0xe800. Vers LK1.1.19
hw_random: RNG not detected
ACPI: PCI interrupt 0000:02:03.0[A] -> GSI 5 (level, low) -> IRQ 5
maestro3: enabled hack for 'Dell Inspiron 8100'
agpgart: Detected an Intel i815 Chipset.
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: AGP aperture is 64M @ 0xe8000000
hw_random: RNG not detected
USB Universal Host Controller Interface driver v2.2
ACPI: PCI interrupt 0000:00:1f.2[D] -> GSI 10 (level, low) -> IRQ 10
uhci_hcd 0000:00:1f.2: Intel Corp. 82801BA/BAM USB (Hub #1)
PCI: Setting latency timer of device 0000:00:1f.2 to 64
uhci_hcd 0000:00:1f.2: irq 10, io base 0xdce0
uhci_hcd 0000:00:1f.2: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
PCI: Enabling device 0000:02:0f.0 (0000 -> 0002)
ACPI: PCI interrupt 0000:02:0f.0[A] -> GSI 10 (level, low) -> IRQ 10
Yenta: CardBus bridge found at 0000:02:0f.0 [1028:00e6]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:02:0f.0, mfunc 0x05033002, devctl 0x64
Yenta: ISA IRQ mask 0x0098, PCI irq 10
Socket status: 30000006
PCI: Enabling device 0000:02:0f.1 (0000 -> 0002)
ACPI: PCI interrupt 0000:02:0f.1[A] -> GSI 10 (level, low) -> IRQ 10
Yenta: CardBus bridge found at 0000:02:0f.1 [1028:00e6]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:02:0f.1, mfunc 0x05033002, devctl 0x64
Yenta: ISA IRQ mask 0x0098, PCI irq 10
Socket status: 30000010
ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ACPI: PCI interrupt 0000:02:06.0[A] -> GSI 10 (level, low) -> IRQ 10
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 774640k swap on /dev/hda2. Priority:-1 extents:1
spurious 8259A interrupt: IRQ7.

[kimchi_sg]

I've finished the install Stage 1 on 3 by Bob P and also encountered the same problem upon boot as the 4 or more others encountered.

* Checking root filesystem [ok]
Failed to open the device '/dev/hda1': No such file or directory

/sbin/rc:line 250: rc_splash:command not found
* Filesystem couldn't be fixed Sad [!!]

/dev/console: No such file or directory
Give root password for maintenance
(or type Control-D for normal startup)

Read this: http://forums.gentoo.org/viewtopic-p-21 ... ml#2128409

Hint: This is NOT not a link to a post that is NOT not posted earlier in this topic.

Also, please DON'T don't use the [code] ... [/code] BBCode tags to enclose everything that is displayed on the screen, for example: [code] my interesting boot error message here [/code]

[Sheepdogj15]

spurious 8259A interrupt: IRQ7.

i've seen this before. to be honest i don't remember if it caused any problems for me, but it could be a contributing factor. basically there seems to be an IRQ conflict or something. i recall trying to search for info on IRQ issues in Gentoo, but i didn't come up with anything.

a work around that will get rid of this error is to disable your parallel port, as that is on this IRQ by default. you'd have to go into your BIOS on next boot and in there should be a setting for it. in fact, if it were me, i'd disable any serial ports as well. you'd only need these if you have a legacy peripherals you want to use, like an ancient printer or a blazing fast 14K external modem.

[eerok]

Stick exactly with the described install procedure, then everything should be alright.

I've had good luck so far with this installation method. I'm comparing it side-by side with a stage3 install, but it's too early to tell whether it's all that much faster on a machine that's fast to begin with (p4 3GHz Xeon w. 2GB ram). Mostly I was driven by curiosity and extra hard drive space.

One thing for sure: after two weeks with gentoo, I've become very fond of it.

Once I'm done setting everything up, I'm open to suggestions for trying some benchmarks to compare the stage3 and 1-on-3 more objectively.

[96140]

I believe I have found a way to solve the problems many of us have had while following this install method. Though there is precious little information on these forums (and most of it directed to users with SATA drives) on solving our reboot problems, I believe my solution will work for both SATA and ATA folks. This is basically a one-size-fits-all (hopefully) solution that combines advice given in this thread and workarounds I found throughout the forums.

First, DO NOT go on to Step 9.9 (unmounting and rebooting) in the guide. If you have to, run the LiveCD and chroot into your Gentoo environment, mounting /mnt/gentoo and all that.

Second, make sure that in your kernel configuration process, you enable support for devfs, but DO NOT have it automount at boot. There's an offchance that one or more of your devices will think they'll need it, even though the system will be running pure udev. This fools them into compliance! Also, make sure you enable support for initrd, as this is what framebuffer will use when you boot. Even though this option's help page says nothing of GRUB usage, I assure you that it is necessary!

Third, run etc-update:

Code: Select all

etc-update

This will come up with a list of about 10 config files that still need manual editing. However, I'm happy to report that I'm almost certain that every file only needs to be overwritten with the most recent version created. This makes sense; as you emerged packages, new configs were written. This etc-update step really should be in the guide (toward the end), as we want our new Gentoo system to use settings that aren't broken or outdated.

Fourth, change back to your / directory. If you're following the gudie and haven't chrooted back in, most likely you are still in /boot/grub. Now that we have a good idea of where we are in relation to our mountpoint, we're going to follow the Official udev Guide's troubleshooting for /dev/console and/or /dev/null errors. Even if these aren't listed in your error messages (for those of you that have tried and failed installation), it doesn't hurt to do this as extra insurance. I'll repeat the steps here:

Code: Select all

# cd /
# mkdir test
# mount --bind / test
# cd test/dev
# ls | less

A long line of devices will come up, but we're looking for console and null. Even if you find them, continue with the instructions, just to make sure they stick around after rebooting.

Code: Select all

# mknod -m 660 console c 5 1
# mknod -m 660 null c 1 3

Even if you get warnings that the devices already exist, re-create them anyway. Next, we unmount test and delete it:

Code: Select all

# cd ../..
# umount test
# rmdir test

Fifth, examine the contents of /etc/mtab (nano /etc/mtab works nicely). Chances are, you'll only see one partition listed; in my case, I only saw /dev/hda4, which was /. As we need our other partitions though, do this:

Code: Select all

# cp /proc/mounts /mnt/gentoo/etc/mtab

I admit this step scared me, as I took a look at /proc/mounts beforehand and saw a lot of things that I wouldn't need, as it lists the various filesystems in use by the LiveCD, but as /etc/mtab is dynamically created, none of the unnecessary information hangs around after rebooting, so this step is safe.

Finally, you may continue with Step 9.9 of the guide; unmount your partitions and reboot! Assuming that you took all these fixes into account, have placed your partitions correctly in fstab and GRUB, and haven't had any errors NOT mentioned yet in this thread, this should fix your problems. But I'm not responsible if it doesn't; this is only an answer to the most common reboot error messages.

[Cpoc]

It makes me happy to read your post and to see that you had problems, that you had to compile your kernel 6 times before you got it right, and that you had the determination to stick with the problem until you solved it. that is exactly what everyone has to do, and i think that a lot of new linux users find configuring the kernel to be a very imposing task. most of them give up, either bailing out or expecting someone else to solve the problem for them instead of seeing the problem through. this guide isn't for everyone, and maybe those users who don't want to spend the effort properly configuring their kernel would be better off following the Gentoo Installation Handbook and using genkernel.

We will have to see what the dev's have in store for us for the next Gentoo install version. Until then I'm stcking with your install method (stage 1/3).

My experience has been that the Stage 1/3 installation method takes a loooong time on older hardware, but it the result is a surprisingly fast system. I have many old Pentium-class boxen that were rescued from a trip to the landfills, and given a new breath of life by a Gentoo Stage 1/3 installation. You're right, on those machines Win 98 has too many problems. Win 2k is not a bad solution, but XP is just too bloated to run on them. Gentoo makes them very useful. Granted, you need a modern HD subsystem and you really need to fill them up with RAM, but they become highly useful platforms under Gentoo.

I recycle PC's all the time. Most of them give way too many issues from 98 installs and Win2000 may work on some of these PC's but as soon as you add a anti-virus it just truns the system into a crawl and you can just forget Xp on these old systems. You right my Gentoo is really fast considered that its working on a P2. Also most older PC run just fine on Gentoo as long as you give it some more[ ram. When I boot from my laptop the boot time is not bad at all in fact it's even quicker than my 1.4 gig with Xp system I have. With Win 2000 it would take sooooo long I just stopped using it untill Gentoo raised it from its dusty grave.

It's funny how I'm using this PC more than my 1 Gig laptop. Everytime I use Gentoo I learn something new.

I really recommend Gentoo for newbies because it forces you to learn. I have tried other distros like Red Hat, Mandrake Lindows, but I did not learn anything from them at all. In fact I have dusted of an old Linux book called "Linux the Complete Reference from Sybex" I know this is an old book but you know what after installing 2 Gentoo systems I can read this book now. The funny thing is it making sence to me. This book is great for general Linux questions. With Gentoo man pages and of course this forum are great. I have no idea why some pople would be afraid of compiling the kernel. The truth is its really easy. Sometimes I fire up the kernel config and just goes through all the options and eveytime I find sometime new. I still belive the best way to learn is the hands on approach. Sometimes this can be very frustrating. I just take a step back and try again another day. Linux is not for eveybody. The more I use it the more it's suiting my needs. This is from a n00b with no Linux, Unix experience at all just from DOS experience a long time ago back in the 386 days.

So thanks for the kind words from a n00b. I'll still be a n00b from some time to come but I'm learning.

I have 1 question that is off topic. I would like to install software raid 1 with your install method for a small file server I'm setting up. Do I just do a reguler install then add the raid support later on I have read that this can be done since all your doing is rebuilding the drive to another disk and adding support in the kernel and a few config files in /etc. This is what I was thinking of doing.

Any tips for this type of install.

Thanks again

[Bob P]

When I boot from my laptop the boot time is not bad at all in fact it's even quicker than my 1.4 gig with Xp system I have. With Win 2000 it would take sooooo long I just stopped using it untill Gentoo raised it from its dusty grave.

yes, its funny that newer PCs with XP don't seem as responsive as some of the older PCs can be with Gentoo. I'm not sure, but I'd guess that its because XP just squanders your resources to the point that you lose all of the benefits of buying faster hardware. I'm not trying to bash XP -- I have to use it for some apps -- but I have never been very fond of any version of Windows, as I have always felt like I have lost control over the OS.

I really recommend Gentoo for newbies because it forces you to learn.

in many respects i agree with you -- if you really want to learn linux, Gentoo is a good distro. but i think that this install method isn't necessarily the best way to go for n00bs -- after all, look at all of the problems that people run into because of kernel misconfiguration. getting the kernel right requires that you know your PC's hardware in depth. most people haven't attained a state of oneness with all of the hardware in their PC, and this is a definite must when it comes to kernel building. its no wonder that the neos get tripped up there...

[Bob P]

I have 1 question that is off topic. I would like to install software raid 1 with your install method for a small file server I'm setting up. Do I just do a reguler install then add the raid support later on I have read that this can be done since all your doing is rebuilding the drive to another disk and adding support in the kernel and a few config files in /etc. This is what I was thinking of doing.

a mirrored system would be a good way to go for a small raid server, as the overhead requirements for 0, 1, and 0/1 aren't that high. you could get by with software raid and your disk I/0 should still be able to overdrive the 110Mbps ethernet interface.

if i were setting up a RAID server for a small LAN, i would modify the paradigm somewhat -- if you're doing this with older hardware (i'm guessing that you are based on your comments about recycling old gear), then i would build a hybrid system. this kind of setup would use RAID 1 on your data partitions, and RAID 0 on your system partitions. you can get away with a setup like this because, unlike windows which handles raid at the device level, linux can handle raid at the partition level.

there are some good examples of how to set up these various types of raid systems in the Docs forum. to adapt to is using this install method, i'd just to the complete installation of the file system using the raid guides, build from a stage 3 tarball, and then rebuild the system like you do in this guide. unfortunately, that type of install really is pretty far off topic, and really deserves its own thread.

[Cpoc]

in many respects i agree with you -- if you really want to learn linux, Gentoo is a good distro. but i think that this install method isn't necessarily the best way to go for n00bs -- after all, look at all of the problems that people run into because of kernel misconfiguration. getting the kernel right requires that you know your PC's hardware in depth. most people haven't attained a state of oneness with all of the hardware in their PC, and this is a definite must when it comes to kernel building. its no wonder that the neos get tripped up there...

This is true but I learned so much in so little time. I did learn about the dmegs|less command from the Live CD. From there it was easier to configure the kernel to my needs. I still feel that if it wasn't for Gentoo I would not be able to learn so much. Sure sometimes I wanted to pull all my hair out and just screem but hey that's part of the learning process. I just stepped back and read your guide over and over again. I liked you comments it was from these comments I was understanding what you were trying to explain. I guess I'm not your average n00b. I don't like being spoon fed just point me in the right direction is all I need and I'll feed myself.

At first I starting posting I can't do this, how you do that, then one member pointed me to the How-too's and to portage and wiki. From there I was busy reading and learning so I guess I'm not your average n00b.

Now back to the forums to learn some more.

[kspencer]

Rather, a "huh, I got it to work" message for a couple of slight differences.

Compaq proliant 1600, P3 500 (Akamai), 512M Ram. 3x 9.1G Ultra2 SCSI drives.

Now I consider myself a novice at best even though I've been prodding at Linux (and Gentoo) for a few years now - I keep running into things that are supposed to be basic knowledge that throw me. So if I state the obvious, please forgive up front.

I first tried to do this about two weeks ago. I appear to have made one glaring error - as near as I can tell, you cannot put / on sdb. (/boot on sda1, /var on sda2, /boot on sdb1, /home on sdb2, /usr on sdc1, swap on sdc2). Lots of tweaking and prodding in vain and I went off to solve other issues. Then I came back and made some basic changes. I'll note exceptions to the instructions as I progress.

1) The partition was /boot and / on sda, /var on sdb, and /home and swap on sdc. They're all (except for swap) reiserfs. The reason is the way apache wants to put the pages in /var, and this is going to be a blog box for a while. I was trying to spread the diskhead loads.

2) No hdparm - they're SCSI drives.

3) Fiddly little giggle - copied timezone New_York to Atlanta, and used that for my ln -s for localtime.

4) Since the display device isn't a framebuffer, I skipped the "gensplash" section - neither emerging splashutils and the subsequent splash_geninitramfs NOR putting a splash in my grub.conf.

5) I made one error in the installation - I forgot to modify the fstab. A quick boot with the min disk and chroot the appropriate systems, modify and write the table, and the subsequent boot was as clean as I could ask.

I'm still running things to see how much improvement comes about - conveniently, this box has had Gentoo installed two previous times for different tasks and I've got various benchmarks available. I will note that I also learned a new lesson during this installation which, though probably in the forums somewhere, I'll pass along just in case.

If you've done a 'one-line' command, it's frustrating to return to learn the process stalled somewhere due to something causing the downloaded file to fail the md5sum. Now I figure most folk know that the first thing is to rm the offending file. And perhaps fewer but still a majority know that "emerge --resume" starts you up again on the particular emerge that got interrupted. But it being a chain - worse, a chain of several emerge commands - means you can be stuck trying to decide just which emerge command got interrupted. I got a wild hair and looked, and lo and behold there IS a log of the emerge commands -- /var/log/emerge.log . Again, I figure the experienced already know of its presence, but I'll still pass it on as something learned.

Bob, thanks for an interesting install, one which looks to be real useful real soon now.

Kirk

[Cpoc]

if i were setting up a RAID server for a small LAN, i would modify the paradigm somewhat -- if you're doing this with older hardware (i'm guessing that you are based on your comments about recycling old gear), then i would build a hybrid system. this kind of setup would use RAID 1 on your data partitions, and RAID 0 on your system partitions. you can get away with a setup like this because, unlike windows which handles raid at the device level, linux can handle raid at the partition level.

there are some good examples of how to set up these various types of raid systems in the Docs forum. to adapt to is using this install method, i'd just to the complete installation of the file system using the raid guides, build from a stage 3 tarball, and then rebuild the system like you do in this guide. unfortunately, that type of install really is pretty far off topic, and really deserves its own thread.

The recycled system is a Samul 2 1 Gigapro system. It was givien to me because it has a broken pin in the VGA connecter. It's one of these all in one motherboards it's process or is 733 Mhz so it's not that slow.

I'm using two 10 gig harddrives for this setup. basicly I want to setup a small file server somethingthat can be on 24/7. Since the pin is broken in the motherboard it does not output the color red on the monitor. So I want this system working with no keyboard and no monitor. After its setup I'll connect via ssh. I just want the data safe because it will hold all the family pictures that my wife has scattered in 3 different PC. I just want all the pictures to be in one PC and the data to be safe. So speed is not really a concern safety of data is. This is why I want a sofware raid 1.

I try it that method I have seen some guides that show you how to transform a normal setup to a raid 1 setup.
It's ok even if I mess up as long as I learn something then it won't be a total lost.

[Bob P]

if you want to pursue this RAID business, let's move it to another thread. you can edit your last post to insert a hyperlink.

[Master One]

Progress update concerning KDE3.4.0_rc1 compilation after installing the system with this fabulous "Stage1 on a Stage3 Tarball" method:

Most of the packages compiled without any problem, even with the extreme optimizations using the stacked CFLAGS+CXXFLAGS+LDFLAGS, but now I am stuck with a very strange problem on some remaining packages, which simply do not want to compile, regardless which flags I set (I already tried with a minimal set of save flags as well, but no change).

I think I need some help, especially since I have no idea, if these problems could be related to this installation method somehow. Please have a look at this thread.

[torchZ06]

nightmorph,

thanks for the jolt of common sense! i tried to do the 1-on-3 3 times on 2 diff machines before i saw your post and all it took for it to work was to do the etc-update at the end. hell, i didnt even finish the update-- just let it do the automated part and skipped the 10 questions that require human intervention, rebooted and presto! it worked!

bob p,
great how-to btw...

[96140]

thanks for the jolt of common sense! i tried to do the 1-on-3 3 times on 2 diff machines before i saw your post and all it took for it to work was to do the etc-update at the end. hell, i didnt even finish the update-- just let it do the automated part and skipped the 10 questions that require human intervention, rebooted and presto! it worked!

You're welcome! Good to know it works

[Bob P]

regarding etc-update -- i've held my tongue and not said this for a couple of days now, but does it really come as a surprise to anyone that you need to pay attention to the on-screen warnings that gentoo provides about updating your config files? after all, updating the config files when you are told to do so falls into the realm of genoo fundamentals -- it is a common sense decision that anyone who is remotely familiar with gentoo is expected to be able to deal with.

[kimchi_sg]

regarding etc-update

It's us gurus who bear the blame - not telling them all about alternatives to etc-update, like dispatch-conf, for instance. I have used dispatch-conf ever since I heard about it, and have never ever lost a configuration file since. Never.

Anyway, even if you did overwrite a file using dispatch-conf, it will have backed up the old one when you chose to use the new file, so you can still retrieve the old one.

[Master One]

I use dispatch-conf with rcs since the beginning, and would never go back to etc-update.

Concerning the mentioned KDE problem: It seems, that various KDE3.4.0_rc1 packages simply can not be compiled using gcc-3.4.3, I am still investigating this issue.

[Bob P]

my point wasn't to say that etc-update is bad, and it isn't related to the all to common problem of stepping on your config files when you update them -- it was to say that ignoring the on-screen updates provided by emerge, such as "10 files in /etc need updating" is very very bad. look at the problems that some of the gentoo n00bs have encountered in this thread because they ignored that message and didn't bother to update their config files.

[96140]

look at the problems that some of the gentoo n00bs have encountered in this thread because they ignored that message and didn't bother to update their config files.

It's not so much that the warnings are ignored as it is that they're easy to forget, unfortunately. Here we've been following step after step in a specific order, and we just keep moving right on from one step to the next, just following what's written on screen. Sure, there are a few places where we know we'll have to deviate, and take that into account.

But it is a little easier to lose track of necessary etec-updates after 24-36 hours of compiling and recompiling. I, for one, didn't intentionally ignore the etc-update warnings the first time I tried this. If I was vaguely aware of them, I probably figured, "Oh, I'll remember to go back in at the end and take care of that, before I reboot." And...I didn't. It's easier than you'd think to get caught up solely in the printed instructions; by the time one gets to the end, things are moving at a fairly rapid pace, and there aren't that many (if any) points of system-specific deviation necessary, so we've lost the subconscious "check your configs carefully" prompting.

Hopefully no one--not even a newvbie--deliberately ignores etc-update...