PXE boot problem

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
Post Reply
suslu
Ronin
Ronin
Posts: 3
Joined: 26 Jul 2012, 05:15
Location: ankara

Re: 64bit official Porteus repository bug reports

Post#1 by suslu » 26 Jul 2012, 13:51

i'm trying to establish a connection between my laptop and PC. to do this; i set up porteus 64 bit to my laptop's C directory and i tried to connect with PXE server. However, while starting at PC, i get some errors related to tftp. What should be done to solve tftp settings? pc cant see the pxelinux.cfg file. :wall:

bnuf
Ronin
Ronin
Posts: 1
Joined: 25 Jul 2012, 09:00
Location: turkey

PXE boot problem

Post#2 by bnuf » 27 Jul 2012, 06:48

Hi everyone I tried to run porteus in pxe booting mode many times.However, although I set it up on my laptop and I tried to connect my pc to it via network connection ,I got serious errors while starting on pc. actually, first i set it with usb but every time i shut down the laptop , all changes disappeared. Therefore i give up using usb stick and i set porteus on my C directory of laptop. At that time i have lots of boot file and i dont actually know which one pc tries to find to boot it.when i try to change dhcp settings in pxelinux.cfg file, pc refuses it and doesnt see the changes. here is the my code in start file . if you notice my problem, please help me immediately.

ps. I get errors: Pxe-E53,Pxe-E36,Pxe-E3B

#!/bin/bash
# This script will start a DHCP server and TFTP server in order to provide
# fully functional environment for PXE booting.
#

cd $(dirname $(readlink -f $0))
sleep 20
# find out our own IP address. If more interfaces are available, use the first one
IP=$(ifconfig $(ls -1 /sys/class/net | grep eth | head -n 1 | sed "s|@||g") | grep "inet addr" | cut -d : -f 2 | cut -d " " -f 1)

# if no IP is assigned to this computer, setup private address randomly
if [ "$IP" = "" ]; then
killall dhcpcd 2>/dev/null
IP="10."$(($RANDOM/130+1))"."$(($RANDOM/130+1))".1"
ifconfig $(ls -1 /sys/class/net | head -n 1 | sed "s|@||g") $IP netmask 255.0.0.0
fi

# calculate C class range
RANGE=$(echo $IP | cut -d "." -f 1-3)

# with copy2ram cheatocde /boot is not availiable, after mounting porteus media you can run this script manually
device=`awk 'c-->0;/Porteus data found in/{c=1}' /mnt/live/var/log/livedbg`
[ "$device" != "/memory/copy2ram" ] && ROOT=/ || ROOT=`cd ../../ ; pwd`

# make sure dnsmasq can be started
killall dnsmasq 2>/dev/null
mkdir -p /var/state/dnsmasq

# start the DHCP server and TFTP server
./dnsmasq --enable-tftp --tftp-root=/boot \
--dhcp-boot=/pxelinux.cfg/pxelinux.0,"$IP",$IP \
--dhcp-range=$RANGE.2,$RANGE.250,infinite --log-dhcp

User avatar
fanthom
Site Admin
Site Admin
Posts: 4547
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: PXE boot problem

Post#3 by fanthom » 27 Jul 2012, 10:29

i guess these 2 posts above comes from the same person using different accounts?

both were posted in wrong categories/treads so i have merged them up here.

questions:
1) do you run pxe services provided with Porteus or 3rd party ones (like Windows http/tftp servers) ? to make it more clear: do you run porteus on your laptop with 'pxe boot' option or you have just unpacked porteus to some directory on your C drive and pointed Windows services to it?
2) did you add necessary drivers to initrd as per FAQ answer 19?

i have posted a sample video of PXE booting done between 2 virtual sessions in Vbox:
http://youtu.be/a7UfhfCtFEo
this is how it supposed to look like so pls watch it carefully.
Please add [Solved] to your thread title if the solution was found.

suslu
Ronin
Ronin
Posts: 3
Joined: 26 Jul 2012, 05:15
Location: ankara

Re: PXE boot problem

Post#4 by suslu » 02 Aug 2012, 06:27

