Re: Re: I cannot shutdown/poweroff after a HW upgrade - kernel gets stuck.
On Sun, Mar 26, 2023 at 11:33 PM Ram Ramesh wrote: > Hi Ramesh, > > this might help. The bug is fixed with kernel 6.0.2-1 > > https://groups.google.com/g/linux.debian.bugs.dist/c/p-sgJiTR00A?pli=1 > > All the best to you > Eike > > Elke, > > Thanks. v6.1 is available on bullseye-backports. I installed it and the > trouble is gone now. > > BTW, does non-free firmware tied to kernel version? > > I use firmware-realtek to deal with my dragon 2.5G NIC that seems to be > unstable without realtek-firmware. I want to make sure I use the correct > version (for linux v6.1), if there is such a requirement. > You will have to add and enable the non-free-firmware repo. deb http://deb.debian.org/debian/ bookworm main non-free contrib non-free-firmware Binary Blobs are not directly tied to a kernel version. Since the kernel became modular drivers and firmware are able to be developed and released on their own schedule. > Regards > Ramesh > -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
Re: Re: I cannot shutdown/poweroff after a HW upgrade - kernel gets stuck.
Hi Ramesh, this might help. The bug is fixed with kernel 6.0.2-1 https://groups.google.com/g/linux.debian.bugs.dist/c/p-sgJiTR00A?pli=1 All the best to you Eike Elke, Thanks. v6.1 is available on bullseye-backports. I installed it and the trouble is gone now. BTW, does non-free firmware tied to kernel version? I use firmware-realtek to deal with my dragon 2.5G NIC that seems to be unstable without realtek-firmware. I want to make sure I use the correct version (for linux v6.1), if there is such a requirement. Regards Ramesh
Re: I cannot shutdown/poweroff after a HW upgrade - kernel gets stuck.
On Sonntag, 26. März 2023 18:08:15 -04 Ram Ramesh wrote: > I wanted to upgrade my server from 10 year old HW to something newer. > THis server runs debian bullseye with v5.19 kernel from backports. [snip] > > The only trouble I have is that it refuses to > reboot/shutdown/poweroff. It seem to go through all steps and reach > the end but seem to get stuck in this endless cycle complaining about > some blkdev issue. Here are the last lines printed on the console > that shows the cycle > > [OK] Reached target Power-off > [67652.NN] block device autoloading is deprecated and will be > removed > > [67667.NN] blkdev_get_no_open: 119 callbacks suppressed > different and number of callbacks being slightly different> > > I assume by "[OK]..." line that we are really at the end of shut down > process. When I turn off physically using power switch and reboot, I > do not get any fsck error messages. So, I assume that filesystems are > safe and kernel is somehow lost in some thread and cannot end the > reboot process. > > Any ideas what I can do? > > Regards > Ramesh Hi Ramesh, this might help. The bug is fixed with kernel 6.0.2-1 https://groups.google.com/g/linux.debian.bugs.dist/c/p-sgJiTR00A?pli=1[1] All the best to you Eike -- Eike Lantzsch KY4PZ / ZP5CGE [1] https://groups.google.com/g/linux.debian.bugs.dist/c/p-sgJiTR00A?pli=1
I cannot shutdown/poweroff after a HW upgrade - kernel gets stuck.
I wanted to upgrade my server from 10 year old HW to something newer. THis server runs debian bullseye with v5.19 kernel from backports. Here is the list of items I got in the upgraded system 1. Intel z690 mother board (asrock steel legend) 2. Core i3-13100 cpu 3. Super Flower 650W PSU, 4. G.SKILL DDR4 RAM 5. 2x SK hynix P31 nvme SSD 1TB each. I reused these from old build 1. Geforce GT 630 video card 2. SAS9211i HBA card for extra SATA ports 3. All my large spinning drives that contained data in RAID6 and RAID1 I made a raid1 on mvme ssd and created 3 partitions. In one I installed debian testing (bookworm with v6.1 kernel) and in another, I image copied the old installation I had before the HW upgrade. Debian bookworm runs fine and reboots/shutsdown as expected. My old system copied over also works fine for most part. It boots and runs everything that I care about. All my RAID disks are working. No issue as long as it runs. The only trouble I have is that it refuses to reboot/shutdown/poweroff. It seem to go through all steps and reach the end but seem to get stuck in this endless cycle complaining about some blkdev issue. Here are the last lines printed on the console that shows the cycle [OK] Reached target Power-off [67652.NN] block device autoloading is deprecated and will be removed [67667.NN] blkdev_get_no_open: 119 callbacks suppressed I assume by "[OK]..." line that we are really at the end of shut down process. When I turn off physically using power switch and reboot, I do not get any fsck error messages. So, I assume that filesystems are safe and kernel is somehow lost in some thread and cannot end the reboot process. Any ideas what I can do? Regards Ramesh
Re: Sid, upgrade kernel casse mon Wifi
Bonsoir Jérôme, jerome moliere, on 2021-02-10 18:30:33 +0100: > Bonjour > d'apres le support System76 la these de la panne materielle semble la plus > probable. Ce ne serait pas surprenant. > Je vais donc commander une carte et tester > Vous avez des references a conseiller en la matiere, compatibles si > possible Linux libre ? Il y a eu une grosse discussion sur debian-devel le mois dernier après que quelqu'un a signalé que le disque d'installation réseau sans firmware non libres mis en avant en page d'accueil de debian.org était un choix malheureux[1]. Attention, il y a beaucoup de lecture en Anglais, si vous vous intéressez au fil de discussion complet. [1] https://lists.debian.org/debian-devel/2021/01/msg00151.html Je n'ai pas retrouvé le message en question, mais il me semble qu'une des difficultés pour avoir des micrologiciels libres dans le domaine des puces de communication sans fil est la réglementation, qui interdit les fabricant de fournir du matériel qui serait capable d'opérer en dehors des bandes autorisées. Il y avait également un ou plusieurs message concernant quelques références pour des puces wifi libres, mais elle ne semblaient ni être les plus performantes, ni être les plus simples à se procurer. > chipsets ath9k ou ath10k . D'autres ? > Quelles references eventuellement ... Dans la gamme Qualcomm Atheros, les chipsets supportés comprennent ceux listés dans la description du paquet firmware-atheros. Ils ne sont malheureusement pas Libres, mais ils sont disponibles via le dépôt non-free. La liste est assez longue, mais peut être obtenue avec la commande : $ apt show firmware-atheros Il y a également des puces Broadcom, Marvell, Intel (mais j'imaginge que vous n'avez pas envie de retenter l'expérience iwlwifi que avez eu), etc. Pour une liste, probablement non exhaustive, des paquets de micrologiciels supportés par non-free pour fournir du wifi, vous pouvez voir le résultat de la commande suivante, qui sur Sid avec non-free me donne : $ apt-cache search ^firmware- | grep -Ei 'wireless|wifi' firmware-ath9k-htc - firmware for AR7010 and AR9271 USB wireless adapters firmware-atheros - Binary firmware for Qualcomm Atheros wireless cards firmware-brcm80211 - Binary firmware for Broadcom/Cypress 802.11 wireless cards firmware-ipw2x00 - Binary firmware for Intel Pro Wireless 2100, 2200 and 2915 firmware-iwlwifi - Binary firmware for Intel Wireless cards firmware-libertas - Binary firmware for Marvell wireless cards firmware-realtek - Binary firmware for Realtek wired/wifi/BT adapters firmware-ti-connectivity - Binary firmware for TI Connectivity wifi and BT/FM/GPS adapters firmware-zd1211 - binary firmware for the zd1211rw wireless driver firmware-ralink - Binary firmware for Ralink wireless cards (dummmy package) > Merci a vous Bonne soirée, -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. signature.asc Description: PGP signature
Re: Sid, upgrade kernel casse mon Wifi
Bonjour d'apres le support System76 la these de la panne materielle semble la plus probable. Je vais donc commander une carte et tester Vous avez des references a conseiller en la matiere, compatibles si possible Linux libre ? chipsets ath9k ou ath10k . D'autres ? Quelles references eventuellement ... Merci a vous Le lun. 8 févr. 2021 à 18:12, jerome moliere a écrit : > Bonjour a tous, > je suis victime d'un souci sournois sur 1 laptop System76 lemur pro dote > de composants Intel 11eme generation. > Suite a l'upgrade du kernel en 5.10-2 (et 3 depuis) je n'ai plus de wifi: > - lspci voit toujours la carte lspci -nnk > lspci -nnk|grep -i network ─╯ > 00:14.3 Network controller [0280]: Intel Corporation Comet Lake PCH-LP > CNVi WiFi [8086:02f0] > > par contre elle est invisible par ip/iwconfig etc > ip a ─╯ > 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group > default qlen 1000 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo >valid_lft forever preferred_lft forever > inet6 ::1/128 scope host >valid_lft forever preferred_lft forever > 2: enx0050b6ebc397: mtu 1500 > qdisc pfifo_fast state UP group default qlen 1000 > link/ether 00:50:b6:eb:c3:97 brd ff:ff:ff:ff:ff:ff > inet 192.168.1.34/24 brd 192.168.1.255 scope global enx0050b6ebc397 >valid_lft forever preferred_lft forever > inet6 2a01:cb19:65b:4100:2b1a:5245:8c46:60f3/64 scope global temporary > dynamic >valid_lft 1773sec preferred_lft 573sec > inet6 2a01:cb19:65b:4100:250:b6ff:feeb:c397/64 scope global dynamic > mngtmpaddr >valid_lft 1773sec preferred_lft 573sec > inet6 fe80::250:b6ff:feeb:c397/64 scope link >valid_lft forever preferred_lft forever > 3: docker0: mtu 1500 qdisc noqueue > state DOWN group default > link/ether 02:42:a0:41:aa:9a brd ff:ff:ff:ff:ff:ff > inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 >valid_lft forever preferred_lft forever > > > Dans les logs du kernel on voit qu'il y a un souci de chargement du > firmware: > sudo dmesg|grep -i iwlwifi > > >─╯ > [4.769596] iwlwifi :00:14.3: minimum version required: (efault)198 > [4.769643] iwlwifi :00:14.3: maximum version supported: (efault)143 > [4.769684] iwlwifi :00:14.3: check git:// > git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git > [4.769744] iwlwifi :00:14.3: Couldn't request the fw > [4.783252] iwlwifi: probe of :00:14.3 failed with error -2 > > > Effectivement avec une version mini (198) > a la version maxi (143) cela > va etre dur de charger quoi que ce soit je pense > J'ai tente de copier les fichiers .ucode chopes sur le site de Intel dans > /lib/firmware mais sans succes > > > Que puis je faire ? > Depuis ma carte wifi est invisible sur toutes les distros avec des kernels > differents j'ai tente plusieurs livecd mais elle est tjs aux abonnes > absents... > > Vos conseils eclaires sont les bienvenus. > Cordialement >
Re: Sid, upgrade kernel casse mon Wifi
Bonjour a tous, merci Etienne de cete reponse... Alors OUI le souci n'est pas specifique a une distro il se produit pour toutes les distros testees (environ 7 ou 8 avec des versions de kernel et de packages linux-firmware differentes) J'ai voulu teste GhostBSD mais la machine est recente et il ne boote pas ...-( La carte Wifi est vue par le systeme avec lspci -nnk et le module essaie de se charger Et juste avant l'update (jusqu'a Dimanche soir ou Lundi) elle fonctionnait tres biem Cela me parait etre du soft pur et dur Pour les numeros de version a noter que Garuda (Arch based) n'indique pas les memes mais ils sont errones et incoherents de la meme facon Merci encore du coup de main... Je dois dire que je n'ai jamais ete confronte a un souci aussi severe Encore merci Le mar. 9 févr. 2021 à 21:26, Étienne Mollier a écrit : > Bonsoir Jérôme, > > jerome moliere, on 2021-02-08 18:12:11 +0100: > > Dans les logs du kernel on voit qu'il y a un souci de chargement du > > firmware: > > sudo dmesg|grep -i iwlwifi > > Les numéros de version ci-après : > > > [4.769596] iwlwifi :00:14.3: minimum version required: > (efault)198 > > > [4.769643] iwlwifi :00:14.3: maximum version supported: > (efault)143 > > sont précédés de la mention "(efault)". Pour une raison ou pour > une autre, le pilote tente d'accèder à une address invalide[1] > pour indiquer les numéros de version de micrologiciel supportés > par le pilote, d'où le résultat confus. > > [1] > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/core-api/printk-formats.rst#n68 > > > [4.769684] iwlwifi :00:14.3: check git:// > > git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git > > [4.769744] iwlwifi :00:14.3: Couldn't request the fw > > [4.783252] iwlwifi: probe of :00:14.3 failed with error -2 > [...] > > Que puis je faire ? > > Depuis ma carte wifi est invisible sur toutes les distros avec des > kernels > > differents j'ai tente plusieurs livecd mais elle est tjs aux abonnes > > absents... > > Si le problème est indépendant des distributions, apparaissant > ailleurs que dans Debian et ses distributions dérivées, alors ça > vaudrait peut-être le coup d'ouvrir un rapport de bogue sur > le bugzilla en amont[2]. > > Éventuellement, ça pourrait valoir le coup de tester avec un > système d'exploitation et un noyau entièrement différent (BSD, > MS Windows), si c'est possible bien entendu, juste pour > s'assurer que ce n'est pas la carte wifi qui a rendu l'âme. > > [2] https://bugzilla.kernel.org/ > > Bonne soirée, > -- > Étienne Mollier > Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da > Sent from /dev/pts/2, please excuse my verbosity. >
Re: Sid, upgrade kernel casse mon Wifi
Bonsoir Jérôme, jerome moliere, on 2021-02-08 18:12:11 +0100: > Dans les logs du kernel on voit qu'il y a un souci de chargement du > firmware: > sudo dmesg|grep -i iwlwifi Les numéros de version ci-après : > [4.769596] iwlwifi :00:14.3: minimum version required: (efault)198 > [4.769643] iwlwifi :00:14.3: maximum version supported: (efault)143 sont précédés de la mention "(efault)". Pour une raison ou pour une autre, le pilote tente d'accèder à une address invalide[1] pour indiquer les numéros de version de micrologiciel supportés par le pilote, d'où le résultat confus. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/core-api/printk-formats.rst#n68 > [4.769684] iwlwifi :00:14.3: check git:// > git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git > [4.769744] iwlwifi :00:14.3: Couldn't request the fw > [4.783252] iwlwifi: probe of :00:14.3 failed with error -2 [...] > Que puis je faire ? > Depuis ma carte wifi est invisible sur toutes les distros avec des kernels > differents j'ai tente plusieurs livecd mais elle est tjs aux abonnes > absents... Si le problème est indépendant des distributions, apparaissant ailleurs que dans Debian et ses distributions dérivées, alors ça vaudrait peut-être le coup d'ouvrir un rapport de bogue sur le bugzilla en amont[2]. Éventuellement, ça pourrait valoir le coup de tester avec un système d'exploitation et un noyau entièrement différent (BSD, MS Windows), si c'est possible bien entendu, juste pour s'assurer que ce n'est pas la carte wifi qui a rendu l'âme. [2] https://bugzilla.kernel.org/ Bonne soirée, -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. signature.asc Description: PGP signature
Sid, upgrade kernel casse mon Wifi
Bonjour a tous, je suis victime d'un souci sournois sur 1 laptop System76 lemur pro dote de composants Intel 11eme generation. Suite a l'upgrade du kernel en 5.10-2 (et 3 depuis) je n'ai plus de wifi: - lspci voit toujours la carte lspci -nnk lspci -nnk|grep -i network ─╯ 00:14.3 Network controller [0280]: Intel Corporation Comet Lake PCH-LP CNVi WiFi [8086:02f0] par contre elle est invisible par ip/iwconfig etc ip a ─╯ 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enx0050b6ebc397: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:50:b6:eb:c3:97 brd ff:ff:ff:ff:ff:ff inet 192.168.1.34/24 brd 192.168.1.255 scope global enx0050b6ebc397 valid_lft forever preferred_lft forever inet6 2a01:cb19:65b:4100:2b1a:5245:8c46:60f3/64 scope global temporary dynamic valid_lft 1773sec preferred_lft 573sec inet6 2a01:cb19:65b:4100:250:b6ff:feeb:c397/64 scope global dynamic mngtmpaddr valid_lft 1773sec preferred_lft 573sec inet6 fe80::250:b6ff:feeb:c397/64 scope link valid_lft forever preferred_lft forever 3: docker0: mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:a0:41:aa:9a brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever Dans les logs du kernel on voit qu'il y a un souci de chargement du firmware: sudo dmesg|grep -i iwlwifi ─╯ [4.769596] iwlwifi :00:14.3: minimum version required: (efault)198 [4.769643] iwlwifi :00:14.3: maximum version supported: (efault)143 [4.769684] iwlwifi :00:14.3: check git:// git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git [4.769744] iwlwifi :00:14.3: Couldn't request the fw [4.783252] iwlwifi: probe of :00:14.3 failed with error -2 Effectivement avec une version mini (198) > a la version maxi (143) cela va etre dur de charger quoi que ce soit je pense J'ai tente de copier les fichiers .ucode chopes sur le site de Intel dans /lib/firmware mais sans succes Que puis je faire ? Depuis ma carte wifi est invisible sur toutes les distros avec des kernels differents j'ai tente plusieurs livecd mais elle est tjs aux abonnes absents... Vos conseils eclaires sont les bienvenus. Cordialement
Re: Upgrade kernel to 3.19+ OR Bumblebee cannot enable discrete graphics
Fri, 01 May 2015 17:15:18 -0700 Joris Bolsens epicbl...@gmail.com écrivait : Just tried that: The following packages have unmet dependencies: linux-headers-4.0.0-trunk-amd64 : Depends: linux-kbuild-4.0 but it is not installable seems linux-kbuild-4.0 is not in sid repos yet Not in Sid yet but in experimental. If you use testing or sid, adding experimental is not a problem. It is a non-automatic release. Jean-Marc jean-m...@6jf.be pgppLdqzll2_l.pgp Description: PGP signature
Re: Upgrade kernel to 3.19+ OR Bumblebee cannot enable discrete graphics
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/01/2015 11:29 PM, Jean-Marc wrote: Not in Sid yet but in experimental. If you use testing or sid, adding experimental is not a problem. It is a non-automatic release. Jean-Marc jean-m...@6jf.be latest kbuild in experimental is 3.18 :/ -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVRUalAAoJEORnMHMHY2FrI5IQAICICOnEkErpBq3emThbTF+d tCyoswrGXP2SYO1xW0+JJ/wSJznRs1C6THYcHFRRMzaFr+L1WBEVD77z5XMTX0hf mQgMcs+YCd1B4o8JSyiL3sZQvPDSAoJjqj3jp8OdKq38JHdJw+UY+Pff9vmWg3oP +j27DX9vR6IHPSfftKuK1JavjdtiNjNM5QrQvRsDqpmunD2jW4FKxjKDmdJcau+y CHPZ46gNti2Qz9k383s+2oQmTc3cjx8gSI3e6kxhgKqsqdr13C6UNX2XeusaPgQh PiSUNduba1I/9vT4sWxKXbqdKejpaGHU00BZ2X5C3hEr+Sqkn6xkvMqDTq1UhIiz NxYXt72cuI654IuQhaEf7ddhwdlulvbVy9YPk4N9Co/kh5PCXwKBRogXzd4G5lW4 wavqDhOcK0H78o4wQHONaBApOHpFzROqbi/WCUVx3TZicOR60oT+PvLT4VchNDpC 8ZUDEDTRFdmY1Gf8W7DgdVtOtsP2p3WrrN2cZgmH0We/TCeUZCa243TyduOILdLl 3xCYqDuL9WlJVgPQyZ+Nj+Jw/S1NO76syqfTwH/SwkF4ok5w3xDO/fUiTzWdhJNC 7Ji1xgOIGOdcZJLCnABCTEjzft0wVaiIM1p+O9gPoKOuLgGTfZhw43eN8fHTt2cN JENxacQuqlsVghrS7lLV =XTaO -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554546a5.10...@gmail.com
Re: Upgrade kernel to 3.19+ OR Bumblebee cannot enable discrete graphics
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/01/2015 12:58 AM, Jean-Marc wrote: Fri, 01 May 2015 00:06:57 -0700 No need to do it yourself, it is already done here: https://packages.debian.org/experimental/linux-image-4.0.0-trunk-amd64 Jean-Marc jean-m...@6jf.be Just tried that: The following packages have unmet dependencies: linux-headers-4.0.0-trunk-amd64 : Depends: linux-kbuild-4.0 but it is not installable seems linux-kbuild-4.0 is not in sid repos yet -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVRBcWAAoJEORnMHMHY2FrXe8QAJUSR9a5DBU6gPcZtTjMlh4z vlM9QOUUI69XujiyxxdsZOFMHE6RpEOLaanqZmtxHf4g6/4ZjMYWtTXHbyN7O4bo P5PcA3FwN0oop8dwPCmD6nXEX9HpaZzHfsUkeJocziSVbFPrBNexNunCWNK4YasP J5LOpwExyCzZXoKk9CrHOjCTAZZgr5SuzKRtdk0tGGc0V43yPtuEsm1LN1Lh+7+l JR474av6LQmHZ943VdKdS9ugzcUicne+EDfn9oYkD/mEBp4HlK0eltcIGo5rXLF+ YDhaX5dSiySyUWq4FB+fXk2XOKGP1SbyS1ubFRy9Ifl5mGLgkVr4FS95bUe5adkY gR0jpu+XOb2GpgtzoPO4hZ7kgbryJ0NthJ1huE7bfphIJtlgV+x5/8D9tm/v4fMx sQgB1B2kNp6enwTZ88QrYLOhOsHXPhynSMnAWmw0VHKk7elV3j25TaULRDzvjpje F5rKrWRC8xDKPJqp4YaiLz2N4SURHCcVSkiyYJ4hydVaCFcl5BlLak2Qfbfqp8L/ DLILqr+fI7nMLObk2zbG1oPG0VhdSfgikK4LP3rPkPJ1LVKUwy3gIe+Gtu2A5POa oW/jrbSq+kgR3kHzUwz+WiORaLjeqJ8Zy+bqcbZnk142Cvf2uvFPt5aP8yz518xA pbHCUARLYxwnD/Jygbtj =d49V -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55441716.4070...@gmail.com
Re: Upgrade kernel to 3.19+ OR Bumblebee cannot enable discrete graphics
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/01/2015 12:05 AM, humbert.olivie...@free.fr wrote: Hi I was wondering if anyone had instructions on how to update to kernel 3.19 or above. I have spent ~an hour googling, but all I can find are tutorials for ubuntu, most of which do it through apt. Looks to be there : https://www.debian.org/releases/stable/i386/ch08s06.html.en Hope that helps Olivier Thanks, thats what im doing now, just compiled 4.0.1 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVQyYRAAoJEORnMHMHY2Fr8n8QAIsFXfhD2G+OQZB0HpE6THJW jFG2uJnqnZKolVF1h5VrjKKDUqMYwUzJuE7MuzzSRXv/9vUub7jzst8rMLbXieDf QAvlrhpvpbWCO666WIcv4uKnj8vy3b8YHUidiCTR8VlMstjOGZL8e8arYT5NFAmi wNscfPn2B+1PA0KQM8GptLNfCp+MkoKP0UyZEAfRFNJldxpEAVDMOwFafnXzkvOd PRyYgL/pcekp2PE+EunmIBMyvYQY7mlrYSc3akesPKPzGG197oae7ll5Vlo3hLnT XH0K3aPLkBe3dPNTT1ykOg+aVlenHUy2RcXJ6tBOxM9Lf58y1r4ktafH2xIeCnPb Fh5/49F96zB8rev6Bnj24RYQV+B8SeWXWqjVoNYmdKbUAV+LtjeMCab6ueCyElu+ Ii201sjL8+1E2PgDFeEzF1JrLE7kSJgbFUgT/fFbrBFz6gzqDMBCGU/9XUqe0nQW XWnxDx43TpjM7H7CZCLee4iBdwddNgKC3+YEARBTb29BLMIp5JwC909XYXwHEkcb 6t/3t651Q8s72j0iwIpWRy1W0aiYqu/akmxkajz2WoFiTu/ZxokTxZpcb0P/l4+B voFMzZqINi8jDz7W+PQ7BVpZF8OukoIjOTKouSQD9KjU6E7KTpJk8SMXtUl/y9LW PcGT/EL4BaCDECDguzhv =RXK2 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55432611.9040...@gmail.com
Re: Upgrade kernel to 3.19+ OR Bumblebee cannot enable discrete graphics
Hi I was wondering if anyone had instructions on how to update to kernel 3.19 or above. I have spent ~an hour googling, but all I can find are tutorials for ubuntu, most of which do it through apt. Looks to be there : https://www.debian.org/releases/stable/i386/ch08s06.html.en Hope that helps Olivier -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1400904479.1028077121.1430463950749.javamail.r...@zimbra61-e11.priv.proxad.net
Re: Upgrade kernel to 3.19+ OR Bumblebee cannot enable discrete graphics
humbert.olivie...@free.fr writes: Looks to be there : https://www.debian.org/releases/stable/i386/ch08s06.html.en the document does not mention configuration with 'make oldconfig', which may simplify the process and has worked for me when i built 3.17. -- juha -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/21827.10602.344858.268...@tutpro.com
Re: Upgrade kernel to 3.19+ OR Bumblebee cannot enable discrete graphics
Le primidi 11 floréal, an CCXXIII, Joris Bolsens a écrit : I was wondering if anyone had instructions on how to update to kernel 3.19 or above. I have spent ~an hour googling, but all I can find are tutorials for ubuntu, most of which do it through apt. I checked jessie-backports but 3.16 seems to be the latest available outside of unstable. There is a 4.0.0 in experimental. It seems configured with a lot fewer options than the usual kernels. But it boots, it may serve as a simpler base for configuring your kernel, because each new version changes the options a lot. (I am trying to use it with a Lenovo Miix 3-1030, a hybrid PC-tablet: it fixes a few things compared to the 3.16 in stable/testing/unstable (no oops when unblanking the screen, clocksource automatically selected) but some things are even less taken into account, especially this one: byt-rt5640 byt-rt5640: ASoC: CPU DAI baytrail-pcm-audio not registered, because the module seems to have been disabled.) Hope this helps. Regards, -- Nicolas George signature.asc Description: Digital signature
Re: Upgrade kernel to 3.19+ OR Bumblebee cannot enable discrete graphics
Fri, 01 May 2015 00:06:57 -0700 Joris Bolsens epicbl...@gmail.com écrivait : [...] Thanks, thats what im doing now, just compiled 4.0.1 No need to do it yourself, it is already done here: https://packages.debian.org/experimental/linux-image-4.0.0-trunk-amd64 Jean-Marc jean-m...@6jf.be pgpyvZFsrLqnI.pgp Description: PGP signature
Upgrade kernel to 3.19+ OR Bumblebee cannot enable discrete graphics
Hi list, I was wondering if anyone had instructions on how to update to kernel 3.19 or above. I have spent ~an hour googling, but all I can find are tutorials for ubuntu, most of which do it through apt. I checked jessie-backports but 3.16 seems to be the latest available outside of unstable. The reason I want to upgrade is I seem to be affected by a bug[1] that causes bumblebee to not be able to switch on my discrete graphics card, and said issue was reportedly fixed in kernel 3.19[2] Or if someone knows how to fix this without upgrading that would be even more appreciated. My issue is that bumblebee can't enable my discrete graphics card. I have a GT 745m 01:00.0 3D controller: NVIDIA Corporation GK107M [GeForce GT 745M] (rev ff) my onboard: 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) whenever I try to `optirun` anything I get --- $ optirun glxgears [37224.064111] [ERROR]Cannot access secondary GPU - error: Could not enable discrete graphics card [37224.064129] [ERROR]Aborting because fallback start is disabled. --- and bumblebee logs: --- [37207.802462] [INFO]bumblebeed 3.2.1 started [37207.802516] [INFO]Initialization completed - now handling client requests [37224.051468] [DEBUG]Accepted new connection [37224.051559] [INFO]Switching dedicated card ON [bbswitch] [37224.064087] [ERROR]Could not enable discrete graphics card [37224.064145] [DEBUG]Socket closed. --- and dmesg: --- [37254.827782] bbswitch: enabling discrete graphics [37254.840269] pci :01:00.0: Refused to change power state, currently in D3 --- [1]: https://github.com/Bumblebee-Project/Bumblebee/issues/615 [2]:https://github.com/Bumblebee-Project/Bumblebee/issues/615#issuecomment-91174982 signature.asc Description: OpenPGP digital signature
Re: upgrade kernel
On 24/01/2015 21:40, Pascal Hambourg wrote: mrr a écrit : I saw somewhere during kernel compilation an option to load a kernel on the fly but I haven't gone further (maybe it was targeted at kernel developers). If you're talking about kexec, it just avoid the firmware POST and bootloader stage of a complete reboot, but not the system init. AFAIK you cannot just swap kernels while userland processes keep running. That was it, thanks for the upgrade Or are you talking about live kernel patching such as ksplice, which allows security patches to be applied to a running kernel without rebooting ? So usually, you do reboot after a kernel upgrade if you want to run the new one. It's the only occasion (I hope systemd hasn't changed that!) when an upgrade needs a reboot (or am I wrong?). Sometimes though you need a simple log out / log in. All running processes using an upgraded executable must be restarted, otherwise it keeps using the old version. This include all the libraries it uses. When the libc, which is used by most programs, is upgraded, it may be easier to reboot the whole system. -- mrr -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54c5e308$0$5111$426a7...@news.free.fr
Re: upgrade kernel
mrr a écrit : I saw somewhere during kernel compilation an option to load a kernel on the fly but I haven't gone further (maybe it was targeted at kernel developers). If you're talking about kexec, it just avoid the firmware POST and bootloader stage of a complete reboot, but not the system init. AFAIK you cannot just swap kernels while userland processes keep running. Or are you talking about live kernel patching such as ksplice, which allows security patches to be applied to a running kernel without rebooting ? So usually, you do reboot after a kernel upgrade if you want to run the new one. It's the only occasion (I hope systemd hasn't changed that!) when an upgrade needs a reboot (or am I wrong?). Sometimes though you need a simple log out / log in. All running processes using an upgraded executable must be restarted, otherwise it keeps using the old version. This include all the libraries it uses. When the libc, which is used by most programs, is upgraded, it may be easier to reboot the whole system. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54c3ff27.5070...@plouf.fr.eu.org
Re: upgrade kernel
On 16/01/2015 17:50, Marc Auslander wrote: Pol Hallen de...@fuckaround.org writes: Hi folks! a security updates of kernel is available (from apt-get upgrade), so: must I reboot my pc (after upgrade) to avoid security problems? Is there another way? thanks for help! Pol I always reboot after a kernel related upgrade on the grounds that if something goes wrong, I want to know about it right now. The alternative is that sometime in the future, a scheduled or unscheduled reboot leads to trouble and you have no idea what caused it! I saw somewhere during kernel compilation an option to load a kernel on the fly but I haven't gone further (maybe it was targeted at kernel developers). So usually, you do reboot after a kernel upgrade if you want to run the new one. It's the only occasion (I hope systemd hasn't changed that!) when an upgrade needs a reboot (or am I wrong?). Sometimes though you need a simple log out / log in. Cheers, -- mrr -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54c33aa9$0$2127$426a3...@news.free.fr
Re: upgrade kernel
Pol Hallen de...@fuckaround.org writes: Hi folks! a security updates of kernel is available (from apt-get upgrade), so: must I reboot my pc (after upgrade) to avoid security problems? Is there another way? thanks for help! Pol I always reboot after a kernel related upgrade on the grounds that if something goes wrong, I want to know about it right now. The alternative is that sometime in the future, a scheduled or unscheduled reboot leads to trouble and you have no idea what caused it! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/877fwmbrx3@aptiva.optonline.net
upgrade kernel
Hi folks! a security updates of kernel is available (from apt-get upgrade), so: must I reboot my pc (after upgrade) to avoid security problems? Is there another way? thanks for help! Pol -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b816bc.8000...@fuckaround.org
Re: upgrade kernel
Hello, Pol Hallen a écrit : a security updates of kernel is available (from apt-get upgrade), so: must I reboot my pc (after upgrade) to avoid security problems? Usually yes. Until then, the old kernel is still active. Is there another way? You could use kexec-tools to load and start the new kernel, skipping the firmware and bootloader stages. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b81d35.80...@plouf.fr.eu.org
Re: unable to upgrade kernel
El vie, 04-07-2014 a las 15:25 +0200, François Patte escribió: Bonjour, I don't understand the following: # apt-get install linux-image-3.14-0.bpo.1-amd64 linux-headers-3.14-0.bpo.1-amd64 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-3.14-0.bpo.1-amd64 : Breaks: initramfs-tools ( 0.110~) but 0.109.1 is to be installed Breaks: initramfs-tools:i386 ( 0.110~) E: Unable to correct problems, you have held broken packages. What exactly is the problem about initramfs: # apt-cache show initramfs-tools Package: initramfs-tools Version: 0.109.1 When you are going to install backport packages (bpo), you must explicitly indicate apt-get to do so, using the -t option to target backport repositories. The problem is that the release version of initramfs-tools is lower than the needed one in backports and it won't be installed if target is not set. If using Wheezy, you must use apt-get this way: apt-get -t=wheezy-backports install linux-image-3.14.0.bpo.1-amd64 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1404574294.15638.9.ca...@chaos.casa
Re: unable to upgrade kernel
On Fri, Jul 4, 2014 at 1:02 PM, François Patte francois.pa...@mi.parisdescartes.fr wrote: Le 04/07/2014 16:12, Lisi Reisz a écrit : On Friday 04 July 2014 14:42:47 Stephen Powell wrote: Since you are trying to install a 3.14 kernel from backports, I assume that you are running wheezy. You need to install the initramfs-tools package from wheezy-backports too, version 0.115~bpo70+1, I think. I had no trouble installing the backported kernel, but I specifically instructed aptitude to use wheezy-backports repository. -t wheezy-backports install OK thank this worked... I thought that adding backports repository to the source.list file was enough! This is quite redondant! The apt priority of *-backports only allows a package to be upgraded automatically. You have to speficy a package for it to be installed. You can check the apt priority of your repositories with apt-cache policy. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAOdo=sxq5a0sbqmg1mcsuda3bamehhad98qppkb+sswwwv4...@mail.gmail.com
unable to upgrade kernel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bonjour, I don't understand the following: # apt-get install linux-image-3.14-0.bpo.1-amd64 linux-headers-3.14-0.bpo.1-amd64 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-3.14-0.bpo.1-amd64 : Breaks: initramfs-tools ( 0.110~) but 0.109.1 is to be installed Breaks: initramfs-tools:i386 ( 0.110~) E: Unable to correct problems, you have held broken packages. What exactly is the problem about initramfs: # apt-cache show initramfs-tools Package: initramfs-tools Version: 0.109.1 - -- François Patte UFR de mathématiques et informatique Laboratoire CNRS MAP5, UMR 8145 Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)1 8394 5849 http://www.math-info.univ-paris5.fr/~patte -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlO2q14ACgkQdE6C2dhV2JWsGgCgj9y2sqCqYXk8mZKe6dLdpbV3 a38AoNIyb/gYRsWmez75TRJNo6I/JkJ5 =2nzs -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53b6ab5f.6080...@mi.parisdescartes.fr
Re: unable to upgrade kernel
On Fri, 04 Jul 2014 09:25:51 -0400 (EDT), François Patte wrote: I don't understand the following: # apt-get install linux-image-3.14-0.bpo.1-amd64 linux-headers-3.14-0.bpo.1-amd64 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-3.14-0.bpo.1-amd64 : Breaks: initramfs-tools ( 0.110~) but 0.109.1 is to be installed Breaks: initramfs-tools:i386 ( 0.110~) E: Unable to correct problems, you have held broken packages. What exactly is the problem about initramfs: # apt-cache show initramfs-tools Package: initramfs-tools Version: 0.109.1 The problem is that the kernel you want to install requires a newer version of initramfs-tools than the one you currently have installed, but apt-get cannot upgrade to a newer version of initramfs-tools. Since you are trying to install a 3.14 kernel from backports, I assume that you are running wheezy. You need to install the initramfs-tools package from wheezy-backports too, version 0.115~bpo70+1, I think. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2017728434.444101.1404481367368.javamail.r...@md01.wow.synacor.com
Re: unable to upgrade kernel
On Friday 04 July 2014 14:42:47 Stephen Powell wrote: Since you are trying to install a 3.14 kernel from backports, I assume that you are running wheezy. You need to install the initramfs-tools package from wheezy-backports too, version 0.115~bpo70+1, I think. I had no trouble installing the backported kernel, but I specifically instructed aptitude to use wheezy-backports repository. -t wheezy-backports install, so perhaps it upgraded dependancies. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201407041512.27209.lisi.re...@gmail.com
Re: unable to upgrade kernel
On 07/04/2014 04:12 PM, Lisi Reisz wrote: On Friday 04 July 2014 14:42:47 Stephen Powell wrote: Since you are trying to install a 3.14 kernel from backports, I assume that you are running wheezy. You need to install the initramfs-tools package from wheezy-backports too, version 0.115~bpo70+1, I think. I had no trouble installing the backported kernel, but I specifically instructed aptitude to use wheezy-backports repository. -t wheezy-backports install, so perhaps it upgraded dependancies. I do not think it is related to the -t wheezy-backports but rather a difference between apt-get and aptitude: Unlike apt-get, aptitude suggests to upgrade initramfs-tools after one has rejected some other proposals. Linux-Fan signature.asc Description: OpenPGP digital signature
Re: unable to upgrade kernel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 04/07/2014 16:12, Lisi Reisz a écrit : On Friday 04 July 2014 14:42:47 Stephen Powell wrote: Since you are trying to install a 3.14 kernel from backports, I assume that you are running wheezy. You need to install the initramfs-tools package from wheezy-backports too, version 0.115~bpo70+1, I think. I had no trouble installing the backported kernel, but I specifically instructed aptitude to use wheezy-backports repository. -t wheezy-backports install OK thank this worked... I thought that adding backports repository to the source.list file was enough! This is quite redondant! - -- François Patte UFR de mathématiques et informatique Laboratoire CNRS MAP5, UMR 8145 Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)1 8394 5849 http://www.math-info.univ-paris5.fr/~patte -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlO23jIACgkQdE6C2dhV2JUUkwCgrrIol3el/EVnvDqto37i9wUa HYYAnR8gZbD5o+MaIYsCd9FZatZbDptQ =lWcG -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53b6de32.6090...@mi.parisdescartes.fr
Re: unable to upgrade kernel
On Friday 04 July 2014 18:02:42 François Patte wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 04/07/2014 16:12, Lisi Reisz a écrit : On Friday 04 July 2014 14:42:47 Stephen Powell wrote: Since you are trying to install a 3.14 kernel from backports, I assume that you are running wheezy. You need to install the initramfs-tools package from wheezy-backports too, version 0.115~bpo70+1, I think. I had no trouble installing the backported kernel, but I specifically instructed aptitude to use wheezy-backports repository. -t wheezy-backports install OK thank this worked... Great! Lisi I thought that adding backports repository to the source.list file was enough! This is quite redondant! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201407041831.50617.lisi.re...@gmail.com
Re: unable to upgrade kernel
On Friday 04 July 2014 15:30:10 Linux-Fan wrote: On 07/04/2014 04:12 PM, Lisi Reisz wrote: On Friday 04 July 2014 14:42:47 Stephen Powell wrote: Since you are trying to install a 3.14 kernel from backports, I assume that you are running wheezy. You need to install the initramfs-tools package from wheezy-backports too, version 0.115~bpo70+1, I think. I had no trouble installing the backported kernel, but I specifically instructed aptitude to use wheezy-backports repository. -t wheezy-backports install, so perhaps it upgraded dependancies. I do not think it is related to the -t wheezy-backports but rather a difference between apt-get and aptitude: Unlike apt-get, aptitude suggests to upgrade initramfs-tools after one has rejected some other proposals. I didn't have to reject anything. It just did it. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201407041831.10053.lisi.re...@gmail.com
Re: unable to upgrade kernel
On 2014-07-04, François Patte francois.pa...@mi.parisdescartes.fr wrote: OK thank this worked... I thought that adding backports repository to the source.list file was enough! This is quite redondant! The repository is desactivated by default; otherwise, well, I'll leave that as an exercise ... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnlrdru2.209.cu...@einstein.electron.org
Re: unable to upgrade kernel
On Fri, Jul 04, 2014 at 07:02:42PM +0200, François Patte wrote: Le 04/07/2014 16:12, Lisi Reisz a écrit : I had no trouble installing the backported kernel, but I specifically instructed aptitude to use wheezy-backports repository. -t wheezy-backports install OK thank this worked... I thought that adding backports repository to the source.list file was enough! This is quite redondant! If you mean redundant, it is a safety precaution. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140705035942.GD10386@tal
Re: Problem upgrade Kernel on DNS323
On Thu, 18 Aug 2011 10:54:08 +0200, Michael Ott wrote: I got the following output when I try to update my DNS323. Can anybody help me? Thanks in advance (...) Can't find /boot/vmlinuz-2.6.39-2-orion5x and /boot/initrd.img-2.6.39-2-orion5x (...) There was a bug for a similar problem, look: linux-image-2.6.38-2-ixp4xx fails to install http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628136 Not sure if that tells you something or can help you with your issue :-? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.08.20.13.48...@gmail.com
Problem upgrade Kernel on DNS323
Hi! I got the following output when I try to update my DNS323. Can anybody help me? Thanks in advance ~# apt-get -uVf dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 4 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? y Setting up linux-image-2.6.39-2-orion5x (2.6.39-3) ... Running depmod. The link /boot/initrd.img is a dangling linkto /boot/initrd.img-3.0.0-1-orion5x Running flash-kernel. Can't find /boot/vmlinuz-2.6.39-2-orion5x and /boot/initrd.img-2.6.39-2-orion5x User postinst hook script [flash-kernel] exited with value 1 dpkg: error processing linux-image-2.6.39-2-orion5x (--configure): subprocess installed post-installation script returned error exit status 1 configured to not write apport reports Setting up linux-image-3.0.0-1-orion5x (3.0.0-1) ... Running depmod. The link /boot/initrd.img is a dangling linkto /boot/initrd.img-2.6.39-2-orion5x Running flash-kernel. Can't find /boot/vmlinuz-3.0.0-1-orion5x and /boot/initrd.img-3.0.0-1-orion5x User postinst hook script [flash-kernel] exited with value 1 dpkg: error processing linux-image-3.0.0-1-orion5x (--configure): subprocess installed post-installation script returned error exit status 1 configured to not write apport reports dpkg: dependency problems prevent configuration of linux-image-orion5x: linux-image-orion5x depends on linux-image-3.0.0-1-orion5x; however: Package linux-image-3.0.0-1-orion5x is not configured yet. dpkg: error processing linux-image-orion5x (--configure): dependency problems - leaving unconfigured configured to not write apport reports dpkg: dependency problems prevent configuration of linux-image-2.6-orion5x: linux-image-2.6-orion5x depends on linux-image-orion5x; however: Package linux-image-orion5x is not configured yet. dpkg: error processing linux-image-2.6-orion5x (--configure): dependency problems - leaving unconfigured configured to not write apport reports Errors were encountered while processing: linux-image-2.6.39-2-orion5x linux-image-3.0.0-1-orion5x linux-image-orion5x linux-image-2.6-orion5x E: Sub-process /usr/bin/dpkg returned an error code (1) CU Michael -- ,''`. : :' : Michael Ott `. `'e-mail: michael at king-coder dot de `- signature.asc Description: Digital signature
Re: How to upgrade kernel in Lenny, not compile a custom one
Greg Madden wrote: On Saturday 02 October 2010 11:59:02 Mark wrote: Based on what I've read, kernel 2.6.32 has fixed the broadcom 4306 rev02 wireless card 1 MB/s speed issue and I'd like to have my Lenny system boot into that kernel to fix this issue. snip Debian backports (official) has the 2.6.32 kernel, add the following to your sources.list: deb http://www.backports.org/debian lenny-backports main Works good. /home/hugo/gpc-qt4-002Sun Oct 03-08:59:10SDB3# uname -a Linux debian 2.6.32-5-686 #1 SMP Sat Sep 18 02:14:45 UTC 2010 i686 GNU/Linux Hugo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/i8a3qg$55...@dough.gmane.org
How to upgrade kernel in Lenny, not compile a custom one
Based on what I've read, kernel 2.6.32 has fixed the broadcom 4306 rev02 wireless card 1 MB/s speed issue and I'd like to have my Lenny system boot into that kernel to fix this issue. The only help I've found for doing this without doing a custom compile is here ( http://www.khattam.info/installing-kernel-2-6-30-or-any-latest-version-available-in-debian-lenny-or-ubuntu-without-having-to-go-through-compiling-2009-08-10.html). As I haven't done this before, can anyone provide feedback on this link, its methods, etc., before I go trying a kernel upgrade? If there is another way, I'm open to suggestions. I don't need a custom kernel, just need to boot Lenny into a 2.6.32 or later kernel, if possible. Thank you, Mark
Re: How to upgrade kernel in Lenny, not compile a custom one
On Saturday 02 October 2010 11:59:02 Mark wrote: Based on what I've read, kernel 2.6.32 has fixed the broadcom 4306 rev02 wireless card 1 MB/s speed issue and I'd like to have my Lenny system boot into that kernel to fix this issue. The only help I've found for doing this without doing a custom compile is here ( http://www.khattam.info/installing-kernel-2-6-30-or-any-latest-version-avai lable-in-debian-lenny-or-ubuntu-without-having-to-go-through-compiling-2009- 08-10.html). As I haven't done this before, can anyone provide feedback on this link, its methods, etc., before I go trying a kernel upgrade? If there is another way, I'm open to suggestions. I don't need a custom kernel, just need to boot Lenny into a 2.6.32 or later kernel, if possible. Thank you, Mark Debian backports (official) has the 2.6.32 kernel, add the following to your sources.list: deb http://www.backports.org/debian lenny-backports main There are other install media available by third parties for newer hardware configurations, google or this list has references also. -- Peace, Greg -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201010021319.56116.gomadtr...@gci.net
Re: Upgrade Kernel, Lose External Display
Clean slate, sort of. I've removed any xorg.conf and am not blacklisting any more. System docked will not give me a display on the external screen, whether booted from old kernel or new one. System undocked works perfectly. I'm attaching a new dmesg output with the system docked with the new kernel and the updated xserver-common and xserver-xorg-core. Unless I'm missing something, it's very much the same story as before. I don't see where the trouble is. The external monitor and its resolution are detected. But nothing is displayed on it. As mentioned before, I filed a bug report. No response to it as of yet. https://bugs.freedesktop.org/show_bug.cgi?id=28524 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.32-5-686 (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Tue Jun 1 04:59:47 UTC 2010 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] NSC Geode by NSC [0.00] Cyrix CyrixInstead [0.00] Centaur CentaurHauls [0.00] Transmeta GenuineTMx86 [0.00] Transmeta TransmetaCPU [0.00] UMC UMC UMC UMC [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009f000 (usable) [0.00] BIOS-e820: 0009f000 - 000a (reserved) [0.00] BIOS-e820: 0010 - 7ffd8000 (usable) [0.00] BIOS-e820: 7ffd8000 - 8000 (reserved) [0.00] BIOS-e820: e000 - f0007000 (reserved) [0.00] BIOS-e820: f0008000 - f000c000 (reserved) [0.00] BIOS-e820: fec0 - fec1 (reserved) [0.00] BIOS-e820: fed2 - fee1 (reserved) [0.00] BIOS-e820: ffb0 - 0001 (reserved) [0.00] DMI 2.3 present. [0.00] last_pfn = 0x7ffd8 max_arch_pfn = 0x10 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-C write-protect [0.00] D-E uncachable [0.00] F-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 0 mask F8000 write-back [0.00] 1 base 0FEDA mask E write-through [0.00] 2 disabled [0.00] 3 disabled [0.00] 4 disabled [0.00] 5 disabled [0.00] 6 disabled [0.00] 7 disabled [0.00] PAT not supported by CPU. [0.00] initial memory mapped : 0 - 0180 [0.00] init_memory_mapping: -373fe000 [0.00] 00 - 40 page 4k [0.00] 40 - 003700 page 2M [0.00] 003700 - 00373fe000 page 4k [0.00] kernel direct mapping tables up to 373fe000 @ 7000-d000 [0.00] RAMDISK: 3781a000 - 37fefcb3 [0.00] Allocated new RAMDISK: 0010 - 008d5cb3 [0.00] Move RAMDISK from 3781a000 - 37fefcb2 to 0010 - 008d5cb2 [0.00] ACPI: RSDP 000fc9b0 00014 (v00 DELL ) [0.00] ACPI: RSDT 7ffd8790 00040 (v01 DELLD05 27D60314 ASL 0061) [0.00] ACPI: FACP 7ffd9400 00074 (v01 DELLD05 27D60314 ASL 0061) [0.00] ACPI: DSDT 7ffda000 0355D (v01 INT430 SYSFexxx 1001 MSFT 010E) [0.00] ACPI: FACS 7ffe8800 00040 [0.00] ACPI: APIC 7ffd9c00 00068 (v01 DELLD05 27D60314 ASL 0047) [0.00] ACPI: ASF! 7ffd9800 0005B (v16 DELLD05 27D60314 ASL 0061) [0.00] ACPI: MCFG 7ffd9bc0 0003E (v16 DELLD05 27D60314 ASL 0061) [0.00] ACPI: SSDT 7ffd8be6 002C2 (v01 PmRef Cpu0Ist 3000 INTL 20030522) [0.00] ACPI: SSDT 7ffd8a0e 001D8 (v01 PmRef Cpu0Cst 3001 INTL 20030522) [0.00] ACPI: SSDT 7ffd8813 001FB (v01 PmRefCpuPm 3000 INTL 20030522) [0.00] ACPI: Local APIC address 0xfee0 [0.00] 1163MB HIGHMEM available. [0.00] 883MB LOWMEM available. [0.00] mapped low ram: 0 - 373fe000 [0.00] low ram: 0 - 373fe000 [0.00] node 0 low ram: - 373fe000 [0.00] node 0 bootmap 9000 - fe80 [0.00] (9 early reservations) == bootmem [00 - 00373fe000] [0.00] #0 [00 - 001000] BIOS data page == [00 - 001000] [0.00] #1 [001000 - 002000]EX TRAMPOLINE == [001000 - 002000] [0.00] #2 [006000 - 007000] TRAMPOLINE == [006000 - 007000] [0.00] #3 [000100 - 00014c3154]TEXT DATA BSS == [000100 - 00014c3154] [0.00] #4 [09f000 - 10]BIOS reserved == [09f000 -
Re: Upgrade Kernel, Lose External Display
On 06/12/2010 03:20 PM, Sven Joachim wrote: On 2010-06-12 21:06 +0200, Gilbert Sullivan wrote: I have both xserver-xorg-video-nouveau and xser-xorg-video-fbdev installed (just confirmed it in aptitude), but it doesn't appear that they are being used. I see. The latest xserver-xorg-core in sid uses nouveau by default, but that version is not in squeeze yet (and will take some time to migrate due to a dependency on a new libc6 on hppa). I did try using the 4-line minimal xorg.conf file suggested at the nouveau.freedesktop.org location to force nouveau to be used. When I booted I got a blue text-graphics screen which said that X had failed to start and which asked if I wanted to view the log (with a choice of yes / no). However, I didn't get a chance to answer because I was then unceremoniously dumped at the console logon prompt. I logged on as root and removed the 4-line file, and then everything was as it had been before. It would be quite interesting to view the log with nouveau used as the X driver. I would trying turning KMS off just to see if I could learn anything, but I haven't yet found out how to do it with a grub 2 system. You may as well blacklist nouveau then, since it is completely useless without KMS (the nouveau X driver requires KMS). Note, however, that without an xorg.conf the most recent xserver-xorg-core will still load the module. Sven Following upgrade of xserver-common and xserver-xorg-core from 2:1.7.7-1 to 2:1.7-2 this morning (06/14) the ensuing reboot saw the external DVI-connected LCD on the port replicator cease to function on *both* kernels, whether or not nouveau was blacklisted. It was failing at loading gdm on the new kernel, and I got the tty2 text graphics thing asking whether or not I wanted to see the xorg log (and not taking either a yes or no answer). Switching to tty1 enabled me to log on when booting with the old kernel and make configuration changes. I removed the blacklist nouveau entry from /etc/modprobe.d/blacklist.conf since the port replicator and external monitor are useless for now. Drivers now being shown by query: $ grep -B2 'Module class: X.Org Video Driver' /var/log/Xorg.0.log (II) Module nouveau: vendor=X.Org Foundation compiled for 1.7.7, module version = 0.0.15 Module class: X.Org Video Driver -- (II) Module nv: vendor=X.Org Foundation compiled for 1.7.7, module version = 2.1.17 Module class: X.Org Video Driver -- (II) Module vesa: vendor=X.Org Foundation compiled for 1.7.7, module version = 2.3.0 Module class: X.Org Video Driver The system with the built-in monitor behaves much better than it ever has before with Open Source drivers. Even with desktop compositing enabled in Xfce switching among applications and workspaces is instantaneous. But my external monitor and the port replicator are now useless to me. I guess I'll keep experimenting and watching the upgrades as they come along, hoping to be able to use my docked configuration again some time. Transitions can be interesting. Regards, Gil -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c16c3d0.2000...@comcast.net
Re: Upgrade Kernel, Lose External Display
On 06/12/2010 03:20 PM, Sven Joachim wrote: You may as well blacklist nouveau then, since it is completely useless without KMS (the nouveau X driver requires KMS). Note, however, that without an xorg.conf the most recent xserver-xorg-core will still load the module. I decided to take baby steps and do one thing at a time. I simply blacklisted nouveau in /etc/modprobe.d/blacklist.conf That solved the problem on this system. Didn't have to do anything like creating a /etc/modeprobe.d/nouveau-kms.conf file with modeset=0 in it or create an Xorg configuration file in /etc/X11 to load a specific driver. The Xorg.0.log is still showing both nv and vesa drivers. Not sure whether that's good or bad, but everything is working without me having to boot into the older kernel. I did file a bug on the 2D driver and will see if anything comes of that. Thank you very much for your help, Sven. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c14fad3.6090...@comcast.net
Re: Upgrade Kernel, Lose External Display
On 06/11/2010 04:30 PM, Andreas Rönnquist wrote: I've ran into this too, and got this solved by blacklisting the nouveau module in /etc/modprobe.d/blacklist.conf (adding a line containing just blacklist nouveau), and adding modeset=0 to my kernel line in /boot/grub/menu.lst (I am still on grub-legacy, don't know how it is done on grub-2 unfortunately) This made the system boot fine, but X didn't start before reinstalling the nvidia drivers. Doing so and rebooted I was in a functional X, just like before the upgrade of the kernel. I wanted to get back to you and thank you again, Andreas. A little research revealed that KMS could be turned off on this system using a modeset=0 line in /etc/modprobe.d/nouveau-kms.conf. However, that turned out to be unnecessary. I decided to do only one thing at a time and test. Adding the blacklist nouveau line to /etc/modprobe.d/blacklist.conf was all that was needed to give me my docked external display back when booting with the new kernel. The nouveau frame buffer is *not* used, apparently, if nouveau is blacklisted. My system is working well now with its odd (at least in my eyes) vesa/nv driver combination. I filed a bug with freedesktop.org and will see what comes of it. I do hope to be able to use the nouveau driver with this system eventually. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c14fc5d.4040...@comcast.net
Re: Upgrade Kernel, Lose External Display
On 2010-06-12 00:15 +0200, Gilbert Sullivan wrote: On 06/11/2010 03:08 PM, Sven Joachim wrote: On 2010-06-11 19:06 +0200, Gilbert Sullivan wrote: I undock from the port replicator and use the notebook's built-in 1920x1200 display, and the boot with the new kernel brings me to normal gdm login and then desktop. The only difference between appearance of boot using old kernel and new kernel is that, after the populating devices message, the text stops scrolling down the middle of the screen and starts scrolling down the left side. So I guess this is a video mode issue. I'm not sure I understand middle of the screen and left side, but the existing screen contents will be erased when nouveau is loaded. This is a notebook, and I have the video set in BIOS to not expand to fill the screen. So it uses and area that's something like 800x600 in the middle of the screen. It uses that small area for the scrolled messages at boot time all the way up until GDM is loaded -- that's when I'm using the old kernel -- with either the 1680x1050 DVI external LCD or the built-in 1920x1200 LCD. Thanks, I understand now. When using the new kernel with the external LCD, it just goes black after the /dev populated message. With the built-in LCD that's the point where it stops using the 800x600 area and starts using the entire screen for the scrolled messages. This is to be expected, because it detects and uses the display's native resolution. This is usually what you want, but you can override it with the video=800x600 boot parameter (or whatever other resolution you like). I booted the system connected to the port replicator and let it go to the black screen. I logged on to it via ssh and got the output of dmesg, which I'm attaching to this message as dmesg.txt. Thanks. I don't see anything unusual in it, in particular nouveau detects the 1680x1050 resolution of the external display: [7.308183] [drm] nouveau :01:00.0: allocated 1680x1050 fb: 0x49000, bo f6feb600 [7.319925] [drm] nouveau :01:00.0: Output DVI-D-1 is running on CRTC 0 using output A [7.319929] [drm] nouveau :01:00.0: Setting dpms mode 0 on tmds encoder (output 2) [7.319931] [drm] nouveau :01:00.0: Output DVI-D-1 is running on CRTC 0 using output A [7.321231] Console: switching to colour frame buffer device 210x65 If you want to report a bug upstream, please see http://nouveau.freedesktop.org/wiki/FrontPage#Bugs. Cheers, Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87zkz0isop@turtle.gmx.de
Re: Upgrade Kernel, Lose External Display
On 06/12/2010 04:03 AM, Sven Joachim wrote: This is to be expected, because it detects and uses the display's native resolution. This is usually what you want, but you can override it with the video=800x600 boot parameter (or whatever other resolution you like). Looks like I have a bit of searching and reading to do. I have just been blithely rolling along with all of the upgrades in Squeeze. Whereas I would have had an idea of how to go about this with grub I notice that a lot of things have changed between the changes in grub and the changes in the way video is handled. I booted the system connected to the port replicator and let it go to the black screen. I logged on to it via ssh and got the output of dmesg, which I'm attaching to this message as dmesg.txt. Thanks. I don't see anything unusual in it, in particular nouveau detects the 1680x1050 resolution of the external display: [7.308183] [drm] nouveau :01:00.0: allocated 1680x1050 fb: 0x49000, bo f6feb600 [7.319925] [drm] nouveau :01:00.0: Output DVI-D-1 is running on CRTC 0 using output A [7.319929] [drm] nouveau :01:00.0: Setting dpms mode 0 on tmds encoder (output 2) [7.319931] [drm] nouveau :01:00.0: Output DVI-D-1 is running on CRTC 0 using output A [7.321231] Console: switching to colour frame buffer device 210x65 Yes, I saw that and wondered why, if it's detecting the resolution properly, it isn't working. I guess the new frame buffer must be incompatible with the card's driver. I tried this: $ grep -B2 'Module class: X.Org Video Driver' /var/log/Xorg.0.log (II) Module nv: vendor=X.Org Foundation compiled for 1.7.7, module version = 2.1.17 Module class: X.Org Video Driver -- (II) Module vesa: vendor=X.Org Foundation compiled for 1.7.7, module version = 2.3.0 Module class: X.Org Video Driver I'm not sure I understand what's going on here. Does that say I'm using nv or vesa now? Whichever one I'm using doesn't seem to like the change. If you want to report a bug upstream, please see http://nouveau.freedesktop.org/wiki/FrontPage#Bugs. Cheers, Sven Yes, thank you, Sven. I think I will attempt to report a bug. I hope they won't mind a bug report from a dumb ox. I really appreciate your help. Regards, Gil -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c138ddd.4050...@comcast.net
Re: Upgrade Kernel, Lose External Display
On Fri, 2010-06-11 at 22:30 +0200, Andreas Rönnquist wrote: On Fri, 11 Jun 2010 13:06:04 -0400 Gilbert Sullivan whirly...@comcast.net wrote: Running Squeeze with Xfce desktop environment (only) on Dell Latitude D810. Nvidia video card running the VESA driver (though there's a bunch of verbiage in dmesg about nouveau). System is normally connected to a port replicator and DVI display (1680x1050). Upgraded from 2.6.32-3 to 2.6.32-6 this morning, saying yes to reconfiguration. Upon reboot I see the normal scrolling of messages in the middle of the screen, but (after populating devices message) the screen goes black. -8-- Many thanks for clues. Hi! I've ran into this too, and got this solved by blacklisting the nouveau module in /etc/modprobe.d/blacklist.conf (adding a line containing just blacklist nouveau), and adding modeset=0 to my kernel line in /boot/grub/menu.lst (I am still on grub-legacy, don't know how it is done on grub-2 unfortunately) This made the system boot fine, but X didn't start before reinstalling the nvidia drivers. Doing so and rebooted I was in a functional X, just like before the upgrade of the kernel. best regards -- Andreas Rönnquist gus...@gusnan.se Thank you Andres :) I experienced a similar problem after upgrading to a new kernel today in squeeze, I noticed the resolution of the screen in text-mode had changed, and X wouldn't load. Since it was a kernel update, I'd figure I would recompile my nvidia driver modules (proprietary nvidia driver). The nvidia installer failed however and looking on this list I saw your message, blacklisting nouveau allows me to load the nvidia driver again (I need some of it's features, nouveau doesn't handle my setup very well yet, mostly 3D acceleration). It looks to me like the nouveau module is conflicting with (any?) other drivers. Regards, Steven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1276360896.2710.8.ca...@portable-steven.lan
Re: Upgrade Kernel, Lose External Display
On 2010-06-12 15:38 +0200, Gilbert Sullivan wrote: On 06/12/2010 04:03 AM, Sven Joachim wrote: Thanks. I don't see anything unusual in it, in particular nouveau detects the 1680x1050 resolution of the external display: [7.308183] [drm] nouveau :01:00.0: allocated 1680x1050 fb: 0x49000, bo f6feb600 [7.319925] [drm] nouveau :01:00.0: Output DVI-D-1 is running on CRTC 0 using output A [7.319929] [drm] nouveau :01:00.0: Setting dpms mode 0 on tmds encoder (output 2) [7.319931] [drm] nouveau :01:00.0: Output DVI-D-1 is running on CRTC 0 using output A [7.321231] Console: switching to colour frame buffer device 210x65 Yes, I saw that and wondered why, if it's detecting the resolution properly, it isn't working. I guess the new frame buffer must be incompatible with the card's driver. Nouveau _is_ the card's driver. Or are you talking about X.Org? I tried this: $ grep -B2 'Module class: X.Org Video Driver' /var/log/Xorg.0.log (II) Module nv: vendor=X.Org Foundation compiled for 1.7.7, module version = 2.1.17 Module class: X.Org Video Driver -- (II) Module vesa: vendor=X.Org Foundation compiled for 1.7.7, module version = 2.3.0 Module class: X.Org Video Driver I'm not sure I understand what's going on here. Does that say I'm using nv or vesa now? Both will not work correctly, and the newest versions of these drivers will refuse to load if nouveau is present. You need to install xserver-xorg-video-nouveau or xserver-xorg-video-fbdev, those are the only X drivers that work with the nouveau kernel module. Whichever one I'm using doesn't seem to like the change. Does X even start? I suppose it doesn't if you only have the nv and vesa drivers. Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87k4q4cfky@turtle.gmx.de
Re: Upgrade Kernel, Lose External Display
On 06/12/2010 01:42 PM, Sven Joachim wrote: On 2010-06-12 15:38 +0200, Gilbert Sullivan wrote: On 06/12/2010 04:03 AM, Sven Joachim wrote: Thanks. I don't see anything unusual in it, in particular nouveau detects the 1680x1050 resolution of the external display: [7.308183] [drm] nouveau :01:00.0: allocated 1680x1050 fb: 0x49000, bo f6feb600 [7.319925] [drm] nouveau :01:00.0: Output DVI-D-1 is running on CRTC 0 using output A [7.319929] [drm] nouveau :01:00.0: Setting dpms mode 0 on tmds encoder (output 2) [7.319931] [drm] nouveau :01:00.0: Output DVI-D-1 is running on CRTC 0 using output A [7.321231] Console: switching to colour frame buffer device 210x65 Yes, I saw that and wondered why, if it's detecting the resolution properly, it isn't working. I guess the new frame buffer must be incompatible with the card's driver. Nouveau _is_ the card's driver. Or are you talking about X.Org? I tried this: $ grep -B2 'Module class: X.Org Video Driver' /var/log/Xorg.0.log (II) Module nv: vendor=X.Org Foundation compiled for 1.7.7, module version = 2.1.17 Module class: X.Org Video Driver -- (II) Module vesa: vendor=X.Org Foundation compiled for 1.7.7, module version = 2.3.0 Module class: X.Org Video Driver I'm not sure I understand what's going on here. Does that say I'm using nv or vesa now? Both will not work correctly, and the newest versions of these drivers will refuse to load if nouveau is present. You need to install xserver-xorg-video-nouveau or xserver-xorg-video-fbdev, those are the only X drivers that work with the nouveau kernel module. I have both xserver-xorg-video-nouveau and xser-xorg-video-fbdev installed (just confirmed it in aptitude), but it doesn't appear that they are being used. I did try using the 4-line minimal xorg.conf file suggested at the nouveau.freedesktop.org location to force nouveau to be used. When I booted I got a blue text-graphics screen which said that X had failed to start and which asked if I wanted to view the log (with a choice of yes / no). However, I didn't get a chance to answer because I was then unceremoniously dumped at the console logon prompt. I logged on as root and removed the 4-line file, and then everything was as it had been before. I would trying turning KMS off just to see if I could learn anything, but I haven't yet found out how to do it with a grub 2 system. Whichever one I'm using doesn't seem to like the change. Does X even start? I suppose it doesn't if you only have the nv and vesa drivers. X apparently *always* starts (except for the one time when I tried to specify use of nouveau in /etc/X11/xorg.conf). I'm showing the nv and vesa drivers in the log in both situations (docked and undocked, new kernel and old kernel). When I'm undocked and using the 1920x1200 display I can boot with the new kernel and everything works perfectly. When I'm docked, booting the new kernel, and using the 1680x1050 display all I get after the waiting for /dev to be populated message is a black screen (on the external display). I just tried lifting the lid of the notebook while it was docked (hard to do because of the physical location of the port replicator) and saw that it, too, was black. When I lifted it further I saw the backlight come on, but no information was being displayed on the screen. I tried using the keyboard toggle to force the external screen to be used, but nothing happened. I logged on to the notebook remotely again and was able to launch graphical applications on the system in the ssh -X session. It looks to me as though X is always loaded, but that something about the new KMS (or whatever it is) doesn't like my docked hardware configuration and won't allow output to any screen when the system is docked. (I may be guilty of assuming more than I should, but I'll admit I'm pretty ignorant of the way all of this stuff works these days.) I'm looking at the link you gave me to see if I can file a meaningful bug report, but so much of the documentation there concerns the process of getting nouveau to work at a time before all of the new packages were released that I'm not sure I know how to proceed without merely making a pest of myself. In the meantime, I boot with the old kernel when docked and the new kernel when undocked, and the system behaves perfectly. I'll keep chipping away at it in the hope of learning something useful or posting a reasonably meaningful bug report. If you have any suggestions regarding testing that I might do I'm willing to give it a shot. I'm wondering what would happen if I performed a fresh installation of Squeeze on the system. But I would *much* rather learn why it's behaving the way it is. I should point out that I have never used proprietary nvidia drivers on this system since the beginning of this netinst of Squeeze. And, as far as I knew, I was using the vesa drivers
Re: Upgrade Kernel, Lose External Display
On 2010-06-12 21:06 +0200, Gilbert Sullivan wrote: I have both xserver-xorg-video-nouveau and xser-xorg-video-fbdev installed (just confirmed it in aptitude), but it doesn't appear that they are being used. I see. The latest xserver-xorg-core in sid uses nouveau by default, but that version is not in squeeze yet (and will take some time to migrate due to a dependency on a new libc6 on hppa). I did try using the 4-line minimal xorg.conf file suggested at the nouveau.freedesktop.org location to force nouveau to be used. When I booted I got a blue text-graphics screen which said that X had failed to start and which asked if I wanted to view the log (with a choice of yes / no). However, I didn't get a chance to answer because I was then unceremoniously dumped at the console logon prompt. I logged on as root and removed the 4-line file, and then everything was as it had been before. It would be quite interesting to view the log with nouveau used as the X driver. I would trying turning KMS off just to see if I could learn anything, but I haven't yet found out how to do it with a grub 2 system. You may as well blacklist nouveau then, since it is completely useless without KMS (the nouveau X driver requires KMS). Note, however, that without an xorg.conf the most recent xserver-xorg-core will still load the module. Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/878w6kcb1q@turtle.gmx.de
Re: Upgrade Kernel, Lose External Display
On 06/12/2010 03:20 PM, Sven Joachim wrote: On 2010-06-12 21:06 +0200, Gilbert Sullivan wrote: I have both xserver-xorg-video-nouveau and xser-xorg-video-fbdev installed (just confirmed it in aptitude), but it doesn't appear that they are being used. I see. The latest xserver-xorg-core in sid uses nouveau by default, but that version is not in squeeze yet (and will take some time to migrate due to a dependency on a new libc6 on hppa). Okay, that's beginning to make a little sense now. I thought that I had read that nouveau was going to be the new default once xserver-xorg-core was updated. I saw an update to that package in the beginning of May and assumed (apparently wrongly) that it was the version that was going to make nouveau the default. I could see that I wasn't using nouveau, but I wasn't concerned because everything was working. I did try using the 4-line minimal xorg.conf file suggested at the nouveau.freedesktop.org location to force nouveau to be used. When I booted I got a blue text-graphics screen which said that X had failed to start and which asked if I wanted to view the log (with a choice of yes / no). However, I didn't get a chance to answer because I was then unceremoniously dumped at the console logon prompt. I logged on as root and removed the 4-line file, and then everything was as it had been before. It would be quite interesting to view the log with nouveau used as the X driver. I'll try reinstating the 4-liner configuration file and then get the dmesg output again. I would trying turning KMS off just to see if I could learn anything, but I haven't yet found out how to do it with a grub 2 system. You may as well blacklist nouveau then, since it is completely useless without KMS (the nouveau X driver requires KMS). Note, however, that without an xorg.conf the most recent xserver-xorg-core will still load the module. Sven I think I'm losing my way here. Am I correct in thinking that I have to do both (turn off KMS and blacklist nouveau). I figured that this would then leave me with vesa as my driver. Do I need to also create an xorg.conf file that specifies vesa as my driver? I'll do some tinkering and see what happens. I still haven't found out how to turn KMS off on this system. I've tried searching on kernel mode setting and various other terms, but all I ever find is information on how to turn it *on* on systems where it isn't the default. So far, the articles on that haven't been helpful to me in figuring out how to turn it off on a system where it is the default. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c13e8e8.6030...@comcast.net
Upgrade Kernel, Lose External Display
Running Squeeze with Xfce desktop environment (only) on Dell Latitude D810. Nvidia video card running the VESA driver (though there's a bunch of verbiage in dmesg about nouveau). System is normally connected to a port replicator and DVI display (1680x1050). Upgraded from 2.6.32-3 to 2.6.32-6 this morning, saying yes to reconfiguration. Upon reboot I see the normal scrolling of messages in the middle of the screen, but (after populating devices message) the screen goes black. After the system stops accessing the HD I use the power button to shut down. (System is configured to shut down when power button is pressed.) I reboot with old kernel. Everything goes normally, of course. I undock from the port replicator and use the notebook's built-in 1920x1200 display, and the boot with the new kernel brings me to normal gdm login and then desktop. The only difference between appearance of boot using old kernel and new kernel is that, after the populating devices message, the text stops scrolling down the middle of the screen and starts scrolling down the left side. So I guess this is a video mode issue. What with all of the recent changes in the way video is handled (and an aging brain) I gave up months ago on keeping up with changes in the video functions of the system. I was going to wait for the dust to settle and then learn how video works after the migration' (or whatever you call it) is complete. I guess I don't have that luxury now. Can someone point me at documentation so I can try to figure out how to deal with this? (I'd like to use the new kernel. I try to keep my system as up-to-date as possible.) Many thanks for clues. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c126cfc.3020...@comcast.net
Re: Upgrade Kernel, Lose External Display
On 2010-06-11 19:06 +0200, Gilbert Sullivan wrote: Running Squeeze with Xfce desktop environment (only) on Dell Latitude D810. Nvidia video card running the VESA driver (though there's a bunch of verbiage in dmesg about nouveau). System is normally connected to a port replicator and DVI display (1680x1050). The new kernel has a new framebuffer driver called nouveau that is (usually) autoloaded by udev and replaces the vesa framebuffer driver. Upon reboot I see the normal scrolling of messages in the middle of the screen, but (after populating devices message) the screen goes black. Ouch. There have been several such reports, but as none of the developers seems to be able to reproduce them, there is not much progress in this area. After the system stops accessing the HD I use the power button to shut down. (System is configured to shut down when power button is pressed.) I reboot with old kernel. Everything goes normally, of course. I undock from the port replicator and use the notebook's built-in 1920x1200 display, and the boot with the new kernel brings me to normal gdm login and then desktop. The only difference between appearance of boot using old kernel and new kernel is that, after the populating devices message, the text stops scrolling down the middle of the screen and starts scrolling down the left side. So I guess this is a video mode issue. I'm not sure I understand middle of the screen and left side, but the existing screen contents will be erased when nouveau is loaded. What with all of the recent changes in the way video is handled (and an aging brain) I gave up months ago on keeping up with changes in the video functions of the system. I was going to wait for the dust to settle and then learn how video works after the migration' (or whatever you call it) is complete. I guess I don't have that luxury now. Can someone point me at documentation so I can try to figure out how to deal with this? (I'd like to use the new kernel. I try to keep my system as up-to-date as possible.) Please send the dmesg output. If possible, connect to the machine via ssh when the port replicator is docked in. Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/877hm5v133@turtle.gmx.de
Re: Upgrade Kernel, Lose External Display
On Fri, 11 Jun 2010 13:06:04 -0400 Gilbert Sullivan whirly...@comcast.net wrote: Running Squeeze with Xfce desktop environment (only) on Dell Latitude D810. Nvidia video card running the VESA driver (though there's a bunch of verbiage in dmesg about nouveau). System is normally connected to a port replicator and DVI display (1680x1050). Upgraded from 2.6.32-3 to 2.6.32-6 this morning, saying yes to reconfiguration. Upon reboot I see the normal scrolling of messages in the middle of the screen, but (after populating devices message) the screen goes black. -8-- Many thanks for clues. Hi! I've ran into this too, and got this solved by blacklisting the nouveau module in /etc/modprobe.d/blacklist.conf (adding a line containing just blacklist nouveau), and adding modeset=0 to my kernel line in /boot/grub/menu.lst (I am still on grub-legacy, don't know how it is done on grub-2 unfortunately) This made the system boot fine, but X didn't start before reinstalling the nvidia drivers. Doing so and rebooted I was in a functional X, just like before the upgrade of the kernel. best regards -- Andreas Rönnquist gus...@gusnan.se -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100611223016.ae55d14e.gus...@gusnan.se
Re: Upgrade Kernel, Lose External Display
On 06/11/2010 03:08 PM, Sven Joachim wrote: On 2010-06-11 19:06 +0200, Gilbert Sullivan wrote: Running Squeeze with Xfce desktop environment (only) on Dell Latitude D810. Nvidia video card running the VESA driver (though there's a bunch of verbiage in dmesg about nouveau). System is normally connected to a port replicator and DVI display (1680x1050). The new kernel has a new framebuffer driver called nouveau that is (usually) autoloaded by udev and replaces the vesa framebuffer driver. Thank you for that information. I suspected that the change to nouveau might be involved in some way. Upon reboot I see the normal scrolling of messages in the middle of the screen, but (after populating devices message) the screen goes black. Ouch. There have been several such reports, but as none of the developers seems to be able to reproduce them, there is not much progress in this area. I can reproduce it for them! ;) After the system stops accessing the HD I use the power button to shut down. (System is configured to shut down when power button is pressed.) I reboot with old kernel. Everything goes normally, of course. I undock from the port replicator and use the notebook's built-in 1920x1200 display, and the boot with the new kernel brings me to normal gdm login and then desktop. The only difference between appearance of boot using old kernel and new kernel is that, after the populating devices message, the text stops scrolling down the middle of the screen and starts scrolling down the left side. So I guess this is a video mode issue. I'm not sure I understand middle of the screen and left side, but the existing screen contents will be erased when nouveau is loaded. This is a notebook, and I have the video set in BIOS to not expand to fill the screen. So it uses and area that's something like 800x600 in the middle of the screen. It uses that small area for the scrolled messages at boot time all the way up until GDM is loaded -- that's when I'm using the old kernel -- with either the 1680x1050 DVI external LCD or the built-in 1920x1200 LCD. When using the new kernel with the external LCD, it just goes black after the /dev populated message. With the built-in LCD that's the point where it stops using the 800x600 area and starts using the entire screen for the scrolled messages. What with all of the recent changes in the way video is handled (and an aging brain) I gave up months ago on keeping up with changes in the video functions of the system. I was going to wait for the dust to settle and then learn how video works after the migration' (or whatever you call it) is complete. I guess I don't have that luxury now. Can someone point me at documentation so I can try to figure out how to deal with this? (I'd like to use the new kernel. I try to keep my system as up-to-date as possible.) Please send the dmesg output. If possible, connect to the machine via ssh when the port replicator is docked in. Sven Thank you, Sven. I booted the system connected to the port replicator and let it go to the black screen. I logged on to it via ssh and got the output of dmesg, which I'm attaching to this message as dmesg.txt. [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.32-5-686 (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Tue Jun 1 04:59:47 UTC 2010 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] NSC Geode by NSC [0.00] Cyrix CyrixInstead [0.00] Centaur CentaurHauls [0.00] Transmeta GenuineTMx86 [0.00] Transmeta TransmetaCPU [0.00] UMC UMC UMC UMC [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009f000 (usable) [0.00] BIOS-e820: 0009f000 - 000a (reserved) [0.00] BIOS-e820: 0010 - 7ffd8000 (usable) [0.00] BIOS-e820: 7ffd8000 - 8000 (reserved) [0.00] BIOS-e820: e000 - f0007000 (reserved) [0.00] BIOS-e820: f0008000 - f000c000 (reserved) [0.00] BIOS-e820: fec0 - fec1 (reserved) [0.00] BIOS-e820: fed2 - fee1 (reserved) [0.00] BIOS-e820: ffb0 - 0001 (reserved) [0.00] DMI 2.3 present. [0.00] last_pfn = 0x7ffd8 max_arch_pfn = 0x10 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-C write-protect [0.00] D-E uncachable [0.00] F-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 0 mask F8000 write-back [
Re: Upgrade Kernel, Lose External Display
On 06/11/2010 04:30 PM, Andreas Rönnquist wrote: On Fri, 11 Jun 2010 13:06:04 -0400 Gilbert Sullivanwhirly...@comcast.net wrote: Running Squeeze with Xfce desktop environment (only) on Dell Latitude D810. Nvidia video card running the VESA driver (though there's a bunch of verbiage in dmesg about nouveau). System is normally connected to a port replicator and DVI display (1680x1050). Upgraded from 2.6.32-3 to 2.6.32-6 this morning, saying yes to reconfiguration. Upon reboot I see the normal scrolling of messages in the middle of the screen, but (after populating devices message) the screen goes black. -8-- Many thanks for clues. Hi! I've ran into this too, and got this solved by blacklisting the nouveau module in /etc/modprobe.d/blacklist.conf (adding a line containing just blacklist nouveau), and adding modeset=0 to my kernel line in /boot/grub/menu.lst (I am still on grub-legacy, don't know how it is done on grub-2 unfortunately) This made the system boot fine, but X didn't start before reinstalling the nvidia drivers. Doing so and rebooted I was in a functional X, just like before the upgrade of the kernel. best regards Many thanks for this information, Andreas. I'll study the possibility of blacklisting nouveau, but it sounds like I'll have to overcome two issues to make use of it. First, I'm using grub 2. Second, I've learned the hard way that this system does not get along with the nvidia proprietary drivers. (That's why I've been using vesa. Vesa has been slow, but absolutely rock solid for me.) Again, many thanks. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c12b6f9.7050...@comcast.net
Re: how can I upgrade kernel in etch
On Sunday 06 June 2010 17:06:25 Long Wind wrote: I have etch which use kernel 2.6.18-6 I want to upgrade it to kernel 2.6.24 or later but it doesn't contain it: deb http://http.us.debian.org/debian etch main Where can I find new kernel images in Debian packages? Suggestions so far: 1. Install linux-image-2.6.-$arch. You probably already have this installed; on Etch it is the 2.6.18 kernel plus some backported fixes. 2. Use Etch backports. Note that using Etch backports at this point means you might not have a clear upgrade path to Lenny without also including Lenny backports. Also, backports isn't (yet) an official part of the stable infrastructure. 3. Upgrade to Lenny. It is (well past) time to consider this. Security support for Etch has run out or will run out very soon. Lenny has been stable for quite some time now; in fact a freeze for Squeeze is currently in the works. Waiting for Squeeze to become stable doesn't save you any work, either -- a Etch - Squeeze upgrade isn't supported; you'd have to do an intermediate upgrade to Lenny anyway. My suggestion: Install linux-image-2.6-$arch-etchnhalf. During the lifetime of Etch, the release team admitted that 2.6.18 was simply not new enough even for Debian stable, at least for some users. Because of this, they provided Etch-and-a- half kernels that are 2.6.24, but did not bump linux-image-$arch, since that would have forced a kernel upgrade on users that were satisfied with 2.6.18. Upgrades from -etchnhalf kernels (to Lenny, which has 2.6.26 in linux- image-2.6-$arch) are supported, but the -etchnhalf kernel may need to be manually uninstalled after the upgrade completes. An -etchnhalf kernel is a temporary fix. It is likely that your current Etch installs have known security vulnerabilities that will not be addressed by Debian. You should upgrade to Lenny, ASAP. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
how can I upgrade kernel in etch
I have etch which use kernel 2.6.18-6 I want to upgrade it to kernel 2.6.24 or later but it doesn't contain it: deb http://http.us.debian.org/debian etch main Where can I find new kernel images in Debian packages? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktinfdise2xcnyofnipxq_wtlll1qmeqctojtz...@mail.gmail.com
Re: how can I upgrade kernel in etch
On 7 June 2010 07:36, Long Wind longwind2...@gmail.com wrote: I have etch which use kernel 2.6.18-6 I want to upgrade it to kernel 2.6.24 or later but it doesn't contain it: deb http://http.us.debian.org/debian etch main Where can I find new kernel images in Debian packages? have you had a look into Debian backports[1] quick search revealed 2.6.26 kernel[2] has been back ported to etch Regards Dale [1] http://www.backports.org/dokuwiki/doku.php [2] http://packages.debian.org/search?keywords=linux-image-2.6searchon=namessection=allsuite=etch-backports -- [WWW] http://quail.southernvaleslug.org/ The significant problems we face cannot be solved at the same level of thinking we were at when we created them - Albert Einstein -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktim_vcugnof8ior7ns-qbzdzxqh-0mebtgqh0...@mail.gmail.com
Re: how can I upgrade kernel in etch
You could install a package like: linux-image-2.6-your architecture what this does is depends on the latest Linux kernel 2.6 and modules. In other words if you have this installed it will always have the latest kernel there too. You might not want that. -- C -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100606202527.6cdd7...@mondo
Re: how can I upgrade kernel in etch
On Sun, 06 Jun 2010 18:06:25 -0400 (EDT), Long Wind longwind2...@gmail.com wrote: I have etch which use kernel 2.6.18-6 I want to upgrade it to kernel 2.6.24 or later but it doesn't contain it: deb http://http.us.debian.org/debian etch main Where can I find new kernel images in Debian packages? You have three main options: (1) Upgrade Etch to Lenny. Follow the upgrade instructions in the release notes for Lenny. (2) Install Lenny over the top of your Etch system, formatting the partitions during the install. Obviously you will lose all files on the partitions that you format when you do this, so think carefully before you do this. At a minimum, you should have /home on a separate partition and not format that partition, so that you don't lose user files (except files belonging to root). (3) Install a newer kernel from Etch backports. There is actually a fourth option, namely installing a kernel from Lenny on your Etch system, but I don't recommend that. Etch is now the oldstable release, so I recommend options (1) or (2). -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/394883158.343386.1275872726361.javamail.r...@md01.wow.synacor.com
(solved)Re: how can I upgrade kernel in etch
Thank Dale, Charles Kroeger and Stephen Powell! I will install from backports. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktilhgiwaquboc_q1sqvsly5f4kbbhrdeegjiq...@mail.gmail.com
Cannot upgrade kernel
I have been going around in circles on this. I am trying to upgrade my kernel from 2.2.20 to the current stable kernel 2.6.18. When I run aptitude I get a glibc error because it needs at least a 2.4.1 kernel to install but the new kernel won't install without the new glibc. Here is what is happening. I am entering: aptitude install linux-image-2.6.18-6-686 After the usual output I get this: preparing to replace libc6 2.3.2.ds1-22sarge3 (using .../libc6_2.3.6.ds1-13etch7i386.deb) ... Then I get notices that I need to turn off daemons like xdm, kdm, xscreensaver all of which are off or not installed. And then it asks: Do you want to upgrade glibc now? [Y/n] After I select Y I get this message: WARNING: This version of glibc requires that you be running kernel version 2.4.1 or later. . . dpkg: error processing /var/cache/apt/archives/lib6_2.3.6.ds1-13etch7_i386.deb --unpack): subprocess pre-installation script returned error exit status 1 Then the whole thing bombs. I have tried an aptitude dist-upgrade and that did not work. Same error messages. I tried putting a hold on glibc but that didn't work either. Even tried the -f parameter with aptitude with no success. Anyone know a way around this so I can to get the kernel upgraded? Thanks, Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cannot upgrade kernel
I was afraid that I was going to have to reinstall the system. You are right. This is an old system that has not been upgraded in quite some time. Thanks, Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cannot upgrade kernel
On Wed, Nov 12, 2008 at 06:17:23AM -0800, Brian Kimsey-Hickman wrote: I have been going around in circles on this. I am trying to upgrade my kernel from 2.2.20 to the current stable kernel 2.6.18. When I run aptitude I get a glibc error because it needs at least a 2.4.1 kernel to install but the new kernel won't install without the new glibc. You seem to be upgrading system from very old stable to lenny. You can not skip stable release and each step upgrade needs attention described in each release note issed for each stable release. It is usualy eaier to install new system in such case, You must make sure to backup your current system first. http://people.debian.org/~osamu/pub/getwiki/html/ch03.en.html#systemwideupgradewithaptitude Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cannot upgrade kernel
On Wed, 12 Nov 2008 06:42:39 -0800 (PST) Brian Kimsey-Hickman [EMAIL PROTECTED] wrote: I was afraid that I was going to have to reinstall the system. You are right. This is an old system that has not been upgraded in quite some time. Well, you can try to upgrade, but as said, you cannot skip releases. If it works, it's fine, if it doesn't, you can still reinstall. However, reinstalling can be an advantage --- or a lot of work ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cannot upgrade kernel
--- On Wed, 11/12/08, Sven Joachim [EMAIL PROTECTED] wrote: From: Sven Joachim [EMAIL PROTECTED] Subject: Re: Cannot upgrade kernel To: debian-user@lists.debian.org Date: Wednesday, November 12, 2008, 9:59 AM On 2008-11-12 15:17 +0100, Brian Kimsey-Hickman wrote: I have been going around in circles on this. I am trying to upgrade my kernel from 2.2.20 to the current stable kernel 2.6.18. When I run aptitude I get a glibc error because it needs at least a 2.4.1 kernel to install but the new kernel won't install without the new glibc. You need to upgrade your kernel before you can upgrade to etch. Replace your ancient woody kernel with a newer one from sarge. Anyone know a way around this so I can to get the kernel upgraded? Download a sarge kernel, e.g. this one: http://archive.debian.net/sarge/kernel-image-2.4.27-2-686 and all its dependencies. Install the packages with dpkg -i, update your bootloader and reboot. If you run into dependency problems, point your sources.list to sarge: deb http://archive.debian.org/debian/ sarge main Then, after apt-get update you can install a sarge kernel without problems. Sven -- Thanks. I probably should have followed that advice. What I ended up doing was copying an old 2.4.18 kernel from a similar system. Edited lilo.conf and ran lilo and believe it or not got the system to boot. Then I ran aptitude dist-upgrade and it took. I could hardly believe it. Most definitely not the preferred method but I got lucky in this case. Thanks everyone for you input. Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cannot upgrade kernel
On 2008-11-12 15:17 +0100, Brian Kimsey-Hickman wrote: I have been going around in circles on this. I am trying to upgrade my kernel from 2.2.20 to the current stable kernel 2.6.18. When I run aptitude I get a glibc error because it needs at least a 2.4.1 kernel to install but the new kernel won't install without the new glibc. You need to upgrade your kernel before you can upgrade to etch. Replace your ancient woody kernel with a newer one from sarge. Anyone know a way around this so I can to get the kernel upgraded? Download a sarge kernel, e.g. this one: http://archive.debian.net/sarge/kernel-image-2.4.27-2-686 and all its dependencies. Install the packages with dpkg -i, update your bootloader and reboot. If you run into dependency problems, point your sources.list to sarge: deb http://archive.debian.org/debian/ sarge main Then, after apt-get update you can install a sarge kernel without problems. Sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dist-upgrade does not upgrade kernel on one of the Sarge machines even with correct source.list
On Thu, Oct 04, 2007 at 10:11:55PM +0530, Siju George wrote: Hi, One of the sarge machines runs and older kernel and apt-get dist-upgrade does not install the newer kernel. Could some one please help me trouble shoot this? debian:~# uname -a Linux debian 2.6.8-11-amd64-k8 #1 Sat Jul 1 12:02:45 UTC 2006 x86_64 GNU/Linux debian:~# apt-get update 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. debian:~# where as the newer Sarge kernel is Linux debian 2.6.8-13-amd64-k8 #1 Sat Jun 9 16:52:03 UTC 2007 x86_64 GNU/Linux What kernel packages do you have installed? If you don't have a kernel-metapackage that always depends on the newest kernel, then you won't get the newer kernel. Look at what packages depend on the newer kernel. At least one will be a kernel meta-package. Install the one that always depends on the newest kernel. For example, on my Etch box, I have: linux-image-amd64, which depends on: linux-image-2.6-amd64, which depends on: linux-image-2.6.18.5-amd64 This will mean that I will always have the most recent kernel automatically selected, even if it jumps to linux-image-2.8. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dist-upgrade does not upgrade kernel on one of the Sarge machines even with correct source.list
Hi, One of the sarge machines runs and older kernel and apt-get dist-upgrade does not install the newer kernel. Could some one please help me trouble shoot this? = debian:~# uname -a Linux debian 2.6.8-11-amd64-k8 #1 Sat Jul 1 12:02:45 UTC 2006 x86_64 GNU/Linux debian:~# apt-get update Hit http://mirror.espri.arizona.edu sarge/main Packages Hit http://mirror.espri.arizona.edu sarge/main Release Hit http://mirror.espri.arizona.edu sarge/main Sources Hit http://mirror.espri.arizona.edu sarge/main Release Hit http://security.debian.org sarge/updates/main Packages Hit http://security.debian.org sarge/updates/main Release Reading Package Lists... Done debian:~# apt-get dist-upgrade Reading Package Lists... Done Building Dependency Tree... Done Calculating Upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. debian:~# === where as the newer Sarge kernel is Linux debian 2.6.8-13-amd64-k8 #1 Sat Jun 9 16:52:03 UTC 2007 x86_64 GNU/Linux Thank you so much :-) Kind Regards Siju -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Safe way to upgrade kernel?
# apt-get install newer-kernel sometimes complains that it will not upgrade the running kernel. So, what is the correct way to upgrade kernel image? -ishwar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Safe way to upgrade kernel?
On Thu, Dec 21, 2006 at 11:31:15AM -0500, Ishwar Rattan wrote: # apt-get install newer-kernel sometimes complains that it will not upgrade the running kernel. So, what is the correct way to upgrade kernel image? what is the exact message? I know it complains that it IS updating the running kernel and that this means the modules have changed and you need to reboot. Is this what you're seeing? A signature.asc Description: Digital signature
Re: Safe way to upgrade kernel?
Ishwar Rattan wrote: # apt-get install newer-kernel sometimes complains that it will not upgrade the running kernel. So, what is the correct way to upgrade kernel image? That's correct, that's the right way. What's the exact message you're getting? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
How upgrade kernel 2.4.31 on dell server?
I've got two powerdege 2850 with 5 disks to configure:) I've installed the iso debian-dell-2.4.31.iso downloaded from http://staff.osuosl.org/~kveton/debian/debian-dell-2.4.31.iso. The installation has been very smooth, the problems arised when I tried to upgrade to the latest kernel available in backports. I have tried different combinations and I always get I have been able to find a suitable tool for generating initrd images, Anybody know how to solve this? Thank you very much -- Arnau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How upgrade kernel 2.4.31 on dell server?
Arnau wrote, On 2006-09-15 07:38: I've got two powerdege 2850 with 5 disks to configure:) I've installed the iso debian-dell-2.4.31.iso downloaded from http://staff.osuosl.org/~kveton/debian/debian-dell-2.4.31.iso. The installation has been very smooth, the problems arised when I tried to upgrade to the latest kernel available in backports. I have tried different combinations and I always get I have been able to find a suitable tool for generating initrd images, Anybody know how to solve this? Thank you very much I believe that you need initramfs-tools or yaird for generating an initrd for the new kernel. Arthur. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[RESOLVIDO] Re: Problemas apos upgrade: Kernel Panic
Ola Marcos, Eu dei boot com um live cd, depois um chroot e mandei um apt-get update apt-get upgrade e ele atualizou o initrd-tools (nao tenho certeza se o nome e esse mesmo) e tudo voltou ao normal, ou seja, sua suposicao estava correta. Marcelo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problemas apos upgrade: Kernel Panic
Ola, Ontem eu fiz um dist-upgrade e hoje meu micro nao sobe. Recebo a seguinte mensagem no inicio do boot: INPUT: at tRANLATED SET 2 KEYBOARD AS /CLASS/INPUT/INPUT0 RAMDISK: incomplet write (-28 !=32768) 8388608 INVALID compressed format (err=1) VFS: Cannot open root device 305 or unknown-block(3,5) Please append a correct root= boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,5) Eu me lembro que durante a atualizacao deu um erro quando estava instalando o ram(alguma coisa). Alguma sugestao? Obrigado Marcelo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problemas apos upgrade: Kernel Panic
Marcelo Luiz de Laia schrieb: Ola, Ontem eu fiz um dist-upgrade e hoje meu micro nao sobe. Recebo a seguinte mensagem no inicio do boot: INPUT: at tRANLATED SET 2 KEYBOARD AS /CLASS/INPUT/INPUT0 RAMDISK: incomplet write (-28 !=32768) 8388608 INVALID compressed format (err=1) VFS: Cannot open root device 305 or unknown-block(3,5) Please append a correct root= boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,5) Eu me lembro que durante a atualizacao deu um erro quando estava instalando o ram(alguma coisa). Bom... sempre tenha um kernel de backup p/ essas emergências Vc mudou o esquema de particionamento do HD? De qualquer maneira, parece que o seu initrd não está ok... só reinstalando o pacote do kernel-image (ou linux-image) novamente... Vc tem algum CD de boot? -- Marcos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get upgrade - kernel-image
On Sat, December 17, 2005 23:37, Josh King said: Ernst-Magne Vindal wrote: Hi, not sure this is a problem but I'll like to check anyway. When doing apt-get upgrade the only package listed for upgrade is the kernel image. this is working fine and I'm not sure what the upgrade will do. The sources list say stable. I got a few packages from unstable, but apt is configured to default stable. Why will apt upgrade the kernel? The installed ver. is ii kernel-image-2.6.8-2-386 2.6.8-16 and the same version no. is the one to upgrade. Can I instead hold the kernel-image? It is a security update: http://lists.debian.org/debian-security-announce/debian-security-announce-2005/msg00323.html I would advise performing the installation. -- http://debianhomepage.org http://debcentral.org Thanks to all for info and links. Did the upgrade and updated grub and /etc/modules, no problems. This is my first install with grup, always used lilo. Can anyone tell me how to turn off ACPI and set smaller fonts? I have no X installed so smaller fonts on the console would be nice. Thanks -- /ernst-magne Webmail @ vindal.com - Debian - Apache2 - Mailen er sendt med SquirrelMail. Webmail for nuts! http://squirrelmail.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
apt-get upgrade - kernel-image
Hi, not sure this is a problem but I'll like to check anyway. When doing apt-get upgrade the only package listed for upgrade is the kernel image. this is working fine and I'm not sure what the upgrade will do. The sources list say stable. I got a few packages from unstable, but apt is configured to default stable. Why will apt upgrade the kernel? The installed ver. is ii kernel-image-2.6.8-2-386 2.6.8-16 and the same version no. is the one to upgrade. Can I instead hold the kernel-image? -- /ernst-magne Webmail @ vindal.com - Debian - Apache2 - Mailen er sendt med SquirrelMail. Webmail for nuts! http://squirrelmail.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get upgrade - kernel-image
Ernst-Magne Vindal wrote: Hi, not sure this is a problem but I'll like to check anyway. When doing apt-get upgrade the only package listed for upgrade is the kernel image. this is working fine and I'm not sure what the upgrade will do. The sources list say stable. I got a few packages from unstable, but apt is configured to default stable. Why will apt upgrade the kernel? The installed ver. is ii kernel-image-2.6.8-2-386 2.6.8-16 and the same version no. is the one to upgrade. Can I instead hold the kernel-image? It is a security update: http://lists.debian.org/debian-security-announce/debian-security-announce-2005/msg00323.html I would advise performing the installation. -- http://debianhomepage.org http://debcentral.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get upgrade - kernel-image
On 12/17/2005 10:50 AM, Ernst-Magne Vindal wrote: Hi, not sure this is a problem but I'll like to check anyway. When doing apt-get upgrade the only package listed for upgrade is the kernel image. this is working fine and I'm not sure what the upgrade will do. The sources list say stable. I got a few packages from unstable, but apt is configured to default stable. Why will apt upgrade the kernel? The installed ver. is ii kernel-image-2.6.8-2-386 2.6.8-16 and the same version no. is the one to upgrade. Can I instead hold the kernel-image? -- /ernst-magne It's a security release: http://www.debian.org/security/2005/dsa-922 DSA-922-1 kernel-source-2.6.8 -- several vulnerabilities apt-cache policy kernel-image-2.6.8-2-686 will show 2.6.8-16sarge1 as Candidate from http://security.debian.org sarge/updates/main Packages Regards, Ralph -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get upgrade - kernel-image
On Sat, Dec 17, 2005 at 04:40:08PM +0100, Ernst-Magne Vindal wrote: Hi, not sure this is a problem but I'll like to check anyway. When doing apt-get upgrade the only package listed for upgrade is the kernel image. this is working fine and I'm not sure what the upgrade will do. The sources list say stable. I got a few packages from unstable, but apt is configured to default stable. Why will apt upgrade the kernel? The installed ver. is ii kernel-image-2.6.8-2-386 2.6.8-16 and the same version no. is the one to upgrade. Can I instead hold the kernel-image? If you do let the upgrade go through, and you use lilo to boot, remember to update lilo.conf and *rerun lilo* before you reboot, otherwise the boot process eill not be able to find the new kernel and the old one will be gone. I had this problem once, when aptitude decided to replace a kernel. It doesn't seem to happen when I installed a kernel of a comletely different verison number (like 2.6.7 to 2.6.8 -- in that case I just get both kernels. But it did once decide to replace a kernel ... In that case rerunning lilo is necessary. -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
upgrade kernel
Bonjour, Je voudrais savoir s'il est possible de mettre à jour son kernel grâce à la commande apt-get upgrade kernel, ou faut-il plutôt télécharger les sources et les recompiler Merci ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com -- Pensez à lire la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: upgrade kernel
Tahar wrote: Bonjour, Je voudrais savoir s'il est possible de mettre à jour son kernel grâce à la commande apt-get upgrade kernel, ou faut-il plutôt télécharger les sources et les recompiler Merci ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com Cela dépend, si tu utilises un kernel fait à la main tu ne dois t'occuper que des patchs, si tu utilises un kernel-debian, alors il se mettra à jour avec le reste de la distribution. Max. -- Pensez à lire la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: upgrade kernel
tu peux faire apt-cache search linux-image ensuite choisir t'a version de noyaux que tu souhaite installer puis apt-get install linux-image-2.6.12-I386 par exemple. Koh Tahar a écrit : Bonjour, Je voudrais savoir s'il est possible de mettre à jour son kernel grâce à la commande apt-get upgrade kernel, ou faut-il plutôt télécharger les sources et les recompiler Merci ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com -- Pensez à lire la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: upgrade kernel
Merci, j'essayerai de faire ça en rentrant je vous tiendrai au courant de mon avancement :D encore merci --- kohzak [EMAIL PROTECTED] a écrit : tu peux faire apt-cache search linux-image ensuite choisir t'a version de noyaux que tu souhaite installer puis apt-get install linux-image-2.6.12-I386 par exemple. Koh Tahar a écrit : Bonjour, Je voudrais savoir s'il est possible de mettre à jour son kernel grâce à la commande apt-get upgrade kernel, ou faut-il plutôt télécharger les sources et les recompiler Merci ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com -- Pensez à lire la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com -- Pensez à lire la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: why upgrade kernel?
According to Matt Zagrabelny, On Wed, 2005-08-17 at 22:50 -0400, [EMAIL PROTECTED] wrote: Will newer versions of some packages eventually need a newer kernel? yes. for instance some desktop stuff is starting to use udev/hotplug. this requires a 2.6 kernel. Can you indicate which ones? I'd like to try them. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: why upgrade kernel?
On Mon, 2005-08-22 at 12:18 -0700, Tony Godshall wrote: According to Matt Zagrabelny, On Wed, 2005-08-17 at 22:50 -0400, [EMAIL PROTECTED] wrote: Will newer versions of some packages eventually need a newer kernel? yes. for instance some desktop stuff is starting to use udev/hotplug. this requires a 2.6 kernel. Can you indicate which ones? I'd like to try them. gnome-volume-manager for one. -matt zagrabelny -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: why upgrade kernel?
On Wed, 2005-08-17 at 22:50 -0400, [EMAIL PROTECTED] wrote: Will newer versions of some packages eventually need a newer kernel? yes. for instance some desktop stuff is starting to use udev/hotplug. this requires a 2.6 kernel. -matt zagrabelny -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: why upgrade kernel?
[EMAIL PROTECTED] wrote: I have a couple of machines which I'm in the process of upgrading to Sarge. I'm wondering about whether to upgrade the kernels. They're all running some version of 2.4, which I've built for the particular machines. If I don't get new hardware which need newer drivers, and I don't care about any of the fancy new features of 2.6 (whatever those are), is there any benefit in upgrading the kernel? Will newer versions of some packages eventually need a newer kernel? There is no benefit under those assumptions. And when a newer version of a package, can't think of one, NEEDS the 2.6 kernel, it will tell you. Aside from that: the 2.6 kernels boot faster, generally, and support for sound (ALSA) and sensors (i2c) is directly in the kernel, so the headache of installing packages goes away and there are more cases like that. My own reason for 2.6.9 is that the soundest patch for multi-user Linux (2.6.9-ruby.vz11) wants that kernel release. If I were to go to 2.6.12 I would get fancier scheduling. H -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: why upgrade kernel?
I wrote: I have a couple of machines which I'm in the process of upgrading to Sarge. I'm wondering about whether to upgrade the kernels. They're all running some version of 2.4, which I've built for the particular machines. If I don't get new hardware which need newer drivers, and I don't care about any of the fancy new features of 2.6 (whatever thosea are), is there any benefit in upgrading the kernel? Will newer versions of some packages eventually need a newer kernel? Thanks for all the suggestions. I guess I'll stick with my 2.4 kernels. But let me also refine the question a bit. Is there any reason to recompile the _same_ kernel in the newly upgraded environment, given that things like the C libraries and the compiler may have changed? Or if the kernel ran fine under woody, will it also be fine under sarge? Thanks. -David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: why upgrade kernel?
On 10:13 Thu 18 Aug 2005, Hugo Vanwoerkom wrote: And when a newer version of a package, can't think of one, NEEDS the 2.6 kernel, it will tell you. My own reason for 2.6.9 is that the soundest patch for multi-user Linux (2.6.9-ruby.vz11) wants that kernel release. Is this patch for a server with many users simutaneously logged in? If I were to go to 2.6.12 I would get fancier scheduling. I am using 2.6.12 but never noticed 'scheduling' feature of it. Where is this scheduling feature and what is it for? regards bxuef -- dhammapada says: All processes are painful. When one sees this with understanding, then one is disillusioned with the things of suffering. This is the Path of Purification. 278 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: why upgrade kernel?
[EMAIL PROTECTED] wrote: On Thursday 18 August 2005 11:50 am, [EMAIL PROTECTED] wrote: I have a couple of machines which I'm in the process of upgrading to Sarge. I'm wondering about whether to upgrade the kernels. They're all running some version of 2.4, which I've built for the particular machines. If I don't get new hardware which need newer drivers, and I don't care about any of the fancy new features of 2.6 (whatever those are), is there any benefit in upgrading the kernel? Will newer versions of some packages eventually need a newer kernel? Thanks in advance for any opinions. -David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] David, Wow, this is a sensitive question and my response is heavily opinionated, as many answers to this question may be. I think a person in your situation really needs to figure out their needs from the systems the operate, which you obviously have. Let me qualify my response first with saying that I am currently running 2.4.27-2 but will be upgrading/recompiling my kernel today. I am learning towards staying with the 2.4 if I can get my webcam to work. They're all running some version of 2.4, which I've built for the particular machines. If I don't get new hardware which need newer drivers, and I don't care about any of the fancy new features of 2.6 (whatever those are), is there any benefit in upgrading the kernel? Exactly. Since 2.4 and 2.6 kernels are both currently supported, and you don't need any new fangled features in the 2.6 kernel...you'll probably best be suited staying with 2.4. Why do I say this? - Don't fix what isn't broken - You will need to reconfig your kernel without use of a previous .config file between 2.4 and 2.6. Not true. When I upgraded from 2.4.19 to 2.6.12.2, I copied over my .config and then re-ran make xconfig to tweak anything that was new / changed. Of course, I got error messages about missing options, but the window came up with everything available anyway and all the things that _hadn't_ changed were automatically selected for me. Configuring the 2.6 kernel was thus much easier than configuring the 2.4 kernel had been (I did the 2.4 kernel from scratch because my pre-2.4 kernel was the 2.2.22idepci kernel that came with the distro when I installed it). Not too big a deal, but with the new options you have to (should) go through each menu and make the right selections. - Going of the last, you should continue to upgrade within the 2.4 kernel series, for however long it is supported. Using your existing .config file will save time and headaches! Upgrading your kernel within the series, of course, keeps you current on security issues and other system related 'upgrades' (the problem with SCSI-emulation comes to mind). - As a previous Hardened Debian programmer told me not too long ago, the 2.6 kernel is suffering from expansion issues. I see his point. There are lots of programmers doing lots of things to the 2.6 kernel right now, inviting security issues that are inherent in new software. Will newer versions of some packages eventually need a newer kernel? Perhaps (again, mention the SCSI-emulation). I wouldn't worry about it right now. Since both kernels are supported, I would stay with what you need. 2.6 isn't the devil or anything, and I would upgrade to it in a heartbeat if I determined that is what I needed. First I need to do some research to see my hardware dependencies before I can make an informed decision. I respect that you did the same before asking the question. Hope this helps. Respectfully, Steve Siebert Since I've now weighed in on this topic, let me state my position -- upgrade unless you have a good reason not to. Having no immediate need to and being concerned about downtime may or may not be a good reason not to upgrade depending on your situation and the criticality of the machine / machines in question. You will probably find performance improvements with the 2.6 kernel since, for example, an O(1) scheduler has been introduced in the 2.6 kernel which means that, no matter how loaded up with potentially runnable processes your machine gets, the time taken by the scheduler to make a decision about what process to run next is constant. This is a significant benefit over the 2.4 and earlier kernels, where the time taken to make the decision was a function of the number of runnable processes in the system. If you really put your machines to work, this can make a noticeable difference to the responsiveness of the machine. There are a lot of improvements in the 2.6 kernel -- another is improved ALSA drivers for sound -- OSS is still supported but the ALSA drivers are generally considered better. I could go on but others are no doubt better qualified to do so. Mark -- To UNSUBSCRIBE, email to [EMAIL
why upgrade kernel?
I have a couple of machines which I'm in the process of upgrading to Sarge. I'm wondering about whether to upgrade the kernels. They're all running some version of 2.4, which I've built for the particular machines. If I don't get new hardware which need newer drivers, and I don't care about any of the fancy new features of 2.6 (whatever those are), is there any benefit in upgrading the kernel? Will newer versions of some packages eventually need a newer kernel? Thanks in advance for any opinions. -David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: why upgrade kernel?
On Thursday 18 August 2005 11:50 am, [EMAIL PROTECTED] wrote: I have a couple of machines which I'm in the process of upgrading to Sarge. I'm wondering about whether to upgrade the kernels. They're all running some version of 2.4, which I've built for the particular machines. If I don't get new hardware which need newer drivers, and I don't care about any of the fancy new features of 2.6 (whatever those are), is there any benefit in upgrading the kernel? Will newer versions of some packages eventually need a newer kernel? Thanks in advance for any opinions. -David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] David, Wow, this is a sensitive question and my response is heavily opinionated, as many answers to this question may be. I think a person in your situation really needs to figure out their needs from the systems the operate, which you obviously have. Let me qualify my response first with saying that I am currently running 2.4.27-2 but will be upgrading/recompiling my kernel today. I am learning towards staying with the 2.4 if I can get my webcam to work. They're all running some version of 2.4, which I've built for the particular machines. If I don't get new hardware which need newer drivers, and I don't care about any of the fancy new features of 2.6 (whatever those are), is there any benefit in upgrading the kernel? Exactly. Since 2.4 and 2.6 kernels are both currently supported, and you don't need any new fangled features in the 2.6 kernel...you'll probably best be suited staying with 2.4. Why do I say this? - Don't fix what isn't broken - You will need to reconfig your kernel without use of a previous .config file between 2.4 and 2.6. Not too big a deal, but with the new options you have to (should) go through each menu and make the right selections. - Going of the last, you should continue to upgrade within the 2.4 kernel series, for however long it is supported. Using your existing .config file will save time and headaches! Upgrading your kernel within the series, of course, keeps you current on security issues and other system related 'upgrades' (the problem with SCSI-emulation comes to mind). - As a previous Hardened Debian programmer told me not too long ago, the 2.6 kernel is suffering from expansion issues. I see his point. There are lots of programmers doing lots of things to the 2.6 kernel right now, inviting security issues that are inherent in new software. Will newer versions of some packages eventually need a newer kernel? Perhaps (again, mention the SCSI-emulation). I wouldn't worry about it right now. Since both kernels are supported, I would stay with what you need. 2.6 isn't the devil or anything, and I would upgrade to it in a heartbeat if I determined that is what I needed. First I need to do some research to see my hardware dependencies before I can make an informed decision. I respect that you did the same before asking the question. Hope this helps. Respectfully, Steve Siebert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: why upgrade kernel?
[EMAIL PROTECTED] wrote: I have a couple of machines which I'm in the process of upgrading to Sarge. I'm wondering about whether to upgrade the kernels. They're all running some version of 2.4, which I've built for the particular machines. If I don't get new hardware which need newer drivers, and I don't care about any of the fancy new features of 2.6 (whatever those are), is there any benefit in upgrading the kernel? Will newer versions of some packages eventually need a newer kernel? There are some changes from 2.4 to 2.6. I haven't been able to sort out all the changes on my machine yet. However, I'm at the point where a little knowledge is a dangerous thing. I would advise you to stay with the 2.4 kernel since it is already working for you. If later you want something like ALSA or udev, then consider a 2.6 kernel. By that time the ongoing development of the 2.6 kernel should be in better shape. You might want to install the packages apt-listbugs and apt-listchanges, if you can use them, to tell you if an upgrade of one of your installed packages actually needs or requires a 2.6 kernel. (I've just installed them myself since I saw them recommended in another thread.) -- (Mr.) Gayle Lee Fairless, http://counter.li.org/, No. 365760. Linux Gcomm 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686 GNU/Linux Linux Gcomm 2.6.11-1-686 #1 Mon Jun 20 22:00:38 MDT 2005 i686 GNU/Linux Linux Gcomm 2.6.12-1-686 #1 Fri Jun 24 12:17:14 CEST 2005 i686 GNU/Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Ugly sarge upgrade -- kernel 2.4.27-2 2.4.27-6
On Wed, Jan 05, 2005 at 06:13:24AM +0100, Thomas Hood wrote: Possibly a result of applications trying to play sound effects but sound not working. I can play ogg files. Sounds like crap (since processor can't decode quickly enough), but screen output for ogg123 is normal. Building your own alsa-modules package may fix the problem. I don't have alsa-modules installed. ogg123 uses OSS drivers. This may be bug #284356. Thanks for the pointer. Hoping that 2.4.27-2-686 may solve my problem. Jason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Ugly sarge upgrade -- kernel 2.4.27-2 2.4.27-6
Upgrading to 2.4.27-2-686 (from sid) does not fix the slowness problem (at least for me). The bug corresponding to this problem is #288272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=288272 Jason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Ugly sarge upgrade -- kernel 2.4.27-2 2.4.27-6
On Sat, Dec 25, 2004 at 03:27:57PM -0500, Michael Murphy wrote:
Any one else? Googling's born no fruit. I'm brand new to debian (a
recent redhat emigree) and am unsure where, or whether, to report
this. Any insight or direction members of this list can share will
be gratefully received.
In case you're still looking for a solution, reverting to 2.4.26 fixes
the problem for me. Here's what I did:
- Point apt at sid
If you have a /etc/apt/sources.list line like this:
deb http://http.us.debian.org/debian sarge main contrib non-free
edit it and change sarge to sid
- Run apt-get update
- Run apt-get install kernel-{image,pcmcia-modules}-2.4.26-1-686
Only trouble with this is that alsa-modules-2.4.26-1-686 does not exist
in sid, so you won't be able to use alsa with 2.4.26...
Jason
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
