Hi Volkmar, are you sure your dhcp-server is answering? If it does, probably the driver for your network card is missing in the intitrd. In this case you must put the driver module into your initrd. For example on a machine where your linux is installed do this: login as root ...edit /etc/sysconfig/kernel ...set INITRD_MODULES="forcedeth jbd ext3" cd /boot mkinitrd -k vmlinuz -i initrd Regards Alfred At 18:55 12.05.2005, Volkmar Glauche wrote:

... apologies for cross-posting this, but perhaps someone on this list can give some advice or has solved the problem below.

---------- Forwarded message ---------- Date: Tue, 10 May 2005 20:08:43 +0200 (CEST) From: Volkmar Glauche To: suse-amd64@suse.com Subject: [suse-amd64] PXE install on Fujitsu Siemens Scaleo T A64XP35

Hi, I am trying to do a PXE install of SuSE Linux Professional on a Fujitsu Siemens Scaleo T A64XP35 box. However, it does seem to have problems initializing the network card after PXE. I have tried the following scenarios: 1) Boot from DVD with install=nfs://myserver/mydir. This works fine, the network card gets its IP over DHCP and starts the download. Yast detects the card as Asus CK804 (apparently using the forcedeth driver?).

2) Boot from the PXE PROM of the network card. This downloads the kernel (linux64 from the DVD) and initrd (initrd64 from DVD) and starts booting. The network card sends a DHCPDISCOVER 2 or 3 times, but does not answer the DHCPOFFER from the DHCP server. Thus it times out on mounting the installation source and I get into linuxrc. However, I did not have any luck to activate the network card manually, either. Any ideas?

-- Volkmar Glauche - Department of Neurology volkmar.glauche@uniklinik-freiburg.de Universitaetsklinikum Freiburg Phone 49(0)761-270-5331 Breisacher Str. 64 Fax 49(0)761-270-5310 79106 Freiburg

-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com

-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com

Hi Volkmar, Am Donnerstag, 12. Mai 2005 18:55 schrieb Volkmar Glauche:

Hi, I am trying to do a PXE install of SuSE Linux Professional on a Fujitsu Siemens Scaleo T A64XP35 box. However, it does seem to have problems initializing the network card after PXE. I have tried the following scenarios: 1) Boot from DVD with install=nfs://myserver/mydir. This works fine, the network card gets its IP over DHCP and starts the download. Yast detects the card as Asus CK804 (apparently using the forcedeth driver?). 2) Boot from the PXE PROM of the network card. This downloads the kernel (linux64 from the DVD) and initrd (initrd64 from DVD) and starts booting. The network card sends a DHCPDISCOVER 2 or 3 times, but does not answer the DHCPOFFER from the DHCP server. Thus it times out on mounting the installation source and I get into linuxrc. However, I did not have any luck to activate the network card manually, either. Any ideas?

I have similar issues with all distr. from 9.1 upwards on certain hardware. The problems turned out to be unfortunate irq layout, where usb (in my case) and nic are sharing the same irq. While netbooting works fine up to the point of hardware detection, the usb driver gets troubled (oopses) for unknown reasons, and stupidly deactivates the whole irq, which kicks the active nic setup into the void.. Here's a serial console log of this happening: usbcore: registered new driver hiddev usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.01:USB HID core driver USB Universal Host Controller Interface driver v2.2 ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10 PCI: setting IRQ 10 as level-triggered ACPI: PCI interrupt 0000:00:10.0[A] -> GSI 10 (level, low) -> IRQ 10 uhci_hcd 0000:00:10.0: UHCI Host Controller irq 10: nobody cared! [<c013500c>] __report_bad_irq+0x1c/0x70 [<c01350eb>] note_interrupt+0x5b/0x80 [<c0134cab>] __do_IRQ+0xdb/0xf0 [<c0105288>] do_IRQ+0x38/0x60 [<c0103cba>] common_interrupt+0x1a/0x20 [<c011e161>] __do_softirq+0x31/0xa0 [<c011e1f6>] do_softirq+0x26/0x30 [<c010528d>] do_IRQ+0x3d/0x60 [<c0103cba>] common_interrupt+0x1a/0x20 [<c0134e89>] setup_irq+0x89/0xd0 [<f8f0dd00>] usb_hcd_irq+0x0/0x60 [usbcore] [<c0134fd1>] request_irq+0x71/0x90 [<f8f1167a>] usb_hcd_pci_probe+0x1aa/0x450 [usbcore] [<c01dac62>] pci_device_probe_static+0x32/0x50 [<c01daca7>] __pci_device_probe+0x27/0x40 [<c01dacdb>] pci_device_probe+0x1b/0x40 [<c0234971>] driver_probe_device+0x21/0x60 [<c0234a9d>] driver_attach+0x4d/0x80 [<c0234e8d>] bus_add_driver+0x6d/0xa0 [<c0235388>] driver_register+0x28/0x30 [<c01daea4>] pci_register_driver+0x54/0x70 [<f881b087>] uhci_hcd_init+0x87/0xd7 [uhci_hcd] [<c012e974>] sys_init_module+0x104/0x180 [<c0102ca7>] syscall_call+0x7/0xb handlers: [<f8f0dd00>] (usb_hcd_irq+0x0/0x60 [usbcore]) Disabling IRQ #10 After this, install attempt from via-rhine fails: via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker ACPI: PCI interrupt 0000:00:12.0[A] -> GSI 10 (level, low) -> IRQ 10 eth0: VIA Rhine II at 0x1c000, 00:0f:ea:ac:e1:76, IRQ 10. eth0: MII PHY found at address 1, status 0x786d advertising 01e1 Link 45e1. eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 I've no idea, why it works from CD-ROM, but then, the nic isn't setup before usb, which means, that an active nic setup somewhat influences the initialization of usb hardware on the same irq.. At least that's my theory about this problem domain. Cheers, Pete