Ok, I think I know what is going on with this one ... Ran into similar on my
Lex m'boards ...
I do not think I ever saw the seg fault, but I might have gotten it and just
pressed on without paying any attention ... So it may be something new, but
lets compare notes and make sure you are with me on the things I can help
you with ...
First item, on my Lex BIOS, I as able to specifically choose that I wanted
the secondary IDE channel to be the boot device ... Check your BIOS and see
if you have this as an option ...
On some boards, there is a jumper that controls this, on others it's a BIOS
setting, on yet others, it will look at both automatically and choose the
one that looks like it might be bootable IF you chose the "BOOT FROM OTHER =
Enabled" in the BIOS ... This means that if there is a "legacy" boot
partition on that 2.5 in hard drive, things might be getting confused ...
Second item, take another look at grub.conf and see if you got it setup
pretty much like this ...
grub.conf line to boot from secondary IDE
****************************************************************************
*********
title AstLinux (Lex Neo - IDE-2m is boot, IDE-1m is kd)
root (hd0,0)
kernel /boot/bzImage root=/dev/hdc1 astlinux=i586 astkd=/dev/hda1
ide=nodma
savedefault
****************************************************************************
*********
I suspect you got something very similar setup for yours ... If so, your
grub.conf should be ok ... The key line is the one starting "kernel" ... The
"title" is just that (notation only) ... Your seg fault MIGHT have
something to do with trying to use ULTRA DMA so go for stability over speed
and use the "ide=nodam" setting ... It will be fast enough ...
Next item, at the console as root (or in putty if you prefer) run the
command "fdisk -l" (that's a lower case "L") ... This command will get fdisk
to return to you what it sees out there that look like drives ... It should
show you your boot CF card and also your 2.5 in hard drive ... Confirm that
fdisk sees /dev/hda and /dev/hdc devices ...
****************************************************************************
You should see something like this for hdc ...
****************************************************************************
Disk /dev/hdc: 256 MB, 256901120 bytes
16 heads, 63 sectors/track, 497 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/hdc1 1 398 200560+ 83 Linux
****************************************************************************
And something like this for hda
****************************************************************************
Disk /dev/hda: 1021 MB, 1021312512 bytes
32 heads, 61 sectors/track, 1021 cylinders
Units = cylinders of 1952 * 512 = 999424 bytes
****************************************************************************
If there is a partition existing on the drive, fdisk will give you this bit
****************************************************************************
Device Boot Start End Blocks Id System
/dev/hda1 1 1021 996465+ 83 Linux
****************************************************************************
If fdisk did not see both devices properly, check your MASTER/SLAVE settings
... Most likely on the 2.5 in hard drive ... Some mother boards may have
trouble seeing it if you leave it "cable select" or if you have it
incorrectly setup to be a slave drive when there is no master in place ...
Maybe try forcing it to be the MASTER using jumpers ...
If fdisk DID see both drives properly, then go ahead and use fdisk to create
a new partition on the 2.5 in hard drive ... You might want to DELETE any
old partitions first ... I have found that GENKD sometimes works better if
the /dev/hda1 partion already exists than if you let it "auto-partition" ...
Once you have a /dev/hda1 patition out there, run the command "genkd
/dev/hda1" ... It will warn you that its about to overwrite an existing
partition ... Tell it to do it anyway ...
I bet that if you work your way through the diagnostics steps above, you
WILL get it working ...
Good luck with it ...
G.Hendershot
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Erick Perez
Sent: Monday, December 11, 2006 11:23 PM
To: Discussion of AstLinux - Asterisk on Compact Flash
Subject: [Astlinux-users] genkd /dev/hda segmentation fault
Hi.
I have a VIA EPIA-CN13000(c7) and I want to run genkd /dev/hda which is a
2.5 hard disk (40gig).
My system boots correctly from /dev/hdc (a CF card)
Here is the output of genkd /dev/hda (hda has no partitions)
genkd /dev/hda
Segmentation Fault
This script.....blabla
I will use /dev/hda1
Creating Partition
Partitioning failed. You are on your own.
Could not determine filesystem size
Creating Filesystem failed. you are on your own.
why does segfault?
BTW I had to modify grub.conf to make my "boot from cf" to point to
root(2,0) and hdc1 instead of root(0,0) and hda1
--
------------------------------------------------------------
Erick Perez
Panama Sistemas
Integradores de Telefonia IP y Soluciones Para Centros de Datos Panama,
Republica de Panama Cel Panama. +(507) 6694-4780
------------------------------------------------------------
_______________________________________________
Astlinux-users mailing list
[email protected]
http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
[EMAIL PROTECTED]
_______________________________________________
Astlinux-users mailing list
[email protected]
http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to [EMAIL
PROTECTED]
