This patch makes it posible to use the bcm2835-audio driver on the Raspberry.
In drivers/staging/vc04_services/bcm2835-audio/TODO Michael Zoran says
that this is to be done, in fact as we noted on
https://bugs.debian.org/856505 without this patch the driver is not
loaded and when loaded it
Hi!
There was a problem that affected all tulip based drivers and which has been
fixed in most of them, for uli526x the problem remains on 2.6.25-rc2 as the
fix has not yet been applied.
A discusion of this bug and the patch to fix it is at
http://bugzilla.kernel.org/show_bug.cgi?id=5839
Several
Hi!
There was a problem that affected all tulip based drivers and which has been
fixed in most of them, for uli526x the problem remains on 2.6.25-rc2 as the
fix has not yet been applied.
A discusion of this bug and the patch to fix it is at
http://bugzilla.kernel.org/show_bug.cgi?id=5839
Several
> > > http://bugzilla.kernel.org/show_bug.cgi?id=5839
> Excellent. I've asked kyle to push that upstream. He ACKd so it should
> go in pretty soon.
Still nothing on the recently released rc1 of 2.6.25, has this been pushed
to Linus?
Regards...
--
Manty/BestiaTester -> http://manty.net
--
To
http://bugzilla.kernel.org/show_bug.cgi?id=5839
Excellent. I've asked kyle to push that upstream. He ACKd so it should
go in pretty soon.
Still nothing on the recently released rc1 of 2.6.25, has this been pushed
to Linus?
Regards...
--
Manty/BestiaTester - http://manty.net
--
To
> Is this perhaps the same problem as described here?
> http://bugzilla.kernel.org/show_bug.cgi?id=5839
Seems right.
> If you think it is, could you add (just cut/paste)
> you email to that bug for me?
Done
> Could you also try the patch I attached to that bug report?
> If it works for
Hi!
I've been experiencing problems with this (internal) card ever since I
bought this motherboard, lately I've been doing some tests and I found out
some things, maybe not enough to let us debug this, but I'll explain it just
in case.
The problem is that if the uli526x card is set up (ifconfig
Hi!
I've been experiencing problems with this (internal) card ever since I
bought this motherboard, lately I've been doing some tests and I found out
some things, maybe not enough to let us debug this, but I'll explain it just
in case.
The problem is that if the uli526x card is set up (ifconfig
> See if the patch below takes care of all of that:
Yes, the patch seems to fix the problem, I have applied it over 2.6.24 and
now the machine is at 1000FD working ok.
Thanks for the fix.
Regards...
--
Manty/BestiaTester -> http://manty.net
--
To unsubscribe from this list: send the line
See if the patch below takes care of all of that:
Yes, the patch seems to fix the problem, I have applied it over 2.6.24 and
now the machine is at 1000FD working ok.
Thanks for the fix.
Regards...
--
Manty/BestiaTester - http://manty.net
--
To unsubscribe from this list: send the line
> I have today compiled dl2k from git, the version with the 2007-12-23 patches
> from Al Viro: dl2k endianness fixes (.24 fodder?) Right before the Al Viro
> patches. This seems to be working perfectly on my system.
Ok, I've been applying Al's patches one by one, everything went fine till I
As I didn't get any ideas on what to do to help find the problem with the
dl2k driver, I'm doing some tests to get to know what has broken it.
I have today compiled dl2k from git, the version with the 2007-12-23 patches
from Al Viro: dl2k endianness fixes (.24 fodder?) Right before the Al Viro
As I didn't get any ideas on what to do to help find the problem with the
dl2k driver, I'm doing some tests to get to know what has broken it.
I have today compiled dl2k from git, the version with the 2007-12-23 patches
from Al Viro: dl2k endianness fixes (.24 fodder?) Right before the Al Viro
I have today compiled dl2k from git, the version with the 2007-12-23 patches
from Al Viro: dl2k endianness fixes (.24 fodder?) Right before the Al Viro
patches. This seems to be working perfectly on my system.
Ok, I've been applying Al's patches one by one, everything went fine till I
applied
> I've been playing with ethtools and got it to work at 100FD by setting it
> manually, but if afterwards I set it to auto it again goes 1000 HD and thus
> not working again.
I have changed my gigabit switch for a 100Mb wrt and the dl2k sets the link
right at 100FD and works much better than when
I've been playing with ethtools and got it to work at 100FD by setting it
manually, but if afterwards I set it to auto it again goes 1000 HD and thus
not working again.
I have changed my gigabit switch for a 100Mb wrt and the dl2k sets the link
right at 100FD and works much better than when
Hi!
I have just updated my server to 2.6.24 and the dl2k driver has stopped
working.
The problem seems to be when autoselecting the media, the driver says that
the card is set as "Auto 1000 Mbps, Half duplex" instead of the usual "Auto
1000 Mbps, Full duplex", I have tried setting "options dl2k
Hi!
I have just updated my server to 2.6.24 and the dl2k driver has stopped
working.
The problem seems to be when autoselecting the media, the driver says that
the card is set as Auto 1000 Mbps, Half duplex instead of the usual Auto
1000 Mbps, Full duplex, I have tried setting options dl2k
> There was a bug in 2.6.23-rc8 that caused this to happen.
>
> It's been fixed in the later -git kernels
> (commits 2f3f22269bdf702311342c5d106dfdd7347d1c3e,
> 853298bc03ef65e3eb392f5d61265605214ee8fb).
You are right, I have downloaded current head of git and seems to work ok.
Sorry for the
> So for this to work, I believe that either ACPI or APM has to have been
> configured into the kernel (and the modules loaded). Your kernel .config
> from earlier shows ACPI built-in to the kernel core, so it should be
> present.
Yes, and it is indeed, the acpid is running and it detects my
So for this to work, I believe that either ACPI or APM has to have been
configured into the kernel (and the modules loaded). Your kernel .config
from earlier shows ACPI built-in to the kernel core, so it should be
present.
Yes, and it is indeed, the acpid is running and it detects my power
There was a bug in 2.6.23-rc8 that caused this to happen.
It's been fixed in the later -git kernels
(commits 2f3f22269bdf702311342c5d106dfdd7347d1c3e,
853298bc03ef65e3eb392f5d61265605214ee8fb).
You are right, I have downloaded current head of git and seems to work ok.
Sorry for the lost
I booted into single mode, then umounted all unneeded stuff and put / to ro,
stopped all unused raids, ... then did...
>/sbin/halt -f -p
>
> The machine *should* poweroff.
Nope, it didn't and what was curious was that I was left at the bash prompt
:-?
> If not, then do the whole thing again
> I'd say your problem is more of a distro issue,
> in that the method you are using to shutdown
> is not actually requesting "poweroff".
> That last mess above ("System halted.") comes from kernel_halt(),
> rather than the expected message ("Power down.") from kernel_power_off().
> So, try
Doesn't fix for me!
I have an Athlon x2 running on a Asus A8N-E mobo which has an NForce 4
chipset, I thought this patch would fix poweroff for me too, but it doesn't.
I'm seing this on 2.6.23-rc8 with and without your patch, here is what I get
on the console:
Shutdown: hdd
Shutdown: hda
System
Doesn't fix for me!
I have an Athlon x2 running on a Asus A8N-E mobo which has an NForce 4
chipset, I thought this patch would fix poweroff for me too, but it doesn't.
I'm seing this on 2.6.23-rc8 with and without your patch, here is what I get
on the console:
Shutdown: hdd
Shutdown: hda
System
I'd say your problem is more of a distro issue,
in that the method you are using to shutdown
is not actually requesting poweroff.
That last mess above (System halted.) comes from kernel_halt(),
rather than the expected message (Power down.) from kernel_power_off().
So, try using the
I booted into single mode, then umounted all unneeded stuff and put / to ro,
stopped all unused raids, ... then did...
/sbin/halt -f -p
The machine *should* poweroff.
Nope, it didn't and what was curious was that I was left at the bash prompt
:-?
If not, then do the whole thing again
> Please send me your .config as well as /etc/grub.conf and the output of
> /proc/cmdline.
I suppose you mean my grub's menu.lst, after looking at it I've done some
more tests and identified the posible cause.
This would be my grub menu.lst:
default 0
fallback 2
timeout 2
color
Please send me your .config as well as /etc/grub.conf and the output of
/proc/cmdline.
I suppose you mean my grub's menu.lst, after looking at it I've done some
more tests and identified the posible cause.
This would be my grub menu.lst:
default 0
fallback 2
timeout 2
color
Hi!
I have just compiled a 2.6.23-rc8 using the config from my 2.6.22 as a basis
and I came out with a not working (almost black) vga text console.
This is what I'm getting on my logs:
Console: colour dummy device 80x25
console [tty0] enabled
Instead of the old:
Console: colour VGA+ 80x25
Hi!
I have just compiled a 2.6.23-rc8 using the config from my 2.6.22 as a basis
and I came out with a not working (almost black) vga text console.
This is what I'm getting on my logs:
Console: colour dummy device 80x25
console [tty0] enabled
Instead of the old:
Console: colour VGA+ 80x25
I have just upgraded from 2.6.20 to 2.6.21, when I rebooted I thought the
computer had halted after loading snd_ymfpci, but what happens is that it
takes 2 minutes (120 seconds mesured with time) for the driver to load, but
then works as expected.
After making a diff between the 2.6.20 and 2.6.21
I have just upgraded from 2.6.20 to 2.6.21, when I rebooted I thought the
computer had halted after loading snd_ymfpci, but what happens is that it
takes 2 minutes (120 seconds mesured with time) for the driver to load, but
then works as expected.
After making a diff between the 2.6.20 and 2.6.21
> > As you can see I now can see the symbolic links perfectly and they work as
> > expected.
> >
> > In fact, this patch is working so well that it poses a security risk, as now
> > the devices on my /mnt/dev directory are not only seen as devices (like they
> > were seen on 2.4.33) but they also
Hi again!
I tried to replicate the problem at home during the weekend with my laptop,
but I couldn't get it to show links with previous kernels, so I guess I had
something different on my samba server or similar, I'm at the real machines
now so I have done the real tests and they look promising.
Hi again!
I tried to replicate the problem at home during the weekend with my laptop,
but I couldn't get it to show links with previous kernels, so I guess I had
something different on my samba server or similar, I'm at the real machines
now so I have done the real tests and they look promising.
As you can see I now can see the symbolic links perfectly and they work as
expected.
In fact, this patch is working so well that it poses a security risk, as now
the devices on my /mnt/dev directory are not only seen as devices (like they
were seen on 2.4.33) but they also work (which
Hi!
I have discovered a problem with the changes applied to smbfs in 2.4.34 and
in the security backports like last Debian's 2.4 kernel update these changes
seem to be made to solve CVE-2006-5871 and they have broken symbolic links
and changed the way that special files (like devices) are seen.
Hi!
I have discovered a problem with the changes applied to smbfs in 2.4.34 and
in the security backports like last Debian's 2.4 kernel update these changes
seem to be made to solve CVE-2006-5871 and they have broken symbolic links
and changed the way that special files (like devices) are seen.
Sorry for not replying before but I could not do any tests before today as
I didn't have access to any of the machines.
> Bingo!
Yes, I can confirm that your patch solves the problem, at least on my test
cases.
Thanks for your help!
Regards...
--
Santiago García Mantiñán
-
To unsubscribe from
Sorry for not replying before but I could not do any tests before today as
I didn't have access to any of the machines.
Bingo!
Yes, I can confirm that your patch solves the problem, at least on my test
cases.
Thanks for your help!
Regards...
--
Santiago García Mantiñán
-
To unsubscribe from
Hi!
When trying to upgrade a machine from 2.6.18 to 2.6.19.1 I found that it
crashed when loading the ebtables rules on startup.
This is an example of the crash I get:
BUG: unable to handle kernel paging request at virtual address e081e004
printing eip:
Hi!
When trying to upgrade a machine from 2.6.18 to 2.6.19.1 I found that it
crashed when loading the ebtables rules on startup.
This is an example of the crash I get:
BUG: unable to handle kernel paging request at virtual address e081e004
printing eip:
> Lovely... It's one of the long lists and these asserts (lines 650 and 654)
> are exactly what would happen if it was corrupted at some place. OTOH, it
> may be for real - i.e. real inodes in wrong state getting on the list, rather
> than corrupted pointer.
You were right, corrupted pointer.
Lovely... It's one of the long lists and these asserts (lines 650 and 654)
are exactly what would happen if it was corrupted at some place. OTOH, it
may be for real - i.e. real inodes in wrong state getting on the list, rather
than corrupted pointer.
You were right, corrupted pointer.
It
Hi!
That's what my server, wich is running 2.4.5, was shouting when I pluged in
my laptop at the console (ttyS0), all I could do was copy the output I was
seeing on minicom to a file, after rebooting I saw that the kernel had left
some of the logging on kern.log, so I'm attaching a file with
Hi!
That's what my server, wich is running 2.4.5, was shouting when I pluged in
my laptop at the console (ttyS0), all I could do was copy the output I was
seeing on minicom to a file, after rebooting I saw that the kernel had left
some of the logging on kern.log, so I'm attaching a file with
> No, that's OK.
I realised about this when I inserted up_and_exit on 2.2 and still it did
the same :-)
> Try putting an
> exit_files(current);
> at the start of rtl8139_thread()
Yes, this seems to solve the problem, thanks!
Regards...
--
Manty/BestiaTester -> http://manty.net
-
To
No, that's OK.
I realised about this when I inserted up_and_exit on 2.2 and still it did
the same :-)
Try putting an
exit_files(current);
at the start of rtl8139_thread()
Yes, this seems to solve the problem, thanks!
Regards...
--
Manty/BestiaTester - http://manty.net
-
To
Hi!
I was tracking down a problem with Debian installation freezing when doing
the ifconfig of the 8139too driver on 2.2.19 kernel, and found that this was
caused by 8139too for 2.2.19 not closing it's file descriptors.
The original code by Jeff for the 2.4 series is ok, and searching for the
Hi!
I was tracking down a problem with Debian installation freezing when doing
the ifconfig of the 8139too driver on 2.2.19 kernel, and found that this was
caused by 8139too for 2.2.19 not closing it's file descriptors.
The original code by Jeff for the 2.4 series is ok, and searching for the
> Are you using Becker's ftp://www.scyld.com/pub/diag/ether-wake.c ?
Yes.
> Did you turn on the enable_wol module option? Note that might be a new
> option in the 2.4.3-preXX series...
Well, it is indeed a 2.4.3-pre feature, as I had looked for it on 2.4.2, it
was not there, but it is at
Are you using Becker's ftp://www.scyld.com/pub/diag/ether-wake.c ?
Yes.
Did you turn on the enable_wol module option? Note that might be a new
option in the 2.4.3-preXX series...
Well, it is indeed a 2.4.3-pre feature, as I had looked for it on 2.4.2, it
was not there, but it is at least
Hi!
I used to be able to run my 12 ethernet ports pentium based bridge without
vga card, but with tty1, tty2, ... still working, as the kernel used to
recognice a kind of a cga card on my machine even though there was none. But
the kernel could write to the memory were the card was supposed to
Hi!
I used to be able to run my 12 ethernet ports pentium based bridge without
vga card, but with tty1, tty2, ... still working, as the kernel used to
recognice a kind of a cga card on my machine even though there was none. But
the kernel could write to the memory were the card was supposed to
56 matches
Mail list logo
