Porteus

meet wrote: ↑

01 Apr 2020, 08:07

.... very unsecure if it gets in to wrong hands.

..like anything else in the world.

However, you can change the default passwords and edit /etc/slim.conf
so that the system stops at a login screen and asks for a username and password.

....And just replace xorg.xzm. No,you need to downgrade xorg properly. I replaced the xorg.xzm to test if the driver would compile then. I didn't care if something else breaks.(I'm pretty sure it will) I also can not say for sure up to which kernel version it will work without further patches. It w...

@Rava xorg 1.20 is the show stopper, the kernel not so much. I once made a test using port-5, replaced the xorg.xzm to see if the 304 driver would compile/work, it worked. But because i do not know how to properly downgrade xorg (if even possible) i gave up on that. I am not aware of any existing pa...

Ed These outputs are confusing.. Example: Why do you load 000-kernel.xzm (and others) from /porteus40/Modules when booting 3.2.2..? browser issue: Have you tried a version that is meant to work with the Porteus version you are actually booting? e.g. Pale Moon or at "dl.porteus.org" so 3.0.1 work, wh...

Small problem here, if ipw2200 is not loaded the first command fails and hence the second command of actual modprobe wont work.... That's right, but based on the previous posts, you can almost certainly say that ipw2200 was always loaded. ;) If you were certain, then just the second command would'v...

Ed what i would do: take a spare usb thumbdrive > make a normal install (msdos partition table, ext2 filesystem, stock porteus-4) no grub/iso booting trickery. You do not need the EFI folder if you want the Thumbdrive to start a 32-bit non-UEFI machine. only boot and porteus are needed. Use the from...

The 304 driver is out of support. AFAIK it is not possible getting it to run on a system since xorg-server 1.20 Porteus 4 with xorg 1.19 will be the last one. -------------------------------------------------------------------------------------------------------- nvidia-304.137-kernel 4.16.3-x86_64 ...

jssouza wrote: ↑

28 Mar 2020, 16:53

Small problem here, if ipw2200 is not loaded the first command fails and hence the second command of actual modprobe wont work....

That's right, but based on the previous posts, you can almost certainly say
that ipw2200 was always loaded.

Ed, use root@porteus:/home/guest# modprobe -r ipw2200 && modprobe ipw2200 (without any path) while 3.2.2 is running. This should un-/reload the driver.It may or may not help. [There will be no output > when done check the wifi.] I see 4.19.113 in the port-4 output, where does this come from? Please ...

So where does one get modprobe?

You have already used this command. -- see page 1.

However,
as root

donald I am not aware of any non protected wireless networks around here. I thought you could do this test with your own wifi AP Only for a test of course - I have read that some driver/firmware combinations can not handle WPA but can connect to an open (unsecured) wifi. With the old version of Por...

Ed, does it connect to a non protected wireless network?

hmmm...Isn't it possible to install port onto a usb thumbdrive
and boot the "old" dell with that one?

Ed
Some options for experimenting:
another browser - pale moon?

If it has to be Firefox, then:
Take port 4 > try the firmware of port 3 if they are different.
If this doesn't help, change the kernel as well.
or try installing the CRDA thing.