UEFI problem

Post here if you are a new Porteus member and you're looking for some help.
Post Reply
User avatar
brokenman
Site Admin
Site Admin
Posts: 6105
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil

Re: UEFI problem

Post#61 by brokenman » 05 Oct 2013, 23:00

You may want to try replacing 3 files on the UEFI USB with files from the standard Porteus 64bit ISO. I don't recall right now if the recompiled kernel was only needed to support the secure boot. You can test to see.

Mount the ISO you have been booting from (as root):
mloop /path/to/Porteus-v2.1-x86_64.xzm
This will mount the ISO at /mnt/loop
Copy the following files from /mnt/loop onto the UEFI USB: initrd.xz, vmlinuz, 000-kernel.xzm

find /mnt/loop -name initrd.xz
000-kernel.xzm belongs in the porteus/base folder and the other two belong in the /EFI/porteus folder.
How do i become super user?
Wear your underpants on the outside and put on a cape.
Top
User avatar
Ed_P
Contributor
Contributor
Posts: 8578
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Re: UEFI problem

Post#62 by Ed_P » 06 Oct 2013, 01:56

brokenman wrote:You may want to try replacing 3 files on the UEFI USB with files from the standard Porteus 64bit ISO. I don't recall right now if the recompiled kernel was only needed to support the secure boot. You can test to see.

Mount the ISO you have been booting from (as root):
mloop /path/to/Porteus-v2.1-x86_64.xzm
This will mount the ISO at /mnt/loop
Copy the following files from /mnt/loop onto the UEFI USB: initrd.xz, vmlinuz, 000-kernel.xzm
I can't do that. The ISO file is on the Win 7 machine and the Win 7 machine has no access to the flash drive.
find /mnt/loop -name initrd.xz
000-kernel.xzm belongs in the porteus/base folder and the other two belong in the /EFI/porteus folder.
Is "find" a command or something I am to do?
Top
User avatar
Ed_P
Contributor
Contributor
Posts: 8578
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Re: UEFI problem

Post#63 by Ed_P » 06 Oct 2013, 02:25

brokenman wrote:You can return the USB to it's former glory by using the commands:
parted /dev/sdX
mklabel msdos
quit
Then partition it using gparted or whatever your tool of preference is.
Doing this and rerunning the script would be a lot easier if Fresh mode wasn't required. Why is it required?
Top
User avatar
brokenman
Site Admin
Site Admin
Posts: 6105
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil

Re: UEFI problem

Post#64 by brokenman » 06 Oct 2013, 15:48

I can't do that. The ISO file is on the Win 7 machine and the Win 7 machine has no access to the flash drive.
Boot into porteus to do it.
Is "find" a command or something I am to do?
It is a command. Sorry I forgot to bold it like all the other commands. 'find' is used to search for files at the console.
Doing this and rerunning the script would be a lot easier if Fresh mode wasn't required. Why is it required?
It's not required anymore. That is why I rewrote the script for you. You can boot into Porteus via an ISO file and run the script now.

EDIT:
I've updated the files on the server. The kernel is now at 3.11.4 stable and I used the same config as Porteus-v2.1 with the addition of EFI support (and some nvidia stuff I needed).
How do i become super user?
Wear your underpants on the outside and put on a cape.
Top
User avatar
Ed_P
Contributor
Contributor
Posts: 8578
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Re: UEFI problem

Post#65 by Ed_P » 06 Oct 2013, 19:58

brokenman wrote:
I can't do that. The ISO file is on the Win 7 machine and the Win 7 machine has no access to the flash drive.
Boot into porteus to do it.
hmmmm An interesting option.
Doing this and rerunning the script would be a lot easier if Fresh mode wasn't required. Why is it required?
It's not required anymore. That is why I rewrote the script for you. You can boot into Porteus via an ISO file and run the script now.
I normally boot my ISO with the change= cheatcode. To boot it in Fresh mode I removed the cheatcode.

I will do a rebuild tonight and report the results.

:beer:
Top
User avatar
brokenman
Site Admin
Site Admin
Posts: 6105
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil

Re: UEFI problem

Post#66 by brokenman » 06 Oct 2013, 20:24

I normally boot my ISO with the change= cheatcode. To boot it in Fresh mode I removed the cheatcode.
Ok i understand now. It is not imperative but it will always be the standard response from all devs. It ensures that no extra user added files are in the way and causing problems which could potentially use up a lot of time only to find that the problem is on the user side.

Thanks for testing.
How do i become super user?
Wear your underpants on the outside and put on a cape.
Top
User avatar
Ed_P
Contributor
Contributor
Posts: 8578
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Re: UEFI problem

Post#67 by Ed_P » 06 Oct 2013, 23:08

brokenman wrote:
I can't do that. The ISO file is on the Win 7 machine and the Win 7 machine has no access to the flash drive.
Boot into porteus to do it.
Son of a gun, that works!! :good: So accessing the UEFI flash drive is a Windows 7 problem not a non-UEFI machine problem.
brokenman wrote:
Is "find" a command or something I am to do?
It is a command. Sorry I forgot to bold it like all the other commands. 'find' is used to search for files at the console.


EDIT:
I've updated the files on the server. The kernel is now at 3.11.4 stable and I used the same config as Porteus-v2.1 with the addition of EFI support (and some nvidia stuff I needed).
I'm a little confused at this point. Am I searching for and copying files to the existing build or am I nuk'ing the flash drive and rerunning the script.



Ok, I tried this approach:

Code: Select all

guest@porteus:~$ parted /dev/sdb
bash: parted: command not found
guest@porteus:~$ su
Password: 
root@porteus:/home/guest# parted /dev/sdb
GNU Parted 2.3
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mklabel msdos                                                    
Warning: Partition(s) on /dev/sdb are being used.                         
Ignore/Cancel? ignore                                                     
Warning: The existing disk label on /dev/sdb will be destroyed and all data on
this disk will be lost. Do you want to continue?
Yes/No? yes                                                               
Error: Partition(s) 1, 2 on /dev/sdb have been written, but we have been unable
to inform the kernel of the change, probably because it/they are in use.  As a
result, the old partition(s) will remain in use.  You should reboot now before
making further changes.
Ignore/Cancel? ignore                                                     
(parted) quit                                                             
Information: You may need to update /etc/fstab.                           

root@porteus:/home/guest#
:o


Rebooted

Ran GParted and reallocated a FAT32 partition.
Got the same GParted mlabel: invalid option "i" error

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# blkid
/dev/sda1: LABEL="PQSERVICE" UUID="9894832D94830CC6" TYPE="ntfs" 
/dev/sda2: LABEL="SYSTEM RESERVED" UUID="ECF483DEF483AA02" TYPE="ntfs" 
/dev/sda3: LABEL="Acer" UUID="48168114168103E2" TYPE="ntfs" 
/dev/sda5: LABEL="Data" UUID="01CD20066B8BF780" TYPE="ntfs" 
/dev/sda6: LABEL="BKUPS" UUID="14E65B5EE65B3F64" TYPE="ntfs" 
/dev/loop0: LABEL="Porteus" TYPE="iso9660" 
/dev/loop1: TYPE="squashfs" 
/dev/loop2: TYPE="squashfs" 
/dev/loop3: TYPE="squashfs" 
/dev/loop4: TYPE="squashfs" 
/dev/loop5: TYPE="squashfs" 
root@porteus:/home/guest# blkid
/dev/sda1: LABEL="PQSERVICE" UUID="9894832D94830CC6" TYPE="ntfs" 
/dev/sda2: LABEL="SYSTEM RESERVED" UUID="ECF483DEF483AA02" TYPE="ntfs" 
/dev/sda3: LABEL="Acer" UUID="48168114168103E2" TYPE="ntfs" 
/dev/sda5: LABEL="Data" UUID="01CD20066B8BF780" TYPE="ntfs" 
/dev/sda6: LABEL="BKUPS" UUID="14E65B5EE65B3F64" TYPE="ntfs" 
/dev/loop0: LABEL="Porteus" TYPE="iso9660" 
/dev/loop1: TYPE="squashfs" 
/dev/loop2: TYPE="squashfs" 
/dev/loop3: TYPE="squashfs" 
/dev/loop4: TYPE="squashfs" 
/dev/loop5: TYPE="squashfs" 
/dev/sdb1: LABEL="PORTEUSEFI" UUID="713D-AD3E" TYPE="vfat" 
root@porteus:/home/guest#
Continuing with....
Look familiar?

Code: Select all

root@porteus:/home/guest# sh /home/guest/Downloads/create-uefi-usb-v2.sh

#### WELCOME TO THE PORTEUS UEFI USB CREATOR ####
#### Type quit at any question to quit.
Script by Brokenman


