I did try setting up a multi boot grub, with the two diferent conventions, but the only thing that helped was compiling the kernel to build in the driver then the old scheme worked. I must admit I did not test the other scheme.
That server (HP DL360 (was a compaq) ) now works fine handling 10,000 emails a day and checking for spam etc.
]]>Well, if I were to venture a guess, it's because your kernel doesn't have devfs built in at all. So the kernel has no idea what /dev/discs/... is supposed to point to.
yep, thats what im saying.
but because its possible to do such a thing, even during the install with the compile youre own kernel option, I think it would be worth adding an example to distinguish between udev and devfs style devices.
seeing as 0.7 comes udev ready, i didnt expect there to be any trouble with device naming conventions. It took me some hours to realise thats what the problem was.
i think its worth the effort to save anyone else the trouble in the future.
thanks again.
]]>devfs
kernel (hd0,7)/vmlinuz-2.6.6-1 root=/dev/discs/disc0/part10 devfs=nomount vga=791 ro
udev / sysfs
kernel (hd0,7)/vmlinuz-2.6.9-1 root=/dev/hda10 vga=791 ro
partition 10... wow
]]>The stock kernel has devfs built in, but if you enable udev devfs is set to nomount. The kernel can then figure out what /dev/discs/... is supposed to be.
]]>the problem is with the devfs / sysfs (or is it udev) naming scheme.
devfs
kernel (hd0,7)/vmlinuz-2.6.6-1 root=/dev/discs/disc0/part10 devfs=nomount vga=791 ro
udev / sysfs
kernel (hd0,7)/vmlinuz-2.6.9-1 root=/dev/hda10 vga=791 ro
before you point it out, these lines are from a different computer, hence the 2.6.6 kernel and devfs=nomount. However, its still the same thing, conflict between devfs / udev naming scheme
hope that made sense.
thanks
Which kernel are you guys using? 2.6.9 ide?
]]>Can anyone else confirm this problem for me?
]]>thanks
]]>The problem is that the udev naming scheme and the devfs naming scheme (at boot time) aren't mutually exclusive. I assume you installed with udev, the device scheme used is the devfs scheme.
This is a problem, but maybe the grub.conf in the installer should reflect the two different options, with the devfs options commented out, as udev is suggested to be the new default. You think?
Dusty
]]>I don't remember if the old style devices work with a devfs enabled boot.
]]>I had problems when booting into the system, the kernel saying it couldnt mount /dev/discs/disc0/part5 (my / partition)
ive forgotten the exact error, but it was at the VFS mount point.
I spent a number of hours trying to figure out what was wrong.
After a while i came across phrakture's(?) post about having grub problems and tried replacing the root=/dev/hda5 instead of the /dev/discs/... style.
this worked.
it would be good if the 0.7 grub config file had something mentioning the different naming schemes for udev vs devfs
admittedly it has this comment
# Old /dev DevFS Grub
# -----------------------------------------------
# /dev/fd0 /dev/floppy/0 (fd0)
# /dev/hda /dev/discs/disc0/disc (hd0)
# /dev/hdb2 /dev/discs/disc1/part2 (hd1,1)
# /dev/hda3 /dev/discs/disc0/part3 (hd0,2)
but it is not really clear what one should use.. especially since the /dev/hda section is labeled Old /dev!!?
for some reason, on _this_ computer (which i installed with 0.6 but have upgraded to use udev), the line root=/dev/discs/disc0/.. works!?
i just thought it bring it to someones attention before it goes 0.7-final
another thing, required kernel parameters.. are there any required for Arch to function? I havent seen anything in the wiki mentioning any requirements or even lack there of.
thanks
edited to `codify' the menu.1st comment
]]>