linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: linux-kernel@vger.kernel.org
Subject: Where are 2.6.x upgrade notes?
Date: 13 Jan 2004 02:55:46 -0500	[thread overview]
Message-ID: <87ptdocmf1.fsf@stark.xeocode.com> (raw)


I'm trying to upgrade to 2.6.1 and running into a number of roadblocks. Before
I start asking stupid questions on mailing lists I'm wonder if there's a
document that lists the typical problems people will run into upgrading?

So far I've bumped into and knew or found how to solve:

. Need to install module-init-tools package

. Need to migrate modules.conf to modprobe.conf
  In my case it doesn't load sound drivers without it

. Alsa starts muted (Everyone knows that right?)

I still have a few problems that I'm stumped on:

. I still get no sound even though every channel is unmuted and the volume
  raised and there are no errors.

  Incidentally, which version of Alsa is included in 2.6.1? Is it the 1.0.1
  release? Or a pre 1.0 release? There are no version numbers anywhere that I
  can find in the dmesg output or the source.

. Mouse wheel doesn't work in X

Surely these are common problems that everyone's faced and there's a simple
Upgrade FAQ somewhere like there was with 2.4?

-- 
greg


             reply	other threads:[~2004-01-13  7:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13  7:55 Greg Stark [this message]
2004-01-13 10:58 ` Where are 2.6.x upgrade notes? Maciej Soltysiak
2004-01-13 19:59   ` Dave Jones
2004-01-14  7:45   ` No mouse wheel under 2.6.1 [Was: Re: Where are 2.6.x upgrade notes?] Greg Stark
2004-01-14  7:51     ` Ralf Hildebrandt
2004-01-14 23:57     ` Thomas Molina
2004-01-17 15:20     ` Joaquim Fellmann
2004-01-17 20:37       ` Greg Stark
2004-01-17 23:18         ` Vojtech Pavlik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ptdocmf1.fsf@stark.xeocode.com \
    --to=gsstark@mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).