I newly installed Debian 6.0 I choose for the 2.6.32-5 686-bigmem kernel because I have 6Gb of RAM Now I want to use Cool n Quiet When I try to do modprobe powernow-k8 I get a 'no such device' message I have an Athlon64 X2 6000+ cpu. Am I using the correct kernel for this?
View 1 RepliesI have defoptions=quiet in my menu.list file and it keeps printing
ignoring bad line 1 'powernow-k8' across the screen during boot. The thing is that I have removed that line from /etc/modprobe.d/options, so why do I keep getting the warning?
I'm running Debian Squeeze/current fine with the default kernel & ATi's Catalyset drivers. I'm struggling to get the display drivers to work with the bigmem kernel as I've got 4GB ram on my machine so might as well try to enable it.
I can have my system work with the normal Squeeze kernel by installing the normal kernel headers & then FGLRX drivers, but after additionally installing the bigmem kernel & headers (linux-image-2.6-686-bigmem & linux-headers-2.6-686-bigmem) I cannot get the system to reach X after removing & then re-installing the video drivers.
Debian Version: 8.3 (Jessie) KDE (although this is NOT a desktop issue)
Basic Hardware:
Gigabyte Motherboard GA-970A-D3P
AMD 8350 CPU (8 cores)
32 GB DDR3 RAM
120GB SSD SATA-6GB/s
750 WD Black SATA-6GB/s
I am getting "Error: No space left on device" regularly during updates or installs, but why. Here is data on the disks, filesystems, etc...
Code: Select all df -h
Filesystem   Size Used Avail Use% Mounted on
/dev/sda1Â Â Â Â 81GÂ Â 27GÂ Â 50GÂ 35% /
devtmpfs     16G   0  16G  0% /dev
tmpfs      16G  76K  16G  1% /dev/shm
tmpfs      16G  18M  16G  1% /run
[code]...
Seems very doubtful that inodes are the killer.I have googled and followed all the threads, and search these forums and found nothing that fits - every answer there was focused on avaiolable space and inodes..And to make the cheese even more binding, the issue has cropped up on another 8.3 system with far more disk space (larger hard drives) and lots more unused inodes
Code: Select alldf -h
Filesystem            Size Used Avail Use% Mounted on
/dev/dm-0Â Â Â Â Â Â Â Â Â Â Â Â Â 907GÂ 6.6GÂ 855GÂ Â 1% /
udev                10M   0  10M  0% /dev
tmpfs               995M 9.2M 986M  1% /run
tmpfs               2.5G  76K 2.5G  1% /dev/shm
tmpfs               5.0M 4.0K 5.0M  1% /run/lock
tmpfs               2.5G   0 2.5G  0% /sys/fs/cgroup
[code]...
I've been testing Squeeze to determine whether KDE4 is finally suitable for my primary machine. Everything seems to be working fine except for detection of IDE devices. My CD/DVD drive no longer automounts and the reason seems to be that no device is being created. My Lenny system detects the drive as /dev/hda, but no such device exists in Squeeze. During boot, Squeeze appears to detect the drive as /dev/sr0 (according to dmesg), but in fact that device does not exist either.I'm actually running the Lenny kernel, as I am unable to compile my Ralink wireless driver (rt2860sta) using the Squeeze kernel. Also, for inquiring minds, I use removable HDD drive bays on my systems to simplify testing.
View 9 Replies View RelatedI run a program (findknxusb) to scan for devices on USB, but the device is not found.
The debugging level for libusb is on:
$ ./findknxusb
Possible addresses for KNX USB devices:
libusb_set_debug...
libusb: setting debugging level to 1 (on)
libusb_init...
[Code]....
I installed Debian Lenny on my HP Laptop - dv6-2120ed. Because i have atheros wireless card i needed to install ath9k which is not supported in 2.6.26 kernel so i compiled it to 2.6.32. Everything is good, but when i boot the new kernel i get "Bar 6: No parent found of for device" for 2 devices - the ethernet LAN card and the sound card. After 1 minute waiting the kernel starts booting and everything works fine (the LAN and the SOUND card too). How can i fix this and what means it exactly?
View 2 Replies View RelatedThe computer networking works fine with a normal static setup, but adding a USB wireless device is not successful. It is my own network so the wpa-ssid and wpa-psk are known to work with Lenny and a previous wireless device.The device is recognized (lsusb) and the driver is confirmed to be in the kernel (lsmod). Here is the iwconfig output:
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
After typing: ifconfig wlan0 192.168.1.144 up I can ping that address, but it is not working. I have just done a fresh install of Sid so that I could get the 2.6.35 kernel which contains the ath9k_htc driver for the USB wireless device that I am using. The firmware is ar9271.fw but my source of that is questionable because it does not seem readily available. I am temporarily using a PCMCIA wired connection which is what I am using to connect to the computer via telnet. (This is just for convenience so as to avoid getting up all the time.) Here is the ifconfig output:
eth0 Link encap:Ethernet HWaddr 00:40:05:07:d9:11
inet addr:192.168.1.122 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::240:5ff:fe07:d911/64 Scope:Link
[code]...
That file works with the previous USB wireless device under Lenny. Am I doing something wrong or is the driver and firmware just not up to snuff yet?
I've recently installed Debian. But the wireless network is not working. In Gnome it says "Device not configured" And if i try a ifup it says: root@accroft-msi:/home/accroft# ifup wlan0Internet Systems Consortium DHCP Client 4.1.1-P1Copyright 2004-2010 Internet Systems Consortium.All rights reserved.
Listening on LPF/wlan0/My mac address here
Sending on LPF/wlan0/My mac address here
Sending on Socket/fallback
[code]....
I've been having a problem with Bluetooth on Debian 8 Jessie i just can't connect to any bluetooth device, i have only tested my smartphone and my bluetooth headphones, i am using blueman manager.After attempting to connect to my bluetooth headphones/smartphone it just disconnects and says "Connection Failed: No such file or directory",i don't know if i have to create a config file or something, the error message doesn't say anything but the error previously mentioned.
View 7 Replies View RelatedI have a problem activating the hotspot on my debian 8. The issue is that I can't activate the hotspot to give other devices wifi connection.
I have the correct driver packages from the non-free repositories (firmware-realtek) and this service (hotspot) worked fine on distros like Ubuntu, Mint and Fedora .
I tried hostapd but it didn't work. I'm using cinnamon desktop.
My os is debian 5.0, netcard is RTL8168D/8111D. I can't use the Static ip, if I setup static ip, output "not found network device", but the network driver have loaded and if I use DHCP mode everything is ok. do you understand my english? What my next steps should be?
View 7 Replies View RelatedI'm not sure if this is a bug in Squeeze beta 2 or if it's something I've overlooked. I have a Maxtor 250 GB external USB drive that I use for backups. It gets auto-mounted fine, always in the same place, and from my normal user account I can write to it, even delete directories on it if I want to. But when, from Gnome, I select the "Safely remove" option, I get an error to the effect that it can't stop the device. The weird thing is that the thing actually *is* unmounted. I've checked the mount point and it's no longer there.Is there some package I maybe should've installed but haven't? I'm not really worried about data loss, since I'm sure the drive wouldn't unmount unless it was properly synched; it's just the error message that bugs me.
View 2 Replies View RelatedI'm configuring a machine with Debian 6. I booted from the DVD, took the defaults, and it eventually came up with a Gnome desktop. Everything worked as expected.
I then installed gcc, g++, the Debian kernel source, and built a new kernel with preemptive multitasking turned on. It built clean, I ran "make install" and it put the kernel files in /boot. I rebooted and got a kernel panic error, to the effect that it couldn't find the root filesystem.
/boot/grub/grub.cfg shows
"linux /boot/vmlinuz-2.6.32-5-686 root=UUID=1890437b-5884-4b83-97cf-62d39f63c872 ro single"
for the original install, but the entry for the new kernel has
"linux /boot/vmlinuz-2.6.30DW-preempt root=/dev/sda1 ro quiet"
/etc/fstab has
# / was on /dev/sda1 during installation
"UUID=1890437b-5884-4b83-97cf-62d39f63c872 / ext3 errors=remount-ro 0 1"
I've tried changing the grub entry to UUID, but the new kernel still panics. grub-mkconfig and update-grub just rebuild the split UUID=/sda1 grub.cfg. The new kernel still seems to be looking for /dev/sda1 even after changing grub.
I am trying to figure out what needs to be done to automatically set read/write permissions for everyone for my proprietary USB device on system boot. I have created a udev rules file which changes the permissions for the device when it is connected, but it does not change the permissions when the system is booted with the device already connected. The file looks like this:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="our vendor id", MODE="0666"
Does something else need to be added to the rules file to make it work when the system boots with the device connected? Is there some other script which needs to be created somewhere?
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.
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 Debian Testing. I am testing XFCE and LXDE and i want to use display manager other than GDM. I have tried SLIM and XDM but when i use them i can't mount partitions and USB through Thunar, PcMan or Nautilus - i get message that i am not authorized (if i do groups in terminal - adm dialout fax cdrom floppy tape audio dip video plugdev games fuse powerdev netdev lpadmin scanner sambashare). When i install GDM everything works fine. I have installed FUSE, HAL, Udev,...I have tried a lot of stuff from AcchLinux forums but nothing worked really.
View 4 Replies View Relatedhow do you change the default audio output device if you have multiple sound cards?
View 14 Replies View Relatedmy thinkpad Edge 11 has some problems with the touchpad and the trackpoint, so i want to permanently disable the touchpad, but not the TrackPoint. Both are PS2 devices.
/dev/input/mouse0 --> TouchPad
/dev/input/mouse1 --> TrackPoint
How can i disable the device? In X it does not work with gpointing-device-settings
Just when I thought my hardware configuring woes were put to an end, I don't have any sound. Here is my lspci list.
Code:
debian:~# lspci | grep Audio
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
And the aplay -l
Code:
debian:~# aplay -l
* List of PLAYBACK Hardware Devices *
card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
Subdevices: 1/1
Subdevice #0: subdevice #0
Working on Debian 7.2.0.
In a specific context I want to automatically make operationnal some USB WiFI devices, deploying automaticaly firwmare (may be not free packages) depending on device ID (vendor ID/product ID). Dev device is a Netgear WNA1000 (driver ath9k, with htc_9271.fw firmware).
I tried to reset the USB bus (modprobe -vr ehci_hcd; modprobe -v ehci_hcd) but it's not really reliable, with sometimes kernel panic.
Is there an "official" way to "mount" the device (the system create the device wlan0) just after deploying the firmware? Maybe using udev ?
I have just bought a DVB-T usb dongle to watch some TV. The software I'm using is vdr, which has to be started through the /etc/init.d/vdr service. I have created a udev script that executes the service on device insertion. It works nicely, however now when I boot up the computer it takes ages to get to desktop. I believe it is because of the WAIT_FOR part. But without this part, the service starts too soon because the usb dongle has been inserted but the firmware has not finished loading. Can someone point out an alternative way to do it? The script is here [URL].
View 4 Replies View RelatedI am using a kernel with no initrd. I have had this kind of panic before. Usually it means that the kernel can access the hard drive because the driver for the controller or filesystem isn't built into the kernel.
The kernel is 2.6.34 vanilla.
My IDE controller is a Silicon Integrated Systems SiS 5513, and I built the driver for it into the kernel BLK_DEV_SIS5513=y
My /boot (hda1) is ext2, and everything else is ext3
EXT2_FS=y
EXT3_FS=y
My grub entry (hda2 is my root partition) kernel (hd0,0)/vmlinuz root=/dev/hda2
I am using Debian testing i386. Just upgraded to 2.6.39-2-686-pae. After reboot, and ever since, I am getting warning: WARNING: Could not find hdaps input device (No such file or directory). You may be using an incompatible version of the hdaps module. Falling back to reading the position from sysfs (uses more power). Use '-y' to silence this warning.
View 1 Replies View Relatedi have this problem i install android sdk, and i install libreries: libstdc++5, lib32stdc++6, lib32ncurses5 and libstdl1.2-dev,
now if i use ldd comand don't have problem, but when i use eclipse and i compile a simple example (hello word example), i have this
error: [Emulator] SDL init failure, reason is: No available video device i have a notebook toshiba satellite A300-1RI whit ATI Radeon 3650, i install the amd driver and all work well.
I am using a 3rd party kernel driver that does not support udev properly. When I was using wheezy I placed the required device files in /lib/udev/devices.
The udev in jessie does not appear to support this. Is there any way to have udev create these device files or will I have to create then using a script at boot-up?
I eventually gave up and migrated to mdadm. Works just fine. Having upgraded to jessie and solved one problem
[URL] ....
I find the next one. When I boot into jessie my RAID device (just a data partition not /) is not found causing the boot to fail as per problems reported here
[URL] ....
After booting I can mount my RAID device but if it's in the fstab when booting it fails. Also, I notice that some of my lvm device names have changed. After a bit of hunting around I found a couple of solutions pointing to running dmraid as a service during boot and changing the entry for the RAID device in fstab to use the UUID.
[URL] .....
This seems to work. However this seems to be a workaround and as the lvm device paths for my / and /usr partitions have also changed, I'm wondering if there is a bug here as mentioned in the second link?
The / and /usr paths changed to /dev/dm-2 and /dev/dm-3 from the /dev/mapper/ form.
Using jessie over 4.2.8 or 4.3.4 kernel.
Used both the default bluez package, 5.23 and building bluez 5.36 by hand.
hciconfig shows a good configuration,
hci0: Type: BR/EDR Bus: UART
BD Address: 78:A5:04:31:3C:4B ACL MTU: 1021:6 SCO MTU: 180:4
UP RUNNING
RX bytes:82105 acl:0 sco:0 events:1989 errors:0
TX bytes:516 acl:0 sco:0 commands:48 errors:0
hcidump -x does show Commands/Events received, beacons are being seen, and collected by our app.
> HCI Event: LE Meta Event (0x3e) plen 42
LE Advertising Report
ADV_IND - Connectable undirected advertising (0)
bdaddr F9:77:66:E8:F7:8B (Random)
Flags: 0x06
[Code] ....
However when the app tries to connect it always gets connection refused at gatt_connect.
gatttool behaves the same way, and hcidump does not show any connection attempts, implying no connection between gatttool and the device, although it is specified on the command line.
Finally although the bluetoothd is running bluetoothctl also shows no default controller found. I had edited /etc/bluetooth/uart.conf, adding an hciattach entry for the device but that changed nothing when restarting the bluetoothd. Entering a garbage entry into that file does not produce any errors, so I am not sure it is even being read.
Also systemctl|grep bluetooth shows :-
sys-devices-virtual-bluetooth-hci0-rfkill0.device loaded active plugged /sys/devices/virtual/bluetooth/hci0/rfkill0
sys-devices-virtual-bluetooth-hci0.device loaded active plugged /sys/devices/virtual/bluetooth/hci0
sys-subsystem-bluetooth-devices-hci0.device loaded active plugged /sys/subsystem/bluetooth/devices/hci0
bluetooth.target loaded active active Bluetooth
/sys/devices/virtual/bluetooth/hci0/address shows the correct MAC, but /sys/subsystem/bluetooth/devices/hci0 does not exist, a post elsewhere indicated this was not a problem but that seems odd.
Is the uart.conf file still used([URL] .... would suggest yes) and if so is the format a full hciattach command or merely the hciattach parameters?
I have been trying to compile a patched driver for use with my RTL8187L wireless device and get this error.
rm -f ieee80211/Module.symvers 2>/dev/null
rm -f ieee80211/Modules.symvers 2>/dev/null
make -C ieee80211 all
[code].....
using this Azio Wireless PCI Adapter[URL] (Network controller: RaLink Device 0701)
View 11 Replies View Related