Re: [gentoo-user] Problem with Xsetup

[Holly Bostick]

Rajat Gujral schreef:
> Sorry forgot to attach the log :((
>
>
> Hi holly, uwe Thanx for ur replies ... I was actually trying to
> install my sound driver when emerge automatically downloaded the
> newer version of kernel i.e 2.6.12-r10 telling me it has a better
> support for sound cards.. After the newer version was downloaded in
> /usr/src/ , i did "make menuconfig" to configure the kernel and save
> the .config file. Then "make && make modules_install" to compile the
> kernel. After that i compiled the kernel and copied it to the /boot
> directory. But forgot to update the grub.conf file ... When rebooted
> the system i tried to start the X server but it always shows the same
> message till now..I thought there maybe some problem with the newer
> version. Then i realize i havent updated the grub.conf file and this
> was my older version being loaded so* *i make the link "linux" point
> towards older version. When i do a uname -a it shows me the older
> version i.e 2.6.12-r6 of the kernel .

OK, this is where I'm a little confused. Would you, first of all, do an

emerge -pv gentoo-sources

This will not do anything (since you're using the --pretend switch);
what I want to know is whether the 'symlink' USE flag is active (+, red)
or inactive (-, blue), which will be revealed by the --verbose switch.

If it was active, then when you emerged the upgraded kernel, the
/usr/src/linux link was automatically adjusted to point to the -r10
kernel just installed, but if the USE flag is inactive, the link
remained pointing to the -r6 kernel previously existing (I assume; if
the USE flag was never active, and you never manually redirected the
links, then /usr/src/linux could still be pointing to the first kernel
you installed, for all I know).

However, the target for the /usr/src/linux symlink is not likely
relevant for this issue.

More of relevance is the directory listing of /boot.

So could you, second of all

1) mount /boot (if not mounted, and did you remember to mount /boot
before installing the new kernel?)

2) post the output of

la /boot (or ls -la /boot if you don't have the 'la' alias, but afaik,
it's a default alias for ls -la).

Oh, wait.... you install your kernels manually, and don't use 'make
install', right? Well, let's look at the output anyway, just to know
what exactly is going on.

Anyway, what you need to do in order to get grub to recognize your new
kernel is not to change the 'linux' link in /usr/src, but to change or
add an entry in grub.conf to point to the new kernel.

For instance, here's my grub.conf:
default=0
timeout=10
splashimage=(hd0,1)/grub/grub-livecd2.xpm.gz

title Gentoo_current (2.6.12-gentoo-r10)
        root (hd0,1)
        kernel /vmlinuz ro quiet root=/dev/hda5
video=vesafb:ywrap,mtrr,1280x1024-32@60
splash=silent,fadein,theme:livecd-2005.1 CONSOLE=/dev/tty1

title Gentoo_prev (2.6.12-gentoo-r9)
        root (hd0,1)
        kernel /vmlinuz.old ro root=/dev/hda5
video=vesafb:ywrap,pmipal,mtrr,1280x1024-32@60
splash=verbose,theme:emergence quiet CONSOLE=/dev/tty1

title Failsafe_current
        root (hd0,1)
        kernel /vmlinuz ro root=/dev/hda5
video=vesafb:ywrap,pmipal,mtrr,1280x1024-32@60 emergency

title SUSE LINUX 9.3
        root (hd0,1)
        kernel /vmlinuz-2.6.11.4-20a-default real_root=/dev/hda6
vga=0x317 selinux=0 splash=silent resume=/dev/hda6  showopts
        initrd /initrd-2.6.11.4-20a-default

But I use 'make install' to install my kernels, so 'vmlinuz' and
'vmlinuz.old' are symlinks to my current and previous kernels, as you
can see from the directory listing:

# la /boot

drwxr-xr-x   5 root root    2048 sep 28 14:11 .
drwxr-xr-x  23 root root     672 sep 14 14:06 ..
-rw-r--r--   1 root root     512 apr 27 14:23 backup_mbr
lrwxrwxrwx   1 root root       1 apr 27 18:52 boot -> .
lrwxrwxrwx   1 root root      24 sep 15 23:35 config ->
config-2.6.12-gentoo-r10
-rw-r--r--   1 root root   60418 mrt 24  2005 config-2.6.11.4-20a-default
-rw-r--r--   1 root root   31914 sep 15 23:35 config-2.6.12-gentoo-r10
-rw-r--r--   1 root root   32555 jul 24 02:08 config-2.6.12-gentoo-r6
-rw-r--r--   1 root root   32009 aug 28 19:18 config-2.6.12-gentoo-r9
lrwxrwxrwx   1 root root      23 sep 28 14:10 config.old ->
config-2.6.12-gentoo-r9
drwxr-xr-x   2 root root    1024 aug 23 19:57 grub
lrwxrwxrwx   1 root root      27 apr 27 14:23 initrd ->
initrd-2.6.11.4-20a-default
-rw-r--r--   1 root root 1365529 apr 27 14:23 initrd-2.6.11.4-20a-default
-rw-r--r--   1 root root       0 apr 29 00:47 .keep
drwx------   2 root root   12288 apr 27 14:13 lost+found
-rw-r--r--   1 root root  138240 apr 27 14:23 message
-rw-r--r--   1 root root     121 mrt 24  2005
README.vmlinux-2.6.11.4-20a-default.gz
-rw-r--r--   1 root root   68372 mrt 24  2005
symvers-2.6.11.4-20a-i386-default.gz
lrwxrwxrwx   1 root root      28 sep 15 23:35 System.map ->
System.map-2.6.12-gentoo-r10
-rw-r--r--   1 root root  708925 mrt 24  2005
System.map-2.6.11.4-20a-default
-rw-r--r--   1 root root  924836 sep 15 23:35 System.map-2.6.12-gentoo-r10
-rw-r--r--   1 root root 1023832 jul 24 02:08 System.map-2.6.12-gentoo-r6
-rw-r--r--   1 root root  972725 aug 28 19:18 System.map-2.6.12-gentoo-r9
lrwxrwxrwx   1 root root      27 sep 28 14:10 System.map.old ->
System.map-2.6.12-gentoo-r9
drwx------   2 root root    1024 apr 29 15:52 .Trash-root
lrwxrwxrwx   1 root root      25 sep 15 23:35 vmlinuz ->
vmlinuz-2.6.12-gentoo-r10
-rw-r--r--   1 root root 1424645 mrt 24  2005 vmlinuz-2.6.11.4-20a-default
-rw-r--r--   1 root root 3458761 sep 15 23:35 vmlinuz-2.6.12-gentoo-r10
-rw-r--r--   1 root root 2122433 jul 24 02:08 vmlinuz-2.6.12-gentoo-r6
-rw-r--r--   1 root root 3540799 aug 28 19:18 vmlinuz-2.6.12-gentoo-r9
lrwxrwxrwx   1 root root      24 sep 28 14:11 vmlinuz.old ->
vmlinuz-2.6.12-gentoo-r9

Since you manually copied your kernels, I can't hazard a guess as to
what your setup may look like, or what you may need to add to grub.conf
to get the new kernel recognized.

> Before that my Xserver was working fine. Does updating to new kernel
> effect the configuration file of Xserver.

Not really. The configuration remains the same, but since the video
driver is a kernel module, in your case the i810 driver

> (II) I810: Driver for Intel Integrated Graphics Chipsets: i810,
> i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G (II)
> Primary Device is: PCI 00:01:0

compiling a new kernel affects the foundation of the X server, rather
than its configuration.

But since you aren't using external kernel modules, as I am, it's hard
to say what your problem might be, unless you somehow confused the
system as to which kernel is supposed to be running in some way.


> Symbol __glXgetActiveScreen from module
> /usr/lib/modules/extensions/libdri.a is unresolved!

doesn't really make any sense... unless the X server is trying to run
the *new* module, against the old kernel. And one of the KDE annoyances
I've found is that it seems to go all wonky and won't start if it has
ever been started with 3D acceleration, and that functionality breaks
(which yours is, given that the error is in glXwhatever). One of the
things that gets on my nerves about KDE, but that's another story.

The whole thing makes me wonder just which kernel you compiled and
installed.

Anyway, let's get your new kernel straightened out and see if the
problem solves itself.

First of all, you want the /usr/src/linux link to point to -r10. That
way anything that needs to be compiled against the kernel will follow
that link and compile against the new kernel rather than the old.

It's up to you, of course, but if it was me, after adjusting the link, I
would check the configuration of and then recompile the new kernel. But
I like to be sure I know what I've done if I had confused myself this
way (and I have done). If you're familiar with kernel compilation--
which you seem to be, since you don't use genkernel-- copying the
.config from the old kernel and running 'make menuconfig' is not much of
a problem; heck, even running through a full 'make menuconfig' isn't a
big deal if you know the settings that your system needs to run
smoothly. Don't forget to install things in the same manner as the old
kernel, where applicable; if you previously installed the i810 module as
a loadable module, then do so again, if static then keep it static,
unless you want to be also mucking about with /etc/modules.autoload.d,
(which is easy enough, but let's try to keep the variables to a minimum
here :) ).

I would then install the kernel with 'make install' rather than manually
(don't forget to mount /boot first, like I do half the time), since
manual kernel installation just gives you more places to make mistakes,
imo, since you have to make up a name for the new kernel to avoid
overwriting the old bzImage with the new one, and I can't be bothered to
keep track of that for more than two iterations. 'make install' conforms
everything so that I don't have to keep track of it, which is fine by me.

Fix your grub.conf so that the entry to boot the new kernel goes to
vmlinuz (if you used make install, or the name of your new kernel if you
for some reason didn't), and the entry to boot the older kernel goes to
vmlinuz.old (if you used make install, etc.,etc.)

Save, unmount /boot, and see what happens when you try to boot the new
kernel. Before starting X, confirm that the new kernel is running (uname
-a again), and then see if KDE will start.

If it doesn't, check if it's failing with the same error or a different
one, and in any case, post it here so we can see what's what.

Hope this helps,
Holly
-- 
gentoo-user@g.o mailing list