search for: nfsaddr

...ears right. It's ENETUNREACH, and I suspect my diskless box does not set its IP parameters right. PXElinux is set up as follows: label linvdr kernel kernel-linvdr append initrd=initrd-linvdr acpi=off root=/dev/nfs \ nfsroot=192.168.20.1:/opt/tftpboot/linvdr,rsize=8192,wsize=8192 \ nfsaddrs=192.168.20.20:192.168.20.1:192.168.20.99:255.255.255.0:linvdr (append line broken for readability only) I also tried ip= instead of nfsaddrs= as well as ip=dhcp, no luck. Why in the world would the kernel not configure its IP values? It's a SuSE 8.0 default kernel, and it has everything se...

Okay, now, before 3.10 is finalized... what bug reports am I still forgetting? -hpa

...reasons I did this was to figure out what extra options are appearing, and why. b4 extending: (the last bit is truncated) Jun 4 06:31:05 truck kernel: Kernel command line: BOOT_IMAGE=vmlinuz-2.6.12-rc5-mm2-soekris-v1 console=ttyS0,115200n81 root=/dev/nfs nfsroot=192.168.42.1:/nfshost/truck nfsaddrs=192.168.42.100:192.168.42.1:192.168.42.1:255.255.255.0:soekris:eth0 panic=5 initrd=initrd-2.6.12-rc5-mm2-soekris-v1.img kgdbwai Jun 4 07:33:58 truck kernel: Kernel command line: console=ttyS0,115200n81 root=/dev/nfs nfsroot=192.168.42.1:/nfshost/truck nfsaddrs=192.168.42.100:192.168.42.1:192...

folks, Im finding that using a config like this: SERIAL 0 19200 #IPAPPEND 2 PROMPT 1 TIMEOUT 100 IMPLICIT 0 APPEND console=ttyS0,19200n81 root=/dev/nfs nfsaddrs=10.10.10.100:10.10.10.2:10.10.10.2:255.255.255.0:soekris:eth0 nfsroot=10.10.10.2:/nfshost/truck panic=15 LABEL deb268 KERNEL vmlinuz-2.6.8-1-386 initrd=initrd.img-2.6.8-1-386 panic=10 LABEL deb268-ram KERNEL vmlinuz-2.6.8-1-386 APPEND console=ttyS0,19200n81 initrd=initrd.img-2.6.8-1-386 root=...

...is stanza: ie with a single 4 at end of APPEND line. LABEL 2.6.11-r10c2-soekris-v1 MENU LABEL ^j. runlevel 4 2.6.11-r10c2-soekris-v1 # 4 MENU DEFAULT KERNEL vmlinuz-2.6.11-r10c2-soekris-v1 APPEND console=ttyS0,19200n81 root=/dev/nfs nfsroot=192.168.42.1:/nfshost/foo nfsaddrs=192.168.42.100:192.168.42.1:192.168.42.1:255.255.255.0:soekris:eth0 panic=5 initrd=initrd-2.6.11-r10c2-soekris-v1.img 4 This usually works for grub on my laptop, but doesnt in pxelinux 308-pre7. I havent gone back to earlier versions, I wanted to check my understanding 1st. Is a single number...

...configure Hope this helps. Steve Oliphant -----Original Message----- From: Harald Milz [mailto:milz at seneca.muc.de] Sent: Tuesday, December 30, 2003 4:05 AM To: syslinux at zytor.com Subject: Re: [syslinux] NFS error 101, again Enrico Weigelt <weigelt at metux.de> wrote: > Isn't nfsaddrs deprecated (use ip= instead) ? I tried both, and nfsaddrs is still documented and properly set up in the source code. >> I also tried ip= instead of nfsaddrs= as well as ip=dhcp, no luck. > perhaps ip=::::::dhcp ? I'll give it a try - although it's documented that ip=dhcp is...

SYSLINUX 3.11-pre5 is hereby a bug fix release candidate. If I don't receive any problem reports, I will release it as-is on Tuesday, August 30. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Hello everyone, I am using pxelinux to boot kernel from network, which goes ok. But when root must be mounted from NFS, I get the following code: Looking up port 100003/2 on 192.168.1.1 RPC: sendmsg returned error 22 portmap: RPC call returned error 22 ROOT-NFS: unable to get nfsd port number from server, using default looking up port of RPC 100005/1 on 192.168.1.1 RPC: sendmsg returned error

...ns at initialization time. I have also merged my tree with v2.6.17-rc5, although it was a completely orthogonal merge set. The following issues are still outstanding, as far as I know; I will try to get to them in a timely manner: a. nfsroot with server defaulting to the server in the ip= or nfsaddrs= option. b. nfsaddrs= (unlike ip=) shouldn't configure networking unless NFS is specified as the root filesystem. c. s390/s390x merge. (Again, if someone could get me some hand holding in setting up a standard Linux on Hercules, that would be really useful.) -hpa

...rectory wrong. Did you try to mount >this directory by another client? I have not tried yet to mount directory by another client. I have no experience with nfs, but I will try it. > How do you tell the kernel the root FS? I have: In /tftpboot/pxelinux.cfg/default default linux root=/dev/nfs nfsaddrs=192.168.1.1:192.168.1.1:192.168.1.1:255.255.255.0:netserver:eth0 nfsroot=192.168.1.1:/netboot/base where netboot/base is where root for client system begins. >If the portmap calls fail the server doesn't want to talk to the >client, perhaps it wants the client to be in the DNS, or else...

