Re: eth0 not coming up after reboot
On Sun, Mar 19, 2006 at 11:38:21PM +, Mitchell Laks wrote: Geert Stappers stappers at debian.org writes: Please provide the output of uname -r from the computer we are talking about. standard etch install linu-image-2.6.15-1-486 Okay, 2.6 kernel (not a 2.4 that _I_ feared) 1) I Follow up. I restored the system to prior state, and rebooted multiple times and now eth0 comes up. I dont know what was wrong before... You can ignore it. Will do, also the other topics raised. Please avoid non-related issues in the same E-mail. (put them in seperate messages) Cheers Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
eth0 not coming up after reboot, highmem not enabled in kernel
Hi, I did a install of etch using the latest release installer. It went nicely. I have two comments and 1 related question. I installed and immediately upgraded to sid. (naughty me). I think of using the latest installer as the best way to get to my preferred desktop :). 2 Issues that I noticed, and 1 separate related question. 1) As soon as I rebooted into my system after the upgrade to sid I noticed that the eth0 was not comming up! So I had to su and do ifup eth0. Then I rebooted again to check and again needed to do ifup eth0. What was wrong? I looked in /etc/network/interfaces and saw all this cruft (i hope that is not a bad word). I saw # This is a list of hotpluggable network interfaces. # They will be activated automatically by the hotplug subsystem. mapping eth0 script grep map eth0 # The primary network interface allow-hotplug eth0 iface eth0 inet static address 192.x.x.x ## instead of what I usually see auto eth0 iface eth0 inet static etc So I simply commented out the cruft replaced by good stuff and rebooted and all was well. What was the problem? What does this new stuff 'add' and what wentwrong? 2) I have 2GB of ram and the installed kernel has no highmem support I had to recompile my own kernel to get support for my RAM. dmesg Warning only 896MB will be used. Use a HIGHMEM enabled kernel I would have preferred if the default kernel would enable highmem. Is that possible. 3) Also, I do have a way cool dual core amd64 processor here to play with. On the other had I really should not futz around too much with chroots and stuff and would like to use all the binary drivers I need for graphics development as well as debian free software so I think (???) I don't want to shift over to amd64 arch as yet. Thus I need ooffice and I need nvidia drivers for 6600GT video card for opengl. So what debian kernel package with highmem can i select. will linux-image-2.6.15-1-k7-smp work on my system? I prefer using a debian kernel for ease of use. For instance Last night i compiled the new kernel by downloading a fresh linux-2.6.15-6 tarball and copying over the debian /boot/config-2.6.15-1-486 to /usr/src/linux and modifying by selecting the Processor Family Opteron/athlon64/hammer/k8 and enabled multiprocessor support and configured high memory support 4GB and otherwise left it as debian had it for the 486. Thus i see CONFIG_X86_PC=y CONFIG_MK8=y and alot of stuff like CONFIG_X86_GENERIC=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_CMPXCHG64=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_TSC=y CONFIG_HPET_TIMER=y Ok. So what does it mean. Am I just using a 32bit kernel with selection of amd64 dual processor? Where can I read more about this? Thanks Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: eth0 not coming up after reboot
On Sun, Mar 19, 2006 at 04:32:07PM +, Mitchell Laks wrote something like: Hi, I did a install of etch using the latest release installer. It went nicely. I | have one comment and a related question. | As soon as I rebooted into my system after the upgrade to sid I noticed that the eth0 was not comming up! So I had to su and do ifup eth0. Then I rebooted again to check and again needed to do ifup eth0. What was wrong? Euh, for some reason was 'ifup eth0' not called (not activated). I looked in /etc/network/interfaces and saw all this cruft (i hope that is not a bad word). They are called stanzas, see `man interfaces` for more information. (When I understood you correct, then was cruft a good word :- ) I saw # This is a list of hotpluggable network interfaces. # They will be activated automatically by the hotplug subsystem. mapping eth0 script grep map eth0 # The primary network interface allow-hotplug eth0 iface eth0 inet static address 192.x.x.x ## instead of what I usually see auto eth0 iface eth0 inet static etc So I simply commented out the cruft replaced by good stuff and rebooted and all was well. What was the problem? What does this new stuff 'add' and what wentwrong? Frankly my dear, I can only guess (and ask further questions). Please provide the output of uname -r from the computer we are talking about. Cheers Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: eth0 not coming up after reboot
Geert Stappers stappers at debian.org writes: Please provide the output of uname -r from the computer we are talking about. standard etch install linu-image-2.6.15-1-486 1) I Follow up. I restored the system to prior state, and rebooted multiple times and now eth0 comes up. I dont know what was wrong before... You can ignore it. 2) Why doesn't debian kernel linux-image-2.6.15-1-486 enable highmem to 4GB. A 1GB memory card (or 2 x512)is very common these days. 3) I now understand the difference between setting up a 64 bit kernel and selecting k8 optimization kernel. I still think there is a need for linux-image-2.6.15-1-k8 and linux-image-2.6.15-1-k8-smp in 386 tree of debian... Thanks for your help, Mitchell Laks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: eth0 not coming up after reboot
On Monday 20 March 2006 00:38, Mitchell Laks wrote: 1) I Follow up. I restored the system to prior state, and rebooted multiple times and now eth0 comes up. I dont know what was wrong before... You can ignore it. If you have multiple NICs in your system, you may be hit by somewhat random device changes. See the errata for the Etch Beta 2 release [1] for further info. 2) Why doesn't debian kernel linux-image-2.6.15-1-486 enable highmem to 4GB. A 1GB memory card (or 2 x512)is very common these days. You'll have to ask the Debian kernel maintainers, not us. 3) I now understand the difference between setting up a 64 bit kernel and selecting k8 optimization kernel. I still think there is a need for linux-image-2.6.15-1-k8 and linux-image-2.6.15-1-k8-smp in 386 tree of debian... Also an issue for the kernel team. We just work with what they offer. Cheers, FJP [1] http://www.debian.org/devel/debian-installer/errata pgp4swrk6wOzN.pgp Description: PGP signature
