- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Kernel 2.6.5
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2004 05:11 AM
тАО05-13-2004 05:11 AM
Has someone a working .config for a Proliant DL 140 and kernel 2.6.X or lower
I have everything almost at work except for the network. I have choose the bcm5700 module and it load without problems, but the network won't com up. I must missing some kernel setting.
So if someone is willing to share his .config file...
TIA
Patrick
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2004 07:14 AM
тАО05-13-2004 07:14 AM
Re: Kernel 2.6.5
Nice idea, but I wouldn't start using other peoples .config file if I were you. You could get yourself in all sorts of problems. Allthough the hardware might be the same, there are so many other things that might be different you might seriously break something.
Lets try and resolve your networking issue instead :)
THe network module loads fine. Does "ifconfig -a" show you your network interface? If it does, you only need to configure it properly. Make sure tcp/ip is set up correctly (ping localhost). There are lots of things to try. Give us more information!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2004 10:22 AM
тАО05-13-2004 10:22 AM
Re: Kernel 2.6.5
This one is the community backed driver, compared to the one by broadcomm or whatever their new name is, which is considered, to say gently, to be a little too fat.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2004 08:55 PM
тАО05-13-2004 08:55 PM
Re: Kernel 2.6.5
Just a error that they dit not get a DHCP address.
I also have activated the Serverworks chipset in the kernel config.
The idee of asking a "working" .config is to see what other people uses with sutch machine an learn from them not blindly to use it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2004 12:51 AM
тАО05-14-2004 12:51 AM
SolutionYou should indeed try to address the network issue first. If everything works but the network, try first to understand what does not work. Maybe you DHCP server is not working fine... as simple as this.
0. Can you do a "ifconfig eth0" without getting an error but status of the card?
1. Does "dmesg3 output reports activities with network interfaces?
# dmesg | grep eth
2. Can you stop the network service then restart it without getting an error?
On RH: service network restart
Debian: /etc/init.d/networking restart
Maybe you dhclient/pump binary is not installed, wich means the system is unable to perform a DHCP request.
3. Is the command "ping 127.0.0.1" working fine without giving errors?
If you are running RedHat, you might send us a "sysreport" output to let us help you.
Hope it helps a bit.
Yours,
Emmanuel