search for: 3f8

I'm trying to get isolinux serial port working on a system. Using UEFI boot mode but system does not have Legacy Serial port (3f8, etc) enabled. Serial port devices are PCI devices, memory mapped I/O with 32-bit offset. Using linux kernel command line console=uart8250,mmio32,xxxx,115200n8 works. However I do not see syslinux/isolinux boot menu. Looking through the code it looks like syslinux assumes serial ports are I/O o...

Hello, I just discovered a strange bug with serial passthrough in xen 4.1 on Debian Wheezy. The Dom0 has a GSM modem connected to serial port. The serial port is passed through to a DomU with options 'irq = [ 4 ]' and 'ioports = [ '3f8-3ff ]'. This worked as expected on Debian Squeeze with Xen 4.0 and Linux kernel 2.6.32 (both for Dom0 and DomU). On Debian Wheezy with Xen 4.1 and Linux kernel 3.2.0 the passthrough seems to work as well (/dev/ttyS0 appears in dmesg of DomU), but something is wrong. The GSM modem doesn't b...

Hello, I just discovered a strange bug with serial passthrough in xen 4.1 on Debian Wheezy. The Dom0 has a GSM modem connected to serial port. The serial port is passed through to a DomU with options 'irq = [ 4 ]' and 'ioports = [ '3f8-3ff ]'. This worked as expected on Debian Squeeze with Xen 4.0 and Linux kernel 2.6.32 (both for Dom0 and DomU). On Debian Wheezy with Xen 4.1 and Linux kernel 3.2.0 the passthrough seems to work as well (/dev/ttyS0 appears in dmesg of DomU), but something is wrong. The GSM modem doesn't b...

...owed: 1) I have xencons=off as a kernel arg for dom0, and when dom0 boots, it finds the serial port. 2) I have blacklisted 8250, 8250_pnp and serial_core, rebooted, no serial port under dom0 3) added the following to my domu config (domu is 32bit centos 5.2, pvm) addirq = [ 4 ] ioports = [ "3f8-3ff" ] 4) now to start the vm and see what happens: # xm create mythserver Using config file "./mythserver". Error: function takes exactly 4 arguments (3 given) My host is 64 bit centos 5.2, domu is 32 bit centos 5.2. I'm running the stock redhat version of xen that ships with...

I configured a domU to access to the physical serial port of the dom0 (/dev/ttyS0) typing this in the domU configuration file: irq = [ 4 ] ioports = [ "3f8-3ff" ] The domU starts without any error, but the serial port isn''t recognised. The /dev/ttyS0 device exists on the domU, and I blacklisted the serial_core, the 8250 and 8250_pnp modules on the dom0. What is the problem? Could you help me, please? Thank you very much! Bye. _______...

Hello Can anyone share a known working config for xen which would transfer a serial interface ( add-on card preferably, mine uses e880-e887 : 0000:03:05.0 / ec00-ec07 : 0000:03:05.0 ) to a DomU ? I've been trying with the stock packages from Centos 5.5 ( fully updated) and also with gitco's 3.4.3 but after 2 days of googling and testing we still fail to access the serial

Greetings, Using Xen 3.1 and Fedora 7, is it possible to export the serial interface such that I can access external devices on COM1 or COM2? I am uncertain if PCI pass-thru is needed or if there''s nothing to configure for this to work in a fully virtualized Linux guest. Any help would be greatly appreciated. Regards, Tony Johnson _______________________________________________

...t;3ea> DW_AT_decl_line : 16 <3eb> DW_AT_type : <0x3f> <3ef> DW_AT_location : 0x6f (location list) <2><3f3>: Abbrev Number: 22 (DW_TAG_formal_parameter) <3f4> DW_AT_name : (indirect string, offset: 0x107): argv <3f8> DW_AT_decl_file : 1 <3f9> DW_AT_decl_line : 16 <3fa> DW_AT_type : <0x58b> <3fe> DW_AT_location : 0xa8 (location list) <2><402>: Abbrev Number: 23 (DW_TAG_variable) <403> DW_AT_name : i <405>...

