Re: Firefox lost restore previous session setting
On 10/21/2016 08:38 PM, Gary Dale wrote: On 21/10/16 07:23 PM, Dutch Ingraham wrote: On Fri, Oct 21, 2016 at 02:32:46PM -0400, Gary Dale wrote: On 21/10/16 04:28 AM, William Satterthwaite wrote: Thanks. The settings button | History has a "Restore Closed Tabs" option that isn't in the History pulldown. When you first start Firefox, the option reads "Restore Closed Windows". Neither actually does the same thing as the "restore previous session" button used to do. I have no idea what criteria Firefox uses to decide which windows/tabs to restore, but they aren't the ones that were open when I closed Firefox. There also doesn't seem to be way of customizing the menu bar to include the option, or even the option in settings button | History section. The History | Restore Closed Tabs is gone. I'm using Firefox 45.4.0. I preferred it when Firefox automatically restored your last session. I didn't mind it when it started asking you nor even when it made you press a button on the startup page. I gather from the increasing difficulty in restoring the previous session, someone has decided that people simply shouldn't do it. :) I am using FF 49.0.1, currently logged into Arch Linux. I have an option History -> Restore Previous Session. I can also go History -> Recently Closed Tabs -> Restore All Tabs. Isn't this what you are looking for, or did I miss something? Interesting. These options weren't there earlier but have now appeared. Unfortunately History | Restore Previous Session is always greyed out. The other ones are now behaving like the Settings Button | History except that they are both present all the time. The Restore Closed Windows opens a new browser with the previous session restored - meaning I have to close the browser that launched it. There is some real weirdness going on with Firefox. I am running 49.0.2 direct from Mozilla and it seems to work as it should. I can go to Edit>Preferences>General and select "Show my windows and tabs from last time" so that it always starts with my previous windows and tabs opened. If I select History>Recently closed Windows>Restore all windows it opens all of the listed windows and leaves my current window open as well. Marc
Re: Can't install security update: server name not resolved
On Fri, 21 Oct 2016 07:35:28 -0400 Carl Fink wrote: > Anyone else seeing this? > > E: Failed to fetch > http://security.debian.org/pool/updates/main/l/linux/linux-headers-3.16.0-4-amd64_3.16.36-1+deb8u2_amd64.deb > Could not resolve 'security-cdn.debian.org > It was apparently temporary. Worked when I got home > Any suggestions? In case you don't know by now, it was probably this: http://gizmodo.com/this-is-probably-why-half-the-internet-shut-down-today-1788062835 https://techcrunch.com/2016/10/21/many-sites-including-twitter-and-spotify-suffering-outage/ http://arstechnica.com/security/2016/10/dos-attack-on-major-dns-provider-brings-internet-to-morning-crawl/ https://krebsonsecurity.com/2016/10/ddos-on-dyn-impacts-twitter-spotify-reddit/ https://tech.slashdot.org/story/16/10/21/135241/several-sites-including-twitter-github-spotify-paypal-nytimes-suffering-outagedyn-dns-under-ddos-attack-update http://www.theregister.co.uk/2016/10/21/dns_devastation_as_dyn_dies_under_denialofservice_attack/ There were apparently at least 3 major phases of attack, with calm between. Nick -- Never FDISK after midnight
list installed packages present only in stable
How can I list all the packages installed on my system that are currently part of the stable distribution but not present in either testing or sid? For example, ibkasten2okteta1controllers1abi1 libkasten2okteta1gui1 are currently part of stable, but not present in either testing or sid. The command should list these packages if they are currently installed. If it matters, here are the repos I am tracking. % inxi -r Repos: Active apt sources in file: /etc/apt/sources.list deb http://httpredir.debian.org/debian/ stretch main contrib non-free deb-src http://httpredir.debian.org/debian/ stretch main contrib non-free deb http://httpredir.debian.org/debian/ stretch-updates main contrib non-free deb-src http://httpredir.debian.org/debian/ stretch-updates main contrib non-free deb http://security.debian.org/ stretch/updates main contrib non-free deb-src http://security.debian.org/ stretch/updates main contrib non-free I prefer to use apt-get to aptitude. But if this can only be done in aptitude, I do not mind using that. thanks raju -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
Re: Can't set up network on Debian 8 fresh install [was: Unidentified subject!]
On Thu, Sep 29, 2016 at 11:31:28AM +0200, to...@tuxteam.de wrote: My abject apologies for the delay in this reply. just got back in town and am just catching up on my email. > Hi, Bob. > > Welcome. > > First, a meta-suggestions > > Try to use a good subject line (I tried to modify it). > This list is read by many volunteers, and is pretty high > volume. Nobody reads everything. A good subject line > will make it more probable that your mail is picked up > by someone knowledgeable in the subject matter. I know but I hit the send key too soon. Sorry. > > Comments interleaved in your main text > > On Wed, Sep 28, 2016 at 03:30:04PM -0700, hol...@cox.net wrote: > > Clean install of deb8 (jessie)on my Thinkpad T4220i laptop. went well > > except for the fact that the network configuration > > with DCP failed. > > This is probably DHCP. That means that the laptop tries to ask in > the local network for an IP address and gets assigned one by the > (local) DHCP server, which these days typically is the internet > router. > > Question: is your Thinkpad connected to the local net via a > network cable? Or via WLAN? Ethernet cable directly to the modem. No router (yet). > > Open a console. What is the output of the command > /sbin/ifconfig > Could you paste it here? root@localhost:/home/holtzm# /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:21:cc:b6:06:8f UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:20 Memory:f250-f252 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:27 errors:0 dropped:0 overruns:0 frame:0 TX packets:27 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3077 (3.0 KiB) TX bytes:307 > > > I was given 3 options. > > 1) try it again. This was hope over experience. > > That means it isn't getting an answer to its DHCP requests. Most > probably it doesn't reach the network, but we can't know for sure > yet. > > > 2) configure manually. Great if I had the first inkling how. I'm a > > complete neophyte when it > >comes to networking. > > 3) continue without configuring a network. The only one that would let > > me continue the > >installation. > > > > I have a functioning desktop pc so I compred some files w/ the laptop. > > Perhaps the output of /sbin/ifconfig on the desktop PC would be > interesting here as well. root@localhost:/home/holtzm# /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:1e:8c:1e:85:82 inet addr:70.190.29.56 Bcast:70.190.29.255 Mask:255.255.255.0 inet6 addr: fe80::21e:8cff:fe1e:8582/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:51469650 errors:0 dropped:0 overruns:0 frame:0 TX packets:189063 errors:0 dropped:0 overruns:0 carrier:6 collisions:0 txqueuelen:1000 RX bytes:3282631748 (3.0 GiB) TX bytes:19166009 (18.2 MiB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:66231 errors:0 dropped:0 overruns:0 frame:0 TX packets:66231 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:18252784 (17.4 MiB) TX bytes:18252784 (17.4 MiB) > > regards > -- tomás -- Bob Holtzman A man is a man who will fight with a sword or conquer Mt. Everest in snow. But the bravest of all owns a '34 Ford and tries for six thousand in low.
Re: Network manager not showing saved network connections
Am 24.10.2016 um 00:26 schrieb Michael Biebl: > Am 23.10.2016 um 23:30 schrieb Paul Seyfert: >> Deleting almost all connections (204 out of 214) in >> /etc/NetworkManager/system-connections/ and only keeping those few I am >> sure to use[2], I get a working state (all connections which I want to > > .. > >> Is this a known bug[3]? Any suggestions what to test/investigate/other >> information I should provide? > > Yes, known issue. You are hitting a D-Bus limit here. > http://bugs.debian.org/781007 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773525 is the merged bug report with more details. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Network manager not showing saved network connections
Am 23.10.2016 um 23:30 schrieb Paul Seyfert: > Deleting almost all connections (204 out of 214) in > /etc/NetworkManager/system-connections/ and only keeping those few I am > sure to use[2], I get a working state (all connections which I want to .. > Is this a known bug[3]? Any suggestions what to test/investigate/other > information I should provide? Yes, known issue. You are hitting a D-Bus limit here. http://bugs.debian.org/781007 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Network manager not showing saved network connections
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, I am using debian stable with network-manager 0.9.10.0-7 and network-manager-gnome 0.9.10.0-2. I recently noticed that seeing a network[0] (eduroam) for which I configured several connections (had three eduroam accounts over the time, and have two setups for one of them for debugging), the nm-applet didn't offer me all connections to choose for connecting to that network. Digging further I went to right click on the nm-applet icon -> Edit connections and got more suspicious as my home network did not appear and I was pretty sure having used my home wifi recently. Searching around, I found that all the settings I was missing in the gui are actually there in /etc/NetworkManager/system-connections: https://mathphys.fsk.uni-heidelberg.de/~pseyfert/slash-etc.png (apparently five eduroam connections [1]) https://mathphys.fsk.uni-heidelberg.de/~pseyfert/nm-applet.png (gui shows only two[4]) restarting network manager (systemctl restart network-manager.service) and/or the nm-applet (killall nm-applet ; nm-applet) doesn't fix the situation. Deleting almost all connections (204 out of 214) in /etc/NetworkManager/system-connections/ and only keeping those few I am sure to use[2], I get a working state (all connections which I want to exist are shown in the nm-applet). When I restore all connections in /etc/NetworkManager/system-connections/, the list in nm-applet is again incomplete. So far I only used the network manager through the nm-applet with my normal user account. Is this a known bug[3]? Any suggestions what to test/investigate/other information I should provide? Cheers, Paul [0] mostly wifi connections, but also mobile broadband seems affected. [1] time stamps are off since I cleared the directory earlier today for debugging and now copied the files back and restarted network-manager and the nm-applet. In the backup they look like this: https://mathphys.fsk.uni-heidelberg.de/~pseyfert/orgs.png [2] including a connection which is not shown. [3] google is somewhat swamped with network manager forgetting passwords or not showing networks after hibernation. [4] note the matching of filename to id https://mathphys.fsk.uni-heidelberg.de/~pseyfert/filename-id.png -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJYDSv6AAoJEPOmP9OjPXmrMSkQAIe9m+hvNuihNUFVREynnQsp VfuVD4PWUh9t6EsvNTs55rNOZwAg6tsc9bLGntFMoeYydDNTr1M5Wj3WLGbju0iY lpJ7c9TQTMJ/7d/lTSbZPe2nllIrH6mCWr4SK7LunMGpXe8gH6V1B5xcLPYE/oUX peCpPt6AQONSjXr3Tmu+MGRl5rA7Xdw41jfmjU6nUXBIJJyGhOvHVaqhon15+qHi 0rrTUO5vGnGvVvTmmYo6F6idqJ1BLcLBMqxUfffi38JiLi3JnTRbGTjXrFE3UkPZ 9A+WWz8A8GIUp6cmxWP39/qC7WBGtfR+HcikElYf4Q4FBQa9W9ZCRA0seBnZM23N VjgqUR4RDaAg4H6LCc3qFKmI76rVRSlPPRNu+pfzuf083b2y/QWBHyu0THWHXB7d ESseXEkGmQw5rOl4oRUJKC6b155uC0SbZvI6/4vIVVBW/G2ZSQPIkMDNo8wfGPv+ QUS6LFB5tvCTNjjJGftN6+fLBYvOhUQXubokCiKHE8oTU3Q4B6iteNAfRASjmDQm s12Up2WNhMeMY3qIZMwG5MDk+MW3LQyRM7sr8Ceko5Zc2I+Gi4S5ob5cF/H6Lpv4 VD7CbSA5NmialHPzGx6np8/j7QWpPlT/f5+3z2Iox1pb1eDeU587++e5M0DmRyZv 8wB3F3UHwxQaGrZr+ymo =h5HL -END PGP SIGNATURE-
Re: Stretch System Stops Boot Process Immediately After Grub Screen
On 10/23/2016 05:26 PM, Frank wrote: Op 23-10-16 om 22:47 schreef Felix Miata: I don't remember having any Stretch installations with fewer than two installed kernels. The currently booted one, originally installed 51 weeks ago, has 6 installed. I've yet to discover any doc suggesting anything about any possibility of automatic removal of old kernels from Debian Testing installations. This is exactly what happens when the binary package version number does not change. The 4.7.6 kernel came in packages with version number 4.7.0-1. So did the 4.7.8 one [1]. This means 4.7.8 simply overwrote 4.7.6. This sort of thing has been happening on my Testing system for years. The older ones I have are 4.6.0-1, 4.5.0-2 and 4.5.0-1. Regards, Frank 1: https://tracker.debian.org/pkg/linux The arrangement has been working for me for quite some time, but it may have bit me in the behind this time around. Thank you for the link. I should have been paying more attention.
Re: Stretch System Stops Boot Process Immediately After Grub Screen
Op 23-10-16 om 22:47 schreef Felix Miata: I don't remember having any Stretch installations with fewer than two installed kernels. The currently booted one, originally installed 51 weeks ago, has 6 installed. I've yet to discover any doc suggesting anything about any possibility of automatic removal of old kernels from Debian Testing installations. This is exactly what happens when the binary package version number does not change. The 4.7.6 kernel came in packages with version number 4.7.0-1. So did the 4.7.8 one [1]. This means 4.7.8 simply overwrote 4.7.6. This sort of thing has been happening on my Testing system for years. The older ones I have are 4.6.0-1, 4.5.0-2 and 4.5.0-1. Regards, Frank 1: https://tracker.debian.org/pkg/linux
Re: Re: Reconfiguring grub2 UFEI system
oops, I notice it is solved now, must have missed those posts in the digest somehow, I was thinking however that maybe it was a case of 'I never installed that version of grub so I'm not going to write to it' as you probably had a slightly different version from the one on SuSE, I am no expert however so may be talking out of turn here.
Re: Stretch System Stops Boot Process Immediately After Grub Screen
On 10/23/2016 04:47 PM, Felix Miata wrote: Jape Person composed on 2016-10-23 14:33 (UTC-0400): Felix Miata wrote: Does the same thing happen booting the previous kernel (4.6?)? Nope. The problem occurred on the first reboot after the upgrade from 4.7.6-1 to 4.7.8-1. The upgrade process didn't leave 4.7.6-1 in place so I could fall back. I don't remember just when I started seeing that upgrade behavioral change in Debian. I used to always use the new kernel for a week or so, and then I would have to use apt to remove the old one if it was no longer needed. I don't remember having any Stretch installations with fewer than two installed kernels. The currently booted one, originally installed 51 weeks ago, has 6 installed. I've yet to discover any doc suggesting anything about any possibility of automatic removal of old kernels from Debian Testing installations. Could it be that the pae kernel your CF-R3 is running is not the recommended kernel for that CPU, and that has something to do with replacement on kernel upgrade instead of simply adding new? During new installations of Debian my systems I chose: linux-image-686-pae for the i386 systems linux-image-amd64 for the 64 bit systems Those new installations offer me the latest available kernel from the Stretch repository for each type of system. At some time in recent months I installed the linux-image-686-pae on the trouble machine. Since that time it has tracked the latest linux-image package just like the two other i386 systems and the amd64 system. I have seen all of these systems keep the older kernel when a "major" kernel version change has occurred in the repository. In those cases I have kept the older kernel around until I was sure it was okay. But for small kernel version jumps the next reboot just shows me the new kernel, the old one having evidently been replaced. Maybe the time is now opportune for an arch upgrade. The supply of devs working 32-bit seems to be shrinking quickly towards critical mass. 32-bit seems to be soon if not already in process of being removed from Stretch: http://news.softpedia.com/news/debian-is-dropping-support-for-older-32-bit-hardware-architectures-in-debian-9-503832.shtml If you mean I should replace the old equipment, I was planning on doing so. The oldest system in my collection is a Sony Viao video workstation that I believe came with Windows 98 on it. I think it is 17 or 18 years old, and is simply one of the best pieces of hardware of any kind I've ever owned. It has run 24/7 since I purchased it. I'm probably going to buy some Libreboot T400s, or I might get some Intel NUCs, if I think Debian's repositories will support that newer hardware. It's a shame, though, to have perfectly useful pieces like the Panasonic CF-R3 be relegated to obsolete software. The thing is a gem. It's tiny even by modern netbook standards but is fast and powerful. It was a marvel when it was introduced, and it's still no slouch. I appreciate your observations and suggestions. Regards, JP
WiFi works during install, not after
So I have a ThinkPad Yoga 11s ultrabook. If I copy over the firmware-realtek package, Debian can install just fine over the WiFi connection. (I don't have wired internet at my home.) After install, everything is fine, except I can't connect to the WiFi. I know it's possible because the installer does it! The wlan0 interface exists and is up, but "dhclient wlan0" ends up assigning 169.169.254.8.192, which is not a routable address. As you might expect, attempts to ping/connect to external systems via IP address fail with "Destination host unreachable" and of course, DNS lookups universally fail. This ultrabook is supposed to have the rtl8723au chipset, which is a USB 802.11/Bluetooth chipset that for some reason Lenovo used in the laptop, with an inside-the-case-only USB connection. The firmware-realtek package is installed on the ultrabook. Interestingly, the rtl8723au module is NOT loaded, and "modprobe rtl8723au" fails with a message about the module not being found, even though it's right there if I "locate rtl8723au", in the drivers/staging directory. Maybe the staging area isn't used by default? I confess I don't remember how to change the path that is searched for loadable modules. Any insights would be most gratefully received. -- Carl Fink c...@finknetwork.com
Re: Reconfiguring grub2 UFEI system
On Sun, 2016-10-23 at 17:49 +0200, Pascal Hambourg wrote: > Le 22/10/2016 à 23:17, Mark Neidorff a écrit : > > On Friday, 10/21/16 10:19:47 PM Pascal Hambourg wrote: > > > > > What is the output of "os-prober" ? > > > > No output. (yes, I ran it as root) > > Then no other system was detected and added to the GRUB menu when > you > ran update-grub. > > > > Are you sure the GRUB that shows up is the one from Debian ? > > > > I'm not sure how to answer that question. The first OS I installed > > was > > OpenSUSE. Then I installed Debian 8.6 twice (on the two separate > > drives in > > the system). All three of these entries are still there even after > > running > > update-grub. > > > > I wouldn't care about the extra entries except that the OpenSUSE > > entry is the > > default. > > Is openSUSE the first entry in the menu ? AFAICS, by default the > first > entry in the menu is the OS which installed the active GRUB. So it > looks > like it is openSUSE's GRUB, not Debian's one. > > From Debian, what it the ouput of the following commands ? > > efibootmgr > ls /boot/ > ls /boot/efi/EFI Last time I used this (update-grub on fully updated Debian testing) a few weeks back it did nothing for me either, however as a workaround you can re-install/re-configure grub-pc and/or grub-pc-bin (via apt- get, synaptic or your personal favourite installer) and that will install the grub menu for you. I think it was the first of these two options (re-install grub-pc) that did the trick but just in case I remember wrongly, I mention the other software too. However, it probably needs tracking down as to why this no longer works for all, so if you are willing, please continue to work through other processes first.
Re: Stretch System Stops Boot Process Immediately After Grub Screen
Jape Person composed on 2016-10-23 14:33 (UTC-0400): Felix Miata wrote: Does the same thing happen booting the previous kernel (4.6?)? Nope. The problem occurred on the first reboot after the upgrade from 4.7.6-1 to 4.7.8-1. The upgrade process didn't leave 4.7.6-1 in place so I could fall back. I don't remember just when I started seeing that upgrade behavioral change in Debian. I used to always use the new kernel for a week or so, and then I would have to use apt to remove the old one if it was no longer needed. I don't remember having any Stretch installations with fewer than two installed kernels. The currently booted one, originally installed 51 weeks ago, has 6 installed. I've yet to discover any doc suggesting anything about any possibility of automatic removal of old kernels from Debian Testing installations. Could it be that the pae kernel your CF-R3 is running is not the recommended kernel for that CPU, and that has something to do with replacement on kernel upgrade instead of simply adding new? Maybe the time is now opportune for an arch upgrade. The supply of devs working 32-bit seems to be shrinking quickly towards critical mass. 32-bit seems to be soon if not already in process of being removed from Stretch: http://news.softpedia.com/news/debian-is-dropping-support-for-older-32-bit-hardware-architectures-in-debian-9-503832.shtml -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: Reconfiguring grub2 UFEI system **SOLVED**
Hi! Em domingo, 23 de Outubro de 2016 20:10:05 WEST, Mark Neidorff escreveu: On Sunday, 10/23/16 10:05:43 AM Laruibasar wrote: Em sábado, 22 de Outubro de 2016 22:17:35 WEST, Mark Neidorff escreveu: > On Friday, 10/21/16 10:19:47 PM Pascal Hambourg wrote: >> Le 21/10/2016 à 20:56, Mark Neidorff a écrit : >> > So, the next step was to clean out the other distros. I >> >> used gparted to >> >> > delete no longer needed partitions and to expand other >> >> partitions to fill >> >> > the space. All is now good. >> > >> > I then ran >> > >> > #update-grub >> > >> > hoping that would regenerate the grub boot menu, (I also tried >> > #update-grub2) but the old entries still appear when the system boots. >> >> Are you talking about entries in GRUB's menu or in the UEFI boot menu ? > > Grub menu. (I don't see a UEFI menu) > >> update-grub only updates the former. > > Good. > >> What is the output of "os-prober" ? > > No output. (yes, I ran it as root) > >> Are you sure the GRUB that shows up is the one from Debian ? > > I'm not sure how to answer that question. The first OS I installed was > OpenSUSE. Then I installed Debian 8.6 twice (on the two > separate drives in > the system). All three of these entries are still there even > after running > update-grub. Have you mounted the EFI partition? Update-grub change grub, I don't think it changes the FIE partitions. And check motherboard bios/uefi for the default entry > I wouldn't care about the extra entries except that the > OpenSUSE entry is the > default. I want Debian to be the default (and, yes there is only one > instance of Debian installed). Yes I tried changing the value > of the default > before I ran update-grub, but that didn't help. > > Thanks for any help, > > Mark Bandarra I went into the UEFI bios, and changed the default entry. Now I get the correct Debian grub boot screen without the extra entries. Once I get the rest of this system configured, I'm going to have to go back and really understand what goes on in the UEFI. I'm marking this as SOLVED. Glad you solve it! If you are going to use several OS on you PC with UEFI, check a solution call rEFInd (uefi boot manager). I use it for dual boot and it was once upon a time the way I use to transition Debian to uefi. Many thanks for the help. Mark -- Enviado do Dekko através do meu dispositivo Ubuntu.
Re: Reconfiguring grub2 UFEI system **SOLVED**
On Sunday, 10/23/16 10:05:43 AM Laruibasar wrote: > Em sábado, 22 de Outubro de 2016 22:17:35 WEST, Mark Neidorff > > escreveu: > > On Friday, 10/21/16 10:19:47 PM Pascal Hambourg wrote: > >> Le 21/10/2016 à 20:56, Mark Neidorff a écrit : > >> > So, the next step was to clean out the other distros. I > >> > >> used gparted to > >> > >> > delete no longer needed partitions and to expand other > >> > >> partitions to fill > >> > >> > the space. All is now good. > >> > > >> > I then ran > >> > > >> > #update-grub > >> > > >> > hoping that would regenerate the grub boot menu, (I also tried > >> > #update-grub2) but the old entries still appear when the system boots. > >> > >> Are you talking about entries in GRUB's menu or in the UEFI boot menu ? > > > > Grub menu. (I don't see a UEFI menu) > > > >> update-grub only updates the former. > > > > Good. > > > >> What is the output of "os-prober" ? > > > > No output. (yes, I ran it as root) > > > >> Are you sure the GRUB that shows up is the one from Debian ? > > > > I'm not sure how to answer that question. The first OS I installed was > > OpenSUSE. Then I installed Debian 8.6 twice (on the two > > separate drives in > > the system). All three of these entries are still there even > > after running > > update-grub. > > Have you mounted the EFI partition? Update-grub change grub, I don't think > it changes the FIE partitions. And check motherboard bios/uefi for the > default entry > > > I wouldn't care about the extra entries except that the > > OpenSUSE entry is the > > default. I want Debian to be the default (and, yes there is only one > > instance of Debian installed). Yes I tried changing the value > > of the default > > before I ran update-grub, but that didn't help. > > > > Thanks for any help, > > > > Mark > > Bandarra I went into the UEFI bios, and changed the default entry. Now I get the correct Debian grub boot screen without the extra entries. Once I get the rest of this system configured, I'm going to have to go back and really understand what goes on in the UEFI. I'm marking this as SOLVED. Many thanks for the help. Mark
Re: Stretch System Stops Boot Process Immediately After Grub Screen
On 10/23/2016 01:33 PM, Felix Miata wrote: James P. Wallen composed on 2016-10-23 12:14 (UTC-0400): On 10/22/2016 18:10 (UTC-0400), Jape Person wrote: It's confusing to see a response from a different person writing as if he was responding to himself. The confusion is caused by my idiotic tendency to confuse which e-mail account I'm using at any given moment. I generally use a separate e-mail account for mailing lists to help with organizational chores. Sorry about that. I did indeed respond to myself using a different e-mail account. Be that as it may, have either of you tried intercepting Grub and unquieting the boot process? Remove quiet, and either change splash to splash=0 or remove splash entirely. Then proceed to boot, and see what if anything shows up on screen besides a blinking underline cursor in the upper left corner. Yes, both of us have tried making changes in the boot process. Heh. There is simply no change in the experience when removing quiet or using nomodeset. The disk access stops instantly when the grub screen disappears. No keyboard controls are effective. The fact that just touching the power switch results in instant shut-down makes me think that the kernel has not even started to load. But computers are faster than I am, so I realize that this issue could be happening at the end of grub or the beginning of the kernel load. Does the same thing happen booting the previous kernel (4.6?)? Nope. The problem occurred on the first reboot after the upgrade from 4.7.6-1 to 4.7.8-1. The upgrade process didn't leave 4.7.6-1 in place so I could fall back. I don't remember just when I started seeing that upgrade behavioral change in Debian. I used to always use the new kernel for a week or so, and then I would have to use apt to remove the old one if it was no longer needed. Have you tried giving it 10 or more minutes before assuming boot won't complete? I have a Stretch installation last updated about three weeks ago, which installed a 4.7 kernel of 26 Sept. Booting it just now took >4.5 minutes to get from the Grub selection to seeing boot messages appear on screen, but from the point messages started appearing, boot proceeded normally. I have >20 multiboot PCs with various distros. I've been encountering this type of boot delay, sometimes as long as more than 13 minutes, with random kernel/initrd pairs in several different distros, for going on two years. It's happened only when Dracut builds the initrd, and only with 64 bit installations. Whenever I've asked anywhere about this I've gotten zero useful response, if any response at all. I've left it at the blinking cursor for hours without seeing any change. I have also been seeing the same odd boot delays (and shutdown delays) on my 64 bit installation for months in Stretch. The delays are not consistent in behavior or duration. I have not been able to find any way to gather useful data. Yeah, kind of annoying. But it's different from what I'm seeing on this i386 installation. Incidentally, sometimes on the amd64 image on another machine I've switched to TTY1 following logon to the GUI and seen systemd countdown messages for starting of various daemons still going on after the boot has apparently succeeded. No intention of providing flame bait here, but if anything like daemon startup failures was happening before the switch to systemd, I was happily ignorant of it until I actually needed the daemon, and it didn't slow my boot or shutdown processes. Just saying. ;-) Now I shall grin, duck, and run. http://markmail.org/message/yj3l3uphno3cgpgp is probably where I first asked publicly. I'll check out your link to see if there's any way I can a) learn something, b) contribute something, c) blame it all on a politician. Thanks, JP
Re: Stretch System Stops Boot Process Immediately After Grub Screen
On 10/23/2016 01:21 PM, Børge Holen wrote: I have to use the nomodeset from time to time where the f*** gfx card has unresolved issues with itself. Atleast it lets me boot to a prompt. Now thinking of it, I have no blinking cursor, I just get a black screen... So different issue all together and I am just rambling on Yes, I think this is a different issue. Once the grub screen disappears there is no disk access at all. I just get the blinking underline cursor in the top left corner of the screen. Using nomodeset, nosplash/splash=0, removing quiet -- none of these changes to the boot line of grub in any combination results in any change. The system simply stops accessing its hard drive and I get the black screen with the blinking underline cursor. Since a touch on the power button results in a system beep and immediate powerdown, I'm thinking it's possible that the system has not even started to load the kernel. When I have time to make some live images, I'll test to see what's going on. Regards, JP
Re: Stretch System Stops Boot Process Immediately After Grub Screen
On 10/23/2016 01:03 PM, Michael Lange wrote: On Sun, 23 Oct 2016 12:14:39 -0400 "James P. Wallen" wrote: Double checked to see if I was right about the video subsystem. It is not ATI, it is Intel integrated. No docs on this thing. It was never officially sold in U.S., where I live currently. Since I can't boot it to usable state, I can't (easily) find out exactly which video it uses. It's probably destine for re-installation anyway. I was just surprised to see such a failure occur after upgrade. If the device has worked with other kernel versions before, you could boot from an USB drive, do a chroot and install a kernel that works, this should be a pretty straightforward procedure. Thanks, Michael. Yes, I posted originally from another e-mail account, so I'm sorry for any confusion that may have caused in the thread. I am planning to boot from a live image on USB key to try chrooting onto the system drive to fix it. I'll probably try update-grub first just in case something weird happened to grub-pc during that part of the upgrade. I could install a different kernel, but I'd prefer working on the system before doing that to see if there's a way to make the current kernel in testing work. I'm kind of surprised that a minor kernel change of this type (probably) resulted in this problem. I'm not sure just what Debian's policy on kernel upgrades is. With major version changes, I think, the upgrade process leaves the old kernel in place so you can fall back on it if the new one fails. But minor revisions to the kernel just install the new kernel in place of the old one. I only noticed this change in upgrade policy -- if that is, indeed, what it is -- over the past couple of years. This computer is definitely a corner case hardware-wise. The straight replacement of the kernel seems to have backfired in this case for this particular machine. Many thanks for your suggestion. And if anyone has seen a bug report that might be pertinent, I'd appreciate a pointer. I've searched briefly, but found nothing. Regards, JP
Re: Stretch System Stops Boot Process Immediately After Grub Screen
James P. Wallen composed on 2016-10-23 12:14 (UTC-0400): On 10/22/2016 18:10 (UTC-0400), Jape Person wrote: It's confusing to see a response from a different person writing as if he was responding to himself. Be that as it may, have either of you tried intercepting Grub and unquieting the boot process? Remove quiet, and either change splash to splash=0 or remove splash entirely. Then proceed to boot, and see what if anything shows up on screen besides a blinking underline cursor in the upper left corner. Does the same thing happen booting the previous kernel (4.6?)? Have you tried giving it 10 or more minutes before assuming boot won't complete? I have a Stretch installation last updated about three weeks ago, which installed a 4.7 kernel of 26 Sept. Booting it just now took >4.5 minutes to get from the Grub selection to seeing boot messages appear on screen, but from the point messages started appearing, boot proceeded normally. I have >20 multiboot PCs with various distros. I've been encountering this type of boot delay, sometimes as long as more than 13 minutes, with random kernel/initrd pairs in several different distros, for going on two years. It's happened only when Dracut builds the initrd, and only with 64 bit installations. Whenever I've asked anywhere about this I've gotten zero useful response, if any response at all. http://markmail.org/message/yj3l3uphno3cgpgp is probably where I first asked publicly. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: Stretch System Stops Boot Process Immediately After Grub Screen
Heck I even remember a one-floppy live distribution that I had for just this purpose. On Sun, Oct 23, 2016 at 7:26 PM, Børge Holen wrote: > Have you tried booting off a live distribution and inserted the old kernel > and symlinked the libraries so you can rerun grub update? I remember we had > to do that with lilo whenever I tried new kernels and forgot all about > lilo. Cannot even remember the last time I did it, since I found the rescue > option in the installation disk. That option wasn't there back in the days > > On Sun, Oct 23, 2016 at 7:21 PM, Børge Holen > wrote: > >> I have to use the nomodeset from time to time where the f*** gfx card has >> unresolved issues with itself. Atleast it lets me boot to a prompt. Now >> thinking of it, I have no blinking cursor, I just get a black screen... So >> different issue all together and I am just rambling on >> >> On Sun, Oct 23, 2016 at 7:03 PM, Michael Lange >> wrote: >> >>> On Sun, 23 Oct 2016 12:14:39 -0400 >>> "James P. Wallen" wrote: >>> >>> > Double checked to see if I was right about the video subsystem. >>> > It is not ATI, it is Intel integrated. No docs on this thing. It >>> > was never officially sold in U.S., where I live currently. Since >>> > I can't boot it to usable state, I can't (easily) find out >>> > exactly which video it uses. >>> > >>> > It's probably destine for re-installation anyway. I was just >>> > surprised to see such a failure occur after upgrade. >>> >>> If the device has worked with other kernel versions before, you >>> could boot from an USB drive, do a chroot and install a kernel that >>> works, this should be a pretty straightforward procedure. >>> >>> Regards >>> >>> Michael >>> >>> >>> >>> .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . >>> .-. >>> >>> You canna change the laws of physics, Captain; I've got to have thirty >>> minutes! >>> >>> >> >
Re: Stretch System Stops Boot Process Immediately After Grub Screen
Have you tried booting off a live distribution and inserted the old kernel and symlinked the libraries so you can rerun grub update? I remember we had to do that with lilo whenever I tried new kernels and forgot all about lilo. Cannot even remember the last time I did it, since I found the rescue option in the installation disk. That option wasn't there back in the days On Sun, Oct 23, 2016 at 7:21 PM, Børge Holen wrote: > I have to use the nomodeset from time to time where the f*** gfx card has > unresolved issues with itself. Atleast it lets me boot to a prompt. Now > thinking of it, I have no blinking cursor, I just get a black screen... So > different issue all together and I am just rambling on > > On Sun, Oct 23, 2016 at 7:03 PM, Michael Lange > wrote: > >> On Sun, 23 Oct 2016 12:14:39 -0400 >> "James P. Wallen" wrote: >> >> > Double checked to see if I was right about the video subsystem. >> > It is not ATI, it is Intel integrated. No docs on this thing. It >> > was never officially sold in U.S., where I live currently. Since >> > I can't boot it to usable state, I can't (easily) find out >> > exactly which video it uses. >> > >> > It's probably destine for re-installation anyway. I was just >> > surprised to see such a failure occur after upgrade. >> >> If the device has worked with other kernel versions before, you >> could boot from an USB drive, do a chroot and install a kernel that >> works, this should be a pretty straightforward procedure. >> >> Regards >> >> Michael >> >> >> >> .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. >> >> You canna change the laws of physics, Captain; I've got to have thirty >> minutes! >> >> >
Re: Stretch System Stops Boot Process Immediately After Grub Screen
I have to use the nomodeset from time to time where the f*** gfx card has unresolved issues with itself. Atleast it lets me boot to a prompt. Now thinking of it, I have no blinking cursor, I just get a black screen... So different issue all together and I am just rambling on On Sun, Oct 23, 2016 at 7:03 PM, Michael Lange wrote: > On Sun, 23 Oct 2016 12:14:39 -0400 > "James P. Wallen" wrote: > > > Double checked to see if I was right about the video subsystem. > > It is not ATI, it is Intel integrated. No docs on this thing. It > > was never officially sold in U.S., where I live currently. Since > > I can't boot it to usable state, I can't (easily) find out > > exactly which video it uses. > > > > It's probably destine for re-installation anyway. I was just > > surprised to see such a failure occur after upgrade. > > If the device has worked with other kernel versions before, you > could boot from an USB drive, do a chroot and install a kernel that > works, this should be a pretty straightforward procedure. > > Regards > > Michael > > > > .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. > > You canna change the laws of physics, Captain; I've got to have thirty > minutes! > >
Re: Stretch System Stops Boot Process Immediately After Grub Screen
On Sun, 23 Oct 2016 12:14:39 -0400 "James P. Wallen" wrote: > Double checked to see if I was right about the video subsystem. > It is not ATI, it is Intel integrated. No docs on this thing. It > was never officially sold in U.S., where I live currently. Since > I can't boot it to usable state, I can't (easily) find out > exactly which video it uses. > > It's probably destine for re-installation anyway. I was just > surprised to see such a failure occur after upgrade. If the device has worked with other kernel versions before, you could boot from an USB drive, do a chroot and install a kernel that works, this should be a pretty straightforward procedure. Regards Michael .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. You canna change the laws of physics, Captain; I've got to have thirty minutes!
Re: Stretch System Stops Boot Process Immediately After Grub Screen
Double checked to see if I was right about the video subsystem. It is not ATI, it is Intel integrated. No docs on this thing. It was never officially sold in U.S., where I live currently. Since I can't boot it to usable state, I can't (easily) find out exactly which video it uses. It's probably destine for re-installation anyway. I was just surprised to see such a failure occur after upgrade. On 10/22/2016 06:10 PM, Jape Person wrote: I've got a little Panasonic CF-R3 mini-laptop which has been kept fully up-to-date in testing every day since Etch was released. (I think the original installation is that old.) I've been using the linux-image-686-pae kernel on the system. The updates today included an update to linux-image-4.7.0-1-686-pae (4.7.8-1) and grub-pc (2.02-beta3-1). Upon reboot the system stops with a blinking underline cursor in the upper left corner. I suspect that the boot process stops immediately after grub. I cannot connect via ssh or even ping the system. Using Ctrl-Alt-Del has no effect, but touching the start-stop switch elicits a beep and immediate power-down. The same results are obtained if I use the grub menu to select recovery mode. A much older desktop system running testing and the same kernel was not adversely affected. I'm only reporting this for purposes of corroboration in case anyone else has seen something similar coincident with these updates. I'm in the midst of some business which will prevent me from delving into the failure right now. I'll get into it some time next week, perhaps. I'm planning to make a couple of different live images on USB keys so that I can boot the failed system to examine it and see if there's anything I might just fix on it. There were no error messages during the upgrade. I'm a bit more inclined to suspect the kernel upgrade than the grub-pc upgrade. This little unit has a strange hybrid video subsystem which shares system memory with the video subsystem. Everything on the system is early Intel Centrino era stuff, but with the video being ATI. Maybe it's weird enough that it caught a corner case with the kernel change. But the system has been in the rolling-upgrade mode for years, so something odd may have happened to grub-pc itself. I suppose chroot to the system drive and running update-grub is worth a shot. If anyone has a suggestion, I'm willing to try to learn. As I said, it will be a little while before I have time to actually dig into it. In the off chance I actually learn something, I'll post back to the thread. Thanks, JP
Re: Reconfiguring grub2 UFEI system
Le 22/10/2016 à 23:17, Mark Neidorff a écrit : On Friday, 10/21/16 10:19:47 PM Pascal Hambourg wrote: What is the output of "os-prober" ? No output. (yes, I ran it as root) Then no other system was detected and added to the GRUB menu when you ran update-grub. Are you sure the GRUB that shows up is the one from Debian ? I'm not sure how to answer that question. The first OS I installed was OpenSUSE. Then I installed Debian 8.6 twice (on the two separate drives in the system). All three of these entries are still there even after running update-grub. I wouldn't care about the extra entries except that the OpenSUSE entry is the default. Is openSUSE the first entry in the menu ? AFAICS, by default the first entry in the menu is the OS which installed the active GRUB. So it looks like it is openSUSE's GRUB, not Debian's one. From Debian, what it the ouput of the following commands ? efibootmgr ls /boot/ ls /boot/efi/EFI
Re: Is possable to use mipi-csi interface on debian?
On Sun, Oct 23, 2016 at 04:24:44PM +0800, yongjie...@gmail.com wrote: > Hi, > > Is possable to use mipi-csi interface on debian? and howto? Are there any > someone can share more information? Thank you. > Yes. The Raspberry Pi's camera interface is supported by PiCamera and V4L2. Other MIPI-CSI cameras have drivers, too; there isn't (as far as I know, could easily be wrong) a fully generic kernel module at this time. http://elinux.org/Jetson/Cameras should be helpful. Once you have a working camera driver for V4L2, most video programs in Debian should work smoothly. -dsr-
Re: Reconfiguring grub2 UFEI system
Em sábado, 22 de Outubro de 2016 22:17:35 WEST, Mark Neidorff escreveu: On Friday, 10/21/16 10:19:47 PM Pascal Hambourg wrote: Le 21/10/2016 à 20:56, Mark Neidorff a écrit : > So, the next step was to clean out the other distros. I used gparted to > delete no longer needed partitions and to expand other partitions to fill > the space. All is now good. > > I then ran > > #update-grub > > hoping that would regenerate the grub boot menu, (I also tried > #update-grub2) but the old entries still appear when the system boots. Are you talking about entries in GRUB's menu or in the UEFI boot menu ? Grub menu. (I don't see a UEFI menu) update-grub only updates the former. Good. What is the output of "os-prober" ? No output. (yes, I ran it as root) Are you sure the GRUB that shows up is the one from Debian ? I'm not sure how to answer that question. The first OS I installed was OpenSUSE. Then I installed Debian 8.6 twice (on the two separate drives in the system). All three of these entries are still there even after running update-grub. Have you mounted the EFI partition? Update-grub change grub, I don't think it changes the FIE partitions. And check motherboard bios/uefi for the default entry I wouldn't care about the extra entries except that the OpenSUSE entry is the default. I want Debian to be the default (and, yes there is only one instance of Debian installed). Yes I tried changing the value of the default before I ran update-grub, but that didn't help. Thanks for any help, Mark Bandarra -- Enviado do Dekko através do meu dispositivo Ubuntu.
Is possable to use mipi-csi interface on debian?
Hi, Is possable to use mipi-csi interface on debian? and howto? Are there any someone can share more information? Thank you. Best Regards, Ethan
Fwd: Re: Compositing Problem
Forwarded Message Subject: Re: Compositing Problem Date: Thu, 20 Oct 2016 09:22:29 +0200 From: Maximiliano Curia To: Debian NVIDIA Maintainers CC: debian-...@lists.debian.org, 841...@bugs.debian.org, Jimmy Johnson Control: tag -1 + help ¡Hola NVIDIA Maintainers! It seems that the new plasma version has some kind of incompatibility with the nvidia-legacy-304xx packages in sid. The following mail reports that using the nvidia packages from backports works as expected. In the kde team we are not using nvidia cards, so we can't reproduce/test this. And frankly, this might be way out of our league. :( Thus the request for help. Is this issue known to you? Should this bug be reassigned to the nvidia packages? Can you reproduce it? If so, can you point us to what the problem might be? Happy hacking, El 2016-10-19 a las 23:33 -0700, Jimmy Johnson escribió: On 10/12/2016 12:10 PM, David Baron wrote: Running must recent kwin, etc., with Sid nvidia-legacy-304xx driver. Window decorations slow or do not show on non-KDE windows. If they do not show, one can pretend they are there and do everything. Effects all compositing options. Where to file bug? Quick fix? Quick fix, force install all your 'nvidia' and 'glx' installed packages back to 'Jessie-backports' and then 'lock-them' works, maybe 20-24 packages that you will be locking, varies a little with my installs, some I had not upgraded and I only had to lock the packages. I used synaptic while in xfce4 and all your kde apps work from xfce4 too as a side note. Note no problem with upgrades and those files being locked, at this time anyways. hehe There's a lot noise out there about fix's, I found nothing works for me. I came up with this fix and it works. While gtk works with the upgrade, plasma don't, it's a problem with plasma, you can't blame nvidia and say they are not doing their part, this is a problem debian plasma, I'm sure they are working on it. Seems to affect only 'legacy-304' and could be a simple code error. With the Debian-nvidia driver: Plasma is unable to start as it could not correctly use OpenGL2. Note dialog is working, sound is working, no plasma. With the Debian-free driver, computer freeze with colorful squiggly lines and I have to push the power button and repair the file system. David, do you have a better fix than down-grading the packages? And I may not need to down grade as many packages as I do, but it works. I unlocked 'libgl1-mesa-glx' so I could upgrade the 3 'mesa' packages of same version, with no ill effects and got a full, clean upgrade. Currently I have 23 nvidia+glx packages locked and all is well. -- Jimmy Johnson Debian Sid/Testing - KDE Plasma Version 5.8.2 - EXT4 at sda18 Registered Linux User #380263 signature.asc Description: PGP signature
