Why is porteus trying to install to my boot drive?
-
- White ninja
- Posts: 5
- Joined: 30 Jun 2022, 03:05
- Distribution: Xubuntu
Why is porteus trying to install to my boot drive?
Hey everyone, I was following the instructions to install Porteus to an external drive with persistence. I copied the boot, efi, and porteus folders to my external drive (located at /dev/sdc) and then ran the linux shell script to install it. However, it then tried to install to dev/sda3 - the partition I'm using right now!! How can I force porteus to use a specific partition? My external drive /dev/sdc is already formatted as FAT, according to gnome-disks.
Why is porteus trying to install to my boot drive?
I've seen this before - make sure you are running the shell script from the target partition - that is make sure in your case you are running it from the files you copied to /dev/sdc, and not from the source files you initially got from /dev/sda3.
I've been in a hurry and blew that before too.
Also note that depending on how modern your machine is, you may *not* have to even run the installation shell script at all. Merely copying the files is enough. Just boot, and if it fails, then go ahead and run the installation shell script - but booting after simply copying without having to run the shell script (or exe) is usually reserved for very modern machines. Worth a try.
I've been in a hurry and blew that before too.

Also note that depending on how modern your machine is, you may *not* have to even run the installation shell script at all. Merely copying the files is enough. Just boot, and if it fails, then go ahead and run the installation shell script - but booting after simply copying without having to run the shell script (or exe) is usually reserved for very modern machines. Worth a try.
That's a UNIX book - cool. -Garth
-
- White ninja
- Posts: 5
- Joined: 30 Jun 2022, 03:05
- Distribution: Xubuntu
Why is porteus trying to install to my boot drive?
@nanZor Yes sir! I made sure I was running the install script from /dev/sdc - in fact, I did it 5 times (my goodness!). Is there anything I can do to force Porteus to use a certain drive?
- Ed_P
- Contributor
- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Why is porteus trying to install to my boot drive?
Are these the instructions you are following?
USB_INSTALLATION.txt wrote:b) navigate to the /boot folder and launch the installer
'bash Porteus-installer-for-Linux.com'
Why is porteus trying to install to my boot drive?
hi,carlyraejepsenftw if you have used a system to put the porteus directories into the removable device,if that system is windows you have to mount the device cd into the boot directory of porteus and run the windows installer not linux.the linux installer is only for the linux host, if you do not change the directory to run the script the installer look always to the system root that is the /dev/sda3.
-
- White ninja
- Posts: 5
- Joined: 30 Jun 2022, 03:05
- Distribution: Xubuntu
Why is porteus trying to install to my boot drive?
Hey friends, thanks for the help - if I cd into my external drive and then run 'bash Porteus-installer-for-Linux.com' instead of 'bash '/home/me/media/sdc/Porteus-installer-for-Linux.com'', I get a different error - that extracting the Porteus installer failed. However, if I just boot to the USB it works! Now I have a different problem - no wifi networks are listed in the wifi menu from the top bar, and there's just an error saying "no network devices detected." I'm using the LXDE 5.0 release of Porteus, on a macbook pro mid-2015 15-inch. Any ideas what's going on?
Why is porteus trying to install to my boot drive?
hi we have to know the wifi device name, try lspci -vnn in console
-
- White ninja
- Posts: 5
- Joined: 30 Jun 2022, 03:05
- Distribution: Xubuntu
Why is porteus trying to install to my boot drive?
Hopefully it doesn't matter whether or not I execute the command from porteus....? I'm traveling atm and I forgot my porteus drive at home
but here's the full lspci output from my Xubuntu install (with working wifi):
https://www.toptal.com/developers/haste ... zipiv.yaml

https://www.toptal.com/developers/haste ... zipiv.yaml
Why is porteus trying to install to my boot drive?
here you have the answer: Kernel driver in use: brcmfmac Kernel modules: brcmfmac you have to load with modprobe or insmod the directory is
/lib/modules/kernel/drivers/net/wireless/broadcom/brcm80211/ try it and if you have network manager you have the link ready.
/lib/modules/kernel/drivers/net/wireless/broadcom/brcm80211/ try it and if you have network manager you have the link ready.
-
- White ninja
- Posts: 5
- Joined: 30 Jun 2022, 03:05
- Distribution: Xubuntu
Why is porteus trying to install to my boot drive?
Thank you kind sir! However, how do I know which file will have the right kernel module? On xubuntu, inside of `/lib/modules/5.13.0-52-generic/kernel/drivers/net/wireless/broadcom/brcm80211/` there are 3 dirs: brcmutil, brcsmac, and brcmfmac. Should I just load all the `.ko` files inside of each folder?
Edit, nevermind, I didn't see you specify brcsmac in your post
Edit, nevermind, I didn't see you specify brcsmac in your post

Why is porteus trying to install to my boot drive?
Code: Select all
root@porteus:~# modinfo /lib/modules/5.18.3-porteus/kernel/drivers/net/wireless/broadcom/brcm80211/brcmfmac/brcmfmac.ko
filename: /lib/modules/5.18.3-porteus/kernel/drivers/net/wireless/broadcom/brcm80211/brcmfmac/brcmfmac.ko
license: Dual BSD/GPL
description: Broadcom 802.11 wireless LAN fullmac driver.
author: Broadcom Corporation
firmware: brcm/brcmfmac*-sdio.*.bin
firmware: brcm/brcmfmac*-sdio.*.txt
firmware: brcm/brcmfmac43752-sdio.clm_blob
firmware: brcm/brcmfmac43752-sdio.bin
firmware: brcm/brcmfmac43012-sdio.clm_blob
firmware: brcm/brcmfmac43012-sdio.bin
firmware: brcm/brcmfmac4373-sdio.clm_blob
firmware: brcm/brcmfmac4373-sdio.bin
firmware: brcm/brcmfmac4359-sdio.bin
firmware: brcm/brcmfmac4356-sdio.clm_blob
firmware: brcm/brcmfmac4356-sdio.bin
firmware: brcm/brcmfmac4354-sdio.clm_blob
firmware: brcm/brcmfmac4354-sdio.bin
firmware: brcm/brcmfmac43456-sdio.bin
firmware: brcm/brcmfmac43455-sdio.clm_blob
firmware: brcm/brcmfmac43455-sdio.bin
firmware: brcm/brcmfmac43430b0-sdio.bin
firmware: brcm/brcmfmac43430-sdio.clm_blob
firmware: brcm/brcmfmac43430-sdio.bin
firmware: brcm/brcmfmac43430a0-sdio.bin
firmware: brcm/brcmfmac4339-sdio.bin
firmware: brcm/brcmfmac43362-sdio.bin
firmware: brcm/brcmfmac4335-sdio.bin
firmware: brcm/brcmfmac43340-sdio.bin
firmware: brcm/brcmfmac4334-sdio.bin
firmware: brcm/brcmfmac4330-sdio.bin
firmware: brcm/brcmfmac4329-sdio.bin
firmware: brcm/brcmfmac43241b5-sdio.bin
firmware: brcm/brcmfmac43241b4-sdio.bin
firmware: brcm/brcmfmac43241b0-sdio.bin
firmware: brcm/brcmfmac43143-sdio.bin
firmware: brcm/brcmfmac4373.bin
firmware: brcm/brcmfmac43569.bin
firmware: brcm/brcmfmac43242a.bin
firmware: brcm/brcmfmac43236b.bin
firmware: brcm/brcmfmac43143.bin
firmware: brcm/brcmfmac*-pcie.*.bin
firmware: brcm/brcmfmac*-pcie.*.txt
firmware: brcm/brcmfmac*-pcie.txt
firmware: brcm/brcmfmac4371-pcie.bin
firmware: brcm/brcmfmac4366c-pcie.bin
firmware: brcm/brcmfmac4366b-pcie.bin
firmware: brcm/brcmfmac4365c-pcie.bin
firmware: brcm/brcmfmac4365b-pcie.bin
firmware: brcm/brcmfmac4364-pcie.bin
firmware: brcm/brcmfmac4359-pcie.bin
firmware: brcm/brcmfmac4358-pcie.bin
firmware: brcm/brcmfmac43570-pcie.clm_blob
firmware: brcm/brcmfmac43570-pcie.bin
firmware: brcm/brcmfmac4356-pcie.clm_blob
firmware: brcm/brcmfmac4356-pcie.bin
firmware: brcm/brcmfmac4350c2-pcie.bin
firmware: brcm/brcmfmac4350-pcie.bin
firmware: brcm/brcmfmac43602-pcie.bin
alias: usb:v04B4p0BDCd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0A5Cp0BDCd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v043Ep3101d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v04B4pBD29d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v13B1p0039d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0A5CpBD27d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0A5CpBD1Fd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0A5CpBD17d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0A5CpBD1Ed*dc*dsc*dp*ic*isc*ip*in*
alias: pci:v000014E4d0000440Dsv*sd*bc02sc80i*
alias: pci:v000014E4d000043C5sv*sd*bc02sc80i*
alias: pci:v000014E4d000043C4sv*sd*bc02sc80i*
alias: pci:v000014E4d000043C3sv*sd*bc02sc80i*
alias: pci:v000014E4d00004365sv000014E4sd00004365bc02sc80i*
alias: pci:v000014E4d000043CCsv*sd*bc02sc80i*
alias: pci:v000014E4d000043CBsv*sd*bc02sc80i*
alias: pci:v000014E4d000043CAsv*sd*bc02sc80i*
alias: pci:v000014E4d00004464sv*sd*bc02sc80i*
alias: pci:v000014E4d0000AA52sv*sd*bc02sc80i*
alias: pci:v000014E4d000043BCsv*sd*bc02sc80i*
alias: pci:v000014E4d000043BBsv*sd*bc02sc80i*
alias: pci:v000014E4d000043BAsv*sd*bc02sc80i*
alias: pci:v000014E4d000043EFsv*sd*bc02sc80i*
alias: pci:v000014E4d000043E9sv*sd*bc02sc80i*
alias: pci:v000014E4d0000AA31sv*sd*bc02sc80i*
alias: pci:v000014E4d000043D9sv*sd*bc02sc80i*
alias: pci:v000014E4d000043D3sv*sd*bc02sc80i*
alias: pci:v000014E4d000043ECsv*sd*bc02sc80i*
alias: pci:v000014E4d00004354sv*sd*bc02sc80i*
alias: pci:v000014E4d00004355sv000014E4sd00004355bc02sc80i*
alias: pci:v000014E4d000043A3sv*sd*bc02sc80i*
alias: sdio:c*v02D0d4355*
alias: sdio:c*v02D0dAAE8*
alias: sdio:c*v02D0dA804*
alias: sdio:c*v02D0d4373*
alias: sdio:c*v02D0d4359*
alias: sdio:c*v02D0d4356*
alias: sdio:c*v02D0d4354*
alias: sdio:c*v02D0dA9BF*
alias: sdio:c*v02D0d4345*
alias: sdio:c*v02D0dA9A6*
alias: sdio:c*v02D0d4339*
alias: sdio:c*v02D0d4335*
alias: sdio:c*v02D0dA9A4*
alias: sdio:c*v02D0dA962*
alias: sdio:c*v02D0dA94D*
alias: sdio:c*v02D0dA94C*
alias: sdio:c*v02D0d4334*
alias: sdio:c*v02D0d4330*
alias: sdio:c*v02D0d4329*
alias: sdio:c*v02D0d4324*
alias: sdio:c*v02D0dA887*
depends: brcmutil,cfg80211
retpoline: Y
intree: Y
name: brcmfmac
vermagic: 5.18.3-porteus SMP preempt mod_unload
sig_id: PKCS#7
signer: Build time autogenerated kernel key
sig_key: 63:7E:96:3F:6B:0A:1C:4B:7A:23:FC:85:12:A1:42:36:AB:2B:75:90
sig_hashalgo: sha1
signature: 5B:C8:37:28:62:EF:6D:CB:B4:77:B9:03:87:27:8E:7A:34:2D:E7:44:
06:8C:13:44:04:94:6D:71:C1:0E:46:2C:E8:3A:FA:FB:27:0E:DE:2D:
D0:04:BD:20:61:0B:19:72:AA:E0:2D:A0:FE:AB:44:C8:A8:0F:1D:22:
F0:91:C9:F9:6E:48:DF:34:21:6A:72:9F:C1:D1:8B:11:B3:EA:63:40:
98:29:CA:B8:50:CD:E3:B2:7D:A2:E1:26:D0:36:A2:DE:7D:E8:86:EA:
45:D2:77:4E:52:EF:24:30:77:AD:EA:C8:D4:26:A2:73:6F:38:3C:AF:
24:C3:9B:10:B7:50:40:ED:FD:F8:4F:68:8C:D4:FA:98:AD:79:59:E5:
6F:FF:9F:44:9B:52:FE:B2:51:C4:A9:AB:04:52:83:DC:2F:60:45:55:
CB:71:4D:63:05:6D:B6:F9:03:C5:46:C0:21:2F:8D:3A:0C:87:33:01:
F3:69:30:9B:A5:B6:96:88:A6:72:A4:BC:4F:BD:20:F0:F8:57:29:02:
C9:E0:9A:2D:24:6B:8C:E0:19:F2:CA:0D:25:19:D0:00:17:FC:EF:D7:
EC:59:AC:17:9B:2D:D4:5F:8F:3E:58:F8:1E:6B:4F:DE:C2:BD:C5:E8:
F1:C1:65:54:43:43:BC:21:72:C6:54:0F:1D:B4:EA:F1:FB:0C:38:98:
33:78:34:8E:14:01:DB:EA:D9:3B:73:7C:A2:D4:5B:E7:5D:D7:58:FE:
DD:A8:CE:79:F2:BC:4D:FA:D3:52:B3:BE:1F:4B:03:8D:F4:29:FC:33:
10:98:DE:A9:98:82:AB:1D:00:A1:61:3F:6D:13:46:64:CE:3C:01:A9:
AD:EA:97:EE:E6:EB:4E:33:7D:B4:3F:76:FC:E1:03:F2:48:D9:32:41:
2A:16:BF:9B:2C:01:C9:87:6B:15:35:E5:9C:6D:06:F3:F2:6A:74:EF:
85:0B:08:BE:07:3C:2F:C6:F3:05:2D:8F:3C:54:77:86:F6:5E:65:89:
E3:19:BA:02:17:55:0A:FF:46:5E:52:6F:8C:15:BB:83:7D:44:0B:EF:
F6:67:D0:0F:E7:C7:5C:B8:52:08:B2:D2:9E:89:64:A0:D0:7C:3A:F1:
5F:C1:67:30:99:63:15:B1:54:B2:F3:E4:13:82:99:92:F4:26:0C:BD:
AB:97:DD:70:7A:0E:A2:EE:EF:DE:C8:54:C4:E2:28:B1:07:91:36:73:
D9:45:98:FD:FE:6C:57:9E:DC:0F:E1:9E:B6:52:81:82:8E:5E:8E:94:
E2:1B:47:E8:34:6F:EC:29:63:44:B8:D1:70:3A:B0:0E:D3:F1:A6:A5:
DA:43:33:E7:40:85:90:79:E3:95:4C:41
parm: txglomsz:Maximum tx packet chain size [SDIO] (int)
parm: debug:Level of debug output (int)
parm: p2pon:Enable legacy p2p management functionality (int)
parm: feature_disable:Disable features (int)
parm: alternative_fw_path:Alternative firmware path (string)
parm: fcmode:Mode of firmware signalled flow control (int)
parm: roamoff:Do not use internal roaming engine (int)
parm: iapp:Enable partial support for the obsoleted Inter-Access Point Protocol (int)
root@porteus:~#