Results 11 to 16 of 16
mm not much help
you should blacklist the pcihp and shpchp modules in /etc/hotplug/blacklist
and you should upgrade to kernel 2.6
(it is on the 2nd cd as a package ...
- 12-03-2005 #11Linux Enthusiast
- Join Date
- Jun 2005
- Posts
- 668
mm not much help
you should blacklist the pcihp and shpchp modules in /etc/hotplug/blacklist
and you should upgrade to kernel 2.6
(it is on the 2nd cd as a package in testing)
come back after you've done that , and then give us a dmesg again.
its certainly not picking it up at the moment, but you should be using a 2.6 kernel for more hardware support really
in my opinion.
- 12-03-2005 #12"you should blacklist the pcihp and shpchp modules in /etc/hotplug/blacklist"
Originally Posted by kern
i have no idea what this means....
also, in the second cd there is no testing/ dir there is
(dont ask me why my hostname is mshome..because i dont know...)Code:gmp@mshome:/mnt/cdrom$ ls CHECKSUMS.md5 CHECKSUMS.md5.asc FILELIST.TXT README.TXT linux-2.6.13/ slackware/ gmp@mshome:/mnt/cdrom$
my bet the 2.6 kernel would be in linux-2.6.13/ wouldnt ya think...
i know the slackware package thing in .tgz and the is kernel-source-2.6.13-noarch-1.tgzCode:gmp@mshome:/mnt/cdrom/linux-2.6.13$ ls README.initrd kernel-headers-2.6.13-i386-1.txt alsa-driver-1.0.9b_2.6.13-i486-1.tgz kernel-headers.WARNING alsa-driver-1.0.9b_2.6.13-i486-1.tgz.asc kernel-modules-2.6.13-i486-1.tgz alsa-driver-1.0.9b_2.6.13-i486-1.txt kernel-modules-2.6.13-i486-1.tgz.asc kernel-generic-2.6.13-i486-1.tgz kernel-modules-2.6.13-i486-1.txt kernel-generic-2.6.13-i486-1.tgz.asc kernel-source-2.6.13-noarch-1.tgz kernel-generic-2.6.13-i486-1.txt kernel-source-2.6.13-noarch-1.tgz.asc kernel-headers-2.6.13-i386-1.tgz kernel-source-2.6.13-noarch-1.txt kernel-headers-2.6.13-i386-1.tgz.asc gmp@mshome:/mnt/cdrom/linux-2.6.13$
should i just use pkgtool and install all of those things?
- 12-03-2005 #13Linux Enthusiast
- Join Date
- Jun 2005
- Posts
- 668
I'd upgrade the 2.4 modules and package to 2.6
and if you notice your dmesg there are a load of errors regarding those two modules I told you to blacklist, and where to blacklist.
thats another matter completely though.
and yes, they are the packages for 2.6 kernel. remember to use the 2.4 headers though, as you are supposed to use the same kernel headers that the glibc you run was compiled _on_.
its not hard to upgrade to 2.6 via packages, instead of using 'pkgtool' why dont you learn how to use package tools 'install/upgrade/removepkg'
- 12-03-2005 #14Linux Enthusiast
- Join Date
- Jun 2005
- Posts
- 668
what does 'cat /etc/HOSTNAME' say?
you probably setup your hostname wrong thinking it was the xp workgroup name.
- 12-05-2005 #15
Ok, so which of these do i install?
and i can install packages by going installpkg packagename.tgz is that what you mean
gmp@mshome:~$cat /etc/HOSTNAMECode:gmp@mshome:/mnt/cdrom/linux-2.6.13$ ls README.initrd kernel-headers-2.6.13-i386-1.txt alsa-driver-1.0.9b_2.6.13-i486-1.tgz kernel-headers.WARNING alsa-driver-1.0.9b_2.6.13-i486-1.tgz.asc kernel-modules-2.6.13-i486-1.tgz alsa-driver-1.0.9b_2.6.13-i486-1.txt kernel-modules-2.6.13-i486-1.tgz.asc kernel-generic-2.6.13-i486-1.tgz kernel-modules-2.6.13-i486-1.txt kernel-generic-2.6.13-i486-1.tgz.asc kernel-source-2.6.13-noarch-1.tgz kernel-generic-2.6.13-i486-1.txt kernel-source-2.6.13-noarch-1.tgz.asc kernel-headers-2.6.13-i386-1.tgz kernel-source-2.6.13-noarch-1.txt kernel-headers-2.6.13-i386-1.tgz.asc gmp@mshome:/mnt/cdrom/linux-2.6.13$
mshome.gmp
gmp@mshome:~$
theres the hostname thingy
- 12-05-2005 #16Linux Enthusiast
- Join Date
- Jun 2005
- Posts
- 668
there you go then, your hostname is wrong, edit it.
as for the kernel, init 1, then install the kernel-generic/kernel-modules pkg's , and remove the 2.4 ones. but do not install the kernel-source, or kernel-headers 2.6 packages.
then remove kernel-generic and kernel-modules packages for _2.4_
make sure you can "lilo -v" with no errors to replace the MBR, and check the /boot/vmlinuz symlink to see if it points to 2.6 and not 2.4
once you've done that, see if your new kernel loads and then give us your dmesg/lsmod/ again
thanks!


Reply With Quote
