6.7.1 DVD Weakest Link

[luther]

RE: 6.71 DVD weakest Link: Network Functionality
# MD5 checksums generated by MD5summer (http://www.md5summer.org)
# Generated 2/15/2012 9:11:08 PM
90c0a0acbbd954145b6f55ca36e2e87f *KNOPPIX_V6.7.1DVD-2011-09-14-EN.iso_EXP
90c0a0acbbd954145b6f55ca36e2e87f *KNOPPIX_V6.7.1DVD-2011-09-14-EN.iso_ACT
Hi,
1) Only Chromium browser functions ok.
2) 6.7.1 Firewall does not recognize Persistent 'Knoppix-data.img'?
3) MAC80211 stack/b43 wireless card driver missing?



Any help/support?
THX
Luther, new to the Linux world!
PS. Mint installed OotB following:
apt-get install b43-fwcutter
apt-get install b43-fwcutter firmware-b43-installer
*******
knoppix@Microknoppix:~$ sudo ifconfig
eth0 Link encap:Ethernet HWaddr 00:0f:b0:fa:e5:31
inet addr:192.168.0.71 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20f:b0ff:fefa:e531/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:507 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:31480 (30.7 KiB) TX bytes:1272 (1.2 KiB)
Interrupt:22 Base address:0xa000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:440 (440.0 B) TX bytes:440 (440.0 B)

knoppix@Microknoppix:~$ lspci -vnn | grep 14e4
06:02.0 Network controller [0280]: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g
Wireless LAN Controller [14e4:4318] (rev 02)

knoppix@Microknoppix:~$ sudo unname -a
sudo: unname: command not found

knoppix@Microknoppix:~$ lspci -vvn|grep 43 -a7
Bus: primary=00, secondary=02, subordinate=03, sec-latency=0
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort-
<SERR- <PERRBridgeCtl:
Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2BPriDiscTmr-
SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
Kernel driver in use: pcieport


knoppix@Microknoppix:~$ sudo dmesg
: No partition found (1)
[ 2.395325] scsi 2:0:0:0: Direct-Access Lexar USB Flash Drive 8.07 PQ: 0 ANSI: 2
[ 2.395843] sd 2:0:0:0: Attached scsi generic sg2 type 0
[ 2.396934] sd 2:0:0:0: [sdb] 15663104 512-byte logical blocks: (8.01 GB/7.46 GiB)
[ 2.397426] sd 2:0:0:0: [sdb] Write Protect is off
[ 2.397430] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 2.397927] sd 2:0:0:0: [sdb] No Caching mode page present
[ 2.397930] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 2.400312] sd 2:0:0:0: [sdb] No Caching mode page present
[ 2.400315] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 2.523709] attempt to access beyond end of device
[ 2.523714] sda3: rw=0, want=66, limit=2
[ 2.523718] isofs_fill_super: bread failed, dev=sda3, iso_blknum=16, block=32
[ 2.531690] attempt to access beyond end of device
[ 2.531695] sda3: rw=0, want=18, limit=2
[ 2.531702] REISERFS warning (device sda3): sh-2006 read_super_block: bread failed (dev sda3,
block 8, size 1024)
[ 2.531709] attempt to access beyond end of device
[ 2.531712] sda3: rw=0, want=130, limit=2
[ 2.531717] REISERFS warning (device sda3): sh-2006 read_super_block: bread failed (dev sda3,
block 64, size 1024)
[ 2.537042] attempt to access beyond end of device
[ 2.537045] sda3: rw=0, want=4, limit=2
[ 2.537049] EXT4-fs (sda3): unable to read superblock
************

[luther]

Hi,
Typing "konqueror" on the command line provides this trace log:
**********
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QStr ing,QString,QString)
kbuildsycoca4 running...
konqueror(3456)/kdecore (KLibrary) findLibraryInternal: plugins should not have a 'lib' prefix:
"libkhtmlpart.so"
konqueror(3456)/kdecore (KLibrary) kde4Factory: The library "/usr/lib/kde4/khtml_kget.so" does
not offer a qt_plugin_instance function.
konqueror(3456)/kdecore (KLibrary) findLibraryInternal: plugins should not have a 'lib' prefix:
"libkhtmlpart.so"
konqueror(3456)/kdeui (kdelibs): Attempt to use QAction "iceweasel" with KXMLGUIFactory!
konqueror(3456)/kdeui (kdelibs): Attempt to use QAction "epiphany" with KXMLGUIFactory!
konqueror(3456)/kdeui (kdelibs): Attempt to use QAction "" with KXMLGUIFactory!
QSslSocket: cannot resolve SSLv2_client_method
QSslSocket: cannot resolve SSLv2_server_method
QPainter::begin: Widget painting can only begin as a result of a paintEvent
QPainter::translate: Painter not active
QPainter::setClipRect: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::drawRects: Painter not active
************
Your comments?
Thanks for your support,
Luther

[luther]

Hi,

Plugging the DNS settings into X's network-admin, got internet connection jump started.
On a live USB, there appears a dummy lock for network-admin.

Question 1:
Can n-a settings be saved on the flash stick?

Question 2:
What is the network-admin equivalent for Adriane, so Elinks can get connected to the internet?

Kind Regards,
luther

[Werner P. Schulz]

Hi, 1) Only Chromium browser functions ok.
2) 6.7.1 Firewall does not recognize Persistent 'Knoppix-data.img'?
3) MAC80211 stack/b43 wireless card driver missing?How do you use your Knoppix DVD download? From DVD, flash disk install, HD installation?
First of all try the cheatcode "knoppix testcd".

[luther]

How do you use your Knoppix DVD download? From DVD, flash disk install, HD installation?
First of all try the cheatcode "knoppix testcd".
Hi,

"knoppix testcd" reported:
Checking KNOPPIX/background.jpg ... Failed!
Checking KNOPPIX/SOURCES.TXT ...
Continue anyway? [ y/N ]

Chromium reported:
Error 137 (net::ERR_NAME_RESOLUTION_FAILED): unknown error
~~~~~~~~~~~
Please refer to:
http://www.mninter.net/~pfourier/screen1.zip

This zip shows installed flash stick footprint and
the reason why background.jpg failed 6.7.1 testcd.

Thanks for reply, Werner!
luther
PS. HD install cannot work on this USB setup.

[Werner P. Schulz]

"knoppix testcd" reported:
Checking KNOPPIX/background.jpg ... Failed!If "knoppix testcd" reports any error, especially within KNOPPIX, there is no need to analyze your other curious problems. The DVD is damaged!

Burn another DVD and test the integrity first.

[luther]

If &quot;knoppix testcd&quot; reports any error, especially within KNOPPIX, there is no need to analyze your other curious problems. The DVD is damaged!

Burn another DVD and test the integrity first.

Dear Werner: My previous post was a testcd of the USB device (flash). At your suggestion, the actual DVD testcd results were:

knoppix 6 found at: /dev/sr0
Checking KNOPPIX/KNOPPIX ... All files OK.
I'm sending this post from 6.7.1 flash install w/Iceweasel. The TRICK was to plug the correct NAMESERVER address into "netcardconfig", e.g.:

sudo netcardconfigIn netcardconfig, "nameserver" defaults to "gateway", which must be changed to get internet connection to the router port. The new "nameserver" address cannot be saved to flash, so it simply has to be entered each session.

My question is, what is the "netcardconfig" equivalent for Adriane? I see NO mention of "nameserver" in Adriane, that Elinks can reference. Elinks DOES function in X-desktop, but doesn't in Adriane. Thanks for the reply! luther

