Re: boot issue with a proliant 350 server

2006-09-25 Thread Frank Guthorel
Hi,

thanks for the tip - I'll try to figure that out first ...

greetings
frank

Geert Stappers wrote:
 On Wed, Sep 20, 2006 at 05:09:52PM +0200, Frank Guthorel wrote:
 Hello,

 I'm trying to let a first generation Compaq Proliant 350 Server run
 Debian, but the 3.1 netinstall CD lets me know that no hard discs are
 available to install it too.
 
 [ further description of the challenge ]
 
 thanks in advance, I appreciate any pointers you people might have
 
 As I understand the problem^Wchallenge is this about new hardware
 where the not the right driver or no driver is loaded.
 
 Loading a driver is done by loading a kernel module, that can be done
 with the command `modprobe modulename`.
 The tricky part is finding out the actual kernel module name.
 
 With `lspci` and `lspci -n` you get a list of the PCI devices in your
 computer.
 
 
 Cheers
 Geert Stappers
 
 
 This e-mail has been scanned for all viruses by Star Internet. The
 service is powered by MessageLabs. For more information on a proactive
 anti-virus service working around the clock, around the globe, visit:
 http://www.star.net.uk
 
 

-- 
Frank Guthorel
Director Interactive

Porter Novelli
Bomastraat 14A
B-9000 Gent

+32 (0)9 223 88 10 (phone)
+32 (0)9 233 03 50 (fax)
+32 (0)479 98 98 91 (mobile)

[EMAIL PROTECTED]
http://www.porternovelli.be



signature.asc
Description: OpenPGP digital signature


Re: boot issue with a proliant 350 server

2006-09-24 Thread Geert Stappers
On Wed, Sep 20, 2006 at 05:09:52PM +0200, Frank Guthorel wrote:
 Hello,
 
 I'm trying to let a first generation Compaq Proliant 350 Server run
 Debian, but the 3.1 netinstall CD lets me know that no hard discs are
 available to install it too.

 [ further description of the challenge ]

 thanks in advance, I appreciate any pointers you people might have

As I understand the problem^Wchallenge is this about new hardware
where the not the right driver or no driver is loaded.

Loading a driver is done by loading a kernel module, that can be done
with the command `modprobe modulename`.
The tricky part is finding out the actual kernel module name.

With `lspci` and `lspci -n` you get a list of the PCI devices in your
computer.


Cheers
Geert Stappers


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]