hi again. We're working together with bnuf for summer internship. we've already tried what you said before, we watched the video that you shared with us carefully but nothing changed. Now, i wanna ask something related to our error messages again. We set porteus up to laptop and trying to boot pc via network connection. When we run porteus in our laptop, we get this(1st one) message in syslog file. After starting at pc, we get this(2nd one) message on screen. what can we do?

laptop:
syslog:

Aug 2 08:21:00 (none) kernel: [ 0.754753] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
Aug 2 08:21:00 (none) kernel: [ 2.526798] sd 6:0:0:0: [sdb] No Caching mode page present
Aug 2 08:21:00 (none) kernel: [ 2.526800] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Aug 2 08:21:00 (none) kernel: [ 2.529422] sd 6:0:0:0: [sdb] No Caching mode page present
Aug 2 08:21:00 (none) kernel: [ 2.529425] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Aug 2 08:21:00 (none) kernel: [ 2.532048] sd 6:0:0:0: [sdb] No Caching mode page present
Aug 2 08:21:00 (none) kernel: [ 2.532050] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Aug 2 08:21:00 (none) kernel: [ 3.356194] FAT-fs (sdb1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Aug 2 08:21:00 (none) kernel: [ 5.236643] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
Aug 2 08:21:00 (none) kernel: [ 5.236732] [Firmware Bug]: _BCQ is used instead of _BQC
Aug 2 08:21:00 (none) kernel: [ 6.327077] tpm_tis 00:04: A TPM error (7) occurred attempting to read a pcr value
Aug 2 08:21:00 (none) console-kit-daemon[1665]: WARNING: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Aug 2 08:21:01 (none) NetworkManager[1724]: <warn> bluez error getting default adapter: The name org.bluez was not provided by any .service files
Aug 2 08:21:02 (none) NetworkManager[1724]: <warn> bluez error getting default adapter: No such adapter
Aug 2 08:21:07 (none) dnsmasq[2109]: no servers found in /etc/resolv.conf, will retry
Aug 2 08:21:11 (none) org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
Aug 2 08:30:08 (none) org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
Aug 2 08:32:38 (none) org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
Aug 2 08:35:08 (none) org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
Aug 2 08:53:23 (none) org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
Aug 2 08:53:50 (none) dnsmasq-tftp[2427]: error 0 TFTP Aborted received from 172.x.x.x
Aug 2 08:53:50 (none) dnsmasq-tftp[2427]: failed sending //boot/pxelinux.0 to 172.x.x.x
Aug 2 08:53:50 (none) dnsmasq-tftp[2427]: file //boot/pxelinux.cfg/44454c4c-4200-1033-804d-c2c04f4c334a not found
Aug 2 08:53:50 (none) dnsmasq-tftp[2427]: file //boot/pxelinux.cfg/01-00-1e-4f-ca-1d-7f not found
Aug 2 08:53:50 (none) dnsmasq-tftp[2427]: file //boot/pxelinux.cfg/AC11FA9B not found
Aug 2 08:53:50 (none) dnsmasq-tftp[2427]: file //boot/pxelinux.cfg/AC11FA9 not found
Aug 2 08:53:50 (none) dnsmasq-tftp[2427]: file //boot/pxelinux.cfg/AC11FA not found
Aug 2 08:53:50 (none) dnsmasq-tftp[2427]: file //boot/pxelinux.cfg/AC11F not found
Aug 2 08:53:50 (none) dnsmasq-tftp[2427]: file //boot/pxelinux.cfg/AC11 not found
Aug 2 08:53:50 (none) dnsmasq-tftp[2427]: file //boot/pxelinux.cfg/AC1 not found
Aug 2 08:53:50 (none) dnsmasq-tftp[2427]: file //boot/pxelinux.cfg/AC not found
Aug 2 08:53:50 (none) dnsmasq-tftp[2427]: file //boot/pxelinux.cfg/A not found
Aug 2 08:53:50 (none) dnsmasq-tftp[2427]: file //boot/ip=172.x.x.x:172.x.x.x:172.x.x.x:255.x.x.x not found


pc:
starting optimized linux rc inspired by <http://www.linux-live.org/>
searching for porteus-v1.2-i486.sgn file
udhcpc: ioctl 0x8933 failed: no such device
httpfs: couldn't connect socket.

porteus data not found.

User avatar
fanthom
Site Admin
Site Admin
Posts: 4547
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: PXE boot problem

Post#5 by fanthom » 02 Aug 2012, 07:01

@suslu
more than likely this is the reason:
udhcpc: ioctl 0x8933 failed: no such device
and my question once again:
2) did you add necessary drivers to initrd as per FAQ answer 19?
fortunately, some time ago i have prepared bigger initrd.xz (32bit only) containing all drivers for 'porteus web-kiosk' project.
pls grab it form here:
http://www.mediafire.com/file/wdu2ms4vsrfcvrf/initrd.xz
replace original /boot/initrd.xz from 32bit porteus-1.2 and add following cheatcode to both: /boot/porteus.cfg and /boot/pxelinux.cfg/default

