From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266737AbUF3QW6 (ORCPT ); Wed, 30 Jun 2004 12:22:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266762AbUF3QW6 (ORCPT ); Wed, 30 Jun 2004 12:22:58 -0400 Received: from ss1000.ms.mff.cuni.cz ([195.113.20.8]:36023 "EHLO ss1000.ms.mff.cuni.cz") by vger.kernel.org with ESMTP id S266737AbUF3QU5 (ORCPT ); Wed, 30 Jun 2004 12:20:57 -0400 Date: Wed, 30 Jun 2004 18:20:54 +0200 From: Rudo Thomas To: Tom Felker Cc: Sean Champ , linux-kernel@vger.kernel.org Subject: Re: problems with CF card reader, kernel 2.6.7 Message-ID: <20040630162054.GA22476@ss1000.ms.mff.cuni.cz> Mail-Followup-To: Tom Felker , Sean Champ , linux-kernel@vger.kernel.org References: <20040630101605.GA3568@tokamak.homeunix.net> <200406301108.02618.tcfelker@mtco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200406301108.02618.tcfelker@mtco.com> User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > This is a stab in the dark, but try running "eject /dev/sg0" on the generic > device coresponding to the card reader (or maybe the disc device, I'm not > sure), after putting the new card in. This forces the kernel to reread the > card's partition table. Actually, this is better done with "blockdev --rereadpt /dev/sda" or similar. Rudo.