public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ajai Khattri <ajai@bway.net>
To: Greg KH <gregkh@gentoo.org>
Cc: Matthew Marlowe <matt@deploylinux.net>,
	 gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] 2004.2 Feature Requests
Date: Sat, 1 May 2004 14:10:45 -0400 (EDT)	[thread overview]
Message-ID: <Pine.BSO.4.58.0405011409220.26804@ida.bway.net> (raw)
In-Reply-To: <20040501015259.GB16006@kroah.com>

On Fri, 30 Apr 2004, Greg KH wrote:

> That's nasty.  Did you report to the hotplug/kernel people?
>
> Hardware detection is hard for all systems.  If it's not
> USB/PCI/Firewire, it is _very_ hard.

Ive had problems with this too on almost every server Ive built.
I generally end up doing "smp-nofb doscsi nodetect nousb nodhcp" to boot
the LiveCD and then load modules by hand...

-- 
Aj.
Sys. Admin / Developer

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-05-01 17:59 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-01  0:37 [gentoo-dev] 2004.2 Feature Requests Matthew Marlowe
2004-05-01  1:52 ` Greg KH
2004-05-01 18:10   ` Ajai Khattri [this message]
2004-05-01 19:10 ` Chris Gianelloni
2004-05-02 23:46   ` Nick Rout
2004-05-02 23:56     ` John Davis
2004-05-03  0:26       ` Jay Maynard
  -- strict thread matches above, loose matches on Subject: below --
2004-04-30  3:42 John Davis
2004-04-30  6:03 ` Joshua Brindle
2004-04-30  7:25   ` Kurt Lieber
2004-04-30 16:37     ` Pieter Van den Abeele
2004-05-02 17:01       ` Donnie Berkholz
2004-05-02 19:34         ` Pieter Van den Abeele
2004-05-02 19:50           ` Nathaniel McCallum
2004-05-02 20:02           ` Paul de Vrieze
2004-04-30 13:39   ` Eric Sammer
2004-05-04  5:23   ` Jason Huebel
2004-05-04  9:04     ` Bjoern Michaelsen
2004-05-04 12:31     ` Troy Dack
2004-05-04 12:35       ` Allen D Parker
2004-05-04 14:31       ` Jason Huebel
2004-05-04 17:00         ` david
2004-05-04 17:21           ` Georgi Georgiev
2004-05-04 22:28             ` Josh Grebe
2004-05-04 22:44               ` Georgi Georgiev
2004-05-08  4:00         ` John Davis
2004-04-30  6:16 ` Kumba
2004-04-30  7:22   ` Joshua Brindle
2004-04-30  7:43     ` Kumba
2004-04-30  7:56       ` Sven Vermeulen
2004-04-30  7:25   ` Sven Vermeulen
2004-04-30  7:48     ` Kumba
2004-04-30 16:44     ` Pieter Van den Abeele
2004-04-30 16:33   ` Pieter Van den Abeele
2004-04-30  7:05 ` Stuart Herbert
2004-04-30 17:37 ` Marius Mauch
2004-04-30 18:15   ` Lars Strojny
2004-05-01 12:23     ` Sven Vermeulen
2004-04-30 22:51   ` N. Owen Gunden
2004-04-30 23:07     ` Jon Portnoy
2004-04-30 23:21       ` N. Owen Gunden
2004-04-30 23:29         ` Jon Portnoy
2004-04-30 23:47           ` Stuart Herbert
2004-05-01  2:16     ` Dan Podeanu
2004-05-01 19:10       ` Chris Gianelloni
2004-05-01 22:21         ` Greg KH
2004-04-30 17:54 ` Lisa Seelye
2004-04-30 19:01 ` John Davis
2004-04-30 23:50 ` Spider
2004-05-01 11:50 ` Heinrich Wendel
2004-05-01 23:41 ` Jason Stubbs
2004-05-03 11:05 ` Josh Glover
2004-05-03 11:10   ` Peter Ruskin
2004-05-07  3:33 ` Olivier Fisette
2004-05-07 19:42   ` Stuart Herbert
2004-05-07  4:26 ` Nick Rout
2004-05-07  6:57   ` Christian Parpart
2004-05-07 15:26     ` Donnie Berkholz
2004-05-07 15:15   ` Chris Bainbridge

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=Pine.BSO.4.58.0405011409220.26804@ida.bway.net \
    --to=ajai@bway.net \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gregkh@gentoo.org \
    --cc=matt@deploylinux.net \
    /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