[Werner P. Schulz]

2) 6.7.1 Firewall does not recognize Persistent 'Knoppix-data.img'?There is an error in the script
http://lists.debian.org/debian-knoppix/2011/10/msg00001.html


sudo: unname: command not foundTry
uname -a
I'm sending this post from 6.7.1 flash install w/Iceweasel.Please tell us the output from

df -h(the screenshot is confusing for me).

By the way, do you really need Adriane, the Knoppix version for blind people?

The NetworkManager Applet left the clock in the panel does not work for you?

[luther]

There is an error in the script
http://lists.debian.org/debian-knoppix/2011/10/msg00001.html

Try
uname -aPlease tell us the output from

df -h(the screenshot is confusing for me).

By the way, do you really need Adriane, the Knoppix version for blind people?

The NetworkManager Applet left the clock in the panel does not work for you?

Hi, I found this firewall patch on the forum: "sudo nano /usr/sbin/firewall" ** I changed "KNOPPIX.IMG" to "KNOPPIX-DATA" Shouldn't this be correct?

Please enlighten me on: "sudo: unname: command not found" and also: "uname -a"

Here is the output from code: df -h
knoppix@Microknoppix:~$ sudo df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sdb1 6.5G 6.5G 1.4M 100% /mnt-system
tmpfs 2.0G 0 2.0G 0% /ramdisk
/dev/cloop 8.7G 8.7G 0 100% /KNOPPIX
/dev/loop0 2.8G 885M 1.9G 32% /KNOPPIX-DATA
unionfs 2.8G 885M 1.9G 32% /UNIONFS
unionfs 2.8G 885M 1.9G 32% /usr
unionfs 2.8G 885M 1.9G 32% /home
tmpfs 10M 56K 10M 1% /UNIONFS/var/run
tmpfs 10M 2.8M 7.3M 28% /run
tmpfs 10M 0 10M 0% /UNIONFS/var/lock
tmpfs 100M 76K 100M 1% /UNIONFS/var/log
tmpfs 2.0G 12K 2.0G 1% /tmp
udev 20M 32K 20M 1% /dev
tmpfs 2.0G 148K 2.0G 1% /dev/shm
knoppix@Microknoppix:~$The screenshot is confusing simply because I swapped out "background.jpg" with an earlier release. I can't imagine this mod effecting functionality. My question to you, Werner, is using a 1 GB Linix/Swap file in flash. Is it relevant?

As far as using Adriane, it appears the ONLY alternative to get Knoppix to work on my older hp dt PC with 95MB RAM. I'm quite sure "nameserver" defaults to "gateway", which needs to be changed inorder to get Elinks on the 'net, like it does w/X-desktop. The clock applet is excess baggage and can be removed, if possible. Thanks for replying to my post. luther PS. Posted w/6.7.1 flash installation


---------------------------------------
Please use the "Go Advanced" button to have more abilities to format the posting; before sending your posting use "Preview" to see how it looks like.

[Werner P. Schulz]

If you allready changed the firewall script, it's ok.

unname != uname

You can start Knoppix with cheatcode "knoppix 2" to start with text-console.
Adriane uses "knoppix-network-manager" or alternativ "network-setup".
The other way to get the network-settings is: Type

adrianewithin the console and then select "Setup".

[luther]

Hi,

My ISP's nameserver address' MUST be
manually entered each session:


sudo nano /etc/resolv.conf
luther
PS. NoScript was blocking format options
**posted w/6.7.1 DVD's flash install
:)

[luther]

Hi,

Anyone know of a tried-and-true method for
downloading and installing the missing "b43"
Synaptic Package for Knoppix 6.7.1?



knoppix@Microknoppix:~$ lspci -vnn | grep 14e4
06:02.0 Network controller [0280]: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g
Wireless LAN Controller [14e4:4318] (rev 02)
http://wiki.debian.org/bcm43xx

http://linuxwireless.org/en/users/Drivers/b43

THX
luther
:confused:

[luther]

Hi,
KK posted on Thread 29775, “The wl drivers are here . . .
If you have the debian-knoppix repository in your /etc/apt /sources.list”

What is the actual debian-knoppix repository URL that I should find in sources,
that KK is referring to?

Trying to get the modules downloaded and installed:


sudo apt-get install broadcom-sta-modules-3.2.4
Shows Broken Packages:


sudo apt-get install broadcom-sta-modules-3.2.4
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed.
This may mean that you have requested an
impossible situation or if you are using the
unstable distribution that some required packages
have not yet been created or been moved out of Incoming.

The following information may help to resolve the situation:
The following packages have unmet dependencies:
broadcom-sta-modules-3.2.4 : Depends: linux-modules-3.2.4
but it is not installable or linux-image-3.2.4
but it is not installable
E: Broken packages
What's UP?
luther
:confused:

[Werner P. Schulz]

I don't have wireless LAN within my testing Knoppix 6.7.1 therefore I cannot verify the installation.

But I can install by CLI-version of aptitude:
b43-fwcutter 1:015-12
firmware-b43-installer 1:015-12
broadcom-sta-modules-3.0.4

Within V6.7.1 you have the Kernel version 3.0.4; therefore you cannot install modules version 3.2.4.

Within CLI-version of aptitude use "l" (little L) to list for example "b43-"
use "v" to get versions
use "+" to select for installation
use "_" to purge installed Packages
use "g" to install

[Werner P. Schulz]

What is the actual debian-knoppix repository URL
http://debian-knoppix.alioth.debian.org/

[luther]

[QUOTE=Werner P. Schulz;126432]I don't have wireless LAN within my testing Knoppix 6.7.1 therefore I cannot verify the installation.

But I can install by CLI-version of aptitude:
b43-fwcutter 1:015-12
firmware-b43-installer 1:015-12
broadcom-sta-modules-3.0.4

/QUOTE]
Dear Werner:
With your suggestion, the b43 driver NOW shows up in Synaptic.
as being installed, thanks!

I have a Broadcom BCM4318 wifi card in the hp laptop,
and NetworkManager Applet 0.8.4 does NOT detect it.
What is the trick to bring up the NM interface and
search for signals? There is NO check box to enable
wireless in NM. What can be missing?

luther
PS. b43/NM functions w/Linux Mint.
:confused:

[luther]

http://wiki.debian.org/bcm43xx#b43_and_b43legacy
http://wiki.debian.org/bcm43xx
http://linuxwireless.org/en/users/Drivers/b43

[Werner P. Schulz]

.. and NetworkManager Applet 0.8.4 does NOT detect it.right-mouse-click to NetworkManager Applet => Edit Connections
=> Wireless => +Add
doesn't work for you?

[luther]

right-mouse-click to NetworkManager Applet => Edit Connections
=> Wireless => +Add
doesn't work for you?
Hi,
NM is setup same as MINT, that DID detect WIFI! Whether it's the LIVE DVD
or FLASH install, results are the same:



knoppix@Microknoppix:~$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
knoppix@Microknoppix:~$
Line by Line "super user" listing:


knoppix@Microknoppix:~$ su
root@Microknoppix:/home/knoppix# dmesg | more
Product: MP3-Streamer
[ 2.439657] usb 2-3: Manufacturer: Xitel
[ 2.567062] attempt to access beyond end of device
[ 2.567067] sda3: rw=0, want=66, limit=2
[ 2.567072] isofs_fill_super: bread failed, dev=sda3, iso_blknum=16, block=3
2
[ 2.575261] attempt to access beyond end of device
[ 2.575265] sda3: rw=0, want=18, limit=2
[ 2.575272] REISERFS warning (device sda3): sh-2006 read_super_block: bread
failed (dev sda3, block 8, size 1024)
[ 2.575279] attempt to access beyond end of device
[ 2.575282] sda3: rw=0, want=130, limit=2
[ 2.575286] REISERFS warning (device sda3): sh-2006 read_super_block: bread
failed (dev sda3, block 64, size 1024)
[ 2.580369] attempt to access beyond end of device
[ 2.580373] sda3: rw=0, want=4, limit=2
[ 2.580377] EXT4-fs (sda3): unable to read superblock
[ 2.586998] attempt to access beyond end of device
[ 2.587002] sda3: rw=0, want=4, limit=2
[ 2.587005] EXT3-fs (sda3): error: unable to read superblock
[ 2.593668] attempt to access beyond end of device
[ 2.593671] sda3: rw=0, want=4, limit=2
[ 2.593675] EXT2-fs (sda3): error: unable to read superblock
[ 2.607078] attempt to access beyond end of device
[ 2.607082] sda3: rw=0, want=65, limit=2
[ 2.607089] attempt to access beyond end of device
[ 2.607092] sda3: rw=0, want=257, limit=2
[ 2.607422] attempt to access beyond end of device
[ 2.607426] sda3: rw=0, want=513, limit=2
[ 2.607444] attempt to access beyond end of device
[ 2.607448] sda3: rw=0, want=68, limit=2
[ 2.607453] attempt to access beyond end of device
[ 2.607456] sda3: rw=0, want=1028, limit=2
[ 2.607461] attempt to access beyond end of device
[ 2.607464] sda3: rw=0, want=2052, limit=2
[ 2.607467] UDF-fs: No partition found (1)
[ 5.411576] UDF-fs: No partition found (1)
[ 5.549935] UDF-fs: No partition found (1)
[ 6.043712] attempt to access beyond end of device
[ 6.043717] sda3: rw=0, want=66, limit=2
[ 6.043722] isofs_fill_super: bread failed, dev=sda3, iso_blknum=16, block=3
2
[ 6.051861] attempt to access beyond end of device
[ 6.051866] sda3: rw=0, want=18, limit=2
[ 6.051873] REISERFS warning (device sda3): sh-2006 read_super_block: bread
failed (dev sda3, block 8, size 1024)
[ 6.051879] attempt to access beyond end of device
[ 6.051882] sda3: rw=0, want=130, limit=2
[ 6.051887] REISERFS warning (device sda3): sh-2006 read_super_block: bread
failed (dev sda3, block 64, size 1024)
[ 6.057032] attempt to access beyond end of device
[ 6.057036] sda3: rw=0, want=4, limit=2
[ 6.057040] EXT4-fs (sda3): unable to read superblock
[ 6.063674] attempt to access beyond end of device
[ 6.063677] sda3: rw=0, want=4, limit=2
[ 6.063680] EXT3-fs (sda3): error: unable to read superblock
[ 6.070330] attempt to access beyond end of device
[ 6.070333] sda3: rw=0, want=4, limit=2
[ 6.070337] EXT2-fs (sda3): error: unable to read superblock
[ 6.083764] attempt to access beyond end of device
[ 6.083769] sda3: rw=0, want=65, limit=2
[ 6.083776] attempt to access beyond end of device
[ 6.083780] sda3: rw=0, want=257, limit=2
[ 6.084160] attempt to access beyond end of device
[ 6.084164] sda3: rw=0, want=513, limit=2
[ 6.084189] attempt to access beyond end of device
[ 6.084192] sda3: rw=0, want=68, limit=2
[ 6.084198] attempt to access beyond end of device
[ 6.084201] sda3: rw=0, want=1028, limit=2
[ 6.084206] attempt to access beyond end of device
[ 6.084209] sda3: rw=0, want=2052, limit=2
[ 6.084212] UDF-fs: No partition found (1)
[ 10.899947] cloop: Can't open device read-write in mode 0x1f
[ 10.942424] cloop: losetup_file: 70648 blocks, 131072 bytes/block, largest b
lock is 131098 bytes.
[ 10.956695] ISO 9660 Extensions: RRIP_1991A
[ 16.839647] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0x8400, revis
ion 0
[ 16.863940] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 16.886609] ATI IXP AC97 controller 0000:00:14.5: PCI INT B -> GSI 17 (level
, low) -> IRQ 17
[ 16.895365] yenta_cardbus 0000:06:04.0: CardBus bridge found [103c:309b]
[ 16.895395] yenta_cardbus 0000:06:04.0: Enabling burst memory read transacti
ons
[ 16.895403] yenta_cardbus 0000:06:04.0: Using INTVAL to route CSC interrupts
to PCI
[ 16.895406] yenta_cardbus 0000:06:04.0: Routing CardBus interrupts to ISA
[ 16.895414] yenta_cardbus 0000:06:04.0: TI: mfunc 0x00a61b22, devctl 0x64
[ 16.925044] serial 0000:00:14.6: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 16.925056] serial 0000:00:14.6: PCI INT B disabled
[ 16.929267] ATI IXP MC97 controller 0000:00:14.6: PCI INT B -> GSI 17 (level
, low) -> IRQ 17
[ 16.962683] 8139cp: 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
[ 17.036734] MC'97 0 converters and GPIO not ready (0x1)
[ 17.124495] yenta_cardbus 0000:06:04.0: ISA IRQ mask 0x0cf8, PCI irq 20
[ 17.124502] yenta_cardbus 0000:06:04.0: Socket status: 30000820
[ 17.124513] yenta_cardbus 0000:06:04.0: pcmcia: parent PCI bridge window: [i
o 0xa000-0xafff]
[ 17.124519] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa000-0xafff: e
xcluding 0xa000-0xa0ff 0xa400-0xa4ff 0xa800-0xa8ff
[ 17.136696] yenta_cardbus 0000:06:04.0: pcmcia: parent PCI bridge window: [m
em 0xc0200000-0xc02fffff]
[ 17.136703] pcmcia_socket pcmcia_socket0: cs: memory probe 0xc0200000-0xc02f
ffff: excluding 0xc0200000-0xc020ffff
[ 17.136722] yenta_cardbus 0000:06:04.0: pcmcia: parent PCI bridge window: [m
em 0x40000000-0x43ffffff pref]
[ 17.136726] pcmcia_socket pcmcia_socket0: cs: memory probe 0x40000000-0x43ff
ffff: excluding 0x40000000-0x43ffffff
[ 17.137428] tifm_7xx1 0000:06:04.3: PCI INT B -> GSI 23 (level, low) -> IRQ
23
[ 17.137642] 8139cp 0000:06:06.0: This (id 10ec:8139 rev 10) is not an 8139C+
compatible chip, use 8139too
[ 17.148881] 8139too: 8139too Fast Ethernet driver 0.9.28
[ 17.148976] 8139too 0000:06:06.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 17.150202] 8139too 0000:06:06.0: eth0: RealTek RTL8139 at 0xa000, 00:0f:b0:
fa:e5:31, IRQ 22
[ 17.670229] wmi: Mapper loaded
[ 17.747857] ACPI: Deprecated procfs I/F for AC is loaded, please retry with
CONFIG_ACPI_PROCFS_POWER cleared
root@Microknoppix:/home/knoppix#

[luther]

77
why does "unable to resolve host microknoppix" get trapped?

Also, "click to prevent changes" fails to activate.

[luther]

78
PLEASE EXPLAIN THIS ERROR TRAPPED BY FLASH INSTALL:
"Ignoring unknown interface =."http://knoppix.net/forum/images/misc/pencil.png

