Hi all, just following up on this post: "I would also suggest though that if you had no issues on Quantal but are in Raring that it may be a kernel issue. Just because it is stable for everyone else doesn't mean it is for that particular machine, So I would file a bug first and see if there is any news from that before you go all kung-fu on the bios/uefi system. "ubuntu-bug linux" in a terminal will file most of the information on a kernel bug for you."
I followed this issue up with a bug report ( https://mail.google.com/mail/u/0/?shva=1#search/bios+update/13e557738ad3f9bc), but have hit a snag - also now detailed in the bug report. Following the instructions from the bug report I installed the upstream kernel to see whether that would fix the system freezes i was having. However my ability to test that kernel is limited by the fact that i can't get the wireless to work on the upstream kernel. I am not sure what the problem is here as wireless works on the current kernel and all the drivers remain installed when i boot to the upstream kernel. During the time i spent on the upstream kernel - tethered to the internet - i didn't have any freezes (working for about 12 hours) this is most encouraging, but i could use more time on it to really see whether its working. Also, the freezes on the current kernel are killing me, so if i could find a fix, or find a way to use the upstream kernel with wireless, that would be great. With the help through the bug report taking a little while to happen i was wondering if someone here might be able to help me trouble-shoot the wireless issue on the upstream kernel. Why wouldn't it work if it works on the current kernel and all the drivers remain installed? I don't know where to begin. Wireless card is: Broadcom Corporation BCM43228 802.11a/b/g/ and is currently running using the Broadcom 802.11 Linux STA wireless driver. Machine is running 64 bit 13.04. I realise that this question is deviating from my original one - about UEFI on a BIOS update - but i see this as all being part of the solution. When i manage to get round to calling Lenovo i will follow this email up with info about the EUFI and BIOS update. Thanks, j On 29 April 2013 16:24, alan c <aecl...@candt.waitrose.com> wrote: > On 29/04/13 12:45, James Morrissey wrote: > >> Hi Dave, >> >> Thanks for getting back to me. >> >> This may work flawlessly. However (and it's a big however) it may not. >> To combat this I would suggest that before you did anything you back >> up your systems and ensure you have install mediums for both windows 7 >> and Ubuntu. This would at least mean that the systems can be >> reinstalled and your data retrieved if the worst should happen. combat >> this >> I would suggest that before you did anything you back >> up your systems and ensure you have install mediums for both windows 7 >> and Ubuntu. This would at least mean that the systems can be >> reinstalled and your data retrieved if the worst should happen. >> - This is frustrating as all my install media are packed in a box which is >> being shipped from overseas. >> >> I would also suggest though that if you had no issues on Quantal but >> are in Raring that it may be a kernel issue. Just because it is >> stable for everyone else doesn't mean it is for that particular >> machine, So I would file a bug first and see if there is any news >> from that before you go all kung-fu on the bios/uefi system. >> "ubuntu-bug linux" in a terminal will file most of the information on >> a kernel bug for you. >> - I thought as much, but the first instruction under filling bugs is that >> you update your BIOS >> (https://help.ubuntu.com/**community/ReportingBugs<https://help.ubuntu.com/community/ReportingBugs> >> ) >> >> Anyway, i have now filed a bug ( >> https://bugs.launchpad.net/**ubuntu/+source/linux/+bug/**1174275<https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1174275> >> ). >> >> If anyone has any other advice i'd welcome it. >> > > The question comes to mind that although in principle the uefi 'bios' > should have a facility to disable uefi, at this stage of the game with a > number of things unproven and unpractised, the worst that could happen is > that uefi is installed, enabled, and the disable uefi is not working > properly. If this should happen, would it be possible to refalsh the bios > back to its existing state I wonder? > > -- > alan cocks > > > -- > ubuntu-uk@lists.ubuntu.com > https://lists.ubuntu.com/**mailman/listinfo/ubuntu-uk<https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk> > https://wiki.ubuntu.com/**UKTeam/ <https://wiki.ubuntu.com/UKTeam/> > www.ppeuk.org <http://www.peliteracy.org>
-- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
