have you inserted usb disk with firmware during installation?

2023-02-19 Thread lsg

installer seems very buggy

bullseye installer can't find firmware after i insert usb disk

after lots of frustration and effort, i realize i shall copy firmware to 
sda1, which use vfat FS, then installer can get firmware without 
prompting me.




Re: hard disk installation method fails

2023-02-17 Thread lsg

i am sorry link in my last mail may not work outside china



Re: hard disk installation method fails

2023-02-17 Thread lsg

Thank David Wright very much!

i think error msg i report is precise, i use cell phone to record screen,

https://pan.baidu.com/s/1a5ADqn1aXo5XmwcDSjVezQ?pwd=1234

this url is valid for 7 days, i am sorry picture isn't very clear. 
installer search disk for iso file, can't find suitable one, and display 
"No kernel modules found" screen



does your installer find your iso file? or do you really install via 
http? network connection isn't needed if you use hard disk installation 
method, with debian-11.6.0-amd64-netinst.iso you can install bare 
minimal debian system








Re: hard disk installation method fails

2023-02-17 Thread lsg



On 2/18/23 11:12, Charles Curley wrote:


That wouldn't help. My method pulls the kernel and initrd from the iso
itself. I got the same error you did.

I used the weekly build, so I shall wait until the next build and see
if that works.

Really? i am afraid vmlinuz and initrd pair in iso file don't include 
program that search disk for iso file, as pair in hd-media directory does


Debian11.6/main/installer-amd64/current/images/hd-media

though it's possible to boot iso file with grub, but it's too complicated

it seems few users are using hard disk installation method theses days



Re: hard disk installation method fails

2023-02-17 Thread lsg

On 2/17/23 22:29, Brian wrote:

There isn't much you can do about this. It is usually a temporary
issue thats happens after Linux kernel updates. The installer is
now out of step. It gets automatically fixed after some time.

Thanks! i've thought updating iso image and hard disk installer are 
automatic


it's very frustrating, i've never been so disappointed with debian

it will be easier if i can determine if they match by matching file name 
of iso file with that of vmlinuz and initrd pair (their file names shall 
all include same version number)


i have successfully used bullseye hard disk installation method for i386 
about one month ago, i don't know why it doesn't work this time






Re: hard disk installation method fails

2023-02-16 Thread lsg

On 2/16/23 22:10, Charles Curley wrote:

You shouldn't need separate vmlinuz and initrd.gz files. You should be
able to boot directly to the iso image. Depending on how talented your
computer's firmware is, you may have to copy the iso image to sdb, not
sdb1. E.g.:

dd if=.iso of=/dev/sdX

What instructions did you start with? Exact URL, please.

I've been playing with a separate partition to house a Debian installer
ISO should I ever need it for rescue or re-installation. But that
depends on having grub installed and a suitable entry for the d-i iso
image. If that's what you want to do, I can help with that also.


Thank Charles!

https://www.debian.org/releases/stable/amd64/ch04s04.en.html

to reproduce my problem, you need 3 files: vmlinuz, initrd.gz and 
corresponding iso file


add entry to grub menu, boot it to see if it can locate iso file, there 
is no need to re-partition your disk


my pc can boot usb stick, but during installation it prompts me for usb 
disk with non-free firmware , this step fails







hard disk installation method fails

2023-02-16 Thread lsg

this is quite unbelievable, it's most widely-used platform: amd64

installer says "No kernel modules found", probably due to kernel mismatch

debian-11.6.0-amd64-netinst.iso is at sdb1, vfat partition, i've checked 
it with sha256sum


vmlinuz and initrd.gz are copied from:

http://ftp.sunet.se/debian/dists/bullseye/main/installer-amd64/current/images/hd-media/



Re: failed to load rtl_bt/rtl8761b_fw.bin

2023-01-13 Thread lsg



Thank David! you are right, i get firmware for bookworm, extract it with 
dpkg-deb, copy it to /lib/firmware/rtl_bt, now bluetooth works in bullseye




failed to load rtl_bt/rtl8761b_fw.bin

2023-01-13 Thread lsg

i have usb wireless dongle, it uses rtl8761b chip, it works in opensuse

but bullseye complains though i have installed non-free firmware-realtek:

[   16.123855] bluetooth hci0: firmware: failed to load 
rtl_bt/rtl8761b_fw.bin (-2)




bullseye installer can't load non-free firmware from usb stick

2023-01-13 Thread lsg
but i use hard disk installation method, i put firmware in same place as 
iso image, installer can locate firmware without prompting me




Re: why rfkill not list my wifi device

2023-01-13 Thread lsg



On 1/10/23 21:17, Charles Curley wrote:

Interesting. Running "modprobe rfkill" wouldn't return anything because
the module is already installed. However, I get a slightly different
result from the lsmod command:

root@jhegaala:~# lsmod | grep rfkill
rfkill 32768  7 bluetooth,thinkpad_acpi,cfg80211
root@jhegaala:~#

The rfkill module is used by three other modules in my case. The first
two are related to bluetooth. The third, which your listing also shows,
controls network interfaces, including wifi. So I conjecture that you
have all the right modules installed.

However, in my reading I found out that not all wifi drivers support
rfkill. That may be your problem.


Thank Charles ! you are right. i have 2 usb wifi adapters now, one can 
be listed by rfkill, the other can't




Re: why rfkill not list my wifi device

2023-01-10 Thread lsg

actually i want to use rfkill to block or unblock device

is it possible to do it with wireless-tools?



Re: why rfkill not list my wifi device

2023-01-10 Thread lsg

