jfz Posted March 15, 2004 Report Share Posted March 15, 2004 I am unable to get Mandrake 10.0 to boot successfully with the enterprise kernel, unless I disable the onboard gigabit NIC on my Intel motherboard. Enabled, the kernel hangs during boot bringing up eth0. Same story with the SMP kernel. The "plain vanilla" linux kernel DOES successfully configure and boot with the NIC enabled, so it can apparently be done (which is how I'm posting this now). Unfortunately, this plain kernel has no idea what to make of my P4's hyperthreading (only one virtual CPU listed under /proc/cpuinfo), and sees less than half of my 2 GB of RAM. I'm just hoping somebody has also seen this behavior and can provide some ideas; if need be, I may have access to a PCI NIC I can try and swap in, but I'm hoping that won't be necessary. System details: 3.0 GHz P4 Intel D875PBZLK mobo 2 GB DDR400 memory MSI GF4 MX440 video SB Live 5.1 audio Liteon burner/DVD ROM drives NB: This same system had been running fine for months under MDK 9.1, only requiring a manual build and install of the NIC driver from a tarball on Intel's website. I already checked, there's nothing there for the 2.6 kernel, unfortunately. Quote Link to comment Share on other sites More sharing options...
thinkliberty Posted March 15, 2004 Report Share Posted March 15, 2004 I am unable to get Mandrake 10.0 to boot successfully with the enterprise kernel, unless I disable the onboard gigabit NIC on my Intel motherboard. Enabled, the kernel hangs during boot bringing up eth0. Same story with the SMP kernel. The "plain vanilla" linux kernel DOES successfully configure and boot with the NIC enabled, so it can apparently be done (which is how I'm posting this now). Unfortunately, this plain kernel has no idea what to make of my P4's hyperthreading (only one virtual CPU listed under /proc/cpuinfo), and sees less than half of my 2 GB of RAM. I'm just hoping somebody has also seen this behavior and can provide some ideas; if need be, I may have access to a PCI NIC I can try and swap in, but I'm hoping that won't be necessary. System details: 3.0 GHz P4 Intel D875PBZLK mobo 2 GB DDR400 memory MSI GF4 MX440 video SB Live 5.1 audio Liteon burner/DVD ROM drives NB: This same system had been running fine for months under MDK 9.1, only requiring a manual build and install of the NIC driver from a tarball on Intel's website. I already checked, there's nothing there for the 2.6 kernel, unfortunately. Post your config file, I can modify it so it will see your RAM. I had problems with MDK's kernel, my usb mouse wouldn't work :( the 2.6.3mm feels faster for my desktop. The only thing I think you'll be missing out on is supermount. There is a patch for that if you think you need it, I can give you instructions on how to add it. Are you using a 2.4 or 2.6 series kernel? Quote Link to comment Share on other sites More sharing options...
jfz Posted March 16, 2004 Author Report Share Posted March 16, 2004 I'm using the 2.6.3-4mdk kernel, or trying to. Here's my lilo.conf: # File generated by DrakX/drakboot # WARNING: do not forget to run lilo after modifying this file boot=/dev/hda map=/boot/map default="linux-enterprise" keytable=/boot/us.klt prompt nowarn timeout=100 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz label="linux" root=/dev/hda1 initrd=/boot/initrd.img append="devfs=mount splash=silent" vga=788 read-only image=/boot/vmlinuz label="linux-nonfb" root=/dev/hda1 initrd=/boot/initrd.img append="devfs=mount" read-only image=/boot/vmlinuz-enterprise label="linux-enterprise" root=/dev/hda1 initrd=/boot/initrd-enterprise.img append="devfs=mount splash=silent" read-only image=/boot/vmlinuz-smp label="linux-smp" root=/dev/hda1 initrd=/boot/initrd-smp.img append="devfs=mount splash=silent" read-only image=/boot/vmlinuz label="failsafe" root=/dev/hda1 initrd=/boot/initrd.img append="failsafe devfs=nomount" read-only other=/dev/fd0 label="floppy" unsafe Quote Link to comment Share on other sites More sharing options...
pmpatrick Posted March 16, 2004 Report Share Posted March 16, 2004 Try adding "acpi=ht" to the append line of your linux entry. Apic has been known to cause a lot of problems with nics. Quote Link to comment Share on other sites More sharing options...
thinkliberty Posted March 16, 2004 Report Share Posted March 16, 2004 I'm using the 2.6.3-4mdk kernel, or trying to. Here's my lilo.conf: # File generated by DrakX/drakboot # WARNING: do not forget to run lilo after modifying this file boot=/dev/hda map=/boot/map default="linux-enterprise" keytable=/boot/us.klt prompt nowarn timeout=100 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz label="linux" root=/dev/hda1 initrd=/boot/initrd.img append="devfs=mount splash=silent" vga=788 read-only image=/boot/vmlinuz label="linux-nonfb" root=/dev/hda1 initrd=/boot/initrd.img append="devfs=mount" read-only image=/boot/vmlinuz-enterprise label="linux-enterprise" root=/dev/hda1 initrd=/boot/initrd-enterprise.img append="devfs=mount splash=silent" read-only image=/boot/vmlinuz-smp label="linux-smp" root=/dev/hda1 initrd=/boot/initrd-smp.img append="devfs=mount splash=silent" read-only image=/boot/vmlinuz label="failsafe" root=/dev/hda1 initrd=/boot/initrd.img append="failsafe devfs=nomount" read-only other=/dev/fd0 label="floppy" unsafe HMmm... I was thinking about the /usr/src/linux/.config file. Sorry for the mixup. Quote Link to comment Share on other sites More sharing options...
jfz Posted March 16, 2004 Author Report Share Posted March 16, 2004 I tried the "acpi=ht" option, which seemed to have no effect at all. I looked for the source .config file with no success, until I realized this last install I didn't bother to select kernel source. I'll try that when I get home tonight, but it's starting to look like that PCI NIC is the best hope. And maybe submitting a bug to Mandrake. Quote Link to comment Share on other sites More sharing options...
jfz Posted March 17, 2004 Author Report Share Posted March 17, 2004 I did some googling around and turned up this bug report: http://www.ussg.iu.edu/hypermail/linux/ker...402.2/1118.html and this one: http://www.ussg.iu.edu/hypermail/linux/ker...403.0/0234.html It looks like some recent patching of the 2.6.3 kernel reintroduced a bug into the e1000 driver that had been removed at one point. Kernel 2.6.4, here I come. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.