View previous topic :: View next topic |
Author |
Message |
Craneology Tux's lil' helper
Joined: 15 May 2003 Posts: 87
|
Posted: Thu Oct 30, 2003 3:08 am Post subject: when I login as my user, errors galore show up... |
|
|
Me = newbie so please be gentle...
When I login as my user, I get a ton of errors around this basis:
modprobe: cant locate module * which is needed in /dev/*
basically it looks like everything which is loaded at the beginning during the runlevels. Any help?
Also, during the runlevels, I get a couple of errors regarding /dev/rtc anyone know how to fix this?
Also, I just installed gnome, so how do I get it running... ? _________________ Gentoo on a Powerbook 12" 1ghz with 756mb ram. YEE HAA |
|
Back to top |
|
|
meowsqueak Veteran
Joined: 26 Aug 2003 Posts: 1549 Location: New Zealand
|
Posted: Thu Oct 30, 2003 3:21 am Post subject: |
|
|
For that rtc error, make sure you have Real Time Clock support enabled in the kernel:
CONFIG_RTC=y |
|
Back to top |
|
|
Craneology Tux's lil' helper
Joined: 15 May 2003 Posts: 87
|
Posted: Thu Oct 30, 2003 3:44 am Post subject: thnx for that tip |
|
|
I guess I forgot to enable that in the installation. Thnx.
Ill go ahead and post all of my problems, since well I have many:
during the loadup before the runlevels I get these errors:
1)kmod: failed exec /sbin/modprobe -s -k nls_iso8859 -1, errno=2
same with scsi_hostadapter, errno=2
[drm:drm_init] *ERROR* cannot initialize the agpgart module
hdc: set_drive_speed_status:status=0x51 {drive ready seek complee error}
error=0x04
ide: assuiming 33mhz system bus speed for PIO modes; override with idebus=xx <-- this right??
AMD_IDE: Bios didnt set cable bits correctly. Enabling workaround.
ds: no socket drivers loaded!
then theres also my biggest problem, which is all the modprobe errors about modules when I login with my username. Also, when I login to gnome, with my username, it errors with a logout under 10 seconds. Also I cant gain su access with my username. Help? Thnx!! _________________ Gentoo on a Powerbook 12" 1ghz with 756mb ram. YEE HAA |
|
Back to top |
|
|
meowsqueak Veteran
Joined: 26 Aug 2003 Posts: 1549 Location: New Zealand
|
Posted: Thu Oct 30, 2003 3:55 am Post subject: |
|
|
Ignore that idebus warning - it's actually correct and has nothing to do with UDMA100 or anything like that. 33MHz is correct. |
|
Back to top |
|
|
Dinini Apprentice
Joined: 11 Jun 2003 Posts: 236
|
Posted: Thu Oct 30, 2003 12:38 pm Post subject: Re: thnx for that tip |
|
|
If all else fails and you are using a 2.4.x kernel, use the genkernel script to build and install your kernel. And don't forget to modules_update after booting into the new kernel.
Craneology wrote: | during the loadup before the runlevels I get these errors:
1)kmod: failed exec /sbin/modprobe -s -k nls_iso8859 -1, errno=2
same with scsi_hostadapter, errno=2 |
errno=2 is "No such file or directory"
1) did you build and install these modules? (make modules_install)
2) are you trying to load the modules from a device which needs a module to be accessed? if so, you need an initrd file referenced in your bootloader that contains the needed module.
Craneology wrote: | Also I cant gain su access with my username. Help? Thnx!! | Add your username to the wheel group. you cannot su to root unless you are a member of wheel. |
|
Back to top |
|
|
Moofed Apprentice
Joined: 22 Oct 2002 Posts: 158 Location: Bloomington, IN
|
Posted: Thu Oct 30, 2003 2:21 pm Post subject: |
|
|
I had the "modprobe: cant locate module * which is needed in /dev/*" errors one time too. If I remember correctly, emerging metalog (or your system logger of choice) fixed it. I guess I forgot that step during that install. |
|
Back to top |
|
|
joehni Apprentice
Joined: 27 Jul 2003 Posts: 175
|
Posted: Thu Oct 30, 2003 4:44 pm Post subject: |
|
|
Thanks! Had the same problem too (but only when logging in as normal user, root went fine). It turns out htat I emerged the logger, but forgot to add it to my startup scripts ... |
|
Back to top |
|
|
kenw n00b
Joined: 02 Dec 2003 Posts: 5
|
Posted: Tue Dec 02, 2003 1:40 pm Post subject: Thanks! but question... |
|
|
So, I had exactly the same problem, and it was solved in exactly the same way. Thanks for the great advice.
My question is: is this solution masking the problem? Or does it actually solve it? Could someone explain why I was getting modprobe errors during a login?
ken.
Gentoo Newbie. |
|
Back to top |
|
|
|