UEFI problem

Post here if you are a new Porteus member and you're looking for some help.
User avatar
Ed_P
Contributor
Contributor
Posts: 3320
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: UEFI problem

Post#76 by Ed_P » 09 Oct 2013, 03:13

brokenman wrote:For your wireless card do some googling on: BCM4313 modprobe
You may need to modprobe wl, or one of the bcm* drivers. Please do a little searching (it is very self gratifying) and once you find the right driver to load, test the wireles.
:%) Tough to google on a system that doesn't have 'net access. And the system that does have 'net access doesn't know how to install drivers onto the system that doesn't.

Oh well, thanks for your help brokenman. The UEFI system is an Acer Aspire One 725, when you guys come up with a Porteus system that supports it's hardware let me know and I will try your script again.
Ed

User avatar
fanthom
Site Admin
Site Admin
Posts: 4617
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: UEFI problem

Post#77 by fanthom » 09 Oct 2013, 08:06

@EdP
broadcom case is well explained in my howto:
viewtopic.php?f=39&t=1099

you just need to blacklist certain drivers - that's it.
Please add [Solved] to your thread title if the solution was found.

User avatar
Ed_P
Contributor
Contributor
Posts: 3320
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: UEFI problem

Post#78 by Ed_P » 11 Oct 2013, 03:08

fanthom wrote:you just need to blacklist certain drivers - that's it.
Thanks fanthom.

Do you see anything I need to blacklist?

Code: Select all

guest@porteus:~$ lspci -knn
bash: lspci: command not found
guest@porteus:~$ su
Password: 
root@porteus:/home/guest# lspci -knn
00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 14h Processor Root Complex [1022:1510]
	Subsystem: Advanced Micro Devices [AMD] Family 14h Processor Root Complex [1022:1510]
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Device [1002:980a]
	Subsystem: Acer Incorporated [ALI] Device [1025:0740]
	Kernel driver in use: radeon
00:01.1 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI Wrestler HDMI Audio [Radeon HD 6250/6310] [1002:1314]
	Subsystem: Acer Incorporated [ALI] Device [1025:0740]
	Kernel driver in use: snd_hda_intel
00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Family 14h Processor Root Port [1022:1512]
	Kernel driver in use: pcieport
00:05.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Family 14h Processor Root Port [1022:1513]
	Kernel driver in use: pcieport
00:10.0 USB controller [0c03]: Advanced Micro Devices [AMD] Hudson USB XHCI Controller [1022:7812] (rev 03)
	Subsystem: Acer Incorporated [ALI] Device [1025:0740]
	Kernel driver in use: xhci_hcd
00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] Hudson SATA Controller [AHCI mode] [1022:7801]
	Subsystem: Acer Incorporated [ALI] Device [1025:0740]
	Kernel driver in use: ahci
00:12.0 USB controller [0c03]: Advanced Micro Devices [AMD] Hudson USB OHCI Controller [1022:7807] (rev 11)
	Subsystem: Acer Incorporated [ALI] Device [1025:0740]
	Kernel driver in use: ohci-pci
00:12.2 USB controller [0c03]: Advanced Micro Devices [AMD] Hudson USB EHCI Controller [1022:7808] (rev 11)
	Subsystem: Acer Incorporated [ALI] Device [1025:0740]
	Kernel driver in use: ehci-pci
00:13.0 USB controller [0c03]: Advanced Micro Devices [AMD] Hudson USB OHCI Controller [1022:7807] (rev 11)
	Subsystem: Acer Incorporated [ALI] Device [1025:0740]
	Kernel driver in use: ohci-pci
00:13.2 USB controller [0c03]: Advanced Micro Devices [AMD] Hudson USB EHCI Controller [1022:7808] (rev 11)
	Subsystem: Acer Incorporated [ALI] Device [1025:0740]
	Kernel driver in use: ehci-pci
00:14.0 SMBus [0c05]: Advanced Micro Devices [AMD] Hudson SMBus Controller [1022:780b] (rev 14)
	Subsystem: Acer Incorporated [ALI] Device [1025:0740]
00:14.2 Audio device [0403]: Advanced Micro Devices [AMD] Hudson Azalia Controller [1022:780d] (rev 01)
	Subsystem: Acer Incorporated [ALI] Device [1025:0740]
	Kernel driver in use: snd_hda_intel
