This is more a question for Darrick than follow up help for Erick I think
...

I am not 100% clear on the reference to (boot 2,0) in grub.conf ... Is this
correct ???  If so, then I am doing it wrong on my setup and am wondering
how it is that mine is working ... I reference (boot 0,0) but am indeed
booting off hdc1 and pointing kd at hda1 ... I seem to recall that I tried
(boot 2,0) and it did not work, but when I set it to (boot 0,0) everything
was happy ...

In my scenario, I use a 256mb CF card connected as /dev/hdc for boot and a
1gb DOM connected as /dev/hda for kd ... Not exactly what he is doing but
similar as far as configuration ... My take on it is he just has a bigger
IDE device for kd but the settings should probably be pretty much the same
...  I do not really understand the details of what this (boot 0,0) setting
in grub.conf is doing, I just know what seems to work for me ...

I agree that the last issue may be the use of command structure "genkd
/dev/hda1" instead of "genkd /dev/hda" ...  I suspect this is the item he
needs to try ... I am not sure that the (boot 0,0) or (boot 2,0) in
grub.conf is really a contributor to what he is seeing ... 

G.Hendershot 


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Darrick Hartman
Sent: Wednesday, December 13, 2006 10:33 PM
To: Discussion of AstLinux - Asterisk on Compact Flash
Subject: Re: [Astlinux-users] genkd /dev/hda segmentation fault

Erick Perez wrote:
> Sorry for the late reply but here are my findings.
> remember:
> hdc is my cf card
> hda is my ide disk (no partitions defined), its a western digital set 
> to master by jumper
>
> i attached a usb disk to see if genkd segfaulted, but doing genkd
> /dev/sda1 ran ok, however doing genkd /dev/hda showed the segfault.
>
> My boot order in BIOS is :
> ch1 master: kodak ata flash
> ch0 master: western digital hard disk
> usb_hdd: usb key
>
> I also manually created a partition on /dev/hda (hda1) and then ran 
> genkd, it also segfaulted.
>
> I'm clueless.....
>   
When you attempted to use 'genkd' on the hard drive AFTER manually creating
the partition, did you use 'genkd /dev/hda1' or 'genkd /dev/hda'?  Also, you
_may_ have to manually create the partition, reboot, then run genkd
(shouldn't have to, but some hardware can be funny with re-reading partition
tables).

genkd is a script.  If you look at it, it will grep the command line to see
if astkd is defined.  If it is, executing genkd with no options will
generate the key disk on that partition.  Note that genkd is designed to
work with a partition, not a disk.

If you are getting a segfault, it's because the script tried to do something
that's not allowed.  (like mounting a drive instead of a partition).  There
could be some additional error checking implemented, but it's usually not an
issue.

Darrick

--
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

_______________________________________________
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]

Reply via email to