Menu
▾
▴
#5 AMD K7-RAID support?
The project works great on my vanilla Intel-board PC
at work - but stalls at the second init on my AMD K7-
RAID board at home.
Anyone have any ideas - workarounds?
HDD-0 and -1 are two physical drives striped on the
RAID controller, maybe the current version cannot
detect this?
Regards,
Brent
Logged In: NO
Hmm Hmm ..
Hi !
I am trying to figure out what actually fails and gets your
computer to fail, what is the last thing you see before it
hangs ?
Is it while vlutil is running ?
it might be when vlutil tries to figure out your partition
makeup something goes wrong.
It should not do this however ... i have a promise raid
controller myself , on my develpment Amd K7 box
and it works fine , detects separate disks and so on . ?
vlutil uses the standard , dmesg aproach , ie looks in dmesg
output to find partitons and then tries to mount it whith
filesystems, i cant see , and have never seen it fail before
makes me worried .. Hmmm
Try to give me some more info about what happens.
I have to say this though , it is probably not much to do
about it with the version you have now, because if it hangs
early in bootup, we cant load an update (because we have to
go through the partition locate routine to be able to update)
And we cannot feed anything through kernel commandline to
make any bigger difference either ... it is pretty crippled
with the pivot_root way i use to boot the new version .. :(
However , try with textmode in boot menu , type init 1
and see if it can boot at all .
CrIxZ , the author of VL .
Logged In: NO
Hmm Hmm ..
Hi !
I am trying to figure out what actually fails and gets your
computer to fail, what is the last thing you see before it
hangs ?
Is it while vlutil is running ?
it might be when vlutil tries to figure out your partition
makeup something goes wrong.
It should not do this however ... i have a promise raid
controller myself , on my develpment Amd K7 box
and it works fine , detects separate disks and so on . ?
vlutil uses the standard , dmesg aproach , ie looks in dmesg
output to find partitons and then tries to mount it whith
filesystems, i cant see , and have never seen it fail before
makes me worried .. Hmmm
Try to give me some more info about what happens.
I have to say this though , it is probably not much to do
about it with the version you have now, because if it hangs
early in bootup, we cant load an update (because we have to
go through the partition locate routine to be able to update)
And we cannot feed anything through kernel commandline to
make any bigger difference either ... it is pretty crippled
with the pivot_root way i use to boot the new version .. :(
However , try with textmode in boot menu , type init 1
and see if it can boot at all .
CrIxZ , the author of VL .
Logged In: NO
Hmm Hmm ..
Hi !
I am trying to figure out what actually fails and gets your
computer to fail, what is the last thing you see before it
hangs ?
Is it while vlutil is running ?
it might be when vlutil tries to figure out your partition
makeup something goes wrong.
It should not do this however ... i have a promise raid
controller myself , on my develpment Amd K7 box
and it works fine , detects separate disks and so on . ?
vlutil uses the standard , dmesg aproach , ie looks in dmesg
output to find partitons and then tries to mount it whith
filesystems, i cant see , and have never seen it fail before
makes me worried .. Hmmm
Try to give me some more info about what happens.
I have to say this though , it is probably not much to do
about it with the version you have now, because if it hangs
early in bootup, we cant load an update (because we have to
go through the partition locate routine to be able to update)
And we cannot feed anything through kernel commandline to
make any bigger difference either ... it is pretty crippled
with the pivot_root way i use to boot the new version .. :(
However , try with textmode in boot menu , type init 1
and see if it can boot at all .
CrIxZ , the author of VL .