Christopher, it's NOT that simple in this case.
I can confirm that 4.3.4 fails and that 4.4.0 works.
But there is definitely nothing in the mainline that might give a chance to
find the "offending" patch, that broke it.
All we _could_ probably do is test 4.4.rc1 ... 4.4rc8.
But that might become
Oleg, huge thanks for your hard work!!
Ты чудо!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1536397
Title:
[nForce2] pata_amd pata_acpi can't load
Status in linux package in Ubuntu:
Guessed so. Oleg did a marvellous job in figuring that out. That was not
easy-peasy by any means.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1536397
Title:
[nForce2] pata_amd pata_ac
** Bug watch added: Linux Kernel Bug Tracker #111901
http://bugzilla.kernel.org/show_bug.cgi?id=111901
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=111901
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member o
Nothing to do ??
I beg to differ!
kernel.org #111901 is a kind of RfC whether CRS usage with old hardware should
be levitated or whether users are---even in future---entitled to boot their <
4.4.0 kernels with pci=nocrs.
And as the forced enabling of CRS was causing the problems that Sergey
re
Besides, about your "fixed upstream": I think it was entirely accidental.
Something got modified in PCI handling, and abracadabra, it made old hardware
work again.
But as fas as I could read the code fix, it didn't look as if Sergey's and mine
hardware was actually targeted.
We were LUCKY that i
Public bug reported:
(This is a sort of RfC. )
I have a PC that still has the good old PCI ports, but I am 100% sure that the
active use of EISA dates back yet more 10 years.
In other words, boards that _only_ support EISA date back 25 years now, while
those that provide *one* EISA slot date ba
** Summary changed:
- (Wishlist) Change EISA support to M (modular)?
+ (Wishlist) Remove EISA support from main kernel image and make it M (modular)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
** Tags added: bot-stop-nagging
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1543919
Title:
(Wishlist) Remove EISA suppo
** Tags added: bitesize
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1543919
Title:
(Wishlist) Remove EISA support from main kernel image and make it M
(modular)?
Status in linux pa
Why "Incomplete"? There's nothing to supply. I simply need some
maintainer's/kernel team's/iuser's feedback on this.
Funny enough that even if I muzzled that bot, "New" still gets auto-changed to
"Incomplete", this time even without an explanation.
Brad, let your bots behave a little more nicely.
** Summary changed:
- (Wishlist) Remove EISA support from main kernel image and make it M (modular)?
+ Remove EISA support from main kernel image and make it M (modular)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
Many, many thanks Sergey!!
This problem really fussed me as I thought it's my hardware (as usual).
They must really have fixed a huge bug in 4.4.0.
For the Ubuntu folks here, note that 4.3.4 from Kernel Mainline will
still NOT work. (neither does 4.3.0-7, which made it into main repo only
2 days a
>4.3.0-040300-generic = pata_amd, pata_acpi error
>4.3.4-040304-generic = pata_amd, pata_acpi error
Confirmed!
> I tried to load Xubuntu 15.10 installation LiveCD from USB Stick. It
was loaded normally. (4.2.0-16-generic)
Aha, _that_ worked?
Well, my 4.2.x was exactly ... let me see ... 4.2.0-10
@Sergey, to find the actual bugger we'd have to test somewhere _between_ 4.3.5
and 4.3.9[99].
However, there was nothing like that available for testing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
Reinald, this is VERY interesting what you've written!
"and found the diskless system serveral times hanging after a day or so
with unrecoverable:"
This is exactly what I could witness on my live cd. It will work perfectly for
one day, then these artifacts will come up.
Whatever you're trying to
Ok, but why "Invalid" and not "Fix Released"?
(just curious :))
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1504078
Title:
[4.2.0-15.18] broken sound: 'output devices' not detected
17 matches
Mail list logo
