Re: Fresh Install Problems
Douglas Allan Tutty wrote: On Sun, Jan 21, 2007 at 07:49:21PM -0600, smugzilla wrote: That brings me to my next question: why are the kernel naming conventions inconsistent? uname -r says I am currently running 2.6.8-em64t-p4-smp but no corresponding version of kernel 2.6.18 is available from Arizona's sid repository. They do have a version for amd64, which is what I would have thought I needed, but now I'm confused. What kernel flavor am I looking for, assuming that my CPU is an old Athlon 64? Pete You may have missed the naming convention change from kernel-image-*** to linux-image-***. I think this was done to allow futuer non-linux (e.g. HURD) kernels. Doug. No, I didn't miss it. I'm searching for linux-image-*** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Fresh Install Problems
Goswin von Brederlow wrote: smugzilla <[EMAIL PROTECTED]> writes: I'm trying a fresh install of debian on my old Athlon 64 3200 box and this one is not proceeding as smoothly as the previous one. The initial install is smooth enough (I'm not even trying to install gnome yet) but I'm having problems as soon as I try to upgrade to sid. Basically the chain of events looks like this: 1. After the initial install I'm running kernel 2.6.8-12-em64t-p4-smp. I have no idea why I appear to have an smp-enabled kernel, but this is what I get when doing a basic install without tweaking the default settings. 2. I change my repositories to point to sid at Arizona. 3. apt-get update runs fine... 4. But when I run apt-get dist-upgrade I get a prompt with a warning that essentially says "You are running a kernel and attempting to remove the same version." I choose "No" when asked if I really want to remove the running kernel, then get two more error messages: "dpkg: error procecssing kernel-image-2.6.8.12..." "dpkg: initrd-tools: dependency problems, but removing anyway" After this my system seems pretty hosed: initrd-tools is gone and so I can't install any non-trivial packages and base-config is gone. Where did I screw up, and how do I fix this? Doing a fresh install and starting again from scratch is definitely an option here. That doesn't realy sound like anything is wrong. Kernel 2.6.8 is to be replaced by 2.6.18, initrdtools by initramfs or yaird or something else more modern and base-config is no more. The only problem is that removing kernel-image-2.6.8.12... fails and without further details it is hard to say why. I guess it is that the package is broken, which would be a serious problem to handle. Please file a bug about it on the kernel-image-2.6.8.12 package with more info. As a workaround try installing a newer kernel from sid before you do an upgrade. Then, after an reboot, remove the old one. Once you managed that go on and upgrade. MfG Goswin That brings me to my next question: why are the kernel naming conventions inconsistent? uname -r says I am currently running 2.6.8-em64t-p4-smp but no corresponding version of kernel 2.6.18 is available from Arizona's sid repository. They do have a version for amd64, which is what I would have thought I needed, but now I'm confused. What kernel flavor am I looking for, assuming that my CPU is an old Athlon 64? Pete -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Fresh Install Problems
I'm trying a fresh install of debian on my old Athlon 64 3200 box and this one is not proceeding as smoothly as the previous one. The initial install is smooth enough (I'm not even trying to install gnome yet) but I'm having problems as soon as I try to upgrade to sid. Basically the chain of events looks like this: 1. After the initial install I'm running kernel 2.6.8-12-em64t-p4-smp. I have no idea why I appear to have an smp-enabled kernel, but this is what I get when doing a basic install without tweaking the default settings. 2. I change my repositories to point to sid at Arizona. 3. apt-get update runs fine... 4. But when I run apt-get dist-upgrade I get a prompt with a warning that essentially says "You are running a kernel and attempting to remove the same version." I choose "No" when asked if I really want to remove the running kernel, then get two more error messages: "dpkg: error procecssing kernel-image-2.6.8.12..." "dpkg: initrd-tools: dependency problems, but removing anyway" After this my system seems pretty hosed: initrd-tools is gone and so I can't install any non-trivial packages and base-config is gone. Where did I screw up, and how do I fix this? Doing a fresh install and starting again from scratch is definitely an option here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: soundcard not detected by alsaconf
Tony Andrews wrote: I've been trying all day to get the sound up and running, but no dice. I have the chaintech vnf4 ultra which has onboard nvidia sound. I have the snd-intel8x0 driver module and modprobe gives no error. I tried commenting out the oss modules but I'm not to sure that I did a thorough job(im a newb) Here's my lsmod output: debian:~# lsmod Module Size Used by isofs 36492 0 nvidia 4384040 12 ipv6 264296 8 af_packet 23308 2 usblp 13696 0 ehci_hcd 30852 0 ohci_hcd 21252 0 tsdev 8576 0 mousedev 11852 1 evdev 10944 0 snd_intel8x0 35988 0 snd_ac97_codec 3220 1 snd_intel8x0 snd_pcm_oss 56680 0 snd_mixer_oss 9520 1 snd_pcm_oss snd_pcm 100876 2 snd_intel8x0,snd_pcm_oss snd_timer 24968 1 snd_pcm snd_page_alloc 12944 2 snd_intel8x0,snd_pcm gameport 5120 1 snd_intel8x0 snd_mpu401_uart 8192 1 snd_intel8x0 snd_rawmidi 26532 1 snd_mpu401_uart snd_seq_device 9164 1 snd_rawmidi snd 56936 9 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi, snd_seq_device soundcore 11232 1 snd psmouse 19340 0 ide_cd 42016 0 cdrom 39208 1 ide_cd forcedeth 18432 0 ext3 119760 1 jbd 58288 1 ext3 mbcache 9928 1 ext3 ide_generic 1856 0 ide_disk 20864 3 amd74xx 14768 1 ide_core 154336 4 ide_cd,ide_generic,ide_disk,amd74xx unix 29696 408 font 9152 0 vesafb 6960 0 cfbcopyarea 4160 1 vesafb cfbimgblt 3328 1 vesafb cfbfillrect 4352 1 vesafb As you can see there's still oss modules loaded(told you im a newb). I'm not sure is thats significant but i'm sure that I don't know what else to try. Its a Debian 64bit distro running 2.6.8-11-amd64-k8 kernel and I believe that the alsa drivers are on by default. any help would be appreciated. Upgrade your kernel to 2.6.12 or better. Worked for me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
