Ok, I guess we can just close this bug then. Please reopen if you are
able to reproduce the problems another time.
** Changed in: dmraid (Ubuntu)
Status: Needs Info => Rejected
--
dmraid set won't activate
https://bugs.launchpad.net/bugs/110427
You received this bug notification because y
I can't help you with this bug anymore. The computer was not mine and
had to be returned to its owner. The owner will just have to live
without it for now.
It was using nvraid, but you already know that. I don't have the
computer with me to look up mobo model number or anything. I did try
comp
Can you give some more information on your hardware, motherboard, raid
controller etc?
** Changed in: dmraid (Ubuntu)
Assignee: (unassigned) => Tormod Volden
Status: Unconfirmed => Needs Info
--
dmraid set won't activate
https://bugs.launchpad.net/bugs/110427
You received this bug no
Sorry Chad, I forgot there are other animals than -i386 out there :) See
http://ubuntuforums.org/showthread.php?t=279628 for how to build a
subset of modules.
--
dmraid set won't activate
https://bugs.launchpad.net/bugs/110427
You received this bug notification because you are a member of Ubuntu
haha, sorry, tormod, but i failed to mention that I'm using x86_64. I
bet you gave me x86 modules. You should have asked though :)
--
dmraid set won't activate
https://bugs.launchpad.net/bugs/110427
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug con
Something is wrong. I deleted all the modules in that directly after
backing them up, and added your new ones. I rebooted into the current
kernel as stated. I reboot the computer. It takes a long time,
complains about the lack of raid45, io buffer errors, and end of device,
as usual.
I manually
I recompiled the drivers/md tree with the dmraid45 patch you referred to
in bug #97655. Try the normal kernel, but replace all modules in
/lib/modules/2.6.20-15-generic/kernel/drivers/md with these. (I am not
sure which modules have been changed, so replace them all.) Take a
backup of that director
certainly. just check out this bug.
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/97655
It has the two patches and a discussion about it.
--
dmraid set won't activate
https://bugs.launchpad.net/bugs/110427
You received this bug notification because you are a member of Ubunt
Can you give a link to that Mandriva patch you are using, or just attach
it here?
--
dmraid set won't activate
https://bugs.launchpad.net/bugs/110427
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubun
No, that is unmountable. It complains that it isn't a valid block
device. I would love to try using the standard kernel with only the
needed modules changed. However, that is a bit too advanced for me, so
you'll have to provide instructions. If i just copied them over, it
would complain about wro
Can you mount /dev/.static/dev/mapper/nvidia_edjdcidj1 ? I am more
worried about your custom kernels. How did you make them? Can you try to
rather use the standard kernel, but rebuild and replace the needed
modules?
--
dmraid set won't activate
https://bugs.launchpad.net/bugs/110427
You received
Is this related to udev? everything else seems to be working right.
--
dmraid set won't activate
https://bugs.launchpad.net/bugs/110427
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
12 matches
Mail list logo