[luther]

Hi,

Output from Mint 11 LXDE flash install:


a23@abc ~ $ sudo iwconfig
[sudo] password for ren:
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=off
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

a23@abc ~ $

Same hardware settings, different OS.
Why can't Knoppix detect wlan0?
THX
luther
PS. posted w/Mint
:confused:

[Werner P. Schulz]

No idea anymore; but you can still try
hwinfo --wlan

[luther]

No idea anymore; but you can still try
hwinfo --wlan
Dear Werner:
Hopefully the last resort does the trick:



knoppix@Microknoppix:~$ sudo hwinfo -wlan
28: PCI 602.0: 0280 Network controller
[Created at pci.318]
UDI: /org/freedesktop/Hal/devices/pci_14e4_4318
Unique ID: 2i_g.+HoqxypXtRE
Parent ID: qscc.hTSZxA6Z5F6
SysFS ID: /devices/pci0000:00/0000:00:14.4/0000:06:02.0
SysFS BusID: 0000:06:02.0
Hardware Class: network
Model: "Hewlett-Packard Company Broadcom 802.11b/g WLAN"
Vendor: pci 0x14e4 "Broadcom"
Device: pci 0x4318 "BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller"
SubVendor: pci 0x103c "Hewlett-Packard Company"
SubDevice: pci 0x1355 "Broadcom 802.11b/g WLAN"
Revision: 0x02
Memory Range: 0xc0204000-0xc0205fff (rw,non-prefetchable)
IRQ: 10 (no events)
Module Alias: "pci:v000014E4d00004318sv0000103Csd00001355bc02sc80 i00"
Driver Info #0:
Driver Status: ssb is not active
Driver Activation Cmd: "modprobe ssb"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #20 (PCI bridge)
54: SCSI 200.0: 10600 Disk
[Created at block.243]
UDI: /org/freedesktop/Hal/devices/storage_model_USB_Flash_Drive
Unique ID: ADDn.bsbRES4MQf1
Parent ID: 06bT.J4B8awCfx34
SysFS ID: /class/block/sdb
SysFS BusID: 2:0:0:0
SysFS Device Link: /devices/pci0000:00/0000:00:13.2/usb1/1-1/1-1:1.0/host2/target2:0:0/2:0:0:0
Hardware Class: disk
Model: "Lexar USB Flash Drive"
Vendor: usb 0x05dc "Lexar"
Device: usb 0xc753 "USB Flash Drive"
Revision: "8.07"
Serial ID: "20111016160715218FA3"
Driver: "usb-storage", "sd"
Driver Modules: "usb_storage"
Device File: /dev/sdb (/dev/sg2)
Device Files: /dev/sdb, /dev/disk/by-id/usb-Lexar_USB_Flash_Drive_20111016160715218FA3-0:0, /dev/disk/by-path/pci-0000:00:13.2-usb-0:1:1.0-scsi-0:0:0:0
Device Number: block 8:16-8:31 (char 21:2)
Features: Hotpluggable
Geometry (Logical): CHS 1022/247/62
Size: 15663104 sectors a 512 bytes
Speed: 480 Mbps
Module Alias: "usb:v05DCpC753d0103dc00dsc00dp00ic08isc06ip50"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #16 (USB Controller)
knoppix@Microknoppix:~$
The latest clue:


knoppix@Microknoppix:~$ sudo modprobe b43
FATAL: Module b43 not found.
knoppix@Microknoppix:~$
Yet Synaptic Package Manager reports b43 installed!
Where is it hidden (screen6.jpg)?

Thanks Werner!
luther
79

[Werner P. Schulz]

What's about
Driver Status: ssb is not active
Driver Activation Cmd: "modprobe ssb"

[utu]

Greetings, Werner & luther.

FWIW, on my machine with 6.7.1, hwinfo -wlan gives strange,
unuseful results relative to hwinfo --wlan.

On my machine, with 6.7.1, I get the following, which I do
find useful.



knoppix@Microknoppix:~$ sudo hwinfo --wlan | grep -i driver
Driver: "wl"
Driver Modules: "wl"
Driver Info #0:
Driver Status: ssb is not active
Driver Activation Cmd: "modprobe ssb"
Driver Info #1:
Driver Status: wl is active
Driver Activation Cmd: "modprobe wl"
In my case I need the wl driver, and here we see it's activated,
while ssb is neither used nor needed.

[luther]

Dear Werner and utu:

So I do a MC of b43 (Mint tried & true) and
use ssb? What is the logic? I would like to see
something in Synaptic Package Manager, etc.,
about ssb status?

file: "/etc/modprobe.d/broadcom-sta-common.conf" blacklist's
BOTH b43 and ssb:


# wl module from Broadcom conflicts with ssb
# We must blacklist the following modules:
blacklist b44
blacklist b43legacy
blacklist b43
blacklist brcm80211
blacklist brcmsmac
blacklist ssb
install wl /sbin/modprobe --ignore-install wl $CMDLINE_OPTS
Thanks for replying to my thread.
luther
PS. Good point to take a breather.
:)

[luther]

Hi,
No screen dialog was observed, other than:


knoppix@Microknoppix:~$ sudo modprobe ssb
knoppix@Microknoppix:~$
I need an interpreter to utu's tip:



knoppix@Microknoppix:~$ sudo hwinfo --wlan | grep -i driv
info.linux.driver = 'b43-pci-bridge'
E: DRIVER=b43-pci-bridge
Driver Info #1:
Driver: "b43-pci-bridge"
Driver Modules: "ssb"
Driver Info #0:
Driver Status: ssb is active
Driver Activation Cmd: "modprobe ssb"

No difference:



knoppix@Microknoppix:~$ sudo iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

knoppix@Microknoppix:~$

luther
PS. Going on Holiday!

[utu]

I think the 4318 is a special case that uses b43 not wl as the driver.
For one person's solution, see post #13 at :
http://knoppix.net/forum/threads/28605-Knoppix-and-my-wireless-adapter-problem/page2?highlight=4318

In luther's case he should probably blacklist wl & ssb.

It would be good to know for your Mint 11 install what lsmod tells us about which drivers work there.

[luther]

In luther's case he should probably blacklist wl & ssb.

It would be good to know for your Mint 11 install what lsmod tells us about which drivers work there.

Dear utu:

At your request:


#toc, .toc, .mw-warning { border: 1px solid rgb(170, 170, 170); background-color: rgb(249, 249, 249); padding: 5px; font-size: 95%; }#toc h2, .toc h2 { display: inline; border: medium none; padding: 0pt; font-size: 100%; font-weight: bold; }#toc #toctitle, .toc #toctitle, #toc .toctitle, .toc .toctitle { text-align: center; }#toc ul, .toc ul { list-style-type: none; list-style-image: none; margin-left: 0pt; padding-left: 0pt; text-align: left; }#toc ul ul, .toc ul ul { margin: 0pt 0pt 0pt 2em; }#toc .toctoggle, .toc .toctoggle { font-size: 94%; }body { font-family: 'Times New Roman'; color: rgb(0, 0, 0); widows: 2; font-style: normal; text-indent: 0in; font-variant: normal; font-weight: normal; font-size: 12pt; text-decoration: none; text-align: left; }table { }td { border-collapse: collapse; text-align: left; vertical-align: top; }p, h1, h2, h3, li { color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-size: 12pt; text-align: left; } a12@1bc ~ $ sudo lsmod

Module Size Used by

binfmt_misc 13213 1

usbhid 41704 0

hid 77084 1 usbhid

