cannot connect to wifi (solved)

[wnewbury]

Got a new used HP EliteDesk. Connects to wifi using win 10 but it can't find any wifi using fossapup 64 (or linux mint) Not just can't connect; Can't even find. Did HP make it windows only? Thanks in advance.

[rockedge]

@wnewbury It is a matter of finding out what type of WiFi device you have in the machine. Then it should be possible to ensure the correct drivers are found and used to use the wireless device/card.

Use Menu->System->Pup-Sysinfo to see if any device is recognized.

Or boot into Windows and check what the network device is.

[bigpup]

This is a lot of steps to make a connection, but it will tell us exactly what your problem is.

menu->Setup->Internet Connection Wizard->Wired or wireless LAN->Network Wizard

Network Wizard wireless connection steps.

1. Select Network Wizard
2. Select wlan0 (your network card may have a different description)
3. Select Wireless in the Configure wireless network box.
4. Select Scan and your ESSID (WIFI router) should come up.
5. Select your ESSID and OK
6. Give a name to your profile. It should already be what you selected in step 5.
7. Encryption. Most people use WPA/TKIP - select it or WPA2.
8. A box will open for you to write the WPA password. It is called a Shared Key. Enter the password.
9. Leave the other boxes as they are. Rarely do these need adjustment.
10. Select Save
11. Select Use This Profile
12. A box will appear showing Puppy trying to connect
13. A box will come up “REPORT ON TEST 0f wlan0CONNECTION”
14. Select Auto DHCP in the Configure interface box and it will go through a handshake routine. and declare itself successful
15. Select done

Select to use this setup on reboot.
Select to use this as default.

If something does not work.
What step?
You do what?
You see what?

Also make sure your system's time zone setting is correct - if not, many website's certificates then act as if they are expired, and the webpage won't display.

[mikeslr]

Hi wnewbury. to the Forum.

Lest you become discouraged and give up too soon, let me explain what's going on. There are two components to every personal computer: the hardware and the operating system. Hardware consists of the motherboard and peripherals such as keyboards, mice, monitors, sound cards, wireless adapters. There are hundreds, by now likely thousands, of different wireless adapters a computer manufacture can choose. The 'foundation' component of an operating system is 'the kernel'. Using an automobile analogy, the kernel is kind of like an operating system's engine and chassis. All other parts of a computing system must be able to communicate with the Kernel; in some instances must be built specifically for that Kernel. [Consider the difference between a car's braking system, and its radio: the latter being pretty much 'plug and play']. To enable that communication between hardware and software requires programs known as drivers and firmware.

Linux.org constantly modifies the kernel (a) to eliminate 'bugs'; (b) to work with newly manufactured hardware; and (c) counter newly discovered or created malware. Often Linux.org provides a Kernel with a major update 10 times a year; with several minor updates between those. But to accommodate the inclusion of drivers needed by new computers some old drivers may not be included. Linux is so good at creating Kernels that a couple of years ago Microsoft stopped making its own: it picks one created by Linux.org, does some modifications, and only occasionally providing an update.

Microsoft has roughly 80% of the personal computing market. With only a few exceptions a manufacturer of computers produces a product that will run Windows. To do that they use a Kernel which works with Windows, includes peripheral components also created to work with Window, provides the Windows Operating System AND all the drivers and firmware needed by those peripherals.

Only as an afterthought, and only if not too expensive, do PC manufacturers sometimes provide firmware and drivers for some other Kernels. So, to a large extent if a Linux Operating system is to communicate with some peripheral, some Linux Dev must create the necessary drivers and firmware. Some peripherals rarely change --e.g. mice and key-boards. But wifi adapters --to handle the evolving graphic capability of websites and transmission capabilities of internet providers-- must evolve. New drivers must be compiled to work with the Kernel in use.

[Firmware is NOT kernel-specific. But to keep Puppys small and reduce demands on RAM, not all possible firmware is included by default: only that which is likely required by the majority of computers capable of running that Puppy. Puppys are built 'modularly'. Firmware is provided in a module with the designation fdrv; in Fossapup64 fdrv_fossapup64_9.5.sfs. That only occupies 40 MBs of hard-drive space. Puppy Devs have published more extensive collections of firmware which may require over 200 Mb of Space. These can be substituted for the 'originals' by merely downloading them, renaming the Download fdrv_fossapup64_9.5.sfs and replacing the original.]

Missing Drivers, on the other hand, present a greater challenge. As I mentioned drivers are ‘Kernel-specific’. Puppy Linux is better able to overcome that challenge than other Linuxes. There are two methods. One is to compile a needed driver for the Kernel you have. Compiling applications isn’t always easy; and something unlikely to be undertaken by ‘newbies’. The other method is to swap the Kernel you have for one which provides the necessary driver. Other Linuxes provide little opportunity to do that. Puppys’ modular build –together with the work of several of our Devs who create and publish Kernels and their drivers-- can make swapping kernels about as easy as swapping the firmware module. Unfortunately, it is only ‘easy’ if the required Kernel already has been published. In the absence of such Kernel and driver, some Puppy Dev may be willing to compile the driver for the Kernel you have.

And an even easier solution may be to pick a different Puppy which already has the necessary Kernel and driver. Unlike other Linuxes, there are many Puppys to choose from.

Bigpup has suggested trying Network-Wizard rather than Simple Network Setup or Frisbee. Although configuring Network-Wizard is a little more complicated than the others, my experience is that it has a better chance of finding a wireless signal if you have the necessary drivers and firmware. So it’s really the first thing to try.

Rockedge’s post is about finding out what wifi-adapter your computer has. If we know the adapter, we can search for the specific driver it needs. Also see this post for other ways to begin that search, https://www.forum.puppylinux.com/viewto ... 73#p101973. And rather than merely telling us that you have a HP EliteDesk, specifying the model will also help: different models may use different wifi adapters.

Take heart. HP is one of the computer manufacture whose wifi-adapters we can usually accommodate. And as a last resort, if all else fails, we can suggest a USB-Dongle known to work.

[wnewbury]

Thanks for all the help. BookwormPup64 does everything I want.