[Solved]modprobe settings not saved in changes.xzm

Post here if you are a new Porteus member and you're looking for some help.
Post Reply
linuxnoob
Black ninja
Black ninja
Posts: 40
Joined: 10 Oct 2013, 14:45
Distribution: porteus 2.1
Location: australia

[Solved]modprobe settings not saved in changes.xzm

Post#1 by linuxnoob » 27 Oct 2013, 01:40

i've been creating my own changes.xzm, by periodically converting the changes folder to a porteus module for backup purposes, kind of like the system restore point in windows.

the only thing i noticed that doesnt get saved is my modprobe settings, and network manager in xfce doesnt connect until i add these lines:

Code: Select all

modprobe -r rtl8192cu
modprobe rtl8192cu swenc=1
do i need a separate script to do this?

if i extract the module and use it as a normal changes folder everything works fine and network manager in xfce connects automatically

i have 2 installs one on hdd that uses normal changes folder and one on usb without changes but has the changes.xzm bulit from the changes folder on hdd
Last edited by linuxnoob on 29 Oct 2013, 00:38, edited 1 time in total.

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

Re: modprobe settings not saved in changes.xzm

Post#2 by fanthom » 27 Oct 2013, 07:14

not sure why it does not get saved but here is the workaround:
add 'rtl8192cu.swenc=1' cheatcode to the porteus.cfg
this will tell udev to load rtl8192cu module with 'swenc' parameter enabled.

you could also store that information in /etc/modprobe.d/rtl8192cu.conf but porteus.cfg is better as you can easily remove this cheat with TAB button when booting on other PCs (and in troubles because of it).
Please add [Solved] to your thread title if the solution was found.

linuxnoob
Black ninja
Black ninja
Posts: 40
Joined: 10 Oct 2013, 14:45
Distribution: porteus 2.1
Location: australia

Re: modprobe settings not saved in changes.xzm

Post#3 by linuxnoob » 28 Oct 2013, 06:50

thanks for your help fanthom, but unfortunately even those modprobe commands arent working now, i've tried deleting the connection, unplug and replug the usb, unload and reload driver, and it still doesnt work even though iwconfig shows an interface and iwlist iwlan1 scan shows the router.

Strangely though, if i uncompress the changes.xzm module and use it as an ordinary changes folder then it works straight away.

Does the module need to be in a specific order? it was at the top of modules folder so i renamed it to be at the end, but it made no difference.

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

Re: modprobe settings not saved in changes.xzm

Post#4 by brokenman » 28 Oct 2013, 10:39

The first thing you should do is boot without your changes module and then see if your technique to get the wifi working still functions. If it does then start looking at the changes module for what is upsetting it. If it worked before and doesn't now then it could be changes, although this driver is reported to be shaky at best.
How do i become super user?
Wear your underpants on the outside and put on a cape.

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

Re: modprobe settings not saved in changes.xzm

Post#5 by fanthom » 28 Oct 2013, 10:41

not sure what you have done and i wont be able to tell you what's wrong without having access to the PC. i would start from the beginning and add components (modules, changes, /rootcopy files) one by one till you find what's causing the troubles.
Please add [Solved] to your thread title if the solution was found.

linuxnoob
Black ninja
Black ninja
Posts: 40
Joined: 10 Oct 2013, 14:45
Distribution: porteus 2.1
Location: australia

Re: modprobe settings not saved in changes.xzm

Post#6 by linuxnoob » 28 Oct 2013, 15:55

ok so after a long day of testing, i finally found what was wrong and possibly a bug.

two porteus installs, hdd and usb. hdd is first device so /porteus defaults to /mnt/sda2/porteus on both.

sgnfile=porteus-usb cheatcode solves that so usb points to /mnt/sdf1/porteus.

but changes still both point to /mnt/sda2/porteus/changes, shouldnt sgnfile= change the default /porteus folder?

so finally i fixed it by setting the changes= /dev/sdf1/porteus/changes cheatcode for the usb.

changes module now works correctly.

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

Re: modprobe settings not saved in changes.xzm

Post#7 by fanthom » 28 Oct 2013, 16:00

shouldnt sgnfile= change the default /porteus folder?
nope. sometimes users may want to boot from 2 different installs but use the same changes.

btw: glad that you sorted it. please add [SOLVED] to the thread title.
Please add [Solved] to your thread title if the solution was found.

linuxnoob
Black ninja
Black ninja
Posts: 40
Joined: 10 Oct 2013, 14:45
Distribution: porteus 2.1
Location: australia

Re: modprobe settings not saved in changes.xzm

Post#8 by linuxnoob » 28 Oct 2013, 23:17

what i mean is, the changes=/porteus cheatcode should default to the booting drive instead of the first drive, that way if you have say 10 installs on 10 different devices you dont need to modify all 10 porteus.cfg files which would be error prone, and if you really want something more complex like booting from one device, loading modules from another, and saving changes to yet another then a more specific changes= path and sgnfile= path can be used.

just my 2 cents, would be more intuitive and easier for people to have a hdd install and a rescue disk type install on a usb and prevent funny things happening if i take my usb to someones elses computer who just happens to have porteus installed on his first hdd.

Post Reply