[Bug 268685] Re: IO errors in install.py, such as ENOSPC should give more detailed errors to the UI.

[schof]

I also am having a similar problem. I am trying to use the utility to
put an ISO of eeebuntu on a flash drive and getting error 256.

More details: Tried on both Sandisk Cruzer Micro 1GB USB and a Kingston
DataTraveler 4GB. Both return similar errors:

[11:16:34] new device:
{'capacity': dbus.UInt64(4002934784L), 'uuid': '3433-3231', 'label': 
'KINGSTON', 'free': 3790135296L, 'fstype': 'vfat', 'device': '/dev/sdb1', 
'mountpoint': '/media/KINGSTON', 'udi': 
'/org/freedesktop/Hal/devices/volume_uuid_3433_3231'}
[11:16:34] adding: /dev/sdb1
[11:16:45] mounting /home/schof/Desktop/eeebuntu-2.0-nbr.iso
[11:16:45] updating dest_status as part of update_row_state
[11:16:49] Installing...
[11:16:49] Source CD: /home/schof/Desktop/eeebuntu-2.0-nbr.iso
[11:16:49] Destination disk: /dev/sdb1
[11:16:49] Persistence size: 128 MB
[11:16:49] Marking partition 1 as active.
[11:16:49] installing the bootloader to /dev/sdb1.
[11:17:00] ['/usr/share/usb-creator/install.py', '-s', '/tmp/tmpZh9c-_/.', 
'-t', '/media/KINGSTON', '-p', '128']
[11:18:35] Unmounting source volume.
[11:18:35] Install command exited with code: 256
[11:18:35] Forcing shutdown of the install process.
[11:18:35] Unmounting source volume.
[11:18:35] Install failed.

any help would be appreciated.

-- 
IO errors in install.py, such as ENOSPC should give more detailed errors to the 
UI.
https://bugs.launchpad.net/bugs/268685
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 42607] Re: Ubuntu Dapper on VIA EPIA-MS; no video after installation

[Schof]

Sorry, we're no longer using that hardware (for unrelated reasons) so  
I can't provide any further information.



Sincerely,


John Schofield



--
John Schofield
Director, Information Technology

Dakim, Inc.
2121 Cloverfield Blvd.
Suite 205
Santa Monica, CA 90404

www.dakim.com
[EMAIL PROTECTED] (e-mail)
dakimschof (AIM)

(310) 566-1350 (Main)
(310) 566-1355 (Direct)
(310) 829-1865 (Fax)

(800) 853-7289 (Tech. Support)
[EMAIL PROTECTED] (Tech. Support)


On Jun 13, 2007, at 10:52 AM, Bryce Harrington wrote:

 Hi Schof,

 It sounds like with LVDS, the EDID info is not getting communicated
 properly, or else the driver is misinterpreting it.

 Have you been able to get this working, perhaps with a newer  
 version of
 Ubuntu?

 If not, from the thread you point to, they offer some additional  
 steps to try - have you tested them?
 - Try setting Option VBEModes
 - Try the vesa driver

 Also, I notice in your xorg.conf that the horizontal and vertical
 refresh rates are set to generic values (a common issue with mis-
 detected monitors).  I would suggest either manually specifying those
 values for the monitor (you can often find them from the monitor's
 manual), or else if you're running Feisty or Gutsy, try commenting  
 them
 out so xorg can try autodetecting them.


 ** Summary changed:

 - Ubuntu Dapper on VIA EPIA-MS; no video after installation
 + Ubuntu Dapper on VIA EPIA-MS with LVDS; no video after installation

 -- 
 Ubuntu Dapper on VIA EPIA-MS with LVDS; no video after installation
 https://bugs.launchpad.net/bugs/42607
 You received this bug notification because you are a direct subscriber
 of the bug.

-- 
Ubuntu Dapper on VIA EPIA-MS with LVDS; no video after installation
https://bugs.launchpad.net/bugs/42607
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs