Re: x : keyboard not working
On Fri, Oct 06, 2017 at 11:08:07AM -0400, Greg Wooledge wrote: > On Fri, Oct 06, 2017 at 05:02:45PM +0200, to...@tuxteam.de wrote: > > On Fri, Oct 06, 2017 at 08:22:41PM +0530, Mayuresh Kathe wrote: > > [X keyboard not working] > > > > This depends on a couple of things. E.g. is your X using X input? > > The more likely candidate is a lack of focus on the correct window. > Depending on the window manager in use, and how it's configured, you > may either need to click on a window, or have the mouse pointer > constantly hovering on that window, in order to be able to type there. > > The former behavior is called "click to focus", and should be familiar > to Microsoft Windows users. > > The latter behavior is called "focus follows mouse", and is the > more traditional X window manager behavior. > > If you actually start X without ANY window manager, you get a borderless > xterm window in the upper left corner. In order to type in that window, > you will need to move the mouse so that it's inside the window. > in this case, you can rule out that candidate. i have been working with unix and unix-like systems since 1997, have been aware of that mouse-focus scenario. :) nevertheless, followed your advice, and did click on the window under "mwm" and hovered over the window under "twm", neither provided me with the required support for keyboard input. for that matter, even "ctrl+alt+backspace" doesn't work to shutdown the x server. :( ~mayuresh
Re: x : keyboard not working
On Fri, Oct 06, 2017 at 05:02:45PM +0200, to...@tuxteam.de wrote: > On Fri, Oct 06, 2017 at 08:22:41PM +0530, Mayuresh Kathe wrote: > > [X keyboard not working] > > This depends on a couple of things. E.g. is your X using X input? > If yes, it's supposed to work automagically. If not, you might need > to put a stanza in your /etc/X11/xorg.conf which looks more or less > like > > Section "InputDevice" > Identifier "the-keyboard" > Driver "kbd" > Option "XkbModel" "pc104" > EndSection > > or something similar. > > Could you post your X server's log? Where is it located? > (the two possibilities know to me are ~/.local/share/xorg/ > and /var/log/Xorg.0.log, depending on whether your X server > runs rootless or not). sure, your stanza for /etc/X11/xorg.conf didn't work, it just refused to startup the X server itself. actually, that file itself did not exist at that location, i had to create it, and when it didn't work, i deleted it, and the same old stuff was on again, i.e. X worked, but keyboard didn't. please find below my X server's log; [ 533.054] X.Org X Server 1.19.2 Release Date: 2017-03-02 [ 533.060] X Protocol Version 11, Revision 0 [ 533.063] Build Operating System: Linux 4.9.0-3-amd64 x86_64 Debian [ 533.065] Current Operating System: Linux tiny 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) x86_64 [ 533.065] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-3-amd64 root=/dev/sda2 ro quiet [ 533.069] Build Date: 07 July 2017 06:14:06AM [ 533.072] xorg-server 2:1.19.2-1+deb9u1 (https://www.debian.org/support) [ 533.074] Current version of pixman: 0.34.0 [ 533.078]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 533.078] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 533.088] (==) Log file: "/home/mayuresh/.local/share/xorg/Xorg.0.log", Time: Fri Oct 6 21:12:15 2017 [ 533.121] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 533.122] (==) No Layout section. Using the first Screen section. [ 533.122] (==) No screen section available. Using defaults. [ 533.122] (**) |-->Screen "Default Screen Section" (0) [ 533.122] (**) | |-->Monitor "" [ 533.123] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 533.123] (==) Automatically adding devices [ 533.123] (==) Automatically enabling devices [ 533.124] (==) Automatically adding GPU devices [ 533.124] (==) Max clients allowed: 256, resource mask: 0x1f [ 533.151] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 533.151]Entry deleted from font path. [ 533.156] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 533.156]Entry deleted from font path. [ 533.156] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist. [ 533.156]Entry deleted from font path. [ 533.156] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 533.156]Entry deleted from font path. [ 533.156] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/100dpi, built-ins [ 533.156] (==) ModulePath set to "/usr/lib/xorg/modules" [ 533.156] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 533.157] (II) Loader magic: 0x5636ced75e00 [ 533.157] (II) Module ABI versions: [ 533.157]X.Org ANSI C Emulation: 0.4 [ 533.157]X.Org Video Driver: 23.0 [ 533.157]X.Org XInput driver : 24.1 [ 533.157]X.Org Server Extension : 10.0 [ 533.161] (++) using VT number 2 [ 533.170] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_33 [ 533.172] (II) xfree86: Adding drm device (/dev/dri/card0) [ 533.174] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0 [ 533.178] (--) PCI:*(0:0:2:0) 8086:22b1:103c:82e1 rev 53, Mem @ 0x9000/16777216, 0x8000/268435456, I/O @ 0x1000/64, BIOS @ 0x/131072 [ 533.178] (II) LoadModule: "glx" [ 533.181] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 533.412] (II) Module glx: vendor="X.Org Foundation" [ 533.412]compiled for 1.19.2, module version = 1.0.0 [ 533.412]ABI class: X.Org Server Extension, version 10.0 [ 533.412] (==) Matched modesetting as autoconfigured driver 0 [ 533.412] (==) Matched fbdev as autoconfigured dri
Re: 9.1.0 : netinst : installs well, but useless after firstboot
On Fri, Oct 06, 2017 at 02:07:27PM +0100, Brian wrote: > On Fri 06 Oct 2017 at 17:41:23 +0530, Mayuresh Kathe wrote: > > > On 2017-10-06 04:06 PM, Brian wrote: > > >On Fri 06 Oct 2017 at 13:34:55 +0530, Mayuresh Kathe wrote: > > > > > >>On Fri, Oct 06, 2017 at 06:03:24PM +1100, Zenaan Harkness wrote: > > >>> > > >>> Are you sure? You may be right - but double check to make sure... > > >> > > >>yes, i am very sure. double checked. the interface wlo1 exists. > > >> > > >>there's a procedure mentioned in the wiki which shows how to setup > > >>wifi via wpa_supplicant through modifications to the file; > > >>/etc/network/interfaces > > >> > > >>it's now working, but not automatically coming up, i still have to > > >>manually issue 'ifup wlo1' in spite of having mentioned "auto" in > > >>the configuration file for the "wlo1" interface. > > >>off to check on that now, but if someone has any advice, please do > > >>share, it would be most welcome. :) > > >> > > >>it kind-a sucks that the debian installer accepts all the wifi > > >>parameters, activates the network only during installation and > > >>then does not include that information for post install work. > > >>atleast provide an option during the installation to accept the > > >>parameters and have them persist after the installation is done. > > > > > >What DE did you install from the installer? > > > > 'de'? desktop environment! > > i did not install any graphical system, i prefer to work at the text > > console, that's why i am on debian, else would have been on ubuntu. > > Not installing a DE is why connectivity did not exist. The outcome is by > design but the reason for it it has never really been given. I think the > idea is that, having not selected to install network-manager you > definitely do not want what the installer has produced and desire to set > up your wireless network with your chosen software. Which is precisely > what you are doing now :). Please see the bug list for netcfg. > > For future reference: you can avoid being in the situation you have now > by > > 1. preseeding with netcfg/target_network_config=ifupdown, or > 2. making a note of the contents of the installer's interfaces file in >/etc/network/ *before* finishing the installation. > > As for your present issue: > > allow-hotplug wlo1 > iface wlo1 inet dhcp > wpa-ssid > wpa-psk > > in /e/n/i should work. tried it, no effect, on close inspection of the boot-up process, the problem seems to be with the wifi hardware on my laptop. it takes more time to initialize and hence when "allow-hotplug" based commands are executed it isn't ready for work. after letting the system boot-up, i have to wait a few seconds before i can issue "ifup wlo1" and that too takes unusually long to complete. thanks nevertheless. :) ~mayuresh
x : keyboard not working
i have now reached a point at which i have given up on resetting
the display resolution to a desirable mode. all attempts based
on suggestions on the list as well on other sources on the web
have failed to produce results.
in desperation, i reached out to the "x windowing system" to
give me a readable font size by way of xterm windows.
i chose the venerable and light "mwm" and configured the
system as below;
.xinitrc
#!/bin/sh
xterm -geometry 80x24+100+100 &
xsetroot -solid black &
mwm
---
.mwmrc
Menu DefaultRootMenu
{
"Root Menu" f.title
"New Window"f.exec "xterm &"
"Shuffle Up"f.circle_up
"Shuffle Down" f.circle_down
"Refresh" f.refresh
"Pack Icons"f.pack_icons
! "Toggle Behavior..."f.set_behavior
no-label f.separator
"Restart..."f.restart
"Quit..." f.quit_mwm
}
!!
!! Default Window Menu Description
!!
Menu DefaultWindowMenu
{
Restore _R AltF5 f.restore
Move_M AltF7 f.move
Size_S AltF8 f.resize
Minimize_n AltF9 f.minimize
Maximize_x AltF10 f.maximize
Lower _L AltF3 f.lower
no-labelf.separator
Close _C AltF4 f.kill
}
!!
!! Key Binding Description
!!
Keys DefaultKeyBindings
{
ShiftEscapewindow|icon f.post_wmenu
Altspace window|icon f.post_wmenu
AltTab root|icon|windowf.next_key
Alt ShiftTab root|icon|windowf.prev_key
AltEscape root|icon|windowf.circle_down
Alt ShiftEscaperoot|icon|windowf.circle_up
Alt Shift Ctrlexclam root|icon|window f.set_behavior
AltF6 window f.next_key transient
Alt ShiftF6window f.prev_key transient
ShiftF10 iconf.post_wmenu
! Alt ShiftDeleteroot|icon|windowf.restart
}
!!
!! Button Binding Description(s)
!!
Buttons DefaultButtonBindings
{
icon|frame f.raise
icon|frame f.post_wmenu
rootf.menu DefaultRootMenu
}
Buttons ExplicitButtonBindings
{
frame|icon f.raise
frame|icon f.post_wmenu
rootf.menu DefaultRootMenu
! iconf.restore
Alt window|icon f.lower
! Alt window|icon f.resize
! Alt window|icon f.move
}
Buttons PointerButtonBindings
{
frame|icon f.raise
frame|icon f.post_wmenu
rootf.menu DefaultRootMenu
window f.raise
! iconf.restore
Alt window|icon f.lower
! Alt window|icon f.resize
! Alt window|icon f.move
}
the above configurations were created by working on copies of
system configuration files delivered along with the installs.
the 'gui' works on executing 'startx' at the command prompt.
and the system "looks" beautiful (in a minimalistic way).
but, the keyboard isn't working under x, no input accepted.
mouse pointer works just fine.
any help and/or pointers in the right direction would be most
welcome.
thanks,
~mayuresh
Re: text-mode : console : resolution : vga 80x25 : how to set?
On 2017-10-06 05:30 PM, Darac Marjal wrote: On Fri, Oct 06, 2017 at 03:00:50PM +0530, Mayuresh Kathe wrote: i tried my level best to do it, but have failed. i used 'dpkg-reconfigure console-setup' and followed the appropriate steps, but yet my console's screen resolution is way to high. not that it's a big problem, just an irritant, the text is usually too tiring to read. can i be helped? Yes. Presumably your system is using "kernel mode setting", wherein the kernel is able to set the resolution of the screen. This results, as you note, in a high-resolution console. would there be any simple way (instead of recompiling the kernel) to disable that kernel mode setting for the resolution? thanks, ~mayuresh
Re: 9.1.0 : netinst : installs well, but useless after firstboot
On 2017-10-06 04:06 PM, Brian wrote: On Fri 06 Oct 2017 at 13:34:55 +0530, Mayuresh Kathe wrote: On Fri, Oct 06, 2017 at 06:03:24PM +1100, Zenaan Harkness wrote: > > Are you sure? You may be right - but double check to make sure... yes, i am very sure. double checked. the interface wlo1 exists. there's a procedure mentioned in the wiki which shows how to setup wifi via wpa_supplicant through modifications to the file; /etc/network/interfaces it's now working, but not automatically coming up, i still have to manually issue 'ifup wlo1' in spite of having mentioned "auto" in the configuration file for the "wlo1" interface. off to check on that now, but if someone has any advice, please do share, it would be most welcome. :) it kind-a sucks that the debian installer accepts all the wifi parameters, activates the network only during installation and then does not include that information for post install work. atleast provide an option during the installation to accept the parameters and have them persist after the installation is done. What DE did you install from the installer? 'de'? desktop environment! i did not install any graphical system, i prefer to work at the text console, that's why i am on debian, else would have been on ubuntu. thanks, ~mayuresh
text-mode : console : resolution : vga 80x25 : how to set?
i tried my level best to do it, but have failed. i used 'dpkg-reconfigure console-setup' and followed the appropriate steps, but yet my console's screen resolution is way to high. not that it's a big problem, just an irritant, the text is usually too tiring to read. can i be helped? thanks, ~mayuresh
Re: 9.1.0 : netinst : installs well, but useless after firstboot
On Fri, Oct 06, 2017 at 06:03:24PM +1100, Zenaan Harkness wrote: > On Fri, Oct 06, 2017 at 12:10:09PM +0530, Mayuresh Kathe wrote: > > On 2017-10-06 11:56 AM, Zenaan Harkness wrote: > > > On Fri, Oct 06, 2017 at 11:07:22AM +0530, Mayuresh Kathe wrote: > > > > hello, > > > > > > > > i just installed the firmware netinst version of 9.1.0 from; > > > > https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/9.1.0+nonfree/amd64/iso-cd/firmware-9.1.0-amd64-netinst.iso > > > > and post first boot failed to get the network readily available. > > > > > > > > the biggest problem is that my machine does not have a wired > > > > network interface, only wifi (which works just fine under ubuntu > > > > 17.04), and so can't figure out how to move ahead without having to > > > > reboot off the ubuntu 17.04 in "live" mode. > > > > > > > > any help on how to proceed with setting up the network after > > > > completion of the install (in spite of having had setup the network > > > > during install) would be most welcome. > > > > > > Install a firmware for your wifi perhaps? If you have Intel, this > > > could be the package required: > > > > > > firmware-iwlwifi > > > > > > Unfortunately this may mean manually downloading the .deb file, > > > transferring it via sneakernet (or saving to a known hdd location) > > > and using a command like: > > > > > > dpkg --install firmware-iwlwifideb > > > > the firmware is already installed during installation process. > > Are you sure? You may be right - but double check to make sure... yes, i am very sure. double checked. the interface wlo1 exists. there's a procedure mentioned in the wiki which shows how to setup wifi via wpa_supplicant through modifications to the file; /etc/network/interfaces it's now working, but not automatically coming up, i still have to manually issue 'ifup wlo1' in spite of having mentioned "auto" in the configuration file for the "wlo1" interface. off to check on that now, but if someone has any advice, please do share, it would be most welcome. :) it kind-a sucks that the debian installer accepts all the wifi parameters, activates the network only during installation and then does not include that information for post install work. atleast provide an option during the installation to accept the parameters and have them persist after the installation is done. thanks, ~mayuresh
Re: 9.1.0 : netinst : installs well, but useless after firstboot
On 2017-10-06 11:56 AM, Zenaan Harkness wrote: On Fri, Oct 06, 2017 at 11:07:22AM +0530, Mayuresh Kathe wrote: hello, i just installed the firmware netinst version of 9.1.0 from; https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/9.1.0+nonfree/amd64/iso-cd/firmware-9.1.0-amd64-netinst.iso and post first boot failed to get the network readily available. the biggest problem is that my machine does not have a wired network interface, only wifi (which works just fine under ubuntu 17.04), and so can't figure out how to move ahead without having to reboot off the ubuntu 17.04 in "live" mode. any help on how to proceed with setting up the network after completion of the install (in spite of having had setup the network during install) would be most welcome. Install a firmware for your wifi perhaps? If you have Intel, this could be the package required: firmware-iwlwifi Unfortunately this may mean manually downloading the .deb file, transferring it via sneakernet (or saving to a known hdd location) and using a command like: dpkg --install firmware-iwlwifideb the firmware is already installed during installation process. that's how the rest of the additional software did get installed in the first place. but, then, after first boot, bang, there's no network. i have experienced this even during previous debian versions on previous (older) hardware. everything during install proceeds just smoothly, but the moment after first boot, the wifi isn't ready for use. am now going through the debian wiki, maybe that might have some pointers about how i could move ahead on this, in the meanwhile if anyone has any suggestions, they are most welcome. :) thanks, ~mayuresh
9.1.0 : netinst : installs well, but useless after firstboot
hello, i just installed the firmware netinst version of 9.1.0 from; https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/9.1.0+nonfree/amd64/iso-cd/firmware-9.1.0-amd64-netinst.iso and post first boot failed to get the network readily available. the biggest problem is that my machine does not have a wired network interface, only wifi (which works just fine under ubuntu 17.04), and so can't figure out how to move ahead without having to reboot off the ubuntu 17.04 in "live" mode. any help on how to proceed with setting up the network after completion of the install (in spite of having had setup the network during install) would be most welcome. thanks, ~mayuresh
Re: Debian Jessie : regular console instead of a hi-res one!
On Mon, Sep 05, 2016 at 06:36:05PM +0100, Brian wrote: > > I'm surprised the OP didn't test them with > > dpkg-reconfigure console-setup This worked. I now have a sane console setting. :) Thanks for that tip Brian. ~Mayuresh
Debian Jessie : regular console instead of a hi-res one!
Hi, Is there any way to get a regular console under Debian Jessie? I don't use a GUI, just plain old CLI, and working on hi-res with "tiny" little fonts is extremely painful. I have tried playing with "console-setup". No results. ~Mayuresh