/dev/sda1: LABEL="PQSERVICE" UUID="9894832D94830CC6" TYPE="ntfs" 
/dev/sda2: LABEL="SYSTEM RESERVED" UUID="ECF483DEF483AA02" TYPE="ntfs" 
/dev/sda3: LABEL="Acer" UUID="48168114168103E2" TYPE="ntfs" 
/dev/sda5: LABEL="Data" UUID="01CD20066B8BF780" TYPE="ntfs" 
/dev/sda6: LABEL="BKUPS" UUID="14E65B5EE65B3F64" TYPE="ntfs" 
/dev/sdb1: LABEL="PORTEUSEFI" UUID="713D-AD3E" TYPE="vfat" 

Above is a list of your partitions.
Please enter the base path to your target USB device.
Example: /dev/sdc (no numbers)
> dev/sdb
1
Target verified as removable

We will now format your USB dev/sdb device with partition UUID's:
713D-AD3E
MAKE SURE YOU ARE CERTAIN!!
Would you like to continue? [y/n]
y

GPT fdisk (gdisk) version 0.8.5

Problem opening dev/sdb for reading! Error is 2.
The specified file does not exist!
mkfs.fat 3.0.22 (2013-07-19)
dev/sdb1: No such file or directory

Please select a partition type for Porteus
[1] FAT32
[2] ext2
[3] ext3
[4] ext4

1mkfs.fat 3.0.22 (2013-07-19)
dev/sdb2: No such file or directory

We will now download the required files (20Mb)from the internet.
Make sure you have an internet connection before continuing.
Press enter to continue

--2013-10-06 22:52:54--  https://dl.dropbox.com/s/1bsl2nqtfv1i01x/porteus-uefi-usb-template.tar.xz
Resolving dl.dropbox.com (dl.dropbox.com)... 54.235.95.67
Connecting to dl.dropbox.com (dl.dropbox.com)|54.235.95.67|:443... connected.
WARNING: cannot verify dl.dropbox.com's certificate, issued by ‘/C=US/O=Thawte, Inc./CN=Thawte SSL CA’:
  Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 302 FOUND
Location: https://dl.dropboxusercontent.com/s/1bsl2nqtfv1i01x/porteus-uefi-usb-template.tar.xz [following]
--2013-10-06 22:52:55--  https://dl.dropboxusercontent.com/s/1bsl2nqtfv1i01x/porteus-uefi-usb-template.tar.xz
Resolving dl.dropboxusercontent.com (dl.dropboxusercontent.com)... 54.243.118.205
Connecting to dl.dropboxusercontent.com (dl.dropboxusercontent.com)|54.243.118.205|:443... connected.
WARNING: cannot verify dl.dropboxusercontent.com's certificate, issued by ‘/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance CA-3’:
  Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 200 OK
Length: 3893752 (3.7M) [application/octet-stream]
Saving to: ‘/home/guest/Downloads/efimods/porteus-uefi-usb-template.tar.xz’

100%[======================================>] 3,893,752   78.7KB/s   in 28s    

2013-10-06 22:53:25 (138 KB/s) - ‘/home/guest/Downloads/efimods/porteus-uefi-usb-template.tar.xz’ saved [3893752/3893752]

--2013-10-06 22:53:25--  https://dl.dropbox.com/s/9nrwswxk1av5gaz/000-uefi-kernel.xzm
Resolving dl.dropbox.com (dl.dropbox.com)... 54.235.95.67
Connecting to dl.dropbox.com (dl.dropbox.com)|54.235.95.67|:443... connected.
WARNING: cannot verify dl.dropbox.com's certificate, issued by ‘/C=US/O=Thawte, Inc./CN=Thawte SSL CA’:
  Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 302 FOUND
Location: https://dl.dropboxusercontent.com/s/9nrwswxk1av5gaz/000-uefi-kernel.xzm [following]
--2013-10-06 22:53:25--  https://dl.dropboxusercontent.com/s/9nrwswxk1av5gaz/000-uefi-kernel.xzm
Resolving dl.dropboxusercontent.com (dl.dropboxusercontent.com)... 54.243.118.205
Connecting to dl.dropboxusercontent.com (dl.dropboxusercontent.com)|54.243.118.205|:443... connected.
WARNING: cannot verify dl.dropboxusercontent.com's certificate, issued by ‘/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance CA-3’:
  Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 200 OK
Length: 15777792 (15M) [application/octet-stream]
Saving to: ‘/home/guest/Downloads/efimods/000-uefi-kernel.xzm’

100%[======================================>] 15,777,792  71.8KB/s   in 2m 3s  

2013-10-06 22:55:29 (126 KB/s) - ‘/home/guest/Downloads/efimods/000-uefi-kernel.xzm’ saved [15777792/15777792]