00:14.3 ISA bridge [0601]: Advanced Micro Devices [AMD] Hudson LPC Bridge [1022:780e] (rev 11)
	Subsystem: Acer Incorporated [ALI] Device [1025:0740]
00:14.4 PCI bridge [0604]: Advanced Micro Devices [AMD] Hudson PCI Bridge [1022:780f] (rev 40)
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 0 [1022:1700] (rev 43)
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 1 [1022:1701]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 2 [1022:1702]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 3 [1022:1703]
	Kernel driver in use: k10temp
00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 4 [1022:1704]
00:18.5 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 6 [1022:1718]
00:18.6 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 5 [1022:1716]
00:18.7 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 7 [1022:1719]
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 05)
	Subsystem: Acer Incorporated [ALI] Device [1025:0740]
	Kernel driver in use: r8169
02:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
	Subsystem: Foxconn International, Inc. Device [105b:e042]
root@porteus:/home/guest# 
Cause I don't. :unknown:
Ed

User avatar
fanthom
Site Admin
Site Admin
Posts: 4617
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: UEFI problem

Post#79 by fanthom » 11 Oct 2013, 08:20

@EdP
please start another thread and i'll give you an answer (users with UEFI troubles probably dont want to read about wifi/other issues)
Please add [Solved] to your thread title if the solution was found.

User avatar
Ed_P
Contributor
Contributor
Posts: 3320
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: UEFI problem

Post#80 by Ed_P » 11 Oct 2013, 17:03

fanthom wrote:@EdP
please start another thread and i'll give you an answer (users with UEFI troubles probably dont want to read about wifi/other issues)
Fair enough fanthom. New thread here: viewtopic.php?f=81&t=2671
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5574
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: UEFI problem

Post#81 by brokenman » 11 Oct 2013, 21:08

when you guys come up with a Porteus system that supports it's hardware let me know and I will try your script again.
Seriously? This leaves a sour taste in my mouth and does not encourage me to help you further with anything. UEFI is a relatively new introduction to hardware and still in it's teething stage for linux.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3320
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: UEFI problem

Post#82 by Ed_P » 11 Oct 2013, 22:33

brokenman wrote:
when you guys come up with a Porteus system that supports it's hardware let me know and I will try your script again.
Seriously? This leaves a sour taste in my mouth and does not encourage me to help you further with anything. UEFI is a relatively new introduction to hardware and still in it's teething stage for linux.
!!! I certainly wasn't trying to annoy you. Wow!! Sorry that it came across that way. :sorry:

Yes, I agree and understand your view on UEFI. It's still new for booting flash drives and multi-boot systems also. And I am VERY impressed that you have developed a way to boot Porteus on it, without having to change the machine's BIOS to legacy mode and back again.
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5574
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: UEFI problem

Post#83 by brokenman » 12 Oct 2013, 01:56

No harm done. Perhaps I was being over sensitive and read it the wrong way.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3320
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: UEFI problem

Post#84 by Ed_P » 12 Oct 2013, 02:39

brokenman wrote:No harm done.
Thank God. :beer:
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 3320
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: UEFI problem

Post#85 by Ed_P » 12 Oct 2013, 05:35

WOW!!

Coming to you LIVE from a UEFI machine. :Yahoo!:



Thank you brokenman. :good:

Thank you fanthom :good:
Ed

User avatar
wread
Module Guard
Module Guard
Posts: 1094
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

Re: UEFI problem

Post#86 by wread » 12 Oct 2013, 15:20

@brokenman
Hi, Jay!
Must UEFI be run from a dos partition? Is that not a security hole? Could "they" develop a virus to destroy or damage the UEFI-partition?

I see it coming: UEFI-attacks...http://news.softpedia.com/news/Flaws-in ... 2798.shtml

See also http://it.slashdot.org/story/13/08/03/0 ... ecure-boot

Could UEFI be hosted in a posix partition? If not, why?

As you are the best UEFI-informed Porteus member, could you make us less (or more) afraid of UEFI?

I am thinking of buying me a new laptop and almost choosing one "without" UEFI :oops:

Regards
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

