I've filed a new bug report #1281930.
Thanks for your help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003297
Title:
Networking and ACPI conflicts
To manage notifications about this bug go to:
Marco Aicardi, thank you for your comment. So your hardware and problem may be
tracked, could you please file a new report with Ubuntu by executing the
following in a terminal while booted into a Ubuntu repository kernel (not a
mainline one) via:
ubuntu-bug linux
For more on this, please read t
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003297
Title:
Networking and ACPI conflicts
To manage notifications about this bug g
As stated elsewhere
(http://ubuntuforums.org/showthread.php?t=2020571&page=2), it seems
there is a bug between forcedeth and AM3+ CPUs.
I have this conflict with Ubuntu 13.10 and it's solved by removing
forcedeth and reloading with "modprobe forcedeth msi=0 msix=0".
Please reopen this bug.
--
Y
Thanks Christopher - bug submitted - id 1264509
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1264509
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003297
Title:
Networking and ACPI conflict
JonnyTech, in order to track your hardware, could you please file a new report
via a terminal:
ubuntu-bug linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003297
Title:
Networking and ACPI conf
I can confirm that this is an ongoing problem and that the forcedeth
workarounds are the only way for me to use ubuntu/mint on my ASRock
motherboard.
Please consider fixing this...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003297
T
So now you're encouraging people to file a duplicate bug report. I
wasn't aware the policy had changed.
And take notice, anyone that happens across this page and is interested,
in the complete lack of a response to the fact that no one was ever
assigned to this bug, not from day one, even when th
David, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control
team, and Ubuntu Bug Squad would like you to please file a new report by
executing the following in a terminal while booted into a Ubuntu repository
kernel (not a mainline one) via:
ubuntu-bug linux
For more on this,
Step one in fixing the bug is getting Ubuntu to pay attention. If
Ubuntu doesn't pay attention, if they continue to just ignore it and
hope it goes away like they've done since the day the bug was filed, it
doesn't matter how much information we provide or how many hoops we jump
through, nothing w
Yeah, lets not let that happen, tell me how I can help and lets get this thing
up and fixed! we can do it!
> Date: Sun, 25 Aug 2013 02:46:50 +
> From: 1003...@bugs.launchpad.net
> To: yoshie1...@hotmail.com
> Subject: [Bug 1003297] Re: Networking and ACPI conflicts
>
>
Yes, this bug is still an issue. I believe this thread has been quiet
because we've all been, well, waiting and hoping for the devs to
actually fix the bug. But as the bug was never even assigned to anyone,
I'm beginning to feel this is going to be another one of those Ubuntu
bugs that's show-sto
This is still a problem, internet does not work on the card.
> Date: Sun, 25 Aug 2013 01:06:27 +
> From: christopher.m.penal...@gmail.com
> To: yoshie1...@hotmail.com
> Subject: [Bug 1003297] Re: Networking and ACPI conflicts
>
> Ganin, this bug was reported a while ag
Ganin, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/
I guess considering the lack of movement on this bug, the only real
longterm solution is to not use an ASrock motherboard. I know my next
motherboard will either be a Gigabyte or an Asus.
In the meantime though, as a workaround, here's something else you can
try:
First remove any of the other mo
I have this exact same problem with the exact same board with a clean
install of 12.10 32 bit except that only the Ubiquity reboot fails to
work. Normal reboot/shutdown works OK. None of the fixes here allowed
me to use the ethernet card on this board. The warning message in
/var/logs/syslog is a
I tested kernel 3.4 as per your instructions, and the bug still exists.
The error message of the bug has changed in this new kernel. It is now:
[8.416857] ACPI Warning: 0x0700-0x073f
SystemIO conflicts with Region \_SB_.PCI0.SM00 1
(20120320/utaddress-251)
However, th
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested
the upstream kernel, please remove the 'needs-upstream-testing' tag(Only
that one
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003297
Title:
Networking and ACPI conflicts
To manage notifications about this bug go to
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003297
Title:
Networking and ACPI conflicts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1003297/
21 matches
Mail list logo