parport_pc 32111 0

ppdev 12849 0

dm_crypt 22463 0

snd_usb_audio 91410 0

snd_atiixp 19400 1

snd_atiixp_modem 18624 0

snd_ac97_codec 105614 2 snd_atiixp,snd_atiixp_modem

ac97_bus 12642 1 snd_ac97_codec

snd_pcm 80244 4 snd_atiixp,snd_atiixp_modem,snd_usb_audio,snd_ac97 _codec

snd_hwdep 13274 1 snd_usb_audio

snd_usbmidi_lib 24388 1 snd_usb_audio

arc4 12473 2

snd_seq_midi 13132 0

snd_rawmidi 25269 2 snd_usbmidi_lib,snd_seq_midi

b43 296610 0

snd_seq_midi_event 14475 1 snd_seq_midi

snd_seq 51291 2 snd_seq_midi,snd_seq_midi_event

joydev 17322 0

mac80211 257001 1 b43

hp_wmi 13418 0

snd_timer 28659 2 snd_pcm,snd_seq

pcmcia 39671 0

sparse_keymap 13666 1 hp_wmi

snd_seq_device 14110 3 snd_seq_midi,snd_rawmidi,snd_seq

cfg80211 156212 2 b43,mac80211

yenta_socket 27230 0

tifm_7xx1 12898 0

psmouse 73312 0

snd 55295 13 snd_atiixp,snd_atiixp_modem,snd_usb_audio,snd_ac97 _codec,snd_hwdep,snd_usbmidi_lib,snd_pcm,snd_rawmi di,snd_seq,snd_timer,snd_seq_device

pcmcia_rsrc 18292 1 yenta_socket

tifm_core 15040 1 tifm_7xx1

serio_raw 12990 0

k8temp 12872 0

pcmcia_core 21505 3 pcmcia,yenta_socket,pcmcia_rsrc

shpchp 32345 0

i2c_piix4 13095 0

soundcore 12600 1 snd

snd_page_alloc 14073 3 snd_atiixp,snd_atiixp_modem,snd_pcm

lp 13349 0

parport 36746 3 parport_pc,ppdev,lp

dm_raid45 88410 0

#toc, .toc, .mw-warning { border: 1px solid rgb(170, 170, 170); background-color: rgb(249, 249, 249); padding: 5px; font-size: 95%; }#toc h2, .toc h2 { display: inline; border: medium none; padding: 0pt; font-size: 100%; font-weight: bold; }#toc #toctitle, .toc #toctitle, #toc .toctitle, .toc .toctitle { text-align: center; }#toc ul, .toc ul { list-style-type: none; list-style-image: none; margin-left: 0pt; padding-left: 0pt; text-align: left; }#toc ul ul, .toc ul ul { margin: 0pt 0pt 0pt 2em; }#toc .toctoggle, .toc .toctoggle { font-size: 94%; }body { font-family: 'Times New Roman'; color: rgb(0, 0, 0); widows: 2; font-style: normal; text-indent: 0in; font-variant: normal; font-weight: normal; font-size: 12pt; text-decoration: none; text-align: left; }table { }td { border-collapse: collapse; text-align: left; vertical-align: top; }p, h1, h2, h3, li { color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-size: 12pt; text-align: left; }
xor 21860 1 dm_raid45

btrfs 527341 0

zlib_deflate 26594 1 btrfs

libcrc32c 12543 1 btrfs

radeon 896428 2

ttm 65184 1 radeon

sdhci_pci 13623 0

firewire_ohci 31504 0

drm_kms_helper 40745 1 radeon

drm 180037 4 radeon,ttm,drm_kms_helper

usb_storage 43946 2

8139too 23208 0

firewire_core 56138 1 firewire_ohci

ssb 45942 1 b43

video 18951 0

pata_atiixp 12968 0

8139cp 22497 0

sdhci 22720 1 sdhci_pci

uas 17676 0

i2c_algo_bit 13184 1 radeon

ati_agp 13202 0

crc_itu_t 12627 1 firewire_core

a12@1bc ~ $

~Mint 11~

[luther]

a23@1bc ~ $ sudo dmesg | grep b43

[ 1.603646] b43-pci-bridge 0000:06:02.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21

[ 17.642924] b43-phy0: Broadcom 4318 WLAN found (core revision 9)

[ 17.751656] Registered led device: b43-phy0::radio

a23@1bc ~ $

[luther]

1:2


a23@1bc ~ $ lsmod
Module Size Used by
usbhid 41704 0
hid 77084 1 usbhid
binfmt_misc 13213 1
parport_pc 32111 0
dm_crypt 22463 0
ppdev 12849 0
snd_usb_audio 91410 0
snd_atiixp 19400 1
arc4 12473 2
snd_atiixp_modem 18624 0
snd_hwdep 13274 1 snd_usb_audio
snd_usbmidi_lib 24388 1 snd_usb_audio
snd_ac97_codec 105614 2 snd_atiixp,snd_atiixp_modem
ac97_bus 12642 1 snd_ac97_codec
snd_pcm 80244 4 snd_usb_audio,snd_atiixp,snd_atiixp_modem,snd_ac97 _codec
snd_seq_midi 13132 0
b43 296610 0
snd_rawmidi 25269 2 snd_usbmidi_lib,snd_seq_midi
mac80211 257001 1 b43
snd_seq_midi_event 14475 1 snd_seq_midi
hp_wmi 13418 0
snd_seq 51291 2 snd_seq_midi,snd_seq_midi_event
joydev 17322 0
sparse_keymap 13666 1 hp_wmi
pcmcia 39671 0
snd_timer 28659 2 snd_pcm,snd_seq
snd_seq_device 14110 3 snd_seq_midi,snd_rawmidi,snd_seq
cfg80211 156212 2 b43,mac80211
psmouse 73312 0
tifm_7xx1 12898 0
snd 55295 13 snd_usb_audio,snd_atiixp,snd_hwdep,snd_atiixp_mode m,snd_usbmidi_lib,snd_ac97_codec,snd_pcm,snd_rawmi di,snd_seq,snd_timer,snd_seq_device
yenta_socket 27230 0
tifm_core 15040 1 tifm_7xx1
pcmcia_rsrc 18292 1 yenta_socket
serio_raw 12990 0
pcmcia_core 21505 3 pcmcia,yenta_socket,pcmcia_rsrc
k8temp 12872 0
soundcore 12600 1 snd
i2c_piix4 13095 0
snd_page_alloc 14073 3 snd_atiixp_modem,snd_atiixp,snd_pcm
shpchp 32345 0
lp 13349 0
parport 36746 3 parport_pc,ppdev,lp
dm_raid45 88410 0
xor 21860 1 dm_raid45
btrfs 527341 0
zlib_deflate 26594 1 btrfs
libcrc32c 12543 1 btrfs
radeon 896428 2
ttm 65184 1 radeon
drm_kms_helper 40745 1 radeon
firewire_ohci 31504 0
usb_storage 43946 2
drm 180037 4 radeon,ttm,drm_kms_helper
8139too 23208 0
ssb 45942 1 b43
video 18951 0
sdhci_pci 13623 0
firewire_core 56138 1 firewire_ohci
uas 17676 0
pata_atiixp 12968 1
8139cp 22497 0
i2c_algo_bit 13184 1 radeon
ati_agp 13202 0
sdhci 22720 1 sdhci_pci
crc_itu_t 12627 1 firewire_core
a23@1bc ~ $


2:2