On 1/10/23 18:10, Alexander V. Makartsev wrote:

In that case check if "rfkill" kernel module is actually loaded, 
because it is necessary for rfkill utility to function:

    $ lsmod | grep -iE "rfkill"

Use "modprobe" utulity to load it:
    $ sudo modprobe rfkill

It is possible that driver module (your current version) for this 
adapter simply doesn't support "rfkill" subsystem.


--
With kindest regards, Alexander.



Thank Alexander! i run lsmod | grep -iE "rfkill", it says

rfkill 20480  2 cfg80211

both "modprobe rfkill" and rfkill return nothing




Re: why rfkill not list my wifi device

2023-01-09 Thread lsg



On 1/10/23 15:26, Alexander V. Makartsev wrote:
For this adapter, according to Wireless Wiki [1], you should use 
universal driver "rtl8xxxu". See if it was loaded:

    $ sudo lsusb -t

Check out the logs for relevant messages:
    $ sudo grep -iE "rtl|firmware" /var/log/syslog

This should give you a hint about a firmware file needed for this adapter.
Probably it is a good idea in general to install firmware package for 
Realtek-based devices from "non-free" section of Debian repos:

    $ sudo apt install firmware-realtek


[1] https://wireless.wiki.kernel.org/en/users/drivers/rtl819x
--
With kindest regards, Alexander.



Thank Alexander!

actually my usb wifi adapter works well in buster but rfkill doesn't

i want to get rfkill to work



Re: why rfkill not list my wifi device

2023-01-09 Thread lsg

On 1/10/23 14:51, Leandro Noferini wrote:


I think for this adapter you need to use the dkms kernel modules: 


–
Ciao
leandro


Thank Leandro! dkms has been installed

root@debian:~# apt install dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
dkms is already the newest version (2.6.1-4).
0 upgraded, 0 newly installed, 0 to remove and 196 not upgraded.



Re: why rfkill not list my wifi device

2023-01-09 Thread lsg



On 1/10/23 12:25, Charles Curley wrote:

What hardware? A suitable lspci list might help.
Mine shows:

root@jhegaala:~# rfkill
ID TYPE  DEVICE   SOFT  HARD
  0 bluetooth tpacpi_bluetooth_sw   blocked unblocked
  3 wlan  phy2unblocked unblocked
root@jhegaala:~#

Then if I use the physical switch to turn off any transmitters, I see:

root@jhegaala:~# rfkill
ID TYPE  DEVICE SOFTHARD
  0 bluetooth tpacpi_bluetooth_sw blocked blocked
  3 wlan  phy2blocked blocked
root@jhegaala:~#



Thank Charles! it's usb wifi adapter, lsusb shows

Bus 001 Device 005: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter


rfkill shows nothing




why rfkill not list my wifi device

2023-01-09 Thread lsg
according to web page by expert, rfkill without options shall list 
wireless device, but it shows nothing though my wifi adapter is active 
in buster




Re: netgear wna3100 not supported by linux?

2023-01-09 Thread lsg


On 1/9/23 17:51, Mark Fletcher wrote:




Looks like you need to use ndiswrapper with the windows drivers to get 
it to work. Saw that on an Ubuntu forum but what’s good for the gander 
is often good for the goose…


Mark



Thank Mark! i've been directed to Ubuntu forum too, it's too 
complicated, i'd rather buy another usb wifi adapter, it's inexpensive 
these days.


netgear wna3100 not supported by linux?

2023-01-09 Thread lsg

i've searched Internet, it doesn't seem supported by linux?? too bad



Re: why some memory are missing

2023-01-08 Thread lsg



On 1/8/23 17:36, hede wrote:


I'm pretty sure it can address 2^32 bit aka 4 GB. But within this 
range there is the PCI address space.  PCI cards are memory mapped. To 
access memory regions on PCI devices you can simply access main 
memory. But you cannot access PCI devices AND use full 4 GB of 
physical main memory within the 2^32 bit range.


Typically Chipsets/BIOS can map the missing memory somewhere above 4 
GB but not every Chipset/BIOS does this. Then even in 64 Bit mode 
you'll lose memory in the range of the PCI address space. If, on the 
other side, the Chipset/BIOS maps those memory regions above 4 GB then 
even in 32 Bit Mode Linux can use this memory (via PAE).


hede


Thank hede! you solved my problem! i enable Memory hole Remapping in 
bios, memtest86+ shows 4095M memory now! top in buster for 686 shows 
3029.6M while top in bullseye for amd shows 3930.9M. Thanks!




Re: why some memory are missing

2023-01-07 Thread lsg


On 1/8/23 07:30, Jeremy Hendricks wrote:
I imagine it’s a bios limitation and it cannot address the full 4GB 
even though it’s a 64bit CPU. This was common with the Intel 925/945 
chipsets even through they supported Intel 64bit CPUs of the time.






Thank Jeremy Hendricks!

it seems to me that someone made foolish mistake

hp seems to say  it's not my fault by reminding user in reference guide 
that "The memory available may be limited by the operating system."


Re: why some memory are missing

2023-01-07 Thread lsg

Thank Greg Wooledge!

i've tried bullseye for amd64, it doesn't help

memtest86+ claims it can test all memory




why some memory are missing

2023-01-07 Thread lsg

i have hp dx5150, running buster

bios shows 4G memory, but in buster, top shows 3282.8M

i have independent graphics card, memory isn't shared i think

i have tried bullseye for amd, it doesn't show 4G either

memtest86+ shows about 3G memory

hp guide says "The memory available may be limited by the operating system."