On Thu, Aug 07, 2008 at 07:52:36PM +0200, Robert Millan wrote:
> > By "small chunk", you mean 64 bytes of data. That's not a program; that's
> > almost certainly register initialization values, which are data, and there
> > is no requirement in the DFSG that arbitrary bits of data (which are too
Package: initramfs-tools
Version: 0.92e
Severity: minor
Tags: patch
Hi,
Please make log_begin_msg not emit a trailing newline - this makes the non-
"quiet" output cleaner and results in half as many lines being emitted. For
example:
Begin: Finding root filesytem ...
Done.
Becomes:
Begin:
Subject: linux-image-2.6.26-1-686 monitor button does not work in hp nx 6110
Package: linux-image-2.6.26-1-686
Severity: normal
-- System Information:
Debian Release: lenny/sid
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'unstable')
Architecture:
If the previous command was reboot(8), then at the Lilo prompt, one
needs the full seven Fn Ends to restore minimal brightness.
If the previous command was shutdown -h now, then at the Lilo prompt
after next powerup, one needs only three or four Fn Ends to restore
minimal brightness.
H> I hope to
Hello, can you please include the output of:
dd if=loop18 bs=512 count=1 iflag=direct | hexdump -C
Cheers,
--
Niv Sardi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Much cleaner:
--- /usr/share/initramfs-tools/hook-functions~ 2008-08-07 20:33:40.0
+0200
+++ /usr/share/initramfs-tools/hook-functions 2008-08-07 21:37:00.0
+0200
@@ -189,6 +189,7 @@
device_path="$1"
while [ "${device_path}" != "/sys" ]; do
+
On Thu, Aug 07, 2008 at 09:02:33PM +0200, Luk Claes wrote:
>
> Feel free to discuss this in -legal, though that doesn't change the fact
> that we currently don't expect textual source for arbitrary bits of data.
Okay, I will (eventually). I don't expect you consider this corner-case
release cri
Package: linux-image-2.6-sparc64
Version: 2.6.25+14
Severity: normal
Using Kerberized NFS4 on a Sparc64 machine, I'm repeatedly getting the following
report from the kernel:
[598814.700855] Kernel unaligned access at TPC[101c64d0]
gss_get_mic_kerberos+0xac/0x16c [rpcsec_gss_krb5]
I don't recall
Robert Millan wrote:
On Thu, Aug 07, 2008 at 09:34:31AM -0700, Steve Langasek wrote:
drivers/media/dvb/frontends/tda10021.c (licensed under GPLv2+) contains a
small chunk of binary code:
static u8 tda10021_inittab[0x40]=
{
0x73, 0x6a, 0x23, 0x0a, 0x02, 0x37, 0x77, 0x1a,
0x37, 0x6
More info plus a possible patch.
/sys/devices/platform/orion-ehci.0/modalias exists which contains
the string platform:orion-ehci
And:
$ modprobe --show-depends platform:orion-ehci
insmod /lib/modules/2.6.26-1-orion5x/kernel/drivers/usb/core/usbcore.ko
insmod /lib/modules/2.6.26-1-orion5x/kernel
Package: linux-image-2.6.26-1-686
Version: 2.6.26-1
--- Please enter the report below this line. ---
Hi Jérémy,
I've noticed it as well, It looks like the module is now named: snd_pcsp
updating your blacklist should solve the issue:
sudo modinfo snd_pcsp
filename:
/lib/modules/2.6.26-1-
On Thu, Aug 07, 2008 at 09:34:31AM -0700, Steve Langasek wrote:
> > drivers/media/dvb/frontends/tda10021.c (licensed under GPLv2+) contains a
> > small chunk of binary code:
>
> > static u8 tda10021_inittab[0x40]=
> > {
> > 0x73, 0x6a, 0x23, 0x0a, 0x02, 0x37, 0x77, 0x1a,
> > 0x37,
On Aug 07, Robert Millan <[EMAIL PROTECTED]> wrote:
> drivers/media/dvb/frontends/tda10021.c (licensed under GPLv2+) contains a
> small chunk of binary code:
What makes you believe this is code instead of data to be loaded in
the card registers?
--
ciao,
Marco
signature.asc
Description: Digita
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.26
> forcemerge 494120 494122
Bug#494120: binary firmware in drivers/media/dvb/frontends/tda10021.c
Bug#494122: binary firmware in drivers/media/dvb/frontends/tda8083.c
Forcibly Merged 494
On Fri, 08 Aug 2008, [EMAIL PROTECTED] wrote:
> Dear HMH, I have continued my observations. It seems the only time I
> have to still hit Fn End to bring the brightness back down is after a
> reboot: using reboot(8) brings one to a super bright Lilo screen.
>
> And 'shutdown -h now' also will give
Your message dated Thu, 7 Aug 2008 09:53:40 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Re: binary firmware in
drivers/media/dvb/dvb-usb/af9005-script.h
has caused the Debian Bug report #494119,
regarding binary firmware in drivers/media/dvb/dvb-usb/af9005-script.h
to be marked as
Dear HMH, I have continued my observations. It seems the only time I
have to still hit Fn End to bring the brightness back down is after a
reboot: using reboot(8) brings one to a super bright Lilo screen.
And 'shutdown -h now' also will give a bright Lilo screen upon next
power up. (It is what I u
Your message dated Thu, 7 Aug 2008 09:35:51 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#494122: binary firmware in
drivers/media/dvb/frontends/tda8083.c
has caused the Debian Bug report #494122,
regarding binary firmware in drivers/media/dvb/frontends/tda8083.c
to be marked
Your message dated Thu, 7 Aug 2008 09:34:31 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#494120: binary firmware in
drivers/media/dvb/frontends/tda10021.c
has caused the Debian Bug report #494120,
regarding binary firmware in drivers/media/dvb/frontends/tda10021.c
to be mark
Hello,
This bug is a bit old, do you still find it to be an issue ? if yes, can
you try to use the etch backport of 2.6.25 and see if it's still a
problem ?
http://packages.debian.org/etch-backports/linux-image-2.6-686
Cheers,
--
Niv Sardi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
Update : the 2.6.18 does recognise the eeprom. However, the drivers seems to
have trouble using the device :
This is the output generated with a rmmod e1000; modprobe e1000 :
Aug 7 16:26:44 pcvlf1700 kernel: Intel(R) PRO/1000 Network Driver - version
7.1.9-k4-NAPI
Aug 7 16:26:44 pcvlf1700 ker
Hi Nathanael,
I believe you made some work on a userland loader for this non-free firmware
(see subject). If you have a minute, could you send a followup to this [1] bug
about the latest status of this?
Thanks!
[1] But, please, not to the old meta-bugs that regroup this problem with other
On Thu, Aug 07, 2008 at 01:17:11PM +0200, Peter Van Biesen wrote:
> can the problem please be fixed in a 2.6.18 kernel ? I'm sure it is fixed in
> 2.6.24 and up, but to run a xen dom0, you need a 2.6.18 kernel.
Can you provide a patch?
Bastian
--
The joys of love made her human and the agoni
Ok, so I couldn't figure out anything, but now while I'm writing this I tried
ls -U, ie. unsorted ls, and found out that all the problematic dirs are in
sequential order
I tested attaching another disk to QNAP, a disk that happens to have an
earlier backup of the same CD FLAC rips... the same
Hi,
can the problem please be fixed in a 2.6.18 kernel ? I'm sure it is fixed in
2.6.24 and up, but to run a xen dom0, you need a 2.6.18 kernel.
Strangely enough, the 2.6.18 non-xen kernel is able to use the e1000 driver
correctly.
Thanks in advance,
Peter.
PS: I just installed the machine
Package: linux-2.6
Version: 2.6.26-1
Severity: serious
Hi,
drivers/media/dvb/frontends/tda8083.c (licensed under GPLv2+) contains a small
chunk of binary code:
static u8 tda8083_init_tab [] = {
0x04, 0x00, 0x4a, 0x79, 0x04, 0x00, 0xff, 0xea,
0x48, 0x42, 0x79, 0x60, 0x70, 0x52, 0x
Package: linux-2.6
Version: 2.6.26-1
Severity: serious
Hi,
drivers/char/drm/mga_ucode.h is entirely composed of binary code:
RegDesc script[] = {
[...]
There's no copyright header in this file. The comments say it's been
generated from "AF05BDA.sys (windows driver)", but they don't sp
Package: linux-2.6
Version: 2.6.26-1
Severity: serious
Hi,
drivers/media/dvb/frontends/tda10021.c (licensed under GPLv2+) contains a
small chunk of binary code:
static u8 tda10021_inittab[0x40]=
{
0x73, 0x6a, 0x23, 0x0a, 0x02, 0x37, 0x77, 0x1a,
0x37, 0x6a, 0x17, 0x8a, 0x1e, 0x86,
On Wed, Aug 06, 2008 at 08:16:44PM +0200, Robert Millan wrote:
> >
> > If you think one of the remaining firmwares is licensed in a way not
> > acceptable for main, please send in tested patches against the driver in
> > linux-2.6 fixing it to request the firmware from userland, and the
> > needed
29 matches
Mail list logo
