Hello Diederik,
Thanks for the good news:
On Fri 13 May 2022 at 02:19:44 +0200 Diederik de Haas
wrote:
[...]
> Francesco reported that the issue was fixed for him in 5.17.0-2-686 which
> corresponds to 5.17.6 upstream kernel.
> Petra & Axel: can you verify whether it is also fixed for you
Am Sa., 9. Apr. 2022, um 08:20 +0200 schrieb Petra R.-P.
:
> Am Sa., 26. Mär. 2022, um 17:19 +0100 schrieb Petra Rübe-Pugliese
> :
> > On Sat 12 Mar 2022 at 21:31:38 +0100 Petra R.-P.
> > wrote:
> > > On Sat 05 Mar 2022 at 17:59:51 +0100
Am Sa., 26. Mär. 2022, um 17:19 +0100 schrieb Petra Rübe-Pugliese
:
> On Sat 12 Mar 2022 at 21:31:38 +0100 Petra R.-P.
> wrote:
> > On Sat 05 Mar 2022 at 17:59:51 +0100 Petra R.-P.
> > wrote:
> > [...]
> >
> > The error persists also in
tes
| device size with M = 1000*1000: 30005 MBytes (30 GB)
| cache/buffer size = 1740 KBytes (type=DualPortCache)
| Capabilities:
| LBA, IORDY(can be disabled)
| Standby timer values: spec'd by Vendor, no device specific minimum
| R/W multiple sector
Am Mo., 4. Apr. 2022, um 10:05 +0200 schrieb Axel Beckert :
[...]
> "fdisk -l /dev/sda" should suffice.
,-[ 1st T41 ]---
| ~ > fdisk -l /dev/sda
| Disk /dev/sda: 27.95 GiB, 30005821440 bytes, 58605120 sectors
| Disk model: IC25N030ATMR0
Am Mo., 4. Apr. 2022, um 16:39 +0900 schrieb Damien Le Moal
:
[...]
> By the way, what is the drive connected on your Thinkpad ? Same as Axel, a
> Samsung HM160HC ? If it is a different drive, then patch 2 (big hammer) may
> be better as this may indicate that the adapter does not like read log
>
Just for the record:
On Mon 04 Apr 2022 at 14:49:05 +0900 Damien Le Moal
wrote:
[...]
> There will be no issue with your 1GB of ram. Giving this amount of ram and
> CPU, step (4) will indeed take a while, but it will run fine.
My T41 Thinkpads only have 500MB of ram and little space left on
th
Am Mi., 30. Mär. 2022, um 08:38 +0200 schrieb Salvatore Bonaccorso
:
[...]
> Thanks for constantly testing the new versions (there is 5.16.18-1
> upcoming btw, or 5.17.1 in experiemntal).
I'm just testing whatever is pulled in automatically by linux-image-686 (in
bookworm).
>
> Do we have a r
On Sat 05 Mar 2022 at 17:59:51 +0100 Petra R.-P.
wrote:
> Update for linux-image-5.16.0-3-686 :
[...]
The error persists also in linux-image-5.16.0-4-686 (5.16.12-1) .
Petra
For the sake of completeness ...
On Wed 09 Mar 2022 at 08:35:57 +0100 Petra R.-P.
wrote:
[...]
> Okay, that's easier: See attached dmesg-T41-k5.15.txt .
Adding dmesg-T41-b-k5.15.txt — corresponding file for the other
T41 notebook, which has slightly different hardware.
fb=false
[4.084072] ACPI: battery: Slot [BAT0] (battery present)
[4.088526] ACPI: video: Video Device [VID] (multi-head: yes rom: no post:
no)
[4.096823] input: Video Bus as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:02/LNXVIDEO:00/input/input2
[4.097138] Floppy drive(s): fd
Hello,
I am the "OP" with the T41 Thinkpads.
On Tue 08 Mar 2022 at 05:58:53 +0900 Damien Le Moal
wrote:
> Could you try taking a video of the boot messages ?
You can find my first attempt (only ≈12MB) here:
https://prp.in-berlin.de/MAQ01257.MP4
I will leave it there for 2 weeks.
Not sure i
Hi Diederik,
Am So., 6. Mär. 2022, um 00:44 +0100 schrieb Diederik de Haas
:
> On Saturday, 5 March 2022 21:12:12 CET Petra R.-P. wrote:
[...]
> How about in /var/log/kern.log.1 (f.e.) ?
The kern.log I inspected yesterday reached back until earlier
days, so I don't think kern.
Update for linux-image-5.16.0-3-686 :
On Sat 19 Feb 2022 at 22:04:14 +0100 Petra R.-P.
wrote:
[...]
> After the lines
>
>Loading Linux 5.16.0-1-686 ...
Now of course: s/-1-/-3-/
>Loading initial ramdisk ...
>
> the screen gets flushed, and I see:
>
>
Hello Diederik,
Thanks for your quick reply:
Am Sa., 19. Feb. 2022, um 22:36 +0100 schrieb Diederik de Haas
:
> On Saturday, 19 February 2022 22:04:14 CET Petra R.-P. wrote:
> > Package: src:linux
> > Version: 5.16.7-2
[...]
> > pn firmware-iwlwifi
>
> I
PC running the same kernel the same message "ata1.00: Read log ..."
appears, but then the boot process continues normally.
linux-image-5.15.0-3-686, which I am using to write this
message, runs fine.
Thanks for maintaining this package
and best regards,
Petra R.-P.
-- P
Source: linux
Severity: wishlist
X-Debbugs-Cc: ased...@mit.edu
Dear Maintainers,
The 5.7 kernel added support for the Modem Host Interface (MHI) bus,
and the 5.11 kernel added MHI network device drivers supporting some
new WWAN devices. The 5.13 kernel (among others) continues to add
additional
uster
> release without changes, but it looks it behaves differently in a buster
> vs. unstable/bullseye environment when the replacement ${version%%-*}
> is involved after the version setting:
>
> , [ perf-minimal ]
> > #!/bin/bash
> >
> > version="
After running a "make install" in git with the 5.10.0-trunk-amd64 kernel, I
can confirm the WiFi card is working on the new Dell XPS 13.
Thanks again for maintaining this package!
Paul
--
:wq
Package: firmware-atheros
Severity: wishlist
thanks
The spiffy new Dell XPS 13 9310 is shipping, but is not sold as supporting
linux yet -- but appears to work great, with the exception of the Qualcomm
Technologies 802.11ax chipset.
In addition to #97994's CONFIG_ATH11K kernel change, Vincent poi
Package: linux-image-5.9.0-1-amd64
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: rgr...@rsu20.org
Dear Maintainer,
Updating to any Linux kernel after 5.7.0-2-amd64 makes the NVMe SSD on Apple
MacBookAir7,1 fail to start.
dmesg spits out:
[ 64.565416] nvme nvme0: cont
gcc-8, and is kernel release
> 5.2.14 with official 5.2.14-rt7 RT-patches from kernel.org -- nothing
> else than kernel optons with "make menuconfig" and then performing "make
> deb-pkg"..
>
Best Professional Regards.
1800X Eight-Core Processor (family: 0x17, model: 0x1,
> stepping: 0x1)
> RAM: 2x F4-3200C16D-32GTZ (making for 4x16GB)
> PSU: Corsair AX1600i 1600W
> GPU: Asus ROG Strix RX VEGA64 OC edition 8GB
> OS: Debian GNU/Linux Sid with currently kernel 4.19.37-3
Package: src:linux
Version: 4.19.9-1
Severity: normal
Dear Maintainer,
with kernel 4.19.9 I have a screen corruption / flickering (not sure how it is
called) on the right side. This only occurs with 144 hz.
here's a screenshot: https://i.imgur.com/c93jGpu.jpg
With 4.18 or older kernels I don't h
Package: src:linux
Version: 4.18.20-2
Followup-For: Bug #914495
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation? Booting into linux-image-4.18.0-3-amd64.
* What exactly did you do (or not do) that was effective
Package: src:linux
Version: 4.18.10-1
Severity: important
Dear Maintainer,
with 4.18.10 the power consumption on idle with polaris chips increases
drastically. More info can be found on
https://www.phoronix.com/scan.php?page=news_item&px=AMDGPU-4.18-Power-Draw. The
Bug is already reported upst
reiser4.0.2-amd64 install
linux-image-4.17.0-3+reiser4.0.2-amd64 install
uname -a
Linux huitzilopochtli 4.17.0-3+reiser4.0.2-amd64 #1 SMP Debian 4.17.18-
1+reiser4.0.2 (2018-08-23) x86_64 GNU/Linux
> Regards,
Best Profes
Hi all
Almost two month past since the last message, and still don't have a
new release of this package, it's a shame since QA informs there is 20
commits since the tag debian/20170823-1. I cannot found any new release
in the Tracker.
Please consider that many people use Testing, or Stable Backpo
Ben
The crashes/hangs stopped once we moved our main filesystem off of btrfs to
xfs.
Thanks
--Nate
On Sat, Jun 30, 2018 at 8:18 PM Ben Hutchings wrote:
> Control: tag -1 mreinfo
>
> On Wed, 11 Oct 2017 17:33:58 -0600 Nate R wrote:
> > Package: src:linux
> > Ver
(attached) for it to apply (fuzz=0)
to my subject Debian kernel -- *assuming* the RT kernel version will
want to keep the new line of code.
Best Professional Regards.
--
Jose R R
http://metztli.it
Hello,
I'm experiencing the same problem on Soekris net5501, also with the latest
testing 4.12.0.1-686 kernel : the boot process gets stuck on "Loading
initial ramdisk".
The 4.9.0.3-686 boots correctly.
Regards
On Sat, 26 Aug 2017 13:02:18 +0200 Francesco Poli
wrote:
> Control: found -1 linux/
Any help would appreciated as linux-headers common are not built in
reiser4 custom kernel build:
make[7]: Leaving directory '/usr/src/build/kernel/build/linux/tools/build'
/usr/bin/make FIXDEP=1 -f Makefile.perf
make[7]: Entering directory '/usr/src/build/kernel/build/linux/tools/perf'
Auto-detec
. The stack trace
most notably included nouveau_pmops_runtime_suspend as a likely culprit.
Shutting down or rebooting the system through normal means (e.g. shutdown
-(h|r)) would apparently never succeed, repeating a similar message.
I found an old thread[1] that recommended booting with
On Sun, Jun 4, 2017 at 3:40 AM, Ben Hutchings wrote:
> On Sun, 2017-06-04 at 03:23 -0700, Jose R R wrote:
>> Niltze [Hello], Konstantin-
>>
>> I am relatively new to git.
>>
>> Will you be so kind (if you know, of course) to convey how to checkout
>> a part
first need to download
relevant branch from current experimental to anticipate issues.
Thank you in advance for your consideration
Best Professional Regards.
--
Jose R R
http://metztli.it
-
Download Debi
On Thu, Mar 30, 2017 at 5:13 PM, Ben Hutchings wrote:
>
> > AFAIK, there's no (performance or size) penalty in enabling it [...]
>
> It's not very large, but yes there is a cost.
>
>
Is it enough to leave it disabled? It seems that being a (standard) sysfs
interface, the penalty is not really muc
ms
>
>
> -- Forwarded message --
> From: Ben Hutchings
> To: 858084-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Thu, 30 Mar 2017 00:13:03 +0100
> Subject: Re: Bug#858084: linux-image-amd64 - kernel option enable request
> On Sat, 2017-03-18 at 10:16 +0
Hello,
I think this bug can be closed as the kernel version has been updated which
pretty much was the purpose of the original bug request.
Thank you.
Kind Regards,
Narayanan.
Package: linux-image-amd64
Version: 4.9+79~bpo8+1
Can you please enable the CONFIG_CPU_FREQ_STAT_DETAILS option for the
kernels.
Thanks in advance.
Regards,
Narayanan.
ts and fixes to
> hardware support.
>
> There will be no ABI bump.
>
> Ben.
>
> --
> Ben Hutchings
> Theory and practice are closer in theory than in practice.
> - John Levine, moderator of
> comp.compilers
>
Best Pr
:50 AM, Ben Hutchings wrote:
> [Reply to all, not just to me.]
>
> On Fri, 2017-02-17 at 08:42 +0530, Narayanan R S wrote:
> > Hello Ben,
> >
> > I did have the documented ICMP network issues when I used the 4.9 version
> > of the backported kernel.
> >
>
Package: linux-image-amd64
Version: 4.9+78
The current (backported) version of linux-image-amd64 (for Jessie) appears
to need a few important fixes from the kernel source (upstream).
Please see:
https://www.spinics.net/lists/kernel/msg2406212.html
https://bugzilla.redhat.com/show_bug.cgi?id=1402
5-1_bp/
By the way none of those packages have *any dependencies* on reiser4
other than being built in a machine with that file system ;-)
You are welcomed to give those a try but I offer no guarantees whatsoever.
Best Profess
> pn firmware-bnx2x
> pn firmware-brcm80211
> pn firmware-cavium
> pn firmware-intel-sound
> pn firmware-intelwimax
> pn firmware-ipw2x00
> pn firmware-ivtv
> pn firmware-iwlwifi
gt; pn linux-doc-4.8
>
> Versions of packages linux-image-4.8.0-1-amd64 is related to:
> pn firmware-amd-graphics
> pn firmware-atheros
> pn firmware-bnx2
> pn firmware-bnx2x
> pn firmware-brcm80211
> pn
bian/stamp/conf/minimal_debian] Error 2
/usr/share/kernel-package/ruleset/minimal.mk:93: recipe for target
'debian/stamp/conf/minimal_debian' failed
Best Professional Regards.
--
Jose R R
http://metztli.it
-
As just a data point, when -march=i686, the kernel builds and seems to
work well using 6.2.0-10 and with no patches to Makefile at all.
On 10/29/2016 10:24 AM, Oswald Buddenhagen wrote:
-no-pie is not a useful option here, because it's passed to the _linker_
only.
i got it to build with this
y mean
that the kernels are currently only built/supported with gcc-5.
vanilla kernels (Linus' tree and the stable ones) could be compiled just fine
with gcc 6.2.0-6 and that now fails.
I still think this is a major regression and regard gcc 6.2.0-7 simply as
broken.
On Thu, 2016-10-20 at 11:
I agree. When the version changes from 6.2.0-6 to 6.2.0-7, only bug
fixes should be included, not changes in functionality. In this case
setting enable-default-pie essentially broke backwards compatibility.
Kernel code that built in -6 failed to build in -7. That, I agree,
should be cons
Concurring with Wolfgang; pulling the source straight from kernel.org
and using identical .config files will work with 6.2.0-6 but fail with
6.2.0-7. I was able to build and install 4.8.3 with no issues after
back-revving gcc et. al. to 6.2.0-6
-- sRw
On 10/20/16 11:09, Wolfgang Walter wr
On Sat, Sep 10, 2016 at 6:10 PM, Ben Hutchings wrote:
> On Sat, 2016-09-10 at 17:37 -0700, Jose R R wrote:
>> On Fri, Sep 9, 2016 at 12:37 PM, Wolfgang Tichy
>> wrote:
>> >
>> > Package: src:linux
>> > Version: 3.16.7-ckt25-2+deb8u3
>> > Severi
ngerprint Coprocessor (WBF
> advanced mode)
> Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b
On Sat, Sep 3, 2016 at 10:30 AM, Ben Hutchings wrote:
>
> On Fri, 2016-09-02 at 16:49 +0100, Ben Hutchings wrote:
> > On Fri, 2016-09-02 at 03:35 -0700, Jose R Rodriguez wrote:
> > >
> > > Niltze, all!
> > >
> > > Currently running Reiser4-pat
Much appreciated, Ben!
On Fri, Sep 2, 2016 at 8:49 AM, Ben Hutchings wrote:
> On Fri, 2016-09-02 at 03:35 -0700, Jose R Rodriguez wrote:
>> Niltze, all!
>>
>> Currently running Reiser4-patched kernel 4.7 built from pristine
>> source upstream:
>>
>> Linu
Niltze, all!
Currently running Reiser4-patched kernel 4.7 built from pristine source
upstream:
Linux mictlantecuhtli 4.7.0.tezcatlipoca #1 SMP PREEMPT Wed Aug 10 05:04:17 PDT
2016 x86_64 GNU/Linux
On the other hand, I have experienced multiple issues building Debian'ized
kernel 4.7.2-1 -- fir
Hi,
We've got some surprising news, you're gonna love it! Just read it here
<http://degostyfri.cyrusoftware.com/e2kbmyw>
Jose R R
:
https://sf.net/projects/debian-reiser4/
Unless anyone knows of a reason not to upload the generated kernel
package files to Bintray (first time I do), I may subsequently upload
Reiser4 (SFRN 4.0.1)-patched kernels 4.5 and 4.6.4.x for Jessie on
AMD64.
Best Professional Regards.
--
Jose R R
http
nudging build procedure along...
apt-get install asciidoc libelf-dev libperl-dev python-dev libnuma-dev
libaudit-dev libunwind-dev libdw-dev libudev-dev libiberty-dev usbip
libusbip-dev liblockdep4.4 linux-tools
On Mon, Apr 25, 2016 at 1:25 PM, Jose R R wrote:
> and, yes, Ben, in other
and, yes, Ben, in other VM instances I have installed asciidoc, (takes
longer to build) but the outcome is the same.
On Mon, Apr 25, 2016 at 1:21 PM, Jose R R wrote:
> Niltze, Ben-
>
> Maybe I am dense, but I in several Debian kernels 4.5.x.y I noticed
> the topic of the subject *and
Niltze, Ben-
Maybe I am dense, but I in several Debian kernels 4.5.x.y I noticed
the topic of the subject *and* associated to this recurring fail
pattern:
On Sun, Apr 17, 2016 at 11:00 AM, Ben Hutchings wrote:
> On Sun, 2016-04-17 at 06:38 -0700, Jose R R wrote:
>> Nilteze, all-
>
On Wed, Apr 20, 2016 at 4:11 AM, Jonáš Vidra wrote:
> On Wed, 20 Apr 2016 12:53:48 +0200 Jose R R wrote:
>
>> is there any reason why Reiser4 SFRN 4.0.1-enabled Debian should not
>> run on Power8? I assume GPT should be selected whereas previously I
>> have tested -- on A
cloud -- only MSDOS disk
partitioning.
Best Professional Regards.
--
Jose R R
http://metztli.it
-
Try at no charge http://b2evolution.net for http://OpenShift.com
'
make[1]: Leaving directory '/usr/src/linux'
Similar message also was also a show stopper in a certain recent iteration
of linux/debian packaging from git.
Any insight appreciated.
Best Professional Regards.
--
Jose R R
http://metztli.it
-
With the latest update Linux mb 3.16.0-4-amd64 #1 SMP Debian
3.16.7-ckt25-1 (2016-03-06) x86_64 GNU/Linux, the bug has been fixed.
Thanks a lot!
Al the Best, Riccardo
.
Moreover, when I shut down the system after using the exfat pendrive,
the system does not shut down. I have to make a hard shut down and
then restar to make it work normally again. That means it has to
recover the journals.
Please help.
Regards,
--
Mr. Goldin R. Bennet
Department of
Hi, I think I've discovered a bug in the kernel 3.16. The issue is
related to the suspend/resume brightness with i965 integrated video
controller. I discovered the bug was not present in the previous debian
stable kernel 3.2 and is still present in the 4.2 and 4.3 kernel from
backports. I compiled
ed cloud infrastructure ;-)
[1]
http://stackoverflow.com/questions/12002315/extract-vmlinux-from-vmlinuz-or-bzimage
[2]
http://unix.stackexchange.com/questions/163346/why-is-it-that-my-initrd-only-has-one-directory-namely-kernel
--
Jose R R
http://metztli.it
--
On Thu, Sep 17, 2015 at 8:56 AM, Ivan Shapovalov wrote:
> On 2015-09-17 at 05:10 -0700, Jose R R wrote:
>> On Sun, Sep 13, 2015 at 6:06 AM, Ivan Shapovalov <
>> intelfx...@gmail.com> wrote:
>> > On 2015-09-13 at 05:57 -0700, Jose R R wrote:
>> > > Her
On Sun, Sep 13, 2015 at 6:06 AM, Ivan Shapovalov wrote:
> On 2015-09-13 at 05:57 -0700, Jose R R wrote:
>> Here is some additional info:
>>
>> A while back, I installed Debian Jessie AMD64 into a KVM virtual
>> machine and also included the initial non-system
On Thu, Sep 10, 2015 at 5:10 AM, Ivan Shapovalov wrote:
> On 2015-09-10 at 04:57 -0700, Jose R R wrote:
>> On Wed, Sep 9, 2015 at 6:16 AM, Ivan Shapovalov > > wrote:
>> > On 2015-09-09 at 00:54 -0700, Jose R R wrote:
>> > > Scratch my previous issue, Ed. It is *no
Appreciated, Ben!
On Sat, Jul 25, 2015 at 7:58 AM, Ben Hutchings wrote:
> On Fri, 2015-07-24 at 22:23 -0700, Jose R R wrote:
> [...]
>> Procedure executes for a while but then:
>>
>> [...]
>> xt_unregister_targetsmodule:
>> net/net
l/usr/src/linux-4.0.8'
debian/rules.gen:25: recipe for target
'binary-arch_amd64_none_amd64_real' failed
make: *** [binary-arch_amd64_none_amd64_real] Error 2
Thank you in advance for any insight. Appreciated.
Best Profess
Package: linux-headers-3.16-0.bpo.2-common
Version: 3.16.3-2~bpo70+1
Severity: normal
Hello,
While attempting to install NVidia drivers v340.46 (x64) on the currentli
running 3.16 Debian kernel, the auto installer fails during the build of the
DKMS module.
It seems the Makefiles chain inside t
Perhaps we should find time to hack at DebConf
-T
On Tue, Aug 19, 2014 at 5:16 PM, Steve McIntyre wrote:
> On Tue, Aug 19, 2014 at 01:38:44PM -0700, Ben Hutchings wrote:
>>
>>So far as I know, no progress has been made on the above steps or any
>>alternate approach.
>
> Ditto, I've not seen (or
The shutdown failure does not occur with linux-3.11.10, the last of the
3.11 series kernels.
-
Package: linux-image-3.13-1-amd64
Followup-For: Bug #735491
Dear Maintainer,
* What led up to the situation?
Upgrading jessie to current, last install was some months after wheezy release
* What exactly did you do (or not do) that was effective (or
ineffective)?
Upgrade was smooth.
n -h now ... it did *and* it did not wake up, restart, etc.
until today that I turned it on from its power switch.
Thus, I agree taht it is possible that a driver may be causing the
issue in the hardware from the person that originated this topic.
Hi Ben
Thanks for the answer. I am sorry that I haven't answered sooner, but I do
not build kernels often, so I took me a while.
I can confirm that the problem have disappeared running the kernel I build
using your patch. My kernel is now:
Linux kelvin 3.11-2-amd64 #1 SMP Debian 3.11.8-1a~test (2
Wow, thank you for your fast answer!
El jue, 29-08-2013 a las 10:31 +0200, Bastian Blank escribió:
> On Wed, Aug 28, 2013 at 09:05:01PM -0300, Carlos R. Pasqualini wrote:
> > can we have this option by default at least on Testing?
>
> Also for you the question: What does it brin
Linux capibara 3.10-0.bpo.2-amd64 #1 SMP Debian 3.10.5-1~bpo70+1
(2013-08-11) x86_64 GNU/Linux
root@capibara:~# grep CONFIG_FANOTIFY /boot/config-$(uname -r)
CONFIG_FANOTIFY=y
# CONFIG_FANOTIFY_ACCESS_PERMISSIONS is not set
may be, as the point on having a unstable/testing distro is to test new
thing
t, and I omitted them by
replacing "...")
--
$ sh ./a.sh
Linux jrofr 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64 GNU/Linux
-rw-r--r-- 1 root root 1427 Jul 24 17:41 /etc/mtab
+ egrep -n (/tmp/|bind) /etc/mtab /proc/mounts
/et
unt(8) and umount(8) highly depends upon /etc/mtab (or
/proc/mounts).
By the way, after forcing /etc/mtab as a regular file on my wheezy
system, I found another problem of mount(8). I will report it to
bugtrack later.
J. R. Okajima
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian
since this problem is a show-stopper for me.
J. R. Okajima
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/10827.1374555641@jrobl
) by
default (by NFS developers).
- mount.nfs always writes the "sec=sys" string (by mount.nfs
developers).
I suppose the best way should be decided after the discussion between
NFS developers, mount.nfs developers and Debian developers.
J. R. Okajima
--
To UNSUBSCRIBE, ema
Package: nfs-common
Version: 1:1.2.6-4
Severity: normal
Dear Maintainer,
I met a strange behavour of mount.nfs.
When I run "mount -o remount /nfs/mntpnt", it terminated silently but
the exit status was 32. Actually when I add "-v" option, it prints
"mount.nfs: mount(2): Invalid argument".
Here
On Wed, Mar 20, 2013 at 7:41 AM, Ben Hutchings wrote:
> On Wed, 2013-03-20 at 02:07 -0700, Luis R. Rodriguez wrote:
>> On Sun, Mar 17, 2013 at 2:43 PM, Ben Hutchings wrote:
>> > [Re-sending to the correct list address.]
>> >
>> > On Sun, 2013-03-17 at 16:24
enerated modules cannot be loaded.
>> > >
>> > > Is there any by-pass for this?
>> > >
>> > > ¹http://marc.info/?t=13635103432&r=1&w=2
>> > > ²http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664767
>> >
>> > Talk to th
Hi customer,
You don't have to reply, this is a test.
I have a new website someurl.com
You are welcome!
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/46h78vyl.8ah
On Wed, Jul 04, 2012 at 01:16:14PM -0500, Jonathan Nieder wrote:
> Jonathan Nieder wrote:
> > Luis R. Rodriguez wrote:
>
> >> FWIW we already provide daily backports of code through compat-wireless.
> >> compat-wireless will eventually be changed to "compat-d
On Thu, May 10, 2012 at 05:28:31AM +0100, Ben Hutchings wrote:
> On Thu, 2012-05-10 at 02:14 +, Huang, Xiong wrote:
> > Hi Jonathan
> >
> > For driver atl1c, we add many patches recently. Please sync with
> > the kernel, the last patch is
> > 80bcb4238dd858d atl1c: remove PHY polling fro
Package: linux-2.6
Version: 3.2.6-1
Severity: normal
Dear Maintainer,
i am unable to mount a filesystem on a known working sata drive in an external
usb enclosure. enclosure is newegg item # N82E16817392032. this is the second
enclosure that i've tried, as i RMA'd the first one thinking it was j
Package: initramfs-tools
Version: 0.101
the following FATAL errors should *possibly* be simply warnings; there
are cases where one might roll their own kernels and not waste cycles
building modules for filesystems that are unnecessary, or choose to make
them part of the kernel as opposed to l
re upgrading.
>From a user's point of view I'd really appreciate if that package could be
kept. Needing multi-arch enabled (with all the dangers of getting the
wrong packages installed or the additional index files to download) just
to have a suiteable kernel would be quite a burden.
(or
ineffective)? See the previous answer
* What was the outcome of this action? Only the version number changed, as
mentioned in the subject line
* What outcome did you expect instead? Changes in some source programs (I
created a tree from the tarball and compared with "diff -r"
On Mon, Dec 12, 2011 at 2:47 PM, Luis R. Rodriguez wrote:
> On Mon, Dec 12, 2011 at 1:58 PM, Ben Hutchings wrote:
>> On Mon, Dec 12, 2011 at 01:40:44PM -0800, Luis R. Rodriguez wrote:
>>> On Mon, Oct 24, 2011 at 6:12 AM, Ben Hutchings wrote:
>>> > Use of the GPL o
On Mon, Dec 12, 2011 at 1:58 PM, Ben Hutchings wrote:
> On Mon, Dec 12, 2011 at 01:40:44PM -0800, Luis R. Rodriguez wrote:
>> On Mon, Oct 24, 2011 at 6:12 AM, Ben Hutchings wrote:
>> > Use of the GPL or a compatible licence doesn't necessarily make the code
>> >
On Mon, Oct 24, 2011 at 6:12 AM, Ben Hutchings wrote:
> Use of the GPL or a compatible licence doesn't necessarily make the code
> any good. We already consider staging modules to be suspect, and this
> should also be true for out-of-tree modules which may receive very
> little review.
>
> Signed
After reading the Ubuntu bug report (#794642) I found that this Debian bug is
also due to the SATA mode in my computer being set to IDE. When this is changed
to AHCI the problem vanishes: /dev/cdrom appears.
On Sun, 09 Oct 2011 11:04:41 +0530 wrote
>On Sun, 2011-10-09 at 04:36 +0000,
Package: linux-2.6
Version: 3.0.0-5
Severity: important
Dear Maintainer,
*** Please consider answering these questions, where appropiate ***
* What led up to the situation? I noticed that it didn't mount the
CDROM.
* What exactly did you do (or not do) that was effective (or
inef
Package: linux-image-2.6-686
--- On Sat, 7/9/11, Debian Bug Tracking System wrote:
> From: Debian Bug Tracking System
> Subject: Message with no Package: tag cannot be processed! (Debian Lenny to
> Squeeze upgrade)
> To: "Linda R"
> Date: Saturday, July 9, 2011, 1:21
1 - 100 of 211 matches
Mail list logo