User avatar
brokenman
Site Admin
Site Admin
Posts: 5574
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: UEFI problem

Post#87 by brokenman » 12 Oct 2013, 18:28

Yes a FAT partition is required for the boot partition of a UEFI machine.
Could "they" develop a virus to destroy or damage the UEFI-partition?
Yes they could (and probably will) find ways to breach the security. This has always been the case and always will. In my mind UEFI is an improvement over BIOS, and secure boot does in fact make it harder to boot into a rootkit. The whole idea of secure boot is that the binary being loaded must be signed. If it is not signed it will not load. In my case I sign my own binaries so I know that no rootkit will boot. It is possible that a third party application within windows (or linux) could install itself to the boot partition but they would then need to become signed. I don't know enough about the windows signing method to comment but on my linux machine this would be impossible.

The MBR has gone and replaced with a GUID (aka GPT "GUID Partition Table") which stores backed up info at the end of the drive too, making recovery of corrupt partitions easier. In any case I immediately imaged the EFI system partition when I bought the laptop as I knew there was a chance of me breaking something. At LBA0 (first 512Kb) there is a fake mbr so if someone installs the older MBR it will not destroy the GUID. The primary GPT header is at logical block 1 and there is a secondary at the last readable block LBA -1 of the disk.

As of today the boot partition can not be anything else but FAT. The firmware is hard coded to only search for this type of partition. Another attack vector could be replacing the FAT32 driver that is loaded but again I am speculating.

My advice is to buy UEFI/BIOS hybrid which is what I have. I can switch from UEFI mode into CMS (normal bios) mode. I recommend this because UEFI is not going away. Everybody will have to face the music some day but it is nice to have something as familiar as the bios when starting to tinker.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
wread
Module Guard
Module Guard
Posts: 1094
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

Re: UEFI problem

Post#88 by wread » 12 Oct 2013, 20:47

Thanks jay, very good explanations!
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

User avatar
Ed_P
Contributor
Contributor
Posts: 3320
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: UEFI problem

Post#89 by Ed_P » 18 Oct 2013, 03:49

@brokenman

FYI Tonight on the UEFI machine I created a Windows 8 Recovery USB flash drive. Like the UEFI Porteus flash drive it boots easily on the UEFI machine.

But on a non-UEFI Windows 7 machine the two flash drives are considerably different. The two FAT32 partitions on the Porteus flash drive show up in Disk Management but do not have drive letters and do not show up in Windows Explorer. The Windows 8 Recovery flash drive has a single FAT32 partition which does get assigned a drive letter and is accessible in Windows Explorer.

Disk Management shows the Porteus flash drive's 1st partition as a EFI System Partition and the 2nd partition as a Primary Partition. Disk management shows the Windows 8 Recovery flash drive's partition as Active, Primary Partition. The files on the partition are:

Code: Select all

C:\Users\Ed>dir f:
 Volume in drive F is RECOVERY
 Volume Serial Number is EAE3-809F

 Directory of F:\

10/17/2013  09:25 PM    <DIR>          efi
10/17/2013  09:25 PM    <DIR>          boot
10/17/2013  09:25 PM    <DIR>          sources
07/25/2012  11:44 PM           398,156 bootmgr
09/20/2012  04:31 AM         1,350,888 bootmgr.efi
               2 File(s)      1,749,044 bytes
               3 Dir(s)   3,761,119,232 bytes free
It would be interesting if the Porteus UEFI approach could use a similar approach as the Windows 8 Recovery approach with it's partitions. The flash drive would be bootable on all machines.
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 3320
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: UEFI problem

Post#90 by Ed_P » 19 Oct 2013, 15:19

@brokenman

BTW The Windows 8 UEFI Recovery flash drive boots on non-UEFI machines also!! :D

Here are images of the flash drive's LBAs you referenced as key:

http://imageshack.us/a/img571/1152/dawt.png
http://imageshack.us/a/img401/6439/ixf4.png
http://imageshack.us/a/img585/1014/9841.png

HTH
brokenman wrote: At LBA0 (first 512Kb) there is a fake mbr so if someone installs the older MBR it will not destroy the GUID. The primary GPT header is at logical block 1 and there is a secondary at the last readable block LBA -1 of the disk.
Ed

Post Reply