Greetings all, Is there currently any mechanism in pxelinux the would send a mac address of the pxe booted interface through to the linux kernel much like ipappend can send the ip address? Kickstarting a system with multiple interfaces can be troublesome. ksdevice is helpful but only in some circumstances such as forcing eth0, but that doesn't always work since probe order changes depending

...r: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Wed, 11 Dec 2019 17:38:21 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 11 Dec 2019 17:48:47 +0000 [klibc] ipconfig: Ignore NTP server address and any additional fields ipconfig should accept any ip=/nfsaddrs= parameter that the kernel accepts. The kernel now supports a 10th field for an NTP server address, but only copies it into procfs. We must accept but ignore it. The kernel also ignores additional fields, and might define meanings to them in future. We must accept and ignore them. References:...

...APPEND root=/dev/ram0 initrd=initrd.gz console=ttyS1,115200 devfs=nomount LABEL linux KERNEL bzImage APPEND root=/dev/hda2 reboot=bios console=ttyS1,115200 LABEL nfs KERNEL bzImage APPEND console=ttyS1,115200 root=/dev/nfs nfsroot=192.168.0.18:/home/mike/nfs/ nfsaddrs=192.168.0.50:192.168.0.18::255.255.255.0:epc:eth0:none LABEL dos KERNEL rom-dos.bss # Add the following line to append for TS-3300 or TS-5300 Rev C or older # hdb=none hdc=none hdd=none hde=none hdf=none hdg=none hdh=none hdi=none hdj=none hdk=none hdl=none # for TS-9500 with Compact...

I have released SYSLINUX 3.08-pre5. Sparse files should now work correctly in extlinux. Symlink support still needs to be added, though. -hpa

...y are not needed - fstype no longer checks whether an ext4 module is installed, which did not work correctly with compressed modules - losetup uses the kernel's structure definitions, rather than its own which were wrong for some architectures - ipconfig ignores extra fields in the ip and nfsaddrs kernel parameters, rather than treating them as an error - Various warning fixes Other changes: - Removed cris port - losetup always uses the modern loop ioctl API - dash changes from upstream are documented A git shortlog of changes since version 2.0.7 follows. Ben. Antonio Ospite (2):...

...ND console=ttyS0,19200n81 root=/dev/hda1 IMPLICIT 0 #DEFAULT sk1 #DEFAULT menu.c32 DEFAULT sk1 PROMPT 0 MENU TITLE Simple Boot Menu LABEL sk1 KERNEL vmlinuz-2.6.10-sk1 APPEND console=ttyS0,19200n81 root=/dev/nfs nfsroot=192.168.42.1:/nfshost/foo nfsaddrs=192.168.42.100:192.168.42.1:192.168.42.1:255.255.255.0:soekris:eth0 panic=5 initrd=initrd-2.6.10-sk1.img 1. as given above, it works fine. 2. if the DEFAULT is switched to menu.c32, then a. I get a complaint about an illegal command in the file - if remove the commented line(s...

...SBM MENU LABEL ^n. mboot KERNEL com32/modules/mboot.c32 APPEND loader.bin LABEL H 2.6.12-rc4-mm2-soekris-v1 MENU LABEL ^h. 2.6.12-rc4-mm2-soekris-v1 KERNEL vmlinuz.pirt APPEND console=ttyS0,19200n81 root=/dev/nfs nfsroot=192.168.42.1:/nfshost/pirt-16 nfsaddrs=192.168.42.100:192.168.42.1:192.168.42.1:255.255.255.0:soekris:eth0 panic=5 I chose 1, Loading memdisk.... Could not find ramdisk image: pirt.img boot: 2 . Usage: chain.c32 (hd|fd)# [partition] boot: 3 . Usage: chain.c32 (hd|fd)# [partition] boot: 4 Loading memtest86.img.....Ready. this one ap...

Hi, everybody! My pxelinux.0/default file is: LABEL linux KERNEL vmlinuz-2.6.16 APPEND initrd=initrd-2.6.16.img root=192.168.4.110:/clients/192.168.4.100/root When mounting I get: switchroot: mount failed: 22 Kernel panic - not syncing: Attempted tp kill init! Before it I get some messages about: Can't find /dev/console. /clients/192.168.4.100/root/dev was empty. I've copied my

...e. @@ -79,55 +81,46 @@ ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf> - This parameter tells the kernel how to configure IP addresses of devices - and also how to set up the IP routing table. It was originally called `nfsaddrs', - but now the boot-time IP configuration works independently of NFS, so it - was renamed to `ip' and the old name remained as an alias for compatibility - reasons. - - If this parameter is missing from the kernel command line, all fields are - assumed to be empty, and the defaults m...

...(", rootserver=%u.%u.%u.%u", NIPQUAD(root_server_addr)); - printk(", rootpath=%s", root_server_path); - printk("\n"); -#endif /* !SILENT */ - - return 0; -} - -module_init(ip_auto_config); - - -/* - * Decode any IP configuration options in the "ip=" or "nfsaddrs=" kernel - * command line parameter. It consists of option fields separated by colons in - * the following order: - * - * <client-ip>:<server-ip>:<gw-ip>:<netmask>:<host name>:<device>:<PROTO> - * - * Any of the fields can be empty which means to...