similar to: More on Problems with PXELinux and ramdisk not loading

Hi, I'm trying to install Fedora Core 3 on an AMD 64-based machine using PXE (via DHCP and TFTP). I've managed to get the machine to load the kernel over the network and start booting, but instead of loading the root fs from initrd.img (that I appended as a config via pxelinux.cfg), it loads the pre-existing rootfs on my harddisk. At the top of dmesg is the message: "so old

We have been using SAMBA for file/print servers and domain controllers in Windows networks for several years. At one site, we have intermittent problems in which the connection to the SAMBA server appears to die: i.e., no one can connect to the share, and the Windows clients (Terminal Servers and workstations) apparently keep re-trying to connect which ultimately locks up those clients.

Hi, I did not find any hints in the web where to configure/setup/manipulate the rx/tx ring buffer allocation within dom0 for xen-unstable, maybe someone here can nudge me towards the right knob. The problem: when booting a handful of domUs and connecting them (comprising a small experimental IP network with links and nodes etc.), some interfaces that have been given by the configuration files

Hi, I stumbled on a rather odd problem. A brand new HP Compaq dx2200 computer didn't want to boot up pxelinux+memdisk image. The computer just gave "Disk I/O error" and stopped there. Workaround was rather simple... Just attach regular floppy drive to the motherboard and everything started working fine. I tried with older 2.05 (pxelinux+memdisk) and newer 3.31. Both produced

If anyone is still interested in this old thread, I have a rh7.3 image running under hvm. It''s a hack, but here''s what I did: Install rh7.3 in a vmware machine with vmware server. Booted off a live cd, ( I used a gentoo installer CD, but any live cd should work) Created a lvm volume on my Xen dom0 >From the liveCD, I use dd to copy the disk image to the lvm image (dd

Hi there, I''m using the Suse Enterprise 10 RC2 along with Xen 3.0.2 on X86-64 and I''m experiencing a problem with the network. I boot into the Xen kernel and everything works just fine. I can browse the net etc. However after a while the network stops responding completely. I am not sure what causes this to happen or what triggers it. After a few hours, the network just stops

Hi, I am trying to use MEMDISK from the GRUB boot loader, and gets stuck on the memory detection. MEMDISK reports dos_mem = 0 low_mem = 0 high_mem = 0

Hello, I am wondering about the behaviour of strsplit. When the pattern matches the beginning of the search string, the mepty string is added to the result, but that's not the case when the pattern matches the end of the search string: strsplit(" hello dolly ") [1] "" "hello" "dolly" The man for strsplit explains the algorithm: " The algorithm

See earlier post - May 10th "Node Panic" Can anyone tell me what might be happening here? I have a 3 node cluster running under RH AS 4 (2.6.9-34.ELsmp) with ocfs2 v. 1.2.1. I've upgraded to 1.2.1 as suggested in the previous post, but one or more of my nodes continues to panic weekly: Aug 16 15:29:02 linux96 kernel: (6670,2):ocfs2_extend_file:787 ERROR: bug expression:

Dear list, I''m trying to get Xen working on a P3-600E with 320 MB RAM. (256+64) It has suse linux 9.1 installed on it, and I tried to get xen running with both the binary download from the xen pages and the suse xen packages mentioned on this list some days ago. Both ''install packages/kernels'' lead to the same error: (XEN) Not enough memory for DOM0 memory

Two more observations: (adding to my previous below email) 1) Centos 5.6 also showing the same ACPI errors as in CentOS 5.5 2)BIOS-E820 map has a difference in the first line: (0000000000010000 instead of 0000000000000000) ================================ - Centos-5.3 BIOS-E820 memory map is: BIOS-e820: 0000000000000000 - 000000000009e000 (usable) BIOS-e820: 000000000009e000 - 00000000000a0000

(FreeDOS developers, I apologize for the redundant parts of this message. But I want to bring the SYSLINUX folks into the discussion, and the SourceForge mailing list archives are broken.) Background: I have a little Sourceforge project (http://unattended.sourceforge.net/) for which I use SYSLINUX to provide CD-ROM and PXE boot support for my boot disk. And it works great with MS-DOS. However,

Hi, I have a Excel file with three spreadsheets: PlanA, PlanB and PlanC. I'm trying to read the three spreadsheets and then adding them together. But, when I try read the PlanA there is an error message: rm(list=ls()) setwd('C:/Test/Dados/Teste') require(RODBC) Arquivo = odbcConnectExcel('T070206_1347.xls') (Geral = sqlFetch(Arquivo, 'PlanA')) (Lactacao =

All, We are facing some issues bringing up a DomVT on Xen x86_64(changeset 9267). We created a disk image with dd 8 G in size. We then booted an associated Dom-VT with a CD-ROM and did net-install of the sles-9 OS. This completes successfully. Then, when the system is brought around for a reboot (having changed the boot option from cdrom to disk), the system hangs after the line

I was using my computer normally when suddenly my btrfs volume became read-only. This is on Chris'' for-linus branch (latest commit cb77fcd88) Here''s the relevant excerpt from dmesg [ 50.877500] r8169 0000:01:00.0: eth1: link up [ 50.880296] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 60.959215] eth1: no IPv6 routers present [ 1904.463247] atkbd serio0: Unknown key

I have a system with several reserved ranges low in the e820 map which cause problems when starting PV domains with PCI devices. The machine memory map looks like: (XEN) 0000000000000000 - 0000000000060000 (usable) (XEN) 0000000000060000 - 0000000000068000 (reserved) (XEN) 0000000000068000 - 000000000009ac00 (usable) (XEN) 000000000009ac00 - 00000000000a0000 (reserved) (XEN) 00000000000e0000

This adds a boolean boot parameter to xen to allow reserved memory regions to be added to the iommu mappings for dom0. The parameter is "iommu_include_reserved" and is off by default. A warning is also traced when incorrect RMRR to system memory map values are detected. This is being added to address some incorrect BIOS''s that do not report correctly the requied reserved memory

Hello everyone, I have a quick question but I am stuck with it and I do not know how to solve it. Imagine I need the distribution function of a Weibull(1,1) at t=3, then I will write pweibull(3,1,1). I want to keep the shape and scale parameters in a list (or a vector or whatever). Then I have parameters<-list(shape=1,scale=1) but when I write pweibull(3,parameters) I get the following

Hi there, while my memdisk setup works perfectly well an an Intel system it fails like this on a Via-C3 based Mini-ITX system (copied manualy, I hope I did not make a mistake): --cut-- Failed to Free base memory, sorry... MEMDISK 2.08 (Debian, 2003-12-22) Copyright 2001-2003 H. Peter Anvin e820: 0000000000000000 000000000009fc00 1 e820: 000000000009fc00 0000000000000400 1 e820: 00000000000f0000

I''m continuing to work on making a new XenCD as previously discussed here. In the course of that work, I''ve generated (actually, currently stuck on) the enclosed crash dump. Thought I''d forward it for interest. To head off questions, you''ll see references to a very large initrd (~114 Mb). The Xen dump may or not be related to this unusual usage.