[opensuse-factory] D-Link DWL 520+ support
In 10.0 there's an update available on the update servers, a script that installs the acx100 firmware for Texas Instruments chipset used in DWL520+. This works fine, the card works without any problems. If I update to 10.2 the card does not work anymore. This script is no more available. If I make a fresh install of 10.2 the card is not even found. Is there a workaround I could try to a) keep my existing card in update (otherwise the update works fine) b) get the firmware to work when I copy it to the same place in a fresh install? Does the firmware (or kernel or something) need some "installing" or is it just to copy the firmware? It looks like the script just fetched the drivers and put the firmware there. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Vahis wrote:
In 10.0 there's an update available on the update servers, a script that installs the acx100 firmware for Texas Instruments chipset used in DWL520+.
This works fine, the card works without any problems.
If I update to 10.2 the card does not work anymore. This script is no more available.
If I make a fresh install of 10.2 the card is not even found.
Is there a workaround I could try to
a) keep my existing card in update (otherwise the update works fine)
b) get the firmware to work when I copy it to the same place in a fresh install?
Does the firmware (or kernel or something) need some "installing" or is it just to copy the firmware? It looks like the script just fetched the drivers and put the firmware there. ---------------------------------------------------------------------
-rw-r--r-- 1 root root 83320 2006-10-05 12:59 /lib/firmware/tiacx111c16 The firmware can be downloaded from the link on site http://acx100.sourceforge.net/wiki/Firmware Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Gentle reader, I've installed openSUSE factory on three different platforms: 1. a three-disk Asrock based workstation, update from 10.2 beta, intallation on an exclusive disk, boot image selection by BIOS - worked like a charm. I could select LILO and everything is fine ;-))) 2. a ECS 320 (Yakumo Green 320) notebook, update from 10.0, worked flawlessly except the boot loader (GRUB doesn't work(tm)). After manually switching to LILO by the system repair function, choosing automatically conversion of existing configuration, it worked. Except that in the automatically generated lilo.conf the image tags were missing, they had to be inserted manually. The hidden splash screen, meant as easter egg, (running penguins) appears sometimes and will lock the boot process (no running penguins, nothing to be selected, CTRL-ALT-DEL doesn't work). 3. a three disk Asustec based Server with soft raid 1, update from 10.1, was really time consuming. The automatic upgrade preserved the LILO boot loader (this is really good, thanks to GRUB doesn't work (tm), but it made an additional md device out of the partitions dedicated for /boot , beeing unable to mount them under /boot and mangling their content. The layout is /dev/hdb1 - /dev/hdc1 - DOS /dev/hdb2 - /dev/hdc2 - /boot, ext2 /dev/hdb3 - /dev/hdc3 - extended /dev/hdb5 - /dev/hdc5 - RAID 1, reiserfs /dev/hdb6 - /dev/hdc6 - swap By the way, where does /boot/message come from? It's not in the RPM data base! The hidden splash screen, meant as easter egg, (running penguins) appears sometimes and will lock the boot process (no running penguins, nothing to be selected, CTRL-ALT-DEL doesn't work). Please, please, while performing an update, doen't make an automatic conversion to GRUB with an existing (and reliably working!) LILO configuration. This will inevitably break the system. Give the installer the chance to select "automatic conversion of boot loader (at Your own risk)" or "preserve old, existing, reliable, really working boot loader". Yours sincerly Christoph-Erdmann Pfeiler --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sunday 17 December 2006 04:16, Christoph-Erdmann Pfeiler wrote:
Gentle reader,
Christoph, The factory is work in progress and it can be broken in much worse ways than you described. Your comments, as detailed as they are, probably fit the best as bug reports in http://bugzill.novell.com in case that nobody reported them. Here they help a little if some of developers see them, otherwise not. I know that reporting bugs is not easy as one has to search trough existing reports before files own bugs, but that is the most reliable way to get things fixed. For instance problem with GRUB-LILO is just good example. GRUB is superior, the only problem is conversion of configuration. -- Regards, Rajko. http://en.opensuse.org/MiniSUSE http://en.opensuse.org/Portal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Rajko M. <rmatov101@charter.net> [2006-12-17 04:12]:
The factory is work in progress and it can be broken in much worse ways than you described.
Not just factory. 10.2 will not install on boards that use the Intel 965 and JMicron chipset for PATA. This is a large fraction of the new boards that support the fastest CPU (Core 2 Duo) on the market. The problem was independently reported several times, and yet (apparently) was never fixed in spite of a "Resolved" status in more than one bug report. I recently posted a history of the problem here, hoping to get advice on how to proceed to get this showstopper -- which has been assigned a very low "normal P5" priority -- fixed. Not for me, as I was able to get past the bug by installing a SCSI optical drive, but for the trusting people who buy the boxed product expecting it to install on common recent hardware, and discover that it won't install.
I know that reporting bugs is not easy as one has to search trough existing reports before files own bugs, but that is the most reliable way to get things fixed.
I spent hours searching prior bug reports and linking separate reports about what appeared to be a single bug. To avoid cluttering the bug reports I emailed the person who has been assigned the bug. I also posted here, following the recommended procedure when one is unsure. http://en.opensuse.org/Submitting_Bug_Reports "Before reporting a bug, make sure that it is really a bug. If in doubt, discuss it on the mailing lists first (opensuse-factory or opensuse)." There was no response from the person currently assigned to the bug nor to my post(s) here. The bug is: https://bugzilla.novell.com/show_bug.cgi?id=227505 It's a showstopper on many of the motherboards that support the Core 2 Duo processor. It's NOT new, and was repeatedly reported earlier. -rex --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sunday 17 December 2006 07:47, rex wrote:
Rajko M. <rmatov101@charter.net> [2006-12-17 04:12]:
The factory is work in progress and it can be broken in much worse ways than you described.
Not just factory. 10.2 will not install on boards that use the Intel 965 and JMicron chipset for PATA. This is a large fraction of the new boards ..... There was no response from the person currently assigned to the bug nor to my post(s) here.
The bug is:
https://bugzilla.novell.com/show_bug.cgi?id=227505
It's a showstopper on many of the motherboards that support the Core 2 Duo processor. It's NOT new, and was repeatedly reported earlier.
-rex
I see. That part of installation is probably the fastest changing and the most complex. It is not easy to keep up. You need hardware to test, you have to look in miscellaneous drivers how they communicate and when hardware vendor comes up with few new bytes it brakes present solution. How complex are issues of hardware configuration I've seen many times. In case of your bug report the hardware is new and they will fix it, but right now it is not top priority as release is already out. No one can do anything for the installer that is on a CD before 10.3. They will focus on issues that are fixable trough online updates. -- Regards, Rajko. http://en.opensuse.org/MiniSUSE http://en.opensuse.org/Portal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (5)
-
Christoph-Erdmann Pfeiler -
Rajko M. -
rex -
Sid Boyce -
Vahis