Re: [gentoo-user] Another issue/questions updating udev from 164-r2 to 171-r5
Am Sonntag, 5. Februar 2012, 12:34:56 schrieb Tanstaafl: I just updated these, and am unsure how to deal with the issues... First issue: *** Found sources for kernel version: 3.0.6-gentoo Checking for suitable kernel configuration options... ERROR: setup CONFIG_BLK_DEV_BSG: is not set when it should be. WARN: setup Please check to make sure these options are set correctly. Failure to do so may cause unexpected problems. I can probably find this when make'ing the new kernel, but if someone knows exactly where to find it that would be appreciated. make menuconfig type / type in the search term, hit enter there you go. -- #163933
Re: [gentoo-user] Another issue/questions updating udev from 164-r2 to 171-r5
On Sun, Feb 5, 2012 at 11:34 AM, Tanstaafl tansta...@libertytrek.org wrote:
I just updated these, and am unsure how to deal with the issues...
First issue:
***
Found sources for kernel version:
3.0.6-gentoo
Checking for suitable kernel configuration options...
ERROR: setup
CONFIG_BLK_DEV_BSG: is not set when it should be.
WARN: setup
Please check to make sure these options are set correctly.
Failure to do so may cause unexpected problems.
I can probably find this when make'ing the new kernel, but if someone knows
exactly where to find it that would be appreciated.
For the next time you need to find a kernel option:
1. go to /usr/src/linux
2. make menuconfig
3. press / (this activates search)
4. enter the config option you are looking
5. press Enter
The menu configurator will tell you where is the option you are
looking for, in this cas (CONFIG_BLK_DEV_BSG):
Symbol: BLK_DEV_BSG [=n]
Type : boolean
Prompt: Block layer SG support v4
Defined at block/Kconfig:50
Depends on: BLOCK [=y]
Location:
- Enable the block layer (BLOCK [=y])
Selected by: BLK_DEV_BSGLIB [=n] BLOCK [=y] || SCSI_SAS_ATTRS
[=n] SCSI [=y]
As you can see, it's an option at the top of the kernel menu config.
***
Next issue/question (from post install log):
***
LOG: postinst
Updating persistent-net rules file
restarting udevd now.
persistent-net does assigning fixed names to network devices.
If you have problems with the persistent-net rules,
just delete the rules file
rm /etc/udev/rules.d/70-persistent-net.rules
and then reboot.
This may however number your devices in a different way than they are now.
So - how do I know if I need to worry about this?
Reboot, if your network works, everything is fine. If it's not, remove
the file /etc/udev/rules.d/70-persistent-net.rules (don't worry, it's
autogenerated), and reboot. If the problem persists, just check that
the names in that file correspond to the services in /etc/init.d. For
example, mine says
# PCI device 0x10ec:0x8136 (r8169)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==40:61:86:4e:a6:57, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==eth*, NAME=eth0
So (if I used OpenRC) I would need to check that /etc/init.d/net.eth0
it's a symlink to /etc/init.d/net.lo.
Next issue/question (from post install log):
WARN: postinst
If you build an initramfs including udev, then please
make sure that the /sbin/udevadm binary gets included,
and your scripts changed to use it,as it replaces the
old helper apps udevinfo, udevtrigger, ...
mount options for directory /dev are no longer
set in /etc/udev/udev.conf, but in /etc/fstab
as for other directories.
If you use /dev/md/*, /dev/loop/* or /dev/rd/*,
then please migrate over to using the device names
/dev/md*, /dev/loop* and /dev/ram*.
The devfs-compat rules have been removed.
For reference see Bug #269359.
Rules for /dev/hd* devices have been removed
Please migrate to libata.
How do I know if I need to worry about any of this stuff? I'm a bit lost
here...
Do you use an initramfs? Look at /boot/grub/grub.conf, is there a line
starting with initrd? If not, worry not.
Thanks for any advice/comments...
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
Re: [gentoo-user] Another issue/questions updating udev from 164-r2 to 171-r5
On 2012-02-05 12:45 PM, Volker Armin Hemmann volkerar...@googlemail.com wrote: Checking for suitable kernel configuration options... ERROR: setup CONFIG_BLK_DEV_BSG: is not set when it should be. WARN: setup Please check to make sure these options are set correctly. Failure to do so may cause unexpected problems. I can probably find this when make'ing the new kernel, but if someone knows exactly where to find it that would be appreciated. make menuconfig type / type in the search term, hit enter there you go. Cool, didn't know about this one... thanks...
Re: [gentoo-user] Another issue/questions updating udev from 164-r2 to 171-r5
On 2012-02-05 12:47 PM, Canek Peláez Valdés can...@gmail.com wrote:
On Sun, Feb 5, 2012 at 11:34 AM, Tanstaafltansta...@libertytrek.org wrote:
For the next time you need to find a kernel option:
1. go to /usr/src/linux
2. make menuconfig
3. press / (this activates search)
4. enter the config option you are looking
5. press Enter
snip
As you can see, it's an option at the top of the kernel menu config.
Yep, many thanks to you (and Volker) for pointing out how to search for
terms...
Reboot, if your network works, everything is fine. If it's not, remove
the file /etc/udev/rules.d/70-persistent-net.rules (don't worry, it's
autogenerated), and reboot. If the problem persists, just check that
the names in that file correspond to the services in /etc/init.d. For
example, mine says
# PCI device 0x10ec:0x8136 (r8169)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==40:61:86:4e:a6:57, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==eth*, NAME=eth0
So (if I used OpenRC) I would need to check that /etc/init.d/net.eth0
it's a symlink to /etc/init.d/net.lo.
Ok, this makes sense, thanks!
Next issue/question (from post install log):
WARN: postinst
If you build an initramfs including udev, then please
make sure that the /sbin/udevadm binary gets included,
and your scripts changed to use it,as it replaces the
old helper apps udevinfo, udevtrigger, ...
mount options for directory /dev are no longer
set in /etc/udev/udev.conf, but in /etc/fstab
as for other directories.
If you use /dev/md/*, /dev/loop/* or /dev/rd/*,
then please migrate over to using the device names
/dev/md*, /dev/loop* and /dev/ram*.
The devfs-compat rules have been removed.
For reference see Bug #269359.
Rules for /dev/hd* devices have been removed
Please migrate to libata.
How do I know if I need to worry about any of this stuff? I'm a bit lost
here...
Do you use an initramfs? Look at /boot/grub/grub.conf, is there a line
starting with initrd? If not, worry not.
Ok, I apparently don't, but... are you saying that all of the stuff that
follows the initramfs warning *all* pertains to using an initramfs?
If so, many thanks again, I'll have to make a note of this in my
maintenance manual...
:)
Re: [gentoo-user] Another issue/questions updating udev from 164-r2 to 171-r5
On Sun, Feb 5, 2012 at 12:21 PM, Tanstaafl tansta...@libertytrek.org wrote: [snip] Ok, I apparently don't, but... are you saying that all of the stuff that follows the initramfs warning *all* pertains to using an initramfs? No, you're right; this: mount options for directory /dev are no longer set in /etc/udev/udev.conf, but in /etc/fstab as for other directories. You only have to worry if you set mount options using udev; almost nobody did that. If you did (I think you'll remember) you only need to set the mount options in fstab (which is what the Gentoo Handbook describes). This line: If you use /dev/md/*, /dev/loop/* or /dev/rd/*, then please migrate over to using the device names /dev/md*, /dev/loop* and /dev/ram*. The devfs-compat rules have been removed. For reference see Bug #269359. Again, I think you'll remember if you used any of those devices, so you are probably fine. And lastly: Rules for /dev/hd* devices have been removed Please migrate to libata. If you don't have IDE devices, nothing to worry about. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
