Bug#373587: Bug#369265: boot.log
El Miércoles, 14 de Junio de 2006 14:31, escribió: > Hi Enrique, > > What I did was to switch the network cable after the kernel was loaded > by PXE and TFTP. That's only an ugly workaround but no solution. You > can also use the fai-cd (even 64bit) for installing a V20z. > Maybe you can disable the second NIC in the BIOS, so the linux kernel > will see only one NIC. I have both ethernet devices connected to the switch where install server is conected. Yesterday, I tried to disable the second NIC in the BIOS, but I couldnt find where. I dont have a deb mirror so I had to chroot to nfsroot and dpkg -i fai-nfsroot package. Is this right? Thanks in advance -- Enrique de la Torre Gordaliza Departamento de Arquitectura de Computadores y Automática Desp. 220A, Facultad CC. Físicas, Univ. Complutense de Madrid Tlfn: 91 394 4389
Bug#369265: boot.log
Installation stops at RPC error and I dont have shell access. How can I read the /tmp/boot.log or dmesg from the client? Any boot parameter? This is an v20z :00:06.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8111 PCI (rev 07) :00:07.0 ISA bridge: Advanced Micro Devices [AMD] AMD-8111 LPC (rev 05) :00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-8111 IDE (rev 03) :00:07.3 Bridge: Advanced Micro Devices [AMD] AMD-8111 ACPI (rev 05) :00:0a.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) :00:0a.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC (rev 01) :00:0b.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) :00:0b.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC (rev 01) :00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration :00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map :00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller :00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control :00:19.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration :00:19.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map :00:19.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller :00:19.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control :01:00.0 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) :01:00.1 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) :01:05.0 VGA compatible controller: Trident Microsystems Blade 3D PCI/AGP (rev 3a) :02:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 03) :02:02.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 03) :02:04.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 08) but only the first ethernet is connected. -- Enrique de la Torre Gordaliza Departamento de Arquitectura de Computadores y Automática Desp. 220A, Facultad CC. Físicas, Univ. Complutense de Madrid Tlfn: 91 394 4389
Bug#369265: boot.log
> On Wed, 14 Jun 2006 12:14:40 +0200, Enrique de la Torre Gordaliza <[EMAIL > PROTECTED]> said: > Installation stops at RPC error and I dont have shell access. How can I read > the /tmp/boot.log or dmesg from the client? Any boot parameter? > This is an v20z Yes, I know those machines. I've tested the fai 2.10.2 (which was released some minutes ago) with three network devices, and I had no problems. But I also had problems with the v20z. IMO this is because the kernel semms to have another order of the network devices, than when doing PXE boot. So PXE boot boots from eth0 (for e.g. maybe the upper NIC), but then the kernel thinks the lower NIC is eth0. So the upper will become eth1 and no network connection is available any more. IMO there was another thread on this problem on the FAI mailing list. Currently I have no real solution for this. -- regards Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