a23@1bc ~ $ sudo dmesg | grep b43
[sudo] password for xXx:
[ 1.603646] b43-pci-bridge 0000:06:02.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 17.642924] b43-phy0: Broadcom 4318 WLAN found (core revision 9)
[ 17.751656] Registered led device: b43-phy0::radio
a23@1bc ~ $

[utu]

@ luther & Werner

luther and I seem to have complementary wifi experiences:

My laptop has a Broadcom 4315 which requires a wl driver
and blacklisting of b43 and ssb drivers. Knoppix does this
automatically; Mint makes it a chore for me to get wl installed.

luther's rig uses a Broadcom 4318 which apparently works
just fine on Mint 11 using both b43 AND ssb; this appears to
be a problem for luther and others in Knoppix.

So, at this point, I think luther may need to do the following with
his Knoppix setup:
1. remove and blacklist the wl module & un-blacklist b43 and ssb, if necessary;
2. obtain or create b43 and ssb modules, if necessary;
3. install b43 and ssb modules; and possibly,
4. update initramfs.

If all this is a correct (and necessary) description of where we are,
then we need to feed this back to Klaus K.

[luther]

Dear Knoppix Hackers:

I'm happy to beta test your distro,
but suggest KK review this stuff,
since Werner, utu and myself are
stumped:

b43 module, size 296,610 used by 0
ssb module, size 045,942 used by 1 b43

1) remove & blacklist wl module
2) un-blacklist b43 and ssb
3) obtain or create b43 & ssb modules
4) install b43 & ssb modules
5) update initramfs
~~~~~~~~~~~~
Excellent replies!
luther

[utu]

The ball still in our court to demonstrate my conjecture
or come up with something better.
Who do we know with a Broadcom 4318 that might accept this challenge?

[luther]

The ball still in our court to demonstrate my conjecture
or come up with something better.
Who do we know with a Broadcom 4318 that might accept this challenge?
Dear utu:

For starters, anyone with a hp pavilion dv8000 notebook.

Also, please enlighten me on "initramfs"?

Once I understand the theory behind your conjecture,
expect to see a posted demo.
THX
luther

[utu]

The only additional 'theory' required is described in the man pages for
modprobe (to add or remove kernel modules; also defines how blacklists work)
and update-initramfs (to do just that).

update-initramfs may only be necessary for liveusb/livecd situations, to
correct for an original initrd to include additional necessary modules
not in the original, such as missing wifi driver(s).

[luther]

@ luther & Werner

luther and I seem to have complementary wifi experiences:

My laptop has a Broadcom 4315 which requires a wl driver
and blacklisting of b43 and ssb drivers. Knoppix does this
automatically; Mint makes it a chore for me to get wl installed.

luther's rig uses a Broadcom 4318 which apparently works
just fine on Mint 11 using both b43 AND ssb; this appears to
be a problem for luther and others in Knoppix.

So, at this point, I think luther may need to do the following with
his Knoppix setup:
1. remove and blacklist the wl module & un-blacklist b43 and ssb, if necessary;
2. obtain or create b43 and ssb modules, if necessary;
3. install b43 and ssb modules; and possibly,
4. update initramfs.

If all this is a correct (and necessary) description of where we are,
then we need to feed this back to Klaus K.

Dear utu:
Is this the conf causing the problem that needs mods?
~~~~~~~~~~~~~~~~
GNU nano 2.2.4 File: /etc/modprobe.d/broadcom-sta-common.conf

# wl module from Broadcom conflicts with ssb
# We must blacklist the following modules:
blacklist b44
blacklist b43legacy
blacklist b43
blacklist brcm80211
blacklist brcmsmac
blacklist ssb
install wl /sbin/modprobe --ignore-install wl $CMDLINE_OPTS
~~~~~~~~~~~~

How would you remove and blacklist wl module?
I can think of several, that might NOT work.

Also, how would you UN-blacklist b43 and ssb?
Logic tells me a hash is all that is needed for each.

Finally, I'm sure you have updated-initramfs before.
What SYNTAX did you use?
I'd prefer to use something that is tried-and-true.

Kind Regards,
luther

[utu]

@ luther

I would sneak up on this in the following way:

1. With your Knoppix, do an lsmod just like you did for Mint.

2. See what wifi drivers are there to start with and remove them all:
as root, modprobe -r wl, then modprobe -r b43, then modprobe -r ssb
then do another lsmod to make sure they're gone.

3. Now, put back the drivers we think you need, ssb & b43:
with modprobe -a ssb and modprobe -a b43
then do another lsmod to see if ssb and b43 are there all right.

4. Find the network gui and see if things are starting to act like they do in Mint.
If you get this far successfully, then you've proved the drivers we chose are
right for the 4318.

The next question will be: does what you've done so far survive a reboot?
Probably not. Then we'll discuss blacklisting and initramfs (or some alternative).

Get back to us on your progress.

[luther]

@ luther

I would sneak up on this in the following way:

1. With your Knoppix, do an lsmod just like you did for Mint.

2. See what wifi drivers are there to start with and remove them all:
as root, modprobe -r wl, then modprobe -r b43, then modprobe -r ssb
then do another lsmod to make sure they're gone.

3. Now, put back the drivers we think you need, ssb & b43:
with modprobe -a ssb and modprobe -a b43
then do another lsmod to see if ssb and b43 are there all right.

4. Find the network gui and see if things are starting to act like they do in Mint.
If you get this far successfully, then you've proved the drivers we chose are
right for the 4318.

The next question will be: does what you've done so far survive a reboot?
Probably not. Then we'll discuss blacklisting and initramfs (or some alternative).

Get back to us on your progress.