ntfs-3g: Failed to access volume 'dev/sdb2': No such file or directory

ntfs-3g 2013.1.13 integrated FUSE 27 - Third Generation NTFS Driver
		Configuration type 1, XATTRS are on, POSIX ACLS are off

Copyright (C) 2005-2007 Yura Pakhuchiy
Copyright (C) 2006-2009 Szabolcs Szakacsits
Copyright (C) 2007-2012 Jean-Pierre Andre
Copyright (C) 2009 Erik Larsson

Usage:    ntfs-3g [-o option[,...]] <device|image_file> <mount_point>

Options:  ro (read-only mount), windows_names, uid=, gid=,
          umask=, fmask=, dmask=, streams_interface=.
          Please see the details in the manual (type: man ntfs-3g).

Example: ntfs-3g /dev/sda1 /mnt/windows

News, support and information:  http://tuxera.com
ntfs-3g: Failed to access volume 'dev/sdb1': No such file or directory

ntfs-3g 2013.1.13 integrated FUSE 27 - Third Generation NTFS Driver
		Configuration type 1, XATTRS are on, POSIX ACLS are off

Copyright (C) 2005-2007 Yura Pakhuchiy
Copyright (C) 2006-2009 Szabolcs Szakacsits
Copyright (C) 2007-2012 Jean-Pierre Andre
Copyright (C) 2009 Erik Larsson

Usage:    ntfs-3g [-o option[,...]] <device|image_file> <mount_point>

Options:  ro (read-only mount), windows_names, uid=, gid=,
          umask=, fmask=, dmask=, streams_interface=.
          Please see the details in the manual (type: man ntfs-3g).

Example: ntfs-3g /dev/sda1 /mnt/windows

News, support and information:  http://tuxera.com
Creating EPS file structure ...
EFI/
EFI/tools/
EFI/tools/drivers_x64/
EFI/tools/drivers_x64/reiserfs_x64.efi
EFI/tools/drivers_x64/iso9660_x64.efi
EFI/tools/drivers_x64/hfs_x64.efi
EFI/tools/drivers_x64/ext4_x64.efi
EFI/tools/drivers_x64/ext2_x64.efi
EFI/tools/drivers_x64/btrfs_x64.efi
EFI/tools/drivers_x64/LICENSE_GPL.txt
EFI/tools/drivers_x64/LICENSE.txt
EFI/tools/Shell.efi
EFI/porteus/
EFI/porteus/refind.conf
EFI/porteus/initrd.xz
EFI/porteus/vmlinuz
EFI/BOOT/
EFI/BOOT/refind.conf
EFI/BOOT/icons/
EFI/BOOT/icons/tool_memtest.icns
EFI/BOOT/icons/arrow_right.icns
EFI/BOOT/icons/os_linux.icns
EFI/BOOT/icons/os_legacy.icns
EFI/BOOT/icons/tool_mok_tool.icns
EFI/BOOT/icons/os_win.icns
EFI/BOOT/icons/tool_shell.icns
EFI/BOOT/icons/arrow_left.icns
EFI/BOOT/icons/vol_external.icns
EFI/BOOT/icons/os_slackware.icns
EFI/BOOT/icons/func_exit.icns
EFI/BOOT/icons/func_firmware.icns
EFI/BOOT/icons/boot_win.icns
EFI/BOOT/icons/transparent.icns
EFI/BOOT/icons/boot_linux.icns
EFI/BOOT/icons/func_about.icns
EFI/BOOT/icons/tool_apple_rescue.icns
EFI/BOOT/icons/vol_internal.icns
EFI/BOOT/icons/tool_part.icns
EFI/BOOT/icons/func_shutdown.icns
EFI/BOOT/icons/func_reset.icns
EFI/BOOT/icons/vol_optical.icns
EFI/BOOT/icons/os_unknown.icns
EFI/BOOT/icons/os_refind.icns
EFI/BOOT/bootx64.efi
EFI/BOOT/myicons/
EFI/BOOT/myicons/porteus-text.png
EFI/BOOT/myicons/porteus-saved.png
EFI/BOOT/myicons/porteus-ram.png
EFI/BOOT/myicons/porteus-fresh.png
EFI/BOOT/myicons/porteus-bootloader.bmp
EFI/BOOT/myicons/func_shutdown.icns
EFI/BOOT/myicons/func_reset.icns
EFI/BOOT/myicons/func_exit.icns
EFI/BOOT/myicons/func_about.icns
/home/guest

