I have a dell poweredge server. In the bios, it has the option to redirect the screen to the serial port. There is also the check box "redirection after boot" which from what I understand will let me to continue to use the serial port attached to a terminal as if it was the main VGA monitor with a keyboard attached.
When I start the machine up, everything goes as expected, I see the output from the bios on my serial terminal, until debian actually starts booting. It all goes blank. If i attach a monitor i can see it is indeed booted and waiting at the debian login prompt. What should I do from here? I was under the impression that if i enabled "console redirection after boot" that the os would be none the wiser and i could continue using the serial console as the main screen as needed, but that does not seem to be the case.
I'm always getting a blank console screen after booting a 2.6.32-trunk-amd64 kernel in squeeze. I still can read the line "Loading, please wait ..." in the display for a second - then it's completely black until X windows is starting. When I try switching from the X console to another virtual console (by pressing Ctrl-Alt-F1 e. g.), the complete system freezes. I have to hard reboot then.When I boot the previous 2.6.32-3-amd64 kernel instead, everything is fine as expected, though.There's a line "GRUB_GFXMODE=1024x768x16@60" in /etc/default/grub as well as a line "set gfxpayload=keep" in /etc/grub.d/00_header. So the problem might be framebuffer related in any way. Any ideas what could be tried?The system is a Latitude E6500 with a Mobile 4 Series Chipset Integrated Graphics Controller
I'm using a dell latitude d630 with an nvidia quadro 135M card. I'm able to suspend without any problems while running the X server. If I try to suspend on console without the X server running, the laptop wakes up to a blank screen. The screen remains blank and my only resort is to type sudo halt (with the screen off).I'm using the proprietary nvidia driver with the nvidia-kernel package on testing.
I am trying to pxe boot ubuntu 10.04.When it boot up,it doesn't show up login prompt from serial console ttyS0, Why ttyS0.conf job isn't invoked automatically ? is there anything wrong with configuration?
I've got a home server running ubuntu 10.0.4. It have no monitor or keyboard. So I want to access it from a serial console. (I use SSH currently but if something goes wrong, I need to be able to do something... so serial console seems a fine thing). OK, so on the server, I tell grub to output everything on ttyS0 and opened a getty on ttyS0. On the client side (Laptop running Ubuntu 10.0.4 with pl2303 USB to Serial adapter) I use Minicom.
Home server restart:I see grub menu, linux kernel messages, login prompt. But, I can't do anything:In grub or at the login prompt, no key press is recognized by the server.I've got write permission to /dev/ttyUSB0. I tried a different getty (mgetty)with no success.I stopped the getty on ttyS0 on the server. And run minicom.
From the server's minicom, if I type something, it appear on the client screen. From the client's minicom, if I type something, some garbage appear on the server screen :(One of this things for each char typed). If I short-circuit pin 2 and 3 of the client serial port, it echoed what I type. The two serial ports are connected with a nullmodem cable. (seems to be a full handshaking cable). Of course, same serial port config for both minicom, grub and getty. Hope I'm understandable enough. (English not my primary language). Can somebody help me make this *$*#! serial console working right ? I'm on it for 10 hours now with no success...
Edit : I nearly forgot to tell you I had to update the standard ubuntu kernel to 2.6.34-020634rc1-generic because there was a bug in the pl2303 driver in the stock kernel (2.6.32-25-generic) which prevented me from doing anything (even receiving).
i was using a serial console program (not minicom) two weeks back but took a break and have no idea what it is! man, it was awesome, too. it had a nice gui, similar to hyperterminal...and from what i think i remember it came packaged with f14.
I am hoping to be able to get an old serial-touchscreen to work with a usb/serial adapter. I had this touchscreen working some years ago on different hardware. I would like to hook it to the machine I am setting up as a multimedia host with mythtv among other things.
Following the instructions I left behind when I got this to work way back when does not work. See [URL] ....
This info is a work around to get the xserver to see the touchscreen. [URL] ....
I do know that the touchscreen works as I am able to get garbage on the screen as in the first part of my howto. But I have not had any success getting xorg to see it. I wish I had posted a copy of the xorg.conf at the time, but......
There is an issue with the current xserver in testing that I am hoping the next update (in unstable) will fix when it gets pushed to testing. That is that Code: Select all# X -configure fails with a segfault. So I am not able to generate the xorg.conf needed to get it to work. I was going to post a bugreport, that is when I found out there is an update in unstable, so I am waiting for it to get pushed at the moment.
Anyway I am hoping that I can link /dev/ttyUSB0 to /dev/tty0 and get it to work. I would like some kind of guess as to my chances of success before I go to all the work of getting the monitor hooked to the host.
I am looking for a solution to administer my remote server running SUSE LINUX 10.1 (X86-64) - Kernel 2.6.16.13-4-smp. I have made changes to server and is able to see the boot process and also able to login to system through serial console.
My question, will I be able to administer the server through serial console incase if my root partition is corrupted and system has gone to maintenance shell(or root shell).
Also is there way to go directly to maintenance shell from grub(not talking about single user mode). I want to go maintenance shell where / partition is not mounted.
I have installed KDE and all the software for it to run on my server through the serial console but when I go and run "startx" I get the following and KDE doesn't start running.
root@u15434060:~# startx X.Org X Server 1.7.6 Release Date: 2010-03-17 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.24-28-server x86_64 Ubuntu
Is there a way to get console output over a serial (COM) port? I have a box that I use as a NAS, DNS, DHCP and mt-daapd server, I don't have a spare monitor and it is not worth buying one just to use it once or twice a year.
I found this guide [url] but it doesn't work with Natty
I am trying to connect to a cisco console port using the usb to serial converter. I am using minicom and I changed me setting to reflect the USB converter cable, but it isn't working. I have set my baud rate to 9600, 8 data bits and no parity. Minicom acts as if it is connected (it doesn't give any errors), but there is nothing on the screen and nothing happens when I type. Also, I use the tail command and it sees the usb connector connected when I unplug it and plug it back in.
I am trying to connect to serial console, local one, just to verify than it works, is is possible?Well, I configure serial console
Code:
# ttyS0 - getty # # This service maintains a getty on ttyS0 from the point the system is # started until it is shut down again.
[code]...
It is started, now I am trying to connect to the console via minicom, is it possible from machine where the console is running?If not, how could I check it remotely?
I have console only on my machine and I have two problems with it:
1) I can't find how to enable programmer dvorak keyboard layout.
2) All the console settings don't stay after reboot, I have to do dpkg-reconfigure console-setup again. But after I do that I loose russian layout that I normally can switch to with Alt+Shift.
I've recently installed a new graphic card after my old one started to go belly-up and it works nicely in X with twinview. The card have one VGA, one DVI and one HDMI. I have the monitor connected to the VGA and my projector connected to the DVI. However, when I boot the monitor (VGA) don't receive a signal. It is dead until X comes up (and when X comes up it does exactly what I want, it uses the VGA monitor as the main screen).
I had this setup on my old card to and it worked fine. Grub and boot console showed on both screens and I never had to tweak anything to make it do this.
how to enable the VGA outlet, either have boot enabled or only the VGA enabled (either way is fine by me but I really want to see Grub and the boot console on startup).
I have an system that d8.2 appears to install correctly. On first (or subsequent) boot, I get the DB8 load screen, then a quick fsck, then nothing. I appear to have some sort of environment running as I can move a mouse pointer, but nothing else.
CTRL-ALT-F2 results in the mouse pointer vanishing, but nothing else. I expected to end up at the CLI.
I have tried different installs and options, always the same result. This machine ran an earlier version with issues.
I have this machine (motherboard ITX Jetaway NF94-270-LF based on CPU Atom N270, full specs here) as a server for some time now (about 4 years). Debian 8.1 is installed on it.
Two days ago, after a power failure, the machine was not able to complete the boot process. I attached a keyboard and a monitor (on VGA port, the motherboard also as a DVI one, but I don't have a suitable monitor) to be able to see what's happening and interact with the machine. Unluckily, at a certain point during the booting sequence the screen goes blank and the monitor goes in standby mode; apart from that, the boot process continues in the background.
As far as I can recall, this behaviour existed for at least a couple of years (if not from the beginning) and the boot process was always completed successfully until two days ago.
The screen goes blank after the setup of the keyboard mapping. I tried everything to avoid the screen going blank: in the Grub menu I set the "vga" parameter, the "nomodeset" parameter, the grub_gfxmode parameter, I removed the "quiet" option, I removed the "load_video" line, I forced the BIOS to only use the VGA port for the video and so on, in order to disable or configure differently the video and the framebuffer. All these stuff had no effect at all: the screen keeps going blank at the same point during the boot process.
The only way I was able to use a fully booted system through keyboard and monitor was via the rescue mode of the Debian 8.1 netinst image. But that way, of course, I wasn't able to observe the normal boot process. So, I checked the boot parameters of the rescue mode and I found that the only usefull parameter was "vga", which I already used and was ineffective.
I have some problem with Debian 7. Just installed Debian 7 wheezy.
Motherboard Intel D2500CC, graphics - Intel GMA 3600. Monitor (BenQ V2200 Eco) connected via VGA cable. No X server installed.
After GRUB boot as soon as modesetting kicks in, the monitor loses the signal and goes black. Keyboard does appear to be active, as Ctl-Alt-Del will cause a reboot.
I tried nomodeset, vga=791, 771 etc kernel parameters, but this won't work.
I have just installed Debian 7.8.0 powerpc on my imac G3 (400Mhz, 256Mb Ram). I had repartitioned the drive with the view of having a dual boot machine, had OS9 installed on partition 1, linux installed on partition 2 and a ext4 data partition and a 1Gb swap partition. After I installed OS9, I ran Debian Installation CD and was successfully installed. Rebooted, got through the on screen text past file system check, then screen went blank. I searched Google and forund that if I ran ctrl+alt+f1 and logged in, then ran lspci, I could get the ID of the graphics. So I did, and:
I'm trying to make dual boot system with Lenny (64bit) along with WinXP. I'm using one HDD with 2 partitions and installed first XP then Lenny. Everything seems fine till the first boot after fresh install. Lenny starts to boot and after same point the screen goes blank and then is turned off and that's it...nothing happens. Happens so fast that I'm unable to see the exact messages on the screen. Maybe somewhere around staring anarcon?
PC is: Athlon64 X2 5400+ Asus M2V-MX motherboard 3GB DDR2 800 500GB WD SATA2 HDD Radeon x800 GTO video
I reinstalled 2 times and it's the same. WinXP is working fine though but I really don't want it to be my OS... Another "hint" from today: The same happens when I use "Try without installing" of Ubuntu 10.04(i386) Live CD. It starts loading and at some point turns off the monitor. Tried also with 8.04(64bit): Boots till it reach something like "Settings sensor limits" and then it's stuck. I have consoles though (Ctrl+Alt+F1/2/3...).
I just recently got a Dell Inspiron 1525 laptop and have installed Debian on it. When I installed it, I did not install the 'Graphical desktop' packages...only the 'Standard system utilities'Everything has been fine, however when I installed Xorg (aptitude install xorg) and restarted my computer, my screen goes blank at bootup. I can see the grub menu, as well as the beginning bootup process, up until udev begins to load. I have a feeling it has something to do with KMS now being loaded but am not sure.
I am having a problem getting my virtual console back after starting XWindows. The display goes blank when I press Ctrl-Alt-F1. If I press Ctrl-Alt-F7 I get the X session back. I have tried setting vga=x31A on the linux boot up. Also tried rdev -v /vmlinuz -1, and rebooted. I have tried two different monitors, same problem. One is a an LCD (Philips 170S6Fb/27, the other a Samsung Sync Master 750s. Originally the Samsung worked fine. I could switch between X and VC no problem. Now that I have the LCD monitor working after changing the XF86Config, I have this problem.
My kernel is 2.2.15-5.0, Redhat 6.2. Here is the output of lspci for the video card:
00:0c.0 VGA compatible controller: ATI Technologies Inc 3D Rage II+ 215GTB [Mach64 GTB] (rev 9a) (prog-if 00 [VGA]) Subsystem: ATI Technologies Inc: Unknown device 4755 Flags: bus master, stepping, medium devsel, latency 0 Memory at e2000000 (32-bit, prefetchable) I/O ports at b400 Memory at e0000000 (32-bit, non-prefetchable) Expansion ROM at 000c0000 [disabled]
Hopefully there is someway to control how linux sets the video mode when switching consoles.
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 had ubuntu studio installed ( for the record I hated it and every ubuntu flavor I have ever used. ) After backing off all the stuff from my home dir I started to install testing from a dvd. ( Is there a net install for testing? I couldn't find it) Don't ask me how it happened but some times I would have two grub graphical boot menus. One would chain to the other. I suspect that happened from one of the very friendly updates ubuntu did. Well when I tried to install testing I got a red screen telling me that grub wouldn't install so I tried lilo. Well it wouldn't install either. Back in the old days when I was a slackware guy installing from a stack of floppies I had a trick to wipe out any boot loaders or other stuff that gave me a problem. I would dd if=/dev/zero of=/dev/<drive info such as hda with no partition number> .
This would write zeros over the drive and it would look like a new drive. So I did this trick. But still no joy ( this is a clue, dd was also thinking that the beginning of the drive was after the boot sector.). I suspected that the installer wasn't doing it's job right. So I got a PCLinuxOs disk and started that installer. The PCLinuOS installer has a cutesy visual bar that shows the partitions. Well sure enough the boot sector showed as blank. This was what the Debian installer had done. It left the boot sector blank and tried to install the boot loader right after it. This won't work. Now I consider when some version of Linux falls on it's face and another version does it right that the version that fell on it's face has a problem.
One might even call it a bug. But I don't know what to do about it. I don't think the problem is with grub or the installer itself. I think how the drive was looked at was faulty. That's why dd didn't blankout the boot sector. So what do I do to help get the Deb people to fix this? The more I think about it the more I think the problem is with udev ( what a surprise) I think this because I suspect dd looks to the info set out by udev to find the beginning of the drive.
I have a new laptop, I first installed Debian stable, but the wifi card didn't work, and the screen was 1024x768. So I installed kernel up to 3.16 with wheezy-backports, but after the boot, the screen become blank. The only way to see the screen is set "nomodeset" in /etc/default/grub, but It's impossible to see the screen beyond 1024x768 resolution.
I also tried to install linux-image deb packet from [URL] .... , because it worked for someone in internet, but not for me.
I've been using ubuntu on a new desktop for a couple of months, but i had an old HP that was given to me in my basement. It has 384Mb of ram, and thats because i had a 256Mb stick laying around. I installed debian becuase it is more suited for older hardware (at least from what I've read). It installed fine, but it boots to a blank screen, and pressing ctrl+alt+F2 bring me to the command line. I checked /etc/X11/xorg.conf to change the driver to vesa, to find out my video card isn't even shown. I ran lspci and I found that it says my graphics card is Intel Corporation 82810E DC-133 (CGC) Chipset graphics controller (rev3) In the device section of xorg.conf, it merly says Identifier"Configured Video Device"
I am trying to get two way serial communications going between a Windows XP system and a Linux system (RHEL 5).I have /sbin/agetty -L 9600 ttyS0
in /etc/inittab. I am using a generic USB to serial adaptor on Windows (Unitek) and a null modem cable. I have putty configured for 9600 baud, 8 bits, no parity, one stop bit, no flow control.I get the login prompt from agetty in the putty window but input does not work; I see weird characters in the putty screen. I can echo output into the device from windows and see it, but
cat < /dev/ttyS0. just prints out weird characters from what I type.
On my CentOS 5.2 install I've installed a dual-port serial card based on the NetMOS 9835 chipset. I've followed the serial instructions, but everything they tell me to do is already done - see setserial outputs below. I've compared these values to the lspci output (below, NetMos card is at the bottom of the output) for the card and it appears right. Problem being, I can't use the serial ports. Oh and I did use search, and looked at every 9835-related article before posting this :)
I have a bit of a dilemma. I'm attempting to use a microcontroller to send MIDI messages over a virtual serial port. I want to (eventually) read them with Mixxx. I'm using an FTDI chip, so I get a /dev/ttyUSB0. I've tried spikenzielabs' Serial-Midi program, but it doesn't see any serial ports. NOTEMIDI looks really old and won't compile on my 10.04 LTS machine.
