Anything better than ndiswrapper for Broadcom wireless card?
by Erik Hemdal
I fear this is an all-too-common question, but I want to verify if there's a better answer among the Fedora best.
I have a Dell TrueMobile 1450 MiniPCI card to configure for FC1. Inside, it's a Broadcom BCM94309 chipset, which Broadcom claims is their "reference implementation" for an 802.11a/b/c wireless interface. Broadcom doesn't sell it direct, so they don't provide any drivers (same deal for all their wireless devices).
I've found a reference on Google that suggests I'm stuck using ndiswrapper with the Windows driver, but it's an older reference to the BCM4301 chipset. Couldn't find any references on the Fedora archive nor the Red Hat 'broadcom-list' archive for my hardware.
Am I stuck with ndiswrapper, or are there better alternatives? Thanks for any help. Erik
19 years, 6 months
Bad SATA (Sil 3112A) performance with kernel 2.6.8
by Andrey Andreev
Hi,
I upgraded my 2.6.6 kernel to 2.6.8 (the fedora update). I run a SATA
drive on a Sil 3112A controller. I quickly noticed that the SATA drive
was no longer visible under /dev/hde, but under /dev/sda, fixed my
fstab, etc.
However, as Sil 3112 has had very varied performance with different
kernels, and there obviously was a change in the way it worked, I ran:
[andrei@brie andrei]$ sudo /sbin/hdparm -t -T /dev/sda
/dev/sda:
Timing buffer-cache reads: 1564 MB in 2.00 seconds = 780.95 MB/sec
Timing buffered disk reads: 44 MB in 3.12 seconds = 14.11 MB/sec
Which is pretty awfuly slow, compared to 2.6.6 (over 50 MB/sec).
Otherwise, I can spot no other errors or problems with it.
Any pointers as to what I should change? Is this a common result with
that controller?
See the relevant dmesg part
8<--------------------------------------->8
SCSI subsystem initialized
libata version 1.02 loaded.
sata_sil version 0.54
ACPI: PCI interrupt 0000:01:0c.0[A] -> GSI 11 (level, low) -> IRQ 11
ata1: SATA max UDMA/100 cmd 0x2285D080 ctl 0x2285D08A bmdma 0x2285D000
irq 11
ata2: SATA max UDMA/100 cmd 0x2285D0C0 ctl 0x2285D0CA bmdma 0x2285D008
irq 11
ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003
88:207f
ata1: dev 0 ATA, max UDMA/133, 312581808 sectors: lba48
ata1(0): applying Seagate errata fix
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: no device found (phy stat 00000000)
scsi1 : sata_sil
Vendor: ATA Model: ST3160023AS Rev: 3.18
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
8<--------------------------------------->8
TIA,
//Andro
19 years, 6 months
Corrupted display when booting without external monitor
by Martijn Bronkhorst
Dear Mailinglist,
I have installed Fedora Core 2 and when I boot, I get my screen all 'torn
apart'. Fedora correctly recognized my videocard (ATI mobility 128mb) and I
have manually selected my display (Dell 104 x 768 Laptop LCD).
The funny thing is, when there is an external monitor connected and you
press the FN key to select to output on both displays .. The screen is
perfect on the laptop. When I boot without an external monitor connected,
the screen is unreadable again.
Can you advise me on what to do, where to look ????
Thnx.
Martijn Bronkhorst
19 years, 6 months
Devlabel and Fstab with usb pendrive
by Darragh Bailey
Been having this problem for a while now.
Used devlabel to deal with a previous problem that depending on whether my
printer was switched on or not would affect which device my usb pendrive was
picked up as. devlabel allowed me to use a symlink to the device which it would
create and delete when the device was added removed, which meant that I could
use a consistent device name in my /etc/fstab file. This allowed me to set it
up so that any user could mount/unmount my pendrive.
my /etc/fstab file has the following entry for this device.
/dev/usb-pendrive /mnt/usb-pendrive vfat
noauto,owner,kudzu,users,noatime,gid=100,umask=002 0 0
The problem is that when updfstab is run I get the following message
cannot stat /dev/usb-pendrive: No such file or directory
which is not supprising really, since unless the pendrive is actually connected
to the machine the device entry isn't going to exist since devlabel will delete
it.
The possible solutions I can see are:
Get updfstab to ignore the entries in /etc/fstab that depend on entries that
may not exist
Get devlabel to not delete the symlink when the device is removed and instead
point it to a non used dev that will not be used by a device (/dev/null comes
to mind, but I'm sure there are others).
I can't seem to work out how to do either of the above or locate any entries on
the internet that cover the same problem.
Or is all just a case that I've added the usb pendrive incorrectly and I should
be adding it so that devlabel and updfstab will create the desired /etc/fstab
entry for me when the pendrive is plugged into the PC?
--
Darragh
"Nothing's foolproof to a sufficently talented fool"
19 years, 7 months
Dell Latitude D600 touchpad problem
by mikko nuotio
I have Dell Latitude D600, 512MB/1.4 GHz/ATI Radeon 9000/Alps GlidePoint
(might be only sold in EU). The problem is I _really_ dislike Alps
GlidePoint (dual, pad and stick) tapping feature.
I am using Fedora core 1 (yarrow) with default Xfree86 shipped with it,
and kernel 2.4.22-2135
I want to disable tapping from both stick and pad (or disable the pad)
I have tried almost every possible way to disable it(I have read most of
tuxmobile stuff for D600).
tpconfig - I disable gpm, boot to runlevel 3 run manually "tpconfig
--tapmode=0" it says ALPS tapping OFF, but when I start X tapping is
still there, even using any existing mouse driver (PS/2, Alps).
Does "tpconfig --tapmode=0" only affect on stick ?
I also try synaptics touchpad driver for xfree86 (I had to compile it).
but xfree will crash if driver not even loaded, only copied to
/usr/X11R6/lib/modules/input (not 100% sure) at least it will crash is
it is loaded.
So I read more documentation and found out that when using synaptics
driver with Alps glidepoint I should have 2.6 kernel to get events from
this device.
So is there any way disable Alps tapping with current kernel
(2.4.22-2135)?
19 years, 7 months
apache (httpd) on FC1/i386 vs FC2/x86_64: 3-8 times as much memory consumption?
by Axel Thimm
Hi,
I recently moved a httpd mirror from i386 to x86_64 hardware. All but
the memory capacity were scaled up (100MBit to 1GBit, Athlon to
Opteron etc.).
The old server is running FC1/i386 and the new one got
FC2/x86_64. Although both distros have httpd in the same upstream
version (2.0.50) the memory footage is quite different, and leads to
the striking of the oom-killer on the new server:
old (FC1/i386):
root 3329 0.0 0.2 26900 2408 ? S Aug29 0:01 /usr/sbin/httpd
apache 32746 0.0 0.5 28388 5984 ? S 06:01 0:03 \_ /usr/sbin/httpd
apache 6206 0.0 0.5 28320 5968 ? S 09:31 0:02 \_ /usr/sbin/httpd
apache 8185 0.0 0.5 28452 6080 ? S 10:09 0:04 \_ /usr/sbin/httpd
apache 10293 0.0 0.5 28452 6056 ? S 11:07 0:03 \_ /usr/sbin/httpd
apache 10378 0.0 0.5 28396 5984 ? S 11:09 0:03 \_ /usr/sbin/httpd
[...]
new (FC2/x86_64):
root 2177 0.0 1.5 189664 15556 ? S Aug30 0:00 /usr/sbin/httpd
apache 2273 0.0 1.7 193076 17984 ? S Aug30 0:03 \_ /usr/sbin/httpd
apache 2282 0.0 1.7 193052 17996 ? S Aug30 0:04 \_ /usr/sbin/httpd
apache 3125 0.0 1.7 193052 17992 ? S Aug30 0:03 \_ /usr/sbin/httpd
apache 3993 0.0 1.7 193052 18060 ? S 01:27 0:03 \_ /usr/sbin/httpd
apache 3994 0.0 1.7 193052 17976 ? S 01:27 0:02 \_ /usr/sbin/httpd
apache 7193 0.0 1.7 193052 17992 ? S 05:01 0:02 \_ /usr/sbin/httpd
Is this normal for i386 -> x86_64? Anyone running httpd on x86_64 to
compare numbers?
Thanks!
--
Axel.Thimm at ATrpms.net
19 years, 7 months
Alsa mixer settings do not appear to be initialized.
by Sam Varshavchik
I see that /etc/init.d/halt runs alsactl store to save the current mixer
settings.
I cannot find anywhere in initscript which restores the saved mixer settings
when booting. Looks like a bug.
19 years, 7 months
TI83+ calculator USB cable and linux...
by Andrew Konosky
Anyone successfully been able to use the link cable to put programs on
your calculator? I've looked around online, but I can't find anything
that works. I found the tidev debian package, but no source tarball, and
I have no idea how to actually send files to the device. Would I mount
it in fstab? Most of the stuff I found with a google search is really
outdated (2.0-2.2 kernel, or website hasnt been updated since 2002....).
Are there current projects working on this? Is there any GUI based
equivalent of thew windows software?
19 years, 7 months
scsi error - 2.6.x
by Tim Fenn
I receive the following error message when trying to either boot to
kernel-2.6.6-1.435.2.3 or using the FC2 install DVD (kernel 2.6.5, I
think?):
SCSI subsystem initialized
Loading sd_mod.ko module
Loading scsi_transport_spi.ko module
Loading sym53c8xx.ko module
sym0: <1010-33> rev 0x1 at pci 0000:00:08.0 irq 193
sym0: using 64 bit DMA addressing
sym0: Symbois NVRAM, ID7, Fast-80, LVD, parity checking
sym0: open drain IRQ line driver, using on-chip SRAM
sym0: using LOAD/STORE-based firmware
sym0: handling phase mismatch from SCRIPTS
sym0: SCSI BUS has been reset
scsi0: sym-2.1.18j
Vendor: QUANTUM Model: ATLAS_V_18_WLS Rev: 0230
Type: Direct-Access ANSI SCSI revision: 03
sym0:6:0: tagged command queuing enabled, command queue depth 16.
scsi(0:0:6:0): Beginning Domain Validation
sym0:6: wide asynchronous
sym0:6:0: ABORT operation started
sym0:6:0: ABORT operation timed-out
sym0:6:0: DEVICE RESET operation started
sym0:6:0: DEVICE RESET operation timed-out
sym0:6:0: BUS RESET operation started
sym0: SCSI BUS reset detected
sym0: SCSI BUS has been reset
sym0:6:0: BUS RESET operation complete
sym0:6:0: ABORT operation started
sym0:6:0: ABORT operation timed-out
sym0:6:0: HOST RESET operation started
sym0: SCSI BUS has been reset
<hangs here>
I've tried to make sure everything is terminated properly, using both
"auto" scsi termination as well as manual termination. No change.
This problem does not occur with FC1 (2.4 kernel), and I have seen
other reports of this type to the LKML related to SCSI with 2.6:
http://lkml.org/lkml/2004/6/5/2
and here:
http://ronmon.shacknet.nu/configs/scsi_boot_error
but no clear solution to the problem is given. Is there a
fix/workaround for this, other than "stick with 2.4"?
Regards,
Tim
19 years, 7 months