Copying porteus files ...
Finishing installation ....
Your installation has finished!!
Make sure you set your system to boot
into UEFI mode and reboot now!
root@porteus:/home/guest# blkid
/dev/sda1: LABEL="PQSERVICE" UUID="9894832D94830CC6" TYPE="ntfs" 
/dev/sda2: LABEL="SYSTEM RESERVED" UUID="ECF483DEF483AA02" TYPE="ntfs" 
/dev/sda3: LABEL="Acer" UUID="48168114168103E2" TYPE="ntfs" 
/dev/sda5: LABEL="Data" UUID="01CD20066B8BF780" TYPE="ntfs" 
/dev/sda6: LABEL="BKUPS" UUID="14E65B5EE65B3F64" TYPE="ntfs" 
/dev/loop0: LABEL="Porteus" TYPE="iso9660" 
/dev/loop1: TYPE="squashfs" 
/dev/loop2: TYPE="squashfs" 
/dev/loop3: TYPE="squashfs" 
/dev/loop4: TYPE="squashfs" 
/dev/loop5: TYPE="squashfs" 
/dev/sdb1: LABEL="PORTEUSEFI" UUID="713D-AD3E" TYPE="vfat" 
root@porteus:/home/guest#
There has got to be an easier way. :%)

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# parted /dev/sdb
GNU Parted 2.3
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mklabel msdos                                                    
Warning: The existing disk label on /dev/sdb will be destroyed and all data on
this disk will be lost. Do you want to continue?
Yes/No? yes                                                               
(parted) quit                                                             
Information: You may need to update /etc/fstab.                           

root@porteus:/home/guest# blkid
/dev/sda1: LABEL="PQSERVICE" UUID="9894832D94830CC6" TYPE="ntfs" 
/dev/sda2: LABEL="SYSTEM RESERVED" UUID="ECF483DEF483AA02" TYPE="ntfs" 
/dev/sda3: LABEL="Acer" UUID="48168114168103E2" TYPE="ntfs" 
/dev/sda5: LABEL="Data" UUID="01CD20066B8BF780" TYPE="ntfs" 
/dev/sda6: LABEL="BKUPS" UUID="14E65B5EE65B3F64" TYPE="ntfs" 
/dev/loop0: LABEL="Porteus" TYPE="iso9660" 
/dev/loop1: TYPE="squashfs" 
/dev/loop2: TYPE="squashfs" 
/dev/loop3: TYPE="squashfs" 
/dev/loop4: TYPE="squashfs" 
/dev/loop5: TYPE="squashfs" 
root@porteus:/home/guest# blkid
/dev/sda1: LABEL="PQSERVICE" UUID="9894832D94830CC6" TYPE="ntfs" 
/dev/sda2: LABEL="SYSTEM RESERVED" UUID="ECF483DEF483AA02" TYPE="ntfs" 
/dev/sda3: LABEL="Acer" UUID="48168114168103E2" TYPE="ntfs" 
/dev/sda5: LABEL="Data" UUID="01CD20066B8BF780" TYPE="ntfs" 
/dev/sda6: LABEL="BKUPS" UUID="14E65B5EE65B3F64" TYPE="ntfs" 
/dev/loop0: LABEL="Porteus" TYPE="iso9660" 
/dev/loop1: TYPE="squashfs" 
/dev/loop2: TYPE="squashfs" 
/dev/loop3: TYPE="squashfs" 
/dev/loop4: TYPE="squashfs" 
/dev/loop5: TYPE="squashfs" 
/dev/sdb1: LABEL="PORTEUSEFI" UUID="3216-C143" TYPE="vfat" 
root@porteus:/home/guest# sh /home/guest/Downloads/create-uefi-usb-v2.sh

#### WELCOME TO THE PORTEUS UEFI USB CREATOR ####
#### Type quit at any question to quit.
Script by Brokenman


/dev/sda1: LABEL="PQSERVICE" UUID="9894832D94830CC6" TYPE="ntfs" 
/dev/sda2: LABEL="SYSTEM RESERVED" UUID="ECF483DEF483AA02" TYPE="ntfs" 
/dev/sda3: LABEL="Acer" UUID="48168114168103E2" TYPE="ntfs" 
/dev/sda5: LABEL="Data" UUID="01CD20066B8BF780" TYPE="ntfs" 
/dev/sda6: LABEL="BKUPS" UUID="14E65B5EE65B3F64" TYPE="ntfs" 
/dev/sdb1: LABEL="PORTEUSEFI" UUID="3216-C143" TYPE="vfat" 