Code: Select all

ramdisk_size=3666
this is necessary as new initrd is slightly bigger.

let me know if that helped.
Please add [Solved] to your thread title if the solution was found.

suslu
Ronin
Ronin
Posts: 3
Joined: 26 Jul 2012, 05:15
Location: ankara

Re: PXE boot problem

Post#6 by suslu » 02 Aug 2012, 08:48

@fanthom thank you very much, it works! however, i need to work with 64 bit version of porteus for running specific program that requires 64 bit os. Can you please explain me what should i add, change in intrd.xz file of the 64 bit version of porteus.

User avatar
fanthom
Site Admin
Site Admin
Posts: 4547
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: PXE boot problem

Post#7 by fanthom » 05 Aug 2012, 12:51

Can you please explain me what should i add, change in intrd.xz file of the 64 bit version of porteus.
sorry but no.
i hate to repeat myself and i have posted where to find instructions two times already.
Please add [Solved] to your thread title if the solution was found.

anadolu
Ronin
Ronin
Posts: 2
Joined: 04 Sep 2012, 16:29
Location: turkey

Boot Error!

Post#8 by anadolu » 05 Sep 2012, 09:05

Hi Fanthom!Yes i booting on edition on the same pc my error messages just boot error :s on the screen just boot error display .This is porteus system info

Output from psinfo
----------------------
script by jayflood
.

====== USER INFO =====
User is: root
.
===== MACHINE INFO =====
Platform: x86_64
Kernel: 3.4.4-porteus
Processor: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz
Base Board Information
Manufacturer: Hewlett-Packard
Product Name: 30A3
MemTotal: 2056440 kB
MemFree: 1193296 kB
Bootparam: root=/dev/ram0 rootfstype=ext4 rw initrd=/boot/initrd.xz autoexec=pxe-boot~& toroot BOOT_IMAGE=/boot/vmlinuz
.
===== LIVE DEBUG INFO =====
# Recognized devices:
/dev/sda1: LABEL="OSIM_VOL" UUID="D6369321369301A3" TYPE="ntfs"
/dev/sda2: UUID="9CB48FE8B48FC2EE" TYPE="ntfs"
/dev/sdb1: LABEL="duygu" UUID="6247-6E4C" TYPE="vfat"

# Porteus boot device:
sdb1

# Porteus data found in:
/mnt/sdb1/porteus

# Changes are stored in:
none

# Non standard /rootcopy dir:
none

