[leaf-user] Agere Wireless LAN driver for uClibc
Hi everybody, I have a miniPCI WLAN card for my Soekris net4801 with an Agere Systems chip. This card seems to emulate a PCMCIA slot and the standard orinoco.o driver that comes with Bering uClibc gives the folowing error (when using the pcmcia_orinoco.lrp package): Linux PCMCIA Card Services 3.2.7 kernel build: 2.4.24 unknown options: [pci] [cardbus] [apm] Intel ISA/PCI/CardBus PCIC probe: TI 1410 rev 01 PCI-to-CardBus at slot 00:0e, mem 0xa0003000 host opts [0]: [isa irq] [pci irq 11] [lat 63/63] [bus 1/1] ISA irqs (scanned) = none!6PCI card interrupts, polling interval = 1000 ms cs: memory probe 0xa000-0xa0ff: excluding 0xa000-0xa00f orinoco.c 0.13e (David Gibson [EMAIL PROTECTED] and others) orinoco_cs.c 0.13e (David Gibson [EMAIL PROTECTED] and others) cs: IO port probe 0x0100-0x04ff: excluding 0x158-0x15f 0x480-0x48f 0x4d0-0x4d7 cs: IO port probe 0x0800-0x08ff: clean. cs: IO port probe 0x0c00-0x0cff: clean. eth3: Error -2 reading firmware info. Wildly guessing capabilities... eth3: Station identity ::: eth3: Looks like an Intersil firmware version 0.0.0 eth3: Intersil firmware earlier than v0.8.x - several features not supported eth3: Ad-hoc demo mode supported eth3: failed to read MAC address! orinoco_cs: register_netdev() failed The problem is (I think) that the card isn't really compatible with the orinoco driver (its a HermesII chip). Agere Systems has an opensource driver available from their website (http://www.agere.com/support/drivers/index.html). I was wondering if anybody had compiled this driver against uClibc for Bering uClibc? I don't have any experience in compiling packages for uClibc and don't really want to get into that if I don't have to. Hope somebody can help me, Sven van Heel --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
[leaf-user] Re: uClibc hdsupp: syslinux error; plus doco errors
Scott Merrill wrote: Using the latest Bering-uClibc 2.2rc4, Im following the Bering instructions for setting up LEAF/Bering(-uClibc) to boot from an M-Systems DiskOnChip: http://leaf.sourceforge.net/doc/guide/budiskonchip.html [T]he doc2000.o module now requires the following three modules to be loaded _first_: nand_ids.o nand_ecc.o nand.o Robert Sprockeels: [turns out it was a bad DiskOnChip device] I too am having problems with 2.2b4 and an M-Systems DiskOnChip. The machine it's on has been unused for over a year, but booted fine with the older pre-uClib Bering software yesterday, so I think the DiskOnChip is not bad. However, the tools in hdsupp.lrp aren't working well for me. I first tried running syslinux on /dev/nftla1, and it never exited. It didn't print errors, and could be killed with ctrl-d, but once run never returned to the command line. I then tried to repartition the disk using 'fdisk /dev/nftla'. All was well until I tried to commit my changes, at which point the app printed 'Calling ioctl() to re-read partition table' and then did nothing: no exit, no response to keys (including ctrl-d and ctrl-c). On rebooting, I found that my changes appeared to have been saved, and so ran fdisk again, changed the partition type to 83, and committed successfully. But when I changed it back to fat12 and attempted to commit the same thing happened: fdisk won't exit. As an aside, once fdisk is refusing to exit shutdown doesn't do anything. The only way to reboot is to power-cycle. I'd guess that there's something wrong with fat12 support in the hdsupp package. Any ideas or suggestions? Thanks, --Eric -- ** * From the desktop of: Eric House, [EMAIL PROTECTED]* *Crosswords 4.0.6 for PocketPC is out!: http://xwords.sourceforge.net * ** --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
re: [leaf-user] DiskOnChip issues (was uClibc hdsupp: syslinux error)
On Monday 28 June 2004 09:49 am, Eric House wrote: I then tried to repartition the disk using 'fdisk /dev/nftla'. All was well until I tried to commit my changes, at which point the app printed 'Calling ioctl() to re-read partition table' and then did nothing: no exit, no response to keys (including ctrl-d and ctrl-c). On rebooting, I found that my changes appeared to have been saved, and so ran fdisk again, changed the partition type to 83, and committed successfully. But when I changed it back to fat12 and attempted to commit the same thing happened: fdisk won't exit. snip I'd guess that there's something wrong with fat12 support in the hdsupp package. Any ideas or suggestions? I experienced new weirdness with my DiskOnChip system last night, too, while tweaking my Shorewall and DNSmasq configurations. _Sometimes_ I could backup the changes to the DoC, and _sometimes_ the backup process would hang. The same symptoms occured when manually unmounting the DoC after manually mounting it: sometimes it would unmount properly, and sometimes it would just hang. I cycled power several times, and tried to determine any consistency in the problem. It _felt_ like quickly doing things with the DoC was the problem (ie: copy an LRP package to the DoC and then immediately unmount the partition, or use lrcfg to backup several packages in quick succession), but I don't think that's correct because _sometimes_ I was able to quickly commit several backups in a row; and _sometimes_ I was able to copy an LRP to the DoC and then immediately unmount it. When rebooting, I did notice that the DoC partition sometimes reported empty sectors which were formatted, or incorrect sectors which were skipped. These were (almost?) always after rebooting due to a failed unmount operation after a write operation to the DoC. I'll be happy to troubleshoot this, if someone can give me some suggestions on what to try. Thanks! Scott --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] uClibc 2.2.0b4 RFE^2 - Enhanced support for dropbear's login banner
How about a super-sized RFE? Basically, it might be a GoodThing to have some default banner for the dropbear service which states that'unauthorized access is prohibited', etc. This would, by default, provide some foundation upon which criminal charges could be brought against someone attempting to infiltrate one's LEAF router (possibly difficult or impossible if there is no clear warning about unauthorized access) or simply act as a deterrant. It would also make an example of how the banner must be a filename and would assist those who wish to employ/change such a banner. To effect this for myself I made the following changes: - created file /etc/dropbear.banner which contains: This router is private property. Authorized access ONLY! All others may be prosecuted. - added a line to /var/lib/lrpkg/dropbear.conf /etc/dropbear.bannerEdit the login banner - and added a line to /var/lib/lrpkg/dropbear.list etc/dropbear.banner Thanks for LEAF! scott; canada --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