...0xd9010000-0xd901ffff at device 0.1 on pci1 acpi_tz0: <Thermal Zone> on acpi0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] ppc0: <Parallel port> port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: <Parallel port bus> on ppc0 ppbus0: [I...

...ked for firmware updates? Have you tried > experimenting with redoing what serial port is assigned what IO base > address to make it consistent between Syslinux and Linux? > > Alternatively, have you considered specifying the full IO address > instead of the low number (like "0x3F8")? > > Hi, actually I didn't do much with Syslinux myself. I found the issue with Grub2 first, and after I brief exchange about it on the Linux-Serial mailing list I decided to look up how Syslinux handles this, and found it has the same problem as Grub2. So I decided to do a goo...

...________________________ To have access to the serial port in DomU, we need to prevent Dom0 from taken hold of this piece of hardware add to /etc/hotplug/blacklist the following modules to exclude from being loaded 8250 8250_pnp serial_core domU config: irq = [ 4 ] ioports = [ "3f8-3ff" ] to load the modules in domU. I had to install module-init-tools I have copied /lib/modules/2.6.11.10-xenU/modules.dep and copied the serials modules to domU I also had to change the permissions of /dev/ttyS0 to 666 I have added the modules to /etc/modules so they load on boot...

...nder domU: - Tell Xen to use something else for its console: in /boot/grub/menu.lst, add "console=xvc0 xencons=xvc0" to the kernel parameters (maybe just xencons is needed) - Tell Xen to "show" IRQ/port to the domU: in domU''s .cfg add addirq = [ 4 ] ioports = [ "3f8-3ff" ] - Tell the domU to autoload the serial module: create in /etc/sysconfig/modules an executable script containing modprobe 8250 Bye! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...nder domU: - Tell Xen to use something else for its console: in /boot/grub/menu.lst, add "console=xvc0 xencons=xvc0" to the kernel parameters (maybe just xencons is needed) - Tell Xen to "show" IRQ/port to the domU: in domU''s .cfg add addirq = [ 4 ] ioports = [ "3f8-3ff" ] - Tell the domU to autoload the serial module: create in /etc/sysconfig/modules an executable script containing modprobe 8250 Bye! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users ____________...

Hi. I''m trying to setup the serial port access from the domU following the instructions at http://wiki.xensource.com/xenwiki/InstallationNotes. So I addedd these configurations to the domU cfg file: irq = [ 4 ] ioports = [ "3f8-3ff" ] When I create this new domU I get this error: Error: function takes exactly 3 arguments (2 given) Is it a bug? I read on this list that you adive a change in the /usr/lib/python/xen/xend/server/irqif.py, but it didn''t fix the problem for me. Could you help me, please? Thank...

...domU : $ grep serial /proc/ioports $ dmesg | grep ttyS $ stty -aF /dev/ttyS0 stty: /dev/ttyS0: Input/output error $ ls -l /dev/ttyS0 crw-rw----. 1 root dialout 4, 64 Apr 12 04:46 /dev/ttyS0 Is there any thing to do in addition to the Xen-3 usual configuration : irq = [ 4 ] ioports = [ "3f8-3ff" ] Thanks, -- Philippe Naudin

...: src:linux Version: 3.2.41-2 Severity: important Hello, I just discovered a strange bug with serial passthrough in xen 4.1 on Debian Wheezy. The Dom0 has a GSM modem connected to serial port. The serial port is passed through to a DomU with options 'irq = [ 4 ]' and 'ioports = [ '3f8-3ff ]'. This worked as expected on Debian Squeeze with Xen 4.0 and Linux kernel 2.6.32 (both for Dom0 and DomU). On Debian Wheezy with Xen 4.1 and Linux kernel 3.2.0 the passthrough seems to work as well (/dev/ttyS0 appears in dmesg of DomU), but something is wrong. The GSM modem doesn't b...

...ates? Have you tried >> experimenting with redoing what serial port is assigned what IO base >> address to make it consistent between Syslinux and Linux? >> >> Alternatively, have you considered specifying the full IO address >> instead of the low number (like "0x3F8")? >> >> > Hi, > > actually I didn't do much with Syslinux myself. I found the issue with Grub2 > first, and after I brief exchange about it on the Linux-Serial mailing list > I decided to look up how Syslinux handles this, and found it has the same > problem...

Timo, I see where at least one other person reported this, but here goes. I went from rc24 to rc25 this morning, and I got an assert and core from my own mailbox withing five minutes: Mar 2 06:52:26 karst dovecot: [ID 107833 mail.error] IMAP(jaearick): file mbox-sync-rewrite.c: line 408: assertion failed: (need_space == (uoff_t)-mails[idx].space) Mar 2 06:52:26 karst dovecot: [ID 107833

Keir, is there a particular reason you chose to use slightly different special mode numbers than Linux, ignoring VIDEO_CURRENT_MODE altogether? I think it wouldn''t be bad to be in sync with Linux here, and I independently think that having a way to avoid mode switching altogether is good to have in case of possible problems on exotic hardware. Jan

...2.6.21.5, 2.6.22.1, 2.6.22.9 Distro(s): slackware 11-12 , now zenwalk 4.8 (was 4.6.1) Application: Dynamic-C v9.21 (Full commercial license) --> http://appdb.winehq.org/objectManager.php?sClass=version&iId=9356 ##### port setup ##### root[drive_c]# dmesg | grep tty 00:0c: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A root[drive_c]# ls -l /dev/ttyS0 lrwxrwxrwx 1 root root 5 2007-10-05 08:39 /dev/ttyS0 -> tts/0 root[drive_c]# ls -l /dev/tts/0 crwxrwx-w- 1 root tty 4, 64 2007-10-05 10:04 /dev/tts/0 root[drive_c]# setserial -abGv /dev/ttyS0 /dev/ttyS0 uart 16550A port 0x03f8 irq 4 baud_base...