- This topic has 140 replies, 21 voices, and was last updated Nov 6-1:52 am by bci.
-
Posts
-
Xecure
So I think it might be the 32-bit B2 system on this particular hp pavilion ze4900.
Network: Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter vendor: Hewlett-Packard driver: 8139too v: 0.9.28 port: 3000 bus ID: 02:00.0 IF: eth0 state: down mac: <filter> Device-2: Broadcom Limited BCM4306 802.11b/g Wireless LAN vendor: Hewlett-Packard driver: b43-pci-bridge v: N/A port: 3000 bus ID: 02:06.0 IF-ID-1: wlan1 state: up mac: <filter>Can you share the output of
inxi -nxxxz
on antiX 21, to compare how it is detected? I suspect you need to unblock the b43-pci-bridge using the Network Assistant for it to work.- This reply was modified 1 year, 7 months ago by Xecure. Reason: More info
antiX Live system enthusiast.
General Live Boot Parameters for antiX.calciumsodium
Can you share the output of
inxi -nxxxz
on antiX 21, to compare how it is detected? I suspect you need to unblock the b43-pci-bridge using the Network Assistant for it to work.Hi @Xecure,
demo@antix1:~ $ inxi -nxxxz Network: Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter vendor: Hewlett-Packard driver: 8139too v: 0.9.28 port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:8139 class-ID: 0200 IF: eth0 state: down mac: <filter> Device-2: Broadcom BCM4306 802.11b/g Wireless LAN vendor: Hewlett-Packard driver: b43-pci-bridge v: N/A port: 3000 bus-ID: 02:06.0 chip-ID: 14e4:4320 class-ID: 0280 IF-ID-1: wlan0 state: down mac: <filter> demo@antix1:~ $Xecure
`driver: b43-pci-bridge v: N/A port: 3000 bus-ID: 02:06.0
chip-ID: 14e4:4320 class-ID: 0280`I have been checking a few posts and it seems that newer b43 firmware have compatibility issues with the device 14e4:4320
First, we will need to figure out if it is the revision 2 or revision 3 wifi chip. Please share
lspci -nn | grep -i "Broadcom"
If it is (rev 2), the firmware comes from the package firmware-b43legacy-installer. If it is (rev 3), the firmware comes from the package firmware-b43-installer.Unfortunately, the firmware doesn’t really come from that package, but that package downloads the firmware from https://downloads.openwrt.org/sources/ or https://www.lwfinger.com/b43-firmware/, so if the files are changed in the source link, they will install newer firmware files.
It still shouldn’t hurt trying to reinstall the package related to the chip and see if this fixes it.
For rev 2, for example, you can reinstall the firmware with:
sudo apt update && sudo apt install --reinstall firmware-b43legacy-installer
Then you unload the b43-pci-bridge module and load it again (you can use the network assistant app to do it in GUI).
You may need to rfkill unlock all, or use antix-wifi-switch to reactivate connman, but that should restart the network connection and reload the firmware.antiX Live system enthusiast.
General Live Boot Parameters for antiX.Hi @Xecure,
It looks like the antiX 19 where the wifi works and the antiX 21 32-bit B2 where the wifi does not work on this hp pavilion ze4900 may use the same rev 03. Please see output below:
antiX 19 jakersfan@jakersfan:~ $ lspci -nn | grep -i "Broadcom" 02:06.0 Network controller [0280]: Broadcom Limited BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03) jakersfan@jakersfan:~ $ antiX 21 demo@antix1:~ $ lspci -nn | grep -i "Broadcom" 02:06.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03) demo@antix1:~ $Edit: AntiX 19 uses Broadcome Limited. AntiX 21 uses Broadcom Inc. Is this an important distinction?
- This reply was modified 1 year, 7 months ago by calciumsodium.
Xecure
ze4900 may use the same rev 03
I will see what was the version if the firmwares used in previous antiX 19.4 and see if they are different to the ones in 21.
If you don’t mind, could you test on a live antiX 19.4 (with persistence) and compare the wifi performance at stock, and after reinstalling and rebooting. Steps are:
0. Test wifi speeds on stock antiX 19.4 i386 (no matter if base or full).
1. Reinstall the firmware-b43-installer package
sudo apt update && sudo apt install --reinstall firmware-b43-installer
2. Save persistence changes and reboot
3. Test wifi speed after update.If the result is the same as in stock (good wifi speeds), I will check to see if the newer firmware-b43-installer package in bullseye gets the firmware files from a different source compared to buster.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Xecure
After checking the source code for firmware-b43-installer, if you reinstall it on antiX-21b2 live USB it should install the correct VERSION=”5.100.138″ firmware and then it should no longer be slow on your system.
As the build-iso environment doesn’t present any specific broadcom 43XX chip, it installs the latest version instead of the version for your hardware.Please try the instructions in my previous post (reinstall firmware-b43-installer, unload and reload the b43-pci-bridge module, restart connman, and check if the connection is no longer slow). This will be a good point to take into account for when another user experiences the same issue and we can redirect at reinstalling this package.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.After checking the source code for firmware-b43-installer, if you reinstall it on antiX-21b2 live USB it should install the correct VERSION=”5.100.138″ firmware and then it should no longer be slow on your system.
As the build-iso environment doesn’t present any specific broadcom 43XX chip, it installs the latest version instead of the version for your hardware.Please try the instructions in my previous post (reinstall firmware-b43-installer, unload and reload the b43-pci-bridge module, restart connman, and check if the connection is no longer slow). This will be a good point to take into account for when another user experiences the same issue and we can redirect at reinstalling this package.
Hi Xecure,
I reinstalled the firmware
sudo apt install –reinstall firmware-b43-installer
then I used antix-wifi-switch to reactivate connman
then I connected to the wifi network.
Network is still very slow.
I tried the centurylink speed test, but the network is just too slow. It did not even register on the centurylink speed test and caused an error. The highest download speed that I could see in conky was 16 Kb/s on this B2 32-bit live usb system.Then I shutdown down and booted up in the installed antiX 19.1 system. I tried the centurylink speed test and the computer downloaded at a comparatively blazingly fast 17 Mb/s.
I think I will stop on this particular post on this issue. I will just keep this ze4900 system on antiX19.1.
Thank you Xecure for your time.
- This reply was modified 1 year, 7 months ago by calciumsodium.
- This reply was modified 1 year, 7 months ago by calciumsodium. Reason: new testing information
Xecure
Sorry I wasn’t clear, calciumsodium. I meant for you to unload and reload the kernel module before connecting to the network, so that it would load the new firmware installed instead of keeping loaded the old one.
As a last test, could you uninstall firmware-b43-installer and install the original buster firmware-b43-installer version? I will give you the commands one at a time.sudo apt purge firmware-b43-installer wget http://ftp.us.debian.org/debian/pool/contrib/b/b43-fwcutter/firmware-b43-installer_019-4+deb10u1_all.deb sudo apt install ./firmware-b43-installer_019-4+deb10u1_all.deb sudo modprobe -r b43-pci-bridge && sleep 2 sudo modprobe b43-pci-bridge antix-wifi-switch --gui connmanOne by one, it first removes the bullseye package, then downloads the old buster package, then installs it, unloads the b43-pci-bridge module (waits 2 seconds), then reloads it again (to load the just installed firmware), and finally launches the antix-wifi-switch program to let you connect again to the wifi.
See if this helps at all. It may take a bi of time (because of the slow internet connection), but it should work (in theory).antiX Live system enthusiast.
General Live Boot Parameters for antiX.Hi Xecure,
I did steps 1-3 fine, but when I tried to unload the b43-pci-bridge module, there was an error:demo@antix1:~ $ sudo modprobe -r b43-pci-bridge && sleep 2 modprobe: FATAL: Module b43-pci-bridge not found. demo@antix1:~ $ sudo modprobe -r b43-pci-bridge modprobe: FATAL: Module b43-pci-bridge not found. demo@antix1:~ $ inxi -nxxxz Network: Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter vendor: Hewlett-Packard driver: 8139too v: 0.9.28 port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:8139 class-ID: 0200 IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> Device-2: Broadcom BCM4306 802.11b/g Wireless LAN vendor: Hewlett-Packard driver: b43-pci-bridge v: N/A port: 3000 bus-ID: 02:06.0 chip-ID: 14e4:4320 class-ID: 0280 IF-ID-1: wlan0 state: down mac: <filter> demo@antix1:~ $ sudo modprobe b43-pci-bridge modprobe: FATAL: Module b43-pci-bridge not found in directory /lib/modules/4.9.0-279-antix.1-486-smp demo@antix1:~What can I do next?
Xecure
What can I do next?
Try with Control Centre > Maintenance > Network Assistant > Drivers and unload and reload the module there.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Robin
Short rapport about my first impressions of antiX21-beta2 Live from USB (intentionally without persistence for now) on a 32 bit Pentium M Notebook:
To put it in a nutshell: Great! Many thanks to anticapitalista and the dev team!
Boots straight up to desktop. This time the display is way better than in the Versions before, no blurry letters, colours are fine and well saturated this time. So the nouveau driver seems to have got some improvement meanwhile. But, and now comes the inevitable »but«, it seems to produce much more CPU load than I was used from antiX 17.4.1 and 19, especially while moving windows around by mouse, CPU goes up to 100%. I’ll have to check whether this can be solved by fine tuning the nouveau driver settings, or whether this can only be helped by installing original nvidia driver again. I’ll start another thread for this detail next days.
In this place I’d like to plead for an additional entry in boot parameter selection:
linux=<width>x<height>
This cheatcode is not wellknown, not even documented, (At least I don’t know of, and I believe It isn’t even in our wiki still). And then it is the equivalent to grub gfxpayload entry, which allows to set a monitor/display and screen setting in case the needed configuration was not determined correctly and automatically. I’ve spent some hours on testing different methods of setting the correct values from within a blurry desktop using first ARandR from antiX control center and then xrandr in a console window. All in vain. It was literally impossible to fix this from within antiX, so this bootcode is of real importance, worthy to get an entry in boot screen. I’m sure I’m not the single person seeing a very poor desktop without this.This is all the technical data I’ve collected until now:
$ inxi -Fxzr System: Kernel: 4.9.0-279-antix.1-486-smp i686 bits: 32 compiler: gcc v: 10.2.1 Desktop: IceWM 2.7.0 Distro: antiX-21-b2_386-full Grup Yorum 6 September 2021 base: Debian GNU/Linux 11 (bullseye) Machine: Type: Other-vm? System: Notebook product: RIM2000 v: N/A serial: <filter> Mobo: Notebook model: RIM2000 serial: <filter> BIOS: Phoenix v: RIM00F0A date: 05/27/2005 Battery: ID-1: BAT0 charge: 0 Wh condition: N/A volts: N/A model: ARIMA LI4403A status: Unknown CPU: Info: Single Core model: Intel Pentium M bits: 32 type: MCP arch: M Dothan rev: 8 cache: L2: 2 MiB flags: nx pae sse sse2 bogomips: 2128 Speed: 1067 MHz min/max: 800/1733 MHz Core speed (MHz): 1: 1067 Graphics: Device-1: NVIDIA NV43M [GeForce Go 6600] vendor: Rioworks driver: N/A bus-ID: 01:00.0 Display: x11 server: X.Org 1.20.11 driver: loaded: nouveau,vesa unloaded: fbdev,modesetting resolution: 1024x768 OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 20.3.5 direct render: Yes Audio: Device-1: Intel 82801FB/FBM/FR/FW/FRW High Definition Audio vendor: Rioworks driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 Device-2: Philips s SAA7131/SAA7133/SAA7135 Video Broadcast Decoder vendor: Animation driver: saa7134 v: 0, 2, 17 bus-ID: 06:03.0 Sound Server-1: ALSA v: k4.9.0-279-antix.1-486-smp running: yes Network: Device-1: Marvell 88E8036 PCI-E Fast Ethernet vendor: Rioworks driver: sky2 v: 1.30 port: 2000 bus-ID: 02:00.0 IF: eth0 state: down mac: <filter> Device-2: Intel PRO/Wireless 2200BG [Calexico2] Network driver: ipw2200 v: 1.2.2kmprq port: 2000 bus-ID: 06:08.0 IF: eth1 state: up mac: <filter> IF-ID-1: irda0 state: down mac: <filter> Drives: Local Storage: total: 151.75 GiB used: 29.42 GiB (19.4%) ID-1: /dev/sda vendor: Seagate model: ST9100823A size: 93.16 GiB ID-2: /dev/sdb type: USB vendor: Generic model: Flash Disk size: 58.59 GiB Swap: ID-1: swap-1 type: partition size: 2 GiB used: 184 KiB (0.0%) dev: /dev/sda9 Sensors: Message: No sensor data found. Is lm-sensors configured? Repos: Packages: 1563 Active apt repos in: /etc/apt/sources.list.d/antix.list 1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/bullseye bullseye main nosystemd nonfree Active apt repos in: /etc/apt/sources.list.d/bullseye-backports.list 1: deb http://deb.debian.org/debian bullseye-backports main contrib non-free Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 1: deb http://ftp.de.debian.org/debian/ bullseye-updates main contrib non-free Active apt repos in: /etc/apt/sources.list.d/debian.list 1: deb http://ftp.de.debian.org/debian/ bullseye main contrib non-free 2: deb http://security.debian.org/ bullseye-security main contrib non-free No active apt repos in: /etc/apt/sources.list.d/various.list Info: Processes: 140 Uptime: 3h 5m Memory: 1.97 GiB used: 1020.7 MiB (50.7%) Init: SysVinit runlevel: 5 Compilers: gcc: 10.2.1 Shell: Bash v: 5.1.4 inxi: 3.3.06And here I’ll append some problematic details from dmesg output of first boot:
$ dmesg (...) [ 0.009102] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization [ 0.009105] Spectre V2 : Mitigation: Full generic retpoline [ 0.009107] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch [ 0.009108] Speculative Store Bypass: Vulnerable [ 0.009109] L1TF: Kernel not compiled for PAE. No mitigation for L1TF [ 0.009135] MDS: Vulnerable: Clear CPU buffers attempted, no microcode [ 1.518351] Warning! fotg210_hcd should always be loaded before uhci_hcd and ohci_hcd, not after [ 20.241771] [Firmware Bug]: ACPI(VGA) defines _DOD but not _DOS [ 20.241840] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no) [ 20.242496] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/LNXVIDEO:00/input/input7 [ 20.242540] [Firmware Bug]: ACPI(VGA1) defines _DOD but not _DOS [ 20.242588] ACPI: Video Device [VGA1] (multi-head: yes rom: no post: no) [ 20.242664] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input8 [ 20.617976] ACPI Warning: SystemIO range 0x00000000000011B0-0x00000000000011BF conflicts with OpRegion 0x0000000000001180-0x00000000000011BB (\GPIO) (20160831/utaddress-238) [ 20.617987] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 20.617988] ACPI Warning: SystemIO range 0x0000000000001180-0x00000000000011AF conflicts with OpRegion 0x0000000000001180-0x00000000000011BB (\GPIO) (20160831/utaddress-238) [ 20.617994] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 20.617995] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 21.735961] nouveau 0000:01:00.0: bios: version 05.43.02.49.18 [ 21.736185] vmap allocation for size 16781312 failed: use vmalloc=<size> to increase size [ 21.736188] nouveau 0000:01:00.0: imem: unable to map PRAMIN BAR [ 21.736194] nouveau 0000:01:00.0: imem ctor failed, -14 [ 21.736202] nouveau: probe of 0000:01:00.0 failed with error -14And now some of my attempts of fixing the resolution problem from within antiX:
– Delay of ca. 60 seconds after graphics mode is supposed to get switched to correct resolution (immedieatly before X-desktop should come up), screen stays black, but backlight stays “on”. Finally desktop appears.
– Desktop has wrong resolution, and no means to switch to correct resolution:
– Graphic display of is slow and generally delayed, movement of windows with mouse pointer is scattering and heavily delayed, causing 100% CPU load.
(looks like everything is software rendered by CPU instead of GPU.)
– Control center –> Session –> Screen Resolution (ARandR) does only show
1024×768
800×600
640×480
The correct Resolution of 1440×900 is missing.
Using xrandr on command line shows same result:$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768 default connected 1024x768+0+0 0mm x 0mm 1024x768 0.00* 800x600 0.00 640x480 0.00Trying to correct this problem by adding the missing resolution following the default steps also fails:
xrandr --newmode "1440x900_60.00" 106.47 1440 1520 1672 1904 900 901 904 932 -HSync +Vsync xrandr --addmode default "1440x900_60.00" xrandr --output default --mode "1440x900_60.00" xrandr: Failed to get size of gamma for output default xrandr: Configure crtc 0 failedA short flicker at screen, but resolution remains unchanged.
Now again:$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1440 x 900 default connected 1024x768+0+0 0mm x 0mm 1024x768 0.00* 800x600 0.00 640x480 0.00 1440x900_60.00 60.00 $ xrandr --output default --mode "1440x900_60.00" xrandr: Failed to get size of gamma for output default xrandr: Configure crtc 0 failed $ xrandr --listmonitors xrandr: Failed to get size of gamma for output default Monitors: 1 0: +default 1024/271x768/203+0+0 default $ xrandr --setmonitor "crtc 0" 1440/370x900/230+0+0 default output list default add monitor default output name default xrandr: Failed to get size of gamma for output default $ xrandr --listmonitors xrandr: Failed to get size of gamma for output default Monitors: 1 0: crtc 0 1440/370x900/230+0+0 default $ xrandr --output default --mode "1440x900_60.00" xrandr: Failed to get size of gamma for output default xrandr: Configure crtc 0 failedNext thing: What does all the dmesg stuff about vulnerabilities mean? I’ve believed antiX was safe in this concern. Can something be done to ship antiX 21 safer (or do I misinterpret this output?) Here is what inxi reported:
$ inxi -Ca CPU: Info: Single Core model: Intel Pentium M bits: 32 type: MCP arch: M Dothan family: 6 model-id: D (13) stepping: 8 microcode: 20 cache: L2: 2 MiB flags: nx pae sse sse2 bogomips: 2128 Speed: 1067 MHz min/max: 800/1733 MHz Core speed (MHz): 1: 1067 Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable Type: l1tf status: Vulnerable Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled Type: meltdown status: Vulnerable Type: spec_store_bypass status: Vulnerable Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling Type: srbds status: Not affected Type: tsx_async_abort status: Not affectedNext observation:
We see still an 3.17.x version of Claws Mail in antiX 21. This is very sad, since it doesn’t work anymore with most email providers, who meanwhile mandatory expect OAUTH procedure for accessing the account via POP/IMAP. This feature has been added in Claws Mail 3.18.0 / 4.0.0 only, so antiX 21 should really ship one of these versions, if possible.Another thing I have to check in detail is: Playing video on any of the bundled players caueses 100% CPU load even when using material of very poor resolution, and in one case even a complete system lock while playing, I had to hard reset. Maybe this is somehow connected to the nouveau driver, since I have never seen this behaviour on any antiX before while using original nvidia drivers on 17.4.1 and 19. Maybe this can also get helped by fine tuning the driver settings of nouveau.
And now @skidoo : zzzfm is simply great. I saw it first time working now, it feels way better than spacefm. You did a great job! Many thanks!
So that’s all I can tell for now, I hope this could help you. Next days I’ll try to check the remaining functions of this notebook under this beta release, one by one, and also on the athlon XP (also 32 bit) board.
Btw, antiX 19 has proven to be rock stable here, uptime of the file server in cellar running on antiX was about 100 days, before I rebooted, merely for this beta-test now.
So long
RobinWindows is like a submarine. Open a window and serious problems will start.
Hi @Xecure,
Success! With your help, I was able to install the firmware-b43-installer version 019-4 that was working in version antiX 19.1. The one installed in antiX 21 B2 was 019-7. That did not work on my ze4900 system using the antiX 21 B2 32-bit version.
After installation of the 019-4 version, I was able to achieve download speed of 17.7 Mb/s and upload speed of 16.0 Mb/s according to the Centurylink speed test. These numbers are similar to the antiX 19.1 installed system on the same computer. I am typing and posting this using this wifi connection as we speak.
I learned the process of determining which driver was not working, learned how to install the correct network driver, learned how to unload and load the network module, etc. I am grateful to learn this.
Thank you for teaching me and working with me to troubleshoot some network issues on the B2 test version.I can now install this B2 system on this computer and do more testing on it.
The sequence of steps that allowed me to install the firmware-b43-installer version 019-4 is as follows:
sudo apt purge firmware-b43-installer wget http://ftp.us.debian.org/debian/pool/contrib/b/b43-fwcutter/firmware-b43-installer_019-4+deb10u1_all.deb sudo apt install ./firmware-b43-installer_019-4+deb10u1_all.deb Control Centre > Maintenance > Network Assistant > Linux drivers and unload the b43 module that was not working. wait for at least 5 seconds Control Centre > Maintenance > Network Assistant > Linux drivers and reload the newly installed b43 module. antix-wifi-switch --gui connman login to wifi networkQuestion: Should we put the Network Assistant module under Control Centre > Network instead of Control Centre > Maintenance?
Xecure
@calciumsodium I am glad it worked. The package version 019-7 in antiX 21 has an inbuilt check in the post install instructions to see what version should be installed (recent vs original buster version). As I mentioned before, the program that builds the ISO does it in a closed environment, so it will default to the “recent” firmware version. Reinstalling the package on a system that requires the older version should fix the problem (it would be great if you could test the same method described before, but instead of installing the buster version, reinstalling the bullseye version, to see if the script does its job properly and installs the older firmware).
In this place I’d like to plead for an additional entry in boot parameter selection:
linux=<width>x<height>
This cheatcode is not wellknown, not even documentedI tried it out on a VM, but it doesn’t work for me. Do I need to remove other boot parameters to work? What kernel versions work with this boot parameter? I am interested in this parameter.
Next thing: What does all the dmesg stuff about vulnerabilities mean?
Based on this thread (I cannot find if it is also true on kernel-org kernels compiled by anticapitalista), kernel 4.9 (32 bits) is not receiving latest kernel security patches, but kernel 4.19 (686-pae only) is (but that is for Debian; as I said, I am not sure if it is the same for antiX compiles kernels).
- This reply was modified 1 year, 7 months ago by Xecure.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.I tried it out on a VM, but it doesn’t work for me. Do I need to remove other boot parameters to work? What kernel versions work with this boot parameter?
Since I have tested 21 beta2 only Live from usb stick by now, without persistence, as I mentioned, the 4.9 kernel as shipped on the ISO is the only one I’ve tested by now. But I remember from setting up antiX 19 long ago that this code works also on a 4.19 kernel. I can confirm this as soon I’ll have once set up persistence and switched to the 686 pae kernel, which will be the 4.19 then.
Maybe the weak performance on my machine compared to the 19 I’ve manually fine tuned for this device already is due to the fact that 21b2 runs on a 486 kernel still. We’ll see.You simply need to append this bootcode to make things work, in my case it reads
linux=1440x900
right at the end of the existing line. No need to remove any other parameter, at least in my case. Additional I use 1024×768 for terminal, from the f7 menu, but this is not mandatory. It works with and without the resolution setting for the terminal, it is independent from this. Maybe it doesn’t work on installed antiX, or in a virtual environment.
I’ve also tried to add a depth value, as defined for »grub gfxpayload linux« parameter, but this fails here:
linux=1440x900x32doesn’t work. Moreover I believe any value not valid for or not supported by the graphics device will be ignored silently. At least I noticed that behaviour during my tests. So, if your virtual device driver doesn’t support the resolution you pass with this code, it will not have any visible effect.Windows is like a submarine. Open a window and serious problems will start.
The package version 019-7 in antiX 21 has an inbuilt check in the post install instructions to see what version should be installed (recent vs original buster version). As I mentioned before, the program that builds the ISO does it in a closed environment, so it will default to the “recent” firmware version. Reinstalling the package on a system that requires the older version should fix the problem (it would be great if you could test the same method described before, but instead of installing the buster version, reinstalling the bullseye version, to see if the script does its job properly and installs the older firmware).
Hi @Xecure,
I tried bothsudo apt purge firmware-b43-installer sudo apt update && sudo apt install firmware-b43-installer Control Centre > Maintenance > Network Assistant > Linux drivers and unload the b43 module that was not working. wait for at least 5 seconds Control Centre > Maintenance > Network Assistant > Linux drivers and reload the newly installed b43 module. antix-wifi-switch --gui connman login to wifi networkand also
sudo apt update && sudo apt install --reinstall firmware-b43-installer Control Centre > Maintenance > Network Assistant > Linux drivers and unload the b43 module that was not working. wait for at least 5 seconds Control Centre > Maintenance > Network Assistant > Linux drivers and reload the newly installed b43 module. antix-wifi-switch --gui connman login to wifi networkNeither of them worked on my ze4900 system. The wifi remained very slow.
The only way so far that worked was to install the buster version of the firmware-b43-installer.
- You must be logged in to reply to this topic.
