Subject: Re: problem on getting CUPS to print - msg#00708

Previous Message by Date: click to view message preview

Re: Native Toolchain

if you have the native toolchain, this is probably what you want to look at: http://www.nslu2-linux.org/wiki/Unslung/AddAPackageToUnslung But that is differnt than what you want to do. you need to get a openembedded environment working to build the unslung kernel http://www.nslu2-linux.org/wiki/OpenEmbedded/HomePage I suggest you read more about the terms you mentioned below, they are all related. bitbake is the tool to build stuff based on openembedded metadata. openslug is a kernel-2.6 based oe distro for the nslu2. All of this is documented. --- In nslu2-linux-hHKSG33TihhbjbujkaE4pw@xxxxxxxxxxxxxxxx, Geert Janssen <geertleon@xxxx> wrote: > Dear Sluggers, > > I am interested in compiling on the nslu2. > I installed the crosstool-native ipkg pacakge. (All 117MB). > Now what? I have a hard time figuring out what exactly to do > to utilize the toolchain. The nslu2-linux wiki pages are very > unorganized and confusing: openembedded, openslug, bitbake, what not. > All I want to know is how to set up the right environment to > use the crosstool-native stuff. What env variables do I need? > Can I make a chroot jail? Then how? > > Here's what I want to be able to do: get the linux-2.4.22 kernel > source and compile a third party module against it. Then I want > that new kernel module to be loaded on the nslu2. > > Thanks for any help/pointers. > > Geert [ Moderator Note: All static information is slowly moving to the Wiki at http://www.nslu2-linux.org ]

Next Message by Date: click to view message preview

new unslung packages

Several new packages were added to unslung this week. These include flac, transcode, ghostscript, and xchat. GNU emacs now supports x11 on unslung. You can force emacs to text mode with "emacs -nw"; some information about how to use x11 on the nslu2 can be found on the wiki. I'd like to hear feedback on whether anyone finds this to be a useful feature. I certainly find it useful for native development. Many modules were enabled in php, including berkeley db and gdbm support, and LDAP. Support for Imap and for libgd is planned, as is PEAR. -- Josh Parsons Philosophy Department 1238 Social Sciences and Humanities Bldg. University of California Davis, CA 95616-8673 USA Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html [ Moderator Note: All static information is slowly moving to the Wiki at http://www.nslu2-linux.org ]

Previous Message by Thread: click to view message preview

Re: Re: problem on getting CUPS to print

> Printer State: processing, accepting jobs. > "Printer not connected; will retry in 30 seconds..." > Device URI: usb:/dev/usb/lp0 > > I don't know what this means, lpq says it's okay, but cups says it's > not. If you just copy a .prn file to the device, does it still print? The question is who's to blame here - the driver or CUPS. Anybody else seen this message and if so with what printer brand? Does /var/log/messages or /proc/bus/usb have anything to say on the issue of the disappearing printer? > Another thing that I discovered: the spoolfiles aren't deleted after > printing. Maybe that's something I have to configure in Cups, didn't > look into that yet, but thought I'd better mention it > here. Which spool files? The ones created by Samba or the ones created by CUPS? As I understand it, the Samba spool directory is completely managed by Samba and jobs are submitted to CUPS using lpr. I'm abroad at the moment (so I'm cut off from my slug), so I will be less than helpful the coming week I'm afraid. best, -- Inge [ Moderator Note: All static information is slowly moving to the Wiki at http://www.nslu2-linux.org ]

Next Message by Thread: click to view message preview

OpenSlug: Trivia and FYI

OpenSlug is rapidly moving towards Beta. I pushed the changes today for the hotplug-ng, and tweaked the kernel command line to boot directly to the jffs2 partition. This resolves an issue with the nslu2-switchbox merge to 4.x. The should be cleared up soon, and after a little testing OpenSlug will be on switchbox 4.x thanks to dyoung and rwhitby. The hotplug-ng scripts boot like a bunny (fast). Full boot is < 45 seconds normally, and about 1 minute 10 seconds on the first boot. That's due to the extra 1 time things that happen on the first boot. Module dependancies, dropbear key..... Here's a shout-out to my e-mail pal John Bowler: Dude, you were right about the auto eth0 in /etc/ network/interfaces. Only the heavens know why that worked before, but the new hotplug doesn't operate exactly like the old scripts. So the ethernet wasn't coming up for the IXP or usbnet drivers automatically like it was with the old scripts. Now I know what you were talking about :). The was fixed with the latest updates also. My current punchlist for OpenSlug beta is short: 1) switchbox 4.x merge and testing (rwhitby's on this and close, so I know this will happen soon). 2) There's a minor annoying message relating to update-modules.postinst that generates the following messages: /usr/lib/ipkg/info/update-modules.postinst: 5: /etc/init.d/modutils.sh: not found postinst script returned status 127 ERROR: update-modules.postinst returned 127 3) /etc/fstab's first entry needs to be tweaked not to be /dev/ram0 for OpenSlug. 4) We need to get to 20 Alpha users. 5) The sysconfsetup scripts explicitly modprobes two drivers: ixp425_eth and ehci-hcd. I think we can get the modules loaded a better way at startup. But I could easily live with this for the first Beta release. Some other things I'm thinking about throwing in: 1) Support for netconsole logging 2) Interrupt driven IXP driver I'll keep everyone posted. Thanks and Cheers, [g2] [ Moderator Note: All static information is slowly moving to the Wiki at http://www.nslu2-linux.org ]