Re: [gentoo-user] Re: disappearing hdc
I hope it is not hardware failure... I'm checking dmesg on every reboot since failure of one of my server :) I've found that I changed configuration of my kernel - cdrom driver is loaded as module and must be loaded on boot (before hotplug/coldplug ?) for hdc to be created. Somehow parport_pc is loaded automaticly. What can I do to force hotplug/coldplug to load ide-cd and so to force udev to create hdc? I added ide-cd to /etc/modules.autoload.d/kernel-2.6. 2005/9/18, Bob Sanders [EMAIL PROTECTED]: On Sat, 17 Sep 2005 20:01:41 +0200 capsel [EMAIL PROTECTED] wrote: So the problem is : When RC_DEVICE_TARBALL=no there is no lp0 and sometimes hdc, it doesn't depend on cd/dvd disc inside my dvd, or on if my printer is set to on/off On a properly operating system, /dev/lp0 will be created if the printer is on at boot - parallel port or usb, or when the printer is turned on - usb. Parallel port will not always create a printer if it's turned on after the system. Not seeing the CDrom/DVD drive every boot indicates some faulty hardware - bad cable, bad connector, dieing southbridge. Given that the printer is also a southbridge device, I'd suggest having recent backups of your hard drive and be prepared for hardware replacement. I haven't ever touched any udev rules and my system (gentoo) worked for more than year (till about two days ago). It is not new or exotic hardware, and I think this is not fault of hardware at all. So AFAIK the error does not depend on RC_DEVICE_TARBALL, hardware, kernel (gentoo-sources, vanilla-sources)... It's sounding like hardware to me. It would benefit you to check dmesg on every boot to see what is discovered during boot up. If the hardware isn't discovered, then udev won't create a node for it. Bob - -- gentoo-user@gentoo.org mailing list -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: disappearing hdc
capsel schreef: I've found that I changed configuration of my kernel - cdrom driver is loaded as module and must be loaded on boot (before hotplug/coldplug ?) for hdc to be created. Somehow parport_pc is loaded automaticly. What can I do to force hotplug/coldplug to load ide-cd and so to force udev to create hdc? I added ide-cd to /etc/modules.autoload.d/kernel-2.6. Well, that should work, but the 'better' way is simply to recompile the kernel so that ide-cd is statically compiled (* or Y, rather than M), and then it would be automatically loaded by the kernel when the device is discovered (which would also tell you if you have a hardware issue, because the device wasn't discovered during the normal hardware scan the kernel makes at boot). What runlevel is hotplug set to run in (rc-update show)? If boot, then the problem with having the module in /etc/modules.autoload.d is that the service (hotplug) is running before the module load, whereas if hotplug is set to run at 'default', it runs *after* the modules in /etc/modules.autoload.d/kernel-2.6 are loaded, or at least that is my experience. But since you aren't likely to be hotplugging your CD device anyway (unless this is a laptop with an external drive), it just makes more sense to compile the driver (Device Drivers= ATA/ATAPI/MFM/RLL support= Include IDE/ATAPI CDROM support) statically (which I thought was the default kernel config setting anyway) and just let coldplug handle it. HTH, Holly -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: disappearing hdc
2005/9/18, Holly Bostick [EMAIL PROTECTED]: Well, that should work, but the 'better' way is simply to recompile the kernel so that ide-cd is statically compiled (* or Y, rather than M), and then it would be automatically loaded by the kernel when the device is discovered (which would also tell you if you have a hardware issue, because the device wasn't discovered during the normal hardware scan the kernel makes at boot). Cd is always detected at boot - when scanning ide's - no matter if I compile ide-cd as module or compile it in. It is not about hardware :) What runlevel is hotplug set to run in (rc-update show)? If boot, then the problem with having the module in /etc/modules.autoload.d is that the service (hotplug) is running before the module load, whereas if hotplug is set to run at 'default', it runs *after* the modules in /etc/modules.autoload.d/kernel-2.6 are loaded, or at least that is my experience. coldplug is in boot runlevel but is started after loading modules and hotplug is dead and buried and... does not do much. But since you aren't likely to be hotplugging your CD device anyway (unless this is a laptop with an external drive), it just makes more sense to compile the driver (Device Drivers= ATA/ATAPI/MFM/RLL support= Include IDE/ATAPI CDROM support) statically (which I thought was the default kernel config setting anyway) and just let coldplug handle it. HTH, Holly CD-rom is built into laptop... I wanted to load my system faster than with everything compiled into core. :) Loading files from hard disk after linux boot is faster than before (grub/lilo). Is there a way to set this to load magicaly at system boot? I thought that coldplug/holdplug should take care of this. Thanks for help :D -- gentoo-user@gentoo.org mailing list
[gentoo-user] Re: disappearing hdc
On 9/16/05, Dave Nebinger [EMAIL PROTECTED] wrote: I did something like that: -I set up RC_DEVICE_TARBALL=no -rebooted, all hdcX disappeard, and hdc appeard -I set up RC_DEVICE_TARBALL=yes -rebooted -there is no hdc* what else can I do? Go to the udev migration thing in the gentoo wiki. There is a command that you have to run to actually rebuild the tarball. Just flipping to no, rebooting, and flipping to yes does not force the tarball recreation. The command in the wiki will tell you how to build the tarball. Reboot with the flag as 'no' to get your devices right, then run the command, then you can flip back to 'yes'. -- gentoo-user@gentoo.org mailing list I've found that devices.tar.bz2 is created on every reboot, but I also tryed to make my own devices.tar.bz2 with my devices and put it to /lib/udev-state... So for example lp* stays (it's another one that disappears), all hdc? stays, but hdc still is not there. File devices.tar.bz2 is updated by system and it has not hdc. What else can I do? -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: disappearing hdc
So for example lp* stays (it's another one that disappears), all hdc? stays, but hdc still is not there. File devices.tar.bz2 is updated by system and it has not hdc. What else can I do? Not use the tarball option? I mean, seriously, are you really seeing it's saving you anything at boot? I couldn't tell any noticeable difference, so I've been running w/o tarball for months... -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: disappearing hdc
2005/9/17, Dave Nebinger [EMAIL PROTECTED]: So for example lp* stays (it's another one that disappears), all hdc? stays, but hdc still is not there. File devices.tar.bz2 is updated by system and it has not hdc. What else can I do? Not use the tarball option? I mean, seriously, are you really seeing it's saving you anything at boot? I couldn't tell any noticeable difference, so I've been running w/o tarball for months... -- gentoo-user@gentoo.org mailing list With RC_DEVICE_TARBALL=yes lp* and all hdc? except hdc stays, and I can see saving device nodes not at boot but when shutting down/reboot. With RC_DEVICE_TARBALL=no hdc is created, and lp*, hdc? does not exist. I'll try to emerge sync now... It is really strange. I haven't ever had such symptoms, even when I switched from 2.4/devfsd to 2.6/udev. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: disappearing hdc
capsel wrote: 2005/9/17, Dave Nebinger [EMAIL PROTECTED]: So for example lp* stays (it's another one that disappears), all hdc? stays, but hdc still is not there. File devices.tar.bz2 is updated by system and it has not hdc. What else can I do? Not use the tarball option? I mean, seriously, are you really seeing it's saving you anything at boot? I couldn't tell any noticeable difference, so I've been running w/o tarball for months... -- gentoo-user@gentoo.org mailing list With RC_DEVICE_TARBALL=yes lp* and all hdc? except hdc stays, and I can see saving device nodes not at boot but when shutting down/reboot. With RC_DEVICE_TARBALL=no hdc is created, and lp*, hdc? does not exist. I'll try to emerge sync now... It is really strange. I haven't ever had such symptoms, even when I switched from 2.4/devfsd to 2.6/udev. Hi, i put RC_DEVICE_TARBALL=no(permanently) a long time ago, had no problems. Now checked and currently it's set to yes but this is due to the fact i had do a complete reinstall a week ago (dying hard on it's way). IIRC when it is set to no udev creates all necessary nodes, you only have to put your own rules to support new/exotic hardware. Now will cp the tarball somewhere for backup and change to 'no'. HTH. Rumen -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: disappearing hdc
As I can see you did not read whole message :) So the problem is : When RC_DEVICE_TARBALL=no there is no lp0 and sometimes hdc, it doesn't depend on cd/dvd disc inside my dvd, or on if my printer is set to on/off When RC_DEVICE_TARBALL=yes lp0, hdc1..20 are in /dev but hdc is only on first reboot after recreating it by hand (mknod) or with MAKEDEV. I made my own devices.tar.bz2 but there was same result. I noticed it yesterday when I wanted to watch film on dvd one more time. Today my brother wanted to print something but cups showed that printer is not connected so I checked why - there was no lp0 in /dev. I haven't ever touched any udev rules and my system (gentoo) worked for more than year (till about two days ago). It is not new or exotic hardware, and I think this is not fault of hardware at all. So AFAIK the error does not depend on RC_DEVICE_TARBALL, hardware, kernel (gentoo-sources, vanilla-sources)... 2005/9/17, Rumen Yotov [EMAIL PROTECTED]: capsel wrote: 2005/9/17, Dave Nebinger [EMAIL PROTECTED]: So for example lp* stays (it's another one that disappears), all hdc? stays, but hdc still is not there. File devices.tar.bz2 is updated by system and it has not hdc. What else can I do? Not use the tarball option? I mean, seriously, are you really seeing it's saving you anything at boot? I couldn't tell any noticeable difference, so I've been running w/o tarball for months... -- gentoo-user@gentoo.org mailing list With RC_DEVICE_TARBALL=yes lp* and all hdc? except hdc stays, and I can see saving device nodes not at boot but when shutting down/reboot. With RC_DEVICE_TARBALL=no hdc is created, and lp*, hdc? does not exist. I'll try to emerge sync now... It is really strange. I haven't ever had such symptoms, even when I switched from 2.4/devfsd to 2.6/udev. Hi, i put RC_DEVICE_TARBALL=no(permanently) a long time ago, had no problems. Now checked and currently it's set to yes but this is due to the fact i had do a complete reinstall a week ago (dying hard on it's way). IIRC when it is set to no udev creates all necessary nodes, you only have to put your own rules to support new/exotic hardware. Now will cp the tarball somewhere for backup and change to 'no'. HTH. Rumen -- gentoo-user@gentoo.org mailing list -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: disappearing hdc
On Sat, 17 Sep 2005 20:01:41 +0200 capsel [EMAIL PROTECTED] wrote: So the problem is : When RC_DEVICE_TARBALL=no there is no lp0 and sometimes hdc, it doesn't depend on cd/dvd disc inside my dvd, or on if my printer is set to on/off On a properly operating system, /dev/lp0 will be created if the printer is on at boot - parallel port or usb, or when the printer is turned on - usb. Parallel port will not always create a printer if it's turned on after the system. Not seeing the CDrom/DVD drive every boot indicates some faulty hardware - bad cable, bad connector, dieing southbridge. Given that the printer is also a southbridge device, I'd suggest having recent backups of your hard drive and be prepared for hardware replacement. I haven't ever touched any udev rules and my system (gentoo) worked for more than year (till about two days ago). It is not new or exotic hardware, and I think this is not fault of hardware at all. So AFAIK the error does not depend on RC_DEVICE_TARBALL, hardware, kernel (gentoo-sources, vanilla-sources)... It's sounding like hardware to me. It would benefit you to check dmesg on every boot to see what is discovered during boot up. If the hardware isn't discovered, then udev won't create a node for it. Bob - -- gentoo-user@gentoo.org mailing list
[gentoo-user] Re: disappearing hdc
On 9/16/05, Dave Nebinger [EMAIL PROTECTED] wrote:
When I create /dev/hdc it stays for one reboot.
These values I've got in /etc/conf.d/rc:
RC_DEVICES=udev
RC_DEVICE_TARBALL=yes
hdc is a cdrom on my laptop. What can cause this?
Turn off the tarball option, or create /dev/hdc and recreate your tarball.
What's happening is upon startup the tarball is used to create the initial
/dev contents. I'm willing to bet the tarball does not have the /dev/hdc
link, therefore it is not being created.
I know that when I did the udev migration it had some steps to build the
tarball, but as I remember I too was missing the /dev/hd{c,d} links. By
setting tarball to no, udev manually recreates the /dev directory based
upon
the devices themselves so it will be there.
Dave
--
gentoo-user@gentoo.org mailing list
I did something like that:
-I set up RC_DEVICE_TARBALL=no
-rebooted, all hdcX disappeard, and hdc appeard
-I set up RC_DEVICE_TARBALL=yes
-rebooted
-there is no hdc*
what else can I do?
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: disappearing hdc
I did something like that: -I set up RC_DEVICE_TARBALL=no -rebooted, all hdcX disappeard, and hdc appeard -I set up RC_DEVICE_TARBALL=yes -rebooted -there is no hdc* what else can I do? Go to the udev migration thing in the gentoo wiki. There is a command that you have to run to actually rebuild the tarball. Just flipping to no, rebooting, and flipping to yes does not force the tarball recreation. The command in the wiki will tell you how to build the tarball. Reboot with the flag as 'no' to get your devices right, then run the command, then you can flip back to 'yes'. -- gentoo-user@gentoo.org mailing list
