Re: [ubuntu-uk] UEFI bios update

[alan c]

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)

Anyway, i have now filed a bug (
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://wiki.ubuntu.com/UKTeam/

[ubuntu-uk] Odp: Reinstall wireless driver doesn't work in 13.04

[bumaw]

With previous versions of gcc

Install Packages

It seems that both gcc-4.3 and gcc-4.4 are installed after install 
build-essential. However, we can explicitly install the following packages:

sudo apt-get install gcc-4.3 gcc-4.4 g++-4.3 g++-4.4

Install Alternatives

Symbolic links cc and c++ are installed by default. We will install symbol 
links for gcc and g++, then link cc and c++ to gcc and g++ respectively.

sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.3 10
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.4 20

sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-4.3 10
sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-4.4 20

sudo update-alternatives --install /usr/bin/cc cc /usr/bin/gcc 30
sudo update-alternatives --set cc /usr/bin/gcc

sudo update-alternatives --install /usr/bin/c++ c++ /usr/bin/g++ 30
sudo update-alternatives --set c++ /usr/bin/g++

Configure Alternatives

The last step is configuring the default commands for gcc, g++. It's easy to 
switch between 4.3 and 4.4 interactively:

sudo update-alternatives --config gcc
sudo update-alternatives --config g++




So to summarise the solution in case you have the same problem:
1) Check https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1049466 to 
see whether there is now a better solution.
2) If not
a) Install kernel 3.6.3 by following 
http://www.upubuntu.com/2012/10/install-linux-kernel-363-in-ubuntu.html
b) Get the firmware by
git clone 
git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git
cd
cd linux-firmware
sudo cp rt3290.bin /lib/firmware

Now how do I mark this thread as solved? 

Reply With Quote 

