I searched the forum about installing the liquorix kernel but I cannot understand why the file /etc/apt/sources.list is not mentioned to invoke the liquorix repository.
Instead, I found: Alternative Performance Kernel for Debian wrote:For anyone interested, just add the following to a sources file (/etc/apt/sources.list.d/liquorix.list): deb [url] or for you scripters, echo "deb [url]
I installed the latest kernel liquorix (2.6.35) but when i want to install the Nvidia driver downloaded on the Nvidia website (256.53), i have an error message because Nvidia doesn't found the kernel source tree.
I install linux-image-2.6.35-6.dmz.2-liquorix-686_2.6.35-16_i386.deb, linux-headers-2.6.35-6.dmz.2-liquorix-686_2.6.35-16_i386.deb and build-essential. I don't understand why the installation doesn't works.
I am in the process of upgrading from squeeze to sid (not my main install, playing around) and would like to try out the liquorix kernel.
So far I've found these links: [url] [url]
I have ran the regular apt-get update && apt-get dist-upgrade and it pulls in newer versions of the liquorix kernel pretty often. Now whenever I boot up my system, I notice that there are now about three different 2.6.36.dmz liquorix kernels installed (I can't remember the exact numberings on that).
How can I remove all versions of the liquorix kernel except for the latest?
I'm using Squeeze and icedove and iceweasel and I've installed the package linux-image-2.6.36-2.dmz.2-liquorix-686. It works fine on my Dell 1521 Inspiron laptop with only one exception. If I'm surfing the web or checking my mail via a wired internet connection I'm fine... if I'm surfing the web or checking my mail via a wifi connection everything is fine... but if I happen to forget to connect to a wifi connection, and I'm in a situation where a wired connection is not available, I can start iceweasel (it doesn't do anything constructive), but checking my mail with icedove (simply starting the program) crashes my computer.
If I boot up with the 2.6.32-5 kernel, the one that's in the regular debian repository, I can not duplicate the crash. Somewhere I read that the liquorix kernels are optimized for a desktop computer. Is this my problem? Is it something else?
During the crash my screen goes to a text console and I see syslogd messages on the screen -- which I cannot reproduce here.
For quite a long time now, I haven't even needed to re-install video drivers most of the time. However, ever since version 2.6.36-0.dmz.4, they haven't been. I booted my system after installing that kernel, re-installed the video drivers, and when that didn't work, completely removed them and re-installed them, and it still didn't work. Well, I was told that the installation was successful but even after restarting it appeared that they weren't working. I installed 2.6.36-0.dmz.5 today and the same problem persists. I tried an older kernel version (2.6.36-4 something) and they worked fine.
View 2 Replies View RelatedI just installed a fresh box with a Ubuntu Lucid 32bit.
Is it possible and safe to install Liquorix Kernel in this distro?
I've done that in debian squeeze installations, but never done that in Ubuntu and really don't know if it's possible.
This is Wheezy x86_64. I tried two different ways to install kernel 2.6.38 on my machine and both have failed. First thing I did was to follow this guide [URL]... el-26.html) and try to compile the latest stable from kernel.org. I don't know why, but it turns into kernel panic when I try to run it. Second thing I did was to install the liquorix 2.6.38, and that also fails, seeming to boot but hanging a second short from the login. I don't know what I'm doing wrong. Is there a special way to install kernels in Debian? This is the first time I tried compiling a kernel, so it's quite likely that the problem is sitting 6 inches from the computer screen. Also, how would I remove those kernels since they're obviously not working? I know I could remove them from the grub menu but I'm not sure how to completely delete them.
View 12 Replies View RelatedI'm trying to compile the 2.6.38 kernel (from the Wheezy sources) on my Squeeze laptop and get the following error: "dpkg-buildpackage: error: debian/rules build gave error exit status 2" After doing apt-get build-dep linux-image-2.6.38-2-amd64 and apt-get source linux-image-2.6.38-2-amd64 I did dpkg-buildpackeg and here is what happened:
[Code]...
I know from a myriad of posts on these forums that Ubuntu is more bleeding edge than Debian Testing. Since, Debian'w own kernel is misbehaving rejecting my video chip (i915), I am tempted to install Ubuntu's kernel in Wheeze.
So, the golden question is: Is it logical and feasible to install Ubuntu's kernel in Wheezy? Wheezy's kernel is 2.6.38.
Just re-installed Wheezy to ssd-drive and noticed that everything works much faster than before. For the older install I made some changes to /etc/fstab (I think) which I found from the web. I don't remember exactly what changes.
Question is: what's the situatation with Wheezys beta4-release and ssd-drive? Do I have to edit something at the moment, or does the installer notice ssd-drive and make everything needed?
I already have a Notebook with windows (for some reason it needs 3 partitions..) and wheezy. When I installed wheezy I create 2 logical partition inside a primary one: one logical for /home and the other one for filesystem. Now I would like to overwrite wheezy and get get jessie, but without touching windows and home.
I already try to upgrading and it went wrong, so I prefer overwrite, what I have to do during "manual installation" phase?
I'm wondering I've read in some places that if people would like to move from a stable branch of Debian to the testing you can usually just replace the lines in sources.list with the testing release and update and then dist-upgrade. Is this true...and if so is it safe?
View 1 Replies View RelatedI upgraded one of my Squeeze installations to Wheezy, but after selecting it in grub, nothing is displayed on screen: no CLI and no GUI. I tried Ctrl + Alt + F[1-7] and I got nothing. My laptop is Acer Aspire 7715Z. I am attributing this to module as there seems to be disk activity, but without a screen, I cannot be certain.
View 14 Replies View RelatedI added the following line to my sources.list
Code: Select alldeb [URL] ..... wheezy main non-free
and then after:
Code: Select allapt-get update
I run:
Code: Select allapt-get install nautilus-dropbox
but I got stuck (console freeze) and I had to reboot hoping to sort out somehow...
After reboot I try to apt-get again but I got the following message (my traslation)
Code: Select allE: dpkg was interrupted.
It's necessary to do "sudo dpkg --configure -a" for correcting the problem
So I went in the console again for that command and I get
Code: Select allConfigurazione di nautilus-dropbox (1.4.0-3)...
Dropbox is the easiest way to share and store your files online. [URL] ....
but nothing fruitful seems to happen; and now how to proceed?
I am installing Whezzy and the installer failed to install grub on the MBR of /dev/sda
My disks are
- /dev/sda : the flash drive with the debian ISO
- /dev/sbd : a small SSD for the / partition (sdb1)
- /dev/sdc + /dev/sdd : a software RAID-1 array with LVM for /home, ...
Grub fails to install on /dev/sda which makes sense since this is the flash drive containing the Debian ISO so no MBR.
I already tried to run grub-update manually on /dev/sdb (with chroot /target grub-install --no-floppy --force "/dev/sdb" ).
It works but the system is not directly bootable. I had access to a second PC to read the grub documentation so was able to boot and to fix my system but this is annoying.
Is it normal to see my flash drive as /dev/sda? Could it be that my flash drive is incorrectly detected as a HD?
Is there a way to force the installer to install grub on /dev/sdb?
I have a server in which I'm trying to install Debian into. There's no BIOS, only EFI boot. The vendor locked it down so there's no way to see it or get into it.
The Wheezy 7.8 netinst CD has EFI boot parameters and works on everything I throw it in, except this one server. Booting it up, the code doesn't see the EFI and boots into normal mode, negating every chance to install it (dozens upon dozens of failed installs).
During boot, I press the [TAB] at the Debian Linux installer menu and get the load parameters (/install.amd/vmlinuz vga=788 etc). What parameter can I add to this line to get it to run in UEFI mode so we can install it?
I have a laptop primarily used for a client work. It is running Debian Wheezy, and wish to keep it intact in case I need to do more work for client.
I would like to install Ubuntu 14.04 alongside Debian, and use Ubuntu as a bit of a play/experiment area, etc... HD has lots of space (600GB free), and as far as I can tell Grub is installed in MBR.
I did some searches, and from what I can tell, it sounds like I can just install Ubuntu from ISO file, specify how much space to use (say 400GB), and that's it. This sounds almost too easy. Once I install and restart machine, will there be selection for what Distro to boot.
Without knowing the consequences I added the Sid repository to Wheezy (installed version) in order to install some software. Only much later I discovered that this generated me some mess which does not allow now to install additional software due to library conflicts.
I tried to install some packages needed to build the PhantomJS but here is what I got:
Code: Select allReading package lists...
Building dependency tree...
Reading state information...
build-essential is already the newest version.
g++ is already the newest version.
g++ set to manually installed.
[Code] ....
Is there a way to clean up the mess that Sid introduced and revert back to the Wheezy versions?
I have an old backup, so it would take me much more time to reinstall/reconfigure certain software, so I am looking to alternatives.
Is there a way to check all the packages and find all the potential conflicts and then a way to restore the original Wheezy content?
is it possible to simulate upgrading a Squeeze installation to a Wheezy or Jessie installation, on a OVH server ?I would like simulate upgrading server, and if not problems, upgrading in real time.I don't do that manipulation, and I don't do mistakes on a production server.
View 2 Replies View RelatedI try to update the packages before upgrade to wheezy,looks like when I run apt-get update,it shows error as per below:
W: GPG error: http://fosiki.com stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 379393E0AAEE96F6
rat:~# apt-key adv --keyserver keyserver.fosiki.com --recv-keys 379393E0AAEE96F6
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --
[code]....
I have just installed Wheezy after repartitioning and had to set up my sources list myself as (most of it) was not done for me. I have just added the main official repository,security updates and the multimedia repository. To be honest I'm not sure if any of them are working when I do an update in aptitude, I think the multimedia one might be. The CD ROM isn't even working despite the fact I have done apt-cdrom add.I am getting the following when run aptitude update:
Ign cdrom://[Debian GNU/Linux testing _Wheezy_ - Official Snapshot i386 CD Binary-1 20110328-05:16] wheezy InRelease
Ign cdrom://[Debian GNU/Linux testing _Wheezy_ - Official Snapshot i386 CD Binary-1
[code]....
I am using Wheezy netinstall on a USB stick. The machine has an Intel DH57JG motherboard, USB keyboard, and no optical drive. The installer loads to the initial screen OK, but the keyboard is not active. This problem has been reported for several years and was supposed to be fixed by kernel 2.6.32, yet here it is. What can I do?
One suggestion has been to disable/enable USB legacy support in the BIOS. It is enabled by default. If I disable it, the installer doesn't load. This keyboard works fine on other Linux machines and on the BIOS in this machine. I read there was a problem with Cherry keyboards and the Squeeze installer. This keyboard is not a Cherry but does have Cherry keyswitches.
I've created my own wheezy live usb-hdd using:# lb config -a i386 --mode debian --distribution wheezy --linux-flavours 686 -b usb-hdd --bootloader syslinux --memtest none -p xfce
P: Considering defaults defined in /etc/live/build.conf
P: Creating config tree
# lb build
The binary.img was created.
Now if I try to boot from this image using qemu, I get a message "No bootable device"
If I check this main partition using gparted, the flag is "lba" instead of "boot".
Even doesn't work if try to change to "boot".
How to solve this problem?
I'm trying to install Wheezy (amd64) from the daily netinst image with the text-based installer. The PC will lock up randomly at some point in the process (usually after about 5-10 minutes). The video signal cuts out, keyboard lights are unresponsive, and I have to hard-reset the machine.I was previously trying to install Linux Mint Debian Edition and had the same problem. Another user reports that this is due to a bug in the nouveau nVidia driver, but I can't confirm it.URL...
I assume the Debian text installer isn't using nouveau, so it seems unlikely that would be the problem. The random timing does suggest an overheating problem, though, and the fact that the video signal drops out would seem to implicate the video card. I had no lockups at all with the OS that was previously installed (Ubuntu 11.04).
I'm trying to install adobe flash player on wheezy (7.4). I've downloaded the package since adobe thinks apt works in a browser (it doesn't on my laptop). Anyway, I've tried installing the adobe flash player package via gdebi and it complains binutils is not installed. fine, I go to synaptic to find binutils and synaptic cannot find it. I'm not even sure why it is not installed. How to get binutils?
Here is my sources.list:
Code: Select all#
# deb cdrom:[Debian GNU/Linux 7.3.0 _Wheezy_ - Official i386 NETINST Binary-1 20131215-03:38]/ wheezy main
# deb cdrom:[Debian GNU/Linux 7.3.0 _Wheezy_ - Official i386 NETINST Binary-1 20131215-03:38]/ wheezy main
# deb http://ftp.us.debian.org/debian/ wheezy main
# deb-src http://ftp.us.debian.org/debian/ wheezy main
[Code] .....
I upgraded from deb7 to deb8, but am no longer able to boot. After passing the grub boot menu, the following messages are displayed:
Code:
Select allLoading, please wait...
[ 6.065713] systemd-fsck[148]: /dev/sda1: clean, 428644/1310720 files, 410616
9/52442880 blocks
[ 7.480551] Error: Driver 'pcspkr' is already registered, aborting...
[ 8.692700] systemd-fsck[341]: /dev/sda5: clean, 145485/6176768 files, 17407409/24695552 blocks
[ 18.066215] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated). Use CAP_NET_ADMIN and alias netdev- instead
_
The screen then clears and an underscore is displayed as the sole character at the top left position of the screen. The system hangs at this point. During installation, I rejected two changed files: /etc/init.d/bootlogd and /etc/libreoffice/sofficerc. For both, I opted to keep the installed version (the default choice of the installer) rather than replacing with the new version. The first might be related to the problem, although it seems to be responsible only for logging the boot process, and I would not expect this to compromise booting.
In case this information is useful, sda1 is mounted at /, sda2 is swap space, sda3 is extended, and sda5 is a logical partition mounted at /home.
I am able to boot into rescue mode, but other than that the system is not usable. Unfortunately, no useful error messages are given to aid in diagnosing the problem.
After installing KDE USB keyboard and mouse won't work. They are added to /proc/bus/input/devices though.
I also tried to install Gnome; same thing.
I took #usb-devices and they were there also..
But #usbhid-dump did not generate anything to screen.
I love using wheezy but i keep having to take my computer downstairs to hook it up to router through ethernet, i need it to connect through wifi and stay connected.
heres my problem, if i use live image and connect to network its fine but during installation process it gets to the network configuration, it will keep disconnecting at dhcp and if i try and continue it gives me the error packages broken due to it not staying connected.
MY WIFI CARD IS A TP-LINK WDN 4800
if i try and just do a net install then it doesnt show my wifi network.
it uses in both cases ar93xx atheros driver for installing, i just need to know how i can try and keep a stable connection over wifi so it can install over wifi so i dont have to keep taking pc downstairs to install it.
i done something that stopped me being able to login into wheezy i was left at black screen with blinking command line, i have reverted to mint debian until i can get a stable connection over wifi to install wheezy again.
A few days ago I bought a Raspberry PI B with Debian Wheezy (7.0 - I think) on it. Before installing a media centre on it I wanted to do some basic configuration/upgrade and decided to upgrade to Debian Jessie. I followed the instructions provided on [URL] .....
Before moving to Jessie I have upgraded the original Wheezy; after the upgrade the version was 7.8. Everything went well till I executed "apt-get dist-upgrade". Errors where generated. As suggested I tried the "apt-get -f install"; but it did not go smoothly either. However, so far, I am accessing the desktop and everything seems fine (although I did not do anything fancy yet). The version recorded is 8.0. Thus, should I worry about the error messages generated?
Please find the log file here: [URL] ......
Note that I put the log file on Google Drive because each time I clicked on "add file" in the "Upload Attachment" tab when editing this message I got:
Internal Server Error:
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, forum-admin@forums.debian.net and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.