Displaying 20 results from an estimated 1000 matches similar to: "Problems in CF Boot creation using SYSLINUX"
2002 Nov 05
0
[leaf-user] RE: CF Boot media creation
I'm home at last. I did a mixture of things. I downloaded DOS6.22 floppy
from putergeeks.com, extracted my old syslinux 1.75 (dos version) into the
same boot floppy and made my CF /dev/hda1 as suggested by Luis (Hail O
King - my saviour). Lo and behold it went thro' like a hot knife thro'
butter. syslinux did not complain at all. I did an xcopy /s of my D: (hard
disk) to my C:(CF) and
2002 Nov 05
0
CF Boot media creation
-----Original Message-----
From: S Mohan [mailto:smohan at vsnl.com]
Sent: 05 November 2002 16:13
To: Luis.F.Correia; leaf-user at lists.sourceforge.net
Subject: RE: [leaf-user] (no subject)
I know that is the proper way. Unfortunately, I'm stuck and am mad at myself
for that.
Error message:
ERROR 440D: Unable to lock drive for exclusive access - when I use syslinux
2.00 from freshmeat.
2002 Nov 05
1
[leaf-user] FW: CF Boot media creation
I downloaded DOS6.22 image from putergeek.com. Used fdisk from that floppy
and format from that floppy. Still no luck.
If I execute fdisk under leaf (monkeynoodle.org) as fdisk/dev/hdc, and give
p for print partition table, I get the following:
Disk /dev/hdc: 16 heads, 32 sectors, 123 cylinders.
Units = cylinders of 512 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hdc1
2002 Nov 05
1
[leaf-user] RE: CF Boot media creation
Hi,
I had the same problem last week. I got it work when I
used an old syslinux (the one from Daschtein Utils).
I think that the problem is with newest version of
syslinux, but could get confirmation from the syslinux
group.
Nick
"S Mohan" wrote:
>
> I'm home at last. I did a mixture of things. I
> downloaded DOS6.22 floppy
> from putergeeks.com, extracted my old
2005 May 26
3
Updated Shorewall build and publish scripts
Attached please find updated build and publish scripts. They set the
''ulink.target'' parameter appropriately when converting docbook->HTML. I
have always hacked my xhtml/params.xsl file to set this parameter; these
updated scripts make that abomination unnecessary.
Paul/Mike: It might be a good idea to add a CVS project for these scripts.
-Tom
--
Tom Eastep \ Nothing is
2014 Jul 16
0
Possible memdisk issue
> On 08Jul2014--09Jul2014, Ady, Peter Anvin, Gene Cumm, Bernd Blaauw, Shao
> Miller, Kenneth Davis, wrote:
> > [...]
>
> Thank you all for your responses. You helped me solve my problem. For
> anyone else that runs into similar trouble and finds this thread, here
> follow summaries of what I've learned.
>
> To recap, our PXE server holds Dell BIOS updates in
2014 Jul 09
0
Possible memdisk issue
On 07/09/2014 01:54 PM, Alexander Perlis wrote:
>
> Ah, this might explain things although I don't know what is meant by
> "intended". First, to clarify, newmkfloppyimg calls mkdosfs 3.0.12, and
> grabs H/S from the output and then computes C. For all the sizes I've
> tried, newmkfloppyimg always tells me H=64 S=32 and then C is the
> approximately the number
2007 Dec 09
1
Formating and Mounting Partitions giving problems
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
<small>Hi <br>
After the installation of </small><small>Windows and L</small><small>inux
on my desktop.I partitioned the disk space under Windows and kept the
partitions as
2014 Jul 15
4
Possible memdisk issue
On 08Jul2014--09Jul2014, Ady, Peter Anvin, Gene Cumm, Bernd Blaauw, Shao
Miller, Kenneth Davis, wrote:
> [...]
Thank you all for your responses. You helped me solve my problem. For
anyone else that runs into similar trouble and finds this thread, here
follow summaries of what I've learned.
To recap, our PXE server holds Dell BIOS updates in FreeDOS floppy
images booted via MEMDISK.
2007 Oct 10
1
DOS/Freedos: Can't use mkfloppyimg.sh or mkdiskimage for +8M images ( Solved)
Hi,
I did found the problem, a combination of 2 factor.
1- I taught that I did install the latest syslinux, but in fact it was
the 3.36 version.
2- Thank to kevin Connelly, he point me to a problem he got with
mkdosfs command. The default FAT16 do not work, but the FAT12 do. By
adding -F12 to the mkdosfs command fix the problem. The default F16 do
seem to work for <8M floppy image.
Thank you
2002 Nov 17
2
Proxy-ARP
I''m working with LEAF boxes as gateway machines. I''m trying to implement
Proxy-ARP to build a bandwidth manager for my network. I''ve gone as per
the lartc howto to implement a transparent bridge in an existing network
and plan to put in my tc script after this. I''m configuring the box as a
standalone one before plugging it into the network. I''m getting
2014 Jul 09
2
Possible memdisk issue
On 07/09/2014 04:00 PM, H. Peter Anvin wrote:
>
> So this would seem consistent that this is the FAT12/FAT16 boundary that
> breaks stuff. Perhaps FreeDOS has a problem with FAT16 on floppies?
If I understand things correctly, a bootable floppy has two key pieces
of executable code: the 512-byte boot sector, and the kernel loaded by
that boot sector.
The kernel can be large, and thus
2004 May 18
0
New 2.0.2b .lrp and new .lrp policy
I have just uploaded a new version of the 2.0.2b .lrp:
http://shorewall.net/pub/shorewall/shorewall-2.0.2b/shorwall-2.0.2b.lrp
ftp://shorewall.net/pub/shorewall/shorewall-2.0.2b/shorwall-2.0.2b.lrp
This version already includes the normal LEAF changes that are present
in the shorewall.lrp distributed with Bering and Bering-uClibc.
Thanks to K.-P. Kirchdörfer, future versions of the .lrp will
2004 May 14
0
2.0.2 .lrp problem
The 2.0.2 .lrp released yesterday contained the wrong version of
/usr/share/shorewall/functions.
I have updated the .lrp with the correct version of the functions file.
[root@lists shorewall-2.0.2]# ls -l shorwall-2.0.2.lrp
-rw-r--r-- 1 root ftp 78325 May 14 06:28 shorwall-2.0.2.lrp
[root@lists shorewall-2.0.2]# grep shorwall 2.0.2.md5sums
3ae771fcbfe217006e88e69a597c6455
2004 Jul 22
2
Ext3 filesystem aborting journal at random times (Maxtor 300GB disk)
Hi,
Sorry if this is an old and fixed issue but I can't really seem to find
a definitive explanation/fix to this in the mail lists. Ever since I
upgraded to FC2 my server randomly decides that it can no longer access
the disk and "aborts" the ext3 journal leaving it read-only as
expected. I've seen the same errors on other mail list, explained away
as disk or disk cable
2013 Oct 04
1
[Bug 70130] New: unable to compile fragment shader program
https://bugs.freedesktop.org/show_bug.cgi?id=70130
Priority: medium
Bug ID: 70130
Assignee: nouveau at lists.freedesktop.org
Summary: unable to compile fragment shader program
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: infyquest at gmail.com
Hardware: x86 (IA32)
2001 Mar 22
1
get root inode failed
Erm, sheez having alot of problems :(
I have just been reading all the archives on the mailing list for the past few hours and
decided to try make the journal with:
tune2fs -j -J10 /dev/hdc1
[root@tkw /]# tune2fs -j -J10 /dev/hdc1
tune2fs 1.20-WIP, 17-Jan-2001 for EXT2 FS 0.5b, 95/08/09
Creating journal inode: done
[root@tkw /]# cat /etc/fstab
/dev/hdc1 /usr/local ext3
2002 Jun 07
0
isolinux probles
Hi,
I'm trying to create a bootable CD, and so far I have had limited success.
On the first CD I created, isolinux worked, but I think I had a kernel
without the necessary initrd support compiled in, so the boot failed.
Now I can't even re-create that success. At the moment the CD's I'm burning
(3 so far) do not even show the display file. I used isolinux-debug.bin for
the
2004 Feb 14
0
Memdisk/floppy image question
Here is the script I put together now. I hope I haven't overlooked
anything.
You might need to modify the first section of variables to suit your setup.
Ofcourse you need to run this as root. May be some version of this
should be included with syslinux?
Basically given an existing floppy image, it creates a larger image and
copies its contents over and sets up the bootsector of the
2003 Jan 16
1
File System corruption
Hi,
Yesterday I nuked an old fat32 partition on my hard drive using fdisk. I
just destroyed the partition and then created a new linux partition. Then I
created an ext3 filesystem with the following command
mkfs.ext3 -j /dev/hdc1
Everything seemed fine so I went ahead and moved all my music (MP3s and
FLACS) onto that partition.
This morning when I turn on my computer I can't mount that