I just installed Debian6-squeezie and upgraded to wheeny, that went fine for itself But now i discover that Debian INSIST in changing my BIOSCLOCKI realy dont like that. Its MY computer and I dicide MY SELF if i 'follow' winter versus summer time commercial brain-f#ck.
I'm successfully dual booting and running Windows XP and Fedora 11 (with EVERY recent update installed), everything works fine EXCEPT that I cannot get both System times to synchronize.. Evey time I run Fedora I find the system time is always an hour different to Windows. Evert time I correct the system time in Fedora it affects my BIOS time settings. If I then go into Windows I first have to go into the BIOS and correct the BIOS time setting by one hour before I get the correct time in Windows........ Nothing is wrong with my Windows side of things, I know this because if I don't log into Fedora then my system times stay correct, only when I correct the settings in Fedora (which are always an hour out) do I get my BIOS changed. Also in Fedora, although I live in the UK (London) Fedora ALWAYS DEFAULTS TO Guernsey, no matter how many times I correct this to LONDON, Fedora always defaults back to Guernsey.... Has anyone else experienced this as I'm sure it's a Bug in Fedora, surely it shouldn't alter my BIOS settings, should it ??
I want reliable way to print bios clock. Using Redhat 5.5. "hwclock --show" command prints out bios time in local format. So if linux is configured UTC=false when "hwclock --show" is the same as bios clock, but if UTC=true "hwclock --show" still prints local time and I must adjust it according to my TZ - something like `hwclock --show`-2 (only example). So method above depends on UTC setting. Is there an unambigous method to print bios time? (Only os interprets bios time as UTC or local - value of bios time is the same if time is not changed).
When I start my computer sometimes I get an error that my floppy drive isn't working and the boot process is halted. So I disabled the floppy disk seek. But Once in a while (sometimes almost every time I start) the BIOS settings are reset and I have to disable floppy disk seek and reorder boot device list again. I have checked the battery and it's fine. What else can be the problem?
System time was drifting ahead increasingly for several days time in the end. This is what I did with the clock about 6 hours "in the future":
Quote:
sntp -P no -r pool.ntp.org hwclock --systohc
i.e. I got the (more or less) exact time from the time server and set the hardware / BIOS timer with this value.I renamed "/etc/adjtime" to beginn with a clean slate. During reboot (shut down phase) I noticed a message saying something like: "hwclock set to system time". I checked in the BIOS and there was a new time about one hour early(!). The boot phase then reset the time again, this time several hours forward (usually two to six hours). This is an iterating process, with a net gain of several hours per boot. It is not always whole hours -- like in a time zone error but it involves also minutes. System is set to UTC as affirmed by the "date" command. What could be the cause of this behaviour of the clock / timer?
I have Ubuntu 10.04.1 32bit installed on my flash drive so wherever I go I can have my own mini personal computer, but one problem I'm having is every computer it is run on the next time it's rebooted to the OS on the hard drive it has UTC time instead of the actual time for the timezone you're in that Windows uses. So is their a way I can make Ubuntu not automatically change the clock to what it wants?
I've got two laptops running Ubuntu. Both have had Lucid installed from the live cd. I have upgraded one of them to Maverick. Both distributions are running great after they boot up, but I haven't experienced any faster boot times with either distibution. Both boot to Bios and then the screen goes black with a blinking cursor in upper left corner of the screen. The black screen remains for 30 to 45 seconds and then I get the Ubuntu splash screen for maybe 5 seconds, and then desktop. Why am I not seeing faster boot times? I realize 45 to 60 seconds is good compared to other os's, but I anticipated much faster boot times. Shut down on the other hand is quite fast at maybe 5 to 10 seconds. Does anyone else get this black screen on boot? Seems like wasted time cause I can't tell what's going on during the time there is a black screen. This is not a real big deal breaker, as I don't reboot very often, but I just wonder why bootup isn't faster.
Since the upgrade from Lenny to Squeeze on my Notebook Toshiba Satellite Pro U200 with Intel Pro/Wireless 3945 ABG I have wireless connection problems.The connection breaks time to time and sometimes cannot connect automaticaly after restart. BTW I didn't change anything on the wireless or network configurations on the notebook and on the wiereless router.
I have a Insprion 14R (N4010) and when I hibernate it will usually restore without a problem, but maybe 15% of the time it will reboot while loading. I would like to figure why, since I'd rather not lose anything... My swap space is 5.9GB, I have 4GB RAM (video uses 1gb, so I have 3gb usable)
I am having problems installing linux on an old PC with the hard drive shredded, old CD drive, old 1 GB RAM card. I want to make sure the problem is not that the memory is partially bad.I recall that there should be some way to get the BIOS to test the memory overnight, but couldn't find this mentioned in the books I checked or in my notes. I believe that the motherboard is made by ASUS, if that helps. When I power on and hit the delete key, I do get some BIOS options, but memtest is not mentioned.
I want to be able to access an old pc at home from any computer but I don't want to leave the computer on all the time (I won't use it regularly and I don't believe in wasting energy just cause I can). I've heard that some bioses have wake-on-LAN but I have no other machine on the LAN that will be left on (apparently it's impossible to wake a computer from off the LAN???) so my solution is to buy a raspberry pi (perhaps there is something cheaper/better??) and leave that on that I can ssh to from anywhere and then wake my pc from there. Unfortunately my bios doesn't have a wake-on-lan function and so I'm hoping that I can update my bios to a version that has a wake-on-lan option (perhaps there is a better way?).
oli@deb-serv:~$ lsb_release -a No LSB modules are available. Distributor ID:Debian Description:Debian GNU/Linux 8.2 (jessie) Release:8.2 Codename:jessie
[Code] ....
So I've started to try and find a new bios to update. I think I need one of these: [URL]
I have been running Jessie on an EFI motherboard for a while, booting just fine from a GPT formatted partition on my 3TB hard drive.
I had to re-purpose that PC, and put the hard drive into a different system that uses a BIOS instead of EFI.
Now when trying to boot, I get a text at the top of the screen that says:Code: Select allGRUB ...so it finds GRUB, but nothing ever happens. <CTRL>+<ALT>+<DEL> resets the system.
parted 2.3 says:Code: Select all 1 1049kB 3001GB 3001GB ext4 boot 2 3001GB 3001GB 32.5MB bios_grub, legacy_boot(I set the legacy_boot flag trying to fix this problem, but that flags the partition, not the MBR)
Is my problem that the "bios_grub" partition is at the end of the disk instead of the beginning?
I have read that newer versions of parted allow you to toggle the "pmbr_boot" flag directly in the MBR by using the command "disk_toggle pmbr_boot" or "disk_set pmbr_boot", but parted 2.3 apparently doesn't support this.
The pmbr_boot flag in the MBR seems more likely to be the problem than the partition at the end of the disk.
Do I need to find a newer version of parted that supports the pmbr_boot flag for MBR (if so, which version please), or do I need to move the partiton to the beginning of the disk?
I was using Arch Linux and encountered an issue with dmraid because it thought my array was removable, which it wasn't. Without any answers or being able to revert to an older kernel, I gave up and switched to Debian, which read my array fine. However, today I updated Debian (sid) and got the 4.4.0 kernel, and the same problem came up... Right now, I'm still running 4.3.
According to this link:URL....the problem is clearly because of the kernel, though technically, the kernel isn't wrong. But unlike the people in that link, I don't have an option in my BIOS to disable hotplugging for my array.
I got a new monitor (a used one), so i hooked up my very old PC. I went to the living-room and checked something. I went back and got a black screen. i did a "cold reboot" (?) and: nothing. Not even the BIOS-messages.
Now i am missing the terms: I replaced the "thing" where the monitor gets plugged (i would say its a PCI-slot, but as the graphics are build-in it doesn't seem to be a graphics-card. I simply don't know. I searched for PCI-slot +monitor and that picture should show it: picture). I rebooted with a live CD and voila: i get a screen. I rebooted into the installed OS and i get a screen. Then it freezes. "Cold reboot" (if it is called that way): again nothing.
So I just recently got an HP pro 1005 all in one PC and tried to install Debian 8.2 on it through a bootable Uefi USB, however, when trying to install, there's always an error like this: "The attempt to mount a file system with type ext4 in LVM VG debian-vg, LV root at /failed."
Also, no matter how many times I completely wipe every partition, there's always this message at the start of the installation saying Windows is already installed as BIOS compatibility mode, and asks me if i still want to install as Uefi, I was wondering if that had anything to do with my error.
I checked the drives health and there wasn't any kind of problems, passed all the tests.
My external USB drive came formatted NTFS. It had a list of compatible OSs on the back of the box.Debian was not listed. I reformatted it during installation never planning to use it for NT. My BIOS just happens to be Phoenix. I have everything up and running fine. I just have to remember not to forget the startup sequence in order to avoid a permanent non-transitory Grub Stage1.5 Error 21. I don't want others to have to clean Grub or start over if it's unnecessary and there is a work around as simple as a startup sequence. Nor am I pointing the finger at Phoenix.
My external USB drive has its own separate DC power supply apparently needing more power than a thumb drive or what it could pull from a USB port. Here's a picture:
Back of the external USB drive WDBAAH0010HCH-00.jpg (11.33 KiB) Viewed 195 times
I have Debian Jessie 8.0 amd-64 installed. It is a dual boot system with Widnows 8.1 alongside. Both the systems work fine with a few glitches coming at times on jessie. But I assume it should get stabilised with time.
Problem is:
The usb keyboard is no longer detected until the GRUB stage crosses.
* This implies I am unable to press F2 to enter into BIOS * I am unable to chose Windows 8.1 by using arrow key on the keyboard.
When the default system (first in the grub list), in this case Debian is selected after time runs out then the keyboard comes back to life and works properly thereafter.
So far I have tried the possible solution given at [URL] .... but it did not work.
Some Information ================
$ lsb_release -a No LSB modules are available. Distributor ID:Debian Description:Debian GNU/Linux testing (jessie) Release:testing Codename:jessie
i am working with an old system that uses a BIOS meant for embedded systems. According to my coworkers this thing boot some version of debian about two years ago. currently I have used there old image and a new one I made of the latest Debian stable build. both images fail to get passed grub.
to be clear the BIOS simply replies "loading grub" takes ten minutes and then crashes.
has anyone ever had trouble with grub crashing systems? this problem seems odd since is did boot with this two years ago and i still have that image.
I'm trying to install Debian Lenny on my new Dell XPS 8100 Desktop with 2 x 1To SATA HD. (No Windows or any other OS install is present on the system) The Bios allows me to change the SATA mode to either "ATA" or "RAID"
- When SATA mode is set to RAID, the installation goes without issues, but when it comes to load into the system, I've got that Stage 1.5 Grub Loading... Error 2 problem. I assume this is due to the Bios "RAID" configuration. I then switched the SATA mode to "ATA" in the Bios and now I can see the menu that allows me to boot my debian install but that part actually fails too saying "ALERT /dev/sda1 does not exist"
- When SATA mode was set to ATA, I tried to re-install the system but this time my drive was not recognized by the installer: "No common CD ROM drive"
I have a backup HDD with a different distro for my laptop and i can boot into it via external usb or if swapped into the laptop. This HDD/install in question is debian testing and was working fine, the issue arose suddenly. I was first suspecting a failure of hardware somewhere on the motherboard, but the hdd i was using with an external usb adapter also works when installed into the machine. also, the HDD is recognized once i have booted using the external HDD and distro, but it is not recognized by the bios. so i dunno, my first guess is something became corrupt within the testing install, but i guess its also possible that there is some wrong with the HDD but thats not immediately apparent as all the data is still accessible.
Should also note that the HDD with testing on it is also recognized when connected via the external usb adapter, while booted from alternative distro/HDD.
Also. just tried this, but i can get the testing HDD/disto to boot if connected externally. it was going pretty quick, but there i did catch a line about a corrupt filesystem. any commands to run to see what might be going on?? log files to look at?
I've been using Ubuntu since 8.04 and I'm getting tired of it. Every time I update to the latest version, even if I wait awhile, something always breaks. I want an OS that I can update without having to worry about something breaking and I hear that Debian is great for that. I'll be installing it in a few hours when I get back from Iron Man 2. I just created this thread because I know I'm going to have questions. Don't worry, I'll try to solve any problems I come across myself before asking here. I'll be installing Debian Stable because I figure that'll be good enough for me.
I guess this might sound strange, but, I want to be asked all the time for either my user password or root password. I have searched high and low and all I can find is people wanting to disable asking for password. My guess is a majority of those users are ex-Windows users. I prefer to be asked as I feel it an added security tool. how to enable the system to ask for the user/root password everytime?
I have only one OS ( Debian 'Squeeze' 6.0.1 ) installed on this system. I observe a time lag which gradually grows. I was asked to install ntpd to prevent this from happening in the future and I did install it which seemed to work for a few days but now I observe the lag again. Just to note, I notice it only when I hibernate my system.
when im trying login in my web ftp with correct pass and username its automaticly refresh the page. I have instaled easy-wi for i can make servers, but ftp dont works. Second problem is cronjobs. i dont know how to enabkle for this panel.
I bought my previous laptop without thinking about whether linux would run or not, I ran into a lot of ton of trouble and had to use ndiswrapper for the wireless and I had to wait year before a patch came so the monitor could be used, and 1 year before it ran stable (back then I used ubuntu). I have a medion computer, their consumer service are very nice, however I fried the hard drive, and when I got the computer back the wireless card weren't visible from linux... I then went into the bios to find out that there were only 2 settings to choose between "off" and "last state", and last state apparently also meant off... in windows both off and last state could be turned into "on" by clicking Fn + F7... but this did not change the bios setting and therefore linux wireless were still off (I know it sounds strange).
Anyway My girlfriend needs a windows computer for gaming (and all of out computers run only linux with the exception of mine which dual boots), so I have desided to buy a new one. My main question is this: which laptop manufactures play nice with linux... I have heard only bad things about dell costumer service, and I want to buy a laptop that I can return w/o to much hassle if it doesn't perform as I am hoping...
My second question is, is there any way to check whether the graphics card and such are compatible with linux ahead of time, (w/o acualy buying it where you can do lspci and then submit it to some webpage) 3rd are there anyway to check whether the fn + key buttons and webcamp works ahead of time (this is only of minor importance, as I find that generally the sound up and brightness up/down works, and that's the most useful)
When I try to open two times Iceweasel I get this:Iceweasel is already running, but is not responding. To open a new window, you must first close the existing Iceweasel process, or restart your system.I am very suprprised, because in Windows xp I can open mozilla firefox 2,3 or more times.
Imagine i want to power off my "Lenny" at exactly 16:00 everiday. no mather what I suppose i showld write a script with the shutdown command and add it to the /etc/init.d . but i will listen to your tips first.