I am running debian testing on a core i3 laptop with a hybrid graphics setup (intel hd 4000 + radeon r5 m230), after the recent upgrade including linux-image-4.2.0-1-amd64, on bootup ...
I get this error:
Code: Select all[ 10.255177] radeon 0000:09:00.0: firmware: direct-loading firmware radeon/hainan_rlc.bin
[ 10.264718] radeon 0000:09:00.0: firmware: direct-loading firmware radeon/hainan_mc.bin
[ 10.271031] radeon 0000:09:00.0: firmware: direct-loading firmware radeon/hainan_smc.bin
[ 10.271037] [drm] Internal thermal controller without fan control
[ 10.271118] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0
[Code] ...
And this:
Code: Select all[ 19.347705] radeon 0000:09:00.0: WB enabled
[ 19.347709] radeon 0000:09:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff880097816c00
[ 19.347711] radeon 0000:09:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff880097816c04
[ 19.347713] radeon 0000:09:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff880097816c08
I installed F11 on a SATA 500 GB Hard drive. I plugged this HD in various computers. It worked fine.
However, when I try it on the following platform (the one I have to get it to work): (PC104 bus, AMD 1.1GZ with 512 RAM), I get a file system error during bootup.
On the other hand, the system gave the chance to enter the root password. So, once I did this, I tried to run commands "fsck -f /dev/sda" and "fsck -f /dev/sda1". The command could not find sda or sda1.
I tried the fsck on different platforms (with the same HD), it worked fine.
I returned the CPU board to the vendor, and I am expecting a new board soon. I assumed the problem could be with the board itself. But, I am not sure.
I decided to fully install Ubuntu 9.10 on my computer Using Entire Disk Space. Installation was completed without any problems so I followed the instructions, Rebooted and took the CD out of the mechanic. After rebooting, when the GRUB was loading, it said the following Error: no such device: 235ea02c-16b5-4abf-af04-af6767b6848f
I tried rebooting several times, even with CD inside. All it did was it moved to choice of System (normal, safe mode, memory check etc...). When I chose Normal, it just refreshed and did not get me anywhere. The same goes for the safe mode. After a certain while I decided to replace it with 10.04. However, this one stopped at 79% saying sth like Retrieving Data *number* of *number*.
It lasted for too long so I rebooted again, now with 9.10 CD inside again. I installed 9.10 hoping that this time it would work the way it should. However, the exact same thing happend. Installation went smoothly but GRUB booting had that error. Now there is Ubuntu 9.10 on my HDD which would not start so I'm writing this using the "10.04 Tryout".
I'm a new ubuntu user and have been trying to get my system to bootup properly after installing the NVIDIA accelerated graphics driver (version current). I've searched and attempted for the past few days and found a few posts and articles describing similar problems as mine but the solutions don't seem to work.
Same problem I am having on bootup [url] but the solution does not work for me.
On bootup instead of going into the GUI splash screen it goes to a full screen terminal same, as the link above. After 5 minutes a command prompt appears requesting me to log in. I wait, eventually it goes into the GUI log in screen and everything works as normal from there.
I run glxgears without the driver installed and get around 500, with it installed 3000.
I have downloaded the latest Ubuntu 9.10 and used 'U904p' a program I had for creating 9.04 live USB I had before. I had 9.04 on the USB pen but thought that 9.10 would be better to install right away rather than upgrading it. So I run through the CLI and make it bootable and all that. I come to put in my pretty old (Spare parts mashed together) Linux box. I get this about 1 minute after the Ubuntu logo and loading bar:
Top of page: WARNING: Couldn't open directory /lib/modules/2.6.31-14-generic: No such file or directory
Then lots of 'FATAL: Could not load /lib/modules/2.6.31-14generic/modules.dep No Such file or directory'
Then I am dumped in to Busybox in initramfs command line. I have been googling and look around the forums all last night and this morning. I find loads of stuff from 9.04 but not 9.10? I tried the old 'Pull USB pen when Ubuntu log shows' and 'Changed SATA settings' turned them off in end, using IDE. Could it be that I created it using the old U904p program. I will look in to the newer one. Seen it about on forums. Otherwise any ideas? I am wanting to build a FOG box for imaging all my PC's and trailing it for work.
i want to use linux but i am having some issues getting it to work on my system. my desktop is a p4 3.4gig with 512 DDR. When I insert my ubuntu CD it starts loading but then i get this screen/message:
Busybox v1.15.3(ubuntu 1:1.15.3-1ubuntu5) built-in shell(ash) Enter 'help' for list of built in commands (initramfs) mount:mounting/dev/loop0 on// filesystem.squashfs failed input/output error Can not mount /dev/loop0 (/cdrom/casper/filesystem/squashfs) on //filesystem.squashfs if I put the same disc into my HP laptop it boots up ubuntu fine. (however it won't allow me to get online, but that is a different issue).
why I'd be receiving this error. I have created a partition and filesystem and put the label in fstab. Everytime I reboot the server it is unable to mount the filesystem. However I am able to mount it manually.
During the boot-sequence of jessie there is more text flying by on the screen (including some errors or warnings) than I can read thorugh fast enough. I don't think this is very serious stuff, and if it were I could always look at dmesg and or syslog i /var/log but I would find it really convenient to log these messages in a file instead of sifting through or grep-ing dmesg.
When duckduckgoing this matter I found [URL] ....
I installed tried bootlogd but when configuring it to "yes" and rebooting nothing comes up in /var/log/boot.
Then I saw this line in above link
If you use systemd as your init system, you may need to use systemctl to debug boot problems.
I'm using debian for the first time and I recently downloaded the Debian Lenny 201 Live CD to test it on my old computer (I'm planning to use Debian 5.0.4). It has a Pentium III (550 MHz) processor, 192 MB RAM, 8 MB graphics memory, 20 GB HDD with a monitor supporting 1024x768 resolution. The problem is, after the booting is complete a blank flashing screen appears with a cross-shaped cursor in the middle. I continues and nothing happens. I tried with solutions like editing the entries with 'live xdriver=fbdev', 'live xdriver=none', and 'live vga=771'.
i rarely need my wireless, and i want it off by default, i am going to disable it during bootup with
echo 0 > /sys/devices/platform/acer-wmi/wireless
what would be the proper place for this? if i put it in rc.local it will be executed very late, i'd rather have it sooner. if add a new script to init.d, then run update-rc.d, i would have to adhere to the start|stop|reload structure of these scripts, right? or do i go a totally different way about this?
I installed debian etch on my system. Installation done successfully, but when it boots up the X server is not starting and showing error. Note : It is perfectly working with debian lenny. Configuration : Intel DG41RQ ,1GB Ram ,160GB HDD.
Since upgrading to Lucid, I am getting the following dialog warning on login: 'Could not apply the stored configuration for monitors X Server does not support size requested' Im using the current proprietary NVIDIA graphics driver with dual heads. My display is fine, but the warning every time I login is annoying. After googling around I found this thread: [URL]. I tried going to Monitor Preferences as suggested. My resolution as displayed in the default tool is set to 3840 x 1200, which I suspect is the issue forcing the dialog, but I cant change the resolution, refresh rate or rotation from the Monitor Preference dialog box. dino99's response (in the referenced post) about xorg.conf not being needed anymore seems relevant. How can I resolve this issue and get rid of this annoying warning? Is there a configuration that I can update with a supported resolution to placate lucid?
On a fresh install of squeeze, I can't log in to an AIM account with being immediately disconnected and given this error: You have been connecting and disconnecting too frequently. Wait ten minutes and try again. If you continue to try, you will need to wait even longer.
I waited for several hours before trying to reconnect, but got the same message. Searching for the error led me to some bug reports from upwards of three years ago.
Strangely, this error hasn't occurred on any of my other squeeze systems.
I can ping login.oscar.aol.com as well as login.messaging.aol.com; both resolve to 205.188.251.43 for me. I tried changing the "Server" under "Advanced" to this address, but again I got the same error.
I installed AcetoneISO (Debian 6) and when I try to mount any .iso image, even one that is created on AcetoneISO I can't! I got an error. Error, could not mount image.
I'm getting "Can't open display" all the time when I log in the server through ssh. penguin@theblue:~$ xeyes Error: Can't open display: laptop:0.0 penguin@theblue:~$ export DISPLAY=192.168.1.101:0.0 penguin@theblue:~$ echo $DISPLAY
[Code].....
The problem I found is sshd server set DISPLAY to localhost all the time.
The problem is next: when I try to install kde 5 into my debian wheezy system (now have kde4), I add 'kubuntu-ppa/next' repo and then try to make 'apt-get update' from 'su'. But I catch next message:
W: Failed to fetch http://ppa.launchpad.net/kubuntu-ppa/ne ... ce/Sources 404 Not Found W: Failed to fetch http://ppa.launchpad.net/kubuntu-ppa/ne ... 4/Packages 404 Not Found W: Failed to fetch http://ppa.launchpad.net/kubuntu-ppa/ne ... 6/Packages 404 Not Found E: Some index files failed to download. They have been ignored, or old ones used instead.
When trying to update the software from wirthin gnome i get the error message. Failed to obtain authentication.Is there a way of updating from the command terminal.how...
I'm running Jessie on an AMD64 with an ATI Radeon HD 7770 card. I have installed the fglrx driver. When I try to play a movie with vlc, it crashes with the following error:
To make a long story short:./usr/bin/mplayer: relocation error: /usr/bin/mplayer: symbol codec_wav_tags, version LIBAVFORMAT_52 not defined in file libavformat.so.52 with link time reference
Debian-unstable. I tried to play some avi files with smplayer. I got an error message and searched the fscking web: http://www.mail-archive.com/pkg-multime ... 02393.html
I downloaded skype 2.2 .deb package on the skype website and tried to install it via sudo dpkg -i skype-debian_2.2.0.25-1_i386.deb and got the following errors:
[code]...
What does the error mean? I am guessing I have a faulty package. old skype can't be used due to segmentation fault error, so I am really hoping for the new upgrade to solve my skype problem.
Miro worked well with Wheezy. When I upgraded to Jessie Miro started generating a python error as such:
Code: Select all~$ miro using /usr/bin/miro.real Traceback (most recent call last): File "/usr/bin/miro.real", line 183, in <module> from miro import startfrontend File "/usr/lib/pymodules/python2.7/miro/startfrontend.py", line 53, in <module>
[Code] ....
I have been searching for a few weeks trying to find an answer to no avail. I tried three different kernels, renaming ~/.miro, checked all dependencies. I reported it as a bug which sat there for a few days and disappeared.
Error - "Oh no! Something has gone wrong." and "A problem has occurred and the system can't recover. Please log out and try again."
How to get back to original nouveau driver after failed nvidia driver install?
What probably happened was a wrong nVidia driver install from the repository.. Because never had any problems earlier, but after I installed some nVidia packages, I get this error.
I already tried to remove nvidia driver by # aptitude purge nvidia-kernel-dkms nvidia-glx It was successful.
Then I reinstalled Xorg Nouveau driver and all its denpendencies by # aptitude install xserver-xorg-video-nouveau It was also successful.
I tried to ignore it (yesterday it made me remove xmms2-plugin-all, i could have lived with that for a few days), but it is getting worse: gnomebaker, mpg123, vorbis-tools, cdrdao, etc.
So i remove beloved apps , run aptitude install -f and what not. The result is that either libao2 or libao4 give me trouble (depending which version is installed at that moment).
After the upgrades are available again it's big fun over here. Is it just me or are others running in a lot of "dpkg returned an error message" too? The first time ever i got to use aptitude to get problems solved. Gnome terminal gives me segmentation fault but no error messages. And so on.
Did not find much here regarding building Gnome 2.30 from source. I'm using jhbuild to build the gnome 2.30 desktop. I have everything, to my knowledge, installed to build gnome. I get an error when trying to build the libIDL library. Anyone have any clue as to what I need installed or changed in the configuration file to build libIDL?
I migrated to Debian sid, but since then I got this error everytime I launch Update Manager (whether it's in graphical mode or from a shell). Just after putting down my root password, I got this error:
Title of the window: (as superuser) A fatal error has been detected in update-manager. Do you want to submit a bug report? Selecting No will close the application. Whether I click Yes or No, nothing happens.
When I try to start korganizer from a konsole, I get the following error reply and kontact crashes
<unknown program name>(24450)/: KUniqueApplication: Cannot find the D-Bus session server: "Did not receive a reply. Possible causes include: the remote application did not send a reply,the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." <unknown program name>(24445)/: KUniqueApplication: Pipe closed unexpectedly.
In my newbie mind - there is something wrong with d-bus or similar. I can however start kmail and KAddressBook without problems. The crash of kontact/korganizer first showed up under my (up-to-date) Squeeze system. I then upgraded to "testing" but the situation is the same. I have filed Bug 274661 with the KDE bug tracking system. So far - no answer........
