similar to: SuSE 9.0 PXE boot problem

Hello, I have downloaded and burned Suse 9.2 Live CD. The problem is, it won't boot. I get "searching for boot record on CDROM... not found" message and then system just boots from hard drive. Other bootable cdroms work, it's just suse that doesn't. I post this here because suse live cd uses isolinux (isolinux.cfg below). Is there a way to make the cd boot, maybe using

It seems like there are several messages in the archive and in various forums about this problem, but I do not see a clear course of action for how to solve it. I am relatively new to Linux, compounding my problem. I just built a new machine for the express purpose of running Xen so my girlfriend and I could experiment and learn about different Linux distros. I am running on an Intel DG35EC

Dave, I have been interested in some of the same questions that you have been asking. A while back I asked a person at VLSI ( http://www.vlsi.fi/ ) in Finland if they had a product that might work. The exchange of email is included below. In summary, the answer was probably no, but maybe in the future. The VS1005 chip he mentions does not seem to have appeared yet. I currently have a pair

I have problems getting the TIMEOUT value work the same way LILO/GRUB does it.. ie it should wait until the timeout and then use the default value. However, it goes straight for the default value without waiting a single second (and a TIMEOUT value of 500 should mean 50 seconds, as it counts in 1/10th of a second, right?) SYSLINUX (isolinux) 2.00 ----8<------8<---- SERIAL 0 38400 TIMEOUT

Hi, I've got another one... NFS error 101 with NFSROOT has been discussed a lot, and hpa gave an answer to it which appears 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 \

I used google but did not come up with anything current to solve my problem. I have not tried any other search engines yet. There is not a search for the CentOS list so I am creating a new post. I have tested the CentOS 5.2 and RHEL 5.3 CD's and they passed. I had to use linux mediacheck ide=nodma to get them to pass. The newest releases seem to most times fail with just linux mediacheck. I

Hi, I test pvgrub on xen-3.3.0. After starting pvgrub with "xm cr xmexample.pv-grub", I can see nothing but qemu window. With "xm li" , I can see this domain is running: Name ID Mem VCPUs State Time(s) Domain-0 0 1024 2 r-----

I have tried to use isolinux 2.05, and I am running into a problem where it will not boot. I have previously used version 1.66, and the older version works just fine. Changing nothing except dropping the new version in does not work. Below is all of the relevant info, I believe. This occurs on multiple machines with different BIOS. I am currently in process of doing a binary search to find the

Having fought my PXE config and eventually getting it to work (had to comment out the group { } statments ? I now come across another issue I cannot resolve and would appreciate some help. in my /tftpboot/pxelinux.cfg/default file I have cause to use the APPEND statement to pass options to the kernel being used. Unfortunately this line has now become longer than 255 characters and appears to be

Thank Zhigang Wang for your response. I have test pvgrub with this config file: #pv-config kernel = "/usr/lib/xen/boot/pv-grub-x86_32.gz" extra = "(hd0,5)/boot/grub/menu.lst" memory = 512 name = "ExampleDomain" disk = [ ''file:/var/lib/xen/images/opensuse11-1/disk0,xvda,w'' ] vif = [ "bridge=eth0" ] root = "/dev/sda5 ro" start

Using wine-0.9.29 with paradox 3.5, I receive the following errors: c:\pdox35>paradox Warning: unprotecting memory to allow real-mode calls. NULL pointer accesses will no longer be caught. err:dosmem:DOSMEM_FreeBlock MCB invalid Cannot load PARADOXR.EXE err:dosmem:DOSMEM_FreeBlock MCB invalid Running paradoxr.exe, I get: c:\pdox35>paradoxr Warning: unprotecting memory to allow

Hi there Gene! Thanks you about your quick response!! As for your request, here is my whole Syslinux.cfg file: default /syslinux/vesamenu.c32 prompt 0 timeout 00 menu hshift 15 menu width 49 menu title Boot menu menu background /syslinux/splash.png menu color title * #FFFFFFFF * menu color border * #00000000 #00000000 none menu color sel * #ffffffff #76a1d0ff * menu color hotsel 1;7;37;40

Apologies if this ends up a dup, but there seems to have been a problem with my original subscription. ------------------------------ Hello, I am currently using Fedora on most of my servers. It does pretty well. I do have occasional problems which seem to me to stem from poor QA. For example, /usr/bin/enable <queue> coming back with "Enable: I don't know what to do!"

Hi, One of my pbx's seems to be having some new issues. crackling interference on the zap channels running through the channel bank, and I noticed that these happen when I hit an "irq miss" in zttool: Current Alarms: No alarms. Sync Source: Digium Wildcard T100P T1/PRI C IRQ Misses: 82695 Bipolar Viol: 0 Tx/Rx Levels: 0/8 3 Total/Conf/Act:

Actually your Syslinux config is less relevant than the kernel config file. Indeed Syslinux infers the method to use from the kernel image itself. I assume the .config is public. I will take a look as soon as I can Thomas Le 04/08/2015 14:09, intrigeri via Syslinux a ?crit : > Thomas Letan via Syslinux wrote (04 Aug 2015 09:27:38 GMT) : >> Are you using EFI Handover Protocol? >

I'm currently running version 2.0.7 of samba(CIFS9000). I have HPUX 11.x installed on the samba server. When I try to run this from inetd it doesn't work. I can run a startup script that runs the smbd as a daemon and it works fine. But if I try to run it from inetd it won't start. The previous version of Samba 1.9.18p10 that I had on this server worked fine. Is this a bug in

Several people already reported this at linux-kernel and elsewhere with no answers, I thought perhaps this would be a more adequate forum... [1.] One line summary of the problem: After I/O, journal is aborted and filesystems made read-only. [2.] Full description of the problem/report: One can't anymore write to the affected file systems. Upon investigation, ext3fs journal was aborted

Hi I had a working system, until recently - its asterisk 1.6.1 from debian - not the lastest as the last doesn't seem to work. but somebody who rang me said my voice mail announcement was all stuttery. so i dialed my voicemail box and its really stuttery... so I have done a reboot and its just as bad, now I am not sure what to check to try and get this working again ..... Alex

Oh, wise Centaurs, On the last install (Suse) I was running on this old notebook (Dell i600m) the audio worked fine. Specifically, Realplayer and onsite players (like you get at NPR and other sites) and youtube played just fine. But with this current install (CentOS 5.3, fully updated) all of those sources just mentioned play choppy. It's like an echo so severe that it's impossible to

Hello all, I'm booting a USB stick (DOS formatted, one 1GB partition) and I'd like to offer the choice of either continue booting from the USB stick, or booting from the installed hard disk (Linux ext3). I've asked this question here previously and Quinn replied saying I should use the 'localboot -1' option which would pass boot to the next device. And so I did. The BIOS