Debian :: Wheezy To Jessie Upgrade Will Not Boot
May 28, 2015
With "quiet" removed from the grub linux line, I'm getting the following error messages when the boot hangs up early in the boot process (19.768231 seconds into boot).:
input: HDA NVidia HDMI/DP,pcm=3 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input6
input: HDA NVidia HDMI/DP,pcm=7 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input7
input: HDA NVidia HDMI/DP,pcm=8 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input8
So, is this a NVidia issue or a sound card issue?
View 1 Replies
ADVERTISEMENT
Aug 13, 2014
I upgraded from deb7 to deb8, but am no longer able to boot. After passing the grub boot menu, the following messages are displayed:
Code:
Select allLoading, please wait...
[ 6.065713] systemd-fsck[148]: /dev/sda1: clean, 428644/1310720 files, 410616
9/52442880 blocks
[ 7.480551] Error: Driver 'pcspkr' is already registered, aborting...
[ 8.692700] systemd-fsck[341]: /dev/sda5: clean, 145485/6176768 files, 17407409/24695552 blocks
[ 18.066215] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated). Use CAP_NET_ADMIN and alias netdev- instead
_
The screen then clears and an underscore is displayed as the sole character at the top left position of the screen. The system hangs at this point. During installation, I rejected two changed files: /etc/init.d/bootlogd and /etc/libreoffice/sofficerc. For both, I opted to keep the installed version (the default choice of the installer) rather than replacing with the new version. The first might be related to the problem, although it seems to be responsible only for logging the boot process, and I would not expect this to compromise booting.
In case this information is useful, sda1 is mounted at /, sda2 is swap space, sda3 is extended, and sda5 is a logical partition mounted at /home.
I am able to boot into rescue mode, but other than that the system is not usable. Unfortunately, no useful error messages are given to aid in diagnosing the problem.
View 12 Replies
View Related
May 27, 2015
I upgraded my Wheezy 7.8 to make sure all packages were installed Before taking the next step to upgrade to Jessie.I upgraded to Jessie and it seemed to run OK....but after reboot I had no network Connection..I checked ifconfig and the wrong network card mac address is being assigned to the wrong card....?I have a clonezilla server on my server, so this was my network interfaces before and after upgrade
Code: Select all# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
[code]...
I even checked nano /etc/resolv.conf and sure enough my gateway was the same for my Internet eth0.When I ran ifconfig I could see that the eth0 mac address was set as eth1..I tried to reset my drbl for clonezilla but that only sees the vmware Connection and not my actural cards.. have taken alook at /etc/udev/rules.d/70-persistent-net.rules and the assignment is right but not ifconfig?
View 14 Replies
View Related
Jul 28, 2015
is it possible to simulate upgrading a Squeeze installation to a Wheezy or Jessie installation, on a OVH server ?I would like simulate upgrading server, and if not problems, upgrading in real time.I don't do that manipulation, and I don't do mistakes on a production server.
View 2 Replies
View Related
Jul 26, 2015
I have upgraded my debian server on april when Jessie came up, but I *forgot* to reboot at this time. As a new kernel* was released this week as a security update, and since my server installed it (via unattended-upgrade on security packages), I rebooted it last night. It never came back online.
I have access to a rescue boot (Ubuntu 12.04 LTS), and tried to analyse the failure (by mounting /sys /dev /proc and /boot and chrooting), but without luck so far.
As it's a dedicated server, I don't have access to the console. What I know :
No log in var/log since the failed reboot. I don't know how to have/find others logs.Previous kernel was 3.2.0-4-amd64, new is 3.16.0-4-amd64, What I tried without luck) :
Change the booting kernel, via update-grub. Tried 3.2, 3.2 with sysvinit and 3.16 rescue mode I think. I should have done it right, but without console it's hard to tell.apt-get update/apt-get upgrade/apt-get dist-upgradeadding nomodeset to kernel load in grubWhat I haven't tried :
update-initramfs, I don't really know why it would block the boot
*linux-image-3.16.0-4-amd64:amd64 3.16.7-ckt11-1+deb8u2
View 6 Replies
View Related
Jun 2, 2015
I've changed my /etc/apt/sources.lst file to use "jessie" repositories instead of "wheezy". I then ran synaptic and updated everything (there were loads of packages, something like 2000 to update).
After this I rebooted. The grub menu shows as usual with the background image I'd set and the operating systems as usual (including Windows 7) however there is no longer a 5 second countdown and when I select *any* menu option, it asks for a username and password.
I don't know what username and password it's asking for as I never used to have one set!!! I did have a username and password set up so that if you wanted to edit a grub menu option so I tried that but to no avail.
I'm using MBR/BIOS not EFI.
View 3 Replies
View Related
Nov 19, 2014
I have done on previous releases, but this time it hangs on me. It's "only" a Virtualbox, so I can reproduce it.
The wheezy already runs systemd, and is fully updated to to latest packages. Does not run any graphical.
Edits the source.list and does
$ apt-get update
$ apt-get upgrade # Did on one upgrade
$ apt-get dist-upgrade
It starts to upgrade (complains about missing version in libpgp-error), libc is installed, but at some point the systemd is running at high CPU and a dpkg seems to be stalled.
Should I disable systemd on wheezy before? This might not have been tested so much.
View 10 Replies
View Related
Feb 9, 2016
Does upgrade from wheezy to jessie modify print drivers....
View 1 Replies
View Related
May 19, 2015
I've had a weird issue recently with Java/Spring. Basically, it would work on all machines but my trusty Debian box. Macs for devs, Ubuntu for production and some devs have it too. This annoyed me, because of course Debian is the greatest and it must work there too! Also, Java is based on the whole write once run anywhere concept, I have never really had a problem with code behaving differently on different Java installs of the same version, even on completely different OSs it seems to behave itself very well. URL....
I moved up to Jessie and the problem goes away. I can only conclude that some library that is called by Java got upgraded, somehow influences the order in which Spring resolves its dependencies. Probably the fact that other devs build on Ubuntu and have got it working there, and the upgrade to Jessie brings my libs more in line with what Ubuntu will be running has done the trick.
View 0 Replies
View Related
Jun 20, 2015
I already have a Notebook with windows (for some reason it needs 3 partitions..) and wheezy. When I installed wheezy I create 2 logical partition inside a primary one: one logical for /home and the other one for filesystem. Now I would like to overwrite wheezy and get get jessie, but without touching windows and home.
I already try to upgrading and it went wrong, so I prefer overwrite, what I have to do during "manual installation" phase?
View 11 Replies
View Related
Jan 22, 2015
I upgraded to Jessie today and found that I have no sound.
Code: Select all# uname -a
Linux ath 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) x86_64 GNU/Linux
There is no sound card on the motherboard. Sound worked previously through HDMI from a Nvidia GTX570
Code: Select all# lspci|grep Audio
09:00.1 Audio device: NVIDIA Corporation GF110 High Definition Audio Controller (rev a1)
Code: Select all# aplay -l
aplay: device_list:268: no soundcards found...
[code]....
View 8 Replies
View Related
May 11, 2015
A few days ago I bought a Raspberry PI B with Debian Wheezy (7.0 - I think) on it. Before installing a media centre on it I wanted to do some basic configuration/upgrade and decided to upgrade to Debian Jessie. I followed the instructions provided on [URL] .....
Before moving to Jessie I have upgraded the original Wheezy; after the upgrade the version was 7.8. Everything went well till I executed "apt-get dist-upgrade". Errors where generated. As suggested I tried the "apt-get -f install"; but it did not go smoothly either. However, so far, I am accessing the desktop and everything seems fine (although I did not do anything fancy yet). The version recorded is 8.0. Thus, should I worry about the error messages generated?
Please find the log file here: [URL] ......
Note that I put the log file on Google Drive because each time I clicked on "add file" in the "Upload Attachment" tab when editing this message I got:
Internal Server Error:
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, forum-admin@forums.debian.net and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
View 7 Replies
View Related
Apr 27, 2015
I did an in-place upgrade to Jessie today and I can only get the GNOME Classic desktop, which I have to select when I log in. I had started to get used to the default desktop in Wheezy, so I'd like it back if possible. When I select gnome system default, I get my desktop, but no menus or anything I can click on at all. All I can do is ctrl-alt-delete and reboot or shutdown. I run it on a Lenovo Ideapad U410.
View 8 Replies
View Related
Sep 9, 2015
I am using a 3rd party kernel driver that does not support udev properly. When I was using wheezy I placed the required device files in /lib/udev/devices.
The udev in jessie does not appear to support this. Is there any way to have udev create these device files or will I have to create then using a script at boot-up?
View 1 Replies
View Related
Dec 25, 2014
I just installed wheezy and upgraded to jessie. I had previously gotten sound working in wheezy by installing the flashplugin-nonfree and flashplugin-nonfree-extrasound packages, after configuring my headset in system settings. However, now I can't get sound to play in firefox. I've installed flashplugin-nonfree, flashplugin-nonfree-extrasound, and pulseaudio, still without luck. The volume is turned all the way up in alsamixer, sound tests play fine, and I can play music in VLC without any problems. This leads me to believe it's not a problem with drivers, but with some package I'm missing that will allow firefox to play sound. Sound wasn't working in the default video player either, before I installed the flash plugin. Is there something I'm missing?
Also, sound doesn't play on Konqueror either (KDE browser), which seems to indicate it's a problem with flash and not with firefox itself. After removing the flash plugin and installing pepperflashplugin-nonfree to ensure the pepper plugin was used instead of flash, sound still would not play in chromium, so I reinstalled the flash plugin and still don't have sound in any browser.
View 1 Replies
View Related
Aug 7, 2015
Used to be, when I connected my phone and turned on USB Storage, it would automount, and I'd get a popup window asking me what I wanted to do (open and view files, or import photos with gthumb). I would just choose open and view files, move photos, music, etc. back and forth...
I would see the device listed in pcmanfm or thunar. Now, nothing happens. I do not get the popup, nor see the device in any file manager, etc. When I do fdisk -l, I do not see the phone listed, but when I do lsusb, I do see it.
Code: Select allBus 008 Device 067: ID 0482:0734 Kyocera Corp.
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
It's a Kyocera Hydro Elite, an android device, set for USB Mass Storage upon connection. The phone knows when it's been connected and gives me the option to turn on the mass storage, which used to trigger the popup on the computer, but the computer no longer responds.
I have thunar-volman and mtp-tools installed.
I don't seem to have any relevant entry in /etc/fstab. Not sure if I did before upgrading to jessie from wheezy or not... I don't believe so...don't think an upgrade would wipe anything from there.
Why I'm not getting access to the phone now? Or how I can mount it without knowing it's location from fdisk? I do not use gnome, but rather plain openbox.
View 12 Replies
View Related
May 8, 2015
I run Debian with Gnome on a beat up workhorse ThinkPad. I upgraded to Jessie last week with just one issue. Before the upgrade, I could plug in a USB drive (I use a couple of WD MyPassports most often) and they would mount, read, and write without a hitch.
Since the upgrade, when I plug in a USB drive, the file manager (3.14.1) sees the drive, but when I click on the drive to access/mount it, I receive a dialog box reading: Oops! Something went wrong. Unhandled error message: Error when getting information for file '/media/user/MyPassport1': Input/output error.
If I hit the little “eject” button in the file manager, then mount the drive as root from a command prompt [e.g., mount -t ntfs-3g /dev/sdb1 /media/external] I can run a directory of the drive, but ls -l /media/external fails. From the command prompt I am unable to perform reads or writes to the drive.
Rebooting into recovery mode (i.e., without Gnome), I get the same behavior with CLI messages reporting I/O errors with the drive. I can run a directory, but ls -l, reads, and writes fail.
This behavior is the same on all three USB ports. It is not limited to these MyPassport devices.
The drives work flawlessly on another headless machine upgraded to Jessie the same day. And on another still running Wheezy.
If I boot the ThinkPad from a live CD (Mint 14, I believe) the USB drives mount, read, and write fine.
My BIOS is up to date, 1.52.
lspci -v says this about USB ports:
Code: Select all00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) (prog-if 00 [UHCI])
Subsystem: Lenovo Device 20f0
Flags: bus master, medium devsel, latency 0, IRQ 23
I/O ports at 1880 [size=32]
Capabilities: [50] PCI Advanced Features
Kernel driver in use: uhci_hcd
[Code] .....
View 4 Replies
View Related
May 20, 2011
I got "stuck" with stable up to now and want to upgrade to Wheezy. But, although I've done this before, I'm having a dependency problem I wanted to ask about before breaking my system somehow. This is the /etc/apt/sources.list, ready for Wheezy:
[URL]
So, I regularly use aptitude as my package manager. After updating the database with aptitude update, trying aptitude full-upgrade gives me a huge of conflicts.
[code]....
But, if I use apt-get dist-upgrade, I get no conflicts. if I dist-upgrade with apt-get, will that affect my daily usage of aptitude (which I prefer)? I know APT is a single database and apt-get and aptitude are just different interfaces, but I guess differences might rise when marking packages as automatically or manually installed.
View 7 Replies
View Related
Jun 9, 2011
I upgraded one of my Squeeze installations to Wheezy, but after selecting it in grub, nothing is displayed on screen: no CLI and no GUI. I tried Ctrl + Alt + F[1-7] and I got nothing. My laptop is Acer Aspire 7715Z. I am attributing this to module as there seems to be disk activity, but without a screen, I cannot be certain.
View 14 Replies
View Related
Jan 17, 2014
Sound is not working perfectly since installation. I fixed it by command: 'alsactl init' every time sound doesn't come out. However, since last week, sound was not working. I suspect it was caused by the 'apt-get upgrade' I did.
Code: Select allroot@debian:~# alsactl init
alsactl: init:1743: No soundcards found...
lspci (only audio)
Code: Select allroot@debian:~# lspci -v
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS7012 AC'97 Sound Controller (rev a0)
Subsystem: Micro-Star International Co., Ltd. Device b002
[Code] ....
It seems I am missing a module/ kernel driver for the sound card
Note: I have testing in sources list but have stable with higher priority. So I should still be in Wheezy
View 5 Replies
View Related
May 4, 2015
i have an installation of wheezy 7.8 i think. i was facing difficulties in read of matroska video. therefore have decided to installer gstreamer1.0 wich should be resolve my problem. i have added the backports repository in apt sources list. after an apt-get update i launch apt-get install gstreamer1.0 . i have noticed it have starting downloading more file than it needs i concluded that it was a upgrade or something like because the kernel was also updated. after the the packet downloading it has started the installation with some errors related to LOCALE LCC. it has stopped and restarted some services wich is normal. i have closed all others apps and restarted. Here start the hell. after the restart i have passed the kde login screen and after BLACK SCREEN with mouse working.
Alt+F2 don't open the krunner
What i have tried? i have rename the /home/jefcolbi/.cache and back it again, rename /home/jefcolbi/.kde and back it again. next i have tried to check the Xorg config file. i created a new one with X -configure, modified it to feet my system configuration this does not resolve the problem but add another the keyboard is not working in graphical mode.
My system configuration:
Toshiba laptop Satellite Pro L300
Dual core
3gb Ram
graphic card:Mobile Intel(R) GMA 4500MHD
sound card: Intel HD Audio
debian whezzy 7.8 with KDE
Note: everything was working fine before trying to install gstreamer1.O from backports repository
View 3 Replies
View Related
Mar 3, 2016
Recently I upgraded my machine from wheezy to jessie.
Everything went smooth until the point that I restarted the node.
During startup I'm getting the following message which is flooding the screen:
Code: Select allsystemd-journald[296]: Failed to forward syslog message: Connection refused
After waiting a long time (the message above still continues to flood the screen), I'm being prompted with the following:
Code: Select allGive root password for maintenance (or type Control-D to continue):
If I press Ctrl+D the boot process continues and finally boots normally.
What I can do to avoid pressing Ctrl+D during the boot process?
I'm assuming that it must be a startup service which is failing but I'm unable to trace which exactly is that.
I'm attaching the full log [URL] ....
View 8 Replies
View Related
Nov 17, 2014
I'm on Wheezy with version 304.117 of the proprietary nvidia driver installed and working, but an application I have needs a newer version of the driver. I'm trying to install the 319.82 version in backports by following the instructions given here, but when I issue the command to install nvidia-kernel-dkms, I get the following:
Code: Select all> sudo aptitude -t wheezy-backports -r install nvidia-kernel-dkms
The following NEW packages will be installed:
libgl1-nvidia-glx-i386:i386{a} nvidia-driver{a}
The following packages will be REMOVED:
libgl1-nvidia-alternatives{u} libglx-nvidia-alternatives{u}
libxvmcnvidia1{u} nvidia-glx{u}
The following packages will be upgraded:
glx-alternative-nvidia glx-diversions libgl1-nvidia-glx
libgl1-nvidia-glx:i386 libnvidia-ml1 nvidia-alternative
nvidia-installer-cleanup nvidia-kernel-dkms nvidia-settings
nvidia-smi nvidia-vdpau-driver xserver-xorg-video-nvidia
The following partially installed packages will be configured:
mint-flashplugin-11:i386
12 packages upgraded, 2 newly installed, 4 to remove and 151 not upgraded.
Need to get 32.3 MB of archives. After unpacking 9,440 kB will be freed.
The following packages have unmet dependencies:
glx-alternative-mesa : Depends: glx-diversions (= 0.2.2) but 0.5.1~bpo70+1 is to be installed.
Internal error: found 2 (choice -> promotion) mappings for a single choice.
Internal error: found 2 (choice -> promotion) mappings for a single choice.
The following actions will resolve these dependencies:
Remove the following packages:
1) glx-alternative-mesa
2) glx-alternative-nvidia
3) libgl1-nvidia-glx
4) libgl1-nvidia-glx:i386
5) nvidia-alternative
6) nvidia-kernel-dkms
[Code] ....
Accept this solution? [Y/n/q/?] q
The mint-flashplugin problem is a separate issue which I've had for a while. I assume that it can be ignored for the purposes of this post.
If I'm reading the aptitude output above correctly, it's telling me that the only way to "resolve" the conflict is by uninstalling all nvidia support, leaving me with no driver at all. Is that right?
View 2 Replies
View Related
Jun 25, 2015
I installed a Debian server a few time ago, with the Squeeze version.
Now I want to upgrade it to Jessie, but all related documentation only talk about the procedures to upgrade from Wheezy to Jessie.
What should I do? Upgrade first Squeeze to Wheezy and after that to Jessie, or I can upgrade from Squeeze to Jessie?
View 3 Replies
View Related
Jun 3, 2015
/var/log/syslog is full of messages
/etc/gdm3/Xsession[3408]: ![1433316153,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] #011ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1
What this means and how to fix it?
View 4 Replies
View Related
Jul 3, 2015
I installed a package (kicad) on my wheezy system using apt-get and it pulled down a shedload more files than I expected.When I restarted the system it turns out I've also been upgraded to
Release 8.0 Jessie
Kernel Linux 3.2.0-4-amd64
GNOME 3.4.2
However I don't have gnome any more. Only XFCE.I tried
Code: Select allroot@client:~# apt-get install gnome
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 packages have unmet dependencies:
gnome : Depends: gnome-core (= 1:3.14+3) but it is not going to be installed
Depends: evolution (>= 3.12) but it is not going to be installed
Depends: evolution-plugins (>= 3.12) but it is not going to be installed
Depends: gnome-shell-extension-weather but it is not going to be installed
Recommends: gnome-software but it is not installable
E: Unable to correct problems, you have held broken packages.
My /etc/apt/sources.list is
Code: Select all#
# deb cdrom:[Debian GNU/Linux 7.7.0 _Wheezy_ - Official amd64 NETINST Binary-1 20141018-13:04]/ wheezy main
#deb cdrom:[Debian GNU/Linux 7.7.0 _Wheezy_ - Official amd64 NETINST Binary-1 20141018-13:04]/ wheezy main
deb http://mirror.waia.asn.au/debian/ wheezy main
deb-src http://mirror.waia.asn.au/debian/ wheezy main
[code]....
View 14 Replies
View Related
Jan 18, 2016
Using x11vnc server on Debian host, and TightVNC viewer client on Windows 7. All was working fine until a server host upgrade, from Wheezy to Jessie. Now, when I try to connect, TightVNC retrieves the certificate as normal, compares and accepts it, and starts stunnel. The next step would normally be to prompt for the VNC password.
Instead it gives an error:
ReadExact: Socket error while reading.
I'm guessing that some thing is missing or misconfigured after the Jessie upgrade, which broke many other things too, as Debian upgrades always seem to do. I have removed and reinstalled the x11vnc package, no effect.
The errors in the log file don't mean a lot to me.
The server is started with this command:
Code: Select allx11vnc -ssl -display :0 -usepw >>vnc-log 2>&1 &
If I start it up without the -ssl flag, and connect from the Windows system with a different client (Mobaxterm) it all goes well.
Relevant part (tail) of the server log file:
Code: Select allThe SSL VNC desktop is: myhost:0
PORT=5900
SSLPORT=5900
19/01/2016 12:31:10 SSL: accept_openssl(OPENSSL_VNC)
19/01/2016 12:31:10 SSL: spawning helper process to handle: 192.168.2.3:51942
19/01/2016 12:31:10 SSL: helper for peerport 51942 is pid 11193:
19/01/2016 12:31:10 connect_tcp: trying: 127.0.0.1 20000
[Code] ....
View 0 Replies
View Related
Aug 22, 2015
X won't start (awesome WM) after upgrading to jessie. It seems to startup up, then just stops. I'm running startx from the command line after logging in. The xorg log (bottom) looks good and I see an exit code of zero.
I do see this in sysout:
Code: Select alldebian xf86TokenToOptinfo: table is NULL
Googled around but I can't find anything specific on this one.
I'm not using any xorg.conf, as booting into a linux rescue cd everything works ok
Code: Select all[ 2275.960]
X.Org X Server 1.16.4
Release Date: 2014-12-20
[ 2275.960] X Protocol Version 11, Revision 0
[ 2275.960] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[ 2275.960] Current Operating System: Linux jj 3.14.25 #1 SMP Fri Dec 5 10:17:33 EST 2014 x86_64
[Code] .....
View 2 Replies
View Related
Dec 23, 2015
After upgrade no sound. I tried "alsactl init" fix and that worked for awhile. Now even that isn't working.
Also tried the following:
# /etc/init.d/alsa-utils reset
[ ok ] Resetting ALSA...done.
# /etc/init.d/alsa-utils restart
# alsactl init
Found hardware: "HDA-Intel" "Realtek ALC898" "HDA:10ec0899,38421034,00100003" "0x1034" "0x3842"
Hardware is initialized using a generic method
View 14 Replies
View Related
Jul 2, 2015
Dell Vostro 230 with integrated Broadcom NIC.
Wakeonlan was working just fine with Wheezy on this machine. After upgrade, wakeonlan will resume from suspend but not from shutdown.
I have no problem with other machines (same software setup) after upgrade. None of my other machines have a broadcom NIC.
No BIOS settings were changed during the upgrade. If I enter the BIOS on boot and make sure settings are correct then 'save' and shutdown, without booting to debian, I can then successfully wakeonlan. Then, if I do not boot debian, but shutdown before debian starts, I can wakeonlan successfully again.
If I boot debian and then shutdown, game over: wakeonlan nolonger works.
$ ethtool eth0 | grep -i wake
Supports Wake-on: g
Wake-on: g
A bit of research found the suggestion:
$ lspci -tv | grep -i ether
+-1c.2-[02]----00.0 Broadcom Corporation NetLink BCM57788 Gigabit Ethernet PCIe
$ cat /proc/acpi/wakeup
Device S-state Status Sysfs node
P0P2 S4 *disabled
P0P3 S4 *disabled
[Code] ....
How to get wakeonlan working under Jessie with a Broadcom BCM57788?
View 8 Replies
View Related