Day Saturday, 27 Kwietnia 2013 10:07 Rowan Berkeley  
wrote 
> This is what happens when I try to 'make' the wireless driver.
> 
> root@rowan-Compaq:/home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508# make
> make -C tools
> make[1]: Entering directory 
> `/home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/tools'
> gcc -g bin2h.c -o bin2h
> make[1]: Leaving directory 
> `/home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/tools'
> /home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/tools/bin2h
> cp -f os/linux/Makefile.6 
> /home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/Makefile
> make -C /lib/modules/3.8.0-19-generic/build 
> SUBDIRS=/home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux modules
> make[1]: Entering directory `/usr/src/linux-headers-3.8.0-19-generic'
>CC [M] 
> /home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../common/rtmp_mcu.o
> /home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../common/rtmp_mcu.c:
>  
> In function ‘RtmpAsicSendCommandToMcu’:
> /home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../common/rtmp_mcu.c:464:8:
>  
> warning: unused variable ‘offset’ [-Wunused-variable]
> /home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../common/rtmp_mcu.c:463:8:
>  
> warning: unused variable ‘Configuration’ [-Wunused-variable]
>CC [M] 
> /home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.o
> /home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:43:23:
>  
> error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before 
> ‘rt2860_remove_one’
> /home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:44:22:
>  
> error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before 
> ‘rt2860_probe’
> /home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:63:46:
>  
> error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before 
> ‘__devinitdata’
> /home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:85:17:
>  
> error: ‘rt2860_pci_tbl’ undeclared here (not in a function)
> /home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:86:17:
>  
> error: ‘rt2860_probe’ undeclared here (not in a function)
> /home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:88:5:
>  
> error: implicit declaration of function ‘__devexit_p’ 
> [-Werror=implicit-function-declaration]
> /home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:88:29:
>  
> error: ‘rt2860_remove_one’ undeclared here (not in a function)
> /home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:292:24:
>  
> error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before 
> ‘rt2860_probe’
> /home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:463:23:
>  
> error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before 
> ‘rt2860_remove_one’
> /home/rowan/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:71:1:
>  
> error: ‘__mod_pci_device_table’ aliased to undefined symbol ‘rt2860_pci_tbl’
> cc1: some warnings being treated as errors
> make[2]: *** 
> [/home/rowan/DPO_RT329

Re: [ubuntu-uk] Wireless in 13.04

[Stuart Ward]

Rowan

Well done, I always advise (and mostly practice) of putting the exact error
message into goggle as soon as you can in the process of solving this sort
of problem. I cant tell you the numbers of times this has saved me hours of
fruitless searching for information about a problem.

Stuart


-- Stuart Ward M +44 7782325143


On 29 April 2013 13:23, Rowan Berkeley  wrote:

> Hi,
>
> I posted a message to the effect that the procedure for reinstalling the
> Ralink RT3290 wireless driver, which worked on 12.10, doesn't work after
> online upgrade to 13.04. Since posting that, I found an online report at
> askubuntu.com which gave the exact same error messages as mine:
> http://askubuntu.com/**questions/285163/ralink-**rt3290-cant-be-installed
>
> I have found that the best solution is to put a copy of the 64-bit version
> of 13.04 on a USB stick then do a complete reinstall from the stick. If you
> do this, the Ralink RT3290 wireless driver will be found and configured
> correctly and permanently. But not when you use the online upgrade from the
> Ubuntu site. This is similar to the problem I had with the boot protect in
> UEFI BIOS. There also, the USB stick with the 64-bit version was the answer.
>
>
>
>
>
> --
> ubuntu-uk@lists.ubuntu.com
> https://lists.ubuntu.com/**mailman/listinfo/ubuntu-uk
> https://wiki.ubuntu.com/**UKTeam/ 
>
-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.ubuntu.com/UKTeam/

Re: [ubuntu-uk] Wireless in 13.04

[Neil Greenwood]

Thanks for posting the solution.

Neil
On Apr 29, 2013 1:24 PM, "Rowan Berkeley"  wrote:

> Hi,
>
> I posted a message to the effect that the procedure for reinstalling the
> Ralink RT3290 wireless driver, which worked on 12.10, doesn't work after
> online upgrade to 13.04. Since posting that, I found an online report at
> askubuntu.com which gave the exact same error messages as mine:
> http://askubuntu.com/**questions/285163/ralink-**rt3290-cant-be-installed
>
> I have found that the best solution is to put a copy of the 64-bit version
> of 13.04 on a USB stick then do a complete reinstall from the stick. If you
> do this, the Ralink RT3290 wireless driver will be found and configured
> correctly and permanently. But not when you use the online upgrade from the
> Ubuntu site. This is similar to the problem I had with the boot protect in
> UEFI BIOS. There also, the USB stick with the 64-bit version was the answer.
>
>
>
>
>
> --
> ubuntu-uk@lists.ubuntu.com
> https://lists.ubuntu.com/**mailman/listinfo/ubuntu-uk
> https://wiki.ubuntu.com/**UKTeam/ 
>
-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.ubuntu.com/UKTeam/

[ubuntu-uk] Wireless in 13.04

[Rowan Berkeley]

Hi,

I posted a message to the effect that the procedure for reinstalling the 
Ralink RT3290 wireless driver, which worked on 12.10, doesn't work after 
online upgrade to 13.04. Since posting that, I found an online report at 
askubuntu.com which gave the exact same error messages as mine:

http://askubuntu.com/questions/285163/ralink-rt3290-cant-be-installed

I have found that the best solution is to put a copy of the 64-bit 
version of 13.04 on a USB stick then do a complete reinstall from the 
stick. If you do this, the Ralink RT3290 wireless driver will be found 
and configured correctly and permanently. But not when you use the 
online upgrade from the Ubuntu site. This is similar to the problem I 
had with the boot protect in UEFI BIOS. There also, the USB stick with 
the 64-bit version was the answer.






--
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.ubuntu.com/UKTeam/

Re: [ubuntu-uk] UEFI bios update

[James Morrissey]

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)

Anyway, i have now filed a bug (
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1174275).

If anyone has any other advice i'd welcome it.

j


On 29 April 2013 13:21, Dave Morley  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 29/04/13 12:04, James Morrissey wrote:
>
>
> 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.
>
> Ubuntu 64 bit supports both UEFI and secureboot so in theory there
> should be no issues there.  However grub is used differently in uefi
> than it is on a normal system and you would need an efi entry for
> Ubuntu and for windows 7 so efi acts as your os selector rather than grub.
>
> In saying all that it may work out of the box and you notice no real
> different because efi also has a bios compatibility mode,called
> legacy, that the system may enable by default and you be none the
> wiser for it.
>
> 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.
>
> - --
> You make it, I'll break it!
>
> I love my job :)
> http://www.ubuntu.com
> http://www.canonical.com
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with undefined - http://www.enigmail.net/
>
> iEYEARECAAYFAlF+V9YACgkQT5xqyT+h3Oi9TgCfehkYGRmU5HrQfVJZYgdeEicz
> SZEAoL2Oho0bBxhVj0GMHMQfeCl1QQjv
> =IcKJ
> -END PGP SIGNATURE-
>
> --
> ubuntu-uk@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
> https://wiki.ubuntu.com/UKTeam/
>

www.ppeuk.org 
-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.ubuntu.com/UKTeam/

Re: [ubuntu-uk] UEFI bios update

[Dave Morley]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 29/04/13 12:04, James Morrissey wrote:


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.

Ubuntu 64 bit supports both UEFI and secureboot so in theory there
should be no issues there.  However grub is used differently in uefi
than it is on a normal system and you would need an efi entry for
Ubuntu and for windows 7 so efi acts as your os selector rather than grub.

In saying all that it may work out of the box and you notice no real
different because efi also has a bios compatibility mode,called
legacy, that the system may enable by default and you be none the
wiser for it.

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.

- -- 
You make it, I'll break it!

I love my job :)
http://www.ubuntu.com
http://www.canonical.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlF+V9YACgkQT5xqyT+h3Oi9TgCfehkYGRmU5HrQfVJZYgdeEicz
SZEAoL2Oho0bBxhVj0GMHMQfeCl1QQjv
=IcKJ
-END PGP SIGNATURE-

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.ubuntu.com/UKTeam/

[ubuntu-uk] UEFI bios update

[James Morrissey]

Hi all,

I posted this in the forums, but have yet to get a response. I was
wondering if anyone here could help.

I'm trying to update my bios, but it looks like, in doing so, the update
wants to enable EFI.

I am looking to update my bios, because i keep having random system freezes
in 13.04 (everyone else is lauding the stability of the release) where
nothing works after the freeze - no input, no output. The machine has even
frozen during the shut-down sequence, forcing me, in all cases, to force
shutdown via the power key. I had none of these problems in 12.10.

I also have a problem where shutting down my system occasionally results in
a restart, although this problem was also around in 12.10 and 12.04.

These problems are sufficiently large (random freezes make my system too
unstable for work) for me to think that a bios update is worthwhile. Also,
my bios is very much out of date being version 1.08 with the update being
to version 2.05.

Notably however, my motherboard appears to be UEFI compatible as my bios
update wants to install UEFI features.

The release notes for the bios update (from the Lenovo website) contain the
following instructions:

"( If this is first time to apply UEFI BIOS Version G8ET66WW/G9ET65WW
(Ver.2.05) or newer version, you have to do following steps. This procedure
is required first time only.)

Windows 7 and Windows XP:

16. Power off the computer.
17. Power on the computer.

18. While the "To interrupt normal startup, press Enter" message is
displayed
at the lower-left area or lower-center area of the screen, press the F1
key.
The ThinkPad Setup menu will be displayed. If a password prompt appears,
type the correct password.
19. Choose "Security" then "Secure Boot" to show the menu.
20. Select "Restore Factory Keys" and press Enter.
21. Select "Yes" to restore Factory keys.
22. Press F10 key and select "Yes" to save and exit from Setup menu.
23. Then the computer is restarted."

I am running 13.04, 64 bit on a Lenovo Thinkpad x131e, dual booting windows
7.

Can anyone tell me if updating is going to prevent me from booting to
Ubuntu - which is my primary OS (ironically i only really keep windows on
the machine for the bios update utility)? Also, if i update the bios, can i
avoid any EFI problems by skipping some of the steps detailed in the bios
release notes? If so which ones?

Any help would be very much appreciated.

Thanks,

j

www.ppeuk.org 
-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.ubuntu.com/UKTeam/