Above is a list of your partitions.
Please enter the base path to your target USB device.
Example: /dev/sdc (no numbers)
> /dev/sdb
1
Target verified as removable

We will now format your USB /dev/sdb device with partition UUID's:
3216-C143
MAKE SURE YOU ARE CERTAIN!!
Would you like to continue? [y/n]
y

GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: not present


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by typing 'q' if
you don't want to convert your MBR partitions to GPT format!
***************************************************************


Command (? for help): This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): 
Command (? for help): Partition number (1-128, default 1): First sector (34-15240542, default = 2048) or {+-}size{KMGTP}: Last sector (2048-15240542, default = 15240542) or {+-}size{KMGTP}: Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'EFI System'

Command (? for help): Partition number (2-128, default 2): First sector (34-15240542, default = 206848) or {+-}size{KMGTP}: Last sector (206848-15240542, default = 15240542) or {+-}size{KMGTP}: Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'Linux filesystem'

Command (? for help): 
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): OK; writing new GUID partition table (GPT) to /dev/sdb.
The operation has completed successfully.
mkfs.fat 3.0.22 (2013-07-19)

Please select a partition type for Porteus
[1] FAT32
[2] ext2
[3] ext3
[4] ext4

1mkfs.fat 3.0.22 (2013-07-19)
mkdosfs: /dev/sdb2 contains a mounted filesystem.

We will now download the required files (20Mb)from the internet.
Make sure you have an internet connection before continuing.
Press enter to continue

--2013-10-06 23:35:22--  https://dl.dropbox.com/s/1bsl2nqtfv1i01x/porteus-uefi-usb-template.tar.xz
Resolving dl.dropbox.com (dl.dropbox.com)... 107.21.212.198
Connecting to dl.dropbox.com (dl.dropbox.com)|107.21.212.198|:443... connected.
WARNING: cannot verify dl.dropbox.com's certificate, issued by ‘/C=US/O=Thawte, Inc./CN=Thawte SSL CA’:
  Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 302 FOUND
Location: https://dl.dropboxusercontent.com/s/1bsl2nqtfv1i01x/porteus-uefi-usb-template.tar.xz [following]
--2013-10-06 23:35:23--  https://dl.dropboxusercontent.com/s/1bsl2nqtfv1i01x/porteus-uefi-usb-template.tar.xz
Resolving dl.dropboxusercontent.com (dl.dropboxusercontent.com)... 23.21.100.40
Connecting to dl.dropboxusercontent.com (dl.dropboxusercontent.com)|23.21.100.40|:443... connected.
WARNING: cannot verify dl.dropboxusercontent.com's certificate, issued by ‘/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance CA-3’:
  Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 200 OK
Length: 3893752 (3.7M) [application/octet-stream]
Saving to: ‘/home/guest/Downloads/efimods/porteus-uefi-usb-template.tar.xz’

100%[======================================>] 3,893,752    272KB/s   in 21s    

2013-10-06 23:35:46 (184 KB/s) - ‘/home/guest/Downloads/efimods/porteus-uefi-usb-template.tar.xz’ saved [3893752/3893752]

--2013-10-06 23:35:46--  https://dl.dropbox.com/s/9nrwswxk1av5gaz/000-uefi-kernel.xzm
Resolving dl.dropbox.com (dl.dropbox.com)... 107.21.212.198
Connecting to dl.dropbox.com (dl.dropbox.com)|107.21.212.198|:443... connected.
WARNING: cannot verify dl.dropbox.com's certificate, issued by ‘/C=US/O=Thawte, Inc./CN=Thawte SSL CA’:
  Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 302 FOUND
Location: https://dl.dropboxusercontent.com/s/9nrwswxk1av5gaz/000-uefi-kernel.xzm [following]
--2013-10-06 23:35:46--  https://dl.dropboxusercontent.com/s/9nrwswxk1av5gaz/000-uefi-kernel.xzm
Resolving dl.dropboxusercontent.com (dl.dropboxusercontent.com)... 23.21.100.40
Connecting to dl.dropboxusercontent.com (dl.dropboxusercontent.com)|23.21.100.40|:443... connected.
WARNING: cannot verify dl.dropboxusercontent.com's certificate, issued by ‘/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance CA-3’:
  Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 200 OK
Length: 15777792 (15M) [application/octet-stream]
Saving to: ‘/home/guest/Downloads/efimods/000-uefi-kernel.xzm’

100%[======================================>] 15,777,792   121KB/s   in 1m 40s 

