Skip to contentSkip to conversation

Problems with udev buildroot

Buildroot Heiko Helmle 2 participants 4 messages Aug 8, 2011 – Aug 9, 2011

lore
Share & tools
lore
#0 lore raw

-- snip --
[hel at verflixtsl6 xtest]$ grep DEVTMPFS build/linux-2.6.39.4/.config CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
-- snip --

I'm using i386 defconfig without any changes (yet) - this seems to enable DEVTMPFS by default.

But after a rebuild with the same .config it looks different now - I'll do a clean rebuild and check again.

Quoted 18 lines

----- Urspr?ngliche Nachricht -----
Von: Peter Korsgaard
Gesendet: 08.08.11 21:43 Uhr
An: Heiko Helmle
Betreff: Re: Problems with udev buildroot

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Heiko" == Heiko Helmle <[email protected]> writes:

?Heiko> Hello
?Heiko> Hit the send button too early :)

?Heiko> it seems like /dev/null is missing and the generated image isn't able to mount anything...

Do you have CONFIG_DEVTMPFS_MOUNT enabled in the kernel? If so, that should take care of /dev/null.

Signature · 1 line
Bye, Peter Korsgaard
#1 lore raw

aah sorry - the rookie found his mistake:

I'm using a cpio'd filesystem as initramfs - and that disables devtmpfs_mount - according to kernel doc, initramfs has to to mount devtmpfs manually to use it.

So I'm still not quite sure if it'd be better to edit the inittab to mount devtmpfs or just put the basic nodes statically into /dev...

Am 08.08.2011 um 22:07 schrieb Heiko Helmle:

Quoted 33 lines

-- snip --
[hel at verflixtsl6 xtest]$ grep DEVTMPFS build/linux-2.6.39.4/.config CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
-- snip --

I'm using i386 defconfig without any changes (yet) - this seems to enable DEVTMPFS by default.

But after a rebuild with the same .config it looks different now - I'll do a clean rebuild and check again.

Quoted 8 lines

----- Urspr?ngliche Nachricht -----
Von: Peter Korsgaard
Gesendet: 08.08.11 21:43 Uhr
An: Heiko Helmle
Betreff: Re: Problems with udev buildroot

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Heiko" == Heiko Helmle <[email protected]> writes:

Quoted 10 lines

Heiko> Hello
Heiko> Hit the send button too early :)

Heiko> it seems like /dev/null is missing and the generated image isn't able to mount anything...

Do you have CONFIG_DEVTMPFS_MOUNT enabled in the kernel? If so, that should take care of /dev/null.

Signature · 1 line
Bye, Peter Korsgaard

_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

#2 lore raw
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Heiko" == Heiko Helmle <[email protected]> writes:

Heiko> aah sorry - the rookie found his mistake:

Heiko> I'm using a cpio'd filesystem as initramfs - and that disables Heiko> devtmpfs_mount - according to kernel doc, initramfs has to to Heiko> mount devtmpfs manually to use it.

Heiko> So I'm still not quite sure if it'd be better to edit the Heiko> inittab to mount devtmpfs or just put the basic nodes statically Heiko> into /dev...

We have native initramfs support in BR, which contains a workaround for the kernel not mounting devtmpfs - Why are you not using that?

Signature · 1 line
Bye, Peter Korsgaard
#3 lore raw

Am 09.08.2011 um 08:31 schrieb Peter Korsgaard:

Quoted 4 lines

We have native initramfs support in BR, which contains a workaround for the kernel not mounting devtmpfs - Why are you not using that?

I guess you mean the one that gets embedded in the kernel image automatically? I wasn't aware that in that case the filesystem receives a workaround. I'll try that next - thank you!

Best Regards
Heiko