![]() |
|
|
Welcome to the { mindfrost82.com } forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
|
|||
|
No such device after kernel upgrade
I upgrade kernel from 2.6.18 to 2.6.26 on debian-40r4a. The network
doesn't work after boot 2.6.26, but it works with 2.6.18 kernel. I've tried to rename the z25_persistent-net.rules file, but no new z25_persistent-net.rules generated after boot with 2.6.26, so the problem remains. Thank you for your time. # /etc/init.d/networking restart Reconfiguring network interfaces...SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device eth0: ERROR while getting interface flags: No such device Failed to bring up eth0 done. # ifconfig -a lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:560 (560.0 b) TX bytes:560 (560.0 b) sit0 Link encap:IPv6-in-IPv4 NOARP MTU 1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) # cat /etc/network/interfaces auto lo iface lo inet loopback allow-hotplug eth0 auto eth0 iface eth0 inet static address 192.168.3.108 netmask 255.255.255.0 gateway 192.168.3.1 # |
|
|||
|
Re: No such device after kernel upgrade
On Aug 21, 2:44*pm, "lovecreatesbea...@gmail.com"
<lovecreatesbea...@gmail.com> wrote: > eth0: ERROR while getting interface flags: No such device > sit0 * *Link encap:IPv6-in-IPv4 My eth0 is missing and there is ``sit0'' which I've not specified in interfaces file. What's this sit0 thing? |
|
|||
|
Re: No such device after kernel upgrade
On 2008-08-21, lovecreatesbea...@gmail.com <lovecreatesbeauty@gmail.com> wrote:
> > > On Aug 21, 2:44*pm, "lovecreatesbea...@gmail.com" ><lovecreatesbea...@gmail.com> wrote: > >> eth0: ERROR while getting interface flags: No such device > >> sit0 * *Link encap:IPv6-in-IPv4 > > My eth0 is missing and there is ``sit0'' which I've not specified in > interfaces file. What's this sit0 thing? sit0 is a tunnel between IPv6 and IPv4. Your eth0 is missing probably because a module is not getting loaded. Look at the output of lsmod under 2.6.18 and the latest kernel. Perhaps the name of the module for your ethernet card has changed. What is the output of lspci? |
|
|||
|
Re: No such device after kernel upgrade
On Aug 21, 9:48 pm, Bill Marcum <marcumb...@bellsouth.net> wrote:
> On 2008-08-21, lovecreatesbea...@gmail.com <lovecreatesbea...@gmail.com> wrote: > > On Aug 21, 2:44 pm, "lovecreatesbea...@gmail.com" > ><lovecreatesbea...@gmail.com> wrote: > > >> eth0: ERROR while getting interface flags: No such device > > >> sit0 Link encap:IPv6-in-IPv4 > > > My eth0 is missing and there is ``sit0'' which I've not specified in > > interfaces file. What's this sit0 thing? > > sit0 is a tunnel between IPv6 and IPv4. Your eth0 is missing probably > because a module is not getting loaded. Thank you. I just issued ``make defconfig'' during the compilation. So, did I not correctly include the component for networking in the new kernel image or in modules for new kernel? I compile and boot with the new compiled kernel on this debian-40r4a smoothly this time. I failed many times on the previous debian-40 distributions. One thing to mention is that I didn't make a initrd image, and I commented the initrd line for the entry to the new kernel. The new entry can boot the new kernel also. #initrd /boot/initrd.img-2.6.18-6-686 > Look at the output of lsmod > under 2.6.18 and the latest kernel. Perhaps the name of the module for > your ethernet card has changed. What is the output of lspci? The lsmod has a empty list on the new kernel. I issued ``make install'' and ``make modules_install'' during the new kernel compilation and install. $ uname -r 2.6.26.2 $ lsmod Module Size Used by $ lspci 00:00.0 Host bridge: ...snipped... 00:01.0 PCI bridge: ... 00:07.0 ISA bridge: ... 00:07.1 IDE interface: ... 00:07.2 USB Controller: ... 00:07.3 Bridge: ... 00:0f.0 VGA compatible controller: ... 00:10.0 SCSI storage controller: ... 00:11.0 PCI bridge: ... 02:00.0 Ethernet controller: ... 02:01.0 Multimedia audio controller: ... 02:02.0 USB Controller: ... $ su -c 'shutdown -r 0' $ uname -r 2.6.18-6-686 $ lsmod Module Size Used by ipv6 226272 12 button 6672 0 ac 5188 0 battery 9636 0 dm_snapshot 15552 0 dm_mirror 19152 0 dm_mod 50232 2 dm_snapshot,dm_mirror loop 15048 0 tsdev 7520 0 snd_ens1371 23616 0 snd_rawmidi 22560 1 snd_ens1371 snd_seq_device 7820 1 snd_rawmidi snd_ac97_codec 83104 1 snd_ens1371 snd_ac97_bus 2400 1 snd_ac97_codec snd_pcm 68676 2 snd_ens1371,snd_ac97_codec snd_timer 20996 1 snd_pcm snd 47012 6 snd_ens1371,snd_rawmidi,snd_seq_device,snd_ac97_co dec,snd_pcm,snd_timer snd_page_alloc 10184 1 snd_pcm es1371 32064 0 gameport 14632 3 snd_ens1371,es1371 soundcore 9248 2 snd,es1371 ac97_codec 17196 1 es1371 psmouse 35016 0 i2c_piix4 8268 0 floppy 53156 0 parport_pc 32132 0 parport 33256 1 parport_pc rtc 12372 0 intel_agp 22204 1 agpgart 29896 1 intel_agp serio_raw 6660 0 i2c_core 19680 1 i2c_piix4 pcspkr 3072 0 shpchp 33024 0 pci_hotplug 28704 1 shpchp evdev 9088 0 ext3 119240 1 jbd 52456 1 ext3 mbcache 8356 1 ext3 sd_mod 19040 3 ide_cd 36064 0 cdrom 32544 1 ide_cd generic 4868 0 [permanent] mptspi 16136 2 mptscsih 21664 1 mptspi mptbase 46176 2 mptspi,mptscsih scsi_transport_spi 22336 1 mptspi scsi_mod 124168 4 sd_mod,mptspi,mptscsih,scsi_transport_spi ehci_hcd 28136 0 pcnet32 30692 0 mii 5344 1 pcnet32 uhci_hcd 21164 0 usbcore 112644 3 ehci_hcd,uhci_hcd piix 9444 0 [permanent] ide_core 110504 3 ide_cd,generic,piix thermal 13608 0 processor 28840 1 thermal fan 4804 0 $ lspci 00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 01) 00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 01) 00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 08) 00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) 00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB 00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08) 00:0f.0 VGA compatible controller: VMware Inc [VMware SVGA II] PCI Display Adapter 00:10.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI- X Fusion-MPT Dual Ultra320 SCSI (rev 01) 00:11.0 PCI bridge: VMware Inc Unknown device 0790 (rev 02) 02:00.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10) 02:01.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 02) 02:02.0 USB Controller: VMware Inc Unknown device 0770 $ |
|
|||
|
Re: No such device after kernel upgrade
Hello,
lovecreatesbea...@gmail.com a écrit : > > I just issued ``make defconfig'' during the compilation. So, did I not > correctly include the component for networking in the new kernel image > or in modules for new kernel? Probably not. In the kernel source root directory, check : $ grep PCNET32 .config > pcnet32 30692 0 Here is the needed module. Check that you have enabled the AMD PCnet32 PCI support, either as a module (CONFIG_PCNET32=m) or built-in (CONFIG_PCNET32=y). > 02:00.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 > [PCnet32 LANCE] (rev 10) |
|
|||
|
Re: No such device after kernel upgrade
On Aug 23, 5:16*am, Pascal Hambourg <boite-a-s...@plouf.fr.eu.org>
wrote: > Hello, > > lovecreatesbea...@gmail.com a écrit : > > > > > I just issued ``make defconfig'' during the compilation. So, did I not > > correctly include the component for networking in the new kernel image > > or in modules for new kernel? > > Probably not. In the kernel source root directory, check : > $ grep PCNET32 .config > > > pcnet32 * * * * * * * *30692 *0 > > Here is the needed module. Check that you have enabled the AMD PCnet32 > PCI support, either as a module (CONFIG_PCNET32=m) or built-in > (CONFIG_PCNET32=y). > > > > > 02:00.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 > > [PCnet32 LANCE] (rev 10) Hi Pascal, thank you. It works now :) $ grep PCNET32 .config # CONFIG_PCNET32 is not set $ make menuconfig scripts/kconfig/mconf arch/x86/Kconfig # # configuration written to .config # *** End of Linux kernel configuration. *** Execute 'make' to build the kernel or try 'make help'. $ grep PCNET32 .config 859:CONFIG_PCNET32=m $ uname -r 2.6.26.2 $ ping debian.org PING debian.org (192.25.206.10) 56(84) bytes of data. 64 bytes from gluck.debian.org (192.25.206.10): icmp_seq=1 ttl=46 time=203 ms 64 bytes from gluck.debian.org (192.25.206.10): icmp_seq=2 ttl=46 time=203 ms ^C --- debian.org ping statistics --- 3 packets transmitted, 2 received, 33% packet loss, time 2004ms rtt min/avg/max/mdev = 203.923/203.933/203.944/0.451 ms $ |
|
|||
|
Re: No such device after kernel upgrade
On Aug 25, 10:07*am, "lovecreatesbea...@gmail.com"
<lovecreatesbea...@gmail.com> wrote: > On Aug 23, 5:16*am, Pascal Hambourg <boite-a-s...@plouf.fr.eu.org> > wrote: > > lovecreatesbea...@gmail.com a écrit : > > > > I just issued ``make defconfig'' during the compilation. So, did I not > > > correctly include the component for networking in the new kernel image > > > or in modules for new kernel? > > > Probably not. In the kernel source root directory, check : > > $ grep PCNET32 .config > > > > pcnet32 * * * * * * * *30692 *0 > > > Here is the needed module. Check that you have enabled the AMD PCnet32 > > PCI support, either as a module (CONFIG_PCNET32=m) or built-in > > (CONFIG_PCNET32=y). > > > > 02:00.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 > > > [PCnet32 LANCE] (rev 10) > > Hi Pascal, thank you. > > It works now :) > > $ grep PCNET32 .config > # CONFIG_PCNET32 is not set > $ make menuconfig > scripts/kconfig/mconf arch/x86/Kconfig > # > # configuration written to .config > # > > *** End of Linux kernel configuration. > *** Execute 'make' to build the kernel or try 'make help'. > > $ grep PCNET32 .config > 859:CONFIG_PCNET32=m > > $ uname -r > 2.6.26.2 > $ ping debian.org > PING debian.org (192.25.206.10) 56(84) bytes of data. > 64 bytes from gluck.debian.org (192.25.206.10): icmp_seq=1 ttl=46 > time=203 ms > 64 bytes from gluck.debian.org (192.25.206.10): icmp_seq=2 ttl=46 > time=203 ms > ^C > --- debian.org ping statistics --- > 3 packets transmitted, 2 received, 33% packet loss, time 2004ms > rtt min/avg/max/mdev = 203.923/203.933/203.944/0.451 ms > $ The hello module works also. I issue the insmod command at putty window, a ssh client side. I'm not in the xwindow command line, but the printk message doesn't show on putty window but on the VMware window where the debian linux is running. $ cat hello.c #include <linux/init.h> #include <linux/module.h> MODULE_LICENSE("Dual BSD/GPL"); static int hello_init(void) { printk(KERN_ALERT "Hello, world\n"); return 0; } static void hello_exit(void) { printk(KERN_ALERT "Goodbye, cruel world\n"); } module_init(hello_init); module_exit(hello_exit); $ $ cat Makefile # If KERNELRELEASE is defined, we've been invoked from the # kernel build system and can use its language. ifneq ($(KERNELRELEASE),) obj-m := hello.o # Otherwise we were called directly from the command # line; invoke the kernel build system. else KERNELDIR ?= /lib/modules/$(shell uname -r)/build PWD := $(shell pwd) default: $(MAKE) -C $(KERNELDIR) M=$(PWD) modules endif $ su -c ' insmod ./hello.ko' $ |
![]() |
|
| Thread Tools | Search this Thread |
| Display Modes | |
|
|