# Loaded modules:
base/000-kernel.xzm
base/001-core.xzm
base/002-xorg.xzm
base/003-lxde.xzm
base/004-kde.xzm
base/005-devel.xzm
base/006-firefox.xzm
base/module.xzm
.
===== SOUND INFO =====
Sound card: 0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xf4700000 irq 45
Sound driver: Advanced Linux Sound Architecture Driver Version 1.0.25.
.
===== PARTITION INFO =====
Mounted:
/dev/sda1 fuseblk 60G 28G 33G 46% /mnt/sda1
/dev/sda2 fuseblk 34G 165M 33G 1% /mnt/sda2
/dev/sdb1 vfat 7.5G 905M 6.7G 12% /mnt/sdb1
.
===== OPTICAl DRIVE =====
sr0
.
===== USB INFO =====
Removables: USB
Removable status: sd0:0:0:0:[sda]Protect
sd2:0:0:0:[sdb]Protect
.
lsusb: Bus 001 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) 64MB QDI U2 DISK
Bus 003 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
.
===== SCREEN INFO =====
Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192
.
===== ACTIVATED MODULES =====
000-kernel.xzm
001-core.xzm
002-xorg.xzm
003-lxde.xzm
004-kde.xzm
005-devel.xzm
006-firefox.xzm
module.xzm
.
===== NETWORK INFO =====
eth0 Link encap:Ethernet HWaddr 00:17:08:42:6f:8c
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:16

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:744 (744.0 B) TX bytes:744 (744.0 B)
.
# Generated by dhcpcd
# /etc/resolv.conf.head can replace this line
# /etc/resolv.conf.tail can replace this line
.
===== PCI INFO =====
lspci: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
Subsystem: Hewlett-Packard Company Compaq nw8440 [103c:30a3]
Kernel modules: intel-agp
00:01.0 PCI bridge [0604]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express PCI Express Root Port [8086:27a1] (rev 03)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 01)
Subsystem: Hewlett-Packard Company Compaq nw8440 [103c:30a3]
Kernel driver in use: snd_hda_intel
Kernel modules: snd-hda-intel
00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 1 [8086:27d0] (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.1 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 2 [8086:27d2] (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.3 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 4 [8086:27d6] (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 [8086:27c8] (rev 01)
Subsystem: Hewlett-Packard Company Compaq nw8440 [103c:30a3]
Kernel driver in use: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 [8086:27c9] (rev 01)
Subsystem: Hewlett-Packard Company Compaq nw8440 [103c:30a3]
Kernel driver in use: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 [8086:27ca] (rev 01)
Subsystem: Hewlett-Packard Company Compaq nw8440 [103c:30a3]
Kernel driver in use: uhci_hcd
00:1d.3 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 [8086:27cb] (rev 01)
Subsystem: Hewlett-Packard Company Compaq nw8440 [103c:30a3]
Kernel driver in use: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller [8086:27cc] (rev 01)
Subsystem: Hewlett-Packard Company Compaq nw8440 [103c:30a3]
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev e1)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge [8086:27b9] (rev 01)
Subsystem: Hewlett-Packard Company Compaq nw8440 [103c:30a3]
Kernel modules: leds-ss4200, intel-rng
00:1f.2 IDE interface [0101]: Intel Corporation 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode] [8086:27c4] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:30a3]
Kernel driver in use: ata_piix
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI M56P [Radeon Mobility X1600] [1002:71c5]
Subsystem: Hewlett-Packard Company Compaq NW8440 [103c:30a3]
Kernel driver in use: radeon
Kernel modules: radeon
02:06.0 CardBus bridge [0607]: Texas Instruments PCIxx12 Cardbus Controller [104c:8039]
Subsystem: Hewlett-Packard Company Compaq nw8440 [103c:30a3]
Kernel driver in use: yenta_cardbus
02:06.1 FireWire (IEEE 1394) [0c00]: Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller [104c:803a]
Subsystem: Hewlett-Packard Company Compaq nw8440 [103c:30a3]
Kernel driver in use: firewire_ohci
Kernel modules: firewire-ohci
02:06.2 Mass storage controller [0180]: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD) [104c:803b]
Subsystem: Hewlett-Packard Company Compaq nw8440 [103c:30a3]
Kernel driver in use: tifm_7xx1
02:06.3 SD Host controller [0805]: Texas Instruments PCIxx12 SDA Standard Compliant SD Host Controller [104c:803c]
Subsystem: Hewlett-Packard Company Compaq nw8440 [103c:30a3]
Kernel driver in use: sdhci-pci
02:06.4 Communication controller [0780]: Texas Instruments PCIxx12 GemCore based SmartCard controller [104c:803d]
Subsystem: Hewlett-Packard Company nc8430 [103c:30a3]
08:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5753M Gigabit Ethernet PCI Express [14e4:16fd] (rev 21)
Subsystem: Hewlett-Packard Company Compaq nw8440 [103c:30a3]
Kernel driver in use: tg3
Kernel modules: tg3
10:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection [8086:4222] (rev 02)
Subsystem: Hewlett-Packard Company PRO/Wireless 3945ABG [Golan] Network Connection [103c:135c]
Kernel driver in use: iwl3945
Kernel modules: iwl3945
.
.
===== LOGS INFO =====
dmesg | tail
.
[ 8.884953] Console: switching to colour frame buffer device 210x65
[ 8.909847] fb0: radeondrmfb frame buffer device
[ 8.909850] drm: registered panic notifier
[ 8.909863] [drm] Initialized radeon 2.16.0 20080528 for 0000:01:00.0 on minor 0
[ 9.864369] tg3 0000:08:00.0: irq 47 for MSI/MSI-X
[ 12.192754] NET: Registered protocol family 10
[ 12.192996] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 12.488501] input: PS/2 Generic Mouse as /devices/platform/i8042/serio4/serio5/input/input8
[ 20.698214] ata1.00: configured for UDMA/100
[ 20.698221] ata1: EH complete
.
.
cat /var/log/messages | tail
.
Sep 5 11:07:13 porteus logger: ACPI group thermal_zone / action LNXTHERM:00 is not defined
Sep 5 11:18:01 porteus logger: ACPI group thermal_zone / action LNXTHERM:00 is not defined
Sep 5 11:18:02 porteus logger: ACPI group thermal_zone / action LNXTHERM:00 is not defined
Sep 5 11:26:41 porteus logger: ACPI group thermal_zone / action LNXTHERM:00 is not defined
Sep 5 11:26:42 porteus logger: ACPI group thermal_zone / action LNXTHERM:00 is not defined
Sep 5 11:32:03 porteus logger: ACPI group thermal_zone / action LNXTHERM:00 is not defined
Sep 5 11:32:04 porteus logger: ACPI group thermal_zone / action LNXTHERM:00 is not defined
Sep 5 11:37:26 porteus logger: ACPI group thermal_zone / action LNXTHERM:00 is not defined
Sep 5 11:37:27 porteus logger: ACPI group thermal_zone / action LNXTHERM:00 is not defined
Sep 5 11:50:24 porteus logger: ACPI group thermal_zone / action LNXTHERM:00 is not defined
..

