Re: [Cooker] 8.2 RC1 install and cooker updates

2002-03-16 Thread Borsenkow Andrej

÷ óÂÔ, 16.03.2002, × 00:26, Serge Pluess ÎÁÐÉÓÁÌ:
 But if I reboot I can't start X unless I do a insmod NVdriver manually as 
 root first.
 
 The line it puts into modules.conf is:
 alias /dev/nvidia/* NVdriver
 

alias /dev/nvidia* NVdriver

remove the slash. If it works for you send bug report to nVidia. If they
get many bug reports chances are they release updated driver when 8.2 is
out.

 I tried to change that to :
 alias char-major-195 NVdriver
 

no it's not going to work with devfs. Ideally you want both lines so
that both devfs and non-devfs cases work.

-andrej




[Cooker] 8.2 RC1 install and cooker updates

2002-03-15 Thread Serge Pluess

Installed 8.2 RC1. Overall great experience. I tried to go through the 
mailing list and through other archive/google searches and managed a few 
things that I couldn't figure out completely. I apologize ff it has come up 
before and it has slipped passed me.

The only thing I noticed from the regular install has to do with the 
network settings.

The install asks for the following settings for the network:

Hostname:
DNS Server:
Gateway:

I put in the FQDN with the hostname, so  machinename.mydomain.com

After the install is through I can't ping any machine on mydomain.com. So I 
check the various configuration files and find the following:

resolv.conf has the following entries:

   search localdomain

   nameserver xxx.yyy.zzz.qqq

Then I look at the file /etc/sysconfig/network and see that the HOSTNAME is 
set to
machinename.mydomain.com but the DOMAINNAME is set to localdomain.

At this stage I can't ping hostnames on my network without the full domainname.

So I add the line domain mydomain.com to resolv.conf  and now I can ping 
hostnames without the domain. I also change the DOMAINNAME line in 
/etc/sysconfig/network to reflect mydomain.com.

I checked on a Redhat 7.2 machine and saw that resolv.conf doesn't have the 
domain line in it and the network file doesn't have the DOMAINNAME line but 
I can ping hostnames on my domain without the full domainname.

Not sure where else to look for this.

The next thing I noticed is when I do updates with the current cooker is 
that it updates bootsplash among other things (version is 1.3.9-1mdk). Now 
with the new one installed the graphical screen disappears and only the 
Mandrake logo shows up under the kernel version. Then I get a black screen 
with the white text for the few init lines. On shutdown I get a black 
screen with a blue bar going accross the bottom.

So I uninstalled the update and then reinstalled the one that came with RC1 
(1.3.8-1mdk) and still the same result. Can't get it back to the graphical 
way of just after the RC1 install.
Also reran lilo and also tried to recreate a new initrd.

This happened also when I did a bootsplash upgrade with Beta 4.

Next install is the emu10k1-tools-0.9.4-1mdk as I have a SB Live 5.1 with 
Digital Boston Speakers.
The rpm installs the needed files like /usr/bin/emu-config , 
/usr/bin/emu10k1-ctl (why was this one renamed from the original package??) 
and /etc/emu.conf where I set the Digital Speaker option to Yes.

If I run the command /usr/bin/emu-config -d manually then everything works 
fine. The documentation then says to add the following lines to the 
/etc/modules.conf :
post-install emu10k1 /usr/bin/emu10k1-ctl

That doesn't work. Only got it to work by adding the following line instead:
post-install emu10k1 /usr/bin/emu-config -d

But that circumvents the use of the options file in /etc

And last but not least :-)  I have a Geforce 2MX 400 and I downloaded the 
newest drivers from NVIDIA (source files for GLX and kernel).
Both compile and install go smooth and X starts properly and all 3D apps 
work great.
But if I reboot I can't start X unless I do a insmod NVdriver manually as 
root first.

The line it puts into modules.conf is:
alias /dev/nvidia/* NVdriver

I tried to change that to :
alias char-major-195 NVdriver

but it still doesn't get loaded at boot time. The only way so far I found 
is to do the manual insmod NVdriver after every boot. (I know that these 
are proprietary drivers and this might not be the right place to discuss 
issues with them, but still thought I would at least mention this).

Ok, I think that's it so far. Am looking forward to the released version 
and see if the above issues will be gone or maybe there are some simple 
fixes for them.

Thank you

Serge