Since removing the deprecated usblp driver from my kernel I no longer have a /dev/lp0 device, or /dev/usb/lp0. I use these for sending files directly to my printer. Should these be created by udev? If so, why might they not be being created? If not, how can I get a persistent device name for my usb printer?
View 1 RepliesMy printer is HP F380 which is the same class as Deskjet 3650. I'm wondering is there an official website I can use to check if my printer is supported? Oh and how do I know which version am running? My kernel is 2.6.16-16
View 2 Replies View RelatedI have a problem defining persistent device naming on a Debian Lenny server.I have:RAID1 controller on the server machine with two SCSI disks.external storage with RAID5. I have / mount on the first partition on the server SCSI disk and /storage mount on the external storage.
I'm experiencing a problem: The system recognizes the system disk (RAID 1), as sda or sdb - randomly.I want: To control the recognition, and tell the system that sda (sda1) will always be the system disk.The motivation: GRUB is configured to work with sda, and when the system disk doesn't, boot process fails, and I end up in the initramfs shell-like interface.
Booting the kernel
.
.
.
mount:mounting /dev on /root/dev failed: No such file or directory
mount:mounting /sys on /root/sys failed: No such file or directory
[code]....
I have a problem defining persistent device naming on a Debian Lenny server.I have:RAID1 controller on the server machine with two SCSI disks.external storage with RAID5. I have / mount on the first partition on the server SCSI disk and /storage mount on the external storage. I'm experiencing a problem: The system recognizes the system disk (RAID 1), as sda or sdb randomly.I want: To control the recognition, and tell the system that sda (sda1) will always be the system disk.The motivation: GRUB is configured to work with sda, and when the system disk doesn't, boot process fails, and I end up in the initramfs shell-like interface.
Code:
Booting the kernel
.
.
.
mount:mounting /dev on /root/dev failed: No such file or directory
mount:mounting /sys on /root/sys failed: No such file or directory
[code]....
Since upgrading to openSUSE 11.4 (x86_64) KDE: 4.6.3 I find that any changes made in the KDE Printer --> Properties --> Margins dialogue with Konqueror, Kate, Kwrite, etc. are not persistent. Such changes are persistent in openSUSE 11.3 (x86_64) KDE: 4.4.4.
Consequently I must open the Printer --> Properties --> Margins dialogue and change the default margin setting (4.23 mm) four times (TBLR) for each print job.
A similar issue with non-persistent duplex printing was solved by installing system-config-printer but that does not provide an option to reset the default margin settings.
I have made the usual searches and checked the printer pages in the SDB. There are some related bug reports on openSUSE, KDE and QT bug tracking systems that make interesting reading (!) but I did not find a user level solution for non-persistent margins.
How are the default KDE print margins set and can they be changed?
Just started using the above distro - anyone know how to make persistent saves to a USB device?
View 5 Replies View RelatedI have a server wich is connected to an iSCSI storage and gets harddisks from this storage. Sometimes I have to add new disks to this server. Everytime I add a disk and make an /etc/init.d/iscsi restart on the server the disks don't have the same device name as before the iscsi restart.
It should be possible to gave the disks persistent names using udev rules. Now I tried to create different rules in "/etc/udev/rules.d/99-static-iscsi-names.rules" e.g.
# /dev/sdc
KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -s %p",RESULT=="360a98000503355344c4a576864467877" NAME=="sdc%n"
In "/etc/rc.local" I added "/sbin/start_udev" and in "/etc/scsi_id.config" I added the line "vendor="NETAPP",model="LUN",options=-g"
[Code]...
I've bought a HP Photosmart printer, HP Photosmart wireless e-All-in-One printer - B110a and i've got a problem installing it properly. I'm using Debian 6.0 Squeeze. When i connect the printer, Debian doesn't recognize my printer as the Photosmart B109 printer for unknown reason. When i go to the site of HP and search for a driver, it directs me to this site:I've downloaded that latest hplip file as a .run file and installed it. My printer is recognized proparly, but when i try to print a colored image, it comes out black/white. Something is not crrect. Does anyone recognize this problem with this type HP printer?
View 7 Replies View RelatedAfter upgrading to Slackware64 13.1 BETA1 my USB printer stopped working. Blacklisting usblp fixed it. See this thread regarding problems with CUPS 1.4.x. It might be a good idea to blacklist it by default in 13.1, just like Nouveau, as this appears to be a problem that has come to stay...
View 5 Replies View RelatedI need to have a persistent Debian install on a thumbdrive to run a computer that is currently diskless (dead hard drive). So far I've managed to get it to boot Squeeze live beta by setting up the thumbdrive with UNetBootin, but it's not persistent. I found this, but step 6 is a mystery to me, as I can find no such command or package.
View 12 Replies View RelatedI was wondering if it can be possible to boot debian from micro sd card and have it persistent. I have checked the bios of my laptop and there are options to boot from USB and HDD (and from floppy, cd, network and hard disk), but not from sd card. Would it be a problem or could there be workarounds. That is of course if the whole thing is a good idea at all.
I have already booted the laptop from USB, but I would like to use it for everyday work and USB sticking out is bound to get snapped off. Sd card on the other hand would go inside in the slot. The hard disk is dead and is a bit expensive to replace (and unnecessary in respect of the volume, I only need a couple of gb for work)
So i installed debian squeeze in virtualbox with xfce and i thought that it was persistent. when i powered down the virtual machine and started it up again later I only had the option of installing it again. Do i use save state to keep it in the installed stage? would i have to do that each time i made a change? i want to make sure so that i don't keep having to re install it.
View 7 Replies View RelatedYes, I know, I know, there are lots of instructions out there on how to create a persistent Linux USB drive. However, I've been having a really hard time finding if it's possible to create the WHOLE thing persistent.For example, I want to turn my 8 GB thumb drive into a portable Debian Squeeze where I can install (persistent) apps and make root-level changes to the filesystem. Is this possible?
View 2 Replies View RelatedI installed debian 8 on a 16 GB usb drive using this guide. I used a debian 8.2 64-bit image with mate. If I were to get a larger usb drive, would I be able to transfer everything from the 16GB drive to it? How?
View 1 Replies View RelatedHow to enable persistent logging with systemd? I find it really weird that all this machinery that is systemd doesn't store persistent logs, what if I'm trying to retrieve some information regarding previous boots?
For instance: I have random suspend issues, after rebooting the computer there's no trace left in the logs of what happened, and furthermore (at least in Jessie) I can no longer see a pm-suspend log.
So, at first it sounds like all you have to do is edit journald.conf setting #Storage=auto to "persistent" and create the /var/log/journal directory, but then reading here /usr/share/doc/systemd/README.Debian
Code: Select allEnabling persistent logging in journald
=======================================
To enable persistent logging, create /var/log/journal and set up proper permissions:
install -d -g systemd-journal /var/log/journal
setfacl -R -nm g:adm:rx,d:g:adm:rx /var/log/journal
and here [URL] ....
There are two main reasons why I decided to not enable persistent logging just yet ....
We did get corrupt journal files in the past where the journal then no longer worked at all [1]. With volatile you can just reboot and have a clean state again. Admittedly, the journal has seen a lot of improvements in the mean time and hopefully is more robust, so this point is no longer true.
We still install rsyslog by default. That means we get store them twice. This is something we don't want to do atm.
I should create a sqeeze image and install it on other computers.Udev should detect network card (NIC) module and load it automatically at startup.How I understand /lib/udev/rules.d/75-persistent-net-generator.rules runs when udev starts, then writes to /etc/udev/rules.d/70-persistent-net.rules.The problem is, udev searches for this NIC on other hardware and the network cannot start.I can solve this problem easily using a startup script to delete /etc/udev/rules.d/70-persistent-net.rules file.
View 2 Replies View RelatedI am trying to use the printer port. But, I get this
Code:
Broadcom EJTAG Debrick Utility v1.6r-hugebird
Failed to lock /dev/parport0: No such device or address
johnh@tux:~/Ubuntu One/hh$
run from johnh I permission denied sudo-ing I get above.
I'm trying to create a persistent live Jessie system on my 8GB USB drive.
If that matters, I'm currently on an Arch Linux system, and I partly followed what's on the relative wiki (Pages Create a new MBR for a USB stick, Manually create a USB flash installation and Install Syslinux), plus a CrunchBang post explaining how to make a persistent live USB out of any Jessie-deriving distro (like their BunsenLabs Hydrogen).
The problem is, even if Debian boots up more than fine, the system isn't persistent at all.
Here's what I did (I know some passages are redundant, but still...):
Downloaded the Cinnamon flavor of Jessie via torrentErased the old MBR
Code: Select all# dd if=/dev/zero of=/dev/sdb bs=512 count=1 && syncCreated a 1.1G W95 FAT32 (LBA) active partition and used the remaining space on a Linux partitionFormatted the first to FAT32 and labelled it "Debian64". Formatted the second to ext4 and labelled it "persistence"
Code: Select all# mkfs.vfat -n Debian64 /dev/sdb1
# mkfs.ext4 /dev/sdb2 -L persistence
Mounted the first partition and the iso
[Code] ....
I have created live persistent usb-hdd (fat32) image, put into USB stick, but now I should create persistent live-rw partition. How this persistent partition should be formatted? Should I format with ext2, or fat32?
View 1 Replies View RelatedI've created live squeeze usb-hdd and if I boot first time the udev system writes the MAC address of the network interfaces into /etc/udev/rules.d/70-persistent-net.rules.Because I use full persistence, the file is there on the next boot and I don't get network running automatically on other computers. My problem is, howto remove 70-persistent-net.rules every time during the startup?
View 5 Replies View RelatedI'm working on my iptables rules on a debian 8 vps and I tried to install iptables-persistent but I was told "Unable to locate package"...
Where can I get this so that I may save my rules for reboot?
I installed few days ago Debian Jessie (Linux server-1 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux) for some tests.I tried to install iptables-persistent with the command "apt-get install iptables-persistent".During the install process, I got the following message :
Code: Select allPreconfiguring packages ...
Selecting previously unselected package netfilter-persistent.
(Reading database ... 31677 files and directories currently installed.)
Preparing to unpack .../netfilter-persistent_1.0.3_all.deb ...
Unpacking netfilter-persistent (1.0.3) ...
Selecting previously unselected package iptables-persistent.
[code]....
Some talks about cups, acpid, ipv6 or systemd but nothing has solved the issue in my case.I used iptables-persistent many times with older debian versions.
I want to customise an amnesic Debian environment (like Kali Live CD) with everything (Users, background, icons, etc.) set up to work the way I need. This OS should be inside a memory stick, and, most important, it has to have an encrypted partition I can mount and unmount whenever I want to save persistent data.
View 5 Replies View RelatedI have set up a hdparm configuration file ( /etc/udev/rules.d/50-hdparm.rules ) with :
Code: Select allACTION=="add", SUBSYSTEM=="block", KERNEL=="sda", RUN+="/usr/bin/hdparm -B 255 -S 0 /dev/sda" .
This works correct when I power on my system, however after waking my computer from sleep mode , /dev/sda appears to operate with APM .
Is there a way I can make this setting to be persistent ,i.e. APM disabled when waking up from sleep mode?
I am running Debian Jessie x64.
I recently changed from Gentoo to Debian Squeeze. All went fine but I have an ALSA issue. I have an AMD Athlon II X4 board with a Nvidia (Realtek) sound chip. After installing I got a lot of "no such device" errors, so I installed the Realtek driver the Debian way and the errors vanished. I could successful run alsactl init and alsamixer.
At this point there is no sound neither in games nor system. alsaplay says (on the screen) that it is playing a wav file but there is no sound. My test ''dd if=/dev/urandom of=/dev/dsp'' complains "/dev/dsp : no such file or directory". Well, all clear. modprobing the snd-*-oss modules brings sound alive but I have to do this after every restart. I have no clue how to make this persistent the Debian way.
I have a 16 GB Sandisk Cruzer Blade USB drive. My aim is to create a portable LMDE operating system. Both for the challenge and to spread the word amongst my friends. Just today, I've converted another mate with an old Dell with stand alone LM9 LTS. On another thread, I recieved a lot of help trying to use GRUB with no real progress other than finding out that needed someone with a lot more knowledge.
viewtopic.php?f=46&t=64335 bear with me for the long description of what I have done so far. I'm trying to avoid us doing things twice. I have used Startup Disk Creator in LM9 to set up my usb. There is still a problem with persistence. Creator uses casper and syslinux to boot. In setup, it gives the option of persistence up to 4 GB file or discard.
The progress window indicates it creates a persistence file. Everything seems to go smoothly to completion and reboot. The boot-up avoids the usual live dvd menu and goes all the way to the live desktop with install Mint shortcut. Change the keyboard to USA Colemak with CapsLock an additional backspace. Reboot the PC, no remove drive and enter request on shutdown, and back to live desktop. No Persistence. Reboot. I go to users and groups and create my own user desktop. Logout of Mint and into my desktop. Change keyboard settings and go to reboot. It wouldn't let me. Needed a root password. Back to the forums to change that. More research tells me that the program creates a seperate ext2 partition labelled casper-rw to generate persistence. Some sites have called it casper.rw Run GParted. dev/sdd- Sandisk 16GB- has a single FAT32 Partition sdd1. No casper-rw ext2 partition. Amongst other things I created the casper-rw and casper.rw partitions to help it along. No effect. I removed the pendrive, and booted up normally. Re-inserted the pendrive to determine the included files.First level-
[Code]...
I have Lenny installed. How to create, using live-helper customized Live USB with a persistent /home partition on this USB stick, to save changes between boots?
View 6 Replies View RelatedI have a Epson Stylus SX115 All In One Printer which i connected to ubuntu 9.10 the other day. Upon installation the drivers for the stylus SX 115 were not available, but there were drivers for the stylus SX110 which i then installed. Printing is fine although for some reason even though i connect via usb cable the printer is not detected as a external device. I have to pull out the usb cable without unmounting-what should i do?
View 8 Replies View RelatedI am using Mepis 8 on my PC and also have a laptop with windows XP installed. I had the laptop connected to the printer (HP Deskjet 930c) on my PC through the Internet Printer Protocol but it suddenly refused to work. I accessed localhost:631 through my broswer on my PC and there was a error message "permission denied on /dev/lp0". Now my printer refuses to work on my PC also. I have tried deleting the printer and rebooting and reinstalling it but the KDE print manager lets me get right to the final stage before informing me it cannot create the printer. All I was trying to find the URL to install on my laptop.
View 7 Replies View RelatedI have a printer that is not getting a device node assigned at boot.The printer is attached with a USB to Parallel (IEEE-1284) adapter cable.When I plug in the usb cable when the machine is running, the printer is assigned the device node: /dev/usb/lp0
I am guessing that during startup, the printer device is not detected since it is plugged in over an adapter cable which may be considered a device in itself?This is for a retail store, and we rely on the printer to pop the cash drawer open, so it kinda has to work without a "secret handshake".Unfortunately our workstations do not have Parallel ports. I would be happy to share terminal output, udev info, I'll write you a poem but I could sure use a helping hand- I'm stumped!