On Fri, Aug 19, 2005 at 11:27:37PM -0600, Bob Proulx wrote:
> L.V.Gandhi wrote:
> > Bob Proulx wrote:
> They are complementary. The discover process runs at boot time to
> load up statically attached hardware. This would typically be things
> like PCI network cards, PCI sound cards, and things li
Malcolm Carlock wrote:
> I guess my only wonderment is why these utilities aren't installed by
> default.
Good question. But the problem is how to do that?
Certainly the new kernel you are installing does not *require* the
'discover' package to be installed. So the kernel package can't list
it
Bob Proulx wrote:
Install 'discover' and 'hotplug' and that should take care of most of
your problems. Those are hardware discovery programs. They will map
the hardware found to the current device drivers. Very nice.
If you have the 2.6 kernel installed then install 'udev' too since it
makes
On 8/20/05, Bob Proulx <[EMAIL PROTECTED]> wrote:
> L.V.Gandhi wrote:
> > Bob Proulx wrote:
> > > Install 'discover' and 'hotplug' and that should take care of most of
> > > your problems. Those are hardware discovery programs. They will map
> > > the hardware found to the current device drivers.
L.V.Gandhi wrote:
> Bob Proulx wrote:
> > Install 'discover' and 'hotplug' and that should take care of most of
> > your problems. Those are hardware discovery programs. They will map
> > the hardware found to the current device drivers. Very nice.
>
> Whether both discover and hot plug are comp
On 8/19/05, Bob Proulx <[EMAIL PROTECTED]> wrote:
> Install 'discover' and 'hotplug' and that should take care of most of
> your problems. Those are hardware discovery programs. They will map
> the hardware found to the current device drivers. Very nice.
Whether both discover and hot plug are c
M Carlock wrote:
> I recently upgraded from woody to sarge per the
> instructions (aptitude etc), which was successful.
>
> However, after then upgrading the kernel from
> 2.2.20-idepci to 2.6.8-2-386, I found I could boot OK,
> but I'd lost eth0 and the ATI framebuffer.
>
> lspci can see both de
Mark Fletcher wrote:
M Carlock wrote:
I recently upgraded from woody to sarge per the
instructions (aptitude etc), which was successful.
However, after then upgrading the kernel from
2.2.20-idepci to 2.6.8-2-386, I found I could boot OK,
but I'd lost eth0 and the ATI framebuffer.
lspci can s
M Carlock wrote:
I recently upgraded from woody to sarge per the
instructions (aptitude etc), which was successful.
However, after then upgrading the kernel from
2.2.20-idepci to 2.6.8-2-386, I found I could boot OK,
but I'd lost eth0 and the ATI framebuffer.
lspci can see both devices, but I'
On Wednesday 17 August 2005 04:37, M Carlock wrote:
> I recently upgraded from woody to sarge per the
> instructions (aptitude etc), which was successful.
>
> However, after then upgrading the kernel from
> 2.2.20-idepci to 2.6.8-2-386, I found I could boot OK,
> but I'd lost eth0 and the ATI frame
I recently upgraded from woody to sarge per the
instructions (aptitude etc), which was successful.
However, after then upgrading the kernel from
2.2.20-idepci to 2.6.8-2-386, I found I could boot OK,
but I'd lost eth0 and the ATI framebuffer.
lspci can see both devices, but I'm at a loss as to
ho
11 matches
Mail list logo