User avatar
Hamza
Warlord
Warlord
Posts: 1846
Joined: 28 Dec 2010, 07:41
Distribution: Porteus
Location: France

Re: PXE boot problem

Post#9 by Hamza » 05 Sep 2012, 13:47

Please use CODE Tag

Code: Select all

[code]My logs
[/code]

Or post your logs on pastebin
NjVFQzY2Rg==

User avatar
fanthom
Site Admin
Site Admin
Posts: 4547
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: PXE boot problem

Post#10 by fanthom » 06 Sep 2012, 14:15

@anadolu
your setup looks pretty normal so 32bit edition should work out of the box.
did you try to repeat the installation?
how did you install it: through porteus installer, win_start_here.bat, lin_start_here.sh or by using external bootloader like for example Grub?
do you boot it from Cd, usb, over network?

finally: please post your bootloader config.
Please add [Solved] to your thread title if the solution was found.

anadolu
Ronin
Ronin
Posts: 2
Joined: 04 Sep 2012, 16:29
Location: turkey

Re: PXE boot problem

Post#11 by anadolu » 10 Sep 2012, 18:59

@fanthom
thanks fanthom i solved the problem. My USB is corrupted. i formatted USB and every things okay. İm so sory for the late reply.
But i still have a problem. i try to network connection with pc and laptop. i have a switch. i coudn't connection pc and laptop than i add to kernel module and i open pc with porteus and i choose PXE boot than open the laptop with the porteus no problem. but i try to open laptop with porteus and network connection, i open the pc, pc opened but porteus has a problem :S i cant find the solution and i dont understand why:S help me please :wall:
The problems Image

User avatar
fanthom
Site Admin
Site Admin
Posts: 4547
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: PXE boot problem

Post#12 by fanthom » 12 Sep 2012, 10:33

@anadolu

i'm sorry but i didn't understand much from your post.
i guess that missing network driver is the problem so please boot porteus normally (from usb/CD) on the PC/laptop which does not boot through PXE and then run 'lspci -k' command which let's you identify network driver used for your card. here is my example:

Code: Select all

44:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
	Subsystem: Hewlett-Packard Company Device 1413
	Kernel driver in use: r8169
	Kernel modules: r8169
then please update initrd with this driver as per FAQ instructions.

btw: PXE seems to get more popular (or maybe users base just grows?) so for next release i'll provide all drivers inside initrd by default.
Please add [Solved] to your thread title if the solution was found.

Post Reply