2013-10-06 23:37:28 (154 KB/s) - ‘/home/guest/Downloads/efimods/000-uefi-kernel.xzm’ saved [15777792/15777792]

Creating EPS file structure ...
EFI/
EFI/tools/
EFI/tools/drivers_x64/
EFI/tools/drivers_x64/reiserfs_x64.efi
EFI/tools/drivers_x64/iso9660_x64.efi
EFI/tools/drivers_x64/hfs_x64.efi
EFI/tools/drivers_x64/ext4_x64.efi
EFI/tools/drivers_x64/ext2_x64.efi
EFI/tools/drivers_x64/btrfs_x64.efi
EFI/tools/drivers_x64/LICENSE_GPL.txt
EFI/tools/drivers_x64/LICENSE.txt
EFI/tools/Shell.efi
EFI/porteus/
EFI/porteus/refind.conf
EFI/porteus/initrd.xz
EFI/porteus/vmlinuz
EFI/BOOT/
EFI/BOOT/refind.conf
EFI/BOOT/icons/
EFI/BOOT/icons/tool_memtest.icns
EFI/BOOT/icons/arrow_right.icns
EFI/BOOT/icons/os_linux.icns
EFI/BOOT/icons/os_legacy.icns
EFI/BOOT/icons/tool_mok_tool.icns
EFI/BOOT/icons/os_win.icns
EFI/BOOT/icons/tool_shell.icns
EFI/BOOT/icons/arrow_left.icns
EFI/BOOT/icons/vol_external.icns
EFI/BOOT/icons/os_slackware.icns
EFI/BOOT/icons/func_exit.icns
EFI/BOOT/icons/func_firmware.icns
EFI/BOOT/icons/boot_win.icns
EFI/BOOT/icons/transparent.icns
EFI/BOOT/icons/boot_linux.icns
EFI/BOOT/icons/func_about.icns
EFI/BOOT/icons/tool_apple_rescue.icns
EFI/BOOT/icons/vol_internal.icns
EFI/BOOT/icons/tool_part.icns
EFI/BOOT/icons/func_shutdown.icns
EFI/BOOT/icons/func_reset.icns
EFI/BOOT/icons/vol_optical.icns
EFI/BOOT/icons/os_unknown.icns
EFI/BOOT/icons/os_refind.icns
EFI/BOOT/bootx64.efi
EFI/BOOT/myicons/
EFI/BOOT/myicons/porteus-text.png
EFI/BOOT/myicons/porteus-saved.png
EFI/BOOT/myicons/porteus-ram.png
EFI/BOOT/myicons/porteus-fresh.png
EFI/BOOT/myicons/porteus-bootloader.bmp
EFI/BOOT/myicons/func_shutdown.icns
EFI/BOOT/myicons/func_reset.icns
EFI/BOOT/myicons/func_exit.icns
EFI/BOOT/myicons/func_about.icns
/home/guest

Copying porteus files ...
Finishing installation ....
Your installation has finished!!
Make sure you set your system to boot
into UEFI mode and reboot now!
root@porteus:/home/guest# blkid
/dev/sda1: LABEL="PQSERVICE" UUID="9894832D94830CC6" TYPE="ntfs" 
/dev/sda2: LABEL="SYSTEM RESERVED" UUID="ECF483DEF483AA02" TYPE="ntfs" 
/dev/sda3: LABEL="Acer" UUID="48168114168103E2" TYPE="ntfs" 
/dev/sda5: LABEL="Data" UUID="01CD20066B8BF780" TYPE="ntfs" 
/dev/sda6: LABEL="BKUPS" UUID="14E65B5EE65B3F64" TYPE="ntfs" 
/dev/loop0: LABEL="Porteus" TYPE="iso9660" 
/dev/loop1: TYPE="squashfs" 
/dev/loop2: TYPE="squashfs" 
/dev/loop3: TYPE="squashfs" 
/dev/loop4: TYPE="squashfs" 
/dev/loop5: TYPE="squashfs" 
/dev/sdb1: LABEL="PORTEUSEFI" UUID="3B09-3C64" TYPE="vfat" SEC_TYPE="msdos" 
/dev/sdb2: UUID="93E0-28CB" TYPE="vfat" 
root@porteus:/home/guest#
Top
User avatar
Ed_P
Contributor
Contributor
Posts: 8578
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Re: UEFI problem

Post#68 by Ed_P » 07 Oct 2013, 05:54

The rebuilt flash drive boots on the UEFI machine but still no Internet connections. This the machine's WiFi NIC.

