I've been running squeeze for a couple of weeks now, no problems, just some minor sound issues but that is not important ATM.Everything was working fine until this morning i guess, the boot process goes as normal but at one moment it just freezes for no apparent reason it just says Starting K Display Manager:kdm. Has anyone experienced this problem before, or has a solution?
View 3 RepliesI'm currently using Debian Lenny 5.0.7 and I tryed to upgrade to Squeeze. I followed the instructions from Debian's Guide:
1. I changed my repositories to squeeze in sources.list
2. # aptitude update
3. # aptitude install apt aptitude dpkg
4. # aptitude safe-upgrade
After this last command, the computer kept working for about 7 hours, it consumed 2 gb RAM and 1 gb swap, and in the end aborted with the following message:
I searched around and I found out that this error is somehow related to C/C++ package compilation, but I found nothing specific related to Debian's upgrade.
I run the 2.6.32-5-686 kernel on Squeeze and the bad nvidia drivers. A recent update, and pardon for not noting which, broke 3d games on my box. From a terminal neverputt yields the following error:
ignatius@lapbox 14:56 [ ~ ]:$ neverputt
X Error of failed request:� BadWindow (invalid Window parameter)
Major opcode of failed request:� 137 (NV-GLX)
[code]....
I can mv xorg.conf to xorg.conf-pre and nexuiz will fire-up. Without 3d of course. I spent an hour or so last week going over my xorg.conf but it just ain't broke! Someone else saw it, too, and reported it but his post remains alone in the thread as of 10 minutes ago.
I have the following system:
HARDWARE, desktop: MSI motherboard A58M-E33
AMD (APU A6-5400k) (dual-core) (AMD Radeon HD 7540D) (3.6Ghz),,,,4GB/RAM
Monitor connected to the motherboard's VGA port.
DEBIAN JESSIE , Linux 3.16.0-4-686-pae
========================================================
The computer continues to run fine no problems, I only see the following fail error at boot up...
kernel: [46717.717430] [Firmware Bug]: cpu 0, failed to setup threshold interrupt for bank 4, block 0 ........
kernel: [46717.717430] [Firmware Bug]: cpu 0, failed to setup threshold interrupt for bank 4, block 1 ..............
the above repeats about 18 or so times. then:::::
[Code] ....
The computer continues to boot, and runs well. I did a search, and I found similar errors reported but NOT the same as this. They were blamed on issues between Linux3.16 and AMD type GPUs ...
Running Debian stable. I added the following command to rc.local and made it executable:mount -t cifs -o username=ted,password=computer,uid=mooreted,gid=users "//192.168.1.121/Storage Volume" /mnt/vortexAfter rebooting dmesg throws the following error:
[ 21.400697] CIFS VFS: Error connecting to IPv4 socket. Aborting operation
[ 21.400708] CIFS VFS: cifs_mount failed w/return code = -101
However, if I run the command as root after the system boots it works fine.Been using this method on other distros for over a year. No idea what the problem is.
For several days I stuck on a problem despite my various searches on the net. I just installed a machine in RC1 Squeeze.
My Partitioning
Disc 1
/ boot RAID 1
/ swap RAID 1 and encrypted
/ RAID 1 and encrypted
[Code]....
So, I installed AGAIN Squeeze
And again boot fails
Now it shows error 15
I tried booting into a LiveCD (ubuntu) to see what is happening
But I can't open grub.cfg file (you're not the owner, it says)
What do I do to boot into my new squeeze?
Is usplash supposed to work? It hasn't worked correctly in squeeze (for me) for some time. It appears for like 2 seconds never to be seen again. And I never see it at shutdown. I tried splashy, but no splash. Plymouth has been no go with nVidia cards. I don't know if that's changed, but I get no splash with that either. usplash doesn't seem to be in the sid repos. Is it obsolete, or just not packaged yet?
View 5 Replies View RelatedI cannot boot after installing Squeeze. /home partition is missing.
Here is the related information.
df -h
Code:
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 6.5G 4.5G 1.7G 73% /
tmpfs 1.7G 0 1.7G 0% /lib/init/rw
udev 1.7G 196K 1.7G 1% /dev
tmpfs 1.7G 0 1.7G 0% /dev/shm
[Code].......
I'm using Debian Squeeze on my Presario CQ40-115AU. Whenever Squeeze finished boot (when the login screen appears), there a loud beep sound come out. The same sound also come out when rebooting/shutting down my laptop and this had never happened when I'm using Lenny. Where can I configure so the sound won't come out ever again.
View 2 Replies View RelatedAfter doing a dist-upgrade today, my one year old install of squeeze will no longer boot. It stops with a black screen and has to be hard reset. Cant even get to tty1. The last line in dmesg is: cfg80211: Calling CRDA to update world regulatory domain
mike@vaio ~ $ lspci | grep Network 06:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100.Just wondered if anyone has any ideas before I restore from a backup?
Whenever I reboot, I get GRUB and the _ pinking, and that's it. With rescue cd I can have chroot shell, to troubleshoot I did the upgrade-from-grub-legacy and installed it to both /dev/sda and /dev/sdb In recovery I redid the upgrade-grub and grub-install commands but still have the same "GRUB and _ blinking".
Because the text "GRUB" and then nothing I didn't enouncter while googling, I need to ask here for further troubleshooting.
I tried installing a live version of Debian Squeeze 6.0.0 for the i386 architecture. I am using a first generation MacBook Pro (Intel Core Duo, not Core 2 Duo).
I managed to boot the live cd and install everything using the "guided installation" option, using the whole drive for Debian (I don't have the Mac OS X Snow Leopard disc so I just wanted to install a strictly Debian system). I installed GRUB to the master boot-record, but after finishing the installation and rebooting I was confronted with the dreaded "question mark". After doing a bit of reading, I found that I should have installed the EFI LILO bootloader to the MBR instead of GRUB, so I reinstalled everything, choosing this option instead. But that didn't work either. More question marks. I imagine I must have to configure either of these bootloaders in the shell, but I don't know how to go about doing this.
How to do this without using a Mac OS X installation disc.
i'm used eeepc here the situation i've already install squeeze AMD64 KDE but i want to try using i386 gnome which is more friendly for my eeepc spec. problem is there other boot in my pc. i'm currently using win7, ubuntu 10.10 32 gnome, and ubuntu ultimate 64 gnome and i don't have external HDD.
Question is i want to remove all linux OS and keep my win7 is it ok if i'm using Gparted to delete all linux OS and then installing deb squeeze i386. my next project is to build portable server on eeepc.
Before I ask I know what I'm asking is not recommended.
On Lenny It was possible to change the boot login to permit logins as root
I can't find how to do that since I installed Squeeze.
I've installed 6.0.1a on my xi3 box [URL] and it works great. However when I remove the monitor and keyboard it doesn't boot (I don't know how far it gets, there is no monitor...). I did not install, and do not want, any kind of GUI interface, command line only. This is going in a closet as a solid state rsync backup repo. I have another small system (not this exact one) running Lenny that runs just fine headless - is this some kind of Squeeze regression? Is there any way I can get this running headless (I can't run Lenny on this box because I don't think the Marvell GbE driver is there or is working in Lenny.
View 7 Replies View RelatedI've done the ordinary sources.list update (lenny to squeeze) and Code: sudo apt-get update sudo apt-get install dpkg apt aptitude.sudo aptitude full-upgrade However, udev failed to install, and I used..Code: touch /etc/udev/kernel-upgrade and did full-upgrade again. Everything was going fine, I went through several package configurations and suddenly, after 30-40 minutes of "Unpacking Setting up." I just heard two system beeps and got an error similar to a kernel panic. The SYSRQs did nothing. Did a hard reboot.I got two kernels in GRUB now. + the GRUB2 chainloading option. Used this one and got Code: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block It's all the same with the 2.6.32-5-686 kernel kernel panic. Using the older kernel didn't fail on the boot up, but showed many UDEV related errors and logging in was impossible - all I get were segmentation faults. Forgot to mention it - my FS is Reiserfs
View 7 Replies View Related'rolling' release as redoing install /upgrade every 6 months is getting 'old' My machine is triple boot
Hard drive is 320 GB
Windows 7 - 167 GB
Ubuntu - Maverick - 73 GB
Ubuntu - Natty - testing version - 65 GB
I do not want to screw up my 'grub' as it's been trashed a couple of times recently and had to re-install everything, which went great with install setting up partitions. I am not sure where 'grub' is installed to. I did install Windows 7 first then let installer split hard drive in half to put Ubuntu on then while installing my second Ubuntu, I let installer split the Ubuntu partition in half, hence the 167 GB Windows and the 2 smaller partitions for Ubuntu.I was thinking to maybe let Debian install over my Maverick install. Would that work and not mess up my Grub and cause me to not be able to boot and have to fix the drama?
I am using Gnome and Squeeze. I am wondering if I have a problem of understanding, or a problem that I found with Gnome.
My configuration is with a 3 hard disk system.
disk1 (Debian)
disk2 (XP and Fedora)
Disk3 (W7 and a Data partition)
When I boot and log in, all partitions for disk2 and disk3 are mounted read-write. Only by going to command line am I able to unmount the drives with the following sequence
cd /media
umount *
umount *
I should be able to mount and umount a drive by providing or responding to a root password. But I am not given the option to present a password. My request is blocked.
I also do not want to see the drives remounted after a boot. I tried to find out how this was managed, but I was unable to discover the module and it's parameter list that controls or does this task.
I have just installed Squeeze on my laptap with a radeon mobility equipped laptop. When it boots, I see the following message:r600_cp: Failed to load firmware "radeon/RV635_pfp.bin".and some others, too, but it stalls at that point, and I cannot use CTRL-ALT-F2 to get a text-based prompt - in fact, I can only seem to get it back with a ALT-SYSRQ (R-E-I-S-V-B) sequence to force a reboot. It is a multi-boot system, with a windows partition, Ubuntu partition, and the new Debian partition. The Ubuntu and Windows partitions will still boot, only the Debian stalls.
When I boot into Ubuntu, I can see the Debian partition, and can see (for instance) the /var/boot/dmesg file, but it only says:"(Nothing has been logged yet.)"So, being new to debian itself (even though, I know, that Ubuntu has a debian base), how can I make it boot without X, which is I presume, the center of the difficulty? Can I change some file on the debian partition using Ubuntu to get the debian partition to boot in text only mode, and then try to fix the radeon driver?
Alternatively, can I put the proper files for the radeon driver *from* the Ubuntu partition *to* the debian partition and expect it to load and boot correctly? I did, at one point, download and install the proprietary ATI driver files on Ubuntu, so can I put them in a proper place on the debian install?
I messed up my install so now I can't boot it. I get errors. I doubt I'll be able to fix it. I messed up the upgrade of the kernel images... I'm not sure whether there's something I could do in the Grub config file... I have one other Linux OS I can use in the meantime (plus Windows OS) so I thought maybe boot that up and check the Debian partition in case there's any files I want to save/keep. If I re-install, is Debian Squeeze LXDE still a good choice? I'm going to install something different in the partition where the other Linux OS is. Right now, it's grub is handling the boot loader. The computer is an old laptop, a Thinkpad T41. The HDD is 160GB.
View 3 Replies View RelatedI've got a fresh install of Squeeze on a 32bit host and I have been unable to boot into XEN/dom0.The Xen Kernel is "linux-image-2.6.32-5-xen-686" (pvops) and Hypervisor is xen-hypervisor-4.0-i386.The system default installed with grub2.It boots quite happily in normal mode, using the above Kernel, but just reboots itself if I try run it as Xen/dom0. (reboots within a second of pressing <enter> ... there is no messages displayed on the screen that I have noticed)The relevant menu (generated by /etc/grub.d/20_linux_xen) entry for running Xen is as below;
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN 4.0-i386' --class debian --class gnu-linux --class gnu --class os --class xen {
insmod part_msdos
[code]....
I've run into an issue that I'm not sure how to address. I'm running Squeeze and upgraded my system this morning.
The packages upgraded were:
About 10 seconds after upgrading, the system froze completely and I had to do a hard restart. The system froze again 10 seconds after the bash login prompt was displayed (I'm not using a display manager) after reboot. The source of the problem appears to be my Realtek 8192SE wireless driver. I was able to boot the kernel in recovery mode and uninstall it, which has fixed the issue. Rebuilding the driver causes the problem again.
I suspect that something to do with the sysv and init packages affected the driver in this way, but I've no idea where to start in trying to fix this. I can't imagine this is a fault of the Realtek driver as it worked just fine up until this point.
I recently purchased a new Lenovo Thinkpad T420i and am having problems installing the latest version of Squeeze from CD. After receiving the laptop, I started it up, configured Windows 7, and confirmed everything is working correctly. Next I went through the Debian installer, which completed successfully. I'll be dual-booting Windows 7 and Debian, so at the partitioning stage I resized my NTFS partition, added a shared VFAT partition, then used the "Guided" install to create my root and swap partitions. My partition layout is code...
I assumed something was wrong with grub, so I booted the CD into rescue mode and chose to reinstall grub onto the Master Boot Record. But nothing changed. Just to experiment, I went into fdisk, deleted all my new partitions (leaving just the Windows ones), and tried rebooting, but the same error happened. I then went through the Debian installer again, being careful to set everything up correctly, but still, the device won't boot.
I'm not even getting to the grub boot screen, so something is wrong even before the point. Reinstalling grub to the Master Boot Record (grub-install /dev/sda) isn't changing anything. How can I troubleshoot this?
I've had Windows XP Home installed on my netbook (Toshiba NB205) and I've just tried to install squeeze via net install. In particular, I installed grub. Everything seemed to go ok during the installation, but when I boot up, all that appears is a blank screen with nothing but at "j" and a cursor. One thing I can think of that might offer a clue, is that when asked to installed grub, the installer said it recognized two operating systems: Microsoft Windows XP Home, and Windows NT/XP. The latter is not really an operating system, but the backup partition.
I don't know how this might affect grub's functioning. What does this "j" mean? Looking at this: [URL]. Could this have some thing to do with boot flag? Should I switch it to my NTFS partition instead of my root partition? Doing that at least let's me boot into Windows. But that's not what I want. I've never dual booted before. So I booted back up with my USB, intending to reinstall Debian, and it loaded grub instead. So apparently grub is now on my USB. Then it booted me into Debian.
I cannot count how many times I have re-installed squeeze, and do all kinds of fixes to grub, but no joy. Every time, there is this ntoskrnl.exe error, and to re-install it. I thought my WIN XP may be corrupted, so I reinstalled it, and updated it with sp3 and all updates. Then I re-installed squeeze (reformatting all partitions). At the end, the installer ask if I want to install grub to mbr. I replied yes. After reboot, only the 2.6.32.3-amd64 and the recovery kernels show up on the grub screen, no winxp.OK, I booted into squeeze kernel and looked at the /boot/grub/grub.cfg file, and there winxp is not included in /etc/grub.d/30_os-prober section. In terminal, I typed
#os-propber and it found winxp in /dev/sda1
then I typed
#update-grub
and now /etc/grub.d/30_os-prober now show winxp.I rebooted, and winxp shows on the grub screen, and I chose winxp.It came back with "ntoskrnl.exe ...error... re-install ntoskrnl..."Here are the details:
fdisk -l
root@SHUM-AMD64:/home/shum# fdisk -l
Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
[code]....
This problem goes back to when I first purchased my laptop 4 years ago: Dell Precision M90. It came with Vista, but I wanted Ubuntu on instead. In order to get bluetooth to work, I had to downgrade the firmware. This is all fine and means bluetooth works in XP too. However, now, I have a dual boot with Windows 7 and Squeeze, I use Vista drivers (as Dell don't provide 7 drivers) and this has upgraded the firmware, and broken bluetooth in Squeeze. How can I get bluetooth working in both Squeeze and Windows 7? Could changing the hardware help? If so, what to?
View 2 Replies View RelatedI have installed vmlinuz and initrd.gz (squeeze) in /boot/newinstallation and added to Grub the lines:titleNova Instalaçãoroot(hd0,0)kernel/boot/newinstall/vmlinuzinitrd/newinstall/initrd.gzNevertheless, when I choose this option at the grub, it begins to start the kernel vmlinuz and thus restart the system. The installed Debian Lenny boots in a normal way.
View 10 Replies View RelatedI am still running the linux-image-2.6.32-5-686 kernel a computer with squeeze. I installed squeeze on it when it was unstable. I would like to bring up to the new stable state.Should I do apt-get install linux-image-2.6.32-5-686or should Iapt-get dist-upgrade
View 1 Replies View Related"drm_fill_in_dev *ERROR* Cannot initialize the agpgart module". I have this problem during boot-up since i first upgraded to Squeeze n it has not gone away after several upgrades. Web search indicates its a kernel problem but no solution found. Is there a solution for this now?
View 2 Replies View Related