Yes. The news item needs to warn:
** Warning: if you take no action, upon the next boot you might
1. Not be able to network.
2. Not be able to see your screen.
3. Not be able to boot.
and thus unable to install the new packages to fix it too.
Therefore be sure to install the new packages ... now,
Package: firmware-misc-nonfree
Version: 20240709-1
> Several firmware files were moved from firmware-misc-nonfree into
> their own package
Are you sure that won't break networking for some people? Best to have a
transitional package that pulls in the rest, and leave it up to the user
to remove
Package: linux-image-amd64
dpkg: warning: while removing linux-image-6.8.11-amd64, directory
'/lib/modules/6.8.11-amd64' not empty so not removed
# ls -l /lib/modules/6.8.11-amd64
total 4
-rw-r--r-- 1 root root 55 05-27 14:48 modules.weakdep
update-initramfs: Generating /boot/initrd.img-6.6.9-amd64
cp: warning: behavior of -n is non-portable and may change in future; use
--update=none instead
cp: warning: behavior of -n is non-portable and may change in future; use
--update=none instead
cp: warning: behavior of -n is non-portable and
Package: firmware-misc-nonfree
Version: 20230625-1
Saw tons of these.
Unpacking firmware-misc-nonfree (20230625-1) over (20230515-3) ...
dpkg: warning: unable to delete old directory '/lib/firmware/wfx': Directory
not empty
dpkg: warning: unable to delete old directory '/lib/firmware/ueagle-atm':
update-initramfs: Generating /boot/initrd.img-5.16.0-6-amd64
W: No zstd in /usr/bin:/sbin:/bin, using gzip
Shouldn't it just not remind the user?
Please have upstream fix this soon. Thanks.
Package: src:linux
Version: 5.4.19-1
No idea where to report this.
# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.4.0-4-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module
r8169
Package: initramfs-tools-core
Version: 0.135
Severity: important
$ aptitude full-upgrade gives thousands of identical
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open
builtin file '/lib/modules/5.4.0-2-amd64/modules.builtin.bin'
depmod: ERROR: ../libkmod/libkmod.c:515
Kernel install warns
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module
r8169
unmerge 925891
retitle 925891 AMD/ATI Carrizo driver incorrectly detected?
thanks
Now making the incorrect driver detection a separate issue.
All I know is with that minimal install, it somehow assumes the correct
driver is present, or it is, but it uses it wrong. See also
https://wiki.debian.org
clone 926149 -1
retitle -1 [AMD/ATI] Carrizo driver incorrectly detected
retitle 926149 Add nomodeset kernel parameter for recovery boot grub entry
thanks
> "BH" == Ben Hutchings writes:
BH> However it might be reasonable to add "nomodeset" to the command line
BH> in GRUB's "recovery" boot m
> However it might be reasonable to add "nomodeset" to the command line
> in GRUB's "recovery" boot menu items.
OK, great. Now all that is left is for me to help you figure out why
the installer incorrectly detects that the drivers are available, etc.
I am able to workaround all this, I just want
B> However it might be reasonable to add "nomodeset" to the command line
B> in GRUB's "recovery" boot menu items.
OK, great. Now all that is left is for me to help you figure out why
the installer incorrectly detects that the drivers are available, etc.
I am able to workaround all this, I just wa
And lo and behold, in /etc/grub.d/10_linux :
if [ "$ubuntu_recovery" = 1 ]; then
GRUB_CMDLINE_LINUX_RECOVERY="$GRUB_CMDLINE_LINUX_RECOVERY nomodeset"
fi
> "BH" == Ben Hutchings writes:
BH> The installer normally uses a dumb framebuffer driver (probably efifb
BH> on this system) that is built into the kernel. This is too low-
BH> performance for a proper desktop.
OK, the installer could first double check that the framebuffer driver
it inten
So the question becomes why does that installer ISO know how to properly deal
with the
BH> 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Carrizo [1002:9874] (rev e6)
BH> Subsystem: ASUSTeK Computer Inc. Device [1043:8719]
giving nice splash screens, a sna
BH> Please send the output of "lspci -vnn" for the system that shows this
BH> problem.
Would lspci -knn be good enough for now?:
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=0;bug=925556;filename=logs.gz;msg=50
Doesn't happen every time, only sometimes.
# egrep init.*Genera\|Log\ started /var/log/apt/term.log
Log started: 2018-09-23 09:51:40
update-initramfs: Generating /boot/initrd.img-4.18.0-1-686-pae
update-initramfs: Generating /boot/initrd.img-4.18.0-1-686-pae
term.log.gz
Description: applicatio
Preliminary results show that the video=SVIDEO-1:d boot line workaround
is working...
rename 906310 vblank wait timed out on crtc 0
thanks
It turns out this is just still the
vblank wait timed out on crtc 0
bug seen on kernels later than 4.15
syslog.gz
Description: syslog
Xorg.0.log.gz
Description: Xlog
I created https://gitlab.freedesktop.org/xorg/app/xrandr/issues/40 .
Package: src:linux
Version: 4.17.14-1
I discovered that the user needs to use xrandr in _two_ steps for
certain resolutions, else he will make his system unusable, needing to
be rebooted, probably after minutes of pressing sysrq...
# egrep initial\ m\|stride /var/log/Xorg.0.log
[20.183] (II)
Package: src:linux
Version: 4.17.8-1
Just wanted to let you know that after about a half an hour browsing
Facebook with chromium, (I didn't try other browsers) the kernel always crashes.
There are never any logs to send. The system just freezes for 10 seconds
and reboots. Nothing gets recorded ab
Happens in all of 4.16.
4.15 unaffected.
Problem turns out not to be related to xrandr.
Problem occurs when starting or stopping X windows.
OK: linux-image-4.16.0-1-amd64:amd64 4.16.5-1
Bad: linux-image-4.16.0-2-amd64:amd64 4.16.16-2
Package: src:linux
Version: 4.16.16-2
Severity: important
Problem occurs with
vmlinuz-4.16.0-2-amd64
No problem in
vmlinuz-4.15.0-3-amd64
Problem occurs if user puts
xrandr --output LVDS-1 --mode 1024x576
in his ~/.xsession
file.
Problem doesn't occur if user just invokes
xrandr --output LVDS-1 -
Package: linux-image-4.16.0-1-amd64
I am also experiencing:
https://unix.stackexchange.com/questions/442698/when-i-log-in-it-hangs-until-crng-init-done
OK now I did,
# aptitude install libelf-dev
The following NEW packages will be installed:
libelf-dev
The following packages will be REMOVED:
linux-headers-4.14.0-1-amd64{pu} linux-headers-4.14.0-1-common{pu} (D:
linux-headers-4.14.0-1-amd64)
And now the error is gone,
# aptitude reinstall
Package: initramfs-tools
Version: 0.130
Severity: wishlist
Showing the user warnings like
systemd-udevd[68]: hwdb.bin does not exist, please run systemd-hwdb update
in journalctl is bad, because according to e.g.,
https://bbs.archlinux.org/viewtopic.php?id=189536
there is nothing he can do about i
Maybe related to https://bugs.debian.org/875924 .
Package: src:linux
Version: 4.12.6-1
There is not enough information in these messages to determine what
package to assign this bug to.
# journalctl | grep -C 1 deprecated
Sep 16 09:10:48 jidanni6 kernel: ACPI: bus type USB registered
Sep 16 09:10:48 jidanni6 kernel: (NULL device *): hwmon_device
Package: initramfs-tools
Version: 0.130
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.12.0-1-amd64
W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays.
W: mdadm: failed to auto-generate the mdadm.conf file.
W: mdadm: please rea
Package: linux-headers-4.11.0-2-amd64
Version: 4.11.11-1
The following packages have unmet dependencies:
linux-headers-4.11.0-2-amd64 : Depends: linux-headers-4.11.0-2-common (=
4.11.11-1+b1) but it is not going to be installed
Today I suddenly see:
Processing triggers for initramfs-tools (0.129) ...
update-initramfs: Generating /boot/initrd.img-4.9.0-2-amd64
W: initramfs-tools configuration sets
RESUME=UUID=eff505d5-d5bf-4bba-8a07-f3d0d11018b9
W: but no matching swap device is available.
I: The initramfs will attempt t
BH> There is no log daemon for logger to talk to.
Err... I mean talk to the same thing that is saving them up to put them
into journalctl.
BH> initramfs-tools does not use systemd. If systemd is failing to log its
BH> output at boot time, that is not a bug in initramfs-tools.
OK I filed #852229 [systemd] failing to log output at boot time
BH> (I recognise that initramfs-tools should log output before it hands
BH> over to systemd (
BH> The delay is applied after every line that is logged, whether or not
BH> it's displayed on the console.
OK maybe they should warn about that in
/usr/share/doc/linux-doc-4.9/Documentation/kernel-parameters.txt.gz
And add a new parameter that only applies to ones that are shown on the
console.
Package: initramfs-tools
Version: 0.126
Severity: wishlist
You generate
/run/initramfs/fsck-root
/run/initramfs/fsck.log
Good.
Please also generate a similar log of the messages that the user sees
fly by upon boot before the ones that are captured by journalctl.
Actually it turns out they are no
Package: src:linux
Version: 4.8.15-2
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.8.0-2-amd64
root=UUID=50c0e259-55bb-4fc0-867e-63160edef01f ro single
systemd.log_level=debug systemd.log_target=kmsg log_buf_len=262144 enforcing=0
panic=33 earlyprintk=vga
worked fine. But if boot_delay=500 is
> "MH" == Marc Haber writes:
MH> Does /lib/ld-linux.so.2 exist on your system?
No.
MH> If not, the error message is correct. The kernel just knows that the
MH> interpreter given in the executable does not exist, it cannot give a
MH> more meaningful error message because lack of knowledge.
Package: src:linux
Version: 4.8.11-1
Severity: wishlist
Please give a more correct message, like 'incompatible binary version'.
Returning a not found error to shells is just plain misleading.
$ set who who2
$ for i in 'ls -l ' 'file ' './'; do $i$1; $i$2; done
-rwxr-xr-x 1 jidanni jidanni 51092 1
Package: src:linux
Version: 4.8.11-1
Severity: minor
Please check to see if /etc/modprobe.d really exists (it might not!) first.
Log started: 2016-12-23 22:37:09
Selecting previously unselected package linux-image-4.8.0-1-amd64.
(Reading database ... 9940 files and directories currently installe
OK now there is only the directory
/etc/kernel/signed_postinst.d/
left behind.
Package: initramfs-tools
Version: 0.126
Severity: minor
Unpacking initramfs-tools (0.126) over (0.125) ...
dpkg: warning: unable to delete old directory '/etc/kernel/signed_postinst.d':
Directory not empty
/etc/kernel/signed_postinst.d:
drwxr-xr-x 2 root 4096 12-20 04:20 .
drwxr-xr-x 7 roo
Hello, do I just purge these?
# aptitude search ~o~i~nfirm
i firmware-amd-graphics
i firmware-linux
i firmware-linux-nonfree
i firmware-misc-nonfree
i firmware-realtek
Won't my computer stop working?
All I know is "one may have noticed () vs. (())". I don't know how they
got there. So I am not the best person to write about it.
BH> The extra parentheses have no special meaning.
Well please document how they got there at least.
BH> What the documentation ought to mention is that a thread's name can
BH> be overridden using prctl(PR_SET_NAME, ...). Care to send a patch?
I have no kernel knowledge.
Package: linux-doc-4.8
Version: 4.8.5-1
Severity: wishlist
File: /usr/share/doc/linux-doc-4.8/Documentation/filesystems/proc.txt.gz
One only sees
tcomm filename of the executable
But no explanation of () vs (())
$ perl -anwle 'print $F[1]' /proc/[0-9]*/stat|sort -u|head
((sd-pam))
(Xor
Package: src:linux
Version: 4.8.5-1
Severity: wishlist
Setting up linux-image-4.8.0-1-686-pae (4.8.5-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.7.0-1-686-pae
I: /initrd.img.old is now a symlink to boot/initrd.img-4.7.0-1-686-pae
I: /vmlinuz is now a symlink to boot/vmlinuz-4.8.0-1-6
Sorry, at least Bug #842221,
dpkg-checkbuilddeps: error: Unmet build dependencies: openssl:native, and
# df /var/cache/apt/archives/ -h
Filesystem Size Used Avail Use% Mounted on
/dev/sdc2 3.1G 2.0G 1018M 66% /var/cache/apt/archives
mean I give up trying to make a .deb. Please send me
I forgot how to save the traceback to disk.
No... unplugging all USB and rebooting doesn't help.
Thanks. It's the Bad EIP value problem of
http://www.linuxquestions.org/questions/fedora-35/bad-eip-value-189710/
I will try unplugging all USB...
In the changelog it seems some detection of
Thinkpad r50e hardware (wifi) perhaps has been added.
causing
Blinking cursor at top-left corner / A plain black screen
as mentioned in
https://community.linuxmint.com/tutorial/view/842
Of course there are no logs available at this point.
Package: src:linux
Version: 4.7.8-1
Version: 4.7.6-1 works fine.
Version: 4.7.8-1 freezes with blank screen after printing two lines.
Thinkpad r50e.
Package: src:linux
Version: 4.4.4-2
Today I got a bug very much like
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764539
but without a custom kernel.
3月 15 10:17:23 jidanni2 swapon[310]: swapon: sys-utils/swapon.c:653:
parse_options: Assertion `ctl->discard' failed.
3月 15 10:17:23 jidanni
> "BH" == Ben Hutchings writes:
BH> I can't reproduce this, using either APT or direct invocation of dpkg.
BH> Please explain how you attempted to upgrade.
I always use aptitude full-upgrade.
Anyway on my jidanni2 machine I also find:
$ set /etc/initramfs-tools/conf.d /var/lib/initramfs-to
So can I delete them anyway?
> "BH" == Ben Hutchings writes:
BH> You've convinced me that this isn't a good way to handle the change.
Glad!
BH> What I intend to do is to add a third option, BUSYBOX=auto, with the
BH> old semantics of BUSYBOX=y, and make that the default. On upgrade you
BH> may be prompted to resolve co
You really need to put something else it its place fast.
Else users will end up with scrambled disks, and unable to boot.
Treat it like a virus.
Can't you just copy the previous kernel into a "4.3a" release?
That way the damaging kernel won't be the default anymore.
> "BH" == Ben Hutchings writes:
>> OK, but you are still going to run into problems if the user has set
>>
>> # apt-config dump|egrep Rec\|Sugg
>> APT::Install-Recommends "false";
>> APT::Install-Suggests "0";
BH> Users that do that need to accept that they will encounter errors like
BH> thi
> "BH" == Ben Hutchings writes:
BH> Wrong, initramfs-tools-core does (and initramfs-tools used to do so
BH> directly).
OK, but you are still going to run into problems if the user has set
# apt-config dump|egrep Rec\|Sugg
APT::Install-Recommends "false";
APT::Install-Suggests "0";
>>>>> "BH" == Ben Hutchings writes:
BH> On Mon, 2015-12-28 at 21:20 +0800, 積丹尼 Dan Jacobson wrote:
>> OK I find BUSYBOX=y.
>> But I don't think I ever tampered with that file.
BH> That is the default.
>> That means that ... you are going t
OK I find BUSYBOX=y.
But I don't think I ever tampered with that file.
That means that ... you are going to have a lot of people with problems
shortly...
B> Read the NEWS.
"You may need
to modify /etc/initramfs-tools/initramfs-tools.conf or install busybox
when upgrading."
$ ls /etc/initramfs-tools/initramfs-tools.conf
ls: cannot access /etc/initramfs-tools/initramfs-tools.conf: No such file or
directory
Maybe that means the default stat
Package: initramfs-tools
Version: 0.121~rc2
Unpacking initramfs-tools (0.121~rc2) over (0.120) ...
dpkg: warning: unable to delete old directory '/etc/initramfs-tools/conf.d':
Directory not empty
dpkg: warning: unable to delete old directory '/var/lib/initramfs-tools':
Directory not empty
$ ls
Package: initramfs-tools
Version: 0.121~rc2
Processing triggers for initramfs-tools (0.121~rc2) ...
update-initramfs: Generating /boot/initrd.img-4.3.0-1-686-pae
E: busybox is required but not installed
E: /usr/share/initramfs-tools/hooks/busybox failed with return 1.
update-initramfs: failed for
Will try Wednesday.
Actually better to have the raid people test. I only have one disk... too risky.
Rotational.
watch outscrambled data fsck forced can't boot stay away...
ata1.00: exception Emask 0x60 SAct 0x1c SErr 0x800 action 0x6 frozen
ata1.00: irq_stat 0x2000, host bus error
ata1: SError: { HostInt }
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/00:10:00:a8:10/08:00:26:00:00/40 tag 2 ncq 1048576 out
res 40/00:20:00:48:11/00:00:26:00:0
Package: src:linux
Version: 4.3.3-2
-- Package-specific info:
** Kernel log: boot messages should be attached
** Model information
not available
** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor
Family DRAM Controller [8086:0104] (rev 09)
Subsys
The first time it happened I couldn't boot again without a fsck.ext4 via
a rescue CD!
Package: src:linux
Version: 4.3.3-2
Severity: important
I am getting these errors (sort -u'd here) with linux-image-4.3.0-1-686-pae
res 40/00:20:00:48:11/00:00:26:00:00/40 Emask 0x60 (host bus error)
ata1.00: cmd 61/d0:d8:80:9e:10/05:00:26:00:00/40 tag 27 ncq 761856 out
ata1.00: configur
> "B" == Debian Bug Tracking System writes:
B> This is covered by the Installation Manual:
B> https://www.debian.org/releases/jessie/amd64/ch06s04.html.en
OK but maybe you should mention that somewhere in the package docs.
Also not everybody has an AMD64.
Package: initramfs-tools
Version: 0.120
Severity: wishlist
I saw "/init: touch not found" during the messages flashing by at boot,
but even installing bootlogd offers no way of capturing them because
they are from initrd.img-4.0.0-1-686-pae .
--
To UNSUBSCRIBE, email to debian-kernel-requ...@li
Package: initramfs-tools
Version: 0.120
Severity: wishlist
I swear I saw something about init: touch not found fly past on my
screen, but I have no log file to prove it.
I wish there was a log file.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscri
reopen 780239
reassign 780239 rsyslog
found 780239 8.8.0-1
thanks
I'll try the above.
BH> On Wed, 2015-03-11 at 10:57 +0800, 積丹尼 Dan Jacobson wrote:
>> Please reassign.
BH> What's the point? I could only reassign it to general so that Holger
BH> could close it.
--
Please reassign.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87vbi844w9@jidanni.org
Package: src:linux
Version: 3.16.7-ckt7-1
Severity: wishlist
Here's a risk I sent to
http://catless.ncl.ac.uk/Risks/28.55.html#subj13
which ought to also be reported here.
One day in a court of law, the log files of a computer system will be
used to prove that some incident happened at some certa
You might ask why one would want fstype auto for /.
Well sometimes it is a lifesaver.
E.g., when trying to boot with a older kernel that doesn't understand
newer filesystems. I don't recall the exact details... but it gave me
the flexibility to change something...
--
To UNSUBSCRIBE, email to deb
For 0.118 not only did I discover setting the root fstype to "auto" in
/etc/fstab and then running mkinitramfs -u make the system guaranteed
unbootable, furthermore I found this code in
/usr/share/initramfs-tools/hook-functions
# check that fstype rootfs recognition
if [ "${FSTYPE}
reopen 766448
retitle root fstype "auto" in /etc/fstab guaranteed unbootable
thanks
Please try these simple steps:
Change /etc/fstab making the type for / be "auto", not ext4 etc.
Now with initramfs-tools Ver: 0.118 installed,
run update-initramfs -u
and reboot.
But first see also #766578.
--
T
Package: initramfs-tools
Version: 0.118
Severity: wishlist
Please mention what disk you are talking about in messages like
"Warning: couldn't identify filesystem type for fsck hook, ignoring."
else the user will get very worried that one of his disks are bad and
need to test them all. Thanks.
Pre
Package: src:linux
Version: 3.16.5-1
Severity: wishlist
Regarding
'Attempt to start maintenance shell failed. Will restart in 5 seconds.'
5 seconds is not long enough to read all but a few of the words on the screen.
Please add a boot parameter to control this.
Also document it in
Documen
Package: initramfs-tools
Version: 0.118
Severity: grave
On all my systems, 0.116 works fine,
0.118 just gives some message about rebooting in 5 seconds that is not
enough time to read.
I.e., the system becomes unbootable.
1. Please tell me what steps you would like me to take.
Thanks.
--
To
Package: initramfs-tools
Version: 0.116
Severity: wishlist
File: /usr/sbin/update-initramfs
Often I see Generating /boot/initrd... twice
# aptitude full-upgrade
...
Setting up linux-image-3.16-3-686-pae (3.16.5-1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/init
Upstream closed https://bugzilla.kernel.org/show_bug.cgi?id=85471
Now what should I do? Thanks.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141014211043.ga9..
BH> Then you'll need to update it.
BH> Are you expecting update-initramfs to warn about this?
All I know is reportbug --template initramfs-tools alerted me to the
existence of /etc/initramfs-tools/conf.d/resume and its outdated
contents.
All I know is initramfs-tools created this file, not me.
B> The latter file is left over from the device ID conversion in a
B> lenny-squeeze upgrade, and is not used.
Yes but the former file points to a non-usable partition too!!
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm
Your 118 also fails to boot to boot.
(Your 118 also fails to boot in addition.)
It says "rebooting in 5 seconds" and indeed reboot in 5 seconds, too
short for me to read what else it said.
Even though I have panic=33 to give it more time.
Maybe it has to do with the
"Warning: couldn't identify f
Package: initramfs-tools
Version: 0.117
File: /usr/share/man/man8/initramfs-tools.8.gz
We read
DEBUG
It is easy to check the generated initramfs for its content. One may
need to double-check if it contains the relevant binaries, libs or mod-
ules:
mkdir tmp/i
Package: initramfs-tools
Version: 0.117
Severity: critical
File: /usr/share/initramfs-tools/hooks/fsck
How are we going to boot with an empty etc/fstab?
It is the only empty file in the whole initrd.img !
dd if=/boot/initrd.img-3.16-2-686-pae skip=6|zcat|
cpio -vt|perl -anwle 'next if /^d/; prin
Package: initramfs-tools
Version: 0.117
Severity: minor
Please list lsinitramfs on initramfs-tools man page's SEE ALSO.
In fact maybe there are others missing too.
Problem, lsinitramfs is in manual section 8 but in bin, not sbin.
Perhaps make it section 1.
Maybe other pages have this problem too
Package: initramfs-tools
Version: 0.117
I discovered these ancient files
$ find /etc/initramfs-tools/conf.d -type f|xargs more|cat
::
/etc/initramfs-tools/conf.d/resume
::
# RESUME=/dev/hda5
RESUME='UUID=89a43990-ecd9-426f-adf2-529902935af4'
::
/etc/initramfs-t
OK submitted https://bugzilla.kernel.org/show_bug.cgi?id=85471 . Thanks.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87y4sytloi@jidanni.org
> "BH" == Ben Hutchings writes:
BH> Control: close -1 3.5.5-1~experimental.1
BH> You don't have the same hardware, so don't hijack this bug.
Should I file a new bug?
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm
# journalctl
10月 02 10:01:12 jidanni5 kernel: ACPI: AC Adapter [ACAD] (on-line)
10月 02 10:01:12 jidanni5 kernel: ACPI Warning: SystemIO range
0x0428-0x042f conflicts with OpRegion 0x0400-0x047f (\PMIO)
(20140424/utaddress-258)
10月 02 10:01:12 jidanni5 kernel: ACPI: If an ACPI dri
Package: linux-doc-3.16
Version: 3.16.3-2
X-debbugs-Cc: Jan-Simon Moeller
Severity: minor
File: /usr/share/doc/linux-doc-3.16/Documentation/bad_memory.txt.gz
Please mention now grub can do badram directly!
$ info grub commands 'command-line and menu entry commands' badram
--
To UNSUBSCRIBE, e
All I know is I couldn't boot with that thing at the top of
# ls /boot/ -ltog
-rw-r--r-- 1 2907647 09-26 08:46 initrd.img-3.16-2-686-pae
drwxr-xr-x 54096 09-23 00:39 grub
-rw-r--r-- 1 2726738 09-22 23:00 initrd.img-3.16-1-686-pae
-rw-r--r-- 1 2089608 09-21 01:56 System.map-3.16-2-686-pae
-rw-r-
1 - 100 of 148 matches
Mail list logo