Dear utu:
Report exceeds posting buffer, but can be found here:
www.mninter.net/~pfourier/utu_mod1.zip (http://www.mninter.net/%7Epfourier/utu_mod1.zip)

Summary:
b43 module gets installed, But where?

HTH
luther

[utu]

@ luther

Looks like ssb was a success, but not b43.

My guess is that Synaptic's fwcutter needs some 'proprietary' driver
information from which to create b43. Something available only from
Broadcom.

Hang in there, I'll google around a bit and get back to you.

[utu]

@ Luther

You have run into Catch22.
fwcutter works best if you have internet access already. You don't
This reference supposedly tells us how to proceed without internet access.

https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx#b43%20-%20No%20Internet%20access

It likely will entail a download of a file from Broadcom, which you can
do with Mint.
Then there will be some magic to work with fwcutter to liberate the
proprietary stuff.

We both need some time to read and try to understand it.
Start reading at 'Installing b43 drivers...no internet access'.

[luther]

@ luther

Looks like ssb was a success, but not b43.

My guess is that Synaptic's fwcutter needs some 'proprietary' driver
information from which to create b43. Something available only from
Broadcom.

Hang in there, I'll google around a bit and get back to you.

Dear utu:

Werner prefers using this Package Manager:

Within CLI-version of aptitude use "l" (little L) to list for example "b43-"
use "v" to get versions
use "+" to select for installation
use "_" to purge installed Packages
use "g" to install
~~~~~~~~~~~~~~~~
Why not use CLI-version of aptitude?
I'm not familiar with its SYNTAX and
can't find any CLI-version docs?
Please help!
luther
PS. Keep it simple!

[luther]

@ Luther

You have run into Catch22.
fwcutter works best if you have internet access already. You don't


Dear utu:

This is the MAIN reason to get WIFI! There are cables running down a flight of
stairs to the routers ethernet port. So knoppix 6.7.1 DVD and CD do have
internet access!

Keep the pile to a minimun, please.
luther

[utu]

Using either CLI and aptitude or Synaptic is ok with me.

I usually use Synaptic and assume it knows better than I how
to get all the dependencies squared away.

I usually defer to Werner since he knows a lot more than I do,
but we've got to be careful to keep b43 separate from STA.
I'm pretty sure STA gets you wl; and, b43 and wl just don't go
together.

I haven't finished my reading yet, but it's probably going to
end up doing a few command line things to get fwcutter and
and the Broadcom proprietary file together in some useful way.

It is too bad you don't have an external wifi like my $10 Netgear;
it lets me use fwcutter to bring in the Broadcom stuff via
Synaptic. That's how I get around this for Ubuntu-derived linuxes.
An alternative for you might be to just temporarily hook your
computer via ethernet to your router.

Back to my reading now.

[luther]

An alternative for you might be to just temporarily hook your
computer via ethernet to your router.

Back to my reading now.

Hey utu!

This computer is already wired to router via RG-45 cable,
so lets move on to the next hurdle . . .

Today, I'm using knoppix 6.7.1 LiveCD, installed to flash. I'll
shut down windows XP and reboot with the LiveUSB. In fact
I'll send you a "bounce", to make sure, next.
luther

[luther]

An alternative for you might be to just temporarily hook your
computer via ethernet to your router.

Back to my reading now.

Hey utu!
If you received this message, Knoppix 6.7.1 is ONLINE, via ethernet.
As stated in previous post, I must plug in my ISP's nameserver into:
/etc/resolv.conf

NetworkManager Applet 0.8.4 does a Master Clear of this script,
every time knoppix gets rebooted.
luther

[utu]

This computer is already wired to router via RG-45 cable,
so lets move on to the next hurdle
If so, give fwcutter another chance to do its thing.

[luther]

If so, give fwcutter another chance to do its thing.
Dear utu:
Suspect b43 is not in the PATH for modprobe, but ssb is:



knoppix@Microknoppix:~$ sudo modprobe -a ssb
knoppix@Microknoppix:~$ sudo modprobe -a b43
WARNING: Module b43 not found.
knoppix@Microknoppix:~$
It appears also that ssb gets blown out, like nameserver,
at re-boot!
Thanks for your time,
luther
PS. Still stumped.

[utu]

@ luther

If you tried to re-install both b43-fwcutter and firmware-b43-install via Synaptic,
What error message did you receive on the final 'Changes applied Details' screen?

When I try it on my unit it identifies correctly my 4315 and says 'not supported'
among other things. It says it tried to use Broadcom 4.150.10.5-4, so at least it
found the Broadcom material.

[luther]

What error message did you receive on the final 'Changes applied Details' screen?

When I try it on my unit it identifies correctly my 4315 and says 'not supported'
among other things. It says it tried to use Broadcom 4.150.10.5-4, so at least it
found the Broadcom material.

Dear utu:

Synaptic, aptitude and apt-get install b43 w/o any errors trapped.
You can see the full apt-get dialog in my earlier report, today.
Synaptic reports "successfully applied all changes", and
NO broken modules. Also, I have not installed any of the Synaptic
"missing recommends".

My question to utu, what does Synaptic say when installing b43
on your PC?

luther

[utu]

@ luther

I had thought we could postpone blacklists, but maybe not.

Your post #27 may be the problem, if that is still what you have.
That file would install wl and blacklist b43. That is the opposite of
what you want to do.

[luther]

@ luther

I had thought we could postpone blacklists, but maybe not.

Your post #27 may be the problem, if that is still what you have.
That file would install wl and blacklist b43. That is the opposite of
what you want to do.

Dear utu:

The file #27 references does not exist in Mint. Also, I just solved
many problems mentioned in this thread by replacing networkmanager
with Wicd Network Manager, yet wicd reports, "no wireless networks found".

Yours,
luther

[Werner P. Schulz]

Why not use CLI-version of aptitude?
I'm not familiar with its SYNTAX and
can't find any CLI-version docs?
Please help!Install "aptitude-doc-en"; it is the CLI-version doc.
Type
file:///usr/share/doc/aptitude/html/en/index.htmlwithin the address line of your Internet Browser to read the doc.

[utu]

@ luther & Werner

I think there may be a problem in how Debian-Knoppix handles Broadcom wifi.
There is a reference which seems authoritative by developers of the b43 driver
series which I rely on here as 'ground truth'. Find this at:
http://linuxwireless.org/en/users/Drivers/b43#Supported_devices

This reference indicates that most Broadcom wifis need either a wl driver or b43 driver,
and many may use either. None will work with both installed simultaneously. As defined
by PCI-IDs, the 4315 which I have should work with either; the 4318 which luther has
is indicated to work only with b43.

Knoppix 6.7.1 automatically sets up wl for my 4315. I think luther has a similar experience
with Mint setting his 4318 up with b43 and ssb.

I note that when I try to use Synaptic to install b43 via fwcutter, it reports
'not supported' and fails to bring in the required Broadcom firmware. I should be able to
choose from either b43 or wl according to the reference. Apparently, part of the Debian-
Knoppix process of installing wl precludes subsequently bringing in b43 material.

If luther initially tried to install the STA driver series which contains wl, then this
may explain why he cannot now bring in b43 as an alternative. There may be some residual
effect from an initial attempt at an STA/wl installation.

Part of what appears with a wl driver installation are some blacklists in /etc/modprobe.d/;
specifically, boadcom-sta-common.conf and one line of blacklist-knoppix.conf. These files
may be the culprit in attempting to do a b43 installation after a wl installation.
These files (at least) probably need to be disabled for the b43 installation to succeed.

An alternative, with Synaptic, might be to do a complete removal of the STA/wl driver before
attempting a subsequent b43 install. Werner can best describe the CLI equivalent of this.

[luther]

@ luther & Werner

I think there may be a problem in how Debian-Knoppix handles Broadcom wifi.
There is a reference which seems authoritative by developers of the b43 driver
series which I rely on here as 'ground truth'. Find this at:
http://linuxwireless.org/en/users/Drivers/b43#Supported_devices

This reference indicates that most Broadcom wifis need either a wl driver or b43 driver,
and many may use either. None will work with both installed simultaneously. As defined
by PCI-IDs, the 4315 which I have should work with either; the 4318 which luther has
is indicated to work only with b43.

Knoppix 6.7.1 automatically sets up wl for my 4315. I think luther has a similar experience
with Mint setting his 4318 up with b43 and ssb.

I note that when I try to use Synaptic to install b43 via fwcutter, it reports
'not supported' and fails to bring in the required Broadcom firmware. I should be able to
choose from either b43 or wl according to the reference. Apparently, part of the Debian-
Knoppix process of installing wl precludes subsequently bringing in b43 material.

If luther initially tried to install the STA driver series which contains wl, then this
may explain why he cannot now bring in b43 as an alternative. There may be some residual
effect from an initial attempt at an STA/wl installation.

Part of what appears with a wl driver installation are some blacklists in /etc/modprobe.d/;
specifically, boadcom-sta-common.conf and one line of blacklist-knoppix.conf. These files
may be the culprit in attempting to do a b43 installation after a wl installation.
These files (at least) probably need to be disabled for the b43 installation to succeed.

An alternative, with Synaptic, might be to do a complete removal of the STA/wl driver before
attempting a subsequent b43 install. Werner can best describe the CLI equivalent of this.

Dear Knoppix Hackers:
I concur these findings by utu have merit. If I do a Synaptic "broadcom" search in Mint, nothing related
to it are installed, except "b43". Applying this same indexing to Knoppix, indicates numerous broadcom
modules installed, suspecting buss contention w/b43.
luther

[luther]

[QUOTE=Werner P. Schulz;126408]
Try
uname -aHi,
As requested:



knoppix@Microknoppix:~$ sudo uname -a
Linux Microknoppix 3.0.4 #12 SMP PREEMPT Thu Sep 8 05:27:05 CEST 2011 i686 GNU/Linux
knoppix@Microknoppix:~$

[luther]

Hi,
Please explain this failure trapped by Wicd:



knoppix@Microknoppix:~$ sudo wicd-cli -y -l
rename failed
# BSSID Channel ESSID
knoppix@Microknoppix:~$

[luther]

8081828384

[luther]

9091929394

[luther]

Hi,
Synaptic Package Manager shows b43 installed, BUT Modprobe can't find it:



knoppix@Microknoppix:~$ sudo modinfo ssb
filename: /lib/modules/3.0.4/kernel/drivers/ssb/ssb.ko
license: GPL
description: Sonics Silicon Backplane driver
alias: pci:v000014E4d0000432Bsv*sd*bc*sc*i*
alias: pci:v000014E4d00004329sv*sd*bc*sc*i*
alias: pci:v000014E4d00004328sv*sd*bc*sc*i*
alias: pci:v000014E4d00004325sv*sd*bc*sc*i*
alias: pci:v000014E4d00004324sv*sd*bc*sc*i*
alias: pci:v000014E4d00004321sv*sd*bc*sc*i*
alias: pci:v000014E4d00004320sv*sd*bc*sc*i*
alias: pci:v000014E4d00004319sv*sd*bc*sc*i*
alias: pci:v000014A4d00004318sv*sd*bc*sc*i*
alias: pci:v000014E4d00004318sv*sd*bc*sc*i*
alias: pci:v000014E4d00004315sv*sd*bc*sc*i*
alias: pci:v000014E4d00004312sv*sd*bc*sc*i*
alias: pci:v000014E4d00004311sv*sd*bc*sc*i*
alias: pci:v000014E4d00004307sv*sd*bc*sc*i*
alias: pci:v000014E4d00004306sv*sd*bc*sc*i*
alias: pci:v000014E4d00004301sv*sd*bc*sc*i*
depends: pcmcia
vermagic: 3.0.4 SMP preempt mod_unload modversions 486
knoppix@Microknoppix:~$ sudo modinfo b43
ERROR: modinfo: could not find module b43
knoppix@Microknoppix:~$ sudo modprobe ssb
knoppix@Microknoppix:~$ sudo modprobe b43
FATAL: Module b43 not found.
knoppix@Microknoppix:~$


9596

END OF BETA TEST:)