Code: Select all

WIRELESS INFO: 
 
02:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless 
LAN Controller (rev 01) 
	Subsystem: Foxconn International, Inc. Device e042 
	Flags: bus master, fast devsel, latency 0 
	Memory at 90100000 (64-bit, non-prefetchable) [size=16K] 
	Capabilities: [40] Power Management version 3 
	Capabilities: [58] Vendor Specific Information: Len=78 <?> 
	Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+ 
	Capabilities: [d0] Express Endpoint, MSI 00 
	Capabilities: [100] Advanced Error Reporting 
	Capabilities: [13c] Virtual Channel 
	Capabilities: [160] Device Serial Number 00-00-8e-ff-ff-4d-08-3e 
	Capabilities: [16c] Power Budgeting <?>
Top
User avatar
brokenman
Site Admin
Site Admin
Posts: 6105
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil

Re: UEFI problem

Post#69 by brokenman » 07 Oct 2013, 13:27

This wifi card is supported by the inbuilt brcm80211 so it should work. Please show which driver is being loaded. As root please run in a console. .

lspci -k|grep -A2 Network

It would be better to simply upload a dump of xpsinfo. The Porteus System Information Tool has a function to upload a full dump of your machine info.
How do i become super user?
Wear your underpants on the outside and put on a cape.
Top
User avatar
Ed_P
Contributor
Contributor
Posts: 8578
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Re: UEFI problem

Post#70 by Ed_P » 07 Oct 2013, 14:42

brokenman wrote:It would be better to simply upload a dump of xpsinfo. The Porteus System Information Tool has a function to upload a full dump of your machine info.
There seems to be a bug with the upload function, it requires a functioning Internet connection. 8)

So where would you like me to email the report?
Top
User avatar
brokenman
Site Admin
Site Admin
Posts: 6105
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil

Re: UEFI problem

Post#71 by brokenman » 07 Oct 2013, 16:55

Go to pastebin.com and upload the file then post the address here. In the meantime the output from the lspci command would help.
How do i become super user?
Wear your underpants on the outside and put on a cape.
Top
User avatar
Ed_P
Contributor
Contributor
Posts: 8578
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Re: UEFI problem

Post#72 by Ed_P » 07 Oct 2013, 19:01

brokenman wrote:Go to pastebin.com and upload the file then post the address here. In the meantime the output from the lspci command would help.
Since you said it would be better to do a dump of xpsinfo I didn't do the lspci command. I've never used pastebin before, hopefully this link is what you want.

http://pastebin.com/VqGKSZmt
Top
User avatar
brokenman
Site Admin
Site Admin
Posts: 6105
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil

Re: UEFI problem

Post#73 by brokenman » 08 Oct 2013, 12:17

This broadcom driver is a pain in posterior. Your kernel driver for wireless is not being loaded. You will need to blacklist some drivers. First please check if the following command loads the correct driver and your wireless works.

modprobe brcm80211
ifconfig wlan0 up

Please give any errors this spits out, and if none check if wifi works.
How do i become super user?
Wear your underpants on the outside and put on a cape.
Top
User avatar
Ed_P
Contributor
Contributor
Posts: 8578
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Re: UEFI problem

Post#74 by Ed_P » 08 Oct 2013, 18:58

The default signon should be root. NOTHING works as guest.

Code: Select all

guest@porteus:~$ modprobe brcm80211
bash: modprobe: command not found
guest@porteus:~$ su
Password: 
root@porteus:/home/guest# modprobe brcm80211
modprobe: FATAL: Module brcm80211 not found.
root@porteus:/home/guest#
Now when booting there is a 30-45 sec freeze of the screen when Porteus is Activating udev ..... I don't know if that is significant or not but I don't recall seeing it other times.

I understand the problem of having multiple drivers from the same company when the company uses the same name for different versions of its drivers. I encounter it when building Windows PEs.
Top
User avatar
brokenman
Site Admin
Site Admin
Posts: 6105
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil

Re: UEFI problem

Post#75 by brokenman » 09 Oct 2013, 01:19

The default signon should be root. NOTHING works as guest.
Correction. Nothing that can screw your machine up permanently works. I work as guest and use a root console when I need to.

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.

modprobe wl loads kernel wireless drivers.
ifconfig wlan0 turns on your wireless card
iwlist wlan0 scan scans the local area to prove that wireless card is working ok.
How do i become super user?
Wear your underpants on the outside and put on a cape.
Top
Post Reply

Return to “Newbie questions”