Hello.

I recently installed 9.1 and rand swaret --update and swaret --upgrade
(including the kernel)

I ran lilo afterwards and was able to boot... but tons of module errors
appeared. I looked in the syslog file and none of the errors were there.
Is there any way I can get the log to be more complete so I can show the
errors I am getting? Thanks,
Sam

On 2004-04-24, Samuel Winchenbach <swinchen@eece.maine.edu> wrote:
> Hello.
>
> I recently installed 9.1 and rand swaret --update and swaret --upgrade
> (including the kernel)
>
> I ran lilo afterwards and was able to boot... but tons of module errors
> appeared. I looked in the syslog file and none of the errors were there.
> Is there any way I can get the log to be more complete so I can show the
> errors I am getting? Thanks,
> Sam
>
>

check the dmesg log.....

also

man dmesg for more info on bootup errors

ken

On Fri, 23 Apr 2004 23:40:10 -0400, Samuel Winchenbach wrote:

> Hello.
>
> I recently installed 9.1 and rand swaret --update and swaret --upgrade
> (including the kernel)
>
> I ran lilo afterwards and was able to boot... but tons of module errors
> appeared. I looked in the syslog file and none of the errors were there.
> Is there any way I can get the log to be more complete so I can show the
> errors I am getting? Thanks,
> Sam

Do you see the errors if you run dmesg?


Scott McMillan

Ok.. I didn't see the error when I ran dmesg, so I rebooted and looked at
the error again. It turns out it was the same module that what failing over
and over again (.../drivers/net/irda/via-ircc.o.gz - any idea what this is?)
so I added that to the blacklist. That took care of that problem... while
I was at it I also commented out the section of rc.M that loads the PCMCIA
stuff.. because that was giving a error as well. Another problem fixed.
Now I have the following problems remaing:

===== On Boot =====
Apr 23 22:11:03 WinchenbachS-1 kernel: kmod: failed to exec
/sbin/modprobe -s -k scsi_hostadapter, errno = 2
Apr 23 22:11:03 WinchenbachS-1 last message repeated 2 times

Apr 23 22:11:03 WinchenbachS-1 kernel: FAT: bogus logical sector size 0
Apr 23 22:11:03 WinchenbachS-1 last message repeated 2 times

Apr 23 22:11:03 WinchenbachS-1 kernel: usb.c: USB device 2 (vend/prod
0x45e/0x47) is not claimed by any active driver.

Apr 23 22:46:20 WinchenbachS-1 modprobe: modprobe: Can't locate module
char-major-10-134
Apr 23 23:23:48 WinchenbachS-1 dialog: /dev/gpmctl: No such file or
directory
Apr 23 23:23:53 WinchenbachS-1 modprobe: modprobe: Can't locate module
char-major-10-134
Apr 23 23:25:59 WinchenbachS-1 dialog: /dev/gpmctl: No such file or
directory
Apr 23 23:26:03 WinchenbachS-1 modprobe: modprobe: Can't locate module
char-major-10-134
Apr 23 23:26:50 WinchenbachS-1 dialog: /dev/gpmctl: No such file or
directory
Apr 23 23:26:54 WinchenbachS-1 modprobe: modprobe: Can't locate module
char-major-10-134
Apr 23 23:27:33 WinchenbachS-1 dialog: /dev/gpmctl: No such file or
directory
Apr 23 23:27:38 WinchenbachS-1 modprobe: modprobe: Can't locate module
char-major-10-134
Apr 23 23:28:02 WinchenbachS-1 dialog: /dev/gpmctl: No such file or
directory
Apr 23 23:28:08 WinchenbachS-1 modprobe: modprobe: Can't locate module
char-major-10-134
Apr 23 23:35:39 WinchenbachS-1 dialog: /dev/gpmctl: No such file or
directory
Apr 23 23:36:12 WinchenbachS-1 dhcpcd[313]: terminating on signal 15

===== Problems With X =====
1) If I run x as root, the sound works fine. If I run x as a normal user I
get an error saying I don't have permission.

2) If I run x as a regular user and do a "glxinfo" X quits and gives this in
the log:

Fatal server error:
Caught signal 11. Server aborting


When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
This can be found in the log file "/var/log/XFree86.0.log".
Please report problems to xfree86@xfree86.org.

(II) RADEON(0): Wrote: rd=8, fd=77, pd=2


3) I get the following errors in X log:

_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/WinchenbachS-1:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
from list!
*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.


(WW) `fonts.dir' not found (or not valid) in
"/usr/X11R6/lib/X11/fonts/local/".
Entry deleted from font path.
(Run 'mkfontdir' on "/usr/X11R6/lib/X11/fonts/local/").

(WW) Open APM failed (/dev/apm_bios) (No such device)

(WW) RADEON(0): Bad V_BIOS checksum

Lots of messages like this (I dont think they are bad... just probing to see
what resolutions are supported):
(WW) (1600x1200,MAG XJ810) mode clock 202.5MHz exceeds DDC maximum 200MHz


Thanks for the help!

Sam

"Scott McMillan" <smcm@usa.net> wrote in message
newsan.2004.04.24.14.12.50.329295@usa.net...
> On Fri, 23 Apr 2004 23:40:10 -0400, Samuel Winchenbach wrote:
>
> > Hello.
> >
> > I recently installed 9.1 and rand swaret --update and swaret --upgrade
> > (including the kernel)
> >
> > I ran lilo afterwards and was able to boot... but tons of module errors
> > appeared. I looked in the syslog file and none of the errors were
there.
> > Is there any way I can get the log to be more complete so I can show the
> > errors I am getting? Thanks,
> > Sam
>
> Do you see the errors if you run dmesg?
>
>
> Scott McMillan

On Sat, 24 Apr 2004 12:56:54 -0400,
Samuel Ace Winchenbach <swinchen@eece.maine.edu> wrote:
>
>===== On Boot =====
> Apr 23 22:46:20 WinchenbachS-1 modprobe: modprobe: Can't locate module
> char-major-10-134

You can decipher these char-major messages through
<file:///usr/src/linux/Docuentation/devices.txt>.
In this case, it seems this message related to BIOS Advanced Power
Management. If this isn't something you use, the easiest way to get rid
of this message is to have the following in your /etc/modules.conf:

alias char-major-10-134 off

> Apr 23 23:23:48 WinchenbachS-1 dialog: /dev/gpmctl: No such file or
> directory

This is related to gpm. Do you have gpm running? Is /etc/rc.d/rc.gpm
enabled?

>===== Problems With X =====
> 1) If I run x as root, the sound works fine. If I run x as a normal user I
> get an error saying I don't have permission.

Has this always been the case, or only since you've upgraded? If it's
the latter, make sure you have the appropriate ALSA modules loaded,
including snd-pcm-oss. If it's the former, the a.o.l.s FAQ mentions
adding users to the sys group for them to have sound. You may want to
try this out.


--
Mark Hill <usenet@mark.ukfsn.org> (devnull address not read)
GPG KeyID: 4A3B58AC

On 25 Apr 2004 00:04:41 GMT,
Mark Hill <devnull@mark.ukfsn.org> wrote:
>
> You can decipher these char-major messages through
><file:///usr/src/linux/Docuentation/devices.txt>.

It would help if I spelt the location correctly.

<file:///usr/src/linux/Documentation/devices.txt>.


--
Mark Hill <usenet@mark.ukfsn.org> (devnull address not read)
GPG KeyID: 4A3B58AC