[utu]

@ luther

The b43 maintainers are not likely at fault here.
Your demonstration of the b43 problem is fine. BUT,
what we need now is something better than a theory
on where things are going wrong in Debian-Knoppix.

We need a demonstration that shows how one might actually
get b43 installed correctly in Knoppix 6.7.1.

There are several possibilities:
1. on a fresh Knoppix 6.7.1 try installing b43 first, not wl;
2. on a 6.7.1 that has been corrupted with blacklists,
remove these and show that things clear up (if they do);
3. as an alternative to 2, if the initial wl install was via
Synaptic, do a complete uninstall of wl then bring in b43; or
4. show in the Debian-Knoppix computer code
where things need to be changed.

Possibly one of the first three would be adequate to
demonstrate the theory. We need a demonstration to
motivate someone with the talent to discuss the fourth.

[luther]

We need a demonstration that shows how one might actually
get b43 installed correctly in Knoppix 6.7.1.

There are several possibilities:
1. on a fresh Knoppix 6.7.1 try installing b43 first, not wl;

utu,
I would start here at #1 and eliminate the install to flash, done previously.
Please call the shots, since both LiveCD and LiveDVD versions are at my disposal.
Ball in your court.
luther

[luther]

No difference than flash install:



knoppix@Microknoppix:~$ sudo lsmod
Module Size Used by
ipv6 204834 10
parport_pc 24471 0
ppdev 4123 0
lp 6082 0
parport 21550 3 parport_pc,ppdev,lp
radeon 568836 2
ttm 37284 1 radeon
drm_kms_helper 17759 1 radeon
snd_usb_audio 61725 0
snd_hwdep 3967 1 snd_usb_audio
snd_usbmidi_lib 12457 1 snd_usb_audio
snd_seq_midi 3208 0
snd_rawmidi 12490 2 snd_usbmidi_lib,snd_seq_midi
hp_wmi 5737 0
sparse_keymap 1996 1 hp_wmi
battery 8245 0
ac 2369 0
wmi 5883 1 hp_wmi
snd_atiixp_modem 6702 0
8250_pci 19757 0
tifm_7xx1 3135 0
snd_atiixp 9174 1
snd_ac97_codec 77917 2 snd_atiixp_modem,snd_atiixp
8139too 14660 0
8139cp 12870 0
pcmcia 24796 0
8250 15664 1 8250_pci
tifm_core 3285 1 tifm_7xx1
mii 2799 2 8139too,8139cp
i2c_piix4 6596 0
k8temp 2423 0
serial_core 12138 1 8250
yenta_socket 15538 0
ac97_bus 742 1 snd_ac97_codec
joydev 6662 0
knoppix@Microknoppix:~$ sudo modprobe -r wl
FATAL: Module wl not found.
knoppix@Microknoppix:~$ sudo modprobe -r b43
FATAL: Module b43 not found.
knoppix@Microknoppix:~$ sudo modprobe -r ssb
knoppix@Microknoppix:~$ sudo modprobe -a ssb
knoppix@Microknoppix:~$ sudo modprobe -a b43
WARNING: Module b43 not found.
knoppix@Microknoppix:~$


utu, suggest jumping to phase IV:
4. show in the Debian-Knoppix computer code
where things need to be changed.
HTH
luther
PS. I'm not a linux programmer.

[Werner P. Schulz]

I would start here at #1 and eliminate the install to flash,That's a good idea!

But please start a new thread, never again refer to this thread and omit all experiences with Mint.

In the meantime this thread is so confusing; therefore nobody seems to be able to help you at this point.

[utu]

@ Werner, most respectfully.

I agree with your observation & suggestion in Post #65,
however, I think luther's Mint experience was and is an essential clue
in this instance.

I hope we don't become so insular on this forum that we cannot
comment on relevant differences amongst the distributions, so long
as we don't allow this to excuse childish flaming exchanges.

My experience with the Mint LXDE forum leads me to believe that they feel
the same way as I do.

Best regards
-utu

[luther]

@ luther


Your demonstration of the b43 problem is fine.


Thanks Werner and utu for allowing me to cut-my-teeth in the OPEN Source
Linux Real-World.
Respectfully,
luther
PS. There are NO stupid questions, only answers.
:D

[Werner P. Schulz]

.. however, I think luther's Mint experience was and is an essential clue
in this instance.Yes, of course, and I didn't try to moderate the thread (except formatting two postings). But I think it is advantageous to look for a solution with the tools of Knoppix alone and the suggestions within this thread (consider the kernel version, examine for really needed module, blacklist etc). A new flash installation is a good starting point without disturbance by trial and error installations.

.. most respectfully .. What's about this? Here we are not in a courtroom :-)

[utu]

never again refer
This seemed a little over the top to me.
;D

[Werner P. Schulz]

But please start a new thread, never again refer to this thread and omit all experiences with Mint.It was a request, not a order! New attempt, new results, new reports.

And now I think it's time to bury this thread.

[luther]

Summary:

1) removed networkmanager

2) installed wicd

:D