Your /etc/kernel-img.conf needs to be updated
Hello ! I'm triying to compile the kernel 2.6.19. The compilation happens good, but when I install the .deb on Debian testing, I get an out error state 1 : Préparation du remplacement de linux-image-2.6.19.070428 2.6.19.suspend2 (en utilisant linux-image-2.6.19.070428_2.6.19.suspend2_i386.deb) ... Ok, Aborting dpkg : erreur de traitement de linux-image-2.6.19.070428_2.6.19.suspend2_i386.deb (--install) : le sous-processus pre-installation script a retourné une erreur de sortie d'état 1 Running postrm hook script /sbin/update-grub. Your /etc/kernel-img.conf needs to be updated. Read grub's NEWS.Debian[1] file and follow its instructions. update-grub works normally, but don't change anything. Where can I find informations about /etc/kernel-img.conf and grub's NEWS.Debian[1] ? I don't understand what I must do. Thanks for help, Thibaud. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Your /etc/kernel-img.conf needs to be updated
Hello ! I'm triying to compile the kernel 2.6.19. The compilation happens good, but when I install the .deb on Debian testing, I get an out error state 1 : Préparation du remplacement de linux-image-2.6.19.070428 2.6.19.suspend2 (en utilisant linux-image-2.6.19.070428_2.6.19.suspend2_i386.deb) ... Ok, Aborting dpkg : erreur de traitement de linux-image-2.6.19.070428_2.6.19.suspend2_i386.deb (--install) : le sous-processus pre-installation script a retourné une erreur de sortie d'état 1 Running postrm hook script /sbin/update-grub. Your /etc/kernel-img.conf needs to be updated. Read grub's NEWS.Debian[1] file and follow its instructions. update-grub works normally, but don't change anything. Where can I find informations about /etc/kernel-img.conf and grub's NEWS.Debian[1] ? I don't understand what I must do. Thanks for help, Thibaud. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
error in compilation kernel 2.6.19 - internal compiler error
Hello ! I'm triyng to compile the kernel 2.6.19 on Debian Testing 4.0 Unfortunately, I can't success. This is my error message : CC [M] drivers/scsi/lpfc/lpfc_sli.o In file included from drivers/scsi/lpfc/lpfc_sli.c:23: include/linux/pci.h:251: internal compiler error: in build_int_cst_wide, at tree.c:803 Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html> for instructions. For Debian GNU/Linux specific bug reporting instructions, see . The bug is not reproducible, so it is likely a hardware or OS problem. make[4]: *** [drivers/scsi/lpfc/lpfc_sli.o] Erreur 1 make[3]: *** [drivers/scsi/lpfc] Erreur 2 make[2]: *** [drivers/scsi] Erreur 2 make[1]: *** [drivers] Erreur 2 make[1]: quittant le répertoire « /home/hulin/src_hitachi/linux-2.6.19 » make: *** [debian/stamp-build-kernel] Erreur 2 Thanks for help, Thibaud. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
error in compilation kernel 2.6.19 - internal compiler error
Hello ! I'm triyng to compile the kernel 2.6.19 on Debian Testing 4.0 Unfortunately, I can't success. This is my error message : CC [M] drivers/scsi/lpfc/lpfc_sli.o In file included from drivers/scsi/lpfc/lpfc_sli.c:23: include/linux/pci.h:251: internal compiler error: in build_int_cst_wide, at tree.c:803 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. For Debian GNU/Linux specific bug reporting instructions, see URL:file:///usr/share/doc/gcc-4.1/README.Bugs. The bug is not reproducible, so it is likely a hardware or OS problem. make[4]: *** [drivers/scsi/lpfc/lpfc_sli.o] Erreur 1 make[3]: *** [drivers/scsi/lpfc] Erreur 2 make[2]: *** [drivers/scsi] Erreur 2 make[1]: *** [drivers] Erreur 2 make[1]: quittant le répertoire « /home/hulin/src_hitachi/linux-2.6.19 » make: *** [debian/stamp-build-kernel] Erreur 2 Thanks for help, Thibaud. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: I can't compile with success because ueagle-atm.ko undefined
Sorry, I tried the kernel 2.6.19 and patched it with suspend2 for 2.6.19 For 2.6.20, suspend2 is on development, so I can't use it Adrian Bunk a écrit : On Sun, Mar 18, 2007 at 12:07:51AM +0100, Thibaud Hulin wrote: Hi, I can't compile with success my kernel, i've got this error message : Building modules, stage 2. MODPOST 1750 modules WARNING: Can't handle masks in drivers/ide/pci/atiixp:05 WARNING: "try_to_freeze" [drivers/usb/atm/ueagle-atm.ko] undefined! make[2]: *** [__modpost] Erreur 1 make[1]: *** [modules] Erreur 2 You didn't mention the kernel version, but this is a bug in kernels 2.6.20 and 2.6.20.1 fixed in kernel 2.6.20.2 (and 2.6.20.3). When I uncheck this module, the compiled kernel works, but there are many problems and the kernel fails after minutes. ... That sounds like an unrelated problem that should be reported. Thanks for help, Thibaud. cu Adrian - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: I can't compile with success because ueagle-atm.ko undefined
Sorry, I tried the kernel 2.6.19 and patched it with suspend2 for 2.6.19 For 2.6.20, suspend2 is on development, so I can't use it Adrian Bunk a écrit : On Sun, Mar 18, 2007 at 12:07:51AM +0100, Thibaud Hulin wrote: Hi, I can't compile with success my kernel, i've got this error message : Building modules, stage 2. MODPOST 1750 modules WARNING: Can't handle masks in drivers/ide/pci/atiixp:05 WARNING: try_to_freeze [drivers/usb/atm/ueagle-atm.ko] undefined! make[2]: *** [__modpost] Erreur 1 make[1]: *** [modules] Erreur 2 You didn't mention the kernel version, but this is a bug in kernels 2.6.20 and 2.6.20.1 fixed in kernel 2.6.20.2 (and 2.6.20.3). When I uncheck this module, the compiled kernel works, but there are many problems and the kernel fails after minutes. ... That sounds like an unrelated problem that should be reported. Thanks for help, Thibaud. cu Adrian - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
I can't compile with success because ueagle-atm.ko undefined
Hi, I can't compile with success my kernel, i've got this error message : Building modules, stage 2. MODPOST 1750 modules WARNING: Can't handle masks in drivers/ide/pci/atiixp:05 WARNING: "try_to_freeze" [drivers/usb/atm/ueagle-atm.ko] undefined! make[2]: *** [__modpost] Erreur 1 make[1]: *** [modules] Erreur 2 When I uncheck this module, the compiled kernel works, but there are many problems and the kernel fails after minutes. I use a Nvdia Geforce graphic card. Thanks for help, Thibaud. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
I can't compile with success because ueagle-atm.ko undefined
Hi, I can't compile with success my kernel, i've got this error message : Building modules, stage 2. MODPOST 1750 modules WARNING: Can't handle masks in drivers/ide/pci/atiixp:05 WARNING: try_to_freeze [drivers/usb/atm/ueagle-atm.ko] undefined! make[2]: *** [__modpost] Erreur 1 make[1]: *** [modules] Erreur 2 When I uncheck this module, the compiled kernel works, but there are many problems and the kernel fails after minutes. I use a Nvdia Geforce graphic card. Thanks for help, Thibaud. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
no swap!
Hi ! After compiling the kernel, I discover that my computer don't use the swap. So, I try a cat .config |grep SW, and I got : CONFIG_SWAP=y # CONFIG_X86_VISWS is not set CONFIG_X86_BSWAP=y CONFIG_SUSPEND2_SWAP=y CONFIG_SUSPEND2_REPLACE_SWSUSP=y # CONFIG_AGP_SWORKS is not set CONFIG_USB_AUERSWALD=m This is my fstab : # /etc/fstab: static file system information. # # proc/proc procdefaults0 0 # /dev/hda1 -- converted during upgrade to edgy UUID=c0808eb9-790a-4a20-a3a2-26a4204d0fb2 / ext3 defaults,errors=remount-ro 0 1 # /dev/hda5 -- converted during upgrade to edgy UUID=dfcca30e-3b78-4110-b578-9b8835ecf062 none swap sw 0 0 #/dev/hda5 noneswapsw 0 0 /dev/hdc/media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/fd0/media/floppy0 autorw,user,noauto 0 0 Is it a problem of LVM or RAID ? I don't understand that very well... Thanks a lot, Thibaud. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
no swap!
Hi ! After compiling the kernel, I discover that my computer don't use the swap. So, I try a cat .config |grep SW, and I got : CONFIG_SWAP=y # CONFIG_X86_VISWS is not set CONFIG_X86_BSWAP=y CONFIG_SUSPEND2_SWAP=y CONFIG_SUSPEND2_REPLACE_SWSUSP=y # CONFIG_AGP_SWORKS is not set CONFIG_USB_AUERSWALD=m This is my fstab : # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 # /dev/hda1 -- converted during upgrade to edgy UUID=c0808eb9-790a-4a20-a3a2-26a4204d0fb2 / ext3 defaults,errors=remount-ro 0 1 # /dev/hda5 -- converted during upgrade to edgy UUID=dfcca30e-3b78-4110-b578-9b8835ecf062 none swap sw 0 0 #/dev/hda5 noneswapsw 0 0 /dev/hdc/media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/fd0/media/floppy0 autorw,user,noauto 0 0 Is it a problem of LVM or RAID ? I don't understand that very well... Thanks a lot, Thibaud. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Problem with USB ports and a dongle
Hi ! I'm trying to use a dongle for ndiswrapper, but it fails because a problem of usb. Note that the problem appear when ndiswrapper is fully uninstalled (and others packages as ndiswrapper-utils, with modprobe -r, etc...). So ; when I get on the first time the dongle, a lsusb give : Bus 001 Device 002: ID 0457:0163 Silicon Integrated Systems Corps. Bus 001 Device 001: ID : But, a few seconds later, the dongle is not recognize with sometimes an error -71. Then, lsusb forget the driver and get : Bus 001 Device 001: ID : How can I configure the kernel to have the good configuration ? I tried different ways, but it fails. I already reinstalled the bios. See at below for the result of these commands (when I try the dongle) : "lspci -v |grep HCI" "cat /var/log/messages" (the end) "dmesg |grep usb" Thanks for help, Thibaud. NB1 : thanks to Alex Davis and Oliver Neukum for advices and recommendations about check if the problem was from ndiswrapper or not. I hope there is not a special list for kernel USB ; if yes : apologizes, I couldn't find it. NB2 : I'm not sure if this message is too long or not. I included the mention "End of the message" at last. --- My hardware : Computer : dell pentium mmx 233 mst ram : 128 Mo dongle : thomson WLG-1500A - chipset Sis163u Kernel 2.6.19 Ubuntu Edgy "lspci -v |grep HCI" : 00:01.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) (prog-if 00 [UHCI]) - "cat /var/log/messages" Feb 11 21:41:08 localhost kernel: [ 6049.104000] usb 1-1: new full speed USB device using uhci_hcd and address 2 Feb 11 21:41:08 localhost kernel: [ 6049.252000] usb 1-1: configuration #1 chosen from 1 choice Feb 11 21:41:12 localhost kernel: [ 6053.592000] usb 1-1: USB disconnect, address 2 Feb 11 21:41:12 localhost kernel: [ 6053.712000] usb 1-1: new full speed USB device using uhci_hcd and address 3 Feb 11 21:41:13 localhost kernel: [ 6053.86] usb 1-1: configuration #1 chosen from 1 choice Feb 11 21:41:15 localhost kernel: [ 6056.592000] usb 1-1: USB disconnect, address 3 Feb 11 21:41:15 localhost kernel: [ 6056.712000] usb 1-1: new full speed USB device using uhci_hcd and address 4 Feb 11 21:41:16 localhost kernel: [ 6056.856000] usb 1-1: configuration #1 chosen from 1 choice Feb 11 21:41:19 localhost kernel: [ 6059.70] usb 1-1: USB disconnect, address 4 Feb 11 21:41:19 localhost kernel: [ 6059.812000] usb 1-1: new full speed USB device using uhci_hcd and address 5 Feb 11 21:41:20 localhost kernel: [ 6059.96] usb 1-1: configuration #1 chosen from 1 choice Feb 11 21:41:20 localhost kernel: [ 6060.204000] usb 1-1: USB disconnect, address 5 Feb 11 21:41:20 localhost kernel: [ 6060.316000] usb 1-1: new full speed USB device using uhci_hcd and address 6 Feb 11 21:41:20 localhost kernel: [ 6060.464000] usb 1-1: configuration #1 chosen from 1 choice Feb 11 21:41:21 localhost kernel: [ 6062.22] usb 1-1: USB disconnect, address 6 Feb 11 21:41:21 localhost kernel: [ 6062.332000] usb 1-1: new full speed USB device using uhci_hcd and address 7 Feb 11 21:41:21 localhost kernel: [ 6062.48] usb 1-1: configuration #1 chosen from 1 choice Feb 11 21:41:22 localhost kernel: [ 6062.724000] usb 1-1: USB disconnect, address 7 Feb 11 21:41:22 localhost kernel: [ 6062.836000] usb 1-1: new full speed USB device using uhci_hcd and address 8 Feb 11 21:41:22 localhost kernel: [ 6062.984000] usb 1-1: configuration #1 chosen from 1 choice Feb 11 21:41:22 localhost kernel: [ 6063.48] usb 1-1: USB disconnect, address 8 Feb 11 21:41:22 localhost kernel: [ 6063.592000] usb 1-1: new full speed USB device using uhci_hcd and address 9 Feb 11 21:41:24 localhost kernel: [ 6064.452000] usb 1-1: new full speed USB device using uhci_hcd and address 10 Feb 11 21:41:24 localhost kernel: [ 6065.012000] usb 1-1: new full speed USB device using uhci_hcd and address 11 Feb 11 21:41:24 localhost kernel: [ 6065.532000] usb 1-1: new full speed USB device using uhci_hcd and address 12 - dmesg |grep usb : [ 17.78] usbcore: registered new interface driver usbfs [ 17.784000] usbcore: registered new interface driver hub [ 17.788000] usbcore: registered new device driver usb [ 17.808000] usb usb1: configuration #1 chosen from 1 choice [ 69.416000] usbcore: registered new interface driver ndiswrapper [ 5916.30] usbcore: deregistering interface driver ndiswrapper [ 6049.104000] usb 1-1: new full speed USB device using uhci_hcd and address 2 [ 6049.252000] usb 1-1: configuration #1 chosen from 1 choice [ 6053.592000] usb 1-1: USB disconnect, address 2 [ 6053.712000] usb 1-1: new full speed USB device using uhci_hcd and address 3 [ 6053.86] usb 1-1: configuration #1 chosen from 1 choice [ 6056.592000] usb 1-1: USB disconnect, address 3 [ 6056.712000] usb 1-1: new full speed USB device using uhci_hcd and address 4 [ 6056.856000] usb 1-1: configuration #1 chosen from 1 choice [
Problem with USB ports and a dongle
Hi ! I'm trying to use a dongle for ndiswrapper, but it fails because a problem of usb. Note that the problem appear when ndiswrapper is fully uninstalled (and others packages as ndiswrapper-utils, with modprobe -r, etc...). So ; when I get on the first time the dongle, a lsusb give : Bus 001 Device 002: ID 0457:0163 Silicon Integrated Systems Corps. Bus 001 Device 001: ID : But, a few seconds later, the dongle is not recognize with sometimes an error -71. Then, lsusb forget the driver and get : Bus 001 Device 001: ID : How can I configure the kernel to have the good configuration ? I tried different ways, but it fails. I already reinstalled the bios. See at below for the result of these commands (when I try the dongle) : lspci -v |grep HCI cat /var/log/messages (the end) dmesg |grep usb Thanks for help, Thibaud. NB1 : thanks to Alex Davis and Oliver Neukum for advices and recommendations about check if the problem was from ndiswrapper or not. I hope there is not a special list for kernel USB ; if yes : apologizes, I couldn't find it. NB2 : I'm not sure if this message is too long or not. I included the mention End of the message at last. --- My hardware : Computer : dell pentium mmx 233 mst ram : 128 Mo dongle : thomson WLG-1500A - chipset Sis163u Kernel 2.6.19 Ubuntu Edgy lspci -v |grep HCI : 00:01.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) (prog-if 00 [UHCI]) - cat /var/log/messages Feb 11 21:41:08 localhost kernel: [ 6049.104000] usb 1-1: new full speed USB device using uhci_hcd and address 2 Feb 11 21:41:08 localhost kernel: [ 6049.252000] usb 1-1: configuration #1 chosen from 1 choice Feb 11 21:41:12 localhost kernel: [ 6053.592000] usb 1-1: USB disconnect, address 2 Feb 11 21:41:12 localhost kernel: [ 6053.712000] usb 1-1: new full speed USB device using uhci_hcd and address 3 Feb 11 21:41:13 localhost kernel: [ 6053.86] usb 1-1: configuration #1 chosen from 1 choice Feb 11 21:41:15 localhost kernel: [ 6056.592000] usb 1-1: USB disconnect, address 3 Feb 11 21:41:15 localhost kernel: [ 6056.712000] usb 1-1: new full speed USB device using uhci_hcd and address 4 Feb 11 21:41:16 localhost kernel: [ 6056.856000] usb 1-1: configuration #1 chosen from 1 choice Feb 11 21:41:19 localhost kernel: [ 6059.70] usb 1-1: USB disconnect, address 4 Feb 11 21:41:19 localhost kernel: [ 6059.812000] usb 1-1: new full speed USB device using uhci_hcd and address 5 Feb 11 21:41:20 localhost kernel: [ 6059.96] usb 1-1: configuration #1 chosen from 1 choice Feb 11 21:41:20 localhost kernel: [ 6060.204000] usb 1-1: USB disconnect, address 5 Feb 11 21:41:20 localhost kernel: [ 6060.316000] usb 1-1: new full speed USB device using uhci_hcd and address 6 Feb 11 21:41:20 localhost kernel: [ 6060.464000] usb 1-1: configuration #1 chosen from 1 choice Feb 11 21:41:21 localhost kernel: [ 6062.22] usb 1-1: USB disconnect, address 6 Feb 11 21:41:21 localhost kernel: [ 6062.332000] usb 1-1: new full speed USB device using uhci_hcd and address 7 Feb 11 21:41:21 localhost kernel: [ 6062.48] usb 1-1: configuration #1 chosen from 1 choice Feb 11 21:41:22 localhost kernel: [ 6062.724000] usb 1-1: USB disconnect, address 7 Feb 11 21:41:22 localhost kernel: [ 6062.836000] usb 1-1: new full speed USB device using uhci_hcd and address 8 Feb 11 21:41:22 localhost kernel: [ 6062.984000] usb 1-1: configuration #1 chosen from 1 choice Feb 11 21:41:22 localhost kernel: [ 6063.48] usb 1-1: USB disconnect, address 8 Feb 11 21:41:22 localhost kernel: [ 6063.592000] usb 1-1: new full speed USB device using uhci_hcd and address 9 Feb 11 21:41:24 localhost kernel: [ 6064.452000] usb 1-1: new full speed USB device using uhci_hcd and address 10 Feb 11 21:41:24 localhost kernel: [ 6065.012000] usb 1-1: new full speed USB device using uhci_hcd and address 11 Feb 11 21:41:24 localhost kernel: [ 6065.532000] usb 1-1: new full speed USB device using uhci_hcd and address 12 - dmesg |grep usb : [ 17.78] usbcore: registered new interface driver usbfs [ 17.784000] usbcore: registered new interface driver hub [ 17.788000] usbcore: registered new device driver usb [ 17.808000] usb usb1: configuration #1 chosen from 1 choice [ 69.416000] usbcore: registered new interface driver ndiswrapper [ 5916.30] usbcore: deregistering interface driver ndiswrapper [ 6049.104000] usb 1-1: new full speed USB device using uhci_hcd and address 2 [ 6049.252000] usb 1-1: configuration #1 chosen from 1 choice [ 6053.592000] usb 1-1: USB disconnect, address 2 [ 6053.712000] usb 1-1: new full speed USB device using uhci_hcd and address 3 [ 6053.86] usb 1-1: configuration #1 chosen from 1 choice [ 6056.592000] usb 1-1: USB disconnect, address 3 [ 6056.712000] usb 1-1: new full speed USB device using uhci_hcd and address 4 [ 6056.856000] usb 1-1: configuration #1 chosen from 1 choice [ 6059.70]
Re: Problem of USB - error 71 : how configure kernel to dongle with chipset
Thanks. In effect, I already post this question in the ndiswrapper list. So, they told me that was a problem of USB and of kernel. Then, I'm looking for configuration of the kernel, because I compiled the 2.6.19, but I no more success. Actually, lsusb recognize, then don't recognize the machine a few seconds after. Ndiswrapper can be installed or not, that change nothing. This is the answer from which I was able to touch with you : --- Thibaud Hulin <[EMAIL PROTECTED]> wrote: > > So, 30 seconds later, the dongle is not recognize. lsusb give : > > Bus 001 Device 001: ID : > > So, I can't use my dongle. If 'lsusb' doesn't see the card, it may indicate problem with your USB host (either hardware, or host driver or both). You may want to try different kernels. Until that part works right, ndiswrapper won't be able to initialize the card. Giri Alex Davis a écrit : As you are using ndiswrapper, you won't much if any help from the kernel developers. ndiswrapper taints the kernel as it links closed-source drivers into kernel space. I strongly advise you to post this question on the ndiswrapper mailing list. Good luck. -Alex - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Problem of USB - error 71 : how configure kernel to dongle with chipset SIS 163u
Hi ! I'm trying to use a dongle with ndiswrapper, but it fails because a problem of usb. Indeed, when I put on first the dongle, a lsusb give : Bus 001 Device 002: ID 0457:0163 Silicon Integrated Systems Corps. Bus 001 Device 001: ID : But, 10 to 30 seconds later, the dongle is not recognize with an error -71. lsusb give : Bus 001 Device 001: ID : How can I configure the kernel to have the good configuration ? I tried different ways, but it fails. Thanks for help, Thibaud. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[no subject]
auth 07267a18 subscribe linux-kernel \ [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[no subject]
auth 07267a18 subscribe linux-kernel \ [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Problem of USB - error 71 : how configure kernel to dongle with chipset SIS 163u
Hi ! I'm trying to use a dongle with ndiswrapper, but it fails because a problem of usb. Indeed, when I put on first the dongle, a lsusb give : Bus 001 Device 002: ID 0457:0163 Silicon Integrated Systems Corps. Bus 001 Device 001: ID : But, 10 to 30 seconds later, the dongle is not recognize with an error -71. lsusb give : Bus 001 Device 001: ID : How can I configure the kernel to have the good configuration ? I tried different ways, but it fails. Thanks for help, Thibaud. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Problem of USB - error 71 : how configure kernel to dongle with chipset
Thanks. In effect, I already post this question in the ndiswrapper list. So, they told me that was a problem of USB and of kernel. Then, I'm looking for configuration of the kernel, because I compiled the 2.6.19, but I no more success. Actually, lsusb recognize, then don't recognize the machine a few seconds after. Ndiswrapper can be installed or not, that change nothing. This is the answer from which I was able to touch with you : --- Thibaud Hulin [EMAIL PROTECTED] wrote: So, 30 seconds later, the dongle is not recognize. lsusb give : Bus 001 Device 001: ID : So, I can't use my dongle. If 'lsusb' doesn't see the card, it may indicate problem with your USB host (either hardware, or host driver or both). You may want to try different kernels. Until that part works right, ndiswrapper won't be able to initialize the card. Giri Alex Davis a écrit : As you are using ndiswrapper, you won't much if any help from the kernel developers. ndiswrapper taints the kernel as it links closed-source drivers into kernel space. I strongly advise you to post this question on the ndiswrapper mailing list. Good luck. -Alex - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Re: error 2 after a compile
Thanks. Before seeing your message, I erase the line with this module in the .config, and if worked. However, I must recompile it, because I forgot someting for suspend2. I'd like install your patch. But how can I do it ? Have you join a patch sched.h ? Randy Dunlap a écrit : On Tue, 06 Feb 2007 21:00:54 +0100 Thibaud Hulin wrote: Hello ! I'm trying to compile a kernel from 2.6.17-10 to 2.6.19 with suspend2. After this command : make-kpkg --append-to-version=swsusp2.070206 kernel_image --initrd kernel_headers --revision=2.6.1 I obtain : Building modules, stage 2. MODPOST 1479 modules WARNING: Can't handle masks in drivers/ide/pci/atiixp:05 WARNING: "try_to_freeze" [drivers/usb/atm/ueagle-atm.ko] undefined! make[2]: *** [__modpost] Erreur 1 make[1]: *** [modules] Erreur 2 make[1]: quittant le répertoire « /home/hulin/src/linux-2.6.19 » make: *** [debian/stamp-build-kernel] Erreur 2 I don't understand the error ? The driver is missing #include . Please try the patch below and report back on it. --- From: Randy Dunlap <[EMAIL PROTECTED]> Driver needs sched.h for try_to_freeze(). Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]> --- drivers/usb/atm/ueagle-atm.c |1 + 1 file changed, 1 insertion(+) --- linux-2619-pv.orig/drivers/usb/atm/ueagle-atm.c +++ linux-2619-pv/drivers/usb/atm/ueagle-atm.c @@ -61,6 +61,7 @@ #include #include #include +#include #include #include #include - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Re: error 2 after a compile
Thanks. Before seeing your message, I erase the line with this module in the .config, and if worked. However, I must recompile it, because I forgot someting for suspend2. I'd like install your patch. But how can I do it ? Have you join a patch sched.h ? Randy Dunlap a écrit : On Tue, 06 Feb 2007 21:00:54 +0100 Thibaud Hulin wrote: Hello ! I'm trying to compile a kernel from 2.6.17-10 to 2.6.19 with suspend2. After this command : make-kpkg --append-to-version=swsusp2.070206 kernel_image --initrd kernel_headers --revision=2.6.1 I obtain : Building modules, stage 2. MODPOST 1479 modules WARNING: Can't handle masks in drivers/ide/pci/atiixp:05 WARNING: try_to_freeze [drivers/usb/atm/ueagle-atm.ko] undefined! make[2]: *** [__modpost] Erreur 1 make[1]: *** [modules] Erreur 2 make[1]: quittant le répertoire « /home/hulin/src/linux-2.6.19 » make: *** [debian/stamp-build-kernel] Erreur 2 I don't understand the error ? The driver is missing #include linux/sched.h. Please try the patch below and report back on it. --- From: Randy Dunlap [EMAIL PROTECTED] Driver needs sched.h for try_to_freeze(). Signed-off-by: Randy Dunlap [EMAIL PROTECTED] --- drivers/usb/atm/ueagle-atm.c |1 + 1 file changed, 1 insertion(+) --- linux-2619-pv.orig/drivers/usb/atm/ueagle-atm.c +++ linux-2619-pv/drivers/usb/atm/ueagle-atm.c @@ -61,6 +61,7 @@ #include linux/usb.h #include linux/firmware.h #include linux/ctype.h +#include linux/sched.h #include linux/kthread.h #include linux/version.h #include linux/mutex.h - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
error 2 after a compile
Hello ! I'm trying to compile a kernel from 2.6.17-10 to 2.6.19 with suspend2. After this command : make-kpkg --append-to-version=swsusp2.070206 kernel_image --initrd kernel_headers --revision=2.6.1 I obtain : Building modules, stage 2. MODPOST 1479 modules WARNING: Can't handle masks in drivers/ide/pci/atiixp:05 WARNING: "try_to_freeze" [drivers/usb/atm/ueagle-atm.ko] undefined! make[2]: *** [__modpost] Erreur 1 make[1]: *** [modules] Erreur 2 make[1]: quittant le répertoire « /home/hulin/src/linux-2.6.19 » make: *** [debian/stamp-build-kernel] Erreur 2 I don't understand the error ? Thanks for help, Thibaud. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
error 2 after a compile
Hello ! I'm trying to compile a kernel from 2.6.17-10 to 2.6.19 with suspend2. After this command : make-kpkg --append-to-version=swsusp2.070206 kernel_image --initrd kernel_headers --revision=2.6.1 I obtain : Building modules, stage 2. MODPOST 1479 modules WARNING: Can't handle masks in drivers/ide/pci/atiixp:05 WARNING: try_to_freeze [drivers/usb/atm/ueagle-atm.ko] undefined! make[2]: *** [__modpost] Erreur 1 make[1]: *** [modules] Erreur 2 make[1]: quittant le répertoire « /home/hulin/src/linux-2.6.19 » make: *** [debian/stamp-build-kernel] Erreur 2 I don't understand the error ? Thanks for help, Thibaud. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
